Problems flashing system images for the Pixel XL - Google Pixel XL Questions & Answers

So I'm pretty accustomed to flashing system images and sideloading OTAs, but for some reason things are just not working for me on my Pixel XL.
Every time I run the "flash-all.bat" script (with the -w removed to preserve data) I can never seem to update properly, I get the following:
Code:
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.776s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.064s]
finished. total time: 1.844s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.356s]
writing 'radioa'...
OKAY [ 0.952s]
finished. total time: 2.322s
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.015s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: [removed]
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boota' (26405 KB)...
OKAY [ 0.680s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.139s
Press any key to exit...
I am on the original stock NDE63L, and I have had failures trying to flash both NDE63P (a few weeks ago) and NDE63X (today's build).
Additionally, ever since this process has failed for me, I am unable to boot into recovery, I just get the picture of the dead Android guy. So because of this I can't adb sideload the OTA as an alternative.
My bootloader is unlocked and I have rooted just fine, boot_a is listed as my active boot slot, but I have no idea why the system flash keeps failing.
Any thoughts as to why this is happening? Alternatively, is there a way to restore my recovery so I can try adb sideloading the OTA?

ChrisG683 said:
So I'm pretty accustomed to flashing system images and sideloading OTAs, but for some reason things are just not working for me on my Pixel XL.
Every time I run the "flash-all.bat" script (with the -w removed to preserve data) I can never seem to update properly, I get the following:
Code:
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.776s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.064s]
finished. total time: 1.844s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.356s]
writing 'radioa'...
OKAY [ 0.952s]
finished. total time: 2.322s
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.015s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: [removed]
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boota' (26405 KB)...
OKAY [ 0.680s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.139s
Press any key to exit...
I am on the original stock NDE63L, and I have had failures trying to flash both NDE63P (a few weeks ago) and NDE63X (today's build).
Additionally, ever since this process has failed for me, I am unable to boot into recovery, I just get the picture of the dead Android guy. So because of this I can't adb sideload the OTA as an alternative.
My bootloader is unlocked and I have rooted just fine, boot_a is listed as my active boot slot, but I have no idea why the system flash keeps failing.
Any thoughts as to why this is happening? Alternatively, is there a way to restore my recovery so I can try adb sideloading the OTA?
Click to expand...
Click to collapse
update ADB and Fastboot to latest version 1.0.3.6 release

Try the steps in my restore-to-stock thread?
I've used these steps twice for "L" and once for "V" builds.
No issues yet.
http://forum.xda-developers.com/pix...stock-soft-t3494478/post69476498#post69476498
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
Oh, I remember getting that "boota does not exist".
I think I edited the script file somehow to fix that.
Can't remember what it was just now.
---------- Post added at 03:10 PM ---------- Previous post was at 03:09 PM ----------
Yours says "sending 'bootloadera'"
But mine that work says "sending 'bootloader_a'".
That may be the edit I did at one point.
But I have not had to edit anything while using the steps listed in my thread I linked to.

Taebom said:
update ADB and Fastboot to latest version 1.0.3.6 release
Click to expand...
Click to collapse
That seems to have done the trick, thank you so much!

Related

Problem flashing system image

How is everyone else flashing the system images? On the Nexus 6 and Nexus 6p I would just fastboot flash the system, vendor, and boot images, but with the Pixel there are tons of different images so I don't want to manually flash and muff something up.. So I've been trying to run the flash-all.bat and It just keeps giving me errors
C:\android>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32820 KB)...
OKAY [ 0.753s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
OKAY [ 1.017s]
finished. total time: 1.770s
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'radio_a' (57048 KB)...
OKAY [ 1.303s]
writing 'radio_a'...
OKAY [ 0.863s]
finished. total time: 2.166s
rebooting into bootloader...
OKAY [ 0.053s]
finished. total time: 0.069s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
and it just stalls there.....
I've updated everything... drivers, sdk, fastboot and whatnot..
My phone is fine, I just have elementalx and root and I want to revert to stock so I can use android pay and receive updates.
I bought my phone from Google Store and I'm trying to flash the V image if that makes a difference.

Cannot install stock rom: FAILED (remote: data too large)

I tried installing Cyanogenmod on a Nexus 5X, and it didn't work, so now I'm trying to install the stock rom from this site: https://developers.google.com/android/images#bullhead.
I'm doing this on Ubuntu 15.10. When I run the flash-all.sh script (on any of them), I get this output:
target reported max download size of 536870912 bytes
sending 'bootloader' (4382 KB)...
OKAY [ 0.195s]
writing 'bootloader'...
OKAY [ 0.077s]
finished. total time: 0.272s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.715s]
writing 'radio'...
OKAY [ 0.338s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: BHZ10i
Baseband Version.....: M8994F-2.6.22.0.56
Serial Number........: 00a9164559592811
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (11469 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.073s]
sending 'recovery' (12521 KB)...
OKAY [ 0.393s]
writing 'recovery'...
OKAY [ 0.092s]
erasing 'system'...
OKAY [ 0.089s]
sending 'system' (1950236 KB)...
FAILED (remote: data too large)
finished. total time: 1.210s
I'm not seeing many resources online about this error. The only thing I've seen is to update fastboot, but I've already got the latest installed with this ppa: http://askubuntu.com/questions/34702/how-do-i-set-up-android-adb
Is there anything that I can do to get it working correctly?
adanedhel728 said:
I tried installing Cyanogenmod on a Nexus 5X, and it didn't work, so now I'm trying to install the stock rom from this site: https://developers.google.com/android/images#bullhead.
I'm doing this on Ubuntu 15.10. When I run the flash-all.sh script (on any of them), I get this output:
target reported max download size of 536870912 bytes
sending 'bootloader' (4382 KB)...
OKAY [ 0.195s]
writing 'bootloader'...
OKAY [ 0.077s]
finished. total time: 0.272s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.715s]
writing 'radio'...
OKAY [ 0.338s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: BHZ10i
Baseband Version.....: M8994F-2.6.22.0.56
Serial Number........: 00a9164559592811
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (11469 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.073s]
sending 'recovery' (12521 KB)...
OKAY [ 0.393s]
writing 'recovery'...
OKAY [ 0.092s]
erasing 'system'...
OKAY [ 0.089s]
sending 'system' (1950236 KB)...
FAILED (remote: data too large)
finished. total time: 1.210s
I'm not seeing many resources online about this error. The only thing I've seen is to update fastboot, but I've already got the latest installed with this ppa: http://askubuntu.com/questions/34702/how-do-i-set-up-android-adb
Is there anything that I can do to get it working correctly?
Click to expand...
Click to collapse
the system image always is too large and usually it gets transferred in smaller pieces automatically. I'd try to flash all the images manually on a Windows mashine, following this guide (section 10).
I did it many times this way without issues.
ulxerker said:
the system image always is too large and usually it gets transferred in smaller pieces automatically. I'd try to flash all the images manually on a Windows mashine, following this guide (section 10).
I did it many times this way without issues.
Click to expand...
Click to collapse
Well, I can't get it working on Windows at all, because the driver won't install. (At least I assume that's the reason why-- The driver won't install and fastboot won't show any devices.)
I tried fixing that, but with no luck.
I did also try section 10 from Ubuntu, with the same results for the system part:
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.284s]
sending sparse 'system' (514493 KB)...
OKAY [ 12.333s]
writing 'system'...
OKAY [ 3.149s]
sending sparse 'system' (514543 KB)...
OKAY [ 12.427s]
writing 'system'...
OKAY [ 3.117s]
sending sparse 'system' (524291 KB)...
FAILED (remote: data too large)
finished. total time: 31.327s
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
icrunchbanger said:
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
Click to expand...
Click to collapse
My gosh, that finally worked, and I didn't believe it would. I had thought that the one I had gotten from that PPA was the newest, but, apparently not. I actually got it directly from Google (which was a chore in itself, but outside the scope of this thread).
Thank you very much. Now, let's see if I can find out how to mark this as solved...
adanedhel728 said:
My gosh, that finally worked, and I didn't believe it would. I had thought that the one I had gotten from that PPA was the newest, but, apparently not. I actually got it directly from Google (which was a chore in itself, but outside the scope of this thread).
Thank you very much. Now, let's see if I can find out how to mark this as solved...
Click to expand...
Click to collapse
Your welcome. Never trust PPA ?
I got issuse
icrunchbanger said:
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
Click to expand...
Click to collapse
Bro link doesnt work, can you sent me app via email: [email protected]
suleymanov5 said:
Bro link doesnt work, can you sent me app via email: [email protected]
Click to expand...
Click to collapse
You can download android tools from Google
https://dl.google.com/android/repository/platform-tools-latest-linux.zip
Also you can check my github for some nifty scripts .
https://github.com/icrunchbanger/android

Nexus 7 2013 LTE bootloop, can't enter Recovery mode; flash write failure

My Nexus 7 2013 LTE was rooted and updated to stock Android 6.0 a year ago, no 3rd party ROM/recovery is installed. Last week while checking emails, it rebooted suddenly then remained at Google letters and unlock icon, I can enter fastboot mode by pressing power and volume- buttons together, the last line shows status unlocked; then if select "Recovery mode", it reboots then shows a dead robot with an exclamation mark only. I downloaded the latest factory image "razorg-mob30x", connect it to my PC and enter adb command "flash-all.bat" (I modified the bat file by removing -w, so it won't wipe the user data), then it shows: FAILED (remote: flash write failure)
sending 'bootloader' (3915 KB)...
OKAY [ 0.135s]
writing 'bootloader' ...
FAILED (remote: flash write failure)
finished. total time 90.811s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time 0.012s
sending 'radio' (76038 KB)...
OKAY [ 2.393s]
writing 'radio' ...
FAILED (remote: flash write failure)
finished. total time 92.549s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time 0.013s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
----------------------------------------------------
Bootloader Version...: FLO-04.08
Basedband Version...: DEB-Z00_2.44.0_0213
Serial Number................: 0879222a
----------------------------------------------------
checking product...
OKAY [ 0.005s]
checking version-bootloader...
OKAY [ 0.006s]
checking version-baseband...
OKAY [ 0.006s]
sending 'boot' (7422 KB)
OKAY [ 0.243s]
writing 'boot' ...
FAILED (remote: flash write failure)
finished. total time 90.151s
Press any key to exit...
Click to expand...
Click to collapse
What else I can do to resuce my pad? Does this mean the memory is physically damaged?
Please advise. Your help is much appreciated.
Bad motherboard, just had to replace mine with exact issue.

flashing problem, please help.. archive doesnot contain boot.sig, recovery.img...

I meet with problem of flashing. but flash failed.
here is the contain. Android 8.1
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 1.113s]
writing 'bootloader'...
OKAY [ 0.357s]
finished. total time: 1.470s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.818s]
writing 'radio'...
OKAY [ 0.580s]
finished. total time: 2.398s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 2030555488 bytes
error: update package missing system.img
Press any key to exit...
after I open the zip file, there is no recovery.img, boot.sig inside.
failed to allocate 2030555488 bytes
Click to expand...
Click to collapse
I had the same problem with my old Windows desktop which has only 4GB of RAM.
Used my notebook with 8 GB of RAM and it worked
i am facing the same issue
---------- Post added at 03:30 PM ---------- Previous post was at 02:53 PM ----------
check this it seems as normal worked for mw too but had a wait a lot
https://www.reddit.com/r/GooglePixel/comments/5zh8a6/archive_does_not_contain_systemsig/
Don't use this Q/A form, it is a pain in the a$$ and hard to follow. Next time just start a regular thread.
Those two errors are normal but what is not normal is that system was not found. Either you unzipped the 2nd nested zip file in the image (supposed to be left alone) or you are using outdated adb/fastboot binaries. They were updated for Pixel, so older ones won't work.

Error Flashing Latest Update

I've tried to install the latest OTA update (October 2019) without success. I'm rooted and when I try to install the update OTA it either hangs at "Preparing system update" without ever finishing or telling me to try again (I have tried via cell signal or wifi without success).
I tried downloading the latest factory image and flashing that instead without the -w via fastboot and now get the following error:
I have upgraded fastboot (platform-tools) to the latest and still get the same error.
Code:
OKAY [ 0.060s]
checking version-bootloader...
OKAY [ 0.059s]
checking version-baseband...
OKAY [ 0.058s]
sending 'boot_a' (65536 KB)...
OKAY [ 2.840s]
writing 'boot_a'...
OKAY [ 0.714s]
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.400s]
writing 'dtbo_a'...
OKAY [ 0.094s]
sending sparse 'system_a' 1/4 (262140 KB)...
OKAY [ 12.270s]
writing 'system_a' 1/4...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 17.136s
Press any key to exit...
Appreciate any help!
Thanks!
You need to be unrooted to take the OTA. Flash the stock boot image again then you can update. Or just sideload the OTA but either way you'll need to reroot.
I understand the need to unroot to take the OTA but why is it failing when trying to flash the factory image?
Code:
Need help!
I've tried several times to flash the factory image with the same results each time (flash-all without -w). I've downloaded the factory image again to make sure it wasn't corrupted.
I booted into fastboot via ADB and it got me into fastbootd mode and I tried doing flash-all from there but it rebooted back into regular fastboot after flashing the bootloader and failed again with the same error. I rebooted back into fastbootd and did the update command (fastboot update image-bonito-qp1a.191005.007.zip) directly from there and looks like it went through flashing system_a but failed when writing system_b (Operation not allowed). The phone now reports that the phone is corrupt (Your device is corrupt. It can't be trusted and may not work properly). It just displays the Google logo but nothing else happens. I can get to fastboot but unsure how to get past this issue.
Here's the output when flashing the factory image...
Code:
flash-all
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8349 KB)...
OKAY [ 0.691s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b4s4-0.2-5736883
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
OKAY [ 0.607s]
finished. total time: 1.303s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (73196 KB)...
OKAY [ 5.316s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g670-00025-190805-B-5781381
(bootloader) Flashing partition modem_a
OKAY [ 0.469s]
finished. total time: 5.790s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.071s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.583s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.047s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (782 MB) to disk... took 32.955s
archive does not contain 'system.sig'
extracting system_other.img (119 MB) to disk... took 3.449s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
extracting vendor.img (462 MB) to disk... took 19.669s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: b4s4-0.2-5736883
Baseband Version.....: g670-00025-190805-B-5781381
Serial Number........: XXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking version-bootloader...
OKAY [ 0.057s]
checking version-baseband...
OKAY [ 0.057s]
sending 'boot_a' (65536 KB)...
OKAY [ 2.447s]
writing 'boot_a'...
OKAY [ 0.631s]
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.410s]
writing 'dtbo_a'...
OKAY [ 0.109s]
sending sparse 'system_a' 1/4 (262140 KB)...
OKAY [ 7.744s]
writing 'system_a' 1/4...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 12.159s
Press any key to exit...
Appreciate any help!
Damn it. Found the issue. Although I downloaded the latest fastboot and placed it in my usual folder, the PC was still pointing to an old version of fastboot in a different folder.
All is good now.
EDIT - removed ( platform-tools_r31.0.0 )

Categories

Resources