[Galaxy Note 3 General] BrunoWestone:
So many opinions...

Hey guys i'm back with news.

Sorry for taking so long but i have been very busy also with HTC (Pain in the ass)

So KNOX !!!!!!

1- IT CAN BE RESETED

2- NO NEED FOR HARDWARE KEY IF PROGRAMMED DIRECTLY VIA JTAG

3- NOTING IS IMPOSSIBLE.

4- WE SHOULD ALL CONCENTRATE IS DISCUSS SOLUTIONS, NOT IF SAMSUNG SERVICES CENTERS DENY WARANTY OR NOT.

The knox security verification starts in the primary bootloader at 0x000319C0 where you can see the following routine:

41 20 62 6F 6F 74 20 6D 65 61 73 75 72 65 6D 65 6E 74 5D 20 3A 20 4F 6C 64 2F 6E 6F 6E 2D 43 4C 20 64 65 76 69 63 65 20 2D 20 4B 4E 4F 58 20 77 61 72 72 61 6E 74 79 20 76 6F 69 64 0A 00 00 00 0A 6B 65 72 6E 65 6C 20 20 40 20 25 78 20 28 25 64 20 62 79 74 65 73 29 0A 00 00 00 72 61 6D 64 69 73 6B 20 40 20 25 78 20 28 25 64 20 62 79 74 65 73 29 0A 00 00 00 00 6D 65 6D 3D 31 30 30 4D 20 63 6F 6E 73 6F 6C 65 3D 6E 75 6C 6C 00 00 00 63 6F 6E 73 6F 6C 65 3D 00 00 00 00 63 6F 6E 73 6F 6C 65 3D 74 74 79 48 53 4C 30 2C 31 31 35 32 30 30 2C 6E 38 25 73 00 20 73 65 63 5F 6C 6F 67 3D 30 78 25 78 40 30 78 25 78 00 00 20 73 65 63 5F 64 62 67 3D 30 78 25 78 40 30 78 25 78 00 00 20 73 65 63 5F 64 65 62 75 67 2E 72 65 73 65 74 5F 72 65 61 73 6F 6E 3D 30 78 25 78 00 00 00 00…. [TIMA boot measurement] : kernel secure check fail..SECURE FAIL: KERNEL.[TIMA boot measurement] : Old/non-CL device - KNOX warranty void.....kernel @ %x (%d bytes)....ramdisk @ %x (%d bytes).....mem=100M console=null...console=....console=ttyHSL0,115200,n8%s. sec_log=0x%x@0x%x.. sec_dbg=0x%x@0x%x.. sec_debug.reset_reason=0x%x.... lcd_attached=%d

and at 0003E9C0…

...AST_UPLOAD..set current.....check_boot_mode = key Down[%d], Up[%d] .....Set debuglevel = 0x%x...Set cp debuglevel = 0x%x....SET PVS MODE = 0xFAFA...is_reboot_case =%d..cable_status = %d...set lpm_mode....cable booting, but cable isn't present..power-down!.....enter normal booting mode...AST_POWERON.....enter download mode.....enter ramdump mode..vibrator started....vibrator stopped....KNOX KERNEL LOCK: 0x%x..KNOX WARRANTY VOID: 0x%x....QUALCOMM SECUREBOOT: ENABLE.QUALCOMM SECUREBOOT: T32 ENABLE.QUALCOMM SECUREBOOT: DISABLE....QUALCOMM SECUREBOOT: NON-SECURE BINARY..CSB-CONFIG-LSB: 0x30....QUALCOMM SECUREBOOT: NONE...reboot_mode = 0x%x, boot_mode = %d, por = 0x%x..error in emmc_recovery_init.....ERROR: Could not do normal boot. Reverting t

After the system preform a checksum compare between the Primary Bootloader, Secundary bootloader and main kernel, the primary bootloader displays the warranty bit as we can see were: x%x..KNOX WARRANTY VOID: 0x% Where % is a variable.

So far i know if we change the % to 0 don't solve anything, because as soon as the phone reboot itself, all the procedure start again and the bit sets itself to the var again.

Some say this will never have a solution to crack and i believe it, but it doesn't mean we can't find another way to deal with this.

IF WE CANNOT RESET THE COUNTER, THERE IS ONLY ONE VIABLE WAY TO GET RID OF THIS KNOX voided:

WE HAVE TO FIND A WAY TO "CONVENCE THE PHONE" THAT HE STILL IS A 4.2.2 XXUAMDE WITH A NON-KNOX BOOTLOADER, (THE KERNEL AND SEANDROID WILL DISPLAY PANIC !!!) AND THEN FLASH THe PHONE WITH THE LATEST 4.3 KNOX ACTIVATED.

DOING THAT, IF THE PHONE BOOTLOADER IS ON 4.2.2 NOT ACTIVATED KNOX, THE PHONE WILL RE-WRITE ALL THE NEW PARTITIONS AND CREATE ALL NEW KNOX CONTAINERS FROM SCRATCH AND IN THE END WE SHOULL HAVE A SAMMY WITH KNOX 0X0

Any help from you on how to do that will be good.