yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] danarama:
Depends how much you need customisation I suppose. If root is just "for apps" then I suppose its fine.

Of course, everyone can have whatever set up they want. This isn't intended to be a "how to" though. More a "whatcha need".

In regards to risk, sure flashing an sboot is risky. More risky than flashing a rom. No more risky than flashing a modem I.wouldn't expect. Flash a corrupt one and you're pretty stuck.

There are ways to mitigate risk though.

1) trusted sources

2) use Md5 to check for corruption

3) ensure you are careful to prevent power source removal

4) ensure you have a solid usb connection

Do these things and the risk should be neglegable.

Back to your point though, why not just flash full official then use cf auto root if root is required?
[Galaxy S III General] montage mahal:
Because I need the original LLA recovery as well as the kernel. Think cf auto root has an older recovery. This way (I hope) I have a full stock rom safe fom sd with root.
[Galaxy S III General] danarama:
Oh ok. What I heard was cf-root gives custom and cf auto-root gives nothing but reading up on it, it gives you a stock recovery itself.
[Galaxy S III General] montage mahal:
Yea it gives you a stock recovery but I don't think it has the fix. Only Chainfire can answer that :)
[Galaxy S III General] mich3lam:
alusuisse mvnedji

This sudden death issues is making me so scared, lol...

It say's that XXELL5 is safe? Here is what it looks like for me:

https://dl.dropbox.com/u/51850370/12.png

In here it looks like I am infected...

https://dl.dropbox.com/u/51850370/11.png

In here I have the XXELL5, am I safe or what?

:confused:
[Galaxy S III General] sh_:
Noone here is reading first post and asking same questions every time :D
[Galaxy S III General] philgalaxs3:
The one you had before flash. cf-auto-root don't install any recovery.
[Galaxy S III General] trionic:
That would be great but I have read exactly the opposite. :(

I really dont know if autoroot keeps the fixed stock recovery as the tool is previous to the fix
[Galaxy S III General] philgalaxs3:
Have a look here : http://autoroot.chainfire.eu/

A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then	clean-up the cache partition and re-flash the stock recovery.
[Galaxy S III General] :
Yh read the same at first thought I was safe as cf root 6.4 does not replace kernel but then read that to be truly safe you also need to have a recovery with the fix and as cf root 6.4 was created before the fix it still as I understand uses a old recovery which does not have the fix for recovery.. So instead I flashed philz recovery which has the fix after i rooted with Cf root...I think I am safe now fingers crosses
[Galaxy S III General] philgalaxs3:
cf root 6.4 replaced the recovery ... cf-auto-root no more

In fact it install a recovery just for flashing . if you would kill by SDS at the moment you would be very unlucky
[Galaxy S III General] priyana:
But, cf-auto-root tar.md5 file contains a recovery.img

You sure it didn't replace the recovery?

Chainfire only say he didn't replace it with CWM recovery.

He put a stock recovery.

The question remains valid. Which stock recovery is it that cf-auto-root put?

But I still flash Philz recovery anyway.
[Galaxy S III General] montage mahal:
+1
[Galaxy S III General] philgalaxs3:
Ah! pertinent remark ! (not senior member for nothing !)

I have a look at recovery.img from cf-auto-root : it seems not to be a XELLA or XELLC one !

You are right : better use Philz recovery.
[Galaxy S III General] :
good to know i was right to flash philz recovery as i wasnt 100% sure if recovery had fix or not. had a feeling it was using old recovery as it was made before the fix...thanks for confirming anyways
[Galaxy S III General] sebarkh:
60 pages of asking the same questions over and over again in gazillion combinations...

Too much for me...

Sent from my washing machine...straight from the tumbler...
[Galaxy S III General] JKM2247:
We are all gifted differently and our knowledge base is definitely varied. However whether an Android "Geek" or "Noob" there is convergence in fear of losing a valued phone and as such most of us want to be sure that we are in the right plane. The major culprit in all this is of course SAMSUNG because of their failure to allay our fears about this very distressing matter of Sudden death of their Flagship product.

It's not just 60 pages of asking questions in a gazillion combinations, as you put it because along the way, input from the more knowledgeable lot among us are questioning some of the prior info given as fact. Two posts or so above yours, a doubt if CF Auto is really a safe option has been raised and the "owner" of this thread seems to concur that he need to read further on the matter, so .........
[Galaxy S III General] danarama:
I did read further and agreed its not a safe option
[Galaxy S III General] Volcanic:
I've noticed that both SDS number under XXELLA and XXELLC are increasing.

I become a little bit worried.
[Galaxy S III General] anubius:
Am I covered? Here is how this all this story made me paranoid:

1. Flash safe recovery ... check

2. Flash safe kernel .... check

3. Flash new bootloader..... no way (we are not that crazy Samsung!)

4. Read hundreds of pages of any forum marked by word "death" until 2 am .... check

5. Check for auctions everyday on ebay for I9300 32Gb model ... check

6. Get rid of original Samsung charger ... check

7. Do not leave charging overnight.... check

8. Turn power each time with the fear of not seeing the screen ... check

I am almost ready to lose my mind..... check

But it is just a phone....(damn but really expensive one). Why did you do this to us Samsung....
[Galaxy S III General] pickandwhammy:
Haha, you're almost letting your phone dictate your life! Nothing after step 2 is necessary, really. Just keep taking Nandroid backups (and if you're so paranoid, then TiBkp update.zips too) and copying them to your PC every week or so. That way even if your phone dies, all you risk losing is some money (in case warranty doesn't work out) and some days of data/settings/apps.

That seems like a reasonable compromise, doesn't it?
[Galaxy S III General] danarama:
Please do not simply say this without linking us to the proof. As yet, not one SDS can be confirmed with proof under XXELLA or XXELLC. Please post links to where you have seen this.
[Galaxy S III General] anubius:
Forgot to add it to my list. I do nandroid and Titanium almost everyday as well. I posted all this just for fun to relax the forum a little bit. When I go to download mode it says flash counter 0 and binary official however the rom is custom I just can't live with stock. So if it dies the warranty should cover it still. I am in Europe and have the original bill for phone from the guy that I bought from ebay and device is almost 6 month old so I think I will chill for now. Feel bad for people that have no warranty though. I can understand their fear. I also wanted to say that we should not flame anyone by asking the same question all the time. The more people we put on new kernel and recovery the better is for us because this is ongoing experiment still to see if that combination will solve SDS problem.
[Galaxy S III General] Kobrax:
I rooted with cf auto root but then flashed PHILz recovery so that should be okay right?

If it's only a temporary recovery isn't using cf auto root ok as long as you then replace the recovery?

You'd be very hard done by if your s3 died during the 30 seconds it takes to root :p
[Galaxy S III General] ivan4o5:
Is the old 4.0.4 bootloader safe for use ? If it is ,I think ,then the best compilation is :

1) 4.0.4 bootloader

