yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] KusakaKyo:
Does anyone know if the lastest versions of Siyah Kernel have this fix??, also, whats the best kernel to get this fix, since i got my S3 with the damned doomed chip, and i have a friend who owns an S3, i wanna make sure what would be a nice kernel to instal in my friend's phone, he doesnt use his phone like i do, so he has no idea how too root his phone or flash a new rom ... Im just trying to make sure i can save as many S3 oblivious users as i can :P
[Galaxy S III General] scottcwhite:
Yes it is BS. I'm ready to do some majoring arguing when I call for another update on Wednesday if they tell me the same thing. What scares me though is what if they say it's a USA phone and Samsung USA says it's an international and neither will touch. In all reality, what can I do? I can't afford to hire a lawyer and sue them
[Galaxy S III General] Kjc99:
Do you have proof of purchase in your package that you sent over seas? I've been following your story and you have been screwed left and right.... Last I remember they were holding your phone ransom for money just to get into the UK I'm hoping everything works out for you as I am also in the United States with an International phone and warranties should not be this hard to receive service! Or they should have a special service center for us to send it HERE IN THE USA if they can sell them here they should fix them TOO
[Galaxy S III General] danarama:
http://xdaforums.com/showthread.php?t=2091045
[Galaxy S III General] scottcwhite:
I definitely agree with your last statement
[Galaxy S III General] Product F(RED):
The thing is they're not sold in the USA by Samsung. While I agree with you that it should be repaired regardless of where it's coming from, sadly it's not the reality. Samsung sells only the US carrier models here, not the i9300. That's why they don't support it. However, I purchased mine from Amazon, from a seller in Germany. The first time I needed repair, the seller told me to ship to them and they forwarded it to a repair center on my behalf. It cost me $80 and 3 weeks time (shipping cost, repair was free under warranty). It was not for SDS, before anyone asks. The seller overnighted it back to me though, which was nice of them.
[Galaxy S III General] ddurgan:
S3 now fixed

I have finally had my S3 fixed by Samsung on it's 3rd attempt by a Service Center. My phone had the eMMC brick bug and was highlighted by the brick bug app. All the symptoms described in this thread.

The 3rd Service Center diagnosed the fault as an electrical fault (not eMMC) and have replaced the main board with a new one that does not have the brick bug firmware etc.

All working now which I am happy out, but not the fact it took Samsung 4 weeks and 3 Service Centers to fix it (even though I told them each time that it had a hardware fault and they only flashed the phone to fix it).
[Galaxy S III General] Generik99:
My S3 has done the same thing.. from working perfectly to brick overnight. Since I obviously can't install the fix, Is there any quick links that I can use to get to the right site for requesting warranty repair? I sent a repair request via Samsung UK (even though I'm in Canada, it's an I-9300) but I haven't heard back.

Is there another avenue for warranty repair, or am I SOL? Sorry if this has been covered before, not really looking forward to reading 470 pages of the thread ;)

Thanks!
[Galaxy S III General] Fygaroo:
On what android version were you when it died?
[Galaxy S III General] Generik99:
I'm not specifically sure, it was whatever the latest Samsung-released version was. I updated via Kies a few weeks ago. The phone was rooted but running the stock kernel.
[Galaxy S III General] macuis:
I also tried contacting Samsung UK and Samsung Hong Kong. They simply refer me back to Samsung Canada, which they referred me to Samsung UK. Vicious circle. I heard this site is pretty good with a quick turn around time. http://www.freesamsungrepairs.com/

