(remote: 'Error getting device locked state No Response')

[Ofuroski]

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!!

 

[boostedduece]

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.

 

[rmckay6]

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.

 

[Ofuroski]

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...

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.

 

[Homeboy76]

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!!

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

 

[jd1639]

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

 

[Ofuroski]

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.

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

 

[Ofuroski]

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?

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

 

[jd1639]

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?

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

 

[Ofuroski]

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

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.

 

[jd1639]

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.

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

 

[Ofuroski]

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

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.

 

[jd1639]

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.

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

 

[Ofuroski]

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

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.

 

[jd1639]

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.

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

 

[v12xke]

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.

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.

 

[Ofuroski]

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.

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

 

[v12xke]

Thanks for your help and info. Here's what getvar posts....

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