• What is it ?
  This is a standalone piece of hardware able to boot your jailbreaked device (a.k.a “tethered boot”), and optionnally to jailbreak and hacktivate it if not already done.
• Why do I need this ?
  If your jailbreaked device is stuck into “recovery mode” (i.e Connect-to-iTunes logo) each time you restart or reboot your device, then it may be usefull for you =)
• I want one !
  From now, I only have a dozen of (working) prototype. I need to raise some minimal funds to start manufacturing them in quantities, to lower the price as much as possible for the community. You can help by buying me a prototype at good price, or simply donate as pre-order



• How do I know if my device is concerned ?
  Any iPhone 3GS made after week 40 (2009). The week number is usually the 4th and 5th digit of the serial number. iPod Touch 2G whose serial number begins with “MC” are concerned or any iPod Touch 3G.
• Which device is supported ?
  From now, iPhone 3GS and iPodTouch 2G/3G are supported, all with OS 3.1 / 3.1.1 / 3.1.2 only, but the later is recommended.
• Will you support OS 3.1.3 ?
  Maybe, or not. iDongle can be easily updated through USB. If jailbreak is available, I’ll try and post a free update.
• Does it provide unlock ?
  Not directly. Look for Geohot’s “sn0w” or Dev Team’s “ultrasn0w” package on Cydia.

Just received the PCB prototypes ! I have 8 pieces 12 pieces on hand, and since it’s hand mounted, for each, it tooks me half an hour to solder all components…

Parts supply is difficult for such low quantities, but If I have enough queries, I should be able to start a little production, but don’t expect prices below 10€, the bill of material, including PCB, is about 22€ each (VAT included) for a 50 pieces batch, and it’s not yet mounted… 30€ could be a good price ?

Of course, if your device don’t need to boot tethered once jailbreaked (old bootrom), this is useless for you, go ahead, you’re lucky.

From now, for late devices, only OS versions up to 3.1.2 supports Jailbreak, so please, don’t upgrade to 3.1.3 until I post an update, and don’t blame me if you do so !

Moreover, you can use it as a mini-USB to 30 pins adapter if you need to connect to a computer with just any regular USB cable.

And please note again, at time of writing, IT DOES’NT WORK (yet) for 3.1.3 devices ! If available, I’ll post a firmware update as soon as possible.

Since I can’t afford the bill for covering a 50 pieces batch, you can donate few bucks to help me start, or become a generous (and famous) geek by buying me one of my prototype at good price

If you place an order afterward, please remember me your Paypal ID, I’ll deduce your donation from your order, and if I can’t raise enough funds, I’ll return money back to anyone asking it.

List of Donors

Here’s the story :

I subscribed, few weeks ago, to an “unlimited data plan” from my mobile provider. I was so enthusiast that I sold my old Nokia N70 (Symbian OS8) on Ebay to buy an expensive Nokia E90 (OS9), infinitively more adequate for heavy use of www and networking applications.

I quickly discovered “what’s under the hood” : this “unlimited” data plan is restricted to HTTP traffic on port 80 by use of proxy filtering that mean no IMAP, no POP, no VNC, no SSH, nor TELNET…

Moreover, there’s an extra filtering on User-Agent to (loosely) prevent its use from your computer by using the phone as modem for example.

I quickly had to found a solution, and the only one available was Tunneling, more precisely HTTP Tunneling, since writing Tun/Tap drivers on Symbian platforms is not possible without manufacturer’s SDK. After some Googling, I found the GNU HTTP Tunnel under GPL license.

Thanks to port of Posix libraries on Symbian OS9 (P.I.P.S), the porting of the project to S60 tooks less than 48h. The most difficult parts were :

1. No poll() function
2. Small heap/stack
3. lack of console

The first point was solved by replacing poll() functions by select(), using threading as workaround to limitations due to implementation :

“select operation cannot be called for the second time on the same socket descriptor before the first select operation on the same socket descriptor completes. (i.e) Only one select operation can be outstanding on a Socket. This is because of the limitation of the underlying Ioctl Ioctl operation. Only one operation may be outstanding for each socket.”

The second point involved reducing size of local arrays, and by increasing default heap/stack size of application using correct statements in mmp file.

Concerning the lack of console, I used stdioserver as output console, and Python for passing command line.