I probably should've went through them instead of sending it to Expansys via the RMA process. I sent my phone on January 8, 2013 which they had received on January 15th. 9 total weeks and counting: still nothing. I've contacted them, but they only know that they've sent the phone to their Expansys UK warehouse. Using this ****ty Motorola RAZR V3... brutal :(
[Galaxy S III General] scottcwhite:
***UPDATE*** It just keeps getting better. Well after about 2 hours of speaking to Samsung UK and Anovo where they had me send my phone I have been informed that they will not be fixed by them as due to a recent change they no longer service the International version, just UK model. So now my phone has to be shipped to a different location in England that services the International S3. What Anovo is doing now is communicating with Telecom (the other facility) to see if it can be shipped straight there. If not I'll have to pay 28 pounds to ship back to me than pay 120 dollars again to ship it back to the second facility. If they tell me that I will just have them throw it on the trash.
[Galaxy S III General] danarama:
They're talking BS then because there is no UK model. ALL UK S3's are the GT-i9300 or GT-i9305 International (or international LTE) model.
[Galaxy S III General] mikey_sam:
Are the newer s3's coming with the unaffected chip ? :o
[Galaxy S III General] Abaddon:
yes, but if the 32gb ones are unaffected
[Galaxy S III General] mikey_sam:
32gb ones were always unaffected right? what about the newer 16gb ones from the jan feb 2013 batch ?are they coming with the newer unaffected chip? i am looking to buy a 16gb one as the 32 gb isn't avialable easily
[Galaxy S III General] Abaddon:
yes. they aren't.

I think they're still affected (New Batch). bought one last week and got SDS three days after good thing it got replaced after 2 hours of having SDS. (Manila,PH)

If I were you I'd rather get a 32gb version instead of a 16gb :)
[Galaxy S III General] _Variable:
Will s4 have sds?

___________________

Sent from the other side...

Press the THANKS button if I helped.
[Galaxy S III General] sh_:
Lol
[Galaxy S III General] nageshv24:
I think we have to wait for about six months when S4 SDS thread pops up.... lol
[Galaxy S III General] _Variable:
It took 6 months for the issue to pop up? :eek::eek:

___________________

Sent from the other side...

Press the THANKS button if I helped.
[Galaxy S III General] mikey_sam:
wow, Thanks mate. That 's very helpful info .some one earlier reported that he got the new unaffected chip on his jan 2013 manufactured s3 and i was gonna take the plunge today. And another friend bought a note 2 last week (feb month manufactured )and it had the unaffected chip

anyways, i am not taking chances again. you just saved me 500 $ :good:

though, are you sure, the one you bought was from the latest batch? did you note the manufacturing month by any chance ?
[Galaxy S III General] Kjc99:
Sounds like where there's was bought they were still unloading old stock
[Galaxy S III General] aspot72:
Just got my S3 on last Friday and checked the chip with eMMC app and it's saying Sane. So happy days.

---------- Post added at 05:53 PM ---------- Previous post was at 05:50 PM ----------

Just got my S3 on last Friday and checked the chip with eMMC app and it's saying Sane. So happy days.
[Galaxy S III General] Z5745:
Hi to all I just got the s3 and I have heard about the ads problem so I downloaded the emmc app to c

check my phone, so I discovered that i have the bad one. What should I do ?

My phone is not rooted working on the last samsung official update 4.1.2
[Galaxy S III General] scottcwhite:
After what I've been going through you could not pay me to buy another S3 International version. I have $750 invested in a phone that is 5000 miles away in the UK plus the 400 I had to spend on this one. If I ever get it back it will get sold with this Nexus 4 and I'll gamble with the S4. If that dies I'll officially wipe my hands of Samsung products.
[Galaxy S III General] Product F(RED):
I know this is off-topic a bit, but my S3 has an insane chip and has been fine. I know that people whose S3 have died have said that it just happened without warning in some case (little to no freezing at all), but if my S3 doesn't die, I don't think I'm getting the S4. It has nothing to do with how Samsung is handling it. I just think that, SDS aside, the S3 (at least the i9300 and i9305) are powerful enough. Sure it's nice to have beefier specs, especially for me since I play a lot of games on my phone. But I feel like it's a lot of people are calling it: The Galaxy S3S. The only thing I really care about is the 2GB of RAM, but even that's not a big deal at this point, since the Nexus 7 has 1GB of RAM, for example.
[Galaxy S III General] Dean-xXx:
When is everyone gonna understand that the emmc app is not for the S3. It was made for the S2, so the sane/insane chip info is not relevant to S3. We use it on the s3 just to check the chip model/version..
[Galaxy S III General] Product F(RED):
I was the one who brought it up in this thread to suggest using it. I specifically told people that it's made for the S2 and is only good for checking the chip in your S3. But the app was recently updated (recently as in weeks ago) to also correctly work on the S3 and Note 2. So now if it says "INSANE CHIP" on your S3, you actually have the bad chip.
[Galaxy S III General] cotarelo:
I woke up also with the phone dead... I tried to charge it without success. Yesterday it was working fine and it had around 30% of battery before going to bed

