yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] ponepo:
Hi guys,

I am a victim of SDS since my S3 died 2012/11/22 (bought 2012/07/09). When I got my new S3 on 2013 January 04 after repair (Technical Service lost mine), I got:

RF cal: 2012.12.6

HW Rev. : 1.500

Type: VTU00M

Date: 11/2012

FwRev: 0xf1

and I thought that everything would have happened and I was saved.

But... after seeing some comments here, the @Oranav's test with the patched Siyah Kernel and the comments from @T0xic4u, I could not take it anymore, I've tried and ...

the Oscar goes to................................................ -------> 2 Oh! :crying::silly::crying:

I also believe that (almost) ALL VTU00M 0XF1 are affected.
[Galaxy S III General] dandroid13:
And now we have a 11/12 too.
[Galaxy S III General] ponepo:
duplicated
[Galaxy S III General] odoto:
it is not as important any more, since we got the first person with a 11/2012 affected chip, but can you please add a line to the OP asking people to report their findings (production date and if they are affected)? It can't hurt to get more data ;)
[Galaxy S III General] suspktu:
did the oranav's test too. got the 2 result with 06/2012. i'm curious if somebody got the 0 result.
[Galaxy S III General] T0xic4u:
Someone with 0XF7 should make the test. Result should be "0" then.

Taper di Tap with my S3 @184 days

---------- Post added at 09:54 PM ---------- Previous post was at 09:28 PM ----------

Translated:

he tested with 0XF7 and got "0". So test works.

Taper di Tap with my S3 @184 days
[Galaxy S III General] qavro:
Color : Titanium Grey - 16GB

Type : VTU00M

FwRev : 0xf1

Date: 07/2012

RF cal: 2012.9.19

HW Rev: MP 1.100

Test result: 2

I am happy at least that my S3 runs like a rocket and never had a glitch with it before applying all the "fix" , hopefully will go the same from now on.
[Galaxy S III General] siavash_Skh:
what is the difference between using eMMC check and Oranav test ? The results are same ?
[Galaxy S III General] danarama:
eMMC app is not conclusive. Its only VTU00M 0xf1 of a certain firmware date (which cannot be answered by app) that are affected.

Basically not ALL VTU00M 0xf1 chips are affected. Only Oranav test can tell you conclusively if you have the firmware which contains the bug but its a little more involved in you have to flash a kernel to test so some people wouldn't like that.
[Galaxy S III General] BlackMonkey:
EMMC checks manufacturing Date and Oranav the date of the firmware

Edit: haha.. I was to slow...
[Galaxy S III General] T0xic4u:
eMMC-Check tells you produktion date of your eMMC

Oranav-Check tells you the more important firmware-date.

Taper di Tap with my S3 @184 days

---------- Post added at 10:55 PM ---------- Previous post was at 10:49 PM ----------

Right now all 0xf1 had firmware date 13.04.2012.

Taper di Tap with my S3 @184 days
[Galaxy S III General] danarama:
All 12....
[Galaxy S III General] qavro:
True, but talking about <20 tests out of millions of chips is hardly conclusive...
[Galaxy S III General] ponepo:
Yes, is correct. But right now, we have 12 of 12.
[Galaxy S III General] g3ar:
hi im from croatia , i have 0xf1 08/12 , i wanna do ornav test but i dont understand what i need to do ( not root expert ) so if u can give me tutorial i wanna do test

ps. should i update to spanish rom 4.1.2 XXELLC , or stay at PDA: I9300XXDLIH

CSC: I9300CROLJ3

Version: 4.1.1

Date: 2012-10-17
[Galaxy S III General] danarama:
Yes but it is not the final answer.
[Galaxy S III General] T0xic4u:
First produktion date we have is 04/12

Last produktion date we have is 11/12

All of them (over 20 tested so far) had firmware 13.04.2012. You really think, that samsung had a different one flashed? It would NOT make any sense.

I worked for Siemens Mobile and Nokia. We never used different software/firmware at same time.

