yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] Rob2222:
When you already had 2 sudden deaths, are you doing something, what other S3 users maybe doesn't do? Maybe some flash-intensive tasks? How full was your internal memory in average in that time you used it? More empty or more full?

Maybe we could find some use types that make sudden death more propably.

Which not means, that your SD is your fault. It should not happen.

BR Rob
[Galaxy S III General] vibsOveebs:
Answer

No. You can't move it.. Do you live in US and your S3 broke having a i9300?
[Galaxy S III General] Rob2222:
Made my day. :laugh: :good:

BR

Rob
[Galaxy S III General] krivinash:
All we do is just a wild guessing.

I do everything to prevent sds.

I hope that samsung will find the solution soon.
[Galaxy S III General] DragonriderX:
Had a close call

I had a very close call with my Galaxy S3 this morning (around 12.30 ish AM), where my phone spontaneously rebooted then got stuck at the Bootloader Splash Screen. Or the Screen that says "Samsung Galaxy SIII GT-I9300T" for 3 and a half minutes before getting into a boot loop. I quickly took out the battery and waited about half an hour then turned it back on, with the phone sorta working but the Internal SD card completely damaged (not even showing up in /mnt folder and not mountable in terminal) and some apps located in /system/app being 0 KB in size

My phone was not in the charger when it happened.

More details about my phone below.

Basic Info

Model: GT-I9300T

Made in: Vietnam

Battery Made in: Vietnam

Firmware Details

Android version: 4.1.1

Baseband version: I9300TDUDLJ2

Kernel version: 3.0.31-527841 dpi@DELL179 #1 SMP PREEMPT Thu Nov 29 13:03:46 KST 2012

Build number: JRO03C.I9300TDUDLK3

AP: I9300TDUDLK3

CP: I9300TDUDLJ2

CSC: I9300TVAUDLK3

As you can see my phone is practically stock standard at the moment, normally i'd be using Siyah but when i updated to 4.1.1 I stuck with the default for the time being.

Details in *#12580*369#

Hardware Revision

MP 1.100

I couldn't take a screenshot of the eMMC Check Application since it tries to save in /mnt/sdcard, and obviously it's not working so it fails but the details from it are below

Phone Model: Samsung m0du

eMMC Chip Type: VTU00M

eMMC Chip Date: 04/2012

eMMC CID: 15010056545530304df1aeed1c955ffb

FwRev: 0xf1

Brick Bug?: No. Sane Chip.
[Galaxy S III General] elencross:
Great, woke up today and my phone was dead, second ****ing time. Both times, left over night to charge, has the notification light blinking to alert me of a message, but phone would not turn on/unlock. The last time Samsung changed my motherboard to fix it, going down to get it fixed again, very very disappointed.
[Galaxy S III General] offgrey:
Probably because the phone has only been out for that long????

By updating to XXELLA or later firmware updates. :D
[Galaxy S III General] clin81:
What is your mobo revision?
[Galaxy S III General] elencross:
I did not check.

Just to provide more info:

1st time:

ROM: Omega (forgot version, but sammybased rom)

Version: Jellybean 4.1.1

2nd:

ROM: Paranoid Android 2.54 (AOSP)

Version Jellybean 4.1.2
[Galaxy S III General] masterex567:
Seen almost all cases to do with notification led.

I've kept it unchecked by default.

Removed the ! mark on new bootloader. Using custom recovery and custom Rom.
[Galaxy S III General] dossy33:
damn Samsung

My GS3 suddenly died 2 days after Xmas. i took it to the Samsung repair centre in Hong Kong where i live and they told me it wasnt a HK purchased phone so they wouldnt repair it under warranty but would replace the motherboard for ($280USD). The phone is only 6 months old and i bought it from ebay as an early adopter, and the seller isnt responding to my email. I emailed samsung customer service and asked them how can i determine where my phone is from so i can email the samsung service centre in wherever, and they told me to contact the seller.

I replied to them that "THE DAMN PHONE IS MADE IN THE SAME EFFING COUNTRY SO WHY ALL THIS STATIC ABOUT NOT FIXING IT!!". i even paid extra for the samsung case, i`ve looked after this phone its not my fault it failed. looks like Ive wasted my money. i think i`m done with Samsung.
[Galaxy S III General] offgrey:
What is the firmware code of your phone? Check using the dialer code *#1234#. That's one way to figure out where your phone was made, unless you've flashed other firmwares already, in which case, I don't really know how to figure out where your phone was meant to be sold in the first place.
[Galaxy S III General] LivingPerson:
What did you do to remove the red exclamation, bro? What is the Download Mode screen telling?
[Galaxy S III General] dossy33:
I cant turn the phone on.....plus yes, I`ve flashed other firmware....i have the original box, i read somewhere that you can tell from the letters on the sticker, but mine had three stickers with ABC on them.....
[Galaxy S III General] offgrey:
Supposedly you can call Samsung there and ask them to check where your phone is from based on the IMEI of your phone.
[Galaxy S III General] ymy3890:
Sudden Death for I9300N and I9300T

Hi there is 9300N and 9300T affected by sudden death problem?Thanks in advance..
[Galaxy S III General] Animor:
Hi,

Just read the latest 15 pages, and I'm a bit confused: how many people had sudden death after flashing ELLA rom+bootloader?

I saw only one on this thread, so why are people so certain that the latest rom doesn't prevent/fix SDS? Are there more than one evidence I missed?

Thanks.
[Galaxy S III General] kw5655:
http://xdaforums.com/showthread.php?t=2065626

Scroll down to the post by Twisted. I came to the forums tonight looking for wifi issues with the note 2 and found both of these threads. I'm freaked. I just bought the Note II 12/24/12 in US from Sprint. This is the first that I've heard of this issue. I do have the extra insurance that Sprint offers, but I wouldn't want to end up 6 months down the road with the same problem.

LOL, I'm keeping the phone anyway. I love this phone. I'll certainly report back though if anything goes amiss.
[Galaxy S III General] sak500:
You can try and check the serial number or imei on the phone itself and email samsung to trace it for which region.
[Galaxy S III General] offgrey:
For one thing it was only recently that Samsung even announced that they knew about the problem. The build date of the XXELLA firmware is December 2012. Samsung only confirmed the SDS problem January. And I don't even really know about that confirmation because it was just from one country specific branch of Samsung. For another, they didn't officially announce that XXELLA IS the fix. You'd think they'd announce that or something because I honestly think that if this phone really is just a ticking time bomb, they'd make a whole lot of news about it because of possible PR backlash, not to mention the cost of replacing motherboards and paying their repair personnel.

It just logically does not make sense. I would like to be proven wrong here, as I've already installed XXELLA on my phone, but the odds are against this particular assumption (that XXELLA fixes SDS).
[Galaxy S III General] t0n0n:
Too many websites reporting that Exynos Abuse = Sudden Death, read carefully, since you can lose your warranty if Samsung finds out that you are not using full stock sw/fw. And we have no confirmation from Samsung that the new bootloader can solve the SDs.

_________________

There's any way to look for electrical spikes? I'm not a specialist, but it seems to be related to charging.

I've seen other phones who had problems with ROMs(stock, not custom) who were tuned for a region or a factory. Maybe Samsung screwed up while packaging everything, and that's why they can solve it via SW/FW. I know they already updated S3 a lot of times, but maybe nobody has seen that or wanted to see or looked for.

Or they are waiting for the mystical day they will release Exynos sources, so our developers can do their job. You know, replacement parts are cheap, at least cheaper than admitting you screwed up.

Sorry if anything is unrelated, I just want to clarify/find out.
[Galaxy S III General] Kjc99:
Is there anyway to reset binary count with new bootloader or can I flash back to stock from Omega Rom V36 will this unroot I am very worried about my moms S3 and we are both rooted with new bootloader

Galaxy S3

Omega Rom V36
[Galaxy S III General] t0n0n:
You can flash a full .tar using Odin, it will full wipe the phone, even the internal memory and as far I know, reset your counters.

Look at the forums to find how to find the correct version for your region/carrier.
[Galaxy S III General] cyberdroxxx:
Now I have 2 samsung flagships siblings slowly sinking into the SDS blackhole.:(
[Galaxy S III General] T0xic4u:
@t0n0n

Flashing a ROM doesn't reset counter. It just changes status from "custom" to official. Counter remains. You have to Do the workaround wich was posted 100 times.

P.S. Flashing with Odin doesn't make a Wipe.

Sorry, but all you say is wrong.

Taper di Tap with my S3 @160 days
[Galaxy S III General] blackspeedy:
The date I gave is the date my phone is made system information or something?

Fill in this code *#12580*369# and you see the information.
[Galaxy S III General] STELIOSFAN:
Check here and here

It's a red small exclamation Mark on top left of the screen when booting. Boot animations come after, so nothing is changed.
[Galaxy S III General] Andrewtst:
My phone was back from service center as well, I just did shutdown and restart. They is no red mark at corner during boot-up.

Mine still 100% stock and no root back yet. Is that means after root, red mark will appear?
[Galaxy S III General] STELIOSFAN:
Most probably, yes. Please check and confirm
[Galaxy S III General] UncleBeer:
Well, that's what folks in those other threads claim, but no-one's been able to explain how I didn't have the mark when rooted (shortly after purchase), but did have it fresh from the service center with new board, stock firmware, and NO root.
[Galaxy S III General] PjotrFias:
What does download mode say?
[Galaxy S III General] Andrewtst:
Means no one actually know it means what? Mine after from service center back, no sign of red dot.
[Galaxy S III General] UncleBeer:
Phone's now rooted (by me) and red mark remains. Hard to imagine the service center would have gone to the trouble of rooting it for me though. ;)
[Galaxy S III General] PjotrFias:
That's true, but the counter could have gone up or even it detected the ROM as Custom.

Anyway, it's connected to never bootloaders, you can get rid of it by flashing the old one. http://xdaforums.com/showthread.php?t=1918667
[Galaxy S III General] UncleBeer:
(a shame to rehash everything that's already been said in the "red mark" thread, but...): Where would a bootloader reside but on the motherboard? The phone's essentially a motherboard, screen, battery and case. Since the motherboard + firmware were factory fresh, it's unfathomable that the "flash counter" or bootloader somehow remained on the phone.

Regardless, as this thread shows, the S3's fragile nature makes it unlikely I'd risk flashing anything just to remove the red mark. I'm happy just to have my phone working again.
[Galaxy S III General] PjotrFias:
Ah, no. OK, you rooted it, so yeah, red mark is to be expected. But if you planned to leave it stock, it would be better to demand that they remove the red mark. Just to be sure there is no issues when you take it back if you need to. That's all I wanted to point out. Sorry that I was unclear.

It's a bit sloppy of service center IMO, to hand you back the phone this condition.
[Galaxy S III General] UncleBeer:
I think you've misunderstood: fresh out of the package after repair at the service center, with a new motherboard and official firmware, (thus highly improbable it was rooted), the red mark appeared at first boot. Again: I can't imagine any way my previous root remained on the phone. All the "working parts" had been replaced.
[Galaxy S III General] relaksua:
Hi guys

I was browsing tru xda about my s3 issue and came across this thread which i m having the same issue .. On the morning 29th Nov, i was replying some whatsapp msgs and about half an hour later...my phone just went dead ... like the rest posted, all seems to fail and no LED light when charging or changing of battery..recovery or even download mode ..the phone failed me when i need it most during my holiday trip ... i rooted the first day i got in back in June and had been using Omega roms with no issues .. didnt touch the kernel though ...already sent it to a service centre and they have yet to get back to me about the problem... glad to know that i am not the only one with this problem
[Galaxy S III General] pedropac72:
I´ve noticed than people who suffer this Sudden Death and can be into Download Mode have this info

ODIN MODE

PRODUCT NAME:

CUSTOM BINARY DOWNLOAD: No

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Custom

With "Product Name" without information and SYSTEM STATUS allways in Custom. Saw in another forum some people still have the name in Product Name, and they were able to reinstall roms into the phone.

I readed almost the complete thread, and I am wondering if it would be the definitive symtom to know if we are dealing with a Sudden Death problem. In fact, this made impossible to Services to know if your phone was rooted and flashed or not. The presence of "Custom" word made some people to doubt about send to Service, but I sent it with this text and I had no problem at all with Warranty (Spain)
[Galaxy S III General] ivan4o5:
Overall

Well guys , I've managed to count the cases of "sudden death" of galaxy s3 in the XDA forum , and it is approximately around 55-65 . I assume that not everyone that owns a smartphone is aware of the XDA forum or that everyone is rooting/flashing their phones , so I guest that is just 30 % of the cases (rough said) .

So statistically , we have around 220 death phones (maybe) . The sells are about to reach 30 million this year , but for now ,lets say they are 20 million . That is about 0.000011 % of the phones . Maybe my math is wrong ,so lets make them about 0.1% of the phones .

The other thing is that most of the cases are related with the Blue phones , and the other part is related with the White phones .

The chanses of having a faulty phone are small , but they persist ... If there are more cases ,please tell us what colour is your phone and when you have bought it ,because I think the problem is related with the early releases .

Thanks for the spared time guys . Peace :angel:
[Galaxy S III General] kanin_rider:
Hmm.. Just sharing my thought on this problem,

If its a hardware failure of the early production releases as stated by most of us here, i think it helps if you check your hardware revision by typing *#12580*369# on dialler, if it says HW rev. MP 1.100, you are probably safe. (Assuming .100 is added to indicate that the fix has been implemented in the motherboard design)

For those who have bought their s3 shortly after its release way back in june OR s3's that are manufactured around that month or earlier, can you check if its hardware is a version/revision 1.0? (Not sure if this version exists) If thats the case, its probably a design flaw in the early batch of production..

And if this theory is correct, we can easily pinpoint which unlucky ones will 'die' suddenly in the future..
[Galaxy S III General] PjotrFias:
I doubt that tells us anything, I have a month and a half older phone and it has the same HW version.
[Galaxy S III General] thekoRngear:
What is that font on your phone? Is it with custom or stock rom??
[Galaxy S III General] dorsalsk:
Not sure if that theory is fully true. But my experience was not a sudden death and cannot really say if the version earlier was 1.100. Anyways this is what happened

My phone had fallen down and the screen broke. So I gave it to the service center to get it fixed. After receiving it, all was fine and had about 50% charge. About half an hour later back home I noticed it was not charging. Once I removed the battery, inserted the sim and tried to turn it on and it wouldn't. If I try to charge, a grey battery icon comes and goes. Initially I thought the battery drained out, and tried a friend's S3 battery but with no use. I took it back to the service center and next day they returned it saying they changed the charger pin on the phone. Now it works fine and shows the version as 1.100. But even though now on stock, I had tried some custom roms and the download count in download mode still shows the same. So I'm kind of sure they haven't done anything with my motherboard.
[Galaxy S III General] spamtrash:
Red exclamation mark ! in the left-top corner during boot, while Samsung S II is displayed.

Its appearance seems to be strange to me, as I have two S3s (both I9300 international).

One is BWDLI1(baseband) XXDLIH, with CWM and speedmod k2-1 kernel - it shows the red mark.

Second one is XXDLID (baseband) XXDLJ4, with siyah 1.7 rc1 - it does not show the red exclamation...

Both received within one week in mid October. Both are blue...:eek:
[Galaxy S III General] ivan4o5:
Imagine that the red ! could tell us which device is going to last longer and wich not ... Just kidding , but that is strange . That was supposed to be the "Samsung counter" , isn't it ?
[Galaxy S III General] t0n0n:
Try it, get a full .tar and flash it via PC Odin.

I'm not talking about a CWM file, I'm talking about a real firmware file.

Source: I once did it after messing with my kernel.
[Galaxy S III General] Allesa:
Guys, out of curiosity, are those people who passed the 200 days mark charge their gs3 using its original usb cable connected to the charger or other usb cables?
[Galaxy S III General] Kjc99:
So flash a tar file which should be safe and this will bring me back to stock firmware and hopefully reset binary count. I live in USA and warranties are very hard to get on international samsung phones in US if the Binary does not reset we just wait for chain fire to update triangle away for new bootloader..... Sorry noob

Galaxy S3

Omega Rom V36
[Galaxy S III General] T0xic4u:
Sorry, you are still wrong. Flashing stock rom with Odin doesn't reset counter and doesn't wipe your phone.

Don't give false advise mate, don't do it.

Taper di Tap with my S3 @160 days
[Galaxy S III General] fedort:
My phone has over 200 days and 80% of the times I´ve used my old Galaxy S2 charger. From now on I only use my S2 charger, just to be sure.
[Galaxy S III General] pigglett:
I've mainly charged mine via pc over night ..odd time with stock wall charger ...mine is 210 days old
[Galaxy S III General] Allesa:
Well im over 200 days too and i use an old blackberry usb cable coupled with the original sgs3 charger and sometimes for more current I use 2A galaxy tab charger connected to that usb.. The GS3 usb cable still sitting nicely inside the box. Anyone else?

Using what cable? Samsung provided USB Cable or other usb cable?
[Galaxy S III General] flight23:
I got my S3 in the begin of June 2012, so now about 215 days. For about 90% I used the original S3 charger and charged it over night (every 1-2 days, for around 6-7 hours). Phone is rooted and was flashed quite often (Omega, Viking, Paranoia etc.).

Until now I have no problems.

Now, for my own safety, I went back to latest german Stock (ell4), rooted it and reseted counter and status to make sure I'm under warranty.

Edit: As many mentiones their phones stuck with blinking LED as if a notification was on hold, when the phone died:

I use timeriffic to switch into airplane mode overnight. So there aren't any incoming messages/notifications when it's being charged.
[Galaxy S III General] skivnit:
Im using the battery kit to charge second battery and keep swapping the batteries.so i hardly use the charger on the phone. So far so good.

Swyped from another galaxy
[Galaxy S III General] KeesStolk:
228 days and still alive.

9 out of 10, charging overnight with the wallcharger that came with the S3.

Flashing Omega roms since day one, currently on Omega v36 and this weekend i flashed the new bootloader separate.
[Galaxy S III General] villieb:
Just for the record (I know this is now 230 odd pages long now), but I've also experienced this sudden death problem.

I can't give you specifics as the phone is (still) with Samsung and here's my story (sorry if it's a bit lengthy)...

On the 22nd November the S3 died and wouldn't turn on. Changed battery, charged overnight still nothing. I sent it to Samsung only to have the phone delivered back to me stating that the main-board wasn't of UK origin. I sent the phone back to the Amazon shop I bought it from and advised that they sold it as a UK phone but Samsung advised my it wasn't a UK phone. They apparently spoke to Samsung who told them that it should be eligible for repair and was sent to a repair centre in Scotland called Regenersis. This repair centre had the phone for a week and it got sent back to the Amazon shop un-repaired stating that it was beyond economical repair due to water damage or excessive force damage or unauthorized repair. Obviously I wasn't happy about this and rejected this. The Amazon shop has sent it to another repair centre - the reason for this...

"Even tho all repair centre should have a same guidance for every repair, but some knows in more details than the other. for example, your unit should be covered by the warranty which I confirm with Samsung, but then the first company you used had never dealt with an unit outside UK and hence they do not know the procedure and had rejected the repair.

Then the second one looked into it and gave the letter to state that it is beyond economically repair but did not state clearly what the problem is. So this time Samsung has put me in touch with someone who they said had more experience and should be straight forward."

Still waiting on Samsung to get back to the Amazon seller....
[Galaxy S III General] duhhh:
218 days use only stock charger
[Galaxy S III General] CSeb95:
Mine died this weekend after a bit more than 210 days.

I used to charge it most often on my computer at work with a Nokia USB cable. Sometimes at home either with the original charger or a blackberry one or on my computer.

I never used the USB cable provided by Samsung as I have plenty of others.

My phone switched to airplane mode at 2am and back on at 6.30am everyday. Notification led was always blinking either for a mail, a SMS, a calendar or FB event ..
[Galaxy S III General] Ottoman52:
#SolveGalaxySIIISuddenDeath

We can make TT a tag like that and maybe Samsung will care much about this topic.At least we can force them to explain the issue.
[Galaxy S III General] prakalejas:
General problems with firmwares and chargers

There's a similar problem with firmware on different samsung device (just to prove, that firmware might cause SDS): http://www.anandtech.com/show/6503/second-update-on-samsung-ssd-840840-pro-failures Basically if you write a lot to device and the firmware has a flaw, then it's inevitable for a nand chip to fail.

On the other side - lot's of posts states, that there might be a problem with the charger, which shortcuts or overvoltage to the cable, thus demaging the motherboard of the phone.

So to be on the safest side (not completely, but better one), 1. we need to monitor charger (or replace with reliable or less powerful), 2. upgrade to latest firmware as soon as possible (upgradeing it on heavily used NAND chip will not fix already damaged parts), but if the damage is big (near complete fail) SDS will likely to happen anyway and such cases would not prove that firmware upgrade didn't help or solved possible failure, it would mean that it was applyed too late. 3. use microsd card as much as possible (I had several micro SD cards also dead during past few years on other devices, so additional backup is also a must).
[Galaxy S III General] enigma1981:
I just worked out that I'm on 296 days and I've charged overnight - every night - since the day I got the phone

Always with the stock wall charger + cable provided.

And while I've been on a custom kernel (siyah/yank555.lu) I've been fast-charging with the current set to 1200mA
[Galaxy S III General] KeesStolk:
http://en.wikipedia.org/wiki/Samsung_Galaxy_S_III

So you had you device mid March?