Develop Bugs

February 2019 Security Update failure

This morning I've just received the February 2019 security update, I've downloaded it but when the installation starts then it fails. Any idea why this happens?
Somebody has the same issue?
Thanks

Restart, connect charger and start again when above 60%.
Sent from my Mi A2 Lite using Tapatalk

locovibe said:
Restart, connect charger and start again when above 60%.
Click to expand...
Click to collapse
I'm going to try and then I'll let you know.
Thank you very much!

locovibe said:
Restart, connect charger and start again when above 60%.
Sent from my Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
Not work for me. Since January I have this problem.

Xmata said:
Not work for me. Since January I have this problem.
Click to expand...
Click to collapse
You need to reflash whole rom with miflasher and unlock bootloader.

Some people solved the issue by stopping the download, turning on mobile data and resuming download on mobile data. Don't forget to turn off your WiFi. Try this before flashing the stock rom again and losing all your data.

Check the log and reflash touched partitions
konan82 said:
This morning I've just received the February 2019 security update, I've downloaded it but when the installation starts then it fails. Any idea why this happens?
Somebody has the same issue?
Thanks
Click to expand...
Click to collapse
I had the same even after reflashing (fastboot flash boot boot.img) of boot image: I do use Magisk. I checked what is happening during the failing update by
adb logcat -e update_engine
It will report you where and what is failing.
In my case it was complaining on system checksum:
02-20 10:06:56.298 2188 2188 I update_engine: [0220/100656.298722:INFO:delta_performer.cc(386)] Applying 4096 operations to partition "system"
02-20 10:06:56.409 2188 2188 E update_engine: [0220/100656.408950:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
So I reflashed system and the update went on well.
Thus you need a computer with adb and fastboot available and stock image from http://en.miui.com/download-354.html of the same version as currently installed.

yakovpol said:
I had the same even after reflashing (fastboot flash boot boot.img) of boot image: I do use Magisk. I checked what is happening during the failing update by
adb logcat | grep update_engine (under Linux)
It will report you where and what is failing.
In my case it was complaining on system checksum:
02-20 10:06:56.298 2188 2188 I update_engine: [0220/100656.298722:INFO:delta_performer.cc(386)] Applying 4096 operations to partition "system"
02-20 10:06:56.409 2188 2188 E update_engine: [0220/100656.408950:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
So I reflashed system and the update went on well.
Thus you need a computer with adb and fastboot available and stock image from http://en.miui.com/download-354.html of the same version as currently installed.
Click to expand...
Click to collapse
Does this format all data?

wenna.speedy said:
You need to reflash whole rom with miflasher and unlock bootloader.
Click to expand...
Click to collapse
Unlock of bootloader will format all partitions and erase all my data, right?

konan82 said:
Unlock of bootloader will format all partitions and erase all my data, right?
Click to expand...
Click to collapse
reflashing rom lock your bootloader. it will erase your data.
unlocking bootloader via adb erase your data again.

if you have rooted phone you can't use OTA

Finally i have also got feb security update after a long waiting period.

IO13 said:
if you have rooted phone you can't use OTA
Click to expand...
Click to collapse
No my phone isn't rooted. I'm still with locked bootloader

marstonpear said:
Some people solved the issue by stopping the download, turning on mobile data and resuming download on mobile data. Don't forget to turn off your WiFi. Try this before flashing the stock rom again and losing all your data.
Click to expand...
Click to collapse
I've tried to download the entire update without WiFi, using mobile data but nothing to do

IO13 said:
if you have rooted phone you can't use OTA
Click to expand...
Click to collapse
Of course you can,
read this:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
I followed the instructions and updated my phone.
I had no problems

konan82 said:
Does this format all data?
Click to expand...
Click to collapse
Of course, not.
Reflashing of boot or system partition doesn't touch you data partition.
---------- Post added at 07:21 PM ---------- Previous post was at 07:04 PM ----------
wenna.speedy said:
reflashing rom lock your bootloader. it will erase your data.
unlocking bootloader via adb erase your data again.
Click to expand...
Click to collapse
It depends how you reflash. Some scripts provided with the stock ROM do contain bootloader lock command. Some do erase data. The performing actions follow from script names. If you are not sure, open a script and check the commands inside.
In a case you have a problem with the OTA update, it is unlikely connected to your data partition. So no need in reflashing it/reflashing entire phone and loosing your data.
---------- Post added at 07:31 PM ---------- Previous post was at 07:21 PM ----------
konan82 said:
Unlock of bootloader will format all partitions and erase all my data, right?
Click to expand...
Click to collapse
There is a way to unlock bootloader on this phone without loosing data, see https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-unlock-bootloader-erasing-t3878453
You do not have to unlock bootloader if you want to flash stock ROM images.

Something interesting
I've had done something interesting recently. I'm not a "pro" user, just a normal. I couldn't install the February update through OTA, every time the install failed.
I had download from the new dump post the full rom. (Sorry i'm a new user and i can't url posting)
k4sh44 said:
Here is the zip file with all images.
But as i told already, i wasn't able to boot with fastboot command the boot.img i extracted.
Click to expand...
Click to collapse
I have saved all my datas in my phone, then in the pc unzip all the files what i downloaded and installed the new rom with this method in fastboot mode.
HoangP05 said:
These are image files that are extracted from the payload of the android P OTA:
Warning: You will erase all of your data
Code:
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash aboot_a aboot.img
fastboot flash aboot_b aboot.img
fastboot flash sbl1_a sbl1.img
fastboot flash sbl1_b sbl1.img
Run the code and then factory reset in recovery, and you will have android P.
Click to expand...
Click to collapse
After that when my phone first rebooted, the most interesting thing was for me, all of my files and apps were in my phone, anything lost, and everything is working. I don't understand why, the new rom works good, and no need restoring.
Only the magisk wasn't good. With the magisk manager I had made a patched boot img file from the full rom files. Then I booted the new patched boot img with fastboot, and then the magisk is perfect too. (but in magisk everything had to reinstalling)

yakovpol said:
I had the same even after reflashing (fastboot flash boot boot.img) of boot image: I do use Magisk. I checked what is happening during the failing update by
adb logcat | grep update_engine (under Linux)
It will report you where and what is failing.
In my case it was complaining on system checksum:
02-20 10:06:56.298 2188 2188 I update_engine: [0220/100656.298722:INFO:delta_performer.cc(386)] Applying 4096 operations to partition "system"
02-20 10:06:56.409 2188 2188 E update_engine: [0220/100656.408950:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
So I reflashed system and the update went on well.
Thus you need a computer with adb and fastboot available and stock image from http://en.miui.com/download-354.html of the same version as currently installed.
Click to expand...
Click to collapse
Do you think a factory reset (done from the attached image) without flashing the Rom could fix the problem?

I had same problem. Something broke when I used Adaway adblocker.
Unlocking OEM with volume down button didn't work.
And than I downloaded this image http://bigota.d.miui.com/V10.0.3.0....0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz
This is January image.
All other images here are for months before. 10.0.3 is Jan, 10.0.2 is Dec and so on
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Unzipped with 7zip this image
_________________________________________
step 1: install adb and fastboot. ( On windows follow this link https://forum.xda-developers.com/sho....php?t=2588979 )
enable the developer menu on your phone (launch settings, go to system->"about phone" and press repeately on build number)
from the developer options ( launch settings, go to system->"about phone"->developer options ) enable adb and allow bootloader unlock
connect the phone to your PC and give adb permissions to your PC. here I used in cmd
Code:
adb devices
so it would ask for permission from PC
turn off the phone
reboot by pressing power + vol down
_________________________________________
Then with adb in recovery I used:
Code:
fastboot oem unlock
then i repeated step 1, becouse of factory reset with unlocking oem
Code:
fastboot getvar current-slot
if i got A i used A in next string, if B, i used B, where ? is used
Code:
fastboot flash boot_? boot.img
Code:
fastboot flash system_? system.img
Code:
fastboot oem lock
Rebooted phone and
then I updated, and everything worked as it should.

konan82 said:
Do you think a factory reset (done from the attached image) without flashing the Rom could fix the problem?
Click to expand...
Click to collapse
No, it will not: Data partition is not being checked during the update process.
What you can do:
(a) try to find out the reason why the update is failing. It is as simple as starting adb logcat during the update and watching through strings containing update_engine for "error" or "fail" words. Then you will know for sure what is wrong in your phone.
or
(b) reflash your current android version with flash_all_except_storage.bat (if you are under Windows) or flash_all_except_storage.sh (if you are under Linux) script which are part of the whole package http://bigota.d.miui.com/V10.0.3.0....0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz
Most likely you will be able to download and perform the update after this.
or
(c) wait for a few hours: Xiaomi must grant a download link for February 10.0.4.0 version at http://en.miui.com/download-354.html and then do what is in (b) option above with the newer version. You will get updated system right away. Or at your own risk use a dump of this version that someone has already provided (find the link above in the same forum).
Wish you success.

device unable to boot Error - mdtp image is corrupted

Hi there,
I have a problem i was try to root my phone.
Now i dont have access to ADB but only fastboot works.
If i start my phone it goes on fastboot mode, and if i try "fast boot twrp-3.3.0-0-daisy.img" i get the error "device unable to boot Error - mdtp image is corrupted"
Can some one help me out, if tried to download the image again but without success..

You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.

a1291762 said:
You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.
Click to expand...
Click to collapse
Sorry im a little bit noob, but how it works:
flastboot flash a?

fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.

Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
a1291762 said:
fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.
Click to expand...
Click to collapse

mj2o said:
Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
Click to expand...
Click to collapse
No OS installed is maybe cause the last rom that you flashed was not flashed in the right slot or correctly flashed.
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.

SubwayChamp said:
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.
Click to expand...
Click to collapse
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.

mj2o said:
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.
Click to expand...
Click to collapse
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.

I have the same problem, what you have did to fix? please

Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.

mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
hi
same issue here @mj2o: Can you please provide a link to the site in English; it all in Chinese and I cannot read it
Thanks

mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
SubwayChamp said:
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.
Click to expand...
Click to collapse
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.

BenG7 said:
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.
Click to expand...
Click to collapse
Why do you want to flash the bootloader, what is the issue?

Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Device unable to boot. Error - mdtp is corrupted

BenG7 said:
Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Click to expand...
Click to collapse
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread

Thanks SubwayChamp,
Will try as advised and keep you updated.
I m going to look for the fastboot rom for my daisy.

SubwayChamp said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread
Click to expand...
Click to collapse
@SubwayChamp
dit it and when I
Code:
fastboot reboot
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
[EDIT]
realised I can
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
and I can flash the twrp-installer-daisy-3.3.1-0-offain.zip
but if I want to reboot; it says
Code:
No OS installed! Are you sure you wish to reboot?
so I went on with flashing lineageos 16
but at the end of the flash, I get
Code:
Failed to mount '/system' (permission denied)
please advise

BenG7 said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use and
@SubwayChamp
dit it and when I
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
Click to expand...
Click to collapse
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.

SubwayChamp said:
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.
Click to expand...
Click to collapse
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!

BenG7 said:
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!
Click to expand...
Click to collapse
This is exactly what I tried to tell you: your issue concerning to this thread was solved.
Now you have an issue regarding how to flash and boot to system attempting to install LOS. TWRP is perfectly capable to mount/remount or unmount partitions if needed, no need an action from the user, this is not the reason why you are not booting but the method and steps is discussed more properly in the same thread.
From here you can take one of hese three routes:
- To insist with trying to flash LOS.
- Flash other rom or a previous known working rom.
- Return completely to stock by flashing a full global rom.
Just I could recommend that for the future when you flash a stock rom take a backup of the most important partitions (without userdata) this could avoid that you need to use EDL anymore.

fastboot loop

I followed this thread to install lineage OS on my MI A2 lite:
https://www.getdroidtips.com/lineage-os-16-xiaomi-mi-a2-lite/
IIRC, on this phone there is no recovery partition:
fastboot flash recovery twrp.img gives the error Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
I flashed TWRP to boot (fastboot flash boot twrp.img) instead of only starting it (fastboot boot twrp.img)
then I followed the procedure thinking that I was on the recovery partition and tried to install lineage os in boot (where twrp was)
now I can only enter the fastboot mode
fastboot boot twrp.img gives a black screen with device unable to boot error - mdtp image is corrupted
fastboot flash boot twrp.img gives the error Writing 'boot' FAILED (remote: 'partition table doesn't exist')
fastboot getvar current-slot gives current-slot: INVALID
the problem seems to be similar to this one:
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
though mdtp_a and mdtp_b are there but they are not active and I am not sure what image I should flash there.
How should I proceed?

baudoux said:
I followed this thread to install lineage OS on my MI A2 lite:
https://www.getdroidtips.com/lineage-os-16-xiaomi-mi-a2-lite/
IIRC, on this phone there is no recovery partition:
fastboot flash recovery twrp.img gives the error Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
I flashed TWRP to boot (fastboot flash boot twrp.img) instead of only starting it (fastboot boot twrp.img)
then I followed the procedure thinking that I was on the recovery partition and tried to install lineage os in boot (where twrp was)
now I can only enter the fastboot mode
fastboot boot twrp.img gives a black screen with device unable to boot error - mdtp image is corrupted
fastboot flash boot twrp.img gives the error Writing 'boot' FAILED (remote: 'partition table doesn't exist')
fastboot getvar current-slot gives current-slot: INVALID
the problem seems to be similar to this one:
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
though mdtp_a and mdtp_b are there but they are not active and I am not sure what image I should flash there.
How should I proceed?
Click to expand...
Click to collapse
How did you think to flash LineageOs in boot where TWRP used to be?
Anyway if you didn´t complete this disastrous attempt you could solve it restoring mdtp partition that is a kind of gpt for other devices.
Flash it in both slot using fastboot. Then you´ll can know which partition is active, if the system yet still alive you´ll can boot on it or boot temporarily to TWRP to do your stuff but if not then you´ll need to restore one or more partitions flashing again the whole stock rom through MiFlash tool.

SubwayChamp said:
How did you think to flash LineageOs in boot where TWRP used to be?
Click to expand...
Click to collapse
this was a typo, and I got lost in the process
SubwayChamp said:
Flash it in both slots using fastboot.
Click to expand...
Click to collapse
you mean flash LINEAGE OS playload.bin or TWRP.img in mdtp_a and mdtp_b?

baudoux said:
this was a typo, and I got lost in the process
you mean flash LINEAGE OS playload.bin or TWRP.img in mdtp_a and mdtp_b?
Click to expand...
Click to collapse
Sorry for delay, yes, in both partitionn you have to flash mdtp, is to restore the table partition.
And about LOS I think you need to read a bit more or you'll have a thermonuclear reaction some day (just kidding) Custom roms come in form of zip and contain scripts that are prepared for developers to can unpack and flash files in the right place so don't worry about it.
First restore your partitions and the next is a ready-to-go.

SubwayChamp said:
yes, in both partitionn you have to flash mdtp, is to restore the table partition.
First restore your partitions and the next is a ready-to-go.
Click to expand...
Click to collapse
I guess you mean fastboot flash mdtp_a mdtp.img and fastboot flash mdtp_b mdtp.img
I cannot find the mdtp.img file

baudoux said:
I guess you mean fastboot flash mdtp_a mdtp.img and fastboot flash mdtp_b mdtp.img
I cannot find the mdtp.img file
Click to expand...
Click to collapse
You´ll find it inside the stock rom.

SOLVED
flashing mtdp_a and mtdp_b did not help, I hat to flash the stock rom again and start the process from scratch
other problems showed up:
I had to downgrade twrp to 3.3.0 to avoid error 7 while flashing LINEAGE OS
and then upgrade it again to 3.3.1 fo avoid error 64 while flashing GAPPS

Twrp 3.3.1-0 & root [updated] kane/troika

Our old twrp have been great compared to nothing but it isn't exactly fully working and freezes a lot on splash screen.
Thanks to @Stricted and @deadman96385 we now have a more functional twrp.
Support for A/B slots.
ADB working.
No need to flash full firmware. Just flash the vbmeta_patch.img and boot twrp.
!!BOOTLOADER MUST BE UNLOCKED!!
YOUR DATA WILL BE WIPED!!​
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Now that we booted to TWRP it's time to format data.
Go to wipe -> format data -> type yes.
"Permanent" install of TWRP (optional):
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot and go to advanced settings.
Use the option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings so that it won't reboot to recovery instead of system..
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
This must be done every time you update your boot.img.
-------------------------------------------------------------------------------------------------------------------------------------------------------
# ROOT:
-----------
# First time:
# Method 1: Root, forced encryption disabled. Full access to data from twrp:
Flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
# Method 2: Root only. Device still encrypted and won't be able to decrypt / mount data in twrp.
Magisk modules through Magisk manager still works:
Flash only Magisk.
----------------------------------------------------------------------------------------------------
# Fastboot flash update without loosing root or data:
----------------------------------------------------------------------------------------
# Already rooted with encryption disabled:
Extract the firmware zip to your adb/fastboot folder.
You already have the patched vbmeta flashed so just remove the stock vbmeta.img from the folder after extraction to avoid flashing it by mistake.
Flash full firmware without wipe. (Use cmds from below. Save as .bat to make it more simple.)
Boot twrp and then install it, fix recovery bootloop.
Reboot recovery, flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
Boot system.
Code:
echo off
echo - UPDATE AND PRESERV ROOT -
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img
fastboot reboot bootloader
pause 10
fastboot boot twrp-3.3.1-test3.img
echo TWRP is booting..
echo - install recovery ramdisk, fix bootloop, flash magisk & dm-verity zip.
echo - alternatively flash only magisk and Disable_Dm-Verity_ForceEncrypt.zip if you want to keep stock recovery.
pause
# Already rooted with device still encrypted:
Flash firmware update, except vbmeta.
Boot twrp and flash Magisk with adb sideload.
(alternative method: boot twrp and flash magisk patched boot.img)
Download TWRP: https://images.stricted.net/test/troika/twrp-3.3.1-test3.img
Download Magisk: https://github.com/topjohnwu/Magisk/releases
Download vbmeta_patch.img & Disable_Dm-Verity_ForceEncrypt.zip attached below.
PLEASE, DON't QUOTE THE WHOLE OP.

Great guide @tys0n and thank you to @Stricted and @deadman96385 for his work !

tys0n said:
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Click to expand...
Click to collapse
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.

daekdroom said:
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.
Click to expand...
Click to collapse
You're right. You can't switch between encrypted / non encrypted without a reset.
This update method have been working for me with the old twrp as well, but this new build is much better and more stable that I see no reason not to switch to the new one.
Actually, I think it may be better to first fastboot flash the new firmware (except vbmeta) so that you have a "clean" boot.img to start with if you're planning to use the install recovery ramdisk. At least if you have the old one installed already.
That's how I switched and I've had no problems.

Worked to my, Thnx

Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards

gonzo1963 said:
Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards
Click to expand...
Click to collapse
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.

tys0n said:
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
Click to expand...
Click to collapse
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk

gonzo1963 said:
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
Good afternoon,
Any answer?
Regards
Enviado desde mi unknown mediante Tapatalk

Bootloop
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?

"Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop."
Agter this restart the phone in recovery mode and then continue as explained.
Sorry in bad english

First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update

Preceptor said:
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?
Click to expand...
Click to collapse
same here !

sennator said:
First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update
Click to expand...
Click to collapse
Hi. Yes, you're right. After flashing the patched vbmeta we need to format data. I've made it more clear in OP now.
Thanks for pointing it out.
kArLiN_dRaKE_MX said:
same here !
Click to expand...
Click to collapse
Format data in twrp

It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.

It worked.
I performed the process again.
and everything went well.
Thanks to everyone involved. :good:
gambiarraweb1 said:
It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.
Click to expand...
Click to collapse

Just a quick question, when I have TWRP and root I can't pass the SafetyNet check, right?

Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?

simije97 said:
Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?
Click to expand...
Click to collapse
You probably have Data encrypted. You need to execute Format Data in TWRP.

Has anyone used the official TWRP version? I've been thinking of transitioning from the older, unofficial, TWRP to that, but I haven't found any comment about it at all.

Question Qualcom CrashDump Mode After OTA, Magisk Lost Root

I was rooted with Magisk 25.2 fine. I followed the OTA update intructions (uninstall, update, install to the other partition etc). When Magisk rebooted my phone I got a messae that says
QUALCOM CrashDump Mode
-------------------------------
dm-verity device corrupted
verity_ctr
I can reboot back into my other partition, and I have a version of the OS that's pre-OTA, but I've lost root there. I can switch between partitions and go from the Qualcom CrashDump to my working non-rooted OS.
How do I get from either of these places to a rooted version of the OTA update?

I'd suggest waiting for the next OTA and do it again.
However, I don't understand why you did the uninstall, update, install to the other partition etc part. I usually just do the following steps:
Install OTA (do NOT reboot yet)
Install Magisk in the other partition
Reboot
So far it has worked for me for each update.

Ecna said:
I was rooted with Magisk 25.2 fine. I followed the OTA update intructions (uninstall, update, install to the other partition etc). When Magisk rebooted my phone I got a messae that says
QUALCOM CrashDump Mode
-------------------------------
dm-verity device corrupted
verity_ctr
I can reboot back into my other partition, and I have a version of the OS that's pre-OTA, but I've lost root there. I can switch between partitions and go from the Qualcom CrashDump to my working non-rooted OS.
How do I get from either of these places to a rooted version of the OTA update?
Click to expand...
Click to collapse
You may be able to copy your good partitions (a or b, whichever works) to the other one. So they'll both be loaded with working stock firmware. Then take the OTA and drop in a magisk patched boot image after OTA is good

Appreciative said:
You may be able to copy your good partitions (a or b, whichever works) to the other one. So they'll both be loaded with working stock firmware. Then take the OTA and drop in a magisk patched boot image after OTA is good
Click to expand...
Click to collapse
How would I copy my good partition to the broken one?

viktak said:
I'd suggest waiting for the next OTA and do it again.
Click to expand...
Click to collapse
The current OTA is still pending, and I don't have root anymore, so waiting won't get me anywhere.
However, I don't understand why you did the uninstall, update, install to the other partition etc part.
Click to expand...
Click to collapse
I just followed the Magisk instructions here:
https://topjohnwu.github.io/Magisk/ota.html

Ecna said:
How would I copy my good partition to the broken one?
Click to expand...
Click to collapse
While on Slot_A Flash copypartitions.zip??
Sorry for the noob question but how do I do "While on Slot_A Flash copypartitions.zip" I cant find the copypartitions.zip please help thanks
forum.xda-developers.com
[SLOT A/B devices] Universal A/B-cloner
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK Ok, thats over with INFO...
forum.xda-developers.com
Something like these, or manually. Be sure to figure out which partition (a or b) is currently good and working so you don't copy the wrong way. If you do copy the wrong direction, you may have to msm

Appreciative said:
While on Slot_A Flash copypartitions.zip??
Sorry for the noob question but how do I do "While on Slot_A Flash copypartitions.zip" I cant find the copypartitions.zip please help thanks
forum.xda-developers.com
[SLOT A/B devices] Universal A/B-cloner
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK Ok, thats over with INFO...
forum.xda-developers.com
Something like these, or manually. Be sure to figure out which partition (a or b) is currently good and working so you don't copy the wrong way. If you do copy the wrong direction, you may have to msm
Click to expand...
Click to collapse
Thank you, I'll dig into these links!

I got similar problem, solved by disabling dm-verify manually. You can try extract vbmeta.img from rom package using payload_dumper, then use fastboot to disable dm-verify.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

I'm having this same problem, but to fix it I need to switch back to the "good" slot and boot my phone normally to fix it. However after booting my phone into fastboot, I'm unable to run the appropriate command:
Code:
fastboot --set-active=a
fastboot: unknown option -- set-active=a
Do I have the wrong version of fastboot installed on my PC? How can the rest of fastboot work but not this specific command?

sumfahg said:
I'm having this same problem, but to fix it I need to switch back to the "good" slot and boot my phone normally to fix it. However after booting my phone into fastboot, I'm unable to run the appropriate command:
Code:
fastboot --set-active=a
fastboot: unknown option -- set-active=a
Do I have the wrong version of fastboot installed on my PC? How can the rest of fastboot work but not this specific command?
Click to expand...
Click to collapse
Make sure you have the latest full platform tools and not the minimum platform tools, or if you are on a windows PC try the fastboot enhanced version

TheGhost1951 said:
Make sure you have the latest full platform tools and not the minimum platform tools, or if you are on a windows PC try the fastboot enhanced version
Click to expand...
Click to collapse
I am on Windows, where can I download fastboot enhanced?

sumfahg said:
I am on Windows, where can I download fastboot enhanced?
Click to expand...
Click to collapse
There is an xda threads on it. Just search xda forums for fastboot enhanced.

sumfahg said:
I am on Windows, where can I download fastboot enhanced?
Click to expand...
Click to collapse
You could try:
fastboot set_active other
Or
fastboot set_active a
Or
fastboot -a (this is in the documentation but I have never tried it, nor see it online often)

zjhjack123 said:
I got similar problem, solved by disabling dm-verify manually. You can try extract vbmeta.img from rom package using payload_dumper, then use fastboot to disable dm-verify.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Spent some time trying to do this. fastboot said Rewriting, Sending, writing, Finished. All OKAY. No error messages in there. But when I rebooted into the other partition I got the same dm-verity crash dump.

Ecna said:
Spent some time trying to do this. fastboot said Rewriting, Sending, writing, Finished. All OKAY. No error messages in there. But when I rebooted into the other partition I got the same dm-verity crash dump.
Click to expand...
Click to collapse
I dug a bit further and tried these as well:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor_a vbmeta_vendor.img
Whenever I try to boot to the a partition, I just loop back into fastboot mode. The b partition still works though.

Appreciative said:
You could try:
fastboot set_active other
Or
fastboot set_active a
Or
fastboot -a (this is in the documentation but I have never tried it, nor see it online often)
Click to expand...
Click to collapse
Fastboot --set-active=a or b which ever you need in bootloader mode

Ecna said:
I dug a bit further and tried these as well:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor_a vbmeta_vendor.img
Whenever I try to boot to the a partition, I just loop back into fastboot mode. The b partition still works though.
Click to expand...
Click to collapse
Maybe you could try set-active a (if a slot is the bad rom) first, reboot into fastboot again and then use fastboot to flash vbmeta with disable verity parameter.
Or you could try to boot into good rom, and flash full update package using local update instead of ota, then see if it can boot into updated rom.

zjhjack123 said:
Maybe you could try set-active a (if a slot is the bad rom) first, reboot into fastboot again and then use fastboot to flash vbmeta with disable verity parameter.
Or you could try to boot into good rom, and flash full update package using local update instead of ota, then see if it can boot into updated rom.
Click to expand...
Click to collapse
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?

Ecna said:
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?
Click to expand...
Click to collapse
When you flash tom in the system, it only update the firmware in another slot. So if your current good rom is in slot b, you can just boot into slot b and apply system update via local update, the updated rom will be in slot a.

Ecna said:
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?
Click to expand...
Click to collapse
If you have the images:
fastboot flash system_a system_a.img
fastboot flash system_b system_b.img
it's also possible to pull the whole partitions down with msm tool (press f8, select partitions and readback, files go to c:\) or using dd.
If not, #19 above