yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] danieldmm:
I do not known if i9305 have "old bootloader"
[Galaxy S III General] leijonasisu:
Same thing is now happening to me.. after flashing AHDR 17.1 I now get this little exclamation mark or whatever.. I'd say it's a form of flash counter.. either way it's annoying and a dead giveaway that my phone is running a custom OS :/
[Galaxy S III General] taylor_t:
Hi,

I tried it too, but it doesn't work with PDA nor Bootloader.

My SIII doesn't boot after both tries.

Tim
[Galaxy S III General] TheFatHobbits:
I was of the understanding that the red exclamation mark indicated that you had an insecure bootloader(?) which allowed you to root
[Galaxy S III General] saebel:
The 0 folder is where your user files goes to in jellybean.Whenever you flash a new rom,the phone count you as a new user and save all your files to a new 0 folder including the old 0 folder.So,if you u want to reach download on internal SD after a flash,that would be Storage/0/download and after a second flash, Storage/0/0/download.Oh,the legacy is just a link folder to your SDs don't worry.
[Galaxy S III General] thegh0sts:
any one running the XXELLA bootloader with CM10.1?
[Galaxy S III General] lockmunk:
hey,your phone same problem with me..I flash XXELLA firmware just now..n I want to flash the old bootloader..it said fail while flashing..

what I do is flash back XXELLA firmware & everything back to normal now..but I really want to flash an old bootloader..somebody can teach me??
[Galaxy S III General] taylor_t:
Hi Lockmunk,

I'm also waiting for help :)

I don't understand how the other users could reflash the old bootloader - I don't work in my case.

The crazy thing is, I got the red rexclamation mark with fw XXELLA. I tried to flash a old FW version, but the the red symbol persists.

What the f(&*# is the difference to the the previous files? And how can I revert it?

Tim

---------- Post added at 02:53 PM ---------- Previous post was at 02:48 PM ----------

Hi @ all,

could somebody create a small video tutorial?

Maybe we can find our problem in this way.

Thanks a lot.

Tim
[Galaxy S III General] edwerd:
same issue hereeee
[Galaxy S III General] danieldmm:
I did not tryed the new XXELLA but if its like that maybe Samsung Intrudeced a new protection but its strange, you guys have ticked debug mode in settings and then flashed with ODIN ?
[Galaxy S III General] taylor_t:
Hi Daniel,

I tried it with USB debug - same result.

I tried it with old FWs and the new FW - always the same :(

The problems come from the new FW XXELLA I think.

Tim
[Galaxy S III General] danieldmm:
Thanks for the fast reply.... so if that the case Samsung made improvements to detect flash counter, thats really strange....

Maybe we have a light at the end of tunnel but its a little dangerous, my bet its to flash the old bootloader with Custom Recovery by making a CWM with the old bootloaders to flash...

But i dont know if it will work or brick the device. Any one wants to try ?
[Galaxy S III General] luismanson:
So basically we have two options now:

* old bootloader, no red symbol but maybe sudden S3 death at any time

* new bootloader, red mark but dead bug could be fixed :|
[Galaxy S III General] 75markus:
where to flash sboot.bin ?

edit : found it , can anyone confirm ?

so it shouldn´t be a problem to make a CWM zip

i´m thinking of

package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
ui_print("Installing old bootloader...");
assert(package_extract_file("sboot.bin", "/tmp/sboot.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p1", "/tmp/sboot.bin"),
delete("/tmp/sboot.bin"));
delete("/tmp/flash_image");
[Galaxy S III General] danieldmm:
tz its trust zone ...

Here you have and god speed....

https://dl.dropbox.com/u/93757059/S3/tuga_teste.zip

Lets all know if worked, in CWM Recovery i think that new boot loader will be Overwriten by the old bootloader but....

The script its very simple:
[Galaxy S III General] muscles019:
Exclamation mark !

Has
[Galaxy S III General] dkionline:
The exclamation shows that your S3 is modified. We don't know if that preventing the sudden death. We will wait for the next update.
[Galaxy S III General] danieldmm:
We are missing something or Samsung are playing with us...

Also it can be relative to partition.

In S3 we have:

mmcblk0p1 BOTA0 = sboot.bin = boot.bin
mmcblk0p2 BOTA1 = sboot. bin = Sbl.bin

Maybe we need to flash mmcblk0p2 in stead of p1.

But we are playing dangerous... :)

Cheers
[Galaxy S III General] edwerd:
:S i really wish someone could figure it out, and just create an app to auto remove it
[Galaxy S III General] lockmunk:
as long we flash custom recovery (cwm),,the exclamation mark will be there...

when i use stock recovery, the red mark not exist there..
[Galaxy S III General] gpvecchi:
Just a thinking: this thread was opened much before the new firmware came out. So the new bootloader came out before Samsung spoke about patching sudden death bug.

Ergo, the new bootloader doesn't patch sudden death issue.
[Galaxy S III General] Droidphilev:
Hi,

first of all: i'm not saying that the newest bootloader fixes anything but you are a bit wrong. This new bootloader is the third release. This thread started when JB was released, also that bootloader (2th one) had an exclamation mark.
[Galaxy S III General] danieldmm:
Thats entirely correct, this one is third generation of bootloader to our i9300.... But indeed strange things happen with this one starting with no dowgrade possible, at least atm not possible...
[Galaxy S III General] edwardtobia:
Well suppoedly its been confirmed by Sammobile that this new bootloader resolves the sudden death issue, if this is correct then it would make sense as to why Samsung do not want people to be able to downgrade, as why would they permit people to downgrade which would increase the amount of returns they will get due to sudden death?
[Galaxy S III General] 75markus:
that´s true.

my wife´s S3 came with 4.1.1., it had the JB bootloader installed by default. i flashed CWM & CM 10.1, got the red ! when booting.

flashed back the old ICS bootloader, the ! is gone after triangle away.

my phone is stuck now to the ELLA bootloader, but i honestly don´t care, i flashed new CM 10.1 today, all working fine.

no need to downgrade to old bootloader for me.
[Galaxy S III General] jinosong:
Guys, listen to this man. Flash the file in the BOOTLOADER section, not PDA. It works.
[Galaxy S III General] edwerd:
didn't work, screwed up my phonee
[Galaxy S III General] dkionline:
It's blacklisted!!! I hate some people that posting **** like that!
[Galaxy S III General] maranello69:
i have just now flashed it on my wife's phone (DLID 4.1.1) in the PDA section and everything looks fine after using TA 2.40

/le: i have just now read the last 3-4 pages, it would be great if the sudden death bug has been fixed in this last bootloader that comes with LLA, if this is the case, can anybody share this new "SDF" (Sudden Death Fixed) bootloader?

i would gladly flashed it and test it for all of us, i really don't care about that ! mark, i flashed the old bootloader just to prove to my wife that nothing is "wrong" with the phone and everything can be undone with a little patience
[Galaxy S III General] danieldmm:
Here you have:

XXELLA New BootLoader TugaPower

Just flash in ODIN in PDA section

Cheers

I will stick to the old boot loader since my phone its 32Gb version and dont have "SDF" ... (updating to XXELLA Light TugaPower with the new tz.img as we speacking) :)
[Galaxy S III General] kadopt:
@danieldmm

does this means that only the 16GB ones may die? I'm using the old bootloader (no exclamation stuff) and not sure if I should use the latest one or not...

I have a 16gb S3.

Cheers!
[Galaxy S III General] danieldmm:
Thats correct, according to Samsung only the version of 16Gb suffer that problem and its not all models of 16Gb... Cheers
[Galaxy S III General] Droidphilev:
Hi,

NOT correct!!! If you have the 3th bootloader (the one that comes with Xella) you won't be able to downgrade. If you say that it works on your phone you're using an old bootloader. There are 3 of them mind, not 2. Also check:

http://xdaforums.com/showthread.php?t=2081748
[Galaxy S III General] danieldmm:
Correct, this was before XXELLA New BootLoader, already watching @odia to see further information....
[Galaxy S III General] anonlee123:
Does any one have any idea how to flash the old bottloader?

I think LLA does not have anyway to downgrade it

Have been trying the whole day
[Galaxy S III General] RevoWution:
Would it be possible that my S III was shipped with this latest firmware that Samsung is rolling out right now? I only just got my S III about 2 weeks ago (arrived on Christmas Eve actually), and it came with JB and not ICS (4.1.1 or something if I remember correctly).

As soon as I rooted my phone and flashed Liquid-RC9, this little red exclamation mark appeared on my boot screen. I didn't take much notice of it until now. It seems like a lot of the fellow S III owners here have never seen it? :)
[Galaxy S III General] danieldmm:
Not possible atm ... :(

Read a little this thread, your bootloader you can downgrade to the old bootloader, if you flash XXELLA with ODIN you canot downgrade then...
[Galaxy S III General] RevoWution:
Thanks buddy :) I just read the entire thread.

