AxlMyk
Well-known member
Can you boot into safe mode and try to figure it out?
Keep tapping the menu key while it's booting.
--Tapatalk 2 on SGS3.
Keep tapping the menu key while it's booting.
--Tapatalk 2 on SGS3.
The problem with the sudden death is only for the international S3's and the 4.1.2 update has the fix for it. Samsung knows what the problem is now and they WILL replace the phone.
I updated my phone with 4.1.2 last week, and it died a sudden death a couple of hours ago, so I don't beleive that 4.1.2 has the fix
The update comes just a short time after Samsung rolled out the Android 4.1.2 update to the Galaxy S3,
Samsung is reportedly rolling out a new firmware update for the Samsung Galaxy S3 that evidently corrects an Exynos CPU vulnerability and MAY solve the Galaxy S3 ?sudden death? issue that owners of the flagship smartphone started seeing in late 2012......SamMobile confirms that the update patches up the Exynos processor exploit
The exploit ... [is] not an issue on the American versions of the Galaxy S3 because they do not use Samsung?s Exynos processors to run.
What?s unclear is whether the update tackles the ?sudden death? issue that Galaxy S3 owners saw arise six months after the device arrived.
People need to read more carefully. The article says this:
This statement would seem to indicate the update to fix the Exynos exploit is not the same as the 4.1.2 update.
The only thing this article says is limited to the international version is the Exynos exploit. Nowhere does it say the sudden death problem is limited to the international version. And as it says directly above, it's "unclear" whether the update solves the sudden death issue.
Samsung is beginning to roll out a security patch to UK Galaxy S3 phones, designed to clear up a bug in the S3's Exynos chip that could potentially see some phones being wiped or bricked by naughty hackers.
The sudden death bug, as it's known, was found by an XDA Developers user and gives hackers access to the RAM of phones including the Galaxy S2, S3 and Note. "RAM dump, kernel code injection and others could be possible via app installation from Play Store," user alephzain explains.
Samsung has pointed out that it only affects a very limited number of devices, but it could affect those running stock Android or custom ROMs after rooting the device.
The update is said to be available now as an over-the-air release or over Kies software but at the time of writing, my Galaxy S3 showed no available update, so it could be that certain models are receiving it before others. XDA explains how to download the update manually using Kies, but warns you do this at your own risk.
Having your phone potentially bricked by a remote hacker with a malicious mind is clearly quite a worrying issue, but it doesn't seem to have been a widespread one. Security holes are sadly quite a common occurrance, particularly in new software that may have had small issues overlooked. Thankfully, Samsung has acted to patch it up before too much damage has been done.
Have you been affected by the bug? Do you know anyone who has? Let me know in the comments below, or over on our rock-solid Facebook page.
Kelly, you're the one who made the statement, and then posted a link as support for that statement. If you're going to do that, at least post one that actually supports your point. Just sayin.
Your last post doesn't address the same issue, I don't think. This is still talking about the expoit.. I've not see any evidence that the bulk of phones which have succumbed to "sudden death" were attached by some malicious hacker. People set them down, and picked them up later to find them dead. I still think the exynos exploit and the rash of dead phones are two separate issues.
Samsung is beginning to roll out a security patch to UK Galaxy S3 phones, designed to clear up a bug in the S3's Exynos chip that could potentially see some phones being wiped or bricked by naughty hackers.
The sudden death bug, as it's known, was found by an XDA Developers user and gives hackers access to the RAM of phones including the Galaxy S2, S3 and Note. "RAM dump, kernel code injection and others could be possible via app installation from Play Store," user alephzain explains.
My S3 just died. I am stuck on the boot screen. I have not installed 4.1.2.
:-(
Sent from my Nexus 7 using Android Central Forums
Yes, stuck on the logo.
Not rooted, totally stock
Trying to get support from Samsung but getting a severe run around. They don't want to touch my phone cause I'm not in the US
Just registered after reading through all/most of the threads....Mine has just died not rooted i was using it loaded skype and it just hung had to remove battery and now stuck on logo..
After doing a bit of research would reloading firmware using odin be of any benefit? I cant get into factory reset i.e home power and vol up but i can get into custom firmware load so use odin and load original firmware?
Thanks for the link Kelly!
I can't even get to recovery mode. Whatever I do I don't get past the Samsung logo....
Thanks for the link Kelly!
I can't even get to recovery mode. Whatever I do I don't get past the Samsung logo....
Just registered after reading through all/most of the threads....Mine has just died not rooted i was using it loaded skype and it just hung had to remove battery and now stuck on logo..
After doing a bit of research would reloading firmware using odin be of any benefit? I cant get into factory reset i.e home power and vol up but i can get into custom firmware load so use odin and load original firmware?
Thanks for the link Kelly!
I can't even get to recovery mode. Whatever I do I don't get past the Samsung logo....
Battery pull didn't solve it either. Thanks for thinking along.
Sent from my Nexus 7 using Android Central Forums