yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] sotmax:
My friebds just flash XXALEF bootloader provided few pages back.

I will added also in op for not searching.

This will remove exclamation mark from splash image and will not increase binary counter every time you use root so no increasing number in super su also.

Will let you feel free to use your device away from death bug and also one more you can reset counter better to go to service if you beed to.

Some ppl claim that is not the bootloader but hw issue.

This one is really hard to believe as it can happens to a 3 months old device or even in a 6 month old device but ir CANNOT in both 3 month and 6 month almost the same date.

Think of it ;)

) ) ) over the air fom galaxy siii ( ( (
[Galaxy S III Android Development] donteo:
Sotmax v13 will have new bootloader or the XXALEF ?
[Galaxy S III Android Development] sotmax:
Bootloader via odin my friend....

) ) ) over the air fom galaxy siii ( ( (
[Galaxy S III Android Development] donteo:
I am on last bootloader i cant install XXALEF i get i fail :\
[Galaxy S III Android Development] sotmax:
Ofcourse its fixed...we have work on this hardly from first hour especially Yank....

View attachment 1619398

) ) ) over the air fom galaxy siii ( ( (
[Galaxy S III Android Development] sotmax:
No problem my friend...

Nothing is offtopic here...

I m happy to discuss whatever here....is a free thread :)

) ) ) over the air fom galaxy siii ( ( (
[Galaxy S III Android Development] sotmax:
No nothing my friend ;)

Continue life :) :)

) ) ) over the air fom galaxy siii ( ( (
[Galaxy S III Android Development] buster041284:
I like reading threw this thread got say sotmax your a good person always understanding and helpful and so calm going to try your ROM again as I am on foxhound just want something different as DSA ROM is no more we lost a good dev keep up the good work my friend
[Galaxy S III Android Development] omek07:
Where i can found this application to check for exynos bug???

thank you

EDIT i found on google play
[Galaxy S III Android Development] wooptarik:
Thanks Sotmax, I've definitely made my mind to flash old bootloader thanks to you :thumbup:
[Galaxy S III Android Development] PearLRoX:
yes in Play Store..

i try the app to .. and my S3 got the Exynos Bug -_-'
[Galaxy S III Android Development] enigma1981:
So is ALF6 considered a 'safe' bootloader?

Swyped from my Galaxy SIII using Tapatalk 2
[Galaxy S III Android Development] buster041284:
so just to be clear i flashed ELLA bootloader to stop the death bug so i can flash i9300XXALEF_sboot.tar and i can reset counter and no red icon on boot and still safe from the death bug still
[Galaxy S III Android Development] hamma:
I use 2.8g and the Check app says my phone IS affected.
[Galaxy S III Android Development] bone069:
Same here :confused:
[Galaxy S III Android Development] buster041284:
Try

ELLA kernel check again
[Galaxy S III Android Development] ajwconsult:
the bug checker is on the play store
[Galaxy S III Android Development] donteo:
How you flash XXALEF after ELLA i use odin place .tar in pda and get fail and after that phone get error and i have to flash all from start ...
[Galaxy S III Android Development] bone069:
Yank explained in his thread that the app does not check the fix included in the new kernel. There is another possibility oft chainfire. I think the fix is working in 2.8g as well.

---------- Post added at 08:23 PM ---------- Previous post was at 08:21 PM ----------

I think there is no way to downgrade from XXELLA. I am having the same issue and the red exclamation mark as well.
[Galaxy S III Android Development] donteo:
anyone try this http://xdaforums.com/showthread.php?p=36315180 ?
[Galaxy S III Android Development] buster041284:
No I was asking can I flash XXALEF after iv flashed ELLA
[Galaxy S III Android Development] donteo:
Not you will get an error :\
[Galaxy S III Android Development] Ra1n3R:
Same here

Any other ideas to loose this damn mark? :(
[Galaxy S III Android Development] sotmax:
You simply cannot my friends :(

I right this in my warning post :(
[Galaxy S III Android Development] Morts:
I don't care about count or red exclamation, because I don't have samsung warranty...ELLA is a safe bootloader?
[Galaxy S III Android Development] sotmax:
This is in third post but took it also from here

Grab it from the attachment
[Galaxy S III Android Development] PearLRoX:
Maybe helps this ??

http://xdaforums.com/showpost.php?p=36250846&postcount=1904

"I used to get the red exclamation mark on my phone from the very first time I rooted and flashed custom Roms or kernel.

I haven't flashed this new boot loader but for those trying to get rid of it follow these steps:

- Use Triangle Away to reset the flash counters, and pull the battery immediately after rebooting starts

- Boot into recovery and perform a wipe, and pull the battery immediately after rebooting starts

- Go to SamMobile and get the stock firmware for your region

- Flash that stock firmware on your device

- Let Android boot, go through device setup (without doing any logins) until Android is fully usable again

- Reboot

- Wait at least 10 minutes

- Check Settings->About device->Status and make sure Device status is not "Modified"

- Perform another factory reset

- Boot into download mode and make sure the flash counter and system status are all set to official

These steps are given by chainfire and they helped me get rid of it. But main thing is to make sure not let your phone boot after resetting counter and wherever it says to pull battery do it as said and wait for at least 15 seconds before reinserting the battery. I had to do this whole thing twice to get it correctly. So do try this and give your feedback if it works with this new boot loader. "
[Galaxy S III Android Development] sotmax:
New bootloader is hard to get rid of it.

I try 3-4 times in a row with many combinations and always stuck at boot.

We will see

I ll try further for a way
[Galaxy S III Android Development] tarzan11:
Hey...just to give me input on resetting flash counter...

Install triangle away...

Start app first time..it downloads files to work....

Select reset counter....

Phone then boots into reset mode/push volume up to reset counter...

Dont have to pull battery...

Phone then restarts....

Immeadiately as soon as phone starts to boot..press vol down/power/home....

Phone goes into into odin/download mode....

Press volume up....

Flash counter reads 0....

Stay on that screen...connect phone to pc...

Flash official rom via odin....

Then in settings/reset/factory reset....reset factory settings...

This way bring you back to stock when needed..

I know this because i did this earlier today just to make sure incase i need to send my phone back at anytime!!

It does make the exclamation mark dissapear only if you flash official rom as steps above....

I have had the red exclamation mark for a long time because im constantly flashing official updates in between custom rom updates to test them....iv never had any problems with flashing custom roms or any other issues (sudden death)..so for me i have this red exclamation mark and will carry on as normal.....

Looking forward to sotmax v13....:):):)
[Galaxy S III Android Development] tarzan11:
Hey...instead of going backwards with the bootloader..cant we go forwards and use current ELLA bootloader!! It supposed to have solved this sudden death issue....just a thought for ALL devs to work on and make it compatable...;)
[Galaxy S III Android Development] Ra1n3R:
http://xdaforums.com/showthread.php?t=2083860

Another way to downgrade the bootloader? Some users answered that it works.

edit: it's curious... I flash the latest samsung kernel (downloaded with perka's file stash) and the exklamation mark is gone! ;) No downgrade needed..
[Galaxy S III Android Development] sotmax:
seems to work.

It have a logical explenation.

I think you can proceed...is a very nice idea and when you get at 4.1.1 proceed to go down to 4.0.4 ;)
[Galaxy S III Android Development] Yank555:
About the exynos-mem exploit, please please read this :

http://xdaforums.com/showpost.php?p=36332434&postcount=1321

Thanx, JP.
[Galaxy S III Android Development] bone069:
Maybe yank can have a look in it and compile it in his kernel.
[Galaxy S III Android Development] Yank555:
No, the bootloader needs to be flashed back by some way like this, the kernel isn't even running at that time, so there's nothing I could put in there to help flash back the old bootloader :(

I guess all Samsung has done this time is, under false pretext (sudden death fix) screw their customers into flashing a bootloader that fixes nothing and only gives them more control over your device so they can check more easily if the phone was rooted :(

I wasn't very happy with them lately because of not publishing latest kernel sources, but this will make a lot of customers angry I guess ...

JP.
[Galaxy S III Android Development] bone069:
Thanks for your quick reply. Do you know why the exclamation mark has gone after he flashed the new XXELLA kernel with XXELLA bootloader? It seems it doesn't have to be downgraded.
[Galaxy S III Android Development] _2bad4u_:
How can i see what bootloader i have is there a way to check.

Thanks
[Galaxy S III Android Development] bone069:
The easiest way is to use system info app.
[Galaxy S III Android Development] Yank555:
Because that's what it's looking for, the stock kernel ;) If it's not there, you get the exclamation mark, that's all there is about it.

From what I read, also the recovery needs to be stock for the mark not to show, but can't confirm nor deny this...

JP.
[Galaxy S III Android Development] _2bad4u_:
I have I9300XXDLIH bootloader, is it ok, or is the broken one?

Thank you very much for the help.
[Galaxy S III Android Development] bone069:
Ahh okay. So reverting back to an older bootloader does not prevent for the sod it is only to don't show Samsung in time the warranty should be required that there was flashed a custom Rom right?
[Galaxy S III Android Development] blyx21:
As long you dnt have the red ! Your ok if ever you do have red ! Go flash old boothloader.

This thing is for warranty purpose.
[Galaxy S III Android Development] _2bad4u_:
I also have the red ! mark when phone boots. I have the phone for 2 months now and no warranty. I hope i don, t get that death probleam.

By the way your v12 version is running great sotmax. Thank you.
[Galaxy S III Android Development] tarzan11:
hey....just to confirm i have now NO red exclamation mark.....

After flashing ELLA official update i was curious if reverting back to ICS 4.0.4 would work....

I can confirm that flashing via pc odin has worked for me..

I was on ELLA official update and then rooted...

Installed triangle away..reset flash counter...

Boot into odin/download mode...flash counter read 0....

Stay in odin mode....

Connect to pc...flash ics 4.0.4.....(XXBLG8 BTU) in my case...

After set up...boot into stock recovery..factory reset...wipe cache..

Boot into odin/download mode and install 4.0.4 bootloader from sotmax rar link from earlier...page 362...

Then root...installed V12 and now i have NO red exclamation mark.......

Also after root and installing v12 my flash counter is still 0....

And after checking..my bootloader is now XXALEF...

Edit; Just to update that i first installed ELLA official with MobileOdin...not sure if above method works after you have installed ELLA official via pc Odin.....
[Galaxy S III Android Development] Yank555:
Well yes and no, devices affected, again from I read so don't take this for gold, were running newer (e.g. JB) bootloader, so it could be the JB bootloader had a flaw that cuased the sudden death, and ICS ones don't ...

But that's a hard call and a mere guess at best.

I believe it is a hardware problem, and there is no "software" cure for it, only Samsung pushed people to upgrade so if they have a dead device they can deny warranty more easily, which in most parts of the world is true, unfortunately.

But if you live in the EU, read this :

https://fsfe.org/freesoftware/legal/flashingdevices.en.html

JP.
[Galaxy S III Android Development] MRDOCA:
So still confused... is my bootloader ok?

I9300XXALF2
[Galaxy S III Android Development] Yank555:
That's a good old one, I'd keep it if I were you.

JP.
[Galaxy S III Android Development] corrsea:
That's what I'm on:) and I'm staying with it.

ROM Sotmax Ultimate V12

Kernel Yank555.lu-V2.8g
[Galaxy S III Android Development] MRDOCA:
Thanks yank. I still dont think its software related lol
[Galaxy S III Android Development] sufi37:
anyone have sotmax default setting for yank555 kernal??
[Galaxy S III Android Development] rekenaar00:
http://xdaforums.com/showpost.php?p=35905148&postcount=3081
[Galaxy S III Android Development] haspko39:
What about my I9300XXDLJ1? I have red Mark! too. What should ı do? :confused:
[Galaxy S III Android Development] AladdinZ:
Hi Sotmax, I have I9300XXBLFB bootloader as I mentioned in a few pages back, I think its the one my phone came with. When I bought it here in Maldives it was XXBLFB meaning its Europe (XX) and ATO firmware which indicates its an Austrian device right? Since then I have been messing around but I think its the same bootloader since then. So its safe to keep it as it is or should I update to latest bootloader? As Yank said I strongly agree that its a hardware fault and there shouldnt be any software cure for the sudden death issue. I hope mine dont die until S4 comes out :p
[Galaxy S III Android Development] sam77744:
dear Bro,download app android system info by play store and chack system/buildnfos.
[Galaxy S III Android Development] Yank555:
It's a hard call, I don't know what's in there... but unless proven otherwise, I won't believe the sudden death can be fixed by a new bootloader, or they need to tell us exactly how sudden death happens...

I'll stick to my old bootloader for the time being.

JP.
[Galaxy S III Android Development] TAT1980:
I have tested my sIII. Withe the app.

No default on my device

Then i tried the same app on my note 10.1 3g

Your device is infected

Is there anywhere a thread for note 10.1 or is it the same way, like the steps on SIII ???

SIII device: sotmax v12, yank kernel 2.8f, I9300XXELL4

Note 10.1 3g: stock rom ( rooted ), N8000XXCLL1
[Galaxy S III Android Development] enigma1981:
Yank, what about ALF6? Is that considered "safe"?

I've asked a couple of times now but since this topic sprung up, the thread is moving a little faster than usual so my other questions have got lost lol

I've never flashed a stock 4.1.2 only a stock 4.1.1 (DLJ1 IIRC) only custom 4.1.2's (wanamlite and sotmax) ...oh and a couple of CM10 nightlies and a CM10.1 nightly but I'm sure they don't count towards bootloader modifications lol
[Galaxy S III Android Development] Ra1n3R:
Common guy's, don't break this topic here with the same questions like "what is with this bootloader...., what is with ....,". There enough topic around xda with "sudden death & various bootloader".

I think sotmax or Yank tell us the news, when they know what is the final solution to fix this problem.
[Galaxy S III Android Development] Yank555:
One last on this (off)-topic from me :

XXA.. are older bootloaders, so it's safe if you want.

Anyway, there is no "safe" bootloader in my oppinion as to sudden death, as I consider it due to a hardware flaw, unless proven otherwise, and there is no software correcting hardware flaws.

The latest is not safe in

administrative

terms, technically they all do their job, they boot your device ;)

Just that, with the latest, Samsung has broken Triangle Away, and thus you cannot reset the counter anymore (for now at least), so that Samsung can more easily deny warranty (outside of europe mainly, here you are protected, I've posted a link previously with the official EU-directive underlining this).

JP.
[Galaxy S III Android Development] tarzan11:
@Yank555...hi mate..hope ya ok....is it true that mobile odin doesnt install the bootloader when flashing an official rom with it....??
[Galaxy S III Android Development] STELIOSFAN:
It has nothing to do with the red mark / bootloader. I remember in this thread we had a discussion about the red mark (cause when I bought mine and rooted it, it had it there) and a couple of members said that their phone died (they had no red mark) and when the phone was returned fixed, it had the red mark....

I personally flashed the newest bootloader, because I can't accept that Samsung is doing that only to identify the phones rooted. After all this was happening before the latest bootloader.
[Galaxy S III Android Development] Yank555:
Never used mobile Odin, on Odin to root the S3, so can't say.

Since you're from Greece (EU), you don't need to worry either way :D

But I don't see what they could have done to fix anything hardware related in a bootloader, and I'm ready to be proven wrong ;)

If it fixes anything, knowbody knows, we don't have sources or source-diffs, plus the broke triangle away flash counter reset and blocking downgrade of the bootloader is proof they don't want you to move back and erase your trail.

Plus online press quoting "sources tell us" this will fix the sudden death, is an good way of pushing people to flash it, especially the breed of folks like us here in xda, the rooting and flashing bunch, extactly those that they could turn down warranty like this, without ever having said this "officially".

OK, I'm starting to sound like a conspiration theorist here, but this is what I believe is happening right now.

JP.
[Galaxy S III Android Development] Musko:
Dear Sotmax, when you plan publish v13 with ELLA?

Thank you.
[Galaxy S III Android Development] sotmax:
So my friends there is a big panic about bootloaders and hw generally.

All opinions accepted this time as no one true knows what happening in there and cause system to fail.

From tue other hand i m just very complicated and curious together.

Why the heck are fail from a specific date and after?

How that is hw related if a phone bought some months ago? Are they have an end date?

Keep thinking of it i can end only in one conclusion.

Its not software but not hardware also...its maybe both.

What i m meaning is that may be the system somehow fails(and fails a lot) and when turns out the new bootloader just cannot take place that time for a reason. No burned hw equipment no nothing.

Just maybe system shut down and close a door behind .

Some of you may remember the bug that affects first gnotes and when you made a factory reset the emmc fails and device locked to splash screen.

I think this is caused with the combination of the latest bootloader(not xxella) and 4.1.2 fw.

