Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358
You'll have to unlock the bootloader. No way around it.
Should I be nervous about unlocking the bootloader?
Didn't my Samsung phone come with it already unlocked?
Should you be nervous? Google the pros and cons then decide for yourself.
No phone nor tablet comes with an unlocked bootloader.
I have an XT1053 and just recently unlocked the bootloader through the Motorola site. I waited until now because my original warranty just expired and knew that unlocking the bootloader would void my warranty. I wanted to unlock the bootloader under 4.4.4 because I didn't know if there would be any problems once Lollipop was offered as an update. The unlock process went very smoothly and took only a few minutes. You probably already know that unlocking wipes your phone, so be prepared to reinstall apps and other files. I have not rooted yet because I'll probably wait to do that after the Lollipop OTA comes around. Even then, I may not root because I'm really pretty happy with the phone as it is. For me, unlocking the bootloader was just of way of preserving the future option to root.
stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
mac1996 said:
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
Do you have fastboot?
if yes, go to your phone bootloader.
Connect to your computer by USB.
Type the following in cmd. (place your recovery img file in fastboot directory)
fastboot flash recovery (your recovery name).img
Sent from my XT1053 using XDA Free mobile app
Check the sticky threads. There's only a year and halfs worth of information available to you here and all over the rest of the internet.
stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
At any point after unlocking the bootloader... To flash recovery, did you do the following...
Start the phone in Fastboot/Bootloader mode.. then from the PC type...
mfastboot flash recovery YourRecovery.img
mfastboot reboot-bootloader
Follow onscreen directions to use vol down key and highlight recovery, then use vol up to select/enter recovery. Once in recovery you can reboot the phone and proceed with whatever you want.
Failure to reboot-bootloader and entering recovery immediately after flashing recovery (i.e. doing something else first) can result in the recovery not sticking.
4.4.4
a year old post by dray_jr says the following:
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
can someone explain this to me? I got my phone around august 2014, it came with 4.4.3 and right now I'm on 4.4.4.
If I use the motorola website and follow their bootloader unlock steps am I fine? will I have any brick issues stated from the quote above?
Thread
Nevermind guys, found the perfect thread for 4.4.4 root!
Thread: http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Final question: I don't have to install supersu root if i install CM12 once i get into TWRP recovery am i correct? (since cms come rooted)
Would flashing a JB kernel (and only the kernel) work to root it as described here?: http://forum.xda-developers.com/crossdevice-dev/sony/guide-xperia-kitkat-4-4-4-rooting-t3003520
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
nhizzat said:
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
Click to expand...
Click to collapse
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
dagoban said:
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
Click to expand...
Click to collapse
I don't proclaim to know the ins and outs of all things android, but I do know this.. Just because a phone has android 4.4.4 doesn't mean its the same 4.4.4 with the same exact flaws and vulnerabilities, susceptible to the same exact root processes. Its why an exploit to root one phone, often doesn't work to root another.
In the case of the Moto X with a locked bootloader, JCASE has come out with many processes exploiting vulnerabilities for Android and the Apps on the Moto X to not only root it, but disable its write protection. As new OTA's have patched an exploit, he came out with other ways.
Starting wth 4.4.2, the vulnerability in the bootoader to disable write protection has been patched.
Jcase's Sunshine tool works on the X with 4.4.3 and lower, and only SOME with 4.4.4. It needs temp root first, etc. For whatever reason, we don't have a way to even temp root the 2013 X on 4.4.4 enough to allow Sunshine to do its work. And despite being asked many times, Jcase pretty much said in the Sunshine discussion threads that v3.0 wont have Moto X 4.4.4 support (unless he changed his mind and I missed it). Yet sunshine and its root processes, etc work on other phones (HTC) with 4.4.4.
But back to the thread you link...
On the X, due to its security measures, with a locked bootloader, you can only flash the Moto signed ROM for your phone. Nothing else. Because of this, you can't flash a custom recovery. To flash items, we use mFastboot and RSDLite. They need the img files, or bin files. If we make our own, they wont be signed, so they wont flash to a phone with a locked bootloader. And you can't package them into a flashable ZIP because stock recovery looks for the Moto digital signature (which we don't have and can't fake), and you can't install TWRP/CWM/Philz/etc to flash that way. So if you manage to pull the JB kernel out of the Moto SBF file, you wont be able to flash it.
Due to write protection on the 2013 X, any changes made to /System and a few other places, will be lost at power off/on. In other words, if you do manage to flash it (or push via adb), it wont stick due to write protection.
We've seen people try and manipulate their phone by trying to DOWNGRADE their ROM. Well, this doesn't work either. GPT.BIN (partition table), and Motoboot.img (bootloader, TZ, and a few other things) get in the way. Even on an X with an Unlocked bootloader, you can't downgrade these parts. Enough who attempted this have ended up bricking their phone immediately, or with later taking an OTA. Sure you can try to flash just system.img, and while that has less risk for bricking, people who have tried this were still not able to use the older Root Exploits (that worked if you hadn't upgraded already). People have tried flashing everything but GPT.BIN and MotoBoot.img. Again, it didn't help with rooting. Not to mention with a missmatched system.img or other parts, features on the phone may not always work properly (going Settings -> Security comes to mind), and you are at risk of bricking should you take an OTA update.
Since that process exploits a vulnerability, and its out there (so the vulnerability is in the public), I'm sure if it worked or was possible, JCASE, Beaups, or others would have put something together.
Now, back on topic of the XT1053... it has an Unlockable bootloader. Unlocking the bootloader disables write protection, and allows you to flash non-moto stuff. So unlocking the bootloader, flashing TWRP, reboot bootloader, enter TWRP and root, is quick, easy, effective, and doesn't rely on vulnerabilities on the phone to be exploited so patches/updates haven't got in the way. Plus you don't have to wait for someone to find them and create a repeatable process.
Related
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
vespadaddy said:
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
Click to expand...
Click to collapse
use fastboot to flash stock recovery on your phone, undo the tethering hack, and take the OTA.
Since you have a Dev Edition with unlocked bootloader, Root and Write Protection Disable survive. You can leave stock recovery on there, unless you really need the features of TWRP like backup, etc. Then you just have to do any NEW hacks for tethering (for 4.4.2 its different than 4.4). Or you can use wifi tether for root app instead of hacks.
There was talk about repackaging the OTA to be installed via TWRP or CWM, but I don't recall the thread containing an actual zip, and think they were mostly talking about what needs to be done. Since its easy enough with the Dev Edition to update, its likely not worth the work repacking it, since it wont work for those with LOCKED bootloaders.
vespadaddy said:
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
Click to expand...
Click to collapse
I pretty much did what was described below and maintained TWRP and root. Note: you must enter TWRP and exit after the update to reinstall SU.
http://forum.xda-developers.com/showpost.php?p=50639372&postcount=25
except I chose not to flash the following...
fastboot flash logo logo.bin
fastboot erase customize
fastboot erase clogo
Whether it makes sense or not my goal is to not "upgrade" my bootloader or GPT until absolutely necessary as they can't be downgraded. The risks associated with doing this are hotly debated so understand what you are getting into if you choose to do this to your phone.
Reverted thether hack.
Recovery tool worked for me on moto x dev. flashed stock recovery. Took ota 442. Flashed twrp. kept root and stuff. no need for a computer.
http://forum.xda-developers.com/showthread.php?t=2334554
Hey guys,
So i was interested in installing a custom rom im my moto x and started by trying to root it.
Every thing was going fine, but after i placed the unlock code via CMD, i've got an error during the root process and my phone just died. Now all that i've got is a black screen, no matter if I try to hard reset or anything.
Any idea?
tl;dr my phone just died in the root process, wtf can i do?
Unlock code? Root process?
Which model do you have? Which version of Android was it on? What exactly were you doing or using to root or unlock?
Which model you have used ?
I have a x1058, it was on android 4.4.2 and was using a tutorial from a brazilian guy, wich involved downloading adb and fastboot scripts and run them trough cmd.
You will need to be far more specific in what commands you did, if any...and the specific errors.
Only way we'll know what's happened.
It may be of some help if you post the tutorial you followed and say exactly at what step things went wrong.
Sent from my Moto X using Tapatalk Pro
monzillo said:
I have a x1058, it was on android 4.4.2 and was using a tutorial from a brazilian guy, wich involved downloading adb and fastboot scripts and run them trough cmd.
Click to expand...
Click to collapse
The XT1058 has a locked bootloader, so I hope that tutorial didn't have you try to downgrade your ROM in order to use SlapMyMoto/MotoWpNoMo to root and disable write protection.
SlapMyMoto/RockMyMoto/etc, used on 4.4 and lower, involved downgrading the rom to use an exploit in 4.2.2 to gain root. But with 4.4.2 you can't downgrade the rom safely, without risk of bricking your phone anymore. Additionally, 4.4.2 closed the exploits used by SlapMyMoto/RockMyMoto to gain root, and the exploit used by MotoWpNoMo to disable write protection.
As others have suggested, post a link to the turtorial, and any error messages you saw while running the scripts.
Also, try booting into bootloader/fastboot mode. Can you get there? What version bootloader does it say you are on? I believe 30.B4 is 4.4.2 and 30.71 is 4.4 and 4.2.2 w/camera fix. If you have 30.B4, then your only fix might be using RSDLite to flash the 4.4.2 SBF for your carrier, or mFastboot to individually flash all parts of 4.4.2 on your phone, and then forget about rooting unless Moto's web site gives out the bootloader unlock code for your phone.
Hi there, I have a UK moto x model xt1052. I am looking to root and flash custom ROMs onto my device, but am concerned that I will brick the device by using a method intended for a different model of moto x.
The UK moto x was shipped with android 4.4.2, later updated to 4.4.4 so there are no earlier builds of android to downgrade to.
Any help will be appreciated.
Timsteels
Figure out if you can, and want to unlock your bootloader.... Then go to the One Stop Shop root thread sticky at the top of the general section. It has all your options.
---------- Post added at 07:31 PM ---------- Previous post was at 07:30 PM ----------
And root methods have nothing to do with your model. It mostly has to do with locked or unlocked bootloader state.
timsteels said:
Hi there, I have a UK moto x model xt1052. I am looking to root and flash custom ROMs onto my device, but am concerned that I will brick the device by using a method intended for a different model of moto x.
Click to expand...
Click to collapse
Process to root the X is the same whether you have an XT1052, XT1053, XT1056, XT1060, etc. As KJ said, with 4.4.4 its all about can you unlock your bootloader or not. (and do you mind voiding your warranty doing so since you don't have a Developer Edition X).
See the One Stop Shop thread, in particular this post -> http://forum.xda-developers.com/mot...-confusion-t2826159/post54671918#post54671918
timsteels said:
The UK moto x was shipped with android 4.4.2, later updated to 4.4.4 so there are no earlier builds of android to downgrade to.
Click to expand...
Click to collapse
And you do NOT WANT TO DOWNGRADE!!!!! Doing so you will risk bricking your phone now, or when you later take an OTA. There are many warnings posted in the forums to not downgrade, and many threads started by those who have ignored the warnings and tried to downgrade and have bricked their phones!!!
Besides that, two key parts, GPT.Bin (partition table), and Motoboot.img (contains bootloader, TZ and a few other parts) will NOT downgrade successfully once on 4.4.2, 4.4.3 or 4.4.4. so any past exploits requiring the older roms wont work anyway.
So unlocking the boot loader is the same process as the us variants of the moto x? I just don't want to turn my phone into a paperweight! I'm not too worried about the warranty, as I am usually careful with my phones.
Unlocking and recovery and ROOT is all the same on any X. What matters is Android version (cause locked 4.4.4 guys can't root in any way), locked or unlocked bootloader and that's about it.
An unlocked X is the same no matter a Dev Edition or any other. All the same.
As far as bricking... The only time that's a giant threat is trying to downgrade. Not saying an X has never been bricked another way, cause everything we do has some risk to it. But most issues are curable.
Ok thanks for the info! And in terms of custom roms, do I need to install one built for the xt1052, or will other ones also work?
That is not something I know about. Never flashed one. Just stock and gravity box.
Read the opening post of rom threads, should have what devices it's for. ?
Ok thanks again! Is there much point in installing the exposed framework or anything similar?
I think many rooted X members here use Gravity Box while on stock rom... So they can customize some things. ?
Ok cool. I will have a look and decide if I want to go ahead. Thanks for all the assistance
timsteels said:
Ok thanks again! Is there much point in installing the exposed framework or anything similar?
Click to expand...
Click to collapse
Many root, install Xposed and some modules to customize their phone rather than running any Custom Roms because the custom roms often lose the Moto features like the notifications and such.
Ok and if I root, unlock bootloader and install xposed, will my phone still receive the ota updates? Or is it a case of reversing the procedure to get the ota updates?
timsteels said:
Ok and if I root, unlock bootloader and install xposed, will my phone still receive the ota updates? Or is it a case of reversing the procedure to get the ota updates?
Click to expand...
Click to collapse
First you can't install an OTA with a custom recovery (like TWRP, CWM, Philz) on the phone. You'll get stuck in a boot loop.
Next, in every OTA there is a "pre-validation check" (a manifest file which contains a list of items to be checked and a SHA type hash code for a type of check sum verification of each part/file its looking at.)
Anything that alters your phone from what the Pre-Validation check is looking for will cause the OTA to fail. So if you modify or remove and system files, have the wrong recovery, etc., those parts would not pass the pre-validation check so the OTA would fail.
Xposed also needs to be disabled, or it will cause the OTA's pre-validation checks to fail.
So it really comes down to what you do after you root.
If you flash TWRP, Root, install Xposed and a few modules, and nothing else, then to take an OTA, you'll need to disable Xposed (there is a flashable zip on your /SDcard to do this), then flash stock recovery.img back on your phone, then you can take the OTA. Once the OTA is successfully installed, you can re-flash custom recovery, re-root if necessary, and re-enable Xposed.
If you rename/delete/modify files from /system (like some do to get rid of bloat), you'll need to un-do that.
If you're like me, I just unlocked, rooted, and installed apps that use root (like Root Explorer, Greenify, Wifi Tether for root), so all I do is flash stock recovery on, take the OTA, and if I lost root, flash TWRP and re-root.
For more see -> http://mark.cdmaforums.com/MotoX-OTA.html
Ok that's good to know. I'll have a think about it. I may wait until lollipop comes out for the moto x.
I've searched and found variations on these questions in other posts, but I didn't come across any pertaining quite to my situation, so I wanted advice before I do something wrong and brick my phone.
I have a Sprint Moto X, unlocked & rooted, running 4.2.2 (I think pre-camera update). I'd like to upgrade to stock Sprint Lollipop (when it comes out) & stay unlocked & rooted.
My understanding of the steps that need to be taken:
1. Unroot my device
2. Re-lock my device
3. Flash TWRP and boot to recovery
4. Flash stock Sprint Lollipop
5. Unlock, then re-root device
Is any of this extraneous, or am I leaving anything out? Do I need to upgrade to KitKat before going to Lollipop?
I also have Xposed installed and I have tweaked the PRL on my device ... this shouldn't complicate the upgrade, right?
Relocking is useless, and unless you know what you're doing, flashing stock updates in custom recovery shouldn't be done. You don't necessarily need to unroot either, just make sure all stock system files are still in place.
Sent from my Moto X
imnuts said:
Relocking is useless, and unless you know what you're doing, flashing stock updates in custom recovery shouldn't be done. You don't necessarily need to unroot either, just make sure all stock system files are still in place.
Sent from my Moto X
Click to expand...
Click to collapse
i have a sprint X and if i am going to update this is how i have allways done it with no issues at all.
you can leave your bootloader unlocked that is no a issue. but i always take OTA's and you cant take a OTA with a modded system. so i allways just flash my stock firmware package. that way it removes my custom recovery. Root, and all Xposed changes. Then i take the OTA and just reinstall TWRP, then SuperSU then what ever else you want.
this is the safest way i have found to update, the nice thing about Unlocked Sprint phones is we can easily Root are phones via TWRP and SuperSu.
just my .02 you can do it how ever you like but this is how i am going to do it when the OTA finally comes out if it ever does.
I got my MotoX about a year ago, non-dev edition on VZW. I installed Hashcode's SafeStrap custom recovery and flashed Kryptonite's "stock" 4.4.2 rom to the stock slot. That satisfied me for the time being and I lost track of current development on the Moto X.
I've been itching for a change though and a software update is just the fix. Since I haven't kept up thoug, I really don't know how to go about it. I've been reading about the options but I don't know where my phone stands. Can I go the CM11-> CM12 route with Safestrap even though my bootloader is locked? Or do I need to use SunShine to unlock my bootloader and install a different custom recovery? And do I need to revert to stock to stock at any point? I'm pretty comfortable with all of this, I just need some nudging in the right direction.
llsmith said:
I got my MotoX about a year ago, non-dev edition on VZW. I installed Hashcode's SafeStrap custom recovery and flashed Kryptonite's "stock" 4.4.2 rom to the stock slot. That satisfied me for the time being and I lost track of current development on the Moto X.
I've been itching for a change though and a software update is just the fix. Since I haven't kept up thoug, I really don't know how to go about it. I've been reading about the options but I don't know where my phone stands. Can I go the CM11-> CM12 route with Safestrap even though my bootloader is locked? Or do I need to use SunShine to unlock my bootloader and install a different custom recovery? And do I need to revert to stock to stock at any point? I'm pretty comfortable with all of this, I just need some nudging in the right direction.
Click to expand...
Click to collapse
If you NEVER took the 4.4.4 OTA you might want to consider unlocking your bootloader via "Sunshine" Then you can flash CM or anything you want with a real recovery and not safestrap. Just know that unlocking your bootloaer on a reatail device will void your warranty.
Travisdroidx2 said:
If you NEVER took the 4.4.4 OTA you might want to consider unlocking your bootloader via "Sunshine" Then you can flash CM or anything you want with a real recovery and not safestrap. Just know that unlocking your bootloaer on a reatail device will void your warranty.
Click to expand...
Click to collapse
Right, my phone has never seen 4.4.4. So I'm going to go ahead and use Sunshine to unlock my boot loader as the first step. The warranty I'm not too concerned about.
I guess the next question is how do I go about replacing safestrap with TWRP? Is it the same as installing TWRP from stock?
llsmith said:
Right, my phone has never seen 4.4.4. So I'm going to go ahead and use Sunshine to unlock my boot loader as the first step. The warranty I'm not too concerned about.
I guess the next question is how do I go about replacing safestrap with TWRP? Is it the same as installing TWRP from stock?
Click to expand...
Click to collapse
You should be familiar with flashing a custom recovery via adb if you have used TWRP on other devices. Once you have the bootloader unlocked you would need the correct recovery image of TWRP for the Moto X and then in bootloader mode use the command "fastboot flash recovery 'recovery.img'" where 'recovery.img' is the exact name of the file. If it flashed and it works properly then you could flash CM12 and Safestrap should be gone if you followed the flashing directions exactly. Don't forget to make a Nandroid of your current setup before you begin! Factory Resetting the device would be crucial if jumping from one ROM to another so it kind of takes care of itself.