Database Develop

Moto X Dev Edition Bootloader Unlock

I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.

if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.

sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
You need a code, even for the dev edition, just typing fastboot oem unlock generates:
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.082s]
finished. total time: 0.082s
and the device still shows:
Device is LOCKED. Status Code: 0

cropythy said:
You need a code, even for the dev edition, just typing fastboot oem unlock generates:
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.082s]
finished. total time: 0.082s
and the device still shows:
Device is LOCKED. Status Code: 0
Click to expand...
Click to collapse
I had to manually put the numbers in, make sure you do not put any spaces between any number, letters. It took me twice
Sent on my Moto X

sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
flashallthetime said:
I had to manually put the numbers in, make sure you do not put any spaces between any number, letters. It took me twice
Sent on my Moto X
Click to expand...
Click to collapse
I tried manually entering it (3 times) i have tried copying it directly, and I have tried copying into notepad and making sure there are no spaces, but it still says my devices is not eligible for a bootloader unlock. Guess I'm calling motorola after work tomorrow.

cropythy said:
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
Click to expand...
Click to collapse
I just tried unlocking a Rogers Canada phone and it told me the phone isn't eligible. It certainly should be and I know I'm doing everything correctly as I unlocked a different one a few days ago.
So being you're seeing the same thing my conclusion is that the backend server which the website communicates with to manage the unlocking is broken at the moment.

cropythy said:
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
Click to expand...
Click to collapse
Try it again today, so far from my testing the unlock website is working again.

sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
As others have said, you need a code. The reason is you have to see like five warnings that the warranty will be voided before you get the code. They want to make sure people can't use the "I didn't know it would void the warranty" response if something goes wrong.

GSM Dev Can't go into CWM recovery
Unlocked bootloader successfully as instructed on motorola developer website.
But my GSM Dev version can't go into CWM recovery. If select "Recovery" on fastboot mode, normally reboot...
Could someone give me any advise?
# fastboot flash recovery cwm6.0.3.6.img
sending 'recovery' (8504 KB)...
OKAY [ 0.710s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.529s

hondamarlboro said:
Unlocked bootloader successfully as instructed on motorola developer website.
But my GSM Dev version can't go into CWM recovery. If select "Recovery" on fastboot mode, normally reboot...
Could someone give me any advise?
# fastboot flash recovery cwm6.0.3.6.img
sending 'recovery' (8504 KB)...
OKAY [ 0.710s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.529s
Click to expand...
Click to collapse
Are you hitting volume up when you select recovery from the bootloader menu? It's not the power button to select, it's volume up.

Volume UP is the "select"
lensgrabber said:
Are you hitting volume up when you select recovery from the bootloader menu? It's not the power button to select, it's volume up.
Click to expand...
Click to collapse
Thank you!!! This is my first moto device and I don't know this manner. Successfully recovery into CWM. Thank you again!

Welcome.
Sent from my XT1053 using Tapatalk

Is possible, Lock bootloader ?
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?

felipendc2012 said:
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
Click to expand...
Click to collapse
I'm trying to figure out the same thing. I followed motorola's instructions on reflashing https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images but it does not re-lock. It tells me "No valid PIV block in SP for userdata"
edit - deleted userdata and it locked, but i still get the warning screen on boot

warranty
I thought Moto had reversed course, and now honors warranty issues on unlocked dev. devices...?

vespadaddy said:
I thought Moto had reversed course, and now honors warranty issues on unlocked dev. devices...?
Click to expand...
Click to collapse
Anyone knows anything about that?
Also, is the image altered in any way after a unlock? or is it exactly the same as a factory reset?
---
edit:
apparently it is all fine
Requesting an unlock code will no longer void the device’s warranty
We will start posting return-to-factory software images
Click to expand...
Click to collapse
-- http://motorola-blog.blogspot.com/2013/11/you-asked-we-listened-announcing.html

Why really lock?
felipendc2012 said:
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
Click to expand...
Click to collapse
Why would you unroot and/or unlock?
If it is a dev edition, it will not hurt the warranty.
The reason for this phone is for unlocking, rooting, flashing and roming.
Once you have saved a nandroid with a custom recovery (TWRP) you can't mess anything up. Go crazy and have fun

[Q] Strange thing happened ! (Dev- XT1068 Indian)

I relocked the bootloader but when i did , I got an error saying 'too many strings' or something
However, I restarted phone in bootloader and saw the status code (It was 2-bootloader status:Locked)
However i gave a 'oem lock' command again.
I get status 2-bootloader status:Locked, after relocking. (well thats ok) but i still see the bootloader unlocked warning.
I could Still flash the warning remover 'logo.bin' file
Now Im confused about whats happening! If my bootloader was locked then how could I get that warning? Rather , How could I ever flash a logo.bin file on my device?
ANy Help AppReciated!

tbiwalkar said:
I relocked the bootloader but when i did , I got an error saying 'too many strings' or something
However, I restarted phone in bootloader and saw the status code (It was 2-bootloader status:Locked)
However i gave a 'oem lock' command again.
I get status 2-bootloader status:Locked, after relocking. (well thats ok) but i still see the bootloader unlocked warning.
I could Still flash the warning remover 'logo.bin' file
Now Im confused about whats happening! If my bootloader was locked then how could I get that warning? Rather , How could I ever flash a logo.bin file on my device?
ANy Help AppReciated!
Click to expand...
Click to collapse
It's no problem to unlock the device again. Just use the same code you received via email.
The bootloader-warning stays because even a relock does not restore warranty.
There's absolutely no reason to relock the device. As long as you are fully unrooted you will be able to install OTA even with unlocked bootloader.

doppelhelix said:
It's no problem to unlock the device again. Just use the same code you received via email.
The bootloader-warning stays because even a relock does not restore warranty.
There's absolutely no reason to relock the device. As long as you are fully unrooted you will be able to install OTA even with unlocked bootloader.
Click to expand...
Click to collapse
I understand but then how am i able to flash logo.bin?

tbiwalkar said:
I understand but then how am i able to flash logo.bin?
Click to expand...
Click to collapse
You have to be unlocked for this. And just keep it unlocked. As I said, there's no point in relocking.

doppelhelix said:
You have to be unlocked for this. And just keep it unlocked. As I said, there's no point in relocking.
Click to expand...
Click to collapse
I am locked and still i am able to flash various logo.bin files using mfastboot

tbiwalkar said:
I am locked and still i am able to flash various logo.bin files using mfastboot
Click to expand...
Click to collapse
Interesting. Thanks for the input. learned somthing new..[emoji4]

[Q] Cant Unlock Bootlader - DEVICE IS ENGINEERING

In fastboot mode where it is supposed to say device is unlocked or device is locked my device says "DEVICE IS ENGINEERING".
Also when I try to unlock the bootloader in WUG's toolkit it says everything ran correctly but when the device reboots it is still locked and never even reset.
I am trying to upgrade android as I am currently in a developer preview. How can I unlock my bootloader to upgrade to the latest stock version of android M?:

Why do people use toolkits on a Nexus device? I know it's just "click, click, click, score!", but only until something goes wrong (and eventually it does go wrong), and there they are totally out of practice to use the basic adb and fastboot commands.
So you should try fastboot, and copy here its output, then maybe somebody will know how to help.

How did you get to have a developer preview? I have a poor memory, but I think it had to be installed manually, and I'm pretty sure that you had to be unlocked to install manually? Can someone with a better memory comment?

Have you even tested fastboot flashing (manually)? I cant imaging an engineering device with a locked bootloader. That said, lets hope the hardware in that thing is identical to the Nexus 6 otherwise flashing something could break it. fastboot boot twrp.img should be the first test as it does not flash anything and should give an indication by the recovery boot being successful that the hardware is at least mostly, identical.

i have same problem, have you found a solution?
I am having same problem. I Installed the MRA58K a month ago and now trying to upgrade to MRA58R, using the Nexus Root Toolkit, I can't get the boot loader unlocked , it says device is engineering.
Please advise if you know the solution.
Thanks
frusso21 said:
In fastboot mode where it is supposed to say device is unlocked or device is locked my device says "DEVICE IS ENGINEERING".
Also when I try to unlock the bootloader in WUG's toolkit it says everything ran correctly but when the device reboots it is still locked and never even reset.
I am trying to upgrade android as I am currently in a developer preview. How can I unlock my bootloader to upgrade to the latest stock version of android M?:
Click to expand...
Click to collapse

1. Don't use toolkits, type commands one by one.
2. Try the new unlock command: fastboot flashing unlock
3. If it still doesn't work, paste the output here, and people will know if they can help or not.
Also: How did you install MRA58K?

istperson said:
1. Don't use toolkits, type commands one by one.
Click to expand...
Click to collapse
+1! Read and do it manually!
Make sure that "OEM unlocking" in developer options is enabled

OEM unlocking is enabled
Droidphilev said:
+1! Read and do it manually!
Make sure that "OEM unlocking" in developer options is enabled
Click to expand...
Click to collapse
OEM unlocking is enabled

istperson said:
2. Try the new unlock command: fastboot flashing unlock
Click to expand...
Click to collapse
Hello, can you explain? i only know the command "fastboot oem unlock"

Droidphilev said:
Hello, can you explain? i only know the command "fastboot oem unlock"
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/verified-boot.html

istperson said:
https://source.android.com/security/verifiedboot/verified-boot.html
Click to expand...
Click to collapse
Thanks for the link but this is too complicated for me. I unlocked using "fastboot oem unlock". I was on Lollipop back then. Should i run this new command also now? I don't understand the difference between 'old' and 'new'.
Thanks!

Droidphilev said:
Thanks for the link but this is too complicated for me. I unlocked using "fastboot oem unlock". I was on Lollipop back then. Should i run this new command also now? I don't understand the difference between 'old' and 'new'.
Thanks!
Click to expand...
Click to collapse
It's not a new state, they just changed the command.
Code:
void usage(void)
{
fprintf(stderr,
/* 1234567890123456789012345678901234567890123456789012345678901234567890123456 */
"usage: fastboot [ <option> ] <command>\n"
"\n"
"commands:\n"
" update <filename> reflash device from update.zip\n"
" flashall flash boot, system, vendor and if found,\n"
" recovery\n"
" flash <partition> [ <filename> ] write a file to a flash partition\n"
" flashing lock locks the device. Prevents flashing"
" partitions\n"
" flashing unlock unlocks the device. Allows user to"
" flash any partition except the ones"
" that are related to bootloader\n"
" flashing lock_critical Prevents flashing bootloader related"
" partitions\n"
" flashing unlock_critical Enables flashing bootloader related"
" partitions\n"
" flashing get_unlock_ability Queries bootloader to see if the"
" device is unlocked\n"
Code:
} else if(!strcmp(*argv, "oem")) {
argc = do_oem_command(argc, argv);
} else if(!strcmp(*argv, "flashing") && argc == 2) {
if(!strcmp(*(argv+1), "unlock") || !strcmp(*(argv+1), "lock")
|| !strcmp(*(argv+1), "unlock_critical")
|| !strcmp(*(argv+1), "lock_critical")
|| !strcmp(*(argv+1), "get_unlock_ability")) {
argc = do_oem_command(argc, argv);
} else {
usage();
return 1;
}

istperson said:
It's not a new state, they just changed the command.
Click to expand...
Click to collapse
I see. Probably the old command still works? It's still here:
https://developers.google.com/android/nexus/images?hl=en

Droidphilev said:
I see. Probably the old command still works? It's still here:
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
The page is not up to date, I bet they'll change it to flashing too soon. The command still works, see above, but it's not checked anymore for syntax, so it's only kept for compatibility reasons, but it's treated as obsolete.

istperson said:
The page is not up to date, I bet they'll change it to flashing too soon. The command still works, see above, but it's not checked anymore for syntax, so it's only kept for compatibility reasons, but it's treated as obsolete.
Click to expand...
Click to collapse
I see, thanks for all!

Ill be honest. If typing commands or following the directions on the nexus google site is too complicated for you then to be honest leave your device stock. Dont go messing with something you dont understand or you will end up with a brick and no one will help you fix it.

istperson said:
https://source.android.com/security/verifiedboot/verified-boot.html
Click to expand...
Click to collapse
My friend, i'm sorry that i lost the link but yesterday i have read somewhere that this new command is for 6P only. Don't know if that's correct. Just FYI.

Droidphilev said:
My friend, i'm sorry that i lost the link but yesterday i have read somewhere that this new command is for 6P only. Don't know if that's correct. Just FYI.
Click to expand...
Click to collapse
If looking at the source, the main command in fastboot is flashing, and OEM is the compatibility one. But I'm sure to use flashing you need a new bootloader that can actually understand it, because fastboot only sends the command, and it's the bootloader that does the unlocking.
So it's possible that the bootloaders up to 58R were not updated to the new commands. Maybe I can check it...
But only later, my virtualbox is acting up.

istperson said:
If looking at the source, the main command in fastboot is flashing, and OEM is the compatibility one. But I'm sure to use flashing you need a new bootloader that can actually understand it, because fastboot only sends the command, and it's the bootloader that does the unlocking.
So it's possible that the bootloaders up to 58R were not updated to the new commands. Maybe I can check it...
But only later, my virtualbox is acting up.
Click to expand...
Click to collapse
No need to do any further investigation. I think we will soon know when the 'old' command doesn't work anymore.
But since you are able to check such things: are you also able to check whether a bootloader is downgradable (in the future)? Would be much more interesting IMHO!
Thanks for your time!

Droidphilev said:
No need to do any further investigation. I think we will soon know when the 'old' command doesn't work anymore.
But since you are able to check such things: are you also able to check whether a bootloader is downgradable (in the future)? Would be much more interesting IMHO!
Thanks for your time!
Click to expand...
Click to collapse
Well, I checked it anyway, and the result was:
Code:
$ fastboot flashing unlock
...
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot oem unlock
...
(bootloader) Device state transition will erase userdata.
(bootloader) Are you sure you want to continue this transition?
(bootloader)
(bootloader) Press POWER key to continue.
(bootloader) Press VOL UP or VOL DOWN key to cancel state transition.
(bootloader) State transition canceled!
OKAY [ 69.909s]
finished. total time: 69.909s
I didn't try if it erases the phone even if it was unlocked.
As for downgrading, I don't know if it's a problem, but it hasn't changed since the last preview.

huawei P9 bootloader relock fail

Hi, I would like to relock the bootloader but I am getting the following message:
FAILED (remote: stat not match)
I use command line and the following command:
fastboot oem relock *******(unlock code)
Any idea?
Thanks

Goldak said:
Hi, I would like to relock the bootloader but I am getting the following message:
FAILED (remote: stat not match)
I use command line and the following command:
fastboot oem relock *******(unlock code)
Any idea?
Thanks
Click to expand...
Click to collapse
Do you see in the Fastboot that Phone (Bootloader) and FRP are unlocked.
If Phone unlocked but FRP locked, you have to enable OEM Unlocking
Do not attempt unlocking Bootloader with TWRP or custom ROM - it triggers Factory resetting and it can brick the phone
Btw, for OTA updates it doesn't matter if Bootloader is locked or not

I am on stock Nougat. I unlocked the bootloader some time ago, then some OTA update came. Right now, what I see in Fastboot is "Phone locked, FRP unlocked"... So it seems that the bootloader was actually locked by the OTA. However the Safetynet test fails and I cannot use NFC payments now. I suppose its the unlocked FRP that causes this. How could I fix it?
Thanks

Goldak said:
I am on stock Nougat. I unlocked the bootloader some time ago, then some OTA update came. Right now, what I see in Fastboot is "Phone locked, FRP unlocked"... So it seems that the bootloader was actually locked by the OTA. However the Safetynet test fails and I cannot use NFC payments now. I suppose its the unlocked FRP that causes this. How could I fix it?
Thanks
Click to expand...
Click to collapse
Some OTA updates do lock the Bootloader.
FRP should not affect SafetyNet.
Btw, which stock ROM you have and do you have Magisk/root (why are you concerned about SafetyNet)?
I'm not using NFC (pay)... but due to certain Google API changes some apps fail to verify SafetyNet

I am on stock EVA-L09C150B388, no root or other modification. So I think the only reason for NFC payment not working/ Safetynet failure might be the unlocked FRP...

Goldak said:
I am on stock EVA-L09C150B388, no root or other modification. So I think the only reason for NFC payment not working/ Safetynet failure might be the unlocked FRP...
Click to expand...
Click to collapse
You can easily uncheck OEM Unlocking and reboot

zgfg said:
You can easily uncheck OEM Unlocking and reboot
Click to expand...
Click to collapse
Unfortunatelly, that did not help...?

Goldak said:
Unfortunatelly, that did not help...
Click to expand...
Click to collapse
Test if your SafetyNet is really (not) ok with the apps attached to
https://forum.xda-developers.com/showpost.php?p=77339761&postcount=566

zgfg said:
Test if your SafetyNet is really (not) ok with the apps attached to
https://forum.xda-developers.com/showpost.php?p=77339761&postcount=566
Click to expand...
Click to collapse
Those two apps show no fails... However SafetyNet Test app from Google play says 'Failed'

Goldak said:
Those two apps show no fails... However SafetyNet Test app from Google play says 'Failed'
Click to expand...
Click to collapse
There is a link in that post - there was some change in SafetyNet/API or key causing not updated apps to fail

The command is "fastboot oem lock", not "relock"

zgfg said:
There is a link in that post - there was some change in SafetyNet/API or key causing not updated apps to fail
Click to expand...
Click to collapse
Thats probably the problem, thanks!

Nokia 7 plus Bootloader Unlock

Hi everyone
I bought my nokia 7 plus with Oreo.
Now updated to 10.
The problem is OEM unlock is disabled always in Dev options
How can i unlock to try custom roms.
Any guidance will be thank ful.

sriram reader said:
Hi everyone
I bought my nokia 7 plus with Oreo.
Now updated to 10.
The problem is OEM unlock is disabled always in Dev options
How can i unlock to try custom roms.
Any guidance will be thank ful.
Click to expand...
Click to collapse
You shouldnt have updated it.. Try downgrade it. On android 10 its disabled for evryone

2gg1 said:
You shouldnt have updated it.. Try downgrade it. On android 10 its disabled for evryone
Click to expand...
Click to collapse
OEM unlock switch NOT unlock bootloafer on Nokia7Plus with ANY Android version 10,9,8.1,8...
is need unlock via fastbboot with unofficialy generated/buyed unlocked file... and for unlocking is need have A8 or A9 with <august2019 security patches/update.,,

I managed to turn my on by turning Dev mode off and back on and you have a few seconds where you can turn it on.. Just waiting for Android 10 to turn up on my phone

TG09 said:
I managed to turn my on by turning Dev mode off and back on and you have a few seconds where you can turn it on.. Just waiting for Android 10 to turn up on my phone
Click to expand...
Click to collapse
read my post above...

Don't know whether or not it's a glitch but my 'OEM unlocking' is stuck in the enabled position, even after a hard reset. I'm on Android 10.
EDIT: safe to say that still does nothing.
C:\adb>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed

Lord Mashie said:
Don't know whether or not it's a glitch but my 'OEM unlocking' is stuck in the enabled position, even after a hard reset. I'm on Android 10.
EDIT: safe to say that still does nothing.
C:\adb>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
sad?

For unlock Bootloader, u will need to downgrade to oreo than need bootloader key... minimul adb to unlock it with the key.
Sent from my TA-1054 using Tapatalk

Lord Mashie said:
Don't know whether or not it's a glitch but my 'OEM unlocking' is stuck in the enabled position, even after a hard reset. I'm on Android 10.
EDIT: safe to say that still does nothing.
C:\adb>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
READ MY POST ABOVE...
BTW: i think, this thread not too long

k3dar7 said:
OEM unlock switch NOT unlock bootloafer on Nokia7Plus with ANY Android version 10,9,8.1,8...
is need unlock via fastbboot with unofficialy generated/buyed unlocked file... and for unlocking is need have A8 or A9 with <august2019 security patches/update.,,
Click to expand...
Click to collapse
Hm...
So what you're saying is that there are no Nokia 7 Plus' that have an unlockable bootloader? Or, to put it another way, do all Nokia 7 Plus' have the option "OEM unlocking" set to off? With no way of switching it on?
Or is there a way to switch it on?
I have booted into download mode, and fastboot flashing unlock, but it returns 0 or failed to unlock.
oh wait... I saw your other post: https://forum.xda-developers.com/showpost.php?p=78764676&postcount=3 In reference to the first item, the website is hikaricalyx?
---------- Post added at 12:18 PM ---------- Previous post was at 11:55 AM ----------
Ok... so... for Nokia 7 Plus...
I need to download ntools, HMD rom for version 8, android 8, adb/fastboot.
Then downgrade to version 8.
Flash HMD version 8 rom. (But how do I flash when it's still locked? Or does downgrading to 8 allow the option oem unlocking to be turned on?)
Unlock bootloader.
Use magisk to get root.
Is that the steps? Or am I missing something?

Search for techmaesto.

techmesto dot com/how-to-downgrade-nokia-7-plus-from-stable-pie-to-stable-oreo/
I'm using that guide, and I get up to the part where I update via SD card. But it says that the update package is older than the current build and downgrade not allowed.
What can be done about this?

Anyone know if Nokia will ever allow the bootloader to be unlocked?

ardvarkmcgark said:
Anyone know if Nokia will ever allow the bootloader to be unlocked?
Click to expand...
Click to collapse
Maybe.. N7+ is almost at his end of updates. So we have a little chance that they will do that like the nokia 8

downgrade android 8, inbox