- Jul 31, 2015
that's why I tried to reflash MIUI with MiFlash.. but due to the error, it didn't work. I also didn't want to try relocking, though.
You can't change the slots on the current TWRP, it's buggy.oh, and just one thought:
could it be, that ROM developers assume that currently installed MIUI ROM is always on a-slot? because a-slot is the default when you open a new phone.
but I did a firmware update before unlocking, and after that, it switched of course to b-slot. from then on it was the default.
now when I flash the ROMs, they might expect it to be a-slot when it is actually b-slot.
getvar snapshot-update-status— Returns the value that the boot control HAL communicated to the bootloader:
MERGING, the bootloader must return
SNAPSHOTTED, the bootloader must return
snapshot-update merge— Completes a merge operation, booting to recovery/fastbootd if necessary. This command is valid only if
merging, and is only supported in fastbootd.
snapshot-update cancel— Sets the boot control HAL's merge status to
CANCELLED. This command is invalid when the device is locked.
I have encountered this error before as well, but had to resolve it differently then.
then you manually flashed the boot.img to boot_a + boot_b with fastboot? I just tried to flash it with the flash_all.bat and MiFlash and whenever it wanted to touch the metadata partition the phone throw a remote error and wouldn't let me touch or change it. it's like read-only as long as the snapshot isn't cancelled. anyway, the fastboot command worked, thank goodness
no prob, i knew, I also just added that info so other people fighting the same problem and reading the post find the fitting tools right away.
I also installed this rom with twrp and I dont face any issues.let me note some things on installing CrDroid / LineageOS with TWRP alpha (06/2021).
This might guide some newcomers.
TWRP alpha seems to be unable to decrypt or mount the internal storage as writeable if NO rom has been installed before or partitions have been wiped and formated. (with MTP enabled in TWRP your computer will find the phone and internal storage, but it will fail to copy files)
IF a rom has been installed before, it tries to decrypt FBE (file based encryption) with the PIN you chose and then it is possible to load files with MTP to internal storage.
So, if you start from scratch, you have no ROM installed before, or wiped and formatted everything:
you fastboot-load TWRP and end up not being able to upload files (like ROM.zip or TWRP.img) with MTP to the internal storage... how do you select the files for flashing if they aren't available?
1) use external sd card (copy files on ext. sd card, select files from there in twrp)
2) use usb-otg if you have one.
or, and that's my way to go if you don't have a phone with ext.sdcard or usb-otg:
3) use ADB sideload.
in TWRP use ADB sideload to Flash the ROM.zip first (CrDroid/LineageOS). Start the ROM, create a PIN. That way the encryption password is set.
Now start TWRP again with fastboot boot twrp.img (because currently the rom-recovery is default).
this time it asks for user password, enter your pin/pattern and TWRP is finally able to decrypt partitions and use the internal storage. from that point on forward you can copy images with MTP to your phones internal storage.
now in TWRP with MTP enabled, copy twrp.img to internal storage and install the twrp.img as ramdisk. don't hit the reboot (to system) button right there, go back and choose reboot-> reboot to recovery first.
After that it's all done, boot to system. The ROM and TWRP recovery is installed, and TWRP is finally able to decrypt storage and partitions.
on a sidenote:
- TWRP a/b switching indeed isn't working, use fastboot.exe --set-active=a (or b)
- if you flash magisk in twrp, *don't* install TWRP to ramdisk again right after that, just reboot to system, or it gets overwritten again.
the process of installing the actual rom with twrp is not the problem here.
Why do u use twerp, when u work with PC? Just use los recovery & sideload zips.the process of installing the actual rom with twrp is not the problem here.
the problem is to get the rom.zip selectable for installation as the internal storage is not accessable from within twrp and MTP. if you are on the lucky side that twrp and your PC via MTP has access to internal storage right away, then it's great!
it was -never- the case on my side, however.
because TWRP is the more versatile tool, los recovery cannot keep up with it and later on I miss many features of it.
*** Disclaimer I am not responsible for any damage you made to your device You have been warned