True Blue - New Dongle and news of support for existing users!

[PatrickBatman]

So the thread reads confirmed now, confirmed by who? Confirmed it plays 1 or 2 games from eboots that are nearly impossible to get. (And I dont mean the Driver SF eboot I know thats on multiupload).

[Digital-Spooker]

So the thread reads confirmed now, confirmed by who?

Confirmed by Gary, he hasn't BS'd us in the past, his information has always been accurate.

[SiLENTGame]

Hey Guys,

little question: This key which was released a couple of hours ago is the masterdisc key, right?

[Digital-Spooker]

I didn't think debug eboots will run on a normal machine....i thought that's the extra bit that "they've" done along with their drm dongle...

Don't see why they wouldn't, we used debug updates to get some 3.56 games working on 3.55 (such as Duke Nukem)

Hey Guys,

little question: This key which was released a couple of hours ago is the masterdisc key, right?

From my understanding, yes, yes it is.

[badabing]

some ex-hacker and release scene member has gotten the 5 games to work with kmeaw from internal hd and he has posted a video in a private german dev board that proofs it. he is trying now to get ALL 3.60 eboots to work startin with battlefield 3.

[SiLENTGame]

sounds very nice.

The thing which we have to do now is to decryot the EBOOT with the masterdisc key and then we will get the fself What we have to do then?

[samdrlvt]

some ex-hacker and release scene member has gotten the 5 games to work with kmeaw from internal hd and he has posted a video in a private german dev board that proofs it. he is trying now to get ALL 3.60 eboots to work startin with battlefield 3.

Some way of ripping the video and share it with us?

[Digital-Spooker]

He should have changed the thread title already like 3 days ago into "jb2 dongle playing 5 3.60 games" cos everything else is a joke and scam to attract visitors only

--

anyone got the skills to implent this into kmEaw 3.55? it would make those jb2 games work from hd

Masterdisc Eboot decryption at PC to get fself:

key:
key sv_iso: 67C0758CF4996FEF7E88F90CC6959D66

algo:
// do crypt
unsigned char sector_key[16];
memset(sector_key, 0, 16);
sector_key[12] = (sector_num & 0xFF000000)>>24;
sector_key[13] = (sector_num & 0x00FF0000)>>16;
sector_key[14] = (sector_num & 0x0000FF00)>> 8;
sector_key[15] = (sector_num & 0x000000FF)>> 0;

// encrypt sector
aes_context aes_ctx;
aes_setkey_enc(&aes_ctx, G_DEBUG_KEY, 128);
aes_crypt_cbc(&aes_ctx, AES_ENCRYPT, aligned_size, sector_key, buff, buff);

// decrypt
aes_context aes_ctx;
aes_setkey_dec(&aes_ctx, G_DEBUG_KEY, 128);
aes_crypt_cbc(&aes_ctx, AES_DECRYPT, aligned_size, sector_key, buff, buff);

Doesn't need to be added to a cfw, it's an algorithm, we can use it to decrypt the fself eboots on the PC then transfer them over, so as long as you have some knowledge of skill with the SDKs and get the keys (btw, this is useless without the keys) from ps3gen.dll it (in theory) should work, I'd wager people with the skills, are working on it, and are staying tight lipped until they CAN do something so the JB2 people can't ramp up their security or something.

Patience is Virtue, we will have our games soon.

[nextbike]

http://www.ps3crunch.net/forum/threa...=9980#post9980

[PatrickBatman]

some ex-hacker and release scene member has gotten the 5 games to work with kmeaw from internal hd and he has posted a video in a private german dev board that proofs it. he is trying now to get ALL 3.60 eboots to work startin with battlefield 3.

From INTERNAL hardrive!?! He was using the dongle? Or the master disc algorithm and sv_iso key to decrypt? Where did you get this info?