Wont Restore Error 29. What Now iPhone 3G

This is a phone which I dont know the history of. It was given to me today to see if I can get it going. So far, when attempting to restore it, I get Error 29. I believe OS4 was installed prior to this issue but Im not sure. Heres the details. Thanks for your help.2010-09-01 22:35:46.000 iTunes1936:20b: restore library built Jun 4 2010 at 01:46:122010-09-01 22:35:46.000 iTunes1936:20b: iTunes: iTunes 9.2.12010-09-01 22:35:46.000 iTunes1936:20b: iTunes: Software payload version: 8A4002010-09-01 22:35:46.000 iTunes1936:148cf: iTunes: Specifying UOI boot image2010-09-01 22:35:46.000 iTunes1936:148cf: requested restore behavior: Erase2010-09-01 22:35:46.000 iTunes1936:148cf: amai: AMAuthInstallPlatformCreateBufferFromNativeFilePath: open failed: No such file or directory2010-09-01 22:35:46.000 iTunes1936:148cf: amai: AMAuthInstallHttpMessageSendSync: httpRequest=<CFHTTPMessage 0x19d92cf0>{url = http://gs.apple.com:80/TSS/controller?action=2; request = POST /TSS/controller?action=2 HTTP/1.1}2010-09-01 22:35:47.000 iTunes1936:148cf: amai: AMAuthInstallRequestSendSync: received tss response (server version: 0.6.31-b2)2010-09-01 22:35:48.000 iTunes1936:148db: iBoot build-version = iBoot-889.242010-09-01 22:35:48.000 iTunes1936:148db: iBoot build-style = RELEASE2010-09-01 22:35:48.000 iTunes1936:148db: DeviceRequest failed: 0xe000404f2010-09-01 22:35:48.000 iTunes1936:148db: command device request for getenv radio-error failed: 20082010-09-01 22:35:48.000 iTunes1936:148db: radio-error not set2010-09-01 22:35:48.000 iTunes1936:148db: unable to open device_map.txt: No such file or directory2010-09-01 22:35:48.000 iTunes1936:148db: <Recovery Mode Device 0x1b03ef20>: production fused device2010-09-01 22:35:48.000 iTunes1936:148db: <Recovery Mode Device 0x1b03ef20>: operation 4 progress -12010-09-01 22:35:48.000 iTunes1936:148db: bootstrapping restore with iBEC2010-09-01 22:35:48.000 iTunes1936:148db: <Recovery Mode Device 0x1b03ef20>: operation 31 progress -12010-09-01 22:35:49.000 iTunes1936:148db: <Recovery Mode Device 0x1b03ef20>: Recovery mode succeeded2010-09-01 22:35:49.000 iTunes1936:20b: device disconnected (isDFU = 0)2010-09-01 22:35:53.000 iTunes1936:20b: device connected (isDFU = 0)2010-09-01 22:35:53.000 iTunes1936:20b: iTunes: SCEP 32010-09-01 22:35:53.000 iTunes1936:1862b: iBoot build-version = iBoot-889.242010-09-01 22:35:53.000 iTunes1936:1862b: iBoot build-style = RELEASE2010-09-01 22:35:53.000 iTunes1936:1862b: DeviceRequest failed: 0xe000404f2010-09-01 22:35:53.000 iTunes1936:1862b: command device request for getenv radio-error failed: 20082010-09-01 22:35:53.000 iTunes1936:1862b: radio-error not set2010-09-01 22:35:53.000 iTunes1936:1862b: <Recovery Mode Device 0x1c09d160>: operation 44 progress -12010-09-01 22:35:53.000 iTunes1936:1862b: requested restore behavior: Erase2010-09-01 22:35:53.000 iTunes1936:1862b: amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done2010-09-01 22:35:53.000 iTunes1936:1862b: unable to open device_map.txt: No such file or directory2010-09-01 22:35:53.000 iTunes1936:1862b: <Recovery Mode Device 0x1c09d160>: production fused device2010-09-01 22:35:53.000 iTunes1936:1862b: <Recovery Mode Device 0x1c09d160>: operation 4 progress -12010-09-01 22:35:53.000 iTunes1936:1862b: <Recovery Mode Device 0x1c09d160>: operation 42 progress -12010-09-01 22:35:54.000 iTunes1936:1862b: <Recovery Mode Device 0x1c09d160>: operation 5 progress -12010-09-01 22:35:55.000 iTunes1936:1862b: DeviceRequest failed: 0xe000404f2010-09-01 22:35:55.000 iTunes1936:1862b: command device request for getenv ramdisk-delay failed: 20082010-09-01 22:35:57.000 iTunes1936:1862b: <Recovery Mode Device 0x1c09d160>: operation 6 progress -12010-09-01 22:35:58.000 iTunes1936:1862b: <Recovery Mode Device 0x1c09d160>: operation 7 progress -12010-09-01 22:35:59.000 iTunes1936:1862b: <Recovery Mode Device 0x1c09d160>: operation 8 progress -12010-09-01 22:35:59.000 iTunes1936:1862b: <Recovery Mode Device 0x1c09d160>: operation 9 progress -12010-09-01 22:35:59.000 iTunes1936:1862b: <Recovery Mode Device 0x1c09d160>: Recovery mode succeeded2010-09-01 22:36:04.000 iTunes1936:20b: device disconnected (isDFU = 0)2010-09-01 22:36:04.000 iTunes1936:20b: _AMRecoveryModeDeviceFinalize: 0x1c09d1602010-09-01 22:36:08.000 iTunes1936:20b: iTunes: received kAMDeviceAttached action, device 0x1c0b4a30, AFC error 0XE80000282010-09-01 22:36:08.000 iTunes1936:20b: iTunes: Restore-mode device appeared, device 0x1c0b4a302010-09-01 22:36:08.000 iTunes1936:20b: iTunes: Creating restore mode device with usbMuxDeviceID 0X12010-09-01 22:36:08.000 iTunes1936:20b: <Restore Device 0x1c0c5070>: operation 3 progress -12010-09-01 22:36:08.000 iTunes1936:20b: <Restore Device 0x1c0c5070>: operation 4 progress -12010-09-01 22:36:08.000 iTunes1936:20b: Supports value queries: 12010-09-01 22:36:08.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 44 progress -12010-09-01 22:36:08.000 iTunes1936:1788f: requested restore behavior: Erase2010-09-01 22:36:08.000 iTunes1936:1788f: amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done2010-09-01 22:36:08.000 iTunes1936:1788f: device did not return saved USB log2010-09-01 22:36:08.000 iTunes1936:1788f: device did not return saved panic log2010-09-01 22:36:08.000 iTunes1936:1788f: previous restore failed with exit status 0x1002010-09-01 22:36:08.000 iTunes1936:1788f: connected to service com.apple.mobile.restored2010-09-01 22:36:08.000 iTunes1936:1788f: using protocol version 122010-09-01 22:36:08.000 iTunes1936:1788f: unable to open device_map.txt: No such file or directory2010-09-01 22:36:08.000 iTunes1936:1788f: board config = n88ap2010-09-01 22:36:08.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 28 progress -12010-09-01 22:36:22.000 iTunes1936:1788f: previous restore failed: sOTGDevice::start : start finishedAppleMultitouchN1SPI: detected HBPP. driver will be kept aliveAppleM2ScalerCSCDriver: Added framebuffer device: AppleM2TVOut id: 81b4f800IOSDIOController::enumerateSlot(): Searching for SDIO device in slot: 0IOSDIOController::enumerateSlot(): Found SDIO I/O device. Function count(1), memory(0)read new style signature 0x43313133 (line:405)FTL:MSG VSVFL Register OKFTL:MSG VFL Init OKIOSDIOIoCardDevice::parseFn0CIS(): Device manufacturer ID 0x2d0, Product ID 0x4325IOSDIOIoCardDevice::parseFn0CIS(): Manufacturer: IOSDIOIoCardDevice::parseFn0CIS(): Product: IOSDIOIoCardDevice::parseFn0CIS(): ProductInfo0: s=D1IOSDIOIoCardDevice::parseFn0CIS(): ProductInfo1: P=N88 m=3.2AppleBCMWLAN::init(): AppleBCMWLAN-42 Aug 4 2010 18:51:11AppleBCMWLAN::init(): Starting with debug level: 4, debug flags: 00000000AppleBCMWLAN::init(): AppleBCMWLAN-42 Aug 4 2010 18:51:11AppleBCMWLAN::init(): Starting with debug level: 4, debug flags: 00000000FTL:MSG VFL_Open OKFTL:MSG YAFTL Register OKfound suitable IOMobileFramebuffer: AppleM2CLCDdisplay-scale = 1display-rotation = 0found PTP interfaceFTL:MSG FTL_Open OKAppleSynopsysOTGDevice - Configuration: PTPAppleSynopsysOTGDevice Interface: PTPAppleSynopsysOTGDevice - Configuration: iPod USB InterfaceAppleSynopsysOTGDevice Interface: USBAudioControlAppleSynopsysOTGDevice Interface: USBAudioStreamingAppleSynopsysOTGDevice Interface: IapOverUsbHidAppleSynopsysOTGDevice - Configuration: PTP + Apple Mobile DeviceAppleSynopsysOTGDevice Interface: PTPAppleSynopsysOTGDevice Interface: AppleUSBMuxAppleSynopsysOTGDevice - Configuration: PTP + Apple Mobile Device + Apple USB EthernetAppleSynopsysOTGDevice Interface: PTPAppleSynopsysOTGDevice Interface: AppleUSBMuxAppleSynopsysOTGDevice Interface: AppleUSBEthernetAppleSynopsysOTGDevice::gated_registerFunction Register function USBAudioControlAppleSynopsysOTGDevice::gated_registerFunction Register function USBAudioStreamingIOAccessoryPortUSB::startAppleSynopsysOTGDevice::gated_registerFunction Register function IapOverUsbHidvirtual bool AppleUSBDeviceMux::start(IOService*) build: Aug 4 2010 18:51:30init_wasteAppleSynopsysOTGDevice::gated_registerFunction Register function AppleUSBMuxAppleSynopsysOTGDevice::gated_registerFunction Register function AppleUSBEthernetAppleUSBEthernetDevice::start: Device MAC address = 0a:0b:ad:0b:ab:e0AppleUSBEthernetDevice::start: Host MAC address = 00:26:b0:92:35:00AppleSynopsysOTGDevice::gated_registerFunction Register function PTPAppleSynopsysOTGDevice::gated_registerFunction all functions registered- we are ready to start usb stackAppleS5L8720XUSBPhy::powerUp : _powered: 0AppleEmbeddedUSBArbitrator::enableDeviceClock : enable: 1, index: 0virtual IOReturn AppleUSBDeviceMux::setProperties(OSObject*) setting debug level to 7AppleSynopsysOTGDevice::handleUSBResetAppleSynopsysOTGDevice::handleUSBResetclose(caller = 0x5695): remote port = 49152close(caller = 0x5695): remote port = 49153close(caller = 0x5695): remote port = 49154client protocol version 12Restore options:SystemPartitionSize => <CFNumber 0xb058e0 0x1a9d5c>{value = +750, type = kCFNumberSInt64Type}entering partition_nand_devicedevice is not a boot-from-NAND deviceentering wait_for_storage_deviceentering format_effaceable_storageeffaceable storage is formatted, clearing iteffaceable storaged clearedentering check_for_restore_logexecuting /sbin/fsck_hfsAppleUSBDeviceMux::handleConnectResult new session 0x83460200 established 62078<-lo0->49152 62078<-usb->13568void AppleUSBDeviceMux::handleMuxTCPInput(__mbuf*) received reset, closing 0x83460200AppleUSBDeviceMux::handleConnectResult new session 0x83460100 established 62078<-lo0->49153 62078<-usb->13824AppleUSBDeviceMux::sessionUpcall socket is closed, session 0x83460100 (62078<-lo0->49153 62078<-usb->13824)AppleUSBDeviceMux::handleConnectResult new session 0x83460200 established 62078<-lo0->49154 62078<-usb->14080AppleUSBDeviceMux::sessionUpcall socket is closed, session 0x83460200 (62078<-lo0->49154 62078<-usb->14080)AppleUSBDeviceMux::handleConnectResult new session 0x83460180 established 62078<-lo0->49155 62078<-usb->14336/dev/rdisk0s1 Executing fsck_hfs (version diskdev_cmds-488.1.7~39).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 Apex8A400.N88OS appears to be OK.executing /sbin/mountfound restore log (size = 11825)entering create_filesystem_partitionsNAND format completecreating encrypted data partitionwipe entire partition: 1 (old = 0 new = 750)block size for /dev/disk0s1: 8192/sbin/newfs_hfs -s -v System -b 8192 -n a=8192,c=8192,e=8192 /dev/disk0s1 executing /sbin/newfs_hfsInitialized /dev/rdisk0s1 as a 750 MB HFS Plus volumeblock size for /dev/disk0s2s1: 8192/sbin/newfs_hfs -s -v Data -J -P -b 8192 -n a=8192,c=8192,e=8192 /dev/disk0s2s1 executing /sbin/newfs_hfsInitialized /dev/rdisk0s2s1 as a 14 GB HFS Plus volume with a 8192k journalentering restore_imagesexecuting /usr/sbin/asrASR STATUS: start223multicast-clientASR: Waiting for connection attempt from servervoid AppleUSBDeviceMux::handleConnectResult(BulkUSBMuxSession*, errno_t) new session to port 12345 failed: 61void AppleUSBDeviceMux::handleConnectResult(BulkUSBMuxSession*, errno_t) new session to port 12345 failed: 61ASR STATUS: setupASR: Validating target...ASR: doneASR STATUS: metadataASR: Validating source...AppleUSBDeviceMux::handleConnectResult new session 0x829b1180 established 12345<-lo0->49158 12345<-usb->15104ASR: Using Hardware AESASR: Using Hardware AESASR: Using Hardware AESASR: doneASR: Using Hardware AESASR: Warning: You may not be able to start up a computer with the target volume.ASR: Retrieving scan information...doneASR: Validating sizes...ASR: doneASR STATUS: restoreASR RESTORE PROGRESS: 2%ASR RESTORE PROGRESS: 4%ASR RESTORE PROGRESS: 6%ASR RESTORE PROGRESS: 8%ASR RESTORE PROGRESS: 10%ASR RESTORE PROGRESS: 12%ASR RESTORE PROGRESS: 14%ASR RESTORE PROGRESS: 16%ASR RESTORE PROGRESS: 18%ASR RESTORE PROGRESS: 20%ASR RESTORE PROGRESS: 22%AppleBCMWLAN::handleIOKitBusyWatchdogTimeout(): Error, no successful firmware download after 60000 ms!! Giving up...ASR RESTORE PROGRESS: 24%ASR RESTORE PROGRESS: 26%ASR RESTORE PROGRESS: 28%ASR RESTORE PROGRESS: 30%ASR RESTORE PROGRESS: 32%ASR RESTORE PROGRESS: 34%ASR RESTORE PROGRESS: 36%ASR RESTORE PROGRESS: 38%ASR RESTORE PROGRESS: 40%ASR RESTORE PROGRESS: 42%ASR RESTORE PROGRESS: 44%ASR RESTORE PROGRESS: 46%ASR RESTORE PROGRESS: 48%ASR RESTORE PROGRESS: 50%ASR RESTORE PROGRESS: 52%ASR RESTORE PROGRESS: 54%ASR RESTORE PROGRESS: 56%ASR RESTORE PROGRESS: 58%ASR RESTORE PROGRESS: 60%ASR RESTORE PROGRESS: 62%ASR RESTORE PROGRESS: 64%ASR RESTORE PROGRESS: 66%ASR RESTORE PROGRESS: 68%ASR RESTORE PROGRESS: 70%ASR RESTORE PROGRESS: 72%ASR RESTORE PROGRESS: 74%ASR RESTORE PROGRESS: 76%ASR RESTORE PROGRESS: 78%ASR RESTORE PROGRESS: 80%ASR RESTORE PROGRESS: 82%ASR RESTORE PROGRESS: 84%ASR RESTORE PROGRESS: 86%ASR RESTORE PROGRESS: 88%ASR RESTORE PROGRESS: 90%ASR RESTORE PROGRESS: 92%ASR RESTORE PROGRESS: 94%ASR RESTORE PROGRESS: 96%ASR RESTORE PROGRESS: 98%ASR RESTORE PROGRESS: 100%ASR: Copied 731038208 bytes in 79.31 seconds, 9001.96 KiB/sASR STATUS: verifyAppleUSBDeviceMux::sessionUpcall socket is closed, session 0x829b1180 (12345<-lo0->49158 12345<-usb->15104)ASR VERIFY PROGRESS: 2%ASR VERIFY PROGRESS: 4%ASR VERIFY PROGRESS: 6%ASR VERIFY PROGRESS: 8%ASR VERIFY PROGRESS: 10%ASR VERIFY PROGRESS: 12%ASR VERIFY PROGRESS: 14%ASR VERIFY PROGRESS: 16%ASR VERIFY PROGRESS: 18%ASR VERIFY PROGRESS: 20%ASR VERIFY PROGRESS: 22%ASR VERIFY PROGRESS: 24%ASR VERIFY PROGRESS: 26%ASR VERIFY PROGRESS: 28%ASR VERIFY PROGRESS: 30%ASR VERIFY PROGRESS: 32%ASR VERIFY PROGRESS: 34%ASR VERIFY PROGRESS: 36%ASR VERIFY PROGRESS: 38%ASR VERIFY PROGRESS: 40%ASR VERIFY PROGRESS: 42%ASR VERIFY PROGRESS: 44%ASR VERIFY PROGRESS: 46%ASR VERIFY PROGRESS: 48%ASR VERIFY PROGRESS: 50%ASR VERIFY PROGRESS: 52%ASR VERIFY PROGRESS: 54%ASR VERIFY PROGRESS: 56%ASR VERIFY PROGRESS: 58%ASR VERIFY PROGRESS: 60%ASR VERIFY PROGRESS: 62%ASR VERIFY PROGRESS: 64%ASR VERIFY PROGRESS: 66%ASR VERIFY PROGRESS: 68%ASR VERIFY PROGRESS: 70%ASR VERIFY PROGRESS: 72%ASR VERIFY PROGRESS: 74%ASR VERIFY PROGRESS: 76%ASR VERIFY PROGRESS: 78%ASR VERIFY PROGRESS: 80%ASR VERIFY PROGRESS: 82%ASR VERIFY PROGRESS: 84%ASR VERIFY PROGRESS: 86%ASR VERIFY PROGRESS: 88%ASR VERIFY PROGRESS: 90%ASR VERIFY PROGRESS: 92%ASR VERIFY PROGRESS: 94%ASR VERIFY PROGRESS: 96%ASR VERIFY PROGRESS: 98%ASR VERIFY PROGRESS: 100%ASR: Verified SHA-1 checksum 731038208 bytes in 23.53 seconds, 30344.18 KiB/sASR STATUS: finishentering mount_filesystemsexecuting /sbin/fsck_hfs/dev/rdisk0s1 Executing fsck_hfs (version diskdev_cmds-488.1.7~39).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 Apex8A400.N88OS appears to be OK.executing /sbin/mountexecuting /sbin/fsck_hfsdisk0s2s1: ioctl(_IOW,d,24,4) is unsupported./dev/rdisk0s2s1 Executing fsck_hfs (version diskdev_cmds-488.1.7~39).Checking 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 Data appears to be OK.executing /sbin/mountentering install_kernel_cachewriting kernelcache to /mnt1/System/Library/Caches/com.apple.kernelcaches/kernelcacheentering install_secure_vault_daemonentering get_hardware_platformplatform-name = s5l8920xlinking /mnt1/usr/sbin/securekeyvaultd to /mnt1/usr/sbin/securekeyvaultd.s5l8920xno securekeyvaultd for s5l8920xentering fixup_varremove_path /mnt1/private/varexecuting /bin/rmcreating directory (owner=0 mode=755) /mnt1/private/varentering modify_fstabentering clear_persistent_boot_argsexecuting /usr/sbin/nvramentering update_NORentering img3_update_NORimg3_flash_NOR_image: flashing LLB data (length = 0xf999)img3_flash_NOR_image: flashing NOR data (length = 0x29999)img3_flash_NOR_image: flashing NOR data (length = 0xbe59)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_bagattempting to create system key bag on /mnt2booted from secure root: give device keybag access to everyoneentering update_gas_gauge_softwareAppleKeyStore:cp_key_store_action(1)AppleKeyStore:cp_key_store_action(1)gasgauge_swupdate failed: -1attempting to dump restore logwriting log file: /mnt1/restore.log==== end of previous restore log ====2010-09-01 22:36:22.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 11 progress -12010-09-01 22:36:28.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 12 progress -12010-09-01 22:36:30.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 12 progress -12010-09-01 22:36:37.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 02010-09-01 22:36:47.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 12010-09-01 22:36:47.000 iTunes1936:1788f: ASR progress: Initialized communication with client2010-09-01 22:36:50.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 52010-09-01 22:36:50.000 iTunes1936:1788f: ASR progress: Starting to send payload2010-09-01 22:36:51.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 62010-09-01 22:36:51.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:36:52.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 72010-09-01 22:36:52.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:36:52.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 82010-09-01 22:36:52.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:36:53.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 92010-09-01 22:36:53.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:36:54.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 102010-09-01 22:36:54.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:36:55.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 112010-09-01 22:36:55.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:36:56.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 122010-09-01 22:36:56.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:36:56.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 132010-09-01 22:36:56.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:36:57.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 142010-09-01 22:36:58.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:36:59.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 152010-09-01 22:36:59.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:36:59.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 162010-09-01 22:36:59.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:00.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 172010-09-01 22:37:00.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:01.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 182010-09-01 22:37:01.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:01.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 192010-09-01 22:37:01.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:02.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 202010-09-01 22:37:02.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:03.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 212010-09-01 22:37:03.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:03.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 222010-09-01 22:37:03.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:04.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 232010-09-01 22:37:04.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:04.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 242010-09-01 22:37:04.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:05.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 252010-09-01 22:37:05.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:06.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 262010-09-01 22:37:06.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:07.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 272010-09-01 22:37:07.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:07.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 282010-09-01 22:37:07.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:08.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 292010-09-01 22:37:08.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:09.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 302010-09-01 22:37:09.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:10.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 312010-09-01 22:37:10.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:11.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 322010-09-01 22:37:11.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:11.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 332010-09-01 22:37:11.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:12.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 342010-09-01 22:37:12.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:13.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 352010-09-01 22:37:13.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:14.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 362010-09-01 22:37:14.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:16.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 372010-09-01 22:37:16.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:17.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 382010-09-01 22:37:17.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:18.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 392010-09-01 22:37:18.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:19.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 402010-09-01 22:37:19.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:19.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 412010-09-01 22:37:19.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:20.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 422010-09-01 22:37:20.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:21.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 432010-09-01 22:37:21.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:21.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 442010-09-01 22:37:21.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:22.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 452010-09-01 22:37:22.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:23.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 462010-09-01 22:37:23.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:23.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 472010-09-01 22:37:23.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:24.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 482010-09-01 22:37:24.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:25.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 492010-09-01 22:37:25.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:26.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 502010-09-01 22:37:26.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:27.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 512010-09-01 22:37:27.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:28.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 522010-09-01 22:37:28.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:28.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 532010-09-01 22:37:28.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:29.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 542010-09-01 22:37:29.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:30.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 552010-09-01 22:37:30.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:31.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 562010-09-01 22:37:31.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:32.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 572010-09-01 22:37:32.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:32.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 582010-09-01 22:37:32.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:33.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 592010-09-01 22:37:33.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:34.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 602010-09-01 22:37:34.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:35.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 612010-09-01 22:37:35.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:36.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 622010-09-01 22:37:36.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:37.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 632010-09-01 22:37:37.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:38.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 642010-09-01 22:37:38.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:39.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 652010-09-01 22:37:39.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:40.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 662010-09-01 22:37:40.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:41.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 672010-09-01 22:37:41.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:41.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 682010-09-01 22:37:41.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:42.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 692010-09-01 22:37:42.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:42.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 702010-09-01 22:37:42.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:43.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 712010-09-01 22:37:43.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:44.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 722010-09-01 22:37:44.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:45.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 732010-09-01 22:37:45.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:45.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 742010-09-01 22:37:45.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:46.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 752010-09-01 22:37:46.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:46.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 762010-09-01 22:37:46.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:47.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 772010-09-01 22:37:47.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:48.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 782010-09-01 22:37:48.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:49.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 792010-09-01 22:37:49.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:49.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 802010-09-01 22:37:49.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:50.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 812010-09-01 22:37:50.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:51.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 822010-09-01 22:37:51.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:51.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 832010-09-01 22:37:51.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:52.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 842010-09-01 22:37:52.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:53.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 852010-09-01 22:37:53.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:54.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 862010-09-01 22:37:54.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:55.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 872010-09-01 22:37:55.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:55.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 882010-09-01 22:37:55.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:56.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 892010-09-01 22:37:56.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:57.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 902010-09-01 22:37:57.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:58.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 912010-09-01 22:37:58.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:58.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 922010-09-01 22:37:58.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:37:59.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 932010-09-01 22:37:59.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:38:00.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 942010-09-01 22:38:00.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:38:01.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 952010-09-01 22:38:01.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:38:02.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 962010-09-01 22:38:02.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:38:03.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 972010-09-01 22:38:03.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:38:04.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 982010-09-01 22:38:04.000 iTunes1936:1788f: ASR progress: Sending payload2010-09-01 22:38:05.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 13 progress 1002010-09-01 22:38:05.000 iTunes1936:1788f: ASR progress: Finished2010-09-01 22:38:06.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 22010-09-01 22:38:06.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 42010-09-01 22:38:07.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 62010-09-01 22:38:07.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 82010-09-01 22:38:08.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 102010-09-01 22:38:08.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 122010-09-01 22:38:09.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 142010-09-01 22:38:09.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 162010-09-01 22:38:10.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 182010-09-01 22:38:10.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 202010-09-01 22:38:11.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 222010-09-01 22:38:11.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 242010-09-01 22:38:11.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 262010-09-01 22:38:12.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 282010-09-01 22:38:12.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 302010-09-01 22:38:13.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 322010-09-01 22:38:13.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 342010-09-01 22:38:14.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 362010-09-01 22:38:14.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 382010-09-01 22:38:15.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 402010-09-01 22:38:15.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 422010-09-01 22:38:16.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 442010-09-01 22:38:16.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 462010-09-01 22:38:17.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 482010-09-01 22:38:17.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 502010-09-01 22:38:18.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 522010-09-01 22:38:18.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 542010-09-01 22:38:19.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 562010-09-01 22:38:19.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 582010-09-01 22:38:19.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 602010-09-01 22:38:20.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 622010-09-01 22:38:20.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 642010-09-01 22:38:21.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 662010-09-01 22:38:21.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 682010-09-01 22:38:22.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 702010-09-01 22:38:22.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 722010-09-01 22:38:23.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 742010-09-01 22:38:23.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 762010-09-01 22:38:24.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 782010-09-01 22:38:24.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 802010-09-01 22:38:25.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 822010-09-01 22:38:25.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 842010-09-01 22:38:26.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 862010-09-01 22:38:26.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 882010-09-01 22:38:27.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 902010-09-01 22:38:27.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 922010-09-01 22:38:27.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 942010-09-01 22:38:28.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 962010-09-01 22:38:28.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 982010-09-01 22:38:29.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 14 progress 1002010-09-01 22:38:29.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 15 progress -12010-09-01 22:38:43.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 16 progress -12010-09-01 22:38:43.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 15 progress -12010-09-01 22:38:45.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 16 progress -12010-09-01 22:38:45.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 27 progress -12010-09-01 22:38:46.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 27 progress -12010-09-01 22:38:46.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 17 progress -12010-09-01 22:38:47.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 25 progress -12010-09-01 22:38:47.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 35 progress -12010-09-01 22:38:47.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 18 progress -12010-09-01 22:39:08.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 49 progress -12010-09-01 22:39:09.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: operation 46 progress -12010-09-01 22:39:33.000 iTunes1936:1788f: device returned AMR error 292010-09-01 22:39:33.000 iTunes1936:1788f: ==== device restore output ====sOTGDevice::start : start finishedAppleMultitouchN1SPI: detected HBPP. driver will be kept aliveAppleM2ScalerCSCDriver: Added framebuffer device: AppleM2TVOut id: 81b4f800IOSDIOController::enumerateSlot(): Searching for SDIO device in slot: 0IOSDIOController::enumerateSlot(): Found SDIO I/O device. Function count(1), memory(0)read new style signature 0x43313133 (line:405)FTL:MSG VSVFL Register OKFTL:MSG VFL Init OKIOSDIOIoCardDevice::parseFn0CIS(): Device manufacturer ID 0x2d0, Product ID 0x4325IOSDIOIoCardDevice::parseFn0CIS(): Manufacturer: IOSDIOIoCardDevice::parseFn0CIS(): Product: IOSDIOIoCardDevice::parseFn0CIS(): ProductInfo0: s=D1IOSDIOIoCardDevice::parseFn0CIS(): ProductInfo1: P=N88 m=3.2AppleBCMWLAN::init(): AppleBCMWLAN-42 Aug 4 2010 18:51:11AppleBCMWLAN::init(): Starting with debug level: 4, debug flags: 00000000AppleBCMWLAN::init(): AppleBCMWLAN-42 Aug 4 2010 18:51:11AppleBCMWLAN::init(): Starting with debug level: 4, debug flags: 00000000FTL:MSG VFL_Open OKFTL:MSG YAFTL Register OKfound suitable IOMobileFramebuffer: AppleM2CLCDdisplay-scale = 1display-rotation = 0found PTP interfaceFTL:MSG FTL_Open OKAppleSynopsysOTGDevice - Configuration: PTPAppleSynopsysOTGDevice Interface: PTPAppleSynopsysOTGDevice - Configuration: iPod USB InterfaceAppleSynopsysOTGDevice Interface: USBAudioControlAppleSynopsysOTGDevice Interface: USBAudioStreamingAppleSynopsysOTGDevice Interface: IapOverUsbHidAppleSynopsysOTGDevice - Configuration: PTP + Apple Mobile DeviceAppleSynopsysOTGDevice Interface: PTPAppleSynopsysOTGDevice Interface: AppleUSBMuxAppleSynopsysOTGDevice - Configuration: PTP + Apple Mobile Device + Apple USB EthernetAppleSynopsysOTGDevice Interface: PTPAppleSynopsysOTGDevice Interface: AppleUSBMuxAppleSynopsysOTGDevice Interface: AppleUSBEthernetAppleSynopsysOTGDevice::gated_registerFunction Register function USBAudioControlAppleSynopsysOTGDevice::gated_registerFunction Register function USBAudioStreamingIOAccessoryPortUSB::startAppleSynopsysOTGDevice::gated_registerFunction Register function IapOverUsbHidvirtual bool AppleUSBDeviceMux::start(IOService*) build: Aug 4 2010 18:51:30init_wasteAppleSynopsysOTGDevice::gated_registerFunction Register function AppleUSBMuxAppleSynopsysOTGDevice::gated_registerFunction Register function AppleUSBEthernetAppleUSBEthernetDevice::start: Device MAC address = 0a:0b:ad:0b:ab:e0AppleUSBEthernetDevice::start: Host MAC address = 00:26:b0:92:35:00close(caller = 0x5695): remote port = 49152close(caller = 0x5695): remote port = 49153client protocol version 12Restore options:SystemPartitionSize => <CFNumber 0xb095c0 0x1a9d5c>{value = +750, type = kCFNumberSInt64Type}entering partition_nand_devicedevice is not a boot-from-NAND deviceentering wait_for_storage_deviceentering format_effaceable_storageeffaceable storage is formatted, clearing iteffaceable storaged clearedentering check_for_restore_logexecuting /sbin/fsck_hfsAppleSynopsysOTGDevice::gated_registerFunction Register function PTPAppleSynopsysOTGDevice::gated_registerFunction all functions registered- we are ready to start usb stackAppleS5L8720XUSBPhy::powerUp : _powered: 0AppleEmbeddedUSBArbitrator::enableDeviceClock : enable: 1, index: 0virtual IOReturn AppleUSBDeviceMux::setProperties(OSObject*) setting debug level to 7AppleSynopsysOTGDevice::handleUSBResetAppleUSBDeviceMux::handleConnectResult new session 0x83440080 established 62078<-lo0->49152 62078<-usb->512void AppleUSBDeviceMux::handleMuxTCPInput(__mbuf*) received reset, closing 0x83440080AppleUSBDeviceMux::handleConnectResult new session 0x83479e80 established 62078<-lo0->49153 62078<-usb->768AppleUSBDeviceMux::sessionUpcall socket is closed, session 0x83479e80 (62078<-lo0->49153 62078<-usb->768)AppleUSBDeviceMux::handleConnectResult new session 0x83440200 established 62078<-lo0->49154 62078<-usb->1024/dev/rdisk0s1 Executing fsck_hfs (version diskdev_cmds-488.1.7~39).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 Apex8A400.N88OS appears to be OK.executing /sbin/mountfound restore log (size = 11803)entering create_filesystem_partitionsNAND format completecreating encrypted data partitionwipe entire partition: 1 (old = 0 new = 750)block size for /dev/disk0s1: 8192/sbin/newfs_hfs -s -v System -b 8192 -n a=8192,c=8192,e=8192 /dev/disk0s1 executing /sbin/newfs_hfsInitialized /dev/rdisk0s1 as a 750 MB HFS Plus volumeblock size for /dev/disk0s2s1: 8192/sbin/newfs_hfs -s -v Data -J -P -b 8192 -n a=8192,c=8192,e=8192 /dev/disk0s2s1 executing /sbin/newfs_hfsInitialized /dev/rdisk0s2s1 as a 14 GB HFS Plus volume with a 8192k journalentering restore_imagesexecuting /usr/sbin/asrASR STATUS: start223multicast-clientASR: Waiting for connection attempt from servervoid AppleUSBDeviceMux::handleConnectResult(BulkUSBMuxSession*, errno_t) new session to port 12345 failed: 61void AppleUSBDeviceMux::handleConnectResult(BulkUSBMuxSession*, errno_t) new session to port 12345 failed: 61ASR STATUS: setupASR: Validating target...ASR: doneASR STATUS: metadataASR: Validating source...AppleUSBDeviceMux::handleConnectResult new session 0x83440180 established 12345<-lo0->49157 12345<-usb->1792ASR: Using Hardware AESASR: Using Hardware AESASR: Using Hardware AESASR: doneASR: Using Hardware AESASR: Warning: You may not be able to start up a computer with the target volume.ASR: Retrieving scan information...doneASR: Validating sizes...ASR: doneASR STATUS: restoreASR RESTORE PROGRESS: 2%ASR RESTORE PROGRESS: 4%ASR RESTORE PROGRESS: 6%ASR RESTORE PROGRESS: 8%ASR RESTORE PROGRESS: 10%ASR RESTORE PROGRESS: 12%ASR RESTORE PROGRESS: 14%ASR RESTORE PROGRESS: 16%ASR RESTORE PROGRESS: 18%ASR RESTORE PROGRESS: 20%ASR RESTORE PROGRESS: 22%AppleBCMWLAN::handleIOKitBusyWatchdogTimeout(): Error, no successful firmware download after 60000 ms!! Giving up...ASR RESTORE PROGRESS: 24%ASR RESTORE PROGRESS: 26%ASR RESTORE PROGRESS: 28%ASR RESTORE PROGRESS: 30%ASR RESTORE PROGRESS: 32%ASR RESTORE PROGRESS: 34%ASR RESTORE PROGRESS: 36%ASR RESTORE PROGRESS: 38%ASR RESTORE PROGRESS: 40%ASR RESTORE PROGRESS: 42%ASR RESTORE PROGRESS: 44%ASR RESTORE PROGRESS: 46%ASR RESTORE PROGRESS: 48%ASR RESTORE PROGRESS: 50%ASR RESTORE PROGRESS: 52%ASR RESTORE PROGRESS: 54%ASR RESTORE PROGRESS: 56%ASR RESTORE PROGRESS: 58%ASR RESTORE PROGRESS: 60%ASR RESTORE PROGRESS: 62%ASR RESTORE PROGRESS: 64%ASR RESTORE PROGRESS: 66%ASR RESTORE PROGRESS: 68%ASR RESTORE PROGRESS: 70%ASR RESTORE PROGRESS: 72%ASR RESTORE PROGRESS: 74%ASR RESTORE PROGRESS: 76%ASR RESTORE PROGRESS: 78%ASR RESTORE PROGRESS: 80%ASR RESTORE PROGRESS: 82%ASR RESTORE PROGRESS: 84%ASR RESTORE PROGRESS: 86%ASR RESTORE PROGRESS: 88%ASR RESTORE PROGRESS: 90%ASR RESTORE PROGRESS: 92%ASR RESTORE PROGRESS: 94%ASR RESTORE PROGRESS: 96%ASR RESTORE PROGRESS: 98%AppleUSBDeviceMux::sessionUpcall socket is closed, session 0x83440180 (12345<-lo0->49157 12345<-usb->1792)ASR RESTORE PROGRESS: 100%ASR: Copied 731038208 bytes in 75.06 seconds, 9511.05 KiB/sASR STATUS: verifyASR VERIFY PROGRESS: 2%ASR VERIFY PROGRESS: 4%ASR VERIFY PROGRESS: 6%ASR VERIFY PROGRESS: 8%ASR VERIFY PROGRESS: 10%ASR VERIFY PROGRESS: 12%ASR VERIFY PROGRESS: 14%ASR VERIFY PROGRESS: 16%ASR VERIFY PROGRESS: 18%ASR VERIFY PROGRESS: 20%ASR VERIFY PROGRESS: 22%ASR VERIFY PROGRESS: 24%ASR VERIFY PROGRESS: 26%ASR VERIFY PROGRESS: 28%ASR VERIFY PROGRESS: 30%ASR VERIFY PROGRESS: 32%ASR VERIFY PROGRESS: 34%ASR VERIFY PROGRESS: 36%ASR VERIFY PROGRESS: 38%ASR VERIFY PROGRESS: 40%ASR VERIFY PROGRESS: 42%ASR VERIFY PROGRESS: 44%ASR VERIFY PROGRESS: 46%ASR VERIFY PROGRESS: 48%ASR VERIFY PROGRESS: 50%ASR VERIFY PROGRESS: 52%ASR VERIFY PROGRESS: 54%ASR VERIFY PROGRESS: 56%ASR VERIFY PROGRESS: 58%ASR VERIFY PROGRESS: 60%ASR VERIFY PROGRESS: 62%ASR VERIFY PROGRESS: 64%ASR VERIFY PROGRESS: 66%ASR VERIFY PROGRESS: 68%ASR VERIFY PROGRESS: 70%ASR VERIFY PROGRESS: 72%ASR VERIFY PROGRESS: 74%ASR VERIFY PROGRESS: 76%ASR VERIFY PROGRESS: 78%ASR VERIFY PROGRESS: 80%ASR VERIFY PROGRESS: 82%ASR VERIFY PROGRESS: 84%ASR VERIFY PROGRESS: 86%ASR VERIFY PROGRESS: 88%ASR VERIFY PROGRESS: 90%ASR VERIFY PROGRESS: 92%ASR VERIFY PROGRESS: 94%ASR VERIFY PROGRESS: 96%ASR VERIFY PROGRESS: 98%ASR VERIFY PROGRESS: 100%ASR: Verified SHA-1 checksum 731038208 bytes in 23.49 seconds, 30385.86 KiB/sASR STATUS: finishentering mount_filesystemsexecuting /sbin/fsck_hfs/dev/rdisk0s1 Executing fsck_hfs (version diskdev_cmds-488.1.7~39).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 Apex8A400.N88OS appears to be OK.executing /sbin/mountexecuting /sbin/fsck_hfsdisk0s2s1: ioctl(_IOW,d,24,4) is unsupported./dev/rdisk0s2s1 Executing fsck_hfs (version diskdev_cmds-488.1.7~39).Checking 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 Data appears to be OK.executing /sbin/mountentering install_kernel_cachewriting kernelcache to /mnt1/System/Library/Caches/com.apple.kernelcaches/kernelcacheentering install_secure_vault_daemonentering get_hardware_platformplatform-name = s5l8920xlinking /mnt1/usr/sbin/securekeyvaultd to /mnt1/usr/sbin/securekeyvaultd.s5l8920xno securekeyvaultd for s5l8920xentering fixup_varremove_path /mnt1/private/varexecuting /bin/rmcreating directory (owner=0 mode=755) /mnt1/private/varentering modify_fstabentering clear_persistent_boot_argsexecuting /usr/sbin/nvramentering update_NORentering img3_update_NORimg3_flash_NOR_image: flashing LLB data (length = 0xf999)img3_flash_NOR_image: flashing NOR data (length = 0x29999)img3_flash_NOR_image: flashing NOR data (length = 0xbe59)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_bagattempting to create system key bag on /mnt2booted from secure root: give device keybag access to everyoneAppleKeyStore:cp_key_store_action(1)entering update_gas_gauge_softwareAppleKeyStore:cp_key_store_action(1)gasgauge_swupdate failed: -1attempting to dump restore logwriting log file: /mnt1/restore.log==== end of device restore output ====2010-09-01 22:39:33.000 iTunes1936:1788f: AMRAuthInstallDeletePersonalizedBundle2010-09-01 22:39:33.000 iTunes1936:1788f: removed personalized bundle2010-09-01 22:39:33.000 iTunes1936:1788f: <Restore Device 0x1c0c5070>: Restore failed (result = 29)2010-09-01 22:39:33.000 iTunes1936:20b: iTunes: Restore error 292010-09-01 22:39:45.000 iTunes1936:20b: device connected (isDFU = 0)2010-09-01 22:39:45.000 iTunes1936:20b: iTunes: SCEP 3 3G (I Believe) iOS 4

Firmware 2.2.1 iPhone 3G Apple Support Poo

Hey this is my first Apple device. After upgrading to 2.2.1 my reception is 50% or less than with 2.2 firmware. I then ran the carrier upgrade, no change. I did a complete restore, no change. Had to google an iPhone hacker site to find out how to roll my iPhone back to 2.2 firmware, which I will try tonight. Why is this information not on the Apple support site? This might be common knowledge but the way apple supports the iPhone seems very heavy handed to me. Why does the signal strength meter lie? Also googled on a hacker site because of 2.2.1 I found 3001#12345# that lets you read the signal db in numbers. So -63 is 5 bars and -103 is 5 bars. Whats up with that? I thought apples marketing shtick for their products was suppose to free me from dorking with hardware and software and let me focus on my business. It seem more like apple will lock you out from the recovery of their mistakes.Lessons learned here are. One, never upgrade again, when everything is working. Two, keep eyes open for the next trade offer from an apple competitor. thinkpad Windows XP Pro

dialing phone numbers with extension x iPhone

Hi,I manage my contacts in Outlook and for telephone numbers with extensions I use the Outlook standard format +countrycode (areacode) phonenumber x exte.g. +49 (911) 12345 x 123By using the Outlook Check Phone number dialog this is the only allowed format. You get this dialog by pressing for instance the Business... button in the phone numbers section of a contact. So far so good - it even syncs perfectly with the iPhone.But if I want to dial that number it simply tells me the number is invalid (because the iPhone DOES NOT dial the extension!). Theoretically it should dial the number, pause at the x and then dial the extension.So I could of course save ALL my phone numbers without the extension (which would be an annoying job) but then I would loose the information about the extension and furthermore I could not use the standard dialog in Outlook. Even more worse: because I sync with the business directory in my company they would override my local settings. I simply cannot tell them to store the phone numbers without extensions company wide only because my iPhone...Blackberry and Windows Mobile systems dial those numbers without problems.Any hints?RegardsDirk Windows PC Windows Vista

Excellent Article Disconnect Between Bars Cell Signal By J. Cheng iPhone 3G

Count to fiveMore bars in more places, reads the latest slogan from one of the largest mobile carriers in the US. Its plastered everywhere, from print ads to billboards to TV commercials. At least here in the US, its pounded into our heads early on that bars = signal level = fewer problems overall. And its kind of true. Generally speaking, the number of bars being displayed on your cell phone give a general idea of whether you have a good chance of making a call.However, there are a number of variables that the phone takes into account when figuring out exactly how many bars to show you in the first place, and in fact, those variables can be (and often are) different among cell carriers, manufacturers, or even different devices from the same manufacturer. Put simply, the number of bars displayed on your phone does not necessarily equal signal level; rather, it would be more accurate to say that the bars are correlated with signal level.Under most normal circumstances, the fact that bars are somewhat disconnected from signal level doesnt really matter. Most average people tend to use the same handset for years, and as long as it works, theyre not paying attention to whether one particular phone on one particular carrier displays one more bar than another phone on the same or a different carrier. However, we geeks are not average people (usually). We pay attention to those tiny details, and we use that information to make judgments on how good or how crappy a phone or a carrier really is.The topic of bars and signal strength has recently come to a head with the introduction of the iPhone 3G. Some of you have written into us expressing dissatisfaction with your iPhone 3Gs number of bars when compared to other handsets you have used, only to discover how to put the phone into field test mode and see that its reading the same level of signal that youre used to. Others have complained about experiencing dropped calls while having a full set of bars. As a result, we took a close look at what makes up all the links in the chain that connect signal level with bars, and why bars are not as reliable an indicator as you might think. Heres what we found:Signal, cell towers, and youWireless engineers talk about signal strength in terms of power: dBm, or decibels to the milliwatt. At the very top of a cell tower, signal is transmitted at roughly +43dBm (20 watts) right at the antenna. However, that power diminishes significantly as you move further away, because the power density of a radio frequency (RF) signal in a vacuum follows the inverse square law in free space. Or, to put it in plain English, every time a signal doubles its distance away from the antenna, its power drops by a factor of four. However, cell towers dont really transmit signal in a vacuum. And, on top of that, its being transmitted from an average of 100 to 300 feet above the ground, or 200ft to 5,000ft away, as the crow flies to your phone. Therefore, the problem of dropped power is magnified significantly.By the time a signal transmitted from the tower hits your cell phone, it will be in the µW (microwatt) or nW (nanowatt) range. Since decibels are based on a logarithmic scale (they merely indicate a change between two numbers), the actual power change between 0dBm and 3dBm is a power of two—the same between 3dBm and 6dBm, and so on. A dBm of zero (which is next to impossible unless you suddenly find yourself climbing halfway up a tower) would be one milliwatt of power, and for every 3 dBm going down into the negatives, that power is being cut in half. So, for example, a dBm of -3 is about a half a milliwatt, -6 is a quarter, and so on. Once you get to -90dBm, youve reached the lower threshold of allowable signal level to connect to a tower.You can see the number of dBm youre getting by putting your phone into field test mode. The method for doing this varies by phone and manufacturer, but generally speaking, its not difficult to find with a little digging on the Internet. For the iPhone, for example, entering 3001#12345# will let you enter field test mode and see your numerical signal level.There are a couple of reasons why the user isnt shown these numbers outright, though. For one, this can fluctuate by seemingly huge amounts with relatively little physical movement, which would cause confusion among users. This is due, in part, to a phenomenon called multipath signal fading.A cell tower signal can be reflected by any sort of material that is partially reflective to electromagnetic radiation (i.e., inorganic material, like certain types of stone, metal, glass, or water.) Sometimes, a certain material can absorb a small part of a signal and reflect the rest of it off in another direction; this reflection means that all these signals are bouncing around and taking different physical paths to your cell phones antenna. Different signals taking different paths means that some take longer paths than others. Since they all are traveling at the speed of light, multiple signal paths mean that some signals will arrive at your cell phones antenna at different times. These signals interact with each other, canceling some parts of the signal out and amplifying others. The typical result is that the power density of signals in these multipath environments will fade in and out. In this respect, a typical urban environment plays **** with RF signals.But multipath signal fading isnt the only thing that affects your ability to make clear phone calls.Call qualityIn addition to signal, theres another variable that factors into your cell phones reception: signal-to-noise ratio (SNR). SNR is affected by the environmental interference factors that we just discussed, i.e., how much interference there is in your raw signal, regardless of the strength of the signal. If youre in the downtown area of a city, and signal is bouncing off buildings, or if youre near a large body of water that reflects signal back, this can affect your call quality significantly. These are situations when you might experience fading while making a phone call on what otherwise seems to be a good signal.This signal-to-noise value can be analyzed on the handset, and its used in conjunction with the phones reported signal level to formulate another scaled value—a call quality estimate—that determines the overall status of the phone and whether its okay to connect to a tower. If this number is low enough, the tower wont let you connect, and hopefully, your phone will attempt to find a better tower within range. If the phone cant find a closer tower, then youre completely out of luck, and no tower will let you connect. At this point, most phones display a message like No Signal or No Service, which isnt entirely accurate. Its more like No Usable Signal according to the thresholds specified by the carrier, but that doesnt fit quite as easily into a ten-pixel-wide area in the corner of your screen.This introduces a new conundrum for the cell carriers in charge of these towers. The carriers are able to set a floor for how low the call quality has to be before the tower wont let you connect. If they set the threshold too high, they run the risk of cutting off huge numbers of customers who may be just outside of the preferred range, and those customers will eventually complain about having no signal at their homes or workplaces. At the same time, however, setting the call quality threshold higher will also mean that there will be no dropped calls. The lower and lower this number is set, the more (and farther away) customers will be able to connect to towers to make calls. However, the level of signal and interference at that distance may cause them to have poorer call quality and more dropped calls.Where the bars come inThe five-point scale, known as bars, comes in when the cell phone itself looks at all these values being communicated from the tower and at the thresholds the tower would like the handset to obey. These values are ultimately what the phone and the tower use to determine whether the phone has a good enough chance of 1) connecting to the tower, and 2) maintaining a decent enough connection to conduct a phone call.Note: There are a number of other variables taken into account at this stage, too. For example, your cell phone may be able to hear the tower just fine, but the tower may still have trouble hearing you. Mobile handsets are limited by the FCC to a transmit power of one watt, so the level of signal transmitted back to the tower is minuscule, compared to the 20 watts coming at you (and being diminished greatly as it reaches you) from the tower. This mismatch in signal strength is mitigated slightly by expensive, extremely sensitive receiver antennas at the top of towers.Depending on the lower threshold of call quality on a particular tower, a phone will calculate a score on a scale of 1 to 5 to show the user how likely he or she is to be able to make a phone call. Lets say, for simplicitys sake, that the towers call quality variable is on a scale from 1 to 100, with 1 being the best and 100 being the worst. If the towers lower threshold is 80, and your phone is reading 65, your phone might display two bars, because its near the bottom but not quite there yet. However, if the carriers engineers set the threshold on the tower to a very low 100—that is, theyll allow cell phones with extremely poor signal quality to connect and make a call—a cell phone could still display two bars if its reading something like 90, because its still near the bottom, but not quite there yet.On the carriers side, you can just crank that number all over the place to make the bars go where you want, former RF engineer and current Ars code monkey Clint Ecker points out. This variable lets engineers make the tower more accurately display the quality of the signal, and its clearly in everyones best interest to make sure its as accurate as possible. After all, peoples jobs, raises, and bonuses are dependent upon being able to provide expected levels of service. Still, that variable is capable of being tweaked in ways that misrepresent reality as well.Manufacturers and standards (or the lack thereof)The fullness of your mobiles five-point bar scale is also dependent upon just how much money the devices manufacturer sank into its RF discriminator (the hardware that filters usable signal out of the noisy RF spectrum). Manufacturers who use a more sensitive (and expensive) RF discriminator will be able to use signals that other handsets could never identify. Some handsets are known for having higher-quality discriminators than others. For example, Nokia spends a bit more on the RF front-end to help phones sort out signal and noise, and so Nokia phones tend to have a reputation for high-quality receivers. Other phone makers may spend a little less on the discriminator hardware, and so may not perform as well.The bars scale is also dependent upon firmware from the manufacturer, OS vendor, and radio firmware provider. So the sensitivity of the bar scale, what will force it up or down, and what the baseline is of this variable on your phone is determined entirely by a string of programmers, none of which are following any specific standard for what qualifies as one bar versus two, three, or four.Why the disarray? It turns out that there is no mention of, or even an attempt to specify, anything about bars or how call quality should be displayed to the end user in the GSM specifications. While manufacturers tend to stay within the same general range for each bar of signal, like womens dress sizes, they dont often match up exactly. This means that the value can (and does) vary between manufacturers, phone models, and even different firmware versions on the same model.For example, Apples recently-released iPhone 2.1 software update offers improved accuracy of the 3G signal strength display. Notice that this doesnt claim to actually improve signal strength or your ability to make calls on the iPhone. Translated into laymans terms, it means we cranked up the bars for the same level of signal. And that (cranked up bars, anyway) is what users have been noticing, too.Its an artIf youve read to this point in the article, youre pretty well aware that the bar scale is a simplified meter for signal that is dependent upon many different factors, and those factors can vary by carrier, cell towers within each carrier, handset manufacturers, phone models, and software. This is why its next to futile to directly compare two phones by the number of bars being displayed, or to compare the same phone from two different carriers, or even the same phone from the same carrier with different versions of the firmware.But what you should take away from this isnt that bars are completely meaningless. They are, after all, there for a reason, which is to give you a good enough estimate of your ability to make a call. Just take the bars with a (very large) grain of salt when the service you get doesnt seem to match up with what the bars tell you, because the relationship between bars and call quality is much more of an art than a science.Doug Apple User for 30+ Years! Mac OS X (10.5.5) (Edited by Moderator) - Yup Thats One Of My Posts! :-)

stuck in signal strength testing mode-- this bad iPhone 3G

Hey, a couple of days ago I punched in the number for testing the signal strength (*3001#12345#*) and now I cant seem to get out of testing mode. That is, I always have the dB number in the upper LH corner rather than bars.Ive tried passing my finger down over the dB number, which used to get me back to bars but this is no longer working. The dB numbers abide when I power down or even do the full hold-down-power-and-home-buttons-until-the-apple-disappears trick.Im actually OK with this (bars seem to be pretty much meaningless anyway) unless its draining the battery or causing some other unanticipated consequence.So... is it OK to leave the phone in dB test mode? If not, how can one get out of test mode when the obvious ways dont work?

access dbm numbers iPhone 3G

how do you find the dbm numbers for your phone? where is it displayed? on someones blog i saw he put in *3001#12345#when i put those numbers i get message error performing request ~ dismiss. toshiba A105

iphone unlocking software . iphone unlock

{YouTube}dPchXuyaqxU{/YouTube}http://tinyurl.com/5g8qopTHIS IS THE LATEST, PROVEN FULL iPHONE SOFTWARE UNLOCK. Newly updated for iPhone firmware 1.1.1 & 1.1.2 & 1.1.3 & 1.1.4. This software will also fix any iPhones that were previously unlocked and bricked during the 1.1.1 , 1.1.2 , 1.1.3, and 1.1.4 upgrade. COMPATIBLE WITH ALL iPHONE (4GB or 8GB or 16GB) WITH FIRMWARE 1.0.0 TO 1.1.4 How To Check Firmware Version of Your iPhone: At the "Activate iPhone" screen, slide your finger where it says "slide for emergency". On the emergency keypad enter *3001#12345#* then press "Call" You are now in the Field Test program. Press "Versions". Look at the number for "Firmware Version". 03.12.06_G is firmware 1.0.0 03.14.08_G is firmware 1.0.1 and 1.0.2 04.01.13_G is firmware 1.1.1 04.02.04_G is firmware 1.1.1 04.02.13_G is firmware 1.1.2 04.03.13_G is firmware 1.1.3 04.04.05_G is firmware 1.1.4 ( LATEST FIRMWARE) INSTANT DIGITAL DELIVERY WILL DELIVER THIS PACKAGE YOU IN MATTER OF SECONDS UPON PAYMENTiphone software inlock.iphone software inlock.iphone software inlock.iphone software inlock.iphone software inlock.iphone software inlock.iphone software inlock.iphone software inlock.iphone software inlock.iphone software inlock.iphone software inlock.iphone software inlock.iphone software inlock.iphone software inlock.

built-in iPhone Field Test App 3G

{*3001#12345#*} and hit call. I had to put the {} here as it would not display correctly. Dont type those, just whats in between.It will launch the field test app.You have to be a nerd to understand any of it, but it might help some and just be of interest to others...While its running, look at the top-left of the screen too - it shows the signal strength in db.Scott  MBP  Mac Pro  Touch  3G iPhone  Mac OS X (10.5.4)  XSAN 

iPhone 3G speed test with following code

Folks,I dont know if that would works in the US but have been advised from the O2 network provider to type the following code and test ur 3G signal speed as some of them getting issues with 3G speed with full 5 bars and connection is not good or other many reason..well here is the instruction Switch off the the wifi connection make sure you 3G netowkr is on. go to the phone tab - then press keypad then type this 3001#12345# and press call iPhone will recognize this and switch to a screen with signal settings. then on the top left hand side where the singal strength is you will see something like -71 or what ever u getI am getting some time -70 with full 5 bars on my iphone 3G connection and its a fast and boy its fast .. like i am using wifiIf you are over -100 and 3g singal is showing with full 5 bars that mean something wrong with the network provider or check with your network provider.I believe there is nothing wrong with iPhone 3G chip as far as i done my text and i get 24/7 3g network conenction in my area and love it...I am so happy with my iPhone 3G its just getting better and better,Message was edited by: mc_monkiez MacBook Air Mac OS X (10.5.4) iPhone 3G 16 GB

iPhone 3G reception problems-used-dbm numbers in tests

I think that by now, most of us understand that the number of bars can be deceiving as an accurate reflection of the signal strength.Many iPhone 3G users around the world who are reporting the lack of usable 3G service have done side by side comparisons with other brands of 3G phones. While the number of bars is not an objective indicator of good service, many of these side by side test also involve usability reports that clearly reflect the iPhone 3G is sick.Has anyone (if not, will some of you - in various countries so we have different systems reporting) do a side by side test using the dbm numbers on the iPhone 3G and other brands of 3G phones? They are an objective measurement of performance, perhaps the only true objective test.I assume (hope) that the Field Test code works on all phones and networks?Field test procedure: Use the phone dial pad and enter * 3001#12345# * call. The dbm is displayed on the top left of the screen where the bars normally appear. If you want to exit the test mode, but retain the dbm display instead of bars, hold the home key about 3-5 seconds. You should then be able to toggle between bars and -dbm by tapping the bars or dbm numbers. Mac Book Mac OS X (10.5.3) POS PC w/Vista

Putting special characters into phone call strings iPhone 3G

Sorry if this has come up before. On iPhone (3G) is it possible to add special characters to cause pauses, for example 555-1212(pause 2 sec)12345#, ornnn-nnn-nnnn(pause 1sec)nnn-nnn-nnnn(pause 1 sec)nnnnnnnnnnnn(pause 2 sec)nnnnn#