• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Froyo Update (Bell) fried internal SD

B

bentonius

Lurker
I'd heard rumblings about the internal SD (basically a partition) on the Galaxy S being a bit fragile. Anyways, I update to Froyo earlier today, things were going along swimmingly. I had only had the update installed for about an hour before I brought my phone out of lockscreen to briefly glimpse the little red error sign in my notification bar for about 2 seconds, then the phone shut off. I turned it back on, it booted to a blank screen. Of course, tried booting a few times, then yanked the battery for 5 minutes. Same result.

Not one to panic, I went online to look up the 3-button recovery steps. I did both the factory reset and the cache partition clear. Boot, nothing. I did notice that sometimes the menu and back buttons would stay lit. This hinted that the internal SD was cooked. Damn. So I'm going into the Bell store tomorrow, and I'll make sure to wear my rage pants.
 
Exactly same thing happened to mine but it lasted about 12 hours with 2.2. Contacted bell and they said bring it in for repair.
 
Same thing happened to me. I lasted 15mins on 2.2. I get the can't mount sdcard error nothing works.

But I bought mine off kijiji. I dont have a warranty.

Anyone have any suggestions?
 
I took it to Bell, so here's the update.

I took it to my nearest Bell Store, they brushed it off as needing the reset. I just let them have their fun, because really, even if you had built this phone with your bare hands they would still go through the motions. So, it didn't work. The guy gets out his blackberry and starts scrolling through this gigantic email. It tells him more of the same, so he calls up another, bigger location about 30 minutes away. He gets off the phone and goes "could you drive to [other store] right now? It needs to get fixed, we have no loaner phones, they have one which they're holding" Sigh, ok.

I drive up there, get taken back to the service desk. There are already 2 galaxys sitting on the desk with their warranty paperwork. At first the guy didn't understand that a loaner was on hold, told me they were getting a bunch in on Monday.

All this has led me to believe that Bell is going to take this on the chin and just start having to fix a ton of these phones. Obviously, if your phone has broken, take it in quickly, because the service waits might just keep getting longer.
 
Took mine in today. The guy had it ready to go out for repair in minutes as it was the 5th galaxy s on warranty today for him. No loaners left of course.
 
I had the same thing happen on my first vibrant... it bricked in a few days of use. Wtf. Anyways, I returned to the shop and I'm on my second one now. I re-updated to 2.2 thinking it was another problem before I found this thread... omg I hope my second one doesn't die.
 
It took two weeks for mine to fry. During those two weeks various applications died at random times though. Reinstalling the app would do nothing to solve the issue. Brought it in today and got $100 credit. Helps offset the $25+tax it cost for a loaner phone and the $50 deposit for the repair order. Don't settle for less than a $100 credit.
 
i upgraded to 2.2 three days ago,
it ran perfectly, what is the chance for a vibrant to have bricking problem????
( it is a bell Vibrant unlocked , using on telus network)
 
Hate To seem like this is rude...

BUT

This is the Samsung Vibrant Forum AKA T-Mobile Galaxy S

NOT THE CANADIAN BELL PHONE NETWORK GALAXY S FORUM

They only share the model name in common and a few of the internals

And as much as I sympathize with the upgrade problems BELL Galaxy S phones are having your asking for help in the wrong place!

Below is the link to where your help is Definitely Gonna Be had!


Samsung Galaxy S - Android Forums

We vibrant people have yet to get our update to 2.2! :mad:

Good Luck!
 
You must log in or register to reply here.
Back
Top Bottom