(adsbygoogle = window.adsbygoogle || []).push({}); Mods can you please sticky this thread, thank you

everyone who saw this post usefull please thank and nominate it, thank you

ATTENTION:::::::::::::::

i got a pm saying it works so ima upload a vid today if possible


Part with checksum i got from YelloJagwa's post (parts 13 and 14)so dont forget to thank him

here is a link to his thread to thank him too

You must login or register to view this content.


....On final step, need to get past checksums and im done....

Dont ask me or anyone else for a lobby because i am seeing alot of that and my inbox keeps getting filled with messages just asking for me to invite them

when i get a lobby running and after me and the people working on this with me test it i will start posting FREE lobbys to everyone

Also people who keep asking what this does, this is to get your modified patch_mp.ff onto MW2 by tricking your ps3 into downloading it and yes you can do challenge lobbys with it



EDIT:::::::::::::::::::::::::::::::::

How to install linux, check bottom

Added way to get past checksum

Added way to unpack files

Added winhex pro thanks to niccrx

Added Modded 1.10 PKG file thanks to lilparth

Added New 1.11 Patch thanks to Durk

Added Net Framework 1.1

Added steps to find ps3 proxy

Added new patch, pkg, no modded patch at the moment.






1. download CF3B5's proxy




You must login or register to view this content.




2. set it up like you would with the unknowns patch blocker




-go to internet connections on ps3
-click custom
-click automatic to you see use proxy
-type in your ip found in command prompt after you type in "ipconfig"



You must login or register to view this content.


-when you get to test connection click start on the proxy then click test connection ( first click ps3 and you might have to turn off your firewall )



You must login or register to view this content.



6. Now open up log on the proxy server



You must login or register to view this content.





7. remove the mw2 patch




8. start up mw2 and accept to download the patch but when it gets to 10% stop the download




9. go to log and you should see this




You must login or register to view this content.




You must login or register to view this content.




10. now keep that up but now you need to get a pkg file from here




You must login or register to view this content.




11. now you will need a patch file to mess with or a modded one




regular patch from Durk




You must login or register to view this content.




Modded patch from Mw2CptPrice_




You must login or register to view this content.






modded 1.10 .PKG thanks to lilparth(wont work now due to 1.11 patch)




You must login or register to view this content.




13. now put your modded patch file in the pkg file that you downloaded earlier by following Micheals post(thanks to him)





You also need the ps3 dev kit thanks to ii-Reactive-NGU





You must login or register to view this content.






Don't post this anywhere else without giving him, Michael, credit.

You need a root account in Linux for this! I used Ubuntu 10.04. The SDK is for Windows as well, but there's no readme for the files. So I set up VMWare with Ubuntu so I can use Linux inside Windows.
In Ubuntu, Fedora, Yellow Dog, etc, type "sudo apt-get install yum" in Terminal.
Type in your root password.
Now, look for a repository with PS3 binaries. You can get some from PS3Bodega.
You need the PS3 SDK kit as well. You can't get the full 600MB one, get the 156MB one. I won't provide a link, go find it.
With yum and the RPM installed, now you can just type "yum ps3unpkgr" in Terminal instead of code editing.
When you get the SDK and install the binaries (the RPM is right there), you can use "ps3unpkgr -x <PKG name>" and unpack everything.
To pack it into a PKG again, use "ps3unpkgr -c <PKG name>" and it will pack.
I'm not going to sit and explain everything so thoroughly if you don't know how to do it. If you really are wanting more, reach me another way.






14. Now you need to fix the checksums(havent tested this part yet cuz i dont have linux)- this is thanks to ecstasy







1.) Calculate the new checksum with Hex Workshop
2.) Use the Windows calculator in scientific mode set to "HEX" to calculate the difference between the two checksum by subtracting one from another.
3.) Lower or up the 2 digit HEX codes (in a "useless" area") according to the difference you have found.

It may be easier to first convert the checksum to decimal before subtracting one from the other. From the answer (decimal code) you can very easily calculate what to change.

Let's say that you found the new checksum to be 1000 (decimal) lower than the old one. This means you will have to add 1000 (decimal) to the new one. The easiest way to do this would be to a change a "00 00 00 00" area in the bios to this : 255 + 255 + 255 + 235 or (in hexadecimal) FF + FF + FF + EB.






15. now go to replace files in the proxy server




You must login or register to view this content.






on the left put (the link that the orginal pkg)in the white box your will need to put this
copy it from your log





You must login or register to view this content.





which is what you got from your log earlier





16. on the right put in your pkg file by clicking the dot or . and then go find your moddified pkg file





You must login or register to view this content.





17. now start up mw2 and install the patch(it will take longer because it is tricking the server to download somthing from your computer)





18. if you did it right this should pop up





You must login or register to view this content.





19. now you are done













thanks to

IW_JOSH for his patch file

Flokko-RCD for his modded patch file

hiskitters23 for helping me the whole way





i have gotten this to work with the pkg but i never put in my patch because i dont really know how to edit the pkg file to put it in there so i posted this because somone out there might know




Should be stickied so people can refrence from it because it does work




i have run into some checksums here and there but if you follow this you shouldnt get any




You do not need to do anything with your hdd and you dont need hdd studio
Please dont ask for invites or plz plz plz get me all the titles and emblems, just do it yourself because it isnt hard and only takes like 2 hours to do if you follow the tut





Edit: for those who cant find proxy after you install it





1. go to start and click search





You must login or register to view this content.





2. click on all files and folders





You must login or register to view this content.





3. search for ps3 proxy server





You must login or register to view this content.





4. click on this folder and drag it to ur desktop





You must login or register to view this content.





5. and your done





You must login or register to view this content.






Fix to netframework by ryguy88





Here are the links:




Original .NET 1.1:
You must login or register to view this content.


Next, download this (.NET 1.1 Service Pack 1):
You must login or register to view this content.

Then restart the machine and run the PS3 Proxy GUI installer, should work for Win7 x64 on my machine.






EDIT::::::::






for those who are trying to do this with me and need winhex





1.download anywinhex





2.go to help>register





3. paste this and click ok





Name: "VDOWN" Addr1: "VDOWN" Addr2: "2010" Key1: 82225C3CD14246EEBD9F106073901D61 Key2: AEE15C3654BE26467AE12A6253FC25E0 Chksm: 89








EDIT::::::::::::::::::::::::;


.How to install linux

1. Download Ubuntu thanks to ryguy88






You must login or register to view this content.







2.download VMwear player







You must login or register to view this content.







3.Open up Vmwear Player and click install new virtual machine







You must login or register to view this content.







4. Now click on the ubuntu and then open







You must login or register to view this content.






5. Follow instructions to download and when u are done this should pop up, u need to sign in with the password u used to register your vmwear player(note, it will take it a long time for this screen to pop up and u may have a black screen with a blinking cursor at the top before this pops up)





You must login or register to view this content.







6. now click applications >accesories>Terminal(like command prompt) and this may take a while to come up also






You must login or register to view this content.






7. Now follow the steps to unpack and pack the pkg

Not to me I only post when i have something to help with.

I am trying the Windows version of the edit from the other post.

looks good will try this

nvm
It blocked the forums cause they don't want stuff leeched but they leeched this post

broken link bro

I see what went wrong... dunno why michael posted that then since -c is check not compress :confused:

1,005 Replies, Well 1,006 NOW! damnn

NAME
rpm - RPM Package Manager
SYNOPSIS
QUERYING AND VERIFYING PACKAGES:

rpm {-q|--query} [select-options] [query-options]

rpm {-V|--verify} [select-options] [verify-options]

rpm --import PUBKEY ...

rpm {-K|--checksig} [--nosignature] [--nodigest] PACKAGE_FILE ...

INSTALLING, UPGRADING, AND REMOVING PACKAGES:

rpm {-i|--install} [install-options] PACKAGE_FILE ...

rpm {-U|--upgrade} [install-options] PACKAGE_FILE ...

rpm {-F|--freshen} [install-options] PACKAGE_FILE ...

rpm {-e|--erase} [--allmatches] [--nodeps] [--noscripts] [--notriggers] [--repackage] [ --test] PACKAGE_NAME ...

MISCELLANEOUS:

rpm {--initdb|--rebuilddb}

rpm {--addsign|--resign} PACKAGE_FILE ...

rpm {--querytags|--showrc}

rpm {--setperms|--setugids} PACKAGE_NAME ...

select-options

[PACKAGE_NAME] [-a,--all] [-f,--file FILE] [-g,--group GROUP] {-p,--package PACKAGE_FILE] [--fileid MD5] [--hdrid SHA1] [--pkgid MD5] [--tid TID] [--querybynumber HDRNUM] [--triggeredby PACKAGE_NAME] [--whatprovides CAPABILITY] [--whatrequires CAPABILITY]

query-options

[--changelog] [-c,--configfiles] [-d,--docfiles] [ --dump] [--filesbypkg] [-i,--info] [--last] [ -l,--list] [--provides] [--qf,--queryformat QUERYFMT] [-R,--requires] [--scripts] [-s,--state] [--triggers,--triggerscripts]

verify-options

[--nodeps] [--nofiles] [--noscripts] [--nodigest] [--nosignature] [--nolinkto] [--nomd5] [--nosize] [ --nouser] [--nogroup] [--nomtime] [--nomode] [ --nordev]

install-options

[--aid] [--allfiles] [--badreloc] [ --excludepath OLDPATH] [--excludedocs] [--force] [-h,--hash] [--ignoresize] [--ignorearch] [--ignoreos] [--includedocs] [--justdb] [--nodeps] [--nodigest] [--nosignature] [--nosuggest] [--noorder] [--noscripts] [--notriggers] [--oldpackage] [--percent] [--prefix NEWPATH] [--relocate OLDPATH=NEWPATH] [--repackage] [--replacefiles] [--replacepkgs] [--test]

DESCTION

rpm is a powerful Package Manager, which can be used to build, install, query, verify, update, and erase individual software packages. A package consists of an archive of files and meta-data used to install and erase the archive files. The meta-data includes helper scripts, file attributes, and descriptive information about the package. Packages come in two varieties: binary packages, used to encapsulate software to be installed, and source packages, containing the source code and recipe necessary to produce binary packages.

One of the following basic modes must be selected: Query, Verify, Signature Check, Install/Upgrade/Freshen, Uninstall, Initialize Database, Rebuild Database, Resign, Add Signature, Set Owners/Groups, Show Querytags, and Show Configuration.
GENERAL OPTIONS

These options can be used in all the different modes.

-?, --help
Print a longer usage message then normal.
--version
Print a single line containing the version number of rpm being used.
--quiet
Print as little as possible - normally only error messages will be displayed.
-v
Print verbose information - normally routine progress messages will be displayed.
-vv
Print lots of ugly debugging information.
--rcfile FILELIST
Each of the files in the colon separated FILELIST is read sequentially by rpm for configuration information. Only the first file in the list must exist, and tildes will be expanded to the value of $HOME. The default FILELIST is /usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc:/etc/rpmrc: ~/.rpmrc.
--pipe CMD
Pipes the output of rpm to the command CMD.
--dbpath DIRECTORY
Use the database in DIRECTORY rather than the default path /var/lib/rpm
--root DIRECTORY
Use the file system tree rooted at DIRECTORY for all operations. Note that this means the database within DIRECTORY will be used for dependency checks and any scriptlet(s) (e.g. %post if installing, or %prep if building, a package) will be run after a chroot(2) to DIRECTORY.

INSTALL AND UPGRADE OPTIONS

The general form of an rpm install command is

rpm {-i|--install} [install-options] PACKAGE_FILE ...

This installs a new package.

The general form of an rpm upgrade command is

rpm {-U|--upgrade} [install-options] PACKAGE_FILE ...

This upgrades or installs the package currently installed to a newer version. This is the same as install, except all other version(s) of the package are removed after the new package is installed.

rpm {-F|--freshen} [install-options] PACKAGE_FILE ...

This will upgrade packages, but only if an earlier version currently exists. The PACKAGE_FILE may be specified as an ftp or http URL, in which case the package will be downloaded before being installed. See FTP/HTTP OPTIONS for information on rpm's internal ftp and http client support.

--aid
Add suggested packages to the transaction set when needed.
--allfiles
Installs or upgrades all the missingok files in the package, regardless if they exist.
--badreloc
Used with --relocate, permit relocations on all file paths, not just those OLDPATH's included in the binary package relocation hint(s).
--excludepath OLDPATH
Don't install files whose name begins with OLDPATH.
--excludedocs
Don't install any files which are marked as documentation (which includes man pages and texinfo documents).
--force
Same as using --replacepkgs, --replacefiles, and --oldpackage.
-h, --hash
Print 50 hash marks as the package archive is unpacked. Use with -v|--verbose for a nicer display.
--ignoresize
Don't check mount file systems for sufficient disk space before installing this package.
--ignorearch
Allow installation or upgrading even if the architectures of the binary package and host don't match.
--ignoreos
Allow installation or upgrading even if the operating systems of the binary package and host don't match.
--includedocs
Install documentation files. This is the default behavior.
--justdb
Update only the database, not the filesystem.
--nodigest
Don't verify package or header digests when reading.
--nosignature
Don't verify package or header signatures when reading.
--nodeps
Don't do a dependency check before installing or upgrading a package.
--nosuggest
Don't suggest package(s) that provide a missing dependency.
--noorder
Don't reorder the packages for an install. The list of packages would normally be reordered to satisfy dependencies.
--noscripts
--nopre
--nopost
--nopreun
--nopostun
Don't execute the scriptlet of the same name. The --noscripts option is equivalent to

--nopre --nopost --nopreun --nopostun

and turns off the execution of the corresponding %pre, %post, %preun, and %postun scriptlet(s).
--notriggers
--notriggerin
--notriggerun
--notriggerpostun
Don't execute any trigger scriptlet of the named type. The --notriggers option is equivalent to

--notriggerin --notriggerun --notriggerpostun

and turns off execution of the corresponding %triggerin, %triggerun, and %triggerpostun scriptlet(s).
--oldpackage
Allow an upgrade to replace a newer package with an older one.
--percent
Print percentages as files are unpacked from the package archive. This is intended to make rpm easy to run from other tools.
--prefix NEWPATH
For relocatable binary packages, translate all file paths that start with the installation prefix in the package relocation hint(s) to NEWPATH.
--relocate OLDPATH=NEWPATH
For relocatable binary packages, translate all file paths that start with OLDPATH in the package relocation hint(s) to NEWPATH. This option can be used repeatedly if several OLDPATH's in the package are to be relocated.
--repackage
Re-package the files before erasing. The previously installed package will be named according to the macro %_repackage_name_fmt and will be created in the directory named by the macro %_repackage_dir (default value is /var/spool/repackage).
--replacefiles
Install the packages even if they replace files from other, already installed, packages.
--replacepkgs
Install the packages even if some of them are already installed on this system.
--test
Do not install the package, simply check for and report potential conflicts.

ERASE OPTIONS

The general form of an rpm erase command is

rpm {-e|--erase} [--allmatches] [--nodeps] [--noscripts] [--notriggers] [--repackage] [--test] PACKAGE_NAME ...

The following options may also be used:

--allmatches
Remove all versions of the package which match PACKAGE_NAME. Normally an error is issued if PACKAGE_NAME matches multiple packages.
--nodeps
Don't check dependencies before uninstalling the packages.
--noscripts
--nopreun
--nopostun
Don't execute the scriptlet of the same name. The --noscripts option during package erase is equivalent to

--nopreun --nopostun

and turns off the execution of the corresponding %preun, and %postun scriptlet(s).
--notriggers
--notriggerun
--notriggerpostun
Don't execute any trigger scriptlet of the named type. The --notriggers option is equivalent to

--notriggerun --notriggerpostun

and turns off execution of the corresponding %triggerun, and %triggerpostun scriptlet(s).
--repackage
Re-package the files before erasing. The previously installed package will be named according to the macro %_repackage_name_fmt and will be created in the directory named by the macro %_repackage_dir (default value is /var/spool/repackage).
--test
Don't really uninstall anything, just go through the motions. Useful in conjunction with the -vv option for debugging.

QUERY OPTIONS

The general form of an rpm query command is

rpm {-q|--query} [select-options] [query-options]

You may specify the format that package information should be printed in. To do this, you use the

--qf|--queryformat QUERYFMT

option, followed by the QUERYFMT format string. Query formats are modified versions of the standard printf(3) formatting. The format is made up of static strings (which may include standard C character escapes for newlines, tabs, and other special characters) and printf(3) type formatters. As rpm already knows the type to print, the type specifier must be omitted however, and replaced by the name of the header tag to be printed, enclosed by {} characters. Tag names are case insensitive, and the leading RPMTAG_ portion of the tag name may be omitted as well.

Alternate output formats may be requested by following the tag with :typetag. Currently, the following types are supported:

:armor
Wrap a public key in ASCII armor.
:base64
Encode binary data using base64.
:date
Use strftime(3) "%c" format.
:day
Use strftime(3) "%a %b %d %Y" format.
:depflags
Format dependency flags.
:fflags
Format file flags.
:hex
Format in hexadecimal.
ctal
Format in octal.
:perms
Format file permissions.
:shescape
Escape single quotes for use in a script.
:triggertype
Display trigger suffix.

For example, to print only the names of the packages queried, you could use %{NAME} as the format string. To print the packages name and distribution information in two columns, you could use %-30{NAME}%{DISTRIBUTION}. rpm will print a list of all of the tags it knows about when it is invoked with the --querytags argument.

There are two subsets of options for querying: package selection, and information selection.
PACKAGE SELECTION OPTIONS:

PACKAGE_NAME
Query installed package named PACKAGE_NAME.
-a, --all
Query all installed packages.
-f, --file FILE
Query package owning FILE.
--fileid MD5
Query package that contains a given file identifier, i.e. the MD5 digest of the file contents.
-g, --group GROUP
Query packages with the group of GROUP.
--hdrid SHA1
Query package that contains a given header identifier, i.e. the SHA1 digest of the immutable header region.
-p, --package PACKAGE_FILE
Query an (uninstalled) package PACKAGE_FILE. The PACKAGE_FILE may be specified as an ftp or http style URL, in which case the package header will be downloaded and queried. See FTP/HTTP OPTIONS for information on rpm's internal ftp and http client support. The PACKAGE_FILE argument(s), if not a binary package, will be interpreted as an ASCII package manifest. Comments are permitted, starting with a '#', and each line of a package manifest file may include white space separated glob expressions, including URL's with remote glob expressions, that will be expanded to paths that are substituted in place of the package manifest as additional PACKAGE_FILE arguments to the query.
--pkgid MD5
Query package that contains a given package identifier, i.e. the MD5 digest of the combined header and payload contents.
--querybynumber HDRNUM
Query the HDRNUMth database entry directly; this is useful only for debugging.
--specfile SPECFILE
Parse and query SPECFILE as if it were a package. Although not all the information (e.g. file lists) is available, this type of query permits rpm to be used to extract information from spec files without having to write a specfile parser.
--tid TID
Query package(s) that have a given TID transaction identifier. A unix time stamp is currently used as a transaction identifier. All package(s) installed or erased within a single transaction have a common identifier.
--triggeredby PACKAGE_NAME
Query packages that are triggered by package(s) PACKAGE_NAME.
--whatprovides CAPABILITY
Query all packages that provide the CAPABILITY capability.
--whatrequires CAPABILITY
Query all packages that requires CAPABILITY for proper functioning.

PACKAGE QUERY OPTIONS:

--changelog
Display change information for the package.
-c, --configfiles
List only configuration files (implies -l).
-d, --docfiles
List only documentation files (implies -l).
--dump
Dump file information as follows:

path size mtime md5sum mode owner group isconfig isdoc rdev symlink

This option must be used with at least one of -l, -c, -d.
--filesbypkg
List all the files in each selected package.
-i, --info
Display package information, including name, version, and description. This uses the --queryformat if one was specified.
--last
Orders the package listing by install time such that the latest packages are at the top.
-l, --list
List files in package.
--provides
List capabilities this package provides.
-R, --requires
List packages on which this package depends.
--scripts
List the package specific scriptlet(s) that are used as part of the installation and uninstallation processes.
-s, --state
Display the states of files in the package (implies -l). The state of each file is one of normal, not installed, or replaced.
--triggers, --triggerscripts
Display the trigger scripts, if any, which are contained in the package.

The ps3unpkgr is part of the set of files that he said he will not provide a link to.

Most of the leaked files are 1.6 and do not (like the set on TPB) contain some vital files. (Like ps3unpkgr)

Assuming you did manage to get hold of ps3unpkgr, ( from the leaked 1.9 release that is FULL, file is 192_sdk_full.rar, but I'm unable to find it), the program is designed to open development packages ONLY and doesn't work with retail packages.

Someone has copied shanes work and put it on ***** claiming it as his own even though hes used the pictures which says 'shane' haha!