[Galaxy S I9000 Q&A, Help & Troubleshooting] tekkneak:
Hi Guys,

Here's some history on the phone:

- Purchased in Aug 2010, came withJK3 (not sure but it was ECLAIR)

- Since then the phone has been performing unbelievable, I had put several ROMs on the phone custom and stock as well as multiple kernels to fix battery drain, etc.

- A few days back after flashing Hamster's 6.3 ROM (which I had been using for a month prior, thus is completely irrelevant to my issue - find it here), I tried to access an app I had recently used when the phone completely froze on me, even power button would not respond; so I did a hard reboot only to be greeted by the cwm recovery window notifying me that the FS partition had changed and what I would like to do.

Knowing I had not changed anything, I simply picked "remove new configuration and boot phone"

Thats where I crapped my pants, the phone would reboot itself every 2 seconds and would not go past the first samsung boot screen.

I tried everything without luck, when finally 2 days later with special thanks to the following people listed below I found out exactly what's wrong with the phone and how to actually get to recovery and get a working boot on the phone.

I tried many many combinations of ROMs and kernels through ODIN and nothing seemed to work, initially I could get past the first boot screen if I re-partitioned with 512 and flashed JM8, but even that stopped working eventually. Finally late last night, I got the phone to boot. Here's what I did:

re-partition the phone with 803

Flash the phone with stock JLU (you will need the complete ROM with PDA, PHONE and CSC files)

Flash JPY

FLASH CF ROOT

FLASH SPEEDMOD kernel k12j

After the final step above you should have working recovery with adb for the first time! so now try the following umount commands and if they work then you are okay and do not have a dead sdcard/controller

umount /dev/block/mmcblk0p1
umount /dev/block/mmcblk0p2
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file

Thanks to codeworkx for the above commands. If you try the above and they dont work or recovery shows the errors such as:

E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)

or cannot mount SD card

then most likely you have either a bad internal SD or bad controller.

Regardless, your phone should now boot. if you can mount your SD card, you should do a complete format in windows after running the commands above; otherwise you still will not be able to access your internal SD and even though you can boot, your data will be lost after each boot and you cannot download anything from market or update current apps.

-------------------------------------------------------------

So now, I have a phone that boots up and works but cannot mount internal nor external SDs, here's the error dmesg gives in this regard, which again codeworkx helped me disect out of the logs:

"mmc0: error -110 whilst initialising MMC card"

I recently opened the phone up to try and see if I could find the location of the internal SD and to my surprise it only took 5 minutes and a little help from diagrams at phonewreck.com

So I know where the internal SD is, but no clue where the controller would be and whether its even possible to replace or any otherway to get the data back from the current internal SD which MAY still be okay in my case...

Any help with this would be appreciated - at this point im willing to try anything.

Thanks and if you have any questions feel free to ask.

People to note and thank for spending hours with me, walking me through what they know: virnik0, Jim_Panse, codeworkx, Josaatt, uppon2 & eitama - thanks guys!