Develop Bugs

Experience 5.2 Update?

The new update is allegedly out. But for me there is no update.
Has anyone a zip or some infos about it?

It's out only for preview program members.

I don't read too well

Out now for everyone now, currently updating now

out now but wont update, just loops for me

ricflairandy said:
out now but wont update, just loops for me
Click to expand...
Click to collapse
Same here, downloads the update, reboots, says its installing, doesn't finish, reboot, back to square one prompting to install.

So happy that it's not just me. I am also having the issue do you think the problem is with the rooted ROMs

jonsharky said:
So happy that it's not just me. I am also having the issue do you think the problem is with the rooted ROMs
Click to expand...
Click to collapse
I don't think so... Just restored with latest factory image, wiping everything and still doesn't work! I have a 2015 16GB model.

On the official shield forums it's been confirmed that the ota update won't work for rooted devices. The flash will be up on developer.nvidia.com in about a week.

JohnRossJennings said:
On the official shield forums it's been confirmed that the ota update won't work for rooted devices. The flash will be up on developer.nvidia.com in about a week.
Click to expand...
Click to collapse
My shield isn't rooted but im getting the same looping problem. I noticed recently though that on boot up my shield says the device is corrupt etc etc as though it has been rooted, but I've not modified anything.maybe this looping update caused that?
Will I need to wait and try and flash a factory image when it comes out?
Sent from my Pixel C using Tapatalk

You can NOT use OTA Updates if you are rooted. END!
The only way back is to factory reset the Shield. In the case of the Pro. This usually means a 2h wait.
Perhaps a quick reset might be enough? Though I have never attempted it before. But simply restoring a Recovery Image won't overwrite the /system Partition, clearing out the remnants of root. Thus allowing you to then update.

adam_purkis said:
My shield isn't rooted but im getting the same looping problem. I noticed recently though that on boot up my shield says the device is corrupt etc etc as though it has been rooted, but I've not modified anything.maybe this looping update caused that?
Will I need to wait and try and flash a factory image when it comes out?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Hi , i am new , having 2015 model
i getting a boot looping when updating and now stay at Nvida Logo page , can you or members here help me how to flash back 5.1 ?
sorry to trouble you.
thank you

Also, the update will definitely not take with TWRP. Looks like I have to wait until the developer release.

chow9229 said:
Hi , i am new , having 2015 model
i getting a boot looping when updating and now stay at Nvida Logo page , can you or members here help me how to flash back 5.1 ?
sorry to trouble you.
thank you
Click to expand...
Click to collapse
Hi, sorry can't give you detailed instructions right now. You'll find the info but a word of advice: Flash manually command by command in fastboot, DO NOT use the flash-all.bat and if you had 5.1 previously then there is no need to flash the bootloader (blob file). You need to be careful with that file, most hard bricks are caused by corrupted bootloader. Pay attention when downloading the Nvidia recovery image, make sure you get the one for your specific device model.
Cheers.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player

lavero.burgos said:
Hi, sorry can't give you detailed instructions right now. You'll find the info but a word of advice: Flash manually command by command in fastboot, DO NOT use the flash-all.bat and if you had 5.1 previously then there is no need to flash the bootloader (blob file). You need to be careful with that file, most hard bricks are caused by corrupted bootloader. Pay attention when downloading the Nvidia recovery image, make sure you get the one for your specific device model.
Cheers.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Click to expand...
Click to collapse
Hi , here my flash details
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 67108864 bytes
sending 'recovery' (13698 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 0.580s]
finished. total time: 0.958s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 67108864 bytes
sending 'boot' (10288 KB)...
OKAY [ 0.254s]
writing 'boot'...
OKAY [ 0.453s]
finished. total time: 0.712s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 67108864 bytes
erasing 'system'...
OKAY [ 0.347s]
sending sparse 'system' 1/31 (62437 KB)...
OKAY [ 1.594s]
writing 'system' 1/31...
OKAY [ 2.723s]
sending sparse 'system' 2/31 (62993 KB)...
OKAY [ 1.622s]
writing 'system' 2/31...
OKAY [ 2.720s]
sending sparse 'system' 3/31 (65443 KB)...
OKAY [ 1.810s]
writing 'system' 3/31...
OKAY [ 3.066s]
sending sparse 'system' 4/31 (65512 KB)...
OKAY [ 1.651s]
writing 'system' 4/31...
OKAY [ 2.788s]
sending sparse 'system' 5/31 (65532 KB)...
OKAY [ 1.671s]
writing 'system' 5/31...
OKAY [ 2.674s]
sending sparse 'system' 6/31 (63893 KB)...
OKAY [ 1.635s]
writing 'system' 6/31...
OKAY [ 2.673s]
sending sparse 'system' 7/31 (58260 KB)...
OKAY [ 1.475s]
writing 'system' 7/31...
OKAY [ 2.320s]
sending sparse 'system' 8/31 (59088 KB)...
OKAY [ 1.502s]
writing 'system' 8/31...
OKAY [ 2.355s]
sending sparse 'system' 9/31 (65533 KB)...
OKAY [ 1.680s]
writing 'system' 9/31...
OKAY [ 2.747s]
sending sparse 'system' 10/31 (64176 KB)...
OKAY [ 1.622s]
writing 'system' 10/31...
OKAY [ 2.494s]
sending sparse 'system' 11/31 (58956 KB)...
OKAY [ 1.504s]
writing 'system' 11/31...
OKAY [ 2.454s]
sending sparse 'system' 12/31 (65532 KB)...
OKAY [ 1.652s]
writing 'system' 12/31...
OKAY [ 2.736s]
sending sparse 'system' 13/31 (60898 KB)...
OKAY [ 1.555s]
writing 'system' 13/31...
OKAY [ 2.704s]
sending sparse 'system' 14/31 (62455 KB)...
OKAY [ 1.627s]
writing 'system' 14/31...
OKAY [ 2.751s]
sending sparse 'system' 15/31 (65532 KB)...
OKAY [ 1.707s]
writing 'system' 15/31...
OKAY [ 2.698s]
sending sparse 'system' 16/31 (65532 KB)...
OKAY [ 1.667s]
writing 'system' 16/31...
OKAY [ 2.690s]
sending sparse 'system' 17/31 (61848 KB)...
OKAY [ 1.551s]
writing 'system' 17/31...
OKAY [ 2.666s]
sending sparse 'system' 18/31 (61428 KB)...
OKAY [ 1.498s]
writing 'system' 18/31...
OKAY [ 2.491s]
sending sparse 'system' 19/31 (65532 KB)...
OKAY [ 1.650s]
writing 'system' 19/31...
OKAY [ 2.736s]
sending sparse 'system' 20/31 (65533 KB)...
OKAY [ 1.677s]
writing 'system' 20/31...
OKAY [ 2.791s]
sending sparse 'system' 21/31 (63217 KB)...
OKAY [ 1.610s]
writing 'system' 21/31...
OKAY [ 2.736s]
sending sparse 'system' 22/31 (65533 KB)...
OKAY [ 1.671s]
writing 'system' 22/31...
OKAY [ 2.857s]
sending sparse 'system' 23/31 (65053 KB)...
OKAY [ 1.714s]
writing 'system' 23/31...
OKAY [ 2.962s]
sending sparse 'system' 24/31 (65534 KB)...
OKAY [ 1.746s]
writing 'system' 24/31...
OKAY [ 3.063s]
sending sparse 'system' 25/31 (63170 KB)...
OKAY [ 1.623s]
writing 'system' 25/31...
OKAY [ 2.748s]
sending sparse 'system' 26/31 (60468 KB)...
OKAY [ 1.535s]
writing 'system' 26/31...
OKAY [ 2.602s]
sending sparse 'system' 27/31 (64617 KB)...
OKAY [ 1.618s]
writing 'system' 27/31...
OKAY [ 2.686s]
sending sparse 'system' 28/31 (65532 KB)...
OKAY [ 1.626s]
writing 'system' 28/31...
OKAY [ 2.682s]
sending sparse 'system' 29/31 (65532 KB)...
OKAY [ 1.644s]
writing 'system' 29/31...
OKAY [ 2.773s]
sending sparse 'system' 30/31 (65532 KB)...
OKAY [ 1.653s]
writing 'system' 30/31...
OKAY [ 2.734s]
sending sparse 'system' 31/31 (16061 KB)...
OKAY [ 0.496s]
writing 'system' 31/31...
OKAY [ 0.808s]
finished. total time: 131.663s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata.img
target reported max download size of 67108864 bytes
erasing 'userdata'...
OKAY [ 1.750s]
sending sparse 'userdata' 1/3 (65532 KB)...
OKAY [ 1.644s]
writing 'userdata' 1/3...
OKAY [ 2.672s]
sending sparse 'userdata' 2/3 (65532 KB)...
OKAY [ 1.617s]
writing 'userdata' 2/3...
OKAY [ 2.620s]
sending sparse 'userdata' 3/3 (5158 KB)...
OKAY [ 0.182s]
writing 'userdata' 3/3...
OKAY [ 0.386s]
finished. total time: 10.884s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash staging blob
target reported max download size of 67108864 bytes
sending 'staging' (3443 KB)...
OKAY [ 0.100s]
writing 'staging'...
OKAY [ 0.175s]
finished. total time: 0.278s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem dtbname
...
(bootloader) tegra210-foster-e-p2530-0930-e02-00.dtb
OKAY [ 0.006s]
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dtb tegra210-foster-e-p2530-0930-e02-00.dtb
error: cannot load 'tegra210-foster-e-p2530-0930-e02-00.dtb'
So i stuck at DTB flash, then i just fast reboot and it back alive, but it back factory default my SSD 500GB storage all gone.
I need to be reformat, remount as storage again and reinstall applications again. I also upgraded to 5.2 too.
just don't know why this update have problem, previously 3 updates (since june 2016) all no issue,
moreover this 5.2 update is the smallest files (140+MB) size compare to the other 3 updates.
can someone explain why? hopefully the next update it would not happen again.
I rather prefer big size file update then this.
BTW i wish to thanks everyone here share and help.
Thank You

I unrooted and still couldn't update. Factory reset did nothing.

adam_purkis said:
My shield isn't rooted but im getting the same looping problem. I noticed recently though that on boot up my shield says the device is corrupt etc etc as though it has been rooted, but I've not modified anything.maybe this looping update caused that?
Will I need to wait and try and flash a factory image when it comes out?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Did you unlock bootloader? If so that is why you are getting the device is corrupt message...

chow9229 said:
just don't know why this update have problem, previously 3 updates (since june 2016) all no issue,
moreover this 5.2 update is the smallest files (140+MB) size compare to the other 3 updates.
can someone explain why? hopefully the next update it would not happen again.
I rather prefer big size file update then this.
BTW i wish to thanks everyone here share and help.
Thank You
Click to expand...
Click to collapse
This update was different, it is a progressive update and it is the first time nvidia do that.
Enviado desde mi Redmi Note 4 mediante Tapatalk

AndroidUser00110001 said:
Did you unlock bootloader? If so that is why you are getting the device is corrupt message...
Click to expand...
Click to collapse
Nope didn't unlock anything it's fully stock and only bought it about 3 weeks ago.
If I flash the factory rom when they release it do you think that will help?
Sent from my D6503 using Tapatalk

adam_purkis said:
Nope didn't unlock anything it's fully stock and only bought it about 3 weeks ago.
If I flash the factory rom when they release it do you think that will help?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Yes, most likely but are you able to boot into 5.1 system and use your shield normally?.

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.

Pixel XL fails to flash stock rom

