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] Installing TWRP on MotoX 4.4.2

hello, I have been searching relentlessly for a real answer to this and have not found clear answers that I believe apply.
I wanted to install TWRP on my retail verizon Moto X running 4.4.2 but I get a message:
Code:
sending 'recovery' (9854 KB)
OKAY [ 0.860s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.260s
In my searches, i saw this message being related to a locked bootloader. The part that gets me is that I unlocked the boot loader when using JCase slapmymoto v1.0 root method. I saw that some 4.4.2 OTA was supposed re-lock the bootloader, but the last I checked, right after rooting, it was still coming back as unlocked and I have not done any updates since rooting.
Any answers on this would be appreciated to clear up my noobness.
Also, I can't remember or find again, the adb/fastboot command for checking the bootloader, if I had that to tell me whether my BL got re-locked I could just go on that.
Thanks in advance!

Slapmymoto does not unlock your bootloader. You can't unlock the bootloader on a retail verizon Moto X. You either have to have the Dev Edition or you can try that Chinese site.
Either way, the only way to do it is to use fastboot oem unlock (unlock code). If you never did that, then you didn't ever unlock.
That said, you can't install TWRP on your phone unless you use that Chinese site to unlock your bootloader. There is a thread on it.
Sent from my Dev Edition Moto X

chuck4100 said:
hello, I have been searching relentlessly for a real answer to this and have not found clear answers that I believe apply.
I wanted to install TWRP on my retail verizon Moto X running 4.4.2 but I get a message:
Code:
sending 'recovery' (9854 KB)
OKAY [ 0.860s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.260s
In my searches, i saw this message being related to a locked bootloader. The part that gets me is that I unlocked the boot loader when using JCase slapmymoto v1.0 root method. I saw that some 4.4.2 OTA was supposed re-lock the bootloader, but the last I checked, right after rooting, it was still coming back as unlocked and I have not done any updates since rooting.
Any answers on this would be appreciated to clear up my noobness.
Also, I can't remember or find again, the adb/fastboot command for checking the bootloader, if I had that to tell me whether my BL got re-locked I could just go on that.
Thanks in advance!
Click to expand...
Click to collapse
The above poster is correct jcase method is not to unlock your bootloader it is just to root your phone and then another method is to disable write protect.
in order to install TWRP you must unlock your bootloader and in order to do that you need to go here and see if your phone is able to have its bootloader unlocked or not. if you want to find out follow the link below.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215
if your phone can not unlock its bootloader then the closeest thing to TWRp you can use is Safestrap that is if they have ported it over to 4.4.2 im not sure if they have yet or not but below is the link to it for you to check out.
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
hope this helps and here is a link to my thread with guides on how to do most things on the moto X
http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358

Hmm, guess i misunderstood what i was doing. The write protect sounds right, guess I mistook that for a bootloader unlock workaround.
Thx for the replies.

I do not believe that I have Dev Edition. I bought my motoX earlier this year, directly from Motorola's website and specified that it was for T-Mobile's network.
All I did was to go online and requested a bootloader unlocking from MotoX.
The phone is now unlocked with TWRP and rooted.
So I am not sure that it cannot be done.
Pat

patspdaphone said:
I do not believe that I have Dev Edition. I bought my motoX earlier this year, directly from Motorola's website and specified that it was for T-Mobile's network.
All I did was to go online and requested a bootloader unlocking from MotoX.
The phone is now unlocked with TWRP and rooted.
So I am not sure that it cannot be done.
Pat
Click to expand...
Click to collapse
Anyone that bought the AT&T or Verizon retail variants cannot get unlock codes through Motorola due to the carrier not allowing unlocked bootloaders. However, codes can be obtained through a third party without Moto's or AT&T/Verizon knowledge.
Sent from my Moto X.

One more semi-related question since I don't want to make another thread just for this....
I thought I saw somewhere that the 4.4.2 OTA will re-lock the bootloader. Is this to mean that if I bought a code and unlocked the bootloader, it would re-lock if I continued with 4.4.2 or updated to 4.4.3?

No it won't if the bootloader loader is unlocked. If you have a locked bootloader and you are rooted with the write protection disabled. You will at least lose the write protection. I am locked and rooted on 4.4.2. I used supersu pro ota survival and kept root, but that's not guaranteed
Sent from my XT1058 using xda app-developers app

Command restricted

After flashing the 4.4.4 factory images i proceed to restore root. not wanting to be stuck on the same wait for new factory images in the future, i'm avoiding overwritting the factory recovery. plan was to boot twrp or cwm and supersu it.
but now trying to boot either i get "command restricted".
All search results for that error that i found in the forum are because of a bad img download (and all from motorola phones). this is not the case. checksum matches.
even moved over to a windows box in case moto linux fastboot was not OK..
Code:
C:\motox\TMO_213.44.1.ghost_row.Retail.en.US>Windows\fastboot.exe oem unlock
...
(bootloader) Device already unlocked!
FAILED (remote failure)
finished. total time: 0.234s
C:\motox\TMO_213.44.1.ghost_row.Retail.en.US>Windows\fastboot.exe boot ..\openrecovery-twrp-2.8.1.0-ghost.img
downloading 'boot.img'...
OKAY [ 0.826s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.950s
what am i missing here?

1. Why do you type fastboot.exe?
2. You can't boot the recovery image from fastboot.
3. Why not overwrite the stock recovery? It takes a second to flash back...

neh. just flashed it.

nhizzat said:
1. Why do you type fastboot.exe?
2. You can't boot the recovery image from fastboot.
3. Why not overwrite the stock recovery? It takes a second to flash back...
Click to expand...
Click to collapse
1. because i got tired of trying to understand and moved to a windows box. where i finally decided to copy the output and paste here
2. i could do that with my nexus one and other phones. or was that just a custom kernel... yeah, i think you are right... no wait, i could do that, yep! ..have to keep reminding me that motox dev != nexus
3. ended up doing that... but i wanted to to boot a custom recovery exactly to probe the original recovery... so that was a 4 step process. flash, root, move what i need to system, flash stock recovery, etc etc etc.

Correction.
Moto X Dev Edition is nothing like a Nexus. ?
A Moto X Dev Edition = every other bootloader unlocked Moto X. No difference, other than keeping warranty when you unlock.
Sorry, just don't want any new X users thinking otherwise, or they could easily get bricked or have big issues thinking they can do things on a Dev Edition that you can't do on other models. ?

KJ said:
Correction.
Moto X Dev Edition is nothing like a Nexus. ?
A Moto X Dev Edition = every other bootloader unlocked Moto X. No difference, other than keeping warranty when you unlock.
Sorry, just don't want any new X users thinking otherwise, or they could easily get bricked or have big issues thinking they can do things on a Dev Edition that you can't do on other models. ?
Click to expand...
Click to collapse
i had just said that but yeah i keep having to remind me.
damn false advertising
Sent from my XT1053 using XDA Free mobile app

False advertising?

XT1068 - Error unlock bootloader, not write new rom

My xt1068 has locked bootloader, and was in the rom 5.0.2 and upgraded to 6.0 alone and began to hang, was then rewrite rom 6.0 (TITAN_RETAILDSDS_6.0_MPB24.65-34_cid7), and not turned over, I tried to rewrite the 5.0. 2 (although I knew that the chance to return was almost zero because the rom does not downgrade with locked bootloader). and not worked ...
I tried to unlock the bootloader and the following error:
(Bootloader) unlock invalid date!
FAILED (remote failure)
finished. Total time: 10.031s
the equipment is stopped, and not do anything already used several commands like "mfastboot oem fb_mode_clear" among others, however nothing happens.
I have a little experience with rom motorola, but nothing is solving.
It will be someone there who can help me ...

how do i root and bootloader unlock an AT&T XT1097 with the latest otas?

I bought a Moto x 2014 off eBay, it is such an amazing device. I noticed that kingroot no longer works. Is there anyway to downgrade? Sunshine also says the firmware is incompatible. I didn't know it had the latest otas when I got it. It's in mint condition
EDIT: It is the AT&T Variant with Security patch 2016-08-01
EDIT: Said screw it and got the Verizon Variant. Yay bootloader unlock

Konner920 said:
I bought a Moto x 2014 off eBay, it is such an amazing device. I noticed that kingroot no longer works. Is there anyway to downgrade? Sunshine also says the firmware is incompatible. I didn't know it had the latest otas when I got it. It's in mint condition
Click to expand...
Click to collapse
I think the best current root method is Magisk. But, before you start doing anything with your phone, you should unlock the bootloader, so that you have more flashing options. First thing to do is enable Developer Options, in Settings, About phone, tap Build number 7 times, go back to Developer Options and enable USB Debugging, and Allow bootloader unlock, if you have that option.
The latest ADB and Fastboot: https://developer.android.com/studio/releases/platform-tools.html
In Bootloader mode:
fastboot getvar all
Copy and save all that info into Notepad and keep it, then:
fastboot oem get_unlock_data
Copy what you get into Notepad, and save it.
Then go to Motorola's website to get the unlock code (you need to sign in):
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
fastboot oem unlock thecodeyoureceive

Gus Ghanem said:
I think the best current root method is Magisk. But, before you start doing anything with your phone, you should unlock the bootloader, so that you have more flashing options. First thing to do is enable Developer Options, in Settings, About phone, tap Build number 7 times, go back to Developer Options and enable USB Debugging, and Allow bootloader unlock, if you have that option.
The latest ADB and Fastboot: https://developer.android.com/studio/releases/platform-tools.html
In Bootloader mode:
fastboot getvar all
Copy and save all that info into Notepad and keep it, then:
fastboot oem get_unlock_data
Copy what you get into Notepad, and save it.
Then go to Motorola's website to get the unlock code (you need to sign in):
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
fastboot oem unlock thecodeyoureceive
Click to expand...
Click to collapse
It's the AT&T Variant it says it does not qualify for bootloader unlocking. Sunshine is unable to work with the firmware and Kingroot doesn't work. Security patch 2016-08-01

Konner920 said:
It's the AT&T Variant it says it does not qualify for bootloader unlocking. Sunshine is unable to work with the firmware and Kingroot doesn't work. Security patch 2016-08-01
Click to expand...
Click to collapse
I'm not familiar with carrier variants, but you might be able to downgrade because you can supposedly flash stock factory images with a locked bootloader. Since you already have the latest update, NEVER EVER flash "gpt.bin" and "motoboot.img" or you may brick the phone; those 2 files cannot be downgraded (partition table and bootloader).
I'm not sure if Magisk works with a locked bootloader, usually most things require a custom recovery, which you can't flash with a locked bootloader.

I will try that soon, I hope I can downgrade it. This phone rocks even with 5.1

Gus Ghanem said:
I'm not familiar with carrier variants, but you might be able to downgrade because you can supposedly flash stock factory images with a locked bootloader. Since you already have the latest update, NEVER EVER flash "gpt.bin" and "motoboot.img" or you may brick the phone; those 2 files cannot be downgraded (partition table and bootloader).
I'm not sure if Magisk works with a locked bootloader, usually most things require a custom recovery, which you can't flash with a locked bootloader.
Click to expand...
Click to collapse
Sorry for double post. Since the bootloader is locked
"mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.363s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.592s
"
I can still get into android but it will not downgrade.

Gus Ghanem said:
I'm not familiar with carrier variants, but you might be able to downgrade because you can supposedly flash stock factory images with a locked bootloader. Since you already have the latest update, NEVER EVER flash "gpt.bin" and "motoboot.img" or you may brick the phone; those 2 files cannot be downgraded (partition table and bootloader).
I'm not sure if Magisk works with a locked bootloader, usually most things require a custom recovery, which you can't flash with a locked bootloader.
Click to expand...
Click to collapse
Magisk won't work on locked bootloader.
I also don't think it's possible to downgrade stock factory images with stock recovery. At least I've heard it can brick devices.
Don't quote me on this but OP might be out of luck. That's the latest ATT security update, which doesn't have a way to temp root so he can unlock the bootloader.

Visi0nofExcellence2 said:
Magisk won't work on locked bootloader.
I also don't think it's possible to downgrade stock factory images with stock recovery. At least I've heard it can brick devices.
Don't quote me on this but OP might be out of luck. That's the latest ATT security update, which doesn't have a way to temp root so he can unlock the bootloader.
Click to expand...
Click to collapse
Luckily fastboot oem fb_mode_reset fixes the boot up. No brick since I didn't touch gpt.bin/motoboot.img but yeah I'm pretty SOL. I love the phone, it works great as it is. I'll just wait and see if someone cracks it.

Could you finnally unlock de att variant bootloader?

No I ended up saying screw it and got a Verizon variant since it can be officially unlocked through motorola. my puretalk sim gives me LTE still.

I know this is off topic but, is it possible to activate this phone with a custom room running on it? I'm running NXROM. I haven't activated it yet. Its through us cellular.

its now 2018 may 21, i have that same problem and sunshine didn't work either is ther
i have the same problem with xt1097 att and sunshine didn't work is there anyone that can unlock the bootloader it is may 21, 2018 and still don't have a solution. i want to keep this phone. i WANT TO UPGRADE IT IF I CAN.
EDIT: It is the AT&T Variant with Security patch 2016-08-01
EDIT: Said screw it and got the Verizon Variant. Yay bootloader unlock[/QUOTE]​