I am triying to fix my iphone 3g which is stuck in recovery mode. All attemps to restore with Itunes fail with error 6, also when starting restore from DFU mode.
The restore log is quite long but sais:

"
2010-11-11 19:55:43.077 [1728:c1c]: iTunes: Creating restore mode device with usbMuxDeviceID 0X9
2010-11-11 19:55:43.077 [1728:c1c]: <Restore Device 067A8D58>: operation 3 progress -1
2010-11-11 19:55:43.085 [1728:c1c]: <Restore Device 067A8D58>: operation 4 progress -1
2010-11-11 19:55:43.102 [1728:c1c]: Supports value queries: 1
2010-11-11 19:55:43.153 [1728:4c8]: <Restore Device 067A8D58>: operation 44 progress -1
2010-11-11 19:55:43.155 [1728:4c8]: requested restore behavior: Erase
2010-11-11 19:55:43.177 [1728:4c8]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
2010-11-11 19:55:43.207 [1728:4c8]: device did not return saved USB log
2010-11-11 19:55:43.208 [1728:4c8]: device did not return saved panic log
2010-11-11 19:55:43.208 [1728:4c8]: previous restore failed with exit status 0x100
2010-11-11 19:55:43.225 [1728:4c8]: connected to service com.apple.mobile.restored
2010-11-11 19:55:43.225 [1728:4c8]: using protocol version 12
2010-11-11 19:55:43.236 [1728:4c8]: unable to open device_map.txt: No such file or directory
2010-11-11 19:55:43.237 [1728:4c8]: board config = n82ap
2010-11-11 19:55:43.275 [1728:4c8]: <Restore Device 067A8D58>: operation 28 progress -1
2010-11-11 19:56:02.049 [1728:4c8]: <Restore Device 067A8D58>: operation 11 progress -1
2010-11-11 19:56:02.099 [1728:4c8]: device returned AMR error 6
2010-11-11 19:56:02.136 [1728:4c8]:
"

so it seems that it cannot write in the EEPROM. Can someone help me track the problem? Ican post the complete log if needed. Is there another way than through itune to write the firmware in the iphone?
Many thanks in advance and PLEASE don't tell me that my Iphone is fried...sniff...

Please help....I'm desperate.

Update and restore alert messages on iPhone, iPad, iPod touch and Apple TV (2nd generation)

Error 6: All of the steps in this article apply to resolve this issue. Following iTunes for Windows: Troubleshooting security software frequently resolves this error. There may be third-party software installed that modifies your default packet size in Windows by inserting a TcpWindowSize entry into your Registry. If your default packet size is set incorrectly it can cause this error. Contact the manufacturer of the software that installed the packet size modification for assistance.

Not enter the downgrading mode, change USB port (the back one of chassis is better) and restart computer.

Or try a different computer etc

Publish (on a pastesite) the full restore log if troubleshooting of USB (and if you are using windows - security software) doesn't help

Thanks for the reply Olethros, may I ask you for some more help?

I tried with 2 different PC and a Mac with a different cable, so it's the iphone.
The iphone is stuck in recovery but I succeed putting it in DFU mode. It is recognized by the PC, starts the restore until the apple with the progress bar apears. Before any progress is shown the error 6 shows up.

The log under recovery mode shows more information:
.....
effaceable storage is formatted, clearing it
effaceable storaged cleared
entering check_for_restore_log
executing /sbin/fsck_hfs
.....here comes the errors....

..... and towards the end of the log
** /dev/rdisk0s1
Executing fsck_hfs (version diskdev_cmds-488.1.7~237).
** Checking non-journaled HFS Plus Volume.
** Detected a case-sensitive volume.
** Checking extents overflow file.
** Checking catalog file.
** Checking multi-linked files.
** Checking catalog hierarchy.
** Checking extended attributes file.
** Checking volume bitmap.
** Checking volume information.
** The volume Apex8A293.iPhoneOS appears to be OK.
executing /sbin/mount
4475)
[FTL:WRN] _AddLbnToRefreshList(0x7, 0x5FF) failed adding new block to list - list is full!!! (line:4520)!
.......

.....So at the end of the log:
[Path /dev/disk0s1] [FSLogMsgID 1652590088] [FSLogMsgOrder Last]
error unmounting '/mnt1': Device not configured
WARNING: unable to unmount partition
......


So it looks like the volume /disk0s1 is having problems. Is there another program as itune restore the iphone? Are there some checks to control the hardware status?

thanks again for your help

Originally Posted by Bricolux

[FTL:WRN] _AddLbnToRefreshList(0x7, 0x5FF) failed adding new block to list - list is full

Again, I can't be 100% sure without seeing the full log. Also you do understand that the part of the "restore log" you are quoting is actually the logged iPhone portion of the previous failed restore.

The specific error I have highlighted suggests that the problem is with your NAND chip - the error is saying that the FTL (flash translation layer) has used up all the entries it keeps reserved for mapping of bad blocks.

You're pretty much in hardware territory, even if you found a software way to tell the FTL to setup the NAND from scratch - you risk that the problem will re-occur when you start to use the NAND again.

Thanks again for your help. So you mean there is a fried NAND gate? is this a NAND gate inside the flash rom chip or is it a separate chip?
Indeed the all errors are FTL something. may I send you the log file for a quick check?

I don't have a block diagram of the iphone, so I don't know what this NAND exachtely does. But do you think draining the battery would do a reset?

Originally Posted by Bricolux

Thanks again for your help. So you mean there is a fried NAND gate? is this a NAND gate inside the flash rom chip or is it a separate chip?
Indeed the all errors are FTL something. may I send you the log file for a quick check?

Originally Posted by Bricolux

I don't have a block diagram of the iphone, so I don't know what this NAND exachtely does. But do you think draining the battery would do a reset?

The NAND is what stores the operating system and your personal files (music, apps etc)

On your model iPhone - only the very early boot files (equivalent to the BIOS on a windows PC) are located elsewhere than the NAND.

The thing about NAND (flash memory) is that it is not suited to being used directly by a regular operating system. The FTL is the flash memory controller and performs several functions including wear levelling and reallocation of bad blocks. To be honest, I think your NAND is failing.

Draining the battery won't help.

OK...the NAND chip is the 16G eeprom... after a quick search I found a block diagram of the iphone, so things are getting clearer. So it's almost impossible to fix.....bouhouhou