Related
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
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.
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
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
Hello all,
Hopefully this is not considered a useless post and is deleted! I have previously owned the OG Droid and GNex, both rooted and have run custom ROMs so, I am not a COMPLETE noob, but I'm also not an expert.
In any event, I purchased a Verizon DE phone so I could easily unlock and root. I have yet to even activate it, so it is FRESH! It has come with 4.2.2, 139.10.53-ghost, which seems like the original image. I want to upgrade this ONLY to the point of still being able to run my standard tethering app (which I am not sure which 4.4 upgrade breaks this functionality), and root. I also want to be able to run custom ROMs if desired.
I am also confused by whether or not there is a potential downgrade "bricking" of the device. There are threads out there which seem like it can be done, (see http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358), and many other threads that say that regardless of being a DE, it cannot be downgraded. If someone can clarify this for me, that would be great.
Three other questions at this point. One, the thread referenced above discussed using TWRP or CWM for recovery. I have only used CWM in the past. Are there pros and cons to either one? Seems like most everyone uses TWRP for the Moto X.
Two, are there ROMs for the Moto X that have all of the rooted functionality of 4.4.2, with none of the drawbacks of stock, rooted 4.4.2? Would I be better off using one of those?
Finally, will I be able to prevent OTA notifications if I stay with stock, rooted, and upgrade only to certain point?
Sorry for all the questions, and yes, I have been searching and reading, but I have not found enough clear information to feel comfortable not asking directly.
Thank you all in ADVANCE!
There are currently 4 Moto or Stock ROMs for the Verizon Moto X XT1060
139.10.53 = Initial Shipping 4.2.2
139.15.1 = 4.2.2 w/camera update or 1st OTA
140.45.5 = 4.4 or 2nd OTA
164.55.2 = 4.4.2 or 3rd OTA.
The Developer Edition, once the bootloader is unlocked, can be rooted no matter what Moto ROM is on your phone.
Due to changes in parts that are included with 4.4.2, under certain circumstances when trying to downgrade from 4.4.2 to 4.4 or lower, you could either brick your phone, or set it up to brick in the future when you take an upgrade. So it is suggested you just stick with what is on your phone once you get on 4.4.2. Besides, you wont need to downgrade to gain root once you unlock your bootloader.
If you haven't had 4.4.2 on your phone yet, you are perfectly welcome to upgrade from 4.2.2 to 4.4, then downgrade to 4.2 w/camera update (4.2.2 with camera update is Blur_Version.139.15.1.ghost_verizon.Verizon.en.US aka VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml). which is pretty much what the "Downgrading the bootloader" section of -> http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358 says.
Why worry about downgrading? Well, Locked bootloader users needed to downgrade to take advantage of an exploit in the older rom to gain root and disable write protection. This is not needed on the Dev Edition once the bootloader is unlocked.
As for custom roms, or 3rd party roms. Once your bootloader is unlocked you can flash them.
As for tethering. If you stick on a Stock Moto ROM, On 4.2.2 I used the Wifi Tether for Root from the Play Store.
For 4.4 and 4.4.2 I Use the wifi_tether_v3_4-experimental1.apk from https://code.google.com/p/android-wifi-tether/
change device profile to galaxy nexus (cdma/lte)
check box: wifi-driver reload
check box: enabled routing fix
If you have troubles, its also suggested to...
check box: wifi-driver reload 2
Doing this, I can set the SSID and WPA key. And it doesn't touch any system files or anything, so it is one less thing to get in the way of taking future OTA updates.
Oh, and the Dev Edition XT1060 and the retail/motomaker XT1060 use the same roms, radios, etc.
To root the dev edition see -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738
KidJoe said:
If you haven't had 4.4.2 on your phone yet, you are perfectly welcome to upgrade from 4.2.2 to 4.4, then downgrade to 4.2 w/camera update (4.2.2 with camera update is Blur_Version.139.15.1.ghost_verizon.Verizon.en.US aka VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml). which is pretty much what the "Downgrading the bootloader" section of -> http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358 says.
Click to expand...
Click to collapse
Thanks KidJoe! So I gather there would really not be a reason to downgrade a DE device anyway, since you can root it regardless of what stock ROM you are running. And since there are ways to wifi tether on 4.4.2, that is a non-issue.
I am still a bit confused regarding your quote above about the "upgrade from 4.2.2 to 4.4, then downgrade to 4.2 w/camera update..." Do you have to follow that path to get to 4.2 w/camera update, or can you just flash that ROM (139.15.1) once unlocked?
I currently use FoxFi on my GNex (paid for it!) and was hoping to use on Moto X. That's really why I didn't want to upgrade too far. Not sure that it works on it though.
Thanks again!
amajamar said:
I am still a bit confused regarding your quote above about the "upgrade from 4.2.2 to 4.4, then downgrade to 4.2 w/camera update..." Do you have to follow that path to get to 4.2 w/camera update, or can you just flash that ROM (139.15.1) once unlocked?
Click to expand...
Click to collapse
No. Was just saying that if you never had 4.4.2 on your phone, wanted to upgrade to 4.4, and later wanted to go back to 4.2.2 w/camera, you could.
amajamar said:
I currently use FoxFi on my GNex (paid for it!) and was hoping to use on Moto X. That's really why I didn't want to upgrade too far. Not sure that it works on it though.
Thanks again!
Click to expand...
Click to collapse
As far as I know, FoxFi still doesn't work on 4.4.2 on the X even when rooted. I don't recall if it works on 4.4. But I never used it.
If you have a DE there is absolutely no reason to downgrade. Ever. If you want to be able to tether here's the easiest way to do it.
Activate your phone.
Take all the updates.
Go to this site: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Follow those directions to a "T". Once that's done, download Xposed Framework, then download MotoTether.
The only time you'll need to worry about being rooted is if you delete bloatware and go to take the next OTA. You'll either need to reinstall all the apps you deleted manually or go to Motorola and request the factory image to reflash it.
The Tallest said:
If you have a DE there is absolutely no reason to downgrade. Ever. If you want to be able to tether here's the easiest way to do it.
Activate your phone.
Take all the updates.
Go to this site:
Follow those directions to a "T". Once that's done, download Xposed Framework, then download MotoTether.
The only time you'll need to worry about being rooted is if you delete bloatware and go to take the next OTA. You'll either need to reinstall all the apps you deleted manually or go to Motorola and request the factory image to reflash it.
Click to expand...
Click to collapse
So I should take the updates BEFORE unlocking? I was assuming it was the other way around. OK. Regarding "bloatware", if you just "freeze" it, does that prevent future OTAs? If you attempt to take an OTA with those apps either frozen or deleted, will you be risking bricking?
amajamar said:
So I should take the updates BEFORE unlocking? I was assuming it was the other way around. OK. Regarding "bloatware", if you just "freeze" it, does that prevent future OTAs? If you attempt to take an OTA with those apps either frozen or deleted, will you be risking bricking?
Click to expand...
Click to collapse
Rather than retyping.. please see -> http://mark.cdmaforums.com/MotoX-Unlock1.htm
while written due to the 3rd party supplier of bootloader unlock codes, the info applies equally to Dev Edition phones (other than the source of your unlock code)
The Tallest said:
If you have a DE there is absolutely no reason to downgrade. Ever. If you want to be able to tether here's the easiest way to do it.
Activate your phone.
Take all the updates.
Go to this site: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Follow those directions to a "T". Once that's done, download Xposed Framework, then download MotoTether.
The only time you'll need to worry about being rooted is if you delete bloatware and go to take the next OTA. You'll either need to reinstall all the apps you deleted manually or go to Motorola and request the factory image to reflash it.
Click to expand...
Click to collapse
I whole-heartedly agree with everything written in this post. You also have to make sure you are on stock recovery if you want to take an OTA. There are plenty of guides around here about taking an OTA, so just make sure you read some of those before you accept an OTA.
I have a suggestion for the OP:
1 - take all the updates on the phone. This will update the radios, boot loader; recovery, and the main ROM (system).
(The boot loader can not be downgraded, but as mentioned above, there really isn't any reason why you would want to try and downgrade your bootloader because you have a DE device)
2 - unlock the bootloader. you can google the steps in the process. Basically you get the unlock key from Motorola. The toughest part of the process is getting the fastboot and device drivers set up properly on your computer. This step will all of the userdata (pictures, apps etc.)
3 - use Fastboot to flash a custom recovery (I use TWRP ver 2.7). then boot into TWRP recovery w/o rebooting. Note that the volume down button is used in the bootloader to highlight your desired option, then volume up is used to select the option. When you are in TWRP and then exit, I believe it will prompt you to install the superuser binaries, which you will want to do.
At this point you can choose do flash a custom 4.4.2 ROM from the Dev section here (the Krypton rom is very good), or you can run stock w/ root. If you choose stock, I recommend the following steps for wifi and customization:
4 - boot up device normally and set it up. you will have be on the stock 4.4.2 rom with root.
5 - install Xposed from here on XDA.
6 then install the xposed module from the moto x apps section (it may also be available to download from within xposed) that enables wifi tethering. This will allow you to use the built in tethering without subscription issues.
7 - install the GravityBox xposed module (you can download this from within Xposed). This allows many of the customizations that you would normally find only in a custom rom (custom quicksettings, reboot options etc).
8 - install rootcloak module for xposed (download within xposed). This will let you run Isis or other apps that don't like root (it comes preconfigured for many apps).
jasoraso said:
I have a suggestion for the OP:
1 - take all the updates on the phone. This will update the radios, boot loader; recovery, and the main ROM (system).
(The boot loader can not be downgraded, but as mentioned above, there really isn't any reason why you would want to try and downgrade your bootloader because you have a DE device)
2 - unlock the bootloader. you can google the steps in the process. Basically you get the unlock key from Motorola. The toughest part of the process is getting the fastboot and device drivers set up properly on your computer. This step will all of the userdata (pictures, apps etc.)
3 - use Fastboot to flash a custom recovery (I use TWRP ver 2.7). then boot into TWRP recovery w/o rebooting. Note that the volume down button is used in the bootloader to highlight your desired option, then volume up is used to select the option. When you are in TWRP and then exit, I believe it will prompt you to install the superuser binaries, which you will want to do.
At this point you can choose do flash a custom 4.4.2 ROM from the Dev section here (the Krypton rom is very good), or you can run stock w/ root. If you choose stock, I recommend the following steps for wifi and customization:
4 - boot up device normally and set it up. you will have be on the stock 4.4.2 rom with root.
5 - install Xposed from here on XDA.
6 then install the xposed module from the moto x apps section (it may also be available to download from within xposed) that enables wifi tethering. This will allow you to use the built in tethering without subscription issues.
7 - install the GravityBox xposed module (you can download this from within Xposed). This allows many of the customizations that you would normally find only in a custom rom (custom quicksettings, reboot options etc).
8 - install rootcloak module for xposed (download within xposed). This will let you run Isis or other apps that don't like root (it comes preconfigured for many apps).
Click to expand...
Click to collapse
After reading the link Kidjoe supplied earlier (That was a FANTASTIC, MUST READ reference for noobs who want to understand the complexities of the Moto X), I may stay off KitKat, as I am not a fan of the white icons in the notification bar, however I do think this is the route (root??) I will take.