yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] montage mahal:
Appears like all 4.1.2 based i9300 builds will have the fix as said in the first post. If so then why are samsung also pushing 4.1.1 to other countrys. Why would they do that without a fix?
[Galaxy S III General] danarama:
Best just to go full official via sammobile.com imho
[Galaxy S III General] strikoo:
Because SDS fix is just a myth
[Galaxy S III General] danarama:
Maybe too big a transition to go from 4.0.4 to 4.1.2 by OTA?
[Galaxy S III General] montage mahal:
Think it's also too big a transition for samsung to make an official statement :)
[Galaxy S III General] zadusimple:
Can someone suggest what will be the consequences of Flashing AOSP based rom and kernel. Will It have fix for the SD?
[Galaxy S III General] gadgetcraze:
This is all getting too confusing and risky. How can Samsung be so irresponsible? High time there was an official statement about this rather than stupid rumors from Sammobile
[Galaxy S III General] danarama:
Yes if its in the list in post 1
[Galaxy S III General] brouwerchris:
http://tweakers.net/nieuws/86386/samsung-komt-met-update-voor-probleem-defecte-galaxy-s-iiis.html

Statement of Samsung about sudden death,Anne ter Braak of Samsung says : "Samsung is aware of the SDS problem,it is caused by a firmware bug,and will be solved by a firmware update in the near future." She never said this was the XXELLA update,this is Sammmobile's statement based on their "sources",maybe their source is the quoted interview of Anne ter Braak on Tweakers? Only Sammobile knows their source. On 3.1.2013 Androidpit.de quoted a German Samsung PR statement similar to the one on Tweakers on 2.1.2013.Also without referring to XXELLA release.So outside Samsung nobody knows anything for sure.
[Galaxy S III General] pickandwhammy:
That's okay - providing an OTA firmware update is a very risky idea, they probably released the LLA kernel as a temporary fix till they Murphy-proof the firmware patch.

Though, considering their original quality check standards with the S3, it's ironic they're being so "careful" now :P
[Galaxy S III General] pride_kr:
Hi, I was reading the OP....

Considering I am a noooob....

My question is... Im on Sotmax V13.... but I didnt wanted to flash Yanks kernel... so I on stock

Am I considered ~safe~ ??

Thanks in advance
[Galaxy S III General] magician369:
So if i want to buy a new galaxy s III,how can i be sure it dose not have this problem.
[Galaxy S III General] quebec1:
i installed omega rom v37. This rom based on the latest release of android xxellc and has xxellc kernel.

I installed the recovery PhilZ Touch 4.00-b04 .

I wanted to know if I am saved by the sudden death so I have to change the kernel?

sorry for my english
[Galaxy S III General] T0xic4u:
Buy 32GB-Version or one that has not affected Chip.

Taper di Tap with my S3 @181 days
[Galaxy S III General] guerouig:
as unbelievable as it may seem, folks on sammobile do not feel so much concerned by the sudden death issue, although they are over a million members!!!! I tried hard to get reactions and the only one who bothered was of the view that "since samsung are repairing on a no question asked" he does not feel so much under pressure.
[Galaxy S III General] danarama:
What kernel does sotmax come with?!

What recovery do you have?

Given you need kernel and recovery for fix, this is a good starting point
[Galaxy S III General] danarama:
Post 1. Custom roms section. What's the first on the list?
[Galaxy S III General] sebarkh:
If error then remove card. No Emmc no problem.:)

Sent from my washing machine...straight from the tumbler...
[Galaxy S III General] stephg27:
Hello,

I follow the SDS topics on XDA since nearly one month now. Mainly because my S3 bought at the very end of 2012 August contains what is called now "the infamous VTU00M eMMC with version 0xf1" which is potentially candidate to SDS issue. For the moment, no problem with my S3 but I remain vigilant.

But here is something I wonder about "update 7", SDS fix and Exynos Exploit.

Currently my S3 is fully stock (always updated using Kies, never rooted) and has the XELL6 ROM.

What I understood reading the first page of this topic is that the XELL6 should contain the "Update 7" fixes and so the presumed SDS fix. And I also read on XDA that Exynos Exploit fix comes with "Update 7".

Starting from that, I guess that, if the XELL6 contains the "Update 7" fixes, then it should also contains the Exynos Exploit fix, right or not?

Nevertheless, I installed on my S3 the following apps to test if the Exynos Exploit is then fixed on my S3 with XELL6:

Exynos Mem Bug Checker (published by Lowlevel Studios on the Play Store)

Voodoo Anti ExynosMemAbuse (published bu Supercurio on his website project voodoo)

Both of these apps tell me that my S3 is vulnerable to the Exploit!

So, either I miss something?! or these applications are not reliable to test Exynos vulnerability?

Thank you very much for the explanations you can provide me to understand this!

Nota Bene: Notice that I don't want to use the Chainfire application because I understood that this app does not have a "test" function; we only know by this app that the system is vulnerable if the app managed to get root using the exploit. But I do want to keep my S3 status as "Normal". So I don't want to use the Chainfire to test my XELL6 stock ROM ;).
[Galaxy S III General] MuertoKo:
You are not safe, go with LLA

And this comes from samsung knowing about exynos bug after than SDS, but still current SDS fix is just a maybe ;)

Enviado desde mi Nexus 7 usando Tapatalk 2
[Galaxy S III General] MIKEMON:
Yes LL6 has a fix in itself, it should be fine, but does not solve the problem, we'll see what the future.
[Galaxy S III General] T0xic4u:
Wrong.

About those apps, they don't tell you the truth. Don't worry, the kernel is fixed

Taper di Tap with my S3 @181 days
[Galaxy S III General] MIKEMON:
Skladem:

Následující ROM obsahují jádra a využití s Aktualizovat 7 "Opravy" aplikované. Máte-li jeden z nich, oficiálně (a NIKDY kořeny), považují sami sebe "Safe"

XXELKC

XXELL1

XXELL4

XXELL5

XXELL6

XXELLA

XXELLC

Objeví se jako všichni 4.1.2 založené i9300 sestavení bude mít opravu.
[Galaxy S III General] MuertoKo:
I know just hate people asking things that are un OP... So even if I dont cause him issues at least I make him work a bit...

Oh and btw guys, I'm not sure he is protected against exynos memory issue, this post is about SDS ;) wasn't LLA the first with exynos memory fix? I don't really care as I just usually use latest but you should always try to guide people to the most safe possible and not answer directly with a lack of reading :)

Enviado desde mi Nexus 7 usando Tapatalk 2
[Galaxy S III General] JuniorLima:
I wanted it as a device carrying overnight with no use, and a sudden, can corrupt data and cause a bug in the firmware EMMC?

---------- Post added at 07:27 PM ---------- Previous post was at 07:11 PM ----------

Hello, I'm still noobs in the subject, but I am an owner of S3 that is concerned and trying to learn to not take damage. I'm reading the whole topic, since the first post, but must continue to have at least a sense of what is BOOTLOADER .... What is it and how is the bootloader?
[Galaxy S III General] stephg27:
Well... Thanks guys for your replies ! ;) Well finally, reading your replies, I understand that maybe the apps I use to test Exynos bugs are not reliable (? :confused:). But also, it seems it is not absolutely clear that XELL6 contains both fixes for SDS and Exynos. Or else: XELL6 contains SDS fix from "update 7" but maybe not Exynos Exploit fix which would be only since XELLA ?
[Galaxy S III General] T0xic4u:
It contains both fixes, but nobody really knows right now, if SD is finaly fixed. Only time will tell.

Taper di Tap with my S3 @181 days
[Galaxy S III General] MuertoKo:
Exactly like this :) best way to test is trying to root with Chainfire app, if it fails its fixed, if you get root then its not. You can simply unroot after in the same way in that case ;)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] stephg27:
Yes ;), I understood that. If only also could communicate on this ! :rolleyes:

Yes, but I don't to trying to root with Chainfire app, even if I can unroot after the test. Because, as I read on the topic of the Chainfire app, if the app manages to use the Exynos exploit to root, then the status of the device will be set as "modified" and I do prefer to preserve the "normal" status of my S3 ;).
[Galaxy S III General] T0xic4u:
Siyah 1.8.7 is online, wich contains the SD-Fix.

http://www.gokhanmoral.com/

Taper di Tap with my S3 @182 days
[Galaxy S III General] JuniorLima:
What is firmware?
[Galaxy S III General] skorzo:
mmm I think I am missing something.

I rooted my phone 6 months ago, and I have rooted it every time that I flashed a new Rom.

Recently I flashed a fresh XELLA so I have stock (fixed) kernel, stock (fixed) recovery.

Now I have 2 options for root:

CFRoot -> Which does not incluces kernel, so I am preserving my stock (fixed) kernel

or

CF Autoroot -> I ..THINK that Autoroot does not affect the Kernel ....

So, Why are you advising rooted terminal users to flash a custom fix kernel to be safe??
[Galaxy S III General] odoto:
I'm not sure if that's entirely true... I'm on 4.1.2 XXELL4, so according to the OP I should be covered SDS-wise... but I just tried the ExynosAbuse app to verify that the exynos bug is fixed... and it is not... I successfully rooted my phone via that app. And, as a nice surprise, the device status is still "unmodified" :)
[Galaxy S III General] Scarface1991:
The awesome thing is that the Siyah CWM recovery also contains the fix, so PhilZ CWM recovery is not the only one "safe" now:
[Galaxy S III General] odoto:
awesome :)

hopefully a bunch of users will try it then, so we can figure out if maybe only eMMC up to a certain production date are equipped with the bloody 2012/04/13 firmware...
[Galaxy S III General] qavro:
i have 1.8.7+ but i think i am a bit "slow"

if i have only one rom, i can use "hijack" ? or only for the ones with dual boot ?
[Galaxy S III General] priyana:
Who are you agreeing with, and which thread of yours is closed by who?
[Galaxy S III General] Scarface1991:
Should work without any problems even with one ROM
[Galaxy S III General] skorzo:
Autoquoting...

First post says

"The following ROMs include a Kernel and recovery with the Update 7 "Fixes" applied. If you have one of these, officially (and NEVER rooted), consider yourself "Safe"

XXELKC

XXELL1

XXELL4

XXELL5

XXELL6

XXELLA

XXELLC

Appears like all 4.1.2 based i9300 builds will have the fix."

I have rooted lots of times my device. My recently fresh flashed XXELLC was rooted flashing CF-Root and then Philz Recovery.

