yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] danarama:
The code is within all 4.1.2 kernels.

Mien actually came back with 4.1.1 on it however. My SDS was in November, before 4.1.2
[Galaxy S III General] pickandwhammy:
I don't mean to sound rude, I'm just curious to know what I'm overlooking: if update7 contains the fix, why can't devs just look at that source and figure out what's changed from the previous source, with respect to wear levelling, of course?
[Galaxy S III General] sebarkh:
We know the differences, but we don't know what the declarations and functions mean, as they are related to the propriety Samsung files we have no sources for.

Sent from my washing machine...straight from the tumbler...
[Galaxy S III General] pickandwhammy:
Hmm, I see. This whole situation just sucks. I almost understand Entropy's frustration in his G+ post. Well, as much as a non-dev can.
[Galaxy S III General] yahyoh:
As I know :

Sammy don't share any changelog for Rom's nor kernel sources which suck :(

And comparing 2 source code is so hard cuz its contin a looooot of codes

But the genius Andreilux found the eMMC patch :D +
[Galaxy S III General] danarama:
If there was a 4.1.2 kernel without the fix and one with the fix, we could compare the binaries. However, we have to compare 4.1.1 to 4.1.2 and obviously there would be too many commits not related to the fix.

You can actually see the changes here in AndreiLux's Github commits:

https://github.com/AndreiLux/Perseus-S3/commit/54ddcbe7aff1c19c07f76a05ab45f37bcbae2951

But I dont know how that reflects in the binary
[Galaxy S III General] Rob2222:
Well, take it the other way... Burned components lead for sure to a dead phone.

But do we know is this is the same as our "sudden death" we here discussing about? It could also be burned cause of ... f.e. liquid damage cause of condensated water I think...

BR

Rob
[Galaxy S III General] yahyoh:
Hmm no I mean on sammy source code not on non stock kernels (cuz non stock kernels already have github with commits which easy to track ) but its hard to find all the changes in the new soruce code base :rolleyes:
[Galaxy S III General] LaughingJohn:
Got my phone back from repair, all working

I got my phone back from T-Mobile UK and it all seems to be working. They set me back to ICS so I've had to upgrade and to set everything up again.

The "repair details" just say:

Software Update

Screening

Which is odd as I was tracking the repair on their system and at one point it said Replacement "IC/PA/FILTER", but for some reason they've decided not to mention that :confused:
[Galaxy S III General] demlasjr:
Looks like Samsung Spain just confirmed those sudden death here: https://www.facebook.com/questions/10151189575046867/?comment_id=24119420&offset=0&total_comments=28

The weird thing is that they said "the update which fix this sudden death will be released soon". I asked them if the XXELC have the fix included or not (because they can talking about the carrier locked devices, which have other firmware). I'm curious what they will answer, if XXELC fixed the sudden death or not.

Screenshot to the discussion: http://i.imgur.com/4Ak6N.png
[Galaxy S III General] kofiaa:
Thanks, how about a translation?

Edit: I used Google translate

"It is not reset once or a thousand times. This problem, as we have explained in other reviews, is in one of the fields in the terminal memory and not have to take it to the store, where they are not technical but commercial, you have to take it to the service center where they know how to fix it. In any case, the update fixes it, is very close to release. Saludos"
[Galaxy S III General] qavro:
lol. that means (if it's yet to be released) that the whole fuss about ELLA was for nothing?!?
[Galaxy S III General] pickandwhammy:
@demlasjr: They might be saying fix is close because XELLA/LLC might not be a Spain-specific firmware?
[Galaxy S III General] qavro:
i was sure that XELLC is the official release for Spain...
[Galaxy S III General] demlasjr:
Guys, is saying:

You don't need to reset it thousands of times (the guy have the phone turning off all the time and others dying). The problem is, as we explained in other comments, with one of the memory fields of the phone and you have to sent it to technical support, not customer support, they know how to fix it. However, the update which fix the issue is soon to be released.

XELLA/LLC is the 4.1.2 for the unlocked devices in Spain. No idea, but this sounds like the last release isn't the one with the fix. So we are still ****ed LOL.
[Galaxy S III General] kaiur:
LLC is PHE (Spain). But I guess he says that because OTA update takes a few days to reach all unbraned phones (I hope Samsung has meant that)
[Galaxy S III General] jimbo77:
What's weird is that after everyone updated to either LLA/LLC and using patched kernel's I haven't read one single case of SDS... If you read the previous pages of this thread you'll see that after the kernels were patched and everyone updated there hasn't been reports of SDS when we used to read at least 1 or 2 per day in some cases....
[Galaxy S III General] modemfish:
The Birck

Mine died yesterday - was just on charge .. Comes up with no PIT partition when trying to reinstall rom - None of the PITs work.

Wrote a compliant email to Simon Stanford with reference to this forum thread.

received reply back below: So for anyone who doesn't have a warranty or proof of purchase please take note :)

I am sorry to hear that your GSIII has suffered failure.

You can arrange to send the phone for a warranty service by calling our customer care team 0330 726 7864 (assuming you are a UK based customer)

You will not need any filled in warranty card or copy of the proof of purchase as this product is clearly within its 24 month warranty period.

Kind Regards

-----------------------------------------------------------------

Ben Pearce

Executive Office

-----------------------------------------------------------------
[Galaxy S III General] jimbo77:
Would you mind sharing what configuration you have on your phone?

ROM?

KERNEL?

RECOVERY?

Thanks...
[Galaxy S III General] demlasjr:
Well, my device is over 6 months old and I had no SDS or any kind of failure. I got the FOTA update since the first day, so I don't think they was talking about LLC. Let's see if they reply back or we will get a new update next days.
[Galaxy S III General] wststreet:
got mine back

Hey guys, mine died about 2 weeks ago, I had CM 10.1 on it and sent it to warranty, I got it back working today, now I have 4.1.2 Samsung ROM on it. I'm a bit scared to flash anything on it. What do you recommend?
[Galaxy S III General] pickandwhammy:
Read this.
[Galaxy S III General] demlasjr:
One stupid question: is there anybody whose S3 died without being flashed at least one time? I don't plan to flash and install a custom, I'm just happy with the stock, so never flashed it. As mine is a survivor, I'm thinking if isn't this the reason never died. Maybe flashing makes the NAND going crazy and writing the files on bad sectors or smth
[Galaxy S III General] wststreet:
I really dislike the samsung rom, and it would be terrible if I were to remain stuck with it. As far as I understand from pickandwhammy's link, I should use a patched recovery. But then updating the rom will overwrite it, I'm waiting for a reply from the CM G+ community if the recovery updates are also patched.

---------- Post added at 04:23 PM ---------- Previous post was at 04:16 PM ----------

Sorry for double posting but I checked with an app and it says I have the

VWU00M 0xf0
[Galaxy S III General] pickandwhammy:
Updating a custom ROM will not overwrite the recovery.
[Galaxy S III General] Kjc99:
They sent it back to you with 4.1.2 on it what build? Maybe that's good news

Galaxy S3

Omega V37
[Galaxy S III General] danarama:
They always send it back with the latest
[Galaxy S III General] KPlax:
The last post 30 minutes ago said that they are speaking about the SII, the last actualization for the S3 fix the sudden death

Samsung Mobile España Perdona Laszlo Demeter estamos hablando de terminales diferentes, moteros viajeros hablan del S II NFC, a ese nos referíamos nosotros. La última actualización de S III sí elimina el riesgo al que estaban expuestos algunos S III. Saludos!
[Galaxy S III General] pickandwhammy:
If I gather correctly, you mean Samsung wasn't even talking about the S3, and so the patches that we think fix the eMMC bug probably do work?
[Galaxy S III General] Anthartic Rain:
I speak spanish. That thread was talking about Galaxy experience in general, and people was talking about SII problems too. Some previous comments said about SDS in SIII and the response says:

"...the last update for SIII indeed solve the risk in some SIII that where exposed to."

It don't say if is it about the Eynox Bug or SDS in specific, but previous comments only refer about SDS so we can deduce the response was about SDS.

They are not much clear and transparent with this, but is the only official reference about the solution for the problem.
[Galaxy S III General] kaiur:
Actually says : "The latest update of S III does eliminate the risk they were exposed to some S III", but what risk? Exynos exploit?.

I think Samsung never be clear about the sudden death of their terminals and causes.
[Galaxy S III General] gabrymr:
I don't think they can... first they would publicly announce that their device has problems. Second - I still don't think they know what the problem 100% is, so why to announce something that may not even be truth?
[Galaxy S III General] behemot24:
I think you're right - the motherf*****s sell 600 € phones and they don't even know how they work.

Then we have to wait for 3 weeks without phone until it's getting repaired, and after that we don't even know for how long the repaired phone will last, because samsung didn't find the cause and didn't make any announcement about it. And we also don't know if they're officially aware of the existence of the SDS and if they work on this matter.

Well done, Samsung...
[Galaxy S III General] Ohamn:
Hi there!

Mine suffered from SDS without ever being flashed. So unfortunately you are not safe if you don't flash either! :(

But I hope that you bought your phone with warranty so all you have to do is to send it in for repairs when/if it dies.

Good luck! :)

// Ohamn
[Galaxy S III General] gabrymr:
It kinda reminds me a bit of a situation with dell/alienware we had a few months ago. They released Bios update rev. 9, it disabled nvidia gpu's.

We cried for a new bios, because tech guys in forums found out it was bios problems, Dellianware said it's not Bios, it's something else... and in the mean time, Dell replaced countless mobo's, changed entire systems, to just fail again. And quite silently now they just release a new rev. of bios that just fixes the problem with a simple flash...
[Galaxy S III General] UncleBeer:
Technology isn't magic. It's all predictable, reproducible, and traceable. Let's not let Samsung wiggle out of this by being Luddites ourselves.
[Galaxy S III General] cocous:
hi i want to ask something if knows anyone.

all hw rev versions MP (1.100 1.200 1.300 1.400 1.500) for 16gb galaxy s3 has the same affected chip VTU00M 0XF1 ?

because i have the mp 1.400 and i have the same.

the only thing changing is the release date. mine is 10/2012.

this is right?

anyone with mp.1500 to tell me what chip it have?

thanks and sorry for my english
[Galaxy S III General] T0xic4u:
Ha, you are exactly the one I'm searching for. Are you rooted and used to flash kernel via recovery?

Taper di Tap with my S3 @183 days
[Galaxy S III General] ponepo:
Hey,

Here I am with:

RF cal: 2012.12.6

HW Rev.: MP 1.500

but:

VTU00M - 11/2012 - 0xf1
[Galaxy S III General] T0xic4u:
@ponepo

Would it mind you to do the test with the siyah special kernel and the Terminal app?

Taper di Tap with my S3 @183 days
[Galaxy S III General] ponepo:
I do not want to change anything in a few days because I use the "blue" to work. As soon as I can get with that I comment...
[Galaxy S III General] peondenegras:
I have update to 4.1.2 yesterday. Is it my phone in danger yet?
[Galaxy S III General] jeffnz:
You need to supply more information than that like running emmc checker from Google play. It pays to actually do some reading before posting as this has all been covered a lot
[Galaxy S III General] timage1979:
Right

I don't know if this is the same thing or is related at all. My phone has not died but over the past 4 days it has become completely unresponsive on a number of occasions. I would say it has happened about 10 times. I go to wake the phone using either the power or home button and nothing happens. The LED will continue to blink if there is a message, email or missed call so I know the phone is still on. Also the battery is never flat when this happens. The only way to get the phone working again is to pull the battery or hold the power button for 10secs to reset the device.

I have downloaded eMMC Brickbug Check from Google Play and it reports that my phone is the following:

Phone Model

Samsung moxx

eMMC chip

Type: VTU00M

Date:04/2012

CID:15010056545530304df1dc2c3adf4f37

FW Rev: 0xF1

Brick Bug?

NO. Sane chip.

Today Kies told me that there was an update which I then installed.

So my device info is as follows

Baseband vesion i9300XXELLA

Kernal version 3.0.31-742798

se.infra@SEP-111 #1

SMP PREEMPT Sat Dec 22 17:04:04 KST

2012

Build number JZ054K.I9300XXELLA

This update did nothing to fix the problem and I got my first freeze within the hour. I have now done a Factory data reset and am still getting the same problem. This is the first android that I have NOT rooted as I have always been happy with the way it has performed.

I have my receipt so can take it in for repair easily enough but just want to check with the experts first. The phone was bought from the Carphone Warehouse and was SIM Free.

I hope that this is enough info.

Thanks for any help.
[Galaxy S III General] owl74:
I know it sounds weird and unrelated, but can you try to reformat your sd card. IIRC this happened to users long time ago with desire hd....it only takes a couple of minutes... it's worth a try imho.
[Galaxy S III General] artesea:
Sounds very much like what mine was doing before it died. I'd suggest that you don't change anything else, with the update you are supposed to have a safe kernel but my guess is it will still die anyway. Whilst I'm sure you don't want to be a guinea pig you've already mentioned you've got the paperwork required to claim on the warranty if it does go wrong.
[Galaxy S III General] sgsboyo:
That sounds exactly like what was happening to mine too. I contacted Samsung, described what was happening and they told me my device was faulty and I'd have to return it to them for checking. So that's where my phone is since today...

I thought at first it might be a problem with external sd card (something i was reading on here gave me that idea) but even without the card in it still would freeze up.

Just waiting to hear back from Samsung to see what they eventually do with it...
[Galaxy S III General] edgetas:
Another one bites the dust ...

For the record, a 16GB 3G from Telstra Australia. Only had stock standard ROMS – inc. last JB release from Testra and never rooted – despite temptation. Been a bit laggy for a few weeks but I had put that down to the phone memory pretty full with installed apps. Looked up someone's phone number, then about half an hour later ... nothing. No lights, no response, removed battery, tried 2 different chargers & PC connection. Completely dead. Off to Telstra ... "A new way to wait".
[Galaxy S III General] ymy3890:
I wrote to Samsung Malaysia and they replied saying they aware the problem and in the midst of fixing but when i asked when will release, they just silent....:(
[Galaxy S III General] sak500:
Mine after it was returned with replaced board.

Samsung m0xx

eMMC chip

Type: VTU00M

Date:09/2012

CID:

FwRev: 0xf1

Brick Bug?

No. Sane chip

It passed the full test.

Details after typing *#12580*369#

RF cal: 2012.12.13

HW Rev.: MP 1.500
[Galaxy S III General] sohail667:
is emmc check is safe or not?

The check dont write and is safe. If your device freeze you memory is damaged. For unfreeze the device remove battery and restart.
[Galaxy S III General] artesea:
No the test doesn't do anything useful on the GS3, we are only using the app to find model and firmware of the EMMC.
[Galaxy S III General] pijindrin:
Well I'm from Argentina and the warranty conditions sock. So having the affected chip after 3 months carrying the virus, I decided to update to stock XXELLA. So I'm running stock kernel. I only rooted via Odin cf root. So my questions are the following:

1. Does rooting expose me?

2. What do you think about the amount of time (3 months) I was running the phone before I flashed to XXELLA? Too much? Enough to damage the phone?

3. Anyone with the faulty chip who didn't have a SDS and have been using the phone for more than 6 or 7 months? It would be great to know that not all the devices with the affected chip have a SDS. Is that possible?

4. I' ve been reading the thread and found lots of synthoms for SDS. So, which synthoms are the most common?

6. Does the emmc chek app or the voodoo anti... app have to show me someting different after flashing to XXELLA?

6. Did I bother you with my questions? :p . Sorry if I did.

Thank you

From one scared paranoid to plenty of paranoids!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] legend_wok:
did you read through this thread? the answers to your questions are there.
[Galaxy S III General] sodeknetters:
Reading this thread after page 300 feels a bit like watching a merry-go-round on a fancy fair.. We've seen everything thats coming by multiple times already. If we go on like this, any new info that will come up might be buried under useless blabla in a matter of hours!!

So please stop replying to all those guys who come ask the same bloody question without reading 1 page back....
[Galaxy S III General] pijindrin:
I did read the thread. To be honest one guy says one thing and another says the oposite. So you can't expect people to stop asking this kind of questions. I only asked those questions cause I'm not sure about the answers. If you guys don't feel like answering then don't. I wouldn't have asked if I had known the answers. Be polite. Rudness will lead you to SDS :D

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] danarama:
1. Not in itself

2. I think nothing of it

3. Can't answer

4. We're not 100% certain what is or is not a symptom. If you wake up one day and your phone doesn't wake up, you have it

5. This is in post one of the sticky thread "sds -are you covered"
[Galaxy S III General] pijindrin:
Thank you for your time!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] hermeson:
There is only one symptoms, after 4 months, your phone dies... And there is no way to put it on again. That's it.

Samsung, apparently release a version which fix this issue, but what happened to whom already had their phone dead?
[Galaxy S III General] -A-P-M-:
But people had sudden death with XXELLA (flashed with Odin / Kies), so why do you think XXELLA fixes sudden death?
[Galaxy S III General] pickandwhammy:
Read SDS theories here.
[Galaxy S III General] cyberdroxxx:
I suggest that you do a factory reset after the update. It did help me with the symptoms your S3 is having.
[Galaxy S III General] Kjc99:
I ran the memory checker in the emmc check app and it passed...does this mean anything or not really as this is an SII app

Galaxy S3

Omeaga Rom V37
[Galaxy S III General] danarama:
Means nothing. Don't run anything in that app. Use it ONLY to get the version
[Galaxy S III General] BlackMonkey:
My S3 ist few days over 6 months ans still alive. All other people that i know and have an S3 didnt have any SDS. I dont think that all S3 will die in the first 6 months.

Edit: Still on LL5, CF auto root and waiting for new official update from vodafone in Germany
[Galaxy S III General] pijindrin:
Thanks for answering!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] cyberdroxxx:
The memory checker is only useable for checking the eMMC chip name and firmware on our SGS3. If your chip type is detected as VTU00M fw 0xf1, then your phone is affected. So far there is no reports of SDS from other chip type.

---------- Post added at 10:26 AM ---------- Previous post was at 10:14 AM ----------

My S3 has the infected VTU00M 0xf1 eMMC. I did experience lag and stuck screen and shutdowns. Sometimes phone rings with incoming calls but I cannot answer those call because my phone just do not respond at all. It is now better after ELLA update.
[Galaxy S III General] normally_crazy:
If I want to go back to stock ROM that my phone came with, I can reboot into recovery and restore from the original ROM nandroid backup I have saved.

Then use titanium back up to get my apps updated and then unroot.

I will be back on stock, right?
[Galaxy S III General] pickandwhammy:
1) You'll still have CWM (or whichever) recovery that you used to restore from

2) I've never unrooted so I don't know if it'll leave traces behind, but I think it will
[Galaxy S III General] T0xic4u:
Show me one case. Didn't read about one who was really on stock.

Taper di Tap with my S3 @183 days
[Galaxy S III General] qavro:
The correct statement is: If your chip type is detected as VTU00M fw 0xf1, then your phone CAN BE affected.

As there are literally millions of S3 out there with exact the same chip and never experienced one single issue. I am one of them. Form what i have understood the main supposition now is that only a single batch with a specific firmware date (13/04/2012) has this issue.

Not all VTU00M/0xF1 chips! And, no, you can't read the firmware date by usual methods to see if you are on the fatidic 13/04 date...

just my 2 cents...
[Galaxy S III General] fishcake13:
On that note. Im on the same chip set but my fw date is 05/2012 with no issues
[Galaxy S III General] T0xic4u:
Sorry to say, but some deeper investigation show, that all chips with 0XF1 may have the same firmware.

13.04.2012

I need some further tests to be 100% sure, but it looks like.

Taper di Tap with my S3 @183 days
[Galaxy S III General] qavro:
Ok, we will wait and see, but that means all VTU00M / 0xf1 chips has to fail and this is very very unlikelly...the number of S3 that never experienced a problem is still huge. Or maybe is too soon to say that...
[Galaxy S III General] TheWizardbc:
My phone has yesterday returned from the repair center.

These are the changes:

It looks like there is a new board version.
[Galaxy S III General] T0xic4u:
Samsung started to implement the fix in its Kernel in November 2012. They switched over to a new version 0XF7 in November 2012. All I need is one guy with eMMC-Chip-Date 11/12 and version 0XF1 to do a test and then we know it for sure......

And "No", that still does not mean that all devices with 0XF1 will fail. I still think that special circumstances have to happen to break your S3.

Taper di Tap with my S3 @184 days
[Galaxy S III General] pickandwhammy:
My phone was bought in December. Had the new bootloader on stock. eMMC app gives me

Type: VTU000M

Date: 09/2012

Revision: 0xf1

Does my device fit into your category?
[Galaxy S III General] T0xic4u:
Your date is 09/12

I need one with 11/12 but still 0XF1

Taper di Tap with my S3 @183 days
[Galaxy S III General] pickandwhammy:
Hmm, I see. Don't think any handsets from my country will have that yet. Maybe Europe/US?
[Galaxy S III General] qavro:
T0xic4u, what you say makes a lot of sense. I think that we will have a huge benefit if we can understand what the fucx those circumstances are :( I believe that even Samsung don't have a clue...
[Galaxy S III General] T0xic4u:
I found ONE guy with this chip, but he wants to stay stock and doesn't want to flash a kernel to do the test. :(

Taper di Tap with my S3 @183 days
[Galaxy S III General] ponepo:
As we discussed yesterday, this is mine. And I am increasingly convinced that almost all VTU00M 0xf1 are infected. As I can change the kernel and run the command, I show the result