iPhone Jailbreak 5.1.1

Download iOS 6 Direct Links – Leaked

2012-06-15T06:09:00.003+02:00

Download iOS 6 Direct Links for iPhone 4S, 4, 3GS – iPad 3, 2 and iPod Touch 4G – Apple TV 3G, 4G.
Apple is planing to unveil it’s iOS 6 firmware at WWDC 2012 as it is confirmed due to banners being hungat the Moscone Center in San Francisco, macrumors reported today that Chinese forum WeiPhone.com claims to contain iOS 6 beta build 10A5316k download links and other unreleased softwares.

Download iOS 6 Direct Links

MacRumors, also notes that:

“The accuracy of the claim can not be confirmed given that the links are not yet pointing to the files, but clicking on the links does take users to an error page stating “Your session has expired.” Altering the URLs to reference a different build number or making other changes yields an “Access denied” error message, suggesting that there is indeed something unique about the URLs.”

iOS 6 Beta, Safari 6 Download Links

Third-generation iPad

Consumer: Wi-Fi, Wi-Fi + Cellular (GSM), WiFi + Cellular (CDMA)
Enterprise: Wi-Fi, WiFi + Cellular (GSM), WiFi + Cellular (CDMA)

iPad 2

Consumer: Wi-Fi, WiFi + 3G (GSM), WiFi + 3G (CDMA), Revised Wi-Fi
Enterprise: Wi-Fi, WiFi + 3G (GSM), WiFi + 3G (CDMA), Revised Wi-Fi

iPhone

Consumer: 4S, 4 (GSM), 4 (CDMA), 3GS
Enterprise: 4S, 4 (GSM), 4 (CDMA), 3GS

iPod touch

Consumer: 4th Generation
Enterprise: 4th Generation

Apple TV

Consumer: 2nd Generation, 3rd Generation

Other iOS

Safari 6

Consumer: - Safari 6 Developer Preview for Lion, Uninstaller

If the Above Links Didn’t work Please Stay Update for iOS 6 Mirror Links

Stay Updated to Download iOS 6

Recommend iOS 6 on Google

Redsn0w Can Jailbreak iOS 5.1.1 On iPhone, iPad, iPod touch (A4 Devices) [How-To-Tutorial]

2012-05-29T07:55:00.002+02:00

Apple is clearly cracking the productivity whip in their iOS team offices and have wasted no time at all in producing and pushing out an update to their mobile operating system, taking the latest version to 5.1.1. While the latest release might offer some additional features, standard bug fixes and security patches, it also serves to keep the jailbreak development teams on their toes by forcing them to push an update where appropriate for their tools.

We have tested and can confirm that current latest version of Redsn0w jailbreaking tool can be used to jailbreak Apple’s latest iOS offering tethered on A4 powered devices such as iPhone 4, iPad 1, iPod touch 4G and below, thus allowing you to have continued access to all of the benefits of a liberated iOS Device. This has also been confirmed by MuscleNerd of the iPhone Dev-Team. We are carrying on our tradition of being reliable when it comes to all things Apple and jailbreak, by bringing you a step by step method on jailbreaking your iPhone, iPad and iPod touch on iOS 5.1.1 using Redsn0w.
How to jailbreak iOS 5.1.1 using Redsn0w

Step 1: Download the latest version of the iPhone Dev Team’s Redsn0w tool for your operating system (Windows / Mac).
Step 2: Not a requirement, but it is always good practice to connect the device to iTunes and perform a backup of the contents. Alternatively, users can opt to back up the device to iCloud if enabled.
Step 3: After the backup is complete, upgrade the device’s firmware to iOS 5.1.1. Users can choose to either do this via an OTA update on the device, or by plugging the device onto your PC or Mac, firing up iTunes and accepting and installing the update, or by downloading the iOS 5.1.1 device-specific firmware file and doing a manual install through iTunes.
Step 4: Download the iOS 5.1 (not iOS 5.1.1) IPSW file that corresponds to the specific device you are using.
Step 5: Locate the Redsn0w download folder from Step 1, unzip the contents and run the executable file to launch Redsn0w.

Step 6: Select ‘Extras’ on the Redsn0w GUI and the choose the ‘Select IPSW’ option.

Step 7: When prompted, point to IPSW file from Step 4 (which is iOS 5.1) and select it.
Step 8: On the main home screen of Redsn0w, select ‘Jailbreak’ and then make sure the ‘Install Cydia’ option is selected before proceeding.
Step 9: The on-screen prompts will now walk you through the process to put the device into DFU mode. This is a requirement for the jailbreak process to be successful. Make sure to follow all steps carefully.
Step 10: When DFU mode is detected, Redsn0w will automate the rest of the process on-screen before finishing off on the device. During the process, it is entirely normal to see white lines of text scrolling down the device’s screen. When the device reboots, the jailbreak process is complete which should be evident by the presence of the Cydia icon on the home screen.
Since this is a tethered jailbreak, you will have to boot your device into tethered boot mode on every restart. You can do this by launching Redsn0w, select "Extras", then"Just Boot" in order to boot your device tethered.

You are now free to feel extremely smug knowing that you are using a jailbroken device, even though Apple have tried their very best to prevent it. The setup process of Cydia is extremely easy, with on-screen prompts guiding users through the process. After the data is done reloading and the Cydia app restarts, it will be ready to use.

untethered511.blogspot.com

Prevent iPhone4 Baseband Update

2012-05-28T15:15:00.002+02:00

UPDATE: This method WILL work for iPhone 4 RESTORING to 4.3

This page ONLY deals with iPhone 4 baseband protection. I'm sorry this will not work for any other device.

You can protect your iPhone 4 BB restoring to iOS 4.2.1. Follow these steps exactly:

Get the latest TinyUmbrella.

