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.
Related
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
Hey guys,
I think my phone is partially bricked. I know that sounds weird, but here's the situation:
I was able to unlock my bootloader (faced multiple write errors using fastboot but it did unlock eventually), I can't reflash using Odin (it fails Error is "Complete Write Fail"), when I tried to format some partitions using clockwork I get:
E: format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
No linux newb here, so I'm guessing my internal partition is fubared..
Here's what's funny... I can flash a rom and boot into the rom usually on the first try. If I boot into the rom, it runs fine until I reboot the phone. Then it takes another *LITERALLY* 10 times of pulling the battery and rebooting the phone because the phone sticks at the Google boot logo. I can boot into recovery, fastboot, no problem.
As my phone sits right now: I can flash clockwork, bootloader unlocked. I'm having to try the NAND restore to 2.3.1 to get it to work. I rebooted the phone multiple times, no problems but then after a phone call...get a notification that the sd card was suddenly removed and now I'm back to square one..
Does anyone have a clue as to why my phone decided to unmount the internal storage and why I can't get this thing to work correctly 100%?
Thanks guys..
Btw, I usually can't mount the USB storage using clockwork when I get these errors. I have to keep rebooting the phone until I get lucky enough to format the /sdcard, then try and mount it up to my computer.
Just rebooted the phone, flashed /system, and mounted up the USB..
Can anyone explain this??
otisranson said:
Hey guys,
I think my phone is partially bricked. I know that sounds weird, but here's the situation:
I was able to unlock my bootloader (faced multiple write errors using fastboot but it did unlock eventually), I can't reflash using Odin (it fails Error is "Complete Write Fail"), when I tried to format some partitions using clockwork I get:
E: format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
No linux newb here, so I'm guessing my internal partition is fubared..
Here's what's funny... I can flash a rom and boot into the rom usually on the first try. If I boot into the rom, it runs fine until I reboot the phone. Then it takes another *LITERALLY* 10 times of pulling the battery and rebooting the phone because the phone sticks at the Google boot logo. I can boot into recovery, fastboot, no problem.
As my phone sits right now: I can flash clockwork, bootloader unlocked. I'm having to try the NAND restore to 2.3.1 to get it to work. I rebooted the phone multiple times, no problems but then after a phone call...get a notification that the sd card was suddenly removed and now I'm back to square one..
Does anyone have a clue as to why my phone decided to unmount the internal storage and why I can't get this thing to work correctly 100%?
Thanks guys..
Btw, I usually can't mount the USB storage using clockwork when I get these errors. I have to keep rebooting the phone until I get lucky enough to format the /sdcard, then try and mount it up to my computer.
Click to expand...
Click to collapse
otisranson said:
Just rebooted the phone, flashed /system, and mounted up the USB..
Can anyone explain this??
Click to expand...
Click to collapse
yup, this ones explainable. classic symptoms of a ns with its internal sd card dying/dead. it happens way too often unfortunately. luckily its a fairly easy and inexpensive repair, if youre not under warranty.
Any direction on how to fix it while not under warranty?
Or take it to tmobile?
otisranson said:
Any direction on how to fix it while not under warranty?
Click to expand...
Click to collapse
check out any local mobile device repair shops. you could probably do it yourself if you dont fear taking the phone apart, it should be to difficult of a repair. its just a matter of buying a replacement(ebay?), taking the phone apart, and replacing the sd.
Found this breakdown, but I don't see where the internal storage is..
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
I've been having similar issues..what is the exact part name for the SD?...I wanna search to buy one
Sent from my Nexus S 4G using XDA Premium App
I think its:
Samsung KB100D00WM-A453 memory package and S5PC110A01 1GHz Cortex A8 Hummingbird Processor.
I'm going to try to find another nexus s mother board as a whole, that's my only option.
otisranson said:
Found this breakdown, but I don't see where the internal storage is..
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
Click to expand...
Click to collapse
I think it's in step 10
i seen something a few weeks ago online on how to replace this...it was a video..i just cant remember where i seen it!
I ended up just purchasing a new phone on ebay.. If I find a nexus s with a cracked screen, I will swap out the mobo.
You can check whether there are blocks flagged as bad by FTL (Flash Translation Layer) in recovery. Check recovery.log file (it can be, the bad blocks will show up after formats).
I was running TWRP 2.7 and told it to wipe the drive. An hour later, it looked like it hadn't moved. I powered down. Then the system bootlooped and TWRP stopped working, not loading past the splash screen.
Using Fastboot I was able to reinstall TWRP 2.7 but it can no longer access the internal drive. I am told it is a size zero. I can't wipe the drive it fails for errors. I can't seem to find a solution.
I downloaded the stock firmware from Asus and tried to install that. No luck, it fails out immediately. I only tried to install the zip file inside of the zip file from Asus using TWRP. No matter what I can't delete or remove the partitions. If I run TWRP 2.6.3 it asks for a password I don't have, as if the drive is encrypted. I also tried Philz CWM and normal CWM and nothing can touch the partitions.
I am starting to get really worried now. I can't seem to find a simple process to restore to stock. I am TEMPTED to use the WIPE DATA function of the Asus Bootloader. But without the Asus recovery on there, I have no idea what will happen.
Can anyone recommend a course of action to restore this to stock? At least to get the Asus Recovery on there? I am running bootloader 10.6.1.14.10.
Thanks to everyone that can help!!!
In TWRP, format (not only wipe) data, but this time be patient until it is finished.
_that said:
In TWRP, format (not only wipe) data, but this time be patient until it is finished.
Click to expand...
Click to collapse
I am totally beside myself. I did exactly as you mentioned about 15 times last night. All that would happen is TWRP would restart after I typed YES.
Today, I did it, and BAM it started working. I will let everyone know how it went in a few hours. I am not touching it again.
Maybe I was just way overtired at that point.
Thank you for the help!!
BigKenW said:
I am totally beside myself. I did exactly as you mentioned about 15 times last night. All that would happen is TWRP would restart after I typed YES.
Today, I did it, and BAM it started working. I will let everyone know how it went in a few hours. I am not touching it again.
Maybe I was just way overtired at that point.
Thank you for the help!!
Click to expand...
Click to collapse
That did it! I was able to install CROMBi-KK and am moving forward!!!
I'm in basically the same boat (I think I got there the same way), except when I try to format now, I get:
Code:
Updating partition details...
E: Unable to mount '/system'
Full SELinux support is present.
Formatting Data using make_ext4fs function.
This is where it sits for an indefinite period of time. In my troubleshooting attemps I've had it display similar messages elsewhere about being unable to mount the /system folder. I tried going into Mounts even and it won't let me check that box.
For now, I'm going to just leave this sit here at this screen for a few hours while I "work" and see what happens, but if anyone has any brilliant ideas, I'm all ears!
SgtMac02 said:
I'm in basically the same boat (I think I got there the same way), except when I try to format now, I get:
Code:
Updating partition details...
E: Unable to mount '/system'
Full SELinux support is present.
Formatting Data using make_ext4fs function.
This is where it sits for an indefinite period of time. In my troubleshooting attemps I've had it display similar messages elsewhere about being unable to mount the /system folder. I tried going into Mounts even and it won't let me check that box.
For now, I'm going to just leave this sit here at this screen for a few hours while I "work" and see what happens, but if anyone has any brilliant ideas, I'm all ears!
Click to expand...
Click to collapse
You should let it finishes the formatting on your /data partition and ignore the /system for now. One user had a very similar issue and reported that it took almost 4.5 hours on his/her device for formatting on his /data partition. It was up running after that so be patient and plug the AC in for your device until it is finished the job, good luck....:fingers-crossed:
LetMeKnow said:
You should let it finishes the formatting on your /data partition and ignore the /system for now. One user had a very similar issue and reported that it took almost 4.5 hours on his/her device for formatting on his /data partition. It was up running after that so be patient and plug the AC in for your device until it is finished the job, good luck....:fingers-crossed:
Click to expand...
Click to collapse
Dude. I don't know how long it actually took. I had waited before for more than an hour and assumed it wasn't going to work since there was ZERO indication of progress. I started it this morning and checked it after I came back from lunch about 4+ hours later and it did indeed work out. I was able to successfully reflash a new ROM again after that and all is well! I'm so glad I finally stumbled across this thread or I don't think I would have ever though to just leave it to do anything for more than an hour. I still can't believe it would take that long...but I guess it does!
I had the same problem (twrp showed internal as 0gb). Is a twrp 2.7 thing or a kitkat thing. Thanks to know I wasnt the only one who f uped. Now I'm back and running. Thanks for the help.
Sent from my UNLOCKED SM900V.
I hope it's not "Another brick in the Wall"
The format was interrupted and now I'm getting the can't mount internal memory. I started the format again and plugged it in and I'm going to leave it alone over night. I hope it works.
Hi, I've made a couple posts about this in both the One M9 and Sprint One M9 forums seeking some help with this phone that signs point to not being a lost cause but I myself am very lost. Neither of those forums seem particularly active at this point in the phone's lifespan so I decided to try posting here. I'll explain what happened and how the phone is behaving and refusing, despite my best efforts, to go back to normal.
I had my Sprint M9 rooted, unlocked, S-Off running Leedroid with TWRP. Last Tuesday, some sort of cascading failure happened causing google services to crash, everything else started crashing and I kept getting crash notifications over and over so I eventually rebooted the device. However, it didn't boot. I eventually got into TWRP, probably jumped the gun on wiping data and system after wiping cache failed to yield any results, but I had a rom on my sd card so I figured I'd just reflash because it was obvious there was something seriously wrong. I couldn't get into download mode.
Cut to now. I have bootloader access, I have TWRP access, none of the main partitions will mount in TWRP (invalid argument). I didn't have any encryption on these partitions but I get the error "Unable to find crypto footer". The solution I see most often touted for the mounting issues is to "Format Data" in TWRP but oddly, I type "yes", I swipe, and I'm met with the exact same errors. This is where it gets weird. As I mentioned, I'm S-Off and unlocked. You'd think I could flash hosd via fastboot, head to download mode and just get a clean RUU install going. And it looks like I can do that, the command line messages I get from fastboot flashing are "OKAY", not "FAILED", and yet, nothing actually flashes! I confirmed this via trying to flash the stock recovery over the TWRP image via fastboot, then booting recovery and still finding TWRP. I'm VERY confused about all of this.
I've seen some info in my searches that indicates some of this stuff can happen if your emmc is faulty (hardware failure), but I've pulled the dmesg log and can't find any errors that would be indicative of emmc failure. Anyone have any idea where to go next? Because I'm stumped.
I've attached a recovery.log and dmesg if anyone wants to take a look. Any suggestions would be greatly appreciated because I'm frankly out of ideas.
So i was using my phone 5 days ago like normal and sudendly it decided to reboot itself, after that it got stuck on the 4 balls android logo and doesnt boot into the system anymore.
what iv tried so far:
-Full Wipe
-Download and flash a full factory image, then full wipe
-Download and flash TWRP with SlimRom + Gapps then full wipe
Nothing works, it always get stuck in bootlogo, it just sits there dancing like its booting normally but it never does, im runing out of options here, what can i do guys?
Note: i have access to bootloader, all button works, also have access to recovery without any issues.
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
audit13 said:
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
Click to expand...
Click to collapse
Let me download a kitkat image and see what happens, ill report back as soon as i do it
audit13 said:
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
Click to expand...
Click to collapse
So... i flashed the first build available in google site for this phone and it booted perfectly, im going to try to flash the last version again and see what happens, but why did this happened then?
mediavieja said:
So... i flashed the first build available in google site for this phone and it booted perfectly, im going to try to flash the last version again and see what happens, but why did this happened then?
Click to expand...
Click to collapse
Aight so i flahshed twrp and slimrom again but im once again stuck on bootloop what do u suggest?
This is a sign that something is faulty in the memory chip. Stock KK, and possibly stock LP, may work but MM will always results in bootloop.
audit13 said:
This is a sign that something is faulty in the memory chip. Stock KK, and possibly stock LP, may work but MM will always results in bootloop.
Click to expand...
Click to collapse
Nope, tried stock MM (latest stock) and didnt work
Try LP and see if it works. If it doesn't, it's definitely the memory chip.
audit13 said:
Try LP and see if it works. If it doesn't, it's definitely the memory chip.
Click to expand...
Click to collapse
Must be then, cause i tried LP and didnt worked
I think it has something to do with differences in partition layouts between kk and LP/mm.
audit13 said:
I think it has something to do with differences in partition layouts between kk and LP/mm.
Click to expand...
Click to collapse
Do u know if theres anyway to fix it?
I know of no way to fix this and I've not seen a post from someone that was able to run LP or mm on an affected phone.
audit13 said:
I know of no way to fix this and I've not seen a post from someone that was able to run LP or mm on an affected phone.
Click to expand...
Click to collapse
Awww well thanks anyway for all ur help men, i really apreciate it
You are very welcome. We are all here to help and learn from each other.
The cheapest solution may be to buy a used nexus with a busted screen but working motherboard and perform a bit of phone surgery. I've done this a few times over the years with great results.
There is a problem where /persist gets easily corrupted. Especially when you have to force reboot. A LOT. This might be your problem.
To find out if this is the case, please do the following:
1. Because you are using a Nexus 5, please download the Skipsoft Unified Android Toolkit (SUAT) and install it. Google it if you need to. Its windows only from what i can tell. Go through the screens until you configured the toolkit. You don't need pro for this setup. If you are running on linux or mac, please find a equivalent set of tools which can do the next 4 steps.
1.5. Unlock the boot-loader. Don't bother about backup, if persist is dead and you have not unlocked the boot-loader before, you WONT get your data back. (Better hope you made a partial-backup beforehand.) (Good thing is, if you did unlock the boot-loader before this problem occurred, RECOVERY OF DATA IS STILL POSSIBLE!)
2. Boot into TWRP recovery. When you get the modifications warning screen, TURN ON modifications. YOU NEED THIS FOR LATER ON.
2.5. If you already have the boot loader unlocked before the problem occurred, NOW is the time to do a backup! If /persist is dead, you will need to erase and re-flash to get android back!
3. On the bottom of the screen should be a button with 4 lines (the middle 2 should be shorter than the outer 2 if you are that blind). That is the log. Keep in mind where that button is. Go into mount and press persist to attempt to mount it.
If persist mounts successfully:
/persist is alive and kicking. Android should be starting successfully. If this is not the case, look for other reasons on why this could be failing. If other options have been exhausted, then you have a dead memory chip. Get it replaced! (And go for a upgrade while you are at it, 16 GB is not a lot. )
If persist does not mount:
Uh oh, looks like trouble. Now this is the time to check your logs. Remember the button i told you to remember? Press that button. Look for a red line that says "Unable to mount /persist (Invalid argument)"
"Unable to mount /persist (Invalid argument)" was not present.
Twrp might not be showing it or there is no way of recovering it. You have a 50% chance of recovery. Do you want to risk it? If so, carry on to step 4.
"Unable to mount /persist" was present but the text in the brackets was different.
Lookup the error code. If it is not any I/O input output errors then you should be fine to continue. If it is, Recovery is not possible.
"Unable to mount /persist (Invalid argument)" was present.
Oh dear. Looks like we have dead partition. However, because we got what we were expecting, recovery is possible. Follow the next steps. They can be done from a ADB shell on the PC or on the device.
4. Load up a ADB shell and run the following command:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
This basically runs a file system check. IT should find problems with the partition and rebuild the file system. Now here comes the next bit. (And this is where you hope you read everything and backed up beforehand.)
5. Go to the main menu and press mount. Try mounting everything. Now back out and press wipe. Press advanced wipe. Select everything that you can. Then "swipe to format" everything. Once that is done, go back into the main menu and press reboot. Press bootloader. You will get a warning about no OS, just swipe to reboot. (Why do you think we are rebooting back to boot-loader?)
If everything went well, you should now be able to re-flash with your choice of ROM. You may have to re-flash normal android first though. Look up guides on how do that.
HSF3232 said:
There is a problem where /persist gets easily corrupted. Especially when you have to force reboot. A LOT. This might be your problem.
To find out if this is the case, please do the following:
1. Because you are using a Nexus 5, please download the Skipsoft Unified Android Toolkit (SUAT) and install it. Google it if you need to. Its windows only from what i can tell. Go through the screens until you configured the toolkit. You don't need pro for this setup. If you are running on linux or mac, please find a equivalent set of tools which can do the next 4 steps.
1.5. Unlock the boot-loader. Don't bother about backup, if persist is dead and you have not unlocked the boot-loader before, you WONT get your data back. (Better hope you made a partial-backup beforehand.) (Good thing is, if you did unlock the boot-loader before this problem occurred, RECOVERY OF DATA IS STILL POSSIBLE!)
2. Boot into TWRP recovery. When you get the modifications warning screen, TURN ON modifications. YOU NEED THIS FOR LATER ON.
2.5. If you already have the boot loader unlocked before the problem occurred, NOW is the time to do a backup! If /persist is dead, you will need to erase and re-flash to get android back!
3. On the bottom of the screen should be a button with 4 lines (the middle 2 should be shorter than the outer 2 if you are that blind). That is the log. Keep in mind where that button is. Go into mount and press persist to attempt to mount it.
If persist mounts successfully:
/persist is alive and kicking. Android should be starting successfully. If this is not the case, look for other reasons on why this could be failing. If other options have been exhausted, then you have a dead memory chip. Get it replaced! (And go for a upgrade while you are at it, 16 GB is not a lot. )
If persist does not mount:
Uh oh, looks like trouble. Now this is the time to check your logs. Remember the button i told you to remember? Press that button. Look for a red line that says "Unable to mount /persist (Invalid argument)"
"Unable to mount /persist (Invalid argument)" was not present.
Twrp might not be showing it or there is no way of recovering it. You have a 50% chance of recovery. Do you want to risk it? If so, carry on to step 4.
"Unable to mount /persist" was present but the text in the brackets was different.
Lookup the error code. If it is not any I/O input output errors then you should be fine to continue. If it is, Recovery is not possible.
"Unable to mount /persist (Invalid argument)" was present.
Oh dear. Looks like we have dead partition. However, because we got what we were expecting, recovery is possible. Follow the next steps. They can be done from a ADB shell on the PC or on the device.
4. Load up a ADB shell and run the following command:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
This basically runs a file system check. IT should find problems with the partition and rebuild the file system. Now here comes the next bit. (And this is where you hope you read everything and backed up beforehand.)
5. Go to the main menu and press mount. Try mounting everything. Now back out and press wipe. Press advanced wipe. Select everything that you can. Then "swipe to format" everything. Once that is done, go back into the main menu and press reboot. Press bootloader. You will get a warning about no OS, just swipe to reboot. (Why do you think we are rebooting back to boot-loader?)
If everything went well, you should now be able to re-flash with your choice of ROM. You may have to re-flash normal android first though. Look up guides on how do that.
Click to expand...
Click to collapse
Well i followed the procedure to fix persist, i was getting Unable to mount "/persist" (Invalid argument) so bu running command e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist i was able to mount it, after that i rebooted the phone to bootloader and i was able to flash and run the latest software update so i have to say thank you very much sir im gonna try to put slimrom now on this bad boy and change the post title to fixed