(New After JK4 Froyo) POLL:Bell I9000M Internal SD Failures

[An Droid]

I think we need a new Poll for anyone that needs to change their answer after upgrading to JK4...Perhaps give JK4 a few days to make sure it's running smoothly before voting...

(Thanks Electroz for the original Poll!)

 

[trinitonesounds]

I got to experience 5 minutes of froyo before multiple force closes and then dead. It went into a reboot loop never getting past the white i9000m logo.

Updated with Kies (latest version--no registry mod)
I was stock JH2.
No lagfix ever installed
I've never flashed any rom.

Sorry guys, Kies is not safer...

Now I have to convince Bell to honor the warranty...

 

[dm-digital]

I don't think there are any issues with Kies or Odin for flashing. I've flashed many times, sometimes 4 times in one day and I've never had any issues. There does seem to be the usual SD issues but I also think there is a USB communications issue. There have been many reports of data corruption while writing to internal/external SD with large files. I personally had an issue pulling large files off of internal/external SD. I think if this problem occurs while flashing new firmware it could cause some corruption that could be noticeable right away or after a bit of use. The partitioning on this device seems to be more sensitive than others and a hiccup while flashing could cause some major issues.

 

[miniflight]

I got to experience 5 minutes of froyo before multiple force closes and then dead. It went into a reboot loop never getting past the white i9000m logo.

Updated with Kies (latest version--no registry mod)
I was stock JH2.
No lagfix ever installed
I've never flashed any rom.

Sorry guys, Kies is not safer...

Now I have to convince Bell to honor the warranty even though I'm on Rogers...

They don't care.

I went today and they just took it and didn't ask anything that sounds like they cared about if I am not with Bells.

I gave them my bro's phone number and info since he is with Bell, just to avoid any problems.

Just don't say something like the phone is "unlocked" lol...the phone is dead so they won't find out anyways if you don't tell them. They won't ask either.

Just tell them that you upgraded through kies and it got the problem.

 

[AllGamer]

it's a hardware defect, if it dies it dies

after all the evidence we've seen (all the reports by our members)

if it's good it will work regardless of what firmware you use, and regardless of the way you flash the firmware

the lag fixes and froyo just accelerates the problem and makes it more evident sooner than later

which is good in a way, it's better to find out before your warranty runs out

 

[evil-doer]

ok im pretty sure mine is a full brick. maybe you can tell me.

less than 24 hours after updating to 2.2 i started getting all of these errors in various programs, so i rebooted the phone, but after it plays the little intro thingy the screen just goes black and thats it. cant do anything else. i tried a factory reset and still the same thing. so is that it?

also. i bought this phone at best buy, but network unlocked it to use on rogers. should i be contacting samsung directly about a replacement/fix? anyone here done that? im REALLY scared that are gonna give me a phone that i am unable to network unlock.

thanks for any info.

 

[AllGamer]

some one welcome me to the club of defund Bell Internal SD

http://forum.xda-developers.com/showthread.php?t=867157

 

[hotdoggie]

@evil-doer

I am in the exact same boat as you! I bought from Best Buy, then unlocked to use on Rogers. Last night, I updated to official Froyo through Kies, and then it just died on me today (many app force closes and then just drop dead). When I get into recovery mode, it says can't mount the SD card.

I think I will just go to a Bell Store tomorrow and see what happens. I will let you know how it goes. Please let me know how yours go too. Thanks.

 

[jdrom]

Mines a goner too

Same issue, have a forced app closure, shut the phone off and it wouldn't start up anymore. Just flashes the Galaxy S GT-I9000M white logo non-stop now.

I can put it into download mode and load up 2.1 (stock) and get to the coloured Galaxy S logo, but then it just goes to a black screen. In recovery mode, it shows stuff about not being able to mount the SD on E:\. I'd assume that's the internal flash?

Luckily I haven't had it for >30 days (on Virgin Mobile) so I'm hoping I can just exchange it and be on my way. I have to call them though apparently since I bought it online.

 

[AllGamer]

i did not have Force Close, the phone just got really really hot during batch restore of TitaniumBackup

 

[newf007]

Mines a goner too

Same issue, have a forced app closure, shut the phone off and it wouldn't start up anymore. Just flashes the Galaxy S GT-I9000M white logo non-stop now.

I can put it into download mode and load up 2.1 (stock) and get to the coloured Galaxy S logo, but then it just goes to a black screen. In recovery mode, it shows stuff about not being able to mount the SD on E:\. I'd assume that's the internal flash?

Luckily I haven't had it for >30 days (on Virgin Mobile) so I'm hoping I can just exchange it and be on my way. I have to call them though apparently since I bought it online.

how did you load up 2.1? i can put my phone in download mode but nothing happens after that. and how do you get in to recovery mode?

 

[jdrom]

Well I can load up 2.1 with Odin and with the auto reboot option checked, it'll go straight to recovery mode after flashing (for whatever reason). Otherwise I can't get to recovery mode.

 

[jflaplante]

Success so far... 12 hours after upgrade.

I sucessfully upgraded to Froyo yesterday.

I had problems with Kies at first and had to do a factory reset before the upgrade. The FileSearcherforKiesFix.exe altough it detected two bad files wasn't enough to make Kies happy.

This phone was bought in october and had the voodoo lagfix installed from the begining. I disabled the lagfix before the froyo upgrade.

My previous samsung phone; the GT-8000 (Omnia II) did have an internal SD card failure after a few months of operation... Also a Bell phone. I'm really concerned by that trend with Samsung and Bell...

 

[nemethb]

I recommend NOT to upgrade. With JH2 I had NO problems. I upgraded to JK4 and about 24 hours later (this morning) I started getting force closes. XDA App. wouldn't open and just scrolling through memory management gave me haptic feedback (even though I had it disabled) and random closes. The phone became unusable fast. I tried a reboot and the phone booted to a black screen where only the buttons lit up. I went into recovery mode and I saw some dbdata error. I figured my phone was a goner. I ended up formatting the internal memory, clearing cache and then doing a factory reset. The phone is up and running now...but for how long.

 

[plemen]

Well... you're going to have upgrade eventually so best to do it now while you are under warranty in case something happens...

I recommend NOT to upgrade. With JH2 I had NO problems. I upgraded to JK4 and about 24 hours later (this morning) I started getting force closes. XDA App. wouldn't open and just scrolling through memory management gave me haptic feedback (even though I had it disabled) and random closes. The phone became unusable fast. I tried a reboot and the phone booted to a black screen where only the buttons lit up. I went into recovery mode and I saw some dbdata error. I figured my phone was a goner. I ended up formatting the internal memory, clearing cache and then doing a factory reset. The phone is up and running now...but for how long.

 

[nemethb]

How's that the case?

 

[beng2k]

Stock JG9 w/ OCLF -> Stock JH2 (kies,voodoo lagfix) -> JK3 (Odin, Speedmod kernel w/ tweaks flashed through odin to get 2e back, no lagfix) -> JK4 (hacked kies, speedmod kernel w/ tweaks flashed through odin to get 2e back, no lagfix)

No SD failure so far, touch wood. Original phone purchased day after launch.

 

[CADmonkey]

Mine died today, started getting FC and then the whole thing froze. I tried restarting it but after the samsung splash screen all I had were glowing buttons.
It ran fine for about a day on JK4 before that on JH2 it never gave any problems.
BTW it was stock updated through Kies.
The guy at the Bell store told me they never get these phones returned, this was a first for him. Either it was his first day on the job or it's typical Bell BS.

 

[spydr11]

Just had my second phone die. The first one died after 28 days with no upgrade. This one after 8 days, 2 days after upgrading to Froyo...

 

[bestbeancounter]

Same thing happened to me this morning.. Froyo was working fine for just over a day and then this morning I turn on my phone, get a bunch of FCs.. I reboot.. get another bunch of FCs.. reboot.. and now it won't go through the "S" splash screen. When the screen disappears I press the buttons and it just glows..

I don't know if it's bricked or what.. when I run recovery I get this error.

E: can't mount /dev/block/mmcblkOp1 (I/O Error)
E: Copy_dbdata_media:can't mount SDCARD:

your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.

Is this what everyone else is getting? And what are my alternatives?

If my phone is pooched then I'll be pretty pissed since this is my 3rd SGS, I gave the SGS up when it had issues in low reception and the 850 band lock fixed it. If this totally pooches my phone I'm never buying another Samsung mobile product again.