So I got a pixel recently. I unlocked the bootloader, installed TWRP, and rooted it. However, it's been a few years since I had an unlocked and rooted phone so I forgot that the OTA updates can't be applied. So I decided to go back to the factory image. A quick google search lead me to an article where they said I could select the Full Unroot option in the settings of SuperSU and it would attempt to restore the stock boot image and recovery image. So I did that, and ended up in a boot loop.
Well, then I decided to try flashing the entire factory images from google, using the flash-all.bat file they provide. It seems to flash the bootloader and the radio fine, but when it comes to the part where it flashes everything in the "image-sailfish-nde63l.zip" (I picked this build because it was the one I was on when the pixel arrived) folder it says "Error: failed to load 'image-sailfish-nde63l.zip': not enough space."
I can still get to the TWRP recovery, and I can get to the bootloader, but currently nothing else seems to work. Please, can anyone help me?
UPDATE: The issue was outdated adb and fastboot. I had 1.0.32, once I had the latest versions (1.0.36 right now) I could fix everything.
UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.
Did you try flashing the stock boot.img to both slots before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure your download is not corrupt or something. https://plus.google.com/+Chainfire/posts/CBL8pnKtA8F
Evo_Shift said:
Did you try flashing the stock boot.img to both partitions before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure you download is not corrupt or something.
Click to expand...
Click to collapse
No, I didn't do any flashing myself before going back to stock. I selected the "Full unroot" option in SuperSU, based on the first result when googling "unroot pixel".
As soon as I did that I was stuck in a bootloop and I tried to restore the factory images according to the google webpage, but that's when I get the error.
Doing what you said doesn't work either, not even redownloading the image.
Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.
UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.
th3p3r50n said:
Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.
Click to expand...
Click to collapse
This happened to me too. That's my current situation. Have adb and fastboot still but can't figure out what steps to fix it.
I think you should focus on why the flash all didn't work. Do you have the latest fastboot? Did you check the md5 of the downloaded rom image? What OS it's your computer running?
How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.
fracman said:
How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.
Click to expand...
Click to collapse
The commands <adb version> and <fastboot --version> seem to return version numbers. My setup returns:
Android Debug Bridge version 1.0.36
Revision fd9e4d07b0f5-android
and
fastboot version fd9e4d07b0f5-android
respectively
Thank you cntryby429. I assumed I was using the latest versions because I had just installed them through the SDK Manager, turns out I was using version 1.0.32. I found the latest version of Minimal ADB and Fastboot and the flash-all script worked fine. I still had a few issues though, so I did a factory reset and then ran the flash-all script again. Now everything works perfectly again. Thanks so much!
Hey all,
So i was trying to update to the Jan build via an edited flash-all.bat (pointing to the correct directory for fastboot and removing -w) and it didn't take because multiple files would come back "*.sig missing". Fastboot sees my device, the SHA for the zip download checks out, and Flash-all will flash a couple of things like the radio. The phone is still on November build (PQ1A.181105.017.A1) though. Anyone else having this issue or any ideas how to correct this?
Thanks!
josephpalozzi said:
Hey all,
So i was trying to update to the Jan build via an edited flash-all.bat (pointing to the correct directory for fastboot and removing -w) and it didn't take because multiple files would come back "*.sig missing". Fastboot sees my device, the SHA for the zip download checks out, and Flash-all will flash a couple of things like the radio. The phone is still on November build (PQ1A.181105.017.A1) though. Anyone else having this issue or any ideas how to correct this?
Thanks!
Click to expand...
Click to collapse
The sig files missing is normal. You can ignore it. But if you're having flashing issues you probably don't have the latest sdk platform tools (fastboot and adb). You need r28. I'm 99 % sure that's your problem.
Sent from my [device_name] using XDA-Developers Legacy app
I never noticed that the .sig files were missing before because I never bothered to scroll back up the cmd window. My fastboot was the lastest version, and I suppose I should have said that up top, but it's always good advice.
I also noticed that it seems it was flashing to the b partition and I'm not sure if that's what was going wrong. I thought Android just knew where to flash and what boot partition to boot from (alternating back and forth).
In the end, I used the stock recovery to adb sideload the OTA, and that worked. Now I'll just wait to experiment more with Feb's update.
josephpalozzi said:
I never noticed that the .sig files were missing before because I never bothered to scroll back up the cmd window. My fastboot was the lastest version, and I suppose I should have said that up top, but it's always good advice.
I also noticed that it seems it was flashing to the b partition and I'm not sure if that's what was going wrong. I thought Android just knew where to flash and what boot partition to boot from (alternating back and forth).
In the end, I used the stock recovery to adb sideload the OTA, and that worked. Now I'll just wait to experiment more with Feb's update.
Click to expand...
Click to collapse
It'll flash to the active slot, so what you saw is normal too. When you extracted the sdk platform tools zip did you just take the fastboot and adb executables? I had some similar issues and ended up taking the other files extracted and put them with fastboot/adb. I'm not sure if they're all need but I'm not having any issues now.
Sent from my [device_name] using XDA-Developers Legacy app
This is just a quick post to document an issue & solution I had when updating my Pixel 5 to the latest OTA and trying to re-root.
I had installed the latest OTA via system update, then downloaded the matching image from the Factory Images Page, pulled the boot.img out of there, transferred it to my Pixel, and used Magisk to patch it.
I then transferred it back to my computer and tried to flash it to the phone using fastboot flash boot boot_patched.img. At this point the phone entered a bootloop.
I booted into the bootloader menu and tried to flash the latest clean system image (without wiping data), when I ran into the following system errors causing the flash to fail when trying to flash the system partition:
Code:
FAILED (remote: Partition system not found)
(and later...)
FAILED (remote: Partition should be flashed in fastbootd)
I initially panicked but the way around this should you ever encounter these errors, is to literally just update your fastboot and adb binaries on your computer. You can grab the latest standalone binaries from here, and throw them where your PATH will find them. After running the flash script again, it worked without a hitch and my phone was up and running without issue.
CarteNoir said:
I initially panicked but the way around this should you ever encounter these errors, is to literally just update your fastboot and adb binaries on your computer. You can grab the latest standalone binaries from here, and throw them where your PATH will find them. After running the flash script again, it worked without a hitch and my phone was up and running without issue.
Click to expand...
Click to collapse
Just wanted to say thanks. I had this issue with my Pixel 6, and updating my ancient ADB/fastboot binaries resolved it!
It's always important to ensure your platform tools are updated! Glad you figured this out!
Thank you!
I had the latest universal ADB/Fastboot drivers installed... but this didn't make a difference
I downloaded latest platform tools, ran the flash-all.bat from there and BOOM, sorted
Thank you so much
Thank you so much. Can't believe the solution is so simple lol
I'm on 11.2.2.2 global, successfully rooted with Magisk. When I follow the OTA update procedure -- uninstall Magisk, install the OTA update but don't reboot, install Magisk to inactive slot, and reboot -- everything appears to work and I don't get any errors, but when the phone boots up afterwards, it's still on 11.2.2.2.
I've tried with the both of the recent OTA updates and the result is the same. Am I doing something wrong, or is this expected when rooted, and I need to wait for the full ROM to be released by 1+?
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com
Okay, I see you can't install incremental OTAs with an unlocked bootloader. Disappointing. Guess I am waiting for full updates.
It is written in a lot of guides. It works when you do it correctly. I got a oneplus 8 and it works without a problem.
0No said:
It is written in a lot of guides. It works when you do it correctly. I got a oneplus 8 and it works without a problem.
Click to expand...
Click to collapse
Well I followed the same procedure when I flashed the full zip of 11.2.2.2, and it worked. So I don't see how I am doing it incorrectly.
Slikkster2k said:
I'm on 11.2.2.2 global, successfully rooted with Magisk. When I follow the OTA update procedure -- uninstall Magisk, install the OTA update but don't reboot, install Magisk to inactive slot, and reboot -- everything appears to work and I don't get any errors, but when the phone boots up afterwards, it's still on 11.2.2.2.
I've tried with the both of the recent OTA updates and the result is the same. Am I doing something wrong, or is this expected when rooted, and I need to wait for the full ROM to be released by 1+?
Click to expand...
Click to collapse
My suggestion is to uninstall magisk (restore the stock image) and reboot. Then do the update and reboot. The use the 11.2.2 modified boot image in fastboot do: fastboot boot boot.img and when it boots let magisk install which will backup then modify the new boot image from 11.2.4.4 and voila you now have root and a backup of the newest boot image which will let you be able to update to the next Ota using this same method
toyanucci said:
My suggestion is to uninstall magisk (restore the stock image) and reboot. Then do the update and reboot. The use the 11.2.2 modified boot image in fastboot do: fastboot boot boot.img and when it boots let magisk install which will backup then modify the new boot image from 11.2.4.4 and voila you now have root and a backup of the newest boot image which will let you be able to update to the next Ota using this same method
Click to expand...
Click to collapse
Well I tried this and I'm really hosed now... phone will only boot to recovery after uninstalling Magisk and rebooting. I tried flashing the stock 11.2.2.2 boot.img from fastboot, and that didn't help either. I'm kinda stuck unless I can flash the full 11.2.2.2 from fastboot or recovery? I don't know how to do that.
Slikkster2k said:
Well I tried this and I'm really hosed now... phone will only boot to recovery after uninstalling Magisk and rebooting. I tried flashing the stock 11.2.2.2 boot.img from fastboot, and that didn't help either. I'm kinda stuck unless I can flash the full 11.2.2.2 from fastboot or recovery? I don't know how to do that.
Click to expand...
Click to collapse
What version OP9 are you using and what OS version and phone version boot images are you using?
Instructions are here for how to do a manual flash via fastboot. Basically extract with payload dumper and flash each image manually like in the example in the link.
toyanucci said:
What version OP9 are you using and what OS version and phone version boot images are you using?
Instructions are here for how to do a manual flash via fastboot. Basically extract with payload dumper and flash each image manually like in the example in the link.
Click to expand...
Click to collapse
Not sure what you mean by what version OP9?
I have 11.2.2.2AA installed, I've tried flashing the matching stock boot image, the magisk patched version of it, and even the stock 11.2.3.3AA boot image.
I found those instructions and I'm trying it, but I'm running into problems with the payload dumper (FileNotFoundError when attempting to dump).
Slikkster2k said:
Not sure what you mean by what version OP9?
I have 11.2.2.2AA installed, I've tried flashing the matching stock boot image, the magisk patched version of it, and even the stock 11.2.3.3AA boot image.
I found those instructions and I'm trying it, but I'm running into problems with the payload dumper (FileNotFoundError when attempting to dump).
Click to expand...
Click to collapse
And you're sure the boot images you've tried are for the global version? If all you've messed with is the boot image I don't see why the phone won't boot Before flashing any boot image it's best to do fastboot boot boot.img. It doesn't overwrite the boot image so in case it doesn't work a simple reboot will get you back up ad running.
Re payload dumber make sure you've CD'd to the right folder? I had the same error when I was trying to do it yesterday and it was because I hadn't CD'd to the right folder.
Have you got the files extracted?
toyanucci said:
And you're sure the boot images you've tried are for the global version? If all you've messed with is the boot image I don't see why the phone won't boot Before flashing any boot image it's best to do fastboot boot boot.img. It doesn't overwrite the boot image so in case it doesn't work a simple reboot will get you back up ad running.
Re payload dumber make sure you've CD'd to the right folder? I had the same error when I was trying to do it yesterday and it was because I hadn't CD'd to the right folder.
Have you got the files extracted?
Click to expand...
Click to collapse
I found them in the root thread in this forum, the user who posted them said they were for global, yes.
I did try using fastboot boot first, but I get this error:
Code:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
So I just tried to flash instead, which flashes successfully, but then it fails to boot after and dumps me back into fastboot or recovery.
I know my way around the command line pretty well, so yes I'm in the right directory. Here's the full error when running extract_android_ota_payload.py:
Code:
Extracting 'abl.img'
Traceback (most recent call last):
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 142, in <module>
main(filename, output_dir)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 121, in main
parse_payload(payload, p, out_f)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 95, in parse_payload
r = decompress_payload('xzcat', data, e.num_blocks * BLOCK_SIZE, operation.data_sha256_hash)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 78, in decompress_payload
p = subprocess.Popen([command, '-'], stdout=subprocess.PIPE, stdin=subprocess.PIPE)
File "C:\Program Files\Python39\lib\subprocess.py", line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Program Files\Python39\lib\subprocess.py", line 1416, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
I believe it's failing because it can't find xzcat. I am trying to install MinGW in an effort to resolve that.
The only boot image I haven't tried yet so far is 11.2.4.4 as I haven't been able to find a copy of that. I don't know why that would work when nothing else has though.
Slikkster2k said:
I found them in the root thread in this forum, the user who posted them said they were for global, yes.
I did try using fastboot boot first, but I get this error:
Code:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
So I just tried to flash instead, which flashes successfully, but then it fails to boot after and dumps me back into fastboot or recovery.
I know my way around the command line pretty well, so yes I'm in the right directory. Here's the full error when running extract_android_ota_payload.py:
Code:
Extracting 'abl.img'
Traceback (most recent call last):
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 142, in <module>
main(filename, output_dir)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 121, in main
parse_payload(payload, p, out_f)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 95, in parse_payload
r = decompress_payload('xzcat', data, e.num_blocks * BLOCK_SIZE, operation.data_sha256_hash)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 78, in decompress_payload
p = subprocess.Popen([command, '-'], stdout=subprocess.PIPE, stdin=subprocess.PIPE)
File "C:\Program Files\Python39\lib\subprocess.py", line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Program Files\Python39\lib\subprocess.py", line 1416, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
I believe it's failing because it can't find xzcat. I am trying to install MinGW in an effort to resolve that.
Click to expand...
Click to collapse
Try the instructions here to get payload dumper working
toyanucci said:
Try the instructions here to get payload dumper working
Click to expand...
Click to collapse
Okay that worked. I should've just tried that version first instead of the 'newer' one I found.
Now when I try to flash I'm getting
Code:
FAILED (remote: 'Flashing is not allowed for Critical Partitions')
I have found that I can use 'fastboot flashing unlock-critical' to unlock these, but it will wipe the phone.
I really don't want to wipe my device if I can avoid it.
Maybe try just flashing the boot partition
Slikkster2k said:
Now when I try to flash I'm getting
Code:
FAILED (remote: 'Flashing is not allowed for Critical Partitions')
I have found that I can use 'fastboot flashing unlock-critical' to unlock these, but it will wipe the phone.
I really don't want to wipe my device if I can avoid it.
Click to expand...
Click to collapse
Maybe try just flashing the boot partition
toyanucci said:
Maybe try just flashing the boot partition
Maybe try just flashing the boot partition
Click to expand...
Click to collapse
Yeah that was the first thing I tried, no dice.
You have 11.2.4.4 global on your phone right? Would you be able to retrieve the stock boot.img and upload it for me so I can try booting with that? It's a long shot but I'm desperate.
Slikkster2k said:
Yeah that was the first thing I tried, no dice.
You have 11.2.4.4 global on your phone right? Would you be able to retrieve the stock boot.img and upload it for me so I can try booting with that? It's a long shot but I'm desperate.
Click to expand...
Click to collapse
Uploaded to mega here
I found 2 backed up images and I wasn't sure which is 4.4 so I uploaded both to the link for you to try
So I tried fastboot flashing unlock_critical just now, and it fails and says Device already : unlocked!
I am finding that these instructions for restoring the OnePlus 8T do not work at all for the OnePlus 9. My phone boots straight to fastboot on slot a, and if I try fastboot reboot fastboot, it fails to boot to fastboot userspace.
On slot b, it will boot to fastboot userspace, which allows me to flash the partitions I extracted from the payload.bin, BUT the list of files is not the same as for the 8T. I flashed the ones that were in list, and a couple more that had similar names as missing ones, but it's still not a complete list. At no point have I done 'fastboot -w' as I don't want to wipe userspace.
I'm also not sure if I should try to flash every file it extracted to the equivalent partition name, as the instructions for the 8T don't do that.
toyanucci said:
Uploaded to mega here
I found 2 backed up images and I wasn't sure which is 4.4 so I uploaded both to the link for you to try
Click to expand...
Click to collapse
Thanks, didn't work unfortunately.
Slikkster2k said:
So I tried fastboot flashing unlock_critical just now, and it fails and says Device already : unlocked!
I am finding that these instructions for restoring the OnePlus 8T do not work at all for the OnePlus 9. My phone boots straight to fastboot on slot a, and if I try fastboot reboot fastboot, it fails to boot to fastboot userspace.
On slot b, it will boot to fastboot userspace, which allows me to flash the partitions I extracted from the payload.bin, BUT the list of files is not the same as for the 8T. I flashed the ones that were in list, and a couple more that had similar names as missing ones, but it's still not a complete list. At no point have I done 'fastboot -w' as I don't want to wipe userspace.
I'm also not sure if I should try to flash every file it extracted to the equivalent partition name, as the instructions for the 8T don't do that.
Click to expand...
Click to collapse
I had a similar situation with the 7T (and 8T lol) and used the info from the link as a guide to flashing every partition. I did have to wipe the phone though but in the end it booted up which was the biggest concern I had
HI all,
While attempting to update my Pixel 7 Pro (while retaining root, via the modified factory zip method where you root init_boot.img, then replace it in the factory zip, then run google's provided flash-all script) I've been encountering this issue when flash-all reached its last step of flashing the actual zip with the images via fastboot:
"fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"
This happens on both the new firmware as well as with the firmware I flashed through this method previously. New firmware after this causes a boot loop, while performing a flash of the old firmware results in the same error but at least gets me back into the system in the state it was in before attempting to upgrade.
Any idea why this is happening? I've ensured fastboot & adb are both up to date and attempted from both Windows and a Fedora laptop both to the same error. It's worth noting I installed the old (current) firmware previously through the same method successfully (before this) so not sure why it's decided to not work now....
Update: tried again via PixelFlasher and did not encounter the error so I guess if anyone else hits this issue and sees this post.... just use PixelFlasher(?????) No idea the why or how but seems to be good now.
Sounds like you were trying to flash in Fastboot mode rather than FastbootD.
Tomadock said:
Sounds like you were trying to flash in Fastboot mode rather than FastbootD.
Click to expand...
Click to collapse
Negative. I also thought that might be the issue and attempted it (the actual command it was running, not the entire script again since that would reboot to bootloader again) in FastbootD as well to the same result.
Sceleratis said:
HI all,
While attempting to update my Pixel 7 Pro (while retaining root, via the modified factory zip method where you root init_boot.img, then replace it in the factory zip, then run google's provided flash-all script) I've been encountering this issue when flash-all reached its last step of flashing the actual zip with the images via fastboot:
"fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"
This happens on both the new firmware as well as with the firmware I flashed through this method previously. New firmware after this causes a boot loop, while performing a flash of the old firmware results in the same error but at least gets me back into the system in the state it was in before attempting to upgrade.
Any idea why this is happening? I've ensured fastboot & adb are both up to date and attempted from both Windows and a Fedora laptop both to the same error. It's worth noting I installed the old (current) firmware previously through the same method successfully (before this) so not sure why it's decided to not work now....
Click to expand...
Click to collapse
i tried the latest version of "SDK Platform Tools"; it worked for me
Sceleratis said:
HI all,
While attempting to update my Pixel 7 Pro (while retaining root, via the modified factory zip method where you root init_boot.img, then replace it in the factory zip, then run google's provided flash-all script) I've been encountering this issue when flash-all reached its last step of flashing the actual zip with the images via fastboot:
"fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"
This happens on both the new firmware as well as with the firmware I flashed through this method previously. New firmware after this causes a boot loop, while performing a flash of the old firmware results in the same error but at least gets me back into the system in the state it was in before attempting to upgrade.
Any idea why this is happening? I've ensured fastboot & adb are both up to date and attempted from both Windows and a Fedora laptop both to the same error. It's worth noting I installed the old (current) firmware previously through the same method successfully (before this) so not sure why it's decided to not work now....
Click to expand...
Click to collapse
Literally error says everything....
You need latest platform tools that supports vendor _kernel_boot partition
Google added vendor kernel boot partition on P7 series that's been supported only on latest platform tools