yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] canad1an:
Interesting poll. Will definitely keep my eye on the results.

I just flashed Froyo XXJPK to my i9000M that I'm using on Rogers. I had it CF-Rooted and OCLF lagfixed, but OCLF caused serious FC's within 24h of use, so I just redid the whole thing, leaving out the lagfix. Given other's experiences with the internal SD's dying, I'll live without the lagfix. I'll see how long Froyo lasts on it's own.
[Galaxy S I9000 Q&A, Help & Troubleshooting] madmack:
My internal sd card died while I was using the JPK firmware.

I used JPC with 803.pit and reparition checked. I even used the OCLF lag fix and that worked fine. After reading reports about people losing their sdcards due to the lagfixes, I decided to uninstall that.

Stayed that way for 2 weeks without a problem. One day, I had this great idea of trying out JPK, I install JPK without reparitioning in Odin, and loaded all PDA/CSC/PHONE from JPK. No lag fix was used. Three days after using the phone, boom.. black screen! backlights are lit constantly and phone doesn't respond to anything. Went into recovery only to realize the dreaded red message about not able to mount /dev/block/mmcblkp0 (device not found).

There goes my story. One thing to note, at the moment the phone died, I was having some terrible reception. Phone kept switching between 3G/H/E constantly. Am thinking maybe the JPK modem was not really meant for our phones and thats why the motherboard (or sdcard) just died suddenly.

or maybe I was just unlucky and received one of the units in the bad batch that bell released.

will be waiting eagerly for the poll's results :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] aridoasis:
i have about 9.22 gig used up as of now (music+movies). thought it was wonky but turned out my external sd had the prob. i'm on JM8. had lag fix (voodoo) installed prior, but no lag fix as of now.
[Galaxy S I9000 Q&A, Help & Troubleshooting] canad1an:
No way. I'm having the same 3G/H/E issue with Rogers now after flashing JPK with JH2 CSC/MODEM and 512 pit for the second time. I think I might revert back to 2.1 before I brick mine. Since I'm not with Bell and have modded it, no warranty for me.
[Galaxy S I9000 Q&A, Help & Troubleshooting] YG007:
I was on JPH when it happened to me. I flashed JPH through Kies and it was totally successful. Had it running for over 12 hours. I had JPC FW before I upgraded, and after the upgrade, I still had all my contacts/text messages etc still on the phone, so I didn't do a reset/wipe of the phone as I did with every other firmware flash.

I had no lagfix running from JPC onward since I actually noticed that applying the lagfix made my phone SLOWER for some reason, espically when swiping through the app menus. I properly uninstalled the lagfix (from RyanZA [unlagfixme command]) and that was at LEAST a week prior to upgrading to JPH. Everything was fine, everything ran, I was showing the phone off to all my friends, showing them the black levels in video, mp3 player sans iTunes. etc. Most of my friends either used the iPhone, or crackberries (btw, they were jealous!! haha)

Anyways, I got into my car in the morning to go to work. After flashing to JPH, I noticed I couldn't pair up the bluetooth with the car, and nothing was new here as it still didn't work. So I plugged in the 3.5mm jack I used to hook up older mp3 players to my car, and ran the audio player. Once I ran the player, it did a FC. I clicked close or whatever the button was, and I tried to run it again. This time, it came up with the FC, but then it totally froze. I couldn't close the message or click anything. My only way out was to take the battery out. Once I did that, reinserted the battery, and powered up the phone I saw the boot sequence, then it went to a black screen with just the backlights on the touch buttons.

I went to the recovery menu (VOL +, home, power) and it said something in red letters about mmcblk0p1 error. I/O error. Once I saw the I/O error part, I knew I was screwed. I went to format the internal SD, and it said the exact same thing.

We'll see what happens as its been 2 weeks and Bell sent out my phone for repair instead of replacing it, (which is messed up since my phone was less than 3 weeks old). Hopefully it was just a bad batch and not something that is going to happen to my replacement phone when I get it back.

So, NO lagfix was applied, and I was on 2.2 JPH when it happened. I had a bunch of videos, but they were on an external SD card, so I don't think that makes any difference. mp3s were on internal SD, but only about 4GB worth. I had 5 pages of apps total, and was rooted. It sucks that the phone died on doing something so basic, but I guess that proves it doesn't matter WHAT you're doing, it'll just break if the HW is messed to begin with.
[Galaxy S I9000 Q&A, Help & Troubleshooting] thedauntlessone:
Hi curio, thanks for taking your time posting here. Been using Voodoo and love it very much. I do have some questions. Would Voodoo specifically do the same thing as the old ex2 lagfix? I'm just wondering if people with i9000m should avoid lagfix completely since there are so many problems with them. However, every i9000m owner should know, the problem won't just disappear. It'll break sooner or later, and sooner is better for warranty reasons. Though using the i9000m with a different carrier is a different ballgame
[Galaxy S I9000 Q&A, Help & Troubleshooting] Chatboy 91:
My internal SD card shat the bed once, and it's been fine ever since. Thankfully I didn't have very much on it, just some music and application data. I made sure to make an external backup afterward though. If I had to guess something in the file system decided to wonky and the system had to restore it to work.

One thing worth mentioning though is when the internal went on me, it wouldn't read my external either.
[Galaxy S I9000 Q&A, Help & Troubleshooting] wang1chung:
go into download mode, and re-flash back to 2.1 with repartition and a 512 pit. i had the same problem. seems to be an issue with jpk. won't let you mount that /dev/block/mmcblkp0.......i've been back on jh2 for a few days without an issues, and the ability to mount /dev/block/mmcblkp0 and go into clockworkmod recovery. i was comparing my jpk /dev partition to my gf's jh2 /dev partition, and they looked different. i dunno, but i'm staying away from 2.2 until the official release now.
[Galaxy S I9000 Q&A, Help & Troubleshooting] madmack:
I did try that, but the phone would just close after showing the Galaxy S logo.

I think there are two different errors. One with (/dev/block/mmcblkp0 not found) and the other with "file exists". If you have the "file exists" problem, then you can fix this by repartitioning the device with some ROM. For the other problem, however, your only solution is the closes Bell repair center!
[Galaxy S I9000 Q&A, Help & Troubleshooting] wang1chung:
you're right..........my error was slightly different. it said device "something or busy" (can't remember what the something part was)........because when i looked in file manager, the /dev/block partition was empty for me, and my gf's had all this crap in hers, including the mmcblkp0.
[Galaxy S I9000 Q&A, Help & Troubleshooting] lgkahn:
i'm not sure the cards are actually bad.. but mucking with the patitions on it with the lag fixes and reinstalling froyo etc.. seems to have screwed up the formatting or partition on the card and made it not readeable/writeable.. and most likely we dont have the correct tools in place to re-partition and reformat the internal sd that the shop with the correct cables can do.
[Galaxy S I9000 Q&A, Help & Troubleshooting] madmack:
That can't be the case. If the partition was messed up, we would at least be able to see /dev/block/mmcblk* devices when we shell in recovery mode. If the mcc devices are listed, then that means the hardware is working and you simply need to repartition. Something like "Parted" or repartitioning can do the job for you.

Problem is when /dev/block/mmcblk* completely disappears from the list of devices. That means the I/O controller is out because the kernel can't even see the device, let alone repartition it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] lgkahn:
well i believe from reading through the threads in most cases it does.. it just says cannot mount .../mmcblk etc.. which means the device is there just the partition is hosed..
[Galaxy S I9000 Q&A, Help & Troubleshooting] madmack:
That may be the case. It really depends on error message that you receive. Refer to my post earlier (post #35) for the difference between the two types of errors.

Most people that returned the device when they received the "not found" error got their motherboards and/or internal sdcards replaced.

I can't wait til I receive my unit back. so hard to live without any of these now!

*patience* *patience* lol
[Galaxy S I9000 Q&A, Help & Troubleshooting] rmanaudio:
OK guys...I PM'ed Richthofen, who I think is a samsung internal friend of the XDA. He is the person who leaks ROMs at times....Anyways, I asked him about this SD internal issue and here is his response:

The I9000M phones are made in the same production lines with I9000 phones (sold worldwide).

I would recon it is a firmware issue.

Either the bootloaders have broken wear leveling (which make the MMC blocks die too fast) or something else is wrong with the firmware.

If this is the case I would replace the bootloaders on the phone (3-button fix will do it) and use firmware made for I9000.

The modem code needs to come from I9000M, eventhou it would work with I9000 modem too (both use same baseband). The bands however are different.

--

Best regards

Roger

So it looks like a firmware issue. My phone did come with 3-button fix working on it so it must have the new bootloader, this might be the reason why mine has lasted 2 months now.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Electroz:
2 months with Froyo?
[Galaxy S I9000 Q&A, Help & Troubleshooting] Uss_Defiant:
Dont put too much stock in that, I had a working 3button i9000m from bell which got bricked after flashing froyo.
[Galaxy S I9000 Q&A, Help & Troubleshooting] rmanaudio:
No, no froyo..im on the stock JH2. Do not flash froyo that is not build for the i9000M as it looks like it will kill it. So this proves that it is the firmware doing all the killing!

I'm putting all my stock in it. The source is not just some guy. He is crediable on XDA and is the only leaker we know. So, he must know something.

But, I dont think we can flash just any I9000 internation firmware on our i9000M, there must be some differences as the Froyo's are killing the i9000M.
[Galaxy S I9000 Q&A, Help & Troubleshooting] floored24:
That doesn't make sense, the poll clearly shows stock jh2 frying as well. Mine is still alive running jh2 with oclf but Im just counting the days to failure, and when it does up for sale she goes after fix and hello desire z
[Galaxy S I9000 Q&A, Help & Troubleshooting] rmanaudio:
There is a lot of stock JH2 running without the new bootloader that fixes the 3B recovery...so maybe that could be it. We need to find out how many stock JH2's with 3B working have died and if they did anything like flash it with something before it died!
[Galaxy S I9000 Q&A, Help & Troubleshooting] xZeDgEx:
I was stock jh2 when mine died. Ticket said hardware was replaced. So no I dont think it is firmware. The phone is a cheap pos is more likely the issue.
[Galaxy S I9000 Q&A, Help & Troubleshooting] laggo:
I was running stock jh2 with working 3 button. My phone died after 1.5 months. I did run OCLF for about 2 weeks before i removed it and unrooted my phone. about 2 weeks after i dropped OCLF my phone died.

unable to mount /dev/......

tried odin with stock jh2 and 512pit, it would flash okay but still no boot, and same mount error.

just took it to bell today, off to samsung it goes!
[Galaxy S I9000 Q&A, Help & Troubleshooting] wang1chung:
i agree with it being a firmware issue, but i have had the 3button fix on my phone since it was released (my phone was originally neutered) and mine still died within 1 hour of loading froyo, so i don't think the updated bootloader "protects" the sdcard.
[Galaxy S I9000 Q&A, Help & Troubleshooting] TriC_101:
This is very true.. the only differences between the i9000 and the i9000m is the radio chip on ours is for 850mhz band and the i9000 is 900mhz.. everything else is the same... same internal SD in the i9000 and the rest of the world as the i9000m

Also the fact I somehow got mine working by flashing alot of different Roms.
[Galaxy S I9000 Q&A, Help & Troubleshooting] daft.71:
Mine died and I had the 3B when I bought it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] devonblue4u:
YeeeeHaaaaa!!!

First off, my I9000M was running 2.2. Lags, the occasional hang, etc. But it was running. Although I hesitated at first on installing one of the lag-fixes, I installed OCLF. Instant BSOD. I have to admit that the freezes and the re-boots were coming at least once a day the week prior to installing OLCF. And Froyo ran for 1.5 months prior to that. My assumption is it was the phone's last gasp, SD card wise.