My phone is a European 16G White GT-I9300A. It is rooted and with a custom 4.1.2 rom. At the moment some work colleague is charging my battery so I can use it again. I am wondering if it is better to apply the patch or take it to the service...:confused:

I am also worried that the rooting has void warranty. :rolleyes:
[Galaxy S III General] Fygaroo:
If the phone is dead they cant see if its rooted , what rom did you use exactly?
[Galaxy S III General] cotarelo:
Sadly, my SGS3 it's not turning on even with full battery charged (I charged it in another phone) :(

I used MS Team HD 6.0 (first one using 4.1.2) ... I have the efsbackup if it is needed... I think I need to take to the service... I am afraid they will tell me warranty it's void ... Besides, I had the phone unlocked via IMEI ... do the European service give you a different phone?

AP: 19300XXBLFB

CP: 19300XXLFB

CSC: I9300PHEBLG1
[Galaxy S III General] Dean-xXx:
On my s3's both showing Yes. Insane chip :silly:

However one is launch day and one is from august.

On one even the chip date is wrong showing 2006 :silly:

So far no problems/freezing with any of them. :angel:
[Galaxy S III General] cotarelo:
Totally agree. I have been through also. I am very upset as I spent 500€ (about 650$) on what it should be the best Android Phone in the market. And there was really a lot of issues (remember when we were waiting for 4.1?, speaker not working). Samsung should shame for this. If I would know this I would have get a SGS1 since that phone never had this issues. We are now in a point that the phone is very important for the daylife (agenda, calendar, mail, maps) specially if you are on the run...

By the way... Can someone tell if they sent their rooted / custom rom phones to the Samsung service and if was a problem to apply the fix?

Regards,
[Galaxy S III General] danarama:
I know someone with an SGS1 and the speaker doesn't work. It also hasn't got 4.1 yet :)
[Galaxy S III General] olyman:
Damaged USB

My S3 died while charging overnight, it seems to match all the sudden death synptoms. I sent it off to Samsung for repair. 10 days later I received a quote from the service centre saying that the problem was a damaged USB and that it would cost £73.94. I've asked them for more information and that this is a problem well documented on the internet and I'm waiting for a response. They've not mentioned any water damage, just 'Damaged USB' and that it's out of warranty. Are they likely to change their diagnosis and do the repairs free of charge?
[Galaxy S III General] geekbrains:
My phone was behaving erratically over the last few weeks (Random reboots, frequent freezes etc). After countless hard resets, it became worse that I couldn't even complete the setup after the hard reset. The phone freezes as soon as it gets connected to WiFi or HSPA networks. Samsung service center returned the phone as fine twice (Express 3 hours Service) but the problem persisted. I demanded to meet with their manager and proved the senior technical engineer wrong right there in the service center. They took 45 minutes to replace my motherboard after all the fuzz that I made and so far this replacement motherboard is working fine for more than a week now without a single reboot or hang.

Strangely enough, my friend's phone with the same affected eMMC hasn't experienced a single reboot or freezing issue.
[Galaxy S III General] amarsana:
done with samsung

My siii died in my pocket 2 months ago. I bought it on ebay in USA. Now no one would touch my dead siii.

Samsung USA told me it is from UK. Samsung UK says it is from Samsung South Africa. I'm calling samsung usa once again. if they don't fix it, I will be done with Samsung. Let me remind you I bought more than 10 pieces of Samsung Siii-s for friends and families. Complete bull****.
[Galaxy S III General] scottcwhite:
***update*** so pissed

Just got off the phone with Anovo again to find out if my phone had been sent from them to Intercity Telecom as Samsung UK directed them to do last week. Apparently Intercity said not to ship it to them because they can't repair it either and that Samsung UK gave incorrect info and it has been escalated. Anovo just wants to ship my phone back to me at my expense which means I waisted $120.00 dollars sending it to them in the first place. So now I have to call SS UK back because this is screwed up. Apparently no one can fix the phone and I should just throw it in the trash.:mad:
[Galaxy S III General] cotarelo:
Service accepted the phone. I will post my impressions in a week
[Galaxy S III General] samalmaskey:
My s3 shows..

Vtu00m

0xf7

Am i safe..from sudden death??
[Galaxy S III General] jeffnz:
Read the first post your answer is there
[Galaxy S III General] samalmaskey:
Ya I read 1st post but i'm still confused

My s3 shows..

0xf7

And in 1st post... it says 0xf1 is not safe...so just to be sure i asked...and....what's the difference betwen 0xf7 and 0xf1...
[Galaxy S III General] Kjc99:
OXF7 firmware is considered safe there are no reported sudden death incidents with that chips firmware consider yourself "safe"
[Galaxy S III General] revo66:
I also have 0xf7 so I think im safe. But I want to root my phone and install the XperianZe or crDroid rom, can I just do that or do I need to flash new recovery, bootloader or kernel first? Are the fixes 'built in'?
[Galaxy S III General] rodrigoyasuda:
With 0xf7 it doesn't matter, you don't need the fix.
[Galaxy S III General] hrubilar:
Sudden Death

Last night, I had the phone charging, the LED blinked and thought it was a message. Press the Home key and the screen was white ... Restart the phone and returned to normal.

I think it was sudden death.

My phone has the latest ROM from Samsung (4.1.2 Nordic Countries) and Siyah kernel 1.8.9

Apparently this correction was protected. Today it works normal.
[Galaxy S III General] Product F(RED):
That has to do with a lockscreen vulnerability... This has nothing to do with that. Nice job baiting your own website with the link though...
[Galaxy S III General] RohanM:
Some Sony Xperia Z handsets reportedly suffering sudden death

http://gsmarena.com/some_sony_xperia_z_handsets_reportedly_suffering_sudden_death-news-5738.php
[Galaxy S III General] Product F(RED):
I wonder if they're using the same chips.
[Galaxy S III General] jay_m3:
why you said it was SDS?? it could be just a simple bug!! all what you needed is givin it a restart!!
[Galaxy S III General] hrubilar:
dije: Creo que fue SDS... No sabía que había otros fallos
[Galaxy S III General] skinerbr:
My turn

Well, my S3 had SDS last february 27th. I bought it on mid august, and it started freezing on latter november, just a few days after I updated from stock ICS to retail JB via FOTA. Brazillian official JB was released by that date. I also had it rooted a few days after the update, but then the freezing was already showing up.

Although it had the freezing issues, the phone never restarted itself. Maybe I am forgetting one or two times it happened, but this surely was not a syptom of my device.

I always kept it plugged to the wall like 12 hours a day, so I slept everyday with it charging and whenever I got up and went to work, just after sitting on my desk I would plug it to the wall again until the end my work day. Then, after getting back home, it often was back on the wall until the next day.

The phone had a cracked LCD after a drop from around 12 inches high on a plush surface, which was such a weird thing as I had it dropped like 10 times from higher locations and on hard surfaces and it didnt have a scratch.

Well, I got it to CSC on the same day it bricked, and was waiting to hear something like the cause of its brick was the cracked LCD.

Before I tell you the news I got today from Samsung about the fix, I must tell you how the damn assistance works here in Brazil, mostly in my city. There's only one CSC for mobile devices here and much more CSCs that only get TVs, DVD players, home theaters and other stuff. Though, the CSC that receives mobiles ALSO receives broken TVs and those other stuff. So, the attendance is pretty f****d up, I had to face a huge line and wait for hours until someone received my phone. The worst thing is they said that they would not call me or contact me at all to give me news about the status of the fix, and I had to call them to get to know what is going on to my phone. But they don't answer their line!!!! When the CSC's phone is not busy, it rings indefinitely and no one answers it!! Hopefully I could follow the repair online on samsung's website since 03/13, which was when they really got the phone to assistance. So, my S3 was from 02/27 to 03/13 stuck at the CSC for nothing!!

