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 ?
Related
Hello,
Today we have a new ota update for HTC One S, but I can't installed it, installation is aborted.
I have downloaded it, then I want to install it, my phone turned off then it turn on with recovery, but I have the message:
Installation aborted.
I have tried to do that manually with recovery, but I have the same message.
Do you have any idea?
Firstly, Is the OTA configured to be flashed via CWM ??
Secondly, Flashing official signed packages require the bootloader to be locked (so ive heard)
Thirdly, Check the MD5 sums match,, Its possible it was a bad download.. This is the most common cause of ''installation aborted'' messages
Here the same
I start the OTA Update for my HTC one S
this error comes on CWM Recovery
ClockworkMod Recovery v5.8.3.1
"Finding update package...
E: Can´t mount INTERNAL SDCARD...
Installation aborted. "
thanks for help
HTC One S only Root and recovery. s-on stock rom
My guess is it's a recovery problem, as the package won't install via manual either.
But I won't dive deeper into the matter now. Just backing up my phone and cleaning it out to be ready for shipping tomorrow. It's going back to retailer because of the MAO chipping issue.
After flashing the Stock Recovery with this wonderful One klick tool the Update is working just fine...
http://forum.xda-developers.com/showthread.php?t=1604677&page=6
I had my Bootloader unlocked via HTCdev... Seems like an unlocked Bootloader has got nothing to do with this issue!
To keep your Phone rooted after the update, use OTA Rootkeeper from the Playstore!
Where did you get the stock recovery? I'm having trouble finding it.. I want to install the OTA update!
eahiv said:
Where did you get the stock recovery? I'm having trouble finding it.. I want to install the OTA update!
Click to expand...
Click to collapse
I follow one of torxx's thread and it took me here, stock recovery available.
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
I bought a China set of OPO last month. I thought this phone originally installed Color Os rom and then re-installed to CM11s 44s version when it selling. When I turned on the phone for the first time, I already get the update notification for the 05q version. So, I tried to update it but it failed to update it for many times that I tried. My phone rebooted when I clicked "flash updates" and loading for a while then failed in cyanogen recovery. I also tried with manually update with downloaded zip file and installed it in cyanogen recovery. It still failed with mentioned "system 7..." message. Is there any way to fix this problem if I want to flash cm11s latest update firmware, rather than use other custom roms? ??
It's impossible to know what the seller did to the phone before you got it so it's probably a good idea to flash the stock images and start from scratch. Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
If your bootloader is locked you'll need to unlock it, but be aware that doing so wipes all user data. Install TWRP recovery and make a nandroid backup of your current setup just in case. Then flash the stock images using fastboot.
Transmitted via Bacon
Actually, what does "system error 7" means when installation?
Here you go
johnsin5393 said:
Actually, what does "system error 7" means when installation?
Click to expand...
Click to collapse
Here you will find what is System 7 error and how to fix it.
http://forum.xda-developers.com/showthread.php?t=2522762
Hi,
I've got TWRP 3.0.2-0 recovery installed with CM12.1.1 YOG7DAS2K1 and am receiving the OTA update for CM13.0 ZNH0EAS2JK Incremental but the installation fails with an error message in recovery saying it's expecting "YOGDAS2K1" level but finds "YOG4PAS1N0". This happens whether I re-enable the CM Recovery update or not.
I found a thread here on XDA linking to all CM official updates. I flashed the recovery from "cm-12.1-YOG7DAS2K1-bacon-signed-fastboot" successfully and then tried the update again but it still failed. Again, happens whether I have CM Recovery update enabled or not.
Verifying current system...
system partition has unexpected contents
E : Failed to install @/cache/recovery/block.map
Click to expand...
Click to collapse
So now I flashed TWRP again. Does someone know what I should do to install the update ? Preferably without returning to stock first.
Solved
Feeling a bit stupid really...
Right under my post in the list was this post which deals with my problem exactly. I just updated my phone using that guide.
hello everyone I just have a couple question regarding my honor 6x USA version. I am still stock MM 6.0 EMUi 4.1....
1. Will I receive ota updates if I have successfully unlocked bootloader and installed root?
2. I have also tried to back up my device via twrp and get a failed error. Is this caused by backing up the oem info?
1. Last time it didn't work for me. The update got downloaded, rebooted to recovery, but TWRP was unable to install it via the command from update app. So I did force-update and live happily...
2. You need to be more specific about the error. It's basicly a hard copy, so not much can go wrong.
Reep1324 said:
1. Last time it didn't work for me. The update got downloaded, rebooted to recovery, but TWRP was unable to install it via the command from update app. So I did force-update and live happily...
2. You need to be more specific about the error. It's basicly a hard copy, so not much can go wrong.
Click to expand...
Click to collapse
The error occurred during the process of backing up data...Error 255 I also believe it said something about tar fork?
http://lmgtfy.com/?q=TWRP+Error+255
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.