Database Develop

Has anyone CID ulocked and had it not void the warranty

Ive been looking for a while and no one is actually sure about voiding the warranty. Has anyone done it and sent it in? Can some one explain about cid unlocking a little. Reading the other posts just gets me (and im sure others) confused

jawnsixteen said:
Ive been looking for a while and no one is actually sure about voiding the warranty. Has anyone done it and sent it in?
Click to expand...
Click to collapse
Let me make it simple... CID Unlock voids your warranty. period. The question comes in that when you try to do warranty work is whether they will notice or not. I've heard some say they don't, and others have said they do. So in a nutshell, just understand that you ARE VOIDING your warranty. You may or may not be "caught" though if you try to get warranty work, but you made the decision to do something that voids it, so you have to live with that choice.
Can some one explain about cid unlocking a little. Reading the other posts just gets me (and im sure others) confused
Click to expand...
Click to collapse
If you can't read and understand this post:
http://forum.xda-developers.com/showthread.php?t=285435
then you have no business doing this procedure. Dr. P has written an excellent post that takes you through the process step by step. Very simple and even tells you what to look for as you do it. There is no point trying to explain it further as it would be the exact same post as Dr. P's since it lays it out step by step in full detail.

ok, thank you.
now just one last question, i have upgraded to the newest tmobile rom, and i read somewhere that by doing that it unlocks somthing, did i read wrong?

jawnsixteen said:
now just one last question, i have upgraded to the newest tmobile rom, and i read somewhere that by doing that it unlocks somthing, did i read wrong?
Click to expand...
Click to collapse
I'm not aware of installing the newest (2.26?) TMobile ROM unlocking anything. You need to do the CID Unlock procedure and then finish by installing a rom like the TMobile 2.26 official rom. But jsut installing this rom doesn't unlock anything, just gets you to a current stable base to work off of for doing custom roms (very important step that too many people seem to be skipping).

Can anyone prove locked bootloader?

I've read a ton of posts on this topic and I understand the general consensus is that the bootloader is locked, but has any developer confirmed this? I asked Chainfire about a cf auto-root and he just assumed the bootloader was locked. People assumed this about the tmobile variant as well and apparently tmobile didn't lock the bootloader as people are rooting as we speak. I just wondered if it was even possible to check without the firmware being released.

johnnyutah22 said:
I've read a ton of posts on this topic and I understand the general consensus is that the bootloader is locked, but has any developer confirmed this? I asked Chainfire about a cf auto-root and he just assumed the bootloader was locked. People assumed this about the tmobile variant as well and apparently tmobile didn't lock the bootloader as people are rooting as we speak. I just wondered if it was even possible to check without the firmware being released.
Click to expand...
Click to collapse
I would but I don't know how. I tried to Google it but didn't come up with a whole lot of info.

johnnyutah22 said:
I've read a ton of posts on this topic and I understand the general consensus is that the bootloader is locked, but has any developer confirmed this? I asked Chainfire about a cf auto-root and he just assumed the bootloader was locked. People assumed this about the tmobile variant as well and apparently tmobile didn't lock the bootloader as people are rooting as we speak. I just wondered if it was even possible to check without the firmware being released.
Click to expand...
Click to collapse
Need to try and flash something, but theres nothing out to flash lol.... Also ATT 99.9 percent of the time like Verizon locks their BLs, there were reports that TMO was locking it's as well but it seems the initial batch is unlocked, could change but I would count on the ATT variant being unlocked.

Guys, it's LOCKED. No, I can't confirm it, but why would AT&T say they don't support unlocked bootloaders and then ship the S5 with an unlocked bootloader? I think not.

MattMJB0188 said:
Guys, it's LOCKED. No, I can't confirm it, but why would AT&T say they don't support unlocked bootloaders and then ship the S5 with an unlocked bootloader? I think not.
Click to expand...
Click to collapse
Pretty much this, which means no root, till a new exploit is found...but how many actual ATT devs are there that planned on getting the S5

djkinetic said:
Pretty much this, which means no root, till a new exploit is found...but how many actual ATT devs are there that planned on getting the S5
Click to expand...
Click to collapse
Probably not a lot. When the S4 had its bootloader patched last year development went down the drain, and fast. Everyone kept saying that the developers will unlock it, and they NEVER DID.
I am not trying to dis-respect any developers on here, but I do not like safestrap. Its no where as good as CWM-Recovery. I also loved flashing AOSP roms.

MattMJB0188 said:
Guys, it's LOCKED. No, I can't confirm it, but why would AT&T say they don't support unlocked bootloaders and then ship the S5 with an unlocked bootloader? I think not.
Click to expand...
Click to collapse
What you say makes perfect sense, I'm just saying that it would be nice to have it confirmed. With all of the back and forth between tmobile and their "Uncarrier" promotions and att's counter marketing, maybe att changed their minds to help their image, who knows, it's just a wishful dream I guess. Hopefully when sammobile makes the firmware available, someone can get Chainfire the recovery partition and he will create a cf auto-root for us to try.

johnnyutah22 said:
What you say makes perfect sense, I'm just saying that it would be nice to have it confirmed. With all of the back and forth between tmobile and their "Uncarrier" promotions and att's counter marketing, maybe att changed their minds to help their image, who knows, it's just a wishful dream I guess. Hopefully when sammobile makes the firmware available, someone can get Chainfire the recovery partition and he will create a cf auto-root for us to try.
Click to expand...
Click to collapse
Here's the problem though, if the BL is locked, cf root will most likely either not flash or not boot according to Chainfire, and if either of these happens not only are u without root, but also the knox warranty flag is tripped and your warranty is voided...unfortunately someone has to be willing to take one for the community to confirm all this.

djkinetic said:
Here's the problem though, if the BL is locked, cf root will most likely either not flash or not boot according to Chainfire, and if either of these happens not only are u without root, but also the knox warranty flag is tripped and your warranty is voided...unfortunately someone has to be willing to take one for the community to confirm all this.
Click to expand...
Click to collapse
Isn't that always the case with an unknown new device? I don't think xda would exist if people weren't willing to take some risks.

Looks like Chainfire is in irc looking for some att testers for auto-root. http://forum.xda-developers.com/showthread.php?t=2696537&page=23

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

Root and BL help

Hi everyone
Okay so Im going to ask a couple of noob questions here. I have been doing a lot of searching on and off xda but I still have a few doubts about rooting/flasing/unlocking my moto x.
If these questions have been asked before I apologize.
First off, I know that my motoX is from ATT, so it has a locked bootloader, right?
And also that it is a 16GB version so is definitely not DE.
I came across a source where it said I can still root my X with a locked bootloader and that must enable me to flash custom roms. Is this true? (I am a little hesitant about trusting websites other than xda). Why do we even need to unlock the bootloader then? if flashing custom roms is a go with root.
My phone is currently on 4.2.2. How am i supposed to find out if this is the pre or post camera update?
I would really appreciate your replies here as I am holding back from updating to KitKat (I read bootloader cant be unlocked on 4.4). Thanks a lot!

See this thread...
http://forum.xda-developers.com/showthread.php?t=2826159
And you can not flash roms without a custom recovery. And you can't have a custom recovery without an unlocked bootloader.
Whatever you read on another site sounds plain wrong. So proceed with caution.
You can try the thread in general about the Chinese Middleman and see if you can unlock your bootloader for $45. That's your only hope at the moment.
Good luck!

alimzia said:
Hi everyone
Okay so Im going to ask a couple of noob questions here. I have been doing a lot of searching on and off xda but I still have a few doubts about rooting/flasing/unlocking my moto x.
If these questions have been asked before I apologize.
First off, I know that my motoX is from ATT, so it has a locked bootloader, right?
And also that it is a 16GB version so is definitely not DE.
I came across a source where it said I can still root my X with a locked bootloader and that must enable me to flash custom roms. Is this true? (I am a little hesitant about trusting websites other than xda). Why do we even need to unlock the bootloader then? if flashing custom roms is a go with root.
My phone is currently on 4.2.2. How am i supposed to find out if this is the pre or post camera update?
I would really appreciate your replies here as I am holding back from updating to KitKat (I read bootloader cant be unlocked on 4.4). Thanks a lot!
Click to expand...
Click to collapse
There is either a lot of misinformation, or misunderstanding, or both. My guess is a little of both.
What you have read about is using an exploit to root and disable write protection. This is VERY different from actually unlocking the bootloader. These exploits are temporary, and they do not allow you to flash custom roms. They only allow flashing "stock-based, safestrap-compatible" ROMs. While this can be useful, there is no comparison to unlocking the bootloader. Be careful to not confuse the two.
@KJ has pointed you in the right direction. I only wanted to clarify that what you are referring to is "write-protect disable", which again is very different from bootloader unlock. Follow his advice and read up so you can better understand. In the mean-time, don't accept any OTAs until you have decided which option is best for you.
Good Luck :good:

samwathegreat said:
There is either a lot of misinformation, or misunderstanding, or both. My guess is a little of both.
What you have read about is using an exploit to root and disable write protection. This is VERY different from actually unlocking the bootloader. These exploits are temporary, and they do not allow you to flash custom roms. They only allow flashing "stock-based, safestrap-compatible" ROMs. While this can be useful, there is no comparison to unlocking the bootloader. Be careful to not confuse the two.
@KJ has pointed you in the right direction. I only wanted to clarify that what you are referring to is "write-protect disable", which again is very different from bootloader unlock. Follow his advice and read up so you can better understand. In the mean-time, don't accept any OTAs until you have decided which option is best for you.
Good Luck :good:
Click to expand...
Click to collapse
Okay i just need root for using titanium backup. Just one question though before i go on with it. After rooting my device (currently 4.2.2) can i continue to get OTA updates? If so, till what version (4.4 max)?
Again thankyou for your replies. Appreciate it.

