Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Pod2g no longer working/helping Chronic Dev Team

maturola

maturola

macrumors 68040
Original poster
Oct 29, 2007
3,863
3
Atlanta, GA
As we seen on pretty much every Jailbreake process, some arguments and disagrements have surfaced over at Chronic Dev Team and Pod2G the finder of "SHAtter" (the current exploit for 4.1 bootrom) is not longer part of the Chronic Dev Team.

Ealier today:

Pod2g said:
From now on, I'm not affiliated with chronic dev team anymore. I'm now working independently
Click to expand...

http://twitter.com/pod2g/status/25033535288

This shouldn't affect development and release of the JB since he shared the details of the exploits with all DeV teams, but it is sad to see him part away.
 
It sucks, but it isn't as bad as what people might think. He even said in his twitter response that he develops exploits not the applications.
 
He's not quitting he's jut saying he's an exploit maker

“@pod2g: To clarify: I'm an exploit maker, not a jailbreak tool developper. SHAtter is my 3rd bootrom exploit (24Kpwn was a team effort tho).”
Click to expand...
 
You have to consider they are trying to make the JB as easy as possible for everyone. Take a look at the steps involved with rooting an Android phone. They are out fast, but not very user friendly. You also have to look at it like this--why release an exploit now when 4.2 will be out in about 2 months.
 
Ikyo said:
You have to consider they are trying to make the JB as easy as possible for everyone. Take a look at the steps involved with rooting an Android phone. They are out fast, but not very user friendly. You also have to look at it like this--why release an exploit now when 4.2 will be out in about 2 months.
Click to expand...
I was under the impression that since this is probably going to be a bootrom (?) jb, that it was independent of the iOS release?
 
Ikyo said:
You also have to look at it like this--why release an exploit now when 4.2 will be out in about 2 months.
Click to expand...

And so the never-ending cycle of never releasing another JB begins...!

4.2 may have a bug when it's released, so better to wait until 4.2.1. But then 4.3 will only be a few months after that, and have more features, so maybe they should wait for that too?

Reminds me of all the questions on here about "should i buy iDevice x now, or wait for iDevice x+1" - no point bothering if you're never going to buy because you're afraid that it will someday be out of date.
 
Scuby said:
And so the never-ending cycle of never releasing another JB begins...!

4.2 may have a bug when it's released, so better to wait until 4.2.1. But then 4.3 will only be a few months after that, and have more features, so maybe they should wait for that too?

Reminds me of all the questions on here about "should i buy iDevice x now, or wait for iDevice x+1" - no point bothering if you're never going to buy because you're afraid that it will someday be out of date.
Click to expand...

Very true, if we keep waiting forget it :D
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back