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
I receive the message from Motorola that the bootloader of mine cannot be unlocked. Has anyone have a solution for rooting the phone without unlocking the bootloader? I read the article Root without unlocking bootloader?, I tried but it failed
C:\android-sdk>fastboot bootclockworkmod-touch-6.0.4.8.img
downloading 'boot.img'...
OKAY [ 0.733s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.837s
thanhbuu said:
I receive the message from Motorola that the bootloader of mine cannot be unlocked. Has anyone have a solution for rooting the phone without unlocking the bootloader? I read the article Root without unlocking bootloader?, I tried but it failed
C:\android-sdk>fastboot bootclockworkmod-touch-6.0.4.8.img
downloading 'boot.img'...
OKAY [ 0.733s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.837s
Click to expand...
Click to collapse
Unlike some other phones, on the 2013 X, you can only boot a custom recovery if it is flashed to the phone. With a locked bootloader you can't flash custom recovery, or anything that isn't Signed by Moto and for your phone.
There are many threads already discussing that Moto does NOT give out the bootloader unlock code for the Retail and Moto Maker X for Verizon, ATT, Republic Wireless and a few other carriers.
THis stickied thread -> [One Stop Shop] How to root the Moto X - Let's end the confusion. has information about unlocking the bootloader, and rooting with a locked and unlocked bootloader.
IF you still have 4.4.2, and bootloader 30.B4 on your phone, or you have an older rom/bootloader on your phone, you should be able to use Jcase's SUNSHINE to unlock the bootloader via hacking a vulnerability. see -> http://forum.xda-developers.com/moto-x/general/request-help-exploit-moto-x-bl-t2828471 as well as -> http://forum.xda-developers.com/showthread.php?t=2792487
But as of now, 4.4.4 & bootloader 30.B7, has patched all vulnerabilities that were exploited to gain root and/or disable write protection on a 2013 X with locked bootloader. In other words... The only way to root a 2013 X which has taken the 4.4.4 update, is to unlock its bootloader. If you can't unlock the bootloader, you can't root it.
And, before you ask... NO, You can NOT safely downgrade all needed parts of your rom/bootloader. So if you have 4.4.4 & 30.B7 on your phone, DO NOT TRY to downgrade because you will either end up with a brick immediately or at the next OTA. And either way, it wold not have downgraded the parts of the phone needed to allow Sunshine or older hacks/exploits to work.
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 ...
I'm hoping someone can help:
I've been rooting/unlocking android phones for years. I've run Linux as my desktop OS for 15 years and I'm used to using fastboot.
I've had an Xperia Zr for a few years and when I saw them new on Ebay new for <$100 I bought another one.
So the first thing I try and do is unlock the bootloader, I have done this on several phones, including the ZR I use as my main phone.
I get the IMEI off the back of the phone and make sure it's the same as the one I get when I *#*#SERVICE#*#* and it is.
In Service->Info->Configuration it does say Rooting status: Bootloader unlock allowed: Yes
I go to sony and get the unlock code for that IMEI (I've done this 4 times, it's always the same, I've double checked all the fields).
When I enter the command from fastboot to unlock the bootloader I get this:
[email protected]:/media/rolf/Data/Android$ sudo fastboot -i 0x0fce oem unlock 0x3214A89EDE406752
...
OKAY [ 1.598s]
finished. total time: 1.598s
So no error, it looks like it worked. When I reboot the phone it's like new again it wiped itself as it does after you unlock the bootloader.
But when I go back to Service->Info->Configuration it does say Rooting status: Bootloader unlock allowed: Yes , but it should now say bootloader unlocked.
When I go back to fastboot and try and flash anything it behaves like it still locked.
[email protected]:/media/rolf/Data/Android$ sudo fastboot flash recovery cm-13.0-20160930-NIGHTLY-dogo-recovery.img
sending 'recovery' (11570 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.369s
The phones both look identical, the new one looks genuine, the FCC ID and model number and Type are the same. The old phone was made in the 25th week of 2013 the new one is 30th week 2014.
Does anyone have any idea what is going on?
Thanks,
Rolf
Use flashtool to unlock bootloader.maybe this will work.I used flashtool to unlock my zr bootloader easily.
Flashtool is just a way for people who don't use the command line to issue commands.
Just to be sure I installed it under Linux and Windows and tried the bootloader unlock from there with the same results on both OSs.
01/004/2016 11:04:58 - INFO - Device connected in fastboot mode
01/007/2016 11:07:45 - INFO - Unlocking phone using key 3214A89EDE406752
01/007/2016 11:07:47 - INFO - ...
01/007/2016 11:07:47 - INFO - OKAY [ 1.385s]
01/007/2016 11:07:47 - INFO - finished. total time: 1.385s
01/007/2016 11:07:47 - INFO - Device will reboot into system now
01/007/2016 11:07:47 - INFO - Unlock code saved to C:\Users\rolf\.flashTool\registeredDevices\EP74168AM1\ulcode.txt
01/007/2016 11:07:47 - INFO - Device disconnected
Like when I use fastboot directly the device factory resets itself but remains a locked bootloader.
Has anyone ever seen a phone that says Bootloader unlock allowed: Yes but when you issue the command it fails silently?
Just to be sure, I have tried many different versions of flashtool. I have also tried using the wrong key to see what happens.
If I change the last digit of the unlock code then the command fails.
[email protected]:~/Documents/Protected/Android/FlashTool/x10flasher_lib$ sudo /home/rolf/Documents/Protected/Android/flashtoolbetalinux/x10flasher_lib/fastboot.linux.64 -i 0x0fce oem unlock 0x3214A89EDE406751
...
FAILED (remote: Command did not succeed)
finished. total time: 0.035s
If I give the correct unlock code the command succeeds, but the phone never unlocks.
[email protected]:~/Documents/Protected/Android/FlashTool/x10flasher_lib$ sudo /home/rolf/Documents/Protected/Android/flashtoolbetalinux/x10flasher_lib/fastboot.linux.64 -i 0x0fce oem unlock 0x3214A89EDE406752
...
OKAY [ 1.569s]
finished. total time: 1.569s
I've tried using 2 different computers now so I have ruled out the computer hardware or software.
It seems to be the phone, this one is made in Malaysia the other one does not say where it was made.
Does anyone have any ideas?
This won't happen if your zr isn't carrier locked.So check it otherwise i'm unable to help you.Here are some great members in zr community can help you with this wired problem.PM with daedroza or sigprof.without PM it's not hard to get help from great members.
Never seen something like this, so the following is mostly a guesswork…
What ROM do you currently have on this phone, and did you reflash it? In theory it's possible that some strange (carrier-specific) ROM version relocks the bootloader during boot; another possibility is that the unlocking process is broken with some bootloader versions. Because creating the TA backup before unlocking needs root, I used old ROMs when unlocking — maybe even something ancient like 10.3.1.A.2.67, which can be rooted with opensource rootkitZ, and definitely not something which requires the malware-infested King Root. So flashing a stock ROM with a different bootloader version may help (the bootloader version number in boot_delivery.xml inside FTF must be different from the installed verson, otherwise flashtool will skip the bootloader parts when flashing — e.g., 10.6.x and 10.7.x stock ROMs have the same VERSION="1264-2309 S1_Boot_Lagan_1.1_10").
Thank you for some excellent advice. I had already re-flashed 5.1.1 with no change, so I tried 5.0.1 and there was also no change.
I found the oldest KitKat Rom I could and flashed that, as before the bootloader unlock command appeared to have worked but this time it rebooted into a boot loop.
I dropped back into fastboot and was able to flash a new boot.img and installing cm13 was quick and easy. The bootloader now shows as unlocked in SERVICE.
What software did you use to flash an old rom?
Hi guys
I just succeed to unlock with potatoNV my ale L21.
but, its looks like there is no twrp for the 2015 version?
Im having this last one and it looks like 99% of xda regarding ale_L21/p8Lite towards 2017 version.
Isnt it possible to know how to switch to twrp/lineage with 2015 hw version?
I tried lot of twrp files regarding "looks like" 2017 ver (none says 2015, so I guess it's 2017):
FAILED (remote: image verification error)
fastboot oem lock-state info
...
(bootloader) FB LockState: UNLOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.000s]
finished. total time: 0.000s
I thank you vm
lm8lm8 said:
Hi guys
I just succeed to unlock with potatoNV my ale L21.
but, its looks like there is no twrp for the 2015 version?
Im having this last one and it looks like 99% of xda regarding ale_L21/p8Lite towards 2017 version.
Isnt it possible to know how to switch to twrp/lineage with 2015 hw version?
I tried lot of twrp files regarding "looks like" 2017 ver (none says 2015, so I guess it's 2017):
FAILED (remote: image verification error)
fastboot oem lock-state info
...
(bootloader) FB LockState: UNLOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.000s]
finished. total time: 0.000s
I thank you vm
Click to expand...
Click to collapse
I run into the same problem and managed to fix this. You have to run the potatoNV again, keeping the testpoint shorten during the reboot, and DO NOT check the "unlock FB" checkbox this time. This checkbox actually effectively locks the bootloader.