Develop Bugs

OTA After I Root?

Will i be able to apply the ota after i root my device i dont want to brick it or loose root?
Thankyou in advance

garner said:
Will i be able to apply the ota after i root my device i donty want to brick it or loose root?
Thankyou in advance
Click to expand...
Click to collapse
Yes but you'll need too root again after I believe.

recklesslife85 said:
Yes but you'll need too root again after I believe.
Click to expand...
Click to collapse
thanks for your reply hope it wont brick the device!

garner said:
thanks for your reply hope it wont brick the device!
Click to expand...
Click to collapse
It won't.
The OTA's come in one of two ways. An incremental package (where it updates from Revision X to revision Y and a full package).
The full package is a full ROM - it wipes /system and pushes everything.
The incremental update is much smaller and patches existing files. This is what you'll be getting. In order to do this the OTA does an assert on every file it wants to patch and makes sure that it hashes out to its expected value. If the hashed value does not match the expected value the update WILL NOT APPLY. You'll get error(7) and it will tell you which assert failed.
So, if you root and don't change anything in /system, flash a new kernel, use an insecure boot image then you'll be able to apply the OTA fine. You will need to fix the permissions on the su binary though as it will recursively chmod /system (su will still be there but with the wrong permissions). Flash the su update package again though and you'll be fine.

krohnjw said:
It won't.
The OTA's come in one of two ways. An incremental package (where it updates from Revision X to revision Y and a full package).
The full package is a full ROM - it wipes /system and pushes everything.
The incremental update is much smaller and patches existing files. This is what you'll be getting. In order to do this the OTA does an assert on every file it wants to patch and makes sure that it hashes out to its expected value. If the hashed value does not match the expected value the update WILL NOT APPLY. You'll get error(7) and it will tell you which assert failed.
So, if you root and don't change anything in /system, flash a new kernel, use an insecure boot image then you'll be able to apply the OTA fine. You will need to fix the permissions on the su binary though as it will recursively chmod /system (su will still be there but with the wrong permissions). Flash the su update package again though and you'll be fine.
Click to expand...
Click to collapse
Thankyou for clearing that up with me, i might just wait till after the ota release then do it

krohnjw said:
It won't.
The OTA's come in one of two ways. An incremental package (where it updates from Revision X to revision Y and a full package).
The full package is a full ROM - it wipes /system and pushes everything.
The incremental update is much smaller and patches existing files. This is what you'll be getting. In order to do this the OTA does an assert on every file it wants to patch and makes sure that it hashes out to its expected value. If the hashed value does not match the expected value the update WILL NOT APPLY. You'll get error(7) and it will tell you which assert failed.
So, if you root and don't change anything in /system, flash a new kernel, use an insecure boot image then you'll be able to apply the OTA fine. You will need to fix the permissions on the su binary though as it will recursively chmod /system (su will still be there but with the wrong permissions). Flash the su update package again though and you'll be fine.
Click to expand...
Click to collapse
what if I just unlock the bootloader and leave everything else the way it is?

rock7632 said:
what if I just unlock the bootloader and leave everything else the way it is?
Click to expand...
Click to collapse
You'll have no problems.

krohnjw said:
You'll have no problems.
Click to expand...
Click to collapse
cool, thanks. I plan on unlocking the bootloader as soon as I get the phone

I followed the directions to unlock the bootloader and root that are posted in the development forum.
Today I decided to try the OTA update.
It reboots to install it, tries to for a very short time and then goes to the picture of an android with an exclamation point. No Idea why, so I'll probably just go a different route.

I don't think mine did that. I was unlocked + rooted (but no CWM flashed or anything) - it rebooted to apply the update, I got a little progress bar for a minute and then it was done.

Restore Root after OTA
Hi,
Can anyone please help with guidance on how to restore root after an OTA update? Running stock ICS ROM (unlocked bootloader) and rooted using Superboot R3.
Can I just simly run the superboot again to root the device?
Thanks,
SAM

jasbur17 said:
I followed the directions to unlock the bootloader and root that are posted in the development forum.
Today I decided to try the OTA update.
It reboots to install it, tries to for a very short time and then goes to the picture of an android with an exclamation point. No Idea why, so I'll probably just go a different route.
Click to expand...
Click to collapse
This is exactly what mine did last night, (found the update from O2) now it wont see the update again ?
What do i need to do to get the update again ? and why didnt it work the 1st time ?

sidhaarthm said:
Hi,
Can anyone please help with guidance on how to restore root after an OTA update? Running stock ICS ROM (unlocked bootloader) and rooted using Superboot R3.
Can I just simly run the superboot again to root the device?
Thanks,
SAM
Click to expand...
Click to collapse
A little bump as I'm looking for the same answer, could anyone help me on this one please
Sorry, ignore my question, found out the answer in the superboot guide. Thanks!

