release? Video
Tuesday, December 9, 2008
What To Do If Your Dog Ate A Loaf Of Bread
This is the question that dwells in the minds and post all the iPod touch 2G owners who do not believe in fairy tales, and still do not know a jailbreak (officially at least [give me the benefit of the doubt]) for ipod touch 2nd generation.
But then the question arises:
when we unlock our ipod?
meantime I want to clarify that it is quite possible THE RELEASE!
said, speaking of timing, and how we can calculate ... Since then, some rumors and speculation can already see the jailbreak from mid-December, the team does not specialize in jailbreak becomes unbalanced and let out a "perhaps the first of January."
But let the facts and see what we see on the site of chronic queue-dev ...
Last night I did not post the new article because one of the steps to jailbreak was missing "(Pending. ..)" from about one day and a half because he was the processing step ... but we see that process proceeds, I'll post quello che compare adesso sul google code di chronic-dev dandovi poi le relative spiegazioni:
"
Current Goals Jailbreak iPod Touch 2G
-Create iBoot 2.x Communication Tool (DONE - See 'iRecovery' in SVN trunk) -Look at new DFU Mode proctool (DONE - It seems to be the equivalant of WTF 2.0 that iTunes attempts to strap onto old devices (iTouch 1G, iPhones) when they are plugged in. Device ID is 0x1227 instead of 0x1222) -Get Filesystem Dump (DONE)
-Find userland exploit, for the time being, as a last resort (Not yet completed) Exploit-Find iBoot (Goal Is Actively Being Worked on / Looked Into)
-Implement exploits, and OWN (Not yet completed) "
How can we see, 6 step 3 is complete (DONE), and one is almost nearing completion ... " (Goal Is Actively Being Worked on / Looked Into) " MA, I actually run 2 and 3 (including one in progress) because the last (
Implement exploits, and OWN -Implement exploits, and OWN (Not yet completed) "
How can we see, 6 step 3 is complete (DONE), and one is almost nearing completion ... " (Goal Is Actively Being Worked on / Looked Into) " MA, I actually run 2 and 3 (including one in progress) because the last (
) is nothing but implement the exploits with the "OWN", and then create and release "simple"! What does this mean? means that it is in the process "iBoot Exploit" and having eliminated the "rootfskey" probably because they act or implemented in the 'iBoot Exploit ", the release could very well be announced by the chronic-dev for mid-December, and the dev team in late December or early January ...
All this of course barring unforeseen circumstances, they may be slowed down or sped up the work.
It is important to know that the chronic-dev is working actively on the last release, and that the steps are very few left!
It is important to know that the chronic-dev is working actively on the last release, and that the steps are very few left!
(not to say virtually no one to bring bad luck: P)
So for now it's just there will be updates of any kind, I will present them without a doubt, then I recommend you follow the directions to enroll for deep in my blog "rss feeds" section of this blog for more news in real time
.
You can also let us note facendomeli updates or help yourself via comments or private messages telling me what you know or suspect.
Links of teams working on the release:
Blog Chronic-dev: http://chronic- dev.org / blog /
Google code project jailbreak of chronic-dev: http://code.google.com/p/chronicdev/
Blog Iphone-dev (Dev-Team): http : / / blog.iphone-dev.org /
remain available for any questions!
Regards for now.
UPDATES
A step backwards for the jailbreak!
Or one on?
Dear friends, unfortunately for the jailbreak iPod touch 2g, were found for "smooth" otherwise, as some rumors said, today we could have the jailbreak, because in fact, "iBoot exploit" would be the last step ... But there were hitches as I said ...
Now we come to see us and such a hitch, and they can delay the jailbreak:
The chronicdev with a message on their blog (entitled A New
Challenge ), explains the difficulties encountered, and explains that it could already be a jailbreak, but that would not have made it possible to launch applications that are not marked.
According to them, in fact, this discovery is a step FORWARD
, for now sanno quali sono gli ultimi 2 exploit che devono trovare, infatti ecco i nuovi step del loro "google code":
"
Current Goals
Jailbreak iPod Touch 2G Current Goals
-Create iBoot 2.x Communication Tool (DONE - See 'iRecovery' in SVN trunk) -Look at new DFU Mode proctool (DONE - It seems to be the equivalant of WTF 2.0 that iTunes attempts to strap onto old devices (iTouch 1G, iPhones) when they are plugged in. Device ID is 0x1227 instead of 0x1222) -Get Filesystem Dump (DONE)
-Find exploit to run unsigned code at DFU / iBoot level (Not Complete) -Find exploit to make the signature check bootrom pass on a patched LLB (Not Complete)
"How do you see two exploits for the non-execution of file" unmarked "and not safe (according to apple: P).
At this point, they will return to work, because that's
will.chronicdev "
(
well, a jailbreak is still possible!
well, a jailbreak is still possible!
), now, even with the help of " MuscleNerd
" the dev-team, you will begin to work on what should be, even according to the chronicdev "the last 2 step"! Unfortunately, there are rumors on the output of the jailbreak, in fact I believe that this obstacle partially set aside the old "weather" ... will.chronicdev ironically concludes his blog post with a "just iBoot exploit to run unsigned code is only the beginning." ie: iBoot exploit to run unsigned code is just the beginning ... Many actually still see the possibility of a release for Christmas gift ... well I hope so!
yet I will keep you informed! stay tuned!
Regards.
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment