[COLDAUSTIN]

Warning

Keep it cool or you will face consequences. Last time i said this and if you want to write AVOID caps and use spoiler brackets.

Originally Posted by GregoryRasputin No offence, but you are a f*cking idiot, True Blue had DRM, all the eBoots N0DRM cracked where the True Blue diseased DRM eBoots. F*ck the dongles and f*ck all you retards that support reDRM. Finally find yourself a brain and use it.....

then proof it, if that was True Blue DRM, by releasing the HEX codes of DRM TB,

it's very strange, because until now, there is NO ONE, who dared to release the hex codes of TB DRM inside the eboots.

fyi, Gregory,
all eboots N0DRM was NOT the same with all eboots TB,
I have 2 proof from one of all eboots
here the facts:

PROOF number ONE:
I could use N0DRM's EBOOT to play the games with TB Dongles,
if DRM TB was removing, I could not play the games with Dongles, right ?

PROOF number TWO:

Click here to see full text

----------------------------------
Need For Speed the Run's eboot by N0DRM was using
FW Version 34000 [03.40]
Key Revision [3.40 - 3.42]
[*] Metadata Info:
Key CB 3C 6F E4 4A B1 A5 A4 BB 14 C3 2F 24 CE 6B 46
IV 5F F8 02 02 12 34 12 A3 6D 29 76 49 C8 B3 06 F8 [*] Metadata Header:
Signature Input Length 0x0000000000000950
unknown_0 0x00000001
Section Count 0x00000007
Key Count 0x00000034
Optional Header Size 0x00000030
unknown_1 0x00000000
unknown_2 0x00000000[*] Metadata Section Headers:
Idx Offset Size Type Index Hashed SHA1 Encrypted Key IV Compressed
000 00000980 00AAD17F 02 00 [YES] 00 [YES] 06 07 [YES]
001 00AB81A0 00061255 02 01 [YES] 08 [YES] 0E 0F [YES]
002 00B19404 00000000 02 02 [YES] 10 [YES] 16 17 [NO ]
003 00B19404 00000000 02 03 [YES] 18 [YES] 1E 1F [NO ]
004 00B19404 00000000 02 04 [YES] 20 [YES] 26 27 [NO ]
005 00B19408 000030C4 03 21 [YES] 28 [NO ] -- -- [NO ]
006 00B1C648 000008C0 01 03 [YES] 2E [NO ] -- -- [NO ]

inside SELF HEADER: SH OFFSET 0x0000000000B1C648
[*] Optional Header
Type Capability Flags
Size 0x00000030
Next [FALSE]
unknown_3 0x0000000000000000
unknown_4 0x0000000000000000
Flags 0x000000000000003B [ 0x01 0x02 REFTOOL DEBUG RETAIL ]
unknown_6 0x00000001
unknown_7 0x00040000

etc.......
--------------------------------

Need For Speed the Run's eboot TrueBlue by PARADOX was using
FW Version 37300 [03.73]
Key Revision [DEBUG (devkit)]
THERE was NO METADATA info
inside SELF HEADER: SH OFFSET 0x000000000188E19F
THERE WAS NO Optional Header
etc........

---------------------------------

it was 'F*CKING' different, eboots !!!

---------------------------------

Originally Posted by GregoryRasputin all the eBoots N0DRM cracked where the True Blue diseased DRM eBoots.

I need the proof for your statements, above, all the eboots N0DRM was all True Blue eboots ??

No offence, so now who is 'f*cking idiot'

[CrashSerious]

Originally Posted by COLDAUSTIN No offence, so now who is 'f*cking idiot'

You. You are a loud mouthed idiot. They ARE different eboots, right. It's be cause they became ELFS and then were resigned with 3.40 keys.

Why do they work on the TB Firmware??? BECAUSE DIP****--- the 3.40 KEYS ARE IN THERE TOO!

(see... you're not the only one that can use pretty colors.)

[Kamertonas]

Originally Posted by COLDAUSTIN then proof it, if that was True Blue DRM, by releasing the HEX codes of DRM TB, it's very strange, because until now, there is NO ONE, who dared to release the hex codes of TB DRM inside the eboots. fyi, Gregory, all eboots N0DRM was NOT the same with all eboots TB, I have 2 proof from one of all eboots here the facts: PROOF number ONE: I could use N0DRM's EBOOT to play the games with TB Dongles, if DRM TB was removing, I could not play the games with Dongles, right ? PROOF number TWO: ---------------------------------- Need For Speed the Run's eboot by N0DRM was using FW Version 34000 [03.40] Key Revision [3.40 - 3.42] [*] Metadata Info: Key CB 3C 6F E4 4A B1 A5 A4 BB 14 C3 2F 24 CE 6B 46 IV 5F F8 02 02 12 34 12 A3 6D 29 76 49 C8 B3 06 F8 [*] Metadata Header: Signature Input Length 0x0000000000000950 unknown_0 0x00000001 Section Count 0x00000007 Key Count 0x00000034 Optional Header Size 0x00000030 unknown_1 0x00000000 unknown_2 0x00000000[*] Metadata Section Headers: Idx Offset Size Type Index Hashed SHA1 Encrypted Key IV Compressed 000 00000980 00AAD17F 02 00 [YES] 00 [YES] 06 07 [YES] 001 00AB81A0 00061255 02 01 [YES] 08 [YES] 0E 0F [YES] 002 00B19404 00000000 02 02 [YES] 10 [YES] 16 17 [NO ] 003 00B19404 00000000 02 03 [YES] 18 [YES] 1E 1F [NO ] 004 00B19404 00000000 02 04 [YES] 20 [YES] 26 27 [NO ] 005 00B19408 000030C4 03 21 [YES] 28 [NO ] -- -- [NO ] 006 00B1C648 000008C0 01 03 [YES] 2E [NO ] -- -- [NO ] inside SELF HEADER: SH OFFSET 0x0000000000B1C648 [*] Optional Header Type Capability Flags Size 0x00000030 Next [FALSE] unknown_3 0x0000000000000000 unknown_4 0x0000000000000000 Flags 0x000000000000003B [ 0x01 0x02 REFTOOL DEBUG RETAIL ] unknown_6 0x00000001 unknown_7 0x00040000 etc....... -------------------------------- Need For Speed the Run's eboot TrueBlue by PARADOX was using FW Version 37300 [03.73] Key Revision [DEBUG (devkit)] THERE was NO METADATA info inside SELF HEADER: SH OFFSET 0x000000000188E19F THERE WAS NO Optional Header etc........ --------------------------------- it was 'F*CKING' different, eboots !!! --------------------------------- I need the proof for your statements, above, all the eboots N0DRM was all True Blue eboots ?? No offence, so now who is 'f*cking idiot'

im afraid this is true nodrm managed to convert true blue eboots but nothing more check here http://www.truebluejb2.com/patches.html
this is more or less complete list of tb releases. You wont see any release by this team beyond this list.
also read theirs nfo on releases

''Finally bury your TB dongle because we removed their unnecessary DRM and their Patches will now work on Cfw 3.55 without any dongle or special TB CFW. (This has nothing to do with the previously leaked 3.60 Keys).''

[hellsing9]

Attention

Any attemp of DERAIL and abuse from caps, i will start with infracts and delete useless posts. You were warned.

[Simonbuck]

Originally Posted by Benzonia Bookmarked, thanks for this! I'm having trouble getting Skyrim (BLUS30778) to work on 3.55. After installing the 1.06 update pkg and placing N0DRM's EBOOT and PARAM fixes into hdd0/game, I'm still getting a message that firmware 4.00 is required. What up?

sounds like you need a firmware spoofer, try this

http://rebug.me/4-11-version-spoofer-2-2/

[COLDAUSTIN]

Originally Posted by Kamertonas im afraid this is true nodrm managed to convert true blue eboots but nothing more check here http://www.truebluejb2.com/patches.html this is more or less complete list of tb releases. You wont see any release by this team beyond this list. also read theirs nfo on releases ''Finally bury your TB dongle because we removed their unnecessary DRM and their Patches will now work on Cfw 3.55 without any dongle or special TB CFW. (This has nothing to do with the previously leaked 3.60 Keys).''

eboot.bin NFS run TB PARADOX : 25.147MB
eboot.bin NFS run N0DRM : 11.380MB
------------------------------------------- -/-
so the unnecessary size DRM TB was 13MB ?

well, my opinions, TB was the coolest one, I'll not bury my Dongles, because
haven't you know, eboot KMEAW and eboot N0DRM/DUPLEX can be play with TB dongles, too ?

I quess, you did not know, about feature of special TB cfw

[GregoryRasputin]

Originally Posted by COLDAUSTIN eboot.bin NFS run TB PARADOX : 25.147MB eboot.bin NFS run N0DRM : 11.380MB ------------------------------------------- -/- so the unnecessary size DRM TB was 13MB ? well, my opinions, TB was the coolest one, I'll not bury my Dongles, because haven't you know, eboot KMEAW and eboot N0DRM/DUPLEX can be play with TB dongles, too ? I quess, you did not know, about feature of special TB cfw

You are a f*cking retard, GTFO of this forum and take yourself back to your CrunchTard brethren.

[Benzonia]

Originally Posted by AkoDinIto Try restarting your ps3 if it does not work install this package http://www.sendspace.com/file/iqby61

Can anyone confirm that this is a legit fix? Don't really want to install random, unverified pkgs.

Originally Posted by Simonbuck sounds like you need a firmware spoofer, try this http://rebug.me/4-11-version-spoofer-2-2/

Cool, thanks for the help and link. I thought spoofers only prevented accidental fw updates tho, not bypassed game checks? I'll give it a try!

[JonahUK]

Originally Posted by COLDAUSTIN eboot.bin NFS run TB PARADOX : 25.147MB eboot.bin NFS run N0DRM : 11.380MB ------------------------------------------- -/- so the unnecessary size DRM TB was 13MB ?

Originally Posted by COLDAUSTIN haven't you know, eboot KMEAW and eboot N0DRM/DUPLEX can be play with TB dongles, too ?

First, the size difference is due to the compression.

Second, of course they will work due to the fact that the required keys are already present in the firmware, nothing to do with the dongle.
TB eboots were signed with an unkown key (DRM) which is why you needed the dongle. This key is not present in regular firmware. N0DRM removed that key and resigned with known keys that ARE present in ANY firmware.

Third, stop stealing oxygen.

[deeptrap]

Still i think TB team used another method to fix the games..

if it would only be converting, why we still cant play le tour 2011 and harry potter part 2 ?

And why did we need discs for some games TB released. while they could be fixed with the n0drm method ?