Database Users

[Q] Error While Attempting to Apply Update.zip

Booted into recovery, tried doing the update.zip got Installation Aborted error (status 7).
Full Error:
Code:
-- install from sdcard...
finding update package...
opening update package...
installing update...
assert failed: file_getprop (" /system/build.prop", "ro.build.fingerprint") == "verizion/shadow_vzw/cdma_shadow/shadow:2.2/vzw/23.15:user/ota-rel-keys,release-keys" || file_getprop(" /system/build.prop" , "ro.build.fingerprint") == "verizion/shadow_vzw/cdma_shadow/shadow:2.2.1/vzw/23.340:user/ota-rel-keys,release-keys"
E:Error in /sdcard/update.zip
(Status7)
Installation aborted.

doronster195 said:
I was rooted with z4, had apps frozen with titanium backup, have bootstrap, used dx overclocker (to undervoltage and to do a quick-boot with "android" logo rather than Droid Eye). I unrooted, unfroze, stock voltage/speed and turned off apply at boot, FORGOT to undo the quick-boot (but I thought it wouldnt matter since i'm unrooted).
Booted into recovery, tried doing the update.zip got Installation Aborted error (status 7), pressed reboot phone and got the M, followed by the "android" logo that WILL NOT GO AWAY.
Phone won't load, what should I do? Need phone to work soon!
Click to expand...
Click to collapse
Ok it sounds like you are stuck in a bootloop.....you can restart your phone by doing a batt pull then when you go to turn it on hold the power button and home at the same time until you see the exclamation mark and droid guy ..this means you are in recovery mode ...then press the search button and a menu will appear ....use volume rockers to scroll and the camera or menu button to select ....go to data wipe/factory reset and select it ...then reboot and if it works your x will be back to how it came out of box if it doesn't then you will have to sbf ...find the sbf file for whatever system version you are on and flash it and that should work

Well, I did a restore, which worked. However, I'd still like to receive the OTA update. I downloaded the update.zip and want to install it myself. Why was i given this installation aborted error? Was it truly because of what I said above--quick boot option?
Edit: Tried booting into normal recovery (not bootstrap), while not rooted, and no rooting tasks have been done since the restore. Trying to "apply sdcard:update.zip" gives me an Error in /sdcard/update.zip (status 7) Installation Aborted
Edit2: Original Post updated with issue

I'm in the same boat...
I unfroze the bloat and unrooted my phone, it was stock with all bloat froze so nothing out of the ordinary to be concerned about.
Ran update.zip and got the same error as you. I'm not savvy enough to understand or figure out what's going wrong with any certainty. My best guess is that something in the build prop doesn't jive with the build prop the update.zip file checks against. I doubt rooting would have caused any change in my build prop and I never did anything to my phone other than root and freeze bloat so my build prop should be fine.

Problem Solved
Fixed the issue thanks to the help from the guys at: (#androidchat on freenode)
specifically tabe and krayzee.
I am 2.3.15 originally, with a bootloader 30.04 (not 30.03).
I used the sbf (that I got from androidchat), and just sbfed. Before activating my phone again, I did the update.zip and it worked just fine.
Guide I used for SBF: droidxforums /forum/hacking-help/12015-complete-droid-x-sbf-flashing-guide.html
(it says you should be careful if you are on 30.04, but i did it on 30.04 so you will be fine)
Hope this helps.

Can you share the sbf I am having the same issue and it is ticking me off. Thanks in advance

i posted the link for the sbf in the above post, i cannot post actual links, so you'll have to add to figure out the url for yourself. Just go to androidchat*org and go to their file database, its in there.

doronster195 said:
Fixed the issue thanks to the help from the guys at: (#androidchat on freenode)
specifically tabe and krayzee.
I am 2.3.15 originally, with a bootloader 30.04 (not 30.03).
I used the sbf (that I got from androidchat), and just sbfed. Before activating my phone again, I did the update.zip and it worked just fine.
Guide I used for SBF: droidxforums /forum/hacking-help/12015-complete-droid-x-sbf-flashing-guide.html
(it says you should be careful if you are on 30.04, but i did it on 30.04 so you will be fine)
Hope this helps.
Click to expand...
Click to collapse
Which sbf did you use? Do you have a link to that? PM if necessary...

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 ?

Phone not booting after attempt to update 4.4

So I got the OTA update to 4.4 on my Nexus 4 4.3. I clicked it and it rebooted, took a few minutes to run some files via dos prompt...Afterwards I ended up at my TWRP screen. I selected "reboot" at the main screen then "system" thinking that the stuff happening at the beginning was the install update to 4.4. Afterwards my phone is no longer booting, like it has no OS. Hindsight, I think I should have done some research before continuing. Need some help? What are my options? Download fresh 4.4 and reinstall or ?

bankmaggot said:
So I got the OTA update to 4.4 on my Nexus 4 4.3. I clicked it and it rebooted, took a few minutes to run some files via dos prompt...Afterwards I ended up at my TWRP screen. I selected "reboot" at the main screen then "system" thinking that the stuff happening at the beginning was the install update to 4.4. Afterwards my phone is no longer booting, like it has no OS. Hindsight, I think I should have done some research before continuing. Need some help? What are my options? Download fresh 4.4 and reinstall or ?
Click to expand...
Click to collapse
Update: I was able to get to the recovery mode hitting down+power. I'm kind of lost at this point. Just give me 4.3 anything at this point.:crying:

I am in the same boat!! Any ideas, i have tried to do a sideload but i get an error installing //sideload.zip
checking for md5 file
skipping md5 check : no md5 file found
warning no file_contexts
file_getprop: failed to stat "/system/build.prop": No such file or directory
e:error executing updater binary in zip '//sideloader.zip'

download factory image and flash it via fastboot..for instructions -->Click Me!

anto.danny said:
download factory image and flash it via fastboot..for instructions -->Click Me!
Click to expand...
Click to collapse
Brilliant, that fixed. Thank you :good:

Asus Zenfone Selfie ZD551KL cannot flash any ROMs or restore recovery. TWRP installed

Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?

Did you fix your problem cause I fix mine my device can boot to fast boot mode if you
Did you fix your problem cause I fix mine my device can boot to fast boot mode if yours can I will send you the original recovery boot manger then download the latest firmware from the official webpage the go to bootloader and update the file it will work for sure but now have a software touch problems I tried to change theme and enable gloves mode it worked fine for a little time

Same issue..
Hey Lobstercat,
I am having the same problem as you..
I have tried TWRP (format /cache, /dalvik, /system and /data) with an unlock bootloader from an Asus Selfie. I have made a backup of it before trying the above. TWRP was able to restore the UL-Z00T-WW-1.12.40.382 OS fine.
But when install through TWRP, on UL-Z00T-WW-1.13.40.661-user.zip, it gives up on authentication, of which I also turned off with the same result.
In sideload mode it failed with the following message;
sudo adb sideload UL-Z00T-WW-1.13.40.661-user.zip serving: 'UL-Z00T-WW-1.13.40.661-user.zip' (~79%) E: fota_return_code 408
I have also tried "sudo fastboot flash system system.img" it failed, with the message "system.img was too large" this rendered my device unbootable and TWRP cannot restore the backup grrr..
I have the latest fastboot and adb from google went through the same above procedure with the same result, TWRP terminal shows files which I cannot be deleted with rm -rf command
I need to update with the OTA updates to UL-Z00T-WW-1.15 from Asus first before moving over to LOS.
Lobstercat said:
Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?
Click to expand...
Click to collapse

Resolved..
I was able to sort it out through this link.
https://forum.xda-developers.com/zenfone-2-laser/orig-development/rom-cyanogenmod-13-0-t3317515
"In order to update your firmware to MM one you can either flash ASUS MM rom in stock recovery or flash a package that will update your fw which you can download right here"
Download that link, sideload it with no issues and lineage OS 14 with no issues.
Now running Lineage OS 14. Damn its quick!

Getting failed to mount'/persist'(invalid argument) while flashing custom rom lineage
Lobstercat said:
Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?
Click to expand...
Click to collapse
I am on latest version of TWRP have done all the process
unlocked bootloader
Rooted my phone
On latest version of TWRP
Official lineage os 14.1
But all time getting failed to mount'/persist'(invalid argument)
Even not able to go back to stock recovery through back2stock.zip process
currently operating my phone through restoring backup
What I need to do please anybody have any solution of this please reply thanks in advance

Jayants susner said:
I am on latest version of TWRP have done all the process
unlocked bootloader
Rooted my phone
On latest version of TWRP
Official lineage os 14.1
But all time getting failed to mount'/persist'(invalid argument)
Even not able to go back to stock recovery through back2stock.zip process
currently operating my phone through restoring backup
What I need to do please anybody have any solution of this please reply thanks in advance
Click to expand...
Click to collapse
Excuses excuses, but bottom line just don't get around to things very fast very often. Did you ever figure it out? It was a long time ago now so I assume you did....

Hi I am new to the whole developing world of android?

So I figured I would just get into it and say that I'm new to this all, I have been doing it for some time now and I thought I had it figured out. But now I got myself stuck into a problem I don't know how to fix, I have the Galaxy S7 Edge SM-G935W8, I was trying to unlock it threw 123unlock for SRS Samsung Unlock. I paid for it threw Sammobile. What I did was on one of the options was, they let me use ADB Toolbox and there was an option to Write a backup of my EFS?. At first I didn't even know what that fully meant. so what it actually did was try to put an EFS on the phone. So because I did it wrong my phone wont even boot up anymore it will go to the Samsung pop up screen and it can only be in Download mode or in Recovery either Stock or TWRP even tried Smart Switch but it keeps saying my phone isn't supported, I tried it all from flashing stock rom to custom. All the time I keep getting back the same error which is
"No Support SINGLE-SKU
Supported API: 3
E:Failed to mount /efs (Invalid Argument)
E:Failed to mount /efs (Invalid Argument)
E:Failed to mount /efs (Invalid Argument)
dm-verity error..."
that exact way is how it is on my phone I'm lost and actually don't know what to do now someone help please.

Well that error is similar to what I get. Is it dual sim? Whats the device status in about phone -> software information?

UnNaMeD__ said:
Well that error is similar to what I get. Is it dual sim? Whats the device status in about phone -> software information?
Click to expand...
Click to collapse
I Actually Figured it out how, I flashed it threw twrp and went under terminal and changed the permissions, Because threw stock recovery I looked threw the recovery log and i figured out that the reason was that the error was just because of permissions, so i decided to find the path where the permission was for the EFS file and i change the permission with "chmod u=rxw" after i changed the permission it was able to boot, but the only thing was that the EFS is completly gone so now what im trying to do is go back to normal stock but flash no-verity with twrp then hoping that i would be able to restore it with smart switch update after it realises that its a samsung.

lhkb96 said:
I Actually Figured it out how, I flashed it threw twrp and went under terminal and changed the permissions, Because threw stock recovery I looked threw the recovery log and i figured out that the reason was that the error was just because of permissions, so i decided to find the path where the permission was for the EFS file and i change the permission with "chmod u=rxw" after i changed the permission it was able to boot, but the only thing was that the EFS is completly gone so now what im trying to do is go back to normal stock but flash no-verity with twrp then hoping that i would be able to restore it with smart switch update after it realises that its a samsung.
Click to expand...
Click to collapse
Oh alright thanks for info! Good luck to you. I know how it feels when you are without EFS lol, once I fixed it by flashing stock ROM from Odin.

UnNaMeD__ said:
Oh alright thanks for info! Good luck to you. I know how it feels when you are without EFS lol, once I fixed it by flashing stock ROM from Odin.
Click to expand...
Click to collapse
I tried that as well by flashing but for some reason I always get an error from the boatloader for under BL it never works but for AP, CP and CSC will work but the boatloader won't for some reason