Database Users

OTA updating a rooted nexus 7

Hi, I am new to the android scene and have a few questions.
Just wondering about the procedure for updating a rooted device, specifically the nexus 7. After I receive my nexus 7, I am planning on unlocking the bootloader, flashing CWM, and then rooting the device. I am not planning on using any custom roms. I am just going to be using stock JB.
If in the future I want to do an OTA update, what is the procedure for this?
From my understanding, it seems this is the procedure for doing an OTA update for rooted nexus 7:
1. unroot the device? (how do you unroot the device?). is this necessary?
2. use cwm to flash the stock recovery, because you won't be able to get the OTA with a custom recovery such as CWM. Is that correct?(also, where do you get the stock recovery??)
3. apply the OTA update. root will be gone.
4. flash CWM and re-root the device
And once I have succesfully OTA updated the nexus 7, re-flashed CWM, and re-rooted back the device, will I have to start from scratch (lose all data, settings, apps, etc?). I know unlocking the bootloader will wipe the device, but will the OTA update process require me to start over?
If I am missing any steps or have some things mixed up, please let me know. Also, if I were to use an OTA root keeper, what would the procedure be like or how would it change the procedure I listed above?
Thanks.

Haven't got my Nexus 7 yet but it looks pretty simple according to this thread: http://forum.xda-developers.com/showthread.php?t=1764794
Basically just need to have OTA RootKeeper installed beforehand, then disable signature verification in CWM and patch the OTA update. Then OTA Rootkeeper can restore root.
HTH

Rooted G2, still received OTA update

I have rooted my G2(D802) in stock rom.
Will I still receive Official OTA update?

1. you will, but the device will refuse to install it because it's rooted
2. you will, the device will install it and your phone will only root to recovery (if you have custom recovery)
those are the only scenarios I know of.

csunny95 said:
I have rooted my G2(D802) in stock rom.
Will I still receive Official OTA update?
Click to expand...
Click to collapse
Yes the update can sill show up and after ignoring it a couple of times it will force itself to install and either a)if you have custom recovery you will bootloop and if you were using twrp there is a way to remove update or you will need to go Back to stock, b)if you have modified system, installed xposed or removed bloat it will refuse to install because those are things that can only be done with root and so will give message won't update because it's suspected of rooting and there are ways to make it so that it won't update but I don't remember
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

[Q] Android marshmallow ota update failed.

Last night received an ota update to marshmallow. Size is around 583mb. After finishing the download. It asked me to install now or later. I hit now, and it rebooted and stock recovery opened and installation stated. After a minute it rebooted without any error back to android 5.1.1 it said it there was an error updating and I have to download the ota again.
I haven't flashed custom recovery or rom or any other mods. But have super su installed. No xposed even. I just ran twrp recovery temporarily without flashing to install super su. Bootloader unlocked. Any inputs how to get this fixed?? Battery is about 62%

Lord of Hell said:
Last night received an ota update to marshmallow. Size is around 583mb. After finishing the download. It asked me to install now or later. I hit now, and it rebooted and stock recovery opened and installation stated. After a minute it rebooted without any error back to android 5.1.1 it said it there was an error updating and I have to download the ota again.
I haven't flashed custom recovery or rom or any other mods. But have super su installed. No xposed even. I just ran twrp recovery temporarily without flashing to install super su. Bootloader unlocked. Any inputs how to get this fixed?? Battery is about 62%
Click to expand...
Click to collapse
Try to use the unroot function on SuperSU. If this doesn't work, I guess you'll need to flash the whole stock rom...

Lord of Hell said:
Last night received an ota update to marshmallow. Size is around 583mb. After finishing the download. It asked me to install now or later. I hit now, and it rebooted and stock recovery opened and installation stated. After a minute it rebooted without any error back to android 5.1.1 it said it there was an error updating and I have to download the ota again.
I haven't flashed custom recovery or rom or any other mods. But have super su installed. No xposed even. I just ran twrp recovery temporarily without flashing to install super su. Bootloader unlocked. Any inputs how to get this fixed?? Battery is about 62%
Click to expand...
Click to collapse
Till u r rooted, you can't update normally. Either try u rooting or
Look for the twrp flashable Marshmallow thread instead if you want to install twrp.
Sent from my XT1562 using Tapatalk

Solved
Totemic_tHiRp said:
Try to use the unroot function on SuperSU. If this doesn't work, I guess you'll need to flash the whole stock rom...
Click to expand...
Click to collapse
Unrooted and flashed stock rom from fastboot commands and system status is still Modified. Downloaded OTA update and it installed itself and system turned to Official from Modified.

Lord of Hell said:
Unrooted and flashed stock rom from fastboot commands and system status is still Modified. Downloaded OTA update and it installed itself and system turned to Official from Modified.
Any suggestions?
Click to expand...
Click to collapse
Suggestions on what...?

Chaotic-Entropy said:
Suggestions on what...?
Click to expand...
Click to collapse
Sorry forgot to remove that line while editing.

I am having this problem with may update. Have unlocked bootloader, no root or super su. Have twrp installed.
Will have more details tonight as I get home. I know very little about tech too.

silverhandorder said:
I am having this problem with may update. Have unlocked bootloader, no root or super su. Have twrp installed.
Will have more details tonight as I get home. I know very little about tech too.
Click to expand...
Click to collapse
Flash stock recovery and try installing the update

Unable to Update to 6.0.1 (MTC20F)

I decided to catch up on security patches today and, with any luck, obtain the OTA update for Android N. I performed a full unroot (SuperSU) and blew away TWRP by flashing stock recovery for my current build of 6.0.1 (MTC19X). I have also flashed everything back to stock except user data. My boot loader remains unlocked. Every time I try to get the update to 6.0.1 (MTC20F) OTA, the phone will reboot normally and try to install the update. The little android's antennae wiggle for a minute or two and then it just falls over with the familiar red exclamation mark showing up.
Anyone have any ideas?
Thanks!

Cryptomap said:
I decided to catch up on security patches today and, with any luck, obtain the OTA update for Android N. I performed a full unroot (SuperSU) and blew away TWRP by flashing stock recovery for my current build of 6.0.1 (MTC19X). I have also flashed everything back to stock except user data. My boot loader remains unlocked. Every time I try to get the update to 6.0.1 (MTC20F) OTA, the phone will reboot normally and try to install the update. The little android's antennae wiggle for a minute or two and then it just falls over with the familiar red exclamation mark showing up.
Anyone have any ideas?
Thanks!
Click to expand...
Click to collapse
When you did have root, did you make any system changes? Perhaps installing a mod or something that's still there? OTA will fail if it detects any system changes. If you truly are back to stock, then you can also grab a zip of the OTA and install it via ADB sideload. That's what I did and it worked fine.

ultyrunner said:
When you did have root, did you make any system changes? Perhaps installing a mod or something that's still there? OTA will fail if it detects any system changes. If you truly are back to stock, then you can also grab a zip of the OTA and install it via ADB sideload. That's what I did and it worked fine.
Click to expand...
Click to collapse
When I had root I ran AdAway, Helium and the XPosed framework. Do you think any of those would cause my hiccup?
EDIT: I also had SELinuxModeChanger installed.
Would my best bet be to re-root and uninstall some of those programs that could edit system files?

Cryptomap said:
When I had root I ran AdAway, Helium and the XPosed framework. Do you think any of those would cause my hiccup?
EDIT: I also had SELinuxModeChanger installed.
Would my best bet be to re-root and uninstall some of those programs that could edit system files?
Click to expand...
Click to collapse
You won't be able to take an OTA with Xposed for sure as it changes the system big-time. If you want to test out Nougat before they post the factory image (if ever, ugh), then follow section 14 of this guide to the letter. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You can still flash TWRP and re-root it, but only systemless, and you can also flash a systemless Adaway. Xposed isn't available for Nougat yet, so if you must have that, you're better to wait.

ultyrunner said:
You won't be able to take an OTA with Xposed for sure as it changes the system big-time. If you want to test out Nougat before they post the factory image (if ever, ugh), then follow section 14 of this guide to the letter. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You can still flash TWRP and re-root it, but only systemless, and you can also flash a systemless Adaway. Xposed isn't available for Nougat yet, so if you must have that, you're better to wait.
Click to expand...
Click to collapse
Heisenberg's guides have been incredibly helpful so I'll try that route.
Thanks for the input!

Cryptomap said:
Heisenberg's guides have been incredibly helpful so I'll try that route.
Thanks for the input!
Click to expand...
Click to collapse
No problem. The thanks button does that too ... Seriously though, you have to be 'completely' stock to take an OTA, thus why I await the factory images with baited breath.

