MDD - anyone rebuilt the power supply?
Looking for any advice, etc. got a MDD from the garbage, great shape, no power & wouldn't boot as a result... no ram or hdd in it either. service tech told me it was a blown psu & were like $150-200 for a used one. so I got a stick of ram found a hard drive @ home & bought a std atx pc psu with an extender cable. rewired the extender cable & plugged it in... let my daughter (she's 4) push the power button & it took off running! installed 10.4 (the mac is for her ;)), seems to be stable & wakes up ok. used the wiring diagram from atxg4.com & since pulled apart the atx psu & put the guts in the MDD psu case. the old psu looks in ok save for the 4 blown capacitors - I've desoldered 3 of them... it's the ACbell model.
so any advice on rebuilding it? parts I need? local stores don't have the caps, they are a very narrow & tall size. coworker told me to check out digikey.com. has anyone else done it & have advice? parts list? what else to check out? thx.
oh, & who sells the replacement fans for the MDD psu?
Message was edited by: kmac1036
Vantec has some fans that work very well and are quieter than the originals:
http://www.vantecusa.com/gl/product/view_detail/116
Get some advice/info within badcaps.net:
http://www.badcaps.net/forum/showthread.php?t=8934
Similar Messages
-
My Mac Pro will not power on. I've replaced the power supply, still will not power on.
Is there anyone with a solution?Try a pram reset:
http://support.apple.com/kb/HT1379 -
G4 MDD won't power on...tried all the basics....is it the power supply?
Put a new battery in, unplugged-replugged, depressed PMU reset...said a couple incantations...nothin....not a spark. How certain can I be that it's the power supply? If it is that, where can I get another one, and are they costly...how hard to install?
Japamac's MDD PSU test page:
http://www.jcsenterprises.com/Japamacs_Page/Blog/D275729F-09DA-4FBB-96B3-BEEEB2C 04619.html
They can be costly. $100 or so used on eBay. Not very difficult to install, though.
An interesting ATX mod using the MDD's PSU case:
http://www.youtube.com/watch?v=wEzbl3eJIro -
My 27" Imac (A1312/EMC2390) keeps shutting down unexpectedly with no warning or "screen of death". So far I reset the SMC, and zapped the PRAM. I even replaced the power supply but the problem continues. My error and system logs seem unhelpful too. Can anyone help me out?
You can get a shutdown like that if the computer gets too hot. Make sure the air intakes on the bottom and the exhaust vent on the top are clean and are not blocked by something in your workspace like papers or the back of the computer being too close to part of the furniture. You need a good six inches (15cm) of clearance between the exhaust slot and other objects or surfaces.
Anti-virus/internet security software, especially the "pay for" kinds, can increase operating temps. So can third-party backup software furnished with many "name-brand" external hard drives.
Fan motors and/or temperature sensors can fail. If you have the original grey disks that shipped with your iMac, find the on that has Apple Hardware Test (AHT) and run it. If you have a failed heat sensor or fan motor, it will detect it with an error code containing "SNS" if it's a bad sensor or "MOT" if its a bad fan motor.
AHT instructions here:
http://support.apple.com/kb/HT1509
Also see if your iMac 27 falls under theis Apple Repair Extension Program:
iMac 1TB Seagate Hard Drive Replacement Program -
This is the full question since I couldn't get it all in the box.
I have some complex questions regarding an iMac, a Time-Machine backup, and iTunes on an iPod.
I live about halfway up an extinct volcano about 12 miles north of San Jose Costa Rica. Some months ago, we had a thunderstorm and as I reached to unplug my computers lightening struck about 50 meters from my house. I had an iMac with a 3-Tb external backup drive, a PC laptop and a laser printer on the same power strip. There was a definite surge and the light brighten and then power was lost for a few minutes.
When power was restored, the PC and the laser printer seemed to work fine but the iMac was cold.
First questions: Is is possible that the power supply was fried and not other essential parts? Would it be worthwhile to replace the power supply? Can I, with limited experience and tools do it or need I take it to a technician? My concern is that if the hard-drive is good, there is personal information on it that I don't want to risk.
Next question: Do I need to replace the hard-drive before taking it for service? How hard is that, can I do it? I have seen videos of the drive replacement on-line.
Those are my iMac questions, now the questions about backup restoration.
If there is a saving grace with this it is that the Time-Machine backup seems fine although I have only accessed the data through Finder. I replaced the iMac with a Macbook Air with significantly less mass storage and I can't just move files to the Macbook. My problem is that I have an iTunes library of some 10,000 songs on the backup and until recently on a 160 Gb iPod which was old and it crashed. I have replaced the iPod but have not tried to restore the iTunes library to it because of my confusion about how to do that. Can anyone tell me how I might do that or give me any insight into the process?
Thanks for any help you can give.Is is possible that the power supply was fried and not other essential parts? Would it be worthwhile to replace the power supply? Can I, with limited experience and tools do it or need I take it to a technician? My concern is that if the hard-drive is good, there is personal information on it that I don't want to risk
Quite possible, but working on iMacs is not easy, & PSU might be prohibitive.
Hopefully the Drive might have info on it, but even pulling that out can be a chore.
If you don't know the model, find the Serial# & use it on one of these sites, but don't post the Serial# here...
http://www.chipmunk.nl/klantenservice/applemodel.html
http://www.appleserialnumberinfo.com/Desktop/index.php
How to find the serial number of your Apple hardware product...
http://support.apple.com/kb/HT1349
I have replaced the iPod but have not tried to restore the iTunes library to it because of my confusion about how to do that. Can anyone tell me how I might do that or give me any insight into the process?
I'd get an external drive & restore the whole works to it, then boot from the External drive. -
How can I replace the power supply IN the time capsule
I have a TimeCapsule that has a bad powersupply. I have opened the timecapsule to confirm this. Has anyone done this before? If so, where did the power supply come from? Cost? I took this to the Apple Igneous bar and they said there is nothing that can be done about it.They said it couldn't even be opened, but simply peeling the rubber bottom off and unscrewing a number of tiny screws and that's it. The 1 TB drive is LOOSE in there. That was a bit of a surprise. I had thought that the issue was the drive itself was bad. I had hoped that if I removed that the AP part would at least work, but after opening it up and firing it up I could hear that the power supply was buzzing thus the conclusion it was the issue.
I am going to put the SATA drive in a reader to see that it is indeed ok. If that checks out, then I know for certain it is the power supply, but I don't know what to use as a sub since the unit needs both 12V and 5V. I'd just as soon find a good supply and use that. Any help would be appreciated.
Thanks,
John A KostelacWhat version is your TC.. A1xxx from the rubber foot?
Power supplies are not available from apple. They do not consider it repairable. It is a sealed consumable.
Power supplies are available from ebay.. simply type time capsule power supply into search.
This is absolutely standard issue that has been ongoing for ages and ages.
See https://sites.google.com/site/lapastenague/a-deconstruction-of-routers-and-modem s/apple-time-capsule-repair
For a multitude of ways to fix it.
The 1 TB drive is LOOSE in there.
No, it is not loose, it has rubber mounts with pins in the bottom base plate. You cannot see the mount points with the base off. This is standard hdd mount for low noise and vibration.
I had thought that the issue was the drive itself was bad.
Drives seldom are the problem. The Gen2 WD black has been less than great though.. and later spinpoint in Gen3 not so good.
Apple Igneous bar -
Does anyone know the power cord part for HP A532 printer? I need a replacement cord. THANKS!
Does anyone know the power cord part for HP A532 printer? I need a replacement cord. THANKS!
Here's the steps to follow if your printer isn't turning on.
If you've gone through all those steps and you still don't have power, there are a lot of places that sell a replacement cord and supply for that printer.
I am an HP employee. -
Hi,
I have the first generation Time Capsule A1254, the power supply inside went south, does anyone know where I can purchase another?
ThanksMight be worth considering a repair of the power supply so you can keep the data on your drive.
I have no association with the link below other than as a customer.
http://www.timecapsulerepair.net/ -
Mac Pro won't start up. What's the best way to check the power supply?
Hello. I'm having a severe problem with my 2007 Mac Pro. The symptoms are very easy to describe. The computer apparently shut itself off overnight, and when I press the power button to turn it on, absolutely nothing happens. No lights, no chime, no signs of any power whatsoever in the computer. I have never had major problems with the computer before. (Although I had recently noticed some minor skipping problems with streaming videos and Firefox had started hanging occasionally.)
So far, I have checked the power cable and the power outlet. I have also reset the SMC (holding in the Power button for 5 seconds with the unit unplugged). I am unable to see any light in the diagnostic LEDs (including LED 1) when I press the DIAG_LED button on the logic board.
While I welcome other suggestions, all I can figure is that this is either a power supply problem or a major logic board failure, but I don't know which. I have a multimeter and would like to test very directly if the power supply is the problem, because they are very expensive and obviously I do not want to order a replacement supply if it would not fix the computer. Does anyone know what the best way to test the supply directly is? What pins on what cable should I test, and what voltage should I look for?
Also: No the computer is not under any warranty. If at all possible, I would like to fix this myself. Thanks for any help you can give.Well, I may have found the answer to my question as to why replacing the fuse dows not seem to be encouraged. I cut out the failed fuse (fast fuse, ceramic, 16 Amp 250V), and replaced it with another that was as close to it in spec as I could find (15 A instead of 16). Then I put the supply back in the case.
When I tried to plug it in, I got an immediate spark, followed by an acrid smell from the power supply. Later inspection revealed that the new fuse blew, as did another component nearby (not sure what it was) where I could see blackening and the smell was concentrated. At this point, I would consider myself lucky if the power supply didn't take anything else on the computer out with it.
Lesson learned; will try a new power supply and go from there. -
I hear sometimes an anoying buzz noise from the power supply. It doesn't always starts when I boot the computer but after 10-20 minutes most of times it starts. I thought that maybe its a low power from my ups wich is 500VA. I conncecet the mac's AC cable directly to an ac outlet and still the noise exists. Has anyone passed any simiral problem.
Thanks in advance
PS: Where can I find the Watts that the power supply needs. No specs in this site or in the manual.?There are dozens of threads on "UPS"
My UPS with Mac Pro, ACD 23" along with modem and router hits 400W and I have APC RS1500VS (which I put in my sig for a reason) and once it gets to 50%+
If all you have is stock RAM and hard drive... get your system off its starvation diet.
I'm just telling you what I know and read and that you can confirm for yourself. Am I sure?
Use your small UPS for home entertainment equipment, monitor and modem and such, not for Mac Pro. -
Is it possible to have HP upgrade the power supply when purchasing a desktop? Base:300W Desired:400W
It isn't in the configuration options to upgrade the power supply. I am considering strongly an HPE500z with an upgrade to 1GB graphics card (from 512MB) and perhaps an upgrade to the processor. I do not know if 300 W should be able to handle the upgrades (it probably will be fine), but with potential future upgrades I see no reason to not go a little bigger on the power supply.
Can anyone help?nDefined,
It should take less than 30 minutes. I installed a Corsair HX 650 into a HPE cabinet.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT -
Why is the power supply for the Mini so big?e
Can anyone explain why the power supply / adapter for the mac mini is so big compared to the power adapters for the macbook? The processor and hard drive for the mini is the same as those for the macbook, so why is the power brick so much bigger? Just curious.
While I doubt anyone who knows for sure will be prepared to pop up and answer, I suspect the reason is two-fold: firstly that the supply is engineered for constant use, 24/7, where laptop supplies are not, and thus it is larger because the components are more rugged and over-specced, and secondly for lowest cost, since it is cheaper to engineer a larger product of this kind than a smaller one, due to the premium cost of the smallest narrow-tolerance components.
-
Is the Power Supply Important?
I see a number of other people are having dual-channel memory issues like me. I'm wondering how important the power supply is. I'm using the PSU that came with a PC case. It's rated at 300W (3.3v/20A, 5v/30A, 12v/10A, -12v/.8A). Using a bench calibrated Fluke 83 I see that the 5v rail is at 5.14v/stable and the 12v rail bounces between 12.19 to 12.21 vdc. Don't know about the 3.3v or the -12v. Maybe I need to check them too? Has anyone had a stability problem that was resolved by getting a better power supply?
those are very unimpressive numbers,10 a at 12v especially
get a better psu
Is the Power Supply Important?
you could say the same re the engine in a car
you would get the same answer from a sensible person -
Hi all - My mac pro 1,1 has an enigmatic problem. It's quad-core, 3Ghz, running OS X 10.7.5. The problem began some months back, when running HD video conferences, HD streaming videos and some other graphics-moderate (I won't say intense) uses, such as slide shows in Just Looking. My machine has an ATY, RadeonX1900 card and 2 monitors - both Apple displays, one being 30 inch 2560x1600, the other being 24 inch 1920x1200.
When I start those types of graphics-moderate apps, after about 5 minutes, something would crash (the monitors making a noise as it did) and the displays would both go black. The power did not appear to be fully cut off from the monitors. I think that the underlying applications, however, did not crash. So, I could still hear and speak to people during video conferences, and I could hear the sound tracks of videos.
Attempts to restart the computer and get the monitors back did not immediately work to undo the problem, if done straight away. The only way to correct the problem (so as to have the monitors work) was to wait for a few minutes and then restart.
After a lot of puzzled looking at console logs (and I confess that I am not an expert), I ran into a blank.
But, because of the timing of the crashes (after ~5minutes use) and restarts (after some minutes wait), I reasoned that the problem might be temperature related.
Once on that path of thought, I found this article:
http://worldtv.com/blog/guides_tutorials/fixing_an_overheating_mac_pro_no_expens e_required.php
I installed both Temperature Monitor and SMCFanControl. And I experimented, and got interesting results:
Now to the puzzling bit: SMCFanControl shows that the speed of the Power Supply Fan doesn't vary much, even if I use SMCFanControl to ramp fan speeds right up. All of the other fans react to SMCFanControl, going up to and above 2500rpm when commanded. But the Power Supply Fan does not. Having watched it for a few days now, the Power Supply Fan, according to AFCFanControl, never varies outside of a range from about 600-640 rpm, regardless of what I do with AFCFanControl.
Also (and not surprisingly), whenever the graphics-moderate apps run, when I ramp all the fan speeds up using SMCFanControl, Temperature Monitor shows that the all of the temperatures within the machine plummet, except in the power supply locations. Power Supply Location 2 is the worst affected. Because the Power Supply Fan does not react as the other fans do, the "crashes" still occur.
I could post some screen shots of the read outs of SMCFanControl and Temperature Monitor, although I think I have covered the key points in this post.
It seems that the Power Supply Fan is still working, but does not respond to increased loads.
Instinctively, I'm worried that if that's right, it might be a hard problem to fix. Any suggestions? Help! I would really appreciate them!
Cheers
PThanks for your response Grant. I had already read about, and I think excluded, dust in graphics card/fan/assembly as a cause. The entire inside of the computer, including the graphics card/fan/assembly, is as clean as a whistle. It looks clean. I've cleaned the dust out every now and then (including a few days ago). Also, my undersanding (derived from the article, linked in my first post) is that I might expect to see high temperatures in the Northbridge and memory module B if the graphics card was overheating. According to Temperature Monitor, however, locations do not increase in temperature when I run the relevant apps. Finally, the graphics card/assembly does not feel too hot to touch.
It is strange that SMCFanControl lists the Power Supply Fan as being software controllable, if that fan is not. Still, your comments are consistent with my observations, as the fan simply does not respond to software control.
There are two upsides: First, I've something of a work-around. I've worked out what temperature must be achieved in Power Supply Location 2 for a crash to occur, and I can watch that location in Temperature Monitor, terminating the process before that treshold is reached. Of course, that's not ideal. Second, ramping all the other fans up does significantly delay the onset of the problem, and makes recovery time much quicker.
Is there any donwside to peridically ramping up the other fans when running the relevant apps? Given that it causes all of the other locations to cool significantly, could this lessesn the life expecancy of the mahcine? (I don't want to run the fans up all the time - that's like sitting next to a jet ready for take off!)
Also, a correction to my first post: Yesterday, with all the other fans running on full and running an HD streaming video, the Power Supply Fan did, eventually, slowly, come up to ~740rpm, which is much higher than the ~640rpm maximum I had previously seen, and this may have aided delaying the onset of the problem.
I'm not sure where this leaves me? The problem might now be able managed. Well, sort-of. But it's not eliminated. -
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 AppleUSBDeviceMHello 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.
Maybe you are looking for
-
PLEASE HELP ME.
-
Where can I get driver for network scanning on my Laserjet Multifunction M1120n for Windows 7?
Where can I get driver for network scanning on my Laserjet Multifunction M1120n for Windows 7 64bit? It must be the Windows 7 driver of Scanto.msi. Thank you for your support. This question was solved. View Solution.
-
How can I store and view a pdf file ?
I have an iphone 3GS 32Gb and want to store a pdf file on my phone so that I can view it later. Email is the only way I have been able to view my pdf file, but I dont really want to do it this way. On previous phones I could save a file on the phones
-
Husband's iphone won't ring. need help please. thanks
My husband's iPhone 4 won't ring. It will vibrate but ringing has stopped. Can't figure out how to change back to ringing. Thanks for any help.
-
Error in creating task list /TMWFLOW/PROJCTC
Hello, We are implementing charm in release 7.1. We are getting an error some times that says that user was not able to create a task list for an urgent correction SMHF. The error message says: There is no active task list in the associated project