2) root

3) custom recovery (with custom kernel)

4) custom kernel

In that case ,if your phone dies and it is able to go into download mode ,samsung will never know that you've rooted your phone .
[Galaxy S III General] pickandwhammy:
If you're in Europe you have nothing to worry about. People like me are the unlucky ones: no Play Store, our per capita income is about a tenth of any developed country's, telecoms don't partner with manufacturers to provide "plans" (meaning we have to buy devices at full price), after-sales support is worse than calling your internet provider's call centre, etc etc.

So, even though I'm in the same state as you (counter is zero, no exclamation mark, etc), if my phone dies I lose about a week's income and I don't even get a temporary handset from Samsung for the time in which they fix it.

Hope that makes you feel better ;)
[Galaxy S III General] qavro:
RootSu mate....i have a question. How for the life of me can i found out what is my current bootloader?

P.S. You can believe me, i've read this entire topic at least 3 times...
[Galaxy S III General] danarama:
Its not mentioned becuase the bootloader doesn't fix anything and is nothing to do with this topic :) I use a 4.0.4 Bootloader
[Galaxy S III General] andrewfung888:
You can use a program in playstore

Android System Info.

Or even BBS in the dump file.

:)
[Galaxy S III General] ivan4o5:
That means we can freely flash custom kernel and custom rom with the old bootloader without fear loosing warranty! Thanks mate ! :)
[Galaxy S III General] qavro:
Bootloader: I9300BVALF4

So, wich one is this? JB bootloader or ICS?
[Galaxy S III General] danarama:
Given that "F" in "LF4" means June, I would say that's ICS :)
[Galaxy S III General] ivan4o5:
*edit* Sorry , doublesend :/
[Galaxy S III General] qavro:
Great. I was hoping for an ICS bootloader, but have no clear idea why i was hoping for it:laugh:
[Galaxy S III General] anubius:
I am really sorry to hear that. Hopefully you phone will be ok. So Samsung doesn't have warranty in your country? Which country you from?
[Galaxy S III General] pickandwhammy:
It does, but I know more than all of tech support the customers directly interact with. They won't understand the concept of an eMMC hardware issue, they will simply follow the rule-book, which states: if anything on download mode doesn't read "default" or "0", void the warranty.
[Galaxy S III General] Pietrone94:
Ok so if my s3 dies i MUST be covered...but some says that s3 was "dead" but could go just in download mode (but impossible to flash with odin)...so go to assistance but sometimes Samsung don't repair it in warranty because system is "custom"...

If this happens...wht do you suggest to do?

(I am italian and i have an italian s3. So not eu warranty)

Inviato dal mio s3 con Resurrection Remix 3.1.4 :D
[Galaxy S III General] bobmatu:
the firmware for my phone it's out and it's I9300XXELLB

in first page there is xella and xellc

it's ok this firmare for suddendeath or not?
[Galaxy S III General] kaiur:
Yes you have. Directives rules in all European Union countries in products purchased inn legal form in the Union territory.

But i think this directive is not so simple; if Samsung prove that the soft manipulation has bricked your phone, could void your warranty I guess, and....how can you prove is "sudden death"? Samsung has admitted its existence?.We all depend on the good faith of Samsung.
[Galaxy S III General] akhil333:
iam installing hydrx-d latest version along with siyah kernal v1.8.8 and siyah kernal.... is it safe from SDS issue? (even theoretically)
[Galaxy S III General] Pietrone94:
Sorry I expressed myself badly :(

I wanted to say tha I am Italian and my s3 is italian..so if something happens and i have to go to the assistance, i have italian warranty which let me have back sooner my s3 phone repaired ...obviously i have eu warranty but beacuse i have also Italian one, i can have few assistance days :)

Inviato dal mio s3 con nuova firma perchè ad artic80 non piaceva quella precedente!!
[Galaxy S III General] danarama:
If you can upload me the boot.img please and give me a link, I can check it tonight. I'm sure it is fixed but best to check.
[Galaxy S III General] JPsy Droid:
I think there is an missunderstood cos of cf-auto-root recovery.

Some people think the recovery is replaced by one new recovery, which comes with cf-auto-root.

=> Till Page 64 I thought cf-auto-root replace the recovery temporarly!, and after rooting it will be replaced with the original recovery the system has before cf-auto-root.

Isn't it? :confused:

Otherwise Chainfires statement of the differences between cf-root and cf-auto-root makes no sense...

Greetz JPsy

Edit: I agree to rootSU #666 - i'm wrong, a stock recovery will be flashed back instead of the recovery which was installed.The reason for this is not clear for me... Maybe someone ask chainfire.
[Galaxy S III General] bobmatu:
where i can find boot.img

sorry :rolleyes:
[Galaxy S III General] priyana:
Reading his explanation, it seems you are right.

The package contains a temporarily recovery, or at least I know believe so.

But like I said, nevertheless I install philz because I must have a custom recovery for my phone.
[Galaxy S III General] danarama:
Within the ROM. Are you not downloading it?
[Galaxy S III General] bobmatu:
i download via ota this afternoon...
[Galaxy S III General] Stromma:
What steps is to be taken for all those who doesn't really care about being safe and only want to prevent to void warranty?

Would a reset of the counter and flashing a stock room be enough to maintain this?

I have to phones and I know it's "just" a phone, but even so I don't feel I want to lose that kind of money because I just played around.

// Strömma
[Galaxy S III General] danarama:
I don't think so.

This says he replaces your recovery with a pre-determined recovery.img supplied in the package.

Basically in another post, he needs to be supplied with a recovery.img for each device, so whatever img was supplied to him when he created Auto Root for teh S3 is the recovery you end up with, which most likely is pre-"safe"
[Galaxy S III General] danarama:
For those who don't care about being "safe" and only care about warranty, the step is simple.

Step 1: Do nothing

For those who don't care about being "safe" and only care about warranty AND are rooted

Step 1: Reset flash counter

Step 2: Flash stock ROM

