Related
I have a T-Mobile Samsung Galaxy S4 on stock 4.3 MK2 and I was wondering if there is a way to restore the MDL bootloader so I can flash ROM's and get my warranty back if I need to. Thanks for the help
re: downgrading
r0b458 said:
I have a T-Mobile Samsung Galaxy S4 on stock 4.3 MK2 and I was wondering if there is a way to restore the MDL bootloader so I can flash ROM's and get my warranty back if I need to. Thanks for the help
Click to expand...
Click to collapse
That cannot be done. Once you have upgraded to 4.3 MK2 you cannot downgrade.
But there are plenty of excellent custom roms which are 4.3 MK2 that you can flash.
NOTE: if you have flashed the official Tmobile MK2 4.3 Odin flash firmware/rom OR if you
have allowed the OTA update and or if you upgrading using KIES and your phone is not yet
rooted and does not have any custom recovery or custom rom in it then you don't need to worry
about your warranty, it will stay GOOD as long as you do not ROOT the phone and as long as
you do not flash any custom recoveries or kernels.
Good luck!
Misterjunky said:
That cannot be done. Once you have upgraded to 4.3 MK2 you cannot downgrade.
But there are plenty of excellent custom roms which are 4.3 MK2 that you can flash.
NOTE: if you have flashed the official Tmobile MK2 4.3 Odin flash firmware/rom OR if you
have allowed the OTA update and or if you upgrading using KIES and your phone is not yet
rooted and does not have any custom recovery or custom rom in it then you don't need to worry
about your warranty, it will stay GOOD as long as you do not ROOT the phone and as long as
you do not flash any custom recoveries or kernels.
Good luck!
Click to expand...
Click to collapse
Aw well I guess I'll just take my chances because I used to flash ROM'S all the time but recently I made the mistake of trying out stock 4.3 and it's actually pretty nice it's just I miss flashing lol. I'm not even sure if I actually have a valid warranty anyways haha but thanks
Misterjunky said:
That cannot be done YET. Once you have upgraded to 4.3 MK2 you cannot downgrade.
But there are plenty of excellent custom roms which are 4.3 MK2 that you can flash.
NOTE: if you have flashed the official Tmobile MK2 4.3 Odin flash firmware/rom OR if you
have allowed the OTA update and or if you upgrading using KIES and your phone is not yet
rooted and does not have any custom recovery or custom rom in it then you don't need to worry
about your warranty, it will stay GOOD as long as you do not ROOT the phone and as long as
you do not flash any custom recoveries or kernels.
Good luck!
Click to expand...
Click to collapse
Hi there Mr. Junky,
You forgot the most important word, in red above. Our Developers are like I was when I was in my younger days of programming, If was said something couldn't be done, I worked till I made it happen and Rooting is a good example of how our XDA "Gurus" have made things happen, and I am confident they will again rise above the rest and do the "Cannot be done" and share it with this community.....
Aloha, and Have a great day! p.s. Thank you for all your useful and clear posts that a LOT of users have benefited from!
I was doing some reading last night through the R&D thread and other various threads linked to through that one... I do believe that someone has been able to revert back to 4.2.2; but it involves some pretty risky methods and equipment which nobody in this thread likely has.
bobolinko said:
Hi there Mr. Junky,
You forgot the most important word, in red above. Our Developers are like I was when I was in my younger days of programming, If was said something couldn't be done, I worked till I made it happen and Rooting is a good example of how our XDA "Gurus" have made things happen, and I am confident they will again rise above the rest and do the "Cannot be done" and share it with this community.....
Aloha, and Have a great day! p.s. Thank you for all your useful and clear posts that a LOT of users have benefited from!
Click to expand...
Click to collapse
You are absolutely right, I did forget the magic work "YET".
But I think this time by the time the devs finally find a way to fully over-come the knox issue
in our S4's we all will have a much newer model, perhaps a Samsung Galaxy S5 or S6 or? LOL
In an attempt keep thread questions down to a minimum and let it be used for development specific questions. I ask that you post general update questions here. I will keep this updated as best I can.
1. Q: How do I update to official T-Mobile release?
A: You can go back to stock and accept the OTA. Or you can download the Update.zip HERE . There are other links from Tesh and Allenjthomsen on their individual threads. (thanks Allen for the update.zip and Dirtybudha for the ftp server)
2. Q: Should I flash the update so I can have the new bootloader?
A: At this time we are waiting for the release of more custom kernels and there are 2 recoveries that will work with the new bootloader
3. Q: Can I go back to 4.3 once I flash?
A: If you flash the new bootloader, you will not be able to odin back to use 4.3 roms. But you can custom flash 4.3 with new Mi7 bootloader and kernels made for that purpose.
4. Q: If I update my N3 will I still have root?
A: At this time, you can gain root using CF-Auto root, but you will lose custom recovery
5. Q: Will flashing the update trip Knox if I originally rooted using De-La Vega?
A: No, flashing the update will simply update your phone to 4.4.2. But trying to flash a custom recovery will trip Knox to 0x1. kingoapp.com does not work as per a user that tried it
6. Q: Can I load TMO Kit Kat without updating bootloader?
A: Yes. You can flash any rom.zip from the dev thread using custom 4.3 Kit Kat Kernels that allow 4.4.2 to run off the 4.3 bootloader.
7. Q: Are there any TMO Kit Kat kernels already in circulation?
A: . Yes. Check the Original Android Development thread.
8. Q: I tried flashing the new posted Odexed and Deodexed roms but get stuck at boot. What's wrong?
A: The new boot.img (Kernel) included in these roms are based off the Kit Kat kernel release. They will not work on the 4.3(Jellybean MI7) bootloader unless you usea custom kernel
9. Q: After I update to official release, how do I get root back?
A: You will need to ODIN CF-Autoroot once you have updated. WARNING: YOU WILL TRIP KNOX USING CF-AUTOROOT
10. Q: Has anyone found a custom recovery that works with the NB4 Bootloader?
A: Yes, it has been noted that Philz recovery and the N9005 TWRP is being tested as per BigBiff's recommendation and is noted as working.
11. Q: Can I flash just the bootloader and the modem?
A: Yes, but you will have compatibilty issues unless you flash one of the two Kit Kat compatible recoveries.
12. Q: I Odined the NB4 file and my phone just sits at black screen with blue recovery on it. Did I do something wrong?
A: NO, there seems to be a glitch in the Odin process. Reboot your phone into download mode and re-Odin the file and it will complete successfully.
13 Q: I have read that there is a way to root Kit Kat without tripping Knox. Is this true?
A: Yes, there is a process that can be used but is not recommended as you can brick your phone and my not be able to recover from the brick.
Kit Kat Kernels :
Wootevers Kernel (TMO Original Android Development thread)
Civato's Kernel (N9005 Original Android Development Thread)
ColonelX R13 (CURRENTLY BEING BUILT AND TESTED)
If anybody see's a Frequently asked question i'm missing. please let me know. Trying to keep up with all 4 threads.
Thanks
If you use the official update, you will get the extSDCard read/write errors back, as they are part of Kit Kat .
to fix, once rooted on the official rom, Open the platform.xml file just like in the custom Kit Kat roms and make it look like this
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE">
<group gid="sdcard_r"/>
<group gid="sdcard_rw"/>
<group gid="media_rw"/>
</permission>
That "SHOULD" fix the read/write problems. Kit Kat is made to only read and write to the internal storage to keep Android running smoothly as people sometimes by cheap laggy sdcards.
dragonstalker said:
If anybody see's a Frequently asked question i'm missing. please let me know. Trying to keep up with all 4 threads.
Thanks
Click to expand...
Click to collapse
I think the big one is people looking for clarification on whether the bootloader is locked or not.
I see a lot of conflicting posts. Mainly from those who don't understand kernel dependencies as they pertain to the boot process.
rjohnstone said:
I think the big one is people looking for clarification on whether the bootloader is locked or not.
I see a lot of conflicting posts. Mainly from those who don't understand kernel dependencies as they pertain to the boot process.
Click to expand...
Click to collapse
That we cannot confirm until Biff gets home and has had a chance to compile a kernel specifically for this bootloader.
Has anyone tried the TWP recovery for the international device? I did the over the air update and am rooted but would like to get the recovery installed. Any ideas?
jimmydigital00 said:
Has anyone tried the TWP recovery for the international device? I did the over the air update and am rooted but would like to get the recovery installed. Any ideas?
Click to expand...
Click to collapse
BigBiff has suggested in one of Ax's threads to try that recovery. If it works for you. please post back so we can get the word out. Right now Philz CWM is confirmed working
tried downloading but asking for username and password...what am i doing wroing...any help is appreciated...thanks,
Will kingo root method work?
Sent from my SM-N900T using XDA Premium 4 mobile app
so dragon i will be able to flash my phone with tar file from SamMobile flashing the phone stock and with 4.4.2 bootloader then being able to root the phone and being able to flash Philz CWM to get custom recovery?
dragonstalker said:
BigBiff has suggested in one of Ax's threads to try that recovery. If it works for you. please post back so we can get the word out. Right now Philz CWM is confirmed working
Click to expand...
Click to collapse
I can confirm that the recovery located here works
http://forum.xda-developers.com/showthread.php?t=2671039&page=5
rockinandroid said:
tried downloading but asking for username and password...what am i doing wroing...any help is appreciated...thanks,
Click to expand...
Click to collapse
changed download server. try now.
blacklabel2020 said:
so dragon i will be able to flash my phone with tar file from SamMobile flashing the phone stock and with 4.4.2 bootloader then being able to root the phone and being able to flash Philz CWM to get custom recovery?
Click to expand...
Click to collapse
if you know how to use the tar file yes. Everything else you are spot on.
Although I've seen some ask this question, I would like some clarification as there is still some conflicting info being spread throughout 4 or 5 threads
From what I gather:
The new 4.4 bootloader now has custom recovery through use of either the TWRP biff posted or the new PhilZ. Both confirmed working.
My question is, does this affect us now being able to custom flash 4.3 roms without having to Odin back to 4.3 just to flash 4.3 roms...if that even is something that is 100% true that we can do since some people say yes we can odin back to 4.3 and some say no.
And with the new bootloader, we should theoretically be able to flash all of the custom 4.4 N9005 ROMs just fine?
dragonstalker said:
changed download server. try now.
Click to expand...
Click to collapse
same thing..asking for username and passwordl
_INSPIREed said:
Although I've seen some ask this question, I would like some clarification as there is still some conflicting info being spread throughout 4 or 5 threads
From what I gather:
The new 4.4 bootloader now has custom recovery through use of either the TWRP biff posted or the new PhilZ. Both confirmed working.
My question is, does this affect us now being able to custom flash 4.3 roms without having to Odin back to 4.3 just to flash 4.3 roms...if that even is something that is 100% true that we can do since some people say yes we can odin back to 4.3 and some say no.
And with the new bootloader, we should theoretically be able to flash all of the custom 4.4 N9005 ROMs just fine?
Click to expand...
Click to collapse
Sorry. No, you cannot flash 4.3 roms via custom recovery once you use the new bootloader. But, yes technically you should be able flash Int. Roms now.
A lot of people are desperate. Chill, wait 2, 3 days everything should be gooood it's only been a day
Sent from my SM-N900T using Tapatalk
chuko303 said:
A lot of people are desperate. Chill, wait 2, 3 days everything should be gooood it's only been a day
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I know, It's not like your phones will stop working unless you update to KitKat today.
beowolf said:
I know, It's not like your phones will stop working unless you update to KitKat today.
Click to expand...
Click to collapse
I'm personally going to wait for evil to release Wicked kit kat! Pumped for that one
Sent from my SM-N900T using Tapatalk
This thread contains information about the KitKat 4.4.2 update to the T999 variants of the Samsung Galaxy S3. Here you will be able to find information on updating, rooting, installing custom recoveries and roms, as well as how to return to stock should you feel the need to. If you feel you need additional help or would like further clarification on a subject just leave a reply in this thread and myself or someone familiar with the matter will do our best to answer and provide promptly help. This is a work in progress since KitKat is new to our devices. As we learn more, additional info and links will be posted. Huge thanks to DocHoliday77 for giving me ideas and helping me make things clearer!
Below I tried to put together a list of questions regarding KitKat in hopes to alleviate confusion and educate others.
F.A.Q.
[Q] Can I just flash the KitKat modem on my older firmware to see if my signal will improve?
WARNING! WARNING!
A) I feel like this is probably the most important thing to know about the KitKat update as of now. DO NOT I repeat DO NOT flash any 4.4.2 modems if you have not taken the official 4.4.2 update for your device via OTA or Odin. If you do, you will brick your device and you will not be able to unbrick it. The current debrick method does not work! Also please do not try to downgrade your bootloader, any such attempt can also brick your device.
YOU HAVE BEEN WARNED!!
Click to expand...
Click to collapse
[Q] My signal has been terrible with KitKat, how can I downgrade my modem to see if I will get a better signal?
A) You cannot use older modems with 4.4.2. You will have no service.
Click to expand...
Click to collapse
[Q] Will KitKat give me Knox?
A) Unsurprisingly, Knox is present in 4.4.2 as it was in 4.3. For more info on Knox, scroll down to the second post.
Click to expand...
Click to collapse
[Q] Is it possible to root my device without tripping the Knox/warranty bit counter, and how can I make sure it stays untripped?
A) Yes, it is possible to root and keep your counter untripped. Scroll down to "How to root" and you will find your answer. To keep the counter at 0, avoid flashing custom recoveries and kernels.
Click to expand...
Click to collapse
[Q] I have tripped my Knox/warranty bit counter, how can I reset it?
A) There is currently no way to reset this counter.
Click to expand...
Click to collapse
[Q] Can I still flash a custom recovery with KitKat firmware?
A) Yes. Please scroll to the end of this post for more info and recommendations.
Click to expand...
Click to collapse
[Q] I am in developer options and I cannot find the option to change my runtime to ART, how can I change it? I'm confused.
A) ART runtime cannot be chosen as default because the option is disabled by Samsung in all of their KitKat firmwares. The default will be Dalvik.
Click to expand...
Click to collapse
If your device has not yet received the KitKat update, please be patient and wait for your carrier to update. If you feel you cannot wait for an official update, there is the option to update unofficially by flashing a custom Rom, just remember that they will be taken from other device's firmware so it may not work the same with your device or it have missing features native to yours. For more information and what you need to update unofficially, check method 3 below on "How to update or return to stock."
General F.A.Q.s
[Q] What Rom's can I safely flash?
A) Any Rom and kernel in this section of the fourms should be okay. Roms labeled for d2lte will work for any d2 device, and T999 Roms will work on T999V & T999N for example.
BUT....some ROM's will not flash without a little intervention, so to speak. If you get a Status 7 error and the ROM will not flash, this is what you do:
Unzip the Rom.
In the Meta-Inf folder, delete the signatures (CERT.RSA, CERT.SF, MANIFEST.MF)
Browse to META-INF\com\google\android\ and open the updater-script in Notepad++
At the top of the script, there will be one or several lines beginning with "Assert". Delete these Lines. Save the updater-script.
Re-Zip the Rom and try again to flash.
Click to expand...
Click to collapse
[Q] Why is my WiFi and/or Bluetooth not working after flashing a T999 based Rom?
A) Most likely this is due to a kernel/module mismatch. Try flashing a custom kernel or a stock modified kernel to fix this.
Click to expand...
Click to collapse
[Q] Why does my phone say it is a T999 or other model?
Because you flashed a rom that was based on or intended for the original T999 model. This is perfectly normal.
If you really want to change it, go to /system/build.prop and edit all lines that say SGH-T999, to your model or whatever you like.
(WARNING!!!) If you change this to a different model than the T999 or T999L, some apps may think they are on that different model device. This can cause a brick if you try to flash firmware with Mobile Odin. Other apps may not function as intended. Use Caution!
Click to expand...
Click to collapse
How to update or return to stock:
Method 1:
The simplest method. If you are on official and unrooted stock firmware, you can simply check for update to your device by going into settings, more, about device, software update. This option is if you do not want root access or plan to root at another time.
Click to expand...
Click to collapse
Method 2:
You can use this method to update your device or return it to its factory state, should you need to. Simply download the stock firmware linked below and flash it with Odin. Just remember, you cannot downgrade your device once you have updated to 4.3 or higher firmware. You can, however, flash an equal or higher version. For example, you updated your device to 4.3 MJC firmware, you can only flash 4.3 MJC, 4.3 NC2, or 4.4.2. If on NC2 firmware you cannot downgrade to MJC even though it is 4.3 because it is a lower firmware. If you flashed 4.4.2, you can only flash 4.4.2. Follow the link below and scroll past the words "root66" where you will see "Official Firmware." Detailed instructions on how to use and flash firmware with Odin will also be found there. Thanks to my good friend @DocHoliday77 for the thread and mrRobinson for the firmwares!
Stock Firmware:
Download
Click to expand...
Click to collapse
Method 3:
You can flash a custom Rom with your custom recovery, but you will need at least a 4.3 bootloader and modem. Bootloader update is required otherwise your device will not boot, modem is needed for data. If you decide to go this route and are on 4.3 bootloader and modem do not upgrade them under any circumstance unless you want a brick and headaches! I will link stock Roms here overtime, meanwhile search for one you like in the development section Click to go to Development Section
Stock NB8 4.4.2 port from Sprint. Daily driver stable! Thanks Doc!
Download Sprint port here
Click to expand...
Click to collapse
How to root:
Method 1:
If you are looking to update your device and be rooted out of the box, check out the pre-rooted root66 firmware thread by @DocHoliday77. Just find the 4.4.2 firmware for your device, download it, and flash with Odin. Detailed instructions on how to use and flash with Odin can also be found in the link below. Make sure you click the box below the words "root66." Knox counter should remain untripped, but it is unconfirmed as of now. If you want to be safer about your counter staying untripped, continue to method 2.
Download root66
Click to expand...
Click to collapse
Method 2:
Use TowelRoot by the legendary geohot. This method is very simple and useful if you have already updated to 4.4.2 and want root access nice and easy. Confirmed to keep your Knox counter untripped!
Download TowelRoot
Click to expand...
Click to collapse
How to install a custom recovery:
Remember, any and ALL methods to flash custom recovery will trip Knox/warranty counter. After installing a custom recovery you will be able to flash custom ROMs, scripts, and mods!
Method 1:
Download your recovery tar file and flash it with Odin in download mode.
Instructions:
Flash File In ODIN
- Power down your device
- Simultaneously press and hold VOL DOWN + HOME BUTTON + POWER BUTTON
- At *Warning* screen, press VOL UP
- Connect your device to its USB cable and plug cable into PC
- Start ODIN on PC
- Verify that "Auto Reboot" and "F. Reset Time" are UNCHECKED
- Click PDA button ("AP" in newer versions)
- Browse PC and select your tar file
- WAIT for "START" button to be enabled (may take a minute)
- Click START button to begin recovery install
- Disconnect USB only when download is finished and you see the message "PASS!" in a green box.
- Remove battery and reboot straight to recovery, very important!
- Now you can either flash whatever you want, or reboot back into system.
Instructions were taking from a thread by az_biker and edited for our device
Click to expand...
Click to collapse
Method 2:
Use an app from the playstore to flash custom recovery like goomanager, ROM Manager, or my favorite, flashify! These method is useful if you have root access on your device, would prefer avoid using Odin, or do not have access to a computer to use Odin.
Click to expand...
Click to collapse
Information about Knox
Knox allows people to use their device on a secure business (work) network. It allows the data which belongs to the business to be encrypted per DoD standards. Once the Knox/warranty bit is tripped, you can no longer use this service because it proves the device has been tampered with. You can imagine how much simpler it would be to manipulate this service without the restrictions Samsung had to enforce in order to protect sensitive data. This is the main reason I believe the Knox bootloader was added and why root access, once gained, is still limited in some cases. There is also claims that a tripped warranty bit means your warranty will be void, but I have not seen any cases where people have been denied warranty. However it is better to play it safe than sorry if you really do care about warranty.
Wikipedia sums it up pretty nicely.
Read more about Samsung Knox on Wikipedia
How to remove Knox
If you do not use or plan to use Knox, the limitations imposed by Samsung can affect your overall experience with root access, or make the service become bloatware. For this reason you may want to remove it. Follow the link below to make your device Knox free. Flash in custom recovery and do not forget to nandroid before you flash! Thanks to bilgerryan over in the Sprint forums!
Get Knox removal zip here
Ill take one!
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
And another!
---------- Post added at 02:08 AM ---------- Previous post was at 02:08 AM ----------
Good write up btw! Thanks!
Just a heads up for T999 users who are going to flash root66 in Odin: flashing root66 in Odin DID trip the warranty bit for my device. I was running NC2 on my T999 (T-Mobile), flashed root66 NC2 and the bit was tripped. If you're worried about maintaining warranty eligibility you should take note.
friedchocolatesoda said:
Just a heads up for T999 users who are going to flash root66 in Odin: flashing root66 in Odin DID trip the warranty bit for my device. I was running NC2 on my T999 (T-Mobile), flashed root66 NC2 and the bit was tripped. If you're worried about maintaining warranty eligibility you should take note.
Click to expand...
Click to collapse
Thanks, but this thread is for touchwiz kitkat. Its not intended for 4.3 or any other build unless specifically related.
But still, im not sure why it tripped the bit on yours. It did just fine on mine and others...
I know this is a kitkat thread but it also tripped the warranty bit on my t999l
Sent from my SGH-T999 using XDA Premium 4 mobile app
friedchocolatesoda said:
Just a heads up for T999 users who are going to flash root66 in Odin: flashing root66 in Odin DID trip the warranty bit for my device. I was running NC2 on my T999 (T-Mobile), flashed root66 NC2 and the bit was tripped. If you're worried about maintaining warranty eligibility you should take note.
Click to expand...
Click to collapse
chalky7880 said:
I know this is a kitkat thread but it also tripped the warranty bit on my t999l
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this is odd as it should not trip the counter even though it was in jellybean.. to my knowledge the counter is tripped when you flash a custom recovery, but I will edit the OP until further confirmation.. thanks for the heads up guys
Edit: flashing kernel will also trip counter
Sent from my SGH-M919 using Tapatalk
Your probably right. I did flash a custom recovery so I bet that's what tripped it
Sent from my SGH-T999 using XDA Premium 4 mobile app
chalky7880 said:
Your probably right. I did flash a custom recovery so I bet that's what tripped it
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's all good, all feedback is appreciated. Believe it or not, it actually gave me the idea to mention in the OP how to keep the warranty bit from being tripped for those who want to avoid tripping it. Thank you!
Sent from my SGH-M919 using Tapatalk
Just fyi for everyone, there have been claims for both in the root66 thread. Some say it tripped the bit, while for others like myself it did not. No idea why, but I do not believe it has anything to do with the root66 firmware. There have been people who tripped the warranty bit just by taking the ota!
DocHoliday77 said:
Just fyi for everyone, there have been claims for both in the root66 thread. Some say it tripped the bit, while for others like myself it did not. No idea why, but I do not believe it has anything to do with the root66 firmware. There have been people who tripped the warranty bit just by taking the ota!
Click to expand...
Click to collapse
That would be a big screw up for Samsung. Really hope this is not the case
Sent from my SGH-M919 using Tapatalk
Its not a common occurrence, but it has happened.
Guys...Im not a total newbie but I have a couple of question. I have my SM-N900T rooted with N900TTMBBMI7..used odin, CF-Root etc etc and its working great...so I have dabbled enough in this so I am a bit dangerous. I have CWM recovery and Titanium backup and can/do make backups before I add any apps, etc.
I would like to upgrade to N900TUVUDNF1 and I have seen that in this thread http://forum.xda-developers.com/showthread.php?t=2761451 there is a deodexed, rooted version by Jovy23 so that is great...I do have a couple of questions I want to be clear on before I start this process :
1) I see that people talk about needing a specific bootloader...do I? Can anyone clarify that for me?
2) I have lots of apps installed on my N900TTMBBMI7 now as you can imagine. Would the process be to install N900TUVUDNF1 with odin as per the instructions and THEN, install Titanium backup and restore my apps? I dont want to spend a lot of time getting the phone back to what I have now if I can avoid it.
3) Will the N900TUVUDNF1 install wipe out my CWM recovery ? Do I need to re-install it after flashing N900TUVUDNF1 ?
4) If something goes really wrong, the process to revert would be to install CWM recovery and restore my N900TTMBBMI7 backup?
Anything else you guys would like to advise me of will be greatly appreciated...
thanks!!
re: NF1 firmware
calderonr said:
Guys...Im not a total newbie but I have a couple of question. I have my SM-N900T rooted with N900TTMBBMI7..used odin, CF-Root etc etc and its working great...so I have dabbled enough in this so I am a bit dangerous. I have CWM recovery and Titanium backup and can/do make backups before I add any apps, etc.
I would like to upgrade to N900TUVUDNF1 and I have seen that in this thread http://forum.xda-developers.com/showthread.php?t=2761451 there is a deodexed, rooted version by Jovy23 so that is great...I do have a couple of questions I want to be clear on before I start this process :
1) I see that people talk about needing a specific bootloader...do I? Can anyone clarify that for me?
2) I have lots of apps installed on my N900TTMBBMI7 now as you can imagine. Would the process be to install N900TUVUDNF1 with odin as per the instructions and THEN, install Titanium backup and restore my apps? I dont want to spend a lot of time getting the phone back to what I have now if I can avoid it.
3) Will the N900TUVUDNF1 install wipe out my CWM recovery ? Do I need to re-install it after flashing N900TUVUDNF1 ?
4) If something goes really wrong, the process to revert would be to install CWM recovery and restore my N900TTMBBMI7 backup?
Anything else you guys would like to advise me of will be greatly appreciated...
thanks!!
Click to expand...
Click to collapse
#1: The NF1 bootloader is part of the official Samsung N900T NF1 Kitkat firmware.
Here is the direct download link for the firmware:
chrome://mega/contenthttp:
https://mega.co.nz/#!ioglFaQD!IzrjOKfoQXnfzTVjItUnjVvqzVSoG4s0wkKLTvit9BY
#2: You will need to restore your apps with titanium backup after odin
flashing the official stock NF1 firmware.
#3: Odin flashing the NF1 firmware will wipe cwm recovery so you will need
to odin flash TWRP recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
#4: Before flashing TWRP you will need to odin flash cf-autoroot which
can be found here:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
#5: Once you flash NF1 firmware you cannot revert back to MI7 firmware
it will either bootloop or get stuck on boot screen if you try doing it.
In other words you cannot downgrade the firmware once it's updated to NF1.
Good luck!
Misterjunky said:
#1: The NF1 bootloader is part of the official Samsung N900T NF1 Kitkat firmware.
Here is the direct download link for the firmware:
chrome://mega/contenthttp:
https://mega.co.nz/#!ioglFaQD!IzrjOKfoQXnfzTVjItUnjVvqzVSoG4s0wkKLTvit9BY
#2: You will need to restore your apps with titanium backup after odin
flashing the official stock NF1 firmware.
#3: Odin flashing the NF1 firmware will wipe cwm recovery so you will need
to odin flash TWRP recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
#4: Before flashing TWRP you will need to odin flash cf-autoroot which
can be found here:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
#5: Once you flash NF1 firmware you cannot revert back to MI7 firmware
it will either bootloop or get stuck on boot screen if you try doing it.
In other words you cannot downgrade the firmware once it's updated to NF1.
Good luck!
Click to expand...
Click to collapse
Wow, thanks for the quick reply..I am glad you answered because I was totally under the impression that reverting back was indeed possible..I would have been in a wold of hurt if something went wrong and I could not revert since I use this device for work as well. So this of course begs a few more followup questions
1) The firmware at https://mega.co.nz/#!ioglFaQD!IzrjOK...4s0wkKLTvit9BY I assume is NOT rooted and therefore I would have to root with CF-Root etc...correct?
2) What is exactly the bootloader in this context? You are not refering to TWRP/CWM I assume? Is it the built in code to get the startup going? I am familiar with Linux bootloader like LILO and GRUB...is it the same concept?
3) Understood on restoring apps with Titanium backup...you refer only to the official firmware. Are you suggesting that I should not use the stock rooted NF1 I found?
4) Understood that flashing NF1 will wipe out CWM. You state to odin flash TWRP. Does that mean I should NOT use CWM and switch to TWRP? I am more familiar with CWM and I would like to continue using that one if possible.
5) Lastly and more importantly, why will reverting back to MI7 will cause the bootloop or stuck on boot screen? Any solution to that at all?
Again, thanks for your suggestions and quick reply!!
calderonr said:
Wow, thanks for the quick reply..I am glad you answered because I was totally under the impression that reverting back was indeed possible..I would have been in a wold of hurt if something went wrong and I could not revert since I use this device for work as well. So this of course begs a few more followup questions
1) The firmware at https://mega.co.nz/#!ioglFaQD!IzrjOK...4s0wkKLTvit9BY I assume is NOT rooted and therefore I would have to root with CF-Root etc...correct?
2) What is exactly the bootloader in this context? You are not refering to TWRP/CWM I assume? Is it the built in code to get the startup going? I am familiar with Linux bootloader like LILO and GRUB...is it the same concept?
3) Understood on restoring apps with Titanium backup...you refer only to the official firmware. Are you suggesting that I should not use the stock rooted NF1 I found?
4) Understood that flashing NF1 will wipe out CWM. You state to odin flash TWRP. Does that mean I should NOT use CWM and switch to TWRP? I am more familiar with CWM and I would like to continue using that one if possible.
5) Lastly and more importantly, why will reverting back to MI7 will cause the bootloop or stuck on boot screen? Any solution to that at all?
Again, thanks for your suggestions and quick reply!!
Click to expand...
Click to collapse
Be careful who you listen to on xda.
If your knox warranty flag is 0x0 DO NOT follow those instructions if you want it to stay that way.
To check, boot into download mode (reboot with volume+power+voldown.
If it's 0x0 and you want to keep it that way, you'll want to know that if you upgrade, flashing a custom recovery WILL ALWAYS trip knox once your bootloader is on kitkat.
The caveat is that if you want kitcat, you have to upgrade your bootloaders for things to work properly.
Now, with all that out of the way...
I would recommend going up to NF4 (bypassing NF1) as it is the latest.
I have a link in my sig with all the files for NF4 which also contains the upgrade method that doesn't trip knox.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
---------- Post added at 11:27 AM ---------- Previous post was at 11:16 AM ----------
In case you can't see my sig due to being in xda app or tapatalk:
NF4 files and instructions: http://forum.xda-developers.com/showthread.php?t=2834398
Or if you're dead set on NF1, there's a link to that thread at the top of the NF4 post. The instructions in post 2 of the nf4 thread are valid for nf1 add well.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Be careful who you listen to on xda.
If your knox warranty flag is 0x0 DO NOT follow those instructions if you want it to stay that way.
To check, boot into download mode (reboot with volume+power+voldown.
If it's 0x0 and you want to keep it that way, you'll want to know that if you upgrade, flashing a custom recovery WILL ALWAYS trip knox once your bootloader is on kitkat.
The caveat is that if you want kitcat, you have to upgrade your bootloaders for things to work properly.
Now, with all that out of the way...
I would recommend going up to NF4 (bypassing NF1) as it is the latest.
I have a link in my sig with all the files for NF4 which also contains the upgrade method that doesn't trip knox.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Toastido...Thanks for the reply...I have already tripped the warranty counter so lets say that at this point I am OK with that
So a few questions for you :
1) I am OK going to NF4 and I assume that the files/links you pointed me to below will still work on a tripped knox flag? Correct?
2) Does the same apply that if I go to NF4 there is no way to revert back to MI7?
3) Does your NF4 upgrade link/instructions contain the bootloader needed ? I assume so but want to make sure just in case I need anything else other than what you pointed me to. I am asking this because you stated "if you want kitcat, you have to upgrade your bootloaders for things to work properly. "
4) Can I continue to use CWM or do I have to switch to TWRP?
5) What about rooting? Is your firmware rooted or do I need to do it myself? If so, what do you recommend for rooting?
Thanks!!!
calderonr said:
Toastido...Thanks for the reply...I have already tripped the warranty counter so lets say that at this point I am OK with that
So a few questions for you :
1) I am OK going to NF1 and I assume that the files/links you pointed me to below will still work on a tripped knox flag? Correct?
2) Does the same apply that if I go to NF1 there is no way to revert back to MI7?
3) Does your NF1 upgrade link/instructions contain the bootloader needed ? I assume so but want to make sure just in case I need anything else other than what you pointed me to. I am asking this because you stated "if you want kitcat, you have to upgrade your bootloaders for things to work properly. "
4) Can I continue to use CWM or do I have to switch to TWRP?
Thanks!!!
Click to expand...
Click to collapse
Hey!
1) yes. I'd recommend just flashing the full package in desktop odin in that case. Power of your device completely for 10 to 30 seconds then boot directly to download mode.
2) yes. Once you go up from jb to kk you cannot go back. This is due to bootloader update efuses.
3) yes they do.
4) you can use cwm if you want, just make sure to get the correct one. Usually they are tagged kk or 4.4. Using jb versions will no longer work.
I assume you meant nf4, but the same applies to either.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Hey!
1) yes. I'd recommend just flashing the full package in desktop odin in that case. Power of your device completely for 10 to 30 seconds then boot directly to download mode.
2) yes. Once you go up from jb to kk you cannot go back. This is due to bootloader update efuses.
3) yes they do.
4) you can use cwm if you want, just make sure to get the correct one. Usually they are tagged kk or 4.4. Using jb versions will no longer work.
I assume you meant nf4, but the same applies to either.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Yeap...I meant NF4 and I sent in an edit but you beat me to it..ok...I will give this a try...I did ask one more question on the edit that I am not sure where it went...
5) About rooting...if I use odin to flash the full package as I have done before (selecting PDA), how would you recommend I root the NF4 since I assume the stock firmware is NOT rooted. Do you recomend CF-Root?
thanks aod sorry to pestering I want to make sure I do this right the first time!!
calderonr said:
Yeap...I meant NF4 and I sent in an edit but you beat me to it..ok...I will give this a try...I did ask one more question on the edit that I am not sure where it went...
5) About rooting...if I use odin to flash the full package as I have done before (selecting PDA), how would you recommend I root the NF4 since I assume the stock firmware is NOT rooted. Do you recomend CF-Root?
thanks aod sorry to pestering I want to make sure I do this right the first time!!
Click to expand...
Click to collapse
Np. As for number 5, yes, CF-Auto-Root is the best (maybe the only?) method for fw beyond ne6. If you do this and find supersu missing, a simple install from the play store afterwards will fix you right up.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Np. As for number 5, yes, CF-Auto-Root is the best (maybe the only?) method for fw beyond ne6. If you do this and find supersu missing, a simple install from the play store afterwards will fix you right up.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Toastido :
Not trying to be dense here but help me understand this. Its re. the inability to go back to MI7 from NF4. You say it has to do with the bootloader, BUT, if I take a CWM backup BEFORE I flash NF4, would not that backup contain the MI7 bootloader in it, so when/if I restore the backup, would not that also restore the MI7 bootloader and the device would not even notice it had flashed NF4 before? Granted I would have to re-clash the JB compatible CWM before I restored, but would that not work? If not, can you explain why?
Thanks!!
calderonr said:
Toastido :
Not trying to be dense here but help me understand this. Its re. the inability to go back to MI7 from NF4. You say it has to do with the bootloader, BUT, if I take a CWM backup BEFORE I flash NF4, would not that backup contain the MI7 bootloader in it, so when/if I restore the backup, would not that also restore the MI7 bootloader and the device would not even notice it had flashed NF4 before? Granted I would have to re-clash the JB compatible CWM before I restored, but would that not work? If not, can you explain why?
Thanks!!
Click to expand...
Click to collapse
No it would not work. The reason, as stated in a previous post, is due to eFused bootloaders. Once the efuse is tripped, it cannot be reset, and the bootloader will fail if it's value is lower than the fused value. Otherwise just flashing the bootloader backwards would work. If you go the odin route you will be protected by odin mode. If you try via recovery of a nandroid that contains the bootloader, it'll either just not work, or (worse) brick your device.
The fuses are tripped in a sequential order. 0,1,2,3 etc. JB BL can only operate on fused value of 1 or lower. KK BL can only install and function (depending on current version) at 3 or lower.
NB4 will fuse to 2. NE6 through NF4 I believe will fuse to 3, thus preventing the JB BL from functioning.
Hope that helps.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Let me know how it goes. I have to update mine to.. I'm on NB4 with no issues but I should update anyways.
Sent from my SM-N900T 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.