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
Running my Note 3 on 4.4.2 (KST/ND3), rooted + CWM Recovery (6.0.4.7.), the system refuses to update OTA due to detected system modifications. Any chance to get it work with rootcloack? If so, what module should I add to rootcloack list?
Thanks
Hello,
i have a working rooted stock Lollipop rom, and after updating su binary it failed, after rebooting it. it is stuck in bootloop even after wiping data.
anyway to fix this without losing root?
Try a flash able zip of supersu 2.4, old one gave me bootloop on my LGOG on Android 5, maybe it'll work for you
-------------------------------------------
HIT Thanks if you like my post
-------------------------------------------
My work:
[TOOL]Kernel/Boot.img (un)packer
[ZIP]Flashable zip to bypass lockscreen for LG E975
[TOOL]ANDROID's COMPLETE TOOLBOX
Baseband Fix fir LG F180X converted to International E975
Internal memory mod for QMobile A700/Walton Primo N1/GPAD G2 - Participated Work
I m having a tegra note 7 which is rooted and has twrp installed.
The device is running on kk4.4.2 . I'm able to install ota 2.1 but after that twrp is giving an error (error executing updater binary) for other ota updates(2.3,2.4,2.5 and ota 3).
As I wanted to test lollipop on my device so pls help me.
Hi,
I'm using HTC ONE M9+, today finally HTC released 6.0 Update for M9+,my hpne downloading update without any problem when i click to Install Now it says Rebooting and after reboot TWRP Kicks in and does nothing.Is there any way to disable TWRP to install this new update ?
Flash back the corresponding "stock" recovery.
You must also have an unmodified system to apply the OTA successfully.
i've flashed "recovery_verified.img__TW_1.90.709.3" now TWRp disabled but during update (at %23) it says OTA failed, my OTA is TW, according to error message i need europe's OTA which i couldn't find on internet
i actually have the same issue i have tried copying the ota and tried flashing through adb but it shows that error executing updater binary zip file and errror flashing the device
im running L 5.0.1 and want to update to m 6.0.1 through ota
i have unlocked bootloader but s-on .how to flash the otp? thanks in advance
MIracles happen! Is there anyone that have already made the update and can tell if the sense it's still there or if HTC have removed everything like in the HTC 10?
i think i can update my phone to 6.0 if i can find Europe OTA, i've searched everywhere but i couldn't find it
even i have downloaded the update but cant install as i have system partition modified...i ve searched for a ruu or stock rom but couldnt find anywhere...however i do have the Indian OTA update.
did anyone managed to install 6.0 update yet ?