My wife's S3 got the OTA before I had heard of the Knox problem.
Her phone has some major issues after the update & I am trying to find a way to fix it.
I flashed the MK3 all in one ordered Rom posted by Thunder Stick on my S3 & it seems great so far.
My question is: since she already has Knox on her phone, can I put CWM or PhilZ on her's so I can flash the same rom I put on my phone, or will this cause Knox issues? I'm not worried about the warranty counter, just worried about bricking it.
Any input is welcomed.
Thanks y'all
monke30butt said:
My wife's S3 got the OTA before I had heard of the Knox problem.
Her phone has some major issues after the update & I am trying to find a way to fix it.
I flashed the MK3 all in one ordered Rom posted by Thunder Stick on my S3 & it seems great so far.
My question is: since she already has Knox on her phone, can I put CWM or PhilZ on her's so I can flash the same rom I put on my phone, or will this cause Knox issues? I'm not worried about the warranty counter, just worried about bricking it.
Any input is welcomed.
Thanks y'all
Click to expand...
Click to collapse
As long as you don't downgrade the bootloader, Read whole 1st POST HERE
joeyhdownsouth said:
As long as you don't downgrade the bootloader, Read whole 1st POST HERE
Click to expand...
Click to collapse
I have read that a few times already. I think what I am unclear on is about the difference between the boot loader & recovery. I was thinking that CWM would replace the boot loader & that is what I was worried about. So, if I have it straight now, the CWM & flashable Rom of MK3 will not replace the boot loader? You need a tar to do the bootloader? So will it matter if the rom has had Knox taken out or should I look for one with knox? I was hoping to use the All In One Rom, but it has no Knox.
Sorry to be a pest guys
monke30butt said:
I have read that a few times already. I think what I am unclear on is about the difference between the boot loader & recovery. I was thinking that CWM would replace the boot loader & that is what I was worried about. So, if I have it straight now, the CWM & flashable Rom of MK3 will not replace the boot loader? You need a tar to do the bootloader? So will it matter if the rom has had Knox taken out or should I look for one with knox? I was hoping to use the All In One Rom, but it has no Knox.
Sorry to be a pest guys
Click to expand...
Click to collapse
CWM will replace the stock Android recovery. Yes, a tar file can downgrade the bootloader. you can flash any ROM as long you do not downgrade the bootloader.
Thanks Joey
Related
Okay, well I'm really starting to dislike this crap.
I replaced the board in my girlfriend s3, and it had 4.3 OTA on it -.-.
Now to my understanding, the OTA update comes with knox in the bootloader.This keeps anyone from flashing custom roms/recoveries.
I've followed all the guides and such. I dont care about 4.3. I just want knox completely removed, and revert it back to 4.1.2. I know that there is bootloaders floating around out there, that should overwrite the knox bootloader, and then flash a stock 4.1.2 rom. Now in theory that should work, but my googling skills have gone down the drain. I can't find any bootloader files, There has to be a way around this, its been over a month now. I honestly don't ever want to upgrade to 4.3. I'm happy with jellybean. It's stable, and smooth.
Just want to pick all your guys' brains xD.
Johnnysauur said:
Okay, well I'm really starting to dislike this crap.
I replaced the board in my girlfriend s3, and it had 4.3 OTA on it -.-.
Now to my understanding, the OTA update comes with knox in the bootloader.This keeps anyone from flashing custom roms/recoveries.
I've followed all the guides and such. I dont care about 4.3. I just want knox completely removed, and revert it back to 4.1.2. I know that there is bootloaders floating around out there, that should overwrite the knox bootloader, and then flash a stock 4.1.2 rom. Now in theory that should work, but my googling skills have gone down the drain. I can't find any bootloader files, There has to be a way around this, its been over a month now. I honestly don't ever want to upgrade to 4.3. I'm happy with jellybean. It's stable, and smooth.
Just want to pick all your guys' brains xD.
Click to expand...
Click to collapse
You should read THIS. It explains everything. You can't overwrite KNOX or downgrade boot loader or you will brick, but you can still root and have custom recovery, then flash a ROM of your choice. Downgrading includes flashing TAR files in ODIN and downgrading mk3 to md4 or lower via zip files.
sent from my GS3
Is there anything different you need to do for custom recovery on 4.3
Sent from my SPH-L710 using xda app-developers app
Johnnysauur said:
Is there anything different you need to do for custom recovery on 4.3
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I believe anything after md4 won't mount storage. Check THIS thread. I flashed the TWRP Tar in ODIN on a Boost GS3 that wouldn't mount storage.
sent from my GS3
joeyhdownsouth said:
You should read THIS. It explains everything. You can't overwrite KNOX or downgrade boot loader or you will brick, but you can still root and have custom recovery, then flash a ROM of your choice. Downgrading includes flashing TAR files in ODIN and downgrading mk3 to md4 or lower via zip files.
sent from my GS3
Click to expand...
Click to collapse
I thought you couldn't root if 4.3 was applied with ota
Sent from my SPH-L710 using xda app-developers app
Johnnysauur said:
Okay, well I'm really starting to dislike this crap.
I replaced the board in my girlfriend s3, and it had 4.3 OTA on it -.-.
Now to my understanding, the OTA update comes with knox in the bootloader.This keeps anyone from flashing custom roms/recoveries.
I've followed all the guides and such. I dont care about 4.3. I just want knox completely removed, and revert it back to 4.1.2. I know that there is bootloaders floating around out there, that should overwrite the knox bootloader, and then flash a stock 4.1.2 rom. Now in theory that should work, but my googling skills have gone down the drain. I can't find any bootloader files, There has to be a way around this, its been over a month now. I honestly don't ever want to upgrade to 4.3. I'm happy with jellybean. It's stable, and smooth.
Just want to pick all your guys' brains xD.
Click to expand...
Click to collapse
At this time, the only way to get Knox out of the bootloader is to write over it with an unknoxed bootloader that's signed by Samsung, and passes the version check by the current bootloader.
Knoxed bootloaders will reject previous bootloader versions, even if those are properly signed.
However, loading a current version bootloader (properly signed) without knox to replace the knoxed one should then allow you to revert back to a previous version.
The only way this wouldn't work is if the knoxed bootloader killed a q-fuse somewhere, but no one has found proof to this.
andyistic said:
At this time, the only way to get Knox out of the bootloader is to write over it with an unknoxed bootloader that's signed by Samsung, and passes the version check by the current bootloader.
Knoxed bootloaders will reject previous bootloader versions, even if those are properly signed.
However, loading a current version bootloader (properly signed) without knox to replace the knoxed one should then allow you to revert back to a previous version.
The only way this wouldn't work is if the knoxed bootloader killed a q-fuse somewhere, but no one has found proof to this.
Click to expand...
Click to collapse
Correction: nobody has positively verified the existence of an eFuse, to my knowledge, just yet. But there is a substantial amount of evidence to suggest its existence. If you try to revert from KNOX to a previous bootloader version, it has a pretty consistent knack for hard-bricking the devices so they won't even power to the download or recovery consoles. From what I've read, people have had similar experiences when attempting to run older versions of TriangleAway to zero out their flash counts. Additionally, every attempt that has been made to revert the KNOX Warranty Void flag that I've read about has resulted in a hard-brick as well.
It's also important to note: At this time, when people say they've removed KNOX what they're really talking about are the apps that came in the 4.3 update. Removing these does not have any impact on the bootloader's status. There is currently no way to remove the KNOX bootloader without irrevocably crippling your device.
I rooted my friends S3 ATT with the s3 toolkit v7.0 he now wants me to unroot it so he can take the 4.3 update it have run the unroot and remove zip multiple times ( I even re rooted it and tried removing it again) and it will not remove clockwork mod recovery even though it says it will, it has successfully unrooted it the phone and removed super user and busy box . he does not want to loose all the data on his phone is there another way to remove clock work mod and get him back to the stock recovery so he can take the 4.3 update with out using triangle away ?
thanks
You would need to flash the stock recovery to replace CWM.
audit13 said:
You would need to flash the stock recovery to replace CWM.
Click to expand...
Click to collapse
where do I acquire a stock recovery and is it flashed through oden or through clockwork ?
thanks
I'm not sure where to find the stock recovery as I have never seen one that is flashable via Odin, CWM, or TWRP.
By updating to stock 4.3, the phone will have a bootloader that cannot be downgraded and Knox will be installed.
I personally avoided the 4.3 update because the 4.3 bootloader makes it tough to go back to stock and tripping the knox counter will void the warranty. Also, knox can interfere with root access.
audit13 said:
I'm not sure where to find the stock recovery as I have never seen one that is flashable via Odin, CWM, or TWRP.
By updating to stock 4.3, the phone will have a bootloader that cannot be downgraded and Knox will be installed.
I personally avoided the 4.3 update because the 4.3 bootloader makes it tough to go back to stock and tripping the knox counter will void the warranty. Also, knox can interfere with root access.
Click to expand...
Click to collapse
actually I'm a blind idiot it is an option right in the tool kit i have just reflashed it and all is good
THANK YOU VERY MUCH I could not have fixed this with out your help
(he never used any custom roms and does not mind that his unit will be locked )
iiipm said:
actually I'm a blind idiot it is an option right in the tool kit i have just reflashed it and all is good
THANK YOU VERY MUCH I could not have fixed this with out your help
(he never used any custom roms and does not mind that his unit will be locked )
Click to expand...
Click to collapse
Hey, thanks for the post. I learned something too:good:
So i have some questions about knox. I'm new to it and sadly had the 4.3 bootloader thrust upon me.
1. Is there a way to remove it/return to a different bootloader? Not just hide it like Billards thing does
2. One way I restore my phone if it freaks out is to run a 1 click stock rooted ljc program. I was reading in a Verizon forum flashing a stock version will brick my phone does this apply for sprint? They said mk3 not mk4
3.if I no longer can use that and need to fix say a soft Brick with no recovery what should I use/do
4. What are the main things i need to be aware or with knox?
I've been reading around and all I'm finding is its security. I know that it's bootloader related but every time I odin a tar file I didn't know that affected a the bootloader. This knox cap has me not even wanting to touch my phone.
Any help would be appreciated and you will get your thanks
Anyone?
I thought all this to but I took the plunge to root and did so with kingo root it went flawless and upon boring l booting just open super su and it will ask you if you want to disable knox just click Yea and you're done and to flash roms flash philz touch recovery with odin and make sure to make a backup is stock and flash away
Sent from my SPH-L900 using xda app-developers app
I have a S4 - with 4.4.2 stock . Sadily ever since the update I had nothing but issues. Getting my 2nd replacement tomorrow to try and resolve this issue where the cell radio locks up and I have no connectivity .
At this point I am ready just say screw the warranty but I dont know what I can do as there so many threads it is very confusing.
Note at this point i dont care about tripping the efuse.
From what I have read is that I can root the phone. But where I am confused at is if I can load custom bootloader /roms I had a moto cliq2 with a locked boot loader that then eventually loaded a 2nd boot loader and then the rom.
Really if anyone can clear up where i stand on getting one of the 4.4.4 aosp roms on the phone I be greatly appreciated.
Bootloader is not locked on this device, so just flash custom recovery with Odin and flash your ROM
+1 serio... If you're not on the evil bastard vzw service, then:root, intstall custom recovery and flash what you want!! You're lucky enough to have a device that hasn't had its n-ts cut off!! I have sprint as a carrier, so I'm in the same boat as you, but I've been collecting phones from all carriers for a while now and since vzw has such a monopoly on the us, I've racked up about 9 vzw phones with locked bootloaders. You're actually quite in luck man. Root, install recovery, ROM, profit!
youdoofus said:
+1 serio... If you're not on the evil bastard vzw service, then:root, intstall custom recovery and flash what you want!! You're lucky enough to have a device that hasn't had its n-ts cut off!! I have sprint as a carrier, so I'm in the same boat as you, but I've been collecting phones from all carriers for a while now and since vzw has such a monopoly on the us, I've racked up about 9 vzw phones with locked bootloaders. You're actually quite in luck man. Root, install recovery, ROM, profit!
Click to expand...
Click to collapse
Actually no root is needed. Just flash recovery with Odin and flash ROM
Fair point, as recovery supercedes root since its not within the os, but whats the fun of romming without rooting?
Sent from my SM-G900P using XDA Free mobile app
youdoofus said:
Fair point, as recovery supercedes root since its not within the os, but whats the fun of romming without rooting?
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
All custom ROMs come pre-rooted. So no reason to root the stock ROM, if all you will be doing is flashing a custom ROM. Just eliminates a step.
Rob
rlichtefeld said:
All custom ROMs come pre-rooted. So no reason to root the stock ROM, if all you will be doing is flashing a custom ROM. Just eliminates a step.
Rob
Click to expand...
Click to collapse
Many people think you have to be rooted to flash a custom recovery, I think this is why they said that
serio22 said:
Actually no root is needed. Just flash recovery with Odin and flash ROM
Click to expand...
Click to collapse
Ok so knox does not lock the boot loader just acts as a trigger for the annoying efuse.
Question still comes down to if I root install recovery and then flash or flash with oldin and not deal with the boot loader. I just got my 2nd replacement another one with 4.4.2 I give it a few days if it does not act up great if it does I just going to flash it .
As the current stock 4.4.2 has caused nothing but connectivity issues for me.
jawa78 said:
Ok so knox does not lock the boot loader just acts as a trigger for the annoying efuse.
Question still comes down to if I root install recovery and then flash or flash with oldin and not deal with the boot loader. I just got my 2nd replacement another one with 4.4.2 I give it a few days if it does not act up great if it does I just going to flash it .
As the current stock 4.4.2 has caused nothing but connectivity issues for me.
Click to expand...
Click to collapse
Just forget the bootloader it is not locked, and no root is needed to flash recovery. Just flash custom recovery of your choice with Odin, reboot straight into recovery RIGHT after, and flash ROM
Edit: and yes pretty much the only thing that will happen is that your counter will be tripped
Just thought of something while flashing a new ROM on my nexus 7 flo. If all custom ROMs are rooted, why then is it then that when you flash some ROMs, root can break? I flashed a different ROM on the n7 and lost root until I went back and reran the exploit
Sent from my SM-G900P using XDA Free mobile app
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.