Develop Bugs

[Q] GT-N7100 rooted on Android 4.3 Knox 0x1 can't update OTA

Hi
I am using Samsung Galaxy Note II GT-N7100
I did a mistake by not doing more research before rooting my phone and now my Knox flag is 0x1.
I upgraded my phone to Android 4.3 then rooted it with Chainfire autoroot using Odin.
Now I am not able to remove KNOX bootloader also if I try to flash a KNOX free bootloader Odin show unsupported device error and device gets soft brick then I have to flash Chainfire autoroot again to start the device again.
Is there any way to get KNOX free bootloader? or to be with Knox bootloader but everything fine like it was before.
Disadvantages are
I can't use Knox feature now.
Cannot update my device OTA or through Samsung Kies so downloading form Sammobile and flashing takes a lot of time.
I don't have any other problem I am running on stock rom 4.3 but I want that I should able to update my mobile OTA and if possible able to use KNOX feature again.
Thank you
Have a nice day

XenonTNT said:
Hi
I am using Samsung Galaxy Note II GT-N7100
I did a mistake by not doing more research before rooting my phone and now my Knox flag is 0x1.
I upgraded my phone to Android 4.3 then rooted it with Chainfire autoroot using Odin.
Now I am not able to remove KNOX bootloader also if I try to flash a KNOX free bootloader Odin show unsupported device error and device gets soft brick then I have to flash Chainfire autoroot again to start the device again.
Is there any way to get KNOX free bootloader? or to be with Knox bootloader but everything fine like it was before.
Disadvantages are
I can't use Knox feature now.
Cannot update my device OTA or through Samsung Kies so downloading form Sammobile and flashing takes a lot of time.
I don't have any other problem I am running on stock rom 4.3 but I want that I should able to update my mobile OTA and if possible able to use KNOX feature again.
Thank you
Have a nice day
Click to expand...
Click to collapse
So far, this issue of 0x1 back to 0x0 is still fly high in the air. I read a lot of thread regarding this issue, until I myself also a bit headache
But, from my understanding after reading so many thread... Once it tripped, there's no way to return back. And you can't (theoritically) to revert back to 4.1.2 bootloader, but perhaps, there's a way. And yes, once it tripped, you can't use any KNOX features.
I still have no better conclusion as well regarding this issue. I got read 1 time somebody is able to revert back to 4.1.2, but still with KNOX 0x1. Most are failed. You may want to read all the thread regarding this issue with a search.
I'm here not to answer exactly on how to revert back. But just to share what I know regarding this tripping issue. To be frank... I also want to know about this, as I need to root my MJ7 Note 3, which so far... no solution yet for the tripping KNOX, so I still hold on to it.

YOu can root if you have not trip 0x1 without tripping it.
antique_sonic;49546705
I also want to know about this said:
I found a way today on the internet that If Note 2 is at 0x0 flag you can root it without increasing the count but it will show custom that you can revert back to original by triangle away may be there is a way for Note 3 too.
I have already rooted so problem starts here
Click to expand...
Click to collapse

I have a rooted official 4.3 OTA rom knox is 1. I used triangle away to make it official. when i check for updates it say that i have the latest rom. I think i can use ota update even knox is 1
Sent from my GT-N7100 using xda app-developers app

Not for me.
tadz202 said:
I have a rooted official 4.3 OTA rom knox is 1. I used triangle away to make it official. when i check for updates it say that i have the latest rom. I think i can use ota update even knox is 1
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I used triangle away also this is my device status in Downloading mode.
Custom binary download No
Current Binary Samsung Official
System Status Offcial
Knox Warranty Void 1
but in Software update you device is modified. May it is showing you because you have already the latest update. Please can you tell me the Device status in Downloading mode also please report back if you are able or not to download update OTA when available.
Thank you.

Same boat
My phone is in the same boat as you. My desire was not so much KNOX as to have 4.3 with phone encryption and root. In order to succeed with my desire, I have to leave the stock 4.3 recovery intact. This greatly reduces my root options. I had root before the update, but it was unable to update after going to 4.3. I tried Kingo in an attempt to fix root, but to no avail. I decided to unroot and re-root. I used Kingo to unroot. From there I had to run saferoot a few times before it was finally able to install SuperSU and associated files. The version it installed is the latest so I'll have to wait until the next release to find out if it can update. Everything else seems to work fine except ES File Explorer appears to no longer be able to mount the /system RW.
saferoot can be found over here
http://forum.xda-developers.com/showthread.php?t=2565758
Hope that helps,
Ddfault
XenonTNT said:
I used triangle away also this is my device status in Downloading mode.
Custom binary download No
Current Binary Samsung Official
System Status Offcial
Knox Warranty Void 1
Click to expand...
Click to collapse

[Q] Note 8.0 Custom Rom

Hi guys I am new to this tablet so any advice but be appreciated.
If i update to kitkat I am told the knox security feature would be installed too.
What if I leave my note 8.0 on 4.2 and root and use custom roms and then if I decide to unroot and flash kitkat, would knox be triggered due to historic custom roms?

fazzxx said:
Hi guys I am new to this tablet so any advice but be appreciated.
If i update to kitkat I am told the knox security feature would be installed too.
What if I leave my note 8.0 on 4.2 and root and use custom roms and then if I decide to unroot and flash kitkat, would knox be triggered due to historic custom roms?
Click to expand...
Click to collapse
Pretty sure flashing a custom recovery will trip knox. No way around it. http://forum.xda-developers.com/showthread.php?t=2800290

Ok thanks what if I just root and not flash a custom rom, would this trigger the knox?

fazzxx said:
Ok thanks what if I just root and not flash a custom rom, would this trigger the knox?
Click to expand...
Click to collapse
It depends on the rooting method you use. The one I used to root 4.4.2 after I updated via Odin was Chainfire's CF-Auto-Root and that tripped KNOX because it installs an unsigned (by Samsung) custom recovery temporarily before re-flashing the stock version.
I've never used Kingo but they claim to be able to root the Note 3 without tripping the KNOX flag so their method using an Android vulnerability to gain temporary root might work for the Note 8.0 as well.
My suggestion would be to use these forums and Google to research all the current methods for rooting the Note 8.0 and make sure there are users who have done it successfully with the KitKat boot loader installed and not tripped the KNOX "warranty" indicator.
Based on the KNOX articles I've read it appears that flashing, or even booting, an insecure kernel can set the eFuse switch which is said to be "impossible" to reverse, so flashing custom kernels and ROM's is out even if you can get root with the stock ROM without tripping the indicator.
I can understand the requirement for KNOX in high security environments but automatically voiding the warranty is just encouraging users to brick their devices in ways that prevent the KNOX flag from being accessed. Perhaps Samsung's position is that once the eFuse flag is set even their service centers cannot reverse it so the device is not able to reconditioned and sold since a tripped KNOX flag also disables some security features in the stock ROM.
Edit: I just read your OP again and if you don't flash the 4.4.2 (KitKat) bootloader and root with CF-Auto-Root you should be fine, even flashing custom kernels and ROM's, and still go back to a completely stock configuration using Odin to install the stock 4.2.2 ROM and TriangleAway to reset the flash counter. AFAIK there is no check of any historical data when the KNOX enabled 4.4.2 bootloader is installed but I would make sure that TriangleAway has successfully reset the flash counter before upgrading just to be safe.
ramjet73

[Q/A] Answers Added - OTA's/Updates, rooting & tripping Knox? - other questions

So I rooted using chainfires method for my Tab S 8.4 wifi (T700) and it tripped Knox (0x1). I know there is no way to currently reset it and there is a bounty out for it. No big deal on tripping it, I wanted to root anyways and want to try out CM12 eventually. After doing some research it appears Knox gets tripped when unofficial firmware or recoveries get flashed via Odin. Knox is not tripped when you flash official Samsung firmware. I had a few questions though I can't seem to get a clear answer on and was hoping to find some or get a discussion going at least about Knox for the Tab S.
Questions and Answers
- Are you still able to receive OTA updates on a stock rooted rom/recovery with Knox tripped?
A: No, not while rooted, "Operating System on your device has been modified in an unauthorized way. Try downloading software updates using Samsung Kies on your PC" Unsure if Knox prevents it but most likely does not.
- Will you lose root if you can get OTA updates?
A: No OTA Updates allowed on rooted devices. Reports have stated that flashing the official firmware update via odin will unroot the device but maintain data, most likely kies is the same when updating. However if a bootloop occurs after flashing, you may need to wipe data and cache via stock recovery.
- If knox is tripped (0x1), if I flash a custom recovery (TWRP/CWM) or use chainfires method to root again will it trip Knox again (0x2)?
A: YES & NO, Knox will not read (0x2) if unofficial img's are flashed via Odin but reports on other devices have stated it will read {0x1(2)}
- If yes can you trip Knox too many times, rendering device inoperable or bricked?
A: NO, tripping Knox only informs if warranty has been voided by flashing unofficial firmware/recovery/img files and root kernals via Odin. When the knox warranty void status is tripped, the knox software will no longer work.
- What is tripped specifically in Knox (for the Galaxy Tab S), an efuse, or is it software or binary code?
A: Most likely an eFuse. There is no way to reset the flag counter as it is believed to be an eFuse that once gets blown it stays damaged and cannot be reset.
***New Questions***
- Will flashing a custom recovery img (TWRP/CWM) via ADB trip Knox (0x1)?
A: Yes, it will trip Knox.
Thanks to all who answer and contribute.
If there are any new questions, updates to be added or wrong information to be corrected please let me know.

No OTAs when you are rooted on custom rom. Dont worry, someone will make a stock custom rom to flash with twrp Or you can odin flash stock lollipop and root with twrp
If you do the ota it will probably not install because of root.
If you flash a custom recovery, or root again.. Knox will stay 0x1. It wont change.
Knox is like a check when booting up your device. Its more like uhh protection. If you install custom stuff then you dont get protection. Knox was a security feature that samsung included. Its really not needed as it really doesnt work. Thats why people trip it. I highly doubt its used for security but I think its just used to detect if warranty has been void or not. Its not something that you should worry.
Hope this helps!

DUHAsianSKILLZ said:
No OTAs when you are rooted on custom rom. Dont worry, someone will make a stock custom rom to flash with twrp Or you can odin flash stock lollipop and root with twrp
If you do the ota it will probably not install because of root.
If you flash a custom recovery, or root again.. Knox will stay 0x1. It wont change.
Knox is like a check when booting up your device. Its more like uhh protection. If you install custom stuff then you dont get protection. Knox was a security feature that samsung included. Its really not needed as it really doesnt work. Thats why people trip it. I highly doubt its used for security but I think its just used to detect if warranty has been void or not. Its not something that you should worry.
Hope this helps!
Click to expand...
Click to collapse
Thanks, I figured Knox is nothing more than just a feature to let Tech's know if the warranty had been voided. Also I figure that flashing the updates myself when they come out would be the best option. Thanks again.

how do you make the knoxx counter back to zero ??
methslushee said:
Thanks, I figured Knox is nothing more than just a feature to let Tech's know if the warranty had been voided. Also I figure that flashing the updates myself when they come out would be the best option. Thanks again.
Click to expand...
Click to collapse
is there a limit to knox number and how can it be made to zero again to retain warranty

[email protected] said:
is there a limit to knox number and how can it be made to zero again to retain warranty
Click to expand...
Click to collapse
Read post two above yours. It can not be reset to zero once it's tripped.

Even if you root and trip knox, although you cannot receive official ota's, you can still use samsung kies to still recieve the updates.

updated OP with answers to questions.

Stupid Knox. This is one "feature" of Samsung devices which makes me less likely to purchase them in the future.

For the new question, flashing any custom recovery with odin or adb will trip knox. Flashing stock should not trip

Note 3 Rooting

I have a Note 3 and im trying to figure out the process of rooting without tripping the Knox Counter. I rooted my Note 2, years ago and has been awhile. Also like to know is there a "triangle away" method to reset the counter.
Model: SM-900T
Android: 5.0
Baseband: N900TUVUFOL1
Kernel: 3.4.0-6005498
Knox: 2.3
Thanks in advance

As far as I know, there is no way to root without tripping Knox.
If the phone is not under warranty, tripping knox should not be an issue. I have tripped Knox on a few phones and have never had an issue.

I asked the same question a while back, and only just 2 days ago rooted my SM-N900T knox 0x0. Asked: Here.
To achieve root on the note 3 without tripping knox you must downgrade from the Lollipop firmware OB6, or FOL1 to NE6 using PC Odin.
Once downgraded to NE6 download and use TowelRoot. This will unlock root without tripping knox, NE6 was the last vulnerable firmware for towelroot on the t-mobile note 3.
Make sure you are flashing official t-mobile firmwares only for kitkat/lollipop when using PC odin.
Flashing any custom recovery, kernal, rom, bootloader, or no longer supported android version (4.3 jellybean) will trip knox.
You can use sammobile to get official firmwares, or if you're risky there are likely download mirrors scattered through the internet.
Once you're rooted on kitkat NE6, to get back to Lollipop and keep root you'll need Mobile Odin Pro to flash FOL1 with the latest Super SU Zip v2.46. (instructions first page of this thread: Here.)
Rooting seems to require some gonads and research first.
When using PC Odin I left options default (Auto Reboot and F. Reset Time).
When using Mobile Odin Pro (or maybe flashfire) make sure to uncheck EverRoot!
Flashfire is the newer free mobile odin pro I think. You might be able to use it in place of Mobile Odin Pro and instead of the supersu zip in addition to flashing FOL1 it comes with an option to inject SuperSU.
I recommend sticking with mobile odin pro for confirmed results. MOP does not support Lollipop.
Note that once you're rooted and upgrade to Lollipop your android system status will change from normal to custom. This prevents future OTA updates.
Root survives factory reset, but flashing official firmware with pc odin will make your phone genuine again as long as you didn't trip knox.
Downgrading to kitkat will very likely require a factory restore. Possibly also when upgrading back to Lollipop.
Note that the XPosed framework on lollipop and samsung touchwiz stock roms does not seem supported.
It seems some people have flashed a Deodexed rom and unofficial xposed to have it working. I made a single attempt and was unable to have it working.
I assume you could stay on kitkat and manage to get xposed working easy.
If you decide to use xposed, do not try to flash the framework without mobile odin pro, or flashfire.
Using a custom recovery, or flashing anything custom with PC Odin will trip knox.
Look over the information around to get a comfortable understanding and good luck!
Proceed only with the understanding that you could always on accident trip knox, or brick your phone.
I believe there is no known way to reset knox flag to 0 on the SM-N900T.
For future readers using a newer firmware than FOL1 it may no longer be possible to pc odin downgrade to kitkat without tripping knox.

So there is no way of downgrading without tripping knox

You can downgrade to kitkat NE6 using PC odin from t-mobile lollipop firmware OB6/OL1. (OL1 being the latest lollipop firmware, OB6 a version older). Once on kitkat NE6 firmware u can use towelroot to gain root and you will not trip knox. Unless you manage to check an option somewhere during this process that would cause you to trip knox. .
As stated, I achieved downgrading/rooting without tripping knox just a couple days ago from the current latest t-mobile galaxy note 3 (SM-N900T) firmware FOL1.
I then upgraded back from KitKat NE6 to Lollipop FOL1 using mobile odin pro.
You can probably downgrade to any 4.4 kitkat firmware, NOT 4.3 jellybean, just fine without tripping knox if you have a kitkat, or lollipop firmware up to FOL1.

I'll try it later, I also want to know if custom roms are possible

From what I've read you can install a custom rom as long as it has a stock kernel, otherwise you trip knox. You would need to flash with flashfire, or mobile odin pro though...
I've only used the stock firmware on my note 3 so don't completely know about using a custom rom.

I don't think a custom ROM can be flash via Odin. A custom ROM requires a custom recovery and a custom recovery will trip Knox on a stock KK or LP AFAIK.

Ohh ok. This is all sorta new to me as well. I had just assumed mobile odin pro could because FlashFire is its "successor".

Will XPosed Framework trigger knox?

Will the xposed framework trip knox 0x1 from the app itself? As long as you don't flash a custom rom/recovery/bootloader anyways.
I've read conflicting things and can't seem to find a direct answer.
Just recently rooted and am on the latest firmware FOL1 Lollipop 5.0 with root and knox 0x0.
Wanted to use a couple modules like AdAway and play youtube in the background. Possibly more assuming knox will stay 0x0.
For now edited the hosts file!

Xposed won't run on Stock Lollipop. A deodexed ROM must be used. So, if you want lollipop and the Xposed Framework, you'll have to trip knox to install a custom ROM, even if it is stock deodexed.

tygerchylde said:
Xposed won't run on Stock Lollipop. A deodexed ROM must be used. So, if you want lollipop and the Xposed Framework, you'll have to trip knox to install a custom ROM, even if it is stock deodexed.
Click to expand...
Click to collapse
I actually had flashed a stock deodexed OB6 using FlashFire without tripping knox. When I flashed the unofficial framework v 75 with flashfire, it did not seem to work though... I believe I may have needed v71 according to reading a post with a similar issue. Requires another attempt, but for now I've decided to stick with my current setup.

Dreamgun said:
I actually had flashed a stock deodexed OB6 using FlashFire without tripping knox. When I flashed the unofficial framework v 75 with flashfire, it did not seem to work though... I believe I may have needed v71 according to reading a post with a similar issue. Requires another attempt, but for now I've decided to stick with my current setup.
Click to expand...
Click to collapse
Wow. I wasn't aware it was possible to flash a stock deodexed ROM without tripping Knox.
Wish I had known that before I installed twrp...