- Forum
- More Android Goodness
- The Archives
- Android Central Archives
- Samsung
- Verizon Droid Charge
- Droid Charge Rooting, ROMs, and Hacks
e:can't mount /cache/recovery/command
-
The problem was that my phone wouldn't work with the SD card in. As soon as I popped it out it the phone worked flawlessly.12-09-2011 08:17 AMLike 0 - Did a little more research, and the concensus seems to be the phone is pretty much bricked. I did manage to odin it back to stock ee4, and it just boot loops the eyeball. Tried everything out there last night. I am heading to Verizon in 5 minutes to see if they are fooled enough to give me a new one.
It was so weird because everything was running fine yesterday, then my battery drained and phone shut off. I went back to put it on charger. I plugged it in and tried to turn it back on and it just stuck on the Samsung screen.12-09-2011 10:27 AMLike 0 - Did a little more research, and the concensus seems to be the phone is pretty much bricked. I did manage to odin it back to stock ee4, and it just boot loops the eyeball. Tried everything out there last night. I am heading to Verizon in 5 minutes to see if they are fooled enough to give me a new one.
It was so weird because everything was running fine yesterday, then my battery drained and phone shut off. I went back to put it on charger. I plugged it in and tried to turn it back on and it just stuck on the Samsung screen.12-09-2011 11:15 AMLike 0 -
Yeah, believe me I tried everything. I tried the Samsung PST. I tried ODINing every build from ed1 to ee4 to cwm and flashing gummy charged 2.0. Nothing worked. They are shipping me a new phone that should be here Monday, and I am back to my enV Touch for the time being. Guess I learned my lesson when it comes to rooting. Looks like stock GB for me from now on.12-09-2011 12:35 PMLike 0 - Did a little more research, and the concensus seems to be the phone is pretty much bricked. I did manage to odin it back to stock ee4, and it just boot loops the eyeball. Tried everything out there last night. I am heading to Verizon in 5 minutes to see if they are fooled enough to give me a new one.
It was so weird because everything was running fine yesterday, then my battery drained and phone shut off. I went back to put it on charger. I plugged it in and tried to turn it back on and it just stuck on the Samsung screen.01-05-2012 03:55 PMLike 0 - reading threw your problem , im new/ish at this and my samsung droid charge has the same problem to a T . i noticed the above post had a link to download a fix for the problem but it was for the nexus s . this may be a noob question but would that download be compatible with the charge as well or would it be specifically for the nexus s ? if not compatible would there be one having the same fix download for the charge ??04-12-2012 06:49 AMLike 0
- that msg above does seem to be outta place, but my droid charge thinks its a Galaxy S11.. so who knows..but there is a fix for the prob.. but since you've cleard up things and have a new one coming theres not much to be said.. enjoy..
PS> dont let the brick thingy worry u so much.. most of the time the brick can be undone as long as you can get to the down load on the phone and connect to odin.. once there ev things a wizz04-16-2012 11:40 PMLike 0 - I got the same message 'can't mount /cache/recovery/command'
Just restoring the ClockworkMod apparently fixed the boot system on the phone:
How to flash ClockworkMod Recovery for the Galaxy S Plus I9001
It seems ClockworkMod corrupts itself...04-19-2013 07:21 AMLike 0
- Forum
- More Android Goodness
- The Archives
- Android Central Archives
- Samsung
- Verizon Droid Charge
- Droid Charge Rooting, ROMs, and Hacks
e:can't mount /cache/recovery/command
« [How-to] Root Droid Charge**5/19/11**[Windows & Mac] Now with GingerSnap!
|
SIM Card is not supported »
LINK TO POST COPIED TO CLIPBOARD