[elpaso666]

Originally Posted by DEFAULTDNB Use a spoofer, or edit the param.sfo for 3.40/41?

did you read what I wrote? PARAM.SFO has been fixed like always version 3.55 or 3.41

last week I have tried the same for SKYRIM with same result... when I used eboot.bin from duplex for patch 1.06 it started to work

[DEFAULTDNB]

Originally Posted by elpaso666 did you read what I wrote? PARAM.SFO has been fixed like always version 3.55 or 3.41 last week I have tried the same for SKYRIM with same result... when I used eboot.bin from duplex for patch 1.06 it started to work

Yeah I read what you wrote.

I use a 9.99 spoofer and havent seen "a system update is required" nag for months.

Just saying.

[elpaso666]

Originally Posted by DEFAULTDNB Yeah I read what you wrote. I use a 9.99 spoofer and havent seen "a system update is required" nag for months. Just saying.

i dont see it when i fix eboot from bd rip, i see it only when fixich PATCH... that means, there is something wrong with fixing...

this just confirms what I have written about Skyrim - my eboot.bin doesnt work, but the one from duplex works
************* [ - Post Merged - ] *************
anyway, im going to test the spoofer why not... right... hehe

[Nimation]

Originally Posted by jjkkyu v1.41 update v1.41 1.Add supporting resign 4.25 EBOOT to 4.21 in 4.XX options. 2.Fix 4.25 EBOOT resign to 3.55/3.41/DEX. http://rghost.net/41443086 Try resigning LittleBigPlanet Karting immediately!!

Hope you don't mind me posting this on some Persian forum, with full credit though.

Mirror (in case anyone has problem with rghost): http://www.mediafire.com/?zj8vsybtg24e09d

[vingen]

Hi, just wonder if you can rewrite the code to search all the eboot in games folder and patch it and replace it with the patched one, and rename the old eboot into eboot.bak. Hope u understand me, kinda boring doing the same thing for 250 games.

[richdotward]

Originally Posted by vingen Hi, just wonder if you can rewrite the code to search all the eboot in games folder and patch it and replace it with the patched one, and rename the old eboot into eboot.bak. Hope u understand me, kinda boring doing the same thing for 250 games.

An expert batch programmer could do im sure. Why would you want to anyhow? Update to one of the 4.xx firmwares and only a small amount of games would even need to be patched. 51 games here and only need to patch two, all others just work fine.

Rich

Sent from my iPad using Tapatalk HD - ps3 4.21 v 1.09 cechc03

[vingen]

Originally Posted by richdotward An expert batch programmer could do im sure. Why would you want to anyhow? Update to one of the 4.xx firmwares and only a small amount of games would even need to be patched. 51 games here and only need to patch two, all others just work fine. Rich Sent from my iPad using Tapatalk HD - ps3 4.21 v 1.09 cechc03

Since i update to 4.30 lots of my game stopped working which are patch for 3.55, when used this resigner i manage to play the game again.

[JonahUK]

Originally Posted by elpaso666 i dont see it when i fix eboot from bd rip, i see it only when fixich PATCH... that means, there is something wrong with fixing... this just confirms what I have written about Skyrim - my eboot.bin doesnt work, but the one from duplex works ************* [ - Post Merged - ] ************* anyway, im going to test the spoofer why not... right... hehe

There is nothing wrong with the fixes or the fixing method, it's your knowledge of the PS3 and pkg file installation that is lacking (no offence intended).

Whenever you install a pkg, it's FW version is written in the PS3's DB. If you then manually change the PARAM.SFO without also editing the DB or rebuilding it, the FW version is still unchanged so will nag for an update.

You can fix it by restarting in Recovery and rebuilding the database, problem solved.

[Ada Love Lace]

Originally Posted by JonahUK There is nothing wrong with the fixes or the fixing method, it's your knowledge of the PS3 and pkg file installation that is lacking (no offence intended). Whenever you install a pkg, it's FW version is written in the PS3's DB. If you then manually change the PARAM.SFO without also editing the DB or rebuilding it, the FW version is still unchanged so will nag for an update. You can fix it by restarting in Recovery and rebuilding the database, problem solved.

or overwrite the SFO by install new PKG ( in some case it s quicker or useful)

[elpaso666]

Originally Posted by JonahUK There is nothing wrong with the fixes or the fixing method, it's your knowledge of the PS3 and pkg file installation that is lacking (no offence intended). Whenever you install a pkg, it's FW version is written in the PS3's DB. If you then manually change the PARAM.SFO without also editing the DB or rebuilding it, the FW version is still unchanged so will nag for an update. You can fix it by restarting in Recovery and rebuilding the database, problem solved.

no problem with offensing. I was thinking about doing something wrong. Anyway FW spoofer could help either right?

Anyway is there a way to change the DB, or rebuilding is the only way? How is DUPLEX creating EBOOT.BIN and PARAM.SFO that work with PATCHED games? Without actually rebuilding it? When the PKG is normally downloaded from sony...

thx
************* [ - Post Merged - ] *************

Originally Posted by Ada Love Lace or overwrite the SFO by install new PKG ( in some case it s quicker or useful)

what do you mean by this? what PKG? some which is design for 3.55 FW natively?