yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] doromax:
Ok, thanks. But maybe my question is no so well explained.

Is recovery part of the Bootloader ?

If I install the new bootloader XXELLA, I install also the recovery stock ?

Or Bootloader and recovery are two different things ?

I hope now my question is clearer ....
[Galaxy S III Original Android Development] slaphead20:
29W86413BJ2527235

Thanks for the kernel and fixes :)
[Galaxy S III Original Android Development] flight23:
Deleted because topic will be continued in Ultimate thread
[Galaxy S III Original Android Development] siavash_Skh:
Bootloader and recovery are two different things

Recovery is which we install zip package with it ( going to recovery = power off phone > holding Volume up + Home + Power )
[Galaxy S III Original Android Development] danarama:
Yep. It is bootloader that boots you into either android, recovery or download mode.
[Galaxy S III Original Android Development] ggnoplay:
I have a question in here. Using phone on OS is safe, recoveries that dont have fixed kernels are not safe. All understood.

What about I switch off my phone and plug in?

Is that big green battery charging icon delivered to the screen by OS based or recovery based software? I know that there is nothing related with memory read write in this case, but people were saying the SDS is caused by faulty chargers also. Thats why I'm asking.

Are we safe charging our phones while switched off?
[Galaxy S III Original Android Development] danarama:
This is a good question because it does indeed appear that the charging mode operates a kernel.
[Galaxy S III Original Android Development] eruben:
I'm still affected according to exynos-mem-bug-checker. Is that ok?
[Galaxy S III Original Android Development] tomertb:
hi if i use sotmax v12 and i flash the latest peresus kernel i'm safe from sds?

or do i need to also change the rom?

thanks
[Galaxy S III Original Android Development] drakester09:
App is no longer useful at diagnosing. Try rooting and it will fail regardless of the status displayed.

Kernel should be enough. Remember to update your recovery as soon as an update is released.
[Galaxy S III Original Android Development] STELIOSFAN:
You are referring to the ExynosAbuse exploit right? Then, it has been stated hundreds of times, in all threads, that this app doesn't check the exploit correctly. Use Chainfire test APP.
[Galaxy S III Original Android Development] 80000037:
Hi, is the latest Perseus kernel has succeed cracking the ExFAT error on 64GB microSD cards?
[Galaxy S III Original Android Development] kadopt:
I tried this kernel and the phone just gave a black screen after the bootloader splash screen. ROM is temasek cm10.1 and it worked with stock, siyah and temasek custom kernels. Also tried to flash rom first then the kernel but had the same results. Recovery is v 6.0.2.7. Thanks
[Galaxy S III Original Android Development] 17RoiDavid:
How long we have to wait for a samsung official update with these fixes? Thx guys!
[Galaxy S III Original Android Development] krivinash:
i need some help!

i ve downloaded new kernel which is .zip .TAR version.

i want to flash it via PC Odin!

do I need to extract it from zip package, or not?

When I try to browse it from PDA, it doesn reckognize unziped one. Just ziped ( compresed ) version.

am I doing something wrong?

please help.

im on stock XXELLA and not rooted phon!
[Galaxy S III Original Android Development] flight23:
When flashing via Odin you have to use the .tar file for flashing.
[Galaxy S III Original Android Development] yahyoh:
read the OP
[Galaxy S III Original Android Development] KS_Ho:
If you want to flash the .tar version use Mobile Odin/PC Odin, no need to extract anything.

Use Recovery to flash the .zip version
[Galaxy S III Original Android Development] eruben:
Exploit status: fail. Which means I'm ok?
[Galaxy S III Original Android Development] G1032:
Oh my God.........
[Galaxy S III Original Android Development] Tyrigi:
In eMMC check i have "Brick Bug? "No. Sane chip." So i don't need the fix right?

Edit: sorry now i've read to ignore it.
[Galaxy S III Original Android Development] kadopt:
Thanks for the info. I rushed in because of the emmc fix. It seems temasek added the fix to his kernel.

Cheers
[Galaxy S III Original Android Development] jeromechrome1:
Can someone help me out here? FM radio is not working. When i turn it on, i hear nothing. It does not force close it just wont work. Im running latest perseus kernel.
[Galaxy S III Original Android Development] STELIOSFAN:
Yes. This is CLEARLY stated in the link that I gave you
[Galaxy S III Original Android Development] yahyoh:
disable dac direct :rolleyes:
[Galaxy S III Original Android Development] Kaydin:
Hello, Andrei!

I was wondering why don't you add the lulzactiveq governor to Perseus. From my testing, lulzactiveq turns off cores dynamically, instead of waiting for an action to happen (like locking the device). Wouldn't that actually use less battery, by just turning off the unneeded cores ? I noticed that pegasusq always keeps the cores on, and I find that pretty draining for the battery. Do some testing too, to confirm this.
[Galaxy S III Original Android Development] tntgdh:
How unlucky you got to be to have a sds on the exact time you are inside the recovery ?
[Galaxy S III Original Android Development] thekoRngear:
DAC Direct enabled. No prob in hearing FM.
[Galaxy S III Original Android Development] Lither:
I want to know about this as well, I want to use dual core instead of quad core to save battery
[Galaxy S III Original Android Development] GrayJack:
STweaks -CPU Hotplugging - Maximum CPU Lock - 2 cores
[Galaxy S III Original Android Development] Kaydin:
No need to do that, since the kernel will ramp up the CPU to all cores when needed, and when there's no need, it'll disable a maximum to 3 cores. Yeah, that's what lulzactiveq does. Never seen pegasusq doing that.
[Galaxy S III Original Android Development] GrayJack:
CPU Hotplug adjusting if you want it (the most easy way - as I mentioned earlier in post or fine adjusting using all settings).
[Galaxy S III Original Android Development] Kaydin:
Yeah, I know, but I thought that more users may find that more appealing instead of having to change the settings.
[Galaxy S III Original Android Development] danarama:
It only has to happen once. How unlucky are you for anything? If there's a risk - mitigate it.
[Galaxy S III Original Android Development] GrayJack:
There is no way to make everybody happy. So if one wants to perform something special - he has all tools for that.

As for me - I cannot see any use of governor if it's advantages mentioned by you can be adjusted manually.
[Galaxy S III Original Android Development] gekap:
ARDH 17.1 + Perseus 31.2 ?

does it make sense to flash Perseus kernel 31.2 to my SGS3 currently running ARHD 17.1 and Perseus 29? does that work? I'm happy with ARHD 17.1, and I'm only thinking about this because of the fix for the "sudden-death-bug" in 31.2... many thanks for info! gerald
[Galaxy S III Original Android Development] Thin_Bezel:
I thought that sTweaks is only for siyah kernel, no???
[Galaxy S III Original Android Development] fifamaniac:
Nop... it works whit perseus too... im using it!!!

Thanx
[Galaxy S III Original Android Development] T0xic4u:
You can use STweaks for Perseus too

Taper di Tap with my S3 @177 days
[Galaxy S III Original Android Development] Philips9:
it is advisable to flash it on AHRD v.18 with the stock kernel and bootloader BLH1, baseband and built ELLA ?

thx in advance
[Galaxy S III Original Android Development] agam1308:
No, is for siyah AND perseus kernel.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] siavash_Skh:
Hi

Im on ELLA Stock (rooted) + Stock Kernel

I installed eMMC bricking check and its the result.

So Im safe or not ?
[Galaxy S III Original Android Development] Chris_84:
Please use search. Been answered couple of times.
[Galaxy S III Original Android Development] Bäcker:
probably. You have the vulnerable chip but the new kernel should protect you
[Galaxy S III Original Android Development] danarama:
Answer is in post 1.
[Galaxy S III Original Android Development] siavash_Skh:
I know that the stock kernel of XELLA is safe but my question is what the app show us, only it show that my phone is a case that is on risk of death so I must use a safe kernel, or it show me that now my phone is protected or not ?
[Galaxy S III Original Android Development] donteo:
The app is made for SII so use it only to see your chip model !
[Galaxy S III Original Android Development] koolshubh:
I have a question in here. Using phone on OS is safe, recoveries that dont have fixed kernels are not safe. All understood.

What about I switch off my phone and plug in?

Is that big green battery charging icon delivered to the screen by OS based or recovery based software? I know that there is nothing related with memory read write in this case, but people were saying the SDS is caused by faulty chargers also. Thats why I'm asking.

Are we safe charging our phones while switched off?
[Galaxy S III Original Android Development] danarama:
It shows you the chip type which you compare to post 1...
[Galaxy S III Original Android Development] siavash_Skh:
Thanks a lot for your answers.

