Downgrade iOS 6 To 5.1.1 On A4 iOS Devices Using Redsn0w

Downgrade iOS 6 To 5.1.1 On A4 iOS Devices Using Redsn0w

Apple is pretty adamant that once a user opts to upgrade, they don’t want them to be able to roll-back the software on their device to a previous version of iOS. In a lot of circumstances, this wouldn’t be an issue, but there are a number of legitimate reasons for users wanting to downgrade to an older version, in this case, from iOS 6 to iOS 5.1.1. Potential reasons for downgrading firmware could range from wanting the iPhone or iPod touch on a version of iOS that currently has an untethered jailbreak* available or could just be because updating to iOS 6 has brought with it some unexpected battery drain or caused other problems. Thankfully, it is entirely possible for owners of specific devices to downgrade with Redsn0w, and we have covered the complete process below.
Apple is pretty adamant that once a user opts to upgrade, they don’t want them to be able to roll-back the software on their device to a previous version of iOS. In a lot of circumstances, this wouldn’t be an issue, but there are a number of legitimate reasons for users wanting to downgrade to an older version, in this case, from iOS 6 to iOS 5.1.1.
Potential reasons for downgrading firmware could range from wanting the iPhone or iPod touch on a version of iOS that currently has an untethered jailbreak* available or could just be because updating to iOS 6 has brought with it some unexpected battery drain or caused other problems. Thankfully, it is entirely possible for owners of specific devices to downgrade with Redsn0w, and we have covered the complete process below.
There a few little things to note and take into account: This downgrade process only applies to iOS devices that are bundled with Apple’s A4 SoC or below. This includes iPhone 4, iPhone 3GS and iPod touch 4G. Later generation devices such as the iPhone 4S or iPad 3 are not susceptible to the limera1n exploit. The downgrade process relies on the SHSH and APTickets being saved for the relevant firmware version that the user is attempting to downgrade to. For those that may not know, the APTicket is something that Apple introduced in iOS 5 as part of the restore process with iTunes and their activation servers. So yes, you need to have SHSH blobs for iOS 5.1.1 firmware saved for the device you want to downgrade. If you don’t already have SHSH blobs saved for iOS 5.1.1, you are out of luck for now as Apple has stopped signing this firmware. Owners of an iPhone that requires a software unlock by using Ultrasn0w must first create a custom built firmware that doesn’t contain the upgraded baseband. The custom created firmware will be the one to which Redsn0w is pointed to in step 5 below.
Step 1: Before going through a downgrade or jailbreak process, it is always a good idea to backup the device in question. Depending on your preferred method, use either iTunes or iCloud to save all relevant files and data from the device.
 Step 2: Download Redsn0w 0.9.14b2 version of the iPhone Dev Team’s Redsn0w tool that is relevant to the operating system of your computer (Windows/Mac). You will also need to download iOS 5.1.1 firmware.
Step 3: Connect the device to your computer using the supplied USB cable. Extract the contents of the downloaded Redsn0w file from step 2 and run the application. Enter your device into DFU mode.
Step 4: From the main Redsn0w interface; select the Extras then select SHSH Blobs from the middle of the available buttons. http://cdn.redmondpie.com/wp-content/uploads/2012/09/Redsnow_Extras_screen.pngStep 2: Download Redsn0w 0.9.14b2 version of the iPhone Dev Team’s Redsn0w tool that is relevant to the operating system of your computer (Windows/Mac). You will also need to download iOS 5.1.1 firmware.

Step 5: The next stage of the process is to select the Stitch option. Redsn0w will now be split into two sections, one dedicated to the IPSW that the user is attempting to downgrade to and the other for the SHSH blobs for the firmware. Click on IPSW and select the relevant firmware file. If relying on a software unlock then this firmware file will be the custom file that was created at an earlier time using Redsn0w, as mentioned in the notes above.

Step 6: If the SHSH blobs for the firmware are saved locally then select Local and point Redsn0w to the place where they are saved. If the blobs are saved within Cydia, then place the device into DFU mode and click on the Cydia option.

Step 7: Redsn0w will create a new IPSW file that has the relevant and correct permissions stitched into it. Users now need to apply the Pwned DFU state to their device by selecting Extras and then Pwned DFU from the Redsn0w main interface.
Step 8: As part of the process, the restore is verified with Apple so that it can be returned as genuine. For this to happen, some additional info needs to be added to the Hosts file stored on the computer. Windows users need to navigate to Windows > System 32 > drivers > etc and open up the Hosts file. Mac OS X users will simply need to open the etc folder.


Step 9: Locate the Hosts file in the aforementioned directory and open it up using your favorite text editor on your computer. At the very bottom of the file add the following text: 74.208.105.171 gs.apple.com. Save the file to its original location. 

Step 10: The final step in the process is to apply the newly stitched firmware to the A4 device through the restore process. Open up the iTunes application on the computer, select the connected device from the left-hand side and invoke a manual restore by pressing left Alt + Restore (OS X) or left Shift + Restore (Windows). When prompted, select the IPSW that Redsn0w has saved and allow the restore process to complete within iTunes.
iTunes may throw an error during restore. This is normal. The firmware should be restored on the device. To exit your device from Recovery mode, start Redsn0w again and navigate to: Extras->Recovery fix to exit your device from Recovery.

World’s First 24kt Gold-Plated iPhone 5 Now Available [IMAGES]

World’s First 24kt Gold-Plated iPhone 5 Now Available [IMAGES]

 

Critics often berate Apple for retailing its smartphones, tablets and computers, at higher price brackets than some would estimate their worth to be, and although it’s a topic of fierce debate, there’s little denying that your average Cupertino product costs a considerable amount more than a similar alternative created by a rivaling company. The new iPhone has sold in excess of five million units hitherto, and the most recent purchase will have left many iPhone 5 owners short of a few dollars, but had they waited for London-based Gold and Co.’s special gold plated edition of the iPhone 5, they may have ended up parting with even more of their hard-earned cash. The company is renowned for adding sheets of gold plating on some of the most sought-after gadgets on the market, and the iPhone 5 – which released on Friday – is certainly the most-wanted device on the market at this point in time. As you can see from the images, the already aesthetically-pleasing device looks stunning laden in solid 24k gold, and although we ourselves don’t have that kind of cash to splash on gold-plating, we’d have to prefer the black model, based on the images. The White & Silver model seemed to be your favorite based on the poll we threw up on Facebook over the weekend, but alongside the gold plating, the darker of the two iPhone 5 configurations certainly oozes the most sophistication. G&Cip51


Prices have yet to be revealed, although having contacted the company personally, I was advised the iPhone 5 would cost $4600 for the gold, with the Rose gold weighing in at around $5000. Considering a 64GB iPhone 4S gold plated by the same company will set you back around $4,300, it seems the predictions aren’t too far off what they’ll retail for, but nevertheless, you’ll really have to push your usual smartphone budget out should you wish to add such a luxury touch to your prized asset.

PassWallet Brings iOS 6 Passbook App To Android [VIDEO]

PassWallet Brings iOS 6 Passbook App To Android [VIDEO]

iOS 6 has, among a slew of new features and enhancements, brought two significant new native apps to the table. The first was Apple’s publicly-flogged in-house Maps app displacing the popular Google offering, while the second – which has been viewed much more favorably upon – was Passbook. Billed as the answer to general pocket clutter like tickets, vouchers and such, it provides an easy way for such passes and gift cards to be stored digitally, utilized with ease, and readily located when required. In essence, it’s another example of Apple attempting to change everything, again. Although it’s only taking its baby steps into adoption (thus, not widely accepted just yet), many big retailers jumped on the bandwagon – and why wouldn’t they? Over the past few years, everything Apple has made has seemed to turn to gold, and it’s little surprise to see the likes of Starbucks, Target, American Airlines, and Live Nation jump aboard the Cupertino gravy train by offering very prompt Passbook support. Whenever a new feature arrives for iOS or Android, an adaptation for the other respective ecosystem seldom seems to be far behind, and developer Attido Mobile has created a Passbook app for those running on Google’s Android. As you may already know, Passbook for iOS 6 stores all wallet fodder within Apple’s “.pkpass” mime type, so it was pretty easy for Attido take advantage of the idea and essentially port it through to Android.Passbook for Android The “.pkpass” mime type can be embedded within digital receipts you find on your everyday web pages. The app, which is called PassWallet, keeps on the lookout for such receipts, importing them via your e-mail accounts as well as websites you happen to visit. One suspects PassWallet, which isn’t exactly brand-new, won’t last very much longer once Apple gets wind of what’s going on, but if you’re on Android and feel like you’re missing out on Passbook, then grab PassWallet from the Google Play link provided below!For those who’ve been using Passbook over the past few days, what do you think? Does it have the potential to be another game-changer? Please share your thoughts via the usual mediums below!

Nokia To Reportedly Sue HTC Over New Windows Phone 8 Handset Design

Nokia To Reportedly Sue HTC Over New Windows Phone 8 Handset Design

The smartphone industry is no stranger to legal wranglings, with Apple and Samsung duking it out in the courts in a very high-profile battle over certain patent infringements. Samsung has already been ordered to pay Apple more than $1 billion in damages after being found to infringe upon various Apple held patents, but that doesn’t seem to be enough as Apple is seeking to extort an additional $707 million from the Korean electronics giants. If recent reports are true, then it looks like Nokia and HTC could be heading for their own legal battle. The information comes from a so-called previously reliable source who has knowledge of the impending court case and says that Nokia is about to launch some legal action against HTC over the look and design of their recently announced Windows Phone 8 smartphones. Nokia and Microsoft have recently held a joint media event to announce the Lumia 820 and 920 devices that will be powered by Windows Phone 8, with the 920 hopefully being the device that propels the Finnish handset maker back to the top of the smartphone charts. HTC-WP-8X-3V-multicolor HTC also held their own event in the last few days with Microsoft’s Steve Ballmer in attendance. The purpose of the event was to announce their own Windows Phone 8 handsets, the HTC 8X and 8S. There is no denying that the newly announced HTC devices look extremely attractive, but you would laugh out of the office for claiming that the 8X has more than a passing resemblance to the Nokia Lumia 820. Much to the possible detriment of HTC, it looks like the similarities haven’t gone unnoticed by Nokia.The source in question is stating that Nokia is preparing their case in an attempt to try and get the HTC 8X banned from sale in certain territories. The device in question isn’t due to go on sale until November, but if Nokia gets their way, then that won’t happen, at least in the parts of the world that their design patents are enforceable. With both sets of devices scheduled to hit the market in November after Windows Phone 8 has officially launched, it’ll be interesting to see how this one pans out and if the legal action actually comes to fruition.

Android Jelly Bean For Galaxy S III Begins Rolling Out, Coming To More Samsung Devices Later This Year

Android Jelly Bean For Galaxy S III Begins Rolling Out, Coming To More Samsung Devices Later This Year

iPhone, iPad and iPod touch users are just becoming acquainted with iOS 6, released by Apple last week, but for Android users, accessing a new firmware is a different ball game entirely. Android Jelly Bean (4.1) arrived some months ago, with the fledgling Google Nexus 7 among the first devices to ship with the new OS as standard, but thanks to the fragmented nature of Android, users of even the most powerful devices have been left waiting. While fragmentation isn’t always a bad thing, it certainly is when you’re waiting for an Android OTA, and it’s a problem which plagued Jelly Bean’s predecessor – Android Ice Cream Sandwich (4.0) – from the get-go. Astonishingly, at present, many devices – notably the Motorola DROID Bionic – still await even an ICS update – a firmware which released towards the latter stages of last year, and although the focus of many Android users’ attentions is now the buttery-smooth Jelly Bean, the flawed updating system is still a point of frustration to many running Google’s mobile OS. In order to offer some clarification to its millions of worldwide smartphone and tablet owners, Samsung has listed a total of fifteen devices set to see Android 4.1 along its flagship Samsung Galaxy S III. Unfortunately, no details have been revealed with regards to a time bracket, but here, via SlashGear, is the apparently classified list: Galaxy Tab 2 7.0 Galaxy Tab 2 10.1 Galaxy Note 10.1 Galaxy S II Galaxy Note Galaxy Tab 7.0 Plus Galaxy S Advance Galaxy S II LTE Galaxy Music Galaxy Chat Galaxy Ace 2 Galaxy Beam Galaxy Ace Plus Galaxy Mini II Galaxy S DUOS Although, not mentioned in the list, the Galaxy S III has already started to see the Jelly Bean OTA as pointed out by a member over at XDA-Developers (via TheNextWeb). It’s also worth noting that Samsung revealed that the Galaxy S III will get Jelly Bean in October but they’ve already started to push out the update a little earlier. Sit tight, as the complete roll out will take some time to complete. The roll out may be further delayed due to carrier review of the update. The Galaxy Tab 10.1 is surprisingly omitted, although the slate – subject to much controversy during the court case with Apple in San Jose – has been superseded by the significantly advanced Galaxy Note 10.1. What’s more, sales of the slab have hit a brick wall, and with the embarrassing story that consumers had returned in their droves it having erroneously thought it was an iPad, it’s little surprise the Korean company seems to be silently shuffling it into obscurity.

If your device is unlocked, then naturally, you’re likely to see Jelly Bean first, since carriers like to spend days / weeks / months – or an infinite amount of time – adding their own software, which causes so many delays.