[Q] Bell 2.2 upgrade and internal SD failure

Search This thread

deezy7

Senior Member
Oct 30, 2007
213
6
GTA
Yea this just happened to me...argh

No way.

Please tell me you're lying....I avoided all 2.2 roms because if my phone dies, I'll die.

or else, PLEASE tell me you had some lagfixes or other stuff installed!

I'm running completely stock on Rogers, and just upgraded via Kies, no registry hack, about 30 minutes ago. LOVING Froyo!!
 

miniflight

Senior Member
Nov 15, 2010
130
5
No way.

Please tell me you're lying....I avoided all 2.2 roms because if my phone dies, I'll die.

or else, PLEASE tell me you had some lagfixes or other stuff installed!

I'm running completely stock on Rogers, and just upgraded via Kies, no registry hack, about 30 minutes ago. LOVING Froyo!!

Well man its only the Bell version have most problem. Rogers should be fine. i9000m is famous for internal sd explosions...

o wellz, good thing nexus s is right on the corner, tho i hate it but guess hv to change a new phone if bell won't take my phone for repair

and yea, i hv everything stock too
 

deezy7

Senior Member
Oct 30, 2007
213
6
GTA
Well man its only the Bell version have most problem. Rogers should be fine. i9000m is famous for internal sd explosions...

o wellz, good thing nexus s is right on the corner, tho i hate it but guess hv to change a new phone if bell won't take my phone for repair

and yea, i hv everything stock too
omg nooo!

happened to my bell vibrant lol

here's my thread about it

http://forum.xda-developers.com/showthread.php?t=866838
just read it, and OMG NOOOOOOOOOOOOOOooooooooooooo!!!

I'm not using the Captivate, I'm using the Bell Vibrant, unlocked on Rogers. So I can't go to Bell to get it fixed (can I?!) if it happens! And, I'm not like, super rich, so I can't just drop $$$ on the Nexus S as much as I want to (besides, no microSD!! wtf?!?!)

I've been following all the threads about people's I9000M's dying after installing 2.2 roms, so I've avoided all of them as well as all lagfixes, etc. I just ASSUMED that a 2.2 update from Bell would be absolutely safe, since ROMS are hacked together by people who don't get paid to work with the code, while the people that get paid to work with the code (i.e. Bell employees) should be able to just put this together absolutely correctly.

This damn troublesome internal SD card!! ****!!! Should I just sell my phone now and get something else...or what...?...

And is it possible to roll back to 2.1 via Kies?
 

miniflight

Senior Member
Nov 15, 2010
130
5
omg nooo!


just read it, and OMG NOOOOOOOOOOOOOOooooooooooooo!!!

I'm not using the Captivate, I'm using the Bell Vibrant, unlocked on Rogers. So I can't go to Bell to get it fixed (can I?!) if it happens! And, I'm not like, super rich, so I can't just drop $$$ on the Nexus S as much as I want to (besides, no microSD!! wtf?!?!)

I've been following all the threads about people's I9000M's dying after installing 2.2 roms, so I've avoided all of them as well as all lagfixes, etc. I just ASSUMED that a 2.2 update from Bell would be absolutely safe, since ROMS are hacked together by people who don't get paid to work with the code, while the people that get paid to work with the code (i.e. Bell employees) should be able to just put this together absolutely correctly.

This damn troublesome internal SD card!! ****!!! Should I just sell my phone now and get something else...or what...?...

And is it possible to roll back to 2.1 via Kies?

Well once the internal sd card exploded, you can't even open the phone so they probably can't find out if your phone is unlocked. You just need to like ask a friend or a family member that uses Bell to go with you and take the phone over to a Bell store and see if they will repair it. Dont tell them you unlocked it lol. Just let say that your friend or a family member that upgraded the phone and the internal sd exploded etc
 

tony604

Senior Member
Feb 11, 2009
84
6
Vancouver
I don't think it really matters how you flash it, or even if you don't flash it at all. I've seen people with bad sd cards on stock 2.1, flash with odin, flash with cwm, flash with kies. Mine went bad just last week. It was running docs rom flashed on jh2 with recovery. Fortunately, the Bell store I took it to took it in for repairs even though I'm on Rogers.
There's clearly a hardware problem. Maybe it's the MoviNand. If that were the case, maybe that's why the Nexus S is using an iNAND instead of the MoviNand.
BTW, this is the 2nd i9000M I had this problem with.
 

Samdroid_G_S

