Database Users

Knox Status still 0x0, how to proceed ?

Hello Guys,
Let's start with the story :
Old Bootloader, Stock Kernel , PhilZ CMW and Rom XXUDMBA with Chainfire Root.
Then i've installed through CMW the Know Free XXMI1, with Adam Kernel and Modem XXMI1 and still CMW Philz.
Suddenly my phone started to get crazy. Not able to receive calls, pohone freeze , screen blinking etc... Tried with factory and wipe but stucked on S4 logo (not even the samsung one)
Installed, through Odin, the MH8 pre-rooted, Modem MH8, Stock Kernel.
Now i've the new Bootloader, Knox Status stil 0x0, New Modem and New Rom. Everything is working but i've a question.
If i would like to have back the Philz Custom Recovery, flashing with odin, the Knox status will reach 0x1 ?
And why now my device says that my status is modified. I have stock kernel, recovery, rom (just knox free).
and if i would like to update the Rom with a stock one, with knox and all the other s***t, do i need to go necessary through Odin ? because OTA are compromised.
Last question is : Is the wifi-fix mandatory ? i don't know how to know if my wifi has problem. So far seems to work perfectly.

riccardoroma said:
Hello Guys,
Let's start with the story :
Old Bootloader, Stock Kernel , PhilZ CMW and Rom XXUDMBA with Chainfire Root.
Then i've installed through CMW the Know Free XXMI1, with Adam Kernel and Modem XXMI1 and still CMW Philz.
Suddenly my phone started to get crazy. Not able to receive calls, pohone freeze , screen blinking etc... Tried with factory and wipe but stucked on S4 logo (not even the samsung one)
Installed, through Odin, the MH8 pre-rooted, Modem MH8, Stock Kernel.
Now i've the new Bootloader, Knox Status stil 0x0, New Modem and New Rom. Everything is working but i've a question.
If i would like to have back the Philz Custom Recovery, flashing with odin, the Knox status will reach 0x1 ?
And why now my device says that my status is modified. I have stock kernel, recovery, rom (just knox free).
and if i would like to update the Rom with a stock one, with knox and all the other s***t, do i need to go necessary through Odin ? because OTA are compromised.
Last question is : Is the wifi-fix mandatory ? i don't know how to know if my wifi has problem. So far seems to work perfectly.
Click to expand...
Click to collapse
Modified because its pre-rooted...
Flashing anything through ODIN will change the void warranty from 0x0 to 0x1 unless its a stock rom (from MH8 up otherwise you will soft brick)....
You might be able to get rid of the modified status if you flash a totally stock rom but who wants to do that?

So the next question is :
If i would like to flash a new pre-rooted or custom rom i'll void my knox anyway. Because now i have stock recovery and this mean that i can flash only through Kies to a stock Rom right ?
Flashing a custom recovery with Odin (Knox 0x1)
Flashing a stock pre-rooted rom with Odin (Knox 0x1)
Flashing a stock rom newer then mine with kies or Odin (Knox 0x0)
am i right ? so i'm stucked on this ROM in other words, unless i'll just don't care about Knox.

CyanogenMod 11 with Knox 0x0

I am collecting information on if and how it is possible to flash CyanogenMod 11 to the Galaxy S5 without setting the Knox Warranty Void flag to 0x1 (which mostly means loosing your warranty). Please feel free to contribute!
Definitely possible is:
Root Galaxy S5 (G900F) while keeping Knox 0x0. This works via Towelroot method.
Install some custom ROMs (NeatROM or ALEXNDR) while kepping Knox 0x0. This works via flashing with Mobile Odin PRO. Instructions are available in both ROM threads.
Now the question is if we can use the Mobile Odin PRO flash method for CyanogenMod ROM and what has to be done to avoid Knox 0x1.
In the CM11 zips there are folders for recovery, system and META-INF as well as boot.img and file_context files.
system: flashing ok
The system folder contains the contents of the system partition and should be fine to flash as the other ROMs with Knox 0x0 have that, too. I don't think any checks on the contents of the system partition are done by Knox (please correct me if i'm wrong!).
boot.img: flashing not safe
The boot.img file contains primarily the kernel image and the ramdisk; details can be found here and instructions on modifying are for example here.
I think at least the kernel image is checked by Knox (i don't know how and when, maybe if it is signed by samsung or if the checksum matches known kernels; any information on that would be helpful!). The ALEXNDR ROM for example uses the same boot.img as the stock G900FXXU1ANG2 firmware. CM11 uses a different kernel (CAF), which quite certainly would not pass any Knox checks. In conclusion i think it is advised NOT to flash the CM11 boot.img if you want to keep Knox 0x0.
This leads to the question if you can use a stock kernel in combination with CM11. It has been reported to work with earlier versions of CM on other devices, but i could not find much information on this, it might or might not work. If anyone has better information on this, please post it!
recovery: flashing not safe
Flashing custom recoveries will trigger Knox 0x1 (as far as i know). I could not yet find out when the recovery is actually installed, the ROM installer only copies the recovery installer into /system/etc/install-cm-recovery.sh and the recovery image to /system/recovery-from-boot.p. My guess is it will be installed on first boot.
As the recovery should not be necessary to run CM11, it should not be flashed. More detailed information welcome!
META-INF: only flash with modiffications
This contains primarily the ROM installer script at /META-INF/com/google/android/updater-script. This is run when you 'flash a zip' (see here for details) and is pretty straightforward to read. Most actions seem harmless, but 2 or 3 might have to be removed/modified, like package_extract_dir("recovery", "/system"); or package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");.
/system/bin/backuptool.sh seems safe, it only backs up and restores addon /system files.
file_contexts: flashing ok
Not sure about this, i don't think it is actually flashed or anything. The other ROMs with Knox 0x0 don't have it, but i don't know how it would trigger Knox 0x1. This seems to be a SELinux config file containing types and ranges for system files etc.
So atm the following would be interesting (DON'T DO THIS, IT WOULD MOST DEFINETELY NOT WORK OR EVEN BRICK YOUR DEVICE! This is just hypothetic.):
Rooted S5 with stock G900FXXU1ANG2 firmware.
Remove the boot.img and recovery part from CM11 zip.
Flash the modified zip via Mobile Odin PRO.
I tried this and it failed. Had to restore device with stock rom and Odin, still Knox 0x0 though.
Has anyone tried something similar? Do you have additional information that might be helpful? Then please contribute!
DISCLAIMER: I can NOT guarantee any of this information to be correct! Whatever you do with this information is completely YOUR OWN RESPONSIBILITY.

aregvadfbg said:
I am collecting information on if and how it is possible to flash CyanogenMod 11 to the Galaxy S5 without setting the Knox Warranty Void flag to 0x1 (which mostly means loosing your warranty). Please feel free to contribute!
Definitely possible is:
Root Galaxy S5 (G900F) while keeping Knox 0x0. This works via Towelroot method.
Install some custom ROMs (NeatROM or ALEXNDR) while kepping Knox 0x0. This works via flashing with Mobile Odin PRO. Instructions are available in both ROM threads.
Now the question is if we can use the Mobile Odin PRO flash method for CyanogenMod ROM and what has to be done to avoid Knox 0x1.
In the CM11 zips there are folders for recovery, system and META-INF as well as boot.img and file_context files.
system: flashing probably ok
The system folder contains the contents of the system partition and should be fine to flash as the other ROMs with Knox 0x0 have that, too. I don't think any checks on the contents of the system partition are done by Knox (please correct me if i'm wrong!).
boot.img: flashing not safe
The boot.img file contains mainly the kernel image and the ramdisk; details can be found here and instructions on modifying are for example here.
I think at least the kernel image is checked by Knox (i don't know how and when, maybe if it is signed by samsung or if the checksum matches known kernels; any information on that would be helpful!). The ALEXNDR ROM for example uses the same boot.img as the stock G900FXXU1ANG2 firmware. CM11 uses a different kernel (CAF), which quite certainly would not pass any Knox checks. In conclusion i think it is advised NOT to flash the CM11 boot.img if you want to keep Knox 0x0.
This leads to the question if you can use a stock kernel in combination with CM11. I could not find much information on this, it might or might not work. If anyone has better information on this, please post it!
recovery: flashing not safe
Flashing custom recoveries will trigger Knox 0x1 (as far as i know). As the recovery should not be necessary to run CM11, it should not be flashed. More detailed information welcome!
META-INF: ?
Not sure about this. I guess it could be ok since the other ROMs with Knox 0x0 have that, too. This seems to contain the AROMA installer etc. When and where is this executed/applied?
file_contexts: ?
Not sure about this. The other ROMs with Knox 0x0 don't have it, but i don't know how it would trigger Knox 0x1. This seems to be a SELinux config file containing types and ranges for system files etc.
So atm the following would be interesting (DON'T DO THIS, IT WOULD MOST DEFINETELY NOT WORK OR EVEN BRICK YOUR DEVICE! This is just hypothetic.):
Rooted S5 with stock G900FXXU1ANG2 firmware.
Remove the boot.img and recovery part from CM11 zip.
Flash the modified zip via Mobile Odin PRO.
Has anyone tried something similar? Do you have additional information that might be helpful? Then please contribute!
DISCLAIMER: I can NOT guarantee any of this information to be correct! Whatever you do with this information is completely YOUR OWN RESPONSIBILITY.
Click to expand...
Click to collapse
You'll never flash cm11 and keep the Knox 0x0 in any way, shape or form. And once again to all people worried about warranty your clearly on the wrong forum

thatsupnow said:
You'll never flash cm11 and keep the Knox 0x0 in any way, shape or form. And once again to all people worried about warranty your clearly on the wrong forum
Click to expand...
Click to collapse
Could you give reasons why you think that it will never be possible?
I do not think using custom software and being concerned about hardware warranty does exclude each other, but that's only my opinion.

aregvadfbg said:
Could you give reasons why you think that it will never be possible?
I do not think using custom software and being concerned about hardware warranty does exclude each other, but that's only my opinion.
Click to expand...
Click to collapse
Because once a custom recovery or kernel is flashed by no matter what means or app KNOX will be triggered to 0x1. If it we`re possible it would have been done a long time ago.

gee2012 said:
Because once a custom recovery or kernel is flashed by no matter what means or app KNOX will be triggered to 0x1. If it we`re possible it would have been done a long time ago.
Click to expand...
Click to collapse
But why do you assume that you have to flash a custom recovery or kernel?
A custom recovery seems only necessary for flashing, which can be done with Mobile Odin PRO.
CM11 may ship with a custom kernel, but that does not mean you can not use another kernel. For example you could try to use the stock kernel instead which has been reported to work with earlier versions of CM on other devices, so it's at least possible. If the stock kernel does not work out of the box, then there would still be the possibility to build CM from source against the stock kernel sources.

aregvadfbg said:
But why do you assume that you have to flash a custom recovery or kernel?
A custom recovery seems only necessary for flashing, which can be done with Mobile Odin PRO.
CM11 may ship with a custom kernel, but that does not mean you can not use another kernel. For example you could try to use the stock kernel instead which has been reported to work with earlier versions of CM on other devices, so it's at least possible. If the stock kernel does not work out of the box, then there would still be the possibility to build CM from source against the stock kernel sources.
Click to expand...
Click to collapse
Don`t want to waste too much time on this discussion, start coding and building an post the solution here on this forum and you`ll get the XDA Nobel prize. Good luck mate

gee2012 said:
Don`t want to waste too much time on this discussion, start coding and building an post the solution here on this forum and you`ll get the XDA Nobel prize. Good luck mate
Click to expand...
Click to collapse
so you are saying it might be possible?

For the Galaxy Note 3 there is a thread where people are doing just that, flashing custom roms via Mobile Odin PRO without the kernel and recovery, and it is working for them. Those ROMs are not CM11 and they use the AROMA installer to skip kernel and recovery flashing, but the principle should be the same.

..

It's so simple:
CM11 is working only along CM kernel, there is no way to run CM11 on Samsung kernel. End of story.

fffft said:
You asked if CM 11 can be installed without affecting the Knox flag. And the answer is no.
Can you install CM 11 without incrementing the Knox flag? No
Can you carefully select bits and pieces to install and keep your Knox flag at it's original 0x0? Yes
Once you start eschewing the CM kernel, recovery, etc you are no longer talking about a CM install anymore. You can't gut the important pieces and pretend that it is still CM.
Click to expand...
Click to collapse
I look at it this way: if i have a system that is looking and behaving like cm11, then i don't care if it's theoretically not exactly cm11.
fffft said:
If Knox is so important to you, you are definately on the wrong site.
Click to expand...
Click to collapse
If there is a reversible way to achive my goal i will first try that, and only then consider a non-reversible way.
lukas77 said:
CM11 is working only along CM kernel, there is no way to run CM11 on Samsung kernel. End of story.
Click to expand...
Click to collapse
Unfortunately this might be true. Do you have information what the differences between those kernels are and why they are incompatible?
I have tried the following and it didn't work:
Removing boot.img and recovery from cm11 zip and removing the corresponding parts from the installer script, also removing device checks and signature checks as the functions are not available if you are flashing through MOP. Device went black during flashing of /system, wouldn't boot afterwards, had to flash stock rom through Odin to restore device. But still Knox 0x0.

aregvadfbg said:
I look at it this way: if i have a system that is looking and behaving like cm11, then i don't care if it's theoretically not exactly cm11.
If there is a reversible way to achive my goal i will first try that, and only then consider a non-reversible way.
Unfortunately this might be true. Do you have information what the differences between those kernels are and why they are incompatible?
I have tried the following and it didn't work:
Removing boot.img and recovery from cm11 zip and removing the corresponding parts from the installer script, also removing device checks and signature checks as the functions are not available if you are flashing through MOP. Device went black during flashing of /system, wouldn't boot afterwards, had to flash stock rom through Odin to restore device. But still Knox 0x0.
Click to expand...
Click to collapse
Much brighter minds then you thought, coded, build and experimented with what you are thinking off now and it simply cannot be done for various reasons:
1. KNOX will always be triggered when a modified custom kernel is installed, there is no fix atm and there will most likely never be one.
2. CM is following the CAF tree which means their kernels aren`t compatible with AOSP.
I`am sure there are more problems but above 2 are the most important ones imo.
Now either live with it or buy a Nexus device for instance which doesn`t have KNOX.

..

[Q] Rooted S4 GT-I9505, How to update from 4.2.2 to more recent ? - keep root

Hello,
I'm using a SGS4 rooted since more than one year and a half (odin, flash a small root bin file if I remember well, flash counter set to 1, no custom recovery and no nandroid backup)
Since I want to implement NFC card emulation now avaliable in android 4.4 in one of my apps, I'd like to update.
I've seen few threads on the subject, and most of them date from a long time (am I late ? ). I'd like to know how I could update normally my actual rom (provided by Orange, precisely I9505XXUAME2), or move to another slightly modified rom like the base rom provided by samsung without all these apps that you can only remove with root.
I don't want to have any data issue I've read about, I don't want to lose my actual apps and their data. (Nandroid backup then restoring apps and their data through nandroid manager?)
Also, if possible i'd like to update without losing my start screen, my parameters, etc... (in the worst case I'd re-set them manually). And finally of course I want to have it rooted at the end of the process.
In fact I want it to be just like if I had done an OTA update, then rooted it.
Also, How to update without setting the Knox counter to 1 ? (My flash counter is set to 1, should I use Triangle Away?)
Is there any simpler way than flashing the new firmware and then importing everything from my old data to the new and reinstalling the changes I made to the system (like avast & such) ?
Also, maybe there exists newest versions of the firmware, but without the new bootloader that has the knox counter ?
Thanks in advance!

tboss1995 said:
Thanks in advance!
Click to expand...
Click to collapse
1. You can't receive OTA updates if you have rooted your device. You have to flash the firmwares via ODIN.
2. You don't need wipe nothing if you flash new stock firmware. Instructions: Flash new firmware (if you don't have wifi flash it one time more), root it again then and you're done. Your data don't have to be affected (maybe you only have to reinstall some app if the data/cache was moved to the SDCARD).
3. Flashing one new stock firmware don't modify KNOX. You actived KNOX rooting your device or flashing one custom recovery. Knox: 0x1 can't be reset. Triangle away only reset the flash counter.

Thanks for your fast answer !
So, flashing a firmware doesn't impact the data.
Updating via Kies sets the Knox counter. Updating via odin doesn't ? Don't I have to do any sort of un-root before updating ?
Is there anything specific I should know about root ? Because I don't want to flash a firmware that I won't be able to root without setting the knox counter.
Also I think that since we can't revert the bootloader update, maybe i'd better not update that bootloader so that I can update future versions and root them without setting knox counter, by installing a knox-free rom even before a knox-free root is released...
Where can I find these roms?

tboss1995 said:
Thanks for your fast answer !
So, flashing a firmware doesn't impact the data.
Updating via Kies sets the Knox counter. Updating via odin doesn't ? Don't I have to do any sort of un-root before updating ?
Is there anything specific I should know about root ? Because I don't want to flash a firmware that I won't be able to root without setting the knox counter.
Also I think that since we can't revert the bootloader update, maybe i'd better not update that bootloader so that I can update future versions and root them without setting knox counter, by installing a knox-free rom even before a knox-free root is released...
Where can I find these roms?
Click to expand...
Click to collapse
1. Updating via ODIN or Kies don't set the KNOX counter. Downgrading YES.
2. Root dissapear if you flash new update via ODIN.
3. You can flash latest firmware and root them without KNOX. Take a look for the method: HERE.

Thanks for the answer again!
Howerver I still have 3 questions because I like to understand what I'm doing :
1. I understand the two terms ROM (OS of the phone) and bootloader (after a certain update, it adds the knox counter, and you can't downgrade it, and it also prevents towelroot from working). What is the called "kernel" ?
2. Up to exactly what version of the bootloader/rom does towelroot work ?
3. What is the difference between "knox-free" and "knox counter 0"? At the end of the method, will I have the new bootloader with a knox counter set to 0, or the old bootloader ?

tboss1995 said:
Thanks for the answer again!
Howerver I still have 3 questions because I like to understand what I'm doing :
1. I understand the two terms ROM (OS of the phone) and bootloader (after a certain update, it adds the knox counter, and you can't downgrade it, and it also prevents towelroot from working). What is the called "kernel" ?
2. Up to exactly what version of the bootloader/rom does towelroot work ?
3. What is the difference between "knox-free" and "knox counter 0"? At the end of the method, will I have the new bootloader with a knox counter set to 0, or the old bootloader ?
Click to expand...
Click to collapse
1. Take a look: HERE.
2. Nobody know it.
3. - KNOX free: This therm is used for the custom ROMS normally. This mean that flashing this ROM dont touch the KNOX counter.
- KNOX counter: You still having your device in warranty if you have KNOX:0x0. You void your warranty if you have KNOX:0x1 in DOWNLOAD MODE.

So it means I'll still have the new bootloader ?
For those who may come to read this article and don't want to watch a video, I've found an article explaining what kernels are. http://m.androidcentral.com/android-z-what-kernel

Root not working

Hi, I tried a million times to root my note 3(900N) after I install a bootloader(from note 4 modded for note 3), a modem and a modded kernel.
I tried to flash a rom, didnt worked(Error flashing zip). After a while, i got problem from that kernel. Now I installed stock lollipop (via odin), I installed a recovery(TWCM) but I cant flash anything. I even tried to flash the SuperSu.zip, it act like a crash.
Before I install that files(bootloader, modem, kernel) I rooted, flashed, etc.
Please help me to root the phone.
May be a problem from kernel or bootloader? Can I install the stock of this files? If I can, where I can get them?
Thank you.
L.E: "I searched and I find this: "Some facts about KNOX status:
It isn’t possible to downgrade to KNOX-disabled firmwares/bootloaders (An attempt sets 0x1) (even though some people state, downgrade is possible when omitting the bootloader file in a firmware package). By downgrading from KNOX-enabled to KNOX-disabled firmware, your devices will be locked to installation of newer firmwares."
I Have KNOX 0x1. I don`t know how I did this. But I can fix this problem?

How to make my s5 root without getting KNOX 1 ?

On my device i have build number G900FXXU1BOC7 and i want to root my device.
I can't understand how to do it without getting KNOX 1 .
I understand that its possible to use custom Rom that already contain root access - but there are so many Rom's here and i don't know witch of them is without KNOX 1 - and i don't know if i will get on of those Rom .. if i will be able to get back in any case to the original build ( G900FXXU1BOC7 )

Yanshof said:
On my device i have build number G900FXXU1BOC7 and i want to root my device.
I can't understand how to do it without getting KNOX 1 .
I understand that its possible to use custom Rom that already contain root access - but there are so many Rom's here and i don't know witch of them is without KNOX 1 - and i don't know if i will get on of those Rom .. if i will be able to get back in any case to the original build ( G900FXXU1BOC7 )
Click to expand...
Click to collapse
You have to download Towelroot and downgrade your kernel to root your phone without tripping Knox.
The kernel you need
https://www.dropbox.com/s/cun1uainm2h07em/KERNEL_G900FXXU1ANE2.tar.md5
The Towelroot app
http://beste-apps.chip.de/android/app/towelroot-apk-android-app,cxo.70416483/
1.Download Odin and select the kernel you downloaded under AP.
2.Get your phone in Download mode and flash the kernel.
3.Then try to boot your phone (i am not sure if this works cause the kernel is for android 4.4.2) install Towelroot and click on Make it Rain.
4.If your phone dont boots you have to install a 4.4.2 fimeware first and then flash the kernel.

Marvin_1003 said:
You have to download Towelroot and downgrade your kernel to root your phone without tripping Knox.
The kernel you need
https://www.dropbox.com/s/cun1uainm2h07em/KERNEL_G900FXXU1ANE2.tar.md5
The Towelroot app
http://beste-apps.chip.de/android/app/towelroot-apk-android-app,cxo.70416483/
1.Download Odin and select the kernel you downloaded under AP.
2.Get your phone in Download mode and flash the kernel.
3.Then try to boot your phone (i am not sure if this works cause the kernel is for android 4.4.2) install Towelroot and click on Make it Rain.
4.If your phone dont boots you have to install a 4.4.2 fimeware first and then flash the kernel.
Click to expand...
Click to collapse
BOC7 is Lollipop, downgrading his Kernel to a KK kernel will brick his phone
He needs to downgrade to KK first, in which case, OP might as well downgrade to the same version KK as the kernel you are suggesting to use belongs to (Pre June 2014 KK ROM)