EA6900 Firmware 1.1.42.155232 A FLOP!
Mr. Moderator, sent you the contact information in regards to my first post EA6900 Firmware 1.1.42.155232 "immediately" as you requested....still no reply from you to "help me" in 4 days. Seeing how technical support runs it's no surprise though.
Got RMA replacement router AE6900 two days ago. Please refer to original post EA6900 Firmware EA6900.
Setup again without a hitch with automatic firmware upgrade to version 1.1.42.155232. Less than 48 hours later the repeating sequence of pulsating, solid, blinking, then solid power light. After three hours with technical support most of time re-explaining the condition over and over again problem moved to engineering level support who will call me back in 24-48 hours. Based on last time to call me back by Senior level tech support in 5 minutes which was 1.5 hours at which point I called them back 24-48 hours could be next week or next month. For those of you reading this post, unless you want to become a Linksys/Belkin Beta tester for free like me, don't buy the EA6900 as technical support is aware of this problem and have no solution other than placing you on hold forever.
Linksys/Belkin Technical support: Just thought of a few solutions to the problem...buy ten of these routers, set them up and wait 2-4 days you should see the pulsing and blinking. You can find a solution on your time and not the customers. Which brings me to my second solution....test your equipment before releasing it!!!!!!
Linksys finally posted the release notes for the latest firmware. I've had my router for a week now and have not experienced any pulsating light. I'm going to assume it might have something to do with your setup. Just a thought.
Product: Linksys EA6900
Classification: Firmware Release Notes
IMPORTANT:
- DO NOT power cycle the Router during the firmware upgrade process.
===========================================================================
Firmware version: 1.1.42 (Build 155232)
Release date: October 1, 2013
- Fixed disconnect issue with some 5GHz clients.
- Fixed L2TP connection status as reported in the webUI.
- Fixed Internet Connection status reported in the webUI in bridge mode.
- Added support for Linksys Smart Wi-Fi on iOS 7 beta 2.
Firmware version: 1.1.42 (Build 154855)
Release date: September 16, 2013
- Initial release
Similar Messages
-
Sharing a nightmare... I received and setup my EA6900 last week. Setup was flawless. Noticed the router was cycling two minutes of pulsating front white (power) light then solid followed by blinking white light at a rate of one per second and 5-9 times, then solid again for a while. This sequence is continuously repeated. I did discover the automatic firmware update installed on the initial setup is 1.1.42.155.232 and the one online is 1.1.42.154855. Note: The pulsing and blinking does not interfere with normal router operation to my knowledge. After an hour with linksys technical support who had me manually install firmware version 1.1.42.154955 (this firmware is the initial firmware and only one posted on linksys online) followed by (Here is the Kicker) a hard reset on the router to factory default. At this point initial setup restarts and automatic firmware update places firmware 1.1.42.155232 Now back where I started and 15 minutes of time wasted. After several attempts trying to explain to the technician the sequence she had me perform set the router back to the initial firmware and then back up again with the automatic update...technician decides to RMA the Router and seemed not to comprehend the fact that resetting the router voided all previous procedures. Every time I tried to explain I got "I see," but I have RMA'ed it no need to worry."
Got RMA link emailed to me and after two hours on phone still have not gotten RMA to work because the serial number does not correspond to the case id number (also told this was a model ea6200 which makes me think last nights technician was completely oblivious)...currently awaiting supervisor to call me.
Setting Firmware back to 1.1.42.154955 and turning off automatic updates seems to fix the pulsing and blinking for the most part...have only seen one sequence of pulsing and blinking in the last two hours. Saw a post that the automatically updated firmware may be a beta version and this is why it is not posted online? Firmware version 1.1.42.155232 does not seem to be ready for primetime.It usually takes about a week after release for the firmware to show up on the support website for download.
Anytime you buy a wireless router shortly after it comes on the market, you have a much higher probability of having to deal with bugs. I never buy a wireless router until after it's been out for 6 months and have read multiple reviews and read feedback. -
My router got reset and im looking for the firmware 1.1.42.158863. Since to my knowlege is the only stable out of the firmwares that wont cause my wifi to randomly drop when it feels like. Unless they finaly fixed it with one of the latest ones.
What wireless modes are you using?
2.4Ghz and 5Ghz routers: Try single mode G or N or mixed G and N on 2.4Ghz and single mode N or Mixed on 5Ghz?
Channel Width set for Auto 20/40Mhz or try 20Mhz only.
Try setting a manual Channel to a open or unused channel. 1, 6 or 11. 11 for single mode N if the channel is clear. 13 for EU regions. Try channel 48 or 149 on 5Ghz. http://en.wikipedia.org/wiki/List_of_WLAN_channels
http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=f2625b15a5d7454b8e7fafbe65d5aa63_4009.xml&pid=80&r...
What security mode are you using? Preferred security is WPA-Personal. WPA2 Only. http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=8ce9e83bd3784001aee72da7f1ef48e8_Changing_the_basi...
http://kb.linksys.com/Linksys/ukp.aspx?pid=80&vw=1&articleid=19073
What wireless devices do you have connected?
Ensure any devices with WiFi adapter drivers are updated.
Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by?
Any other WiFi routers in the area? Link> Use http://www.metageek.net/support/metageek-software-archives/ to find out. Use v3. How many?
WMM Support must be enabled for single wireless N mode to function.
http://kb.linksys.com/Linksys/ukp.aspx?vw=1&articleid=5471
Router Placement
Forum User - "Well I feel really dumb. After moving the router away from other electronic devices my speeds are back to normal. Just a heads up for anyone experiencing slow speeds, you might want to move it away from other electronics and see if that helps."
3-6' feet minimum safe distance between devices.
Placement on main level floor and central in the building and WELL ventilated is preferred. Not in basements or closets as building materials, or near by electronics devices could interfere or hinder good signal propagation. -
I have downloaded the firmware 4 times over the past 4 or 5 months and every time I try to open the image file I get an invalid error. Has anyone else had this issue? Can anyone tell me where else I can download the firmware from? I will appreciate any advice or suggestions
you dont need to open it just put it on a wired. pc where you can find it then do the update. shouldn't have to touch the file at all. factory reset, flash the file, factory reset then config from scratch should give you the best results. hope this helps
-
EA6900 Wireless Auto Channel Issue
EA6900 Firmware: 1.1.42.156465
Wireless auto channel doesn't properly analyze network for channel selection and spacing.
It's best with this device to use a third party software like free "Wifi Analyzer" for mobile devices to find out which channels are not use in at the location and manually set the EA6900 wireless channels.
Please remember to Kudo those that help you.
Linksys
Communities Technical SupportHave you experienced this to your other wireless devices? If so, relocate the device at least a few feet away from the router, not too close nor too far. Make sure to use different name for both 2.4 GHz and 5 GHz wireless settings. You may also change the wireless channel on your router to avoid interference. Preferred channels to use are 1, 6, 9 and 11 since they're considered as non-overlapping channels. If this doesn't help, you may reflash the router's firmware then reset the router for 30 seconds and reconfigure it.
-
EA6900
Firmware: 1.1.42.158863
Media and FTP Servers disabled
Please remember to Kudo those that help you.
Linksys
Communities Technical SupportThis is nice. Thanks for sharing. Would like to try this real soon.
-
EA6900 drops 2.4 GHz wifi every other day
Hey,
my EA6900 (firmware version 1.1.42.158863) drops the 2.4 GHz network every other day or so. At that point, all connected devices lose the network connection and cannot connect again until I manually reset the router. This is a big pain in the **bleep**.
Here is what this looks like on a Linux client:
May 4 07:50:06 habanero dhclient: DHCPREQUEST of 192.168.1.104 on wlan0 to 255.255.255.255 port 67 (xid=0x553aef8)
May 4 07:50:35 dhclient: last message repeated 2 times
May 4 07:50:39 habanero dhclient: DHCPREQUEST of 192.168.1.104 on wlan0 to 255.255.255.255 port 67 (xid=0x553aef8)
May 4 07:50:57 habanero dhclient: DHCPREQUEST of 192.168.1.104 on wlan0 to 255.255.255.255 port 67 (xid=0x553aef8)
May 4 07:51:13 habanero avahi-daemon[1696]: Withdrawing address record for 2605:6000:100e:c073:21e:68ff:fed6:7636 on eth0.
May 4 07:51:13 habanero avahi-daemon[1696]: Registering new address record for 2605:6000:100e:c073:21e:68ff:fed6:7636 on eth0.*.
May 4 07:51:13 habanero avahi-daemon[1696]: Registering new address record for fe80::21e:68ff:fed6:7636 on eth0.*.
May 4 07:51:13 habanero avahi-daemon[1696]: Withdrawing address record for 2605:6000:100e:c073:a18e:f467:24c3:f7bb on wlan0.
May 4 07:51:13 habanero avahi-daemon[1696]: Registering new address record for 2605:6000:100e:c073:a18e:f467:24c3:f7bb on wlan0.*.
May 4 07:51:13 habanero avahi-daemon[1696]: Registering new address record for fe80::216:eaff:febc:cc0e on wlan0.*.
May 4 07:51:15 habanero kernel: [425404.872139] cfg80211: Calling CRDA to update world regulatory domain
May 4 07:51:15 habanero wpa_supplicant[1981]: wlan0: CTRL-EVENT-DISCONNECTED bssid=48:f8:b3:9d:ae:5b reason=4
May 4 07:51:15 habanero NetworkManager[1772]: <info> (wlan0): supplicant interface state: completed -> disconnected
May 4 07:51:15 habanero NetworkManager[1772]: <info> (wlan0): supplicant interface state: disconnected -> scanning
May 4 07:51:15 habanero kernel: [425405.033185] cfg80211: World regulatory domain updated:
May 4 07:51:15 habanero kernel: [425405.033189] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
May 4 07:51:15 habanero kernel: [425405.033192] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 4 07:51:15 habanero kernel: [425405.033194] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 4 07:51:15 habanero kernel: [425405.033196] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
May 4 07:51:15 habanero kernel: [425405.033198] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 4 07:51:15 habanero kernel: [425405.033200] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 4 07:51:17 habanero avahi-daemon[1696]: Withdrawing address record for 2605:6000:100e:c073:3d66:cec1:f213:3d26 on eth0.
May 4 07:51:17 habanero avahi-daemon[1696]: Leaving mDNS multicast group on interface eth0.IPv6 with address 2605:6000:100e:c073:3d66:cec1:f213:3d26.
May 4 07:51:17 habanero avahi-daemon[1696]: Joining mDNS multicast group on interface eth0.IPv6 with address 2605:6000:100e:c073:21e:68ff:fed6:7636.
May 4 07:51:17 habanero dhclient: DHCPREQUEST of 192.168.1.104 on wlan0 to 255.255.255.255 port 67 (xid=0x553aef8)
May 4 07:51:21 habanero NetworkManager[1772]: <info> (eth0): carrier now OFF (device state 100, deferring action for 4 seconds)
May 4 07:51:21 habanero kernel: [425411.065496] r8169 0000:03:00.0 eth0: link down
May 4 07:51:23 habanero NetworkManager[1772]: <info> (eth0): carrier now ON (device state 100)
May 4 07:51:23 habanero kernel: [425412.693894] r8169 0000:03:00.0 eth0: link up
May 4 07:51:30 habanero NetworkManager[1772]: <warn> (wlan0): link timed out.
May 4 07:51:30 habanero NetworkManager[1772]: <info> (wlan0): device state change: activated -> failed (reason 'SSID not found') [100 120 53]
May 4 07:51:30 habanero NetworkManager[1772]: <warn> Activation (wlan0) failed for connection 'olalmaro5'
May 4 07:51:30 habanero dbus[1572]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
May 4 07:51:30 habanero NetworkManager[1772]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
May 4 07:51:30 habanero NetworkManager[1772]: <info> (wlan0): deactivating device (reason 'none') [0]
May 4 07:51:30 habanero NetworkManager[1772]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 19785
May 4 07:51:30 habanero avahi-daemon[1696]: Withdrawing address record for 2605:6000:100e:c073:a18e:f467:24c3:f7bb on wlan0.
May 4 07:51:30 habanero avahi-daemon[1696]: Withdrawing address record for 2605:6000:100e:c073:216:eaff:febc:cc0e on wlan0.
May 4 07:51:30 habanero avahi-daemon[1696]: Leaving mDNS multicast group on interface wlan0.IPv6 with address 2605:6000:100e:c073:216:eaff:febc:cc0e.
May 4 07:51:30 habanero avahi-daemon[1696]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::216:eaff:febc:cc0e.
May 4 07:51:30 habanero avahi-daemon[1696]: Withdrawing address record for fe80::216:eaff:febc:cc0e on wlan0.
May 4 07:51:30 habanero avahi-daemon[1696]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::216:eaff:febc:cc0e.
May 4 07:51:30 habanero avahi-daemon[1696]: Interface wlan0.IPv6 no longer relevant for mDNS.
How do I fix this?
I've enabled automatic router firmware updates, but this has not helped over the last weeks.
Thanks in advance,
RobertThere is a bunch of people with this router ( me included) that are having issues with the wireless dropping out. Some more than others as far as the frequency of it. I have a ticket open with them and have been talking to them every few days about it. One thing I discovered the other day that has stopped it from dropping connections on the 2.4 is to set the mode to G only. I have given this info to linksys and they are supposed to get back to me by tomorrow with some more info. I am assuming it is the same problem as yours: everything is working fine then all of a sudden devices start to disconnect randomly. An my laptops it shows as the SSID is available but it wont connect to it. Only way to get back on is to reboot the router. As suggested by linksys the security is set to WPA2 Personal and the bandwidth is set to 20 mHz instead of auto. There was a big thread about this starting to happen when the last update came out that went from 1.1.42.156465 to 1.1.42.158863. If the Auto update was checked it got the update and started to disconnect wireless stuff. Might want to see what hardware version your is, the 1.0 came with the 1.1.42.156465 so if yours has updated to the newer one you could roll back and see if it gets better. there is a go back to last version button on the UI. but if you have the hw ver 1.1 it came with the updated version and we have been told not to go back as it may brick the router. here is the thread: http://community.linksys.com/t5/Wireless-Routers/EA6900-New-Firmware-1-1-42-158863/td-p/770985
-
Ap-manager ip address is not reachable
Hi,
we have Cisco 4402 Wireless LAN standalone controller, we recently upgraded the firmware from 4.0.155.0 to 4.0.179.11.
with new image we are unable to ping manager ip address but unable to ping ap-manager ip address. however both manager an d ap-manager interfaces are in same subnet.
Please help me any one face this type of problem.
Thanking you,
Regards,
Ranga Kishore
9959344436That is normal behavior.
-
Lags about every ten minutes when gaming
HI all,
last six months i cant game as i have terrible lag spikes that last 10 seconds or so every ten minutes.
I've setup pingplotter on another computer to monitor it and i get 100% packet loss on the first hop from the router.
its getting really anoying now , any ideas
done the usual updating of drivers virus scans etc, resetting router but nothing seems to help
regards
KeysMicrosoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Pete>C:\>TRACECERT 11.1.0.1
'C:\' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Pete>tracert bt,co,uk
Unable to resolve target system name bt,co,uk.
C:\Users\Pete>tracert www.bt.co.uk
Tracing route to www.bt.com [193.113.9.162]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms BThomehub.home [192.168.1.254]
2 7 ms 6 ms 6 ms 213.120.155.232
3 5 ms 5 ms 8 ms 213.120.155.190
4 6 ms 5 ms 6 ms 217.41.222.10
5 5 ms 5 ms 6 ms 31.55.164.195
6 6 ms 6 ms 6 ms 31.55.164.109
7 6 ms 6 ms 5 ms acc2-10GigE-0-5-0-5.bm.21cn-ipp.bt.net [109.159.
248.226]
8 17 ms 15 ms 16 ms core2-te-0-15-0-0.ilford.ukcore.bt.net [109.159.
248.14]
9 17 ms 17 ms 17 ms core2-pos1-1.birmingham.ukcore.bt.net [62.172.10
3.93]
10 15 ms 16 ms 14 ms iar1-gig5-5.birmingham.ukcore.bt.net [62.6.196.9
8]
11 16 ms 15 ms 16 ms 62.172.57.218
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out. -
EA6900 Update and Two Suggestions for Future Firmware "Nice to Haves"
Hey, first off, I've been a user of Linksys Routers for many years now, so I am familiar with the different settings and other selections that you generally see on the firmware pages. As to the EA6900, I am very, very PLEASED with how this router initially set up, along with the different pages in it's firmware. With the one exception noted below, the pages and the various settings "flow" very well. This baby is up and kickin and the house is literally dripping in both 2.4 and 5 GHz RF. The DHCP Reservation and MAC Wireless Filtering Tables worked without a hitch. The setup for FTP and NAS was simple! BTW, the setup for FTP shares is far easier than what we had to do using the EA3000 firmware. Kudos there! I am using the router associated with a server that is hosting about 25 different wired devices throughout the house, with a Cisco SG-200-08 Smart Switch behind the router for the LAN, which is load balancing on a Teamed (2 NIC'S) 2GB Adapter . The router grabbed Comcast's Native IPv6 and set that up flawlessly. Here is the information on how all that went (read from the bottom up): http://www.dslreports.com/forum/r28693387-IPv6-Dumb-Questions-About-My-IPv6-Goat-Roped-Hookup Information on how the netwrk worked in Teaming and LAG mode is here: https://supportforums.cisco.com/message/4071888#4071888
OK:, So, Mr. Linksys Firmware Developer, whoever and wherever you are, I have two suggestions on the user GUI that would make everyone's life a little easier next time the firmware is updated:
1. Please make it so numbers, particularly MAC and IPv6 numbers, can be copied and then pasted to another place in the firmware. For example, in the Information tab of the Device Settings section, I should be able to copy MAC and IP numbers and then be able to paste them, say, in the DHCP Reservation Table. Other Linksys device firmware allowed for this.
2. For goodness sakes, PLEASE don't nest the Diagnostics tab under the Troubleshooting group. It drives me nuts to think that getting the router's status, to ping or traceroute, or to do a firmware backup would be found in "Troubleshooting". Suggest that all y'all just remove the Diagnostics tab to the far left side of the application and have that item as its own stand-alone group!
Then I will be most happy. As if it really matters, BUT I wanted to give all y'all my perspective from a user way down in the day-to-day weeds. A most happy Boy otherwise.
Crazy Jumpin jack
Marietta, GA
Crazy Jumpin Jack (Gregory)Hi Crazy Jack,
We'll get the Team into your suggestions and commendations. Appreciate the feedback. We hope to see you help out in the Community as well.
Regards,
24JUAN80
Linksys Support Community Moderator
The Search Function is your friend.... and Google too.
How to Secure your Network
How to Upgrade Routers Firmware
Setting-Up a Router with DSL Internet Service
Setting-Up a Router with Cable Internet Service
How to Hard Reset or 30/30/30 your Router -
EA6900 - Upgraded to latest firmware now can't login to router
Upgraded EA6900 to latest firmware (11629 I believe). Now unable to login to router using either mylocal.router or linksyssmartwifi.com. Continues to pop up message that setup not complete. I repeat the steps to reset the router to factory settings and end up in same spot. I've tried the procedure connected wired to the router and wirelss to the router. I can login to router using smartwifi app on iPad however. Wireless connection still works as devices can connect. I'm stumbed.
Try clearing you browser's history and temporary files. Also restart the computer just in case.
Please remember to Kudo those that help you.
Linksys
Communities Technical Support -
IPhone 3G 8GB / iTunes just stuck at "restoring iPhone firmware"
Hi, so i have big problem. when i try to restore my iPhone 3G, everything is fine until itunes don't reach "Restoring iPhone firmware..." and then it just hangs there. And I don't know what to do... because it doesn't show any error, and iphone don't shut down. it just stays here. i tried to kick it out of recovery but it doesn't work.
can anybody help? or should i just use that iphone for parts...
picture here:
http://sphotos.ak.fbcdn.net/hphotos-ak-snc4/hs912.snc4/72516170352079641850_100000011775082_591342_2257315n.jpgHere is log from itunes. CAN HELP ME ANYBODY???
{quote:title=LordMMX wrote:}2010-10-29 18:31:10.872 [4792:494]: restore library built Aug 6 2010 at 11:14:46
2010-10-29 18:31:10.872 [4792:494]: iTunes: iTunes 10.0.1.22
2010-10-29 18:31:10.872 [4792:494]: iTunes: Software payload version: 8C5115c (option key)
2010-10-29 18:31:17.569 [4792:72c]: iTunes: Specifying UOI boot image
2010-10-29 18:31:17.572 [4792:72c]: requested restore behavior: Erase
2010-10-29 18:31:17.578 [4792:72c]: amai: AMAuthInstallPlatformCreateDataFromFileURL: can't resolve file
2010-10-29 18:31:17.580 [4792:72c]: amai: AMAuthInstallDebugWriteObject: debug object written: C:\Users\PETERP~1\AppData\Local\Temp\Per45D.tmp\amai\debug\tss-request.plist
2010-10-29 18:31:22.491 [4792:72c]: amai: AMAuthInstallRequestSendSync: received tss response (server version: 0.6.30-b2)
2010-10-29 18:31:22.492 [4792:72c]: amai: AMAuthInstallDebugWriteObject: debug object written: C:\Users\PETERP~1\AppData\Local\Temp\Per45D.tmp\amai\debug\tss-response.plist
2010-10-29 18:31:23.024 [4792:1cc]: <DFU Device 080882C0>: production fused device
2010-10-29 18:31:23.024 [4792:1cc]: unable to open device_map.txt: No such file or directory
2010-10-29 18:31:23.025 [4792:1cc]: WinDFU::OpenDFUDevice: path: \\?\USB#VID05AC&PID1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#cd098742
2010-10-29 18:31:23.025 [4792:1cc]: WinDFU::OpenDeviceByPath: \\?\USB#VID05AC&PID1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#cd098742
2010-10-29 18:31:23.073 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 1
2010-10-29 18:31:23.078 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 3
2010-10-29 18:31:23.085 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 5
2010-10-29 18:31:23.089 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 7
2010-10-29 18:31:23.094 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 9
2010-10-29 18:31:23.100 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 11
2010-10-29 18:31:23.104 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 13
2010-10-29 18:31:23.108 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 15
2010-10-29 18:31:23.112 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 17
2010-10-29 18:31:23.116 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 19
2010-10-29 18:31:23.121 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 21
2010-10-29 18:31:23.125 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 23
2010-10-29 18:31:23.130 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 25
2010-10-29 18:31:23.135 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 27
2010-10-29 18:31:23.139 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 29
2010-10-29 18:31:23.145 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 31
2010-10-29 18:31:23.149 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 33
2010-10-29 18:31:23.153 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 35
2010-10-29 18:31:23.157 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 37
2010-10-29 18:31:23.161 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 39
2010-10-29 18:31:23.165 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 41
2010-10-29 18:31:23.169 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 43
2010-10-29 18:31:23.173 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 44
2010-10-29 18:31:23.177 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 46
2010-10-29 18:31:23.181 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 48
2010-10-29 18:31:23.185 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 50
2010-10-29 18:31:23.189 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 52
2010-10-29 18:31:23.193 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 54
2010-10-29 18:31:23.197 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 56
2010-10-29 18:31:23.201 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 58
2010-10-29 18:31:23.205 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 60
2010-10-29 18:31:23.209 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 62
2010-10-29 18:31:23.213 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 64
2010-10-29 18:31:23.217 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 66
2010-10-29 18:31:23.221 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 68
2010-10-29 18:31:23.225 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 70
2010-10-29 18:31:23.229 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 72
2010-10-29 18:31:23.233 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 74
2010-10-29 18:31:23.237 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 76
2010-10-29 18:31:23.241 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 78
2010-10-29 18:31:23.245 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 80
2010-10-29 18:31:23.249 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 82
2010-10-29 18:31:23.253 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 84
2010-10-29 18:31:23.257 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 86
2010-10-29 18:31:23.261 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 87
2010-10-29 18:31:23.265 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 89
2010-10-29 18:31:23.269 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 91
2010-10-29 18:31:23.273 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 93
2010-10-29 18:31:23.277 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 95
2010-10-29 18:31:23.281 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 97
2010-10-29 18:31:23.285 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 99
2010-10-29 18:31:23.285 [4792:1cc]: WinDFU::UploadData: EOF, cbRead: 296
2010-10-29 18:31:23.287 [4792:1cc]: <DFU Device 080882C0>: operation 0 progress 100
2010-10-29 18:31:23.287 [4792:1cc]: WinDFU::UploadData: ZLP
2010-10-29 18:31:23.288 [4792:1cc]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
2010-10-29 18:31:23.288 [4792:1cc]: WinDFU::ProcessUpdateState: status.bState == DFUSTATE_MANIFESTSYNC
2010-10-29 18:31:23.288 [4792:1cc]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
2010-10-29 18:31:23.288 [4792:1cc]: WinDFU::ProcessUpdateState: status.bState == DFUSTATEMANIFEST, PollTimeout: 3000
2010-10-29 18:31:26.288 [4792:1cc]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
2010-10-29 18:31:26.288 [4792:1cc]: WinDFU::ProcessUpdateState: status.bState == DFUSTATE_MANIFEST_WAITRESET
2010-10-29 18:31:26.288 [4792:1cc]: WinDFU::ResetDevice: resetting...
2010-10-29 18:31:26.354 [4792:1cc]: WinDFU::FinalizeDfuUpdate: success
2010-10-29 18:31:26.354 [4792:1cc]: <DFU Device 080882C0>: DFU succeeded
2010-10-29 18:31:26.381 [4792:1710]: WinAMRestore::OnInterfaceRemoval: \\?\USB#VID05AC&PID1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#cd098742
2010-10-29 18:31:26.383 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7ea30, notify: 2, connected: 0
2010-10-29 18:31:26.384 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7e850, notify: 2, connected: 1
2010-10-29 18:31:26.384 [4792:1710]: AppleDevice::NotifyDisconnect: DFU \\?\USB#VID05AC&PID1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#cd098742, inst: 0x7c7e850
2010-10-29 18:31:26.384 [4792:1710]: _AMDFUModeDeviceFinalize: 080882C0
2010-10-29 18:31:31.285 [4792:1710]: WinAMRestore::OnInterfaceArrival: \\?\USB#VID05AC&PID1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#e95afe21
2010-10-29 18:31:31.285 [4792:1710]: WinAMRestore::AddAppleDeviceToDeviceList: \\?\USB#VID05AC&PID1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#e95afe21
2010-10-29 18:31:31.311 [4792:1710]: AppleDevice::EnumerateHubPorts: DoesDriverNameMatchDeviceID failed
2010-10-29 18:31:31.324 [4792:1710]: AppleDevice::EnumerateHubPorts: DoesDriverNameMatchDeviceID failed
2010-10-29 18:31:31.329 [4792:1710]: AppleDevice::SetNotification: CONNECT, interface type: 1, id: \\?\USB#VID05AC&PID1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#e95afe21, inst: 0x7c7ed00
2010-10-29 18:31:31.329 [4792:1710]: WinAMRestore::AddAppleDeviceToDeviceList, new device
2010-10-29 18:31:31.329 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7ea30, notify: 2, connected: 0
2010-10-29 18:31:31.329 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7e850, notify: 0, connected: 0
2010-10-29 18:31:31.329 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7ed00, notify: 1, connected: 0
2010-10-29 18:31:31.329 [4792:1710]: AppleDevice::NotifyConnect: Device type: 2, Interfaces total: 2, arrived: 1
2010-10-29 18:31:31.329 [4792:1710]: AppleDevice::NotifyConnect: Interfaces total != arrived, no notification
2010-10-29 18:31:31.331 [4792:1710]: WinAMRestore::OnInterfaceArrival: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#e95afe21
2010-10-29 18:31:31.331 [4792:1710]: WinAMRestore::AddAppleDeviceToDeviceList: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#e95afe21
2010-10-29 18:31:31.344 [4792:1710]: AppleDevice::EnumerateHubPorts: DoesDriverNameMatchDeviceID failed
2010-10-29 18:31:31.357 [4792:1710]: AppleDevice::EnumerateHubPorts: DoesDriverNameMatchDeviceID failed
2010-10-29 18:31:31.362 [4792:1710]: WinAMRestore::AddAppleDeviceToDeviceList, device already connected, new interface
2010-10-29 18:31:31.362 [4792:1710]: AppleDevice::SetDeviceID: AMDINTERFACEDFU \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#e95afe21, inst: 0x7c7ed00
2010-10-29 18:31:31.362 [4792:1710]: AppleDevice::SetNotification: CONNECT, interface type: 1, id: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#e95afe21, inst: 0x7c7ed00
2010-10-29 18:31:31.362 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7ea30, notify: 2, connected: 0
2010-10-29 18:31:31.362 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7e850, notify: 0, connected: 0
2010-10-29 18:31:31.362 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7ed00, notify: 1, connected: 1
2010-10-29 18:31:31.362 [4792:1710]: AppleDevice::NotifyConnect: Device type: 2, Interfaces total: 2, arrived: 2
2010-10-29 18:31:31.362 [4792:1710]: AppleDevice::NotifyConnect: IBOOT, IBOOT \\?\USB#VID05AC&PID1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#e95afe21, inst: 0x7c7ed00
2010-10-29 18:31:31.362 [4792:1710]: IBOOT, DFU \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#e95afe21, inst: 0x7c7ed00
2010-10-29 18:31:31.362 [4792:494]: iTunes: SCEP 5
2010-10-29 18:31:31.485 [4792:14a8]: iBoot build-version = iBoot-931.71.13
2010-10-29 18:31:31.486 [4792:14a8]: iBoot build-style = RELEASE
2010-10-29 18:31:31.486 [4792:14a8]: AMDeviceIoControl: GetOverlappedResult failed
2010-10-29 18:31:31.486 [4792:14a8]: AMDeviceIoControl: pipe stall
2010-10-29 18:31:31.486 [4792:14a8]: USBControlTransfer: error 31, usbd status c0000004
2010-10-29 18:31:31.487 [4792:14a8]: command device request for 'getenv radio-error' failed: 2008
2010-10-29 18:31:31.487 [4792:14a8]: radio-error not set
2010-10-29 18:31:31.487 [4792:14a8]: <Recovery Mode Device 07E212F8>: operation 44 progress -1
2010-10-29 18:31:31.487 [4792:14a8]: requested restore behavior: Erase
2010-10-29 18:31:31.492 [4792:14a8]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
2010-10-29 18:31:31.494 [4792:14a8]: unable to open device_map.txt: No such file or directory
2010-10-29 18:31:31.495 [4792:14a8]: <Recovery Mode Device 07E212F8>: production fused device
2010-10-29 18:31:31.496 [4792:14a8]: interface has 1 endpoints, file pipe = 1
2010-10-29 18:31:31.496 [4792:14a8]: <Recovery Mode Device 07E212F8>: operation 4 progress -1
2010-10-29 18:31:31.704 [4792:14a8]: <Recovery Mode Device 07E212F8>: operation 42 progress -1
2010-10-29 18:31:32.755 [4792:14a8]: <Recovery Mode Device 07E212F8>: operation 5 progress -1
2010-10-29 18:31:33.217 [4792:14a8]: AMDeviceIoControl: GetOverlappedResult failed
2010-10-29 18:31:33.217 [4792:14a8]: AMDeviceIoControl: pipe stall
2010-10-29 18:31:33.217 [4792:14a8]: USBControlTransfer: error 31, usbd status c0000004
2010-10-29 18:31:33.217 [4792:14a8]: command device request for 'getenv ramdisk-delay' failed: 2008
2010-10-29 18:31:35.622 [4792:14a8]: <Recovery Mode Device 07E212F8>: operation 6 progress -1
2010-10-29 18:31:36.635 [4792:14a8]: <Recovery Mode Device 07E212F8>: operation 7 progress -1
2010-10-29 18:31:36.772 [4792:14a8]: <Recovery Mode Device 07E212F8>: operation 8 progress -1
2010-10-29 18:31:36.772 [4792:14a8]: <Recovery Mode Device 07E212F8>: operation 9 progress -1
2010-10-29 18:31:36.773 [4792:14a8]: <Recovery Mode Device 07E212F8>: Recovery mode succeeded
2010-10-29 18:31:38.823 [4792:1710]: WinAMRestore::OnInterfaceRemoval: \\?\USB#VID05AC&PID1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#e95afe21
2010-10-29 18:31:38.826 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7ea30, notify: 2, connected: 0
2010-10-29 18:31:38.826 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7e850, notify: 2, connected: 0
2010-10-29 18:31:38.826 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7ed00, notify: 2, connected: 1
2010-10-29 18:31:38.826 [4792:1710]: AppleDevice::NotifyDisconnect: IBOOT, IBOOT \\?\USB#VID05AC&PID1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#e95afe21, inst: 0x7c7ed00
2010-10-29 18:31:38.826 [4792:1710]: IBOOT, DFU \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#e95afe21, inst: 0x7c7ed00
2010-10-29 18:31:38.828 [4792:1710]: _AMRecoveryModeDeviceFinalize: 07E212F8
2010-10-29 18:31:38.836 [4792:1710]: WinAMRestore::OnInterfaceRemoval: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#e95afe21
2010-10-29 18:31:38.838 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7ea30, notify: 2, connected: 0
2010-10-29 18:31:38.838 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7e850, notify: 2, connected: 0
2010-10-29 18:31:38.838 [4792:1710]: WinAMRestore::ProcessDevNodesChanges: device: 0x07c7ed00, notify: 2, connected: 0
2010-10-29 18:31:46.023 [4792:494]: iTunes: received kAMDeviceAttached action, device 07E95F90, AFC error 0XE8000028
2010-10-29 18:31:46.023 [4792:494]: iTunes: Restore-mode device appeared, device 07E95F90
2010-10-29 18:31:46.023 [4792:494]: iTunes: Creating restore mode device with usbMuxDeviceID 0X4
2010-10-29 18:31:46.023 [4792:494]: <Restore Device 07F01578>: operation 3 progress -1
2010-10-29 18:31:46.026 [4792:494]: <Restore Device 07F01578>: operation 4 progress -1
2010-10-29 18:31:46.047 [4792:494]: Supports value queries: 1
2010-10-29 18:31:46.065 [4792:cfc]: <Restore Device 07F01578>: operation 44 progress -1
2010-10-29 18:31:46.065 [4792:cfc]: requested restore behavior: Erase
2010-10-29 18:31:46.071 [4792:cfc]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
2010-10-29 18:31:46.080 [4792:cfc]: device did not return saved USB log
2010-10-29 18:31:46.080 [4792:cfc]: device did not return saved panic log
2010-10-29 18:31:46.098 [4792:cfc]: connected to service com.apple.mobile.restored
2010-10-29 18:31:46.098 [4792:cfc]: using protocol version 12
2010-10-29 18:31:46.114 [4792:cfc]: unable to open device_map.txt: No such file or directory
2010-10-29 18:31:46.115 [4792:cfc]: board config = n82ap
2010-10-29 18:31:46.166 [4792:cfc]: <Restore Device 07F01578>: operation 28 progress -1
2010-10-29 18:31:49.175 [4792:cfc]: <Restore Device 07F01578>: operation 28 progress -1
2010-10-29 18:31:52.184 [4792:cfc]: <Restore Device 07F01578>: operation 28 progress -1
2010-10-29 18:31:55.190 [4792:cfc]: <Restore Device 07F01578>: operation 28 progress -1
2010-10-29 18:32:13.018 [4792:cfc]: <Restore Device 07F01578>: operation 11 progress -1
2010-10-29 18:32:14.225 [4792:cfc]: <Restore Device 07F01578>: operation 12 progress -1
2010-10-29 18:32:23.581 [4792:cfc]: <Restore Device 07F01578>: operation 12 progress -1
2010-10-29 18:32:32.877 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 0
2010-10-29 18:32:42.886 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 1
2010-10-29 18:32:42.886 [4792:cfc]: ASR progress: Initialized communication with client
2010-10-29 18:32:47.894 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 5
2010-10-29 18:32:47.894 [4792:cfc]: ASR progress: Starting to send payload
2010-10-29 18:32:48.497 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 6
2010-10-29 18:32:48.497 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:32:50.148 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 7
2010-10-29 18:32:50.148 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:32:51.627 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 8
2010-10-29 18:32:51.627 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:32:56.511 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 9
2010-10-29 18:32:56.511 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:32:57.635 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 10
2010-10-29 18:32:57.635 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:32:58.838 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 11
2010-10-29 18:32:58.838 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:00.456 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 12
2010-10-29 18:33:00.456 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:02.341 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 13
2010-10-29 18:33:02.341 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:04.306 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 14
2010-10-29 18:33:04.306 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:06.130 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 15
2010-10-29 18:33:06.130 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:08.006 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 16
2010-10-29 18:33:08.006 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:09.695 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 17
2010-10-29 18:33:09.695 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:11.438 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 18
2010-10-29 18:33:11.438 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:13.252 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 19
2010-10-29 18:33:13.252 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:15.373 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 20
2010-10-29 18:33:15.373 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:17.272 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 21
2010-10-29 18:33:17.272 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:18.910 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 22
2010-10-29 18:33:18.910 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:20.896 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 23
2010-10-29 18:33:20.896 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:22.677 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 24
2010-10-29 18:33:22.677 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:25.545 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 25
2010-10-29 18:33:25.545 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:29.106 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 26
2010-10-29 18:33:29.106 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:31.174 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 27
2010-10-29 18:33:31.174 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:32.874 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 28
2010-10-29 18:33:32.874 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:34.856 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 29
2010-10-29 18:33:34.856 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:37.016 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 30
2010-10-29 18:33:37.016 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:39.167 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 31
2010-10-29 18:33:39.167 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:41.036 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 32
2010-10-29 18:33:41.037 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:42.893 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 33
2010-10-29 18:33:42.893 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:44.994 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 34
2010-10-29 18:33:44.994 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:46.698 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 35
2010-10-29 18:33:46.698 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:48.606 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 36
2010-10-29 18:33:48.606 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:50.612 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 37
2010-10-29 18:33:50.612 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:52.323 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 38
2010-10-29 18:33:52.323 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:54.349 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 39
2010-10-29 18:33:54.349 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:56.708 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 40
2010-10-29 18:33:56.708 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:33:58.641 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 41
2010-10-29 18:33:58.641 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:00.392 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 42
2010-10-29 18:34:00.392 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:02.432 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 43
2010-10-29 18:34:02.432 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:04.260 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 44
2010-10-29 18:34:04.260 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:06.279 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 45
2010-10-29 18:34:06.279 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:07.771 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 46
2010-10-29 18:34:07.771 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:09.049 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 47
2010-10-29 18:34:09.049 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:10.371 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 48
2010-10-29 18:34:10.371 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:11.377 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 49
2010-10-29 18:34:11.377 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:12.866 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 50
2010-10-29 18:34:12.866 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:14.823 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 51
2010-10-29 18:34:14.823 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:16.635 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 52
2010-10-29 18:34:16.635 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:18.296 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 53
2010-10-29 18:34:18.296 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:19.974 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 54
2010-10-29 18:34:19.974 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:22.094 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 55
2010-10-29 18:34:22.095 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:23.715 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 56
2010-10-29 18:34:23.715 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:25.522 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 57
2010-10-29 18:34:25.522 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:27.257 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 58
2010-10-29 18:34:27.257 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:29.282 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 59
2010-10-29 18:34:29.282 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:31.046 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 60
2010-10-29 18:34:31.046 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:32.803 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 61
2010-10-29 18:34:32.803 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:34.793 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 62
2010-10-29 18:34:34.793 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:36.504 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 63
2010-10-29 18:34:36.504 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:38.002 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 64
2010-10-29 18:34:38.002 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:39.773 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 65
2010-10-29 18:34:39.774 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:41.840 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 66
2010-10-29 18:34:41.840 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:43.981 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 67
2010-10-29 18:34:43.981 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:45.839 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 68
2010-10-29 18:34:45.839 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:47.199 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 69
2010-10-29 18:34:47.199 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:48.985 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 70
2010-10-29 18:34:48.985 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:51.355 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 71
2010-10-29 18:34:51.355 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:52.445 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 72
2010-10-29 18:34:52.445 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:54.983 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 73
2010-10-29 18:34:54.983 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:57.231 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 74
2010-10-29 18:34:57.231 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:34:59.298 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 75
2010-10-29 18:34:59.298 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:01.791 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 76
2010-10-29 18:35:01.791 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:03.915 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 77
2010-10-29 18:35:03.915 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:06.475 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 78
2010-10-29 18:35:06.475 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:08.622 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 79
2010-10-29 18:35:08.622 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:10.475 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 80
2010-10-29 18:35:10.475 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:12.825 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 81
2010-10-29 18:35:12.826 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:15.170 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 82
2010-10-29 18:35:15.170 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:17.219 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 83
2010-10-29 18:35:17.219 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:19.209 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 84
2010-10-29 18:35:19.209 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:21.858 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 85
2010-10-29 18:35:21.858 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:23.512 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 86
2010-10-29 18:35:23.513 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:26.246 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 87
2010-10-29 18:35:26.246 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:27.771 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 88
2010-10-29 18:35:27.771 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:29.640 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 89
2010-10-29 18:35:29.641 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:31.919 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 90
2010-10-29 18:35:31.919 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:33.844 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 91
2010-10-29 18:35:33.844 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:35.697 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 92
2010-10-29 18:35:35.697 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:37.876 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 93
2010-10-29 18:35:37.876 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:39.967 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 94
2010-10-29 18:35:39.967 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:41.920 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 95
2010-10-29 18:35:41.920 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:43.925 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 96
2010-10-29 18:35:43.925 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:46.514 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 97
2010-10-29 18:35:46.514 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:49.226 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 98
2010-10-29 18:35:49.226 [4792:cfc]: ASR progress: Sending payload
2010-10-29 18:35:52.359 [4792:cfc]: <Restore Device 07F01578>: operation 13 progress 100
2010-10-29 18:35:52.359 [4792:cfc]: ASR progress: Finished
2010-10-29 18:35:57.555 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 2
2010-10-29 18:35:59.155 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 4
2010-10-29 18:36:00.761 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 6
2010-10-29 18:36:02.372 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 8
2010-10-29 18:36:04.017 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 10
2010-10-29 18:36:05.582 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 12
2010-10-29 18:36:07.189 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 14
2010-10-29 18:36:08.796 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 16
2010-10-29 18:36:10.403 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 18
2010-10-29 18:36:12.011 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 20
2010-10-29 18:36:13.617 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 22
2010-10-29 18:36:15.223 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 24
2010-10-29 18:36:16.831 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 26
2010-10-29 18:36:18.437 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 28
2010-10-29 18:36:20.043 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 30
2010-10-29 18:36:21.650 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 32
2010-10-29 18:36:23.257 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 34
2010-10-29 18:36:24.864 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 36
2010-10-29 18:36:26.470 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 38
2010-10-29 18:36:28.078 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 40
2010-10-29 18:36:29.684 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 42
2010-10-29 18:36:31.559 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 44
2010-10-29 18:36:33.165 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 46
2010-10-29 18:36:34.771 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 48
2010-10-29 18:36:36.379 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 50
2010-10-29 18:36:37.986 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 52
2010-10-29 18:36:39.593 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 54
2010-10-29 18:36:41.199 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 56
2010-10-29 18:36:42.806 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 58
2010-10-29 18:36:44.412 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 60
2010-10-29 18:36:46.021 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 62
2010-10-29 18:36:47.626 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 64
2010-10-29 18:36:49.232 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 66
2010-10-29 18:36:50.840 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 68
2010-10-29 18:36:52.448 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 70
2010-10-29 18:36:54.054 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 72
2010-10-29 18:36:55.660 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 74
2010-10-29 18:36:57.267 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 76
2010-10-29 18:36:58.875 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 78
2010-10-29 18:37:00.481 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 80
2010-10-29 18:37:02.088 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 82
2010-10-29 18:37:03.695 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 84
2010-10-29 18:37:05.570 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 86
2010-10-29 18:37:07.176 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 88
2010-10-29 18:37:08.783 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 90
2010-10-29 18:37:10.390 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 92
2010-10-29 18:37:11.998 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 94
2010-10-29 18:37:13.605 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 96
2010-10-29 18:37:15.211 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 98
2010-10-29 18:37:16.608 [4792:cfc]: <Restore Device 07F01578>: operation 14 progress 100
2010-10-29 18:37:16.783 [4792:cfc]: <Restore Device 07F01578>: operation 15 progress -1
2010-10-29 18:37:33.476 [4792:cfc]: <Restore Device 07F01578>: operation 16 progress -1
2010-10-29 18:37:33.634 [4792:cfc]: <Restore Device 07F01578>: operation 15 progress -1
2010-10-29 18:37:37.438 [4792:cfc]: <Restore Device 07F01578>: operation 16 progress -1
2010-10-29 18:37:37.598 [4792:cfc]: <Restore Device 07F01578>: operation 27 progress -1
2010-10-29 18:37:39.923 [4792:cfc]: <Restore Device 07F01578>: operation 27 progress -1
2010-10-29 18:37:41.266 [4792:cfc]: <Restore Device 07F01578>: operation 17 progress -1
2010-10-29 18:37:41.610 [4792:cfc]: <Restore Device 07F01578>: operation 25 progress -1
2010-10-29 18:37:42.477 [4792:cfc]: <Restore Device 07F01578>: operation 35 progress -1
2010-10-29 18:37:42.841 [4792:cfc]: <Restore Device 07F01578>: operation 18 progress 0
2010-10-29 18:56:50.170 [4792:494]: iTunes: received kAMDeviceDetached action, device 07E95F90
2010-10-29 18:56:50.171 [4792:cfc]: recv(4384, 4) failed: connection closed
2010-10-29 18:56:50.171 [4792:cfc]: unable to read message size: -1
2010-10-29 18:56:50.171 [4792:cfc]: unable to read message from device
2010-10-29 18:56:50.171 [4792:cfc]: AMRAuthInstallDeletePersonalizedBundle
2010-10-29 18:56:50.236 [4792:cfc]: removed personalized bundle
2010-10-29 18:56:50.236 [4792:cfc]: <Restore Device 07F01578>: Restore failed (result = 9)
2010-10-29 18:56:50.332 [4792:494]: iTunes: Restore error 9
{quote} -
Since the latest update, most of my third party apps no longer work, none of my photo software, torrent programs, open office, NOTHING!! It is most frustrating - is there a way to 'downgrade' and go back to a previous version of the firmware, or am I just stuck with no apps that work?
They just don't open, and i get an error message like this:
Process:
Google Chrome [27305]
Path:
/Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Identifier:
com.google.Chrome
Version:
27.0.1453.93 (1453.93)
Code Type:
X86 (Native)
Parent Process: launchd [166]
User ID:
501
Date/Time:
2013-05-26 08:08:17.911 +0930
OS Version:
Mac OS X 10.8.3 (12D78)
Report Version: 10
Interval Since Last Report:
28298 sec
Crashes Since Last Report:
13993583
Per-App Crashes Since Last Report: 1
Anonymous UUID:
1681FA19-E0EA-448F-4E99-067A50E38854
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
/usr/lib/libz.1.dylib
Dyld Error Message:
Library not loaded: /usr/lib/libz.1.dylib
Referenced from: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
Reason: not a dylib
Binary Images:
0xb000 -
0xbff3 +com.google.Chrome (27.0.1453.93 - 1453.93) <7ABACF68-7D3E-30FA-8B03-9A1C0FFFF4F9> /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
0xf000 - 0x408ffaf +com.google.Chrome.framework (27.0.1453.93 - 1453.93) <C691C1FF-CF8A-3CFA-9F0D-10CDAFA2540F> /Applications/Google Chrome.app/Contents/Versions/27.0.1453.93/Google Chrome Framework.framework/Google Chrome Framework
0x43b8000 - 0x4f74ff7 com.apple.AppKit (6.8 - 1187.37) <6FBB3467-04F9-395F-8EA8-C84347C5BE43> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x5491000 - 0x5491fff com.apple.ApplicationServices (45 - 45) <677C4ACC-9D12-366F-8A87-B898AC806DD9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x549c000 - 0x54c1ff7 com.apple.CoreVideo (1.8 - 99.4) <A26DE896-32E0-3D5E-BA89-02AD23FA96B3> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x54dc000 - 0x55a5ff3 com.apple.Bluetooth (4.1.3 - 4.1.3f3) <7909C26F-90FB-359F-84DD-51583A2DC3DA> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
0x55f8000 - 0x563affb com.apple.RemoteViewServices (2.0 - 80.6) <AE962502-4539-3893-A2EB-9D384652AEAC> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/Remot eViewServices
0x5665000 - 0x587cfff com.apple.CoreData (106.1 - 407.7) <17FD06D6-AD7C-345A-8FA4-1F0FBFF4DAE1> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x592a000 - 0x5ae6ffd libicucore.A.dylib (491.11.2) <59A23F06-16AD-35F8-BA58-D17305232402> /usr/lib/libicucore.A.dylib
0x8fe0a000 - 0x8fe3ce57 dyld (210.2.3) <23516BE4-29BE-350C-91C9-F36E7999F0F1> /usr/lib/dyld
0x902fe000 - 0x90362ff3 libstdc++.6.dylib (56) <F8FA490A-8F3C-3645-ABF5-78926CE9C62C> /usr/lib/libstdc++.6.dylib
0x90ce3000 - 0x90e5bff5 com.apple.QuartzCore (1.8 - 304.2) <FB737C74-C460-32A3-9107-D2112BAE6EBC> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x9120e000 - 0x9132affb com.apple.desktopservices (1.7.3 - 1.7.3) <7157C51D-C695-3C9E-B532-F551E7E55B56> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x9132b000 - 0x91488ffb com.apple.QTKit (7.7.1 - 2599.24) <39CC892D-2874-33FE-BE30-87FE07D875BD> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0x9148c000 - 0x91599057 libobjc.A.dylib (532.2) <FA455371-7395-3D58-A89B-D1520612D1BC> /usr/lib/libobjc.A.dylib
0x91d3a000 - 0x91d7cff7 libcups.2.dylib (327.3) <C7A4A315-FA15-354B-8BC9-BE824C4EFF6D> /usr/lib/libcups.2.dylib
0x91df4000 - 0x920b4ff3 com.apple.security (7.0 - 55179.11) <165A3105-9ADF-329B-93FC-3C8EFAEDDD13> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x9302b000 - 0x93213ffb com.apple.CoreFoundation (6.8 - 744.18) <68AFEE40-0078-347E-9DEE-32CFE0062A10> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x93573000 - 0x93573fff com.apple.Accelerate (1.8 - Accelerate 1.8) <4EC0548E-3A3F-310D-A366-47B51D5B6398> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x93a62000 - 0x93a62ffd com.apple.audio.units.AudioUnit (1.8 - 1.8) <D35BA73D-1E56-3A1D-9F9F-971F3BF8C136> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x93f64000 - 0x93fccff7 com.apple.framework.IOKit (2.0.1 - 755.22.5) <F9A70D23-1108-3616-9DE3-6C5730CA7AB2> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x94474000 - 0x944a3ff7 com.apple.securityinterface (6.0 - 55024.4) <7C5E28DC-F8BE-3238-883F-E1646A2AF895> /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInter face
0x94760000 - 0x947c4fff com.apple.datadetectorscore (4.1 - 269.2) <B4D53047-C613-32F8-9E08-0154EA81B487> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
0x94884000 - 0x948defff com.apple.ImageCaptureCore (5.0.2 - 5.0.2) <BB0D85EE-A85D-3E7B-B04E-720886553258> /System/Library/Frameworks/ImageCaptureCore.framework/Versions/A/ImageCaptureCo re
0x949b2000 - 0x949f4ff7 libauto.dylib (185.1) <B2B5B639-6778-352A-828D-FD8B64A3E8B3> /usr/lib/libauto.dylib
0x949f9000 - 0x949f9fff com.apple.Cocoa (6.7 - 19) <354094F0-F36B-36F9-BF5F-FD60590FBEB9> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x95365000 - 0x95365fff libSystem.B.dylib (169.3) <81C58EAB-0E76-3EAB-BDFD-C5A6FE95536F> /usr/lib/libSystem.B.dylib
0x95366000 - 0x953b4ff3 com.apple.SystemConfiguration (1.12.2 - 1.12.2) <6E858B9F-337A-314E-88B7-24A274ACE568> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x95490000 - 0x9549efff com.apple.opengl (1.8.7 - 1.8.7) <0631EC1D-833B-39D2-A907-A9F7617E5504> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x9549f000 - 0x95588ff7 libxml2.2.dylib (22.3) <015A4FA6-5BB9-3F95-AFB8-B9281E22685B> /usr/lib/libxml2.2.dylib
0x95868000 - 0x95b86ff3 com.apple.Foundation (6.8 - 945.16) <C4D95341-B4FF-30AC-815A-A23C019C57A3> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x95e49000 - 0x95fa1ffb com.apple.audio.toolbox.AudioToolbox (1.8 - 1.8) <0D36953C-9897-3E9B-8C70-847E90B203A2> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x97b16000 - 0x97b74ff7 com.apple.audio.CoreAudio (4.1.1 - 4.1.1) <953DD669-8C6E-387D-AB3F-D8C8965347DF> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x97bc5000 - 0x97e5ffff com.apple.AddressBook.framework (7.1 - 1169) <AF50144A-A327-3367-81B1-95B3D46E56F0> /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
0x99699000 - 0x99a7cfff com.apple.HIToolbox (2.0 - 626.1) <ECC3F04F-C4B7-35BF-B10E-183B749DAB92> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x99c23000 - 0x99c2cfff com.apple.DiskArbitration (2.5.2 - 2.5.2) <89822A83-B450-3363-8E9C-9B80CB4450B1> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x99c2d000 - 0x99c37fff com.apple.speech.recognition.framework (4.1.5 - 4.1.5) <B855E8B4-2EE3-3BFF-8547-98A0F084F9AF> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x99f02000 - 0x99f1fff7 libresolv.9.dylib (51) <B9742A2A-DF15-3F6E-8FCE-778A58214B3A> /usr/lib/libresolv.9.dylib
0x99f20000 - 0x99f20fff com.apple.Carbon (154 - 155) <604ADD9D-5835-3294-842E-3A4AEBCCB548> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x9a08f000 - 0x9a08ffff com.apple.CoreServices (57 - 57) <956C6C6D-A5DD-314F-9C57-4A61D41F30CE> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
Model: MacBookPro8,2, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2 GHz, 4 GB, SMC 1.69f4
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB
Graphics: AMD Radeon HD 6490M, AMD Radeon HD 6490M, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.100.16)
Bluetooth: Version 4.1.3f3 11349, 2 service, 18 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: ST9500325ASG, 500.11 GB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 3
USB Device: My Passport 071A, 0x1058 (Western Digital Technologies, Inc.), 0x071a, 0xfa130000 / 6
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 5
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 7
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0245, 0xfa120000 / 4
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 2
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3 -
CME\7960 running SIP firmware - How do i setup incoming calls? - Can anyone help please?
Hi Guys,
I have a SIP trunk setup with a 2811 running CME version 7. I can make outbound calls ok but having issues getting the incoming calls working, i have 1 number on my SIP trunk and that is 01133501788 and i want that to ring my Cisco 7960 which is running SIP firmware not SCCP. I have included by config for anyone who can help me, i just want the incoming call to work.
Many Thanks.
Matthew.
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname Router
boot-start-marker
boot-end-marker
logging message-counter syslog
no aaa new-model
clock timezone GMT 0
dot11 syslog
ip source-route
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.1.1
ip dhcp excluded-address 10.10.10.1
ip dhcp pool DATA_POOL
network 10.10.10.0 255.255.255.0
default-router 10.10.10.1
dns-server 188.92.232.50 188.92.232.100
ip dhcp pool VOICE_POOL
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
dns-server 188.92.232.50 188.92.232.100
option 150 ip 192.168.1.1
ip name-server 188.92.232.50
ip name-server 188.92.232.100
no ipv6 cef
multilink bundle-name authenticated
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
no supplementary-service sip moved-temporarily
no supplementary-service sip refer
sip
bind control source-interface FastEthernet0/1.20
bind media source-interface FastEthernet0/1.20
registrar server
voice class codec 1
codec preference 2 g711ulaw
codec preference 3 g711alaw
voice register global
mode cme
source-address 192.168.1.1 port 5060
max-dn 144
max-pool 42
load 7960-7940 P0S3-8-12-00
authenticate register
tftp-path flash:
create profile sync 0008072514198272
voice register dn 1
number 6999
allow watch
name SIP
label SIP
voice register pool 1
id mac 000F.902B.40E0
type 7960
number 1 dn 1
dtmf-relay sip-notify
username cisco password cisco
codec g711ulaw
voice translation-rule 1
rule 1 /^9\(.*\)/ /\1/
voice translation-rule 2
rule 1 /^6...$/ /4143*002/
voice translation-profile DiscardDigit9
translate calling 2
translate called 1
voice translation-profile IncomingSIP
translate calling 1133501788
voice-card 0
no dspfarm
username matt privilege 15 secret 5 $1$DCD0$SjWqnKgDSGVzzIKRerXh11
archive
log config
hidekeys
interface FastEthernet0/0
ip address 194.12.0.222 255.255.255.252
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
interface FastEthernet0/1
no ip address
ip nat inside
ip virtual-reassembly
duplex auto
speed auto
interface FastEthernet0/1.10
description DATA
encapsulation dot1Q 10
ip address 10.10.10.1 255.255.255.0
ip nat inside
ip virtual-reassembly
interface FastEthernet0/1.20
description VOICE
encapsulation dot1Q 20
ip address 192.168.1.1 255.255.255.0
ip nat inside
ip virtual-reassembly
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 194.12.0.221
ip http server
ip http authentication local
no ip http secure-server
ip nat inside source list 1 interface FastEthernet0/0 overload
access-list 1 permit 192.168.1.0 0.0.0.255
access-list 1 permit 10.10.10.0 0.0.0.255
tftp-server flash:P003-8-12-00.bin
tftp-server flash:P003-8-12-00.sbn
tftp-server flash:P0S3-8-12-00.loads
tftp-server flash:P0S3-8-12-00.sb2
tftp-server flash:P003-8-12-00
tftp-server flash:P003-8-12-00.loads
tftp-server flash:P003-8-12-00.sb2
tftp-server flash:SIP000F902B40E0.cnf.xml
control-plane
mgcp behavior g729-variants static-pt
dial-peer cor custom
dial-peer voice 2 voip
description Outgoing Geographic
translation-profile outgoing DiscardDigit9
destination-pattern 0[7]........
voice-class codec 1
session protocol sipv2
session target dns:sip.cloudcalling.co.uk
dtmf-relay rtp-nte
no vad
dial-peer voice 1 voip
description IncomingSIP
translation-profile incoming IncomingSIP
voice-class codec 1
session protocol sipv2
session target dns:sip.cloudcalling.co.uk
incoming called-number .T
dtmf-relay sip-notify rtp-nte
no vad
sip-ua
credentials username 4143*002 password 7 password realm sip.cloudcalling.co.uk
authentication username 4143*002 password 7 password
nat symmetric role passive
nat symmetric check-media-src
calling-info sip-to-pstn number set 4143*002
no remote-party-id
retry invite 3
retry register 3
timers connect 100
registrar dns:sip.cloudcalling.co.uk expires 60
sip-server dns:sip.cloudcalling.co.uk
host-registrar
gatekeeper
shutdown
telephony-service
load 7960-7940 P0S3-8-12-00
max-ephones 24
max-dn 30
ip source-address 192.168.1.1 port 2000
max-conferences 8 gain -6
web admin system name Admin secret 5 $1$Fktw$t9GQkdDdHmoYdwptO8.or.
transfer-system full-consult
create cnf-files version-stamp Jan 01 2002 00:00:00
line con 0
line aux 0
line vty 0 4
login
scheduler allocate 20000 1000
ntp server 85.119.80.232
end
Router#You my friend are a star! worked straight away, many thanks. Just one more thing, when i make an outgoing call, it always appears as "blocked" on my phone, my sip trunk is set to allow CME to alter outgoing CLI's how would i program the outgoing CLI to 01133501788 also?
The new working config is below with your suggestion, which works!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname Router
boot-start-marker
boot-end-marker
logging message-counter syslog
no aaa new-model
clock timezone GMT 0
dot11 syslog
ip source-route
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.1.1
ip dhcp excluded-address 10.10.10.1
ip dhcp pool DATA_POOL
network 10.10.10.0 255.255.255.0
default-router 10.10.10.1
dns-server 188.92.232.50 188.92.232.100
ip dhcp pool VOICE_POOL
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
dns-server 188.92.232.50 188.92.232.100
option 150 ip 192.168.1.1
ip name-server 188.92.232.50
ip name-server 188.92.232.100
no ipv6 cef
multilink bundle-name authenticated
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
no supplementary-service sip moved-temporarily
no supplementary-service sip refer
sip
registrar server
voice class codec 1
codec preference 2 g711ulaw
codec preference 3 g711alaw
voice register global
mode cme
source-address 192.168.1.1 port 5060
max-dn 144
max-pool 42
load 7960-7940 P0S3-8-12-00
authenticate register
tftp-path flash:
create profile sync 0015244443466064
voice register dn 1
number 6999
allow watch
name SIP
label SIP
voice register pool 1
id mac 000F.902B.40E0
type 7960
number 1 dn 1
dtmf-relay sip-notify
username cisco password cisco
codec g711ulaw
voice translation-rule 1
rule 1 /^6...$/ /4143*002/
voice translation-rule 3
rule 1 /^01133501788$/ /6999/
rule 2 /^1133501788$/ /6999/
voice translation-profile IncomingSIP
translate called 3
voice translation-profile Translatetrunk
translate calling 1
voice-card 0
no dspfarm
username matt privilege 15 secret 5 $1$DCD0$SjWqnKgDSGVzzIKRerXh11
archive
log config
hidekeys
interface FastEthernet0/0
ip address 194.12.0.222 255.255.255.252
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
interface FastEthernet0/1
no ip address
ip nat inside
ip virtual-reassembly
duplex auto
speed auto
interface FastEthernet0/1.10
description DATA
encapsulation dot1Q 10
ip address 10.10.10.1 255.255.255.0
ip nat inside
ip virtual-reassembly
interface FastEthernet0/1.20
description VOICE
encapsulation dot1Q 20
ip address 192.168.1.1 255.255.255.0
ip nat inside
ip virtual-reassembly
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 194.12.0.221
ip http server
ip http authentication local
no ip http secure-server
ip nat inside source list 1 interface FastEthernet0/0 overload
access-list 1 permit 192.168.1.0 0.0.0.255
access-list 1 permit 10.10.10.0 0.0.0.255
tftp-server flash:P003-8-12-00.bin
tftp-server flash:P003-8-12-00.sbn
tftp-server flash:P0S3-8-12-00.loads
tftp-server flash:P0S3-8-12-00.sb2
tftp-server flash:P003-8-12-00
tftp-server flash:P003-8-12-00.loads
tftp-server flash:P003-8-12-00.sb2
tftp-server flash:SIP000F902B40E0.cnf.xml
control-plane
mgcp behavior g729-variants static-pt
dial-peer cor custom
dial-peer voice 1 voip
description IncomingSIP
translation-profile incoming IncomingSIP
voice-class codec 1
session protocol sipv2
session target sip-server
incoming called-number .T
dtmf-relay sip-notify rtp-nte
no vad
dial-peer voice 2 voip
description Outgoing Geographic
translation-profile outgoing Translatetrunk
destination-pattern 0[7]........
voice-class codec 1
session protocol sipv2
session target dns:sip.cloudcalling.co.uk
dtmf-relay rtp-nte
no vad
sip-ua
credentials username 4143*002 password 7 password realm sip.cloudcalling.co.uk
authentication username 4143*002 password 7 password
nat symmetric role passive
nat symmetric check-media-src
calling-info sip-to-pstn number set 4143*002
no remote-party-id
retry invite 3
retry register 3
timers connect 100
registrar dns:sip.cloudcalling.co.uk expires 60
sip-server dns:sip.cloudcalling.co.uk
host-registrar
gatekeeper
shutdown
telephony-service
load 7960-7940 P0S3-8-12-00
max-ephones 24
max-dn 30
ip source-address 192.168.1.1 port 2000
max-conferences 8 gain -6
web admin system name Admin secret 5 $1$Fktw$t9GQkdDdHmoYdwptO8.or.
transfer-system full-consult
create cnf-files version-stamp 7960 Dec 17 2013 14:35:13
line con 0
line aux 0
line vty 0 4
login
scheduler allocate 20000 1000
ntp server 85.119.80.232
end
Router# -
Satellite R630-155 - Fan is too noisy and SSD upgrade
I am the owner of a Toshiba Satellite R630-155 (Core i5-480). My problems are:
1. The fan is too noisy and never stops. In normal operation (browsing and general office work) there is a constant high pitch noise that is audible three to four meters away in an office environment - in high load you just can't stand it!!! The fan never stops... even when you are doing nothing...
2. Heat is a big problem. The bottom of the laptop is constantly overheating and i have to place it on my desk in a way that the bottom left corner is outside of the table so it can breath fresh air from below - if not, the temperature rises and the (loud) fan is unable to keep up. When i work with the laptop while sitting on a sofa, i have to place a thick book between the laptop and my legs. The book must be thick (more than an inch) with hard covers, otherwise the heat passes through the book!!!!
3. Last (but not least, i just mention the biggest problems here) it's the problem with SSD installation. I bought a used Corsair F80 (80Gb SSD) from a friend, but i was unable to use it with the Toshiba - the BIOS was not detecting the disk. I tried installing all latest firmware updates for both laptop and SSD but i had no success. Then i gave the disk back and i bought a brand new Zalman 128Gb SSD (SSD0128N1 Sandforce) but i had exactly the same problem. I contacted my local Toshiba support and after a lot of conversation the only answer i got is that the laptop is not compatible with those SSD's and this is acceptable by Toshiba and not their problem. They told me that if i need an SSD upgrade i can only go for the Toshiba SSD that is installed on the portege series, which is sold by Toshiba for a ridiculously expensive price - about $500 for 128Gb. I contacted the European support center and i got the exact same reply. I searched on the Internet and i found someone else with the exact same problem with a Corsair 128Gb SSD - he found that the laptop detects the SSD after ten to twenty reboots. I tried that and it was true - after a lot of reboots the laptop detected the Zalman disk and i was able to install Windows 7 successfully, but the process is unacceptable. Also the disk is benchmarked by official sites at the speed of an OCZ Vertex 2 128Gb (and slightly better), but when i ran a benchmark in the Toshiba, the results I got were below half of the advertised speed. Same benchmark in another machine for the same disk, resulted in the advertised speeds.
Shame for Toshiba... nice design and portability but everything else is a big flaw. Their support in non existent and they do not value their customers. I feel they stole my money and I'll never buy a Toshiba laptop again.
Sorry for the big message, but I need I have to warn potential customers. Can someone help me with any of the above problems? Do you have the same problems too?
To be continued...Hi buddy,
Regarding the fan and heat issue: Did you make BIOS update? Friend of me has Satellite R630 too and he told me that fan activity with new BIOS version 2.10 is reduced. Furthermore the notebook is cooler than before so I would recommend installing this update. You can download the BIOS update here:
http://eu.computers.toshiba-europe.com > Support & Downloads > Download Drivers
But before you start the BIOS update you should consider the following tips:
-Run update as Administrator only
-Unzip all files from zip archive before you start the update file
-Close all running programs and also the antivirus and firewall
-Make sure that battery is fully charged
Regarding the SSDs its always a little bit complicated installing 3rd party products and nobody can guarantee that such parts would work. You are always on safely side with original Toshiba spare parts.
Everything what you can do is installing the newest firmware for SSD and hope that it works but who knows maybe the BIOS update will also help you in this case ;)
Maybe you are looking for
-
Edit a form in Acrobat but NOT in Designer
I have Adobe Acrobat Professional 8.1.7 on Windows XP SP3. What I want to know is how to edit a form in Acrobat without using LiveCycle Designer. Here's the issue: with a PDF open (generated via either a print job or File>Create PDF) under the Forms
-
I'm trying to find out the mobile data network info on my iPhone 3GS it's on Vodafone at the moment but I want to use my orange sim so I need to change the pan details help
-
How to call a function with event
How do I call a function with a event inside it? function showTopTen(e:Event):void highscoreData = new XML(e.target.data); trace("Hiscores: " + highscoreData.item[0].name.text() + " - " + highscoreData.item[0].score.text()) //showTopTen(); .
-
Insane Object BDHP+58EBC, and +58DD4. Please help?
I have tried the suggestions in the KB "What is an Insane Object Error Mean and What Should I do?", but they did not clear my error. My vi functions normally, but I am concerned that this error may cause a "booby-trap" to be lurking in my distributed
-
LEAP support in Aironet 340 Bridge
Hi. Can anyone tell me if a Cisco Aironet 340 Bridge (BR342) acting as an access point will support LEAP. Does the client have to support it? Or does the access point have to support it? Or both? If Windows XP supports it, does a 340 client adapter h