Hi all,
First of all, my phone is completely vanilla, no rooting or modifications were done. Running 5.0
Here's my situation:
After fully charging the phone yesterday and sending some messages on whatsapp, I drove out to get food and while on the way there, the phone blacked out. At first, I was able to get to the colored dots loading screen but it would always get stuck there and shut off. Then I keep trying to restart it up and it got worse and worse, now I'm always stuck at the GOOGLE screen. I'm not sure if this is a boot loop issue as it just gets stuck at GOOGLE screen. I tried the recovery mode cache wipe and it gets stuck at the GOOGLE screen in the middle of the wipe, or blacks out.
So this morning, after fiddling around the power buttons some more, I am able to get the battery logo while charging, though it is weird that it shows 100% then completely drained the next minute or so. I try to load into the recovery mode again and this is what I see at the bottom
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/log
E: Can't open /cache/recovery/log
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)
Am I screwed? I'm not sure what to do at this point.
Today, I am stuck at the colored dots boot animation but after smacking the power button side a bit, I'm back to being stuck on the Google screen. What's worse the recovery mode can't be maintained on the screen as it blacks out after 5-10 seconds. What can I do at this point?
I was going to use WUGfresh to reflasth the ROM but I think this wipe all data on he phone? Is there anything I can do at this point to retrieve all my apps, photos and what not? Nothing is backed up.
Any tips or advice would be greatly appreciated.
Thanks
Related
Ok, so first of all, the current firmware on the phone keeps crashing every 5 seconds, and some recovery log process keeps forceclosing, so I NEED to get a new rom. This current one is not functional.
I finally downloaded a ROM, and put it on the root of my SD card.
Now, when I booted to CWM (holding vol up and vol down, and holding power), I get some errors.
It looks something like this:
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
Enter: POWER Key. Select : Vol UP/ Vol Down
reboot system now
reinstall packages
delete all user data
delete cache data
E:Can't mount /dev/block/stl11
(Invalid argument)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
-- Appling Multi-CSC...
Installing Multi-CSC
E:Can't mount /dev/block/stl11
(Invalid Argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/stl11
(Invalid Argument)
And so the CWM is messed up.
Now the menu looks something like this, (Totally different from what I've seen before)
Any idea how to get cwm functioning? By the way, I did not use ROM manager. Heard it messes stuff up.
Thanks.
Use the guide in the second link in my signature.
lumin30 said:
Use the guide in the second link in my signature.
Click to expand...
Click to collapse
Thank you sooooo much :laugh:
I finally fixed my phone!
Hi guys,
Had a thread open on modaco for this issue but had no joy. I'm having exactly the same issues as the thread starter in the link below, you guys have helped me before and wondered if you had any suggestions on a way forward?
http://www.modaco.com/topic/358071-phone-near-bricked-help-needed/
Basically I've had ics updated on the phone with the boot loader unlocked and of course the phone rooted. The update went through fine and I've been using the phone for a couple of days until it crashed and stuck on the splash screen since then it will only go into recovery mode with the following errors:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Have tried wiping cache, formatting cache and numerous other things as per the thread on modaco but no joy. I've literally had the phone a few days and think it's unlikely to be a hardware fault unless it's exactly the same as the OP had.
Willing to try anything!
Thanks
I have waked up and noticed that the phone is stuck on google logo, i tried to restore factory settings but that was not applicable
so i followed that post http://forum.xda-developers.com/showthread.php?t=2513701 to unlock the bootloader and install factory rom
after several tries my mobile phone can't start and when it starts the apps begin to crash one after the other, I noticed that the mobile recognize a memory of 250 MB (although I have a 32 GB storage) and I think thats the problem
Now I can open the recovery mode but the following errors appears:
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/log_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)
So I don't know what to do!!!!! please help
Unfortunately, it looks like the emmc has died. RMA it asap.
vin4yak said:
Unfortunately, it looks like the emmc has died. RMA it asap.
Click to expand...
Click to collapse
what is the emmc???
ahmedaziz555 said:
what is the emmc???
Click to expand...
Click to collapse
The internal flash memory module (32GB) of your phone.
Same thing happened to me. Was stuck in loading screen. Reset to factory settings. My apps would crash and I cant connect to my network. I also followed that same guide but it didn't help.
Yep, phone's internal storage is probably dead. RMA!
Just curious: for how much time did you use your phone before crashing? Was it completely stock?
Simonna said:
Just curious: for how much time did you use your phone before crashing? Was it completely stock?
Click to expand...
Click to collapse
Yes it was completely stock and i used the phone for 2 weeks
I was on Android 4.4.2, and was going to sideload the 4.4.3 update. I went into recovery, moved one step below the sideload update option, and landed on clear cache. My volume up button wouldn't take me back up to the ADB Sideload option, so I figured clearing the cache would bring me back up to the top. The phone was stuck on the "Wiping cache..." loading bar for 20 minutes until I finally force rebooted it. On completing the reboot, my phone wouldn't connect to the cell network, and all of my gapps crashed. I tried going back into recovery, and got errors saying;
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)
I really don't know how to go forward from here, so I'm hoping somebody can point me in the right direction. Thanks!
darthsentinel said:
I was on Android 4.4.2, and was going to sideload the 4.4.3 update. I went into recovery, moved one step below the sideload update option, and landed on clear cache. My volume up button wouldn't take me back up to the ADB Sideload option, so I figured clearing the cache would bring me back up to the top. The phone was stuck on the "Wiping cache..." loading bar for 20 minutes until I finally force rebooted it. On completing the reboot, my phone wouldn't connect to the cell network, and all of my gapps crashed. I tried going back into recovery, and got errors saying;
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)
I really don't know how to go forward from here, so I'm hoping somebody can point me in the right direction. Thanks!
Click to expand...
Click to collapse
If bootloader is unlocked, try flashing the cache file from the ktu84m package.
Aerowinder said:
If bootloader is unlocked, try flashing the cache file from the ktu84m package.
Click to expand...
Click to collapse
Sadly, the bootloader is locked.
This same thing happened to me the other day. I ended up having to reflash the factory image
Sent from my Nexus 5 using Tapatalk
the cache partition got messed up because you didn't let it finish the cache formatting process.
Head over to the stock recovery and keep formatting the cache partition few times.. If it gives the same error, erase it again!
I've faced similar errors and formatting cache a few times solved it!
- Sent from an IceCold Hammerhead!
Happen to me this morning as well. Just let be until completed. Should take approximately 10-15 minutes. Be patient. :victory:
Hi there,
I was given a Samsung Galaxy S4 mini GT-I9195 by friend. The phone unfrotunately does not boot anymore. Upon pressing the power button the phone vibrates and proceeds to the "Samsung Galaxy S4 mini GT-I9195" logo screen. The logo is displayed for a couple of seconds, before the screen turns black. In order to restart the phone you need to remove and reinsert the battery, because pressing the power button does not help.
The phone still runs the original software, as far as I know. So no custom rumos, unlocked bootloaders or the like.
Entering recovery mode I am presented ith the following error message:
E: failed to mount /efs (Invalid argument)
E: failed to mount /system (Invalid argument)
Selecting "wipe cache partition" produces the following error messsages:
E: failed to mount /cache
E: Can't mount / cache/recovery/log
E: Can't open / cache/recovery/log
Selecting "wipe data/ factory reset" produces these errors:
E: format_volume: make_extf4fs failed on /dev/block/platform/msms_sdcc.l/by-name/userdata
Is there any chance left for me to revive the device or do I have a Samsung made paperweight?
Thanks a bunch!
Ron