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

December 18, 2011 // 12:35 am - Although we agree with homebrew PS3 developers including KaKaRoToKS and CrashSerious on the True Blue dongle, it appears the first PS3 JailBreak 2 (JB2) dongle clone has now surfaced called the JB-King from China.

Based on the pictures below, the JB-King dongle looks similar to the P3Go GT Break Clone PS3 ModChip, but like TB allows playing 3.6x+ PlayStation 3 games on FW 3.55 from normal BD-R discs and from the PS3 HDD.

Download: JB-King PS3 Driver / JB-King PS3 Upgrade Guide / JB-King PS3 Upgrade Tools / JB-King PS3 Upgrade File / Fhash Tool - Verify SHA1 CODE (CRC: 975C731C) / MD5 Verify Tool - Verify MD5 CODE (CRC: E44542D8) / JBK Reset Patch 2.3 Upgrade (CRC: F06B0D4D)

Below are the (roughly translated) JB-King specifications from the clone's official site (linked above) courtesy of SilverTone International Co via

How to upgrade?

1. Press on JBK back Switch and plug in PC, will appear Finding Hardware Device.
2. According to PS3 console model, open "Driver" file to find the compatible driver with your own ps3, and install it, then appear"STM Device in DFU Mode" normally.
3. Open file by step "JBK upgrade TOOLS\Release\Upgrade.ex

Congratulations! Latest high quality PS3 JB-King released! If you want to unlock you own PS3 console and enjoy the latest and most popular PS3 games, you can have one more choice- high quality PS3 JB-King.

PS3 JB-King Dongle

Unlock the true potential of your PS3 with JB-King Dongle- keep your PS3 on a homebrew enabled custom fireware, while at the same time enjoying the latest and most popular PS3 games.

JB-King Features

Attention: All JB-King we sell now,default V2.3 firmware,no need to update TB2 V2.3 firmware.