Yes, just run the root batch file again.

r3k0 said:
This is exactly what mine did last night, (found the update from O2) now it wont see the update again ?
What do i need to do to get the update again ? and why didnt it work the 1st time ?
Click to expand...
Click to collapse
Do you have clockwork recovery installed?
I think that OTA fails if you have an alternative recovery.
I have root and unlocked bootloader, i flashed the original recovery over clockwork one...let's wait and see if OTA apply succesfully.

lesilent said:
Do you have clockwork recovery installed?
I think that OTA fails if you have an alternative recovery.
I have root and unlocked bootloader, i flashed the original recovery over clockwork one...let's wait and see if OTA apply succesfully.
Click to expand...
Click to collapse
The OTA update zip should get downloaded to /cache. You can then use CWM recovery to flash that if you don't want to revert to stock recovery.

Does rooting only removes the ability for OTA updates?

Hey guys just received my n7 yesterday and am very pleased with this, however I have some questions.
Does rooting (only) removes your OTA updates access? I also own a Galaxy S4 (rooted) and I can't get OTA, it says it's modified, but I did flash a custom update on it and kernel. So if I just root my n7, and not flash anything, I will still get OTA's correct? I just want to use some apps which requires root access and not planning to flash a custom rooms or anything. Thanks for any help.
Sent from my Nexus 7 using Tapatalk 4

Mine is always rooted, and I get all OTAs.
Sent from my Nexus 7 using xda app-developers app

You just need to have the stock recovery to receive OTAs.

Username invalid said:
You just need to have the stock recovery to receive OTAs.
Click to expand...
Click to collapse
So if I have twrp installed, i won't receive them?
Sent from my Nexus 7 using Tapatalk 4

Takes 10 seconds to reflash the stock recovery.

UPDATE: SuperSU-v1.55 added the fix for the OTA update issue, so this post is no longer necessary unless you are using an older version of SuperSU
This post also applies to JSS15Q update.
I actually went through and tested JWR66N rooted with SuperSU and the JSS15J OTA update. I expected it to work but it exited with an error.
Ironically the JSS15J OTA actually did patch every single file successfully but near the end while setting permissions, it came up with an error, so after reboot you'll actually be running with all JSS15J rom files, except your build will still say JWR66N, you'll still be running the JWR66N recovery, and you'll still be running the 3.05 bootloader.
I tracked down the issue and put together a fix for it. If you want, it is attached to this post. You just run it after installing SuperSU, so basically:
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip (SuperSU v1.55 or greater incorporates the OTA fix)
install UPDATE-SuperSU-v1.55.zip
install UPDATE-SuperSU-ota.zip (can be chain installed, just make sure you choose to install it 2nd)
reboot
You'll need to redo these steps (both the installs) after you receive the OTA to preserve root and ability to receive future OTAs.
Also as others have mentioned it is best to be running stock recovery (which the above commands will allow you to do because twrp is never flashed on the tablet) I've attached the stock recovery for JSS15J in case someone needs it.
If you make ANY modifications or delete files from the stock ROM with your new root privileges, then you will greatly increase the chances of the OTA failing. Adding new files is normally fine.

Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Sent from my Nexus 7 using xda app-developers app

rmm200 said:
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Click to expand...
Click to collapse
On some platforms, especially when flashing bootloaders and/or radios, the stock recovery pulls some funky maneuvers to get that done. Often custom recoveries are not privy to those maneuvers. Also sometimes custom recoveries will experiment with custom kernels which don't always have the bootloader and/or radio devices mapped the same as the stock kernel. This can lead to problems to.
Thus it is safest to use stock recovery to flash OTAs.
I have flashed the complete JSS15J OTA except for the bootloader part using TWRP and it works ok. All the ROM files are patched.
I just didn't feel like risking my tablet with the bootloader flash portion of JSS15J OTA using twrp. It might work fine. I just know from the past the potential for issues are higher in that section of the OTA flash.

Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?

