Database Develop

[STEP-BY-STEP INSTRUCTIONS] Unlocking and Rooting a Dev Ed Moto X Running Kit Kat

I posted these step-by-step instructions in another thread but thought others might like to see them in their own thread. This works for Dev Ed Moto X's running either 4.4 or 4.4.2. If you have a non-Dev Ed with an unlockable bootloader, it works for those, too, but of course you void your warranty if you unlock your bootloader if you have a non-Dev Ed.
To unlock and root the developer edition:
1) Get the unlock code from Motorola and unlock the bootloader by following the directions in this link, including downloading the Android SDK and installing Motorola Device Manager:
Unlock Moto X Bootloader
2) Get mfastboot.exe here:
mfastboot.exe
and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
3) Get the TWRP custom recovery for kit kat here:
TWRP for Moto X 4.4
and place it in the same directory as fastboot.
4) On your unlocked Moto X, enable USB debugging and download SuperSU here:
SuperSU 1.93
5) Double check to make sure USB debugging has been enabled! Put your unlocked Moto X into bootloader mode by pressing the Volume Down button and then the Power button. Hold for about 3 seconds and release and you should be in bootloader mode. Connect your Moto X to your PC via a USB cable.
6) Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
7) At the command prompt type:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
to flash the custom recovery to your Moto X.
8) After the custom recovery has been flashed to your Moto X, at the command prompt type:
fastboot reboot-bootloader
to reboot into the bootloader.
(I am not sure if this step is necessary but I read somewhere it was necessary and I did it and it worked).
9) Unplug your device from your PC. Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and pressing the Volume Up button to select the recovery mode.
10) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
If you want to check to see if you successfully rooted, you can download Root Checker Basic from the playstore and it will tell you if you are rooted.
From what I have read you can use the version of TWRP I linked to above to root 4.4.2.
Remember, to take an OTA, you have to revert back to stock!

bumping this.

+1
Sent from my XT1060 using Tapatalk

Thx
Sent from my XT1058 using Tapatalk

I assume this is the same process regardless of Android build # (ie. After updating to 4.4.2) ...
Tapatalked via my moto x

YankInDaSouth said:
I assume this is the same process regardless of Android build # (ie. After updating to 4.4.2) ...
Click to expand...
Click to collapse
It works for both 4.4 and 4.4.2.

Can anyone post the steps to flash stock recovery to accept the OTA TO 4.4.2? Thanks.
Sent from my XT1060 using Tapatalk

ragingd said:
Can anyone post the steps to flash stock recovery to accept the OTA TO 4.4.2? Thanks.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Grab the firmware for your model here: http://sbf.droid-developers.org/phone.php?device=0
Then you can follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images ... Of course if you don't have flash every component, only what you need. Recovery of course and perhaps system...
Tapatalked via my moto x

Assistance
Perhaps someone could shed some light on this for me. I have a T-Mobile (XT1053) with an unlocked bootloader (I'm certain it's unlocked as I get the unlocked bootloader warning). I unlocked via Motorolas site. I then attempted to install TWRP with mfastboot, which it says it has done, but then when I attempt to reboot into recovery, it just ends up at a black screen (off essentially) and I can only power up as normal. Any one have any ideas?

Tuse0708 said:
Perhaps someone could shed some light on this for me. I have a T-Mobile (XT1053) with an unlocked bootloader (I'm certain it's unlocked as I get the unlocked bootloader warning). I unlocked via Motorolas site. I then attempted to install TWRP with mfastboot, which it says it has done, but then when I attempt to reboot into recovery, it just ends up at a black screen (off essentially) and I can only power up as normal. Any one have any ideas?
Click to expand...
Click to collapse
First, with your device disconnected from any power source, boot into bootloader mode and verify that it says Device is UNLOCKED. Status Code: 3. BTW - the bootloader unlocked warning logo stays even if you relock the bootloader unless you flash a new logo.
Then if it does say device is unlocked, hit Volume Down to highlight Recovery and Volume Up to select recovery. Is that when you see a black screen? It takes TWRP a little while to load.

Cozume said:
First, with your device disconnected from any power source, boot into bootloader mode and verify that it says Device is UNLOCKED. Status Code: 3. BTW - the bootloader unlocked warning logo stays even if you relock the bootloader unless you flash a new logo.
Then if it does say device is unlocked, hit Volume Down to highlight Recovery and Volume Up to select recovery. Is that when you see a black screen? It takes TWRP a little while to load.
Click to expand...
Click to collapse
Nevermind....Thanks for the help, got it going.

thanks!

jodaboda said:
thanks!
Click to expand...
Click to collapse
You are welcome!

So I'm getting an unlock code. I am currently on 4.4.2, and if I read the posts right, I don't have to downgrade to 4.4 to root, TWRP will still root 4.4.2 without issue, right?
EDIT
Nevermind. I've slapped my Moto, so I'm going to SBF back to 4.4.2 to make sure there aren't any... issues...

I'm currently rooted on 4.4. I have made changes to /system, so I can't take the OTA. I got an unlock code today. I understand that unlocking the bootloader will induce a Factory Data Reset. Do I need to SBF to stock 4.4 (or 4.2.2) before I do this? Will the FDR clear up the changes I made?
Furthermore, what order should I do these steps in? If I have 4.4 and unlock/root it, I can't take the OTA with non-stock recovery, correct? I would need a flashable ZIP for TWRP/CWM? Would it be better to unlock, FDR, take OTA to 4.4.2, then do TWRP and root?
Hopefully this isn't too silly of a question, I appreciate any advice for the best path to take on this.

Hey all, just ordered a Dev Edition to go along with my N5 and had a question regarding mfastboot. I downloaded mfastboot from one of the stickies, it was only one file and placed it in my sdk platform tools folder. I was reading on Motorola website about flashing factory images and seen this note-"NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility.". First of all, what does it mean included in Windows directory? And I'm guessing about not using the Android fastboot utility, they want you to use "mfastboot flash...." instead of "fastboot flash...."? Just trying to get some research in before I receive the device. I'm used to using fastboot on my Galaxy Nexus and now my N5. I used to have alot of Moto devices before this and using the SBF files in Moto's flashing tool, but never had an unlockable bootloader Moto device that can use some form of fastboot.

t1.8matt said:
Hey all, just ordered a Dev Edition to go along with my N5 and had a question regarding mfastboot. I downloaded mfastboot from one of the stickies, it was only one file and placed it in my sdk platform tools folder. I was reading on Motorola website about flashing factory images and seen this note-"NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility.". First of all, what does it mean included in Windows directory? And I'm guessing about not using the Android fastboot utility, they want you to use "mfastboot flash...." instead of "fastboot flash...."? Just trying to get some research in before I receive the device. I'm used to using fastboot on my Galaxy Nexus and now my N5. I used to have alot of Moto devices before this and using the SBF files in Moto's flashing tool, but never had an unlockable bootloader Moto device that can use some form of fastboot.
Click to expand...
Click to collapse
Fastboot can't handle the file sizes. So Motorola made mfastboot. You have to use it when flashing the Moto x.
Sent from my cell phone telephone....

kj2112 said:
Fastboot can't handle the file sizes. So Motorola made mfastboot. You have to use it when flashing the Moto x.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
Ok, gotcha. And I've been reading a little about people wanting to downgrade from 4.4.2, but if you have a locked bootloader and upgraded to the latest bootloader, they can't without bricking. I assume this won't be an issue with an unlocked bootloader, even though I'm not sure of why you would want to downgrade. Edit: I see, for root reasons, but this shouldn't be an issue if you're flashing SuperSU in TWRP?
Edit again: I should read more. Rooting 4.4.2 with an unlocked bootloader isn't an issue if I follow this guide in this thread. Thanks for your help. Looking forward to getting this device.

t1.8matt said:
Ok, gotcha. And I've been reading a little about people wanting to downgrade from 4.4.2, but if you have a locked bootloader and upgraded to the latest bootloader, they can't without bricking. I assume this won't be an issue with an unlocked bootloader, even though I'm not sure of why you would want to downgrade. Edit: I see, for root reasons, but this shouldn't be an issue if you're flashing SuperSU in TWRP?
Edit again: I should read more. Rooting 4.4.2 with an unlocked bootloader isn't an issue if I follow this guide in this thread. Thanks for your help. Looking forward to getting this device.
Click to expand...
Click to collapse
Root will be easy. Same as a nexus. Unlock bootloader, flash custom recovery....root. install superSU if needed.
As far as what's NOT like a nexus....yes, you can still brick downgrading an unlocked device....even the dev edition...which is no different than any other unlocked Moto x. Without going into all the details, you can read about it all over....there is a specific way to downgrade. And you cannot take an ota after....that MAY brick any Moto x...locked or unlocked. There is tonnes of conflicting opinions on this....so read as much as you can, and decide from there. There's very specific ways to downgrade and upgrade after. In my opinion....there's risk involved in all of it.
Just Google "Moto x brick downgrade xda" to read the stories.
If you find you must downgrade from 4.4.2.....study hard before you do.
Sent from my N5, N7, Moto X,G Tab 3 or S2.....

kj2112 said:
Root will be easy. Same as a nexus. Unlock bootloader, flash custom recovery....root. install superSU if needed.
As far as what's NOT like a nexus....yes, you can still brick downgrading an unlocked device....even the dev edition...which is no different than any other unlocked Moto x. Without going into all the details, you can read about it all over....there is a specific way to downgrade. And you cannot take an ota after....that MAY brick any Moto x...locked or unlocked.
If you find you must downgrade from 4.4.2.....study hard before you do.
Sent from my N5, N7, Moto X,G Tab 3 or S2.....
Click to expand...
Click to collapse
Great info. But the only reason people are downgrading from 4.4.2 is if they have a locked bootloader and want to retain root?

[Q] Fastboot failure help needed

I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):

You should check out the 'Chinese Middleman' thread. If you get the bootloader unlocked you should be able to fix anything.

I can't unlock the bootloader since this is not a Dev edition. Unless something has changed, I'll check it.

You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk

shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Even though it's not a Dev edition?

Yes you should be able too.
Sent from my XT1053 using Tapatalk

danman421 said:
Even though it's not a Dev edition?
Click to expand...
Click to collapse
All XT1053s can be unlocked, yes. Additionally, if you follow my advice, you don't NEED to unlock. If one of the commands fails, simply skip to the next as I previously advised, and TRY flashing with RSD Lite after you have run the commands I listed.
If you want to check and make sure fastboot is working, type:
fastboot devices
if you see your phone and it's serial number listed, you fastboot IS properly communicating with your phone.
You do not need to unlock your BL to do any of this...but if you are interested in ROOTING, you will need to.

All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?

shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.

danman421 said:
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
Click to expand...
Click to collapse
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
danman421 said:
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
Click to expand...
Click to collapse
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.

samwathegreat said:
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
Click to expand...
Click to collapse
So if I am reading this correctly, there is no way to keep all of my data and take the update?

danman421 said:
So if I am reading this correctly, there is no way to keep all of my data and take the update?
Click to expand...
Click to collapse
You can attempt to, by either editing the XML in the SBF and removing the line that says "erase userdata", or by skipping the erase userdata if you use the manual method, but either way CAN mess everything up.
You used an EXPLOIT previously. Any time you use an exploit, you should -expect- to have to wipe everything and re-install from scratch if you want to get back to stock in order to be able to take updates. Keep this in mind if you use any exploits in the future.

Hi! This hasn't seemed to spelled out yet..... But many Moto x's can be unlocked, not just dev editions. However, you stated in the opening post that you have a Verizon Non dev, which can not be unlocked. Only way is to pay the "China middleman" (See thread in general with that name).
And personally.... I would stay on 4.2.2 and do the Slapmymoto method to get root and write protection disabled. That is the best root scenario, aside from unlocking the bootloader.
If you update to 4.4.2 or higher, you will have write protection enabled always, and no root, or sorta root with towelroot and pie. But that will limit what you can do.
See the How do I root my phone sticky thread in general for your options.

I should have posted earlier. I ran RSDLite and put the newest version on. I am unrooted. My Moto X is a Sept '13 version the the middleman probably wont work anyways. Its not worth it with this phone, im tired of the rooting, I guess im at that point in my life... Thanks for all your help though guys!

danman421 said:
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
Click to expand...
Click to collapse
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.

You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.

KidJoe said:
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
Click to expand...
Click to collapse
Good catch! ?
OP... Perhaps full disclosure of what you have done on the phone would help.
Or is that how it was?
If it's been downgraded to 4.2.2 after being on 4.4.2... As said above.... You could brick now... Especially if you OTA.
I'd tread lightly at this point.

danman421 said:
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
Click to expand...
Click to collapse
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.

Yes, that was a good catch. What I did was RSD Lite to 4.4.4 now which reset all my data.

KidJoe said:
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Click to expand...
Click to collapse
Correct, I do not need help anymore but thank you.

[Q] Unknown baseband and IMEI, need some help

So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?

http://forum.xda-developers.com/showthread.php?t=2972693 I don't know if this can help you or not I'm assuming you've already seen it

mikeboballen said:
http://forum.xda-developers.com/showthread.php?t=2972693 I don't know if this can help you or not I'm assuming you've already seen it
Click to expand...
Click to collapse
That was the guide I was following, which led to this somehow.
I'm thinking about re-locking and un-rooting now so I'll have a shot at the warranty claim.

Good luck man hope it all works out for you

ccarrionc said:
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
Click to expand...
Click to collapse
On this Nexus 6 thread some people had success flashing back to stock modems/baseband - these would be the commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
http://forum.xda-developers.com/nexus-6/help/imei-repair-t3000420
Then if that doesn't work then this:
http://forum.xda-developers.com/showthread.php?t=1960918
Then there is this:
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"

JulesJam said:
On this Nexus 6 thread some people had success flashing back to stock modems/baseband - these would be the commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
http://forum.xda-developers.com/nexus-6/help/imei-repair-t3000420
Then if that doesn't work then this:
http://forum.xda-developers.com/showthread.php?t=1960918
Then there is this:
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"
Click to expand...
Click to collapse
Thanks, but nothing worked. I'm starting to wonder if it might be a hardware issue...

ccarrionc said:
Thanks, but nothing worked. I'm starting to wonder if it might be a hardware issue...
Click to expand...
Click to collapse
Did you try this method using QPST?
http://forum.xda-developers.com/showthread.php?t=1960918

JulesJam said:
Did you try this method using QPST?
http://forum.xda-developers.com/showthread.php?t=1960918
Click to expand...
Click to collapse
I did, but I couldn't get the software to recognize my phone, it does seem kinda outdated (2012). Used QPST 2.7.

ccarrionc said:
I did, but I couldn't get the software to recognize my phone, it does seem kinda outdated (2012). Used QPST 2.7.
Click to expand...
Click to collapse
Sounds like you need to get a warranty replacement. It could be a hardware problem but even if it is not, they really need to make these phones less easy to eff up.
The IMEI is on the efs partition that we cannot even flash so I don't know how they can get messed up by the consumer but obviously they do. Someone on the N6 thread was saying it is a Qualcomm issue.

JulesJam said:
Sounds like you need to get a warranty replacement. It could be a hardware problem but even if it is not, they really need to make these phones less easy to eff up.
The IMEI is on the efs partition that we cannot even flash so I don't know how they can get messed up by the consumer but obviously they do. Someone on the N6 thread was saying it is a Qualcomm issue.
Click to expand...
Click to collapse
If I can't get the unlocked bootloader warning to go off, then I'm done for I think.
Unless people at the support center don't bother restarting it or anything... fingers crossed.
Plan B is to hardbrick it somehow so no one can turn it on and see my mess, haha.

ccarrionc said:
If I can't get the unlocked bootloader warning to go off, then I'm done for I think.
Click to expand...
Click to collapse
That is possible - there are plenty of threads on how to do that.
But even once you relock, your status code will be locked 2, not locked 0 so they can tell from the device. Also, you had to get an unlock code directly from them so if your device didn't qualify for bootloader unlock with maintaining your warranty, then they will know from that too.
Also, your qe will likely show 0/1 even though you unrooted. You can see the qe in stock recovery.
---------- Post added at 03:49 AM ---------- Previous post was at 03:46 AM ----------
ccarrionc said:
Unless people at the support center don't bother restarting it or anything... fingers crossed.
Click to expand...
Click to collapse
They will know b/c you got an unlock code to unlock it.
ccarrionc said:
Plan B is to hardbrick it somehow so no one can turn it on and see my mess, haha.
Click to expand...
Click to collapse
I would check the warranty status online. Even if the warranty is void, they may be able to repair the phone for a reasonable price if you don't hard brick it.

