Latest News, tutorials and site updates:
New* Killer App- Mac Freeware Review
Current Firmware Version: 2.2.0 **
Hack that iPhone and iTouch: Chat
iPhone:**NEW How to Unlock the iPhone 3G - Mac and Windows **
iPhone: How to Jailbreak Your 2.2.0 3G iPhone (Mac)
iPhone: How to Unlock/Jailbreak Your 2.2.0 2G iPhone Using QuickPwn (Windows)
iPhone: How to Organize Your iPhone Applications Into Folders
iPhone: How to Unlock/Jailbreak Your 2.2.0 2G iPhone (Mac) **
iPhone: How to Jailbreak Your 2.x.x 3G iPhone (Mac) [Updated]
iPhone: How to Jailbreak Your iPhone With QuickPwn [2.1 Firmware]
iPod Touch: How to Jailbreak Your 2.0.1 iPod Touch (Mac)
iPhone: How to Sync Your iPhone With Multiple Computers ( Mac and Windows)
iPhone: How to Trick Your iPhone Into Thinking Its On Wi-Fi
Thursday, October 9, 2008
The Dev Team has posted some of the snags they are coming across on the way to a 3G unlock.
We’ve been exploring different ideas with the 3G unlock, but this past weekend one of us hit a big snag. For whatever reason, all of our poking and prodding of the 3G baseband caused it to finally have a breakdown. After one specific exploit run, all of a sudden our baseband stopped responding to the OS. Even after multiple restore attempts, we were plagued with errors like this:
Somehow our software hacking had caused the baseband chip’s SPI bus to stop responding (so it looked like a hardware problem). Even though BBUpdaterExtreme reported the correct baseband version, it failed basic tests like memtest:
If you’re familiar with the baseband revision history for the 3G iPhone, you may have noticed that the above captures were done at the original 01.45 baseband. As dire (and hardware-related) as these messages sounded, though, there was a simple solution. We just updated to 01.46 and then downgraded again (because we can run unsigned code on the baseband CPU) to 01.45.
We tried to recreate the problem by using the same exploit over again, but it doesn’t appear to be reproducible (which is actually disappointing, as it might have been exploitable).
Anyway, there you go…a random, technical snapshot of dev team work.
Posted by -Administration- at 12:05 PM