[partially solved(in a way)]"Your data may be corrupted" on LineageOS nightly if I update the os.

Search This thread

User699

Senior Member
Feb 28, 2021
99
1
12
8
I am using Xiaomi Mi A2, jasmine-sprout, Android 10 and it is rooted with magisk without gapps. Also, I am using the official LinageOS.

I am trying to update my LineageOS, but it always says "Your data may be corupted". I just don't want to delete my data (factory reset), just to update my os...

I have that problem since I installed lineage for the very first time in Nov.2020. It does not work manually with twrp and neither with lineage's recovery. It also doesn't work with the inbuild updater app.
While updating with twrp, I viewed the logcat using `adb logcat' and it installed successfully. But after rebooting it booted to stock lineage recovery telling me my data may be corrupted. (btw, I booted twrp using `fastboot boot twrp')

If I press on that `try again' button often enough, it boots into the os again.. But that os isn't updated...


I know there are a lot of issues like that, but none solved mine...
I reflashed the os again and did a factory reset once. It worked after doing a factory reset, but I cannot do that for every update.
The problem is that I also can't backup my whole files, apps and settings because seedvault wouldn't recovery them correctly and via twrp everything is encrypted (Seems to be an Android 10 issue... Besides: I also had to use an unoffical twrp somewhere from here, because the official one didn't even start).

On this offical site https://wiki.lineageos.org/devices/jasmine_sprout/install they told me I could ask for support on freenode. However, after 4 hours only one person tried to help, another stuff member just told me "i'm not interested in figuring out your issue". However, that very same person told me that that screen (the screen with try again / format data.) I get is called `rescue party'.

