blobsaver VS cicuta_virosa

Iirc it does it through recovery, I know this does it through DFU and you should be able to bypass the passcode!

https://github.com/airsquared/blobsaver/releases works on Windows.

use blobsaver: https://github.com/airsquared/blobsaver

At this moment there is no protocol. iPhones 8 and up can't use saved blobs anymore because of something new in iOS 16 (cryptix) more info (could change in thw future, no one knows with apple. As for saving blobs in your case. You can only save blobs for current signed fw, which are 16.3.1 and 16.4. Use blobsaver. There is a method to save your onboard 14.3 blobs. Search the sub for it. You never know, might come in handy in the future.

just use blobsaver, if it's saved, it's valid

https://github.com/airsquared/blobsaver, just make sure you dont press “read from device” after you save it the first time.

Hi, try with BlobSaver , is cross-platform and really easy to use!

download blobsaver to you computer and get your apnonce/generator pair from the phone. Write these down just to be sure. And now you can use that same blobsaver program or either of the online services tsssaver.1conan.com or shsh.host to save your blobs. You can only start with the blobs that are currently officially being signed by apple.

blobs here you go

I referred to this one

I can almost guarantee so many exploits wouldn't be sold to companies like Cellebrite or to foreign governments, or even given out for free, if Apple paid market rate for them. They won't though, because they prefer to reflect and obscure, pretending that the problem doesn't exist.

Okay, I KNOW I'm going to sound like an ETA kid, but let me assure you, I'm on iPadOS 14.6 anyways, so I'm going to be sticking to checkra1n for a while now. I heard there was some news for iOS 14.4-14.4.2 and possibly 14.5, hinted here, but not as likely. I've heard that they need a kernel exploit before anything can be declared finished, which makes sense. Then one got released. So then I was told to wait until all the iOS firmware that were affected were unsigned. Strange, but iOS 14.5 was signed at the time, so I went along with it. Then iOS 14.5 got unsigned. So why isn't unc0ver updated? I mean, it is a bit hasty, considering some of us are still blown away by the fact that the unc0ver team even came back, but what about the info I was heard?

Modernpwner, the team that found the iOS 14.3 and below exploits for jailbreaks (unc0ver and Taurine) has hinted at a possible bypass that could lead to a jailbreak for 14.5 (PAC bypass section of https://github.com/ModernPwner/cicuta_virosa). You could theoretically update to either one of these versions right now since they’re being signed, but given the time it takes for jailbreaks to become a thing, these versions might not be signed by Apple if or when a full jailbreak is released for them. You’d have to play the waiting game for a good while if you update now, and none of these exploits are guaranteed to be stable enough for a full fledged jailbreak anyways. That’s why blob saving is so powerful!

With the release of iOS/iPadOS 14.5 and the public disclosure of security content for 14.5 (https://support.apple.com/en-us/HT212317), as well as the potential for another exploit for 14.5 from Modernpwner (PAC bypass section of https://github.com/ModernPwner/cicuta_virosa), updating looks enticing right now. However, you don’t have to lose your jailbreak and play the waiting game.

If you remember how we got our 14.3 jailbreak, ModernPwner released an exploit named "cicuta_virosa" that worked up to 14.3. On the bottom of the README, he mentioned the following:

https://github.com/ModernPwner/cicuta_virosa In the PAC bypass section, they say,