Problem reflashing stock image - Google Pixel XL Questions & Answers

I keep getting this error when flashing the stock image, anyone knows what this is about? Cant reflash the image, I am on stock everything..
Flashing boot separately works..
I am on the V build..
Also, cant change active slot from fastboot.. But booted twrp and changed the slot fine...
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boota' (26405 KB)...
OKAY [ 0.731s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.186s
when flashing system image getting this..
C:\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'systema' 1/3 (521974 KB)...
OKAY [ 13.026s]
writing 'systema' 1/3...
FAILED (remote: partition table doesn't exist)
finished. total time: 13.119s

Update your ADB/fastboot drivers from Android SDK Manager.

xocomaox said:
Update your ADB/fastboot drivers from Android SDK Manager.
Click to expand...
Click to collapse
Still the same error..

siddhesh.raikar said:
Still the same error..
Click to expand...
Click to collapse
Are you using the minimal fastboot and adb

Yeah, definitely get the 1.6gb package as it has the correct files.
Also make sure you are using the correct fastboot executable as you can have multiple instances of it on your computer. If you have edited the PATH system variable make sure to change it to the new location if you installed the SDK suite.

Yeah I had so many different toolkits and adb folders on my PC, it wouldn't work till I deleted all of them then download the Android SDK from Google, and installed platform tools. All the quick answer, dummy proof adb files on the internet do not work for this phone

Lost Storage Capacity after flashing Stock
My available storage fell from 128 to 112 after flashing the stock image. I imagine it has to do with failed partition_a flashing at some step. But was curious if anyone else had this problem? I'm currently going through the recommendations above (as I shamefully also {though cmd prompted from Platform_Tools} have the minimal adb set on my comp as well)... I have deleted all that I was aware of - and am still completing a successful flash (as I previously had been) but still have not been able to regain that lost 16 gigs of space. Next step will be to dig through the comp to see if there are any leftovers from the minimal packages hiding around on my computer.
I have been flashing from google sdk package; thought I had gotten rid of all minimal adb tools, but still missing internal storage. Any advice?
I can provide (though not at the moment) the terminal command-line history - if that would be any help.
Thanks.

federalitamale said:
I have been flashing from google sdk package; thought I had gotten rid of all minimal adb tools, but still missing internal storage. Any advice?
Click to expand...
Click to collapse
You'll probably have to factory reset to recover the lost space, if nothing else works.

Thanks. I will try that. For clarity sake, I should have said earlier, my 128 pixel is showing an available 110 gigs of a possible 112. Not 112 free of a possible 128. 16 gigs just seem to have vanished off the card.

cam30era said:
You'll probably have to factory reset to recover the lost space, if nothing else works.
Click to expand...
Click to collapse
Unfortunately that did not recover the missing internal drive space. I attempted both from the settings, and from recovery mode.
I've attached a .txt of everything that succeeded and failed during the flash.
Oh - and I should have been looking at my phone rather than Windows. It's still missing - but it's actually:
Used: 8.22 GB of 119 GB - so only 9 GB missing. Sorry.
It's like rather than erasing and formatting the original system when I flashed the stock image - it just repartitioned it to unusable space; and set up a new partition of the system I was then flashing.

federalitamale said:
Used: 8.22 GB of 119 GB - so only 9 GB missing. Sorry.
Click to expand...
Click to collapse
This is exactly as it should display, the 'missing' 9GB is the operating system itself, which is not reported in storage settings.
Its that way on every phone.

uicnren said:
This is exactly as it should display, the 'missing' 9GB is the operating system itself, which is not reported in storage settings.
Its that way on every phone.
Click to expand...
Click to collapse
But wouldn't that mean there is 17.2 GB of "system" on it? Storage shows as 8.2 GB of system installed on the device, and the phone is factory reset (I haven't put any apps or data on it). Yet it still only shows like 111 GB free after that. So 111 GB free plus the 8.2 system still doesn't add up to 128. So what/where is that remaining 9?. Sorry if I'm being dense.
Before I stupidly flashed TWRP on it, it showed 119 GB free of 128 GB. That's why I flashed the stock on it to fix my dumb mistake and run TWRP read only on it to do the systemless root, to keep OTA updates.
So I reflashed the stock image, then I successfully ran, Read only TWRP, flashed chain fire's SU. I have root status, have confirmed I only have the stock recovery. Yet my total storage (used plus free) only shows as 119 GB. As well, I discovered this morning, OTA updates will not install.
Reflashed stock again, stopped there. Still 119 GB, still can't install OTA updates.
Thanks for the advice.

Related

[Q] GPE 5.0.1 Bricked my phone - can anybody help?

Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!
should be in Q&A mate
I have requiested the mods to move this
So first things first. You are not bricked, you are just stuck. Bricked means your device cannot boot, cannot turn on, cannot access any bootloaders or recovery.
You messed something up and it is failing to boot, it isnt bricked.
Second, running disk encryption on rooted devices is especially dangerous for these scenarios. Disk encryption attempts to prevent many of the things running roms, custom recoveries and such put on the device.
Now, I cannot recall if a full GPE version can do this or not, but from Fastboot you should be able to flash just the system partition. But being you are encrypted it may fail to access your old data. The command for that would be:
Fastboot flash system system.img (if you were able to obtain a system.img)
Again that works on Nexus devices, I cant recall if the GPE fastboot accepts it as well.
Wish you well, but honestly I would expect to lose your data. The reason the update failed the second time was because you are Rooted. 5.0+ has a new OTA system where any changes to the system partition can/will fail the OTA.
tschakk said:
Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!
Click to expand...
Click to collapse
First, your phone isnt bricked, its not bricked as long as you can access HBOOT, second, why would you encrypt your phone? uhg... I dont know what to tell you, try RUUing to stock, but dont expect to keep your data...
I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..
tschakk said:
I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..
Click to expand...
Click to collapse
You can only flash boot and recovery individually, you would have to put system.img and android-info.txt in a zip and flash in ruu mode
UNBELIEVABLE!
I could restore the system with dd... Just copied the system.img from Android 4.4.4 to the block device.. now the phone is booting up and i can see my data... uffff.. :victory:
so now i will do a backup and then go on...
Solution
If someone should encounter the same issue, this is what I have done to fix it:
I didn't want to lose my data, so I did not reinstall the RUU.. I couldn't get my data with ADB backup, because you need a system display to do it. And I also couldn't find any recovery which supported device encryption for the m8.. So I thought to backup my data partition with 'dd' to an external SD card and then if necessary I would reinstall the full system with RUU..
Code:
$ cat /fstab.qcom #to find the needed partitions
$ dd if=</dev/block/DATA-DEVICE> of=/external-sd/backup.bin
Now I knew I had a backup and was on the safe side. So I wanted to try to rewrite the system partition with the system.img from 4.4.4 GPE RUU. But fastboot flash didn't work. I always got this error message:
Code:
$ fastboot flash system system.img
...
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
So what the hell, I used 'dd' also for this... :
Code:
$ cat /fstab.qcom #again to find the needed partitions
$ dd if=/external-sd/system.img of=</dev/block/SYSTEM-DEVICE>
And this actually worked, my m8 booted up with Android 4.4.4. First thing I did when Android booted was a full Android backup with adb.. To be safe to have my data back, because I didn't really know how to extract my encrypted data from the bin file I've created before... Then I just installed the update to 5.0.1 and this time it worked...

Stuck in bootloop, can't flash

Posted in the general thread, but no replies.
I seem to have softbricked my phone by rooting then applying the OTA update. I've tried re-rooting, wiping cache, factory resetting, etc., and nothing seems to work. Following the steps in http://forum.xda-developers.com/zenf...d-zf2-t3127835 I can get to step 7, but when I submit any of the commands I get this:
Code:
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14822 KB)...
OKAY [ 0.666s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.839s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.545s]
writing 'recovery'...
FAILED (remote: Permission denied
)
finished. total time: 0.716s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11868 KB)...
OKAY [ 0.522s]
writing 'boot'...
FAILED (remote: Permission denied
)
finished. total time: 0.694s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Permission denied)
finished. total time: 125.564s
It wasn't clear if it was a windows permission error or an android permission error, so I tried an admin command prompt but that didn't change anything.
Any suggestions? Thanks in advance
Bump in hopes of a solution
And another bump, any help would be greatly appreciated
I'm wondering if it has to do with having a bootloader installed being over a certain version. I had 2 Asus Zenfone 2s and I get the same error messages. I can't remember what my first ZF2 had for firmware to start, but I was a dummy and updated it all the way to 2.20.40.90 stock. Everytime I tried to write via fastboot, Permission Denied. My new ZF2 on 2.20.40.59 also has the same problem. I feel like Asus patched the ability to fastboot these files or something. Running CMD as Administrator doesn't help the situation.
bumping because I'm having the same issue, coming back to stock after having CM12.1
As easy as it sounds, the solution was just flashing the newest software from the ASUS website, using adb sideload UL-Z00A-WW-2.20.40.97-user.zip
I can't imagine why I wouldn't have done that sooner, but it fixed it. Whether that worked due to something else I did, i have no idea, but my phone is now working
I had that before but fortunately I was able to fix it.
Get a microsd, but a firmware from Asus website, make sure that it is the correct one if you have WW then download WW, download it from Asus website or it will not work.
Then put the micro sd on the phone., rename the file MOFD_UPDATE don't put zip cause it will be doubled.
Boot to bootloader then boot to recovery. Automatically the phone will restore itself.
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
I was also unable to mount the SD card, might have something to do with MOFD not being mapped.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
KylarBStern said:
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
ebanreb37 said:
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
I already tried it, I wrote in my post that I tried it. And it didn't work.
KylarBStern said:
I already tried it, I wrote in my post that I tried it. And it didn't work.
Click to expand...
Click to collapse
SD card MUST be FAT32 or 32gb or less. If you are using anything else it won't detect the sd card.
Cheers...
Ok it's been a while since I've tried anything with this phone and just now I did what you said, copied the firmware file which I downloaded from ASUS to a 2GB sd card formatted in fat32, rebooted to recovery phone applied the update sucessfully and restarted but I am still stuck in bootloop ? I tried every method so I asume the phone is ****ed and I should send it back for RMA ?

Can't Update Verizon HTC 10 to Android 7 Nougat

Hello everyone,
I have a factory HTC 10, Verizon phone. I'm running on Straight Talk so I don't get OTA updates, but I've updated with my laptop and Sync Manager before, so I know I can. So, I finally got the notification on Sync Manager that I could update my phone, from 6.0.1 Software # 1.85.605.9 to 7.0 S# 2.41.605.20. I go to update it add it stops at 19% and says that I have to low battery, I then charge it 100% and try again, but the same thing happens, the update stops at 19% and says my batteries to low.
Now, in my phone under About, the software # is 1.85.605.9, however when I boot to Download Mode my software # reads 2.41.605.20. And I confirmed this with Sync Manager, when my phone is normal booted and plugged in Sync Manager says my software # is 1.85.605.9. But when in Download Mode and plugged in Sync Manager reads 2.41.605.20.
I backed up my phone and did a Factory Data Reset, hoping that would help, but I still have the same problem. Can anyone help?
Thank you.
https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586 here is the link to the latest official RUU for vzw.
Thank you.
I wanted to flash Nougat the first time that the upgrade failed but I couldn't find the RUU online at the time.
However, I still cant get the update to work. Following the directions from the link, I still cant get my phone to update.
this is what I get on the CMD Prompt,
- PS C:\Unlock> htc_fastboot oem rebootRUU
...
OKAY [ 0.085s]
finished. total time: 0.100s
- PS C:\Unlock> htc_fastboot flash zip android7.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2512129245 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2512129245 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2512129245 is not a multiple of the block size 4096
OKAY [ 1.012s]
writing 'zip' 1/1...
(bootloader) HOSD CL#857212
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_9
(bootloader) j4njZ
(bootloader) ERR preload central directory info failed (EOCD).
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 2.099s
Is my phone really screwed up?
Check the MD5 of your download vs the AFH download link. Make sure they match
I don't think you read the first post of the topic which holds the RUU! It's all explained there how to flash it. I would take the SDCard method. You can't "just" flash it.
Read the first post from the given link and it will be clear.
So take the RUU zip rename it and put it on the SD then boot into download mode and follow procedure
82dodge331 said:
Thank you.
I wanted to flash Nougat the first time that the upgrade failed but I couldn't find the RUU online at the time.
However, I still cant get the update to work. Following the directions from the link, I still cant get my phone to update.
this is what I get on the CMD Prompt,
- PS C:\Unlock> htc_fastboot oem rebootRUU
...
OKAY [ 0.085s]
finished. total time: 0.100s
- PS C:\Unlock> htc_fastboot flash zip android7.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2512129245 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2512129245 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2512129245 is not a multiple of the block size 4096
OKAY [ 1.012s]
writing 'zip' 1/1...
(bootloader) HOSD CL#857212
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_9
(bootloader) j4njZ
(bootloader) ERR preload central directory info failed (EOCD).
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 2.099s
Is my phone really screwed up?
Click to expand...
Click to collapse
You ever have any luck?
aer0zer0 said:
You ever have any luck?
Click to expand...
Click to collapse
He didn't post back, so I would imagine he followed the instructions in the OP this time. :laugh:
xunholyx said:
He didn't post back, so I would imagine he followed the instructions in the OP this time. :laugh:
Click to expand...
Click to collapse
I always try to ask, just to make sure they aren't stuck or frustrated. It's hard being new, and having people flame respond all the time (as I'm sure you saw some of the previous comments)
Thanks everyone for assuming I'm an idiot that doesn't know how to read. I did try to load the RUU via the SD card, that didn't work either. Yes it was formatted to FAT32. The phone recognized the card but didn't detect the RUU. zip file.
Anyway, I haven't bothered since I've been busy and the phone is working.
Is there a reason why my phone says its running Nougat in Download mode, but is running Marshmallow when booted up?
82dodge331 said:
Thanks everyone for assuming I'm an idiot that doesn't know how to read. I did try to load the RUU via the SD card, that didn't work either. Yes it was formatted to FAT32. The phone recognized the card but didn't detect the RUU. zip file.
Anyway, I haven't bothered since I've been busy and the phone is working.
Is there a reason why my phone says its running Nougat in Download mode, but is running Marshmallow when booted up?
Click to expand...
Click to collapse
sounds like firmware from nougat mixed with marshmallow OS. was the RUU.zip renamed to 2PS6IMG.zip?
If Nougat and Marshmallow did mix, could that have happened when my upgrade failed the first time? I tried renaming it a few things, I think I renamed it to 2PS6IMG.zip, but cant remember. Also, I tried to use my 128GB SD card, formatted it to FAT32, but I had to download a format software, as I could get Windows to format it natively, in File Explorer or Command line. Could the SD card be to large? I wanna try again, but I'm gonna get a smaller SD card to try.
82dodge331 said:
If Nougat and Marshmallow did mix, could that have happened when my upgrade failed the first time? I tried renaming it a few things, I think I renamed it to 2PS6IMG.zip, but cant remember. Also, I tried to use my 128GB SD card, formatted it to FAT32, but I had to download a format software, as I could get Windows to format it natively, in File Explorer of Command line. Could the SD card be to large? I wanna try again, but I'm gonna get a smaller SD card to try.
Click to expand...
Click to collapse
What it says in download mode is your firmware version, what it says in settings > about is your ROM base (what the ROM you are running is based on)
Also, with the 10 you don't need to have your card formatted to FAT32. exFAT will work just fine. I would suggest you re-format to that and try again (128gb cards aren't made for FAT32). And make sure you haven't accidentally renamed it to 2PS6IMG.zip.zip (I've seen that mistake several times before).
Well, like I said I formatted to FAT32 because that's what aer0's tutorial said to do. I didn't think it would work with my 128GB, and I was worried I was going to corrupt it, but it didn't.
anyway, I'm going to get an 8GB SD card and try again, I'll format to FAT32 first just to try, then if it doesn't work I'll reformat to exFAT and go again.
I'll report back tonight.
well it worked, I'm running Nougat. I got a 16GB SD card, couldn't find an 8 at Walmart, was already formatted to FAT32, I loaded the .zip file on there from my computer and renamed it 2PS6IMG.zip. Flashed perfectly.
after I plugged it into Sync Manager just to see if it would recognize my phone, as I've trouble with that before. And turns out there's a new update. So, I tried to upgrade, to the new latest and it failed @ 19% again, with a battery to low warning. I had 90% battery. I just cant update my phone through Sync Manager I guess.
Thanks aer0 for the help. I think my problem was I wasn't renaming the zip file right or at all. I tried so many times I forgot exactly what I tried. anyway, I might be even more helpful to add to your tutorial to rename what ever zip a person downloads, they need to rename it to 2PS6IMG.zip. Because, I understood it as, download whichever 2PS6IMG_something.zip, drop it on the SD and go. Just might be more helpful.
82dodge331 said:
well it worked, I'm running Nougat. I got a 16GB SD card, couldn't find an 8 at Walmart, was already formatted to FAT32, I loaded the .zip file on there from my computer and renamed it 2PS6IMG.zip. Flashed perfectly.
after I plugged it into Sync Manager just to see if it would recognize my phone, as I've trouble with that before. And turns out there's a new update. So, I tried to upgrade, to the new latest and it failed @ 19% again, with a battery to low warning. I had 90% battery. I just cant update my phone through Sync Manager I guess.
Thanks aer0 for the help. I think my problem was I wasn't renaming the zip file right or at all. I tried so many times I forgot exactly what I tried. anyway, I might be even more helpful to add to your tutorial to rename what ever zip a person downloads, they need to rename it to 2PS6IMG.zip. Because, I understood it as, download whichever 2PS6IMG_something.zip, drop it on the SD and go. Just might be more helpful.
Click to expand...
Click to collapse
I unfortunately don't have the hosting rights to those files. That's @Kisakuku and others. Have I thought about it, sure have... The only problem with renaming them all to what it should be is you lose tracking of the versions, with so many it's easy to do. What I have done is on my PC, I created a sub directory of all the RUU's, then renamed them appropriately within, so I can drag and drop to the SD. Also, with OCD, I have multiple 4gb SDs labelled with versions. Which RUU did you flash? .23 is the newest, shouldn't be a new release just yet.
I didn't mean for you to rename all the files, as you said no one could keep track of which version is which. I meant you should add a note in the instructions for the downloader to rename the file after they download the zip.
I flashed to .20, because I didn't know .23 was available until I connected to Sync Manager. So I tried to update though Sync Manager to .23 from .20, and it failed @ 19%
82dodge331 said:
I didn't mean for you to rename all the files, as you said no one could keep track of which version is which. I meant you should add a note in the instructions for the downloader to rename the file after they download the zip.
I flashed to .20, because I didn't know .23 was available until I connected to Sync Manager. So I tried to update though Sync Manager to .23 from .20, and it failed @ 19%
Click to expand...
Click to collapse
I updated the OP in the verizon RUU thread per your request sir
It was just a suggestion, but hopefully it helps others just as it did for me.
Again, I appreciate the help.

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.

Can't Flash Factory Image.

Hey everyone,
So my Pixel 2 XL is kinda stuck at the moment. I'm having problems getting stock back up on my Pixel 2 XL, When I click onto flash-all command it does the job till it gets near the end of the process and then comes up with the error as 'Target didn't report max-download-size' I've used other factory images for the Pixel 2 XL CMD and the phone isn't having it at all. I really don't know what to do at this point. I need some kind of fix to this. Any advice would be really great.
** NEW ERROR **
target reported max download size of 536870912 bytes
sending 'bootloader' (36356 KB)...
OKAY [ 0.799s]
writing 'bootloader'...
OKAY [ 0.370s]
finished. total time: 1.169s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.341s]
writing 'radio'...
OKAY [ 0.570s]
finished. total time: 1.911s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: failed to load 'image-taimen-pq2a.190405.003.zip': Not enough space
Press any key to exit...
When you say you flashed others and all was ok, what month are those images from? What I'm wondering is if you have out dated fastboot. Did you already update your platform tools? If not, do that and see if it works.
I usually run into this issue if I don't have enough free space on my C drive (at least 4 GBs; the system partition image is around 2 GBs...). And if it's not the free space issue, usually it's merely just a change/re-initialization of the USB cord. Make sure you have the latest platform-tools (r28.0.2 is the most up-to-date version) as well as using a USB-C to USB-A cord (USB-C to USB-C seems to cause endless amount of issues and is usually the root cause for random unknown reasons...)...it usually sets things up right to work the next time around.
But, if making sure of all the previous things, and you restarted your phone and computer already, then you might try re-downloading the Full Factory image and extracting it once again (don't forget to re-edit the .bat/.sh file to not include the "-w" attribute); and consider even going through the trouble of comparing checksums to make sure you are getting/using the exact proper copy of the factory image...
good luck to you and hope this helps...
Fe Mike said:
When you say you flashed others and all was ok, what month are those images from? What I'm wondering is if you have out dated fastboot. Did you already update your platform tools? If not, do that and see if it works.
Click to expand...
Click to collapse
I uninstalled and reinstalled fastboot, re-downloaded platform tools and reinstalled all drivers. I downloaded the factory file straight from google which was the android 9.0 April 2019 update. Yet I'm still having this problem. It was working fine yesterday as I went to reboot it, it just went straight into a bootloop. The phone was rooted via magisk.
So I got a new error now and fastboot is telling me that there is not enough space to load the zip file. Everything is extracted out of the image zip file and moved into the adb folder
Finally Solved the problem! So I booted the phone into its stock recovery and pushed the adb zip file through and then after waiting for 20 minutes I rebooted the phone and its booted into its stock rom. Thanks everyone!
Knxed_ said:
Finally Solved the problem! So I booted the phone into its stock recovery and pushed the adb zip file through and then after waiting for 20 minutes I rebooted the phone and its booted into its stock rom. Thanks everyone!
Click to expand...
Click to collapse
You can boot twrp and flash the ota as well

Categories

Resources