Please Help! It's day 3.....I still have fail to Restore:
1600/1601 errors have no end! I will try to give as much detail about what has happened so far.
Phone: 3GS on 3.1.3 New bootrom (No SHSH saved...Just got it and could only save at 4.1).

Worked fine-original-never jailbroken... I am able to put the phone in DFU mode and START a restore, but then iTunes 10.x.x (latest) will give me the 1600 (or similar) error when I try to restore to the latest Custom firmware (from latest pwnage 4.1.2). I've tried just about everything. I'm open to any advice to get this phone working again JB & Unlocked @ OS4.1.

Tried 3 different PCs:
1. HP XP 10.x.x latest iTunes...Full uninstal+reinstall. (This is the MAIN computer and this is where the log is from).(Sauriks URL in my HOSTS file). This computer has done restores before (but not Custom restores...).
2. HP Vista 8.x iTunes
3. Dell XP 9.x iTunes

Of course I tried both DFU (error 16xx) and Restore Mode (error 21). I also looked for those files mentioned in the iTunes file directory (Device Support/...), but I have no such folder (after reinstalling). It was there before and I deleted the contents as instructed to no success either. Same thing with x12220000_4_Recovery.ispw.

The Original 4.1 Firmware however is passing the error stage where the iTunes says Preparing Ipone for Restore and the White screen shows on the iPhone, Then apple logo, and then the oval circle where it starts to save the files into the iPhone(Progress bar)....as I have done on 3G's and iPods in the past.....Of course I IMMEDDIATELY before the bar starts I remove the USB cord/or "End-task" iTunes because I dont want to update the baseband (I need to be able to unlock). Based on this, I don't think that anything is wrong with the USB port/settings.

I have tried 3 different firmware (One I cooked on Pwnage 4.1.2 myself on a mac, and one I downloaded from Rapidshare. Still no go.

I tried using different USB ports and a different 30 pin connector cable.

I'm at your mercy. 3 days on it....and yesterday I went to sleep at about 6:00am...This is driving me crazy.

I hope the log files are of help:
Last log file: http://pastebin.com/jqqAJK70
One in the middle: http://pastebin.com/kbVuXXbX
1st log file: http://pastebin.com/c4ycB3av

Did u try ireb for ih8sn0w?
And the restore?

iH8sn0w.com | Jailbreak your iPod touches and iPhones

If not, try a mac.

As explained more than once on this forum recently:

(and also clearly stated on the pwnagetool 4.1.2 release info at Dev-Team Blog )

PwnageTool 4.1's DFU mode is more than just your normal DFU mode.

Those who use windows need to keep this in mind.

As of yesterday, you have a two-part solution:

PwnageTool 4.1.2 custom IPSW (made on mac) + Redsn0w 0.9.6b2 (run on windows to put your iPhone into pwnagetool DFU mode)

see http://www.hackint0sh.org/f206/183546.htm for more details.

Also @lamanodedios - how many times do we have to say that we don't support or recommend any ih8sn0w software here (that includes f0recast, iREB and sn0wbreeze amongst others). These tools aren't updated with the latest exploits and can be dangerous if people use them without knowing their limitations.

Thanks,
That did it. Had to enter DFU mode with Redsn0w 0.9.6b2 on Windows computer. Was VERY tricky though because the phone was stuck on apple logo (Could not Turn Off/Only DFU or Restore)....after some attempts and while the progress bar was moving from left to right I decided to keep holding the "Home" button...till I noticed that the progress bar went all the way though and I got the message "Succesfully Enter DFU mode". Then after that I resore the custom firmware wit iTunes. Thanks...

Now I have another problem: The WiFi never turns off and kills the battery overnight. I use the SBSetting WiFi toggle manually when I can but I usually fall asleep with the music (TuneIn Radio/Streaming). I will look for this on other threads and if I see no solution, I will start new one.
Thanks

Originally Posted by webassist

Thanks,
That did it. Had to enter DFU mode with Redsn0w 0.9.6b2 on Windows computer. Was VERY tricky though because the phone was stuck on apple logo (Could not Turn Off/Only DFU or Restore)....after some attempts and while the progress bar was moving from left to right I decided to keep holding the "Home" button...till I noticed that the progress bar went all the way though and I got the message "Succesfully Enter DFU mode". Then after that I resore the custom firmware wit iTunes. Thanks...

Now I have another problem: The WiFi never turns off and kills the battery overnight. I use the SBSetting WiFi toggle manually when I can but I usually fall asleep with the music (TuneIn Radio/Streaming). I will look for this on other threads and if I see no solution, I will start new one.
Thanks

Wifi should turn off when the screen has been locked for 30 minutes. I'm running 3GS + custom IPSW from pwnagetool 3.1.2 with baseband 4.26.08 and have no such problem.

Have you installed anything else after the unlock?

Did you restore from iTunes backup?

I know this is not the case, but this thread reminded of a recent problem I've faced with one of my test 3GS, that may help other folks in a similar situation: 3GS phones may fail to restore with 4.1 and 4.2 if they have their battery replaced with an OEM/after market one.

The reason is a hardware difference in the battery circuitry and 4.1 and 4.2 (did not test 4.0.x) will update the battery firmware (probably to make it last longer?). Some OEM batteries will not respond correctly and the update will fail with errors codes 21, 28 and 29. As a result the phone will be stuck in a "restore mode" reboot loop.

Under 4.1 it may be possible to get out of the loop with the standard "setenv auto-boot yes, saveenv, reboot" magic (several programs can do it, but all use the same commands update the NVRAM), but in roughly 9 out of 10 restore attempts followed by several "kick out of restore mode" it will stay in the loop. Under 4.2 GM I was never able to get it out of the loop.

Placing an original battery back in the 3GS allowed it to restore 4.1 and 4.2GM flawlessly.

Firmware 3.1.3 restore without problems with either battery.

Originally Posted by aviegas

I know this is not the case, but this thread reminded of a recent problem I've faced with one of my test 3GS, that may help other folks in a similar situation: 3GS phones may fail to restore with 4.1 and 4.2 if they have their battery replaced with an OEM/after market one.

The reason is a hardware difference in the battery circuitry and 4.1 and 4.2 (did not test 4.0.x) will update the battery firmware (probably to make it last longer?). Some OEM batteries will not respond correctly and the update will fail with errors codes 21, 28 and 29. As a result the phone will be stuck in a "restore mode" reboot loop.

Under 4.1 it may be possible to get out of the loop with the standard "setenv auto-boot yes, saveenv, reboot" magic (several programs can do it, but all use the same commands update the NVRAM), but in roughly 9 out of 10 restore attempts followed by several "kick out of restore mode" it will stay in the loop. Under 4.2 GM I was never able to get it out of the loop.

Placing an original battery back in the 3GS allowed it to restore 4.1 and 4.2GM flawlessly.

Firmware 3.1.3 restore without problems with either battery.

Thanks very much for this info, is there anything in the restore logs that will indicate that it is the after market battery at fault?

Originally Posted by Olethros

Thanks very much for this info, is there anything in the restore logs that will indicate that it is the after market battery at fault?

You will see something like this:

Code:

entering update_device_firmware
entering update_iBoot
write_image3_data: flashing LLB data (length = 0x241d0)
write_image3_data: flashing NOR data (length = 0x2a984)
write_image3_data: flashing NOR data (length = 0xbcc4)
write_image3_data: flashing NOR data (length = 0x2604)
write_image3_data: flashing NOR data (length = 0xa894)
write_image3_data: flashing NOR data (length = 0xdbc4)
write_image3_data: flashing NOR data (length = 0xfd04)
write_image3_data: flashing NOR data (length = 0x4fc4)
write_image3_data: flashing NOR data (length = 0x4bc4)
write_image3_data: flashing NOR data (length = 0x4d44)
write_image3_data: flashing NOR data (length = 0x6184)
write_image3_data: flashing NOR data (length = 0x12a44)
entering update_gas_gauge
0: RamrodErrorDomain/3ea: update_gas_gauge: gasgauge_swupdate returned -1
attempting to dump restore log
writing log file: /mnt1/restore.log

and like this:

Code:

entering update_NOR
entering img3_update_NOR
img3_flash_NOR_image: flashing LLB data (length = 0xf999)
img3_flash_NOR_image: flashing NOR data (length = 0x2a9d9)
img3_flash_NOR_image: flashing NOR data (length = 0xbc19)
img3_flash_NOR_image: flashing NOR data (length = 0x2619)
img3_flash_NOR_image: flashing NOR data (length = 0xb259)
img3_flash_NOR_image: flashing NOR data (length = 0xdbd9)
img3_flash_NOR_image: flashing NOR data (length = 0xfd19)
img3_flash_NOR_image: flashing NOR data (length = 0x4fd9)
img3_flash_NOR_image: flashing NOR data (length = 0x4bd9)
img3_flash_NOR_image: flashing NOR data (length = 0x4d59)
img3_flash_NOR_image: flashing NOR data (length = 0x6199)
img3_flash_NOR_image: flashing NOR data (length = 0x12a59)
entering create_system_key_bag
attempting to create system key bag on /mnt2
entering update_IR_MCU
looking for mcu nub...no entry from path!
TiSerialFlasher not supported on this platform. Exiting.
entering update_gas_gauge_software
booted from secure root: give device keybag access to everyone
AppleKeyStore:cp_key_store_action(1)
should not be here 1AppleKeyStore:cp_key_store_action(1)
gasgauge_swupdate failed: -1
attempting to dump restore log
writing log file: /mnt1/restore.log

In both parts for the update log file you will see that
gasgauge_swupdate failed.

Originally Posted by aviegas

You will see something like this:
...
In both parts for the update log file you will see that
gasgauge_swupdate failed.

I was actually thinking it would related to gasgauge, I saw similar errors on 3.1.3 (which also had a battery firmware update I guess). What I didn't know was that this was related to aftermarket batteries

Originally Posted by Olethros

I was actually thinking it would related to gasgauge, I saw similar errors on 3.1.3 (which also had a battery firmware update I guess). What I didn't know was that this was related to aftermarket batteries

It took me quite a while to figure out that it could be related to the battery. First, because it may work on 4.1, I was able to restore on 4.1 once. But when I tried with 4.2GM, I could not get it to work at all. I kept getting errors 21/28/29 (depending on the process used to restore), and I was wrongly associating the problem with the firmware manipulation I was using to prevent the baseband upgrade (I've tried 3 different methods).

Replacing the battery with an Apple original made the restore flawless, and I even repeated it a few times to be sure. The same happened with other 3GS I have access to (family) that had the battery replaced.

In any case, it was not easy to find references in Google about it. Too many references to people that were able to kick it out of restore with this or that tools (all using the same method to fix the NVRAM to autoboot). But a search to "gasgaue 3gs" show reports as early as June... Once you know what to search for, it becomes clear.