PS4 News on Facebook! PS4 News on Twitter! PS4 News on YouTube! PS4 News RSS Feed!

Home PS4 News - Latest PlayStation 4 and PS3 News

173w ago - As a follow-up on our previous article with the spirit of Operation: Mongoose in mind, we are continuing to examine both the Cobra and True Blue PS3 DRM-infected dongles and TB EBOOT files, and welcome any help with this project from other PlayStation 3 developers in the scene!

First let me tell you the following explanation is not a theory or any rumors, it's actually how the USB dongles work to allow different things.

We heard many rumors / theories about the process of the Cobra / True Blue but I didn't see anyone give any big answer about that (I'm not saying I would give you the big answer but the explanation how it works and how to make this possible)

Cobra / True Blue Part 1

Both dongle use syscall / payload (after a big investigation, both dongle also follow the work of graf_chokolo and the functionality of the dongle can be ported into a CFW (not a good idea from some devs I guess)

Cobra / True Blue use a lv1_wrapper (syscall implementation) that can allow to use subroutine function into kernel mode call. Following the dump of the Cobra / True Blue, every subroutine are indicated inside the dump (probably the reason of some clone like JB-King)

What all this mean ?

About the TB Eboot, i come back on what i said recently, the TB Eboot come from original Eboot (don't make any sense that they access to the dev server when have not Eboot on it) the PSN dev don't exist this way... but for related beta development games and testing beta multiplayer mode, interface beta test PSN for games etc... but nothing related to a Eboot.

TB use original Eboot and make their own sign (you can easily generate a new NPDRM sign with a Self/elf)

How can boot the games, the NPDRM Sign made in TB can't be run into a user mode, you would have a error of boot and every program that you resign etc... will not boot into a usermode... that's why we need to use a syscall that can let use into a kernel mode to execute a program that not recognized and authorized by the system. The dongle validates the actual eboot by syscall / subroutine.

For example, I want to have a execute something into the CoreOS but I'm not allowed because I can only execute this on a kernel mode, fine, I use my actual user mode to turn into a kernel mode by using a syscall.

A Syscall can allow you to execute, create, read, load, etc... The limitation of a dongle = the PS3 system, a dongle it's only here to prevent a error that by using redirection and syscall, the dongle give a correct answer that PS3 system execute.

If you check correctly the dump you can see 0x80 -> correspond to the C library, also when you call into kernel mode, the kernel fix the table permission that allow to give big access. You can recognized r1 stack register -> 0xA0 (debugger mode) -> R2 stack status...

Ok you probably gonna ask, what is that ? lol

It's actually a schema / plan from the dongle, the dongle is here to give a strong access to the system that you can execute what you want.

For example the PS2 Emu of Cobra = PS2 self (is not executed into a user mode but kernel mode / debugger mode that) reason why it can be execute under a PS3 Slim retail without following an error system.

How this can help ?

This mean many things, that you don't need any keys to execute under a kernel / debugger mode because anyway the syscall will give you a whole access to the cell execution.

I want to give a simply explanation that everybody can understand, the TB EBoot = Original Eboot from Original game, we not interested by the sce header, etc... we only want the elf header program represent and related to the game execution (like a exe, you patch the exe to be run without cd) here almost the same, we patch the elf with a fake sign can be run into a specific mode without asking anything.

What is weird, graf gave many oriented possibility and no one try to exploit them but only in a business way. Anyway like I said, the dongle is in relation with the PS3 system/Dev_Flash/Core_OS

I'm also working on it and try to do my best to release something strong and free... but my knowledge is limited and I can't do that alone.

Why I explain all that, it's because I want to see also some good dev can work on it with me, actually I want to thanks graf for all this awesome stuff, cfwprophet and all the PS3 scene that support us, I say also thanks to the people who insult me and said I'm a fake... more you said that and more I don't care and offer good stuff

Somebody said he want to be fame, no at all... I don't really care, my family and my gf give me already that by supporting me, it's enough

Anyway I would like this project to encourage PS3 homebrew developers to help out if they can, and also for the work that cfwprophet, me and others are doing on it will be updated here periodically.

PS: Probably go have more explanation and more stuff about it in the next week. Oh yes about the Debug PKG that is available on PSN Dev (it's not related to the TB Eboot)

You can make a Debug PKG yourself by only extracting the ELF, make a Self without NPDRM, leave him Eboot.self and make a PKG without NPDRM, this represent exactly what is a debug PKG (it's a standard Self inside a PKG without NPDRM)


Project: Cobra and True Blue PS3 Dongles, TB EBOOTs Examined

Follow us on Twitter, Facebook and drop by the PS3 Hacks and PS3 CFW forums for the latest PlayStation 3 scene and PS4 Hacks & JailBreak updates with PlayStation 4 homebrew PS4 Downloads.




#802 - Tidusnake666 - 147w ago
Tidusnake666's Avatar
I do not know, by what miracle guys have run Batman Arkham City on TB CFW, it gave me black screen all the time, and I tried with and without disc, with and without patch, with and without dlc... etc.

1) Then I tried to make a PSN-like package to run it with the TB unplugged (you remember good old times, eh?). After 2.5 hours of converting NPDRM-update-like-pkg signed with debug keys with hard-as-nutshell-to-decrypt eboot, I finally managed to create a pkg. It run, but at the install it hanged.

2) So, I made another (obvious) solution in half an hour - reencrypted eboot, so you can replace it directly over your game dump and play happily on any 3.55 CFW (included TB) without problems (haven't tried dlc's on TB CFW yet). Tested on TB CFW v2 with dongle plugged.

Instructions:

1. Replace ebbot in your game's dump directory with this: http://www.sendspace.com/file/3u2rb5 (THIS IS NOT AN OLD EBOOT, IT'S CONVERTER!)
2. Run the game, allow it to install data, start new game, when you'll regain control of Bruce, while moving the character, you should press PS button and chose "Exit game"
3. Start multiman, copy "PATCH" directory d/l from here: http://www.sendspace.com/file/8yp618 to your hdd0/game/BLUS30538/USRDIR (game install directory)
4. Start the game again, wait till another install finishes, enjoy!

No old semi-working patches were used, it's a real deal, patched to run in a way for TB users, who have troubles launching the usual style.

Come on guys, I sacrificed some precious hours of sleep (it's 4 AM here), I deserve some +reps

#801 - kyubey - 148w ago
kyubey's Avatar
updated version refer to:

-the software
-the hardware (new dongle)

?

#800 - HWARAKADLAH - 148w ago
HWARAKADLAH's Avatar
Here is another update from the TB site:

23 - 7 - 2012

The True Blue team will soon be launching an updated version of our dongle, hence our silence and lack of news/updates. The changes include a new style casing to help differentiate clones from the authentic True Blue dongles. The new version dongle will be compatible with EBOOT patches released to date, whilst existing authentic True Blue dongles in the market will continue to be supported in the same firmware releases.

You can expect a spate of EBOOT releases shortly after the new version dongle is released. We also plan to include a lot of extra features for our loyal True Blue user base in upcoming firmware releases. which will also function seamlessly on existing authentic True Blue dongles.

We would also like to bring to our potential customers and existing users attention that the website: truebluejb2.cc is selling FAKE dongles. We are in no way associated with them nor will we replace or support their fake dongles.

Information received suggests that they have not yet cloned our new style packaging, so large qty's of devices in the market which do NOT come packed in the packaging detailed below (30-5-2012 news) are most likely fake. We will continue to monitor the situation daily.

The upcoming new firmware releases will also block the clones and help users differentiate fakes from authentic dongles.

Upcoming firmware releases will block these fake devices and furthermore EBOOT's will not support the clones. PB2 and JBking clone devices will also be blocked in the future and will not function correctly with our upcoming features!

We thank our customers for their continuing support and hope you will enjoy the coming features and EBOOT patches.........

The clones sold by truebluejb2.cc can be differentiated by checking the PCB inside the casing using the guide below, as previously posted in news.

#799 - fantopoulos - 150w ago
fantopoulos's Avatar
very crazy stuff, i think you will probably need kind of update, or adapter, or something for the true blue to work, the pieces just do not add up to me.

#798 - Erz - 150w ago
Erz's Avatar
Ouch! Please don't make another dongle

If they did make another dongle for high rocket price then, I guess I have to say goodbye to PS3 and welcome 360

#797 - leon315 - 150w ago
leon315's Avatar
man, you don't have to pirate, nor get their dongle...

#796 - elser1 - 150w ago
elser1's Avatar
I'm sure they've made enough ten times over considering its not their games they are allowing us to pirate. what about free verios, or karmas a bit hope you all go to jail tb there to modify it.

#795 - hey69 - 150w ago
hey69's Avatar
If it wasn't 60 bloody EURO maybe , and so would lots of other people i think

#794 - saito1234 - 150w ago
saito1234's Avatar
I'm afraid that if True Blue really releases a new dongle soon, they won't release any more eboot for the dongle, as it already has a lot of clones, and they probably want to sell more from their new dongle...

#793 - Xyth - 152w ago
Xyth's Avatar
TrueBlue (JB2) will stop production and another dongle will be released according to LighTake's site:

True Blue JB2 was stop producing and a newest replace product will be released in July, please pay close attention to TB official site news update in recently days. Any questions just contact sales for help.

A newer replace DRM dongle with build-in ndw function will be released July 20th.

Q: Does the old TB dongle compatible with the new one?
A: Yes! our supplier said the old TB will still get support on updating so that it can play new games as the new dongle. If there is a change, I will advance notice.

Q: What's the name and function of the new dongle?
A: It's still a mystery currently, I will update immediately if I heard something from our supplier.

We have confirmed that the new dongle is still called True Blue (aka JB2 / TB), but it was changed new packaging and add more function in it. What's the new technical support? I am sorry we don't know currently except compatible with the old TB eboots.