Well, today it showed up as returned to CSC and I called Samsung's national customer attention center for Brazil, as I couldn't reach the local CSC staff with their stupid non-responsive phone. I asked the girl how was my phone (and of course took the chance to claim a lot about this poor CSC which can't even call their customers), and what a great surprise was to hear she telling me it was fixed with the mainboard AND THE LCD replaced. This was totally unexpected. Well, I won't believe until I see it personally, but I can tell you this would be a great gift from Sammy.

I know I wrote a lot, but I think we should share as much information as we can in this thread. This issue is really disappointing for a device that costs so much.

Cheers, guys. I'll be back to report about device's new hardware.
[Galaxy S III General] oae08:
Which recovery is SDS proof? I am on CWM 6.0.3.0

Thanks...
[Galaxy S III General] jeffnz:
Read the first post all your answers are there , strangely you question has been asked many times hence reason op put answers in first post
[Galaxy S III General] oae08:
Actually that is in the other thread ;) anyways yeah ive read it and it says only philz siyah and twrp. I hate twrp and siyah doesnt work with latest cm nightlies. So i have no choice except philz.
[Galaxy S III General] Product F(RED):
PhilZ 4 is good. It is literally just CWM Touch with a ton of extra settings, like the ability to flash more than one ZIP at once.
[Galaxy S III General] danarama:
Ha ha. .. I think "just" is an unfair word. :)

---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------

Like product says above, Philz is good. I'd actually say its great
[Galaxy S III General] Product F(RED):
Lol you're right. By "just" I meant to emphasize that it's built on CWM Touch, but improves on it by a lot. It's kind of like how AOKP is CyanogenMod with a ton more useful features.
[Galaxy S III General] danarama:
Yeah I know :)
[Galaxy S III General] NeatWolf:
Hi everyone!

Here's my experience:

Got a international, unbranded GT-i9300 16GB Pebble Blue (EU, bought in Italy) on August 2012.

Installed a custom 4.1.1 rom with Syiah Kernel, worked with no problems for the last 4 months.

Started to experience some stuttering when unlocking the phone, and when using SwiftKey 2 weeks before SDS.

Left the phone for charging in the morning.

At midday Found the blue led blinking while still plugged to the charger, tried to unlock the screen but couldn't.

Rebooted the phone and is now stuck at the Samsung Logo, doesn't get to the Syiah boot image, when charging (*IF* it's charging) the display stays on, the animation is frozen.

To switch off the phone I have to remove the battery.

What I see in Download mode:

Odin mode

Product Name:

Custom binary download: No

Current Binary: Samsung Official

System Status: Custom​

I believe it could be SDS, and stumbled upon this topic.

I quickly browsed through a few of the >400 pages and the main post but I'm still dubious, probably a few more Questions/Answers could be appended to the first post.

Is there a solution to this? Has anyone managed to fix the phone without changing the motherboard? Are there documented cases of resurrection?

Is it safe to leave it charging since the display doesn't turn off? Is it even charging?

I'm also a bit curious about people that have experienced the SDS but I should probably be opening a new topic/poll.

I'd like to know, in average, what is the success rate of sending the phone to Samsung and having it repaired under warranty with "System Status: Custom".

I've read there have been many cases, and I'm a bit confused: shouldn't Samsung apply the same policy worldwide?

Is it more probable to have it repaired in the EU?

Thanks for your time. :cowboy:
[Galaxy S III General] satishp:
Correct me if I'm wrong. I've been silently following this issue on XDA since a while and from what I found out from a thread researching on the new patch is that, the patch is only if the device meets certain criteria. That is, as everyone knows, the VTU00M chip with firmware revision 0xf1. But if u notice more clearly, the patch is applied only if the date of manufacture (of the said chip) is 13-04-2012. If your device has a chip with manufacturing date other than the one mentioned, the patch is not applied.

So does this prove that people experiencing the issue have chips manufactured in the month of April 2012? Because, when you take numbers, the galaxy S3 sold 20 million units in the first few months alone. Newer chips only started showing up in December 2012 and later batches, by which time the the number of sold devices reached 40 million.

In short, what I'm trying to say is that, an average of atleast 30 million devices would have shipped with firmware revision, 0xf1. But if every chip with this firmware had to die, that would result in 30 million dead phones at some point of time.

So, isnt there a possibility that chips manufactured at the mentioned date of 13-04-2012 have died? Atleast thats what the patch implies.
[Galaxy S III General] danarama:
Its not the manufacture date. Its the firmware revision date... or to be more specific, the date 0xf1 was released that the patch looks for. Manufacture date is the date the hardware of the chip was built but is irrelevant for sds.