Database Users

[Q] Wont root after manual update?

I just pushed the new 4.2 update via adb,
I then tried re-rooting as I lost root in the project.
I used WugFreshs at first, which said successful. I tried root check and titanium backup which both said no root access.
I then tried mikes toolkit and chose root and install busybox, all that wen through great and said successful, so I retried Tibackup and rootchecker again, both were denied root access.
This time round, rootcheck said "System Running Slow" whilst checking for root access.
What should I do?
Re-boot into recovery and clear cache etc?
Factory reset?
Both?
For some reason superuser is installed not supersu if that makes a difference?
Any help appreciated.

Wilks3y said:
I just pushed the new 4.2 update via adb,
I then tried re-rooting as I lost root in the project.
I used WugFreshs at first, which said successful. I tried root check and titanium backup which both said no root access.
I then tried mikes toolkit and chose root and install busybox, all that wen through great and said successful, so I retried Tibackup and rootchecker again, both were denied root access.
This time round, rootcheck said "System Running Slow" whilst checking for root access.
What should I do?
Re-boot into recovery and clear cache etc?
Factory reset?
Both?
For some reason superuser is installed not supersu if that makes a difference?
Any help appreciated.
Click to expand...
Click to collapse
I apply the update by doing fresh install:
-always backup your data
Then I use wug's nexus root toolkit:
-flash stock + unroot 4.1.2 jzo54k
-flash zip stock + unroot 4.2 jop40c
-change the model type to "NAKASI: Android *.*.* Any build"
-apply root

gesitkumara said:
I apply the update by doing fresh install:
-always backup your data
Then I use wug's nexus root toolkit:
-flash stock + unroot 4.1.2 jzo54k
-flash zip stock + unroot 4.2 jop40c
-change the model type to "NAKASI: Android *.*.* Any build"
-apply root
Click to expand...
Click to collapse
I applied the update over the top of 4.1.2, wiped cache and then restarted.
I then used Wug's toolkit to root, which didn't work.
So I tried Mikes, which also didnt work.
Both report the Root as being succesful, but they arent.
If I change the model to all types on Wug's, would that make a difference?
Is it worth trying a manual root?

I use the Google Nexus 7 Toolkit which was great in fixing the problems after upgrade. Flashing the previous version bootloader (I think that is what it was) solved the root problem. The hints and guidance in this application are great and have always solved my problems. No offence meant to Wug here, I just find the other application suits me better.
Sent using Tapatalk 2

Waxwrong said:
I use the Google Nexus 7 Toolkit which was great in fixing the problems after upgrade. Flashing the previous version bootloader (I think that is what it was) solved the root problem. The hints and guidance in this application are great and have always solved my problems. No offence meant to Wug here, I just find the other application suits me better.
Sent using Tapatalk 2
Click to expand...
Click to collapse
As already said, both Toolkits have been attempted and both report that its rooted, but my device tells me otherwize, as do Titanium Backup.
Can someone just give me a step by step for what I should do to gain Root again?!

Wilks3y said:
As already said, both Toolkits have been attempted and both report that its rooted, but my device tells me otherwize, as do Titanium Backup.
Can someone just give me a step by step for what I should do to gain Root again?!
Click to expand...
Click to collapse
Hi, are you using the fully updated version of Toolkit (updated to include the 4.2 stuff. When I did mine I was told to go ahead but if it didn't work the next step was to flash the 4.1 bootloader? as it was compatible with 4.2
The root with the 4.2 bootloader didn't give me root so I flashed the 4.1 bootloader and rooted again. This was successful for me. The Toolkit application gives you step by step instructions as you request as long as it is updated to do 4.2 and follow the advice you should have no problem.
I don't think you can do the full updates in the application unless you are a donater. If I remember correctly you cannot update the application unless you use the donater version. The update for 4.2 came out at almost the same time as 4.2 was being pushed to devices.
You sound cluey enough to know you must use USB debugging but many users don't realise this or the tapping on the build trick to get the developer options available so you can select USB debugging.
Sent using Tapatalk 2

Waxwrong said:
Hi, are you using the fully updated version of Toolkit (updated to include the 4.2 stuff. When I did mine I was told to go ahead but if it didn't work the next step was to flash the 4.1 bootloader? as it was compatible with 4.2
The root with the 4.2 bootloader didn't give me root so I flashed the 4.1 bootloader and rooted again. This was successful for me. The Toolkit application gives you step by step instructions as you request as long as it is updated to do 4.2 and follow the advice you should have no problem.
I don't think you can do the full updates in the application unless you are a donater. If I remember correctly you cannot update the application donate version. The update for 4.2 came out at almost the same time as 4.2 was being pushed to devices.
You sound cluey enough to know you must use USB debugging but many users don't realise this or the tapping on the build trick to get the developer options available so you can select USB debugging.
Sent using Tapatalk 2
Click to expand...
Click to collapse
Hey mate, thanks for your reply !
I downloaded both ToolKits yesterday, so I'm guessing they are the newly updated ones?
Yes my tablet has usb debugging enabled, and is put into the Camera Mode.
I will have another go tonight, and try a different way, including using the "All Models" choice you mentioned.
If this doens't work, whereabouts in the ToolKit(Wug's) if the option to downgrade HBOOT in order to try the Root method you attempted which was successful.
Again, thanks mate !

Wilks3y said:
Hey mate, thanks for your reply !
I downloaded both ToolKits yesterday, so I'm guessing they are the newly updated ones?
Yes my tablet has usb debugging enabled, and is put into the Camera Mode.
I will have another go tonight, and try a different way, including using the "All Models" choice you mentioned.
If this doens't work, whereabouts in the ToolKit(Wug's) if the option to downgrade HBOOT in order to try the Root method you attempted which was successful.
Again, thanks mate !
Click to expand...
Click to collapse
I don't use Rug's Toolkit but Mike's Toolkit (only because it is easier to follow and use because it tells you what to do at all stages). You can see if it is updated by checking whether it has functions for 4.2 - I always use it for flashing the latest roms as well as the unlocking, root, recovery, etc, all of which the Toolkit guides you through. It even downloads the roms for you.
My only question is why did you put it in camera mode, change it back.
Sent using Tapatalk 2

Just install the 4.2 that is already Stock rooted, de-odexed apps.
Install the ROM as already Stock rooted, de-odexed apps.
Here is the link for the download: http://www.scottsroms.com/downloads.php?do=file&id=288
Thanks to Scott's post http://forum.xda-developers.com/showthread.php?t=1991157

[Q] Updated to 4.2.2 and lost my custom recovery

I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.

moose&beer said:
I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.
Click to expand...
Click to collapse
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.

sfobrien said:
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.
Click to expand...
Click to collapse
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.

I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.

sfobrien said:
I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.
Click to expand...
Click to collapse
No worries. And yeah, I did the OTA, but held off until Google pushed a notification to my N10 for the update. I'll give goomanager a try. Appreciate the replies. Thanks.

This is normal behaviour in a OTA update. Installs a couple of files that, if a custom recovery is installed, reflash stock recovery on reboot. This doesn't happen if you flash a factory image.
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app

three west said:
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.
Click to expand...
Click to collapse
Thanks - I'll give goomanager a try.

beekay201 said:
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I assumed the same, but I got the same situation as OP, I'll try reinstalling TWRP using Nexus Root Toolkit, or does goomanager have a special functionality for those conditions?
Update: Used NRT to install TWRP in the advanced settings, worked beautifully.

The latest Google OTA's are not successfully installing unless you restore stock recovery fist and some are failing if you are rooted as well.
Best bet if you are running as rooted or custom recovery is to backup first, un-root, restore stock then sideload the OTA. This will save you lots of frustration and heartburn.
It's easy enough to restore stock and to re-root so just make it part of your ota routine.

[Q] Lost TWRP and root - Help needed

Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.

Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
tigas68 said:
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Click to expand...
Click to collapse

spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
thanks. :good:

tigas68 said:
thanks. :good:
Click to expand...
Click to collapse
Still isn't working...
When i tried to fastboot the recovery img the device turns off and never turns on again on is own!
Help please!
I like my root...!

here's the screens of waht happens.
This his what happens when i try to go into recovery mode...

