Related
So I am planning on rooting my Verizon Moto Maker locked bootloader Moto X running 4.4 before the 4.4.2 OTA gets pushed and I want to safely stay rooted. Here is what I am planning on doing and please correct me if I am wrong or doing things unnecessarily:
1) Save my custom wallpaper using these instructions:
How to Pull Custom Wallpaper
2) Root using Slap My Moto method
- here it the 4.4 OTA if 4.4.2 has already come out by the time I do this
Verizon 4.4 OTA
3) Make an EFS b/u
4) Install Titanium b/u and make a post-root b/u
5) Use Titanium b/u to freeze MotorolaOTA so that the 4.4.2 OTA won't be pushed to my device
- will freezing MotorolaOTA stop the OTA from being downloaded or will it just stop the notification popup?
6) Uninstall Motorola Device Manager from my PC so that it won't try to upgrade my phone's OS every time I connect my phone to my PC
- is there any way to stop MDM from checking for updates without uninstalling it?
- will I lose the Motorola drivers for my Moto X if I uninstall MDM?
Also when am I supposed to wipe my dalvik cache wrt back ups and rooting? Am I supposed to clear any other cache or data anywhere along the way?
Then after I root, I can selectively flash the 4.4.2 update:
Slap My Moto Page 150
Important Warning Before Flashing 4.4.2 Page 15
System.img, boot.img, non-hlos.bin and fsg.mbn
Cozume said:
So I am planning on rooting my Verizon Moto Maker locked bootloader Moto X running 4.4 before the 4.4.2 OTA gets pushed and I want to safely stay rooted. Here is what I am planning on doing and please correct me if I am wrong or doing things unnecessarily:
1) Flash TWRP and boot into it to make a pre-root nandroid b/u
- I know the custom recovery won't stick when I reboot, just doing it to make a pre-root b/u
- is this necessary as long as the sbf firmware is available?
2) Root using Slap My Moto method
3) Make an EFS b/u
4) Install Titanium b/u and make a post-root b/u
5) Use Titanium b/u to freeze MotorolaOTA so that the OTA won't be pushed to my device
- will freezing MotorolaOTA stop the OTA from being downloaded or will it just stop the notification popup?
6) Uninstall Motorola Device Manager from my PC so that it won't try to upgrade my phone's OS every time I connect my phone to my PC
- is there any way to stop MDM from checking for updates without uninstalling it?
- will I lose the Motorola drivers for my Moto X if I uninstall MDM?
Also when am I supposed to wipe my dalvik cache wrt back ups and rooting? Am I supposed to clear any other cache or data anywhere along the way?
Also, I can't hit the thanks button anymore today but if you help me I will come back tomorrow and hit it, I promise!
Click to expand...
Click to collapse
Flashing twrp while having a locked boot loader? Idk
Sent on my Gummy running Lenoto X
flashallthetime said:
Flashing twrp while having a locked boot loader? Idk
Click to expand...
Click to collapse
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.
Cozume said:
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.
Click to expand...
Click to collapse
well good! you're on the right track. 3 best pieces of advice here:
1. Search first
2. Read alot (yes even some long threads with several pages)
3. Then Q & A is here for you.
Glad you're being safe with your exepnsive device, some noobs usually shoot first ask questions later.
Cozume said:
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.
Click to expand...
Click to collapse
Flashing a custom recovery always requires a unlocked boot loader, On a more serious note, I would wait for the Verizon ota to arrive and see how folks manage to root their phones, if its possible?
Sent on my Gummy running Lenoto X
flashallthetime said:
On a more serious note, I would wait for the Verizon ota to arrive and see how folks manage to root their phones, if its possible?
Click to expand...
Click to collapse
I want to do it now in case the exploit is closed forever in 4.4.2. Then if someone comes up with a new way to root 4.4.2, I can unroot, revert to stock and take the update then, right?
Cozume said:
I want to do it now in case the exploit is closed forever in 4.4.2. Then if someone comes up with a new way to root 4.4.2, I can unroot, revert to stock and take the update then, right?
Click to expand...
Click to collapse
No, wait and see what happens, it makes sense flash 4.4.2 now, it won't make any difference now or later, second point is, you can not flash the 4.4.2 sbf firmware as Verizon's version is not available why?,your boot loader is locked, you not flash any sbf with a locked. boot loader, you can ONLY flash your specific carriers sbf firmware. Read please. I have 6 months of moto x experience behind me, been here from day 1
Sent on my Gummy running Lenoto X
My advice. Root it now, wait it out. If they can't come up with an exploit for 4.4.2, sell your phone, get a developer edition then you can do whatever you want.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
SymbioticGenius said:
My advice. Root it now, wait it out. If they can't come up with an exploit for 4.4.2, sell your phone, get a developer edition then you can do whatever you want.
Click to expand...
Click to collapse
yeah, but it will cause me great sadness to sell my beautiful wood backed baby!!!
flashallthetime said:
it won't make any difference now or later
Click to expand...
Click to collapse
well, yes it would because if I take the OTA then I won't be rooted unless someone finds an exploit for 4.4.2 and I will never be rooted if someone doesn't.
flashallthetime said:
i
, second point is, you can not flash the 4.4.2 sbf firmware as Verizon's version is not available why?,your boot loader is locked, you not flash any sbf with a locked. boot loader, you can ONLY flash your specific carriers sbf firmware.
Click to expand...
Click to collapse
I am getting confused now. If I stay on 4.4 rooted and something happens to my device, can I or can't I flash the sbf for Verizon 4.4 with a locked bootloader to restore my device?
Maybe I wasn't clear but my plan is to root on 4.4 and stay there by freezing MotorolaOTA, which is the app that installs the updates and sends the annoying message. I was going to stay on 4.4 rooted and not upgrade to 4.4.2 unless someone can come up with a way to root it with a locked bootloader.
Cozume said:
yeah, that is my plan. But it will cause me great sadness to sell my beautiful wood backed baby!!!
Click to expand...
Click to collapse
Go for it root it now, I have no idea which sbf firmware you can flash that won't brick your device and I guess we'll see you back with the developer edition. Did you read my previous post? Is Verizon's or at&t 4.4.2 firmware available? Not last time I checked. Locked bootloaders can not flash any sbf firmware only your specific carriers sbf firmware can be flashed
Sent on my Gummy running Lenoto X
flashallthetime said:
Go for it root it now, I have no idea which sbf firmware you can flash that won't brick your device and I guess we'll see you back with the developer edition. Did you read my previous post? Is Verizon's or at&t 4.4.2 firmware available? Not last time I checked. Locked bootloaders can not flash any sbf firmware only your specific carriers sbf firmware can be flashed
Click to expand...
Click to collapse
Did you read my previous post:
My Previous Post
My plan is to NEVER flash 4.4.2 unless someone can root 4.4.2. Then I would unroot and take the OTA, not flash anything. Can't I unroot on 4.4 and take the OTA?
Cozume said:
Did you read my previous post:
My Previous Post
My plan is to NEVER flash 4.4.2 unless someone can root 4.4.2. Then I would unroot and take the OTA, not flash anything. Can't I unroot on 4.4 and take the OTA?
Click to expand...
Click to collapse
No one knows yet for sure what and will not work for the 4.4.2 ota, you'll just have to wait. Probably the only way is keep the 4.4 boot loader while running the 4.4.2 system only but its all speculation until the ota comes out
Sent on my Gummy running Lenoto X
flashallthetime said:
No one knows yet for sure what and will not work for the 4.4.2 ota, you'll just have to wait. Probably the only way is keep the 4.4 boot loader while running the 4.4.2 system only but its all speculation until the ota comes out
Click to expand...
Click to collapse
I am not planning on taking the 4.4.2 OTA. The whole point of freezing MotorolaOTA is to block the OTA.
So here is where I am at...
Initially I had a Moto X 4.4 on VZW. I downgraded to 4.2.2, ran RockMyMoto then ran MotoWPNoMo.
Rooted with Write Protection Off. Reflashed the Camera Update. Ran SlapMyMoto, took the 4.4 update and finished the 4.4 root steps.
I went like this for quite a while then decided to install SafeStrap and the 4.4.2 rooted rom.
Had issues and flashed back to 4.2.2 - this is where I am at now. If I run RockMyMoto I get
System is not write protected...
Executing step 3...
If I install SuperSu I get "binaries not installed."
I can confirm that Write Protection is off but I don't know if I am rooted.
What do I need to do to get back to 4.4 rooted with Write Protection off? If I run SlapMyMoto what OTA will I get... 4.4 or 4.4.2?
Please Help!
HTC-OH_SNAP said:
So here is where I am at...
Initially I had a Moto X 4.4 on VZW. I downgraded to 4.2.2, ran RockMyMoto then ran MotoWPNoMo.
Rooted with Write Protection Off. Reflashed the Camera Update. Ran SlapMyMoto, took the 4.4 update and finished the 4.4 root steps.
I went like this for quite a while then decided to install SafeStrap and the 4.4.2 rooted rom.
Had issues and flashed back to 4.2.2 - this is where I am at now. If I run RockMyMoto I get
System is not write protected...
Executing step 3...
If I install SuperSu I get "binaries not installed."
I can confirm that Write Protection is off but I don't know if I am rooted.
What do I need to do to get back to 4.4 rooted with Write Protection off? If I run SlapMyMoto what OTA will I get... 4.4 or 4.4.2?
Please Help!
Click to expand...
Click to collapse
Stop right there. If you ota to 4.4.2, very very good chance you will be bricked.
Its very common knowledge and there's posts in nearly every thread about this.
The advice most give is simple....don't downgrade from 4.4.2.... ever. Unless you have a few hundred bucks laying around for a new phone.
So, now you have already. So you need to tread extremely lightly. I would not alter a single thing now, until you do lots if research and figure out how, and if, you can get back to 4.4.2. Rooting would be my last concern at this point. Learning exactly what wrong moves can brick my phone would be my only priority.
I would help, but I am one who says never downgrade from 4.4.2. Period. So I've never researched the who process of downgrading against this advice. One thing is for sure DO NOT TAKE AN OTA.
There's a good chance you can get back to 4.4.2 somehow....but not by ota.... So chances are root and 4.4.2 will never happen now. In fact, you may be stuck exactly with what you have now.
Read up and see what choices you now have....before you do a thing.
Good luck!!!!
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
First step is to figure out if you ever had the 4.4.2 boot loader on your phone. If you did not....for sure....then you should still be safe.
kj2112 said:
Stop right there. If you ota to 4.4.2, very very good chance you will be bricked.
Its very common knowledge and there's posts in nearly every thread about this.
The advice most give is simple....don't downgrade from 4.4.2.... ever. Unless you have a few hundred bucks laying around for a new phone.
So, now you have already. So you need to tread extremely lightly. I would not alter a single thing now, until you do lots if research and figure out how, and if, you can get back to 4.4.2. Rooting would be my last concern at this point. Learning exactly what wrong moves can brick my phone would be my only priority.
I would help, but I am one who says never downgrade from 4.4.2. Period. So I've never researched the who process of downgrading against this advice. One thing is for sure DO NOT TAKE AN OTA.
There's a good chance you can get back to 4.4.2 somehow....but not by ota.... So chances are root and 4.4.2 will never happen now. In fact, you may be stuck exactly with what you have now.
Read up and see what choices you now have....before you do a thing.
Good luck!!!!
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
First step is to figure out if you ever had the 4.4.2 boot loader on your phone. If you did not....for sure....then you should still be safe.
Click to expand...
Click to collapse
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
HTC-OH_SNAP said:
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
Click to expand...
Click to collapse
I've always had an unlocked boot loader.....all I know about locked methods and whatnot I've read here.
So maybe try asking in the ROM thread if it updates boot loader?
You just want to be sure before anything else.
Don't want to see you or anyone with a brick.
kj2112 said:
I've always had an unlocked boot loader.....all I know about locked methods and whatnot I've read here.
So maybe try asking in the ROM thread if it updates boot loader?
You just want to be sure before anything else.
Don't want to see you or anyone with a brick.
Click to expand...
Click to collapse
The Safestrap process, and installing a proper safestrap rom does not update the phone's bootloader. I think it also doesn't touch the GPT.BIN.
I know you haven't had experience with Safestrap, so think of it as kind of a Host OS/Guest OS setup, or if it was a PC then kind of like a Virtual PC setup where you could have a PC running real Windows 7 on your C drive that you boot too, plus having Windows 8 in a virtual PC and the Virtual PC's image file being stored on your "D drive". Installing W8 in the virutal PC doesn't touch the W7 "host" os, or its boot partition, etc. (its not 100% exactly the same, but that is the best analogy I can come up with at the moment).
---------- Post added at 06:35 AM ---------- Previous post was at 06:02 AM ----------
HTC-OH_SNAP said:
Let me clarify something... I did not take the 4.4.2 OTA. I was on 4.4, installed safestrap and flashed the 4.4.2 rooted stock ROM. Does flashing in safestrap affect the boot loader? How can I determine which boot loader I have? I still have write protection off just no root.
Click to expand...
Click to collapse
re: safestrap affecting the bootloader, no, it does not. At least if you are using a ROM made for safestrap, and properly follow the process.
To determine the bootloader version, boot the phone to bootloader mode it should show the version number. I believe 30.B4 is 4.4.2 and 30.71 is 4.4 and 4.2.2 w/camera fix. As @kj2112 has mentioned, If the bootloader has been updated to 4.4.2, do NOT attempt to downgrade. However when using safestrap properly, its different.
As for the error at step 3... apparently it is common for those who had once used MotoWpNoMo to disable write protection, then trying to run though the SlapMyMoto process.
The actual process for getting a working Safestrap setup is the same for all Moto X's, however the Safestrap roms, and possibly the installer, are model specific... So, for example, if you have a Verizon X with locked bootloader, you could still follow [GUIDE] Republic Wireless Moto X KitKat 4.4.2 Root, Safestrap, TWRP, and MotoWpNoMo but using the Verizon specific SBFs, SafeStrap and Safestrap Roms instead of the ones for T-Mobile and RW linked in that thread (like on steps 1b, 3a, 5a, 6b).
Because of that, I'll point you to -> http://forum.xda-developers.com/showpost.php?p=52401229&postcount=30 as it is the quickest link I can find to a work around for slapmymoto if you've already disabled write protection with MotoWpNoMo.
I'm sure if you took the time to read every post in the SlapMyMoto thread or the entire MotoWpNoMo thread you will likely find discussions about your situation and a fix. For example: Post 349 through 357 of the MotoWpNoMo thread is a user having the same issue, but later says it was due to the SlapMyMoto file being the older 0.5c version rather than 1.0.
I'm sorry, I'm just not good with RockMyMoto/SlapMyMoto/MotoWpNoMo/etc and Safestrap as I have an unlocked bootloader, so I never had to mess with them to root and disable write protection.
how do i spf back to 4.2.2?
coolguy71261 said:
how do i spf back to 4.2.2?
Click to expand...
Click to collapse
This is someone's thread with their particular issue. If we start helping you in this thread with your issue....that is called thread hijacking.
You need to ask in a thread relevant to your issue, or start a new thread.
However.....since we don't know anything about your situation or your issue.....advice is hard to give.
You can probably start here tho.... http://forum.xda-developers.com/showthread.php?t=2603358
If that doesn't help, you need to make your own thread. And be as specific as possible with the details. But only start a thread if searching comes up with nothing and no existing threads match your issue.
Just some XDA etiquette.
Good luck.
And sorry to OP for off topic.
If you rooted with rockmymoto and took write protection off. You'll still have it so the only process you'll need to do is slapmymoto on 4.4. Safestrap will work with 4.2.2 and 4.4. If you want root stay there don't go to 4.4.2
MOTO X
KidJoe said:
Great Advice
Click to expand...
Click to collapse
Ok... so here is how the whole thing ended.
Checked my Bootloader - it was still 30.71.
Verified I still had Write Protection off.
Ran SlapMyMoto 1.0.
Took the OTA (From 4.2.2 it is still 4.4 and NOT 4.4.2)
Ran the ADB Shell Commands.
Installed SuperSu from the Play Market, and...
Rooted 4.4 with Write Protection Off.
Thanks!
Broke phone sending it back to moto.. Trying to install the update but it fails .. Thinking because of root so going to try the factory reset and see if that will unroot and let 4.4.2 install
doitinthedirt said:
Broke phone sending it back to moto.. Trying to install the update but it fails .. Thinking because of root so going to try the factory reset and see if that will unroot and let 4.4.2 install
Click to expand...
Click to collapse
If you used SlapMyMoto you should already know that it is not compatible with 4.4.2 - did you even read the relevant threads? Most likely you have modified something in /system OR you have custom recovery installed. Both of these issues are well documented here and will prevent you from accepting ANY OTA update.
A factory reset probably won't help, but if you follow the instructions in the "Return to Stock" thread (and flash the ENTIRE stock SBF for YOUR carrier) it will probably fix you right up.
It is irresponsible to flash things without knowing the consequences and then 'send it back to moto'. This results in higher prices for all of us, and encourages the OEMs to lock the devices down TIGHT.
samwathegreat said:
If you used SlapMyMoto you should already know that it is not compatible with 4.4.2 - did you even read the relevant threads? Most likely you have modified something in /system OR you have custom recovery installed. Both of these issues are well documented here and will prevent you from accepting ANY OTA update.
A factory reset probably won't help, but if you follow the instructions in the "Return to Stock" thread (and flash the ENTIRE stock SBF for YOUR carrier) it will probably fix you right up.
It is irresponsible to flash things without knowing the consequences and then 'send it back to moto'. This results in higher prices for all of us, and encourages the OEMs to lock the devices down TIGHT.
Click to expand...
Click to collapse
Thanks for the info.. but give the ben of doubt. the phone was dropped by my brother and the glass is broke. the phone works fine. and is currently working perfect on 4.4 rooted with slapmymoto and wipemymoto
I have the replacement phone here now and it came with 4.4.2 and I want to experiment with the old broke one before sending it back. I want to know what I can do and cannot do with 4.4.2 using Pie root and Towelroot, but try on the broke phone first, that's why I need to change from a good working 4.4 root to 4.4.2
Peace
doitinthedirt said:
Thanks for the info.. but give the ben of doubt. the phone was dropped by my brother and the glass is broke. the phone works fine. and is currently working perfect on 4.4 rooted with slapmymoto and wipemymoto
What I have the replacement phone here now and it came with 4.4.2 and I want to experiment with the old broke one before sending it back. I want to know what I can do and cannot do with 4.4.2 using Pie root and Towelroot, but try on the broke phone first
Peace Saw
Click to expand...
Click to collapse
Ok, that makes more sense I guess.
Yes if you want to experiment, download the entire 4.4.2 SBF for Verizon (that is your carrier, right?)
It is this one: http://sbf.droid-developers.org/download.php?device=0&file=841
Follow the instructions in the Return to Stock thread. Everything you need is there - all the tools, binaries, and drivers.
Once you have flashed the SBF, you will be on STOCK 4.4.2 and you can experiment all you want!
Good Luck
samwathegreat said:
Ok, that makes more sense I guess.
Yes if you want to experiment, download the entire 4.4.2 SBF for Verizon (that is your carrier, right?)
It is this one: http://sbf.droid-developers.org/download.php?device=0&file=841
Follow the instructions in the Return to Stock thread. Everything you need is there - all the tools, binaries, and drivers.
Once you have flashed the SBF, you will be on STOCK 4.4.2 and you can experiment all you want!
Good Luck
Click to expand...
Click to collapse
I've downloaded the ota and its on the phone now, can i flash this
doitinthedirt said:
I've downloaded the ota and its on the phone now, can i flash this
Click to expand...
Click to collapse
Nope. Not unless you have STOCK recovery, and an unmodified /system - which it appears you do not.
Just follow my previous instructions and flash the entire stock SBF (NOT the OTA). This will fix you right up in about 4 minutes...
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.