yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] marcus905:
Sadly, this is not the case.

I had something totally unexpected these days. I sent my phone to repairs twice because it kept freezing, they upgraded it and sent it back (bought the phone in Italy and sent to the Italian SC) still freezing.

Then a few days ago while seeing if it would stop freezing after a while, I've got an half SDS, white static at boot and download mode with no product name, everything official except custom system -- so a pretty much standard one.

Got the mail today that the phone is out of warranty for unspecified reasons. I think that I'll start arguing with them to see if they will fix it, else I'll take the case to a small claims court and then we'll see.

Anyway, if I have to go to a small claims this will be the last Samsung product I'll buy.

IMO, Samsung: if you don't want to do a recall, just fix those ones that are RMAed no questions asked if it's because of the SDS. You're losing customers here...
[Galaxy S III General] danarama:
Yep. They've lost me already, but I'm here for another 12 months
[Galaxy S III General] sewer56lol:
My next move is back to Xperia.

Sony gives great support to devs at XDA.

Not buying Samsung again.
[Galaxy S III General] Blackwolf10:
hi guys my galaxy s3 has the effected chip so i updated to the leaked 4.2.2 so should i consider myself safe ??
[Galaxy S III General] Thin_Bezel:
Yes
[Galaxy S III General] OrangeRafi:
Yes & No. Only time will tell if your phone will die or not
[Galaxy S III General] Kjc99:
Yes I have the same question I know we can consider NEW releases from Samsung SDS safe but what kernel comes with the leak? Is it a newer kernel or is it safer to wait for official release of 4.2.2?
[Galaxy S III General] danarama:
Of course its a newer kernel
[Galaxy S III General] Blackwolf10:
as the person above said its a new kernel so the official will only be good for bug fixes maybe new features too (the only bug i have is graphic glitches when battery is low) and samsung will give kernel sources then so we can have custom awesome kernels
[Galaxy S III General] skycasaway:
my problem please check

i have got a soft brick,, it means i played with odin repartion , delete Nand and flash stock buttons ,,, so it's my own mistake !!

what i realized to my weird problem is that when i enter restore mode the mobile custom number Gt-i9300 has disappeared,,,

also when flashing my firmware with odin,, it sais there's no PIT file for mapping,, keeping in mind my phone is 16 gb ,, AUT swiss version.

i might help you with these infos
[Galaxy S III General] dwarazyjot:
Hi all,

GT-I9300
Android 4.1.2
Modem I9300XXEMB6
3.0.31-Siyah-1.8.9+
Omega v41 - ZSEMB1
Philz touch recovery 5.05.7
Bootloader XXEMD2

Type VTUooM
Date 05/2012
FwRev 0xf1

Am I safe or upgrade Omega soft to newer? I'm thinking of v42 on XXEMR2. v43 was bad to me so I stayed on v41. Thx.
[Galaxy S III General] alentor:
Hey, I got the infected chip I'm running CM10.1, should I flash XXELKC firmware? Will it make safer will I still be able to use CM10.1?

Thank you..
[Galaxy S III General] jeffnz:
read the first post all your answers are there
[Galaxy S III General] alentor:
Thank you, do I have to install both Siyah kernel and PhilZ recovery or installing one is enough, also can I install an Siyah based kernerl? I've tried tto download Siyah kernel but the the link on the website(http://www.gokhanmoral.com/) but the download link seem not tonfunction..

Thank you
[Galaxy S III General] Waquar:
My Samsung S3 sudden death!!!

Hi, This is Waquar Adel from Dhaka, Bangladesh. Two weeks back in the morning I found out my S3 phone's power is off. The Samsung authorized service center informed me, the motherboard is gone, and need to replace it. And that would cost me BDT. 27000tk. The phone was a gift from my wife to me on Feb 3rd for my Birthday. This phone has made my hole family (me, my wife, 3 kids) very unhappy. If any any one can help me out from this disaster pls let me know.

Thanks
[Galaxy S III General] tqgia2:
I don't know if anyone can help you if your motherboard is gone...

Does your phone get into download mode? If so could try a flash
[Galaxy S III General] danarama:
It should be covered by warranty
[Galaxy S III General] stevoswifty:
Sane chip according to emmc does that mean im ok im rooted
[Galaxy S III General] jeffnz:
I see you are new but did you at least read the first post??

all the answers are there, if you don't have the affected chip then you are fine.
[Galaxy S III General] Sam654:
Posting in the correct forum now ;)

