Hubble Starts to Wake Up
Posted by noreply@blogger.com (Zibri) on under reas, mth, thieves | 
After all it's all about money.
ADSENSE robbed all the money in the adsense account
gained in ONE MONTH of advertising on this site.
No reason given.
No explainations.
No nothing.
$4000 in advertising (thanks to YOUR support)
just vanished.
Well, I don't really care so much about money
I am not even selling ZiPhone but I wanted you all
to know what's happening.
I'm disgusted.
Posted by on under iphe, th weekend, beta releases, reas, ipod touch, frts, expiry, ski resort, betas, timeframe, kernel, challenges, blog |
While we continue working on the two current remaining challenges from Apple (the iPhone 3G soft unlock and iPod Touch 2G jailbreakâ??see the end of this post), weâ??re also watching the latest beta releases from Apple.
The first beta 2.2 from Apple reveals a few things:
To demonstrate point #3, hereâ??s the non-AppStore application Terminal.app running on 2.2, showing the kernel build information.
Hardware already vulnerable to pwnage remains vulnerable in version 2.2.
Regarding the two current challenges: the 3G iPhone soft unlock and iPod Touch 2G jailbreak are still relatively new challenges (compare them with the timeframe of the iPhone challenges last year). Weâ??re making slow advances on both fronts, but itâ??s not the sort of thing that can be easily described in a blog like this.
But, to maybe show how interlinked these challenges are, this weekend weâ??ll be trying some hardware based ideas on the iPod Touch 2G jailbreak :)
Posted by on under iphe, th weekend, beta releases, reas, ipod touch, frts, expiry, ski resort, betas, timeframe, kernel, challenges, blog |
While we continue working on the two current remaining challenges from Apple (the iPhone 3G soft unlock and iPod Touch 2G jailbreakâ??see the end of this post), weâ??re also watching the latest beta releases from Apple.
The first beta 2.2 from Apple reveals a few things:
To demonstrate point #3, hereâ??s the non-AppStore application Terminal.app running on 2.2, showing the kernel build information.
Hardware already vulnerable to pwnage remains vulnerable in version 2.2.
Regarding the two current challenges: the 3G iPhone soft unlock and iPod Touch 2G jailbreak are still relatively new challenges (compare them with the timeframe of the iPhone challenges last year). Weâ??re making slow advances on both fronts, but itâ??s not the sort of thing that can be easily described in a blog like this.
But, to maybe show how interlinked these challenges are, this weekend weâ??ll be trying some hardware based ideas on the iPod Touch 2G jailbreak :)
Posted by planetbeing on under level interface, extence, iphone, reas, dev team, new image, out of the blue, svn, parser, vulnerability, futzing, lt, ibss, stock |
So how did I manage to FIX the problem I mentioned earlier? The reason I was so vague on the details is that I used a confidential iBoot vulnerability that we didn't want Apple to know even existed! This allowed me to bootstrap openiboot directly from a stock iBSS that was loaded through DFU mode. I still can't tell you exactly what it is, but since geohot already leaked the existence of it, I figure I can tell you it exists and is what I used. :)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.
