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.

Moto Z2 force constantly bootlooping, Stock rom load but NO Wi-FI or Cellular network

I have struggled to fix my bootlooping problem , After install LOS rom/ other rom and flashing the Magisk. Everything installed fine, but for some reason, after restarting the system it will get to LOS loading screen and bootloop. I attempted to install a stock rom on it, but that load fine but it WIFI and Cellular Network doesn't work. The boot loader has been unlocked Any detail instruction will be highly appreciated. Thanks
Background info, I have spent more than 1 years using this awesome phone with Lineage OS 15.1 , I wake up one morning with the constantly boot looping. I have the T-Mobile version with the bootloader unlocked. I have also spent weeks going through and following other threads but haven't been able to resolved my issue.

sammd301 said:
I have struggled to fix my bootlooping problem , After install LOS rom/ other rom and flashing the Magisk. Everything installed fine, but for some reason, after restarting the system it will get to LOS loading screen and bootloop. I attempted to install a stock rom on it, but that load fine but it WIFI and Cellular Network doesn't work. The boot loader has been unlocked Any detail instruction will be highly appreciated. Thanks
Background info, I have spent more than 1 years using this awesome phone with Lineage OS 15.1 , I wake up one morning with the constantly boot looping. I have the T-Mobile version with the bootloader unlocked. I have also spent weeks going through and following other threads but haven't been able to resolved my issue.
Click to expand...
Click to collapse
Whenever you move from custom to stock and vice versa you should format user data. Easiest way is in bootloader mode, issue the command 'fastboot -w' w/o quotes.

41rw4lk said:
Whenever you move from custom to stock and vice versa you should format user data. Easiest way is in bootloader mode, issue the command 'fastboot -w' w/o quotes.
Click to expand...
Click to collapse
I applied the "fastboot -w" below is the output I got; Still no WIFI and Cellular network not working
-------------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
-------------------------------------------------

sammd301 said:
I applied the "fastboot -w" below is the output I got; Still no WIFI and Cellular network not working
-------------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
-------------------------------------------------
Click to expand...
Click to collapse
Do you have an imei number still? Is the bootloader still unlocked? Have you tried following the return to stock thread and doing a clean install of the latest TMO firmware?

41rw4lk said:
Do you have an imei number still? Is the bootloader still unlocked? Have you tried following the return to stock thread and doing a clean install of the latest TMO firmware?
Click to expand...
Click to collapse
The IMEI number is “Unknown” , Yes the bootloader is Unlocked because, I am able to flash TWRP image on the phone. Yes I spent close to a week following the return to stock thread, the first time I did it, the Cellular network come on about 30 minutes after the phone completed loading to the home screen. Thanks for the guidance

You need to blankflash, then flash the latest TMO firmware for your phone. Usually you lose baseband when you flash the wrong firmware, does it say XT1789-04 by the usb port?

sammd301 said:
The IMEI number is “Unknown” , Yes the bootloader is Unlocked because, I am able to flash TWRP image on the phone. Yes I spent close to a week following the return to stock thread, the first time I did it, the Cellular network come on about 30 minutes after the phone completed loading to the home screen. Thanks for the guidance
Click to expand...
Click to collapse
I would go through the unlock process again. Your bootloader shows flashing_locked

Uzephi said:
I would go through the unlock process again. Your bootloader shows flashing_locked
Click to expand...
Click to collapse
I follow the procedure to unlocked the bootloader again, it now shows "flashing_unlocked" as show in the photo below; I flashed another oem rom but still no wifi and network and Still Baseband /Baseline is < not found>

sammd301 said:
I follow the procedure to unlocked the bootloader again, it now shows "flashing_unlocked" as show in the photo below; I flashed another oem rom but still no wifi and network and Still Baseband /Baseline is < not found>
Click to expand...
Click to collapse
Can you link the flash all you used and how you flashed it?

Uzephi said:
Can you link the flash all you used and how you flashed it?
Click to expand...
Click to collapse
I have been following this tread on xda [ https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 ]
Below is the steps
How to fix your phone:
Download the Utilities zip Link to the flash all https://www.androidfilehost.com/?fid=5862345805528053597
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!

sammd301 said:
I have been following this tread on xda [ https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 ]
Below is the steps
How to fix your phone:
Download the Utilities zip Link to the flash all https://www.androidfilehost.com/?fid=5862345805528053597
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
Click to expand...
Click to collapse
What zip did you use?
Edit: that thread uses AFH which has an older version bootloader than in your picture so something isn't going right. How long does it take to flash?
Edit 2: does your phone reboot after running the .bat file?

I used the T-Mobile Flash All zip the link was to google drive https://drive.google.com/file/d/1Bo_ry_38J6BHy4-A4fuhAnv94C5yV1TW/edit

sammd301 said:
I used the T-Mobile Flash All zip the link was to google drive https://drive.google.com/file/d/1Bo_ry_38J6BHy4-A4fuhAnv94C5yV1TW/edit
Click to expand...
Click to collapse
Yeah, that one is old. Try https://androidfilehost.com/?fid=11410963190603877456 just like the guide states, it should open command prompt and you should see it flashing. The process can take s minute or two. If it immediately closes within 30 seconds or hangs, it didn't flash

Uzephi said:
What zip did you use?
Edit: that thread uses AFH which has an older version bootloader than in your picture so something isn't going right. How long does it take to flash?
Edit 2: does your phone reboot after running the .bat file?[/QUOTE
Yes the phone does reboot by itself after running the .bat file, But it reboot back to bootloader screen.
Click to expand...
Click to collapse

Uzephi said:
Yeah, that one is old. Try https://androidfilehost.com/?fid=11410963190603877456 just like the guide states, it should open command prompt and you should see it flashing. The process can take s minute or two. If it immediately closes within 30 seconds or hangs, it didn't flash
Click to expand...
Click to collapse
I download the suggested rom [ https://androidfilehost.com/?fid=11410963190603877456 ] and flashed it to my phone running flashall.bat via Windows PowerShell,
It took approximately 6 minutes for the flashing to be complete, but with some minor error, Afterword the phone reboot back to the bootloader screen. After starting it still doesn't show the IMEI number and No cellular network or WIFI available.
The output of the flashing process is below along with the attach screenshot of the error;
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.803s]
finished. total time: 0.807s

sammd301 said:
I download the suggested rom [ https://androidfilehost.com/?fid=11410963190603877456 ] and flashed it to my phone running flashall.bat via Windows PowerShell,
It took approximately 6 minutes for the flashing to be complete, but with some minor error, Afterword the phone reboot back to the bootloader screen. After starting it still doesn't show the IMEI number and No cellular network or WIFI available.
The output of the flashing process is below along with the attach screenshot of the error;
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.803s]
finished. total time: 0.807s
Click to expand...
Click to collapse
Flash again, after it is done, type fastboot --set-active=other and then run it one last time. Then boot your phone.

Uzephi said:
Flash again, after it is done, type fastboot --set-active=other and then run it one last time. Then boot your phone.
Click to expand...
Click to collapse
After flashing the rom again, and getting the error " Erase successful, but not automatically formatting..." I input the fastboot command "fastboot --set-active=other" and I got back "unknown option -- set-active=other" as show in the image below. Was the syntax right?
I have been googling the errors I have received like "Erase successful, but not automatically formatting.
File system type raw not supported" to see if I can land on page that can help resolve the issue with the phone.

I have downloaded the latest adb and fastboot platform tools versions, after running the flashall.bat file, I still got the same error at the end. I follow up with the "fastboot --set-active=other" command and this time I got [ Setting current slot to '`' FAILED (remote: '') ] as show in the image below.

sammd301 said:
I have downloaded the latest adb and fastboot platform tools versions, after running the flashall.bat file, I still got the same error at the end. I follow up with the "fastboot --set-active=other" command and this time I got [ Setting current slot to '`' FAILED (remote: '') ] as show in the image below.
Click to expand...
Click to collapse
Seems it isn't recognizing other then, which it should. Do =_b then to see if you can swap to slot B

Uzephi said:
Seems it isn't recognizing other then, which it should. Do =_b then to see if you can swap to slot B
Click to expand...
Click to collapse
After inputting the command [ fastboot --set-active=_b ] the output I got back was [ Slot _b does not exist. supported slots are:
a
b ]
I proceed to input [ fastboot --set-active=b ] the output was [ Setting current slot to 'b' ]
So I the flashing again and input the [ fastboot --set-active=b ] again and got back [ Setting current slot to 'b' ]
I pressed the power button to start the phone from bootloader menu , the phone boot-loop with the Motorola logo as show, after 6 to 8 cycling of the boot looping with the Motorola logo the phone bootup again with T-Mobile logo. When it got home screen, I saw again that Network and cellular still not working and No IMEI number too.

Help with root for Alldocube M5X Pro

I am in over my head once more and could use help from someone more experienced.
The problem?
I bought an Alldocube M5X Pro tablet for my kids. First thing I did was root it using Magisk. I found the stock ROM, extracted the boot.img file, patched it with magisk manager, unlocked the bootloader and then used the fastboot command to flash the modified boot.img. Smooth sailing, worked flawlessly, kids were happy. 2 kids, 1 tablet, the happiness didn't last too long. They both wanted to use the tablet all the time. So when I found a sales promotion for the same model tablet, I decided to buy one more. Tablet #2 arrives, also an Alldocube M5X Pro, model T1006, Kernel version 3.18.60, Android version 8.0.0, same as tablet #1. I go through the same steps, but when I try to flash the modified boot.img file on the new tablet, it tells me Remote: Flash WRITE failure.
Here's what I did, step by step:
1. I verified that the 2nd tablet had the same build number as the 1st tablet. It did: T1006_V1.01_20200504
2. I enabled USB debugging in developer options and set the OEM Unlock option to ON
3. I trusted the connected computer in order to use the adb commands
4. I rebooted to the bootloader and executed the command Fastboot OEM unlock
C:\adb>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 7.825s]
finished. total time: 7.826s
Click to expand...
Click to collapse
5. I executed the command Fastboot Flash boot magisk_patched.img with the img file in the path from where I'm running the command
C:\adb>fastboot flash boot magisk_patched.img
target reported max download size of 134217728 bytes
sending 'boot' (10253 KB)...
OKAY [ 0.468s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.633s
Click to expand...
Click to collapse
6. I've tried erasing the cache and user data partitions from the stock recovery and repeating step 5, but received the same error.
And that's where I'm stuck. The tablet can reboot from there, will detect tampering and proceed to run an erase command and starts with the Android Setup tutorial.
Just for the hell of it I tried flashing the stock ROM using the SP Flash tool for Mediatek devices, which works just fine. I then tried tried flashing an older build (0304) but still received the same error when trying to flash the boot.img
I also tried flashing a custom recovery as well as booting a recovery.img but in both cases the tablet ends up booting normally, I assume because the custom recovery isn't compatible with this device.
Everything I find online about flash write failure errors seems to indicate a defective emmc however most of those are specific to the Nexus 5 phone. The difference here seems to be that I can unlock the bootloader just fine, it stays unlocked as far as I can tell and I can overwrite with a new ROM, so I'm thinking the emmc is fine.
I'm just trying to puzzle this together from what I can find online, but I could really use the help of someone with more insight into the inner workings of Android.
Any help would be greatly appreciated.

After flashing 4 different ROMs, formatting the emmc completely and doing lord knows what else, it finally dawned on me that I could simply flash the patched boot image using the SP Flash tool instead of via Fastboot. It does wipe the data, and starts the Android setup wizard, but once that is completed, I was able to install Magisk Manager and download the missing files. The device rebooted after that and came back with systemless root.
Problem solved.

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.

Question Red Magic 8 Pro stuck fastboot

Red Magic 8 Pro stuck fastboot
It no longer has sideload mode in recovery

Did you somehow change your slot? If you haven't upgraded the firmware, then the 2nd slot is empty, and it will not boot anything.

BoJaXz said:
Did you somehow change your slot? If you haven't upgraded the firmware, then the 2nd slot is empty, and it will not boot anything.
Click to expand...
Click to collapse
I switched both slots, but I can't boot up

Mr.PvT said:
I switched both slots, but I can't boot up
Click to expand...
Click to collapse
What steps did you do before you got stuck in fastboot?

BoJaXz said:
What steps did you do before you got stuck in fastboot?
Click to expand...
Click to collapse
I patched the root boot file then flashed it failed, then I flashed each file in the payload, I deleted the super, the files in the super can't be flashed oddly, are you rooted, can backup the whole partition help me
Thank you

Mr.PvT said:
I patched the root boot file then flashed it failed, then I flashed each file in the payload, I deleted the super, the files in the super can't be flashed oddly, are you rooted, can backup the whole partition help me
Thank you
Click to expand...
Click to collapse
Did you oem unlock before you tried flashing? You may have to flash the whole image

BoJaXz said:
Did you oem unlock before you tried flashing? You may have to flash the whole image
Click to expand...
Click to collapse
I unlocked the bootloader, I flashed all the files in the payload but still can't boot, hang fastboot or boot to the logo and then shut down
I need someone to back up all my partitions, that's the only way I can do it

Mr.PvT said:
I unlocked the bootloader, I flashed all the files in the payload but still can't boot, hang fastboot or boot to the logo and then shut down
I need someone to back up all my partitions, that's the only way I can do it
Click to expand...
Click to collapse
Did you flash boot.img or init_boot.img?
It sounds like you are booting the wrong slot.

BoJaXz said:
Did you flash boot.img or init_boot.img?
It sounds like you are booting the wrong slot.
Click to expand...
Click to collapse
I flashed those 2 files and changed both slots but failed to start the phone

I faced with the problem by locking the bootloader with init_boot.img for magisk. Then I unlocked it again and switched aactive slot to b and then to a in "Fastboot Enhance" tool. After that my phone entered to the system.
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com

@Mr.PvT did you ever make any progress with this? I am in the same boat now. Flashed a GSI and tested it out. DIdnt like it so flashed the 3.18 Payload.bin thru Fastboot enhance and am stuck on Bootloader. Cant access anything else as no matter what I choose it boots to bootloader.

DarkestSpawn said:
@Mr.PvT did you ever make any progress with this? I am in the same boat now. Flashed a GSI and tested it out. DIdnt like it so flashed the 3.18 Payload.bin thru Fastboot enhance and am stuck on Bootloader. Cant access anything else as no matter what I choose it boots to bootloader.
Click to expand...
Click to collapse
I also went from a GSI to stock ROM and this worked, some steps may be unnecessary:
In bootloader change active slot to a
Flash all of payload.bin images
Reboot to fastboot and flash all of payload images
Reboot to recovery
Hold volume down for a few seconds to enable sideload
Connect the phone to a pc and ADB sideload NX729J-update.zip
Then wipe data and reboot
Also did your calls and messages work when using the GSI?

edzchen said:
I also went from a GSI to stock ROM and this worked, some steps may be unnecessary:
In bootloader change active slot to a
Flash all of payload.bin images
Reboot to fastboot and flash all of payload images
Reboot to recovery
Hold volume down for a few seconds to enable sideload
Connect the phone to a pc and ADB sideload NX729J-update.zip
Then wipe data and reboot
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
In bootloader:
fastboot flash odm odm.img
target reported max download size of 805306368 bytes
sending 'odm' (1284 KB)...
OKAY [ 0.032s]
writing 'odm'...
FAILED (remote: (odm_a) No such partition)
finished. total time: 0.038s
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system_dlkm system_dlkm.img
target reported max download size of 805306368 bytes
sending 'system_dlkm' (428 KB)...
OKAY [ 0.011s]
writing 'system_dlkm'...
FAILED (remote: (system_dlkm_a) No such partition)
finished. total time: 0.018s
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system_ext system_ext.img
target reported max download size of 805306368 bytes
sending 'system_ext' (730792 KB)...
OKAY [ 17.204s]
writing 'system_ext'...
FAILED (remote: (system_ext_a) No such partition)
finished. total time: 17.211s
Nothing happens when I flash system & vendor.
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash vendor_dlkm vendor_dlkm.img
target reported max download size of 805306368 bytes
sending 'vendor_dlkm' (93564 KB)...
OKAY [ 2.181s]
writing 'vendor_dlkm'...
FAILED (remote: (vendor_dlkm_a) No such partition)
finished. total time: 2.187s
In Fastbootd:
Everything that failed in bootloader, flashed beside system. Could only flash _b slots. Nothing seems to exist for slot a. I did not fastboot format or erase anything to my knowledge unless Fastboot Enhance did so when I flashed the playload.bin thru it without having logs on to watch what it did. If it formated or erased any partitions can they be recreated?
And last when in Recovery:
F:\Files\Downloads\RM8P>adb sideload NX729J-update.zip
loading: 'NX729J-update.zip'
error: closed

DarkestSpawn said:
Everything that failed in bootloader, flashed beside system.
Click to expand...
Click to collapse
What is the error when flashing system?
If it has something to do with not being able to resize the system partition, check this link:
Fix FAILED (remote: 'Not enough space to resize partition')
In this comprehensive tutorial, we will show you the steps to fix the FAILED (remote: 'Not enough space to resize partition') error.
www.droidwin.com
I had this problem too.
Which GSI were u on
edzchen said:
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse

edzchen said:
What is the error when flashing system?
If it has something to do with not being able to resize the system partition, check this link:
Fix FAILED (remote: 'Not enough space to resize partition')
In this comprehensive tutorial, we will show you the steps to fix the FAILED (remote: 'Not enough space to resize partition') error.
www.droidwin.com
I had this problem too.
Which GSI were u on
Click to expand...
Click to collapse
I just retried in bootloader with a new outcome this time:
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/6 (786364 KB) OKAY [ 18.742s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
I copied the fastboot.exe from fastboot enchanced to the directory of the extracted payload.bin. Was able to recreate partitions. Am attempting to recover from potential brick.
I tried LineageOS TD-based. Didnt attempt calls or messages. Was just checking out the feel of the rom and its capabilities.

Can someone run this fastboot command in bootloader and fastbootd and save the results in a text file?
fastboot getvar all
Omit the serial number in bootloader and fastbootd's printout.

DarkestSpawn said:
Can someone run this fastboot command in bootloader and fastbootd and save the results in a text file?
fastboot getvar all
Omit the serial number in bootloader and fastbootd's printout.
Click to expand...
Click to collapse
Here you go:

ugene1980 said:
Here you go:
Click to expand...
Click to collapse
So looking thru this, the only difference I have is:
(bootloader) partition-size:userdata: 0x718BCD3000 Mine
(bootloader) partition-size:userdata: 0x35F5CD3000 Yours
as well as:
(bootloader) slot-successful:a:yes Yours
(bootloader) slot-successful:a:no Mine
but thats because it hasnt successfully booted since last flash.
I also need the fastbootd's printout. The one provided was from bootloader. The one from fastbootd will give logical partitions and has slot info.

edzchen said:
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
Did you install carrier serivces from google play, setup APN settings for your carrier and Installing new IMS package: Treble Settings -> IMS features -> install IMS for Qualcomm -> install package. I cant remember if that was in there. Still trying to get booted again

DarkestSpawn said:
Did you install carrier serivces from google play, setup APN settings for your carrier and Installing new IMS package: Treble Settings -> IMS features -> install IMS for Qualcomm -> install package. I cant remember if that was in there. Still trying to get booted again
Click to expand...
Click to collapse
Yeap I did all that but calls and texts only half worked. I could do calls but no audio and I could send texts but couldn't receive. Was the main reason why I switched back to stock