Database Users

[Q] Unable to sideload stock OTA 4.3 JWR66Y from JWR66V - set_perm Status 7

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

Can't Flash OTA update.zip via TWRP

As the title says, I can't flash Update.zip. During flashing process it says,
''assert failed: getprop(''ro.product.device'') == jflte
E:Error executing updater binary in zip. '/sdcard/update.zip'
error flashing zip '/sdcard/update.zip'
updating partition details...
FAILED
I'm using 4.4.2 rooted, SU, TWRP 2.7.0.0. I've searched the forum and one thread says it's because of Exposed Framework. i've uninstalled it, but still nothing.

OTA fails
The OTA updates doesn't works correctly , this is the reason who I update with odin (Don't worry , your data are safe when you update on odin).

ain't there any way to update my device via ota

When you have "assert failed" issue, open ZIP file through WinRAR, go under META-INF/com/google/android and open updater-script, delete any line like the followings:
Code:
assert(getprop("ro.product.device") == "NAMEOFDEVICE" || getprop("ro.build.product") == "NAMEOFDEVICE");
Where NAMEOFDEVICE can be jflte, jfltexx etc. Leave directly a "mount" or "uiprint" line as 1st line, save the file and confirm the modification in WinRAR's popup. Finally flash the file
Inviato dal mio GT-I9505

[Q] Issue upgrading from 5.0.0 to 5.0.1 on Nexus 7 (2013 WiFi)

I'm trying to apply the 5.0.1 LRX22C OTA update file on my Nexus 7 (2013 WiFi), which is currently running 5.0.0 Build LRX21P. I've tried installing the zip through TWRP recovery and by sideloading using the Nexus Root Toolkit from my computer...no luck either way.
Here's the issue I'm running into:
During the OTA zip install process, I get an error saying that the user build on my device is LRX21V, and the update aborts because the package expects build LRX21P. (My device settings say that I'm on LRX21P.) I upgraded to 5.0.0 in the first place by manually installing the OTA zip from build KTU84P. I'm not sure if that has anything to do with the issue, since I did not wait for the OTA to become available when it rolled out to me in the System Update feature (maybe sideloading OTAs triggers my device to load test/interim builds?).
Here's what I get in the TWRP log:
Installing '/sdcard/bc4516eb14461efdfaf309311b1f09328b654012.signed-razor-LRX22C-from-LRX21P.bc4516eb.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
script aborted: Package expects build fingerprint of google/razor/flo:5.0/LRX21P/1570855:user/release-keys or google/razor/flo:5.0.1/LRX22C/1602158:user/release-keys; this device has Android/omni_flo/flo:5.0/LRX21V/dees_troy11241447:eng/test-keys.
Package expects build fingerprint of google/razor/flo:5.0/LRX21P/1570855:user/release-keys or google/razor/flo:5.0.1/LRX22C/1602158:user/release-keys; this device has Android/omni_flo/flo:5.0/LRX21V/dees_troy11241447:eng/test-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/bc4516eb14461efdfaf309311b1f09328b654012.signed-razor-LRX22C-from-LRX21P.bc4516eb.zip'
Error flashing zip '/sdcard/bc4516eb14461efdfaf309311b1f09328b654012.signed-razor-LRX22C-from-LRX21P.bc4516eb.zip'
Click to expand...
Click to collapse
Anyone know how I can get the update to work? I don't want to wipe my device to flash a factory image...it's not that urgent. But if there's a way I can upgrade without waiting for the OTA to rollout to me, that'd be nice.
Thanks for any help!

Wrong section, 2013 N7 Q&A is here,
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa?nocache=1&z=9648081501945854
?

Error executing updater binary

Hey!
I'm trying to install CM, but it always gives me the error executing updater binary in zip.
I've got TWRP 2.8.7.0 and tried with CM13 and CM12 on my Huawei G7-L01
I hope somebody can help me

Help! installed SuperSU.zip but it fail to root my Le Pro3?

Hello,
I have followed the step of the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" and successfully unlocked the bootloader and loaded various customized ROM and they boot and work OK. The only issues is that I am not able root my device. I have tried to install different version of SuperSU in TWRP but during the the installation at the "Boot image patcher" stage, it shows:
**********************
Boot image patcher
**********************
-Finding boot image
--- Boor image: /dev/block/sde18
- Decompressing ramdisk
- Checking patch status
--- Already patched. attempting to find stock backup
--- Stock remote failed, attempting ramdisk restore
- checking patch status
- Patching sepolicy
--- Failure, aborting
After reboot, the SuperSU app is there but the device is not rooted and SuperSU keeps saying a binary update is required and it downloads it but fail to install. Verified by RootChecker app and LukcyPatcher, the device is not rooted. Anyone have the experience? How can I solve it? Thank you ~~~

dennytsai said:
Hello,
I have followed the step of the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" and successfully unlocked the bootloader and loaded various customized ROM and they boot and work OK. The only issues is that I am not able root my device. I have tried to install different version of SuperSU in TWRP but during the the installation at the "Boot image patcher" stage, it shows:
**********************
Boot image patcher
**********************
-Finding boot image
--- Boor image: /dev/block/sde18
- Decompressing ramdisk
- Checking patch status
--- Already patched. attempting to find stock backup
--- Stock remote failed, attempting ramdisk restore
- checking patch status
- Patching sepolicy
--- Failure, aborting
After reboot, the SuperSU app is there but the device is not rooted and SuperSU keeps saying a binary update is required and it downloads it but fail to install. Verified by RootChecker app and LukcyPatcher, the device is not rooted. Anyone have the experience? How can I solve it? Thank you ~~~
Click to expand...
Click to collapse
Did you flash the latest SU version ? http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
If not worked, flash Magisk here : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hope it will work. Good luck :fingers-crossed:

bayad said:
Did you flash the latest SU version ? http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
If not worked, flash Magisk here : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hope it will work. Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks for your suggestion.
I flash the Majisk v12 in TWRP. It did not show any errors during installation but it doesn't work. After reboot, I cannot see the app. I install Majisk Manager and it confirms that the phone is not rooter and it cannot detect the location of bootimage. Is it possible that something wrong with my bootimage? I followed the instruction of the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" thread and I am now able to flash any custom ROM but just cannot root. Anyone have similar experience??

hi fir me same problem.... i an on N and i flash super su. 78 and its ok.... i think compatibility problem ??

dennytsai said:
Hello,
I have followed the step of the "X727 (US Model) Persistent bootloader unlock from 5.8.019s" and successfully unlocked the bootloader and loaded various customized ROM and they boot and work OK. The only issues is that I am not able root my device. I have tried to install different version of SuperSU in TWRP but during the the installation at the "Boot image patcher" stage, it shows:
**********************
Boot image patcher
**********************
-Finding boot image
--- Boor image: /dev/block/sde18
- Decompressing ramdisk
- Checking patch status
--- Already patched. attempting to find stock backup
--- Stock remote failed, attempting ramdisk restore
- checking patch status
- Patching sepolicy
--- Failure, aborting
After reboot, the SuperSU app is there but the device is not rooted and SuperSU keeps saying a binary update is required and it downloads it but fail to install. Verified by RootChecker app and LukcyPatcher, the device is not rooted. Anyone have the experience? How can I solve it? Thank you ~~~
Click to expand...
Click to collapse
Flash the lastest version of ElementalX Kernel and reboot system. After, flash the supersu. The ElementalX Kernel is required before attempting to root.
Greeting from Chile