Pocket.info - Mobile 2.0
Mobile Web 2.0 News, Views, and Developer Community
Pocket.info - Mobile 2.0 » All Tags » OS X » 1.1.1 » Apple (RSS)


Browse by Tags

  • 1.1.2 jailbreak software released

    Filed under: Handsets , ATT , EDGE , Apple , OS X The kind folks at Conceited Software / TouchFree have just dropped their 1.1.2 jailbreak GUI on the freedom-lovin' iPhone world. According to Erica at TUAW , the OS X software siphons data from your downgraded (or pre-existing) 1.1.1 iPod touch or iPhone, upgrades it with the Jailbreak, installs Installer.app and SSH.app, and then ups the whole shebang to your device. As mentioned, you'll need to have 1.1.1 on your system (if you've upgraded or purchased a device with 1.1.2 installed), and this won't fly on units that have been "hactivated" (i.e., it only works with iTunes-activated devices). Hit the read link and learn all about sticking it to Apple... proper-like. [Thanks to everyone who sent this in] Read | Permalink | Email this | Linking Blogs | Comments

  • Apple hit with class-action antitrust lawsuit over bricked iPhones

    Filed under: Handsets , ATT , EDGE , Apple , OS X Apple has obviously made some enemies over this whole iPhone firmware situation, and clearly not everyone wants to follow the straight-and-narrow when it comes to the company's factory-limited and locked device . Now, at least one California resident named Timothy Smith has decided to bring the fight to the Cupertino monolith's doorstep -- and he showed up with lawyers . According to papers filed last week, the angry iPhone owner is suing Apple in hopes of barring the company from selling locked phones, and forcing the Mac-maker to provide warranty service for customers even if they've bricked their phones via third-party software -- though there seems to be no definitive evidence that Apple's update is the source of the brickings. The suit claims that, "Apple forced plaintiff and the class members to pay substantially more for the iPhone and cell phone service than they would have paid in a competitive marketplace either for the iPhone or for AT&T's cell phone service," and that the company, "Acted in defiance and without sufficient consideration of consumers' rights to unlock their iPhones because it knew that the probable result of its update would be to render unlocked iPhones inoperable." The lawyers in the case have set up a website where owners can join in on the suit -- so if you're feeling slighted , maybe they can help. Read | Permalink | Email this | Linking Blogs | Comments

  • iPhone 1.1.1 to 1.0.2 downgrade instructions released!

    Filed under: Software , Apple , OS X Well would you look at that, instructions are now available for downgrading your iPhone from 1.1.1 to 1.0.2. It won't downgrade your baseband, meaning so far you can't re-unlock an iPhone that's been 1.1.1-ified, but it's still 1.0.2 in all its third-party application glory. The iPhone Dev Team folks are working on a way to downgrade the new firmware to let people unlock their phones again, but for now AT&T users sitting pretty, and non-AT&T folks can at least do the WiFi thing. There's a video tutorial after the break. [Thanks to everyone who sent this in] Read - iPhone Dev Wiki instructions Read - Hackint0sh thread where the magic happened Permalink | Email this | Linking Blogs | Comments

  • iPhone 1.1.1 "bug" unleashes music over Bluetooth

    Filed under: Apple , OS X The iPhone 1.1.1 update has a hidden little surprise for y'all: Bluetooth audio streaming is now available off of your iPhone for whatever you darn please, meaning you can finally listen to music from the phone wirelessly. Oddly enough, this "function" has been unleashed by a Visual Voicemail bug that leaves Bluetooth audio on even after you've left the Voicemail interface. Of course, it's only mono audio, and the audio keeps playing out of your built-in speaker -- if you plug in headphones to cut off the speaker you'll lose Bluetooth streaming as well -- but it's nice to see Apple forking over some "should have been there in the first place" functionality accidentally to go along with all that stuff of the same ilk 1 .1.1 took away from us . Read | Permalink | Email this | Linking Blogs | Comments
    Filed under: , , , , ,

  • iPhone update: facts and fiction

    Filed under: Features , ATT , Apple , OS X If you haven't already bitten the bullet and taken your unlocked iPhone down that scariest of paths, the 1.1.1 update , we're here to sort out a bit of the hearsay from the actual and fairly inconvenient truth. Even if you have already updated, or never even unlocked or jailbroke your iPhone to begin with, there's still a lot to learn, so let's dive in, shall we? Most people with a jailbroken iPhone will end up with a "factory-fresh" iPhone after the 1.1.1 firmware update. Your mileage may vary, and isolated incidents of bricking have occurred, but most people are just going to have a 3rd party-free, AT&T-only iPhone in their pocket when the day is through, and bricking seems to be just as common for a virgin iPhones as for jailbroken ones. As for when we'll have full use of the iPhone again is unclear, but TUAW's Erica Sadun says " don't expect a jailbreak anytime soon ," which doesn't seem promising. Apparently the security is going to be a whole lot harder to crack this time around. As for unlocked iPhones, you should probably hold off for the time being. The most serious problems we're hearing so far relate to iPhone Dev Team's anySIM unlock, which has left some iPhones "bricked" with an "Incorrect SIM" error message (seen above). That's not to say a workaround won't be found in the future, but for now anySIM users should certainly stay away from 1.1.1. SuperSIM and TurboSIM users are also advised not to update, but we have less solid info about that. iPhoneSIMfree users seem to be in fine shape as long as they're rocking an AT&T SIM card -- though that does seem to defeat the purpose of an unlocked iPhone in the first place. Please let us know about your personal experience with the update on an unlocked phone so we can get a clearer picture of the exact damage, but it's probably best for you to restore your phone to...
Copyright 2008 - Pocket.info