pod2g update via his blog

[bradl]

It doesn't matter whether you've downloaded the file, if it's not installed on your phone before Apple stops signing install requests you WILL NOT be able to install it on your phone. Any time you install iOS on a phone, it MUST phone home to Apple for permission. If you wait until after 5.1 is released you will ONLY be able to install 5.1.

That doesn't sound right.. I was successfully able to install 3.1.2 on my iPhone 3G when 3.1.3 was already out, as I had 3.1.1 installed at that time. It wasn't until about 3 months later that I installed 3.1.3, which I was able to get successfully as well; so I don't know if that is the case, or if that has changed.

BL.

 

[Mikhailov]

It wasn't any of the devs that said it would drop later this week though.

 

[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)

That explains. I figured I shud have checked twitter myself. Followe along with there convo. Oh well, maybe whoever said this knows something we don't and there is some substance to it.

 

[yamatitan]

That doesn't sound right.. I was successfully able to install 3.1.2 on my iPhone 3G when 3.1.3 was already out, as I had 3.1.1 installed at that time. It wasn't until about 3 months later that I installed 3.1.3, which I was able to get successfully as well; so I don't know if that is the case, or if that has changed.

BL.

Its changed apple stopped signing old software after 5.0 release.

Edit let me rephrase apple isnt signing anything after 5.0, so now that 5.0.1 is out you cant get 5.0. So when 5.1 comes out you wont be able to get 5.0 or 5.0.1. I believe they are still signing for software before 5.0.

 

[whiskeyvol]

It wasn't any of the devs that said it would drop later this week though.

i've bolded the important parts

From P0sixninja twitter

@YourAnonNews thanks for the mention. Things are going smoothly so far

In response to AnonNews:

the iPhone 4S isn't able to be jailbroken until @pod2g @MuscleNerd @p0sixninja and crew drop it later this week.

 

[Quazimojo]

Generally you will have a few hours to get to your computer and install it before Apple stops signing it.

That is why i updated because you never can be certain you will have time when they launch 5.02/5.1 etc.

I would hate to think because of my stubbornness i missed the chance to Jailbreak my device and that very well could be the case for some.

As the saying go's "You have been warned"

 

[tctony]

Now you know why my 4s is still sitting in it's box waiting to be activated, a full download of the 9a405 build of 5.0.1 sitting on my mac, and I'm still on my jailbroken and unlocked iPhone 3G. There is no way anyone should have expected a jailbreak to be ready for any version of iOS for this new hardware, and that is the real source of the issue: people's unrealistic expectations. When you have patience and WAIT, your experience will be much better and your frustrations much less.

BL.

I don't think expectations were that unrealistic.

The first iPhone was jailbroken in less than a month. The 3G in 9 days. The 3GS in 2 weeks. The 4 in 1 month.

 

[Wowzera]

I believe you missed the part about my having the full download of 5.0.1 (9a405) sitting on my Mac.

I am ready for the jailbreak, but may also need the unlock. I never said I wasn't prepared, but just haven't activated my 4S and complained like everyone else has about a jailbreak taking to long, because I know how long it could take to find exploits like this. A lot of people don't appreciate the time it takes to do this, and that reveals a lot about themselves.

BL.

So? What makes you think you can upgrade to 5.0.1 when Apple stops signing this firmware? You can download any firmware files and that does not mean you can upgrade/downgrade to them.

i guess you missed the part of the discussion about the 'dream team' probably waiting for 5.1 until they release the a5 jailbreak

They're working on the 5.0.1, there's no "waiting for 5.1".

 

[whiskeyvol]

They're working on the 5.0.1, there's no "waiting for 5.1".

do you honestly believe they're not working on a 5.1 jailbreak, considering they're all developers and the beta software has been released to developers?

 

[bradl]

So? What makes you think you can upgrade to 5.0.1 when Apple stops signing this firmware? You can download any firmware files and that does not mean you can upgrade/downgrade to them.

As I said, the fact that I was able to upgrade from 3.0 to 3.1.2 when 3.1.3 was available. Unless Apple changed its practices, there should really be nothing stopping me from following the same path. In iTunes, I:

1. plug in my phone,
2. hold shift+restore,
3. navigate to my download of iOS, and
4. watch the new iOS get installed on my iPhone.

Worked for 3.x, so unless Apple made any changes to its process, that should work. Keep in mind, I'm still on that iPhone 3G until a JB comes out for the 4S. then I move to it.

BL.

 

[Dwalls90]

i've bolded the important parts

