Seriously U want - 100 EURO DOLLARS - Check it

Depacco.com

Thursday, January 17, 2008

iPhone Firmware 1.1.3 Imminent: Breaks Unlock, Activation & Installer

I’m sure by now everyone with an iPhone has seen and is equally excited about the latest firmware update for Apple’s iconic shiny phone. When videos of the update running on a live phone surfaced (hat tip TUAW) this weekend I was a bit skeptical, but it appears this update is legit. Killer new features will include: saving pinned locations in Google Maps, location triangulation via cell tower location (wow!), movable springboard icons, and multiple recipient SMSing.
Now these updates sound great but what about the thousands of iPhone users running hacked firmware like me? As with previous updates the word on the street is that 1.1.3 will in fact break 3rd party apps and unlocks, and will most likely leave you with a bricked iPhone.

From Jesus Diaz and iPhone hacker Natetrue via Gizmodo:
The update breaks AnySim’s unlocks. Logically, you can’t unlock this update using AnySim and there’s no alternative to iTunes for activation. If you want to activate, it will only work using iTunes and a standard AT&T account. Nate says, “that is the only way we have been able to activate so far.” Nate tried to upgrade an AnySim 1.2u iPhone and it failed. Even while he was able to force it to boot, the phone refused to activate even with a normal AT&T SIM card. “I suspect it’s due to the fact that the baseband could not be upgraded to the 1.1.3 ‘required’ version”, he says.

Other updates remain untested, like iPhone Sim Free or any of the hardware-based ones, like TurboSIM. In theory, these should work just fine, but jailbreak and activation would be absolutely impossible for the time being. We would have to wait until the update gets released in the open to try new alternative activation methods.

While I could live without the 1.1.2 updates, the 1.1.3 actually has some juicy new features. I wonder when Apple is going to get the clue that people are dead set on using their devices as they see fit? Will the February SDK even solve any of these problems, or just create more?

No comments: