4.3 Update failing - Nexus 7 Q&A, Help & Troubleshooting

Hi everyone, I have a rooted with stock rom nexus7 with TWRP recovery, every time I want to update to 4.3, it fails, at first it comes to install and after saying 'Verifying Package', it goes to recovery first menu, Any suggestions??
by the way, I don't want to loose any of my data.

Gosh, there are so many threads on this. Did you search or read anything? The specific error is important, but you didn't say what it was. Depending on which error you have determines how to fix it. Was it an 'Error executing updater binary in zip...' or did you get a verification failure on a file such as 'debuggerd' or a system app that you may have replaced or frozen? I was able to fix my problems for a stock rom and kernel, rooted with TWRP after reading the threads in this forum. And your data won't be 'loose' nor will you lose data with this update, but you will lose root, which can be regained easily.

Related

4.2 Update Recovery Error - Unique Issue

I'm getting an error in recovery I've never seen before in my 3+ years with Android, rooting, etc. The error is this:
"assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so"
I get the error when I try to apply the 4.2 OTA .zip package in Clockworkmod Touch Recovery. I am on the newest (3.41) bootloader and obviously I have root. The system files all pass the check, but I'm getting this error and despite having Googled some answers, I've come up empty handed. Apart from flashing back to full stock, I am not sure what to do. Any thoughts from anyone?
JFMFT said:
I'm getting an error in recovery I've never seen before in my 3+ years with Android, rooting, etc. The error is this:
"assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so"
I get the error when I try to apply the 4.2 OTA .zip package in Clockworkmod Touch Recovery. I am on the newest (3.41) bootloader and obviously I have root. The system files all pass the check, but I'm getting this error and despite having Googled some answers, I've come up empty handed. Apart from flashing back to full stock, I am not sure what to do. Any thoughts from anyone?
Click to expand...
Click to collapse
dont know how to fix the error, but there is a newer bootloader version (4.13)
http://forum.xda-developers.com/showthread.php?t=1989319
Have you flashed a custom kernel? Some of the custom kernels also update that file so it is no longer stock, and hence it fails the assertion check on upgrade.
You can download the original stock 4.1.2 file here:
http://forum.xda-developers.com/showpost.php?p=34057950&postcount=221
:good:
Forgot to mention, you'll also need the stock 4.1.2 kernel installed if it isn't already, you can grab a copy here:
http://forum.xda-developers.com/showpost.php?p=33030559&postcount=4
Cheers,
Dave.
I have the same issue with assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so").
I have the stock kernel 4.1.2 and even installed 4.13 bootloader but this error is still there.
I'm under 4.1.2 stock, unlocked/rooted, that's all.
Any idea how to solve that ?

[Q] 4.2.2 Update Error Help

So My Nexus 7 is simple Stock android 4.2.1 with root and i go to update to 4.2.2 and i get a error (The red triangle one)
Can anybody help i hear there are others with this same problem but yet to find somebody with a solution, do you think i should unroot and relock the nexus and try and update again or just reflash back to stock image
That screen sounds a bit like the stock recovery, not a custom recovery as one would expect with a rooted device. Please explain.
The error that occurred is given in the recovery log file - /cache/recovery/recovery.log
Please report what the error was. If you actually have root in the ROM you should be able to view this file.
No need to relock your boot loader - that is unrelated and relocking it only complicates things.
One more thing - OTAs are not designed to be robust in the face of and arbitrarily reconfigured ROM. It is unreasonable to expect that they will work correctly on a rooted device. They are meant for 100% stock devices, PERIOD. While you may not remember explicitly changing something, if you gave root privilege to an app, that app might have changed things which cause the problem that occurs. On this forum, there have been claims that Stickmount, Beats Audio, and even Titanium Backup can cause these sorts of problems.
bftb0 said:
That screen sounds a bit like the stock recovery, not a custom recovery as one would expect with a rooted device. Please explain.
The error that occurred is given in the recovery log file - /cache/recovery/recovery.log
Please report what the error was. If you actually have root in the ROM you should be able to view this file.
No need to relock your boot loader - that is unrelated and relocking it only complicates things.
One more thing - OTAs are not designed to be robust in the face of and arbitrarily reconfigured ROM. It is unreasonable to expect that they will work correctly on a rooted device. They are meant for 100% stock devices, PERIOD. While you may not remember explicitly changing something, if you gave root privilege to an app, that app might have changed things which cause the problem that occurs. On this forum, there have been claims that Stickmount, Beats Audio, and even Titanium Backup can cause these sorts of problems.
Click to expand...
Click to collapse
And how do you fix this? I have the same problem. I guess you need a different file then the OTA one. Where do you get this file?
Thanks!
MatthiasSchuetze said:
And how do you fix this? I have the same problem. I guess you need a different file then the OTA one. Where do you get this file?
Click to expand...
Click to collapse
Ummm... you are forcing me to guess about your situation. You are rooted, but also do not have a custom recovery installed?
What error message do you find in the /cache/recovery/recovery.log file? Please do not simply say "Status 7", report the FULL ERROR message.
As I said, the OTAs are meant to be used with pure stock ROMs, not customized/rooted ROMs. There do not exist an infinite array of OTA file variations corresponding to a fix for the exact problem you are experiencing, unless you were to create one for yourself by unpacking the OTA zip file and hand-editing the META-INF/com/google/android/updater-script file to skip over the problem you are experiencing.
And if you did that, you would certainly need to use a custom recovery to install it, as doing the operation described above would break the signing of the OTA package, so the stock recovery would refuse to install it.
The other alternative which allows you to use the unmodified OTA is to "fix up" a customized ROM by manually replacing all files that were removed or altered with their original stock versions. This process seems almost as ridiculous as the scenario described above, as now you are purposely breaking the modifications performed by root-aware apps (Stickmount? Beats Audio? Titanium Backup?)
The amount of effort this whole process will take is variable depending on how much stuff has been changed since you rooted. When the OTA performs it's checks prior to beginning it's patching operations, it halts on the first check which fails. Which might mean that you will need to iterate several to many times the process of:
- run the OTA, look at the error in /recovery/log/recovery.log
- hand patch the file involved
- re-run the OTA.
Doing the above can be problematic if you have changed multiple framework files - if you replace stuff one file at a time it is possible to wedge the OS because of dependency issues.
The only good news here is that because the OTA runs all it's checks before it patches anything, it is safe to run it as many times as you can tolerate. (On tilapia devices, though there is evidence that using custom recoveries is almost never a good idea if you want the radio firmware to be updated correctly).
A wholly better idea is to simply start over. Make a full Nandroid backup of your current ROM. If you want, you can also experiment with backup/restore apps like Titanium Backup and/or Carbon.. Then you install a pure stock ROM from the Google Factory images, and begin re-customizing all over again, as if you had just bought the tablet.
If you don't like the result, restore your Nandroid backup. That's what backups are for.**
good luck
** its a good idea to get copies of your Nandroid backups off of the device, as there are various ways that the entire /data partition can get wiped - including the psuedo-SD card containing all your precious backups. You've been warned.
First of all. Thanks for the quick response. Secondly, I get this error on both my nexus devices. The Galaxy Nexus and the Nexus 7. Though I don't know if it is exactly the same error - it is very similar (with the android guy on its back and the red triangle). I have a picture of the error message that comes up on the Galaxy Nexus. Both devices have an unlocked bootloader and a custom recovery. The Nexus 7 is deffinitely rooted with the Galaxy Nexus I'm not sure - I thought so but Titanium Backup doesn't let me backup anything and I don't have a custom ROM running on the phone.
So if I understood you correctly I should go back to the stock recovery and unroot it as well and then try it again?!
Why is the picture that I attached not showing?
This is the error message:
ClockworkMod Recovery v6.0.1.9
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation update...
Verifying current system...
assert failed: apply_patch_check("/system/build.
prop". "THEN A WHOLE LOT OF NUMBERS AND LETTERS")
E: Error in /cache/07501b11ad3b.signed-yakyu-JDQ3
9-from-JOP40D.07501b11.zip
(Status 7)
Installation aborted.
I rechecked it for the Nexus 7. The message is slightly different:
assert failed: apply_patch_check ("/system/lib/libSR_A
udioIn.so", "THEN THE NUMBERS AND LETTERS AGAIN")
E: Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-fr
om-JOP40D. 6ece895e.zip
(Status 7)
Installation aborted.
Now, it does show (the picture). Nice.
MatthiasSchuetze said:
First of all. Thanks for the quick response. Secondly, I get this error on both my nexus devices. The Galaxy Nexus and the Nexus 7. Though I don't know if it is exactly the same error - it is very similar (with the android guy on its back and the red triangle). I have a picture of the error message that comes up on the Galaxy Nexus. Both devices have an unlocked bootloader and a custom recovery. The Nexus 7 is deffinitely rooted with the Galaxy Nexus I'm not sure - I thought so but Titanium Backup doesn't let me backup anything and I don't have a custom ROM running on the phone.
So if I understood you correctly I should go back to the stock recovery and unroot it as well and then try it again?!
Why is the picture that I attached not showing?
This is the error message:
ClockworkMod Recovery v6.0.1.9
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation update...
Verifying current system...
assert failed: apply_patch_check("/system/build.
prop". "THEN A WHOLE LOT OF NUMBERS AND LETTERS")
E: Error in /cache/07501b11ad3b.signed-yakyu-JDQ3
9-from-JOP40D.07501b11.zip
(Status 7)
Installation aborted.
I rechecked it for the Nexus 7. The message is slightly different:
assert failed: apply_patch_check ("/system/lib/libSR_A
udioIn.so", "THEN THE NUMBERS AND LETTERS AGAIN")
E: Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-fr
om-JOP40D. 6ece895e.zip
(Status 7)
Installation aborted.
Now, it does show (the picture). Nice.
Click to expand...
Click to collapse
On both devices the files do not match the expectations (assert failed), i.e those files are not the original ones the OTA is expecting -> You need to re-apply the original files to your ROM before you can apply the OTA or you need to do flash the 4.2.2 system manually, which probably might be the easier solution.

Need help with update for nexus 4

Hello
I am using a nexus 4 and today the kitkat update showed up on was downloaded and their was a notification... I clicked that and it took me to the screen which says that you will update to four point four etc etc.. I clicked reboot and install then it rebooted and said updating system then suddenly it showed me an error there was an Android lying down with a red triangle above it I shut down the phone and rebooted then the phone started up and everything was normal there was no update but my phone works on four point three..
. I use a rooted phone could this be Beal cause of root help
I yes that notification doesn't appear now
If you have a root phone and made changes to the /system partition then the OTA update can fail. You can manually download the OTA package here, read the instruction in the same thread on how to sideload. http://forum.xda-developers.com/showthread.php?t=2145848
Just remember that on rooted phones, there is a possibilty the update fail and you won't be able to boot and require flashing factory image to restore it and losing all your data in the process.
eksasol said:
If you have a root phone and made changes to the /system partition then the OTA update can fail. You can manually download the OTA package here, read the instruction in the same thread on how to sideload. http://forum.xda-developers.com/showthread.php?t=2145848
Just remember that on rooted phones, there is a possibilty the update fail and you won't be able to boot and require flashing factory image to restore it and losing all your data in the process.
Click to expand...
Click to collapse
But I did not tamper with system files so I don't think there is a possibility of that.....
The update notification is not sowing up I went to about phone and clicked system updates but now it shows your phone is up to date

How do I update to Android 7.0 on the Axon 7 (USA Model) with TWRP Recovery installed

I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29
Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Only use ota if you don't want twrp/root anymore.
Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2

SAMSUNG GALAXY NOTE 4 (dm-verity verification failed)

I’ve tried looking for solutions online, but to no avail I can’t seem to fix by myself I have recently installed LineageOS 16 , been using it for months until recently it started to slow down, and die down what i mean is the booting process takes time and after booting there is some random crashes and it reboots , I was able to solve the problem using TWRP by wiping out the cache and resetting back to factory settings, but it was taking so long to boot after and then I decided to flash it once again, started from scratch and it worked for some time until it crashed once again leaving me to unfixable bootloop, it stays on LineageOS logo, then screen dims and then just bootloops, so i decided to flash the STOCK ROM using odin which apparently worked It booted and the process was painful because every boot im doing it got slower and slower until it would be stuck at Samsung Logo and then reboots once again, so I reflashed it once again and when it booted, I was bombarded by system apps not reponsing properly, icon like ‘System UI has stopped’ and then most of the In-built app would do the same and it crashed this time, this time when it booted it is stuck to samsung logo, so i tried wiping the cache and formatting data on stock recovery and it is still stuck on boot-loop, if lucky it goes to samsung logo and just literally in that state forever, i left it for hours and it is still the same. and then when i tried booting to stock rom there was a message below that says (dm-verity verification failed), I googled it and it is a cause for tampering system files and I just couldn’t get to work it out and find a proper solution. I hope you all can help me out. Every-time i try to flash the stock rom the message is , (Installing system updates, error, goes to recovery then it has the problem below) If anyone has encountered the same problem, or has a solution I would appreciate it. Thank you.
Samsung Galaxy Note 4 (SM-N910C) treltex
A dm-verity (device mapper verification) is most likely related to a DRK (device root key) fail as well. Contrary to popular belief, flashing the Samsung official factory firmware does not fix all. As I'm sure you have already come to realize nite even flashing a previous nandroid backup resolves the issues.
There are many YouTube vids of fixing dm-verity but the comments are mixed. Some recommend using 4files with and additional file in the pit (partition information table) but that is also very risky and you could wind worse off than you already are.
Your best bet is to flash a "no opt encryt .zip" and follow the introductions. If this is successful you will need to flash the .zip with every no rom or you'll get dm-verity error. The .zip is not a permanent fix but more like a patch, so to speak. The link below is for general info and I can't vouch for the downloads provided from the site. Its best to download your .zips from XDA.
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
https://www.google.com/search?ie=UT...e=android-browser&q=xda+no-verity-opt-encrypt
There is also a force encrip .zip you could look into. Good luck
Thank you. I hope this fixes my problem.. But where do I flash it through odin or TWRP??
I tried flashing the zip i got error 1
Mr. JAVI said:
A dm-verity (device mapper verification) is most likely related to a DRK (device root key) fail as well. Contrary to popular belief, flashing the Samsung official factory firmware does not fix all. As I'm sure you have already come to realize nite even flashing a previous nandroid backup resolves the issues.
There are many YouTube vids of fixing dm-verity but the comments are mixed. Some recommend using 4files with and additional file in the pit (partition information table) but that is also very risky and you could wind worse off than you already are.
Your best bet is to flash a "no opt encryt .zip" and follow the introductions. If this is successful you will need to flash the .zip with every no rom or you'll get dm-verity error. The .zip is not a permanent fix but more like a patch, so to speak. The link below is for general info and I can't vouch for the downloads provided from the site. Its best to download your .zips from XDA.
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
https://www.google.com/search?ie=UT...e=android-browser&q=xda+no-verity-opt-encrypt
There is also a force encrip .zip you could look into. Good luck
Click to expand...
Click to collapse
I tried flashing the zip file in TWRP after installing the stock rom, and I got a Error 1 code
kenesuuu said:
I tried flashing the zip file in TWRP after installing the stock rom, and I got a Error 1 code
Click to expand...
Click to collapse
Try this, read threw the entire tread, follow the instructions. I'd alsoblike to add dm-verity and drk are some of the most difficult to solve, at least in my experience. Furthermore, I would highly recommend making a nandroid backup of all your partitions, especially EFS, boot. I'll see if I can find the no opt encrypt .zip in the meantime. I believe it was 6.0 or 6.1 .
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Error 1
https://forum.xda-developers.com/galaxy-s7/help/error-installing-verity-opt-encrypt-zip-t3436385
scroll down to
JUST WANT TO DISABLE VERITY/ENCRYPTION
https://www.google.com/amp/s/forum....azyflasher-tool-flashing-custom-t3549210/amp/
read threw the rest of the thread.
I don't believe you'll have any success on pure stock firmware. Chances are you'll need to flash a custom kernel for your specific device and/or root package. Unfortunately, theres no one size fits all when it comes to dm-verity or drk.

Categories

Resources