Edit: The staff member told me that there is an os on slot a and b and that the recovery is on both (I thought on one slot there is the recovery and on the other one there's the os). So that my device boots after pressing often enough on the `try again' button is because it boots the othere slot which still contains the unupdated os (that's what the support told me).

Since this issue couldn't be solved by their support as well, they finally pointed me to you.

I really hope you can help me! And if you need anything, just ask for it.
 

tecknight

Recognized Contributor
Jun 12, 2010
986
849
123
Las Vegas
OK @User699 I have some ideas as to what your issues are.
But I have several questions and/or requests for you in order to determine what your issues are.

It sounds to me like your userdata is encrypted and LineageOS has access to the encryption keys, but perhaps your recovery does not have access to the keys.
FYI: RescueParty is a boot subsystem that attempts to recover if a bootloop is detected.

Here are some questions or requests that I need you to answer:

1. When you boot your system normally, you DO have access to your userdata partition.
You can install or remove apps and otherwise function normally when you boot into LineageOS, correct ?

2. Which recovery (type and version, ie: TWRP ver 3.4.0.1) do you currently have installed ?
You mentioned booting into TWRP by telling fastboot to boot the TWRP directly.

3. You say you have Magisk installed, so I need you to boot up, enable adb, connect a USB cable and open up a Windows command line.
in the command line, type:
adb shell + enter
You should see something like:
jasmine_sprout: / $
Now type:
su + enter
you should see:
jasmine_sprout: / #
Now type:
ls /dev/block/by-name -l + enter
copy the output and post it to this thread.
Thanks.

4. You can boot your phone into fastboot mode and run fastboot commands from as PC, correct ?

5. Download this image: https://androidfilehost.com/?fid=17248734326145702860
I will tell you what to do with it in a minute

Once you respond, I will tell you what you need to do next. If you can get to the adb shell and get root by running su, we should be able to backup everything, so worst case we CAN wipe your data, update your ROM, then restore your data
 
Last edited:
  • Like
Reactions: User699

User699

Senior Member
Feb 28, 2021
99
1
12
8
Thank you very much for answering @tecknight !

1. Yes, all that works perfectly.

2. Currently I have the official lineage recovery installed which was the newest when I flashed my ROM for the very first time. It's called lineage-17.1-20201114-recovery-jasmine_sprout.img.
I booted TWRP with fastboot, that's true. I am using an unofficial twrp which I got somewhere from here. It says 3.4.0-0 is its version (official twrp didn't boot).

3. Here's the output from ls /dev/block/by-name -l :

Bash:
total 0
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 abl_a -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 abl_b -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 apdp -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 bk1 -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 bluetooth_a -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 bluetooth_b -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 boot_a -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 boot_b -> /dev/block/mmcblk0p63
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 cache -> /dev/block/mmcblk0p64
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 cmnlib64_a -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 cmnlib64_b -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 cmnlib_a -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 cmnlib_b -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 ddr -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 devcfg_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 devcfg_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 devinfo -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 dip -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 1972-03-24 14:06 dpo -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 dsp_a -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 dsp_b -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 frp -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 1972-03-24 14:06 fsc -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 fsg -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 hyp_a -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 hyp_b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 keymaster_a -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 keymaster_b -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 keystore -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 1972-03-24 14:06 limits -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 logdump -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 logfs -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 mdtp_a -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 mdtp_b -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 mdtpsecapp_a -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 mdtpsecapp_b -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 minidump -> /dev/block/mmcblk0p61
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 misc -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 18 1972-03-24 14:06 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 22 1972-03-24 14:06 mmcblk0rpmb -> /dev/block/mmcblk0rpmb
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 modem_a -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 modem_b -> /dev/block/mmcblk0p59
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 modemst1 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 modemst2 -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 msadp -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 oops -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 persist -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 persistbak -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 pmic_a -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 pmic_b -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 rawdump -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 rpm_a -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 rpm_b -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 1972-03-24 14:06 sec -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 splash -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 20 1972-03-24 14:06 ssd -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 sti -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 20 1972-03-24 14:06 storsec -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 1972-03-24 14:06 switch -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 system_a -> /dev/block/mmcblk0p65
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 system_b -> /dev/block/mmcblk0p66
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 toolsfv -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 tz_a -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 tz_b -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 userdata -> /dev/block/mmcblk0p69
lrwxrwxrwx 1 root root 20 1972-03-24 14:06 vbmeta_a -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1972-03-24 14:06 vbmeta_b -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 vendor_a -> /dev/block/mmcblk0p67
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 vendor_b -> /dev/block/mmcblk0p68
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 xbl_a -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1972-03-24 14:06 xbl_b -> /dev/block/mmcblk0p41

4. Yes, I can boot into fastboot and run fastboot commands.

5. Done.



Edit: I just booted your linked version of twrp. It asked me for a password first (all versions I tried didn't) and after I typed in my password it was able to decrypt my userdata! I'll wait for your instructions, but I'll just create a backup with every single entry that I can select there. Thanks already!
 
Last edited:

tecknight

Recognized Contributor
Jun 12, 2010
986
849
123
Las Vegas
I am so glad to hear about the TWRP being able to read your encrypted partitions.
The first thing I see is that your system is using a partition layout known as treble.
Treble is designed to make updates, especially OTA (over the air) updates safer.

To make the updates safer, treble has an a and b image of pretty much every partition that might change during an update.
The bootloader has an active slot indicator
When an OTA update is loaded, It updates the NON active slot. If the OTA is successful, the bootloader changes the active slot (from A to B, for instance), then reboots

Do you see that you have an a and b partition for:
boot
system
vendor
bluetooth
abl
cmnlib64
cmnlib
devcfg
dsp
hyp
keymaster
and several others

So I need you to boot the phone to fastboot, connect it to your PC and type:
fastboot getvar all + enter

Save the results and post them to this thread

Next, try flashing the TWRP image I had you download by placing the file twrp-3.5.0-jasmine_sprout.img in the folder containing your fastboot.exe and typing:

fastboot flash recovery twrp-3.5.0-jasmine_sprout.img + enter

If it successfully flashes recovery, type:
fastboot reboot recovery + enter

Now see if it loads up TWRP.
Thanks
 
Last edited:

User699

Senior Member
Feb 28, 2021
99
1
12
8
fastboot getvar all
Code:
prompt:~$ fastboot getvar all
getvar:all FAILED (remote: unknown command)
finished. total time: 0.000s

fastboot flash recovery <twrpimagename>
Code:
prompt:~$ fastboot flash recovery ./twrp-3.5.0-jasmine_sprout.img
target reported max download size of 805306368 bytes
sending 'recovery' (35497 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s

I could use
Code:
fastboot flash boot twrp.img
though.

EDIT: No, I can't, even though it worked that way with lineageOS' recovery. Output:
Code:
prompt:~$ fastboot flash boot ./twrp-3.5.0-jasmine_sprout.img
target didn't report max-download-size
sending 'boot' (35497 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s

Any idea @tecknight ?
 
Last edited:

tecknight

Recognized Contributor
Jun 12, 2010
986
849
123
Las Vegas
Try:
fastboot oem device-info

Really, fastboot getvar all shows nothing ?
My Xiaomi shows this:
C:\Program Files (x86)\Tiny ADB and Fastboot>fastboot getvar all
(bootloader) DP:0x0
(bootloader) token:VQEBIQEQ1kekQ0NylG8kUtJFKdSXfwMHY3VydGFuYQIEHRKPsg
(bootloader) parallel-download-flash:yes
(bootloader) hw-revision:10001
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes-
(bootloader) battery-voltage:3884
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x1000
(bootloader) logical-block-size: 0x1000
(bootloader) variant:SM_ UFS
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x20000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0xA00000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x200000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x200000
(bootloader) partition-type:ALIGN_TO_128K_2:raw
(bootloader) partition-size:ALIGN_TO_128K_2: 0x1A000
(bootloader) partition-type:bootbak:raw
(bootloader) partition-size:bootbak: 0x8000000
(bootloader) partition-type:dtbobak:raw
(bootloader) partition-size:dtbobak: 0x1800000
(bootloader) partition-type:vbmetabak:raw
(bootloader) partition-size:vbmetabak: 0x10000
(bootloader) partition-type:dtbo:raw
(bootloader) partition-size:dtbo: 0x1800000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0x8000000
(bootloader) partition-type:vbmeta:raw
(bootloader) partition-size:vbmeta: 0x10000
(bootloader) partition-type:catecontentfv:raw
(bootloader) partition-size:catecontentfv: 0x100000
(bootloader) partition-type:catefv:raw
(bootloader) partition-size:catefv: 0x80000
(bootloader) partition-type:secdata:raw
(bootloader) partition-size:secdata: 0x7000
(bootloader) partition-type:uefivarstore:raw
(bootloader) partition-size:uefivarstore: 0x80000
(bootloader) partition-type:multiimgqti:raw
(bootloader) partition-size:multiimgqti: 0x8000
(bootloader) partition-type:multiimgoem:raw
(bootloader) partition-size:multiimgoem: 0x8000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:cateloader:raw
(bootloader) partition-size:cateloader: 0x200000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x1000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x20A4000
(bootloader) partition-type:spunvm:raw
(bootloader) partition-size:spunvm: 0x800000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:uefisecappbak:raw
(bootloader) partition-size:uefisecappbak: 0x200000
(bootloader) partition-type:imagefvbak:raw
(bootloader) partition-size:imagefvbak: 0x200000
(bootloader) partition-type:qupfwbak:raw
(bootloader) partition-size:qupfwbak: 0x10000
(bootloader) partition-type:devcfgbak:raw
(bootloader) partition-size:devcfgbak: 0x20000
(bootloader) partition-type:cmnlib64bak:raw
(bootloader) partition-size:cmnlib64bak: 0x80000
(bootloader) partition-type:cmnlibbak:raw
(bootloader) partition-size:cmnlibbak: 0x80000
(bootloader) partition-type:keymasterbak:raw
(bootloader) partition-size:keymasterbak: 0x80000
(bootloader) partition-type:dspbak:raw
(bootloader) partition-size:dspbak: 0x2000000
(bootloader) partition-type:ablbak:raw
(bootloader) partition-size:ablbak: 0x800000
(bootloader) partition-type:mdtpbak:raw
(bootloader) partition-size:mdtpbak: 0x2000000
(bootloader) partition-type:mdtpsecappbak:raw
(bootloader) partition-size:mdtpsecappbak: 0x400000
(bootloader) partition-type:bluetoothbak:raw
(bootloader) partition-size:bluetoothbak: 0x100000
(bootloader) partition-type:modembak:raw
(bootloader) partition-size:modembak: 0x10000000
(bootloader) partition-type:hypbak:raw
(bootloader) partition-size:hypbak: 0x80000
(bootloader) partition-type:tzbak:raw
(bootloader) partition-size:tzbak: 0x400000
(bootloader) partition-type:aopbak:raw
(bootloader) partition-size:aopbak: 0x80000
(bootloader) partition-type:uefisecapp:raw
(bootloader) partition-size:uefisecapp: 0x200000
(bootloader) partition-type:imagefv:raw
(bootloader) partition-size:imagefv: 0x200000
(bootloader) partition-type:qupfw:raw
(bootloader) partition-size:qupfw: 0x10000
(bootloader) partition-type:devcfg:raw
(bootloader) partition-size:devcfg: 0x20000
(bootloader) partition-type:cmnlib64:raw
(bootloader) partition-size:cmnlib64: 0x80000
(bootloader) partition-type:cmnlib:raw
(bootloader) partition-size:cmnlib: 0x80000
(bootloader) partition-type:keymaster:raw
(bootloader) partition-size:keymaster: 0x80000
(bootloader) partition-type:dsp:raw
(bootloader) partition-size:dsp: 0x2000000
(bootloader) partition-type:abl:raw
(bootloader) partition-size:abl: 0x800000
(bootloader) partition-type:mdtp:raw
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:mdtpsecapp:raw
(bootloader) partition-size:mdtpsecapp: 0x400000
(bootloader) partition-type:bluetooth:raw
(bootloader) partition-size:bluetooth: 0x100000
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0x10000000
(bootloader) partition-type:hyp:raw
(bootloader) partition-size:hyp: 0x80000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x400000
(bootloader) partition-type:aop:raw
(bootloader) partition-size:aop: 0x80000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:cdt:raw
(bootloader) partition-size:cdt: 0x20000
(bootloader) partition-type:ALIGN_TO_128K_1:raw
(bootloader) partition-size:ALIGN_TO_128K_1: 0x1A000
(bootloader) partition-type:xbl_configbak:raw
(bootloader) partition-size:xbl_configbak: 0x20000
(bootloader) partition-type:xblbak:raw
(bootloader) partition-size:xblbak: 0x700000
(bootloader) partition-type:xbl_config:raw
(bootloader) partition-size:xbl_config: 0x20000
(bootloader) partition-type:xbl:raw
(bootloader) partition-size:xbl: 0x700000
(bootloader) partition-type:userdata:f2fs
(bootloader) partition-size:userdata: 0x1A2CDD3000
(bootloader) partition-type:super:raw
(bootloader) partition-size:super: 0x200000000
(bootloader) partition-type:ffu:raw
(bootloader) partition-size:ffu: 0x800000
(bootloader) partition-type:gsort:raw
(bootloader) partition-size:gsort: 0x1000000
(bootloader) partition-type:exaid:raw
(bootloader) partition-size:exaid: 0x18000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x18000000
(bootloader) partition-type:metadata:raw
(bootloader) partition-size:metadata: 0x1000000
(bootloader) partition-type:vbmeta_systembak:raw
(bootloader) partition-size:vbmeta_systembak: 0x10000
(bootloader) partition-type:vbmeta_system:raw
(bootloader) partition-size:vbmeta_system: 0x10000
(bootloader) partition-type:recoverybak:raw
(bootloader) partition-size:recoverybak: 0x8000000
(bootloader) partition-type:recovery:raw
(bootloader) partition-size:recovery: 0x8000000
(bootloader) partition-type:cust:raw
(bootloader) partition-size:cust: 0x40000000
(bootloader) partition-type:minidump:raw
(bootloader) partition-size:minidump: 0x8000000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-type:persist:raw
(bootloader) partition-size:persist: 0x2000000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) secure:yes
(bootloader) serialno:591c2700
(bootloader) anti:1
(bootloader) cpuid:0x1d128fb2
(bootloader) product:curtana
(bootloader) is-userspace:no
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
all:

Finished. Total time: 0.162s
 

User699

Senior Member
Feb 28, 2021
99
1
12
8
fastboot oem device-info
Code:
prompt:~$ fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [  0.001s]
finished. total time: 0.001s

Yes, fastboot getvar all only gave me the above output (the one I inserted in my previous reply).
 

tecknight

Recognized Contributor
Jun 12, 2010
986
849
123
Las Vegas
OK, try:
fastboot getvar partition-type:recovery

fastboot getvar partition-size:recovery

My deviceinfo:

C:\Program Files (x86)\Tiny ADB and Fastboot>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.005s]
Finished. Total time: 0.006s
 
Last edited:

User699

Senior Member
Feb 28, 2021
99
1
12
8
fastboot getvar partition-type:recovery
Code:
prompt:~$ fastboot getvar partition-type:recovery
getvar:partition-type:recovery FAILED (remote: unknown command)
finished. total time: 0.000s

fastboot getvar partition-size:recovery
Code:
prompt:~$ fastboot getvar partition-size:recovery
getvar:partition-size:recovery FAILED (remote: GetVar Variable Not found)
finished. total time: 0.001s
 

User699

Senior Member
Feb 28, 2021
99
1
12
8
Something is odd about it... I tried different getvar commands found here http://adbcommand.com/fastboot and after I typed in fastboot getvar product, the fastboot picture on my device disappeared and showed
Press any key to continue
instead.
I did that and it rebooted normally into my system. However, I bootet into fastboot again and tried the exact command again and it gave me that:

Code:
prompt:~$ fastboot getvar product
product: jasmine
finished. total time: 0.001s
Right after that I inserted the same again and it gave me
Code:
prompt:~$ fastboot getvar product
getvar:product FAILED (remote: unknown command)
finished. total time: 0.000s
and after I tried again I got the same text again which I quoted above...
 

tecknight

Recognized Contributor
Jun 12, 2010
986
849
123
Las Vegas
OK, do you have a Micro SD ?
If you do, make sure it's in your phone and lets boot TWRP:
fastboot boot recovery twrp-3.5.0-jasmine_sprout.img

do a backup to your MicroSD using TWRP.
When it's done stay in TWRP, cuz we need to do more stuff
 

User699

Senior Member
Feb 28, 2021
99
1
12
8
OK, do you have a Micro SD ?
If you do, make sure it's in your phone and lets boot TWRP:
fastboot boot recovery twrp-3.5.0-jasmine_sprout.img

do a backup to your MicroSD using TWRP

No, this device doesn't have an sdcard. But I did a backup checking every option twrp provides and transfered it (and my pictures, files etc) to my computer.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    OK @User699 I have some ideas as to what your issues are.
    But I have several questions and/or requests for you in order to determine what your issues are.

    It sounds to me like your userdata is encrypted and LineageOS has access to the encryption keys, but perhaps your recovery does not have access to the keys.
    FYI: RescueParty is a boot subsystem that attempts to recover if a bootloop is detected.

    Here are some questions or requests that I need you to answer:

    1. When you boot your system normally, you DO have access to your userdata partition.
    You can install or remove apps and otherwise function normally when you boot into LineageOS, correct ?

    2. Which recovery (type and version, ie: TWRP ver 3.4.0.1) do you currently have installed ?
    You mentioned booting into TWRP by telling fastboot to boot the TWRP directly.

    3. You say you have Magisk installed, so I need you to boot up, enable adb, connect a USB cable and open up a Windows command line.
    in the command line, type:
    adb shell + enter
    You should see something like:
    jasmine_sprout: / $
    Now type:
    su + enter
    you should see:
    jasmine_sprout: / #
    Now type:
    ls /dev/block/by-name -l + enter
    copy the output and post it to this thread.
    Thanks.

    4. You can boot your phone into fastboot mode and run fastboot commands from as PC, correct ?

    5. Download this image: https://androidfilehost.com/?fid=17248734326145702860
    I will tell you what to do with it in a minute

    Once you respond, I will tell you what you need to do next. If you can get to the adb shell and get root by running su, we should be able to backup everything, so worst case we CAN wipe your data, update your ROM, then restore your data
    1
    It runs and tells me


    -- Further information following shortly --
    The cannot access /data is clearly due to the encryption
    1
    Update: I tried this https://www.thecustomdroid.com/install-ota-update-rooted-android-device-guide/ as well, but it won't boot either. There's just the rescue party.
    1
    Update:
    FIXED my error (at least I can update my system now).


    Here's what I did

    1) I applied that LOS system update to my inactive slot (b, in my case).
    2) Rebooted. And got rescue party. The log shows decryption problems, but I just proceeded anyways.
    3) I pressed the back arrow in the rescue party to get back to the main screen of LOS' recovery.
    4) Since I was in slot b now, I sideloaded the update package which is going to be applied to slot a in my case.
    5) Rebooted into system.
    6 DONE.

    I did't had to reset my data and the os in slot a is bootable and updated.



    However, slot b still is unbootable... But atleast I can Update my OS.



    Thank you @tecknight for all of your help and time! Even though we couldn't solve the unbootable slot b, you still helped me to learn a lot of interessting things and even provided a version of twrp which can decrypt my user data. Really, thank you!
    1
    Update:
    FIXED my error (at least I can update my system now).


    Here's what I did

    1) I applied that LOS system update to my inactive slot (b, in my case).
    2) Rebooted. And got rescue party. The log shows decryption problems, but I just proceeded anyways.
    3) I pressed the back arrow in the rescue party to get back to the main screen of LOS' recovery.
    4) Since I was in slot b now, I sideloaded the update package which is going to be applied to slot a in my case.
    5) Rebooted into system.
    6 DONE.

    I did't had to reset my data and the os in slot a is bootable and updated.



    However, slot b still is unbootable... But atleast I can Update my OS.



    Thank you @tecknight for all of your help and time! Even though we couldn't solve the unbootable slot b, you still helped me to learn a lot of interessting things and even provided a version of twrp which can decrypt my user data. Really, thank you!
    @User699 I'm glad you got this fixed.
    I was out of town for a couple days.
    Also I'm glad you (we) learned a lot in the process.
    It was a pleasure working with you. I expect to see you helping others as you are a quick learner, my friend.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone