M
mike_galaxy_s
Gast
Es gibt sehr, sehr gute Neuigkeiten!
Hier die Quelle http://forum.xda-developers.com/showthread.php?p=47765738
Hier die Quelle http://forum.xda-developers.com/showthread.php?p=47765738
I have good news. I found a way for reseting counter on new KNOX devices. So you know KNOX' s information is stored in an emmc symlink file. Some people says it is storing in mmcblk0boot0, some people says that is same with mmcblk0 and some people can't find mmcblk0boot0. Actually I have not got a KNOX enabled device but I have testers for KNOX counter reset tool ( Making for S4 currently ). One of my tester opened that symlink ( He's not my tester now and I don't know which symlink is that. ) and edited with a hex editor and he saw a flag which shows counter status ( Hex value ). He edited that to 0x0 and rebooted the device. We saw 0x0 in bootloader screen. But when we rebooted the device it gone to back. So I know there is a hardware protection ( Special thanks to [MENTION=289089]gokhanmoral[/MENTION] ). I think harware protection provided by eFuse chip. So there are two ways for reseting counter.
1) Rewrite kernel and undefine the eFuse chip. eFuse chip is defined in the kernel. Then there should be no hardware protection and we can edit that emmc symlink to reset counter. Shortly, we can modify bootloader.
2) Modify an Odin flashable tar as you want. But you need Samsung's special key to sign. If you sign that with Samsung's special key, counter will not be changed. But it's hard to get Samsung's special key. We can find it in an official flashable tar. It's not impossible but it's near to the impossible I think.
I'm going to make an app for doing first way automatticly.
Zuletzt bearbeitet von einem Moderator: