Develop Bugs

[q] kernel is not seandroid enforcing

I've installed the latest Tmobile 4.4.2 Firmware via SamMobile. I came from M17 4.3. Updated via Odin to Tmobile 4.4.2, I then rooted via CF Auto root (Don't care about Knox at this point) successfully and following that flashed Philz recovery with success.
Everything is all good, as I am familiar with other devices and rooting and booting into recovery. At this point I downloaded the latest SlimKat and Lean Kernel to flash onto my system. Reboot into recovery, flash is a success, however when I reboot the system I start to get a bootloop saying Kernel is not seandroid enforcing set warranty bit: Kernel..I've tried to JUST flash SlimKat with the same results. Following this It continues to bootloop so I am forced to Odin from my PC back to Tmobile stock 4.4.2.
Can someone assist me with a solution? TLR, Custom ROMs/Kernels are not allowing me to boot due to Kernel is not seandroid enforcing set warranty bit: Kernel bootloop

My guess would be that slimkat doesn't support 4.4 bootloader yet.

Oh wow, if it was that simple the whole time..Lol, is there a list of ROMs that do?

Custom kernels will ALWAYS show that on boot.
Dev's turn off the SEANDROID permission crap because not all root apps deal with that permission properly.
Bootloop on the other hand would be a different issue doubtfully related to this.

t3tr1s_ said:
Oh wow, if it was that simple the whole time..Lol, is there a list of ROMs that do?
Click to expand...
Click to collapse
You have to read the op of the rom you're interested in. If it doesn't say it supports both bootloaders then it's most probably for 4.3 bl only.
Anthem here says it supports both bl.

I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?

t3tr1s_ said:
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
Click to expand...
Click to collapse
I am not a technical person but how I understand it is that custom recovery/rom flashes doesn't load/replace the bl.
Cm and aosp-based roms were dev'd for 4.3 until a month or two ago when they start supporting both bl and even then not all roms do.

t3tr1s_ said:
I'm confused, can a 4.4.2 ROM only be on a 4.3 BL?
Click to expand...
Click to collapse
Yes, it sure can.
If you're fully upgraded to the KK package completely, ex: through odin, you have to use a KK rom that has the 4.4.2/Kernel bootloader components.
If you don't fully want to commit to KK completely you can flash a KK rom that has a kernel with the older boot loader. That will allow you to go back to 4.3.
I suspect given time, 4.3 support will be slowly dropped in favor of a full KK implementation on this forum. In the transition period, be careful what you pick and choose to install.
I, like many others, have gone full KK inc. bootloader, etc for full compatibility with everything. When you go full update, you get the updated firmware and bits for the modems, etc.

Thank you very much for all your help, it was the bootloader issue. Just me not reading into things fully, very glad that I asked. I am now running Beanstalk on my Note!
Now that I have all of that cleared up, my next question is the S-PEN. I'm assuming all CM/AOSP ROMs will not support it, thus making me switch to TouchWiz. Is that true? Or are there Apps that I can still use in conjunction with my S-PEN?
As far as TouchWiz is concerned, is Xnote updated to the KK BL and compatible with our Tmobile version? I searched the thread but did not find any answer. If not, what is a suitable replacement to maintain funcionality of the S-PEN while having bloatware removed?

There are apps but it won't give you the full Samsung spen experience like on stock.
Sent from my SM-N900T using Tapatalk

As long as I have a note taking app I think i would be good to go. It's really the only feature I use.

also having this problem

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] 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] Atempting to remove Knox from firmware befor update.

I have a T-mobile Galaxy S4, SGH-M919 running android 4.2.2 and want to upgrade to android 4.3. Okay my question is can I remove knox from the update before updating? I HATE KNOX. I saw where over at s4 mini archive they showed a way that they say it can be removed. Any ideas? Anyone tried this? Any other ways to remove??? Any help would be great. I am sorry if this has been posted or asked before, I have not seen it. http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html

Just use this. http://forum.xda-developers.com/showthread.php?t=2544612 and install a custom rom. Any reason why you want 4.3? You can install 4.4.4 which just came out. Remember to just flash modem only and not the lte modem or you will break sound. If you want to stay completely stock and not have Knox there is no way.

+1 on custom rom. Something like this: http://forum.xda-developers.com/showthread.php?t=2876946

Sorry been a little busy. I'm currently using the MDL bootloader, no knox. I hear there is performance and feature advantage to updating to a newer bootloader. The reason I am looking at 4.3 is that some people have stated that you can remove knox from the bootloader in 4.3. The people stated that they have been able to do this to the S4 mini's 4.3 bootloader. I have looked at the links you two have given me, thank you. What bootloaders are you two using? Also have you seen this as this is what got me thinking. http://forum.xda-developers.com/showthread.php?t=2549357

Bootloader has nothing directly to do with performance. Be careful what you read.

lalec said:
Bootloader has nothing directly to do with performance. Be careful what you read.
Click to expand...
Click to collapse
True. But I would prefer to be 100% knox free. So not just a knox free rom, but the bootloader as well. Staying on android 4.2.2 will do that but at the same time I would like to upgrade to a newer android version. I have seen some nice custom roms with nice performance, but they are 4.3 and newer. And this is why I am looking.

Jamessr79 said:
True. But I would prefer to be 100% knox free. So not just a knox free rom, but the bootloader as well. Staying on android 4.2.2 will do that but at the same time I would like to upgrade to a newer android version. I have seen some nice custom roms with nice performance, but they are 4.3 and newer. And this is why I am looking.
Click to expand...
Click to collapse
You can keep MDL boot loader, and flash 4.3, 4.4.2, or 4.4.4 ROMs no problem. I've got an M919 with MDL boot loader and am currently running Dirty Unicorns (4.4.4-based) ROM.
I've got all the benefit of the latest version of Android (plus many customizations!) and no Knox.
The only think that you can't do on the MDL boot loader is run a newer LTE modem... the LTE modem (non-hlos.bin) is tied to the boot loader. However the GSM modem (modem.bin) is not, so you can update that part of it. It's something to keep in mind, but the LTE modem in MDL is fine and works for me quite well even in marginal signal areas.
Marc

Frankenscript said:
You can keep MDL boot loader, and flash 4.3, 4.4.2, or 4.4.4 ROMs no problem. I've got an M919 with MDL boot loader and am currently running Dirty Unicorns (4.4.4-based) ROM.
I've got all the benefit of the latest version of Android (plus many customizations!) and no Knox.
The only think that you can't do on the MDL boot loader is run a newer LTE modem... the LTE modem (non-hlos.bin) is tied to the boot loader. However the GSM modem (modem.bin) is not, so you can update that part of it. It's something to keep in mind, but the LTE modem in MDL is fine and works for me quite well even in marginal signal areas.
Marc
Click to expand...
Click to collapse
Thank you for the info. Are you on an AOSP 4.4.4 ROM (Dirty Unicorns)? I'm on the MDL bootloader looking to install a TW 4.4.4 ROM.

HKSpeed said:
Thank you for the info. Are you on an AOSP 4.4.4 ROM (Dirty Unicorns)? I'm on the MDL bootloader looking to install a TW 4.4.4 ROM.
Click to expand...
Click to collapse
A stock firmware? If it contains the bootloader, it will automatically replace your existing one.
tetakpatalked from Nexus 7 flo

HKSpeed said:
Thank you for the info. Are you on an AOSP 4.4.4 ROM (Dirty Unicorns)? I'm on the MDL bootloader looking to install a TW 4.4.4 ROM.
Click to expand...
Click to collapse
Yes, it's based off AOSP. See the Samsung home page for Dirty Unicorns here. Also the G+ Community for it.
If you are looking for a TW ROM, I had a great experience with GoldenEye v. 38 over the summer. Very stable, and everything worked, even on my ATT version S4 I337 using SafeStrap. I got sick of SafeStrap limitations and eventually bought a M919 so I could do anything I wanted ROM wise... but GoldenEye was very nice. Debloated, very stable, felt good.
Being very satisfied with my current version of Dirty Unicorns, I'll probably not change any time soon, thought I've been tempted to install SlimKat and build up the features I want. I use SlimKat on a tablet, and like it's very light footprint. Quite zippy.
Marc

tetakpatak said:
A stock firmware? If it contains the bootloader, it will automatically replace your existing one.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Just something to remember: Bootloaders (all the bad KNOX junk) CANNOT be flashed via custom recovery. So if you are flashing a stock ROM (firmware?) via custom recovery you will NOT get KNOX. If, however you decide to flash a ROM/firmware via Odin chances are very good that you will be getting a new bootloader and all the KNOX garbage it brings.
TLR
If you flash via recovery you won't get KNOX, if you flash via Odin you probably will.
Modems must also be flashed in Odin, but as far as KNOX goes, it's the bootloader you don't want.

Okay, does this mean I have knox or do not have knox.

Jamessr79 said:
Okay, does this mean I have knox or do not have knox.
Click to expand...
Click to collapse
It seems to me like you're still knox-free
tetakpatalked from Nexus 7 flo

Jamessr79 said:
Okay, does this mean I have knox or do not have knox.
Click to expand...
Click to collapse
Yup.
No Knox there.
You would see a Knox warranty line in that bootloader screen if you had it.

Cool, so it worked.

question
lordcheeto03 said:
Just something to remember: Bootloaders (all the bad KNOX junk) CANNOT be flashed via custom recovery. So if you are flashing a stock ROM (firmware?) via custom recovery you will NOT get KNOX. If, however you decide to flash a ROM/firmware via Odin chances are very good that you will be getting a new bootloader and all the KNOX garbage it brings.
TLR
If you flash via recovery you won't get KNOX, if you flash via Odin you probably will.
Modems must also be flashed in Odin, but as far as KNOX goes, it's the bootloader you don't want.
Click to expand...
Click to collapse
So what you are saying is if I flash a stock zip via custom recover no KNOX? Has this been tested? I removed knox on 4.3 but got crazy and tried 4.4.4 now random restarts.

Jamessr79 said:
So what you are saying is if I flash a stock zip via custom recover no KNOX? Has this been tested? I removed knox on 4.3 but got crazy and tried 4.4.4 now random restarts.
Click to expand...
Click to collapse
Yes, what I'm saying has been tested and confirmed 100%. There is no way to flash a KNOX-implemented bootloader (or ANY bootloader for that matter) via custom recovery. You seem to have the misconception that the KNOX apps within the ROM is what all the KNOX talk is about. If anything, it's only a small part. Now, I'm not absolutely certain of how this works as I've only followed the technical posts in the Development only forum regarding this for the first 10 or so pages, so if I say something that isn't exactly accurate, please forgive me. The basic gist is that when you hear about KNOX and why it's not necessarily wanted in the updated firmwares isn't because of a few user-removable apps; it's something at the hardware level that, when during the boot up tests and checks, it notices that there is a custom kernel or custom recovery in place instead of the expected stock kernel/recovery, it blows an e-fuse and forever after tells anyone who looks at the download mode that the device has been modified at one point or another.
About the random restarts, without knowing whether you updated from 4.3 to 4.4.4 via custom recovery or other official means, all I can say is to try a factory reset and/or use Odin to re-flash the firmware and do a factory reset after that.

lordcheeto03 said:
Yes, what I'm saying has been tested and confirmed 100%. There is no way to flash a KNOX-implemented bootloader (or ANY bootloader for that matter) via custom recovery. You seem to have the misconception that the KNOX apps within the ROM is what all the KNOX talk is about. If anything, it's only a small part. Now, I'm not absolutely certain of how this works as I've only followed the technical posts in the Development only forum regarding this for the first 10 or so pages, so if I say something that isn't exactly accurate, please forgive me. The basic gist is that when you hear about KNOX and why it's not necessarily wanted in the updated firmwares isn't because of a few user-removable apps; it's something at the hardware level that, when during the boot up tests and checks, it notices that there is a custom kernel or custom recovery in place instead of the expected stock kernel/recovery, it blows an e-fuse and forever after tells anyone who looks at the download mode that the device has been modified at one point or another.
About the random restarts, without knowing whether you updated from 4.3 to 4.4.4 via custom recovery or other official means, all I can say is to try a factory reset and/or use Odin to re-flash the firmware and do a factory reset after that.
Click to expand...
Click to collapse
Okay, I misunderstood on what you said could be flashed, but will have to take a look. Could you please point me in the right direction for that forum. As far as the misconception goes I do know that KNOX is in the bootloader. I also know that KNOX app/software is found in the rom as well. As for KNOX being in the rom Titanium Backup helps to remove most of it. Or I can just installing a custom rom that has it removed. The main reason that I had started this forum was to remove the KNOX from the bootloader. The reason I pointed to http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html in the first post is because they stated it could be done. After doing some other looking around and talking to others I tried it. Seems like it works on android 4.3, but 4.4.2 and 4.4.4. when I try to do the same it is not happy. I updated via Odin. The first time was 4.2 to 4.3 after modding the bootloader and not the rom. It works fine no KNOX lines in download mode. Still KNOX in the rom but uninstalled using Titanium Backup. Currently I am running android 4.3 on my Galaxy S4 no issues and as far as I can tell no KNOX.

Jamessr79 said:
Okay, I misunderstood on what you said could be flashed, but will have to take a look. Could you please point me in the right direction for that forum. As far as the misconception goes I do know that KNOX is in the bootloader. I also know that KNOX app/software is found in the rom as well. As for KNOX being in the rom Titanium Backup helps to remove most of it. Or I can just installing a custom rom that has it removed. The main reason that I had started this forum was to remove the KNOX from the bootloader. The reason I pointed to http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html in the first post is because they stated it could be done. After doing some other looking around and talking to others I tried it. Seems like it works on android 4.3, but 4.4.2 and 4.4.4. when I try to do the same it is not happy. I updated via Odin. The first time was 4.2 to 4.3 after modding the bootloader and not the rom. It works fine no KNOX lines in download mode. Still KNOX in the rom but uninstalled using Titanium Backup. Currently I am running android 4.3 on my Galaxy S4 no issues and as far as I can tell no KNOX.
Click to expand...
Click to collapse
Wait.... your on 4.3 or 4.2 and have been able to unlock the bootloader on them?? Everything you said above is exactly what I have seen and heard also with the addition that the signatures not matching verification checks are what is blowing the q fuse or what Knox and the Samsung / att security freak out about right?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app

I was on 4.2 and downloaded the stock 4.3 to my Linux pc. I then did what was stated on the s4 mini forums and was able to remove Knox from the bootloader, then the rom via titanium backup. Note as far as I know you can't remove Knox once it is already there.

[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