Post: How to Boot Debug on a Retail PS3 Unit
09-08-2011, 04:08 AM #1
Stack0verfl0w
Computer engineer
(adsbygoogle = window.adsbygoogle || []).push({}); PS3 CEX to DEX Kit (Retail to Debug) Surfaces, Requires IDPS
few weeks back we saw a video on You must login or register to view this content.

DEX to CEX Converter By "You know who"


Originally posted by another user
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"



Originally posted by another user

**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.

[/IMG]
I ASKED MATH FOR THE .TXT HIS WORDS
You must login or register to view this content.
Download:You must login or register to view this content. PASSWORD pass: ps3scene
mirror: You must login or register to view this content.
You must login or register to view this content.
You must login or register to view this content.

DOWNLOAD 3.70 DEBUG HERE You must login or register to view this content.
source: ps3 news
(adsbygoogle = window.adsbygoogle || []).push({});

The following 7 users say thank you to Stack0verfl0w for this useful post:

AMNE, Chaizm, forcer911, FrOzTi, jannu22, PS3 Prodigy, ZombieGoBoom1

The following user groaned Stack0verfl0w for this awful post:

STyLe_JapaN
09-19-2011, 10:01 PM #119
Stack0verfl0w
Computer engineer
Originally posted by dakilla010 View Post
look this isnt a 3.70 frimware might say it but not the real 3.70 so its spoofed so theses no debug or rebug on 3.70 yet or didnt even get leak so

:lol: actually it is and is not a spoof it was leaked so........
09-19-2011, 11:27 PM #120
lol everyone keeps fighting
09-19-2011, 11:59 PM #121
Pauliinho14
Error… Cat invasion!
and after this big discussion have anyone done this by this tutorial?
09-21-2011, 12:18 AM #122
Originally posted by calimba View Post
CONSOLE_SETUP_CEX.SIG decrypted

You must login or register to view this content.


Ohh thanks who the one posted it... This is the one from getData no mention to request_idps.txt like the one i found. This one we get in the cex-dex is already modified. No fuctions requestidps/idpsconfig. Someone will post even the one ins SetIpds directory so we can compare.
09-21-2011, 01:19 AM #123
Originally posted by Coding View Post
:lol: actually it is and is not a spoof it was leaked so........


i did mean it like that lol... what i was trying to say is it spoofed and you said no ok i got that ... can it be done on rebug that i wanna know if so nice.....
09-26-2011, 08:03 AM #124
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.

The following 2 users say thank you to acdcz20 for this useful post:

jannu22, kuruptaz
09-26-2011, 09:08 AM #125
RikuKH3
Save Point
acdcz20, are you tried it yourself? Can you confirm its working?
09-26-2011, 02:37 PM #126
Yes I can confirm that my way works, so long as you know what you are doing
09-26-2011, 03:40 PM #127
RikuKH3
Save Point
So I pressume retail firmware doesn't check Target ID byte in IDPS and loads just fine after rewriting it to '0x82'? Because we still need to run it in service mode in order to downgrade to debug fw.

And debug fw checks just this single byte in idps? It looks a little fishy to me...

Copyright © 2026, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo