Develop Bugs

January OTA won't Sideload--Strange Error

I have my Pixel 2 XL currently running on the December update (8.1) and Magisk installed, stock recovery. Downloaded the January OTA file (multiple times, actually) and when I run the command to Sideload the OTA zip in Stock Recovery, I get the following error messages:
Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does not match framework matrix 1.0 Installation aborted.
Click to expand...
Click to collapse
Never seen that before and Google/XDA search came up empty or bad results. I also tried to update my adb/tools using Android Studio, still no dice.

The error provided seems to point to Magisk's modification to the dtbo to disable AVB 2.0/dm-verity.
Might have to reflash stock dtbo.img. Or just flash full factory image with the -w flaf removed from the flash-all.bat.

ilal2ielli said:
The error provided seems to point to Magisk's modification to the dtbo to disable AVB 2.0/dm-verity.
Might have to reflash stock dtbo.img. Or just flash full factory image with the -w flaf removed from the flash-all.bat.
Click to expand...
Click to collapse
Yep... that's where I'm at, looking to install the full image with -w omitted. I've even tried to uninstall Magisk (full removal) without luck.

WorldOfJohnboy said:
Yep... that's where I'm at, looking to install the full image with -w omitted. I've even tried to uninstall Magisk (full removal) without luck.
Click to expand...
Click to collapse
Might be able to try restoring images option in Magisk Manager too before installing full image.
I just install the full images each update though, less problems that way.

OK, so I fixed it by going back to stock (December) Boot and DTBO images, then Sideloaded the OTA which worked fine. Worst case, I'll flash the full System without wipe if I have issues. So it looks as if @ilal2ielli was right! Also, credit to THIS post by @sn0warmy for the steps.

Yep, I had the same issue last night and couldn't find anything on Google. Drove me crazy for a good 30 minutes! Then I recalled that you have to be 100% stock to take updates so I flashed stock boot.img and it took the update just fine afterwards. I did not need to flash dtbo.img.

I'm all flashed, but having issues with the Magisk Patched Boot image. Flashed stock back in since it would only boot to recovery or bootloader. I may revert to booting to TWRP and flashing the Magisk that way.

I uninstalled Magisk using the Magisk app and reflashed the stock boot image but I am still getting the January
update installation error. Do I need to use the Magisk-uninstaller zip file?

seckelg said:
I uninstalled Magisk using the Magisk app and reflashed the stock boot image but I am still getting the January
update installation error. Do I need to use the Magisk-uninstaller zip file?
Click to expand...
Click to collapse
Did you flash the December stock boot.img? You may also want to try flashing the December dtbo.img. I did both and my issues are resolved.

WorldOfJohnboy said:
Did you flash the December stock boot.img? You may also want to try flashing the December dtbo.img. I did both and my issues are resolved.
Click to expand...
Click to collapse
Yes, I flashed the boot.img from taimen-opm1.171019.011 and I just did the same with the dtbo.img. Unfortunately the update still won't take. Thanks for the reply though.

seckelg said:
Yes, I flashed the boot.img from taimen-opm1.171019.011 and I just did the same with the dtbo.img. Unfortunately the update still won't take. Thanks for the reply though.
Click to expand...
Click to collapse
Then flash the full image minus the -w from fastboot.

v12xke said:
Then flash the full image minus the -w from fastboot.
Click to expand...
Click to collapse
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 1.069s]
writing 'bootloader'...
FAILED (remote: Flashing is not allowed for Critical Partitions)
finished. total time: 1.084s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.769s]
writing 'radio'...
OKAY [ 0.588s]
finished. total time: 2.365s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
error: update package missing boot.img
Press any key to exit...

fastracer said:
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 1.069s]
writing 'bootloader'...
FAILED (remote: Flashing is not allowed for Critical Partitions)
finished. total time: 1.084s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.769s]
writing 'radio'...
OKAY [ 0.588s]
finished. total time: 2.365s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
error: update package missing boot.img
Press any key to exit...
Click to expand...
Click to collapse
Looks like you didn't unlock your critical partition, which is preventing the factory image from flashing the bootloader. Google blocks boot.img flashes if the bootloader isn't the most updated or the one that matches the boot.img.
You'll need to fastboot unlock_critical, which will wipe your phone and data currently stored on it to progress any further.

fastracer said:
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
Click to expand...
Click to collapse
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:

ilal2ielli said:
Looks like you didn't unlock your critical partition, which is preventing the factory image from flashing the bootloader. Google blocks boot.img flashes if the bootloader isn't the most updated or the one that matches the boot.img.
You'll need to fastboot unlock_critical, which will wipe your phone and data currently stored on it to progress any further.
Click to expand...
Click to collapse
v12xke said:
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:
Click to expand...
Click to collapse
Thanks guys! I'm sure I critical unlocked it BUT I did mess around with so much stuff since this happened I probably did something I wasn't supposed to I'm gonna redo the crictical unlock and start over...thanks again!

v12xke said:
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:
Click to expand...
Click to collapse
Hi. I went through and relocked and then unlocked both the standard "unlock" and the "critical unlock". Then I tried to flash the Feburary image but was met with a "device is corrupt message" that looked like the bootloader warning message except the yellow triangle was red. The sideloading the OTA also gives an error:
E: Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does no match framework matrix 1.0
Installation aborted.
Do you have any idea how I could fix this?
Thanks in advance

km00000 said:
Hi. I went through and relocked and then unlocked both the standard "unlock" and the "critical unlock". Then I tried to flash the Feburary image but was met with a "device is corrupt message" that looked like the bootloader warning message except the yellow triangle was red. The sideloading the OTA also gives an error:
E: Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does no match framework matrix 1.0
Installation aborted.
Do you have any idea how I could fix this?
Thanks in advance
Click to expand...
Click to collapse
Use the most recent adb from the Google factory image page. Also don't use an edited flash-all.bat.

ilal2ielli said:
Use the most recent adb from the Google factory image page. Also don't use an edited flash-all.bat.
Click to expand...
Click to collapse
I've been using the most recent adb (version 1.0.36). Only thing I can think of is that I somehow I added an older version to my PATH so that I could use it from any folder and now Windows keeps using the older version. Is that the latest version?

km00000 said:
I've been using the most recent adb (version 1.0.36). Only thing I can think of is that I somehow I added an older version to my PATH so that I could use it from any folder and now Windows keeps using the older version. Is that the latest version?
Click to expand...
Click to collapse
You arent' running the lastest version of the binaries due to your current path statement. ADB version now is 10.3.9. You should delete all versions off your PC. Edit your path statement with a single ADB folder (C:\ADB\) . Now add this folder to PATH. Go HERE and download the latest version binaries -27.0.1 (December 2017). Unzip the entire zip file into the C:\ADB folder. Reboot. As a test, open a command window and type path and C:\ADB should be there. Make sure your connection to phone in BOOTLOADER MODE is good by typing "fastboot devices" and you should immediately get your serial number back. Now unzip the entire contents of the full Google image (Not OTA) into your ADB folder. Do not further unzip the nested update.zip. Leave that alone. At this point either type flash-all.bat or double click on the batch file to initiate the script.

v12xke said:
You arent' running the lastest version of the binaries due to your current path statement. ADB version now is 10.3.9. You should delete all versions off your PC. Edit your path statement with a single ADB folder (C:\ADB\) . Now add this folder to PATH. Go HERE and download the latest version binaries -27.0.1 (December 2017). Unzip the entire zip file into the C:\ADB folder. Reboot. As a test, open a command window and type path and C:\ADB should be there. Make sure your connection to phone in BOOTLOADER MODE is good by typing "fastboot devices" and you should immediately get your serial number back. Now unzip the entire contents of the full Google image (Not OTA) into your ADB folder. Do not further unzip the nested update.zip. Leave that alone. At this point either type flash-all.bat or double click on the batch file to initiate the script.
Click to expand...
Click to collapse
I was able to force it to go to the adb I downloaded and got it installed. I actually just changed the flash-all.bat script to use the correct adb version by point it to the freshly downloaded platform-tools. I'm not sure where this old ADB is located. It's not in my PATH when I look at environment variables. I don't have any other ADB or platform-tools downloaded, that I know off.
Anyway I got it to work and I'll just make sure to point it to the correct platform-tools whenever I flash something in the future. Can't believe I've been on the developer preview 2 since like November.

Update Pie (December)

Hi all!
I installed PIE using the VPN method in the beginning of the month. Now, the update (about 90mb) was released but I'm getting an error message.
I tried several networks, WiFi or cellular but the error persists.
Does any one has an idea on what I can do? I don't have a working windows computer unfortunately.
Regards!

How on earth did you turn on the battery % in the status bar?? I'm also on pie, december update went without errors,

Gregor250385 said:
How on earth did you turn on the battery % in the status bar??
Click to expand...
Click to collapse
asking the real questions!

Gregor250385 said:
How on earth did you turn on the battery % in the status bar?? I'm also on pie, december update went without errors,
Click to expand...
Click to collapse
You can use: https://play.google.com/store/apps/details?id=com.bryancandi.android.uituner
This is what I used and is working without issues.
I'm just not able to update to the lastest version rolled out today. Damn it!

well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .

TheAwesomeRB1 said:
well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .
Click to expand...
Click to collapse
Thanks for that input.
However, one question. Will this work on a MacBook? My windows computer is simply not working at all. I don't have any other computer at the moment.

senntennce said:
Thanks for that input.
However, one question. Will this work on a MacBook? My windows computer is simply not working at all. I don't have any other computer at the moment.
Click to expand...
Click to collapse
Well you can try to use vmware workstation and emulate windows, theoretically it would work but dont forget to install the drivers otherwise it wont be recognized.
Edit : platform tools exists also for mac os.

reboot and try to update again, do this a few times. mine did this but a reboot or two and it fixed itself, dont know if its the same issue though

DrEzkimo said:
reboot and try to update again, do this a few times. mine did this but a reboot or two and it fixed itself, dont know if its the same issue though
Click to expand...
Click to collapse
I tried that for the day... Like 20 times already and still nothing.
I will give a few more tries.
Thanks!

senntennce said:
I tried that for the day... Like 20 times already and still nothing.
I will give a few more tries.
Thanks!
Click to expand...
Click to collapse
Just do what i told it will be fine, as i said there is a version of platform tools for mac os, if you need further help i ll be here.

TheAwesomeRB1 said:
well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .
Click to expand...
Click to collapse
There's literally no reason to revert back to Oreo. OP just need to flash boot and system images from his current version in both slots before updating.

Does this version have the bug as vpn version? For example flash of screen (normale/black)?

croccio said:
Does this version have the bug as vpn version? For example flash of screen (normale/black)?
Click to expand...
Click to collapse
Nope, works perfectly, 0 bugs.

i have problems with wifi
can't connect to any of my saved wifi
tried to reset wifi twice, but it doesn't work

Hakkinan said:
There's literally no reason to revert back to Oreo. OP just need to flash boot and system images from his current version in both slots before updating.
Click to expand...
Click to collapse
I'm currently downloading those files.
The commands that I need will be:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
Correct?
Thanks

Well, for my case i would rather remove everey thing and start from scratch for a fresh start with only One command and zero risk, if you get the same result with fastbooting go ahead.

TheAwesomeRB1 said:
well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .
Click to expand...
Click to collapse
XIaomi specifically warns you about NOT reverting to Oreo once you are on Pie.

After doing some research, found that using a macbook, we should change the codes to:
./fastboot flash boot_a boot.img
./fastboot flash boot_b boot.img
./fastboot flash system_a system.img
./fastboot flash system_b system.img
But after doing:
./fastboot flash system_a system.img
I got this error message:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/4 (522236 KB)...
OKAY [ 18.147s]
writing 'system_a' 1/4...
FAILED (remote: Partition flashing is not allowed)
Tried every code but the message is always the same: FAILED (remote: Partition flashing is not allowed)
I enabled OEM Unlocking in Developer Options and debugging.
What I'm I missing?
Edit: Yeah, after reading some more, it seems that it is required to have the boot loader unlocked and I don't have it. Bummer.

senntennce said:
After doing some research, found that using a macbook, we should change the codes to:
./fastboot flash boot_a boot.img
./fastboot flash boot_b boot.img
./fastboot flash system_a system.img
./fastboot flash system_b system.img
But after doing:
./fastboot flash system_a system.img
I got this error message:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/4 (522236 KB)...
OKAY [ 18.147s]
writing 'system_a' 1/4...
FAILED (remote: Partition flashing is not allowed)
Tried every code but the message is always the same: FAILED (remote: Partition flashing is not allowed)
I enabled OEM Unlocking in Developer Options and debugging.
What I'm I missing?
Click to expand...
Click to collapse
I'm not sure about MacOS (since i don't have one) but in Windows/Linux this happens when you use an older version of fastboot.

senntennce said:
After doing some research, found that using a macbook, we should change the codes to:
./fastboot flash boot_a boot.img
./fastboot flash boot_b boot.img
./fastboot flash system_a system.img
./fastboot flash system_b system.img
But after doing:
./fastboot flash system_a system.img
I got this error message:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/4 (522236 KB)...
OKAY [ 18.147s]
writing 'system_a' 1/4...
FAILED (remote: Partition flashing is not allowed)
Tried every code but the message is always the same: FAILED (remote: Partition flashing is not allowed)
I enabled OEM Unlocking in Developer Options and debugging.
What I'm I missing?
Click to expand...
Click to collapse
Since your windows is down, can you try it on a virtual machine (vmware workstation) ?

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.

Rooting Motorola One Action w/ Android 10

I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.

[email protected] said:
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
Click to expand...
Click to collapse
Hi!!
I have a model XT2013-1. I was having the same problem as you, so I updated TROIKA-RETBR on 02/22/2020.
After updating, I did the procedure of this link "https://forum.xda-developers.com/one-action/how-to/twrp-magisk-root-motorola-one-action-t3975883", skipping the step "8.2- Now tap on Wipe> Format Data> Type Yes and go back to the home screen again. " This step gave me the looping error.
Now root works perfect !!

Thank you very much. I will try it.

BL1ND4D0 said:
Hi!!
I have a model XT2013-1. I was having the same problem as you, so I updated TROIKA-RETBR on 02/22/2020.
After updating, I did the procedure of this link "https://forum.xda-developers.com/one-action/how-to/twrp-magisk-root-motorola-one-action-t3975883", skipping the step "8.2- Now tap on Wipe> Format Data> Type Yes and go back to the home screen again. " This step gave me the looping error.
Now root works perfect !!
Click to expand...
Click to collapse
I am still getting the following error message. I have no idea why. Would you please help me what to do? Thank you very much.
fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (37524 KB) OKAY [ 1.209s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed

[email protected] said:
I am still getting the following error message. I have no idea why. Would you please help me what to do? Thank you very much.
fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (37524 KB) OKAY [ 1.209s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
It's A/B device so it doesn't have dedicated recovery partition. It's inside boot.img.
Use fastboot boot twrp.img
Once booted to twrp, you can use the twrp installer zip to flash twrp recovery ramdisk to your boot.img for permanent installation.

tys0n said:
It's A/B device so it doesn't have dedicated recovery partition. It's inside boot.img.
Use fastboot boot twrp.img
Once booted to twrp, you can use the twrp installer zip to flash twrp recovery ramdisk to your boot.img for permanent installation.
Click to expand...
Click to collapse
Thank you very much for your help. I tried but I was still getting the following error message.
fastboot boot twrp.img
Sending 'boot.img' (37524 KB) OKAY [ 0.990s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Would you tell me what to do?

[email protected] said:
Thank you very much for your help. I tried but I was still getting the following error message.
fastboot boot twrp.img
Sending 'boot.img' (37524 KB) OKAY [ 0.990s]
Booting FAILED (remote: '')
fastboot: error: Command failed
Would you tell me what to do?
Click to expand...
Click to collapse
Did you follow all instructions from twrp thread. like flashing modified vbmeta and wipe data before booting twrp?
Also take a look at the original thread for one vision as it has a newer zip that contains only one modified vbmeta.img instead of two different ones in the older zip that is posted in one action's twrp thread.

I rooted using fastboot, I could never get into TWRP to flash anything.
In fastboot, I flashed the modified vbmeta.img, then flashed the magisk patched boot img file (I created this with magisk), then flashed the patched vbmeta.img file, then did a fastboot wipe.
Rebooted, set up the phone, installed magisk manager and opened, it needed to update some files. Rebooted, and the device was rooted.

goofball2k said:
I rooted using fastboot, I could never get into TWRP to flash anything.
In fastboot, I flashed the modified vbmeta.img, then flashed the magisk patched boot img file (I created this with magisk), then flashed the patched vbmeta.img file, then did a fastboot wipe.
Rebooted, set up the phone, installed magisk manager and opened, it needed to update some files. Rebooted, and the device was rooted.
Click to expand...
Click to collapse
Thank you very much for your input. You must be an expert! WOW! Sorry I am not that expert........ Would you mind explaining (1) how to modify vbmeta.img and (2) how to patch boot.img? It is very impressive to read what you have done, but sorry I am still a beginner. Also, when I flash, "fastboot flash (File Name)" ok?
Thank yuo very much for your help.

[email protected] said:
Thank you very much for your input. You must be an expert! WOW! Sorry I am not that expert........ Would you mind explaining (1) how to modify vbmeta.img and (2) how to patch boot.img? It is very impressive to read what you have done, but sorry I am still a beginner. Also, when I flash, "fastboot flash (File Name)" ok?
Thank yuo very much for your help.
Click to expand...
Click to collapse
You don't need to modify vbmeta.img. I am using the older version of the root Moto Vision package, which has a vbmeta.img file, and a patched vbmeta.img file.
For the modified boot img, I downloaded the full image from https://mirrors.lolinet.com/firmware/moto/troika/official/
Extract, and then take the boot.img file, you will want that saved to a phone that has Magisk installed.
Follow these instructions to patch
https://www.ytechb.com/how-to-patch-a-file-in-magisk-manager/
Once you have that, you will want that patched file into the fastboot directory on your computer. You will also want the vbmeta and the patched vbmeta img files (from the root moto vision package) in this directory. I have not used the updated version, I am using the older. I don't know about using the newer package which only has 1 vbmeta file.
Put your phone into fastboot mode.
Flash the vbmeta.img file, then the magisk patched boot file, then the vbmeta patched file. Then do a fastboot wipe of the phone.
Reboot the phone.
Set it up again, install magisk manager, then open it, and it should ask to configure. Let it do that, it should reboot and after that, you should be rooted.

[email protected] said:
I have Motorola One Action w/ Android 10 running. I need to root this phone to recover the data. However, when following the instruction, I received the following error message.
C:\adb>fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
downloading 'boot.img'...
OKAY [ 1.118s]
booting...
FAILED (remote failure)
finished. total time: 1.305s
Can anyone help me what to do?
Thank you very much for your help.
Click to expand...
Click to collapse
I guess goofball2k detailed reply might have helped by now. On the other hand, I'm just curious to know that the next time you or anyone else for that matter face the same issue, please flash the stock firmware (using any of the Android 10 tools from here ) at that instance, then again start the same process and let me know whether you succeed or not (you will still have to execute the fastboot boot twrp command around 4-8 times, but during all these attempts, you should now get the success message, and after x number of attempts, you should succeed). So in short, if flashing the stock firmware after that error helps you out, do let me know

Thank you
binary**# said:
I guess goofball2k detailed reply might have helped by now. On the other hand, I'm just curious to know that the next time you or anyone else for that matter face the same issue, please flash the stock firmware (using any of the Android 10 tools from here ) at that instance, then again start the same process and let me know whether you succeed or not (you will still have to execute the fastboot boot twrp command around 4-8 times, but during all these attempts, you should now get the success message, and after x number of attempts, you should succeed). So in short, if flashing the stock firmware after that error helps you out, do let me know
Click to expand...
Click to collapse
Thank you very much for your input.

How are you!!
It doesn't leave me at all ... everything I want to flash throws the same error:
C:\platform-tools>fastboot boot vbmeta.img
creating boot image...
creating boot image - 6144 bytes
downloading 'boot.img'...
OKAY [ 0.013s]
booting...
FAILED (remote failure)
finished. total time: 0.184s
What can be?

Polnareff said:
How are you!!
It doesn't leave me at all ... everything I want to flash throws the same error:
C:\platform-tools>fastboot boot vbmeta.img
creating boot image...
creating boot image - 6144 bytes
downloading 'boot.img'...
OKAY [ 0.013s]
booting...
FAILED (remote failure)
finished. total time: 0.184s
What can be?
Click to expand...
Click to collapse
You aren't flashing, your command is trying to boot from vbmeta.img. You are missing the flashing command.

Question OP9P stuck in fastboot mode, no OS or recovery Help!

I am new to flashing custom roms, and I got lineage running but I wanted to try Evo X, when I tried flashing through lineage Recovery it booted back into lineage, ok, so I erased all datat through lineage recovery and installed TWRP. I got that on but within a few clicks of messing around I found myself with no recovery or OS and im only stuck in fastboot, I have no idea how to get out of it. mods take this post down if posted in the wrong community. I just though this would be the best place to post it. I am new to XDA, I have these ADB logs from the command I was trying to run
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot boot C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools\TWRP-3.5.1-lemonadep-Nebrassy-2.img
Sending 'boot.img' (196608 KB) OKAY [ 4.500s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
I have no idea why it keep failing, I would greatly appreciate any help to get my phone working again.

Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.

oddlyspaced said:
Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.
Click to expand...
Click to collapse
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery

eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery
Click to expand...
Click to collapse
I guess you should try msm tool then

Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.

RazOne said:
Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.
Click to expand...
Click to collapse
I have gotten msm tool and my firmware, but nothing is showing up in msm when my device is connected
ive linked a screenshot of what my msm tool looks like, im just so desperate to get my phone back

Power off phone, position mouse cursor o er start button on msm tool, hold down vol up and down simultaneously, plug phone into computer wait a quick second and press start. That should work.

eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
Click to expand...
Click to collapse
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps

IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
I LITERALLY CANNOT THANK YOU ENOUGH, YOU ARE LIKE THE DAD I NEVER HAD.

Lol, i'm not that old found the answer myself in a forum after 2 days of being stuck in fastboot.

IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
hello guys i am facing that same issue but my own show slot_b and then i try to use your step but still not work help me plizzz

Googled the error you have. Check this post (and following ones)
[SOLVED] - Bootloop with completely new OPO9pro after oem unlock
Hello, just received the phone (EU), updated latest online udpate. (no Google account etc added, just fast setup) Enabled developer options, OEM unlocking and USB debugging. After update, 1*reboot. then another reboot to bootloader, and executed...
forum.xda-developers.com
I think you should start over and use "fastboot flashing unlock" instead of fastboot oem unlock.
Follow the link in that thread. Droidwin has the best tutorials for oneplus you'll find. Never had this error myself, so can't say for sure what to do.