Looks like my bootloader (I9300ZSDLK2) may not be the newest one after all. I still have the ! symptom as I have a newer bootloader (I don't mind it, to be honest), but I guess it doesn't include the Sudden Death fix. That's my main concern at the moment (16GB S III owner) :(

Cheers for the heads up regarding not being able to downgrade the bootloader if I were to flash the most up to date one :)
[Galaxy S III General] Tuurrr:
Is the red exclamation mark only visible during booting or also when you use the phone?
[Galaxy S III General] danieldmm:
Only when booting...
[Galaxy S III General] Tuurrr:
Just flashed Bootloader_XXELLA_Odin.tar (http://xdaforums.com/showpost.php?p=36258060&postcount=41425)... No red exclamation mark here?! I'm on Omega rom v35 btw...

When I use Triangle Away I see the red exclamation mark, but not on a normal boot?!
[Galaxy S III General] UrbanDesigns:
I reset my flash counter the other day using Triangle Away and had no problems whatsoever
[Galaxy S III General] thekoRngear:
I have auto reset at boot and still get that exclamation sign when booting. I can remember it just didn't happen despite using custom stuffs on ICS or jb until this new BL came.
[Galaxy S III General] overflyer:
Oh thank you so much, now the exclamation mark is back -.- (running CM10.1, had the old Old_BootLoader_i9300_TugaPower.tar.md5 on there before WHICH MADE EXCLAMATION MARK VANISH, came from stock 4.1.2 premium suite when exclamation mark first occured)
[Galaxy S III General] amviewer:
Don't know what the fuzz is about but i don't have the issue.

My counter was reset to 0 via traingle away.

Flashed XELLA via pc odin.

Cf-root 6.4 via pc odin.

Exclamation appeared.

Ran traingle away again.

Exclamation gone.
[Galaxy S III General] danieldmm:
Now put a custom recovery to flash custom rom and then tell me ...

@To all if you want do downgrade bootloader its already a solution, flash a ROM ICS that it's not BTU, then make update with OTA to 4.1.1 and new bootloader its gone, then update do XXELLA with Mobile ODIN ;)

http://xdaforums.com/showthread.php?p=36315180
[Galaxy S III General] overflyer:
I also ran triangle away, again. Red exclamation mark with the new XELLA bootload doesnt go away :(
[Galaxy S III General] amviewer:
I don't do custom roms, only stock and adjust them to my need. But yes in most cases the kernel is custom in those roms which makes the counter go up and the exclamation appears.
[Galaxy S III General] kerbiii:
Does the old bootloader dont work on XELLA?

- SIII GT-I9300
[Galaxy S III General] overflyer:
Flashing the old bootloader again gives me FAIL!

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Old_BootLoader_i9300_TugaPower.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

EDIT: Crap: HELP! My phone wont start now. a screen aapers saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.

EDIT: I just flashed the new XELLA Bottloader with ODIN again and now I got the red exclamation mark, AGAIN, but well, at least my phone works :)
[Galaxy S III General] MattBooth:
My theory is this:

The same Sudden Death problem is a godsend to us. If the motherboard dies, Samsung have very little chances of finding out that you ran custom (because the phone will not boot or power on). If anything else goes wrong with these phones we can still make it appear stock.

With this new bootloader it makes it harder to appear stock in certain situations.

I'll stick with the old BL and then if my phone bricks at least I have no problems returning under warranty
[Galaxy S III General] danieldmm:
I liked the way you think, altouth i dont have Sudden Death, if i have 16Gb version i for sure will make like you think...

Cheers

SOLUTION for the bootloader (Tanks to @Odia)
[Galaxy S III General] shahru98:
apparently i tried the old bootloader on my 16gb S3 on XXELLA and it worked. no more red ! when booting up.

im on cRdroid custom rom by the way.
[Galaxy S III General] danieldmm:
And custom recovery ?
[Galaxy S III General] shahru98:
i think im using CWM 6.0.12 or something. it came with the Samsung toolkit.
[Galaxy S III General] joaodrp:
My i9300 is with omega v36 and stock kernel, I had that red pipe after rooting the stock rom but after installing omega it has disappeared from boot, but when I enter in recovery boot it shows up. Any guesses?
[Galaxy S III General] DigiRay:
I need some help guys.

I got my Gt-I9300 in august, it's the sim free international version. It came with XXLF2 ICS I think it was. I did OTA updates up to DL4 JB 4.1.1. Everything was fine up to then. I decided I wanted to root my phone and used the Exybos Abuse app. That was fine too. I deleted some things with Titanium and then realised I had deleted 2 widgets I couldn't get back. So I flashed my phone with the same STOCK firmware I had, the DL4.

After that, entering recovery shows counter as 1 and it says modified under the Setting -> About phone -> Status.

I used Triangle away and re-flashed the stock rom. Recovery still showed counter as 1 but the Status in android said it was original. And there was no red ! at bootup.

Today, I recieved the new OTA update for XXELLA 4.1.2 but it told me to get stuffed. Downloaded the update and all ok, but when it came to installing it, it gave an error, rebooted, red ! appeared and sayed modified under the Status in Android.

I thought: I'll manually flash via odin the latest firmware for PHE Spain. That worked ok, no red ! at boot up, but status is still Modified and I lost root (due to removing the Exynos hack in this firmware I guess).

Now I'd like to be able to set my phone back to being completly stock, counter at 0 and unmodified in status.

If I understand corrently, I can achieve this by flashing my original ICS rom via odin, then gaining root from exynos abuse or a cf-root custom recovery, then I use triangle away to reset it, then I flash the old bootloader that's been posted here, then Triangle Away again, before the phone reboots I flash back to the XXELLA rom and that's it?? The phone will be back to unmodified, counter at 0 and I'll be able to do the OTA updates??

How about root? Is there a way to root on XXELLA without it showing anywhere and keeping the OTA update possibility??

Please help as I still have 14 months left on my contract permanency without being able to get a new phone replacement and if anything goes worng the warranty won't cover my phone as it stands.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III General] overflyer:
Odin 3.07 freezes while trying to flash GT-I9300_ClockworkMod-Recovery-Touch-6.0.1.9

Ok, so Im trying to Flash GT-I9300_ClockworkMod-Recovery-Touch-6.0.1.9_ODIN.tar after I rooted my new S3 black 16GB with CF-6.4-root.tar before with Odin 3.07 now for half an hour now, but its just frozen at the "recover.img" stage. No blue bar is moving at my S3 display at all of course. What am I supposed to do? If I disconnect it, I brick it right? :(

SERIOUSLY, pls help. I hope this doesnt take a day or so for anyone to read as usual :/

EDIT: I just have said it "stopped". Froze is not the right word since the gui and everything is still responding fine.

BTW: As soon as I just ROOTED my S3 with the standard CF-6.4-root file, the red exclamation mark was back. And this S3 was never custom rom flashed EVER before! Its brand new. It had the Stock 4.1.2 XELL4 on it before!
[Galaxy S III General] danieldmm:
It will not brick ;)

XXELL4 have new bootloaders, because that you have red exclation.
[Galaxy S III General] overflyer:
Thanks man, yeah good thing it didnt. Yes I know the new issue with the "!" , just wanted to say that even rooting stock is enough to cause it.
[Galaxy S III General] overflyer:
I installed the old bootloader and the exclamation mark vanished :) BTW Is it normal that ChatOn is working with CM10.1 :D ?
[Galaxy S III General] danieldmm:
Yes, chatON its not dependent of Samsung ROM...
[Galaxy S III General] stash86:
Well, 2 days ago, I decided to upgrade my rooted ICS to JB 4.1.1 via ODIN. I got no red exclamation, but my S3 status is modified. I don't know whether factory reset via KIES will help me to return my phone back to "original" status. Anyone have tried to do it before?

