yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] Product F(RED):
I agree completely, especially since they allegedly replaced either the entire board or whatever part was at fault, and I'm sitting here stuck with the same issue a second time. It would suck to pay to ship it to Germany again for a fix, with the price and wait time, but I'd feel much more comfortable knowing they recognize and are addressing these issues. In other words, I refuse to pay to get it fixed again, just to have it break down another 3 months later. It happened 3 months in the first time and 3 months in the second time (my phone is barely 6 months old if you don't count whatever they fixed!). Someone else said they also had the issue 3 months in. This is BS.

And by the way, if you're on custom firmware don't update to the latest update that allegedly fixes the Sudden Death issue; it includes a new bootloader that increments just for having a custom recovery (in other words it doesn't just go up for flashing things, but also for actually having things on your phone). I'd wait to see if it's a guaranteed fix.
[Galaxy S III General] Entropy512:
If you have VTU00M fwrev 0xf1 flash, you are probably at risk. I9305 is too new to tell

No. In fact, there's nothing that indicates there is a bug in the bootloader/kernel/system firmware yet. Given the behavior of the problem and Samsung's past history, it's likely a bug in internal eMMC firmware (which can, at best be field-patched if it only involves a few bytes of microcode - major changes are not possible in the field.) This upcoming update likely contains a workaround for that eMMC bug.

Look at the Superbrick bug - There was no underlying "bug" in any of Samsung's firmwares, except that they didn't block commands that would trigger a known bug in the underlying flash memory. Now, in any hardware without that bug, issuing secure erase commands is fine. The workaround for the bug is simple: Don't send secure erase commands to the damn chip.

Unknown. Right now any device with VTU00M flash is at risk - but how high the risk is we don't know.

No one knows yet. If it's done in the kernel, we'll know EXACTLY what/how they fixed it and how to apply the fix to custom firmwares. If it's the bootloader, we won't know unless they explicitly states that they changed the bootloader to fix it. If it's in /system (HIGHLY unlikely) we might see something.

Most likely place they'll fix this is the kernel with a variant of the Sumrall patch from last spring, OR an alteration to the MMC code in order to avoid doing something (we don't know what) that the chip doesn't like (this would be similar to how Superbrick is worked around). So far, every time Samsung has ever fixed or worked around an eMMC bug/defect, it's been in the kernel and not the bootloader. So everyone flashing this new bootloader is just making it more likely they'll be denied warranty support if their device dies.

Bull****. You have ZERO evidence to substantiate this claim.

And why do you think it's the bootloader? There's no evidence to say WHERE the fix will be applied because there isn't even any information about HOW the failures are occurring. Right now, I'd say it's most likely going to be a kernel fix.

If it's a wear leveller bug, there's a possibility fixed wear leveller firmware might "repair" damage to the internal data structures.

Search before posting. I posted an example of how this has been done to Samsung eMMC chips in the past only 1-2 days ago. (Search this thread for Sumrall...)

Minor eMMC microcode updates can be done at runtime. It's fairly safe since it apparently patches the firmware after it has loaded into volatile memory (and hence a power cycle removes the patch if it's misapplied). This is what the Galaxy Nexus patch for VYL00M/KYL00M/MAG4FA fwrev 0x25 did.

Major eMMC microcode updates can't be done so easily, which is why the underlying Superbrick flaw was never fixed.

Don't make definitive claims you have no evidence to support.
[Galaxy S III General] jody2k:
Is there a way to check that you have a VTU00M flash?
[Galaxy S III General] Product F(RED):
Great. My S3 hasn't died yet, but in addition to not being able to make calls with it right now, I can expect it to die since it has the exact eMMC chip that was mentioned to be at risk...

Search the Play Store for "eMMC" and download the app that comes up. Ignore the part that says you're not at risk because it only identifies the chip in the S2.
[Galaxy S III General] jody2k:
Same here..im having exact the same chip ;/ starting to worry...but im not having any strange symptoms at the moment. Whatever that means ofcourse
[Galaxy S III General] Motogp1:
Excuse me who the f*** do you think your talking too !!!!

Sent from either Nexus 4 or SGS3 using XDA premium.
[Galaxy S III General] LenAsh:
The sheep and speculators...
[Galaxy S III General] xaueious:
Was waiting for a sensible mind to make a reply like this. Thanks.
[Galaxy S III General] vadonka:
bootloader is not even close to other custom things like kernel, cwm, etc.

bootloader is made by the samsung, so i hardly believe samsung will deny the warrantly because of the phone have the XXELLA bootloader.

if the flash counter is zero and the system/binary status is official then you have no problem.

but i agree about the new bootloader probably doesn't fix the sudden death. this is not confirmed by the samsung yet.

im currently using the XXELLA bootloader/modem/rom. flash counter is zero and everything is official. triangle away app installed running at every boot, so no matter that the new bootloader detect the insecure kernel the app will reset the counter after every reboot, so if my phone will die unexpectedly, but the bootloader remain working, the flash counter will be zero, and everything is official. if the samsung deny the warranlty in that case i will kick some ass badly :)
[Galaxy S III General] liamR:
@vadonka

How did you manage to get TA to run every boot ?
[Galaxy S III General] vadonka:
i just enabled the auto reset at boot option.
[Galaxy S III General] chevli:
Guys, if your phone dies, don't worry, just get it repaired under warranty. No need to prevent it from happening.

If it lives then that's fantastic but I would personally prefer it to die before the warranty rather than after.

Either way keep backing up your phone especially any sentimental stuff on your internal storage.

Just so you know, my phone died, it was rooted and custom rom and they still repaired without question and upgraded my phone to 32gb. I understand the inconvenience but I am sure you can temporarily get your hands on another handset whilst in repair.
[Galaxy S III General] Product F(RED):
The reason I'm complaining is because I live in the US and my phone is originally from the UK, and the seller (through Amazon) is in Germany. Samsung refuses to repair any phone from the UK/Europe unless it's being shipped from a UK/Euro address. I had to ship to the seller to ship to Samsung, and that took $80 and a month to get back. Now it seems I have to do it again.

Before people complain and ask me why I bought the i9300, it's because it's the *real* Galaxy S3, not the crappy US S3 with the Snapdragon S4 processor. I also bought this before the S3 came out on any US carrier, and on top of it all I'm on prepaid, so I had no incentive to buy a US S3. This is not the way it should be handled. HTC fixed my friend's international One X despite the fact that he's from the US and the phone is from the UK.

I'm not going to update to the latest bootloader from Samsung, because I think what they're planning to do (and call me paranoid) is to increment everyone's flash counter with the new bootloader (it increments just for HAVING a custom recovery or modified ROM on your phone), and then admitting to the issue to reduce the number of phones they have to fix. In other words, they'll probably refuse to fix people's phones for being rooted/modified. Whether or not this turns out to be true, I am NOT happy with the way Samsung is handling this.
[Galaxy S III General] emelsk:
While it may sound like a good conspiracy theory, the red exclamation point is not something just introduced with this update. There were reported instances of it way before ELLA became available.
[Galaxy S III General] Marilize-Legajuana:
Yeah good question, im interesting in that too. anyone know?

And please, what is bootloader/kernel/firmware? What is mean CM10? Is update 10.1 needed?

Yesterday im updated my android from 4.1.1 to 4.1.2 directly from my GS3 via Software Update.

It was: I9300XXDLID (kernel 3.0.31-368423, SEP-78#1, October 19, 2012)

And now: I9300XXELL4 (kernel 3.0.31-566833, SEP-64#1, December 10, 2012)
[Galaxy S III General] Product F(RED):
As I said before, search "eMMC" in the Play Store and it'll tell you. It's for the S2 but it works.
[Galaxy S III General] _delice_doluca_:
I believe by updating the bootloader Samsung has decided to cut the budgets of the repearings. They now are trying to mark devices with customisations or root permanentely so they can easily refuse to repair them when they are broken instead of trying to solve the problem. I know that many users do not even root their phones but still there are enough people to think them they can save up from some extra motherboard money.

This is why they will never tell people if the FW has a fix or not. Because if they tell the truth and say it does not "fix" the "problem" then everyone will know 1) Samsung tried to mark them 2) there is a "problem"

Definetely the last Samsung product.
[Galaxy S III General] Product F(RED):
That's exactly what I'm saying. They'll probably admit to the a problem eventually, but only after this update has gone out. And you'll probably get your phone back updated if it dies, so honestly it's better to let it die than update. It's a bit of a conspiracy theory, but think about it. We're a big community; they can seriously reduce costs by denying a chunk of S3 owners repairs because their devices are rooted.
[Galaxy S III General] Obagleyfreer:
How would Samsung know if you'd rooted or were running a custom ROM?

