How to: Fix Error 60000ms Giving Up when Jailbreaking

On January 10, 2012, in Fixes, by Ian Ziyar

If you tried to jailbreak your iPhone/iPod Touch/iPad and redsn0w or greenpois0n gave you the error 60000ms, you need to restore your iPhone/iPod Touch/iPad and then rejailbreak. This error means that you are redoing a jailbreak which has already been done meaning that you have probably used redsn0w in the past for a different reason but perhaps it failed. Regardless, watch the video below for details.

This guide is made free of charge but the website costs money to run.  Please consider supporting us by sending a small “thank you” payment to our PayPal.


11 Responses to “How to: Fix Error 60000ms Giving Up when Jailbreaking”

  1. […] Note, if you get the infamous error 60000ms, go to this guide to figure out how to fix it. How to fix error 60000ms guide […]

  2. Delia Villiers says:

    Im confused as to how we re-store using this i-faith thing?

  3. Hello my Name is Antonio and I leave in Veneto – PD (Italy).My compliment for page.I see yours commets.We advise you one commets. Thanks.

  4. Free High PR Backlink!…

    If you want a free backlinks, go to Just fill in the offer and your backlink is permanent….

  5. Good afternoon my Name is Monia and I leave in Italy.Our compliment for page.I see ours commets.We advise you one posts. Thanks.

  6. hoguedog says:

    got 600000 error and downloaded ifaith and pawnd my ipod touch 3g. then went to itunes and put it in dfu mode and hit restore with out holding shift and it worked perfect. i tried everything else and this is the only thing that worked.

  7. sengchan says:

    change date and time and try connect to itune again… my iphone3gs have same problem 60000ms i fix it by this.

  8. Bo says:

    I tried restore Itunes, it keep give me error (-1). Could you tell me how to fix this error.

  9. IOSCUBE says:

    That’s interesting to know!

Leave a Reply to Allevamento Rottweiler


Time limit is exhausted. Please reload the CAPTCHA.

©2012 All copyrights and trademarks are the property of their registered owners. is an independent blog and has/is not authorized, sponsored, or otherwise approved by Apple, Inc