yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] skivnit:
Hopefully the newly released note 2 official firmware includes the fix in the kernel. Because on my note 2 I have the same chip
[Galaxy S III General] InfX:
I had XXALF5 handy, just ungz-ed it and did a search, neither "VTU00M" nor "movi operation is failed" are there.
[Galaxy S III General] qavro:
Nothing can fix an SDS because the phone is already dead. :D

But to prevent it, yes it seems. One of those at this moment.
[Galaxy S III General] drraptor:
+ 1 we have to wait and see, but still IMHO, we should trust the developers word:)

Samsung will not admit it of SDS existent quite ing that is a bit too soon for everybody to start jumping around like happy rabbits.

Sent:) from my GT-I9100 using Tapatalk 2
[Galaxy S III General] STELIOSFAN:
Not only. You can also flash Yank which includes the fix (and others updated as we speak). It has been mentioned a couple of pages before
[Galaxy S III General] mjb:
Ok, both XXELKC and XXELL5 from perka's file stash have the strings associated with the patch.

The only other kernel there is XXDLJ5, and it doesn't have the strings.

If anyone can provide me with the boot.img file from anything in between XXDLJ5 and XXELKC, I can check them.
[Galaxy S III General] Animor:
So you are saying that XXELL5 is safe?
[Galaxy S III General] jakmeister:
Yeah, Tried that zip file, and gave me a heart attack when my phone froze at the Samsung loading screen. Ended up have to do a full wipe in recovery and do a NAND restore before it boots normally again (even though it is not usually required --- why it happened is still a mystery to me).

Anyway, finger crossed everything will work smoothly from now on. :)
[Galaxy S III General] mjb:
The Kernel is compressed - so you need to extract it out of the boot.img file so you can decompress it, and then search. I don't know if you did this, but my recent check suggests that XXALF5 won't have it anyway.
[Galaxy S III General] qavro:
I have all the possible trust in both AndreiLux and Entropy512. I just don't trust the manufacturers of the chips so much...
[Galaxy S III General] mjb:
Absolutely not, I'm saying that it has the strings associated with the supposed SDS fix.

Given this, I don't think this fix will help, or - perhaps - the date restriction in the code is too restrictive, and more than that date of the firmware revision is affected.

Only samsung knows for sure, and there still may be a fix forthcoming.
[Galaxy S III General] drraptor:
Samsung haven't fixed the super brick bug yet :p
[Galaxy S III General] InfX:
Let my try and give you an analogy. Let's say you have a huge cupboards with a lot of tiny drawers. Thats your flash memory. Now, let's say, the cupboard and the drawers are made of very low quality stuff, so each time you open a drawer, it wears out a little bit. Eventually, after you open a given drawer too many times, it breaks and can no longer be used. That's a NAND flash memory. Since you would still like to use the cupboard for as long as possible, you will instruct the user to try & avoid using the same drawers over & over again leaving the other ones unused, telling him to go for the least used drawers first. That's wear leveling. And the user is the wear leveler in this case. Now, lets say you have a dumb user that tends to ignore the instructions after one week of use, and starts using a single drawer for everything. That's a faulty wear leveler. Now, let's say we can remind the user to use different drawers every single day. That's the software workaround.

I hope you get an idea, LOL.

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

I did. And i did the same on WanamLite.XXELLA.V5.3 and found those strings. I had no utility to decompress the img properly, though, so i just went for the gz magic (0x1f8b) to find the start of it, cut the header off with hex editor and extracted as .gz after.
[Galaxy S III General] cristian274:
"a very specific date"? What date u guys talking about? As i understand, this supposed "can-fix-kernel" just only work for some s3 with a specific date?doesn't it? If there, when is that specific date and how to define it?
[Galaxy S III General] ponepo:
Hi,

The user mark3d4death posted this SDS with XXELLA --> http://xdaforums.com/showpost.php?p=36387849&postcount=2433

and confirmed it was 100% XELLA with --> http://xdaforums.com/showpost.php?p=36390060&postcount=2442