All you need to do is flash stock firmware and kernel and reset flash counter with Triangle Away app, just like people have been doing in the past.

The red mark only comes back if you have a custom kernel on your device.
[Galaxy S III General] Product F(RED):
The new bootloader actively checks if you have a custom recovery or kernel on your device on every boot. The old bootloader, before this update, would only go up if you flashed something custom using ODIN. This one must check signatures or something to be able to do what it does.
[Galaxy S III General] zyclops1:
After reading this thread I put my s3 back

To the box and remove battery also,Samsung news says fix on the way,waiting for it.

I dont wanna loos my s3.

:(:(:(:(:(
[Galaxy S III General] philicom:
But surely if with the new bootloader we still suffer sudden deaths then Samsung won't even know if it's rooted or not?

Besides if it does fix the sudden death issue (doubtful imo) then you win either way. As they say prevention better than cure.

Personally I think people who still have their warranty and are lucky enough to be able to send it off for repair, cost effectively of course, should just hold fire and not rush into anything.

You may even get a 32gb :D
[Galaxy S III General] Product F(RED):
As I mentioned before, I have a separate issue that is also hardware failure but not sudden death. If your S3 dies, it gets replaced with an updated one. If that happens and something else fails (like what happened to me), then you can kiss your warranty and repair goodbye if you're rooted.
[Galaxy S III General] jshashwat93:
I used to get the red exclamation mark on my phone from the very first time I rooted and flashed custom Roms or kernel.

I haven't flashed this new boot loader but for those trying to get rid of it follow these steps:

- Use Triangle Away to reset the flash counters, and pull the battery immediately after rebooting starts

- Boot into recovery and perform a wipe, and pull the battery immediately after rebooting starts

- Go to SamMobile and get the stock firmware for your region

- Flash that stock firmware on your device

- Let Android boot, go through device setup (without doing any logins) until Android is fully usable again

- Reboot

- Wait at least 10 minutes

- Check Settings->About device->Status and make sure Device status is not "Modified"

- Perform another factory reset

- Boot into download mode and make sure the flash counter and system status are all set to official

These steps are given by chainfire and they helped me get rid of it. But main thing is to make sure not let your phone boot after resetting counter and wherever it says to pull battery do it as said and wait for at least 15 seconds before reinserting the battery. I had to do this whole thing twice to get it correctly. So do try this and give your feedback if it works with this new boot loader.
[Galaxy S III General] RkoViper81:
So I have had my S3 for like maybe a week if that & then all of a sudden after i rooted the device was running cyanogenmod 10 when it got stuck at the spinning cyanogenmod logo on bootup & now it won't power up light up or anything. All I know is I am P*ssed never had any phone hardware issues with apple in the 5 years I was an apple user

I was running firmware 4.1.1 I believe

From Canada

Rom CM10 thats all I know sorry am new to android from an iphone 5
[Galaxy S III General] Yellow_Racing:
UPDATE: I dropped my phone off at Alltech in Adelaide at lunchtime yesterday and got an sms at 8:30am today saying the phone was ready to collect.. Great work Alltech.

Fault: No Power

Service: Short Circuit, replace main PBA, IMEI Write, S/W I9100TDVLP3
[Galaxy S III General] sak500:
What's your new phone MB HW rev ? 1.15? EDIT: Sorry meant 1.5, mines the same.
[Galaxy S III General] varun3gr8:
what is GPU UI rendering
[Galaxy S III General] vadonka:
guys, XXELLA bootloader coming with the latest official samsung firmware!

so just say when sombody asking: "i just installed the latest update with kies, nothing else"

this is an official update, nothing custom. dont say that that you install this because of the sudden death or anything else.

samsung will not deny warrantly because you install a new official update to your phone. this is nonsense!

just play stupid :)

it will work
[Galaxy S III General] Yellow_Racing:
Phone is charging atm,

AP: I9003TDUDLK2

CP: I9300TDUDLJ2

CSC: I9300TTELDK2

RF CAL: 2012.11.30

HW REV: MP 1.500

Cheers Robski
[Galaxy S III General] Entropy512:
Search the thread, it's been covered many times.

An irresponsible idiot who falsely led users to believe they were safe despite ABSOLUTELY ZERO evidence to indicate this firmware release had any sort of fix... Especially the fact that it has a build date prior to Samsung saying a "fix was coming soon".
[Galaxy S III General] Droidphilev:
Hi,

I was so *stupid* to flash this new bootloader. :( Flashing the old bootloader from ICS is not possible anymore now (with pc odin). Is there anyone trying to fix this?

I truly regret all the speculations that this new bootloader should fix SDS
[Galaxy S III General] naathaanb96:
My phone screen takes ages to respond when woken unless on a custom kernel with swipe to wake. Is it on its way out?
[Galaxy S III General] Yellow_Racing:
Possibly, I had no lag at all. All I thought was strange was my car would not connect to bluetooth automatically as it had done without fail for 6 months.
[Galaxy S III General] r2001uk:
A quick question to anyone in the UK who sent their phone off for repair and have got it back:

Were you updated on the progress, or contacted at all? Did the phone just turn up one day? I've not heard anything and I sent mine in before christmas. I know the holiday period was likely to cause delays due to all the bank holidays, but I was wondering if I should expect any form of contact or just wait patiently for a delivery.
[Galaxy S III General] jay_m3:
yes of course you can, even you can give it a try with the JTAG
[Galaxy S III General] zadusimple:
Can i use the CheckROM_V4_LG8.tar to flash the older bootloader?
[Galaxy S III General] vadonka:
No need to revert back the old bootloader. When the samsung will release the official fix for the sudden death probably that release will contain a bootloader too (a simple kernel update cant fix the microcode, this is false information)

Just wait a little bit.
[Galaxy S III General] dimi22:
Guys i hear that the new bootloader detects root??

I just checked ota in the morning and the phone said not available system is modified. Yesterday it didnt say that... is samsung pushing bootloader upload secretly?
[Galaxy S III General] 75markus:
+1

guys, are you really scared because of that small ! when booting up ?? no need to worry, just leave it alone, it won´t harm you :p
[Galaxy S III General] Droidphilev:
Hi again,

Well maybe i should forget the ICS bootloader i used to use untill yesterday but on the other hand: 'if it works, don't fix it' if you know what i mean. I have the old bootloader in a tar so if anyone comes up with a solution i guess i will reflash it. :)
[Galaxy S III General] dimi22:
After removing root it says no update available.....

How can i check if my bootloader updated
[Galaxy S III General] vadonka:
Yes the new bootloader detect custom (insecure) kernel and custom recovery and set the flash counter to 1 after every reboot.

The only workarond that use the Triangle Away app with auto reset at boot option, so the flash counter resetted after every reboot (or you need to manual reset the flash counter after every reboot)
[Galaxy S III General] -A-P-M-:
Do you have international SGS3 (GT-i9300) ?
[Galaxy S III General] Sango2:
Well for me, I sent my phone to Anovo (Samsung's service center in the UK), since Samsung UK instructed me to contact them. I was in weekly contact with them to see if they received it.

They finally gotten my phone and repaired it yesterday and will be sending it back to me in the US shortly.

Address Info of Samsung's UK Service Center.

A NOVO LTD

A Novo Communication House Samsung

Vulcan Road North

Norwich

NR6 6AQ

United Kingdom

Telephone: +44 (0)1603 269 900

Fax: +44 (0)1603 269 911
[Galaxy S III General] chikiball:
Model GT-19300 international, bought from Singtel Singapore on end of may 2012.

Stock ROM updated to latest release.

Chronology: Charge my phone until around 85%, then took the cable out, leave it on the desk for about 5 minutes, screen off (after 1 minute), see that there is a notification blue led blinking, press home button to wake up - not waking up, press power button to wake up - not waking up LED still flashing, remove the battery, put battery back, press power button - not powering, try to charge - cannot charge. Die, bring to samsung repair center at Singapura Plaza, one day later replaced the Main board and LCD (i think it means the display). got it back (loosing all my apps data and game save, sms, chat history etc)
[Galaxy S III General] robogo1982:
It's not the ! they worry about, but possible future warranty claims.
[Galaxy S III General] Nees3:
This information is FALSE. Rebooted several times. Everything is still official in Download Mode! (stock kernel + custom recovery)
[Galaxy S III General] 75markus:
I know, but if your phone really suddenly dies, who should find out ? They replace the hardware and that's it.

sent from 127.0.0.1
[Galaxy S III General] siavash_Skh:
Dose triangle away work on ELLA ?

So. When we on a rooted ELLA Can we reset the counter with triangle away then flash the official one to avoid setting flash counter to 1 ?
[Galaxy S III General] qavro:
After carefully reading this entire topic twice, i want to thank to Entropy512.

My personal opinia on this (not that will matter in any way) is that nobody knows exactly what and when happens with the damn phone. Samsung included.

p.s. never had any problem with mine, it works smooth and fast with good battery time (darky8.3/syiah)

and i had it rooted and flashed on the second day i bought it. All i do is that i never use the wall charger and i never let my phone charging over night (i also think this is placebo because nobody can say for sure it has anything to do with charging either) but this is because i don't like the battery being charged fast. But i do this for all my batteries (RC/airsoft/etc)
[Galaxy S III General] dimi22:
Thanks but this was not my question
[Galaxy S III General] vadonka:
Then your bootloader is not the XXELLA but the older one.

---------- Post added at 10:49 AM ---------- Previous post was at 10:44 AM ----------

Yes

Flash the ELLA bootloader, use the triangle away app, then power off, then start with bootloader mode, you will see everything is official and flash counter will be zero. If you flash any official firmware your system status remain official, and the red exclamation mark will be dissapeared.

The exclamation mark only appear when you have insecure/custom kernel (for rooting) and/or custom recovery. In that case the bootloader detect this and auto set the flash counter to 1 after the bootup. Thats why you need to use the triangle away app.
[Galaxy S III General] nhariamine:
How to flash just the bootloader on a custom rom like Omega JB 4.1.2? and do i need to flash the whole rom to get rid of the Sudden Death?
[Galaxy S III General] LemonPlusTea:
I already had my phone die on me once. I just checked the emmc chip with the software, and I still have the same type of emmc chip, VTU00M.

If the phone dies again and this time its out of my warranty period I'm going to be so pissed.
[Galaxy S III General] PjotrFias:
It's still not confirmed if this bootloader/ROM actually fixes anything. The guys that actually know what they are talking about say no ATM.
[Galaxy S III General] boomboomer:
Go to page 19 of the XELLA 'fixes sudden death' thread in general forum, download the bootloader zip and flash using Odin on your PC - it won't affect the ROM you have installed.

No-one knows if this BL fixes sudden death btw, it's all conjecture at the moment.
[Galaxy S III General] mkrajaci:
On sammobile said that XXELLA firmware solve problem. Is it true?
[Galaxy S III General] nil.shunya:
Can somebody plz upload the oldbootloader in tar (jb one):)
[Galaxy S III General] vadonka:
you can find a bootloader only odin tar in here: http://niekske.myftp.biz:81/ajaxplorer/index.php#1

but it is not confirmed that this fix anything!

---------- Post added at 11:14 AM ---------- Previous post was at 11:13 AM ----------

who said that? :)

i only see speculations :rolleyes:
[Galaxy S III General] nhariamine:
look at sammobile update for this build, it indeed fixes the sudden death issue confiremed
[Galaxy S III General] UncleBeer:
Mine too. :(

+1
[Galaxy S III General] turt:
I agree with you, same for me on ELLA with new bootloader.

I have flashed CF-root 6.4 so I'm rooted and I have custom recovery, but it's still Official in Download mode.
[Galaxy S III General] _Sasan_:
http://www.sammobile.com/2013/01/03...ynos-security-exploit-sudden-death-issue-too/

Faryaab updated its post there:

"UPDATE: Our sources confirm that Samsung has fixed the sudden death issue with the latest Galaxy S III Software Update."
[Galaxy S III General] vadonka:
read this: http://xdaforums.com/showpost.php?p=36220532&postcount=2200

---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------

this is new information. if this is true one more reason to update to the XXELLA
[Galaxy S III General] ramb:
But for my case is Samsung wants to void my warranty and ask me to pay for the cost of replacing the motherboard due to my phone is rooted.
[Galaxy S III General] zyclops1:
"good guy apple is replacing samsung’s handsets. my s3 died 2 days ago and now i will get iphone 5. sounds fair to me."

i saw this comment in this pagehttp://nvonews.com/2012/12/26/samsung-galaxy-s3-sudden-death-issue-hogs-limelight-main-features/

is this true?????/ :silly: :silly: :silly: :silly: :silly: :silly: