Hello,
So 2 days ago I received the OTA update for 6.0. Yesterday when my battery was low the device turned off unexpectedly. When I finally had a chance to plug it in the phone went into a BOOT LOOP. I left it over night hoping with the additional charge it would stop but no luck.
After not being able to get into recovery mode because of continued resetting. I looked up several videos and posts from Nexus users with the same issue. I found the solution to be tapping the power button repeatedly till device is fixed. It sounded absurd but it worked and the phone stopped resetting and started to charge as normal. I let the phone charge for about an hour and then proceeded to turn it on.
At that point it was then stuck at the Google logo. So after about 15 minutes of waiting I decided to do a hard reset. When doing so I an encountered an error which I am unfamiliar with. I have a picture of what it tell me but can't seem post it on the forum.
IT SAYS:
Supported API: 3
E: failed to mount/cache (Invalid Argument)
--Wiping Data...
Formatting Data...
E: failed to mount /cache (invalid argument)
Formatting /cache...
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
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_install
E: Can't open/cache/recovery/last_install
Data wipe complete.
E: failed to mount /cache (invalid argument)
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_install
E: Can't open/cache/recovery/last_install
E: failed to mount /cache (invalid argument)
After it did the wipe it got stuck at the new splash screen:
At this point I'm not sure what to do from here or where to begin to fix this problem.
djillusion954 said:
Hello,
So 2 days ago I received the OTA update for 6.0. Yesterday when my battery was low the device turned off unexpectedly. When I finally had a chance to plug it in the phone went into a BOOT LOOP. I left it over night hoping with the additional charge it would stop but no luck.
After not being able to get into recovery mode because of continued resetting. I looked up several videos and posts from Nexus users with the same issue. I found the solution to be tapping the power button repeatedly till device is fixed. It sounded absurd but it worked and the phone stopped resetting and started to charge as normal. I let the phone charge for about an hour and then proceeded to turn it on.
At that point it was then stuck at the Google logo. So after about 15 minutes of waiting I decided to do a hard reset. When doing so I an encountered an error which I am unfamiliar with. I have a picture of what it tell me but can't seem post it on the forum.
IT SAYS:
Supported API: 3
E: failed to mount/cache (Invalid Argument)
--Wiping Data...
Formatting Data...
E: failed to mount /cache (invalid argument)
Formatting /cache...
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
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_install
E: Can't open/cache/recovery/last_install
Data wipe complete.
E: failed to mount /cache (invalid argument)
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_install
E: Can't open/cache/recovery/last_install
E: failed to mount /cache (invalid argument)
After it did the wipe it got stuck at the new splash screen:
At this point I'm not sure what to do from here or where to begin to fix this problem.
Click to expand...
Click to collapse
This is why people should NOT, EVER let their devices batteries run low on juice.
Charge up your device with an AC charger, forget USB, and leave it for a few hours. then boot to bootloader and flash MRA56K factory image.
beekay201 said:
This is why people should NOT, EVER let their devices batteries run low on juice.
Charge up your device with an AC charger, forget USB, and leave it for a few hours. then boot to bootloader and flash MRA56K factory image.
Click to expand...
Click to collapse
MRA56K factory image???????????? what is that and where can I find it???
Maybe the op meant to say mra58k?
Hey. So, same problem here (same errors), but a faulty power button caused the reboot in the middle of the update.
Replaced the power button but now can't flash anything since my USB debugging was off (unrooted- from day one just auto-updated).
Can I do something or I'm screwed? we don't have here google services and I bought the device from US (google store website).
Related
My Samsung Galaxy S Relay 4G took a dump tonight. It crashed and rebooted [normal shut off to black screen and turn back on kinda crash]. Not totally unheard of, it's electronic so things happen. Anyway, I sit there holding it while watching tv waiting for it to come back on and it doesn't! It sits at the screen that says "Samsung GALAXY S RELAY 4G exclusively from T-Mobile". I work with computers everyday so I know this a bad sign. I try a full power cycle by removing the battery and that didn't help. I tried just letting it do it's thing while I ate dinner and that didn't help. So I start Googling and just about the only stuff I can find is how to root the phone. I find things about booting to Safe Mode [didn't work, same result], things about rooting [hangs up at the Downloading... screen] and things about factory reset [not my 1st choice but it's already broke]. So I try to boot into the restore mode and it says:
failed to mount /system (invalid argument)
So I'm kinda lost. Basically the phone won't boot up, it won't boot safe mode and I can't get it to boot to recovery. Any help from the wise android community?
This is an official...not a rooted one.
Either emmc is borked or you have a bad battery....Samsung put this special battery feature in them that when the battery goes bad it acts like a brick...I had this happen once and with me battery it booted right back up....also have you tried Odin back to stock yet?
I just tried swapping to a known good battery [GF has the same phone] and that didn't fix it. I tried the Odin reset and that's how I saw the failed to mount /system error
Full error when loading Odin with Vol Up, Home and Power:
E:failed to mount /system (invalid argument)
Can't mount '/system' (invalid argument)
E:failed to mount /efs (invalid argument)
E:failed to mount /system (invalid argument)
# Manual Mode #
--Applying Multi-CSC...
E:failed to mount /system (invalid argument)
Can't mount '/system' (invalid argument)
invader138 said:
Full error when loading Odin with Vol Up, Home and Power:
E:failed to mount /system (invalid argument)
Can't mount '/system' (invalid argument)
E:failed to mount /efs (invalid argument)
E:failed to mount /system (invalid argument)
# Manual Mode #
--Applying Multi-CSC...
E:failed to mount /system (invalid argument)
Can't mount '/system' (invalid argument)
Click to expand...
Click to collapse
I fixed it by reflashing to the latest stock ROM with Samsung Kies. I had everything backed up so it was an easy restore of apps after the flash. I hope this helps someone in the future.
noob here. long time reader, first time poster. first off, you have a fantastic site that has educated me immensely, and allowed me to properly root many devices.
now onto my problem. i have a galaxy s4 4.4.4 i337 (NOT rooted at the time) that unfortunately went belly up the other day with the seemingly typical message of "...data corrupted....perform factory reset...". after a number of restart attempts, including pulling the battery, i decided to check out the recovery mode. it had an image of a passed out android with a statement No command right below it. before undertaking the reset, i chose the reboot system now from the menu on the upper left which resulted in No command changing to Error! while the following entries appeared (exactly as shown, including the repeat statements) at the bottom in red:
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount /data (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_kernel_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_last_kernel_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/emmc_checksum_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
i could not find any suggestion other than to reset, so i went ahead with it. everything seemed to be fine afterwards and i was event able to root it. at some point, however, i decided to revisit the system recovery screen, only to be greeted by the passed out android image with No command below it! whatta?! when i selected reboot system now menu, No command once again changed to Error!, but nothing appeared at the bottom this time around, and the phone booted up without a problem. i reset the phone one more time, but it still continues to exhibit the same exact behavior as i have described. the phone itself seems to be functioning properly, yet i cannot let go of the fact that something is still not kosher under the hood, especially since it died on me so suddenly. please help! thank you.
Mr Bottomtooth said:
noob here. long time reader, first time poster. first off, you have a fantastic site that has educated me immensely, and allowed me to properly root many devices.
now onto my problem. i have a galaxy s4 4.4.4 i337 (NOT rooted at the time) that unfortunately went belly up the other day with the seemingly typical message of "...data corrupted....perform factory reset...". after a number of restart attempts, including pulling the battery, i decided to check out the recovery mode. it had an image of a passed out android with a statement No command right below it. before undertaking the reset, i chose the reboot system now from the menu on the upper left which resulted in No command changing to Error! while the following entries appeared (exactly as shown, including the repeat statements) at the bottom in red:
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount /data (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_kernel_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_last_kernel_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/emmc_checksum_log.txt (Invalid argument)
E:failed to mount /data (Invalid argument)
i could not find any suggestion other than to reset, so i went ahead with it. everything seemed to be fine afterwards and i was event able to root it. at some point, however, i decided to revisit the system recovery screen, only to be greeted by the passed out android image with No command below it! whatta?! when i selected reboot system now menu, No command once again changed to Error!, but nothing appeared at the bottom this time around, and the phone booted up without a problem. i reset the phone one more time, but it still continues to exhibit the same exact behavior as i have described. the phone itself seems to be functioning properly, yet i cannot let go of the fact that something is still not kosher under the hood, especially since it died on me so suddenly. please help! thank you.
Click to expand...
Click to collapse
bump
So...I'm a little bit of a newbie when it comes to fixing technology, so I hope to be as clear as possible. All of a sudden my Samsung Galaxy s4 died few hours ago. It would just boot and get stuck at the "Samsung Galaxy s4 GT-I9505" screen (If I plug it to charge it remains stuck at the screen where the battery is grey and it has a white circle in it). Before that it normally booted up for like 20-30 seconds. Then it rebooted that way. Now, I can get to recovery mode, and what I get is the following text when entering:
E:failed to mount /efs (invalid argument)
E:failed to mount /system (invalid argument)
# MANUAL MODE #
--Appling Multi-CSC
E:failed to mount /system (invalid argument)
can't mount '/system' (invalid argument)
E:failed to mount /cache (invalid argument)
can't mount '/cache' (invalid argument)
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_recovery
E:failed to mount /data (invalid argument)
E:can't mount /data/log/recovery_log.txt
E:failed to mount /system (invalid argument)
E:failed to mount /cache (invalid argument)
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)
I didn't perform any root or flashing since I barely know what they are, I tried an emergency recovery and initialization with Kies by booting the phone into download mode but it says that my phone doesn't support it, which is weird. How big of a problem is this? I brought the phone to a local technician which said I should contact Samsung assistance because "the internal memory is gone" (as for damaged, I assume) but I don't think it can be right since again, I booted it up in the morning and for 30 seconds it was perfectly fine, I am thinking more of a corruption, somehow, of the files. Is there any way I can get out of this state? Can I recover any data from it? I underestimated the situation and I've never done a backup of the phone sadly... If it can help, when this happened I was on firmware 4.4.2. Thanks in advantage for any reply.
dariomrk said:
Do you have your warranty? I suppose that the hardware is damaged. In that case you will probably need a motherboard replacement.
Click to expand...
Click to collapse
Phone was bought in November 2013 so I suppose it's not eligible for warranty replacement
CrashRatchet008 said:
So...I'm a little bit of a newbie when it comes to fixing technology, so I hope to be as clear as possible. All of a sudden my Samsung Galaxy s4 died few hours ago. It would just boot and get stuck at the "Samsung Galaxy s4 GT-I9505" screen (If I plug it to charge it remains stuck at the screen where the battery is grey and it has a white circle in it). Before that it normally booted up for like 20-30 seconds. Then it rebooted that way. Now, I can get to recovery mode, and what I get is the following text when entering:
E:failed to mount /efs (invalid argument)
E:failed to mount /system (invalid argument)
# MANUAL MODE #
--Appling Multi-CSC
E:failed to mount /system (invalid argument)
can't mount '/system' (invalid argument)
E:failed to mount /cache (invalid argument)
can't mount '/cache' (invalid argument)
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/last_recovery
E:failed to mount /data (invalid argument)
E:can't mount /data/log/recovery_log.txt
E:failed to mount /system (invalid argument)
E:failed to mount /cache (invalid argument)
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)
I didn't perform any root or flashing since I barely know what they are, I tried an emergency recovery and initialization with Kies by booting the phone into download mode but it says that my phone doesn't support it, which is weird. How big of a problem is this? I brought the phone to a local technician which said I should contact Samsung assistance because "the internal memory is gone" (as for damaged, I assume) but I don't think it can be right since again, I booted it up in the morning and for 30 seconds it was perfectly fine, I am thinking more of a corruption, somehow, of the files. Is there any way I can get out of this state? Can I recover any data from it? I underestimated the situation and I've never done a backup of the phone sadly... If it can help, when this happened I was on firmware 4.4.2. Thanks in advantage for any reply.
Click to expand...
Click to collapse
Greetings and welcome to assist. It sounds like your partition table is corrupt, can you get into download mode ? If you can try kies/smartswitch emergency firmware recovery
Good Luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. It sounds like your partition table is corrupt, can you get into download mode ? If you can try kies/smartswitch emergency firmware recovery
Good Luck
Sawdoctor
Click to expand...
Click to collapse
As I mentioned in the OP, I already tried the emergency firmware recovery, but both Kies, Kies 3 and SmartSwitch claim that the phone is not eligible for the emergency recovery. Of course, I tried performing these operations by entering in download mode and then connecting the phone to the pc to perform the operation but no luck so far. Other options? Do I need to flash a new firmware?
CrashRatchet008 said:
As I mentioned in the OP, I already tried the emergency firmware recovery, but both Kies, Kies 3 and SmartSwitch claim that the phone is not eligible for the emergency recovery. Of course, I tried performing these operations by entering in download mode and then connecting the phone to the pc to perform the operation but no luck so far. Other options? Do I need to flash a new firmware?
Click to expand...
Click to collapse
Try this thread, if the firmware doesn't work you could try mskips toolkit, that has an emergency firmware recovery. As a last resort you could flash a pitfile
https://forum.xda-developers.com/showthread.php?t=2751515
Good luck
Sawdoctor
Hello people!
So, i will tell all the story, i tried to flash a ROM in my Xperia Z3 (D6643), following this tutorial, the TWRP worked fine, even after installation the message was "Installation successful" then i rebooted. But nothing, just nothing, even TWRP :crying:
He vibrates when i tri to power on in any boot method, i can also connect in PC in fastboot mode.
I had rooted and unlocked bootloader, any solutions?
Edit: I flashed TWRP again and now i can enter in recovery mode, then i tried factory reset, theres the log:
Could not mount /data and unable to find cryptofolder
Failed to mount /data (invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount /cache (invalid argument)
Failed to mount /data (invalid argument)
...done
Unable to mount storage
Failed to mount /data (invalid argument)
Failed to mount /cache (invalid argument)
Full SELinux support is present.
Failed to mount /cache (invalid argument)
Failed to mount /cache (invalid argument)
Failed to mount /data/media/TWRP/.twrps
Failed to mount /data (invalid argument)
MTP Enabled
Failed to mount /data (invalid argument)
Formating Cache using make_ext4fs...
Failed to mount /data (invalid argument)
Updating partition details...
Failed to mount /data (invalid argument)
...done
Unable to mout storage
Edit: I noticied the internal storage is listed with 0MB. Please help...
Edit: Ok i got it, i will let the solution if someone is having the same issue
CM 14.1 dont work on Xperia Z3 D6643, that was the problem, the solution was find a compatible ROM. In this case i used this one.
Pretty simple
I'm new to the site, hopefully this is in the right area. I've searched and spent hours trying to figure this out. Can anyone tell me why this ZTE K85 that I was given is looping a screen? I've tried everything I can think of to get access to it through my pc but I can't get into it.
The screen that keeps looping says
E: Failed to mount \cache (Invalid argument)
E: failed to mount \cache
E: failed to set up expected mounts for install; aborting
E: Failed to mount \cache (Invalid argument)
Installation aborted.
The update failed, the phone will restart in 5 seconds...