Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Sorry, but where's that from :confused:

From his blog update today:

"Sandox broken
Here are some news about the current work on the A5 research.

@planetbeing escaped from the sandbox with the help of @saurik. Thanks to their awesome work, there should be nothing left blocking for the A5 jailbreak.

Now it should be a matter of days. Still no precise ETA of course.

We all want this to be finished ASAP, we're getting tired!"


Maybe he omitted the detail of it being untethered, but he didn't explicit detail it.

It's from a few posts back. The post titled A5 FAQ. It's the first line in that post.
 
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

Its untethered its the same exploit as found in all devices i spoke with p0six about this
 
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

Its untethered its the same exploit as found in all devices i spoke with p0six about this

sounds good. i bet its gonna be stable as hell with these guys working on it too...look forward!
 
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

Josh said thats wat there striving for total stability
 
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

Name dropping!!! Jk jk, at this point I could care less I just want to jailbreak this 4S!!
 
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

Name dropping!!! Jk jk, at this point I could care less I just want to jailbreak this 4S!!

actually i remember him proving he talks to that dude...
 
Took the plunge and updated my ipad 2 today to 5.0.1 from 4.3.3 and am awaiting the JB like everyone else.
Thanks to the dream team for their efforts.
Mac.
 
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

rick snagwell said:
Ksizzle9 said:
Name dropping!!! Jk jk, at this point I could care less I just want to jailbreak this 4S!!

actually i remember him proving he talks to that dude...

Yes i remember reading that thread a while back. Unless it was a diff one. I was most certainly not calling him a liar. Just can't wait to see the JB on my 4S!!!!

Edit: there isn't anyway you can date drop is there? I ask only with the best of intentions. Just give us a lil something to look forward to! Jk jk. I know, number one rule in JB: don't talk about JB.
 
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

Lol aint as iff josh is famous aha anyway who cares fact is its untethered and its coming and we can all be very thankfull to the team especially pod2g for there hard work and effort
 
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

Aha nice fight club reference it is a bit like that ahha
 
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

snowwhite007 said:
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

Aha nice fight club reference it is a bit like that ahha

Love it!!!
 
It's from a few posts back. The post titled A5 FAQ. It's the first line in that post.

indeed, the first line is a question, the answer pod2g give to his own question is:

"The exploit I used to inject the untethering files to the 4S relies on having a developer account, and can't be released publicly.
It's the same reason why @MuscleNerd has an iPad 2 tethered jailbreak but couldn't distribute it.
So, we need to find a distributable exploit to remount the system partition read/write and to set Corona files at the correct places."

Thats what they have now!
 
planetbeing also posted some details about whats been going on and some more details about the process and the steps and where they are in those steps.

http://www.reddit.com/r/jailbreak/comments/oe2n1/why_we_can_never_give_etas_for_jailbreaks/

Very nice read posted by planetbeing:

Why we can never give ETAs for jailbreaks. (self.jailbreak)
submitted 3 hours ago by planetbeing
The problem with giving any definite ETAs is that there can always be problems that crop up that blindside us that will take an unknown amount of time to solve (if they are even solvable). Let me give you a little timeline about this sandbox issue, for example (though I have to avoid giving currently classified technical details ;)).

Generally, constructing jailbreaks takes a lot of time researching issues: how, conceptually, are we going to break Apple's protections and mitigations against it. Then, to figure out what precise techniques will we use to implement our ideas. Those take an unknown amount time and may actually be impossible. It is theoretically possible for Apple, if they don't make any mistakes, to create a system that prevents jailbreaking. Then, after those are figured out, time can be spent coding the jailbreak, which takes a more predictable amount of engineering time. Unfortunately, sometimes while coding, you happen to discover the method you thought would theoretically work, even a method you tested before, might have unforeseen difficulties because you made some incorrect assumptions.

When we're at the research stage, we can't give an ETA because we don't even know if it's going to be possible. When we're at the engineering stage, we can't give an ETA because heaven forbid we find that we've made a mistaken assumption and need to go back to the research stage.

I started to actively participate on January 6th, and I thought I could contribute by helping to figure out the sandbox issues since that's the one thing that needed to be researched at that point. The following five days has been one of the more irritating weeks of my life. On day 1, pod2g and I both independently came up with a way to circumvent the sandbox that would've been nice and simple. Unfortunately, later that day we discovered we misread the sandbox profile and it would not be possible. The next day was spent trying to see if any clever variation of the first idea could get around the sandbox: no. Then we were messing around and found a small vulnerability in the sandbox, a one millimeter hole in a huge wall if you will, and it seemed like it could be weaponized to get around the sandbox so we can break out. Eventually, I came up with the plan that formed the basis of what we have right now, but it needed three different pieces to make work. I managed to furnish the first piece myself pretty quickly, but the other two were not forthcoming. The next few days were filled with brilliant ideas by brilliant people that would work if only such-and-such were true. Every day, it was two steps forward and one step back. Then pod2g made a suggestion on how the second piece could be obtained and saurik managed to find it fairly quickly going off his suggestion. The day before, we thought we had finally gotten it: The idea had gotten past basic testing, so we made a few tweets on progress. Then later we found out, crushingly, that there was a weird behavior that prevented our method from working in practice. The next day was us scrambling to figure out a variation of the idea that would work, which required finding other candidates for the idea's prerequisites. saurik managed to figure some stuff out that gave us a little more invaluable wiggle room in finding the prerequisites and I managed to find something that would work. I created a proof of concept and it worked!

The result is basically building a program that aims a tiny bullet to shoot out of the one millimeter hole in our sandbox, having it bounce off of a few different surfaces (that we were lucky to find) to adjust our aim and have it go down the exhaust port of the Death Star, and instead of blowing it up, bounce off a few more surfaces inside the Death Star to get to the control room, and have the bullet bounce off buttons and levers to aim the Death Star at the sandbox wall to blow it up.

We don't think there's any more issues and we are starting to engineer it, but we don't really want to say we don't think there's any more issues because one or more might crop up. So basically, we've had really significant progress, but we can't give an ETA.
 
That is a very good find!

Thanks

yea the community over there isn't too big but those in the know sometimes participate. Besides planetbeing, I know xuzz (chpwn) is there as well.

----------

He also said in another post "However, the latest breakthrough was definitely significant progress. It's seriously good news."
 
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

brayhite said:
glad they are making progress and its really sad he had to explain it to people.

Is this your yearly post? listed as a newbie and member since 2003??

Aha leech JKJK
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.