iPhone 3gs stuck in DFU loop, can't restore

[viliuset]

My iPhone was stuck in DFU loop after trying to upgrate to 4.2.1 from jaibreaked 4.1. I know, I'm stupid, but that was my first day having iPhone, I did not know much about it.
Now it is in DFU loop, can't turn the phone on or see any logo on it. Tried to install official, also custom firmware on my own Mac and also tried on my friends Mac. Didn't work out. When trying to install official firmware it says that this device is eligible for chosen software or got error 28. When trying to install custom firmware got the error 1600.

Please help if you had similar situation.
Thanks in advance

[i.Annie]

With error 28, let the battery drain. I'm assuming you probably don't want to open the phone up and take the battery out...but if you're comfortable doing that it would be faster than letting the battery drain. But after draining the battery, try restoring again to a custom 4.2.1 firmware.

[viliuset]

but where do I get custom 4.2.1 firmware?
and I suppose it takes long time for battery to drain by itself without opening the phone, doesn't it?

btw, will I be able to downgrade it to jailbreaked 4.1? I think my bootrom is the new one.

[i.Annie]

It could take a couple days to a week to drain the battery depending on how much you had left.

You can ask x98car for the custom firmware if you don't have PwnageTool to make it yourself. You could try restoring to a stock 4.2.1 as well it should be fine. You can only downgrade with SHSHs. You should check for SHSHs if you can.

[viliuset]

It could take a couple days to a week to drain the battery depending on how much you had left.

You can ask x98car for the custom firmware if you don't have PwnageTool to make it yourself. You could try restoring to a stock 4.2.1 as well it should be fine. You can only downgrade with SHSHs. You should check for SHSHs if you can.

ok. I drained the battery out. Now I can see iTunes logo and it's out of DFU loop.
But still cannot restore to any custom either official firmware. Getting errors 16xx and when tried on windows using iReb to fix 16xx got 3xxx error.
ay ideas?

[i.Annie]

Have you tried to restore to a regular 4.2.1 firmware

[max414]

ok. I drained the battery out. Now I can see iTunes logo and it's out of DFU loop.
But still cannot restore to any custom either official firmware. Getting errors 16xx and when tried on windows using iReb to fix 16xx got 3xxx error.
ay ideas?

to solve errors 16xx , start tss server option on tiny umbrella and try with restore

[iYeow]

ok. I drained the battery out. Now I can see iTunes logo and it's out of DFU loop.
But still cannot restore to any custom either official firmware. Getting errors 16xx and when tried on windows using iReb to fix 16xx got 3xxx error.
ay ideas?

If you want to restore to custom firmware, you need to run redsn0w 0.9.6 any beta version, browse to stock firmware and use it to put you into dfu mode before you can restore to cfw thru itunes.

[thehumble1]

I got out of DFU mode by using iREB to put it in PWNED DFU then loaded a Sn0wbreeze custom 4.1 IPSW then I used Redsn0w 0.9.6b5 to JB and knock it out of the DFU loop. I know this won't work completely for 4.2.1 because Sn0wbreeze doesn't work with 4.2 nor does Redsn0w right? I think that like iYeow said though Redsn0w 0.9.6XX will put it in PWNED DFU which is what you need for most custom FM to take without errors. Some errors are okay though and you can ignore them as long as it went through the process of loading and verifying the firmware. If you've got that far, go ahead and JB it with Redsn0w and see if it took.

I don't think TU will fix 16xx errors. That's done with PWNED DFU afaik. TU will keep you from getting "this device is not eligible for chosen software" error.

[GrandMstrBud]

Has anyone found a resolution for this yet? I have a 3GS that is also suck in a recovery loop.

[EpicGamer]

but it into dfu mode then do a clean restore then maybe do a custom fw upgrade

[iYeow]

Has anyone found a resolution for this yet? I have a 3GS that is also suck in a recovery loop.

when you say recovery mode, you should also let us know the error code, not just recovery mode