So I figured I would just get into it and say that I'm new to this all, I have been doing it for some time now and I thought I had it figured out. But now I got myself stuck into a problem I don't know how to fix, I have the Galaxy S7 Edge SM-G935W8, I was trying to unlock it threw 123unlock for SRS Samsung Unlock. I paid for it threw Sammobile. What I did was on one of the options was, they let me use ADB Toolbox and there was an option to Write a backup of my EFS?. At first I didn't even know what that fully meant. so what it actually did was try to put an EFS on the phone. So because I did it wrong my phone wont even boot up anymore it will go to the Samsung pop up screen and it can only be in Download mode or in Recovery either Stock or TWRP even tried Smart Switch but it keeps saying my phone isn't supported, I tried it all from flashing stock rom to custom. All the time I keep getting back the same error which is
"No Support SINGLE-SKU
Supported API: 3
E:Failed to mount /efs (Invalid Argument)
E:Failed to mount /efs (Invalid Argument)
E:Failed to mount /efs (Invalid Argument)
dm-verity error..."
that exact way is how it is on my phone I'm lost and actually don't know what to do now someone help please.
Well that error is similar to what I get. Is it dual sim? Whats the device status in about phone -> software information?
UnNaMeD__ said:
Well that error is similar to what I get. Is it dual sim? Whats the device status in about phone -> software information?
Click to expand...
Click to collapse
I Actually Figured it out how, I flashed it threw twrp and went under terminal and changed the permissions, Because threw stock recovery I looked threw the recovery log and i figured out that the reason was that the error was just because of permissions, so i decided to find the path where the permission was for the EFS file and i change the permission with "chmod u=rxw" after i changed the permission it was able to boot, but the only thing was that the EFS is completly gone so now what im trying to do is go back to normal stock but flash no-verity with twrp then hoping that i would be able to restore it with smart switch update after it realises that its a samsung.
lhkb96 said:
I Actually Figured it out how, I flashed it threw twrp and went under terminal and changed the permissions, Because threw stock recovery I looked threw the recovery log and i figured out that the reason was that the error was just because of permissions, so i decided to find the path where the permission was for the EFS file and i change the permission with "chmod u=rxw" after i changed the permission it was able to boot, but the only thing was that the EFS is completly gone so now what im trying to do is go back to normal stock but flash no-verity with twrp then hoping that i would be able to restore it with smart switch update after it realises that its a samsung.
Click to expand...
Click to collapse
Oh alright thanks for info! Good luck to you. I know how it feels when you are without EFS lol, once I fixed it by flashing stock ROM from Odin.
UnNaMeD__ said:
Oh alright thanks for info! Good luck to you. I know how it feels when you are without EFS lol, once I fixed it by flashing stock ROM from Odin.
Click to expand...
Click to collapse
I tried that as well by flashing but for some reason I always get an error from the boatloader for under BL it never works but for AP, CP and CSC will work but the boatloader won't for some reason
Related
I've searched for a good three hours now and can't find a solution. Here's my problem, I got root, I got TWRP, I tried to install cyanogenmod, when it's installing it just stops and says FAILED in big red letters. The small letters say error executing update binary in "cyanogenmod.zip" I tried rebooting into android it just goes back to twrp. ive tried reflashing the .zip, same error. I've tried every flash to stock method I could find and those get stuck on the attached picture's step. I'm really close to giving up and am very frustrated. please help thanks. Oh and i have the att version.
I'm having a very similar problem. I was able to install TWRP just fine. However, during the installation of Cyanogenmod 10.2, it gave me these error messages: "assert failed: run_program("/sys/bin/loki.sh," "E:Error executing updater binary in zip '/sdcar", and "Error flashing zip '/sdcard/cm-10.2.0-d800.zip.'" Now, whenever I turn my phone on, it displays the LG logo with "Security Error" written underneath it. I tried doing a factory reset in TWRP, but that didn't fix the problem.
Here's loki.sh:
Code:
#!/sbin/sh
#
# This leverages the loki_patch utility created by djrbliss which allows us
# to bypass the bootloader checks on jfltevzw and jflteatt
# See here for more information on loki: https://github.com/djrbliss/loki
#
export C=/tmp/loki_tmpdir
mkdir -p $C
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=$C/aboot.img
/system/bin/loki_patch boot $C/aboot.img /tmp/boot.img $C/boot.lok || exit 1
/system/bin/loki_flash boot $C/boot.lok || exit 1
rm -rf $C
exit 0
Edit:
I ended up using this guide to revert my G2 to its original state. While I'm not sure why Cyanogenmod failed to install, I suspect it may be because the version I used was not designed for the most recent OTA update (10o).
jtmaher said:
I'm having a very similar problem. I was able to install TWRP just fine. However, during the installation of Cyanogenmod 10.2, it gave me these error messages: "assert failed: run_program("/sys/bin/loki.sh," "E:Error executing updater binary in zip '/sdcar", and "Error flashing zip '/sdcard/cm-10.2.0-d800.zip.'" Now, whenever I turn my phone on, it displays the LG logo with "Security Error" written underneath it. I tried doing a factory reset in TWRP, but that didn't fix the problem.
Here's loki.sh:
Code:
#!/sbin/sh
#
# This leverages the loki_patch utility created by djrbliss which allows us
# to bypass the bootloader checks on jfltevzw and jflteatt
# See here for more information on loki: https://github.com/djrbliss/loki
#
export C=/tmp/loki_tmpdir
mkdir -p $C
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=$C/aboot.img
/system/bin/loki_patch boot $C/aboot.img /tmp/boot.img $C/boot.lok || exit 1
/system/bin/loki_flash boot $C/boot.lok || exit 1
rm -rf $C
exit 0
Edit:
I ended up using this guide with the AT&T files mentioned in this guide to revert my G2 to its original state. However, I still have no idea why Cyanogenmod failed to install.
Click to expand...
Click to collapse
Did you use flashtool 1.8 or 1.5? I'll try this out today. thanks.
Bjangles said:
I've searched for a good three hours now and can't find a solution. Here's my problem, I got root, I got TWRP, I tried to install cyanogenmod, when it's installing it just stops and says FAILED in big red letters. The small letters say error executing update binary in "cyanogenmod.zip" I tried rebooting into android it just goes back to twrp. ive tried reflashing the .zip, same error. I've tried every flash to stock method I could find and those get stuck on the attached picture's step. I'm really close to giving up and am very frustrated. please help thanks. Oh and i have the att version.
Click to expand...
Click to collapse
I just had the same problem, on the T-Mo. I was able to restore from the back up I had just created. I saw today the cm had an m release of cm11. Tried installing and it failed. Tried rebooting went right back into recovery. Scared the crap out of me. But I'm back up and running. A little sad that it didn't work I miss cm. Is it possible that my Loki I flashed not 30 minutes ago didn't work?
chasingeuphoria said:
I just had the same problem, on the T-Mo. I was able to restore from the back up I had just created. I saw today the cm had an m release of cm11. Tried installing and it failed. Tried rebooting went right back into recovery. Scared the crap out of me. But I'm back up and running. A little sad that it didn't work I miss cm. Is it possible that my Loki I flashed not 30 minutes ago didn't work?
Click to expand...
Click to collapse
I think it was just a bad download. Unfortunately, I wasn't smart enough to make a backup before I tried to install CM. I tried the other guys fix and it worked for me.
I can't find anything, anywhere else about this. I would like to find more information before I do it again. Not sure if I could handle that again. I've never had this happen before.
Sent from my LG-D801 using XDA Premium 4 mobile app
Bjangles said:
I think it was just a bad download. Unfortunately, I wasn't smart enough to make a backup before I tried to install CM. I tried the other guys fix and it worked for me.
Click to expand...
Click to collapse
I don't think it was a bad download. I think it has something to do with the recovery. But I've searched and searched can't find anything. Don't want to ask here because if it has been asked here before it would cause an uproar. Lol. Anyway prolly going to give up. I do miss CyanogenMod. But I'm obviously not smart enough
I posted in a Q&A thread last week about the same issue. Once you take an update (10o for at&t) your boot.img is changed and won't be recognized when trying to flash. If you revert back to stock, you should be able to regain root, install recovery and flash.
Edit: found the thread. datechnerd even posted some modified roms for 10o. I think he did same for other variants.
http://forum.xda-developers.com/showthread.php?t=2589381
Sent from my LG-D800 using xda app-developers app
Hi every one! First thing I'm so sorry for not strong english language.
And this is the first post for me.
Let's the problem. I buy Nexus4 from one man in http://www.overclockzone.com/forums/forumdisplay.php/168-LG
it's Thai website. He provide Nexus4 but It have not Imei and baseband unknown that's means can't call or used gps.
I think I can solved this solution cause my old mobile is Galaxy s(SC-02b) and I learn how to update rom or used in other country by flash modem from http://forum.xda-developers.com/showthread.php?t=1614417.
The first i thinking just flash modem or radio.
But It's not easy I tried in many solution also http://forum.xda-developers.com/showthread.php?t=2347060
all still baseband unknown . This is my notice this device
1.Model - ZNFE960 (Made in Korea)
2.When i got this device it's used miui rom not problem except baseband unknown with 4.2.2 (JDQ39) and franco kernel r195
3.I can back to stock rom just 4.2.2 (JDQ39).The newer 4.3 (JWR66Y) and 4.4(KRT16S) It's not work bootloop but i didn't try 4.4.2 (KOT49H)
4.The boot loop of stock rom 4.3 or 4.4 after then i get into recovery mode for wipe data it have this status before
E:Can't mount/cache/recovery/log
E:Can't open/cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount/cache/recovery/last_log
E:Can't open/cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount/cache/recovery/last_install
E:Can't open/cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
and when I wipe data and cache. The status for wipe show below that message but still boot loop and I get into recovery mode again that message not show but show status of wipe data (still boot loop)
5.Baseband version on fastboot was show
6.When I flash radio . It's update on fastboot but still baseband unknown
7.It's unlock bootloader every time although get factory image
8.It's ota update 4.3 when i connected wifi . if it's download successfull then show notification all the time.
9.If I restart and install, It's stuck Android upgrading is starting apps.Although I wipe data it still bootloop.(but not show error message like (4))
10.In Root folder.There are many folder are empty as cache,config,data,firmware,persist and sbin.
solve solution and suggest me please.........:good:
I would start here:
http://forum.xda-developers.com/showthread.php?t=2015469
Wugfresh's toolkit has assisted many N4 owners with returning their phones to stock, gaining root, custom recoveries and unlocking. It will also help you to get the proper drivers.
Get it back to factory stock. Once there, root and install a custom recovery.
The toolkit will download whatever drivers it needs, updated SU, whatever version of stock you want and the custom recovery you want to use.
Sent from my Nexus 4 using Tapatalk
ph37rd said:
I would start here:
http://forum.xda-developers.com/showthread.php?t=2015469
Wugfresh's toolkit has assisted many N4 owners with returning their phones to stock, gaining root, custom recoveries and unlocking. It will also help you to get the proper drivers.
Get it back to factory stock. Once there, root and install a custom recovery.
The toolkit will download whatever drivers it needs, updated SU, whatever version of stock you want and the custom recovery you want to use.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thank you for suggestion. I tried to use it before . the custom recovery works but still not help baseband and imei
Has to do with originating country the phone was released in & the country you're trying to use the phone in.
Return it if you can...If you can't return it I'd say your probably toast unfortunately.
Google it...there are a lot of people that have never found a solution to it.
mrhiab said:
Has to do with originating country the phone was released in & the country you're trying to use the phone in.
Return it if you can...If you can't return it I'd say your probably toast unfortunately.
Google it...there are a lot of people that have never found a solution to it.
Click to expand...
Click to collapse
thank you very much for this suggestion . Yes I can't return to original country. The device from Hongkong but i stay in Thailand . What a problem why i can't used it .
why my old phone galaxy s (sc-02b) from japan. It's lock carrier network but i just type mmc/mnc . That stock rom of sc-02b it always have baseband version all time but in custom rom as cm10.1 or another maybe not have just flash kernel and modem in it.
Remark it , the mobile in engineer mode (mtk) it have 4 option are
phone inforation
battery information
Usage statics
wi-fi information
It's a normally? it's not have telephony?
I think it my mobile lost imei.and i want to flash imei but not have option . And I doubt about hardware failed maybe losse wire network or
the simcard's tray not connect with board or dirty.i will find to buy screwdriver and try it.
Thank you very much mrhiab
Hello everyone!
A few days ago I bought myself a P10 plus on a vacation to China. Since I live in Sweden I decided to rebrand it to the European firmware (since it had the asian firmware installed) through FunkyHuawei when I got home. I got my bootloader code from Huawei support and succesfully unlocked it as well as installed TWRP. The first problem I encountered was that I was unable to create any backups of my phone as well as being unable to install or flash anything.
I then restarted my phone into recovery mode and suddenly it didn't boot into TWRP anymore, only EMUI stock recovery. I tried flashing TWRP several times but the phone still wouldn't boot into it, so I tried factory resetting the phone and the flashing TWRP once again. This is where the real problems started.
The firmware is gone, no OS is installed, I cannot do anything through TWRP (i only get error messages such as "E:Unable to find partition size for /boot" as well as Failed to mount /cache (Invalid Argument)")
Even worse is that the bootloader wont load as far as i can tell so I can't do anything through adb nor fastboot either. I'm completely stuck in TWRP. I can't even wipe nor change file system.
Is my phone damaged beyond repair or is there anyone on here that might have a solution?
Thanks in advance, any suggestions welcome!
EDIT: Okay this is really weird...
Suddenly my phone booted into the OS, even though TWRP said there were no OS installed. What is the next step from here to ensure this won't happen again?
Check this thread can help you to restore to stock firmwares anytime and even update ur phone.https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page44
jkrz said:
Hello everyone!
A few days ago I bought myself a P10 plus on a vacation to China. Since I live in Sweden I decided to rebrand it to the European firmware (since it had the asian firmware installed) through FunkyHuawei when I got home. I got my bootloader code from Huawei support and succesfully unlocked it as well as installed TWRP. The first problem I encountered was that I was unable to create any backups of my phone as well as being unable to install or flash anything.
I then restarted my phone into recovery mode and suddenly it didn't boot into TWRP anymore, only EMUI stock recovery. I tried flashing TWRP several times but the phone still wouldn't boot into it, so I tried factory resetting the phone and the flashing TWRP once again. This is where the real problems started.
The firmware is gone, no OS is installed, I cannot do anything through TWRP (i only get error messages such as "E:Unable to find partition size for /boot" as well as Failed to mount /cache (Invalid Argument)")
Even worse is that the bootloader wont load as far as i can tell so I can't do anything through adb nor fastboot either. I'm completely stuck in TWRP. I can't even wipe nor change file system.
Is my phone damaged beyond repair or is there anyone on here that might have a solution?
Thanks in advance, any suggestions welcome!
EDIT: Okay this is really weird...
Suddenly my phone booted into the OS, even though TWRP said there were no OS installed. What is the next step from here to ensure this won't happen again?
Click to expand...
Click to collapse
You should see if you have the UFS memory or eMMC.
If you have eMMC version the current available TWRP is not working.
I made a testing version for TWRP that works on eMMC and was able to rebrand from China to International.
PM me if you need anything..
So i've gotten my phone working again (with the chinese ROM) but since TWRP won't work there's no way for me to rebrand it. My phone has eMMC 5.0 if that's any help.
MosquitoByte said:
You should see if you have the UFS memory or eMMC.
If you have eMMC version the current available TWRP is not working.
I made a testing version for TWRP that works on eMMC and was able to rebrand from China to International.
PM me if you need anything..
Click to expand...
Click to collapse
can you share the TWRP works in eMMC plz . many thanks
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....
Traing to flash combanishin rom for sm g928f the odin stop on (set partion) then i plug the device but it boot on this screen
No support single-sku
Dm-verity error
Faild code :0x02
E:failed to mount/cache ( invalid argument)
E:cant mount /cache/recovery/last_locale
Thanks for every one who vewed my post ...i fixed it alhamd llah (thanks my god)
mishrag said:
Thanks for every one who vewed my post ...i fixed it alhamd llah (thanks my god)
Click to expand...
Click to collapse
How? i have same problem
can you share to us how you fixed it? i have the same problem.
mishrag said:
Thanks for every one who vewed my post ...i fixed it alhamd llah (thanks my god)
Click to expand...
Click to collapse
Please tell us how you fixed the problem. I have a similar issue on a galaxy a510fd
rmunene said:
Please tell us how you fixed the problem. I have a similar issue on a galaxy a510fd
Click to expand...
Click to collapse
He flashed stock firmware to fix it. To avoid that issue you have to already have the root zip like Su on internal memory when you flash TWRP. And boot into recovery once it finishes and flash root. If that fails flash a custom ROM then root
Hey Please help, I have the same problem on a Galaxy J5
I have the same problem on j510H its not accepting the correct pattern and keeps restarting after maybe 1 minute i can't wipe neither can reset it telling me E failed to open dev block....... I flashed stock via odin its passed but when phone restarted it telling me no command and i see the old rom is there with no change