pod2g update via his blog

[Shaddow825]

Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A334 Safari/7534.48.3)



Pod2g isn't the dev team. The dev-team prefers to wait for new iOS versions so as many people have a shot at JBing as possible. Other devs don't have to have this philosophy. Take Comex's iPad 2 JB for example. It could've been saved for ios 5, but he didn't feel like waiting for that

True, but he gave it to dev-team and they packaged and released it. I'm sure he didn't force them to.

----------

It would go against their past philosophies of burning exploits by releasing them at an inopportune time. If they take Any longer and 5.1 is released before the A5 jailbreak, but 5.1 patches the jailbreak, then they will have played their cards poorly.

And their tweets are cute and all, but are often: (1) inaccurate with release dates (2) vague in details (3) don't reveal all details relating to exploits.

I would take them with a grain of salt and be patient, because none of know what apple will and wont patch and what the jb devs have up their sleeve.

I know it goes against their past philosophies. That was my point. That they aren't as dumb as people say they are by "burning" this. At best they know it was closed in 5.1 at worst they tell everyone to get on 5.0.1 (or stay on 5.0) and *do not* upgrade. Everyone who cares and is waiting can do that. So they have not burned ANYTHING. Because if you are on 5.0.1 you will be able to jailbreak if you did what they said. Nothing burned. It doesnt matter if 5.1 gets released in the meantime because you should follow what they said and not upgrade. Still nothing burned.

It isn't like once the window is closed any A5 devices will even be able to restore. You will most likely be stuck with whatever firmware you put on there during the window, be it 5.0.1 or 5.1. The firmware to fix the exploit will come out in a week or 2 anyways, be it, 5.0.2 or 5.1.1. So it really doesnt matter. Releasing it to A4 made no practical difference.

 

[solo118]

i'm still unsure what to do. i'm still on 5.0 cuz of fear of losing an unlock. and 5.1 b3 just came out. i don't think apple releases officials so soon after betas. i think i still have some time to wait til 5.0.1.

You have to decide what you rather have. Personally I rather have a JB so I did like pod2g said and updated to 5.0.1 to avoid getting locked out.

If you really need an unlock I do not know what to tell you because 5.0.1 has an upgraded baseband.

 

[philip in al]

Ok, now I'm really confused. Do I need to go ahead and update my JB 4.3 iPad 2, to 5.01 now, or just stay JB and wait on the new JB release?

 

[Dwalls90]

True, but he gave it to dev-team and they packaged and released it. I'm sure he didn't force them to.

----------



I know it goes against their past philosophies. That was my point. That they aren't as dumb as people say they are by "burning" this. At best they know it was closed in 5.1 at worst they tell everyone to get on 5.0.1 (or stay on 5.0) and *do not* upgrade. Everyone who cares and is waiting can do that. So they have not burned ANYTHING. Because if you are on 5.0.1 you will be able to jailbreak if you did what they said. Nothing burned. It doesnt matter if 5.1 gets released in the meantime because you should follow what they said and not upgrade. Still nothing burned.

It isn't like once the window is closed any A5 devices will even be able to restore. You will most likely be stuck with whatever firmware you put on there during the window, be it 5.0.1 or 5.1. The firmware to fix the exploit will come out in a week or 2 anyways, be it, 5.0.2 or 5.1.1. So it really doesnt matter. Releasing it to A4 made no practical difference.

There's no question it will be closed in 5.1, which begs the question, why they would have released the 5.0.1 for half of devices and then release it for the other half after 5.1. These guys know exactly what they're doing. They didn't release 5.0.1 untethered for half the devices without a timetable or good game plan for the A5 devices. It's bad practice and I don't see them doing that. They must have another exploit or secret weapon up their sleeve and are just waiting on Apple to drop 5.1.

 

[Qoo]

Ok, now I'm really confused. Do I need to go ahead and update my JB 4.3 iPad 2, to 5.01 now, or just stay JB and wait on the new JB release?

I would stay with the 4.3 JB until the 5.0.1 JB released for the ipad 2. That's why i am still on 4.3.3 JB for my ipad 2 now

 

[ihav0frnds]

You have to decide what you rather have. Personally I rather have a JB so I did like pod2g said and updated to 5.0.1 to avoid getting locked out.

If you really need an unlock I do not know what to tell you because 5.0.1 has an upgraded baseband.

i want both! is the jailbreak only working on 5.0.1? if so, then i'll update now. but if it works on 5.0 also, then i'd have a chance of both?

 

[Shaddow825]

There's no question it will be closed in 5.1, which begs the question, why they would have released the 5.0.1 for half of devices and then release it for the other half after 5.1. These guys know exactly what they're doing. They didn't release 5.0.1 untethered for half the devices without a timetable or good game plan for the A5 devices. It's bad practice and I don't see them doing that. They must have another exploit or secret weapon up their sleeve and are just waiting on Apple to drop 5.1.

ion1c's 4.3.whatever exploit wasnt closed for many versions, it doesnt always happen. When I say they knew it was closed, i mean they knew it before they released it. As in it didnt work in the current betas.

THEY HAVE A PLAN FOR A5. It is.. you get on 5.0.1 and wait. That's it. It doesn't matter if they wait til 5.1, you'll still be on 5.0.1 because that's what you were told to do. If you didn't then you lose. It isn't bad practice. The only thing you will get if they have another untether for 5.1 is a 2 week window till 5.1.1 comes out to be able to do restores if you jack your phone up. In the big picture (which is what they look at) that is NOTHING.

 

[Dwalls90]

ion1c's 4.3.whatever exploit wasnt closed for many versions, it doesnt always happen. When I say they knew it was closed, i mean they knew it before they released it. As in it didnt work in the current betas.

THEY HAVE A PLAN FOR A5. It is.. you get on 5.0.1 and wait. That's it. It doesn't matter if they wait til 5.1, you'll still be on 5.0.1 because that's what you were told to do. If you didn't then you lose. It isn't bad practice. The only thing you will get if they have another untether for 5.1 is a 2 week window till 5.1.1 comes out to be able to do restores if you jack your phone up. In the big picture (which is what they look at) that is NOTHING.

Obviously, bud. You shifted the argument to something that anyone in the jailbreak community knows.

But you don't know for sure when the A5 jailbreak will drop or if this 5.0.1 untether exploit is their only one, or if they're conserving for 5.1

 

[TSX]

They are not going to wait till 5.1 to release a A5 JB. Remember the chronic dev team said they had 5 exploits in 5.0 beta to use, but when the GM came out all the exploits where closed. I think ionic1 has a 5.1 JB but who knows if apple Will close it when the GM is released.

 

[maturola]

I think Apple will patch the exploit with the release of 5.1 regardless. If I'm not mistaken pod2g already explained how the exploit works for the a4 chip and iOS5 on his blog. Isn't it the same for the A5?

So what difference does it make if he releases now or waits?

Not the same, the A4 + iOS5 exploit can't be fix on software, that is a Bootroom exploit, the A5 exploit had been kept secret to avoid patching.

 

[TSX]

Not the same, the A4 + iOS5 exploit can't be fix on software, that is a Bootroom exploit, the A5 exploit had been kept secret to avoid patching.

If I'm not mistaken It can be patched, bootrom exploits are only for the JB to be untethered.

 

[terraphantm]

True, but he gave it to dev-team and they packaged and released it. I'm sure he didn't force them to.

At that point what good would it have done to not package and release it in redsn0w? Let's say the dev team decided not to release it - Chronic would've still done so and the exploit would still be revealed. When there's no point in saving an exploit anymore (due to a leak or someone else releasing), the dev team doesn't bother holding back. Remember 24kpwn (leaked) and Purplesn0w (independently discovered and released by geohot)? Once there was no more point in holding onto the exploits, they released tools that used them

 

[Ksizzle9]

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)

Not the same, the A4 + iOS5 exploit can't be fix on software, that is a Bootroom exploit, the A5 exploit had been kept secret to avoid patching.

If I'm not mistaken It can be patched, bootrom exploits are only for the JB to be untethered.

If I'm not mistaken, bootrom level exploits always leave the door open for tethered. Don't quote me on this, but I'm fairly certain. I'm still learning the ins and outs of how the jailbreak actually works on the iPhone. I understand the simplicity of actually jailbreaking it with the programs, just learning everything else that is involved. So again, don't quote me and this may be what you are saying, but the bootrom exploit should ALWAYS leave the door open for the tether JB.

 

[la79]

THEY HAVE A PLAN FOR A5. It is.. you get on 5.0.1 and wait. That's it. It doesn't matter if they wait til 5.1, you'll still be on 5.0.1 because that's what you were told to do. If you didn't then you lose. It isn't bad practice. The only thing you will get if they have another untether for 5.1 is a 2 week window till 5.1.1 comes out to be able to do restores if you jack your phone up. In the big picture (which is what they look at) that is NOTHING.

Perfectly said.

 

[maturola]

If I'm not mistaken It can be patched, bootrom exploits are only for the JB to be untethered.

Most Jailbreak required at 2 type of exploits, once that give access (let's call it the door) and another that allow storage (let's call it the closet), the untethered part is when both exploit exist so the code that allow access can be stored locally and it can be call at boot. Bootrom cannot be patch, it is READ ONLY MEMORY, it can only be fix by hardware revision.

Perfectly said.

LOL no, the Big picture is to include those cases where you could revert back if it is a problem, or if the current unlock required to stay behing, that is thinking about the big picture, not just a narrow view of a few impatient people

 

[Dwalls90]

They are not going to wait till 5.1 to release a A5 JB. Remember the chronic dev team said they had 5 exploits in 5.0 beta to use, but when the GM came out all the exploits where closed. I think ionic1 has a 5.1 JB but who knows if apple Will close it when the GM is released.

Not exactly. They said their software/userland exploits had been patched. I'm guessing maybe Comex was told about them somehow and then patched them upon joining Apple but that's pure speculation.

They claimed they had 5 bootrom level exploits, meaning that if they were bootrom, they cannot be patched by software. No one knows what happened with those ...

Not the same, the A4 + iOS5 exploit can't be fix on software, that is a Bootroom exploit, the A5 exploit had been kept secret to avoid patching.

Yes, although the untether component could be.

If I'm not mistaken It can be patched, bootrom exploits are only for the JB to be untethered.

Bootroom exploits allow for a jailbreak and cannot be patched/prevented by Apple. Untether components are software level and can be patched through iOS updates. This is why there was an A4 or lower tethered jailbreak since the bootrom exploit was discovered but there hasn't been an A5 one.

If I'm not mistaken, bootrom level exploits always leave the door open for tethered. Don't quote me on this, but I'm fairly certain. I'm still learning the ins and outs of how the jailbreak actually works on the iPhone. I understand the simplicity of actually jailbreaking it with the programs, just learning everything else that is involved. So again, don't quote me and this may be what you are saying, but the bootrom exploit should ALWAYS leave the door open for the tether JB.

Yes, that's correct.

That's why we are crossing our fingers for a definite A5 bootrom level exploit.

 

[Ksizzle9]

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)

Yes my legs are even crossed.

 

[nepalisherpa]

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)

Yes my legs are even crossed.

You must be a girl!

 

[bansheebeat]

How serious is everyone taking the "release later this week" comment?

 

[bradl]

How serious is everyone taking the "release later this week" comment?

Not really taking it seriously at all. I'm about 98% sure it won't happen this week.

Musclenerd's tweets along with pod2g's last tweet pretty much sums it up:

Sorry, we can't release the A5 for the developers the exploit used have to be kept secret. I know this is unfair.

Before that, he explained that you needed a developer account (and appropriate tools from it) to jailbreak the A5:

How could pod2g have an untethered 4S and dev teams still haven't released tools to achieve this at home?
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.

So if they couldn't distribute it legally, and just got @saurik to join the team and make progress, while they are near having something, there is no way they are going to have it ready (read: idiotproof) for distribution by the end of this week. Just isn't going to happen.

BL.

 

[jbarresi19]

Well plant being just posted for the first time in over a year..

@planetbeing- And we're out of the sandbox with @saurik's invaluable help! (well, at least there's a PoC) Turning out more complex than X-Gold 618.

I thought they were already done with the sandbox but i guess they are definitely now. Not sure what PoC means, anyone?

I am guessing this can only be more good news

----------

Nevermind I just googled it and PoC means proof of concept.

 

[SayMilesAway]

what exactly is the sandbox?

 

[Ksizzle9]

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)

Yes my legs are even crossed.

You must be a girl!

Edit: the sandbox comment was answered a few pages back. Something about an area to trap bad behaving code.

The crossed legs was a joke, if they were my jewels would be smashed.

 

[ihav0frnds]

errrbody get yo 5.0.1!!

 

[Shaddow825]

Obviously, bud. You shifted the argument to something that anyone in the jailbreak community knows.

But you don't know for sure when the A5 jailbreak will drop or if this 5.0.1 untether exploit is their only one, or if they're conserving for 5.1

I never said I knew anything that anyone else did. It may come out after 5.4.6 comes out in 10 months for all I know, or after IOS6. And if it does, it WONT MATTER ONE BIT. Nothing will have been burned. They will advise people to keep on 5.0.1 if they want a jailbreak if the hole closes in anything >5.0.1

I only said from looking at all the facts, there is nothing to point to a new exploit and that every reason brought up so far does not do so. And everything that they have said points to it being the same exploit. They have all but said "Dwalls90, we are working on the same exploit" I dont understand where the opinion that its a new exploit is coming from based on the fact that the A4 was released. That makes no sense.

----------

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)



If I'm not mistaken, bootrom level exploits always leave the door open for tethered. Don't quote me on this, but I'm fairly certain. I'm still learning the ins and outs of how the jailbreak actually works on the iPhone. I understand the simplicity of actually jailbreaking it with the programs, just learning everything else that is involved. So again, don't quote me and this may be what you are saying, but the bootrom exploit should ALWAYS leave the door open for the tether JB.

Bootrom exploits can vary. The 24kpwn bootrom exploit on 3g and 3gs old bootrom makes them always untethered, it's that big of a hole. So big that for the only time ever Apple changed the bootrom midcycle.

The great things about any bootrom exploit is the unpatchability and as a result they always have some little crack (or big crack) to start the userland exploits going.

----------

Not really taking it seriously at all. I'm about 98% sure it won't happen this week.

Musclenerd's tweets along with pod2g's last tweet pretty much sums it up:



Before that, he explained that you needed a developer account (and appropriate tools from it) to jailbreak the A5:



So if they couldn't distribute it legally, and just got @saurik to join the team and make progress, while they are near having something, there is no way they are going to have it ready (read: idiotproof) for distribution by the end of this week. Just isn't going to happen.

BL.

they could distribute the instructions legally and let anyone with a developer account utilize it, but they wont. They won't because as long as it's kept secret and undisclosed it's their equivalent of a bootrom level exploit that isnt patched. It gives them a crack in the system to get in and look around and find exploits in other parts of the system. If they didn't have that, you would probably have to wait for an exploit to be in a more visible part of the OS much as safari and not low level stuff like racoon (which corona is based on) which would greatly diminish the chances of a jailbreak.