Hello 
I have an iPhone 3GS that is stuck with a tethered jailbreak on 5.0.1. If I restart, I have to use redsn0w each time to boot the phone in a normal mode and when it is switched off redsn0w says it is in DFU mode. Anytime I try to restore it in the DFU mode it is stuck in, there are always errors preventing me from restoring. Some facts:
- New bootrom
- Corona untethered jb does not work
- Attempts to put in pwned DFU using redsn0w/iREB do not work, iTunes gives random errors (2005, not eligible for this requested build etc)
- No shsh blobs I know of
- Running the 06.15.00 baseband
I would like to install the untethered JB. I have made the ipsw using snowbreeze but since restoring does not work I cannot do anything with it. Could anyone please help me with this please?
Thank you all so much
Edit: From what I can tell, it's possible I updated it with the wrong 5.0.1 custom FW that is for the old bootrom, and not the new as it should be, since it says on redsn0w that if the production week from the serial number is <45 it should be old (which my SN indicated). Though looking on the system profiler on OSX now I can see it is the new bootrom, so I'm pretty sure this is the root of the problem causing all the strange behaviour.
I have an iPhone 3GS that is stuck with a tethered jailbreak on 5.0.1. If I restart, I have to use redsn0w each time to boot the phone in a normal mode and when it is switched off redsn0w says it is in DFU mode. Anytime I try to restore it in the DFU mode it is stuck in, there are always errors preventing me from restoring. Some facts:
- New bootrom
- Corona untethered jb does not work
- Attempts to put in pwned DFU using redsn0w/iREB do not work, iTunes gives random errors (2005, not eligible for this requested build etc)
- No shsh blobs I know of
- Running the 06.15.00 baseband
I would like to install the untethered JB. I have made the ipsw using snowbreeze but since restoring does not work I cannot do anything with it. Could anyone please help me with this please?
Thank you all so much
Edit: From what I can tell, it's possible I updated it with the wrong 5.0.1 custom FW that is for the old bootrom, and not the new as it should be, since it says on redsn0w that if the production week from the serial number is <45 it should be old (which my SN indicated). Though looking on the system profiler on OSX now I can see it is the new bootrom, so I'm pretty sure this is the root of the problem causing all the strange behaviour.
Last edited: