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
Related
I've never experienced the fastboot error below and I am not sure about how to proceed.
The error is on the third to last line.
I am attempting to flash the Google factory image: yakju-jwr66y-factory-09207065
to my maguro.
Code:
sending 'bootloader' (2308 KB)...
OKAY [ 0.224s]
writing 'bootloader'...
OKAY [ 0.290s]
finished. total time: 0.518s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: 0149BD310A01D011
--------------------------------------------
checking product...
OKAY [ 0.008s]
sending 'boot' (4376 KB)...
OKAY [ 0.416s]
writing 'boot'...
OKAY [ 0.526s]
sending 'recovery' (4924 KB)...
OKAY [ 0.468s]
writing 'recovery'...
OKAY [ 0.600s]
erasing 'system'...
OKAY [ 0.018s]
sending 'system' (479248 KB)...
OKAY [ 44.424s]
writing 'system'...
[B][COLOR="Red"]FAILED (remote: Write Fail)[/COLOR][/B]
finished. total time: 46.532s
Press any key to exit...
Edit:
I locked and then unlocked the bootloader and re-downloaded and verified the factory image before flashing. After doing this I was able to successfully flash the factory image.
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!
Please explain throughly and provide the download links, I've only had an android for a month and I am still learning the OS / Phone
tryfont said:
Please explain throughly and provide the download links, I've only had an android for a month and I am still learning the OS / Phone
Click to expand...
Click to collapse
Third post in the thread below. Just get the 7.1.2 full image instead of the 7.1.1 I mention in that post.
Pay attention to removing the -w from the flashall bat file. That is the key to saving your data.
And second to the last post in the thread are the instructions for getting root back.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
SOLVED
TonikJDK said:
Third post in the thread below. Just get the 7.1.2 full image instead of the 7.1.1 I mention in that post.
Pay attention to removing the -w from the flashall bat file. That is the key to saving your data.
And second to the last post in the thread are the instructions for getting root back.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
I'm on a mac, not sure how to do the last step with running the .bat file
Edit: went into the bat file and ran the equivalent commands in terminal
(fastboot flash bootloader bootloader-marlin-8996-012001-1702151126.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-marlin-n2g47e.zip)
Here is the terminal messages I got
Last login: Mon Apr 3 18:00:13 on ttys000
Tryfons-MBP:~ tryfon$ cd /Users/tryfon/Desktop/platform-tools
Tryfons-MBPlatform-tools tryfon$ ./fastboot flash bootloader bootloader-marlin-8996-012001-1702151126.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32380 KB)...
OKAY [ 0.811s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.163s]
finished. total time: 4.974s
Tryfons-MBPlatform-tools tryfon$ fastboot reboot-bootloader
-bash: fastboot: command not found
Tryfons-MBPlatform-tools tryfon$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
Tryfons-MBPlatform-tools tryfon$ fastboot flash radio radio-marlin-8996-012901-1702171013.img
-bash: fastboot: command not found
Tryfons-MBPlatform-tools tryfon$ ./fastboot flash radio radio-marlin-8996-012901-1702171013.img
target reported max download size of 536870912 bytes
sending 'radio_b' (57240 KB)...
OKAY [ 1.444s]
writing 'radio_b'...
OKAY [ 0.704s]
finished. total time: 2.148s
Tryfons-MBPlatform-tools tryfon$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
Tryfons-MBPlatform-tools tryfon$ ./fastboot update image-marlin-n2g47e.zip
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'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: 8996-012001-1702151126
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT72A0200395
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_b' (25997 KB)...
OKAY [ 0.701s]
writing 'boot_b'...
OKAY [ 0.260s]
erasing 'system_b'...
OKAY [ 0.457s]
sending sparse 'system_b' 1/4 (514854 KB)...
OKAY [ 14.106s]
writing 'system_b' 1/4...
OKAY [ 6.005s]
sending sparse 'system_b' 2/4 (524140 KB)...
OKAY [ 14.606s]
writing 'system_b' 2/4...
OKAY [ 4.937s]
sending sparse 'system_b' 3/4 (512784 KB)...
OKAY [ 14.072s]
writing 'system_b' 3/4...
OKAY [ 6.243s]
sending sparse 'system_b' 4/4 (32756 KB)...
OKAY [ 0.905s]
writing 'system_b' 4/4...
OKAY [ 0.297s]
erasing 'system_a'...
OKAY [ 0.411s]
sending sparse 'system_a' 1/4 (520579 KB)...
OKAY [ 13.904s]
writing 'system_a' 1/4...
OKAY [ 3.787s]
sending sparse 'system_a' 2/4 (521193 KB)...
OKAY [ 13.721s]
writing 'system_a' 2/4...
OKAY [ 4.103s]
sending sparse 'system_a' 3/4 (510216 KB)...
OKAY [ 14.206s]
writing 'system_a' 3/4...
OKAY [ 3.788s]
sending sparse 'system_a' 4/4 (128745 KB)...
OKAY [ 3.513s]
writing 'system_a' 4/4...
OKAY [ 1.049s]
erasing 'vendor_b'...
OKAY [ 0.154s]
sending 'vendor_b' (242238 KB)...
OKAY [ 6.003s]
writing 'vendor_b'...
OKAY [ 3.653s]
Setting current slot to 'b'...
OKAY [ 0.087s]
rebooting...
finished. total time: 131.364s
Tryfons-MBPlatform-tools tryfon$
Everything turned out fine!!!
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.
From the start: I was previously running the PixelDust ROM and wanted to try the 11 preview so i attempted to flash it via ADB commands. Script ran through the first time and finished overall but had some failed parts under the formatting section and rewriting partitions. With the first time using it i did forget to take out the -W string, well i purposely left it as i dont mind resetting the phone. Fast forward 8 hours, my phone still wont boot past the white google screen after NUMEROUS retries with flashing the 11 preview through ADB as well as using the flash-all. It also now shows the RED "your device is corrupted" screen on initial boot (not the standard yellow warning after unlocking) and seems like it bootloops to the bootloader or google screen and stays there. ANY help greatly appreciated.
Currently trying to use the Deuces flash-all script and latest version of Android 10. Will report
Welcome to Deuces Flashing Script!
v5.0-Windows
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
fastboot version eac51f2bb6a8-android
Fastboot Detected!
Checking if device is detected via Fastboot.
Device Detected in Fastboot!
Are you SURE you want to continue?
Press Enter to continue...:
This tool will reformat partitions in your device!
It will attempt to keep your user data!
Data could be lost! - Use At Your Own Risk!
Continue? (y/N) y
Checking if bootloader is unlocked.
Look at device to confirm if script is waiting...
Preparing files for flash...
Extracting C:\Users\Tiffany\Downloads\Deuces-Bootloop-Recovery-Flashing-Script-master\Deuces-Bootloop-Recovery-Flashing-Script-master\taimen110.zip...
target reported max download size of 536870912 bytes
sending 'bootloader' (36356 KB)...
OKAY [ 0.940s]
writing 'bootloader'...
OKAY [ 0.388s]
finished. total time: 1.412s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 0.576s]
finished. total time: 2.198s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.008s
Extracting C:\Users\Tiffany\Downloads\Deuces-Bootloop-Recovery-Flashing-Script-master\Deuces-Bootloop-Recovery-Flashing-Script-master\_work\taimen-qq2a.200501.001.b3\image-taimen-qq2a.200501.001.b3.zip.
Flashing B-Slot items first.
target reported max download size of 536870912 bytes
erasing 'system_b'...
OKAY [ 0.033s]
sending 'system_b' (313556 KB)...
OKAY [ 8.515s]
writing 'system_b'...
OKAY [ 1.475s]
finished. total time: 10.358s
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.086s]
writing 'boot'...
OKAY [ 0.372s]
finished. total time: 1.462s
target reported max download size of 536870912 bytes
sending 'dtbo' (8192 KB)...
OKAY [ 0.217s]
writing 'dtbo'...
OKAY [ 0.079s]
finished. total time: 0.302s
target reported max download size of 536870912 bytes
sending sparse 'system' (524284 KB)...
OKAY [ 26.436s]
writing 'system'...
OKAY [ 2.457s]
sending sparse 'system' (524284 KB)...
OKAY [ 25.678s]
writing 'system'...
OKAY [ 2.472s]
sending sparse 'system' (524284 KB)...
OKAY [ 24.613s]
writing 'system'...
OKAY [ 2.464s]
sending sparse 'system' (524284 KB)...
OKAY [ 25.794s]
writing 'system'...
OKAY [ 2.462s]
sending sparse 'system' (340260 KB)...
OKAY [ 15.858s]
writing 'system'...
OKAY [ 1.593s]
finished. total time: 129.943s
target reported max download size of 536870912 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.004s]
writing 'vbmeta'...
OKAY [ 0.006s]
finished. total time: 0.012s
target reported max download size of 536870912 bytes
sending 'vendor' (349176 KB)...
OKAY [ 9.269s]
writing 'vendor'...
OKAY [ 1.645s]
finished. total time: 10.922s
Format UserData? (y/N) n
Done!
Press Enter to continue...:
Android 10 worked....