can you please help me find the "no" button?
its the cancel button dude..
can you please help me find the "no" button?
if your blobs are saved, i believe, you can always downgrade to the firmware that your saved blob was by pointing itunes to Saurik's server.
so technically you should be able to upgrade without fear, knowing you can always roll back. (as long as your hashed)
correct?
its the cancel button dude..![]()
How do you save blobs?
It is too late to save your 4.0 SHSH. Notcom has confirmed that the signing window is closed. You can now only install 4.0.1 if you do not have your 4.0 SHSH saved.
Can you explain why the "signing window" is closed? I'm not getting that part. If people haven't upgraded to 4.0.1 yet, why can't they still save the blobs?
How do you save blobs?
Can you explain why the "signing window" is closed? I'm not getting that part. If people haven't upgraded to 4.0.1 yet, why can't they still save the blobs?
If anyone has a second maybe someone can expplain this to me, not new to iphones but new to all this....i did save my 4.0 blobs but only cause every one said we should...now if we jailbreak 4.0 why would we need our 4.0 blobs? What does it do for us. This may be a very stupid question but like i said im new to this. What i kind of get out of it is that if we jailbreak 4.0 and need to go back to an unjailbroken 4.0 we can because our 4.0 blobs are saved. if they werent we would have to go to 4.01 which may not be jailbroken. is that right?
If anyone has a second maybe someone can expplain this to me, not new to iphones but new to all this....i did save my 4.0 blobs but only cause every one said we should...now if we jailbreak 4.0 why would we need our 4.0 blobs? What does it do for us. This may be a very stupid question but like i said im new to this. What i kind of get out of it is that if we jailbreak 4.0 and need to go back to an unjailbroken 4.0 we can because our 4.0 blobs are saved. if they werent we would have to go to 4.01 which may not be jailbroken. is that right?
Anyone know if there's a way to check if your 4.0 blob was backed up to Cydia? I'm 99.9% sure I did, but I wish there was a way to check.
Anyone know if there's a way to check if your 4.0 blob was backed up to Cydia? I'm 99.9% sure I did, but I wish there was a way to check.
hey bud i might be wrong and anyone correct me if i am, but in tiny umberalla after its done it says it was sent to Cydia....
http://thefirmwareumbrella.blogspot.com/
or if your j/b already u used cydia... but the 4.0 window has closed already so if you havent done it, you're too late
what if you saved it locally? I was able to save 4.0 blobs locally...can I update to 4.0.1 safely?
what if you saved it locally? I was able to save 4.0 blobs locally...can I update to 4.0.1 safely?
Just wait for MuscleNerd. That's always the best policy. Nobody has confirmed whether there is a baseband update or if there are hidden changes. Just wait.
can you please help me find the "no" button?
if your blobs are saved, i believe, you can always downgrade to the firmware that your saved blob was by pointing itunes to Saurik's server.
so technically you should be able to upgrade without fear, knowing you can always roll back. (as long as your hashed)
correct?
SHSHs can only be obtained from Apple's server, because they have to be signed using Apple's private key. This is why your SHSH for a firmware version can only be obtained while Apple is still signing that version. SHSH stands for signature hash, and is just a technical term for an encrypted signature attached to a message (in this case, the message authorizing installation of a version of the iPhone firmware).
The SHSH is not saved anywhere on your device or in a backup. It is used only briefly to authorize an installation, and is requested anew for each installation. It is different for each version of the firmware. TinyUmbrella can save your SHSH as it is returned by Apple, but only if you request it while Apple is still signing. Same for Cydia. They take advantage of the fact that Apple failed to include a time check in their authorization scheme, so the same SHSH is returned each time you request the same version. This was really poor security design on Apple's part, since it make it possible to spoof Apple's server as long as you cache your SHSH for each version while Apple is still signing.
As soon as Apple stops signing a version of the firmware, it can no longer be requested and cached. And it is absolutely impossible to generate a new SHSH yourself unless you can obtain Apple's private signing key. Good luck with that.