Related
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!
Hi everyone
More than a question, I wanted to share some steps I plan to follow to apply the monthly system update and check I am on the right track. I had a Google Pixel 2 for a few months and I am learning more about the model every day.
Previously, I tried to follow different procedures found here on XDA such as applying OTA with boot images temporarily restored but I ended up with a bootloop not event TWRP could fix since all data was encrypted.
Objective:
Update the system to the latest Pixel 2 update (in this case Feb 2018) avoiding bootloops or bricks
Current Status:
Pixel 2 Walleye with Jan 2018 update
Rooted systemlessly with Magisk
No Magisk modules installed
/system modified since I have AdAway and other apps
No BusyBox installed
No Custom Recovery installed
Proposed steps:
Uninstall Magisk completely
Remove root apps from Device Admin (such as Greenify, Tasker, etc.)
Download latest factory image from Google
Extract the following from the image zip:
bootloader.img
radio.img
boot.img
dbto.img
cache.img
system.img
recovery.img
Restart phone into booloader
Fastboot bootloader.img
Reboot the bootloader
Fastboot the following commands in this order:
radio.img
boot.img
dbto.img
cache.img
system.img
recovery.img
Reboot phone
Install Magisk by patching boot
Re-run root apps (AdAway, etc.)
Renable root apps as Device Admin (Tasker, Greenify, etc.)
Is the above safe enough to avoid bootloop and also not lose apps and data installed?
I am aware any modifications to /system will be lost.
Have a look, let me know if on track, and if you want, give me your blessing.
Yesterday I used Dueces bootloop recovery script to update without losing anything.
I had magisk + TWRP installed
Download full update not OTA, extract to program tools directory or where you keep your goodies. Pull all factory update in folder with deuces recovery script.
From stk rooted ROM reboot bootloader,
Run dueces script from bootloader
After finished script No to format data
Reboot system when done.
From there you should be good to go, you will need to repatch but image in magisk and all that but i lost no data and had no issues
So I was on 1.171019.019 installed 1.172019.21 from fastboot with script and wiped nothing and lost nothing..
** My directions are probably incomplete so follow his instructions in his OP.
This has been discussed all over the place on the forums but you're over complicating the update process. Here's what you do:
Code:
Download the latest Pixel update
extract the update in your ADB folder on a computer
reboot to bootloader
look for the flash-all.bat and remove the -w at the bottom of that code, Save that file (the -w is what causes the device to be wiped)
run flash-all.bat
once that finishes you can fastboot boot twrp.img
it won't decrypt (Feb update broke TWRP decryption) but go read only and get into ADB Sideload mode
adb sideload kernel.zip
adb sideload magisk.zip
reboot
This is what I've done everytime (minus the adb sideload) and I have had zero issues. No loss of data being the biggest concern. Did this using the march update just yesterday and now I'm good to go.
It is worth saying when you start trying to flash (roms, kernels ect..) and you get a little crazy, Dueces Bootloop Recovery script is 100% something to have on deck if something /does/ go wrong.
nolimit78 said:
adb sideload kernel.zip
Click to expand...
Click to collapse
kernel.zip from where? The OTA? One you saved with TWRP on it?
I currently have TWRP and Magisk (default - nothing changed yet) installed on the February update. Is this going to be a monthly thing - flash the update, reinstall TWRP, reinstall Magisk? Not a complaint, just want to know what I'm doing. (Samsung, for all its faults, was a little easier after 6 years of not even having to look at what I was doing. I'll get comfortable with the Pixel, but this is my first update with TWRP and Magisk installed - it did the February update almost before I could read the screen.)
Rukbat said:
kernel.zip from where? The OTA? One you saved with TWRP on it?
I currently have TWRP and Magisk (default - nothing changed yet) installed on the February update. Is this going to be a monthly thing - flash the update, reinstall TWRP, reinstall Magisk? Not a complaint, just want to know what I'm doing. (Samsung, for all its faults, was a little easier after 6 years of not even having to look at what I was doing. I'll get comfortable with the Pixel, but this is my first update with TWRP and Magisk installed - it did the February update almost before I could read the screen.)
Click to expand...
Click to collapse
The kernel.zip is whatever kernel you'd like to use (flash or elemental) but it's not required. I just rename for shorter commands for ADB Yes, you've hit the nail on the head. If you're going to be stock/rooted, you'll have to do this every month to stay current.
And we're still waiting for Dees_Troy to figure out how to add decryption back to TWRP, so it's reinstall everything - including fingerprints - every month. Oh, well. (Hey, no pressure, Dees_Troy - I appreciate just having TWRP on this thing.)
Rukbat said:
And we're still waiting for Dees_Troy to figure out how to add decryption back to TWRP, so it's reinstall everything - including fingerprints - every month. Oh, well. (Hey, no pressure, Dees_Troy - I appreciate just having TWRP on this thing.)
Click to expand...
Click to collapse
In my process outline, you don't have to remove fingerprints.
To boot to TWRP to handle files that you already copied to the phone? TWRP doesn't decrypt the names any more, does it? So all you see is garbage (encrypted hash, I guess). If I want to restore a backup I have to remove the PIN, which seems to remove the fingerprints. Or are you saying to restore the PIN and the fingerprints are still active?
Rukbat said:
To boot to TWRP to handle files that you already copied to the phone?
Click to expand...
Click to collapse
No, this is only to apply the update and flash a custom kernel and magisk
Rukbat said:
TWRP doesn't decrypt the names any more, does it?
Click to expand...
Click to collapse
No, it sure doesn't. This was caused by the Feb Update
Rukbat said:
If I want to restore a backup I have to remove the PIN, which seems to remove the fingerprints.
Click to expand...
Click to collapse
Yeah, to do anything in TWRP (outside of ADB Sideloading) you'll need to remove the PIN.
And evidently something else. I removed the PIN, updated, and the phone's been sitting on the G screen for half an hour. So I rebooted to the bootloader, locked it, and now I'm flashing 021. I have a bad feeling that I'm going to be stuck.
---------- Post added at 05:09 PM ---------- Previous post was at 04:10 PM ----------
As I feared. So I followed Google's instructions to flash the factory image. It went fine, until I got:
Created filesystem with 11/7389184 inodes and 511894/29553659 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
Click to expand...
Click to collapse
Then it wrote the system, but
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
Click to expand...
Click to collapse
It never reboots. If I reboot at that point, I get the recovery screen.
If I reboot into the bootloader and lock it, I get the bootloader with "ERROR: LoadImageAndAuth Failed: Load Error" at the bottom.
I was able to load twrp.img and use it to sideload twrp.zip, but that still doesn't get me back to Android. I tried b ooting into A and B and got the same result - TWRP.
What next? Is there a fix, or does this one have to be replaced also?
Rukbat said:
And evidently something else. I removed the PIN, updated, and the phone's been sitting on the G screen for half an hour. So I rebooted to the bootloader, locked it, and now I'm flashing 021. I have a bad feeling that I'm going to be stuck.
---------- Post added at 05:09 PM ---------- Previous post was at 04:10 PM ----------
As I feared. So I followed Google's instructions to flash the factory image. It went fine, until I got:
Then it wrote the system, but
It never reboots. If I reboot at that point, I get the recovery screen.
If I reboot into the bootloader and lock it, I get the bootloader with "ERROR: LoadImageAndAuth Failed: Load Error" at the bottom.
I was able to load twrp.img and use it to sideload twrp.zip, but that still doesn't get me back to Android. I tried b ooting into A and B and got the same result - TWRP.
What next? Is there a fix, or does this one have to be replaced also?
Click to expand...
Click to collapse
Oh my gosh. Stop sending your phone back.
Update your platform-tools. Change cables. Change ports. Use the search function.
Sent from my Pixel 2 using Tapatalk
I'm not exactly new at this. Different cable, every USB port (including a 2.0 port, new download of both Google's driver and adb/fastboot, a new download of the firmware (and the sha256 is correct).
The next thing I'm going to try, as soon as I finish eating, is another computer. If that fails, and I'm pretty sure it will, I'll call Google tech support. Since it happened twice during an OTA, on two different phones, I may be able to get someone who knows how to feed the firmware into a nearly dead phone. I'm just looking for ideas I haven't had, when I post here. I'm about out of ideas. Again.
Evidently some computer manufacturers don't exactly build what they claim to build. My desktop has 2 USB 3.0 ports (which I already knew wouldn't work) and - supposedly - a USB 2.0 port. Flashing the firmware on the "2.0" port didn't work. Evidently it's not 2.0.
So I resurrected an old Windows 8.0 laptop. I think it has 0 cores running at 0MHz - it's SLOW! But it finally flashed the February update. Tomorrow (it's going on midnight here, and the phone is still downloading the last Google backup) I'll update to March.
Madness - but at least I have a working phone, and know how to get it working again if I need to (and have a few lifetimes to do it). And I have another laptop in the closet that actually works. That one gets resurrected next.
So what you're experiencing isn't new or an issue with your phone that you'd need to RMA the device. It's a learning curve because the A/B partitions are a completely different beast compared to older/other Android devices. Use Duece's Bootloop Recovery script to fix your problems. It'll work and you'll be good to go. Just be sure not to wipe. During my testing, I had to figure out all this myself and was /REALLY/ close to RMA'ing my device. But I continued to research and plugging away and found that that script helps users in your situation, as I've been in that very same situation myself.
No, it's a learning curve because, even though the USB ports on the back of the case are labeled 2.0, and have black plastic, they act like 3.0 ports with a Pixel 2. Doing exactly what both I and Google tech support did with the supposed 2.0 ports, on the aging laptop with real 2.0 ports, solved the "problem" that both Google and I were having. The phone was fine, what we were doing was right, the Acer desktop has a documentation error, and that was the only problem. (Even Google didn't seem to be aware of the USB 3.0/Pixel2 incompatibility, which many of the people in the Pixel 2 forums at XDA are.)
Follow the guide in my signature, it works, and you don't have to muck around with removing PINs and fingerprints.
Thanks for paying attention, but what really bothers me is having to remove the fingerprints in order to do a backup or restore in TWRP. I'm used to just booting to it and flashing a backup if I need it for some reason. If only Google would leave the fingerprint file alone when we went to None for the lock screen, just putting the PIN back would bring the fingerprints back. There's really no reason to delete that file. Maybe delete individual prints at the user's discretion (like changing passwords every once in a while), but not delete the whole thing just because I want to back up my current configuration.
What I do is uninstall Magisk. Then do the normal update from the update page in settings. After this I copy Magisk zip file to a usb drive. I boot into twrp using ADB. It doesn't decrypt but that doesn't matter. Use the USB as storage and install Magisk zip file through TWRP. Reboot and you are done updating with Magisk installed.
That sounds like an easy way of doing it, but doesn't the update balk at the patched boot file? Mine balked at something yesterday, which is what started all the mess yesterday. (Or does Magisk have a "remove and replace the boot file" button?)
nolimit78 said:
This has been discussed all over the place on the forums but you're over complicating the update process. Here's what you do:
Code:
Download the latest Pixel update
extract the update in your ADB folder on a computer
reboot to bootloader
look for the flash-all.bat and remove the -w at the bottom of that code, Save that file (the -w is what causes the device to be wiped)
run flash-all.bat
once that finishes you can fastboot boot twrp.img
it won't decrypt (Feb update broke TWRP decryption) but go read only and get into ADB Sideload mode
adb sideload kernel.zip
adb sideload magisk.zip
reboot
This is what I've done everytime (minus the adb sideload) and I have had zero issues. No loss of data being the biggest concern. Did this using the march update just yesterday and now I'm good to go.
It is worth saying when you start trying to flash (roms, kernels ect..) and you get a little crazy, Dueces Bootloop Recovery script is 100% something to have on deck if something /does/ go wrong.
Click to expand...
Click to collapse
Thank you for the feedback!
One question I had for a while: flashing the data.img wipes what? Doesn't it wipe the apps you have installed?
I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.
Update
I have managed to get adb push to start sending global v10.2.2.0 to the root folder. I'm hoping this will allow me to flash from twrp.
Mota420 said:
I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.
Click to expand...
Click to collapse
Update 2 phone working but still confused.
Pushing the ROM via ADB did indeed allow me to flash from twrp and restore the phone. My question now is why did it happen? Is the new OTA MIUI 10.3... update incompatible with twrp or did something anomalous happen with the flash? I flashed exactly the same method I used with the 10.2.2 ROM a few weeks ago....
OTA's should only be used when completely stock! Even though you uninstalled root, there were still system modifications that more than likely caused your issues. The fastboot version of the firmware is different than the TWRP image. You can not flash a TWRP image via fastboot, hence the missing scripts and bat files. If you had actually downloaded the fastboot image, you would have had a flash_all.bat file that would have returned your device completely to stock with a single run of that file.
Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.
Mota420 said:
Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.
Click to expand...
Click to collapse
OTA's are not a complete image. It is a partial update that only replaces what it has to replace. If MiFlash dis not recognize the image, it was either the wrong image or a corrupt image.
Sometimes updates to the system and recovery partitions fix exploits that things like root and TWRP take advantage of.
Fastboot isn't something you flash to the phone. It is a command line used to flash a dull factory image to the device properly. You do not need MiFlash to flash a fastboot factory image. All you do is extract the full image to your ADB folder unless it is system wide, boot your device into the bootloader, connect ir to your PC, and run the flash_all.bat command contained in the folder you extracted. A command prompt window will open, everything will complete after about a few minutes the window will close, and your phone will reboot.
So the "fastboot" rom is a rom designed to be flashed using fastboot? The miflash error was given because the rom I was trying to flash was corrupted. That makes sense as I'd never known of a fastboot rom before. But it has been a few years since I rooted and romd my phone. I always did the typical flash from the rom image from twrp. I'm still not sure how I got myself in a boot loop unless when I wiped after flashing twrp I accidentally selected another option that erased more than I wanted.. Which makes perfect sense. I knew it had to be an ID10T error lol.
Thanks for the explanation.
Hello,
Earlier today, I flashed the Google OTA on my Pixel 2 (walleye) using TWRP’s sideload feature and the following adb command
Code:
adb sideload ota.zip
Previously, after flashing that zip file, I always reboot, let the phone finish the system update, then reboot to the bootloader where I use Fastboot to boot the TWRP image file so I can re-root the phone with Magisk. Today, I tired to do this same thing, but it did not work. First I rebooted to the boot loader using
Code:
adb reboot bootloader
That command worked. Then I ran
Code:
fastboot devices
That worked as well and my phone was recognized. I then tried to boot the TWRP image with
Code:
fastboot boot twrp.img
This is where the problem occurred. The error code I received was:
Code:
Sending ‘boot.img’ (32768 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
I have no way to boot TWRP right now, any chance you know what to do about this error? I need some way to boot TWRP on my phone.
Thank you in advance!
Can't help, but I'm glad I checked the forum before updating, otherwise I may have run into the same problem. Guess I'll wait until someone responds or you respond with a solution. I usually wait until Sultan posts his kernel update anyway, so I'm in no big hurry.
Edit:
Actually, I noticed you flashed the OTA via ADB. You might try downloading the full image from Google's Pixel factory image page and flashing that via Deuce's boot loop script. Just be sure to pay attention to the prompts and don't accidentally wipe your device.
It's a pretty simple process. Just unzip the contents of the Pixel Image into your ADB folder along with the contents of the zip file inside the image, and then run deuce.bat from the command line initiated from your ADB folder. Then, after it's finished, reboot the device once, update play services, reboot into fastboot, and boot from TWRP to do the rest of your flashing. That's how I update every month and I never run into problems.
jallenhayslett said:
Can't help, but I'm glad I checked the forum before updating, otherwise I may have run into the same problem. Guess I'll wait until someone responds or you respond with a solution. I usually wait until Sultan posts his kernel update anyway, so I'm in no big hurry.
Edit:
Actually, I noticed you flashed the OTA via ADB. You might try downloading the full image from Google's Pixel factory image page and flashing that via Deuce's boot loop script. Just be sure to pay attention to the prompts and don't accidentally wipe your device.
It's a pretty simple process. Just unzip the contents of the Pixel Image into your ADB folder along with the contents of the zip file inside the image, and then run deuce.bat from the command line initiated from your ADB folder. Then, after it's finished, reboot the device once, update play services, reboot into fastboot, and boot from TWRP to do the rest of your flashing. That's how I update every month and I never run into problems.
Click to expand...
Click to collapse
Thank you so much!! This worked when nothing else would! I will keep this in mind for next time :good:
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