Samsung Galaxy S3 will not turn on

[AxlMyk]

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.

 

[Kelly Kearns]

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.

 

[banjo67xxx]

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

 

[Kelly Kearns]

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

Samsung says it was, they are replacing these phones. This article is a couple weeks old.

http://www.gottabemobile.com/2013/01/03/latest-galaxy-s3-update-could-fix-sudden-death-issue/

Sent from my SAMSUNG-SGH-I747

 

[meyerweb#CB]

People need to read more carefully. The article says this:

The update comes just a short time after Samsung rolled out the Android 4.1.2 update to the Galaxy S3,

This statement would seem to indicate the update to fix the Exynos exploit is not the same as the 4.1.2 update.

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.

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.

 

[Kelly Kearns]

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.

That is ONE of the 8 million articles on this issue, that many of us have been following. Context is really important.

Sent from my SAMSUNG-SGH-I747

 

[Kelly Kearns]

meyerweb, Gave you some time to look into all this, don't know if you did.

Couple of key things: Exynos chip - The US Version runs on Snapdragon.

The Sudden Death: "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."

The Exynos vulnerability is the Sudden Death Syndrome. Now haven't followed the argument too much, but last I heard, that while the motherboard was basically being "fried" Samsung had determined it was not an actual faulty motherboard, but a software issue, a problem in Samsung's custom ROM and other ROMS based on it.

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.

Samsung Galaxy S3 'sudden death' security flaw fixed in UK | CNET UK

Again, context is everything, not my job to go out searching for all the info on something if I give someone a piece of info. Next time if you don't see where something is coming from, instead of saying I need to read something a bit better, maybe asking a question might get your further. I don't just pull things out of the air. If I haven't heard of something, I say I haven't. If I'm not sure of something, I say I'm not sure. If I can't remember something, I say I can't remember it.

Just sayin'

 

[meyerweb#CB]

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.

 

[Kelly Kearns]

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.

Again, not my job to go researching and my last post does very well address it. Yes, I know about it charging overnight in most cases and then it is dead..got it. Yes, Samsung has looked into this and as they have been clear about:

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.

They have found the Sudden Death is caused by the Exynos issue, it also has allowed apps to exploit this vulnerability. Which means it doesn't have to be a hacker hacking into your phone.

When someone is having the issue with Sudden Death, I'm expecting they know a bit about it. Then if I post something to them about it and they aren't really familiar with the Sudden Death, I expect questions. You aren't having this issue, you are just worried about critiquing me. I'm not a writer here, I'm not an adviser here, I'm not an educator here, I am a user. It is not my job to go educate someone on every aspect of something they ask about and assume they know nothing about it when they post a question. They post a question, there is more, fine, they post something else and then we can get deeper into it. What I find interesting is that you are not even the one with the issue, yet you are the one trying to tell me that I need to put out the info from beginning to end on this issue.

Nope, that's not how it works. People ask questions, you give them some info, if they don't understand or need more info, they post another question.

 

[jetrated]

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

 

[Kelly Kearns]

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

Rooted or not?

I'm guessing it is stuck on the Samsung logo?

 

[jetrated]

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

 

[Kelly Kearns]

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

Hmmm...sounds like a totally different issue than Sudden Death, because with that, it's just completely dead. I've seen some stuff about this where rooted devices are concerned.

Quick search and I found this on a non-rooted device. Look through this and see if there is something that will work for you here.

http://www.samsunggalaxys3forum.com/forum/samsung-galaxy-s3-help/9015-stuck-boot-screen-not-rooted-modified-urgent.html

If none of this work, you might want to start a thread with a good description in the thread title and then more will see it that might can help. I don't root at all, so not familiar with any of that and I have read about some issue here for non-rooted devices that the people that do a lot of rooting, know how to fix.

 

[proaccs]

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?

 

[jetrated]

Thanks for the link Kelly!
I can't even get to recovery mode. Whatever I do I don't get past the Samsung logo....

 

[Kelly Kearns]

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....

I would suggest one of you start a thread and both of you post on it and those that are really familiar with fixing these kinds of issues will see the thread description and they will come in the thread and help you.

 

[Almeuit]

Thanks for the link Kelly!
I can't even get to recovery mode. Whatever I do I don't get past the Samsung logo....

Have you tried the good old battery pull? I'd suggest taking the battery out for 2 minutes then put it back in.. Then try and go into recovery. If not then I'd do what Kelly said.

Sent from my Sprint S3 using AC forums

 

[jetrated]

Battery pull didn't solve it either. Thanks for thinking along.

Sent from my Nexus 7 using Android Central Forums

 

[proaccs]

Yep tried everything it is looking like a trip to the store its foooooooked

 

[Kelly Kearns]

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

Now this is bugging me...I'm about to catch up on a couple of things, might try and do some searching on this issue online since it is now officially bugging me...