Accidentally rooted my new RMA phone before I installed the 5.0 update that needed to be installed. How do I temp unroot so that I can install the update. I tried disabling Superuser to no avail. Every time I try installing the OTA I get an error saying system must be remounted or something.
mdandashly said:
Accidentally rooted my new RMA phone before I installed the 5.0 update that needed to be installed. How do I temp unroot so that I can install the update. I tried disabling Superuser to no avail. Every time I try installing the OTA I get an error saying system must be remounted or something.
Click to expand...
Click to collapse
no such thing as temp unroot.
1. you can flash the factory img, which is already the latest, then reroot.
2. you can flash any of the aosp roms, which are all the latest, in the android and original development sections, and not worry about an ota, ever.
simms22 said:
no such thing as temp unroot.
1. you can flash the factory img, which is already the latest, then reroot.
2. you can flash any of the aosp roms, which are all the latest, in the android and original development sections, and not worry about an ota, ever.
Click to expand...
Click to collapse
Gotcha, I seem to remember being able to temporarily unroot back in the day.
You have to flash the stock factory image to unroot. If you do, you might as well just flash the stock factory image with the LRX21O update included, at https://developers.google.com/android/nexus/images
Edit: Sorry I just realized someone else replied while i was typing.
mdandashly said:
Gotcha, I seem to remember being able to temporarily unroot back in the day.
Click to expand...
Click to collapse
there were methods in the past, and there might be methods in the future. it just at this point with lollipop, there isnt any methods yet.
simms22 said:
there were methods in the past, and there might be methods in the future. it just at this point with lollipop, there isnt any methods yet.
Click to expand...
Click to collapse
Got it. That must have been my confusion. Flashed the factory image.
You're right
Right within the SuperSU app, if you go into settings, and scroll all the way down you can go into the option for "Full Unroot." You can also use Wugfresh toolkit to unroot, this will be "permanent" but as soon as you flash 5.01 you can reroot using either adb/fastboot (fastboot boot root.img) or using chainfire auto root or wugfresh.
I used fastboot to flash system then the OTA worked few days later rerooted.
The full unroot method via SuperSU app did not allow the OTA to take.
Related
Have the VZW G2 rooted on the previous OTA update, now starting to see the nag screen to update again.
Last time, I reverted to stock and had to set up everything again from scratch. I needed root so did that but now at the same point again.
Is there an easier way to update, without having to wipe everything and start over again?
TIA
I was rooted and just installed the update. Went through fine and kept root. All my had to do was install/update xposed framework and reboot to get my modules working again. Aside from xposed I had no modified system files and stock recovery. I had not uninstalled any pre-installed apps, just have a few frozen with titanium.
How did you install the update? I tried the OTA path and it gave some hex error after the reboot
wujuyamakin said:
How did you install the update? I tried the OTA path and it gave some hex error after the reboot
Click to expand...
Click to collapse
If you find a solution would you kind enough to share? Ive been delaying my install and when i finally decided to do it, it errors.
wujuyamakin said:
Have the VZW G2 rooted on the previous OTA update, now starting to see the nag screen to update again.
Last time, I reverted to stock and had to set up everything again from scratch. I needed root so did that but now at the same point again.
Is there an easier way to update, without having to wipe everything and start over again?
TIA
Click to expand...
Click to collapse
Other than root, are you stock? If so, should be able to take ota with non issue. If you modded wifi hotspot, need to change it back for ota. Did you also install custom recovery?
wujuyamakin said:
How did you install the update? I tried the OTA path and it gave some hex error after the reboot
Click to expand...
Click to collapse
I didn't have any errors but I have no system files modded.
Thanks mhirsh, you nailed it. I had to restore the stock wifi hotspot app, do OTA update, then do the steps for wifi hotspot again.
It's actually the only root feature I've used for quite a while now. The root uninstallers I've tried have all failed to remove bloatware. I'll be looking at other root benefits to get more use out of it.
And to think I spent days restoring my phone from scratch last update ... lol.
wujuyamakin said:
Thanks mhirsh, you nailed it. I had to restore the stock wifi hotspot app, do OTA update, then do the steps for wifi hotspot again.
It's actually the only root feature I've used for quite a while now. The root uninstallers I've tried have all failed to remove bloatware. I'll be looking at other root benefits to get more use out of it.
And to think I spent days restoring my phone from scratch last update ... lol.
Click to expand...
Click to collapse
I tired this with no success. So i didnt delete my stock wifi hotspots (apk and odex) just renamed them. I removed my modded one and switched back to original names, rebooted, downloaded ota and it errored when it tried to install. Am i missing a step? Thanks in advance
lg g2 Verizon ota update with twrp
I have tried to do the ota Verizon update and get stuck in twrp . It won't reboot after that. I found the commands to get it to reboot on this site but it won't do the update. I'm new to all of this and still learning . please help me figure this out. Thanks
wrayzor71 said:
I have tried to do the ota Verizon update and get stuck in twrp . It won't reboot after that. I found the commands to get it to reboot on this site but it won't do the update. I'm new to all of this and still learning . please help me figure this out. Thanks
Click to expand...
Click to collapse
I couldn't get the OTA update to work until I went back to stock and unrooted. I was rooted with stock except I had performed the audio mod and the tethering mod which modified system files. Once I unrooted and factory reset to stock everything updated fine. haven't rooted again yet kind of waiting for stock lollipop OTA update to show up soon.
wrayzor71 said:
I have tried to do the ota Verizon update and get stuck in twrp . It won't reboot after that. I found the commands to get it to reboot on this site but it won't do the update. I'm new to all of this and still learning . please help me figure this out. Thanks
Click to expand...
Click to collapse
TheJuicer said:
I couldn't get the OTA update to work until I went back to stock and unrooted. I was rooted with stock except I had performed the audio mod and the tethering mod which modified system files. Once I unrooted and factory reset to stock everything updated fine. haven't rooted again yet kind of waiting for stock lollipop OTA update to show up soon.
Click to expand...
Click to collapse
You should never attempt OTA unless you are stock (having only root will be ok).
Yeah i had forgotten i had performed those mods after i rooted. Initially i thought i was just stock and rooted. Thankfully pretty easy to go back to stock.
Forgive me if this has been asked before. I did search, but I couldn't seem to find an answer to this.
I have a dev edition model. I really want to root, but have been holding off because there are bugs with the current build of Lollipop and I'm kind of hoping Moto will release a 5.02 update soon to kill the memory leak and other issues. That being said, I have really been itching for root.
If I did root, what would I have to do to this phone to update it to the new version? Would I have to completely return to stock and wipe? Or could I ADB sideload? Seems like I was reading that you can't update at all when you're rooted, even if you disable root.
Without any idea how much longer it'll be before the next update, I'm finding it harder and harder to hold off on root, but I don't want to go through hell to get it back to stock and update it.
Thanks for any help and sorry if this has already been asked.
From what I understand, root is fine. It is installing a custom recovery that will stop you from getting the OTA. You can very easily undo root. As a matter if fact, you can pretty easily reinstall the stock recovery also.
diggitydogg said:
From what I understand, root is fine. It is installing a custom recovery that will stop you from getting the OTA. You can very easily undo root. As a matter if fact, you can pretty easily reinstall the stock recovery also.
Click to expand...
Click to collapse
Thanks for the reply.
Most of the time, that's true. I have updated a lot of phones by simply unrooting, applying the update, and rooting again, or using ADB sideload and then just rooting. But from what I have been reading about the Moto X 2014, you have to completely restore it back to stock before doing anything, even if you just use the temp boot method to root.
Is that wrong? I can't seem to find any info that confirms either way.
I've installed custom recovery, how can I reverse it and install the original recovery for update?
One advantage of root is you'll have Titanium Backup, so even if you do have to do a full wipe before applying the update, you could just update it and restore everything back quickly using TiBu. With lollipop, apparently the update file checks for the entire system checksum as a whole instead of each file so any slight modification to the system will mostly require pure stock and this is the same even with the nexus. So yeah, you most likely have to wipe your device before updating. I'd say, wait till Xposed for Lollipop is out, its almost there, once it comes out go ahead and root it, it'll at least be worth the hassle then
If you're rooted with lollipop and want to take an OTA update you can flash stock recovery and the stock system image. At that point you should still have all apps/data and be able to take a OTA update. The recovery and system files should be the exact version you already have and of course anytime you flash realize you could lose data!
Steve-x said:
If you're rooted with lollipop and want to take an OTA update you can flash stock recovery and the stock system image. At that point you should still have all apps/data and be able to take a OTA update. The recovery and system files should be the exact version you already have and of course anytime you flash realize you could lose data!
Click to expand...
Click to collapse
Right. All you need to do is flash the stock /system partition and also the recovery if you replaced it. I don't know why everyone's talking about having to wipe the entire phone with the all the stock images.
Hey guys. Forgive me for my noobness here, I'm still kind of new to rooting etc. So I've got an Australian nexus 6, running 5.0.1, its rooted, I used the nexus root toolkit, and it installed twrp, I want to update to 5.1, downloaded the update from aosp or whatever and tried to sideload it, I kept getting errors and fails. Both twrp and adb are updated. Now I think from what I've read, after rooting a 5.0 device you can't receive OTAs anymore. I just got the OTA notification, I downloaded it and pressed install, it restarted then booted into twrp and didn't start the update process. I've tried unrooting but it failed. My questions are: can I install the OTA through twrp? Is there a way to bypass twrp to continue the update? Can I factory reset through settings on the phone to go back to stock and then do the update that way? (I've heard its bad to factory reset like that, not sure why or if its true?) Just want 5.1 already! Any help is appreciated, and if possible dumb it down a bit because some terminology still is not known to me
Thanks in advance
ice_cold17 said:
Hey guys. Forgive me for my noobness here, I'm still kind of new to rooting etc. So I've got an Australian nexus 6, running 5.0.1, its rooted, I used the nexus root toolkit, and it installed twrp, I want to update to 5.1, downloaded the update from aosp or whatever and tried to sideload it, I kept getting errors and fails. Both twrp and adb are updated. Now I think from what I've read, after rooting a 5.0 device you can't receive OTAs anymore. I just got the OTA notification, I downloaded it and pressed install, it restarted then booted into twrp and didn't start the update process. I've tried unrooting but it failed. My questions are: can I install the OTA through twrp? Is there a way to bypass twrp to continue the update? Can I factory reset through settings on the phone to go back to stock and then do the update that way? (I've heard its bad to factory reset like that, not sure why or if its true?) Just want 5.1 already! Any help is appreciated, and if possible dumb it down a bit because some terminology still is not known to me
Thanks in advance
Click to expand...
Click to collapse
If you're unlocked, rooted and have TWRP, why not just install custom ROM? Otherwise you can download factory image that you want, unzip and flash images individually via fastboot. Just don't flash user data and you won't loose data.
Just use the toolkit to 100% flash back go stock. It will unroot and reinstall stock recovery. Just remember to always keep USB debugging on and keep that boot loader unlocked. Once your back to the out box state you should be v able to receive ota. Or just use toolkit to flash the new stock image for your device. Ends with I.
Sent from my Nexus 6
I've never flashed files individually. I don't like any of the Roms, I prefer stock android but I like the perks of rooting. Could you give me a step by step on flashing the files individually please
ice_cold17 said:
I've never flashed files individually. I don't like any of the Roms, I prefer stock android but I like the perks of rooting. Could you give me a step by step on flashing the files individually please
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008, method 2.
Awesome thanks, so if I don't flash "user data" I can keep my stuff, will that mess it up in anyway? What about the step that says erase user data, can I skip that then?
ice_cold17 said:
Awesome thanks, so if I don't flash "user data" I can keep my stuff, will that mess it up in anyway? What about the step that says erase user data, can I skip that then?
Click to expand...
Click to collapse
I don`t erase and flash userdata usualy, its good to erase cache and then flash cache cache.img. A data factory reset after the procedure is adviced however for preventing fc`s and such.
So in the end is should wipe anyway? Oh well I was trying to avoid that only as a last resort. It wouldn't even let me unroot through the toolkit for some reason...
I, too, would like to know this. I have looked through many forums and sites to try to find an answer.
My Nexus 6 is:
- bootloader unlocked
- TWRP recovery
- rooted
I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts.
Is there a flashable update.zip that allows the update to 5.1? (I have seen a few, but they usually have encryption disabled - which I believe will cause me to lose my data?)
Would it be easy enough to restore stock recovery and unroot, which would allow me to flash the OTA normally - then just flash TWRP and root again?
How would I go about this?
fubofo said:
I, too, would like to know this. I have looked through many forums and sites to try to find an answer.
My Nexus 6 is:
- bootloader unlocked
- TWRP recovery
- rooted
I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts.
Is there a flashable update.zip that allows the update to 5.1? (I have seen a few, but they usually have encryption disabled - which I believe will cause me to lose my data?)
Would it be easy enough to restore stock recovery and unroot, which would allow me to flash the OTA normally - then just flash TWRP and root again?
How would I go about this?
Click to expand...
Click to collapse
Why not just download the factory image of your choice, then fastboot flash everything but user data. You will keep all your data. Many users go this route. Personally, I like a fresh start that doing a factory reset gives. I backup everything to the cloud and then restore what I need to have on my phone. I mention this because it is recommended to preform a factory reset after installing the images separately. Thus avoiding any boot loops or force closings.
Evolution_Freak said:
Why not just download the factory image of your choice, then fastboot flash everything but user data. You will keep all your data. Many users go this route. Personally, I like a fresh start that doing a factory reset gives. I backup everything to the cloud and then restore what I need to have on my phone. I mention this because it is recommended to preform a factory reset after installing the images separately. Thus avoiding any boot loops or force closings.
Click to expand...
Click to collapse
So do I need to flash all the images?
Can I also leave out the recovery image - or do I flash it and re-flash TWRP after?
Does flashing the OTA (normally) factory reset the device wiping all accounts and setup?
I don't want to perform a factory reset as I use the device for business and have many email accounts, sync accounts, contact accounts and other tweaks that I don't want to have to spend a few days setting up again.
fubofo said:
So do I need to flash all the images?
Can I also leave out the recovery image - or do I flash it and re-flash TWRP after?
Does flashing the OTA (normally) factory reset the device wiping all accounts and setup?
I don't want to perform a factory reset as I use the device for business and have many email accounts, sync accounts, contact accounts and other tweaks that I don't want to have to spend a few days setting up again.
Click to expand...
Click to collapse
I understand, everyone's situation is different. No, an OTA will preserve all your accounts and data. Your best bet in your situation may be to flash stock recovery and remove root. Then you could sideload the OTA. Also, though I don't use or really recommend the use of toolkits, the NRT may have options available for your needs as well. There is a possibility that just removing root and TWRP may still leave traces behind. Enough that the OTA may fail.
Evolution_Freak said:
I understand, everyone's situation is different. No, an OTA will preserve all your accounts and data. Your best bet in your situation may be to flash stock recovery and remove root. Then you could sideload the OTA. Also, though I don't use or really recommend the use of toolkits, the NRT may have options available for your needs as well. There is a possibility that just removing root and TWRP may still leave traces behind. Enough that the OTA may fail.
Click to expand...
Click to collapse
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
fubofo said:
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
Click to expand...
Click to collapse
Relocking the bootloader wipes the device, so you don't want to do that.
What is your ultimate goal? Your absolute ideal situation, once you're updated. Let's learn that and work from there.
fubofo said:
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
Click to expand...
Click to collapse
You don't have to relock your bootloader. That doesn't matter. As for recovery, I believe all you have to do is obtain the proper recovery for the build you are currently running, the fastboot flash it from bootloader.
Look here for more info:
http://forum.xda-developers.com/showthread.php?t=3063857
rootSU said:
Relocking the bootloader wipes the device, so you don't want to do that.
What is your ultimate goal? Your absolute ideal situation, once you're updated. Let's learn that and work from there.
Click to expand...
Click to collapse
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
fubofo said:
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
Click to expand...
Click to collapse
OK, let me ask this, what is your current software? 5.0 or 5.0.1?
fubofo said:
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
Click to expand...
Click to collapse
No. That is not enough information. That is your IMMEDIATE goal. I need to know what is your ULTIMATE goal?
Right now you're rooted with twrp. In order to give you the best advice I need to know your ultimate goal is. Why are you rooted with twrp? Do you need this in the future? Why are you thinking about locking the bootloader
All this has an affect on what method you use.
rootSU said:
No. That is not enough information. That is your IMMEDIATE goal. I need to know what is your ULTIMATE goal?
Right now you're rooted with twrp. In order to give you the best advice I need to know your ultimate goal is. Why are you rooted with twrp? Do you need this in the future? Why are you thinking about locking the bootloader
All this has an affect on what method you use.
Click to expand...
Click to collapse
Thank you sir for helping!
Evolution_Freak said:
You don't have to relock your bootloader. That doesn't matter. As for recovery, I believe all you have to do is obtain the proper recovery for the build you are currently running, the fastboot flash it from bootloader.
Look here for more info:
http://forum.xda-developers.com/showthread.php?t=3063857
Click to expand...
Click to collapse
Thanks @Evolution_Freak I'll give a shot at flashing just the stock recovery, unrooting and trying the OTA
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.
As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.
And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...
And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.
But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know?
I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.
Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?
If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.
Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.
Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.
Rbh50815 said:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
Click to expand...
Click to collapse
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img
You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.
So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!
bluesrph said:
So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!
Click to expand...
Click to collapse
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
saurabh40629 said:
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Click to expand...
Click to collapse
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs
bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Click to expand...
Click to collapse
Dm-verity u can bypass but bootloader one, you can not. Look at the apps, mods section.
bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
You shouldn't try to flash the partial OTAs while you are rooted and have a custom recovery installed. The partial zip will try to make specific changes in the restricted partitions (/system, /boot, /recovery, etc.) related to the update and prior modifications to these files may cause the update to fail and the phone to brick. You can still use the "Update" tab in the Settings menu to download the update though as OOS will detect root and download the full zip of the update for you. Simply flash the full zip in TWRP, wipe cache/dalvik, then flash SuperSU and you're good to go the next time an update rolls out. Updating by this method (rooting immedately after flashing update) will also prevent OOS from replacing TWRP with the stock recovery again. When you download the update, you'll know if it's the full zip if the file is >1 GB (they're usually ~1.4 GB,, whereas the partial zips are a few hundred MB).
Unlocked bootloader warning screen is cannot be removed without relocked and fully resetting (wiping) the phone. DM-verity warning screen can be removed by following this guide. Make sure that you are flashing the correct firmware for you current version of OOS though, flashing the wrong version can brick you phone.