I've been trying to flash custom ROMs and TWRP, but haven't been able to. I can boot the TWRP image, but as soon as I try to flash the .zip file, it comes back with:
Failed to mount '/system (Invalid argument) ...done Failed to mount '/vendor (Invalid argument)
I can flash the stock firmware, via fastboot, but not custom ROMs, or TWRP. I have tried flashing stock boot image, and trying it again. Then I've tried erasing boot a and b, also flashing the stock firmware, and then TWRP. Ive been able to flash many ROMs in the past, but this just cropped up.
UPDATE: I think the problem is that, my device was originally a Verizon model. I used the adb method to unlock bootloader when it was on Android 9. I recently updated to the Dec firmware, and that's when my issues started. I can flash only the Dec patch. All others refuse to flash.
Related
I was trying to flash ecliptic ROM from PACMAN Rom and got a status 7 error during installation, the problem is that I had already erased my cache, data, and system before flashing. I cannot flash any roms without error messages now and whenever I try to format my system,cache, or data I get the error:
E:Unable to mount 'system'
E:Unable to mount '/cache'
Can anyone help me please? I have tried using clockworkmod recovery and every time I attempt to format it just freezes indefinitely.
Reboot recovery when you get in to recovery. There are some ROMs that the only way to flash them is to reboot the recovery.
Sent from my HTC One using Tapatalk
Did you just recently flash your current recovery? Sounds like you need to reflash your recovery, and make sure your using the correct one for the m7. Which recovery and version are you currently on?
Status 7 refers to either an error in the rom zips updater-script, or the rom zips updater-binary is not compatibe with your current recovery.
boot into recovery mode.
So , I was helping my buddy out with his Roger branded HTC One M8... He had the latest OTA, unlocked the bootloader, installed a custom recovery, and finally tried to flash ARHD 10.2.....
ARHD won't flash because it says it's a corrupt .ZIP.....
The Backup we made before flashing, recovers, then reboots back into recovery ( fails )
Any other ROM also says corrupt .ZIP...
Have never had an issue like this before, and I have no idea what to do from this point on....
Already tried recovering the backup & flashing a different ROM.
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Any help would be greatly appreciated! ( PHONE MODEL M8_UL )
What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
tutchthesky7 said:
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Click to expand...
Click to collapse
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.
redpoint73 said:
What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.
Click to expand...
Click to collapse
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S
tutchthesky7 said:
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S
Click to expand...
Click to collapse
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
Will try that and report back
redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
tutchthesky7 said:
Will try that and report back
Click to expand...
Click to collapse
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.
Did you fastboot erase cache before installing TWRP, as I suggested?
Sir_Kato said:
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.
Click to expand...
Click to collapse
the log got me thinking, after updating TWRP and then clearing the cache the mounting issue seemed wierd, so I tried sideloading to sdcard0 after clearing the cache once more then installing from sideload.zip on sdcard0, which entered the ARHD install GUI. so now I just need a confirmation on whether installing from sdcard0 is dangerous as a reformat mid install will erase the zip im trying to install from. soft brick is bad enough, really want to avoid an expensive paperweight.
I'm still in the menu, waiting for more seasoned minds to respond before I go through with it.
---------- Post added at 02:37 PM ---------- Previous post was at 02:29 PM ----------
redpoint73 said:
Did you fastboot erase cache before installing TWRP, as I suggested?
Click to expand...
Click to collapse
I did indeed. Just got the confirmation on the go ahead from OP. Better safe than sorry. Will post the outcome.
It worked beautifully, **** is so Cash. Thanks guys. you've been of great help.
Hi, XDA community.
I got this phone today and user reported that suddenly is boot looping until battery dies.
When trying to wipe, stock recovery prompted:
Code:
E:failed to mount /cache (Invalid argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid argument)
I tried the following so far:
============================================================================
(#1)
If I wipe data or cache I get a big FAIL message and then
Code:
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
cust copying files...
copy cust files system error!ret = -1
I have no info if it's running JB or KK, nor B116 or whatever (I assumed it might be running JB).
============================================================================
(#2)
I can ADB and FASTBOOT to it, but device cannot be recognized properly.
Code:
C:\huawei>adb.exe devices
List of devices attached
? recovery
C:\huawei>adb.exe reboot bootloader
C:\huawei>fastboot.exe devices
????????(?(???O?(???????(?(? fastboot
I think that the bootloader is locked.
Code:
C:\huawei>fastboot.exe oem get-bootinfo
...
(bootloader) locked
OKAY [ 2.201s]
finished. total time: 2.201s
I tried to unlock it with something I found somewhere and apparently it worked:
Code:
C:\huawei>fastboot oem unlock UUUUUUUUUUUUUUUU
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\huawei>fastboot.exe oem get-bootinfo
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
I tried to delete the stock recovery and install TWRP, some other Open Recovery, and it prompted OKAY.
However after rebooting to recovery, is gone, I faced the exact same stock recovery with the same E:failed to mount /cache (Invalid argument) and the big FAIL when trying to wipe.
When going back to ADB and FASTBOOT, the bootloader is back to locked status. I can unlocked again (somehow) with the UUUUUUU thing but I'm not sure if this is actually flashing something.
============================================================================
(#3)
I tried to download Ascend P6 Software (P6-U06,Android 4.4.2,Emotion UI 2.3,V100R001C00B520,Latin_North_America-Channel,05011SYH).zip from the main portal (I am located in LATAM).
http://consumer.huawei.com/ve/support/products/manuals/ascend-p6-ve.htm
I got a UPDATE.APP file of 1.61GB. I copied the file on a 4GB microSD leaving it on the root under dload folder, inserted on the phone and rebooted using VOL+ VOL- combination, not plugged on the USB.
It didn't work. I ended in the same stock recovery with the E:failed to mount /cache (Invalid argument) error and the big FAIL again if tried to wipe.
I am running out of ideas. I will try to get in touch with Huawei later to see if I can get a bootloader unlock code for this phone since I cannot get the Product ID with the *#*#whatever, of course because is bricked.
Does anyone have anything that I might be missing here?
Should I tried with a 4.2.2 stock update.app instead of this 4.4.2?
Thank you so much for your time.
Hope to hear back from anybody.
UPDATE:
============================================================================
(#4)
I tried to extract and flash the boot, recovery, efi, system, cust, userdata, cache images from the 4.4.2 UPDATE.APP with the latest HuaweiUpdateExtractor_0.9.9.3 I found here. I used the fastboot flash for that (I had to unlock the bootloader again with the UUUUUUU command).
It took all of them with OKAY messages, excepted for the system one which prompted.
Code:
target reported max download size of 838860800 bytes
Invalid sparse file format at header magi
And when rebooting, it came back to the boot loop in the ASCEND logo, and when VOL+ VOL- same thing, back to stock recovery with mount /cache error and the BIG FAIL message when trying to wipe.
I am not sure if the thing that I keep getting the bootloader back to locked status everytime and reboot the phone is a bad sign.
Still no progress... will continue tomorrow.
Try wiping all infastboot and then reflashing clean. Files to make the prio list are boot.img recovery.img and cust.img Dont reboot untill you reflashed the files or you will get to a hard brick. So make a wipe and right after that flash. No reboots inbetween.
Sent from my SM-G850F
Hi help,
I did something wrong with firmware flash.
So phone is bricked.
I followed on XDA the OP3 Unbrick forum, now my phone can turn on.
but I have an older bootloader. Also I het failed, when I press recovery, I can also only connect with fastboot and not ADB.
Help.
HELP ME
YourTheBest said:
HELP ME
Click to expand...
Click to collapse
flash this TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21835&task=get
First go into fastboot then flash by typing fastboot flash recovery <name of the twrp you downloaded above><a
You can now flash latest OOS from TWRP
strumaticjoker2 said:
flash this TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21835&task=get
First go into fastboot then flash by typing fastboot flash recovery <name of the twrp you downloaded above><a
You can now flash latest OOS from TWRP
Click to expand...
Click to collapse
I did that, thanks.
Doesn't work. I can do fastboot boot twrp.img
but when I install OOS or other ROM i get this error: ERROR 7 *unknow command and
failed to mount /cache (invalid argument)
failed to mount /system (invalid argument)
[email protected]#$%^&*()_
I get stupid error: when phones start/reboot.
md5 checkum failed
boot failed
recovery failed
My whole #!#$$#@ life failed.
Had the same few nights ago. Check the forum for the unbrick guide - method 2.
orlexx said:
Had the same few nights ago. Check the forum for the unbrick guide - method 2.
Click to expand...
Click to collapse
Then I lost al my WhatsApp messages... Right?
I can see the data files.
I still have issues!
Help
I'm having issues flashing a custom rom to my 7T (1903). Tried flashing with TWRP, couldn't mount my storage to flash the files, tried fastboot instead and I keep getting errors: FAILED (remote: Partition not found), so I tried re-installing a stock fastboot firmware and the MSM Tool, but I still get partition errors. Any help would be greatly appreciated.