Hey i remember reading that with the iphone 4 saving your shsh blobs is only half the battle now and theres something else that goes on with the restore now, can anyone clarify any of this for me?

Originally Posted by truehybridx

Hey i remember reading that with the iphone 4 saving your shsh blobs is only half the battle now and theres something else that goes on with the restore now, can anyone clarify any of this for me?

I believe the baseband also has its own shsh blob which umbrella covers but other than that its still the same as the 3GS, No shsh files on sauriks server or saved locally then you won't be able to restore to a previous firmware than what is available and being signed by apple (i.e you cannot technically restore to iOS 4.0 now without shsh on file sense Apple released 4.0.1 and stopped signing 4.0)

Originally Posted by truehybridx

Hey i remember reading that with the iphone 4 saving your shsh blobs is only half the battle now and theres something else that goes on with the restore now, can anyone clarify any of this for me?

Nothing goes on with the restore .
If you have the shsh stored locally then you can use tinyumbrella, click on start tss server and begin to restore.

At the end of the restore, you will get error 1004 in itunes, ignore it, and use tiny umbrella and click on "kick device out of recovery".

That's all.

edited! thanks

Originally Posted by alpineflip

I believe the baseband also has its own shsh blob which umbrella covers but other than that its still the same as the 3GS, No shsh files on sauriks server or saved locally then you won't be able to restore to a previous firmware than what is available and being signed by apple (i.e you cannot technically restore to iOS 4.0 now without shsh on file sense Apple released 4.0.1 and stopped signing 4.0)

The baseband is signed by Apple during restore, this cannot be cached in a usable way by umbrella or saurik's server (because each signing request includes a unique/random number generated by the baseband cpu).
If Apple still will sign a request for a specific baseband, then that allows downgrading (as well as restoring to the same version or upgrading). This means people testing iOS 4.1beta can safely downgrade their baseband to iOS 4.0 level on an iPhone 4. This is only valid while Apple is still signing restore requests for that specific baseband. So after the beta is over, people will not be to downgrade baseband to 4.0 level.

Originally Posted by dtube

Nothing goes on with the restore .
If you have the shsh stored locally then you can use tinyumbrella, click on start tss server and begin to restore.

At the end of the restore, you will get error 1004 in itunes, ignore it, and use tiny umbrella and click on "kick device out of recovery"

Pretty sure this 1004 is due to the invalid or missing baseband signed request as mentioned above.
Resolution/workaround is as described by dtube.

The 1004 is really strange, as I got one even when restoring to a firmware that is being currently signed Apple (not cached).

But my guess is that it has to do with having the Cydia / Umbrella in the path (that is having a modified host file, either manually for Cydia or automatically by Umbrella).

Of course it is bacause of having a modified hosts file... if your hosts file is modified then iTunes will send a request for the baseband SHSH blob to sauriks/umbrella server. And those don't support those requests... and the result is error 1004.

Originally Posted by mikrohard

Of course it is bacause of having a modified hosts file... if your hosts file is modified then iTunes will send a request for the baseband SHSH blob to sauriks/umbrella server. And those don't support those requests... and the result is error 1004.

mikrohard is correct. The 1004 error is iTunes telling you that it didn't get the valid response from the SHSH server for the baseband and it is then unable to process the flash because of that. This will happen if you are using saurik's server as mikrohard mentioned, because saurik's server does not yet cache baseband SHSHs. It has not been announced that it ever will, but it's possible, I suppose.

Originally Posted by n1ckn4m3

saurik's server does not yet cache baseband SHSHs. It has not been announced that it ever will, but it's possible, I suppose.

It's pointless to cache baseband signing - as explained earlier, each baseband signing request includes a random number generated by the baseband CPU. So that signing request is only valid during that specific restore session.

The only way it would be useful to cache this signed request is if the baseband cpu can be tricked - a custom payload that over-rides the default random number generation to always generate a predicable number (and then cache the signed response from Apple).

This still is not very useful unless that payload was able to be delivered via a baseband bootloader exploit.

This is just my thoughts on the matter. I am sure that the true baseband hackers have already thought through and discounted this scenario as unpractical.

Originally Posted by dtube

Nothing goes on with the restore .
If you have the shsh stored locally then you can use tinyumbrella, click on start tss server and begin to restore.

At the end of the restore, you will get error 1004 in itunes, ignore it, and use tiny umbrella and click on "kick device out of recovery".

That's all.

oh i coulda used tiny umbrella for that lol... i used rslite