Ordering an iPhone 3GS? Make sure it’s available at your store first!
iPhone, iPhone 3G S | Doug | June 26, 2009 at 10:41 pmIf you’re ordering an iPhone 3GS you may want to check Apple’s iPhone 3GS Availability page which Apple recently added. It’s updated hourly!
Remember to bring the following items if you’re buying an iPhone 3GS:
Tags: iphone 3gs
- Credit card
- Social security number
- Valid, government-issued photo ID
- Your current wireless account number and password or PIN (if you’re already with AT&T)
-
iTunes Store Now Available in Mexico
-
Apple’s Find my iPhone Service Helps Owner Reclaim Stolen iPhone
-
Having troubles with Gmail?
-
New iPhone 4G coming to Verizon Wireless in 2010?
Tweet This
Digg This
Save to delicious
Stumble it
Loading ...
Is quickpwn releasing the jailbreak today or not I’d rather use it than redsnow
You can only use redsn0w or PwnageTool to jailbreak iPhone 3.0 (as these are the only tools that Dev-Team have released). See my Jailbreak iPhone OS 3.0 with redsn0w post for more details.
Is there a jailbreak available for the 3GS already?
No, there is no iPhone 3GS jailbreak yet.
According to the dev team, there never will be. ‘redsn0w is the new QuickPwn’
Bruce, Redsn0w is made by the same folks who made quickpwn, and it utilizes the pwnage tool. It even has the pineapple logo you are used to seeing when you jailbreak. If you are holding out just because you aren’t familiar with the name redsn0w, rest assured, it comes from the same people. The iPhone Dev team.
Thanks for that info steve, but I already knew that. I have already jailbroken my phone using redsnow but I find it kind of buggy.
Answer: It is replaced by redsn0w, the mobile site wasn’t updated. Thanks!
The bugginess has nothing at all to do with redsn0w. Remember that 3.x is not 2.x. There were a lot of API updates. Some were changed. A few were deprecated. Anything that relies on the old API code that has now changed will not work right. Anything that was written for 2.x and has not been tested on 3.0 may not work right. The deeper into the OS and hardware that the app works, the more likely it is to have problems.
I assume you weren’t around for the transition from 1.x to 2.x. Nothing at all that was written for 1.x worked on 2.x. *Nothing* Be glad most things work this time around.