I've read through a lot about this half SDS or freezing issue and it's really paining me!

From the three screen shots, I hope you can see that:

1) I've got the Dummy File generator and have been using "Generate(FULL)" mostly on the INTERNAL SD, but also in the INTERNAL MEMORY. You can also see that I've got loads of space, which is because I installed a new ROM and this is the first thing I ran in the hopes to solve this issue.

2) I've downloaded the eMMC check and it says that I'm running the Type: VTU00M (YES. Insane chip).

3) In my settings it says that I'm running 4.2.2 of Omega v45 which is meant to be Type XXUFME3.

I'm still getting freezes.

How many times do I need to run the dummy file generator?

Advice would be well appreciated.

Thanks

Sam
[Galaxy S III General] stevoswifty:
Yea I read it but still learning about it all didnt mean to post a daft question
[Galaxy S III General] jeffnz:
all good just follow the links in first post if you still aren't sure.
[Galaxy S III General] Sam654:
I'm in Australia and on the Telstra network.

The sammobile site doesn't list my baseband version. So I would assume that I just pick the latest? But then am a little concerned that there isn't a 4.2.2 version and if that's going to cause me problems.

I want to ask what this is changing, my ROM, or something that won't be seen, but I'll hold back any more questions as I don't want any more abuse from the previous poster.
[Galaxy S III General] jeffnz:
if you are running 4.2.2 then you should be fine, the freezes may be due to something else. Follow the link in first post to the other SDS thread for more information.
[Galaxy S III General] stevoswifty:
They will just blag you till you give up
[Galaxy S III General] Product F(RED):
Which is a big reason I hopped to the Note 2. Better specs, no SDS (at least on the US models). It's not really a solution, but this problem is a big reason I switched.
[Galaxy S III General] sxi200:
Sister's phone died last week. Taking it in to Samsung on Wednesday. Forgot to apply the sds fix for her. Was on an old version of Wanamlite. She's now using my old s3 until she gets it replaced.
[Galaxy S III General] kingeran:
Mine died after 10 month only

Another one bite the ....:( and Samsung ignores
[Galaxy S III General] brainvision:
Hi guys..

Do you think it's safe - and a good practice - to write down here imei and serial number??

{ brvsn • PAC-man 22.3.0 on Nxs7.3g • Tapatalk 4 }
[Galaxy S III General] Product F(RED):
Here, I would not.
[Galaxy S III General] jay_m3:
yea right! :) r u gonna buy me ticket and pay me hotel? cool!
[Galaxy S III General] matijaz:
i9300 died

