hmn... Not able to JB on 3GS is NOT because of the modem firmware has been updated & patched the vulnerability/hole required for the current JB method... You are wrong in this point..
It is because of 2 thing..
1.) The chips
The specific number they have chosen is the device's ECID, or "unique-chip-id", a number that all devices have so far had, although we haven't seen any previous use for it.
2.) The signature server
Of course, new hardware comes every year, and Apple decided to strike hard with the new iPhone 3G[S]. Rather than just throw in new local protections, Apple decided that every restore of the device would be verified as being valid and safe by Apple itself.
To do this, during the restore process, users see "Verifying restore with Apple...", during which time a challenge/response protocol is used between the iPhone and Apple: a "partial digest" of the firmware files being used is sent to a server, which can then decide to sign off on the result... or not.
Not only does this allow Apple to keep custom firmwares from getting loaded onto the device, but it also allows them to recall existing firmwares by keeping people from restoring to them in the future. To do this they simply would refuse to ever sign, for example, iPhoneOS 3.0 again.
However, to make this model secure, one must verify that their system is not subject to a simple "replay attack": where one just stores a copy of Apple's sign off and then returns it at a later point. This is a "beginner's attack", and one that is easily mitigated by any of a number of strategies.
QUOTE(davidmak @ Sep 21 2009, 04:47 PM)
Yes, even if you downloaded the iPhone OS v3.01 file you can never restore back because Apple has stopped signing 3.01. Also JB won't work at least for now because the modem firmware has been updated and patched a vulnerability/hole required for the current JB method. A new JB method is on the way. No one knows when but it'll be here when it is here.
This post has been edited by sugen: Sep 21 2009, 05:09 PM