I have a new tab that I manually updated via fastboot to 4.3 JWR66V. It is unlocked and rooted, but does not have a custom recovery or anything else unusual on it.
I received a notification of an OTA update and found that JWR66Y has been released. When I tried to run the OTA update, it just left me at the "No Command" prompt, so I downloaded the zip 847b52d071443031e1addb3a54c4df75d29037ae.signed-mantaray-JWR66Y-from-JWR66V.847b52d0.zip and tried to use adb sideload to upgrade.
The sideload starts, but after a short while, it errors out with the following:
set_perm some changes failed
error in /tmp/update.zip
(Status 7)
Does anyone know what might be going on here? I was trying to keep the device clean and close enough to stock that I'd be able to easily upgrade OTA or at the very least with adb sideload, but I'd obviously prefer to keep root so I can use things like Titanium and such.
DEinspanjer said:
I have a new tab that I manually updated via fastboot to 4.3 JWR66V. It is unlocked and rooted, but does not have a custom recovery or anything else unusual on it.
I received a notification of an OTA update and found that JWR66Y has been released. When I tried to run the OTA update, it just left me at the "No Command" prompt, so I downloaded the zip 847b52d071443031e1addb3a54c4df75d29037ae.signed-mantaray-JWR66Y-from-JWR66V.847b52d0.zip and tried to use adb sideload to upgrade.
The sideload starts, but after a short while, it errors out with the following:
set_perm some changes failed
error in /tmp/update.zip
(Status 7)
Does anyone know what might be going on here? I was trying to keep the device clean and close enough to stock that I'd be able to easily upgrade OTA or at the very least with adb sideload, but I'd obviously prefer to keep root so I can use things like Titanium and such.
Click to expand...
Click to collapse
With mine I installed TWRP to install the OTA, went good. And then I flashed Stock Recovery again .
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
The problem is because of root. You have to unroot (scroll all the way down through the SuperSu settings and do a full unroot), then apply the OTA, and re-root.
nyijedi said:
The problem is because of root. You have to unroot (scroll all the way down through the SuperSu settings and do a full unroot), then apply the OTA, and re-root.
Click to expand...
Click to collapse
That's correct, after unrooting the device, the update installed successfully. Thanks.
Further follow-up for future readers.
There was a recent update to SuperSU that indicated in the changelog it fixed a problem with root blocking OTA upgrades. I received a new OTA offer this weekend, and it was able to apply with no problem despite still being rooted with the latest SuperSU.
Thank you very much for the assistance all.
kual said:
That's correct, after unrooting the device, the update installed successfully. Thanks.
Click to expand...
Click to collapse
hi , I'm trying to update my nexus 10 to kitkat 4.4 and have a same problem.
The error in /tmp/update.zip.
I unrooted it but I still had a same error .
What should I do to fix it?
thaibinh0496 said:
hi , I'm trying to update my nexus 10 to kitkat 4.4 and have a same problem.
The error in /tmp/update.zip.
I unrooted it but I still had a same error .
What should I do to fix it?
Click to expand...
Click to collapse
Hi, i had the same error when trying to update to kitkat via ADB sideload OTA update. The problem was in the file "/system/bin/debuggerd", which was changed by SuperSu and may be by Stickmount. Update reported Error 7 while checking system.
So i replaced file "debuggerd" using root explorer with the unchanged version from factory image of JWR66Y and then uninstalled SuperSu (because it continued to change this file after reboot).
After that OTA update was applied successfully.
kual said:
Hi, i had the same error when trying to update to kitkat via ADB sideload OTA update. The problem was in the file "/system/bin/debuggerd", which was changed by SuperSu and may be by Stickmount. Update reported Error 7 while checking system.
So i replaced file "debuggerd" using root explorer with the unchanged version from factory image of JWR66Y and then uninstalled SuperSu (because it continued to change this file after reboot).
After that OTA update was applied successfully.
Click to expand...
Click to collapse
Thank you for this. it FINALLY worked for me.
Sideload r66v
Followed proc
http://forum.xda-developers.com/showthread.php?t=2379616
Hi
i got same error updating to OTA 4.4.2
problem is that i can not access to superSU
ask me binary update
i pushed update package and installed by install zip from sdcard
and installation successed but still can not access asking me binary
any tip ?
what happen if i uninstall superSU ? only thing i wouldn't like to lose whatsapp access
THNKS
Hi guys,
Sorry, a very noob person here when it comes to andriod. My rooted device kept on asking me to install the MJ7 software update from Verizon. After searching the method online, I disabled SuperSU then applied survival mode. However, after numerous attempt, it always failed during the middle of installation and error code 402 was given at the end.
How can I get the update and keep it rooted? Was I missing some files that I deleted after root? or perhaps was the other Superuser(by chainsDD) I installed to correct signature mismatch is interfering with the SuperSU?
Please help! THANKS A MILLION!
Hi All,
I'm currently on D80220b-466-92. Recently got a notification about a software update. Should be D80220c in update, I know some person who did update and got that new version (we bought our devices in the same place).
But I've rooted my device and OTA failed for me with some error code. On rebooting I've got a message that my device is rooted and OTA won't work there.
Right, so I've removed any modification: host from AdAway, adabbeb camera and player mod, SuperSu full deinstalliation from it settings.
Did reboot, kick off OTA downloads again and it failed for me again.
So, is that possible to do that or should I fully reflash my device on stock firmware.
There should be some checks that OTA update script are checking, and needs to find that.
I have a Verizon GS5 that I previously rooted. I gave the phone to my girlfriend and factory wiped it beforehand, losing root, and now when I try to have her take the latest update that came out, it gives an update error. She had no need for root, and I hoped just factory resetting would put it back on the path without update errors. Guess I was wrong.
I re-installed towel-root and SuperSU then did a full unroot, but that still isn't allowing the OTA to pass without an error. Two things I did before I factory reset on my rooted GS5 was the SDCard Fix and Xposed + Tethering Mod. I'm wondering if those changes are still existing (even after the factory reset) and somehow the update sees those/ and stops / gives the error. Is there a way to see the update error log? (E.g. maybe root now and then undo the sdcard fix / exposed tether hack)? I'm just looking for a way to get around doing a full wipe and re-image with ODIN.
I re-rooted and looked at the logfile.. it says the update error was unexpected contents at /system/csc/feature.xml.
I looked into the file and see xposed framework and Wanam elements modified this file. I need a clean one... could anybody on the original 4.4 that came with the Verizon GS5 upload this file??
EDIT: I see now it made a .bak file there, so I restored it. Let's see if unrooting and updating will work now.
SUCCESS! It's funny how i had to root to look at the log file to find what was wrong then unroot to update. Thankfully sdcardfix and xposed made backups of the two files it modified so I could restore them so the checksum on the update would pass.
So I deleted SU off of bin, xbin, and apk. deleted xgel and what not checked root checker and verified i had no root access. tried installing ota lolipop and got a script error status 7, then next time error in cache where the update was. then tried odin flashing stock software. that failed.
attatched pictures of my problems. we want to put my g.fs back to stock due to her upgrade next month.
thoughts?