it died cca month ago, i still have more then a month of warranty but custom binary download count says 1 and Guys from croatian service said - no can do - you broke it :(

Phone can still charge and download mode is "working" i tried to flash latest JB image but write to nand failed:(

So big question here is - does this void warranty? Croatia is still not a part of EU (will be in less then a month)

I talked to samsung Croatia and they said .. well nothing smart. Anyone had same problem?
[Galaxy S III General] Product F(RED):
When the phone dies, the custom binary counter goes to 1 either way, because the phone isn't able to get the checksum of the recovery (since the memory is destroyed for lack of a better word). So it just assumes that you have a custom recovery on there.
[Galaxy S III General] goranbm:
Hello I am curently on XEMC2 4.1.2 stock softwer. I would like to upgrade, can you please suggest what is the best stock firmware to upgrade (4.2.1 or ??) and what custom ROM and Kernel would you suggest for upgrade ? Thank you for your answer.
[Galaxy S III General] matijaz:
Hi Product F(RED)!

Thanks for the info!

Do you have any link describing that? Not that i don't believe you, i'll need something to send to guys from their service saying - AHA! you were wrong!
[Galaxy S III General] Product F(RED):
Unfortunately, I don't have any official documentation, if that's what you're asking about. And I doubt Samsung would divulge such information.

But like I said, the way that the custom binary counter works is that it has a checksum for the stock recovery. If the stock recovery is altered or replaced, the checksum changes, and therefore the binary counter goes up. Since there is "no recovery" or ROM anymore, the checksum comparison fails, and it goes up.

You can tell them this if you want. Maybe link them to this thread?
[Galaxy S III General] matijaz:
Thanks man :good:, I understand it now. I'll send them my phone and provide them with information you just said. if they start to complain i link them this thread. I just hope that i'll get my sgs3 back :/
[Galaxy S III General] goranbm:
If I flash 4.2.1 Jelly Bean (XXUFMB3) or leaked 4.2.2 XXUFME3, could I have any problem in case of SDS (warranty) ??
[Galaxy S III General] Wodge80:
Sudden death on i9305 S3 4G LTE :(

I discovered this thread after a sudden death issue occurring on my Samsung Galaxy S3 4G i9305 which I bought on kogan.com.au in October last year and it died on me on Monday 3 June, last week! The phone just decided to restart itself out of the blue (wasn't even using it at the time, just sitting on my desk next to the computer - not plugged into anything), then hang on the boot splash screen. It is just over 230 days old and has been sent back to Kogan for warranty claim. I was meticulous about ensuring the firmware was up to date on the phone through OTA updates and the firmware was at 4.1.2 at the time of the suddden death!

I only discovered this phenomenon existed once it happened to me and started researching it, by this time it was too late for me!

Kogan received my phone and after daily phone requests to them to fast-track the inspection, they tested it on the 4th day of hassling them and decided that they cannot repair the phone and will send me a replacement. Since they are sold out of the i9305 phones (thank gawd!) they have offered me a free upgrade to the S4 i9505 and store credit for the balance of the price I paid vs cheaper cost of the new phone. Now to fight for 12 months warranty on this replacement rather than continuing the old phones warranty (have 4 months left of a 12 month coverage on the old phone). Hopefully this new phone doesn't have the same issues since its a Snapdragon processor rather than Samsung's Exynos.
[Galaxy S III General] tangosierra_:
Didn't I read somewhere... That 4G models are not affected by SDS, or something?
[Galaxy S III General] Wodge80:
Reading is one thing, but experiencing the problem for yourself is another! :(

I also read that this problem was supposed to be fixed by updating to the latest stock firmware, which I did anyway and still ended up with a bricked phone! :(
[Galaxy S III General] Garreh1989:
Sudden Death Experience

Me and my friend both had the Sudden death. My phone was just sitting on the work surface with about 4% battery left (It was quite late at night) and i came back to it to find it completely dead. Tried charging, changing the battery and hard reset but nothing worked. Sent it back to ThreeUK and they repaired and sent it back to me in 3 working days! :)

My friends died while he had his laptop tethered to the phone.

Mines been working fine since the logic board was changed, and i'm now running SuperNexus 2.0 which is awesome :)
[Galaxy S III General] tom0:
I have the affected memory and the last stock ROM.

Have anybody with a sudden death notice havy battery consumtion and a stuck UI?

I have to restart nearly all 3 days to became a better battery use but it is annoying if I doesn't came over a working day.

It can happend that it hung with blue LED on and it stuck at the boot up and I have to try several times to start.

It look like the processor use and power down is nearly normal.

Max. processor power max. a quarter and deep sleep most time round 50% in CPU spy. If I use less higher deep sleep.

High consumption was showing in system (not Android system) and the UI.

After a restart all look ok for a longer time.
[Galaxy S III General] sohaib770:
S3 Dead

Ok My S3 died last night! it was not on charge it just switched off and wont switch back or charge or connect to PC... no recovery mode no download mode nothing at all! No response! i dont have a warranty that i can claim! Any Suggestions! Paid a lot of money for it... and love the phone! Plz Help!
[Galaxy S III General] brainvision:
Oh men I'm so sad for all of you who run into this awful problem! :(

BTW, it would be very useful for the entire community if who reports the sudden death of his device could also tell us what they flashed, if they already have the last basedand or the xda recovery tool..

Thanks.. ;)

{ brvsn • PAC-man 22.3.0 on Nxs7.3g • Tapatalk 4 }
[Galaxy S III General] jondiehl:
My wife and I purchased a pair of white Galaxy S III phones on August 1st, 2012. Both are 16GB models, SPH-L710. Both are bone stock, and have the most recent stock OTA updates that have been pushed out from Sprint.

About 2 weeks ago, I noticed that my phone had turned itself off after being on my nightstand charging all night (which is what I always do, but my alarm didn't wake me up because the phone had powered down).

I thought nothing of this and restarted it. Over the next few days, it would randomly turn itself off or an application would lock up and the screen would go dark and unresponsive, forcing me to hold the power button for what seems like forever, or eventually take the phone out of it's case to do a battery pull. It would do this about 1-2x daily, usually after the screen had been off or if it had been charging for a while.

Today, while on the charger at my office, I was listening to my TuneInRadio app, paused it to take a call on my landline for a few minutes, and then went to turn the screen back on to start up the radio again and found it had shutdown once again. This time though, it did not respond and would not reboot at all. Took it to my local Sprint service center and they said it was DOA and want me to pay $50 for a phone swap (I don't have insurance on the phone, never do as I always upgrade every 22 months and my warranties on phones are enough as I'm very careful with them).

Anyway, has anyone had luck sending their phone into Samsung for warranty replacement? I'm reading that it might be 3+ weeks before I'd get my phone back, and even then they might try to claim that I've overcharged my phone or some other BS to get them out of a warranty claim (this is per a local Samsung rep at my Best Buy store, stating that you can "overcharge" these phones if you don't pull them off of the charger when it tells you to, which I find odd).
[Galaxy S III General] dhirend_6d:
That is downright BS, overcharging the phone?? How can one do that?? By keeping the phone where a lightning bolt would strike??

These Samsung guys know there is this problem of freezes and stuff still they talk BS like this. Modern phones and batteries stop charging when the battery is full (will cut off the power once it has been fully charged, overcharging protection), Charging circuit have hardware protection. One can however damage the device if there is excessive heating produced while charging which is usually produced when one is doing heavy stuff while charging (Eg : - Playing games etc).
[Galaxy S III General] Krep3:
what about warranty in another country? I'm in Honduras (That is in central america if you don't know lol a small country) and my carrier says since I got the phone over 6 months ago my warranty is over and I'll have to pay for the repair.

ROM : Stock I9300XXEMC2 (rooted with cf auto root)

Recovery : ClockworkMod Touch Recovery 6.0.3.1 (http://xdaforums.com/show....php?t=1719744)

Kernel : Stock (I haven't done anything else besides rooting and installing cmw)

I didn't leave my phone charging last night, and this morning I woke up to a dead phone, initially I thought that the battery had run out and tried to charge it but nothing happened, tried another charger as well as my charger on another phone so that's not the problem, can't get to recovery or download mode.

I did had the unusual freezes a couple of weeks ago when I was running CM 10.1 that's why upgraded to I9300XXEMC2 and everything was back to normal the phone was perfect until today.
[Galaxy S III General] andrewilley:
As this is a known manufacturing defect, you could try contacting your local Samsung offices and see if they can do anything for you (or the offices within the market that the phone was purchased in). Localised firmware doesn't help, but that can be got around.

However Samsung sadly seem to be one of those companies that (even though these devices are often all made in the same factories) will try to wriggle out of their moral responsibility to their users by sticking to the letter of their regional policies. It may save them a few dollars/pounds/euros/yen here and there, but it does their global brand image no good at all.

Andre
[Galaxy S III General] menelmar:
Some questions about flashing custom roms

Please excuse me, if answer was in this topic earlier.

I activated my SGS3 on December, 25th (2012), and then, phone was updated to SDS-safe stock 4.1.2 at the end of January (2013)

Now I'm going to flash custom ROM (MIUI on 4.1.1 base), trying to avoid SDS threat.

Am I planning it right?:

1) Gain the root

2) Flash custom kernel with SDS fix via Odin (i.e. Boeffla)

3) Install custom recovery with SDS fix

4) Flash ROM

Will it work safely together? AFAIK, the fix is contained in kernel and recovery, not in the ROM itself, so will flashing safe kernel and recovery make the further usage SDS-safe? :confused:
[Galaxy S III General] ereziel:
Yes, fix is in kernel and recovery not in the rom itself, but beware as roms contains a kernel also, just double check the rom too
[Galaxy S III General] joooe:
It's a voodoo thing.
[Galaxy S III General] andrewilley:
I think it must be a problem which prevents Google or XDA searches from working...

Andre
[Galaxy S III General] android addicts:
I like to know one information about the warranty claim.

I have I9300 with 2 year warranty. Now it almost left few weeks. I have an SDS Galaxy S3. Its firmware is I9300XXEMC2 (Android 4.1.2). Rooted and installed official CWM touch recovery and installed Googy max kernel. My binary counter automatically resets using Tingle away app.

I like to know, if my phone sudden death, can Samsung identify I have a modified firmware? Will they replace another device for me?

Thanks!
[Galaxy S III General] Mar-cel:
Hi, I have the XXEMC2 firmware and eMMC Check says:

Type:VTU00M

Date:05/2012

Cid:15010056545530304df187233b375f8b

FwRev:0xf1

I'm safe if not what can I do?

Sorry, for my bad English :)
[Galaxy S III General] :
Already reply , hi !

