I would like to know how many of you had successfully updated their SGS (Samsung Galaxy S) to Froyo. I think this will help us understand the failure rates so people who do not want to risk bricking their phone.
1) Updated with no problems
2) Updated with problems
3) Tried to update and having problems
4) Did not update at all
If you are talking about roms.. Well most are a 1. I habent heard of an official froyo update. And.if.you by chance do.brick it, there are ways to unbrick it pretty easily.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have the Bell Vibrant which is the I9000M.
I thought that Bell released an official update for their new Froyo. Check it out here
mobilesyrup.com/2010/12/08/bell-samsung-galaxy-s-vibrant-upgrade-to-os-2-2-froyo-coming-december-10th/
Did update my Bell Samsung Galaxy S GT-I9000M with Bell release Froyo available using Kies and all seemed to be running smoothly until I had issues connecting my bluetooth and trying the voicedialing features that did not work in my case and after got Force close on every apps. Did a shutdown and got the device in a loop at boot up.
Will try tonight to reload the device with 2.1 and see from there to retry 2.2.
Finger cross !
I upgraded with no problems but I did do a factory reset as things started to get a bit slow and from what Ive read it is a good idea to do a reset to get rid of any residual 2.1 stuff on the device. Since then the update has been working well for me...
KNOCK ON WOOD!!!
I have 2 SGS phones so you'll just have to add another vote to the "successful upgrade" option in addition to the one I was able to cast
I've flashed the following 2.2's without any problems so far:
- unofficial JK3 (Canada) via ODIN
- official JK4 (Canada) via Kies
- straight JPU via ODIN
- JPU Doc RomMOD v2 via update.zip recovery
No problems with flashing.
And yes, clearing data & cache is helpful (mandatory?). Backups are good!
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
ssj2miguelx said:
I would like to know how many of you had successfully updated their SGS (Samsung Galaxy S) to Froyo. I think this will help us understand the failure rates so people who do not want to risk bricking their phone.
1) Updated with no problems
2) Updated with problems
3) Tried to update and having problems
4) Did not update at all
Click to expand...
Click to collapse
AllGamer said:
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
Click to expand...
Click to collapse
Cool. That makes this type of poll misleading then because someone reporting success today may have issues tomorrow (we can't change our vote correct?).
That's right. I saw your post about your phone going bust. Sorry to hear that.
I just can't get Kies to work -- it just says "connecting to device" and it hangs
Also can't install MPT USB drivers -- always fails. I installed the correct x64 bit Windows 7 drivers and everything.
Ughh
Wow. I didn't think people would have problems after the update. Man, I really should wait until we all know that its okay to update. I am new when it comes to the SGS so if I fail at it, I don't want to start crying. This is such a nice phone....so if it works, why break it?
ssj2miguelx said:
Wow. I didn't think people would have problems after the update. Man, I really should wait until we all know that its okay to update. I am new when it comes to the SGS so if I fail at it, I don't want to start crying. This is such a nice phone....so if it works, why break it?
Click to expand...
Click to collapse
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Funkadelick said:
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Click to expand...
Click to collapse
If your card is gonna die its gonna die no matter if you upgrade or not....Flashing just seems to speed up the corruption.
Thats a good question. People seem to be having big issues with this new Froyo update here, http://forum.xda-developers.com/showthread.php?t=867157. I really hope Bell gets a fix for this new "firmware Froyo 2.2" that they just released.
If the Nexus S is the so similar to the SGS I9000M why dont we have Gingerbread (2.3) yet?
Again people. It's not the froyo update that's a problem it's bad internal SDcards. These phones were dying before froyo came out and without ever flashing anything.
If they're gunna die, they're gunna die. Flashing just helps to speed up the failures. SO flash away and hope it blows before your warranty is up.
Funkadelick said:
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Click to expand...
Click to collapse
If I was you I'd flash the crap outta your phone. If your black screen was due to a weak internal SD then it's gunna go. So flash it and hope it goes so you can get a new(repaired) one. Of course the wait time is a bit long right now for repairs. And there's no guarantee that the newly repaired one won't blow.
Damn this phone....
And yes, clearing data & cache is helpful (mandatory?). Backups are good!
Click to expand...
Click to collapse
How to do it?
It will delete also my files (photos, music....) on the internal memory?
Regards
Sent from my GT-I9000 using Tapatalk
AllGamer said:
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
Click to expand...
Click to collapse
yeah!
my phone upgrade went well..but i have occasional force closure on apps. Then one day it just hang using Msn Talk Pro and I had to pull the battery out to reboot and it never came back on - stuck after the bootup S logo. grrrr..
how long does the warranty repair usually takes?
Anyone in Vancouver Canada that are non Bell subscriber have any problem bringing it in? Which store do you guys go to? I will try the same store for hassle free repair job. Thanks
Videonut said:
Again people. It's not the froyo update that's a problem it's bad internal SDcards. These phones were dying before froyo came out and without ever flashing anything.
If they're gunna die, they're gunna die. Flashing just helps to speed up the failures. SO flash away and hope it blows before your warranty is up.
Click to expand...
Click to collapse
Is there a chance that my phone has a bad internal SDcard?
betaboy00 said:
yeah!
my phone upgrade went well..but i have occasional force closure on apps. Then one day it just hang using Msn Talk Pro and I had to pull the battery out to reboot and it never came back on - stuck after the bootup S logo. grrrr..
how long does the warranty repair usually takes?
Anyone in Vancouver Canada that are non Bell subscriber have any problem bringing it in? Which store do you guys go to? I will try the same store for hassle free repair job. Thanks
Click to expand...
Click to collapse
Took mine into the bell store at guilford mall, originally purchased at wireless wave.Unlocked and being used on the fido network. No issue at all, the guy took down my cell number as a way to track its progress.
ssj2miguelx said:
Is there a chance that my phone has a bad internal SDcard?
Click to expand...
Click to collapse
There's no way to know for sure. Some ppl seem to have a bunch of force closes bfore it dies and others just turn it on and it's dead.
OK so in Australia we got the SGS FroYo 2.2 update in November and when I went to upgrade my phone everything went stupid. Basically I'd never needed/wanted to root or anything like that my phone was running with its basic firmware plus OCLF to fix the lag. Basically I got over excited about the update and didn't read anything and well I bricked my phone because I didn't remove OCLF. That was fine and dandy until I released that my 3br would not work anymore (don't ask my why) so i had to send it in for warranty. So thats the background/past before everything went stupid again.
Now I got my phone back and the 2.2 upgrade had been installed the repair deatils where:
- Inspected and chemically cleaned all contacts
- Upgraded handset to latest available software DTJP3
- Unit tested and passed live on air test
- Handset meets all manufacturer specifications SU
Click to expand...
Click to collapse
Now like I said I got my phone back and everything was fine & dandy but I noticed it was really slow, slower then 2.1 was. Also my D button would not work, no matter how hard i tried to press it, even when I swiped over it the blue line thing goes around it. Along with not being able to press the d button, anything located near the side of the screen would just not register my touch. Also my phone would just decide without me touching it to just select things and malfunction, type whatever text it liked, it also would constantly scroll up and down and basically just screwed my head in. Now I thought this was just a temporary error so I restored factory settings through 3BR and privacy settings method and it seemed fixed. So I applied z4root so i could OCLF back to fix the lag but that bricked my phone so I had to reset it again and then I applied voodoo lagfix (the one click method from market). I didn't really notice and difference with the voodoo lagfix so i disabled it and bam! my phone went even more stupid. So I googled and searched xda and removed voodoo entirely by flashing back to the original firmware and that seem to fix everything but the D for about 5 mins and now its not as bad as it was but its still malfunctioning all over the place and I can't even have it on the 1st screen without it constantly going into my contacts and trying to delete them or type things...
So what do I do? If I send it back for warranty will they notice that the firmwares not optus but the orginal (from samsung-firmwares.com)? will that break my warranty? Plus sending it for warranty now will mean I won't get the phone back till January at the earliest. Or can someone suggest something else to go about fixing it?
Sorry about long post, thought going into detail would be better and more helpful.
Hey mate,
If you reflash with dtjp3 from samfirmwares then that is the firmware they put on and will not be able to tell you fkd with it.
Good luck
Alex
Been happy with it since December. Had problems yesterday rebooting after removing battery - an application had frozen. Can't recall which one. Eventually got it to reboot, but all the home screens were wiped and a number of apps had simply gone. Some that were left insisted on force close. The ones I use mainly are OK up to a point but they usually don't remember that they have run before after sleep - so I have to go through all the terms of acceptance and redo the settings.
The 3 button combo no longer seems to work - although I never did try it with Froyo.
Help appreciated
Got 3 button combo to work eventually!
What firmware are you using?
lcgmadeira said:
What firmware are you using?
Click to expand...
Click to collapse
2.2.1 XXJPY downoaded with Kies
I've reinstalled various apps and all is well now it seems. I remember what the app was that screwed things up. It was Samsung AccuWeather Clock. Had problems with it before. Don't know why I bothered trying it again - a foolish mistake I think!
check the lost file directories.. my guess is you have some dsk corruption.
Hey guys-
Kinda a weird problem.
So my captivate won't play any system sounds at all. It's particularly weird, since all media apps work just fine. This was fresh from Samsung's repair center, and had a new install of official 2.2 on it. It wasn't even rooted when this problem started, and after a flash to 2.3.3 it still has the problem. I've tried changing the ringtone, notifications, and every other sound; same thing with turning everything up all the way. Nothing has changed and there is no silent mode active anywhere. It seems to only vibrate when a message comes in. I'm fairly confident that it's not a software problem, due to the updated firmware and kernel. Has anyone had this problem? Do they know of a workaround?
lisurgec said:
Hey guys-
Kinda a weird problem.
So my captivate won't play any system sounds at all. It's particularly weird, since all media apps work just fine. This was fresh from Samsung's repair center, and had a new install of official 2.2 on it. It wasn't even rooted when this problem started, and after a flash to 2.3.3 it still has the problem. I've tried changing the ringtone, notifications, and every other sound; same thing with turning everything up all the way. Nothing has changed and there is no silent mode active anywhere. It seems to only vibrate when a message comes in. I'm fairly confident that it's not a software problem, due to the updated firmware and kernel. Has anyone had this problem? Do they know of a workaround?
Click to expand...
Click to collapse
Mabey an odin one click, then keys update to froyo might work ??? !! I'M NOT TELLING YOU TO DO THAT, I'm just suggesting that might work. If it came with froyo then you might get a bootloop so I would suggest getting a jig if try this way
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
jig
in all cases the jig is your lifeline lol. I SUGGEST having a jig handy when any new roms are installed. There are alot of good roms out there having no phone for a couple days changes the perspective and for you to make a jig is under 10$ .... Did I mention lovin the new Serendipity 7, good clean rom.
Get the actual CSDJ for German DBT yesterday. Was under 100 Mb with MaysecPatch. So far so good..
But my whole UI is lagging now, SBrwoser loads pictures on websites so fast as my old s5, in app scrolling like on Pinterest is laggy as hell too. The Cameraquality is lower then before, no singel Picture is really clear..washed out and stuff. My BT Devices need a reconnect after this Update, strange too. I think something went definitley not right.
What i done so far:
Write Sammy via SamsungMembers a bad message of this **** perfomrnace with this actual Update.
Cleared my Cache Partition via Recovery
Backup all my stuff so maybe i reset the whole Phone on weekend if nothing get better next days.
Restartet the Device many many times since yesterday. Just in case this maybe can help.
Revert back on FHD+ resoloution, so the laggy perfomrnace is around 30 % better but not good
Chance between the normal and power mode for battery, just in case of testing if something get better but nope..
*Edit* Ohh and the Problem with random reboots is back -.- Was gone with CSDE but seems to be back..oh cmon whats wrong with mayupdate -.-
Does anyone facing this issues too ? I hope that just something went wrong within the Updateprocess and this is just a temporal problem till i reset the wohle phone.