yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] Pietrone94:
sorry for noob question...i boight my s3 in December...and i have date 06/12...is that normal?!?!?!
[Galaxy S III General] T0xic4u:
Yes.

Taper di Tap with my S3 @184 days
[Galaxy S III General] Pietrone94:
can you please tell me why is it normal?? :)
[Galaxy S III General] zscomp:
Because it is.
[Galaxy S III General] Pietrone94:
mmm ok <:laugh::laugh::D
[Galaxy S III General] T0xic4u:
You bought a phone in Dezember. But parts of it were built month ago. Maybe the whole phone was built month ago.

Taper di Tap with my S3 @184 days
[Galaxy S III General] Pietrone94:
ok thank you for the reply :)
[Galaxy S III General] T0xic4u:
You are welcome. :p

Taper di Tap with my S3 @184 days
[Galaxy S III General] lockmunk:
i bought my phone in july..but emmc chip date 09/2012..heheee :D
[Galaxy S III General] alijee:
I am on stock ELKC rom with JKay deluxe mod and siyah v1.8.8 kernel...should i consider myself safe or should i install ELLA rom?? ecause i have same effected eMMC version.
[Galaxy S III General] T0xic4u:
Kernel is ok, maybe you should also flash a fixed recovery

Taper di Tap with my S3 @184 days

---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------

If stock one was replaced during Root.

Taper di Tap with my S3 @184 days
[Galaxy S III General] pijindrin:
And how do you check the full date? Btw I have XXELLA stock rom, perseus kernel and philz recovery. Is that safe or should I change something?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] T0xic4u:
What is your chip-date shown by eMMC-Check

Taper di Tap with my S3 @184 days
[Galaxy S III General] qavro:
http://xdaforums.com/showthread.php?p=36696791
[Galaxy S III General] RevoWution:
Mine is 10/12, with 0xF1.

Damn, 1 month early :P
[Galaxy S III General] pijindrin:
That's the teeminal test. It only gives you a number 2 or 0 but no date.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] Rob2222:
Yes, but it ONLY gives you a 2 when the date matches the date in the fix source code. So this 2 gives you the date indeed.

BR

Rob
[Galaxy S III General] alijee:
sorry i am new... how to flash a safe recovery? and how do i know about my current recovery?
[Galaxy S III General] pijindrin:
And the date would be?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] Rob2222:
*rechecked*

Should be 13.04.2012. The fix checks for this date.

See fix, mmc_ops.c line 709: Link

BR

Rob
[Galaxy S III General] T0xic4u:
13.04.2012

Taper di Tap with my S3 @184 days
[Galaxy S III General] T0xic4u:
http://xdaforums.com/showthread.php?p=36499838

Taper di Tap with my S3 @184 days

---------- Post added at 02:38 PM ---------- Previous post was at 02:09 PM ----------

Would it mind you to make the test??

Right now the latest I have is with chip-date 09/12

Taper di Tap with my S3 @184 days
[Galaxy S III General] sak500:
Mine died after 7 months. For some it died after 3 months so noone can be sure when the phone will die
[Galaxy S III General] pickandwhammy:
Power phone off, hold volume up and home, power on. You'll boot into recovery.

For more info on SDS read this[B]http://xdaforums.com/showthread.php?t=2095618[B].
[Galaxy S III General] demlasjr:
Hey guys, sorry for late. Yes, they weren't precise about what bug: exynos or emmc. Looks like somebody already asked which one yesterday, so we are waiting for the answer.

Thanks mate for the info. I bought mine on Amazon, 2 years warranty and had no SDS and hope it will never die.
[Galaxy S III General] MuertoKo:
SamsungMobileEs on twitter said some times already that the "premium suite" fixed sudden death ;) not official but it's something. Now lets see how good the fix is!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] zscomp:
Can we have a link with the tweet;

Thank you.
[Galaxy S III General] MuertoKo:
It's the answer to this question here:

https://twitter.com/JuliioFV/status/291482161494781952

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] mesoh:
The eMMC app gives me :

type : VTUOOM

date : 11/2012

FwRev : 0xf7

and *#12580*369# :

XXDLJ

HW Rev 1.500

12/2012

Does my devise s3 (16gb) fit into sudden death category????????
[Galaxy S III General] ICavalera:
Lucky guy! :)
[Galaxy S III General] T0xic4u:
With the help of many nice guys we made a test with a (surprising) result:

The eMMC with Chip-Date 04/12 up to 10/12 have all the same internal firmware:

All have 13.04.2012

My guess even 11/12 0XF1 has this firmware.

Conclusion: 0XF1 = 13.04.2012

Taper di Tap with my S3 @184 days
[Galaxy S III General] qavro:
If it is so, then why the fix is not triggered by the firmware, meaning 0XF1 ?

It is triggered by the 13.04.2012 EMMC firmware date...I think is too soon to conclude that all 0xf1 are holding 13.04.2012 date, how many people have took the test?
[Galaxy S III General] Product F(RED):
Oh great going Samsung. So they knew about the problem and updated the firmware later or changed chips.
[Galaxy S III General] qavro:
Nothing wrong with the chips per se. Many VTU00M are with a newer firmware...
[Galaxy S III General] g3ar:
so what is next step :D
[Galaxy S III General] pickandwhammy:
LOL, that question just deserved a LOL! Especially with the suffixed smiley! :laugh:
[Galaxy S III General] T0xic4u:
Actually we don't know the meaning of 0XF1 and 0XF7. We got 10 tests that showed 0XF1 could mean 13.04.2012. I don't know any good reason why Samsung should put in a different firmware in chips with same code. But we know for sure, that 0XF7 isn't affected as it has a new firmware.

Reason why the magic code inside the kernel watch after 13.04.2012 and not after 0XF1 could be, that this way is easier. I realy don't know.

