13-02-2013 07:33 - edited 13-02-2013 08:05
13-02-2013 07:33 - edited 13-02-2013 08:05
I received an in-phone notification last Tuesday from Samsung alerting me to an update to my existing 4.1.2 firmware so I went ahead with it. When the update finished, I noticed straight away that my phone was lagging considerably and when I cleared my RAM, it would take sometimes up to 20 seconds for my phone to become responsive again. This is my third Galaxy S device (after the SGSI and SGSII) so I'm very familiar with the OS and basic troubleshooting so I put this down to a need for a factory reset.
After factory resetting, I didn't install any apps for a while just in case it was a rogue app hanging but I noticed no change. In fact, it became worse. My phone would randomly freeze up. I'd be doing everyday stuff like browsing the internet/Twitter and my screen would just hang. Sometimes I would take it out of my pocket and I'd be unable to unlock it, it would just stay blank and the only way to revive the device would be to force restart either by holding the power button or removing the battery.
I spent about 4 hours researching the issue last night to see if it was a global problem or just my phone and I discovered that this issue was affecting hundreds of people, all on 4.1.2. One particular dev forum believes the issue points to a fault with devices bought around 5-7 months ago that all break and become corrupt with this software update. I've not rooted nor manipulated my device in anyway, this all happened after updating officially via Samsung.
Anyway, could someone suggest what I should do next? Any help would be appreciated.
Solved! Go to Solution.
27-03-2013 21:32 - edited 27-03-2013 21:36
I should have mentioned after I started having problems all I have tried to use the phone for has been
pattern unlock
play store (to try uninstall 3 things I thoghut were maybe the cause, they're reinstalled now and fine)
SMS
gmail
and ~3 hours of trying to use google nav
nothing hugely taxing, and that caused those 52 reboots.
I'm a developer and genuinly very careful about what I install, how I treat my phone I had no doubts after reading the threads what the problem was, those problems may eventually trickle back in a few weeks only long term testing can show it's truly fixed, but a newer firmware is the only thing that's stopped it dead for now.
XELLA has freeze/lockup/powerdown/brick issues, o2 need to sort out their branded update asap, and prioritise support for anyone reporting issues on XELLA in the mean time :
http://www.reddit.com/r/Android/comments/18dqye/heads_up_sgs3_i9300_users_the_firmware_samsung/
http://forum.xda-developers.com/showthread.php?t=2122346
http://forum.xda-developers.com/showthread.php?t=2133401
Oh, one minor thing for anyone else, the com ports never showed up yellow as per MI5's instructions, they were blue with text in when connected in odin 3.7 for me.
if it lists a com port in te blocks under ID:COM and the md5 is checked and clear when you add it to the PDA section then you're good to go.
Anyway, many thanks once again for your help, saved me a fair bit of searching about for the right threads for the most recent odin, time to get back to reboot free life again
on 27-03-2013 23:15
on 27-03-2013 23:15
on 28-03-2013 08:30
Just to add to this, my s3 was freezing and or dropping phone calls. I did a factory reset last night and it seems to have resolved the problem.
Didn't lose anything this time either!
on 28-03-2013 12:01
If you were on XELLA firmware, a 16gb phone, and you weren't just unlucky with some other software, then those freezes will return shortly. factory reset is the first thing people try after some basic debugging / cache removal.
but good luck!
on 28-03-2013 17:15
on 28-03-2013 17:32
on 28-03-2013 17:48
on 28-03-2013 17:48
on 29-03-2013 10:15
on 29-03-2013 10:15
on 03-04-2013 20:14
It's been an entire week, not one single reboot in that time since updating the firmware.
The only issue I have found with ODIN flashing sa ammobile rom is that my CSC isn't the same as the phone Sales Code,
The CSC is i9300OXAEMB5 but kies picks it up as O2U instead of BTU matching the rom, and so says it's unable to do firmware updates on the phone.
I'd need to reset it to BTU with a CSC changer or a factory reset apparently, but both would wipe my phone data. So I'm stuck with ODIN only updates, unless I risk sacrificing everything as ADB backups aren't as reliable as titanium backups but I'm not rooting the phone.
on 03-04-2013 20:42
on 03-04-2013 20:42