Could be explained with an advanced and faulty wear leveling?
[Galaxy S III General] mjb:
Same process as I. Good stuff.

---------- Post added at 11:44 PM ---------- Previous post was at 11:43 PM ----------

Then says he had a Siyah kernel 3 posts later:

http://xdaforums.com/showpost.php?p=36390137&postcount=2445
[Galaxy S III General] zscomp:
Then patch was implemented at least in all kernels from XXELKC and later?
[Galaxy S III General] mjb:
It's deep within the code for the fix:

date = ((data_buf[327] << 24) | (data_buf[326] << 16) |
(data_buf[325] << 8) | data_buf[324]);

if (date != 0x20120413) {
err = -1;
return err;
}

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

Looks that way, yes.
[Galaxy S III General] zscomp:
Then brick reports must inlude these roms also then and not the only one case with XXELLA allready mentioned.

I am not sure that this is THE fix.

Found another one http://xdaforums.com/showpost.php?p=36350315&postcount=2302
[Galaxy S III General] mjb:
Yep, I'm sadly thinking the same thing. I've PM'd both AndreiLux and Entropy512 bringing this to their attention.
[Galaxy S III General] drraptor:
Did you read that post carefully ??:p:D
[Galaxy S III General] zscomp:
Stupid grey color plus budget lcd = fail :silly:
[Galaxy S III General] kaiur:
+1

http://xdaforums.com/showpost.php?p=36352924&postcount=2311
[Galaxy S III General] qavro:
Hell NO ! That post is mine and it was a joke!

At this moment it does'nt seem a smart joke anymore...

But i have explained that later without using grey letters :(

My apologies for that.

Back on topic: What troubles me is this:

Which means that only the EMMC firmware of a single day (2012/04/13)

is bad and need to be patched? Or all before that day and inclusive that day?
[Galaxy S III General] htcsnap93:
I can inform you that unhappy rabbits also jumo around.
[Galaxy S III General] 80000037:
could you please edit/delete your post then? :)

I know you're joking, but seems that lot of people didn't get the joke and can cause unnecessary trouble later on (ex: Andre took it seriously etc).
[Galaxy S III General] qavro:
True, but my affirmation was not exclusively made for the happy ones only. Even the sick rabbits can jump from what i know. And before we will both get warned let's stop the off-topic here.

I did so.
[Galaxy S III General] fault123:
My SIII I9300 16 GB just died yesterday, 8th January 2013. I bought it on 2nd of August 2012. So its 5 months and 6 days.

It was rooted, on stock rom, no modifications whatsoever. Was using 4.1.1 version.

It died in my pocket, doing nothing, just 10 minute after making a phone call.
[Galaxy S III General] zoot1:
Which rom and kernel?
[Galaxy S III General] cristian274:
Please please make this more clearly, i think i still didn't get the full answer:crying:. It means that those kernels only work with emmc firmware date which is 2012/04/13 and not for emmc firmware with the day after then?
[Galaxy S III General] InfX:
It mean 2012/04/13 only.

2012/04/13, Friday the 13th, lol. I really hope it wasn't a bad eMMC dev joke.

In any case, maybe that's the only affected eMMC firmware version, there isn't much point in working around nonexistent issues, you know.

