Related
hi
I have a challenge with my N9005. It does a reboot, then when I enter the password to login it hangs for a few seconds, and reboots again. When I take take the battery out for a while I'm able to now login. but at this point it says "deleting KNOX". I realise that all my applications are nowhere to be found. Google PlayStore too is off. Bottomline is, there is nothing on the fone at this point; not even the Samsung and Google Folders. Its happend 4 times within the last month.
Please help. Thanks
TeddyLu said:
hi
I have a challenge with my N9005. It does a reboot, then when I enter the password to login it hangs for a few seconds, and reboots again. When I take take the battery out for a while I'm able to now login. but at this point it says "deleting KNOX". I realise that all my applications are nowhere to be found. Google PlayStore too is off. Bottomline is, there is nothing on the fone at this point; not even the Samsung and Google Folders. Its happend 4 times within the last month.
Please help. Thanks
Click to expand...
Click to collapse
Were u using Knox before ? If u were using Knox all ur data are encrypted inside Knox. The problem arose when Knox container damaged (Knox 0x1). If that is what happened then ur Knox data is surely be gone.
nlatifolia said:
Were u using Knox before ? If u were using Knox all ur data are encrypted inside Knox. The problem arose when Knox container damaged (Knox 0x1). If that is what happened then ur Knox data is surely be gone.
Click to expand...
Click to collapse
I hadnt moved any of the data to KNOX. I hardly even use KNOX, though its installed and set up. Is there a solution to the KNOX container getting damaged so often? an update or something available?
Thanks.
TeddyLu said:
I hadnt moved any of the data to KNOX. I hardly even use KNOX, though its installed and set up. Is there a solution to the KNOX container getting damaged so often? an update or something available?
Thanks.
Click to expand...
Click to collapse
I dont know whats going on to ur phone but it seems that Knox has broken. Check via download mode VolDown-Home-Power at the same time whether Knox values is 0x1 or still 0x0..
nlatifolia said:
I dont know whats going on to ur phone but it seems that Knox has broken. Check via download mode VolDown-Home-Power at the same time whether Knox values is 0x1 or still 0x0..
Click to expand...
Click to collapse
It's still 0x0
Reflash your Stock ROM, If your KNOX is 0x0 still all it'll do is repair any damage to the system files and restore it.
So I recently installed a custom kernel so I could change my SELinux status to Permissive to use NTFS mount, and now I just realized I lost private mode. Installing a stock kernel should give that back to me, as Knox will no longer be tripped.
Can anyone help me with the stock kernel? Data is expensive where I live, so downloading the stock firmware isn't really an option, but I know the kernel should be rather small.
Please help! Thank you!
Not going to work the way you seem to think. If you installed a custom kernel, you would have incremented your Knox flag to 0x1. Reverting to a stock kernel will not reset the Knox flag, so barring any unexpected advances regarding Knox, you won't be getting your private mode back unless you explicitly saved your private mode container encryption keys in advance.
As to the stock kernel, if you still need it, it will vary by firmware version /carrrier and you didn't even provide that basic information about your phone. Search the forum to see if anyone has posted the extracted version of kernel that you need. If not, then download the stock firmware to your PC (since you don't want to pay for mobile data) and use winrar to extract it.
.
Thanks for the reply. Didn't know it was carrier based to be honest. As for the Knox flag, I don't mean the warranty counter in download mode. That's been gone long ago. I merely mean the software Knox "we have detected unauthorized actions" messages. Soon as that tripped, no more private mode. But I know flashing the stock kernel should solve it. Regardless, I've searched the forum, all I can find is either the full firmware which I'm now biting the bullet and getting, or custom kernels which got me into this mess. I could remove the message by using wanam or even supersu to remove Knox all together, but my end game is to get private mode back.
Reverting to the stock kernel will remove the "we have detected unauthorized actions" message. It will not reset the Knox flag, nor restore access to your private mode. Note that the Knox flag is different from the flash counter.
.
So the only way to reset the Knox flag is via reflashing stock rom? Because that's how I got private mode back last time. As I said, my Knox flag in download mode has been 0x1 for a very long time, and private mode worked fine.
HrBingR said:
So the only way to reset the Knox flag is via reflashing stock rom? Because that's how I got private mode back last time. As I said, my Knox flag in download mode has been 0x1 for a very long time, and private mode worked fine.
Click to expand...
Click to collapse
The only way that I know of to restore private mode with an incremented Knox flag (0x1) is if you have saved the container encryption keys. I can only assume that you do have the keys extant on your device. Based on your previous experience, then do as you did before. Which is to say that restoring the full firmware (or perhaps even just stock kernel) should give you private mode back on the assumption that your keys are present in /userdata. As compared to someone who no longer has the keys and cannot regain private mode with a 0x1 flag period.
If somehow you don't have the keys and can re-enable private mode with a 0x1 flag, we'd like to know how. But for the moment, we'll just assume that you have the keys on your handset and doing as you did before will restore private mode in your case.
.
fffft said:
The only way that I know of to restore private mode with an incremented Knox flag (0x1) is if you have saved the container encryption keys. I can only assume that you do have the keys extant on your device. Based on your previous experience, then do as you did before. Which is to say that restoring the full firmware (or perhaps even just stock kernel) should give you private mode back on the assumption that your keys are present in /userdata. As compared to someone who no longer has the keys and cannot regain private mode with a 0x1 flag period.
If somehow you don't have the keys and can re-enable private mode with a 0x1 flag, we'd like to know how. But for the moment, we'll just assume that you have the keys on your handset and doing as you did before will restore private mode in your case.
.
Click to expand...
Click to collapse
I'm not even sure what keys you're talking about? I was on cm, loaded up Odin and flashed my phone, wiped data and private mode worked. It's always worked except in cases with custom kernels and where Knox was removed o disabled. I've never backed up any keys for Knox in user data at all, and my warranty flag is 0x1. Has been for ages. The only time I've seen private mode not work is if software Knox is tripped/removed. For example, I'd install stock rom and use towelroot to root and private mode worked great. I've never done anything to backup Knox encryption keys.
Thanks for all the help mate.
I tried to root with towelroot=not support?:crying:
I tryied vroot and it support,no dare to click, will it trip knox?
Others like geniusroot,kingo root support n trip knox?
Any chances to root without trip knox?
Thank you.
Hello.
I had rooted my Galaxy S4 (i9505), 4.4.2, without triggering the Knox Flag, using CF-Auto-Root, via Odin. The Flash Counter is now 1, due to flashing something, but Knox is 0x0. Flash counter can be reseted by using Triangle Away,
Hope this helps.
http://forum.xda-developers.com/showthread.php?t=2292615
Proof:
https://www.dropbox.com/s/mkjnmpwcq6pz2se/DSC_3831.JPG?dl=0
(no 0x1 flag)
https://www.dropbox.com/s/gctx9ejiin47rrp/Screenshot 2014-10-04 17.08.39.png?dl=0
(device supported by Kies)
https://www.dropbox.com/s/v8hpbmo815ltn1w/2014-10-04 14.09.39.png?dl=0
(SuperUser working)
Mind that you have to install BusyBox from Google Play, cause it does not come with it.
Have fun
costin96 said:
Hello.
I had rooted my Galaxy S4 (i9505), 4.4.2, without triggering the Knox Flag, using CF-Auto-Root, via Odin. The Flash Counter is now 1, due to flashing something, but Knox is 0x0. Flash counter can be reseted by using Triangle Away,
Hope this helps.
http://forum.xda-developers.com/showthread.php?t=2292615
Proof:
https://www.dropbox.com/s/mkjnmpwcq6pz2se/DSC_3831.JPG?dl=0
(no 0x1 flag)
https://www.dropbox.com/s/gctx9ejiin47rrp/Screenshot 2014-10-04 17.08.39.png?dl=0
(device supported by Kies)
https://www.dropbox.com/s/v8hpbmo815ltn1w/2014-10-04 14.09.39.png?dl=0
(SuperUser working)
Mind that you have to install BusyBox from Google Play, cause it does not come with it.
Have fun
Click to expand...
Click to collapse
Thanks to you.Still can not root at the moment fir I9500
Not included - Triangle Away - ! NOT OPERATIONAL ON THE GT-I9500 !
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)
ttkyy said:
Thanks to you
Click to expand...
Click to collapse
Bear in mind, that I am not 100% sure that it will work on ALL Galaxy S4 devices (I mean not trigger it).
Also bear in mind that OTA (Over the air update) will NOT work, it will return the message "Phone was been personalized."
Although, Kies sees it. Also make sure you don't have Knox mode activated or installed.
LATER EDIT:
I see that Triangle Away is only for the Qualcomm Galaxy S4 (9505). That means that you can't, at this moment, reset the flash counter. There are basically two things to worry about:
- Knox Flag -> as which seems so, I avoided it by installing that CF-Auto-Root on my 9505. I am not sure about avoiding it on 9500, but it should work.
- Flash Counter -> it raises everything you flash something via download mode. If it's 0, in Settings > About Phone > Status >Phone Status, it will return "Original" or something. If it's anything else than 0 (like 1, which I currently have cause I re-flashed root due to some tiny problem), it will return "personalized" or something like it. That will still void warranty IF the phone is sent to warranty like that, but will NOT trigger Knox. Also that will stop OTA Updates from working, but Kies updates will work (for some reason, samsung bug, use it ).
I have no idea how to help you regarding that Flash Counter on the 9500.
costin96 said:
Bear in mind, that I am not 100% sure that it will work on ALL Galaxy S4 devices (I mean not trigger it).
Also bear in mind that OTA (Over the air update) will NOT work, it will return the message "Phone was been personalized."
Although, Kies sees it. Also make sure you don't have Knox mode activated or installed.
LATER EDIT:
I see that Triangle Away is only for the Qualcomm Galaxy S4 (9505). That means that you can't, at this moment, reset the flash counter. There are basically two things to worry about:
- Knox Flag -> as which seems so, I avoided it by installing that CF-Auto-Root on my 9505. I am not sure about avoiding it on 9500, but it should work.
- Flash Counter -> it raises everything you flash something via download mode. If it's 0, in Settings > About Phone > Status >Phone Status, it will return "Original" or something. If it's anything else than 0 (like 1, which I currently have cause I re-flashed root due to some tiny problem), it will return "personalized" or something like it. That will still void warranty IF the phone is sent to warranty like that, but will NOT trigger Knox. Also that will stop OTA Updates from working, but Kies updates will work (for some reason, samsung bug, use it ).
I have no idea how to help you regarding that Flash Counter on the 9500.
Click to expand...
Click to collapse
Thanks again.
I just hav to avoid to take the risk and prevent warranty void,the answer is not to root at the moment.
Thanks gain:good:
I need help
please some one .. i need help and it's so important . one of my friend encrypted his data though knox and regardless of what super su and root do with knox and it's disabling knox ... he rooted his phone ! (he is todler and didn't take notice )
anyway his knox now is disabled and he can't access to his data because in security knox is disabled .. how can we enable knox so he can decrypt knox with password and access to his data ... thanks in advance and keep in mind that please guys if you are not sure about how can solve problem without losing data , guide me . data encrypted with knox is so important to him .
target device is Galaxy note 3 n9005 .
If knox is 0x1, then you are out of luck.
celderic said:
If knox is 0x1, then you are out of luck.
Click to expand...
Click to collapse
if we unroot phone can't we just enable it ?
Depends how it's rooted. If Knox Warranty Void is 0x1 - you can't do nothing to it. If device is rooted keeping Knox flag 0x0, there might be a way to recover the data somehow, since Knox shouldnt be locked up.
Spere said:
Depends how it's rooted. If Knox Warranty Void is 0x1 - you can't do nothing to it. If device is rooted keeping Knox flag 0x0, there might be a way to recover the data somehow, since Knox shouldnt be locked up.
Click to expand...
Click to collapse
since Knox shouldnt be locked up " what is tha mean ? he used cf-root , i wonder knox is disabled , and data locked down in on the internal .. if we unroot it won't re enabled ?
if someone root he can't use knox for entire phone life
afraaa said:
since Knox shouldnt be locked up " what is tha mean ? he used cf-root , i wonder knox is disabled , and data locked down in on the internal .. if we unroot it won't re enabled ?
if someone root he can't use knox for entire phone life
Click to expand...
Click to collapse
If he used cf-auto-root Knox warranty is void (you can check that booting phone to download mode, if you don't know how or what that is, Google it. If there is line "Knox Warranty Void 0x1" means warranty is void, and "0x0" means it's fine)
Knox is 0x1 on his phone and that means there is no way to recover data from Knox container, at least as for now, most probably will never be.
Spere said:
If he used cf-auto-root Knox warranty is void (you can check that booting phone to download mode, if you don't know how or what that is, Google it. If there is line "Knox Warranty Void 0x1" means warranty is void, and "0x0" means it's fine)
Knox is 0x1 on his phone and that means there is no way to recover data from Knox container, at least as for now, most probably will never be.
Click to expand...
Click to collapse
yeah i know .. abut all you said ... i know guaranty is void but data to him is much important than phone guaranty .. i guess he should get phone to samsung and tell them " data all i need if you want money or void warranty the ndo it ... i guess the only way is samsung speciallists to bring back data !!! i wonder how he ignore the part that super su want's to disable knox !!!!
i wanna test to unroot and see if knox returns or not
afraaa said:
yeah i know .. abut all you said ... i know guaranty is void but data to him is much important than phone guaranty .. i guess he should get phone to samsung and tell them " data all i need if you want money or void warranty the ndo it ... i guess the only way is samsung speciallists to bring back data !!! i wonder how he ignore the part that super su want's to disable knox !!!!
i wanna test to unroot and see if knox returns or not
Click to expand...
Click to collapse
Oh god. Knox warranty void means Knox is not secure anymore. You can't recover data no matter what you do. If you unroot, it changes nothing.
Read this article from Samsung about Knox and CF-Auto-Root.
It clearly says: "Once the e-fuse bit is burned, a Samsung KNOX-enabled device can no longer create a KNOX Container, or access the data previously stored in an existing KNOX Container. This is a mechanism to ensure that enterprise data will be protected as long as the rooting attempt is detected."
Spere said:
Oh god. Knox warranty void means Knox is not secure anymore. You can't recover data no matter what you do. If you unroot, it changes nothing.
Read this article from Samsung about Knox and CF-Auto-Root.
It clearly says: "Once the e-fuse bit is burned, a Samsung KNOX-enabled device can no longer create a KNOX Container, or access the data previously stored in an existing KNOX Container. This is a mechanism to ensure that enterprise data will be protected as long as the rooting attempt is detected."
Click to expand...
Click to collapse
okay ... thanks for your time . really appreciated . if anyone knows other useful thing please let me know , this data is now not accessible is so critical unfortunately
Hi I have a note 4 (marshmallow 6.0.1).
If I tripped knox by either rooting or flashing a custom rom, and then if I decided to revert back say i unrooted and re-flashed the stock rom.
Assuming everything is back normal except that
now you have "knox warrnety void 0*1"
Will I still be able to:
-Enable Knox active protection from Samsung's "smart manager" app.
-Use "Samsung my knox" app
-Use Samsung pay or android pay
-Do OTA updates
Or is having a "stock non-rooted rom" still not enough and you won't be able to do all of the above as long as you have already tripped knox?
(Also apparently you cannot enable it while "rooted" even if you have managed to root it without tripping Knox).
Thanks in advance :good:
No. Period
pr1jker said:
No. Period
Click to expand...
Click to collapse
Hmm... I thought the warranty is the only thing you have to worry about after you trigger Knox