yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] aleks07:
Check out this thread:

http://xdaforums.com/showthread.php?t=832827
[Galaxy S I9000 Q&A, Help & Troubleshooting] hburn:
nevermind...
[Galaxy S I9000 Q&A, Help & Troubleshooting] a7ad67:
not working the same problem same error
[Galaxy S I9000 Q&A, Help & Troubleshooting] jark99:
My brothers galaxy S has broke too...internal sd card problem. Were going to bell today luckily he bought it and contract. IF BELL doesnt give him a Galaxy S replacement.....there gonna regret running into me, i swear, this is the WOrst customer service and Samsung needs to OWN up to its DEFECTS :@ :@ :@.....

signed

angry samsung user.

p.s. anyone know on how to get samsung to recall the units??
[Galaxy S I9000 Q&A, Help & Troubleshooting] aquenne:
well, 2 days back with my sgs.

gps seems better, battery life seems better, but reception is definitely worse.

in areas where I would normally have 1 or 2 bars, im not getting service now...dropping calls etc..

any hope that this will fix with the official froyo??
[Galaxy S I9000 Q&A, Help & Troubleshooting] Bax5:
Hi Everyone.

So I have a Bell i9000, and at first i had the comatose problem on 3 of the phones, search comatose on this forum and you'll find the thread about that. My third one, i did the 850mHz lock on it and all is working well. I rooted the phone using one click lag fix about 2-3 weeks ago.

And today, while uninstalling a bunch of unused applications, i get that my internal and external (8gb kingston) sd cards are "unavailable". it kind of scared me cause i thought it might be done. But luckily, a power off power on fixed it.

Am I right that this is not the same issue you guys are "polling" about?

I'm running 2.1 with lag fix.

I would be extrememly unhappy if this phone started to fail again...
[Galaxy S I9000 Q&A, Help & Troubleshooting] aquenne:
Probably not what you want to hear, but having the external SD fail happened to me about 2 weeks before the internal went.
[Galaxy S I9000 Q&A, Help & Troubleshooting] dkolody:
Another one bites the dust....

Sent it into the shop today.(Date on Battery Aug 18) I will let you know in 3-6 weeks (ugh) what they did.

Not sure if I can go that long but I have no choice. :-)
[Galaxy S I9000 Q&A, Help & Troubleshooting] saikrishnamraju:
Same problem here, SD card failed and won't boot. I unlocked my phone and using Telus SIM. I think I won't get the warranty from BELL but looking for some kind of service to fix this issue. Can I send my phone directly to Futuretel for repair? How much they charge.
[Galaxy S I9000 Q&A, Help & Troubleshooting] jark99:
You have to email FutureTel Solutions and they will reply with a shipping address and everything. I shipped mine from Bell and they charged me $100 which is bull****, when my cell comes back i am going to complain so much about that fee.:(
[Galaxy S I9000 Q&A, Help & Troubleshooting] xxgg:
Slightly Off Topic:

I know this thread of for i9000m specific only but

Does anyone heard of any same death issues of Captivate from Telus & Rogers ?

How suck would it be if only or majority of issues are from Bell's i9000m phone?

Wow!

Also, by looking at the DEV thread of CyanogenMOD for SGS, it looks like when a ROM is properly built it will not require any sort of lagfix.

I guess AOSP + drivers form SGS ROM will be the best for us.

I hope CM ROM for SGS progress quickly.

Mean while, I sure am not going to be messing with any other custom ROMs out there as it does not seem to be 100% happy with i9000M models.
[Galaxy S I9000 Q&A, Help & Troubleshooting] jark99:
Samsung loves Rogers :) i am going to assume no, there isnt any dying phones yet. BUT only time will tell. and i think they have fixed this isssue for Rogers. But wait and see....the phone is relatively new
[Galaxy S I9000 Q&A, Help & Troubleshooting] er1cha:
Phone returned - Full S/W Upgrade

Hi,

I think i posted earlier about my phone having the black screen issue. It was 31 days in and it originally started when trying to flash a new rom using ODIN.

Anyways, after 1 month and lots of getting passed off to Bell, Samsung, The Source (where i bought it), back to Bell, etc. I was finally able to get it fixed.

My repair invoice says "Full S/W Upgrade & Phone reset by manufacturer." My battery date is 2010.07.17

Hopefully someone will leak this mysterious S/W upgrade and we can start fixing these on our own. Let me know if you need any more information regarding my repair.

-er1cha
[Galaxy S I9000 Q&A, Help & Troubleshooting] sleeplessfreek:
Could someone post a list of places who can do a fix on this phone?

