Sponsored Links

PS4 News on Facebook! PS4 News on Twitter! PS4 News on YouTube! PS4 News RSS Feed!
Sponsored Links
Sponsored Links
Home PS4 News - Latest PlayStation 4 and PS3 News

PS3 3.60+ Games Booting on 3.55 / 3.41 CFW Without Dongle WIP


Sponsored Links
165w ago - Below is a work-in-progress (WIP) of PS3 3.60+ games booting on PlayStation 3 Custom Firmware (CFW) 3.55 and 3.41 without a dongle for those interested in experimenting further with it.

What you need ?

1- PS3 3.55 CFW Rebug or 3.55/3.41 with Debug
2- Debug Dev_Flash (Also allow to have the debug options on retail)
3- Backup of your own CFW DEV_Flash (make a dev_flash path on your USB Device)
4- A File Manager
5- EBOOT.BIN of your games (also from Paradox)

What you need to know

Rebug normal in Debug mode 2

  • You need to put your PS3 in boot mode -> debugger mode (and not system software mode)
  • We're gonna use the debugger mode to debug the self execution we don't need to have NPDRM, anyway the debugger don't know how to Debug the Self NPDRM
  • Release mode -> Development mode
  • All the content type configuration -> Development mode

Dongle uses modified sprx/modules/lib related to the Debug files to be loaded when you boot the PS3 on CFW.

Almost all the EBOOT Paradox don't have NPDRM -> it's a simple self (fake sign header) renamed to EBOOT.BIN (like i was explaining many times) -> call function to the debugger -> sprx/modules loader.

Let's do a small test to be sure that you understand.. take whatever EBOOT Paradox, open with editeur hexa, check the first header ->

[Register or Login to view code]

You can see that is a standard Self without NPDRM only have a fake sign header.

Rename this file EBOOT.SELF than .bin transfer your self on your usb stick/storage, launch a file manager, add the self to the path of your game and execute your self after that, self will load on the path APP_HOME of your XMB.

If you launch that with the debugger mode, it execute without problem and the debugger don't need to have NPDRM (anyway the debugger don't know how to read Self NPDRM)

Why we need debug_devflash

We need that to replace some specific temporary file to allow to boot on debugger mode and reload the XMB, also the backup of your dev_flash CFW it's here to put back your files (that allow to reboot without crash).

I don't put all now put this is one of the step and WIP of game 3.60+ boot on 3.55/3.41. Remember that the dongle use also standard Self to be load on a debugger mode.


PS3 3.60+ Games Booting on 3.55 / 3.41 CFW Without Dongle WIP

Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter, Facebook and drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene and PlayStation 4 scene updates and fresh homebrew PS3 Downloads. Enjoy!

Comments 255

• Please Register at PS4News.com or Login to make comments on Site News articles.
 
#175 - DeViL303 - 167w ago
DeViL303's Avatar
Yes that might work, could be what cfwprophet is hinting at! I know all retail files are used up until now, but its nice to have a fresh dump of 4.00 debug files to work with too isnt it!

BTW: He means index.dat which is an encrypted version of version.txt with some other info. possibly need to swap version.txt too.

I havnt been trying any of this. too busy!

300th Post! wahoo! heres the 4.00 Debug Dump. have fun and be careful! http://www.woofiles.com/dl-279107-FBoR3WlY-Debug4.00PUPextractedDeViL303.rar

BTW: Can people Please stop using progskeet etc to dump new firmwares dev_flash, do it the easy way!

Anyone on here thats got a nice upload speed feel like uploading that to multiupload or similar so the links stay alive for a while feel free! Ive only got a 50kbs upload speed

#174 - elser1 - 167w ago
elser1's Avatar
i'll do anything to help also.i have a retail 3.41 slim if needed to test anything.

#173 - spunkybunny - 167w ago
spunkybunny's Avatar
Quote Originally Posted by cfwprophet View Post
Anyway, according to the scene version.dat is tied to vsh.self cause vsh.self has the system software version hardcoded in it and there for you need to patch vsh.self if you want to spoof the fw version. This would also mean you can not use a vsh.self of a higher fw on a lower one right ? cause the versions are tied to each other, right ?

Then why not copy both files? version.dat and vsh.self? If they are linked together then copy them both from 4.00 to CFW and they will still be together so they should work right?

#172 - cfwprophet - 167w ago
cfwprophet's Avatar
Forgot to mentoin that we have used RETAIL files of 4.0 and also used a RETAIL 3.41 base fw.

#171 - racer0018 - 167w ago
racer0018's Avatar
Sounds good and will help in anyway that you need. Thanks for all the hard work.

#170 - lionsfan420 - 167w ago
lionsfan420's Avatar
Big thanx to cfwprophet, and DeVil303 for the advice, and files we are about to receive. again Thanx

#169 - DeViL303 - 167w ago
DeViL303's Avatar
Cool, thanks for the info ! I'm uploading a dump of debug 4.00 PUP, all update packages, dev_flash etc, might be of help to someone who hasn't got their system set up to unpack it themselves.

#168 - cfwprophet - 167w ago
cfwprophet's Avatar
Ahaaa NOW peoples start to understand eh ? Stop bashing and start to use your brain ! That is what we want to do

But anyway we TeaM AC1D will show maybe some more if peoples stop yada, yada, and focusing on things others before have sayed and if the use to start there brain for some own investigations.

Anyway, according to the scene version.dat is tied to vsh.self cause vsh.self has the system software version hardcoded in it and there for you need to patch vsh.self if you want to spoof the fw version. This would also mean you can not use a vsh.self of a higher fw on a lower one right ? cause the versions are tied to each other, right ?

Well we have successfully booted 4.0 vsh.self and there correspondet sprx's (also from 4.0) on FW 3.41

Also still the signed HB like MM and so on still work without troubles. We tried on a FAT and on SLIM. Weird a slim gives some weird messages what a FAT dont do but it still works. I mean eg. error has accord the system couldn't be execute pls connect yada, yada but it worked also on the slim after pressing the ps button.

There are 5 files you need to test by your own, vsh.self is one of them you just need to figure out the other 4 and then you can try by your own and see: OMG it's working

ps. I have installed them on dev_flash with MM 02.09 and not just emulated, oh and it also works on 3.55

#167 - DeViL303 - 167w ago
DeViL303's Avatar
Probably no point uploading these debug 4.00 dev_flash and update pkgs is there? anyone who needs em can just get them from the PUP anyway, and if they don't have the skills to do that they probably shouldnt be messing with their firmware in the first place! Happy hacking!

[release:04.0000:build:53640,20111122:tetsu@tetsu-linux18 target:0001EX-ww]

#166 - treveera - 167w ago
treveera's Avatar
Quote Originally Posted by Emad47 View Post
AC1D team if you want us to believe you then give us a fix for a game.


Do you actually think they need someone like you to believe them?

 

Sponsored Links

Sponsored Links

Advertising - Affiliates - Contact Us - PS4 Downloads - PS4 Forums - Privacy Statement - Site Rules - Top - © 2015 PlayStation 4 News