I have a Nokia N1 with A5CN51C (i.e. Android 5.0.2), rooted.
The descriptions how to change it to a FM version include a step "unlocking bootloader" but neither does my "developer option" section provide for any such option nor does the "fastboot oem unlock" command work (failes due to "unknown oem command").
Are there other users where this is/has been also the case? What can be done about that? Will the option appear if I upgrade to a higher CN Android version? Has someone done that successfully? Any other options?
Related
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
My razer phone, after the OEM unlock, unlocked it using two-party commands, wrote it into the lineage OS system, and then, cheap, used "fast boot flashing lock_critical" FastBoot flashing lock " After locking the mobile phone, it was found that the "Developer Options" had changed to not allow OEM to unlock. Now the mobile phone is restarted indefinitely, using the "fast boot flash unlock" FastBoot flashing unlock_critical " It can't be unlocked. Unable to write to the official firmware, nor can it start properly! Help, gods! Help me!:crying::crying::crying:
It keeps saying that "Your device has failed a routine safety check and will not boot". I tried flashing almost all .kdz files. The phone just loops and shows me this ****y error message. I tried unlocking the bootloader and failed every time because "Enable OEM unlock" was switched off in Dev. options.
Any solutions?
if you have fastboot, try "fastboot oem unlock" with adb that is. maybe it will work
Pouchon514 said:
if you have fastboot, try "fastboot oem unlock" with adb that is. maybe it will work
Click to expand...
Click to collapse
ADB and Fastboot or two different things. You can't issue a fastboot command with ADB.
"Fastboot OEM unlock" will not work if OEM toggle is or was greyed out.
Ive follow the unlock method on xda for unlocking realme x bootloader... but when i tried to flash the powerd shell comment "fastboot flashing unlock" command the phone get out form fastboot mode and says press any button to reboot and the powerdshell showing ""Comment writing failed"
but the indepth test showing application showing submitted successfully.....!!!!
my fon is 6/64 with chines rom RMX1901_11_A.21
Use cmd prompt instead of powershell. Try other bootloader unlocking commands, I don't remember which worked for me, Google search it
maybe use cmd amd don't forget to turn on "enable oem unlock" in the developer options
Hey fam, hope you've been keeping well and safe.
I recently bought the Pixel 6 Pro (so happy with it!) and am currently in the process of rooting it.
It's a fairly simple process, and I've done it with all but I'm not sure what's going wrong at the initial unlocking the bootloader stage.
OEM Unlocking & USB Debugging is enabled - I've tried to deactivate/reactive it, used different ports etc. but to no avail.
It just won't unlock, and instead just gives me prompts of commands.
I've attached the screenshots.
What am I missing/doing wrong? Thanks!
are you in fastboot when you are running these commands? boot into fastboot. type the command ' fastboot --version , what version does it output?
run fastboot devices command so your devices appears, then run the unlock command again. make sure you are you using latest platform-tools (not mininal adb etc). also reinstall the driver just in case. then
you can also just go to Android's Flash Tool to unlock the device:
Android Flash Tool
flash.android.com
Alekos said:
are you in fastboot when you are running these commands? boot into fastboot. type the command ' fastboot --version , what version does it output?
run fastboot devices command so your devices appears, then run the unlock command again. make sure you are you using latest platform-tools (not mininal adb etc). also reinstall the driver just in case. then
you can also just go to Android's Flash Tool to unlock the device:
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
Thankyou so much for your quick and really helpful reply!
So I've investigated further, and re-installed all the tools/as you mentioned above - still no avail.
There does seem to be some sort of an issue as the fastboot version command responds back with 'version unknown'.
The Android Flash Tool looks like the best solution (didn't even know it existed, so thanks for that!) but I'm unsure how to proceed with it in order to unlock the bootloader (from what I'm gathered you need to have an unlocked bootloader before using it?)
I'm assuming you deselect the 'lock bootloader' option so that the tool unlocks the bootloader and then doesn't relock it? I've attached a screenshot to just check as well.
rajalot said:
Thankyou so much for your quick and really helpful reply!
So I've investigated further, and re-installed all the tools/as you mentioned above - still no avail.
There does seem to be some sort of an issue as the fastboot version command responds back with 'version unknown'.
The Android Flash Tool looks like the best solution (didn't even know it existed, so thanks for that!) but I'm unsure how to proceed with it in order to unlock the bootloader (from what I'm gathered you need to have an unlocked bootloader before using it?)
I'm assuming you deselect the 'lock bootloader' option so that the tool unlocks the bootloader and then doesn't relock it? I've attached a screenshot to just check as well.
Click to expand...
Click to collapse
yeah you need to have OEM Unlocking enabled to use Google's Flash Tool. if you don't need any data, just enable these options in the flash tool: Wipe and Force Flash Partitions. That will unlock the bootloader and wipe/reflash Android. Enabling the "lock bootloader" option will re-lock the bootloader but since you are rooting it, leave it unchecked.
But you should look into why Platform-Tools isn't working on your system. Here are instructions on how to set it up (make sure to remove all other platform-tools)
there's also Nexus Tools from Github (developed my a known tech journalist)
@rajalot besides what @Alekos said, I always go straight to the source for the latest SDK Platform Tools every time I flash anything. Also, Get the Google USB Driver (this is for Windows). Note, a recent experience. I have a Samsung tablet and have the Samsung USB drivers installed. This driver worked perfectly fine for my Pixel 6 Pro too for the last two months, but for June the full factory image would error out trying to flash until I uninstalled Samsung's driver and went back to Google's. So if you have any other device USB drivers installed than Google's, you may have to uninstall those and install Google's.
But yeah, as @Alekos said, the site Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own) will get you what you need too although if there's a conflicting driver, you would still have to solve that.
I'm going out on a limb but is this a Verizon p6p?
Nergal di Cuthah said:
I'm going out on a limb but is this a Verizon p6p?
Click to expand...
Click to collapse
I hope @rajalot updates us, although they said they did enable OEM Unlocking (and seem to be indicating that they have since re-disabled and re-enabled it, although that can be interpreted differently), which would usually indicate that they're not using a Verizon device. Weird, huh? I'm guessing the Platform Tools version is the culprit, but I'd like to hear back to confirm.
rajalot said:
OEM Unlocking & USB Debugging is enabled - I've tried to deactivate/reactive it, used different ports etc. but to no
Click to expand...
Click to collapse
bump!
well i had exactly the same issue with new pixel 6a.
installed latest google driver , latest platform tools... no luck
Nexustools did the trick for me instantly
thanks @Alekos for this share!!