Apple strongly recommends that you do not jailbreak your iPhone. Really.

“While jailbreaking an iPhone is legal in the US, Apple has always clearly stood against it, warning that it may void your warranty,” Sébastien Page writes for iDownloadBlog. “You can’t criticize Apple for this policy because it makes lots of sense. Why would they try to fix an issue if the device is running unauthorized code on it, right?”

Page reports, “Reddit user DurianNinja found an interesting paragraph tucked inside Apple’s retail store purchase policies that shows what I feel is interesting wording about jailbreaking an iOS device: ‘Making unauthorized modifications to the software on an iPhone violates the iPhone software license agreement. The common term for modifying an iPhone is jail-breaking, with a particular emphasis on the second part of that term. That’s why we strongly, almost emphatically, recommend that you do not do so. Really. Should you be unable to use your iPhone due to an unauthorized software modification, its repair will not be covered under the warranty.'”

Page writes, “If you ever have a software problem with a jailbroken iOS device and you want to take it to Apple for warranty service, you should always make sure you restore your device first, for two reasons.”

Read more in the full article here.

49 Comments

  1. Why would you want to, it pretty much makes it just as much garbage as android. If you want a piece of shit phone just buy an android, and stop jail breaking iPhones.

    1. Prior to iOS 6 my iPhone was always jailbroken. Every reason I did…. Are the things we now enjoy as part of iOS.

      MANY of the features of iOS were born in the jail breaking community.

      Remember back when you couldn’t even COPY/PASTE????????? (iOS 3.something)
      Yep apple feared that was something an iPhone user could not figure out how to use.
      Jail breaking also fixed security holes in iOS that apple took months to fix…

      Jail breaking isn’t “always bad” but I’ll agree that people can go way overboard and install everything under the sun and really hinder their devices.

      Lockscreen
      Notification Center
      Control center
      Multitasking
      Background…
      Copy/paste
      Some security holes
      Battery percentage instead of icon

      All of these were implemented by Apple later. Some of which years after the jailbreak community had them.

      The lockscreen info was one of the first jailbreaks, android copied it and used it their os.. When Apple finally got around to implementing it, android fanboys claimed Apple copied android.. When android copied the jailbreak community.

      I have not jailbroke my iOS devices since a brief jailbrake in iOS 6 after it dropped. I have no want or desire to do so anymore.
      But I won’t bash those that do, I understand why they do.

      Some apps that Apple pulled from the App Store, not for security but other reasons (Apple used to pull apps because another dev claimed the app was similar to theirs.. Even though theirs was the newer one) they find themselves on cydia etc.

      And it’s obvious if you do jailbrake to restore before you go to Apple for service.. It’s not apples problem if you do and mess things up.

      1. Just to nitpick: I think the reason that Apple took as long as they did to add copy-and-paste was because they were trying to figure out a way to do it simply and easily — you know, Apple-style.

        That little magnifying glass UI they came up with works great, but I’m sure it took awhile to design.

        ——RM

        1. i’ll give you that.

          but copy/paste has been around for ever… It amazes me how ALL phone OS’s took forever to implement it.

          Microsoft, did as well.
          Not sure with Android.
          I know BB had it when I got my first/only BB.

          Apple took over 3 years… THAT just isn’t right.

          1. Apple takes a little longer because it likes to get things done right. And to prove they were successful in this, check out every competing platform who quickly copied Apple’s particular implementation of copy/paste.

            1. 3 years……………………………..
              Microsoft took a few months.

              If you guys do not remember… that little magnifying glass… WAS ADDED LATER. it was double tap to highlight the text to copy. again… 3 years later..
              http://www.technologytell.com/apple/46138/iphone-30-cut-copy-and-paste/

              “So how’s it work? Well, quite simply. You double-tap on a piece of text and a pop up menu will appear with the options cut, copy and paste. At either end of the highlighted text, there are markers. You drag these markers to extend the amount of text you want to cut or copy. Pasting the text is as you’d expect; double-tap in the place, and select paste.”

              Just looked it up, Android had copy/paste from day one, BUT it was limited to usage between certain apps. Which was later changed to system wide.

              Now knowing it took Apple 5 years to develop the iPhone… that means 8 years total to come up with copy/paste.

            2. I don’t like to quibble, but I believe Apple took longer because they initially recognized that implementing copy/paste was a large security risk, so they didn’t want to do it. However due to customer demand they took their time to implement it in a secure fashion. Not in the insecure manner that is used on Android. Security takes more effort.

            3. Apple repeatedly stated it had nothing to do with security, 100% “looks”
              read all the articles from back in the day (it’s not hard to do research)

      2. I recently jailbreaked my iPhone 5S.

        The experience showed everything that’s good and bad about jail breaking. Some apps were brilliant, besting Apple’s. Other apps simply refused to work. Whilst others worked haphazardly. Finally, it broke some of the Apple apps.

        In the end, I had to restore it. But whilst it was frustrating I had much fun exploring another App Store and seeing what the jail breaking community dreams up.

    2. The argument is usually “It’s my device so I can do whatever I want with it and no one can tell me otherwise.” Most car manufacturers tell people not to modify their vehicles but it’s certainly done all the time even at the risk of voiding warranties. However if I had the modifications done and things went wrong, I wouldn’t go crying back to the manufacturer to help me out.

      Apple is telling consumers not to modify their iPhones to basically save them any future grief of having an insecure device. I’m not sure if some modifications can compromise a whole network. I just don’t think it’s something consumers should be upset about if they’re told not to jailbreak their smartphones. I doubt even Android device manufacturers would actually encourage consumers to do such a thing.

      1. Android does actually..
        The ability to Root an android is basically built into the “OS” in the vast majority of Fragmendoid’s.
        Very few can’t or are hard to Root.

        just did some searching.
        http://www.cnet.com/news/google-encourages-rooting-of-phones/
        older article but Google doens;t care if their phones are rooted..
        granted, recently they started restricting rooted phones from even viewing the movies on their store.. Not sure if they are doing this to “properly” rooted devices.. or rooted devices via some hack.

        I don’t know, I don’t follow fragmendorid much.

        And you are correct about similar approach to mods on cars. Depending on the manufacturer *some* mods are fine, while others they will not touch.

        I replaced my HD in my 2011 27″ iMac with a SSHD and a cable from OWC. my video card died.. (Known issue with the 2011 iMac’s)
        So first thing I did.. open the iMac and swapped out the HD to the old one from Apple. Put the SSHD back in after I got it back, fixed free of charge.

        I probably could have left the SSHD in there.. but didn’t want the tech to open it up and claim the SSHD caused the issue. Or the hardware test to even remotely show the HD in the iMac isn’t standard..

    3. “Why would you want to, it pretty much makes it just as much garbage as android. “

      No it doesn’t. Being jailbroken allows you to do any number of stuff. While some kiddies will theme the fsck out of their iPhones, others look for only those things they can enable that offer enhanced functionality without compromising the solid polished iOS.

      “stop jail breaking iPhones”
      Why do you care?

  2. Though I really do wish Apple would give us back access to the WiFi modem so that we could have nifty a WiFi network analysis tools such as those I find on Android. It’s embarassing to have to pull out my Android phone to do a heat map.

      1. Why would anyone care what kind of phone someone ELSE buys, uses, enjoys? Most people outgrew that petty behavior somewhere in their adolescence. I pity those of you who just can’t let go.

  3. “…we strongly, almost emphatically, recommend that you do not do so. Really.”

    Almost. But not quite emphatically. Really. You gotta love that Apple legal language; even there, they will find the way to keep some levity…

  4. If you feel the need to jailbreak an iPhone why bother getting an iPhone? Get an android cheaper, root that and hack away to your heart’s content.

    On the other hand, getting an iPhone means that you are in a closed garden environment and your security being compromised is minimized.

    An iPhone is used for using not for hacking. There are enough troubles with iOS updates, why would you want to add more variables to the equation?

    Ideally if you know what you’re doing and are very careful there shouldn’t be problem, but most jailbreakers just want to download stuff that Apple doesn’t support and may cause problems down the road.

    To the jailbreakers that know exactly what they’re doing, more power to you. To the jailbreakers who haven’t a clue and just want to add features, you get what you deserve.

  5. Jailbreaking means that Apple has a hole in its security. Unless Apple closes that hole immediately that means that Apple approves of jailbreaking to some extent.

    They disapprove officially but approve by letting this go on over the many generations of the iOS. What do we make of that?

    1. No Apple closes the means people use to jailbrake the devices with the next update. Every iOS update the jailbrake community waits for someone to release a new jailbrake, sometimes it takes months..

      Honestly I don’t think there is a jailbrake for iOS 8 yet. It took forever for iOS 7 to have one..

      1. That’s not entirely true. Some updates have not patched the exploit that the jailbreak takes advantage of. Also Apple has never just released an update that did nothing but block a jailbreak.

        1. no, they always incorporate it into the next update. They don’t outright say “this fixes a jailbreak” though.. although Apple *did* credit a jailbreak team as fixing a few security holes.
          the worst one was a PDF exploit that Apple didn’t catch/fix until the 2nd update.

          Every Jailbreak uses a different method, the teams basically have to start from scratch every update.

          1. This is false:
            “no, they always incorporate it into the next update.”

            This contradicts your first sentence:
            “the worst one was a PDF exploit that Apple didn’t catch/fix until the 2nd update.

            The fact is many jailbreaks have survived iOS updates. In the past couple of years, Apple has been a little bit better about rolling up the patches into their updates, but nonetheless, often, as you point out yourself, their releases don’t always patch the jailbreaks.

            “Every Jailbreak uses a different method, the teams basically have to start from scratch every update.”

            That’s not really true either. Not only does not every update block the jailbreaks, but not every update that does patch every exploit the the jailbreak at the time uses. Jailbreaks don’t take advantage of just one flaw, but usually several and not always are all of them or even any of them patched when the next update comes out.

            Bootrom exploits have even survived hardware updates.

            All of this is indicative of Apple’s priorities, especially when you consider that Apple has never issue an update solely to block a jailbreak.

            They’ll fix security flaws, but most that jailbreakers end up taking advantage of aren’t significant threats. As such Apple doesn’t always interrupt their upgrade schedule to deal with them. Due to the fact that Apple works on multiple versions at the same time, jailbreaks can, and have, survived multiple updates both software and hardware.

            1. pick apart *my* wording…

              iOS updates have always killed jailbreaks. the PDF exploit WAS the exception..
              4.0.1 was already in/out of beta when they realized the issue. 4.0.2 was released a few weeks later.

              https://en.wikipedia.org/wiki/History_of_iOS
              Compare the releases to the jailbreak release dates.. find a jailbreak that survived an iOS update. They were all broken by updates.

              Now.. *some* of the jailbreaks were not released due to the soon to be released iOS update, so you would be correct a “jailbreak” would have survived an update.

              “especially when you consider that Apple has never issue an update solely to block a jailbreak.”

              AHEM… READ the iOS 4.0.2 patch notes. the ONLY thing it did was patch the PDF exploit.

              But honestly I don’t care. Haven’t even followed the jailbreak scene in years, just randomly pop in and see whats going on. Like I said the last time i had a jailbroken iPhone was in iOS 5, and a brief (2-3 days) iOS 6 jailbreak.
              iOS 6 finally added the last few things out of the box that i was jailbreaking for.

              I wouldn’t mind the option to remove that gaudy flat dock though.. pretty much everything else in iOS 8 i’m either used to now, or I like.

            2. Wow, you really like to contradict yourself don’t you? You did it again in a single paragraph:
              “OS updates have always killed jailbreaks. the PDF exploit WAS the exception..”

              I’m not sure if English isn’t your first language, but “always” and “every” means there are no exceptions.

              Despite that, 4.0.1 wasn’t the only exception. Heck as recently as 7.1.1 -> 7.1.2 a jailbreak made the jump.

              I’ve been jailbreaking since the 1st iPhone, and having a jailbreak survive an update isn’t that rare of an event.

              “AHEM… READ the iOS 4.0.2 patch notes. the ONLY thing it did was patch the PDF exploit.”

              Right, and read what I wrote. The PDF exploit was a serious security issue that Apple had to deal with regardless of whether or not people were jailbreaking, they didn’t release it solely to block jailbreaking, but rather to protect all users from an significant threat from malicious PDFs. This differs greatly from most flaws the jailbreaks take advantage of which don’t present active or significant threats. Hence, Apple patches for all kinds of reasons, solely preventing jailbreaking isn’t one of them.

            3. you’re grasping.

              iOS 7.1.2 RELEASED june 30th
              iOS 7.1.1 jailbreak RELEASED june 23rd AFTER 7.1.2 WENT GOLD…….. and was able to use more than one flaw to jailbreak, iH8sn0w released it knowing that Apple didn’t fix it yet (cause it was unknown to apple…)

              http://www.idownloadblog.com/2014/06/23/ios-7-1-1-untethered-jailbreak-burns-two-exploits/

              https://en.wikipedia.org/wiki/IOS_7#7.1.2 june 30

              the Pdf exploit was the exception to the rule, my comment stands.

              But again… I don’t care. I have no need/desire to jailbreak anymore. And i could care less if you do.

            4. “iOS 7.1.2 RELEASED june 30th
              iOS 7.1.1 jailbreak RELEASED june 23rd AFTER 7.1.2 WENT GOLD…….. and was able to use more than one flaw to jailbreak, iH8sn0w released it knowing that Apple didn’t fix it yet (cause it was unknown to apple…)”

              BUT… you said Apple always patches in the next update. They didn’t. What “gold” are you talking about here… We’re not talking about Apple burning the firmware, it was still out for developer beta and Apple could’ve at any time during the 7 days not released it. They made the choice to go ahead with it. Again, you said “every” patch kills the jailbreak. Here are two, one that you mentioned, and one off the top of my head that happened to be a very recent example where you were wrong.

              “you may want to read about the phrase”

              I’m familiar with the phrase, but you didn’t say, “as a rule…” you were pretty emphatic, and still are, that it never happened… except the two times we’ve now mentioned as well as others.

              Want another example? As I mentioned before, there are bootrom exploits. Bootrom jailbreaks rely on hardware flaws, and there have been those that Apple never did patch with iOS updates, nor could they.

              What’s your problem that you can’t just admit you were wrong? Apple sometimes releases iOS updates that don’t break the jailbreak. That’s a fact. You know this, and yet you feel some weird need to argue otherwise.

            5. Also here’s another one… also recent… Evasion7 lasted from 7.0->7.0.1->7.02->7.03->7.04
              It made it all the way to the 4th beta of 7.1

              That was several months.

              The jailbreak for 6.1.3 went 6.1.3->6.1.4->6.1.5->6.1.6

              Again, we’re talking about several months.

              How many exceptions does it take before you stop saying “always”?

            6. Simple. Learn to do research before you post.
              http://theiphonewiki.com/wiki/Evasi0n
              Notice there were REVISIONS to the jailbreak? cause yeah.. Apple kept patching the holes they used.
              Note the list they used to jailbreak iOS.. they did not release ALL exploits at once, when Apple patched one.. they switched to the next.

              My above comments that you can’t yet see has a list of multiple links… “Your comments awaiting Moderation” from MDN.
              Yeah I took a screenshot in case MDN never “approves” it.

              AGAIN, all you are doing is proving “but, I know what i’m talking about” and ZERO facts to back it up… I AM.

            7. You started this with:
              “No Apple closes the means people use to jailbrake the devices with the next update. Every iOS update the jailbrake community waits for someone to release a new jailbrake, sometimes it takes months… [snip] Every Jailbreak uses a different method, the teams basically have to start from scratch every update.”

              Now you acknowledge that 4.0.2 was an exception. And 7.1.2 was an exception. And certainly you can admit the bootrom jailbreaks are exceptions… and of course 6.1.3.

              But despite your “multiple exceptions prove the always”, you not only won’t admit you were wrong, but continue to get the facts wrong

              “AGAIN, all you are doing is proving “but, I know what i’m talking about” and ZERO facts to back it up… I AM.”

              I’m listing specifics that are easy to verify through wikis. You’re going on and on proving that your initial statement was incorrect without being adult enough to admit it.

              You might want to read the page that you linked to… at least the very first line. You pointed to the Evasion jailbreak, not the Evasion7 jailbreak. The Evasion jailbreak was for 6.0->6.1.2, but thanks for pointing out more evidence that your initial comment was wrong. Apple didn’t block that jailbreak to the point where the Evasion team had to “start from scratch”, nor did they even patch every exploit, which is why they were able to turn around new versions of Evasion so quickly.

              But go ahead and click on the link on the first line of the page you linked to and go to Evasion7. You’ll see that my comment is absolutely correct… Evasion7 worked 7.0->7.0.1->7.02->7.03->7.04
              It made it all the way to the 4th beta of 7.1 and only then was revised to provide support from some of the exploits being patched.

              Seriously, what’s so hard about saying “I said ‘always’ when I should’ve said ‘sometimes'”?

            8. 4.0.2 was the exception.

              Like I have said, which YOU can’t understand…..

              the others you mention WERE RELEASED ONLY CAUSE THE GOLD MASTER WAS RELEASED AND THE FLAW WAS STILL THERE.

              “The Evasion jailbreak was for 6.0->6.1.2, but thanks for pointing out more evidence that your initial comment was wrong. Apple didn’t block that jailbreak to the point where the Evasion team had to “start from scratch”, nor did they even patch every exploit, which is why they were able to turn around new versions of Evasion so quickly.”

              WITH REVISIONS ON EVERY VERSION OF iOS CAUSE OF THE LIST OF FLAWS THEY DISCOVERED, THEY ONLY BURNED 1 FLAW EACH REVISION THAT APPLE PATCHED.

              How F’n dumb are you?

              Take the time and read the history of back and forth between Apple and the Jailbreak community. They never released a jailbreak with EVERY flaw in it… they released 1-2 exploits per release…. so they could continue to HAVE a jailbreak later after Apple patched it…

              Simple…
              Look at the dates of iOS release, compare to Jailbreak releases… and compare to Jailbreak revisions…

              And sometimes………….. people learn from reading.

            9. “4.0.2 was the exception.” Again, you said “always”, not “as a rule” which would imply that there could be exception.

              “the others you mention WERE RELEASED ONLY CAUSE THE GOLD MASTER WAS RELEASED AND THE FLAW WAS STILL THERE.”

              BS… You said “no, they always incorporate it into the next update.” You did not say, “they try to incorporate it in the next update”. And there’s no Gold Master situation here. Look it up. They had a week with 7.1.2 in which to make the patch. They didn’t. This literally contradicts your statement. Why it contradicts your statement isn’t relevant.

              “With revisions on every version of iOS cause of the list of flaws they discovered, they only burned 1 flaw each revision that Apple patched.”

              Right, but again, this contradicts what your original comment was. You said, that the jailbreak developers had to “start from scratch” each time there was an update. You did not say, “while a jailbreak may be blocked, Apple won’t always patch all of the flaws that enable a jailbreak, thus in 6.0->6.1.2 the jailbreak developers didn’t have to start from scratch”.

              “Take the time and read the history of back and forth between Apple and the Jailbreak community. They never released a jailbreak with EVERY flaw in it… they released 1-2 exploits per release…. so they could continue to HAVE a jailbreak later after Apple patched it…”

              Here’s why you’re confused. You think that the jailbreak depends on 1 flaw in order to work. No, it requires several flaws. In 6.0->6.1.2, Apple patched some of the flaws along the way, but there were still enough flaws being used that Apple did not patch that enabled Evasion to utilize previous unused flaws in order to make minor and quick revisions to the tool. 6.0->6.1.2 doesn’t contradict your statement that Apple patches in updates, which is why I didn’t bring it up. You did, but once you brought it up, I mentioned that it contradicts your argument that jailbreak developers need to “start from scratch”.

              You’re still not addressing how the bootrom based jailbreaks contradict your statement that “Every iOS update the jailbrake community waits for someone to release a new jailbrake, sometimes it takes months.” or the other examples where the jailbreak spanned multiple versions.

            10. Actually I did, but MDN is being lazy and not moderating like they normally do… (Or just deciding to stay out of this)
              When you post more than 2-3 links, it automatically gets lost to the “awaiting moderation” hell

              And what you CONTINUE to ignore… Script kiddies always ignore it…

              AGAIN…. READ THE TIMELINE OF APPLE’S PATCHES… AND COMPARE THEM TO THE TIMELINE OF THE JAILBREAKS….

              You will notice something, well.. you won’t cause you can’t do any research on your own… ever..
              There were multiple holes/flaws in iOS 6 that you keep harping on, WHICH IS TRUE… The envision jailbreak DID NOT INCLUDE all of the flaws at first… EACH time Apple plugged the hole, envision used the next on their list…
              Envision rev 1 CAN’T jailbreak 6.1.1 Rev 1.4 CAN……
              NOTE the DATES that APPLE released iOS 6.1.1 FEBRUARY 6TH 2013 (ONLY for iPhone 4S, everyone else was iOS 6.1 on January 28th)
              Envision Rev 1.0 FEBUARY 4TH 2013….. WHICH CAN JAILBREAK iOS 6.0 THROUGH 6.1

              IT CAN’T F’N JAILBREAK 6.1.2 BECAUSE APPLE HASN’T F’N RELEASED IT YET……..
              Envision CAN HOWENVER Jailbreak iOS 6.1.2 in REV 1.4 WHICH WAS RELEASED AFTER iOS 6.1.2 was released…. but stopped in iOS 6.1.3 which was 3 weeks later… they VERY NEXT update…

              IT’S HOW THEY WORK… Why in the hell would you PUBLISH every security flaw that YOU ARE USING TO JAILBREAK iOS…. so Apple can fix them and render your “work” worthless in one shot?

              Did you even READ any of the links I posted? the hackers involved wrote it out in detail HOW they released the jailbreaks… and was careful to NOT burn ALL of the exploits at once…

              DO SOME READING…. EVERYTHING I have quoted from is from those very papers PUBLISHED by the hackers involved themselves…….. NOT MY WORDS……

              You still do not understand the concept of gold masters..
              The hackers ARE developers…. THEY get the GM build and take note that their flaw is STILL THERE….

              NOW here is where your script kiddie ass thinks you have won the debate…….

              But your logic is flawed, the jailbreak HAS NOT BEEN MADE PUBLIC AT THIS POINT….. SO APPLE HAS NO F’N CLUE IT EXISTS……. THEY CAN’T PATCH WHAT THEY DO NOT KNOW EXISTS….. THAT IS WHEN THE JAILBREAKS ARE RELEASED (AFTER THE GM HAS BEEN VERIFIED TO BE UNPATCHED) Which tends to be either same day or shortly after the full iOS release.

              YOU think that apple didn’t patch it, but Apple didn’t know of the flaw BECAUSE it has not been made public yet…

              ALL you have to do is spend some time READING the papers the jailbreak hackers have made DESCRIBING the whole process.. I HAVE PROVIDED THE LINKS FOR YOU…

              YOU respond with “But… I know what i’m talking about” yet ZERO proof of anything, beyond verification you are a Script Kiddie. (And/Or Troll)

              I have better things to do with my time than trying to convince a troll he’s wrong, because he refuses to READ. Believe what you want, IDGAF.

              ANYONE that wants to decide for themselves about he subject…

              theiphonewiki.com/wiki/Jailbreak (May have to copy/paste it, or use one of the other links I posted.. Trying to make sure this post doesn’t get auto-moderated to oblivion..)

              Go there, and start reading all about all the jailbreaks, the vulnerabilities used, how long they were active etc. ALSO you can READ the papers published, or transcripts of speeches given, BY the authors of the jailbreaks and see how they found the flaw/hole, when they decided to use said hole/flaw, and the cat and mouse game they have played with Apple over the years.

              I’m done feeding the troll.

            11. Thanks for yet again providing more proof that you were wrong. I think we’re done here. In summary:

              You wrote:
              “OS updates have always killed jailbreaks.”
              And then admit that this isn’t the case. 4.0.2 you admit was an exception. If something has an exception, by definition, it’s not “always”.

              Instead of being an adult about it, and admitting you were wrong, you then continue to admit other examples, but these don’t count because the were “Gold Master” according to you (no proof, just timelines). Ok, but again, these other examples prove your statement wrong. you can’t admit that Look, it would be one thing to be adult enough to admit that your statement was incorrect, and we could easily agree on when updates have or have not killed jailbreaks, but you seem unable to admit when you’ve been caught being wrong even when you go on to write things proving yourself wrong.

              You then go on to argue about 6.1.2 which I didn’t even bring up… you did. And yet it proves another one of your statements to be wrong. The jailbreak developers didn’t have to “start from scratch”. You then go on to argue something I’m not even saying about it. I’m pointing out that your statement was wrong about starting from scratch. And you yourself admit this in your own argument. The fact is along the way with Evasion, Apple patched some of the exploits, but not every exploit Evasion was using, nor the ones it was reserving. Thus, the quick turnaround as opposed to starting from scratch.

              It’s too bad your post that didn’t get moderated by MDN wasn’t posted. Here you are again acknowledging the bootrom exploits as something that did in fact prove your statement incorrect.

              That the bootrom jailbreaks didn’t work on all models or all iOS versions doesn’t matter. Likewise it doesn’t matter why an iOS update doesn’t break an update (timing), nor does it matter how many jailbreaks weren’t broken by updates. The mere fact that 1 did (and you even admit others did) proves your statement incorrect.

            12. Shorter:

              “It doesn’t matter, cause…. cause…. I’m right and you’re wrong”

              You still can’t read.
              You are looking at Rev. 1.4 and calling it a win.. you can’t look at dates, you can’t look at the papers the hackers themselves state that you are wrong.. why would you? Cause, you’re “right”

              LMFAO.

              Troll/Script Kiddie confirmed.

              “The fact is along the way with Evasion, Apple patched some of the exploits, but not every exploit Evasion was using, nor the ones it was reserving.”

              NOW you are starting to get it…………….
              Half right.
              Apple can’t patch what Apple didn’t know about.

            13. “It doesn’t matter, cause…. cause…. I’m right and you’re wrong”

              That’s because you are wrong. You just won’t admit that you’re wrong. What is you problem that when faced with the facts you can’t just admit that what you wrote was wrong, and then restate what you should’ve said to begin with.

              It’s really a weird personality trait. You aren’t disputing the facts that proved that you were wrong, in fact you even brought them up yourself.

              “You still can’t read.”

              This is another funny one. Take a look at every comment I wrote. Read them. Notice that I never said Evasion (not 7) was an example of you being wrong with “Patches break every jailbreak”, but if you could read you’d see that over and over I wrote that Evasion was an example where Apple didn’t patch every patch that was being used and thus it’s an example where the jailbreak team didn’t have to start from scratch, contrary to your statement that they did.

              It has nothing to do with Apple not knowing about unused exploits, but rather of the various exploits any one version of Evasion was using at any one time, Apple only patched some of them, allowing the team to continue to use the ones Apple didn’t patch along with the ones on the list that had never been used.

              I think your confusion is that you seem to believe that 1 jailbreak version = 1 exploit as opposed to 1 jailbreak version requiring several exploits.

              Your special type of trolling here is called a strawman. I’m correcting you on the fact that not every update from Apple patches everything that the jailbreak team is using for the jailrbeak and thus your statement “has to start over from scratch” is incorrect. I’m only arguing this in regards to Evasion… which you brought up in the argument of “every update breaks the jailbreak” which is a different argument which you yourself proved incorrect as well.

              The second type of trolling you’re doing is called an Overwhelming Exception
              http://en.wikipedia.org/wiki/Overwhelming_exception

              You stated that every update has always broken a jailbreak and they’ve had to always start over from scratch. Then when presented with the exceptions, you acknowledge them, but instead of admitting your statements were wrong and simply saying, “right, I should have said, ‘generally/most of the time jailbreaks are broken when new updates come out'”.

              Between the two logical fallacies you’re deploying, there’s really nothing else for me to point out other than you obviously have issues accepting when you’ve said something that is incorrect even when you yourself bring up the facts that prove your statement wrong.

            14. Oh look, 8.1.2 is out and…

              Apple didn’t patch any exploits that the Taig jailbreak was using for for 8.1.1:

              http://www.taig.com/en/

              I know, you’re going to say, but “always” doesn’t count in this, yet another exception, because because because uh… it only fixed ringtones?

            15. read your link…

              Update came afterwards..
              “V1.2.0 (2014-12-10)
              Support all device with iOS8.1.2.”

              IF mdn is letting posts here again..
              They even said that there IS an exploit in 8.2 beta they are using, but have not released…. so it can be Jailbroken when Apple releases it. Possible they have more than one hole they are using.

              http://www.evasi0njailbreak.com/8.1.2-released-can-i-jailbreak-8.1.2-taig-untethered/

              “Today, in a surprise release, without having first entered iOS developer beta form, Apple issued iOS 8.1.2 (the second incremental 8.1.x update, of course succeeding 8.1.1) to the general public. As of now, unlike its predecessor, 8.1.2 cannot be jailbroken by way of either TaiG, being the latest 8.1.1 Untethered jailbreak or the older Pangu for iOS 8 through 8.1 utility, which was patched when Apple released 8.1.1. ”

              what?………………………. wait 8.1.1 tag jailbreak does’t work?
              oh wait.. it does if you use the 1.2.0 version they released after iOS 8.1.2

            16. “read your link…
              Update came afterwards..
              “V1.2.0 (2014-12-10)
              Support all device with iOS8.1.2.”

              Read what your original comment was and what I said you were wrong about. 8.1.2 did not patch any exploits. Taig modified the jailbreak tool and released it within hours of 8.1.2. Again, this is contrary to what you said regarding Apple always patching exploits and the jailbreakers having to start over from scratch.

              They even said that there IS an exploit in 8.2 beta they are using, but have not released…. so it can be Jailbroken when Apple releases it. Possible they have more than one hole they are using.

              This is funny because all along you’ve been bringing up points that prove your previous statements incorrect. Here you go again with 8.2 beta. I didn’t bring this up, you did. Again, because you need to be reminded of this each time. Your two points that I said were wrong were:
              1) OS updates always kill jailbreaks by patching the known exploits in the next update
              2) Every Jailbreak uses a different method, the teams basically have to start from scratch every update.”

              While both statements are incorrect, 8.1.2 is contrary to the first statement and *your* example of 8.2 beta is contrary to the second statement.

              what?………………………. wait 8.1.1 tag jailbreak does’t work?
              oh wait.. it does if you use the 1.2.0 version they released after iOS 8.1.2

              Right, but that’s not because Apple patched any exploit, which was the point you were making. This is why I think you’re confused. You’ve looked through the history of jailbreaks and seen version upgrades corresponding with dates after iOS version updates and concluded that the iOS version update patched all of the exploits being used, when in reality sometimes:
              1) Not every exploit being used in one version of the jailbreak was patched.
              2) No exploit was patched at all.
              3) The jailbreak tool needed to be modified simply to recognize the new version number.
              4) The jailbreak tool need to be modified simply to deal with minor modifications in the system.

              None of these count as:
              1) OS updates always kill jailbreaks by patching the known exploits in the next update
              2) Every Jailbreak uses a different method, the teams basically have to start from scratch every update.”

              Look at your original comment. How can you justify saying that you weren’t wrong, even if you just want to modify it as “sometimes” or even “usually” instead of “always”.

              The whole point here is that you wrote what you did in terms of Apple’s intent, and clearly through this thread, you yourself have brought up examples where Apple hasn’t prioritized around killing jailbreaks, and 8.1.2 shows that simply fixing a bug regarding ringtones was more important to Apple than patching an exploit being used in a jailbreak.

              And by the way, looking back on your original comment. You wrote:
              “Honestly I don’t think there is a jailbrake for iOS 8 yet.”

              I’ve totally let you slide on that.

  6. I love my apple devices. And the reason I don’t by Android is because they suck. I don’t jailbreak my devices while under warranty, but once I upgrade to a new device I like to jailbreak the older one and have some extra fun with it.

  7. That ridiculous mentality of taking shorts cuts , never works , be real you want to have a piece junk go ahead.
    Feel better buy your apps.
    And screw jail breaking .

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.