|
Re:iPhone Dev Team: Updates from Blog 1 Year, 5 Months ago
|
Karma: 12
|
Jailbreakme v2.0 was a great success, and it’s provided a nice leveling point for all jailbreakers and unlockers on all devices at firmware versions less than 4.0.2/3.2.2. We hope that everybody ever interested in jailbreaks or unlocks was able to join in on the jailbreakme bonanza. Those of you who had Cydia capture your SHSH blobs, or those of you who captured them locally, will always be able to benefit from the jailbreakme.com v2.0 release. Congratulations!
Now it’s a few weeks later, and Apple has closed the jailbreakme.com hole. They’re shipping devices with FW 4.0.2/3.2.2, impervious to this particular jailbreak. So now, people will begin to ask: will there be a jailbreak for devices that shipped with 4.0.2/3.2.2, out of the box?
No, there won’t be. FW 4.0.2/3.2.2 was *only* released to fix the jailbreakme hole. With FW 4.1 still in its beta stages, it makes no sense to escalate the “cat & mouse” with Apple for FW updates that only fix the jailbreak holes. To quote WOPR, “the only winning move is not to play”.
If the cat & mouse game escalates too quickly, especially during beta FW periods, nobody but Apple benefits. For this reason, there won’t be a 4.0.2/3.2.2 jailbreak specifically during the period where 4.0.2/3.2.2 is the latest public release. At best, some future 4.1x FW jailbreak *may* be compatible with 4.0.2/3.2.2 (but don’t count on that).
If any of this is confusing, please ask below in our comments section!
P.S.: For those of you with iPhone3G or iPod Touch 2G(not MC version), it’s true you can always use redsn0w to jailbreak your 4.x devices. Don’t let that dilute the above message, though  |
|
tatb4urot18 (User)
'Nak Ng Tinapa!!!
applei Newbie
Posts: 89
|
|
|
|
|
Re:iPhone Dev Team: Updates from Blog 1 Year, 5 Months ago
|
Karma: 153
|
|
Musclenerd's tweet about itunes 10:
iTunes 10 is safe for JBers+unlockers: DFU mode, syncing, selecting IPSW, all okay (Stay away from 4.1 next week though!)
42 minutes ago via web
|
|
|
|
|
|
|
Re:iPhone Dev Team: Updates from Blog 1 Year, 5 Months ago
|
Karma: 190
|
Heads up from MN 
 |
|
|
|
|
|
|
Re:iPhone Dev Team: Updates from Blog 1 Year, 5 Months ago
|
Karma: 190
|
|
|
|
|
|
|
|
|
Re:iPhone Dev Team: Updates from Blog 1 Year, 5 Months ago
|
Karma: 114
|
|
hmm... then it must be redsn0w or pwnagetool again which is better IMO (less bug)
|
|
|
|
TEAM Applei
Filipino Iphone Community
˙ʎɐʍʎuɐ ǝʌılɐ ʇno sʇǝƃ ʎpoqoN ˙ʎlsnoıɹǝs ǝɟıl ǝʞɐʇ ɹǝʌǝN |
|
|
|
Re:iPhone Dev Team: Updates from Blog 1 Year, 5 Months ago
|
Karma: 144
|
we need redsn0w not pwnagetool
why? for those already on 4.0.2 OFW pwnagetool is not a solution, since it creates a CFW. A CFW requires that the device should be currently pwned in order for a succesful restore/update using a CFW.
What we need is redsn0w type jailbreak
tiny umbrella + redsn0w = perfect |
|
|
|
kikz
TEAM applei
Filipino Iphone Community
Emancipate yourself from mental slavery... |
|
|
|
Re:iPhone Dev Team: Updates from Blog 1 Year, 5 Months ago
|
Karma: 114
|
ay mali, pwnagetool and redsn0w pala ay di pede sa new bootrom  erase! erase! hahaha! |
|
|
|
TEAM Applei
Filipino Iphone Community
˙ʎɐʍʎuɐ ǝʌılɐ ʇno sʇǝƃ ʎpoqoN ˙ʎlsnoıɹǝs ǝɟıl ǝʞɐʇ ɹǝʌǝN |
|
|
|
Re:iPhone Dev Team: Updates from Blog 1 Year, 5 Months ago
|
Karma: 114
|
kikz wrote:
we need redsn0w not pwnagetool
why? for those already on 4.0.2 OFW pwnagetool is not a solution, since it creates a CFW. A CFW requires that the device should be currently pwned in order for a succesful restore/update using a CFW.
What we need is redsn0w type jailbreak
tiny umbrella + redsn0w = perfect
pede redsn0w sa new bootrom?
|
|
|
|
TEAM Applei
Filipino Iphone Community
˙ʎɐʍʎuɐ ǝʌılɐ ʇno sʇǝƃ ʎpoqoN ˙ʎlsnoıɹǝs ǝɟıl ǝʞɐʇ ɹǝʌǝN |
|
|
|
Re:iPhone Dev Team: Updates from Blog 1 Year, 5 Months ago
|
Karma: 144
|
source: www.iclarified.com
The iPhone Dev-Team has issued a warning to remind users not to update to the new iOS 4.1 firmware that is expected today.
Today you’ll likely start seeing iTunes innocently offer you a new version of iOS…version 4.1. Don’t accept it…it’s a trap!
This time of year there are lots of new iPhone owners, and not everybody knows that accepting new iOS updates is the surest way to lose your jailbreak and/or unlock. While those of you who have Cydia or TinyUmbrella backups of your FW hashes will always be able to get back to 4.0.1 if you make this mistake, this doesn’t hold for unlockers. There’s currently no known way to revert your baseband — if you update your baseband you’ll lose the ultrasn0w unlock, possible forever. |
|
|
|
kikz
TEAM applei
Filipino Iphone Community
Emancipate yourself from mental slavery... |
|
|
|
Re:iPhone Dev Team: Updates from Blog 1 Year, 5 Months ago
|
Karma: 114
|
|
To add to that, if your new iphone 4 is already on 4.0.2 and if you think you won't lose anything anyway by upgrading to 4.1 because dev team already announced that there won't be any jailbreak on 4.0.2. Hold that thought, especially if your iphone 4 is carrier locked! FW 4.0.2 still has 01.59.00 baseband, and an unlock is still available. FW 4.1 has updated the baseband to 02.14.00 (no unlock ATM).
If dev team suddenly comes out with a redsn0w version of jailbreak for (4.0.2-4.1), you can still unlock your baseband after jailbreaking your iphone. Otherwise, you won't have any option but to wait for a 02.14.00 unlock which may come later or may not come at all
|
|
|
|
TEAM Applei
Filipino Iphone Community
˙ʎɐʍʎuɐ ǝʌılɐ ʇno sʇǝƃ ʎpoqoN ˙ʎlsnoıɹǝs ǝɟıl ǝʞɐʇ ɹǝʌǝN |
|
|
|
Forums 
