Thursday, 25 October 2012

Unlock iOS 6 On iPhone 4/iPhone 3GS With Ultrasn0w Fixer

Those of you who were unwilling to update to the latest iOS 6 because there was no unlock available can now update because Ultrasn0w Fixer can now unlock iOS 6 for iPhone 4 and 3GS. 

iOS 6 Utrasn0w Fixer unlock
This is not the ultrasn0w official tool. However, it works with the official tool for basebands that are compatible, and can be unlocked by the official ultrasn0w. It can be used until there’s an update for the official tool to unlock the latest iOS 6 firmware.
iOS 6 Ultrasn0w fixer supported devices
  • iPhone 3GS
  • iPhone 4
iOS 6 ultrasn0w fixer supported basebands
  • 01.59.00 (iPhone 4)
  • 04.26.08 (iPhone 3GS)
  • 05.11.07 (iPhone 3GS)
  • 05.13.01 (iPhone 3GS)
  • 05.12.01 (iPhone 3GS)
  • 06.15.00 (iPhone 3GS)
How to unlock iOS 6 on iphone 4/ iPhone 3GS Using Ultrasn0w fixer:

Step 1: Jailbreak your i device @ ios 6

Step 2: Launch Cydia.
Step 3: Open Manage > Sources. Tap ‘Edit’ at the right corner at the top and add this repo:
Step 4: Tap on the URL you entered above.
Step 6: Ultrasn0w fixer for iOS 6 will be visible. Start the process by tapping on it.
Step 7: Download the official tool of ultrasn0w unlocker.
Congrats. You would now be able to get the iOS 6 unlock for iPhone 4/3GS. This can be used until the official tool is updated. Remember to download the ultrasn0w fixer first before the official tool.

Thursday, 18 October 2012

iPhone Dev-Team Announces Massive Update to RedSn0w

The iPhone Dev-Team has announced RedSn0w 0.9.15b1 which brings numerous new features including the ability to restore to older firmware not being signed by Apple.

New Features:
● restore from any 5.x iOS to any other (up, down or the same) 5.x iOS on all devices as long as you have the correct blobs (see more below)
● Cydia now included in the tethered 6.0 jailbreak on A4 devices
● automatically "Just Boot" tethered when qualifying A4 device connects in DFU mode
untethered 6.0 jailbreak on old-bootrom 3GS
● untethered 6.0 hactivation on any 3GS or iPhone4
● directly restore pre-A5 devices to earlier firmware - no more complicated 15-step how-to's with stitching, iTunes errors, and "hosts file" concerns
● fetch new signed blobs for any IPSW (present or future - no redsn0w update required) using Extras->SHSH Blobs->New
● block the BB update for any 3GS or iPhone4 restore (past, present, or future - no redsn0w update required) using Extras->Even More->Restore
● deactivate any iPhone, useful for testing your "official" unlock status through iTunes. (Please only deactivate your own iPhone!)
● activation status shown on "Even more" page
● significantly more (very nerdy) info returned by "Identify" button when device is in Normal mode
● tethered jailbreak of ATV2 supported (but the only thing available for it is the SSH2 custom bundle available here - no Cydia yet. Must use "Select IPSW" for tethered boot of ATV2 for now).
● auto-exit WTF mode for older devices with broken buttons
● any time a set of blobs is fetched remotely (from Apple or Cydia), redsn0w also saves them locally (and will check there first if you click "Local")
● for your future restoring convenience, you should also submit all of your past and present TinyUmbrella blobs to Cydia if you haven't done so yet. Resubmitting is okay and won't cause conflicts.

iOS 5 to iOS 5 Restores for A5+ Devices

1. redsn0w now lets you restore an A5+ device from any iOS5 to any other iOS5 as long as you have correct 5.x blobs for the starting (current) and ending points of the restore
● APtickets eliminated "higher-version only" comparison of firmware restores (just like BBtickets did for the baseband)
● example restores supported by redsn0w if you have the correct blobs: 5.1.1-to-5.0.1, 5.0.1-to-5.1.1, 5.1.1-to-5.1.1, 5.0.1-to-5.0.1
● if you don't have the blobs locally, let redsn0w try to fetch them remotely (redsn0w always tries both Apple and Cydia). Any succesful remote fetch also saves a local copy too.

2. You DO NOT QUALIFY for iOS5-to-iOS5 restores if you got to your current 5.x via an OTA update
● the tickets saved by Cydia, redsn0w, and TinyUmbrella do not cover OTA update ramdisk images 
● even if they did, it's the "wrong kind" of ramdisk (you'd need to start at that earlier pre-OTA FW)
● devices fresh from factory or refurb may fall in the "does not qualify" category (your results will vary)
● it's okay if you previously got to 5.x via an OTA update, as long as your current 5.x was installed via a normal iTunes restore. All that matters is how you got to your current 5.x most recently
● redsn0w detects an OTA/normal-restore APticket mismatch very early, so if you don't know your status there should be no harm in trying. Any device in recovery mode after such a mismatch can boot normally again just by going back to "Even More" screen from the "Restore" screen (or use "Recovery Fix" if you quit redsn0w before doing that).

3. Unlike the A4 devices, redsn0w can't (usefully) prevent the baseband updates of A5+ iPhones and iPads.
● and so, redsn0w automatically flashes the currently signed baseband when it does A5+ restores, even if those basebands didn't come with the original firmware
● stay away from this if you have an unofficial unlock that isn't supported by the newest baseband
● the least-tested baseband update code in redsn0w is for iPad2,3 and iPad3,2. Please give any feedback on those iOS5 restores in the comments section below.

4. iPad2 owners (all three models) with saved 4.x blobs can use those instead, even from 6.x
● if you have both 4.x and 5.x iPad2 blobs, you can always get to 5.x via the 4.x blobs, even if you're currently on 6.x
● you cannot get to 5.x from 6.x without the 4.x blobs (but you may still qualify for the iOS5-to-iOS5 restore described above)
● if somehow you have 4.x blobs but no 5.x blobs, you can still go down to 4.x from 6.x
● this only applies to iPad2 owners (they're the only A5+ devices that ever had a public 4.x FW)
● redsn0w still supports (but doesn't require) jailbreaking A5+ devices at 5.0.1 and 5.1.1. Just head back to the first page after re-restoring to 5.x. It's always much faster to jailbreak those FW versions with a freshly-restored device, before letting iTunes restore from a saved userland backup.

5. ultrasn0w isn't yet updated for 6.x
● by now you probably should be taking advantage of the extremely cheap IMEI-based unlocks of iPhones sold by established online retailers like http:://
● still, IMEI-based unlocks don't work in all cases. We'll announce when ultrasn0w is ported up to 6.x
● redsn0w will still hactivate your 3GS or iPhone4 if you run it before the device is activated. Due to the current tethered 6.x JB status, redsn0w now hactivates 6.x without requiring subsequent tethered boots. If you accidentally hactivate with redsn0w, use the "Deactivate" checkbox available from the Jailbreak screen, not the normal one in "Even more"

6. As always, redsn0w lets you "Fetch" the SHSH blobs currently flashed onto your pre-A5 device
● use this if you're at 5.x or 4.x but without having saved your blobs when the window was open
● this is only useful when Apple is no longer signing the firmware, otherwise Cydia/redsn0w "New"/TinyUmbrella blobs are superior (but you're welcome to fetch your 6.0 blobs this way anyway)
● fetching blobs in this fashion will automatically forward them up to Cydia, as well as save a local copy

We'll be posting tutorials on how to use these new features shortly. You can follow us on TwitterFacebook, and RSS.

● How to Manually Submit Your Saved SHSH Blobs to Cydia (WindowsMac)
● How to Jailbreak Your iPhone 4 Using RedSn0w [6.0] (WindowsMac)
● How to Jailbreak Your iPod Touch 4G Using RedSn0w [6.0] (WindowsMac]
● How to Re-Restore Your iPhone From iOS 5.x to iOS 5.x (WindowsMac)
● How to Re-Restore Your iPad From iOS 5.x to iOS 5.x (WindowsMac)
● How to Upgrade Your iPhone 4, 3GS Without Updating the Baseband (WindowsMac)
● How to Downgrade Your iPhone 4 From iOS 6.x to iOS 5.x (WindowsMac)
...more to come!

You can download RedSn0w 0.9.15b1 from here.

Read More

How to Downgrade Your iPhone 3GS From iOS 6.x to iOS 5.x (Windows)

These are instructions on how to downgrade your iPhone 3GS from iOS 6.x to iOS 5.x using saved SHSH blobs and Redsn0w for Windows.

Step One
Create a folder on your desktop called Pwnage

Download the latest version of RedSn0w from here and place it in the Pwnage folder. Likewise, download the firmware you would like to restore to and the firmware you are current on from here and place it/them in the Pwnage folder. 

Extract the RedSn0w zip file to the Pwnage folder.

Step Two
Right click or control-click the redsn0w application from the redsn0w folder we extracted earlier and chooseRun as administrator from the popup menu that appears.

Step Three
Click Extras from the main menu.

Step Four
Click Even More from the Extras menu.

Step Five
Click Restore from the Even More menu.

Step Six
Click IPSW from the Restore menu, choose the IPSW you would like to restore to from the window that appears, and click Open.

Step Seven
Redsn0w will ask you if you would like to prevent the baseband from being updated. Click Yes.

Step Eight
Redsn0w will inform you that Pwned DFU mode is needed to restore. Click the OK button.

Step Nine
Connect your device, turn it off, and then click the Next button

Step Ten
RedSn0w will now guide you through the steps to get into DFU mode. You can find more help with DFU modehere.

Hold down both the Home button and the Power button for 10 seconds.

Release the Power button and continue holding the Home button until RedSn0w detects the device.

Step Eleven
Your iPhone will now be exploited with limera1n.

Step Twelve
RedSn0w will check Cydia to see if you have the correct blobs saved.

If RedSn0w is unable to find your blobs automatically you can try to click the Remote button to try again or you can click the Local button to search for blobs on your computer.

Step Thirteen
RedSn0w will now prepare a system restore image.

Step Fourteen
Your device will then be restored to the new firmware.

Step Fifteen
You'll be informed when your restore has completed successfully. 

Thursday, 16 August 2012

ATF SL3 Simlock Recovery v9.0 Update!


In the past, when a dead Nokia BB5 SL3 Phone comes to your shop, it was only
possible for you to backup the IMEI via a Backup RPL Function. There was no
way for you to backup a possibly 100% working SIMLOCK inside the phone because
you needed Local/Test Mode in order to get the PM Backups. Dead Phones cannot
give you Local/Test Mode at all, so you cannot backup the Simlocks even if you
wanted to.
Now here comes the Solution... The ATF Simlock Recovery Module v1.0 will allow
you to BACKUP SIMLOCKS from a DEAD PHONE! Just a 1-click solution for Recovery
Level 1 and Level 2 for NON-CORRUPTED SIMLOCKS on a DEAD PHONE. 
Even if your phone SIMLOCKS are CORRUPTED, The ATF Network can still attempt to 
perform a Level 3 Recovery from it, but it will cost you some ATF SL3 Credits.

Here is a Short Description about the three Simlock Recovery Levels:

Recovery Level 1:

* Phone DOES NOT need to be AUthorized
* 100% Stand Alone
* Supports ALL SL3 XSR3 NAND Blocks for RAPUv1, RAPUv2, RAPIDO, RAPG3v4 and BCM21351
* Supports ALL SL3 XSR2 NAND Blocks for RAPUv1, RAPUv2, RAPIDO, RAPG3v4 and BCM21351
* Supports ALL SL3 NOR Blocks for RAP3Gv3 (FULL PM RECOVERY)
* Supports ALL SL2 NOR Blocks for RAP3Gv3 (FULL PM RECOVERY)
* Supports ALL SL1 NOR Blocks for RAP3Gv3 (FULL PM RECOVERY)
* Supports USB or FBUS Connection (FBUS ONLY FOR RAP3Gv3)
* Recover from DUMP FILE or from Connected PHONE
* The output file is a REGULAR PM FILE with PM 120 Sections 0, 1, 2 and 3

Recovery Level 2:

* Phone NEEDS to be Authorized via The ATF Network
* Supports ALL SL3 XSR3 NAND Blocks for RAPUv1, RAPUv2, RAPIDO, RAPG3v4 and BCM21351
* Supports ALL SL3 XSR2 NAND Blocks for RAPUv1, RAPUv2, RAPIDO, RAPG3v4 and BCM21351
* Supports ALL SL2 NOR Blocks for RAP3Gv3 (FULL PM RECOVERY)
* Supports ALL SL1 NOR Blocks for RAP3Gv3 (FULL PM RECOVERY)
* Supports USB or FBUS Connection (FBUS ONLY FOR RAP3Gv3)
* Recover from Connected PHONE ONLY
* Recovery Time will depend on Fragmentation Level of the XSR Blocks
* SIMLOCKS WILL BE VERIFIED (Since Phone is already Authorized)
* The output file is a REGULAR PM FILE with PM 120 Sections 0, 1, 2 and 3

Recovery Level 3:

* Needs SL3 Credits and only available for ATF Network Activated Users
* Phone NEEDS to be Authorized via The ATF Network
* Recovery is performed by our Servers (NOT STAND ALONE)
* Supports ALL SL3 XSR3 NAND Blocks for RAPUv1, RAPUv2, RAPIDO, RAPG3v4 and BCM
* Supports ALL SL3 XSR2 NAND Blocks for RAPUv1, RAPUv2, RAPIDO, RAPG3v4 and BCM
* Supports ALL SL3 NOR Blocks for RAP3Gv3
* Supports USB or FBUS Connection (FBUS ONLY FOR RAP3Gv3)
* Recovery Time will depend on CURRENT TASK LOAD on the ATF Simlock Recovery Server
* SIMLOCKS WILL BE VERIFIED (Since Phone is already Authorized)
* The output file is a REGULAR PM FILE with PM 120 Sections 0, 1, 2 and 3
* POSSIBLE TO SUPPORT OVERWRITTEN PM 120 Blocks with Wrong PM 120 Blocks
* SUCCESS RATE = 95% if the Phone is not wrongly Repartitioned by a wrong Firmware 


1. Level 1 Recovered Simlocks are NOT VERFIED to be Working (NOT GUARANTEED)
2. Level 2 Recovered Simlocks are 100% VERIFIED and Guaranteed to WORK
3. Level 3 Recovered Simlocks are 100% VERIFIED and Guaranteed to WORK


If your phone is DEAD, but the SIMLOCKS are 100% OK, then the ATF Simlock 
Recovery Module will recover your simlocks for you via Recovery Level 1 or 2.
If your phone is DEAD, and the SIMLOCKS are possibly corrupted, then the 
ATF Simlock Recovery Module will recover your simlocks for you via Recovery
Level 3 + ATF SL3 Credits.

Box Firmware Update:

New ATF Firmware LogiCore 10.3.15 for ATF Chrome, ATF Lightning and ATF Nitro Boxes

Other Updates:
* MEEGO PHONE Authorization EVEN IF 20-digit SL3 Code is detected.
* Shows full RPL (Certificates) Information during Backup RPL on BB5 Phones.
--> Checks Original IMEI
--> Checks Original Product Code
--> Checks PA_PUBLIC_ID
--> Checks Original BT ID
--> Checks Original WLAN ID

* New option in Settings "Select USB Connection by Default when ATF Software Starts"
* Cross Flashing is now IMPOSSIBLE if Phone has good IMEI (NO MORE WRONG FIRMWARES)
* Flash File CRC32 is now CHECKED BY DEFAULT on Flash Files downloaded from NaviFirm etc... 
* Other small tweaks which I already forgot to mention...

Wednesday, 15 August 2012

Google+ App for iOS Now Opens Links in Chrome, Lets Teens Join Hangouts

Google has updated its Google+ app for iOS to make web links open in Chrome and to lets teens join and create Hangouts.

Stay connected and share life as it happens with Google+ for iPhone and iPad. Join a Hangout, post a photo, or see what friends are sharing while you're on the go.

✓ New iPad-optimized layout brings your stream to life 
✓ Share photos directly to Events for all your friends to enjoy
✓ Video chat with up to 9 friends with mobile Hangouts
✓ Turn on Instant Upload to sync photos from your phone to a private Google+ album
✓ Chat with a friend or all your friends at once with Messenger from your phone
✓ Check out the What's Hot stream to see popular posts
✓ View the Nearby stream to see what people near your location are saying
✓ See vibrant, high-resolution images on Retina display devices

What's New In This Version:
✓ Web links in posts now open in Chrome (if installed)
✓ Teens can now join and create Hangouts 
✓ Instant Upload bug fixes to improve performance

You can download Google+ from the App Store for free.

Monday, 13 August 2012

Leaked Photos of the 'iPhone 5' Logic Board

This follows a series of part leaks by the site which includes photos of the much rumored 9-pin mini-dock connector.

Apple is expected to unveil the next generation iPhone on September 12th.

Saturday, 11 August 2012

Students Build USB Controller for Angry Birds

Super Angry Birds is a force feedback USB controller for Angry Birds that simulates the feeling of a slingshot. The controller was created by Hideaki Matsui and
Andrew Spitz for a class at the Copenhagen Institute of Interaction Design.

All the controls found in the game are available in this device. You can control the pull, the angle, and of course trigger the special power of the bird. We hacked a motorized fader found in audio mixing consoles to simulate the force you would feel when using a slingshot.

We programmed in Max/MSP and Arduino. For controlling the hardware, we used an Arduino-based microcontroller called Music & Motors developed by CIID.

This was part of the class on Haptics at CIID run by Bill Verplank and David Gauthier.

Take a look at the controller in action below...

[via Omar]

Wednesday, 8 August 2012

Apple Is Banishing Google From iOS 6: 10 Reasons Why

Apple and Google have long since become bitter rivals in the mobile market. In fact, Apple announced on Aug. 6 that it would not offer a native YouTube app in iOS 6. Users hoping to access YouTube videos will be forced to watch them from within the browser. Google will also likely launch a YouTube app in the App Store.
Apple’s decision to keep YouTube out of  iOS 6 comes just a few months after it announced that the native Google Maps app would also be stricken from iOS 6 and be replaced by its own Maps application. It’s not immediately clear if Apple will come up with something to replace YouTube.
Still, it’s clear that Apple wants nothing to do with Google in iOS 6. And every last remnant of the search giant’s apps must be gone before Apple will feel entirely ready to release the latest edition of the mobile operating system.
Here are the reasons why.
1. They’re competitors, aren’t they?
It shouldn’t come as much of a surprise that Apple doesn’t want Google infiltrating iOS 6. After all, the companies are intense competitors in the mobile space. Google offers Android; Apple delivers iOS. Apple has the iPhone, and now, thanks to its Motorola buy, Google is in the hardware business. It never makes business sense to let a rival prosper in your territory.
2. Maps mean big business
When Apple announced that it was ditching Google Maps for its own alternative, the idea seemed to make some sense. Mapping is big business that drives people to a respective company’s products. By allowing iOS users to run Google Maps, Apple was giving the search company an opening to promote its brand, the Android mobile operating system. It also allowed Google to earn advertising dollars from Maps and Search. Now that its own Maps application will be the new standard, Apple doesn’t need to worry about that anymore.
3. Don’t forget about Lala
Years ago, Apple acquired Lala, a music-streaming site, and promptly closed it. Since then, speculation has continued to crop up over why it did so. Is it possible that Apple acquired the team to work on a streaming video service? If so, that service wouldn’t be a YouTube competitor, per se, but it could allow users to stream iTunes programming to devices. In the off chance that happens either this year or in the future, it would only make sense for Apple to want to get rid of YouTube now.
4. Apple’s Motorola troubles
Apple is by no means happy with Motorola, even if it wasn’t owned by Google. The company has, in fact, sued Motorola for patent infringement in its mobile devices. It’s entirely possible that Apple doesn’t want to partner with Googlenow simply because it owns Motorola.

5. Apple’s lawsuits revolve around Android
It can’t be said enough that a key component in Apple’s decision to drop Google apps from iOS 6 could be its ongoing litigation with Android vendors. Apple doesn’t want to look like it’s playing both sides by offering the same native applications as Android. But by offering not one, but two, Google applications in iOS, it might make some juries believe Apple doesn’t have quite as big of an issue with Android as it seems to suggest.
6. Could Apple be lining up a Google lawsuit?
It’s impossible to discount the possibility of Apple preparing a lawsuit against Google. After all, Apple could win a landmark ruling in its Android fight with Samsung, and if that happens, it could take the battle to Google’s doorsteps. Partnering with the company now would make that a bit more difficult.
7. Mobile advertising is coming on strong
Mobile advertising is the often-forgotten culprit in many of the poor decisions companies make with their operating systems. Apple realizes that the future of the mobile space will revolve around intra-app ads, and it might not want to give Google two places to use AdMob to rake in some cash from every iPhone and iPad owner out there.
8. Apple wants to leverage revenue opportunities
With the thought of mobile advertising in mind, Apple might just want to make some cash itself. Thanks to its iAd platform, Apple could conceivably integrate ads into its Maps application and any program it might use to replace YouTube. Apple’s revenue opportunities might even extend beyond advertising to other options, like virtual goods or company lists in Maps. Don’t underestimate the revenue-seeking efforts behind Apple’s decision to get rid of Google.
9. Don’t forget Apple’s penchant for control
If there is anything Apple is known for, it’s control. The company hates allowing other companies to impact the overall usability of its operating systems. As a result, Apple might have finally decided that all native applications running in iOS 6 should come from its own developers. If owners want anything else, they’ll have to go to the App Store to find it. For Apple, its decisions often revolve around control. And this might just be another one of those decisions.
10. An iOS 5 nixing would have been a bad idea
Apple’s decision to ditch Google apps in iOS 6 might have as much to do with hardware as software. If Apple got rid of two popular mobile applications in iOS 5 and launched the barely updated iPhone 4S at the same time, critics would have hit it hard. But now that Apple is expected to launch a major iPhone hardware update this fall, the lack of a few popular competing apps might be overlooked. It’s an interesting move on Apple’s part.

iOS 6 Offers New Wi-Fi Plus Cellular Mode

iOS 6 Beta 4 brings a new feature called Wi-Fi Plus Cellular that lets apps having trouble with poor Wi-Fi use cellular data instead.

The feature is accessible from the Settings -> General -> Cellular menu. 

Also new in iOS 6 is the ability to decide whether to use cellular data for iCloud Documents, iTunes, FaceTime, Passbook Updates, and Reading List.

Take a look at the screenshot below.

[via AppAdvice]

Saturday, 4 August 2012

iPhone Serial # Checker (3G & 3G'S)

This freesoftware by chevli is usefull to check your iphone's serial # if it is safe or unsafe to update the baseband from older to 6.15 especially in 3G's, can easily recognized the bootroom with your iDevice through color coding (green > safety & red > risky). It is tested for some advanced user's.