yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] corkie1:
But why would it have stayed official for a few days and then suddenly have changed to modified etc. CF root was run straight after the ota update so it was like fine for 4/5 days.
[Galaxy S II Original Android Development] Presjar:
I get this also. I have a N7105T

Anyone have ideas?
[Galaxy S II Original Android Development] juming:
Use titanium backup, look for sysscope, if it's frozen, defrost it and then reboot once or twice, then recheck your status.
[Galaxy S II Original Android Development] popimp315:
Supported the dev by buying it on the store. I'll get my confirmation stuff on here tomorrow. Its new years and I have a lovely girlfriend I haven't seen because of the army.
[Galaxy S II Original Android Development] Chainfire:
Released v2.40 - with Verizon Note 2 support :) (needs unlocked bootloaders)
[Galaxy S II Original Android Development] THE RED BLUR:
Happy New year Mr Chainfire. And thanks for your great work and great tools that has helped me and a lot of people on xda. :);):beer::thumbup:

Have a fantastic 2013.

SIGNATURE

PHONE : SGSII

Sent via: Tapatalk 2

Main ROM: NeatRom Lite 4.0

KERNEL : Siyah v6.0b4 tar test version

(DEFAULT PROFILE AND SETTINGS but pegasusq And sio applied via SetCPU)

MODEM : BVLP7

BATTERY : Stock 1650mAh

EXTERNAL Sdcard : Samsung Class 10 32gb

LAUNCHER : Apex

Guide to install Siyah on Ljs and tools to have a bug free rom = http://xdaforums.com/showthread.php?p=35923600
[Galaxy S II Original Android Development] Tindo1:
It works on S3 with CM Nightly 27. Does Chainfire have one brain like me? If so how the f### does he get go be so brilliant?! Are there any brain training exercises I can do to match up???
[Galaxy S II Original Android Development] NB2A:
Just downloaded from the market for I605 Note 2. I did not try it yet though. Thanks for your work and happy new year!:good:
[Galaxy S II Original Android Development] mrdreamers:
PLZ HELP!

is there another way to get rid of the yellow triangle?

because my Straight Talk SGS2- SGH-S959G is not compatible with Triangle Away :(

will this work? https://www.youtube.com/watch?v=-Cckjb0tx2U
[Galaxy S II Original Android Development] joshpdavis80:
I just tried this on my verizon note 2. I cannot boot my phone. It shows the yellow triangle and, " system software not authorized by verizon wireless has been found on your phone," message. Please help. I am locked rooted with stock rom. Thanks.
[Galaxy S II Original Android Development] Chainfire:
Err yes, you need an unlocked bootloader for this. Else there wouldn't be a reason for your flash counter to be non-0 in the first place. I'm amazed somebody would actually try this on a locked bootloader. Reflash stock recovery to fix (I think ?)
[Galaxy S II Original Android Development] DroidXcon:
Awesome thanks for the work.

I apologize if this is obvious or covered. So in order to use this we need to flash a stock rooted image. Then use triangle away and unroot. Leaving bootloader unlocked correct. Because flashing the locked bootloader would trip the counter again correct?

From my Galaxy Note 2 via Tapatalk
[Galaxy S II Original Android Development] coxlufc:
Thanks Chainfire worked flawlessly on mine :)
[Galaxy S II Original Android Development] ihvarrived:
Awesome.. worked flawlessly :-)
[Galaxy S II Original Android Development] naveediftikhar:
hahah

found something strange...i used this app to get rid of my triangle when i was on some ics rom...but now that ive returned to gb rom (checkrom 6) to be exact i just cant reproduce that triangle...haha no matter what custom kernel i flash that triangle doesnt appear back...so i guess this app does work for ppl on gb aswell:P...:D...in a way!:p
[Galaxy S II Original Android Development] chrisvr4:
Worked a charm for me :D super dUpEr work!

Just one thing though how many times can we use this app ? anyone know :)
[Galaxy S II Original Android Development] RotesMeerJogger:
why is it necessary to set counter to 0? i don't have yellow triangle because found a tutorial here on xda how remove it. so i not really need this app right? :-)
[Galaxy S II Original Android Development] claire85gr:
What tutorial? Can you link it, please?
[Galaxy S II Original Android Development] twigster:
Assuming we are thinking about the same tutorial.

That tutorial just removes the triangle but doesn't return your flash counter to zero. This app brings back the valuable zero required in the event of needing to take your phone back to Samsung for warranty reasons. Other than that, no its not needed and running this should be done cautiously and only when absolutely necessary due to how it can brick your phone.

That said I've been following this thread waiting for just such a post from someone, and nothing yet, even from people who don't read first that this only works on ics roms.

Big thanks to chainfire for all your work.
[Galaxy S II Original Android Development] ephraim:
It resets the counter to zero and as long as you don't flash a custom kernel through odin, then it won't increase the counter and the triangle won't appear. Flashing through CWM won't increase the counter.
[Galaxy S II Original Android Development] raqball:
This is pure awesome'ness.. I went from 47 to 0 in the push of a button..

Thank you Sir!!! :-)
[Galaxy S II Original Android Development] drdrewdown:
this worked like a champ on my Epic 4G Touch (Sprint SGSII), as well as my girls. (same phone)

thanks a bunch!
[Galaxy S II Original Android Development] nrnbow:
Simply works (stock CM9 build 02202012)! Thanks! Now I don't have to buy a jig :p
[Galaxy S II Original Android Development] Visentinel:
Worked great on wanamlite xxlph rom. The current status was correct also, I did confirm it before resetting. Well done!.
[Galaxy S II Original Android Development] nickmax1:
works perfectly on Omega 3.0 ICS !

thanks!
[Galaxy S II Original Android Development] RotesMeerJogger:
of course. i had removed the yellow triangle with this tutorial.
[Galaxy S II Original Android Development] claire85gr:
Ok thanks RotesMeerJogger, it worked but didnt reset counter

Actually i'm with Checkrom RevoHD v6 + Siyah 2.6.12 with the new bootloader from xila2 (the one that won't let jig usb work)

Will this apk work if I flash an ics rom (for example the "Resurrection Remix ics v9.3 black edition XXLPH 4.0.3 FULL-Wipe")

in CWM

(not Odin) ?

Or maybe i'll need to flash official ics leak from odin before
[Galaxy S II Original Android Development] betoNL:
I confess, I didn't read all the pages of this thread, but I am curious:

Anyone bricked his phone with this tool yet? (as warned as potential risk on first post)

Or only smooth flash count resets happening so far ?

.
[Galaxy S II Original Android Development] Bologna:
Yes...that's the right way to reset counter...

I was with Hyperdroid rom...and today I've flashed this one http://xdaforums.com/showthread.php?t=1482574 (XXLPH)...and...

worked perfectly!
[Galaxy S II Original Android Development] RotesMeerJogger:
i know but i don't know why people reset counter? what is my handicap if i have a counter of 30 (as example) to a counter of 0? :)
[Galaxy S II Original Android Development] stealthj:
I9100 cm9 perfect!!!
[Galaxy S II Original Android Development] Bologna:
Phone warranty and triangle away
[Galaxy S II Original Android Development] NB2A:
Count at 1

I am using a Verizon Note rooted and unlocked using beans build 4 with a count at 1.Is it even possible to set it back to 0 since it says in many cases it stays at 1 anyway?

Thanks again Chainfire and happy new year
[Galaxy S II Original Android Development] gpvecchi:
I think that XXELLA release of 4.1.2 for S3 has a new bootloader...

Working with it?
[Galaxy S II Original Android Development] deepgrass:
Tested and worked with S3 on XXELLA 4.1.2 release. The "!" at boot is also removed. :good:
[Galaxy S II Original Android Development] Ezekiel62:
Thanks for this :)

Work on the note 2 with omega rom 9.1, but counter reset to 1 at every boot :/
[Galaxy S II Original Android Development] joshpdavis80:
I had to odin back to the factory rom. I unlocked and rerooted. Now everything is good. I originally tried this because my device status showed "modified" and I was trying to change that.

Thanks for developing this.
[Galaxy S II Original Android Development] robogo1982:
Weird. Doesn't really work for me. The app says it's reset, but I still have the red exclamation mark at boot.

XXELLA (WanamLite 5.3), Galaxsih 2.0 beta 7.
[Galaxy S II Original Android Development] briteway:
Can someone please help with a step-by-step procedure?

I have an S3 I9300T which was rooted and the flash counter reads 1, in the settings>about phone I could see "modified." I only rooted it but stayed with the stock rom. Some time after that, there was a firmware update on ICS which I updated and afterwards realised that I lost root. None of my apps that require root could work thereafter. When checked settings>about phone, there was no "modified" anymore. When tried to get back into bootloader, there was no CWM either, it's back to stock bootloader, but when I checked the flash counter it says 1.

Now I have a warranty issue (crackling during a call only to other Samsung devices) and wanted to return it to stock. Also the new JB firmware update keeps popping up. I thought I'll reset the flash counter to 0 before I do that and then take it in for warranty but I'm not sure of the procedure from here on. Do I need to root it again before reset? Can someone please post the steps I need to take, I'll appreciate it so much. Thank you.
[Galaxy S II Original Android Development] gpvecchi:
:confused:
[Galaxy S II Original Android Development] robogo1982:
What's so confusing? I'll spell it out again.

I flashed the new bootloader from the XXELLA ROM and now Triangle Away doesn't really work anymore. It says the binary counter is reset to 0, but when I reboot my phone, I still see the red exclamation. When I boot into download mode, it says the flash counter is 1 and that the device status is modified (but I am aware Triangle Away doesn't even fix that, so it's all good).

I'll try some shenanigans with Odin and older ROMs and see what I can do.
[Galaxy S II Original Android Development] Ezekiel62:
Any clue for the count = 1 when rebooting a note 2 ? (latest cwmr with root, rom omega 9.1) ?
[Galaxy S II Original Android Development] corkie1:
Hi all 2 questions:

I am running stock 4.1.2 rooted. I have a small issue whereby the status is changing from official to custom in download mode. Why would it be randomly changing - you would think it would either stay at one or the other. When it does change randomly this is what i get in download mode

odin mode

product name: gt-i300

custom binary download: no

current binary: samsung official

system status: custom

Second question the LLA OTA download is available for my phone now - does anyone know if Triangle away would work with CF root 6.4 on LLA?
[Galaxy S II Original Android Development] stanley08:
Flash old bootloader, reset flash counter then flash new bootloader. I guess it should be fine. Or just wait for chainfire to update the App. We all know he is working hard on this now. He always is.

Please hit thanks if I helped you.
[Galaxy S II Original Android Development] vadonka:
i have the same problem

when i was updated to the new bootloader my flash counter was zero and my system status is official with stock rom, but after flash the new bootloader with the odin the flash counter incremented again!

the triangle away app not working with this new bootloader XXELLA

anybody have a location of the old bootloader odin file?
[Galaxy S II Original Android Development] Chainfire:
I know trying to explain this is futile, so this will be the last time I bother trying. It's not like this hasn't been stated in this thread a couple of hundred times already.

If you want the counter to stay 0 on various supported devices (including the S3 with the new bootloaders), you need to be running STOCK kernel and STOCK recovery, or the counter will reset to 1 automatically at each boot.

This is because these bootloaders check the kernel and recovery signature at each boot. So if you using T/A with CUSTOM kernel or CUSTOM recovery, T/A will reset the counter to 0, but then the next boot the bootloader will detect the CUSTOM kernel/recovery and reset the counter to 1.

If you're running a custom ROM, a custom kernel, a custom recovery, CWM, TWRP, etc, this will cause the counter to auto-reset to 1.
[Galaxy S II Original Android Development] Ezekiel62:
Agree with you, but i have a friend, using the same rom (omega 9.1), but stock kernel, and counter stay at 0 and status at official.

I think i will try to set back the stock kernel and give it a try :)

and thx for the information :)

another question :

in the first post, there a link to TA and a link to a .tar file, what is the tar file for ?
[Galaxy S II Original Android Development] vadonka:
this will be a problem. so if i installed the new bootloader the flash counter always incremented when i have only the root access.

but the TA app need root access so i cant use it without root, so if i have new bootloader i cant reset the counter to zero unless if i flash the old bootloader back. the problem is i cant find anywhere an old bootloader odin file :(

damn i should wait before i install the new bootloader, but im afraid from the sudden death because my phone is the 16gb model too. this is bloody horrible, this is a huge shame for the samsung made this mistake. im sit and wait for my phone will die, i always have a backup phone in my pocket because my phone can die in any moment.
[Galaxy S II Original Android Development] dcharleyultra:
Read the 2nd bullet in the FAQ in the first post.

Swyped from my SPH-L710
[Galaxy S II Original Android Development] Ezekiel62:
Ok, this tar is for Samsung Galaxy S II GT-I9100 ONLY, so it's not my case :) i understand things a little more :)

so, i will try with stock recovery+kernel and see if counter go to 0 after reboot :)
[Galaxy S II Original Android Development] siavash_Skh:
Thanks alot for your explain

So if my flash counter is 10 for example and then upgrade to lasted official firmware (ELLA), then i can install the trangle away on it and reset my counter ? ( after rooting it )

so you say we should reset the counter and then without any boot should go to an official one ?
[Galaxy S II Original Android Development] fitipardi:
Thanks, now i understand it better

Enviado desde el bar con una birra en la otra mano
[Galaxy S II Original Android Development] ZaKaTRoN:
Hello!

I have a SGS3, so, which firmware should I use to get status "System Normal"?

Thanks!!
[Galaxy S II Original Android Development] ajayverma99:
Not working

Not working.. On New bootloader... XXELLA....
[Galaxy S II Original Android Development] sarbe:
Stock firmware, everything stock and unrooted will set status normal.

---------- Post added at 03:14 PM ---------- Previous post was at 03:14 PM ----------

Works for me on LLA.
[Galaxy S II Original Android Development] siavash_Skh:
You flash the official LLA then root it then use triangle away ? It works for u? The counter set to 0 ? It is 0 still ? Or after boot set to 1?

How can we avoid setting couner to 1? By flashing the official LLA again after using triangle away?
[Galaxy S II Original Android Development] ajayverma99:
Today updated with new bootloader XXELLA.

and now triangle aap not reset my Binary count.

When I clicked reset option its show successful and binary count is 0 but after restart the phone again it's show Binary count 1.

ROM : crDroid v10

Bootloader : I9300XXELLA

Kernal : Siyah 1.8.6
[Galaxy S II Original Android Development] radekg7:
I have the same on my galaxy 3 XXELLA.
[Galaxy S II Original Android Development] beardymarrow:
This is what I did

Install Stock ROM

Flash CF Auto-root from Odin to get Stock Recovery and gain root

Install SuperSU and Triangle Away from Play

Reset Counter using Triangle Away

Unroot (from SuperSU)

Wipe Cache and Wipe Data/Factory Reset (from Stock Recovery)

Admittedly this wasn't on ELLA, but it should work exactly the same and give you back the status you need.

---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------

You have a Custom ROM and a Custom kernel, so will not get 0. As CF says
[Galaxy S II Original Android Development] MattBooth:
Not trying to be a PITA here, but...

I'm running my own ROM, running XXELLA WITHOUT the latest bootloader that's going around.

Using Triangle Away I'm able to reset the flash counter to 0, which shows both in the app and Download Mode as official and 0. I use CWM as my recovery...

I understand this may be the case for the new bootloader, but for the un-upgraded, triangle away still works.
[Galaxy S II Original Android Development] sarbe:
I have custom kernel and I have 0. CF says sometimes it will not stay at 0 not always.
[Galaxy S II Original Android Development] siavash_Skh:
Did you reboot after set the flash counter to 0 ?

Chainfire told that if you are on custom rom or kernel after a reboot the bootloader detect and set the counter to 1

Plz reboot your phone and tell us what happened ?
[Galaxy S II Original Android Development] thekoRngear:
I am on custom stuffs. Set v2.40 to auto-reset and after each boot I see the binary is zero/status official BUT that red exclamatory sign is still there which used to not happen until I flashed the new bootloader.
[Galaxy S II Original Android Development] Xardas:
Hi all...Same issue here..

Wanamlite 5.3 flashed through CWM + ELLA bootloader flashed with Odin pc..

Triangle away doesn't reset my counter at all (maybe cause it was set on 1 anyway) .

And plus that F***ING exclamation mark appears at every boot which makes me just a little ***damn nervous...

Chainfire we'd like to ear your voice here please :good:
[Galaxy S II Original Android Development] thekoRngear:
If I set it to auto reset it just is fine with download/recovery/ ta status. But the red mark is always there. Until that new bootloader came it just was fine.
[Galaxy S II Original Android Development] sarbe:
I have rebooted and get the same as the pics I posted, the only thing I have is the red exclamation mark.
[Galaxy S II Original Android Development] Chainfire:
Nothing but the same questions and statements. Nobody bothers to read the first post, nobody bothers to read the last few pages and find your answer. Nobody is asking a new question, it's just the same question on repeat. For most questions asked the past few pages, the answer is 23 posts before this one, if not, then the answer is in the first post.

I'm closing this thread for the time being. Maybe I'll open it again next week when people have gotten used to the new S3 bootloader and perhaps learn to read. Then again, maybe not. This is the first time that I've had to resort to this, let us hope it is also the last.
[Galaxy S II Original Android Development] Chainfire:
Triangle Away v2.45 has been released !

I've just released v2.45, with support for some more device models, and an option to workaround the system modified status. You should all re-read the first two posts to become informed about how and when it works. It works for me on my S3 and Note2, but this solution will be bootloader, firmware, and device dependent. Hopefully it will work for you, and Samsung will not patch against it too quickly.

I'm reopening the thread for now - hopefully we'll see some decent feedback - but if I see too many of the same questions that are answered once every page and/or by the first few posts of the thread, I will simply close it again.
[Galaxy S II Original Android Development] Conan179:
hmmm the new funktion is only working with supersu, becouse i have superuser and can use it.:(
[Galaxy S II Original Android Development] Chainfire:
I have no control over Superuser and thus cannot get the information I need out of it.
[Galaxy S II Original Android Development] bdastoor:
Chainfire, just defrosting the sysscope.apk using Titanium Backup and rebooting takes my S3 and Note 10.1 system status back to official after I run TriangleAway when I need to and stays that way.

So are others missing this easy workaround?
[Galaxy S II Original Android Development] briteway:
Ok, I did it. This is how:

- I was already on the stock ROM but lost root after an upgrade to ICS a few months ago (flash counter = 1)

- Install SuperSU > full unroot

- Flash CF Auto-root via Odin (flash counter = 2)

- Install Triangle Away

- Reset counter with Triangle Away (flash counter = 0)

- Update firmware to JB (or full unroot with SuperSU) - all back to stock

- Back up everything with My Backup then Factory Reset

Now to take it back for warranty and hopefully the in-call crackling issue is fixed.
[Galaxy S II Original Android Development] DeHAWK:
Chainfire, great job as usual. I've been using your apps for a long time, first on my SGS2. I've never ever had any problems what so ever. Now on my GT-I9305, running stock 4.1.2, stock kernel and rooted with EverRoot then TA. Everything is just great, no traces of root!

To all others; take the time to read Chainfires first post once in a while. He make changes to the posts about the applikation.

Once again Chainfire, THANKS for the job you do. The Galaxy phones would never had been the same without you.:)
[Galaxy S II Original Android Development] Chainfire:
Which status are you talking about, the bootloader status or the Settings status ?

Many methods have been suggested by many people, and I have taken an effort to try every single one of them, and at least for me - none of them work reliably whilst also remaining rooted. Most of them are ridiculous if you even think about the process. BUT, and that is a big but, these things are firmware specific and may even be influenced by which programs you have installed. I've seen defrosting SysScope trigger the status going back to normal a few times, only to jump to modified a few boots later. Other times, it didn't work at all, and reset the bootloader value to modified as well.

The method I have implemented in this case works perfectly on my own devices for the time being. I can't speak for anyone else's experience.

EDIT: Nevertheless, I will also implement your suggestion, if it works in your case, maybe it works well enough for other cases.
[Galaxy S II Original Android Development] dingolino:
Dear Chainfire,

do you see any benefit from having the new DLL7-France bootloader for the Note2?

Stability?

Beside booting the phone are there any other firmware patches, corrections etc included in the "typical" bootloader?

sorry for this more general question, but I am trying to figure out whether it would make sense for me to flash also the new bootloader to my Note 2 (so far I have used the omega custom rom).

Best regards,

dingolino
[Galaxy S II Original Android Development] siavash_Skh:
Hi

Device: Galacy S III

Rom: official LLA (ROOTED)

Kernel: Stock

Recovery: Touch 6.0.2.7

I used triangle away 2.45

At the first boot :

Setting:

Device status: normal

Download mod:

Counter:0

Official

Custom

Red exclamation just appears when I want to go recovery (holding up ....)

After reboot :

Setting:

Device status: normal

Download mod:

Counter:1

Custom

Custom

Red exclamation just appears when I want to go recovery (holding up ....)

---------- Post added at 11:36 PM ---------- Previous post was at 10:59 PM ----------

I back to stock recovery and try again with ver 2.45

Device: Galacy S III

Rom: official LLA (ROOTED)

Kernel: Stock

Recovery: Stock

After reseting using trangle away :

Setting:

Device status: normal

Download mod:

Counter:0

Current Binary : samsung Official

System Status : Custom

Red exclamation gone (even when I am going to recovery there is no Red exclamation point)

After some reboot the above conditions didnt change.

The problem is just system Status in Download Mod, if I unroot does it become official ?