I have thanks limitation :(
[Galaxy S III Original Android Development] danarama:
Why have you posted question identical to ggnoplay?
[Galaxy S III Original Android Development] psyntific:
No you're not safe..

Sent from my GT-I9300 on ARHD 18 with perseus 31.2
[Galaxy S III Original Android Development] 80000037:
I believe the problem with the non-patched recovery is not that you will get SDS while you are idle (doing nothing) in recovery mode.

The real problem is when you use recovery mode to flash something into the emmc (rom, kernel, mod, etc).

If the recovery kernel is not patched, it might trigger the SDS when it write data to the emmc.
[Galaxy S III Original Android Development] koolshubh:
Cause I same have the question and looking for the answer....

And this ques was left unanswered... :)
[Galaxy S III Original Android Development] qwerty12:
OS-based. /lpm.rc (the init.rc file that is read in the LPM mode to decide what programs to start) is in the kernel's ramdisk and /system/bin/playlpm (the charging animation program) is on the, well, /system partition.
[Galaxy S III Original Android Development] DaReDeViL:
There is a bug when minute beep is enabled in call settings, it drops network signal at 00:59 of call duration.

I remember this bug was first seen on S2 jb rom xxlsj and i'm surprised to see it on S3 and only with the latest perseus. Maybe it has something to do with update7 ? I will try another kernel based on update7 ....

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] tntgdh:
You couldn't be more right my friend. I will avoid recover until it is fixed.

---------- Post added at 02:56 PM ---------- Previous post was at 02:54 PM ----------

Well I don't always get into recovery, but when I do, is for less then a minute. ...
[Galaxy S III Original Android Development] siavash_Skh:
But another members said that I am at risk but by using the stock kernel of XELLA I am protected ? dont you agree ?
[Galaxy S III Original Android Development] danarama:
This kernel protects you (who would otherwise not be safe) from the eMMC failure. These fixes come from Update 7 of Samsung's source code, which we assume ELLA Kernel is built from.
[Galaxy S III Original Android Development] psyntific:
yeah you're protected with stock ella or perseus 31.2
[Galaxy S III Original Android Development] koolshubh:
So wts the conclusion in simple words??

I really did not get u.... :p

Sorryy..
[Galaxy S III Original Android Development] cammel:
I don't get it either...

I'm on stock ELLA with stock kernel, rooted but with stock recovery (using cf-auto-root), so am I safe or not??

Is the fix included by samsung on this ELLA kernel or only perseus has it included??

Thanks in advance for the help!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] siavash_Skh:
Thanks, so far now, the only kernel that 100% we sure about that is Perseus!
[Galaxy S III Original Android Development] 0mega007:
Hi, im on stock ICS and have the affected EMMC, how can i download or apply the official samsung solution to the SDS (From my PC) and keep the stock kernel and current ICS ROM?
[Galaxy S III Original Android Development] jeromechrome1:
I disabled DAC Direct. Still no sound. :(
[Galaxy S III Original Android Development] siavash_Skh:
My question is when we flash the cf_auto_root, it dont make any change in stock recovery or it has an old stock recovery and after rooting it flash that old one (that may not be safe) ?
[Galaxy S III Original Android Development] DaReDeViL:
Edit : flashed boeffla latest kernel and the bug is gone ...

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] thekoRngear:
I guess Boeffla now has this too.
[Galaxy S III Original Android Development] siavash_Skh:
You have 2 choice

1. upgrade to a JB rom and then flash perseus 31.2

2. upgrade to lasted official XELLA ROM and use it with stock kernel or perseus 31.2 .

In both of them recommended to do not flash any custom recovery yet.
[Galaxy S III Original Android Development] __Michael__:
Why 30.2 and not 31.2?
[Galaxy S III Original Android Development] ggnoplay:
Hope someone can answer this.

@AndreiLux You are just awesome! I have no warranty in my country since I bought mine from Germany, and you, sir, saved me from loosing my 4-month-old S3 :) Really good developer who likes to do what he does precisely. Thanks a lot :)

Can you please answer my question also? :)
[Galaxy S III Original Android Development] cammel:
Same here... Can please someone answer this? Thanks a lot!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] mamba720027:
From what I gather if you're in recovery/boothloader mode etc from any type and kind of recovery,you're at risk. Don't think its a big deal as it sounds cause who uses recovery mode extensively.

All peeps need to do is flash Perseus or any kernel with the fix and you're safe.

Too many paranoid questions and it all leads to same answer :D
[Galaxy S III Original Android Development] MuertoKo:
Do a search on this thread on Andrei's posts, get alreay gave a big explanation on why he wont add lulzactive.

To sum up, ot does nothing you can't do tweaking pegasusq so why adding it?

Been answered many times so please read back, you can as well pm me if you want to ask in Spanish ;)

But answering it easy, there's no safe recovery right now

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] duowing:
If I remember correctly, I thought AndreiLux had mentioned something about the custom recoveries basically having their own kernel that they run when you boot into them. So that way they're able to run, I remember him making a mention of it at least on the Note at some times conflicting with your primary kernel. So that might be why right now stock recovery is the only one that's safe?
[Galaxy S III Original Android Development] siavash_Skh:
Sorry, It was a mistake, I corrected it.
[Galaxy S III Original Android Development] mamba720027:
Its the opposite of being safe. Because they contain their own kernel,the fix is not incorporated and is the reason why any recovery at the moment is not safe except "LLA stock and onwards" as mentioned in the OP.

Edit: so its best to install any updated ROM that have the stock XXELLA firmware update with Perseus.
[Galaxy S III Original Android Development] wooptarik:
true, looks like Philz is updating his touch recovery with Latest LLA fixes for SDS, will be up soon
[Galaxy S III Original Android Development] eruben:
Is there a way to flash stock LLA recovery over currently installed CWM 6.0.2.7 without installing stock firmware?
[Galaxy S III Original Android Development] Lither:
So using lulzactiveq will not lag as it will uses more cores when needed but pegasusq limits how many cores can use?

I'm using the default settings in STweaks, any settings I should change?
[Galaxy S III Original Android Development] GrayJack:
Yes, use Moble Odin, take a stock firmware and clear everything excepts "Recovery" field.
[Galaxy S III Original Android Development] johho:
Reading trough the forum I'm getting the impression that in the next 1h many thousands gs3 have to die because they don't have to newest fixed cwm or kernel.

Everyone is in total panic.

Guys think of how many thousands times you already rebooted into cwm or flashed your Rom before without that it's got sds.

So you can be pretty sure you will survive another day without a fixed cwm.

I think the danger of bricking your device when only to get newest cwm you flash a stock Rom again followed by a custom Rom again followed by flashing the kernel again is much bigger than if you just wait until your custom cwm is updated with the fix.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] mamba720027:
I guess Andrei don't consider those governor functional enough to be compatible with our current CPU logic,from what I gather by reading the quoted statement about governors below.
[Galaxy S III Original Android Development] cammel:
I was going to ask something similar... I'm on stock ELLA rooted with cf-auto-root as it installs a stock recovery but I guess not the one from ELLA, so the question is, can I use mobile Odin to flash ELLA recovery on top of whatever recovery cf-auto-installs? Can the special recovery that mobile uses to flash things damage my phone?

Thanks a lot in advance!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Scarface1991:
I think the safest bet is to not flash anything right now through cwm until it gets updated and then just flash the fixed cwm. I wanted to flash a new ROM today but I think I will hold out until CWM Recovery gets an update.
[Galaxy S III Original Android Development] Striatum_bdr:
Stop with all this!!

Thus thread is a kernel thread! Just wait until recoveries are rebuilt against correct sources and you'll just update it as usual! And till then don't use your recovery that will be enough to protect your phone! If you don't use it it can't damage anything there is no magic in there.
[Galaxy S III Original Android Development] Entropy512:
WRONG. The fix is applied when the kernel BOOTS, not when it is FLASHED. So there is no need to reflash Perseus every time you enter recvoery. You only need to reflash it if you flash or nandroid-restore something with another kernel.

Could it be that mfc-secure stuff? I haven't had time to really poke it, but I'm assuming it's somehow DRM related (and right now why I suspect Netflix's JPlayer bombs on CM10.1)

Older Samsung devices (I9100, I777, N7000, etc...) didn't use their recovery partition at all - recovery was in the main kernel partition.

All Exynos 4412-based devices I know of actually USE their recovery partition.

Agreed.

You should try reading.

Which is clear evidence that you didn't read. If you had read you'd know that on I9300 it is only used to display model/fwrev as the app is MEANT TO CHECK FOR A TOTALLY DIFFERENT BUG. The app is designed for last year's Galaxy S2 "Superbrick" bug - NOT this one, the only reason for its use in relation to THIS bug is because it is the easiest way to get model/fwrev.

You should never do this. A user will take your simplification and assume it as truth, and that's where blatantly false rumors start. Like this whole bootloader bull****. For something like this, one must be clear and precise.

Actually not true - it's for any kernel that implements its interface. My old Daily Driver kernels supported its predecessor ExTweaks.

However there are a variety of barriers to officially supporting it in CM, and there were a number of issues I had with its default handling (defaults were stored in an XML in the initramfs instead of read on first boot - so were not compatible with stuff like ASV), so I never resumed support for it in ICS. The default handling might be fixed now, dunno.

I wouldn't claim 100% sure. We're 100% sure it has the Samsung Update7 patch. I would NOT trust Samsung to the point of claiming that we're 100% sure that patch is a robust reliable fix. Samsung's got a long track record of non-robust/unreliable fixes (like their first proposal for a Superbrick fix to the community...)
[Galaxy S III Original Android Development] Nees3:
Everyone is talking about the LLA kernel, and OP states kernel 31 and above has the fix. Then... this means I9300XXELKC (Build Date: 30-11-2012) also contains the fix, because......... The kernel is also 31! So what info is correct? Something doesnt fit here. And OR Kernel 31 + higher changelist from LLA or its kernel 31 disregarding changelist? The changelist from ELKC 566833 , starts with a 5, the LLA has a changelist that starts with a 7. Is this related to UPDATE5 and UPDATE7 and only update7 contains the fix? If so, then the info from OP is wrong.

Can anyone clarify this?
[Galaxy S III Original Android Development] bala_gamer:
Using persues latest and i feel charging is slower than before? is it just me or some other noted this too?

---------- Post added at 09:27 PM ---------- Previous post was at 09:23 PM ----------

stock LLA and above + persues 31 and above have the fix!
[Galaxy S III Original Android Development] thekoRngear:
Nah, mate, not happened with me. I had it flashed with 56% discharging and it went smooth. The slow charging however would occur whenever I flashed a new rom and siyah (full wipe).
[Galaxy S III Original Android Development] bala_gamer:
to be more precise its super slow until it reaches around 50% margin then its fast. CHecked the current with power widget and its 999mA, Nothing draining the battery in the bg too... hmm weird.
[Galaxy S III Original Android Development] pRo_lama:
Guys, I have stock ROM (XEO) + stock kernel + with CF Auto + CWM 6.0.1.2:

PDA:

I9300XXELKC

CSC:

I9300OXXELK4

MODEM:

I9300XXELKC

I want to know if I only need to flash Perseus kernel or I'll need something other from XELLA firmware ??? Becasue I don't want to flash FW from my region (ORS) because of bug with WiFi and also I don't want to change CSC to BTU. (if it necessary I will change XEO to BTU).
[Galaxy S III Original Android Development] mamba720027:
I haven't notice this but I only charge fully onetime on AC outlet power with the latest thus far and I'm not using Samsung stock charger.

I notice one time while charging the frequency stock on maximum which was 1704 for me but I was doing some undervolting mostly at the time. It was probably random glitch caused by the messy trial and error test for stability I was doing.
[Galaxy S III Original Android Development] Scarface1991:
Flash Perseus and you should be good. Note however that the CWM recovey is still not safe yet.
[Galaxy S III Original Android Development] AndreiLux:
The app didn't change at all but I just switched over to dynamically generating the xml on first boot and a few other stuff in the action script implementations that makes it much more flexible than how it was in the ExTweaks times. Anyway all those problems are non-issues now for me here.

I'm happy to see people are barging in the last few pages asking questions that I already answer in the OP...
[Galaxy S III Original Android Development] mamba720027:
If you were charging from below 20% it would take some time esp if the device gets warm while it is chargeing. Mine normally takes a while like hour an half if I drain it to 1% and recharge and in between it speedsup then slows down around 90%
[Galaxy S III Original Android Development] fifamaniac:
Dont waste ur time answering anymore, i guess u are busy enough working to give us the best kernel from u.

Thanx by your really hard work... guess some persons dont know how coding its sometimes difficult and that u are doing this completely free for all of us...

Im a Omega user and the members sometimes ignore the qustions that have been answered allready on the OP or in the FAQ, and they do it weel done...