Develop Bugs

ROOT de la Vega now available for T-Mobile Note3 :)

So... after first being impatient and buying a T-Mobile Note3 on Craigslist to use on AT&T and then later seeing how the bootloader locked AT&T Note3 was rooted by DG and Chainfire I ended up getting a contract renewal with AT&T after all and went with the AT&T Note3.
Now I thought I might try to experiment a little and see if I can replicate that root method on the T-Mobile Note3 because it's so brilliant and doesn't trigger the Know warranty void flag.
I can confirm it works just as well on the T-Mobile Note3 !!
ALL CREDIT for the method goes to DesignGears and Chainfire! The Original Thread is HERE: http://forum.xda-developers.com/showthread.php?t=2474422
All steps are exactly the same. THIS IS ONLY FOR N900TUVUBMI7 firmware, so that must be the current one installed on your phone.
Please follow all steps in the original AT&T thread, just skip the oneclick.exe and start with flashing the root_de_la_vega.tar using ODIN.
There is not really a need to so this if you already rooted with the AutoRoot method and triggered the Knox flag. This is for the careful guys who have NOT rooted yet, only want root (no custom ROM or recovery) and would rather like to preserve that Know Warranty 0x0 Flag
Link to the needed file for T-Mobile Note3 is HERE:
http://www.electron73.org/XDA/N900T/ROOT_DE_LA_VEGA-TMO.ZIP
Enjoy

Nice! If I wanted to go stock again, can I just flash the stock firmware in odin and it wont trip the knox flag?

lm that guy said:
Nice! If I wanted to go stock again, can I just flash the stock firmware in odin and it wont trip the knox flag?
Click to expand...
Click to collapse
Unfortunatley, once you trip the Knox Flag you can't untrip it - doing Odin to Stock will return you to stock but it does not remove the Knox flag...once it's tripped - it's tripped.

mocsab said:
Unfortunatley, once you trip the Knox Flag you can't untrip it - doing Odin to Stock will return you to stock but it does not remove the Knox flag...once it's tripped - it's tripped.
Click to expand...
Click to collapse
Oh no I haven't tripped my Knox flag yet I was asking if I use this method to root and I wanted to go back to stock later down the road, Will I trip the Knox flag if i odin the official stock firmware?

Its good to have this method available for those who are very conscious of Knox falg/warranty. Personally:
I will be doing a full root on my second N3. I have to; in the memory of my first N3... RIP where ever you are now.

lm that guy said:
Oh no I haven't tripped my Knox flag yet I was asking if I use this method to root and I wanted to go back to stock later down the road, Will I trip the Knox flag if i odin the official stock firmware?
Click to expand...
Click to collapse
I am not positive - but I think if you flash anything - it will trip it - if you odin back to stock - it would include a new kernel and that would tirp the flag - I may be wrong - but I believe I read this the other day.
WHy would you want to return to stock? To return the phone or something if something went wrong? Maybe there is another way to remove root.?

I dont think you even have to remove root. There will be now ay to tell if you are rooted using that method. Unless you use app that ask you SU permission. So before return just do Factory Reset. That i think should take care of things. IMHO.

lm that guy said:
Oh no I haven't tripped my Knox flag yet I was asking if I use this method to root and I wanted to go back to stock later down the road, Will I trip the Knox flag if i odin the official stock firmware?
Click to expand...
Click to collapse
No, if you ODIN back to full stock or do a factory reset/wipe the Knox flag will NOT be triggered. That flag only triggers if you install a CUSTOM recovery or kernel (custom rom).

For the Galaxy S3, there's also a "no trip root" thread where you simply flash a root-injected TouchWhiz, which I used, and as long as you never flash anything non-Samsung in ODIN, you'll never trip the flash counter flag (which can be reset with TriangleAway anyway, unlike the KNOX flag afaik). But, once rooted, you don't need ODIN, and flashing TWRP recovery via the GooManager app (or dd'ing the img over the recovery partition) doesn't trip the flag, nor does subsequent ROM flashes from recovery over the system partition.
Is it the same situation here, or is the KNOX flag different, in that it will always get tripped as soon as it sees an unsigned partition on bootup?

Darn.. Wish I came upon this like 2 days after I had my TMO note 3. Ive already tripped my Knox. Oh well.

Has anybody tested this method. Does it work
Sent from my SM-N900T using xda app-developers app

DriftorX said:
Darn.. Wish I came upon this like 2 days after I had my TMO note 3. Ive already tripped my Knox. Oh well.
Click to expand...
Click to collapse
The one thing that will eventually have me tripping my Knox flag is if a nice custom kernel comes along. But until then, a simple way to root without tripping the flag will hold me over :fingers-crossed:. Also I'm returning my phone in a week so it's important I don't trip it right now. I want to root and play around with my phone until then.
bbh4r4l said:
Has anybody tested this method. Does it work
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I will test in about 10 minutes when my phone gets finished charging to 100% and will report back. :laugh:
Edit: everything works Thanks OP for posting this!!

Just rooted via this method. It worked fine and knox is stil 0x0. It also didn't factory reset my phone like I thought it would, I'm going to do it anyway, but I wasn't getting any FCs or anything either. Thank you for getting this out to us TMO users!

I don't get it. Rooting doesn't trip knox regardless. But flashing a custom kernel or rom does. So what is the point of this method if it will trip knox as soon as you flash a kernel or rom anyway.

HughesNet said:
I don't get it. Rooting doesn't trip knox regardless. But flashing a custom kernel or rom does. So what is the point of this method if it will trip knox as soon as you flash a kernel or rom anyway.
Click to expand...
Click to collapse
For one you can use apps that require root. Also, you can uninstall bloatware and push apks to your phone using adb etc. A little more work than flashing a prebuilt custom rom, but you can get many of the same results.
*You also said rooting doesn't trip knox regardless, but it actually does unless you do it via this method.

Just did this. Easy as cake. Now I just need to sim unlock my note to use my ATT sim and I will be good to go!!

effortless said:
For one you can use apps that require root. Also, you can uninstall bloatware and push apks to your phone using adb etc. A little more work than flashing a prebuilt custom rom, but you can get many of the same results.
*You also said rooting doesn't trip knox regardless, but it actually does unless you do it via this method.
Click to expand...
Click to collapse
I know you don't need a custom rom for some things. I run stock deodex myself. I flashed custom recovery immediately after root. I guess I thought that is what triggered knox. Either way matters little to me though. I know tmobile won't check knox counter if I use jump and even if they did I could sell on ebay and come out ahead. So I don't really understand why people worry about it. Insurance covers it if you damage it or need warranty service.

HughesNet said:
I know you don't need a custom rom for some things. I run stock deodex myself. I flashed custom recovery immediately after root. I guess I thought that is what triggered knox. Either way matters little to me though. I know tmobile won't check knox counter if I use jump and even if they did I could sell on ebay and come out ahead. So I don't really understand why people worry about it. Insurance covers it if you damage it or need warranty service.
Click to expand...
Click to collapse
Yeah... Seems to me like a kinda-sorta placebo effect or simply one of those things that people can use who *must* have everything completely untraceable to the "T." Like you said, there's virtually no "real" reason this is very necessary, far's I can tell... But, regardless, good work on this - without a doubt - and definitely always a big "plus" to have multiple working methods! :good:

HughesNet said:
I don't get it. Rooting doesn't trip knox regardless. But flashing a custom kernel or rom does. So what is the point of this method if it will trip knox as soon as you flash a kernel or rom anyway.
Click to expand...
Click to collapse
exactly. I think op might not know everything like he is implying. he just wants some attention
*****es be be like "nice phone"

mocsab said:
I am not positive - but I think if you flash anything - it will trip it - if you odin back to stock - it would include a new kernel and that would tirp the flag - I may be wrong - but I believe I read this the other day.
WHy would you want to return to stock? To return the phone or something if something went wrong? Maybe there is another way to remove root.?
Click to expand...
Click to collapse
If people read up on how KNOX actually works, there wouldn't be so much confusion.
The KNOX WARRANTY VOID flag is set to 0x1 when the bootloader detects (via Qualcomm SecureBoot) that you are booting either a kernel or a recovery that isn't SELinux enforcing (it displays a message such as RECOVERY IS NOT SEANDROID ENFORCING - Set Warranty Bit: recovery). It remembers that the partition you booted was insecure and flags it in its own little memory area. It sets individual warranty bits for each partition - boot (kernel), recovery, cache (if you happen to put something there that it doesn't approve of), system. If ANY of those partition warranty bits are set, the KNOX WARRANTY VOID flag is set to 0x1.
This is all explained in the KNOX white paper available on the Samsung web site.
Now, if someone figures out how to write-enable the protected flash area so the flag can be reset AND disable Qualcomm SecureBoot so that it doesn't set the flag over and over again, we'll be in business. For now, only Samsung knows how to do it.

The ultimate guide about Knox

Because it's not very clear even after reading many xda Thread, and users have many problems withknox I deciced to gather informations about Knox.
1 :What is Knox?: http://omegadroid.co/wanted-knox-void-warranty-0x1/
All you wanted to know about KNOX Void Warranty 0×1
By tamirda • October 9, 2013
Screenshot_2013-02-25_11_35_AM
Recently, Samsung announced that her all new devices will get an Android 4.3 update that includes KNOX Security system. According to Samsung, these devices will get the update:
Samsung Galaxy S3
Samsyng Galaxy Note II
Samsung Galaxy S4
Samsung Galaxy Note 3 (already has KNOX Security system)
Most of the users don’t root their devices and use it normally and for them KNOX Security system is a great option.
But what happanes if we want to root our device?
Now the problem begins.
Normal(unrooted and so..) devices are flaged as KNOX Void Warranty 0×0 right from the factory.
When we flash items which weren’t signed by Samsung, it flags your device as KNOX Void Warranty 0×1.
According to Chainfire, KNOX status is indeed an eFuse. This means that even JTAG can not reset the KNOX status back to 0×0.
Some facts about KNOX status:
It isn’t possible to downgrade to KNOX-disabled firmwares/bootloaders (An attempt sets 0×1) (even though some people state, downgrade is possible when omitting the bootloader file in a firmware package). By downgrading from KNOX-enabled to KNOX-disabled firmware, your devices will be locked to installation of newer firmwares.
Let’s focus on that fact. As we mentioned above, Devices like S4, S3 and Note II which came without KNOX will get the KNOX system.For example, S4 I9505 got about a month ago 4.2.2 update that includes KNOX-enabled system(MH1). If you try to downgrade to KNOX-disabled system(MGA for example) your device will be flaged as KNOX Void Warranty 0×1 and will get a special lock – you won’t be able to update to any KNOX-enabled firmware even by ODIN. Samsung’s 4.3 update is KNOX-enabled, so if you tried to downgrade to KNOX-disabled firmware(for example MH8->MGA), you won’t be able to install 4.3 update.
This problem is only for devices which didn’t come with KNOX-enabled system from the factory(S4, S3 and Note 2)
Jeffery Butler confirmed this information:
FYI…Samsung told me that Knox warranty becomes 0×1(void) when the device with secured bootloader attempts to have non-secured bootloader. MH1 is the very first binary with secured bootloader. If MH1 is attempted to be downgraded to lower version(i.e. MGD) which has non-secured bootloader, then Knox warranty becomes void forever, and this means that the device can be used only for non-Knox device(no container can be created).
If you try to downgrade to KNOX-disabled firmware, you can’t install any new firmaware(that includes KNOX-enabled system) and use your device only with the old firmwares.
Even if you flash a KNOX-enabled firmware via odin (e.g. the latest fw) knox will be set to 0×1.
Flashing unsigned or modified images via odin will set knox to 0×1.
According to these two, flashing root/kernel/recovery/latest firmware by samsung/etc. will set KNOX status to 0×1.
Samsung stated, resetting the flag is impossible.
Chainfire confirmed that it is impossible to reset the flag.
KNOX is mandatory and can not be completely removed.
In custom roms we can remove KNOX apps, but the status remains 0×1.
Warranty Void is not a counter, it is a flag (0,1). We have never seen 0×2 or so.
Mirroring all partitions from a clean 0×0-Device to a 0×1-Device via JTAG produces an unfunctional device (reversible by restoring the 0×1 partitions on the phone).
Using JTAG or other repair tools to reset the flag is impossible.
KNOX bootloader verifies signatures of kernels and recoveries. No custom ones possible without voiding the knox warranty.
Again, if we flash kernel/recovery/etc. we will void the warranty.
This si how 0×1 looks like:
2rn7beq.jpg
This is how 0×0 looks like:
attachment.php
I guess you are asking yourself now, what the hell 0×1 means?
If your device is flageed as 0×1. you should forget about your warranty.
Chainfire and other people confirmed that your can’t use your warranty:
Worse than that, I’ve also been hearing that service center instructions are indeed that devices with this status tripped will not receive any warranty repairs. (Of course, the action they take may still depend on the service center). Their excuse is that the hardware is damaged by the owner. Seems Samsung is catching up in scumbaggery to HTC, who years ago attributed my HTC Diamond’s screen damage (digitizer detached) to the installation of HSPL
To anyone in the know it is obvious that this doesn’t really fly, and the eFuse blowing (is this the hardware damage?) is intentionally done by the bootloader when unsigned software is loaded.
If you want to read the whole Chainfire’s statement, click here.
What is eFUSE? it’s a technology that allows reprogramming a read-only memory chip in real-time, even though such chips come with hard-coded code that cannot be generally changed after manufacturing.
When flashing unofficial software on the device, the status of the system and KNOX is switched to CUSTOM while increasing a binary flash counter, which helps Samsung find out whether the device has been tampered with. However, while Chainfire’s TriangleAway app has let users switch the status back to official and reset the flash counter until now, the KNOX status is based on eFUSE – basically, once you flash custom kernels or root the Note 3, the KNOX code gets rewritten, and this constitutes hardware damage.
Well, all I can say is think twice before you play with your Samsung device. If you don’t care about warranty, and you like custom roms and cool stuff just be aware of this information and continue with what you are doing.
Rajaasim1980 said:
KNOX is a new security system in official update of Android 4.3
on Samsung devices which prevents access to multiple applications when rooting your device and prevents the flash counter being reset to 0
Click to expand...
Click to collapse
theq86 said:
As you may already know, the latest Samsung firmwares came with a new secured bootloader. You can recognize it in download mode easily. It states: Knox warranty void: 0x0 or 0x1.
As for now, there is no way to reset that flag from 0x1 to 0x0.
Then I read in a comment of Chainfires post concerning that flag, that as long as you do not try to downgrade to a non secured bootloader, this flag will not change. He claims to have that information directly from Samsung.
https://plus.google.com/u/0/+Chainfire/posts
Has anyone already experience with rooting an "untouched" S4 which has the secured bootloader and can confirm or decline that?
- - - - - - - - - -
Conclusions and Facts about KNOX-enabled firmwares (based on statements from chainfires post and it's comments above, ans based on this thread)
Not possible to downgrade to KNOX-disabled firmwares/bootloaders (An attempt sets 0x1) (even though some people state, downgrade is possible when omitting the bootloader file in a firmware package: see http://forum.xda-developers.com/showthread.php?t=2444671, not confirmed)
Even if you flash a KNOX-enabled firmware via odin (e.g. the latest fw) knox will be set to 0x1
Flashing unsigned or modified images via odin will set knox to 0x1
Samsung stated, resetting the flag is impossible
KNOX is mandatory and can not be completely removed
Warranty Void is no counter, it is a flag (0,1) it was never seen 0x2 or so
Mirroring all partitions from a clean 0x0-Device to a 0x1-Device via JTAG produces an unfunctional device (reversible by restoring the 0x1 partitions on the phone)
KNOX bootloader verifies signatures of kernels and recoveries. No custom ones possible without voiding the knox warranty
Assumptions on how KNOX flag in bootloader works:
Some experts think, an eFuse is involved. (http://en.wikipedia.org/wiki/EFUSE). An eFuse is mostly only incremential. Even unwriteable by low level tools or JTAG. But it is still not proven, that eFuse is used.
Knox technical information:
https://www.samsungknox.com/overview/technical-details
Click to expand...
Click to collapse
2: Can i downgrade the bootloader?
cosmyndemeter said:
from mj5 bootloader downgrade is possible, read this for newest than mj5 downgrade not possible!
do not try! you can brick your phone forever!!!
Click to expand...
Click to collapse
3:Can i install custom roms?
DeepankarS said:
You can do any customization on your phone like a normal phone, but customizing it means that you have triggered the KNOX counter to 1. Thus on a stock rom you can never use KNOX if KNOX reads 1.
FYI the MK4 (bootloader) or MJ9 (babseband version) has blocked installation of any custom roms on our n7100s via odin. You cannot even downgrade to 4.1.2 official via odin, So flashing via recoveries is the only way left.
And also it is recommended that you install custom roms via Philz/TWRP/CWM recoveries to flash custom roms and everything.
Hope the lil knowledge helped.
Click to expand...
Click to collapse
4 Can i root my note 2 with 4.3 knox?
Yes, but there are chances to trigger the KNOX counter to 1
yeminswe said:
4.3 root
http://forum.xda-developers.com/showthread.php?t=2540761
http://forum.xda-developers.com/showthread.php?t=2573576
>D
Click to expand...
Click to collapse
If you see any questions about knox, post here we will answer.

number 1 link is error,not found.
what about knox container ?

sora9009 said:
number 1 link is error,not found.
what about knox container ?
Click to expand...
Click to collapse
Link fixed.
Thanks

What about kernels?
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.

Irwenzhao said:
What about kernels?
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.
Click to expand...
Click to collapse
KNOX bootloader verifies signatures of kernels and recoveries. No custom ones possible without voiding the knox warranty

Is there any way to get the knox back to 0 from 0x1????
Sent from my GT-I9500 using Tapatalk 4 - Hassan K. Malik

HassanM said:
Is there any way to get the knox back to 0 from 0x1????
Sent from my GT-I9500 using Tapatalk 4 - Hassan K. Malik
Click to expand...
Click to collapse
Not yet,although note 3 has been reported to somehow reverse it but that's just wishing too much.

singhpratik87 said:
Not yet,although note 3 has been reported to somehow reverse it but that's just wishing too much.
Click to expand...
Click to collapse
On the note 3 it's done by special bootloader leaked by sammy. The only chance for the note 2 is if note 2 bootloader is leaked. No other way.
Sent from my GT-N7100

I dont care about warranty , all i care that , if i installed a custom rom and the Knox bit is set to 0X1 and i want to get back to the stock , can i install Knox again or not ? because i like the knox idea

hazemsalah said:
I dont care about warranty , all i care that , if i installed a custom rom and the Knox bit is set to 0X1 and i want to get back to the stock , can i install Knox again or not ? because i like the knox idea
Click to expand...
Click to collapse
Once your counter goes to 1 no more Knox app , it can't be used anymore.
Sent from my GT-N7100

gregsarg post :
We have a fix....just not on xda....yet
Mobiletechvideos.com now offers a bootloader downgrade service for our devices. ..
The Knox flags can be reset quite easily according to them....
So if you want the old Knox free phone back....see below and get your anti-knox groove on....
See the product description tab in the middle of the page. ..g
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-2-bootloader-sboot-downgrade-service/

Hmmm it's kinda fishy , but could be true. So you send them your phone ? I don't get it. And all around is jtag heh
Sent from my GT-N7100

note2nooby said:
Hmmm it's kinda fishy , but could be true. So you send them your phone ? I don't get it. And all around is jtag heh
Sent from my GT-N7100
Click to expand...
Click to collapse
Nope i can't risk to send my phone (400 euro), but it looks like they have the solution.I send them mail to ask if i can pay for the file and instruvtions but no answer till now.They want 75 for the reset and 45 for express shipping end delivery.I told them that i am
agree to pay all the ammount for the file.
And one more thing-if i send them phone i can't be sure that they will reset it instead of just replacing MB and write my old IMEI e.t.c

gencho81 said:
Nope i can't risk to send my phone (400 euro), but it looks like they have the solution.I send them mail to ask if i can pay for the file and instruvtions but no answer till now.They want 75 for the reset and 45 for express shipping end delivery.I told them that i am
agree to pay all the ammount for the file.
And one more thing-if i send them phone i can't be sure that they will reset it instead of just replacing MB and write my old IMEI e.t.c
Click to expand...
Click to collapse
I'm quite sure they are using jtag and service bootloader. That's why they need the phone. It's not the same way like the exynos fix for note 3.
Sent from my GT-N7100

I-9192 official status again
i have installed a few weeks later a rooted rom from another forum, and triggered the knox to 0x01 (so i cant receive official updates from samsung)
but, today i needed to reset my phone to factory default, than i was curious to check the phone status, and for my surprise was "Official" again...
i read in various sites that the knox flag cannot be reverted... is that true?
the files i was used to root:
Odin 3.09
Kernel_root_I9192.tar
SuperSU_1.41.zip
the only bad thing is that i lost my root
anyone have the same result just reseting the phone?
thx and sorry for bad english

Soooo. As far as i know the knox wont get updates from Samsung and Block using knox app? And what features are lost from a triggered knox? I flashed the original firmware again and all its ok so far. Theres any blocked feature that o didnt realize?

Need help
I've a s4mini 19192 and today I flashed samsungs official KitKat update to my phone... I tried to root it like I rooted the 4.2.2 update... But can't do.... Then I decided to downgrade to the old version 4.2.2 but odin says can't.... And fails... Someone can help me?

Is it possible to check when the flag was triggered?
I was sold a GN3, in witch the KNOX flag was already set* and I'm trying to avoid a situation in witch the seller will say that I've set the flag.
* not checked beforehand - my mistake - but still I can return it or get a discount under the law

hello..just got the s4 mini dual sim 9192... 2 days back..i was on 4.2.2 indian firmware....checked download mode and it said knox 0*0...now i flashed the 4.4.2 firmware downloaded from sammobile via odin and when i recheck knox is gone....!!!!
just said binary and system which changed from official to custom once i rooted it with CF-root method(nothing else was working...saferoot/towelroot etc)..and as i seem to have read that flashing stock rom reverts these back to official...is it true?
and does this mean that my knox firmware phone has been converted to a non-knox one after kit kat upgrade?
please anyone let me know..thanks

@Fataz bro i have a few questions
I'm currently on FNE2 stock deodexded custom rom with a FNE2 bootloader, when i go download mode it says "KNOX WARRANTY VOID:1"
1 - Does this means Knox is tripped as 0x1
2- Can i install a stock firmware higher than FNE2 from sammobile via odin
GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi

[Q] Will Triangle Away trip Knox itself?

I needed to bring my GT N7100 (intern. version) back to complete stock.
It was rooted, had a custom recovery and (deknoxed) custom rom and thus several binary counts.
For start i put back stock recovery and ran Triangle Away. After that my smarter part thought...well....why not upgrade to latest official firmware.
So i downloaded N7100XXUEMK9_N7100PHNEMK2_PHN form sammobile and flashed happily through Odin.....
Just after that i realised my binary count must have been stuck on 1 cuz of the custom rom i had.
Now i'm stuck with a rather weird set up in download mode:
Custom Binary Download: Yes (1 counts)
Current Binary: Samsung official
System Status: Official
KNOX Warranty void: 0
In order to reset my binary count back to 0 i have to reroot and rerun Triangle Away, but afaik most rooting ways will trip Knox, so in that case it has no use.
I wanna give this root method a try
http://forum.xda-developers.com/showthread.php?t=2565758
cuz in the thread i found 1 or 2 posts that confirmed root without tripping Knox on the international GT N7100 on MK9 bootloader
So my question is....will Triangle Away itself trip knox?
I've been searching the forums for a few days now, but just can't find the answer.
Any help would be much appreciated!

Triangle away won't but rooting definitely will.

Where you able to fix the issue? I have a similar problem.
Nirak said:
I needed to bring my GT N7100 (intern. version) back to complete stock.
It was rooted, had a custom recovery and (deknoxed) custom rom and thus several binary counts.
For start i put back stock recovery and ran Triangle Away. After that my smarter part thought...well....why not upgrade to latest official firmware.
So i downloaded N7100XXUEMK9_N7100PHNEMK2_PHN form sammobile and flashed happily through Odin.....
Just after that i realised my binary count must have been stuck on 1 cuz of the custom rom i had.
Now i'm stuck with a rather weird set up in download mode:
Custom Binary Download: Yes (1 counts)
Current Binary: Samsung official
System Status: Official
KNOX Warranty void: 0
In order to reset my binary count back to 0 i have to reroot and rerun Triangle Away, but afaik most rooting ways will trip Knox, so in that case it has no use.
I wanna give this root method a try
http://forum.xda-developers.com/showthread.php?t=2565758
cuz in the thread i found 1 or 2 posts that confirmed root without tripping Knox on the international GT N7100 on MK9 bootloader
So my question is....will Triangle Away itself trip knox?
I've been searching the forums for a few days now, but just can't find the answer.
Any help would be much appreciated!
Click to expand...
Click to collapse

dalanik said:
Triangle away won't but rooting definitely will.
Click to expand...
Click to collapse
Hi, thanks for replying! Are you sure about that? I am in the same situation as the OP, I did a search and I think it is possible to root without tripping KNOX by following this guide:
http://www.ibtimes.co.uk/root-galax...-4-3-bypassing-knox-warranty-void-bit-1432252
After reading the xda thread linked in that post it does seem like this may be a successful method on the N7100, however, I can't find any concrete evidence that Triangle Away will be successful on a KNOX enabled device and will not trip the KNOX counter.
UPDATE:
So I just rooted my note ii using the method outlined in the xda thread (which is linked in the link I posted above), and it did not trip the KNOX flag. I then downloaded Triangle Away and granted it root access, it failed to reboot. I am not sure why, it did not work though.
My current status is:
AP: N7100XXUEMK9
CP: N7100XXUEMJ9
CSC: N7100BTUEMK2
Custom Binary Download: Yes (2 counts)
Current Binary: Samsung Official
System Status: Custom
KNOX Warranty Void: 0
AP SWAEV: A2
Update
Used Triangle Away v3.01, it cleared my Custom Binary Download, but it DID trip the Knox Warranty Void to 1. So to confirm, root = no trip, Triangle Away current version will not reboot, Triangle Away older version = trip KNOX.

Rooting as i mentioned in OP worked like a charm, but when i installed Triangle Away 3.25 it didn't work, so i installed an older version of it, 3.10.
This one worked en fully resetted my binary counter, unfortunately this indeed tripped KNOX:crying:
Maybe i made the mistake of using an older version of TA, i didn't read enough before i decided to do that, or maybe it's just how TA works, regardless of which version.
Anyhow....i've now joined the official Knox 0x1 club, while everything else is flagged 'official'.
I can hook up the phone to Kies, no problem, OTA works, device gets registered and says the newest software is already installed.

Nirak said:
Rooting as i mentioned in OP worked like a charm, but when i installed Triangle Away 3.25 it didn't work, so i installed an older version of it, 3.10.
This one worked en fully resetted my binary counter, unfortunately this indeed tripped KNOX:crying:
Maybe i made the mistake of using an older version of TA, i didn't read enough before i decided to do that, or maybe it's just how TA works, regardless of which version.
Anyhow....i've now joined the official Knox 0x1 club, while everything else is flagged 'official'.
I can hook up the phone to Kies, no problem, OTA works, device gets registered and says the newest software is already installed.
Click to expand...
Click to collapse
Iam on the same situation guys, except i havent tripped knox yet.
My flash counter is custom while everything else is official and knox is 0x0, the only diference is that my device is a i9505 s4 but it works the same for this.
So there is no way for me to get my warranty back since my flash counter is custom even the knox is untripped?
Thanks

alundra212 said:
Iam on the same situation guys, except i havent tripped knox yet.
My flash counter is custom while everything else is official and knox is 0x0, the only diference is that my device is a i9505 s4 but it works the same for this.
So there is no way for me to get my warranty back since my flash counter is custom even the knox is untripped?
Thanks
Click to expand...
Click to collapse
Nope, no change as for now. TA (any version) will trip your KNOX for sure; You could try reading up on the 'reset KNOX counter' for your S4, i read somewhere that for Exynos chipset it can be done (not easy!), for Snapdragon there's no possibility and i really doubt it will come ever.

triangle away will trip knox flag because need a custom kernel to reset download binary.
flashing a custom kernel is what trigger knox!

If u wanna unroot u cant use an 4.1 rom to use triangle away to reset to 0 and upgrade after to 4.3 ?

[SOLVED] KNOX doubts before buying i747

Hello everybody,
My current device is a Captivate, and I'm thinking about upgrading to an i747. After doing some research in the forums I found out about knox, but find it a little bit confusing, let's see..
1) Has there been any known cases of devices that were shipped with a knox bootloader?
2) In a i747, what does a knox bootloader look like in Download Mode (as opposite to a non-knox one, does it say knox warranty void or something else?)
3) This is where I'm most confused. If you've got a knox bootloader, then you can't downgrade it, and can't flash anything except for new official otas? would anything except the ota void it? can you flash CM11 for example? and if it's void, that means that it's a hard brick? or does it still work? Can you go foward if it's void (again, like cm11)?
4) Let's say the one I get comes with 4.0, I can root and move freely between CM and stock as long as I don't flash 4.3?
I also have the option to go for a S4 Mini, but given it has the same issue and similar hw.. love the S3 screen
Thanks in advance!

Samsung s3, s4, Note 3, etc. that shipped with 4.3 will include Knox.
If the device shipped with Knox, you will see something like warranty bit in the text at the top of the download screen.
If you have a knox bootloader, you cannot downgrade to an earlier bootloader but you can still install a custom recovery and custom ROMs which voids the warranty but does not brick the phone.You can flash any ROM you want with a 4.3 Knox bootloader as long as the ROM does not try to flash a new bootloader.
If you have a stock 4.3 phone and try to load anything that is not official Samsung software, it will trigger the knox counter (change from 0 to 1 or 0x0 to 0x1) and void your warranty. At the moment, there is no way to reset the knox counter to 0.
Yes, if you get a 4.04 phone, you can install a custom recovery, custom ROM, and move freely among custom ROMs if these ROMs are support but the installed bootloader.
I have done all of this with an i747m (Bell version of the s3).

That's crystal clear, I was confused and thought that if you had knox and flashed anything else over it it would brick... but I see now, just avoid bootloaders.
Thanks!

Warranty Void Question

hello i have a question ive boughed a galaxy note 8 a last week and stuped me updated to 4.4.2 and im not new to samsung device i had one my self and rooted not even(for my friends) one but never had such situasion but i still got warranty and i dont want to lose it i know there is knox on my device now and if i root with vroot my system status will change to custom and will not touch knox so my question is when ill root and use triangle away and send my note to samsung after theyll format it will the system status stay official or go back to custom?

the_ziom said:
hello i have a question ive boughed a galaxy note 8 a last week and stuped me updated to 4.4.2 and im not new to samsung device i had one my self and rooted not even(for my friends) one but never had such situasion but i still got warranty and i dont want to lose it i know there is knox on my device now and if i root with vroot my system status will change to custom and will not touch knox so my question is when ill root and use triangle away and send my note to samsung after theyll format it will the system status stay official or go back to custom?
Click to expand...
Click to collapse
TriangleAway still works with the KitKat KNOX enabled bootloader but the counter it resets is not the KNOX warranty flag. If you've flashed any unsigned (by Samsung) image to your tablet, including custom recoveries, kernels and/or ROM's, or rooted with CF Auto Root (which flashes a custom recovery) since upgrading to KitKat 4.4.2, your KNOX flag has been triggered and your warranty is already voided.
ramjet73

ramjet73 said:
TriangleAway still works with the KitKat KNOX enabled bootloader but the counter it resets is not the KNOX warranty flag. If you've flashed any unsigned (by Samsung) image to your tablet, including custom recoveries, kernels and/or ROM's, or rooted with CF Auto Root (which flashes a custom recovery) since upgrading to KitKat 4.4.2, your KNOX flag has been triggered and your warranty is already voided.
ramjet73
Click to expand...
Click to collapse
No you dont get my question im aware of knox and I dont want to touch it but I head that rooting changes the system status to custom in download modeand in system it changes to modified and if samsung see tht than the warranty if void so once again my question is when I root with vroot or with kingo root they both dont touch knox and than use triangle away and SET system status back to official or normal and after formating will the official or normal status stay of will it be turned back to custom/modified

