Related
I apologize for the Noob question(s), but does anyone know if the **.zip.md5sum** file as listed below needs to be flashed in conjunction with the actual Rom? If so, do they need to be flashed in a particular order? I haven't been doing so since it appears to be a blank file based on the size. I only ask because ever since switching to OmniRom from GummyRom, my phone seems to get stuck at the Samsung logo screen. About half the time it requires a battery pull because my phone seems to just be stuck at boot. I'm using the latest version of CWM and have read in the Omni thread that switching to the latest version of TWRP resolved the problem. I am just curious if others are or have experienced this problem and what they did to resolve it?
Lastly, I know this is more like a three part question and if I have to post it in another thread I will. But I did try to install TWRP from the Goo Manager app and when the download page loads it doesn't install anything. The page just says it's preparing my download, but doesn't download anything. Any thoughts or suggestions would be greatly appreciated...
I am using a Verizon Galaxy S4
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip 2013-12-08 18:40 193587 KB
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum 2013-12-08 18:40 0 KB
droidzen10 said:
I apologize for the Noob question(s), but does anyone know if the **.zip.md5sum** file as listed below needs to be flashed in conjunction with the actual Rom? If so, do they need to be flashed in a particular order? I haven't been doing so since it appears to be a blank file based on the size. I only ask because ever since switching to OmniRom from GummyRom, my phone seems to get stuck at the Samsung logo screen. About half the time it requires a battery pull because my phone seems to just be stuck at boot. I'm using the latest version of CWM and have read in the Omni thread that switching to the latest version of TWRP resolved the problem. I am just curious if others are or have experienced this problem and what they did to resolve it?
Lastly, I know this is more like a three part question and if I have to post it in another thread I will. But I did try to install TWRP from the Goo Manager app and when the download page loads it doesn't install anything. The page just says it's preparing my download, but doesn't download anything. Any thoughts or suggestions would be greatly appreciated...
I am using a Verizon Galaxy S4
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip 2013-12-08 18:40 193587 KB
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum 2013-12-08 18:40 0 KB
Click to expand...
Click to collapse
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
It should not be flashed.
Its been a while since I used the twrp check-sum someone correct me if wrong.....I verify the MD5 before i put the rom on phone to ensure its a good download.
GooManager has always been flaky on my Skyrocket and on my buddies S3, but that is just me talking, nothing against goomanager. That being said I have always preferred to flash recoveries from the recovery, or odin this ensures (me) that the flash went well.
You can almost always find a zip of the latest recovery for your phone in one of the development threads or you can ask on the S4 Q&A thread if someone has one or if they can get you one. I haven't been to your forum but i'm sure there is a TWRP thread to follow.
OmniRom flashing question
Tweakecho said:
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
It should not be flashed.
Its been a while since I used the twrp check-sum someone correct me if wrong.....I verify the MD5 before i put the rom on phone to ensure its a good download.
GooManager has always been flaky on my Skyrocket and on my buddies S3, but that is just me talking, nothing against goomanager. That being said I have always preferred to flash recoveries from the recovery, or odin this ensures (me) that the flash went well.
You can almost always find a zip of the latest recovery for your phone in one of the development threads or you can ask on the S4 Q&A thread if someone has one or if they can get you one. I haven't been to your forum but i'm sure there is a TWRP thread to follow.
Click to expand...
Click to collapse
Thanks for your answer and suggestion regarding flashing a recovery. I've been doing a lot of reading here on XDA and quite a few have suggested using Flashify to flash recoveries....
Tweakecho said:
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
Click to expand...
Click to collapse
It doesn't work that way for me. I always put the files in the same folder but TWRP 2.6.3.3 always says that there is no md5 file to be found.
Riiquiem said:
It doesn't work that way for me. I always put the files in the same folder but TWRP 2.6.3.3 always says that there is no md5 file to be found.
Click to expand...
Click to collapse
It's because the file extension is wrong.
Zip md5 Verification (looks for file with zipname.zip.md5)
So, if you downloaded these files :
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum
You need to rename "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum" to "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5".
AngryHapposai said:
It's because the file extension is wrong.
Zip md5 Verification (looks for file with zipname.zip.md5)
So, if you downloaded these files :
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum
You need to rename "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum" to "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5".
Click to expand...
Click to collapse
That explains why mine always reports an error as well. *fixes all future build md5's
Having the same problem MD5 not found while flashing ROM. lemme try renaming. Will say again, if its work
I am currently running Kangakat 4.3 and am trying to update to 4.4.2. I am using TWRP 2.6.0.3 and have not had any issues with updating the ROM in the past. However this time I keep getting an Install Failed error message. I performed a factory reset and have downloaded the ROM from different sites however it does not matter. It still fails to update.
TWRP states unable to open ZIP file.
I updated to TWRP 2.6.3.0 and still receive unable to open zip file. I have downloaded the zip file from both the primary and mirror sites.
I am rather frustrated at this point and am hoping for some help.
AMG_Roadster said:
I am currently running Kangakat 4.3 and am trying to update to 4.4.2. I am using TWRP 2.6.0.3 and have not had any issues with updating the ROM in the past. However this time I keep getting an Install Failed error message. I performed a factory reset and have downloaded the ROM from different sites however it does not matter. It still fails to update.
TWRP states unable to open ZIP file.
I updated to TWRP 2.6.3.0 and still receive unable to open zip file. I have downloaded the zip file from both the primary and mirror sites.
I am rather frustrated at this point and am hoping for some help.
Click to expand...
Click to collapse
Have you tried to re-download the rom ? It could be a bad zip file and you just need to redo it.
hednik said:
Have you tried to re-download the rom ? It could be a bad zip file and you just need to redo it.
Click to expand...
Click to collapse
I tried downloading it to the phone multiple times and still encountered the install fail error.
Once I downloaded it to the computer and moved it over to the phone it installed without issue. I am not sure what the problem was but it is working now.
AMG_Roadster said:
I tried downloading it to the phone multiple times and still encountered the install fail error.
Once I downloaded it to the computer and moved it over to the phone it installed without issue. I am not sure what the problem was but it is working now.
Click to expand...
Click to collapse
That's been an issue in the past with many devices. Sometimes the rom you download on your phone just won't flash but always best to check the MD5 anyway. Glad it got ironed out.
I'm getting this error when trying to flash lollipop roms. I can flash Kitkat roms fine as I'm currently running xdabbeb VS982.5 1.0.0 (G3 rom), but it won't let me flash any lollipop rom. I installed twrp via the autorec program which installs 2.7.0.0 then I updated twrp within twrp with the flashable zip.
Please help
Thank you
Anyone?
Seriously no one knows? What is everyone else using that is flashing the latest 5.0.2 roms?
What am I getting this error?
Please help
Possible Fix
I've also had this problem. The only way I can seem to fix it is to also download the .md5 along with the rom itself. Just make sure its in the same folder as the rom. Everytime I have that problem with TWRP this seems to fix it. Let me know if it works for you!
Edit: Also I forgot to mention, if one isn't available to download I can help with that.
Thanks for the suggestion. I'll give it a try. If there is no. Md5 what do I do then?
All you need to do if it comes to that is download an md5 checker on your computer. Just curious, what rom are you trying to flash?
I tried resurrection remix and liquid lollipop roms. I had no issues with the initial 5.0 lollipop roms so I'm not sure what changed with 5.0.2.
So the md5 checker generates the .Md5 then you just put that on the SD card with the rom?
Resurrection remix should have an md5 on the download page right below the rom itself.
derekmt95 said:
All you need to do if it comes to that is download an md5 checker on your computer. Just curious, what rom are you trying to flash?
Click to expand...
Click to collapse
Can you point me to the program to use on my computer? Do I just load the .zip file in the program to generate the .md5sum file then put both the zip and the .md5sum file on the sdcard before flashing?
Thanks
derekmt95 said:
I've also had this problem. The only way I can seem to fix it is to also download the .md5 along with the rom itself. Just make sure its in the same folder as the rom. Everytime I have that problem with TWRP this seems to fix it. Let me know if it works for you!
Edit: Also I forgot to mention, if one isn't available to download I can help with that.
Click to expand...
Click to collapse
Nope, I downloaded the md5 file along with the zip and I'm still getting the same "error executing updater binary in zip".
Any other suggestion? How is no one else having this same issue? I'm using the latest version of TWRP 2.8.3.1 probably like most people. I don't understand.
xxNiradxx said:
Nope, I downloaded the md5 file along with the zip and I'm still getting the same "error executing updater binary in zip".
Any other suggestion? How is no one else having this same issue? I'm using the latest version of TWRP 2.8.3.1 probably like most people. I don't understand.
Click to expand...
Click to collapse
Try to reflash the TWRP.. or maybe is something wrong with the zip file
Use the TWRP compiled by blastagator
Nope, still getting same error with latest twrp.
Finally got it working. I downgraded TWRP to 2.7.0.0 and the lollipop roms are flashing fine now.
Thanks everyone for your help.
xxNiradxx said:
Finally got it working. I downgraded TWRP to 2.7.0.0 and the lollipop roms are flashing fine now.
Thanks everyone for your help.
Click to expand...
Click to collapse
How did you downgrade because I cannot seem to find a way to do it.
TheAnonymousButler said:
How did you downgrade because I cannot seem to find a way to do it.
Click to expand...
Click to collapse
just run AutoRec again and you are all set.
LG G2 cm-11 M12 : Error executing updater binary in zip (TWRP)
kashif87 said:
just run AutoRec again and you are all set.
Click to expand...
Click to collapse
Hi, I am having the same problem. Actually my LG G2 was stuck in boot loop with secure boot error. I used SRK tool to flash the partition files as well as TWRP recovery 2.8.6.1. I have wiped everything and there is no OS installed. I am stuck in TWRP recovery screen [cannot downgrade /upgrade]. I am using and OTG cable to flash the cm-11 custom ROM but it is giving me the same error. Can anyone help ?? It has been 10 days I am trying and my phone is dying please help...
Thanks in advance...
before flash 5.1.1 aosp lollipop rom u must to flash first lollipop bootstack
Hi,
I am assuming the reply was for me. Actually I am not installing lollipop. I am going for kitkat but nothing is working now. I have tried cm-10.2, cm-11 M12, cm-11 M7 but all are showing "error executing updater binary in zip". Please if someone can help me out....
Thanks is advance....
@[email protected] i think kk aosp room need jb bootleader
Hello everyone,
I am running a D802 on stock Lollipop and installed TWRP 2.8.6.0 via AutoRec. Now I booted into recovery, wiped System and Cache and got the Error message when installing CrDroid (Marshmallow 6.0.1). Now I tried installing TWRP 3.0.2.0, which succeeded and then downloaded the twrp 2.7.0.0 zip to try that as the ROM still wouldnt install. But it wont install the older TWRP. So I am asking for help to either
1) Install TWRP 2.7.0.0
or
2) Delete the getprop lines from updater-script (after I removed them I get an error 6 so i probably removed too much?)
Thank you in advance
(Guide for Error 7: http://forum.xda-developers.com/showthread.php?t=2522762)
EDIT: Someone said installing another Kernel might allow installation of the ROMs. Which Kernel could work for my phone?
EDIT 2: When flashing TWRP 2.7.0.0 it says "assert failed: run_program("/tmp/loki.sh")==0". So what exactly am I missing on my phone? Is Loki the MM Bootloader?
EDIT 3: Could it be that the build.prop was deleted when I wiped system? Would be weird if that was the cause, but I simply dont know..
Edit: Booted in Downloa Mode and flashed v30D KDZ with the 2014 LG Flashtool. Works with Stock ROM for now
Every single one of the roms I've tried to install have failed during installation and have all said Zip corrupt. Any idea why this keeps happening? Is there another way to install these roms other than twrp and cwm. Could the transfer method of the Rom files have anything to do with the corrupt zips? I would greatly appreciate any helpful input from anyone.
@twistedshellz: before flash, check md5sum of downloaded zip and compare it with the one on downloadsite. If they differ, try another modem /pc /smartphone for downloading
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....