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] Please help me. Knox!

Hello guys!!!
I have a Galaxy Note II N7100 for the past 1 year. I recently installed Hurricane v 8 rom which is based on 4.3 firmware.As I was using it, I realized the RAM was increasing up to 1.3 GB, the only thing that could fix it was to reboot the phone. Later I watched a youtube review of a Note II with an official 4.3 installed and the RAM was about 600 MB on that persons phone. So I went ahead and downloaded a 4.3 firmware N7100DDUEML4 from sammobile.com. After the installation via Odin I boot the phone and it was fine. I read a few articles on how I can root the 4.3 firmware with CF Autoroot and did it as it should be done. After the reboot, Knox blocked the SU and the KNOX flag went to 0x1. After all this I decided to install Philz Recovery via Odin and got access to recovery. My plan was to recover my Hurricane Rom that I previously backed up. After Philz recovery restored the Hurricane Rom, I got stack on Boot Screen. Because Knox is flagged 0x1 I can't install any firmware via Odin anymore. So the next step I did is to restore my phone via Kies. I managed to successfully restore it and now I have a 4.3 firmware N7100XXUEMK9 firmware and Android Status As Enforcing. How can I get root access with this firmware and what should I do with Knox flag 0x1?
Thank you in advance guys!!!

The SafeRoot exploit has been confirmed working for N7100 too (check here), but it can't help to reverse Knox flag 0x1. Try it out. it should work. Anyway, why bother warranty after 12 months?
MichaelVaughn said:
Hello guys!!!
I have a Galaxy Note II N7100 for the past 1 year. I recently installed Hurricane v 8 rom which is based on 4.3 firmware.As I was using it, I realized the RAM was increasing up to 1.3 GB, the only thing that could fix it was to reboot the phone. Later I watched a youtube review of a Note II with an official 4.3 installed and the RAM was about 600 MB on that persons phone. So I went ahead and downloaded a 4.3 firmware N7100DDUEML4 from sammobile.com. After the installation via Odin I boot the phone and it was fine. I read a few articles on how I can root the 4.3 firmware with CF Autoroot and did it as it should be done. After the reboot, Knox blocked the SU and the KNOX flag went to 0x1. After all this I decided to install Philz Recovery via Odin and got access to recovery. My plan was to recover my Hurricane Rom that I previously backed up. After Philz recovery restored the Hurricane Rom, I got stack on Boot Screen. Because Knox is flagged 0x1 I can't install any firmware via Odin anymore. So the next step I did is to restore my phone via Kies. I managed to successfully restore it and now I have a 4.3 firmware N7100XXUEMK9 firmware and Android Status As Enforcing. How can I get root access with this firmware and what should I do with Knox flag 0x1?
Thank you in advance guys!!!
Click to expand...
Click to collapse

xbean said:
The SafeRoot exploit has been confirmed working for N7100 too (check here), but it can't help to reverse Knox flag 0x1. Try it out. it should work. Anyway, why bother warranty after 12 months?
Click to expand...
Click to collapse
Thank you so much for your reply, yeah it is true but it is not that I am worried about the warranty, I want to revert back to a different rom and patch a bootloader so I can install custom firmwares.MJ5 bootloader patch doesn't work for me. Is it possible at this time to patch this MK9 or it is still unsolved issue? Thank you once again for your reply.

I have read a lot of posts & make sure I understand the details before I upgrade to v4.3. The far too many failures for upgrades that I've ever seen prior to v4.3 make me more conscious than ever. I'm on MJ5 bootloader & successfully loaded two different custom ROMs without any problem. I suggest you to do more reading in this forums prior to the upgrade. If you're on bootloader newer than MJ5 then I would suggest to stay with the bootloader & root it with the Safeboot method then clean up the KNOX crap. It should work great after the upgrade, root & clean up. cheers.
MichaelVaughn said:
Thank you so much for your reply, yeah it is true but it is not that I am worried about the warranty, I want to revert back to a different rom and patch a bootloader so I can install custom firmwares.MJ5 bootloader patch doesn't work for me. Is it possible at this time to patch this MK9 or it is still unsolved issue? Thank you once again for your reply.
Click to expand...
Click to collapse

MichaelVaughn said:
Thank you so much for your reply, yeah it is true but it is not that I am worried about the warranty, I want to revert back to a different rom and patch a bootloader so I can install custom firmwares.MJ5 bootloader patch doesn't work for me. Is it possible at this time to patch this MK9 or it is still unsolved issue? Thank you once again for your reply.
Click to expand...
Click to collapse
Try this link it will be helpful to you..
http://forum.xda-developers.com/showpost.php?p=48032704&postcount=4753
:good::good:

4.4.2 bootloader

Where do I go to flash the new 4.4.2 bootloader and baseband
Sent from my SGH-M919 using Tapatalk

http://forum.xda-developers.com/showthread.php?t=2677252
Sent from my SGH-M919 using XDA Premium 4 mobile app

How do I flash with mobile odin
Sent from my SGH-M919 using Tapatalk

Can I ask...
I've been reading thru some of these threads, and I'm coming to the conclusion that even with KitKat the bootloader is still unlocked, is this true? I have at&t version and they started locking that down with 4.3 JB.
Thanks.

MoodSwinger said:
I've been reading thru some of these threads, and I'm coming to the conclusion that even with KitKat the bootloader is still unlocked, is this true? I have at&t version and they started locking that down with 4.3 JB.
Thanks.
Click to expand...
Click to collapse
Correct, fortunately still unlocked.

muniz_ri said:
Correct, fortunately still unlocked.
Click to expand...
Click to collapse
This caught my eye. How is that possible with the bootloader unlock, is that just for AT&T? I am on T Mobile GS4 running 4.3 and I can see the knox counter on it 0x0 and I was informed that once updated from 4.2 to 4.3 and above the bootloader is now locked. Please clarify I would like to know. I am rooted though on stock through using this forum and have not tripped knox using this method. http://forum.xda-developers.com/showthread.php?t=2565758
I would love to find a way to install CWM without tripping the counter and trying other roms again but I here I can use bootstrap to run a custom rom, but no word on getting CWM installed without tripping the counter......unless I am wrong and I hope I am!
Thanks,
Mr Wizard

mr wizard said:
This caught my eye. How is that possible with the bootloader unlock, is that just for AT&T? I am on T Mobile GS4 running 4.3 and I can see the knox counter on it 0x0 and I was informed that once updated from 4.2 to 4.3 and above the bootloader is now locked. Please clarify I would like to know. I am rooted though on stock through using this forum and have not tripped knox using this method. http://forum.xda-developers.com/showthread.php?t=2565758
I would love to find a way to install CWM without tripping the counter and trying other roms again but I here I can use bootstrap to run a custom rom, but no word on getting CWM installed without tripping the counter......unless I am wrong and I hope I am!
Thanks,
Mr Wizard
Click to expand...
Click to collapse
I want to know that too.

mr wizard said:
This caught my eye. How is that possible with the bootloader unlock, is that just for AT&T? I am on T Mobile GS4 running 4.3 and I can see the knox counter on it 0x0 and I was informed that once updated from 4.2 to 4.3 and above the bootloader is now locked. Please clarify I would like to know. I am rooted though on stock through using this forum and have not tripped knox using this method. http://forum.xda-developers.com/showthread.php?t=2565758
I would love to find a way to install CWM without tripping the counter and trying other roms again but I here I can use bootstrap to run a custom rom, but no word on getting CWM installed without tripping the counter......unless I am wrong and I hope I am!
Thanks,
Mr Wizard
Click to expand...
Click to collapse
I think you have a definition difference. The bootloader is unlocked on the TMO S4. That is you can use the bootloader to update and install modems, roms, recoveries, etc. It is not locked and will let you do this.
However, if you use the 4.3 and above bootloader, it will set a flag if you flash a recovery. This is known as the Knox Warranty flag. And, this is what is shown on the ODIN or bootloader screen.
BTW, if you update to NB4 (Kit Kat) with a 4.3 bootloader or later, the SafeRoot method will not work. The only known rooting method at this time is the CF-Auto-Root which will trip the Knox flag. So, if you are fully stock 4.4.2 you will trip your Knox flag if you root the phone.
However, you can do it. It doesn't lock you out of doing it. It just records that you've done it.
Rob

rlichtefeld said:
I think you have a definition difference. The bootloader is unlocked on the TMO S4. That is you can use the bootloader to update and install modems, roms, recoveries, etc. It is not locked and will let you do this.
However, if you use the 4.3 and above bootloader, it will set a flag if you flash a recovery. This is known as the Knox Warranty flag. And, this is what is shown on the ODIN or bootloader screen.
BTW, if you update to NB4 (Kit Kat) with a 4.3 bootloader or later, the SafeRoot method will not work. The only known rooting method at this time is the CF-Auto-Root which will trip the Knox flag. So, if you are fully stock 4.4.2 you will trip your Knox flag if you root the phone.
However, you can do it. It doesn't lock you out of doing it. It just records that you've done it.
Rob
Click to expand...
Click to collapse
So if Knox counter doesn't matter you can still root device..are you still able to install custom roms? or isn't that possible ATM? Trying to get rid of the severe lag 4.4.2 OTA update has bestowed upon my gf's phone.

PaSsAtDrOiD said:
So if Knox counter doesn't matter you can still root device..are you still able to install custom roms? or isn't that possible ATM? Trying to get rid of the severe lag 4.4.2 OTA update has bestowed upon my gf's phone.
Click to expand...
Click to collapse
You can flash anything you want with the TMO S4.
However, if you need to return it for warranty, they MAY check the Knox flag, and they MAY not do the warranty service for free. That hasn't been shown to be a fact, but it is the reason for the flag in the first place.
It has been stated by a few people that re-flashing back to full stock will remove the Knox flag. I cannot verify it, since I haven't tried it.
Rob

Can anyone shed some light on a couple of points? I currently have the MDL bootloader along with the NB4 modem. This all runs fine with my daily driver (LightSpeed) 4.2.2 ROM, as well as the (Insane Kit Kat) 4.4.2 I've been experimenting with. I do understand that I can't go back to the MDL bootloader if I update. Knox issues aside, is there any actual advantage to having the new bootloader? Since my warranty is running out soon anyways, I'm not too worried about tripping Knox. So, does the NB4 bootloader offer any real performance or feature advantages? Can I still run 4.2.2 or 4.3 ROMs with it, or will it limit me to 4.4.2+ ROMs? Does it impact the usage of different kernels? Thanks!

rlichtefeld said:
You can flash anything you want with the TMO S4.
However, if you need to return it for warranty, they MAY check the Knox flag, and they MAY not do the warranty service for free. That hasn't been shown to be a fact, but it is the reason for the flag in the first place.
It has been stated by a few people that re-flashing back to full stock will remove the Knox flag. I cannot verify it, since I haven't tried it.
Rob
Click to expand...
Click to collapse
It won't remove the Knox flag although they MAY not check it or they MAY when I did my warrenty return they did not but that doesn't mean it will always be the case
Sent from my SGH-M919 using Tapatalk

hella356 said:
Can anyone shed some light on a couple of points? I currently have the MDL bootloader along with the NB4 modem. This all runs fine with my daily driver (LightSpeed) 4.2.2 ROM, as well as the (Insane Kit Kat) 4.4.2 I've been experimenting with. I do understand that I can't go back to the MDL bootloader if I update. Knox issues aside, is there any actual advantage to having the new bootloader? Since my warranty is running out soon anyways, I'm not too worried about tripping Knox. So, does the NB4 bootloader offer any real performance or feature advantages? Can I still run 4.2.2 or 4.3 ROMs with it, or will it limit me to 4.4.2+ ROMs? Does it impact the usage of different kernels? Thanks!
Click to expand...
Click to collapse
If you don't care about knox you better off going to the new bootloader ,the NB4 wifi driver is not present on the MDL bootloader so you still using the old wifi. I notice very strong wifi signal after upgrade to kitkat bootloader to flashed modem and wifi fix.The best way is to flash the NB4 firmware through Odin so you can get everything needed and go from there.

Thanks, makomek. I've been wondering about that, but haven't really found much info beyond the Knox implications. I have gotten an improvement in general phone call stability and download speed with the NB4 modem. Is what your're talking about related to the NON-HLOS.bin being installed? As I recall, that was to improve LTE, but I apparently it's actually related to WiFi. Or could be both? At least it's good to hear there are positive reasons to update the bootloader. Any idea if doing this would lock me into only using KitKat ROMs/kernels, or would 4.2/4.3 still work? Your input is much appreciated.
makomek said:
If you don't care about knox you better off going to the new bootloader ,the NB4 wifi driver is not present on the MDL bootloader so you still using the old wifi. I notice very strong wifi signal after upgrade to kitkat bootloader to flashed modem and wifi fix.The best way is to flash the NB4 firmware through Odin so you can get everything needed and go from there.
Click to expand...
Click to collapse

PaSsAtDrOiD said:
So if Knox counter doesn't matter you can still root device..are you still able to install custom roms? or isn't that possible ATM? Trying to get rid of the severe lag 4.4.2 OTA update has bestowed upon my gf's phone.
Click to expand...
Click to collapse
If your girlfriend's phone is stock, unrooted, and she took the OTA, the easiest way to get rid of lag is to factory reset. If she doesn't care about being rooted and just wants the stock rom, this is the easiest way to improve performance. Just start over. OTAs, in my opinion, are like a dirty flash.

[Q] Successfully Rooted with Towelroot on Note 3(SM-N900T), have some questions...

Successfully rooted without tripping Knox with Towelroot. NE6 firmware. I have T-Mobile Jump and would like to Jump to the Note 4 when it comes out. If I install TWRP and make a backup of stock, will I trip knox and void my JUMP eligibility? Wanted to install via Flashify and install Xposed framework at some point down the line.
Thanks!

Steameffekt said:
Successfully rooted without tripping Knox with Towelroot. NE6 firmware. I have T-Mobile Jump and would like to Jump to the Note 4 when it comes out. If I install TWRP and make a backup of stock, will I trip knox and void my JUMP eligibility? Wanted to install via Flashify and install Xposed framework at some point down the line.
Thanks!
Click to expand...
Click to collapse
Yes.. Custom recovery or custom kernel will trip knox
Sent from my SM-N900T using Tapatalk

effortless said:
Yes.. Custom recovery or custom kernel will trip knox
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
If I flashed back to stock, did a factory reset, would it still say custom?

Steameffekt said:
If I flashed back to stock, did a factory reset, would it still say custom?
Click to expand...
Click to collapse
As long as you didn't flash a custom kernel or recovery, it should be OK once you flash stock.
Even if you trip Knox, flash back to stock and jump when the time comes. They generally don't care about that as long as your phone is not damaged.
Knox warranty void is not the phone warranty. It's telling you Knox can't secure your phone anymore. Its (Knox's) warranty is void. People all over the Internet don't even know what Knox is and they spread misinformation.
Look up what Knox really is. It is an app that runs on your phone and creates a secure Android environment within itself. It's like another phone with its own launcher and app store that is secure. It's meant for employees to use their personal phone for work purposes as well.
When you trip the Knox warranty, Knox triggers an efuse that will prevent the secure container from being able to be created... Meaning Knox will never work again on your phone. It's a security measure so that companies will take the Samsung phones seriously in the work space. In reality it has worked for them as the department of defense recently approved a few Samsung models with Knox.
If you don't plan on using Knox for anything, then trip Knox and enjoy custom kernels/recoveries etc. If you do plan on using it, it's not a good idea to even root your phone as the whole purpose of Knox is to be secure and rooting will make Knox vulnerable.. You might even get fired if your IT department finds out.
Sent from my SM-N900T using Tapatalk

effortless said:
Yes.. Custom recovery or custom kernel will trip knox
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
effortless said:
As long as you didn't flash a custom kernel or recovery, it should be OK once you flash stock.
Even if you trip Knox, flash back to stock and jump when the time comes. They generally don't care about that as long as your phone is not damaged.
Knox warranty void is not the phone warranty. It's telling you Knox can't secure your phone anymore. Its (Knox's) warranty is void. People all over the Internet don't even know what Knox is and they spread misinformation.
Look up what Knox really is. It is an app that runs on your phone and creates a secure Android environment within itself. It's like another phone with its own launcher and app store that is secure. It's meant for employees to use their personal phone for work purposes as well.
When you trip the Knox warranty, Knox triggers an efuse that will prevent the secure container from being able to be created... Meaning Knox will never work again on your phone. It's a security measure so that companies will take the Samsung phones seriously in the work space. In reality it has worked for them as the department of defense recently approved a few Samsung models with Knox.
If you don't plan on using Knox for anything, then trip Knox and enjoy custom kernels/recoveries etc. If you do plan on using it, it's not a good idea to even root your phone as the whole purpose of Knox is to be secure and rooting will make Knox vulnerable.. You might even get fired if your IT department finds out.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Makes sense and I probably will flash a custom recovery. I just don't understand the fuss with people wanting not to trip knox if they're not even gonna use it.

I successfully rooted my Tmo Note 3 with Towelroot v2. I am currently on NE6 Boot-loader and have Knox at 0x0 and would like to remain there. I would like to upgrade to the new firmware NF1 which is not rootable with Towelroot yet. Does anyone know if using Mobile Odin Pro is able to keep root if manually done without breaking/tripping Knox? I think I remember reading somewhere that it was okay to do so and ignore the message even though it asks to download a file and then it gives a warning saying that:
"Using, Mobile Odin on this device will void your warranty, as the Knox counter will be triggered .This is not reversible".
Can someone confirm if its Okay to ignore the warning and that activating Mobile Odin Pro on my phone is OK without triggering Know 0x1, or was that other posting I read somewhere wrong? I cannot remember where I read it. If not possible to use Mobile Odin without triggering Knox 0x1,. is there any other way to root NF1 without triggering knox on our device? What do you guys think?

un-answered question............
I don't know why I have not asked this before, but here it goes..........
First, I just want to say that I could care less about Knox...
(my phone already has the knox pox)
But for future reference if I had a brand new Note 3 with official stock NB4 baseband
and I rooted it successfully using Towelroot (or root de la vaga) would it be possible
to simply rename a custom rom like Hyperdrive to "update.zip" and copy it to the
internal sdcard then boot into the stock NB4 recovery and flash/install "update.zip"?
If the only problem with this method would be the fact that a different kernel would
also flashed along with the rom it would be an easy fix by just removing the kernel
from the custom rom file before flashing the update.zip?
I know that more likely than not this method would not work.
But if it did work it should not trip the knox right?

Eudeferrer said:
I successfully rooted my Tmo Note 3 with Towelroot v2. I am currently on NE6 Boot-loader and have Knox at 0x0 and would like to remain there. I would like to upgrade to the new firmware NF1 which is not rootable with Towelroot yet. Does anyone know if using Mobile Odin Pro is able to keep root if manually done without breaking/tripping Knox? I think I remember reading somewhere that it was okay to do so and ignore the message even though it asks to download a file and then it gives a warning saying that:
"Using, Mobile Odin on this device will void your warranty, as the Knox counter will be triggered .This is not reversible".
Can someone confirm if its Okay to ignore the warning and that activating Mobile Odin Pro on my phone is OK without triggering Know 0x1, or was that other posting I read somewhere wrong? I cannot remember where I read it. If not possible to use Mobile Odin without triggering Knox 0x1,. is there any other way to root NF1 without triggering knox on our device? What do you guys think?
Click to expand...
Click to collapse
Sent from my SM-N900T using xda premium

re: modile odin - knox
Eudeferrer said:
I successfully rooted my Tmo Note 3 with Towelroot v2. I am currently on NE6 Boot-loader and have Knox at 0x0 and would like to remain there. I would like to upgrade to the new firmware NF1 which is not rootable with Towelroot yet. Does anyone know if using Mobile Odin Pro is able to keep root if manually done without breaking/tripping Knox? I think I remember reading somewhere that it was okay to do so and ignore the message even though it asks to download a file and then it gives a warning saying that:
"Using, Mobile Odin on this device will void your warranty, as the Knox counter will be triggered .This is not reversible". Can someone confirm if its Okay to ignore the warning and that activating Mobile Odin Pro on my phone is OK without triggering Know 0x1, or was that other posting I read somewhere wrong? I cannot remember where I read it. If not possible to use Mobile Odin without triggering Knox 0x1,. is there any other way to root NF1 without triggering knox on our device? What do you guys think?
Click to expand...
Click to collapse
I just checked and it's OK to "install" Mobile Odin on your phone and it
it will NOT trip the KNOX counter by simply installing it as long as you:
1: Don't flash any custom recoveries like twrp/cwm.
2: Don't flash any stock or custom kernels.
3: Don't flash any modems/baseband or bootloaders.
4: Don't flash any custom odin flashable firmwares.
In mobile odin there is no option to flash cwm/twrp
flashable zip files of any kind including custom roms.
Good luck!

Misterjunky said:
I just checked and it's OK to "install" Mobile Odin on your phone and it
it will NOT trip the KNOX counter by simply installing it as long as you:
1: Don't flash any custom recoveries like twrp/cwm.
2: Don't flash any stock or custom kernels.
3: Don't flash any modems/baseband or bootloaders.
4: Don't flash any custom odin flashable firmwares.
In mobile odin there is no option to flash cwm/twrp
flashable zip files of any kind including custom roms.
Good luck!
Click to expand...
Click to collapse
Why would flashing a stock kernel/baseband or firmware cause Knox to change to 0x1 when done through Mobile Odin? I thought this would happen only through custom based ones?

re: knox - mobile odin
Eudeferrer said:
Why would flashing a stock kernel/baseband or firmware cause Knox to change to 0x1 when done through Mobile Odin? I thought this would happen only through custom based ones?
Click to expand...
Click to collapse
First of all I never said not to odin flash stock official firmware in my post.
If you or anyone else knows for sure that the modem/baseband or kernel you are
wanting to flash are 100% official stock 4.4.2 Kitkat NB4/NE6/NF1 versions then
its just fine to flash those.
However since knox cannot be rolled back and to keep things on the SAFE side I
always suggest the very safest way to do these things which even a NOOB would
understand without getting into trouble with a lot of unexpected issues. :laugh:
Good luck!

Misterjunky said:
First of all I never said not to odin flash stock official firmware in my post.
If you or anyone else knows for sure that the modem/baseband or kernel you are
wanting to flash are 100% official stock 4.4.2 Kitkat NB4/NE6/NF1 versions then
its just fine to flash those.
However since knox cannot be rolled back and to keep things on the SAFE side I
always suggest the very safest way to do these things which even a NOOB would
understand without getting into trouble with a lot of unexpected issues. :laugh:
Good luck!
Click to expand...
Click to collapse
My bad. I guess I misunderstood you the first time. Thank you for your response.

[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