On a side note, my phone basically loops at the start up 19000M screen now and i assumed it to be the SD failure.

What are some ways of testing it to ensure this?

My phone just passed the 60 mark and it seems like my only hope is a repair center.

Damn.. Can we sue samsung already? Any lawyers with a messed up SGS who would like to help out the commnuity?
[Galaxy S I9000 Q&A, Help & Troubleshooting] kevinhu.ca:
My one still working good.

I am not a heavy user, approx 4 GB.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Lightarrow:
ARGH Mine died AGAIN. 2 weeks after recieving the replacement.

Did NOT Flash with odin, Just CWM. Was using Doc's ROM with Speedmod Kernel, No LagFix.

Im going to try to exchage this phone with the Desire Z. Im sick of this crap. I got an android phone to be able to flash it and try stuff on it. Not to corrupt SD Cards every 2 weeks ! Sadly it's been 3 months i had the phone so i fear ill be stuck with it. Maybe repair it, then sell it on ebay or something.
[Galaxy S I9000 Q&A, Help & Troubleshooting] catalinu:
I think that I forgot to mention: "Absolut service" give 90 days warranty for their repairs...
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
just calm down people, that is the goal of this sticky poll

to figure out what is causing the Internal SD to go dark

in a few of those cases it seems to correlate to the idea of the I/O being dead

in most other cases it seems to suggest it's the partition that it's messed up

from all the topics that has shown up and came across it appears that people that were playing with the last few leaks of Froyo had the worse problem, which might relate to the I/O issue, or simply might be a bug in Froyo tht caused the I/O to be burned?

On the rest of the people that were just installing lag fixes to get an extra boost in performance, were mostly Partition related errors, which should be fixable with some hard work.

we are still in the process of gathering data, any information or lead should be taken into consideration
[Galaxy S I9000 Q&A, Help & Troubleshooting] icsocket:
I have two phones with 2.1, no fix, voted once. No issue so far. I am a light user without external SD, my other half is a heavy user with 16G external memory.
[Galaxy S I9000 Q&A, Help & Troubleshooting] dawgpound6985:
Just for my own clarification...The internal SDCard corruption is mostly (if not all) happening on the i9000M yes? Has there been any one with other Galaxy phones with the same issues? Also, I know, Bell has been warrantying the phones, but how can we be assured that the problem really has been fixed by Samsung? Has anyone who has gotten a repaired Bell Vibrant have another corrupted internal SDCard? (I'm assuming the last question is a little bit harder to find since people would be more cautious the second time around.)
[Galaxy S I9000 Q&A, Help & Troubleshooting] thedauntlessone:
There seems to be a much higher rate of i9000m SD cards dying. I don't think they are corrupted, I think they are literally dying. It seems they are defective in the first place, and would have died unusually fast anyway from regular use.

I think another good thing to mention is WHERE you got your phone from (East vs West coast etc) to see where the defective phones are coming from. Regardless, there's a large majority of people with working phones vs dead phones though sample size is quite small.
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
you can't really conclude that until we have run another poll to check on the other models
[Galaxy S I9000 Q&A, Help & Troubleshooting] decepticon:
My internal SD was about 30-40% full, uninstalled original One Click Lagfix, rebooted, installed 2.XX and it killed it.

Was on JH2 but I don't think the FW had anything to do with it as it was working fine for days before.
[Galaxy S I9000 Q&A, Help & Troubleshooting] moophone:
Mine died after less then one month. I'm now waiting for a replacement.

I asked RyanZA if the OCLF was possibly related, see my post and his reply below. I can't reformat the card in recovery. The dealer said this is the third phone with this exact problem he has seen.

---

Hey man. Sorry to bug you, but I'm hoping you could help. I have a Bell GT-i9000 I just flashed JPC on. I applied your OCLF from the market, and all was well. I checked my phone last night and there was an error in the notification area about did not cleanly unmount /sdcard. I power cycled the phone but it now only boots to a black screen.

I tried reflashing but I cant seem to access /sdcard (no root). I'm not sure but I think the OCLF ext2 extensions are causing the problem? Since I cant su in now I cant fix it.

Do you know of any way I can get root or re-flash/format the internal sdcard? I can get to both recovery and download from the phone.

Cheers!

Greg

---

Probably not OCLF, since it doesn't modify /sdcard

Best bet is adb reboot recovery, and then use the format sd card and clear data options
[Galaxy S I9000 Q&A, Help & Troubleshooting] moophone:
Could someone put together a howto for this "hard work" to fix it? I might have a shot at fixing/fsck'ing it if I had root again, but I cann't use update.zip.

Is there a recovery tool that will let you run an update.zip from say /tmp?

I really want to know if its really dead, or if its just flagged as dirty, and needs to be fsck'd and remounted
[Galaxy S I9000 Q&A, Help & Troubleshooting] moophone:
Fortunately the freezing has been fixed in all the more recent firmwares
[Galaxy S I9000 Q&A, Help & Troubleshooting] wagenbach:
This issue recently happened to me. I had the phone for about a month, and everything was fine (actually the battery life was horrible, like 6 hours on a full charge, but that's another story). I put on JPK, and I loved it. With it, you were able to put it into 2g mode to save battery (something you couldn't do with the stock Bell), and the GPS actually worked!

I couldn't figure out how to root JPK, but it was already pretty fast, and everything worked well, so I just left it.

Everything was fine for about 3 days, when all of a sudden, in the middle of a text conversation, my texts began to fail sending.

I rebooted, and this time a whole bunch of apps had problems loading.

I rebooted again, and this time, it stayed on the "S" screen for a bit, before going blank with the bottom two "menu" and "back keys" lit up.

No problem, I thought, just reflash with Odin. Didn't work. I got that error message that everyone was talking about, the one about the SD card not being able to mount. I went on here, and discovered that this was an actual issue that might not be fixable.

Luckily, I bought the phone in the first week of September, so I went down to the Bell store where I bought it. I showed the guy how it didn't boot, and he said that he'll replace it right away, under their DOA policy. He was like, "This is obviously defective, there's no disputing that." He also said that normally, it was a 15 day return policy, but he said because they were low on stock, the DOA policy has been extended to 60 days (what one thing has to do with the other, I don't know).

Anyways, they were out of stock and they said that I would get a replacement in a couple days when some arrived. They actually ended up calling me back later that night saying that some arrived, and I exchanged the phone no problem. He didn't ask me anything about rooting or firmwares or unlocking or anything like that.

I got the new phone now, but I'm kind of torn between keeping it stock, or doing the whole 2.2 flashing again just to see if that was what was really causing the problem. The 60 day policy gets reset with the new phone, so I basically have 60 days to find a problem with this phone, and still get an off the shelf replacement.

Anyways, just wanted to contribute somehow to this site. Thanks for all the information guys.
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
do it, do the JPK flash again, play with it as much as you can and see if it dies

if it does, then we can get a confirmation JPK is one of the cause behind all this
[Galaxy S I9000 Q&A, Help & Troubleshooting] madmack:
I just want to note here that when we receive the sdcard was unable to mount error, we're really talking about the internal memory of the phone and not the internal sdcard.

a simple command such as "busybox df" should show you how and what each partition is being setup.

from that command, you'd see that /dev/block/mmcblk0p2 is mounted on /data which I know most lagfixes work with, and that is not the internal sdcard (8GB/16GB) it is, in fact, about 2GB.

the actual internal sdcard is mounted on /dev/block/vold/* which is not failing from what we can tell based on the received errors in recovery
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
well the mmcblk0p2 is a partition of the internal SD that's why a 16 GB internal SD reads as 13.8 available to user after they take out the 2 GB chunk for system use

but that is a good point you bring up, so in this scenario it shows the system partition is messed up, but internal SD is still good

technically one should be able to fix/restore the 2 GB partition to get it working again.
[Galaxy S I9000 Q&A, Help & Troubleshooting] madmack:
interesting. I didn't quite realize that.

anyone with a broken phone can check whether the /dev/block/vold devices are there ? if they are, then its probably just the mmc partition 2GB of the 8/16GB that is screwed. and not the entire sdcard.

anybody knows if ticking Re-Partition in Odin actually rewrites the partitioning table for the sdcard ? if so, how come we don't lose our data in the rest of the remaining space in the sdcard ? (is this even possible?)
[Galaxy S I9000 Q&A, Help & Troubleshooting] rmanaudio:
We gotta get some Dev's on this...im sure it can be fixed without hardware replacement! Some sort of a work around!
[Galaxy S I9000 Q&A, Help & Troubleshooting] dawgpound6985:
Here's what I get:

$ df
df
/dev: 166704K total, 0K used, 166704K available (block size 4096)
/tmp: 166704K total, 8K used, 166696K available (block size 4096)
/mnt/.lfs: Function not implemented
/efs: 6064K total, 5128K used, 936K available (block size 1024)
/system: 282432K total, 250328K used, 32104K available (block size 4096)
/cache: 30792K total, 20K used, 30772K available (block size 4096)
[Galaxy S I9000 Q&A, Help & Troubleshooting] supercurio:
Hello,

When the Linux kernel (stock) don't detect the internal SD device at all (no trace in dmesg) I'm afraid no workaround exist!

There must be something wrong with many of these phones, my bet is that it's defective hardware.

About lagfixes. Not everyone of them are created equal. With OCLF, you create and wite big loop ext2 files even if the space is not used. Always more than 1GB.

With Voodoo, only the space used is copied to the vfat partition then restored to ext4 again. It means that if you have 100MB in /data, the entire operation will need only ~ 205MB in total.

Voodoo re-partition the internal sd for /data only, and it take care of the alignment to prevent the bad performance and premature wear that append if your sectors are not aligned with the memory chip size.

I would suggest I9000M users to stress their sdcard a little and see if it crash, and get a replacement ASAP instead of using a defective phone which will eventually die in a few months or about a year with light use.

But of course, what I said here is completely wrong if the repaired phones are really just a software restore.

If it's right, i have no explanation and suggest to ask exactly what Samsung repair center did ;)
[Galaxy S I9000 Q&A, Help & Troubleshooting] madmack:
is your phone broken ? can you run "ls /dev/block" and "ls /dev/block/vo*" and post your results here ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] dawgpound6985:
Yes my phone is broken. Here's what I get:

$ ls /dev/block
ls /dev/block
stl12
stl5
stl2
stl1
bml12
bml11
bml10
bml9
bml8
bml7
bml6
bml5
bml4
bml3
bml2
bml1
bml0!c
tfsr12
tfsr11
tfsr10
tfsr9
tfsr8
tfsr7
tfsr6
tfsr5
tfsr4
tfsr3
tfsr2
tfsr1
tfsr0!c
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
ram15
ram14
ram13
ram12
ram11
ram10
ram9
ram8
ram7
ram6
ram5
ram4
ram3
ram2
ram1
ram0
mmcblk0p2
mmcblk0p1
stl3
stl11
stl10
stl9
stl4
stl8
stl7
stl6
mmcblk0

$ ls /dev/block/vo*
ls /dev/block/vo*
/dev/block/vo*: No such file or directory
[Galaxy S I9000 Q&A, Help & Troubleshooting] madmack:
Your phone is not broken :) only your partitions are messed up.

notice that you have the mmcblk0 files listed, in my case, they weren't.

Try to flash any ROM via Odin that uses the Voodoo fix. One guy reported that to work, then use the Voodoo uninstall method to get it off and restored back to rfs (samsung's filesystem). Then you can flash any ROM from here on out.

If that doesn't work, you'll have to use a tool like "Parted" in a rooted recovery to get the partitions set again.
[Galaxy S I9000 Q&A, Help & Troubleshooting] wang1chung:
i posted the exact same thing about 1 month ago, and people said i was stupid for thinking flashing roms could brick a phone.......clearly there is no rhyme or reason to the bricking (once you flash, it's a ticking timebomb no matter what). i think i'm going to have to follow suit and sell mine as well since no progress is being made. just no desire for me (don't like the keyboard).

btw, out of curiousity, did you notice if your motherboard was replaced when you got it back?
[Galaxy S I9000 Q&A, Help & Troubleshooting] xxgg:
What do you think of over models of Galaxy S? The Captivate? It seems that we are not hearing much from those users?

Than again why take a a chance from any of Galaxy S...

I too seriously think that there must be something different from i9000 to i9000m model. Sure, we've seen users who has not done any flashing/lag fixing get bricked too but... it's not just this phone, some % of every other phone in the world get bricked for whatever reason too.

I think I am gonna go with HTC Dezire from Telus as I see use for cheaper than other android phones.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Lightarrow:
Yes, Motherboard was replaced. one week after receiving my replacement, i've noticed things appearing on the SD card like Lost.Dir, could not open all my files..

Then this morning, Booted, Only had basic apps with launcher, Could not mount SD.

Im really afraid to keep this phone because it's been 3 months and i got 3yrs with bell.... i do not plan on spending money on repairs or another phone in that 3 years. My last phone was a HTC Touch, which i flashed many times, without issues, even dropped it once.

I don't like the keyboard on the Z but i see no other alternative (i hate iphones) unless you found something else that is nice and works with bell !?
[Galaxy S I9000 Q&A, Help & Troubleshooting] xxgg:
Take it back to Bell, complain, if nothing, ask to speak to manager, demand that you want comparable android phone. Which currently is only Dezire Z.

Unlike a lot of us, atleast you are with Bell and have Bell to go back to.

Good Luck!
[Galaxy S I9000 Q&A, Help & Troubleshooting] Lightarrow:
I already sent it back for repairs this morning. The rep told me that if it happens a 3rd time (which it will because i will not stop flashing because of crappy hardware) they will be able to change my phone for free to another android.

I would have liked the Desire HD but they don't have it.

Good luck to all of you that are not dealing with bell. Sad to see that this phone has so many issues!!
[Galaxy S I9000 Q&A, Help & Troubleshooting] yondaime3001:
i think after all that troubles about something should not even have any kind of problems...am gonna rethink about buying the i9000 galaxy s :S
[Galaxy S I9000 Q&A, Help & Troubleshooting] tylerham:
The Captivate from Rogers has been out for a week so I think it is too early to hear about issues.

Also, it has a slightly different model number from the AT&T Captivate so there may be issues when using AT&T ROMS.
[Galaxy S I9000 Q&A, Help & Troubleshooting] aquenne:
Is anyone else experiencing this as well?

Ive gotten a significant drop in reception all over the place, I dropping calls, I used to be able to drive and stream music, or use the GPS navigation, thats all impossible now. This is all after getting my phone back from repair, before it went out the above all worked fine.

Any recommendations on what to do next? Go after Bell? Samsung?

If the phone was like this from day 1, it definitely would of gone back within the 7 day window.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Freija:
I just dropped off my phone at the Bell store. I'm with Rogers though, but I had the full receipt in my name so there was no problem there I suppose (Actually, they didn't even ask me for ID)

I was charged a $35 quotation fee that I apparently get reinbursed for when I get the phone back. According to the rep. that served me they've been getting alot of SGSes in this week, but it should take "11 or 12 days" depending on how many phones get sent to the repair center.

Hopefully they don't find an excuse to refuse service and charge me some stupid fees. I'll let you guys know when I get the phone back.
[Galaxy S I9000 Q&A, Help & Troubleshooting] sleeplessfreek:
I was just on the phone with samsung and they told me to send my phone to futuretel.

They also noted after a 3rd attempt for repairs, samsung will begin covering the costs for it.

Has anyone gone with this route?
[Galaxy S I9000 Q&A, Help & Troubleshooting] jark99:
Alot of people have gone this route, people actually go and email FutureTel Solutions themselves and they usually reply to send the phone in.
[Galaxy S I9000 Q&A, Help & Troubleshooting] sleeplessfreek:
I just got the same reply. They told me to go to my provider and grab a proof of purchase and then they will send it in for me...

However, i got mine from wireless wave w/o a contract... do you know if they will do the same?

Btw, how are the repairs?

Also, how much does it cost to send it in myself?
[Galaxy S I9000 Q&A, Help & Troubleshooting] xxgg:
If you were gonna buy without contract, you should always buy directly from the carrier.

But anyways,,, yes, goto Wireless Wave. They should know what to do.
[Galaxy S I9000 Q&A, Help & Troubleshooting] xxgg:
I don't understand?

How is Samsung going to cover the cost for it ?

FutureTel will get paid by Samsung? Usually that is how it should work anyways.

By the way, who did you ship your phone with and how did the shipping costed ?

By the way, FutureTel provide 90 days warranty (for same issues they repaired for).

So flash the F**k away within that period of time, I am sure after two months if the phone doesn't brick... I would feel somewhat safe too.

Thanks for NotSoWellBuiltPhone, FutureTel is getting good business out of us.

Now people, let's think twice before we recommend this phone to anyone you care for.
[Galaxy S I9000 Q&A, Help & Troubleshooting] wang1chung:
Lost.dir is from the froyo roms i've noticed (when my phone worked).

i would've thought if your motherboard was replaced recently, it would be replaced from a new revision of motherboards, hopefully without a hardware issue (assuming it's a hardware issue). since it still failed, i am going to lean towards software issues.

nah, there is nothing else, except the z (i'm not going with an iphone either).
[Galaxy S I9000 Q&A, Help & Troubleshooting] xxgg:
I flashed the UniversalLagFix http://xdaforums.com/showthread.php?t=814228

which is a modified CWM Recovery, it can actually detect, mount & utilize it (external sdcard that is).

I guess that normal ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] a7ad67:
can it detect the internal sd or just the external. can u flash on the external ??