3gs error 21 restoring redsn0w stitched 5.1.1?

stlmac08 · 08-18-2012, 06:56 PM

I have a 3gs (new boot rom) on baseband 05.12.01, iOS 4.3.3, originally unlocked with Ultrasn0w 1.2.4.

I am upgrading to 5.1.1 and plan to jailbreak and unlock. I created a custom firmware in redsn0w 0.9.14b2, stitching my 5.1.1 blobs to it. I then used the tool to go into pwned DFU mode and it indicates I am successful. Then I restore the firmware in iTunes and get "The iPhone could not be restored. An unknown error occurred (21)."

The only thing I see in google is that I might not have been in pwned DFU mode. Retrying does not help. Same error (and I have to get out of recovery mode after the failure with Tiny Umbrella so that I can power off the device from 4.3.3 and try to pwn DFU again.)

I do notice that as I am entering pwned DFU mode in redsn0w, that the last timer stops at about 8 seconds and the screen goes on to downloading some exploit to the device. When the screen changes, I quickly release the button and redsn0w says I am in pwned DFU mode. One time I held the button longer as if to complete the 15 seconds, but that caused the exploit to fail and I had to futz around with it a little to get it rebooted after that for the next attempt.

What else could be wrong?

djdarkxd · 08-18-2012, 07:03 PM

use snowbreeze to do into dfu mode

stlmac08 · 08-18-2012, 07:12 PM

Quote:

Originally Posted by djdarkxd

use snowbreeze to do into dfu mode

I am on Macintosh. Snowbreeze is Windows only.

djdarkxd · 08-18-2012, 07:25 PM

well that sucks... do u have another computer?

bianchin69 · 08-18-2012, 07:46 PM

Does the restore go most of the way through?
Try fix recovery in redsnow after the error

stlmac08 · 08-18-2012, 08:27 PM

Quote:

Originally Posted by bianchin69

Does the restore go most of the way through?
Try fix recovery in redsnow after the error

The restore fails early and I am able to get back to 4.3.3 on the device to try again. The device is working 4.3.3 now and has gone through this cycle several times.

The issue is, what are the causes of the error 21 and how to properly flash the stitched firmware.

bianchin69 · 08-18-2012, 08:29 PM

Try running tiny umbrella while restoring?

stlmac08 · 08-18-2012, 08:53 PM

Quote:

Originally Posted by bianchin69

Try running tiny umbrella while restoring?

Actually, I tried that the first time, running the TSS server to serve up my BLOB and got error 3004 and 11 before I figured out I need to stitch the SHSH to my custom firmware. Once I did that, I did not run TSS server.

Are you saying I need to do both, run TSS server and use the stitched firmware? Or what should I have Tiny Umbrella be doing while I try the restore?

get · 08-19-2012, 12:16 AM

if you are upgrading to ios 5.1.1, just cook up a custom firmware that preserves your baseband using redsn0w. then restore through itunes pointing it to your preserved BB custom firmware...done

apple is still signing 5.1.1 so there is no need for tinyumbrella, stitching blobs, or anything crazy like that.

---------- EDIT ----------

also, make sure your host file is not blocking itunes for calling home.

MrElectrifyer · 08-19-2012, 01:05 AM

Quote:

Originally Posted by get

if you are upgrading to ios 5.1.1, just cook up a custom firmware that preserves your baseband using redsn0w. then restore through itunes pointing it to your preserved BB custom firmware...done

apple is still signing 5.1.1 so there is no need for tinyumbrella, stitching blobs, or anything crazy like that.

---------- EDIT ----------

also, make sure your host file is not blocking itunes for calling home.

Ensure that you don't have the "Set Hosts to Cydia on Exit" checkbox checked under TinyUmbrella's "Advanced" tab.

stlmac08 · 08-19-2012, 09:54 AM

Quote:

Originally Posted by get

if you are upgrading to ios 5.1.1, just cook up a custom firmware that preserves your baseband using redsn0w. then restore through itunes pointing it to your preserved BB custom firmware...done

apple is still signing 5.1.1 so there is no need for tinyumbrella, stitching blobs, or anything crazy like that.[color="#d3e009"]

Tried that simple approach and was getting 1604 errors until I put the device into pwned DFU mode in redsn0w. Then I let Apple sign it normally and it worked. Question - why couldn't I use Tiny Umbrella TSS server or stitching to use my saved BLOB? I want to be able to do the restore again after iOS 6 comes out and don't understand why I had to let Apple sign it today, rather than use the blob I saved for 5.1.1 a few months back.

