I've tried searching the forums but haven't been able to find any answers to my problem.
I'm currently running a MT3G with Super D 1.9.2 so I figured I would post in the G1 Q&A since this is a 32B phone and might be more receptive to a better answer. Anyway...
So for a few months since I've flashed many different custom roms, I've had an issue with USB mounting. The SD card will correctly mount to my PC and my PC can view the files on the microSD card. BUT, whenever I try and copy a file to my SD card, my file explorer freezes and my phone starts lagging like crazy and I have to pull the battery.
I've tried doing this on 2 other PCs with 2 different Operating Systems on them but they do the exact same thing. I've also tried a different microSD card but it does the same thing...
Is this a known issue with ROMs? Or is there something I may be overlooking?
It would be nice to fix this issue because it's just a nuisance. It's not the end of the world if I don't get it fixed as I can use my SD card reader, but it would be more convenient if I found a solution.
Any help is appreciated.
I have never had a problem with it. Don't rule out the possibility of a hardware failure.
Did you ever try to let the phone do its thing or does it just lockup for a long period of time?
I almost always use adb to push files instead of mounting, give that a shot. There are a ton of guides that tell you how to set it up, an easy google search guide you.
Yes, I have tried letting the phone do its thing, its very slow but I *could* shut it off that way if I wanted, but the lag persists.
I have been messing around with adb pushing system files, I will try and push files to the sdcard. I found the topic in the sticky showing how to do this.
Also, it might be worth noting that the same behavior happens when trying to mount from Amon_RA's recovery.
Thanks.
Try formatting the card again from the recovery, or whatever way you wanted. But if it keeps happening on the stock firmware, different roms, different cards, it sounds like hardware failure.
Related
Well I've been around the net lately especially here, and have been noticing a number of people Not being able to Root there phone because of something thats sound simple but in the end is actually pretty Complicated. I myself have encountered this problem when attempting to Re-Root my G1.
Heres an example of whats going on in two diffrent ways, there still might be more I'm unaware, but this is mainly what I'm Seeing.
1 Reason
User attempts to Format G1 via USB
When attempting to do so computer fails at this process because the G1
ejects itself for no reason at all. And when putting the sd card back G1 doesnt accept it so it prompts you to reformart it, which by the way doesn't work because if you put the DREAIMG.nbh on the card after formatting it from the phone,it repeats the above.
2nd Reason
User is able to format card sucssesfully
And user is able to put DREAIMG.nbh on card but, when attempting to downgrade to RC9/RC7 from the bootloader menu it flashes the message
"No image file" (In green text or not pressing the Send key to enter fastboot wont work)
And to top it off, (Goldcard, Rogers, Another SD Card and XP Machine options do not work(Well for me they dont)
So XDA Community, I am asking (and so are many others) is this a Phone Problem
A Card Problem or did Google finally "blacklist" the DREAIMG.nbh file, so you cant downgrade to RC9/RC7
And if not please solve What the Muck is going on here!!!.
It sounds like a card problem. You are still able to downgrade to rc29 or rc7.
sd card
I had the same problem, it was my sd card. I think caused by not using the HTC usb cable. I believe it corupted my card.
Okay so here's the run down:
I've been having this problem with my G1 for awhile now, I've been connecting it to my computer, selecting Mount and it all works like normal. I go to my computer -> "Andrizzle" and then I can see all the folders. It's only when I attempt to modify anything in the SD Card that it will then disconnect and my phone acts like I chose to disconnect, allowing me to select mount again.
It's really annoying because now I have to take the SD card out, put it in a SD reader and then do it from there. Although it's not a HUGE hassle, it's still an unnecessary step that I'd like to solve. I've been trying to find a problem similar to this and couldn't find the right way to word it, nor could I find anyone with this issue in a thread. If someone has already solved this problem please direct me to it, otherwise I'm here anxiously awaiting some divine intervention!
instead of divine intervention, you get me, sorry life's a *****
This kept happening to me also, but my problem was on ubuntu, It was kicking me off because it was mistaken my phone for my ipod, I flashed a different rom and rebooted my computer and that did the trick for me, but you have prob already tried this......right?
i was going thru this ealier today. jus to to recovery and fix the file systems option will fix it believe it or not
So wait how exactly do I do that?
I know how to get to the recovery mode but there's a setting I need to change?
Nevermind.
That didn't solve it either
Bump?
Any help from anyone? This is a seriously annoying issue to have
What ROM are you using? What OS?
Give a little more details on your setup
I had the same problem today
I just powered down, then removed the sdcard and put it back in then rebooted. Then it was just fine. My guess is the contacts were just miss aligned.
I was on the Cyanogen STABLE 4.0.4 but am now currently on the Experimental version.
I have USB Debugging on and i've tried other SD cards. I don't know what the problem is. Any other information you need? I really want this to be fixed it's very annoying when I'm trying to do anything
i actually cannot remember the last time i tried to mount my sdcard while my phone was up and running (i.e. not in recovery), i always use adb bc it makes life better.
try to mount it in recovery with ums_enable and ums_disable to mount and unmount the sdcard respectively. if those work then it may be something that will not allow the phone to mount the sdcard when it is fully powered up (i.e. not in recovery).
i use to get a problem where it would mount then quickly unmount the sdcard. i usually just had to either try it a lot, or use my card reader.
I tried going into recovery and doing so,
it still didn't transfer the file.
I can see it in the Explorer, I can browse all the folders and such, look at pictures / videos / music but when I try to move anything around or transfer a file over it stops running.
Any ideas?
First: I'm not a noob. I don't need noob-like advise. I'm not asking a question here, just frustrated with my Hero right now.
I have Fresh 2.1.2. It's awesome. I recently encountered an error and I don't think it's any inherent fault of the ROM. I think there might be an issue with either the SD card or the way the phone interacts with it. This is not a physical problem, intuition and savvy tell me that it's a software issue.
There are two (likely related) problems:
PROBLEM 1: At some point, shortly after flashing Fresh 2.1.2 (not toast) My phone became unable to "find" mp3's and images on my memory card. I've tried lots of things. A complete reformatting of the SD card, reflashing the rom, reflashing again from stock, different music and gallery apps. Nothing works. Everywhere I go I'm given, and I hear, noobish advise like "eject and remount the card", "put your music in the /sdcard/Music directory" etc. Of course those were the first things I tried before even asking for help. [Reminder: I'm not asking for help in this thread.] Once in a random while the vanilla music app will scan for music and either finds none or hangs forever. Other music apps won't even try. For the record I have tried--
HTC music app
Vanilla (Android 2.1) Music App
Mixzing
TuneWiki
Meridian
DoubleTwist (released this week)
Results are the same across the board. I have also deleted all music and image folders and files. Then adding them back after a few reboots one by one with different music files. I CAN play music by selecting the files from a file browser like ES File Explorer and Astro.
PROBLEM 2: The Sd card no longer mounts. i get no USB debugging icon in the notification bar and it will only charge. I don't get a choice of mount options--nothing. But it does charge. Because of this I can no longer ADB. All apps can still see and use the SD card as storage and A2SD is also working as advertised. I tried backing up only the most important files then putting them back after a clean wipe and repartition of the SD card.
PROBLEM 3: I'm getting a lot of silly advise. I wouldn't be on xda if I needed simple-ass advise.
Hope I'm not offending anyone but I know this type of thing happens to most of us when we need help with a real issue.
/rant
scirio said:
First: I'm not a noob. I don't need noob-like advise. I'm not asking a question here, just frustrated with my Hero right now.
Click to expand...
Click to collapse
Perfectly understandable. I have my own set of rants about 2.1, so I understand.
PROBLEM 2: The Sd card no longer mounts. i get no USB debugging icon in the notification bar and it will only charge. I don't get a choice of mount options--nothing. But it does charge. Because of this I can no longer ADB. All apps can still see and use the SD card as storage and A2SD is also working as advertised. I tried backing up only the most important files then putting them back after a clean wipe and repartition of the SD card.
Click to expand...
Click to collapse
I isolated this issue because this also happened to me. I was showing a friend of mine (who also owns a Hero) all the things I have done with A2SD. He liked the boot animation of Fresh 2.1.2, so I put that on his phone (his runs Fresh 1.1). After I searched his phone for the boot animation files, I disconnected his phone from ADB and put mine, only to find out ADB wasn't working. Thought this may have been the switching of the phone, so I killed the adb server and restarted it. No luck. I rebooted the phone...no luck. Checked to see if USB Debugging was on, and it was. I turned the debugging off, then on again to see if maybe it's a setting issue...no such luck on the fix.
Ended up reflashing the rom again to fix it.
Have you tried rebooting your phone?
Sounds like you need to try a different SD card buddy. If that does'nt work then try a different Rom, if that does'nt work then nandroid back to a 1.5 or ruu to 1.5 and start over.
Your problems are there because you allow them to be there. If and when you RUU and repeat the root process once more essentially making your Hero a "Virgin" again you should be able to fix above stated issue and be on your way.
If none of these work, then your answers are not in XDA, but on the phone with sprint's insurance department.
have a great day.
tkirton said:
Perfectly understandable. I have my own set of rants about 2.1, so I understand.
I isolated this issue because this also happened to me. ...
Ended up reflashing the rom again to fix it.
Click to expand...
Click to collapse
I had already tried that, didn't work.
doojer said:
Have you tried rebooting your phone?
Click to expand...
Click to collapse
this guy.
So my phone got stuck at boot screen. Bell says I get full replacement, but I'm gonna lose all the data. I have the internal full of children opening gifts on Christmas.
Reading a million forums. Tried to learn enough to flash the firmware with odin. Tried flashing the stock JH2 back to phone. Phone boots to recovery and says problem mounting SD.
Can ADB be used to connect to phone in "Download mode" to Pull the media???
PLEASE PLEASE help?????
after odin is done the phone reboots to:
E:Can't mount /dev/block/mmcblk0p1
(no such file or derectory)
E:copy_dbdata_media: Can't mount SDCARD:\copy default media content failed
I'm still desperately trying to get my files. I've read about 1254 more threads. Found this one about flashing back to eclair...
http://forum.xda-developers.com/showthread.php?t=797302
So far I tried JH2, JL2, JM8 and still no luck. Anybody out there got any ideas?? links to help or compassionate remarks?
Phone no boot need remove files inside...is this really an impossibility??
Argh.... it never happens when the internal has useless data aye.
You tried flashing a firmware using all three files (PDA, modem, CSC) with repartition?
P.s. apologies if you have tried all this, just trying to establish a baseline
Sent from my GT-I9000 using XDA App
From what i understand the internal SD card has 2 main partitions. One that's about 2 gigs for Android OS and apps and the remainder of the card stores media and such. (I think that's correct) So I've tried carefully to just poke around the OS area of the SD card in hopes that I can get it to boot up just once to connect and get the pictures off it. I'm fairly sure that "re-partition" would erase the whole card.
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Hoodmin said:
From what i understand the internal SD card has 2 main partitions. One that's about 2 gigs for Android OS and apps and the remainder of the card stores media and such. (I think that's correct) So I've tried carefully to just poke around the OS area of the SD card in hopes that I can get it to boot up just once to connect and get the pictures off it. I'm fairly sure that "re-partition" would erase the whole card.
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Click to expand...
Click to collapse
Repartition only erases the 2GB portion, ive done several repartitions and it never touched my personal files on the internal SD
Hoodmin said:
I'm starting to consider ripping this damn phone apart and physically removing the internal SD, but I'm not even sure if that is possible or helpful.
Click to expand...
Click to collapse
That won't work...the 'internal SD' is not a SD card in the traditional sense (standard, mini, micro) - it's a physical chip (IC) that's soldered on to the mainboard.
I haven't heard of anyone being able to pull data off a phone that's got the mmcblk0p1 failure. The best I've heard is of people repartitioning/formating the sd memory in order to get it working again - but of course, that would mean losing all data...sorry...
As what EarlZ said, repartition won't touch the part of the SD dedicated to user data. I've flashed via Odin countless of times and never once did my internal SD get wiped with a repartition so why not flash to something like JPU with repartition using 512 pit file?.
Edit: and reading the error seems to tell me it's a problem in the 2GB portion of the internal SD where the system and such get stored. So yes, do try a repartition. I guarantee you that your user data will be safe. The only time it would get wiped is if you actually choose to format that partition like how one does in Windows or through the settings. Odin flash won't do this most definitely.
If that fails...
Also take a look at this...
This guy seemed to have been lucky and got is supposed dead I9000m SGS working again. Here's his procedure:
http://forum.xda-developers.com/showthread.php?t=905975
Worth a shot.
Well hot damn them are some good replies. I was brave enough to try re-partition and a few mod roms like in the thread mention as well as a few thread techniques I read. I must have read about 4622 threads by now. Still no luck for me I really really appreciate the help.
Thinkin I might just go wrap up the kids christmas presents tonight while they sleep and just make em open them all again hahaha.
In the mean time I'll just keep readin and keep tryin. Learned a lot at least.
So....
Original problem = boot cycle
-I flash back to JH2 and at least to phone gets to recovery mode and i see the mmcblk0p1 error. progress
-try flashing to the newer JL2 and it goes back to boot cycle
-try flashing back to JH2 to get recover mode again and still boot cycle
-read a million forums about trying mod roms and other techniques and still boot cycle
-get encouraged that re-partition will only affect OS side of SD card and try a million things again. Still boot cycle
-decide to go back to the JK4 that i started on and seems to be the root of all evil and then BAM recovery mode returns and this time it even recognized the device
-any attempt to connect with device either with kies or windows explorer causes PC crash
-phone even recognized by ADB I "think" this program could be used to try and "pull" media from the device but that's just a guess and I don't know how to use it
-the error now is not mmcblk0p1 instead: E:Can't/b mount /devlock/stl10 which could mean something or could be just the same and it leads me to this thread: http://forum.xda-developers.com/showthread.php?t=788850
-try flash techniques in the thread and back to boot cycle
-try going back to the JK4 so I have recovery mode again and still boot cycle. progress gone
I'm gonna flash this damn thing again and again until the damn copper lights on fire
Wow i Admire you man.Listen i dont know much about ADB but i think i saw a post of someone that literally pushed files in his internal card with it,and i clearly remember him saying he could browse through his phone although its card was burned.If so then a single copy would be possible.Since i cant help more,you better start reading on how to use it and find basic commands for it.
I wish you the best man!!!!
Have you tried this kernel: http://forum.xda-developers.com/showthread.php?t=901772
I seem to be able to get that running on my dead GT-i9000M. It has a file browser so maybe you can see if your pictures are even there/accessible. Also has a USB Mass Storage option but it didn't seem to work for me.
However, phone is still dead and needs to go in for repairs/replacement.
OK so now I'm f&*#ed
Tried JP1 method from this stupid page
http://briefmobile.com/how-to-android-2-2-on-galaxy-s
and now I don't have download mode anymore.
somebody plz just shoot me
EDIT: Ok excuse this panic post. I still had connection to ADB and a simple "adb reboot download" command got me back.
Wow thank JDROM. This recovery mode really looks promising. I got the file manager working but I can't seem to find any directories with DCIM/ label or any media. Sure looks like this could help me somehow. Might only have half the SD mounted or something. I'll have to play around and read some more, but I gotta say this is the best progress I made in a while.
THanks SO much
Edit: Found in File manager to run partition manager and formating options show up. In here there is mounting options to /mnt/sdcard or /mnt/external_sd except when I try it returns the E:Can't mount /dev/block/mmcblk0p1 to /mnt/sdcard with parameters vfat(null) So hmmmm....
Edit: Also learned a bit more about ADB commands to possibly ""Adb pull /sdcard/DCIM"" if I ever get it mounted.
Well that's it for me. The quest is over. I admit defeat. Memories Lost. Game Over
That sucks man...i had a bunch of stuff on my phone that i lost when the internal died....mine took out the external sdcard i had in it too - so all my backups were destroyed as well!
Moral of story: Save important crap on something like dropbox!
Some dev should make a program that automatically syncs certain directories (like pictures, or backup folders) to dropbox. I'd donate for that.....
I have a problem and found this unanswered question in the internet:
Hello,
so I have a rather big problem here. My internal SD-card on my I9000 does not accept any changes(delete/write/move).
The funny thing is that I can actually copy files to my sd and delete files. I can even format it(from recovery mode, windows, menu) whatever I do seems to work till I reboot. After every reboot my system is back to the state before I changed anything.
I tried everyway I could think of. Changing permissins via adb shell, installing file system fixes via adb push(to my surprise it did allow me to copy files directly into /system as long as I did it while in recovery mode).
I even tried several different firmwares. No matter what I do it's the same, no changes are permanent. As soon as I reboot every change is gone.
This feels like working with oracle and forgetting to commit.
Is there a way to format the sd card via adb shell? Preferably a low level format(since the quick format doesn't seem to do anything). Or some sort of forced flush for the sd card? Some way to just clear my internal sd should do the trick.
Every solution I found on the internet didn't work.
What does work is the download mode, the recovery mode and adb.
I sure hope someone has an idea. It's rather unpleasent being unable to change anything on the internal sd.
My problem is exactly the one stated above, and I have tried pretty much everything I found in the internet, including running Ubuntu live cd and format/partition/etc, but the problem persists.
I need one of 3 possibilities:
1 - Someone tell me what is wrong and how to fix
2 - Since Internal SD is unchangeable, would like to know how to make /data and /sdcard to be mounted on external sd at boot time (probably some changes at firmware or kernel).
3 - Someone tell me that it is broken and cannot be repaired by software, must be hardware serviced.
Really thanks in advance
Same problem!
i do have the EXACT same Problem!!!! Any solution jet?
Got a similar problem with my Galaxy Tab... Anyone found a solution yet?
friend of mine has a htc and uses a program called superwipe
http://forum.xda-developers.com/showthread.php?t=834812
dont know if it will work on the galaxy s though, but coukd be worth a read through the notes and posts
Wow . I have a similar problem. Although EVEN more troublesome.
Inaddition to all this
I cannot even DELETE the alarms taht i set before having this problem. I cannot Install the apps as well.
Uninstalling the ones - and they reappear the next time I boot.
Need Serious HELP on this.
My phone is restricted to ONLY making calls and sms. Thats all.
I have the *EXACT* same issue here. Only with a Sprint Galaxy Tab. My reboot is fresh and gives me "nothing" every time I boot no matter how much I configure. I can't write anything to the internal SD card or make any new folders.
jrhsu529 said:
I have the *EXACT* same issue here. Only with a Sprint Galaxy Tab. My reboot is fresh and gives me "nothing" every time I boot no matter how much I configure. I can't write anything to the internal SD card or make any new folders.
Click to expand...
Click to collapse
I have a different problem. My internal sd seems slow. Anyway, I must feel lucky.
If you look at page 15 of the following datasheet, you will notice that the moviNAND can be set in a "write-protect" mode:
http://web3032.sh1.magic2008.cn.m1.magic2008.cn/uFile/3032/201144131545503.pdf
See if you can read the CSD register data on your phone, and mingle with it.
Good luck.
Any one fix this
Any one fix this I have the same problem
Yesterday I gave the soluction, but someone deleted my post.
EDIT!!
Sorry, I wrong topic!!!! Sorry!!!!
superandroid2011 said:
I have a problem and found this unanswered question in the internet:
Hello,
so I have a rather big problem here. My internal SD-card on my I9000 does not accept any changes(delete/write/move).
The funny thing is that I can actually copy files to my sd and delete files. I can even format it(from recovery mode, windows, menu) whatever I do seems to work till I reboot. After every reboot my system is back to the state before I changed anything.
I tried everyway I could think of. Changing permissins via adb shell, installing file system fixes via adb push(to my surprise it did allow me to copy files directly into /system as long as I did it while in recovery mode).
I even tried several different firmwares. No matter what I do it's the same, no changes are permanent. As soon as I reboot every change is gone.
This feels like working with oracle and forgetting to commit.
Is there a way to format the sd card via adb shell? Preferably a low level format(since the quick format doesn't seem to do anything). Or some sort of forced flush for the sd card? Some way to just clear my internal sd should do the trick.
Every solution I found on the internet didn't work.
What does work is the download mode, the recovery mode and adb.
I sure hope someone has an idea. It's rather unpleasent being unable to change anything on the internal sd.
My problem is exactly the one stated above, and I have tried pretty much everything I found in the internet, including running Ubuntu live cd and format/partition/etc, but the problem persists.
I need one of 3 possibilities:
1 - Someone tell me what is wrong and how to fix
2 - Since Internal SD is unchangeable, would like to know how to make /data and /sdcard to be mounted on external sd at boot time (probably some changes at firmware or kernel).
3 - Someone tell me that it is broken and cannot be repaired by software, must be hardware serviced.
Really thanks in advance
Click to expand...
Click to collapse
Looks like my problem as well
http://forum.xda-developers.com/showthread.php?t=2155644
To test quick go development->>launch tools->>bad behavior->>crash the system server.
Your device will reboot and you will have both in/ext sdcard (if its the same prob).
damgood said:
Looks like my problem as well
http://forum.xda-developers.com/showthread.php?t=2155644
To test quick go development->>launch tools->>bad behavior->>crash the system server.
Your device will reboot and you will have both in/ext sdcard (if its the same prob).
Click to expand...
Click to collapse
I have the same problem, cannot even use the phone as it FC any apps after boot. And no changes possible to the sdcard.
Have you found a solution yet?
DerBusisVoll said:
I have the same problem, cannot even use the phone as it FC any apps after boot. And no changes possible to the sdcard.
Have you found a solution yet?
Click to expand...
Click to collapse
Sorry - no - I had to start from scratch, my thougt was too many files on the ext card But I not sure and cannot recall - My phone is working good now. Only advice is to reinstall from scratch
I am also facing the same problem on my galaxy nexus after upgrading to KK using custom ROM. Any solution?
Does anybosy able to doanload the superwipe?
superandroid2011 said:
I have a problem and found this unanswered question in the internet:
Hello,
so I have a rather big problem here. My internal SD-card on my I9000 does not accept any changes(delete/write/move).
The funny thing is that I can actually copy files to my sd and delete files. I can even format it(from recovery mode, windows, menu) whatever I do seems to work till I reboot. After every reboot my system is back to the state before I changed anything.
I tried everyway I could think of. Changing permissins via adb shell, installing file system fixes via adb push(to my surprise it did allow me to copy files directly into /system as long as I did it while in recovery mode).
I even tried several different firmwares. No matter what I do it's the same, no changes are permanent. As soon as I reboot every change is gone.
This feels like working with oracle and forgetting to commit.
Is there a way to format the sd card via adb shell? Preferably a low level format(since the quick format doesn't seem to do anything). Or some sort of forced flush for the sd card? Some way to just clear my internal sd should do the trick.
Every solution I found on the internet didn't work.
What does work is the download mode, the recovery mode and adb.
I sure hope someone has an idea. It's rather unpleasent being unable to change anything on the internal sd.
My problem is exactly the one stated above, and I have tried pretty much everything I found in the internet, including running Ubuntu live cd and format/partition/etc, but the problem persists.
I need one of 3 possibilities:
1 - Someone tell me what is wrong and how to fix
2 - Since Internal SD is unchangeable, would like to know how to make /data and /sdcard to be mounted on external sd at boot time (probably some changes at firmware or kernel).
3 - Someone tell me that it is broken and cannot be repaired by software, must be hardware serviced.
Really thanks in advance
Click to expand...
Click to collapse
Galaxy Tab 2 running on blisspop rom
I have to reboot every time this happens. The error message in mx player shows cannot write to internal sd..
Es xplorer cannot delete any item. Terminal emulator shows mount as read only
Any way to fix this?