yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] pickandwhammy:
We might still see some deaths due to existent damage (there's a term for this, no?), but yeah, we won't know for sure for another few months. I hate long term 'observation'. Actually I hate long-term anything.

N4 was my first choice despite the no-sdcard and embedded-battery crap (no LTE support is not an issue in my country), but Play Store doesn't sell devices here. And retail prices of S3 are actually cheaper.
[Galaxy S III General] invinciblecc:
I flashed phills recovery and yanks kernel now i am supposedly safe right
[Galaxy S III General] kofiaa:
Yes you should be. Right now we are all hoping it's fixed.
[Galaxy S III General] hermeson:
So Just taken the screenshot of my New S3, my fw is the vunerable one?
[Galaxy S III General] markie32:
Yep
[Galaxy S III General] hermeson:
Oh gosh! How can I update it to the Safe fw? Thanks
[Galaxy S III General] kofiaa:
Flash persues or any sds safe kernel, then flash philz custom recovery to be safe.

Please try and read the previous pages, all these questions have been answered.
[Galaxy S III General] hermeson:
I am going to check it... Thanks

---------- Post added at 10:13 AM ---------- Previous post was at 09:26 AM ----------

Kofiaa, it is funny, coz I had updated to XAELLA last week, but it seems the detail of "fw issue" remained on my phone?!

I read the post you said, but I couldn't find something like safe kernel! Can I just update the kernel?

thank you
[Galaxy S III General] kofiaa:
Yeah, use Philz recovery to flash a safe kernel. boeffla, persues are all safe.
[Galaxy S III General] XVSBL:
A good kernel that is supposed to be sds safe comes with PhliZ cwm
[Galaxy S III General] gabrymr:
even older than mine and same chip/rev, based on what I've read in this thread, I can only guess, you are, but it's just a guess...
[Galaxy S III General] XVSBL:
Can you tell me if mine is sds safe??
[Galaxy S III General] KeesStolk:
As far I know, Siyah didn't patched his kernels to the newly found string/code they found in the later kernels from Sammy.

So if those found strings does indeed fix the sudden death, then no you are not.
[Galaxy S III General] hermeson:
You need to install emmc check to find out. Go to market
[Galaxy S III General] maccboy2010:
How do we find out which ones are cursed mine is the 16gb pebble blue I bought it 27th December, I updated it the other day as well. Mine isn't routed and has the standard 4.1.2 Samsung touchwiz.

sent from my awesome unlocked galaxy s3.

---------- Post added at 03:19 PM ---------- Previous post was at 02:58 PM ----------

Its got to be something to do with charging most people's phones are dying at night while plugged in charging, or just taken off from charging. It seems tht its frying something on the board. My brother girlfriend works in car phone warehouse and she said Samsung are replacing the main board and speakers for some strange reason. Why change the speakers? ? And she said there is loads bieng brought back with this problem. Ill try and find out more from her when I next see her. :)

sent from my awesome unlocked galaxy s3.
[Galaxy S III General] hermeson:
Mine has died from nothing. It was on my desk, unplugged, nothing around, it has gone =/
[Galaxy S III General] shethsa:
In my case Samsung said they're replacing the mic. That sounds funny
[Galaxy S III General] invinciblecc:
Guys I have flashed yank llus kernel and this has over clicking to 1.6 ghz is it safe to run the phone at this frequency consistently what side effects does it have
[Galaxy S III General] sotmax:
Speed needs power only..

Just more drain nothing else.

Apart from that this kernel is running just great with evn no overheating at all...
[Galaxy S III General] XVSBL:
Can I flash perseus kernel without Odin and just using cwm. And could you give me a link to the latest version of the perseus kernel?
[Galaxy S III General] maccboy2010:
Thats what I ment there replacing the main board and speakers n mics why change them, they must think there faulty for some reason. I'll try and get some more info from my brother's misses she said shes had loads coming back bricked to car phone warehouse.

sent from my awesome unlocked galaxy s3.
[Galaxy S III General] blackyz:
Yes

Sent from my GT-I9300
[Galaxy S III General] maccboy2010:
Can someone tell me if mine is one of the unlucky ones pls ?

sent from my awesome unlocked galaxy s3.
[Galaxy S III General] htcsnap93:
No we cant. Get emmc check from the apple store and check if the firmware 0xf1
[Galaxy S III General] cyberdroxxx:
Yes my S3 flickers green too. I am on ELLA Uk plus Purseus kernel. Yes sir I know ELLA has the fix but I still wants the Purseus kernel to back it up
[Galaxy S III General] XVSBL:
Is mine safe?
[Galaxy S III General] Tenacious:
Read this http://xdaforums.com/showthread.php?t=2091045
[Galaxy S III General] XLR8_2K:
RIP S3 using Omega v.36 + SiyahKernel S3 v1.8.6

Mine just died one hour ago.

Was with omega v.36 (xella) & siah 1.8.6

with charger, checked some messages, put it down.

15 minutes later, grabed it, green light was on, screen was off. No response. I felt the first chill down my spine.

Pulled the battery, put it back.

No recovery mode, no download mode, no screen response, no led response, nothing at all. with or without charger.

any ideias? besides trying to use the warranty?

(was in fact using triangle away before dying, and was saying all the correct info)

thanks in advance guys... :crying:
[Galaxy S III General] animoo:
Holy crap!

Am I the only unlucky one, whose GS3 died into soft brick (stuck on SGSIII boot screen, DL mode works, but can't flash anything with Odin). In DL-mode it can be seen, that it was modified, my counter is on 2, custom binary etc.... I think it is "better" if it completely died, no one can revive it, so your warranty is not void....But in my case it is not sure...:(:eek:

Your one will be fixed under warranty imo...
[Galaxy S III General] offgrey:
If it's completely dead, there's nothing you can do really. It's absolutely dead and there's nothing else to try, unless you want to try someone else's battery in your phone or your battery in their phone. Frankly, if I were you, I'd just take it directly to the service center.
[Galaxy S III General] sotmax:
Unfortunately

No rom or kernel or bootloader related....(opinion)

Last 2 days i have received a couple of reports that s3's died either stock XXELLA or old bootloader or even patched kernel and safe recoveries.....

We have to get deeper into this..

The most strange thing is that sudden deasth takes place from a date and after and start to affect whatever find in its way

Seems to me that have nothing to do with version or whatever.

If you can my friends whoever is affected by sd please pm me the following.

-Device made in

-Battery made in

-Device region

-16 or 32 gb

-State of happening(etc charge overnight or after sms or both)

regards
[Galaxy S III General] bogstandard:
Don't know if this counts as SDS, but mine rebooted last night as now hangs at the samsung splash screen. I can enter download mode but (so far) I have been unable to flash stock (be through Odin or Kies). Gonna sort out a warranty return tomorrow... :(
[Galaxy S III General] XVSBL:
So basically I just downloaded a bunch of kernels and new recovery and stuff to not have sds. But everyone gets it?
[Galaxy S III General] vasp3690:
I have been trying to understand myself and looking at the options of installing the latest firmware ELLA on the international version I was under the impression that the already posted option of ELLA through odin would also include the kernel that is fixed, am I right in that assumption?
[Galaxy S III General] offgrey:
Yes. Flashing XXELLA through Odin will give you the firmware, the kernel, the bootloader, the fixed stock recovery.

So far, no one has been sure of how to solve SDS. All we have are assumptions as to how we can prevent SDS. It doesn't hurt to move on to newer firmware as they may patch the problem. If you have been using your phone which has the old eMMC firmware, the eMMC wear leveller may have suffered enough damage as it is and may fail leading to SDS even if already on patched kernels and recoveries.
[Galaxy S III General] drsiddique5700:
Sudden death

guys i live in india does sudden death also affecting indian users?please help
[Galaxy S III General] mclaudio:
mine is in service center

omega v35

bootloader XXLA

kernel syiha

recovery philz recovery

at night it started to became slow...then....during night in standyby completly died...
[Galaxy S III General] Dave83:
Affected is FW Rev Fx1 or FW Rev: 0xf1?
[Galaxy S III General] aniobash:
Yes, like plague!
[Galaxy S III General] sotmax:
There are many reports of sd in stock XXELLA alrwady my friend :(

) ) ) over the air fom galaxy siii ( ( (
[Galaxy S III General] XVSBL:
How do you check your emmc level?
[Galaxy S III General] danarama:
Unfortunately that disproves nothing. The damage could have been done before ELLA update.

These kernel fixes been in place since XXELKC.

Only real way to disprove the fixes is to find a factory flashed 4.1.2 suffer sds.

What I mean by factory flashed is brand new, in box, official 4.1 2 from factory. If one of those has sds, only then can we start to compile evidence that these fixes don't work.

Unfortunately anything that existed with older than 4.1.2 or unofficial firmware at any time, cannot be used to prove or disprove anything as they are predisposed to the fault by not having "protection"

Edit > here's an analogy....

1 - If you walk directly into a nuclear warzone already wearing your 4.1.2 radiation suit. You should be fine.

2 - If you walk into the nuclear warzone wearing your 4.1.1 jeans, you will get poisoned.

3 - If you walk into the nuclear zone in your jeans THEN put your suit on, you may or may not get poisoned - depending on the amount of exposure.....

BUT the only way to prove the suit doesnt work is to do number 1 and still get poisoned.

Most SDS cases are number 2 or 3. We haven't seen 1 yet to my knowledge
[Galaxy S III General] DonHuan:
But none of them here, in XDA?

There were some reports of SDS in XXELLA firmware but with Siyah kernel, which is SDS affected.
[Galaxy S III General] XVSBL:
What if there is no Samsung center were I live what do I do if I get sds
[Galaxy S III General] Dave83:
Hey guys, this eMMC Chip is affected from sd?

http://s8.postimage.org/80dh90tqd/Screenshot_2013_01_05_21_30_22.png
[Galaxy S III General] cyberdroxxx:
Yes yours is infected.
[Galaxy S III General] behemot24:
you can find your geographical zone covered by samsung here and send them an e-mail or call them to ask the procedure for replacement/repair.
[Galaxy S III General] Scarface1991:
The important thing is not the Firmware but the Kernel which is being used. So far to my knowledge there hasn`t been any evidence that a SIII died with a SDS fixed Kernel. It is true that there had been reports with broken phones that had XXELLA installed but after further inspection you find that all of those cases had other Kernels installed, like the Siyah Kernel, which is not safe.
[Galaxy S III General] T0xic4u:
Dudes, reread the Topics of those who reported they had a SD even with XXELLA.

ALL DIDN'T HAVE A FIXED KERNEL. THEY WERE USING XXELLA ROM BUT A KERNEL LIKE SIYAH WICH IS "NOT" FIXED

So please stop starting new rumors.

Taper di Tap with my S3 @180 days
[Galaxy S III General] mstevan:
Some people using xella kernel, but have SDS...

http://xdaforums.com/showthread.php?t=2060403
[Galaxy S III General] philicom:
Can you provide sources?
[Galaxy S III General] danarama:
It doesn't really matter. Please read my previous post about a page back
[Galaxy S III General] mstevan:
Nice explanation, didnt read before my posting. Think you are right.

I personaly use a Perseus, none of confirmed sds with that kernel.
[Galaxy S III General] pickandwhammy:
Agreed (and nice analogy!) but since most deaths are happening after the 4th month, can't we assume that devices that have been on unpatched kernels for less than a month - maybe a couple of weeks - are very unlikely to have suffered enough damage for the NAND to die in the near future?
[Galaxy S III General] DonHuan:
Who knows? We can only guess and wait.
[Galaxy S III General] danarama:
If the fixes do actually work, we should start to see the issue gradually disappear into the past. We cannot assume anything about the timelines though as 4.1.2 roll out is still occurring.

Logic would tell us that the shorter exposure to excessive wear will likely manifest itself in a longer time (excessive wear + normal wear to the point of failure) or not at all. The problem is, there is still the possibility.

4 months 4.1.1 = failure

4 months 4.1.2 = no failure

But....

2 months 4.1.1 + 8 months 4.1.2 = ?

1 month 4.1.1 is less likely to fail than above but not beyond the realms of possibility.
[Galaxy S III General] mstevan:
Little off topic: Note 2 also suffering from SDS. http://xdaforums.com/showthread.php?t=2092073... just read on their forums... My next communication device will be a pager. He is not suffering from sds...
[Galaxy S III General] pickandwhammy:
Hmm. Plus there's the whole problem of the issue not being universal, i.e., we can't say that all unpatched devices will die in this bracket of time. And of course, individual usage and pure luck come into the picture.

This is worse than quantum Physics!
[Galaxy S III General] danarama:
Yes indeed that. Not all VTU00M 0xf1 s3's will die because its a certain firmware release date only affected. It becomes cloudier and cloudier.

I think the best we can all do is ensure we're up-to-date then we can get on with our lives :)
[Galaxy S III General] pickandwhammy:
Word!
[Galaxy S III General] yahyoh:
i don't know why some people still using unsafe kernel - recovery

there is sticky thread in the top of general forum to know if u r safe or not :eek::eek::eek:

i bet i will come tomorrow with one (or more ) still using syiah 1.8.6 with died phone :silly::silly:
[Galaxy S III General] DonHuan:
No.
[Galaxy S III General] danarama:
No. Its a 16GB chip
[Galaxy S III General] mjb:
Fw Rev Fx1 is not valid. The revision is in hexadecimal, which is represented by the characters 0-9 and A-F. The first two characters are usually "0x", which helps to disambiguate between hex and another number base. (for example, "23" vs. "0x23").

So, to answer your question, the affected revision is 0xF1 (0xf1 is the same thing, case has no significance to hex values)
[Galaxy S III General] rezapatel:
The word is probably depreciate?

But I hear what you're saying, I am from Pakistan and N4 is almost 650$ here.

Sent from my Galaxy S3
[Galaxy S III General] Scarface1991:
You have received reports where s3`s died on completely Stock XXELLA Firmware using the Stock XXELLA Kernel or with a fixed Kernel?

I do believe you but why is there not one report in this thread where a device died with a fixed custom kernel or a Stock Kernel with the fix? We need those reports so that people like Entropy512 can examine this because for now the status is: you are practically "safe" if you use a fixed kernel and a fixed recovery.
[Galaxy S III General] liamR:
So let say ELLA (or any 4.1.2 kernels) does fix the problem, but if it's really a wear problem, that means who ever bought the S3 lately and update its rom to ELLA will be just fine and everybody else that "infected" should hope that their S3 will die within warranty period else they're screwed.

That being said, anybody interesting of buying a S3 in mint condition (224 days and still kicking) ? ;)
[Galaxy S III General] behemot24:
I will sell mine too as soon as they repair it and buy some other brand, cause i hear that samsung note 2 also has the sds.
[Galaxy S III General] Scarface1991:
Awesome! :) Siyah 1.8.7 will be released very soon
[Galaxy S III General] hermeson:
Guys, where can I download the kernel? Coz I downloaded the ELLA, but the kernel still the same.
[Galaxy S III General] vibsOveebs:
reply

Use yank kernel and you'll be fine
[Galaxy S III General] chimas16:
Is there any solution if my S3 is already dead? I have try to flash via odin and always get a error message. The only way is to send it to samsung or is there any other way?
[Galaxy S III General] offgrey:
There is no other solution other than sending it back to Samsung.
[Galaxy S III General] vibsOveebs:
Reply

Yeah you need to send it to Samsung. Just curious, how many months of usage broke it broke? And were you rooted, I'm scared for my s3
[Galaxy S III General] shethsa:
Isn't it high time Samsung comes out in the open on this issue. This thread is now 2 months old and the issues aren't dyng down. Instead we are getting into the Stockholm syndrome praising Samsung for releasing software fixes which don't see to be holding up and treating us like guinea pigs for their flagship phone.
[Galaxy S III General] kipue:
Well, according to the eMMc check application, I m with the faulty mem chip.

I m running temasek's unnoficial for a while now, always up to date, and upgraded syiha to 1.8.7.

If anything ever happens, I ll let you people know.
[Galaxy S III General] nj1266:
I did the eMMC chip check and I got:

Type: MAG4FB

FwRev: 0xf1

So it is a different chip type but the same affected firmware. What am I to expect from this?

This is the third S3 that I got. The new one had dropped calls. The second one had SDS. And this one is refurbished. I would thing that the motherboard was changed on this last unit.

Sent from my iPhone 7
[Galaxy S III General] pickandwhammy:
iPhone 7?!
[Galaxy S III General] Product F(RED):
I just thought of something. To add to my argument that bootloader only exists to void warranties and doesn't actually solve anything, ponder this:

If a bootloader can only be flashed through ODIN, why would Samsung release it in an official OTA?

Easy: Because only people who root their devices would use ODIN, and only those people would have their warranties voided by the bootloader. We don't take OTA's. We flash everything manually. That's why they did this.
[Galaxy S III General] jnr21:
You know that we can change tapatalks "sent from..." signature manually... ;)
[Galaxy S III General] pickandwhammy:
LOL, yes, but why put that?! Is it a satirical viewpoint on duality of human nature, or is it just moron-logic? :P

---------- Post added at 11:43 AM ---------- Previous post was at 11:41 AM ----------

That might not be true: Samsung service centres also flash devices via ODIN.
[Galaxy S III General] sak500:
Well what do u think? S3 features would probably end up in iphone7 and then they will claim its their tech and will sure samsung.
[Galaxy S III General] mjb:
Where did you get that idea?

---------- Post added at 07:54 PM ---------- Previous post was at 07:39 PM ----------

I don't think you can actually say that - I find it hard to believe that a given FW Rev would have more than one internal date - or that this bug only existed for one potential revision of the revision. I suspect that it's safer to just say that all VTU00M/0xF1 chips are affected, as since we don't yet have some printk's telling us what date our chips are we have to assume they're all the same.

This I can agree with! ;)
[Galaxy S III General] danarama:
I'm paraphrasing one of the devs who implemented the code. I foget which one. The fix code only executes if the firmware date matches one specific date.

Edit..

Originally Posted by AndreiLux

The patch additionally checks that the firmware date is 2012/04/13 and only applies the commands then.
[Galaxy S III General] nj1266:
It is just a joke. You know like I am posting from the future. Now can someone please help with the question that I posted.

Sent from my iPhone 7
[Galaxy S III General] kofiaa:
Are you on an international 16 gb I9300 s3? I've never seen the chipset you have.
[Galaxy S III General] nj1266:
No. It is a US unit. It is 16 gig dual core unit. I have read that the Note II has that chip set but with a different firmware.

