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] 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] (AT&T) Best path to 4.4.2 from 4.4?

My setup: 4.4 ATT Moto X, Rooted (by way of latest jcase method), Locked bootloader, and I'm pretty sure write protection is off (though I don't remember how to check)
What I am wanting to know is how would and should I be able to get to 4.4.2, and get my root back (as I'm not confident any method will be able to "keep" my root safely without screwing something else up)? What's the best way based on my setup, and what files or tools would I need(stock 4.4 or 4.4.2 ROM, a new recovery image, etc)?
Since the root method I used hijacks the recovery, I suppose I technically don't have a functional one (other than it maintaining my root). Do I even need a custom recovery? I don't ever plan to flash anything other than basic stock firmware, though I may toy around with Xposed in the future. Also as a sidenote, im currently using ART instead of Dalvik. If any method or technique might conflict with that (other than Xposed), then let me know to the best of your knowledge.

Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)

...
Sent from my XT1058 using XDA Premium 4 mobile app

kj2112 said:
Write protection will be enabled on 4.4.2. You can have root, but a shutdown or hard reboot will erase the changes you make that are root oriented.
As far as getting to 4.4.2.....tonnes of info already here...multiple threads.
Here's a basic guide...and Google can help too. Read any thread related to 4.4.2 and locked bootloaders.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
Honestly i dont even care to have an unlocked bootloader. I just realy need root after I update. Write protection, so far i think, i've only needed for AdAway to work on my phone, though Im sure I have used or applied it else on my device. And thanks for the thread, but I was already subscribed .

Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)
Click to expand...
Click to collapse
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.

NameLessThugZero said:
While I would like to test that out further for you, I have only one phone lol. I very lightly looked in safestrap sometime ago when I was trying to find how to root previous versions of my phones software. Back then I didn't feel I needed it, as I was and still am trying to keep things simple this time around with my Android device. I'll look into it again and see if needs have changed, but would reeeeeally like to just find a way to get root after updating. Your way does actually sound enticing however.
Click to expand...
Click to collapse
The only ways to use 4.4.2 Rooted with Write Protection DISABLED is the Safestrap way, or to unlock your bootloader.
Since you have AT&T, Moto doesn't give out the code to unlock your bootloader (Non-Developer Edition Verizon phones are the same way.) so if you really want to unlock your bootloader, see -> http://forum.xda-developers.com/moto-x/general/verizon-moto-maker-bootloader-unlock-t2680651 I know the thread title says VERIZON but it works for ATT users too.

I see, thanks for the explanation, because I certainly wouldn't have know it was for AT&T users too! I'll check them out.
Sent from my XT1058 using XDA Premium 4 mobile app

Ctrl-Freak said:
I am using safestrap on my locked AT&T moto to get 4.4.2 + root + r/w on system - works perfectly.
(I modified the OTA to create a flashable zip that patches stock 4.4 up to 4.4.2, without updating the bootloader. I have an untested 4.4.2 flashable zip, and when the official SBF is released, I'll make another and test it myself.)[/QUOTE
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse

NameLessThugZero said:
So essentially, I cant just install Safestrap, then update to 4.4.2, correct? I'd need to do what you did, which is to modify the OTA?
Click to expand...
Click to collapse
Right. You want a modified version of the OTA that does not modify your bootloader and will patch /system from 4.4 to 4.4.2. I also manually patched the kernel up to 4.4.2.
And, my experience is that you also have to downgrade to 4.2.2. I don't quite understand why, but I have never been able to upgrade to 4.4.x (neither from the 4.4 leak or the official 4.4 version) without going back to 4.2.2 first. The eclipse ROM instructions, on the other hand, suggest that a safestrap:twrp factory wipe might be enough, but I remember trying that once, and it didn't work. YMMV
I already made a zip to flash a full copy of 4.4.2 (not a patch) that I made from my system dump, but it hasn't been tested. (I'm waiting for the SBF.)

Alright. Well I guess I'll have to wait a bit for someone to come out or prove there's a safer, surer method to update. Moto always did like to make thing like this difficult, heh.
Sent from my XT1058 using XDA Premium 4 mobile app

