Related
Hi, quick question. I read that with Note 3, because all the stock ROMs are knox-enabled, I can upgrade by flashing via Odin (even if I have Knox tripped).
So this:
If you try to downgrade to KNOX-disabled system(MGA for example) your device will be flaged as KNOX Void Warranty 0×1 and will get a special lock – you won’t be able to update to any KNOX-enabled firmware even by ODIN.
Click to expand...
Click to collapse
doesn't apply because there aren't knox-disabled firmwares.
What about if I downgrade using Odin? By flashing an older firmware? If I'm not on the newer bootloaders I can, right? But will Knox be tripped?
I also read that if you try to flash a non-Knox firmware onto a Knox phone you'll be bricked. I can't remember which thread/what circumstances, so hoping someone can shed some light on that.
Lastly, if I'm on unrooted stock firmware, can I use URDLV to "patch" the newest firmware, then flash it to get the rooted latest firmware WITHOUT the newer bootloader and WITHOUT tripping knox? So I can choose to downgrade should the new firmware has any problems.
Situation on trip the Knox or not: (No idea on downgrade as I never try, I think it won't under same bootloader version)
Flash any stock ROM including Kitkat officially or not with odin without rooting - won't trip knox.
Officially phone came with MJ1 or older - root with URDLV won't trip knox.
Officially phone came with MJ7 or later - root with any method will trip knox.
Officially phone came with MJ1 but later updates to MJ7 with OTA/KIES/PC Odin and later - root with any method will trip knox.
Officially at MJ1 and rooted and update to any firmware excluding KitKat ROM using Mobile Odin Pro only - root will remain and won't trip the knox.
Install any custom recovery and custom kernel will trip the knox.
Update KitKat via Mobile Odin Pro (MOP) without trip the Knox:
Your current bootloader is not newer than MJ1.
Load Official Poland ROM in MOP
Enable EverRoot, Choose option "Download mode" in after flashing. Start flashing.
After booted into Download Mode, connect your phone to your computer and run PC Odin 3.09.
Load this bootloader http://forum.xda-developers.com/showpost.php?p=49425513&postcount=352 in the BL section
Check Phone Bootloader Update and F.Reset.time, un-check Auto Reboot and Start Flashing.
When Odin says RESET!, switch off your phone and reboot normally.
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.
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.
Hi to everyone, I have a galaxy A5(2016) A510F and I want to root it but this will trip knox so I want to ask if we root a stock rom and flash it via odin does this detect root and trip knox ? (we will modify the system.img that we find in.tar file)
It probably won't trigger KNOX, but root access would be unstable, at best. Try using KingRoot instead - if it works on your device, it will root it and keep the KNOX counter the same, and if it doesn't, it'll just tell you that it can't root your phone.
I don't want try it because my phone it's new so can someone try it and post the result ? Maybe someone that have already trigger knox, this don't want to be a problem for him/her
EDIT: I think Kingroot don't work http://forum.xda-developers.com/sam...ment/galaxy-a5-2016-success-kingroot-t3400564
Up
I tried king root, but after reebooting my phone was unrooted. I suggest you to flash cf autoroot because, yes, it trips knox counter, but If u soft-brick your device in any way, you can always solve it using odin and flashing stock firmware/PIT...
They are two different things, maybe you are confused because it doesn't mean that if you flash cf autoroot and soft-brick your devices you can unbrick it just flashing stock rom, yes this is true but you can unbrick you phone in anytime without having cf autoroot!
I didn't mean that, i know odin doesn't request root permission, I said that if he flashes cf autoroot and he soft-bricks his device ( I know it's almost impossible ) he will resolve the problem by flashing stock formware (or a custom ROM after wiped cache, dalvik, data and system)
Unfortunately not possible to pre-root a stock Samsung 5.1.1 or 6.0 rom and preserve knox. It will boot loop your device. Selinux will block root and prevent the device from booting unless the boot.img is patched to remove the selinux root restriction.
However patching the boot.img trips knox, catch 22 situation.
Keep hoping for kingroot or Kingoroot if you want to preserve the knox counter.
Thanks for the reply
Can anyone try this http://www.samsungsfour.com/tutorials/how-to-root-all-samsung-galaxy-smartphones-without-pc.html ? I don't want to trip my knox!
If it works it wont trip knox as it doesn't touch the binaries.
Unfortunatelly, I can't try because i've already tripped the knox
I have rooted my S4 without tripping KNOX. If I would flash a custom recovery using flashify and use said recovery to install a custom ROM, would it trip KNOX?
More info
It says that the binary is unofficial, but knox is still 0x0