Get the latest greenpois0n rc5 update (http://greenpois0n.com)

Open TinyUmbrella

Plug in your device and save SHSH (make sure 4.2.1 SHSH were saved, if not don't bother continuing)

Start TSS Server (If you get errors read the help section or FAQs or comment below typically it fails because you have some kind of web sharing enabled... use google to fix it - your issue really not much I can do...)

Open iTunes

Select your device in iTunes

Shift(windows) / Option(Mac) restore -> Select the 4.2.1 ipsw

Restore SHOULD error with a 1013 error. Click the "ok's" and close iTunes.

With your device sitting with the usb pointing to iTunes (recovery mode), enter DFU by pressing and holding HOME + POWER until your screen goes black... then after a count of 2 (1.5-2 seconds) let go of POWER but keep holding HOME. If all goes well you will see nothing but a black screen. If your timing is even a LITTLE bit off, you will see the apple logo and your phone will boot back into recovery mode... Go back to step 10 and try again.

You're now in DFU mode. Start greenpois0n and press 'Jailbreak'

Once greenpois0n has finished its thing. Press 'Complete!'

Let your device restart. You should end up on the activation screen.

Congrats your baseband was preserved and you are now on 4.2.1

Put your device into DFU mode and then click 'Fix Recovery'

Click 'Yes'

Your device's screen will turn white and you'll see debug boot information.

Eventually your device will boot into the activation screen.

Congrats. You're on 4.2.1 (again)? :)

If you get a 16XX error then try entering DFU and go to step 5.

If your restore does NOT end in a 1013, it means your baseband was updated. This is likely because you did not have the TSS server running OR you updated without TinyUmbrella OR you are working with a device OTHER than iPhone 4.

Sn0wbreeze 2.9.4 With iOS 5.1.1 Untethered Jailbreak Support Released

2012-05-26T17:56:00.004+02:00

iH8sn0w has also released Sn0wbreeze v2.9.4, which includes suport for iOS 5.1.1 untethered jailbreak for iPhone, iPad and iPod Touch.

Sn0wbreeze makes use of pod2G's iOS 5.1.1 untethered jailbreak, which was released earlier today.

Sn0wbreeze allows users to create custom iOS 5.1.1 firmware file that is pre-jailbroken, which can then be used to upgrade their iPhone, iPad or iPod Touch to iOS 5.1.1. In case of iPhone, Sn0wbreeze also preserves the baseband from getting upgraded so that it can be unlocked using Ultrasn0w (though Ultrasn0w is not yet compatible with iOS 5.1.1).

Here's what's new in Sn0wbreeze v2.9.4:

Added the 5.1.1/9B206 untether that was released with today's absinthe update.
Added 5.0/9B206f (Apple TV 2) support.
Minor UI changes (thanks @icj_!).
Bug Fixes.

Sn0wbreeze 2.9.4 supports the following iOS devices running on iOS 5.1.1:

iPhone 3GS, iPhone 4
iPad 1
iPod Touch 3G, iPod Touch 4G
Apple TV 2

iH8sn0w has explained why Sn0wbreeze doesn't support iPhone 4S, iPad 2, which are powered by A5 chip and iPad 3 (the new iPad), which is powered by the A5X chip:

A5(X) Support?: As stated many times in the past, sn0wbreeze cannot be updated to work on A5(X) devices until a low level exploit in DFU or iBoot is found and made public. Therefore, A5(X) users will have to rely on using the lovely absinthe.

A5(X) Baseband Preservation/Hacktivation? For those running A5(X) devices and need to preserve your baseband, there is nothing you can do at the moment. For those wanting to hacktivate, the only advice I can give is to buy the carrier's SIM (the one its locked to obviously) on ebay. The SIM does not have to be active with the carrier to activate the phone.

Sn0wbreeze also doesn't support the revised iOS 5.1.1 software update that was released by Apple earlier today, so GSM iPhone 4 users should download the older iOS 5.1.1 from here.

In our opinion, Absinthe is the easiest way to jailbreak your iOS device, but iPhone 4 and iPhone 3GS users who depend on unlocking should use Sn0wbreeze or Redsn0w (whenever Dev team releases it with iOS 5.1.1 untethered jailbreak support) as it preserves the baseband.

You can download the latest version Sn0wbreeze, which is available only for Windows users using this link.

If you need help with Absinthe 2.0.x, then check out our step-by-step guide to jailbreak your iOS device using Absinthe 2.0.1:

As always, let us know how it goes in the comments.

Absinthe 2.0 has arrived!

2012-05-25T14:54:00.001+02:00

After copious amounts of work and many sleepless nights Absinthe 2.0 is finally here to jailbreak your device. This release has been a large collaborative effort between Chronic-Dev Team and iPhone Dev Teams (Jailbreak Dream Team)
This jailbreak supports firmware 5.1.1 ONLY and is again one of the most easiest jailbreaks to use (so easy your grandma could do it ;D)

Absinthe 2.0 supports the following devices:

iPad1,1 – 2,1 – 2,2 – 2,3 – 3,1 – 3,2 – 3,3
iPhone2,1 – 3,1 – 3,3 – 4,1
iPod3,1 – 4,1
(Support for iPad2,4 will be added at a later date)

How To Use Absinthe 2.0:

1. Make a backup of your device in iTunes by right clicking on your device name under the ‘Devices’ menu and click ‘Back Up’.
2. Once your backup is complete return to your device and go to Settings – General – Reset – Erase all Content and Settings. This will make the jailbreak process much faster.
3. Open Absinthe and be sure you are still connected via USB cable to your computer.
4. Click ‘Jailbreak’ and wait…. just be patient and do not disconnect your device.
5. Once jailbroken return to iTunes and restore your backup from earlier. Right click on your device name under the ‘Devices’ menu in the left panel of iTunes and click ‘Restore from Back Up…’ then select the latest backup you created before. (restoring this backup will return all the content previously on your device ie, apps, photos, etc.)
6. Thanks for using Absinthe, enjoy your jailbroken iDevice!

Download Links

Absinthe2.0 MacOSX (10.5, 10.6, 10.7)
Absinthe2.0 Windows (XP/Vista/Win7)
Absinthe2.0 Linux (x86/x86_64)

Absinthe 2.0 is out !

2012-05-25T14:44:00.002+02:00

The 5.1.1 untethered jailbreak I talked about for weeks now is out. Hopefully.

The wait is over !

Enjoy guys !

Actual download website : http://greenpois0n.com/

~pod2g

iOS 5.1.1 Untethered Jailbreak: Absinthe 2.0 Now Covers iPad 3,3; Release Expected Friday In HITB Conference

2012-05-25T05:03:00.002+02:00

It was confirmed earlier this week that the highly anticipated iOS 5.1.1 untethered jailbreak would be called "Absinthe 2.0" and that the new tool should be released for public as early as this week. Thanks to "xvolks," one of the members of the jailbreak team, users also got a glimpse of the jailbreak tool in action in a video.
Until now, the new untethered jailbreak tool "Absinthe 2.0" was expected to cover the majority of devices, running iOS 5.1.1, while two devices - the global version of the new iPad and the iPad 2 Wi-Fi, R2 - remained to be tested with the new jailbreak tool.
On Thursday, pod2g took to his Twitter page once again and made the announcement of the inclusion of the iPad 3,3 to the list of supported devices. With the new iPad now fully supported by the iOS 5.1.1 untethered jailbreak, the only device left to be tested is iPad 2 Wi-Fi, R2 (iPad 2,4).
"OK just added iPad3,3 support to Absinthe thanks to @flawlessfox. Only remains iPad2,4 now but we need the actual device," pod2g tweeted.
Here's the updated list of devices that the new jailbreak will support:
Tested devices: iPhone 3GS, iPhone 4, iPhone 4 CDMA, iPhone 4S, iPad 1, iPad 2 Wi-Fi, iPad 2 GSM, iPad 2 CDMA, iPad 3 Wi-Fi, iPad 3 CDMA, iPad 3 Global, iPod 3G, iPod 4G and Apple TV 2.

Devices still need to test: iPad 2 Wi-Fi, R2.
Unsupported devices: Apple TV 3.
Will It Be Released In The Hack In The Box Conference On Friday?
With leading iOS hackers like pod2g, MuscleNerd and others attending the "Hack In The Box" (HITB) security conference in Amsterdam, the entire jailbreak community is having a close eye on the event for any significant news regarding the iOS 5.1.1 untethered jailbreak. Helping the excitement ramp up, pod2g even tweeted:
"Any people of #HITB2012AMS has an iPad2,4? Model number: either MC954 or MC989. Please check in Settings / General / About."
According to iDownloadBlog, given that only one device left to be tested, the chances of the release of the iOS 5.1.1 untethered jailbreak this week has been increased. Rumors also gaining momentum saying that the Chronic Dev Team and company might release the tool during the Dream Team's HITB keynote Friday.
The site even suggested that the iOS 5.1.1 untethered jailbreak would be demonstrated live in the conference Friday, followed by its highly awaited released before the conference concludes. The speculation was based on a tweet sent out by the official Twitter account for the Hack In The Box Security Conference. The tweet confirmed that "Jailbreak Live" would take place Friday, for which they are offering special 1-day passes.
"SPECIAL @chronicdevteam 1-day passes for #HITB2012AMS @ EUR699! Come see @pod2g @p0sixninja @planetbeing @nikias JAILBREAK LIVE (Pls RT)," read the tweet.
Key Facts About iOS 5.1.1 Untethered Jailbreak
iOS hacker MuscleNerd has shared some key facts about the upcoming jailbreak tool. However, he has clearly mentioned that the information "is tentative and subject to last minute refinements." Here's the crux of his post:

pod2g's 5.1.1 untethered jailbreak covers all devices, except for AppleTV3,1, which currently has no path for jailbreaking.
The 5.1.1 A5 jailbreak is very similar to the A5 5.0.1 jailbreak. iOS hacker "pimskeks" has done a tremendous job supporting both 5.0.1 and 5.1.1 in Absinthe.
Similar to 5.0.1, there will also be a 5.1.1 CLI "cinject" binary and redsn0w version of the 5.1.1 untethered jailbreak.
Absinthe, cinject, and redsn0w will all provide the same jailbreak in different fashions.

Pod2g has also updated his blog with multiple reasons to jailbreak iOS devices. According to him, jailbreaking allows:

Changing the iOS experience with powerful tweaks that can't ever exist on the AppStore : SBSettings, WinterBoard, IntelliScreenX, LockInfo, and lot of others...
Playing retro games on console and arcade emulators.
Having access to a unix shell in your pocket, and all the open source software that can run on a unix OS.

He made it clear that jailbreak is not mean for pirating App Store applications.

iPhone Applications in Python

2012-05-25T04:51:00.000+02:00

Writing iPhone applications is easy. Well, if you are willing to wait until Apple provides the ability to run their SDK-based applications on actual hardware. Until then, you are forced to go through a quite long list of steps. While I've updated this process somewhat, it's still anything but "easy".

Even then, when you get the whole thing working, you still have to know Objective-C. To some extent there is no getting around that without someone writing a giant abstraction for you: Apple's frameworks are all written in Objective-C, and their APIs are documented in it. However, that doesn't mean you really need to also learn all the quirks of C syntax or be forced to use Objective-C libraries to solve all of your problems when you are already deep into something else.

This same issue came up on the desktop, and spawned a number of projects that connect Objective-C with other languages. This is an area I have recently gotten into, writing JocStrap, which unifies Java and Objective-C's object models, allowing one to, for instance, develop for the iPhone in Java. Having done this then put me in the perfect frame of mind to try to get other languages over, and the #1 request was Python, which already has an amazing project behind it: PyObjC.

The effort for porting this turned out to be minimal, and the maintainer of the project (Ronald Oussoren) has contacted me about merging my changes, which means that its support that is likely to stay around for quite a while. To get it, one need only install Cydia Packager (which contains a bootstrap of the Telesphoreo project), and install the PyObjC package under the Python section (or apt-get install pyobjc).

A Sample Application

In addition to this, however, I have included a sample program called HelloPython that performs the same function (with almost identical code) to my existing HelloJava and HelloScript (JavaScript) programs: use SQLite3 to access your contact information, and display a nice iPhone UITable with the results. Great thanks goes out to Dave Arter for this, who did much of the implementation of this sample application (I being quite busy and not even knowing Python, which luckily was not needed to port PyObjC).

To get this program, and its source code, install the package iPhone/Python from the Python section (or apt-get install iphone-python). This will install all required dependencies (including PyObjC) and place HelloPython.app in /Applications, inside which is the source code (which is an "of course" given that it's Python). The complete source code for this may also be seen online from my Subversion repository.

A Quick Introduction

In order to help users who are new to PyObjC be able to use this bridge effectively, I think it useful to quickly go through a few points of this file. I am not going to attempt to replace the PyObjC manual, but do think that people who are already familiar with Apple's SDK (and who already know Python) should be able to jump into this almost immediately given just a few pointers.

import objc from _uicaboodle import UIApplicationMain from objc import YES, NO, NULL from sqlite3 import dbapi2 as sqlite

To start with, we see the block of import statements. The last one is from Python's included SQLite3 support, but the first three are new. In Objective-C, boolean values are specified using single-byte 0/1 values represented by the constants YES/NO. In order to make certain to use the correct ABI, PyObjC therefore provides YES/NO constants to use in these cases. (Note that I'm actually not certain that it does this for ABI purposes, but if it doesn't then it should.)

The weirdest part, though, is NULL. This is there because Python doesn't really have a null value: it's None is just another object that an object may choose to refer to. Isn't that enough? If you pass None to an Objective-C message, PyObjC will pass NULL. Unfortunately, there is another case: messages that take a pointer to an object. These come up a lot with error handling (where the message will fill in the pointer to point to a description of the problem).

This form of API is mapped to Python byref argument passing by PyObjC... which makes passing None not helpful if you really want to pass a NULL pointer (to disable error handling, which might be useful). Therefore, we get another constant NULL that disables the byref behavior.

Finally there is the line importing UIApplicationMain from _uicaboodle. This is probably temporary, and might get better addressed by the author of PyObjC as he merges in this support. UIApplicationMain, the first function called by an Objective-C iPhone Application, is itself exported as a C API, which means it can't be automatically discovered by PyObjC.

Functions like this would normally be supported, I believe, by a system known as BridgeSupport, but I didn't have enough time to figure out how. (Besides, the equivalent desktop function NSApplicationMain doesn't use BridgeSupport anyway, so maybe it isn't even encouraged.) We can see it used at the very bottom of the file.

UIApplicationMain(["HelloPython"], PYApplication)

This function takes first the set of arguments passed to the program, with the first argument being the name of the project. I've obviously cheated here, so if anyone can tell me how to get the arguments that were passed to the program (and maybe even verify that doing so works out alright), I will happily modify the program. The second argument s a class that derives from UIApplication that will be instantiated and provide the actual functionality of the program.

To get at classes such as UIApplication, we have to have PyObjC parse the Objective-C frameworks. This is done using objc.loadBundle, which takes both the name of the framework and its path. Here I bring in both Celestial (which has the AV* classes for multimedia support) and UIKit.

objc.loadBundle("Celestial", globals(), "/System/Library/Frameworks/Celestial.framework") objc.loadBundle("UIKit", globals(), "/System/Library/Frameworks/UIKit.framework")

After this, you generally can just directly use an Objective-C class by name as if it were a Python class object, calling static methods on it to send messages to its metaclass. As a simple example we see getting the default size of a navigation bar.

navsize = UINavigationBar.defaultSize() navrect = ((0, 0), (inner[1][0], navsize[1]))

This function returns a struct of two elements (a width/height), which we can see on the next line is accessed using array syntax. PyObjC does not attempt to provide access to the names of the elements as this information is usually not provided in the binary frameworks. If you have nested structs (such as a rectangle, which consists of a point and a size) then they are represented as nested arrays.

While this is all well and good for no-argument or even one-argument messages, in Objective-C multiple arguments are provided using an infix keyword notation that Python does not itself support. PyObjC therefore has to translate this functionality, and chooses to convert all the :'s in a raw selector to _'s. Something that used to be written [a does:b to:c] thereby gets converted to a.does_to_(b, c).

col = UITableColumn.alloc().initWithTitle_identifier_width_("Name", "name", 320)

This example also demonstrates another difference: how objects are instantiated. In Objective-C, to allocate an object, you normally send the message alloc to the metaclass object you wish to obtain an instance of. This, however, isn't the only way to get a new object as you could also call allocWithZone, and technically it is only a convention as a message named connectToServer could also serve this function. PyObjC directly maps this mechanism to Python.

The last thing we have to look at is how to provide messages back to Objective-C. This is done quite easily by providing a method with the appropriately mangled name, but there's a catch: in Objective-C the receiver is expected to know how to parse the arguments that it is passed, whereas the sender is allowed to be ignorant. This functionality comes up while connecting to remote proxy objects, or when attempting to reflect a message to determine its arguments.

This causes Python a greater challenge than some other languages as it doesn't use declared argument types. While it is important to Objective-C whether a message takes a double or a pointer, to Python there is no difference. When overriding an existing message PyObjC can just follow the inheritence hierarchy to figure it out, but barring that case the signature needs to be specified somewhere.

In PyObjC, you specify this with a special annotation objc.signature, which takes the Objective-C type signature of the method. This signature is made up of a number of different characters that represent the type. A complete list of these signature elements can be found in Apple's developer documentation.

@objc.signature("i@:@i") def sectionList_rowForSection_(self, list, section):

To exemplify this, this method takes two non-self arguments: an object (list) and an integer (section). It also returns an integer. Now, much in the same way that Python represents the self argument explicitely, in Objective-C the type signature also represents a couple hidden arguments. One of them is self, and the other is the name of the message that is being called in the form of a "selector" (which is really just an intern'd string pointer). These arguments, in that order, come before the other arguments that are defined.

Putting all of that together, we get the signature integer, object, selector, object, integer, or i@:@i. This may seem irritating, and it is: normally this sort of thing might be handled via BridgeSupport, with a list of the standard callbacks that an object might receive and their standard signatures. If someone knows more about BridgeSupport and would like to help with this, their contribution would be quite useful (although now that the maintainer of PyObjC is involved, that might be handled pretty quickly, and all we need is a good list).

Any Questions?

After all of that, I hope everything just works for you, but if you'd like to find other people working on iPhone applications in Python, I encourage you to join the iPhone/Python mailing list, hosted at the Telesphoreo project.

Good luck!

UnTethered Jailbreak iPhone 4 5.1.1 Redsn0w - Video

2012-05-24T09:12:00.003+02:00

UnTethered Jailbreak iPhone 4 5.1.1 Redsn0w - Video A few days ago we showed you a video demonstrating the iOS 5.1.1 untethered jailbreak using Absinthe 2.0 by Xvolks , also Pod2g has said untethered jailbreak of iOS 5.1.1 is just days away from release, Today we have More news about The ability to Jailbreak iPhone 4 on iOS 5.1.1 with Redsn0w Jailbreak.

It is a simple demo by InteVyDis . The module builds a bundle you have to install on the device with the help of redsn0w tool. Finally the device will be jailbroken and you'll get remote CANVAS shell.
Update: InteVyDis has released an untethered jailbreak for A4 devices on iOS 5.1.1 as part of Vulndisco Mobile 1.7. The module is vd_ios_untether_5_1_1.
vulndisco mobile 1.7 is out with untethered 5.1.1

It works by creating a custom bundle you have to install via RedSn0w.
The module builds a bundle you have to install on the device with the help of redsn0w tool. Finally the device will be jailbroken and you’ll get remote CANVAS shell.
I01nc notes that the company is a legit source of exploits. “@legerov runs a company: Intevydis that sell exploit packs for many years. If that JB were fake he would hurt his own business.”
The unfortunate thing is that now two sets of exploits may now be revealed to Apple and some people may pay for the expensive exploit pack despite it being available free in a few days from pod2g.
MuscleNerd tweets “the most troublesome part is that (potentially) close to 2x as many exploits will be burned now with 2 A4 JBs”.

UnTethered Jailbreak iPhone 4 5.1.1 Redsn0w - Video :

Support Jailbreak Greenpoison Absinthe for Iphone 4S / Ipad 2 UnTethered on iOS 5.0 / 5.0.1 On Google

Genuine Untethered jailbreak and Unlock iphone 4/4s ios 5.1 .1 With Safe Apple Team support

2012-05-24T08:44:00.001+02:00

Great news for all iPhone enthusiasts, http://unlockjailbreak.blogspot.com have released the latest iPhone unlock and untethered jailbreak method capable of unlocking the latest iPhone 4/4S ios 5 5.1. It is available to download now at Apple solution Dot Com

appleunlocker have been providing unlock and jailbreak solutions for the iPhone since the release of the iPhone 2G (June 2007) making them the most accomplished iPhone unlocking/jailbrea king services within the industry.

Visit Apple unlocker official web site: Apple Solution Dot Com
Their latest application allows the ability to jailbreak/ unlock iPhone 4/4S the latest iOS 5.1 untethered installed on the iPhone 4S/4/3G, 5.1.

Many new features that are limited on the factory set iPhone are enabled by using the software offered here. Just a few of the features include the use of any network provider, free GPS navigation applications, 1000’s of wallpapers, ringtones and much more.
Visit Official web site Just Click here

appleunlocker state that this unlock solution is the easiest, safest and most reliable iPhone unlock software on the market and after running the software on multiple models of iPhone this statement is not too far from the truth. There have been no faults to report.

The Jailbreak iPhone 4S team state that this unlock solution is the easiest, safest and most reliable iPhone jailbreak/unlock software on the market and after running the software on multiple models of iPhone this statement has proven to be fact.

One major advantage of the software is that the jailbrea king/unlocking process is completely reversible and there will be no evidence that your iPhone has been jailbroken/unlocked should one ever need to return your iPhone to the store for repair.

The iPhone itself is packed with a wide assortment of features and functions, but it is typically only available on expensive price plans and predetermined networks. This has created anger within the jailbreak iPhone community, as it is believed that the customer should have the freedom to choose their own price plan or network provider.

The wonderful feature of the iPhone unlocking software is that upon unlocking the iPhone one will not lose any of the great features and functionality of the iPhone. This provides the iPhone user absolute freedom over network choice, and a fully functioning device.

The Jailbreak/ Unlock iPhone 4S/4/3GS ios 5.1 untethered software comes with a full 30 day money back guarantee, lifetime updates and most important of all, lifetime support. If one should require first class service at an affordable price, there is only one simple choice that has to be made.

bluemaumau.org

Caching Apple's Signature Server

2012-05-24T08:40:00.000+02:00

Click here to skip directly to the instructions. Personally, I find it much less powerful to say "do this" than "do this, here is how it works, and this is why", because the former just causes more confusion and more problems down the road. However, some disagree. Those people can click this link. ;P

Please, for the love of all that is holy, do not e-mail me if you have problems. ;P Instead, go to ModMyi.com, where there is a special forum called 3G[S] Downgrading, created for the purposes of this article.

Seriously: there is no way I could possibly hope to answer even the number of e-mails I'm currently receiving regarding this, and the article isn't even out yet. There is this wonderful scene from Bruce Almighty where Bruce sees his e-mail inbox: that happens to me every day. :(

I have very little respect for Apple at this point: I make no secret of this fact. Apple, as a company, has turned into a corporate hypocrisy, embodying the very ideals that it claims to be rebelling against. "Think Different", as a slogan, has become a cold criticism of their own actions with regards to their product lines.

The Next Hope

Apple is not just a computer company: Apple is a movement. This concept was finally and truly cemented in the public mindset when Apple carved itself a lasting place in the history of marketing with its 1984 superbowl commercial for Macintosh.

Styled after the classic Orwellian dystopia, 1984, this commercial was set in a future where all aspects of individuality had been stamped out by the overlords, constantly vigilant, watching from their television monitors.

This world, as well as everyone in it, was rendered in a blue and gray: some believe we are to see the overlords as IBM, well renowned for their corporate beaurocracy, and soon to be hated for trying to control our very thoughts with their bland machinery.

Others, including the creative director of the commercial, Lee Clow, state that the commercial represents the abstract struggle of "the few against the many": Apple's Macintosh standing as a symbol of "empowerment". [Wikipedia]

The True Enemy

However, as time grew on, Apple's real stance on individual expression and "empowerment" in particular, became clear: they are staunchly against it. Apple's insistence on controlling the experience of their products sounds very similar to the "garden of pure ideology" expoused by the Big Brother in their own commercial.

Today we celebrate the first glorious anniversary of the Information Purification Directives. We have created, for the first time in all history, a garden of pure ideology: where each worker may bloom, secure from the pests of any contradictory... thoughts.

Our Unification of Thoughts is more powerful a weapon than any fleet or army on Earth. We are one people: with one will, one resolve, one cause. Our enemies shall talk themselves to death and we will bury them with their own confusion. We shall prevail!

The Point of Jailbreaking

This is why many of us (upwards of 10% of all iPhone users, in fact) "jailbreak" our devices: we want choice. We believe that Apple has maintained its lead as the best mobile hardware platform provider, and we encourage that innovation by purchasing not only their devices but also numerous applications from their App Store; but, and this is important: we want more.

Sometimes, it is "only" marketing restrictions: there is no fundamental reason why only the 3G[S] can record video (although the quality of the camera on the iPhone 2G and 3G is not very high), or why the iPhone 2G is somehow unable to do MMS.

Applications like Google Latitude or Voice are likewise "rejected" (Apple likes to claim that they didn't reject these applications, they simply "didn't accept" them...) from the App Store because they might "confuse" the user by replacing functionality that exists with better equivalents.

Our need for "more", however, goes deeper: jailbreaking isn't just about applications that Apple "rejected", but is also about taking provided tools and going in a new direction. The most popular packages available in Cydia aren't even "applications", but are "extensions": seamless and pervasive modifications to existing software.

An Exploit a Day...

On desktop computers such markets are implicit: the computer is yours, and you can do whatever you want with it. You can purchase any kind of hardware, download any kind of software, and make any modifications you feel to be fit. However, Apple doesn't want us treating our iPhones like computers, no matter how similar they seem.

This means that those of us who demand to have the freedom to use the device we rightfully own the way we want to use it are in a constant battle with Apple. Each time they release a new product, or even just a software upgrade for an old one, we have to go to work defeating any new protections.

This arms race is what defines the "homebrew" community on most devices: each upgrade to the PlayStation Portable, for example, brings not only new features but also new restrictions, requiring users to find a new "exploit" to defeat the new defense.

What makes the iPhone platform special, however, is PwnageTool from the iPhone Dev Team: the trust chain on these devices has been completely defeated, and only with new hardware can Apple fix the issues to keep us out.

The Signature Server

Of course, new hardware comes every year, and Apple decided to strike hard with the new iPhone 3G[S]. Rather than just throw in new local protections, Apple decided that every restore of the device would be verified as being valid and safe by Apple itself.

To do this, during the restore process, users see "Verifying restore with Apple...", during which time a challenge/response protocol is used between the iPhone and Apple: a "partial digest" of the firmware files being used is sent to a server, which can then decide to sign off on the result... or not.

Not only does this allow Apple to keep custom firmwares from getting loaded onto the device, but it also allows them to recall existing firmwares by keeping people from restoring to them in the future. To do this they simply would refuse to ever sign, for example, iPhoneOS 3.0 again.

However, to make this model secure, one must verify that their system is not subject to a simple "replay attack": where one just stores a copy of Apple's sign off and then returns it at a later point. This is a "beginner's attack", and one that is easily mitigated by any of a number of strategies.

For a Purple Ra1ny Day

Apple's 3G[S] security mechanism, however, fails this test. Rather than even using a simple random number, they use a hardcoded challenge per device. The specific number they have chosen is the device's ECID, or "unique-chip-id", a number that all devices have so far had, although we haven't seen any previous use for it.

This means that, given an ECID, one can ask Apple's signature server to sign any firmware that they currently consider "OK" (which returns a blob that includes the critical SHSH, which is the signature hash) and then store the result forever.

In practice, there is only one critical file that we need signed: the one with the bug. ;P This is the iBSS, which is one of the modes of iBoot. Given that ECID/iBSS signature, one can load the buggy code and then continue with the jailbreak.

This is, in fact, what purplera1n.com was doing: it returned to you a file that contained just the signature hash for the iBSS file, as that is "sufficient". Eventually someone may write a tool to use this file.

Personalized Firmware

What iTunes does with these blobs is to "personalize" the firmware file, integrating the ECID, SHSH, and CERT blocks into it, so that the iPhone can verify the result. It does this in a temporary directory where users can actually just watch and grab the files.

So, many users have gone in and carefully gotten both the iBSS and iBEC files from this personalization mechanism. The iBSS file from this process actually contains no more information than the tiny purplera1nyday file.

However, and this is unfortunate: just because this information is "sufficient to jailbreak", doesn't mean it is convenient. Without someone writing a special jailbreak tool that uses these files as input you are pretty much stuck.

Your iPhone 3G[S] has an ECID SHSH on file.

Instead, what you really want, is to store the entire personalized firmware set required by iTunes to do a restore (or, more realistically: a full set of SHSH blobs). At this point you should be able to use iTunes to do a "normal" restore of the device.

This functionality was offered, very near to the end of the window, by Cydia: one needed only to agree to have the process done, and your ECID was used on Cydia's server to generate and store a full set of SHSH blobs using Apple's signature process.

In doing this, over 50,000 3G[S] devices got their ECID SHSHs "on file", and are now prepared to continue to restore to iPhoneOS 3.0 indefinitely.

A Narrow Window

Unfortunately, due to the timing of the release (it took a while for me to figure out how to do this effectively), many users failed to get their ECID's in by Apple's cutoff. However, while this means these users will not be able to downgrade to (or even stay at) 3.0, an exploit has (supposedly) been found in 3.1.

This means that, at some point in the tangible but unknown future, users will be able to use iPhoneOS 3.1 on their 3G[S] to jailbreak their devices.

To faciliate this, the Cydia "on file" system is going to come back online tonight and start signing ECIDs using the 3.1 firmware, to prepare for the coming release from Apple when users will once again be locked out.

Hopefully, by then, we'll have hundreds of thousands of users fully protected against Apple's "Information Purification Directives".

Bypassing the Overlord

To this end, I have constructed a server that duplicates the functionality exposed by Apple's signature server, except using "on file" results rather than live requests.

All we need, then, is to make iTunes use it. Luckily, most operating systems also have the ability to locally define bypasses on specific hostnames through a file called hosts. Using this, we can redirect requests to Apple's signature server to Cydia.

So, open the file C:\Windows\System32\drivers\etc\hosts (Windows) or /etc/hosts (Mac OS X) and add the following entry to the bottom of the file.

74.208.10.249 gs.apple.com

Now, when iTunes thinks it is talking to Apple, it is talking to Cydia instead. Doing this will allow iTunes to access signatures already stored by Cydia's "on file" feature.

This server will also act as a cache for any SHSH blobs it hasn't seen, acting as an intermediary to Apple's server. This effectively registers your device with the "on file" mechanism, which means you can now enjoy the protections of being able to downgrade your firmware in the future even if you aren't jailbroken.

This point should be stressed: even if you don't jailbreak, and even if you never intend to jailbreak, you should consider using the new "on file" service.

Let's say that Apple releases an OS upgrade in the future, you take it, and they break something important. Maybe they break your e-mail account, or your todo list. Your business is now crippled.

If only you could downgrade, right? Alas, Apple won't let you anymore. That's where the new signature cache server comes in: by doing your restores through this server you secure your ability to not accept upgrades from Apple if the need is dire.

Performing the Restore

Now, one would have hoped that the process would be as easy as "restore using the 3.0 IPSW". If only we were that lucky. The first problem is that a downgrade from 3.1 to 3.0 must be initiated in DFU mode.

So, we begin: hold down the lock and menu buttons (some call these the power and home buttons) for 10 seconds, letting go of the lock button but continuing to hold menu until iTunes recognizes the device with the message: "iTunes has detected an iPhone in recovery mode. You must restore this iPhone before it can be used with iTunes.".

Note that, at this point, your iPhone's screen should be entirely black. Many people confuse "DFU" with "recovery" (and in fact, iTunes itself glosses over this), but they are quite different. If you see anything on your screen, such as the iTunes logo and a sync cable, or a cartoon of Steve Jobs swearing in Cyrillic, you are in recovery mode and need to try again. One can find videos online that may help.

At this point, you should do a "normal" restore to the 3.0 software. When doing this, remember to hold down the option key (on Mac OS X) or the shift key (Windows) while clicking the Restore button in iTunes. Select the firmware (which is probably named iPhone2,1_3.0_7A341_Restore.ipsw), and things should be on their way.

Please note that I do not have signatures for 3.0.1, only for 3.0. For some very small number of users I also have a signature for 3.0.1, but I ran out of time hitting the Wednesday deadline getting the code for this working and generalized.

If you would like to try restoring to 3.0.1 with my server, therefore, to see if you have 3.0.1 keys on file you can try, but it may fail late in the process with a very weird error. All users "on file", however, have 3.0 ready to go.

Upcoming 3.1 Exploit

If you encouter "unknown error (3002)", you probably do not have your ECID SHSH's for 3.0 "on file" with Cydia. Unfortunately, as Apple is no longer allowing users to sign the 3.0 firmware, it is no longer possible to register your device with Cydia.

Luckily, it has been reported that iPhoneOS 3.1 is vulnerable to another exploit. This means that, once a jailbreak is released for 3.1, users will be able to prepare themselves for future jailbreaks even if they missed the first round of signature storage (which I unfortunately was only able to start very late in the 3.0 game).

Once you even attempt to use this service (or if you tell Cydia to "make your life easier") you will be signed up for the signature tracker, and Cydia HQ will do its best to manage your ability to restore.

And again, if you have any issues with this process, please please please do not e-mail me. Instead, go to ModMyi.com, where there is a special forum called 3G[S] Downgrading, created for the purposes of this article.

NAND Format Invalid

OK, if you were already using 3.0 then this process should "just work". However, if you had already upgraded to 3.1 you will encounted a nasty error: "The iPhone "iPhone" could not be restored. An unknown error occured (1015).". This is expected behavior.

For people who are curious, what has happened is that a section of the NAND storage has been slightly reorganized in 3.1, and the 3.0 iBoot can no longer parse it. If we pulled out iRecovery and checked the iBoot logs over USB we'd see the following messages (the typos are Apple's).

[WMR:ERR] NAND format invalid (mismatch, corrupt, read error or blank NAND device) [WMR:ERR] boolSignatureFound false boolProductionFormatVerified true nSig 0x0 ****************************************************************************** ****************************************************************************** AND: NAND initialisaton failed due to format mismatch or uninitialised NAND. AND: Please reboot with reformatting enabled. ****************************************************************************** ****************************************************************************** NAND FTL failed initialisation

The first time this happened to me I actually spent a while with MuscleNerd working out how to do what it asked: "reboot with reformatting enabled". That was a severe waste of time: after you fix this, it still won't boot, and you will need to go through a second restore to finish the process.

However, it turns out a second restore also formats the NAND correctly by itself. So, without bothering to do anything else to the device (leaving it in the recovery mode it is now in: DFU is no longer required), just start the restore over again in the same manner as before, once again selecting the 3.0 firmware.

Stuck in Restore

Unfortunately, this second restore is also going to fail (*sigh*), and irritatingly enough it is going to cause the exact same error message: "The iPhone "iPhone" could not be restored. An unknown error occured (1015).". This is still expected behavior.

For those who are again curious, what has happened is that when the device turns on it has to decide what it is going to do: wait for instructions over USB, or continue into the boot process. This is determined by an NVRAM variable named auto-boot, which is currently set to "false".

Normally this is set at the end of the restore process, but technically we were unable to finish the restore: it is my understanding that this is because upgrading to 3.1 installed the 3.1 baseband (which is currently not unlockable, btw), and the baseband upgrade in the 3.0 release then fails, stopping the restore.

However, that seems to be the last and least important part of the restore, so we technically won: we are never, though, going to be able to restore back to 3.0 without hitting this 1015 again, though.

Jailbreak with redsn0w or purplera1n

You have two. The first is to use iRecovery to manually set auto-boot to "true", and the second is to just go ahead and jailbreak your device.

We will go ahead and do option #2 (jailbreak), as even just getting iRecovery working on your computer is something that I don't look forward to trying to describe. ;P (In fact, it still isn't working on my Windows computer.)

At this point, you can just run your jailbreak tool of choice, which should jailbreak the device and boot it into the normal operating system. Congratualations, you just overthrew your orwellian overlord, and have taken back control of your device.

At least today, we will prevail!

iPhone Theming on WinterBoard

2012-05-24T08:38:00.001+02:00

Pretty much the most requested application for iPhoneOS 2.x has been SummerBoard. Unfortunately, RiPDev is busy writing a new Installer for 2.x (the branding for which they bought off of NullRiver, whom I hope made a pretty penny on that transaction), which means no SummerBoard, not for us. (Also, RiPDev seems like they are going to be selling a similar product via Installer, so its unlikely that they are going to want the competition from anything free.)

This, unfortunately, leaves the rest of us in a lurch. It gives me a warm feeling inside when I see the wallpapers I've taken show up behind SpringBoard, and I haven't been able to do that since I upgraded to the iPhone 3G. Seeing as I just finished releasing a new version of Cydia (which has a number of features people have been looking for in it), I figured I'd have time to solve this: enter WinterBoard.

Now, when I do things, I like to seriously do things. Here, that means not just creating a "temporary solution": WinterBoard, to me, needs to be everything SummerBoard was and wasn't. I mean, let's face it: SummerBoard was nice, but it just didn't cut it after a while and NullRiver pretty much stopped updating it after only a few months of work. Also, as it wasn't open source, no one else could continue the project.

For those who don't know that much about SummerBoard the idea is that you should be able to theme SpringBoard: change the icons of applications, use a custom wallpaper (well, a wallpaper at all), and even modify the statusbar and dock. This is pretty much all SummerBoard did, though. Even this had a bunch of issues involving localization (themes often do not work very well in other languages as icons are themed by the displayed name of the program. Besides, many more things to theme started cropping up in the community: sliders, batteries, etc..

What SummerBoard really had going for it, though, was how it worked: it hooks into SpringBoard and overrides functionality down into its core. This lets it swap out icons at runtime without having to actually muck around on disk and swap out the .png files. This, in turn, makes it incredibly safe: you don't have to worry that the guy packaging the theme managed to think through backups correctly (or that the people who wrote the package mangager didn't think through package conflicts... I'm looking at you Installer...): the theme sits entirely self contained in its own folder.

With WinterBoard, I therefore wanted to bring as much power as I could for theming the device down in one simple backend tool as I possibly could, and I think I've drastically succeeded. Pretty much every form of graphic-file related theme I've so far seen (and a few other varieties we may think of) is supported by WinterBoard, all using the SummerBoard model of "the safe other folder". WinterBoard truly is the modern replacement for SummerBoard. It's also open source.

What is a Theme?

A theme is a folder that sits in /Library/Themes (or $HOME/Library/SummerBoard/Themes, which is supported for backwards compatibility with SummerBoard, but storing themes there is wrong on a few different levels). These folders end in ".theme" and are otherwise the name of the theme; for example: "Transparent Icon Labels.theme". Inside of this folder you have a set of folders, a number of .png files, and optionally an Info.plist that contains some extended information.

One thing I wished I had done, btw, is spent the extra hour before going to bed thinking through having it be <name>.theme instead of just <name>, but by the time I woke up again there were already hundreds of themes posted and it was too late :P. I have gone ahead and made this change, as documented in the previous paragraph, but themes without this extension will still work.

One thing that is a drastic modification from SummerBoard is that you can have multiple themes installed at once. This is partly due to how powerful WinterBoard is: there are so many things you can theme that people really want to be able to mix and match them. This means you might have a battery theme installed from one source, a set of icons from another, and might override the wallpaper with your user settings.

The interface for this is a priority ordered list of themes that you can drag around (with the same interface as the MobilePhone favorites screen, although the dragging is a little more finicky, a bug I currently believe to be a fault in the control Apple made public for doing that), each of which can either be checked or unchecked, which indicates whether it is turned on.

Legacy Theme Support

As most of the existing themes out there are designed for SummerBoard, it is definitely important to support this "de-facto standard" of theme organization. The way a SummerBoard theme worked is by having a few components, all of which are optional:

Dock.png - replacement graphic for the bottom dock (which may be transparent)
Icons/ - a folder of files such as Calendar.png which are used as application icons
StatusBar.png - graphic to display as the status bar at the top, when its "dark"
Wallpaper.png - an image to display behind all of the icons on SpringBoard

This is really simple and is supported fully by WinterBoard. The one thing that should be pointed out: the Icons/ folder was horrendously non-internationalized. As it uses the displayed name of the program (such as "Calendar"), if you are using a different language icons simply don't theme. The way some of the larger themes got around this by seriously providing icons (often duplicate files as Installer didn't support symlinks very well at all) for every possible name of a program in the many languages the phone supported.

Personally, I think that's nuts, and it's been confusing users of WinterBoard over the last few days. WinterBoard therefore looks up the english variation of the name and attempts that if it can't find an icon specifically for the current language. Also, if you have your device switched to use Celsius for temperatures the Weather icon is also different (and is even loaded as a special case): WinterBoard corrects this oversight as well, mapping the Weather icon in as would be expected.

One final note on icon themes: App Store applications often are "composed" by SpringBoard from a flat, square graphic by wrapping them in a button style with a shadow. This effect can destroy many theme sets, to the point where people have called this wrapping "raping". WinterBoard therefore turns this behavior off for icons that are themed. If, however, your theme is designed with this effect in mind you can set the key ComposeStoreIcons to true in your Info.plist file. (Please note that this behavior is currently a little weird in how its supported with multiple themes. This will be fixed.)

Miscellaneous Features

Video Wallpaper - Apparently some people have become addicted to video wallpaper, a feature that has been around on and off in various forms from random theme packages. In order to bring this into the WinterBoard fold you can specify a Wallpaper.mp4 file that will be placed at the very bottom of the wallpaper stack. Obviously, your video will need to be the right dimensions for the device. (Please note that right now it skips a little to a black screen as it loops.)
Sounds - A bunch of system sounds are stored in /System/Library/Audio/UISounds/. If you create a folder in your theme called UISounds/ you will be able to theme these (provided you also can provide .caf files). Support for other formats may be forthcoming.
Web Clips - If you want to theme Web Clips you can do so using Icons/ using the name of the clip (example: Google.png). This works very similarly to how Icons/ themes other icons by name.
Lock Background - You can also theme the background of the lock screen using LockBackground.png.
SMS Background - Behind the SMS windows you can put an image using SMSBackground.png.
Debug Output - If you activate syslogd you can set Debug to true in your com.saurik.WinterBoard.plist preferences file (yes, this is rather esoteric) in order to get a dump of various hooks. This can help figure out filenames you might want to theme.
Font Replacement - WinterBoard can globally rename one font into another. To do this, by way of example: you can place a key "FontName-Helvetica" with the value "Courier New" to use the latter font anywhere someone would have used the former.
Per-Page Wallpapers - You can have a different wallpaper per page of SpringBoard icons by having a file named Page#.png, such as Page0.png. This graphic will be displayed above widgets and wallpapers, but below the icons. Unfortunately, due to a bug that I'm working on fixing, it will also be displayed above the dock when your icons are wiggling. Please do not freak out when this happens ;P.
Icon Alpha - Setting the IconAlpha key of your Info.plist to some decimal number between 0 and 1 will affect the transparency of the icons.

Theming Bundle Resources

The entire idea, though, of theming things by their displayed named is wrong, even if not for localization reasons: with App Store multiple programs are allowed to have the same name. What they should have that's unique, though is their "bundle identifier". Pretty much everything we think about on Apple computers is stored in the form of a "bundle" (including our themes in short order, albeit usually with extensions like .theme... *sigh*). These then have names which are supposed to be unique (although watch them not end up being all the time in practice).

In general, the way you figure out the bundle identifier of a bundle is to open its Info.plist file and read the key for CFBundleIdentifier. This can be done using the Property List Editor tool on a Mac or by using either Apple's (desktop) or Erica's (on-device) plutil to convert the file to XML. Now, I realize this can be difficult, so please bear with me for a moment and I'll show you an alternative.

With this information you can now use the bundle identifier as the name of a file in Icons/ (such as Icons/com.apple.mobilemail.png). The fun doesn't stop there, though. More often than not (although there are some irritating exceptions) most of the graphics files on disk are loaded using a filename offset from a named bundle (in which case they are called "resources". An example of this are the pictures used for battery status on the lock screen. These files are stored in /System/Library/CoreServices/SpringBoard.app: a bundle that represents the SpringBoard program.

To theme these we then simply need to get their name (such as BatteryBG_1.png) and then place a file in Bundles/com.apple.springboard (com.apple.springboard is the bundle identifier of com.apple.springboard). As promised, there's another option if getting that bundle identifier is getting irritating: you can also use Folders/SpringBoard.app/BatteryBG_1.png to theme bundle resources by folder name.

This mechanism should provide a very generic mechanism for theming files from random programs even, including App Store applications. (This is possible to do in WinterBoard, btw, as WinterBoard doesn't just hook SummerBoard: its resident in every program that's running to provide global themes.) It is so generic that it even replaces StatusBar.png and Dock.png: we can theme FSO_BG.png and SBDockBG.png out of SpringBoard's bundle.

Oh, one more thing: as I love genericity I also use this system to replace the Icons/ folder entirely (which is kind of a weird concept anyway). The icons for applications are stored as icon.png inside the bundle and are accessed as such, so you can mostly theme using Bundles/com.apple.mobilemail/icon.png (for example). I think there may still be some issues with how this works, though, so I might stick to Icons/ for a bit longer until I iron out all the kinks (specifically having to do with multi-app bundles like MobileSlideShow).

Cached .artwork Themes

Finally, the most complex example of image-based themes I've so far seen has to do with .artwork files. These files exist as loading lots of small .png files from disk can be irritatingly time consuming, so instead they are loaded as a block and stored (I believe) in a shared memory cache. As these tiny graphics are often used to build all aspects of the interface these represent the ultima thule of iPhone theming.

Messing with them, though, is currently really hard: you have to use special tools to unpack the files and all you get out of them are a bunch of numerically-named png files (.artwork files don't have filenames in them). You then have to carefully make new images of the same size and rebuild the complete .artwork file, which then has to be installed on the phone with a rickety package that attempts to backup and restore the original. Yeek!

After I heard about this, I set out to fix this with WinterBoard: I want theming to be a fun, safe experience that can be taken up by anybody without special tools. To do this I first analyzed how .artwork files worked, and lo and behold there actually are filenames that go with all of those png files people were compressing (already this makes the task a million times easier.

At first I implemented this by providing a folder in your theme called UIImages/ in which you can store replacements for these files. As an example, you might have UIImages/UISearchFieldIcon.png (which happens to be the name of the little magnifying glass used at the left of text fields to indicate you can search with them).

However, I have since figured out that these .artwork files are actually designed to be a cache of files that are otherwise part of a bundle and should really be stored in Folders/UIKit.framework/. The UIImages/ path will be maintained for backwards compatibility. This new understanding, combined with some code updates, means that we can now theme any .artwork file (such as those used for MobilePhone.app).

I'm writing this documentation a little bit before the WinterBoard release related to it, so for right now you need to keep using UIImages/. The support for MobilePhone.app is in there, but hooking back to UIKit.framework/ is not.

Of course, you need to know what you can put there to make this feature useful. For a list of filenames you can theme you can grab this text file, but just having the names isn't really helpful. While I currently feel uncomfortable distributing a copy of these images from Apple as a file on my website, I have released a tool as part of WinterBoard that will let you quickly extract them for yourself called, yep, UIImages. Here's how you use it:

$ mkdir /tmp/images $ cd /tmp/images $ /Applications/WinterBoard.app/UIImages $ ls UISearchFieldIcon.png -la -rw-r--r-- 1 root wheel 468 Aug 4 03:13 UISearchFieldIcon.png

One final variant are things that are loaded from a "mapped image domain". Common examples of this are the TextInput localization bundles. The way you specify these is using Domains/TextInput_ru/std-kb-ru.png.

Theming with HTML

So, while staring at the desktop, I realized "wait, why don't I make that a website? then you could do all kinds of neat things with it!". This dream has been made a reality with the latest version of WinterBoard. There is a new file you can add called Wallpaper.html which puts a UIWebDocumentView behind SpringBoard. (You can use LockBackground.html to do the same thing on the lock screen.)

This view has a transparent background and has been told not to clear what's behind it, so you can set its background-color: CSS to transparent if you want to see through to Wallpaper.png (although you can also use standard HTML to handle the backgrounds now rather than resorting to that specific case).

The example theme, "Saurik", uses this to do a cross-fade background between two images (as I really couldn't decide which one I liked better ;P). Now, for those who have tried to do such effects before with MobileSafari and felt it was way too slow (as the JavaScript engine is miserable and the way it renders is equally bad) you should seriously check it out.

The way I did this (and this is just a property of my theme, you can do anything you want obviously) is to use the WebKit-specific CSS properties Apple provided us with for doing transforms and animations. These work beutifully and are super fast. For more documentation on these, you should go to Apple's iPhone Reference Library and get the two guides they have for download.

If what you really want is to install "widgets" (things that sit on the wallpaper and provide interesting HTML functionality) then you should use Widget.html: these will get layered on top of all other wallpaper layers (in priority order) and not conflict against the wallpaper in other themes.

Theming .strings Localization Files

When a program needs to support multiple languages, what it does is it constructs multiple folders in its bundle of the form <language>.lproj. Inside of these folders it has .strings files, which are serialized property lists (which, in turn, can be in one of a number of different formats). These .strings files are called "tables" and map from "keys" to localized strings.

As an example, SpringBoard.app has a folder English.lproj, which contains a file SpringBoard.strings, which maps the key "AWAY_LOCK_LABEL" to the value "slide to unlock". This string is what is displayed on the main lock screen under the slider.

This file is stored in the binary version of the property list format, but you can convert it by first installing Erica's Utilities from Cydia and then running plutil -c xml1 on the file (I'd recommend doing this to a copy so you aren't changing your original).

If you'd like to change this text you can mirror that same structure in your theme under Folders/SpringBoard.app/. Inside your SpringBoard.strings you will want to map just that one string to a different value. The simplest format you can use is the string table format, which looks like this:

"AWAY_LOCK_LABEL" = "slide to saurik";

A quick note on the naming of a language: it used to be that, if you wanted English, you used English.lproj. This naming scheme was used for a few more languages until it became obvious that it didn't scale, at which point the localization system switched to using ISO country codes. The software on the iPhone, though, continues to use the older names for its .lproj folders.

However, I actually haven't figured out yet how to get these old names, so I don't support them. If you want to theme something in English you will need to use en.lproj, not English.lproj, even if the original folder on disk was using the older name.

SpringBoard Text Styles

For a while a really common request was that WinterBoard A) let you "fix" the color of the icon labels to SummerBoard's white and B) allow you to make them transparent. The former is supported by modifying Info.plist which allows for many CSS styles to be applied to the labels. This takes the form of two keys: DockedIconLabelStyle and UndockedIconLabelStyle. An example of a reasonable value is "color: blue; font-family: monospace".

The story on this is a little more complicated, though, and is worth mentioning: the default color for docked icon labels is white, but SpringBoard makes all the other icons get gray text. This behavior was apparently changed by SummerBoard to make the text more consistently viewable over random wallpapers. Specifically, all text is rendered white.

To make WinterBoard correctly support these old themes, it does something similar. Specifically, if it detects that no themes are specifically setting any styles (so there are no DockedIconLabelStyle or UndockedIconLabelStyle values in play) it forces SpringBoard to render all icon labels as if they were on the dock. To override specifically this behavior (which I doubt there is any good reason to do rather than just applying a specific style) you can set the key UndockedIconLabels to true.

Similarly, you can set TimeStyle to change the style of text used to render the clock on the status bar and OperatorNameStyle to change any text-based (not image based) carrier names (such as those used by MakeItMine). Another new addition is CalendarIconDateStyle and CalendarIconDayStyle, which modify the number and day of the week that are drawn on the calendar icon, respectively.

Finally we have BadgeStyle, which you can use to change the rendering of the little badge icons that appear on icons (like for new mail).

More to Come!

This is actually not even all WinterBoard does currently, but certainly isn't all WinterBoard will be able to do given another few days of work. For continued updates on new WinterBoard functionality keep checking out this page: I'm going to be continue to update this page as more features are designed!

Top Cydia Tweaks

2012-05-23T11:16:00.002+02:00

Welcome to iJailbreak’s Top Cydia Tweaks section. In this section you will find the top Cydia tweaks for your iPhone, iPod Touch and iPad. Scroll through the list, click on the Cydia tweak that intrigues you, and discover how it can make your experience easier when using your iPhone, iPod Touch or iPad. Note #1: We will be updating this page with the latest top Cydia tweaks when new articles are published, so make sure you come back soon!

Top 10 Cydia Tweaks For Newly Jailbroken iPhone 4S
Tweak #1: IntelliScreenX Tweak #2: SBSettings Tweak #3: Activator Tweak #4: VoiceUtils Tweak #5: InfiniDock or InfiniFolders or InfiniBoard Tweak #6: BiteSMS Tweak #7: Springtomize 2 Tweak #8: GridTab for Safari or Tab+ Tweak #9: iFile Tweak #10: Twitkafly

Top 15 Cydia Tweaks For Newly Jailbroken iPad 2

Tweak #1: SBSettings Tweak #2: Activator Tweak #3: InfiniDock or InfiniFolders or InfiniBoard Tweak #4: RetinaPad or FullForce Tweak #5: WeatherIcon or LiveClock Tweak #6: Springtomize 2 Tweak #7: Gridlock Tweak #8: Barrel Tweak #9: SpringBoard Invaders or SpringBlock Breaker Tweak #10: TwikaFly Tweak #11: SplitMail for iPad Tweak #12: ProTube HD Tweak #13: NoLockScreen Tweak #14: iFile Tweak #15: Fullscreen For iPad

Top 7 Fun Cydia Tweaks For iPhone, iPod Touch, iPad

Tweak #1: Barrel Tweak #2: Graviboard Tweak #3: Springboard Invaders | SpringBlock Breaker Tweak #4: 3DBoard | DeepEnd Tweak #5: Dreamboard Tweak #6: RecognizeMe Tweak #7: AndroidLock XT

Top 7 Essential Cydia Tweaks For iPad (1G + 2G)

Tweak #1: The “Infini” Lineup Infinidock | Infinifolders | Infiniboard Tweak #2: SBSettings Tweak #3: The Fullscreen Duo FullForce | RetinaPad Tweak #4: Gridlock Tweak #5: Springtomize Tweak #6: LockInfo Tweak #7: The Auto Wifi Connecting Duo

Top 5 Networking and Browsing Cydia Tweaks

Tweak #1: SpotURL Tweak #2: WiFiFoFum Tweak #3: 3G Unrestrictor Tweak #4: Safari Download Manager Tweak #5: WhatIP

Top 5 FREE Cydia Tweaks

Tweak #1: Remove Background Tweak #2: CyDelete Tweak #3: BytaFont Tweak #4: Running Indicator Tweak #5: DreamBoard

Top 5 Messaging Cydia Tweaks

Tweak #1: QuickReply For SMS Tweak #2: Mail Enhancer [2.0+] Tweak #3: ManualCorrect Pro Tweak #4: TwitkaFly Tweak #5: I’m Busy SMS

Top 5 Security and Efficiency Cydia Tweaks

Tweak #1: Homescreen Settings Tweak #2: Switcher Rotator Tweak #3: Direct Closer Pro Tweak #4: NewContact Tweak #5: iProtect

Top 10 Cydia Tweaks For April, 2011

Tweak #1: BiteSMS Tweak #2: LiveClock Tweak #3: WeatherIcon Tweak #4: ScrollingBoard Tweak #5: Icon Renamer Tweak #6: MultIcon Mover Tweak #7: Springtomize Tweak #8: SBSettings Tweak #9: CameraButtons Tweak #10: StayOpened The Top 15 Cydia Tweaks For Your Newly Jailbroken iPad 2 On iOS 5.0.1 The Top 10 Cydia Tweaks For Your Newly Jailbroken iPhone 4S Running iOS 5.0 Or iOS 5.0.1

5.1.x untethered jailbreak FAQ

2012-05-23T08:08:00.001+02:00

I receive lots of questions either by email or twitter about the 5.1.x untethered jailbreak.

Here are some answers :

The poll about releasing now or waiting for 6.0 ended with a 64% / 33% to release ASAP. Where is the link ? ETA ? How much % done ? etc.

As I said earlier in twitter, there's still a lot to do to have a user friendly and well tested tool to install the jailbreak on end users devices. Expect a release in a couple of weeks.
Will it be compatible with my <any random iOS device> ?

It will be compatible with any device running iOS 5.1.1 except iPod 3G, iPhone 3Gs and ATV3 (right now, may change in a near future, nobody knows).
Why is it so slow to release now that the iPad 3,1 has been demoed ?

There are 16 different devices out there to work on and to test. It takes time.
May I be a beta tester ?

No, sorry. Only really trusted people (that can be counted on one hand) could have access to the jailbreak. I don't want any leak to happen.
What if I offer you 1,000,000$ ?

That doesn't change a thing.

Be patient, it's gonna happen.

See you my friends.

~pod2g

IDC script to help reverse iOS 5 binaries with IDA < 6.2

2012-05-23T08:07:00.001+02:00

Apple is not standing still and in iOS 5 the default compiler is LLVM instead of GCC. It produces somewhat different code and IDA < 6.2 fail to resolve references which are now relative to PC.

I wrote a little IDC script to resolve those refs (I don't know if another solution exists...). Feel free to use it and modify it to your needs.

It's on github.

Here is an example of code dissasembled with IDA :

__text:00001000 MOV R4, 0x12344
__text:00001008 ADD R4, PC

After executing this IDC script :

__text:00001000 MOV R4, 0x12344
__text:00001008 ADD R4, PC ; off_13350

(if the address is named, the name will appear instead of off_xxx)

The xref is also added so that when you type X on address 0x13350 you'll see where it is used.

Hope it could help.

~pod2g

Why jailbreak ?

2012-05-23T05:19:00.000+02:00

There are multiple reasons to jailbreak, including :

changing the iOS experience with powerful tweaks that can't ever exist on the AppStore : SBSettings, WinterBoard, IntelliScreenX, LockInfo, and lot of others...
playing retro games on console and arcade emulators.
having access to a unix shell in you pocket, and all the open source software that can run on a unix OS.

The jailbreak is not meant for (and we are totally against it) :

pirating AppStore applications

Also please don't pirate Cydia tweaks, there are people working hard on these, and the price is usually low. There's no reason to do that.

Some facts about the 5.1.1 untethered jailbreak

2012-05-23T05:18:00.001+02:00

@MuscleNerd wrote a quick sheet about the upcoming tools (link).

I won't rephrase him, so here are the contents of the file at the time of writing :

* All info below is tentative and subject to last minute refinements
* @pod2g's 5.1.1 jailbreak+untether is working out great. All devices are covered except for AppleTV3,1, which currently has no path for jailbreaking.
- the initial 5.1.1 plan used a kernel exploit from @westbaer which unfortunately precluded use in iPod3,1 and iPhone2,1
- @planetbeing stepped up and provided a kernel exploit that covers both of those. Those two JBers are the bomb!
* The 5.1.1 A5 JB is very similar to the A5 5.0.1 JB. @pimskeks has done a tremendous job supporting both 5.0.1 and 5.1.1 in absinthe
* Similar to 5.0.1, there will also be a 5.1.1 CLI "cinject" binary and redsn0w version of the 5.1.1 JB+untether. Absinthe, cinject, and redsn0w will all provide the same JB in different fashions.
- timing is indeterminate. Plans are for this week, but a number of factors can influence that.
* For those wishing to donate, we've set up a new 5.1.1 paypal URL: paypal
* Please don't pirate AppStore apps (seriously, please do not).

~pod2g

List of tested devices for the upcoming 5.1.1 jailbreak

2012-05-23T05:17:00.001+02:00

Here is the list of devices that are known to work for sure :

iPhone 3Gs
iPhone 4
iPhone 4 CDMA
iPhone 4S
iPad 1
iPad 2 Wifi
iPad 2 GSM
iPad 2 CDMA
iPad 3 Wifi
iPad 3 CDMA
iPod 3G
iPod 4G

Here is the list of devices that won't be supported :

AppleTV 3

Remains to test (but that should work) :

iPad 2 Wifi, R2
iPad 3 Global
AppleTV 2

[updated May 20th 2012, 11:00 GMT]