• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help SD card won't mount

chefant

Lurker
My computer recognizes my phone as the f drive, but it doesn't recognize my sd card as a separate drive. Anybody know what happened? is it the new update?
 
My computer recognizes my phone as the f drive, but it doesn't recognize my sd card as a separate drive. Anybody know what happened? is it the new update?
You need to give us more detailed info like what configuration you have in terms of rom etc. Also do you have usb debugging on? Settings>Applications>Development
 
You need to download verizon's media manager in order to access the SD drive when connected through the phone. Good luck getting it to work correctly or reconizing the phone. Im running 64 bit Windows 7 and it gives me a read error every time I want to move content around. And if your running mac, it doesnt work at ALL.
 
Well to begin I am guessing the data in SDCard is intact and file allocation table is not corrupted and you can access it via console/explorer from your phone. So if you having problem it reading as USB disk drive then first uninstall and I mean completely remove all trace of the USB drive from hardware profile. Don't have the phone connected via USB yet, make sure your connection is set to USB Disk Drive in phone and SDCard is mounted. Just to make sure after that restart your phone and then connected it to PC via USB. When it happens your PC will scan it as new hardware as you removed it before and install the drivers and give you local mount to access it from your computer.

I mean look at the bright side at least you are not having my phantom issue. I give up as being AOSP dev for 1month now as I uninstalled Android ADK and halted my own project till I get back.

I know thats why I said I know I seen that name before and same question. The problem you encountered was first documented by me on XDA MT4G as byproduct of testing faux's kernel.

I mean I downloaded the v0.2 kernel and after I successfully flashed it I was not able to boot as I was stuck in myTouch4G Logo. Now normally I don't back things up as I know what I am doing but in this case after the problems I urge and recommend everyone to do total backup specially using source from unknown developers.

So I took poll why I was the one having issue and found out few of us under curtain condition were having this issue while others are not. So I begin to investigate and try to count for all the variables. Thats how the whole BS started and thing got out of control lol

First I came across the CWM3.0.0.5(2.1.5.4) issue as it would not update from 2.1.5.2 so I manually flashed CWM3.0.0.0 via console and solved that problem, I was one step closer to creating the same condition. Then came the SDCard issue... man o man as I am writing this ill tell you below what I am doing but after the v0.2 kernel flash I reverted back to Gr8's v0.5 stock kernel and the SDCard would not get mounted due the permission base strcuture being read only thus not able to access it thought MT4G nor PC via USB mount. So I had to manually AGAIN try to change the permission base though console which didn't work as the fstab couldn't be written to nor permission was ever amended. But I used some brain and accessed the /mnt/sdcard(19gb) via console and CPed files to /data(1gb) and /dev(300mb). So after I transfer the data to those slice I took the SDCard out and put 2nd SDcard and transfer the files back till I did this 19times to match the 19gb.

After that once my data was secured I started the test as I have never encountered this type of problem before. So 2days passed and after about 50+ kernel and rom flash I could not produce the same variables so I gave up and uninstalled Android SDK and remove trace of every POS I could lol as I needed my phone back online as people would call me home and was like WTF happened why I am not picking up.

So today not following my better judgment I tried the v0.3 kernel :P and baaam I got passed myTouch4G logo but got stuck on bootsplash. As like I did before I did testing again and again with wipe cache/davlik with and without but yield no result. So I again reverted back to stock kernel and when I got back the SDCard went totally blank as this time it didn't turn /sdcard -ro.

So I am at the moment manually accessing the raw file allocation table so I can extract the data from my sdcard and reconstruct it from 3 images. Thats 19gb each, one from SDCard that it happend to, 2nd one the backup sdcard and 3rd is from the HD. Now you are asking if I have it 2 places why am I wasting time lol because I didn't originally back it up. So now I have to reconstruct 19gb from 58gb of data which will take about 1week to get back where I was.

So if anyone wasted time reading this even if you are developer like me do NOT do any testing or anything unless you backup your data or you would be like me as you would waste 1week just to get back where you originally started :P so pray for me 58gb of raw data to convert to 19gb actual.
 
I'm guessing you might have the same problem I am having. Look at the Properties of the indicated drive, is it showing up as a CD drive? A Google search will show that we are certainly not alone with this problem.

The card is ok, because file manager apps like Astro and Root Explorer can read the sd card contents, it just isn't available through Mass Storage Mode on your computer.

Unfortunately, I haven't been able to find a fix for my wife's Fascinate yet. I can tell you I just upgraded her Fascinate from the stock DI01 software to DL09 then to the DL30 leaked rom.
 
Couple long threads on this already. Eject the CD when it shows up on Windoze and then the mass storage (disk) device will show up. Or, if the installer runs and asks about loading the drivers, say "no" and the mass storage device will show up and then just mount it as usual via the phone. If you want to download the useless drivers, that's up to you.

larry
 
Back
Top Bottom