Edit : I just reboot into Download mode. No flash counter, all status there is "Original". So I guess I'll leave it for now, until I have time to reset it by KIES....
[Galaxy S III General] kerbiii:
Does the old bootloader will work with xellc? Or theres another old bootloader?

I flash the xellc thru pc odin, is there a new old bootloader for XELLC that can remove the red exclamation mark?

Update: the old bootloader i used before dont work anymore, it makes me reflash my rom
[Galaxy S III General] darkevilsta:
Flashed ELLA. Rooted it first with CF-Autoroot and got the red exclamation and system status modified. Used TA and both went away. Then when I flashed Philz Recovery and Perseus they came back. TA isnt able to reset either the exclamation or modified status but at least works with CF-Autoroot and the new bootloader
[Galaxy S III General] kerbiii:
I think in order to remove it i need to downgrade to 4.1.1 then flash the old bootloader then flash the 4.1.2 voa mobile odin

Can someone verify this?
[Galaxy S III General] danieldmm:
No, you can downgrade with Custom CWM, just search here in XDA and you will find.

Sent by i9300 powered wih TugaPower ROM
[Galaxy S III General] kerbiii:
What do i need to search?
[Galaxy S III General] edenk:
Thanks for sharing information
[Galaxy S III General] danieldmm:
http://xdaforums.com/showthread.php?p=36433966#post36433966
[Galaxy S III General] Paolonicus:
Just an Inquiry

I took a look on the instructions posted, but I considered the current setup that I have, and by all means I still needed Root Access. I was thinking, and I don't know if anyone had tried this. I have Mobile Odin Pro (v3.65) and it has the option of maintaining root access after flashing even with WIPE. Instead of using the regular Odin PC, I will instead use Mobile Odin with WIPE and Root Access in flashing firmwares, then after the whole process is complete, I will use the same software to flash PhilzTouch Recovery, then restore my Nandroid Backup.

Do you think this would work? :confused:
[Galaxy S III General] ereziel:
Yes, it definitelly is because of flash counter and custom firmware/kernel on it, as every 9300 I have flashed CWM now have that exclamation mark.

And as OP says, that mark is not gone when resetting download counter
[Samsung Galaxy Nexus] turdbogls:
I remember one of the first ROMs i flashed on my nexus was Code Name Android, and it had the option to hide the navigation bar on the lock screen only.

is this something that can easily be implemented into JB? i noticed it was taken off of ROMs because it interfered with incoming calls when the screen was on (wasn't able to answer call) just curious if it was ever fixed or if this is a simple mod that i could do myself with some layout tweaks or something.

anyone have a clue?
[Samsung Galaxy Nexus] gbarayah:
I use Widgetlocker - lock screen replacement app, and it has an option to hide the navigation bar. I highly recommend it, very customizable with tons of sliders/themes to choose from and is very light on using system resources and draining battery.
[Samsung Galaxy Nexus] turdbogls:
you sure about that? i know it has the option to hide the navigation bar buttons, but the black bar is still there.

i want the wallpaper to go from the notification bar all the way down to the bottom of the screen.
[Samsung Galaxy Nexus] gbarayah:
Oh okay. If that's the case then you'll need to go a different route. Widgetlocker just blacks it out.
[Samsung Galaxy Nexus] gbarayah:
Here is a screen cap of what it looks like.
[Samsung Galaxy Nexus] gbarayah:
Its not quite as bad on the device as it blends into the bottom of the phone but still not using the complete screen.
[Sony Xperia T, TL, TX, V] wemsinho:
I am still looking for How-To's for the following things:

- Unlocking Bootloader

- Root

- CWM

I really DON'T find the safe instructions for doing this. Are there some out there?

Thanks in advance!

Sent from Wemsi's LT30p
[Sony Xperia T, TL, TX, V] yesyesimanoob:
Unlocking bootloader:

Follow Sony's instructions here: http://unlockbootloader.sonymobile.com/

For the IMEI, just don't enter the last digit (the T has a 15-digit IMEI, Sony's site only accepts 14 digits) and it will work just fine.

Rooting:

Flashtool worked perfectly for me. Run it, click "Root", and follow the on-screen instructions. http://androxyde.github.com/

For the adb driver selection, choose "Xperia TX". It will work for the T.

CWM:

I don't think there is a "tried and true" solution yet.
[Sony Xperia T, TL, TX, V] charlatan01:
Your process is great, thanks for that. If you want an alternative to the root method above, I used this one and it works great as well.

Here
[Sony Xperia T, TL, TX, V] AvRS:
Moved. Question threads do not belong in the Development section, that's why we have a Q&A section.

Thanks

AvRS
[Sony Xperia T, TL, TX, V] xda-nat:
I am not having any luck unlocking the bootloader with the steps on the sony site.

not sure which is the 'unlock button' but have tried holding both up and down volume but neither prompts for drivers.

first time I plugged in it tried to install the drivers itself but just popped up the little window with various x's in it, but no chance to actually install one by hand at that point.

I do get the clunky windows sound, as I plug in.

If I look in device manager whilst doing this - holding vol up - I see an exclamation node called 'S1Boot Fastboot' but 5 seconds later it disappears before I can install any driver for it.

if I hold vol down the same thing happens but instead the node in device manager says 'S1Boot Download'

cant seem to install the driver as per the steps at all :(

can anyone offer some assistance?

thanks
[Sony Xperia T, TL, TX, V] papped:
Follow this, you need to download Flashtool first

http://xdaforums.com/showpost.php?p=32344530&postcount=35

blue led = fastboot mode
[Sony Xperia T, TL, TX, V] yesyesimanoob:
A good indicator of whether or not you're in the right mode is the notification light should turn blue and the screen should stay black. Hold the volume up while you plug it into USB, then hold it down for another 0.5-1 second until you see the blue light. That should be the right mode. But you have to plug it in right away, if the splash/boot screen comes up, you were too slow.