I'm using this guide and changing the file names for the LTE version based on the mysid-itl41d factory files google released. I need to unroot my phone to swap it after realizing the screen has a green washed out tint. I'm getting stuck trying to flash the actual zip file due to an error below:
Code:
C:\nexus>fastboot-windows flash radio radio-cdma-toro-i515.ek01.img
sending 'radio' (3704 KB)... OKAY
writing 'radio'... OKAY
C:\nexus>fastboot-windows -w update image-mysid-itl41d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKJ10
Baseband Version.....: I515.EK02
Serial Number........: 014691491501C017
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
checking version-cdma... FAILED
Device version-cdma is 'I515.EK05'.
Update requires 'I515.EK01'.
I tried pushing the CDMA radio to the phone but the version doesn't seem to update. Does anyone know how to resolve this?
evahnyird said:
I'm using this guide and changing the file names for the LTE version based on the mysid-itl41d factory files google released. I need to unroot my phone to swap it after realizing the screen has a green washed out tint. I'm getting stuck trying to flash the actual zip file due to an error below:
Code:
C:\nexus>fastboot-windows flash radio radio-cdma-toro-i515.ek01.img
sending 'radio' (3704 KB)... OKAY
writing 'radio'... OKAY
C:\nexus>fastboot-windows -w update image-mysid-itl41d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKJ10
Baseband Version.....: I515.EK02
Serial Number........: 014691491501C017
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
checking version-cdma... FAILED
Device version-cdma is 'I515.EK05'.
Update requires 'I515.EK01'.
I tried pushing the CDMA radio to the phone but the version doesn't seem to update. Does anyone know how to resolve this?
Click to expand...
Click to collapse
You're not flashing the radio correctly and the script is bombing on the radio check. In the package itself there is an flash-all script that will enumerate the steps needed.
This is not correct: fastboot-windows flash radio radio-cdma-toro-i515.ek01.img
Again, if your binary is named fastboot-windows then use that, the radio is the issue. That's radio-cdma, not radio.
If you want to do it manually here are the steps:
You need to flash the CDMA Radio
Code:
fastboot flash radio-cdma radio-cdma-toro-i515.ek01.img
Then flash the (LTE?) Radio
Code:
fastboot flash radio radio-toro-i515.ek02.img
The automatic script also flashes the boot loader
Code:
fastboot flash bootloader bootloader-toro-primekj10.img
The use the provided ZIP:
Code:
fastboot -w update image-mysid-itl41d.zip
If you extract that zip you can also manually flash boot, recovery, system and userdata
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
I knew I was doing something wrong... how exactly do I run the script? I'm a little new to using cmd to flash everything since I used odin primarily with my fascinate. Thanks!
Edit: do I type "sh flash-all.sh" ?
evahnyird said:
I knew I was doing something wrong... how exactly do I run the script? I'm a little new to using cmd to flash everything since I used odin primarily with my fascinate. Thanks!
Click to expand...
Click to collapse
It's a bash script, so if you're in windows you don't
Just do it manually
fastboot flash bootloader bootloader-toro-primekj10.img
fastboot flash radio-cdma radio-cdma-toro-i515.ek01.img
fastboot flash radio radio-toro-i515.ek02.img
fastboot -w update image-mysid-itl41d.zip
The script reboots back into the boot loader after each flash:
fastboot reboot-bootloader
I've flashed with fastboot many times and never did that, but it won't hurt anything.
It worked perfectly the second time around. Thanks a million!
THANK YOU THANK YOU!!! I soft bricked my device this morning by flashing an incorrect update.zip and following these steps, after trying just about everything else, was the only way I could restore it.
Of course I had stupidly wiped my Nandroid backup when I tried a wipe to fix things. Due to the lack of a memory card, a full wipe takes out your Nandroid backups too! I forsee this causing lots of drama on these boards in the future, unless someone finds a way to access the internal storage while in recovery mode (from a computer that is).
Hi,
thank you for response,
i had problem at this line:
fastboot flash radio-cdma radio-cdma-toro-i515.ek01.img
look that picture in the atonement it explained my problem ..
So I ran into trouble while trying to root and am having trouble flashing the stock images. I downloaded the factory images (4.3 (JLS36C)) from google. Flashing the bootloader image(bootloader-deb-flo-03.14.img) seems to work just fine but when I try to update to the provided "image-razorg-JLS36C.zip" I have trouble. I read that the radio included (radio-deb-deb-g00_1.23.0_0720.img) is the wrong one but then found conflicting information that it is just mis-named. I tried renaming the file to the the baseband that is being requested (DEB-G00_2.25.1_0802) but that didn't work either and I can't locate that specific file to add to the directory.
Below is the log from terminal, I highlighted everything that throws errors. I also tried using the WugFresh tool through parallels and got the same issues. Is it something simple I'm missing? It feels really close to working. Please let me know how I can fix this, thanks for your time.
**Edit: I also tried flashing only the baseband radio ./fastboot flash radio "file" to the file that was included in the google download but it still threw the same errors.**
Code:
Last login: Fri Sep 27 23:44:48 on ttys000
cpe-75-85-155-82:~ kyler$ cd Downloads
cpe-75-85-155-82:Downloads kyler$ cd "android tools"
cpe-75-85-155-82:android tools kyler$ ./fastboot flash bootloader bootloader-deb-flo-03.14.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.134s]
writing 'bootloader'...
OKAY [ 1.334s]
finished. total time: 1.469s
cpe-75-85-155-82:android tools kyler$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.005s
cpe-75-85-155-82:android tools kyler$ ./fastboot -w update image-razorg-JLS36C.zip
[B]archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'[/B]
--------------------------------------------
Bootloader Version...: FLO-03.14
[B]Baseband Version.....: DEB-[/B]
Serial Number........: 08664aa9
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
[B]checking version-baseband...
FAILED
Device version-baseband is 'DEB-'.
Update requires 'DEB-G00_2.25.1_0802'.[/B]
finished. total time: 0.024s
cpe-75-85-155-82:android tools kyler$
Might want to try using the flashall.sh script (I think that is the name, but should be in the main directory of image). Have not tried it on my deb yet, but has always worked for my other nexus devices, including flo.
Sent from my Nexus 7 using Tapatalk 4
pudgewack said:
Might want to try using the flashall.sh script (I think that is the name, but should be in the main directory of image). Have not tried it on my deb yet, but has always worked for my other nexus devices, including flo.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Wow thanks, that worked great. Strange though because as I looked at the commands earlier in the script they were the same as the ones I was trying to use manually to fix it in the first place.
From flash-all.sh:
Code:
./fastboot flash bootloader bootloader-deb-flo-03.14.img
./fastboot reboot-bootloader
sleep 5
./fastboot flash radio radio-deb-deb-g00_1.23.0_0720.img
./fastboot reboot-bootloader
sleep 5
./fastboot -w update image-razorg-JLS36C.zip
Well I guess there must be something I'm missing... The log is still throwing the errors:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
So if you know how I could fix that it would be great, otherwise the device seems to be working properly.
[email protected] said:
Wow thanks, that worked great. Strange though because as I looked at the commands earlier in the script they were the same as the ones I was trying to use manually to fix it in the first place.
From flash-all.sh:
Code:
./fastboot flash bootloader bootloader-deb-flo-03.14.img
./fastboot reboot-bootloader
sleep 5
./fastboot flash radio radio-deb-deb-g00_1.23.0_0720.img
./fastboot reboot-bootloader
sleep 5
./fastboot -w update image-razorg-JLS36C.zip
Well I guess there must be something I'm missing... The log is still throwing the errors:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
So if you know how I could fix that it would be great, otherwise the device seems to be working properly.
Click to expand...
Click to collapse
Earlier you didn't flash in the same sequence.
Earlier you flashed
bootloader-deb-flo-03.14.img
image-razorg-JLS36C.zip
The script flashes
bootloader-deb-flo-03.14.img
radio-deb-deb-g00_1.23.0_0720.img
image-razorg-JLS36C.zip
When you flash image-razorg-JLS36C.zip, it verifies the radio you have *installed* on the tablet is the version required. Since you never flashed the radio earlier, the check failed. Later you tried to rename it, which does no good because renaming it isn't installing it, and the version check to see what you have installed failed again.
I am only commenting on the log you posted. You mention in the edit that you flashed the radio but didn't post the log, so I can not be sure what you did achieved what you intended.
The missing .sig errors are normal. Google didn't sign their factory images, which is why you need to be bootloader unlocked to factory restore.
Hello all,
My Nexus 7 (2013) was bricked about a year ago by a google update, like many other. I just got around looking into it now. I'm having some trouble as you may have guessed.
Here's the current state of affairs :
Cannot get past the white Google logo
Can boot into fastboot
fastboot is locked
bootloader version is FLO-04.02
Can boot into recovery mode
factory reset fails on mounting /cache
Here's what I've tried so far, from several sources here and there
Download Official Android image and run a flash-all.sh
unlock the bootloader with `fastboot oem unlock`
factory reset from recovery mode
All of these end up failing because bootloader is locked or because it freezes (most often at some kind of wiping data step).
This is the output of the `.flash-all.sh` command.
Code:
floby $ ./flash-all.sh
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.005s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 07cd6455
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-04.02'.
Update requires 'FLO-04.05'.
finished. total time: 0.019s
I cannot post links but here is what it looks like:
image svRKQ5g on imgur
image y5Pa3br on imgur
Do you have any idea how I can unbrick this ?
Thank you all in advance.
Hello,
does anyone have any idea to help me ?
Floby said:
Hello,
does anyone have any idea to help me ?
Click to expand...
Click to collapse
It looks like bootloader 4.02 wasn't written correctly. Get bootloader 4.05 and push it to see if that fixes the issue. IIRC, bootloader 4.05 is part of android 5.1.1. I'm not sure which factory image you're trying to install, but start by addressing the error and push bootloader 4.05 before anything else.
quickdraw86 said:
It looks like bootloader 4.02 wasn't written correctly. Get bootloader 4.05 and push it to see if that fixes the issue. IIRC, bootloader 4.05 is part of android 5.1.1. I'm not sure which factory image you're trying to install, but start by addressing the error and push bootloader 4.05 before anything else.
Click to expand...
Click to collapse
Thanks for your reply, I was indeed getting new binaries from the latest 5.x release. I'll try and push the new bootloader and post updates.
Hi everyone, I'm using fastboot 1:7.0.0+r33-2 (latest version in repo) on Ubuntu 18.04 and i can't change active slot :
Code:
$ fastboot getvar current-slot
current-slot: _b
$ fastboot set_active a
Slot a does not exist. supported slots are:
(just empty lines)
Bootloader is unlocked.
Can anyone confirm that there is a problem with that particular version ? I can't check with the one from SDK Platform Tools at the moment - maybe it's OK with it.
BTW, it is possible to switch slot with locked bootloader ?
Bootloader Version...: 00872-LAHAINA-2.487493.1
Baseband Version.....: 00781-LC_ALL_PACK-1
Serial Number........: f2e1c7ed
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in merging state')
fastboot: error: Command failed
Please help me
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