Your favorite Apple, iPhone, iPad, iOS, Jailbreak, and Cydia site.
07-11-2008, 04:02 PM #161
this may be a stupid question, but I have been absent from the iPhone community for quite some time since mine was broken, but I'm getting my "new" (but still not 3G) iPhone from the US tomorrow.
however, my question is if "2.0 is unlocked and jailbroken" actually means "unlocked, jailbroken and activated" or not? because I read that you have to re-activate your iPhone while updating to 2.0, so just activating it with 1.1.4 running and then upgrading won't help me, will it?
07-11-2008, 09:10 PM #162
07-12-2008, 07:18 AM #163
At 23.18 AEST at blog.iphone-dev.org there is a new video there now if you want to see.
Last edited by louisb1966; 07-12-2008 at 08:15 AM.
07-12-2008, 09:22 AM #164
Will I be able to have my IBlacklist back? I really need that s...t =D
07-12-2008, 01:57 PM #165
Modeler / Animator
High 5 Productions
07-12-2008, 03:28 PM #166
i upgraded to 2.0 because im so impatient and now i cant downgrade ..my phone is locked ......help.....hello?
Last edited by Bstock1990; 07-12-2008 at 03:30 PM.
07-12-2008, 04:23 PM #167
07-12-2008, 04:33 PM #168
Two thumbs up you
07-12-2008, 04:35 PM #169
Downgrading does not work w/7.5 from 7.7. I have tried it on both Mac & Windows OS.
07-12-2008, 04:51 PM #170
so should I get the itunes 7.5 or 7.6
07-12-2008, 04:55 PM #171
when you upgrade to 2.0 then your baseband changes and if you want to down grade you have to downgrade the baseband, try searching for that i think this is the main issue over here
07-12-2008, 04:58 PM #172
I'm twiddling my thumbs waiting to upgrade to 2.0 so I can jailbreak. Even if I do however..... I'm limited to the app store until previous programs become 2.0 compatible so I dunno if it's even worth it.Screw #Winning, I'm #Juanning
iMac 27" i5 quad 2.8Ghz (1TB), MacBook Pro 17" 2.6, iPhone 4s
07-12-2008, 04:58 PM #173
BootNeuter 2.0 which is the lastest on video of dev team i think that will help you to load 1.1.4
07-12-2008, 05:16 PM #174
i appreciate everyones help but the phone is stuck in recovery mode (itunes logo and usb cable logo) and i cant even shut my phone off!!!!
well im going to try to restore 2.0 so its in emergency mode and then re instal itunes in 7.6 and try to do a system restore??
Last edited by Bstock1990; 07-12-2008 at 05:16 PM. Reason: Automerged Doublepost
07-12-2008, 05:41 PM #175
hell yeah holmes, i ken't believe!
07-12-2008, 06:16 PM #176
hopefully it will be out on Monday
07-12-2008, 06:36 PM #177
The Following User Says Thank You to mixi92 For This Useful Post:
07-13-2008, 05:14 AM #178
i love this site. endless hours of reading the same crap over and over. you guys are so impatient.
07-13-2008, 05:23 AM #179
The Following User Says Thank You to ronsantis For This Useful Post:
07-13-2008, 07:06 AM #180
The Dev Team Posted this about 15 minutes ago on their blog
Rush, rush, rush....
Over the last year we’ve discovered some interesting things about the software used in the iPhone. These “hacks” , “exploits” *and “techniques”, or whatever you want to call them, are valuable*- not only from a financial perspective (so scummy people can sell unlocking software) but also from a strategic point of view. Think of it like a game of poker, showing your hand too early would certainly make you lose “the game”.*
The majority of iPhone users are not technical - they want an easy, one-stop, simple application that will allow them to quickly and painlessly unlock their phone. If we were to release a crummy command-line based tool that does the immediate job that everyone is screaming for, we’d only end up in the following situation:
1) The technique is released to the world and people use this technique to quickly create GUI apps that they charge*cash-money for, or re-release something hacky and horrible that bricks lots of devices, or for example disables the WiFi that then causes more stress that ultimately comes back to us
2) The technique is exposed to the vendor, allowing them to locate and repair the security hole. Sometimes these security holes span product versions, for example: between the first generation and second generation iPhone. In such a case releasing the knowledge in the middle of the product development cycle is pointless and risks the “usefulness” of the technique - especially if there are existing hacks/techniques that work just fine.
The iPhone DevTeam is comprised of a group of people who work together over IRC from various parts of the world. This distributed method of working happens 24 hours a day with people performing tasks in the time that best suits their time-zones. It is a completely self-managing, self-regulating and member-funded organization. Most of us have never met face-to-face and we rarely know real names - in fact, we would more than likely not recognize each other if we walk past one another on the street. Despite this we follow a strict “hacker code”: ground rules by which we all abide.*
Perhaps the foremost of these rules is management of knowledge. We keep*certain*information private, restricted to members of the team only (to help with points 1 and 2 above), and members are entrusted to make sure this secrecy is consistently enforced. This makes*the team. Only when there is a majority vote from the team do we make any announcement or release.*
So now we come onto Geohot, the self appointed media frontman for last year’s iPhone hacks. Geohot actually worked with us a month or so before the media-circus that he led. Geohot is certainly a bright guy, but he couldn’t abide by rules that I described in the last paragraph and because of this he was asked to leave the team. Of course like any hacker Geohot continued on for his goal.
Using some of our techniques and tools (and some of his) and using his own brain power (and that of an unnamed Russian) he was able to release his hardware hack and demonstrate the first unlocked iPhone to the world, he has also demonstrated other things during the last year and some of those releases have helped us with our work.
We thought that Geohot would have matured somewhat in the last year, but this clearly isn’t the case, as sadly one of the team members has leaked a copy of our exploit to Geohot and he is now using this to provoke us into making an early release :-(
So finally, just in case some of you were wondering, we’re not sitting on this tool because we’re full of ourselves or up our own asses. We’re not sitting on it cause we like to see you writhe. We are testing it to make sure it’s as glitch-free as we can make it. We want to avoid releasing something that turns expensive phones into pretty looking paperweights. Don’t you agree it’s worth the wait?
If others want to feel like they’re in control by posting all-knowing entries on their blogs, we can’t stop that, but the new PwnageTool will be released when it’s ready, and not a moment later.*