Listen up rebels and anti-establishment fiends, PwnageTool 4.1 is now up and running thanks to the iPhone Dev-Team. The biggest news in addition to the usual iPhone/iPod hacks is the addition of the Apple 2G jailbreak. Of course, like all jailbreaks of late (including both limera1n and greenpois0n), this is also untethered.
Here’s what the Dev-Team says on its blog:
Through a combination of the recently released geohot limera1n exploit , @comex’s recently released pf kernel exploit, and our original pwnage2 exploit, PwnageTool 4.1 works untethered on these devices at firmware 4.1:
- AppleTV 2G
- iPad (firmware 3.2.2)
- iPod touch 4G
- iPod touch 3G
- iPhone4
- iPhone 3GS
- iPhone 3G
PwnageTool allows you to restore to a custom IPSW file. For instance, you can restore to a pre-jailbroken firmware while simultaneously maintaining your current baseband (and thus your ultrasn0w carrier unlock). You can also add whatever packages you want in the “Expert” mode of PwnageTool, if you wish to pre-install Cydia packages. iPhone 3G users get the additional benefit of selecting their own boot and recovery logos, and features like multitasking and battery charge percentage.
The fact that you can go back to pre-jailbroken firmware without any problems with your current baseband is huge, because most of you who have unlocked iPhone handsets have been holding off for a while.
The Dev-Team goes on for Apple 2G users, since it’s the new addition after all:
AppleTV 2G users: Welcome to the JB family! Right now, about all you can do is command-line stuff via ssh. You also have afc2 available, so you can use tools like ifunbox to move files around. These are the *very* early days of AppleTV 2G jailbreaking, so it’ll take some time for JB app developers to come up with methods to use your AppleTV 2G from the remote, versus the command line. PS: Your ssh password is “alpine”…please change it when you can 🙂
Looking to get cracking with the new PwnageTool? Check out the iPhone Dev-Team blog for all the links to the tools you’ll need right below.
[Via: Dev-Team Blog]