alimzia said:
Okay i just need root for using titanium backup. Just one question though before i go on with it. After rooting my device (currently 4.2.2) can i continue to get OTA updates? If so, till what version (4.4 max)?
Again thankyou for your replies. Appreciate it.
Click to expand...
Click to collapse
If you are now on 4.2.2, you're one of the lucky ones..... You can still use the slapmymoto method and get full root with write protection disabled!!
See that section in the one stop shop thread.
?
But you can't go higher than 4.4 to keep all that.

Hey Sam i know this is Off topic but tell me more about Republic wireless and why you like them im thinking of switching from big red

qweesy said:
Hey Sam i know this is Off topic but tell me more about Republic wireless and why you like them im thinking of switching from big red
Click to expand...
Click to collapse
Sent you a PM.

KJ said:
If you are now on 4.2.2, you're one of the lucky ones..... You can still use the slapmymoto method and get full root with write protection disabled!!
See that section in the one stop shop thread.
?
But you can't go higher than 4.4 to keep all that.
Click to expand...
Click to collapse
Okay, after rooting will i be able to receive OTA for 4.4? If so, will it still be write protection disabled?

alimzia said:
Okay, after rooting will i be able to receive OTA for 4.4? If so, will it still be write protection disabled?
Click to expand...
Click to collapse
You would have to read the slapmymoto thread, but I believe you would flash 4.4 with fastboot . And that's it. If you upgrade to 4.4.2 or higher, you will have write protection enabled again.

KJ said:
You would have to read the slapmymoto thread, but I believe you would flash 4.4 with fastboot . And that's it. If you upgrade to 4.4.2 or higher, you will have write protection enabled again.
Click to expand...
Click to collapse
Yeah I read that. It is a long method...
I dont know why write protection is so important, i dont know what it does. All I care about is root. If write protection doesn't matter to me just as much, should i rather just receive the OTA to 4.4 right now and THEN root my device? (I just need root privileges for titanium and xposed)
What would you recommend? Is write disabling write protection that important? Thanks again.
Isnt there a way to root directly from 4.4? (Wont slapmymoto work?)

alimzia said:
Yeah I read that. It is a long method...
I dont know why write protection is so important, i dont know what it does. All I care about is root. If write protection doesn't matter to me just as much, should i rather just receive the OTA to 4.4 right now and THEN root my device? (I just need root privileges for titanium and xposed)
What would you recommend? Is write disabling write protection that important? Thanks again.
Click to expand...
Click to collapse
Yes, it is that important. Without write protect disabled, you have to re-root after every reboot. Titanium backup won't work fully because all changes are reverted upon reboot. You will have a heck of a time getting xposed to word if you even can without it disabled.
Yes you can update to 4.4 but not higher. If you use safestrap, you can flash stock based Roms all the way up to 4.4.4. But your bootloader and partition table will remain on 4.4 - this allows you to keep root and write protect disabled.
Be very careful. If you update the bootloader or partition table past 4.4 there is no going back and you will lose the ability to disable write protect permanently.
Basically, without write protect disabled, anything you change gets reverted back upon reboot. You also lose root and have to re-root after every reboot... Not very useful...

alimzia said:
Yeah I read that. It is a long method...
I dont know why write protection is so important, i dont know what it does. All I care about is root. If write protection doesn't matter to me just as much, should i rather just receive the OTA to 4.4 right now and THEN root my device? (I just need root privileges for titanium and xposed)
What would you recommend? Is write disabling write protection that important? Thanks again.
Isnt there a way to root directly from 4.4? (Wont slapmymoto work?)
Click to expand...
Click to collapse
I'm not a slapmymoto expert, since I never needed it... But I believe you need to start on 4.2.2 with it. Then upgrade. Again... You'd need to read on it.
With write protection disabled you can store to the system then. Definitely needed for Xposed.
Trust me.... There's people with locked bootloaders on 4.4.2 and up that would kill to be able to use slapmymoto. ?

Alright thanks a lot guys. Ive made up my mind, going to go through with it, definitely need xposed!
Oh btw just out of curiosity, does Towel-pie-root work with 4.4?

alimzia said:
Alright thanks a lot guys. Ive made up my mind, going to go through with it, definitely need xposed!
Oh btw just out of curiosity, does Towel-pie-root work with 4.4?
Click to expand...
Click to collapse
I believe so.... But people have trouble with Xposed.
---------- Post added at 07:27 PM ---------- Previous post was at 07:26 PM ----------
Same thing too.... Even IF you get Xposed to work... All undone on a reboot or power down.

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.