[Q] foxfi and the new system update verizon

if i update my moto x dev edition will it break foxfi. i see they just updated to 4.4 but im scared to do it hate having to use the bluetooth connection.

trinniboy68 said:
if i update my moto x dev edition will it break foxfi. i see they just updated to 4.4 but im scared to do it hate having to use the bluetooth connection.
Click to expand...
Click to collapse
Since you have the developer edition, are you rooted? If so, why not use the stock framework tether? You can use the Xposed module, or the Entitlement Check remover.
Also, if you are rooted, you can use the latest experimental build of WiFi Tether for Root Users.
Is there a specific reason you are wanting to use FoxFi? The only reason I can imagine is that you are not rooted.....but if you aren't rooted, why did you get the Developer Edition?

@trinniboy68,
I agree with @samwathegreat. If you have a Dev Edition, why not unlock your bootloader and root? It doesn't void your warranty on the Dev Edition. And its pretty easy on the Dev Edition.
If you root, and all you want to do is Tether, then to make taking future OTA's easier, I suggest using Wifi Tether For Root app (See my notes about setup at the bootom of THIS PAGE. )
Another option is [APP][MOD][Root]Hotspot Entitlement Bypass v1.1 5/9/2014, but it does make changes to the build.prop, and while it undoes them, I haven't tested to see if it changes the checksum of the build.prop when it reverts its changes(if it does, that would get in the way of future OTA's)

moto x
KidJoe said:
@trinniboy68,
I agree with @samwathegreat. If you have a Dev Edition, why not unlock your bootloader and root? It doesn't void your warranty on the Dev Edition. And its pretty easy on the Dev Edition.
If you root, and all you want to do is Tether, then to make taking future OTA's easier, I suggest using Wifi Tether For Root app (See my notes about setup at the bootom of THIS PAGE. )
Another option is [APP][MOD][Root]Hotspot Entitlement Bypass v1.1 5/9/2014, but it does make changes to the build.prop, and while it undoes them, I haven't tested to see if it changes the checksum of the build.prop when it reverts its changes(if it does, that would get in the way of future OTA's)
Click to expand...
Click to collapse
i have an unlocked bootloader. havent rooted yet cause i like the features of the moto are there roms that will dupl. the stock moto. i have verizon unlimited internet so need the ability to wifi link to my computer. as i am on the road a lot and its more secure to use my own wifi than someone elses. having a mac there arent any hacks for my phone, the one i did find the dev. isnt supporting it yet and bricking my phone i cant take right now as im fairly new to this. i rooted my s3