JB-King later upgrade firmware must be downloaded from JB-King official Web site from now on. If download unofficial upgrade firmware from other website, it will not be received normal after-sale service.

  • Booting of games from v3.6+ (up to v3.73) from special BD-R discs available from official resellers
  • Runs games up to v3.56 from HDD in conjunction with 'backup managers'
  • Does not require the Power/Eject trick
  • Custom v3.55 Dongle firmware behaves like OFW when 'JB-King' is not inserted
  • Manufactured from highest grade components and Actel based
  • Durable and high quality metal case design
  • Tough and durable plastic packaging
  • Further features to be added as they are developed
  • Supports Fat and Slim consoles currently running any firmware up to v3.55
  • And any PS3 which can be downgraded from v3.6+ to v3.55 (NOTE: Requires other tools, 'JB-King' currently can't downgrade a Console)
  • Supports all regions of consoles
  • Supports all regions of ISO's to be released
  • Rock solid crystal oscillator on board for flawless timing
  • The 'JB-King' dongle allows booting of the latest the ISO's (3.6+) from special BD-R discs which can be purchased from all official resellers.
  • The discs can be burned by any BD-R recorder and there are no special requirements on either PC or BD burner types.

Updated JB-King Feature List

1. Booting of games designed for PS3 system software v3.6 and above

2. Runs your existing games and new v3.6+ games from HDD in conjunction with standard backup managers

3. Supports Fat and Slim PS3 consoles currently running any firmware up to v3.55 and any PS3 which can be downgraded successfully from v3.6+ to v3.55 (NOTE: requires other tools, JB-King cannot downgrade a console)

4. Supports all regions of consoles

5. Supports all regions of v3.6+ games

6. Rock solid crystal oscillator on board for flawless timing

7. Durable and high quality plastic case design

8. Tough and durable plastic packaging

9. Further features to be added as they are developed

10. On board 2 MBytes SPI flash

11. Does not require the power/eject trick

12. Custom v3.55 Dongle firmware behaves like OFW when JB-King is not inserted

13. Manufactured from highest grade components and Actel based

PS3 JB-King Installation Guide

Step 1: Make sure your PS3 is in V3.55 system, either OFW (official firmware) or CFW (official firmware). Which means if your PS3 is lower than V3.55, just update it to V3.55! If your PS3 is higher than V3.55, sorry, you can not use this item. please use E3 flasher to downgrade your PS3 to V3.55 first.

Step 2: When your PS3 is in V3.55, you need to install the PS3 JB-King V3.55 CFW. Here is the method on how to install PS3 JB-King V3.55 CFW. The update method is just the same as update the official firmware via USB storage.

  • Download the PS3 JB-King V3.55 CFW
  • Extract the file, you will get "JB king-3.55-CFW" folder, you can see "PS3UPDAT.PUP" iqnside.
  • Prepare a USB storage, create a folder named "PS3"in the root of your USB storage, then create another folder named "UPDATE" in the "PS3" folder, in the end put the "PS3UPDAT.PUP" in the "UPDATE" folder. So it is: USB storage----PS3----UPDATE----PS3UPDAT.PUP
  • Insert your USB storage into your PS3 USB interface and power on your PS3.
  • Move to the system update option and choose update via USB storage.
  • Choose the PS3UPDAT.PUP and start updating, go and drink a beer, wait until it finishes updating. Don't do anything during the update progress.
  • Your PS3 will be in PS3 JB-King V3.55 CFW after the installation.

Step 3: Update your PS3 JB-King to the latest version V2.3.

  • Download the JB-King PS3 Update v2.3
  • Extract the file you will get "JB-King Update-2.3.pkg"
  • Put the "JB-King Update-2.3.pkg" file in your USB storage.
  • Insert the USB storage into your PS3 and then install the pkg file in your PS3.
  • After you finish the installation, you will see the "True blue Update V2.3"
  • Click the "True blue Update V2.3" it will ask you to insert your PS3 JB-King. then insert your PS3 JB-King.
  • Go on the update procress to finish the update.

After this step, you have installed the PS3 JB-King successfully. Let's go and start playing a game. I will take "FEAR 3" as an example.

Notice: You need to replace the PS3 JB-King eboot for the V3.60+ games before you play the games.

It means you need to download the both FEAR 3 game file and also F.E.A.R.3_EBOOT_PATCH_TB_ PS3-PARADOX if you don't do this step, the screen will freeze and change black. ok I have downloaded those files and also have patched it, let's go.

  • Before you power on the PS3, just insert the PS3 JB-King and the your game HDD.
  • Login Multiman and find the FEAR3
  • Press X to login the game
  • It will take you back to XMB
  • Go to "app_home/PS3_GAME/" and click it to play FEAR3
  • Done, congratulations!


Q:Will more new cracked games release later?
A: Our JB-King Team has mastered the core cracking technology, and has the ability to crack games by ourselves. We will regularly renew the cracked games eboot files, please pay your attention to our official website for details. Just rest assured to buy and use our JB-King.

Q: How do I use JB-King to play a purchased PS3 game that requires 3.6+ PS3 firmware?
A: JB-King does not support directly playing original game discs requiring 3.6+ on lower firmware versions. In order to play such recent games on your jailbroken 3.55 CFW PS3 you must first dump your original game disc to HDD using one of the many supported PS3 backup managers such as Multiman.

Once you have dumped the game, you must obtain and install a "JB-King patch" corresponding to said game from the internet. This procedure effectively creates a copy of your game on a HDD, modified to function on your 3.55 CFW PS3 in conjunction with JB-King. For full details, please refer to the JB-King Users Guide on the download page.

Q: Where can I obtain JB-King patch files?
A: Unfortunately we cannot host JB-King patch files on this website, however they are easily obtainable through the search facility provided on the Game Patches page.

Q: What are the requirements for using JB-King?
A: In order to use JB-King, you MUST have a PS3 running firmware v3.55 or lower. If your PS3 is running a firmware version higher than 3.55 then you must first downgrade your PS3 via other means (such as hardware downgrade, please refer elsewhere for further information).

Q: What is the general procedure for getting 3.6+ games running on a 3.55 CFW PS3 with JB-King?
A: The procedure is as follows:

1) Download and install the JB-King 3.55 CFW (custom firmware) on your PS3. The JB-King CFW is required in order to allow the JB-King dongle to function with your PS3
2) Obtain dumps of your 3.6+ PS3 games using PS3 backup managers or other methods
3) Obtain JB-King game patches corresponding to the game dumps you have, and install these patches over the top of your game dumps. The patched game dumps should be stored either on your PS3's internal HDD or an external USB HDD
4) Insert the JB-King dongle into your PS3 and turn on the console. Once the PS3 has finished booting, you may then launch your favourite backup manager (such as Multiman) and from there select your JB-King patched games

Q: There is no JB-King patch available for my favourite game XYZ, can I still play it with JB-King?
A: Unfortunately, you will need to wait until a JB-King patch is available. The JB-King team monitors various web forums, so if there is a title you want to play then make a post on a PS3 related forum requesting the game. We will most likely see your post and do our best to release a patch as soon as possible.

