need help with White Knight Chronicles II cant get it to work

[baddagger]

oh, ok. It sounds like you have the old file manager. I think the new one came in at 4.03. We're on 4.04 right now. It's not a major update, but whenever you have time don't forget to update your multiMAN. You've pretty much got it done now.

ok so i brought the file over to my pc.. i took the eboot and put it in the same fold that had the eboot fix program.... now do i take that file and use it to replace the update eboot i installed on my ps3 hard drive? or do i use that eboot file to replace the eboot file on my external hard drive that has the game on it? or do i replace both?

[BahumatLord]

after you ran eboot_fix.bat you should see 2 eboot files. One named EBOOT.BIN_ORIGINAL. You can delete that one. The other named EBOOT.BIN. You copy that file back to where you originally copied it from using multiMAN's file manager. Do not put it in your game backup folder. you don't have to do anything to your game backup

[baddagger]

well that game is working right now .. im at the install screen so, sooo far its good.. Thanks soo much for all the help man

[BahumatLord]

Now that you know how to do it you should be able to patch other games pretty easily. Have fun man

[ynotrhyme]

Do we need to patch the eboots from their respected update folders for all games?

[dan74cold]

I can't get this to work.

Game backup is my game backs folder on ps3.
Installed update 101 and copied to pc eboot_bin and param_sfo from ps3 game update dir.
After running eboot_fix I've got new eboot_bin, edited fw in param_sfo to 3.55, then ftped both files to pse games update folder /dev_hdd0/game/BLUS30784.
Ftped param_sfo from game backup dir changed fw from 3.66 to 3.55 and ftped it back to ps3.
Started MM selected WCK2 and then started game from BD icon.

System asked about update to 3.6. What I did wrong ?
BTW there is psarc file in WCK2 update but this is encrypted .sdat file, so BruteForce can't fix this one. AFAIK there is no way to decrypt .sdat files currently.

[BahumatLord]

The game works - ignore the psarc and sdat files. What firmware are you running? You should install a 4.20 version spoofer. As long as the eboot is fixed it doesn't matter what the param.sfo says.

[BahumatLord]

since you're fixing the update you don't need to touch the actual game backup

[dan74cold]

I'm on 3.55 kemaw, game is on internal hdd., shall I set some special flags for this game in MM ?
I don't have a 4.20 version spoofer installed, but I was thinking that this is only necessary while connecting to PSN with CFW.
This is first time I've ever see such message (about fw update), how its even possible when I've edited param_sfo ?

To make sure I got idea, game is signed with 3.66 keys and those are unknown, but game update is signed with 3.60 and they are known. So all we need to do is install update and resign eboot form game update directory ?

I did that even fixed param_sfo but can't launch game because when I cancel update to 3.6 system returns XMB. I will try install spoofer, is there kemaw version or I have to switch to rebug ?

[BahumatLord]

Ok - here's how editing the PARAM.SFO works. When you do it on your game backup, you need to hit refresh in multiman for it to read the change. When you do it on your update folder the index doesn't get updated until you do at least one successful launch. You would need to make a dummy update pkg with just the eboot and changed param.sfo. It's complicated and a pain in the ass if you don't know how to do it already. The easiest thing you can do is install a version spoofer. Yes, they were used to help getting on PSN, but they also prevent this kind of thing where you get prompted to update and prevent accidental system updates. Everybody should have one installed. No excuses on that when your little sister or a friend accidentally updates your system when you're not around. The best one to use is the one made by Rebug. It works on KMEAW too so you just need to install the spoofer and activate it following the on-screen prompts. You don't have to swap firmwares. You should be able to find it in the Rebug section on PS3SceneFiles or Codename: REBUG