[Custom Packages][Solved] Info.plist Command for symlink available?

[volkspost]

I have searched a lot and looked into the packages that come with Pwnage 1.1 but did not find a solution so far.

I wonder if it is possible to embed a "Command" for creating a symlink into the Info.plist of the custom packge.

Background: I am enhancing my webservice for creating Custom Carrier bundels (see here). Right now I am able to autocreate a complete pwn custom package with all the files and Info.plist on my webserver and make it ready for download. I could even create a symlink (the one the carrier bundle needs function properly on the iPhone) on the webserver, put it in the package, but this one is of cause resolved to the target (the carrier.bundle) when downloading.

Would like to be able to: I would need a Command (like the ones that are used for setting ownership and permission like "+s" in Info.plist) to create a symlink when building the custom firmware. Right now my custom package has a directory called my_Tmobile_US.bundle in /files/System/Library/Carrier Bundles/ and I would have to create a symlink 310410 into that directory with the help of Info.plist.

I know the commands for creating symlinks, that's not the problem, but I am unaware if it's possible to use them via Info.plist. Maybe its a similar process as Pwnage 1.1 uses for the pachtes with calling patch files, but I dont know.
If creating a symlink would be possible one could auto-create custom bundels that contain complete carrier bundles all from a web-interface without working on plist files.

BTW: I have seen here custom packages available for download that use Mac OS X Aliases. Even though this surprisingly works on building custom firmware if you use a Mac and Mac version of Pwnage 1.1 you are screwed in Windows. If you open those packages in Windows the Mac-Alias is converted to the target file/folder.

Hope you can can help on that

best,
volkspost

[iThor]

The only way currently is to use a pre-fabricated alias made under OS X as the plist affects the firmware prior to it being on a live system so if there was a command it would just use OS X to manufacture the SymLink not the iPHone. You could use a LaunchDaemon on first boot to make the SymLink as suggested by Chronic.

[volkspost]

The only way currently is to use a pre-fabricated alias made under OS X as the plist affects the firmware prior to it being on a live system so if there was a command it would just use OS X to manufacture the SymLink not the iPHone. You could use a LaunchDaemon on first boot to make the SymLink as suggested by Chronic.

Hi iThor!
I know and thats the problem. Using Mac OS x Aliasses works under Mac OS X but it wont help once you work on Windows. I have copied the budles with the Alias to a Winwows machine and the Alias turns into a folder.
I'll give Cronic's suggestion a try, saw it around in the forum.

Thx anyway

volkspost

[Iunder]

I now made a bundle for my custom plist files, i have set permissions to 0777. Is that correct permission for plist files or bether use another one ? Thnx in advance

[volkspost]

The only way currently is to use a pre-fabricated alias made under OS X as the plist affects the firmware prior to it being on a live system so if there was a command it would just use OS X to manufacture the SymLink not the iPHone. You could use a LaunchDaemon on first boot to make the SymLink as suggested by Chronic.

I have solved the issue with using a custom launch daemon and a script as suggested by ChronicProductions. Its already working. After some testing I will pubish it all.

thx

volkspost

[volkspost]

As promised here is a solution if your custom bundle needs special commands like mine (ln -s for creating a symlink). Works with FW 1.1.4 - 2.0 Beta 3 on pwnaged iPhone, boot neutered, unlocked. Applies to all other situations where you need to execute commands.

My goal was to create custom carrier bundles inside a pwn bundle, thats quite easy and done by my php driven website (not online yet - later today). To make the custom carrier bundle work properly once installed, a symlink with the MCC/MNC is needed.
I could not archive this with the known commands in the Info.plist. So I found a hint by ChronicProductions in another thread telling to use a combination of Launch Daemon and script. I played around the rainy Sunday, her's the result (example).

The Launch Daemon below and the script are auto-created by my PHP-driven webservice. The example Launch Daemon sits in /files/System/Library/LaunchDaemons the script sits inside my custom carrier bundle (/System/Library/Carrier Bundles/o2_de_custom.bundle).

After installing the custom firmware (including the bundle) with PwnageTool 1.1 on the first reboot of the iphone the Launch Daemon is calling the script once.
The script is then checking, if a specific symlink already exists and is renaming it then. After that the needed symlink is created, the Launch Daemon deleted and last not least the script itself is deleted - voila

Hope that helps, will work in other szenarios where commands are needed.

BTW: I found out about the Launch Daemon after checking the custom firmware file, the Dev Team uses a Launch Daemon for operating Boot Neuter. So - as usual - all credit goes to the Dev Team!

volkspost

Launch Daemon

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>KeepAlive</key>
<false/>
<key>Label</key>
<string>com.yourdomain.pwn_carrierbundle</string>
<key>LaunchOnlyOnce</key>
<true/>
<key>Nice</key>
<integer>20</integer>
<key>ProgramArguments</key>
<array>
<string>/System/Library/Carrier Bundles/o2_de_custom.bundle/symlinker.sh</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>StandardErrorPath</key>
<string>/var/logs/bn-stderr</string>
<key>StandardOutPath</key>
<string>/var/logs/bn-stdout</string>
</dict>
</plist>

Script

#!/bin/sh
#
# Name: Symlink Creator for o2_de_custom.bundle
# Desc: The shell script is called by the custom Launch Daemon
# de.volkspost.pwn_carrierbundle.o2_de_pwn.plist
# One-time checks if symlink is already there, renames it the and
# creates symlink for the custom carrier bundle
# deletes Launch Daemon and gets auto-deleted itself when done
#

# For users on Apple partner carriers but without iPhone contract
# Check if a symlink 26207 exists and rename it to old_26207
if [ -d /System/Library/Carrier\ Bundles/26207 ]
then
mv /System/Library/Carrier\ Bundles/26207 /System/Library/Carrier\ Bundles/old_26207
fi

# Create symlink for the custom carrier bundle o2_de_custom.bundle
ln -s /System/Library/Carrier\ Bundles/o2_de_custom.bundle /System/Library/Carrier\ Bundles/26207

# Remove the Launch Daemon de.volkspost.pwn_carrierbundle.o2_de_pwn.plist
rm /System/Library/LaunchDaemons/com.yourcompany.pwn_carrierbundle.o2_de_pwn.plist

# remove this script from custom carrier bundle o2_de_custom.bundle directory
rm /System/Library/Carrier\ Bundles/o2_de_custom.bundle/symlinker.sh

@mods: Would be great if one of you could insert a [Solved] into the thread title, thx a million