Hello,
i have a Pixel XL which i have just purchased second hand. The previous owner flashed the Android P beta and i wanted to restore to the last Oreo.
Started skipsoft tool and chose to restore to stock, device found and flash starts but always fails to finish with the following status. The stock Rom i am trying to flash was downloaded from official sources. Any ideas what to try?
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1711291800
Baseband Version.....: 8996-130091-1802061512
Serial Number........: HT69T0XXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.047s]
checking version-baseband...
OKAY [ 0.045s]
sending 'boot_b' (30177 KB)...
OKAY [ 0.748s]
writing 'boot_b'...
OKAY [ 0.608s]
erasing 'system_b'...
OKAY [ 1.091s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 12.765s]
writing 'system_b' 1/4...
OKAY [ 3.989s]
sending sparse 'system_b' 2/4 (524284 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 32.709s

Make sure your SDK (ADB, fastboot) is up to date.
Is the phone in working condition?

Is the bootloader unlocked?

jiggly cable dude,replace cable before flashing again cause u could brick it.Device fine!

Well that data partition could be corrupt. I would suggest wiping date then try to reflash the factory image. If the data won't wipe you might have a bad emmc

dosada said:
Hello,
i have a Pixel XL which i have just purchased second hand. The previous owner flashed the Android P beta and i wanted to restore to the last Oreo.
Started skipsoft tool and chose to restore to stock, device found and flash starts but always fails to finish with the following status. The stock Rom i am trying to flash was downloaded from official sources. Any ideas what to try?
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1711291800
Baseband Version.....: 8996-130091-1802061512
Serial Number........: HT69T0XXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.047s]
checking version-baseband...
OKAY [ 0.045s]
sending 'boot_b' (30177 KB)...
OKAY [ 0.748s]
writing 'boot_b'...
OKAY [ 0.608s]
erasing 'system_b'...
OKAY [ 1.091s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 12.765s]
writing 'system_b' 1/4...
OKAY [ 3.989s]
sending sparse 'system_b' 2/4 (524284 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 32.709s
Click to expand...
Click to collapse
DR3W5K1 said:
Well that data partition could be corrupt. I would suggest wiping date then try to reflash the factory image. If the data won't wipe you might have a bad emmc
Click to expand...
Click to collapse
Is the device 128gb? If so refer to this post by me.
https://forum.xda-developers.com/showpost.php?p=76710445&postcount=23

i would go to developers.google.com and download and flash-all the the latest rom. if that doesn't work fastboot boot twrp.img and goto Wipe -Format Data .

DR3W5K1 said:
Make sure your SDK (ADB, fastboot) is up to date.
Is the phone in working condition?
Click to expand...
Click to collapse
I'm going to second this. I could not flash back to June 8.1 factory from the P beta without updating my ADB and Fastboot to the latest google provides.
I had the latest "Minimal ADB and Fastboot" from XDA and that was not working at all - lots of errors thrown.

dosada said:
Hello,
i have a Pixel XL which i have just purchased second hand. The previous owner flashed the Android P beta and i wanted to restore to the last Oreo.
Started skipsoft tool and chose to restore to stock, device found and flash starts but always fails to finish with the following status. The stock Rom i am trying to flash was downloaded from official sources. Any ideas what to try?
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1711291800
Baseband Version.....: 8996-130091-1802061512
Serial Number........: HT69T0XXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.047s]
checking version-baseband...
OKAY [ 0.045s]
sending 'boot_b' (30177 KB)...
OKAY [ 0.748s]
writing 'boot_b'...
OKAY [ 0.608s]
erasing 'system_b'...
OKAY [ 1.091s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 12.765s]
writing 'system_b' 1/4...
OKAY [ 3.989s]
sending sparse 'system_b' 2/4 (524284 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 32.709s
Click to expand...
Click to collapse
I had a similar issue and it started with release of May image and no matter what i did with cable changes like mentioned or using a different pc or using a different usb port or updating to latest fastboot/adb ... switching slots.. i could not flash the full image with -w removed.. i went back and reverted to April full image ... I have not yet tried June but my guess is it will be similiar result with failing on that exact spot as you mentioned. Same exact error.
---------- Post added at 08:40 PM ---------- Previous post was at 08:00 PM ----------
firefly777 said:
I had a similar issue and it started with release of May image and no matter what i did with cable changes like mentioned or using a different pc or using a different usb port or updating to latest fastboot/adb ... switching slots.. i could not flash the full image with -w removed.. i went back and reverted to April full image ... I have not yet tried June but my guess is it will be similiar result with failing on that exact spot as you mentioned. Same exact error.
Click to expand...
Click to collapse
Here's what i did to get past this error so maybe worth a try.. as i mentioned above i reverted to April i flashed slot B with full image ... no data wipes in any of this btw.. so i removed -w from flash-all
i let it do its thing and reboot
i switched to slot A and again did the april flash all no data wipes (remove -w)
then i tried the june full image again no data wipes (remove -w) and voila it finally worked.. so try that to see if it works for you.
no data wipe needed.
flash april full image (remove -w) to both slot b and slot a
keep it on slot a
flash june full image (remove -w)
so up to now i had always flashed only to active slot and not both but with this trick it worked for June as well but first start with April. hope that works for you too bud

[Help] Trying to return to stock

So I've been on the original stable Q build and haven't updated since. Recently I've been getting the popup saying its time to update. The bottom option is always remind me later. Yesterday it popped up and i auto clicked the bottom one, however the "remind me later" wasn't there and i ended up clicking "update at 2am". 2am, update, lost root.
I know you can do the boot.img patch but i decided to do a clean install. So i downloaded the full december factory image and did the following,
Cd to platform-tools, - Adb reboot bootloader, - Flash-all.bat
Reboots to bootloader_b, everything works good, until it tries writing the system. I get
checking product...
OKAY [ 0.060s]
checking version-bootloader...
OKAY [ 0.059s]
checking version-baseband...
OKAY [ 0.084s]
sending 'boot_b' (65536 KB)...
OKAY [ 1.486s]
writing 'boot_b'...
OKAY [ 0.686s]
sending sparse 'system_b' 1/4 (262140 KB)...
OKAY [ 6.110s]
writing 'system_b' 1/4...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 8.813s
Press any key to exit...
After everything it writes the fastboot screen goes dark and comes back before it writes something else. Did i miss a command? Magisk manager doesn't give me the option for full uninstall either so, i figured it'd be easier to just go back to stock and root from there.
Any help or suggestions would be appreciated.

MOD ACTION:
Update of platform tools solved the issue as reported by OP. Thread closed at his request.

Problems flashing a clean crosshatch 10 AOSP build to Pixel3XL

So, I just got a Pixel3 XL and am trying to build and flash my own clean AOSP build (as a starting point). I'm pretty technical, but new to the ROM world. (Would have posted in the ROM sub-forum, but my acct is brand new, if a mod wants to move it, cool.)
After successfully building, I'm getting an error halfway through running fastboot flashall now, after the reboot. Has anyone hit an error at Writing 'product_a'?
For my setup, I basically followed this awesome guide by @codevalley : https://forum.xda-developers.com/pixel-3/how-to/noobs-guide-to-building-aosp-scratch-t4012293
Since it was a new phone, the additional steps I had to do were:
* Connect to network in order to enable OEM unlock
* install the right drivers so fastboot would work, not just adb
* re-flash the OEM firmware, otherwise fastboot fails right away
The only oddball thing about my setup is that I'm building in an ubuntu VM and flashing it from windows after copying the whole target/product directory over.
Code:
C:\android-target\target\product\crosshatch>fastboot flashall
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 95FY1XXXX
--------------------------------------------
Checking 'product' OKAY [ 0.044s]
Setting current slot to 'a' OKAY [ 0.512s]
Sending 'boot_a' (65536 KB) OKAY [ 0.432s]
Writing 'boot_a' OKAY [ 0.400s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_a' OKAY [ 0.087s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.099s]
Writing 'vbmeta_a' OKAY [ 0.039s]
Rebooting into fastboot OKAY [ 0.045s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.009s]
Sending 'product_a' (299008 KB) OKAY [ 1.783s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Anyone got any thoughts? Googling this error is really not turning up much....

sam_242 said:
So, I just got a Pixel3 XL and am trying to build and flash my own clean AOSP build (as a starting point). I'm pretty technical, but new to the ROM world. (Would have posted in the ROM sub-forum, but my acct is brand new, if a mod wants to move it, cool.)
After successfully building, I'm getting an error halfway through running fastboot flashall now, after the reboot. Has anyone hit an error at Writing 'product_a'?
For my setup, I basically followed this awesome guide by @codevalley : https://forum.xda-developers.com/pixel-3/how-to/noobs-guide-to-building-aosp-scratch-t4012293
Since it was a new phone, the additional steps I had to do were:
* Connect to network in order to enable OEM unlock
* install the right drivers so fastboot would work, not just adb
* re-flash the OEM firmware, otherwise fastboot fails right away
The only oddball thing about my setup is that I'm building in an ubuntu VM and flashing it from windows after copying the whole target/product directory over.
Code:
C:\android-target\target\product\crosshatch>fastboot flashall
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 95FY1XXXX
--------------------------------------------
Checking 'product' OKAY [ 0.044s]
Setting current slot to 'a' OKAY [ 0.512s]
Sending 'boot_a' (65536 KB) OKAY [ 0.432s]
Writing 'boot_a' OKAY [ 0.400s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_a' OKAY [ 0.087s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.099s]
Writing 'vbmeta_a' OKAY [ 0.039s]
Rebooting into fastboot OKAY [ 0.045s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.009s]
Sending 'product_a' (299008 KB) OKAY [ 1.783s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Anyone got any thoughts? Googling this error is really not turning up much....
Click to expand...
Click to collapse
The only thing I see is that it is only flashing to slot_a. It is my understanding that you need to flash to both partitions a and b before the process will work. For me it has only worked when I flashed to both partitions. Also adding .\ before the command may help. For some reason it only flashes for me when I add it.
Sent from my Pixel 3 XL

Does the AOSP build process generate full OTA images similar to what are found here: https://developers.google.com/android/ota?
If so, try flashing just the bootloader in fastboot, boot into recovery, and sideload the full OTA.

sam_242 said:
So, I just got a Pixel3 XL and am trying to build and flash my own clean AOSP build (as a starting point). I'm pretty technical, but new to the ROM world. (Would have posted in the ROM sub-forum, but my acct is brand new, if a mod wants to move it, cool.)
After successfully building, I'm getting an error halfway through running fastboot flashall now, after the reboot. Has anyone hit an error at Writing 'product_a'?
For my setup, I basically followed this awesome guide by @codevalley : https://forum.xda-developers.com/pixel-3/how-to/noobs-guide-to-building-aosp-scratch-t4012293
Since it was a new phone, the additional steps I had to do were:
* Connect to network in order to enable OEM unlock
* install the right drivers so fastboot would work, not just adb
* re-flash the OEM firmware, otherwise fastboot fails right away
The only oddball thing about my setup is that I'm building in an ubuntu VM and flashing it from windows after copying the whole target/product directory over.
Code:
C:\android-target\target\product\crosshatch>fastboot flashall
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 95FY1XXXX
--------------------------------------------
Checking 'product' OKAY [ 0.044s]
Setting current slot to 'a' OKAY [ 0.512s]
Sending 'boot_a' (65536 KB) OKAY [ 0.432s]
Writing 'boot_a' OKAY [ 0.400s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_a' OKAY [ 0.087s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.099s]
Writing 'vbmeta_a' OKAY [ 0.039s]
Rebooting into fastboot OKAY [ 0.045s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.009s]
Sending 'product_a' (299008 KB) OKAY [ 1.783s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Anyone got any thoughts? Googling this error is really not turning up much....
Click to expand...
Click to collapse
I had this exact error running fastboot from shell on a Chromebook. Simply booting into the full Ubuntu installation I had installed on the Chromebook allowed me to flash.
I believed in my case the error was due to running out of memory. Though using an old fastboot version or a c -> c cable could also cause trouble.
You can also manually flash partitions instead of using the script. Remember, to get to fastbootd, you have to "fastboot reboot fastboot" from the bootloader.

ktmom said:
Though using an old fastboot version or a c -> c cable could also cause trouble.
Click to expand...
Click to collapse
Both of these are good points. You wouldn't think a USB-C to USB-C cable could cause fastboot problems but I've experienced this first hand. I can't quite remember the error I had, but I couldn't flash the stock factory images while using a USB-C to C cable. Switching to a USB-A to C cable (USB 2.0) resolved it.