PS3 xRegistry editing

[lmn7]

Nothing to do… I guess this game keep reading the resolutions from the BD PARAM.SFO (as DMC 4).

Since it worked for you, it probably depends on the games.


Side Note: Definitely GTA4 is region locked on Ps3 too (at least for SD users), since, even if it worked, you're not supposed to modify the PARAM.SFO, and therefore the PAL GTA4, couldn't start on a USA Ps3 (RDR i.e. doesn't have this problem).

It doesn't depend on games, using the modified PARAM.SFO should at least fix that video output error. Try rebuilding the database, since I assume you used the file copier to transfer the sfo, the PS3 is probably still using the old cached version in the database.

Also region locks on the PS3 aren't really a thing, most PS3's are region free and can play any game from any region. Unless you're strictly talking about video output.

 

[Peppe90]

It doesn't depend on games, using the modified PARAM.SFO should at least fix that video output error. Try rebuilding the database, since I assume you used the file copier to transfer the sfo, the PS3 is probably still using the old cached version in the database.

This makes sense, I'll try it right away.

Also region locks on the PS3 aren't really a thing, most PS3's are region free and can play any game from any region. Unless you're strictly talking about video output.

Yes, it's a video output problem. I'm pretty sure if use HD resolutions the game would normally boot. The message refer to the video output , not console region. Btw this game is pratically region locked for SD users (officially speaking).
I think it's the only one out of my 54 games with this issue.

Can I rebuild the database with the HAN Toolbox option, it's reliable??

 

[Peppe90]

Try rebuilding the database, since I assume you used the file copier to transfer the sfo, the PS3 is probably still using the old cached version in the database.

You're a scholar! Problem solved!!

In case I'd need to do this again (for other games), there's another way to clear the cache aside from rebuilding the database??

 

[lmn7]

Can I rebuild the database with the HAN Toolbox option, it's reliable??

Yes.

In case I'd need to do this again (for other games), there's another way to clear the cache aside from rebuilding the database??

You can create a game pkg with nothing but the PARAM.SFO inside, this will automatically update the database with the new PARAM.SFO. You can't use make_package_custom.exe to do this as it creates a different type of pkg, instead you should use something like psn_package_npdrm.exe. I'm not really familiar with all of the pkg creating tools, so you'll have to search around a bit.

 

[Peppe90]

You can create a game pkg with nothing but the PARAM.SFO inside, this will automatically update the database with the new PARAM.SFO. You can't use make_package_custom.exe to do this as it creates a different type of pkg, instead you should use something like psn_package_npdrm.exe. I'm not really familiar with all of the pkg creating tools, so you'll have to search around a bit.

I done it with the aldo's tools. Downloaded the GTA4 1.08 update, extracted it with PS3 Package Gui, changed the PARAM.SFO with your one and repacked it all with Content ID.

I noticed one thing. when repacking, the program changes the PS3 system version from 4.3000 (that's the correct one of the update PARAM.SFO) to 3.4000:

 

[DeViL303]

I noticed one thing. when repacking, the program changes the PS3 system version from 4.3000 (that's the correct one of the update PARAM.SFO) to 3.4000:

That's just the minimum version required for that game, it's not important.

 

[Peppe90]

That's just the minimum version required for that game, it's not important.

Ah ok, however it was an option I can change:

 

[Peppe90]

You can create a game pkg with nothing but the PARAM.SFO inside, this will automatically update the database with the new PARAM.SFO. You can't use make_package_custom.exe to do this as it creates a different type of pkg, instead you should use something like psn_package_npdrm.exe. I'm not really familiar with all of the pkg creating tools, so you'll have to search around a bit.

That's just the minimum version required for that game, it's not important.

A couple questions:

- Now I can just put the pkg into the pendrive and install, or I need to create a path on the Pendrive, like PS3/game/BLES00229/...pkg??

- I need to enable something before to install, like HAN or the debug packages option??

EDIT: The package's name matters?? I named it like the original update the aldo's tools program downloaded:

 

[DeViL303]

- Now I can just put the pkg into the pendrive and install, or I need to create a path on the Pendrive, like PS3/game/BLES00229/...pkg??

Just put it on the root, or in a "packages" folder. There are separate sections in the Package Manager for each location.

- I need to enable something before to install, like HAN or the debug packages option??

Yes, you always need to enable one of those to install packages on OFW. It depends if you have resigned the package or not which one you use. If you are just installing a PARAM.SFO you don't need to resign it, so just use Debug package enabler.

The package's name matters?? I named it like the original update the aldo's tools program downloaded:

No it does not matter, you can name the package anything you want. The content ID and category are the important things, that is the location the package installs to = dev_hdd0/game/CONTENTID/

 

[Peppe90]

Yes, you always need to enable one of those to install packages on OFW. It depends if you have resigned the package or not which one you use. If you are just installing a PARAM.SFO you don't need to resign it, so just use Debug package enabler.

I'm installing the full 1.08 update package (19mb), just replaced the PARAM.SFO and repacked. I need to resign it??

 

[DeViL303]

I'm installing the full 1.08 update package (19mb), just replaced the PARAM.SFO and repacked. I need to resign it??

It depends if it's an update for a disc game or a PSN game I think. I really don't know. it depends on file types in the update too. Safest thing is to resign it, then use HAN enabler to install it and run it.

 

[Peppe90]

It depends if it's an update for a disc game or a PSN game I think. I really don't know. it depends on file types in the update too. Safest thing is to resign it, then use HAN enabler to install it and run it.

It's an official update for GTA4. This game install almost 4gb of data into the HDD but it's the BD version. The pkg @Imn7 gave me the other time was unsigned. What could happen if I try to install it as it is?? You think it's not safe?? Anyway I could just delete the game folder, no problem. I'll re-install it and download the update from the ps3, if something will go wrong.

Otherwise, I should learn about this resigning thing. It's like when a Update is downloaded from the PSN, it have a sign (related to my ps3) that wouldn't have if downloaded from aldo's tools program, right?? So I need to resign the pkg to associate it to my ps3.

 

[Peppe90]

Just noticed I can't install packages anymore. I have this exact problem:

https://www.reddit.com/r/ps3homebrew/comments/9i11f0/ps3_with_han_installed_cant_browse_for_pkgs/

I think I'll do as that guy. Maybe the firmware/database rebuilding delete some HAN packages files?

 

[pinky]

you will get an infinite loading sign if the pkg(s) contain unique characters.

 

[lmn7]

What could happen if I try to install it as it is?? You think it's not safe??

Packages don't need to be signed, in fact you aren't even supposed to sign game/DLC/update packages, that is widely spread misinformation that everyone seems to follow. You should only resign PS2/PSX type packages. Use the debug package enabler for others.

Just noticed I can't install packages anymore. I have this exact problem

Not sure, doubt it's caused by a database rebuild though...

 

[Peppe90]

you will get an infinite loading sign if the pkg(s) contain unique characters.

The icon remains Always on infinite loading, even if there's nothing connected to the USB ports (exaclty as for the guy from that link).
In the delete options instead, the standard option is loaded, I can access it (btw it can't see the pkg into the pendrive if I connect it).

I've only the pkg on the pendrive. The Ps3 can see it as Always, I can enter the pendrive from the official columns or browse it with HAN Toolbox Explorer and see the pkg file.

Packages don't need to be signed, in fact you aren't even supposed to sign game/DLC/update packages, that is widely spread misinformation that everyone seems to follow. You should only resign PS2/PSX type packages. Use the debug package enabler for others.

Good to know

Not sure, doubt it's caused by a database rebuild though...

What about the filesystem check/rebuilding?? Most times it just do the check, but sometimes it says that the filesystem is damaged, then rebuild it.

However since that guy solved, I think I'll do the same.
What about directly reinstalling the HFW > HAN, instead of: OFW > HFW > HAN ?? That guy opted for the latter, but it's needed actually?

...If you have better suggestions for solving/figuring out the cause of the issue, let me know.

 

[pinky]

not sure. I've never experienced this problem. it's possible a rebuild of the database will work, but I don't know if anything is written to it before installation.

 

[Peppe90]

not sure. I've never experienced this problem. it's possible a rebuild of the database will work, but I don't know if anything is written to it before installation.

I already done the database rebuilding (to update a PARAM.SFO I replaced). I was asking if it clould be the cause of this problem. But @Imn7 said it's improbable.

 

[lmn7]

I already done the database rebuilding (to update a PARAM.SFO I replaced). I was asking if it clould be the cause of this problem. But @Imn7 said it's improbable.

I've never had this issue so I'm not sure. If you can't solve it, just reinstall HFW and you should be good to go.

 

[pinky]

I already done the database rebuilding (to update a PARAM.SFO I replaced). I was asking if it clould be the cause of this problem. But @Imn7 said it's improbable.

well, the only time I've seen that is a pkg with unique characters like the trademark symbol. the wii u does the same thing. if it's happening with all pkgs, yeah, reinstall the firmware.