JulesJam said:
That is possible - there are plenty of threads on how to do that.
But even once you relock, your status code will be locked 2, not locked 0 so they can tell from the device. Also, you had to get an unlock code directly from them so if your device didn't qualify for bootloader unlock with maintaining your warranty, then they will know from that too.
Also, your qe will likely show 0/1 even though you unrooted. You can see the qe in stock recovery.
Click to expand...
Click to collapse
So the only way is getting the phone to not be able to turn on at all? Is there any known way to get off with it?

You need to flash an image from your original provider and it will work fine again. Right now you have an incompatible modem and as a result you will have no IMEI/mobile data or wifi as the radio portion of the phone is disabled.

ccarrionc said:
So the only way is getting the phone to not be able to turn on at all? Is there any known way to get off with it?
Click to expand...
Click to collapse
No, they have you in the database as having requested an unlock code.

ccarrionc said:
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
Click to expand...
Click to collapse
As someone post above. You need the stock modem of your phone model, but in your case any xt1097 will work just flash using the Fastboot mode steps and everything will be fine. I have a post on the general section "guide to convert 1097 to 1095" there you can find all the possible scenarios.
Good luck.

Steve-x said:
You need to flash an image from your original provider and it will work fine again. Right now you have an incompatible modem and as a result you will have no IMEI/mobile data or wifi as the radio portion of the phone is disabled.
Click to expand...
Click to collapse
That is what I said above but he said he tried it and it didn't work.
OP - you need to make sure you are flashing the right files - you need to flash the modem/baseband files for your device (XT1097).

JulesJam said:
That is what I said above but he said he tried it and it didn't work.
OP - you need to make sure you are flashing the right files - you need to flash the modem/baseband files for your device (XT1097).
Click to expand...
Click to collapse
I am 100% sure the files used were not the correct ones.

juliospinoza said:
As someone post above. You need the stock modem of your phone model, but in your case any xt1097 will work just flash using the Fastboot mode steps and everything will be fine. I have a post on the general section "guide to convert 1097 to 1095" there you can find all the possible scenarios.
Good luck.
Click to expand...
Click to collapse
I was following your guide, everything was fine until the OTA update came up. Is there anyway to get back to the xt1097 firmware I had before? It was 4.4.4 with Telcel.

ccarrionc said:
I was following your guide, everything was fine until the OTA update came up. Is there anyway to get back to the xt1097 firmware I had before? It was 4.4.4 with Telcel.
Click to expand...
Click to collapse
What was the exact version you had before? For future reference you shouldn't flash firmware from another provider unless you have original firmware to reflash if you experience an issue.

Steve-x said:
What was the exact version you had before? For future reference you shouldn't flash firmware from another provider unless you have original firmware to reflash if you experience an issue.
Click to expand...
Click to collapse
Found a firmware from my original provider, everything is back to normal (except now I have the different status code in the fastboot screen).
For future reference, I just installed the previous firmware through fastboot (with mfastboot, of course). IMEI was recognized again and baseband too.

[Q][Solved] Relocking the bootloader

Hey guys,
I am currently trying to get my Moto X back to stock and relock the bootloader. Not because I need to, but just because I want to. I have a retDe XT1092 which I have converted to a XT1095. Is there any way to get the phone back to software status official and relock the bootloader? It doesn't matter to me that Motorola does know that I was unlocked before, I just want to relock it. I hope you guys can help me.

May I ask why you want to relock it? There really is no benefit to relocking it. :/
Anyway the command is:
fastboot oem lock
Sent from my XT1095

I know, but want to keep myself from flashing on this phone. I am trying to get away from rooting on non-nexus phones.
Yeah I've tried that multiple times, but as long as your software status isn't official the oem lock will fail. I'd guess this happens because most images you can download are not signed images.

