Related
Attempting to partition sd card with ext4 -a process I completed multiple times successfully on a Nexus One, the process appeared to complete but now the phone will not mount the sd card. I've tried a wipe/reset, to no avail. I can still access and partition the sd card through adb, but the phone cannot mount it to format/partition, restore from recovery, partition sd-card from within ClockWork Recovery, nothing. I've re-partitioned the sd card through adb, which indicated a successful completion, but the phone still refuses to mount the sd card. If this weren't a Nexus S with it's cursed internal sd-card I would simply swap out the sd card with another or format it externally like all the google topics I pull up on the subject suggest.
Is this fixable or has the fused sd-card scenario become a liability?
Common Error messages:
Can't mount /sdcard
Can't mount /sdcard/.android_secure
Phone: Nexus S
Recovery Img: ClockworkMod Recovery 3.0.2.4
Rom: CM 7.0.3 (now wiped, cannot put back on since sd card won't mount)
fstab:
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard vfat rw
Can mount everything except the last one, /sdcard.
I've attempted all: wipe/reset, format using clockwork, partition using clockwork, partition using adb, changing fstab, etc etc.
All topics I've found on the net end up being resolved by taking out the sd-card and formatting externally or using different card. i've had a N1 for well over a year and done far worse without problems, this phone seems to be very fragile for a 'developer' phone.
Jacks0n said:
Attempting to partition sd card with ext4 -a process I completed multiple times successfully on a Nexus One, the process appeared to complete but now the phone will not mount the sd card. I've tried a wipe/reset, to no avail. I can still access and partition the sd card through adb, but the phone cannot mount it to format/partition, restore from recovery, partition sd-card from within ClockWork Recovery, nothing. I've re-partitioned the sd card through adb, which indicated a successful completion, but the phone still refuses to mount the sd card. If this weren't a Nexus S with it's cursed internal sd-card I would simply swap out the sd card with another or format it externally like all the google topics I pull up on the subject suggest.
Is this fixable or has the fused sd-card scenario become a liability?
Common Error messages:
Can't mount /sdcard
Can't mount /sdcard/.android_secure
Phone: Nexus S
Recovery Img: ClockworkMod Recovery 3.0.2.4
Rom: CM 7.0.3 (now wiped, cannot put back on since sd card won't mount)
fstab:
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard vfat rw
Can mount everything except the last one, /sdcard.
I've attempted all: wipe/reset, format using clockwork, partition using clockwork, partition using adb, changing fstab, etc etc.
All topics I've found on the net end up being resolved by taking out the sd-card and formatting externally or using different card. i've had a N1 for well over a year and done far worse without problems, this phone seems to be very fragile for a 'developer' phone.
Click to expand...
Click to collapse
Are you able to go with ADB through the directories?
and yeah, false Section! Q&A would be better
I am having the same issue. I actually just got my phone back from Samsung support (which is real ****ty) because the SD card started having I/O issues.
According to the ticket information they replaced the PCB.
Anyway, I immediately installed Clockwork recovery and transferred the latest Blandroid rom to the root of the SD card. No matter what I do I cannot mount the SD card from the recovery menu or format it from the recovery menu. Mounting USB storage works fine, though.
Hiya I got the same problem
Any salutation yet ?
Yeah. Don't format the internal storage with clockworkmod etc.
I have that issue I cant even open phone now
albundy2010 said:
Yeah. Don't format the internal storage with clockworkmod etc.
Click to expand...
Click to collapse
Hi The phone just stuck in boot logo I can patch iso file from adb though but I cant mount or even wipe devlink cache I dont know what to do ?
Did you ever get this resolved? If so, can you tell me how you did it?
Jouten said:
Did you ever get this resolved? If so, can you tell me how you did it?
Click to expand...
Click to collapse
1.power off...on it back...test it
2.plug your usb cable, boot into recovery..will heard usb sound from your PC, if does not work, try several times plug the usb untill you get usb sound...unplug, then reboot...
3.fresh install ROM...
Yeah, don't mess with the internal memory. I semi-bricked a Droid Incredible one time doing that. It ended up making all the internal partitions FAT. Took me hours to fix it. Be careful. I am afraid to even do it on my crespo4g. When I mount it in gparted running Linux Mint, the internal sd card showed up as not partitioned. I didn't even think about trying to partition it thinking back on the Incredible.
A solution, at least, for flashing/updating roms
Just happened to me, using CM9 after enabling the encryption I can't access the /data /sdcard paths. It would be nice to be able to read them but for me the biggest problem was how to update to the latest CM9 nighty.
In the end I've tricked the clockwork recovery to think the cache partition is the sdcard. I'll post the method in case someone find it useful.
1. Tranfer the update to the cache partition.
- Normally big enough, wipe it from the cwm if there is not enough space
adb push update-cm-9-20120305-NIGHTLY-crespo-signed.zip /cache/update.zip
2. Log into the phone and mount cache to sdcard.
adb shell
mount /dev/block/mtdblock4 /sdcard
3. Go into the cwm option to flash the uploaded package, it wont give you the mount error as we already mounted /sdcard
4. After the update log again and clear the update package, and unmount /sdcard
adb shell
rm /cache/update.zip
umount /sdcard
As long as you don't have to wipe you can continue updating and using your encrypted storage without much trouble
Help, internal storage not showing
Hi,
I wanted to go back from CM9 to Stock rom, but now I did something wrong (don't know what exactly) and my device is still on CM, but unable to access the internal storage. I cannot even take pictures or access it through CWM.
Any thoughts?
Hi i flash locky another CWR AND IT'S FIX LUCKY ME B^)
Sent from my Nexus S using xda app-developers app
getting SD card back
rellivisit said:
Hi,
I wanted to go back from CM9 to Stock rom, but now I did something wrong (don't know what exactly) and my device is still on CM, but unable to access the internal storage. I cannot even take pictures or access it through CWM.
Any thoughts?
Click to expand...
Click to collapse
I have had no luck using multiple methods to partition sd card with Nexus S. Each time I can view the modified fat32 partition from windows, add files etc, but cannot be recognised from within CWM recovery.
Left me unable to reflash roms etc.
The only thing which has worked for me is to use mini tool for windows and mount usb storage from recovery. Do a refresh from mini tool and it should come up in the list of drives. delete the partition(s) you find there (not your notebook ones of course), and reformat it as fat 32.
CWM>Advanced>Reboot recovery, move over your rom to the sd card, then try to find it in CWM, should now show up :fingers-crossed:
So yeah, my phone was regular 2.3.4 and it wouldn't always reboot easily (took multiple tries). So I figured I'd install CyanogenMod 7 like all the cool kids. I'm a programmer, this should be easy, right? Wrong.
So after much trial and error fastboot decided to randomly find my phone and let me unlock it (long story...). I start playing around with adb and fastboot, having a good old time. I decide to do the ClockworkMod Recovery image and it works great. I try to do an "update from sdcard" with the latest CyanogenMod for Nexus S and it amazingly works!... Except that it still won't boot up. It sits on the Google loading screen--I suspect failing to mount anything.
I found out about this:
Code:
ClockworkMod Recovery v4.0.0.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/platform/s3c-sdhci.0/by-name/media (null)
2 /system ext4 /dev/block/platform/s3c-sdhci.0/by-name/system (null)
3 /cache yaffs2 cache (null)
4 /data ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata (null)
5 /misc mtd misc (null)
6 /boot mtd boot (null)
7 /recovery mtd recovery (null)
8 /bootloader mtd bootloader (null)
9 /radio mtd radio (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Notice all of the (null)s....
Also this:
Code:
-- Install from sdcard...
Finding update package...
I:Update location: /sdcard/update.zip
W:failed to mount /dev/block/platform/s3c-sdhci.0/by-name/media (No such file or directory)
E:Can't mount /sdcard/update.zip
Installation aborted.
mtd: successfully wrote block at 0
I:Set boot command ""
E:Unable to write to ums lunfile (No such file or directory)
...and this, clearly from fstab:
Code:
/dev/block/platform/s5pc110-onenand # mount -a
mount -a
mount: mounting /dev/block/platform/s3c-sdhci.0/by-name/userdata on /data failed
: No such file or directory
mount: mounting /dev/block/platform/s3c-sdhci.0/by-name/system on /system failed
: No such file or directory
mount: mounting /dev/block/platform/s3c-sdhci.0/by-name/media on /sdcard failed:
No such file or directory
There's no s3c-sdhci.0 in /dev/block/platform.... only s5pc110-onenand (which happens to be the title of the processor and memory used in my phone).
So yeah, that's where my brain gives out.
I'd like to install CM7, or at the least get a working phone back somehow.
Oh yeah, I tried doing adb shell and a nandroid restore command w/ downloaded nandroid backup. No love. It told me "unknown volume for path [/sdcard] Can't mount /sdcard". No ****.
Ideas?
Thanks!
Small update:
about 1 out of 100 times, it'll allow me to mount the sdcard after some random fiddling. I have tried multiple recovery images, erasing partitions, flashing random things... nothing works!
The one or two times it mounted the sdcard, I was able to perform an "update from sdcard" but then it would just do what it has done for a long time--sit at the google loading screen for hours and never actually boot into the real OS.
Sigh. Hardware issue maybe?
Hi,
what's your phones status?
My Nexus seems at a similar state now I came across http://forum.xda-developers.com/showthread.php?t=991276 and had to try it (why not, I have nandroid backups, Titanium etc. ...) I applied a setting, rebooted and got stuck at the google logo. It would boot into recovery but there it has no access to sdcard, system, data (but cache is mounted). After lots of fiddling I got it to work once, whiped, flashed a rom and all looked good again. But now I did a reboot and the phone is stuck again and in recovery (CWM 3.something) I get no sdcard
What happened and how to fix it?
I managed to flash a stock system back on the phone and it still didn't work, so I called Samsung and they let me RMA the phone. I got it back three weeks later, in good shape. They had to replace the PBA, the mainboard, and they did it all for free. They even gave me a shipping label to use when I shipped it out. Nice.
At the least, I think it's necessary to flash a stock bootloader and lock the phone before calling them.
Good luck!
Good for you
I tried flashing a stock rom, both using fastboot and also using Odin, both methods fail or get stuck while flashing the system.img
Looks like I've screwed up
If I could at least once get to the data on sdcard ...
i think i found a workaround
i tried flashing the old clockworkmod (3.1.0.1) and the flashing the latestest one twice and then clockworkmod was able to mount the sdcard. huge relief. installed the rom and then rebooted and the system booted well.
also tried installing the clockwork manager app and flashing the latest recovery from the app and then rebooted into recovery. it was able to mount the sdcard now.
not sure if this random success or a fix. it worked.
Had the same exact issue. Sprint tech replaced the phone for me for $35 without insurance. But basically the internal memory would only mount once every 10-100 reboots.
Definitely a manufacturing issue.
obsanity said:
Had the same exact issue. Sprint tech replaced the phone for me for $35 without insurance. But basically the internal memory would only mount once every 10-100 reboots.
Definitely a manufacturing issue.
Click to expand...
Click to collapse
Have you tried reflashing the recovery twice?
Did the sprint tech provide the details on what exactly the issue was?
In my case, the phone is contract free and I have to approach samsung support if this issue occurs again.
Since the sdcard is some times mounting, i am hopeful that there should be a way out via sw.
gsrdemon said:
Have you tried reflashing the recovery twice?
Did the sprint tech provide the details on what exactly the issue was?
In my case, the phone is contract free and I have to approach samsung support if this issue occurs again.
Since the sdcard is some times mounting, i am hopeful that there should be a way out via sw.
Click to expand...
Click to collapse
Samsung service center repaired the device (mother board replaced); in warranty.
Sent from my Nexus S
Is this phone salvageable? I have quite the odd problem. I have plenty of backups, so I'm not worried about fully wiping the Nexus S.
I was running CM9 Alpha 11 when I heard about the ICS 4.0.4 OTA update for the I9020A. I rebooted into my recovery to make a nandroid backup. That's when the problems started. Mounting /sdcard, /system and /data fail, but mounting /cache works. Attempting to mount to USB Storage gives a "Unable to write to ums lunfile" error. When I noticed that the backups weren't taking, I tried to reboot normally but encountered bootlooping. As a last resort, I tried "fastboot oem unlock" but it freezes. Battery pull gives "FAILED (status read failed (too many links))" on windows.
Model: Nexus S I9020A
HW Version: Rev 16
Bootloader: I9020XXKA3
Baseband: I9020UCKF1
Carrier: ATT
ROM: CM9 Alpha 11
Recovery: ClockworkMod Touch Recovery v5.8.0.2
Bootloader: Locked
Busybox: v1.19.3-cm9
Accessible: fastboot, adb, adb shell with #, busybox, and recovery.
Symptoms: Bootlooping, unmountable /sdcard, /system and /data, cannot mount to USB Storage, bootloader does not unlock.
EDIT: Found this unfortunate bit of news. Looks like I'll be sending it in for repairs and hoping they won't notice the recovery.
EDIT2: I found out that I can flash zip files through a roundabout method to mount /cache as /sdcard. Unfortunately, all I've been able to do is to flash recovery since system and everything else isn't mounted. I haven't been able to get ./flash_image to work. I've tried making the mounts executable as well as flash_image. My last option is looking for the "Android system recovery <3e>" in the form of a .zip and flashing that so it looks like my warranty is still intact.
adb push update.zip /cache
adb shell
mount /dev/block/mtdblock4 /sdcard
Click to expand...
Click to collapse
After this, you can use the recovery to flash the update. So far, I've tested going back and forth between ClockworkMod Recovery 5.0.2.0 and ClockworkMod Touch Recovery 5.8.0.2.
EDIT3: ./flash_image doesn't work. However, flash_image works because I have busybox installed on my phone.
Can't mount SD card in recovery. See http://bit.ly/LgBTUN.
Tried fix permissions, mount sdcard in recovery says Error mounting /sdcard, other stuff too. Still no go.
Found forum posts with same problem in several HTC phones but don't think the fix works for TF101.
I'd like to put the Megatron ROM on my TF101 though I'd be happy just to get ASUS upgrades. They keep failing - I think from my Dvorak keyboard mod (see device config below).
Any ideas?
TF101. Stock, rooted rom with modded key mapping for Dvorak keyboard when docked. Android Version 3.2.1. Kernel 2.6.36.3 [email protected] #1, Build Number HTK75.US_epad.8.6.5.19-20111107.
Can you still boot Android or did you already wipe?
I also see ROM manager, which is usually bad news for the TF...
That's a rather old recovery, if you can get ADB access you can try my PERI tool to reflash a newer recovery that should mount properly, and then flash a ROM with that.
Good luck!
First, thanks for the help.
I tried your tool. Besides having entertaining comments, it just left me frustrated.
You can see some screenshots at https://docs.google.com/open?id=0B46V3MQdpAUOek1GRGlvS0FKTms
I'm wondering if the problem is that I can't mount / as RW. Perhaps I'm just not getting the right args to adb's mount command. I think I should be able to remount / RW as I can run "adb shell" and then "su" to get the "#" prompt.
I do think part of the problem is that /sdcard is not actually my sdcard. It is a symlink to /mnt/sdcard which is where the physical sdcard is mounted.
I tried to modify init.ventana.rc. I think that is the right file - I just found it by poking my head around. This is what I wanted to change:
Code:
on early-init
mount debugfs debugfs /sys/kernel/debug
export EXTERNAL_STORAGE /mnt/sdcard
mkdir /mnt/sdcard 0000 system system
# for backwards compatibility
symlink /mnt/sdcard /sdcard
But I can't mount / RW so I can't change it. I tried this:
Code:
$ adb root
adbd cannot run as root in production builds
$
I'm definitely rooted. I can su to root in ADB. I also have a SuperUser that seems to be working.
Update: I can mount / RW via ES File Explorer. I can then adb shell, su, and then update files in /. I pushed my updated init.ventana.rc but when I rebooted it reverted to the original.
I'm terribly frustrated.
Any ideas? I seem to have a totally useless CWM. I can't even put a file on /sdcard/update.zip because the sdcard isn't booted when I'm in recover.
Once I get / mounted RW, can I just copy a working CWM into some system directory?
I've spent half my day messing around with this thing. I'm very comfortable with the command line and would happily do a manual install if someone could tell me how to do that.
I tried the adb equivalent of:
Code:
run_program("/sbin/busybox", "dd", "if=/tmp/recoveryblob", "of=/dev/block/mmcblk0p4");
using the 5.5 recoveryblob but it didn't seem to do anything. If I just knew the magic commands, I'd be happy to do them.
Hi there.
I just released the beta version of my EasyFlasher tool.
Try using that, it'll flash Rogue Recovery for you which should successfully mount the sdcard.
You may need to use that (It's Nvflash based) It won't work on a Tf101G or Sl101 though. Give it a shot.
PERI didn't work because your ADB drivers don't work.
Thanks for your help. I finally got a working CWM by following this thread. I then flashed the CWMs you pointed to.
Problem solved.
Though I can always f-up my upgrade to CM9 and be back here for help in a few hours.
Too Funny
I just posted my thanks reply and then noticed that you two pointed me to the solution that I found.
I appreciate your help and timeliness (and your nvflash program too).
Neil
Got my TF101 BK70 SBK1 in same situation and this thread helped me a lot.
Just put my tf into apx mode (hold up + power for 7 seconds, screen stays black but device manager can see APX device connected, then use Universal Naked drivers to fix it.
After that, just open EasyFlasher and choose which recovery you want.
I also had the same problem, I didn't see this thread so I used this workaround:
if you have the keyboard dock you can mount an external usb drive as the sdcard (under the mount options) and do all the backups/flashing from there
Sent from my Transformer using xda app-developers app
There are two sd cards, the internal sd card which is the phone's built-in USB storage, and external sd card which is the removable sd card that is physically located at the back of the phone and is sealed by your phone's battery.
so technically speaking you should be choosing the "choose zip from external sd card" based on how you described storing your rom.
I'm not sure as to why your sdcard is unmounted, but you can remount it back using CWM. There should be a "mounts and storage" section in CWM menu, where you can remount the internal USB storage by selecting "mount /sdcard".
If you want to recover the data in your Android phone, just go to http://android-recovery.net/.
Need help with this can't mount /sd card /
Here is what I am getting (pics). This is on the Tf101 with CWM via 1 click root method
Trying to run e2fsck with the tablet on TWRP, didn't worked and now adb no longer recognizes the tablet when in recovery.
Tried using the command promp in recovery, no go as well.
Trying to fsck /system and /data, because my system stopped working again
Asked Man said:
Trying to run e2fsck with the tablet on TWRP, didn't worked and now adb no longer recognizes the tablet when in recovery.
Tried using the command promp in recovery, no go as well.
Trying to fsck /system and /data, because my system stopped working again
Click to expand...
Click to collapse
Did you find a solution to this? I'm stuck in TWRP with a busted /data dir which I want to fsck.
Bumping this very old thread. I have the same problem, /data got corrupted and mounts read only, and my device bootloops. TWRP works fine, but I'm unable to wipe because of this. The filesystem is ext4, and e2fsck won't touch it. Is the anything to do besides formatting it? What happens if I do that?