Originally Posted by hquest

Let me just add some real cool info:

In fact, a fix here should be made: proper path is "~/Library/Application Support/PwnageTool/CustomPackages/" (note the slash after ~ char).

No need to modify official Pwnage files anymore; just drop bundles on this folder and they appears on Custom Packages

Now I can pwn my phone with all fixes I need, in a ridiculous simple way ^^

I saw that one. I am running pwnageTool 2.0.2 but dont see "~/Library/Application Support/PwnageTool/CustomPackages/", dont know why.

Just to add, dropping a custom payload into PwnageTool package does not alter the programm, the bundles are just available.

Once I find out why i dont see the path I will update the info.

thx hquest,
v.

Path needs to be created by hand.

Originally Posted by hquest

Path needs to be created by hand.

Ok, thanks for the info. i will give it a try.
v.

Am I misunderstanding something? I used the same carrier bundle I created for 2.0 and uploaded it again after PWNing to 2.01 and it worked for both... Is it not suppose to work in 2.0? I simply added the files via iFuntastic... worked in both software versions...

Originally Posted by bouda

Am I misunderstanding something? I used the same carrier bundle I created for 2.0 and uploaded it again after PWNing to 2.01 and it worked for both... Is it not suppose to work in 2.0? I simply added the files via iFuntastic... worked in both software versions...

I did not try this one. In FW 2.0.1's carrier bundles the following values changed (inside the bundles files):
version.plist FW 2.0 FW 2.01.
BuiltVersion 26 -> 2
CFBundleVersion 1 -> 2.2

Info.plist
CFBundleVersion 1 -> 2.2

Since FW 2.0 beta 4 the new file ResourceRules.plist got introduced.

I always try to keep the service up to date. Apple usually changes values for a reason. Maybe other functions access and use the files. So the FW 2.0 bundle may work on FW 2.0.1 as you said but I would upgrade.

During the day I will extend the service so you can select either to download the PwnageTool 2.0.2 compatible bundle (only for use with PwnageTool) or the pure custom bundle along with a custom readme for installation.

Just brilliant, thanks volkspost.

Did both of our phones this morning (the manual SSH way as I didn't want to incur the girlfriend's wrath by having to restore her phone AGAIN! ) - works like a charm.

Originally Posted by KneelBee

Just brilliant, thanks volkspost.

Did both of our phones this morning (the manual SSH way as I didn't want to incur the girlfriend's wrath by having to restore her phone AGAIN! ) - works like a charm.

Glad it worked for you. To make things easier I have extended the service a bit. Along with the PwnageTool 2.0.2 compatible custom bundle you can now download a version for manual installation along with a custom readme how to install for your carrier. This version is workng for Windows users aswell.

hey volkspost great site very easy to use, I created a custom bundle for TMobile US wasn't sure if it was really necessary but I kept getting that update carrier settings so I said why not (always clicked cancel either way)...I dropped the bundle in the correct folder and did not need to create a symlinc as my MCC/MNC was a 5 digit # combined that wasn't listed...rebooted the phone but didn't notice Carrier Services in Settings>Phone> but I have not synced yet to see if the message has popped up as I will not be home till later is it possible I missed something? or just wait to sync and see maybe? either way excellent post!

Originally Posted by alpineflip

.I dropped the bundle in the correct folder and did not need to create a symlinc as my MCC/MNC was a 5 digit # combined that wasn't listed...

You need to either create the symlink if it does not exist, or ensure current link points to bundle you just uploaded. But this step can't be skipped.

Originally Posted by alpineflip

hey volkspost great site very easy to use, I created a custom bundle for TMobile US wasn't sure if it was really necessary but I kept getting that update carrier settings so I said why not (always clicked cancel either way)...I dropped the bundle in the correct folder and did not need to create a symlinc as my MCC/MNC was a 5 digit # combined that wasn't listed...rebooted the phone but didn't notice Carrier Services in Settings>Phone> but I have not synced yet to see if the message has popped up as I will not be home till later is it possible I missed something? or just wait to sync and see maybe? either way excellent post!

As hquest said: You have to create the symlink, wont work otherwise. First check if the Symlink is there. if so, rename it to old_symlink. Then create the symlink as stated in the readme.
Reason: Once you insert the simcard or start the iPhone, the unique MCC/MNC (the number) from your provider gets searched in that directory on the iPhone. if it's there (the symlink), the iPhone uses the file (in this case carrier bundle) that is associated. So a correct symlink (it's similar to an Alias on Mac-OS X) is absolutely necessary to make it function.

Hope that helps