Airtel and Vodafone have comfired the prices for the iPhone 3G in India:
8 GB iPhone 3G for Rs 31,000,- (locked with contract)
16 GB iPhone 3G for 36,000,- (locked with contract)
The iPhone will be locked to one network only, meaning if you buy from Airtel you will only be able to use with Airtel.
With www.RebelSimCard.com you can unlock your iPhone 3G without modifying the original firmware and use with any Network worldwide. This is especially handy when you travel to another country and do not wish to pay the high roaming charges.
For more details visit:
Airtel iPhone 3G page
Vodafone iPhone 3G page
www.iPhoneNirvana.net
Thursday, August 21, 2008
Friday, August 15, 2008
Official launch of iPhone 3G in India
Apple has announced that Airtel and Vodafone would bring the iPhone 3G to India. For all those whom we could not supply with an iPhone the time of waiting has come to an end. Although Airtel and Vodafone will sell a locked version, there are already methods to unlock the Phone without modifying the original fimware (Check out http://rebelsimcard.com for details). Pricing details are not available. According to some source the 8GB iPhone 3G should sell for 31000 Rs (37000 Rs for 16 GB version) which would seem quite overpriced compared to prices in other countries. Apple has announced that the iPhone 3G would not sell for more than 199 US for 8GB iPhone 3G and 299 US for 16 GB iPhone 3G. We are still waiting for a confirmation from both Airtel and Vodafone.
www.iphonenirvana.net
www.iphonenirvana.net
Sunday, October 28, 2007
2 Per Person iPhone Limit, No Cash Accepted
Apple has taken new measures to discourage iPhone resellers. Whereas they used to enforce a five unit per customer limit, they knocked it all the way down to two per person. This probably won't be a big problem for most of you. What might be a problem is that they are now no longer accepting cash for purchases of iPhones, so if you have bad credit or lack a debit card, you're out of luck.
“Customer response to the iPhone has been off the charts, and limiting iPhone sales to two per customer helps us ensure that there are enough iPhones for people who are shopping for themselves or buying a gift,” Ms. Kerris said. “We’re requiring a credit or debit card for payment to discourage unauthorized resellers.”
“Customer response to the iPhone has been off the charts, and limiting iPhone sales to two per customer helps us ensure that there are enough iPhones for people who are shopping for themselves or buying a gift,” Ms. Kerris said. “We’re requiring a credit or debit card for payment to discourage unauthorized resellers.”
Tuesday, October 23, 2007
Gizmodo: 250,000 Unlocked iPhones Have Been Sold
Apple just stated in their earnings call that out of 1.4 million iPhones sold since launch, 250,000 are unlocked. They know this from subtracting the number of iPhones activated on AT&T from the number of iPhones sold total—which is 250k. That's a farmhouse load of unlocked phones, which match up with the 500,000 downloads of AnySIM 1.0 unlocker we've seen before. Those are official numbers from the iPhone Dev Team, which make sense when you factor in lookeyloos who download it and people who unlock even with an active AT&T plan.
Saturday, October 20, 2007
iPhone Stress testing
Ever since we did our first iPod nano review with stress tests all those years ago, we have gotten a lot of requests for durability tests on other products. But no product since then has received nearly as many requests... until the iPhone. Readers have written from far and wide asking us to abuse our iPhones as badly as they do on a daily basis, because no one wants to plunk down $500-$600 for a device that (some believe) looks like it could scratch or break if the winds change.
Just a couple of weeks before the iPhone launched, Apple announced that it had pulled a switcheroo with the screen covering from the clear plastic used on most iPods to a scratch-resistant glass. While viewed largely as a marketing move that was planned all along (Apple could not have made such a decision so close to launch time without severely pushing back production), the announcement did serve to soothe the nerves of many geeks who were worried about having to wrap their iPhones in silk-stitched bubble wrap in order to protect them from the world. But still, the questions kept coming in: "How durable will it be? Will it be able to survive the crap that I put my phones through?"
And so here you have it. You may have seen a few other reviews that attempted to "test" the durability of the iPhone, but none really went so far as to answer the questions that our readers had.
First, let us preface this by saying that, as many of you know, one of the official Ars Technica iPhones was put through a wedding during the weekend immediately after purchase. This involved at least two full days of jostling the device around, naked with no protection, in various bags and purses with things like keys, cameras, laptops, other phones, jewelry, pins, and more. And of course, lots and lots of showing off. During this time, it was dropped from standing height onto linoleum flooring twice during the reception, both by Clint and by another member of the wedding party. Neither of those drops caused any harm to the iPhone whatsoever, and the device came out from the weekend as if it were still brand new.
Throughout the week, we continued to be not-so-careful whatsoever with our iPhone. We sat down with the iPhone in various pockets (including the back pocket) with absolutely nothing to report afterwards. It was crammed into tight-fitting pockets with keys and other knickknacks, laptop bags with other electronic equipment and tools, purses with cameras and change and various metal objects... and we could not get the screen to scratch. We were beginning to lose hope that the screen could be scratched at all; good news for you all, but bad news for us.
We had to step it up a notch when we entered our formal testing phase, and so we placed the iPhone into a plastic bag with two sets of keys, a pocket knife, and a handful of rocks. Ten minutes of shaking, rubbing, and overall mashing resulted in almost nothing. Almost. One tiny scratch showed up in a somewhat inconspicuous place on the glass. In fact, it was very hard to photograph.
We wanted to see whether we could get it to scratch up a bit more, and so we threw it twice down the length of a sidewalk, face down. Surely skidding on the sidewalk would scratch the screen up at least a little bit, right? Sort of. We were able to generate a few very light scratches after skidding it down the sidewalk twice, none of which were visible while the LCD was on, and most of which looked more like streaks that could be wiped off than actual scratches.
We did, however, manage to create a tiny crack in the lower, right-hand corner of the glass next to the home button (out of the way of the screen itself) upon the second throw.
We then proceeded to drop the iPhone onto the concrete sidewalk three times. This essentially brought the iPhone drops from this height to about five times if you include the two drops at the wedding. None of these three subsequent drops caused any further damage to the iPhone's screen or glass covering, although it did begin to rough up the sides a bit.
Naturally, if you drop an iPhone anywhere in public—on the street, in an office, etc.—you run the risk of someone stepping on the phone. We've received numerous reader e-mails saying that their phones, iPods, and other gadgets had been stepped on with varying degrees of survivability. This happens enough that we decided to add it to the tests, so we placed the iPhone face down on the sidewalk and had a 225-pound man (Mr. Clint Ecker) step on it while walking by.
We heard a crack, but we weren't sure what had happened until we checked out the damage. A large spider crack had appeared in the lower right of the glass, close to the Safari button on the home screen. However, while ugly, the crack was in the glass and not the LCD screen itself, so it therefore did not impede our use of the iPhone at all. We could still make and receive calls, make and receive SMSes, send and receive e-mail, and listen to songs on the iPod.
The crack was much more noticeable in outdoor light compared to indoors:
...and less noticeable when the screen was on.
Since the iPhone had fared so well with other drop tests, we were curious as to how it would fare when knocked off of a third-floor balcony. When we did this test on the second-generation iPod shuffle, it practically floated down and landed on the ground like a leaf; such would not be the case with the iPhone.
The drop from the third-floor balcony, surprisingly, did not yield any further physical damage to the glass or the screen that we could see. However, it did kill the iPhone's touchscreen, rendering it mostly useless. At least it still has that pretty rose background, right?
But we said "mostly" useless. Despite being put through a world of hurt and now with a completely nonfunctional touchscreen, the iPhone was still able to receive phone calls. How were we able to answer the calls if you can't touch anything on the screen to answer them, you ask? Via those annoying-yet-handy iPhone headphones with the clicky switch, that's how. Call quality when answering a phone call after this much abuse suffered, however. It was very tinny-sounding (this was not the case when we tested phone calls with the headphones before), and we thought it sounded like the caller might have had us on speakerphone (he did not). Also surprisingly, we were able to listen to a random selection of music on the iPhone through the use of the headphones' clicky button, and the now non-touchscreen LCD happily displayed the album art for it. Even the volume control buttons on the side of the iPhone still worked. So if you've always wanted the equivalent of a heavy iPod shuffle with a giant screen to display album art and the ability to receive phone calls, the iPhone still served its purpose.
We knew that the iPhone was coming to the end of the road, and so we performed the most-requested and most-sure-to-kill-the-iPhone test of all: the toilet test. If we had a dime for every single story we've heard over the years about people who have somehow managed to drop their phones into the toilet, we wouldn't be writing this review right now. If you don't believe this, just ask around among your friends and coworkers; there is sure to be at least a few stories of people's phones coming to an untimely meeting with our dear friend H2O.
But not everyone's phones get fried when they get dropped into the toilet (or some other body of water). Because of the ability to take out the battery on most cell phones, some people (not all) have been able to save their phones from certain death by removing it from the water, taking out the battery immediately, and letting everything dry for several days. This was the case with a good friend of ours who was pushed into a fountain with his cell phone, a Motorola SLVR, just a few weeks ago (long story). He thought the phone was dead, but he let it dry out for several days with the battery out and found that he was still able to make and receive calls on it.
We put on whatever random song that the iPhone chose for us (something by good old Justin Timberlake) and said what we believed to be our last goodbyes to the iPhone. Then it went in the toilet.
About seven seconds later, the screen started flickering. Nine seconds after that, the music stopped playing. We took the iPhone out, let the excess water drain, did not remove the battery (since the battery is not user-removable) and set it out on the back porch to dry out. But just as we suspected, the iPhone was fried; there was no reviving it.
Some will argue that if we had removed the phone from the water earlier, it might have survived. That may have been true temporarily, but due to the battery being non-removable, we believe it would have died regardless. Water was able to seep into every crevice of the iPhone and would have made its way to the battery eventually, even if we had removed it from the water earlier.
If you're interested in seeing live video of the stress-testing process, check out our short film with a very touching ending.
We conclude that the iPhone is, for nearly all everyday uses, pretty darn durable and practically impossible to scratch. However, as with most electronics—particularly those with large screens—you should at least keep an eye out for hitting the screen at funny angles onto things like table corners and the like. Although even if you did that, the LCD itself would likely not crack, and you would not lose any real functionality, but nobody wants ugly spider cracks in their otherwise-beautiful glass, right?
Source: http://arstechnica.com/reviews/hardware/iphone-review.ars/13
Just a couple of weeks before the iPhone launched, Apple announced that it had pulled a switcheroo with the screen covering from the clear plastic used on most iPods to a scratch-resistant glass. While viewed largely as a marketing move that was planned all along (Apple could not have made such a decision so close to launch time without severely pushing back production), the announcement did serve to soothe the nerves of many geeks who were worried about having to wrap their iPhones in silk-stitched bubble wrap in order to protect them from the world. But still, the questions kept coming in: "How durable will it be? Will it be able to survive the crap that I put my phones through?"
And so here you have it. You may have seen a few other reviews that attempted to "test" the durability of the iPhone, but none really went so far as to answer the questions that our readers had.
First, let us preface this by saying that, as many of you know, one of the official Ars Technica iPhones was put through a wedding during the weekend immediately after purchase. This involved at least two full days of jostling the device around, naked with no protection, in various bags and purses with things like keys, cameras, laptops, other phones, jewelry, pins, and more. And of course, lots and lots of showing off. During this time, it was dropped from standing height onto linoleum flooring twice during the reception, both by Clint and by another member of the wedding party. Neither of those drops caused any harm to the iPhone whatsoever, and the device came out from the weekend as if it were still brand new.
Throughout the week, we continued to be not-so-careful whatsoever with our iPhone. We sat down with the iPhone in various pockets (including the back pocket) with absolutely nothing to report afterwards. It was crammed into tight-fitting pockets with keys and other knickknacks, laptop bags with other electronic equipment and tools, purses with cameras and change and various metal objects... and we could not get the screen to scratch. We were beginning to lose hope that the screen could be scratched at all; good news for you all, but bad news for us.
We had to step it up a notch when we entered our formal testing phase, and so we placed the iPhone into a plastic bag with two sets of keys, a pocket knife, and a handful of rocks. Ten minutes of shaking, rubbing, and overall mashing resulted in almost nothing. Almost. One tiny scratch showed up in a somewhat inconspicuous place on the glass. In fact, it was very hard to photograph.
We wanted to see whether we could get it to scratch up a bit more, and so we threw it twice down the length of a sidewalk, face down. Surely skidding on the sidewalk would scratch the screen up at least a little bit, right? Sort of. We were able to generate a few very light scratches after skidding it down the sidewalk twice, none of which were visible while the LCD was on, and most of which looked more like streaks that could be wiped off than actual scratches.
We did, however, manage to create a tiny crack in the lower, right-hand corner of the glass next to the home button (out of the way of the screen itself) upon the second throw.
We then proceeded to drop the iPhone onto the concrete sidewalk three times. This essentially brought the iPhone drops from this height to about five times if you include the two drops at the wedding. None of these three subsequent drops caused any further damage to the iPhone's screen or glass covering, although it did begin to rough up the sides a bit.
Naturally, if you drop an iPhone anywhere in public—on the street, in an office, etc.—you run the risk of someone stepping on the phone. We've received numerous reader e-mails saying that their phones, iPods, and other gadgets had been stepped on with varying degrees of survivability. This happens enough that we decided to add it to the tests, so we placed the iPhone face down on the sidewalk and had a 225-pound man (Mr. Clint Ecker) step on it while walking by.
We heard a crack, but we weren't sure what had happened until we checked out the damage. A large spider crack had appeared in the lower right of the glass, close to the Safari button on the home screen. However, while ugly, the crack was in the glass and not the LCD screen itself, so it therefore did not impede our use of the iPhone at all. We could still make and receive calls, make and receive SMSes, send and receive e-mail, and listen to songs on the iPod.
The crack was much more noticeable in outdoor light compared to indoors:
...and less noticeable when the screen was on.
Since the iPhone had fared so well with other drop tests, we were curious as to how it would fare when knocked off of a third-floor balcony. When we did this test on the second-generation iPod shuffle, it practically floated down and landed on the ground like a leaf; such would not be the case with the iPhone.
The drop from the third-floor balcony, surprisingly, did not yield any further physical damage to the glass or the screen that we could see. However, it did kill the iPhone's touchscreen, rendering it mostly useless. At least it still has that pretty rose background, right?
But we said "mostly" useless. Despite being put through a world of hurt and now with a completely nonfunctional touchscreen, the iPhone was still able to receive phone calls. How were we able to answer the calls if you can't touch anything on the screen to answer them, you ask? Via those annoying-yet-handy iPhone headphones with the clicky switch, that's how. Call quality when answering a phone call after this much abuse suffered, however. It was very tinny-sounding (this was not the case when we tested phone calls with the headphones before), and we thought it sounded like the caller might have had us on speakerphone (he did not). Also surprisingly, we were able to listen to a random selection of music on the iPhone through the use of the headphones' clicky button, and the now non-touchscreen LCD happily displayed the album art for it. Even the volume control buttons on the side of the iPhone still worked. So if you've always wanted the equivalent of a heavy iPod shuffle with a giant screen to display album art and the ability to receive phone calls, the iPhone still served its purpose.
We knew that the iPhone was coming to the end of the road, and so we performed the most-requested and most-sure-to-kill-the-iPhone test of all: the toilet test. If we had a dime for every single story we've heard over the years about people who have somehow managed to drop their phones into the toilet, we wouldn't be writing this review right now. If you don't believe this, just ask around among your friends and coworkers; there is sure to be at least a few stories of people's phones coming to an untimely meeting with our dear friend H2O.
But not everyone's phones get fried when they get dropped into the toilet (or some other body of water). Because of the ability to take out the battery on most cell phones, some people (not all) have been able to save their phones from certain death by removing it from the water, taking out the battery immediately, and letting everything dry for several days. This was the case with a good friend of ours who was pushed into a fountain with his cell phone, a Motorola SLVR, just a few weeks ago (long story). He thought the phone was dead, but he let it dry out for several days with the battery out and found that he was still able to make and receive calls on it.
We put on whatever random song that the iPhone chose for us (something by good old Justin Timberlake) and said what we believed to be our last goodbyes to the iPhone. Then it went in the toilet.
About seven seconds later, the screen started flickering. Nine seconds after that, the music stopped playing. We took the iPhone out, let the excess water drain, did not remove the battery (since the battery is not user-removable) and set it out on the back porch to dry out. But just as we suspected, the iPhone was fried; there was no reviving it.
Some will argue that if we had removed the phone from the water earlier, it might have survived. That may have been true temporarily, but due to the battery being non-removable, we believe it would have died regardless. Water was able to seep into every crevice of the iPhone and would have made its way to the battery eventually, even if we had removed it from the water earlier.
If you're interested in seeing live video of the stress-testing process, check out our short film with a very touching ending.
We conclude that the iPhone is, for nearly all everyday uses, pretty darn durable and practically impossible to scratch. However, as with most electronics—particularly those with large screens—you should at least keep an eye out for hitting the screen at funny angles onto things like table corners and the like. Although even if you did that, the LCD itself would likely not crack, and you would not lose any real functionality, but nobody wants ugly spider cracks in their otherwise-beautiful glass, right?
Source: http://arstechnica.com/reviews/hardware/iphone-review.ars/13
Friday, October 19, 2007
Disabling SSH, Increasing Battery life
Yesterday we were browsing the web to find some tricks on how to increase battery life. There are some well known tricks like:
-disabling Wifi if not required
-setting your Email to check once every hour instead of once every 15 minutes
-setting Auto-lock to 1 minute-
-setting the brightness of the Screen to around 30% and using Auto brightness etc.
Basically these settings will improve battery performance on the iPhone and we are ok with it considering all the things the iPhone does for us, but still we thought that there might be something else to improve battery performance on the iPhone.
So we came accross 2 articles, one was intended for iPhone users with Firmware version 1.1.1, it suggested to restore the iPhone. The other article was related to iPhones with Firmware 1.0.2. Since most of you are on Firmware 1.0.2 we will be focusing more on that.
While unlocking the iPhone it was required to install SSH on it to be able to install third party Applications. What most of us did not realize was that SSH is one hidden little battery drainer. This almost went unnoticed until Michael Johnston from iPhoneAlley "identified the culprit". Here is what Michael found out:
------------------beginning of transmission------------------
If you are still on firmware 1.0.2 and have installed those cool third-party iPhone applications but are observing reduced battery life then here is some good news. Michael Johnston over at iPhoneAlley has identified the culprit (application) which could be draining your iPhone's battery life.
The iPhone application which could be causing the issue is OpenSSH in case you have it installed on your iPhone, the tool which allows remote login to your iPhone from a computer. Michael also has a logical explanation for it, he says "The problem is, SSH requires that a listener called SSHD constantly runs, waiting for a remote login attempt. This in turn drains your battery."
Hmm, so now that you know the culprit your first reaction would be to uninstall it from your iPhone, maybe that is not required as there is a cleaner solution to this problem. The solution is to disable SSH which can be achieve using a simple tool called Services. Assuming that you have already installed Installer.app and OpenSSH on your iPhone all you need to do is download Community Sources in case not already done, then under Utilities in Installer.app, install Services. After you have waited for the iPhone to reload the homescreen and see the Services icon tap to launch Services and simply toggle SSH off.
Once SSH is turned off using the above instructions you should no longer observe the reduced battery life.
---------------------end of transmission---------------------
This might be your first contact with third party Application installations, so we will try to guide you on how to do it. This will be some pre-training for those who will want to upgrade their firmware in future.
Note: This process is only recommended for Users who feel comfortable using a Computer. Your iPhone will need to be connected to the Internet via WIFI.
1. Community Sources is already installed on your iPhone (on those which we shipped at least) so let's move one to the next step
2. If you are on a PC download ibrickr (http://www.iphone-hacks.com/downloads/file/37), MAC users download INdependence (http://independence.googlecode.com/files/iNdependence_v1.2.4.dmg)
3. Unpack the respective .zip files
4. Connect your iPhone via USB to your Computer
5. Quit iTunes & iTunes helper applications
6. Launch iBrickr on your PC or INdependence on your MAC
7. Install Installer.app (your PC will also need to be connected to the Internet for this to work)
iBrickr (PC):
If you use iBrickr click on Applications and browse to Installer.app, install Installer.app on your iPhone. This will download the file from the net and place it onto your iPhone.
INdependence (MAC):
If you use INdependence First download Installer.zip from www.iphonenirvana.net/Installer.zip and unpack it. Then from within INdependence browse to Applications/ Users and click add, browse to the unpacked Installer.app and add it, it will ask you to enter your IP address and password. To get your IP address on your iPhone go to Settings/Wifi/click on the blue arrow next to your Network and your IP address will be displayed. Enter it into Independence and put the password: dottie
8. Now the application should be installed on the iPhone, disconnect it from the Computer and restart your iPhone.
9. Start it up, and installer Application should be there on your Home-screen. Tap on the Installer Icon, it will start to refresh the listings (if you have a slow Internet connection this could take some time).
10. Browse to Services under Utilities, and install it.
11. Restart your Phone. Services should now be displayed on the Home-screen. Tap on it and disable SSH. You're done
Troubleshooting: If you have too many Applications on your Home Screen you might not see Services, for this you need to install Launcher application which will enable you to access all your third party Applications.
Now that you have Installer.app on your iPhone you can install more Application.
Tip: We recommend to uninstall TextEdit application from your iPhone, because it allows you to rename the /root folder or /var folder, which could cause damage to the iPhone software. We had one instance of that already. If that happens to you the iPhone will need to be restored to it's factory settings using the 1.0.2 Firmware restore file.
-disabling Wifi if not required
-setting your Email to check once every hour instead of once every 15 minutes
-setting Auto-lock to 1 minute-
-setting the brightness of the Screen to around 30% and using Auto brightness etc.
Basically these settings will improve battery performance on the iPhone and we are ok with it considering all the things the iPhone does for us, but still we thought that there might be something else to improve battery performance on the iPhone.
So we came accross 2 articles, one was intended for iPhone users with Firmware version 1.1.1, it suggested to restore the iPhone. The other article was related to iPhones with Firmware 1.0.2. Since most of you are on Firmware 1.0.2 we will be focusing more on that.
While unlocking the iPhone it was required to install SSH on it to be able to install third party Applications. What most of us did not realize was that SSH is one hidden little battery drainer. This almost went unnoticed until Michael Johnston from iPhoneAlley "identified the culprit". Here is what Michael found out:
------------------beginning of transmission------------------
If you are still on firmware 1.0.2 and have installed those cool third-party iPhone applications but are observing reduced battery life then here is some good news. Michael Johnston over at iPhoneAlley has identified the culprit (application) which could be draining your iPhone's battery life.The iPhone application which could be causing the issue is OpenSSH in case you have it installed on your iPhone, the tool which allows remote login to your iPhone from a computer. Michael also has a logical explanation for it, he says "The problem is, SSH requires that a listener called SSHD constantly runs, waiting for a remote login attempt. This in turn drains your battery."
Hmm, so now that you know the culprit your first reaction would be to uninstall it from your iPhone, maybe that is not required as there is a cleaner solution to this problem. The solution is to disable SSH which can be achieve using a simple tool called Services. Assuming that you have already installed Installer.app and OpenSSH on your iPhone all you need to do is download Community Sources in case not already done, then under Utilities in Installer.app, install Services. After you have waited for the iPhone to reload the homescreen and see the Services icon tap to launch Services and simply toggle SSH off.
Once SSH is turned off using the above instructions you should no longer observe the reduced battery life.
---------------------end of transmission---------------------
This might be your first contact with third party Application installations, so we will try to guide you on how to do it. This will be some pre-training for those who will want to upgrade their firmware in future.
Note: This process is only recommended for Users who feel comfortable using a Computer. Your iPhone will need to be connected to the Internet via WIFI.
1. Community Sources is already installed on your iPhone (on those which we shipped at least) so let's move one to the next step2. If you are on a PC download ibrickr (http://www.iphone-hacks.com/downloads/file/37), MAC users download INdependence (http://independence.googlecode.com/files/iNdependence_v1.2.4.dmg)
3. Unpack the respective .zip files
4. Connect your iPhone via USB to your Computer
5. Quit iTunes & iTunes helper applications
6. Launch iBrickr on your PC or INdependence on your MAC
7. Install Installer.app (your PC will also need to be connected to the Internet for this to work)
iBrickr (PC):
If you use iBrickr click on Applications and browse to Installer.app, install Installer.app on your iPhone. This will download the file from the net and place it onto your iPhone.
INdependence (MAC):
If you use INdependence First download Installer.zip from www.iphonenirvana.net/Installer.zip and unpack it. Then from within INdependence browse to Applications/ Users and click add, browse to the unpacked Installer.app and add it, it will ask you to enter your IP address and password. To get your IP address on your iPhone go to Settings/Wifi/click on the blue arrow next to your Network and your IP address will be displayed. Enter it into Independence and put the password: dottie
8. Now the application should be installed on the iPhone, disconnect it from the Computer and restart your iPhone.
9. Start it up, and installer Application should be there on your Home-screen. Tap on the Installer Icon, it will start to refresh the listings (if you have a slow Internet connection this could take some time).
10. Browse to Services under Utilities, and install it.
11. Restart your Phone. Services should now be displayed on the Home-screen. Tap on it and disable SSH. You're done
Troubleshooting: If you have too many Applications on your Home Screen you might not see Services, for this you need to install Launcher application which will enable you to access all your third party Applications.
Now that you have Installer.app on your iPhone you can install more Application.
Tip: We recommend to uninstall TextEdit application from your iPhone, because it allows you to rename the /root folder or /var folder, which could cause damage to the iPhone software. We had one instance of that already. If that happens to you the iPhone will need to be restored to it's factory settings using the 1.0.2 Firmware restore file.
Thursday, October 18, 2007
iPhone 1.1.1 official & hidden features
Obviously there’s Apple’s publicised list, the majority of which could hardly be described as earth-shattering:
-iTunes Wi-Fi Music Store
-Louder speakerphone and receiver volume
-Home Button double-click shortcut to phone favorites or music controls
-Space bar double-tap shortcut to intelligently insert period and space
-Mail attachments are viewable in portrait and landscape
-Stocks and cities in Stocks and Weather can be re-ordered
-Apple Bluetooth Headset battery status in the Status Bar
-Support for TV Out
-Preference to turn off EDGE/GPRS when roaming internationally
-New Passcode lock time intervals
-Adjustable alert volume
What Apple didn’t mention was the following:
-Ability to change voicemail password directly from the iPhone. Tap “Settings,” then “Phone,” then “Change Voicemail Password.”
-You can now change the sound that is played when a new text message is received. Tap “Settings,” then “Sounds,” then “New Text Message.”
-Mobile Safari “Debug console”, showing HTML errors encountered when rendering Web pages. Tap “Settings,” then “Safari,” then “Developer”
-New video playback options, including selectable resume functionality to begin playing videos where they left off or from the beginning, as well as closed captioning support. Tap “Settings,” then “iPod.”
Finally, proving that nobody - even the Jesus phone - is perfect, there are a handful of security fixes and “refinements”:
-Bluetooth
An attacker within Bluetooth range may be able to cause an unexpected application termination or arbitrary code execution. “An input validation issue exists in the iPhone’s Bluetooth server. By sending maliciously-crafted Service Discovery Protocol (SDP) packets to an iPhone with Bluetooth enabled, an attacker may trigger the issue, which may lead to unexpected application termination or arbitrary code execution. This update addresses the issue by performing additional validation of SDP packets.”
-Mail
Checking email over untrusted networks may lead to information disclosure via a man-in-the-middle attack “When Mail is configured to use SSL for incoming and outgoing connections, it does not warn the user when the identity of the mail server has changed or cannot be trusted. An attacker capable of intercepting the connection may be able to impersonate the user’s mail server and obtain the user’s email credentials or other sensitive information. This update addresses the issue by properly warning when the identity of the remote mail server has changed.”
Following a telephone (”tel:”) link in Mail will dial a phone number without confirmation “Mail supports telephone (”tel:”) links to dial phone numbers. By enticing a user to follow a telephone link in a mail message, an attacker can cause iPhone to place a call without user confirmation. This update addresses the issue by providing a confirmation window before dialing a phone number via a telephone link in Mail.”
-Safari
Visiting a malicious website may lead to the disclosure of URL contents “A design issue in Safari allows a web page to read the URL that is currently being viewed in its parent window. By enticing a user to visit a maliciously crafted web page, an attacker may be able to obtain the URL of an unrelated page. This update addresses the issue through an improved cross-domain security check.”
Visiting a malicious website may lead to unintended dialing or dialing a different number than expected
“Safari supports telephone (”tel:”) links to dial phone numbers. When a telephone link is selected, Safari will confirm that the number should be dialed. A maliciously crafted telephone link may cause a different number to be displayed during confirmation than the one actually dialed. Exiting Safari during the confirmation process may result in unintentional confirmation. This update addresses the issue by properly displaying the number that will be dialed, and requiring confirmation for telephone links.”
Visiting a malicious website may lead to cross-site scripting “A cross-site scripting vulnerability exists in Safari that allows malicious websites to set JavaScript window properties of websites served from a different domain. By enticing a user to visit a maliciously crafted website, an attacker can trigger the issue, resulting in getting or setting the window status and location of pages served from other websites. This update addresses the issue by providing improved access controls on these properties.”
Disabling JavaScript does not take effect until Safari is restarted “Safari can be configured to enable or disable JavaScript. This preference does not take effect until the next time Safari is restarted. This usually occurs when the iPhone is restarted. This may mislead users into believing that JavaScript is disabled when it is not. This update addresses the issue by applying the new preference prior to loading new web pages.”
Visiting a malicious website may result in cross-site scripting “A cross-site scripting issue in Safari allows a maliciously crafted website to bypass the same-origin policy using ‘frame’ tags. By enticing a user to visit a maliciously crafted web page, an attacker can trigger the issue, which may lead to the execution of JavaScript in the context of another site. This update addresses the issue by disallowing JavaScript as an “iframe” source, and limiting JavaScript in frame tags to the same access as the site from which it was served.”
Visiting a malicious website may result in cross-site scripting “A cross-site scripting issue in Safari allows JavaScript events to be associated with the wrong frame. By enticing a user to visit a maliciously crafted web page, an attacker may cause the execution of JavaScript in the context of another site. This update addresses the issue by associating JavaScript events to the correct source frame.”
JavaScript on websites may access or manipulate the contents of documents served over HTTPS “An issue in Safari allows content served over HTTP to alter or access content served over HTTPS in the same domain. By enticing a user to visit a maliciously crafted web page, an attacker may cause the execution of JavaScript in the context of HTTPS web pages in that domain. This update addresses the issue by limiting access between JavaScript executing in HTTP and HTTPS frames.”
As with any security update, reading the worst-case-scenario description makes you fearful of ever using the device; in reality, I’m sure few people have been affected by any of these issues. Still, it’s good to know Apple have addressed them!
What’s more complicated is advising the large number of people who, having added third-party software to their iPhone, are wondering if it’s worth installing 1.1.1 and losing all that flexibility. At the end of the day, only you know exactly what you want from your iPhone, and while the hacking community is working on a compatible Jailbreak fix there’s no guarantee when (or even if) they’ll produce it. Speaking for myself (and you must remember I’m still waiting even for the option to buy an iPhone come launch day in the UK) the headline mobile iTunes store wouldn’t be enough for me to sacrifice all of the incredible mods being churned out.
To reiterate, if you’ve unlocked your iPhone then don’t perform the 1.1.1 firmware upgrade until you’ve replaced the AT&T SIM lock, else you could end up with a recalcitrant iPhone that won’t work at all.
-iTunes Wi-Fi Music Store
-Louder speakerphone and receiver volume
-Home Button double-click shortcut to phone favorites or music controls
-Space bar double-tap shortcut to intelligently insert period and space
-Mail attachments are viewable in portrait and landscape
-Stocks and cities in Stocks and Weather can be re-ordered
-Apple Bluetooth Headset battery status in the Status Bar
-Support for TV Out
-Preference to turn off EDGE/GPRS when roaming internationally
-New Passcode lock time intervals
-Adjustable alert volume
What Apple didn’t mention was the following:
-Ability to change voicemail password directly from the iPhone. Tap “Settings,” then “Phone,” then “Change Voicemail Password.”
-You can now change the sound that is played when a new text message is received. Tap “Settings,” then “Sounds,” then “New Text Message.”
-Mobile Safari “Debug console”, showing HTML errors encountered when rendering Web pages. Tap “Settings,” then “Safari,” then “Developer”
-New video playback options, including selectable resume functionality to begin playing videos where they left off or from the beginning, as well as closed captioning support. Tap “Settings,” then “iPod.”
Finally, proving that nobody - even the Jesus phone - is perfect, there are a handful of security fixes and “refinements”:
-Bluetooth
An attacker within Bluetooth range may be able to cause an unexpected application termination or arbitrary code execution. “An input validation issue exists in the iPhone’s Bluetooth server. By sending maliciously-crafted Service Discovery Protocol (SDP) packets to an iPhone with Bluetooth enabled, an attacker may trigger the issue, which may lead to unexpected application termination or arbitrary code execution. This update addresses the issue by performing additional validation of SDP packets.”
Checking email over untrusted networks may lead to information disclosure via a man-in-the-middle attack “When Mail is configured to use SSL for incoming and outgoing connections, it does not warn the user when the identity of the mail server has changed or cannot be trusted. An attacker capable of intercepting the connection may be able to impersonate the user’s mail server and obtain the user’s email credentials or other sensitive information. This update addresses the issue by properly warning when the identity of the remote mail server has changed.”
Following a telephone (”tel:”) link in Mail will dial a phone number without confirmation “Mail supports telephone (”tel:”) links to dial phone numbers. By enticing a user to follow a telephone link in a mail message, an attacker can cause iPhone to place a call without user confirmation. This update addresses the issue by providing a confirmation window before dialing a phone number via a telephone link in Mail.”
-Safari
Visiting a malicious website may lead to the disclosure of URL contents “A design issue in Safari allows a web page to read the URL that is currently being viewed in its parent window. By enticing a user to visit a maliciously crafted web page, an attacker may be able to obtain the URL of an unrelated page. This update addresses the issue through an improved cross-domain security check.”
Visiting a malicious website may lead to unintended dialing or dialing a different number than expected
“Safari supports telephone (”tel:”) links to dial phone numbers. When a telephone link is selected, Safari will confirm that the number should be dialed. A maliciously crafted telephone link may cause a different number to be displayed during confirmation than the one actually dialed. Exiting Safari during the confirmation process may result in unintentional confirmation. This update addresses the issue by properly displaying the number that will be dialed, and requiring confirmation for telephone links.”
Visiting a malicious website may lead to cross-site scripting “A cross-site scripting vulnerability exists in Safari that allows malicious websites to set JavaScript window properties of websites served from a different domain. By enticing a user to visit a maliciously crafted website, an attacker can trigger the issue, resulting in getting or setting the window status and location of pages served from other websites. This update addresses the issue by providing improved access controls on these properties.”
Disabling JavaScript does not take effect until Safari is restarted “Safari can be configured to enable or disable JavaScript. This preference does not take effect until the next time Safari is restarted. This usually occurs when the iPhone is restarted. This may mislead users into believing that JavaScript is disabled when it is not. This update addresses the issue by applying the new preference prior to loading new web pages.”
Visiting a malicious website may result in cross-site scripting “A cross-site scripting issue in Safari allows a maliciously crafted website to bypass the same-origin policy using ‘frame’ tags. By enticing a user to visit a maliciously crafted web page, an attacker can trigger the issue, which may lead to the execution of JavaScript in the context of another site. This update addresses the issue by disallowing JavaScript as an “iframe” source, and limiting JavaScript in frame tags to the same access as the site from which it was served.”
Visiting a malicious website may result in cross-site scripting “A cross-site scripting issue in Safari allows JavaScript events to be associated with the wrong frame. By enticing a user to visit a maliciously crafted web page, an attacker may cause the execution of JavaScript in the context of another site. This update addresses the issue by associating JavaScript events to the correct source frame.”
JavaScript on websites may access or manipulate the contents of documents served over HTTPS “An issue in Safari allows content served over HTTP to alter or access content served over HTTPS in the same domain. By enticing a user to visit a maliciously crafted web page, an attacker may cause the execution of JavaScript in the context of HTTPS web pages in that domain. This update addresses the issue by limiting access between JavaScript executing in HTTP and HTTPS frames.”
As with any security update, reading the worst-case-scenario description makes you fearful of ever using the device; in reality, I’m sure few people have been affected by any of these issues. Still, it’s good to know Apple have addressed them!
What’s more complicated is advising the large number of people who, having added third-party software to their iPhone, are wondering if it’s worth installing 1.1.1 and losing all that flexibility. At the end of the day, only you know exactly what you want from your iPhone, and while the hacking community is working on a compatible Jailbreak fix there’s no guarantee when (or even if) they’ll produce it. Speaking for myself (and you must remember I’m still waiting even for the option to buy an iPhone come launch day in the UK) the headline mobile iTunes store wouldn’t be enough for me to sacrifice all of the incredible mods being churned out.
To reiterate, if you’ve unlocked your iPhone then don’t perform the 1.1.1 firmware upgrade until you’ve replaced the AT&T SIM lock, else you could end up with a recalcitrant iPhone that won’t work at all.
Subscribe to:
Posts (Atom)