Senior Member
Nov 14, 2010
381
37
Yea good thing mine died last week, got ahead of everyone else updating through Kies , hopfully I wont have to wait to long to get my phone back. I feel naked without it :(
 

danyul

Member
Feb 11, 2008
15
0
Vancouver
omg nooo!


just read it, and OMG NOOOOOOOOOOOOOOooooooooooooo!!!

I'm not using the Captivate, I'm using the Bell Vibrant, unlocked on Rogers. So I can't go to Bell to get it fixed (can I?!) if it happens! And, I'm not like, super rich, so I can't just drop $$$ on the Nexus S as much as I want to (besides, no microSD!! wtf?!?!)

I've been following all the threads about people's I9000M's dying after installing 2.2 roms, so I've avoided all of them as well as all lagfixes, etc. I just ASSUMED that a 2.2 update from Bell would be absolutely safe, since ROMS are hacked together by people who don't get paid to work with the code, while the people that get paid to work with the code (i.e. Bell employees) should be able to just put this together absolutely correctly.

This damn troublesome internal SD card!! ****!!! Should I just sell my phone now and get something else...or what...?...

And is it possible to roll back to 2.1 via Kies?
I had mine unocked on Fido and the internal sd problem occurred. I took it into the bell store. They charged me $35 for a repair quotation fee (incase it was water damaged).

It came back 2 weeks later...well a completely new phone came back 2 weeks later and they refunded my $35 since it was a warranty issue. My phone was rooted and had 2.2 but that didn't matter to them.
 

AvatarReborn

Senior Member
Oct 8, 2007
143
11
Man I feel bad for you guys !

Don't know what to say.

I've been very fortunate (knock on wood) to have not had any SD issues with my phone.

Had since release day and flashed at least a half dozen times with odin.
 

Existence.

Member
Sep 19, 2010
22
0
Just sent my phone in today for repair. I flashed a custom firmware I created with a lagfix enabled (stupid move, I know) which caused my phone to boot-loop. I had access to download mode, though, which allowed me to flash stock UGJH2 so I wasn't running a custom firmware when they looked at it.
 

evil-doer

Senior Member
Aug 4, 2010
408
27
Ontario
I had mine unocked on Fido and the internal sd problem occurred. I took it into the bell store. They charged me $35 for a repair quotation fee (incase it was water damaged).

It came back 2 weeks later...well a completely new phone came back 2 weeks later and they refunded my $35 since it was a warranty issue. My phone was rooted and had 2.2 but that didn't matter to them.

you got a new one in return? are the new ones network unlockable? i thought they remedied that? im also on rogers using a network unlocked bell vibrant and im very scared of bricking because i may get a phone back that i cant unlock.

btw i upgraded to 2.2 without issue.
 

danyul

Member
Feb 11, 2008
15
0
Vancouver
you got a new one in return? are the new ones network unlockable? i thought they remedied that? im also on rogers using a network unlocked bell vibrant and im very scared of bricking because i may get a phone back that i cant unlock.

btw i upgraded to 2.2 without issue.

Yeah, I was able to unlock it fine with the code generated by the SGS Unlocker that is in the market.
 

jpyper2010

Member
Aug 25, 2010
5
1
Yup... just upgraded with Kies an hour ago. Seemed OK and then just died. Now running an endless loop with logo and black screen. Can not get into recovery mode with 3 btn rec. Arrrgh. Going to Bell tomorrow.
 

MaverickHHH

Senior Member
Sep 3, 2010
81
6
I had a very similar problem where it ended saying "internal SD card damaged". HOWEVER I did not have to send it in to repair (yet!).

I recovered holding down "home+power+volume UP" (as opposed to DOWN). This gives you a bios menu that you can reformat internal SD, cache and factory reset. Do this and hopefully it will boot up again. To be safe, do another Factory Reset from within the OS and reformat the internal SD again.

After I did this, it is up and running good so far. Currently re-configuring from scratch again...
 

AllGamer

Retired Forum Moderator
May 24, 2008
11,915
1,655
SGH-T989
AT&T Samsung Galaxy Note I717
It died after JK4

OMG!

WOW! here's an irony...

phone was originally JG9, went to JH2 no problem, updated from JH2 to JH2+SPL fix no problem, when from JH2 SPL fix to JK3 no problem....

now after upgrading from JK3 to official JK4 toasted, during when i was restoring all the stuff back from Titanium Backup

it got stuck several times, rebooted the phone a few times, now it's totally black screen, and with the soft key lid, but doing nothing :eek::confused:

I can go into both Recovery and or Download modes

I can flash back to any version of ROM i want, but always get the dreadful message /dev/block/mmcblk0p1


.... sigh... :( time to dig out the invoice and go to the store for repair
 

Frostshock

Senior Member
Aug 11, 2010
77
1
And as if on cue, there it goes. Unlocked phone, one of my widgets was screwed up, then black screen. Reboot, black screen. And of course today is the day I finally root it, but if it can't start they can't tell so ha :p

I am not willing to submit to dead SD yet though. This phone has been working since August 6th. I'll try wiping everything that can be wiped in recovery mode.

Edit: Nope, it's completely dead. I have the smartphone protection plan though, so I can "lose" this phone and get a brand new one for $150. Although preferably they give me a replacement then and there or a Desire Z. I do not want to leave the store tomorrow without a permanent replacement.
 
Last edited: