Posted by on under mac check, iphone, jailbreak, iphe, software package, important news, hack, interface | 
These instructions are deprecated - it's much easier to download iBrickr and just use the Ringtones interface.
I worked my eyes bloody today crawling through disassembly to help ziel port his Jailbreak program to Windows, and today we can announce that we have succeeded! All the iPhone users running Windows can now put custom ringtones and sounds onto their iPhones.
IMPORTANT NEWS: The iPhone software update 1.0.1 makes these instructions invalid. You STILL need to acquire the old 1.0.0 software package for Jailbreak to still work. Apple will surely have stopped distributing the package by now so I will see what I can do to get Jailbreak working on the new package. Watch for updates!
If you have a Mac, check out the Mac instructions over at
Hack the iPhone.
These instructions work...Read the rest of this post
Tagi: mac check, iphone, jailbreak, iphe, software package, important news, hack, interface
Posted by on under jailbreak, iphone, phe, dev team, rk, itunes |
Well, the iPhone Dev Team has done it again. A working jailbreak for 1.1.3 is finally here.
STATEMENT OF RISK
As all upgrades are risky, this one is doubly so. You may have to restore your phone using iTunes and start again if it fails. Make sure to back up first!
Let's continue
This jailbreak, like the 1.1.2 jailbreak, comes as an upgrade. This means you need to have a 1.1.1 or 1.1.2 jailbroken phone already, before you can begin.
QUESTIONS? See the FAQ
Official Jailbreak release works for iPod Touch, and is easier to do. Go here for that.
Update - unlocked phones appear to remain unlocked and work properly after the update, according to scattered reports.
MAC...
Read the rest of this post
Tagi: jailbreak, iphone, phe, dev team, rk, itunes
Posted by on under kathy griffin, pwnage, engadget, jailbreak, hacks, stranger, web page |
Hereâ??s one happy Pwnage advocate. Anyone know who he is? :)
Update: By the way, Woz is no stranger to iPhone Dev Team hacks. Some of you may remember his visiting the Dev Teamâ??s ridiculously easy 1.1.1 jailbreak that required absolutely no PC or Mac at allâ??just a web page visit to http://jailbreakme.com
That was done on Kathy Griffinâ??s actual show: http://www.viddler.com/explore/engadget/videos/23/
Tagi: kathy griffin, pwnage, engadget, jailbreak, hacks, stranger, web page
Posted by on under technical snapshot, spi bus, baseband, unsigned code, software hacking, memtest, hardware problem, reas, sime, ipod touch, jailbreak, snag, two steps, attempts |
â?? one step back.
Disclaimer!! This is a purely technical post with no pragmatic use! There is no 3G unlock in this post. There is no iPod Touch 2G jailbreak in this post. Itâ??s just a random technical post related to the 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.
Tagi: technical snapshot, spi bus, baseband, unsigned code, software hacking, memtest, hardware problem, reas, sime, ipod touch, jailbreak, snag, two steps, attempts
Posted by on under technical snapshot, spi bus, baseband, unsigned code, software hacking, memtest, hardware problem, reas, sime, ipod touch, jailbreak, snag, two steps, attempts |
â?? one step back.
Disclaimer!! This is a purely technical post with no pragmatic use! There is no 3G unlock in this post. There is no iPod Touch 2G jailbreak in this post. Itâ??s just a random technical post related to the 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.
Tagi: technical snapshot, spi bus, baseband, unsigned code, software hacking, memtest, hardware problem, reas, sime, ipod touch, jailbreak, snag, two steps, attempts
