yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] behemot24:
my S3 (firmware ELLA rooted) died today in the middle of the day :good:

I used it before noon, and when I wanted to call somebody after lunch, all I found in my pocket was a brick :highfive: No download mode and no sign of life when I put it to charge. Really dead.

I'm going tomorrow at a samsung center...
[Galaxy S III General] skivnit:
I have another theory. My s3 used to reboot randomly a lot when i leave it on my pocket and drive. I dunno if its the pressure or the heat but every time i took it out after a long drive it was very hot and unresponsive. I had to keep the power button pressed until it rebooted. Now that disabled the auto screen light off, it stopped doing that. I did not have one reboot for more than a month now

Swyped from another galaxy
[Galaxy S III General] Fallen04:
My S3 died (half dead), no recovery, had download mode but wasn't able to flash anything. Sent the phone away for repairs and they replaced the mainboard under warranty. The phone was purchased in June (16GB international version)
[Galaxy S III General] joanquro:
Downgrading the bootloader is easier than that....

see this, it works.

http://xdaforums.com/showthread.php?t=2081748
[Galaxy S III General] XenomorphXx121:
Phone model samsung m0xx

Emmc chip VTU00M

Date 06/2012

Brick bug? No

Memory test said congratulations

Only ever use cable and plug that came with phone and have firmware build xxell4 and baseband xxell4

Had no problems as yet
[Galaxy S III General] 75markus:
i guess mine is one of the oldest (emmc 04/2012) see screenshot

but ... no problems till now ;

my co-workers SIII is newer and ... died last week :(

he was running CWM & CM 10.1, but they didn´t ask anyway; he should get it back repaired end of this week.
[Galaxy S III General] CHEVYbarracuda1:
OMG im rly asking myself why i bought this device.. Like im living in fear will my phone die.. If it is goin to die just it shud die when im situation when i dont need phone.. Just imagine it dying when u need phone urgently.. Rly i dont want nobody to experience this..
[Galaxy S III General] erlos:
When u bought device ?
[Galaxy S III General] Ohamn:
At last...

I'm one of the "happy" owners of a "half dead" S3.

http://xdaforums.com/showpost.php?p=35451419&postcount=398

I sent the phone in December 17:th.

Today I got confirmation from the store where I left my phone for shipment to Samsung that my phone is repaired and can be collected! :good:

They swapped the main board and upgraded to the "latest software" according to the shop.

The phone was serviced by Samsung Sweden.

My work mate have collected the phone and I will get it tomorrow morning at work!! :D

Will definitely get back with more info tomorrow when I have the phone in my hand!

// Ohamn
[Galaxy S III General] drakester09:
Very relevant information

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

Seems the fix is inside the update 7 sources.
[Galaxy S III General] Neokazaki:
Wrong threaf, sorry

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III General] kaiur:
Can anyone explain in simply words the meaning? tanks
[Galaxy S III General] Sad56:
New sources are older than update 6.

But new sources include the sudden death fix.

So now Andreilux can provide the files to be include on all custom kernel to fix the sudden death.

Fixs are all in the kernel, not in the bootloader.

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III General] dimi22:
I think a the same. Some app must be causing overheating while charging overnight and that bricks the phone.

---------- Post added at 11:05 PM ---------- Previous post was at 11:02 PM ----------

Although its kind of old did someone maybe checked if this or some kind of code is in the new update?

https://android.googlesource.com/kernel/omap/+/3c57a612f12b069bbc863ec0c74a26850d76a9e8
[Galaxy S III General] kaiur:
Update 7 is ELLA, isn't it? And update 6 is ELL4?

Thanks in advance
[Galaxy S III General] MuertoKo:
Actually it's not older than U6 but older than other sources where devs pic code from.

Samsung releases some big repository for a bunch of devices and releases fixes to each one that can be applied to all. So they have info from a tablet or from Note 2 sources that is more up to date than U7, but this one includes a fix for Sudden Dead issue :)

Waiting for Andrei to confirm this but I bet I read this from him some time ago (about sources) and he already confirmed that U7 kernel fixes the issue.

Btw I guess LLA kernel is U7 updated but had no confirmation of it, at least not that I could find!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] UncleBeer:
Nope. Waaaay too many examples of folks' phones that weren't even plugged in suffering SDS. If charging has anything to do with it, it appears it's only a minor contributing factor.
[Galaxy S III General] iridaki:
FINALLY, a confirmation!!

iR¡D@k!* ? from i9300 via Tapatalk 2
[Galaxy S III General] Sad56:
Thanks for the precisions ;)

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III General] Tenacious:
Yes they fix sds but the sources are not older from u6 they are older from AndreiLux sources that is becose he is cherry picking sources for his kernel from various samsung sources.

Get your facts straight.

Edit

MuertoKo already answer this Tapatalk is f****** with me.
[Galaxy S III General] mclaudio:
i had xxla bootloader and shyha kernel and this night it just dead !

yesterady night i felt the phone very very slow...maybe it was alread dying...

so this may be one of the symptoms...

also this means that xxla and shya do not correct the bug
[Galaxy S III General] MuertoKo:
As said the fix is kernel side, so using siyah you missed the fix sorry :( he will update it sure, but for now stock (Andrei said he'd be ready in an hour though)

Btw this adds that LLA bootloader is not more than crap, sorry :(

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] Tenacious:
edit

F again
[Galaxy S III General] dimi22:
So what upgrade contains the SDS fix?? and how did someone find this out?? what is the fix what does the fix?? :confused::confused:
[Galaxy S III General] mjb:
eMMC dev permissions makes no sense, as it's exynos-mem permissions, which isn't to do with the eMMC. He was referring to SDS as well, as the fix is likely to be kernel based, not bootloader.

There's no evidence that the fix will be from the bootloader (and why would it? the function of the bootloader is just to find the kernel on the device, and boot it). The fact that XXELLA had a new bootloader has just led to people making an assumption.

(And as you can see above, it's likely that the fix is indeed kernel based)

No, that's not what the article said - the problem there was with the secure erase functionality of the eMMC firmware. This is similar to the SGS2 superbrick problem.

About half? About the same as how 7 is half of 14? give him a break.

No - they used the same eMMC chip in some of the Note 2's. Can still be the eMMC firmware.

Seriously, stop with the conspiracy theories. The fault is likely to lie in the eMMC firmware, which is still software. Samsung are aware of it (they've apparently stated as much), and are apparently working on a fix. This takes time, so you're not going to see the fix in a few hours, more likely a few weeks.

And as you can see above, it appears that the fix has been identified in the kernel source release a few days ago.
[Galaxy S III General] MuertoKo:
Just flash perseus when he updates it withing an hour and fix done :)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] mjb:
Right - I probably will, but first waiting to see what he commits to his git repository!

And I was really referring to the timeline from when Samsung initially acknowledged the problem, not from when I posted.

Exciting times!
[Galaxy S III General] DEEBS808:
Yeah I'm just kidding. I'm loving android and all its possibilities :D
[Galaxy S III General] qavro:
Seriously,you can take a break. As long as you need it. Unless you are from Samsung you are not better than us. Meaning you suppose things. Even if you are from Samsung (covert ops) we are waiting an official statement. We are all good at guessing.
[Galaxy S III General] Entropy512:
No. Only connection with charging is:

Charging holds a wakelock, and when wakelocked, the device does background I/O it would normally not do.

No. New bootloader doesn't fix the issue. Where'd you read that? Not from any trusted competent source, that's for sure.

So all if the idiots who blindly flashed a bootloader despite being told it was almost surely not the fix, and despite the fact that flashing a bootloader is the most dangerous operation you can possibly do on your device, and despite wide documentation that new bootloaders prevent TriangleAway from operating properly, are screwed and it's their own damn fault for blindly ****ing around with their device without any research, common sense, or thinking.

A kernel doesn't have to CAUSE a problem - However, if hardware is faulty a kernel CAN work around faulty hardware.

Which is what is being done. Samsung is fixing this problem the same way they fixed the "random insertion of 32kb of zeros" problem on the Galaxy Nexus - on the fly patching of the eMMC firmware on boot.

The fix DOES appear in Update7 sources (see the link above to AndreiLux's post, I asked him to look at the MMC driver for changes since I couldn't do so until later tonight). As to which binary builds this is present in - We don't know. It should be identifiable by unpacking a kernel zImage and searching for VTU00M.

Anyone running ELLA/ELL4 bootloaders but another kernel is NOT SAFE.

Anyone running ELLA/ELL4 system firmware but a custom kernel is currently NOT SAFE

Anyone running any custom kernel is currently NOT SAFE

You MAY BE SAFE if you are running the original ELLA or ELL4 kernel.
[Galaxy S III General] mjb:
Occam's razor.
[Galaxy S III General] Nees3:
Why would you say that. Triangle Away works just as before, all official and no counter on my device after I updated. And if you use custom recovery, just rerun triangle away. I dont see ANY issue here that it doesn't make it work properly.
[Galaxy S III General] saragc:
I think my GS3 has also suffered from SDS. This afternoon, right after I sent a text message, I tried to turn the screen back on and it didn't respond. I took off the battery and put it back on, tried to charge it and nothing happens. I still had around 70% left on my battery... I have tried all the usual things (recovery mode and so on) and nothing works.

Unfortunately I have just returned from a long holiday abroad, in a remote place, and I didn't have the chance to backup my photos using wi-fi as I usually do. I have lots of photos taken with a SLR (all properly backed up) but I had some great ones taken with my GS3 in places where taking a SLR wasn't an option. Did anyone managed to save their photos after this happened? Or is the internal memory gone as well?

Thank you :)
[Galaxy S III General] mjb:
Just FYI to the thread, by my reading of the Update 7 sources, It's definitely the VTU00M/0xf1 chip that's affected.
[Galaxy S III General] Animor:
Do you have a diff between update 7 source and the previous source?

I would be happy to see the alleged fix code for the SDS.
[Galaxy S III General] T0xic4u:
Or maybe this is the only Chip that gets a fix? That doesn't mean, that other Chips aren't "infected"?

Taper di Tap with my S3 @176 days
[Galaxy S III General] mjb:
Yes, I'd say you could assume that. Although it's highly unlikely that other chips are affected.
[Galaxy S III General] Animor:
Do you have a link of update 7 source code?
[Galaxy S III General] Entropy512:
The full diff is MASSIVE. Andrei is working on a "chunked" diff with just MMC changes.

I'm working on diffing the whole thing myself but I was at work long enough I'll just wait for and review Andrei's chunked diff.

I need to look at the source, but from what I heard from Andrei, it sounds like it may only be patching VTU00M. That means no other chip is affected OR Samsung is not yet aware of what other chips may be affected.
[Galaxy S III General] InfX:
Hm, dd-ing it straight to the eMMC partition? Nice to know it works. I really don't envy someone dd-ing a wrong file(s) into it and only noticing after rebooting :)

Thanks for posting.
[Galaxy S III General] Animor:
Entropy512, thank you.

How can you explain users that had XXELLA stock rom, and still suffered from SDS? There are more than one report of it.
[Galaxy S III General] iridaki:
You are being unecessarilhy harsh here, especially considering that you are addressing people who are under the fear that their expensive phones will die on them suddenly. AdreiLux seems to be more skeptical regarding the possibility of the fix depending on the new bootloader as well. Calling names surely doesn't make you look smarter than the "idiots" who took a step -granted maybe rushed- towards a probable fix of a dreadful issue. And you may know much more than the average joe here, but you still have ZERO evidence that the new bootloader doesn't do anything at all that contributes to fixing the SDS, so you may have as well been nicer. Just my 2 cents.
[Galaxy S III General] silverwings2008:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=I9300
[Galaxy S III General] Animor:
Thanks! And there is the diff I was looking for from AndreiLux:

https://github.com/AndreiLux/Perseus-S3/commit/a03cc073ac1fc4c790635cf5d555156c5c4db9cc
[Galaxy S III General] iExitus:
http://xdaforums.com/showthread.php?p=36459955
[Galaxy S III General] JazzyJives:
Whitewash.....

Interesting article on Cnet (google "cnet s3 sudden death")....

..Samsung and some of the tech press seem to be trying to whitewash this issue and blame hackers / rooters on the problem, thus trying to make out that the fault does not lie with them....

read some of the comments at the bottom...
[Galaxy S III General] T0xic4u:
New Perseus Kernel is done, just flashed it.

Taper di Tap with my S3 @176 days
[Galaxy S III General] iridaki:
That's what the blogs/sites that confuse sudden death with the exynos-mem bug are doing, it is not Samsung's fault.
[Galaxy S III General] mjb:
I've just done this, and can confirm that the XXELLA kernel does include this string.
[Galaxy S III General] Animor:
How come you knew that SDS is related to eMMC (and specifically version VTU00M) before samsung released their code? What led to this assumption?
[Galaxy S III General] iridaki:
First custom kernel with the Sudden Death Fix and proper Exynos-mem Bug Fix incorporated released.
[Galaxy S III General] eitama:
Entropy / Andrie,

I sold my s3 a while back and now use a note 2 which seems to have the same chip. Do you guys have an idea if the update 7 sources were also released to the note 2? Should I drive to flash a note 2 kernel with the workaround built into it?

There is no info on this subject in the note 2 forums even though I saw some posts of people complaining about sds on note 2.

Thanks for all your hard work.
[Galaxy S III General] AndreiLux:
Do you have the same chip revision ? Type VTU00M and revision 0xF1 ? I'll be updating the Note 2 kernel as well anyway.
[Galaxy S III General] eitama:
Yes I do! 16gb with exact same model and fw.

http://db.tt/aZgdY4xc
[Galaxy S III General] InfX:
Just took a look at the diffs and i have to admit, i don't nearly get what this does. What are those "movi commands"? Where can one find a data-sheet to decode the magics? :(

BTW, just took the kernel image from the WanamLite v5.3 CWM zip (that's what i am currently running), un-gz-ed it, and actually found the "movi operation is failed" error string in there. Good for me, i guess ;)

AndreiLux, thanks A LOT for your research.
[Galaxy S III General] \m/aximuS:
Stock XXELLA

Stock XXELLA kernel include SDS fix ?
[Galaxy S III General] InfX:
WanamLite v5.3 seems to include it, it is a modified stock, so i guess it does.
[Galaxy S III General] mjb:
I'd hazard a guess that it does - but I'd certainly like someone like Entropy to weigh in.
[Galaxy S III General] dossy33:
yeah tried that they refused to help!!!!!!! i pointed out that they knew it wasnt a HK purchased phone but wouldnt tell me what region it was from....new definition of useless!!
[Galaxy S III General] smsmasters:
Is there a way to check if I already have any bad blocks on my eMMC?
[Galaxy S III General] Entropy512:
I have yet to see any such reports... The one report I've seen of an XXELLA failure was XXELLA system + Siyah.

I have all of the evidence I need - I now have kernel source for a complete eMMC firmware patch. The fix is in the kernel, not in the bootloader. It's being patched in the EXACT same way as the GNex 32kb-of-zeros fix patch, which had zero bootloader involvement.

The fact is that flashing a bootloader is a fundamentally dangerous operation, and flashing a bootloader with known regressions in functionality is 100% reckless and stupid.

The fact is that Samsung has NEVER fixed a problem like this in the bootloader before. There was ZERO evidence pointing there. There was plenty of evidence (the GNex VYL00M/KYL00M/MAG4FA 0x25 patch) pointing to the fix being in the kernel when it came out.

All of the symptoms and behavior pointed this way.

1) Some devices were exhibiting "Superbrick-ish" behavior where certain eMMC regions were working and others were inaccessible

2) It was ONLY happening on 16GB devices - this is the most obvious piece of evidence. If it weren't the eMMC, it would have been seen on 32/64GB devices

3) It would be the third time in one year Samsung has ****ed up their wear leveller, their quality control is clearly crap in this regard.
[Galaxy S III General] Allesa:
This actually made sense. I actually had sudden slow downs when using launcher8, framerates dropped to around 5-10 fps after updating to ELLA based anonorom using siyah or prev perseus version. Before updating it was fine. From a non-dev pov I thought it was a rom thing. So i flashed Ultimarom inadvertently using the default ELLA stock kernel. Performance on launcher8 was back instantly.

Almost sold my gs3 and whoring myself to wp8 L920. Hopefully we all dodge a bullet here.
[Galaxy S III General] jakmeister:
OK, I'm one of those "idiots" who flashed the new bootloader (you can blame my fear and Noob-ness for that). So what should I do now? Did I inadvertily do more harm to my phone if I keep it (I do have a habit of turn my phone off during the night and restart it the next morning)? And is there any way to reverse the process or reload the old bootloader via Odin or CWM?
[Galaxy S III General] JH323:
small update from HK...finally got my f motherboard replaced after visiting the repair center 3 times in 9 days...things are running smoothly so far but HK still hasn't got the FW update...still on LL1, 4.1.1

anyways overheard a couple of customers while in the repair center that their note 2 have started to develop similar issues to mine (semi-death, keep freezing and need to take battery out, etc to boot)

would be interested if this would become a bigger issue later...

anyways still disappointed by Samsung over this incident :(
[Galaxy S III General] bry4ntt:
Looking at Perseus kernel v31 changelog: "Kernels >v31 and beyond stock LLA are now the only truly protected ones."

Is it confirmed that LLA stock kernel has the fix?
[Galaxy S III General] Rob2222:
Yes, it looks good.

http://xdaforums.com/showthread.php?p=36465270#post36465270

I also uncompressed the zimage from XXELLA and found the string VTU00M, which is a good indicator that can support the assumption that XXELLA already has the fix implemented.

BR

Rob
[Galaxy S III General] desynch-:
How easy was it to get a warranty from them? I have an HK one that died this morning but I'm in the USA.
[Galaxy S III General] cristian274:
so it means that we just need to have cleanly XELLA stock rom and we can avoid SDS?
[Galaxy S III General] drraptor:
Thanks to all the developers who worked on this issue, we finally have identified and fixed this SDS issue.:)

But why is Samsung hadn't issued LLA update for regions other than Europe ?

I bought it from middle east, the latest is 4.1.2 without the new kernel. :banghead: and I can't ( unavoidable reasons) flash new kernel :mad:

---------- Post added at 08:40 AM ---------- Previous post was at 08:37 AM ----------

You just need to flash the XELLA kernel or one based on it
[Galaxy S III General] mardex80:
Can you check if LL4 have this string too?

Enviado desde mi S3 con Tapatalk.
[Galaxy S III General] naathaanb96:
Trying to register my phone for warranty and as I bought it off someone who got it on a telstra contract I'm not sure of the purchase date. Is there a way to find this out?
[Galaxy S III General] Kjc99:
I am running Omega V36 with XXELLA kernel and new bootloader I should be okay for now right? Did I read something about recovery on the last couple pages? Does it matter which recovery we are using and also I know this bootloader is new and I flashed it hoping for a quick fix but other than the (!) it won't hurt my S3 right

Galaxy S3

Omega Rom V36
[Galaxy S III General] Entropy512:
We don't know the exact conditions under which the wear leveller is failing - so you should use a recovery that is patched too.

http://review.cyanogenmod.org/#/c/29932/ - patch has been submitted to CM gerrit. If it even boots on my n8013 I'm merging it.
[Galaxy S III General] Kjc99:
I am using cwm touch 6.0.1.2

Galaxy S3

Omega Rom V36
[Galaxy S III General] zoot1:
Older recoveries are not patched yet..new recoveries will have to be release which include this patch..
[Galaxy S III General] sak500:
Glad it worked out. Can you post the revision and other Hw info of your mainboard?

---------- Post added at 05:10 AM ---------- Previous post was at 05:08 AM ----------

Install emmc brickbug from google playstore. IT will test it.
[Galaxy S III General] AndreiLux:
The patch additionally checks that the firmware date is 2012/04/13 and only applies the commands then.

So you need type: VTU00M revision: 0xf1 and internal firmware date of 2012/04/13 for the bug to have an effect. The date which eMMC brickbug checker reads is the production date as it seems.

So there might be phones with VTU00M/0xf1 out there which are not affected, I don't know if that makes sense in regard that if the revision would even be the same then.
[Galaxy S III General] skivnit:
Just to confirm., the Perseus kernel contains the fix but the Ella stock kernel doesn't? Or are we safe on latest stock kernel
[Galaxy S III General] zoot1:
Is there a way to check this date??As the firmware revision date may or may not be the same..
[Galaxy S III General] kofiaa:
Run the eMMC check app, it's in the play store.
[Galaxy S III General] Angeluz01:
am i safe?

Thz for reply^^;

ics 4.04 Omega 9.1 XXBLG1
[Galaxy S III General] perry04:
Where can i get a patched recovery dude? I think only Kernel dont solve the Problem or misunderstand?

-Galaxy s3 with tapatalk-
[Galaxy S III General] AndreiLux:
No, the date shown in the eMMC app is the production date, the internal firmware date is something else and not possible to read out through normal methods.
[Galaxy S III General] kofiaa:
Thanks. It's better to just flash your kernel anyway, better safe than sorry.

Thank you for giving us a fix :thumbup::)
[Galaxy S III General] bala_gamer:
Kernel solves the problem with your daily usage, patched recovery is needed for safely flashing roms (if you flash roms)

《posted from samsung rom》
[Galaxy S III General] mjb:
No, it looks like ELLA has the fix. It certainly contains the strings used in the patch applied to Perseus.
[Galaxy S III General] sak500:
Anyone losing their photos or other files on ext SD ? My replaced phone has started doing it again. The old one started losing my files / pics stored on ext SD and finally killed my 32GB SD card and i had to get it replaced under warranty from sandisk.

Now my fixed (new MB) phone has lost my pics from last few days which are showing in dropbox only. WTF is going on with S3.

Just in case gonna backup everything and also save it on my pc.
[Galaxy S III General] linezero:
Mine says:

Type: VTU00M

Date: 08/2012

CID:150*****..........

FwRev: 0xf1

brick bug?

No. sane chip.

does this mean im safe?