solved.
end
Now I cant boot to any image.
Code:
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.488s]
booting...
FAILED (remote: Error calling AvbLoadAndVerifyBootImages Load Error)
finished. total time: 1.861s
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.486s]
booting...
FAILED (remote: Error calling AvbLoadAndVerifyBootImages Load Error)
finished. total time: 1.860s
Flaah all is required man
you also need to update to the latest platform-tools
I had the same problem doing flash-all
masri1987 said:
you also need to update to the latest platform-tools
I had the same problem doing flash-all
Click to expand...
Click to collapse
This did it for me as well. I was using choco to install it on windows, but its stuck on v26. I don't think scoop had a newer version either. https://developer.android.com/studio/releases/platform-tools
download sdk platform tools and factory image and unzip the factory image into the platform tools folder and run flash all.bat
masri1987 said:
you also need to update to the latest platform-tools
I had the same problem doing flash-all
Click to expand...
Click to collapse
I've been fighting with this for 3 hours and never thought to try this.....I was using ADB from 2017, wondering why the flash commands weren't working right. D'oh!!!! Thank you so much!
jcmills4 said:
I've been fighting with this for 3 hours and never thought to try this.....I was using ADB from 2017, wondering why the flash commands weren't working right. D'oh!!!! Thank you so much!
Click to expand...
Click to collapse
no worries man glad you combed the thread and found the answer
J32A said:
download sdk platform tools and factory image and unzip the factory image into the platform tools folder and run flash all.bat
Click to expand...
Click to collapse
I'm in the same situation and whenever I try to flash all I get this
finished. total time: 0.071s
extracting android-info.txt (0 MB)...
extracting boot.img (64 MB)...
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)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2157 MB)...
And it fails everytime
Any idea what I'm doing wrong?
mrnovanova said:
I'm in the same situation and whenever I try to flash all I get this
finished. total time: 0.071s
extracting android-info.txt (0 MB)...
extracting boot.img (64 MB)...
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)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2157 MB)...
And it fails everytime
Any idea what I'm doing wrong?
Click to expand...
Click to collapse
Do you have the latest sdk tools and fastboot? That's probably the problem.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Do you have the latest sdk tools and fastboot? That's probably the problem.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sorry to resurrect an old thread but I'm getting these exact messages when flashing a google image and I do have the latest platform tools and fastboot drivers. I'm unlocked and rooted. I was in the process of flashing a rom so I tried to Wipe/Advanced Wipe : Dalvik / ART Cache, System and Data (all but internal storage), I got error mkfs.fat process ended with error 1. unable to wipe storage, unable to wipe /auto00.
Thoughts?
spuri78 said:
Sorry to resurrect an old thread but I'm getting these exact messages when flashing a google image and I do have the latest platform tools and fastboot drivers. I'm unlocked and rooted. I was in the process of flashing a rom so I tried to Wipe/Advanced Wipe : Dalvik / ART Cache, System and Data (all but internal storage), I got error mkfs.fat process ended with error 1. unable to wipe storage, unable to wipe /auto00.
Thoughts?
Click to expand...
Click to collapse
I am currently in the same situation as you. Let me know if you manage to get it sorted.
Segnale007 said:
I am currently in the same situation as you. Let me know if you manage to get it sorted.
Click to expand...
Click to collapse
so you getting these messages when flashing a google image as well?
extracting boot.img (64 MB) to disk... took 0.222s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.022s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
extracting product.img (194 MB) to disk... took 0.629s
archive does not contain 'product.sig'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2158 MB) to disk... took 11.435s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 2.597s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 2.356s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
spuri78 said:
so you getting these messages when flashing a google image as well?
extracting boot.img (64 MB) to disk... took 0.222s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.022s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
extracting product.img (194 MB) to disk... took 0.629s
archive does not contain 'product.sig'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2158 MB) to disk... took 11.435s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 2.597s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 2.356s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Click to expand...
Click to collapse
So far I have only been trying to restore TWRP but I am getting the following
Code:
[email protected] ~ $ fastboot flash recovery Downloads/twrp-3.2.3-3-crosshatch.img
Sending 'recovery' (65536 KB) OKAY [ 1.790s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
Finished. Total time: 2.229s
fastboot boot Downloads/twrp-3.2.3-3-crosshatch.img
Downloading 'boot.img' OKAY [ 1.750s]
booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
Finished. Total time: 1.869s
I will try and re-flash the bootloader now. Hopefully it will let me.
---------- Post added at 10:08 AM ---------- Previous post was at 09:56 AM ----------
Segnale007 said:
So far I have only been trying to restore TWRP but I am getting the following
Code:
[email protected] ~ $ fastboot flash recovery Downloads/twrp-3.2.3-3-crosshatch.img
Sending 'recovery' (65536 KB) OKAY [ 1.790s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
Finished. Total time: 2.229s
fastboot boot Downloads/twrp-3.2.3-3-crosshatch.img
Downloading 'boot.img' OKAY [ 1.750s]
booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
Finished. Total time: 1.869s
I will try and re-flash the bootloader now. Hopefully it will let me.
Click to expand...
Click to collapse
Flashing entire crosshatch-pq1a.181205.006-factory-96b23504.zip did the trick for me. Apparently phone doesn't like you to wipe /vendor. Good luck
spuri78 said:
so you getting these messages when flashing a google image as well?
extracting boot.img (64 MB) to disk... took 0.222s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.022s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
extracting product.img (194 MB) to disk... took 0.629s
archive does not contain 'product.sig'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2158 MB) to disk... took 11.435s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 2.597s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 2.356s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Click to expand...
Click to collapse
Did you stop it at the last 'File system type raw not supported'? If yes let it run until it stops.
Homeboy76 said:
Did you stop it at the last 'File system type raw not supported'? If yes let it run until it stops.
Click to expand...
Click to collapse
No, I didn't stop it. I only copied this bit as it had the 'not supported'.
---------- Post added at 11:29 AM ---------- Previous post was at 11:29 AM ----------
Segnale007 said:
So far I have only been trying to restore TWRP but I am getting the following
Code:
[email protected] ~ $ fastboot flash recovery Downloads/twrp-3.2.3-3-crosshatch.img
Sending 'recovery' (65536 KB) OKAY [ 1.790s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
Finished. Total time: 2.229s
fastboot boot Downloads/twrp-3.2.3-3-crosshatch.img
Downloading 'boot.img' OKAY [ 1.750s]
booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
Finished. Total time: 1.869s
I will try and re-flash the bootloader now. Hopefully it will let me.
---------- Post added at 10:08 AM ---------- Previous post was at 09:56 AM ----------
Flashing entire crosshatch-pq1a.181205.006-factory-96b23504.zip did the trick for me. Apparently phone doesn't like you to wipe /vendor. Good luck
Click to expand...
Click to collapse
I flashed the factory build again. Apparently the messages I was getting are normal.
spuri78 said:
...I flashed the factory build again. Apparently the messages I was getting are normal.
Click to expand...
Click to collapse
Had this issue to except in the bootloader screen it says Samsung. Where it should say micron
billyt1 said:
Had this issue to except in the bootloader screen it says Samsung. Where it should say micron
Click to expand...
Click to collapse
What are you trying to do?
Homeboy76 said:
What are you trying to do?
Click to expand...
Click to collapse
To go back to stock from a custom rom. flash-all.bat didnt work. Ota did tho
Hi, I recently changed to a Custom ROM (Resurrection Remix) and stupid me forgot to backup before unlocking the bootloader, meaning I don't have a stock image. Here's the whole thing:
Resurrection Remix is based on LOS, so I have Lineage recovery atm.
I don't have TWRP flashed, but even when I used fastboot boot twrp.img it booted into TWRP and kept flashing the TWRP logo you see when you boot into it. If you have a TWRP backup I can try and use, that would be great. When I try flashing the official factory image, it just flashes a few things, says it can't find the file 'userdata' and says it failed, here's what happens:
HTML:
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32424 KB)...
OKAY [ 2.031s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 1.949s]
finished. total time: 3.985s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.054s
target reported max download size of 536870912 bytes
sending 'radio_a' (57140 KB)...
OKAY [ 3.132s]
writing 'radio_a'...
OKAY [ 0.461s]
finished. total time: 3.601s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.998s
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 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1938 MB) to disk... took 127.844s
archive does not contain 'system.sig'
extracting system_other.img (311 MB) to disk... took 104.834s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (260 MB) to disk... took 13.234s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
Press any key to exit...
My Pixel XL is in bootloader mode and I do have an OS installed, so I still can access the phone.
Please help, thanks!
Lol. Why do you try to flash stock image using minimal ADB/Fastboot? Did you try following the Google way?
Basically: unzip the factory image and double click flash-all.bat script ?
Here is a proper how-to:
https://developers.google.com/android/images
Good luck...
Agree with @5.1's thoughts. Update to latest/greatest platform tools from Google Developers site...then ensure you have downloaded the proper Factory Image. Then flash per the instructions on the Google site.
---------- Post added at 09:09 AM ---------- Previous post was at 09:07 AM ----------
Agree with @5.1's thoughts. Update to latest/greatest platform tools from Google Developers site...then ensure you have downloaded the proper Factory Image. Then flash per the instructions on the Google site.
As the title says, I had rooted my device, but after about 2 months, decided I wanted to unroot, and go back to normal. I will let you know the steps I took, and the problem I am currently facing to see if anyone can provide some help.
1. I performed a factory reset
2. I flashed my stock boot.img that I backed up prior to rooting with Magisk
3. I booted the device, and factory reset again
4. I locked my bootloader, and then tried to apply my OTA Update (installation failed).
5. After referencing a few google support articles, they suggested to flash the latest Factory Image with the flash-all script.
6. I unlocked my bootloader
7. booted to fastboot, and ran flash-all.bat
8. The Factory image failed on Sending 'product'
9. I modified the flash-all.bat file, and removed the -w from the fastboot update section, and ran it again.
10. Factory image failed on Sending 'product' again
11. I manually sent the command through fastboot. "fastboot update image-crosshatch-qp1a.191005.007.zip (please note, I this is the October factory image, I also tried all of the above with the November factory image with the same failuer).
This is what is displayed when the update is attempted. can someone help me understand what steps I am missing.
C:\Android\Sdk\platform-tools>fastboot update image-crosshatch-qp1a.191005.007.zip
--------------------------------------------
Bootloader Version...: b1c1-0.2-5672671
Baseband Version.....: g845-00048-190722-B-5745561
Serial Number........: 8CRY16G6K
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.057s]
Checking 'version-bootloader' OKAY [ 0.058s]
Checking 'version-baseband' OKAY [ 0.056s]
Setting current slot to 'b' OKAY [ 0.372s]
extracting boot.img (64 MB) to disk... took 0.300s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 0.325s]
Writing 'boot_b' OKAY [ 0.207s]
extracting dtbo.img (8 MB) to disk... took 0.029s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_b' OKAY [ 0.074s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.116s]
Writing 'vbmeta_b' OKAY [ 0.057s]
archive does not contain 'vbmeta_system.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.057s]
< waiting for any device >
Sending 'system_b' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.022s]
Resizing 'product_b' OKAY [ 0.006s]
Resizing 'system_b' OKAY [ 0.006s]
Resizing 'vendor_b' OKAY [ 0.006s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1985 MB) to disk... took 13.550s
archive does not contain 'product.sig'
Sending 'product' (2033548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Khilbron said:
As the title says, I had rooted my device, but after about 2 months, decided I wanted to unroot, and go back to normal. I will let you know the steps I took, and the problem I am currently facing to see if anyone can provide some help.
1. I performed a factory reset
2. I flashed my stock boot.img that I backed up prior to rooting with Magisk
3. I booted the device, and factory reset again
4. I locked my bootloader, and then tried to apply my OTA Update (installation failed).
5. After referencing a few google support articles, they suggested to flash the latest Factory Image with the flash-all script.
6. I unlocked my bootloader
7. booted to fastboot, and ran flash-all.bat
8. The Factory image failed on Sending 'product'
9. I modified the flash-all.bat file, and removed the -w from the fastboot update section, and ran it again.
10. Factory image failed on Sending 'product' again
11. I manually sent the command through fastboot. "fastboot update image-crosshatch-qp1a.191005.007.zip (please note, I this is the October factory image, I also tried all of the above with the November factory image with the same failuer).
This is what is displayed when the update is attempted. can someone help me understand what steps I am missing.
C:\Android\Sdk\platform-tools>fastboot update image-crosshatch-qp1a.191005.007.zip
--------------------------------------------
Bootloader Version...: b1c1-0.2-5672671
Baseband Version.....: g845-00048-190722-B-5745561
Serial Number........: 8CRY16G6K
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.057s]
Checking 'version-bootloader' OKAY [ 0.058s]
Checking 'version-baseband' OKAY [ 0.056s]
Setting current slot to 'b' OKAY [ 0.372s]
extracting boot.img (64 MB) to disk... took 0.300s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 0.325s]
Writing 'boot_b' OKAY [ 0.207s]
extracting dtbo.img (8 MB) to disk... took 0.029s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_b' OKAY [ 0.074s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.116s]
Writing 'vbmeta_b' OKAY [ 0.057s]
archive does not contain 'vbmeta_system.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.057s]
< waiting for any device >
Sending 'system_b' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.022s]
Resizing 'product_b' OKAY [ 0.006s]
Resizing 'system_b' OKAY [ 0.006s]
Resizing 'vendor_b' OKAY [ 0.006s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1985 MB) to disk... took 13.550s
archive does not contain 'product.sig'
Sending 'product' (2033548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Click to expand...
Click to collapse
Do you have the latest sdk platform tools?
jd1639 said:
Do you have the latest sdk platform tools?
Click to expand...
Click to collapse
I thought I was, I just checked, and apparently I need to update my platform-tools, as they changed with the November build release. I will update and get back to you.
EDIT:
I will note, I had the latest platform-tools as of 10/28/2019, but when I checked Android studio, it showed there was a new version.
Khilbron said:
I thought I was, I just checked, and apparently I need to update my platform-tools, as they changed with the November build release. I will update and get back to you.
EDIT:
I will note, I had the latest platform-tools as of 10/28/2019, but when I checked Android studio, it showed there was a new version.
Click to expand...
Click to collapse
Looks like your fastboot directory is not mapped properly in environment variables. The easy way past that error is with your phone still connected and in fastbootd use the arrow keys to go to recovery and then do sideload from ADB and slieload the same version as you were trying to flash. that will do the same thing as flash-all (without -w) except it will change your slots.
sliding_billy said:
Looks like your fastboot directory is not mapped properly in environment variables. The easy way past that error is with your phone still connected and in fastbootd use the arrow keys to go to recovery and then do sideload from ADB and slieload the same version as you were trying to flash. that will do the same thing as flash-all (without -w) except it will change your slots.
Click to expand...
Click to collapse
I actually tried that while waiting on a reply to this post, when I did the sideload on the update file, it failed due to signature.
I then downloaded the Full OTA, and was able to sideload it sucessfully, but I would much rather prefer to flash the latest Factory Image, and have comfort knowing that my issue was an issue with the platform tools version.
jd1639 said:
Do you have the latest sdk platform tools?
Click to expand...
Click to collapse
Alright, using Platform Tools 29.0.5, I am still receiving the same error when attempting to run flash-all.bat with and without the -w. Even when manually executing fastboot update image-crosshatch-qp1a.191105.003.zip
I know that I can boot to recovery, and ADB sideload the latest Full OTA, that was previously successful. However, I want to make sure that I won't encounter any future problems doing OTA updates through the device.
Do you have any additional suggestions?
Khilbron said:
Alright, using Platform Tools 29.0.5, I am still receiving the same error when attempting to run flash-all.bat with and without the -w. Even when manually executing fastboot update image-crosshatch-qp1a.191105.003.zip
I know that I can boot to recovery, and ADB sideload the latest Full OTA, that was previously successful. However, I want to make sure that I won't encounter any future problems doing OTA updates through the device.
Do you have any additional suggestions?
Click to expand...
Click to collapse
- Change USB port or change USB Cable.
- Make sure the USB port you are using is not a charging USB port.
Also, if you are going to lock the bootloader make sure you are 100 percent stock if you do not want to brick your phone. Flash factory image with -w.
Khilbron said:
I actually tried that while waiting on a reply to this post, when I did the sideload on the update file, it failed due to signature.
I then downloaded the Full OTA, and was able to sideload it sucessfully, but I would much rather prefer to flash the latest Factory Image, and have comfort knowing that my issue was an issue with the platform tools version.
Click to expand...
Click to collapse
Glad you at least got out of the error, and as you noticed I did mean the full OTA. Just be sure to add the directory containing Fastboot to your PATH environment variable (the flash-all script must be able to find it). Easy way to check if your path is mapped OK, shift+right click to open a command prompt somewhere other than where you have fastboot (like your desktop) and run a fatboot devices command from there to see if it executes.
Homeboy76 said:
- Change USB port or change USB Cable.
- Make sure the USB port you are using is not a charging USB port.
Also if you are going to lock the bootloader make sure you are 100 percent stock if you do not want to brick your phone. Flash factory image with -w.
Click to expand...
Click to collapse
I've tried both USB 3.0 ports on my laptop, both USB 3.0 ports on my Docking station, as well as the Type-C port on both the laptop and docking station, all give the same error.
I have tried flashing the factory image with and without -w, which is where this problem comes, It fails everytime trying to flash it. I have currently sideloaded the latest Full OTA, and I am awaiting additional steps that I haven't thought of before I re-lock.
sliding_billy said:
Glad you at least got out of the error, and as you noticed I did mean the full OTA. Just be sure to add the directory containing Fastboot to your PATH environment variable (the flash-all script must be able to find it).
Click to expand...
Click to collapse
I modified the Flash-All script to change the path to the platform-tools installation directory, which did not resolve the issue.
Until further information I haven't tried comes up, I have sideloaded the Full OTA, and will sit with my bootloader unlocked for the time being.
Khilbron said:
I modified the Flash-All script to change the path to the platform-tools installation directory, which did not resolve the issue.
Until further information I haven't tried comes up, I have sideloaded the Full OTA, and will sit with my bootloader unlocked for the time being.
Click to expand...
Click to collapse
Just one thing before you waste any more time doing other stuff, loading the OTA only installs to the opposite slot. Do it once more to get back to your original slot and have the OTA in both. Is your hesitance to check the path due to running a MAC? If so, just dump the extracted image (including the flash-all .bat or .sh) directly into your fastboot directory including fastboot itself.
sliding_billy said:
Just one thing before you waste any more time doing other stuff, loading the OTA only installs to the opposite slot. Do it once more to get back to your original slot and have the OTA in both. Is your hesitance to check the path due to running a MAC? If so, just dump the extracted image (including the flash-all .bat or .sh) directly into your fastboot directory including fastboot itself.
Click to expand...
Click to collapse
Naa, I'm on a PC. I have tried 2 flash-all files, the original with the files copied to SYSTEM32, and a modified one, that points directly to my platform-tools directory.
This is the default Flash-All
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-crosshatch-b1c1-0.2-5672671.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-crosshatch-g845-00048-190722-b-5745561.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-crosshatch-qp1a.191105.003.zip
echo Press any key to exit...
pause >nul
exit
Click to expand...
Click to collapse
and this is the modified file, both generate the same issue
PATH=%PATH%;"C:\Users\cmears\AppData\Local\Android\Sdk\platform-tools"
fastboot flash bootloader bootloader-crosshatch-b1c1-0.2-5672671.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-crosshatch-g845-00048-190722-b-5745561.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-crosshatch-qp1a.191105.003.zip
echo Press any key to exit...
pause >nul
exit
Click to expand...
Click to collapse
Note: I also have another copy of the original Flash-All without the -w, that also generates the error.
Khilbron said:
I modified the Flash-All script to change the path to the platform-tools installation directory, which did not resolve the issue.
Until further information I haven't tried comes up, I have sideloaded the Full OTA, and will sit with my bootloader unlocked for the time being.
Click to expand...
Click to collapse
Khilbron said:
I modified the Flash-All script to change the path to the platform-tools installation directory, which did not resolve the issue.
Until further information I haven't tried comes up, I have sideloaded the Full OTA, and will sit with my bootloader unlocked for the time being.
Click to expand...
Click to collapse
There is no need the modify the flash-all.bat file.
- Did you extract the factory image in the Platform-tools folder or whatever folder that has fastboot in it?
- Did you open a 'command prompt' in the Platform-tools folder?
- Did you check the sha256 of the factory image you downloaded?
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Look at #4 in the guide.
Homeboy76 said:
There is no need the modify the flash-all.bat file.
- Did you extract the factory image in the Platform-tools folder or whatever folder that has fastboot in it?
- Did you open a 'command prompt' in the Platform-tools folder?
- Did you check the sha256 of the factory image you downloaded?
https://forum.xda-developers.com/pi...-10-q-root-t3996969/post80774791#post80774791
Look at #4 in the guide.
Click to expand...
Click to collapse
1. Yes, I extracted it to the platform-toosl directory
2. Yes I executed the flash-all from command prompt, in the platform-tools directory.
3. Yes, the Hash matches the Checksum listed on the Factory Image page for Google
Just for record, during the flash-all process, it successfully flashes the Bootloader, and the radio. It only fails on the update flash, at the Product stage.
Khilbron said:
1. Yes, I extracted it to the platform-toosl directory
2. Yes I executed the flash-all from command prompt, in the platform-tools directory.
3. Yes, the Hash matches the Checksum listed on the Factory Image page for Google
Just for record, during the flash-all process, it successfully flashes the Bootloader, and the radio. It only fails on the update flash, at the Product stage.
Click to expand...
Click to collapse
Ok!
Homeboy76 said:
There is no need the modify the flash-all.bat file.
- Did you extract the factory image in the Platform-tools folder or whatever folder that has fastboot in it?
- Did you open a 'command prompt' in the Platform-tools folder?
- Did you check the sha256 of the factory image you downloaded?
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Look at #4 in the guide.
Click to expand...
Click to collapse
Khilbron said:
1. Yes, I extracted it to the platform-toosl directory
2. Yes I executed the flash-all from command prompt, in the platform-tools directory.
3. Yes, the Hash matches the Checksum listed on the Factory Image page for Google
Click to expand...
Click to collapse
I wonder if Google did something with the flash-all script in November or if it is having problems with fastbootd, or if it based on the October install leading up to it because there seem to be more than a normal amount of flash-all issues. I'm on custom, so I am using a sideload method. Strange idea, but since ultimately you are looking to clean wipe. Do a factory reset and then a flash-all to both slots.
sliding_billy said:
I wonder if Google did something with the flash-all script in November or if it is having problems with fastbootd, or if it based on the October install leading up to it because there seem to be more than a normal amount of flash-all issues. I'm on custom, so I am using a sideload method. Strange idea, but since ultimately you are looking to clean wipe. Do a factory reset and then a flash-all to both slots.
Click to expand...
Click to collapse
If he does a factory reset on his phone, I don't think a flash-all is necessary.
Homeboy76 said:
If he does a factory reset on his phone, I don't think a flash-all is necessary.
Click to expand...
Click to collapse
No, just wondering if the command script will work.
Homeboy76 said:
If he does a factory reset on his phone, I don't think a flash-all is necessary.
Click to expand...
Click to collapse
I did do a factory reset on my device, after I sideloaded the October OTA. But when I tried to download the update manually through my device, It failed to install, so I had to unlock my bootloader again, and sideload the november OTA. I am trying to get away from having to sideload any OTA updates, and just update directly through my phone, so I don't have to keep it tethered to a PC to update. And I want to keep my bootloader locked, to avoid issues with Google Pay.
Khilbron said:
I did do a factory reset on my device, after I sideloaded the October OTA. But when I tried to download the update manually through my device, It failed to install, so I had to unlock my bootloader again, and sideload the november OTA. I am trying to get away from having to sideload any OTA updates, and just update directly through my phone, so I don't have to keep it tethered to a PC to update. And I want to keep my bootloader locked, to avoid issues with Google Pay.
Click to expand...
Click to collapse
if you are 100 percent stock you should have no problem taking the OTA without unlocking the bootloader.
Hi guys,
Please help me with my phone.
I have my pixel XL rooted and accidentally upgraded to android 10 and lost my root.
However, when i was in the process of trying to re-root the phone, i probably did something stupid and got my phone soft bricked with the phone turning into to a bootloop showing the Google sign and the screen on booting up.
I am able to enter the bootloader screen and tried to flash the Factory Stock image, from the old version such as 7.1.0 to the new version 10.0.0 but failed.
This is the message i got every time i flash the factory image.
============================================================
Microsoft Windows [版本 10.0.18362.720]
(c) 2019 Microsoft Corporation. 著作權所有，並保留一切權利。
D:\Program Files (x86)\Android\Minimal ADB and Fastboot\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32480 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.060s]
finished. total time: 2.950s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_a' (57156 KB)...
OKAY [ 1.550s]
writing 'radio_a'...
OKAY [ 0.498s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.053s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.325s
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 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1998 MB) to disk... took 9.441s
archive does not contain 'system.sig'
extracting system_other.img (293 MB) to disk... took 1.527s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (253 MB) to disk... took 1.275s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: 蝟餌絞?曆??唳?摰?瑼???(2)
error: Cannot generate image for userdata
Press any key to exit...
;urgently need your help.
sam
samsam2020 said:
Hi guys,
Please help me with my phone.
I have my pixel XL rooted and accidentally upgraded to android 10 and lost my root.
However, when i was in the process of trying to re-root the phone, i probably did something stupid and got my phone soft bricked with the phone turning into to a bootloop showing the Google sign and the screen on booting up.
I am able to enter the bootloader screen and tried to flash the Factory Stock image, from the old version such as 7.1.0 to the new version 10.0.0 but failed.
This is the message i got every time i flash the factory image.
============================================================
Microsoft Windows [版本 10.0.18362.720]
(c) 2019 Microsoft Corporation. 著作權所有，並保留一切權利。
D:\Program Files (x86)\Android\Minimal ADB and Fastboot\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32480 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.060s]
finished. total time: 2.950s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_a' (57156 KB)...
OKAY [ 1.550s]
writing 'radio_a'...
OKAY [ 0.498s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.053s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.325s
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 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1998 MB) to disk... took 9.441s
archive does not contain 'system.sig'
extracting system_other.img (293 MB) to disk... took 1.527s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (253 MB) to disk... took 1.275s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: 蝟餌絞?曆??唳?摰?瑼???(2)
error: Cannot generate image for userdata
Press any key to exit...
;urgently need your help.
sam
Click to expand...
Click to collapse
You installed an Android 10 factory image, please DO NOT try installing an Android 7xx factory image.
If your bootloader is unlocked try this using this Guide:
- First, remove (uninstall) Minimal ADB from your computer.
- Second, download and install SDK Platform-tools r29.0.6 on your computer. There is a link in the guide: Prerequisites c.
- You are on Android 10 Factory Image (10.0.0 (QP1A.191005.007.A3, Dec 2019)) so just do # 9 in the guide to root/reroot.
Note: Check your bootloader and radio version.
Why? You tried to flash an Android 7xx factory image and it look like the Android 7xx bootloader and radio replaced the Android 10 bootloader and radio.
If your bootloader and radio are not:
- bootloader-marlin-8996-012001-1908071822.img
- radio-marlin-8996-130361-1905270421.img
Open a command prompt #1 in the guide and flash them:
Code:
fastboot flash bootloader bootloader-marlin-8996-012001-1908071822.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-130361-1905270421.img
fastboot reboot-bootloader
Homeboy76 said:
You installed an Android 10 factory image, please DO NOT try installing an Android 7xx factory image.
If your bootloader is unlocked try this using this Guide:
- First, remove (uninstall) Minimal ADB from your computer.
- Second, download and install SDK Platform-tools r29.0.6 on your computer. There is a link in the guide: Prerequisites c.
- You are on Android 10 Factory Image (10.0.0 (QP1A.191005.007.A3, Dec 2019)) so just do # 9 in the guide to root/reroot.
Note: Check your bootloader and radio version.
Why? You tried to flash an Android 7xx factory image and it look like the Android 7xx bootloader and radio replaced the Android 10 bootloader and radio.
If your bootloader and radio are not:
- bootloader-marlin-8996-012001-1908071822.img
- radio-marlin-8996-130361-1905270421.img
Open a command prompt #1 in the guide and flash them:
Code:
fastboot flash bootloader bootloader-marlin-8996-012001-1908071822.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-130361-1905270421.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
:good::good::good:
Very GOOD man!
Just tried and i was able to restore the factory image
also rooted my phone again!!
Million thanks for your help.
pics, pardon the **** quality
Tried rooting it, fastboot works but ADB doesn't seem to recognise my device. I went to the link it gave me and followed the tutorial it gave me clicked on it hopes of at least getting back to stock, but at the step were I run the bash script (flash-all.sh) it errors out.
Spoiler: flash-all.sh output
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (4610 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
OKAY [ 0.154s]
finished. total time: 0.366s
rebooting into bootloader...
OKAY [ 0.019s]
finished. total time: 0.069s
target reported max download size of 536870912 bytes
sending 'radio' (56630 KB)...
OKAY [ 1.463s]
writing 'radio'...
OKAY [ 0.535s]
finished. total time: 1.998s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.070s
extracting android-info.txt (0 MB)...
extracting boot.img (11 MB)...
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (17 MB)...
archive does not contain 'recovery.sig'
extracting system.img (1909 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (185 MB)...
archive does not contain 'vendor.sig'
wiping userdata...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.44.5 (15-Dec-2018)
/tmp/TemporaryFile-QFwJ4m: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Where/how can I fix my mess via fastboot or something else?
Extract Android 10 rom and flash the images.
jjgvv said:
Extract Android 10 rom and flash the images.
Click to expand...
Click to collapse
Wouldn't Android 10 run like crap on the Nexus 5X, though? I've only tried some of the 8.1 ROMs, that's the highest it goes on the official page.
seething_n00b said:
Wouldn't Android 10 run like crap on the Nexus 5X, though? I've only tried some of the 8.1 ROMs, that's the highest it goes on the official page.
Click to expand...
Click to collapse
It will not run like crap but will also not be very fast.
seething_n00b said:
Wouldn't Android 10 run like crap on the Nexus 5X, though? I've only tried some of the 8.1 ROMs, that's the highest it goes on the official page.
Click to expand...
Click to collapse
custom rom, 8.1 is Google Offical firmware, offical firmware wont extract ot so
Solved on my own by realising I could just flash TWRP via fastboot. Duh.
jjgvv said:
custom rom, 8.1 is Google Offical firmware, offical firmware wont extract ot so
Click to expand...
Click to collapse
"8.1 won't work, so try 10!" You're even more of an idiot than me.
nope,8.1 is offical ota and can not be flashed in fastboot but only in recovery.