iOS 6.x SHSH Blobs on Cydia/Saurik Server are Not Saved Correctly Causing Restore Issues

Hello there! If you are new here, you might want to subscribe to the RSS feed for updates on this topic!

#OhMyBlobs, it seems that Cydia is not saving your iOS 6.x SHSH blobs properly on Saurik’s server. If you plan to upgrade or downgrade your iOS, you must read this now.

This problem seems to be caused by aptickets (what is this?) that were solely saved by Cydia (upon Cydia launch) don’t have all essentials to boot (iBoot bit is missing) your iPhone. Redsn0w won’t notice it missing from the apticket and will continue saving your blobs.

ih8sn0w and Saurik are aware of this issue although there’s no official word from Saurik just yet. What I’m pretty sure is that many people relied entirely on Cydia’s automatic saving of SHSH blobs and have never saved an actually copy on their local computers. If you’ve been using iFaith and have saved your SHSH blobs regularly then you should be fine.

Editor's note: learn more by reading our ebook on starting your own iPhone repair & unlock business

If you’re new to iPhone restoring, downgrading and jailbreaking, SHSH blobs allow you to restore to an earlier version of iOS which is no longer being signed by Apple. For example, Apple is currently signing iOS 6.1.3, so if you’re trying to downgrade to earlier iOS version you will get error 3194 on iTunes. That’s basically Apple telling you that you cannot downgrade your iOS. However, by using SHSH blobs, you can trick iTunes to allow your device to be downgraded.

Why do people want to downgrade? Mainly for the untethered jailbreaking. It also allows you to restore your device to a working state especially if you messed it up. An iPhone 3GS can always be downgraded to iOS 4.1 as Apple never closed the signing window. If you fancy to learn about all these stuff, checkout my eBook here.

Based on people’s feedback, 6.1.2 Cydia Blobs are around 3.5kb in size while iFaith 6.1.2 blob is about 18k. That’s about 15k difference in file size which shows that there are plenty of missing information.

So, how would this affect you if you have an iPhone 4? Assuming that you’re trying to install iOS 6.1.2 with your Cydia blobs, you may be able to restore it but your iPhone will not boot properly and get stuck in soft DFU mode (black screen).

If you are still on iOS 6.0 and up to 6.1.2 on an iPhone 3GS, iPhone 4 or any A4-based iDevices, the safest way to dump your SHSH blobs is to use iFaith. The steps are outlined below:

How to Save SHSH Blobs using iFaith (Windows only) via jailbreakqa

iFaith supports iPad 1, iPhone 3GS (new bootrom), iPhone 4, and iPod touch 3rd and 4th generation. It does not support iPad 2, iPhone 4S, or older devices (iPhone 3GS with old bootrom, iPhone 3G, or iPod touch 2nd generation). As of April 2012, it may not work correctly if you have an 8 GB iPhone 4 (see here).

Step 1: Download iFaith

  1. Download iFaith here: (Note: iFaith may be detected as a Trojan by AVG and possibly other antivirus programs. This is a false positive and you may have to temporarily disable your antivirus program to use iFaith.)
  2. Have your device plugged in and powered off.
  3. Unzip the file and run the .exe file.

Step 2: Dump SHSH blobs onto your computer

  1. You will see a welcome/warning screen. Click OK.
  2. You are presented with 4 options. Select “Dump SHSH blobs” if you have not done so previously.
  3. A screen will pop up telling you what devices are supported (Apple TV 2, iPad 1, iPhone 3GS, iPhone 4, iPod touch 3 and 4).
  4. Click proceed then more credits, press let’s go!
  5. Another pop-up will ask if you are dumping an Apple TV 2, so click the appropriate button.
  6. Now, making sure your device is plugged in AND powered off, you can press the START button and put your device into DFU mode. iFaith will dump your current iOS device’s SHSH blobs onto your hard drive. The process takes about 10 minutes, and it may seem to hang on one part of the process, but be patient.
  7. Once done, iFaith will ask you to save the blobs on your computer. I chose to make a new folder for this. Note that iFaith also stores your blobs on its own remote server.
  8. iFaith will take you back to the main menu so you can build your signed IPSW.

Step 3: Build the signed IPSW

  1. OK, now click on “Build signed IPSW”.
  2. Click the “Browse for SHSH blobs cache” button. An Explorer window will open. Navigate to the folder that you had saved your blobs in the previous step – you should see a file that looks like this: iPhone_4-4.3.2_(8H7)-blobs.ifaith (here I am using 4.3.2 but yours will be whichever firmware you are using on your phone).
  3. You will now be prompted to browse for the stock IPSW for this firmware. There is also the option to have iFaith download it for you if you do not have it on your computer.
  4. Select the stock IPSW and iFaith will verify it.
  5. iFaith will then build the signed custom IPSW for you and place it on your desktop.
  6. You then can have iFaith put your device into PWN DFU for you if you want to restore your custom IPSW now, or just shut iFaith down if you are just building the IPSW for possible future use.
  7. If you want to restore to your new custom firmware, just use iReb (included in the iFaith program) to get your phone into PWN DFU mode, close iFaith, open iTunes, press and hold the shift key and press restore, browse to the signed custom firmware you created with iFaith and press OK, then restore.

This may be a bit overwhelming for many, so I only have one advice for everyone. Whatever iOS version you’re on right now, just stick to it until the situation becomes clearer and there are going to be fixes soon.

Random Posts:

AT&T Rejected Your iPhone Unlock Request with Their New Policies? Here’s How to Check
How to Unlock Your AT&T-Locked iPhone for Free by Contacting AT&T Support
Officially Permanent Unlock for Your AT&T iPhone 3G, 3GS, 4, 4S or iPhone 5
10 Frequently Asked Questions on Official IMEI Factory iPhone Unlock

How to Buy a Factory Unlocked AT&T iPhone 5 for Under $250

Share this and be awesome!

Comments & Discussion

  1. "although there’s no official word from Saurik just yet" <- (This is only because I'm in the middle of writing a massive "book" on the subject, as people would probably expect from me; it isn't like there is really any requirement that I say something quickly, as there has been tons of comments on this from MuscleNerd and iH8sn0w, who are the resident experts on this protocol.)

  2. I knew something must have been up when I was trying to upgrade from 5.0.1 to 6.1.2 and couldn't. Redsn0w was telling me that there was errors with my blobs. Here's good luck to a 6.1.3 JB

  3. Hi All,

    I've got an iphone 4 which stuck into soft dfu mode. I cannot exit from this. Tried everything. If I wanted to put into DFU mode it cames back immeditatelly to soft DFU.
    Please HELP!

    Many Thanks!

  4. I know this wasn't on purpose, but Saurik should feel so bad about this that he should be pressuring devs to come up with a jailbreak for iOS 6.1.3 for the models that can't downgrade.
    Many folks, like me, got stuck on 6.1.3, and because redsn0w TOLD ME the blobs were complete with a valid APTicket, I can't go back now. If iOS 6.x is the last iOS for the 3GS, I'll be stuck FOREVER on an iOS that can not have an untethered jailbreak. FOREVER!! I wish they'd focus for a little bit on 6.1.3 before tackling iOS 7.c which isn't even out yet!

Leave a Reply to saurik Cancel reply

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