It was common on other platforms I've used, but I don't know about here.

Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically). I have been installing OTA updates on rooted Nexus devices with custom recoveries since the Nexus One, and assuming the new Nexus 7 works the same way, the following applies:
If you are running stock ROM, your deivce will receive the notification and download the update, even if rooted
If you are running stock recovery, the update will install automatically as normal
If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
If you have modified files in /system, the OTA update is pretty much guaranteed to fail regardless of which recovery you use
If you successfully install the OTA update, you will no longer have root, so flash SuperSU using a custom recovery after the OTA update installs
Also:
You can always look for the OTA zip URLs on XDA and just download the update yourself to flash if you don't want to wait for it to come to your device (this is what I always do)
You can flash factory images instead of the update, without losing data (see other threads for how)
If you want to keep stock recovery installed, you can always use fastboot to boot a custom recovery without flashing it, in case you ever need it
The above is accurate and correct as far as I'm aware from my own experience over the years with Nexus devices. I'm sure someone will be happy to correct me if anything is wrong Hope this helps.

phazerorg said:
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically).
Click to expand...
Click to collapse
I thought the same about root not blocking the OTA update install from being successful, but that was with years of using superuser.
With SuperSU (I am not sure which version introduced it) they set the immutable flag on a file in almost every OTA. I believe this is to support some OTA survival mode. This causes the OTA to fail in the section where it sets permissions. All the files are patched at that point, but the build.prop hasn't been modified to reflect the new version # and the bootloader and recovery haven't been flash.
You'll essentially be running JSS15J but your software will report it is on JWR66N, your bootloader wouldn't have been patched, and you would be running JWR66N recovery.

TheAltruistic said:
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
Click to expand...
Click to collapse
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2

nolook said:
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
Click to expand...
Click to collapse
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.

Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
Titanium backup is an app, I assume with files he is targeting e. G. Config files.
Sent from my Nexus 7 (2013)

Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
It means don't modify or delete any files in /system
Don't remove a system app that shipped with the tablet. You can install a new version as that just hides the one in /system, but if you remove or modify the original, then the OTA will very likely fail (depending on how complex the OTA is)
Adding files is ok.

Alright, so here's my scenario. Hopefully someone can tell me what should happen:
I am running the stock ROM on my Nexus 7 (2013), but I have ClockWorkMod Recovery installed and I'm using Koush's Superuser app for root permissions. The only system file that I think I have changed is my hosts file because of Adaway. That is easily reverted, though.
So can I just download the OTA, install it manually from the custom recovery (flashing the update.zip file), and then re-flash Koush's superuser app back onto the device?
Will that go smoothly, and will the newer build number be accurately reflected in my About Phone afterward?
(that last part is just my OCD talking)

phazerorg said:
:
[*]If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
Click to expand...
Click to collapse
This was very helpful, and this is the category i fall in. However, i have installed a kernel. does that change anything?
So basically what you are saying is this, with my current set up:
1 - i will get the update, it will download, but wont install. I should boot into TWRP and install the file that way. Correct? Where is the downloaded file stores?
2 - I can just wait for the download to be posted on here, and just install via twrp.
3 - either way, after installing it, i will lose root. I should then boot into twrp and flash supersu.
Correct?

Theoretically it could work. I believe the flash has worked with twrp.
Personally I always put stock recovery back to flash ota's though especially if there is a bootloader (or radio if you have a mobile version) because on some platforms they involve special procedures that may not be in the custom recovery.
On nexus it looks like it will work with custom recovery but it takes so little effort to put stock recovery back I just do it automatically.
Having said that, I've seen one person post it worked on twrp but haven't read an experience on cwm. Not saying it will or won't work.

If we are running the stock ROM, but have it rooted with the custom recovery, why cant we just use Wegfresh's nexus toolkit to Unroot and image using the updated IMG file?
Then go through and use it to recreate the root\custom recovery again?

[Q] OTA JSS15R While Rooted

Currently trying to update my Nexus 7 to JSS15R (8MB OTA that may have helped multitouch issue?)
I am running rooted stock ROM, unlocked bootloader etc. Current build number is JSS15Q.
I've heard the newer versions of SuperSU have the OTA fix built in. I haven't been able to update though. I noticed there was an update and I went to update my Nexus 7. It went to update like it should, but I got an error and it never changed.
Flashed the OTA fix thinking it would help. No.
Forced OTA update by stopping Google Framework. No.
Flashed SuperSU 1.65 and tried to update again. No.
Any suggestions on what I should do? Manually flash the update without loosing root or an data?

Did you reflash the ota after you flashed supersu?
What was the error message?

sfhub said:
Did you reflash the ota after you flashed supersu?
What was the error message?
Click to expand...
Click to collapse
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.

When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.

church said:
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
Click to expand...
Click to collapse
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.

datallboy said:
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
Click to expand...
Click to collapse
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.

church said:
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
Click to expand...
Click to collapse
I found a zip for the ota update, don't remember where, but should I be able just to flash it with TWRP without loosing anything?

It will lose the option to blend milkshakes

church said:
It will lose the option to blend milkshakes
Click to expand...
Click to collapse
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.

Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.

