[Q] Should I Install OTA update? - Moto X Q&A

Hi, First off, I'm super rusty in the custom rom and kernell scene so explain things as easily as you can please.
Now, I have a moto x XT1053, the unlocked variant that they sold on the moto website that came with a net10 chip.
The thing is that I obviously unlocked the bootloader and installed the TWRP recovery. I have (almost) stock android and by that I mean stock with Xposed. I want to know if any of you guys could point me in the right direction, I mean, do I install the OTA update or do I return my phone to stock, and if it's the later, How do I return my phone to stock to do a proper OTA update?
Thanks in advance!

I have the same phone and was in pretty much your situation, including being rusty in flashing roms, kernels and such. I went with the OTA and am very glad I did. My subjective impression is that it's faster and at least as stable.
I thought my phone was close-to-stock, as I had removed some stuff (Xposed, notably) a while back to receive the 4.4.2 OTA. But the new Lollipop OTA wouldn't install, so I took the bull by the horns and flashed stock system.img that I got from Motorola's official firmware repository. I had to request access, and it took about 12 hours for that to come through.
After I downloaded the firmware zip file, I unpacked it and located the system.img file. Search on Google or this forum for the way to flash an img file to your phone, if you've forgotten (as I had). When I have time later today, I'll try to post a link to some clear instructions. I don't want to try to tell you from memory, as this is something I do about once or twice year since I got a Moto X (I tinkered a *whole* lot more when I had an HTC Sensation, but I've decided that if I want to keep my wife, I'd better stop playing with my mobile phone.)
I did this at the advice of a Motorola technician, who said the "most definitive way to return to unroot" was to flash stock system.img for 4.4.4. (I was part of last week's U.S. soak test, so Moto techs were handling questions from people like me who were wrestling with the OTA.)
I had worried that I might lose apps and data by flashing system.img, but I didn't lose a thing. I *did*, though, lose root, and I haven't re-rooted yet. Before I root, I'm waiting for the stock Lollipop 5.1 firmware to be made available on the Motorola repository so that I can have a backup of stock recovery.img.
Meanwhile, I'm enjoying Lollipop, which is like having a new phone.

varxx said:
I have the same phone and was in pretty much your situation, including being rusty in flashing roms, kernels and such. I went with the OTA and am very glad I did. My subjective impression is that it's faster and at least as stable.
I thought my phone was close-to-stock, as I had removed some stuff (Xposed, notably) a while back to receive the 4.4.2 OTA. But the new Lollipop OTA wouldn't install, so I took the bull by the horns and flashed stock system.img that I got from Motorola's official firmware repository. I had to request access, and it took about 12 hours for that to come through.
After I downloaded the firmware zip file, I unpacked it and located the system.img file. Search on Google or this forum for the way to flash an img file to your phone, if you've forgotten (as I had). When I have time later today, I'll try to post a link to some clear instructions. I don't want to try to tell you from memory, as this is something I do about once or twice year since I got a Moto X (I tinkered a *whole* lot more when I had an HTC Sensation, but I've decided that if I want to keep my wife, I'd better stop playing with my mobile phone.)
I did this at the advice of a Motorola technician, who said the "most definitive way to return to unroot" was to flash stock system.img for 4.4.4. (I was part of last week's U.S. soak test, so Moto techs were handling questions from people like me who were wrestling with the OTA.)
I had worried that I might lose apps and data by flashing system.img, but I didn't lose a thing. I *did*, though, lose root, and I haven't re-rooted yet. Before I root, I'm waiting for the stock Lollipop 5.1 firmware to be made available on the Motorola repository so that I can have a backup of stock recovery.img.
Meanwhile, I'm enjoying Lollipop, which is like having a new phone.
Click to expand...
Click to collapse
So, should I:
Delete GravityBox and Xposed
Install the .img file found within the zip for the Moto X dev Edition
Then I'll be able to install the OTA withouth losing data?

mundofeliz said:
So, should I:
Delete GravityBox and Xposed
Install the .img file found within the zip for the Moto X dev Edition
Then I'll be able to install the OTA withouth losing data?
Click to expand...
Click to collapse
The sequence you describe worked for me, assuming "deleting" GravityBox and Xposed is the preferred way of removing them. I can't remember.
The .img file to flash is system.img. You need to know how to get to fast boot/bootloader mode and perform the flash, of course.
If your experience is like mine, after receiving and installing the OTA, you'll have Lollipop without having lost any apps or data.
But you may want to wait for someone whose more up on this procedure to weigh in. When I updated, I proceeded as if I might lose all my apps and data, so I was pleasantly surprised.
BTW, I've since re-rooted, and I haven't had any problems. It's reassuring that the 5.1 ROM image is now available officially from Moto and elsewhere (info courtesy of dtg7: http://forum.xda-developers.com/showpost.php?p=61800775&postcount=11).

I'll do a Nandroid just in case. I'll do the steps above too, since all I've done is unlock bootloader, root and xposed I think this'll work for me. Kinda did only that originally for that reason but that was sooooo long ago. And also because the Moto X is such an amazing phone to begin with, I never saw the need to install other roms. Did you flash just the system.img, the recovery.img or both? I requested the firmware from moto and they approved but in the meantime I also downloaded the original too from filefactory, the exact same firmware I'm running (without modifications I mean.

mundofeliz said:
I'll do a Nandroid just in case. I'll do the steps above too, since all I've done is unlock bootloader, root and xposed I think this'll work for me. Kinda did only that originally for that reason but that was sooooo long ago. And also because the Moto X is such an amazing phone to begin with, I never saw the need to install other roms. Did you flash just the system.img, the recovery.img or both? I requested the firmware from moto and they approved but in the meantime I also downloaded the original too from filefactory, the exact same firmware I'm running (without modifications I mean.
Click to expand...
Click to collapse
IIRC, you'll need to do the Nandroid backup before you unroot, right?
I just flashed system.img. Won't that effectively restore the stock recovery? EDIT: According to the readme.txt file bundled in the stock ROM's zip file, recovery.img is flashed separately from system.img, so system.img will *not* restore the stock recovery.
I always feel safer running official firmware from Moto. For one thing, the labeling on the Moto dl site is very explicit, so you know exactly what you're getting.
I agree that the Moto X is a cool enough phone with a stock ROM that there's little need for custom ROMs. I was a flash-aholic when I had an HTC Sensation. But the Moto X pretty much has everything I need. Under KitKat, I did use XPosed to kill the Google search box, but otherwise I've been happy with the stock ROMs.
Oh, and I usually eventually run a custom recovery (TWRP) so I'll have more boot options. But I don't see that as essential now. I find I'm actually using my phone more than tweaking it, which is a change from previous phones.

Related

OTA 139.15.1 keep root

All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
First item, this is a question so it should belong in the question and answer threads! Secondly look here http://forum.xda-developers.com/showthread.php?t=2466191
Sent on my Moto X
Sorry, and thanks! I'll probably give this a shot, make that camera work a little better...
You can always install the SafeStrap ROM here. That's what I did.
http://forum.xda-developers.com/showthread.php?t=2484908
[Rom] [VZW] SafeStrap 139.12.57
Sent from my Moto X
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
mercado79 said:
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
Click to expand...
Click to collapse
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
dymmeh said:
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
Click to expand...
Click to collapse
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
mercado79 said:
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
Click to expand...
Click to collapse
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
juancaperez2000 said:
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
That's what I thought too. Thanks.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
will2live said:
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
Click to expand...
Click to collapse
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
mercado79 said:
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
Click to expand...
Click to collapse
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
boardrx182 said:
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
Click to expand...
Click to collapse
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
dymmeh said:
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
Click to expand...
Click to collapse
That's awesome, didn't realize that would happen automatically. I completely expected that I'd have to complete the entire root process steps that were outlined in an earlier post if I wanted root. Thanks for the reply.
will2live said:
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
Click to expand...
Click to collapse
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
jayboyyyy said:
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
Click to expand...
Click to collapse
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
will2live said:
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
Click to expand...
Click to collapse
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
jayboyyyy said:
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
Click to expand...
Click to collapse
Gotchya, makes total sense now what you are saying. I think there is just confusion at times when talking about root & OTA because of different ways to do it in a case like this device. Being a Moto guy for so long tho i'm use to all the BS they throw at us.....lol. That said that is why i posted the link I did. Imho it's a bad plan to update using the other method of installing pwnmymoto and not running it first before taking the OTA. Doing the process to protect root before updating is a much safer bet atm imo. Sure its a little more work but at the end of the day you dont have to be worried as much moving forward. Only concern I have still for doing it the longer way is if that process will work when they push out 4.3. It had alot of changes in it so lord only knows what will be up for keeping root. And really in my case its no concern but for all the folks with consumer version it is still a concern i think for the time being

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

Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Icon000 said:
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Click to expand...
Click to collapse
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
matt99017d said:
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
Icon000 said:
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
Click to expand...
Click to collapse
the only rom out for SS that i am aware of is just a ported tmobile rom for vzw phones that has the update built in. Basically it is just the OTA stock rom running on SS. This is what I am using currently. Not sure if it flashable for ATT phones, but I'm sure there is some workaround there. Or maybe the OP on that thread can make a ATT one if you asked him. SS is stable as of now. Haven't had any new updates to it because no one is having any problems currently (at least with moto x devices).
For your question pertaining to options for taking the OTA. There are 4 methods now.
1. SS method described above
2. use the thread called something like "keep root through the OTA." It basically takes the ota without updating the BL so you can still downgrade to your stock original FW that you are on now. It's the same thing as the SS method because SS also does not udpate the BL, but you won't be using SS for this method obviously.
3. you can flash recovery.img (and system.img if you need to) or just RSD, then install pwnmymoto without running it, then take the ota and pwnmymoto will root the phone automatically after the ota is taken. you won't be able to downgrade your FW anymore with this method.
4. you can just take the ota (also must flash or use rsd to take it obviously) and then use jcase's rockmymoto root exploit. This uses adb commands and telnet stuff. Not too difficult but if you are unfamiliar with all of that then it will take at least some reading. There is also a thread out there for windows users that simplifies it pretty well.
For future Kit kat root. it is still up in the air what will happen with that. I chose to use SS because it was easy. quick. and allows me to make nandroids. I also like knowing that I can still flash to original stock FW in case that might be necessarry for getting root on kit kat. This seems less likely now that jcase created a root method for the OTA that is out, but I'm still just playing it safe personally, even if it might be pointless now.

[Q] 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

[Q] Having trouble figuring out rooting & recovery works on Moto X coming from Nexus

[Q] Having trouble figuring out rooting & recovery works on Moto X coming from Nexus
I'm no noob, I've been rooting for a while, but I can't figure out how to root this damn thing . On a Nexus, I just unlocked, flashed TWRP, then flashed superuser from TWRP, and I was done. How does it work on this phone? Can I just flash TWRP and then from TWRP flash a root zip? I'd rather not use any toolkits and such (which seem to be all the rage on this forum). Running Pure edition btw. On latest Lollipop OTA.
mateopase said:
I'm no noob, I've been rooting for a while, but I can't figure out how to root this damn thing . On a Nexus, I just unlocked, flashed TWRP, then flashed superuser from TWRP, and I was done. How does it work on this phone? Can I just flash TWRP and then from TWRP flash a root zip? I'd rather not use any toolkits and such (which seem to be all the rage on this forum). Running Pure edition btw. On latest Lollipop OTA.
Click to expand...
Click to collapse
Yes its pretty much the same, the forums are abit immature at the moment there aernt any proper guides, i just did things the Nexus way
unlock your bootloader first through motorola, following the instructions (make sure there are no spaces in the unlock key): https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
flash twrp, then install the superSU zip from adb sideload or from your internal storage if it was already downloaded
youre done
also, you could flash the stock logo image to remove the warning boot image, http://forum.xda-developers.com/moto-x-2014/development/warning-message-unlocked-bootloader-t2871478 to make things look nicer
IINexusII said:
Yes its pretty much the same, the forums are abit immature at the moment there aernt any proper guides, i just did things the Nexus way
unlock your bootloader first through motorola, following the instructions (make sure there are no spaces in the unlock key): https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
flash twrp, then install the superSU zip from adb sideload or from your internal storage if it was already downloaded
youre done
also, you could flash the stock logo image to remove the warning boot image, http://forum.xda-developers.com/moto-x-2014/development/warning-message-unlocked-bootloader-t2871478 to make things look nicer
Click to expand...
Click to collapse
Awesome, thanks. Looks like that's what I'll end up doing. I really messed up my phone though when trying to get back to stock. Hopefully my stock image request will be approved soon and I'll be able to go through the process again.
One more question, if I kinda messed up restoring everything to 4.4.4, but I can boot the phone properly, will updating to 5.0 via an OTA update fix any mistakes I made along the way?
mateopase said:
One more question, if I kinda messed up restoring everything to 4.4.4, but I can boot the phone properly, will updating to 5.0 via an OTA update fix any mistakes I made along the way?
Click to expand...
Click to collapse
Not necessarily. The ota contains only changed files (not all files) and therefore if something is wrong with a file that wasn't changed (including anything in /data) then it will still be broken after the update.
crpalmer said:
Not necessarily. The ota contains only changed files (not all files) and therefore if something is wrong with a file that wasn't changed (including anything in /data) then it will still be broken after the update.
Click to expand...
Click to collapse
Alright. Do you know of any way to return to stock without going through Motorola's waiting game. It's been a few hours now and I still haven't been approved for the download.
mateopase said:
Alright. Do you know of any way to return to stock without going through Motorola's waiting game. It's been a few hours now and I still haven't been approved for the download.
Click to expand...
Click to collapse
Honestly, I haven't looked at what options are available for images to flash.
When I asked for firmware, I believe that I asked on a Friday evening and received access on the following Monday morning. So maybe you'll get access in another 15-16 hours? That is your safest bet if your phone is working well enough to last you until then.

Can a rooted phone be updated?

Can a rooted phone be updated? If i root my razor, will i be able to update without re-rooting?
ChronosTrigger said:
Can a rooted phone be updated? If i root my razor, will i be able to update without re-rooting?
Click to expand...
Click to collapse
No, it fails to install. You need to reflash the stock boot image to take an OTA.
Confused still
CurtisMJ said:
No, it fails to install. You need to reflash the stock boot image to take an OTA.
Click to expand...
Click to collapse
I'm Sorry i'm so nooby in this regard.
So do you mean i have to basically get the stock ROM back again.
Then I can re-root like i did with the earlier version?
ChronosTrigger said:
I'm Sorry i'm so nooby in this regard.
So do you mean i have to basically get the stock ROM back again.
Then I can re-root like i did with the earlier version?
Click to expand...
Click to collapse
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
WARNING: This file is really intended for a developer to use in making a rooted slot. Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? Although, mostly likely, it won't flash at all if you are rooted.
I used adb to capture the Razer Phone 2 MR2 OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5
translucentfocus said:
WARNING: Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? I'm not rooted, just trying to help people get the files they need.
I used adb to capture the OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5
Click to expand...
Click to collapse
So With this. You can root, AND if they have any Update for the phone in the future, I can Update it without losing my root?
ChronosTrigger said:
So With this. You can root, AND if they have any Update for the phone in the future, I can Update it without losing my root?
Click to expand...
Click to collapse
Not quite... The update will likely fail to apply due to checksum failures. If it did go through it would probably brick the kernel so that's a good thing. Sorry, there's not really a way to automatically root after official OTAs as they update block by block between two known states, and neither is rooted. It's just sort of not possible, by design. You have to unroot, update and root again.
The OTA package translucentfocus has provided allows us to reproduce a single slot before the week's wait for the factory image so we can root sooner.
translucentfocus said:
WARNING: Flashing the file below could? remove root or cause other issues if you're rooted. Brick maybe? I'm not rooted, just trying to help people get the files they need.
I used adb to capture the OTA. It's located here.
I also downloaded it... but figure y'all would prefer a link straight to the Google source
SHA1 is the file name so you can verify it. E9F494FACBF8B7A6DF32F342C84459A7051ACE24
The SHA256 I calculated was: FF571E225BC81C8D450964E0C7BA28DF13E963798F9E5AF7E7C142DE7FBE51A5
Click to expand...
Click to collapse
which OTA is this? Also how to update
xterminater07 said:
which OTA is this? Also how to update
Click to expand...
Click to collapse
Sorry, I didn't specify. It's the MR2 update for the Razer Phone 2. Original reply has been also updated with version information in bold.
How to update? Actually, I posted the OTA because it's really for someone to make a slot with root before Razer releases the Factory MR2 Images--as @CurtisMJ mentioned previously.
CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
Sorry to bring back an old thread but just a few questions if you don't mind.
I just bought a used Razer 2 seems like the user rooted it (I was unaware) and it has been years since I rooted anything. I downloaded root checker and it said I was rooted. I assume I'm running the stock rom, though magisk manager was installed on the phone when I turned it on so I guess it's not stock. I guess this means I can not take any OTA or it could brick? I went into system update and it still checked to make sure I was up to date so maybe OTA isn't disabled? So much has changed with apps and rooting since I messed with it that I don't know enough and I don't want to brick or bootloop the device.
Thanks
Univsoldur said:
Sorry to bring back an old thread but just a few questions if you don't mind.
I just bought a used Razer 2 seems like the user rooted it (I was unaware) and it has been years since I rooted anything. I downloaded root checker and it said I was rooted. I assume I'm running the stock rom, though magisk manager was installed on the phone when I turned it on so I guess it's not stock. I guess this means I can not take any OTA or it could brick? I went into system update and it still checked to make sure I was up to date so maybe OTA isn't disabled? So much has changed with apps and rooting since I messed with it that I don't know enough and I don't want to brick or bootloop the device.
Thanks
Click to expand...
Click to collapse
Yes, that sounds about right. When rooted the OTA function doesn't disable right away. Only after its downloaded an update and actually tries to apply it it'll refuse. The new Android update engine is pretty good at not bricking. My guess is probably stock. If it's rooted, then the bootloader is unlocked, and it's not too bad. For magisk root at least all you need to do is flash the stock boot image and the OTA will apply. With factory images around and an unlocked bootloader you'll have a hard time bricking it. Just don't untick "OEM Unlocking" in developer options. Ever. (Or at least until you've fully restored stock firmware. It's supposed to be disabled so you can't make that mistake but Magisk hide tricks the firmware into believing the bootloader is locked so it's enabled. Whaddayagonnado)
CurtisMJ said:
Yes. Razer's update engine doesn't seem to have the option to download full images like some other OEMs, so only fully stock ROM can be upgraded.
On that note, Razer seems to have set a week as the delay for releasing factory images, so if you want to keep root you might want to wait after an OTA, though we may be able to reproduce a slot earlier if someone captures the OTA package (but it's not as verifiable of course)
Click to expand...
Click to collapse
CurtisMJ said:
Yes, that sounds about right. When rooted the OTA function doesn't disable right away. Only after its downloaded an update and actually tries to apply it it'll refuse. The new Android update engine is pretty good at not bricking. My guess is probably stock. If it's rooted, then the bootloader is unlocked, and it's not too bad. For magisk root at least all you need to do is flash the stock boot image and the OTA will apply. With factory images around and an unlocked bootloader you'll have a hard time bricking it. Just don't untick "OEM Unlocking" in developer options. Ever. (Or at least until you've fully restored stock firmware. It's supposed to be disabled so you can't make that mistake but Magisk hide tricks the firmware into believing the bootloader is locked so it's enabled. Whaddayagonnado)
Click to expand...
Click to collapse
Thanks for the detailed response I managed to get up with the previous owner on swappa last night. He told me he unlocked the phone but never actually got around to rooting it. He also said it is running stock and the reason magisk is still on the phone after a wipe is because magisk persists after a wipe.
Messages from him.
Sorry about that, I did unlock the bootloader but I never actually got around to rooting. I usually relock the bootloader before I sell it but I completely forgot. You can apply an ota because I never installed a custom recovery, something else I didn't get around to doing. You can easily relock the bootloader using adb. If you need help with this let me know and I can walk you through it. But the bootloader being unlocked has zero effect on ota's. You are all good to go as far as that goes.
Oh no you're absolutely fine with an ota. I just looked it up and you're absolutely right, magisk does survive a reboot now. Since I didn't load a custom recovery though an ota will install just fine. Although when an ota does install though it will most likely remove magisk because it will write over the boot.img with the factory one. Here is the link to the factory images. It includes instructions on how to install it. But honestly a new ota should be released any time now since the last one I think was November. Once that installs you will be completely back to stock.
Does this sound accurate to y'all. Thanks again
@Univsoldur His knowledge seems a little dated. Kind of how mine was a few months ago Anyways here goes:
If a root checker says it's rooted then it probably is. I'm not sure why he says it isn't.
Magisk does indeed persist through a data wipe. I wasn't aware magiskinit could unpack the manager APK though. Neat
He's right in that an unlocked bootloader won't affect OTAs, but having magisk installed will.
The RP2 uses the new A/B update scheme. In this case it doesn't matter whether a custom recovery was ever installed. Recovery mode is not used during the process of installation. Unfortunately the new update scheme is also heavily based on deltas, even on the kernel image, so OTAs will be broken as it won't be able to retrieve a full kernel image from the OTA servers. Some OEMs' ROMs can do that, but Razer's can't. You can flash the factory images if you truly want a clean start, but to fix OTAs and remove magisk, reflashing just the kernel image with one from the factory image should be sufficient. The magisk uninstaller won't work due to the data wipe so that's probably the only option.
CurtisMJ said:
@Univsoldur His knowledge seems a little dated. Kind of how mine was a few months ago Anyways here goes:
If a root checker says it's rooted then it probably is. I'm not sure why he says it isn't.
Magisk does indeed persist through a data wipe. I wasn't aware magiskinit could unpack the manager APK though. Neat
He's right in that an unlocked bootloader won't affect OTAs, but having magisk installed will.
The RP2 uses the new A/B update scheme. In this case it doesn't matter whether a custom recovery was ever installed. Recovery mode is not used during the process of installation. Unfortunately the new update scheme is also heavily based on deltas, even on the kernel image, so OTAs will be broken as it won't be able to retrieve a full kernel image from the OTA servers. Some OEMs' ROMs can do that, but Razer's can't. You can flash the factory images if you truly want a clean start, but to fix OTAs and remove magisk, reflashing just the kernel image with one from the factory image should be sufficient. The magisk uninstaller won't work due to the data wipe so that's probably the only option.
Click to expand...
Click to collapse
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?
I'm wondering if it would be possible to flash the unlocked Razer phone 2 firmware to the AT&T version. Would the bootloader need to be unlocked?
Univsoldur said:
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?
Click to expand...
Click to collapse
Yes, that will return it to stock and remove Magisk. No, if you flash the factory image you don't need to do anything further with the kernel.
---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------
DrGonzo6o said:
I'm wondering if it would be possible to flash the unlocked Razer phone 2 firmware to the AT&T version. Would the bootloader need to be unlocked?
Click to expand...
Click to collapse
The bootloader needs to be unlocked, yes. I had the unlocked one from the start, so I can't comment on how well that will work though.
Has anyone with an AT&T version successfully flashed unlocked firmware?
Univsoldur said:
So you think to get it back to stock I could just go here.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Will that remove magisk and return it back to stock I would assume there is no threat of flashing the stock image. Besides that do I need to mess with the kernel?
Click to expand...
Click to collapse
I did post a full unroot guide...

Categories

Resources