Hi,
I have rooted my German Galaxy Note 3 n9005 with Towelroot, and subsequently upgraded with Mobile Odin from NB7 to latest firmware NF4 and also flashed the latest X-Note custom Rom. Until now I have kept my Knox at 0x0 since I have never flashed custom kernels or recovery. I have also deactivated all Knox-related apps and processes. Now I have the following question: IfI flash at this stage a custom recovery with Mobile Odin Pro would it trigger Knox counter and if yes then why? I mean how can I trip Knox if Knox is no more present on my phone?
Steven1962 said:
Hi,
I have rooted my German Galaxy Note 3 n9005 with Towelroot, and subsequently upgraded with Mobile Odin from NB7 to latest firmware NF4 and also flashed the latest X-Note custom Rom. Until now I have kept my Knox at 0x0 since I have never flashed custom kernels or recovery. I have also deactivated all Knox-related apps and processes. Now I have the following question: IfI flash at this stage a custom recovery with Mobile Odin Pro would it trigger Knox counter and if yes then why? I mean how can I trip Knox if Knox is no more present on my phone?
Click to expand...
Click to collapse
Custom Recovery is meant to trip KNOX at all costs. I understand you used the MOP route to get to X-Note with KNOX at 0x0, but recovery or custom kernels WILL trip KNOX as it detected a breach in the bootloader-kernel-recovery TrustZone.
MOP with custom ROM and 0x0 is a case where you can bypass KNOX, but that's as far as it goes. Any sort of kernel or recovery flash will trip KNOX.
nicholaschum said:
Custom Recovery is meant to trip KNOX at all costs. I understand you used the MOP route to get to X-Note with KNOX at 0x0, but recovery or custom kernels WILL trip KNOX as it detected a breach in the bootloader-kernel-recovery TrustZone.
MOP with custom ROM and 0x0 is a case where you can bypass KNOX, but that's as far as it goes. Any sort of kernel or recovery flash will trip KNOX.
Click to expand...
Click to collapse
Many thanks for the answer. I was hoping that I won't trip Knox since I keep the old Kitkat bootloader and the new NF4 stock kernel untouched. Interesting how this Knox system works... From what you said I understand that you cannot FULLY deaktivate Knox even if you freeze or delete the appropriate files and it sort of gets resurrected if you flash custom recovery, right?
Steven1962 said:
Many thanks for the answer. I was hoping that I won't trip Knox since I keep the old Kitkat bootloader and the new NF4 stock kernel untouched. Interesting how this Knox system works... From what you said I understand that you cannot FULLY deaktivate Knox even if you freeze or delete the appropriate files and it sort of gets resurrected if you flash custom recovery, right?
Click to expand...
Click to collapse
It's at the bootloader level. Think of it as a lever that only get switched on when you flash a kernel or a custom recovery.
Related
Hello again,
I'm not sure if I can replace my Note 3 under warranty FOC with the status screen at recovery showing the following messages :
Current Binary : Samsung Official
System Status : Custom
Knox Kernel Lock : 0x0
Knox Warranty Void : 0x0
I'm just worried about the System Status : Custom message. Is that a problem?
I unrooted using the method explained in this thread and this link directly takes to my post in that thread : http://forum.xda-developers.com/showthread.php?p=46511887#post46511887
Do I have to do anything else for replacement under warranty?
Thank you for any information.
Remove SD card and reboot. Then check status again.
Or you can just Flash stock room through Odin and it will all be official again.
Sent from my SM-N9005 using Tapatalk
alom5 said:
Or you can just Flash stock room through Odin and it will all be official again.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Thank you. I flashed the official latest rom and everything is official again.
But why do I read so many times that flashing custom roms will void warranty, if this can be reverted by flashing official roms?
Is it that the knox will be tripped to 0x1? I flashed using the method I mentioned above but my knox stayed at 0x0...
amgreenhawk said:
Thank you. I flashed the official latest rom and everything is official again.
But why do I read so many times that flashing custom roms will void warranty, if this can be reverted by flashing official roms?
Is it that the knox will be tripped to 0x1? I flashed using the method I mentioned above but my knox stayed at 0x0...
Click to expand...
Click to collapse
Most custom roms require a custom recovery to be installed, this will trip Knox. Also most custom roms have altered kernels, this too will trip Knox.
You have simply gained root without replacing the recovery or the kernel.
amgreenhawk said:
Thank you. I flashed the official latest rom and everything is official again.
But why do I read so many times that flashing custom roms will void warranty, if this can be reverted by flashing official roms?
Is it that the knox will be tripped to 0x1? I flashed using the method I mentioned above but my knox stayed at 0x0...
Click to expand...
Click to collapse
There's a bit of murky waters regarding the warranty if knox is tripped. But recently Samsung have said knox tripping does not affect warranty. But to be on the safe side some people decide to not trip knox. There are ways to root and flash custom roms without trooping knox but not if you are on one of the latter bootloaders.
Once knox is tripped there is no going back as it stands. ..... But if you like to customize your phone and make it look and feel much nicer .... Who gives a foookk .....I for one don't?
Also knox can be tripped flashing stock firmware using odin.... If you are unlucky. ..
Sent from my SM-N9005 using Tapatalk
Thank you all for the Knox explanations. That cleared up some doubts of mine.
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?
i rooted my device using towelroot. the knox counter still shows 0x0.
is there any way to install twrp recovery without tripping knox?
cheers experts
edit: (so that i can backup my stock rom) yes, i know i can reflash stock rom without tripping knox, but want to try the non-knox tripping instructions to flash custom rom, having a complete backup before i do
would it be possible to use this app to install twrp without tripping knox?
Hi,
Installing anything "Custom" , will trip the knox counter
malybru said:
Hi,
Installing anything "Custom" , will trip the knox counter
Click to expand...
Click to collapse
Well on the i9505, few TW based custom roms dont trip knox
But yeah any custom recovery or kernel will trip knox
"If someone helps, never forget to hit thanks ? "
Hey guys, im new here. coming from a nexus 4.
What i should know before i root my s5 ? I heard something about knox, what is this, it's likea bootloader or something like i must get rid of before rooting my device and installing roms ?
Read a few threads, everything you're asking has been posted thousands of times over
*Detection* said:
Read a few threads, everything you're asking has been posted thousands of times over
Click to expand...
Click to collapse
I read about root, but can't find infos about knox.
Just use cf auto root and odex, that's it ?
KNOX is Samsungs way of voiding your warranty, when their hardware is at fault, but you have flashed something custom
0x0 = valid
0x1 = void
Soon as you flash anything custom, 0x1 - and it's irreversible
If you don't care, root using CF Auto Root and ODIN
Or TWRP 2.8.7.0 & ODIN, then SuperSU zip from TWRP recovery
Like I say, everything is posted thousands of times over, if you'd checked the thread below this one, you'd have known what KNOX was
http://forum.xda-developers.com/galaxy-s5/help/rom-opt-t3188679
*Detection* said:
KNOX is Samsungs way of voiding your warranty, when their hardware is at fault, but you have flashed something custom
0x0 = valid
0x1 = void
Soon as you flash anything custom, 0x1 - and it's irreversible
If you don't care, root using CF Auto Root and ODIN
Or TWRP 2.8.7.0 & ODIN, then SuperSU zip from TWRP recovery
Like I say, everything is posted thousands of times over, if you'd checked the thread below this one, you'd have known what KNOX was
http://forum.xda-developers.com/galaxy-s5/help/rom-opt-t3188679
Click to expand...
Click to collapse
So there is no way to root without loosing knox/warranty?
If you have a pre June 2014 KitKat ROM running, you can root using Towelroot app, then upgrade to Lollipop using Flashfire to keep root / not trip KNOX
That's the only other method
*Detection* said:
If you have a pre June 2014 KitKat ROM running, you can root using Towelroot app, then upgrade to Lollipop using Flashfire to keep root / not trip KNOX
That's the only other method
Click to expand...
Click to collapse
Can i downgrade to that kitkat and root on lollipop without loosing knox ?
RootNightmareX said:
Can i downgrade to that kitkat and root on lollipop without loosing knox ?
Click to expand...
Click to collapse
Yup, sammobile .com and ODIN - instructions under the download in the firmware section
*Detection* said:
Yup, sammobile .com and ODIN - instructions under the download in the firmware section
Click to expand...
Click to collapse
So i must do this to be sure i don't trip knox: downgrade to kitkat (and i will not lose knox) and then root and then update to lolipop and my warranty is still there (knox 0x0) ?
RootNightmareX said:
So i must do this to be sure i don't trip knox: downgrade to kitkat (and i will not lose knox) and then root and then update to lolipop and my warranty is still there (knox 0x0) ?
Click to expand...
Click to collapse
Flashing a stock Samsung ROM will not trip KNOX, so you're safe to flash any stock ROM without worrying about KNOX, KNOX is only tripped by flashing custom stuff not signed by Samsung
But to upgrade to Lollipop without losing root or tripping KNOX, you have to use Flashfire after running Towelroot on KK, otherwise you'll lose root, and then have no other options than flashing back to KK or tripping KNOX by using CF Auto Root
*Detection* said:
Flashing a stock Samsung ROM will not trip KNOX, so you're safe to flash any stock ROM without worrying about KNOX, KNOX is only tripped by flashing custom stuff not signed by Samsung
But to upgrade to Lollipop without losing root or tripping KNOX, you have to use Flashfire after running Towelroot on KK, otherwise you'll lose root, and then have no other options than flashing back to KK or tripping KNOX by using CF Auto Root
Click to expand...
Click to collapse
And if i root from kitkat, can i flash custom recovery and flash custom roms without tripping knox ?
How to Reset Knox 0x0 when using LOLLIPOP stock rom? Can someone help me?
Mvys said:
How to Reset Knox 0x0 when using LOLLIPOP stock rom? Can someone help me?
Click to expand...
Click to collapse
Impossible with n9005.....maybe with exynos....
But they said we should downgrade to kitkat first? So we can root it through Towelroot then the know will not tripped 0x1. Then flash lollipop firmware?
Teorically (and practically) detrip Knox is possible (there are many cases of people who went to Samsung and had their already 0x1 phones detripped without hw replacements. But unfortunately nobody know (or better, want to make know) how does it work. Soooooooo, your ****ed
You have to downgrade to Kit kat
Than Flash an special Kernel (dont know which)
After flashing the Kernel Wifi will Not work so be sure you have mobile data. Than download towelroot run it and flash Newer kernel.
Than you are rooted with Knox 0x0. Maybe you can try update from kit kat to lolipop with mobile odin. İ tried but Tripped Knox Unfortunately. So make sure you are always using Original samsung kernel and recovery ... (by mine was an ****ing kernel that Tripped knox)