I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
ejason said:
I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
Click to expand...
Click to collapse
PwnMyMoto and jcase's methods are for locked bootloaders. You first need to unlock your bootloader. Then you need to decide if you want to take the OTA to 4.4 or not because once you upgrade to 4.2.2 post-camera, you can never downgrade to 4.2.2 pre-camera without bricking your device.
If you want to upgrade to 4.4, here are the instructions to unlock and gain root:
[STEP-BY-STEP INSTRUCTIONS] Unlocking and Rooting a Dev Ed Moto X Running Kit Kat
I have read of others who kept the 4.2.2 bootloader and other partitions and just selectively flashed those partitions they wanted as each new upgrade's sbf firmware was released. I don't know what advantages there are to doing that.
ejason said:
I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
Click to expand...
Click to collapse
It's a Developer Edition. Take all the updates available (4.2.2 camera update, 4.4 and now 4.4.2). Get the unlock code from Motorola and unlock your bootloader. Once that is done, flash twrp recovery and then install root via twrp.
Very simple on Dev Editions just because you can unlock the bootloader and flash an alternate recovery (twrp, cwm, etc..).
I agree. Unlock your bootloader (Doesn't void warranty on Developer Edition), flash TWRP recovery, then boot to TWRP and install/flash SuperSU. And it doesn't matter what ROM version you're running. (there is a TWRP for 4.2.2 and one for 4.4/4.4.2).
As mentioned, the bootloader included in the android versions can prevent you from downgrading the rom version. (i.e. bootloader in 4.4.2 prevents you from downgrading to any previous ROM). Why would you want to downgrade? If you have a locked bootloader, you'd want to downgrade to be able to use the root processes needed when you have a locked bootloader. But if you have an unlocked bootloader, because you can flash an alternate recovery (not possible with locked bootloader) and root no matter what ROM version you have installed, the only reason to downgrade would be if you encounter a bug you can't deal with that isn't present in the older roms.
because 4.4.2 fixes the exchange and bluetooth issues, and doesn't introduce anything new, its suggested you update to 4.4.2 if you have an unlocked boot loader (4.4.2 isn't rootable on locked bootloaders and may not be, so its recommended that those with locked bootloaders who want to root stick with 4.4).
KidJoe said:
I agree. Unlock your bootloader (Doesn't void warranty on Developer Edition), flash TWRP recovery, then boot to TWRP and install/flash SuperSU. And it doesn't matter what ROM version you're running. (there is a TWRP for 4.2.2 and one for 4.4/4.4.2).
I didn't know there was a different TWRP for 4.2.2.
As mentioned, the bootloader included in the android versions can prevent you from downgrading the rom version. (i.e. bootloader in 4.4.2 prevents you from downgrading to any previous ROM). Why would you want to downgrade? If you have a locked bootloader, you'd want to downgrade to be able to use the root processes needed when you have a locked bootloader. But if you have an unlocked bootloader, because you can flash an alternate recovery (not possible with locked bootloader) and root no matter what ROM version you have installed, the only reason to downgrade would be if you encounter a bug you can't deal with that isn't present in the older roms.
because 4.4.2 fixes the exchange and bluetooth issues, and doesn't introduce anything new, its suggested you update to 4.4.2 if you have an unlocked boot loader (4.4.2 isn't rootable on locked bootloaders and may not be, so its recommended that those with locked bootloaders who want to root stick with 4.4).
Click to expand...
Click to collapse
From what i have read 4.4.2 isn't rootable at all. Even if you have an unlocked bootloader. Is that correct?
Great info, thanks.
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
I did something like that for an HTC ONE i have on straight talk. I unlocked the bootloader from the HTC website, then installed TWRP, and then rooted and its running a 4.4.2 ROM that is great.
ejason said:
From what i have read 4.4.2 isn't rootable at all. Even if you have an unlocked bootloader. Is that correct?
Click to expand...
Click to collapse
Incorrect. You can do whatever you want with the DE, regardless of what version of Android you're on.
Sent from my Moto X
ejason said:
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
Click to expand...
Click to collapse
There are directions on a 1 page pamphlet that came with your VZW DE on how to unlock the bootloader.
Sent from my Dev Edition Moto X
ejason said:
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
Click to expand...
Click to collapse
It is all in that step-by-step link I gave you above.
Ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the TWRP.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and CD into that folder and still the same error.
Can i install the TWRP with goo manager?
ejason said:
Ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the TWRP.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and CD into that folder and still the same error.
Can i install the TWRP with goo manager?
Click to expand...
Click to collapse
did it finish flashing? mine says that when i flash a recovery also, but it flashes.
after you flash it dont reboot, just go into recovery (volume down to move the selection, volume up to execute)
then select reboot system, and it will ask if you want to root.
ejason said:
ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the twrp.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and cd into that folder and still the same error.
Can i install the twrp with goo manager?
Click to expand...
Click to collapse
ok, thanks for everyones hellp. Done and done..
Related
I haven't don it yet getting all the info I need before hand.
1) After I unlock the bootloader will I be able to flash the most recent update for 4.4.4 or will I just be able to unfreeze the OTA and still keep root?
2) If I loose root since I now have an unlocked bootloader I'm just a SuperSU flash away from root, right?
3) Since I'm still on 4.4.2 will I have any issues if I need to flash back to it?
Anything else I might have missed that is important either from mistakes or just general knowledge I missed would be appreciated. Thanks and Good Night everybody!
Icon000 said:
I haven't don it yet getting all the info I need before hand.
1) After I unlock the bootloader will I be able to flash the most recent update for 4.4.4 or will I just be able to unfreeze the OTA and still keep root?
Click to expand...
Click to collapse
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
2) If I loose root since I now have an unlocked bootloader I'm just a SuperSU flash away from root, right?
Click to expand...
Click to collapse
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
3) Since I'm still on 4.4.2 will I have any issues if I need to flash back to it?
Click to expand...
Click to collapse
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
tcrews said:
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
Click to expand...
Click to collapse
Great explanation! :good:
tcrews said:
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
Click to expand...
Click to collapse
Why do you recommend flashing 4.4.4 over accepting the OTA? I still want to be able to use the additions originally provided by Motorola. I didn't seen a rom built on Moto Stock. Did I miss it?
Flash the stock 4.4.4 ROM that is for your device.
What's better...4.4.2 with patches to make it 4.4.4 (via an OTA) or just the full 4.4.4 (via the full 4.4.4 install) without the need for patching to make it 4.4.4?
Oh well...it looks like there isn't a FULL 4.4.4 for AT&T Moto X released yet....just 4.4.2. Flash the full 4.4.2 then take the OTA update to 4.4.4 and then flash TWRP to get root.
AT&T 4.4.2
http://sbf.droid-developers.org/download.php?device=0&file=849
You can just flash the system.img from the download with mfastboot to revert any changes you did (root, etc..) so that the OTA can be installed successfully. You'll just want to get fully updated before flashing an alternative recovery like TWRP.
Can we update phone's software via ota even after unlocking the boot loader and installing custom recovery
Nooooooooooooooooo
No, Not even in your dreams,
From what I've learned from my own Issue
http://forum.xda-developers.com/moto-x/moto-x-qa/totally-screwed-updating-rooted-x-4-4-4-t2896292
Never update phone's software via ota, while you are on Custom Recovery.
Patel21 is correct, you can't with a custom recovery.
You need stock recovery to take the OTA, then you can reinstall a custom recovery
m.ryuu said:
Can we update phone's software via ota even after unlocking the boot loader and installing custom recovery
Click to expand...
Click to collapse
Yes you can as long as you flash back to stock recovery before accepting the OTA. Once done, flash custom recovery and root if lost.
m.ryuu said:
Can we update phone's software via ota even after unlocking the boot loader and installing custom recovery
Click to expand...
Click to collapse
OTA will not install when you have a custom recovery on your phone. Instead you'll be stuck in a bootloop if you have tried to install an OTA with a custom recovery.
Rather than my retyping everything... Please see -> http://mark.cdmaforums.com/MotoX-OTA.html
I've flashed ota updates via custom recovery, you just have to know what you're doing. Also, the Moto boot loader won't relock as far as I know after an update. It doesn't on the Dev edition, not sure about unlocked retail or devices that have been unlocked with sunshine.
Sent from my Moto X
Since all unlocked devices are the same as the dev edition....the same would be true.
KJ said:
Since all unlocked devices are the same as the dev edition....the same would be true.
Click to expand...
Click to collapse
The only thing I want sure of was sunshine. If you unlocked via a code, then yes, all of them act the same.
Sent from my Moto X
imnuts said:
I've flashed ota updates via custom recovery, you just have to know what you're doing. Also, the Moto boot loader won't relock as far as I know after an update. It doesn't on the Dev edition, not sure about unlocked retail or devices that have been unlocked with sunshine.
Sent from my Moto X
Click to expand...
Click to collapse
I don't completely understand how Sunshine works, so I can't say for sure, however based on reading the thread, my understanding is it wont relock.
But if you unlock via mfastboot oem unlock {YourUniqueCode} your bootloader will not relock itself. This holds true for developer and non-developer alike.
Someone pls post a Link to stock recovery
m.ryuu said:
Someone pls post a Link to stock recovery
Click to expand...
Click to collapse
It's in the sbf for your phone/carrier/version.
4.4.4 version Asia retail not there
m.ryuu said:
4.4.4 version Asia retail not there
Click to expand...
Click to collapse
Have you checked -> http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25 too?
Is it possible to get custom roms on xperia play r800i locked boot loader. Running gin2kat android 2.3.7.
I have the 2013 model of the MotoX and its XT1058 version. I am currently on KitKat 4.4.2 and it's rooted. I was wondering if I will lose root if I take the OTA update to 4.4.4 and if that is so, is there a way to keep the root on 4.4.4. Thanks!
I second this. Same situation as you (Verizon model) and would like to go 4.4.4 and keep my root.
popcornmeat said:
I have the 2013 model of the MotoX and its XT1058 version. I am currently on KitKat 4.4.2 and it's rooted. I was wondering if I will lose root if I take the OTA update to 4.4.4 and if that is so, is there a way to keep the root on 4.4.4. Thanks!
Click to expand...
Click to collapse
If your bootloader is unlocked, yes, you can keep root, though you will need to the reflash supersu.zip (or have twrp automagically do it). Otherwise, no. There is no root available for unlocked 4.4.4. If you don't have an unlocked bootloader, check out the Sunshine thread in the general section.
Is your X an ATT XT1058? If not, you should be able to unlock for free through Moto (there are a number of threads around on doing so). For you @EpicBlob, since you are using a Verizon XT1060, if it isn't the Dev Edition, Sunshine is your only option now and is $25 to use.
Kind of, if root is hidden via superSU you can take the ota & then use sunshine. But why risk it.
As I recall, you can keep root but you will loose write access to system. This means if you use root to modify anything, it wont stick after a reboot. I would advise against it unless you have an unlocked bootloader.
If you have a custom recovery, you need to flash your stock recovery first also. ?
Darth said:
If you have a custom recovery, you need to flash your stock recovery first also. ?
Click to expand...
Click to collapse
Where can I find the stock recovery for XT1052 running 4.4.4... tried alot couldnt find it......can u point me...???
JJHunterx said:
As I recall, you can keep root but you will loose write access to system. This means if you use root to modify anything, it wont stick after a reboot. I would advise against it unless you have an unlocked bootloader.
Click to expand...
Click to collapse
I have an AT&T XT1058 too, my but i had my BL unlocked through sunshine.
I am still on 4.4, but now that i have my BL unlocked, i want to update to 4.4.4. Why do you say that i can keep the root but i will loose write access to system?
Can't i restore it?
Minato04 said:
I have an AT&T XT1058 too, my but i had my BL unlocked through sunshine.
I am still on 4.4, but now that i have my BL unlocked, i want to update to 4.4.4. Why do you say that i can keep the root but i will loose write access to system?
Can't i restore it?
Click to expand...
Click to collapse
You didn't mention you had an unlocked bootloader.
If it were me, I would RSD back to stock 4.4, take the OTA's to 4.4.4, flash recovery, flash root. (Only if you have an unlocked bootloader of course. )
I would just find the 4.4.4 AT&T sbf/fxz and flash it manually instead of taking OTAs.
popcornmeat said:
I have the 2013 model of the MotoX and its XT1058 version. I am currently on KitKat 4.4.2 and it's rooted. I was wondering if I will lose root if I take the OTA update to 4.4.4 and if that is so, is there a way to keep the root on 4.4.4. Thanks!
Click to expand...
Click to collapse
EpicBlob said:
I second this. Same situation as you (Verizon model) and would like to go 4.4.4 and keep my root.
Click to expand...
Click to collapse
Sorry I'm joining late... But...
If your bootloader is LOCKED (Standard on the ATT XT1058, and Verizon XT1060), then do not upgrade to 4.4.4. You will lose Root. The vulnerabilities exploited by Pie and Towel have been patched in 4.4.4, and you will not be able to re-root.
However, If while on 4.4.2 or lower you have unlocked your bootloader by either using Sunshine, or purchasing an Unlock Code from the China Middle man when available (the only two options to unlock the bootloader on the ATT XT1058 and Verizon XT1060 non-developer edition), you will likely lose root taking the update, but can re-root after 4.4.4 is on your phone.
To take OTA, you need stock recovery on your phone, and to be as close to stock as possible (so the OTA's preflash validation check doesn't fail). After the OTA is installed, flash TWRP, reboot-bootloader and enter TWRP.
The other option is to download the 4.4.4 SBF from one of the sites listed in -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347 and flash your phone with it via RSDLite or mFastboot. After flashing, use mFastboot to flash TWRP recovery, reboot-bootloader, then enter TWRP.
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.
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.