Related
I did look though the form to see if this had been answered but I couldn't see anything. I rooted my Note 3 using Odin and tripped the KNOX counter. Now of course it won't update. Is there a way of getting round this or have I smegged it up already?
Sorry if this has been answered but I couldn't find anything!
English_Gentleman said:
I did look though the form to see if this had been answered but I couldn't see anything. I rooted my Note 3 using Odin and tripped the KNOX counter. Now of course it won't update. Is there a way of getting round this or have I smegged it up already?
Sorry if this has been answered but I couldn't find anything!
Click to expand...
Click to collapse
What is your status when you boot to Odin/download mode? (most interested in RP SWREV part).
Either way - you tripped the Knox flag, and as far as we know (so far) that can't be reversed (at least not by us).
However you are now free to do any other Odin stuff you want - for instance you can easily update to some stock NEWER or EQUAL version that you like, or install a custom recovery, kernel or ROM.
Another option might be to try with Kies 3 in "recovery mode" - that should force-update you to the latest official version for your phone. But Knox will most likely stay 1.
The reason that it's not updating is because it's rooted, not because the knox flag is tripped. You can't get updates on a rooted phone.
To update it, just download the firmware and then flash it with Odin. You will lose root, but since knox is tripped anyway, just re-root it with CF-Autoroot.
Thanks guys! I plugged it into Kies and it updated. I lost ROOT but I think I'll leave it for a while now until someone fixes the KNOX tip and a possible way to get updates with ROOT.
Even though it's warranty void... I think I'll leave it for now just so I don't mess it up big time next time!
Get Wanam Xposed, you will also need the xposed framework. There is a setting in wanam xposed that let's you fool your system into thinking it's not rooted. You will be able to update that way. I've managed to do it twice and I'm rooted.
Sent from my SM-N9005 using Tapatalk
Im aware you cant reset knox counter thats not what im asking. After you trip knox and root using CF method, can you flash stock everything with Odin and take OTA's normally?
charlie-n said:
Im aware you cant reset knox counter thats not what im asking. After you trip knox and root using CF method, can you flash stock everything with Odin and take OTA's normally?
Click to expand...
Click to collapse
I have a similar question... currently Rooted and have been getting an update message for system update> Can I accept it?
charlie-n said:
Im aware you cant reset knox counter thats not what im asking. After you trip knox and root using CF method, can you flash stock everything with Odin and take OTA's normally?
Click to expand...
Click to collapse
Good question, I am coming from the EVO Lte, and am new to Samsung. So I am a little curious as well.
I have the same question. I've searched the forums and can't find a definite answer. Some say you can flash back to stock and accept OTAs with Knox still tripped, while others say that Knox being 0x1 will disable OTAs completely.
blackrabbitklan said:
I have the same question. I've searched the forums and can't find a definite answer. Some say you can flash back to stock and accept OTAs with Knox still tripped, while others say that Knox being 0x1 will disable OTAs completely.
Click to expand...
Click to collapse
I think OTAs will not work, but you can still update via Kies.
BLuFeNiX said:
I think OTAs will not work, but you can still update via Kies.
Click to expand...
Click to collapse
Thanks for the info. That won't be a problem for me, but if I ever end up selling the device, I guess I'll have to explain the situation to the potential buyer. I've read there's an OTA out of the box on some devices, and mine will be here tomorrow. I was gonna play around with it completely stock just in case I have any issues and have to send it back. Once I'm sure I'm keeping it, if there is an update, I'll root first and then flash back to see what happens. I'll update this thread with my results.
BLuFeNiX said:
I think OTAs will not work, but you can still update via Kies.
Click to expand...
Click to collapse
How do you update via Kies ?
trevagreene said:
How do you update via Kies ?
Click to expand...
Click to collapse
Based on my experience with my siii and other samsung devices it's more or less:
1) Make sure kies is up to date (I usually get prompted, otherwise go to "information>check for updates" at the top of kies)
2) plug in your phone (if you have pin or some other security system make sure you unlock it and on the home screen)
3) You should see the device under connected devices
4) At this point I usually get prompted, if you don't make sure the device is selected and look under "firmware information" and it should either allow you to update or tell you the device is up to date.
I rooted my s5 after 1 week, of course Knox status has changed and ota is not working, because Rom status is custom.After doing factory reset ota is working, as well as Rom status is official. I have to mention that I did rooting because of blocking ads and unwanted apps, so I do not use any custom Rom.hope this could help to understand Knox and ota difficulties.
Odesláno z mého SM-G900F pomocí Tapatalk
standa75 said:
I rooted my s5 after 1 week, of course Knox status has changed and ota is not working, because Rom status is custom.After doing factory reset ota is working, as well as Rom status is official. I have to mention that I did rooting because of blocking ads and unwanted apps, so I do not use any custom Rom.hope this could help to understand Knox and ota difficulties.
Odesláno z mého SM-G900F pomocí Tapatalk
Click to expand...
Click to collapse
So was rooting preserved after you did a factory reset? Was the knox counter status back to 0 or was it still tripped
vayu said:
So was rooting preserved after you did a factory reset? Was the knox counter status back to 0 or was it still tripped
Click to expand...
Click to collapse
I am still rooted after factory reset via stock Rom. Knox status is tripped. Afaik there is not known solution how to reset Knox to previous state now.
Odesláno z mého SM-G900F pomocí Tapatalk
Can someone please explain to me what is this KNOX and what does it do. How can I check its status?!
It's like the triangle on various Samsung devices. From what I understand, it will display a message or counter if you've modified the OS. This basically tells a service tech or phone carrier employee that you messed with the phone and voided your warranty. As stated, it also disables OTAs as well.
Hi,
Its been a few years since ive Rooted or been ontop of the forums ect.
Just wanted to let other people know my experience with Un-Rooting my S5 GM-900F
- Rooted with Odin + tar file
- Un-Rooted with Super SU
- Typically their is now an update available but cannot update as Samsung recognise that the phone was previously rooted.
- On a PC or Mac download Kies and update.
- Nothing has flagged up with any counters, did not experience any problems with KNOX
Hope this helps everyone.
MaxiBizzle said:
Hi,
Its been a few years since ive Rooted or been ontop of the forums ect.
Just wanted to let other people know my experience with Un-Rooting my S5 GM-900F
- Rooted with Odin + tar file
- Un-Rooted with Super SU
- Typically their is now an update available but cannot update as Samsung recognise that the phone was previously rooted.
- On a PC or Mac download Kies and update.
- Nothing has flagged up with any counters, did not experience any problems with KNOX
Hope this helps everyone.
Click to expand...
Click to collapse
Using CF Auto Root increases your flash counter and trips the KNOX warranty flag!
Unrooting with SuperSU and updating with Kies have reset the KNOX WARRANTY VOID to 0x0?!
Until now, it was impossible to reset KNOX!!!
Please confirm
castillofr said:
Using CF Auto Root increases your flash counter and trips the KNOX warranty flag!
Unrooting with SuperSU and updating with Kies have reset the KNOX WARRANTY VOID to 0x0?!
Until now, it was impossible to reset KNOX!!!
Please confirm
Click to expand...
Click to collapse
Not true, KNOX will still say 0x1 after unrooting, he probably means the system status and binaries are reset to Official again.
castillofr said:
Using CF Auto Root increases your flash counter and trips the KNOX warranty flag!
Unrooting with SuperSU and updating with Kies have reset the KNOX WARRANTY VOID to 0x0?!
Until now, it was impossible to reset KNOX!!!
Please confirm
Click to expand...
Click to collapse
Hi,
Well the uninstall of SuperSU went ahead with no problems, a box did flag up saying something about would you like to disable KNOX before continuing and just confirmed it.
Since the Un-Root, i have just opened KNOX again and havent had any problems at all. I did complete a factory reset just for my OCD needs with it and nothing has been triggered and no flags or counters. Still have the KNOX app with the set up wizard client available to get it going if i ever need it again so..
Didnt realise that people where having a problem with KNOX if im honest, when i finish work i shall have a play around with it and update this if i encounter any problems.
gee2012 said:
Not true, KNOX will still say 0x1 after unrooting, he probably means the system status and binaries are reset to Official again.
Click to expand...
Click to collapse
This might well be the case, i dont fully understand all of the tech terms regarding the binaries but only have a little knowledge when it comes to checking the counters and any flags or problems.
- Say for example that KNOX was tripped, a) What would happen and when/where would i encounter a problem and b) Is their any detrimental effect on the overall phone or just for KNOX?
Regards.
MaxiBizzle said:
This might well be the case, i dont fully understand all of the tech terms regarding the binaries but only have a little knowledge when it comes to checking the counters and any flags or problems.
- Say for example that KNOX was tripped, a) What would happen and when/where would i encounter a problem and b) Is their any detrimental effect on the overall phone or just for KNOX?
Regards.
Click to expand...
Click to collapse
KNOX, Private Mode and off course warranty are affected when the KNOX void flag says 0x1 and you are rooted. If you unrooted correctly as discribed by the OP Knox and Private Mode should work again after you flashed a stock rom.
gaudent 206854
gee2012 said:
KNOX, Private Mode and off course warranty are affected when the KNOX void flag says 0x1. If you unrooted correctly as discribed by the OP Knox and Private Mode should work again if you flashed a stock rom.
Click to expand...
Click to collapse
Hi,
Well KNOX is working as it did the first day i got the S5 and havent encountered any problems nor seen any flags. IF their were to be a void flag 0x1 where would i see this?
I was just nosing around on the forums and saw that alot of people were Un-Rooting via SuperSU and then using Kies to then boot the stock rom.
Thanks for your help and advice. Sorry this seemed like a dud thread!
MaxiBizzle said:
Hi,
Well KNOX is working as it did the first day i got the S5 and havent encountered any problems nor seen any flags. IF their were to be a void flag 0x1 where would i see this?
I was just nosing around on the forums and saw that alot of people were Un-Rooting via SuperSU and then using Kies to then boot the stock rom.
Thanks for your help and advice. Sorry this seemed like a dud thread!
Click to expand...
Click to collapse
KNOX is only tripped intentionaly (not by accident), that is if you root with CF Auto Root or flash a custom recovery or kernel with (Mobile) Odin.
kararye and
gee2012 said:
KNOX is only tripped intentionaly (not by accident), that is if you root with CF Auto Root or flash a custom recovery or kernel with (Mobile) Odin.
Click to expand...
Click to collapse
Ok no worries. Completed the Root with Odin v3.09 i believe, did not flash any custom roms or anything was just playing around with xposed installer, Mobile Odin was never used.
Not sure if that makes any difference?
MaxiBizzle said:
Ok no worries. Completed the Root with Odin v3.09 i believe, did not flash any custom roms or anything was just playing around with xposed installer, Mobile Odin was never used.
Not sure if that makes any difference?
Click to expand...
Click to collapse
What what software did you root with Odin? If you used CF Root your flag is 0x1.
gee2012 said:
What what software did you root with Odin? If you used CF Root your flag is 0x1.
Click to expand...
Click to collapse
Hi,
Oh right i see what you mean now, sorry for the delay. It was CF-Root
MaxiBizzle said:
Hi,
Oh right i see what you mean now, sorry for the delay. It was CF-Root
Click to expand...
Click to collapse
As you live in the EU warranty for the device is still valid when rooted/tripped KNOX unless the manufacturer can prove the issue is caused by rooting.
gee2012 said:
As you live in the EU warranty for the device is still valid when rooted/tripped KNOX unless the manufacturer can prove the issue is caused by rooting.
Click to expand...
Click to collapse
Hi,
Oh right i didnt know that. Is it just within the EU that the warranty is still valid? Are their any other countries that are the same?
Just a general question then, with regarding the voidance of KNOX or anything, would that only effect me if i wanted to send the phone back for whatever reason? The counters for example wouldnt made a difference for my phone and daily useage anyway so if i just keep the phone and continue to not having any problems i could have as many counters on it as possible?
Just getting my head around the whole void/counters thing.
MaxiBizzle said:
Hi,
Oh right i didnt know that. Is it just within the EU that the warranty is still valid? Are their any other countries that are the same?
Just a general question then, with regarding the voidance of KNOX or anything, would that only effect me if i wanted to send the phone back for whatever reason? The counters for example wouldnt made a difference for my phone and daily useage anyway so if i just keep the phone and continue to not having any problems i could have as many counters on it as possible?
Just getting my head around the whole void/counters thing.
Click to expand...
Click to collapse
Afaik only in the EU by EU law wich superceeds OEM terms/conditions.
gee2012 said:
KNOX, Private Mode and off course warranty are affected when the KNOX void flag says 0x1 and you are rooted. If you unrooted correctly as discribed by the OP Knox and Private Mode should work again after you flashed a stock rom.
Click to expand...
Click to collapse
I have currently official status but Knox 0x1.
The one & only thing concerned then is warranty. Knox based apps and all others should work as before Knox 0x1.
Hawke84 said: "If the Knox warranty void line says 0x1 then you cannot use knox softwareas your device has been flagged as insecure. By this i mean that if your workplace / company supports bring your own device to work for corporate emails etc and they use knox to keep security your device will not allow this. You are still able to use future samsung firmware releases with the knox flag 0x1. hope this makes sense. sorry for any confusion this has caused!"
Hi gurus. first off, bought my first note 4 some days ago.. always thought the note series would be too big a phone for me.. what have i been thinking??? this is hands down the best phone i have ever had.. cant remember the last time a phone gave me this feeling..
but I am at a crossroad here.. i really REALLY miss root, but a little hesitant regarding tripping the e-fuse/knox/warranty. havent had a Samsung since the S4 was newly released.
I do not want to flash custom roms, just root stock and debloat and titanium backup, xposed, ad blocking etc..
in this regard, towelroot, stumproot is genius i think, and still able to receive OTA. but does not work on the note 4 of course.
but what happens when Lollipop arrives, seem to remember that the L would be different regarding root? should i wait to root until the Lollipop update arrives, should be here soon for our devices..
do you think there will be a workaround for the e-fuse trippin?
in general, whats your thoughts about this..?
my phone is the Snapdragon, SM-N910F.
Don't hold your breath for a root that doesn't trip Knox, and don't worry about it unless you work for a corporation that requires the use of Knox.
Chainfire had already proven root on devices with LP; I don't see any reason to wait. Being rooted doesn't often seem to be a problem regarding warranty.
Thanks for your reply rcobourn. Would one be able to receive ota with Chain fire auto root? What's the preferred rooting method when only going stock.?
Will root make Private Mode unusable?
I don't care about voiding warranty with knox 1 or 0x1, but I want knox Private mode to work on a Rooted exynos.
Any one knows if rooted knox still works or it must disabled with Titanium Backup?
SJGSM said:
Will root make Private Mode unusable?
I don't care about voiding warranty with knox 1 or 0x1, but I want knox Private mode to work on a Rooted exynos.
Any one knows if rooted knox still works or it must disabled with Titanium Backup?
Click to expand...
Click to collapse
i am rooted and using private mode just try xsecurestorage by wanam and your good to go
just folder mount breaks the private mode
buljo said:
Thanks for your reply rcobourn. Would one be able to receive ota with Chain fire auto root? What's the preferred rooting method when only going stock.?
Click to expand...
Click to collapse
SJGSM said:
Will root make Private Mode unusable?
I don't care about voiding warranty with knox 1 or 0x1, but I want knox Private mode to work on a Rooted exynos.
Any one knows if rooted knox still works or it must disabled with Titanium Backup?
Click to expand...
Click to collapse
CF breaks OTA as I found out the hard way, it tried to auto install and soft bricked itself last night. Easy fix, just flash the latest firmware from sammobile.
As for private mode that is only broken if you use Xposed without Xsecurestorage
Can we use kies for updates? Or do we have to flash roms all the way?
buljo said:
Can we use kies for updates? Or do we have to flash roms all the way?
Click to expand...
Click to collapse
Not if it's rooted. Flash using ODIN, dunno what it's like now but in the S2 days Kies was an awful piece of crap, whereas ODIN always worked perfectly.
buljo said:
Can we use kies for updates? Or do we have to flash roms all the way?
Click to expand...
Click to collapse
I highly doubt Kies will work properly, although it does tell me when there is an update for my phone when rooted so it might but I personally wouldn't try it as it most likely will do the same thing as letting it install the OTA automatically and soft brick it
Fuzzi99 said:
I highly doubt Kies will work properly, although it does tell me when there is an update for my phone when rooted so it might but I personally wouldn't try it as it most likely will do the same thing as letting it install the OTA automatically and soft brick it
Click to expand...
Click to collapse
Worked for me when the last update came out, I just updated via Kies while I was rooted. Everything went good.
Did you keep root while using kies?
buljo said:
Did you keep root while using kies?
Click to expand...
Click to collapse
I was rooted while I used kies to update, after the update the root got removed and I had to root it again with the same method I used to root it before the update.
Hawke84 said:
Lots of work went I to finding a solution on S4 when knox first came out including by chainfire with no luck. Also since october people have been trying to root note 4 without tripping knox with no luck.
There is no difference in the system of tripped and not tripped. Soon as anything unsigned or insecure is flashed the bootloader burns the efuse
Sent from my SM-G920F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As you can see my idea was a bust but here is the original op
Okay, Lets try this here because nobody seems interested in helping in the T-Mobile section.
ThePagel said:
Correct me if I am wrong here, the reason knox is being tripped by cf auto root is because of the way it acquirers root not because it is rooted. With that in mind I would Like to make a tar ball with a pre rooted system.img. To make sure it will have the best possibility to not trip knox and not cause a soft brick I want to use a system dump from a running phone that has only been rooted. I am pretty sure this has worked on every galaxy phone before the s6 and the only reason you don't hear more about it recently is because of the success of towelroot. I am getting this phone on the 1st (so excited) and would like root but want to try samsung pay more.
If you are willing to help I need the following:
Be on a 100% stock samsung bloated system with root (absolutely no tweaked systems I need pure stock with root)
Install supersu into /system (supersu settings)
Make a system.img dump with adb or terminal emulator and upload it for me (as long as you do not dump the data partition no personal data will be dumped)
At this point I will make the tarball and upload it and have the person who made the system dump flash the tarball. If he/she boots up fine I will the need a volunteer who has not rooted and verified that knox has not been tripped on his/her phone to flash it and see if knox still has its warranty. Obviously the volunteer should go into this not caring if knox gets tripped.
To make things completely clear I need the following:
Somebody who knows how to dump with adb/terminal emulator and already rooted
Somebody without a tripped knox warranty who doesn't care if it gets tripped
Click to expand...
Click to collapse
As soon as you flash an unsigned image Knox is going to be tripped.
Lots of work went I to finding a solution on S4 when knox first came out including by chainfire with no luck. Also since october people have been trying to root note 4 without tripping knox with no luck.
There is no difference in the system of tripped and not tripped. Soon as anything unsigned or insecure is flashed the bootloader burns the efuse
Sent from my SM-G920F using XDA Premium 4 mobile app
Drumrocker said:
As soon as you flash an unsigned image Knox is going to be tripped.
Click to expand...
Click to collapse
^^^ This, unfortunately, ends the discussion altogether.
Drumrocker said:
As soon as you flash an unsigned image Knox is going to be tripped.
Click to expand...
Click to collapse
Hawke84 said:
Lots of work went I to finding a solution on S4 when knox first came out including by chainfire with no luck. Also since october people have been trying to root note 4 without tripping knox with no luck.
There is no difference in the system of tripped and not tripped. Soon as anything unsigned or insecure is flashed the bootloader burns the efuse
Sent from my SM-G920F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CafeKampuchia said:
^^^ This, unfortunately, ends the discussion altogether.
Click to expand...
Click to collapse
Indeed now I get closure, thank you.
So how does safestrap work?
lowspeed said:
So how does safestrap work?
Click to expand...
Click to collapse
Doesn't matter in this instance because you need root to use safestrap. He is pretty open on how safestrap works if you look at his threads and website.
Sorry guys, which signature needs to be applied? I found a guide to sign Windows modded drivers, I don't know if this can be applied here, too...
The real trick is getting it signed. There might be no easy way to do that unless the key method can be replicated to make signed binaries. This could be a samsung proprietery tool. That said I did find an interesting nugget of info hxxp://galaxys4root.com/what-is-binary-counter/ in the comments section.
HI,
I flashed pre rooted firmware 4.2.2 using ODIN on my Samsung I-9500 4.2.2. Then the status is remain same
Binary : Samsung Official
System : Official.
Then I installed Wanam apk to modify the UI, It asked me to download Xposed framework I grant Super user permission. Once It completed I checked the status
Binary : Samsung Official
System : Custom.
I flashed stock firmware 4.2.2 and did the reset factory reset. Then it changed to
Binary : Samsung Official
System : Official.
My question, Is the hidden binary count or knox counter triggered or not ?
If I updated to stock 4.3 Is the Knox Warranty bit 0×0 or 0×1 ?
Please help me.
The rooted aspect only seems to be possible provided nothing in the UI itself is changed? There is a trigger file in the rom. Something that obviously a Wanam install triggers. All that seems to indicate that it might actually be possible to have a pre-rooted rom and install via recovery. But considering the phone model referenced, its possible this particular workaround has been plugged. On the off chance that it has not. It might be the only viable way to do root without tripping knox. I imagine the existing stock roms with root preloaded however trip knox (I saw no indication of that in posts but I did not dig that deep).
If anyone can answer that in the affirmative or negative it might be worth noting. Will knox get tripped on a stock (but pre-rooted) rom?
The point of this thread is to point out something we already know and have known for some time? WTF
shollywood said:
The point of this thread is to point out something we already know and have known for some time? WTF
Click to expand...
Click to collapse
I don't think the OP was aware of all the information when he started the thread. I think the thread title has since been changed.
But yeah, i guess the thread could be closed.