So I have the TMo X that I rooted using the RMM exploit. Worked perfectly, but it seems the exploit is permanent. I have used Moto Toolbox, RSD Lite to get back to stock and with both ways I em up still having system RW privilidges. Not that I am complaining but is that normal? I was even able to root the official kitkat after the OTA just by installing supersu.
Do you have a Dev edition?
Sent from my XT1060 using Tapatalk
No the regular Tmo edition.
Related
I have a VZW moto X with locked bootloader , currently rooted using MotoRoot (jcase's first root option)
I know that motoroot and pwnmymoto will not work post-OTA upgrade.
I currently only use root for TiBu to backup a few things and disable the system stuff that i do not use.
My question is: Will the OTA (when it comes) kill all of those disables if i remove root?
Is there any way to keep motoroot or pwnmymoto through the OTA with OTA rootkeeper?
There's a thread here in q and a that is a tutorial on how to keep root and update.
Sent from my XT1058 using XDA Premium 4 mobile app
My Moto X is rooted, but other than that, it's pretty much stock. I'm aware of how to flash back to stock using RSD Lite and Jcase's new root method, but my question is: Do I have to do all of that?
Can't I simply use Voodoo OTA Rootkeeper to temp unroot and then take the 4.4 OTA? I am not running a custom recovery.
Has anyone tried this?
greyhulk said:
My Moto X is rooted, but other than that, it's pretty much stock. I'm aware of how to flash back to stock using RSD Lite and Jcase's new root method, but my question is: Do I have to do all of that?
Can't I simply use Voodoo OTA Rootkeeper to temp unroot and then take the 4.4 OTA? I am not running a custom recovery.
Has anyone tried this?
Click to expand...
Click to collapse
Try and guarantee it will result in bootloops, obviously you are using one of jcases root methods which hijacks the stock recovery
Unfortunately there is no easy way around it afraik.
Just rsdlite back to stock, except the ota and root with jcases new slapmymoto.
Sent on my Moto X
flashallthetime said:
Try and guarantee it will result in bootloops, obviously you are using one of jcases root methods which hijacks the stock recovery
Unfortunately there is no easy way around it afraik.
Just rsdlite back to stock, except the ota and root with jcases new slapmymoto.
Sent on my Moto X
Click to expand...
Click to collapse
I forgot about the bootloader. I thought part of the root process was restoring it. What a shame. Thanks!
greyhulk said:
I forgot about the bootloader. I thought part of the root process was restoring it. What a shame. Thanks!
Click to expand...
Click to collapse
No easy way, no cutting corners either
Sent on my Moto X
I'm a VZW Galaxy Nexus user who took advantage of the Black Friday sale on the Moto X Developer Edition (for Verizon). I guess I've been spoiled by how easy it was to unlock, root, take OTA updates on my Galaxy Nexus and both the 2012 and 2013 Nexus 7 tablets. I've been researching the Moto X methods while I wait for the phones to arrive, and I'd like to see if my understanding is correct.
1. Because I'll have a DE (Developer Edition) version, rather than a MM (MotoMaker) version, bootloader unlocking should be easy. I get the code from Motorola and follow the instructions on the Motorola website. Right?
2. For the same reason as above, rooting should be as easy as flashing custom recovery (Hashcode's TWRP 2.6.3.1 I think it is as I type this), then booting into that custom recovery and flashing the latest SuperSU. Right?
If yes to both above, then this is just as easy as it was on my Nexus devices.
What about taking OTA updates? On my Nexus phones and tablets, even with custom recovery and root I was able to take OTA updates (everything was basically stock). If I lost root (like I did when I updated to 4.4), I simply flashed SuperSU again from TWRP or CWM. Would this be any different on the moto x? I've seen posts where people with rooted moto x got stuck in boot loops after accepting the 4.4 update. Was that because they had a MM version and had to use PwnMyMoto or RockMyMoto or some similar exploit-method of gaining root? If I have the DE version, should I first flash stock recovery and unroot? Flashing stock recovery is simple, but how would I unroot the moto x if I had rooted it just by flashing SuperSU from TWRP?
Thanks in advance for the help.
GrillMouster said:
I'm a VZW Galaxy Nexus user who took advantage of the Black Friday sale on the Moto X Developer Edition (for Verizon). I guess I've been spoiled by how easy it was to unlock, root, take OTA updates on my Galaxy Nexus and both the 2012 and 2013 Nexus 7 tablets. I've been researching the Moto X methods while I wait for the phones to arrive, and I'd like to see if my understanding is correct.
1. Because I'll have a DE (Developer Edition) version, rather than a MM (MotoMaker) version, bootloader unlocking should be easy. I get the code from Motorola and follow the instructions on the Motorola website. Right?
2. For the same reason as above, rooting should be as easy as flashing custom recovery (Hashcode's TWRP 2.6.3.1 I think it is as I type this), then booting into that custom recovery and flashing the latest SuperSU. Right?
If yes to both above, then this is just as easy as it was on my Nexus devices.
What about taking OTA updates? On my Nexus phones and tablets, even with custom recovery and root I was able to take OTA updates (everything was basically stock). If I lost root (like I did when I updated to 4.4), I simply flashed SuperSU again from TWRP or CWM. Would this be any different on the moto x? I've seen posts where people with rooted moto x got stuck in boot loops after accepting the 4.4 update. Was that because they had a MM version and had to use PwnMyMoto or RockMyMoto or some similar exploit-method of gaining root? If I have the DE version, should I first flash stock recovery and unroot? Flashing stock recovery is simple, but how would I unroot the moto x if I had rooted it just by flashing SuperSU from TWRP?
Thanks in advance for the help.
Click to expand...
Click to collapse
Yes to both questions. But no, you cant take OTAs with a custom recovery.
The problems only happened when people tried to root devices that didn't have an unlockable bootloader (ATT, Verizon). Other models are fine.
You need to have the stock recovery, and all stock files. The 4.4 OTA kills root anyway. So you just have to flash TWRP again afterwards and root with SSU.
GoClifGo05 said:
That's not true. I have VZW developer edition, unlocked the booloader the day I got and I received the Camera OTA and 4.4 OTA with no issues.
You need to have the stock recovery, and all stock files. The 4.4 OTA kills root anyway. So you just have to flash TWRP again afterwards and root with SSU.
Click to expand...
Click to collapse
With TWRP? That's new. I know it works on stock recovery, but he asked about a custom one. I'll edit my post though...i can see how it sounds wrong.
No not with TWRP sorry.... It seemed as if you meant unlocking the bl blocked the ota alone. My bad.
Sent from my Moto X DE
GoClifGo05 said:
No not with TWRP sorry.... It seemed as if you meant unlocking the bl blocked the ota alone. My bad.
Sent from my Moto X DE
Click to expand...
Click to collapse
Yeah that's why I edited the post. I worded it wrong.
GoClifGo05 said:
You need to have the stock recovery, and all stock files.....
Click to expand...
Click to collapse
No problem. By "all stock files", I assume that I won't have a problem, since I haven't in the past. I haven't removed any stock apps, just disabled them (even VZW bloatware). I use stock ROM and just want root for Titanium Backup, Quickboot, tethering, maybe Greenify (but I don't think I'll use that on the moto x). Actually, I'm not sure about tethering, since the method I've seen for native tethering on the moto x involves replacing "VzwEntitlementService.apk" from the "/system/priv-app/" directory with a modified one. Would that cause an OTA to fail (assuming I had stock recovery)?
Yea just meant apps. If you can disable them from within settings then you're fine. If you modify anything in system or delete system apps via TiBu then the Ota will fail.
Sent from my Moto X DE
For some reason I can't find a sure answer or How-To on rooting 4.4.2 for my GSM DE on T-Mobile. Someone point me in the right direction. This 4.4.2 update popup is getting really annoying.
Sent from my XT1053 using Tapatalk
overthatscreen said:
For some reason I can't find a sure answer or How-To on rooting 4.4.2 for my GSM DE on T-Mobile. Someone point me in the right direction. This 4.4.2 update popup is getting really annoying.
Click to expand...
Click to collapse
Is your bootloader unlocked? If so I am sure it will only be a matter of time before someone updates the TWRP custom recovery for a Moto X on 4.4.2.
The only way to root 4.4.2 is off your phone's bootloader is unlocked or can be unlocked.
There is no root for locked bootloader
Here is the process for unlocked bootloader
Unlock your bootloader
Install custom recovery
Flash SuperSU flashable zip
And your done
Sent from my XT1056 using XDA Premium 4 mobile app
dray_jr said:
Install custom recovery
Click to expand...
Click to collapse
But can you use the version of TWRP that is for 4.4? Or has it been updated for 4.4.2? Don't the custom recoveries need to be updated for the new versions of the OS?
The same version of twrp works for 4.4 and 4.4.2.
So essentially the same steps that I performed for Rooting 4.4 applies to 4.4.2 ? I thought something would have changed, but I'll take your word for it.
And is it safe to assume my bootloader should stay unlocked since I already went through the root process with 4.4?
Sent from my XT1053 using Tapatalk
overthatscreen said:
So essentially the same steps that I performed for Rooting 4.4 applies to 4.4.2 ? I thought something would have changed, but I'll take your word for it.
And is it safe to assume my bootloader should stay unlocked since I already went through the root process with 4.4?
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Yes and Yes. I also have a GSM Dev Edition with an Unlocked Bootloader and the same root method worked and the bootloader remained unlocked.
overthatscreen said:
So essentially the same steps that I performed for Rooting 4.4 applies to 4.4.2 ?
Click to expand...
Click to collapse
It is always the same if your bootloader is unlocked in that you flash custom recovery and install a superuser. The only thing that would change is if the custom recovery changes for the new version of the OS or if the super user is updated.
I just outlined it all here:
How To Root Your Unlocked Moto X Running Kit Kat
overthatscreen said:
And is it safe to assume my bootloader should stay unlocked since I already went through the root process with 4.4?
Click to expand...
Click to collapse
Going through the root process has nothing to do with unlocking your bootloader. Once unlocked, your bootloader will stay unlocked until you relock it.
Sounds good. I'll just reflash back to stock and update then root.
Sent from my XT1053 using Tapatalk
Well I just got done flashing with the Moto X Restore Utility, updated to 4.4.2, flashed TWRP, and rooted.
Aw well. I was going to contribute that if you were annoyed by the 4.4.2 OTA constantly in your face: you can disable the MotorolaOTA system service.
I was on verizon galaxy nexus for over two years. I wanted better radio performance, so i got a moto x. Nexus bootloader was unlocked and I was a bit of a crackflasher.
I have unlocked bootloader on moto x and installed twrp and supersu.
I did all this before taking firmware update, so I can see how it runs on 4.2.2. I ran it awhile and wanted to try kk out. I downloaded the ota update and went to have it autoflash, but instead, it rebooted into twrp.
so, I have downloaded rsdlite (i used to have a droid x, so i am familiar) and will get the 4.4.2 firmware downloaded too.
Q: can i flash aosp 4.4.2 roms with my x in it's 4.2.2 state or do i need the 4.4.2 update first?
Q: are there standalone radio (baseband) files around I can download and flash in recovery?
Thx!
RSDLite when you have an unlocked bootloader?
Grab the 4.4.2 sbf, extract the individual imgs, then flash with fastboot.
You will find the moto x is no nexus I'm afraid. Not a flashaholics phone for sure. There's just a few ROMs....not a lot of mods, and whatever you do, once on 4.4.2....never downgrade. It can cost you your phone. Dev edition or not.
Just a heads up!!
BTW....not knocking it....I still recommend it to everyone I know!!! Except the couple rooting and tinkering types....then I recommend the N5 hands down.
update : upgraded to kk firmware with rsdlite. bootloader still unlocked. I am on Eclipse now and enjoying it.
Sent from my XT1060 using Tapatalk
kochoid said:
update : upgraded to kk firmware with rsdlite. bootloader still unlocked. I am on Eclipse now and enjoying it.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I moved from a galaxy nexus last fall to the X. I definitely flashed constantly... now with an unlocked bootloader (MotoMaker!) I don't have the need. Xposed is all you really need to get features you want, unless you just like to tinker.