[Vibrant Q&A, Help & Troubleshooting] Geovanni Galaxy:
Help ...on my third phone!

Hey I have the Bell Vibrant which by U.S. standards is not really a Vibrant at all. It's the GT-i9000M model and seems to be similar to the European Galaxy S.

I AM ON MY THIRD PHONE!

The first two bricked with the same "E:can't mount..." error

I was clueless when it first happened and felt useless with the tech support both Samsung and Social Hub had to offer. The second time it happened (within 2 weeks) I tried downloading the compatible files from Samsung's download page and followed the steps according to this thread. There must have been a USB problem because Odin started the process but froze during initialization. I tried this numerous times without luck so brought it back to my provider. I'm a computer tech guy and not being able to fix this really ****** me off!

I'm on my third phone now and want to take preventative steps but not sure how. From brickage experience I know what the cause has been. Unlike people who have encountered this issue during the 2.1-2.2 update. My problem has been with 2.2. I was unlucky enough to purchase my phone the day 2.2 was released. Each replacement already had 2.2 on it. This problem is lurking on every GT-i9000M v2.2 owners phone and can erupt at anytime. (

Not just during the firmware update

)

Issue specifically with the GT-i9000M:

The internal SD mounting issue (after successful update) is caused directly with the network connection software portion of Froyo 2.2. Most people have not experienced this because they have an active data plan and have not turned off data, packets and roaming within the phone's system settings. (I shut down all data connectivity allowing only for Wifi since I have access at home and at the office. I have no need for any internet access elsewhere.) Both phones crashed to a black rebooting screen loop with no recovery possibilities (...can't mount error) while a stock app was trying to access a background network connection where none was available. If your phone also crashed "to an un-mountable sd card black screen loop" under normal operation ask yourself what it was you were doing at the time ...most likely some program on your phone was trying to access a network.

Now I am very cautious about apps which may spontaneously search for a connection when WiFi is not available. This has left me very paranoid because this can easily happen again and Samsung as not addressed the specific issue and doesn't have any plans to do so. The superiors I have spoken with have lead me to believe it's up to Android to fix the problem although this is specific to the GT-i9000M model.

Sorry for the long post ...This is what happens when stress kicks in.

Questions:

1) Are the rooting files listed in this thread compatible with the GT-i9000M?

2) USB debugging was turned off prior to each crash ...could this be why Odin was unable to initialize? (I noticed the crash did not effect any call settings so believe the last known USB settings might be functional)

3) Is there a preventative rooting fix I can do before this happens again?

(All three phones have had the same kernel =

2.6.32.9 shout.lee@SEP-09#1 build number: FRYO.UGJk4)

***I'd like to find Mr. Lee and shove my phone up his ***

4) Are there any different GT-i9000M/I9000UGJK4 compatible kernels with Froyo 2.2?

5) Is Froyo 2.3 an official update and will it address the issue I'm dealing with?

I love the phone when it's functioning but right now it has been bricked for longer than it has been operational.

Any information is greatly appreciated,

Geovanni