Database Develop

OTA 139.15.1 keep root

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Can I unroot without wiping / back to stock?

Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.

GADGTGUY said:
Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.
Click to expand...
Click to collapse
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.

You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6

the_rooter said:
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.
Click to expand...
Click to collapse
They push a BES client that checks. They already told me they know the phone is rooted. (big brother)
jj14 said:
You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6
Click to expand...
Click to collapse
Thanks for this info....
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.

GADGTGUY said:
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
It may - but it still won't get you direct OTA (since OTA now checks for any change to system files)

GADGTGUY said:
[snip]I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
Just to echo what jj14 said. The "Full unroot" option in SuperSU will remove root, but it won't (at least it hadn't on the last version of it that I tried) revert one file that root modifies, so, while you won't have root, and the BES client should work, the update checks the entire file system, so it will fail. A quick flash of only the system.img file using fastboot will remove root and leave everything else untouched.

Thanks for all the advice guys!
I appreciate the assistance... this is why this community rocks!
D.

I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.

GADGTGUY said:
I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.
Click to expand...
Click to collapse
Many of us would recommend you learn fastboot commands manually rather than relying on toolkits. This helps you get out of trouble when things go wrong. That said, its too late now

[Q] Updating rooted Nexus 6 question

I have an unlocked Nexus 6 64gb from Ebay that I activated on Verizon. I rooted it, installed 5.1 and did the build.prop and settings.db changes and have tethering, etc (unlimited).
A few questions:
Will the OTA update show up on my phone since it is rooted and/or since it was not purchased from Verizon?
If it does show up and I let it update to 5.1.1, will I need to do the build.prop and settings.db changes again?
If it does not show up and I install from Google's image, do I need to do the build.prop and settings.db changes again?
I am sure these are basic questions... sorry... this was my first phone root and will be my first update to apply since doing that.

an update will show up whether you have root or not, BUT.. you can not take or apply an ota if any system files have been changed. and guess what rooting your device did, change system files.

simms22 said:
an update will show up whether you have root or not, BUT.. you can not take or apply an ota if any system files have been changed. and guess what rooting your device did, change system files.
Click to expand...
Click to collapse
Ok thanks. So that means I update with the Google Image if I want to. I think there is an option to do that without a wipe. Is that recommended / OK? If so, I wont have to change any files again, right?

hifiaudio2 said:
Ok thanks. So that means I update with the Google Image if I want to. I think there is an option to do that without a wipe. Is that recommended / OK? If so, I wont have to change any files again, right?
Click to expand...
Click to collapse
factory image, or any custom rom. and yes, you can update via factory image and do it a certain way to not lose data. you dont ever "have to" change any files. if you keep it stock, completely, you get an update ota, and you keep goung after that. if you root, tou have choices. i keep my choices simple. i root and use custom kernels btw. i also use custom roms. so, for me, updating is just flashing the latest custom rom(be it stock/rooted or real cutom rom).

simms22 said:
factory image, or any custom rom. and yes, you can update via factory image and do it a certain way to not lose data. you dont ever "have to" change any files. if you keep it stock, completely, you get an update ota, and you keep goung after that. if you root, tou have choices. i keep my choices simple. i root and use custom kernels btw. i also use custom roms. so, for me, updating is just flashing the latest custom rom(be it stock/rooted or real cutom rom).
Click to expand...
Click to collapse
Thanks again for the help. So my wife has the exact phone and same root with hotspot enabled as I do. I forgot to tell her to ignore the update, so when the OTA verizon update showed up this morning, she installed it. Her phone still says 5.1, so I assume it just tried to install but didnt work, but the Hotspot icon was removed (I just went into settings and selected it again, and it seemed to work still), but I dont know what error it might have given when she tried to install or what settings or files that I had changed, like build.prop, etc, might be changed back. Is it likely that the system trying to install the OTA update would have changed my modified settings?
Going forward, I plan to fire up Wug's rootkit and just flash the 5.1.1 image with no wipe. SO everything I did on both phones should already be ready to go when the flash finishes, right? No settings for me to change all over again?

Will have to redo the build.prop edits. Full image flash will replace the build.prop with new one.

prdog1 said:
Will have to redo the build.prop edits. Full image flash will replace the build.prop with new one.
Click to expand...
Click to collapse
Cool, all done, thanks.

Unroot/Relock/revert to stock

Hey everyone,
I'm over rooting. Had an issue today where a backup refused to restore and in trying to fix it, I've deleted my OS. Yes, I'm bad at this. No big deal, I have backups of all my photos and other important stuff.
I don't really want to do the rooting/flashing thing anymore and just want to get my phone back to normal/out of the box as possible so that it will receive regular OTA updates etc. I just want to simplify things.
TWRP is installed. Is it as simple as flashing the latest official update? Or do I need to relock the phone somehow too?
I was going to follow: https://forum.xda-developers.com/oneplus-3t/how-to/guide-to-revert-oneplus-3t-to-stock-t3676210 but wanted to be sure that it would work even though I don't currently have an OS installed.
Thanks!

Southrncomfortjm said:
I'm over rooting. Had an issue today where a backup refused to restore and in trying to fix it, I've deleted my OS.
Click to expand...
Click to collapse
That isn't root. That is your lack of knowledge of the functions of custom recovery, and what the results will be. Better learning and knowledge, and a little more care could have easily prevented it from happening. You wiped the selections in the "Advanced" wipe section of TWRP. And the fact it's called "Advanced" should have been a good clue to not mess with it, unless you know exactly what you are doing.
It's also an easy condition to recover from.
Southrncomfortjm said:
I don't really want to do the rooting/flashing thing anymore and just want to get my phone back to normal/out of the box as possible so that it will receive regular OTA updates etc. I just want to simplify things.
TWRP is installed. Is it as simple as flashing the latest official update? Or do I need to relock the phone somehow too?
I was going to follow: https://forum.xda-developers.com/oneplus-3t/how-to/guide-to-revert-oneplus-3t-to-stock-t3676210 but wanted to be sure that it would work even though I don't currently have an OS installed.
Click to expand...
Click to collapse
That guide is needlessly complicated. Just download the flash the "full" update zip using TWRP, from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Make sure you are using a version of TWRP which supports Oreo (if you were on Oreo when you wiped OS, it should be okay). And that is all there is to it. You will be fully restored to stock, and after rebooting, stock recovery will replace TWRP.
You don't need to lock the bootloader to do this, and you don't need it for future OTAs. But a locked bootloader is arguably more secure, if you really don't need custom recovery or root.
On the other hand, if you still want to give root/phone mods a shot; the way to restore, and still have root is the same (flash full update zip). But just flash Magisk or SuperSU before rebooting, and you will be rooted, and still have TWRP.

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...