you're safe
[Galaxy S III General] Frostik:
Yes. I claimed my S3 around 2 months ago and I got revision 0xf1 too. This chip is OK.
[Galaxy S III General] :
This chip is unsafe but the firmware you have it's ok for fix the bug.
[Galaxy S III General] Frostik:
tony84200, you are right. I had issues with 0xf1, although the firmware was supposed to bypass it, I think I used XXEMC2. I got 0xf7 from the service. I'm sorry for wrong post.
[Galaxy S III General] scottcwhite:
Going on 4 months now that anovo has had my phone and still debating wether they will fix it or not
[Galaxy S III General] darryl3736428:
Sent to Samsung Service Center in Plaza Low Yat, KL, Malaysia last Sunday.

Just received a call 30 minutes ago (11.00pm GMT +08:00), stating that my Motherboard fried. Won't tell me further information as Techinician went home.

Warranty ended in early June 2013... Now asking for RM600++ or around USD200 to fix..

ROM: Stock 4.1.2 (Forgotten which baseband)

Rooted

Triangle Away - ed
[Galaxy S III General] CSeb95:
delete
[Galaxy S III General] listas_fede:
What's Samsung say about this statement? I'm having this exact issue and haven't found anywhere on the net if Samsung acknowldges this side effect of their patch or they believe they fixed this problem once and for all.

I've just sent my phone in for warranty and they just "upgraded firmware to the latest version" (which, of course I had done prior to sending it in). I will have to get my phone back tomorrow from the shop, but I'm certain the problem will arise back, since I've already seen this.

Please, if anyone has any info on the status of this issue, let me know. It'll be useful information for my discussions with the tech guy at the shop tomorrow.

Thanks in advance.
[Galaxy S III General] Rob2222:
Hello.

No, Samsung never acknowledged this.

However, all Firmwares newer than March/April 2013 have a newer and better version of this fix/protection, where the phone should not freeze anymore.

So upgrade to the newest firmware now indeed can solve the freezing issues, too.

BR

Rob
[Galaxy S III General] chrizhaynes:
Few weeks left? Hows that s3 on been out 14 months so that's 10 months left. Thats if you got it on release
[Galaxy S III General] android addicts:
Ops! I think you have misunderstand it. I mentioned, I have purchases it few weeks ago. :D not the phone release date.
[Galaxy S III General] jshashwat93:
I never updated to the bootloader which might have the fix. I am on CM 10.1 which has the kernel with the fix and also have Philz Recovery with the fix. So is it advisable for me to flash a new Sammy ROM for the bootloader upgrade and flash back CM 10.1 or is it fine?
[Galaxy S III General] chs4326:
I am a bit confused as no dates are provided in the 1st post.

My Kernel version is: 3.0.31-171637 se.infra@SEP-100 #1 Tue Feb 19 16:06:59 KST 2013

Build number is Omega v44.4 - XXUFMB3

Bootloader is I19300XXEMA2

I have the VTU00M 0xf1 chip. Need I worry?
[Galaxy S III General] jj92942000:
I take it v44.4 is based on 4.2.x, cuz I have 43.6.1 based on 4.1.2. I'd update to latest 46.1 no wipe, suggest siyah kernel and PhilZTouch recovery then you're totally covered.
[Galaxy S III General] chs4326:
Hmmm... Tried that but Omega 46.1 caused so many freezes and lags that I feared the phone was about to be bricked. Random freezes which resulted in eventually not being able to have the backcase on, cause I was removing the battery so often. That's the reason I found this thread in the first place. It was a challenge to revert back to v44.4 - and this did not remove the lags completely. A lot better, but still had to remove the battery occasionally. After 4 times this afternoon, I had enough and now I'm back on stock (unrooted) and we will see how it goes. So far it has been 6 hours without no problems. Do not install Omega 46.1. I have no idea why this happened to me, but I wouldn't risk it. Am not the only one who has installed Omega 46.1 and gotten this problem. I do have the "insane chip" perhaps it's related, I'm not very informed about these issues. Possibly something from Omega 46.1 stuck with me, I know that the baseband version in "About device" was too new to be Omega v44.4. But didn't bother to look into it further as I feared the phone would brick after nearly 100 restarts over the last few days. Restored an old nandroid backup if it matters. Anyway to sum up, it appears as if beeing unrooted on stock has removed the lags and freezes completely, and Omega rom 46.1 appears to be absolute crap.