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]I'm not a noob, not yet a woman..i mean, expert.

Hello!
Recently jumped shipped to AT&T moto x and am absolutely loving it. I was perusing around the forum, and really wanted to ask some questions on a specific thread but due to the fear and anxiety of sounding dumb and wasting everyone else's time, I'm just posting a question here hoping that even stupid questions are answered with lots of love. I'm pretty comfortable with rooting, flashing.....aka I'm really good at following instructions, but would really like to expand my knowledge further and am having difficult time getting the explanations I need. SO, hoping some kind soul on here with AT&T Moto X will answer my questions in one shot.
Since my Moto X automatically updated with the new camera update via OTA when I got it four days ago, I was able to successfully root it using JCase's new RockMyMoto method. So, now I'm rooted - great. Everything is set up perfectly the way I want. Then now I find out that AT&T 4.4 is leaked, meaning it's probably going to be ready for an OTA update in the near future (I'm not planning on using the leaked one). So my questions are as follows...
1. I'm going to keep mine rooted until AT&T has 4.4 available for OTA update. Can I simply just run that update when it's available (which will break the root), then just re-root it when that's also available (which it seems like will be rather soon according to Jcase's tweet...)? Or will running the OTA update on my rooted moto x cause more issues other than simply breaking the root? Should I be going back to stock, get the OTA update, THEN re-root it?
2. My understanding is that AT&T boot loader is still locked down...so to my limited knowledge, this means I'm not able to make a NANDROID back up using CWM...am I wrong here in any way? Is there a way to make a NANDROID-like back up (which I used to back in S3 days) without having my bootloader unlocked?
3. Tethering...I was able to use FoxFi fine on my S3 (I got that good old granfathered unlimited data plan....), but it does not seem to work on my new Moto X. Is there any known work around for this? I have Titanium Backup Pro as well, so thought I could maybe just freeze the tether provision or w/e by AT&T but seems like I'm also somehow misunderstanding that there as no such thing seems to exist.
Thanks,
Yoondroid

I can only respond to your first question. You can not take an ota while rooted. The exploit breaks the stock recovery. In order to take the update, you'll have to fastboot the factory images to revert to an in rooted state and then accept the ota. It's really easy and only takes a few minutes... Assuming you have adb set up and know how to use it, if not, an hour or so if searching and reading will get you up to speed.
Sent from my XT1058 using XDA Premium 4 mobile app

theraffman said:
I can only respond to your first question. You can not take an ota while rooted. The exploit breaks the stock recovery. In order to take the update, you'll have to fastboot the factory images to revert to an in rooted state and then accept the ota. It's really easy and only takes a few minutes... Assuming you have adb set up and know how to use it, if not, an hour or so if searching and reading will get you up to speed.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can also just flash the recovery.img back and take the OTA update while rooted.

You can install safestrap to make a backup and WiFi tether root works with some minor changes there's a thread somewhere.

Hmm, thanks guys I'll be checking out/learning more about the fastboot option
As for tethering, I've found some good information though for the first option, I haven't figured out a way to patch the at&t apk OP posted in his thread. Seems like quite the ingenious work around though, so hopefully I'll be able to figure it out soon! The second option seems to be a quick work around to get tethering to work, but seems way less secure...and I'll be using tethering to do work which I prefer to be on a much secure network, so we'll see.
First (tricking the phone to think it's not an at&t phone when turning on tethering in native app): http://forum.xda-developers.com/showthread.php?t=2443562
Second: http://forum.xda-developers.com/showthread.php?t=2449534&page=3

mandrsn1 said:
You can also just flash the recovery.img back and take the OTA update while rooted.
Click to expand...
Click to collapse
just so the OP is led astray, if you only flash the recovery.img and you have made changes to your system apps or anything in the /system then you won't be able to take the ota and it will likely through you into a BL. If you don't know what you have changed, then go ahead and flash the system.img as well as recovery and you will be good to go. If you know what you changed then uninstall all of your root apps and change everything you change in the /system back to how it was and take the ota (after flashing recovery.img of coarse).
here is a great guide to adb stuff for you as well that got me started. still go back to it for reference occasionally. its a little old but it is still good.
http://forum.xda-developers.com/showthread.php?t=872128

[Q] 4.2.2 Root to 4.4 Root on AT&T

Okay, I am just wanting to clear things up for myself with this question. I've seen it similarly asked on other threads, but I have yet to find answer to them.
Currently, I am Stock + camera update + rooted with RockMyMoto. I haven't frozen or uninstalled or otherwise done anything to system apps or files (I disabled a few through Android itself before root, but never touched them since) I do use Permissions Denied; an app that does what it says for any app I chose, however I only use it for non-system apps. My phone is essentially stock, with root (bootloader locked). Thats all I want for whenever I update to 4.4 at the moment. Speaking of which...
I am trying to determine the best way to go about this. Since I havent done much to my phone, I am curious to know if I can just install the OTA (since I've altered no system files, but I know this isn't usually advised) then apply the latest root method done by jcase. Can it be as straight forward as that? Or do I absolutely need to flash back to STOCK stock, apply the camera update, the apply the 4.4 update, THEN use his method?
Trying to find a method that is at least safe. Preferably safe, quick and easy. But I know these methods aren't always quick .

NameLessThugZero said:
Okay, I am just wanting to clear things up for myself with this question. I've seen it similarly asked on other threads, but I have yet to find answer to them.
Currently, I am Stock + camera update + rooted with RockMyMoto. I haven't frozen or uninstalled or otherwise done anything to system apps or files (I disabled a few through Android itself before root, but never touched them since) I do use Permissions Denied; an app that does what it says for any app I chose, however I only use it for non-system apps. My phone is essentially stock, with root (bootloader locked). Thats all I want for whenever I update to 4.4 at the moment. Speaking of which...
I am trying to determine the best way to go about this. Since I havent done much to my phone, I am curious to know if I can just install the OTA (since I've altered no system files, but I know this isn't usually advised) then apply the latest root method done by jcase. Can it be as straight forward as that? Or do I absolutely need to flash back to STOCK stock, apply the camera update, the apply the 4.4 update, THEN use his method?
Trying to find a method that is at least safe. Preferably safe, quick and easy. But I know these methods aren't always quick .
Click to expand...
Click to collapse
Pawnymoto hijacks the stock recovery so you won't be able to install the update, you need to flash the stick recovery at the least
Sent on my Moto X

flashallthetime said:
Pawnymoto hijacks the stock recovery so you won't be able to install the update, you need to flash the stick recovery at the least
Sent on my Moto X
Click to expand...
Click to collapse
What do I need in order to do that, or should I just RSD lite back to a stock Moto X?

NameLessThugZero said:
What do I need in order to do that, or should I just RSD lite back to a stock Moto X?
Click to expand...
Click to collapse
I would say its safer to rsdlite back to 100% stock, that way you know everything is ready to accept the ota and you won't end up in a bootloop
Sent on my Moto X

[Q] Moto X AT&T Wifi hotspot / tethering

I am getting of very good price on a Moto X from AT&T. I plan to unlock it for use in Canada.
I am wondering if tethering / wifi hotspot will be available ? since the bootloader is not unlockable and even rooting might be impossible depending on what android version it comes with, i'm worried i might be stuck with it. and the wifi hotspot is a must for me.
any help would be appreciated.
thanks,

armrob said:
I am getting of very good price on a Moto X from AT&T. I plan to unlock it for use in Canada.
I am wondering if tethering / wifi hotspot will be available ? since the bootloader is not unlockable and even rooting might be impossible depending on what android version it comes with, i'm worried i might be stuck with it. and the wifi hotspot is a must for me.
any help would be appreciated.
thanks,
Click to expand...
Click to collapse
i don't know what ATT's policy is but if you're on a tiered data plan through VZW, tethering is enabled by default.

If you're running 4.4 you're golden can permanent root and disable write protection using slapmymoto, I did it with the toolkit, you can find it here, send me a pm if you need help. If you're on 4.4.2 you can use towelPie to root and the entitlement hack linked below the towelPie root link. I have a moto x verizon locked boot on 4.4.2 and have towelPie set to root at reboot and works flawlessly, but beware verizon is sending 4.4.4 to phones starting today, I got the update downloaded it just to see which update it was and than quickly opened FX explorer and went to the root cache folder and sent it to outerspace LOL and than went to the root/system/pri-apps folder and deleted the 3c_OTA.apk and 3c_OTA.odex files so it wouldn't ever download it again.. beware each time you rebooot you must redelete those two files since towelPie is only good til the next reboot.
After rooting with towelPie than run the entitlement hack linked below.. the dev has set it up to run at reboot, but it doesn't work currently with the 4.4.2 combo using towelPie, towelPie does run and root automatically at each reboot but the entitlement hack is running at the same time during boot and it tries to do its thing before towelPie has done its thing LOL and fails. the solution is easy just run it manually after each boot. works like a charm.
Edit: I have wrote the developer and he has informed me he is going to fix the entitlement hack by placing a time delay in the app so it gives towelPie time to finish root first, so just keep a lookout for his vers. 1.3 in the entitlement hack thread.
http://forum.xda-developers.com/moto-x/themes-apps/root-towelpieroot-motorola-devices-t2825059
http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152

doitinthedirt said:
If you're running 4.4 you're golden can permanent root and disable write protection using slapmymoto, I did it with the toolkit, you can find it here, send me a pm if you need help. If you're on 4.4.2 you can use towelPie to root and the entitlement hack linked below the towelPie root link. I have a moto x verizon locked boot on 4.4.2 and have towelPie set to root at reboot and works flawlessly, but beware verizon is sending 4.4.4 to phones starting today, I got the update downloaded it just to see which update it was and than quickly opened FX explorer and went to the root cache folder and sent it to outerspace LOL and than went to the root/system/pri-apps folder and deleted the 3c_OTA.apk and 3c_OTA.odex files so it wouldn't ever download it again.. beware each time you rebooot you must redelete those two files since towelPie is only good til the next reboot.
After rooting with towelPie than run the entitlement hack linked below.. the dev has set it up to run at reboot, but it doesn't work currently with the 4.4.2 combo using towelPie, towelPie does run and root automatically at each reboot but the entitlement hack is running at the same time during boot and it tries to do its thing before towelPie has done its thing LOL and fails. the solution is easy just run it manually after each boot. works like a charm.
Edit: I have wrote the developer and he has informed me he is going to fix the entitlement hack by placing a time delay in the app so it gives towelPie time to finish root first, so just keep a lookout for his vers. 1.3 in the entitlement hack thread.
http://forum.xda-developers.com/moto-x/themes-apps/root-towelpieroot-motorola-devices-t2825059
http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
Click to expand...
Click to collapse
OK, perfet. I will try that.
thanks,

armrob said:
OK, perfet. I will try that.
thanks,
Click to expand...
Click to collapse
and by the way you have to check the option to run those apps at reboot they're not automatically set to do it.