Is your phone still converted to 1095? If so that is why lock wont work.
You would have to flash back the 1092 de image to be unmodified.
Sent from my XT1095

Okay good to know. I thought this wouldnt matter. But are there even any existing official images for the 1092?

Moto x firmwares:
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25
Sent from my XT1095

These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.

Bl4ckX said:
These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.
Click to expand...
Click to collapse
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.

juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095

juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.

AGISCI said:
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095
Click to expand...
Click to collapse
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
strafer69 said:
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.
Click to expand...
Click to collapse
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?

Bl4ckX said:
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?
Click to expand...
Click to collapse
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095

AGISCI said:
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095
Click to expand...
Click to collapse
I am currently downloading the XT1092 retDe image. I will report back in 6hours when I am back from work and this damn free download is finished. It takes forever..

The bootloader unlocked message would be a signed Motorola image since it is shipped with the phone. The bootloader essentially has a toggle that would switch between the normal and the unlocked message. I assume the toggle just doesn't get switched back when you OEM lock. It's not like he flashed a different custom logo or anything.
Sent from my Moto X 2014 Pure Edition using Tapatalk

Correct. You will notice the status message when you enter the bootloader there is a status code. 1=LOCKED 2=RELOCKED and 3=UNLOCKED. Once you unlock the bootloader, you can never go back to status 1 again and you will always get the bootloader unlocked message. If you read the message it states that the bootloader HAS been unlocked. There is a counter trigger in the phone telling it how many times it has been unlocked. When I had my old Galaxy S2 Skyrocket I remembered a program that would "RESET" this counter, but I do not believe one exists for Motorola. Once you unlock your bootloader there is no going back.
http://i5.androidxda.com/main/Motorola_Bootloader_Warning.png

Yeah I know about this relocked state, but it doesn't matter as I don't want to RMA the phone. I just want it locked but I wasn't able to accomplish a successful oem lock and I am now searching for a way to do so.
Edit: So this morning after the download had finished I brought my X to fastboot mode. And for whichever reason the software status was set to official even on the XT1095 image. I would have sworn that this wasn't the case when I flashed it and I have no idea why it changed. And a big thanks to you @AGISCI after typing "fastboot oem lock begin" I could flash the Image you linked here and software status stayed official and I was even able to relock the bootloader. So I simply must have had wrong images in the past, because I did entirely the same process I did now, 3 times already and it didn't work out at all.
So thanks again guys. The only annoyance is that I can't get rid of the bootloader unlocked message. This one seems to stay.

Relock Droid Turbo Bootloader

What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.

mlw4428 said:
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
Click to expand...
Click to collapse
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.

According to jcase relocking the bootloader it still shows a modified status code. Your warranty is permanently voided.

Are you on an Edge plan? Otherwise I don't know why you would be returning the phone to upgrade. Also not sure what their rules are on permanently modifying the software of one of these essentially "lease-to-own" devices, so might want to check the terms and conditions if this applies to you. If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Sent from my XT1254 using Tapatalk

SpyderPride said:
If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Click to expand...
Click to collapse
A bootloader unlocked, rooted XT1254 would be more valuable to a buyer than one locked down. You've already done all the hard work.

TheSt33v said:
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
Click to expand...
Click to collapse
Heya so I'm in a serious bind.
I skipped your step 1 and locked my bootloader. I have an unlocked bootloader. I recently upgraded through the normal verizon pushed update the marshmallow update. Anyhow. I now want to return the phone for an upgrade and well... I locked the bootloader. Then turn the phone off and turned it back on and it now says locked, but it says failed to validate system image. I then got freaked out and downloaded all the step 1 files and tried to flash the stock rom (which i already had installed!) and that doesn't seem to work. Did I brick my phone? Is there any way to get it working now that it is locked with any kind of android at all?

You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571

Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
TheSt33v said:
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse

droidfun1 said:
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
Click to expand...
Click to collapse
Strange. As far as I understand it, RSDlite just automates fastboot, so even if you're using RSDlite, you're actually using fastboot. Whatever works though.
As for the unlocked bootloader message, see my response to that post you made.