Database Develop

Gaining root on AT&T Moto X with Kitkat leak

I really HATE to have to post this and I will do so quite reluctantly....
I am certainly NOT a noob when it comes to Android, rooting, etc. But, the X is my first Moto android phone. I recently purchased mine via CTO with the AT&T Kitkat leak already installed. The person I bought it from claims there is NO WAY to gain root. He said he installed the leak via stock recovery.
The leak I'm running is 140.44.3.ghost_att.ATT.en.US.
Can anyone who's kind enough and well versed in Moto devices explain to me HOW I can how I can gain root on this leak and/or get Safestrap TWRP installed and if not, will I still be able to receive OTA updates being that the bootloader is locked and the stock recovery is intact? I just don't understand enough about Moto devices. I've searched and searched and can't really find the answers myself otherwise I wouldn't post here on XDA like the moron that I am.
I have a hard time accepting that I can't gain root despite not being able to unlock the bootloader. I realize that certain versions are only compatible with Safestrap (I hope I'm understanding that correctly) but, again I don't understand enough of how Moto's work. I've always had Samsung's or HTC's which are SUPER easy to use via ADB, etc.
Any help is greatly appreciated.

t3chn0s1s said:
I really HATE to have to post this and I will do so quite reluctantly....
I am certainly NOT a noob when it comes to Android, rooting, etc. But, the X is my first Moto android phone. I recently purchased mine via CTO with the AT&T Kitkat leak already installed. The person I bought it from claims there is NO WAY to gain root. He said he installed the leak via stock recovery.
The leak I'm running is 140.44.3.ghost_att.ATT.en.US.
Can anyone who's kind enough and well versed in Moto devices explain to me HOW I can how I can gain root on this leak and/or get Safestrap TWRP installed and if not, will I still be able to receive OTA updates being that the bootloader is locked and the stock recovery is intact? I just don't understand enough about Moto devices. I've searched and searched and can't really find the answers myself otherwise I wouldn't post here on XDA like the moron that I am.
I have a hard time accepting that I can't gain root despite not being able to unlock the bootloader. I realize that certain versions are only compatible with Safestrap (I hope I'm understanding that correctly) but, again I don't understand enough of how Moto's work. I've always had Samsung's or HTC's which are SUPER easy to use via ADB, etc.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Have you read this thread? It should give you a headstart if you haven't.

RagnaParadise said:
Have you read this thread? It should give you a headstart if you haven't.
Click to expand...
Click to collapse
Thanks Ragna... I haven't. I appreciate the help greatly. Moto's are so different from anything I'm used to and being that I am not starting out from a stock position makes it even more confusing.
Sent from my Nexus 5

t3chn0s1s said:
Thanks Ragna... I haven't. I appreciate the help greatly. Moto's are so different from anything I'm used to and being that I am not starting out from a stock position makes it even more confusing.
Sent from my Nexus 5
Click to expand...
Click to collapse
You might want to check out whether your phone is bootloader unlockable. I think you should be able to flash 4.4 on it completely soon, I would suggest holding out until then.
By the way, welcome to the Moto X camp.
Sent from my Moto X using Tapatalk

RagnaParadise said:
You might want to check out whether your phone is bootloader unlockable. I think you should be able to flash 4.4 on it completely soon, I would suggest holding out until then.
By the way, welcome to the Moto X camp.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
If he has an att moto x then it has a locked bootloader.
t3chn0s1s said:
Thanks Ragna... I haven't. I appreciate the help greatly. Moto's are so different from anything I'm used to and being that I am not starting out from a stock position makes it even more confusing.
Sent from my Nexus 5
Click to expand...
Click to collapse
To get back to stock all you need to do is download the 4.2.2 stock firmware images and then use rsdlite to install them... Assuming you have adb anyway configured, it only takes a few minutes.
From there you can do a fresh install of the 4.4 ota or take the steps to get 4.4 ota with root.
AT&T Moto X rocking rooted 4.4

theraffman said:
If he has an att moto x then it has a locked bootloader.
Click to expand...
Click to collapse
I wasn't certain because it was flashed over. I'm running on a Verizon ROM and frankly I wouldn't have known it was a Latin America version if I got it like that. So... Oh well. I suppose the probability that it is an AT&T version is much higher. In that case, OP's SOL for a bootloader unlock. Lol
Sent from my Moto X using Tapatalk

theraffman said:
If he has an att moto x then it has a locked bootloader.
To get back to stock all you need to do is download the 4.2.2 stock firmware images and then use rsdlite to install them... Assuming you have adb anyway configured, it only takes a few minutes.
From there you can do a fresh install of the 4.4 ota or take the steps to get 4.4 ota with root.
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
I'm just reading your post now but, this is exactly what I did... I just used RDS Lite to return to stock 4.2.2 and then OTA'd to 4.4 and now I'm gonna use jcase's exploit to gain root. THANKS SO MUCH FOR THE INFO GUYS!

theraffman said:
If he has an att moto x then it has a locked bootloader.
To get back to stock all you need to do is download the 4.2.2 stock firmware images and then use rsdlite to install them... Assuming you have adb anyway configured, it only takes a few minutes.
From there you can do a fresh install of the 4.4 ota or take the steps to get 4.4 ota with root.
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
RagnaParadise said:
You might want to check out whether your phone is bootloader unlockable. I think you should be able to flash 4.4 on it completely soon, I would suggest holding out until then.
By the way, welcome to the Moto X camp.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Thanks Ragna. I appreciate the info and being the "welcome wagon", LOL. Yeah - I'm obviously on the AT&T version (not a Dev Edition) so my BL is unlockable which - is complete bulls**t. I don't get why Moto has to pull this crap or why AT&T gives a rats ass what we do with our phones.

I was able to root my Verizon on 4.4 Just take your time and read thoroughly.
It's sort of a rough set of instructions not for the faint of heart.

SYNSYNACKACK said:
I was able to root my Verizon on 4.4 Just take your time and read thoroughly.
It's sort of a rough set of instructions not for the faint of heart.
Click to expand...
Click to collapse
Yea... So I've read. Telnet is SO old school... Was kinda surprised to see that as part of the process. I haven't yet taken the plunge but will probably eventually go for it. Just a little confused since I'm already on stock 4.4 so I'm not sure if I should start at step 1 or what. Oh well... I'll figure it out. Thanks for the suggestions.
Sent from my Nexus 5

Rooting

What is the past of least resistance to root a 4.4 tmo X? In order to keep data, is it still that insanely long process?
Sent from my XT1053 using Tapatalk

Bump............

WIth the T-Mobile variant you have two choices to root..
1. Unlock bootloader, flash twrp recovery, boot into twrp and install SU (or use TWRP's option to root). But this voids your warranty (since you don't have the developer edition), and unlocking the boot loader will wipe your device and data.
2. Use SlapMyMoto which has a lot of manual steps, and you need to reboot to "recovery" (well its modified and you don't have recovery), when you want R/W ability. (Or you have to also do the MotoWpNoMo process to gain R/W full time). But this has many steps.

KidJoe said:
WIth the T-Mobile variant you have two choices to root..
1. Unlock bootloader, flash twrp recovery, boot into twrp and install SU (or use TWRP's option to root). But this voids your warranty (since you don't have the developer edition), and unlocking the boot loader will wipe your device and data.
2. Use SlapMyMoto which has a lot of manual steps, and you need to reboot to "recovery" (well its modified and you don't have recovery), when you want R/W ability. (Or you have to also do the MotoWpNoMo process to gain R/W full time). But this has many steps.
Click to expand...
Click to collapse
thanks - re #1, will upgrades be painful i.e., new OTAs?

km8j said:
thanks - re #1, will upgrades be painful i.e., new OTAs?
Click to expand...
Click to collapse
OTA's will be more painful with #2 as there will be more to restore to stock. And of course the unknowns of if the new OTA will be rootable or not, and how long before a root process comes out.
For #1, you should be able to just put stock recovery back and take the OTA, then reflash TWRP and re-root.

http://forum.xda-developers.com/showthread.php?t=2556400
Sent from my XT1058 using Tapatalk

Just following up. There is still no easy root method right?
Sent from my XT1053 using Tapatalk

km8j said:
Just following up. There is still no easy root method right?
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Can't be any easier than unlocking your bootloader ,flash recovery and install superuser. 3 simple steps from my perspective
Sent on my Moto X

flashallthetime said:
Can't be any easier than unlocking your bootloader ,flash recovery and install superuser. 3 simple steps from my perspective
Sent on my Moto X
Click to expand...
Click to collapse
Unless u have Dev. Edition u cannot unlock boot loader.. I'm on 4.4 and I am fully rooted.
Slapped my Moto

xpsychox said:
Unless u have Dev. Edition u cannot unlock boot loader.. I'm on 4.4 and I am fully rooted.
Slapped my Moto
Click to expand...
Click to collapse
You can unlock the Sprint & Tmo version. No dev edition required.
Sent from my Moto X

Same with Rogers, only versions that can't unlock are Verizon and AT&T consumer version
Sent on my Moto X

quickstang said:
You can unlock the Sprint & Tmo version. No dev edition required.
Sent from my Moto X
Click to expand...
Click to collapse
I knew u couldn't do on at and Verizon...but he also never said what he had..not that I saw
Slapped my Moto

and what if you have the T-Mobile Moto X, haven't got the email to unlock bootloader and you can't get adb to recognize device?

DanRo80 said:
and what if you have the T-Mobile Moto X, haven't got the email to unlock bootloader and you can't get adb to recognize device?
Click to expand...
Click to collapse
There was another thread about this... Guy said he used a new gmail account and got email
Slapped my Moto

Just bumping to see if there are any new reasonable ways of rooting kitkat?
Sent from my XT1053 using Tapatalk

km8j said:
Just bumping to see if there are any new reasonable ways of rooting kitkat?
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Well, if you don't have an unlocked bootloader, SlapMyMoto (which now incorporates the MotoWpNoMo process into its steps) is the only way (there have been some efforts to consolidate/automate the process). And may not be usable if you're already on 4.4.2 (taking the 4.4.2 OTA update or flashing the full 4.4.2 SBF prevents you from flashing older ROMs which is a crucial step in using SlapMyMoto).
I've not see a 4.4.2 specific root process for locked bootloaders yet, but to be honest, I have a unlocked bootloader, so I haven't been completely paying attention.
If you have an unlocked bootloader, root process is still the same.

there is not going to be any new way to root 4.4 is not going to get a new exploit because 4.4.2 is out and Devs are working on finding a way to root it so the people with locked bootloaders can update.
if you want to root your device you have allready been giving the only 2 ways to do it
Locked bootloader - SlapMyMoto
Unlocked bootloader - Customer Recovery and SUPERSU
please dont bump your thread for info you allready have.
here is a link to both guides for both methods and a guide for unlocking your bootloader.
http://forum.xda-developers.com/showthread.php?t=2603358

Question about unlocked/rooted VZW Moto X

So I really miss rooting and modding my phones so I was thinking about do that Chinese method of unlocking my verizon wireless moto x. I just have a couple questions if anyone could answer I'd appreciate it. I can't find much info about 4.4.2 for the verizon moto x because before this unlock discovery, it wasn't possible
1. Once I unlock, is rooting just a simple adb command away?
2. Will I still be able receive android updates via OTA from verizon in the future? Assuming I remain on stock rom and don't flash a rom.
3. My main goal would to be able to tether. So is there a xposed mod to enable tethering on stock rom?
I've only seen this info for DE Moto Xs' and outdated info so I just want to be as updated as possible before I decide to do this.

tu3218 said:
So I really miss rooting and modding my phones so I was thinking about do that Chinese method of unlocking my verizon wireless moto x. I just have a couple questions if anyone could answer I'd appreciate it. I can't find much info about 4.4.2 for the verizon moto x because before this unlock discovery, it wasn't possible
1. Once I unlock, is rooting just a simple adb command away?
2. Will I still be able receive android updates via OTA from verizon in the future? Assuming I remain on stock rom and don't flash a rom.
3. My main goal would to be able to tether. So is there a xposed mod to enable tethering on stock rom?
I've only seen this info for DE Moto Xs' and outdated info so I just want to be as updated as possible before I decide to do this.
Click to expand...
Click to collapse
1. after you unlock the bootloader Rooting is as easy as installed TWRP or CWM then flashing SuperSU flashable sip and your rooted.
2. yes you will still get OTA updates. but in order to use the OTA update you will have to reflash the stock recovery. then take the update and reflash TWRP or CWM and SuperSU and your rooted again.
3.yea there is
hope this answered all your questions.

^^ this
Also, with an unlocked bootloader....you now have a phone that is no different than a dev edition. Aside from your warranty.
There's nothing else special about the dev edition. You keep your warranty on a DE.....that's where its specialness ends.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

dray_jr said:
1. after you unlock the bootloader Rooting is as easy as installed TWRP or CWM then flashing SuperSU flashable sip and your rooted.
2. yes you will still get OTA updates. but in order to use the OTA update you will have to reflash the stock recovery. then take the update and reflash TWRP or CWM and SuperSU and your rooted again.
3.yea there is
hope this answered all your questions.
Click to expand...
Click to collapse
Yeah thanks a lot! My plan would be to just run stock software but just add the tethering xposed module. But my main concern was receiving future OTAs so it's good to know that I still can. Is it pretty safe to root/unlock this phone? My galaxy nexus was a breeze(obviously being a nexus), but like my S3, there was no flashing back to stock recovery, taking OTA, an than flashing CWM again. At least it wasn't as easy as you described lol I think because there was always concern about whether the update removed ability to root access. Is that possible with this phone or with the unlocking of the bootloader, does that take that variable out? Thanks again. Oh yeah last question, once I'm unlocked, can I lock it back up again and go back to completely stock if I wanted to for some reason? Or is it a done deal.

tu3218 said:
Yeah thanks a lot! My plan would be to just run stock software but just add the tethering xposed module. But my main concern was receiving future OTAs so it's good to know that I still can. Is it pretty safe to root/unlock this phone? My galaxy nexus was a breeze(obviously being a nexus), but like my S3, there was no flashing back to stock recovery, taking OTA, an than flashing CWM again. At least it wasn't as easy as you described lol I think because there was always concern about whether the update removed ability to root access. Is that possible with this phone or with the unlocking of the bootloader, does that take that variable out? Thanks again. Oh yeah last question, once I'm unlocked, can I lock it back up again and go back to completely stock if I wanted to for some reason? Or is it a done deal.
Click to expand...
Click to collapse
the unlocking the bootloader process is kind of a pain but not too bad.
custom recovery and root are as simple as one command and one flashable zip
as long as you follow directions and read before doing anything then it should be safe. but rooting and modifying your phone is never %100 save.
when you unlock your bootloader you will always be able to root your phone no matter what android version your on. but it is always possible that they make some crazy change and we have issues.
once unlocked you can relock with with "fastboot oem lock" but that stupid warning msg about you bootloader being unlocked won't go away unless you flash a custom boot screen.
i hope i answered all your questions to your full needs and if you have any more please feel free to ask here or PM me if need be.

Unlocking the bootloader is pretty easy if you have adb setup. Don't forget to backup via helium (download to computer or cloud not local.) since unlocking will delete everything and helium can work without root.
Xposed module is great, less intrusive than flashing roms and you can easily get the tethering, etc.
Sent from my Nexus 7 using Tapatalk

[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.

New Moto X. can I put a rom on it?

I had a Moto X that I unlocked via the China seller, and it's being replaced because it's bricked. is there a way to put roms on a locked device? or can I unlock the bootloader again for cheap? I paid roughly 40 dollars for it last time.

jcase has a thread for using an exploit to root your phone without unlocking the bootloader. It can be found here:
http://forum.xda-developers.com/moto-x/orig-development/root-write-protection-bypass-motox-t2444957
NOTE: Please read the entire jcase link so you understand the risk/process!
Is there a reason why you want a custom ROM? It's certainly your choice, and respectable but if you're looking for minor tweaks to make it look different you may just want to try the GravityBox module with the Xposed Framework. That way you can just worry about rooting your phone, and then tweaking everything else to your liking after that.

I enjoy PA pie along with halo, PA has the best pie controls in my opinion. So it seems they sent me a moto x on 4.4.2, is my only option pie root than using safestrap? Or what is the best way to go about putting a ROM on this?

ovismos said:
jcase has a thread for using an exploit to root your phone without unlocking the bootloader. It can be found here:
http://forum.xda-developers.com/moto-x/orig-development/root-write-protection-bypass-motox-t2444957
NOTE: Please read the entire jcase link so you understand the risk/process!
Is there a reason why you want a custom ROM? It's certainly your choice, and respectable but if you're looking for minor tweaks to make it look different you may just want to try the GravityBox module with the Xposed Framework. That way you can just worry about rooting your phone, and then tweaking everything else to your liking after that.
Click to expand...
Click to collapse
^^^

scottshebs said:
^^^
Click to expand...
Click to collapse
You'll need a way to get a custom recovery running to install the ROM. TBH, I have a Dev Edition VZW Moto X, so all I do is unlock my bootloader.
Having that being said it looks (from what I read!) like Safestrap allows you to use a custom recovery, in addition of making nandroids and such. From what you're telling me, it pretty much looks like the way to go.

ovismos said:
You'll need a way to get a custom recovery running to install the ROM. TBH, I have a Dev Edition VZW Moto X, so all I do is unlock my bootloader.
Having that being said it looks (from what I read!) like Safestrap allows you to use a custom recovery, in addition of making nandroids and such. From what you're telling me, it pretty much looks like the way to go.
Click to expand...
Click to collapse
Would the 4.4.2 pie root work? It says it does not disable write protection and it is a tethered root.

Right. And safestrap won't work on 4.4.2.
So no, unless you unlock the bootloader again, you won't be able to flash a custom rom or recovery unfortunately.

scottshebs said:
Would the 4.4.2 pie root work? It says it does not disable write protection and it is a tethered root.
Click to expand...
Click to collapse
It doesn't look like it.
http://forum.xda-developers.com/moto-x/moto-x-qa/att-moto-x-rooting-long-term-effects-t2854742
From KidJoe in that post:
"As for safestrap, I don't use it since I have a Dev Edition and unlocked my bootloader. There are some threads and discussions over on Rootzwiki.com BUT you will need to be rooted with write protection disabled to use SafeStrap... Since you are now on 4.4.2, you can't disable write protection, so safestrap is out. "
So I think customer recovery is out unless you get a bootloader unlocked. And without custom recovery, you wouldn't be able to do a custom ROM.
You can still root the stock ROM though! That's what the PIE method will do. Don't think that will give you custom recovery.

Also, you want TowelPieRoot. Not either individually. That will give you root, but not disabled write protection. So mostly it's only useful for certain apps to be used.

KJ said:
Right. And safestrap won't work on 4.4.2.
So no, unless you unlock the bootloader again, you won't be able to flash a custom rom or recovery unfortunately.
Click to expand...
Click to collapse
Beat me to it.

ovismos said:
Beat me to it.
Click to expand...
Click to collapse
So I'm basically ****ed. Any possible way to downgrade to 4.4?
KJ said:
Also, you want TowelPieRoot. Not either individually. That will give you root, but not disabled write protection. So mostly it's only useful for certain apps to be used.
Click to expand...
Click to collapse

scottshebs said:
So I'm basically ****ed. Any possible way to downgrade to 4.4?
Click to expand...
Click to collapse
Downgrading is a dangerous thing on the X... It can easily end up in a brick, or other issues... Or a brick later.
No one who knows how this phone works ever recommends downgrading.
So no.... You are out of luck right now.
You can try the Middleman again... Or wait for a Possible exploit maybe being released, sometime.
But most advise not to upgrade either until this exploit that maybe will come out comes out. In vase 4.4.4 is incompatible with it.
It will also cost you money though.
---------- Post added at 03:17 PM ---------- Previous post was at 03:11 PM ----------
BTW, mixing the dangerous on its own downgrading with slapmymoto and safestrap is a definite recipe for disaster.

scottshebs said:
So I'm basically ****ed. Any possible way to downgrade to 4.4?
Click to expand...
Click to collapse
Not the parts that matter when it comes to disabling write protection on a locked boot loader phone, and certainly not safely for the rest of the Roms.
Rather than retype...
KidJoe said:
No.
For ALL Developer Editions Moto X, and some carrier editions (Like T-Mobile, Sprint, Rogers and others), Motorola freely gives away the BootLoader Unlock codes when requested On Motorola's Web SIte. In the case of the Non-Developer Editions, it voids their warranty to request the code. However, for some carriers (like ATT, Verizon and republic Wireless in the USA) motorola does not give out the unlock code.
So when you get your X, try to get the unlock code from Moto's web site. Then....
If you can get the code, and unlock the bootloader, you can root and disable write protection no matter what ROM is on your phone.
If you can NOT unlock your bootloader, and you are on 4.4.2 you can use TowelPieRoot to root (but write protection is still enabled).
If you can NOT unlock your bootloader, and your are on 4.4.4 you can not root.
If you can NOT unlock your bootloader, and by some miracle your phone is still on 4.4 (aka 4.4.0) or below, you can look at SlapMyMoto and MotoWpNoMo to root and disable write protection. HOWEVER, once you upgrade you will lose write protection, and be subject to the above conditions on rooting depending on your ROM version
And no, if you are on 4.4.4 you can NOT fully downgrade to 4.4.2 or lower. If you are on 4.4.2 you can NOT fully downgrade to 4.4 (aka 4.4.0) or lower! If you try, you will likely brick your phone or set it up to brick with future OTA's.
EDIT: And if Moto's web site doesn't give out your bootloader unlock code, you MIGHT have a chance using the China Middleman (see the thread in the general section). If its available and you can purchase that way, you can then unlock your bootloader exactly as if you got the code from Moto's own web site and follow any instructions as if you got the code from moto. The only difference is where you got the code, and how much it cost.
If you decide to go the China Middleman route, see -> http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177/post52648309
Click to expand...
Click to collapse
oh and about safestrap, it needs write protection disabled to install. Something that can only be done on 4.4.0 and 4.2.2 with camera fix Roms if you have a locked boot loader

KidJoe said:
Not the parts that matter when it comes to disabling write protection on a locked boot loader phone, and certainly not safely for the rest of the Roms.
Rather than retype...
oh and about safestrap, it needs write protection disabled to install. Something that can only be done on 4.4.0 and 4.2.2 with camera fix Roms if you have a locked boot loader
Click to expand...
Click to collapse
****
So if I towelpieroot I could use xposed for the time being?

scottshebs said:
****
So if I towelpieroot I could use xposed for the time being?
Click to expand...
Click to collapse
Seems people have trouble getting Xposed to work. Read through that thread about it.