Why should I be unsafe due to rooting ?? That "and NEVER rooted" is killing me :(

Thanks!!
[Galaxy S III General] JuniorLima:
What would be the difference between CWM Recovery and being both safe? Which is the best? What is the difference between him? What deo installs?

---------- Post added at 11:47 PM ---------- Previous post was at 11:42 PM ----------

How so? As the damage could have been done before? no death occurs in a sudden? or he is slowly dying? ..
[Galaxy S III General] gadgetcraze:
Buy a 32 GB. Apparently those are safe.
[Galaxy S III General] JuniorLima:
that wear you talking about? how is this wear?
[Galaxy S III General] philgalaxs3:
Hi

Don't understand the "and NEVER rooted" too , but sure that root is NOT a problem . don't be afraid neither killed .
[Galaxy S III General] priyana:
I think the NEVER rooted part is to say that if Kies or OTA is the one installing the updates to you, you are safe.

Otherwise, you could be just a supposedly handy person and updated your ROM to one of the safe ROM using CWM or whatever and your recovery is not safe.
[Galaxy S III General] jin1992:
Re: [Important] Sudden Death Fix - Are you covered?

When booting into download mode, system status is still shown as custom or does sds even prevents u from booting into download mode ?
[Galaxy S III General] pickandwhammy:
If your phone has died you can't boot into anything. That's quite obvious, if you just spend a moment thinking about what the word "death" implies.
[Galaxy S III General] jin1992:
thank you for the quick reply, i was reading up and i saw posts about people being able to boot up to download mode(dont know if its a totally different issue) but they are unable to flash anything via pc odin because of a pit error or something.
[Galaxy S III General] pickandwhammy:
Hmm, it's possible that the memory "sectors" from bootloader and ramdisk to ODIN (which is like fastboot) are fine while the wear has happened elsewhere. Even if it's going to download mode, it's pointless since you can't flash anything. Ever. :P
[Galaxy S III General] mjb:
[Please excuse the excessive quoting, but I think it's needed for context]

Try reading Entropy512's post on this subject. Basically, the wear will still occur, but at a certain point, the amount of wear will not trigger a bug in the eMMC firmware with the soft-fix applied.
[Galaxy S III General] danarama:
To all those querying why you cannot be considered safe unless you never rooted (on stock)

Rooting typically gives you a custom recovery. You may have flashed a custom kernel. I don't want those people falsely believing they are safe.

To be safe and stock requires a fixed recovery and kernel.

Let me reword it
[Galaxy S III General] tqgia2:
CF-Autoroot keeps you on stock recovery and kernel though, which would make you safe right?
[Galaxy S III General] danarama:
Yes, if you rooted one of the official builds mentioned in the first post. If you rooted an older version then flashed a new rom (only) for example, your recovery wouldn't be safe.
[Galaxy S III General] pickandwhammy:
There might be some tangents going here. I think what rootSU meant was this:

- You are only safe if you have only been on safe ROMs (stock/custom) and safe recoveries (stock/custom)

- If you have spent any time on an unsafe ROM, be it stock or custom, you aren't immune to damage

Think of it as radiation exposure and the safe ROMs and recoveries being hazmat suits (brilliant analogy by someone, I don't remember who! EDIT: It was rootSU :p ).
[Galaxy S III General] danarama:
That would be me :)

http://xdaforums.com/showpost.php?p=36664104&postcount=3315
[Galaxy S III General] T0xic4u:
@rootSu

Would it mind you to edit post 1??

We now have a second fixed custom recovery. It is the siyah recovery. You get it when you highjack the installed recovery.

Taper di Tap with my S3 @182 days
[Galaxy S III General] pickandwhammy:
Do you mean "jailbreak" instead of "highjack"? Either way the correct word is "flash over".
[Galaxy S III General] qavro:
he meant the hijack option in Syiah kernel. Accesible from Stweaks
[Galaxy S III General] T0xic4u:
Yes, sorry "hijack" not highjack.

Taper di Tap with my S3 @182 days
[Galaxy S III General] pickandwhammy:
I see. So it flashes the "2nd ROM Utils" - whatever that is - to the recovery partition, thus erasing "recovery" entirely. I can't think of a situation where it would be useful, unless the "2nd ROM Utils" can't be accessed in any other way.
[Galaxy S III General] qavro:
True. That's why i am waiting for a "patched" CWM...
[Galaxy S III General] mjb:
Oranav, could you use the same read function that's used to fetch the firmware date to read the entire firmware (while in the vendor specific debug mode)?

or is that what the code you've found does? How did you get on?
[Galaxy S III General] tiktakt0w:
?

Will Samsung Void my warranty if my custom binary count is 0 while System status is "custom".....noob question indeed and current binary is : Samsung Official?
[Galaxy S III General] Scarface1991:
Yes they could, actually I have the same problem. System status custom means that you have messed around with the system folder in some kind of way which means of course that you have root. So yes this could mean that you won't get warranty.

But people were able to revert the system status to official although using a custom rom and a custom Kernel.

Visit the how to flash old bootloader thread for more info.
[Galaxy S III General] Oranav:
http://xdaforums.com/showthread.php?t=2096045

Short answer: The code that fetches the firmware date is the code for getting a "Smart Report"; it can't be used to read the eMMC RAM.

However, I found other code that can dump the eMMC RAM. I'm just afraid to run it on my device since I don't have a spare one.
[Galaxy S III General] Pietrone94:
I flashed an old bootloader a week ago. The i put siyah and 2 roms and all were right (the passage were: deep clean 1-->root-->triangle away-->flash fw stock ita-->root-->triangle away-->roms)

I had counter 0, no "exclamation mark", and in download mode everything right: all official samsung...

Then i continued flashing roms and all kept roghe except for system status which is "custom"

The only way to have it original is to flash a fw stock but this means that i can't flash roms because it will return "custom"....so...what to do??

Personally i think i will keep it and if my s3 will have sudden death...hope samsung will repair it in warranty!

Inviato dal mio s3 da Resurrection Remix 3.1.4 :D
[Galaxy S III General] xanthrax:
basically according to this http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:31999L0044:EN:NOT

ALL EU members should benefit for 2 yrs guarantee NO MATTER WHAT SOFTWARE WE USE .

as long as Samsung cannot prove that any kind of SDS or whatever ... was determined by a different app/software/rom that he doesn`t accept it , we must be covered !

-=-=-

there is a bilingual option , switch to it for easy understanding
[Galaxy S III General] Oranav:
I've patched Siyah 1.8.7 to export movi_ops via sysfs, so you can know whether your device is affected or not.

Flash the attached kernel, then do "cat /sys/class/block/mmcblk0/device/movi_ops". 2 means affected, 0 means not, other values mean my code has a bug. :)

Re-flash your everyday kernel afterwards. Don't use mine.

I take no responsibility whatsoever if anything happens. Do it with your own responsibility.

* I'm refactoring Samsung's code to use the mmc quirk mechanism properly (Linux conventions); after I'm done, I will submit this as a patch to the common kernels (Siyah, Perseus, CM etc.) and maybe to mainline, so you won't need a special kernel for this.
[Galaxy S III General] dimi22:
Guys i have the Xella stock rom atm.:laugh::victory: BUT BUT :confused: HOW CAN I ROOT WITHOUT CUSTOM KERNEL/?
[Galaxy S III General] qavro:
cf-auto root?
[Galaxy S III General] tcpma:
where is the truth?

This thread says: stock rom from XXELKC to XELLC without root or stock rom from XXELKC to XELLC with root and one of 5 custom kernel and custom recovery PhilZ Recovery V4 or custom rom based on stock rom from XXELKC to XELLC

An other thread ( **Ultimate GS3 sudden death thread**) says: stock XELLA or custom rom with custom kernel Perseus Kernel V30.1+custom recovery PhilZ Recovery V4
[Galaxy S III General] Pietrone94:
is this to watch if you are covered from sudden death??
[Galaxy S III General] qavro:
more like if you are vulnerable, as we don't really know if the last release really fixes the SDS totally...
[Galaxy S III General] dimi22:
doesn't work for this XELLA kernel with SdS fix?
[Galaxy S III General] Pietrone94:
Thanks mate :)

SDS means?? Sudden (S) Death (D) ......(S)?? :D
[Galaxy S III General] qavro:
Sudden Death Syndrome
[Galaxy S III General] Pietrone94:
Thanks again mate ;)
[Galaxy S III General] danarama:
Is it stand alone or can it only be used with the siyah kernel? If its stand alone, is there a download link?
[Galaxy S III General] xanthrax:
is not standalone , it came with siyah only
[Galaxy S III General] danarama:
In this thread, we have decompressed kernels going back to ELKC and found the fix contained within.
[Galaxy S III General] T0xic4u:
It's not stand alone, but you could mention it. If someone uses siyah, he could also use its recovery.

Taper di Tap with my S3 @182 days
[Galaxy S III General] danarama:
Is there a Recovery version number?
[Galaxy S III General] xanthrax:
CM - based Recovery v6.0.1.4 Siyah
[Galaxy S III General] tcpma:
ok, understood. last question, why do you suggest 5 custom kernel but in the other only Perseus?
[Galaxy S III General] danarama:
I don't know what you're talking about. Sorry.

There are 5 custom kernels that are "fixed". These are listed in Post 1.
[Galaxy S III General] Stromma:
Sorry for this noob question, but I can't figure out wether I'm safe or not.

I believe my phone is one of those that is at risk. I'm running rooted stock 4.1.2, downloaded from Sammobile and flashed via Odin:

I don't think I've downloaded or installed any unsafe apps or apk's, at least not that I'm aware about. Should I consider myself safe or do I need to worry?

// Strömma
[Galaxy S III General] Pietrone94:
guys i know that to be "safe" of SDS you must have the kernel fix but also the recovery fix...

siyah 1.8.7 has the kernel fix, but the recovery fix??

thanks
[Galaxy S III General] danarama:
You have the stock kernel so that *should" be fine. I dont know what recovery you have though. If you used CF-root, you will have CWM and will need to replace it.

Post 1 has a list of recoveries you can use.
[Galaxy S III General] xanthrax:
so , siyah has a build in recovery

when you flash the kernel you`ll keep your previous safe recovery but alse you can use his own recovery by hijacking it from its tool stweaks

after reboot you`ll get his recovery i mentioned above , siyah v6.0.1.4

-=-=-

hijacking it it seems to be uselss somehow , gokhan provided this option `cause many users requested .

my recommendation is to use as rootSU said above a safe recovery from 1st post
[Galaxy S III General] tcpma:
In "Ultimate GS3 sudden death" thread they suggest to flash only Perseus kernel but if you checked that 5 kernels in Post1 of this thread are fixed, all right
[Galaxy S III General] Pietrone94:
ok but...for example:

now i have siyah 1.8.6 with his recovery...

if i flash siyah 1.8.7 then my recovery will be the safe one??
[Galaxy S III General] Stromma:
I believe I used CF-root via Odin, but I'm not sure. How can I check this?

// Strömma
[Galaxy S III General] xanthrax:
1st - are you still using 1.8.6 !?! ... that`s dangerous as we talk about it for some days now ..

2nd - if you have flashed a safe recovery and now you want to flash siyah 1.8.7 the recovery will stay there , no change . it will change if you will hijack it to his recovery v6.0.1.4 which according to gokhan is safe also
[Galaxy S III General] Pietrone94:
yep guy, now i put 1.8.7 ;) thanks..all clear ;)
[Galaxy S III General] EViollet:
*sigh*

For goodness sake, NO.

You have 3 different software parts on the GS3:

* bootloader

* recovery

* rom

The bootloader appears not to have the fix. NO bootloader is currently known to have the fix. So, any version will do. It won't protect you.

There is currently ONE known recovery that includes the kernel that fixes the SDS : philz recovery. No more.

ROM. This is what you're running on your phone. It comes bundled with a kernel. The SDS fix is included in the kernel. If you use the latest Siyah kernel, then you're safe. Up until the moment you boot recovery. Then you depend on the recovery you currently have on your phone.

Siyah kernel, however, has a peculiarity: it comes bundled with it's own TEMPORARY recovery that is used to manage 2 ROMs.

If you reboot in recovery from the Siyah STweaks tool, then you'll be using the Siyah recovery, which is correctly patched.

If you reboot in recovery from the ROM (or any other means of rebooting to recovery), you'll be back on your default recovery.

You can also "hijack recovery" from the Siyah STweaks tool. This will overwrite your current recovery with the Siyah recovery. And you will be protected whichever means of rebooting to recovery you choose.

I hope this is simple enough and will prevent all future questions like this.

Regards,