I'm currently using stock MF6 firmware and there is no indication of the Knox warranty void flag in download mode. Does anyone know which firmware introduced this flag on the S4 mini or is it not implemented, yet? I'm asking because I want root access and need to know which prerooted firmwares I can choose from without this flag.
kodan2k said:
I'm currently using stock MF6 firmware and there is no indication of the Knox warranty void flag in download mode. Does anyone know which firmware introduced this flag on the S4 mini or is it not implemented, yet? I'm asking because I want root access and need to know which prerooted firmwares I can choose from without this flag.
Click to expand...
Click to collapse
As far as I can tell, there's no Knox flag known on any S4 mini firmware or variant. Definitely mine has no sign of it either. And from what I read, at least ith the S4 it was never transparent, only when the flag appared could you kill it, in older firmwares no matter what you did the flag was never set until you upgraded and there was something considered wrong then.
4.4 is supposed to bring Knox for the mini so it may bring the flag, which could be easier, harder or the same to avoid as the S4, only time will tell I guess. If it's similar, hopefully enough will have been learnt by the time S4 mini get 4.4 that we can easily get around it.
@Nil Einne
Thank you for your reply. Which firmware version are you using?
(I9195XXUA)MG3 (which is 4.2.2 / JDQ39). It's currently the latest for my CSC. I may root soon perhaps using a prerooted firmware (since mine is so old) but I'm waiting to see if anyone has tried it on a 16GB version. I didn't mention before but I guess it's clear now I have an I9195 but I haven't seen any mention of Knox flag seen for any variant of the S4 mini on current firmwares.
My s4 mini (I9195) came with firmware MF7 and was upgraded OTA to MG8.
After that I flashed with Odin to MH2 (Android 4.2.2).
Thereafter I flashed a custom rom (Slim with 4.3.1).
Where and how can I see whether my Knox warranty void might be 0x1 now.
And what if I flash back with Odin to firmware MF7?
Is that still possible without a later upgrade problem?
Curious about your info.
New Rom XXUBMJ7 whit KNOX bootloader (aboot.mbn) and aplications.
After flash this Rom we have on Download Mode:
KnoxKernelLock: 0x0
KnoxWarrantyVoid: 0x0
Like on Note 3 N9005, if we flash something, customer, root, KnoxWarrantyVoid: go to 0x1 and this is not reversible.
To Root
The Root-Kit-V1 install all superuser, SU and busybox but after reboot the SuperSU can't access to system, KNOX not permit.
To solve this we must flash after, on recovery the UPDATE-SuperSU-v1.65.zip from Chainfire. After we have root alright.
My case like on Note 3:
I not need the KNOX, the phone is only for me, then after root I delete all KNOX apk + odex from system/app.
Good luck
Is it possible to go back to old bootloader WITHOUT knox?
ladislav.heller said:
Is it possible to go back to old bootloader WITHOUT knox?
Click to expand...
Click to collapse
See response on Development Thread to this your question.
Always the KNOX:
You can read this post Always the KNOX.
Many info about KNOX.
Because it's not very clear even after reading many xda Thread, and users have many problems withknox I deciced to gather informations about Knox.
1 :What is Knox?: http://omegadroid.co/wanted-knox-void-warranty-0x1/
All you wanted to know about KNOX Void Warranty 0×1
By tamirda • October 9, 2013
Screenshot_2013-02-25_11_35_AM
Recently, Samsung announced that her all new devices will get an Android 4.3 update that includes KNOX Security system. According to Samsung, these devices will get the update:
Samsung Galaxy S3
Samsyng Galaxy Note II
Samsung Galaxy S4
Samsung Galaxy Note 3 (already has KNOX Security system)
Most of the users don’t root their devices and use it normally and for them KNOX Security system is a great option.
But what happanes if we want to root our device?
Now the problem begins.
Normal(unrooted and so..) devices are flaged as KNOX Void Warranty 0×0 right from the factory.
When we flash items which weren’t signed by Samsung, it flags your device as KNOX Void Warranty 0×1.
According to Chainfire, KNOX status is indeed an eFuse. This means that even JTAG can not reset the KNOX status back to 0×0.
Some facts about KNOX status:
It isn’t possible to downgrade to KNOX-disabled firmwares/bootloaders (An attempt sets 0×1) (even though some people state, downgrade is possible when omitting the bootloader file in a firmware package). By downgrading from KNOX-enabled to KNOX-disabled firmware, your devices will be locked to installation of newer firmwares.
Let’s focus on that fact. As we mentioned above, Devices like S4, S3 and Note II which came without KNOX will get the KNOX system.For example, S4 I9505 got about a month ago 4.2.2 update that includes KNOX-enabled system(MH1). 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. Samsung’s 4.3 update is KNOX-enabled, so if you tried to downgrade to KNOX-disabled firmware(for example MH8->MGA), you won’t be able to install 4.3 update.
This problem is only for devices which didn’t come with KNOX-enabled system from the factory(S4, S3 and Note 2)
Jeffery Butler confirmed this information:
FYI…Samsung told me that Knox warranty becomes 0×1(void) when the device with secured bootloader attempts to have non-secured bootloader. MH1 is the very first binary with secured bootloader. If MH1 is attempted to be downgraded to lower version(i.e. MGD) which has non-secured bootloader, then Knox warranty becomes void forever, and this means that the device can be used only for non-Knox device(no container can be created).
If you try to downgrade to KNOX-disabled firmware, you can’t install any new firmaware(that includes KNOX-enabled system) and use your device only with the old firmwares.
Even if you flash a KNOX-enabled firmware via odin (e.g. the latest fw) knox will be set to 0×1.
Flashing unsigned or modified images via odin will set knox to 0×1.
According to these two, flashing root/kernel/recovery/latest firmware by samsung/etc. will set KNOX status to 0×1.
Samsung stated, resetting the flag is impossible.
Chainfire confirmed that it is impossible to reset the flag.
KNOX is mandatory and can not be completely removed.
In custom roms we can remove KNOX apps, but the status remains 0×1.
Warranty Void is not a counter, it is a flag (0,1). We have never seen 0×2 or so.
Mirroring all partitions from a clean 0×0-Device to a 0×1-Device via JTAG produces an unfunctional device (reversible by restoring the 0×1 partitions on the phone).
Using JTAG or other repair tools to reset the flag is impossible.
KNOX bootloader verifies signatures of kernels and recoveries. No custom ones possible without voiding the knox warranty.
Again, if we flash kernel/recovery/etc. we will void the warranty.
This si how 0×1 looks like:
2rn7beq.jpg
This is how 0×0 looks like:
attachment.php
I guess you are asking yourself now, what the hell 0×1 means?
If your device is flageed as 0×1. you should forget about your warranty.
Chainfire and other people confirmed that your can’t use your warranty:
Worse than that, I’ve also been hearing that service center instructions are indeed that devices with this status tripped will not receive any warranty repairs. (Of course, the action they take may still depend on the service center). Their excuse is that the hardware is damaged by the owner. Seems Samsung is catching up in scumbaggery to HTC, who years ago attributed my HTC Diamond’s screen damage (digitizer detached) to the installation of HSPL
To anyone in the know it is obvious that this doesn’t really fly, and the eFuse blowing (is this the hardware damage?) is intentionally done by the bootloader when unsigned software is loaded.
If you want to read the whole Chainfire’s statement, click here.
What is eFUSE? it’s a technology that allows reprogramming a read-only memory chip in real-time, even though such chips come with hard-coded code that cannot be generally changed after manufacturing.
When flashing unofficial software on the device, the status of the system and KNOX is switched to CUSTOM while increasing a binary flash counter, which helps Samsung find out whether the device has been tampered with. However, while Chainfire’s TriangleAway app has let users switch the status back to official and reset the flash counter until now, the KNOX status is based on eFUSE – basically, once you flash custom kernels or root the Note 3, the KNOX code gets rewritten, and this constitutes hardware damage.
Well, all I can say is think twice before you play with your Samsung device. If you don’t care about warranty, and you like custom roms and cool stuff just be aware of this information and continue with what you are doing.
Rajaasim1980 said:
KNOX is a new security system in official update of Android 4.3
on Samsung devices which prevents access to multiple applications when rooting your device and prevents the flash counter being reset to 0
Click to expand...
Click to collapse
theq86 said:
As you may already know, the latest Samsung firmwares came with a new secured bootloader. You can recognize it in download mode easily. It states: Knox warranty void: 0x0 or 0x1.
As for now, there is no way to reset that flag from 0x1 to 0x0.
Then I read in a comment of Chainfires post concerning that flag, that as long as you do not try to downgrade to a non secured bootloader, this flag will not change. He claims to have that information directly from Samsung.
https://plus.google.com/u/0/+Chainfire/posts
Has anyone already experience with rooting an "untouched" S4 which has the secured bootloader and can confirm or decline that?
- - - - - - - - - -
Conclusions and Facts about KNOX-enabled firmwares (based on statements from chainfires post and it's comments above, ans based on this thread)
Not possible to downgrade to KNOX-disabled firmwares/bootloaders (An attempt sets 0x1) (even though some people state, downgrade is possible when omitting the bootloader file in a firmware package: see http://forum.xda-developers.com/showthread.php?t=2444671, not confirmed)
Even if you flash a KNOX-enabled firmware via odin (e.g. the latest fw) knox will be set to 0x1
Flashing unsigned or modified images via odin will set knox to 0x1
Samsung stated, resetting the flag is impossible
KNOX is mandatory and can not be completely removed
Warranty Void is no counter, it is a flag (0,1) it was never seen 0x2 or so
Mirroring all partitions from a clean 0x0-Device to a 0x1-Device via JTAG produces an unfunctional device (reversible by restoring the 0x1 partitions on the phone)
KNOX bootloader verifies signatures of kernels and recoveries. No custom ones possible without voiding the knox warranty
Assumptions on how KNOX flag in bootloader works:
Some experts think, an eFuse is involved. (http://en.wikipedia.org/wiki/EFUSE). An eFuse is mostly only incremential. Even unwriteable by low level tools or JTAG. But it is still not proven, that eFuse is used.
Knox technical information:
https://www.samsungknox.com/overview/technical-details
Click to expand...
Click to collapse
2: Can i downgrade the bootloader?
cosmyndemeter said:
from mj5 bootloader downgrade is possible, read this for newest than mj5 downgrade not possible!
do not try! you can brick your phone forever!!!
Click to expand...
Click to collapse
3:Can i install custom roms?
DeepankarS said:
You can do any customization on your phone like a normal phone, but customizing it means that you have triggered the KNOX counter to 1. Thus on a stock rom you can never use KNOX if KNOX reads 1.
FYI the MK4 (bootloader) or MJ9 (babseband version) has blocked installation of any custom roms on our n7100s via odin. You cannot even downgrade to 4.1.2 official via odin, So flashing via recoveries is the only way left.
And also it is recommended that you install custom roms via Philz/TWRP/CWM recoveries to flash custom roms and everything.
Hope the lil knowledge helped.
Click to expand...
Click to collapse
4 Can i root my note 2 with 4.3 knox?
Yes, but there are chances to trigger the KNOX counter to 1
yeminswe said:
4.3 root
http://forum.xda-developers.com/showthread.php?t=2540761
http://forum.xda-developers.com/showthread.php?t=2573576
>D
Click to expand...
Click to collapse
If you see any questions about knox, post here we will answer.
number 1 link is error,not found.
what about knox container ?
sora9009 said:
number 1 link is error,not found.
what about knox container ?
Click to expand...
Click to collapse
Link fixed.
Thanks
What about kernels?
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.
Irwenzhao said:
What about kernels?
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.
Click to expand...
Click to collapse
KNOX bootloader verifies signatures of kernels and recoveries. No custom ones possible without voiding the knox warranty
Is there any way to get the knox back to 0 from 0x1????
Sent from my GT-I9500 using Tapatalk 4 - Hassan K. Malik
HassanM said:
Is there any way to get the knox back to 0 from 0x1????
Sent from my GT-I9500 using Tapatalk 4 - Hassan K. Malik
Click to expand...
Click to collapse
Not yet,although note 3 has been reported to somehow reverse it but that's just wishing too much.
singhpratik87 said:
Not yet,although note 3 has been reported to somehow reverse it but that's just wishing too much.
Click to expand...
Click to collapse
On the note 3 it's done by special bootloader leaked by sammy. The only chance for the note 2 is if note 2 bootloader is leaked. No other way.
Sent from my GT-N7100
I dont care about warranty , all i care that , if i installed a custom rom and the Knox bit is set to 0X1 and i want to get back to the stock , can i install Knox again or not ? because i like the knox idea
hazemsalah said:
I dont care about warranty , all i care that , if i installed a custom rom and the Knox bit is set to 0X1 and i want to get back to the stock , can i install Knox again or not ? because i like the knox idea
Click to expand...
Click to collapse
Once your counter goes to 1 no more Knox app , it can't be used anymore.
Sent from my GT-N7100
gregsarg post :
We have a fix....just not on xda....yet
Mobiletechvideos.com now offers a bootloader downgrade service for our devices. ..
The Knox flags can be reset quite easily according to them....
So if you want the old Knox free phone back....see below and get your anti-knox groove on....
See the product description tab in the middle of the page. ..g
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-2-bootloader-sboot-downgrade-service/
Hmmm it's kinda fishy , but could be true. So you send them your phone ? I don't get it. And all around is jtag heh
Sent from my GT-N7100
note2nooby said:
Hmmm it's kinda fishy , but could be true. So you send them your phone ? I don't get it. And all around is jtag heh
Sent from my GT-N7100
Click to expand...
Click to collapse
Nope i can't risk to send my phone (400 euro), but it looks like they have the solution.I send them mail to ask if i can pay for the file and instruvtions but no answer till now.They want 75 for the reset and 45 for express shipping end delivery.I told them that i am
agree to pay all the ammount for the file.
And one more thing-if i send them phone i can't be sure that they will reset it instead of just replacing MB and write my old IMEI e.t.c
gencho81 said:
Nope i can't risk to send my phone (400 euro), but it looks like they have the solution.I send them mail to ask if i can pay for the file and instruvtions but no answer till now.They want 75 for the reset and 45 for express shipping end delivery.I told them that i am
agree to pay all the ammount for the file.
And one more thing-if i send them phone i can't be sure that they will reset it instead of just replacing MB and write my old IMEI e.t.c
Click to expand...
Click to collapse
I'm quite sure they are using jtag and service bootloader. That's why they need the phone. It's not the same way like the exynos fix for note 3.
Sent from my GT-N7100
I-9192 official status again
i have installed a few weeks later a rooted rom from another forum, and triggered the knox to 0x01 (so i cant receive official updates from samsung)
but, today i needed to reset my phone to factory default, than i was curious to check the phone status, and for my surprise was "Official" again...
i read in various sites that the knox flag cannot be reverted... is that true?
the files i was used to root:
Odin 3.09
Kernel_root_I9192.tar
SuperSU_1.41.zip
the only bad thing is that i lost my root
anyone have the same result just reseting the phone?
thx and sorry for bad english
Soooo. As far as i know the knox wont get updates from Samsung and Block using knox app? And what features are lost from a triggered knox? I flashed the original firmware again and all its ok so far. Theres any blocked feature that o didnt realize?
Need help
I've a s4mini 19192 and today I flashed samsungs official KitKat update to my phone... I tried to root it like I rooted the 4.2.2 update... But can't do.... Then I decided to downgrade to the old version 4.2.2 but odin says can't.... And fails... Someone can help me?
Is it possible to check when the flag was triggered?
I was sold a GN3, in witch the KNOX flag was already set* and I'm trying to avoid a situation in witch the seller will say that I've set the flag.
* not checked beforehand - my mistake - but still I can return it or get a discount under the law
hello..just got the s4 mini dual sim 9192... 2 days back..i was on 4.2.2 indian firmware....checked download mode and it said knox 0*0...now i flashed the 4.4.2 firmware downloaded from sammobile via odin and when i recheck knox is gone....!!!!
just said binary and system which changed from official to custom once i rooted it with CF-root method(nothing else was working...saferoot/towelroot etc)..and as i seem to have read that flashing stock rom reverts these back to official...is it true?
and does this mean that my knox firmware phone has been converted to a non-knox one after kit kat upgrade?
please anyone let me know..thanks
@Fataz bro i have a few questions
I'm currently on FNE2 stock deodexded custom rom with a FNE2 bootloader, when i go download mode it says "KNOX WARRANTY VOID:1"
1 - Does this means Knox is tripped as 0x1
2- Can i install a stock firmware higher than FNE2 from sammobile via odin
GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi
hello i have a question ive boughed a galaxy note 8 a last week and stuped me updated to 4.4.2 and im not new to samsung device i had one my self and rooted not even(for my friends) one but never had such situasion but i still got warranty and i dont want to lose it i know there is knox on my device now and if i root with vroot my system status will change to custom and will not touch knox so my question is when ill root and use triangle away and send my note to samsung after theyll format it will the system status stay official or go back to custom?
the_ziom said:
hello i have a question ive boughed a galaxy note 8 a last week and stuped me updated to 4.4.2 and im not new to samsung device i had one my self and rooted not even(for my friends) one but never had such situasion but i still got warranty and i dont want to lose it i know there is knox on my device now and if i root with vroot my system status will change to custom and will not touch knox so my question is when ill root and use triangle away and send my note to samsung after theyll format it will the system status stay official or go back to custom?
Click to expand...
Click to collapse
TriangleAway still works with the KitKat KNOX enabled bootloader but the counter it resets is not the KNOX warranty flag. If you've flashed any unsigned (by Samsung) image to your tablet, including custom recoveries, kernels and/or ROM's, or rooted with CF Auto Root (which flashes a custom recovery) since upgrading to KitKat 4.4.2, your KNOX flag has been triggered and your warranty is already voided.
ramjet73
ramjet73 said:
TriangleAway still works with the KitKat KNOX enabled bootloader but the counter it resets is not the KNOX warranty flag. If you've flashed any unsigned (by Samsung) image to your tablet, including custom recoveries, kernels and/or ROM's, or rooted with CF Auto Root (which flashes a custom recovery) since upgrading to KitKat 4.4.2, your KNOX flag has been triggered and your warranty is already voided.
ramjet73
Click to expand...
Click to collapse
No you dont get my question im aware of knox and I dont want to touch it but I head that rooting changes the system status to custom in download modeand in system it changes to modified and if samsung see tht than the warranty if void so once again my question is when I root with vroot or with kingo root they both dont touch knox and than use triangle away and SET system status back to official or normal and after formating will the official or normal status stay of will it be turned back to custom/modified
the_ziom said:
No you dont get my question im aware of knox and I dont want to touch it but I head that rooting changes the system status to custom in download modeand in system it changes to modified and if samsung see tht than the warranty if void so once again my question is when I root with vroot or with kingo root they both dont touch knox and than use triangle away and SET system status back to official or normal and after formating will the official or normal status stay of will it be turned back to custom/modified
Click to expand...
Click to collapse
I haven't used either of those rooting methods so I can't answer that. According to the Kingo website the chances of tripping the KNOX flag are 1 in 1000, but they don't mention the flash counter. OTOH, Samsung claims that KNOX can be tripped with as little as a custom kernel initialization script:
For example, some KNOX security mechanisms, such as SE for Android, will trigger an e-fuse if the system is booted with an arbitrary kernel, kernel initialization script or data, and therefore be disabled and no longer function correctly.
Click to expand...
Click to collapse
I know you said that you're not asking about the KNOX implications but maybe you should. Regarding resetting the flash counter and custom configuration with TriangleAway, I suggest posting your scenario in that thread and hope for a response from Chainfire, the developer of that app. If you can root with one of those methods without tripping Knox, my experience is that after using Odin to flash the stock ROM and running TriangleAway when I was using the 4.2 ROM and bootloader there was no indication on the bootloader screen or using the stock ROM that "tampering" was detected, but things might have changed with the 4.4 bootloader.
Good luck, and please let us know how it turns out.
ramjet73
ramjet73 said:
I haven't used either of those rooting methods so I can't answer that. According to the Kingo website the chances of tripping the KNOX flag are 1 in 1000, but they don't mention the flash counter. OTOH, Samsung claims that KNOX can be tripped with as little as a custom kernel initialization script:
I know you said that you're not asking about the KNOX implications but maybe you should. Regarding resetting the flash counter and custom configuration with TriangleAway, I suggest posting your scenario in that thread and hope for a response from Chainfire, the developer of that app. If you can root with one of those methods without tripping Knox, my experience is that after using Odin to flash the stock ROM and running TriangleAway when I was using the 4.2 ROM and bootloader there was no indication on the bootloader screen or using the stock ROM that "tampering" was detected, but things might have changed with the 4.4 bootloader.
Good luck, and please let us know how it turns out.
ramjet73
Click to expand...
Click to collapse
Well non of those methods worked I had to root via odin so bye bye warranty
I just got my new S4 recently and I took the 4.4.4 update that was avaliable for it. I have been reading on here for hours about how if you root it/upload custom boot loader it'll trip knox.
Could someone answer me a few questions. I would really appreciate it!
Does knox matter if you don't have a warranty etc?
Is there a way to go ahead and root 4.4.4/NH7 without tripping knox or at all?
Also, is there custom boot loaders and all that for this update as well?
1) nope.. only if it still has Samsung warranty
2) not at the moment
3) no, they are not needed
Someone reset Knox on note 3 exynos.......
NOOB alert!
Please forgive me in advance if this question is totally off the mark.
I've been using Fenny's 4.4.2 ROM for a while, under the impression that it is MDL based and I'd still be able to flash back to stock 4.2 if needed, and set the flash count back to 0 -- i.e. keep the warranty.
If I'm totally wrong and my warranty is already voided, can any of you let me know? I can then begin playing with custom roms to my heart's content!
If I was right ... anyway to enjoy any 4.4.4 ROM without voiding the warranty (i.e. with the ability to move back to something which will not have tripped the switch)? If yes, where can I find that info, or can you post detailed instructions?
[I've read that if I switch to MK2 there is no way to keep the warranty if I root. That true? I see many roms claiming to have removes knox ... does that help? ]
I thank you in advance for bearing with me.
It all depends which boot loader your phone has.
If your phone was on the 4.2 MDL firmware, it has no Knox counter active, and you can flash away without making any permanent changes. Note, the firmware on the phone isn't the same as the ROM... for example, I'm using a 4.4.4 ROM (Dirty Unicorns) on my phone which still has the 4.2 MDL firmware. So, if I wanted to, I could return it to stock and there would be no sign it ever was used in a nonstandard way.
However, any newer firmware version on the phone has the Knox counter that gets permanently, irreversibly tripped if you flash a nonstandard recovery (such as the TWRP or CWM most of us use). So, in these phones, there's no way to play with ROMs without making irreversible changes.
Marc