yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] sgsboyo:
I've been having to reset my phone by long-holding power like that for days now. Maybe it's nothing to do with SDS after all, and maybe it's just faulty firmware or something? Mind you, having said that, using eMMC check on my phone it confirms I've got the VTU00M FwRev: 0xf1 chip...
[Galaxy S III General] krivinash:
did you flash the new perseus kernel?
[Galaxy S III General] Rob2222:
No, as I said, I am on complete stock (but rooted with cf-auto-root) XXELLA firmware. ROM+Kernel+BL

Would like to know, if other stock XXELLA users than sgsboyo and me also get random freezes now SINCE using XXELLA?!

As I said, I never had an freeze before. But we will see.

BR

Robert
[Galaxy S III General] DJ Palmis:
I found a data sheet of an old (4.3) Samsung NAND.

Commands are quite the same..

So what they do is:

-read SMART data (every time?!)

-If it runs on a board with a NAND with the infamous firmware they run mmc_start_movi_operation()

-This Function seems to "enter in smart mode" and then they "erase" some memory range of NAND.

That is the strange thing: They erase for exampre from 0x00040300 to 0x4A03B510.. But then again from 0x00040304 to 0x28004790!

And so on.

My hope is that they resets some error counter in the NAND registers.

And so I'm optimistic: There are no "strange" workaround!

Maybe error counter grows up with no/wrong reason!

We only have to know what 0x10210000 command means in the MMC4.4..

But It's quite easy to understand that they enter in the SMART mode..

Post Scriptum: Well I have the infamous NAND/fw..
[Galaxy S III General] skivnit:
He doesn't need to flash perseus as the ella kernel has the fix inside

Swyped from another galaxy
[Galaxy S III General] kosovito:
Im exactly the same situation.

Stock with cf-auto-root, no problem here.

CF-Auto-Root is fine right?
[Galaxy S III General] vadonka:
Thanks!

I really dont have time currently to dig up to the kernel source... i just want a reliable phone right now :)

currently i always have a backup phone in my pocket just in case...
[Galaxy S III General] krivinash:
how do you understand this sentence that Andrei wrote about Perseus kernel : "Kernels >v31 and beyond stock LLA are now the only truly protected ones". ?

after readinig it a 100 times , I ve decided to flash new kernel over the stock ella. :fingers-crossed:

cheers mate!
[Galaxy S III General] qazibasit:
I use the blackberry charger its low ampere charger takes long to charge but keeps the battery healthy and no overcharge in the sleeping hours.
[Galaxy S III General] bitubo:
ok thx

so i don't flash bootloader :)

but about a Perseus Kernel, this Kernel can read SDcard with Exfat ?
[Galaxy S III General] DonHuan:
Sure. No problems here.
[Galaxy S III General] kaiur:
I understood: "v31 and beyond , Stock ELLA are now the only...." So you can flash only ELLA if you want...

But right now there more kernels that contains the fix.
[Galaxy S III General] krivinash:
that is yesturdays sentence. there are few more kernels today. :good:
[Galaxy S III General] bitubo:
:good: cool
[Galaxy S III General] Bigben38:
So now the fix seems good but my question is really simple : is my phone is damaged and could dies earlier because of that issue which run in my phone during 3 months?

Thank you so much for your answer.
[Galaxy S III General] osbazoka:
XXELLA doesn't solve SD

After installing the latest update form samsung "XXELLA" united Kingdom BTU, but I couldn't choose the BTU and it'd installed withthe SER version............it worked fine for about two days with wonderful battery usage, but suddenly it refused to boot after a shut down by a complete battery drainage. first I thought it's a charging issue but after charging for some time, the problem persists, it kept trying to boot with the samsung logo and model No, but with no use. I wiped the cash from the BL, but it didn't boot too, so I had to wipe the data "factory reset" then it booted again after several attempts.

I guess the "XXELLA" with the new BL doesn't solve the SD issue.
[Galaxy S III General] Scarface1991:
So many people ask about is this safe or is that safe, stick to what developers say and read a few pages back:

So all ELLA/4/etc Firmwares with Stock Kernel should be safe but of course nothing guaranteed because the devs think that those firmwares have the fix already applied. Why do that think that way?

Here:

If I`m understanding correctly they are not absolutely sure if what Samsung has released in Update7 is also included in the XXELLA/4/etc Firmwares by default.

So I think that the safest bet is to flash a Kernel that is update7 based, like Perseus for example.

And again the bootloader has nothing to do with the SDS.
[Galaxy S III General] wooptarik:
If your phone is still alive & working, how come this sd?
[Galaxy S III General] sgsboyo:
I've flashed what was stock I9300XXELLA with the perseus kernel now, and for the moment it seems better (hasn't crashed since that flash).

Have now also rooted and various other things.

Dammit, if my phone's gonna pack-in anyway I may as well experiment a bit with it first!
[Galaxy S III General] Scarface1991:
I think people are getting paranoid. Every freeze or random reboot is now for people directly connected to the SDS which is bullcrap. Like Entropy512 said, there is no way to find out if it`s going to happen or not. Some people report sudden performance drops before it happens but that`s it.

Best way is to flash a safe Kernel and that`s it.
[Galaxy S III General] vadonka:
the short answer is no.

if your phone working fine currently and you dont have any strange symptoms what can be predict any crc error, then your nand store was not damaged.

---------- Post added at 10:59 PM ---------- Previous post was at 10:55 PM ----------

the freeze and reboots may predict (or may not) crc error what can be a sign that the nand storage is already damaged but it is still working.

but this symptoms not neccessary connected to the SDS. it may happen that the nand storage will damage after too much reflash or any power issue.

the problem is a nand storage is not act like a magnetic drive, what is dying slowly producing more and more bad sectors. the nand storage once is damaged it will die completely very soon.

one thing is certain, if you experience random freeze and reboots save all your data and do a full wipe. most of the time the full wipe will solve the lag/freeze/reboot issue beacuse this problem rarely caused by hw error.

if everybody will use the stock clean rom after a full wipe, the SDS will happen without any warning.

this slowing issues is probably independent from the SDS main reason.
[Galaxy S III General] Isadora:
No freezes for me since flashing XXELLA - everything stock and also using cf-auto root
[Galaxy S III General] Bigben38:
Very very good news. Thank you for your prompt answer.
[Galaxy S III General] Scarface1991:
Yes correct it can predict the SDS but some people had random freezes on the ELLA firmware with the Stock Kernel and now they are claiming that the fix is not working which can be confusing for some people. Fact is that so far there was no documented case where a I9300 died which had the stock ELLA firmware with stock kernel installed and I really hope it stays that way.
[Galaxy S III General] Bigben38:
Not any official news from samsung ?
[Galaxy S III General] vadonka:
no nothing, just rumors and speculations
[Galaxy S III General] artesea:
Mine didn't die on the ELLA kernel, however it failed to do much else. It crashed several times including during the Google sign-in on initial boot (had also factory reset). In the end I rolled back to an older firmware (and so an older kernel), which at least got me back in to the phone. However later in the day the phone finally locked up.

Pretty sure the phone had reached a point of no return around 2 weeks before.
[Galaxy S III General] Bigben38:
Not really serious from Samsung....
[Galaxy S III General] osbazoka:
It depend on how do you define SD...I considered it a sudden fail in the system causing loss of data......some people couldn't reach download or BL and ran for the warranty, others like me, after several attempts reached the BL and could finally do a reset to get the phone back from death.

plz check this http://xdaforums.com/showthread.php?t=2089302&page=5
[Galaxy S III General] AaronMichael:
Guys, I got a quick question. Someone at the CM10.1 thread pointed out something that makes a bit of sense. Now with the kernel fix and all, what about the wear that the NAND has already experienced? Before the software fix it would've gone through few months of torture depending when you bought the device.

Is this something to be concerned about?

Sent from my GT-I9300
[Galaxy S III General] tntgdh:
And that is why i flashed Perseus here. Better be safe than sorry. ... if washing my hair with my cat's piss could save my precious phone. .... man.... bring that cat !!!!
[Galaxy S III General] cristian274:
Lol same as my feeling :laugh: . Btw, it is apparently that perseus is safer than XELLA stock kernel since there was a man experience what we called first sign of SDS when using stock kernel as i've seen in few previous pages
[Galaxy S III General] vadonka:
this whole sh*t sounds like you buy a fancy sport car with an engine what have a serious issue, what can be cause the car may stopped in the middle of nowhere and you may even eat bugs for prevent that.

this is horrible what the samy doing, i can understand if this issue affect some low end cheap model, but not. this is happening with the flagship model. this is more than shame.

my first android phone was a motorola, i was totally regret that i was bought that phone. i was said never again motorola!

