Re-Install 3.1.2 Firmware on 3.1.2 Iphone 3Gs Stuck in Recovery Mode with no SHSH

I made a very foolish mistake. I took an iPhone 3Gs with 3.1.2 and wanted to jailbreak it using redsn0w. When it came to picking whether it was an old or new bootrom, i went ahead with old as it was a week 41 iPhone. Well, turns out the phone would not reboot, so I am now assuming it is actually a new bootrom and I would have to do a full restore 3.1.2 as per the instructions.

Now the phone is stuck in recovery mode with all black screen. Trying to reset/reboot the phone by holding power/home does absolutely nothing.

I want to go back to 3.1.2 or upgrade to 3.1.3, 4.0 or 4.0.1 but I do not have the SHSH for any of those firmwares. I am not downgrading, but I still can't get Apple to sign the firmwares. I even tried restoring with a custom Pwned 3.1.2 firmware, but that did not work either; just got an error 1600.

Can I do anything here or is my only option to upgrade to 4.1 and just wait for the jailbreak/unlock?

If it helps, I am able to go into System Profile and get my 16 digit ECID code, unfortunately, tinyumbrella is not picking up the iphone as it is in DFU mode and I am tehrefore unable to create any SHSH for it.

Thanks

Quote:

---

Originally Posted by miroesq

I made a very foolish mistake. I took an iPhone 3Gs with 3.1.2 and wanted to jailbreak it using redsn0w. When it came to picking whether it was an old or new bootrom, i went ahead with old as it was a week 41 iPhone. Well, turns out the phone would not reboot, so I am now assuming it is actually a new bootrom and I would have to do a full restore 3.1.2 as per the instructions.

Now the phone is stuck in recovery mode with all black screen. Trying to reset/reboot the phone by holding power/home does absolutely nothing.

I want to go back to 3.1.2 or upgrade to 3.1.3, 4.0 or 4.0.1 but I do not have the SHSH for any of those firmwares. I am not downgrading, but I still can't get Apple to sign the firmwares. I even tried restoring with a custom Pwned 3.1.2 firmware, but that did not work either; just got an error 1600.

Can I do anything here or is my only option to upgrade to 4.1 and just wait for the jailbreak/unlock?

If it helps, I am able to go into System Profile and get my 16 digit ECID code, unfortunately, tinyumbrella is not picking up the iphone as it is in DFU mode and I am tehrefore unable to create any SHSH for it.

---

Use advanced mode in tinyumbrella and type in the 16 digit ECID. Then try and request a SHSH for each of the iOS versions from Cydia. You don't even need the iPhone connected if you use advanced mode.

You are 100% stuck without a SHSH. The week number criteria has ALWAYS been only a rule of thumb and it takes only a few seconds more to check the true bootrom version via DFU mode.

Quote:

---

Originally Posted by Olethros

Use advanced mode in tinyumbrella and type in the 16 digit ECID. Then try and request a SHSH for each of the iOS versions from Cydia. You don't even need the iPhone connected if you use advanced mode.

---

i tried doing that already and it's not working for some reason:

09/14/2010 19:50:18.089 Processing SHSH Request...
09/14/2010 19:50:18.100 Asking CYDIA for SHSH blobs for iPhone3GS 3.1.2 (7D11)...
09/14/2010 19:51:23.614 This device isn't eligible for the requested build.
09/14/2010 19:51:23.622 CYDIA DOES NOT HAVE YOUR SHSH FOR iPhone3GS 3.1.2 (7D11) THERE IS NO WAY FOR YOU TO GET THEM. SORRY. YOU ARE JUST TOO LATE.

only SHSH i was able to get was 4.1. is there any solution to this problem?

thanks

Quote:

---

Originally Posted by miroesq

i tried doing that already and it's not working for some reason:

09/14/2010 19:50:18.089 Processing SHSH Request...
09/14/2010 19:50:18.100 Asking CYDIA for SHSH blobs for iPhone3GS 3.1.2 (7D11)...
09/14/2010 19:51:23.614 This device isn't eligible for the requested build.
09/14/2010 19:51:23.622 CYDIA DOES NOT HAVE YOUR SHSH FOR iPhone3GS 3.1.2 (7D11) THERE IS NO WAY FOR YOU TO GET THEM. SORRY. YOU ARE JUST TOO LATE.

only SHSH i was able to get was 4.1. is there any solution to this problem?

---

This is the risk of not backing up your SHSH. Apple is using this as a way to keep users up to date and as a way to fight unlock and jailbreak.

If you truly have a new bootrom 3GS (you've been looking at the ECID in system profiler, have you checked the iBoot version also?)

I have two ideas, neither of them will allow you to jailbreak in the short term.

What is more important ? keeping the ability to unlock (sometime in the near future) or the recovery of personal/important files on the iPhone?

Quote:

---

Originally Posted by Olethros

What is more important ? keeping the ability to unlock (sometime in the near future) or the recovery of personal/important files on the iPhone?

---

i have nothing of importance on the phone. my only priority is to get the phone unlocked as quickly as i can so that i may use it.

Have you confirmed that it truly is a new bootrom 3GS?

If it is... the best solution I can think of is this Preventing baseband update as a last-ditch effort [iPhone Dev Team] (adapted to iOS 4.1)

I don't know 100% if this works with iOS 4.x it definitely works with iOS 3.1.3

It will save your baseband from being updated.

However you will still end up on iOS 4.1 - which can't be jailbroken. When it is jailbroken, you should be able to unlock with ultrasn0w.

If you don't manage to prevent your baseband upgrade, then you will be waiting a lot longer.

There is NO solution that allows you to jailbreak and unlock today. You are stuck. (unless it really is old bootrom and sometheing else went wrong with your redsn0w jailbreak attempt)

Quote:

---

Originally Posted by Olethros

Have you confirmed that it truly is a new bootrom 3GS?

---

I went into System Profiler and I have iBoot-359.3.2 so it's definitely new bootrom.

For some strange reason I thought signing of firmware needed to be done for downgrades, not updates. My stupid mistake, but still I think there really should have been a warning in Redsn0w. All it said that if it does not work out, then I may have to do a complete restore, which I really could care less about. There was no warning to ensure that you have an SHSH, or better yet, a note telling you how to check if it's an old or new bootrom or even a link to a url that would tell you how to find out which version you have to ensure a smooth jailbreak.

If I can't do anything about the jailbreak/unlock now, then I think it would be best just to wait and see what happens with the 4.1 low level pwn that is supposedly coming out soon or see if someone comes up with a more reliable method for upgrading to 4.1 without updating the baseband, but as long as there is no benefit to me right now, I don't think there is a reason to risk it.

All I really want to do is kick this thing out of dfu mode and have it boot into it's old 3.1.2. Is there any way to access the file system and perhaps remove the files for installed by the jailbreak attempt then try to reboot? Also been reading a bit about maybe letting the battery drain, then have it boot out of DFU. Not sure if that would even help as I'm assuming it's the changes that were done by Redsn0w, using the setting of old bootrom, that are preventing the phone from booting.

Quote:

---

Originally Posted by miroesq

I went into System Profiler and I have iBoot-359.3.2 so it's definitely new bootrom.

For some strange reason I thought signing of firmware needed to be done for downgrades, not updates. My stupid mistake, but still I think there really should have been a warning in Redsn0w. All it said that if it does not work out, then I may have to do a complete restore, which I really could care less about. There was no warning to ensure that you have an SHSH, or better yet, a note telling you how to check if it's an old or new bootrom or even a link to a url that would tell you how to find out which version you have to ensure a smooth jailbreak.

If I can't do anything about the jailbreak/unlock now, then I think it would be best just to wait and see what happens with the 4.1 low level pwn that is supposedly coming out soon or see if someone comes up with a more reliable method for upgrading to 4.1 without updating the baseband, but as long as there is no benefit to me right now, I don't think there is a reason to risk it.

All I really want to do is kick this thing out of dfu mode and have it boot into it's old 3.1.2. Is there any way to access the file system and perhaps remove the files for installed by the jailbreak attempt then try to reboot? Also been reading a bit about maybe letting the battery drain, then have it boot out of DFU. Not sure if that would even help as I'm assuming it's the changes that were done by Redsn0w, using the setting of old bootrom, that are preventing the phone from booting.

---

You can't kick it out of DFU mode without signed LLB, your 3.1.2 low level bootloader is now corrupted and it is the first piece of software code that your iPhone uses in bootup.

Don't confuse other fixes like the battery drain/blackra1n solution. That is for a very different problem and the phones in that situation are NOT in DFU mode.

Quote:

---

Originally Posted by Olethros

You can't kick it out of DFU mode without signed LLB, your 3.1.2 low level bootloader is now corrupted and it is the first piece of software code that your iPhone uses in bootup.

Don't confuse other fixes like the battery drain/blackra1n solution. That is for a very different problem and the phones in that situation are NOT in DFU mode.

---

Thanks Olethros for all your help, I really appreciate it. I will just wait it out till there is a "safe" restore solution to 4.1 without the baseband update as I have the SHSH blobs for that. Hopefully it won't be to long.

Who knows, maybe the new 4.1 jailbreak will also include an unlock for the included baseband and then all of our lives would be a whole lot easier :)

Quote:

---

Originally Posted by miroesq

Who knows, maybe the new 4.1 jailbreak will also include an unlock for the included baseband and then all of our lives would be a whole lot easier :)

---

I would be very surprised if it does.

The pattern of unlocks from the iPhone dev team since the introduction of the 3G has been quite constant. One unlock per major iOS release.

If they have any more baseband exploits (a lot of their potential exploits have been closed by Apple's baseband cleanup that began with 05.11.07 where Apple reduced the attack surface by more than 50%) they will be saving them for iOS 5.0