trinniboy68 said:
i have an unlocked bootloader. havent rooted yet cause i like the features of the moto are there roms that will dupl. the stock moto. i have verizon unlimited internet so need the ability to wifi link to my computer. as i am on the road a lot and its more secure to use my own wifi than someone elses. having a mac there arent any hacks for my phone, the one i did find the dev. isnt supporting it yet and bricking my phone i cant take right now as im fairly new to this. i rooted my s3
Click to expand...
Click to collapse
No 'hacks' for your phone? The entire android SDK is available for MAC. We have several users here who have flashed their phones 100% with MAC.
If you download the MAC Toolkit, it includes everything you need, even though it isn't supported by its devs anymore. You just won't use any of the scripts (that's all that no longer supported). Also, since you have the DEV edition, you WON'T lose your warranty by rooting it. It's HIGHLY unlikely you will brick your phone unless you do something totally stupid that is well documented here (like: you NEVER downgrade or flash older firmwares/versions on your Moto X - this is one of the few ways you can brick it).
Since you have already unlocked the BL, all you would do is fastboot flash TWRP recovery, and it will root for you. Then you can use either method that @KidJoe and I have suggested for you. There honestly isn't much at all you can mess up.
Additionally, once you install TWRP, you can take a full backup that you could restore in the event of a problem. PLUS the SBF images are available, so even without a backup your phone could still be restored back to stock.

trinniboy68 said:
i have an unlocked bootloader. havent rooted yet cause i like the features of the moto are there roms that will dupl. the stock moto. i have verizon unlimited internet so need the ability to wifi link to my computer. as i am on the road a lot and its more secure to use my own wifi than someone elses. having a mac there arent any hacks for my phone, the one i did find the dev. isnt supporting it yet and bricking my phone i cant take right now as im fairly new to this. i rooted my s3
Click to expand...
Click to collapse
Some of these sentences run together, so If I miss anything, I'm sorry.
Rooting wont remove any features of the stock Moto roms. As far as "other roms" duplicating stock, I haven't run anything but the stock rom. While there are "alternates" (like CM) if they are NOT based on stock, they will not have the Moto specific features like active display, always on listening (OK google now....), etc.
I have unlimited data too. I purchased the Dev X since I was going to have to buy an X at full retail because I wanted to keep my Unlimited (and be able to root without waiting on vulnerabilities/exploits).
All I've done is unlocked the bootloader, to root I just flashed TWRP recovery, and installed SuperSU (see -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738 although the TWRP and SuperSU versions linked are a little out of date now, they still work on 4.4 and 4.4.2). Then I use Wifi Tether for Root as mentioned earlier, greenify, Root Explorer, Quick Boot (reboot), Adree and not really much else that needs root, and no extra tweaks/hacks. In other words, I run stock, but rooted, with a few apps that need ROOT access, and nothing else modified on my phone.
The tools to flash the stock SBF files are RSDLite and mFastboot. Rsdlite is a GUI tool that flashes the full SBF/XML file, all commands, in like a batch mode. mFastboot is a command line tool that allows you to flash parts/pieces one at a time. I don't know if there is an RSDlite for Mac OS, but there is an mFastboot. So if you mess your phone up badly enough, you can usually recover with the stock images. (the only note being DO NOT DOWNGRADE your ROM!! for more see -> http://mark.cdmaforums.com/MotoX-Downgrade.htm )

thanks
KidJoe said:
Some of these sentences run together, so If I miss anything, I'm sorry.
Rooting wont remove any features of the stock Moto roms. As far as "other roms" duplicating stock, I haven't run anything but the stock rom. While there are "alternates" (like CM) if they are NOT based on stock, they will not have the Moto specific features like active display, always on listening (OK google now....), etc.
I have unlimited data too. I purchased the Dev X since I was going to have to buy an X at full retail because I wanted to keep my Unlimited (and be able to root without waiting on vulnerabilities/exploits).
All I've done is unlocked the bootloader, to root I just flashed TWRP recovery, and installed SuperSU (see -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738 although the TWRP and SuperSU versions linked are a little out of date now, they still work on 4.4 and 4.4.2). Then I use Wifi Tether for Root as mentioned earlier, greenify, Root Explorer, Quick Boot (reboot), Adree and not really much else that needs root, and no extra tweaks/hacks. In other words, I run stock, but rooted, with a few apps that need ROOT access, and nothing else modified on my phone.
The tools to flash the stock SBF files are RSDLite and mFastboot. Rsdlite is a GUI tool that flashes the full SBF/XML file, all commands, in like a batch mode. mFastboot is a command line tool that allows you to flash parts/pieces one at a time. I don't know if there is an RSDlite for Mac OS, but there is an mFastboot. So if you mess your phone up badly enough, you can usually recover with the stock images. (the only note being DO NOT DOWNGRADE your ROM!! for more see -> http://mark.cdmaforums.com/MotoX-Downgrade.htm )
Click to expand...
Click to collapse
thank you for the info

[Q] Best practice for updating VZW unlocked bootloader rooted 4.4.2 Stock ROM

I am on Verizon 4.4.2, bootloader unlocked, rooted, with TWRP. Obviously, OTA won't work, but what is the best way for me to update to 4.4.4 stock ROM w/o wiping my user data?

If the Moto X is anything like the Nexus 5, there may be an OTA update.zip that is lurking around and you can just flash that and then reflash root to update you to the latest software version. Or you could download and flash the SYSTEM.IMG and BOOT.IMG from the 4.4.4 Verizon ROM. I'd recommend the first one and make sure that someone else can safely say that the second method would even work!

Toys Samurai said:
I am on Verizon 4.4.2, bootloader unlocked, rooted, with TWRP. Obviously, OTA won't work, but what is the best way for me to update to 4.4.4 stock ROM w/o wiping my user data?
Click to expand...
Click to collapse
The proper way to update is to use the 4.4.4 FXZ from here: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
In order to retain your data and apps, you need to use the tools provided by @SamuriHL and use the "keep data" option.
Everything you need is listed in the first post, including links and instructions for the tools to use. All of your apps and settings will be intact --AS LONG as you use the tools provided in the OP. If you fail to do this, you WILL lose your data. Afterwards, you can flash TWRP again (from here: http://techerrata.com/browse/twrp2/ghost ) using fastboot, and re-root your device.
Next time, please remember to post your questions in Q&A, not general.
Good Luck :good:
P.S. I also want to add that using the FXZ is superior to taking the OTA for several reasons, many that I don't care to list. First and foremost, you don't need to worry about flashing stock recovery back (required to take an OTA), and you don't need to worry about any changes you may have made to /system. Follow the simple instructions, and it is done.
You will find numerous instances of people who have struggled to take the OTA, or who have spent enormous amounts of time trying only to have the OTA fail to install. I doubt you'll find ONE person who has struggled with the FXZ. It is so much simpler that I don't understand why anyone recommends using the OTA unless you are completely stock and unrooted. IMO, that is the only time you should use the OTA when an FXZ is available.

samwathegreat said:
The proper way to update is to use the 4.4.4 FXZ from here: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
In order to retain your data and apps, you need to use the tools provided by @SamuriHL and use the "keep data" option.
Everything you need is listed in the first post, including links and instructions for the tools to use. All of your apps and settings will be intact --AS LONG as you use the tools provided in the OP. If you fail to do this, you WILL lose your data. Afterwards, you can flash TWRP again (from here: http://techerrata.com/browse/twrp2/ghost ) using fastboot, and re-root your device.
Next time, please remember to post your questions in Q&A, not general.
Good Luck :good:
P.S. I also want to add that using the FXZ is superior to taking the OTA for several reasons, many that I don't care to list. First and foremost, you don't need to worry about flashing stock recovery back (required to take an OTA), and you don't need to worry about any changes you may have made to /system. Follow the simple instructions, and it is done.
You will find numerous instances of people who have struggled to take the OTA, or who have spent enormous amounts of time trying only to have the OTA fail to install. I doubt you'll find ONE person who has struggled with the FXZ. It is so much simpler that I don't understand why anyone recommends using the OTA unless you are completely stock and unrooted. IMO, that is the only time you should use the OTA when an FXZ is available.
Click to expand...
Click to collapse
Curious,
What would the difference be in using FXZ vs flashing a 4.4.4 ROM such as krypton? Is it because the FXZ will update boot loader?

SR3TLAW said:
Curious,
What would the difference be in using FXZ vs flashing a 4.4.4 ROM such as krypton? Is it because the FXZ will update boot loader?
Click to expand...
Click to collapse
Flashing Krypton is possible from Custom recovery, unlike an OTA / FXZ. In addition, I believe that Krypton only includes the /system and /boot partitions. This is why he states that you need to be on 4.4.2+ first.
The FXZ overwrites all relevant partitions with new data.

Vekhez said:
If the Moto X is anything like the Nexus 5, there may be an OTA update.zip that is lurking around and you can just flash that and then reflash root to update you to the latest software version. Or you could download and flash the SYSTEM.IMG and BOOT.IMG from the 4.4.4 Verizon ROM. I'd recommend the first one and make sure that someone else can safely say that the second method would even work!
Click to expand...
Click to collapse
Unfortunately the X is nothing like the N5.

KJ said:
Unfortunately the X is nothing like the N5.
Click to expand...
Click to collapse
Yeah, I've found that out as of recently, they are very different devices, very very different indeed