the_ziom said:
No you dont get my question im aware of knox and I dont want to touch it but I head that rooting changes the system status to custom in download modeand in system it changes to modified and if samsung see tht than the warranty if void so once again my question is when I root with vroot or with kingo root they both dont touch knox and than use triangle away and SET system status back to official or normal and after formating will the official or normal status stay of will it be turned back to custom/modified
Click to expand...
Click to collapse
I haven't used either of those rooting methods so I can't answer that. According to the Kingo website the chances of tripping the KNOX flag are 1 in 1000, but they don't mention the flash counter. OTOH, Samsung claims that KNOX can be tripped with as little as a custom kernel initialization script:
For example, some KNOX security mechanisms, such as SE for Android, will trigger an e-fuse if the system is booted with an arbitrary kernel, kernel initialization script or data, and therefore be disabled and no longer function correctly.
Click to expand...
Click to collapse
I know you said that you're not asking about the KNOX implications but maybe you should. Regarding resetting the flash counter and custom configuration with TriangleAway, I suggest posting your scenario in that thread and hope for a response from Chainfire, the developer of that app. If you can root with one of those methods without tripping Knox, my experience is that after using Odin to flash the stock ROM and running TriangleAway when I was using the 4.2 ROM and bootloader there was no indication on the bootloader screen or using the stock ROM that "tampering" was detected, but things might have changed with the 4.4 bootloader.
Good luck, and please let us know how it turns out.
ramjet73

ramjet73 said:
I haven't used either of those rooting methods so I can't answer that. According to the Kingo website the chances of tripping the KNOX flag are 1 in 1000, but they don't mention the flash counter. OTOH, Samsung claims that KNOX can be tripped with as little as a custom kernel initialization script:
I know you said that you're not asking about the KNOX implications but maybe you should. Regarding resetting the flash counter and custom configuration with TriangleAway, I suggest posting your scenario in that thread and hope for a response from Chainfire, the developer of that app. If you can root with one of those methods without tripping Knox, my experience is that after using Odin to flash the stock ROM and running TriangleAway when I was using the 4.2 ROM and bootloader there was no indication on the bootloader screen or using the stock ROM that "tampering" was detected, but things might have changed with the 4.4 bootloader.
Good luck, and please let us know how it turns out.
ramjet73
Click to expand...
Click to collapse
Well non of those methods worked I had to root via odin so bye bye warranty