I've been trying to unlock a Blu G5 - I've gotten as far as patching the disk image and all that is left to do is just flash the image onto the phone.
The issue is whenever I try to flash something onto the phone I get the following error :
Code:
FAILED (remote: Flashing Lock Flag is locked. Please unlock it first!)
.
When I go to unlock through Flashing unlock I get the error in the title - OEM unlock gives me cmd not found.
I have USB debugging and OEM unlocking both enabled inside the app settings. I'm not sure if its pertinent but on Magisk I see "Ramdisk : No". I've also been unable to get into recovery mode despite trying every combination possible except for once on accident (which I haven't been able to replicate).
Any help would be appreciated, Thanks!
yodamaul said:
I've been trying to unlock a Blu G5 - I've gotten as far as patching the disk image and all that is left to do is just flash the image onto the phone.
The issue is whenever I try to flash something onto the phone I get the following error :
Code:
FAILED (remote: Flashing Lock Flag is locked. Please unlock it first!)
.
When I go to unlock through Flashing unlock I get the error in the title - OEM unlock gives me cmd not found.
I have USB debugging and OEM unlocking both enabled inside the app settings. I'm not sure if its pertinent but on Magisk I see "Ramdisk : No". I've also been unable to get into recovery mode despite trying every combination possible except for once on accident (which I haven't been able to replicate).
Any help would be appreciated, Thanks!
Click to expand...
Click to collapse
having the same problem right now. did you get a fix?
Related
Hello,
I recently got a new Nexus 5X, I enabled USB Debugging and I tried using the CMD and it worked fin with commands like:
adb devices
adb reboot bootloader
However, once I boot into bootloader, I can't use any of the commands such as:
fastboot boot "C:\USERS\Path\To\TWRP.img"
it just gives this error:
downloading 'boot.img'...
OKAY [ 0.612s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.627s
I installed the drivers so USB Debugging works on my PC. However USB Debugging doesn't work when I am in bootloader.
The only reason I want to do this is because I want to be able to enable "Multi Window" mode with out having a rooted device as I want to play games that don't allow a device to be rooted.
Thanks.
Your boot loader is locked by default that's why you get the rather helpful error output: "(remote: unlock device to use this command)" Always read error outputs and try to understand them .
What you'll have to do is to unlock your device , the great thing is that you have a Nexus phone so it will be easy.
Step 1: Go to settings -->> Developers options -->> OEM unlocking toggle it to ON.
Step 2: Reboot your device to fastboot mode
Step 3: Use the command
Code:
fastboot oem unlock
(This will wipe your device so back up your important files)
Step 4: Fastboot command will work now all of them be careful this freedom comes with responsibilities! You can easily soft brick your device.
A small consideration all the information I just gave you is easy to find! The search function on XDA is great and the pinned threads are gold :good:. It will also increase your understanding of the methods used and your device :highfive:
Xacky said:
Your boot loader is locked by default that's why you get the rather helpful error output: "(remote: unlock device to use this command)" Always read error outputs and try to understand them .
What you'll have to do is to unlock your device , the great thing is that you have a Nexus phone so it will be easy.
Step 1: Go to settings -->> Developers options -->> OEM unlocking toggle it to ON.
Step 2: Reboot your device to fastboot mode
Step 3: Use the command
Code:
fastboot oem unlock
(This will wipe your device so back up your important files)
Step 4: Fastboot command will work now all of them be careful this freedom comes with responsibilities! You can easily soft brick your device.
A small consideration all the information I just gave you is easy to find! The search function on XDA is great and the pinned threads are gold :good:. It will also increase your understanding of the methods used and your device :highfive:
Click to expand...
Click to collapse
Is this basically making the device rooted?
No, you are simply unlocking the bootloader so changes can be made. You won't be rooted until you have installed SuperSU. This is a good guide that will tell you everything: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I recently purchased a used Pixel C. The previous owner stated that the bootloader is unlocked but he never flashed anything. It is running stock. I want to re-lock to the bootloader to do away with the annoying message upon boot up. What is the appropriate fastboot command? Some posts make mention of new fastboot commands. Thanks
reboot on fastboot mode
type: fastboot flashing lock
wait for format userdata
done
Solved
Thanks. That worked perfectly.
Hmmm... My bootloader is unlocked and the developer option is grayed out to lock it.
If I follow these commands to lock via fastboot ("fastboot flashing lock") I get the following error:
FAILED (remote: Enable OEM unlock is not set)
geekdaddy said:
Hmmm... My bootloader is unlocked and the developer option is grayed out to lock it.
If I follow these commands to lock via fastboot ("fastboot flashing lock") I get the following error:
FAILED (remote: Enable OEM unlock is not set)
Click to expand...
Click to collapse
Settings>Developer options>Enable OEM Unlocking
tabormeister said:
Settings>Developer options>Enable OEM Unlocking
Click to expand...
Click to collapse
Thanks -- but that option is greyed-out.
No longer a problem for me since I think I'll probably run rooted with the final rev of lineageos +microg and Magisk. So I need to stay unlocked anyhow.
geekdaddy said:
Thanks -- but that option is greyed-out.
No longer a problem for me since I think I'll probably run rooted with the final rev of lineageos +microg and Magisk. So I need to stay unlocked anyhow.
Click to expand...
Click to collapse
I just flashed LOS17.1 yesterday and HOLY crap it's great. Good call.
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 ****ed up. Hard.
After installing LineageOS I noticed some apps that use SafetyNet not working correctly. I didn't have root so I thought the only thing that could trigger it was the unlocked bootloader. I locked the bootloader in the developer settings, and booted into download mode. I executed fastboot flashing lock_critical which reported as already locked. Next I ran fastboot flashing lock which was executed successfully, then I rebooted my phone.
Now I'm in a bootloop with red text on the bootscreen saying "your device has failed verification and may not work properly Booting in 5 seconds". I am only able to access download mode, no recovery or OS. If I try to flash something it obvoiusly tells me FAILED (remote: 'Flashing is not allowed in Lock State')
Time for a new phone?
Just run
Code:
fastboot flashing unlock && fastboot flashing unlock_critical
then re-flash your rom or stock firmware
TheJnazap said:
After installing LineageOS I noticed some apps that use SafetyNet not working correctly. I didn't have root so I thought the only thing that could trigger it was the unlocked bootloader. ...
Click to expand...
Click to collapse
Look at my post here (look at the last 1/3 of the post). SafetyNet fails because it sees LineageOS. Use Magisk and then hide Magisk Manager.... that seemed to do the trick for me.
Hello friends
a friend brought me a Moto G7 Play (XT1952-2), and said he had forgotten the password, the email and all, to try to recover, he tried to flash, but did not unlock the bootloader, did not enable USB debugging and did not enable OEM unlock and yet downgraded on mobile.
The result is that the phone no longer leaves the Start Up Failed screen, it shows the following messages:
Fastboot AP Flash Mode (Secure)
SSM: Android checking failed.
No bootable A / B slot
Failed to boot Linux, failing back to fastboot
Fastboot Reason: Falling Through Normal Boot Mode
I already tried to unlock the bootloader, but as the OEM unlock option is not enabled, I could not. I tried to flash with the same rom as before or with a more current one and it didn't change anything either. I've tried basically everything I found in the forums. Can someone give me an idea of what to do?
Tks!
riickseven said:
Hello friends
a friend brought me a Moto G7 Play (XT1952-2), and said he had forgotten the password, the email and all, to try to recover, he tried to flash, but did not unlock the bootloader, did not enable USB debugging and did not enable OEM unlock and yet downgraded on mobile.
The result is that the phone no longer leaves the Start Up Failed screen, it shows the following messages:
Fastboot AP Flash Mode (Secure)
SSM: Android checking failed.
No bootable A / B slot
Failed to boot Linux, failing back to fastboot
Fastboot Reason: Falling Through Normal Boot Mode
I already tried to unlock the bootloader, but as the OEM unlock option is not enabled, I could not. I tried to flash with the same rom as before or with a more current one and it didn't change anything either. I've tried basically everything I found in the forums. Can someone give me an idea of what to do?
Tks!
Click to expand...
Click to collapse
Download Your Latest ota zip from
https://mirrors.lolinet.com/firmware/moto/channel/official/
then flash via rsd lite that will fix your phone and reset it
Help download
motorola/aljeter/aljeter:9/PPPS29.55-35-12-3/a0b9b:user/release-keys