• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

How is your Bell I9000M?

  • Internal SD Dead - UGJG9/UGJH2 Firmware/No Lagfix

    Votes: 21 3.4%
  • Internal SD Dead - UGJG9/UGJH2 Firmware/With Lagfix

    Votes: 13 2.1%
  • Internal SD Dead - Other 2.1 Firmware/No Lagfix

    Votes: 6 1.0%
  • Internal SD Dead - Other 2.1 Firmware/With Lagfix

    Votes: 2 0.3%
  • Internal SD Dead - 2.2 Froyo Firmware/No Lagfix

    Votes: 253 41.1%
  • Internal SD Dead - 2.2 Froyo Firmware/With Lagfix

    Votes: 81 13.1%
  • Still Working - 2.1 Firmware/No Lagfix

    Votes: 21 3.4%
  • Still Working - 2.1 Firmware/With Lagfix

    Votes: 6 1.0%
  • Still Working - 2.2 Froyo Firmware/No Lagfix

    Votes: 152 24.7%
  • Still Working - 2.2 Froyo Firmware/With Lagfix

    Votes: 61 9.9%

  • Total voters
    616
Search This thread
Sep 20, 2007
13
2
Abbotsford, BC
I got to experience 5 minutes of froyo :rolleyes: 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...
 
Last edited:

dm-digital

Senior Member
Jan 6, 2010
97
1
Orangeville
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

Senior Member
Nov 15, 2010
130
5
I got to experience 5 minutes of froyo :rolleyes: 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

Retired Forum Moderator
May 24, 2008
11,894
1,647
SGH-T989
AT&T Samsung Galaxy Note I717
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

Senior Member
Aug 4, 2010
408
27
Ontario
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.
 

hotdoggie

Member
Aug 23, 2010
15
0
@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.
 
Last edited:

jdrom

Member
Dec 10, 2010
42
2
Toronto, ON
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.
 

newf007

New member
Aug 12, 2010
4
0
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

Member
Dec 10, 2010
42
2
Toronto, ON
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

Member
Nov 17, 2009
14
2
Sherbrooke, Québec
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...
 
  • Like
Reactions: xedd

nemethb

Senior Member
Aug 22, 2010
208
3
Ottawa
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

Senior Member
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.
 

beng2k

Senior Member
Jun 20, 2007
70
7
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.
 
Last edited:

CADmonkey

Member
Aug 23, 2010
8
0
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

Senior Member
Oct 25, 2010
59
4
Edmonton, AB
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

