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 softbricked my N7. Can still get to flashboot. However, I have tried following so many guides to flash back to stock to recover from this that I'm going a little manic about it. I just recently tried the Nexus Root Toolkit and it's method. But I get this:
*******Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [6.617s]
finished. total time: 6.617s
sending 'bootloader' <2100 KB>...
OKAY [0.070s]
writing 'bootloader'...
FAILED <remote: SIgnature mismatched!!!>
finished. total time: 0.090s
rebooting into bootloader...
OKAY [0.010s]
finished. total time: 0.010s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
______________________________
Bootloader version...: FLO-03.14
Baseband Version...: none
Serial Number...: 0584c016
______________________________
checking product...
FAILED
Device product is 'flo'/
Update requires 'grouper'.
finished. total time: 0.020s
Booting up your freshly flashed stock device...
_______________________________
and a paragraph about what to do if it doesnt work. i did what it requested and the same thing. Please help me.
usefuladjective said:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
______________________________
Bootloader version...: FLO-03.14
Baseband Version...: none
Serial Number...: 0584c016
______________________________
checking product...
FAILED
Device product is 'flo'/
Update requires 'grouper'..
Click to expand...
Click to collapse
You are trying to flash grouper files on a flo. Get the flo files.
meekrawb said:
You are trying to flash grouper files on a flo. Get the flo files.
Click to expand...
Click to collapse
I've tried flashing just about every image that is available. Each attempt says the same thing.
I'm still having issues.
I've flashed every image that the toolkit gives me a prompt for and it still won't do anything.
Please help me. I'm desperate.
Download the 4.4.2 image from Google site for flo, boot into recovery mode and side load the image.
Sent from my Nexus 7 using XDA Premium 4 mobile app
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?
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.
Hello, I am trying to unroot my phone and relock the bootloader, but I am having some troubles.
After some trial and error with various forums guides here on XDA, I have been trying to use the Tool All in One, the MSM, but nothing is working. Furthermore, I am worried that I have bricked my phone.
The things I have done so far are:
Initially, I rooted the phone with Magisk. During this, I made a file that told my GPS to be where an application wanted it to be, and saved is a system file.
I have since decided to resell the phone and the buyer wants it to be stock. So, I tried the above mentioned tools of Tool All In one, and tried to flash a stock rom but it gave me an error.
I tried MSM but the device comes back as an error to do with serial number or something.
Whilst playing around with these tools, I have some how sent the phone into a permanent fastboot state and I am unable to reboot into any other state, and so I tried to use the guide found here, https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/
This just lead to another failure, where it said I don't have the partitian.
If anyone can help me just get the phone to being a stock phone with no bootloader unlock, that would be great. Happy to chat over Discord if that helps!
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: c9c9ee59
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: require product=msmnile
Setting current slot to 'a' OKAY [ 0.008s]
extracting boot.img (96 MB) to disk... took 0.262s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 2.328s]
Writing 'boot_a' OKAY [ 0.422s]
extracting dtbo.img (16 MB) to disk... took 0.038s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.399s]
Writing 'dtbo' OKAY [ 0.059s]
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' (8 KB) OKAY [ 0.012s]
Writing 'vbmeta' OKAY [ 0.003s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.227s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.426s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Press any key to exit...
This is what I get when I try to use https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/
"fastboot reboot fastboot" to get into fastbootD and then reflash all partitions
In case anyone stumbles across this one day looking for a fix, I found one. My issue was that msm would not connect to sahara and tool all in one wouldn't lock the boot loader without the phone becoming corrupt. To make matters worse, through out all this I lost the ability to use adb and had to use fastboot, and even worse, I some how lost the os entirely and was only able to get into the boot loader.
So the fix for all of this, aka, how to get back to entirely stock software with no root or Bootloader unlocked is this:
1. Install lineageos recover and then os using fast boot so there is at least an operating system and ability to use adb again.
2. Start the phone entirely so you know it works
3. Go back to the bootloader and Install twrp recover
4. Format phone and then adb sideload oxygen os
5. boatload lock with Tool all in one
And wallah it was fixed. If someone needs to know the exact step by step I'm sure I might reply again one day but for now, I'm going to bed!