Database Users

Unable to create backup folder from TWRP, can't take OTA, or anything

I've been struggling with my phone from day 1- hopefully someone here has experienced and solved some of what I've been facing.
First some info:
I have a non-rooted XPE 1575 with an unlocked bootloader. I have never been able to receive an OTA update and needed to install 6.0 using a clean install of a stock ROM. I now can not successfully install the security OTA update (i get a dead Andy 'Error'). I have flashed stock recovery, boot image, and system chunks. No luck.
More alarming to me (and possibly a hint at what is going on) is that i can not even back up my phone using TWRP (v2.8.7.0). My internal memory is too small for this, so when i try backing up to my 128 GB sdcard (formatted to be adaptable), i get the following error E: Unable to create folder: /external_sd/TWRP/BACKUPS (errorno=5) E: Failed to make backup folder.
So, i can't stay 'stock-like' and just use OTA updates, and i can't backup my phone and then try to install a clean updated ROM.
Any ideas from anyone?

Try using the latest twrp.

Wow- I thought I was on the latest. I actually had it downloaded, but for some reason flashed the older one. The new version resolved this issue and I now have a backup, so I'm in good shape. Thanks so much!
lafester said:
Try using the latest twrp.
Click to expand...
Click to collapse

Honor 6 PLUS - NEW UPDATE!!

Hello everyone, today for the Honor 6 Plus is a new OTA is the C432B571 some people have jumped him via OTA and others not so you can download the update I put and upgrade to the latest version which is the PE-TL10C432B571.
Instructions: download, unzip and copy the folder dload update.app in SD.
LINK http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v55895/f1/full/update.zip

Awesome..!! This is just like the B190 OTA update for Honor 7.
So they are updating the Lollipop version for their devices too, this is the first approach like this I have seen.

This is an update improving mm is passed from the B560, B571 this new update

Does this work on honor 6 too?

Dynos said:
Does this work on honor 6 too?
Click to expand...
Click to collapse
No, it's for the plus

Damn, any word on when h6 gets this?

I'm on the PE-TL10C432B560 but when I tried to update it gave me "FAILED TO UPGRADE" and I was forced to restart my H6+.
Did you get the same error?
I placed my update.app in a dload folder, inside my External SD Card.
Thanks in advance

fefferico said:
I'm on the PE-TL10C432B560 but when I tried to update it gave me "FAILED TO UPGRADE" and I was forced to restart my H6+.
Did you get the same error?
I placed my update.app in a dload folder, inside my External SD Card.
Thanks in advance
Click to expand...
Click to collapse
Have you stock boot and recovery partitions? No root?
If you have, you must remove Supersu (select full unroot), flash stock partitions and then do the update.
If you don't have root, consider first and foremost a backup with Huawei Backup. Then download the zip file from here and follow the instructions.

zinko_pt said:
Have you stock boot and recovery partitions? No root?
If you have, you must remove Supersu (select full unroot), flash stock partitions and then do the update.
If you don't have root, consider first and foremost a backup with Huawei Backup. Then download the zip file from here and follow the instructions.
Click to expand...
Click to collapse
Thanks a lot mate!
With the link you provided I was able to successfully upgrade my H6+
Anyway I'm still official, no root, no unlocked bootloader.... strange considering that I lost my MotoG1 warranty after a week
Thanks again

I have downloaded the zip (didn't extract it) and i have created /dload file in internal memory and put that zip inside it, then i have open updater and select that zip and my 6+ enter in installing mode, but it stuck at 99% and it doesn't continue, someone knows whats wrong with it ?

You should have extracted it.
Extract the zip file unitl you have an update.app and put this into your dload folder. Then try updating again with force update method. If this doesn´t work

zinko_pt said:
Have you stock boot and recovery partitions? No root?
If you have, you must remove Supersu (select full unroot), flash stock partitions and then do the update.
If you don't have root, consider first and foremost a backup with Huawei Backup. Then download the zip file from here and follow the instructions.
Click to expand...
Click to collapse
Hello Zinko_pt,
I have the PE-TL10C900B331 and my phone shows me the PE-TL10C432B571 to update. If I run the automatic update it is not working. At 1% the installing stops and phone reboots.
I tried the german site with the zip and force installing but it is the same
Could you help me? No root phone
Thank you in advance

ofczi said:
Hello Zinko_pt,
I have the PE-TL10C900B331 and my phone shows me the PE-TL10C432B571 to update. If I run the automatic update it is not working. At 1% the installing stops and phone reboots.
I tried the german site with the zip and force installing but it is the same
Could you help me? No root phone
Thank you in advance
Click to expand...
Click to collapse
First I would try to get an update file that I could check its integrity either by MD5 or other form of verification. That would ruled out corrupted file cause.
Second, I would backup all my important things with native Huawei backup app into SD or PC. The I would perform a factory reset and setup just the Google account and Huawei ID if your ROM has one. Also setup HiCare app. Make sure all are updated. Then try to check update and if it works, great, if it doesn´t then try force update.
Only after update I would restore backup.

May I please ask what are the changes in this update? I am a huawei honor 6 plus user.
Thank you in advance for your response!

Does this work on PE-TL10C185B561 ?
As i worked on the steps but it stops at 5% although there is enough free space & battery charge

assemaskar said:
Does this work on PE-TL10C185B561 ?
As i worked on the steps but it stops at 5% although there is enough free space & battery charge
Click to expand...
Click to collapse
No, only it works in PE-TL10C432

zinko_pt said:
First I would try to get an update file that I could check its integrity either by MD5 or other form of verification. That would ruled out corrupted file cause.
Second, I would backup all my important things with native Huawei backup app into SD or PC. The I would perform a factory reset and setup just the Google account and Huawei ID if your ROM has one. Also setup HiCare app. Make sure all are updated. Then try to check update and if it works, great, if it doesn´t then try force update.
Only after update I would restore backup.
Click to expand...
Click to collapse
Thanks it works! Factory reset was needed. I think the problem was, that I encrypted the phone itself before.

ofczi said:
Thanks it works! Factory reset was needed. I think the problem was, that I encrypted the phone itself before.
Click to expand...
Click to collapse
From my experience, encrypted phones don´t go along with automatic turn on/off and updates.

oh.joan said:
May I please ask what are the changes in this update? I am a huawei honor 6 plus user.
Thank you in advance for your response!
Click to expand...
Click to collapse
If you're already on MM, it's just bug fixes and optimizations

Hi
my device run on PE-TL10C185B510, does this update work and what new features it will add?

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

Honor 8 FRD-L04 B385 update?

I just randomly went to firmware finder to refresh and found a new update for the FRD-L04, did anyone attempt to install this yet?
EDIT: I tried to install it through firmware finder and it didn't pass the verification at the end
https://drive.google.com/open?id=0B4baHcoSeBbgY21CVjlPNk45YlE
https://drive.google.com/open?id=0B4baHcoSeBbgYTZiR1ZDeUpoWnc
https://drive.google.com/open?id=0B4baHcoSeBbgV0g3ejBlMXlzdkk
I have downloaded the 3 zips in this update and verified the md5 they are all good if someone figures out how to install this

krchi said:
I just randomly went to firmware finder to refresh and found a new update for the FRD-L04, did anyone attempt to install this yet?
Click to expand...
Click to collapse
I found the same... Gonna try!

Jessooca said:
How did that work out for you Jorge??
Sent from my FRD-L04 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hi!
I tried but didnt worked. There´s no option to begin the update in the app...

JorgeCS said:
Hi!
I tried but didnt worked. There´s no option to begin the update in the app...
Click to expand...
Click to collapse
Top right download full update it'll download once you hit that and remove the proxy but it won't get authorized when you go to install it.

Well the good news I see out of this even if we cannot install is that the update is finally coming after 2 months of the other versions enjoying it for that long. Hopefully it fixes the battery drain.
Sent from my FRD-L04 using Tapatalk

Received the OTA update for the B380 version on my FRD L09C185 yesterday. But no notable change in the battery life till now.

krchi said:
Top right download full update it'll download once you hit that and remove the proxy but it won't get authorized when you go to install it.
Click to expand...
Click to collapse
Yep, you can't install this...

Can you install the full firmware from B162 though?

Gus194 said:
Can you install the full firmware from B162 though?
Click to expand...
Click to collapse
You can try and tell us

Thanks for the find! Your file sizes are off unfortunately, they should be:
400MB - update_data_full_public.zip
622MB - update_full_FRD-L04_hw_usa.zip
1.3GB - update.zip
Here are the correct files: https://drive.google.com/open?id=0B0zE1Kk8sIB6M2R4QUVsN3JBOGs

Jessooca said:
So the 622mb update file is the correct B385 update file? Can i push it to the phone via adb? Or what's the best way to install it??
Click to expand...
Click to collapse
Likely you'd push both update.zip and the region specific zip to where the stock recovery is expecting, then from a powered-off state use the key combinations to force-udpate. I'm unsure why there are 3 zips this time though since B360 was only 2 zips, I haven't had time yet to look at the contents.

Telperion said:
Thanks for the find! Your file sizes are off unfortunately, they should be:
400MB - update_data_full_public.zip
622MB - update_full_FRD-L04_hw_usa.zip
1.3GB - update.zip
Here are the correct files: https://drive.google.com/open?id=0B0zE1Kk8sIB6M2R4QUVsN3JBOGs
Click to expand...
Click to collapse
Mines was just the OTA files you have the full ota files

Jessooca said:
Did you install the update you found?
Click to expand...
Click to collapse
I tried.

I think you have to extract the update.app and do the update via recovery....if I remember correctly. I'd do it now but no USB-C cable here at work...

usmcnyc said:
I think you have to extract the update.app and do the update via recovery....if I remember correctly. I'd do it now but no USB-C cable here at work...
Click to expand...
Click to collapse
Tried that, compatibility error.

Telperion said:
Tried that, compatibility error.
Click to expand...
Click to collapse
:crying:
---------- Post added at 03:30 PM ---------- Previous post was at 02:44 PM ----------
In theory, we could also just extract the recovery.img, system.img and vendor.img and flash via fastboot.....or no? I know that's generally the way I've flashed things on my Shield TV

usmcnyc said:
:crying:
---------- Post added at 03:30 PM ---------- Previous post was at 02:44 PM ----------
In theory, we could also just extract the recovery.img, system.img and vendor.img and flash via fastboot.....or no? I know that's generally the way I've flashed things on my Shield TV
Click to expand...
Click to collapse
Just tried that too, boot, recovery, and system will flash but vendor fails. When I load to the system it still shows B360 but certain parts of the OS don't work -- can't access Developer Options, for example. It seems as if this package just doesn't work right.
Update: If anybody else wants to attempt it, remove all PIN/password protection first. I had to factory reset.

Telperion said:
Just tried that too, boot, recovery, and system will flash but vendor fails. When I load to the system it still shows B360 but certain parts of the OS don't work -- can't access Developer Options, for example. It seems as if this package just doesn't work right.
Update: If anybody else wants to attempt it, remove all PIN/password protection first. I had to factory reset.
Click to expand...
Click to collapse
Sounds like we're stuck...thanks for trying all that though, saved me a huge headache...

usmcnyc said:
Sounds like we're stuck...thanks for trying all that though, saved me a huge headache...
Click to expand...
Click to collapse
Of note is that the 72309 firmware (B360) zips can be flashed from TWRP with no issue. This zip however fails to install.
Things I tried which failed:
Unpacking UPDATE.APP and force-updating from /external_sd/dload/ folder
Flashing extracted images from bootloader*
Modifying updater-script and flashing in TWRP (mountencrypt was throwing an error, others too)
Updating updater-script and update-binary and flashing in TWRP (same errors)
Flashing images from bootloader, boot and system worked but vendor failed, but the device did boot. It didn't, however, show the new software version -- but that may be because the software version is read from the vendor partition which wouldn't flash. In any event, flashing this way the device was unstable. I couldn't set a screen PIN and Developer Options would crash the Settings menu when I attempted to access it.
Someone more skilled than me would need to extract the contents of all 3 zips and make one TWRP-flashable zip.

Telperion said:
Of note is that the 72309 firmware (B360) zips can be flashed from TWRP with no issue. This zip however fails to install.
Things I tried which failed:
Unpacking UPDATE.APP and force-updating from /external_sd/dload/ folder
Flashing extracted images from bootloader*
Modifying updater-script and flashing in TWRP (mountencrypt was throwing an error, others too)
Updating updater-script and update-binary and flashing in TWRP (same errors)
Flashing images from bootloader, boot and system worked but vendor failed, but the device did boot. It didn't, however, show the new software version -- but that may be because the software version is read from the vendor partition which wouldn't flash. In any event, flashing this way the device was unstable. I couldn't set a screen PIN and Developer Options would crash the Settings menu when I attempted to access it.
Someone more skilled than me would need to extract the contents of all 3 zips and make one TWRP-flashable zip.
Click to expand...
Click to collapse
There's a 1.9gb OTA on firmware finder...I'd download it here at work but the internet is too slow, it'd take hours.

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