To quote from a (now removed) Tweet of Squarepusher2: "BTW Mathieulh I know you gave durandal that CEX-DEX ZIP, that it wasn't you that bundled that up, and you were not supposed to do so either"

**WARNING** IF THIS TUTOTIAL ISN'T FOLLOWED TO THE LETTER YOU MAY BRICK, THE AUTHOR (THAT WOULD BE ME) DENIES ALL KINDS OF RESPONSABILITY SHOULD YOUR PS3 GET DAMAGED IN ANY WAYS. YOU KNOW THE RISKS **WARNING**

Requirements:

1. A playstation 3 on firmware 3.55 or below
2. A dongle to go to Service mode
3. A usb pendrive
4. A brain
5. The author of this little trick.
6. Have your pc connected directly to the ps3 on ethernet with the ip set to 192.168.0.100 and the hostmask to 255.255.255.0 (make sure no firewall is running, not even windows one, this may prevent your console from connecting to the pc)

Procedure:

** PART 1 **

1. Set your console into service mode with any compatible dongle.

2. Put the content of the converter-console folder at the root of your usb pendrive.

3. Extract ObjectiveSuites-GetData on your PC.

4. Put the usb pendrive on the last usb port on the right of your console.

5. Run ObjectiveSuites.exe from ObjectiveSuites-GetData

6. You now have a few seconds to start your console, start it.

7. Objective Suite should display "PASS" and txt files will be created in the Temp dir. Once done, power off your console.

8. Get ALL these txt files from your temp directory and send them to the author (me) with informations about your playstation 3 model (FAT/SLIM, CECH* model)

** PART 2 **

9. You should recieve from the author (Yeah me again) a file called request_idps.txt

10. Extract ObjectiveSuites-SetIdps on your pc.

11. Put the request_idps.txt in your temp folder (MAKE EXTRA SURE IT'S THERE OR YOU WILL BRICK)

12. Run ObjectiveSuites.exe from the ObjectiveSuites-SetIdps directory.

13. Start the SAME CONSOLE YOU GOT THE TXT FILES FROM (If it's another console you WILL BRICK IT).

14. Wait until Objective suite displays "PASS" Then power off your console, at this point your console should be a Debug one.

** PART 3 **

15. You will now need to do a drive initialisation in order to use the bluray drive on your console. Put your usb pendrive on your pc, delete all the files you previously put in there, Put "Lv2Diag.self" from the "set up" directory at the root of your pendrive along with PS3UPDAT.PUP (that's 3.30 debug firmware)

16. Put the pendrive on the usb port on the most right of your console.

17. Power on the console, The screen will be black and the green led will stay lit, wait until it blinks and the console powers off, once it does the firmware will be installed.

18. Put the pendrive back on pc, delete the files you put in there previously, and copy the content of the "drivefix" folder to the root of the pendrive.

19. Put the pendrive at the usb port most on the right of your console and power it on.

20. The drive initialisation will then occur, wait a couple of seconds, then power off the console (you may have to unplug it from the AC)

21. Put the pendrive back onto the pc, delete the files you previously put in there, then copy the Lv2diag.self from the "finalize" folder.

22. Put the pendrive on the usb port on the most right of your console. Power it on. Your console will power on for a few seconds then power off.

CONGRATULATIONS YOU HAVE NOW COMPLETED ALL THE STEPS AND YOUR CONSOLE IS A FULLY FUNCTIONAL DEBUG BOX. YOU NOW JUST NEED TO POWER IT ON AND COMPLETE THE USUAL FIRST TIME SETUP PROCEDURE.

I'm surprised that no one has figured this one out yet, seeing as Mathieulh gave a big hint...three weeks ago, and I saw it today....

Note, this should not be attempted unless you know what you are doing, as it could lead to bricking.

Here's how you do it.

1. Get otheros++ running on 3.41 or 3.55, I used 3.41 but 3.55 might work...

2. boot linux, and dump your nor flash, with

    dd if=/dev/ps3nflasha of=nor.bin

3. ensure that /dev/ps3dmproxy exits, if not look here...You must login or register to view this content.

4. download and compile ps3dm-utils..

5. dump your ipds, with

    ./ps3dm_aim /dev/ps3dmproxy get_dev_id

6. now open your nor dump with a hex editor searching for your ipds, you should find it twice, replace the 6th byte with 82 on both of them

7.

    dd if=modifiednor.bin of=/dev/ps3nflasha

This takes a while..

8. Prepare a flash drive for service mode, with the 3.41 debug firmware **do not flash a higher firmware ** as well as a lv2diag.self

9. Finally, flash that as if you were downgrading, and you are now on a full debug firmware...



If you have problems refer to You must login or register to view this content.

This is the first thing TUHTA and me did...but isn't working. The cex-dex Toolkit make something more than just changing target ID. Accordin to the .SIG.XML( the first posted) you can create your own request_idps using the files you get with the tool, BUT only a small part you need "get" or "check" something while connected on sony's server. The latest .SIG.XML posted(the one in the cex-dex tool GetData dir) seems that don't have requestidps part(that is in the XML in the SetIdps dir). Anyway "flashing" with Linux maybe could make some mistakes that's why i'm waiting progskeet.

Noone have an example of request_idps.txt... Anyway in a chatlog someone says that he had one... The problem is if this person could share with us so we can study it.

Noone have an example of request_idps.txt... Anyway in a chatlog someone says that he had one... The problem is if this person could share with us so we can study it.

Do a dump of eid compare with debug change and rename .txt and your good.

./ps3dm_iim /dev/ps3dmproxy get_data 0x0>dump

What we need for dump eid?
Edit: I found this:

Right?