Left my phone to charge over night and woke it up finding it turned off. (You can imagine the shock!!)
I turned it on back and it has been stuck on the boot screen with the flying dots since then. (Annoyed!!)
When I go into recovery mode and try deleting cache or wipe data I get a lot of error messages saying can't mount cache/recovery/log
Can't unlock boatloader to flash stock. It keeps relocking upon each restart.
Each time I wipe I get these error messages.
Wiping data...
Formatting/data...
- hide quoted text -
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
Data wipe complete
- hide quoted text -
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)
Can someone please help me. I am really frustrated. Please don't tell me it's a hardware problem....
Um this sounds like a hardware problem. Sorry
Sent from my Nexus 5 using Tapatalk
Your NAND is fried. Definitely a hardware issue. RMA in you only option.
theesotericone said:
Your NAND is fried. Definitely a hardware issue. RMA in you only option.
Click to expand...
Click to collapse
I feel like crying right now. My phone does not have any warranty.
I've been compiling NAND failures for the last few months - am I right to assume your phone was 100 % stock?
So far, my WAG is related to the ftrim. We do know they've improved the way it works in the last couple of updates - and made it more aggressive as well.
That does track well with the emmc casualties I'm seeing. But it could be a red herring as well - wear and NAND quality being the most obvious factors.
I wonder, how many of the failures occurred after a night-long charging ( which triggers ftrim) ?
Sent from my Nexus 5 using XDA Free mobile app
Niflheimer said:
I've been compiling NAND failures for the last few months - am I right to assume your phone was 100 % stock?
So far, my WAG is related to the ftrim. We do know they've improved the way it works in the last couple of updates - and made it more aggressive as well.
That does track well with the emmc casualties I'm seeing. But it could be a red herring as well - wear and NAND quality being the most obvious factors.
I wonder, how many of the failures occurred after a night-long charging ( which triggers ftrim) ?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes 100% stock and unrooted.
I don't know. I woke up and found it turned off. Then I got a bunch of error messages when I tried wiping cache and data.
Is it by some chance possible to save my phone??? I really need to know. I've been up searching the web. I realize I'm not alone now.
Phone_evolution said:
Is it by some chance possible to save my phone???
Click to expand...
Click to collapse
No. The memory is bad. Sorry man those are the facts.
By normal means? A straight and categoric no. In theory we could try reformat it externally, maybe even read it but... It's not gonna happen - at least not affordable.
Buying the emmc chip and replacing it is doable - but again probably not affordable if u don't already have the tools.
Sent from my Nexus 5 using XDA Free mobile app
Niflheimer said:
By normal means? A straight and categoric no. In theory we could try reformat it externally, maybe even read it but... It's not gonna happen - at least not affordable.
Buying the emmc chip and replacing it is doable - but again probably not affordable if u don't already have the tools.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In a recovery there is an option which is apply update from ADB. Neither that can help me???
Instead of buying parts to fix the device, you should look into getting a new replacement
Related
I have some weird stuff going on and I was wondering if maybe someone could tell me what it means. My phone is running fine, in fact better than ever. But when I reboot into recovery mode, and before I apply update.zip and I am in stock recovery (blue), I get the follow message below all of the recovery options (error message is in red):
E: Can't mount /dev/block/st111
(Invalid Argument)
E Can't mount /dev/block/mmcblk0p1
(Invalid Argument)
# MANUAL MODE #
E: Can't mount /dev/block/st111
(Invalid Argument)
E: Can't mount /dev/block/st111
(Invalid Argument)
Then, when I do a backup through CWM, everything goes through fine and then I get this message:
Back complete!
E: Can't open /cache/recovery/log
E: Can't open CACHE:recovery/log
When I go into CWM recovery, I do see a backup labeled with the correct date and everything, so I guess it is backing up correctly? Not quite sure what to make of it.
Ignore it.
Sent from my SCH-I500 using XDA App
JayRHamlin said:
I have some weird stuff going on and I was wondering if maybe someone could tell me what it means. My phone is running fine, in fact better than ever. But when I reboot into recovery mode, and before I apply update.zip and I am in stock recovery (blue), I get the follow message below all of the recovery options (error message is in red):
E: Can't mount /dev/block/st111
(Invalid Argument)
E Can't mount /dev/block/mmcblk0p1
(Invalid Argument)
# MANUAL MODE #
E: Can't mount /dev/block/st111
(Invalid Argument)
E: Can't mount /dev/block/st111
(Invalid Argument)
Then, when I do a backup through CWM, everything goes through fine and then I get this message:
Back complete!
E: Can't open /cache/recovery/log
E: Can't open CACHE:recovery/log
When I go into CWM recovery, I do see a backup labeled with the correct date and everything, so I guess it is backing up correctly? Not quite sure what to make of it.
Click to expand...
Click to collapse
I've had this happen and it happens when you have lagfix enabled and try to revert/odin back to a stock kernel (non voodoo) you'll need to follow the manual disabling procedure (of lagfix) by injecting an empty file named "disable lagfix" into the clockwork folder on your SD card then reboot. After that you should be clear to do a clean flash to get everything working properly. If you tried restoring right now it would probably give you an MD5 mismatch, and trying to flash from recovery would probably give you dev/block errors and it would cancel installation until you get your file system back in order.
bdemartino said:
I've had this happen and it happens when you have lagfix enabled and try to revert/odin back to a stock kernel (non voodoo) you'll need to follow the manual disabling procedure (of lagfix) by injecting an empty file named "disable lagfix" into the clockwork folder on your SD card then reboot. After that you should be clear to do a clean flash to get everything working properly. If you tried restoring right now it would probably give you an MD5 mismatch, and trying to flash from recovery would probably give you dev/block errors and it would cancel installation until you get your file system back in order.
Click to expand...
Click to collapse
OK that makes sense. I was flashing all over the place trying to fix that radio issue. Although I liked Add's answer better. Much more convenient
Sent from my SCH-I500 using XDA App
JayRHamlin said:
OK that makes sense. I was flashing all over the place trying to fix that radio issue. Although I liked Add's answer better. Much more convenient
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Lol yea, I tried that too when I buggered mine up, but since I couldn't flash anything in recovery I decided to find out how to fix it
i tried rooting my phone on 2.3.5 then found out i needed 2.3.3 max to root, so i tried flashing 2.3.3 to my phone, something went wrong and now after several attepths at restoring it it just boot cycles. i can get into download mode no problem, but it doesnt matter what i flash it tells me it cant mount efs or dbdata. is there a way to fix this or do i need to send my phone off to get it repaired?
melli.
could reflashing the efs sort this? if so where can i download it? cause i can't find the efs.rfs anywhere...
error messages in android system recovery as follows:
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
E:check_selective_file:can't mount /efs
-- Copying media files...
E:failed to mount /efs (invalid argument)
E:failed to mount /dbdata (invalid argument)
E:copy_dbdata_media:Cant mount /dbdata
your storage not prepared yet, please use ui men
u for format and reboot actions.
Media files copy failed.
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /efs (invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
i have tried all the options in the recovery menu and none have helped...
melli.
ok i have now got my phone working again with a few hours tinkering thru heimdall. but now i have no imei number its just blank... any ideas? i have tried every rooting method ive managed to find on here so far none work so i can't edit the stuff in the efs partioion anyway. any other ideas???
melli.
well even despite the lack of replies suggesting how to fix this i have managed to fix it... got my phone working again it is stuck with the 004999010640000 imei but it works, so thanks for the help...
melli.
melliwuk said:
i tried rooting my phone on 2.3.5 then found out i needed 2.3.3 max to root, so i tried flashing 2.3.3 to my phone, something went wrong and now after several attepths at restoring it it just boot cycles. i can get into download mode no problem, but it doesnt matter what i flash it tells me it cant mount efs or dbdata. is there a way to fix this or do i need to send my phone off to get it repaired?
melli.
could reflashing the efs sort this? if so where can i download it? cause i can't find the efs.rfs anywhere...
error messages in android system recovery as follows:
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
E:check_selective_file:can't mount /efs
-- Copying media files...
E:failed to mount /efs (invalid argument)
E:failed to mount /dbdata (invalid argument)
E:copy_dbdata_media:Cant mount /dbdata
your storage not prepared yet, please use ui men
u for format and reboot actions.
Media files copy failed.
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /efs (invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
i have tried all the options in the recovery menu and none have helped...
melli.
ok i have now got my phone working again with a few hours tinkering thru heimdall. but now i have no imei number its just blank... any ideas? i have tried every rooting method ive managed to find on here so far none work so i can't edit the stuff in the efs partioion anyway. any other ideas???
melli.
well even despite the lack of replies suggesting how to fix this i have managed to fix it... got my phone working again it is stuck with the 004999010640000 imei but it works, so thanks for the help...
melli.
Click to expand...
Click to collapse
I have the same errors on my Infuse.
How did you fix???? I'm pulling my hair out.
i have the same problem on SGT
did you find a solution?
I have the same problem on Galaxy ace
I did finally get it sorted if i remember correctly i had to use heimdall to flash not odin i think odin was the problem. Sorry it took so long to answer guys but ive barely been on here since then, too much work! lol
Sent from my GT-I9000 using XDA
melliwuk said:
I did finally get it sorted if i remember correctly i had to use heimdall to flash not odin i think odin was the problem. Sorry it took so long to answer guys but ive barely been on here since then, too much work! lol
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
i have same problem any one have that solution?
the acutel problem
ALL SAMSUNG ANDROID PHONE WHO GIVE ERRORS LIKE THIS
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
E:check_selective_file:can't mount /efs
-- Copying media files...
E:failed to mount /efs (invalid argument)
E:failed to mount /dbdata (invalid argument)
E:copy_dbdata_media:Cant mount /dbdata
your storage not prepared yet, please use ui men
u for format and reboot actions.
Media files copy failed.
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /efs (invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
THATS MEAN THE BUILD IN MEMORY CHIP HAS BEEN PHYSICALY DAMGED ONLY REBALLING OR CHANGING THAT CHIP CAN ONLU SOLVE YOU PROBLEM THERE IS NOTHING U CAN SOLVE THIS BUY SOFTWARE ITS NOT A SOFTWARE PROBLEM..................
What planet are you living on mate??? Its nothing to do with a damaged memory chip. Its cause a flash failed and the boot loader is looking for a partition that doesn't exist cause its not all there.
If you must post please make sure you have a clue what you're posting...
Sent from my GT-I9000 using XDA
[email protected] said:
i have same problem any one have that solution?
Click to expand...
Click to collapse
First of all what is the error its giving when you boot? Once you post that I can hopefully help.
Sent from my GT-I9000 using XDA
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
Hello,
I had recently bought a Nexus 5 Model LG-D821 of 32gb storage.It was all ok but suddenly got switch off and reboot itself .Then I see welcome screen,select wifi,etc and finally it shows home screen.I got the pop up message notifying "camera has stopped" "gallery has stopped" etc.Then i checked into setting under storage there i see all mine data was erased.I had "32 Gb" of storage now i see total space of "128mb".There was only 5mb available storage.Further, there was unknown baseband version,unknow IMEI and unavailable Network.I take out the sim and inserted again but it doesnt worked.My Nexus 5 is unrooted,locked(bootloader version-HHZ11K) with a Build Number KTU84P currently running android 4.4.4 fully stock. Now I need help from you all expertise.How to fix this problem?Can it be fixed?Any help would be greatly appreciated.I dont know much about technicalities,provide me step by step guide to solve this issue.
:
thank you>>
Sounds like a bad emmc get a warranty replacement I see this a lot from the nexus 5
Yeah, you can try reflashing stock and what not.... But if you just bought it... I'd get it replaced instead.
spinninbsod said:
Sounds like a bad emmc get a warranty replacement I see this a lot from the nexus 5
Click to expand...
Click to collapse
hello,
thanks for the reply but i dont think there is a replacement warranty for this device.I bought from amazon japan there i see 30 days return policy.I dont know what to do..
KJ said:
Yeah, you can try reflashing stock and what not.... But if you just bought it... I'd get it replaced instead.
Click to expand...
Click to collapse
hello,
thank you for the reply.I tried to flash stock but this but unable to do that.It says like this in recovery
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)
Try mobile uncle tool
Sent from my GT-I8262 using XDA Free mobile app
pradip.108 said:
Try mobile uncle tool
Sent from my GT-I8262 using XDA Free mobile app
Click to expand...
Click to collapse
bad idea!!!!!
pradip.108 said:
Try mobile uncle tool
Sent from my GT-I8262 using XDA Free mobile app
Click to expand...
Click to collapse
Its meant for mtk devices nt qualcom
doctor_droid said:
Its meant for mtk devices nt qualcom
Click to expand...
Click to collapse
My friend got trolled by a kid that told him to use that tool for flashing custom recovery on his Xperia L, and he bricked his device
ZammyHedgeFox said:
My friend got trolled by a kid that told him to use that tool for flashing custom recovery on his Xperia L, and he bricked his device
Click to expand...
Click to collapse
Must have been a hardbrick lol
Friend od mine had the same issue. It is emmc failure. There is nothing you can do about it. Had to be send for replacement. In other words flash memory is dead.
yam.riddle said:
hello,
thank you for the reply.I tried to flash stock but this but unable to do that.It says like this in recovery
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)
Click to expand...
Click to collapse
Try flashing just the cache partition through fastboot.
Code:
fastboot erase cache
Code:
fastboot flash cache cache.img
varuntis1993 said:
Try flashing just the cache partition through fastboot.
Code:
fastboot erase cache
Code:
fastboot flash cache cache.img
Click to expand...
Click to collapse
i got this error:
Failed <remote:failed to erase partition>
yam.riddle said:
i got this error:
Failed <remote:failed to erase partition>
Click to expand...
Click to collapse
Try relocking your bootloader with fastboot oem lock, them reboot the bootloader. If it stays locked, then try LG Flashtool. If it reverts to being unlocked after the reboot then your eMMC is damaged and you'll have to RMA.
Well, my Nexus 5 had a similar problem, but mine was unable to mount /persist.
So all thanks to this, my Nexus 5 was saved. You might want to try this if that doesn't work.
Lethargy said:
Try relocking your bootloader with fastboot oem lock, them reboot the bootloader. If it stays locked, then try LG Flashtool. If it reverts to being unlocked after the reboot then your eMMC is damaged and you'll have to RMA.
Click to expand...
Click to collapse
hello,
It is by default locked.when i hit fastboot oem unlock,bootloader is unlocked but after reboot in bootloader it stays locked.Does LG Flashtool works in my case?
yam.riddle said:
hello,
It is by default locked.when i hit fastboot oem unlock,bootloader is unlocked but after reboot in bootloader it stays locked.Does LG Flashtool works in my case?
Click to expand...
Click to collapse
Probably not but you can try. Most likely you'll have to RMA.
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