yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] cammel:
We, or at least I, don't know what stock recovery cf-auto-root flashes after rooting the phone, so in order to be sure after rooting your phone flash a safe recovery like phil's CWM based recovery if you want a custom one for example, or the stock one from XXELLA or XXELLC depending on which firmware are you installing.. You can do this easily with mobile odin pro, but there also some other ways to do it.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] siavash_Skh:
Did you see anyone advantage to have new rom with new kernels ?? No

I think it is like the kernel fix. Maybe there is a fix in it ( for example for booting into download mode).

Can anyone refuse it ?

Edit: we dont need to approve any advantage of new bootloader loader to use it.

We need any approvement of no advantage of it to not using it.
[Galaxy S III General] shaq89:
OK I'm using ELLA, if I root with CF-Auto root, how to flash stock ELLA recovery only?
[Galaxy S III General] siavash_Skh:
Use mobile odin
[Galaxy S III General] philgalaxs3:
Could please explain how to install Cf-auto-root with mobile odin . without installing the CF recovery ?

Thks
[Galaxy S III General] cammel:
Exactly

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] Droidphilev:
hi,

ok... i'm trying this but it seems i am doing something wrong. The "cat /sys/class/block/mmcblk0/device/movi_ops" should be typed in terminal app, right?

EDIT: found it. You cannot do this in terminal of aroma fileman.

I have a 2 btw. Machine bought in august and never had any problems with it
[Galaxy S III General] T0xic4u:
Yes, open Terminal-App. First type in: su

SuperSu will Pop up and you have to give Superuser-Rights. Then copy&paste the above command. Please let me know, what Chip-Date you have in eMMC-Check-App

Taper di Tap with my S3 @183 days
[Galaxy S III General] Droidphilev:
hi,

have a 2

chip is VTU00M rev 0xf1 dated 05/2012

i wrote above: i did it correct but in aroma fileman, that does not work. just FYI
[Galaxy S III General] invinciblecc:
Guys can i flash this mattiadjs

[MOD][JB/ICS][15DEC] bestMultiTaskingFix 7 - Multitasking with no lags!

I am on yanks 555 kernel am using swap coupled with zram and want to improve multitasking even more also i am not using hard swap but using ram expander to create swap file in external memory so even though I don't have swap partition can i flash this to get the tweaked build prop settings for enhancing multitasking

Do I need to turn off zram before flashing this
[Galaxy S III General] danarama:
Yes I can refuse it. I'm not knocking you for use it so calm down and post rationally.

There is no proven advantage. There is proven disadvantage. Its as simple as that

Personally I prefer custom kernels so its BAD for me. Bad = disadvantage!

Please calm your attitude.
[Galaxy S III General] T0xic4u:
@treare

THX.

I have a theory. But to proof it, I need someone with Chip-Date 10/12. Better 11/12 but still 0XF1. I checked all posted screenshots in this forum and ah.de.

All screenshots showed, that Chip-Date 04/12 up to 10/12 are on 0XF1. Found some with 11/12 using 0XF1 and some with 0XF7.

