yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] Egan:
Follow up to this post

Ok my device is sent for repair to Samsung. The repair center told me its a known problem and I probably receive a new one. I hope that new one will be a 32GB version and not the same 16GB version, cause that would mean another ticker. I'll have it back in 12 days :).
[Galaxy S III General] zoeperzazke:
My Galaxy S3 died Saturday after 197 days of use. It happend in teh afternoon, when I hadn't used it for some hours and took it out again it didn't start up. Completely dead :(

I have a completely original phone, never changed the software or firmware manually.

Happened in the Netherlands, but I noted that the shops of our providers don't recognize the problem yet. I have to send it to the only repair centre we have, hopefully it'll be back soon....
[Galaxy S III General] _2bad4u_:
This problem happens only to 16 GB, or it's all devices (16,32,64GB)
[Galaxy S III General] malamen123:
I use emmc check and i have this my phone is affected? When i use exynus mem check i see this
[Galaxy S III General] sewe:
I don't, mine is MAG4FB

Skickat från min GT-N7105 via Tapatalk 2
[Galaxy S III General] reycharlesconrad:
I just got my phone back from the service center. It was rooted the time that it was sent in but they were not able to check as it can only go to the download mode. They replaced the motherboard free of charge.

Now I'm checking again the Emmc code and I still have the VTU00M chip with fwrev:0xf7. Does this mean that my phone can die again soon?
[Galaxy S III General] wooptarik:
probably, but not soon though
[Galaxy S III General] Crunozaur:
so instead of fixing the issue, samsung made it easier to reject your warranty, correct?

i can't wait till i change my phone on google x!
[Galaxy S III General] juliano_q:
So they are replacing the motherboards with the same defective model and probably a lot of people will have trouble again in around 6 months after the warranty period ended?

Way to go Sammy.
[Galaxy S III General] enigma1981:
I'm VTU00M and fwrev 0xf1... dated 06/2012

Should I worry more than I already am?

Swyped from my Galaxy SIII using Tapatalk 2
[Galaxy S III General] Crunozaur:
i think warranty on each hardware piece is extended if they repair it, but it depends on country's regulations i suppose
[Galaxy S III General] skivnit:
Mine is same and dated as 05/12.
[Galaxy S III General] whitebait:
I don't know if it makes any difference, but my replacement mainboard is:

Type: VTU00M

Date: 11/2012

FwRev: 0xf7

I'm on XELLA, BTU UK unbranded handset.
[Galaxy S III General] freakerload:
Hello i have flashed the new bootloader xxella per odin and have the rom omega v36 on it.

Can i downgrade the bootloader when i flash my stock 4.1.1 Rom per odin?

I do not understand it properly, i have no warranty on xxella with custom rom and kernel?

Or what does it mean samsung can easier reject the warranty?
[Galaxy S III General] qavro:
just adding to the list:

Type: VTU00M

Date: 07.2012

FwRev: 0xf1

Brickbug: NO. Sane chip

After testing the memory i get: Congratulation. Your test passed

with an average of 27MB/sec
[Galaxy S III General] masterex567:
Mine is also 7/2012.

How do i flash stock recovery alongside custom rom?
[Galaxy S III General] DonHuan:
Mine

32GB

version:

Type: VWU00M

Date: 05/2012

FwRev: 0xf0

Bought it in July 2012. So far it is fine.
[Galaxy S III General] zoot1:
You will have warranty if your phone dies completely..

However with the new bootloader it is difficult to fake that you have not rooted/flashed your phone.. The binary counter resets after every boot AFAIK.. And there is an ! Mark in the download screen..

Moving back to older bootloader is again difficult as you have to do it via the OTA way as not all firmwares have bootloader packed with it and cannot be downgraded using Odin.. Older bootloader gets blacklisted.. Again AFAIK

That app checks for a bug which was existing in older gs2 models not suitable for sgs3 sds problem.. No one knows why and how this happens so everything is a guess..
[Galaxy S III General] thekoRngear:
Not that difficult now.

Method by dr Love that worked for me.

Simple Odia Method
[Galaxy S III General] jimbo77:
My SGS3 marble white 16GB says it was manufactured on 6.06.2012 so it just has passed the 7 months mark...I bought it on July 14th though...

I haven't had any issue or early symptom of SDS, i hope it runs just fine...

Both Battery and Phone were manufactured in China :)
[Galaxy S III General] Damien7:
again...

Hello, my gs3 died yesterday for the second time. first time it was in october 2012, and at the samsung center they replaced the mainboard of the phone. it happened with android 4.0.4 official stock.

and now same issue again :( I picked up the phone to unlock it and it was turned off without any possibility to turn it on..

Today I've brought it to the assistance center again...

It's an italian device, 16GB with JB 4.1.1 stock, bought in june 2012
[Galaxy S III General] duhhh:
wtf never again samsung
[Galaxy S III General] fmtrx:
wear level

It would be nice if we had an app that could measure the NAND "wear" level.

But i am not sure if this is possible. I am not aware if manufacturer has a SMART-like mechanism (as found in hard disks) implemented

in order to get its readings...
[Galaxy S III General] moujibzinc:
You're safe !

You're the first person to report a DSDS = Double SDS ! #facepalm
[Galaxy S III General] UncleBeer:
Well, it's gonna come to that for many of us, since they're replacing faulty boards with . . . faulty boards. PR-wise, it'd be smart for Samsung to make an open admission of the problem, and arrange some sort of swap / upgrade deal for all affected.
[Galaxy S III General] Damien7:
nice... I signed up here for the occasion :crying:

you're absolutely right
[Galaxy S III General] DonHuan:
To swap 20 million phones? Cool joke.
[Galaxy S III General] blyx21:
Wow your also the first one I heard got died in ics rom. Thats s**t! :mad:
[Galaxy S III General] skivnit:
I bought mine in May 2012. It's okay for now. I'm doing something different though. I'm just swapping batteries. I hardly charge the phone directly. I dunno. If that is related
[Galaxy S III General] donteo:
How i check the Emmc code :confused: :confused:
[Galaxy S III General] erto90:
from play store download eMMC Check
[Galaxy S III General] offgrey:
He's not necessarily safe. We aren't even really sure that it's the eMMC chip that fails. At this point in time, when Samsung hasn't announced what's causing the SDS exactly and no one in XDA has figured it out yet, it's still just unfortunately an educated guess.
[Galaxy S III General] fedort:
Is the blue screen a sign of sudden death? I started having a blue screen since last month when getting the phone out of deep sleep.
[Galaxy S III General] mike1986.:
Flashing custom ROMs in most cases doesn't void warranty.

http://xdaforums.com/showthread.php?t=1894668
[Galaxy S III General] mark3d4death:
Nope! No power at all, no charging screen when plugged in, no nothing! No download mode with the jig either (not even sure if these get the s3 into download mode as with the s2)... But I've sent it off to Samsung via Special Delivery today, so I'll have to wait and see! Hopefully it's too dead for them to JTAG or whatever they do to read the flash count as mine is 1 due to not being able to reset the new bootloader using TA.

---------- Post added at 05:02 PM ---------- Previous post was at 04:59 PM ----------

That's cool! Thanks! :)... Hopefully all I will be well then! I don't suppose you know if this effects the Galaxy Note II as well? Due to the similar hardware?
[Galaxy S III General] thorcyar:
question

Hello

has anyone seen arround there a LTE model (i9305) affected by sds please ?

Downloaded emmc and info shown is :

phone model : m3xx

eMMC chip :

type MAG4FB

date : 09/2012

FwRev : 0xf7
[Galaxy S III General] intrudar:
Seriously is this a conspiracy against s3 or really have do something with?!. :confused:
[Galaxy S III General] Ahish.s:
Delete
[Galaxy S III General] skivnit:
Let's talk numbers here. How many xda users have a s3 and how many experienced the sds? This will give us a pretty good sample for statistical studies.

I think it should be front paged and pinned

Swyped from another galaxy
[Galaxy S III General] PjotrFias:
Was XELLA on the phone when you got it back? Because 0xf7 is new FwRev for this chip.

Can someone that updated phone to XELLA with Odin, Kies or OTA check eMMC chip. If it updates FwRev, then it really fixes SDS.

Fun fact, SDS is a big political party over here, currently they have the power and we are falling deeper and deeper.
[Galaxy S III General] fatsomak:
After extensively reading almost all the threads, one can safely say it is

ONLY THE 16GB model

which is suffering sudden death. Anyone with a dead 32gb raise yo hand. Im buying S3 32gb end of month :D thanx to this thread :D
[Galaxy S III General] xanthrax:
Won't be relevant mate , all SG s3 haters will vote yes , at least this is what I would do for an iPhone poll . :D The polls in general aren't relevant anyway , at least for me even though I already opened one a month ago ... :cool:
[Galaxy S III General] PIRATA!:
So no way to fix this at the moment, not even with the last firmware XXELLA?
[Galaxy S III General] theobabis:
Sorry to disappoint you but until Samsung gives the permission and sends the appropriate title it won't happen.

Not here, nor nowhere else.

It's really like the "we hear you" about the sources which now nobody talks about.

Very sorry to say it, but really can't believe that everybody babysits sammy.

We don't want a solution, we need the problem.
[Galaxy S III General] OmarBizreh:
I have: VTU00M fwrev 0xf1 flash dated: 09/2012

got the phone 2 weeks ago.

Never charge with wall charger after I have lost my Xperia P because of it (According to what many fix centers told me). Anyhow I didn't really like the idea of having the phone recharged in 40 minutes (from 1% -> 100% that was the case of Xperia P)

So I didn't want to risk it with my S3, let's hope the problem turns out to be because of using the wall charger and not a faulty hardware as some of use have no warranty (I'm one of them :( )

My Phone Info:

Android: 4.1.2 (Flashed using Odin) Using Switzerland copy downloaded from Sammobile.

Manufactored In: Vietnam

Battery: Cell created in Korea, assembled in Vietnam

Good luck people :)
[Galaxy S III General] jody2k:
No.
[Galaxy S III General] htcsnap93:
I have seen this thread for the first time. I spit around but couldnt find the intel.

My emmc check

eMMC chip :

type vtu00m

date : 05/2012

FwRev : 0xf1

And the exynos mem bug is present

2 questions

1. What is the exynos mem bug

2. Why is de vtu00m type flagged als vulnerable here on xda ?

Kind regards,

Thomas
[Galaxy S III General] koolshubh:
Can I do a memory check using emmc check???
[Galaxy S III General] PjotrFias:
Yes
[Galaxy S III General] offgrey:
If I were you I'd wait for the S4 in May, but that might just be you waiting for another can of problems. :\ But hey, we never know, maybe a fix of some sort for SDS (or at least, information on the damn issue) will be out by then. I think you should cross that road when you get there. If the possibility of losing data is a dealbreaker from you, maybe you should consider another phone. On the other hand, it isn't really that surprising that there are many many many S3s being reported as suddenly dying for the mere fact that more than 30 million handsets were sold. There will always be quality issues/bugs with all products, imo.

The Exynos mem bug was an exploit that could root your phone without flashing anything on Odin. Theoretically, any app could just root for you without you even knowing and wreak havoc on your phone.

The VTU00M type of eMMC is flagged as vulnerable to S3 Sudden Death for the mere fact that many of the S3's use this particular chip. As such, many (if not all) of the SDS cases reported here were probably using VTU00M chip, hence it being flagged as vulnerable.
[Galaxy S III General] Thin_Bezel:
Yeah but how come that all reported devices are dead only after a period of 200-250 days????
[Galaxy S III General] sewe:
Note 2 seems to die aswell

Skickat från min GT-N7105 via Tapatalk 2
[Galaxy S III General] nfribeiro:
I truly believe that Samsung really doesn't know how to fix this SDS issue. Instead, they decided to give the impression that they know about the problem and also that they are working on a fix. It will be bad for their reputation to admit another faulty device after the eMMC hardbrick bug present on the Galaxy Notes and in the latest firmwares of S2 (4.0.4).

At least, they could give as a bonus like a warning message:

"This device will self-destruct in 5 seconds" :D
[Galaxy S III General] dr.ketan:
Just to add my friend's device was s3 and that's why I have posted here.

I have not read such issue on note2 forum, surprised to see two cases above. May be it could be something other rather than sds.
[Galaxy S III General] nfribeiro:
Dr Ketan, I hope you are right, my friend.
[Galaxy S III General] sewe:
Sorry about that

Skickat från min GT-N7105 via Tapatalk 2
[Galaxy S III General] koolshubh:
What is memory check in emmc check..

I statrted it in the app and then aborted it since it was very time consuming...
[Galaxy S III General] sam77744:
I want to know

I want to know, when I go in recovery mod for f-reset that time there android icon was slept and red tringle seen, what is this, pls help me thanks in advance.
[Galaxy S III General] Steveon:
deleted

Mistakes
[Galaxy S III General] exhardy:
my s3 just died just a few moments ago, with the newest bootloader flashed from Samsung CS (because i just got a screen replacement 3 days ago),

just trying to browse Facebook before sleep but it locks up suddenly and it is dead now.
[Galaxy S III General] vasp3690:
My phone apparently was booked with an engineer today and service was completed within a day. If that wasn't a motherboard replacement I'm taking my hats off for them. Now to see how fast they ship it back to me
[Galaxy S III General] storm01amorteo:
If that wasnt a mobo replacement, what it could be?. We all would like to know if problem is related to firmware or a hardware problem. Please let us know.
[Galaxy S III General] htcsnap93:
Thanks mate, with all the holidays that went by I havent had time to read in.

Last question, how can i prevent my device to be rooted by such apps ?
[Galaxy S III General] Blue_Nexus:
Maybe not a main board replacement ?

Hi Folks,

I called samsung today to check on the status of my phone. It has been sitting at awaiting parts from 3/1/13 and they've had the phone from 21/12/12.

I asked what parts had been ordered and what the exact problem was. At this point I hit a brick wall no one knew nothing. I insisted that if they have ordered parts they must have diagnosed the fault, I explained that I wanted the detail behind the fault to reassure me that if I got a repaired phone the same issue would not reoccur, eventually (after a long long time on hold) they just hung up on me.

It seems that if they do know the cause of SDS then its a secret. I am assuming that whatever this part is they have ordered is not a mainboard (they'd be up the creek if they'd ran out of main boards since 3/1/13) Surely they can't have done that many repairs ? :silly:
[Galaxy S III General] vasp3690:
According to them defaults sticking was a hardware problem as firmware flashing did not cure it the first time.

Could have been early symptoms.. who knows?

I dud have the 1.100 mmc and vtu
[Galaxy S III General] jay_m3:
Mine also since 29 may and still running smoothly! !:)

---------- Post added at 08:51 PM ---------- Previous post was at 08:46 PM ----------

It checks your emmc health it should show 14, 7 gb checked if you're on the 16 gb version
[Galaxy S III General] mitky82:
Just change charger with that from S2

5V-0, 7A

Gharging time 2,5h.

And dont use deffected usb cable, who broke our phones.

To check if cable is deffected, just put to pc and phone and wait to notifications from pc for connect/disconnect

If hapens about a minute or more connect/disconnect, again and again is deffective.

Or just dont use them.

;)

Im with one of the first device, never use original charger and cable after i see connecting/disconnecting again and again and i dont have any problem.

Maybe that connect/disconnect with time broke some part in device.

Phone when is on charge dont display that connect/disconnect but its happen.
[Galaxy S III General] InfX:
You would need to peek into the wear leveler data structures for that, those are only accessible to the microcode running inside the eMMC chip. But i'd really like to hear about anyone managing to pull this off anyway :)
[Galaxy S III General] jay_m3:
Out of target. ..
[Galaxy S III General] blackspeedy:
Mine is from 5-30-2012(222 days) and it is still alive:(

Why i don't like it? Now i am running on stock firmware.I wanna be 100% sure that i will have my warranty.

I am running on XXELLA 4.1.2

HWRev: MP 1.100
[Galaxy S III General] vasp3690:
I doubt that there is anyone in the world that can reweld items on the mainboard other than the usb port. All of the rest of the parts most likely are done by machines inside the samsung factory. Its much easier to replace the whole thing rather than wait for a part for it. Looks like the repair center must have been overlooking your repair and not being clear
[Galaxy S III General] whitebait:
No, when I got it back it was on 4.1.1, that was 31st Dec. As soon as I connected it to Kies it said it wanted to do an update and got me on 4.1.2, I then got XELLA as an OTA update a few days later. The mainboard rev is 1.500. Can't recall what the FwRev was when I got it back from Samsung, sorry.
[Galaxy S III General] arkane78:
The date you give, is that the date you ordered the phone or the date it arrived or it's manufacture date?

If the manufacture date, how do you get that information, I can't find it on mine.
[Galaxy S III General] emelsk:
I'm running positively verified ELLA bootloader; eMMC check still shows FwRev 0xf1, though.
[Galaxy S III General] SpudULike:
Confirmation of terms of SDS

If this has been asked before then sorry, but I need an explicit reminder away from the noise throughout this thread.

Some have talked of SDS only referring to phones that are completely dead, by this I assume no LED when on a charger, nothing at all when attempting to power up. Others, like me, have added to this thread with phones that are not completely dead, their phones power up but get stuck at the boot loader screen, and they can still get to the download screen, but cannot flash because of a .pit error.

Are these phone suffering the same problem? If not, is there a syndrome that my phone, and those like it, can be described to have?

To all intents and purposes, my phone is currently a paperweight and could be confused by some as 'dead'. I think this needs to be made clear because, if there is more than one reason why phones are becoming regularly unusable then this should be even more worrying.
[Galaxy S III General] jonny68:
Update from me

Got a brand new Galaxy S3 from fonemenders, checked the IMEI number and its different so it appears instead of repairing the phone they just gave me a new one, the guy said it was sent to Samsung, maybe they are inundated with so many dead Galaxy S3, s they don't have time to repair them all.

Switched the phone on and checked, it was on ICS but updated to Jelly Bean now, have to wait till I go to a computer tomorrow to root as i just use Nexus 7 and can't use that or indeed the phone itself to root.

Phone currently says I9300NELK1 which I believe to be JB but I'm definitely not staying on stock, back to AOSP for me, Liquid Smooth ROM.

I'm delighted to get a new phone however I'm still concerned about what might happen in the future, a fix for this has to come about soon, have read all through this thread there is mass confusion but i don't believe ella is the fix for the sudden death.

Taking me hours to download all my apps again, set phone up, etc but talk about relief.

Hope those affected get sorted.
[Galaxy S III General] whitebait:
I've been treating the two as the same thing. Same result anyway, and it seems likely that the cause is the same. There was talk earlier in the thread about it being different degrees of corruption in the eMMC. Mine died in the same way yours did, stuck in a bootloop. And Samsung's fix was a mainboard replacement, same as the phones that completely die...
[Galaxy S III General] jay_m3:
So do I
[Galaxy S III General] InfX:
Same here.
[Galaxy S III General] perry04:
Its the Kernel Which erases emmc Bug , Not the bootloader ;)

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III General] xcartay:
New Bux Fix with XXELLA Jellybean 4.1.2

