12 V power supply / built in airport

any plans to add a 12V power supply input?
this would be very handy for the usage in motorhomes, cars, ships etc.
also a buildt in air port express would be great, one wire less...
so apple, go ahead and make Hi Hfi even better

You could introduce some noise by mounting a power supply inside of the SCXI chassis. The chassis itself does provide some degree of shielding, so you would be eliminating some of that shielding by placing that power supply inside. However, we have no specs for that because the chassis was not designed for that application. Another option may be to use the SCXI-1124 analog output module. While it has 6 channels with a +/- 10V range, you can cascade channels to get up to 60V per module. Below is the link to the SCXI-1124 produce page. I hope this information helps.
SCXI-1124

Similar Messages

  • Power Supply for Airport Extreme

    Hi
    Does anyone know where I can get a new power supply for my airport extreme in the UK? Mine has died, and I don't really want to buy a whole new base station just because of the external supply. (I know the actual unit is working through plugging in a power supply from my other base station)
    I tried Apple, who weren't really any help.
    Thanks in advance!
    Tom.

    Tom welcome to the discussions.
    I would probably call the Apple number.
    1-800-MY APPLE
    I am sure that they can point you in the right direction.
    I am a little shocked that one of the Apple Retail stores can't offer you a Power Supply.
    If all else fails, it sounds like you have tried an alternitve, if it works use it, until you can get a replacment.
    Don

  • Airport Extreme: Specification power supply

    Hello:
    after having read all the existing material on this site, I still have a very easy question:
    The power supply for the Airport Extreme, which electrical power range does it support? Does it only work in the US (100-120V) or would it also work abroad (eg. 100-240V)?
    Would be nice if someone could have a look at the bottom of the power supply and post the result.
    Thanks.
    Peter.

    The Airport Extreme Base Station (802.11n) supports 100-240V.
    Regards,
    Chris

  • Replacement power supply for Airport N base station?

    I'm in need of a replacement power supply for an Airport Extreme N base station.
    Is this something I can pick up at a friendly neighborhood Radio Shack, or do I need to order the OEM part from Apple?
    I don't need the automatic international voltage switching, just something that can power this puppy with US AC. Thanks.

    Tom welcome to the discussions.
    I would probably call the Apple number.
    1-800-MY APPLE
    I am sure that they can point you in the right direction.
    I am a little shocked that one of the Apple Retail stores can't offer you a Power Supply.
    If all else fails, it sounds like you have tried an alternitve, if it works use it, until you can get a replacment.
    Don

  • IMac G5 bluetooth + airport + power supply problems - oh and the dvd drive

    Yeah, seems like a lot is going wrong with my mac lately. I bought the iMac G5(no isight) model last year around july. I had some power issues (i.e. leaving the house with it turned on to come home and find it off) For the last year though that was all that was wrong. Once I had to reinstall OS X because it would not find the OS X harddrive during one of these power losses, but that was it.
    Then about two weeks ago, I came home to a turned off iMac. I thought the power had gone out in my apartment, but the clocks were all right, and to my surprise the iMac would not turned on. Because I am not under warranty I searched online and found an extended exchange program for my emc model. (http://www.apple.com/support/imac/powersupply/repairextension/) I made an appt at the apple store and they replaced the power supply.
    I got the machine back two nights ago and my bluetooth hardware wasn't recognized. And I now had a new "ink" system preference panel in the hardware section which aparently is some sort of handwriting recognition tablet. It ticked me off, but I just wanted to use my computer.
    Well today I came home from work and my computer was acting funny. Everywhere I clicked brought up dashboard. This had never happened before and I had no choice but to force a shutdown. Powered it back up and poof, there goes my airport card. No hardware recognized. Now I have a 25 ft cable running the floor of my apartment. This was cause enough to call apple. I was told to make another apointment to bring the computer in. The guy made it sound like it was no big deal to lug a 30 lb bulky computer 40 miles and through a crowded mall. He also made no promises that the repairs would be covered under the exchange program.
    I just wanted to hear any suggestions before I decide whether or not its worth it to bring in the computer. Nothing shows up in system profiler under bluetooth or airport. Should I just lie to the "genius" and tell them that my computer still shuts down randomly? I think that way they would at least replace the logic board (which I think is the problem) before telling me to sell my kidney and pay for repairs. I've tried reseting the SMU, and I looked at the bluetooth and airport cards to see if they had been accidently disconnected during the PS replacement. They are actually screwed into the logic board so I think their connections are efficient.
    Oh and about the DVD drive. I have to use two cd's in order to burn a single disc. The first disc I put in the drive NEVER works. It spins for about 30 seconds then starts buzzing like blender and spits the cd back out. The second blank disc I put in USUALLY works, but sometimes it takes three discs. This problem has always been there since day 1, but I don't burn enough cd's for it to be an issue.
    Thank you for listening to my gripes. I really don't think I'll make the mistake of buying the first issue of a model.
    iBook G4 900mghz, iMac G5 20" 2.0 ghz   Mac OS X (10.4.8)  

    OK, first thing -to restore your bluetooth, shut down, unplug for a few minutes and then reboot. Thay usually brings the BT back. You should also repair permissions. Reset your SMU nd your PRAM as well.
    Try those four things and please post back,
    Miriam

  • Where can I find a power supply for 2nd - 5th Generation Airport Extreme?

    I have an Airport Extreme that needs a power supply and cord.   Where can I purchase one?  Is this something Apple sells separately?  Or, if someone could supply the part numbef for their power supply that could aid in my search, that would be great.  I have a 4th generation AirPort Extreme that needs one.  Thanks!

    Amazon
    http://www.amazon.com/Genuine-EADP-20BB-supply-AirPort-Extreme/dp/B00AAQ3JE8/ref =pd_sim_sbs_e_1?ie=UTF8&refRID=07Z3H174172XDAET831A

  • I lost the power supply cable of my AirPort Extreme.

    I need a power supply cord for my AirPort Extreme.

    If it is the tall one, it is standard figure 8 power cable available in any store with electrical items. But not in white.. they are black and grey and even brown but never white. Also the Apple ones are top quality.
    If it is the flat one you are talking about the whole power supply. Any 12v 2A or greater with standard 2.5mm dc adapter will work fine.

  • Is airport  extreme working with 220 v  power supply?

    my cousin  gave me an airport extreme as present , bought in USA.Can I connect it with 220v power supply (greece) or what I must do to connect it to 220v power supply?

    It will accept AC input voltages between 100 and 240 AC,  50 to 60 HZ.  All you will need is an adapter plug to interface between the US plug and the Euro/Greece wall socket. These adapter plugs are low cost.

  • Airport Extreme Power supply

    I have a dome type Airport, which my daughter was using. Until she said it had stopped working. Got her to bring it over and found no power from the jack plug. So took the case apart. Power was reaching the circuit board, but no 5 volt out, so it was not the lead. I have made a start on looking for a replacement Transformer and noted that I have a Nokia phone one that has the same power out. Would it be worth fitting a jack to this, to use on the Airport. Or has someone an idea of a way of getting a replacement. Nothing like the Foxlink Tech. comes up on a search.
    Regards
    Dave

    Perhaps you will have better luck posting or starting a new thread in the Airport / Time Capsule category.
    http://discussions.apple.com/category.jspa?categoryID=140
    As far as your problem, I don't know the power requirements of the older Airport Extreme Base stations, but if the power requirements are listed on the device and you can find a transformer that can supply that (your nokia PS), then cut and splice the old end of the broken power supply and solder (do not twist) the old end onto the new PS.
    I don't know your electrical background but you want to make sure that you don't get the wires backwards on the plug. Make sure that you don't cut the wire to short on the plug end encase you need to repair again.
    Another solution is a universal power supply. Radio Shack and maybe Walmart sell these. They come with different voltage settings and different plugs that you can switch out. Keep in mind that they may not have the plug end that will match your AP.

  • Airport Extreme Power Supply Voltage?

    We just moved and apparently packed our AEBS separately from the power supply. Does anyone know the voltage and output current (or power) from the power supply so that I might use an alternative until we find the original?
    I hate to spend the $20 (and shipping) for a unit I'll find some days from now...
    Thanks,

    The Airport Extreme power supply brick output is rated at 5.1V DC, 2.4 A. The polarity of the plug's sleave is negative, the center terminal is positive.

  • Airport replacement power supply

    Hi,
    I have an Airport Extreme Base Station/802.11N-USA.
    The power supply blew out in a storm.
    Is the power supply on the Apple Store website
    the proper replacement? It does not look the same!
    It looks like the power supply for the older Airport devices.
    http://store.apple.com/1-800-MY-APPLE/WebObjects/AppleStore.woa/wa/RSLID?mco=18A D1F05&nplm=M9479LL/A
    If not, is there someplace to get a correct replacement?
    Thanks,
    John Boccio
    [email protected]

    Hi,
    I have an Airport Extreme Base Station/802.11N-USA.
    The power supply blew out in a storm.
    Is the power supply on the Apple Store website
    the proper replacement? It does not look the same!
    It looks like the power supply for the older Airport
    devices.
    http://store.apple.com/1-800-MY-APPLE/WebObjects/Apple
    Store.woa/wa/RSLID?mco=18AD1F05&nplm=M9479LL/A
    If not, is there someplace to get a correct
    replacement?
    Thanks,
    John Boccio
    [email protected]
    The power supply in the AEBSn is not a user-replaceable item. You will need to have it serviced by Apple or an Apple certified technician.

  • Airport extreme power supply buzzing sound

    My airport extreme model A1301 power brick is making a buzzing sound and I think is dropping my internet. has anyone encounter this problem?  can i just get a new power supply cord or replace the whole thing?

    A "buzzing" sound typically indicates a failed or faulty electrical component. Unfortunately, there is no user serviceable items on the AirPort's power brick. However, there are a number of vendors that offer replacements. If you bought your AirPort along with a Mac laptop or desktop, and have AppleCare, it may be possible to request a replacement from Apple.

  • Choosing the Right Power Supply

    First things first. If you've got a poor-quality and/or faulty power supply, nothing else you do will work to solve your problems. Stick to the basics before you go further...The short answer is to buy a hi-powered, brand name supply, like the new ENERMAX line (430 W or higher) or ANTEC True550. Almost nothing else will do with today's computers. In over 30 years of electronic/computer service, I have found that 85% or more of problems were power-related.
    If you want to know more, read on...
    Choosing The Right Power Supply
    If you’re reading this, there’s a good chance that one of my colleagues or I believe that you could be experiencing problems with your power supply, based upon the symptoms you mentioned in your post, and provided you with this link. Relax, you’re not alone. In 30 years of electronic and computer troubleshooting, I’d say that the majority of the electronic, mainframe, mini, and microcomputer problems I’ve diagnosed and repaired were with the basic power the problematic device was receiving. The symptoms often included random reboots, crashing, the BSOD, lockups, etc.
    (As the national support technician for few major computer service companies, working US Defense contracts, I was often the person that had to fly in and correct the problem, or “walk through” the on-site technician as he closely followed my instructions. I achieved success in my career by carefully reading the manuals, knowing where to go for more information that was otherwise unavailable to me, and/or systematically troubleshooting until the problems were discovered and repaired. I never had the option of giving up.)
    The most overlooked component when building or upgrading a PC is the power supply unit (PSU). Some people use their old case and PSU when they upgrade. Some use the PSU that came with their new case. Some people even buy a new PSU. And most inexperienced builders all make the same mistake: The PSU that they’re trying to use is simply inadequate for the job.
    Suppose you’re upgrading to a new motherboard, CPU, ram, and video card, but still using the old case and PSU. It’s most likely that you’re upgrading in order to build a machine that is more powerful, faster, has a more colorful display, can number-crunch more quickly, play the latest games, etc. These gains in performance all have one thing in common: They require more raw power. However, have you thought about where that power comes from?
    Suppose you’re building a new system with a new case and PSU. Has it occurred to you that the company that you bought the case/PSU from might make more money if they skimp on the supply, even if the supply has a large wattage rating? Most bulk power supply manufacturers don’t make good PSU’s. They use older, cheaper technology, and slap on labels that represent the PSU’s peak outputs, and not their continuous output rating. These companies are intentionally misleading you in order to sell you an inferior product. Brands I avoid when building/repairing my friends’ and family’s computers: Allied, Q-Tec, Chieftech, and many others.
    For those of you who bought a power supply separately, did you know that you’re only supposed to run a power supply continuously at 30-70% (with 50% being optimal) of its continuous rating for maximum efficiency (which means less heat to you)? Most inexperienced builders either buy PSU’s that are matched to their equipment’s continuous power usage, or ones that are even less powerful than they need. Why? Because they’re trying to save money.
    I mean, what’s the fun in a power supply? You don’t get any games with it, there’s no more storage, hardly ever any more bells and whistles, etc. A power supply is boring, and it’s supposed to be, because it’s supposed to provide a stable, reliable platform upon which the rest of the equipment can easily access the amount of power it needs, and when it’s needed. In almost EVERY review of powers supplies, the same point is stressed: Better safe than sorry.
    But what does safe vs sorry mean? It can mean that you don’t have to waste money on the wrong PSU in the first place, but it can also mean that you don’t have to replace your expensive ram, CPU, video card, etc. NEEDLESSLY, or because your cheap PSU destroyed them. What? A cheap power supply can wreck your computer? YES IT CAN. A cheap power supply can cause thermal damage, not only from the heat it produces, but also the heat it can create in your components as well. RAM is especially sensitive to heat, and there’s RAM in your CPU, your video cards, and, well, your RAM too. A cheap switching power supply, run at its maximum, or peak, continuously can also destroy components by creating RF (Radio Frequency) signals on your power rails, signals which the components on your peripheral devices were not equipped to handle in the first place.
    So this begs the question, how does one choose the right power supply? I’ll illustrate this using my own PC as the example. This is my setup that I use for video processing:
    K7N2G-ILSR
    Athlon 2500+ Barton @ 2125Mhz
    AMD Retail Heatsink/Fan
    2 - 512MB DDR333 w/Thermaltake Spreaders (slot 1&3)
    MSI TV@nywhere Video Capture
    ATI Radeon 9600
    120GB Maxtor DiamondMax Plus 9 SATA
    30GB Quantum IDE
    TEAC DV-W50E DVD/CD-R/W
    BTC DVD-ROM Drive
    Artec CD-R/W
    Using this Power Supply Calculator link:
    http://www.jscustompcs.com/power_supply/
    I plug in all my equipment values, but some of this can be a little tricky. For example, since I often run the CPU like an XP 3000, I choose the 3000 as my processor; it’s the same chip run at the faster rate. I also choose the ATI Radeon video card, and I select the RAM wattage for 2 sticks of DDR. I also choose every card I have, like my video capture card, but I also select the boxes for the separate cards that correspond to the functions that my ILSR provides as well (and that I use), like sound, USB, Firewire, NIC, etc.  Although I use the onboard SATA controller, I don’t select the SCSI PCI card, because, in truth, I’ve probably made up for it by selecting all the other corresponding devices, including cards that the motherboard replaces. I check the boxes for the fans and drives I use, and I’m done, right?
    Not yet.
    I just remembered that I plan to upgrade soon, so I go back and change the values to reflect my impending changes. I mean, I want to make sure that I have enough power to begin with so that I don’t have to replace the power supply again, right?
    Ok. Done. I look at the bottom and see that it tells me that I need a 468 watt PSU. So a 480 watt supply will do, right? Wrong.
    Remember that, for efficiency, long-life, and less heat, you want your actual power consumption to fall between 30-70% of the PSU’s rating, so add 30% (minimum) to the 468, and you get 468 + (468*.30)= 608 Watts! Holy Cow!
    However, I’d only need a 608-Watt supply if I was using all the devices at once, and I don’t. But, in truth, with video and audio processing, I often get close when I process, burn, and monitor at the same time. (Hardcore gamers also get close a lot, as they blast the sound and push that video to its limits.) So, let’s take off 10% (maximum) of 608, for a total of 541 Watts.
    I need a 550 Watt supply, but not just ANY 550 watt PSU. I need a supply that can give me enough power on the critical 3.3, 5, and 12V rails combined. I also want a supply from a trusted, name-brand manufacturer, so I start hitting the many online reviews. Here are just two from Tom’s Hardware:
    http://www6.tomshardware.com/howto/20030609/index.html
    http://www6.tomshardware.com/howto/20021021/index.html
    Read these in their entirety. I didn’t post them because they’re pretty links.
    In the end, I chose Antec, because they’ve got the reputation, the recommendation, and because the Antec True550 has better specs than the rest of the 550 Watt competition. I also bought it from a reputable company I found on Pricegrabber.com, for the lowest price I could find, $95.00 shipped to my door. (In truth, I wanted two mini-redundant supplies, like the hospitals and military use, but they were too expensive.)
    The result? Not only are the random reboots, crashing, the BSOD, lockups, etc., gone like magic, but I also now have “peace of mind” in that whatever might happen to my equipment in the future, I know almost for certain that the PSU is NOT the problem. I also bought an UPS, because the East Coast Blackout proved to me that even the Antec True550 isn’t going to provide me any power for emergency shutdown if it doesn’t get its power from somewhere.
    Even if your problem doesn’t lie in the PSU completely, it gives you a GREAT platform for troubleshooting further. If you’re not reasonably certain that the supply is the cause, borrow one, or buy one that you can return once you’ve solved the problem. But, above all else, BUY THE RIGHT SUPPLY before you do anything else! Otherwise, you could be plugging and unplugging components, buying and blowing up expensive memory, and causing even further damage, until you give up or die.
    I mean, I assume you built your own system to enjoy “more bang for your buck,” right? What’s the fun of a random reboot in the middle of Unreal Tournament 2003?
    William Hopkins
    Former Staff Sergeant, USAF
    B.A., B.S., with Honors
    The University of California, San Diego
    [email protected]
    P.S. It should be noted that while Enermax, ThermalTake, Zalman, Fortron, and others make great PSU’s, and I compared and considered them, the Antec still won out overall in my critical evaluation, like it did in so may others’ reviews. You’d probably be ok if you went with another reputable manufacturer as listed above, but pick a supply that gives you at least 230 watts on the 3.3 and 5V lines combined, and still meets the 30% criteria as stated above. Remember, if the manufacturers don’t give you maximum combined specs up front, they’re untrustworthy right off the bat. With power supplies, you definitely end up getting what you pay for. Don’t say nobody warned you.
    P.P.S. Update! After recent developments, it looks like Enermax is the leader, but only the latest line of PSU's.

    Ok, as an electrical engineer...I have to step in here! LOL
    First, these amp rating are for 2 +12 rails. That is why you see a protection of around 15-18A on the +12 rail. That means each Rail is allowed up to 18A lets say for the new Enermax 1.2 version like the one I have.
    Now, Lets say 18A for 12V....well as you know the Abit NF7-S uses the 12V for powering the CPU.
    Lets say you have a Barton like me and you want it stable at around 2.4-2.5Ghz. You will have to put lets say around 2V to the cpu to get it stable at that kinda speed, specially if you have high FSB like I do. So 12V * 18Amps = 216W ....well the converter on the NFS-7 is really bad, its loss on the step down convertion is probably around 25% along with the PSU lost cuz its not running at 25oC (another 15%)....you will actually only get around 100-120W for the CPU.
    Now, if you go into Sandra and see how much a Barton eats up at 2.4Ghz you will see its around 110Watts.
    So, if you wanna push more, dont even think about it! Prime Power test fails and your +12 rail will drop as low as 11.60 Volts.
    Now, lets say you got yourself a AMD 64 bit chip and you wanna overclock it....I bet it will need more than 110Watts.
    So, what im saying is, dont buy nothing less than a 500 Watt PSU!
    You really need around 20-22 A on the main +12 along with really really good cooling on the case and PSU so it is running at a 100%.
    http://forums.amdmb.com/showindex.php?s=&threadid=287828
    i found this quite interesting especially the bit re the power loss turning the 12v into 1.6v or what ever cpu needs

  • TS3694 iPhone 5.....during update to iOS 7 I have lost the power supply (blackout)

    this issue , happen to my iPhone 5.....during update to iOS 7 I have lost the power supply (blackout)
    Sudden screen : USB pointing to iTunes . it shows that it need a restore and update .. after downloading the software
    and extracting .. found Error1 at the point Verify firmware . AGAIN AND
    and this is the log ..
    2014-08-11 15:46:30.611 [4472:1648]: restore library built Feb 12 2014 at 16:27:17
    2014-08-11 15:46:30.611 [4472:1648]: iTunes: iTunes 11.3.1.2
    2014-08-11 15:46:30.611 [4472:1648]: iTunes: Software payload version: 11D257 (option key)
    2014-08-11 15:46:30.611 [4472:1648]: iTunes: Using MobileRestore state machine
    [13:47:25.0555] Changing state from 'Idle' to 'Restoring'
    [13:47:25.0555] device software does not support nonce generation
    [13:47:25.0555] requested restore behavior: Erase
    [13:47:25.0570] requested variant: Erase
    [13:47:25.0570] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 061FEA80 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 061FD2E0 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
    [13:47:26.0569] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
    [13:47:26.0569] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
    [13:47:26.0569] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
    [13:47:26.0569] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 0BA32F38 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
    [13:47:26.0569] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
    [13:47:26.0569] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/Dell/AppData/Local/Temp/Per2046.tmp/amai/debug/tss-re quest.plist
    [13:47:27.0068] amai: tss_submit_job: HttpQueryInfo returned 200
    [13:47:27.0286] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
    [13:47:27.0286] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/Dell/AppData/Local/Temp/Per2046.tmp/amai/debug/tss-re sponse.plist
    [13:47:27.0318] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
    [13:47:27.0333] <DFU Device 0562C260>: production fused device
    [13:47:27.0333] requested restore behavior: Erase
    [13:47:27.0333] device software does not support nonce generation
    [13:47:27.0349] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#93126bb7
    [13:47:27.0349] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#93126bb7
    [13:47:27.0364] <DFU Device 0562C260>: operation 0 progress 2
    [13:47:27.0380] <DFU Device 0562C260>: operation 0 progress 5
    [13:47:27.0396] <DFU Device 0562C260>: operation 0 progress 8
    [13:47:27.0411] <DFU Device 0562C260>: operation 0 progress 10
    [13:47:27.0427] <DFU Device 0562C260>: operation 0 progress 13
    [13:47:27.0442] <DFU Device 0562C260>: operation 0 progress 16
    [13:47:27.0458] <DFU Device 0562C260>: operation 0 progress 18
    [13:47:27.0474] <DFU Device 0562C260>: operation 0 progress 21
    [13:47:27.0489] <DFU Device 0562C260>: operation 0 progress 24
    [13:47:27.0505] <DFU Device 0562C260>: operation 0 progress 26
    [13:47:27.0520] <DFU Device 0562C260>: operation 0 progress 29
    [13:47:27.0536] <DFU Device 0562C260>: operation 0 progress 32
    [13:47:27.0552] <DFU Device 0562C260>: operation 0 progress 34
    [13:47:27.0567] <DFU Device 0562C260>: operation 0 progress 37
    [13:47:27.0583] <DFU Device 0562C260>: operation 0 progress 40
    [13:47:27.0598] <DFU Device 0562C260>: operation 0 progress 42
    [13:47:27.0614] <DFU Device 0562C260>: operation 0 progress 45
    [13:47:27.0630] <DFU Device 0562C260>: operation 0 progress 48
    [13:47:27.0645] <DFU Device 0562C260>: operation 0 progress 50
    [13:47:27.0661] <DFU Device 0562C260>: operation 0 progress 53
    [13:47:27.0676] <DFU Device 0562C260>: operation 0 progress 56
    [13:47:27.0692] <DFU Device 0562C260>: operation 0 progress 59
    [13:47:27.0708] <DFU Device 0562C260>: operation 0 progress 61
    [13:47:27.0723] <DFU Device 0562C260>: operation 0 progress 64
    [13:47:27.0739] <DFU Device 0562C260>: operation 0 progress 67
    [13:47:27.0754] <DFU Device 0562C260>: operation 0 progress 69
    [13:47:27.0770] <DFU Device 0562C260>: operation 0 progress 72
    [13:47:27.0786] <DFU Device 0562C260>: operation 0 progress 75
    [13:47:27.0801] <DFU Device 0562C260>: operation 0 progress 77
    [13:47:27.0817] <DFU Device 0562C260>: operation 0 progress 80
    [13:47:27.0832] <DFU Device 0562C260>: operation 0 progress 83
    [13:47:27.0848] <DFU Device 0562C260>: operation 0 progress 85
    [13:47:27.0864] <DFU Device 0562C260>: operation 0 progress 88
    [13:47:27.0879] <DFU Device 0562C260>: operation 0 progress 91
    [13:47:27.0895] <DFU Device 0562C260>: operation 0 progress 93
    [13:47:27.0910] <DFU Device 0562C260>: operation 0 progress 96
    [13:47:27.0926] <DFU Device 0562C260>: operation 0 progress 99
    [13:47:27.0926] WinDFU::UploadData: EOF, cbRead: 554
    [13:47:27.0942] <DFU Device 0562C260>: operation 0 progress 100
    [13:47:27.0942] WinDFU::UploadData: ZLP
    [13:47:27.0957] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
    [13:47:27.0957] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
    [13:47:27.0957] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
    [13:47:27.0957] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
    [13:47:30.0968] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
    [13:47:30.0968] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
    [13:47:30.0968] WinDFU::ResetDevice: resetting...
    [13:47:31.0046] WinDFU::FinalizeDfuUpdate: success
    [13:47:31.0046] <DFU Device 0562C260>: DFU succeeded
    [13:47:31.0046] Finished DFU Restore Phase: Successful
    [13:47:31.0218] DFU mode device disconnected
    [13:47:31.0218] Device removed when in state Restoring, moving device to transition state
    [13:47:31.0218] Changing state from 'Restoring' to 'Transitioning'
    [13:47:31.0218] Creating timer to monitor transition
    [13:47:32.0175] DFU mode device connected
    [13:47:32.0175] Transitioning device returned, continuing restore.
    [13:47:32.0175] Canceling timer
    [13:47:32.0175] Changing state from 'Transitioning' to 'Restoring'
    [13:47:32.0175] AppleDevice::GetDeviceID: failed for iBoot
    [13:47:32.0175] requested restore behavior: Erase
    [13:47:32.0175] requested variant: Erase
    [13:47:32.0175] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is True
    [13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreLogo" Digest = "<CFData 061FDC70 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreDeviceTree" Digest = "<CFData 061FE378 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreKernelCache" Digest = "<CFData 0B9D5148 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreRamDisk" Digest = "<CFData 0B9D5190 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBEC" Digest = "<CFData 0B9D51D8 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 0B9D5220 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "KernelCache" Digest = "<CFData 0B9D5268 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow1" Digest = "<CFData 0B9D52B0 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow0" Digest = "<CFData 0B9D52F8 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 0B9D5340 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBoot" Digest = "<CFData 0B9D5388 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "DeviceTree" Digest = "<CFData 0B9D53D0 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging1" Digest = "<CFData 0B9D5418 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "AppleLogo" Digest = "<CFData 0B9D5460 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryPlugin" Digest = "<CFData 0B9D54A8 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryFull" Digest = "<CFData 06266350 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging0" Digest = "<CFData 06266398 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RecoveryMode" Digest = "<CFData 062663E0 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 064698C8 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
    [13:47:33.0064] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
    [13:47:33.0064] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/Dell/AppData/Local/Temp/Per2046.tmp/amai/debug/tss-re quest.plist
    [13:47:33.0298] amai: tss_submit_job: HttpQueryInfo returned 200
    [13:47:33.0501] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
    [13:47:33.0501] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/Dell/AppData/Local/Temp/Per2046.tmp/amai/debug/tss-re sponse.plist
    [13:47:33.0501] amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "iBSS" has been previously personalized; skipping it
    [13:47:33.0501] amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "LLB" has been previously personalized; skipping it
    [13:47:33.0517] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
    [13:47:33.0532] <DFU Device 0BA2A9D8>: production fused device
    [13:47:33.0532] requested restore behavior: Erase
    [13:47:33.0532] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:33.0532] AppleDevice::GetDeviceID: failed for iBoot
    [13:47:33.0532] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#ca28221e
    [13:47:33.0532] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#ca28221e
    [13:47:33.0564] <DFU Device 0BA2A9D8>: operation 0 progress 0
    [13:47:33.0579] <DFU Device 0BA2A9D8>: operation 0 progress 1
    [13:47:33.0595] <DFU Device 0BA2A9D8>: operation 0 progress 2
    [13:47:33.0626] <DFU Device 0BA2A9D8>: operation 0 progress 3
    [13:47:33.0642] <DFU Device 0BA2A9D8>: operation 0 progress 4
    [13:47:33.0657] <DFU Device 0BA2A9D8>: operation 0 progress 5
    [13:47:33.0688] <DFU Device 0BA2A9D8>: operation 0 progress 6
    [13:47:33.0704] <DFU Device 0BA2A9D8>: operation 0 progress 7
    [13:47:33.0735] <DFU Device 0BA2A9D8>: operation 0 progress 8
    [13:47:33.0751] <DFU Device 0BA2A9D8>: operation 0 progress 9
    [13:47:33.0766] <DFU Device 0BA2A9D8>: operation 0 progress 10
    [13:47:33.0798] <DFU Device 0BA2A9D8>: operation 0 progress 11
    [13:47:33.0813] <DFU Device 0BA2A9D8>: operation 0 progress 12
    [13:47:33.0844] <DFU Device 0BA2A9D8>: operation 0 progress 13
    [13:47:33.0860] <DFU Device 0BA2A9D8>: operation 0 progress 14
    [13:47:33.0876] <DFU Device 0BA2A9D8>: operation 0 progress 15
    [13:47:33.0907] <DFU Device 0BA2A9D8>: operation 0 progress 16
    [13:47:33.0922] <DFU Device 0BA2A9D8>: operation 0 progress 17
    [13:47:33.0954] <DFU Device 0BA2A9D8>: operation 0 progress 18
    [13:47:33.0969] <DFU Device 0BA2A9D8>: operation 0 progress 19
    [13:47:33.0985] <DFU Device 0BA2A9D8>: operation 0 progress 20
    [13:47:34.0016] <DFU Device 0BA2A9D8>: operation 0 progress 21
    [13:47:34.0032] <DFU Device 0BA2A9D8>: operation 0 progress 22
    [13:47:34.0063] <DFU Device 0BA2A9D8>: operation 0 progress 23
    [13:47:34.0078] <DFU Device 0BA2A9D8>: operation 0 progress 24
    [13:47:34.0094] <DFU Device 0BA2A9D8>: operation 0 progress 25
    [13:47:34.0125] <DFU Device 0BA2A9D8>: operation 0 progress 26
    [13:47:34.0141] <DFU Device 0BA2A9D8>: operation 0 progress 27
    [13:47:34.0172] <DFU Device 0BA2A9D8>: operation 0 progress 28
    [13:47:34.0188] <DFU Device 0BA2A9D8>: operation 0 progress 29
    [13:47:34.0203] <DFU Device 0BA2A9D8>: operation 0 progress 30
    [13:47:34.0234] <DFU Device 0BA2A9D8>: operation 0 progress 31
    [13:47:34.0250] <DFU Device 0BA2A9D8>: operation 0 progress 32
    [13:47:34.0281] <DFU Device 0BA2A9D8>: operation 0 progress 33
    [13:47:34.0297] <DFU Device 0BA2A9D8>: operation 0 progress 34
    [13:47:34.0312] <DFU Device 0BA2A9D8>: operation 0 progress 35
    [13:47:34.0344] <DFU Device 0BA2A9D8>: operation 0 progress 36
    [13:47:34.0359] <DFU Device 0BA2A9D8>: operation 0 progress 37
    [13:47:34.0390] <DFU Device 0BA2A9D8>: operation 0 progress 38
    [13:47:34.0406] <DFU Device 0BA2A9D8>: operation 0 progress 39
    [13:47:34.0422] <DFU Device 0BA2A9D8>: operation 0 progress 40
    [13:47:34.0453] <DFU Device 0BA2A9D8>: operation 0 progress 41
    [13:47:34.0468] <DFU Device 0BA2A9D8>: operation 0 progress 42
    [13:47:34.0500] <DFU Device 0BA2A9D8>: operation 0 progress 43
    [13:47:34.0515] <DFU Device 0BA2A9D8>: operation 0 progress 44
    [13:47:34.0531] <DFU Device 0BA2A9D8>: operation 0 progress 45
    [13:47:34.0562] <DFU Device 0BA2A9D8>: operation 0 progress 46
    [13:47:34.0578] <DFU Device 0BA2A9D8>: operation 0 progress 47
    [13:47:34.0593] <DFU Device 0BA2A9D8>: operation 0 progress 48
    [13:47:34.0624] <DFU Device 0BA2A9D8>: operation 0 progress 49
    [13:47:34.0640] <DFU Device 0BA2A9D8>: operation 0 progress 50
    [13:47:34.0671] <DFU Device 0BA2A9D8>: operation 0 progress 51
    [13:47:34.0687] <DFU Device 0BA2A9D8>: operation 0 progress 52
    [13:47:34.0702] <DFU Device 0BA2A9D8>: operation 0 progress 53
    [13:47:34.0734] <DFU Device 0BA2A9D8>: operation 0 progress 54
    [13:47:34.0749] <DFU Device 0BA2A9D8>: operation 0 progress 55
    [13:47:34.0780] <DFU Device 0BA2A9D8>: operation 0 progress 56
    [13:47:34.0796] <DFU Device 0BA2A9D8>: operation 0 progress 57
    [13:47:34.0812] <DFU Device 0BA2A9D8>: operation 0 progress 58
    [13:47:34.0843] <DFU Device 0BA2A9D8>: operation 0 progress 59
    [13:47:34.0858] <DFU Device 0BA2A9D8>: operation 0 progress 60
    [13:47:34.0890] <DFU Device 0BA2A9D8>: operation 0 progress 61
    [13:47:34.0905] <DFU Device 0BA2A9D8>: operation 0 progress 62
    [13:47:34.0921] <DFU Device 0BA2A9D8>: operation 0 progress 63
    [13:47:34.0952] <DFU Device 0BA2A9D8>: operation 0 progress 64
    [13:47:34.0968] <DFU Device 0BA2A9D8>: operation 0 progress 65
    [13:47:34.0999] <DFU Device 0BA2A9D8>: operation 0 progress 66
    [13:47:35.0014] <DFU Device 0BA2A9D8>: operation 0 progress 67
    [13:47:35.0030] <DFU Device 0BA2A9D8>: operation 0 progress 68
    [13:47:35.0061] <DFU Device 0BA2A9D8>: operation 0 progress 69
    [13:47:35.0077] <DFU Device 0BA2A9D8>: operation 0 progress 70
    [13:47:35.0108] <DFU Device 0BA2A9D8>: operation 0 progress 71
    [13:47:35.0124] <DFU Device 0BA2A9D8>: operation 0 progress 72
    [13:47:35.0139] <DFU Device 0BA2A9D8>: operation 0 progress 73
    [13:47:35.0170] <DFU Device 0BA2A9D8>: operation 0 progress 74
    [13:47:35.0186] <DFU Device 0BA2A9D8>: operation 0 progress 75
    [13:47:35.0217] <DFU Device 0BA2A9D8>: operation 0 progress 76
    [13:47:35.0233] <DFU Device 0BA2A9D8>: operation 0 progress 77
    [13:47:35.0248] <DFU Device 0BA2A9D8>: operation 0 progress 78
    [13:47:35.0280] <DFU Device 0BA2A9D8>: operation 0 progress 79
    [13:47:35.0295] <DFU Device 0BA2A9D8>: operation 0 progress 80
    [13:47:35.0326] <DFU Device 0BA2A9D8>: operation 0 progress 81
    [13:47:35.0342] <DFU Device 0BA2A9D8>: operation 0 progress 82
    [13:47:35.0358] <DFU Device 0BA2A9D8>: operation 0 progress 83
    [13:47:35.0389] <DFU Device 0BA2A9D8>: operation 0 progress 84
    [13:47:35.0404] <DFU Device 0BA2A9D8>: operation 0 progress 85
    [13:47:35.0436] <DFU Device 0BA2A9D8>: operation 0 progress 86
    [13:47:35.0451] <DFU Device 0BA2A9D8>: operation 0 progress 87
    [13:47:35.0467] <DFU Device 0BA2A9D8>: operation 0 progress 88
    [13:47:35.0498] <DFU Device 0BA2A9D8>: operation 0 progress 89
    [13:47:35.0514] <DFU Device 0BA2A9D8>: operation 0 progress 90
    [13:47:35.0529] <DFU Device 0BA2A9D8>: operation 0 progress 91
    [13:47:35.0560] <DFU Device 0BA2A9D8>: operation 0 progress 92
    [13:47:35.0576] <DFU Device 0BA2A9D8>: operation 0 progress 93
    [13:47:35.0607] <DFU Device 0BA2A9D8>: operation 0 progress 94
    [13:47:35.0623] <DFU Device 0BA2A9D8>: operation 0 progress 95
    [13:47:35.0638] <DFU Device 0BA2A9D8>: operation 0 progress 96
    [13:47:35.0670] <DFU Device 0BA2A9D8>: operation 0 progress 97
    [13:47:35.0685] <DFU Device 0BA2A9D8>: operation 0 progress 98
    [13:47:35.0716] <DFU Device 0BA2A9D8>: operation 0 progress 99
    [13:47:35.0716] WinDFU::UploadData: EOF, cbRead: 1116
    [13:47:35.0732] <DFU Device 0BA2A9D8>: operation 0 progress 100
    [13:47:35.0732] WinDFU::UploadData: ZLP
    [13:47:35.0748] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
    [13:47:35.0748] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
    [13:47:35.0748] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
    [13:47:35.0748] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
    [13:47:38.0758] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
    [13:47:38.0758] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
    [13:47:38.0758] WinDFU::ResetDevice: resetting...
    [13:47:38.0836] WinDFU::FinalizeDfuUpdate: success
    [13:47:38.0836] <DFU Device 0BA2A9D8>: DFU succeeded
    [13:47:38.0836] Finished DFU Restore Phase: Successful
    [13:47:39.0039] DFU mode device disconnected
    [13:47:39.0039] Device removed when in state Restoring, moving device to transition state
    [13:47:39.0039] Changing state from 'Restoring' to 'Transitioning'
    [13:47:39.0039] Creating timer to monitor transition
    [13:47:41.0674] Recovery mode device connected
    [13:47:41.0674] Transitioning device returned, continuing restore.
    [13:47:41.0674] Canceling timer
    [13:47:41.0674] Changing state from 'Transitioning' to 'Restoring'
    [13:47:41.0684] requested restore behavior: Erase
    [13:47:41.0684] requested variant: Erase
    [13:47:41.0684] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "iBSS" has been previously personalized; skipping it
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "LLB" has been previously personalized; skipping it
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
    [13:47:42.0528] iBoot build-version = iBoot-1940.10.58
    [13:47:42.0528] iBoot build-style = RELEASE
    [13:47:42.0528] requested restore behavior: Erase
    [13:47:42.0528] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0528] requested restore behavior: Erase
    [13:47:42.0528] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0543] unable to open device_map.txt: No such file or directory
    [13:47:42.0543] found device map entry for 0x00008950 0x00000002. boardConfig=n42ap platform=s5l8950x
    [13:47:42.0543] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [13:47:42.0543] AMDeviceIoControl: GetOverlappedResult failed
    [13:47:42.0543] AMDeviceIoControl: pipe stall
    [13:47:42.0543] USBControlTransfer: error 31, usbd status c0000004
    [13:47:42.0543] command device request for 'getenv radio-error' failed: 2008
    [13:47:42.0543] radio-error not set
    [13:47:42.0543] unable to open device_map.txt: No such file or directory
    [13:47:42.0543] <Recovery Mode Device 0555AEB8>: production fused device
    [13:47:42.0543] requested restore behavior: Erase
    [13:47:42.0543] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0543] requested restore behavior: Erase
    [13:47:42.0543] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0543] interface has 1 endpoints, file pipe = 1
    [13:47:42.0543]
    [13:47:42.0543] <Recovery Mode Device 0555AEB8>: operation 4 progress -1
    [13:47:42.0606] unable to open device_map.txt: No such file or directory
    [13:47:42.0606] found device map entry for 0x00008950 0x00000002. boardConfig=n42ap platform=s5l8950x
    [13:47:42.0606] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [13:47:42.0606] requested restore behavior: Erase
    [13:47:42.0606] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0606] requested restore behavior: Erase
    [13:47:42.0606] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0606] <Recovery Mode Device 0555AEB8>: operation 42 progress -1
    [13:47:42.0606] requested restore behavior: Erase
    [13:47:42.0621] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:43.0651] <Recovery Mode Device 0555AEB8>: operation 5 progress -1
    [13:47:43.0994] unable to open device_map.txt: No such file or directory
    [13:47:43.0994] found device map entry for 0x00008950 0x00000002. boardConfig=n42ap platform=s5l8950x
    [13:47:43.0994] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [13:47:43.0994] AMDeviceIoControl: GetOverlappedResult failed
    [13:47:43.0994] AMDeviceIoControl: pipe stall
    [13:47:43.0994] USBControlTransfer: error 31, usbd status c0000004
    [13:47:43.0994] command device request for 'getenv ramdisk-delay' failed: 2008
    [13:47:45.0616] <Recovery Mode Device 0555AEB8>: operation 6 progress -1
    [13:47:46.0630] <Recovery Mode Device 0555AEB8>: operation 7 progress -1
    [13:47:46.0942] <Recovery Mode Device 0555AEB8>: operation 8 progress -1
    [13:47:46.0958] unable to open device_map.txt: No such file or directory
    [13:47:46.0958] found device map entry for 0x00008950 0x00000002. boardConfig=n42ap platform=s5l8950x
    [13:47:46.0958] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [13:47:46.0958] <Recovery Mode Device 0555AEB8>: operation 9 progress -1
    [13:47:46.0958] <Recovery Mode Device 0555AEB8>: Recovery mode succeeded
    [13:47:46.0958] Finished Recovery Restore Phase: Successful
    [13:47:48.0409] Recovery mode device disconnected
    [13:47:48.0409] Device removed when in state Restoring, moving device to transition state
    [13:47:48.0409] Changing state from 'Restoring' to 'Transitioning'
    [13:47:48.0409] Creating timer to monitor transition
    [13:47:52.0895] RestoreOS mode device connected
    [13:47:52.0895] Transitioning device returned, continuing restore.
    [13:47:52.0905] Canceling timer
    [13:47:52.0905] Changing state from 'Transitioning' to 'Restoring'
    [13:47:52.0905] <Restore Device 05577800>: operation 44 progress -1
    [13:47:52.0905] requested restore behavior: Erase
    [13:47:52.0905] requested variant: Erase
    [13:47:52.0905] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "iBSS" has been previously personalized; skipping it
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "LLB" has been previously personalized; skipping it
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
    [13:47:53.0792] requested restore behavior: Erase
    [13:47:53.0792] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:53.0792] device did not return saved USB log
    [13:47:53.0792] device did not return saved panic log
    [13:47:53.0792] previous restore failed with exit status 0x100
    [13:47:53.0792] connected to service com.apple.mobile.restored
    [13:47:53.0808] using protocol version 13
    [13:47:53.0808] unable to open device_map.txt: No such file or directory
    [13:47:53.0808] board config = n42ap
    [13:47:53.0808] no value returned for BootArgs
    [13:47:53.0824] _copyDeviceProperty() failed for restore bootargs
    [13:47:53.0824] no value returned for MarketingPartNumber
    [13:47:53.0824] _copyDeviceProperty() failed for mpn
    [13:47:53.0824] requested restore behavior: Erase
    [13:47:53.0824] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:53.0839] value query for 'HardwareModel' returned 'N42AP'
    [13:47:53.0839] <Restore Device 05577800>: operation 28 progress -1
    [13:48:10.0360] previous restore failed: re:INF@ 145] created partition 1 as 'Effaceable'
    [13:48:10.0360] [nand_part_core:INF@ 145] created partition 2 as 'NVRAM'
    [13:48:10.0360] [nand_part_core:INF@ 145] created partition 3 as 'Firmware'
    [13:48:10.0360] [nand_part_core:INF@ 145] created partition 4 as 'Filesystem'
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 4
    [13:48:10.0360] [nand_part_core:INF@ 145] created partition 5 as 'System Config'
    [13:48:10.0360] [nand_part_core:INF@ 145] created partition 6 as 'Diagnostic Data'
    [13:48:10.0360] [nand_part_core:INF@ 145] created partition 7 as 'Bad Block Table'
    [13:48:10.0360] com.apple.AppleFSCompressionTypeZlib load succeeded
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 7
    [13:48:10.0360] AppleSamsungSerial: Identified Serial Port on ARM Device=uart1 at 0x32600000(0x82cc6000)
    [13:48:10.0360] L2TP domain init
    [13:48:10.0360] L2TP domain init complete
    [13:48:10.0360] PPTP domain init
    [13:48:10.0360] AppleSwissPPNFTL started with IOFlashStoragePartition provider
    [13:48:10.0360] [NAND] _FindFlashMediaAndKeepout:601 physical nand block offset 1
    [13:48:10.0360] AppleNANDFTL registered[NAND] start:356 this 0x85e41800 PROVIDER=0x85f2a400 flashMedia=0x85f2a400
    [13:48:10.0360] [NAND] WMR_Start:149 Apple PPN NAND Driver, Read/Write
    [13:48:10.0360] [NAND] WMR_Start:174 FIL_Init  [OK]
    [13:48:10.0360] AppleSamsungSerial: Identified Serial Port on ARM Device=uart3 at 0x32800000(0xde3b4000)
    [13:48:10.0360] virtual bool AppleDisplayPipe::start_hardware(IOService *), auto-detect chip
    [13:48:10.0360] [NAND] WMR_Open:371 VFL_Open    [OK]
    [13:48:10.0360] Scaler 0 enableDeviceClock(true,HALF_CLOCK_INDEX) = 0x0
    [13:48:10.0360] Scaler 0 enableDeviceClock(true,FULL_CLOCK_INDEX) = 0x0
    [13:48:10.0360] Scaler 0 enableDevicePower(true,0,HALF_CLOCK_INDEX) = 0x0
    [13:48:10.0360] Scaler 0 enableDeviceClock(false,FULL_CLOCK_INDEX) = 0x0
    [13:48:10.0360] void AppleDisplayPipe::setupVideoDownscalingLimits(): minimum-frequency property not found, using getClockFrequency(0) instead.
    [13:48:10.0360] Scaler 1 enableDeviceClock(true,HALF_CLOCK_INDEX) = 0x0
    [13:48:10.0360] Scaler 1 enableDeviceClock(true,FULL_CLOCK_INDEX) = 0x0
    [13:48:10.0360] Scaler 1 enableDevicePower(true,0,HALF_CLOCK_INDEX) = 0x0
    [13:48:10.0360] Scaler 1 enableDeviceClock(false,FULL_CLOCK_INDEX) = 0x0
    [13:48:10.0360] AppleMultitouchN1SPI: successfully started
    [13:48:10.0360] AppleH4CamIn::start - back camera expected
    [13:48:10.0360] AppleH4CamIn::start - front camera expected
    [13:48:10.0360] AppleH4CamIn::power_off_hardware
    [13:48:10.0360] AppleAP3DSH::probe found device with ID: 0x3f
    [13:48:10.0360] AppleAP3DSH::handleStart _calibrationMatrix [64699 -1892 -370] [-1570 65035 -244] [849 465 63854]
    [13:48:10.0360] AppleAP3DSH::handleStart _calibrationOffsets [518853 -714699 -1661621]
    [13:48:10.0360] AppleAP3DSH::handleStart - No calibration inverse matrix or the data is invalid, Compute locally
    [13:48:10.0360] AppleAP3DSH::handleStart _calibrationInverseMatrix [66427 1929 393] [1599 66087 261] [-895 -507 67257]
    [13:48:10.0360] AppleAP3DSH::handleStart _odr400HzSampleInterval = 2440
    [13:48:10.0360] AppleH4CamIn::setPowerStateGated: 0
    [13:48:10.0360] AppleCS35L19Amp: could not allocate control 395
    [13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableDetect 1
    [13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableType USBHost
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_handleUSBCableConnect cable connected, but don't have device configuration yet
    [13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableDetect 0
    [13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableType Detached
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_handleUSBCableConnect cable connected, but don't have device configuration yet
    [13:48:10.0360] AppleMultitouchN1SPI: detected HBPP. driver will be kept alive
    [13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableDetect 1
    [13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableType USBHost
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_handleUSBCableConnect cable connected, but don't have device configuration yet
    [13:48:10.0360] display-scale = 2
    [13:48:10.0360] display-rotation = 0
    [13:48:10.0360] found applelogo at /usr/share/progressui/[email protected]
    [13:48:10.0360] found display: primary
    [13:48:10.0360] display: 640 x 1136
    [13:48:10.0360] found PTP interface
    [13:48:10.0360] AppleSynopsysOTGDevice - Configuration: PTP
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: PTP
    [13:48:10.0360] AppleSynopsysOTGDevice - Configuration: iPod USB Interface
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: USBAudioControl
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: USBAudioStreaming
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: IapOverUsbHid
    [13:48:10.0360] AppleSynopsysOTGDevice - Configuration: PTP + Apple Mobile Device
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: PTP
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: AppleUSBMux
    [13:48:10.0360] AppleSynopsysOTGDevice - Configuration: PTP + Apple Mobile Device + Apple USB Ethernet
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: PTP
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: AppleUSBMux
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: AppleUSBEthernet
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function USBAudioControl
    [13:48:10.0360] IOAccessoryPortUSB::start
    [13:48:10.0360] virtual bool AppleUSBDeviceMux::start(IOService *) build: Jun 11 2014 20:11:28
    [13:48:10.0360] init_waste
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function AppleUSBMux
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function USBAudioStreaming
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function IapOverUsbHid
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function AppleUSBEthernet
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function PTP
    [13:48:10.0360] AppleSynopsysOTGDevice::startUSBStack Starting usb stack
    [13:48:10.0360] IOReturn AppleUSBDeviceMux::setPropertiesGated(OSObject *) setting debug level to 7
    [13:48:10.0360] AppleBCMWLANCore::init(): IO80211-46 Jun 11 2014 20:10:03
    [13:48:10.0360] [NAND] WMR_Open:420 FTL_Open    [OK]
    [13:48:10.0360] [NAND] _publishServices:642 FTL capabilities: 0x00000001
    [13:48:10.0360] [NAND] _ppnvflGetStruct:3469 Checking borrowed blocks - count: 23 max_count: 23
    [13:48:10.0360] [NAND] _fetchBorrowedList:881 number of borrowed blocks 16
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 0
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 1
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 2
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 3
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 5
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 6
    [13:48:10.0360] 000828.945879 wlan.N[0] AppleBCMWLANCore::start(): Starting with MAC Address: <<<mac address>>>
    [13:48:10.0360] 000828.946182 wlan.N[1] AppleBCMWLANCore::setPowerStateGated():   powerState 1, fStateFlags 0x20, dev 0xc476b000 (this 1, provider 0)
    [13:48:10.0360] 000828.946197 wlan.N[2] AppleBCMWLANCore::setPowerStateGated():  Received power state change before driver has initialized, ignoring
    [13:48:10.0360] IO80211Peer::addPhyStatistics Phy stats started for addr <<<mac address>>>
    [13:48:10.0360] IO80211Peer::addPhyStatistics Tx Completion stats started for addr <<<mac address>>>
    [13:48:10.0360] IO80211PeerManager::initWithInterface cant add monitoring timer
    [13:48:10.0360] Started logging for intf
    [13:48:10.0360] IO80211PeerManager::initWithInterface: inited peer manager
    [13:48:10.0360] IO80211Interface::init peerManager=0x87cb8800
    [13:48:10.0360] start:156
    [13:48:10.0360] start:156
    [13:48:10.0360] AppleARMBacklight::start: No AAP function
    [13:48:10.0360] [effaceable:INIT] found current generation, 90, in group 1
    [13:48:10.0360] [effaceable:INIT] started
    [13:48:10.0360] [effaceable:INIT] started
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49152 62078<-usb->4608
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49153 62078<-usb->4864
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888adec8 established 62078<-lo0->49154 62078<-usb->5120
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade18 established 62078<-lo0->49155 62078<-usb->5376
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888adec8
    [13:48:10.0360] recv(13, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade18
    [13:48:10.0360] recv(14, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade18 established 62078<-lo0->49156 62078<-usb->5632
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49157 62078<-usb->5888
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49158 62078<-usb->6144
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49159 62078<-usb->6400
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49160 62078<-usb->6656
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49161 62078<-usb->6912
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49162 62078<-usb->7168
    [13:48:10.0360] unrecognized key 'BootArgs' in value query
    [13:48:10.0360] failed to handle value query for key 'BootArgs', sending back empty response
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49163 62078<-usb->7424
    [13:48:10.0360] unrecognized key 'MarketingPartNumber' in value query
    [13:48:10.0360] failed to handle value query for key 'MarketingPartNumber', sending back empty response
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49164 62078<-usb->7680
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] client protocol version 13
    [13:48:10.0360] *** UUID 4B2AC217-7071-EC47-8945-EB5E2188BE49 ***
    [13:48:10.0360] Restore options:
    [13:48:10.0360]  UUID                           => <CFString 0x19315c0 [0x2f3ad0]>{contents = "4B2AC217-7071-EC47-8945-EB5E2188BE49"}
    [13:48:10.0360]  MinimumSystemPartition         => <CFNumber 0x1931510 [0x2f3ad0]>{value = +1660, type = kCFNumberSInt64Type}
    [13:48:10.0360]  SystemPartitionSize            => <CFNumber 0x1930f50 [0x2f3ad0]>{value = +1660, type = kCFNumberSInt64Type}
    [13:48:10.0360]  SystemPartitionPadding         => <CFBasicHash 0x192f3c0 [0x2f3ad0]>{type = mutable dict, count = 5,
    [13:48:10.0360] entries =>
    [13:48:10.0360]  2 : <CFString 0x1931540 [0x2f3ad0]>{contents = "128"} = <CFNumber 0x1931570 [0x2f3ad0]>{value = +1280, type = kCFNumberSInt64Type}
    [13:48:10.0360]  3 : <CFString 0x1930f20 [0x2f3ad0]>{contents = "16"} = <CFNumber 0x192f3f0 [0x2f3ad0]>{value = +160, type = kCFNumberSInt64Type}
    [13:48:10.0360]  4 : <CFString 0x192ede0 [0x2f3ad0]>{contents = "32"} = <CFNumber 0x1931250 [0x2f3ad0]>{value = +320, type = kCFNumberSInt64Type}
    [13:48:10.0360]  5 : <CFString 0x1931960 [0x2f3ad0]>{contents = "8"} = <CFNumber 0x192ed50 [0x2f3ad0]>{value = +80, type = kCFNumberSInt64Type}
    [13:48:10.0360]  8 : <CFString 0x1931180 [0x2f3ad0]>{contents = "64"} = <CFNumber 0x1931950 [0x2f3ad0]>{value = +640, type = kCFNumberSInt64Type}
    [13:48:10.0360] }
    [13:48:10.0360]
    [13:48:10.0360] entering load_sep_os
    [13:48:10.0360] device has no sep
    [13:48:10.0360] entering partition_nand_device
    [13:48:10.0360] device supports boot-from-NAND
    [13:48:10.0360] nand device is already partitioned
    [13:48:10.0360] entering wait_for_storage_device
    [13:48:10.0360] Searching for NAND service
    [13:48:10.0360] Found NAND service: IOFlashStoragePartition
    [13:48:10.0360] NAND initialized. Waiting for devnode.
    [13:48:10.0360] entering clear_remap_variable
    [13:48:10.0360] executing /usr/sbin/nvram
    [13:48:10.0360] entering format_effaceable_storage
    [13:48:10.0360] effaceable storage is formatted, clearing it
    [13:48:10.0360] effaceable storaged cleared
    [13:48:10.0360] entering ramrod_probe_media
    [13:48:10.0360] device partitioning scheme is GPT
    [13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
    [13:48:10.0360] executing /sbin/fsck_hfs
    [13:48:10.0360] AppleD1972PMUPowerSource: limiting USB input current to 390 mA (measured 462 mA)
    [13:48:10.0360] ** /dev/rdisk0s1s1
    [13:48:10.0360]    Executing fsck_hfs (version hfs-277.10.5).
    [13:48:10.0360] ** Checking Journaled HFS Plus volume.
    [13:48:10.0360] ** Detected a case-sensitive volume.
    [13:48:10.0360]    The volume name is Sochi11D257.N42OS
    [13:48:10.0360] ** Checking extents overflow file.
    [13:48:10.0360] ** Checking catalog file.
    [13:48:10.0360] ** Checking multi-linked files.
    [13:48:10.0360] ** Checking catalog hierarchy.
    [13:48:10.0360] ** Checking extended attributes file.
    [13:48:10.0360] ** Checking volume bitmap.
    [13:48:10.0360] ** Checking volume information.
    [13:48:10.0360] ** Trimming unused blocks.
    [13:48:10.0360] ** The volume Sochi11D257.N42OS appears to be OK.
    [13:48:10.0360] executing /sbin/mount_hfs
    [13:48:10.0360] mount_hfs: Could not create property for re-key environment check: No such file or directory
    [13:48:10.0360] /dev/disk0s1s1 mounted on /mnt1
    [13:48:10.0360] entering check_for_restore_log
    [13:48:10.0360] found restore log (size = 28347)
    [13:48:10.0360] entering unmount_filesystems
    [13:48:10.0360] error unmounting '/mnt2': Invalid argument
    [13:48:10.0360] entering clean_NAND
    [13:48:10.0360] NAND format complete
    [13:48:10.0360] entering ramrod_probe_media
    [13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0 system= data=
    [13:48:10.0360] entering format_storage_for_LwVM
    [13:48:10.0360] entering ramrod_probe_media
    [13:48:10.0360] device partitioning scheme is GPT
    [13:48:10.0360] unexpected partition 'LwVM' - skipping
    [13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system= data=
    [13:48:10.0360] entering create_filesystem_partitions
    [13:48:10.0360] User specified system partition size, skipping firmware extras size.
    [13:48:10.0360] system partition padding size is: 167772160 bytes
    [13:48:10.0360] unable to open : No such file or directory
    [13:48:10.0360] creating 2 partitions
    [13:48:10.0360] creating encrypted data partition
    [13:48:10.0360] entering ramrod_probe_media
    [13:48:10.0360] device partitioning scheme is GPT
    [13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
    [13:48:10.0360] wipe entire partition: 1 (old = 0 new = 1820)
    [13:48:10.0360] block size for /dev/disk0s1s1: 4096
    [13:48:10.0360] /sbin/newfs_hfs -s -v System -J /dev/disk0s1s1
    [13:48:10.0360] executing /sbin/newfs_hfs -s -v System -J /dev/disk0s1s1
    [13:48:10.0360] Initialized /dev/rdisk0s1s1 as a 2 GB case-sensitive HFS Plus volume with a 8192k journal
    [13:48:10.0360] block size for /dev/disk0s1s2: 4096
    [13:48:10.0360] /sbin/newfs_hfs -s -v Data -J -P /dev/disk0s1s2
    [13:48:10.0360] executing /sbin/newfs_hfs -s -v Data -J -P /dev/disk0s1s2
    [13:48:10.0360] Initialized /dev/rdisk0s1s2 as a 13 GB case-sensitive HFS Plus volume with a 8192k journal
    [13:48:10.0360] entering ramrod_probe_media
    [13:48:10.0360] device partitioning scheme is GPT
    [13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
    [13:48:10.0360] entering mount_filesystems
    [13:48:10.0360] executing /sbin/fsck_hfs
    [13:48:10.0360] ** /dev/rdisk0s1s1
    [13:48:10.0360]    Executing fsck_hfs (version hfs-277.10.5).
    [13:48:10.0360] ** Checking Journaled HFS Plus volume.
    [13:48:10.0360] ** Detected a case-sensitive volume.
    [13:48:10.0360]    The volume name is System
    [13:48:10.0360] ** Checking extents overflow file.
    [13:48:10.0360] ** Checking catalog file.
    [13:48:10.0360] ** Checking multi-linked files.
    [13:48:10.0360] ** Checking catalog hierarchy.
    [13:48:10.0360] ** Checking extended attributes file.
    [13:48:10.0360] ** Checking volume bitmap.
    [13:48:10.0360] ** Checking volume information.
    [13:48:10.0360] ** Trimming unused blocks.
    [13:48:10.0360] ** The volume System appears to be OK.
    [13:48:10.0360] executing /sbin/mount_hfs
    [13:48:10.0360] mount_hfs: Could not create property for re-key environment check: No such file or directory
    [13:48:10.0360] /dev/disk0s1s1 mounted on /mnt1
    [13:48:10.0360] executing /sbin/fsck_hfs
    [13:48:10.0360] ** /dev/rdisk0s1s2
    [13:48:10.0360]    Executing fsck_hfs (version hfs-277.10.5).
    [13:48:10.0360] ** Checking Journaled HFS Plus volume.
    [13:48:10.0360] ** Detected a case-sensitive volume.
    [13:48:10.0360]    The volume name is Data
    [13:48:10.0360] ** Checking extents overflow file.
    [13:48:10.0360] ** Checking catalog file.
    [13:48:10.0360] ** Checking multi-linked files.
    [13:48:10.0360] ** Checking catalog hierarchy.
    [13:48:10.0360] ** Checking extended attributes file.
    [13:48:10.0360] ** Checking volume bitmap.
    [13:48:10.0360] ** Checking volume information.
    [13:48:10.0360] ** Trimming unused blocks.
    [13:48:10.0360] ** The volume Data appears to be OK.
    [13:48:10.0360] executing /sbin/mount_hfs
    [13:48:10.0360] mount_hfs: Could not create property for re-key environment check: No such file or directory
    [13:48:10.0360] /dev/disk0s1s2 mounted on /mnt2
    [13:48:10.0360] entering resize_system_partition_to_options
    [13:48:10.0360] User specified system partition size, skipping firmware extras size.
    [13:48:10.0360] Found SystemPartitionPadding value of 167772160 bytes
    [13:48:10.0360] Erasing system partition prior to resize operation.
    [13:48:10.0360] block size for /dev/disk0s1s1: 4096
    [13:48:10.0360] /sbin/newfs_hfs -s -v System -J /dev/disk0s1s1
    [13:48:10.0360] executing /sbin/newfs_hfs -s -v System -J /dev/disk0s1s1
    [13:48:10.0360] Initialized /dev/rdisk0s1s1 as a 2 GB case-sensitive HFS Plus volume with a 8192k journal
    [13:48:10.0360] executing /sbin/fsck_hfs
    [13:48:10.0360] ** /dev/rdisk0s1s1
    [13:48:10.0360]    Executing fsck_hfs (version hfs-277.10.5).
    [13:48:10.0360] ** Checking Journaled HFS Plus volume.
    [13:48:10.0360] ** Detected a case-sensitive volume.
    [13:48:10.0360]    The volume name is System
    [13:48:10.0360] ** Checking extents overflow file.
    [13:48:10.0360] ** Checking catalog file.
    [13:48:10.0360] ** Checking multi-linked files.
    [13:48:10.0360] ** Checking catalog hierarchy.
    [13:48:10.0360] ** Checking extended attributes file.
    [13:48:10.0360] ** Checking volume bitmap.
    [13:48:10.0360] ** Checking volume information.
    [13:48:10.0360] ** Trimming unused blocks.
    [13:48:10.0360] ** The volume System appears to be OK.
    [13:48:10.0360] executing /sbin/mount_hfs
    [13:48:10.0360] mount_hfs: Could not create property for re-key environment check: No such file or directory
    [13:48:10.0360] /dev/disk0s1s1 mounted on /mnt1
    [13:48:10.0360] Trying to resize system partition to 1908408320 bytes aka 1820 MB
    [13:48:10.0360] entering adjust_partition_preflight
    [13:48:10.0360] partition:0 requiredSize=465920
    [13:48:10.0360] no change in size
    [13:48:10.0360] Successfully resized the system partition
    [13:48:10.0360] entering maximize_data_partition
    [13:48:10.0360] entering adjust_partition_preflight
    [13:48:10.0360] partition:1 requiredSize=<<<<<IMEI>>>>>>6
    [13:48:10.0360] maximizing data partition to 13946060799 bytes
    [13:48:10.0360] entering adjust_partition_preflight
    [13:48:10.0360] partition:1 requiredSize=3404800
    [13:48:10.0360] no change in size
    [13:48:10.0360] Successfully resized data partition to consume free blocks
    [13:48:10.0360] The system partition now has a total HFS+ capacity of 1820 MB
    [13:48:10.0360] entering ramrod_probe_media
    [13:48:10.0360] device partitioning scheme is GPT
    [13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
    [13:48:10.0360] entering unmount_filesystems
    [13:48:10.0360] entering ramrod_ticket_update
    [13:48:10.0360] looking up root ticket hash
    [13:48:10.0360] device tree ticket-hash: <CFData 0x1930040 [0x2f3ad0]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
    [13:48:10.0360] ticket_hash: <<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>
    [13:48:10.0360] received valid ticket (2741 bytes)
    [13:48:10.0360] entering restore_images
    [13:48:10.0360] Successfully marked device node /dev/rdisk0s1s1 as static data
    [13:48:10.0360] executing /usr/sbin/asr -source asr://localhost:12345 -target /dev/disk0s1s1 -erase -noprompt --chunkchecksum --puppetstrings
    [13:48:10.0360] void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 12345 failed: 61
    [13:48:10.0360] void AppleUSBDeviceM

    Hello gamavranje,
    Thanks for using Apple Support Communities.
    The icons you're seeing on your iPhone indicate it is in recovery mode.  Please plug your iPhone into your computer, and restore it with iTunes.
    If you can't update or restore your iOS device
    http://support.apple.com/kb/HT1808
    Use iTunes to restore your iOS device to factory settings
    http://support.apple.com/kb/HT1414
    Take care,
    Alex H.

  • How do I use LabVIEW to control and vary the voltage on my Agilent Power Supply and simultaneously record temp from 1 DMM and voltage from another DMM?

    I am using an Agilent Power Supply  to apply a voltage to a
    thermistor to heat an Al chassis.  I want to use LabVIEW to tell
    the power supply to apply 5V for 10 minutes, then step to 7V for 10
    minutes, etc.  I am completely new to LabVIEW, so any help would be greatly appreciated!
    In addition to that, I want to place a type J thermocouple onto the Al
    surface and use a Keithley 2000 DMM to monitor the temperature (it has
    a built in conversion from V to Temp for type J).  I will also be
    using another Kelthley 2000 DMM to record the output voltage of a new
    uncalibrated thermocouple.  I would like to collect the output
    voltage for this uncalibrated thermocouple and the temperature reading
    from the type J simultaneously.  How should I go about doing this
    in LabVIEW?  I will be using version 6.1.  The power supply
    and DMMs will be connected to a PC using GPIB.
    Again any suggestions would be greatly appreciated- I have no idea
    where to begin on such a project.  I have taught myself how to
    make a basic VI- converting temp in oC to oF, but  that is as far
    as my knowledge goes.

    What you want to do should be fairly straightward and a good way to learn labview. 
    First off, if you haven't already, I would download the drivers for the Keithley and Agilent instruments.  I found the keithley drivers at the link below.  You will need to find the labview drivers for the Agilent PS at their website.  Drivers are the VI's you will use in your program to control the insturments.
    http://sine.ni.com/apps/we/niid_web_display.download_page?p_id_guid=E3B19B3E90B0659CE034080020E74861
    If you open Labview and go to the help menu and click on Labview bookshelf there is alot of information on getting you started coding labview.   This should get you started, if you have anymore questions just ask in this same thread and I am sure you will get all the help you need.
    Brian
    Message Edited by BrianPack on 09-14-2005 05:21 PM
    Message Edited by BrianPack on 09-14-2005 05:21 PM

Maybe you are looking for

  • Struts1.1 + tomcat 5.5 and jndi

    Hi all, I have made a web application using struts 1.1. In this I am using tomcat container security check for log in. For this I have REALM tag in META-INF/context.xml. Now I am thinking to use JNDI for connection pooling, so that I can avoid to put

  • [svn] 3127: Updating asdoc to replace the avmplus call with new set of java files.

    Revision: 3127 Author: [email protected] Date: 2008-09-05 14:16:53 -0700 (Fri, 05 Sep 2008) Log Message: Updating asdoc to replace the avmplus call with new set of java files. Removing all files related to asdochelper. QA: Yes, also please test on no

  • Despair of a switcher (longish)

    Hi all, I wanted to share my experience of pure frustration with Apples hardware and see if there is anyone else with similar experiences. After researching and reading many magazines, web sites and books, and playing with a Powerbook, I decided to t

  • HELP! My images will not drop into a pages!

    Hello, I am writing a large paper with many images.  There are probably around 15-20 images already in the paper, with text, but when I tried to drop in another picture it did not show up.  I could click 'edit' and it would say 'undo drop' but there

  • Where do I report an attempt  to hack my iTunes account via e-mail

    Just got an e-mail pretending to be from iTunes  saying my account has been suspended due to multiple failed attempts to access my account and to reactivate it I must go on line via a link. I thought this a little strange so I visited iTunes on my ph