Free Soft
Oct 28
Credits..
Posted by noreply@blogger.com (Zibri) in george hotz, team tool, impressive team, unsigned code, breakthru, th time, pwns, menti, peoe, elite, blog on 10 28th, 2008| icon3
The 837 Key



I wonder why I am the one accused of stealing
and then NOBODY gives me the credit for what I have done.

The only 2 things I did in the iPhone scene
were to DUMP THE 837 KEY and booting from an unsigned ramdisk.
(nobody even understood what it was when
I posted it on my blog).

Now the so called "dev team" released their tool
and I see no mention of that.

George Hotz wrote a code based on dev team tool
to "execute unsigned code at dfu level"...

Look at the start of the code:

const unsigned char key837[]={0x18,0x84,0x58,0xA6,0xD1,0x50,0x34,0xDF,0xE3,0x86,0xF2,0x3B,0x61,0xD4,0x37,0x74};

That is the key I dumped.
Without it NO TOOL could ever be possible.

That's why I called it a "major breakthru" at that time.

That key also made it possible to decrypt the ramdisk and
create a custom one.

Now if you remember I have always credited people
(george hotz for his unlock based on gray's work and
many members of iphone-elite that now are calling
themselves "dev team").

Now I won't say anyone stole anything.
But these are the FACTS.

Dev team did an impressive team work this time
and even if I don't personally like the tool I see
no other way to do things on 2.0.
(If I'll see one I'll tell you) :)

The same people accusing me
of "stealing" didn't EVER credit me for what
I've done.

And I repeat for who wasn't
reading at that time:
no ZiPhone (iLiberty/iPlus) could
ever be existed without the ramdisk
exploit I found and
no "pwns" without the 837 key.

Zibri.


Tagi: george hotz, team tool, impressive team, unsigned code, breakthru, th time, pwns, menti, peoe, elite, blog

Dec 4

â?? 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:

SPI error

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:

memtest fail

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.

flashing back 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

next >