yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] danarama:
By using your intelligence! All rom threads have dates in title :o
[Galaxy S III General] sharif swm:
Help please

unfortunately, my friend's S3 had sudden death. and he couldn't took it to guarantee.

is there any solution to this problem with out going to samsung or buying new motherboard :( :(

HELP PLEASE
[Galaxy S III General] sherlock5545:
If it's dead, there's no other solution.

Sent from my GT-I9300
[Galaxy S III General] ra3or:
nobody tried so far to replace the faulty memory chip on the motherboard?
[Galaxy S III General] danarama:
It can be done but you need tools and skills.
[Galaxy S III General] sharif swm:
What about buying new mother board?

How it coasts?!
[Galaxy S III General] danarama:
Expensive. £150+ (GBP)
[Galaxy S III General] sharif swm:
And is not there any any way to repair mother board or turn on the phone :(((
[Galaxy S III General] danarama:
turn on - no, its dead.

repair - see post above your first post today. Answered immediately before you posted
[Galaxy S III General] icedfirefly:
It´s my S3 in danger?

Hello guys.

I just bought an S3 and then i read about the sudden death issue :(

I installed the eMMC check and got the following message:

Chip eMMC

Type: VTU00M

Date 07/2012

CID: 150100565 etc etc etc

FwRev: 0xf1

SGS3 Sudden Death

Yes. Chip in danger.

Then i did the test and got the following:

Congratulations, passed revision.

591s.

(14,7 GB) 25,5 MB/s

My android version is 4.1.2

Baseband

I9300UBELL1

Kernel version

3.0.31-789635

se.infra@SEP-88 #1

SMP PREEMPT Fri Jan 25 00:23:01 KST

2013

I´m pretty lost, could someone help me to know if i´m at risk and should update something or if it´s ok.

Thanks in advance!!!
[Galaxy S III General] danarama:
Enough said! ;)

Make sure you are covered in post 1.
[Galaxy S III General] icedfirefly:
Hi rootSU.

That´s the thing, i bought it used, and it got the official release (stock) and it´s rooted.

But i´m not 100% sure if they did or did not change to a custom kernel or recovery

In post 1 said:

Stock:

All 4.1.2 official releases (stock) include a Kernel, bootloader and recovery with the Update 7 "Fixes" (or newer) applied. If you have 4.1.2, officially consider yourself "Safe".***

Stock (but rooted):

If you rooted a 4.1.2 stock ROM, you will still be safe, however - if you changed to a custom kernel or recovery, you need to look at the below custom sections to ensure your kernel or recovery are listed as safe.

The below official kernels were tested, but we no longer need to test. All 4.1.2 (stock) kernels and newer have fixes.

XXELKC

XXELL1

XXELL4

XXELL5

XXELL6

XXELLA

XXELLB

XXELLC

So, the info in my cell is:

Baseband

I9300UBELL1

Kernel version

3.0.31-789635

se.infra@SEP-88 #1

SMP PREEMPT Fri Jan 25 00:23:01 KST

I dont know if i´m covered or not.

I´m sorry for asking again, but it´s just not clear to me how to check if my cel is at risk or not.

I´m a bit new to all this and i´m trying to understand it, but i don´t want my cell to fail in the meanwhile.

And it said at the beggining that stock kernels are safe and then talk about a fix1 and fix2 and i dont understand if i have to manually apply some kind of fix or not...

Thanks!
[Galaxy S III General] danarama:
Then flash a safe one yourself.

The fixes are in the safe kernels. We cant tell if your kernel has been changed or not, so its best to flash one you know is safe.
[Galaxy S III General] ginzo:
I'm sorry if it was already explained but I didn't find any info on first page..

I'm using philz touch (latest) with a latest a 4.2.2 leaked em7.

4.2.2 stock kernel has the sds fix or not?

Yesterday night, while opening chrome browser the phone got blocked on loading page then after 30sec I've noticed 3 vibrations. . I pushed power button to restart my phone again.. no other issues till now.. that was sds synthom? :confused:

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III General] danarama:
It is covered in post 1.
[Galaxy S III General] rumpelst:
rootSu I admire your patience :) I will try not to abuse it with my question... Why is reseting flash counter so important. I estimate that in case of hardware problem I would be able to go back to ics bootloader and reset flash counter before I will give it to service. In case of half sudden death I'm out of luck cause service would be able to refuse warranty whatever I did or not with my device. What is the other differences between ics and jb bootloader Is there any beside a fix in micro kernel of download mode

..?

Wysyłane z mojego GT-I9300 za pomocą Tapatalk 2
[Galaxy S III General] kadopt:
If case of hardware failure you may not be able to flash anything and they may still be able to check your custom binary flash counter. Actually if you have hardware failure how do you reset your counter if your device does not load the os to run triangle away?

If you don't care about warranty use latest bootloader but if you do use ics bootloader like me. New bootloader flags your device with a red exclamation mark in case of custom recovery or by having flashed custom software and always gives at least 1 binary count in that case, the old does not. Also the bootloader being safe or not cannot be confirmed because there's no source code to check it out.
[Galaxy S III General] rumpelst:
My point is that in case of hardware failure as a screen problem for example, you lost contact with os which is in good condition ready to bee read by service man. In that case red flag and counter does not matter cause they will see CM or other custom rom. I know thats obvious but how many failures beside sudden death ends with memory error which means true brick not a system without interface. The only thing is that red mark, flash counter are on boot (partition ?) so much more chanse to be read than OS in case of hardware problem ?

Wysyłane z mojego GT-I9300 za pomocą Tapatalk 2
[Galaxy S III General] danarama:
They can read you counter if;

You're in a boot loop

You have half sds

You have no screen

You cannot reset your flash counter if;

You are in a boot loop

You have half sds

Touch and AMOLED screen malfunction

So you see, its important to stay on top of your flash counter if you expect a warranty repair

If you can flash a stock ROM that's great.

If your reset is already done :

Half sds - no further action

Full sds - no further action

AMOLED failure - flash stock (MHL)

Touch failure - flash stock (OTG mouse / mobile Odib)

USB socket failure - flash stock mobile Odin

It can't help if combination of faults:

Touch and AMOLED failure (cannot control and output)

USB and bootloop

However there's still a chance that they wont boot into recovery or android.

So why risk it?
[Galaxy S III General] rumpelst:
Thank You. I do not mind to risk a warranty and I will downgrade bootloader I ask cause to know better what is the risk that service would be able to check counter and not beeing able to identify what os was running on device.. So save for me will be downgrade bootloader with odin and after that l'd be able to accomplish root acces and flash recovery without pc Odin and download mode..?

Wysyłane z mojego GT-I9300 za pomocą Tapatalk 2
[Galaxy S III General] sherlock5545:
You can just root, then flash ICS bootloader. From this point on, never use Download Mode again. To flash, either use recovery packages or use Mobile Odin. That should cover all your needs.

Sent from my GT-I9300
[Galaxy S III General] .NetRolller 3D:
Doesn't half-SDS always show flash count=0, current binary=official, device status=custom, no matter what the actual values were?
[Galaxy S III General] danarama:
I cannot guarantee that and I'm not sure that it's relevant either. Resetting the flash counter is mainly for other issues, outside of the scope of SDS
[Galaxy S III General] shouk_1987:
faid ersihow

Following thread
[Galaxy S III General] eng.helewa:
hello,

my galaxy s3 i9300 can not boot up it continuously restarts.

i can not access recovery when hold vol.up + home + power it takes me to samsung logo with little red exclamation mark in the top left corner and then restarts

I cannot flash any rom thought odin. Just flashed recovery :(

what to do please ?
[Galaxy S III General] danarama:
Boot to download mode (vol down + power + home) and let me know exactly what the screen says.
[Galaxy S III General] eng.helewa:
ODIN MODE

PRODUCT NAME: GT-I9300

CUSTOM BINARY DOWNLOAD: YES (5 counts)

CURRENT BINARY: Custom

SYSTEM STATUS: Custom

Downloading..
[Galaxy S III General] danarama:
OK the "good news" is you don't have "Half SDS" because usually the product name is blank.

I would first try to flash a stock ROM via ODIN
[Galaxy S III General] eng.helewa:
i tried to flash the current rom via odin

I9300XXELLB_I9300OJVELL3_I9300XXELLA_HOME.tar.md5

this is the result

<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> tz.img
<ID:0/005> NAND Write Start!!
<ID:0/005> sboot.bin
<ID:0/005> system.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy S III General] danarama:
I think your internal memory is screwed but not by sds. Will probably need a repair from a service Centre but your flash counter will possibly cause issues. Might be worth creating your own support thread just in case someone else knows a fix.
[Galaxy S III General] eng.helewa:
thank you where should i create my thread?

thanks again :)
[Galaxy S III General] danarama:
Q&a
[Galaxy S III General] android addicts:
Could anyone please tell me how do I check my boot loader version?
[Galaxy S III General] danarama:
Theres an app somewhere but what stock ROM were you on when you rooted? Because that is also your answer ;)
[Galaxy S III General] luis4ever:
I checked the version of my eMMC and I have the faulty one. But I dont want to keep on stock so... If I flash any custom rom based on 4.1.2(let's say ARHD for example), flash a kernel listed on OP or keep stock from 4.1.2 and have TWRP or Philz recovery am i protected?
[Galaxy S III General] danarama:
Its all in post 1, so why ask?
[Galaxy S III General] luis4ever:
I just want to be sure and ready to go.
[Galaxy S III General] danarama:
Makes sense. Answer in post 1
[Galaxy S III General] android addicts:
Previously I have rooted and installed CWM recovery and after that installed several custom kernels, CM10.1 and Android Revolution HD (4.2.2 leaked version). But now I'm reset the flash counter, unrooted and installed Android 4.1.2 jelly bean I9300XXEMC2_I9300ODDEMC1_SLK firmware using PC ODIN.
[Galaxy S III General] danarama:
You said a lot of words, none of which answered my question. Ah well, guess its not relevant now.

You always have the bootloader of the last official rom you had
[Galaxy S III General] android addicts:
Little bid confuse. I guess i have a JB bootloader.
[Galaxy S III General] Samzter:
thanks man, it's great i bumped into this thread. gotta check my s3's chip when it arrives this weekend. good thing my old man's one got the 0xf7 revision :)

..but mine's in the waiting... lol
[Galaxy S III General] dhirend_6d:
Well if you officially updated to JellyBean at the beginning, then you have a JellyBean bootloader.

I don t know whether bootloader is flashed or not when flashing a stock ROM in ODIN though. Never used ODIN except for rooting and CWM in the beginning.
[Galaxy S III General] danarama:
Yes it is. Only some OTAs don't because the bootloader is not updated every time.
[Galaxy S III General] chs4326:
I am a bit confused as no dates are provided in the 1st post and my Kernel name appears to be all about dates.

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

CWM-based Recovery v5.5.0.4 CF-v1.5

I have the VTU00M 0xf1 chip. Need I worry?
[Galaxy S III General] danarama:
Your kernel comes with the rom. Read custom rom section of post 1
[Galaxy S III General] danarama:
Your recovery isn't safe!
[Galaxy S III General] chs4326:
Thank you! I take it that the kernel is safe, but the CWM-recovery is not and need to be updated? Will the bootloader automatically be updated if I update CWM-recovery?

EDIT:

You are fast! Ok I will update it then, will this automatically provide me with a safe bootloader?
[Galaxy S III General] jj92942000:
Install PhilZTouch recovery, best and gets you covered.
[Galaxy S III General] danarama:
recovery and bootloader are 2 separate things. Theres nothing wrong with your bootloader. Your bootloader always remains at whatever version the last officially installed rom was.... So unless you were on 4.1.1 when you last had an official ROM, you're fine.
[Galaxy S III General] chs4326:
Crystal clear. Thank you for your time.
[Galaxy S III General] Andr0id7:
Do S3 Clones covered by SDS?
[Galaxy S III General] danarama:
You're joking, right?

S3 clones are not s3's. They are different phones completely. The only similarity is the clone is built to look like an S3.

If the S3 is a house brick and the clone was a block of butter painted red, you wouldn't expect the butter to have the same properties as the brick. A builder can't answer any brick related questions about your butter and be correct. He also can't build you a House
[Galaxy S III General] android addicts:
Thanks friend. When I purchase this phone it has android 4.1.2 JB (out of the box). seller unboxed it front of me.

I thought it can check using about phone.
[Galaxy S III General] rayiskon:
https://plus.google.com/u/0/104711040110222472212/posts/Rs3WW8AkW9k

if this works, people with corrupted eMMC (SDS) and obviously no warranty might eventually be able to boot from an external SD card.
[Galaxy S III General] danarama:
Aren't there already similar threads here?
[Galaxy S III General] rayiskon:
i don't own an S3 anymore so i don't follow this forum. just trying to help. no need to be an ass.
[Galaxy S III General] danarama:
That would be you rude face. This thread is a preventative measure thread, not a repair thread. Please post your "help" in the existing threads.
[Galaxy S III General] febtober:
My phone looks like it is in the "half SDS" state now, which is annoying, but normally I would just run to a Sprint store tomorrow and get it swapped out, no big deal. However it looks like I've run into a bit of a snag....

I was talking to a Sprint rep at a local store on the phone just now, and he asked if the screen had any cracks on it. I said yes, I dropped it a few months ago and there are some cracks on the screen, but they don't bother me and they have nothing to do with the current problem. However he stated that since the screen has cracks in it, their techs aren't allowed to remove the screen since the whole thing could fall apart.

And since the tech can't remove the screen, he can't test the motherboard. Since he can't test the motherboard, they can't actually determine what the problem is (even though it's fairly obvious) and they can't cover it under warranty. I'll have to go through my insurance and pay the $100 deductible.

The cracked screen never caused any problems or issues, it was just mildly annoying to look at, so I never bothered getting it replaced. Now it looks like it's going to prevent me from having a nice simple phone exchange...
[Galaxy S III General] danarama:
I Don't think US variants have the affected chip
[Galaxy S III General] idiotechnick:
mostly the international version. Now i know why some GS 3 devices are burn.... Maybe they just SDS problem that happen during your travel or even sleep. I almost burn the phone when i watching movie and sat down on my bed while i just texting to my friend, i put my phone down and watching about 5 minute and when i pickup the phone is really really hot... like burning hot!!! and the screen i just freeze on whattsap text. Good god i check my phone... if i sleep or just ignore the phone maybe it going to burn my house down.
[Galaxy S III General] danarama:
Thats not this issue
[Galaxy S III General] rascal0pl:
Googy-Max Kernel

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

Is it safe?
[Galaxy S III General] danarama:
Its essentially Siyah kernel sources so yes, it's safe
[Galaxy S III General] pickandwhammy:
Off topic: S3 explodes while charging - http://newlaunches.com/archives/sam...s-middle-night-battery-swells-bag-popcorn.php

EDIT: And here's another! Explodes in the woman's trousers!
[Galaxy S III General] Erik1805:
Can you send your device back if there is an SD?
[Galaxy S III General] gabraelli228:
googy kernel 2.0+. it is safe or not?
[Galaxy S III General] danarama:
Read 3 posts before yours.

Remember, always read the last 2 pages of a thread before posting.
[Galaxy S III General] cyceron:
As I read this thread, I understand that CM is completely safe from Sudden Death?
[Galaxy S III General] danarama:
No. only what is in post 1 or newer.
[Galaxy S III General] cyceron:
aproth still

latest nightly is safe?
[Galaxy S III General] danarama:
Its in post 1
[Galaxy S III General] android addicts:
After I installed Goomax kernel I run the exynos men bug checker app. Now it shows I'm protected. But before few months ago it shows I'm affected. Why is that? Is it a kernel change?

Sent from my GT-I9300
[Galaxy S III General] danarama:
Ask developer. Exynos mem bug checker absolutely irrelevant to anything in this thread, as discussed in post 1.
[Galaxy S III General] danarama:
Thread locked. We have really gone as far as we need to with this thread.

Everything released since 4.1.2 has the fixes. Stick with up-to-date releases and you'll be fine.

This thread was designed purely to get "Tell me about SDS" discussions out of the development threads and it did that well, but these discussions no longer exist.

Please keep all further SDS discussions to the **Ultimate GS3 sudden death thread**
[Galaxy S III General] danarama:
wee need OTA files to find out. Obviously FULL official includes bootloader.

The OTA does I beleive, but as above, haven't seen the OTA files so hard to tell.

However, I would wish everyone would forget about bootloader :)
[Galaxy S III General] siavash_Skh:
But I have older versions (FULL official) downloaded from sammobile that they dont include. XELLA was the first time I see the sboot file on the package.
[Galaxy S III General] IamIrene:
that good

but so far I using wanamlite 5.3 which is base on ELLA

but now I running perseus kernel 31 + cwm touch recovery 6.0.2.7

am I safe ?
[Galaxy S III General] danarama:
Your recovery is NOT in the fixed recoveries list on post 1!
[Galaxy S III General] glaudrem:
So, am I correct if I assume any Stock Official 4.1.2 update (XELLA, XELLC, XELL4) has the fix included? I have always installed latest official version and now my kernel is version 3.0.31-566833

Many thank for helping noobs like me.
[Galaxy S III General] danarama:
Yes you're right! I assumed all did like HTC.

OK I'm downloading ELLC to see.... But its taking long time.
[Galaxy S III General] danarama:
XXELL4 - We believe not

XXELLA - We believe Yes

XXELLC - We do not know yet
[Galaxy S III General] glaudrem:
Thanks. I have XELL4 which seems to be Unbranded UK. What makes you think this does not include fix?

I really would appreciate if Samsung says something. It is a bit annonying that you spend a lot of money and you must rely on community for getting things fixed.

Sorry for noobish ask but first time using odin and whatever. Will it wipe my phone if I install XELLA over XELL4?

Again, many thanks. You are bringing light to the darkest hour of our S3
[Galaxy S III General] IamIrene:
ya so I better flash the philz touch recovery ?
[Galaxy S III General] mkrajaci:
Just one noob again. Is my phone safe?
[Galaxy S III General] glaudrem:
That kernel is same as mine, just change what comes after 3.0.31
[Galaxy S III General] krivinash:
not.

you dont have any protection.

you need new kernel or new FW (XXELLA).
[Galaxy S III General] glaudrem:
But I have FW XELL4 which suposely only change Country and kernel says the same...
[Galaxy S III General] mkrajaci:
Should I wait official fw for my carrier?
[Galaxy S III General] drakester09:
If you want to be safe now: no.
[Galaxy S III General] danarama:
Yes, if you're not comfortable flashing official firmwares from other countries, which in itself is risky, perhaps its best to wait.

If this fix really does fix the issue, we're all going to get it officially at some point soon.
[Galaxy S III General] siavash_Skh:
Maybe no

I suggest u to flash xella official rom. Or flash the perseus 31.2 on the current rom.

Read the post 1 too
[Galaxy S III General] Rob2222:
It's OK. XXELL5 kernel contains the VTU00M string, as same as XXELLA.

And cause of that string we assume, that this kernel already has the fix.

Everything as fine as it could be.

@All:

When you assume XXELLA contains the fix, cause of the string is in the kernel binary, then you must put XXELL5 to the white list also, cause it contains the string and more strings (f.e. "movi operation is failed") from the fix. XXELL6 contains them also.

XXELL4 I didn't have unpacked yet. If someone gives me a direct link to the kernel I can check that, too.

BR

Rob
[Galaxy S III General] danarama:
We're going on what has been drip fed through from devs but I will be looking at the strings over the weekend. However, have we seen XXELL5 SDS? I think so.

Also, what evidence is there that they are the only strings that are forming part of the fix?
[Galaxy S III General] Rob2222:
The appearance of the strings is a indication that we can assume the fix is already compiled into this kernel binary. If the fix wouldn't be compiled in, the strings would not be there.

Read this:

http://xdaforums.com/showthread.php?p=36491646#post36491646

However, no one here guarantees that the fix will prevent SD to 100.0%!

So just because we maybe see a SD with XXELL5/6/A, it doesn't mean, that the fix code isn't in there.

BR

Rob
[Galaxy S III General] danarama:
Im not sure which post that points to in the thread. Nothing that seems to articulate with our coversation.

Anyway my point was, how do we know those strings + others arent needed and they needed other strings but didnt realise until after LL5 was released?

https://dl.dropbox.com/u/20471345/SUroot/SGS3/ELL4_boot.img

Edit > OK see your edit now.. But still, we dont know the strings form part of the fix and the full fix wasnt identified,.

What we REALLY need to know is the full extent of what the source code commits produce within the kernel.

We need a kernel built from source without the fix, then the same kernel with the fixes and compare the dump of boot.img
[Galaxy S III General] Rob2222:
Ive updated my post. Please read it once again.

Checking XXELL4 now. Will update this post with result.

EDIT: XXELL4 also contains it already:

VTU00M <4>%s: movi operation is failed

Compare it with the code from the fix:

https://github.com/AndreiLux/Perseus-S3/commit/a03cc073ac1fc4c790635cf5d555156c5c4db9cc

However, for me personally it's safe enough. I'm using stock XXELL5 atm.

BR

Rob
[Galaxy S III General] danarama:
Ive updated my post too. Likewise ;)
[Galaxy S III General] danarama:
So in essence the fix is crap? Because actually the strings say it (in its entirety) has been present since ELL4?

In which case, what did ELL4 > ELLA actually change?
[Galaxy S III General] Rob2222:
No! Why you assume that? It is not bad, that this fix was in stock kernels for longer time. Thats not negative.

However the fix source code wasn't aviable to be put in custom kernels until source 7 came out and now devs can put the fix in their own custom kernels,too.

The main point is: Nobody here at XDA knows for sure what the fix actually does. So nobody can say, if the fix prevents SD for 100.00%.

Cause of that even Entropy said the fix will prevent SD in 90% in _his opinion_. And thats my opinion, too.

Long story short: We cannot be 100% sure to be 100% safe at this time. It could(!) be, that even the fix cannot prevent SD in all cases.

But you should use a kernel that contains the fix, thats for sure.

BR

Rob