Database Develop

Mounting the SD..... Disconnected?

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?

[solved] Card "Preparing SD card; Checking for errors"

Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again

Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.

I'm having the same problem How did you delete the fsck_msdos from the bin?

theinstagator said:
I'm having the same problem How did you delete the fsck_msdos from the bin?
Click to expand...
Click to collapse
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone

I was having this same issue..it would typically take up to 5 minutes or more to "check for errors" after a boot.
To fix this I backed up my sdcard, reformatted, copied everything back, then reflashed. Everything was fine after that.

i have somewhat the same problem but in my case it sometimes say blank sdcard or damged sd card it read fine when plugged into an sd card reader any help

Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.

hmaxos said:
Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.
Click to expand...
Click to collapse
Well, after getting other errors such as "no enough space" from Platinum Backup (there was a space on SD Card), I had to go to Format the SD after copying everything. Then I copied back the important folder the SD. I also had to reinstall SwiftKey. Now everything is fine and no data loss.

SD card Checking for errors
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Well I will try to backup and format it.... If it works then good if not then I will have to root my LG P880 .

My Problem is "preparing external sd card checking for errors" now that error is not showing while following above steps but now when i click my memory card that is not opening and after opened my memory card my internal device memory also not opening .

baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
Simple fix, Difficult decision. Remove SD Card from slot then Factory reset phone. Once it comes too just go through all steps to setting up device then reinsert the SD Card into the slot. BOOM!

thank you very very much it worked for me
baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
thank you so much but it is read only please help

yeah...
supremeteam256 said:
Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.
Click to expand...
Click to collapse
i am having same issue i always changes roms please can you halp me..

still not working mine is lenovo K3 Note And my Phone is rooted. It is showing Preparing SD card checking for errors

Didn't work for me.
Hard reset don't work.
Delete the fsck.msdos but don't work.
The fsck.msdos file comes on every wipe back.
I think this is a cm issue.
On stock no problems with my external sd card on my HTC One M8.
I'm going crazy...

No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,

Anitha Sivakumar said:
No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,
Click to expand...
Click to collapse
ive deleted the fcsk file on bin
the notif "preparing sd card" was gone but another problem occured, i cant even open my storage, ext sd card and even internal card ive tried your solution, ive put my sd card on another device, i cant find any fcsk files that you mention i cant even delete any file from my card using another mobile :crying::crying::crying:

It worked.... Thanks bro..
:good:
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse

sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Bloody Brilliant. I have no idea why I could not find this solution two years ago. I have spent several hours searching for this solution, several times. In my case, I needed to remove the fsck.exfat file in the /system/bin folder.
My attention span is extremely short. I have been living with a 3 to 4-minute card scan for a 256GB microSD in my Samsung Note 3 for two and a half years. For all of the reboots I have done (which must be near a thousand, if that's not severely underestimated) I have had to deal with waiting to use my phone. I can't tell you how discouraging it has been to have such a powerful, useful device crippled by such a stupid flaw: that of checking the SD card that you rarely remove, for errors, every single time the phone is rebooted, even after graceful reboots called by the "proper" methods.
I can't tell you how many times I have rebooted my phone, only to forget the reason I rebooted it, because my phone took 4 minutes to reboot.
Productivity to the cubed-root.​Pisses me off.
Someone who has more voice than me please get the Android People to change this. As of Nougat, this is still the default behavior. How can an organization be so stupid...? I have no doubt that just this flaw has sent many people to the Apple camps. Who the cuff in their right mind would want to deal with such a hassle?? Are they seriously unaware of the trend for people to actually believe that their devices, machines and technology ought to be doing things faster than previous generations?
(Please just take the following cynicism with a grain of salt. I just learned the above fix, something I really should have figured out a long time ago/kicking myself!!) :crying:
For the anally-inverted who might bring up the obvious argument that your phone will no longer be able to detect or fix corruption, all that needs to be done is the following:
1) move the fsck.exfat (or whatever the formatting) file to a different folder. In my case I moved it to the /data folder
2) use some delay scripting program that will symlink the fsck.exfat file to a tmpfs location say, 30 seconds after boot; or longer if needed. This intermediary step is necessary in order to create a temporary symlink, which will be nonexistent upon reboot.. If we didn't create a temporary symlink, the fsck.exfat command would be immediately available after each reboot (which we don't want) because symlinks are normally permanent. Therefore, this step will need to be run after every reboot (but again, time-delayed).
3) the last command is to create another symlink, linking the tmpfs fsck.exfat symlink created in the last step back to the /system/bin folder (or wherever it originally resided). So this is a symlink of another symlink. This step actually should only need to be done once, since this symlink should remain after reboot, even though it is initially broken upon reboot until the previous command recreates the intermediary symlink. It should become effective again when the previous step is run by the time-delayed scripting program.
Now your phone has the ability to check the card upon you calling the fsck.exfat routine through normal means, one of which can just be a simple unmount -> mount request from the Android system settings . Your card won't be needlessly fsck-checked to death every bloody time you reboot your phone.
(If you found this tutorial helpful and desire to quote or improve upon it, please cite/credit me for the inspiration! It came through much effort and learning!)

This is not a question. This is me venting.

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.

Internal SD card failing after 2.2 Rogers update?

Im having issues with the internal SD card after the update. So is Dennishwc
http://forum.xda-developers.com/showpost.php?p=10484065&postcount=1057
Via Windows 7 64 "Error 0x80070057:The parameter is incorrect 'for file copy and 'The file is too large for the destination file system' when I try to make a folders.
When I try to format in Windows, it shows capacity only as 2.19GB rather than 13gb or whatever it should be. Same occurs on a Win XP laptop I tried, but explanation of the errors are more general but seem to be the same.
Seems it might be this issue that 2.2 caused for the SGS Vibrant ?
http://forum.xda-developers.com/showthread.php?t=860328
http://forum.xda-developers.com/showthread.php?t=846384
Could just be the SD card failing unrelated to the update, but I have no idea. Seems I can copy to an external SD, and then copy via the phone to the internal SD. Odd.
I have tried format via Windows, which resulted in 2.19gb size, but phone reboot reset it to 13gb. Format via phone did not resolve either.
Any fix that will work? or is it borked.

I'll repost my question here.
Did you try the "format internal-sd" from CWM recovery ?

No, Im new-ish to Android so I dont know all the apps to use yet, but have done phone hacking for years on Palm and iOS.
Seems CWM Recovery is a desktop app? I will try when Im off work.

rye&ginger said:
No, Im new-ish to Android so I dont know all the apps to use yet, but have done phone hacking for years on Palm and iOS.
Seems CWM Recovery is a desktop app? I will try when Im off work.
Click to expand...
Click to collapse
Download Rom Manager from the market and run it. Click on install clockworkmod recovery. Then you can reboot into recovery. Please see the clockworkmod thread for more info
Sent from my SGH-I897 using XDA App

Don't forget to root first. I had a pain rooting this JL1. I spent 20 minutes playing with JL1 and I couldn't stand the lagginess. I'm sure lagfix would've helped, but I just went to a custom ROM instead.

Tried superoneclick only once and I'm rooted even went as far as unlocking it. Also, my phone isn't affected by the sd card bug. I can transfer files bigger than 2.19 Gb and it's showing the full size in Windows. Froyo runs flawless so far even though it's still not clear whether it's official or not.

Hmm, that's an odd one indeed.
Curious - I took a look at the 2 threads that Rye pointed out and one seems to be about external sd issues and the other about the mounting issues with 2.2 vibrant kernels. Doesn't seem like the problem you are having is either one of those... Could be but didn't seem that way upon review.
Did you happen to try and restore any backup after upgrading to 2.2 or anything? Can't imagine what would cause it but seems like it's getting mounted strangely or something... Surprised that a format internal sd wouldn't fix it in recovery...
Second question - what Samsung drivers / driver pack are you using on your Windows 7 x64 install? Wondering if the driver is failing to recognize the file system type and is causing Windows to treat it as a file system that shouldn't accept a file larger than 2+GB...

I havent noticed any problems with the size of the file. What happened with mine is that i transfered a couple of movies (about 3 or so) and then transfered about 4 gigs of music. halfway through the music it started giving me the error. after that, even transferring individual mp3 or pictures would result in an error. The internal sd card showed up on my computer as having 8gig free. after that i ran the check disk (by right clicking, going to properties then tools). my computer found errors and corrected them. after that, the internal sd card showed up as only having like less than a hundred mb left

Riker2k, not sure if the drivers for Windows are the issue. I think I installed some drivers called SGH-i897_Captivate_USB_Drivers_5_02_0_2 that I got from the Samsung website, but I also just installed Kies to get the 2.2 update.
On the XP laptop, I was just using mass storage so it must have been generic drivers that were already on it.
To be clear, its usually shows as correct size in Windows explorer, but when I go to the format utility in Windows, it shows 2.19gb.
Im about to do the CWM recovery format and will post the results.

If you are using the Rogers 2.2 update with no kernel modifications then the CWM will not work for you.
The Froyo kernel from Samsung comes with Recovery 3e which RomManager can not replace for 2e as 3e requires digitally signed packages.
consider (i have not tried):
- root device
- adb shell
- su
- backup any files you need on /sdcard to /sdcard/external_sd
- use the format commands to re-format /sdcard
-- probably mkfs.vfat or the like.

rye&ginger said:
Riker2k, not sure if the drivers for Windows are the issue. I think I installed some drivers called SGH-i897_Captivate_USB_Drivers_5_02_0_2 that I got from the Samsung website, but I also just installed Kies to get the 2.2 update.
On the XP laptop, I was just using mass storage so it must have been generic drivers that were already on it.
To be clear, its usually shows as correct size in Windows explorer, but when I go to the format utility in Windows, it shows 2.19GB.
Im about to do the CWM recovery format and will post the results.
Click to expand...
Click to collapse
Yea, really not sure if the drivers are a problem or not. When I checked mine, running the Rogers 2.2, it shows the same as what yours does in the format utility - 2.19GB. That is odd because it seems to set the filesystem type as FAT32 which can easily handle the 13.0GB size of the volume. The properties in Windows show 13.0GB w/ about 11.0GB on my disk that is available...
Regardless, I would be hesitant to format or repair that disk within Windows. Who knows if there is something within Android that is put there as a translation layer that maybe Windows isn't seeing / reading correctly through the driver, etc. I'm sure someone does know but I'm not that guy so if anyone call fill in the details...
And, after just testing on my own system... bang, same issue trying to copy a 900MB file to it... Hmm, this just got interesting.
Going to check a couple of other things, will post result.

I had this exact same issue. The only fix for it that I could find was to do a complete restore of the stock rom. Oh well, nice to have a fresh phone.

Hmm, this is not a fun problem.
Just tested formatting the volume - from within the running phone only, mind you - and the result is strange. After copying everything from my SD card to my computer, with no issues, I unmounted the USB, formatted the card through the settings / sd card storage menu / format internal sd card. Took about 30 seconds after which point I reconnected the device, windows picked it up and I mounted it, recopied about 2GB worth of data to the card with no issues at all. Added an additional 500MB file to it with no issues. Disconnected the device from within windows using the safe removal tray tool, turned off usb connection on the device and then unplugged it. Remount the usb device and windows sees it no issues but I can't copy a single item or create a folder on it. Exact same errors as what Rye described and I encountered the first time.
So, seems like after a fresh format the sd card can be mounted in windows, ONCE, and then all hell breaks loose.
Why??? Will keep testing but looking like I need to move back to my previous di11igaf's ROM. Can't work like this...
Interested in what you find, Rye.

Oh btw, i am able to transfer files with no problems if i connect to the pc in media player mode. I have problems when i am in mass storage and kies connect modes

Riker2k, good stuff. I have no news, Im stuck where I am unless I swap the kernel it seems as I cant use CMW Recovery to format.
This is over my head, so I will for now probably just do a format, load up the card via Windows, and then use the external card to slowly add items when I want to and transfer over to the internal through the handheld. Ghetto. Either our Sd cards will get worse and die, or more people will have issues and it will get patched I guess?
Dennishwc, I will try media player mode but I think it did nothing when I connected that way the other day. I didnt mess with it much though. I need mass storage to use iSyncr app though, but there is a wi-fi add-on that may help me avoid that.

Well I just tried the format and dump a lot of stuff via Windows idea, and it only did about 2.2gb before the error stopped the fun. It did this twice, so this is is EXACTLY at the 2.19gb capacity that Windows is seeing in the format utility. So, I do have some news.
Again, this is over my head as to what to do next.

Has anyone tried moving files over via adb and see if you hit a 2.19GB limit?

I am having the same issue when copy files while connected in USB Mass Storage Mode (consistent).
On the plus side, I also tried connecting in USB Kies Mode, and I have yet to see this error. Copying is slower; but, it seems to work.
This could be a workaround for folks getting the error in Mass Storage Mode.
I am running Rogers 2.2 (all stock) and rooted with SuperOneClick.

i'm having the exact same problem. if i pick "mass storage" i can't copy anything over hte internal sd card, but if i use "media play" option, i can do it without any problem. i guess that's a temporary solution

i'm having the same problem, though the size and free space of the internal storage shows up correctly in my system.
i can also copy files no problem to the external SD when in mass storage mode.

Internal SD card issue - Need Guru help

Guys, need some help here
I'm generally ok at fixing these sorts of problems but this one has got me well and truly stumped.
Been trying without much luck to flash a working fw onto i9000 since updating to rom with voodoo and forgetting to disable lage fix before flashing non voodoo rom. Even flashing back with voodoo rom doesnt help.
I think I've finally managed to ascertain the root cause of the issue seems to be that either the internal sd card is somehow write protected or the current journalling on the ext4 partition is undoing and changes to that partition (where does journal reside?). I seem to be in a viscious circle as well. I cant mkfs a new ext2 partition as it complains that it wasnt unmounted cleanly, If I ignore I get a segmentation fault. If I e2fsck the partition it complains it cant write to the superblock, If I use alternate superblock it complains there is data in the journal, trys to replay the journal and complains it cant write the superblock. If I tunefs to disable the journal it complains that the needs_recovery flag is set so need to e2fsck the filesystem first :-S.
I've flashed kernel that has recovery option to disable lagfix. If I choose this and reboot it just sits at Galaxy S boot screen indefinite (over an hour waited). If I mount USB using same recovery mode, I can see the files in the partition, I can (through windows) delete the files so folder shows no files however disk still shows a percentage used. If I eject and remount all the files are back. I have formatted the partition as fat32 and re-labeled the drive. Format completes succesfully (done this both using cmd line and right click format). on eject and remount, label change has remained but files are back again. Partition still shows up as ext4 when looking via adb shell.
Have tried to use parted, but despite all parted functions giving success indicator, no changes are ever made.
I'm now at a loss on how to proceed?
Anyone any ideas on what next steps could yield any further results?

I had a similar issue... what solved it was to flash Darky's ressurection rom. Had to flash it 3 times in a row.. Flashed with Odin 1.7.
Hope it helps, i know how frustrating it is.
Sent from my GT-I9000 using Tapatalk

I have tried Darkys res rom, It wouldnt boot, just stuck at Galaxy S boot screen so didnt persue it. I'll try doing it multiple times as you suggest and let you know. Ta
EDIT: Nope tried it 4 times, same result, boots to Galaxy S screen, I get the voice prompt saying its coverting system, will take approx 2 mins, then another voice prompt about restore, then it sits there indefinetly (waited about 20 mins each time). Whilst its in this state adb devices shows device in recovery, and I can get an adb shell, however there seems to be no commands accesible, cd, ls, mount etc

nivenj said:
I have tried Darkys res rom, It wouldnt boot, just stuck at Galaxy S boot screen so didnt persue it. I'll try doing it multiple times as you suggest and let you know. Ta
Click to expand...
Click to collapse
I have a way that may fix your bricked phone. If it gets to the SGS logo boot animation, I would try flashing CM7. Try it out and then try reverting back to a stock rom.
Here are the instructions:
http://forum.cyanogenmod.com/topic/15275-gt-i9000-cyanogenmod-7-we-love-bugs-version-20110211/
You MUST follow the instructions to the letter though. Do not deviate from them!
How do I know this may work? Because it happened to me. My phone was bricked, then I flashed CM7 and now it works again. I've tested going back to stock rom and it works. Give it a try. It may be tough reverting back to stock since CM7 gingerbread is awesome! lol

If that doesn't work try flashing one of the earlier Froyo ROMs, I used XXJP2, and then moving on from there. The key is to ensure that whatever ROM you use has all three files (PDA, Modem, & CSC) and tick Re-Partitioning on Odin.
Again this is what worked for me and my device was restored to great working order.

robbiev80 said:
I have a way that may fix your bricked phone. If it gets to the SGS logo boot animation, I would try flashing CM7. Try it out and then try reverting back to a stock rom.
Here are the instructions:
http://forum.cyanogenmod.com/topic/15275-gt-i9000-cyanogenmod-7-we-love-bugs-version-20110211/
You MUST follow the instructions to the letter though. Do not deviate from them!
How do I know this may work? Because it happened to me. My phone was bricked, then I flashed CM7 and now it works again. I've tested going back to stock rom and it works. Give it a try. It may be tough reverting back to stock since CM7 gingerbread is awesome! lol
Click to expand...
Click to collapse
Thanks for the suggestion but this wont work, as I said above, the root of my problem is that the internal SD card wont keep any changes I make to it. Once I upload the zip file and the phone reboots into download mode in order to flash with Odin, the files I would have put on the internal SD card will no longer be there. It seems to me that the FS cant set the recovery_flag to clean and therefore keeps replaying the journal and overwriting any changes on reboot.
I sort of proved this earlier, by managing to flash JP4 with speedmod kernel. This allows the phone to boot, but it has major force close issues. I can take a photo, see it in images, I can even mount it via USB and see it on my laptop. When I reboot, the photo is gone and anything I've deleted is back again.
Fundamentally I need someone who maybe has some experience fixing the filesystem, I cant see any Roms working until this manages to get resolved

thecrucible said:
If that doesn't work try flashing one of the earlier Froyo ROMs, I used XXJP2, and then moving on from there. The key is to ensure that whatever ROM you use has all three files (PDA, Modem, & CSC) and tick Re-Partitioning on Odin.
Again this is what worked for me and my device was restored to great working order.
Click to expand...
Click to collapse
Ive tried JP2, but no joy. Also tried
JFF,JS5,DDJG4,Darkys Res,JP4,JM8,JS3,EUGENE373,JPC,JP3,JM5 & Finally JPU, All with a mixture of partitioning and not.

got an ext-sd card? if so remove it, format sd, then try factory reseting,
edit : flash an old rom, like jm2, ascertain its function then yell again (missed a line *doh*)

azuresystem said:
got an ext-sd card? if so remove it, format sd, then try factory reseting,
edit : flash an old rom, like jm2, ascertain its function then yell again (missed a line *doh*)
Click to expand...
Click to collapse
Yep tried all that, tried formating via recovery mode, says successful, but all data still exists on reboot. Have tried formating using windows, via command line, via adb shell, they all say they are succesfull but on reboot, same problem exists and all data is still there :-S

nivenj said:
Ive tried JP2, but no joy. Also tried
JFF,JS5,DDJG4,Darkys Res,JP4,JM8,JS3,EUGENE373,JPC,JP3,JM5 & Finally JPU, All with a mixture of partitioning and not.
Click to expand...
Click to collapse
I am sorry, not sure where to go from there. Keep Googling and maybe you'll come across something helpful.
Sent from my Galaxy S using Tapatalk

Hi. Has anyone come across a solution to this problem. Any changes to the data on my internal SD card are lost on reboot, and many of my apps are not working.

jm_928 said:
Hi. Has anyone come across a solution to this problem. Any changes to the data on my internal SD card are lost on reboot, and many of my apps are not working.
Click to expand...
Click to collapse
Try editing the void.fstab to swap the internal sd card and external sd card. --- it won't address issues with internal card, but it may get you up and going again..

fooman123 said:
Try editing the void.fstab to swap the internal sd card and external sd card. --- it won't address issues with internal card, but it may get you up and going again..
Click to expand...
Click to collapse
Thanks fooman123. Can you tell me where I can find the void.fstab file?

jm_928 said:
Thanks fooman123. Can you tell me where I can find the void.fstab file?
Click to expand...
Click to collapse
see this tread:
http://forum.xda-developers.com/showthread.php?t=1088474&page=14
use the correct void.fstab for your phone (i9000 and i9003 are different)
backup the original and compare the new and old void.fstab file..