Database Develop

OTA 139.15.1 keep root

All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?

First item, this is a question so it should belong in the question and answer threads! Secondly look here http://forum.xda-developers.com/showthread.php?t=2466191
Sent on my Moto X

Sorry, and thanks! I'll probably give this a shot, make that camera work a little better...

You can always install the SafeStrap ROM here. That's what I did.
http://forum.xda-developers.com/showthread.php?t=2484908
[Rom] [VZW] SafeStrap 139.12.57
Sent from my Moto X

The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.

dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X

mercado79 said:
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
Click to expand...
Click to collapse
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.

dymmeh said:
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
Click to expand...
Click to collapse
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X

mercado79 said:
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
Click to expand...
Click to collapse
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk

juancaperez2000 said:
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
That's what I thought too. Thanks.

MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191

will2live said:
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
Click to expand...
Click to collapse
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.

MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
mercado79 said:
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
Click to expand...
Click to collapse
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.

dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!

boardrx182 said:
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
Click to expand...
Click to collapse
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you

dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
dymmeh said:
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
Click to expand...
Click to collapse
That's awesome, didn't realize that would happen automatically. I completely expected that I'd have to complete the entire root process steps that were outlined in an earlier post if I wanted root. Thanks for the reply.

will2live said:
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
Click to expand...
Click to collapse
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.

jayboyyyy said:
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
Click to expand...
Click to collapse
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.

will2live said:
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
Click to expand...
Click to collapse
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.

jayboyyyy said:
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
Click to expand...
Click to collapse
Gotchya, makes total sense now what you are saying. I think there is just confusion at times when talking about root & OTA because of different ways to do it in a case like this device. Being a Moto guy for so long tho i'm use to all the BS they throw at us.....lol. That said that is why i posted the link I did. Imho it's a bad plan to update using the other method of installing pwnmymoto and not running it first before taking the OTA. Doing the process to protect root before updating is a much safer bet atm imo. Sure its a little more work but at the end of the day you dont have to be worried as much moving forward. Only concern I have still for doing it the longer way is if that process will work when they push out 4.3. It had alot of changes in it so lord only knows what will be up for keeping root. And really in my case its no concern but for all the folks with consumer version it is still a concern i think for the time being

[Q] Can I update? Confused by so many unclear posts.

Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks

Icon000 said:
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Click to expand...
Click to collapse
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(

I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
matt99017d said:
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse

Icon000 said:
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
Click to expand...
Click to collapse
the only rom out for SS that i am aware of is just a ported tmobile rom for vzw phones that has the update built in. Basically it is just the OTA stock rom running on SS. This is what I am using currently. Not sure if it flashable for ATT phones, but I'm sure there is some workaround there. Or maybe the OP on that thread can make a ATT one if you asked him. SS is stable as of now. Haven't had any new updates to it because no one is having any problems currently (at least with moto x devices).
For your question pertaining to options for taking the OTA. There are 4 methods now.
1. SS method described above
2. use the thread called something like "keep root through the OTA." It basically takes the ota without updating the BL so you can still downgrade to your stock original FW that you are on now. It's the same thing as the SS method because SS also does not udpate the BL, but you won't be using SS for this method obviously.
3. you can flash recovery.img (and system.img if you need to) or just RSD, then install pwnmymoto without running it, then take the ota and pwnmymoto will root the phone automatically after the ota is taken. you won't be able to downgrade your FW anymore with this method.
4. you can just take the ota (also must flash or use rsd to take it obviously) and then use jcase's rockmymoto root exploit. This uses adb commands and telnet stuff. Not too difficult but if you are unfamiliar with all of that then it will take at least some reading. There is also a thread out there for windows users that simplifies it pretty well.
For future Kit kat root. it is still up in the air what will happen with that. I chose to use SS because it was easy. quick. and allows me to make nandroids. I also like knowing that I can still flash to original stock FW in case that might be necessarry for getting root on kit kat. This seems less likely now that jcase created a root method for the OTA that is out, but I'm still just playing it safe personally, even if it might be pointless now.

[Q] Safestrap 4.4 or use JCase to root???

I am about to get a Moto X from Verizon and I know it has a locked bootloader
I never dealt with a locked phone in the past and this will be my first moto so I am doing a lot of reading
Correct me if I'm wrong, but I guess the phone will come with 4.2 on it so I'll have two options:
1) Use safestrap and flash 4.4 as a second rom. I am guessing the disadvantage will be loss of disk space for the second rom (maybe other disadvantages, I don't know) but I'll be able to do nandroid backups and flash zips
2) Use the JCase method to root using SlapMyMoto and MotoWpNoMo, etc. (I'll be rooted, but no flashing roms or zips, or nandroid backups)
In that case, which method do you guys really recommend? Do I really need custom roms on this phone since it is almost stock and I can still get xposed to do a lot of the things I'd be interested in with just the root?
If I use the JCase method, do I lose the ability to use safestrap in the future?
Thanks

The moto xs leaving moto maker for Verizon should all be 4.4 at this point. Can't whole heartedly speak to your other questions though.
Sent from my SCH-I925 using Tapatalk

I used to be a flash-o-holic and so far I'm perfectly satisfied with just having root and xposed
sent from my Moto X

I'm rooted, using xposed and gravity box. Very happy with phone. Came from an s3 and have to say I don't miss flashing Roms. Real learning curve for me to root but JCase methods worked perfect and google was my friend through the many steps. Good luck!
Sent from my XT1060 using Tapatalk

SlapMyMoto. You're not gonna want to flash roms on this phone.

Thanks for the replies.
I guess if the phone comes with 4.4 already, I only have the JCase's root option, anyway.
But reading the replies here as well as other threads, I see that most people are pretty content with the stock rom + root + gravitybox/xposed. That's great to know.
I can't wait to get the phone tomorrow

Does Safestrap load 4.4.2 roms now?

aptalca said:
Thanks for the replies.
I guess if the phone comes with 4.4 already, I only have the JCase's root option, anyway.
But reading the replies here as well as other threads, I see that most people are pretty content with the stock rom + root + gravitybox/xposed. That's great to know.
I can't wait to get the phone tomorrow
Click to expand...
Click to collapse
Safestrap works on 4.4 too

But you have to have satestrapped it when you were on the 4.2 bootloader, correct? So if you took an ota or if your phone shipped with 4.4, your bootloader was updated and you can no longer safestrap

Is this for real?

I was just Google searching hoping for some good news... And came across this posted yesterday...
http://www.youmobile.org/blogs/entry/Root-Moto-X-KitKat
... Any truth to that? And is it for any carrier, i.e att?
Sent from my XT1058 using Tapatalk

Links to a thread on here.

Yea I saw that, but they are not the same...
Sent from my XT1058 using Tapatalk

They want you to dl this http://www.cydiaimpactor.com/
Anyone know what it is?

Maybe it works for root....but write protection will be enabled. So all root changes will be lost on reboot or power down.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

kj2112 said:
Maybe it works for root....but write protection will be enabled. So all root changes will be lost on reboot or power down.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
So here's my "dumb" question? Would apps like Greenify and Ti backup still possibly work since they just need root permissions, where as Xposed and other apps that need a reboot would be basically worthless?

jbaumert said:
So here's my "dumb" question? Would apps like Greenify and Ti backup still possibly work since they just need root permissions, where as Xposed and other apps that need a reboot would be basically worthless?
Click to expand...
Click to collapse
There's other threads where this stuff gets talked about, but im pretty sure for things like that it would probably work. But any actual changes to anything would get reversed.
I've always been unlocked....so I don't have firsthand experience though.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

I'm not too sure about that root method.
Step 11 tells you to downgrade the Bootloader (MOTOBOOT.IMG) and GPT.BIN which is part of the security stuff. Correct me if I'm wrong, but aren't those the main components involved with bricking when trying to downgrade from 4.4.2 to 4.4 and lower?
But again, with a locked bootloader, as @kj2112 said, Write Protection will still be enabled.

KidJoe said:
I'm not too sure about that root method.
Step 11 tells you to downgrade the Bootloader (MOTOBOOT.IMG) and GPT.BIN which is part of the security stuff. Correct me if I'm wrong, but aren't those the main components involved with bricking when trying to downgrade from 4.4.2 to 4.4 and lower?
But again, with a locked bootloader, as @kj2112 said, Write Protection will still be enabled.
Click to expand...
Click to collapse
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?

Jumnhy said:
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Click to expand...
Click to collapse
Please see my response to you in the 4.2.2 to 4.4.2 thread.

kj2112 said:
Please see my response to you in the 4.2.2 to 4.4.2 thread.
Click to expand...
Click to collapse
Thanks, didn't realize until afterward it was the same voice in both threads.

Jumnhy said:
I've been a bit confused by allusions to rooting without write protection. Everyone says similar stuff to what you guys have said--well, without write protection disabled you'll lose root on reboot. I'd be okay with that, just avoid rebooting my phone and using stuff that requires a reboot to take effect. The only thing I really want root for is to see my partial wakelocks to be able to properly troubleshoot battery issues. I really like the stock Moto X ux. If I could, I'd probably use some Xposed modules too, but all I really really want is to get better insight into my wakelock situation. Elsewhere, though, I read that root is totally impossible on 4.4.2, unless you have an unlocked bootloader (which I obviously don't). So, is it possible to get root, even if it doesn't survive a soft reset?
Click to expand...
Click to collapse
take a read of -> http://mark.cdmaforums.com/MotoX-LockedRoot.html
Root itself is not lost on reboot, only changes done to the /system folder and other protected places.
But yes, if you already have 4.4.2 on your phone, and can't unlock your bootloader, you won't be able to root.

Jumnhy said:
Thanks, didn't realize until afterward it was the same voice in both threads.
Click to expand...
Click to collapse
Where you found another same threads ?

DANIEL AMBRUSO said:
Where you found another same threads ?
Click to expand...
Click to collapse
It was just kj2112 explaining a similar issue to me. Check it out, but essentially my understanding is that there's no root for 4.4.2 if the phone never had root previously (ie, if you naively took the OTA like me without thnking about implications for root.
---------- Post added at 10:01 PM ---------- Previous post was at 09:56 PM ----------
KidJoe said:
take a read of -> http://mark.cdmaforums.com/MotoX-LockedRoot.html
Root itself is not lost on reboot, only changes done to the /system folder and other protected places.
But yes, if you already have 4.4.2 on your phone, and can't unlock your bootloader, you won't be able to root.
Click to expand...
Click to collapse
Solid, thanks for the concise summary. I'd read jcase's posts a while back about a potential exploit--something about using it in a teaching session at BlackHat? He even says though, that the exploit he has will probably never be useful for the average user insofar as it would be too hard to implement and n00bz like myself would end up bricking our phones. So I'm not holding my breath on that one. Ugh. Sad I missed the window for the Chinese connection. Should have jumped on it.

The Tallest said:
Links to a thread on here.
Click to expand...
Click to collapse
Works with 4.4 and post-camera 4.2.2, but if you take the OTA to 4.-4-.2 it upgrades your bootloader and you lose the ability to turn write protection off ; root is pretty much useless at that point.
I have the Republic Wireless XT1049 and did the upgrade shown here and have 4.4.2 with write protect off.
Do not attempt this if you are already running 4.4.2!!!!!!!!!!!!!!! Your bootloader is already changed and you run a big risk of bricking if you try to downgrade to the 4.2.2 bootloader!!!
http://forum.xda-developers.com/mot...ireless-moto-x-kitkat-4-t2738233/post52348028
As usual, read the instructions carefully.
Then read through the posts! Different rooters had different issues!
AFAIK no one bricked though.

glarepate said:
Works with 4.4 and post-camera 4.2.2, but if you take the OTA to 4.-4-.2 it upgrades your bootloader and you lose the ability to turn write protection off ; root is pretty much useless at that point.
I have the Republic Wireless XT1049 and did the upgrade shown here and have 4.4.2 with write protect off.
Do not attempt this if you are already running 4.4.2!!!!!!!!!!!!!!! Your bootloader is already changed and you run a big risk of bricking if you try to downgrade to the 4.2.2 bootloader!!!
http://forum.xda-developers.com/mot...ireless-moto-x-kitkat-4-t2738233/post52348028
As usual, read the instructions carefully.
Then read through the posts! Different rooters had different issues!
AFAIK no one bricked though.
Click to expand...
Click to collapse
The steps in the thread you link to are how to use use 4.4.2 via Safestrap, which does add a layer of complexity. It is the only option to take 4.4.2 IF you have a locked bootloader and are rooted and write protection disabled. And many do have good luck with it, so it is an option IF your phone is still on 4.4.
If I understand correctly, each safestrap rom is unique for the carrier.. in other words, you can't use the Republic Wireless SS rom if you are on Verizon. You can't use the Verizon SS rom if you are on ATT, etc. (for example, they were waiting on the ATT 4.4.2 SBF to create a SS Rom for the ATT X).

KidJoe said:
The steps in the thread you link to are how to use use 4.4.2 via Safestrap, which does add a layer of complexity. It is the only option to take 4.4.2 IF you have a locked bootloader and are rooted and write protection disabled. And many do have good luck with it, so it is an option IF your phone is still on 4.4.
If I understand correctly, each safestrap rom is unique for the carrier.. in other words, you can't use the Republic Wireless SS rom if you are on Verizon. You can't use the Verizon SS rom if you are on ATT, etc. (for example, they were waiting on the ATT 4.4.2 SBF to create a SS Rom for the ATT X).
Click to expand...
Click to collapse
Yes, if you have already gone to 4.4.2 you are out of luck.
I'm using the T-Mobile SafeStrap Recovery with my RW Moto X. This was done by a Franken-ROM process that uses the 4.4.2 ROM without using the 4.4.2 bootloader and using the SS recovery to flash a zip file with some components of the 4.4.2 ROM and then flashing SuperSU. Whether or not it should be working, it is. Nothing I can, or want to, do about that.
But I am sure you are right that this resultant ROM would not work on phones from other carriers. Versions for other carriers are being developed though. It may simply be a matter of time and interest by motivated individuals until this is available for just about everyone.

[Q] VZW 4.4.4 Unlocked: Root and Tether enabled?

Before I update my DevEd to 4.4.4, I want to ensure that I will still be able to root (use recovery tool or something else?) and that there is some way to use tether.
On 4.4.3, I've been happy using WiFi Tether for Root users - would be nice if this continued to work, but am okay using a different method if need be.
Can someone confirm that both root & tether are functional, and if so, what method(s) are working?

With an Unlocked Bootloader, Yes, you can root by flashing TWRP and SuperSU, the same process. Just make sure you have the latest TWRP and SuperSU from their source web sites. That will be true for ALL updates so long as you have an unlocked bootloader. And it can be dev edition or carrier edition, as long as the bootloader is unlocked.
Wifi tether for root still works on my VZW Dev X with 4.4.4 update.

Mercutio5 said:
Before I update my DevEd to 4.4.4, I want to ensure that I will still be able to root (use recovery tool or something else?) and that there is some way to use tether.
On 4.4.3, I've been happy using WiFi Tether for Root users - would be nice if this continued to work, but am okay using a different method if need be.
Can someone confirm that both root & tether are functional, and if so, what method(s) are working?
Click to expand...
Click to collapse
Of course...you're unlocked. Same method - flash TWRP and it will root for you. Since you don't seem to be aware -- you can NOT update unless you flash back stock recovery and un-do any changes you made to /system including installing Xposed (if you did). If all you are using root for is WiFi Tether, nothing to worry about as you probably haven't modified /system. You WILL have to flash back the stock recovery.img before you can accept any OTA. Its always been like this.
WiFi tether should work on 4.4.4, as should the entitlement 'hack'. (I believe both have been confirmed, but check the entitlement hack threads to be sure about it)
And finally......since you mention being on 4.4.3 now, I'm assuming you are using the XT1053 GSM Dev edition (since 4.4.3 was never released for VZW). If so...you do realize that 4.4.4 isn't out yet for the XT1053, right?
It's only out for the VZW XT1060 and soak-tests are just now happening for the AT&T XT1058.

samwathegreat said:
Of course...you're unlocked. Same method - flash TWRP and it will root for you. Since you don't seem to be aware -- you can NOT update unless you flash back stock recovery and un-do any changes you made to /system including installing Xposed (if you did). If all you are using root for is WiFi Tether, nothing to worry about as you probably haven't modified /system. You WILL have to flash back the stock recovery.img before you can accept any OTA. Its always been like this.
WiFi tether should work on 4.4.4, as should the entitlement 'hack'. (I believe both have been confirmed, but check the entitlement hack threads to be sure about it)
And finally......since you mention being on 4.4.3 now, I'm assuming you are using the XT1053 GSM Dev edition (since 4.4.3 was never released for VZW). If so...you do realize that 4.4.4 isn't out yet for the XT1053, right?
It's only out for the VZW XT1060 and soak-tests are just now happening for the AT&T XT1058.
Click to expand...
Click to collapse
I'd just assumed to be on 4.4.3 since it's previous to 4.4.4 - but you're correct, I'm on 4.4.2 VZW. After reading through some update methods discussed on XDA, it seems that using RSDLite w/FXZ is the easiest - no need to undo any changes made to /system (I'm sure I've made some, but have no idea what they might have been) and no need to remove TWRP. Plus it supposedly preserves all the data.
And thank you for assuaging my concerns re: root & tether

Mercutio5 said:
I'd just assumed to be on 4.4.3 since it's previous to 4.4.4 - but you're correct, I'm on 4.4.2 VZW. After reading through some update methods discussed on XDA, it seems that using RSDLite w/FXZ is the easiest - no need to undo any changes made to /system (I'm sure I've made some, but have no idea what they might have been) and no need to remove TWRP. Plus it supposedly preserves all the data.
And thank you for assuaging my concerns re: root & tether
Click to expand...
Click to collapse
Take caution!! The original leaked fxz was indeed a keep data fxz. It's now gone. The new official leaked fxz is NOT a keep data fxz.
All you have to do is edit the XML file and remove the line containing 'erase userdata' and it will preserve your data.
If you don't do this all your data WILL be erased.
Keep that in mind...
Good luck

samwathegreat said:
Take caution!! The original leaked fxz was indeed a keep data fxz. It's now gone. The new official leaked fxz is NOT a keep data fxz.
All you have to do is edit the XML file and remove the line containing 'erase userdata' and it will preserve your data.
If you don't do this all your data WILL be erased.
Keep that in mind...
Good luck
Click to expand...
Click to collapse
Yikes!! Thank you for the heads up.
How did the leaked FXZ disappear? Surely someone's still got it somewhere?

Mercutio5 said:
Yikes!! Thank you for the heads up.
How did the leaked FXZ disappear? Surely someone's still got it somewhere?
Click to expand...
Click to collapse
Its all the same "inside" except the included XML file now contains the "Erase USERDATA" statement. Just remove that line from the XML before flashing with RSDLite and you're good.
No reason for the original leak to stick around.