church said:
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
Click to expand...
Click to collapse
Stock recovery is on my device. I'm temporarily booting TWRP with the Nexus Toolkit so I can flash things.

datallboy said:
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
Click to expand...
Click to collapse
Next time you have an error with stock recovery (android fallen down) press/hold power, then press/release VolUp, then release Power.
This will show you the error log.
As to your current problem, if your unit won't download and notify you about JSS15R download it by hand and place in your virtual sdcard, then temporary boot into tarp and choose install, selecting the ota zip.
---------- Post added at 08:58 PM ---------- Previous post was at 08:55 PM ----------
datallboy said:
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Click to expand...
Click to collapse
Install the ota update.zip, then before reboot, immediately install supersu.
Do it that way and you won't lose root.

Forced OTA and it failed. I had already flashed the superSU.zip before
If you can't read this is the log...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check ("/system/build.prop" [numbers and letters]
E: Error in /cache/(update file.zip)
(Status 7)
Installation aborted.
Any way to manually flash the update? Because SuperSU OTA isn't working.

So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.

Guhrasoh said:
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Click to expand...
Click to collapse
Now that you mention it I tweaked it with PimpMyRom. I'll take that off and try to update.

I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.

datallboy said:
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
Click to expand...
Click to collapse
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.

sfhub said:
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
Click to expand...
Click to collapse
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.

datallboy said:
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
Click to expand...
Click to collapse
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.

sfhub said:
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
Click to expand...
Click to collapse
I'll probably just backup apps + data and use JSS15R factory image. Made the mistake of not making a backup of my build.prop.
Good thing it's a Nexus Device!

Ota 5.28.605.2 ota

Just got it on my htc one... for use on stock rom/stock recovery....
https://www.androidfilehost.com/?fid=23622183712466856
RUU coming too
http://forum.xda-developers.com/showthread.php?t=2867643

Can I use the zip u provided to update? I'm totally stock. S-on. On 4.4.2. And how to do it it's been years for me. Thought I needed a .pmg file?

rickyjohn said:
Can I use the zip u provided to update? I'm totally stock. S-on. On 4.4.2. And how to do it it's been years for me. Thought I needed a .pmg file?
Click to expand...
Click to collapse
If you are s-on, you can't flash anything custom or stock. You will need to root and s-off first. Or you could take the ota if all you want is the update. If you want to get some customization on there...you should do some reading through the threads. Things are a bit different since a few years ago and this phone doesn't have an external sd card...
Sent from my Lunar Ecliptic One.

rickyjohn said:
Can I use the zip u provided to update? I'm totally stock. S-on. On 4.4.2. And how to do it it's been years for me. Thought I needed a .pmg file?
Click to expand...
Click to collapse
First link is 100% stock and will work on stock recovery. Just place it on the phone storage or SD and boot to stock recovery. Choose the appropriate "apply update from" and then point to that file.
brymaster5000 said:
If you are s-on, you can't flash anything custom or stock. You will need to root and s-off first. Or you could take the ota if all you want is the update. If you want to get some customization on there...you should do some reading through the threads. Things are a bit different since a few years ago and this phone doesn't have an external sd card...
Sent from my Lunar Ecliptic One.
Click to expand...
Click to collapse

every time i try to get into the recovery menu i just get a picture of the phone with a red triangle and exclamation point.

Any idea if towelroot works with this update? I noticed that the update notes on the vzw website says "Device root vulnerability issue has been resolved"
Sent from my HTC6500LVW using Tapatalk

rickyjohn said:
every time i try to get into the recovery menu i just get a picture of the phone with a red triangle and exclamation point.
Click to expand...
Click to collapse
That is your stock recovery. Stock recovery is not meant to go into like custom ones. It's used for ota's, factory resets, and that's about it.
Sent from my Lunar Ecliptic One.

got "invalid operation" when trying to update with the zip file, it is on device storage, any ideas? does the zip need to be renamed?

rickyjohn said:
got "invalid operation" when trying to update with the zip file, it is on device storage, any ideas? does the zip need to be renamed?
Click to expand...
Click to collapse
When flashing an OTA everything has to be bone stock. If you have stock tethering enabled, Xposed Framework installed, or files missing from /system/apps, it will fail.

That's a bummer. I'm totally stock. Just changed fonts, that's it. Guess it just won't go. thanks

I restored stock recovery and stock hotspot and the OTA still won't install properly -- I'm not sure what I'm missing. Is there any way to flash the OTA when rooted without wiping my phone?

Ovy13 said:
I restored stock recovery and stock hotspot and the OTA still won't install properly -- I'm not sure what I'm missing. Is there any way to flash the OTA when rooted without wiping my phone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2485319
Flash in trwp the full odex ROM. I don't know if updating via ota while rooted will work. I know unlock and s-off doesn't matter from personal experience.
Sent from my One using XDA Free mobile app

Uzephi said:
http://forum.xda-developers.com/showthread.php?t=2485319
Flash in trwp the full odex ROM. I don't know if updating via ota while rooted will work. I know unlock and s-off doesn't matter from personal experience.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
In the past, simply restoring stock recovery, updating normally, and then flashing a custom recovery was enough. Doesn't seem to work this time, or there's simply some customization I've forgotten about.

If I'm not mistaken, just the presence of the su binary can be enough to abort an official ota. If you have the official OTA zip and attempt flashing through the stock recovery and it fails, the error message should give some indication of the problem. The script runs a check on the contents of /system and if anything is off it will fail.

pastorbennett said:
If I'm not mistaken, just the presence of the su binary can be enough to abort an official ota. If you have the official OTA zip and attempt flashing through the stock recovery and it fails, the error message should give some indication of the problem. The script runs a check on the contents of /system and if anything is off it will fail.
Click to expand...
Click to collapse
Su is fine. It simply won't work afterwords. Any other system changes will cause it to fail though.

dottat said:
Su is fine. It simply won't work afterwords. Any other system changes will cause it to fail though.
Click to expand...
Click to collapse
So I have TWRP, root, s-off, and XPosed installed. Verizon sent me the OTA update, but I need to return everything to stock before I do anything with the update? I'm a little dense here...

PiperCub49 said:
So I have TWRP, root, s-off, and XPosed installed. Verizon sent me the OTA update, but I need to return everything to stock before I do anything with the update? I'm a little dense here...
Click to expand...
Click to collapse
Disable xposed. Flash stock recovery and take the ota. Then flash custom recovery via Fastboot and flash su.zip in Twrp.
Assuming of course you made no other /system mods other than root and xposed.

[Q] failed to update rooted nexus 7 2013 from 4.4.3 to 4.4.4

Hi everyone,
I posted this thread in General Discussion Q&A and then found this forum, so I posted once again in hoping to get some solution.
I have updated my rooted Nexus 7 2013-LTE using the method described here from 4.4.2 to 4.4.3 succesfully:
liliputing.com/2014/06/upgrade-nexus-android-4-4-3-without-losing-root.html
I used SuperSU and Xposed framework was temporarily uninstalled. However, when I tried the same procedure to update from 4.4.3 to 4.4.4, following errors are appearing:
file "/system/bin/debuggerd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/debuggerd" has unexpected contents.
"/system/bin/debuggerd" has unexpected contents.
E:Error in /cache/0c3dd9bfb71f2b8437be322e6cab5832ce2b4d35.signed-razorg-KTU84P-from-KTU84L.0c3dd9bf.zip
(Status 7)
Installation aborted.
It seems that file debuggerd is somehow changed (my guess by stickmount app). Is it correct that I have to replace the one installed in my /system/bin/ with the original one to continue updating to 4.4.4? Does anyone have the original debuggerd file nexus 7 2013-lte 4.4.3?
Thx u all

hood2ts said:
It seems that file debuggerd is somehow changed (my guess by stickmount app). Is it correct that I have to replace the one installed in my /system/bin/ with the original one to continue updating to 4.4.4? Does anyone have the original debuggerd file nexus 7 2013-lte 4.4.3?
Thx u all
Click to expand...
Click to collapse
Did you try uninstalling stick mount first? That should put the original debuggerd back.

Did you flash back to the stock recovery before accepting the OTA?

meekrawb said:
Did you try uninstalling stick mount first? That should put the original debuggerd back.
Click to expand...
Click to collapse
I tried uninstalling stickmount, but the debuggerd file is still unchanged. The OTA update is still failed. Anyway, thank u for suggesting an idea.

nhizzat said:
Did you flash back to the stock recovery before accepting the OTA?
Click to expand...
Click to collapse
Nice thing to update using method described in:
liliputing.com/2014/06/upgrade-nexus-android-4-4-3-without-losing-root.html,
is that you move forward with what you have. Will try flashing back to the stock revovery if that simpler method not working .

Not sure why anybody would make a guide on how to update without losing root. Worried about losing data and settings? Sure. Worried about losing root? Never.
If you want simple, you can either use adb sideload with the stock recovery or flash the OTA in a custom recovery like you would any other zip file. If you find you don't have root, flash SuperSU.zip again.

Finally, I used NRT to flash to 4.4.4 using system image with option not to wipe data. Many thanks to nhizzat and meekrawb.