DECR-1000A 4.53 firmware

A DECR-1000A kit I am receiving is believed to have a 4.53 firmware installed.

As I can't seem to find much information about it on psdevwiki, does anybody have any experience with that firmware?

 

I don't have a PUP file for that firmware. I have 4.50 and 4.55.
I doubt it has much different from the 2 I just listed but it's nice to see a firmware we don't have listed anywhere.

 

I'll take a backup of everything I can before I do anything, but ideally I'd like to install a firmware with OtherOS support so I've been looking at 3.15 MFW released.

Do you know of any patches I could apply to for example the 4.55 PUP to use with MFW Builder and install to the kit?

Also, is it not possible to include the relevant ps1 and ps2emu files and for use on the ref kit in any way? I know usually this is not possible on a ref kit, but since this link (http://www.psdevwiki.com/ps3/4.53_CEX) shows that some ps1 & ps2emu related files were changed in the CEX variant of the firmware, is it not possible to port these over?

 

I can't imagine why you'd want to install OtherOS when there's not really much support for it and could lead to issues.

I have no experience with MFW but I'm sure you CAN do it, it's just a lot more work since DECR firmware is a lot more restricted than say a DECH (DEX) firmware.

I assume you can try and mess with the PS1/2 emulation files but I don't know how much success you'll have. I know XboxSurgeon was having a go at it but no idea if he hit a roadblock or if he succeeded.

 

I was thinking of using the kit for multiple reasons, but since it hasn't had much support I probably will just use it for my main purposes instead.
Do you know how to use the internal HDD for BD Emulation purposes?

 

http://assemblergames.com/l/threads/using-ps3-bdemulator-for-dex-test-tool.50203/

 

There's a tool called PS3 Gen Tools (official tool by sony so I cant link it) that allows you to format an HDD or Flash Drive to be used as a BDEMU device.

I don't really know how to use the internal HDD as such but I assume you can send the image over Target Manager and it will write to it. Not overly sure but it could work.

Or follow the guide above this post.

 

You can upload via Target Manager over LAN, via command line over LAN (if you have the SDK installed) or as PixelButts said you can use the PS3 Generator Tools to upload a BDEMU image you've created by a locally connected harddrive (i.e. remove the DEV HDD from it's bay and connect via a powered USB to SATA to your PC).

Any chance you picked up your Reference Tool from UK eBay very recently? I picked up two off a seller on there recently and one was filled with Playstation Home development builds, and the other was from Quantic Dream and had a rather unfinished build of Heavy Rain on! So be mindful of any goodies you might have on your BDEMU drive before you format it.

 

Excellent, that seemed to work perfectly.. when I updated Target Manager to v4.20

Do you know whether I'm able to convert/repackage pkg files for CEX/DEX consoles to install and run correctly on a DECR-1000? I've heard people have been able to.

 

If you mean paid content PSN packages, yes. Download your .pkg and corresponding .rap file (legally owned for this particular purpose!), extract the PKG with PkgView or something similar taking note of the ContentID (needed for package.conf, sample below).

Content_ID=UP0177-NPUB30242_00-CRAZYTAXIPACKAGE
K_Licensee = 00000000000000000000000000000000
DRMType = Free
Content_Type = GameExec
Package_Version = 01.00

(adjust package version according to the original PKG's PARAM.SFO)

Copy out the EBOOT.BIN and any EDAT you may find in the extracted pkg folder to somewhere, then using ESSSE Resigner, resign the EBOOT and EDAT you just copied out as free content for 4.21 CFW (if your REF TOOL is 4.21+ FW) using the .rap (and potentially a klic, or both maybe), and then decrypt the now patched CEX NPDRM EBOOT.BIN using TrueAncestor SELF Resigner and then patch using the same tool to a DEX NPDRM EBOOT. You may have to brute force and play about to get the klic or search for it online, but it's pretty simple once you figure it out.

Then with your resigned as free EDAT and resigned as free NPDRM DEX EBOOT, rebuild the pkg including the modified files you've made using my sample package.conf above (fill in correct ContentID) and use force_package_npdrm.exe to finally build the PKG.

Command should be something like "force_package_npdrm package.conf NPEBXXXXX"

Obviously replace NPEBXXXXX with the one that corresponds with your original package.

If you want to keep the original packages "vanilla" so to speak, just repackage the pkg up without modifying any files and then just FTP over the fixed files afterwards to where the pkg was installed. Or you can create little fix pkgs that you can install. Completely up to you.

Baring in mind this is for PSN NPDRM content and not disc based games, the process is a little different if you want to do these, i'll add the necessary steps if needed.

Hope this helps, and if you need any files or a hand, feel free to give me a PM.

 

Hmm, I'll give this another go tomorrow, but using Crazy Taxi with the above gives me this:-

Code:

>> !ERROR!: D:\CT\NPUB30242/USRDIR/CrazyTaxi.edat is not a supported NPDRM EDATA
. (already authorized)
>> !ERROR!: D:\CT\NPUB30242/USRDIR/CrazyTaxi.edat is not an NPDRM EDATA.

 

Is that when rebuilding the package? If so, use the version I said to use, force_package_npdrm.exe

If thats not it, then unfortunately you've either missed/ballsed up a step or my instructions are terrible.

It works, definitely with Crazy Taxi as its what I've used to test the method and i'm looking at it on my TOOL right now.

 

QUICK RECAP ON STEPS:
Extract PKG
Get ContentID
Resign EBOOT.BIN and EDAT as free for 4.21 CFW (NPDRM) using ESSSE and applicable .rap.
Decrypt EBOOT.BIN you just made so you end up wth EBOOT.ELF, then resign as DEX NPDRM using other tool and end up with a finished DEX NPDRM EBOOT.BIN.
Repackage up with force_package_npdrm.exe

Sorry for double post, meant to edit. Mods feel free to merge. Cheers.

 

Hmm, well I'm basically doing that. The error comes up when using make_package_npdrm.exe, I can't seem to find force_package_npdrm.exe.

 

So, I extract it, get the ContentID, then..

Use ESSSE and:
Resign EDAT with option 5
Resign EBOOT with option 1 and then option 2 for FREE NPDRM 4.21

Then use TrueAncestor SELF Resigner and:
Decrypt with option 1 to make ELF and then 11 to make DEX NPDRM EBOOT.BIN

Then attempt to repackage, which gives me the error above.

EDIT: This seems to work and run properly on the TOOL when I just repackage it up and copy over the modified files, so maybe it is my version of make_package_npdrm.exe which is creating the issue rather than the modified files being the issue.

 

Will PM you with a link to it. Two tinkles.

EDIT: Done.

 

I haven't had much luck with unlocking the emulation of PS1/2 on my decr yet....

 

DECR lack any PS2 hardware and its firmware doesn't have the PS1 or PS2 emu.

 

Maybe by using the MFW builder it could be done. I'd imagine you'd just need to get the right versions for the firmware of the respective PS1 and PS2 emulator files and dependencies and ensure everything gets hooked properly.

The solution might even have to be a PS3 application which would load all of the necessary modules first needed for actually booting the PS1/PS2 emulators as opposed to the system software natively handling it.

 

The FW I am on now allows Ps1 classics to run but not Isos. The ps2 classics crash the kit completely.