Related
Are there Amy methods to root after the OTA update on ATT MOTO X? I bought a moto x and ran the update before researching on how to root it. I'm currently showing version 139.12.54.
You can't, unless you have unlocked bootloader. I don't know if you can downgrade and then follow the procedure to keep root over OTA.
waiflih said:
I don't know if you can downgrade and then follow the procedure to keep root over OTA.
Click to expand...
Click to collapse
No. You cannot downgrade.
mandrsn1 said:
No. You cannot downgrade.
Click to expand...
Click to collapse
Yup. I'm stuck on this boat too. Did the ota. Can't downgrade. Can't root. If there is no intention to unlock the bootloaders for At&t, then I know I'm gonna put this on swappa for cheap.
But I think I'm going to hold out for a bit seeming that I'm really liking stock, and I have other phones to Dev on. I hope unlock comes our way.
Sent from my XT1058 using Tapatalk 4
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
Hello all.
Ok, I have read all the posts/threads for rooting and am still confused as each thread links to another which links to another, which changes another ,etc. Need proper organization of threads it looks like.
Anyway, I just received the GSM Unlocked MOTO X (NOT DEV ED.) for TMO or ATT.
How do I root? Again, I have read the threads and am terribly confused. I have the 4.2.2 software and have NOT updated to any OTA.
Can someone clearly highlight the steps I should be taking?
Am not a noob and currently own N5 and S4 Dev Edition.
Thanks!
ditto
I am also confused, do I download the pwnmymoto for the att or tmobile version? Just got my moto x today.
markwebb said:
Hello all.
Ok, I have read all the posts/threads for rooting and am still confused as each thread links to another which links to another, which changes another ,etc. Need proper organization of threads it looks like.
Anyway, I just received the GSM Unlocked MOTO X (NOT DEV ED.) for TMO or ATT.
How do I root? Again, I have read the threads and am terribly confused. I have the 4.2.2 software and have NOT updated to any OTA.
Can someone clearly highlight the steps I should be taking?
Am not a noob and currently own N5 and S4 Dev Edition.
Thanks!
Click to expand...
Click to collapse
RockMyMoto
then, MotoWpNoMo to keep root as w/o you have a "temp" root, or tethered, if that is the correct term. AKA, reboots/shutdowns can trip it back to stock w/o root.
so are these phones the x1053 or x1058?
buschris said:
so are these phones the x1053 or x1058?
Click to expand...
Click to collapse
X1053
Sent from my XT1053 using xda app-developers app
TKTAB911 said:
RockMyMoto
then, MotoWpNoMo to keep root as w/o you have a "temp" root, or tethered, if that is the correct term. AKA, reboots/shutdowns can trip it back to stock w/o root.
Click to expand...
Click to collapse
Thanks... then can I take the ota to kit Kat 4.4 or will I lose root? I did unlock bootloader BTW.
Sent from my XT1053 using xda app-developers app
markwebb said:
Thanks... then can I take the ota to kit Kat 4.4 or will I lose root? I did unlock bootloader BTW.
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
I am thinking of unlocking mine as well, and I am on 4.4 already, just got the phone today.
Not sure if I should unlock, it will be my daughters phone and I'll probably need the warranty
markwebb said:
Thanks... then can I take the ota to kit Kat 4.4 or will I lose root? I did unlock bootloader BTW.
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
Since you've unlocked the bootloader, follow the root directions for the dev edition. What you're doing is wholly unnecessary.
Unlock bootloader, download latest CWMR or TWRP and SuperSu, then fastboot (or mfastboot) flash recovery, boot into recovery, adb push supersu.zip /sdcard, flash in recovery. Done.
buschris said:
I am thinking of unlocking mine as well, and I am on 4.4 already, just got the phone today.
Not sure if I should unlock, it will be my daughters phone and I'll probably need the warranty
Click to expand...
Click to collapse
I'd start with root without unlocking.
nhizzat said:
Since you've unlocked the bootloader, follow the root directions for the dev edition. What you're doing is wholly unnecessary.
Unlock bootloader, download latest CWMR or TWRP and SuperSu, then fastboot (or mfastboot) flash recovery, boot into recovery, adb push supersu.zip /sdcard, flash in recovery. Done.
Click to expand...
Click to collapse
Thanks..that is what I was looking for. So, should I update to OTA first since I am unlocked, or root now per dev edition instruction? If so, then how would I take the OTA if I am on custom recovery? Is there a zip of the OTA?
Thanks again!
markwebb said:
Thanks..that is what I was looking for. So, should I update to OTA first since I am unlocked, or root now per dev edition instruction? If so, then how would I take the OTA if I am on custom recovery? Is there a zip of the OTA?
Thanks again!
Click to expand...
Click to collapse
You should take the 4.4 OTA first. In order to take the OTA you need to have stock recovery. Once you take the OTA then you can flash a customer recovery and flash a super user app through it.
Sent from my Moto X on KitKat
Dark9781 said:
You should take the 4.4 OTA first. In order to take the OTA you need to have stock recovery. Once you take the OTA then you can flash a customer recovery and flash a super user app through it.
Sent from my Moto X on KitKat
Click to expand...
Click to collapse
From current experiences with other devices, that is exactly what I did. I am now updated to 4.4, with custom recovery and root!
Thanks guys...shame this isn't in an updated simple "how to" thread
markwebb said:
Thanks guys...shame this isn't in an updated simple "how to" thread
Click to expand...
Click to collapse
It isn't difficult at all. People seem to be easily confused and make things more complicated than necessary.
markwebb said:
From current experiences with other devices, that is exactly what I did. I am now updated to 4.4, with custom recovery and root!
Thanks guys...shame this isn't in an updated simple "how to" thread
Click to expand...
Click to collapse
Rooting with an unlocked bootloader is perhaps the easiest thing to do. You know this from past experience so why would it be any different with the Moto X?
The real challenge is when you want to root with a locked bootloader (and even that is becoming gradually easier).
esskayy said:
Rooting with an unlocked bootloader is perhaps the easiest thing to do. You know this from past experience so why would it be any different with the Moto X?
The real challenge is when you want to root with a locked bootloader (and even that is becoming gradually easier).
Click to expand...
Click to collapse
Correct.
But i began the process with a locked bootloader and getting to the answer/correct path was a challenge in these threads compared to other threads.
So I took the plunge and unlocked.
Sent from my Nexus 5 using xda app-developers app
Title says it all. Will I get the new radio/bootloader when CM12 gets updated? The update includes the ability to use the 700Mhz TMobile freq as well as VoLTE.
They normally do, yes.
Custom ROMs do not provide bootloaders
rootSU said:
Custom ROMs do not provide bootloaders
Click to expand...
Click to collapse
I didn't think so. I went ahead and restored back to stock and updated to 5.1 from the google factory images. I'll probably go back to CM when they update to 5.1.
Thanks!
rootSU said:
Custom ROMs do not provide bootloaders
Click to expand...
Click to collapse
Cm does
Sent from my Nexus 6 using XDA Free mobile app
rootSU said:
Custom ROMs do not provide bootloaders
Click to expand...
Click to collapse
CM does. What they're currently doing is they are checking your bootloader version, and the ZIP refuses to flash if you're not on 5.1 bootloader (because downgrading the bootloader might be reason of all these bricks). If you are, then the ZIP flashes and writes bootloader (the version you already have) and radio again.
http://review.cyanogenmod.org/#/c/91181/
Tasssadar said:
CM does. What they're currently doing is they are checking your bootloader version, and the ZIP refuses to flash if you're not on 5.1 bootloader (because downgrading the bootloader might be reason of all these bricks). If you are, then the ZIP flashes and writes bootloader (the version you already have) and radio again.
http://review.cyanogenmod.org/#/c/91181/
Click to expand...
Click to collapse
OK I stand corrected, however, flashing CM will not upgrade the bootloader, which is what the OP asked.
The bricks mostly seem to occur for people who have locked their bootloader. They locked it then when android cannot boot, they cannot unlock it again. Most the threads I have seen have not involved anyone flashing older bootloaders yet they still have the problem. Whether, Android would boot for these people had they not locked it is uncertain. Its hard to say whether the OTA just didnt take and they didnt check it booted before locking the BL or whether the BL actually caused the loop once locked... But definitely people have this issue who have not attempted to downgrade.
One of the perks of using custom roms, I never update my bootloader.
The issue with cm specifically is that the zip attempted to downgrade the bootloader which isn't possible. Bad things followed.
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
The issue with cm specifically is that the zip attempted to downgrade the bootloader which isn't possible. Bad things followed.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ah OK. I don't tend to read threads that have "cm" in the title so I've missed that.
rootSU said:
Ah OK. I don't tend to read threads that have "cm" in the title so I've missed that.
Click to expand...
Click to collapse
(looks at this thread title) Hmm...
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
(looks at this thread title) Hmm...
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Yes. "Tend" . This one piqued my interest as it was asking about the bootloaders though.
rootSU said:
OK I stand corrected, however, flashing CM will not upgrade the bootloader, which is what the OP asked.
The bricks mostly seem to occur for people who have locked their bootloader. They locked it then when android cannot boot, they cannot unlock it again. Most the threads I have seen have not involved anyone flashing older bootloaders yet they still have the problem. Whether, Android would boot for these people had they not locked it is uncertain. Its hard to say whether the OTA just didnt take and they didnt check it booted before locking the BL or whether the BL actually caused the loop once locked... But definitely people have this issue who have not attempted to downgrade.
One of the perks of using custom roms, I never update my bootloader.
Click to expand...
Click to collapse
No, we haven't locked our bootloaders. They have moved all nightlies except one left there. I think that explains sth. Thats how it happens to most of us i think. I never locked my BL, and that happens too. Maybe too soon to judge . Now all i got is a hard bricked phone.
randy6644 said:
No, we haven't locked our bootloaders. They have moved all nightlies except one left there. I think that explains sth. Thats how it happens to most of us i think. I never locked my BL, and that happens too. Maybe too soon to judge . Now all i got is a hard bricked phone.
Click to expand...
Click to collapse
To be hoinest I haven't been following CM specific bricks. That may indeed be what is happening to CM users. I was talking seemingly out of context about all the other threads where peiople had upgraded using fastboot then relocked their BL's
rootSU said:
To be hoinest I haven't been following CM specific bricks. That may indeed be what is happening to CM users. I was talking seemingly out of context about all the other threads where peiople had upgraded using fastboot then relocked their BL's
Click to expand...
Click to collapse
relocking bootloader leads to a bootloop , and it's nothing like a real hard brick like mine. So sad~
rootSU said:
OK I stand corrected, however, flashing CM will not upgrade the bootloader, which is what the OP asked.
The bricks mostly seem to occur for people who have locked their bootloader. They locked it then when android cannot boot, they cannot unlock it again. Most the threads I have seen have not involved anyone flashing older bootloaders yet they still have the problem. Whether, Android would boot for these people had they not locked it is uncertain. Its hard to say whether the OTA just didnt take and they didnt check it booted before locking the BL or whether the BL actually caused the loop once locked... But definitely people have this issue who have not attempted to downgrade.
One of the perks of using custom roms, I never update my bootloader.
Click to expand...
Click to collapse
but they will upgrade the bootloader to 5.1, which means those running 5.0.2 will upgrade.
Most bricks are happening because CM includes the bootloader and you cannot downgrade bootlodaers, if you tried in fastboot it will stop you from doing this. CM uses an old way of accomplishing this which force downgrades the bootloader and messes up the partitioning, resulting in a brick.
I have seen 3 or 4 cases in person from this, and those users never relocked their boot loader like you described.
Circaflex said:
but they will upgrade the bootloader to 5.1, which means those running 5.0.2 will upgrade.
Click to expand...
Click to collapse
Great. Got it. At some point in the future, cm "will" upgrade the bootloader but right now they will refuse to flash.
I'm safe. Haven't used cm since cm6.
Hey does anyone know if or when the moto x 2014 will get its bootloader officially unlocked by Motorola. Was researching on the site and it seems as though Verizon models are getting their bootloaders officially unlocked. Since they said the carrier models aren't getting marshmallow they could at least unlock our bootloaders so wencan get root and flash some roms. Or if anyone knows how to get it done unofficially..... I'm all ears. Thanks
I'm unlocked on Verizon, but att I don't know if or when. If you haven't upgraded above 5.0 you can root with mofo and unlock with sunshine.
Zekedw said:
Hey does anyone know if or when the moto x 2014 will get its bootloader officially unlocked by Motorola. Was researching on the site and it seems as though Verizon models are getting their bootloaders officially unlocked. Since they said the carrier models aren't getting marshmallow they could at least unlock our bootloaders so wencan get root and flash some roms. Or if anyone knows how to get it done unofficially..... I'm all ears. Thanks
Click to expand...
Click to collapse
That's the thing, motorola never announced that verizon got it. It just magically started to work when someone tried to unlock his bootloader then they told all of us. There is no way to know if it will ever be able to be unlocked. But everyone can keep trying, maybe one day it will work.
Sent from my XT1095 using Tapatalk
oraixearl said:
I'm unlocked on Verizon, but att I don't know if or when. If you haven't upgraded above 5.0 you can root with mofo and unlock with sunshine.
Click to expand...
Click to collapse
Already upgraded to 5.1
Zekedw said:
Already upgraded to 5.1
Click to expand...
Click to collapse
Don't know of a way outside of unlock code from moto then. If you can gain root (at least temp root) sunshine will still unlock it. But haven't seen anybody figure it out yet for 5.1. Maybe keep an eye on kingroot see if they've got it yet.
oraixearl said:
Don't know of a way outside of unlock code from moto then. If you can gain root (at least temp root) sunshine will still unlock it. But haven't seen anybody figure it out yet for 5.1. Maybe keep an eye on kingroot see if they've got it yet.
Click to expand...
Click to collapse
It works now !!!
Sent from my XT1097 using Tapatalk
Yann68 said:
It works now !!!
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
What works now? Can you please guide me how to root and unlock bootloader of moto x 2014 at&t
abdullah.ahsan11 said:
What works now? Can you please guide me how to root and unlock bootloader of moto x 2014 at&t
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x-2014/general/root-bootloader-unlock-att-xt1097-5-1-t3309889
xconomicron said:
http://forum.xda-developers.com/moto-x-2014/general/root-bootloader-unlock-att-xt1097-5-1-t3309889
Click to expand...
Click to collapse
I've tried this already almost 20 times. Rooting via king Root won't get past 56% every time. Getting failure again and again and again.
abdullah.ahsan11 said:
I've tried this already almost 20 times. Rooting via king Root won't get past 56% every time. Getting failure again and again and again.
Click to expand...
Click to collapse
Clear the cache of the app after it fails. Read the thread. It is random how it works...but it does.