JBK Reset Patch 2.3 Upgrade (CRC: F06B0D4D)

JB-King user, pls don't upgrade with TrueBlue V2.4 firmware, it may cause upgrade error and be unusable.

If upgrade with TB2.4 wrong, don't worry, pls download and run special repair patch "JBK reset patch 2.3_upgrade.dfu" from JB-King official website, it can recovery your JB-King to default settings and work normally. With upgrade in the future, JB-King can be perfectly compatible with the latest TB 2.4 released games. Pls be assured that use of JB-King.


1. Default setting JB-King, can not run special BD-R games, pls proceed with upgrading "upgrade 20111220.dfu", all functions of TB2.3 can be work normally.

2. With strong hardware design, JB-King won't be unusable caused by upgrade TB 2.4 wrong. More important and mysterious function will be released, being expecting!

MD5: 2A9CEA5056A5681F0126EABCA117B47D
SHA1: E426B39291197AB21F671411F63C49A0E987417B

JB-King PS3 JB2 (True Blue) JailBreak 2 Dongle Clone Surfaces

JB-King PS3 JB2 (True Blue) JailBreak 2 Dongle Clone Surfaces

JB-King PS3 JB2 (True Blue) JailBreak 2 Dongle Clone Surfaces

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.

#64 - PS4 News - July 4, 2012 // 6:39 am
PS4 News's Avatar
Below is the JB-King v2.7 PS3 JB2 JailBreak 2 dongle clone update and details, as follows:

Download: JB-King Upgrade Package v2.7

JB-King team released our 2.7 upgrade. This time, we upgrade code inside,make system to be stronger and safer. All 2.7 games can be supported,including the coming games.

We'll going on upgrading and releasing more games for friends that love gaming.

Thanks for all of your supporting and helping. Best Regards.


Order Up
Tiger Woods PGA TOUR 13
Max Payne 3
Dragon's Dogma
SBK Generations
Tom Clancy's Ghost Recon - Future Soldier
Major League Baseball 2K12
Game of Thrones

#63 - PS4 News - April 10, 2012 // 8:58 am
PS4 News's Avatar
Here is another update from JB-King for those following: JB-King release upgrade V2.51 and solve the PS3 HDD format problem.

Download: JB-King Upgrade Package v2.51

Date: 2012-04-10

JB-King team has released "upgrade V2.51" and solve the PS3 HDD format problem!

This upgrade content:

1. Rebuild the Security Architecture, avoid PS3 console HDD harm from Eboots including malicious code.
2. Support and

#62 - TheDevil - April 7, 2012 // 11:52 am
TheDevil's Avatar
News update from JB-King site: Statement for latest TB eboot format HDD problem!

Date: 2012-04-07

1. JB-king Team apologize sincerely to our little part JB-king users, whose HDD was erased by playing games below:

2. Our Team will release new upgrade firmware next week, to solve the Erasing HDD problem when playing new games. Expecting to notice JB-king official website

3. Kindly advise JB-king users delay to play below games before we release new upgrade firmware.

4. In order to avoid similar incident happenning again, JB-King office will better supply JB-King users with game Eboot download space, and welcome to download game Eboots from it.

5. We strongly despise that TB takes the ps3 players as a tool to maintain his windfall profits. We never be afraid of competition, as which is for better servicing our customers but not hurt whose benefits.

Eboots list not support now:

  • 機動戦士ガンダムUC
  • Silent Hill Downpour
  • Snipers - Invisible, Silent, Deadly
  • Tales of Graces f
  • Top Gun: Hard Lock

#61 - PS4 News - April 5, 2012 // 6:35 am
PS4 News's Avatar
News update from JB-King site for those interested:

Date: 2012-04-06

1. JB-King would not be blocked unless TB's going to block TB regular users' upgrading.

2. JB-King users do not have to worry about the coming TB upgrade, we will crack it soon and make JB-King compatible with upgrade package, even the new TB CFW. As we have successfully made it compatible with V2.3, V2.4 and V2.5, it is inevitably we're in the condition to make a further cracking of new ungrading package.

3. We strongly condemn TB's behavior of spiteful competition, who threatens to turn the comsumers' console to brick so as to acheive its goal of monopolizing ps3 break market. Certainly which would greatly impair comsumers' benefits. However, similar behavior would never be from us as we always insist on the tenet of "customer first'.

