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

January 15, 2012 // 5:07 am - Below is an update from our Team AC1D ongoing thread on how current PS3 games work on lower Custom Firmware.

Finally, after a long period of a scene that got riddled by money hungry dongle suppliers we uncover this big scam and show you how things actually work.

First of all, none of the code the dongles use comes from the creators. All files used come directly from higher PS3 firmwares. This works by using plugins / SPRX's who are basically just drivers, from a higher PS3 firmware.

To get games to work, you need to use the files from higher firmwares, that games require. Those plugins we are talking about, also have the decrypt information stored in them that the games use to work.

Some of the newer SPRX's are compatible with older firmwares and can be used on older firmwares quiet easily. All you need to do is place them in the right folder and that's it.

Of course this procedure doesn't work with all the games quite so easy, some of the 3.6+ games load right away, others need some fixing. This fixing is done by patching the SPRX's to work with the lower firmware. Porting the drivers, so they can work with lower firmwares should be the easiest task.

Basically all this DRM does is nothing. The stick holds some drivers, like i explained earlier in this post, and lets the system use them. The HyperVisior LV1 Patches are nothing more then redirections to the USB stick / DRM fake.

The USB stick holds some dev_flash files, the system then uses. Its basically the same thing we did in the early stages of the Custom Firmware to load modified files quick and easy.

So after knowing all this, this explains why the dongles use DRM on their USB stick, simply to not let us see that they are really just scamming us with the cheapest materials they could find and some (by now old) dev_flash files stored in it. It's nothing more, and I'm sure that TeaM AC1D will empower more things and work on more in the future then the dongles have in last months.

We love Open Source and that's why we share this information with you. This needs to be stopped and we should all join hands to finally put an end to all of this. Use this information and do what you have to do.

Our respect goes out to Kakaroto, grafchokolo, Hermes, Deank, JaiCraB, Jjolano, Stoker25, Redsquirrel87, GeoHot, Condorstrike, Team Hades and everybody else we forgot to mention here.

Don't let yourself get fooled by these dongles guys and happy hacking to everyone!

-Team AC1D-

Team AC1D Uncovers How Current PS3 Games Work on Lower CFW

PlayStation Follow us on Twitter, Facebook and join us at our new site WWW.PSXHAX.COM!

#175 - spaceshot - January 16, 2012 // 4:21 am
spaceshot's Avatar
I have been waiting just too long for the Batman AC's crack to show up for ps3.

Hope that is the first thing to come out now..

#174 - DeViL303 - January 16, 2012 // 3:55 am
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!

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

#173 - elser1 - January 16, 2012 // 3:01 am
elser1's Avatar
i'll do anything to help also.i have a retail 3.41 slim if needed to test anything.

#172 - spunkybunny - January 16, 2012 // 3:01 am
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?

#171 - cfwprophet - January 16, 2012 // 2:48 am
cfwprophet's Avatar
Forgot to mentoin that we have used RETAIL files of 4.0 and also used a RETAIL 3.41 base fw.

#170 - racer0018 - January 16, 2012 // 2:45 am
racer0018's Avatar
Sounds good and will help in anyway that you need. Thanks for all the hard work.

#169 - lionsfan420 - January 16, 2012 // 2:40 am
lionsfan420's Avatar
Big thanx to cfwprophet, and DeVil303 for the advice, and files we are about to receive. again Thanx

#168 - DeViL303 - January 16, 2012 // 2:27 am
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.

#167 - cfwprophet - January 16, 2012 // 2:09 am
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

#166 - DeViL303 - January 16, 2012 // 1:31 am
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:[email protected] target:0001:DEX-ww]