When I rooted ,I backup and delete some some flexT9 input file, then I find out I can not recive SMS after root .
So I unroot ,now I get OTA update but it's says error about I miss some flexT9 file.I can not restore file without root.
Now I can never root again ,and I can not even UPDATE OTA because system fille ar change.
What can I do NOW ?
Especially if its still on warranty, send it in saying that the OTA2 failed. If enough people do it they'll release a flashable system image, I'm sure...
Moved To General​
No questions in the development section Please!​
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 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 own a rooted Note 3. (Take a look to the attached screenshot)
An OTA upgrade has been notified and downloaded. But I haven't installed yet because I think I'll lost my root if I do that thing.
Is that right?
Is there a "safe" way to upgrade my Note's firmware without loosing root?
cinciopillo said:
I own a rooted Note 3. (Take a look to the attached screenshot)
An OTA upgrade has been notified and downloaded. But I haven't installed yet because I think I'll lost my root if I do that thing.
Is that right?
Is there a "safe" way to upgrade my Note's firmware without loosing root?
Click to expand...
Click to collapse
You cannot OTA update if the phone has been rooted. If you do that, the error message will be shown.
Follow this instruction to OTA update and keep root:
1. Open SuperSU settings
2. Scroll down to the bottom, Enable Pro
3. Check Survival mode
4. Uncheck Enable Superuser
5. Install OTA update
6. After reboot, Enable Superuser
7. Disable Survival mode
Note: You have to purchase Superuser Pro for this to work, and you have to reboot after upgrading to Pro.
cinciopillo said:
I own a rooted Note 3. (Take a look to the attached screenshot)
An OTA upgrade has been notified and downloaded. But I haven't installed yet because I think I'll lost my root if I do that thing.
Is that right?
Is there a "safe" way to upgrade my Note's firmware without loosing root?
Click to expand...
Click to collapse
@cinciopillo you will loss root access. You have to root it again, if any way available to root it again. "Kindly ignore this"
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?