And yes as yank said and i agree sammy didnt fix anything with the new bootloader...just tracks better and can deny more devices from replacing.....

) ) ) over the air fom galaxy siii ( ( (
[Galaxy S III Android Development] buster041284:
u are mabey rightsotmax but one thing chainfire samsung underestimate the great dev's of xda iam sure they will have a fix to sort out this flash counter and red icon they done it before so just if the bootloader does fix death bug then its worth the flash
[Galaxy S III Android Development] donteo:
Sotmax when v13 will be released this weekend or other :confused:
[Galaxy S III Android Development] blyx21:
From what I see/read theres no sudden death in ics rom yet? Almost all in jb rom. Hmmm....
[Galaxy S III Android Development] buster041284:
i have a theory I9300XXELLA ment to fix sudden death but I9300XXELLA is only uk firmware so why not released for everyone all over the world does not make sense plus EU countries are protected by statutory rights even if we are rooted ot custom firmware we are stll protected reason i say this is because lot of people and dev's think samsung have done this new update to void people warranty if they have sudden death because its hardware problem not firmware i don't know what is the truth but i will say one think samsung are getting like apple which is disappointment
[Galaxy S III Android Development] heyitsmik:
Weird battery life

Hello sotmax and all,

To start off, I wanna thank you for creating this awesome ROM and this is my first ROM on my S3 (I tried V8 and never bothered trying anything else cos it seemed so perfect)

However, I just upgraded from v8 to v12 and my battery life has gotten really bad. I monitor my battery usage quite a bit and I realize that now a lot of % goes to Android OS, Android System, Mediaserver. In the past it used to be:

~60% on Screen

~5% on WhatsApp

~5% on Android OS

~5% on Android System

Now it's:

~40% on Screen

~12% on Android OS

~11% on Android System

~11% on WhatsApp

I know the ratios for WhatsApp and the 2 Androids are the same, but my usage has not changed much. And I noticed that my phone heats up a lot quicker than it used to. Plus now I'm using WiFi for more than half the time, compared to the past when I use HSDPA (my WiFi consumption is about half of HSDPA) and yet I went from 100->20% in 10 hours, compared to 100%->20% in 14 hours when I was on V8 (and used more HSDPA)

Oh yeah I installed quite a lot of the add-ons in the pre-booting menu, like now I have 2 cameras (the Nexus 4 one and the stock one), I have the hackers keyboard, emoji plugin etc but I almost never use those add-ons.

Anybody having the same problem with battery life as me? :(
[Galaxy S III Android Development] sotmax:
Bootloader edit is not my place to play my friend but for sure cf or someone else will find a solution

99% tonight my friend...

thats why i tell everyone to rollback to ics bootloader.

V12 is different as a firmware so in most cases a clean install is higly recommended

) ) ) over the air fom galaxy siii ( ( (
[Galaxy S III Android Development] johnzoids:
Something Strange :

Ive been using V12 since it was released, All of a sundden today morning , the phone kept on restarting itself ..

then i tried reseting cashe and dalvik and installed galaxshia kernel then i got an encryption error..and asked to reset the device .. but when tried that still got the error. i reflashed the sotmax rom and used stock kernel and then it came back to before old previous installation with the stock kernel .

do you think the yank kernel was causing a problem .. i used the sotmax setting for the kernel ..

for the last 15 mins or so no restarts ..

just feels a bit slow ..

SORRY STILL GETTING RESTARTS ..
[Galaxy S III Android Development] tarzan11:
Hey...just to remind you guyz i got rid of my red exclamation mark and flasher counter set at 0 after root..by flashing ics 4.0.4 and bootloader via pc odin...i posted how a few pages back....;););)

---------- Post added at 01:47 PM ---------- Previous post was at 01:30 PM ----------

Hey...just to confirm MobileOdin Does Not install bootloader when flashing official rom...iv just reinstalled ELLA official with MobileOdin and my bootloader is still the same (XXALEF) after running Android System Info from playstore...

---------- Post added at 02:09 PM ---------- Previous post was at 01:47 PM ----------

Now rooting..5th time in 2 days...am i a flasholic!!!;););)
[Galaxy S III Android Development] sotmax:
No problem with yank.

Just make a clean install and if you re on newst bootloader roll back.

Read third post if didnt see that again ;)

) ) ) over the air fom galaxy siii ( ( (
[Galaxy S III Android Development] selami023:
Guys where can i see if this bootloader is an old one I9300XXBLH3?
[Galaxy S III Android Development] blyx21:
It happen to me but not like yours that restarting. Mine was keep on wakening when I try to lock the screen close the screen. then I install anti virus n scan wether there some malicious software that I install and erase some software that I currently install then wipe cache and its gone. We just need to be careful installing things...
[Galaxy S III Android Development] pradeepb:
Still wennnnnnnnnnnn?????? I m eagerly Waiting to flash my S3 with lovely v13 ;)... Before i go to office ;)
[Galaxy S III Android Development] tarzan11:
Hey...V13 wont be long guyz....;););)
[Galaxy S III Android Development] ajwconsult:
and your nice addition for us 3-uk users :)..
[Galaxy S III Android Development] pradeepb:
Its 1am in morning here.. Hope so it will be released by tom morning :) c u guys :)