Just curious? But has "Dynasty Warriors Gundam 3" been patched? Or is this one of the many TB patched games still waiting it's turn?
|
|
|
|
Would you like to get all the new info from
PSX-Scene in your email each day?
Want to learn more about the team keeping you up to date with the latest scene news?
Read about them now! Check out our Developer bios, too! | ||
|
|
Just curious? But has "Dynasty Warriors Gundam 3" been patched? Or is this one of the many TB patched games still waiting it's turn?

Hey bitsbubba, I am the only one allowed around here to give twisted sarcasm! So stop it, before I get angry!
I found another site with more patched eboots--seems like the other site [ps3scenefiles.com] didn't include these. hmm? Someone fell asleep?
I don't link the site, because I don't know if it may contain other files than just patched eboots--so "only" a moderator will have to PM me so they can do their own investigation to see if they would like to share the site's info around here.

I made a mistake with one of the patches and it asked me for a higher firmware when I tried to run the game. It then said something like it will require to upgrade the firmware next time I try to load a game or something like that.
What are the steps to start all over? Do I try to repatch it again? Or must I run the rebuild database feature?

If you edited the PARAM correctly then yes just run Restore Database, if problem still persists them maybe the problem lies in the PARAM
can anybody help me out please i get unsupported data with call of juarez and binary domain??
I did the database rebuilt--- was scared, since this was my first time, but everything went fine. I lost my ghost icons created by EXT GAME DATA for many of my PSN games installed on my external and also the album folders for all of them.
The game was: SUPER STREET FIGHTER IV: ARCADE VERSION - BLUS30793
I had installed patch 1.05, 1.06, then 1.07 and then replaced the 1.07 fix files. Each patch had it's own fix files, but I was lazy to upload each one after I would install each patch. Perhaps this was it? Or perhaps 1.07 had a encrypted eboot. Because I had trouble creating a install pkg with that eboot.
I didn't see the sense of having to replace the fix files for each update. I thought since all fixes had just a param and eboot replacement, that I would do it until the last patch. Why could this had failed? Also the NFO file did not specify I had to replace each pkg install with the fix files -- one at a time. See below:
Now I am afraid to try this again, even in the proper sequence. I don't want to go through the database rebuilt. I hope someone else can report that they were able to successfully make this game work with all three patches and fixes?Code:+-__-Installation Notes-__--__--__--__--__--__--__--__--ooO-(__)-Ooo--__--+ | | | install patch updates 1.05, 1.06 and 1.07, yes all 3 are required. | | replace included files in /dev_hdd0/game/BLUS30793 | | | | tested on 3.55 MFW, but should work fine on 3.40+ | \ / +--Rant--------------------- - - - -------------------------------+

What I did for games like this was to let the PS3 update the game t where it errored out, then I went back into mM and applied the patch (to where ot worked fine with a spoof) but the best way to bypass the 'Rebuild Database' is to buold the patched EBOOT and PARAM into a pkg (or find one already built) and install that way

That is what I originally attempted to do with this pkg. Especially now since I had recently discovered the wonderful feature of PS3_EXTRA.
So I tried to create a pkg version of that fix file, but got this error that I reported in the last post found here: http://psx-scene.com/forums/f149/%5B...ml#post1012119 ([Mega-Thread] HACKING a PS3 - Tutorials and Explanations)
If you know how I can work this out, I would really appreciate this my Jedi master.![]()

| « Previous Thread | Next Thread » |