updating to latest OTA 11.0.1.1.IN11AA

I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.

cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
Update using local, dont reboot - go to magisk; install to inactive slot(after OTA) *disable module to be safe - Then restart

cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it

dladz said:
If you're on ob3 I read that it needs to wipe, if you're on 11.0.0 stable then just update, don't reboot, disable magisk modules, patch after OTA in magisk and that's it
Click to expand...
Click to collapse
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?

cubeplayer1 said:
Sounds easy enough. Should I also worry about flashing back to stock kernel as well?
Click to expand...
Click to collapse
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?

I'm rooted with an unlocked bootloader on 11.IN11AA (Global). How do I perform a local upgrade without the OTA file to put into the root folder? It seems like the Global version of the OTA file is nowhere to be found and I can't download it via System Update since it fails due to root. Do we need to just wait for the 11.0.1.1.IN11AA OTA zip file to be posted? Thanks in advance.

Yes, looks like we are in waiting mode for it to show up...

dladz said:
If you update then the kernel gets done too.
If you have modules installed disable them first.
You'll be fine.
PS: so are you on ob3 or 11 stable?
Click to expand...
Click to collapse
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.

cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
You'd have to install locally even with oxygen updater.

galaxys said:
Yes, looks like we are in waiting mode for it to show up...
Click to expand...
Click to collapse
Yea I guess that's why Oxygen Updater isn't showing anything new for me. Once it shows up on the internet, I'm sure the OU app will refresh and show an available update.

cubeplayer1 said:
I have unlocked bootloader + root with magisk. Is there anything special I need to do before letting the OTA update? What about afterwards, will I need to re root?
Sorry if this question was already asked and answered- I couldn't find anything. Just want to make sure I'm not doing anything stupid, thanks in advance.
For clarity I'm on the latest magisk canary and am using a U.S. phone.
Click to expand...
Click to collapse
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.

cubeplayer1 said:
Stable. Haven't done the update yet because I'm getting "installation problem" when I try to download OTA. Oxygen updater not working either. Not sure what's up lol but I'm over it. Guess I gotta go find the file and install locally.
Click to expand...
Click to collapse
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).

dlhxr said:
For those with trouble installing 11.0.1.1 AA update with root as Google server only pushed incremental OTA at the moment.
1. Flash your current version unpatched boot.img into both slots in fastboot
2. Use the following command to boot from a patched boot, but not modifying the partitions. (fastboot boot patched.img)
3. Update with system updater with incremental ota.
4. Don't reboot, but flash the magisk with magisk app to the inactive slot.
5. Reboot and done.
Click to expand...
Click to collapse
Thanks for these steps, it worked for me. After I flashed Magisk via the Magisk App to the inactive slot, I rebooted and had the latest version installed with root preserved. :highfive:

After I did it I'm getting the com.android.phone stopping and my Sims aren't recognized. I cleared cache, phone and SIM toolkit but didn't work. Grrrrr

I'm a rooted global user and update has never showed until today. It was only 405mb and Google play services was showing the update. Oxygen updater shows nothing and system update shows nothing. I'm gonna wait to see what happens since it's not a full update

Same here global 406 mb ota. It's like not recognizing we have root...

bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
Good looking out bro, that worked a charm. :good:

bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
^^^^^^This -- easiest and fastest root upgrade I have ever done on any device.
Magisk is now built to do it this way.

bouchigo said:
I just updated and kept root. I used to use this method on my Pixel 2 XL when I didn't want to flash the images, or was away from my PC.
Method: https://tinyurl.com/y2bxeuq5
The link should work now.
Disregard the TWRP part (skip Step 4....go from Step 3 to Step 5).
Click to expand...
Click to collapse
This worked for me as well taking the actual partial OTA update from system update and going through the steps in Magisk.
A little nerve wracking considering the many times trying to update has failed on my last couple OP devices, but at least this time, it worked.
Thanks.

anyone have a patched magisk boot for IN2025?
I did the steps of flashing the stock boot.img, then booting the patched img, installed the OTA, used magisk to patch before reboot, but when it rebooted it said installation failed, and i was unable to access magisk after that as it was on the wrong slot... I had to apply the OTA update again, and now am stick without root
IN short, need either a stock IN2025 boot image to patch myself, or a magisk patched one...
TIA