yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] perry04:
I am on omega with XXELLA Kernel, am I Safe or will i need a updated recovery? Dont want to Flash other Firmware, so is the Kernel enough?

-Galaxy s3 with tapatalk-
[Galaxy S III General] Kjc99:
On Criskelo rom 4.1.1 my ex sd card started checking for errors every time I woke it then one day it fried so I dunno maybe the card or the S3

Galaxy S3

Omega Rom V36
[Galaxy S III General] STELIOSFAN:
That's strange. If you dial *#12580*369# is the HW rev. same on both phones?
[Galaxy S III General] WeedoBrT:
What happened: Phone, with 28% of battery, was left last night on charger. Today morning, I saw steady blue indicator light. Tried to turn on the screen- nothing. I held the power button, the indicator light went off. Since then its not turning on at all. I tried to leave it on charger, take the battery out. No signs of life :crying:

What ROM/Firmware: Omega 33.3

What kernel: Syiah kernel v 1.8

OC or UV: standard

Where phone was made: i dunno

Where battery was made: korea
[Galaxy S III General] Sstennizz:
Mine died this morning too.. Same symptoms, white version, stock rom, rooted, stock battery..

Going to have it fixed tomorrow. Was wondering one thing though.

I suppose a new mainboard would result in total loss of data right? Since the flash mem is on the mainboard? Or is there a way to retrieve the data before changing the board? Definitely slapping myself on the back of the head for leaving the nandroid backups on the internal mem. Phone was doing so good since I bought it, I didn't feel the need of downloading them to my laptop yet.. STUPIDSTUPIDSTUPID..
[Galaxy S III General] pedropac72:
So sorry. As long as I know there is no way to recovery data.

Enviado desde mi SGS3 reparado tras la Muerte Súbita usando Tapatalk
[Galaxy S III General] nailrik:
Mine died 2 days ago, can't believe so many experiencing same trouble.. Here's my story,

Galaxy S3 (international ver.)

16GB + 64GB sandisc

Bought in Indonesia on June'12

Rooted and using UK unbranded JB 4.1.1 stock rom(never flash any roms before)

Battery made in korea

Have around 150+apps inside (still had 2gb int & 30gb ext free storage)

Like usual monday morning, I went to work with fully charge S3(always leave it charging overnight). Played bit of puzzle game during work, browsing, social networks and stuff..used 3G for connection and around noon the last time I checked the phone, it was 59% power left. Then just left it inside my pocket and busy with work, around 3 o'clock I checked it and it was already dead. No sign of life whatsoever..no vibrate warning(battery down)..no LED flash..just black screen. Tried to pull out the battery..sim card..sd card..charged with USB to comp..to power source..used power pack...booting downloader..but nothing happen, black and perhaps bit warm. I don't have spare batt so can't confirm if it's the batt or the device itself.

Well..I'm going to take it to SSC on saturday, hopefully they can confirm what's the problem right away without waiting for days to know.
[Galaxy S III General] KickButts:
What happened: Went to bed, left phone on charge, woke to the green "fully charged" light, but no response to buttons. Pulled the battery to make it reboot, and now nothing. Neither download nor recovery modes, no charging light, nothing. Took it to TA and they replaced the motherboard. I will get it back tomorrow.

What ROM/Firmware: Leaked 4.1.2 from XDA.

What kernel: Stock

OV or UV: No

Where phone was made: Brazil

Where battery was made: Stock; no idea
[Galaxy S III General] drcursor:
Mine passed way this morning:

What happened: Today as I got home I noticed that my SGS3 had a blinking red light (or was it the blue one?) , tried turning the screen on...but it looked like it was frozen (but a little bit warmer than normal).

Took the battery out, put the battery back on, tried turning it on, and...nothing...

Connected it to the charger (original one) - no reaction.

It now looks completly dead.

I've tried connecting it do different chargers, different USB cables, directly to a PC, but neither the status light nor the screen react in any way.

I didn't flash any ROM for the last few months, and I didn't install anything new.

I think the phone just isn't charging (and I don't have any extra battery to try it out...)

What ROM/Firmware: Some official 4.1.x WWE

What kernel: Stock

OV or UV: No

Where phone was made: No idea

Where battery was made: Stock
[Galaxy S III General] spamtrash:
First one (unbranded): AP XXDLJ4, CP XXDLID, CSC: Unknown :D:D:D, RF Cal 2012.9.5, HW Rev. MP 1.100

