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.
Related
I've made a bit of a mess and I need help please. My s4 is softbricked, but as softbricks go, it's rather hard.
I have an early S4 i9505 bought from Carphone Warehouse (UK, unlocked, pre knox). I rooted it, installed TBackup, greenify and got it how I wanted it. Then I downloaded a stock firmware from Sammobile and tested to see if I could get it back to 'warranty' condition, which was a success.
Confident that I could obtain warranty if I needed it, I re-rooted it, installed TB and greenify, and it ran sweetly for months from that point onwards.
I read about the arrival of updates (and knox) and concluded I didn't need them. It was working, leave it alone.
Then out of the blue, my nice stable machine broke. I didn't change anything I was aware of to cause it.
No normal boot.
No recovery.
Download only.
Using Odin, I tried allsorts, eventually getting the same Sammobile firmware to run.
2 days later, it broke again, same as before, but worse!?
Then I tried all sorts of stuff downloading no end of things trying to get it to boot or even go into recovery. The most promising approach was to reload the firmware along with a .pit file, but still no joy. I've lost track of the other things I tried, but I've been doing it for a week, so a lot has been done. In desperation, I even tried downloading the latest firmware, so I now have signs of knox of the odin page.
I now have the following symptoms:
Booting into recovery brings up the blue 'booting recovery' message then just blackness.
Normal boot is exactly the same as above.
Unpowered conection to my laptop gives a 5 second boot loop featuring the buzz only.
I can reliably boot into download and download stuff with Odin and change the little Odin page status messages. After (foolishly) trying the latest firmware, these messages say
ODIN MODE
PRODUCT NAME GT-I9505
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION: enable
eMMC BURST MODE enabled
Please can anyone give me some advice on what else I could try?
Thanks
Steve
Wrinklespots said:
ODIN MODE
PRODUCT NAME GT-I9505
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION: enable
eMMC BURST MODE enabled
Please can anyone give me some advice on what else I could try?
Thanks
Steve
Click to expand...
Click to collapse
If anything else is not working (especially, if you're unable to go to recovery) I'd call sammy service center. Your download mode says that you did not rooted your phone, and knox is untouched either.
spamtrash said:
If anything else is not working (especially, if you're unable to go to recovery) I'd call sammy service center. Your download mode says that you did not rooted your phone, and knox is untouched either.
Click to expand...
Click to collapse
Thanks for looking spamtrash.
I was wondering if I could get away with that. It does look good from the Odin display, but the flash counter must have a pretty high number in it by now! Won't that show up somewhere?
Do you think it does actually have a fault on it, rather than just some software that's messed up and needs tweaking?
Thanks
Steve
Wrinklespots said:
Thanks for looking spamtrash.
I was wondering if I could get away with that. It does look good from the Odin display, but the flash counter must have a pretty high number in it by now! Won't that show up somewhere?
Do you think it does actually have a fault on it, rather than just some software that's messed up and needs tweaking?
Thanks
Steve
Click to expand...
Click to collapse
1. Are you able to go to recovery mode?
2. Assuming that your previous communicates were taken from the screen in download mode - you're clean.
If answer for 1 is: NO, and assuming 2: do not bother the flash counter. Flash counter does not means you messed with custom ROMs, it just means amount of the ROM update tries. As they are unable to prove that the counter was not increased by failed KIES updates, you're safe.
To go deeper, service will have to flash and wipe your phone.
One thing: remove your sd card prior to giving/sending it out.
Try a different usb cable.I was in same boat as you (after stupidly thinking mobile odin pro liked modems).
Luckily I had an unused cable off my tab 3.
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
Hello
This afternoon, I'm trying to activate the Private Mode for my S7 Edge. At first, it does not let me enable it after I turn it off.
Then I performed a factory reset. Right now, the phone does let me turn the private mode on and off, but there is no option for me to transfer video or pictures into private mode. I press and hold the file, but in the More Option, there is not anything which let me move the file into private mode.
Is there any solution for this? Please help
Have you rooted your phone? Rooting triggers knox which makes it useless and to my knowledge, private mode uses knox. I kniw for certain secret mode in browser does use knox. Once knox is triggered then these features become unavailable. The reason for this is because root drastically weakens knox security so samsung purposefully kill knox on root. Thats the risk you have to take if you root. If you havent rooted then i have no idea what is going on but this is my first thoughts based on what you have said
richhaynes said:
Have you rooted your phone? Rooting triggers knox which makes it useless and to my knowledge, private mode uses knox. I kniw for certain secret mode in browser does use knox. Once knox is triggered then these features become unavailable. The reason for this is because root drastically weakens knox security so samsung purposefully kill knox on root. Thats the risk you have to take if you root. If you havent rooted then i have no idea what is going on but this is my first thoughts based on what you have said
Click to expand...
Click to collapse
i was rooted for awhile private mode did not work and then i unrooted my phone. private mode works just fine even with a tripped knox. so it root itself that disable private mode.
ecg803 said:
i was rooted for awhile private mode did not work and then i unrooted my phone. private mode works just fine even with a tripped knox. so it root itself that disable private mode.
Click to expand...
Click to collapse
Now im really confused as I know for certain a tripped knox kills secret mode on the browser. I just assumed private mode would suffer the same fate....
richhaynes said:
Now im really confused as I know for certain a tripped knox kills secret mode on the browser. I just assumed private mode would suffer the same fate....
Click to expand...
Click to collapse
here u go
ecg803 said:
here u go
Click to expand...
Click to collapse
one more to show iam not rooted
ecg803 said:
not rooted
Click to expand...
Click to collapse
Private mode is a Knox container. Knox CANNOT be tripped to use Knox containers.
Sent from my SM-G935T using Tapatalk
toastido said:
Private mode is a Knox container. Knox CANNOT be tripped to use Knox containers.
Click to expand...
Click to collapse
well my knox is tripped
Yes, it "turns on" but cannot be used.
Edit: your didn't say that, OP did, my bad.
Sent from my SM-G935T using Tapatalk
the op probably is rooted and just did not put that information in their. i had my phone rooted and was testing private mode and it did not work but then i went back to all stock phone. i had private mode back.
ecg803, can you actually put anything in to private though? Switching it on or off doesnt mean its usable. For example, go to gallery, select an item, click more in top right, and is the 'move to private' option available? I agree with toastido that although you can switch it on and off, the actual ability to put anything in there should be, ahem, toast
yes i can.
delete
Im puzzled. You are the only person i have come across to have it working after tripping knox. Dont suppose you have any numbers for the UK national lottery tomorrow?
I had same problem with S5 which is unrooted but Twrp was installed which triggers Knox counter. Now Marshmallow 6.0.1 is not letting Samsung Browser to open private tab unlike on my S4 which is rooted and has 5.0.1 lollipop. It is a Marshmallow + Samsung scandal.
Hi!
I'm trying to go back to stock to try knox features like secure folder. I have restored my device (Spain unbranded) with SmartSwitch and flashing firmware through Odin.
My problem is that Knox and Secure folder says that it can not work because I have installed unauthorized software. SafetyNet passes, on download mode, I see all official, and Apps (like banking apps) works fine without detecting root.
I have warranty void bit = 1. This means that, even flashing again stock firmware, I will never be able to use Knox? I'm worried about using root cloacks methods because of something stops working (for example due an update) I will unable to access to secure folder.
Thanks a lot in advance!
runtime_Err0r said:
Hi!
I'm trying to go back to stock to try knox features like secure folder. I have restored my device (Spain unbranded) with SmartSwitch and flashing firmware through Odin.
My problem is that Knox and Secure folder says that it can not work because I have installed unauthorized software. SafetyNet passes, on download mode, I see all official, and Apps (like banking apps) works fine without detecting root.
I have warranty void bit = 1. This means that, even flashing again stock firmware, I will never be able to use Knox? I'm worried about using root cloacks methods because of something stops working (for example due an update) I will unable to access to secure folder.
Thanks a lot in advance!
Click to expand...
Click to collapse
As your knox is tripped already i.e. showing 0×1 so you will never be able to use knox related security features as well as samaung pay on your phone..When knox is tripped once while in rooting or trying any unauthorised software installation, it will never been reset to initial state either by trying to install stock firmware again..
DroidHackeR said:
As your knox is tripped already i.e. showing 0×1 so you will never be able to use knox related security features as well as samaung pay on your phone..When knox is tripped once while in rooting or trying any unauthorised software installation, it will never been reset to initial state either by trying to install stock firmware again..
Click to expand...
Click to collapse
Ok thanks a lot for the info!
runtime_Err0r said:
Ok thanks a lot for the info!
Click to expand...
Click to collapse
https://forum.xda-developers.com/s7-edge/how-to/guide-secure-folder-samsung-knox-s-t3560079
^^That thread has a tutorial on how to get knox features working if your knox was tripped however I don't think it will as secure as it would be if used the knox features without knox being tripped.
runtime_Err0r said:
Ok thanks a lot for the info!
Click to expand...
Click to collapse
I can recommend you flashing ambasadii's ROM. I'm currently using it with the latest SuperStock Kernel and have secure folder fully working. You'll have to download the full 10.1 ROM and the 10.2 OTA which is about 500mb