It is like "never change a running system"

My conclusion:

Samsung noticed a bug and fixed it. New firmware for eMMC was born and flashed in November. 0XF7 was born.

Taper di Tap with my S3 @184 days
[Galaxy S III General] danarama:
I do not think anything until the results massively support the theory. You should know that about me by now ;)
[Galaxy S III General] odoto:
no offence, but in case you never flashed custom roms you probably shouldn't.. you would lose warranty and without any real gain of information, since by now we are relatively sure all 0xF1 chips are affected

well, unless you are planning to go custom rom anyway, then there wouldn't be any harm I guess ;)
[Galaxy S III General] T0xic4u:
Agreed

Taper di Tap with my S3 @184 days
[Galaxy S III General] odoto:
I agree with you from a scientific point of view, you can't particularly call 20 data points a sufficient dataset... but I'm with T0xic4u here, odds that we'll find 0xF1s with different firmwares are quite low... sadly (got 0xF1 myself)
[Galaxy S III General] danarama:
Im already on my second 0xF1.

Sure all things point to it being the same. just saying, I reserve judgement until we get some higher numbers.

I'll put in the OP "It appears all 0xf1 are affected" when we hit 40 - 0
[Galaxy S III General] massaro33:
Hi i am from BiH and also on 0xF1 running Criscello rom 4.1.2 xxlkc and whit stock kernel and phill touch recowery. Now want to flash this new omega rom should i change kernel and cwm. I have in mind boefla kernel. Ty
[Galaxy S III General] danarama:
The Omega Kernel is fine. Also Philz recovery is fine.
[Galaxy S III General] Zylian91:
I am secured, thank you :) Please let us know if new information about this arises
[Galaxy S III General] rezapatel:
Add another one to the list of 20.

Mine is a 6/12 0xF1 and results in a 2.

Sent from my Galaxy S3
[Galaxy S III General] NiggZ:
i need assistance trying to fix this i have gone through and my phone is affected.

i am using the stock rom.

what do I need to download to stop my phone from freezing all the time.

thanks
[Galaxy S III General] chimas16:
Hi, I have same problem. I bought my S3 in USA and brought it to Argentina where I live. I send it to Samsung yesterday and they do not accept it as I bought it outside the country. Does anyone know what can I do? Is it any solution to this I can try?
[Galaxy S III General] philgalaxs3:
Give more details :

which stock rom ?

what do u mean by "my phone from freezing all the time." ?
[Galaxy S III General] pijindrin:
I'm running stock XXELLA with perseus kernel and philz recovery. Is that safe or should I change someting?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] pickandwhammy:
Is it a locked model or an international one?
[Galaxy S III General] Peeyar:
Guys is the stock kernel of the latest ellc safe from sds and exynos bug? Or should i need to flash perseus kernel?
[Galaxy S III General] pickandwhammy:
Supposedly safe. In fact that's the source from where the rest of the kernels/recoveries have been patched from.
[Galaxy S III General] Peeyar:
Thnx dude
[Galaxy S III General] NiggZ:
Well i checked and i have

eMMC: VTU00M

FW Rev: 0xF1

where do I get what ROM it is ?

is it under Settings > About Phone?

if so i have XXELJ2??
[Galaxy S III General] pickandwhammy:
That's probably your baseband.
[Galaxy S III General] nex86:
It's funny that XELL4 apparently should contain the fix but it got released long before they officially stated that they're working on a fix.

so either they already knew back in november about it and made a fix or XELL4 doesn't contain it. I don't know...
[Galaxy S III General] pickandwhammy:
Latter is more likely, but even so, the former isn't so shocking. Samsung would naturally want to keep this hushed up, so they waited to see if enough people were affected for it to become a concern. It's all hypothetical anyway.
[Galaxy S III General] nex86:
probably. but I'm paranoid and don't want to go back to XELL4 unless I have a 100% proof that it contains the fix.