Although if they rooted on JB, they may be unable to reset flash counter so it would mean ICS sboot flashed before step1.
[Galaxy S III General] Stromma:
Does this mean that there's no way to flash a stock rom, root and restore from Titanium, and then unroot again?

// Strömma
[Galaxy S III General] qavro:
Yes you can. And when you are done restoring just run triangle away and you are totally "stock" even if checked in download mode. And the last operation should be un-root.
[Galaxy S III General] pickandwhammy:
Depends on how you root and unroot.
[Galaxy S III General] danarama:
I've never flashed stock. Some say it wipes. Others say not. But no, you can't use Ti
[Galaxy S III General] pickandwhammy:
I'd flashed stock once to try the NFC fix. Kept bootlooping until I went into the stock recovery and said "reset to factory settings" or something along those lines. Unbeknownst to me, that thing formatted my internal SDCARD (and hence the Nandroid backup which I was supposed to restore to fix the NFC problem).

So, yeah, you can't use Ti.
[Galaxy S III General] Stromma:
So the correct steps would be:

1: Flash ICS sboot

2: Reset flash counter

3: Flash stock ROM

According to this the answer is no, cause I still end up with "modified" and a changed counter without being able to set it back.

// Strömma
[Galaxy S III General] cammel:
I was on stock ELLA installed with pc Odin so my bootloader was updated, then I rooted it using cf-auto-root, my counter was on 16 and the status modified.

When ELLC came out, I ran triangle away 2.55 so my counter went down to 0 and all my status on bootloader mode was on original. Then I flashed ELLC using Mobile Odin pro, enabling the everoot option and both my status on the phone (the one under setting/status and the 2 on bootloader mode) are on original and normal, and my flash counter is still on 0.

So...im running stock ELLC, rooted and with the binary count on 0 and all my statuses are on normal/original.

Hope this helps!

Some screenshots:

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] yethz:
I just bought my s3 week ago and after visiting this site i saw this thread 1st and said it to myself Oh crap i bought a new phone that could possibly die. No worries though i have my warranty but then i check my eMMC and to my surprise my phone isnt affected of the manufacturers fault.

Sent from my GT-I9300
[Galaxy S III General] T0xic4u:
First of all thank you for your work. I tested this and my result is "2".

I'm using patched Kernel since AndreiLux released them. I'm close to the deadline of 200 days. So having the absolutly affected eMMC, we will see in a few more days, if it works.

Taper di Tap with my S3 @183 days
[Galaxy S III General] cammel:
Sorry I quote myself but one of the screenshots I uploaded had the imei number and I forgot to remove it before posting it, so I had to delete it and now since I'm on tapatalk I can add pictures to that post, so I have to write a new post.. :p

Well, here are all the screenshots again.. Sorry about that! :rolleyes:

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] guerouig:
Yes, I confirm : for me as well it worked like this, everything back to normal with kies, ota and the lot.
[Galaxy S III General] siavash_Skh:
Deleted

Sorry
[Galaxy S III General] montage mahal:
+1 :D
[Galaxy S III General] jimbo77:
Well mine is affected too. I've got a 2, I've flashed latest Siyah Kernel and Recovery and my phone was manufactured back in June 2012. So I recently broke the 180 days mark... Let see if my phones survives with the patched kernels :)
[Galaxy S III General] quebec1:
excuseme where do you used the everoot option?
[Galaxy S III General] bobmatu:
ok i have uploded the boot file from firmware I9300XXELLB
[Galaxy S III General] lukesan:
Hey all,

Just received my brandnew S3 from amazon.de yesterday.

Now I had been reading about this bug, if you can still call it a bug that is, so I did a OTA update to 4.1.2 and factory reset before I began installing stuff.

Now I checked the emmc and you guessed it, the famous one and also hw ver 1.1 which I am not happy about at all.

I already had 2 reboots with the screen on, so does this have anything to do with the whole thing of that nand or the hw version?
[Galaxy S III General] danarama:
Reboots? No
[Galaxy S III General] cammel:
Is one of the options of mobile Odin pro to always keep root when flashing new firmwares

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] quebec1:
so if I understand you used triangle way, you reset the counter, and you flashed a stock rom with mobile odin pro using the option everoot, to keep the root on the new rom and the counter is still zero?

it's alright?

which version of mobile odin pro did you use?

I have a xxella bootloader, think that this procedure will work for me?

sorry for my english
[Galaxy S III General] philgalaxs3:
OK : Seems to be the same as XELLA and XELLC
[Galaxy S III General] cammel:
Exactly. All you understood is right!

I'm using the latest version of mobile Odin pro from play store cause I bought it long time ago (v. 3.57 is the newest) and I also have XXELLA bootloader, so should have no problems at all. The flash counter should be on 0, official status on bootloader and also normal status under setting/about/status and still your phone should be rooted! :D

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] philgalaxs3:
XXELLA bootloader does NOT contain any fix ! so why are u happy to have it ?

mobile Odin pro does NOT flash the bootloader !?
[Galaxy S III General] quebec1:
others questions:

1) but after used triangle away, the phone reboot in download mode, at this point How do j use odin mobile pro?

2) i restat the phone with my cooked rom and after i use odin mobile pro?

3) but if j restart the phone with my cooked rom, the counter not immediately return to one?

sorry for my english
[Galaxy S III General] erikrh:
duh

hi, i just bought this cellphone and i wasn't aware of this "sudden death" thing until now :crying: so i read the OP but i'm still kinda confused :silly: my chip type is the affected one but my stock rom is XXELL4 and my phone is rooted, so, am i "safe" ? :confused:

thank you!
[Galaxy S III General] Scarface1991:
What Kernel are you using? If you use the Stock XXELL4 Kernel then you should be safe.
[Galaxy S III General] montage mahal:
Why not have it? Did samsung release it for nothing? It only triggers your flash counter if your on a custom recovery, or kernel.
[Galaxy S III General] cammel:
I never said I'm happy to have it.

I only explained what my phone's situation is.

I don't care about the bootloader cause I don't use any custom kernel or recovery. And there is no evidence that this new bootloader doesn't or does fix the sudden death problem so... What's the problem of having it? Does it bothers you in any way?

And I know mobile odin doesn't flash bootloaders, I never said I flash the bootloader using it.

If you read what I said before, you'll see that I explained that I flashed XXELLA using pc Odin so the bootloader got updated, then I reset the flash counter with triangle away and THEN I flashed XXELLC firmware with mobile odin pro cause the bootloader was already updated. I just said that to help others to have their phones rooted but with the flash counter at zero and all of the phone status to original (in case they have to take it to the warranty) unless of course they flash a custom kernel or recovery, but I don't personally need any custom recovery or kernel.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] invinciblecc:
Oii

Those roms are for 4.1.2 based roms

I am on 4.1.1

Tell me which 4.1.2 rom to flash first I don't want to flash the new bootloader and would like to keep root and swap support if preferable ill keep phils recovery and yanks kernel So please suggest which 4.1.2 rom to flash which

1) has multi window features

2) has swap support

3) is supported by yanks 555 kernel thanks

￼

4) doesn't need the new bootloder

---------- Post added at 10:18 PM ---------- Previous post was at 10:05 PM ----------

Need to ask and confirming something

Turn on show touches in development options

Try to keep two index fingers or two thumbs of your both hands on the screens edge then move them towards the center till they are just about to touch and now notice the behaviour of the two dots they merge before the fingers touching my case,try to love them apart and they will still show one dot..... Is it the case with everyone or is my display affected as i sleep over it anyone?????
[Galaxy S III General] philgalaxs3:
OK no problem . As you are a senior member I just want to know if I miss something .

It doesnt bother me you have it .

---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------

post 1 said : "Do I need any particular Bootloader? No - There is no evidence to suggest this fixes anything"

and I did nt see somewhere any advantage to have this bootloader . Have you seen ? (could be interesting ...)
[Galaxy S III General] erikrh:
yes, i use the stock kernel, good to know i'm safe, thank you! :good:
[Galaxy S III General] danarama:
There no advantage to the new sboot. There are disadvantages for those who see and want the benefits of custom kernels and recoveries
[Galaxy S III General] shaq89:
CF-Auto root

If I root with cf-auto root (without cwm), am I safe, or I need to have custom kernel and custom recovery?

Thanks.
[Galaxy S III General] montage mahal:
No one knows for sure if the new sboot has a fix or not. It doesn't bother me as i don't use a custom kernel or recovery and doesn't affect my flash counter. But then again every ones different :)