update verification failed while trying OTA updates. Pls give me a solution for it
If device is a Samsung one, look inside here:
How to solve "Verification Fail" in Samsung devices | The TechRim
While rooting and changing stock rom of android there may arise different problems ..... while rooting or changing Rom is "Verification Fail".
thetechrim.com
anirban197 said:
update verification failed while trying OTA updates. Pls give me a solution for it
Click to expand...
Click to collapse
The cause of this problem depends on whether your device was rooted or had a custom recovery installed before you tried applying the OTA update.
If you were rooted or had custom recovery installed, first, you have to remove root and/or any other system modifications that you made and you have to restore stock recovery instead of having custom recovery installed. Stock OTA updates require an unmodified system partition and they also require stock recovery because the OTA update process checks the system partition to verify whether it is stock or not and the OTA process has to boot into stock recovery in order to install the OTA update before it can boot into the new system.
If you were not rooted or had custom recovery installed then the update may have failed due to one of your partitions being corrupted.
Either way, the solution is to manually download the update to your PC and then use Odin to flash the update. After the update, you can root the device again and/or install TWRP again. But be warned, if the update comes with a locked bootloader that can not be unlocked then you will not be able to install TWRP and you may not be able to root the device if certain aspects of the software have been patched to prevent rooting exploits.
Related
i tried to install update 68, the shield reboots get me to the screen with the android on its back, select the update install, then it errors out?
is the device being rooted causing the issue o the bootloader.
also if this or any small update installed correctly would i lose my root access,
if i lose root, will i always have to start from a factory rest and lose all my information to root it again.
thanks
An unlocked bootloader is not the problem. If you somehow modified the system image ( like rooted/removed apps, integrated updates into ROM, installed custom recovery or something else) the update process will fail because of it. That might have to do with the fact its an incremental update which checks if it is modified/rooted and/or will update apps which aren´t there anymore.
One way to solve this is to backup your apps and data. Then flash stock recovery and stock image via fastboot and install all updates from the beginning.
The other way is to go to Nvidias Support Page for the Shield. Then download the latest Update for it. It´s an sh package which needs to be extracted under Ubuntu or special tool for windows. Then you can flash the newest image and recovery directly with fastboot. Didn´t try that.
Hope i was able to help you.
So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Saw the probable solution on another post.
mdecaminop said:
So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Click to expand...
Click to collapse
In these forums somewhere I read that the unroot was done using Super su's full unroot option. However it apparently left behind a few files that caused the OTA to fail. So what he did was to uninstall Supersu, reinstall Supersu and update the binary. Then use full unroot function... Maybe it will work for you if you have unrooted using SUpersu...
Unrooting, locking the bootloader, and flashing the stock recovery doesn't allow you to take OTA's.
There is THIS thread, providing OTA files that can be flashed in TWRP or CWM. And are official files from Nvidia.
You have to flash these every time there's an OTA, or just flash a full stock image through fastboot, and never root or flash a recovery.
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
mycologik said:
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
Click to expand...
Click to collapse
Well it seems my second hand tablet has been rooted as well ... I've got the exact same problem that yours ...
Is there a way to go back as out of the box ?
Hi, my nexus 5 is root and use TWRP recovery. every month i get security patch notification but the installation failed.
should i unroot my device or revert to stock recovery or both?
You would need to do both in order to install OTA updates. Alternatively, you could manually flash each partition but leave userdata alone.
Whenever i click on software update it says connecting then gives me a message Registration Failed.
How am i supposed to get phone updates after root?
vangry2020 said:
Whenever i click on software update it says connecting then gives me a message Registration Failed.
How am i supposed to get phone updates after root?
Click to expand...
Click to collapse
Stock updates require an unmodified system, and they also require stock recovery, meaning, no root, no exposed or any other kind of system modification. Even if you did find a way to apply the update while being rooted, it would probably soft brick the device, then you would have to repair the device, IF it can be repaired.
If you want to apply a stock update, return your device to full unmodified stock system, then the update should work. If you have custom recovery, you need to flash the stock recovery back onto your device before you apply the update because the stock update requires stock recovery in order for it actually flash the update.
After applying the update, root the device again and install custom recovery(if you had custom recovery).
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Stock updates require an unmodified system, and they also require stock recovery, meaning, no root, no exposed or any other kind of system modification. Even if you did find a way to apply the update while being rooted, it would probably soft brick the device, then you would have to repair the device, IF it can be repaired.
If you want to apply a stock update, return your device to full unmodified stock system, then the update should work. If you have custom recovery, you need to flash the stock recovery back onto your device before you apply the update because the stock update requires stock recovery in order for it actually flash the update.
After applying the update, root the device again and install custom recovery(if you had custom recovery).
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply.
Is there a way to recover my files and settings exactly as they were after the update since the phone is erased when i unlock the bootloader?
Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Uxlewl said:
Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Click to expand...
Click to collapse
Yes, if you used TWRP to create a backup of your stock ROM before you flashed a custom ROM, you just use TWRP to restore the backup of stock ROM.
Or, if you didn't use TWRP to backup your stock ROM, you can flash your device's stock firmware using the flashtool designed to be used with devices made by your device's manufacturer.
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Uxlewl said:
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Click to expand...
Click to collapse
No, installing TWRP does not require root. Yes, TWRP and root prevent the installation of OTA updates.
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Uxlewl said:
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Click to expand...
Click to collapse
To be more specific, installing TWRP does not necessarily prevent a device from actually receiving/downloading OTA updates, it prevents the actual installation of OTA updates because part of the OTA update includes automatically booting into stock recovery to apply the update. If you have TWRP installed, the OTA update can possibly be downloaded to the device but when the device automatically tries to reboot into recovery, it is trying to boot into stock recovery but if you have TWRP installed, it can't boot into stock recovery to apply the update and when it tries to boot into TWRP, it will try to apply the update but it will fail, resulting in a bricked device and the device will have to be restored.
When it comes to OTA updates, all that is required is an unmodified stock system partition(meaning, no root or any other kind of modifications to the system partition), stock recovery(meaning, no TWRP) and the update has to be offered by your carrier if they offer the update for your specific device.
If a device is rooted, has other system modifications and/or has TWRP installed and you want to apply a stock OTA update, you have to remove root and any other system modifications and you must replace TWRP with the original stock recovery before you can apply the update. If you have TWRP and or root and you remove them to apply an OTA update, you can root the device again and install TWRP again after the update, provided that the OTA does not come with a locked bootloader that can not be unlocked, in this case, you will not be able to reinstall TWRP or root because the bootloader will be locked, which prevents you from installing TWRP again. Sometimes, users remove root and TWRP to apply OTA updates with the intention of rooting and/or installing TWRP again after the update but then get stuck in a position where they can no longer root the device or install TWRP because the bootloader gets locked during the update and there is no way to unlock the newly updated bootloader, from then on, they are stuck with stock with no way to get root, TWRP and custom ROMs reapplied to the device because they were not aware that the update came with a locked bootloader that can not be unlocked by any means.