I've been googling this for a while and haven't found anything conclusive. Some sources say this won't trip knox, other sources say it will. I've read and searched through a few Q&A threads here as well, and again, some say this is okay to do and others say it is not.
Can I flash an official,stock .zip of the previous build number, N900VVRUEOB6, over top of the newest build number, N900VVUREFOF1, without tripping knox? My phone updated itself - the nag screen appeared after unlocking and my phone immediately rebooted and installed the update against my will.
Would this void my warranty? I have read that using Odin would definitely trip knox, so I would be flashing the zip from recovery mode. There is no kernel update involved so it should allow me to do this.
Is there any other way to roll back the security update that fixed stagefright?
aklyatne said:
I've been googling this for a while and haven't found anything conclusive. Some sources say this won't trip knox, other sources say it will. I've read and searched through a few Q&A threads here as well, and again, some say this is okay to do and others say it is not.
Can I flash an official,stock .zip of the previous build number, N900VVRUEOB6, over top of the newest build number, N900VVUREFOF1, without tripping knox? My phone updated itself - the nag screen appeared after unlocking and my phone immediately rebooted and installed the update against my will.
Would this void my warranty? I have read that using Odin would definitely trip knox, so I would be flashing the zip from recovery mode. There is no kernel update involved so it should allow me to do this.
Is there any other way to roll back the security update that fixed stagefright?
Click to expand...
Click to collapse
OF1 has downgrade protection so you can't Odin back. It will trip knox. If knox is not 0x0, your warranty is void.
Dravekx said:
OF1 has downgrade protection so you can't Odin back. It will trip knox. If knox is not 0x0, your warranty is void.
Click to expand...
Click to collapse
I wasn't going to use Odin.
I'm guessing that means I can't flash the file from recovery mode either though?
Related
Hi,
I'm a new S4 (i337M) owner, I had a S2 but it broke.
I saw a couples of warning about the Knox BS from Samsung and I want to be sure that I understand everything.
My Android Version is 4.3 MK6 . In the download mode, I have the knox 0x0 . If I install the CWM Recovery, is it possible to keep the 0x0 or it will trip to 0x1 ? My phone is rooted but I want to do a nandroid backup before playing with mods and roms and I think that it's not possible without a custom recovery.
If I trip knox to 0x1, I know that I will not be able to use the knox option (and I don't give a sh_t about Knox) but if it's possible to do a nandroid without tripping the 0x0, it will be nice
Thanks guys !
Yes, if you flash CWM, your Knox will trip to 0x1, and your warranty will be void.
No, you cannot do a Nandroid without a custom recovery, which means you will trip your Knox counter.
Yes, you CAN root your MK6 without tripping Knox, it just will not give you custom recovery options.
ve6ay said:
Yes, if you flash CWM, your Knox will trip to 0x1, and your warranty will be void.
No, you cannot do a Nandroid without a custom recovery, which means you will trip your Knox counter.
Yes, you CAN root your MK6 without tripping Knox, it just will not give you custom recovery options.
Click to expand...
Click to collapse
First of all, big thanks for your fast reply !
My S4 is rooted ( I did it an hour after I had the phone ) , so if I have a Knox 0x1 and if I don't care about the know feature and about the phone's warranty, do I will be able to flash customs roms and original roms ?
I have the same problem!!!
maxflay said:
First of all, big thanks for your fast reply !
My S4 is rooted ( I did it an hour after I had the phone ) , so if I have a Knox 0x1 and if I don't care about the know feature and about the phone's warranty, do I will be able to flash customs roms and original roms ?
Click to expand...
Click to collapse
I have an AT&T S4 that has a tripped Knox counter(0x1). I have no problems gaining root access. I have used Odin 3.10, Heimdall, Casual, and Loki to try to obtain a custom recovery such as CWM or TWRP, but none of these worked. I'm starting to think that if the Knox counter is tripped, the container for Samsung's Knox software is locked forever and you can never flash a custom recovery. Someone PLEASE tell me I'm wrong and there is a way to flash custom recovery with a 0x1 counter tripped.
seanswiggett said:
I have an AT&T S4 that has a tripped Knox counter(0x1). I have no problems gaining root access. I have used Odin 3.10, Heimdall, Casual, and Loki to try to obtain a custom recovery such as CWM or TWRP, but none of these worked. I'm starting to think that if the Knox counter is tripped, the container for Samsung's Knox software is locked forever and you can never flash a custom recovery. Someone PLEASE tell me I'm wrong and there is a way to flash custom recovery with a 0x1 counter tripped.
Click to expand...
Click to collapse
On the SGH-I337, any bootloader more recent than the original MDB or MDL are locked in such a way that you can not load a custom kernel or a custom recovery. You are limited to root, safestrap, and Samsung Touchwiz based firmware. As far as I know, it has nothing to do with knox.
Incidentally, the original MDB and MDL bootloaders were locked as well, but LOKI exploited a flaw in the bootloader code which allowed custom kernel and custom recovery to be installed. This flaw was removed starting with the MK2 and newer bootloaders.
I have a old Samsung Charge that I have been using. I have used odin and custom roms and the phone is currently rooted....so I have some experience with doing so. I am planning on upgrading to a new Galaxy S5 and will need to root and tether when I get it. I use my phone for internet connections, so I need to get all the files necessary before I begin working on the new phone.
I have downloaded both the NCG and the NE9 Kernels, Odin 3.09 (which I found 3 versions of, and settled on the internal marked Samsung). I downloaded the Multitool v4.44 but I don't think that is necessary. I also have SuperSU Pro and SuperSU, and Towelroot. So I think I have everything I need....I also have wifi tether...which I will need to get back on line if necessary...
I was looking around for a PIT file, not sure if I need it...but if things go wrong, I would like to have it to set the phone back to stock.
Is there a pit file available...and do i need it...
Thanks
wetwaterdog said:
I have a old Samsung Charge that I have been using. I have used odin and custom roms and the phone is currently rooted....so I have some experience with doing so. I am planning on upgrading to a new Galaxy S5 and will need to root and tether when I get it. I use my phone for internet connections, so I need to get all the files necessary before I begin working on the new phone.
I have downloaded both the NCG and the NE9 Kernels, Odin 3.09 (which I found 3 versions of, and settled on the internal marked Samsung). I downloaded the Multitool v4.44 but I don't think that is necessary. I also have SuperSU Pro and SuperSU, and Towelroot. So I think I have everything I need....I also have wifi tether...which I will need to get back on line if necessary...
I was looking around for a PIT file, not sure if I need it...but if things go wrong, I would like to have it to set the phone back to stock.
Is there a pit file available...and do i need it...
Thanks
Click to expand...
Click to collapse
All you need to get rooted is towelroot. I initially rooted and installed safestrap and put Alliance ROM on to a rom slot before I found out safestrap rom slots are borked and you have to install custom roms on the stock slot. I odined back to stock NCG and did not use the pit file and all came out good. After I re-rooted, I just use Xposed framework and modules.
You can find the pit file and everything else you need to go back to stock here ==> http://forum.xda-developers.com/showpost.php?p=53447942&postcount=1
Thanks for the link.....
I noticed the stock kernels are around 2GB each.
When I was collecting files for my root, I had come across a posting by Cat McGowan titled something like "How to get root back after the NE9 OTA update
within that posting, there were 2 kernels that were needed to be downloaded.....which I did..
1) G900V_NCG_Stock_Kernel.tar.md5 at 11,431 kb
2) G990V_NE9_Stock_Kernel.tar.md5 at 11,471 kb
When I used your links, the Stock kernels are about 2 gb each. Big difference.
What if anything are the 2 smaller kernels used for as opposed to the larger 2gb kernels.
wetwaterdog said:
Thanks for the link.....
I noticed the stock kernels are around 2GB each.
When I was collecting files for my root, I had come across a posting by Cat McGowan titled something like "How to get root back after the NE9 OTA update
within that posting, there were 2 kernels that were needed to be downloaded.....which I did..
1) G900V_NCG_Stock_Kernel.tar.md5 at 11,431 kb
2) G990V_NE9_Stock_Kernel.tar.md5 at 11,471 kb
When I used your links, the Stock kernels are about 2 gb each. Big difference.
What if anything are the 2 smaller kernels used for as opposed to the larger 2gb kernels.
Click to expand...
Click to collapse
The links in the post I pointed you to are the full factory stock system tar files. The entire phone package of which just the kernel is a small part. If you want to root NE9 you have one of two options. If you are running NCG, you can just go ahead and take the NE9 OTA update. HOWEVER !!!! You will lose root with NE9 and Towelroot will not work to root it. You need to flash the NCG kernel into NE9, apply towel root, then flash back to the NE9 kernel and voila ... you will have yourself a shiny new rooted NE9 S5
Option two would be to install NE9 via Odin with the factory tar file. Either way, you have to flash the NCG kernel to obtain root and then flash the newer kernel...
Thanks for clearing that up....
Waterdog
Chopstix9 said:
The links in the post I pointed you to are the full factory stock system tar files. The entire phone package of which just the kernel is a small part. If you want to root NE9 you have one of two options. If you are running NCG, you can just go ahead and take the NE9 OTA update. HOWEVER !!!! You will lose root with NE9 and Towelroot will not work to root it. You need to flash the NCG kernel into NE9, apply towel root, then flash back to the NE9 kernel and voila ... you will have yourself a shiny new rooted NE9 S5
Option two would be to install NE9 via Odin with the factory tar file. Either way, you have to flash the NCG kernel to obtain root and then flash the newer kernel...
Click to expand...
Click to collapse
Will that void knox?
playingbball20 said:
Will that void knox?
Click to expand...
Click to collapse
I originally rooted/supersu/busybox/safestrap/alliance and found I screwed up using rom slot. I odined back to stock ngc with tar file, re-rooed, supersu/exposed framework and modules is what I currently run. I just shut down the phone and first booted into stock recovery then shut it down and booted into download mode. No where on the screens did I see any indication knox was tripped. I believe a message gets displayed that knox warranty void if it is tripped. So, no, I am going to say it is knox safe.
Chopstix9 said:
I originally rooted/supersu/busybox/safestrap/alliance and found I screwed up using rom slot. I odined back to stock ngc with tar file, re-rooed, supersu/exposed framework and modules is what I currently run. I just shut down the phone and first booted into stock recovery then shut it down and booted into download mode. No where on the screens did I see any indication knox was tripped. I believe a message gets displayed that knox warranty void if it is tripped. So, no, I am going to say it is knox safe.
Click to expand...
Click to collapse
The only way to know if your knox has been tripped is to go into download mode. There is a notification on there for
Knox=0x0 - not tripped
knox=0x1 - knox tripped
playingbball20 said:
The only way to know if your knox has been tripped is to go into download mode. There is a notification on there for
Knox=0x0 - not tripped
knox=0x1 - knox tripped
Click to expand...
Click to collapse
Knox not even listed on the screen, maybe disabled in Xposed framework
ODIN MODE
PRODUCT NAME: SM-G900V
CURRENT BINARY: Samsung Official
REACTIVATION LOCK(KK): OFF
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, PI
UDC START
But I did read in other threads in researching prior to all I did that knox does not get tripped. I researched both before initial root and prior to odin back to stock.
Chopstix9 said:
Knox not even listed on the screen, maybe disabled in Xposed framework
ODIN MODE
PRODUCT NAME: SM-G900V
CURRENT BINARY: Samsung Official
REACTIVATION LOCK(KK): OFF
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, PI
UDC START
But I did read in other threads in researching prior to all I did that knox does not get tripped. I researched both before initial root and prior to odin back to stock.
Click to expand...
Click to collapse
I found out the REACTIVATION LOCK(KK): OFF should be REACTIVATION LOCK(KK): ON, so your knox is tripped
playingbball20 said:
I found out the REACTIVATION LOCK(KK): OFF should be REACTIVATION LOCK(KK): ON, so your knox is tripped
Click to expand...
Click to collapse
I dunno about that ... supersu disables knox and I think that's why it says it is off. (I could odin back to stock to see if it says on but I ain't screwing with a good thing). I downloaded samsung phone info app from play store and knox status is 0x0 ... that is knox not tripped.
Furthermore; that knox status of 0x0 is not just after rooting the phone. When I first got it, I rooted, installed safestrap, supersu, busybox and installed alliance rom on rom slot. Then found out about the bugs in safestrap and I odined back to stock. I then rooted, supersu and Xposed framework with modules. The knox status is STILL 0x0 ... so I feel pretty confident in saying people are safe to flash away if they do it properly.
Chopstix9 said:
Furthermore; that knox status of 0x0 is not just after rooting the phone. When I first got it, I rooted, installed safestrap, supersu, busybox and installed alliance rom on rom slot. Then found out about the bugs in safestrap and I odined back to stock. I then rooted, supersu and Xposed framework with modules. The knox status is STILL 0x0 ... so I feel pretty confident in saying people are safe to flash away if they do it properly.
Click to expand...
Click to collapse
Verizon and all there crap in making everything different. My bad, why wouldn't they just have the knox counter on their download?
playingbball20 said:
Verizon and all there crap in making everything different. My bad, why wouldn't they just have the knox counter on their download?
Click to expand...
Click to collapse
I wouldn't have anything but VZW ... I travel all over the country and stream data all day long on my trips and hardly ever lose connection. You're not gonna do that with the other 3 major carriers out there.
Chopstix9 said:
I wouldn't have anything but VZW ... I travel all over the country and stream data all day long on my trips and hardly ever lose connection. You're not gonna do that with the other 3 major carriers out there.
Click to expand...
Click to collapse
Very true.
I went into download mode and there was nothing about knox 0x0 or 0x1. It does however, say "system status: custom" and when I rebooted, it says "custom" on the samsung flash with an unlocked lock. I followed the instructions from rootjunky and I seem to have root, but as for knox and my warranty, I'm not sure if I screwed up big time.
Edit: Okay, so I did a bit more searching and I guess "system status: custom" doesn't have anything to do with knox so I'm okay? Also, what caused this? towelroot, supersu, rootchecker? I still would like to know I can tell if I tripped knox though.
Chowlz said:
I went into download mode and there was nothing about knox 0x0 or 0x1. It does however, say "system status: custom" and when I rebooted, it says "custom" on the samsung flash with an unlocked lock. I followed the instructions from rootjunky and I seem to have root, but as for knox and my warranty, I'm not sure if I screwed up big time.
Edit: Okay, so I did a bit more searching and I guess "system status: custom" doesn't have anything to do with knox so I'm okay? Also, what caused this? towelroot, supersu, rootchecker? I still would like to know I can tell if I tripped knox though.
Click to expand...
Click to collapse
I believe it will say Knox Warranty Status Void or Warranty Bit 0x1, either way you will know if you tripped it in download mode. Towelroot dose not trip knox. As for custom status having root and having a modified system will cause this. It will return to Official when you Odin back to stock with no root.
Misterxtc said:
I believe it will say Knox Warranty Status Void or Warranty Bit 0x1, either way you will know if you tripped it in download mode. Towelroot dose not trip knox. As for custom status having root and having a modified system will cause this. It will return to Official when you Odin back to stock with no root.
Click to expand...
Click to collapse
Awesome! Thanks for the reply!
Hi, i have note 3 sm n9005 or something and rooted my phone for some stupid reason, its still on stock the only thing that i think happened was i have supersu, i paniced and factory reset, now supersu has a error thing with something to do with binary settings or something. All i want to do it fully reset my phone, if its any help im british with EE... does flashing supersu trip knox counter? Am i actually rooted for if i were to flash stock? Will that trip it? Iv knly had phone few months and im scared... if i flash stock can i then update legally coz i cant update because the device is modified? I used odin... can someone help please, i know nothing and yes, i should look into what im doing more before hand. Can you explain everything and what to do please? Every little thing, please and without tripping knox and as if it was out the box new. Please
Firstly, flashing SuperSU trips KNOX. In the first place, to install SuperSU you need a custom recovery which would ALSO trip KNOX. Flashing back to stock unroots your phone too.
If you are convinced that you have not tripped KNOX, just re flash your phone back to stock with ODIN.
This_Guyse said:
Firstly, flashing SuperSU trips KNOX. In the first place, to install SuperSU you need a custom recovery which would ALSO trip KNOX. Flashing back to stock unroots your phone too.
If you are convinced that you have not tripped KNOX, just re flash your phone back to stock with ODIN.
Click to expand...
Click to collapse
I dont have a clue what i first did but what i did magically apeared with supersu. Can i flash stock which will get rid of supersu and can i reset my knox counter? And am i actually rooted seen as i factory reset?
MarkDyer1 said:
I dont have a clue what i first did but what i did magically apeared with supersu. Can i flash stock which will get rid of supersu and can i reset my knox counter? And am i actually rooted seen as i factory reset?
Click to expand...
Click to collapse
Flashing stock will get rid of SuperSU and root but you cannot reset KNOX. It is permanently 0x1 and will always be.
This_Guyse said:
Flashing stock will get rid of SuperSU and root but you cannot reset KNOX. It is permanently 0x1 and will always be.
Click to expand...
Click to collapse
What about the fact i factory reset? Is it still rooted to flash stock? And doesnt it have to be a unrooted stocked rather than flashing rooted stock? And where do i got stock and do i need to unzip files and stuff?
MarkDyer1 said:
Hi, i have note 3 sm n9005 or something and rooted my phone for some stupid reason, its still on stock the only thing that i think happened was i have supersu, i paniced and factory reset, now supersu has a error thing with something to do with binary settings or something. All i want to do it fully reset my phone, if its any help im british with EE... does flashing supersu trip knox counter? Am i actually rooted for if i were to flash stock? Will that trip it? Iv knly had phone few months and im scared... if i flash stock can i then update legally coz i cant update because the device is modified? I used odin... can someone help please, i know nothing and yes, i should look into what im doing more before hand. Can you explain everything and what to do please? Every little thing, please and without tripping knox and as if it was out the box new. Please
Click to expand...
Click to collapse
Reboot in download mode I. E. Volume down+home+power, check the knox counter if it's 0x1 then it has already been tripped and you have been set free ?? and if it's 0x0 you are still locked in a cage.
Report back with what you see.
saadramiz said:
Reboot in download mode I. E. Volume down+home+power, check the knox counter if it's 0x1 then it has already been tripped and you have been set free ?? and if it's 0x0 you are still locked in a cage.
Report back with what you see.
Click to expand...
Click to collapse
I know i have done something coz when i want to update it says this device has been modified. But i havent flashed any roms so surely knox should be 0x0 and flashing stock keeps it 0x0 doesnt it?
MarkDyer1 said:
I know i have done something coz when i want to update it says this device has been modified. But i havent flashed any roms so surely knox should be 0x0 and flashing stock keeps it 0x0 doesnt it?
Click to expand...
Click to collapse
Yes, if your Knox is still 0x0, flashing stock keeps it 0x0.
Use Phone INFO ★Samsung★ app to check for the Knox Warranty Void status (in the GENERAL INFO section).
Hello folks,
today I flashed official Lollipop 5.0.1 via ODIN on my N910-F and accidently tripped my KNOX Counter. So be careful if you do not want to void your warranty.
My phone is carrier branded DTM (T-Mobile) and had latest OTA firmware 4.4.4 *ANK4 on it. Back when i did buy my device I decided to debrand my phone as soon as Lollipop comes out.
So I did and flashed in one step from KitKat (T-Mobile) to Lollipop (Open). From what I read a assumed it would be no problem because it's a newer build but in some way it tripped my Knox Counter to 0x1 (3).
I did use Odin 3.09 as suggested by sammobile but ended up with an error (Fail) at the end of the flashing procedure. I downloaded Odin 3.10 and reflashed without any problems. This might be also considered as a reason for tripping the counter (as it says 3). I checked my counter after 2 factory resets afterwards.
Now I'm actually good to root I guess. Be careful.
EDIT: When I'm performing a factory reset from within the ROM it fails with "dm-verity verification failed..." message and takes me to the Android system recovery. From there I can do the factory reset. I think there is something gone wrong. Ideas on that message?
raupe1337 said:
Hello folks,
today I flashed official Lollipop 5.0.1 via ODIN in my N910-F and accidently tripped my KNOX Counter. So be careful if you do not want to void your warranty.
My phone is carrier branded DTM (T-Mobile) and had latest OTA firmware 4.4.4 *ANK4 on it. Back when i did buy my device I decided to debrand my phone as soon as Lollipop comes out.
So I did and flashed in one step from KitKat (T-Mobile) to Lollipop (Open). From what I read a assumed it would be no problem because it's a newer build but in some way it tripped my Knox Counter to 0x1 (3).
I did use Odin 3.09 as suggested by sammobile but ended up with an error (Fail) at the end of the flashing procedure. I downloaded Odin 3.10 and reflashed without any problems. This might be also considered as a reason for tripping the counter (as it says 3). I checked my counter after 2 factory resets afterwards.
Now I'm actually good to root I guess. Be careful.
Click to expand...
Click to collapse
I never heard of this? You tripped Knox with the official firmware? Did you maybe have the wrong options selected in Odin, as you would be the first who is able to trip Knox with official firmware???
I don't know why it tripped it. I haven't tripped it even after using Z3X box.
Everytime I use a firmware from sammobile it never tripped any counter of my phones.
marleyb said:
Did you maybe have the wrong options selected in Odin, as you would be the first who is able to trip Knox with official firmware???
Click to expand...
Click to collapse
Had standard options selected which are "Auto Reboot" and "F. Reset Time".
I might think the trip is not caused by flashing but performing a factory reset afterwards which results in "dm-verity verification failed..." message in the recovery menu. From what I know this error is caused by root which I didn't.
Update: Device is now working as supposed. After two failed attempts to flash the firmware via Kies new it worked on a third time. No error on factory reset.
My assumption is that there went something horribly wrong on first time flashing the firmware via ODIN, which preventet the factory reset from performing as usual. Knox detected that inexplicable status and graded it as modified which tripped the Knox counter then. I have no other explanation for this, maybe the 0.01% got real in my case.