then i buy an LG phone. same as before, sh*t software, zero support. never again lg!

then i buy the galaxy S3. this phone was a great phone until now...

motorola, lg both of a mid-range company, but i was thinking until now the samsung is one of the high-end company.

my next phone probably a nexus. maybe the google reference phone not have such issue...i had enough of this.

ps.: i dont care what sh*t some android mobile phone there is no chance that i will buy any apple products! ever!

i hate apple more than anything :rolleyes:
[Galaxy S III General] drakester09:
All devices have issues, you'd better read a lot in the respective forums before committing to a model.

Unfortunately this issue presented itself after quite some time, I was lucky enough to get it until december and did not experience any issue whatsoever.

My girlfriend has a LG Optimus 4X HD, which has a locked bootloader but much better (IMHO) stock software. At least it feels like genuine ICS.

However the device still hasn't been updated to JB, and the situation looks grim.

The grass might seem greener in other pastures... but it might not be as green as it looks.

I'd wait to see what comes in the pipeline this year.

But remember... Samsung has s**t quality control when it comes to eMMCs. Better watch out and don't get a 16GB :P
[Galaxy S III General] guitahero:
Dear Xda friends

I am not a complete noob and I am posting this since my phone fits some criteria that might shed some light in case it dies.

I have a galaxy s3 since june 21th and just completed 202 days of perfect usage and functioning. I was afraid of device dying and after reading about the new XELLA kernel i have flashed ONLY the stock kernel from the Luxemburg firmware downloaded from the sammobile.

I used the Mobile Odin so there was no bootloader update as well radio/baseband.

I have the apparently faulty chip with the 0xf1 revision and I used the built in bad blocks check tool in the "eMMC check" app 3 times to see if I could force some trouble with the older kernel; there was no hanging or freezing.

So, if my phone dies we might think that this new ELLA kernel is not enough to prevent SDS, or that my phone was about to die even though having no issues so far.
[Galaxy S III General] Entropy512:
Or maybe you're just clueless... If your problems started when you ran your battery down to nothing, and, more importantly, you eventually got your device working again which makes it blatantly obvious you are NOT experiencing the problem discussed in this thread.

THE PROBLEMS YOU HAD WERE COMPLETELY UNRELATED TO THIS ISSUE. STOP BLAMING THINGS THAT ARE YOUR OWN DAMN FAULT LIKE RUNNING THE BATTERY DOWN UNTIL THE PROTECTION CIRCUIT TRIPS (unclean shutdowns can corrupt the filesystem requiring a wipe...) ON SOMEONE ELSE.
[Galaxy S III General] pickandwhammy:
:good: Whatareply :silly:
[Galaxy S III General] erwingle:
Greetings from the Philippines. I'm attaching a screenshot using eMMc app of my S3. Am i safe and need not to worry?
[Galaxy S III General] nebelriss:
It happend 2 week ago. Left my s3 on the table without touching it for a while. I took the phone and it was dead. Couldn't start or even charge it. I was running the latest nightly cm10 with stock kernel. It was build in korea and stock battery.

My phone was from the first charge, bought it on release.

I brought it to my carrier and they send it to repair. I is now repaired and I will get it back in a few days. In the online repair log they wrote that they hat to replace a part of the phone, but didn't specify which one, I will ask when I get it back. And they repaired it under warranty.

Ah, I don't know if its related but I hat a loose connection on my headphone jack.
[Galaxy S III General] Entropy512:
S2 is designed for a 1650 mAh battery, and the charger chip is fundamentally limited to 650 mA.

N7000 has a 2100 battery, and it's charger chip is SUPPOSED to go up to 1A. (Samsung ****ed up though and left a 700 or 800 mA current limiter still engaged).

Most other manufacturers charge at faster than C/2 rates, so 650 mA on a 1650 mAh battery is slow (especially since the device's operating current comes out of that 650 budget), and 900 mA on a 2100 mAh battery is a medium rate (again, device operating power comes out of that 900 mA budget.)

The descriptions from everyone sound like a weak solder joint somewhere to me.
[Galaxy S III General] spamtrash:
You could be right. One almost common symptom - overheating before the death - can result from that as well
[Galaxy S III General] bligui:
Well Samsung is quick about this problem it was supposed to be 4-8 weeks for an answer but my provider just called me that my replacement phone is ready and I got upgraded to an i9305
[Galaxy S III General] Obagleyfreer:
Not sure if it helps but here is a screenshot from i9305 I bought direct from Samsung.

It does have the red exclamation mark in the corner when rooted :)
[Galaxy S III General] jody2k:
Those who experiencing this problem who dont have warrenty you can always try to put the phone motherboard in a oven@+-100 degrees. This could fix some solder points
[Galaxy S III General] wshyang:
Are i9305 phones affected? Makes me wonder if I should just upgrade now.
[Galaxy S III General] InfX:
TBH, this is not the first time i am hearing about this kind of "fix". I seriously doubt anyone has got anything fixed by heating it up in the oven (technically - attempting a reflow in a home oven). Anyway, reflow temps are way beyond 100C.
[Galaxy S III General] Obagleyfreer:
Microwave works better in my opinion
[Galaxy S III General] InfX:
Well, at least putting a pcb in a normal oven does have a technical base after all. But mw gives you some special effects :)
[Galaxy S III General] CamMcArtney:
ahh samsung said the same as vodafone, due to cracked screen warranty is void even if its not the cause...

Wont be buying samsung again tbh, but still got 7 months on plan, if anyone thinks of a solution, would be grand haha
[Galaxy S III General] giuliano199:
Yeah! It got me too...

Rooted it yesterday with CF-Root and switched CWM for the standard Galaxy S3 Recovery to recieve OTA-Updates.

Everything was running well even Overclocking to 1.6Ghz with Stock Kernel (Not on Boot! Just temporary).

And today...

I read this whole Thread the last hours and it seems like it was random that this happend just after rooting.

What Happend: As I said I rooted and installed apps like App2SD and Beats Audio Drivers

In the evening it was at 5% so I plugged the Standard Cable in and played NOVA 3. After Half an hour (at full brightness) it was on 7%. I unplugged it accidently and plugged it in again then it wasn't loading properly anymore so I left it beside my bed and the next morning I tried to turn on the screen but nothing happend. No LED too. Took the Battery and the SD Card out and put the Battery back in and plugged it in but nothing. No Bootscreen. No Download Mode. No Recovery.

Gonna bring it back to the shop tomorrow. No Dowlnoad Mode = Root not recognizable

Haven't got a f*cking backup... -.- because Kies always crashed while trying

What ROM/Firmware: Jellybean 4.1.1 Latest Official (in Germany)

What kernel: Stock

OC or UV: temporary 1.6Ghz for Benchmark but put it back to 1.4

Where phone was made: ? Made by Samsung

Where battery was made: Made in Korea, Assembled in China

When it was bought: 2012-05-31

Color: Marble White

BTW: Maybe every device dies after some time and the ones bought early after the release are starting to die now... :rolleyes: :confused:
[Galaxy S III General] carlos_dz:
sudden dead

Battery was around 30% at night, plug it to stock wall charger with stock usb cable, was surprised that alarm didnt go off, power button didnt respond, home button either, took battery out put it in, no respond, plug it to computer.. no signs of live, tried another wall charger and usb cable also.

Firmware: flashed jelly bean via odin, first official release from poland./ didnt install any custom rom before or after.

everything else its stock.

bought it on june, mexico.

color: blue
[Galaxy S III General] kortelainen:
Made my first rooting and installed Omega custom rom three days ago. This afternoon I made a call, walked to pub, checked my phone and it was dead, had over 50% battery. Computer doesn't recognize phone anymore. Took phone to local dealer and tested with another battery and charged over fifteen minutes and no signs of life. Now it will ship to repair shop, lets hope it goes to guarantee.

What ROM/Firmware: Omega v34 Jelly Bean 4.1.2

What kernel: stock or what ever came with Omega

OC or UV: -

Where phone was made: No idea

Where battery was made: No idea

When it was bought: mid June in Finland

Color: Pebble blue
[Galaxy S III General] Rob2222:
I've fixed two nividia graphic cards with screen issues that way. But I used 160°C. Sure, it's not for long time use but one they were working for some month again. Then I've replaces them without trying again.

BR

Rob
[Galaxy S III General] spamtrash:
Hmmm.. amber Brown one shows HW Rev MP 1.400 Samsung changed something???

And one more... I think it may be interested for everyone who:

- rooted/flashed non-stock ROM;

- is an (un)happy owner of phone which died, but the download mode is available.

HERE is a thread which I'd think could be sticky or linked in the first post of this thread by @OP.
[Galaxy S III General] saadxe:
Got my SIII fixed in warranty, now it's back to life!

Just had a motherboard replacement, no further details given.

For details:

http://xdaforums.com/showthread.php?t=1994144
[Galaxy S III General] Juancito:
Samsung sucks

After 4 weeks, I received à phonecall from service center. Their report: no warranty due to fall, pressure damage. They put a photo of some scratches on the screen.

I had 3 options: 500€ for repairing, 50€ for getting my phone back (unrepaired), or getting my phone destroyed (free).

I'm furious, but cannot do anything.

I'm sure that those scratches were not cause of the sudden death of my phone. But what can I do to prove that? I went to bed with a working phone, and woke up with a dead phone.

SAMSUNG SUCKS!!!
[Galaxy S III General] sachilleas:
500 euros for repairing??? What?
[Galaxy S III General] Juancito:
Yep. Luckely I was sitting down when I heard the news...
[Galaxy S III General] pickandwhammy:
Quite the opposite - you're in the same boat. Flash patched kernel and recovery.

Note: These stats won't change after flashing. Quite obvious, since your hardware isn't changing, it's just the way it's being handled that is.
[Galaxy S III General] nckeong88:
I think you can find the answer if you will just read a few pages back.....
[Galaxy S III General] jeffnz:
you obviously haven't bothered reading too much on here have you. Your device is one of the ones at risk but since you haven't stated what you have flashed ie kernel, there is now way of telling.

A suggestion would be to read back a few pages and take note of entropy's comments as he has his head around it as much if not more than anyone.
[Galaxy S III General] T0xic4u:
Or just read this:

http://xdaforums.com/showthread.php?p=36499838

Taper di Tap with my S3 @178 days
[Galaxy S III General] fmtrx:
I do not understand the logic of some people here. They keep posting the screenshots and ask if they are safe.

I am seeing this every day...

Ok it is easier for you, i understand...You just make a question and wait.

Besides it is too boring to do a search or read some well written posts here from some experienced members in this thread and figure this out by yourself. Too much hassle.

It sucks doesn't it ? On the other hand, you just post and wait. Much better this way.huh? :cool:

But two things:

1) it may be easier for you but you make it harder for others when we have the thread flooded by a series of similar questions, where as the answers are already given again and again

in previous posts - sometimes 3-4 posts above(!).

2) How can you be sure for the validity of a random poster here who will answer to you for example: "you are safe mate, it is a good chip, no need to upgrade to Perseus or XELLA" .

I mean, you have to do some work on your own and study some facts that were

already

provided here by some

experienced

people that they know better and only then

you will know if you are safe or not. If you read some posts It is not hard to understand who knows what he is talking about and who does not have a clue.

You just cannot trust e.g. some user named nikyLauda1949 posting "you are good to go son". He may only know about race driving. :confused:
[Galaxy S III General] raoulserban:
Hello!

most likely a noob question , yet please understand that i tried to learn as much as possible about custom ROM/KERNEL etc

regarding this issue with the SDS. i went all stock/normal/counter0 with odin, than i flashed the latest ELLA.

i did not messed up with kernel or so, just custom recovery i used before getting on stock.

i would like to know if the ELLA ROM i flashed from sammobile has rewrote the kernel to the latest one(with he fix). i did not found the name on google.

i have this one http://xdaforums.com/attachment.php?attachmentid=1632829&stc=1&d=1357812098

i missunderstood something. when in stock, if i go into recovery menu and i use it a lot(clear cahe) is the eMMC not protected by the Kernel cause in recovery kernel isnt working! right?

wich custom recovery can i use wich has the fix for SDS. do i need root to flash it with odin. CF-auto root i understood isnt messing with kernels, does custom recovery?

if i use custom recovery i will have the red exclamation mark, can i remove it with triangle away again? i have the new bootloader cause i flashed ELLA. in this case i would like to know how to get on stock again.

Thank you in advance
[Galaxy S III General] pickandwhammy:
Dude, please read through the forums. And use search!
[Galaxy S III General] Haano:
Phils touch recovery v4.00-b4 has the SDS fix, You need to have a patched recovery to prevent SDS bricks in recovery, just to be safe.

With the new bootloader you will always have a red exclamation mark no matter what, Triangle away does not work with the new bootloader.

Search as there is a thread that shows you how to get back to old boot loader.

Guys i dont see the red exclamation mark even though ive flashed the new bootloader in odin as pda. Is there any way to confirm which one im on? ITs fine i see it now, so small!