After checking many title.tik (original and modified for installation) I got the exact "formula" to calculate the new value in
let's take the 1st 16 bytes of a ticket (dunno which one, it doesn't matter):
000300045CA5714B61BA6F982BDEA4C0
looking at that wii page and that 3ds page you see that:
04 = RSA_2048 SHA256 (signature type)
You must leave 04 as is.
Change 03 to 01.
About last byte (let's call it 0x0F):
(0x0F) XOR (02)
so, in our example:
(C0) XOR (02) = C2
where C2 is the correct value to make the certificate beeing recognized by the console.
So you have no more to "test" if adding or removing 2 from byte 0x0F, just xor its original value with 02.
The real history in this "mistery" is clearly explained by the great @crediar in his answer at page 6 of this thread.
Thank you for reading
let's take the 1st 16 bytes of a ticket (dunno which one, it doesn't matter):
000300045CA5714B61BA6F982BDEA4C0
looking at that wii page and that 3ds page you see that:
04 = RSA_2048 SHA256 (signature type)
You must leave 04 as is.
Change 03 to 01.
About last byte (let's call it 0x0F):
(0x0F) XOR (02)
so, in our example:
(C0) XOR (02) = C2
where C2 is the correct value to make the certificate beeing recognized by the console.
So you have no more to "test" if adding or removing 2 from byte 0x0F, just xor its original value with 02.
The real history in this "mistery" is clearly explained by the great @crediar in his answer at page 6 of this thread.
Thank you for reading
Last edited by asper,