Yesterday reading about the SUDDEN DEATH issue, i found this article: http://androidadvices.com/exynos-bug-fix-galaxy-s3-update-with-xxella-jellybean-firmware/ but when i try to implement it in my device i get an error message from ODIN that reads like this: "MD5 Hash Invalid" and the process stops.

i´m following the exact instructions, use specified software and versions and i tried a lots of times, but always get the same mistake. How can i install this fix? Whats is this MD5 Hash error?

Mi device is the SGS3, model GT-I9300

Android 4.1.1

Baseband I9300UBDLI2

It´s all original, except for the root i made only to use Titanium Backup

Can some help Me? i dont want to loose my phone, it´s only a month old. :crying:

Thanks!!!
[Galaxy S III General] InfX:
We are not talking the eMMC dev permissions stuff here, we are talking about the sudden death issue.
[Galaxy S III General] mitky82:
Re download firmware or, download from here-XDA.

http://xdaforums.com/showthread.php?t=2077844
[Galaxy S III General] RectorReflector:
Please! Stop spamming useless posts!

Only react if your phone died. Yours is still running, so what's the problem? Suffering of attentionproblems?
[Galaxy S III General] dimi22:
Hey fellows i am very busy last days but just to let you know.

Today the dutch Samsung 4.1.2 update came out for the first time. I heard nothing about a fix, because the first message from samsung came from the Netherlands i think if the 4.1.2 had the SDS fix Samsung had published that....

But But... is there anyone who can check if there is something changed in the rom? in the bootloader? maybe it is fixed and Samsung shuts the **** up because its already to much bad publicity for them.. don't know?

Other news... i have about 250 report and when i have time i think friday.. i wil make publish it on a blog website and i will create a petition website for refunds.
[Galaxy S III General] vibsOveebs:
Question/Concern

I realized Samsung is saying the fixed the Exynose security threat and the sudden death with MP 1.100 I have a 7 month old i9300 but I live in U.S and I'm a heavy flasher. So I dont plan on switching to Omega 36 or the new XXELK Jan 13 fix.. Let's say my phone dies one day, would I give it to Samsung U.S to fix it?:confused::confused:

Thanks in advance!
[Galaxy S III General] htcsnap93:
In most cases if your motherboard breaks or burns you are saved. All memory is welded on it and they cant and wont look if your phone is modded. It is near impossible.

In most cases.
[Galaxy S III General] vibsOveebs:
Thanks

Thanks, but just to make sure Sam US will take care of it it by sending it to uk or something?
[Galaxy S III General] htcsnap93:
I cant awnser that. I would jump the bullet though if you know for a fact that it is the motherboard and not a faulty flash!

I had an Sony Erricson X10i and it broke down twice with a burned mobo whilst having a custom rom. First time the phone company replaced it, the second time they did it in the repair center of SE. Both free of charge.
[Galaxy S III General] amirharony:
i had the same problem and posted it in the help forum.. can u move it here?

http://xdaforums.com/showthread.php?p=34886901#post34886901