Apple Urges Users Not To Jailbreak In “Support” Section

Well guys, Apple has finally gone off the deep end. They have actually taken the time to write up an article on reasons on why not to jailbreak. The article was created on April 16th of this year. I stumbled on this article after getting a random tip on Twitter.

Well, Apple gives some very stupid reasons to not jailbreak. They state this in regards to jailbreaking:

Unauthorized modification of iPhone OS has been a major source of instability, disruption of services, and other issues

Well, we all know this is bullshiznit. All of my iDevices have always been jailbroken (since iPhone OS 1.1.1 (before it was even known as iPhone OS). All of my devices have been jailbroken and unlocked. These have been my devices since 2007 in order: iPod touch 1G, iPod touch 2G, iPhone 3G, and iPhone 2G.

Now, I have not had a single issue. Ever. I’ve even hacked many other iDevices from my friends and family and no one has ever had an issue. Unless. Unless, they (or I) do something stupid, as in, I like to tinker around with the inner workings, and when I’m working on some sort of hack for my personal use, I sometimes “brick” my iDevice, but it’s always restorable.

Here’s a little more of what Apple says:

This article is about adverse issues experienced by customers who have made unauthorized modifications to the iPhone OS (this hacking process is often called “jailbreaking”). Issues that have been encountered include instability, disruption of services, and compromised security.

As designed by Apple, the iPhone OS ensures that the iPhone, iPad, and iPod touch operate reliably. Some customers have not understood the risks of installing software that makes unauthorized modifications to the iPhone OS (“jailbreaking”) on their iPhone, iPad, or iPod touch. Customers who have installed software that makes these modifications have encountered numerous problems in the operation of their hacked iPhone, iPad, or iPod touch.

Now, Apple lists the following as reasons:

Device and application instability: Frequent and unexpected crashes of the device, crashes and freezes of built-in apps and third-party apps, and loss of data.

Unreliable voice and data: Dropped calls, slow or unreliable data connections, and delayed or inaccurate location data.

Disruption of services: Services such as Visual Voicemail, YouTube, Weather, and Stocks have been disrupted or no longer work on the device. Additionally, third-party apps that use the Apple Push Notification Service have had difficulty receiving notifications or received notifications that were intended for a different hacked device. Other push-based services such as MobileMe and Exchange have experienced problems synchronizing data with their respective servers.

Compromised security: Security compromises have been introduced by these modifications that could allow hackers to steal personal information, damage the device, attack the wireless network, or introduce malware or viruses.

Shortened battery life: The hacked software has caused an accelerated battery drain that shortens the operation of an iPhone, iPad, or iPod touch on a single battery charge.

Inability to apply future software updates: Some unauthorized modifications have caused damage to the iPhone OS that is not repairable. This can result in the hacked iPhone, iPad, or iPod touch becoming permanently inoperable when a future Apple-supplied iPhone OS update is installed.

Now, what they neglect to mention is that, Apple’s stupid attempts at blocking jailbreaking cause all of these issues.

As for the battery loss and slow downs, this is only caused if you just install stuff all willy nilly like I see a lot of (especially) iPod touch owners. Winterboard and SBSettings are a killer. if you don’t install these, you are good.

Before the iPad was shown (then iPhone OS 4.0) I never used Winterboard for homescreen wallpaper, but, in my quest to theme the hell out of my devices to look like the real thing, I am sacrificing battery life. Now, I could update to real 4.0 since I’m an official developer, but I don’t want to lose my unlock. Plain and simple.

There is no “security” risks. The only “security” risk Apple is referring to is their own. There is nothing that happens to the iPhone or iPod touch that could be considered a “security risk”.

Now, as for “Disruption Of Services”, this is Apple’s own doing. Push notifications, YouTube, Visual Voicemail, MobileMe, and on and on and on, that’s all Apple. If they would make a system where it’s all generalized, there would be no issues.

Overall, that article is a total waste of time and space on their servers. This is the stupidest thing I have ever read. It’s stupid, misinformed, and very biased. This only shows the lame excuses Apple wants you to hear, not the truth.

People, I am all for jailbreaking and unlocking. I hate having a closed off device that I can’t use the way I want to. Whether there is a real “reason” to jailbreak, besides the unlock, doesn’t matter to me. I will find a reason. I love having access to the filesystem so I can do as I please in there.

So there you go guys. Just a little something I found, and my 2 cents worth. 🙂

Here’s Apple’s “support” article for those interested, just tap, or click, here.

Incoming search terms:

  • Unauthorized modification of iOS has been a major source of instability disruption of services and other issues

Comments

  1. Warning: mysql_query(): No such file or directory in /homepages/13/d372251105/htdocs/LEi Mobile/wp-content/plugins/comment-rating/comment-rating.php on line 219

    Warning: mysql_query(): A link to the server could not be established in /homepages/13/d372251105/htdocs/LEi Mobile/wp-content/plugins/comment-rating/comment-rating.php on line 219

    Warning: mysql_query(): No such file or directory in /homepages/13/d372251105/htdocs/LEi Mobile/wp-content/plugins/comment-rating/comment-rating.php on line 226

    Warning: mysql_query(): A link to the server could not be established in /homepages/13/d372251105/htdocs/LEi Mobile/wp-content/plugins/comment-rating/comment-rating.php on line 226
    class="comment even thread-even depth-1" id="comment-452">

Leave a Reply

Your email address will not be published. Required fields are marked *