Sent from my iPhone 7
[Galaxy S III General] danarama:
All we know is its VTU00M 0xf1 that is affected. We are not aware of any other chips.
[Galaxy S III General] JessyCute:
Hello.. Does anyone see this thread? http://xdaforums.com/showthread.php?t=2089302

XXELLA still have SDS problem.
[Galaxy S III General] pickandwhammy:
I couldn't even go through the whole thread, it's FILLED with n00b questions and conclusions. Left a bad taste in my mouth.
[Galaxy S III General] T0xic4u:
Where Do you read that SD is back on XXELLA?? All cases I read so far didn't had a fixed Kernel. Most of them thought, that it is ok to have XXELLA ROM and used an outdated kernel. There is absolutly no proof that SD is back.

Taper di Tap with my S3 @182 days
[Galaxy S III General] danarama:
The issue could have existed on the phone before the SDS actually happened. Proves nothing unfortunately.

To quote myself:
[Galaxy S III General] JessyCute:
Thank rootSU, My point is.. if there is any new solution or clue in the other thread, we gonna back to update this thread for discuss. ^^

My S3 already flashed Perseus Alpha31 and PhilZ Touch follow the lastest solution of this thread.

But I'm still paranoid, so I'm monitoring all new threads everyday if there is any news update.
[Galaxy S III General] mjb:
Right, I understood that, but the point still stands - we can't actually definitively say that there is more than one date on those chips - so it's safer to say "Unknown, but assume you're vulnerable.", rather than "some chips are not affected". Since we cannot (currently) retrieve the date in the chip, we just can't assume there's more than the one we know of.
[Galaxy S III General] pickandwhammy:
You're perfectly safe only if you've purchased your device after the fix had been released, and you never booted it up, flashed the patches straight-away. This is almost impossible.

So, since you're "carrying the virus" all you can do is wait and watch. It's going to be a long wait too, so be patient :)
[Galaxy S III General] mjb:
@rootSU: I'm not trying to pick on you, honest!

I also don't think you can say that either. We know next to nothing about what the fix to the eMMC firmware does, and if it's a bug like Entropy512 describes, then your analogy falls down flat - it'd be like you are still being exposed to radiation, but instead, your new radiation suit adjusts your DNA (but only while wearing it) so that the radiation has no effect on you.

The point I'm trying to make is this:

We don't know what the fix does, if it actually fixes SDS, or if it's completely unrelated. we can make a best guess, but we just cannot assume anything about what the consequences or effects will be.

We can have theories, sure, but we just can't state anything that could only be confirmed by knowing what the fix does.
[Galaxy S III General] hermeson:
Jessy, how do u update ur kernel? Cheers
[Galaxy S III General] JessyCute:
You can download .tar file for flash from this thread (http://xdaforums.com/showthread.php?t=1691401)

but let use PhilZ Touch 4 for your recovery, and u can download from this thread (http://xdaforums.com/showthread.php?t=2002953).

Cheers. ^^
[Galaxy S III General] pickandwhammy:
Okay so if both of you are agreeing on the same point: that there is nothing we can do but wait, WHAT'S THE BLOODY PROBLEM!?
[Galaxy S III General] Scarface1991:
A bootloader can also be flashed through CWM, you don't need Odin for that.
[Galaxy S III General] hermeson:
Thanks... I am going to try, if something goes wrong I will txt u... Ta
[Galaxy S III General] 17RoiDavid:
hi guys have you ever heard about SDS with ELL4 kernel or it's just like ELLA?
[Galaxy S III General] Plymouthbiker:
Plugged mine in on Friday night. It was running a little slow. Woke up on Saturday morning went over to the phone and it was displaying the Samsung Galaxy S3 splash screen that you get when you boot it up for the first time and wouldn't do anything else. Booted it up to the download screen and it wouldnt state what model the phone it was. I've heard this means the motherboard is dead.

Had the phone for about 6 months. From looking at how many people are going through this, I think Samsung have a very serious issue going on.

Off to the carphonewarehouse I go today then...... :mad: