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
Related
Alright, where to begin.
I've owned quite a few Samsung phones by now and I've rooted every single one of them and installed custom recovery and ROMs. But with KNOX on the S4 this has made me unsure...
What will happen to my device when I root it now? I figure it'll trigger the Knox flag to 0x1. What are the drawbacks of that? Will it affect the function of my device?
And is the rooting procedure done as usual with Odin like on the S3?
And maybe most of all, is it worth rooting the S4 and installing custom ROMs?
Many questions, but I haven't found any real answers to any of them...
Nothing will happen to your device when counter z 0×1
Drawback z you'll void ur warranty & youll not get official updates if u r on I9500.If ur on I9505 then triangle away can solve both problems.No function gets hampers until you really mess with ur phone but that's after root
Yes the procedure z same
Well if ur on I9500 then there r only customised stock version nothing much only debloated or deodexed.If ur on I9505 then definitely worth it
Sent from my GT-I9500 using XDA Premium 4 mobile app
Triangle away dont do much with the knox . Once trigger there is no way at the moment to reset this.
hjertis said:
Alright, where to begin.
I've owned quite a few Samsung phones by now and I've rooted every single one of them and installed custom recovery and ROMs. But with KNOX on the S4 this has made me unsure...
What will happen to my device when I root it now? I figure it'll trigger the Knox flag to 0x1. What are the drawbacks of that? Will it affect the function of my device?
And is the rooting procedure done as usual with Odin like on the S3?
And maybe most of all, is it worth rooting the S4 and installing custom ROMs?
Many questions, but I haven't found any real answers to any of them...
Click to expand...
Click to collapse
What happens when you actually get Knox flagged to 0x1?
You basically lose the ability to install Knox softwares, and your device will be flagged as 'insecure', which means if your company allows employees to bring their own device to work for accessing corporate emails etc and they use knox to keep security, your device will not allow this. However, you will still have the ability to use future samsung firmware releases even though you have the knox flagged.
How do you trigger Knox?
You still can root your phone with CFautoroot, but that will trigger knox to flagged to 0x1. If you try to downgrade your firmware, knox will also trigger to 0x1, therefore, once you upgrade to new bootloader, there is no way to go back to old bootloader without knox. (I would suggest if you do not want knox, but you want the new firmware, you've got to manually flash the modem.bin files using Odin)
Lastly, there is still a big question mark as to whether Samsung will actually service devices with knox 0x1
kenshi08 said:
What happens when you actually get Knox flagged to 0x1?
You basically lose the ability to install Knox softwares, and your device will be flagged as 'insecure', which means if your company allows employees to bring their own device to work for accessing corporate emails etc and they use knox to keep security, your device will not allow this. However, you will still have the ability to use future samsung firmware releases even though you have the knox flagged.
How do you trigger Knox?
You still can root your phone with CFautoroot, but that will trigger knox to flagged to 0x1. If you try to downgrade your firmware, knox will also trigger to 0x1, therefore, once you upgrade to new bootloader, there is no way to go back to old bootloader without knox. (I would suggest if you do not want knox, but you want the new firmware, you've got to manually flash the modem.bin files using Odin)
Lastly, there is still a big question mark as to whether Samsung will actually service devices with knox 0x1
Click to expand...
Click to collapse
I agree with you except last words. Modem has nothing to do with knox... flashing a different modem version from rest of FW version (ROM and CSC) will probably give some data or voice problems, and he will still have the same android 4.2.2 version....
What I suggest if he wants last FW, is just flash it, root it, delete all knox files, assume he will have knox bit activated, and enjoy it.
I recently purchased a SM-N900W8. Love this device, just retired my S2 which i messed around with for a few years and never had issues...
I neglected to do research on XDA (Big mistake) before rooting it and had no idea about the repercussions of this KNOX issue.
I used this method to root it (http://galaxynote3root.com/galaxy-note-3-root/how-to-root-galaxy-note-3/)
I successfully installed CWM recovery and SuperSu and the phone is rooted. I had no intentions of installing Custom Roms just yet just wanted to be able to use some of my favorite apps that require rooting. The phones Current Binary and Phone status have both been tagged custom but my KNOX Warranty Void is still tagged at 0X0. Needless to say maybe I got lucky?
I was hoping to Revert to Stock and Unroot so I could follow this method instead (http://forum.xda-developers.com/showthread.php?t=2498850)
Is there anyways to Accomplish this without tripping the KNOX counter? I've been scouring the forums for several hours trying to find a concrete answer but cannot.
I have downloaded my stock firmware (http://www.sammobile.com/firmwares/3/?download=26653)
Any help or suggestions would be greatly appreciated. I have included a screenshot of my device info. I apologize in advance if this issue has already been addressed.
Thanks,
-Rob
For device info and Knox warranty status, you can use my app Phone INFO ★Samsung★ to get more detailed info.
Download link in my signature.
Why did you even install CWM if you didn't need it ?
Why do you want to remove it ? Don't fix it if it ain't broken. De la vega will trip Knox in 4.4, so leave it as it is.
Sent from my N9005
Dejan Sathanas said:
Why did you even install CWM if you didn't need it ?
Why do you want to remove it ? Don't fix it if it ain't broken. De la vega will trip Knox in 4.4, so leave it as it is.
Sent from my N9005
Click to expand...
Click to collapse
Will do. Was just worried about official updates and warranty if phone still says custom but knox is not tripped. But bell outsources another company for repairs and doesn't send back to Samsung directly so I probably don't need to worry to much..
I used CWM because I've used it for a couple years with my S2 and enjoyed the features so when I saw cwm was avaliable for note 3 I jumped on it.
But there is no way to revert to stock without tripping count?
Thanks.
SSJ3Rob said:
Will do. Was just worried about official updates and warranty if phone still says custom but knox is not tripped. But bell outsources another company for repairs and doesn't send back to Samsung directly so I probably don't need to worry to much..
I used CWM because I've used it for a couple years with my S2 and enjoyed the features so when I saw cwm was avaliable for note 3 I jumped on it.
But there is no way to revert to stock without tripping count?
Thanks.
Click to expand...
Click to collapse
Flashing stock using odin should rever everything back to stock and possibly not trip knox counte, I am saying possibly cuz nobody has tried to flash stock recovery and try to keep knox cool as custom recoveries have tripped everyone's knox AFAIK. But your phone FW or maybe something else might make your device an exception.
Sent From My SM-N9005 To All You Wonder Nobodies!!
Khizar said:
Flashing stock using odin should rever everything back to stock and possibly not trip knox counte, I am saying possibly cuz nobody has tried to flash stock recovery and try to keep knox cool as custom recoveries have tripped everyone's knox AFAIK. But your phone FW or maybe something else might make your device an exception.
Click to expand...
Click to collapse
I will leave as is for now until more info on the subject surfaces. As much as I want to try to flash back to stock recovery and test your theory I will hold out and not mess around with CWM or mess with apps requiring root to much incase it decides to trip the counter.
Thanks.
I got my i9505 unlocked without any warranty. Its running stock I9505XXUGNE5. What could be consequences if I root my device?
Would I be able to receive OTA updates after rooting?
Do I need to delete all KNOX related stuff after rooting? Because I've heard that CF root method does interfere with KNOX in such a way that you get random reboots.
Firstly you have a i9505 unlocked so there are no problem for root.Secondly if u will root u can't receive ota updates and when you are trying to root thay ask you stop the knox...after cf-rooted you never install knox again...because your flash counter start counting...but your device supported triangleaway so u can clear all your counter and u also back to official.
Sent from my GT-I9500 using XDA Premium 4 mobile app
fleming.patel said:
Firstly you have a i9505 unlocked so there are no problem for root.Secondly if u will root u can't receive ota updates and when you are trying to root thay ask you stop the knox...after cf-rooted you never install knox again...because your flash counter start counting...but your device supported triangleaway so u can clear all your counter and u also back to official.
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What I understand from your post is:
1) I can't receive OTA updates after rooting, so how will I upgrade to latest stock? Using Odin?
2) If I use CF-Root, KNOX will be deleted and I should not install it again, right?
3) Knox counter can be cleared using 'triangleaway', right?
So it means there is not much to lose other than KNOX? My last android phone was Xperia U and when I unlocked its bootloader its DRM keys were destroyed which means no more Bravia engine and XLoud. I hope nothing like this happens with S4.
Yoy can get ota update via kies and when you clear you flash counter u can install knox agian....and not much thing u lose except knox.
Sent from my GT-I9500 using XDA Premium 4 mobile app
You cant reset knox counter with triangleaway
Sent from my SM-G900F using Tapatalk
You should read the first thread in the Q&A section about Knox. You are getting things mixed.
If you flash a good custom rom, you really don't want to go back to stock. Don't ask what a good rom is, because that's all about personal preference.
you're confusing some stuff.
the Knox warranty void counter WILL BE TRIPPED if you'll root your device, hence, your Knox app will not work on your device.
there is no possible way to reset the Knox counter as for now.
You won't get OTA updates, because your phone will change from Official status to Custom, though with xposed module: wanam xposed, you can trick your device to be official, and still get updates via the option there: fake system status.
you can always flash a new rom with odin, even stock roms of course... but you will have to root the device again.
triangle away will reset the flash counter, but it will not reset the Knox warranty void counter.
you can see that counter in download mode (pwr button+volume down+home button)
Knox warranty void: 0x0 (not tripped) 0x1 (tripped)
Sorry for the nooby question, but what does OTA mean?
Mo Neenja31 said:
Sorry for the nooby question, but what does OTA mean?
Click to expand...
Click to collapse
OTA is update Over The Air.
myawan said:
I got my i9505 unlocked without any warranty. Its running stock I9505XXUGNE5. What could be consequences if I root my device?
Would I be able to receive OTA updates after rooting?
Do I need to delete all KNOX related stuff after rooting? Because I've heard that CF root method does interfere with KNOX in such a way that you get random reboots.
Click to expand...
Click to collapse
No, no updates but you can restore via odin of you decide later you want them. For knox phones if you will be going custom then I recommend to do so sooner than later, I've got this crazy hunch......
I had number of issues with wifi just breaking intermittently on a knox bootloader gs4 once I went custom. I would have to power down for a few minutes and then power back on to get it to come back up! it's odd because with time it seems that this issue goes away on its own for good once the custom rom and kernel has had a chance to settle, which takes a few days... The only reason why I think that this would happen is because knox can't be disabled completely and perhaps the knox bootloader is looking for some kind of knox response from the wifi driver which isn't present because it's not availble in custom rom and perhaps there is a fail count that need to be triggered before knox bootloader just give up and disables this check completely? Anyone else's thoughts on this?
But beware, for me, this issue comes back once you re-flash a new custom rom/kernel and then you have to wait it out again...
So it seems knox is still active somewhat even though you have a custom rom/kernel installed. The other reason why I recommend switching sooner rather than later is this approach, I would imagine allows for more time to react and fine tune software to work with different bootloaders Eventually as kernels and custom roms are optimized the code should speak better to the knox bootloader.
If your always upgrading then you may not be allowing enough time for open source community to react and mature to the unforeseen changes that appear in new bootloaders.
I have another gs4 no knox MDJ bootloader and have no wifi issues at all, it solid! but this may be because the community has had more time to talk to and MDJ bootloader.
Sent from my iPad using Tapatalk
yonye87 said:
you're confusing some stuff.
the Knox warranty void counter WILL BE TRIPPED if you'll root your device, hence, your Knox app will not work on your device.
there is no possible way to reset the Knox counter as for now.
You won't get OTA updates, because your phone will change from Official status to Custom, though with xposed module: wanam xposed, you can trick your device to be official, and still get updates via the option there: fake system status.
you can always flash a new rom with odin, even stock roms of course... but you will have to root the device again.
triangle away will reset the flash counter, but it will not reset the Knox warranty void counter.
you can see that counter in download mode (pwr button+volume down+home button)
Knox warranty void: 0x0 (not tripped) 0x1 (tripped)
Click to expand...
Click to collapse
Triangle away can reset your phone to Official status and allow you to get OTA's again as well.
Just got a new S5 and I've been out of the scene for a while.
Can someone point me in the direction of some up to date info/guide? I've been scouring xda for 30 mins now and can't figure out the best way to get Recovery and Root.
Bonus question: I've read that using a rootkit irreversibly increases a counter from 0x0 to 0x1 whereas TowelRoot does not. Is this true?
check your kernel version first. if its date is lower than 3rd June then TowelRoot will not trigger KNOX. but if its later than 3rd June any method used to root will trigger KNOX to 0x1
Custom kernel and recovery are out of the question. They will trigger KNOX no matter whatever you do as of now.
wajiman said:
check your kernel version first. if its date is lower than 3rd June then TowelRoot will not trigger KNOX. but if its later than 3rd June any method used to root will trigger KNOX to 0x1
Custom kernel and recovery are out of the question. They will trigger KNOX no matter whatever you do as of now.
Click to expand...
Click to collapse
Thursday May 8th. Does this mean I should go with TowelRoot? Or are you saying it doesn't matter as I intend to enable recovery anyway?
kelevra7 said:
Thursday May 8th. Does this mean I should go with TowelRoot? Or are you saying it doesn't matter as I intend to enable recovery anyway?
Click to expand...
Click to collapse
you can use towelroot, knox wont be tripped as the kernel version is less than 3rd june.
but if you flash custom recovery or kernel knox will get tripped as of now. And as you intend to enable recovery anyway, so it means you are willing to get knox tirpped hence you can use any way to root
I can confirm that towelroot will not trip knox on G900F.
Sent from my SM-G900F using XDA Premium 4 mobile app
wajiman said:
you can use towelroot, knox wont be tripped as the kernel version is less than 3rd june.
but if you flash custom recovery or kernel knox will get tripped as of now. And as you intend to enable recovery anyway, so it means you are willing to get knox tirpped hence you can use any way to root
Click to expand...
Click to collapse
Thanks for the clarification. So I'm now going to install TowelRoot, and then install TWRP from the play store. You're saying that it is only after I install TWRP that KNOX will get tripped? Even though TWRP is now official (in the play store)?
Have I got the order right?
kelevra7 said:
Thanks for the clarification. So I'm now going to install TowelRoot, and then install TWRP from the play store. You're saying that it is only after I install TWRP that KNOX will get tripped? Even though TWRP is now official (in the play store)?
Have I got the order right?
Click to expand...
Click to collapse
Yup, all non stock stuff like custom recovery`s and kernels will trip KNOX to 0x1 permanantly if flashed with (Mobile) Odin.
kelevra7 said:
Thanks for the clarification. So I'm now going to install TowelRoot, and then install TWRP from the play store. You're saying that it is only after I install TWRP that KNOX will get tripped? Even though TWRP is now official (in the play store)?
Have I got the order right?
Click to expand...
Click to collapse
AFAIK yes
gee2012 said:
Yup, all non stock stuff like custom recovery`s and kernels will trip KNOX to 0x1 permanantly if flashed with (Mobile) Odin.
Click to expand...
Click to collapse
Aaaah. That makes sense. I've just seen that in SuperSU I can disable KNOX. If I do that, install CM11 and reenable KNOX will it still show 0x1?
Would you also mind confirming that I've got the right idea about what comes next:
1. Install towelroot.
2. Install SuperSU.
3. Update SU binaries (disabling KNOX in the process).
4. Install TWRP from Playstore
5. Flash CM11
Do I need to back up my EFS partition first or will this be covered by restoring to Stock ROM (should I need to do so)?
Also this process means I don't even need Odin. Is this correct?!
kelevra7 said:
Aaaah. That makes sense. I've just seen that in SuperSU I can disable KNOX. If I do that, install CM11 and reenable KNOX will it still show 0x1?
Would you also mind confirming that I've got the right idea about what comes next:
1. Install towelroot.
2. Install SuperSU.
3. Update SU binaries (disabling KNOX in the process).
4. Install TWRP from Playstore
5. Flash CM11
Do I need to back up my EFS partition first or will this be covered by restoring to Stock ROM (should I need to do so)?
Also this process means I don't even need Odin. Is this correct?!
Click to expand...
Click to collapse
Step 4 will always trip KNOX unfortunately. If you only root like with steps 1 to 3 on roms with kernels build before june 3rd KNOX will remain 0x0. You simply cannot flash custom recovery`s without tripping KNOX (it will remain active and detect security breaches).
gee2012 said:
Step 4 will always trip KNOX unfortunately. If you only root like steps 1 to 3 on roms with kernels build before june 3rd KNOX will remain 0x0. You simply cannot flash custom recovery`s without tripping KNOX (it will remain active and detect security breaches).
Click to expand...
Click to collapse
I see. So there is no way to maintain my warranty if I want to install a custom ROM? Shall I go ahead and disable KNOX through SuperSU?
kelevra7 said:
I see. So there is no way to maintain my warranty if I want to install a custom ROM? Shall I go ahead and disable KNOX through SuperSU?
Click to expand...
Click to collapse
Look here for a KNOX explanation (different levels) http://omegadroid.co/wanted-knox-void-warranty-0x1/. You can root your decice with TR and disable KNOX notifications showing up and still keep warranty. Flashing custom recovery`s will trip KNOX.
Warranty is also region dependent, for instance rooting a device in the EU http://forum.xda-developers.com/showthread.php?t=1998801 doesn`t void warranty by law. Look how rooting is handled in your region.
gee2012 said:
Look here for a KNOX explanation (different levels) http://omegadroid.co/wanted-knox-void-warranty-0x1/. You can root your decice with TR and disable KNOX notifications showing up and still keep warranty. Flashing custom recovery`s will trip KNOX.
Warranty is also region dependent, for instance rooting a device in the EU http://forum.xda-developers.com/showthread.php?t=1998801 doesn`t void warranty by law. Look how rooting is handled in your region.
Click to expand...
Click to collapse
Thanks this is a great link. Very helpful. I have subsequently 'disabled' KNOX through SuperSU even though I'm doubtful this will really do anything with regard to my warranty. I'm already set on flashing a custom ROM so flashing TWRP is a must for me.
P.S. I've only just realised CM11 isn't available for the S5. Can you recommend any custom ROMS other than Omega and Alliance? What do you use?
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!"