Taper di Tap with my S3 @183 days
[Galaxy S III General] Scarface1991:
Look at Entropy512`s posts. They will describe in detail why there is no evidence at all that there is a fix in the bootloader. The only thing this bootloader seems to do is to screw up Triangle Away so you can`t reset the flash counter. However there is plenty of evidence that the fix is in inside the kernel. Until now I don`t know of any case where a device died although having installed a fixed kernel. I don`t say I`m 100% sure that devices won`t die although having a fixed Kernel but that`s the best we can do now.
[Galaxy S III General] Droidphilev:
Hi,

wow, big job that you did. Can i know what you are assuming please?
[Galaxy S III General] quebec1:
@cammel help me please?
[Galaxy S III General] montage mahal:
Screw up triangle away? Not if your on a stock kernel and recovery. Have you read the last 10 posts?
[Galaxy S III General] danarama:
Triangle away is a moot point if you're stock kernel and recovery. My point is (and always was) that it does screw with the flash counter if you dont want to be limited to stock kernel and recovery.
[Galaxy S III General] siavash_Skh:
I mean after using cf_auto_root u can flash stock recovery using stock rom through mobile odin.

---------- Post added at 10:53 PM ---------- Previous post was at 10:46 PM ----------

Ya. I know what do you say.

But there is the risk of sudden death. The worst thing that I see about a phone until now. So I can't risk about it.

You cant approve that is has no advantage like new kernel.

Because samsung didn't say anything about it. So no one can confirm anything about that which can solved this problem. Samsung is responsible for all our worries. Shame on Samsung!!
[Galaxy S III General] T0xic4u:
@treare

My theory:

Samsung started to put in the magic code of update-7 in November.

Samsung started to put in a new firmware for eMMC in November. (0XF7)

So I guess all Chips with 0XF1 have the same firmware-date 13.04.2012

This would make our test with terminal-emulator needless.

I assume Samsung knew about SD for a long time.

Taper di Tap with my S3 @183 days
[Galaxy S III General] Scarface1991:
I read almost this whole thread.

The majority of people here uses Custom Kernels and Custom ROMs and with the new bootloader I couldn`t reset the counter no matter what. It would always go on 1 no matter what. Afterwards I installed the old ICS Bootloader and everything was good again. All on official and no exclamation mark. People use the new bootloader and think there is some kind of fix there and that`s fine if you are on a Stock configuration (although there is no evidence for a fix inside the bootloader). But if you still want to be sure to get warranty when using a Custom ROM or/and a Custom Kernel, you need the old Bootloader (at least I did) to reset the counter.

Exactly!
[Galaxy S III General] danarama:
dan@dan-Latitude-E6410:~/Documents/Boot$ grep -a -i VTU00M ELLB_kernel
VTU00M<4>%s: movi operation is failed
[Galaxy S III General] montage mahal:
Everyone is different. I think it's safer for me (this is just my opinion) to stay on the stock+root road till this sudden death thing blows over. I can go back down the custom road when my warranty is up. :D
[Galaxy S III General] Droidphilev:
hi,

Quite possible, yes :(

I know someone who works at Samsung (not phone related though). It seems that they don't care too much. As long as the count of replacements is marginal...
[Galaxy S III General] danarama:
To confirm to those wondering about CF Autoroot, I don't know what the recovery image is that's used but it's kernel does not have the update 7 fixes in it.

dan@dan-Latitude-E6410:~/Documents/Boot$ grep -a -i VTU00M Philz_recovery
VTU00M<4>%s: movi operation is failed
dan@dan-Latitude-E6410:~/Documents/Boot$ grep -a -i VTU00M CF-AR_recovery
dan@dan-Latitude-E6410:~/Documents/Boot$
[Galaxy S III General] danarama:
Quite right. "To each his own".
[Galaxy S III General] \m/aximuS:
Stock kernel XXELLC 100% contains sudden death fix, or is better to use the custom kernel? Because i don't have warranty, and i am so afraid sudden death.
[Galaxy S III General] cocous:
my phone 16gb has the VTU00M 0XF1 chip and is 10/2012 and te mp is 1.400

why?

maybe you must wrong
[Galaxy S III General] danarama:
10/2012 is October. October is before November, so your s3 doesn't disprove the theory
[Galaxy S III General] T0xic4u:
If you could/would do the test, I bet you would get a "2" as result and we would knew, that your "internal" firmware-date is 13.04.2012. So I realy would aprreciate it, if you would be so kind to do the test.

Taper di Tap with my S3 @183 days
[Galaxy S III General] Kobrax:
So few S3's are dying in comparison to how many are sold so why worry?

Just follow the steps to make sure you Are safe and just use your phone as you wish.

Worst case scenario your phone dies. Big deal get it replaced. If you follow the steps you won't have to worry.

Old bootloader, fixed kernel and recovery. Flash triangle away to get official status. Sorted
[Galaxy S III General] cammel:
The thing is that I don't know what rom are you using or you want to use, if it's a custom rom and you have already updated your bootloader then your flash counter will always go up to 1 after using triangle away, what I did works only if you flash a stock firmware with stock kernel and stock recovery...

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] brainimpact:
Something is not correct in what he is saying, if he's Stock everything when he got SDS then why is he worried that about taking it for repair b/c is System Status is Custom?

He's not being honest or making a genuine mistake thinking stock only means ROM
[Galaxy S III General] philgalaxs3:
see post 1 : Stock kernel XXELLC contains sudden death fix ... as far XDA people knows . No need of a custom kernel.
[Galaxy S III General] EViollet:
Hi.

I'm not sure it's important to flash the old bootloader.

If the phone is borked, then the flash won't be readable anyway so Samsung cannot tell if it's been rooted or not.

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III General] philgalaxs3:
make sense .

but old bootloader can be usefull for warranty in case of other problem than SDS ...
[Galaxy S III General] danarama:
For SDS itself, its not important. What if the fault is something else? Like faulty USB port? Other NAND issues that do not prevent download mode? Radio Brick? Any fault that essentially prevents you flashing back to stock.

You're right, SDS it's not important, but it was never important for that reason anyway. It was all the other little faults it was important for.

We have to try and remember, there is more to the S3 than SDS :)
[Galaxy S III General] Scarface1991:
There were several cases here where phones died without a reason but you could still go into download mode but you couldn`t flash anything through odin, it would always fail and recovery was not accessible.

If you have a case like that, then it is important in my opinion to have everything on official, so you don`t run into warranty problems. That`s my opinion.
[Galaxy S III General] EViollet:
Yep.

You're all right. I had kind of overlooked the fact that there are thousands of ways to bork the phone...

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III General] T0xic4u:
Agreed :thumbup:

Taper di Tap with my S3 @183 days
[Galaxy S III General] danarama:
A little knowledge can be very dangerous. A little knowledge AND a USB cable can be catastrophic ;)
[Galaxy S III General] nexy33:
Just received my s3 back from samsung repair uk now has VTU00M 0XF7

Baseband I9300 NELK2

Build xxell4
[Galaxy S III General] Kev_cr:
I don't really get the siyah recovery stuff...I've flashed CWM kernel package and installed stweaks...its suppoused to have hacked my recovery but is it secure now? Or should I also install siyah recovery via odin (couldn't find download links at devs page...anyway thibk I've seen it somewhere here)
[Galaxy S III General] cammel:
Hello again!

Chainfire has just updated cf-auto-Root with XXELLC stock recovery!!!

Just to let you guys know! :D:D:D

Enviado desde mi Nexus 7 usando Tapatalk 2
[Galaxy S III General] odoto:
I'm not too sure about that... I'm relatively sure I read about cases of SDS where download mode was still possible, although flashing wasn't (errors every time). This might be because the portion of the eMMC where the bootloader resides was still working.

Don't quote me on that, but if it's true, flash counter does matter for SDS.

Of course there is a possibility that those cases weren't SDS, just looking like SDS :P

---------- Post added at 01:52 AM ---------- Previous post was at 01:42 AM ----------

what is the production date of your eMMC?

---------- Post added at 02:00 AM ---------- Previous post was at 01:52 AM ----------

like T0xic4u I would appreciate if you would test if your chip is affected or not... provided you are okay with flashing kernels of course! if you still got a clean flash counter you probably shouldn't ;)

but in case you want to, look here: http://xdaforums.com/showpost.php?p=36696791&postcount=531
[Galaxy S III General] rlorange:
My GOD these posts just keep coming...

---------- Post added at 12:29 PM ---------- Previous post was at 12:25 PM ----------

Indeed I am probably the perfect candidate for testing l the magic code in update 7. I have had my phone since June and flashed the hell out of it.

Interestingly tho I'm still on the boot loader that came with my device and have rarely flashed using Odin
[Galaxy S III General] danarama:
Chainfire has updated to the ELLC recovery in Cf-auto-root

http://xdaforums.com/showthread.php?t=1957273&page=39
[Galaxy S III General] siavash_Skh:
In a persian forum I see one person suffering from SDS. Its phone was on poland 4.1.2 rooted official rom. He didn't change the kernel or recovery. But because of root procedure maybe he had a old recovery.
[Galaxy S III General] jfsyl:
Hello,

One question : Why Omega 36 is not in the safe "CUSTOM ROM" ?

thks you
[Galaxy S III General] pickandwhammy:
Please read this.

I should automate this reply :\
[Galaxy S III General] gadgetcraze:
Hmm. Time to un root and go stock I guess. My country's warranty system is really screwed up. I wonder they will honor the warranty even if they don't find a loophole. They are used to passing on every defect as moisture related damage.
[Galaxy S III General] pickandwhammy:
I wouldn't suggest doing that just because there's a risk. Don't let their bad QC and buggy chips/memory decide how you use your phone. Flash the old bootloader and use TA to reset counters.

Beyond that, if it goes bonkers, bad luck - at worst you'll lose some money. At least your experience would have been what you wanted it to be :)
[Galaxy S III General] lukesan:
Ok, I'm in a bit of debate with myself here.

Got my S3 2 days ago from amazon and they told me I could sent it back. Yes, it has the famous vtu00m and 0xf1 date 09/2012

Replacing it via amazon I will probably get the same version.

Is there a way to check on a box via a sn or so if it has newer hardware?
[Galaxy S III General] T0xic4u:
@odoto

Chip-Date of mine: 05/12

Firmwaredate: 13.04.2012

Taper di Tap with my S3 @184 days
[Galaxy S III General] pickandwhammy:
How did you find firmware date?
[Galaxy S III General] danarama:
The issue is not a hardware issue. Its a firmware issue
[Galaxy S III General] danarama:
It's the very first one in the list!
[Galaxy S III General] T0xic4u:
With this test:

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

Taper di Tap with my S3 @184 days
[Galaxy S III General] qavro:
Darky ROM v8.4 is based on XELLA. When you flash it you have 2 options, XELLA kernel or Syiah, so i think you should have a look at this one as well.

Not a safe recovery yet though unless you hijack from Stweaks using Syiah kernel.
[Galaxy S III General] pickandwhammy:
Okay. Thanks.
[Galaxy S III General] whiper:
Chip-Date of mine: 05/12

Firmwaredate: 13.04.2012

actual on Siyah 1.8.7

Survived without patch since 07.06.12 = 221 days
[Galaxy S III General] g4ngst4h:
Then i flash this new "CF-AutoRoot" overwriting the previous one with ODIN?

sorry for my english.
[Galaxy S III General] priyana:
Maybe you can ask for a 32GB one instead?
[Galaxy S III General] danarama:
CF-Auto-root will replace whatever recovery you have with the one it is supplied with, in this case ELLC. I have not used CF-Auto-root, so I cannot say how it works however.
[Galaxy S III General] g4ngst4h:
i have the last stock rom update (ELLC, 4.1.2) with samsung kies. Yesterday i flash with CF-Autoroot and my terminal is rooted succefully but i read in these forums the problem with the recovery.

Can i flash with odin only the new recovery ELLC.img posted by you?
[Galaxy S III General] alijee:
I am on stock ELKC rom with JKay deluxe mod and siyah v1.8.8 kernel...should i consider myself safe or should i install ELLA rom?? ecause i have same effected eMMC version.

and sorry i m new so dont know which recovery i am running...
[Galaxy S III General] quebec1:
ok, now j have a omega rom. if i want to install a stock rom what do i do?

i installed trinagle away e odin mobile pro.

After lanch trinagle away the phone rebbot in a particular download mode, now how do install the rom with odin mobile pro?

sorry for my english
[Galaxy S III General] strongyin1977:
thanks.....
[Galaxy S III General] don_rico:
Lost the plot.... recovery flash?

Hi there, so... flashing i.e. perseus or siyah gives me the sds "fix" but the recovery bit is a bit new for me. Do i have to flash another zip again?
[Galaxy S III General] pickandwhammy:
Please go through this thread:

http://xdaforums.com/showthread.php?t=2095618
[Galaxy S III General] danarama:
Can you not use CF-Auto-root again? if its possible it would be easiest (Download new version)
[Galaxy S III General] g4ngst4h:
Yes, i have flashed with the new version and it's ok. Now i have count 2 times.. can i use the latest version 2.55 of triangle away to reset the counter without fear to brick?
[Galaxy S III General] danarama:
There is always risk. Should work fine but depends what sboot you have as to whether it stays at 0.
[Galaxy S III General] g4ngst4h:
How I can find the version I have and if it supports triangle away?
[Galaxy S III General] MuertoKo:
Hey root you should check SamsungMobileES on twitter ;)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] T0xic4u:
The result was exact the same before you flashed everything.

Taper di Tap with my S3 @178 days
[Galaxy S III General] ducky1979:
i too have VTU00M with 0xf1 thats obviously the on board emmc, so it would be nice to see if there is a different version out there.

So im playing pot luck then really, but at least because i have the ICS sboot i can flash everything back to stock if i have to.

or i could flash the new sboot now as i doubt ill use odin on the pc again, how can i get hold of the newest sboot?

at least then im covered all ways, safest firmware and flash counter at 0.

or if i have the newest sboot and a custom recovery will it not reset the counter to 1 on every boot??
[Galaxy S III General] T0xic4u:
Read first post please. Bootloader doesn't fix the SD. Kernel does. Is it that difficult to read the Start Topic?

Taper di Tap with my S3 @178 days
[Galaxy S III General] IRoN MaN9:
i know mate it's the same no thing change
[Galaxy S III General] ducky1979:
thanks i understand that, im on the latest perseus kernel and philz recovery so both kernels are the current 'safe' ones, my question was more regarding the fact the latest sboot stops us having the ability of clearing the flash counter for good. and i cant be arsed to run triangle away after every boot.
[Galaxy S III General] IRoN MaN9:
dude we all know it's the kernal but as you see the pic there's nothing change before and after installed the kernal
[Galaxy S III General] T0xic4u:
@ducky

Oki doki. Sorry for missunderstanding.

Taper di Tap with my S3 @178 days

---------- Post added at 01:31 AM ---------- Previous post was at 01:29 AM ----------

@Iron

Dude, the fix doesn't change your Hardware. This App just gives Info about your Hardware.

Taper di Tap with my S3 @178 days
[Galaxy S III General] Scarface1991:
1. This App was orignallly developed for the SII to find out if you had a eMMC chip that is potentially harmful (eMMC superbrick Bug)

2. But We can use this App to find out if a device (I9300) is potentially harmful to the Sudden Death Syndrome.

Thanks to the devs we know that a VTU00M type eMMC chip with the Revision 0xf1 is potentially harmful, so your device can die suddenly if it`s without the fix.

As others said before: The Kernel fix will not change any hardware, that`s why nothing has changed in your screenshot.

Actually what I just told you now is on the very first post in this thread
[Galaxy S III General] IRoN MaN9:
this is your first answer to me may be you confuse with another one

anyway i really greatful to your answer thank you so much here's another question i hope you can help with it

is there away to know trully and surly that our phones save from sds

and there's another q i see some mombers talking about vidio codec problem do u know any thing about that

and thanx again 4 ur concert:)
[Galaxy S III General] Bushido76:
No it isn't. We have to rely on the quality of samsungs source code fix.

Do you mean the playback problem? There was some video stuttering in Perseus 31.1 because the software needs access to a "restricted" memory area. Andrei quick fixed it in 31.2 but wants to rework this in a future version.
[Galaxy S III General] thegh0sts:
the kernel update does change how it writes to the EMMC with regards to wear levelling.
[Galaxy S III General] Scarface1991:
Yes but IRoN MaN9 wanted to know why the eMMC brickbug check app didn`t change any descriptions of the eMMC Chip after the fix and the answer is simply because the fix doesn`t change any hardware. I mean how could it? :D
[Galaxy S III General] kadopt:
Temasek's custom kernel also has the fix.

http://xdaforums.com/showthread.php?p=29339117
[Galaxy S III General] jakmeister:
I'm running ARHD v17 (a LKC base ROM) at the moment, and I'm slightly reluctent to upgrade to a XELLA ROM as I've almost 200 apps to restore and flashed quite a few mods to it. Will I be still vulnerable to SDS to just flash the XELLA based kernel and recovery, rather than flash all three?

Thanks
[Galaxy S III General] Karl978:
I think you can flash only kernel and cwm, and should be safe.
[Galaxy S III General] brouwerchris:
Read post #30 and #40 again.

Doesn't this mean that the stock XXELLA recovery is "SDS safe"and should be included in the OP list ?
[Galaxy S III General] duhhh:
is it possible this fix to be added to ICS kernel?
[Galaxy S III General] thegh0sts:
just update to JB already! :p
[Galaxy S III General] duhhh:
I don't want,because of Garmin.It runs only on ICS
[Galaxy S III General] danarama:
Yes it does but I slept instead :)
[Galaxy S III General] qavro:
i have used 2.55 but in download mode (ella) the status said: Custom. The count was 0 and the system binary was: official

After extensive reading on the TA topic i've found that 2.37 version is perfect for ella: in download mode all are perfect now: zero counter, and official allover. :D
[Galaxy S III General] danarama:
I only saw this today. Added to OP.

I have a 2 btw on 0xf1
[Galaxy S III General] T0xic4u:
So yours is the 11th test. And all have "2" as a result. Tested on 04/12 up to 10/12. I'm still waiting for 2 guys with 11/12 and 0XF1.

Taper di Tap with my S3 @184 days
[Galaxy S III General] dandroid13:
The link to Oranav's post is broken, 404.
[Galaxy S III General] cocous:
hi i ant to ask something

I heard that only the mp 1.100 16gb s3 with affected chip VTU00M, revision 0xf1 with release date 04/12 has the problem

this is true?

because i have the 16gb s3 with mp 1.400 and has the same chip VTU00M, revision 0xf1

and some friend have the mp 1.500 and again have this chip VTU00M, revision 0xf1.

all this phones are defective?

sorry for my english
[Galaxy S III General] T0xic4u:
As far as we know, all VTU00M 0XF1 are affected.

Taper di Tap with my S3 @184 days
[Galaxy S III General] dandroid13:
So the guys in the other thread were wrong, saw some comments that it's only 1.100 :confused:
[Galaxy S III General] RohanAJoshi:
frendz, today i got my s3 new, but my is eMMC is the VTU00M 0XF1.

so what i need to do for avoiding SDS ?
[Galaxy S III General] T0xic4u:
Read first post. Can't be that difficult. :banghead:

Taper di Tap with my S3 @184 days
[Galaxy S III General] danarama:
Obrigado,

It's odd because I used the link several times in tapatalk to get to the post to download the attachment and copy the commands, but confirm using desktop, 404.

Anyway fixed now...
[Galaxy S III General] ivan4o5:
This is what I have :

Color : Titanium Gray (16gb)

Type : VTU00M

FwRev : 0xf1

Date: 07/2012

Oranav's test --> 2
[Galaxy S III General] dandroid13:
I have

Color : Marble White - 16GB

Type : VTU00M

FwRev : 0xf1

Date: 05/2012

RF cal: 2012.8.10

HW Rev: MP 1.100

Oranav's test: 2