09-15-2012,05:52 PM

Originally Posted by
JOshISPoser
if you are patching an update, you patch the update folder, not the original back up folder. that might be why you're getting unsupported data if i'm understanding it correctly.
other than that, i would just use pkg's if it is this difficult. i've really only used one patch, but it was only a 1.0 patch, so i didn't need to patch an update.
Yea the problem that most of us were having is that when manually patching your GAME data folder the database does not update and still recognizes it as a 3.60 and up update. That is why the PKG's are the best solution if you do not care to use the spoofer. You are right though, keep GAME data fixes separate from the main game folder with the game. Not sure if this was the problem that Plop47 was experiencing or not but this is not what I was doing. I know better 

Originally Posted by
HyperTech
if the n0drm file is for the original game, then you have to replace the param.sfo and the eboot.bin into the backup game directory.
internal hdd=hdd0/games/blus88888
external hdd=usb/gamez/blus88888
if the n0drm file is for an update version of the game, then you have to replace the param.sfo and the eboot.bin into the update game directory.
internal hdd=hdd0/game/blus88888
external hdd=hdd0/game/blus88888
i hope its help.
You are also on the right track but its pretty much the same thing I was explaining above that even when you do exactly as you instructed here, the game updates that you manually patch will still show 3.60 or higher unless you use one of the repackaged NODRM updates out there or repackage it yourself. Then it will update the PS3 database and everything should work fine as normal. All the patches I DL'ed from PS3 news the other day work great so far!
As far as I know, my ps3 has never had an undetected error.