Second, unbranded: AP: XXDLIH, CP:BWDLI1, CSC UDLI3, RF Cal: 2012.7.13, HW Rev. MP 1.100

Anyway, I should get next one on Monday or Tureday, as it will be amber brown - most recent???... as it presumably will be stock, I'll make OTA/KIES update, then I'll add siyah and then replace with speedmod... lets see how it will look like... (and NO, I'm not collecting S3's... yet ;) )
[Galaxy S III General] Mushyuk:
Mine Died today this afternoon at around 45% charged, left on bed flashing blue led indicator pressed all buttons no response removed battery and then nothing no life in phone.

Sim free from Carphone warehouse

Stock Rom Jelly bean from official update.

Rooted

No UV/OV

Kernal:Stock

No idea where made Stock Battery

Returned to CPW for repair upto 14 days.

Bought On release day.
[Galaxy S III General] spamtrash:
Guys, as most of you are unable to give the manufacturing date fir died phone or HW Revision value, can you add the infor when did you purchased the phone?
[Galaxy S III General] bligui:
I see most are June-July time frame, so I guess it has to do with early production dates at least for now.
[Galaxy S III General] servenaya:
$500 paper weight scare

My horror story started when my phone's battery died. I decided to turn of the phone and charge it so it would charge quicker. I plugged the phone and the battery charging animation came on and the red led also turned on. Later that night I woke up and saw that the green led was on meaning it was charged. So I turned it back on, and went back to sleep. When I woke up i did not see the green status light on (the phone was still plugged in). When i tried to wake the phone it did not respond, it seemed like it was bricked. My wife has a S3 so I took out my battery inserted her battery and the phone booted normally. I then believed the battery had just died, I tried charging the battery using her phone and mine and it didn't charge. When I got to work I asked a coworker who also has a S3. When I asked him to try and charge the damaged battery with his phone the battery started to charge. The battery was drained completely even though I had charged it all night. I charged it using my phone and now the battery works perfectly.

Ive noticed that when I charge my phone turned off some how I start to see glitches with the battery life. Since I then I've always charged my phone on and never had an issue again. Seems like the firmware on the motherboard which manages power off charging has issues. My recommendation would be charge your phone when its on. Do not charge your phone turned off.
[Galaxy S III General] jmap123:
The most IRRITATING thing that could happen

What happened: 5 Mins post leaving the office, I had 100 things to do on the way home in the car (mostly phone calls). Phone connected to Bluetooth kit, tried to make first call, took 3 mins to change from a frozen state then to phone rebooted. Took at least 5 mins the reboot then once rebooted, the handset had been reset to factory settings! This was only the start. I made about an hours worth of calls, got home and had dinner. Went to get my phone post meal and found it had hung on the boot page. From here, was up till 1:30am this morning trying to rectify then came to work and spent most of the day trying to rectify. Tried at least half dozen roms, PDA files, .pit files - you name it, ive tried it. Now that I have found this page, I feel slightly more comfortable that im not the only one in this basket. Off to Samsung tomorrow morning now...VERY unhappy

What ROM/Firmware: 4.0.4 International

What kernel: Stock

OV or UV: NA

Where phone was made: Veitnam

Where battery was made: Stock; Korea

What are other's doing with their handsets? Taking to Samsung? Is this the final solution?
[Galaxy S III General] PjotrFias:
For now it looks like that's the only solution.
[Galaxy S III General] bligui:
Got tired and bought a Galaxy Note just hope it doesn't commit suicide on me, this hasn't been one of the best experiences with a cellphone in my life. I paid well over 800 USD for the thing to die on me and now they say it might be 4-8 weeks to find out if they will do it on warranty. if not I shall move to who knows what brand.
[Galaxy S III General] jmap123:
Why wouldnt they cover under warranty? Because you flashed it?

I could understand if you burnt something out or over heated due to dialing up CPU speed/etc, but this has to be a known issue surely?!?!?!

Either way, we are all in the same boat. How are you finding the note in comparison to the S3 if you dont mind me asking?
[Galaxy S III General] bligui:
Well it most likely will but I can not wait 4-8 weeks but then again that is the way Latin America gets treated, the Note I have to say is quite a nice device and I am liking it a lot only thing is it won't fit on some of my dress pants but I can live with that compromise. Ahhh and the screen real estate uff that is just sweeeettttt.
[Galaxy S III General] CamMcArtney:
happened to me about 2 weeks ago, long story short i took mine into vodafone and trusty vodafone sent it away took a few weeks came back saying that it would cost $230 to fix, i said no, got it back and they clearly hadnt even taken a screw off the back (provided i had cracked the screen so i assume they blamed it on that) but either way proving that vodafone are useless as tits on a bull...

So I plan on taking it into samsung tomorrow, hopefully they dont try pin it on the screen either otherwise ill be stuck with my old nokia e71 till my plan runs out :/
[Galaxy S III General] PjotrFias:
Wait, is the screen even cracked?

Does it show anything when you charge it? You can prove that screen is OK then.

Over here, every phone suddenly wets itself when it comes to the service center. So its wise to take a picture of the water indicators before sending it to repairs.
[Galaxy S III General] pedropac72:
Where is the water indicator? The guy in the shop confirmed before sending that water indicator was okay. If you go to the shop I think is imperative to make the guy to make all checks before sending to avoid problems.

Enviado desde mi SGS3 reparado tras la Muerte Súbita usando Tapatalk
[Galaxy S III General] bala_gamer:
Don't bother about the recovery unless you are planning to flash some other rom. Hopefully all the existing recoveries will be updated soon and then you can flash those recoveries and consider updating your roms.

《posted from samsung rom》

---------- Post added at 11:41 AM ---------- Previous post was at 11:39 AM ----------

Its been mention again and again, all 0xf1 firmwares are prone to brick bug, so you have to flash the stock lla kernel or the pursues latest to stay safe.

《posted from samsung rom》
[Galaxy S III General] mjb:
No, VTU00M / 0xf1 is what matters. You are vulnerable.

You only need to get an updated recovery if you plan to use it for flashing or making nandroid backups/restores. For day to day usage of your S3, XXELLA should be fine.
[Galaxy S III General] BVG7981:
Hi

Hi guys... Long time reader (of this very scary thread) first time poster... :silly:

I bought my S3 back in July... So far its not given me troubles... Still seems to go strong. But this thread has made me a paranoid wreck...

I have not rooted the phone. Its still on the official JB 4.1.1 updated through Kies... I guess I am just not brave enough to fool around with it just yet... Its my first Android, you see... :)

Anyways. I came across this link in this thread...

ww.w.samsungupdate.com/android-how-to/new-update-fix-galaxy-s3-sudden-death-and-exynos-security-exploit

And it says - " You can update your Galaxy S3 via Samsung Kies (recommended method) by opening Kies and then Select Tools -> Select Firmware Upgrade and Initialization -> Enter Model “GT-I9300″ – >

Enter Serial “RF1C56VAJYF”

. This will initialize the update with the latest Android version."

Could someone tell me if its safe to use this serial number? My phone gives me a different serial number. When I tried it on Kies, it did show me that the LLA firmware was available. I live in Kuwait and its not been officially released here.

Thanks for your help... :)
[Galaxy S III General] iridaki:
eMMC app gives me: 05/2012

but checking via the SSID gives me: 2012/06/09.

So two different dates, but none of them is the internal firmware date, correct?
[Galaxy S III General] zoot1:
See..the kernel is handling the emmc when you are normally using the phone..i.e. day to day usage...

However when you boot into recovery mode or download mode..the kernel is not running..and the emmc is accessed by the recovery..so there is a chance of a brick if the recovery is an unpatched one..
[Galaxy S III General] koolshubh:
Well explained... (Y)
[Galaxy S III General] nckeong88:
Too bad for me the fix came 2 days late but glad that there is a fix now as the replacement is likely the same component.
[Galaxy S III General] Kjc99:
How do we know this XXELLA KERNEL IS Even the fix it sounds like a guessing game to me still after reading the last 50 or so pages plus people on official XXELLA including kernel have suffered sudden death

Galaxy S3

Omega Rom V36
[Galaxy S III General] r2001uk:
Still waiting for mine - a part was on order and it was received yesterday. I was kind of hoping they'd have done the repair yesterday too since it's been sat with them for some time now.

It's hard living without a phone, I thought it'd be ok but it's definitely becoming more and more inconvenient!

As it seems that the phones are coming back with the same cursed component, I think I'm going to sell up and get a Nexus 4 or Note 2. Although, is it true the Note 2's have the same risk?
[Galaxy S III General] -A-P-M-:
Most phones died over night after charging. Since there are many defective chargers, can this be related to a faulty charger? For example, I have my sgs3 for about 6 months and a few days ago charging became very slow (didnt charge fully after whole night). I used HTC's charger and charging is nornal again. Ive seen that many sgs3 owners got problems with charger. Can some faulty chargers start charging very skow and others give too much electricty which burns internals?
[Galaxy S III General] MATTHEWLONG:
Mine is back repaired after less than a week. Phew!.
[Galaxy S III General] Lagggi:
Mine is 7 months old and still alive although operates in 1.6ghz...
[Galaxy S III General] mjb:
The patch to the MMC driver discovered in the Update 7 sources released by Samsung performs a procedure that is nearly identical to the fix for another mmc firmware bug in a different samsung device.

