PS3 xRegistry editing

[Peppe90]

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.

Thank you for the hint. However the problem isn't that in this case.

I re-installed the HFW (4.84.2), initialized HAN from the xploit page and the Package Manger has returned to work.

The update package have been installed without problems.

 

[Peppe90]

I guess there isn't any way to do something like that for PAL Ps1 games, to force them outputting at 60hz

 

[lmn7]

I guess there isn't any way to do something like that for PAL Ps1 games, to force them outputting at 60hz

I have never tried, but the idea is probably similar.

 

[Peppe90]

I have never tried, but the idea is probably similar.

Btw they are region locked, I think I can't boot them now, with the region set to North America.

 

[sandungas]

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.

Btw, for the PARAM.SFO files that are BOOTABLE=1 (in other words, all games and apps) there is no need to rebuild database

The problem is when we replace a PARAM.SFO by unnofficial means the info inside the database about that PARAM.SFO gets outdated
XMB loads the info from the database (not from the real PARAM.SFO), so what you see on XMB is outdated

But if you try to boot that game/app you will see a error message on screen because there is a mistmach in between the info inside the real PARAM.SFO and the info about that PARAM.SFO inside the database
After that error the firmware takes you back to XMB (you was trying to boot the game but the game doesnt boots at this first try)
At that point the database is updated and the info from the new PARAM.SFO is included in it... so from that point the game will work normally

----------------
In other words... if you want to replace a PARAM.SFO (by unnofficial means) there are 2 optional ways to complete the hack
1) by entering recovery menu and using rebuild database
2) by trying to boot it, "eating" that error, and repeat

Personally i think the option 1 is better... but i made lot of experiments with custom PARAM.SFO files where i was using option 2 (because lazyness)

 

[Peppe90]

Btw, for the PARAM.SFO files that are BOOTABLE=1 (in other words, all games and apps) there is no need to rebuild database

The problem is when we replace a PARAM.SFO by unnofficial means the info inside the database about that PARAM.SFO gets outdated
XMB loads the info from the database (not from the real PARAM.SFO), so what you see on XMB is outdated

But if you try to boot that game/app you will see a error message on screen because there is a mistmach in between the info inside the real PARAM.SFO and the info about that PARAM.SFO inside the database
After that error the firmware takes you back to XMB (you was trying to boot the game but the game doesnt boots at this first try)
At that point the database is updated and the info from the new PARAM.SFO is included in it... so from that point the game will work normally

----------------
In other words... if you want to replace a PARAM.SFO (by unnofficial means) there are 2 optional ways to complete the hack
1) by entering recovery menu and using rebuild database
2) by trying to boot it, "eating" that error, and repeat

Personally i think the option 1 is better... but i made lot of experiments with custom PARAM.SFO files where i was using option 2 (because lazyness)

This is interesting. I think I tried to boot the game more than one time… It always gave me the same error as the file wasn't replaced (the game couldn't output with the current video mode).

Rebulding the database bothered me a little 'cause I had to re-done my game's albums.

For this reason I wanted to learn the package installation method. It's very easy, and even quicker ('cause the file copier could take from a second to half an hour…).

 

[Peppe90]

Btw, for the PARAM.SFO files that are BOOTABLE=1 (in other words, all games and apps) there is no need to rebuild database

The problem is when we replace a PARAM.SFO by unnofficial means the info inside the database about that PARAM.SFO gets outdated
XMB loads the info from the database (not from the real PARAM.SFO), so what you see on XMB is outdated

But if you try to boot that game/app you will see a error message on screen because there is a mistmach in between the info inside the real PARAM.SFO and the info about that PARAM.SFO inside the database
After that error the firmware takes you back to XMB (you was trying to boot the game but the game doesnt boots at this first try)
At that point the database is updated and the info from the new PARAM.SFO is included in it... so from that point the game will work normally

----------------
In other words... if you want to replace a PARAM.SFO (by unnofficial means) there are 2 optional ways to complete the hack
1) by entering recovery menu and using rebuild database
2) by trying to boot it, "eating" that error, and repeat

Personally i think the option 1 is better... but i made lot of experiments with custom PARAM.SFO files where i was using option 2 (because lazyness)

I confirm, just trying to boot a game doesn't update the database.

I update the One Piece Pirate Warriors PARAM.SFO (it's a PSN game and don't have any official update, so I could only replace the SFO to do the trick).
I tried to boot the game multiple times, switching from 2 profiles, rebooting the Ps3 a couple times. It keep showing the message that the game couldn't boot with current video mode: therefore it just keep reading the SFO as it was before replacing, from the cache.

Now I'll finish check the other couple games to see if there are any needing to edit, then I'll do one last database rebuild.

 

[pinky]

you'll probably have to reinstall the PARAM.SFO if opening the game doesn't update the database. normally, replacing the file won't work, since the original credentials are in the metadata file.

 

[Peppe90]

you'll probably have to reinstall the PARAM.SFO if opening the game doesn't update the database. normally, replacing the file won't work, since the original credentials are in the metadata file.

I replaced the PARAM.SFO with the file copier. I don't know other ways to "install" it (as I said this game doesn't have any update).

However just replacing the PARAM.SFO should work (it worked for GTA 4), but it need to rebuild the database to read the replaced file.

 

[sandungas]

I confirm, just trying to boot a game doesn't update the database.

I made it tenths of times and the database was always updated for me... so im not sure why it doesnt works for you

The only requirement for it to work is the game/app needs to be bootable...otherway if you dont boot it the database is not rebuilt

 

[Peppe90]

I made it tenths of times and the database was always updated for me... so im not sure why it doesnt works for you

The only requirement for it to work is the game/app needs to be bootable...otherway if you dont boot it the database is not rebuilt

"Bootable" is checked in all PARAM.SFO I replaced. Maybe it depends on console type/firmware, I don't know.

Anyway, I found some games that are actually region locked (so the Ps3 games 100% region free story I heard, is not so true. They wanted you to buy a new HD tv by force…).

I edited their PARAM.SFO, then rebuilded the database, this time with the HAN Toolbox function (definitely quicker).

It worked for:
- Siren Blood Curse-PSN
- Wolfenstein 3d-PSN
- GT5 Prologue-BD

Didn't worked for:
- Flower-PSN (it tells me it happened a error…)
- One Piece Pirate Warriors-PSN (it seems to boot, but after some seconds it sends me back to the XMB)
- Fist of the North Star Ken's Rage-BD (keep showing me the usual video output message)

I'll try editing the SFO again in some different way, hoping it'll work. These are the last 3 games that I miss to make everything to work.

 

[Peppe90]

I have never tried, but the idea is probably similar.

What to do in this case:

I guess I have to leave the value as it is ignoring it. So it would be: 01 00 04 00 It's correct?? I already tried to overwrite the default 01 with 00, probably the cause of the errore is that.

Btw I really need to add this attribute flag for PSN games (Flower in this case)?? They only read from the HDD PARAM.SFO, what is it for this flag actually?

The one piece one has one more field, that NP_COMM_ID:

 

[lmn7]

What to do in this case:

View attachment 17411
I guess I have to leave the value as it is ignoring it. So it would be: 01 00 04 00 It's correct?? I already tried to overwrite the default 01 with 00, probably the cause of the errore is that.

Btw I really need to add this attribute flag for PSN games (Flower in this case)?? They only read from the HDD PARAM.SFO, what is it for this flag actually?

The one piece one has one more field, that NP_COMM_ID:

View attachment 17412

Change the 01 to 00. For PSN games you just change the resolution flags, no need to write that special flag as it reads the PARAM.SFO from the HDD.

 

[Peppe90]

Found out that One Piece have an update, so I made a package as I done with GTA 4 and installed it. Same thing, it keep ejecting me back to the XMB (I tried both ways with and without the attribute flag).

I'll try the same with Flower.

 

[Peppe90]

Change the 01 to 00. For PSN games you just change the resolution flags, no need to write that special flag as it reads the PARAM.SFO from the HDD.

Ah ok, so I'll try with flower just adding the NTSC resolutions without HEX editing

 

[Peppe90]

Change the 01 to 00. For PSN games you just change the resolution flags, no need to write that special flag as it reads the PARAM.SFO from the HDD.

Great, it worked for Flower!!

But I'm completely clueless about One Piece Maybe the problem is that I use the flag the first time, so it remains in memory even after next updates??
Actually before the last attempt I deleted Flower, then re-installed it. But it's about 650mb of download, One Piece is 11GB!! I hope I don't have to re-download it, but if it's the only solution...

 

[lmn7]

Great, it worked for Flower!!

But I'm completely clueless about One Piece Maybe the problem is that I use the flag the first time, so it remains in memory even after next updates??
Actually before the last attempt I deleted Flower, then re-installed it. But it's about 650mb of download, One Piece is 11GB!! I hope I don't have to re-download it, but if it's the only solution...

Yes that could be it, you need to rebuild database every time if you're replacing it through the file copier.

 

[pinky]

I replaced the PARAM.SFO with the file copier. I don't know other ways to "install" it (as I said this game doesn't have any update).

However just replacing the PARAM.SFO should work (it worked for GTA 4), but it need to rebuild the database to read the replaced file.

rebuilding the database rebuilds the metadata file (the database), so that's why it worked. you can make a package with ps3tools just package the PARAM.SFO, not the entire game. ignore the error about the EBOOT.BIN and ICON0.png. they're not needed to update the database. the package should be 100KBs iirc.

 

[Peppe90]

rebuilding the database rebuilds the metadata file (the database), so that's why it worked. you can make a package with ps3tools just package the PARAM.SFO, not the entire game. ignore the error about the EBOOT.BIN and ICON0.png. they're not needed to update the database. the package should be 100KBs iirc.

Well, to package the entire game isn't even possible for me. I'm packaging just the game update when available.

This is really interesting. Then I don't need to package the update, but just the PARAM.SFO. So pratically, for Ken's Rage (this game don't have any update) I've only to put the PARAM.SFO in a folder and drag and drop that folder here:

I understood correctly?

 

[Peppe90]

Yes that could be it, you need to rebuild database every time if you're replacing it through the file copier.

Yes, I'm rebuilding the database every time (I replaced all the files in a once, to rebuild all in a once), but for those 3 games it didn't worked.
Probably the issue about Flower and One Piece (both PSN games) is the attribute flag. I solved for Flower, but I fear I need to reinstall One Piece…
What if I delete the One Piece Param.SFO?? It will reset the flag thing?? Maybe it's Worth a try before deleting/reinstalling it.