But also, XELL4 is the latest update for my country (Germany/DBT) and with XELLC or XELLA I woudn't have warrenty because of the different CSC.

Can they even still check it after a Sudden-Death?
[Galaxy S III General] pickandwhammy:
I doubt if warranty is dependent on CSC, but even so, most sudden deaths reported on XDA could at best be booted into download mode.
[Galaxy S III General] Kjc99:
Has anyone looked into the new ZSEMA1 firmware build date 1/4/13 maybe something new pertaining to sudden death?

Galaxy S3

Omega Rom V37
[Galaxy S III General] danarama:
XXELL4 was the 4th release of December. It includes the fixes (it has been checked).

XXELKC is the 12th release of November and it also contains the fixes (I checked this one personally).

My sds occurred in November, quite early before most others'. Its very likely they've known about it since then. They will have been working in a fix because warranty repairs cost THEM money.

Please don't be so niaive to think they make announcements for our benefit. They will have compared the cost of warranty repairs versus the cost of releasing a fix + the damage such a statement can make before rolling out the workaround
[Galaxy S III General] danarama:
We can't really check for "something new". Currently we can only:

1) look at the latest source code (update 7 is still the latest)

2) search the kernel binary for certain keyword. At the moment, we're searching for VTU00M. That is part of the trigger of the code, which wouldn't change. Its not like its a text file we can just read.

We wont know until next source release
[Galaxy S III General] sittingduckz:
Sudden Death

So far so good here, fingers are crossed :eek:
[Galaxy S III General] Rafa91:
Firmware revision: 0xf1

Production date: 04/2012

Oranav's test result: 2

I have always have my phone rooted and with custom ROMs, guess im just lucky :P
[Galaxy S III General] cocous:
Firmware revision: 0xf1

MP 1.400

Production date: 10/2012

Oranav's test result: 2

maybe all s3 with this version have the problem

but some people says the problem is only with 04/12 release date

what is true?
[Galaxy S III General] gabrymr:
Now we pretty much now, that every 0xF1 even the ones made in november, have the same firmware, which is the problem.
[Galaxy S III General] qavro:
You are confusing the release date with the EMMC firmware date.

You can have a phone released in november but the firmware still the april one. And that is the problem.
[Galaxy S III General] chimas16:
It's unlocked and international. There is no way I can fix it?
[Galaxy S III General] Stevemann:
Help please

And if my S3 is bricked....is there any way to revive it without a replacement mainboard?

Thanks.
[Galaxy S III General] chimas16:
Same here...is it possible to revive it without the change of the mainboard? I'm having problems with Samsung as they do not accept my phone as I bought it outside my country
[Galaxy S III General] T0xic4u:
Dead = dead. No defibrilator here.

But maybe Dr. House is able to help.......

Taper di Tap with my S3 @185 days
[Galaxy S III General] quebec1:
what do j do for execute oranav test?

soory for my english
[Galaxy S III General] vbuijten:
Same issue

Hi,

Seems I have same issue.. last days my phone started rebooting more and more often, thought it was a matter of apps using too much memory so I wasn't planning on flashing it at the time.

Suddenly phone was dead, starting up only shows the "Samsung Galaxy S3" start screen and sticks there. Can't go in recovery mode, only download mode. However in download mode can't flash from Odin with a new firmware, it gives an error after 5 seconds.

I have installed one of the Roms from this forum.. In download mode it shows my counter of changes at 3.. Does this void my warranty?

Any other ideas of reviving the phone?

Back to HTC desire for now :(

Thanks,

Vincent
[Galaxy S III General] danarama:
Follow link in post 1
[Galaxy S III General] danarama:
What does it say in download mode?
[Galaxy S III General] T0xic4u:
And what kernel was flashed?

Taper di Tap with my S3 @185 days
[Galaxy S III General] Thin_Bezel:
Hello where to do this procedure? ??
[Galaxy S III General] T0xic4u:
In Terminal-Emulator from Playstore.

Taper di Tap with my S3 @185 days
[Galaxy S III General] quebec1:
i see the first post and downloaded siyah-s3-v1.8.7-cwm-movi_ops_exported, but i don't understud what should I do after the flash.

sorry for my english
[Galaxy S III General] ivan4o5:
1) Go to GooglePlay store and type terminal

2) download Android terminal emulator

3) run it

4) type : su

5) give permisions (simply click allow)

6) type : cat /sys/class/block/mmcblk0/device/movi_ops

7) it will give you a value of 0 (not affected) , 2 (affected)
[Galaxy S III General] ali4796:
it is not needed to download terminal emulator

if you have root explorer

you can go to that address and open "movi_ops" as text
[Galaxy S III General] quebec1:
ok the result is 2.

i bought the phone in december but it was produced 06/2012. I have seen that with emmc test

other information:

ap: i9300xxellc

cp: i9300xxella

csc: i9300pheell3

rf cal: 2012.8.28

hw rev.: mp 1.100

hower now i installed omega rom v 37.1 with perseus.alpha31.2 kernel and philz_touch_recovery_4.00-b04 and hope for the best.

Then if you were to burn the motherboard because of the sudden death will bring it to samsung with warrenty
[Galaxy S III General] cammel:
I cannot find the cat folder.. Where is it?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] ponepo:
@T0xic4u, in the spanish Forum www.htcmania.com, less than five hours ago, an user has opened a post so that people will report their results with de @Oranav,s test and, so far, 10 of 10 got a "2".
[Galaxy S III General] danarama:
cat is not a folder. Its a command. The folder path starts at /sys
[Galaxy S III General] ali4796:
if you are going to use root explorer

it starts with sys

:

sys/class/block/mmcblk0/device/movi_ops
[Galaxy S III General] cammel:
I don't have that file! :confused:

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] quebec1:
for do the test you must flask the siyah kernel on first post

sorry for my english
[Galaxy S III General] cammel:
Ohhhh OK.. Sorry I missed that.. So I need to have siyah kernel in order to have that file??

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] quebec1:
in the first page there is a link for the this kernel that you must use for the test. After the test you must flash again your kernel

exuseme cammel for this question?
[Galaxy S III General] Westylakey:
The console command returned "2".

I am running Omega V36 XELLA & Philz Touch b04

Emmc:

VTU00M

Date: 06/2012

FwRev: 0xf1

Screeeeewed ;)
[Galaxy S III General] cammel:
@quebec1 if you are on omega rom then you are already rooted, so run triangle away to reset your flash counter and after it's done, before the phone boots up itself take the battery out and then put it on again and enter to download mode (power+home+volume down) without letting the phone fully load the OS cause it will trigger your flash counter to 1 if you do so, then use odin PC to flash any stock firmware you like, let's say you install XXELLC, after you flash the firmware your flash counter SHOULD still be at zero and your status original (cause you are on a stock firmware) and if you need root, then root it using cf-auto-root cause it installs a safe recovery after rooting (the stock one from XXELLC)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] quebec1:
1) i take the battery out when i see the written saumsung on the display cell?

2) but after i used triangle away the phone restart alone in download mode?

3) but when i enter in download mode hte phone don't load os it's allright?

4) but you used odin mobile pro? How do you use it?

sorry for my english
[Galaxy S III General] odoto:
seriously, stop apologizing :P
[Galaxy S III General] danarama:
Re: [Important] Sudden Death Fix - Are you covered?

Flash counter goes up when you boot into android. So if you reset counter then reboot, it needs reset again.

After reset, don't let phone boot. Boot into download mode. Then connect to pc with odin on. Not mobile odin
[Galaxy S III General] sebarkh:
Odp: [Important] Sudden Death Fix - Are you covered?

It seems that everyone has 2...

, it means that's all emmcs have fw date 14th of April. It doesn't matter if they were made in April May June November or December they are all affected...

Sent from my washing machine...straight from the tumbler...
[Galaxy S III General] T0xic4u:
AW: [Important] Sudden Death Fix - Are you covered?

