Hello, after a search on these forums I could not find any topic about my specific problem so here goes.
I purchased a secondhand P605.
When I checked the Knox trigger it said 0x1, which made me wonder if anyone tried to root it before. It is not rooted at the moment, and I am unable to root it because Knox prevents it. I did update it to Lollipop.
So, I took to the Web and tried to disable Knox. This seems impossible, due to the fact that I don't even have permission to enter the Knox container!
Does anyone have any idea how to disable Knox when one doesn't have access to Knox at all?
Thanks in advance.
Airethilien said:
Hello, after a search on these forums I could not find any topic about my specific problem so here goes.
I purchased a secondhand P605.
When I checked the Knox trigger it said 0x1, which made me wonder if anyone tried to root it before. It is not rooted at the moment, and I am unable to root it because Knox prevents it. I did update it to Lollipop.
So, I took to the Web and tried to disable Knox. This seems impossible, due to the fact that I don't even have permission to enter the Knox container!
Does anyone have any idea how to disable Knox when one doesn't have access to Knox at all?
Thanks in advance.
Click to expand...
Click to collapse
If you updated to 5.1.1 then you need a modded kernel to root. Install TWRP, then flash new kernel and then flash supersu.
Your P605has definitely been modified either with a kernel or recovery, that's why you have Knox trigger 0x1.
Will try that , thank you.
Related
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.
I've had my I9192 for about 2 months. I updated it right after receiving it, and rooted it using Kingo. Everything was working great until I received the software update. I installed the update a couple of days ago and lost root. I tried Kingo again, but I'm getting the Samsung Security (knox) message that it was blocking it. Even though I never installed Knox, it must be running in the background.
I've done some reading since on Kingo, Knox, and updating while rooting. I have now come to the realization that my warranty is probably void, my phone will no longer get official updates, and there is no Santa Claus.
In researching the problem, I found some reference to download mode. and the Knox Kernel lock. When I start my phone in download mode, this is what it shows:
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0 (I think this and the next one are good)
Knox Warranty Void: 0x0
CSB-Config-LSB: 0x30 (I don't know what this is)
Write Protection: Enabled
Can anyone confirm my assumptions? I just want to get back to my original state before updating a few days ago. Original FW with root capability. I'm ok with resetting the phone and reinstalling if necessary.
If I screwed the pooch on this one, then I guess it's time to go CFW route to get to root.
Thanks for any input.
Once you got a fw with Knox you can't go back.
And yes, 0x0 is good but if you flash a kernel for root you will get 0x1..
Sent from my GT-I9195 using xda app-developers app
mnezo said:
Once you got a fw with Knox you can't go back.
And yes, 0x0 is good but if you flash a kernel for root you will get 0x1..
Sent from my GT-I9195 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the input. Since, I am at 0x0, will I still get fw updates?
As I mentioned, I thought you had to be a 0x1 to be excluded from official updates. Or does the fact the System Status is now Custom, exclude me from those updates?
Snotick said:
Thanks for the input. Since, I am at 0x0, will I still get fw updates?
As I mentioned, I thought you had to be a 0x1 to be excluded from official updates. Or does the fact the System Status is now Custom, exclude me from those updates?
Click to expand...
Click to collapse
Yes. As your System Status is now set to Custom then you can not receive official updates by OTA.
GeoDum said:
Yes. As your System Status is now set to Custom then you can not receive official updates by OTA.
Click to expand...
Click to collapse
Thanks.
I'm still reading conflicting reports about how Samsung is handling all of this. You say I won't receive official updates OTA. Will I be able to side load them via Kies?
I'm also confused about the Knox security. It seems like it is more for people that want to use their phones for work. I don't, and am 99% certain that I never will. Should I even care what my Knox count is?
Snotick said:
Thanks.
I'm still reading conflicting reports about how Samsung is handling all of this. You say I won't receive official updates OTA. Will I be able to side load them via Kies?
I'm also confused about the Knox security. It seems like it is more for people that want to use their phones for work. I don't, and am 99% certain that I never will. Should I even care what my Knox count is?
Click to expand...
Click to collapse
In some countries Knox warranty 0x1 = Void warranty So yes sometimes u should care about Knox
Read more here
SilviuMik said:
In some countries Knox warranty 0x1 = Void warranty So yes sometimes u should care about Knox
Read more here
Click to expand...
Click to collapse
Sorry, I should have mentioned that I am in the U.S.
At this point, I would trade my warranty for a rooted phone running stock fw going forward. As it stands now, I can't root (at least not the with one click) and I won't be updating fw going forward. Seems like a double whammy.
Snotick said:
I've had my I9192 for about 2 months. I updated it right after receiving it, and rooted it using Kingo. Everything was working great until I received the software update. I installed the update a couple of days ago and lost root. I tried Kingo again, but I'm getting the Samsung Security (knox) message that it was blocking it. Even though I never installed Knox, it must be running in the background.
I've done some reading since on Kingo, Knox, and updating while rooting. I have now come to the realization that my warranty is probably void, my phone will no longer get official updates, and there is no Santa Claus.
In researching the problem, I found some reference to download mode. and the Knox Kernel lock. When I start my phone in download mode, this is what it shows:
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0 (I think this and the next one are good)
Knox Warranty Void: 0x0
CSB-Config-LSB: 0x30 (I don't know what this is)
Write Protection: Enabled
Can anyone confirm my assumptions? I just want to get back to my original state before updating a few days ago. Original FW with root capability. I'm ok with resetting the phone and reinstalling if necessary.
If I screwed the pooch on this one, then I guess it's time to go CFW route to get to root.
Thanks for any input.
Click to expand...
Click to collapse
Hi man many Questions but i think i can help you.
If made nearly the same like you the only differnce i flash the new upadte by my self via Odin.
So lets start step by Step:
1. You can go back to your old Firmeware with root is possible as befor! For that you must search your Firmeware via I-net and flash them via Odin like me. No changes on the Knox flag
2. That Custom stat: Yes you will be able to get OTA by me it Works. You can emulated the Offical state via Wanam Xposed and it will show you too as Offical in the Download mod.
3. Warranty is still in place
Look at my Post on a other Thread: littel Guide from me
There i explain what you must do to get back to your older Firmeware
Happy new Year for you all
Greets
Killer
I've noticed that there's been some discussion about the new knox bootloader in regards to rooting our device. Now, when I boot my I9505 into download mode I get this wall of text in the upper left corner telling me "knox warranty void 0x1 blah blah" and likewise when I boot into recovery captain obvious knox pops up in the corner reminding me that I'm running a custom recovery.
Now that I have rooted my tablet and flashed TWRP via Odin I have yet to see a single sign of that infamous knox flag. Download mode - nothing, recovery boot - nothing... nothing except my settings telling me my device status is custom, and even that can be spoofed via Wanam Xposed.
Am I missing something or is the knox bootloader simply not present in my firmware version? (XXUBMJ6 NEE/nordic countries)
Also, has anyone had success using TriangleAway on the P600 to reset the flash counter? Not that I currently need it, just curious..
Sent from my SM-P600 using XDA Premium HD app
TWRP?
Andmoreagain said:
I've noticed that there's been some discussion about the new knox bootloader in regards to rooting our device. Now, when I boot my I9505 into download mode I get this wall of text in the upper left corner telling me "knox warranty void 0x1 blah blah" and likewise when I boot into recovery captain obvious knox pops up in the corner reminding me that I'm running a custom recovery.
Now that I have rooted my tablet and flashed TWRP via Odin I have yet to see a single sign of that infamous knox flag. Download mode - nothing, recovery boot - nothing... nothing except my settings telling me my device status is custom, and even that can be spoofed via Wanam Xposed.
Am I missing something or is the knox bootloader simply not present in my firmware version? (XXUBMJ6 NEE/nordic countries)
Also, has anyone had success using TriangleAway on the P600 to reset the flash counter? Not that I currently need it, just curious..
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
hi. I want to know how you flashed TWRP for P600 as i cant find the file anywhere on the internet. . I rooted it using a stock recovery. I froze the knoxx apps as they were interfering with my root and giving notifications on a security threat. Please any help with TWRP i cant find it.
ahsenrauf said:
hi. I want to know how you flashed TWRP for P600 as i cant find the file anywhere on the internet. . I rooted it using a stock recovery. I froze the knoxx apps as they were interfering with my root and giving notifications on a security threat. Please any help with TWRP i cant find it.
Click to expand...
Click to collapse
Here, download the .tar file 2.6.3.3 & flash via odin
http://goo.im/devs/OpenRecovery/lt03wifiue
There is a big discussion about this in a german forum is use:
http://www.pocketpc.ch/samsung-gala...278-anleitung-root-fuer-note-10-1-2014-a.html
It's weird that the p600 does not have the same download mode display as the p605. It says nothing about knox on the p600 download mode. So the guys on the other forum are confident that triangle away should work to reset the counter on p600 because it's not a knox flag. But as far as I know Triangle Away does not support the note 10.1 2014 yet. So I guess we have to wait and see
clouds5 said:
It's weird that the p600 does not have the same download mode display as the p605...
Click to expand...
Click to collapse
Strange, strange... because first I got this. See: http://forum.xda-developers.com/showthread.php?t=2538464
But now the text in the left corner is missing. Maybe because I use the wanam tweck? This means that there is - maybe - no hardware flag
PS. Also when I open the system update in the settings, I didn't get any longer a warning that the update is blocked?! I got it in the beginning...
clouds5 said:
There is a big discussion about this in a german forum is use:
http://www.pocketpc.ch/samsung-gala...278-anleitung-root-fuer-note-10-1-2014-a.html
It's weird that the p600 does not have the same download mode display as the p605. It says nothing about knox on the p600 download mode. So the guys on the other forum are confident that triangle away should work to reset the counter on p600 because it's not a knox flag. But as far as I know Triangle Away does not support the note 10.1 2014 yet. So I guess we have to wait and see
Click to expand...
Click to collapse
Thanks for the reply and the link.
A "warranty void etc." message has popped up in download mode as of now but you're right, it says nothing about knox whatsoever, and the strange part is is that it didn't appear until I actually flashed a mod via recovery and wiped cache/dalvik. Before that there was no message in the corner, even though I had already flashed cf-root and TWRP via Odin.
Elim said:
Also when I open the system update in the settings, I didn't get any longer a warning that the update is blocked?! I got it in the beginning...
Click to expand...
Click to collapse
Same here. Even though there were no updates available at the time I last checked I got no warning message.
Maybe the P600 just has less security implementations than the other versions for whatever reason...
''Knox warranty void 0x1'' is the KNOX FLAG. It means that you cannot use the secure Knox container, and you will not get OTA update. Of course you can download and install new software updates.
shayind4 said:
''Knox warranty void 0x1'' is the KNOX FLAG. It means that you cannot use the secure Knox container, and you will not get OTA update. Of course you can download and install new software updates.
Click to expand...
Click to collapse
No warranty too, though, sadly...
shayind4 said:
''Knox warranty void 0x1'' is the KNOX FLAG. It means that you cannot use the secure Knox container, and you will not get OTA update. Of course you can download and install new software updates.
Click to expand...
Click to collapse
Yes, but it does not say anything about "KNOX" or "0x1" when I enter Download Mode. I should also correct what I said in my previous post. It doesn't say "Warranty Void" but rather "Warranty Bit: 1".
ODIN MODE
PRODUCT NAME: SM-P600
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
WARRANTY BIT: 1
This is identical to how it used to be on the old 4.2.2 non-knox bootloaders and it's NOT the Knox flag. It's the binary counter.
Andmoreagain said:
Yes, but it does not say anything about "KNOX" or "0x1" when I enter Download Mode. I should also correct what I said in my previous post. It doesn't say "Warranty Void" but rather "Warranty Bit: 1".
ODIN MODE
PRODUCT NAME: SM-P600
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
WARRANTY BIT: 1
This is identical to how it used to be on the old 4.2.2 non-knox bootloaders and it's NOT the Knox flag. It's the binary counter.
Click to expand...
Click to collapse
I have SM-P605. I think Knox bootloader is present from 4.3 onward. If SM-P600 has Knox app in the apps drawer and Knox security apps under Application manager then it's likely to have a Knox bootloader Tripping the Knox flag means the Knox container can never be accessed or used again but the phone/tablet itself is OK for regular use. I have not come across a phone/tablet with Knox apps and non-Knox bootloader.
Knox has been mentioned in this SM-P600 thread: http://forum.xda-developers.com/showthread.php?t=2618509
shayind4 said:
I have SM-P605. I think Knox bootloader is present from 4.3 onward. If SM-P600 has Knox app in the apps drawer and Knox security apps under Application manager then it's likely to have a Knox bootloader Tripping the Knox flag means the Knox container can never be accessed or used again but the phone/tablet itself is OK for regular use. I have not come across a phone/tablet with Knox apps and non-Knox bootloader.
Knox has been mentioned in this SM-P600 thread: http://forum.xda-developers.com/showthread.php?t=2618509
Click to expand...
Click to collapse
Whether a Knox bootloader is present in the P600 or not, then at least the flag is not visible in download mode or during boot. Either way I'm satisfied as long as I don't have to be reminded every day that my tablet is running an unofficial kernel and recovery.
Andmoreagain said:
Whether a Knox bootloader is present in the P600 or not, then at least the flag is not visible in download mode or during boot. Either way I'm satisfied as long as I don't have to be reminded every day that my tablet is running an unofficial kernel and recovery.
Click to expand...
Click to collapse
So who turns their tablet off? Mine runs 24/7...
Help!!!!
I think I made the half brick from the P605.
The message SECURE CHECK FAIL: recovery - appiar when trying to use ODIN. (custom recovery)
The REACTIVATION LOCK is ON . How to avoid it????
Please help!
Thanks a lot!
So i have a Galaxy s4 mini with sprint as my carrier. I'm currently trying to root it via Kingo root app but the problem is that everytime i try, the end result is NeedRoot. I checked my phone and apparently the problem is that everytime I try to root, i get a little shield on my phone saying "Security notice" once it's clicked it states " An attempt to access a secure area on your phone without authorization has been blocked. Make sure your phone is protected by updating the security policy to the latest version from samsung". So how do I remove this policy problem? I just want to root my S4 Mini. Any help/advice is great help, thank you!
No one has an answer?
irvinavitia said:
No one has an answer?
Click to expand...
Click to collapse
If you took all the updates and are on NA7, no. As far as I know we need ODIN/Kies to root now. Ideally, we wouldn't have have taken the update that made Knox an issue. Someone would have dumped update, broken it apart and gave us a zip to flash everything but the bootloader so we wouldn't have these issues.
I believe you will find the answer to your question here ...
Rooting SPH-L520 Under KNOX?
http://forum.xda-developers.com/showthread.php?t=2676255
mdawdy said:
I believe you will find the answer to your question here ...
Rooting SPH-L520 Under KNOX?
http://forum.xda-developers.com/showthread.php?t=2676255
Click to expand...
Click to collapse
Did you notice who posted last on there?
Hi i have a s4 mini gti9195i with knox rooted by kingo root apk
how can i change from kingo's superuser to supersu from chainfire? The update of the binary fails.
Not fast but 100% good way:
1. Flash stock firmware with odin (remove kingoroot and all it's trash).
2. Use CF-Auto-root or (if you plan to use custom roms) flash custom recovery.
Notice:
CF-Auto-root probably will trip knox flag when trying to disable knox security.
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