EDIT: Woops posted too fast without full title. Should be like, Device not reading SD card in various ways. Haha... man Im tired >.>
Hi guys,
So it seems I managed to screw something up regarding my SD card while I was messing around with my devices (MT3G 1.2). I figured maybe you can direct me to some things I haven't tried yet.
Here is all the available info:
When trying to access SD card in RA Recovery I get:
E: Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)
E: Can't mount SDCARD:
When booted into android, I constantly have "SD Card Removed" in my notifications and not amount of rebooting or reseating the sd card seems to change that.
If I slap the SD card in another device and mount the card on windows, it shows up seemingly alright there. I also tried simply formatting it fresh to FAT32 there and putting it back into my MT3G, but it didn't seem to make a difference.
After trying to format the card, I seem to get these files I haven't heard of before showing up on the card:
qxdm_20100531_060541_2.dm
qxdm_20100531_062913_1.dm
etc, etc... about 10 of them now.
I'm hoping that this is something I can reverse, and not some sort of really bad hardware or driver issue. Any hints or tips would be greatly appreciated. Thanks!
technogecko6 said:
EDIT: Woops posted too fast without full title. Should be like, Device not reading SD card in various ways. Haha... man Im tired >.>
Hi guys,
So it seems I managed to screw something up regarding my SD card while I was messing around with my devices (MT3G 1.2). I figured maybe you can direct me to some things I haven't tried yet.
Here is all the available info:
When trying to access SD card in RA Recovery I get:
E: Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)
E: Can't mount SDCARD:
When booted into android, I constantly have "SD Card Removed" in my notifications and not amount of rebooting or reseating the sd card seems to change that.
If I slap the SD card in another device and mount the card on windows, it shows up seemingly alright there. I also tried simply formatting it fresh to FAT32 there and putting it back into my MT3G, but it didn't seem to make a difference.
After trying to format the card, I seem to get these files I haven't heard of before showing up on the card:
qxdm_20100531_060541_2.dm
qxdm_20100531_062913_1.dm
etc, etc... about 10 of them now.
I'm hoping that this is something I can reverse, and not some sort of really bad hardware or driver issue. Any hints or tips would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
That's very odd. qXDm is a program used with CMDA phones to mod ESN's and program them.. Flip phones and such.. not meant for smart phones since we'd have no use for a tool of that nature.
If you're running RA 1.7 then I believe accessing the SD card is out of question anyhow because something is broken with that.. not sure what though but I can't use mine either.
If you can boot into android, try this:
open the dialer and dial
Code:
*#*#4636#*#*
DON'T press call, just wait a sec. - a menu should appear. Choose the first item (phone information, or similar), and scroll down - there should be a button there with something about qxdm on it. Possibly 'disable qxdm'. Try selecting that.
Tried that, but it had "Enable QDSM SD Log", not disable... tried it regardless but made no real change anyway. :/
Did you ever find a solution to this issue? I have the same problem - it occured durring a SAPPIMG.ZIP flashing of my phone - it seems that for some reason QXDM was turned on during this proccess.
Typically, the following fastboot command would turn QXDM SD logging off, but it does not work for me (I believe it may only be available in ENG SPLs).
Code:
fastboot oem enableqxdm 0
Related
First of all let me say hello to everyone as I am new to here and that if there is a thread about this please point me there as I have searched far and wide and tried everything imaginable and nothing helped whatso ever.
I recently got myself the HTC touch with these specs
sapphire pvt 32b ship s-on g
hboot-1.33.0006 (sapp10000)
cpld-10
radio-2.22.19.261
I tried a tutorial I had found on how to flash it (Sorry in my frustration I lost the link for it) everything went well I know I had to get a file manager to activate an apk program for it then type in a code...after that it prompted to restart which I did and now it wont go past the vodafone loading screen.
its not bricked as I can get to the hboot screen still and I can go to the other screen the black one where you can wipe the card/ use the update.zip etc.
I took the sd card out of my phone to put the files needed onto it as my phone couldn't be mounted anymore and now when I put it back in I get the
can't mount SD card error (cant mount /dev/block/mmcblk0p1 or /dev/block/mmcblk0) (no such file or directory)
so now it seems like I am royaly screwed here as my phone doesnt even read its own sd card...could I have accidently removed something from the SDcard which was needed for it to be recognized or is there a way to work around this
please can someone help me as I have been searching for a good 14 hours straight as I need my phone for work...
thanks in advance
Is the sdcard formatted as FAT32? Most come partitioned as FAT but all the tutorials say updating rom requires FAT32.
sorry I forgot to mention that yes it is formatted to FAT32, I did the format on the pc so I lost all the files that were on it, but as it is an sd card and not the internal memory it shouldn't have had any information on it required to mount it otherwise if I would get a new sd card it wouldn't work
the sd card that came with mine btw is an 8gb micro SD HC
I have a normal 2gb Micro SD but it doesn't read that one either.
so in otherwords I have just flashed my phone with the flashrec-20090815.apk which then asked to restart...I did that and then wiped before the backup, which should only mean I cannot go back to the stock settings unless some other dutch vodafone magic user would be so kind as to send me his nandroid backup
but other than that I would really like to figure out why my phone can't mount the SD card, either of them
EDIT: When I searched around the net about can't mount SD card error (cant mount /dev/block/mmcblk0p1 or /dev/block/mmcblk0) (no such file or directory)
I found that every other person that has this problem is a HTC dream user which makes me think I accidently got a Dream file flashed to my phone, yet wouldn't just the right sappimg.nbh be able to return things to normal? Or is this just wishful thinking...
Well second this story from me. I have the exact problem as you have. Hope someone will stumble upon this thread and give us guidance..
//N
well I don't know how much of a difference it makes but I just got both fastboot AND ADB to work, at first only fastboot worked for me, so now when I am in the recovery screen I can put adb commands in even though it is not started up fully (Cant get past loading screen yet)
hmm...latest update, I think I did something horribly wrong now...it no longer goes into the recovery-RAv1.2.1G screen (The black screen with green words) it now brings me to a different recovery screen, the one with the phone and the exclamation (!) mark
As long as you can go into fastbood hope is not lost.
Did you already do an SPL update? if yes you can just install any rom you want.
try to put an rom (lets say cyanogenmod) via microsd to usb adapter on the drive and call it update.zip.
Get this tools: http://www.megaupload.com/?d=EZU065GP
You need to install the USB driver for the phone if you not already have.
Connect the phone to the PC and boot you phone by holding "Back" and "On" into fastboot.
then run the "Boot Modified Recovery" script. Select "Apply sdcard:update.zip", make an wipe and the Phone start normally with the rom you selected.
It would be very helpful if you write would you already did to the phone.
ok, first things first...tired the program you sent me (Awesome by the way thanks) but the SPL I am using is a non engineerings spl meaning I cannot actually DO anything in fastboot
so without being able to start my phone up fully or use adb (I Lost that option once the recovery part disapeared for some reason) it would be great to know if I can still change the spl to an engineering one.
and now for a long list of what I did in the order I did it in so you can tell me just where I went wrong and tell me if I screwed up my phone completey or not (if not I have a special insurance on this that I pay extra for and might...JUST might cover this problem)
anyways.
At first I looked for a theme for the phone when realizing it wasn't going to be easy, I needed to flash them which is nothing I had done before (Should have realized then an there not to do it, knowing my luck)
anyways.
I turned on the usage of unkown applications and turned USB debugging on.
I put the flashrec-20090815.apk and recovery-RAv1.2.1G onto my sd card as told by the tutorial I downloaded linda file manager (Or something around those lines) to activate the flashrec thingy...followed by using the recovery thing and then it said it needed to be restarted.
I restarted it into the recovery like it told me to do, everything was going perfect.
This tutorial did not say to make a backup first so I never did (ARGH i hate that part the most) it told me to do a wipe, so I did...followed by sending the update.zip (This part confused me as they did not tell me to have the update.zip on it.
So I popped the sd card out (This may be where I went horribly wrong) put it into the SD card reader and put the update.zip rom on it I wanted to use.
Put the SD card back into my phone, and then it went wrong, I tried to run the update.zip and it said that it could not mount the sd card do to the dev/block thingy I posted above.
I have tried everything against that, I wiped the card...tried to format it through the phone (Same thing, could not mount) I formatted it on the pc to FAT32 (I made sure it was 32) and still, no matter what I do it wont mount...
strangely though someone suggested using the sappimg.nbh somewhere else, I got it...put it onto my SD card, started up hboot and it read it, tried to apply it but it said something about my CID or something being incorrect...but that DOES mean that the phone reads my SD cards (Since I have a 2gb sd and an 8gb sd HC (The one it came with)) and both of them work for doing that, but the sappimg part doesnt work.
after trying that sappimg.zip one though also with no good results, I tried to get back into the recovery part for the adb so that I could try something someone suggested about mounting the sd card image thingy through that...but when I booted up the recovery I got the normal android recovery (the one with only three choices and the phone with the exclamation mark) meaning I somehow lost my recovery RAv.......
so that is what has been done, please, please, please tell me I didnt horribly screw things up...if someone can help me I promise never to mess around with things I don't know about...
odanion said:
hmm...latest update, I think I did something horribly wrong now...it no longer goes into the recovery-RAv1.2.1G screen (The black screen with green words) it now brings me to a different recovery screen, the one with the phone and the exclamation (!) mark
Click to expand...
Click to collapse
I was wondering what happen when you press both Home and Power buttons at this moment. What the phone shows. Is there any menu we can use?
Is the ADB recognizes the phone in recovery mode in this moment?
I am also having similar problems with my sapphire. I can fastboot to recovery rom but cannot mount the SD card I can use adb
/dev/block/mmcblk0p1 no such file or directory when I try to access sdcard.
I have tried 4 different sd cards with different partitions on them but it will not read any of them.
I have tried to restore a nandroid backup by using adb push to put the img files in /sdcard. I assume it is just using the phone internal memory as the sdcard does not mount. I have used adb shell to flash_image the nandroid img files but it still does boot up succesfully. Just hangs at vodafone screen...
I used the root method at unlockr.com, and i have #root# access in the terminal emu app. When i get to the part at unlockr about flashing recovery, (thru terminal emulator) i get an error reading /sdcard/recovery-RA-heroc-v1.5.2.iso
I have RUU'd the phone at least 5 times... I have also tried using the cmd using the guide here, and get an error at basically the same spot.
my hero is 1.56.651.2. i have spent over 15 hours across 2 days searching forums and trying different methods, but i guess i must be doing something wrong.
btw.. the very first time i tried using the method from unlockr (root through cmd, flash recovery through terminal emu) it *almost* worked. It tried and got a ton of messages and an error regarding too little memory. after i looked it up and realized i could have just freed up memory in the PHONE(not sdcard) it was too late, i had already RUU'd again. It hasnt come close to flashing since, only the error reading message.
i get an error reading /sdcard/recovery-RA-heroc-v1.5.2.iso
Click to expand...
Click to collapse
this isn't your issue is it?
----------------------
settings>sd card and phone storeage>unmount sd card
settings>sd card and phone storeage>format sd card
do a RUU to go back to bone stock, same version you have
http://forum.xda-developers.com/showthread.php?t=608434
follow this
http://forum.xda-developers.com/showthread.php?t=583291
EDIT: and when it get to this part about "flash_image recovery recovery-RA-heroc-v1.5.2.img" give it an extra min after you hit enter and it "looks" like it's done before proceeding
let me know if you get stuck, i'll keep an eye on this thread also let me know at exactly which step "looks weird"
oops that was just a typo. I have been using .img for the file ext like you are supposed to. I have formatted the sd before trying, and the same error. The guide you pointed me to also did not work, I always get a flash error at (step 18). I have RUU'd at least 5 times to start over, and it didnt help any.
and about giving it an extra minute after the flash command, it instantly tells me
"error reading /sdcard/recovery-RA-heroc-v1.5.2.img"
so i cant really do that.
What should i do
I have ran into that same issue. I would guess you have upgraded the stock sd card. If you have, it is formated to fat32 not fat like the original. Try formating the card fat then try again. Good luck to you.
Dave
EDIT: I see you have formated the card. I believe the card has to be fat not fat 32 (someone correct me if im wrong). When I was rooting my phone I had same error til I formated it fat. May the force be with you.
What do you mean by upgraded the sd card? I didnt ever do that...at least not on purpose. So how would i check the format?
Put the card into a card reader in a pc, right click on drive and hit properties.
crap, i dont have a reader for this type of card. no way to do it through the phone?
and this problem couldnt be from anything else, could it?
cweezyf said:
crap, i dont have a reader for this type of card. no way to do it through the phone?
and this problem couldnt be from anything else, could it?
Click to expand...
Click to collapse
you can mount the card from the notifications bar when you plug your phone in usb. then just right click on the removable disk in my computer (mine's drive H: ) then click "properties"
it will bring up this window
if it says FAT32 then there's the (assumed) problem.
Okay!
it IS fat32.
cweezyf said:
Okay!
it IS fat32.
Click to expand...
Click to collapse
do you know how to format?
before you format be sure to save anything you have on your sd card that you want/need as it will erase everything.
1. move anything you like to save to your computer from your sd card
2. right click on the removable disk in my computer
3. click on "format"
4. in the little window that pops up chose "FAT" leave everything else alone
5. click start.
6. thats it!
damn its not working.
As soon as i click format it unmounts...any idea?
BTW thanks for the help
cweezyf said:
damn its not working.
As soon as i click format it unmounts...any idea?
BTW thanks for the help
Click to expand...
Click to collapse
i've never tried it that way, but you will probably have to go the card reader option, or use...
GParted
windows disk management
but those tools give you the power to seriously mess up your computer. so i recommend running these on someone's computer you don't like.
or the card reader option
You can format the card under "SDCard and Phone storage"
Just unmount then format.
Okay well modchipper said he had the same problem, and the sd has to be formatted to FAT,not Fat32.
Gparted and the other tool, how can they mess up my computer?
The format option in the phone formats to FAT32...
If you're not careful you can accidentally nuke your hard drive, instead of your sdcard.
Well i tried windows disk management and it didnt see the drive. Gives me a feeling that gparted wont work either. does anyone know for fact that sdcard format has to be FAT?
Well once again I'm at my mom's, and her USB ports are screwed up, so I couldn't tel you what mine is formatted as.
Well i have multiple SDCards, but the one that is currently in my phone is formatted in FAT32 & I believe that was the one I used to root & flash the recovery originally...
Well this just seems impossible it seems ive hit a wall...
Im trying to use Fresh pre kitchen, but that wont work either because i have windows 7.
The Fresh Pre-kitchen works fine on Win7.
Hey guys
This is my 3rd time rooting my phone and I keep getting the error
unable to mount to /dev/block/mmcblk1p1 when trying to run the update.
I can not even see my SD card inside android.
I have already reformatted my card to see if that would fix the problem.
Is there some mount command I can run from root to fix this issue?
Thanks!
fikal1 said:
Hey guys
This is my 3rd time rooting my phone and I keep getting the error
unable to mount to /dev/block/mmcblk1p1 when trying to run the update.
I can not even see my SD card inside android.
I have already reformatted my card to see if that would fix the problem.
Is there some mount command I can run from root to fix this issue?
Thanks!
Click to expand...
Click to collapse
This should go in Q&A, really, but here goes.
There are four possible causes:
1. SDcard failure (try another to eliminate this prob)
2. SDcard corruption (try another OS to format it, like an old smartphone or linux)
3. DI Software corruption (least likely, but can be eliminated by a bootloader PB31IMG.zip flash -- know that this fix would blank all your userdata, apps, settings, not stored outside of the 1gb nand&RAM).
4 DI Hardware failure (this possiblity is why I hated the rapid sdcard eject/insert method--that sdcard lock mechanism is just a itty bit of spring steel and an itty bitty little latch) -- how to eliminate? try the card in a card reader or device.
Good luck!
what was the file system type that you partition the card to?
Its fat32, and thats what I reformatted it to also.
I've been using android on my phone for awhile, and tried a bunch of different builds and never got this error. Yesterday when i was switching back to shubcraft all of the sudden the boot loader gives me
mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount sd card. cannot continue.
/bin/sh: cant't access tty; job control turned off
i tried loading just about ever build and get the same thing.
I've changed the startup.txt and i always reformat before i switch builds. i was thinking it might be the sd card itself, but it works fine in winmo.
if anyone can help me it would be much appreciated, im having android withdrawls...
oh and its the stock 16gb class 2
EDIT: It randomly started working again...strange...
This Is What I Do
I was getting either the same thing or something very close to it on about 2 rom to the best of my understanding is when your trying to flash (for lack of better words) a new rom you still have some left over traces either on your storage card or the phone so what you need to do is format your SD card and reflash your phones rom.
I took the origin file put it on my sd card unzipped it there went into the android rom folder cut the plain android folder paste it withe the other folders then reased every folder EXCEPT the PLAIN ANDROID FOLDER now put the sd card in the phone enable the the sound then install android.
To be able to watch the process after you flash your rom go to settings, system, power (battery) and uncheck everything so it doesn't sleep. when you install now you will see the progress and will be able to read the progress if you see 2 things have failed
This is my process and it hasn't failed yet when I didn't do it this way I had fails.
Striving said:
I was getting either the same thing or something very close to it on about 2 rom to the best of my understanding is when your trying to flash (for lack of better words) a new rom you still have some left over traces either on your storage card or the phone so what you need to do is format your SD card and reflash your phones rom.
I took the origin file put it on my sd card unzipped it there went into the android rom folder cut the plain android folder paste it withe the other folders then reased every folder EXCEPT the PLAIN ANDROID FOLDER now put the sd card in the phone enable the the sound then install android.
To be able to watch the process after you flash your rom go to settings, system, power (battery) and uncheck everything so it doesn't sleep. when you install now you will see the progress and will be able to read the progress if you see 2 things have failed
This is my process and it hasn't failed yet when I didn't do it this way I had fails.
Click to expand...
Click to collapse
you can search a tool named SDFORMATER V2.0, it will be worked.
okay this is now happening to me as well!
had been using Android and various different builds without hitch.
but today after trying the Hyperdroid build the sd card fails to mount on startup.
Editing the startup.txt does nothing, have also flash to the latest chuckyrom and formatted the sd card time and time again and tried different builds.
anyone have any other suggestions?
Ta
working again now.
the fix for me was to reupload my backup to the sd, format then upload the required new build.
very odd...
snigs said:
working again now.
the fix for me was to reupload my backup to the sd, format then upload the required new build.
very odd...
Click to expand...
Click to collapse
odd indeed...for me i had to reformat my sd card using my phone, didnt really make any sense to me but it worked
After trying to do a root, following all the instructions on this site to a T, my phone booted up and presented me with a "SD card damaged, you may have to reformat" message.
I can click on it and hit reformat, but nothing happens.
I've tried doing the Odin recovery back to the stock /system, but that didn't seem to do anything. I've also booted into android recovery mode and tried wiping the cache partition, as well as doing factory reset.
HELP PLEASE!!!
UPDATE: the SD card is recognized when plugged into my computer via microSD adapter. Re-formatting on computer to the standard FAT32. will let you know how that goes, but still open to suggestions on assumption of failure.
Update 2: format failed. Popped it back into phone to try a last-ditch attempt at SOMETHING working.
It's still giving me an error message, though it's a different one;
Blank External SD card
SD card blank or has unsupported file system
Tried to format it on my phone, and it does nothing yet again.
how to proceed?
Raccio14 said:
Update 2: format failed. Popped it back into phone to try a last-ditch attempt at SOMETHING working.
It's still giving me an error message, though it's a different one;
Blank External SD card
SD card blank or has unsupported file system
Tried to format it on my phone, and it does nothing yet again.
how to proceed?
Click to expand...
Click to collapse
1. Post your questions in the GENERAL section.
2. Take what appears to be a faulty SD card back to VZW and get a new one.
3. ????????
4. Profit.
5. Post your questions in the GENERAL section.
Sent from my Fascinate using the XDA app
I have the same problem and did the same thing with my computer I think the sd is no longer good. I am using my sd card from my droid now and I now have a dead card too.
Sent from my SCH-I500 using Tapatalk
My Wildfire has now killed 4 SD cards. I think there is something seriously wrong with this phone.
This EXACT thing happened to my SD card, and while rooting, EXACTLY according to instructions.
I wound up just opening the automated Root batch file
and running the commands and pushing the files without the stupid automatic thing.
Something about the SD card mounting to the computer, and the computer rebooting while hanging onto a file for read/write.
I took it to Verizon and they replaced my SD card. It was even rooted, with Wireless Tether right on the home screen, LOL. Oh well.
Don't feel bad. The Samsung cards that came with the device are crap. Mine crapped out on day 2.
Call customer service and have them replace it.There's nothing you can do to fix it. Trust me, I tried...