Originally Posted by nmiklas21

Understood!Probably jailbreaking with custom 4.1 will fail also, so my last chance will be the custom pwnage tool, whenever you are ready with it, tell me how we can proceed.
Thanks again

not probably. It will fail.
You cannot restore stock firmware 4.1 or custom firmware 4.1 without a valid SHSH for that particular firmware version.

The custom firmware 4.2.1 that Olethros is evaluating can be used because at this time Apple is still signing it during the restore process.
What you need to do now is SAVE your 4.2.1 SHSH with tinyumbrella.

Just wait for Olethros to finish his testings

Originally Posted by dtube

Just wait for Olethros to finish his testings

Well, I managed to restore from 4.1 to 4.2.1 with special pwnagetool custom IPSW & TinyUmbrella - this did NOT update my baseband or send my phone into a bootlopp (as just restoing to 4.2.1 with TinyUmbrella does)

Then I jailbroke with redsn0w and it all seems okay now. Still testing. Might not need TinyUmbrella.

Originally Posted by Olethros

Well, I managed to restore from 4.1 to 4.2.1 with special pwnagetool custom IPSW & TinyUmbrella - this did NOT update my baseband or send my phone into a bootlopp (as just restoing to 4.2.1 with TinyUmbrella does)

good to hear, i may give it a run :-).
yeah the bootloop is because stock fw will have BB update enabled and custom disabled it.

Then I jailbroke with redsn0w and it all seems okay now. Still testing. Might not need TinyUmbrella.

no need while apple still signing 4.2.1 but you will probably need it for restore custom fw when Apple decides to stop it.

Originally Posted by dtube

good to hear, i may give it a run :-).
yeah the bootloop is because stock fw will have BB update enabled and custom disabled it.

no need while apple still signing 4.2.1 but you will probably need it for restore custom fw when Apple decides to stop it.

I tried the solution provided by olethros, but nothing different happen, we got the 1600 error,on the next test 1604, the phone still remained in DFU mode. I finally tried a simple restore directly from itunes without tiny umbrella running or anything else and I got a 1013 error or something like that. The only good news are that during the last restore with itunes the phone's screen openened and the itunes logo appeared, obviously now is on recovery mode, also tiny umbrella can ''see'' the phone now and (I don't know how) the phone appears to have fm 4.1 and bb 1.59.00. I have selected from tiny umbrella the option kick out from recovery mode and the phone stucks with the silver apple on the screen. Turn it off and on and the phone is on recovery mode. Any suggestions now? Should I try just tethered jailbreak with redsnow?

Originally Posted by nmiklas21

I tried the solution provided by olethros, but nothing different happen, we got the 1600 error,on the next test 1604, the phone still remained in DFU mode. I finally tried a simple restore directly from itunes without tiny umbrella running or anything else and I got a 1013 error or something like that. The only good news are that during the last restore with itunes the phone's screen openened and the itunes logo appeared, obviously now is on recovery mode, also tiny umbrella can ''see'' the phone now and (I don't know how) the phone appears to have fm 4.1 and bb 1.59.00. I have selected from tiny umbrella the option kick out from recovery mode and the phone stucks with the silver apple on the screen. Turn it off and on and the phone is on recovery mode. Any suggestions now? Should I try just tethered jailbreak with redsnow?

When you made the custom 4.2.1 IPSW I provided, did you then put the phone into pwned dfu mode (either via pwnagetool or via redsn0w 0.9.6?). This is required to restore custom IPSW from iOS 4.1 and higher.

This is NOT the same as simply putting the iPhone into DFU mode.
The 1600 error is likely connected to this. The 1604 error maybe also.

Originally Posted by Olethros

When you made the custom 4.2.1 IPSW I provided, did you then put the phone into pwned dfu mode (either via pwnagetool or via redsn0w 0.9.6?). This is required to restore custom IPSW from iOS 4.1 and higher.

This is NOT the same as simply putting the iPhone into DFU mode.
The 1600 error is likely connected to this. The 1604 error maybe also.

The phone was in dfu mode all these days,but just in case I was following the instruction of pwnage tool (hold power+home button etc). Pwnage recognised that the phone is in dfu mode and the whole process seemed to go smoothly until the end that I had the errors in iTunes. The strange is that the screen didn't respond at all, the phone didn't reboot just remained with a black screen as on the other attempts I did the previous days. Is it possible to be a hardware issue? Even restoring directly from itunes failed..

Originally Posted by nmiklas21

The phone was in dfu mode all these days,but just in case I was following the instruction of pwnage tool (hold power+home button etc). Pwnage recognised that the phone is in dfu mode and the whole process seemed to go smoothly until the end that I had the errors in iTunes. The strange is that the screen didn't respond at all, the phone didn't reboot just remained with a black screen as on the other attempts I did the previous days. Is it possible to be a hardware issue? Even restoring directly from itunes failed..

It's possible that there is a hardware problem - but it's unlikely - There is a difference between DFU mode and pwned DFU mode. Also, you cannot have iTunes running while you try and enter Pwned DFU mode.

Originally Posted by nmiklas21

The phone was in dfu mode all these days,but just in case I was following the instruction of pwnage tool (hold power+home button etc). Pwnage recognised that the phone is in dfu mode and the whole process seemed to go smoothly until the end that I had the errors in iTunes. The strange is that the screen didn't respond at all, the phone didn't reboot just remained with a black screen as on the other attempts I did the previous days. Is it possible to be a hardware issue? Even restoring directly from itunes failed..

Please be thorough in reading the responses -- we're not talking about DFU mode, we're talking about "Pwned DFU" mode, which is something different, provided by the exploits in the more recent jailbreaks that allow these devices to restore custom firmware. You can access this by using PwnageTool or redsn0w -- you cannot access Pwned DFU mode in any other way, and standard DFU mode will NOT allow you to restore a custom firmware.

hi friends i am facing such problem please help me.
hxxp://forum.iphone-developers.com/hacking-jailbreaking-modding/798-iphone4-stuck-dfu-mode-help.html

from where i can get custom activated baseband preserved 01.59.00 iOS 4.2.1 for my i