Database Info

Can't mount sd card

Hi there I have a problem
My problem is that i've just root'ed my HTC Desire (I think?)
But my Desire won't boot right.. It only boots to recovery mode...
If i try to install an update.zip with clockwork it says can't read sd card
Pretty much anything i do on clockwork it says "E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD:"
I have also tried adb but it says device not found
My computer registres my Desire when i plug it in but it doesn't recognize it..
What shall i do next?
Ps. I am running windows 7 x64
Sorry for any spelling errors i hope you understand and are able to help me

I had a similar problem. Try booting into clockworkmod recovery, connect your phone to your PC and select mount USB (or something like that) from the partitions menu. This should give you access to your SD card on your PC. Next, backup the contents of your SD card and then delete all partitions. I used gParted but i guess you can use disk manager in windows. One deleted, don't format the card or anything, just reboot the phone and hopefully you should boot up OK. Now you can format the SD card from within Android. Before you do all this is might be worth removing your SD card and seeing if you can boot up OK without it.

Thanks for reply
When I choose to "mount usb storage" nothing really happens it is not getting recoqnized
The phone won't boot without sd-card
Do you or anyone else know if you can sync your desire from recovery mode?

One step further
Okay i now got one step furter
My phone can now start up, but it still can't registre sd card
It just says sd-card removed
Any ideas

have you tried the "mount usb" option again? Although nothing appears to happen on the phone, you should be able to access the card from your PC. it worked for me in both Win7 and Ubuntu. Other than that I can't think of anything else apart from trying a different SD card.

I can't choose mount usb storage any more.. I can't get into clockwork
Now, when i press recovery I get into a black screen with at red triangle and i can choose from 3 or 4 things, inluding wipe and apply udate
I've allready tried a diffrent sdcard

Similar problem but extra issues
Searched for hours and been in a live chat a number of times and posted on another forum but can not find specific solution.
I wanted to install this http://forum.xda-developers.com/showthread.php?t=789830 HD rom so I partitioned my sdcard (successfully, to ext3 1.5gb, 33mb linux swap, rest fat32) and started wiping via ClockworkMod recovery.
That is when I ran into problems.
Now I can not mount my sdcard - "E:Can't mount /dev/blocl/mmcblk0 (or /dev/block/mmcblk0p1) (invalid argument) Error mounting SDCARD:!"
When I reboot, it just loops.
WinXP will detect my device via adb (when in recovery) but can't see the sdcard.
I had never used fastboot, so I am not sure if I am typing commands correctly.
Htc Desire 2.2 GSM * Uk 3 network * 8gb class2 sdcard * Bravo pvt1 ship S-off Alpharev * Clockwork 2.5.0.7 * HBOOT 0.93.0001 *
Was on Teppic's rom with init.d support http://forum.xda-developers.com/showthread.php?t=773997
Any help would be very much appriciated.
I hope I haven't missed an obvious or relavent thread.
EDIT
Tried sdcard from Nokia6500 but Desire won't mount that either.
When I go into fastboot and plug in my usb, I do get "FASTBOOT USB" come up, so why would cmd "fastboot devices" not detect my phone? In recovery, cmd "adb devices" it does detect it.

I don't mean to be a pest but i doubt any of us can live without our desire's
BUMP

I have the same problem when i make ext etc. for me helps putting card into another phone with android and format it
Sent from my HTC Desire using XDA App

I have no other android device but...
I have managed to get fastboot cmd's to recognise my device.
Just need to figure how to flash my phone but I dont really want to take any backwards steps in terms of flashing a recovery.
Would like to flash my last set-up if it is possible.
Wish me luck lol
EDIT
Sorted....ish
Long short cut short is:
sdcard reader, reformatted to all fat32 with Paragon hard disc manager 8.
copied rom zip to sd.
full wipe with clockwork recovery.
Then inserted sd and installed zip from sdcard.
booted.
smiled again, even though its a practically stock rom.

ok i just waited and it finally booted up normally and went under sdcard and erased all that data this removes the partitions

[Q] i9000 - internal sdcard gone - problems with boot / external sdcard mounting

Hi,
I have an i9000 and unfortunately, the internal sdcard is not recognised at all.
I can only boot using voodoo 500hz kernel, to bypass this problem.
All other kernels will fail at boot screen (reboot loop).
After booting with voodoo kernel, I've rooted the phone and connected through ssh to it (adb shell)
Listing devices in /dev/block showing nothing like mmcblk (/dev/block/mmcblk0)
I thought it must be the card itself or the controller so I went and bought an external sd card (8gb).
After I insert it, the phone shows it has 0 (zero) capacity , tried to format it to fat32, ext2, etc, both on device (parted) and computer (windows, linux). Not a chance. Tested it using a i9100 I also own and the card was recognised correctly.
Next step was to check if the controller still works so again adb shell and checked for a mmcblk device in /dev/block.
This time, a /dev/block/mmcblk0 and /dev/block/mmcblk0p1 / /dev/block/mmcblk0p2 were listed.
Removed the external card, no device at all so the internal sd card is gone for good.
Next step was to use a hack to swap the internal/external sd cards in (/etc/vold.fstab), but even it is recognized in recovery mode (I can factory format/ wipe data), still 0 size in android interface and I can't use Camera and other apps.
I tried to mount it manually, directly on phone (adb shell), with mount comand and it works! I can create files on it, which are persistent.
So the controller actually works and the card is recognised low level.
BUT, why Android interface (java layer) won't recognize it? It says it's there but size is 0.
Please help, I can't use a lot of features on the phone, I don't know what to do.
Tried to mount it manually (to /mnt/sdcard), and even it get mounted and everything works on shell (creating files, etc), still 0 size in Android.
Running df in shell shows the correct size.
Checked the fstab / vold.fstab / vold.conf , everything seems to be ok.
Can anyone help me to fix this issue? Or at least, to give me some clues / ideas? I've lost several nights and I can't find a fix.
I'm good at linux but don't know very much about Android and it's java layer over linux.

It happenned to me too... not sure it can help you, but this is how i fixed my problem:
1. connect i9000 to the pc thru usb.
2. found a filename "no media" in the root directory.
3. erase the "no media' filename and everything is back to normal.

Did you fix it? I have the same problem and can't find a solution yet

[Q] unable to mount USB storage with CWM

I trying to flash new ROM
PC is able to use fastboot utilities ok but just wont detect it as a removable storage device so i cant load any ROMS onto the SD
i try to mount USB with CWM and it gives the error E:Unable to write to ums lunfile (No such file or directory)
if i let the phone try to boot normaly i get about 10 seconds of home screen and it reboots and cycle continues.
but while phone is connected and running home screen i get a new CD drive which i cant access and also device manager reports HTC with drivers required.
problem is HTC dont have drivers and phone re boots within 10 or so seconds and when it does the device vanishes
ive read through all the threads with similar issues but none have solved my problem.
my phone is bricked until i solve this and im freaking out cause its only 5 days old.
ive been reading forum for past 2 days and nothing has helped me

USB mount has never worked on CWM for our device (Snapdragon S4 version of the One X). Its a known issue.
CWM doesn't really support our device, its just a port. And it has huge issues (USB mount being just one of them) because of that. You can install a custom recovery that actually supports our device, TWRP. Head over to the Development forum and find the TWRP thread, and it should tell you how to flash TWRP over adb.
Most (if not all) of our devs recommend being on TWRP.

I am not able to mount sd card from cwm
can't partition non -vfat error

[Q] Internal storage no longer available!

Hi guys, I've got a little bit of a problem here, I can no longer acces the internal storage of my tf700, except through Root Explorer...
It is rooted but still locked. When I type "df" in Terminal, it says Permission Denied, next to storage/sdcard0. Does anyone have an idea on how to fix this?
Please help me
Edit:
Just tried to do a factory restore, but still no luck :/

Recently, /sdcard has been giving me a headache -- I can no longer mount it in CWM. In the ROM itself, I can access it with any file explorer without any problems whatsoever. I wonder if something has changed.
Which version of stock are you on currently? The .25?

storage issues
Tried to install a new app from Play store an got a insufficient storage available error
thats on a tf00t 32g with class 10 micro-SD 32g
runing CROMI 3.2
any help would be appreciated.

Might be worth giving this a try?
Boot into recovery, plug in the USB cable, go into adb shell, make sure that /data is mounted, then:
cd /data/media
chown -R media_rw.media_rw *

Problems with TWRP Backup - unable to mount sd/ext

I've been searching both this forum and the net generally and not found an answer to my specific problem so I'm hoping someone can help.
I'm trying to swap out my ROM, I'm currently running CM 11 nightly but I'm getting endless FCs with apps so thought I'd try something different.
When I try to run the nandroid backup with TWRP v2.7.0.1 the backup fails every time with the error E: unable to mount '/sd-ext'
Can anyone advise? Thanks

tht looks like external sd card.
Try changing location for your backup to internal memory or make sure you got SD card plugged in to SD slot.
you may also try command on terminal emulator (or via adb shell):
ln -s /storage/emulated/0/ /sd-ext/
it will create symbolic link named sd-ext in root of your system and it will point to internal storage (if I am not mistaken, from now on it should not matter if you select internal or external storage as target for your backup - it will end up as internal anyways)
Sent from my TF300T using XDA Free mobile app

Thanks, the backup was to be created on the internal SD card, but you are right it is almost certainly a problem with the external card. I'm unable to mount either the dock SD or micro SD cards in TWRP - the options are just greyed out and can't be selected.
I can't get either card to mount when I boot to system ether I have noticed. I've tried formatting them as FAT32, EXFAT and NTFS and no dice so I'm wondering if this is a KK issue - they both worked flawlessly when I was running PA and Omnirom JB ROMs.
I've managed to find a workaround - I've flashed CWM and have been able to do a nandroid backup with that - but I still can't mount either the micro SD or dock SD cards with CWM or in system when I flashed KatKISS ROM - and of course now I can't use any old TWRP nandroids I have from JB ROMs without reflashing TWRP. I'd also rather be running TWRP ultimately if I can so it would be good to get to the bottom of what is causing this issue.
Not quite sure what the command line you suggested does, but I'm guessing it won't be useful with the problem as it stands now?

sorry for late reply as I was out of internet lately.
that command creates /sd-ext/ folder that acts similar to shortcut to intertnal sdcard
any call for /sd-ext (for example: cd /sd-ext) will end up on internal sdcard.
That wont help with accessing your external sdcard (as this was main issue here) - it would merely fool installer to 'think' it is working on external sd while it was still on internal.
Sent from my TF300T using XDA Free mobile app

Thanks for your help. I've had endless troubles which ultimately ended in a hard brick during a failed flash of the stock ROM. I'm waiting for a replacement motherboard - something wasn't right with the old board anyway, it doesn't seem that it was just ROM issue. Hopefully when it comes I'll find that it wasn't a hardware issue associated with the SD cards as well.