Absolutely no support should be expected or will be given. XPwn is also NOT winpwn. Winpwn will have things like easy package management, an actual, non-lame system of installing stuff.
I've seen the code for it, and it will be pretty awesome when finished. Those tasks are outside the scope of XPwn. This utility is merely an implementation of Pwnage, which is the work of roxfan, Turbo, wizdaz, bgm, and pumpkin. Those guys are the real heroes. MuscleNerd has put a lot of work into the 3G effort.
The BootNeuter unlock for first-generation iPhones packaged within is primarily his effort. Thanks also go to gray and c1de0x for their RCE efforts.
Thanks to chris for his hardware wisdom, Zf for his French humor, and pytey for the support on the serial stuff. XPwn attempts to use all the same data files and patches as PwnageTool to avoid duplication of present and future labor. I believe that wizdaz probably put the most sweat into PwnageTool, and the pwnage ramdisk is the work of Turbo.
XPwn on Linux would not have been possible without libibooter, which was written by cmw, based on the Linux iPhone recovery driver written by geohot. A special shout-out to cmw, who I have been helping with winpwn. He's put a lot of hard work into winpwn, and should also be credited with doing some of the initial exploratory work with the undocumented DMG format. There are three utilities in this package, as well as the bundles and FirmwareBundles folders from PwnageTool, and Turbo's autopwn ramdisk.
The general series of steps should be to use ipsw to create a custom IPSW with the user's preferences done once per custom ipsw required , then itunespwn done once per computer so that future DFU restores will be made easier. Finally, either dfu-util Mac or Linux or idevice Windows should be used as necessary on the iPhone to perform the actual exploit necessary to allow it to accept our code. It is technically possible to skip itunespwn and just use idevice or skip idevice and just use itunespwn, but I recommend doing both.
NOTE: Important change for 2. This is important, since that's how the jailbreak actually occurs. Yes, I know, confusing syntax. You can also specify actions to exclude from the "FilesystemPatches" section of the Info.
The most common use of the '-e' flag is to disable automatic activation, i. Note that the double-quotes are necessary. This value is specified in megabytes NOT mebibytes. This allows the restore to happen much, much more quickly. This is disabled by default for unlock safety reasons. These provide instructions to BootNeuter which provides unlocking for iPhones.
If you choose to use BootNeuter, you must specify the location where the 3. These cannot be included with xpwn due to copyright restrictions.
If you do not specify -cleanup, BootNeuter will be accessible via SpringBoard. The last options are for tar-files to merge. All permissions and ownership will be preserved except for already directories that already exist. This is to prevent accidental clobbering we're guessing you don't really want to alter permissions on existing directories. Come join the forum here And downloads will be here Stuck at the iPlus screen at need to start over?
Labels: dev team , iphone , jailbreak , unlocking. Tuesday, March 11, iPhone 2. Get the scoop on the 2. More on Hackint0sh. Zibri Says Check Out iLiberty! This initial version does not unlock, but it will do Jailbreak or Activate only, for those people who like to keep-it-simple. ZERO chance of ending up with a downgraded bootloader by accident as with some other programs. Rerunning iPlus. If you need to rerun iPlus - for example if you forgot to put payload. You do not need to use -u though, and do not use installer to add apps before rerunning.
Posted by geeb at PM 2 comments:. They are "just tar errors on uid changes that are not harmful". They will be cleaned up on the next version. People are asking for the differences between iPlus and Ziphone: iPlus patches afc2, uses the 3. Ziphone empties your refrigerator and makes your dog pregnant. Posted by geeb at AM 3 comments:. The reason? Exploit is being a bitch! More news when I have it. We are pleased to announce iPlus 2. Posted by geeb at AM 5 comments:.
Labels: aviegas , dev team , geeb , iphone , iplus. Sunday, March 9, iPlus 2. Sneak preview of iPlus 2. Pic1 Pic2 Coming soon! Oh, and 2. Posted by geeb at PM 6 comments:.
Tired of messing with command lines? OK, to make iPlus a 1-click operation: Make a command line desktop shortcut Command line shortcuts on the desktop? What's next, dogs and cats living together in harmony? Right click on an empty space on the desktop to open the context menu 2. Select New 3. Select Shortcut with a left-click 4. Dont forget the "" in the correct places! Select Next 6. Name your shortcut iPlus is a good name and push Finish.
To run it, stick your iPhone on the dock and click that shortcut! New Version of iPlus Coming Soon! The most important change is that now I know how to prevent the "Reair Needed" problem that has been report by some users.
Once again with the help of some folks from the Dev Team I was able to figure out where the problem is and devise a way to fix it. Also the following features are planned: - PPC support - Better payload integration - Second pass completion infomation. Star Permalink master. Branches Tags. Could not load branches. Could not load tags. Raw Blame. Open with Desktop View raw View blame. This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below.
To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters. You signed in with another tab or window.
Reload to refresh your session.
0コメント