(remote: 'Error getting device locked state No Response') - Google Pixel 3 XL Questions & Answers
So I was flashing my device to the December update on my unlocked bootloader Pixel 3. Everything seemed to work fine and it loaded after the flash. Went through the startup options and reset the phone. Now I can only turn it on by holding down power and Volume Down to load in Fastboot Mode. When I do it gives me "Device state: error!" (error is in red).
When I open command prompt and type fastboot flashing unlock it tells me:
FAILED (remote: 'Error getting device locked state No Response') after 9 seconds.
Any advice on how to get this back up and running? I've done some google searches but haven't found this error message. Thanks in advance!!
First thing to try is flash factory image with flash-all, and then start over. You could try and remove -w from flash-all script to try first, so it doesn't wipe the phone.
Getting to bootloader is always a good sign at least.
I am having the same problem. Except when i go to flash the recovery or even the boot image i keep getting error not allowed. I too can only boot to the bootloader.
I've tried this.
Sending 'bootloader_b' (8489 KB) OKAY [ 0.437s]
Writing 'bootloader_b' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 9.809s
rebooting into bootloader OKAY [ 0.062s]
Finished. Total time: 0.062s
< waiting for any device >
Sending 'radio_b' (71148 KB) OKAY [ 2.598s]
Writing 'radio_b' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 11.955s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.058s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-5034669
Baseband Version.....: values given
Serial Number........: values given
--------------------------------------------
Checking product OKAY [ 0.052s]
Checking version-bootloader OKAY [ 0.054s]
Checking version-baseband OKAY [ 0.059s]
extracting boot.img (64 MB) to disk... took 0.627s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.062s
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 5.967s
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 71.632s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 12.458s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.004s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 12.275s
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.457s]
Writing 'boot_b' FAILED (remote: 'error getting device locked state No Response')
Finished. Total time: 185.977s
Press any key to exit...
boostedduece said:
First thing to try is flash factory image with flash-all, and then start over. You could try and remove -w from flash-all script to try first, so it doesn't wipe the phone.
Getting to bootloader is always a good sign at least.
Click to expand...
Click to collapse
Ofuroski said:
So I was flashing my device to the December update on my unlocked bootloader Pixel 3. Everything seemed to work fine and it loaded after the flash. Went through the startup options and reset the phone. Now I can only turn it on by holding down power and Volume Down to load in Fastboot Mode. When I do it gives me "Device state: error!" (error is in red).
When I open command prompt and type fastboot flashing unlock it tells me:
FAILED (remote: 'Error getting device locked state No Response') after 9 seconds.
Any advice on how to get this back up and running? I've done some google searches but haven't found this error message. Thanks in advance!!
Click to expand...
Click to collapse
When you load fastboot mode what is the 'device state'?
what version of SDK Platform-tools is on your computer?
It should be r28.0.1
Did you open the Command Prompt in the Platform-tools folder?
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + December 2018 Security Patch
Make sure you all have the latest sdk platform tools, r28. Looking at your posts here it looks like that is the problem. And to op, once the bootloader is unlocked it'll stay that way unless you specifically lock it so there's no need to try again. But, once you're in the bootloader use the command fastboot devices. Does it return a serial number or just hang like when you tried to unlock again. If it just hangs there's either a problem with your fastboot drivers or try different cables and USB ports.
Sent from my [device_name] using XDA-Developers Legacy app
Yes, I'm in the powershell in the folder and have the latest SDK. As stated, when I boot up into Fastboot mode, it gives device state as "error!" in red lettering like it's unable to determine if it's locked or not. It does not say locked or unlocked.
Homeboy76 said:
When you load fastboot mode what is the 'device state'?
what version of SDK Platform-tools is on your computer?
It should be r28.0.1
Did you open the Command Prompt in the Platform-tools folder?
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + December 2018 Security Patch
Click to expand...
Click to collapse
When I type adb devices it says list of devices and is blank. However if I type commands such as flash-all it will recognize the device and attempt to flash (although it fails as seen above) since it gets hung up on not being able to determine the locked state. When doing this, it does show a serial number. Any other ideas?
jd1639 said:
Make sure you all have the latest sdk platform tools, r28. Looking at your posts here it looks like that is the problem. And to op, once the bootloader is unlocked it'll stay that way unless you specifically lock it so there's no need to try again. But, once you're in the bootloader use the command fastboot devices. Does it return a serial number or just hang like when you tried to unlock again. If it just hangs there's either a problem with your fastboot drivers or try different cables and USB ports.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ofuroski said:
When I type adb devices it says list of devices and is blank. However if I type commands such as flash-all it will recognize the device and attempt to flash (although it fails as seen above) since it gets hung up on not being able to determine the locked state. When doing this, it does show a serial number. Any other ideas?
Click to expand...
Click to collapse
If you're booted into the bootloader adb doesn't work. It's only for when you're in system or recovery. Fastboot is what you need when booted into the bootloader. I'm sure, based on the flash-all working, that if you type fastboot devices when booted into the bootloader you'll get yet serial number returned.
Have you tried to flash only the bootloader image to both slots?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
If you're booted into the bootloader adb doesn't work. It's only for when you're in system or recovery. Fastboot is what you need when booted into the bootloader. I'm sure, based on the flash-all working, that if you type fastboot devices when booted into the bootloader you'll get yet serial number returned.
Have you tried to flash only the bootloader image to both slots?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, you are 100% correct. When I type fastboot devices the serial does appear. However, this still does not help me with the "device state: error!" message. The only thing I've flashed was the December update, so I'm not sure what you mean by flashing only the bootloader image to both slots.
Ofuroski said:
Yes, you are 100% correct. When I type fastboot devices the serial does appear. However, this still does not help me with the "device state: error!" message. The only thing I've flashed was the December update, so I'm not sure what you mean by flashing only the bootloader image to both slots.
Click to expand...
Click to collapse
If you extract the factory image you'll find a bootloader-blueline- image file. You would use
fastboot flash bootloader --slot all bootloader.img (where bootloader is the full name of the file)
Edit, sorry you have the XL so it would be bootloader-crosshatch-
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
If you extract the factory image you'll find a bootloader-blueline- image file. You would use
fastboot flash bootloader --slot all bootloader.img (where bootloader is the full name of the file)
Edit, sorry you have the XL so it would be bootloader-crosshatch-
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Right. I tried that now and it gives me the same.
Sending 'bootloader_a' (8489 KB) OKAY
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
Finished.
Ofuroski said:
Right. I tried that now and it gives me the same.
Sending 'bootloader_a' (8489 KB) OKAY
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
Finished.
Click to expand...
Click to collapse
Then something is probably wrong with your device. But try one last thing, booted into the bootloader try
fastboot flashing unlock_critical
This shouldn't make any difference but who knows. It'll wipe the device too so plan for that.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Then something is probably wrong with your device. But try one last thing, booted into the bootloader try
fastboot flashing unlock_critical
This shouldn't make any difference but who knows. It'll wipe the device too so plan for that.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Wiping doesn't matter since I already wiped when flashing the December update right before the error occurred, but I think that command was for Pixel 2? It tells me
FAILED (remote: 'invalid argument unlock_critical') when I try that command.
I'm trying to figure out why the phone gives no response when trying to determine the locked state. Seems odd that I haven't seen this error message brought up anywhere on these forums before.
Ofuroski said:
Wiping doesn't matter since I already wiped when flashing the December update right before the error occurred, but I think that command was for Pixel 2? It tells me
FAILED (remote: 'invalid argument unlock_critical') when I try that command.
I'm trying to figure out why the phone gives no response when trying to determine the locked state. Seems odd that I haven't seen this error message brought up anywhere on these forums before.
Click to expand...
Click to collapse
I'm betting your eMMC is bad since nothing seems to be able to determine the lock state. When you boot to the bootloader the device state should say locked or unlocked and yours says error. So it's not being read correctly or at all. I haven't seen this problem either with this device but there's always a first. You should be able to RMA the device and that's where I would go from here.
Sent from my [device_name] using XDA-Developers Legacy app
Ofuroski said:
Wiping doesn't matter since I already wiped when flashing the December update right before the error occurred, but I think that command was for Pixel 2? It tells me
FAILED (remote: 'invalid argument unlock_critical') when I try that command. I'm trying to figure out why the phone gives no response when trying to determine the locked state. Seems odd that I haven't seen this error message brought up anywhere on these forums before.
Click to expand...
Click to collapse
Yes, unlock_critical was only needed for the Pixel 2. Run "fastboot getvar all" and post the result. At least the first 30 lines or so. Sounds like you ran factory reset from within system and that is when the trouble started, but how about when you run it (FDR) from recovery mode? ADB commands will only work in recovery mode.
v12xke said:
Yes, unlock_critical was only needed for the Pixel 2. Run "fastboot getvar all" and post the result. At least the first 30 lines or so. Sounds like you ran factory reset from within system and that is when the trouble started, but how about when you run it (FDR) from recovery mode? ADB commands will only work in recovery mode.
Click to expand...
Click to collapse
Thanks for your help and info. Here's what getvar posts.
(bootloader) product:crosshatch
(bootloader) serialno:85HY008F7
(bootloader) variant:MSM USF
(bootloader) max-download-size:0x10000000
(bootloader) slot-suffixes:_a,_b
(bootloader) version-bootloader:b1c1-0.1-5034669
(bootloader) version-baseband:g845-00023-180917-B-5014671
(bootloader) secure-boot:NONE
(bootloader) secure:no
(bootloader) hw-revision:EVT1.1
(bootloader) slot-count:2
(bootloader) current-slot:b
(bootloader) unlocked:error
(bootloader) nos-production:error
(bootloader) off-mode-charge:1
(bootloader) slot-retry-count:a:3
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) battery-voltage:3790
(bootloader) battery-soc-ok:yes
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd:0x2000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc:0x100000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore:0x80000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp:0x80000
Ofuroski said:
Thanks for your help and info. Here's what getvar posts....
Click to expand...
Click to collapse
The notable ones I see are different from mine. Everything else is the same except for the differences between blueline and crosshatch. I'm not a dev and don't know exactly what they mean but there is something wrong with secure-boot. Since you were stock there should be little risk in running the flashing command and try lock and then unlock the bootloader. Generally the rule is once the bl is unlocked you never go back for any reason, but you are dead in the water right now anyway. Hopefully you are in good shape warranty-wise in case you can't recover.
(bootloader) secure-bootRODUCTION
(bootloader) secure:yes
(bootloader) unlocked:yes
(bootloader) nos-production:yes
I have exactly same issue on Pixel5.
Did you find any solution?
Not sure if this helps anyone else, I had my Pixel 3 XL just break.
Bootloader failed to verify/load image. Going into rescue mode didnt work. Fastboot was giving the same No response error
Fastboot command (flash:bootloader_b) failed: 'error getting device locked state No Response'
I tried to flash the bootloader
(env) ➜ platform-tools fastboot flash bootloader bootloader-crosshatch-b1c1-0.3-7065185.img
Sending 'bootloader_b' (8517 KB) OKAY [ 0.310s]
Writing 'bootloader_b' FAILED (remote: 'error getting device locked state No Response')
and i tried to unlock the bootloader
(env) ➜ platform-tools fastboot flashing unlock
FAILED (remote: 'Error getting device locked state No Response')
fastboot: error: Command failed
So i figured this thing was bricked so i started play around with every command to see if anything would work
(env) ➜ platform-tools fastboot update ~/Downloads/crosshatch-rq2a.210405.006/image-crosshatch-rq2a.210405.006.zip
--------------------------------------------
Bootloader Version...: b1c1-0.3-7241706
Baseband Version.....: g845-00173-210331-B-7249945
Serial Number........: 8BLY10DMG
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.058s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'b1c1-0.3-7241706'.
Update requires 'b1c1-0.3-7065185'.
fastboot: error: requirements not met!
(env) ➜ platform-tools fastboot flashing unlock
FAILED (remote: 'Error getting device locked state No Response')
fastboot: error: Command failed
(env) ➜ platform-tools fastboot oem fastboot oem
FAILED (remote: 'Invalid oem command fastboot')
fastboot: error: Command failed
(env) ➜ platform-tools fastboot oem ddrtest
FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
(env) ➜ platform-tools fastboot oem
fastboot: usage: empty oem command
(env) ➜ platform-tools fastboot oem citadel state
FAILED (remote: 'failed to get citadel state No Response')
fastboot: error: Command failed
(env) ➜ platform-tools fastboot oem citadel reset
OKAY [ 0.190s]
Finished. Total time: 0.190s
(env) ➜ platform-tools fastboot oem citadel state
(bootloader) Citadel state:
(bootloader) Version : 1
(bootloader) Bootloader state: 0
(bootloader) Production state: 1
(bootloader) Number of locks : 4
(bootloader) Lock[0]: 1
(bootloader) Lock[1]: 1
(bootloader) Lock[2]: 1
(bootloader) Lock[3]: 0
OKAY [ 0.151s]
Finished. Total time: 0.151s
(env) ➜ platform-tools fastboot flashing unlock
FAILED (remote: 'flashing unlock is not allowed')
fastboot: error: Command failed
(env) ➜ platform-tools fastboot oem citadel reset-locks
FAILED (remote: 'failed to reset citadel AVB locks Device Error')
fastboot: error: Command failed
(env) ➜ platform-tools fastboot oem citadel reset-locks
(env) ➜ platform-tools fastboot reboot
Rebooting OKAY [ 0.080s]
Finished. Total time: 0.080s
I finally got a different screen after
fastboot oem citadel reset
fastboot oem citadel state
fastboot oem citadel reset-locks
fastboot reboot
This gave me an android with a No connection error message and fastboot was no longer showing the device. I then hit power+up vol until it rebooted, hit power+down vol until it rebooted.. and it booted into Android!
hope something here helps someone else, I have no idea what i actually did but
Related
Wildfire jammed in FASTBOOT
Welcome. I have the following problem with my HTC. When you turn on the phone immediately turns on fastboot and can not control buttons Vol + / - on the menu. Can I come in hboot, but there did not respond to my commands. It is a chance to solve the problem? *** UNLOCKED *** BUZZ PVT SHIP S-ON HBOOT-1002.0000 MICROP-0622 TOUCH PANEL-ATMELC03_16ac RADIO-3.35.20.10 Click to expand... Click to collapse
BukeR00 said: Welcome. I have the following problem with my HTC. When you turn on the phone immediately turns on fastboot and can not control buttons Vol + / - on the menu. Can I come in hboot, but there did not respond to my commands. It is a chance to solve the problem? Click to expand... Click to collapse Does it boot Into hboot or fastboot specifically? Also do you have an sdcard in the phone? And lastly when you plug in the usb cable to issue commands does the phone change to hbootUSB or fastbootUSB at all and does Windows detect and Install drivers? Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
When I push the power button, phone starts in FASTBOOT. I can run it in hboot by pressing Vol-+ PWR. In both modes, the buttons are not working. When I connect the USB cable changes as FASTBOOT USB / HBOOT USB or something like that. I have a card in your phone, I try without the card.
BukeR00 said: When I push the power button, phone starts in FASTBOOT. I can run it in hboot by pressing Vol-+ PWR. In both modes, the buttons are not working. When I connect the USB cable changes as FASTBOOT USB / HBOOT USB or something like that. I have a card in your phone, I try without the card. Click to expand... Click to collapse OK please try without the card in also when you are in fastboot USB can you issue the command fastboot getvar all please and see if it works. Sent from my Nexus 7 using Tapatalk 4
Code: C:\adb>fastboot getvar all INFOversion: 0.5 INFOversion-bootloader: 1.02.0000 INFOversion-baseband: 3.35.20.10 INFOversion-cpld: None INFOversion-microp: 0622 INFOversion-main: 2.46.0.0 INFOserialno: ########### INFOimei: ########### INFOproduct: buzz INFOplatform: HBOOT-7225 INFOmodelid: PC4910000 INFOcidnum: HTC__032 INFObattery-status: good INFObattery-voltage: 3955mV INFOpartition-layout: HTC INFOsecurity: on INFObuild-mode: SHIP INFOboot-mode: FASTBOOT INFOcommitno-bootloader: 42e5cc47 INFOhbootpreupdate: 11 INFOgencheckpt: 0 all: Done! finished. total time: 0.053s Without the card the same problems. Keys are not working. When I'm try to upload RUU crashes. 155 ERROR. I tried to many versions, as last RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed Thanks for your reply
BukeR00 said: Code: C:\adb>fastboot getvar all INFOversion: 0.5 INFOversion-bootloader: 1.02.0000 INFOversion-baseband: 3.35.20.10 INFOversion-cpld: None INFOversion-microp: 0622 INFOversion-main: 2.46.0.0 INFOserialno: ########## INFOimei: ############### INFOproduct: buzz INFOplatform: HBOOT-7225 INFOmodelid: PC4910000 INFOcidnum: HTC__032 INFObattery-status: good INFObattery-voltage: 3955mV INFOpartition-layout: HTC INFOsecurity: on INFObuild-mode: SHIP INFOboot-mode: FASTBOOT INFOcommitno-bootloader: 42e5cc47 INFOhbootpreupdate: 11 INFOgencheckpt: 0 all: Done! finished. total time: 0.053s Without the card the same problems. Keys are not working. When I'm try to upload RUU crashes. 155 ERROR. I tried to many versions, as last RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed Thanks for your reply Click to expand... Click to collapse I should have said, block out your imei and HTC serial number like I have. You never know whos watching... Anyway, your bootloader is still unlocked so ruus wont flash. You can use the command fastboot oem lock to relock the bootloader. But, it's unlikely that it will work as you have an upgraded hboot. If I was you I would I would extract the Rom.zip from the ruu. Then extract that Rom.zip and you should end up with several images and some .nbh files. place the boot.img, system.img, data.img Into your fastboot folder. Then you going to want to format the phone with fastboot and then flash the phone with fastboot. http://androidforums.com/one-s-all-things-root/714676-list-fastboot-command.html here is a command list but I will tell you what I think it should be, and if you hit a snag refer to the link. So the commands should be in this order assuming you are CD'd to your fastboot folder fastboot format boot fastboot format system fastboot format data fastboot format cache Then assuming it all goes well then issue these commands fastboot flash system.img fastboot flash data.img fastboot flash boot.img fastboot flash boot.img fastboot reboot Yes that flash the boot.img twice is not a typo all going well after this you should able to boot up. if you hit any big problems just hit the thread pal Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Code: C:\adb>fastboot oem lock ... INFOLock successfully... FAILED (status read failed (No such file or directory)) finished. total time: 0.015s In FASTBOOT shows now - *** RELOCKED *** Code: fastboot format boot fastboot format system fastboot format data fastboot format cache It does not work. There is no these commands Code: C:\adb>fastboot erase boot erasing 'boot'... FAILED (remote: not allowed) finished. total time: 0.002s C:\adb> fastboot erase data erasing 'data'... FAILED (remote: not allowed) finished. total time: 0.002s C:\adb>fastboot erase system erasing 'system'... FAILED (remote: not allowed) finished. total time: 0.002s Code: C:\adb>fastboot flash system.img unknown partition 'system.img' error: cannot determine image filename for 'system.img' C:\adb>\fastboot flash data.img '\fastboot' is not recognized as an internal or external command, operable program or batch file. C:\adb>fastboot flash boot.img unknown partition 'boot.img' error: cannot determine image filename for 'boot.img' C:\adb>fastboot flash system system.img sending 'system' (212163 KB)... OKAY [ 44.854s] writing 'system'... INFOsignature checking... FAILED (remote: signature verify fail) finished. total time: 98.833s C:\adb>fastboot flash boot boot.img sending 'boot' (2476 KB)... OKAY [ 1.050s] writing 'boot'... INFOsignature checking... FAILED (remote: signature verify fail) finished. total time: 1.689s C:\adb>fastboot reboot rebooting... finished. total time: 0.012s In my rom.zip there is no data.img After the command fastboot reboot the phone hangs on the white HTC boot screen.
BukeR00 said: Code: C:\adb>fastboot oem lock ... INFOLock successfully... FAILED (status read failed (No such file or directory)) finished. total time: 0.015s In FASTBOOT shows now - *** RELOCKED *** Code: fastboot format boot fastboot format system fastboot format data fastboot format cache It does not work. There is no these commands Code: C:\adb>fastboot erase boot erasing 'boot'... FAILED (remote: not allowed) finished. total time: 0.002s C:\adb> fastboot erase data erasing 'data'... FAILED (remote: not allowed) finished. total time: 0.002s C:\adb>fastboot erase system erasing 'system'... FAILED (remote: not allowed) finished. total time: 0.002s Code: C:\adb>fastboot flash system.img unknown partition 'system.img' error: cannot determine image filename for 'system.img' C:\adb>\fastboot flash data.img '\fastboot' is not recognized as an internal or external command, operable program or batch file. C:\adb>fastboot flash boot.img unknown partition 'boot.img' error: cannot determine image filename for 'boot.img' C:\adb>fastboot flash system system.img sending 'system' (212163 KB)... OKAY [ 44.854s] writing 'system'... INFOsignature checking... FAILED (remote: signature verify fail) finished. total time: 98.833s C:\adb>fastboot flash boot boot.img sending 'boot' (2476 KB)... OKAY [ 1.050s] writing 'boot'... INFOsignature checking... FAILED (remote: signature verify fail) finished. total time: 1.689s C:\adb>fastboot reboot rebooting... finished. total time: 0.012s In my rom.zip there is no data.img After the command fastboot reboot the phone hangs on the white HTC boot screen. Click to expand... Click to collapse Ah. This could be problematic. I should have been clearer, I didn't mean for you to lock your bootloader again, I was simply informing you it would need to be locked for an ruu to run. None of those commands will work while the bootloader is locked. If you were the one to unlock the device the you can unlock it again assuming you have the unlock_token.bin, using the same fastboot command again. If you didn't you will have to go to www.htcdev.com and make an account, then go to bootloader unlock, select wildfire buzz and ignore the bootloader update, as you already have it. (Skip should be near the bottom.) Then follow the instructions and get the bootloader unlocked again. Then issue the commands excluding the lock bootloader one and the flash data data.img as you don't have it. Its not a problem though, I was just covering all bases, incase it did have a data.img in there make sure you still do the data format though! Sorry for the confusion Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
What version of RUU I must use? I tested 3 versions and none of them has data.img I have uploaded the files system.img, recovery.img, userdata.img and the phone still does not work. How can I delete the data. Fastboot format command does not work, there is no such command. And after the command fastboot erase still: Code: C:\adb>fastboot erase boot erasing 'boot'... FAILED (remote: not allowed) finished. total time: 0.002s C:\adb> fastboot erase data erasing 'data'... FAILED (remote: not allowed) finished. total time: 0.002s C:\adb>fastboot erase system erasing 'system'... FAILED (remote: not allowed) finished. total time: 0.002s
BukeR00 said: What version of RUU I must use? I tested 3 versions and none of them has data.img I have uploaded the files system.img, recovery.img, userdata.img and the phone still does not work. How can I delete the data. Fastboot format command does not work, there is no such command. And after the command fastboot erase still: Code: C:\adb>fastboot erase boot erasing 'boot'... FAILED (remote: not allowed) finished. total time: 0.002s C:\adb> fastboot erase data erasing 'data'... FAILED (remote: not allowed) finished. total time: 0.002s C:\adb>fastboot erase system erasing 'system'... FAILED (remote: not allowed) finished. total time: 0.002s Click to expand... Click to collapse did you get the bootloader unlocked again? fastboot commands will only work on unlocked bootloaders. Dont worry about the data.img, you do not need it. i simply added it incase the ruu had it and you got confused. again, it is not required.
Yes, I have unlocked bootloader, but comands still don't work. //edit: C:\sdk\sdk\platform-tools>fastboot format boot formatting 'boot' partition... FAILED (remote: unknown command) FAILED (remote: unknown command) finished. total time: 0.006s C:\sdk\sdk\platform-tools>fastboot format system\ formatting 'system\' partition... FAILED (remote: unknown command) FAILED (remote: unknown command) finished. total time: 0.006s C:\sdk\sdk\platform-tools>fastboot format userdata formatting 'userdata' partition... FAILED (remote: unknown command) FAILED (remote: unknown command) finished. total time: 0.006s Click to expand... Click to collapse
BukeR00 said: Yes, I have unlocked bootloader, but comands still don't work. //edit: Click to expand... Click to collapse hmmm. well if we cannot format the partitions then we are not going to have much luck :/ ok lets try a different tactic. download this and rename it to just recovery.img . then place it into your adb folder and then issue the following command via fastboot. Code: fastboot boot recovery.img hopefully this will allow you to boot into clockworkmod recovery. when you enter clockworkmod recovery use the volume buttons to move and the trackball to select, power is back. format everything. then try to mount your sdcard using advanced/mount storage or sdcard, something to that effect. then place this file onto it. all going well you should be able to then flash this rom. dismount the usb storage, then go back to the main menu (power button) then go to flash/install, select choose zip and then the zip file we placed there. hopefully the recovery will install without issue. then, open the copy of the rom you downloaded on your pc and extract the boot.img. reboot the phone into fastboot and then use the command fastboot flash boot boot.img all going well this rom will boot and you will have a working phone again.
Unfortunately, it does not change anything. I can not enter into Clockworkmod recovery. The keys are not working
BukeR00 said: Unfortunately, it does not change anything. I can not enter into Clockworkmod recovery. The keys are not working Click to expand... Click to collapse it should boot into cwm automatically, no button intervention required.
Unfortunately does not turn ClockworkMod. Phone lay two days without batteries, has launched today as normal. Everything worked. I wanted to do S-OFF by unrevoked, entered into hboot, the phone resets and hung on the HTC screen. After removing the battery turns on hboot again. In Unrevoked I saw that wrote "ClockworMode Recovery"
BukeR00 said: Unfortunately does not turn ClockworkMod. Phone lay two days without batteries, has launched today as normal. Everything worked. I wanted to do S-OFF by unrevoked, entered into hboot, the phone resets and hung on the HTC screen. After removing the battery turns on hboot again. In Unrevoked I saw that wrote "ClockworMode Recovery" Click to expand... Click to collapse Unrevoked doesnt s-off it only roots and flashes a recovery. Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Bricked device: Cannot unlock, flash, boot, unable to mount partition, missing table
I had lollipop running without real issues for a while. After a complete battery drain, I put it on the charger. Upon trying to turn the device on, it hung on the Google screen showing an unlocked padlock at the bottom.
I tried to see how far I could go, and can boot into fastboot but no further.
I thought I would start the usual flashing process from the start by bringing it back to stock and then back to root. Initially the device was unlocked. I locked it with "fastboot oem lock" the rebooted to bootloader. Now when I run "fastboot oem unlock", the unit freezes up when I select Yes to confirm unlocking the bootloader.
Code:
C:\Android>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (Too many links))
finished. total time: 898.264s
Previously, before I locked it, when I tried to flash recovery & bootloader, I received "FAILED (remote: flash write failure)" and "fastboot FAILED (remote: Partition table doesn't exist)" errors. Now, I cannot try to reflash because I can't get unlocked ("FAILED (remote: Bootloader is locked.)")
Current status:
Code:
C:\Android>fastboot-toolkit oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) SB=Y
OKAY [ 0.016s]
finished. total time: 0.016s
integramodder said:
I had lollipop running without real issues for a while. After a complete battery drain, I put it on the charger. Upon trying to turn the device on, it hung on the Google screen showing an unlocked padlock at the bottom.
I tried to see how far I could go, and can boot into fastboot but no further.
I thought I would start the usual flashing process from the start by bringing it back to stock and then back to root. Initially the device was unlocked. I locked it with "fastboot oem lock" the rebooted to bootloader. Now when I run "fastboot oem unlock", the unit freezes up when I select Yes to confirm unlocking the bootloader.
Code:
C:\Android>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (Too many links))
finished. total time: 898.264s
Previously, before I locked it, when I tried to flash recovery & bootloader, I received "FAILED (remote: flash write failure)" and "fastboot FAILED (remote: Partition table doesn't exist)" errors. Now, I cannot try to reflash because I can't get unlocked ("FAILED (remote: Bootloader is locked.)")
Current status:
Code:
C:\Android>fastboot-toolkit oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) SB=Y
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
Same exact thing happened to mine last week. I've followed the exact same steps as you with no luck..Maybe some has recovered from this?????
zerocool00 said: Same exact thing happened to mine last week. I've followed the exact same steps as you with no luck..Maybe some has recovered from this????? Click to expand... Click to collapse So was this a Google OTA update that caused this?
integramodder said: So was this a Google OTA update that caused this? Click to expand... Click to collapse Anyone else have any suggestions?
Can't get bootloader unlocked
Trying to unlock the bootloader, got my Unlock_code.bin file, but when I try to use it I get this error message: C:\Users\Will\Desktop\fastboot>fastboot flash unlocktoken unlock_code.bin target reported max download size of 800000000 bytes sending 'unlocktoken' (0 KB)... OKAY [ 1.007s] writing 'unlocktoken'... (bootloader) flash unlocktoken (bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp (bootloader) [KillSwitch] Last Byte is 0X01, enable unlock FAILED (remote: UnlockToken Verify Fail!!) finished. total time: 1.082s And of course when I reboot into bootloader it says it is locked. Tried moving the file with fastboot and the unlock_code file to a couple different places and nothing helped, and rebooting both phone and PC. Any ideas?
willfill said: Trying to unlock the bootloader, got my Unlock_code.bin file, but when I try to use it I get this error message: C:\Users\Will\Desktop\fastboot>fastboot flash unlocktoken unlock_code.bin target reported max download size of 800000000 bytes sending 'unlocktoken' (0 KB)... OKAY [ 1.007s] writing 'unlocktoken'... (bootloader) flash unlocktoken (bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp (bootloader) [KillSwitch] Last Byte is 0X01, enable unlock FAILED (remote: UnlockToken Verify Fail!!) finished. total time: 1.082s And of course when I reboot into bootloader it says it is locked. Tried moving the file with fastboot and the unlock_code file to a couple different places and nothing helped, and rebooting both phone and PC. Any ideas? Click to expand... Click to collapse Did you enable unlocking in dev options? If so, many others who have had an issue with their unlock tokens reported that using a different browser worked for them. Search the forum, there's at least one thread on about it.
Also the error message says your unlock token is 0KB. Are you sure the file is complete? Maybe try redownload it and verify it with an MD5 hash.
I figured it out, it was just that I copied the code to get the unlock file improperly when I was in CMD. I had to copy it, but I had to turn off "enable line wrapping selection" in the cmd properties, when I tried before to copy it I ended up copying a bunch of extra info that I edited out in notepad, and I think that caused an extra space or error to be somewhere in the code, even though it worked on the HTC site. Anyway thank you for the tips guys!
willfill said: Trying to unlock the bootloader, got my Unlock_code.bin file, but when I try to use it I get this error message: C:\Users\Will\Desktop\fastboot>fastboot flash unlocktoken unlock_code.bin target reported max download size of 800000000 bytes sending 'unlocktoken' (0 KB)... OKAY [ 1.007s] writing 'unlocktoken'... (bootloader) flash unlocktoken (bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp (bootloader) [KillSwitch] Last Byte is 0X01, enable unlock FAILED (remote: UnlockToken Verify Fail!!) finished. total time: 1.082s And of course when I reboot into bootloader it says it is locked. Tried moving the file with fastboot and the unlock_code file to a couple different places and nothing helped, and rebooting both phone and PC. Any ideas? Click to expand... Click to collapse Maybe your computer automatically extracted the file or something Sent from my 2PS64 using XDA-Developers mobile app
I had to request unlock multiple times and use different browsers until it finally worked. I believe it finally worked when I completed the process with the MS Edge browser. Sent from my HTC 10 using Tapatalk
XT1670 revert to stock issue
SOLVED I will make a topic about it https://forum.xda-developers.com/g5/help/how-to-revert-moto-g5-xt1670-to-stock-t4183425 Hello, how are you all over there? I here in trouble with this XT1670. I have installed several roms but now i want to go back to the official one, but it dont lock the bootloader. Tried the following command (twice) to lock the bootloader: fastboot oem lock And i get the following result: Code: (bootloader) Flash valid Android images now (bootloader) Then re-run this command to lock OKAY [ 0.016s] finished. total time: 0.016s Now i use the following command: fastboot flash boot boot.img And the following was obtained: Code: target reported max download size of 535822336 bytes sending 'boot' (16384 KB) ... OKAY [0.545s] writing 'boot' ... (bootloader) Security version downgrade (bootloader) Image boot failed validation (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 0.747s I have already tried several. Boot, gpt, oem with official rom. All showing the error "Security version downgrade" I also tried Lenovo's Rescue & Smart app, but it says the SKU is wrong and doesn't recognize the mobile phone. I don't know how to continue. I could put an official rom, but when you restart the phone the bootloader appears. It only starts when press start. Not only does that happen. Every so often, the phone turns itself off and remains in the bootloader. And then when you start up, bug reports pop up to share with who knows what. I do not know what to do. You are the experts. Ty in advance
[solved] lost build.prop -> no more booting
Hello kind saviour, I accidentally deleted my build.prop file and now my phone is stuck on "the boot loader is unlocked and software integrity cannot be guaranteed..." screen at boot. I use the AOSIP rom for OnePlus 7t,if that helps. I do NOT want to lose any data and preferably not lose any system settings either. Updating the ROM is OK for me. Please let me know if that is a good idea however. The good part: fastboot boot TWRP.img works, sdcard data de-cryption works, i can access files with MTP. Already made a backup of most important data. I do not know which AOSIP version I have, but it's not the latest. Doesn't work: fastboot boot magisk-patched.img (image might be too old?) Doesn't work: fastboot reboot fastboot + fastboot boot boot.img -> Error: *FAILED (remote: 'Download is not allowed on locked devices') Booting from A instead of B goes into infinite booting animation. adb commands during twrp don't work No adb access anywhere else I have no backup of build.prop I have a builT.prop file and i suspect i saved it with wrong name (but I still can't access /system partition) I had access to /system partition during first twrp boot, but accidentally mounted it as read only the first time. After following reboots to twrp, system is always unmountable (both from slot a as well as slot b). Even after deleting twrp folder from pc, the system partition remains unmountable: *Failed to mount '/system_root' (Permission denied) *Failed to mount '/vendor' (Permission denied) bootloader is unlocked & phone is rooted with magisk. If you could help me with a solution where i can keep my data you would make me soo happy. Having a rough time with life lately and you could be my second coming of Jesus Thanks in advance.
Dirty flash latest aosip with TWRP or with fastboot
HueyT said: Dirty flash latest aosip with TWRP or with fastboot Click to expand... Click to collapse Thank you! I will try that later today and report back.
I tried dirty flashing the latest AOSIP update, and it made everything worse. (Maybe I was on the wrong slot??) Now there is no fastbootD, no recovery, and neither possible to fastboot boot twrp.img! Only thing that worked was the bootloader (fastboot). I didn't even get the usual "the boot loader is unlocked and software integrity cannot be guaranteed..." screen. However, i changed slot with fastboot and now I have recovery and fastbootD and can boot twrp again. Now I'm really worried about messing up my next steps, so would be super grateful for any help you can give me. I believe we are near a solution here. Big Questions: Should I dirty update the rom from fastbootD or from TWRP? Which *SLOT* do I update from? History of how everything went wrong: Spoiler: command line messages and responses fastboot update OSiP-10-Gapps-hotdogb-20210621-img.zip Code: -------------------------------------------- Bootloader Version...: unknown Baseband Version.....: Serial Number........: 9de0f5c0 -------------------------------------------- extracting android-info.txt (0 MB) to RAM... android-info.txt syntax error: Setting current slot to 'b' FAILED (remote: 'set_active command is not allowed on locked devices') fastboot: error: Command failed fastboot oem device-info Code: FAILED (remote: 'Unable to open fastboot HAL') fastboot: error: Command failed //I manually rebooted to bootloader (fastboot) here// fastboot oem device-info Code: (bootloader) Verity mode: true (bootloader) Device unlocked: true (bootloader) Device critical unlocked: false (bootloader) Charger screen enabled: true (bootloader) enable_dm_verity: true (bootloader) have_console: false (bootloader) selinux_type: SELINUX_TYPE_INVALID (bootloader) boot_mode: NORMAL_MODE (bootloader) kmemleak_detect: false (bootloader) force_training: 0 (bootloader) mount_tempfs: 0 (bootloader) op_abl_version: 0x31 (bootloader) cal_rebootcount: 0x31 OKAY [ 0.050s] Finished. Total time: 0.053s fastboot reboot fastboot Code: Rebooting into fastboot OKAY [ 0.004s] < waiting for any device > fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Update: i found a solution by updating adb/fastboot .exe files, flashing twrp-3-5-1_10-hotdog-sdcardfs.img and dirty flashing the latest aosip image in twrp's fastboot mode I got a "QUALCOMM CrashDump Mode" message once but it boots to aosip now. We will see if the crashdump messages appear again or not.