|
|||||||||
|
|||||||||
|
|
|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Installer is already on a pwned iPhone. I've done it myself.
|
| Sponsored links Remove advertisements | |
|
|
|
|
|
|||
|
Cheers for that
The next step would be to incorporate some kind of payload functionality, similar to iPlus/iLiberty+, so that apps/fixes/whatever can be slipstreamed into ipsws as well.Kudos to the dev team
|
|
|||
|
The chronic dev team (http://www.chronic-dev.org/) are working on a tool called ipsw builder. Check it out...
James,
__________________
I like pie. |
| Sponsored links Remove advertisements | |
|
|
|
|
|
|||
|
Well, of course! Firmware 2.0 has a "shitload" of changes to the frameworks that make even Installer.app incompatible. Installer.app doesn't exist because there are no apps to install compatible with 2.0
|
|
|||
|
Quote:
James,
__________________
I like pie. |
|
|||
|
Here is some info you should look at:
When the IPSW Builder is running, it will move items to /tmp/ipsw for later use. While this is happening, one of the dmg files will be openable (mounts as a normal image, to be precise) and from there you can add applications to your liking. You must do this during this time: -after PwnageTool's progress screen says 'attaching root filesystem to...' and -before the PwnageTool asks gets your user password and starts patching and jailbreaking. I saw this during a random run (the dmg file somehow was visibly open and I tried adding apps in an 'I wonder if I can do this..." moment) and it stuck. Hope this helps.
__________________
HowardForums member, active in the Apple and related subforums. Member of the Samsung Blackjack Users Group Last edited by GenesisDH; 04-03-2008 at 01:19 PM. Reason: clarification |
| Sponsored links Remove advertisements | |
|
|
|
|
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|
|
|