Is pod2g on Facebook? I've run across a page that looks legit and it said "2-3 days" on Thursday. Just curious.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
pod2g update via his blog
- Thread starter rick snagwell
- Start date
- Sort by reaction score
This has got to be one of the most eagerly awaited JB yet!
How spoiled was I when I picked up a new 4 in July, and had it JB 20 minutes after breaking the seal on the box -
How spoiled was I when I picked up a new 4 in July, and had it JB 20 minutes after breaking the seal on the box -
@bornauk--@pod2g well @planetbeing just tweeted his only just got the JB together never mind testing it. ****in hell this is just ******** now!! WOW
@planetbeing --@bornauk I was working on it every second I was awake yesterday. There's a lot of work that needs to be done. No one said it'd be quick.
Looks like we got some time to go Really disappointed cause i had a feeling it would be today, oh well done refreshing every 5 minutes
@planetbeing --@bornauk I was working on it every second I was awake yesterday. There's a lot of work that needs to be done. No one said it'd be quick.
Looks like we got some time to go
Really disappointed cause i had a feeling it would be today, oh well done refreshing every 5 minutesWirelessly 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)
No he aint on FB, both teams have jailbreak and its just a case of perfecting the tool then uploading them to there servers so that miltiple servers can be used when released to avoid to much hassle i wouldnt wait for it to happen today aim for more midweek.
macslayer118 said:
No he aint on FB, both teams have jailbreak and its just a case of perfecting the tool then uploading them to there servers so that miltiple servers can be used when released to avoid to much hassle i wouldnt wait for it to happen today aim for more midweek.
im sure snowwhite talks to josh. @poisxninja
---
I am here: http://maps.google.com/maps?ll=32.775204,-117.251912
---
I am here: http://maps.google.com/maps?ll=32.775204,-117.251912
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)
Man its cool if ppl think im lying who cares aint getting the 4s jb any faster aha
rick snagwell said:
Man its cool if ppl think im lying who cares aint getting the 4s jb any faster aha
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)
Of course i am did i say i had it? Anyway lets just move on ill keep my thoughts to myself just thought i was helping my bad
jbarresi19 said:
Of course i am did i say i had it? Anyway lets just move on ill keep my thoughts to myself just thought i was helping my bad
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)
It looks like I'll just learn to take any tweeted ETA's with a grain of salt. I def don't think the dev team means to be late, just problems.
It looks like I'll just learn to take any tweeted ETA's with a grain of salt. I def don't think the dev team means to be late, just problems.
It's not your thoughts that people found annoying, it's your acting as if you have some inside information that no one else does and when you're called on it, you act like this.
Q: How were your guesses helping any more than everyone elses guesses?
A: They weren't.
On one hand, I'm patient and understanding because without this "Dream Team", there would never be a JB for the A5 devices. Thus, having a JB released later rather than never is obviously better.
However, on the other hand, the only real reason why I'm personally frustrated is twofold. For one, I've had the 4S since a week after it was launched. It has been almost four months. Having an unjailbroken iPhone makes owning an iPhone so much less fun and entertaining in my opinion. To be honest, I've been carrying around my Jailbroken iPhone 4 because the tweaks I have activated on it greatly outweigh the 4S's enhanced functions and other benefits.
For example, I hate the multitasking bar on the default device - I much rather prefer the multifl0w tweak. Not to mention simple tweaks such as NoBookMarks, themes, etc. which surprisingly go a long way in making your user experience better. A Jailbroken iPhone 4 > an unjailbroken iPhone 4S in my opinion. It's frustrating to have a phone that is 67% faster, etc., and not be able to use its full power and potential. So, in a nutshell, I've been using my 4S for pictures/videos/phone calls/Siri (which I rarely actually use), etc., and using my 4 for everything else. Now, this is mostly irrelevant to the Dev Team, but I just wanted to voice my frustrations in this perspective. (As an aside, has anyone else contemplated selling their 4S and using the 4 as their primary device until a JB for A5 was released?)
Secondly, and most importantly, I hate when people release ETAs which are based on nothing. {Granted, none of them specifically stated a solidified time frame, but it was obviously inferred from ... "matter of days" ...}
Now, if PlanetBeing just now got unsigned code running on the 4S, not even mentioning the testing, creating the public program to install, etc. processes, we're probably at least another 3-4+ days from a public release - and that's if no problems arise and everything runs smoothly according to plan. I thought that Pod2G's last blog message meant they were in the final process of compiling a public release, not still working on trying to get unsigned code to work.
Oh well, hopefully the JB will be available in the next week. Just a little frustrating that the team were estimating 3-ish days when they hadn't even got unsigned code to work yet (a fairly substantial step in the JB process.)
P.S. Since the vulnerability for the 5.0.1 exploit has been patched in the 5.1 Beta, here's to realistically using the 4S on 5.0.1 for the next several months (maybe even after the iPhone 5 is launched). Cheers.
P.S.S. One can only hope the A6 processor won't be this difficult to crack. But it probably will be even worse.
However, on the other hand, the only real reason why I'm personally frustrated is twofold. For one, I've had the 4S since a week after it was launched. It has been almost four months. Having an unjailbroken iPhone makes owning an iPhone so much less fun and entertaining in my opinion. To be honest, I've been carrying around my Jailbroken iPhone 4 because the tweaks I have activated on it greatly outweigh the 4S's enhanced functions and other benefits.
For example, I hate the multitasking bar on the default device - I much rather prefer the multifl0w tweak. Not to mention simple tweaks such as NoBookMarks, themes, etc. which surprisingly go a long way in making your user experience better. A Jailbroken iPhone 4 > an unjailbroken iPhone 4S in my opinion. It's frustrating to have a phone that is 67% faster, etc., and not be able to use its full power and potential. So, in a nutshell, I've been using my 4S for pictures/videos/phone calls/Siri (which I rarely actually use), etc., and using my 4 for everything else. Now, this is mostly irrelevant to the Dev Team, but I just wanted to voice my frustrations in this perspective. (As an aside, has anyone else contemplated selling their 4S and using the 4 as their primary device until a JB for A5 was released?)
Secondly, and most importantly, I hate when people release ETAs which are based on nothing. {Granted, none of them specifically stated a solidified time frame, but it was obviously inferred from ... "matter of days" ...}
Now, if PlanetBeing just now got unsigned code running on the 4S, not even mentioning the testing, creating the public program to install, etc. processes, we're probably at least another 3-4+ days from a public release - and that's if no problems arise and everything runs smoothly according to plan. I thought that Pod2G's last blog message meant they were in the final process of compiling a public release, not still working on trying to get unsigned code to work.
Oh well, hopefully the JB will be available in the next week. Just a little frustrating that the team were estimating 3-ish days when they hadn't even got unsigned code to work yet (a fairly substantial step in the JB process.)
P.S. Since the vulnerability for the 5.0.1 exploit has been patched in the 5.1 Beta, here's to realistically using the 4S on 5.0.1 for the next several months (maybe even after the iPhone 5 is launched). Cheers.
P.S.S. One can only hope the A6 processor won't be this difficult to crack. But it probably will be even worse.
Last edited:
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 know man i was jus pointing out you dont have to defend me as peoples minds are made up lol plus i dont care iff they think im lying
rick snagwell said:
I know man i was jus pointing out you dont have to defend me as peoples minds are made up lol plus i dont care iff they think im lying
Viperidae I have never seen the team if you are referring to the dev-team or chronic estimating anytime let alone 3 days.. We would all like to see the jailbreak now but unless we know how to do it ourselves not much we can say or do really.. also hard to understand how much work is involved. I don't think they are slacking.
Last edited:
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)
How was i called on it lol? Who even cares man Fact is i talk to Josh i have never boasted about it nor made a big deal of it! So just move on
TC25 said:
How was i called on it lol? Who even cares man Fact is i talk to Josh i have never boasted about it nor made a big deal of it! So just move on
So snowwhite007 talks to Josh let him brag or say or do what he wants. in the end it really doesn't matter.. not like we will get the jailbreak any faster.
not like we will get the jailbreak any faster.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 think he is referring to the overall situation with pod trying to be as friendly as possible. giving us an ETA a couple of weeks ago, before the post saying a "matter of days", saying that it should be in a week, then saying "a matter of days" has just gotten a lot of peoples hopes up.
Like I posted before, I don't think anyone is trying to mislead us, they are just running into problems. Let's just move forward and hope that this JB is released soon, so of we have any issues, we will still have the option of a restore to 5.0.1. At this point, I'm willing to sit on a JB 5.0.1 until the next JB is ready.
This isnt great news for the masses wanting JB because it's clearly becoming harder and harder with each new hardware/major iOS release. As I said before, the proof is in the pudding so to speak, we haven't had a unlock since 1.59.00 BB I don't remember but I think that it was the very first BB used on the iPhone 4. So seeing how none of the other BB have been unlocked, apparently the unlock portion doesn't get easier either. I'm just thankful there are a select few still out there trying to give us what we want. A jailbreak.
labman said:
I think he is referring to the overall situation with pod trying to be as friendly as possible. giving us an ETA a couple of weeks ago, before the post saying a "matter of days", saying that it should be in a week, then saying "a matter of days" has just gotten a lot of peoples hopes up.
Like I posted before, I don't think anyone is trying to mislead us, they are just running into problems. Let's just move forward and hope that this JB is released soon, so of we have any issues, we will still have the option of a restore to 5.0.1. At this point, I'm willing to sit on a JB 5.0.1 until the next JB is ready.
This isnt great news for the masses wanting JB because it's clearly becoming harder and harder with each new hardware/major iOS release. As I said before, the proof is in the pudding so to speak, we haven't had a unlock since 1.59.00 BB I don't remember but I think that it was the very first BB used on the iPhone 4. So seeing how none of the other BB have been unlocked, apparently the unlock portion doesn't get easier either. I'm just thankful there are a select few still out there trying to give us what we want. A jailbreak.
planetbeing is dev team not chronic I believe...
I'm glad these groups are back doing what they do...cuz both teams started to get lazy when Geohot and Comex did all the work...
I'd say we still have a week or so to go... who knows if they're using corona or some sort of variable to that, or perphaphs is a unique A5 thing...
I'm glad these groups are back doing what they do...cuz both teams started to get lazy when Geohot and Comex did all the work...
I'd say we still have a week or so to go... who knows if they're using corona or some sort of variable to that, or perphaphs is a unique A5 thing...
you are right on the 1st part I stand corrected. On the rest that's your opinion.
Actually I think new hardware every year actually improves the possibility of a JB, new hardware might come with new bugs.
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)
Not at all. Sorry. We could wish that but it's the opposite. The A6 may bring the beginning of the end for jailbreaking I'm thinking.
TSX said:
Not at all. Sorry. We could wish that but it's the opposite. The A6 may bring the beginning of the end for jailbreaking I'm thinking.
Wow, you talk to Josh!?!?!? Awesome, dude. So, you must know exactly when the jb will come out being so close to jb greatness like you are. That's right, you said mid-week. Just think, everyone, only 3 more days!