So if I want to unlock the bootloader on day 1, I just have to boot into fastboot mode, plug into my computer, start adb, and then run "fastboot oem unlock"? I've never had a nexus before so I'm not sure if this is the right procedure.
Not quite. Previously this would have been the case but now you have to boot the phone first. You can skip all of the configuration stuff because all you need to do is get into Developer Settings and flip the Enable OEM Unlock toggle. Then you can reboot into bootloader and run fastboot oem unlock. This is of course assuming that you have the correct drivers in Windows or the correct package in Linux.
Related
Stuck at google splash screen, ADB doesn't list devices with "ADB Devices" command
I was using Masgisk. I followed the steps from masgisk to restore before i took the OTA. The ota moved to step 2 but then restarted. Now i am stuck at the splash screen. I can get reboot to the bootloader but after I lauch my CMD from the platform tools window and use the command "ADB Devices" nothing is listed. I don't remember enabling usb debugging prior to this. Is there anything i can do to flash something that will not erase my data. If not is there any way i can flash the factory image?
angelino0919 said:
I was using Masgisk. I followed the steps from masgisk to restore before i took the OTA. The ota moved to step 2 but then restarted. Now i am stuck at the splash screen. I can get reboot to the bootloader but after I lauch my CMD from the platform tools window and use the command "ADB Devices" nothing is listed. I don't remember enabling usb debugging prior to this. Is there anything i can do to flash something that will not erase my data. If not is there any way i can flash the factory image?
Click to expand...
Click to collapse
Is your bootloader "fully" unlocked?? Have you tried side loading the OTA? It will not wipe data. From bootloader mode, type in fastboot devices to see if you get your phone ID displayed. The USB debugging part is what's worrying me though! Is OEM unlocking checked off in developer options at least??
Badger50 said:
Is your bootloader "fully" unlocked?? Have you tried side loading the OTA? It will not wipe data. From bootloader mode, type in fastboot devices to see if you get your phone ID displayed. The USB debugging part is what's worrying me though! Is OEM unlocking checked off in developer options at least??
Click to expand...
Click to collapse
Thank you for your reply, yes device state is unlocked and when I use fastboot devices I see something but not when I use adb devices
Edit: I was able to restore the factory image thank you though
Hi,
I am using my Nextbit Robin Oem Unlock from last 1 year but today i decided to go back to stock with locked Oem.
I flashed the stock rom and locked the Oem at the same time but when i restarted the phone it got stuck at the boot.
So I went ahead with the 'fastboot oem unlock' command, and here's the problem. All flashing command returns FAILED <remote: device is locked...>.
fastboot oem device-info reads: Device tampered: false, Device unlocked: false. So bootloader is locked. At this point I assume that the bootloader is unlocked, but revert back to locked after reboot (the phone automatically rebooted after executing oem unlock command, so can't get around that).
Tried numerous other methods, using different adb files, no dice. Can't even flash TWRP. Tried adb sideload, same. Tried executing fastboot oem unlock with various different parameter, still locked after reboot. I cannot flash anything into locked bootloader.
Google researched it for few hours, same problem happened to other phones from other manufacturers that came returned from warranty replacement with modified motherboard; OR tampered/broken eMMC/NAND flash. But no such case for Nextbit Robin (yet?).
Pretty hopeless right now since I just found out that Nextbit Robin support ended on Aug 1st.
Guess I'm stuck with locked bootloader and no cell signal phone. Unless someone can help. One can always hope.
Anyway, thanks for reading.
Mukul_Meena said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post76659814
Click to expand...
Click to collapse
If you bootloader is unlocked I think you can give a try to the Nextbit's Unbrick Tool
As you want to go back to stock , I think this is a good idea.
Now if your bootloader isn't unlocked there is unfortunately nothing I can do for you , unless you unlock it .
Edit #1: If your bootloader is locked , go to bootloader mode by pressing volume down + power button for about 20 seconds and try to see the bootloader state with fastboot commands. If it is unlocked , follow the process in the @nextbitKhang's thread .
Yes that's the main issue. Oem is Locked.
Is there any Oem unlock code i can use to unlock from ADB?
I don't think so ,I'm not sure, but I hope you'll find one.
On your Robin go to settings > system > about phone > tap build number until it shows developer options.
Go into developer options which is in settings > system > developer options.
Make sure OEM unlocking is enabled. (for good measure disable then re-enable)
Also make sure usb debugging is enabled. Have the Robin plugged into a computer so you can enable to pop-up on Robin asking for access for the computer.
Once they are both enabled shut down your phone. Turn it back on while pressing vol down+power and plugged into your computer.
In adb run command fastboot oem unlock
please i'm experiencing the same issue not on nextbit but on GIonee.
i have re-activate both OEM unlocking and USB debugging several times but it all void
same error: Remote: OEM unlock is not allowed
please kindly help
So... I have been stuck with a HTC One E9+ for many months with a lock screen that I literally can't unlock, and flashed TWRP but can't be used because of locked bootloader, I had finally discovered a way to get the unlock token. Here's a little bit of story. I tried to run 'fastboot oem get_identifier_token' in bootloader mode, but the phone returned unknown command. I had tried that when everything was normal. I had check the settings in developer options, and there is nothing related to unlocking bootloader inside there. Until recently, I had discovered 'fastboot oem rebootRUU' from other blog post.
All in all, if you couldn't get the bootloader unlock token in bootloader mode, try to get it in RUU mode.
Good luck!
Hi, i tried to run the command "fastboot oem rebootRUU" but no code appeared.
A chain of unfortunate(or reckless) events led to my soft bricked Robin. This is the current state of the device:
Does not boot normally, stuck at boot loop.
Have access to fastboot mode and Stock recovery.
No access to adb.
Device is OEM Locked and does not allow flashing anything from Fastboot.
What are my options? I have seen posts for other devices where they toggle OEM Lock status from Fastboot
Also some other cases where they use QFIL to flash stock OS.
Please advise.
Can unlock the boot loader with
Code:
fastboot -i 0x2c3f oem unlock
Did you get the drivers n stuff?
(apologies if you know all that).
Ive had my LG G7 for about a year now. I managed to unlock the bootloader without any problems and used magisk ok.
I just came to upgrade the firmware without any problems. I enabled dev and usb debug but the 'Enable oem unlock' button is greyed out and displays "bootloader already unlocked" ok so not a problem - that is until I come to access the bootloader again.
Here is the message:
Welcome to Fastboot mode: Please check "Enable OEM unlock" in developer options
adb commands no longer work at this point as connection is lost. Only choice is manually reboot or switch off.
WTF now what. Im unable to root or restore the bootloader. So even though its unlocked and displays the bootloader unlocked message when booting - Fastboot does not see it and it still wants me to 'Enable oem unlock' but its greyed out.
Any suggestions please anyone
You can use QFIL to restore laf_a & laf_b. Then flash full rom (Refurbish) in Download mode.
ps: the reason is you do not flash full rom after unlock bootloader in order to tell to the machine that you are in the illegal mode kakaka.
Thanks for your reply nttuan. I just about gave up hope. Im totally paranoid without root. No decent firewall, cant freeze garbage etc.
Being relatively unsure, would you mind going over the QFIL method with me.
Thanks
chadandchew said:
Thanks for your reply nttuan. I just about gave up hope. Im totally paranoid without root. No decent firewall
Click to expand...
Click to collapse
Never used QFIL before. Where do I get the firehose elf file from. I noticed a couple of elf files in the extracted folder, is it one of these.
Do I have to create any xml files and do I have to rename any of the kdz extracted files?
Some posts are a bit old and for other models.
Instead of flash the boot_a from magisk_patched image, you can use command
fastboot boot magisk_patched.img
and use the LGUP to reflash the firmware.
If you look at the photo above I LOSE ALL ADB commands after adb reboot bootloader.
fastboot boot magisk_patched.img or any other command just displays "Waiting For any Device" in CMD window.
This is my problem because the bootloader is already unlocked and oem greyed out - it is asking me to "Enable OEM Unlock"
I am wanting to either root the phone or restore bootloader to locked. Sorry for any confusion
type fastboot devices and show me the result.
maybe you do not have correct fastboot driver
It did say waiting for any device but now its gone from bad to worse. I followed this guide Here and now all I get is fastboot screen, see photo. If I now try fastboot devices then fastboot flash boot_a magisk_patched.img it shows error which does not look good actually , photo 2. Cant get download mode. If I try to get it by holding volume button and inserting usb lead I get this nasty screen, photo 3. I think that some of the partitions may have been overwitten. . Stupid move on my part.
Forgot to mention - EDL is still accessable
Ive managed to sort the above problem
QFIL flashed only the following 6 files :
abl_a and abl_b
laf_a and laf_b
boot_a and boot_b
Phone rebooted perfectly after this.
Thanks for your advice