The patch also includes some character strings which can be searched for in the binary kernel of XXELLA, as when code is compiled, strings are left as they are.

The kernel from the XXELLA firmware DOES include these strings, so it's probably safe to assume that the kernel includes the code that performs the in-RAM fix to the mmc firmware.

The fact that some people have reported that they've experienced SDS on the XXELLA ROM is interesting - none have confirmed 100% that they had the XXELLA kernel running (to the best of my knowledge). This means that for some reason they may have been running another kernel that doesn't have the patch.
[Galaxy S III General] STELIOSFAN:
Can you please point out these posts? I can't seem to find any people with XXELLA KERNEL who had SDS

We have NOTHING TO LOOSE by flashing XXELLA stock kernel, or custom kernel with the SDS fix.
[Galaxy S III General] BVG7981:
Help?

Help? Anyone? :cyclops:
[Galaxy S III General] vadonka:
what custom kernel have SDS fix? i dont hear about that nothing.
[Galaxy S III General] krivinash:
i dont understand: when you flash stock rom, in this case XXELLA, you AUTOMATICLY have XXELLA kernel or not?

If you dont have, you must flash tne new perseus kernel with the patch!

plesae, confirme me that!!
[Galaxy S III General] STELIOSFAN:
As far as I know

Perseus

Yank Kernel v3.0a

Boeffla-Kernel 2.6-alpha1

maybe there are other kernels as well, but these are the ones I know

What do you mean by stock? Flash it from where? Generally, if you d/l the stock FW and flash it then this contains everything. Bootloader, kernel etc.
[Galaxy S III General] drraptor:
This post will help http://xdaforums.com/showthread.php?p=36469480
[Galaxy S III General] krivinash:
stock LLA rom, for UK's market, downloaded from sammobile, on first page XDA topic with stock roms.

flashed with pc Odin.

how can I check my kernel version? only in settings-about device?

thanks man!
[Galaxy S III General] kofiaa:
Yes it should work. But haven't you been reading anything from this thread? We are discussing the sudden death fix.
[Galaxy S III General] Kjc99:
Sorry spoke to soon I went back and read the Sudden death reported was someone who flashed only LLA bootloader not kernel I truly hope this works

CAN SOMEONE CONFIRM IM ON THE RIGHT KERNEL PLZ

Galaxy S3

Omega Rom V36
[Galaxy S III General] krivinash:
I have to point this out :

Perseus alpha31 (09/01):

....Nobody was secure from a smart exploiter up until then, SuperCurios or Chainfire's software fixes are also just patching a single hole in what is a Swiss cheese. Kernels >v31 and beyond stock LLA are now the only truly protected ones.

Samsung's fix for the sudden death syndrome (SDS) included. It is caused by eMMC failure on phones with VTU00M internal memory chips with revision 0xF1. You can check your phone with the "eMMC Brickbug Check" in the Play Store (Ignore the message if it says you're not affected, the type and revision is what matters). The patch is a firmware soft-patch that is applied on every boot and MMC resume, it is not a permanent fix. You will need to stay forever on kernels which include the patch, this also will include updated recoveries.

in my opinion, only Perseus + LLA is FINAL SOLUTION for our problems!
[Galaxy S III General] BVG7981:
Yes... I get that... The link I was talking about is also supposed to fix the sudden death bug...

I was just wondering how safe it is for multiple people to use the same serial number that forces Kies to initialize the LLE firmware...
[Galaxy S III General] kofiaa:
So far there have been no complaints, try entering your serial and see if you'll get the update. If you're in UK and on btu you should get the update.
[Galaxy S III General] mcbyte_it:
appears that I am at risk, but why ?!

I read the title of this thread since I bought my galaxy s3, but not having ever had problems, never went into details.

now with the new perseus kernel 31.2, which fixes SDS and exonys bu, I found that he mentioned what phone with what eMMC chipset are at risk, and my device DOES use the mentioned chipset (VTU00M. rev 0xF1).

Since day 1 I rooted and installed custom ROM's, and most of the time I use Siyah kernels (now 1.8.6), and never had blocking issues, is it only time before I suffer from this issues, or just by luck?

I am going to put perseus kernel soon.
[Galaxy S III General] skivnit:
I'm still confused. Some posts say lla kernel is safe others say you need Perseus. So which one is it
[Galaxy S III General] aghazi:
Just use the method 2 in following post and you will be fine. Use CMW recovery. Twrp did not work for me. I successfully downgraded from new bootloader using this method.

http://xdaforums.com/showthread.php?t=2083860
[Galaxy S III General] dimi22:
You have the exact same kernel as i do. I flashed the latest updated trought kies :good:
[Galaxy S III General] Amos91:
Phone ready to collect today (broke on 27th December). Will I be stuck with the new bootloader? (UK phone).
[Galaxy S III General] zoot1:
It is very simple..the latest lla kernel has a code which fixes this issue..

Andreilux went through the published kernel sources..which in this case is Update 7 in this case..and found the code..

He merged this code with his kernel and published the Perseus kernel..

He submitted this patch to gerrit...so now other kernel developers can include this code in their custom kernels..
[Galaxy S III General] dimi22:
is I9300XXELL5 the same as XELLA with the sds fix ?
[Galaxy S III General] zscomp:
If i understood it correctly, we have an assumption? that because similar code is implemented in kernels for similar problems in other samsung phones, so that means we have the same problem in S3.

If this is true then all or almost all 16GB phones are affected, as i didnt saw a phone with different emmc.(maybe some new phones have newer revision?)

We are talking then for millions S3's that are going to die?

Maybe this code then doesnt have to do anything with the "SDS issue" and is more of a precaution or even testing trying to figure out the problem from Samsung?
[Galaxy S III General] zoot1:
If you go through Andreilux's post..this code only gets activated when the reference to a particular internal eMMC date is matched..hence even though there are millions of 16GB SGS3's not all eMMCs will have that internal date...

Hence, this code affects only a sub segment of those phone which have a particular internal date..
[Galaxy S III General] blublub:
Sorry for me being an idiot but how can software prevent a hardware malfunction due to bad quality control of mmc chips.

All I can understand is that software takes care of wear levels using the chips in correct/alternate order and can therefore prolong the failure but how can it be prevent when already having defective mmc chips from the start?

Sent from Mobile, might include T9 typos :)
[Galaxy S III General] krivinash:
I think that it's combination is the solution.

according to this from 1st post:

...Kernels >v31 and beyond stock LLA are now the only truly protected ones.

Can someone confirm this?
[Galaxy S III General] Kjc99:
Sorry one more question for you guys... And you all have been very helpful is the cwm zip file to downgrade bootloader safe? And also is it recommended or should I stick with the new one and wait for a way to reset count and fix (!)

Galaxy S3

Omega Rom V36
[Galaxy S III General] Nees3:
Have you searched for it in older kernels? Why wouldn't that string appear also in those? If it does, then this means nothing.
[Galaxy S III General] Animor:
There is still no explanation to why users with XXELLA rom had suffered from SDS.

Two examples I've found:

http://xdaforums.com/showthread.php?p=36387849#post36387849

http://xdaforums.com/showthread.php?t=2089302

Pethaps this fix only suppose to fix this issue, but failes to do so. Perhaps it was "too late" for those users. I don't know... What do you think?
[Galaxy S III General] drraptor:
Thanks for explanation, I did read Andreilux's reference to an internal date, but I'm confused. Did he meant, SDS affects only a select batch of VT00M fx01 chips ?:confused:
[Galaxy S III General] kaiur:
First one had Siyah Kernell
[Galaxy S III General] mjb:
No, because I don't have copies handy. But good point. I'll see if I can find a couple and check.
[Galaxy S III General] qavro:
Yes, Andrei said the fix addresses just a emmc lot with a very specific date.

The real question here is: WHEN (if any) Samsung will announce officially that this last release (7) is indeed the SDS fix. If this will not happen and more SDS fill follow even with the said fix, we can just assume that the SDS might actually have more than one reason to occur.

Just my 2 cents.
[Galaxy S III General] drraptor:
Did they fixed the super brick bug in 4.0.4 galaxy S2:rolleyes:
[Galaxy S III General] cristian274:
So let's make this clear, it means that we just need to flash one of these 2 kernels (Perseus or XELLA stock kernel) to fix SDS? Thanks.
[Galaxy S III General] qavro:
But i am not saying the fix is not working! I am saying that is a bit too soon for everybody to start jumping around like happy rabbits. We have to wait and see.