Also, I needed an AT&T SIM card to activate. I had one from another phone that was unused. I have another 3gs I need to do. Will I be able to use the same SIM again, since it never had service turned on? (Hope I didn't "consume" the SIM card)

After activating and looking in the general settings to see my baseband preserved, I used Absinthe for the jailbreak with no apparent issue. I know it is said that I should have run it right away without setting up the phone for the cleanest jailbreak, but is what I have OK, if it appears to be working, or should I redo just to run Absinthe before the setup and before I spend a lot of time customizing the phone to my tastes? Or do I increase my risk of 5.1.1 going unstable in actual use later because of this?

And the final step UltraSn0w made it work with a TMobile SIM fine.

So I should proceed to install my favorite Cydia and iTunes apps, unless there is any reason I should have done the Absinthe before the phone setup.

Thanks

get · 08-20-2012, 02:22 AM

Quote:

Originally Posted by stlmac08

Tried that simple approach and was getting 1604 errors until I put the device into pwned DFU mode in redsn0w. Then I let Apple sign it normally and it worked. Question - why couldn't I use Tiny Umbrella TSS server or stitching to use my saved BLOB? I want to be able to do the restore again after iOS 6 comes out and don't understand why I had to let Apple sign it today, rather than use the blob I saved for 5.1.1 a few months back.

My guess is it had something to do with your APTicket. Due you not ever running iOS5 and only saving your SHSH Blobs that may have been your problem. iDevices running iOS5 depend on the APTicket being legitimate to be able to boot. If not, the device will enter Recovery Mode.

Now that you have iOS5 firmware installed on your iPhone and legitimately signed by Apple, you should save your Blobs again.

stlmac08 · 08-20-2012, 07:07 AM

Quote:

Originally Posted by get

My guess is it had something to do with your APTicket. Due you not ever running iOS5 and only saving your SHSH Blobs that may have been your problem. iDevices running iOS5 depend on the APTicket being legitimate to be able to boot. If not, the device will enter Recovery Mode.

Now that you have iOS5 firmware installed on your iPhone and legitimately signed by Apple, you should save your Blobs again.

I thought TinyUmbrella was able to save APTickets even for devices that have never run iOS 5. So, are you saying that Tiny Umbrella saves the APTicket of only the currently installed iOS version? Also, do I have to have the device plugged in when I save the blobs? Often I did not plug in the devices because TinyUmbrella keeps a list of my devices.

Also, any comments on my other questions in post #11?

Thanks

stlmac08 · 08-20-2012, 11:34 AM

I plan to try again with a fresh BLOB just to see if I can leave Apple's server out of the loop. But will I be able to use that same AT&T SIM card again that I already used to activate the phone after redoing the iOS again?

Should I be able to use the Tiny Umbrella TSS server if I have a proper blob with AP Ticket, in order to restore the RedSn0w custom firmware? Or should I be retrying it by stitching instead. At this point, I want to ascertain I could reinstall 5.1.1 without the help of Apple, after iOS 6 is out.

Thanks

---------- EDIT ----------

I started a new thread specifically to discuss the Tiny Umbrella part of this issue and there I am advised by a high-post-count member that Tiny Umbrella saves the APTickets even if device is on older firmware, or not connected -- suggesting that is not the issue with my 3gs 5.1.1 install failures.

Saving APTickets in Tiny Umbrella?
Saving APTickets in Tiny Umbrella? - SiNfuL iPhone

So back to my questions of post 11 highlighted in yellow, can anyone please advise?

MrElectrifyer · 08-20-2012, 03:48 PM

Quote:

Originally Posted by stlmac08

.
.
.
So back to my questions of post 11 highlighted in yellow, can anyone please advise?

SHSH Blobs are only necessary for downgrades, not upgrades. I suspect that since you are updating to the latest firmware, there is some iTunes so called "security feature" in place preventing you from getting restore verification from a third party source.

As for using the same AT&T sim to activate your iPhone, there is no limit to how many times you can activate an iPhone using a specific SIM, regardless of whether or not it is receiving service from the carrier. It would be as stupid as requiring a payment to restore your iPhone in the case of an issue.

As for the jailbreaking on fresh restore, there shouldn't be any future issues due to jail breaking if it's functioning correctly at this moment. But, as your iPhone is supported, I would much rather suggest you do the jailbreak via a signed custom firmware created via sn0wbreeze. That way, once you restore via iTunes, it would already be jailbroken and plus, there wouldn't be any need for SHSH blobs again for that particular firmware (so long as you have the custom iPSW backed up) as it's already signed by an SHSH blob.

stlmac08 · 08-20-2012, 09:57 PM

Quote:

Originally Posted by MrElectrifyer

SHSH Blobs are only necessary for downgrades, not upgrades. I suspect that since you are updating to the latest firmware, there is some iTunes so called "security feature" in place preventing you from getting restore verification from a third party source....I would much rather suggest you do the jailbreak via a signed custom firmware created via sn0wbreeze. That way, once you restore via iTunes, it would already be jailbroken and plus, there wouldn't be any need for SHSH blobs again for that particular firmware (so long as you have the custom iPSW backed up) as it's already signed by an SHSH blob.

Sn0wbreeze is Windows only, so I had tried to create the custom firmware with redSn0w instead. Why couldn't I restore the firmware with the stitched blob in iTunes? Or, will the stitched blob method only work after Apple stops signing?

joecef · 08-20-2012, 10:12 PM

stitched is for firmware no longer being signed by apple

bianchin69 · 08-20-2012, 10:30 PM

Quote:

Originally Posted by joecef

stitched is for firmware no longer being signed by apple

OMG at least someone reads post

stlmac08 · 08-21-2012, 05:14 AM

Quote:

Originally Posted by joecef

stitched is for firmware no longer being signed by apple

I understand that I don't need to be using stitched yet, with Apple still signing as I already have a jailbroken unlocked 3gs (that relied on Apple's signing). My question, is why can't I make a practice run of the technique of stitching now, to be able to see it work now, so I can be confident I will be able to do a restore later after Apple has stopped signing?

In other words, I would think that either using stitched or using TSS server should be able to succeed now (and just simply not call on Apple for a signing), but I do not understand what went wrong.

I just want to test/practice the procedure I would follow after the signing 5.1.1 stops, now, while the signing is still available.

How would the fact that Apple is still signing prevent using stitched firmware now from working? That just makes no sense to me, and right now, I have zero confidence that I would be able to restore the 3gs with jailbreak/unlock/5.1.1 after iOS 6 comes out, with all the trouble I had above.