Related
I just unlocked my bootloader via the "chinese" unlock code...How to I get back to 100% stock after having been rooted via SlapMyMoto?
As I understand, the slapmymoto method replaces the recovery. Can I just flash the stock recovery back over it? Should I SFB back to 4.2.2 post camera then OTA back to 4.4?
JJHunterx said:
I just unlocked my bootloader via the "chinese" unlock code...How to I get back to 100% stock after having been rooted via SlapMyMoto?
As I understand, the slapmymoto method replaces the recovery. Can I just flash the stock recovery back over it? Should I SFB back to 4.2.2 post camera then OTA back to 4.4?
Click to expand...
Click to collapse
Full restore to stock would be to SBF back to appropriate version.
To just flash a recovery, simply download one, move it to ADB folder then run
Code:
fastboot flash recovery nameofyourfile.zip
asuhoops8628 said:
Full restore to stock would be to SBF back to appropriate version.
To just flash a recovery, simply download one, move it to ADB folder then run
Code:
fastboot flash recovery nameofyourfile.zip
Click to expand...
Click to collapse
If I SBF back to 4.2.2 will that flash the stock recovery and allow me to OTA to 4.4 no problem?
JJHunterx said:
If I SBF back to 4.2.2 will that flash the stock recovery and allow me to OTA to 4.4 no problem?
Click to expand...
Click to collapse
Yes, if you use RSDLite to flash a SBF you are flashing the full stock rom, recovery, boot, etc.
If you want to be on stock 4.4, why not just use RSDLite to flash the 4.4. SBF?
KidJoe said:
Yes, if you use RSDLite to flash a SBF you are flashing the full stock rom, recovery, boot, etc.
If you want to be on stock 4.4, why not just use RSDLite to flash the 4.4. SBF?
Click to expand...
Click to collapse
For some reason, I didn't think 4.4 had a SBF...Found it. Thanks.
I am rooted 4.4 and got an unlock code.
Seems like the most straightforward method to get to fully rooted (with r/w) on 4.4.2 would be to SBF 4.4 to return to full stock. Take the OTA to 4.4.2, then unlock.
Is there a way to root without a custom recovery? I was under the impression that it was much more simple with an unlocked bootloader. The guides I've seen for installing TWRP are certainly much more simple than the SlapMyMoto process, but I thought it was as simple as just installing SuperSU or putting the APK in /system or something. I guess I was mistaken on that part.
Thanks!
fury683 said:
I am rooted 4.4 and got an unlock code.
Seems like the most straightforward method to get to fully rooted (with r/w) on 4.4.2 would be to SBF 4.4 to return to full stock. Take the OTA to 4.4.2, then unlock.
Is there a way to root without a custom recovery? I was under the impression that it was much more simple with an unlocked bootloader. The guides I've seen for installing TWRP are certainly much more simple than the SlapMyMoto process, but I thought it was as simple as just installing SuperSU or putting the APK in /system or something. I guess I was mistaken on that part.
Thanks!
Click to expand...
Click to collapse
You can unlock your BL regardless of what version of android you are on. I just wanted to get back to stock so slapmymoto was no longer active (which is kinda a workaround for root imho, but it works and does its job.)
To root with an unlocked bootloader, all you have to do is download the TWRP img file and the supersu.zip file. Push the supersu.zip to your SD card. Use fastboot to flash TWRP img file. Boot into the recovery you just flashed and install the supersu.zip file. Bam you're rooted.
fury683 said:
I am rooted 4.4 and got an unlock code.
Seems like the most straightforward method to get to fully rooted (with r/w) on 4.4.2 would be to SBF 4.4 to return to full stock. Take the OTA to 4.4.2, then unlock.
Is there a way to root without a custom recovery? I was under the impression that it was much more simple with an unlocked bootloader. The guides I've seen for installing TWRP are certainly much more simple than the SlapMyMoto process, but I thought it was as simple as just installing SuperSU or putting the APK in /system or something. I guess I was mistaken on that part.
Thanks!
Click to expand...
Click to collapse
Well, you can unlock your bootloader at any time once you have the unlock code. The Android version on your phone doesn't matter.
Flashing TWRP, booting to it and installing SuperSU is how you root with an unlocked bootloader. (for full details see -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 which makes it seem like a longer process than it is.) That process is as easy as it gets, and works no matter what ROM you are on.
If you want to be on 4.4.2, and going to use RSDLite to flash an SBF anyway, the most straight forward way would be to flash the 4.4.2 SBF, then Root by flashing TWRP, booting to it, and installing SuperSU.
KidJoe said:
Well, you can unlock your bootloader at any time once you have the unlock code. The Android version on your phone doesn't matter.
Flashing TWRP, booting to it and installing SuperSU is how you root with an unlocked bootloader. (for full details see -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 which makes it seem like a longer process than it is.) That process is as easy as it gets, and works no matter what ROM you are on.
If you want to be on 4.4.2, and going to use RSDLite to flash an SBF anyway, the most straight forward way would be to flash the 4.4.2 SBF, then Root by flashing TWRP, booting to it, and installing SuperSU.
Click to expand...
Click to collapse
Thanks. Can I SBF with 4.4.2 even thought I'm still on 4.4? Or do I need to do 4.4 SBF, OTA to 4.4.2 then unlock and do TWRP/root?
Thanks again.
fury683 said:
Thanks. Can I SBF with 4.4.2 even thought I'm still on 4.4? Or do I need to do 4.4 SBF, OTA to 4.4.2 then unlock and do TWRP/root?
Thanks again.
Click to expand...
Click to collapse
No matter what rom is on your phone right now, if you have the bootloader unlock code, you can unlock. You don't have to be on a special version to unlock your phone's bootloader once you have the code.
The OTA's are incremental updates. They require pre-requisites be in place or they fail. You must be on a specific previous ROM, and "step up." They check for specific files/version/check sums to be on your phone before they install. If your phone doesn't match the version the OTA is looking for, or a particular file on your phone doesn't match what the OTA is looking for, the OTA will fail. To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
SBF's are complete roms containing every file/partition/modem for that version. You can flash the 4.4.2 SBF directly over any other ROM version. It wont stop you.
Just remember when flashing an SBF, there is a line in the XML that RSDLite uses that controls whether it wipes your data or not when flashing. (The thread about returning to stock using RSDlite explains it.) BUT since the process of unlocking your bootloader will factory reset your phone which wipes the data anyway...RSDLite erasing your data isn't a problem if you do it right before or right after you unlock your bootloader.
KidJoe said:
No matter what rom is on your phone right now, if you have the bootloader unlock code, you can unlock. You don't have to be on a special version to unlock your phone's bootloader once you have the code.
The OTA's are incremental updates. They require pre-requisites be in place or they fail. You must be on a specific previous ROM, and "step up." They check for specific files/version/check sums to be on your phone before they install. If your phone doesn't match the version the OTA is looking for, or a particular file on your phone doesn't match what the OTA is looking for, the OTA will fail. To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
SBF's are complete roms containing every file/partition/modem for that version. You can flash the 4.4.2 SBF directly over any other ROM version. It wont stop you.
Just remember when flashing an SBF, there is a line in the XML that RSDLite uses that controls whether it wipes your data or not when flashing. (The thread about returning to stock using RSDlite explains it.) BUT since the process of unlocking your bootloader will factory reset your phone which wipes the data anyway...RSDLite erasing your data isn't a problem if you do it right before or right after you unlock your bootloader.
Click to expand...
Click to collapse
After unlocking though, flashing the system.img from an SBF file and a custom recovery brings you basically back to "stock" (excluding the custom recovery) so you don't have to use RSDLite, correct?
EvanVanVan said:
After unlocking though, flashing the system.img from an SBF file and a custom recovery brings you basically back to "stock" (excluding the custom recovery) so you don't have to use RSDLite, correct?
Click to expand...
Click to collapse
For the most part, you can use mfastboot to flash just system.img and recovery.img, this will get those two parts back to stock, which is often enough to allow you to take an OTA update, however, if you've touched any other part, your phone wont be 100% stock. And then, how long does it take for the OTA to install and reboot? Now, in fury683's case, the phone is on 4.4 and he wants to go to 4.4.2. But if the phone was on say either of the 4.2.2 versions and he wanted to go to 4.4.2, then you'd also have multiple OTA's to install.
Using the full SBF and RSDlite will flash all parts, gets you to 100% stock, and immediately on the version you want. I don't know everything that SlapMyMoto and MotoWpNoMo touch, so I can't say for sure if flashing system and recovery are enough to totally remove them, or just remove enough to allow you to take an OTA.
System.img takes the longest to flash via either mFastboot or RSDLite, the rest are really quick, so the time spent using RSDLite to flash everything isn't that much more than manually flashing just system.img and recovery.img via mfastboot.
So considering that the mfastboot oem unlock does a factory reset anyway (so data is going to be lost), and flashing with RSDlite flashes all parts as 1 batched operation (i.e. you don't have to individually execute mfastboot lines...) using RSDLite can get you to the final destination, and ensure 100% stock, more easily.
I did mine last night from 4.4. I unlocked, got a clean 4.4 , took ota, flash twrp, install su. If you do in the right order shouldn't take more than 30 mins to be up and running again. If you use Titanium backup be sure to pull your files to computer before doing the bootloader unlock.
KidJoe said:
No matter what rom is on your phone right now, if you have the bootloader unlock code, you can unlock. You don't have to be on a special version to unlock your phone's bootloader once you have the code.
The OTA's are incremental updates. They require pre-requisites be in place or they fail. You must be on a specific previous ROM, and "step up." They check for specific files/version/check sums to be on your phone before they install. If your phone doesn't match the version the OTA is looking for, or a particular file on your phone doesn't match what the OTA is looking for, the OTA will fail. To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
SBF's are complete roms containing every file/partition/modem for that version. You can flash the 4.4.2 SBF directly over any other ROM version. It wont stop you.
Just remember when flashing an SBF, there is a line in the XML that RSDLite uses that controls whether it wipes your data or not when flashing. (The thread about returning to stock using RSDlite explains it.) BUT since the process of unlocking your bootloader will factory reset your phone which wipes the data anyway...RSDLite erasing your data isn't a problem if you do it right before or right after you unlock your bootloader.
Click to expand...
Click to collapse
Thanks for your help. The process was much less painful than I expected. Aside from downloading the SBF file, whole process to SBF, unlock, flash TWRP and root took about 20 minutes.
Working great now!
Thanks again
Ok, hope I don't get too much heat over this, my old device was a Samsung with unlocked bootloader, so everything was easily flashed.
Anyway, as to the best order of things, I'm still on AT&T 4.2.2 pre camera update, so I easily rooted with with pwnmymoto. I have Xposed installed with a few modules.
For the unlock steps -looks like this is the best guide: http://forum.xda-developers.com/showpost.php?p=51363645&postcount=394 and using: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-c
Q: Is my recovery from pwnmymoto "stock" as it needs to be for unlocking process?
Can I just uncheck/disable the modules I have with xposed, or do I need to delete the framework? (which sounds like the only way is to use RSD to install the original ROM?)
Should I also unfreeze any files? (I think I only froze the one's related to motorola OTA)
My intent is to get to 4.4.2, and I know it's optimal to remove things from pwnmymoto (I know unlocking will wipe everything but my ROM), so probably after I've installed TWRP and rooted, to flash the file for AT&T 4.4.2 http://forum.xda-developers.com/moto-x/general/-t2688009 or does it need to be incremental, as I'm on 4.2 (i.e flash 4.2 camera update, then 4.4, etc.) -sorry if I seem a bit confused
Thanks in advance! any and all help is very much appreciated!
Hopefully not too many questions -if any has the best suggestion for any, would be great
M973 said:
Hopefully not too many questions -if any has the best suggestion for any, would be great
Click to expand...
Click to collapse
Just to be clear if you eant 4.4.2 stock use the xposed framework disabler, it said leaving the modules was ok according to the link you posted. I don't know personally.
But honestly if your unlocking the bootloader then just go to 4.4.2 first then unlock since you'll lose everything. I believe bootloader unlock wipes the system parition too. I don't know for sure.
drago10029 said:
Just to be clear if you eant 4.4.2 stock use the xposed framework disabler, it said leaving the modules was ok according to the link you posted. I don't know personally.
But honestly if your unlocking the bootloader then just go to 4.4.2 first then unlock since you'll lose everything. I believe bootloader unlock wipes the system parition too. I don't know for sure.
Click to expand...
Click to collapse
I think 4.4.2 isn't fully released yet OTA for AT&T, so it would be flashing to stock and taking each OTA in sequence to 4.4 I think? I believe the framework disabler is a zip that needs to be flashed, so that would only be after I have a custom recovery.
I just don't want to mess up anything, want to make sure I have the right recovery for unlocking, and that I've disabled anything that could cause an issue.
Edit: from the pwnmymoto thread, Jcase writes: "In the process we remove stock recovery, so OTAs will not be a worry."
I guess that means i don't have stock recovery?
Edit: I was thinking I needed stock recovery, I guess I just need fastboot which is what I have?
I just want to make sure, if anyone has unlocked from pwnmymoto
Thanks
M973 said:
I think 4.4.2 isn't fully released yet OTA for AT&T, so it would be flashing to stock and taking each OTA in sequence to 4.4 I think? I believe the framework disabler is a zip that needs to be flashed, so that would only be after I have a custom recovery.
I just don't want to mess up anything, want to make sure I have the right recovery for unlocking, and that I've disabled anything that could cause an issue.
Edit: from the pwnmymoto thread, Jcase writes: "In the process we remove stock recovery, so OTAs will not be a worry."
I guess that means i don't have stock recovery?
Edit: I was thinking I needed stock recovery, I guess I just need fastboot which is what I have?
I just want to make sure, if anyone has unlocked from pwnmymoto
Thanks
Click to expand...
Click to collapse
np problem bro, happy rooting! may the flash be ever in your favor
Title pretty much sums it all. I've an XT1058 with unlocked bootloader running stock rooted Kitkat 4.4. I want to update to stock 4.4.2 to try and use the new screen mirroring feature with my Chromecast (AFAIK, I need to be at least on 4.4.1, right?). Is there a way not to lose the unlocked bootloader and/or the root when I flash the update?
Similar question: Do I have to go back to stock (i.e., unrooted, locked) before I flash 4.4.2, or can I flash it over my current stock ROM?
Thank you all in advance.
Deivid85 said:
Title pretty much sums it all. I've an XT1058 with unlocked bootloader running stock rooted Kitkat 4.4. I want to update to stock 4.4.2 to try and use the new screen mirroring feature with my Chromecast (AFAIK, I need to be at least on 4.4.1, right?). Is there a way not to lose the unlocked bootloader and/or the root when I flash the update?
Similar question: Do I have to go back to stock (i.e., unrooted, locked) before I flash 4.4.2, or can I flash it over my current stock ROM?
Thank you all in advance.
Click to expand...
Click to collapse
If you have unlocked the bootloader, there is no fear of "losing" it. Bootloader unlocking is permanent, so even if root is lost, you can simply re-flash TWRP and re-root. Disclaimer: I'm sure you do know the difference between unlocking the bootloader (permanent), and using one of the write-protect-disable exploits (like MotoWpNoMo - which is NOT permanent and would be lost if upgraded to 4.4.2), but I wanted to point this out just in case. If you are indeed bootloader-unlocked, you will have a "WARNING BOOTLOADER UNLOCKED" screen appear upon boot. Again, I apologize if this is redundant...
If you want to take the OTA to 4.4.2, you would need to flash back stock recovery, un-do any mods you have made to /system, and disable Xposed (if installed). This could be complicated if you aren't sure what mods you may or may not have made...
There is no 4.4.1 for the Moto X - we skipped straight from 4.4 to 4.4.2. I'm not sure which version was the first to support Chromecast, however.
It would be easiest to "go back to stock" rather than trying to figure out how to un-do any modifications you may or may not have made. Additionally, it is preferable to flash the entire stock 4.4.2 SBF (which will erase ALL of your data - backup anything you need first), rather than trying to retain the userdata and just flash /system. Issues can arise if you try to retain your userdata.
My advice (for what its worth) is to follow the instructions in the Return to Stock thread to flash the ENTIRE STOCK 4.4.2 SBF for YOUR carrier. This will return you to 100% stock with no root. You WILL retain your unlocked bootloader so afterwards, you can simply flash TWRP, and re-root your phone.
By going this route, you minimize any potential problems that might arise by trying to take the OTA, or by flashing the SBF without erasing userdata.
If you have any questions or need clarification, let me know.
Good Luck
samwathegreat said:
If you have unlocked the bootloader, there is no fear of "losing" it. Bootloader unlocking is permanent, so even if root is lost, you can simply re-flash TWRP and re-root. Disclaimer: I'm sure you do know the difference between unlocking the bootloader (permanent), and using one of the write-protect-disable exploits (like MotoWpNoMo - which is NOT permanent and would be lost if upgraded to 4.4.2), but I wanted to point this out just in case. If you are indeed bootloader-unlocked, you will have a "WARNING BOOTLOADER UNLOCKED" screen appear upon boot. Again, I apologize if this is redundant...
If you want to take the OTA to 4.4.2, you would need to flash back stock recovery, un-do any mods you have made to /system, and disable Xposed (if installed). This could be complicated if you aren't sure what mods you may or may not have made...
There is no 4.4.1 for the Moto X - we skipped straight from 4.4 to 4.4.2. I'm not sure which version was the first to support Chromecast, however.
It would be easiest to "go back to stock" rather than trying to figure out how to un-do any modifications you may or may not have made. Additionally, it is preferable to flash the entire stock 4.4.2 SBF (which will erase ALL of your data - backup anything you need first), rather than trying to retain the userdata and just flash /system. Issues can arise if you try to retain your userdata.
My advice (for what its worth) is to follow the instructions in the Return to Stock thread to flash the ENTIRE STOCK 4.4.2 SBF for YOUR carrier. This will return you to 100% stock with no root. You WILL retain your unlocked bootloader so afterwards, you can simply flash TWRP, and re-root your phone.
By going this route, you minimize any potential problems that might arise by trying to take the OTA, or by flashing the SBF without erasing userdata.
If you have any questions or need clarification, let me know.
Good Luck
Click to expand...
Click to collapse
Thank you very much for the thorough and detalied reply! I'll follow your advice and report back.
Also, as a follow up question (actually, more like checking I got your reply right): Given that I do have the bootloader permanently unlocked, all I need to root 4.4.2 is flashing back TWRP and hit the root option? (I know you said exactly that, but I got lost after reading al the PIE tethered root threads, so just wanted to make sure that is for locked bootloaders, and not my case).
Thanks again!
Deivid85 said:
Thank you very much for the thorough and detalied reply! I'll follow your advice and report back.
Also, as a follow up question (actually, more like checking I got your reply right): Given that I do have the bootloader permanently unlocked, all I need to root 4.4.2 is flashing back TWRP and hit the root option? (I know you said exactly that, but I got lost after reading al the PIE tethered root threads, so just wanted to make sure that is for locked bootloaders, and not my case).
Thanks again!
Click to expand...
Click to collapse
You are correct. Nothing in the PIE thread is relevant to us with unlocked bootloaders.
Worked like a charm!
I actually in the same situations as the OP, EXCEPT my bootloader is locked and I used a couple of jcase's methods to get my root, so no TWRP. Would the same instructions still apply? What would be the best way to backup things?
NameLessThugZero said:
I actually in the same situations as the OP, EXCEPT my bootloader is locked and I used a couple of jcase's methods to get my root, so no TWRP. Would the same instructions still apply? What would be the best way to backup things?
Click to expand...
Click to collapse
Actually, nothing about your situation is similar to the OPs since you don't have unlocked bootloader....or do you mean the situation is similar in that you want to be able to use chromecast?
Regardless, nothing in this thread is relevant to you. The 4.4.2 bootloader is impervious to any known write-protect-disable exploits, so if you DO update to 4.4.2 you will PERMANENTLY lose write-protect. The only option once on 4.4.2+ is to use tethered root such as PIE, which does not disable write protect, does not allow writing to /system, and any and all changes are lost upon reboot. You must then re-connect to PC, and re-run the exploit to gain root again.....not very pretty....
The ONLY option for you (besides bootloader unlock) if you want to retain write-protect-disable and persistent Root, is to follow the advice in this thread: http://forum.xda-developers.com/moto-x/moto-x-qa/upgrade-4-4-root-t2822191
And heed the warnings!!! One simple / innocent mistake will result in either a brick, or PERMANENT loss of write-protect-disable. Take extreme caution.
Good Luck
samwathegreat said:
Actually, nothing about your situation is similar to the OPs since you don't have unlocked bootloader....or do you mean the situation is similar in that you want to be able to use chromecast?
Regardless, nothing in this thread is relevant to you. The 4.4.2 bootloader is impervious to any known write-protect-disable exploits, so if you DO update to 4.4.2 you will PERMANENTLY lose write-protect. The only option once on 4.4.2+ is to use tethered root such as PIE, which does not disable write protect, does not allow writing to /system, and any and all changes are lost upon reboot. You must then re-connect to PC, and re-run the exploit to gain root again.....not very pretty....
The ONLY option for you (besides bootloader unlock) if you want to retain write-protect-disable and persistent Root, is to follow the advice in this thread: http://forum.xda-developers.com/moto-x/moto-x-qa/upgrade-4-4-root-t2822191
And heed the warnings!!! One simple / innocent mistake will result in either a brick, or PERMANENT loss of write-protect-disable. Take extreme caution.
Good Luck
Click to expand...
Click to collapse
I guess I was trying to be too concise, sorry. I know I dont want to go the safestrap route because of time and complexity, nor do I want to do anything with chromecast(which I forgot was mentioned, my bad). I did however plan to use PIE as soon as I heard about it. The route I was simply going to take was just to flash stock 4.4.2 SBF, then apply PIE( which I know isnt permanent after a hard reboot) since I knew that would be to safest way to get root without screwing up stuff. That said, cant this method work just as well? And sure I have to worry about getting SuperUser Xposed up and running again, which I believe has been posted about already, in the comments. But i think that would be all unless Im missing something else.
NameLessThugZero said:
I guess I was trying to be too concise, sorry. I know I dont want to go the safestrap route because of time and complexity, nor do I want to do anything with chromecast(which I forgot was mentioned, my bad). I did however plan to use PIE as soon as I heard about it. The route I was simply going to take was just to flash stock 4.4.2 SBF, then apply PIE( which I know isnt permanent after a hard reboot) since I knew that would be to safest way to get root without screwing up stuff. That said, cant this method work just as well? And sure I have to worry about getting SuperUser Xposed up and running again, which I believe has been posted about already, in the comments. But i think that would be all unless Im missing something else.
Click to expand...
Click to collapse
Sure! If you don't mind losing write-protect-disable forever, and having to re-root each time you reboot, go for it! I highly suggest you follow the instructions in the "Return to Stock" thread (in general sub-forum) to flash the entire 4.4.2 SBF for YOUR carrier. This will give you bone-stock 4.4.2, and will erase everything. Back up anything important first. Then you can follow the instructions in the PIE thread.
The suggested method is highlighted in red in your post above. You CANNOT use the method listed in THIS thread, because you cannot flash custom recovery unless you have unlocked bootloader.
I -think- PIE will work with Titanium Backup (confirm that first), so you can probably back-up anything that you can't just re-install from the play store and restore it afterwards. Copy everything you want to keep from the internal storage (pictures, etc.), because they will be erased as well.
That's pretty much it. I don't think you've missed anything, but keep in mind that bootloader unlock (and the 4.4 exploits) are both far superior to PIE as far as usability and persistence. You'll have to try and reboot as seldom as possible.
Good Luck!!! :good:
EDIT: Keep in mind also that once you update to 4.4.4, PIE will NOT WORK, and you will LOSE ROOT FOREVER (unless another exploit is released, which is unlikely at best).
samwathegreat said:
Sure! If you don't mind losing write-protect-disable forever, and having to re-root each time you reboot, go for it! I highly suggest you follow the instructions in the "Return to Stock" thread (in general sub-forum) to flash the entire 4.4.2 SBF for YOUR carrier. This will give you bone-stock 4.4.2, and will erase everything. Back up anything important first. Then you can follow the instructions in the PIE thread.
The suggested method is highlighted in red in your post above. You CANNOT use the method listed in THIS thread, because you cannot flash custom recovery unless you have unlocked bootloader.
I -think- PIE will work with Titanium Backup (confirm that first), so you can probably back-up anything that you can't just re-install from the play store and restore it afterwards. Copy everything you want to keep from the internal storage (pictures, etc.), because they will be erased as well.
That's pretty much it. I don't think you've missed anything, but keep in mind that bootloader unlock (and the 4.4 exploits) are both far superior to PIE as far as usability and persistence. You'll have to try and reboot as seldom as possible.
Good Luck!!! :good:
EDIT: Keep in mind also that once you update to 4.4.4, PIE will NOT WORK, and you will LOSE ROOT FOREVER (unless another exploit is released, which is unlikely at best).
Click to expand...
Click to collapse
Sweet, thanks for your help. Ill check on the TB thing. Ill update if I need any other help.
NameLessThugZero said:
I guess I was trying to be too concise, sorry. I know I dont want to go the safestrap route because of time and complexity, nor do I want to do anything with chromecast(which I forgot was mentioned, my bad). I did however plan to use PIE as soon as I heard about it. The route I was simply going to take was just to flash stock 4.4.2 SBF, then apply PIE( which I know isnt permanent after a hard reboot) since I knew that would be to safest way to get root without screwing up stuff. That said, cant this method work just as well? And sure I have to worry about getting SuperUser Xposed up and running again, which I believe has been posted about already, in the comments. But i think that would be all unless Im missing something else.
Click to expand...
Click to collapse
Keep in mind, that PIE itself isn't as good of root as using SlapMyMoto & MotoWpNoMo together.
On the X there are two parts needed for effective Root. 1. Root Exploit, and 2. Write Protection Dis-abler.
PIE is a root Exploit. It exploits a vulnerability to grant root access. It does not address Write Protection.
Write Protection on the X prevents proper access to /system or the like. Some apps wont be able to create new files in the protected folders, and any changes made to existing files (including, but not limited to, App installs, file modifications, deletions, renames, etc) are not permanent and are lost at power off/on. This is also why PIE root is lost at power off/on.
In the past (4.4 and below days) SlapMyMoto was the Root Exploit, and MotoWpNoMo was the write protection dis-abler. Once thought to be permanent, the exploit used by MotoWpNoMo was plugged in 4.4.2 making it not work. Write protection becomes re-enabled, and there is no new exploit to disable it.
Why do I mention this? In reading the various threads, especially the Pie thread, there appear to be special instructions to install XPosed when write protection is enabled that you'll need to keep in mind, as well as info on how to re-root and get Xposed working again if you do power off/on. Because write protection is enabled, there are some apps and hacks that may not work. Some of the Tethering tricks for example.
Unlocking the bootloader gets around this. Once you unlock the bootloader, you can always install a custom recovery (like TWRP) and root from there. In the process, write protection becomes disabled. There is no need to wait on a vulnerability in the code to be exploited to gain root and disable write protection.
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 have a Republic Wireless Moto x (XT1049) with an unlocked bootloader, and knowing how rare it is (literally 0 support on any thread/site/country), I'm still going to ask a few questions, maybe start a band of RWers with unlocked Moto Xs that will only survive by sticking together/cuddling for warmth.
Before anyone starts to disbelieve me, I do have an xt1049 (not confusing it) with an unlocked bootloader (not confusing it with simply being rooted). I achieved this by purchasing a $25 license for SunShine by the jcase crew, and it worked wonderfully for whoever is out there, looking to unlock you xt1049. Why did I want to fork out 25 bucks for this? I started to hate the grind with towelpieroot+xposed every time I turned my device on, plus things like Viper4Android (among others) don't work well with temp roots, plus no write protection off, which has its purposes.
So on to my questions, (1) are there any custom ROMs designed for XT1049? (Probably no, so before you tell me no, (1a) are there any that work with my model?)
(2) If no one knows 1 or 1a, theoretically, what would happen if I flashed a ROM, say, CM 11/12, onto my phone? Please, to avoid a clutter of responses that consist of "idk probs no," have some level of confidence before answering.
For the theorists, Republic has a bunch of republic things going on in the background for the plural wifis to work correctly, how would these services (wifi calling/stuff) be affected, but also how would more universal things (moto x line specifically, but universal across carriers)? I don't know a whole lot about carriers because I have a serious phobia of letter combinations like CDMA and LTE, but to help understanding the "universal things" I mentioned, looking at the CM11 download page, one ZIP file can be used to flash the XT1053, XT1056, XT1058, XT1060, XT1055, you get the point. OK you got me, to refine it down,(3) I'm just trying to get a complete understanding of what would happen without trying it. I might/probably/would try it some other day, I have a load of college on my plate so if I have to undo anything (another question: (4) would I be able to revert to republic stuff if I have the correct zip, or what would have to go wrong so that I wouldn't be able to get to my bootloader/recovery?) I don't pay my phone bill, and my pops would be pissed if he read this so that's why I might not want to test it, but if there is a way to return I will be ballsy anyway.
(5) A question that I've had for a while but I never needed it answered, bootloaders remain unlocked after an update, right? My old phone (RIP HTC design 4g ) lost support at 4.2 and I never updated it the entire time it was rooted/unlocked. My moto on the other hand has 4.4.4 coming out soon and yeah I don't know the answer to it. I think it's implied it stays unlocked, but no one ever says it directly...
Well, thanks if you made it this far! And I would link whatever I could but I am a new user to this site and I'm restricted, you can just look up Sunshine jcase if interested.
Hi, this is my first time posting on xda, so I apologize ahead of time if I don't do it correctly. I'm also very interested in what can be done with a Republic Wireless Moto X (2013) in order to update to 4.4.4 and still be able to use TowelPieRoot and Xposed. I also looked at the SunShine unlocker but have not tried it yet. I'm currently on 4.4.2 and I just go the update notification today for 4.4.4 (much later than my wife's phone, which does not have TowelPieRoot or Xposed). Just wondering if you had any success with updating and still remaining unlocked and able to use TowelPieRoot and Xposed. Thanks for any feedback!
Unlocked boot loader...
Today I unlocked the boot loader on my Republic Wireless XT1049, since they were trying to force me to upgrade to android 4.4.4 from 4.4.2, and I realized that running Sunshine on 4.4.2 would be my last opportunity for unlocking the boot loader, before upgrading. I haven't yet rooted or updated to 4.4.4. Have either of you upgraded to 4.4.4 android with an uplocked boot loader, and re-rooted? Is there anything different about root in 4.4.4 vs 4.4.2, if you have an unlocked boot loader? Would the "Rooting Unlocked Bootloader" instructions in this guide work in android 4.4.2 and/or 4.4.4? Or, would Sunshine SUInstaller make that unnecessary? (Hopefully SUInstaller would work in 4.4.4...)
I'm on 4.4.2 with an unlocked bootloader from when the china man was giving out unlock codes. Having my code guarantees that I can unlock my bootloader even after locking it again for an update. I'm not sure how Sunshine works but be careful before taking the 4.4.4. update and do lots of research before doing anything to your device.
To answer some questions:
CM11 and CM12 will flash fine. The problem you'll have is a loss of phone functionality. With Republic, their app is baked into their custom ROM. But you can use it like a tablet and get a feel for what lollipop will look like on our phone. Make sure you have a nandroid backup or you'll lose everything. CM11 requires a wipe before it will install and CM12 requires you have CM11 (at least it did the last I checked) so you'll want to make sure you have a backup so you can get your working RW ROM back. Otherwise you'll have to flash the Stock RW ROM and start from scratch.
I've done lots of digging and have been able to get the Republic app working on CM11 and CM12 but the functionality is still missing. My tweaks allow texts on CM11 but it's from the "hidden number" not the RW number and the formatting is messed up upon receiving a message. Calls don't work at all on either ROM.
I posted a thread in General with my instructions to get the app working. I'm hoping someone with more ROM knowledge than myself can take a look at the RW Stock ROM and see what else needs to be moved into a CM ROM to give us functionality. I tried moving everything over and skipping duplicates and now I've seriously messed my phone up and will likely have to relock, unlock, flash TWRP and hope I can restore from my TWRP backup.
I've only tried CM11 and CM12, I have no idea how another ROM will affect our phone. Chances are you'll end up in an endless boot after flashing. You could brick the phone though, or end up in a situation like I'm currently in.
bstevens23 said:
I'm on 4.4.2 with an unlocked bootloader from when the china man was giving out unlock codes. Having my code guarantees that I can unlock my bootloader even after locking it again for an update. I'm not sure how Sunshine works but be careful before taking the 4.4.4. update and do lots of research before doing anything to your device.
Click to expand...
Click to collapse
Thanks for the warning about upgrading. I still haven't decided to allow my phone to upgrade to 4.4.4 android, but the most immediate issue I face with not upgrading is that my phone automatically downloaded the update, and now it is incessantly prompting me to install it. I have found any way to stop the annoying prompting. I would rather wait before updating, because there are always details you don't know about such upgrades, and I have no pressing need for the upgrade, except that ultimately I would like to be able to root my phone, also allow for writing to the system partition, so that recording calls would be possible.
You raise a good point in mentioning your capability to lock and unlock the boot loader. As far as I know Sunshine only unlocks the boot loader. I haven't seen that it provides any code or other means for re-locking it. It is also my understanding that technically there are 3 possible locking states of the boot loader. The factory state not only being locked but also indicating that it was never unlocked. It's my understanding that once a boot loader is unlocked, it can be re-locked, but never restored to the factory locked state that indicates it was never unlocked. That said, I don't know whether it matters if the boot loader is unlocked when running the Republic Wireless upgrade. In other threads I had read claims that once a boot loader is unlocked, that it should remain unlocked after OS upgrades, and as such, in a state that would allow for rooting. But, I am far from an expert on that.
bstevens23 said:
To answer some questions:
CM11 and CM12 will flash fine. The problem you'll have is a loss of phone functionality. With Republic, their app is baked into their custom ROM. But you can use it like a tablet and get a feel for what lollipop will look like on our phone. Make sure you have a nandroid backup or you'll lose everything. CM11 requires a wipe before it will install and CM12 requires you have CM11 (at least it did the last I checked) so you'll want to make sure you have a backup so you can get your working RW ROM back. Otherwise you'll have to flash the Stock RW ROM and start from scratch.
I've done lots of digging and have been able to get the Republic app working on CM11 and CM12 but the functionality is still missing. My tweaks allow texts on CM11 but it's from the "hidden number" not the RW number and the formatting is messed up upon receiving a message. Calls don't work at all on either ROM.
I posted a thread in General with my instructions to get the app working. I'm hoping someone with more ROM knowledge than myself can take a look at the RW Stock ROM and see what else needs to be moved into a CM ROM to give us functionality. I tried moving everything over and skipping duplicates and now I've seriously messed my phone up and will likely have to relock, unlock, flash TWRP and hope I can restore from my TWRP backup.
I've only tried CM11 and CM12, I have no idea how another ROM will affect our phone. Chances are you'll end up in an endless boot after flashing. You could brick the phone though, or end up in a situation like I'm currently in.
Click to expand...
Click to collapse
I hope there will be others who are willing to collaborate in your endeavors to reverse engineer the ROM that you are working on. Are you pursuing that because nobody has been able to root a Republic Wireless XT1049 on android 4.4.2 with a ROM? It seems that the original poster found some way to root 4.4.2 with his unlocked boot loader. I would be interest to know how he did that.
gxdaspark said:
Thanks for the warning about upgrading. I still haven't decided to allow my phone to upgrade to 4.4.4 android, but the most immediate issue I face with not upgrading is that my phone automatically downloaded the update, and now it is incessantly prompting me to install it. I have found any way to stop the annoying prompting. I would rather wait before updating, because there are always details you don't know about such upgrades, and I have no pressing need for the upgrade, except that ultimately I would like to be able to root my phone, also allow for writing to the system partition, so that recording calls would be possible.
You raise a good point in mentioning your capability to lock and unlock the boot loader. As far as I know Sunshine only unlocks the boot loader. I haven't seen that it provides any code or other means for re-locking it. It is also my understanding that technically there are 3 possible locking states of the boot loader. The factory state not only being locked but also indicating that it was never unlocked. It's my understanding that once a boot loader is unlocked, it can be re-locked, but never restored to the factory locked state that indicates it was never unlocked. That said, I don't know whether it matters if the boot loader is unlocked when running the Republic Wireless upgrade. In other threads I had read claims that once a boot loader is unlocked, that it should remain unlocked after OS upgrades, and as such, in a state that would allow for rooting. But, I am far from an expert on that.
Click to expand...
Click to collapse
I have yet to update to 4.4.4 because I've heard of people having problems with Messenger after the update. I'm waiting to see how my wife's phone functions on it before I make the leap and get the stock recovery back to take the OTA. Until then, I get the obnoxious update warning constantly as well. I could probably freeze the app with Titanium, we'll see if it bothers me enough in the next few days. I'm not sure if the bootloader will need to change for the update as I've only ever had 4.4.2 since I was bootloader unlocked. I know flashing the stock recovery is needed and I feel like that may require a relocked bootloader. As far as I know, from a software/OTA side at least, relocked and locked are equal. Republic/Moto would care about relocked but I don't think the system throws any flags for taking stock software updates because of it.
I hope there will be others who are willing to collaborate in your endeavors to reverse engineer the ROM that you are working on. Are you pursuing that because nobody has been able to root a Republic Wireless XT1049 on android 4.4.2 with a ROM? It seems that the original poster found some way to root 4.4.2 with his unlocked boot loader. I would be interest to know how he did that.
Click to expand...
Click to collapse
I'm pursuing this because I want CM12 to test out Lollipop since I have no idea when Republic is going to push it out to us. I haven't heard of Sprint getting soak tests yet and we're typically 2-3 months behind Sprint. Waiting until May when Google I/O takes place will be difficult for me, especially if they break their current trend and announce the next version of Android.
My goal is much more ambitious than just CM12 though. I got the Republic app to recognize CM11 as native, meaning if someone can figure out which radio portions I'm missing and get the phone functioning as if it were the Republic ROM, we would not be restricted to just the stock ROM/software anymore. I've been an Android user for a few years now and I've always had the ability to flash whatever I wanted if it was available for my device. Since joining RW, I'm extremely restricted. I have 1 ROM option, which is only helpful because it allows Xposed. But I no longer have the ability to test the newest version of Android whenever I please, or to give a custom ROM a spin if I feel like it. If we can figure out what makes the RW ROM function properly, that wouldn't be a restriction anymore. That's my goal.
Unfortunately, I have no idea what I'm doing. The best I can do is compare files and try pulling random things. I'm hoping someone with more ROM knowledge will be able to take a look at the RW ROM and see which pieces I'm missing. I feel like CM12 is going to be a bit more complicated though, and might not be possible at this time. We'll see though. I know something is getting screwed up with the MEID because the Republic app doesn't recognize an MEID at all. How to go about fixing that? Beyond me.
step-by-step, 4.4.4 root
I think the steps would be: first Sunshine, then 4.4.4 OTA, then root, then Xposed. Is that correct? After I unlock with Sunshine, will my phone still prompt me to update to 4.4.4? Or do I need to need to download 4.4.4 and then flash it? After Sunshine, do I FIRST need to flash 4.4.2 custom recovery? If so, where can I get that? I should probably get a copy of that anyway, even if I don't need it now.
It seems pretty easy overall, but I think I need to refer to a step-by-step guide to make sure I do all of this correctly. If I start the guide below, can you please be so kind as to make corrections for me? Add, remove, or change steps? Thanks!!! Here it goes, this is my best guess at the steps I need to take:
1. Go to theroot.ninja and complete the unlock process.
2. Download and install Android SDK on PC (installer_r24.1.2-windows.exe).
3. Download and install Motorola Device Manager on PC.
4. Get mfastboot.exe and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
***Do I just drag this .exe to the said folder on my PC?***
5. Get the TWRP for Moto X 4.4 custom recovery for kit kat and place it in the same directory as fastboot.
6. Enable USB debugging and download SuperSU
7. Double check to make sure USB debugging has been enabled. Put your unlocked Moto X into bootloader mode by pressing the Volume Down button and then the Power button. Hold for about 3 seconds and release and you should be in bootloader mode. Connect your Moto X to your PC via a USB cable.
8. Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
9. At the command prompt type: mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img to flash the custom recovery to your Moto X.
***Is this the version of TWRP I need to root 4.4.2? What about 4.4.4? Or do I just flash the 4.4.4 OTA on top of 4.4.2?***
10. After the custom recovery has been flashed to your Moto X, at the command prompt type: fastboot reboot-bootloader to reboot into the bootloader.
11. Unplug your device from your PC. Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and pressing the Volume Up button to select the recovery mode.
12. You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
*** I also saw this:
"For new users who have only unlocked their bootloaders, flashed TWRP and rooted, then only make use of apps like RootExplorer, QuickBoot(reboot), Adfree, Wifi Tether for Root, etc.. that do NOT modify /System, the easiest way to take the OTA is to...
download the SBF/FXZ for your carrier and the Software Version currently on your phone. Do NOT use a lower Software Version, or the SBF/FXZ for another carrier or you will risk bricking your phone!!!
unzip it.
boot the phone into fastbootAP/bootloader mode
use mfastboot to flash the recovery.img to your phone - mfastboot flash recovery recovery.img
immediately reboot into fastbootAP/bootloader - mfastboot reboot-bootloader
select recovery.
once you've entered stock recovery, you can reboot back into normal system.
take the OTA when it gets to your phone.
you will likely remain rooted, and its optional to flash your custom recovery back on there via mFastboot
However, if you are running Xposed, did a wifi tethering hack, edited build.prop, DELETED bloat from your phone, your phone will fail the OTA Update's validation checks and it will fail. In that case, you can boot back into fasbootAP/Bootloader mode, use mfastboot to flash system.img (mfastboot flash system.img ) from the SBF/FXZ you already downloaded and unzipped. then reboot ( mfastboot reboot ), and try the OTA again. You will need to re-root by flashing custom recovery (like twrp), and re-install SuperSU."
***Is there any way to break down the whole thing into simpler steps???*** THANKS!!!
PackerDroid said:
I think the steps would be: first Sunshine, then 4.4.4 OTA, then root, then Xposed. Is that correct? After I unlock with Sunshine, will my phone still prompt me to update to 4.4.4? Or do I need to need to download 4.4.4 and then flash it? After Sunshine, do I FIRST need to flash 4.4.2 custom recovery? If so, where can I get that? I should probably get a copy of that anyway, even if I don't need it now.
It seems pretty easy overall, but I think I need to refer to a step-by-step guide to make sure I do all of this correctly. If I start the guide below, can you please be so kind as to make corrections for me? Add, remove, or change steps? Thanks!!! Here it goes, this is my best guess at the steps I need to take:
1. Go to theroot.ninja and complete the unlock process.
2. Download and install Android SDK on PC (installer_r24.1.2-windows.exe).
3. Download and install Motorola Device Manager on PC.
4. Get mfastboot.exe and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
***Do I just drag this .exe to the said folder on my PC?***
5. Get the TWRP for Moto X 4.4 custom recovery for kit kat and place it in the same directory as fastboot.
6. Enable USB debugging and download SuperSU
7. Double check to make sure USB debugging has been enabled. Put your unlocked Moto X into bootloader mode by pressing the Volume Down button and then the Power button. Hold for about 3 seconds and release and you should be in bootloader mode. Connect your Moto X to your PC via a USB cable.
8. Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
9. At the command prompt type: mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img to flash the custom recovery to your Moto X.
***Is this the version of TWRP I need to root 4.4.2? What about 4.4.4? Or do I just flash the 4.4.4 OTA on top of 4.4.2?***
10. After the custom recovery has been flashed to your Moto X, at the command prompt type: fastboot reboot-bootloader to reboot into the bootloader.
11. Unplug your device from your PC. Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and pressing the Volume Up button to select the recovery mode.
12. You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
*** I also saw this:
"For new users who have only unlocked their bootloaders, flashed TWRP and rooted, then only make use of apps like RootExplorer, QuickBoot(reboot), Adfree, Wifi Tether for Root, etc.. that do NOT modify /System, the easiest way to take the OTA is to...
download the SBF/FXZ for your carrier and the Software Version currently on your phone. Do NOT use a lower Software Version, or the SBF/FXZ for another carrier or you will risk bricking your phone!!!
unzip it.
boot the phone into fastbootAP/bootloader mode
use mfastboot to flash the recovery.img to your phone - mfastboot flash recovery recovery.img
immediately reboot into fastbootAP/bootloader - mfastboot reboot-bootloader
select recovery.
once you've entered stock recovery, you can reboot back into normal system.
take the OTA when it gets to your phone.
you will likely remain rooted, and its optional to flash your custom recovery back on there via mFastboot
However, if you are running Xposed, did a wifi tethering hack, edited build.prop, DELETED bloat from your phone, your phone will fail the OTA Update's validation checks and it will fail. In that case, you can boot back into fasbootAP/Bootloader mode, use mfastboot to flash system.img (mfastboot flash system.img ) from the SBF/FXZ you already downloaded and unzipped. then reboot ( mfastboot reboot ), and try the OTA again. You will need to re-root by flashing custom recovery (like twrp), and re-install SuperSU."
***Is there any way to break down the whole thing into simpler steps???*** THANKS!!!
Click to expand...
Click to collapse
Were you able to break this down into simpler steps? Did the steps work for you?