Built-in fingerprint error while updating through OTA in stock recovery - Moto E4 Questions & Answers

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.

Related

[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

Ota updates

I own a find 5 and the latest 2 omni nightly updates failed to flash via the ota system update.. I tried manually via twrp recovery and it still failed so i flashed clockworkmod and it failed again via the ota updater so i tried manually again and this time it worked..
Sent from my Find 5 using Tapatalk
How is it that it failed? Did it return any specific error?

downgrading failed while adb sideloading jellybean firmware

hi
tried 2 downgrade from kitkat .54 to jellybean-1.18.40.9
used the below link tutorial
http://forum.xda-developers.com/showpost.php?p=55886429&postcount=969
its by some xda memeber only
but while sideloading
got errors
e:end of footer from/tmp/update.zip not 0xFFFF (file exists)
e:signature verification failed
installation aborted
e:can't open/tmp/update-script.log
e:cannot load volume/misc
what should i do
anyone knows right procedure for downgrading from kk to jb
I dont know if this trick will be succeed on your device. but I did.
flash TWRP..suggest to used latest twrp..
full wipe. include system..
reboot bootloader. there will show warn pop up that is no os. just ignore..
flash stock recovery
then flash stock jb by adb sideload..
hope it can help you

DRK error ENG binary needed??

hello, after choosing to go back to an official rom, I have a DRK error message
https://postimg.org/image/cr8lkrul5/
the phone reboot into recovery then tells me to install ENG Binary
https://postimg.org/image/dvjn7nuev/
By installing twrp and doing root it works but i would like to have access to OTA updates and so do not go through TWRP.
do you have solutions?
(the images are from google and are only for information so you can see what it is).
Drk
Hello I have the same problem what procedure did you do for your device to boot?
You can flash official firmware and flash twrp and root your phone. Without twrp i dont now...
How i can remove this error pmease? I want ota update...

UPDATE.ZIP is corrupt

This morning i received the android 10 ota update on my k20(davinciin). I have twrp and magisk installed and since ota updates fail with twrp installed I simply unrooted my device which replaced twrp with stock recovery. On installing the OTA it says installation failed 'update.zip is corrupt'. Need help.
Why didn't you install through twrp? Just download ROM and install
yaro666 said:
Why didn't you install through twrp? Just download ROM and install
Click to expand...
Click to collapse
Can I do that without wiping my data?

Categories

Resources