first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip

I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.

zephiK said:
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
Click to expand...
Click to collapse
zephiK,
Already done that! I flashed the CWM recovery throught fastboot. The device turned off. When i turn it on again and tried to go into recovery mode, so i can flash the SU from chain fire, but got the image on my post!
The phone is unlocked!

That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!

Johnsonyc said:
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
Click to expand...
Click to collapse
I used the sctock rom downloaded from the google developers website!

Johnsonyc said:
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Click to expand...
Click to collapse
What he said. The recovery flash isn't going through.
Sent from my Nexus 4 using Tapatalk 4 Beta

Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world

spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.

kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.

kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Johnsonyc said:
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
Click to expand...
Click to collapse
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:

sn0warmy said:
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
Click to expand...
Click to collapse
I don't even really use root explorer anymore just like having the ability to make nandroid backups. But after doing a clean install of 4.3 in fastboot and it only took 30 minutes from start to finish including app and data restores nandroids to me are not that useful anymore (I don't flash custom ROMs anymore). Google automatically re-installed all my apps as soon as I reconfigured my WIFI, they also restored my APN and my work WIFI settings but not Bluetooth. And I used Helium to restore the user app data and all my texts and helium doesn't need root access to work.
Here is the start of Koush's post on Google+ where he talks about superuser on 4.3.
I finally had a chance to dig into seeing why Superuser is broken on Android 4.3. https://android.googlesource.com/platform/dalvik/+/9907ca3cb8982063a846426ad3bdf3f90e3b87c2
Basically /system is mounted as nosuid to any zygote spawned process (ie, all Android apps). Root will still continue to work via adb shell, etc.
This is a pretty nasty change. It seems that SuperSU works around this by replacing install-recovery.sh to run a su daemon that pipes subsequent through it. Pretty hacky, but understandable why it was done this way.
Will need to look into how to do this in a less invasive fashion, if that is even possible. Of course, if building from source, this change can simply be reverted.

Here's a better explanation about superuser from Android Police.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/

Rooting for me is used for restoring my apps and stuffs using titanium backup. Another useful thing about rooting is the ability to check saved wifi passwords.

Just install twrp from fastboot and then flash the su zip file in twrp
Sent from my Nexus 4 using Tapatalk 2

EddyOS said:
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
Click to expand...
Click to collapse
@EddyOS
Your answer is what forums are not about! Instead of helping you had an atitude of an ass...!
@ Everyone else
After 5 or 6 attemps, doing it by the book, the CWD worked and i now have a Recovery mode! I didn´t did anything different, so i couldn´t really understand what went wrong before... SU from chainfire works perfectly! It´s now Rooted! And yes, the tuturials are idiot proof!
There´s something that´s bothering my mind... I can´t unistall some trash that cames with the 4.3 version using titanium backup, because he can´t find the apk files...! I could do it with the 4.2.2 version, but not with this one. I'm using the deoxed version.
Does anyone has the same problems?

[Q] Help with lost root after 4.3 OTA update

Got a question. I lost root after the 4.3 ota update. Is it possible to get it back without losing everything on the tablet again? I was running SuperSU and OTARootkeeper at the time. When I got into OTARootkeeper is says the su file is there, but when I click restore root it seems not to be able to. I am not a super power user. I used WUGs tookkit to unlock it and root it in the first place. Also does this mean I lost unlock also?
Thanks!

I was in the same situation after installing the update through custom recovery. I remained unlocked. I used Wugs toolkit to root and install custom recovery (TWRP). In recovery I installed Chainfire's updated SuperSu zip. After booting back up, I had root and custom recovery. Search for SuperSu v1.43.

Groid said:
I was in the same situation after installing the update through custom recovery. I remained unlocked. I used Wugs toolkit to root and install custom recovery (TWRP). In recovery I installed Chainfire's updated SuperSu zip. After booting back up, I had root and custom recovery. Search for SuperSu v1.43.
Click to expand...
Click to collapse
Did you lose any data?

xzb6np said:
Did you lose any data?
Click to expand...
Click to collapse
No, you do not lose data after flashing a recovery. Chainfire leased SuperSU 1.5 today.

Username invalid said:
No, you do not lose data after flashing a recovery. Chainfire leased SuperSU 1.5 today.
Click to expand...
Click to collapse
Flashed 4.3 and lost root. I have downloaded the latest SU to my N7 and how am unsure how to go about flashing the ZIP since I no longer have access to custom recovery.

it worked
Username invalid said:
No, you do not lose data after flashing a recovery. Chainfire leased SuperSU 1.5 today.
Click to expand...
Click to collapse
Ok opened up Wugs Nexus Root toolkit. Let it update everything it wanted to and then then told it to root. I was indeed still unlocked and it went ahead and reestablished root without losing anything. I updated OTA RootKeeper afterward and all seems happy.
Thanks!

killswitch11 said:
Flashed 4.3 and lost root. I have downloaded the latest SU to my N7 and how am unsure how to go about flashing the ZIP since I no longer have access to custom recovery.
Click to expand...
Click to collapse
Flash the TWRP image via fastboot. Either with a toolkit or manually.

xzb6np said:
Did you lose any data?
Click to expand...
Click to collapse
As username is invalid posted, no you do not lose data by that method. At least, I lost no data.

Groid said:
As username is invalid posted, no you do not lose data by that method. At least, I lost no data.
Click to expand...
Click to collapse
You only lose data if you lock/unlock bootloader or wipe it yourself
Sent from my Nexus 7 using XDA Premium HD app

OK got one crazy issue. I root but sometimes I lose it and have to reboot to get it back. SuperSu can't write the binary. Every time I open it it wants to write the binary but can't seem to. After a reboot Otarootkeeper say root is there. Then later it will be gone and I have to reboot to get it back.
Sent from my Nexus 7 using XDA Premium HD app

xzb6np said:
OK got one crazy issue. I root but sometimes I lose it and have to reboot to get it back. SuperSu can't write the binary. Every time I open it it wants to write the binary but can't seem to. After a reboot Otarootkeeper say root is there. Then later it will be gone and I have to reboot to get it back.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I have the same issue, used Wugfreshs Toolkit to root after 4.3, on reboot i have no root.

Update OTA with root and TWRP

I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?

ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!

ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433

ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
You must do the following:
1. Return to complete stock - that means get rid of root and TWRP. Best way to do that is download the factory image from Google, extract the boot, recovery, and system images from the factory image, and Flash those, for example: fastboot flash recovery recovery.img Don't flash data.img so you can keep your data.
2. OTAs depend on stock recovery to load, so now that you're back to stock, you have 2 choices. You can simply boot your phone normally, wait for the notification for the update, install it, and you're done - or, you can access android's stock recovery and side load the OTA zip using ADB. Good luck
Sent from my Nexus 6P using Tapatalk

Gamer_Josh said:
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!
Click to expand...
Click to collapse
I forgot to mention that I also had TWRP recovery installed. The result was like it is with a normal OTA update, as none of my data/apps/settings were affected. Worked like a charm!

DJBhardwaj said:
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.

ponzi314 said:
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.
Click to expand...
Click to collapse
You are sure that you used the correct OTA file?

DJBhardwaj said:
You are sure that you used the correct OTA file?
Click to expand...
Click to collapse
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3

ponzi314 said:
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
Click to expand...
Click to collapse
That's weird. It has worked for me everytime, and most users here.

DJBhardwaj said:
That's weird. It has worked for me everytime, and most users here.
Click to expand...
Click to collapse
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.

tech_head said:
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.
Click to expand...
Click to collapse
Sideloading the update, right?

DJBhardwaj said:
Sideloading the update, right?
Click to expand...
Click to collapse
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.

tech_head said:
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.
Click to expand...
Click to collapse
I also avoid using any toolkits. Yes I know they are fast and easy, and of course someone's hardwork. But I like to everything manual, same as you. :highfive:

I usually like to do things like that manually, because I like to know how things work. But I was under a bit of a time crunch at that point, so decided to try the Nexus Root Toolkit. Though I do understand the procedure of sideloading OTA updates via ADB, from researching and reading on the forums here.
Anywho, I hope you are able to get it going OP.

The OTA fixed it for me, thank you so much!