yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] xInfinity12:
Just Flashed PhilZ Touch 4 recovery and the latest Perseus Kernel. Just wanna make sure that I'm safe for now? and When I Turn On My Device There is this red ! Thing on the upper Left. Is that Normal?
[Galaxy S III General] Scarface1991:
It means that you are using a custom ROM or/and a custom Kernel. When you go into download mode, then you will see that the counter should be above 0 which also means that your warranty is now void.
[Galaxy S III General] corrsea:
Sotmax Ultimate V13 has the fix. Both stock ELLA kernel and Yank555 V3a included (chose in aroma)

http://xdaforums.com/showthread.php?t=1944035

[ROM][4.1.2] [XXELLA][Sotmax Jelly Bean Ultimate Stock V13] GT-i9300 *stable as rock*

ROM Sotmax Ultimate V13

Kernel Yank555.lu-V3a
[Galaxy S III General] zyclops1:
Me too
[Galaxy S III General] xInfinity12:
I think Thats normal then? I have the PhilZ touch recovery 4 and perseus latest kernel with a base band of I9300XXDLID and Android Version 4.1.1 Iam asking is Am I safe now on the sds?
[Galaxy S III General] ducky1979:
If you bought the phone new then you are covered under Samsungs 2 year warranty. Most people take their phone back to the carrier but Samsung also provide a way to have a repair done. It's worth looking at their website to find either your nearest repair center or a number to call to arrange a repair if you have to. So don't despair. You should be covered.
[Galaxy S III General] Scarface1991:
It is normal and yes you should be safe.
[Galaxy S III General] washpota:
The confusion is about flashing a non-Indian official ROM (UK) on an Indian S3 via Kies by putting the phone in download mode. (Method 2 in this post: http://xdaforums.com/showpost.php?p=36167846&postcount=1)

My worry is, if I flash a UK official ROM on an Indian S3 (since there is no official Indian XELLA yet), would they void my warranty?
[Galaxy S III General] :
funny how every brick is caused by this "sudden death bug", according to every people who had read about it, after or before his/her phone bricked... we can't forget that one fix doesn't make such thing as a miracle, and if you bricked your phone, you can't say that if you had flashed those "good" kernels/recoveries/bootloaders your phone wouldn't had bricked.
[Galaxy S III General] sebarkh:
Does this explanation makes sense according to you? If recovery uses kernel, and the kernel is patched then any recovery would be ok...

Sent from my washing machine...straight from the tumbler...
[Galaxy S III General] drakester09:
He never said that is the same, it has its own kernel inside, thus, it needs to be patched and updated as well.
[Galaxy S III General] hypergamer1231:
I have a 32gb s3 and the chip is

Type : VWU000M

Date 06/2012

FwRev : 0xf0

is this an unaffected chip...And if yes then does it mean am safe if I use any rom...now I am on Stock non rooted XXella

Please help guys
[Galaxy S III General] :
Let's take Siyah's kernel, for instance: you can flash it as a kernel and as a recovery at the same time. It's a kernel and a recovery. But let's take Perseus kernel: it's only a kernel, and you can't flash it to recovery, because the recovery isn't included. You can even flash Perseus as a kernel and Siyah as a recovery, but at the Siyah's recovery you will be also using Siyah as the kernel, doesn't matter which kernel you install.

In less words: the recovery is built from a separated kernel, System = kernel 1 (boot.img) / Recovery = kernel 2 (recovery.img) and by flashing a boot.img you are not changing the recovery's kernel.
[Galaxy S III General] danarama:
Re: [Important] Sudden Death Fix - Are you covered?

Fair comment man :)
[Galaxy S III General] aureliomilitao:
is true

after install 4.1.2 rom, the Sudden Death Fix forever ???
[Galaxy S III General] BossStang:
As long as you stay on a safe kernel.
[Galaxy S III General] Rafa91:
Re: [Important] Sudden Death Fix - Are you covered?

Perfectly clear thanks :)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] fredy204:
thanks
[Galaxy S III General] nikolaz111:
check in settings

The eMMC version can be checked in the phone settings?
[Galaxy S III General] kadopt:
No, use this https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
[Galaxy S III General] avi.laza:
and recovery
[Galaxy S III General] owl74:
there were a few instances here though that even after flashing a safe rom/kernel/revovery, the phone still had SDS so it also depend wheteher there was already a little damage to the unit before flashing the safe rom/kernel/revovery.
[Galaxy S III General] avi.laza:
i guess it's possible
[Galaxy S III General] danarama:
It is possible the damage is already done, sure but these instances above you mention, I've still never seen one. Or at least never seen one which I have not managed to dismiss as there was something suspect or inaccurate or actually not safe there.
[Galaxy S III General] pickandwhammy:
Corrigendum? :p
[Galaxy S III General] owl74:
I am 101% sure I read somewhere about someone with 4.1.2 and still the phone died... I can't remember which thread though. I think I replied asking how long he had an unsafe rom/kernel/recovery, and I vaguely remember you also commented...
[Galaxy S III General] danarama:
All 4.1.2 SDS that I have commented on, I have dismissed as not being proof of anything for one reason or another
[Galaxy S III General] sumsar99:
I have two SGS3 with exact same setup and one of them got hit by SDS yesterday.

Android Version 4.1.2

Baseband version I9300XXELKC

ROM FoxHound Rising 1.6

Kernel Siyah 1.8.4 <--- (I assume this was the reason for SDS right)

Build number JZO54K.I9300XXELKC

On the one phone that I still have left working I have now updated the following:

Android Version 4.1.2

Baseband version I9300XXELKC

ROM FoxHound Rising 1.6

Kernel Siyah 1.8.9 <--- (SDS safe)

Build number JZO54K.I9300XXELKC

I have also updated the CWM Recovery to 6.0.3.0 (SDS safe)

What I now wonder is, do I also have to somehow fix the bootloader (suggested by AndreiLUX) to be 100% safe or does the XXELKC ROM which it looks that I have, mean that the bootloader is already SDS safe?

Btw, thank you OP for a superb collection of info regarding this issue. To bad I didn't know about this in time.
[Galaxy S III General] danarama:
Don't trust cwm. Read page 238 of this thread. Install philz.
[Galaxy S III General] sumsar99:
Ohh OK, will read asap. But besides that do you think the bootloader is ok if I have a XXELKC ROM?
[Galaxy S III General] danarama:
Yes. All 4.1.2 bootloaders should be.
[Galaxy S III General] RohanM:
Permanent fix for SDS.

Hello All,

Permanent fix for SDS. Well I don't need to fear for SDS any more as I SOLD my sgs3 today.. yuppie... :good::cyclops::):angel:

So I am unsubscribing this thread now. Bye Bye to all.
[Galaxy S III General] NightOrchid:
Hi guys

Im in UK, Just got my new boxed S3 yesterday and Im reading this.. cant believe this, when I got the phone home and connected to wifi, i recieved 5 OTA updates, eventually ending up on 412 XXEMC2 (Mon Mar 11), but I do have the insane chip.

As this is my main phone, I dont root or flash custom Roms, so am i right in thinking that Im safe from both the Exonyos Exploit bug and the Sudden death bug, also Am I safe to flash stock Roms or Modems through PC ODIN.

Cheers
[Galaxy S III General] sherlock5545:
If you are on the latest update and have the latest bootloader, you should be able to use Download Mode without problems, and therefore PC Odin.

Sent from my GT-I9300
[Galaxy S III General] NightOrchid:
Much appreciated, thank you. I got all 5 updates OTA which brought my S3 from 411 to 412 which looks like I have the latest BTU UK Rom It seems to be a trait with Samsung phones.. no matter what you buy... theres always Something,

Cheers
[Galaxy S III General] drakester09:
You are OK. :)

Even though your phone has the chip, having 4.1.2 and EMC2 makes you safe from the two flaws.

Enjoy your phone, despite the issues it's a great device. :highfive:
[Galaxy S III General] jay_m3:
Hi,

am on I9300XXELLA

Kernel ver : 3.0.31-742798

should i consider my S3 is safe?
[Galaxy S III General] danarama:
You should consider reading post 1 :)
[Galaxy S III General] jay_m3:
yes i did mate, be sure am the kind of person who reads before asking!! but i wanted just to make a confirmation from your side ;) and i got it ! thx!!
[Galaxy S III General] jeffnz:
You asked this on the other thread a while back and was given same answer.
[Galaxy S III General] zyclops1:
i want to root my device because my binery flash count is 1.

if i use CF-auto-root (stock recovery supplied with this) am i safe until i clear that 1 using TriangleAway.

only for 30 minutes :silly: :silly:
[Galaxy S III General] danarama:
If you want to be unrooted AND have official status, you must:

1) Re root (CF-Auto is fine)

2) Install and run Triangle Away

3) Reflash stock ROM to remove root from Download mode.

However, if you already have official bootloader XXELKC or newer, you must do it this way:

1) Re root (CF-Auto is fine)

2) Install and run Triangle Away

3) After you press volume up to reset counter, but before phone boots (when you see galaxy S3 splash screen) remove battery quickly*

4) Reflash stock ROM to remove root from Download Mode.

* This is because when it boots, it sets the counter again. Stop it booting, stops the counter.
[Galaxy S III General] sherlock5545:
You don't need to reset the flash counter to be safe, do you? Anyway, if you are with the latest update and root with Cf autoroot, there's no problem as it supplies the stock recovery, which is safe. If you don't have the latest bootloader, then use Triangle Away to reset the counter. That's it.

Sent from my GT-I9300
[Galaxy S III General] zyclops1:
i was on latest EMC2 FW,so i root it,then flash

1.Philz recovery

2.flash old ICS bootloader

3.reset the flash counter

4.again flashed the EMC2 FW

i think this method is ok :D :D

---------- Post added at 12:37 PM ---------- Previous post was at 12:32 PM ----------

another problem :crying:

after that system sates is custom

---------- Post added at 12:42 PM ---------- Previous post was at 12:37 PM ----------

sorry for the trouble guys finally all things are offcial :D thanks alot guys :D
[Galaxy S III General] -Rahimin-:
thanks for all this suggestions and all. i'll appreciate it
[Galaxy S III General] danarama:
You don't need to reset it to be safe. You do need it to return warranty status for other issues however
[Galaxy S III General] zyclops1:
Yeah thats why i did it :thumbup: ;);)
[Galaxy S III General] zyclops1:
have a question :silly:

if i root with this CF-auto-root (stock recovery supplied with this)

i have root and im safe,but no powerfull recovery.

is this true?????? :angel:
[Galaxy S III General] pickandwhammy:
Yes. If you want the optimum algorithm:

Flash stock ROM with safe bootloader

Flash CF-auto-root

Flash PhilZ or TWRP or any other safe recovery

Downgrade bootloader

Use TriangleAway
[Galaxy S III General] zyclops1:
Why downgrade BL????
[Galaxy S III General] pickandwhammy:
For counter reset (warranty).
[Galaxy S III General] corgar:
There's a way to trigger sudden death? I'm reading of a lot of People getting a brand new s3 with warranty.

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III General] danarama:
I don't think anyone got a brand new s3 for this.

Obviously the opposite of post 1 is unsafe but I cannot ethically tell you how to trigger sds
[Galaxy S III General] zyclops1:
I think I should stay on stock ;);););)
[Galaxy S III General] kadopt:
Stock? Like crapwiz? Nah. I'm using Temasek's CM10.1 with is custom kernel and ICS bootloader and I'm not going back!
[Galaxy S III General] Kjc99:
Hey guys just a quick question... I did ask this in Omega thread but I wanted another opinion.... I'm running Omega V43.2(XXEMC2) But I'm using an old theme and under Titanium backup it says my System UI is XXELL5 I know system UI doesn't affect Sudden death but I wanted to be completely sure so is it safe to use this old theme with this new rom if it changes the firmware of the System UI... Thanks for bering with me but I HATE SUDDEN DEATH SYNDROME
[Galaxy S III General] danarama:
The only thing packaged with the ROM to do with SDS is the kernel.

Theoretically if you could use a fixed jb kernel with ICS, you'd still be safe (but you can't)
[Galaxy S III General] pistoke:
I have the latest Omega v43.3 rom (XXEMC3) and the latest Perseus alpha35 kernel. If I understood you right, I should not get any freezes while using DFG even I have a buggy chip. Of course I'm thinking that older XXEMB5 isn't better than newer XXEMC3... ;) So, do I get any advantages if I use DFG? I tried it couple of times and my phone gets very slow for a while(counter stops). Nothing more. Is that normal? My phone have had some freezes and boot ups during it's life, but I don't know if it's SDS related or not.
[Galaxy S III General] JJEgan:
Nothing more. Is that normal? My phone have had some freezes and boot ups during it's life, but I don't know if it's SDS related or not.[/QUOTE]

Not usually .

Can be rom or kernel .

jje
[Galaxy S III General] pijindrin:
Seven months and still going...

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] aasimkhan30:
Ics Roms

is installing cm9 or aokp ics can cause sudden death
[Galaxy S III General] danarama:
It wont cause it (the cause is emmc firmware) it just can't prevent it.
[Galaxy S III General] junky4rd:
still confused

i don't know about SDS in mine SGS III

since i bought at june 2012 but still i don't get any SDS in my SGS III

only one thing that i got, my SGS always broke my microSD card.

but i have notice and replace mine to the samsung service center, that my board have been replace and have hardware revision

between june and now

at mine june product i get 05/2012

hardware

but

after replacement board i get 12/2012 hardware with ICS firmware

maybe sammy fix the hardware, the onlye thing that the engineer said always try to update your devices from PC not from OTA that could occur some hardware issue, but i haven't experience with SDS after and before replacement board except mine SGS III fix with microSD issue.

sorry for my bad english but maybe this is help you guys :)

last thing :D

and check your burn LCD sgs III, i have notice burn on mine sgs III, and it will shown up at blue wallpaper notification and tab bluecolour are really shown up :) replace it when still warranty :)
[Galaxy S III General] bortak:
Just a warning. Don't know if the SDS is covered by the MC2 firmware, but my girlfriends phone just died yesterday on it.
[Galaxy S III General] ginzo:
Could you please give us more info?

Kernel?

Bootloader?

Tapatalked from my Galaxy S3

Rom: Maya v3 XXEMC2 ♥

Kernel: Boeffla 2.10 beta2

Modem: XXEMC2

Operator: Vodafone

Recovery: Philz Touch
[Galaxy S III General] Kjc99:
I'd like to have more info as well... It is very unlikely that Samsung would take the SDS patch out of any new firmware
[Galaxy S III General] ginzo:
I agree, it is not possible that Samsung takes SDS patch out.....!

Tapatalked from my Galaxy S3

Rom: Maya v3 XXEMC2 ♥

Kernel: Boeffla 2.10 beta2

Modem: XXEMC2

Operator: Vodafone

Recovery: Philz Touch
[Galaxy S III General] danarama:
They wont have removed it but there has always been a chance that it was never 100% effective. We just don't know
[Galaxy S III General] ginzo:
I really hope that it is effective on new versions. . If not, oh my....

Tapatalked from my Galaxy S3

Rom: Maya v3 XXEMC2 ♥

Kernel: Boeffla 2.10 beta2

Modem: XXEMC2

Operator: Vodafone

Recovery: Philz Touch
[Galaxy S III General] danarama:
We have certainly seen an enourmous drop in sds reports since v1 of the fix. Reports that still come in are mostly ics. Theres the odd jb report but they have so far all been unsubstantiated.
[Galaxy S III General] bortak:
Sorry for the late reply guys.

It was the stock, unrooted MC2 firmware from sammobile, flashed with odin. So latest firmware/ recovery/ bootloader. It died during the night.

BIG HOWEVER

After taking it to EE it might have been water damaged, however neither me or her know how that could be possible. So it's a 50/50 really.
[Galaxy S III General] IndianHacker:
Friends,

I have read the 1st post of this thread and still asking these questions because I am a bit confused..

Here are my phone details (from 'about device')

Model: GT-I9300

Version: 4.1.2

Baseband version: I9300XXEMB5

Kernel Version: 3.0.31-996085 se.infra@SEP-89 #1 SMP PREEMPT Mon Feb 25 11:49:05 KST 2013

Build number: JZO54K.I9300XXEMB5

Operator: Vodafone (India)

CSC: Unknown

I checked with the eMMC checker app (v.1.4.4) and it shows that my phone has eMMC chip of type VTU00M and FwRev: 0xf1 and it is an Insane chip.

So, based on the above info, could someone please tell me if I am safe or I need to take any further steps? I have not rooted my phone after I flashed the above FW with Odin. I have experienced sudden shut downs before but not much after I updated the firmware.

Also I wanted to understand what is the difference between Kernel, ROM, and Recovery as I also wish to update to a custom ROM..

Thanks in advance!

--IH
[Galaxy S III General] pickandwhammy:
Yes, you're on a "safe" ROM.

ROM = Read Only Memory.

Kernel = Heart of the OS, responsible for low-level initialisations, memory and process management, etc. It's the first component of an OS that is loaded on to the RAM, and it's kept there, since it doesn't change while booted.

Recovery = Another OS, minimalistic, but has root access to all memory, used mainly for writing to partitions that are in use when booted into Android (the primary OS), such as /system and /data.

Rest: read up on your own. Enough information on the internet.

PS: Your handle is quite the misnomer.
[Galaxy S III General] danarama:
Maybe he is a farmer, hacking away at the wheat crops :)
[Galaxy S III General] IndianHacker:
Thanks a lot for confirming and the definitions of the terms I asked! :)

Not that I didn't know what they mean; I wanted to understand in the context of the process of updating my phone to one of the custom ROMs available.. No wonder it provoked you to write the postscript above.. :cool:

I liked that too... :)

--IH
[Galaxy S III General] pickandwhammy:
No worries! From an SDS point of view, the problem is in the eMMC firmware, the fix is unfortunately a "workaround" in the kernel because that's much safer to flash than a firmware upgrade (that's equivalent to flashing your BIOS).

So, bottomline is: whatever you use, ALL the kernels that exist on your device should be patched. Two obvious ones are the Android kernel and the recovery one.

There's also Download Mode, and though it hasn't been confirmed, we're pretty sure Samsung's "fastboot" also utilises a kernel that could potentially be unsafe. Since this mode is part of the bootloader, it's very likely that the new bootloaders (exclamation mark ones) have the patch whereas the older ones don't. This is where it gets tricky because faking warranty is a lot easier when using the old bootloader.

Note: most custom ROMs (at least the well-known ones) had patched their kernels pretty much as soon as update7 was out. This is not true of recoveries, especially CWM, which still hasn't been patched. There are other recoveries like PhilZ Touch (CWM based) and TWRP which are safe, though. One advantage of a flagship powerhouse having such pathetic bugs is that there will be a lot of devs around :p
[Galaxy S III General] oliwatts:
Hi Folks.

Small update from a fellow sufferer with a SGS3 with a VTU00M rev. 0xf1 chip :crying:

I experienced all the freezing issues and finally managed to find this thread.

I was using

- CM10.1 Nightlies ,

- ClockWorkRecovery 3.0.6.1

- CM standard kernel (?).

I had understood the the CM10.1 nightlies included the fix although I was still experiencing very regular freezes with the following Apps, i can only assume every level needs to have the fix present, fixed per element rather than one fix present to resolve the issue for everything.

- Google Play

- Facebook.

- Keyboard issues (with SWIFTKEY Flow).

- Chrome

I have applied

- TWRP 2.5.0.0 Recovery (via GooManager)

- SiyahKernel s3-v1.9.1

- CM10.1 Nightly 20130416.

Things are MUCH better, i've had one freeze in 24hours which is not conclusive and one failure to boot after a controlled reboot (stuck at CM splash screen). I'm not 100% confident but things are much improved and it took my a while to understand all the advice.

Thanks everyone.
[Galaxy S III General] pickandwhammy:
UNSAFE

If your phone froze and returned to normal that could have been the SDS fix at work.

Apps don't write to memory, they ask the OS to, which in turn invokes kernel functions to do so. Hence the fix is at the kernel layer, not application.
[Galaxy S III General] oliwatts:
Thanks for the clarifications. For a semi-technical users with only growing experience of phone flashing your response is incredibly helpful and teaches me a lot.

I had missed any reference to CWR 6.0.3.1 being UNSAFE. It does absolutely tally with this update.

A parallel post had mentioned experience problems with specific Apps, but of course that is most likely coincidence and simply exercising my phone more rigorously with my favourite apps caused the failure.

Brilliant, lets see how it goes.
[Galaxy S III General] danarama:
6.0.3.1 should be safe if its compiled with the full cm 10.1 kernel. You would have to ask the op of any thread you want to download cwm from since anyone can compile it.

Of course you said 3.0.6.1 not 6.0.3.1 :)
[Galaxy S III General] mobjohn:
Flashin with ODIN safe?

I have the insane chip and i am on 4.1.1 stock rom. My phone says that there is no update available is it safe to flash a 4.1.2 rom like MB1 with ODIN? I search a few threads and i cant really get a certain answer.
[Galaxy S III General] danarama:
Its always going to be risky using download mode...

I don't know what to tell you. Personally, if it were me - i'd accept the risk and flash it but its your decision.
[Galaxy S III General] mobjohn:
Flash

Thanks for the quick reply. Usin odin will update the bootloader? I have a single file rom Do i have to tick the Update bootloader option?
[Galaxy S III General] danarama:
Guide here

http://xdaforums.com/showthread.php?p=26530736
[Galaxy S III General] migz012788:
Hi there. Just to clarify. Right now im on omega 43.3 rom. And im using philz touch recovery. Obviously that recovery is safe. However the kernel that I am using is the one that the omega 43.3 rom is using(the stock kernel that comes on omega rom 43.3) and the version of that rom is XXEMC3. Just to clarify, is that version of ROM and a kernel comes with it is included on fix v2? Or update 8? Thanks :)
[Galaxy S III General] danarama:
MB1+ is update 8. This is in post 1
[Galaxy S III General] migz012788:
Yeah. And MC3 is newer than MB1 so it is in update 8 right?
[Galaxy S III General] danarama:
Just apply logic and you'll be OK
[Galaxy S III General] meodollar:
nice i tried and succes. ty
[Galaxy S III General] guerouig:
Like so many, I have the infamous chip an so have taken all "preventive" measures - safe ROM, safe kernel, safe recovery..." But like so many I'm falsholic, mostly through recovery or Mobile Odin and sometimes through Odin. Do these quasi dalily flashing have adverse effects on sds? my device is almost a year old now and has seen a great deal of stock and custom roms, besides numerous nightlies. Or, can I say that if it is alive, despite all this, I'm home and dry?
[Galaxy S III General] pickandwhammy:
If you're asking about SDS, then you shouldn't have any trouble, since you mentioned everything is safe (I'm assuming bootloader too?).

If you're asking about NAND wear in general, nothing you can do to stop that, it's analogous to batteries dying over time, but like the batteries, it actually takes a LONG time for it to happen. Only case I've seen is when a friend fried two sdcards one after the other by symlinking /data and Dalvik to them. Stupidest thing to do, IMO.
[Galaxy S III General] danarama:
If you rooted before 4.1.2 and haven't updated the bootloader, do not use Desktop Odin