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.
Related
I am new to android and this is my new first android.
I saw postings yesterday says OTA 4.0.2 rolled out, and people got it already and there are manual way to get it, so I decided try to work on it. I followed the guide how to unlock bootloader and how to root, the first steps went through, but I can get through the last steps because it isays 'waiting for device', i tried everything. somehow I see the bootloader is unlocked.
I installed the stripped 4.0.2 update from here . I used odin mode. now my battery is dropping 1% every few minutes.
I want to flash restore stock image see if I can fix the problem. I trie flash it with odin, but oding crashed.
can anybody help?
Are you running Linux??
Edit:
From Windows or Linux (only tested by myself of Debian Linux) with fastboot in your PATH:
Reboot into bootloader (adb reboot bootloader)
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
windows.
USB driver is installed when phone is normal mode. but in orin the usb driver does not show.
Moved. Please don't post in the wrong forums.
this is GSM version.
where do you get the image files? also why I can't do in orin?
is there a simple way to flash the factory image directory or any gui tool to do it?
Files are here: http://code.google.com/android/nexus/images.html
Make sure to pick the right one: yakju is GSM and mysid is CDMA
Download the tgz file and extract it (might need winrar on windows IDK)
All the Radio,Bootloader,Recovery and system files are included. The only way I know how to flash these files is fastboot, which imo is a safer way than odin - though I have not really used odin before.
can you explain how to use fastboot. I tried vol-up+down+power, it boot into fastboot, I supose it is, on bottom, it says 'unlocked'. what should I do next?
I am really new to this. I don't want to mess with me device like putting custom rom or stuff. I just want keep it original, it looks better that way. I do not want to add any fancy stuff to it unless they are really good. I used to do tweaks with windows mobile, they had better gui tools to work around make things easier.
citrix80 said:
can you explain how to use fastboot. I tried vol-up+down+power, it boot into fastboot, I supose it is, on bottom, it says 'unlocked'. what should I do next?
I am really new to this. I don't want to mess with me device like putting custom rom or stuff. I just want keep it original, it looks better that way. I do not want to add any fancy stuff to it unless they are really good. I used to do tweaks with windows mobile, they had better gui tools to work around make things easier.
Click to expand...
Click to collapse
You need the android sdk installed on your computer. Read this guide:
http://www.xda-developers.com/android/adb-easy-tutorial/
There are also a handful of threads in this very forum answering your same question. A few of which I have given step by step guides myself. Do a quick search.
I downloaded file from
http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84
and used fastboot, all steps worked out.
here is the log
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-toro-primekj1
0.img
error: cannot load 'bootloader-toro-primekj10.img'
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-maguro-primek
j10.img
error: cannot load 'bootloader-maguro-primekj10.img'
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-maguro-primek
k15.img
sending 'bootloader' (2308 KB)... OKAY [ 0.296s]
writing 'bootloader'... OKAY [ 0.604s]
finished. total time: 0.900s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.007s]
finished. total time: 0.007s
C:\android-sdk\platform-tools>fastboot flash radio radio-maguro-i9250xxkk6.img
sending 'radio' (12288 KB)... OKAY [ 1.545s]
writing 'radio'... OKAY [ 2.375s]
finished. total time: 3.920s
C:\android-sdk\platform-tools> fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.007s]
finished. total time: 0.007s
C:\android-sdk\platform-tools> fastboot update image-yakju-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I9250XXKK6
Serial Number........: 0146882D0601C00A
--------------------------------------------
checking product... OKAY [ 0.007s]
checking version-bootloader... OKAY [ 0.007s]
checking version-baseband... OKAY [ 0.008s]
sending 'boot' (4074 KB)... OKAY [ 0.517s]
writing 'boot'... OKAY [ 0.492s]
sending 'recovery' (4406 KB)... OKAY [ 0.562s]
writing 'recovery'... OKAY [ 0.789s]
sending 'system' (317594 KB)... OKAY [ 39.809s]
writing 'system'... OKAY [ 36.250s]
rebooting...
finished. total time: 78.476s
C:\android-sdk\platform-tools>
the phone reboot automatically after the last step.
the battery is still dropping.
is there a way to reset to 4.0.1? I am not sure what is causing the problem.
I really need someone to help me...Please...im on the verge of suicide here
i unlocked and rooted, dl'd cwm.
i dl'd the SDK package (i dont have platform-tools, i have tools)
i put the cwm image, and the tgz files on the root directory (there no /sdcard)
i turn on usb debugging
i load bootloader
i launch cwm recovery
i navigate to the sdk folder (cd c:/ > cd sdk > cd tools) then type fastboot -w update image-yakju-itl41f.zip and get an invalid command error ..that didnt work so i copied the tgz and cwm file to the folder which contains the adb stuff and try again..same result
PLEASE HELP...i know im an annoying **** n00b thats wasting youre time but ive been at this since 9am PLEASE
You dont put the files on your phone. They go in the same folder on your computer as fastboot.exe
trilogee said:
I really need someone to help me...Please...im on the verge of suicide here
i unlocked and rooted, dl'd cwm.
i dl'd the SDK package (i dont have platform-tools, i have tools)
i put the cwm image, and the tgz files on the root directory (there no /sdcard)
i turn on usb debugging
i load bootloader
i launch cwm recovery
i navigate to the sdk folder (cd c:/ > cd sdk > cd tools) then type fastboot -w update image-yakju-itl41f.zip and get an invalid command error ..that didnt work so i copied the tgz and cwm file to the folder which contains the adb stuff and try again..same result
PLEASE HELP...i know im an annoying **** n00b thats wasting youre time but ive been at this since 9am PLEASE
Click to expand...
Click to collapse
put files in ur tools folder inside sdk and you fastboot -w update image-yakju-itl41f.zip and get an invalid command error ,,,should of been ,,, fastboot flash -w
oh god didnt realize i got any replies.
so ive gotten past that part now i have a more frustrating problem...installed platforms-tools from the sdk manager, that enable me to get this:
c:\sdk\platform-tools>fastboot -w update image-yakju-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >
but when i open the image zip the boot recover and system are there.
the waiting for devices deal, in device manager Android Phone is listed with sub Android ADB interface...driver is installed and device is recognized...why does it still say waiting for device...thank you guys so much.
If I get this working today I promise I will make a small donation to both xda and those that help me.
you need open the zip then extra the tar inside it with 7 zip, then copy all 4 extracted file into sdk folder, or same folder with fastboot. then run fastboot. you can use my output in page 1. type exact same thing.
trilogee
How sure are you that the phone is in bootloader mode at the time of flashing? Try executing fastboot devices first to confirm that fastboot can see the phone...Then what the OP has suggested above or do what you were doing.
Hey I think I explained this in another post, not sure where, but fastboot devices initiates a blank command line. Doesn't show anything...which is odd though because I downloaded the right drivers from Samsung, it's recognized on my computer and it worked with ODIN (although updating through odin actually bricked me and forced me to restore)
trilogee said:
Hey I think I explained this in another post, not sure where, but fastboot devices initiates a blank command line. Doesn't show anything...which is odd though because I downloaded the right drivers from Samsung, it's recognized on my computer and it worked with ODIN (although updating through odin actually bricked me and forced me to restore)
Click to expand...
Click to collapse
If fastboot is showing a blank command line, then it means that it can't see your phone. Anything done after that is not going to work. It could then be one of two things, i.e. either your setup is not correct or your phone is not in bootloader mode. Can adb see the phone normally from your PC, i.e. can it see it when you call 'adb devices' or can you see the logcat output?
With the former, I can suggest that you check if the installation is correctly done? As with the latter, I tend to get adb to reboot the phone in bootloader by issuing a 'adb reboot bootloader' and is far quicker than the button-press option.
did you install sdk and driver? when your phone in normal mode, plug in usb to pc, in device manager, you see android driver?
I tried again. whe I get here
C:\android-sdk\platform-tools>fastboot -w update image-yakju-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
but the files are actually in the zip file.
the process still finished.
did it skip those files?
I think that has something to do with the .sig verification settings
..same thing happened to me but image flashed fine and everything seems to be running smoothly. Crazy how I struggled with this so much at first its actually an extremely simple process.
Sent from my Galaxy Nexus using XDA App
I'm trying to root my phone, but I can't flash any boot or recovery images to it, whether that's the patched boot.img, TWRP, or even the stock factory images themselves. I've already unlocked the bootloader, using
Code:
fastboot flashing unlock_critical
.
I am running the newest version of adb and fastboot, downloaded yesterday:
Code:
$ fastboot --version
fastboot version 0.0.1-4500957
Installed as [REDACTED]
$ adb version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as [REDACTED]
When I try to flash the stock factory images, downloaded straight from Google, I get this series of errors:
Code:
$ adb reboot bootloader
$ ./flash-all.sh
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.201s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.201s
extracting android-info.txt (0 MB) to RAM...
Warning: Could not determine slot for secondary images. Ignoring.
extracting boot.img (40 MB) to disk... took 0.289s
target didn't report max-download-size
archive does not contain 'boot.sig'
extracting dtbo.img (8 MB) to disk... took 0.039s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1936 MB) to disk...
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 (349 MB) to disk... took 4.445s
error: Failed to identify current slot
Other fastboot commands also fail with inconsistent error messages and failure modes:
Code:
$ fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (40960 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s
If I try with the -S flag:
Code:
$ fastboot -S 512K flash boot boot.img
Invalid sparse file format at header magic
sending sparse 'boot' 1/51 (508 KB)...
which hangs indefinitely, never sending even the first segment.
I can try booting directly, which yields the same problem:
Code:
$ fastboot boot boot.img
downloading 'boot.img'...
# hangs indefinitely
Similarly,
Code:
$ fastboot --set-active=_a
hangs indefinitely as well. I have to restart the bootloader to kill it, at which point it just prints the confusing error:
Code:
Device does not support slots
(the Pixel 2 XL does support slots!).
The error messages aren't always consistent; sometimes the first fastboot flash boot boot.img command will appear to hang (requiring a restart, similar to
Code:
--set-active
) instead of printing the error message about max-download-size. I've let that run for about fifteen minutes before having to kill it. Unlike system.img, boot.img is only about 40MB, so it shouldn't take that long to flash - something is clearly wrong.
I've also tried this with multiple cables on different USB ports, with the same sorts of results each time.
Am I missing a step? How can I flash the factory images and the patched boot.img?
Most likely not model specific issue but the Pixel-2XL forum:
https://forum.xda-developers.com/pixel-2-xl/help
i have the same problem, and it seems nothing works, tried every single solution on the internet i could find, multiple cables, adb/fastboot up to date
exact same problem as OP
chimeracoder said:
I'm trying to root my phone, but I can't flash any boot or recovery images to it, whether that's the patched boot.img, TWRP, or even the stock factory images themselves. I've already unlocked the bootloader, using
Code:
fastboot flashing unlock_critical
.
Click to expand...
Click to collapse
You're in the wrong forum, using the wrong unlock command, depending on whether you have Pixel 2 or Pixel 2 XL and likely using the wrong factory image too.
You're in the Pixel 2 forum (5" model), not Pixel 2 XL (6" model). You need to go here; https://forum.xda-developers.com/pixel-2-xl/help
You need to make sure you enable developer option on phone first - then in developer option, tick - allow OEM Unlocking, and USB debugging
then it should allow you to go ahead as you have.
Check this out here. Your issue happens when you play around with the bootloader settings and something gets borked. This tool saved me from having to RMA.
EDIT: Never mind, the culprit was the USB C x USB C cable I was using at the office. Back home, I used my USB A x USB C cable and was able to recover the device.
I'm having the exact same problem! I have a Pixel 2, at January 8.1.0 version (OPM1.171019.013). It was rooted with Magisk latest version. Today I decided to reflash the firmware, without wipe, and the flashing was not successful. Now I'm afraid I have a small brick in my hands.
I'm now using the latest fastboot (0.0.1-4500957) and adb (1.0.39 / 0.0.1-4500957) versions. I don't know if I was on the latest versions when I tried to flash the firmware.
I always flashed the firmware using a USB A port on my Dell XPS 9560 notebook. Today I flashed from a USB C port, I don't know if this was the cause for the failed flash. I'm at the office, and I don't have a USB A x USB C cable available.
My Pixel 2 is stuck at the bootloader. Recovery mode and Download mode options don't do anything, it just goes back to the bootloader screen. Bootloader version is mw8998-002.0059.00. It tells me I'm on slot b, and I can't change slots, issuing fastboot --set-active=a either returns:
Code:
error: Device does not support slots
OR:
Code:
FAILED (remote: unknown command)
When I issue fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img either one of these messages is displayed:
Code:
error: Failed to identify current slot
OR:
Code:
target didn't report max-download-size
sending 'bootloader' (38644 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
Has anyone found a solution?
same problem。
could you solve it?
opooi said:
same problem。
could you solve it?
Click to expand...
Click to collapse
As the post above yours suggests, swap out USB cables.
If that doesn't resolve the issue, try these:
-make sure your SDK tools are up to date
-make sure your files are in the correct "platform tools" folder for using fastboot
-make sure your fastboot commands are correct
There is a link to a Pixel 2 XL "guide" in my sig, it covers most issues and processes for the 2 XL.
Az Biker said:
As the post above yours suggests, swap out USB cables.
If that doesn't resolve the issue, try these:
-make sure your SDK tools are up to date
-make sure your files are in the correct "platform tools" folder for using fastboot
-make sure your fastboot commands are correct
There is a link to a Pixel 2 XL "guide" in my sig, it covers most issues and processes for the 2 XL.
Click to expand...
Click to collapse
yes，i use platform-tools_r28.0.0-linux to fastboot,but it still failed.
I compiled AOSP to run "fastboot flashall -w" for pixel 2 xl.it showed:
target reported max download size of 536870912 bytes
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Warning: RAID stripe-width 1 not an even multiple of stride 2.
Creating filesystem with 13902843 4k blocks and 3481600 inodes
Filesystem UUID: e8137926-c3cb-4ddc-bdd1-311c79ed416c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Bootloader Version...: TMZ12a
Baseband Version.....: g8998-00164-1710262031
Serial Number........: 710KPCA0244667
checking product...
OKAY [ 0.000s]
sending 'boot_b' (40960 KB)...
FAILED (data write failure (Protocol error))
finished. total time: 0.162s
Click to expand...
Click to collapse
i feel sad to cry,but i can't solve it
@opooi have you made any progress on fixing it? I've had the exact same issue even with the commands hanging. I fixed it somehow, I don't remember how. I think I booted stock recovery and factory reset. I also tried different images and cleaning my driver's and starting fresh. I was going crazy trying everything I could ever think of and then it just flashed. I'm so scared about it happening again. Also another thing to try, try to reboot bootloader a couple times back to back and see if it helps.
Some guy on Reddit just said he uninstalled magisk, then ran the flash-all and his phone started having this issue. It happened to me when I booted twrp, wiped system data cache and then booted to bootloader and tried to flash.
I have my Pixel 2 XL currently running on the December update (8.1) and Magisk installed, stock recovery. Downloaded the January OTA file (multiple times, actually) and when I run the command to Sideload the OTA zip in Stock Recovery, I get the following error messages:
Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does not match framework matrix 1.0 Installation aborted.
Click to expand...
Click to collapse
Never seen that before and Google/XDA search came up empty or bad results. I also tried to update my adb/tools using Android Studio, still no dice.
The error provided seems to point to Magisk's modification to the dtbo to disable AVB 2.0/dm-verity.
Might have to reflash stock dtbo.img. Or just flash full factory image with the -w flaf removed from the flash-all.bat.
ilal2ielli said:
The error provided seems to point to Magisk's modification to the dtbo to disable AVB 2.0/dm-verity.
Might have to reflash stock dtbo.img. Or just flash full factory image with the -w flaf removed from the flash-all.bat.
Click to expand...
Click to collapse
Yep... that's where I'm at, looking to install the full image with -w omitted. I've even tried to uninstall Magisk (full removal) without luck.
WorldOfJohnboy said:
Yep... that's where I'm at, looking to install the full image with -w omitted. I've even tried to uninstall Magisk (full removal) without luck.
Click to expand...
Click to collapse
Might be able to try restoring images option in Magisk Manager too before installing full image.
I just install the full images each update though, less problems that way.
OK, so I fixed it by going back to stock (December) Boot and DTBO images, then Sideloaded the OTA which worked fine. Worst case, I'll flash the full System without wipe if I have issues. So it looks as if @ilal2ielli was right! Also, credit to THIS post by @sn0warmy for the steps.
Yep, I had the same issue last night and couldn't find anything on Google. Drove me crazy for a good 30 minutes! Then I recalled that you have to be 100% stock to take updates so I flashed stock boot.img and it took the update just fine afterwards. I did not need to flash dtbo.img.
I'm all flashed, but having issues with the Magisk Patched Boot image. Flashed stock back in since it would only boot to recovery or bootloader. I may revert to booting to TWRP and flashing the Magisk that way.
I uninstalled Magisk using the Magisk app and reflashed the stock boot image but I am still getting the January
update installation error. Do I need to use the Magisk-uninstaller zip file?
seckelg said:
I uninstalled Magisk using the Magisk app and reflashed the stock boot image but I am still getting the January
update installation error. Do I need to use the Magisk-uninstaller zip file?
Click to expand...
Click to collapse
Did you flash the December stock boot.img? You may also want to try flashing the December dtbo.img. I did both and my issues are resolved.
WorldOfJohnboy said:
Did you flash the December stock boot.img? You may also want to try flashing the December dtbo.img. I did both and my issues are resolved.
Click to expand...
Click to collapse
Yes, I flashed the boot.img from taimen-opm1.171019.011 and I just did the same with the dtbo.img. Unfortunately the update still won't take. Thanks for the reply though.
seckelg said:
Yes, I flashed the boot.img from taimen-opm1.171019.011 and I just did the same with the dtbo.img. Unfortunately the update still won't take. Thanks for the reply though.
Click to expand...
Click to collapse
Then flash the full image minus the -w from fastboot.
v12xke said:
Then flash the full image minus the -w from fastboot.
Click to expand...
Click to collapse
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 1.069s]
writing 'bootloader'...
FAILED (remote: Flashing is not allowed for Critical Partitions)
finished. total time: 1.084s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.769s]
writing 'radio'...
OKAY [ 0.588s]
finished. total time: 2.365s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
error: update package missing boot.img
Press any key to exit...
fastracer said:
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 1.069s]
writing 'bootloader'...
FAILED (remote: Flashing is not allowed for Critical Partitions)
finished. total time: 1.084s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.769s]
writing 'radio'...
OKAY [ 0.588s]
finished. total time: 2.365s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
error: update package missing boot.img
Press any key to exit...
Click to expand...
Click to collapse
Looks like you didn't unlock your critical partition, which is preventing the factory image from flashing the bootloader. Google blocks boot.img flashes if the bootloader isn't the most updated or the one that matches the boot.img.
You'll need to fastboot unlock_critical, which will wipe your phone and data currently stored on it to progress any further.
fastracer said:
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
Click to expand...
Click to collapse
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:
ilal2ielli said:
Looks like you didn't unlock your critical partition, which is preventing the factory image from flashing the bootloader. Google blocks boot.img flashes if the bootloader isn't the most updated or the one that matches the boot.img.
You'll need to fastboot unlock_critical, which will wipe your phone and data currently stored on it to progress any further.
Click to expand...
Click to collapse
v12xke said:
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:
Click to expand...
Click to collapse
Thanks guys! I'm sure I critical unlocked it BUT I did mess around with so much stuff since this happened I probably did something I wasn't supposed to I'm gonna redo the crictical unlock and start over...thanks again!
v12xke said:
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:
Click to expand...
Click to collapse
Hi. I went through and relocked and then unlocked both the standard "unlock" and the "critical unlock". Then I tried to flash the Feburary image but was met with a "device is corrupt message" that looked like the bootloader warning message except the yellow triangle was red. The sideloading the OTA also gives an error:
E: Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does no match framework matrix 1.0
Installation aborted.
Do you have any idea how I could fix this?
Thanks in advance
km00000 said:
Hi. I went through and relocked and then unlocked both the standard "unlock" and the "critical unlock". Then I tried to flash the Feburary image but was met with a "device is corrupt message" that looked like the bootloader warning message except the yellow triangle was red. The sideloading the OTA also gives an error:
E: Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does no match framework matrix 1.0
Installation aborted.
Do you have any idea how I could fix this?
Thanks in advance
Click to expand...
Click to collapse
Use the most recent adb from the Google factory image page. Also don't use an edited flash-all.bat.
ilal2ielli said:
Use the most recent adb from the Google factory image page. Also don't use an edited flash-all.bat.
Click to expand...
Click to collapse
I've been using the most recent adb (version 1.0.36). Only thing I can think of is that I somehow I added an older version to my PATH so that I could use it from any folder and now Windows keeps using the older version. Is that the latest version?
km00000 said:
I've been using the most recent adb (version 1.0.36). Only thing I can think of is that I somehow I added an older version to my PATH so that I could use it from any folder and now Windows keeps using the older version. Is that the latest version?
Click to expand...
Click to collapse
You arent' running the lastest version of the binaries due to your current path statement. ADB version now is 10.3.9. You should delete all versions off your PC. Edit your path statement with a single ADB folder (C:\ADB\) . Now add this folder to PATH. Go HERE and download the latest version binaries -27.0.1 (December 2017). Unzip the entire zip file into the C:\ADB folder. Reboot. As a test, open a command window and type path and C:\ADB should be there. Make sure your connection to phone in BOOTLOADER MODE is good by typing "fastboot devices" and you should immediately get your serial number back. Now unzip the entire contents of the full Google image (Not OTA) into your ADB folder. Do not further unzip the nested update.zip. Leave that alone. At this point either type flash-all.bat or double click on the batch file to initiate the script.
v12xke said:
You arent' running the lastest version of the binaries due to your current path statement. ADB version now is 10.3.9. You should delete all versions off your PC. Edit your path statement with a single ADB folder (C:\ADB\) . Now add this folder to PATH. Go HERE and download the latest version binaries -27.0.1 (December 2017). Unzip the entire zip file into the C:\ADB folder. Reboot. As a test, open a command window and type path and C:\ADB should be there. Make sure your connection to phone in BOOTLOADER MODE is good by typing "fastboot devices" and you should immediately get your serial number back. Now unzip the entire contents of the full Google image (Not OTA) into your ADB folder. Do not further unzip the nested update.zip. Leave that alone. At this point either type flash-all.bat or double click on the batch file to initiate the script.
Click to expand...
Click to collapse
I was able to force it to go to the adb I downloaded and got it installed. I actually just changed the flash-all.bat script to use the correct adb version by point it to the freshly downloaded platform-tools. I'm not sure where this old ADB is located. It's not in my PATH when I look at environment variables. I don't have any other ADB or platform-tools downloaded, that I know off.
Anyway I got it to work and I'll just make sure to point it to the correct platform-tools whenever I flash something in the future. Can't believe I've been on the developer preview 2 since like November.
I was trying to flash android 8.1 to my new Pixel 2 XL after it didn't OTA well, then the device got stuck in bootloop,
then decided to go back to 8.0 and got the error: Cannot generate image for userdata
full :
target reported max download size of 536870912 bytes
sending 'bootloader_a' (55680 KB)...
OKAY [ 47.517s]
writing 'bootloader_a'...
OKAY [ 0.552s]
finished. total time: 48.072s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 51.809s]
writing 'radio_a'...
OKAY [ 0.566s]
finished. total time: 52.379s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.253s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.034s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1867 MB) to disk... took 12.752s
archive does not contain 'system.sig'
extracting system_other.img (590 MB) to disk... took 4.501s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
extracting vendor.img (341 MB) to disk... took 2.588s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: %1 is not a valid Win32 application. (193)
error: Cannot generate image for userdata
Press any key to exit...
anyone has any idea how to solve it ?
before flashing the device was rooted with magisk and had twrp installed
I had the same error on MacOS, no idea how to resolve it so I used the skipsoft toolkit to flash-all
Make sure you have the latest fastboot binary installed from Google.
I'd try and flash January Security again. It should work if you run the flash-all
you can try this method, it really helped me when an update didn't work. I use it now to make every update, so I don't have any problems.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
thanks for the answers I tried flash-all with the latest android platform tools this is what gave me the error of image for userdata...
SkipSoft doesn't seem to support the new 2017 Pixel 2 XL..
phildenice said:
you can try this method, it really helped me when an update didn't work. I use it now to make every update, so I don't have any problems.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
yeah I tried it gave me the same error of the userdata image..
You could try to unzip system.img and flash individually
hi I also tried flashing individualy (after flash-all failed) and I got the same error - userdata.img
You could try to unzip system.img and flash individually
You might wanna try using fastboot to format the userdata partition; be sure to format partition on both a & b slots...
If you need help or more clarification, let me know...
Hope this helps...
Sorry I didn't see your answer
---------- Post added at 11:27 AM ---------- Previous post was at 11:18 AM ----------
And try :
fastboot format userdata
to see if solves the issue
REM_8 said:
I was trying to flash android 8.1 to my new Pixel 2 XL after it didn't OTA well, then the device got stuck in bootloop,
then decided to go back to 8.0 and got the error: Cannot generate image for userdata
.................................
Click to expand...
Click to collapse
A few things to check that have messed other users up as well:\
make sure you unzipped the factory image then unzip the second zip file for the boot img
make sure OEM unlock is ON
make sure USB Debugging is ON
make sure you have a 2.0 USB cable
try rebooting your PC
make sure your SDK tools are the LATEST version
make sure you're getting your command prompt in the same folder as your platform tools
not saying these will fix your issue, but have seen these trip up others..
Good luck.
Az Biker said:
A few things to check that have messed other users up as well:\
make sure you unzipped the factory image then unzip the second zip file for the boot img
make sure OEM unlock is ON
make sure USB Debugging is ON
make sure you have a 2.0 USB cable
try rebooting your PC
make sure your SDK tools are the LATEST version
make sure you're getting your command prompt in the same folder as your platform tools
not saying these will fix your issue, but have seen these trip up others..
Good luck.
Click to expand...
Click to collapse
Flash-all doesn't like unzipping the second folder. At least it didn't for me.
Larzzzz82 said:
Flash-all doesn't like unzipping the second folder. At least it didn't for me.
Click to expand...
Click to collapse
Extract the secondary zip, and place it in your SDK platform-tools folder. Then try again.
I did that. That's why I said flash-all doesn't like that. I moved the unzipped second folder into my platform tools folder and all went well.
Flashing this device is nothing like Shamu was.
Larzzzz82 said:
I did that. That's why I said flash-all doesn't like that. I moved the unzipped second folder into my platform tools folder and all went well.
Flashing this device is nothing like Shamu was.
Click to expand...
Click to collapse
I hear that bro. Not like the 6p either. But we'll manage :good:
So while flashing an update, my Pixel 3XL turned off and now it only loads in fastboot (every other options goes to black screen). On the fastboot screen I get "Device state: error!" not locked or unlocked. When trying flash-all.bat, here's the read out. When I exit, nothing has changed. I can still only turn on the phone in fastboot and no other options. If anyone has any ideas, I would greatly appreciate it!
Sending 'bootloader_b' (8489 KB) OKAY [ 0.399s]
Writing 'bootloader_b' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 9.746s
rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.052s
< waiting for any device >
Sending 'radio_b' (71148 KB) OKAY [ 2.501s]
Writing 'radio_b' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 11.845s
rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
Checking product OKAY [ 0.060s]
Checking version-bootloader OKAY [ 0.058s]
Checking version-baseband OKAY [ 0.062s]
extracting boot.img (64 MB) to disk... took 0.735s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.075s
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 3.284s
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 27.091s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 5.520s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.002s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 5.421s
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.
Sending 'boot_b' (65536 KB) OKAY [ 2.338s]
Writing 'boot_b' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 76.748s
Press any key to exit...
Do you have the current platform tools? Also, use a C>A USB cable and not a C>C.
Yup, using a C to A cable. Downloaded the tools today so I'm pretty sure it's more of the device state error! problem and the error of no response error during flash.
sal-paradise said:
Yup, using a C to A cable. Downloaded the rooms today so I'm pretty sure it's more of the device state error! problem and the error of no response error during flash.
Click to expand...
Click to collapse
The exact
same thing happened to me. I had to sideload and install the ota. zip and all is good again.
sal-paradise said:
Yup, using a C to A cable. Downloaded the rooms today so I'm pretty sure it's more of the device state error! problem and the error of no response error during flash.
Click to expand...
Click to collapse
No answer about the platform tools, but had you updated the phone before this way? If not, different computer, cable, port, etc. The platform tools haven't changed since a few months before nd of last year, so if you had done this before that part should be safe...
Did you confirm the file download and make sure that it was not corrupted when you unzipped the D/L? Otherwise, the above post about using the OTA through recovery is a good option.
P.S. It helps if you quote the person trying to help so that they know there is an answer.
Patch7 said:
The exact
same thing happened to me. I had to sideload and install the ota. zip and all is good again.
Click to expand...
Click to collapse
How do I sideload the ota if I can't get into recovery? All the menu option through the volume rocker in fastboot leads to the device turning off.
Every now and then I have to swap ports on my computer because I'll get weird errors, not sure if I've seen this one specifically though. Swap ports, swap cables, mix and match until it works or you go through every option you've got.
Speak gentle words of encouragement too.
Seamonkey79 said:
Every now and then I have to swap ports on my computer because I'll get weird errors, not sure if I've seen this one specifically though. Swap ports, swap cables, mix and match until it works or you go through every option you've got.
Speak gentle words of encouragement too.
Click to expand...
Click to collapse
Unfortunately this is a bigger problem than just cables, ports, and gentle words
sal-paradise said:
How do I sideload the ota if I can't get into recovery? All the menu option through the volume rocker in fastboot leads to the device turning off.
Click to expand...
Click to collapse
You can't.
sliding_billy said:
No answer about the platform tools, but had you updated the phone before this way? If not, different computer, cable, port, etc. The platform tools haven't changed since a few months before nd of last year, so if you had done this before that part should be safe...
Did you confirm the file download and make sure that it was not corrupted when you unzipped the D/L? Otherwise, the above post about using the OTA through recovery is a good option.
P.S. It helps if you quote the person trying to help so that they know there is an answer.
Click to expand...
Click to collapse
Right, but that's not an option because all options beyond fastboot lead to a black screen.
Homeboy76 said:
You can't.
Click to expand...
Click to collapse
Exactly.
sal-paradise said:
Exactly.
Click to expand...
Click to collapse
Try this:
On your Computer:
- Open a Command Prompt in the Platform-tools folder
- Make sure these files are in the Platform-tools folder:
bootloader-crosshatch-b1c1-0.1-5191736.img
radio-crosshatch-g845-00009-181130-b-5157073.im
image-crosshatch-pq2a.190305.002.zip
- Boot the phone to fastboot mode
- Connect the phone to the computer with the A to C USB cable
The type these commands (one at a time) at the Command Prompt and press enter after each command:
fastboot flash bootloader bootloader-crosshatch-b1c1-0.1-5191736.img
fastboot reboot-bootloader
fastboot flash radio radio-crosshatch-g845-00009-181130-b-5157073.img
fastboot reboot-bootloader
fastboot update image-crosshatch-pq2a.190305.002.zip
sal-paradise said:
Right, but that's not an option because all options beyond fastboot lead to a black screen.
Click to expand...
Click to collapse
Have you tried the flash-all besides since the initial try? If not, I would definitely retry. Perhaps try changing slots from fastboot and see if you can boot to system or recovery (for OTA or factory reset) or run the flash-all from the other slot.
fastboot --set-active=a
---------- Post added at 03:09 PM ---------- Previous post was at 02:57 PM ----------
sliding_billy said:
Have you tried the flash-all besides since the initial try? If not, I would definitely retry. Perhaps try changing slots from fastboot and see if you can boot to system or recovery (for OTA or factory reset) or run the flash-all from the other slot.
fastboot --set-active=a
Click to expand...
Click to collapse
If that doesn't work, you should be able to change slots with the fastboot boot [twrp].img version of TWRP (run from fastboot) and then reboot to system.
sliding_billy said:
Have you tried the flash-all besides since the initial try? If not, I would definitely retry. Perhaps try changing slots from fastboot and see if you can boot to system or recovery (for OTA or factory reset) or run the flash-all from the other slot.
fastboot --set-active=a
---------- Post added at 03:09 PM ---------- Previous post was at 02:57 PM ----------
If that doesn't work, you should be able to change slots with the fastboot boot [twrp].img version of TWRP (run from fastboot) and then reboot to system.
Click to expand...
Click to collapse
When I try this, here's what I get:
PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002> ./fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 9.219s
PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002>
And yes, everytime I try flash-all I get the same at my original post with the same error:
FAILED (remote: 'error getting device locked state No Response')
Homeboy76 said:
Try this:
On your Computer:
- Open a Command Prompt in the Platform-tools folder
- Make sure these files are in the Platform-tools folder:
bootloader-crosshatch-b1c1-0.1-5191736.img
radio-crosshatch-g845-00009-181130-b-5157073.im
image-crosshatch-pq2a.190305.002.zip
- Boot the phone to fastboot mode
- Connect the phone to the computer with the A to C USB cable
The type these commands (one at a time) at the Command Prompt and press enter after each command:
fastboot flash bootloader bootloader-crosshatch-b1c1-0.1-5191736.img
fastboot reboot-bootloader
fastboot flash radio radio-crosshatch-g845-00009-181130-b-5157073.img
fastboot reboot-bootloader
fastboot update image-crosshatch-pq2a.190305.002.zip
Click to expand...
Click to collapse
I have an older bootloader version, so when I try this, it tells me:
PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002> ./fastboot update image-crosshatch-pq2a.190305.002.zip
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-5034669
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 85HY008F7
--------------------------------------------
Checking product OKAY [ 0.062s]
Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-5034669'.
Update requires 'b1c1-0.1-5191736'.
fastboot: error: requirements not met!
sal-paradise said:
I have an older bootloader version, so when I try this, it tells me:
PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002> ./fastboot update image-crosshatch-pq2a.190305.002.zip
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-5034669
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 85HY008F7
--------------------------------------------
Checking product OKAY [ 0.062s]
Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-5034669'.
Update requires 'b1c1-0.1-5191736'.
fastboot: error: requirements not met!
Click to expand...
Click to collapse
¯\_(ツ)_/¯
sal-paradise said:
When I try this, here's what I get:
PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002> ./fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 9.219s
PS C:\Users\Englands\Desktop\crosshatch-pq2a.190305.002>
And yes, everytime I try flash-all I get the same at my original post with the same error:
FAILED (remote: 'error getting device locked state No Response')
Click to expand...
Click to collapse
Sorry, but I just got back online (been one of those nights). Looking at all the back and forth, I feel like there is a communication gap between you and those of us helping. There are questions and suggestions unanswered. For one, I never saw a reply to if this is the first time you are attempting to update via a flash-all on the same computer/port/cable/etc. That will answer a bit about your knowledge and the hardware functionality. If all that is a go, the only thing that jumps out at me is the possibility of a bad download or something easy to remedy like a command problem or file location/path issue. Have you checked with Google? I know that getting a replacement sucks, but you may need to start over. The folks here have done this tons of times and got back from bricks probably more severe than yours. I have never seen a device that could get to fastboot not be recoverable if all of the things we are talking about are being executed properly, but there is always a first like a serious phone hardware failure that nothing is going to solve except for a replacement.
One thing I see is the PS location. I know there are some commands that don't play nice in PowerShell, so type 'cmd' from PS and get to a standard command prompt.
sal-paradise said:
How do I sideload the ota if I can't get into recovery? All the menu option through the volume rocker in fastboot leads to the device turning off.
Click to expand...
Click to collapse
I had the exact thing happened to me on my Pixel 2 XL but nothing worked,
not even the "Duce Script". I decided to use the "Skip Soft" tool as my last resort
and to my surprise it worked and fixed it in less than 10 minutes!
Unfortunately the Dev hasn't added the Crosshatch yet. I suggest you download it
and ask him to add it in the "Device Support" section, he''ll add it once he sees more requests.
Good luck.
sliding_billy said:
Sorry, but I just got back online (been one of those nights). Looking at all the back and forth, I feel like there is a communication gap between you and those of us helping. There are questions and suggestions unanswered. For one, I never saw a reply to if this is the first time you are attempting to update via a flash-all on the same computer/port/cable/etc. That will answer a bit about your knowledge and the hardware functionality. If all that is a go, the only thing that jumps out at me is the possibility of a bad download or something easy to remedy like a command problem or file location/path issue. Have you checked with Google? I know that getting a replacement sucks, but you may need to start over. The folks here have done this tons of times and got back from bricks probably more severe than yours. I have never seen a device that could get to fastboot not be recoverable if all of the things we are talking about are being executed properly, but there is always a first like a serious phone hardware failure that nothing is going to solve except for a replacement.
One thing I see is the PS location. I know there are some commands that don't play nice in PowerShell, so type 'cmd' from PS and get to a standard command prompt.
Click to expand...
Click to collapse
My apologies, I thought a previous comment mentioning computer/port/cables that I responded to clarified this. This is not the issue as I've done it with multiple desktops and multiple USB A to C cables. Even when attempting to change from slot B to A I get the device state error, which I've copied in another post on here. Isn't that the problem here? If I can't figure out a way to get around the fact that there's no response when trying to determine the lock state, I don't think we can fix the problem here. I don't see how this would have to do with being in powershell or not or being a bad download. Since most things fail in fastboot because of this error, this is what I was trying to get more info on to get corrected as it clearly seems to be the heart of the failure.
Unfortunately a lot of the back and forth is because of the repetition about cables and ports or asking me to recover which I appreciate, but I stated choosing recovery sends me to a black screen. When there's been actual commands to try in fastboot, I've posted the results they've given, but it still comes back to " FAILED (remote: 'error getting device locked state No Response') "
sal-paradise said:
My apologies, I thought a previous comment mentioning computer/port/cables that I responded to clarified this. This is not the issue as I've done it with multiple desktops and multiple USB A to C cables. Even when attempting to change from slot B to A I get the device state error, which I've copied in another post on here. Isn't that the problem here? If I can't figure out a way to get around the fact that there's no response when trying to determine the lock state, I don't think we can fix the problem here. I don't see how this would have to do with being in powershell or not or being a bad download. Since most things fail in fastboot because of this error, this is what I was trying to get more info on to get corrected as it clearly seems to be the heart of the failure.
Unfortunately a lot of the back and forth is because of the repetition about cables and ports or asking me to recover which I appreciate, but I stated choosing recovery sends me to a black screen. When there's been actual commands to try in fastboot, I've posted the results they've given, but it still comes back to " FAILED (remote: 'error getting device locked state No Response') "
Click to expand...
Click to collapse
I appreciate the reply. Some of the things are just things that take no real effort (like downloading/extracting the factory image again to be safe), while the PS thing was just to make sure that if folks are sending commands to try that they are sending the right ones. The question about whether you were using a Mac or Linix (that I think has been deleted since I read it) got me thinking about that and not that running the flash-all batch would react differently.
Last thing, have you tried anything with the TWRP .img version like changing slots or even doing a factory reset?