Ok i seen this error couple times when i doa wipe/data factory reset, i always forget to post the error so im do my best to remember the error and maybe some one can help me what it means
if i remember correctly the error says
wipe ext error extfsf_4 /dev/block/system/mmcblk2p1
like i said im unsure what the error really put out i was goin off memory, so that could be wrong, just wondering had an error similar to that
Try This Method???
Sounds like your sdcard.. Backup your stuff, format your sdcard, and try again..
if this helped.. slap my thanks button please
Related
How can i fix this??
Can you only access recovery mode (power+home) and stock SPL (power+camera)..? I have the same issue.. Are you stuck trying to boot on the G1 Tmobile screen? You could try wiping in recovery (alt+w). That empties the cache... or you could try reformatting your memory card.. WARNING: Wiping will erase all data and settings.. so back up if you can. Hope this helps.
I have hard spl , but i wanted to go into reovery and see if there was the alt b for nandroid backup because i wanted to start looking into to doing that next and when i boot into reovery mode i see that error up top, everything is working perfectly i just dont want to have a problem when i get up the courage to move my apps to sd , i stay away from fastboot. I only use fastboot to downgrade back to rc29 because thats the .nbh that is on my sd card i think
You should take advantage of the search forum tab because it can work wonders when it comes to these types of issues because your not alone.. But I believe that in recovery it always says "E: cant run /cache/recovery/command" ... you shouldnt have to worry about it, unless ur paranoid. But search that command in the search forum tab and youll probably find an answer.
Fixed i somehow had put an old recovery.img on my sd card , i flashed the jesusfreke1.43 recovery.img and all is well... does everybody have a black script run for a minute before the JF recovery pops up?? If so ..Im all set thanks
you're one to talk, you have a thread about a "bricked" phone when we have several threads devoted to people asking for help when they can't boot
Hello,
I have a htc desire s (s-on, 2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04 installed).
When I start the phone with fastboot enabled, the widgets occasionally close and load again.
So everything start normal, but sometimes the widgets close in less than a second after startup and load again.
This only happens since 2.10.401.8 is installed.
I think that it's htc sense that crashes, but I'm not certain.
Already tried a factory reset, but same result.
Does Anyone have an idea what wrong and/or a solution?
After further testing I guess fast boot isn't working correctly anymore even after factory reset.
Is this a hardware problem or is there a way to test if it is a hardware problem?
Now it start to take a lot of time to startup and shutdown.
I also can't get in recovery: "E:Can't mount /cache/recovery/command"
From what I've seen on here, this sounds like what used to be called "the dreaded eMCC chip" problem, but is actually the "cache" partition being corrupted.
From what I've read, you may just about get away with it. Have a look at the following threads;-
http://forum.xda-developers.com/showthread.php?t=1177299
http://forum.xda-developers.com/showthread.php?t=1314629
Thanks, I feared that it was the emmc problem.
I have never pulled out the battery.
I will look into the threads, but I don't know if there is much I can do being s-on.
Update:
I had to send the device to HTC and they replaced the mainboard.
Everything is working good again.
Hi.
Once I tried to install RUU on S-offed rooted phone. Instalation stopped and didn't continue. I had the same problem with partitions
I also can't get in recovery: "E:Can't mount /cache/recovery/command"
Click to expand...
Click to collapse
What helped is to format cache partition in recovery. After that I could bring back my previous rom. In the end I didn't try to install RUU anymore.
I hope it will help.
---
Sorry, I didn't see your last post
So, as the topic states, I'm having major problems as of late.
Nexus S, GT-I9020A
ROM: CM9
Over the past few months, my phones been acting up. My phone when rebooted stalls at the Google Lock Screen. I am unable to mount the E drive in CWM as well,
Going into CWM,
1) wipe data/factory reset gives me problems, results below
--Wiping Data...
Formatting /data...
E: Format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/userdata
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete
2) wipe cache partition
--Wiping cache...
Formatting /cache...
Cache wipe complete.
3) Mounts and Storage
Error mounting /sdcard!
Error mounting /system!
Error mounting /data!
format /sdcard ...
Error mounting /sdcard!
Skipping format...
Done
4) Apply update from .zip file on SD card
E: can't mount /sdcard/
.... That's about all the options that I would go through to fix a rom. I don't know what else to do, last time this happened the E drive magically mounted and I was able to turn my phone back on, this time I've not been so lucky.
Reading around, I haven't been able to get any information on where to go next, most topics seem to be successful with the things I've done. I'm afraid that the phone is bricked, is there anything else I could try before I throw in the towel?
What version of CWM recovery are you using?
polobunny said:
What version of CWM recovery are you using?
Click to expand...
Click to collapse
I knew I forgot something,
v5.0.2.0
Bump to the top,
Is there any insight on the way forward? I've heard of Odin as something that may help, but from what I've read, Odin is only Samsung, Fastboot for Google.
No one has been able to help me, or anyone else with this issue, although it seems rather common in the past 6 months. I have read dozens of threads with this problem, they are all mostly ignored, little replied to, and never solved.
CWM Touch is what is did it to your phone. I would suggest switching to another recovery at least, and try installing a new ROM that way if you already have one on your phone. If you have nothing on the memory already, good luck getting something on it, you're probably going to have to send it in.
In my experience, nothing will work to write to your MS once it is corrupted. I have tried the Toolkit, ADB, ODIN, and Fastboot. All of it worked correctly until it got to the MS portion of my memory, then it would error out and complete, with no change. I have put well over 100 hours of reading and effort into it. Went from knowing NOTHING about this except how to flash a ROM, to knowing all of the fastboot commands by heart... Still no luck.
Aggravating, I know. But that's the way the cookie crumbles sometimes. :crying:
DizturbedOne said:
No one has been able to help me, or anyone else with this issue, although it seems rather common in the past 6 months. I have read dozens of threads with this problem, they are all mostly ignored, little replied to, and never solved.
CWM Touch is what is did it to your phone. I would suggest switching to another recovery at least, and try installing a new ROM that way if you already have one on your phone. If you have nothing on the memory already, good luck getting something on it, you're probably going to have to send it in.
In my experience, nothing will work to write to your MS once it is corrupted. I have tried the Toolkit, ADB, ODIN, and Fastboot. All of it worked correctly until it got to the MS portion of my memory, then it would error out and complete, with no change. I have put well over 100 hours of reading and effort into it. Went from knowing NOTHING about this except how to flash a ROM, to knowing all of the fastboot commands by heart... Still no luck.
Aggravating, I know. But that's the way the cookie crumbles sometimes. :crying:
Click to expand...
Click to collapse
Ah, seemingly so eh? The phone is probably not even worth sending it in as it would probably cost just as much to buy a new one.
I don't have CWM Touch (assuming that's CWM with touch function), just CWM that requires the vol rockers. It's an old version.
Hmm, it's been a while, but how would I be able to change the recovery if I can't access the E drive? I presume ADB? Then hope it works?
Anyways, thanks for your help, it's been quite frustrating seeing nothing turn up.
Another bump in hopes anyone with a fix reads this.
"UID's on the system are inconsistent. you need to wipe your data partition or your device will be unstable" there's a button that says "I'm feeling Lucky"
Any one can tell me how to solve this phorblem try many time flash to stock and fix permission via TWRP.. problem still here.. ANy idea??:crying::crying:
lhk92218 said:
"UID's on the system are inconsistent. you need to wipe your data partition or your device will be unstable" there's a button that says "I'm feeling Lucky"
Any one can tell me how to solve this phorblem try many time flash to stock and fix permission via TWRP.. problem still here.. ANy idea??:crying::crying:
Click to expand...
Click to collapse
now... some of button cant use. look like the virtual home button. no response after press.
Please help!!!!! who can help me???
The only solution is to wipe the device.
Never use "Fix permissions" Its pointless and causes more problems than it's worth
So recently my old phone died and i just bought this one, maybe i can take it to warranty but im not sure because i did root it and tried to changw the Rom.
So, I tried to changw the rom but I didnt realise that wiping /system would delete the Rom file too bc i didnt have an external sd, so my phone is stuck in TWRP. My computer is slow and adb doesnt seems to work, whenever i tried to sideload a Rom my pc would freeze and adb would stop with no explanation other than "adb Failed"
I got an external sd, upooad the stock and miui roms and tried to install em both (separately) but none seemed to work, my phone boots and i get the "Encryption Unsuccessful" message, but whenever I try to do a factory reset i cant wipe "data".
I already tried to partition data to the external sd but it doesnt works either...
Is there any other way I can fix this? Ive been trying for days, digging up every forum, but I cant find a solution.
I really need to make it work, im quite desperate at this point.
Thanks in advance, and sorry for my weak english skills haha
JoeBrand said:
So recently my old phone died and i just bought this one, maybe i can take it to warranty but im not sure because i did root it and tried to changw the Rom.
So, I tried to changw the rom but I didnt realise that wiping /system would delete the Rom file too bc i didnt have an external sd, so my phone is stuck in TWRP. My computer is slow and adb doesnt seems to work, whenever i tried to sideload a Rom my pc would freeze and adb would stop with no explanation other than "adb Failed"
I got an external sd, upooad the stock and miui roms and tried to install em both (separately) but none seemed to work, my phone boots and i get the "Encryption Unsuccessful" message, but whenever I try to do a factory reset i cant wipe "data".
I already tried to partition data to the external sd but it doesnt works either...
Is there any other way I can fix this? Ive been trying for days, digging up every forum, but I cant find a solution.
I really need to make it work, im quite desperate at this point.
Thanks in advance, and sorry for my weak english skills haha
Click to expand...
Click to collapse
Greetings and welcome to assist. Is your bootloader locked ? that may be the problem. I did find this thread that has a twrp flashable stock rom if that helps to recover the device
http://forum.xda-developers.com/showpost.php?p=67461583&postcount=3
Good Luck
Sawdoctor