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.
Related
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.
Days past I successfully unlocked the bootloader on my girlfriend's Taimen handset, flashed TWRP etc etc. No hitches whatsoever. I bought another for myself via the Google Store.
I booted it up today. As was on hers, OEM Unlock is prevented until I allow the handset to update to 8.1.
Done. OEM unlock then accessible and enabled.
I used my girlfriend's same PC with the same Minimal ADB and Fastboot, rebooted to fastboot and execute
Code:
fastboot flashing unlock_critical
Are you sure? ...volume up/down and power button to commit. Done. The unlock appeared successful as it rebooted to the out of box setup routine again.
I transferred the TWRP zip to the handset and rebooted to fastboot. Upon executing the command to temp boot TWRP from the IMG file fastboot
Code:
boot path "C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.2.1-2-taimen.img"
I got the following response...
Code:
downloading 'boot.img'...
OKAY [ 0.870s]
booting...
FAILED (remote: Can not boot in Lock State)
finished. total time: 0.873s
Sure enough I look down at the handset and the fastboot menu reflects it's locked again. Weird.
I reboot and check OEM unlock. It reflects OEM unlock still toggled on. I go back to fastboot and again execute
Code:
fastboot flashing unlock_critical
Code:
FAILED (remote: Device already : unlocked!)
finished. total time: 0.002s
This is despite fastboot clearly showing "device state - locked"
I regress to dev options and toggle OEM unlock off. Reboot. Toggle OEM Unlock back on.
Same ill behavior.
Am I missing something??
try fastboot flashing unlock
depending on bootloader version you no longer need to fastboot flashing unlock_critical
see here.
@uicnren You a gentlemen and a scholar. Simple as that. Thanks.
Pay_It_Forward_Pete said:
@uicnren You a gentlemen and a scholar. Simple as that. Thanks.
Click to expand...
Click to collapse
:good:
Hey guys, i have to send my Pixel C to repair so i want to lock my bootloader. My Problem is, that i cant enable OEM unlocking in the developer options because its grayed out saying that my bootloader is already unlocked. "fastboot flashing lock" and "fastboot oem lock" both give me the error "FAILED (remote: Enable OEM unlock is not set)".
Is there a workaround for this?
Thanks for your help!
I also have this issue.
Same thing here. I loaded LineageOS and have decided to go back to factory. I can't figure it out either. Here are my results.
fastboot flashing lock
FAILED (remote: Enable OEM unlock is not set)
finished. total time: 0.022s
fastboot flashing unlock
FAILED (remote: Device already unlocked)
finished. total time: 0.003s
fastboot flashing get_unlock_ability
(bootloader) 0
OKAY [ 0.020s]
finished. total time: 0.020s
Ok all, I finally figured it out.
I had to download factory image 6.0.1 (MXB48J) go thru the instructions to flash this image.
Started up in android went thru the min setup to get into Settings and Developer Options. Turn on USB debugging and the OEM Unocking.
adb reboot bootloader
flashboot flashing lock
Prompted me about wiping the device.
Everything is good.
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.
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.