PS: Just took a look at the "eMMC check" app, it says 04/2012 :( since you don't exactly release eMMC versions multiple times a month, i am most definitely affecter :crying:

PPS: I hope workaround actually works.
[Galaxy S III General] qavro:
InfX, AndreiLux said that the date you have in the EMMC app is not the same with the EMMCfirmware date, that firmware date cannot be read by usual methods he said...
[Galaxy S III General] bala_gamer:
stock :cyclops:
[Galaxy S III General] evivbulgroz:
How did you check the ssid?
[Galaxy S III General] avesalom:
Theoretically 0xf1 VTU00M eMMC responsible for the sudden death of s iii. In my device after the test I ran showed the 0xf0 VWU00M eMMC which is not affected.

My model is the 32gb that it seems, has not experienced the problem of world that I've been looking for.

So owners 32gb (and 64gb those are) probably should not worry ...

The thing that rankles with Samsung is that exploited the fact we foist the new bootloader with the famous "goodies" and that which is not related to the so-called "fix".

Root and Custom mods the only solution ...
[Galaxy S III General] Rob2222:
Exact! AndreiLux talking about the emmc FIRMWARE date. Not the emmc MANUFACTURE date.

I could imagine/would assume, all VTU00M emmc ics with firmware 0x1f have all the same firmware date. Don't care when they are manufactured. Just cause it's the same firmware version.

BR

Robert
[Galaxy S III General] drraptor:
Official XXLEA kernel seems to have the fix too:)
[Galaxy S III General] cristian274:
but how can we find out the exact emmcfirmware date so we can decide whether we need to flash XELLA kernel to avoid SDS? additionally,my emmc check app told me that mine date is 06/2012
[Galaxy S III General] behemot24:
so I've been today in a service center authorized by samsung and they knew about the bug. they said they will send the phone to the factory and it will take 2 to 3 weeks before it gets back repaired... :(
[Galaxy S III General] zoot1:
There is no way to know..as of now..
[Galaxy S III General] avesalom:
As far as I searched I did not find someone with a 32gb version that had a problem.

Knowing someone? For I am confident in what I wrote above.
[Galaxy S III General] koolshubh:
Just did a emmc check and I found out that my fwrev is oxf7 and the date is 11/2012... But I got the same chip like otherss... :(

So am I on a safer side?
[Galaxy S III General] montage mahal:
Mass confusion on this thread. It's crazy. If people are afraid of sds flash all to LLA and get warranty back. If you wanna root, mod flash a rom or what ever its always done at your own risk any hows. I'll be staying with stock warranty till there is a clear answer, the more I read this thread the more consufed I get.
[Galaxy S III General] drraptor:
You can't check the date with usual methods :p
[Galaxy S III General] avesalom:
Theoretically if you have the same chip, you are candidate for sds sometime.... :(
[Galaxy S III General] fault123:
I mentioned that it was stock rom, and no modification. So its stock kernel too.

And the bad thing is I bought it from Switzerland and now I am in Turkey. Here in Turkey Samsung does not accept to repair the phones bought from out of country, even if i accept to pay for it. So I do not know what to do, but one thing I know, I'll be damned if I touch any SAMSUNG from this day on.
[Galaxy S III General] Amos91:
Just got my UK S3 back from Samsung. Been given to me on ICS DLJ4 but they have also replaced my chipped screen and case. Happy days :good:

Same IMEI number btw.
[Galaxy S III General] InfX:
Good point. Any kernel build with this date being printed in a kernel trace? Or exposed via proc? Anyone building his own custom kernels should be able to easily do this.
[Galaxy S III General] koolshubh:
I have a question in here. Using phone on OS is safe, recoveries that dont have fixed kernels are not safe. All understood.

What about I switch off my phone and plug in?

Is that big green battery charging icon delivered to the screen by OS based or recovery based software? I know that there is nothing related with memory read write in this case, but people were saying the SDS is caused by faulty chargers also. Thats why I'm asking.

Are we safe charging our phones while switched off?
[Galaxy S III General] skivnit:
Nope. Urs is oxf7 not ofx1
[Galaxy S III General] 17RoiDavid:
i don't understand if XXELL4 is safe and if samsung is about to release these andrei's fixes with a new update soon...
[Galaxy S III General] electrotune1200:
Andrei found the fixes in the ELLA kernel...

I know there's a heap of bull**** in this thread... Just read a little bit guys...
[Galaxy S III General] rushless:
Seems four key things are missing in this thread's first post to guide the discussion, though may have been added later (too many pages to see):

1. What chipset version (S4 or quad)

2. 16GB or 32GB, Apparently even those are slightly different motherboards (not just the flash size different).

3. Is the device rooted?

4. Using a custom kernel?

Not seeing how software fixes this issue since not too many options besides lowering clock or step down the radio power to the chipsets. That assumes thresholds of the circuit gates allow such changes in the chips.
[Galaxy S III General] 17RoiDavid:
yeah ok he found it in the ELLA kernel. but i'm using ELL4. is it safe?

if not, there's gonna be another official samsung update for that?
[Galaxy S III General] electrotune1200:
As far as I know, there are no patches in the ELL4 kernel.

Patches were found in ELKC, and ELL5. May be more, but that's what I've gathered so far.

If you want to ease your mind, update to ELLA.
[Galaxy S III General] smokey_bear:
Another XXELLA released, this time for Luxembourg, includes like the XXELLA for United Kingdom also a new bootloader:

LUX: (Austria, Belgium, France, Germany, Hungary, Italy, Spain, United Kingdom)

Build Date: 22.12.2012, Changelist 742798 (UK XXELLA has the same changelist)

See attached images LUX and UK, first image is LUX, second is UK.
[Galaxy S III General] 80000037:
there are reports from france forum member, that 32GB models also suffers from SDS.

later on, one of the mods from that forum post here and confirm the news.

i guess what matters is not the emmc chip type, but the emmc firmware rev...

on my 64GB SGS3, the firmware rev is 0xf2. Chip type is V6U00M, but logically, the memory type should different since mine are 64GB.

and i noticed that those who suffered from SDS lately, got replacement board with new emmc, same type, but new rev, 0xf7.

we can't determine the emmc firmware date, but we can look at the firmware rev code...
[Galaxy S III General] Mikulec:
This thread gone berserk, everybody acting like crazy asking the same things over and over.

Please update the first post with some up to date info.
[Galaxy S III General] electrotune1200:
Too many S3's as Christmas presents I gather :p
[Galaxy S III General] CHEVYbarracuda1:
So im on 32 gb model and have same type and fwrev as u but still for prevention i flashed perseus kernel
[Galaxy S III General] AILD:
https://github.com/cyanogenmod/andr...mmit/da8461692362317a8ffce4d4646953985fcf4e1d

Is that eMMC brick bug fix on cm10.1 ?
[Galaxy S III General] koolshubh:
Stock Kernal XXELLA or PERSUES 30.2 == "BUG FIX"!!

Am I ryt??
[Galaxy S III General] CHEVYbarracuda1:
Yea i think u r
[Galaxy S III General] bruno12345:
Fix SDS or Exynos bug??
[Galaxy S III General] sweeney_uk:
Nope I had Perseus 30.2 and xxella and mine went yesterday. Phones4u UK are repairing under warranty....I hope
[Galaxy S III General] DJ Palmis:
err = mmc_movi_cmd(card->host, 0xEFAC62EC);

I'm not going to tell you "I told you" ^_^
[Galaxy S III General] kaiur:
Perseus 31
[Galaxy S III General] abhi4168:
http://xdaforums.com/showthread.php?t=1691401 >>31.2 has the fix and it released today.
[Galaxy S III General] koolshubh:
Both sds as well as exynos bug...

---------- Post added at 06:23 PM ---------- Previous post was at 06:19 PM ----------

Dude perseus 31.2 is realsed and u said ur s3 died yestrday.. how its possible???

Dont jump around giving false information!!!
[Galaxy S III General] gsw5700:
Also see boeffla kernel 2.6 alpha1 which also has the fix

Sent via TCP/IP
[Galaxy S III General] DanXo:
Mine died today. I had it on the charger over night and in the morning I woke up the green LED was on but the phone didn't respond to home or unlock button. I pulled the battery out and after that I was not able to turn it on or go into recovery/download mode. I bought the phone last year in June.

It's the GT-I9300 Exynos with Omega V36 and Siyah 1.8.6

Made in Korea

Battery: Made in Japan, Assembled in China

I hope that T-Mobile Croatia will fix it under warranty.
[Galaxy S III General] barton71:
Just collected my S3 from the service centre this morning (It was in for 3 weeks) and guy at the desk said that 4 different engineers had looked at my handset and none of them could figure out what the problem was. In the end they just gave me a new handset. Although i am happy that i got a new handset, i would have though that Samsung would have been aware of the issue and would have sent out some kind of information to their authorised service centres, so that the technicians would know what to look for. Obviously not.
[Galaxy S III General] blublub:
Got it thx

Sent from Mobile, might include T9 typos :)
[Galaxy S III General] yahyoh:
yep

i think + https://github.com/AndreiLux/Perseus-S3/commit/85fc375addd4893ab2d96077dd4c034755d8616e

https://github.com/AndreiLux/Perseus-S3/commit/ac5880b1937e35a24f45638f18153770be2b2a6a
[Galaxy S III General] pickandwhammy:
Changelog evidence:
[Galaxy S III General] cristian274:
it seems that we have a case with stock kernel XELLA still affected SDS !?! Weird !!! >"<
[Galaxy S III General] flight23:
What's weird? He wrote he had Perseus 30.2 and xxella Rom. Perseus 30.2 wasn't safe yet, first safe version was 31
[Galaxy S III General] yahyoh:
my sister has GS3 with XXELL5 + stock kernel

but the kernel compiled on 10 dec i'm not sure if it has the patch :confused: :rolleyes:
[Galaxy S III General] Scarface1991:
Wow you just answered all questions I had about this whole issue in one single post. Amazing, that`s why XDA is so awesome, because there are people like you here around.
[Galaxy S III General] cristian274:
my friends, just one idiot question, can anyone tell me do we need to root the device before flashing custom kernels which i mean is Perseus 31.2? shame on me because this is the first time i flash kernel :silly:
[Galaxy S III General] yahyoh:
no u don't u can flash it via Odin but u need root to control the kernel setting :)
[Galaxy S III General] :
Just flashed today's nightly... Let's hope it's safe! ;)
[Galaxy S III General] Morle:
Thanks for all.

Enviado desde mi Nexus 7 usando Tapatalk 2
[Galaxy S III General] sam77744:
you are on right kernel ella
[Galaxy S III General] sweeney_uk:
Sorry if I gave false info it was Perseus kernel released on the 6th Jan can't find that version as the phone is away being repaired.
[Galaxy S III General] CHEVYbarracuda1:
Well it says 16gb so my conclusion is that 32 gb models werent dramatically affected..
[Galaxy S III General] Notor1ouS-:
so am i right, i just need to flash a kernel with the SD fix ? (running wanam5.3)

do i need to flash bootloader/recovery? im running cwm touch (some october release)
[Galaxy S III General] FreeSTYL3:
quick question:

i have stock xxella + cfRoot 6.4.. (not autoroot)

Is my kernel in any way changed?

Do i have the fix now?
[Galaxy S III General] CHEVYbarracuda1:
Yup and the new rom xella..
[Galaxy S III General] vasp3690:
Samsung repair team in Leeds... complete tools....

They returned the phone to me unfixed and unpgraded either. Still on previous than ELLA firmware and according to them phone fixed.

Phone is getting back.in the box for the 3d time. Unless they fix they keyboard issue it has I wont accept it back. After 3 attempts samsung is supposed to give me a new phone
[Galaxy S III General] fitipardi:
I think that is better flash perseus v31.2 kernel. It is most safe

Regards

Ed. At moment nobody talk about SDS with perseus kernel

Enviado desde el bar con una birra en la otra mano
[Galaxy S III General] bitubo:
hi,

if i install Omega V36 LLA,Kernel Omega LLA Stock and stay with Old Bootloader

it's safe or not ?

Thank's
[Galaxy S III General] Nees3:
LOL

That kernel release isn't even out for 24 hours and it seems if you have XELLA, it's the same patch, because it should be based on that same source as Perseus.
[Galaxy S III General] hermeson:
another S3 dead

What happened: turn off and never come back on again.

Where phone was made. China

Where battery was made. Korea

What firmware you were running. Cannot remember, I believe 4.1.1

Can you access download mode? NO =( (anyone know any trick)
[Galaxy S III General] behemot24:
I confirm the phone suddenly started to act strange one day before it dies: random lagging, freezing, reboot.
[Galaxy S III General] bocke85:
is there any kernel 4 cm 10.1 with the sds fix?!
[Galaxy S III General] Egan:
I disconfirm that, mine was smooth as butter when it happened...nothing strange before.
[Galaxy S III General] Scarface1991:
Answer is 2 pages back:

And the bootloader has nothing to do with the Sudden Death Syndrome.
[Galaxy S III General] DonHuan:
If you aren't rooted and on stock, what should you do - just wait for Samsung to release new rom version or flash fixed kernel (perseus, boeffla, yank555.lu) via Odin?

My friend bought his SGS3 in November, so, is he affected?
[Galaxy S III General] behemot24:
then maybe for my phone it wasn't the "sudden death" syndrom, but it was more like "torture until death" bug :)
[Galaxy S III General] kofiaa:
Use the eMMC app to determine if he is.

I've read about people who reported reboots and lag before suffering from sds.
[Galaxy S III General] DonHuan:
But it doesn't say whether you are affected or not.

http://xdaforums.com/showthread.php?p=36473044#post36473044

http://xdaforums.com/showthread.php?p=36473767#post36473767
[Galaxy S III General] kofiaa:
I know. But, if you have a chipset with VTU00M/0xf1 you could be vulnerable. There is no exact way to know.
[Galaxy S III General] FreeSTYL3:
cfroot modifies your kernel?
[Galaxy S III General] sgsboyo:
Apologies if I'm asking a question that's already been asked but this is a very confusing discussion! I've installed stock ELLA firmware off sammobile site but i'm unsure if this includes the sds fix? My phone is still randomly crashing (have removed the external sd card as I've a feeling it's not helping).

My phone isn't rooted now and device status says "normal" (sadly, however, flash counter sitting at 2 but I guess I can live with that if it's not going to fail and force me to send it for repair).

So, basically my question is should I (or, even, do I need to) flash with perseus kernel?

I'm learning every day and love Android but I'm just sad my latest (and favourite) mobile is less than satisfactory at the moment.
[Galaxy S III General] sodeknetters:
Yes, stock kernel is fixed as well...

If you are currently on stock, by all means update to LLA rom or newer. You'll be safe.
[Galaxy S III General] vadonka:
so if im understand correctly...

im on this:

ROM: Omega v36 (XXELLA)

Bootloader: XXELLA

Kernel: 3.0.36-Perseus-alpha31.2

...and im safe now.

im right?
[Galaxy S III General] krivinash:
I hope that we are :D

i think that onlu xxella isn't enough.

I always read the first page of Perseus kernel, where Andrei wrote changelog for new kernel: "Kernels >v31 and beyond stock LLA are now the only truly protected ones".

cheers!

i
[Galaxy S III General] :
The fix was implemented in today's nightly (9/1).
[Galaxy S III General] sgsboyo:
Since my phone is still suffering from random crashes even with stock I9300XXELLA I'm just wondering if there's any app or some way that I can find out WHY it's crashing?

Can anybody help?
[Galaxy S III General] fitipardi:
Hi vadonka, i remember you and yours kernels from O2X.

Yes, you are safe. Like sex with condom (joke off).

Regards

Enviado desde el bar con una birra en la otra mano
[Galaxy S III General] Rob2222:
I'm also on STOCK XXELLA bootloader + rom + kernel since it came out. Flashed with odin. BL installation confirmed.

Today I had the first freeze ever on my SGS3 16GB from June 2012 (VTU00M, 0xf1).

I wanted to wipe the screenlock away and then it froze. Power button doesn't power it off.

Had to reset the phone by pressing power 10 seconds. No problems after reboot.

*wondering*

BR

Robert
[Galaxy S III General] behemot24:
right, "SDS" is like "AIDS" :cowboy: my S3 wasn't protected...