Taper di Tap with my S3 @184 days
[Galaxy S III General] qavro:
Well, then i think we should all run patched kernels/roms and to continue praying that this was all about SDS
[Galaxy S III General] Scarface1991:
Well that`s actually the only thing that you can do, to be as safe as possible...
[Galaxy S III General] Lui-g:
Tick Tock...

Apologies if this has been covered in this thread, I have read many pages, but admittedly not all since there's just too much traffic on this & other XDA threads I follow.

OK, I have a UK (Originally Three branded) S3 - back since UK launch day. (it's a white 16GB and with all the innards of a SDS-vulnerable device). I've always exclusively ran stock-only ROMS, and generally rooted them for use of Titanium.

I first had a completely non-responsive (& warm) S3 late last month after flashing a stock ROM days before ELLA came out.

Since then, I've had complete freezes (with screen on, whilst usin the phone) usually doing simple things (browsing, reading email, changing a setting) - the only solution is to hold the power button for a reboot.

I've read & been told elsewhere that this is the precursor to SDS. I've always alternated between a couple of different chargers (neither from Samsung).

This screen freezing has kept happening (once or twice a day) despite many total wipes, and re-flashings - I'm currently on stock ELLA.

I even tried another SD card, and am currently NOT using any SD cards (still freezes - so it's not related).

I'm on my last test stretch, which is NO ROOT and therefore NOT use Titanium or any other app-based restore solution, and see if I still get freezes.

I'm expecting so, in which case it brings me onto my question:

How can I get Samsung to fix a phone that occasionally completely freezes, but, thanks to ELLA, may not actually die completely...

Is there some way to "speed up" the death? I'm willing to do anything (without root).

Thanks in advance for any insight.
[Galaxy S III General] houser789:
Got my phone back yesterday after 2 weeks at Vodafone repair center.

No mention of the fact that it was rooted and that I replaced the Vodafone branded ROM with an international ROM.

What they did:

Motherboard has been replaced. eMMC has FW rev 0xf7, dated 12/2012.

Phone came back with 4.1.2 ELL4 installed. Funny that that is not a Vodafone branded version, although I bought it at the Vodafone shop and brought it there for repair. (Phone had 4.1.1 / DLIH when it died).

Question:

I need to have all my data and settings back, but I want to keep it stock standard for some time in case something happens again.

Now that my phone is on 4.1.2, is there any way to root my phone, do a partial restore from Titanium backup and then unroot, without losing my data and without leaving any traces of rooting?

Thanks!
[Galaxy S III General] dc_power!:
This is what I would do... to be on the safe side and NOT trigger the custom counter...

- Lookup the HIDSWVER and locate/download the same rom image at/from sammobile or samsung-updates

- pre-root it

- flash it with Odin

- perform your restore and other root requiring chores

- fully unroot from within Superuser or flash the untouched/non-rooted original stock again.

(if you can specify what your hidswver is, someone could prepare a pre-rooted stock image for you)
[Galaxy S III General] animoo:
I've got some bad news for you, m8. My phone did the same a few days ago, before it completely died. I suggest you not to root or modificate anything, because it is possible that your GS3 will end soon.... As I read earlier, ELLA doesn't repair a half-ruined chip, so you have the chance...:rolleyes:
[Galaxy S III General] Egan:
After a week in repair I got my device back, with a board replace. I got it back this way:

- Board: A/S ASSY-PBA MAIN COMMGT I9300 SEE 9041437

- Firmware: XXELL4

- eMMC chip: VTU00M 11/2012 0xf7

- Same IMEI: which is new for me after a board replace.
[Galaxy S III General] droidgirl74:
Thx, at least I now know, that I have the faulty chip, too... :(

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III General] jay_m3:
they can replace the board and give it same imei (old) as they have spare virgin boards called swap
[Galaxy S III General] T0xic4u:
We finished the terminal test:

Result:

All eMMC with 0XF1 got a "2" wich means all have firmware 13.04.2012.

Even those from November.

Taper di Tap with my S3 @184 days
[Galaxy S III General] DonHuan:
But why then only little amount of all devices die, if they all have the very same chip & firmware?
[Galaxy S III General] T0xic4u:
@DonHuan

Maybe different circumstances?

Taper di Tap with my S3 @184 days
[Galaxy S III General] odoto:
or worst case: they would all die eventually without the fix
[Galaxy S III General] DonHuan:
You mean some people use their phone more often than others? Cause there were some users with SDS using stock rom, w/o root, they didn't flash custom...

There must be sth else...
[Galaxy S III General] T0xic4u:
Maybe just bad luck.??

Taper di Tap with my S3 @184 days
[Galaxy S III General] DonHuan:
That's it! :D
[Galaxy S III General] gabrymr:
Heat, cold, humidity, power fluctuations, "bad luck" who knows and the fact that it happens to some, not even 50% of the devices is really strange, if it did, there would be quite a riot...
[Galaxy S III General] ponepo:
Only the good die young ;)
[Galaxy S III General] Isadora:
Wonderful... so when my mobo was replaced in October, they put another one with a dodgy eMMC in.
[Galaxy S III General] danarama:
Ditto,

but they didnt know what thej issue was then.
[Galaxy S III General] Isadora:
My S2 has the brickbug eMMC, my S3 has the SDS eMMC... Wondering what the S4 will have! Maybe I should ask for a discount :p
[Galaxy S III General] gabrymr:
Well my "brand new" one is with september chip too, so... I guess when they have and if they have to fix it, they might finally give me a good one.

And for the S4... it will have eMMC with built in experimental portal device "for testing", but you know how it goes... Looks like Samsung is going for Aperture science business model - crazy and all.
[Galaxy S III General] Technician:
Well here's a strange one. emmc check shows VTU00M but no mention of a FW REV number. The date is 6/2012 and i'm running

XXELLA. The phone's not rooted.

What does that tell me, safe or not?
[Galaxy S III General] jackie1234:
You must have root for check if you are save thats what the say to my.i had no root same as you

Then i rooted and then shows fw rev was no good

Sorry for my bad englisch
[Galaxy S III General] Technician:
Ahh, that explains it then. I belive there's a way round it without the need to gain root so I'll give that a try first.

Thank anyway.
[Galaxy S III General] Kjc99:
Does the new ZSEMA1 Galaxy S3 firmware have anything different from LLA OR LLC pertaining to a sudden death fix has anyone looked into it I noticed the build date was 1/4/13 as XXELLA and XXELLC were made in December

Galaxy S3

Omega Rom V37
[Galaxy S III General] danarama:
FYI, you don't need to look for the date. You can pretty much tell from the name. forget XXE for now. Look at LLA and LLC.

The First L = 2012

The second L = December

The A or C is the version number (1-9 then A-Z)

So if L = 2012, M = 2013

January - December = A - L

So MA1 = 2013, January, Version 1

LLC = 2012, December, Version 12

:)
[Galaxy S III General] Rob2222:
Hello,

am I wrong, or is the new incoming death report count falling?! :good:

At least I have the feeling that the big wave is indeed over at the moment.

2-3 weeks ago we had one or more new death reports here incoming daily.

I have the same feeling in the other forums I am looking at.

It seems to me that the fix in XXELL* is indeed working.

BR

Robert
[Galaxy S III General] ivan4o5:
It seems like that . Eaven if the fix is locking into infinite loop ( read more here http://xdaforums.com/showthread.php?t=2096045 ) .

But either way , there aren't a lot of deaths these days :D .
[Galaxy S III General] JKM2247:
At this rate, like someone argued some posts earlier, if the number of SG3 reported dying or dead in this thread is anything to go by, and since in my very fair estimation, of all the people contributing here[Those aware of XDA generally and this thread particularly], I wouldn't give this Random sample as representing beyond 1% of all owners of this phone, there must be an avalanche of phones going back to Samsung.

Doesn't anyone here have an ear at Samsung to inform the rest of us what they are doing about this. This phone is their flagship Android phone. So, surely they must be worried stiff of the damage this unfortunate "deaths" may be causing to their brand.

in the meantime mine is Pebble Blue on JB 4.1.2 Official, RF Call: 2012-10-23 and H/W Rev. :MP 1.100 currently fine but wondering if I will come to this thread to report otherwise sooner or later
[Galaxy S III General] Toadeh:
Apparently mines on its way back to carphone warehouse. No idea if its fixed or not. Will keep you posted....
[Galaxy S III General] b0gd4n:
I bought mine from carphone.

I am thinking of taking it to them rather than samsung.

What did you have to do to send it to them?
[Galaxy S III General] JohnM1973:
Very concerning, got mine from Argos beginning of November, hw version is m1.100, rf call 2012-06-15, would I be right in thinking that means it was built in quite an early batch and has been "lying" in stock at Argos until I purchased it? Will be expecting it to die some time around April or May for a guess then!
[Galaxy S III General] Toadeh:
Nothing special, just took it in, said it doesn't work, they checked it and sent it off for manf repair. Its been 9 days so far, should be in wed or thurs i should think
[Galaxy S III General] b0gd4n:
Did you had custom rom installed on it?
[Galaxy S III General] Obagleyfreer:
It seems to me that the majority of these cases are in the UK.

Could be a faulty batch of mobos and a lot of them made there way to the UK market.
[Galaxy S III General] pedropac72:
Here in Spain we have a lot of units too.

Enviado desde mi SGS3 reparado tras la Muerte Súbita usando Tapatalk
[Galaxy S III General] edugmax:
I took mine to the Samsung Customer Center and the mainboard was replaced to fix it, they said it wasn't a firmware problem.

There were a few people with Galaxys SIII there, but I don't know if they had the same problem.
[Galaxy S III General] Mister B:
Not just UK, spoke with telewiz worker today & they confirmed quite a high number of dead S3 returns here in Thailand.

Think I will be going for the XT925, sure the S3 has some great features but a 600USD paperweight is not what I want some time in the future along with warranty hassle & downtime plus knowledge of Samsungs poor warranty here & bad reputation in phone & notebook long term durability :-/
[Galaxy S III General] zziggy:
Just dropped mine into service. Left on charge last night. Today dead.

2-3 weeks they said it will be gone. Back to my old SGS1 for XMas/New Year. :(

i9300 purchased July this year. 2 year contract and by law in my country 2 year warranty. I hope I don't lose it for 2-3 weeks every 4 months though.
[Galaxy S III General] tommy2601:
Even I have purchased my device in july, probably my sg3's death is around the corner and I am getting all premonitions of it lately its behaving weirdly ie screen goes blank and doesn't respond at all and I ill have to pull the battery out and restart , I have tried many costume roms but no luck...and earlier I had carging issues which got solved by changing the usb cable(of htc brand).I had owened htc desire hd earlier for almost 1year 8 months and idint even have a single issue with it. I am pretty disappointed and frustrated with the quality of samsung.
[Galaxy S III General] DDRMSTRPRO:
Now, i have both a SGH-i747 and a GT-9300, and my ATT branded SGH-i747 is showing some of the symptoms of failure that the GT-9300s show.

Symptoms:

1. After a long rest, power button doesn't always turn screen on, just the capactive touch buttons sometimes. It usually means that I have to click the power button again, turning off the lights. Second time turning it on almost always works, though.

2. The home button, after a long rest, doesn't turn the screen on unless i triple-click it in rapid succession.

3. Front camera is considerably darker then the one on my GT-9300.

My i747 is a ATT launch unit.

Should i backup everything onto the other phone now, or am i just being paranoid?
[Galaxy S III General] Magnanimousdude:
Please post your date for purchase

Hello All,

Please post you s3 date of purchase and year of manufacture, in this way we can identify which month batches are faulty ones, i am pretty sure international version in all country is affected but need to identify which batches are faulty ones.

Some says Jun-July models (bought on august, September..) for some they bought when it got released means in the month of June-July itself so obviously those who bought in the month of Jun-July, there manufacture date should be either starting june or pre june.. just wanted to know so that rest be assured

Bought : August

Manufactured : July
[Galaxy S III General] Motogp1:
Got mine in June , build date June 7th
[Galaxy S III General] Toadeh:
Nope, it was 100% standard. Which is rare for me :)
[Galaxy S III General] Mrboxfacetramp13:
It's rare for most of us :cowboy:
[Galaxy S III General] mogambo000:
Mines suddenly died yesterday after working fine from the day i bought it in July. Was running Sotmax Jelly Bean Ultimate Stock V9.

Tried to get it into download and recovery mode, but it's not happening. Would it be worth it getting a jig to check if that will force it into download mode? Also as it is rooted and was on a custom rom, would samsung do a warranty repair?
[Galaxy S III General] aureum:
Samsung also wil not be able to boot the phone so he can't see if it's rooted or not. They will change You a mothertboard as You can read in older posts.
[Galaxy S III General] Paulb_:
Phone completely dead and now back for warranty at Amsterdam service center.

Symptoms: Last seen in normal operation at around 50% charge. Half hour later out of pocket, everything completely black, cool to the touch and unresponsive to every known key combination and battery disconnects. Not charging. Status confirmed at service center with different battery and chargers. Guy there said he had seen it before.

Model: 16GB Pebble Blue

Bought: july 24

Software: Rooted, Omega ROM, no overclocking or other special tweaks.
[Galaxy S III General] T0xic4u:
And what do you want to tell us with your screenshot?

Taper di Tap with my S3 @185 days
[Galaxy S III General] Superunleadedv:
s3 died today. hard earned 700$ down the drain. repair center is charging me 300$ to replace the motherboard. sigh... im feeling hopeless....
[Galaxy S III General] *GalaxyFanatic*:
Just checked my S3 & I got this...

So am I safe as ive had a few major freeze ups & even a couple of random reboots???

Sent from my GT-I9300 using Xparent ICS Tapatalk 2
[Galaxy S III General] Superunleadedv:
is it true? samsung will not cover international warranty? i have a dead s3... and repair center here in the Philippines will charge me 300$ to replace the motherboard...

is there any fix.. badly needed help.... :(
[Galaxy S III General] cyberdroxxx:
What ROM was on it when it died. Why they charge $300, No warranty, rooted?
[Galaxy S III General] yvliew:
my S3 i9300 also died yesterday. It went off all of a sudden. It was able to turn on but only Boot screen. saying Samsung galaxy S III ... I am rooted and custom. I couldn't went into recovery mode too.. So i went to samsung straight, the cs thought might be software glitch. says they will try to flash it. after one hour i was told they couldn't flash it either. So they had to change to motherboard. Lucky I was covered with warranty. It got fixed for free the next day. now my eMMC version showing

Type : VTU00M

Date : 12/2012

CID : too long

FwRev : 0xf7

Is this a safe chip???
[Galaxy S III General] Superunleadedv:
im on stock JB. havent messed with it. the repair center said my phone isn't from the Philippines so they have to charge me 300$ to replace the motherboard... so, im desperately looking for help.. 300$ is to big for me.

i saw an OTA fix on some tech site. but how can i do it when my phone is bricked.... :( oh samsung...
[Galaxy S III General] danarama:
Stock JB 4.1.2? 4.1.1?

What features did it have? MultiWindow? Editable Status bar toggles?
[Galaxy S III General] Superunleadedv:
i think i have the 4.1.2..
[Galaxy S III General] skivnit:
Presumably yes
[Galaxy S III General] odoto:
That would be really bad news, since we assumed all 4.1.2 stock roms are fixed :/
[Galaxy S III General] T0xic4u:
He said he is from Philippines. He said he was stock. Newest firmware for Phillipines is ta ta ta taaaaaa 4.1.1!!!

Taper di Tap with my S3 @185 days
[Galaxy S III General] yhrn:
No no no no. The fix is believed to have been introduced with XXELLA. Mine died on XXELL5 which is also 4.1.2 but older than XXELLA.
[Galaxy S III General] T0xic4u:
Nope. XXELL5 should be fixed too. Were you full stock when it died??

Taper di Tap with my S3 @185 days
[Galaxy S III General] odoto:
Wait a sec... I thought all versions down to XXELL1 have been checked (via string search) and were found safe? :/

(I'm on XELL4 myself)
[Galaxy S III General] danarama:
Actually we've deconstructed kernels all the way back to XXELKC and found the "fix" code.

However, we are still unsure if the fault is instantaneous or happens over time.

We still haven't seen any proof from users who have had sds on 4.1.2 that they were 100% stock, unrooted, unmodified, 100% of the time so basically, we still *know* nothing. All we have are theories
[Galaxy S III General] T0xic4u:
Yhrn wasn't on stock rom. He was on a custom rom and maybe custom kernel wich wasn't fixed.

He was on NeatRomLite.

Taper di Tap with my S3 @185 days
[Galaxy S III General] yhrn:
Ok, in that case I stand corrected. I was not on stock kernel.
[Galaxy S III General] Kjc99:
How can this one person get into recovery mode with a sudden death I thought only download mode was possible?

Galaxy S3

Omega Rom V37
[Galaxy S III General] yhrn:
In that case I don't think it is SDS. I could not even get into download mode. The phone was DEAD.