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 ?

Can't update to 4.1.1. Please Help!!!

Let me start off by saying that I have tried everything I can find. I have tried the ADB sideload method. I have tried to go to the firmware it's trying to upgrade from. I've tried both stock recovery and CWM. I'm not a n00b when it comes to unlocking, rooting, flashing etc. Anyway, here's the story. My dad bought a Nexus 7 32GB and it kept asking him to update to 4.1.1 for the landscape rotation. The first time he tried it, it failed because it was trying to update from a specific firmware that he didn't have. He has JRO03S. It was trying to update from JRO03D to the new 4.1.1 update. It fails every time no matter what. Like I stated earlier, I've tried both stock recovery and CWM, but they both error out. I've included some pictures of the error in CWM and the about device screen, but nothing from stock recovery. I was too lazy to put the stock recovery back on there to take a picture, but if it's necessary for a solution then I will. Yes, I have searched here and google. Every solution that I have found has not worked. If anyone can help me then you would be a lifesaver. Thanks for taking the time to read through all this. If I'm not being specific enough then please let me know what else you need to know.

The assert() failure you see in the custom recovery is to be expected - it is the installer script checking to make sure that someone is attempting to apply the update to an exact version of the factory software. In this case, exact also means the version of the recovery boot in use which is trying to process the update.
In general, you can not use a custom recovery with an unmodified OTA installer file because of that first assert.
The OTA updates are NOT complete re-installs; they use a patching tool to fix up existing files on the device. That allows their size to be quite a bit smaller than a full new install. Read that again - existing files!.
It is my impression (someone correct me if I am wrong) that the installer scripts also do checksums on each individual target files that are intended to be patched, and if a single one of them fails, the install will spontaneously abort - part way through the process.
That has serious consequences, as now a failed partial install will block a subsequent attempt - if any of the target files get successfully patched, they will no longer have the checksum expected by the update script - they will no longer have the (old file) checksum. [ note I might be fuzzy on whether the individual file checks cause a wholesale abort of the installation session, or they cause a per-file abort ]
In general, you can only use an OTA patch kit on a modified phone if you have not altered any of the files involved in the patching process, and you are using the stock recovery. If you want to use a custom recovery, for certain you need to diddle the update .zip file at a minimum to remove that initial assert(), and also verify that you have not removed or fooled with any of the files from the original distro that are involved in the patching process.
Given where you are, I suggest you make backups (possibly including using Titanium Backup), and start over with the phone (flash a stock 4.1.x or 4.2.x installation or a custom ROM). OR, if you happen to have a near bone-stock backup (meaning the only thing you have done is install the Superuser.apk and su binary), you could restore that, restore the stock recovery, and then proceed with the update from there.
good luck

bftb0 said:
The assert() failure you see in the custom recovery is to be expected - it is the installer script checking to make sure that someone is attempting to apply the update to an exact version of the factory software. In this case, exact also means the version of the recovery boot in use which is trying to process the update.
In general, you can not use a custom recovery with an unmodified OTA installer file because of that first assert.
The OTA updates are NOT complete re-installs; they use a patching tool to fix up existing files on the device. That allows their size to be quite a bit smaller than a full new install. Read that again - existing files!.
It is my impression (someone correct me if I am wrong) that the installer scripts also do checksums on each individual target files that are intended to be patched, and if a single one of them fails, the install will spontaneously abort - part way through the process.
That has serious consequences, as now a failed partial install will block a subsequent attempt - if any of the target files get successfully patched, they will no longer have the checksum expected by the update script - they will no longer have the (old file) checksum. [ note I might be fuzzy on whether the individual file checks cause a wholesale abort of the installation session, or they cause a per-file abort ]
In general, you can only use an OTA patch kit on a modified phone if you have not altered any of the files involved in the patching process, and you are using the stock recovery. If you want to use a custom recovery, for certain you need to diddle the update .zip file at a minimum to remove that initial assert(), and also verify that you have not removed or fooled with any of the files from the original distro that are involved in the patching process.
Given where you are, I suggest you make backups (possibly including using Titanium Backup), and start over with the phone (flash a stock 4.1.x or 4.2.x installation or a custom ROM). OR, if you happen to have a near bone-stock backup (meaning the only thing you have done is install the Superuser.apk and su binary), you could restore that, restore the stock recovery, and then proceed with the update from there.
good luck
Click to expand...
Click to collapse
I appreciate your response. I think I may have left some things out. I am not rooted. I have only flashed the custom recovery and unlocked the bootloader. That's it. If I have to start completely over then I will. I have already tried that though. I'm willing to try any solutions that anyone has. Thanks again for your response.

Evo4eva said:
I appreciate your response. I think I may have left some things out. I am not rooted. I have only flashed the custom recovery and unlocked the bootloader. That's it. If I have to start completely over then I will. I have already tried that though. I'm willing to try any solutions that anyone has. Thanks again for your response.
Click to expand...
Click to collapse
OK. I saw the "ClockworkMod Recovery v6.0.1.0" banner and assumed rooting.
Well, let's look at the assert that you show failing (first image)
assert failed: apply_patch_check("EMMC: /dev/block/platform/sdhci-tegra.3/by-name/LNX:5007....)
Click to expand...
Click to collapse
The "LNX" partition is the "boot.img" area of the device - the kernel and ramdisk for your regular OS boot.
The fact that the assert fails means one of two things:
- that your boot partition has been modified from "stock", or
- the update .zip file is intended for some other version of a factory rom.
One of those two things. Would be sort of surprising if the OTA process mis-judged which factory release was currently on the phone. From the first image, it sure looks like the update package is intended for a from/to migration of:
JRO03S -> JZ054K
and your status screen does show JRO03S. Are you sure don't have a slightly modified boot partition?
I'm not sure what the four parameters in the assert statement are - I would think that at least one of them has to be a checksum. As the LNX (boot) partition is just a binary blob there is no filesystem present; perhaps the shorter numbers are byte lengths within the partition.
If you want to download the same OTA and fool with it (for instance to omit that first assert in META-INF/com/google/android/updater-script, re-zip it & try with TWRP), this link seems to be working:
http://android.clients.google.com/p...signed-nakasi-JZO54K-from-JRO03S.d41da8f6.zip
That's the same place the OTA process gets it from (and stuffs it into /cache along with a recovery-command file).
good luck
---------- Post added at 02:22 PM ---------- Previous post was at 02:04 PM ----------
Update -
On a lark I downloaded the OTA (referenced in the URL above) and took a look at
META-INF/com/google/android/updater-script
the assert that you see failing is the very last check before it actually begins the patching process!
That means that all the other checks (things in the /system partition) passed before that last check failed.
That certainly seems to imply a boot image that has been diddled with. Since you still show JRO03S (I'm not sure about the kernel string - I don't know what it is supposed to be), most likely this would have been a flashable zip that modified something only in the ramdisk. Does that sound familiar?

bftb0 said:
OK. I saw the "ClockworkMod Recovery v6.0.1.0" banner and assumed rooting.
Well, let's look at the assert that you show failing (first image)
The "LNX" partition is the "boot.img" area of the device - the kernel and ramdisk for your regular OS boot.
The fact that the assert fails means one of two things:
- that your boot partition has been modified from "stock", or
- the update .zip file is intended for some other version of a factory rom.
One of those two things. Would be sort of surprising if the OTA process mis-judged which factory release was currently on the phone. From the first image, it sure looks like the update package is intended for a from/to migration of:
JRO03S -> JZ054K
and your status screen does show JRO03S. Are you sure don't have a slightly modified boot partition?
I'm not sure what the four parameters in the assert statement are - I would think that at least one of them has to be a checksum. As the LNX (boot) partition is just a binary blob there is no filesystem present; perhaps the shorter numbers are byte lengths within the partition.
If you want to download the same OTA and fool with it (for instance to omit that first assert in META-INF/com/google/android/updater-script, re-zip it & try with TWRP), this link seems to be working:
http://android.clients.google.com/p...signed-nakasi-JZO54K-from-JRO03S.d41da8f6.zip
That's the same place the OTA process gets it from (and stuffs it into /cache along with a recovery-command file).
good luck
---------- Post added at 02:22 PM ---------- Previous post was at 02:04 PM ----------
Update -
On a lark I downloaded the OTA (referenced in the URL above) and took a look at
META-INF/com/google/android/updater-script
the assert that you see failing is the very last check before it actually begins the patching process!
That means that all the other checks (things in the /system partition) passed before that last check failed.
That certainly seems to imply a boot image that has been diddled with. Since you still show JRO03S (I'm not sure about the kernel string - I don't know what it is supposed to be), most likely this would have been a flashable zip that modified something only in the ramdisk. Does that sound familiar?
Click to expand...
Click to collapse
All I did was use the nexus 7 toolkit to unlock the bootloader and flash CWM touch. Yes, I do think CWM was a zip file. I'm not sure though. It's been a while since I did all that. I didn't flash anything else though.

Evo4eva said:
All I did was use the nexus 7 toolkit to unlock the bootloader and flash CWM touch. Yes, I do think CWM was a zip file. I'm not sure though. It's been a while since I did all that. I didn't flash anything else though.
Click to expand...
Click to collapse
Well, I don't know what to tell you then. Everything looks kosher except for the fact the installer is complaining about the existing boot partition not matching what it is looking for. If you took that check out, and let the patcher-thingy do its work, it could easily bork your boot image and render your tablet OS unbootable.
At this point, if you are intent on staying on 4.1.x, I suggest you install Titanium Backup, back up all your User apps & data (not the system apps), and install the full factory image for JZO54K from here
To be on the safe side, make a backup of everything on your "SD card" - after you have done the Titanium Backup.

bftb0 said:
Well, I don't know what to tell you then. Everything looks kosher except for the fact the installer is complaining about the existing boot partition not matching what it is looking for. If you took that check out, and let the patcher-thingy do its work, it could easily bork your boot image and render your tablet OS unbootable.
At this point, if you are intent on staying on 4.1.x, I suggest you install Titanium Backup, back up all your User apps & data (not the system apps), and install the full factory image for JZO54K from here
To be on the safe side, make a backup of everything on your "SD card" - after you have done the Titanium Backup.
Click to expand...
Click to collapse
Well, unfortunately I have already tried that factory image on stock recovery and through ADB. It failed also. I appreciate all the help so far, but it looks like my dad has a bunk tablet. I'll just flash the stock recovery and have him get an exchange. I don't see another option. Thanks again!

Evo4eva said:
Well, unfortunately I have already tried that factory image on stock recovery and through ADB. It failed also. I appreciate all the help so far, but it looks like my dad has a bunk tablet. I'll just flash the stock recovery and have him get an exchange. I don't see another option. Thanks again!
Click to expand...
Click to collapse
Well I would think that is a failure with a different root cause as the factory installs don't really care about what is on the tablet - well, except maybe for a version check of the bootloader, and I do see that JZO54K did have the older v3.41 bootloader. That's a possibility.
What error occurs when you try to flash that factory image?
FWIW, oldblue910 mantains an archive of Nexus 7 factory images. You didn't mention whether or not you were on the WiFi only version (nakasi) or 3G version (nakasig), but he has both on his site.
good luck
PS I note that I never checked if there was a different OTA depending on whether or not the unit in question was 3G vs. WiFi-only, although TBH it would be weird if the wrong one got delivered over the air to the tablet. It does seem quite odd though, that the only thing which doesn't pass the initial OTA assert checks (checksums) is the boot image.

bftb0 said:
Well I would think that is a failure with a different root cause as the factory installs don't really care about what is on the tablet - well, except maybe for a version check of the bootloader, and I do see that JZO54K did have the older v3.41 bootloader. That's a possibility.
What error occurs when you try to flash that factory image?
FWIW, oldblue910 mantains an archive of Nexus 7 factory images. You didn't mention whether or not you were on the WiFi only version (nakasi) or 3G version (nakasig), but he has both on his site.
good luck
PS I note that I never checked if there was a different OTA depending on whether or not the unit in question was 3G vs. WiFi-only, although TBH it would be weird if the wrong one got delivered over the air to the tablet. It does seem quite odd though, that the only thing which doesn't pass the initial OTA assert checks (checksums) is the boot image.
Click to expand...
Click to collapse
It's the WiFi only version. I know this whole situation is weird. I've been rooting and flashing since the G1 and have never encountered anything like this. I did make sure I tried the one that was for the WiFi version and it still didn't work though. Thanks again for all your help.

[solved] "Footer is wrong" error after updating to 5.0 - can't flash (workaround)

[solved] "Footer is wrong" error after updating to 5.0 - can't flash (workaround)
I just decided to upgrade my Note 3 (N9005) from 4.4.2 to Lollipop - I was holding off until Xposed for TW seemed nice and stable - and used this guide to do it. The intention was to go up to 5.0 and then put on a custom 5.1 rom on with xposed.
Since putting 5.0 on, however, I appear to be able to flash almost nothing - everything comes up with the...
"Finding update package...
Verifying update package...
E: footer is wrong
E: footer is wrong
E: signature verification failed
Installation aborted"
...error, then reboots. I tried changing from CWM to TWRP, and discovered that anything which uses the Aroma installer won't run either - if I turn off verification it starts then quits back to TWRP. I tried a whole bunch of other update threads but ended up with a device that wouldn't boot.
At this point I decided to push the 5.0 ROM from Sammobile back on via Odin and try to start afresh. My device is currently working with 5.0 (and CWM) on it but I still cannot flash anything - with the one exception of arter97's kernel, which flashes fine!!!
I'm stumped. I've read various threads about the "Footer is wrong" error and am none the wiser. It cannot be the files, I've pulled a number of them numerous times (various machines too) and checked the hashes and they're all good, but I can't fined anything conclusive to give me a way forward.
Can anyone suggest a next step? Please?

After another day of fruitless searching I finally found a thread (in this forum, ironically) which discussed the problems with TWRP 3 and Aroma.
I installed TWRP 2.8.7 - still no joy with the verification - but with verification disabled (I'd checked the hashes) I finally managed to install a 5.1 custom ROM. So while I'm none-the-wiser as to the source of the "Footer is wrong" error, at least I've been able to work round it.
Hope this helps someone else.

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....