After numerous flashes with every rom listed in this thread (better than a soap opera's triumphs and tragedies..), web searches, file downloads, phone calls to bell/bestbuy/samsung, sacrificing chickens....I gave up for about 2 weeks.

Bored one day, I picked up the phone and tried calling around to see if I could song and dance around the fact that I had no reciept (craigslist...save the comments, I already know how stupid that was), a store manager suggested a shop.

I called around, and after 2 tries I got a quote for the motherboard.....65 bucks installed, 2 days turn around. Results; picked up the phone yesterday, works like the day I got it!

Moral of the story; I have modded my last SGS. This thing is not as robust or as well thought out as my old iPhone 3G. Blame the hardware or TW, it doesn't matter. My SGS was down for a month while I still paid Bell about $75 for my plan. $72 more (repair + taxes) is a lesson well learned.
[Galaxy S I9000 Q&A, Help & Troubleshooting] madmack:
which store might that be :D
[Galaxy S I9000 Q&A, Help & Troubleshooting] deadly0ne:
I would also like to know which store you have got this phone repaired. That would help myself and many others from the trouble of not being able to get it fixed or have no receipt. :D
[Galaxy S I9000 Q&A, Help & Troubleshooting] d3a:
got mine back from bell from repair... let the countdown begin for this thing to fry again :(
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllGamer:
install lag fix

i want to see it die again with lag fix :p

if it doesn't die, then everyone should get their phones replaced
[Galaxy S I9000 Q&A, Help & Troubleshooting] devonblue4u:
the best thing to do is phone around in your area to see who's capable of replacing a MB at a reasonable price. I'm just saying it's possible. And I don't know how long this fix will last, as I just got it back yesterday. This way I'm not promoting a store at all (and the blame that goes with it.). Maybe there should be a poll on the average price of fixes out of warrantee (i.e, we craigslisters), so those who don't have a receipt know what they're up against.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Yeria:
My phone is working fine since the day of purchase so far, and I just wanted to share my information/experience so you guys can compare. I tried to write down every possible relevant information I could think of...

The date of purchase: September 13th, 2010 (from the receipt)

Bought from: A Bell Store

Battery manufactured date: August 27th, 2010

The last two digit of IMEI: 04

Has applied lag-fix(es): No

Has flashed any firmware: No

Firmware version: 2.1-update1

Kernel version: 2.6.29 darae.ahn@sep-20 #2

Build number: ECLAIR.UGJH2

3B recovery mode availability: Yes from the beginning

Rooted: Yes (I think? I unlocked it by following instructions from this board)

Unlocked: Yes, with Rogers

Apps usage: Heavy, 100+ apps installed, using 425MB of 2GB space

Internal SD usage: Light, ~6GB, mostly movies, watch them about 1 hour a day on average (commute)

External SD usage: Heavy, 6~7GB, mostly MP3 and pictures

Other information: I almost never shutdown my phone unless I have installed 5 or 6 apps in a row and became a bit too slow to my liking. My phone almost always have 40 or more hours of uptime.

As a software developer, I try to start investigating issues by comparing detailed information/specifications of the broken system against functioning systems. The problem is, often such comparison is difficult because nobody really provides them in detail. I have no experience with mobile development, but I felt it couldn't be too different from any other development environment...and I think my information should be able to help some.

If you have any other question or have additional information you would like to have, just ask me...I'll post them again as long as I can find them.
[Galaxy S I9000 Q&A, Help & Troubleshooting] kcmarus:
anyone know of a place to get the mobo fixed? (Vancouver) Im in the same boat as devonblue and a few others with a messed up internal sd and no reciept.
[Galaxy S I9000 Q&A, Help & Troubleshooting] karakake:
Got mine back today. Mainboard has replaced. Will apply lagfix and root again.

My repair completion paper is from a Samsung certified service center in Richmond,

called Future tech. You might wanna call them and see if they can fix it at a cost..
[Galaxy S I9000 Q&A, Help & Troubleshooting] devonblue4u:
since I'm getting PM on this one, I'll post a link. Remember, as with the comments by others on flashing, don't blame me. It's just a link.

http://jpcellrepair.com
[Galaxy S I9000 Q&A, Help & Troubleshooting] cyfawcett:
Future Shop

I bought mine at a future shop on Sept 15 and Samsung said I need to take it back to the provider (Bell), but Bell isn't my provider. The internal SD card is totally fried and I have no idea how to fix my phone.

1. Anyone know if I can get Future Shop to send it in for warranty replacement?

2. Is there somewhere in the Toronto area (East side) that I can get the motherboard replaced? If so, does anyone know how much it will cost?

Thanks for any assistance.
[Galaxy S I9000 Q&A, Help & Troubleshooting] plemen:
I think you mean FutureTel:

http://futuretel.ca/

These are the guys Bell sends the phones to for repair.
[Galaxy S I9000 Q&A, Help & Troubleshooting] cyfawcett:
No I mean Future Shop as that is where I bought my phone at full retail cost, but I am not using Bell as a provider (I use Fido). I don't use Bell for wireless service, but I'm going to have to try to get them to send the phone back to Samsung to repair; which will probably be completed by Futuretel, but who knows for sure really?
[Galaxy S I9000 Q&A, Help & Troubleshooting] contalyst:
There is an extension to 60 day DOA policy for the SGS, you may be able to talk future shop into honoring it. The fine print does say that the phone had to be brought into the retailer before the initial 30 days was up...

I returned my first SGS about 40 days after I bought it and just told them I was in trying to show a random employee my problem with the phone but it was miraculously working that day. They eventually honored the DOA policy and I'm on my 3rd one now. The second I returned the same day as the problems i had happened straight away.
[Galaxy S I9000 Q&A, Help & Troubleshooting] YG007:
I just got my phone back. Mobo was replaced. Flashed JP6 on it... seeing how long it will last.

I'll keep you guys posted.

This time around, the new mobo had the 3 button recovery.

I applied JPK with overwriting the bootloader in Odin AND repartition.

Then I applied JP6.

Root, NO lagfix, my personal ringtone mod, TWlauncher landscape mod.

Made a CW backup.

Did a Factory Reset.

Formatted the internal SD via the settings menu, 3x.

Hopefully this one will last longer than a week.
[Galaxy S I9000 Q&A, Help & Troubleshooting] tylerham:
Is there a way to / can a mod reset the poll?

It would be interesting to have everyone update their votes one month later. Mine changed (from 2.1 lagfix and working to 2.2 no lagfix and dead.)
[Galaxy S I9000 Q&A, Help & Troubleshooting] Vaanhoot:
Hey cyfawcett, I was in the same boat as you, bought my phone at Best Buy outright and unlocked it to use it on Rogers. My internal sd went and I just took it back to Bell and told them I was using it as a PDA. They had no problem with sending it in for repair. Just make sure you don't leave your fido sim card in it, just put the bell one that came in the box back in it. Still waiting to get it back.
[Galaxy S I9000 Q&A, Help & Troubleshooting] cyfawcett:
Hey thanks for the advice! I'm going to try that in the morning! Will post my results!

Cheers Bro!
[Galaxy S I9000 Q&A, Help & Troubleshooting] cyfawcett:
Thanks for the advice! I'll try that first, and go to Bell if they won't help me out.

Cheers
[Galaxy S I9000 Q&A, Help & Troubleshooting] thedauntlessone:
Hay guyz I thought it's a software issue why are mainboards getting replaced? /sarcasm.

Wang and everyone else out there, stop spreading misinformation.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Vaanhoot:
All the best. Will keep you updated with what happens to me as my phone was running JPM firmware and was unlocked when the internal sd went. They sent it away over a week ago and still haven't heard anything. The said they would contact me soon if out of warranty work had to be done (problem was caused by me) and no call yet. The phone wouldn't boot so maybe there is no way to detect that I was running unofficial firmware.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Dark4eons:
I got my i9000m back yesterday, took about 2 weeks, no details on the work though, I was too glad to have it back, compared to the loaner I had (lg xenon) this phone is sooooo much better
[Galaxy S I9000 Q&A, Help & Troubleshooting] wang1chung:
hey bud, why don't you relax, and read the threads. i am merely stating what i have read in this thread and others related to sdcard failures. not EVERYONE is having their mainboards replaced, some are having a simple reflash done.
[Galaxy S I9000 Q&A, Help & Troubleshooting] thedauntlessone:
When you start pointing fingers and telling people to read the thread, at least read the thread yourself. There were plenty of mainboard replacement confirmation EARLY IN THE THREAD and I was there when this whole thread started. Also, there were only 2 or 3 people who came here and said they got a software reflash. Maybe they had a different problem, maybe not.

Further yet, you seem to think this reflash is "simple." If it is this simple, someone would've done something LONG time ago. The people over at samsung reflashing the phones are probably using the developers kit to access the phone differently to reflash and repartition the phones. These devices are state of the art and dev kits are not cheap. Unless samsung themselves repackage this flash for us (which is extremely unlikely, may even be impossible), we will probably never get to do this ourselves.
[Galaxy S I9000 Q&A, Help & Troubleshooting] wang1chung:
fair enough, it is not a simple reflash. i meant simple in comparison to ripping apart the phone to replace the motherboard, but whatever, still the wrong choice of words.

but i never said you had a 100% chance of fixing your phone with a reflash. i said there was a chance it was only a corrupted sdcard that could be fixed by flashing, otherwise you'll probably have to have the motherboard replaced.

and you started pointing fingers at me first btw.
[Galaxy S I9000 Q&A, Help & Troubleshooting] TriC_101:
I fixed my phone by flashing new roms.. don't know what I did but it worked and I have flashed my phone over 20 times since then without an issue.
[Galaxy S I9000 Q&A, Help & Troubleshooting] smacman:
Which mount error were you seeing? Was it sd...... Or mmcblk....?
[Galaxy S I9000 Q&A, Help & Troubleshooting] jark99:
anyone got any success returning this phone through Bell without a receipt???...

im going to samsung service center on tuesday in missausaga to see if i can directly get it fixed....hope it works.