Facts:
08.07.2012 = DEX conversion method get’s *Leaked*
1.8.2012 = 3.60 keys got leaked and confirmed working with the help of euss.
15.8.2012 = DUPLEX cracks TB dongle.
So…What you think about this?. And no..it’s not a WHOIS investigation.
Regards
Hellsing9
|
hellsing9, You have the wrong statements !
1. DEX convension was leaks because of one member from E3 Team who had the source.
2. 3.60, yes it was working BUT it can not be decrypting TB's EBOOT ! haven't you try it ?
3. DUPLEX was not cracks TB dongle, because if TB's DRM was really removing then Duplex's eboot could not be running with TB dongle, RIGHT ?
I looked at DUPLEX's EBOOT and TB's EBOOT, with hex editor, and compare it, and it was so many different.
TB's EBOOT has the BIGGER SIZE than DUPLEX's EBOOT !!
You could see key revision TB's EBOOT.bin was using DEBUG[dev], and it could not be converted without SELF keys for DEBUG [dev]. As far I know, the key revision for DEBUG [dev] 8000 is not leaks, yet !! Maybe DUPLEX has it ??
And key revision of Duplex's EBOOT.bin was using keys leaks, last leak keys 3.60, for example [3.40 - 3.42], and Duplex was using ORIGINAL EBOOT.bin to crack it.
Wondering, WHY was not using TB's EBOOT to crack for ??
I have a question for you, hellsing9,
WHY DUPLEX was NOT using TB's EBOOT.bin for removing TB's DRM ?
fyi, TB's EBOOT.bin was EBOOT.elf !!
TB team converted EBOOT.ELF to EBOOT.BIN WITHOUT COMPRESS it !
try to convert original eboot.bin to eboot.elf, see the bytesizes, it is the same with TB's EBOOT.BIN bytesizes or not !
also, with HEX EDITOR, I found inside Duplex's EBOOT.bin, his SIGNATURE !
but I could not found his SIGNATURE DUPLEX, inside EBOOT.elf (converted from Duplex's original eboot.bin)
I tried to remember it, eboot.bin was encrypt, right ?
and eboot.elf was decrypt, right ?
so how was possibly Duplex knew inside encrypt TB's eboot.bin, the hex numbers was TB's DRM ? it was ENCRYPT, right ?
Here my facts:
Duplex found OFFICIAL's DRM and blaming to TB for cover up, so the 'OFFICIAL' will not removing old DRM with the NEW DRM.
I'm newbie, here
but not in other's ps3 forum, I read this, and I disagree with hellsing9, so I decided to register one, in here, usually I just step by and look only the news inside ps3hax.
this is my opinions to all 'a war between both of them'