Him saying things are going smoothly means they're making headway, but he never agreed and said that we would see it this week.

They're working on the 5.0.1, there's no "waiting for 5.1".

And you read this where? Source?

As I said, the fact that I was able to upgrade from 3.0 to 3.1.2 when 3.1.3 was available. Unless Apple changed its practices, there should really be nothing stopping me from following the same path. In iTunes, I:

1. plug in my phone,
2. hold shift+restore,
3. navigate to my download of iOS, and
4. watch the new iOS get installed on my iPhone.

Worked for 3.x, so unless Apple made any changes to its process, that should work. Keep in mind, I'm still on that iPhone 3G until a JB comes out for the 4S. then I move to it.

BL.

If you have an old-boot rom 3GS or older, then yes, this practice will work, as SHSH blobs are not required. For new-bootrom 3gs -> iPhone 4S you need blobs, and blobs won't even work on the iPhone 4S

 

[bradl]

If you have an old-boot rom 3GS or older, then yes, this practice will work, as SHSH blobs are not required. For new-bootrom 3gs -> iPhone 4S you need blobs, and blobs won't even work on the iPhone 4S

That would explain why that would work on my 3G. So something HAD changed.

BL.

 

[Wowzera]

And you read this where? Source?

I won't link you any sources, but you can go through p0sixninja, pod2g and musclenerd timeline. They didn't mention any 5.1 wait and also adviced all users to keep/upgrade in/to 5.0.1.

----------

As I said, the fact that I was able to upgrade from 3.0 to 3.1.2 when 3.1.3 was available. Unless Apple changed its practices, there should really be nothing stopping me from following the same path. In iTunes, I:

1. plug in my phone,
2. hold shift+restore,
3. navigate to my download of iOS, and
4. watch the new iOS get installed on my iPhone.

Worked for 3.x, so unless Apple made any changes to its process, that should work. Keep in mind, I'm still on that iPhone 3G until a JB comes out for the 4S. then I move to it.

BL.

This is how things normally work, if Apple is still signing the firmware. If the current firmware is 5.1 and you're on 5.0, you won't be able to upgrade to 5.0.1 (as there's no bootrom exploit for A5 devices).

 

[Dwalls90]

I won't link you any sources, but you can go through p0sixninja, pod2g and musclenerd timeline. They didn't mention any 5.1 wait and also adviced all users to keep/upgrade in/to 5.0.1.

Just like when they also told us to stay on 5.0.0, right? Sorry bud, but them telling us to stay on 5.0.1 shouldn't be taken as the law of the land. We are staying on 5.0.1 because we have to, but 5.1 may be a game changer. If it's dropped they might as well reconfigure it for 5.1.

 

[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)

I for one, would GLADLY take a jailbroken 5.0.1 over a fantastically updated 5.1. I can probably add all of the features of 5.1 in JB on 5.0.1. Also, I went thru the timeline after my last post, I agree with the above reader that they clearly stated that the A5 JB would drop this week. I may have to check it again, after all I'm human and make mistakes.

 

[Shaddow825]

II'm not saying you're necessarily right or wrong, but it's presumptuous to assume it's THAT easy. I would assume that it's more difficult than you're making it out to be, and that the untethered component may require some different exploits, especially for A5. But that's assuming that there is even a bootrom exploit for A5 ... which there's no evidence of yet. If they had one, I'm not sure why they wouldn't reveal it. It's not like Apple can patch it, as you said.



I think that they must have another untether exploit up their sleeves, if they were so willingly wishing to release the 5.0.1 one so late in the game, and with the A5 release clearly not being as easy or as soon as we all thought.

Pod2g specifically said that this works on the A5 and they "only" just need an injection vector

https://twitter.com/#!/pod2g/status/151638900165718016

Like I said, there is nothing that they have said that seems to point to another untether.

I think that they prob should not have released this 5.0.1 untether at this point with 5.1 in beta. But it does give some clues as to whats going on. Especially considering that a4 users could have gone back to 5.0.1 with their SHSH/APTickets saved and it would have only benefited A5 users to keep it unreleased where they could have told them to stay on 5.0.1.

Assuming they are smarter than it might appear (which is safe to say!) would lead one to believe that they might know this is closed in 5.1. This would explain all their actions so far. Releasing it to A4 users, encouraging A5 users to get onto 5.0.1 while they can (or stay on 5.0 and wait for the backport), and going into real detail as to what the exploit was. The only thing that doesnt fit is, if it didnt work on 5.1 they could have said that already to emphasize the importance of staying on 5.0.1 (but maybe that warning will come with an actual 5.1 release, as they never address anything to do with future IOS releases until they are released)

 

[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)

All great points, I wish we could get a little more info out of pod and the rest of the devs but it ain't gonna happen. That's sad because some of us(like many in this thread) wait patiently and don't bash the guy who seemed to be the only person with a JB for ios 5. I tend to think that if we don't see anything this week we will start the real waiting game on 5.1, at this point I just want to see a A5 jailbreak. I have a iPad 2 as well but could give a **** less if it's jailbroken. It serves it's purpose well without jailbreak. However I would love to see one on my 4S. Sorry for those who want their iPad 2 broken, for me the phone better suits jailbroken.

 

[Dwalls90]

Pod2g specifically said that this works on the A5 and they "only" just need an injection vector

https://twitter.com/#!/pod2g/status/151638900165718016

Like I said, there is nothing that they have said that seems to point to another untether.

I think that they prob should not have released this 5.0.1 untether at this point with 5.1 in beta. But it does give some clues as to whats going on. Especially considering that a4 users could have gone back to 5.0.1 with their SHSH/APTickets saved and it would have only benefited A5 users to keep it unreleased where they could have told them to stay on 5.0.1.

Assuming they are smarter than it might appear (which is safe to say!) would lead one to believe that they might know this is closed in 5.1. This would explain all their actions so far. Releasing it to A4 users, encouraging A5 users to get onto 5.0.1 while they can (or stay on 5.0 and wait for the backport), and going into real detail as to what the exploit was. The only thing that doesnt fit is, if it didnt work on 5.1 they could have said that already to emphasize the importance of staying on 5.0.1 (but maybe that warning will come with an actual 5.1 release, as they never address anything to do with future IOS releases until they are released)

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.

 

[Applejuiced]

It sure is interesting.
Kinda like the days of our lives

 

[ihav0frnds]

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.

 

[tctony]

It sure is interesting.
Kinda like the days of our lives

Like sand through the hour glass....

Thats what this wait feels like!

 

[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)

Thru the 24 hour glass.

 

[terraphantm]

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 specifically said that this works on the A5 and they "only" just need an injection vector

https://twitter.com/#!/pod2g/status/151638900165718016

Like I said, there is nothing that they have said that seems to point to another untether.

I think that they prob should not have released this 5.0.1 untether at this point with 5.1 in beta. But it does give some clues as to whats going on. Especially considering that a4 users could have gone back to 5.0.1 with their SHSH/APTickets saved and it would have only benefited A5 users to keep it unreleased where they could have told them to stay on 5.0.1.

Assuming they are smarter than it might appear (which is safe to say!) would lead one to believe that they might know this is closed in 5.1. This would explain all their actions so far. Releasing it to A4 users, encouraging A5 users to get onto 5.0.1 while they can (or stay on 5.0 and wait for the backport), and going into real detail as to what the exploit was. The only thing that doesnt fit is, if it didnt work on 5.1 they could have said that already to emphasize the importance of staying on 5.0.1 (but maybe that warning will come with an actual 5.1 release, as they never address anything to do with future IOS releases until they are released)

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.

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

 

[Dwalls90]

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/9A406 Safari/7534.48.3)

Pod2g specifically said that this works on the A5 and they "only" just need an injection vector

https://twitter.com/#!/pod2g/status/151638900165718016

Like I said, there is nothing that they have said that seems to point to another untether.

I think that they prob should not have released this 5.0.1 untether at this point with 5.1 in beta. But it does give some clues as to whats going on. Especially considering that a4 users could have gone back to 5.0.1 with their SHSH/APTickets saved and it would have only benefited A5 users to keep it unreleased where they could have told them to stay on 5.0.1.

Assuming they are smarter than it might appear (which is safe to say!) would lead one to believe that they might know this is closed in 5.1. This would explain all their actions so far. Releasing it to A4 users, encouraging A5 users to get onto 5.0.1 while they can (or stay on 5.0 and wait for the backport), and going into real detail as to what the exploit was. The only thing that doesnt fit is, if it didnt work on 5.1 they could have said that already to emphasize the importance of staying on 5.0.1 (but maybe that warning will come with an actual 5.1 release, as they never address anything to do with future IOS releases until they are released)[/I]

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.

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

When I say JB devs, that includes the dev team, chronic dev and individuals. And he released it for 4.3.3 because that was the current iOS release at the time. 4.3.4 + brought no new features other than patching the jailbreak. If he waited for ios 5 would mean waiting several months ...

 

[NanoNyrd]

(deleted - I posted before thinking).