4. As JB-King dongle comes from JB-King team's self-designed hardware program, there is no doubt that we can regenerate under any condition.

5. If TB sets up malicious code to JB-King, TB users can not be excluded. As TB can not completely distinguish the differences between TB and JB-King, that's also the reason for why they could not block JB-King in V2.4 upgrade package.

From zadow28: Been testing my new tracker on the upgrade.exe from jbking and got some visual results with big difference in security.. you can see the results here.

first download:

small guide to open the visual files.

then download the visual files:

just open the files with the guide. i would recommend upgrade jbking. blue spot is start, and you scroll in with mouse. this is from start, too when i load the different images.

its show the way with fake loops, as they are in the software (encryption) the path.. it speaks for themselves.


#60 - PS4 News - March 16, 2012 // 5:42 am
PS4 News's Avatar
Below is a video from their page of the JB-King v2.5 PS3 JB2 (True Blue) JailBreak 2 dongle clone with the details below, as follows:

1. After upgrade 2.5, JB-King could support all functions of TB2.5

2. JB-King has its true ability to break any updated content and plugging of TB2.X in the future.

3. JB-King can break any disc games of TB, allow players to clone disc on their own (We may release all of them when update next time).

4. JB-King has ability to release game eboot, which has been modified and only support JB-King. Most important is that we will not use special disc.

5. JB-King price will be easier approach soon

Updated method Please follow the procedure, or it will be difficult for you to play games smoothly.)

1. Press on JB-King upgrade switch and plug in main USB interface. Open “Upgrade.exe” and upgrade “updrade2.5.dfu". Then pull out JB-King and close “Upgrade.exe”

2. Do not press on JB-King power switch. Plug it into PC. After about 5-8 seconds, pull out JB-King.

3. Press on JB-King upgrade switch power again, and plug it into USB interface. Open “Upgrade.exe” and upgrade “S_2.5.dfu”. The process will last for a longer time, please be patient!

3. If you get tips as follows, congratulation! You upgrade successfully.

2012.03.16 Update 2.5

(upgrade console system: TrueBlue-3.55-v2-cfw)

Download: / TrueBlue-3.55-v2-cfw.rar

1: upgrade2.5.dfu MD5: 9c3e1e50f6c7116a1ebb94577495a353
2: S_2.5.dfu MD5: 8b62de1d035cb9807ac6745920b78f19

Download: / 2012.03.16 JBKing 2.5

JB-King Upgrade Package V2012.03.16


Update content: 2012-3-16: Support all V2.5 games


1/ PC Driver
2/ JBK Upgrade Tools
3/ How to upgrade Version 2011.12.21
4/ JBK reset patch 2.3_upgrade
5/ reset patch guide V2.3
6/ upgrade V2.40
7/ upgrade V2.41
8/ upgrade V2.42
9/ upgrade V2.5

From zadow28: mmhhh the dfu files from JB can be extracted as three types. Bin/hex and s19.. the s.19 files loads as memory in ida pro. the dongle protection is old from 2009.

Here is an link for extracting the dfu files:

So here some info:

[Register or Login to view code]

This is from upgrade2.5.hex update:

[Register or Login to view code]

This is from the jb 2.5 upgrade (2.5.s19):

[Register or Login to view code]

Ok was looking in to the update.exe and what happens when you load the dfu file.

Seems we are in the right track, since the upgrade uses the same software for extracting the dfu files.

[Register or Login to view code]

Found this code hidden in sub 404490:

[Register or Login to view code]

Here is some more:
int __thiscall sub_403760(void *this, int a2)
void *v2; // edi@1
int v3; // eax@1
int v4; // eax@3
int v5; // eax@5
int v6; // eax@7
int v7; // eax@9
int v8; // eax@11
int v9; // eax@13
int v10; // eax@15
int v11; // eax@17
int v12; // eax@19
int v13; // eax@21
int v14; // eax@23
int v15; // eax@25
int v16; // eax@27
int v17; // ST44_4@29
int v18; // esi@29
int v19; // eax@29
signed int v20; // eax@61
unsigned int v21; // esi

int v22; // eax@126
int v23; // edi@126
int v24; // eax@128
int v25; // eax@128
int v26; // eax@128
int v27; // eax@128
int v28; // eax@128
int v29; // eax@128
int v30; // eax@128
int v31; // eax@128
int v32; // eax@128
int v33; // eax@128
int v34; // eax@128
int v35; // ST3C_4@128
int v36; // eax@128
int v37; // eax@130
int v38; // eax@132
int v39; // eax@134
int v40; // eax@136
int v41; // eax@138
int v42; // eax@140
int v43; // eax@142
int v44; // eax@144
int v45; // eax@146
int v46; // eax@148
int v47; // eax@150
LPCSTR v48; // eax@152
int v49; // eax@154
int v50; // eax@156
int v51; // eax@160
int v52; // eax@162
int v53; // eax@164
int v54; // eax@166
int v55; // eax@168
int v56; // eax@170
int v57; // eax@172
int v58; // eax@174
int v59; // eax@176
int result; // eax@178
void *v61; // [sp-8h] [bp-84h]@31
rsize_t v62; // [sp-4h] [bp-80h]@31
char *v63; // [sp-4h] [bp-80h]@69
const CHAR *v64; // [sp-4h] [bp-80h]@126
int v65; // [sp+Ch] [bp-70h]@128
int v66; // [sp+10h] [bp-6Ch]@128
int v67; // [sp+14h] [bp-68h]@128
int v68; // [sp+18h] [bp-64h]@128
int v69; // [sp+1Ch] [bp-60h]@128
int v70; // [sp+20h] [bp-5Ch]@128
int v71; // [sp+24h] [bp-58h]@128
int v72; // [sp+28h] [bp-54h]@128
int v73; // [sp+2Ch] [bp-50h]@128
int v74; // [sp+30h] [bp-4Ch]@128
int v75; // [sp+34h] [bp-48h]@128
int v76; // [sp+38h] [bp-44h]@3
int v77; // [sp+3Ch] [bp-40h]@11
int v78; // [sp+40h] [bp-3Ch]@15
int v79; // [sp+44h] [bp-38h]@17
int v80; // [sp+48h] [bp-34h]@7
int v81; // [sp+4Ch] [bp-30h]@19
int v82; // [sp+50h] [bp-2Ch]@21
int v83; // [sp+54h] [bp-28h]@25
int v84; // [sp+58h] [bp-24h]@27
int v85; // [sp+5Ch] [bp-20h]@5
LPCSTR Str; // [sp+60h] [bp-1Ch]@29
int v87; // [sp+64h] [bp-18h]@23
int v88; // [sp+68h] [bp-14h]@13
int v89; // [sp+6Ch] [bp-10h]@9
int v90; // [sp+78h] [bp-4h]@3

v2 = this;
v3 = _LN13_16();
if ( !v3 )
v76 = (*(int (__thiscall **)(int))(*(_DWORD *)v3 + 12))(v3) + 16;
v90 = 0;
v4 = _LN13_16();
if ( !v4 )
v85 = (*(int (__thiscall **)(int))(*(_DWORD *)v4 + 12))(v4) + 16;
LOBYTE(v90) = 1;
v5 = _LN13_16();
if ( !v5 )
v80 = (*(int (__thiscall **)(int))(*(_DWORD *)v5 + 12))(v5) + 16;
LOBYTE(v90) = 2;
v6 = _LN13_16();
if ( !v6 )
v89 = (*(int (__thiscall **)(int))(*(_DWORD *)v6 + 12))(v6) + 16;
LOBYTE(v90) = 3;
v7 = _LN13_16();
if ( !v7 )
v77 = (*(int (__thiscall **)(int))(*(_DWORD *)v7 + 12))(v7) + 16;
LOBYTE(v90) = 4;
v8 = _LN13_16();
if ( !v8 )
v88 = (*(int (__thiscall **)(int))(*(_DWORD *)v8 + 12))(v8) + 16;
LOBYTE(v90) = 5;
v9 = _LN13_16();
if ( !v9 )
v78 = (*(int (__thiscall **)(int))(*(_DWORD *)v9 + 12))(v9) + 16;
LOBYTE(v90) = 6;
v10 = _LN13_16();
if ( !v10 )
v79 = (*(int (__thiscall **)(int))(*(_DWORD *)v10 + 12))(v10) + 16;
LOBYTE(v90) = 7;
v11 = _LN13_16();
if ( !v11 )
v81 = (*(int (__thiscall **)(int))(*(_DWORD *)v11 + 12))(v11) + 16;
LOBYTE(v90) = 8;
v12 = _LN13_16();
if ( !v12 )
v82 = (*(int (__thiscall **)(int))(*(_DWORD *)v12 + 12))(v12) + 16;
LOBYTE(v90) = 9;
v13 = _LN13_16();
if ( !v13 )
v87 = (*(int (__thiscall **)(int))(*(_DWORD *)v13 + 12))(v13) + 16;
LOBYTE(v90) = 10;
v14 = _LN13_16();
if ( !v14 )
v83 = (*(int (__thiscall **)(int))(*(_DWORD *)v14 + 12))(v14) + 16;
LOBYTE(v90) = 11;
v15 = _LN13_16();
if ( !v15 )
v84 = (*(int (__thiscall **)(int))(*(_DWORD *)v15 + 12))(v15) + 16;
LOBYTE(v90) = 12;
v16 = _LN13_16();
if ( !v16 )
Str = (LPCSTR)((*(int (__thiscall **)(int))(*(_DWORD *)v16 + 12))(v16) + 16);
v17 = *((_DWORD *)v2 + 282);
LOBYTE(v90) = 13;
sub_4022D0((int)&v84, "Target: %02i\n", v17);
v18 = a2;
v19 = *(_DWORD *)(a2 + 32);
if ( v19 )
if ( v19 != 4 )
goto LABEL_34;
v62 = 19;
v61 = "Operation: UPGRADE\n";
v62 = 18;
v61 = "Operation: DETACH\n";
sub_401E70(v61, v62);
sub_4022D0((int)&v80, "TransferSize: %i\n", *(_WORD *)(v18 + 309));
switch ( *(_BYTE *)(v18 + 315) )
case 0:
sub_403520("DFU State: STATE_IDLE\n");
case 1:
sub_403520("DFU State: STATE_DETACH\n");
case 2:
sub_403520("DFU State: STATE_DFU_IDLE\n");
case 3:
sub_403520("DFU State: STATE_DFU_DOWNLOAD_SYNC\n");
case 4:
sub_403520("DFU State: STATE_DFU_DOWNLOAD_BUSY\n");
case 5:
sub_403520("DFU State: STATE_DFU_DOWNLOAD_IDLE\n");
case 0xA:
sub_403520("DFU State: STATE_DFU_ERROR\n");
sub_4022D0((int)&Str, "DFU State: (Unknown 0x%02X)\n", *(_BYTE *)(v18 + 315));
sub_4020F0((char *)Str, *((_DWORD *)Str - 3));
switch ( *(_BYTE *)(v18 + 311) )
case 0:
sub_403520("DFU Status: STATUS_OK\n");
case 1:
sub_403520("DFU Status: STATUS_errTARGET\n");
case 2:
sub_403520("DFU Status: STATUS_errFILE\n");
case 3:
sub_403520("DFU Status: STATUS_errWRITE\n");
case 4:
sub_403520("DFU Status: STATUS_errERASE\n");
case 5:
sub_403520("DFU Status: STATUS_errCHECK_ERASE\n");
case 6:
sub_403520("DFU Status: STATUS_errPROG\n");
case 7:
sub_403520("DFU Status: STATUS_errVERIFY\n");
case 8:
sub_403520("DFU Status: STATUS_errADDRESS\n");
case 9:
sub_403520("DFU Status: STATUS_errNOTDONE\n");
case 0xA:
sub_403520("DFU Status: STATUS_errFIRMWARE\n");
case 0xB:
sub_403520("DFU Status: STATUS_errVENDOR\n");
case 0xC:
sub_403520("DFU Status: STATUS_errUSBR\n");
case 0xD:
sub_403520("DFU Status: STATUS_errPOR\n");
case 0xE:
sub_403520("DFU Status: STATUS_errUNKNOWN\n");
case 0xF:
sub_403520("DFU Status: STATUS_errSTALLEDPKT\n");
sub_4022D0((int)&Str, "DFU Status: (Unknown 0x%02X)\n", *(_BYTE *)(v18 + 311));
sub_4020F0((char *)Str, *((_DWORD *)Str - 3));
v20 = *(_DWORD *)(v18 + 317);
if ( v20 > 201326592 )
if ( v20 > 301989888 )
if ( v20 > 352321536 )
if ( v20 == 369098752 )
v63 = "Request: Identifying device after reenumeration. \n";
goto LABEL_111;
if ( v20 == 352321536 )
v63 = "Request: Awaiting PLUG EVENT. \n";
goto LABEL_111;
if ( v20 == 318767104 )
v63 = "Request: Selecting target. \n";
goto LABEL_111;
if ( v20 == 335544320 )
v63 = "Request: Awaiting UNPLUG EVENT. \n";
goto LABEL_111;
if ( v20 == 301989888 )
sub_4020F0("Request: Abort Request. \n", 0x19u);
goto LABEL_112;
if ( v20 > 251658240 )
if ( v20 == 268435456 )
v63 = "Request: Clear Status Request. \n";
goto LABEL_111;
if ( v20 == 285212672 )
v63 = "Request: Get State Request. \n";
goto LABEL_111;
if ( v20 == 251658240 )
v63 = "Request: Get Status Request. \n";
goto LABEL_111;
if ( v20 == 218103808 )
v63 = "Request: Download Request. \n";
goto LABEL_111;
if ( v20 == 234881024 )
v63 = "Request: Upload Request. \n";
goto LABEL_111;
goto LABEL_109;
if ( v20 == 201326592 )
sub_4020F0("Request: Detach Request. \n", 0x1Au);
goto LABEL_112;
if ( v20 > 117440512 )
if ( v20 > 167772160 )
if ( v20 == 184549376 )
v63 = "Request: Closing device. \n";
goto LABEL_111;
if ( v20 == 167772160 )
v63 = "Request: Opening device. \n";
goto LABEL_111;
if ( v20 == 134217728 )
v63 = "Request: Getting amount of alternates. \n";
goto LABEL_111;
if ( v20 == 150994944 )
v63 = "Request: Getting interface Descriptor. \n";
goto LABEL_111;
goto LABEL_109;
if ( v20 == 117440512 )
v63 = "Request: Getting amount of interfaces. \n";
goto LABEL_111;
if ( v20 > 67108864 )
if ( v20 == 83886080 )
v63 = "Request: Getting amount of configurations. \n";
goto LABEL_111;
if ( v20 == 100663296 )
v63 = "Request: Getting Configuration Descriptor. \n";
goto LABEL_111;
goto LABEL_109;
if ( v20 == 67108864 )
v63 = "Request: Getting String Descriptor. \n";
goto LABEL_111;
if ( v20 == 33554432 )
v63 = "Request: Getting Device Descriptor. \n";
goto LABEL_111;
if ( v20 != 50331648 )
sub_4022D0((int)&Str, "Request: (unknown 0x%08X). \n", *(_DWORD *)(v18 + 317));
sub_4020F0((char *)Str, *((_DWORD *)Str - 3));
goto LABEL_112;
v63 = "Request: Getting DFU Descriptor. \n";
sub_4022D0((int)&v81, "CurrentNBlock: 0x%04X\n", *(_DWORD *)(v18 + 321));
sub_4022D0((int)&v82, "CurrentLength: 0x%04X\n", *(_DWORD *)(v18 + 325));
sub_4022D0((int)&v83, "Percent: %i%%\n", *(_BYTE *)(v18 + 308));
v21 = *(_DWORD *)(v18 + 337);
if ( v21 > 0x12345007 )
switch ( v21 )
case 0x12345008u:
sub_402970("Error Code: Bad parameter\n");
case 0x12345009u:
sub_402970("Error Code: Bad state machine in firmware\n");
case 0x1234500Au:
sub_402970("Error Code: Unexpected error\n");
case 0x1234500Bu:
sub_402970("Error Code: DFU error\n");
case 0x1234500Cu:
sub_402970("Error Code: Retry error\n");
goto LABEL_125;
switch ( v21 )
case 0x12345007u:
sub_401E70("Error Code: DFU already running\n", 0x20u);
case 0x12340000u:
sub_401E70("Error Code: no error (!)\n", 0x19u);
case 0x12345001u:
sub_402970("Error Code: Unable to launch operation (Thread problem)\n");
sub_4022D0((int)&Str, "Error Code: Unknown error 0x%08X. \n", v21);
v22 = *((_DWORD *)v2 + 282);
v23 = v87;
v64 = (const CHAR *)v87;
if ( v22 >= 0 )
sub_4022D0((int)&Str, "Target %02i: %s", v22);
v64 = Str;
v24 = sub_4024C0(&v65, &v84, &v87);
LOBYTE(v90) = 14;
v25 = sub_4024C0(&v66, v24, &v76);
LOBYTE(v90) = 15;
v26 = sub_4024C0(&v67, v25, &v85);
LOBYTE(v90) = 16;
v27 = sub_4024C0(&v68, v26, &v80);
LOBYTE(v90) = 17;
v28 = sub_4024C0(&v69, v27, &v89);
LOBYTE(v90) = 18;
v29 = sub_4024C0(&v70, v28, &v77);
LOBYTE(v90) = 19;
v30 = sub_4024C0(&v71, v29, &v88);
LOBYTE(v90) = 20;
v31 = sub_4024C0(&v72, v30, &v78);
LOBYTE(v90) = 21;
v32 = sub_4024C0(&v73, v31, &v79);
LOBYTE(v90) = 22;
v33 = sub_4024C0(&v74, v32, &v81);
LOBYTE(v90) = 23;
v34 = sub_4024C0(&v75, v33, &v82);
LOBYTE(v90) = 24;
v35 = *(_DWORD *)sub_4024C0(&a2, v34, &v83);
LOBYTE(v90) = 25;
AfxMessageBox(v35, 0, 0);
v36 = a2 - 16;
LOBYTE(v90) = 24;
if ( _InterlockedDecrement((signed __int32 *)(a2 - 16 + 12))

#59 - Bartholomy - January 10, 2012 // 1:17 am
Bartholomy's Avatar
Uhm, looking their last announce, seems a JBking BDR will be released, more than an HDD eboot.

#58 - landon - December 31, 2011 // 4:48 pm
landon's Avatar
Hope they could make 3.55 eboot for HDD version of PES 12/FIFA 12

#57 - PS4 News - December 30, 2011 // 4:53 pm
PS4 News's Avatar
Today the JB-King PS3 JB2 (True Blue) JailBreak 2 dongle software has been updated to version 2.4 following their JBK Reset Patch 2.3 Upgrade release alongside a video of it in action below.

Download: JB-King Upgrade Package V2011.12.30 / JB-King PS3 3.55 CFW

To quote from their page:

JB-King can support latest upgrade 2.4 games!!!

1. After upgrade 2.4, JB-King could support all functions of TB2.4
2. JB-King has its true ability to break any updated content and plugging of TB2.X in the future.
3. JB-King can break any disc games of TB, allow players to clone disc on their own. (We may release all of them when update next time)
4. JB-King has ability to release game eboot, which has been modified and only support JB-King. Most important is that we will not use special disc.
5. JB-King price will be easilier approach soon

Latest game EBOOTs:

  • Dead.Rising.2
  • NHL_12_EUR NHL
  • The.Adventures.of.Tintin
  • Ni_no_Kuni_Shiroki_Seihai_no_Jouou_JPN
  • Nurarihyon_no_Mago_Hyakki_Ryouran_Taisen_MERRY_XMAS
  • Start The Party Save the World
  • Sengoku_Basara_3_Utage_JPN

Updated List:

  • Dead.Rising.2
  • NHL_12_EUR NHL
  • The.Adventures.of.Tintin
  • Ni_no_Kuni_Shiroki_Seihai_no_Jouou_JPN
  • Nurarihyon_no_Mago_Hyakki_Ryouran_Taisen_MERRY_XMA S
  • Start The Party Save the World
  • Sengoku_Basara_3_Utage_JPN
  • PES2012 (V2)

From IRC:

2011.12.28 update 2.4

1: updrade2.4.dfu MD5: 41c4c101adedffb29dd3bc5f99eca1b0
2: spi 2.4_upgrade.dfu MD5: 8b27f8873cd2304dbebb5e1218a6b35e

How to upgrade?

1. Upgrade updrade2.4.dfu, and then pull out JB-King.
2. About 8 seconds later, pull in JB-king again, upgrade "spi 2.4_upgrade.dfu" The process will last for some time. Please wait.
3. after the two steps, congratulation! You upgrade successfully.

Attention: If JB-King could not work normally after upgrade, please try the above steps again, and change an USB interface, better for the one close to your PC motherboard. Please do not use USB extension line.

Upgraded content:

Support the following HDD games:

  • Dead.Rising.2
  • NHL_12_EUR NHL
  • The. Adventures.of.Tintin
  • Ni_no_Kuni_Shiroki_Seihai_no_Jouou_JPN
  • Nurarihyon_no_Mago_Hyakki_Ryouran_Taisen_MERRY_XMAS
  • Start The Party Save the World
  • Sengoku_Basara_3_Utage_JPN

After New Year’s Day, JB-King will support some disc Games as follows:

5: PES2012 (V2)

#56 - NTA - December 21, 2011 // 3:59 pm
NTA's Avatar
Didn't someone get sued for the old jailbreak dongles and the clones a while back? I can't think of the name

#55 - Erz - December 21, 2011 // 10:24 am
Erz's Avatar
Here is the link

Hope this help (^_^)