I have received the 4.3 OTA update but I am rooted with tons of apps. Can I use the OTA update or will I have to do it manually and loose everything ?
I have tried the OTA update but it goes to team win screen and then nothing. I have pressed reboot and it back to 4.2.2
Just need help on how to approach this
.
Thanks in advance.
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
Hello!
I had previously rooted my AT&T Samsung Galaxy S4 using towelroot and everything was fine. However, I recently received an alert from AT&T stating that a new update was available. I currently have 4.4.2 and from this forum, it sounds like the update was for 4.4.4.
I went to download and install the update, but when I did so, the update failed and my root was removed. I cannot reroot using towelroot nor can I get the update to complete, it just resets at about 25%.
I'd like to install the update successfully and possibly reroot, although root is a lesser priority. Does anyone have any ideas on how I can fix this problem?
Thank you.
Do you have a recovery installed? Just flash the SuperSU from recovery, reboot and install binaries. Problem solved.
HORiZUN said:
Do you have a recovery installed? Just flash the SuperSU from recovery, reboot and install binaries. Problem solved.
Click to expand...
Click to collapse
What are binaries and how do you install them? thanks
Deep_Blue_9 said:
Hello!
I had previously rooted my AT&T Samsung Galaxy S4 using towelroot and everything was fine. However, I recently received an alert from AT&T stating that a new update was available. I currently have 4.4.2 and from this forum, it sounds like the update was for 4.4.4.
I went to download and install the update, but when I did so, the update failed and my root was removed. I cannot reroot using towelroot nor can I get the update to complete, it just resets at about 25%.
I'd like to install the update successfully and possibly reroot, although root is a lesser priority. Does anyone have any ideas on how I can fix this problem?
Thank you.
Click to expand...
Click to collapse
The process is lil bit costly. I was all afternoon looking for it . I think this is the solution:
1. There is no official firmware file for NC1. You will have to flash the NB1 file first then apply the update to NC1: HERE
2. You can root your phone and have the latest update for your device. How? Follow this GUIDE.
3. Enjoy
It's easier for my device, I guess. If I flash a rom that doesn't have root access, I just flash the SuperSU zip in recovery and reboot. Unlocked bootloaders make it sooo easy to mess with the phone
Joku1981 said:
The process is lil bit costly. I was all afternoon looking for it . I think this is the solution:
1. There is no official firmware file for NC1. You will have to flash the NB1 file first then apply the update to NC1: HERE
2. You can root your phone and have the latest update for your device. How? Follow this GUIDE.
3. Enjoy
Click to expand...
Click to collapse
Thanks, things are good now!
I followed the instructions for your step Step 1 spelled out in detail at
http://forum.xda-developers.com/showthread.php?t=2616221
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
http://forum.xda-developers.com/showthread.php?t=2674223
and I was able to update to 4.4.4 successfully. I haven't tried to root my phone but I'm not sure if I really want to so everything seems resolved.
How can someone pull OTA if person has no root? or how can I download OTA while rooted on Android TV 5.0.2 and then someone snatch ? it says system up to date at first it would download but when I tried to install it just gave me error.
I have my phone rooted (originally it was king root but I managed to get SUroot on it) and have TWRP recovery installed, other than that my phone is stock. Yesterday I got a notice that there was an OTA update. I tried it out of curiosity but it failed with no harm done just an error. Does anyone know what the update is? Is it worth reverting to stock for?