Senior Member
Sep 2, 2010
67
0
Calgary
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.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Nice, some ****ing clowns here are scamming Bell and are looking for our help.

    Here's my offer - I'll personally brick your phone by shoving it so far up your ass you'll have to puke it out your mouth.

    ****ing morons.
    4
    Legal Recourse

    The nightmare of the defective Galaxy S Vibrant sold by Bell is not going to end any time soon. Bell blames Samsung, Samsung blames Bell, and at times both blame the customer.

    But, customers in Ontario and likely in other provinces have rights under consumer-focused law.

    In Ontario there is the Sale of Goods Act. A retailer is liable to a purchaser for a defective product. From the Osgoode Hall Law School, York University www site:

    "...The legal standard is that goods must be merchantable and reasonably fit for their purpose. This includes an implied durability test; that is to say, if a product with an expected life of five years breaks down after 14 months, then it likely was defective at the time of sale. Depending on the particular facts, a consumer may have a right to reject (return) the goods for a refund or keep the goods and recover damages which would be equivalent to the cost of a repair. Under section 9 (3) of the Consumer Protection Act 2002 these obligations of the retailer may not be excluded or waived when selling to a consumer. Any attempt to do so is of no legal effect. Retailers therefore have primary legal responsibility to purchasers. "

    Bell typically retails the Samsung Galaxy within the terms of a 3-year contract. Bell expects the Galaxy to be durable for 3 years. So we can assume that if this product breaks down 4 months after the sale, it was defective at the time of sale (IIRC, the sale of the Galaxy S began in August 2010).

    I believe the Galaxy S Vibrant sold by Bell is a defective product. There is overwhelming evidence that a significant number of unflashed, unrooted, and otherwise untouched Galaxy handsets become bricked. It is unsalvageable by the customer.

    If you purchased this phone and it's broken, you should go to your retail point of purchase and demand a complete refund.

    (I am not a lawyer, and nothing in the above should be construed as giving legal advice. Contact your own lawyer or consumer protection agency).
    3
    just sent the following to engadget, gizmodo, google, and jame myers (a bell vp)

    Hi,

    I am writing to report a growing issue with Samsung Galaxy S phone sold by Bell Mobility in Canada. The code name of the model is I9000M and it is branded as Galaxy S Vibrant by Bell.

    My Galaxy S experience was much less stellar than what most reviews had indicated. Before going into the discussion of grief, here is a comic relief: Someone has made this analogy - Samsung Galaxy S phone is like a very hot girlfriend who treats you badly and toys with your emotions; and yet, you still want to keep her mostly because she is just so damn hot.

    I will go into details momentarily but in essence the issue is that this Galaxy S model fails at startup due to internal SD card not being mounted (a dead phone). This issue is affecting more and more users on a daily basis. I will provide links to some of the forums where users have been reporting the same issue. I am hoping that, by reporting to you the trusted news source, this issue can get a wider coverage and awareness can be raised for current users and potential buyers. And, ultimately, affected users in Canada will get an in-depth answer/analysis and proper support from Samsung and Bell.

    Here are a couple of links to the forums where this issue was reported and discussed:

    http://forum.xda-developers.com/showthread.php?t=868569
    http://www.samsunggalaxysforum.com/index.php?topic=2377.0

    First, in order to give myself some credibility/qualification as a backup to my claims and analysis based on my research, I would like to provide a little bit of my background:

    I am a lead developer of a world-class, very successful financial software. I have been designing and writing software for over 15 years. I consider myself very technically savvy.

    * The Issue:

    I bought the Galaxy S phone late October this year. As aforementioned, my experience with the phone had been frustrating and disappointing. It was always laggy and at times very sluggish.

    Last Friday, Bell pushed out the Android 2.2 (Froyo) firmware update. After updating it with Froyo, my phone ran okay on Saturday, although it was already acting up - more occurrences of Force Close, slow loading of applications and frequent reloading of home screen.

    Finally, on Sunday, Android Market stopped working so I rebooted my phone. Upon startup, after the Samsung logo/intro, the screen went black and the phone could no longer boot up. Subsequent reboots resulted to the same black screen. By going into recovery mode, it showed that the internal SD card had become corrupted and could not be mounted. This was preventing the Android OS from continuing to load.

    Prior to the failure, I have never rooted my phone, applied any lagfix, and used any firmware. I am completely honest on this.

    * My Research and Analysis:

    First and foremost, let me admit that I am new to the Android platform and my research has been limited so far. However, because of my technical background, I believe my analysis does carry some truth.

    For Bell's variant of Galaxy S (Vibrant/I9000M), it has an 16GB internal SD card, built-in and, I believe, soldered on the motherboard. It is my strong belief that the SD card used in this Canadian model is of low quality and defects. Even when I was doing the initial research on the phone prior to my purchase, I had read reports about corrupted internal SD cards. I thought those were just isolated cases and how wrong was I! (I chose Samsung Galaxy S mostly based on the universal glowing reviews on the phone.)

    By updating to Froyo, I believe it triggers the SD card issue sooner and in a more direct way, unfortunately.

    My research continues. It turns out that the current Android OS relies on an SD card for caching. It seems an SD card is required. Coming from software development myself, I question this requirement. This should have been an option. However highly recommended (for optimization and speed), this shall remain optional.

    From what I read, Samsung implemented the low-level I/O interface to SD cards. This also shocked me if it is true. Why would Google allow a third-party hardware manufacturer to implement such a core component of Android? I would not completely trust a non-software-centric company to build software.

    Samsung's implementation was to use a very old (possibly obsolete) file system called RFS to manage I/O calls from/to SD cards. According to tests/debugging conducted by other Android developers, this RFS implementation is faulty and creates a lot of I/O errors. Because of this inferior file system and the huge amount of error logs it writes to the SD cards, the SD card is more prone to wears and breakdowns, which makes the phone a ticking time bomb.

    * Summary and Final Thoughts:

    This SD card/dead phone issue appears affecting users mostly from Canada, which is the only country issuing the I9000M model. The problem seems to be a result of a combination of faulty SD cards and inferior software implementation.

    As a developer, I am deeply disappointed and frustrated with the Android platform. I will not recommend any Android device to anyone as a consumer product. And, from my own experience and due to the fragmentation of the platform, I would not recommend Android to my boss as a viable business platform. My Android experience so far has been very similar to that of Microsoft Windows - Android will be buggy for a long long time and supporting Android devices will be an utter nightmare (just ask any Android developer: how many devices do you have to test with your apps? how many users bad-month your apps because they don't work with a particular device?).
    2
    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!)
    2
    I received a reply from Chris Olsen from "Olsen on your side" from CTV.

    My Email to Chris:

    Dear Mr Olsen

    Bell released a high-end android phone a few months ago from Samsung, the Galaxy S Vibrant. There are major issues with this phone that are not being addressed by both Bell and Samsung. Something is wrong with the internal memory (on board SD memory) and it is becoming corrupt. This causes the phone to no longer boot and becomes non-functioning . The only way to fix this issue is to replace the entire mainboard.

    Here are 2 threads on a very popular Android forums about this issue.

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

    Here is a link to a online petition that has been setup.

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

    I myself have my phone in for repairs, the expected wait times are 4-6 weeks. When I asked for a loaner phone the Bell employee told me I had to rent one for $25. The phone I would receive is a regular non-smart phone. I am unable to suspend the data portion of my account for the duration of the repair times. Therefore I would end up paying for data that I could not use.

    There have been hundreds if not in the thousands of users who have had replacement phones. Some have had the phone in for repairs longer than they have actually had it in their hands. Some have multiple replacements. The repaired phones are no better than the originals, they can die anytime.

    There are many models of the Samsung Galaxy S, and the only one to have this issue is the Bell specific version the i9000M Bell Galaxy S Vibrant.

    We, Bell Galaxy S users, would love some help with this issue. We are a small non-influential group of people who are getting ignored by two big companies.

    Thank you for your time,



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

    Chris Olsen's Response:

    Contact the commissioner for complaints for telecommunications services to ask about the compensation issue.

    In my view bell should give you a free replacement – and then charge Samsung for that.
    The phone is samsung’s issue – but you are a bell customer and bell should go to bat for you in my view

    By the way I had someone sho had this problem – and after a few attempts at fixing it – it appears Samsung has finally got it right so
    When you get it back it should be okay – but let me know

    Chris O



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


    I have emailed him back again and hope to hear more!