Nope, as we got 0XF7 in November. Those are not affected. So do those from december.

Taper di Tap with my S3 @185 days
[Galaxy S III General] BrunoEboli:
Re: [Important] Sudden Death Fix - Are you covered?

I'm using xxella 4.1.2!

Am I safe?

Check VTU00m / 07/12 / 0xf1:confused:

Enviado de meu GT-I9300 usando o Tapatalk 2
[Galaxy S III General] T0xic4u:
AW: [Important] Sudden Death Fix - Are you covered?

Is it that difficult to read first post??

http://xdaforums.com/showthread.php?p=36499838

Taper di Tap with my S3 @185 days
[Galaxy S III General] cammel:
Re: [Important] Sudden Death Fix - Are you covered?

1) yes

2) no

3) exactly

4) I used it cause I already was on a stock firmware and I didn't want my counter to go up to 1 when rooting it, so I used mobile odin pro to not increase my flash counter and keep root. When you are on a stock firmware (or maybe on any firmware or rom) if you want to flash a new STOCK firmware and keep root and your binary count at zero, then you use mobile Odin pro instead of pc Odin. Or at least that's what I do.

Exactly, I think you don't need mobile odin right now, just use pc Odin as rootSU said.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] nhariamine:
When i was charging my S3 just a few mins ago, when it reached 100% i checked it and it says battery 0% Plug in the charger. iwas so afraid !

I rebooted the S3 and it ran normally and it show 100% battery right now .

Does this problem happend to anyone here before??
[Galaxy S III General] xanthrax:
my obituary

VTU00M

06/2012

FwRev : 0xf1

-=-=-

below a terminal emulator screenshot for those who wants to know how it looks like

i`ve done the command twice `cause i missed the space after cat so , the first row is my error

the result is "2"
[Galaxy S III General] qtwrk:
eMMC check VTU00M with 0xF1 , date 05/2012

result was 2 ...
[Galaxy S III General] Marilize-Legajuana:
Lol after reading lot of posts, no body with 0xF1 got another number :cool:
[Galaxy S III General] Grouxho:
VTU00m / 04/12 / 0xf1 -

Oranav Test: 2

Greetings from Madrid.
[Galaxy S III General] Team hammer:
is there a download to help against this??
[Galaxy S III General] g3ar:
i have q , my emmc says 08/12 , so aprox my device is old 170 days ? but i bougt device on 18-12-2012 . so does that "error" counting days since i bought device or
[Galaxy S III General] thealgorithm:
Just got the Galaxy S3 as a upgrade with my carrier (Vodafone) Unfortunately the type of emmc chip etc is the same as the ones reported as having the issues.

One question i need to ask is the following.. All users seem to have mentioned that the phone completely dies. which mean no indication of charging or detection (whether unknown or known device). If the emmc was corrupted, surely there should still be some signs of life (even if the galaxy S3 does not boot up or show anything on the screen). Eg connecting it to pc would give some type of response, or charging it would turn the led on etc.

Could perhaps the early signs of issues with the emmc somehow cause the device to attempt to read and overheat/damage something internally (not just the emmc) eventually which leads the device to be completely dead?

I updated to the latest version (xxell5, UK Jellybean 4.12) I assume the XXELLA is the same, just a debranded version?

I am sure there will be a huge influx of people reporting their phones damaged during the next few months. None the less, whats the worst that can happen. Just a trip to the store and a replacement same day (and believe me, they will, otherwise no paying the huge bill for the phone every month!)
[Galaxy S III General] g3ar:
small amount of devices is affected so all 16GB eMMC: VTU00M FW Rev: 0xF1 is affected but not all will die ?
[Galaxy S III General] slay3r85:
Anyone in Canada had their GT-I9300 repaired ? Samsung Canada refused to repair it because its an international model and they may not have the parts. Where can i get it repaired, (warranty or not) and hope its cheaper than buy a new one. I bought it at newegg.ca in june. Would UK still support warranty if i ask them to repair? I guess exorbiting shipping price but if warranty still good it may be worth it!
[Galaxy S III General] gadgetcraze:
Re: [Important] Sudden Death Fix - Are you covered?

Oranav test result 2

04/12 firmware.

Phone bought in June in India.
[Galaxy S III General] zyclops1:
how to know new bootloader is installed or not?

<ID:0/014> Odin v.3 engine (ID:14)..

<ID:0/014> File analysis..

<ID:0/014> SetupConnection..

<ID:0/014> Initialzation..

<ID:0/014> Get PIT for mapping..

<ID:0/014> Firmware update start..

<ID:0/014> boot.img

<ID:0/014> NAND Write Start!!

<ID:0/014> recovery.img

<ID:0/014> system.img

<ID:0/014> modem.bin

<ID:0/014> cache.img

<ID:0/014> hidden.img

<ID:0/014> sboot.bin

<ID:0/014> tz.img

<ID:0/014> RQT_CLOSE !!

<ID:0/014> RES OK !!

<ID:0/014> Completed..

<OSM> All threads completed. (succeed 1 / failed 0)

<ID:0/014> Removed!!

<ID:0/013> Added!!
[Galaxy S III General] Andante1980:
Oranav test result: 2

Date: 05/2012

Bought: Early december in India
[Galaxy S III General] danarama:
Re: [Important] Sudden Death Fix - Are you covered?

Looks like its just a matter of time that all die, unless the fix works
[Galaxy S III General] Rob2222:
Yes, bootloader was installed.

BR

Rob
[Galaxy S III General] vbuijten:
Hi rootSU,

In download mode it gives me the normal "Warning!!" screen first, when I continue by pressing volume up I get:

Top-left of screen in very small font:

ODIN MODE

PRODUCT NAME: GT-I9300

CUSTOM BINARY DOWNLOAD: Yes (3 counts)

CURRENT BINARY: Custom

SYSTEM STATUS: Custom

Then in the middle the Android logo, below that:

"Downloading...

Do not turn off target !!"

Mind you, it's not connected, so why does it say ODIN MODE ?

I have been running this rom fine for the last 2 months (a Samsung rom downloaded from here) and didn't change anything since until my phone started acting up..

Thanks,

Vincent
[Galaxy S III General] aniobash:
I am using Siyah 1.8.8 and there is no such file movi_ops

here is a screenshot where the first two commands are "cat" and the last is "ls" of the "device"
[Galaxy S III General] danarama:
I'm sorry but thats not good from a warranty status... I'm not sure if there is anyway to reset that now. You may need to ask in teh QA sub forum :(
[Galaxy S III General] T0xic4u:
AW: [Important] Sudden Death Fix - Are you covered?

You have to use the special siyah 1.8.7.

Watch first post

Taper di Tap with my S3 @186 days
[Galaxy S III General] pickandwhammy:
A Galaxy S device (maybe even all Samsung Android phones) can be booted into three possible modes, in order of complexity:

* Android

* Recovery

* Download mode (this is Samsung's version of "fastboot" used in other devices)

With the three-finger salute, you're booting into download mode, and the device is ready to receive instructions and data via USB cable, controlled by ODIN and communicated by device drivers.

To reset all the counters to zero, use TriangleAway. If you're on the new bootloader, you'll have to downgrade first.

Read this post for more information.
[Galaxy S III General] nex86:
not possible since he doesn't have a chance to run Triangle Away.

He will be lucky if samsung repairs the phone on warrenty, otherwise: Have fun paying.
[Galaxy S III General] Kjc99:
Re: [Important] Sudden Death Fix - Are you covered?

Running custom rom... if mobo.fries and EVERYTHING IN DOWNLOAD mode said official it will remain that way after the sudden death too right?

Galaxy S3

Omega Rom V37
[Galaxy S III General] blyx21:
Re: [Important] Sudden Death Fix - Are you covered?

Correct.