Locked Bootloader, No Recovery, Stuck in bootloop. Is it dead? - Google Pixel XL Questions & Answers

Hi guys,
Quick backstory: I've got a Pixel XL 3, I sold my Pixel XL on eBay with a description like "PIxel XL, bootlocker unlocked, rooted and blah blah". The user has returned the phone to me claiming it is not working. I've received the device and sure enough it's in some sort of bootloop (although this was definitely not how I sent it to him). This post is not to rant about how I've been shafted by the buyer although I am still furious because I now have a phone which I hope is not actually bricked. (and I know I'd never win a dispute process cause I cannot prove the phone was in a working state when I sent it).
To cut to the chase:
The phone boot loops - it shows the "G" on the white background for less than a second, then reboots, after 2 seconds, it comes back up with the "G" and reboots, and so on.
I can get into fastboot mode. Interestingly, the status shows "Device is LOCKED" - which is definitely NOT how I previously had the phone.
I cant get to recovery mode. It just goes into the boot loop again.
Using the adb tools, I cant issue the "fastboot flashing unlock" or "fastboot oem unlock" commands because it returns: "FAILED (remote: 'oem unlock is not allowed')"
I am unable to get into the phone OS to change the settings because the phone is boot looping
Given the fact I am unable to get to recovery, I am unable to sideload an OTA zip. And given the fact that I cant boot into the OS, I cant enable oem unlocking.
Do I have any hope at resurrecting this phone in any way?

wizzkidd said:
Hi guys,
Quick backstory: I've got a Pixel XL 3, I sold my Pixel XL on eBay with a description like "PIxel XL, bootlocker unlocked, rooted and blah blah". The user has returned the phone to me claiming it is not working. I've received the device and sure enough it's in some sort of bootloop (although this was definitely not how I sent it to him). This post is not to rant about how I've been shafted by the buyer although I am still furious because I now have a phone which I hope is not actually bricked. (and I know I'd never win a dispute process cause I cannot prove the phone was in a working state when I sent it).
To cut to the chase:
The phone boot loops - it shows the "G" on the white background for less than a second, then reboots, after 2 seconds, it comes back up with the "G" and reboots, and so on.
I can get into fastboot mode. Interestingly, the status shows "Device is LOCKED" - which is definitely NOT how I previously had the phone.
I cant get to recovery mode. It just goes into the boot loop again.
Using the adb tools, I cant issue the "fastboot flashing unlock" or "fastboot oem unlock" commands because it returns: "FAILED (remote: 'oem unlock is not allowed')"
I am unable to get into the phone OS to change the settings because the phone is boot looping
Given the fact I am unable to get to recovery, I am unable to sideload an OTA zip. And given the fact that I cant boot into the OS, I cant enable oem unlocking.
Do I have any hope at resurrecting this phone in any way?
Click to expand...
Click to collapse
If you can boot fastboot mode:
This is may work:
- Download the latest SDK Platform-tools (r28.0.3)from here to your computer.
- Download the latest Pixel XL (marlin) Factory Image ( May 2019) to your Computer.
- Install the SDK Platform-tools.
- Extract the Pixel XL (marlin) Factory Image in the Platform-tools folder.
Note: If you have your Pixel 3 XL Factory Image (crosshatch) extracted in the Platform-tools folder. Move the flash-all.bat, flash-all.sh and flash-all.base to another folder before extracting the Pixel XL (marlin) Factory Image to the Platform-tools folder.
- Open a Command prompt in the Platform-tools folder #1 in the guide
- Type flash-all
- If it works, it should boot.
- login to your google account and set up your phone.
[Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76
Then if you purchased you Pixel XL from Google Do #3 to unlock the bootloader.

Thanks Homeboy76 for taking the time to provide a detailed response. However unfortunately this did not work. I tried it already (but with what possibly could have been an older version of the platform tools and older factory image). So I gave it another shot using platform-tools r28.0.3 and the marlin factory image version 9.0.0 (PQ3A.190505.001, May 2019).
The results were the same as my previous attempt. I get several errors on certain commands in the flash-all.bat file. These all provide a error responses complaining about the bootloader, my guess is because it is locked and using flash-all requires an unlocked bootloader. Whereas a side-load is said to work regardless of it being locked, but is only possible via recover (which isn't working for me). For clarity, the out put of flash-all looks like this:
Sending 'bootloader_a' (32424 KB) OKAY [ 0.789s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.013s]
Finished. Total time: 0.016s
Sending 'radio_a' (57156 KB) OKAY [ 1.400s]
Writing 'radio_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.007s]
Finished. Total time: 0.012s
--------------------------------------------
Bootloader Version...: 8996-012001-1812132253
Baseband Version.....: 8996-130181-1811270246
Serial Number........: HT69L0203996
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.047s]
Checking 'version-bootloader' OKAY [ 0.047s]
Checking 'version-baseband' FAILED
Device version-baseband is '8996-130181-1811270246'.
Update requires '8996-130281-1903110834'.
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse
Random question. How did this guy manage to lock the bootloader when it was unlocked by me using 'dePixel8' a very long time ago. He did question why the phone was starting up with the warning message, and I explained that it's by design because the bootloader is unlocked. I guess he decided to try and "fix" that, and ended up screwing up this phone. Hence sending it back with a fake story.

wizzkidd said:
Thanks Homeboy76 for taking the time to provide a detailed response. However unfortunately this did not work. I tried it already (but with what possibly could have been an older version of the platform tools and older factory image). So I gave it another shot using platform-tools r28.0.3 and the marlin factory image version 9.0.0 (PQ3A.190505.001, May 2019).
The results were the same as my previous attempt. I get several errors on certain commands in the flash-all.bat file. These all provide a error responses complaining about the bootloader, my guess is because it is locked and using flash-all requires an unlocked bootloader. Whereas a side-load is said to work regardless of it being locked, but is only possible via recover (which isn't working for me). For clarity, the out put of flash-all looks like this:
Random question. How did this guy manage to lock the bootloader when it was unlocked by me using 'dePixel8' a very long time ago. He did question why the phone was starting up with the warning message, and I explained that it's by design because the bootloader is unlocked. I guess he decided to try and "fix" that, and ended up screwing up this phone. Hence sending it back with a fake story.
Click to expand...
Click to collapse
Darn CRS ( Can't Remember S#@t) your original post did say the bootloader was locked.
Locking the bootloader is easy but , if he locked the bootloader without returning the phone to 100 percent stock. He most likely bricked the phone.

I had a guy screw up a phone the day he got it. Luckily he admitted to everything and did not try to return.
I bet you can get this guy to admit fault if you try hard enough.
Sent from my SM-P205 using Tapatalk

Did you every find a way to fix the issue? I'm in the EXACT same boat with a Pixel 3 XL stuck in a boot loop. Only thing I can access is Fastboot. My scenario is EXACTLY how you described yours.

Related

Stock Robin endless reboots, not OEM unlocked

My Robin is now endless booting - splash screen, teal Robin screen, then I see the OS for a sec then it does it all over again. I am/was running latest Stock Android/Nextbit rom from OTA updates. Nothing fancy, not unlocked, not rooted. Developer was enabled but not OEM unlocking (I don't think).
I tried a few things today - installed USB drivers, downloaded ADB package and the Nextbot ROM. I can get to fastboot and recovery mode but not sure how to proceed. Fastboot sees the phone attached to my PC from commandline. I tried the instructions to flash stock but I get
Code:
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: NBQGLMB650302177
--------------------------------------------
sending 'boot' (12413 KB)...
OKAY [ 0.431s]
writing 'boot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.580s
I also tried
Code:
C:\1tmp\nextbit\N108>fastboot -i 0x2c3f oem unlock
...
FAILED (remote: oem unlock is not allowed)
Any advice? I don't care if I lose everything on the phone - it was all backed up. I just want my Robin working again!
If its unticked in dev settings, I don't know how you gonna get around this.
But before trying the fancy '-i 0x2c3f' to unlock have you tried the basic oem unlock code without that code? fastbook oem unlock?
Only few Robins require that fancy command others don't need it. Mine doesn't.
Also you said you do see the OS for a second you mean literally a second? Keep it plugged in at boot and see if that extends that time enough to tick OEM unlock.
Turns out I was overthinking it. I just did the factory restore from the recovery menu and I'm back up and running again.
Ha! Thats good to know.

HELP! Pixel 2 XL may be bricked

Long story short, I attempted to flash the first 9.0.0 factory image and now my phone is seemingly bricked. I keep getting errors that say that fastboot can't detect the current slot. When I try to manually select the slot with --set-active=a/b it returns with my device doesn't support slots. If I try to flash anything individually like the bootloader/radio cmd/powershell just sits there with the "_" underscore blinking for all eternity. TWRP is already flashed and when I try to boot to it it sits on the splash screen indefinitely. I can't fastboot boot TWRP either because I can't flash anything. Deuce's script did the same thing. I tried 3 different cables and am using a brand new computer and latest Platform Tools.
Should I contact google for a warranty replacement? I don't have the order # but that should be irrelevant I think since this phone is still under a year old.
Any ideas????
fastboot: error: Failed to identify current slot
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.003s
fastboot: error: Failed to identify current slot
rebooting into bootloader OKAY [ 0.004s]
Finished. Total time: 0.004s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ12g
getvar:version-baseband FAILED (remote: unknown command)
fastboot: error: requirements not met!
Press any key to exit...
Update: I installed Android Studio and subsequently, the USB drivers from the SDK manager and somehow I got the phone to boot again. I still cannot flash anything though, I still get the "unable to identify current slot error above.
I hate the the windows Powershell. I always open a command window and work from that.
Make sure you have the most current drivers, and that USB debugging is turned on.
From the horror stories I've read, i always always always do an adb or fastboot devices before i do anything.
If you flash a factory image, don't unzip the file inside the factory image. The flash all.bat file expects that zip to be there.
I've also gotten into the habit of booting the phone that has just been flashed before I root it.
Have you wiped the cache's? Done a reset?
Just throwing things out there...
Good luck I hope you get it all sorted out.

Bricked even though I can fastboot?

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?

unable to flash twrp onto recovery or vbmeta(img verification removed vbmeta) on vbmeta partition

so recently ive tried again to root my motorola g5s (not plus) and after unlocking the bootloader which took like 5 mins, i ran into a problem, i did get the right twrp img for my motorola yet when i try to flash it onto the recovery like ive been told to, it says img unsigned or corrupted, ive asked in the r/AndroidRoot discord and nothing worked. Not too long after i went online on forums to try and find a way to get this fixed, ive seen that appearently even if it says img unsigned or corrupted, to try "fastboot boot twrp.img" while that did get the phone to boot, it booted into normal Android OS, so next i was told to try to flash a vbmeta.img with the verifications removed onto the vbmeta partition but got this error:
(bootloader) is-logical:vbmeta: not found Sending 'vbmeta' (0 KB) OKAY [ 0.165s] Writing 'vbmeta' (bootloader) Invalid partition name vbmeta FAILED (remote: '') fastboot: error: Command failed
ive taken some screenshots of the cmd window in hopes of that helping to find whats wrong ill attach em(theyre named by me smashing my head against the keyboard because it doesnt work)
antipositive said:
so recently ive tried again to root my motorola g5s (not plus) and after unlocking the bootloader which took like 5 mins, i ran into a problem, i did get the right twrp img for my motorola yet when i try to flash it onto the recovery like ive been told to, it says img unsigned or corrupted, ive asked in the r/AndroidRoot discord and nothing worked. Not too long after i went online on forums to try and find a way to get this fixed, ive seen that appearently even if it says img unsigned or corrupted, to try "fastboot boot twrp.img" while that did get the phone to boot, it booted into normal Android OS, so next i was told to try to flash a vbmeta.img with the verifications removed onto the vbmeta partition but got this error:
(bootloader) is-logical:vbmeta: not found Sending 'vbmeta' (0 KB) OKAY [ 0.165s] Writing 'vbmeta' (bootloader) Invalid partition name vbmeta FAILED (remote: '') fastboot: error: Command failed
ive taken some screenshots of the cmd window in hopes of that helping to find whats wrong ill attach em(theyre named by me smashing my head against the keyboard because it doesnt work)
Click to expand...
Click to collapse
What does getvar all say? remove imei before posting
Code:
fastboot getvar all
sd_shadow said:
What does getvar all say? remove imei before posting
Code:
fastboot getvar all
Click to expand...
Click to collapse
Ill check that tomorrow after installing the new battery, what's imei?
So in cmd i just type "fastboot getvar all" in the platform-tools folder?
antipositive said:
Ill check that tomorrow after installing the new battery, what's imei?
So in cmd i just type "fastboot getvar all" in the platform-tools folder?
Click to expand...
Click to collapse
sd_shadow said:
What does getvar all say? remove imei before posting
Code:
fastboot getvar all
Click to expand...
Click to collapse
...bad news, the battery was replaced... Part of the backlight is ****ed but so little it doesnt matter, yet the entire bottum of the screen with the three buttons, its unresponsive altho it worked shortly after the replacement was finished, now it just stopped working. Idk if its even worth at that point to even replace the screen, really depends on the cost ngl but as of now i put the rooting on ice.
Youll hear from me again soon maybe.

Coming back to an old problem

Hello,
Many many many moons ago i decided to try install LineageOS on my old pixel c, then the world when weird and the tablet has lived in a drawer, today it came out and i can't remember where i got up to so looking for guidance before i kill it.
This is what i do know:-
1. Doesn't have an OS as it won't boot properly
2. Get to a recovery menu but trying to boot to "Android recovery" doesn't work (just reboots)
3. Message in the recovery menu states "OS on your tablet is damaged. Needs Recovery" this is along side the Product name, Hardware Version, Bootloader Version and Lock State.
And advice on where to start very much appreciated.
I took another punt at this, tablet is "waiting for fastboot command...." from my mac when attempting to write the recovery image using the following: ./fastboot flash recovery twrp-3.7.0_9-1-dragon.img from my Mac i hit the following error:-
Sending 'recovery' OKAY
Writing 'recovery' FAILED (remote: 'unsupported command')
fastboot: error: command failed
./fastboot oem unlock says it is unlocked already

Categories

Resources