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, I'm running a stock 4.3 rom with twrp recovery. I initially had the Franco kernel for my phone, but when I encountered recurrent errors when trying to install the 4.4 update I reverted to stock kernel, but I still have the same issues
Whenever I try to flash the update, whether installing directly or through add sideload, I get an error saying 'system/lib/hw/power.msm8690 contains unexpected content,
Error executing updater binary'
And the install fails. Reverting to the stock kernel hasn't helped and neither had updating twrp.
I'm a n00b, so now I'm stuck, hoping someone here can help me out, cheers
Sent from my Nexus 4 using Tapatalk
Instead of using the OTA package, you should flash the full 4.4 rom instead, flashing in recovery won't wipe your data. http://forum.xda-developers.com/showthread.php?t=2527295
Flashing OTA packages using custom recoveries on a modified rom will undoubtly give you issues.
I have ota downloaded waiting to install I'm rooted and unlocked I have twrp installed how do I confirm that phone is stock and then how do I install it using twrp if stock.install failed previously
I'm on global beta 6.7.21 and got an update notification of 6.7.26. A 93MB file. It downloaded ok but whenever I try to install it via TWRP it shows failure. Shows that the fingerprint doesn't match. i thought since I patched the boot.img with UBP it showed problem. So I went on to flash 6.7.21 first, then without patching boot.img tried to flash the 93MB ota. It failed again and showed the same failure that fingerprint doesn't match. It should be Xiaomi/kenzo/************* whereas it is Xiaomi/omni_kenzo/************* . Anyone on global beta miui8 having the same problem? Shout out any possible solution I may have missed.
The flashaholic in me can't live with 6.7.21 when there's 6.7.26 is out.
My phone was officially unlocked, always failed on incremental update, reboot phone then I received another ota full rom update. I normally copied it to external sd card, then flashed rom, flashed superSU and latest xposed v86 by solarwarez in one flash. Rebooted phone, everything was works great.
Sent from my Redmi Note 3 using Tapatalk
twrp not supported for OTA updates try flash full ROM
Sent from my Redmi Note 3 using XDA-Developers mobile app
Tried even TWRP for flashing update but this OTA terminated with error that shown below from recovery log
Verification failed ended with ERROR:.......
Abish4 said:
Tried even TWRP for flashing update but this OTA terminated with error that shown below from recovery log
Verification failed ended with ERROR:.......
Click to expand...
Click to collapse
You can't install an ota on a rooted device with twrp. You need stock recovery and a stock untouched system and boot.img.