[Q] Kies, Updates, Root, & Private Mode - Galaxy S 5 Q&A, Help & Troubleshooting

I have read in several threads that updating using Kies would lose root, is this true? And is this the safest way to unroot the device back to stock? And i know right now rooting the Galaxy S5 causes the Private Mode unusable, is un rooting the phone back to stock make Private mode usable again? Even though the Knox counter was tripped?

Related

Need the stock G900F kernel.

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.

[Q] S4 I9500 BN2 root without trip knox.

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:

help unbrick my Samsung Galaxy s5

hello,
i tried to root my S5 and it worked now i removed my Root with Super Su un root option and i wanna return it like it was before, but seems it does working
cuz my knox is not working so when i try go to my phone options and try update the android ver it says i massed up with my phone settings so i can not now.
how i can return it to normal
my build is
KOT49.G900FXXU1ANG7
android 4.4.2
country: israel
seems i can not find anywhere Kot49 files to somehow unbrick it
or is there way restore my knox so i can update my phone ?
This is not brick ... when you root your phone you triggered the knox to 0x1 and there is no cure for this now
u want to update phone using OTA method is it? over the air method right? if yes simply flash ur firmware using odin then u will back to stock status and get updates from ota. hope that helps. once knox counter move up to 1, for now u cant get it off.

Samsung Pay still not working after restoring to stock through ODIN

Got my S7 yesterday, played around with root, and decided to go with a stock experience for the time being so I can use Samsung Pay and MST (blasphemous, I know). I used ODIN to restore back to stock, verified KNOX counter wasn't tripped, and went on setting everything up.
I installed Samsung Pay and launched, only to run into the access denied message you would see if you were attempting to open it with a rooted device. Any thoughts as to what could be happening?
Song0330 said:
Got my S7 yesterday, played around with root, and decided to go with a stock experience for the time being so I can use Samsung Pay and MST (blasphemous, I know). I used ODIN to restore back to stock, verified KNOX counter wasn't tripped, and went on setting everything up.
I installed Samsung Pay and launched, only to run into the access denied message you would see if you were attempting to open it with a rooted device. Any thoughts as to what could be happening?
Click to expand...
Click to collapse
I would make sure you followed the return to stock instructions in psouza4 thread (http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039). I flashed through odin yestererday and took the pf2 update that was available when I was done. I am able to install and access Samsung pay. What all did you flash in ODIN?
thefirst__noel said:
I would make sure you followed the return to stock instructions in psouza4 thread (http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039). I flashed through odin yestererday and took the pf2 update that was available when I was done. I am able to install and access Samsung pay. What all did you flash in ODIN?
Click to expand...
Click to collapse
Resolved! Actually, it was my strict adherence to the instructions that led to the issue - the instructions only tell you to flash AP, CP, and CSC back down to PE1. Which was fine and dandy, but my BL remained at PF2, which is the reason why I had issues loading Samsung Pay. I was afraid that I had either tripped the mythical physical e-fuse somehow, or my phone was blacklisted from Samsung Pay servers - fortunately this was not the case! Once I updated everything back to PF2, Samsung Pay was able to load.
Help Galaxy s7
Hello friends, I made the root process in my S7 GALAXY, but the direct method cf self root, now my knox is 0x1. Is this with your method, I can return to the original state knox 0x0 and able to use the Samsung pay ???
[email protected] said:
Hello friends, I made the root process in my S7 GALAXY, but the direct method cf self root, now my knox is 0x1. Is this with your method, I can return to the original state knox 0x0 and able to use the Samsung pay ???
Click to expand...
Click to collapse
Sorry but there's no method at this time to reset Knox back to 0x0. The method of root that was posted here wouldn't trip Knox which is why when flashing back to stock they are able to use Samsung Pay again.
how to trip that knox again? and how to check knox state? I had installed stock samsung s7 edge India ROM latest but now smart tutor apps is gone (that i intalled from playstore) and samsung pay is not working

Galaxy S7 Edge Private Mode Is Not Working

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.

Categories

Resources