Restoring complete flash archive

Recently I made a flash archive of my system solaris 8 to tape using the command:
FLARCREATE -N SUN-EC1.FLAR -C -S -R / -T /DEV/RMT/0
I have 2 disks of 32 GB and I will replace them for 2 of 72 GB.
Which command should I use to restore my system completely after the change of the disks?
The image was taken from a live system ; Can I have some problem when restoring the copy?

To restore the backup made with flarcreate you need to boot your upgraded server with the Installation disk CD1
I used the form on the <OK> prompt:
boot cdrom - w
Then the installation should start whare you have to define slices and network parameters and then you should be offered to install OS from standard location (cd) or flash archive. There you need to select flash_archive (I think it is Cntr-4 of F4) which should guide you to select source (local tape) and you just have to confirm and sit down and watch.
Good luck!
Zika from RSA

Similar Messages

Security for flash archive restore with NFS

When Flash archive is restored by using NFS, user id and password is not required though they are asked in case of FTP used.
If NFS client host name is registered in NFS server, anyone can restore the backup file if only they know that host name with NFS server name and exported directory.
I found the kerberos selection during resotre process set up on Interactive install, which is on the following screen.
--- Configure Kerberos Security ------------------------------------------
Enter the information required to configuration your system as a Kerberos Cient.
Your Network Administrator ca provide this inforamtion.
Defalult Realm :
Administration Server :
. First KDC:
Additional KDC:
Additional KDC:
Additional KDC:
I did not yet establish the kerberos server, but if any one already tried this function, could you please let me know if this can protect NFS server access by using user id and password.

One option is to secure the OBP with a password.
At the OK prompt, set the security-mode to "command" and then set a password. Careful not to loose this password. With this set the only option is to "boot" without supplying the firmware password.
Commands:
# halt
ok setenv security-mode = command
ok setent security-password <enterpasswd>
ok reset-all

Are nfs mounts allowed in vfstab after a flash archive restore?

I am restoring a server using a flash archive. The vfstab on the original server contains an entry for an nfs mount. It looks like during the push of the archive to the new server, the vfstab gets saved to vfstab.orig and the nfs mount is removed from vfstab. So I added a finish script to add the nfs mount back to vfstab and now the server gets hung during S73nfs.client during reboot.
Are nfs mounts not allowed in vfstab after a flash archive restore?

One option is to secure the OBP with a password.
At the OK prompt, set the security-mode to "command" and then set a password. Careful not to loose this password. With this set the only option is to "boot" without supplying the firmware password.
Commands:
# halt
ok setenv security-mode = command
ok setent security-password <enterpasswd>
ok reset-all

Flash Archive restored files

Hi,
We are moving servers (T2000' / Solaris10) to a new Datacentre and using swing kit to reduce the downtime on the production databases.
We plan to take a Flash Archive of the OS and restore the swing kit (exactly the same config) from the Flash Archive, we also plan to take ufsdumps.
Would anyone know the exact files which are not restored as part of the Flash Archive please?? I know Flash Archive runs a sys-unconfig so hosts, defaultrouter, defaultdomain and the Network will not be restored but are there any other files which will not be restored???
Thanks in advance.

LDAP may or may not work. I have three T2000s that I need to update and I've flar'ed them and restored them to a matching T2000 just so there won't be any surprises when I do the real boxes. Sometimes LDAP works, sometimes it doesn't.

Flash archive to tape

I would like to make flash archive to tape device.
But the following 'flarcreate' command failed.
' flarcreate -n archivetry1 -H -c -t /dev/rmt/0'
where archivetry1 is just the name of archive
/dev/rmt/0 is tape device just attached.
Solaris version is 8
Is there someone who knows the correct format of this command.

Further trial with another command like 'mt -f /dev/rmt/0 erase' reported media error.
So after replacing tape media, 'flarcreate -n archive1 -N -t /dev/rmt/0' was successfully completed.
However, restore operation failed with dump as of now.
Is this command format of flash archive creation correct?

WARNING: Flash Archive IDs do not match (possible corrupt archive)

I'm running into problems when trying to use a newly patched Solaris 10 system's flash image via my Solaris 9 Jumpstart server. I'm able to use other flash's (Solaris 9 and 10) fine, but when I use this flash I get:
Extracted 823.00 MB ( 99% of 824.99 MB archive)
Extracted 824.00 MB ( 99% of 824.99 MB archive)
Extracted 824.99 MB (100% of 824.99 MB archive)
WARNING: Flash Archive IDs do not match (possible corrupt archive)
Extraction complete
Postdeployment processing
No local customization defined
cp: cannot create /a/etc/init.d/flash_reboot_processing: No such file or directory
Can not set reboot customization scripts
ERROR: Error while processing system postdeployment script
ERROR: Postdeployment processing failure
ERROR: Flash installation failed
Solaris installation program exited.
I've use the same script I've always used twice to create the flash to no avail.
Any ideas?

Hi,
I have the same problem, How did yoy fix this. /usr at this stage is a ram disk i assume. Can you increase this.
Cheers
Paul

Creating Standby server ---- Flash archive/Alternate Boot Environment.

Dear All,
I want to patch upgrade the Centralized login server which holds more than 200 users. To avoid this production outage during the downtime of upgradation, we are planning to create all the logins and application in the alternate server manually. But i feel (lazy) hesitate to create logins and copy the applications in the statndby server. Since "chpasswd" is not in solaris, i can't copy the /etc/passwd & shadow file to standby server.
So i have the plan to achieve this by
i) creating flash archive of existing login server
ii) Creating Alternate boot environment in the standby server and flash restore the archive in it.
Whether the above mentioned plan is achievable, how to create the entire flash archive of solaris os?? and how to deploy it in the alternate boot environment.?
Regards,
Siva

Done, I've given the same path in Standby Database [datafiles, controlfiles] as it has been given in the Primary Database.
MoreOver, I m manually switching logfiles at primary database [alter system switch logfile] they are copied and applied sucessfully at standby database. But the archived files that I have copied with cold backup are not applied yet. Infact they are not retrieved executing the below query.
select name, applied from v$archived_log;
How can I apply those archived logs? [archives that copied with cold backup]
Regards.

How can I export an Flash archive to Powerpoint or into a Visual basic form

How can I export an Flash archive(Flash cs4 profesional) with animation to Powerpoint or into a Visual basic form ?,

How can I export an Flash archive(Flash cs4 profesional) with animation to Powerpoint or into a Visual basic form ?,

I restored my iPhone 5 to IOS 7.1 on computer and tried to restore from icloud back up. It says "restore completed" but Apple logo keeps popping up every 5 seconds. It restored only contacts and sms. I can access the phone but have to stop if logo pops

I restored my iPhone 5 to IOS 7.1 on computer and tried to restore from icloud back up. It says "restore completed" but Apple logo keeps popping up every 5 seconds. It restored only contacts and sms. I can access the phone but have to stop if logo pops

Hello khanhlinh98,
I would recommend performing the following steps in order to stabilize your iPhone.
Will not turn on, will not turn on unless connected to power, or unexpected power off
Verify that the Sleep/Wake button functions. If it does not function, inspect it for signs of damage. If the button is damaged or is not functioning when pressed, seek service.
Check if a Liquid Contact Indicator (LCI) is activated or there are signs of corrosion. Learn about LCIsand corrosion.
Connect the iPhone to the iPhone's USB power adapter and let it charge for at least ten minutes.
After at least 30 minutes, if:
The home screen appears: The iPhone should be working. Update to the latest version of iOS if necessary. Continue charging it until it is completely charged and you see the battery icon in the upper-right corner of the screen. Then unplug the phone from power. If it immediately turns off, seek service.
The low-battery image appears, even after the phone has charged for at least 20 minutes: See "iPhone displays the low-battery image and is unresponsive" symptom in this article.
Something other than the Home screen or Low Battery image appears, continue with this article for further troubleshooting steps.
If the iPhone did not turn on, reset it while connected to the iPhone USB power adapter.
If the display turns on, go to step 4.
If the display remains black, go to next step.
Connect the iPhone to a computer and open iTunes. If iTunes recognizes the iPhone and indicates that it is in recovery mode, attempt to restore the iPhone. If the iPhone doesn't appear in iTunes or if you have difficulties in restoring the iPhone, see this article for further assistance.
If restoring the iPhone resolved the issue, go to step 4. If restoring the iPhone did not solve the issue, seek service.
My issue is still not resolved. What do I do next?
Contact Apple Support.
iPhone: Hardware troubleshooting
http://support.apple.com/kb/TS2802
Cheers,
Allen

Flash archive to zone?

Is there a way to take a flar from a solaris 10 physical machine and install it into a zone of another machine (also solaris 10)? I see the migration software for solaris 8 to a container, but not solaris 10 to container.

redhat_123 wrote:
Even if we have a whole root zone, extracting a flash archive wouldnt help. We really need to wait for Sun to provide a native P2V for Sol10. There would be work arounds, but not going to be supported by Sun.I'm not sure there's value in P2V for Solaris 10. IMO that would be handled just by building the zone and migrating what you've got to the zone.
I'm sure I'm missing something here... the question is what.
Best,

Solaris 8 container install problem using Ultra 60 flash archive

Hi
I have an M4000 configured with a Solaris 8 container.
I am using a flash archive from an Ultra 60.
Below is the problem when I install.
# zoneadm -z f714clone install -u -a /var/flar/fid714_20090515.flar
Log File: /var/tmp/f714clone.install.26921.log
Source: /var/flar/fid714_20090515.flar
Installing: This may take several minutes...
Postprocessing: This may take several minutes...
WARNING: zone did not finish booting.
Last entry in the logfile is...
[Fri May 15 12:21:22 BST 2009] Postprocess: Performing zone sys-unconfig
It just sits at the WARNING doing nothing.
I connected to the container console using "zlogin -C f714clone" but this just gives me a blank screen with no output and unable to do anything.
I used a different archive from a V120 and had no problems.
Is there something I need to configure for a Ultra 60.
Thanks in advance.
Steve.

I got this to work. It seems, for whatever reason, that it doesn't like the '-u' flag for an Ultra 60. I installed using '-p' instead and it was fine, it even came up with the new IP I had assinged.
zoneadm -z QeSun01b install -p -a qesun01.flar

Flash archive on solaris 8/9

Hello,
I have a nfs server containing flar image but this box is not a boot server.
I need to boot from CDROM and recover OS from a flash archive server (NFS). I have all the files in place too.
what command do i need to run from the ok prompt of the corrupt server so that it boot initially for CD Rom and installs from the flash archive?
ok> boot cdrom - install net=nfs_servername:/path_to_archive
or
ok> boot cdrom - install nfs=nfs_servername:/path_to_archive
please help i have have been searching a lot bot with no luck please help.

I have seen
boot cdrom - install tape=/dev/rmt/0n
i have seen this in man of boot
ok boot cdrom -F wanboot - install
and saw this on some fourm
boot cdrom -o prompt -F wanboot -V - install
but not sure how do i use them though.
and also dont know where i can specify the nfs server and archive path at boot prompt.
Any ideas?

Solaris 10 physical to Solaris 10 zones via flash archive

Hi,
I need to migrate E25K domains (all Solaris 10) to zones on an M9000. The solution architect has suggested zones on the M9000 made from flash archives of the source E25K domains for speed & simplicity (read : avoid a rebuild of the application environment and all that entails). But as best I can tell, you can only use flash archives to provision zones as part of the branded zones architecture and it does not include SOlaris 10.
As best I can tell, this is not possible - at least not in a supported way; I have seen some blogs that have hacks for making a zone from a solaris 10 flash archive but I can't do that sort of thing here.
Is my view correct? If it is, is there any timeframe for Solaris 10 P2V?
I am aware that OpenSolaris now supports Solaris (TM) as a branded zone but that will not help me here.
TIA
Steve

You log an RFE the same way you log a bug with Sun/Oracle, by calling the Support Center. For that, you would need a support contract or server serial number. If you have a relationship with a Sun/Oracle sales team, you may also be able to speak with them directly and ask if they could open the call on your behalf. The call that you open is investigated and may be determined by Sun/Oracle to be an RFE. I think I mentioned earlier that the Solari10 P2V may already have been requested by various customers, but it is always good to log the call and have yourself added as an interested party.

Solaris 9 U7 (2004/09) MultiLayered Flash Archive issue + solution ?

In Solaris 9 Update 7 (2004/09) the multilayered flash archive installation feature is broken.
I think that this is a known issue:
4945516 Failure of multi-layered archive with Solaris 9 4/03 on Postdeployment process
I manage to flash my archives by changing the following statement found at line 24 of the file
../Solaris_9/Tools/Boot/usr/lib/flash/postdeployment_processing
from
if [ ! -L $FLASH_ROOT/etc/rc2.d/S98flash_reboot ] ; then
to
if [ -L $FLASH_ROOT/etc/rc2.d/S98flash_reboot ] ; then
This issue is addressed in the patch 113434-22
113434-22/SUNWinst/reloc/usr/lib/flash/postdeployment_processing
But the if statement is not the good one.
Is this correct ?
Coco D.

Ideas.. Hmm, none which seems that correct, but you could try some things.
If it gets the wrong IP that could explain why it fails to copy the sysidcfg file.
First you could try and do a snoop on the ethernet address;
snoop ether 0:3:ba:14:c6:cd
(you could also try the -v flag to increase the verbosity).
The things you should look for are arp/rarp requests, the jumpstart client will use arp/rarp to determine its IP address, snoop will show you which server that responds, and what address it gets, futher more its a good idea to verify that the response to the bootparams requests comes from the correct server.
Of course there might be other oddnesses as well.
Was the data you provided extracts? If it was you should check the /etc/ethers and /etc/bootparams for duplicates entries, so there are no other occourances of the clients ehternet address in /etc/ethers, and no bogus entries starting with * or the same hostname in /etc/bootparams.
If you added the client manually you could always try and use the Tools/rm_install_client and Tools/add_install_client scripts to add it again, these script sometimes detect problems with the configuration.
Lastly you didn't show us your /etc/nsswitch.conf file, but i assume that it has "files" first for the ethers, hosts and bootparams entries?
Good luck
//Magnus

Restore completed status 4014 iphone 5s

i try to restore my iphone 5s form 3 PC and change 2 Cabels
every time give me a 4014 and the finall time give me
and this is a log for it status:2005
2014-04-14 06:40:05.147 [15724:4538]: restore library built Feb 12 2014 at 16:27:17
2014-04-14 06:40:05.147 [15724:4538]: iTunes: iTunes 11.1.5.5
2014-04-14 06:40:05.148 [15724:4538]: iTunes: Software payload version: 11D167
2014-04-14 06:40:05.148 [15724:4538]: iTunes: Using MobileRestore state machine
[04:40:49.0144] Changing state from 'Idle' to 'Restoring'
[04:40:49.0147] AppleDevice::GetDeviceID: failed for iBoot
[04:40:49.0148] AppleDevice::GetDeviceID: failed for iBoot
[04:40:49.0151] requested restore behavior: Erase
[04:40:49.0153] requested variant: Erase
[04:40:49.0186] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[04:40:49.0680] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is True
[04:40:49.0684] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreLogo" Digest = "<CFData 123A06E8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0686] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreDeviceTree" Digest = "<CFData 123A5D88 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0688] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreKernelCache" Digest = "<CFData 1239F068 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0692] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreRamDisk" Digest = "<CFData 123A3160 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0693] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBEC" Digest = "<CFData 1239F410 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0695] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 1239FC80 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0697] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "KernelCache" Digest = "<CFData 123A18E8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0699] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "Diags" not part of manifest, skipping
[04:40:49.0701] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "CFELoader" not part of manifest, skipping
[04:40:49.0702] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RBM" not part of manifest, skipping
[04:40:49.0704] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PHLEET" not part of manifest, skipping
[04:40:49.0705] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PERTOS" not part of manifest, skipping
[04:40:49.0706] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PEHammer" not part of manifest, skipping
[04:40:49.0709] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow1" Digest = "<CFData 123A0418 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0712] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow0" Digest = "<CFData 123A60E8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0714] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 123A02B0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0715] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBoot" Digest = "<CFData 123A0B68 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0717] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "DeviceTree" Digest = "<CFData 123A06A0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0719] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "SEP" Digest = "<CFData 123A26F8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0721] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging1" Digest = "<CFData 1239F6E0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0723] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreSEP" Digest = "<CFData 123A4630 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0724] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "AppleLogo" Digest = "<CFData 123A4F30 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0726] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryPlugin" Digest = "<CFData 123A0B20 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0728] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryFull" Digest = "<CFData 123A35E0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0730] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging0" Digest = "<CFData 123A26B0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0731] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RecoveryMode" Digest = "<CFData 123A2308 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[04:40:49.0733] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 11F7B4D8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:40:49.0735] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
[04:40:49.0736] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/ADMINI~1/AppData/Local/Temp/Per4976.tmp/amai/debug/ts s-request.plist
[04:40:50.0792] amai: tss_submit_job: HttpQueryInfo returned 200
[04:40:51.0005] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
[04:40:51.0007] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/ADMINI~1/AppData/Local/Temp/Per4976.tmp/amai/debug/ts s-response.plist
[04:40:51.0541] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
[04:40:51.0542] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "CFELoader"
[04:40:51.0544] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "RBM"
[04:40:51.0546] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PHLEET"
[04:40:51.0547] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PERTOS"
[04:40:51.0548] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PEHammer"
[04:40:51.0919] <DFU Device 05FDA3F0>: production fused device
[04:40:51.0920] requested restore behavior: Erase
[04:40:51.0924] AppleDevice::GetDeviceID: failed for iBoot
[04:40:51.0925] AppleDevice::GetDeviceID: failed for iBoot
[04:40:51.0936] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#64c33543
[04:40:51.0937] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#64c33543
[04:40:51.0939] <DFU Device 05FDA3F0>: operation 0 progress 1
[04:40:51.0940] <DFU Device 05FDA3F0>: operation 0 progress 2
[04:40:51.0942] <DFU Device 05FDA3F0>: operation 0 progress 4
[04:40:51.0944] <DFU Device 05FDA3F0>: operation 0 progress 5
[04:40:51.0946] <DFU Device 05FDA3F0>: operation 0 progress 7
[04:40:51.0948] <DFU Device 05FDA3F0>: operation 0 progress 8
[04:40:51.0950] <DFU Device 05FDA3F0>: operation 0 progress 9
[04:40:51.0952] <DFU Device 05FDA3F0>: operation 0 progress 11
[04:40:51.0954] <DFU Device 05FDA3F0>: operation 0 progress 12
[04:40:51.0956] <DFU Device 05FDA3F0>: operation 0 progress 14
[04:40:51.0958] <DFU Device 05FDA3F0>: operation 0 progress 15
[04:40:51.0960] <DFU Device 05FDA3F0>: operation 0 progress 17
[04:40:51.0962] <DFU Device 05FDA3F0>: operation 0 progress 18
[04:40:51.0964] <DFU Device 05FDA3F0>: operation 0 progress 19
[04:40:51.0966] <DFU Device 05FDA3F0>: operation 0 progress 21
[04:40:51.0968] <DFU Device 05FDA3F0>: operation 0 progress 22
[04:40:51.0970] <DFU Device 05FDA3F0>: operation 0 progress 24
[04:40:51.0972] <DFU Device 05FDA3F0>: operation 0 progress 25
[04:40:51.0974] <DFU Device 05FDA3F0>: operation 0 progress 26
[04:40:51.0976] <DFU Device 05FDA3F0>: operation 0 progress 28
[04:40:51.0978] <DFU Device 05FDA3F0>: operation 0 progress 29
[04:40:51.0980] <DFU Device 05FDA3F0>: operation 0 progress 31
[04:40:51.0983] <DFU Device 05FDA3F0>: operation 0 progress 32
[04:40:51.0986] <DFU Device 05FDA3F0>: operation 0 progress 34
[04:40:51.0989] <DFU Device 05FDA3F0>: operation 0 progress 35
[04:40:51.0991] <DFU Device 05FDA3F0>: operation 0 progress 36
[04:40:51.0993] <DFU Device 05FDA3F0>: operation 0 progress 38
[04:40:51.0995] <DFU Device 05FDA3F0>: operation 0 progress 39
[04:40:51.0997] <DFU Device 05FDA3F0>: operation 0 progress 41
[04:40:51.0999] <DFU Device 05FDA3F0>: operation 0 progress 42
[04:40:52.0001] <DFU Device 05FDA3F0>: operation 0 progress 43
[04:40:52.0003] <DFU Device 05FDA3F0>: operation 0 progress 45
[04:40:52.0005] <DFU Device 05FDA3F0>: operation 0 progress 46
[04:40:52.0007] <DFU Device 05FDA3F0>: operation 0 progress 48
[04:40:52.0009] <DFU Device 05FDA3F0>: operation 0 progress 49
[04:40:52.0011] <DFU Device 05FDA3F0>: operation 0 progress 51
[04:40:52.0013] <DFU Device 05FDA3F0>: operation 0 progress 52
[04:40:52.0015] <DFU Device 05FDA3F0>: operation 0 progress 53
[04:40:52.0017] <DFU Device 05FDA3F0>: operation 0 progress 55
[04:40:52.0019] <DFU Device 05FDA3F0>: operation 0 progress 56
[04:40:52.0021] <DFU Device 05FDA3F0>: operation 0 progress 58
[04:40:52.0023] <DFU Device 05FDA3F0>: operation 0 progress 59
[04:40:52.0025] <DFU Device 05FDA3F0>: operation 0 progress 60
[04:40:52.0027] <DFU Device 05FDA3F0>: operation 0 progress 62
[04:40:52.0029] <DFU Device 05FDA3F0>: operation 0 progress 63
[04:40:52.0031] <DFU Device 05FDA3F0>: operation 0 progress 65
[04:40:52.0033] <DFU Device 05FDA3F0>: operation 0 progress 66
[04:40:52.0035] <DFU Device 05FDA3F0>: operation 0 progress 68
[04:40:52.0037] <DFU Device 05FDA3F0>: operation 0 progress 69
[04:40:52.0039] <DFU Device 05FDA3F0>: operation 0 progress 70
[04:40:52.0041] <DFU Device 05FDA3F0>: operation 0 progress 72
[04:40:52.0043] <DFU Device 05FDA3F0>: operation 0 progress 73
[04:40:52.0045] <DFU Device 05FDA3F0>: operation 0 progress 75
[04:40:52.0047] <DFU Device 05FDA3F0>: operation 0 progress 76
[04:40:52.0049] <DFU Device 05FDA3F0>: operation 0 progress 77
[04:40:52.0051] <DFU Device 05FDA3F0>: operation 0 progress 79
[04:40:52.0053] <DFU Device 05FDA3F0>: operation 0 progress 80
[04:40:52.0055] <DFU Device 05FDA3F0>: operation 0 progress 82
[04:40:52.0057] <DFU Device 05FDA3F0>: operation 0 progress 83
[04:40:52.0059] <DFU Device 05FDA3F0>: operation 0 progress 85
[04:40:52.0061] <DFU Device 05FDA3F0>: operation 0 progress 86
[04:40:52.0063] <DFU Device 05FDA3F0>: operation 0 progress 87
[04:40:52.0065] <DFU Device 05FDA3F0>: operation 0 progress 89
[04:40:52.0067] <DFU Device 05FDA3F0>: operation 0 progress 90
[04:40:52.0069] <DFU Device 05FDA3F0>: operation 0 progress 92
[04:40:52.0071] <DFU Device 05FDA3F0>: operation 0 progress 93
[04:40:52.0073] <DFU Device 05FDA3F0>: operation 0 progress 95
[04:40:52.0075] <DFU Device 05FDA3F0>: operation 0 progress 96
[04:40:52.0077] <DFU Device 05FDA3F0>: operation 0 progress 97
[04:40:52.0079] <DFU Device 05FDA3F0>: operation 0 progress 99
[04:40:52.0079] WinDFU::UploadData: EOF, cbRead: 1084
[04:40:52.0081] <DFU Device 05FDA3F0>: operation 0 progress 100
[04:40:52.0082] WinDFU::UploadData: ZLP
[04:40:52.0082] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
[04:40:52.0083] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
[04:40:52.0084] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
[04:40:52.0085] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
[04:40:55.0081] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
[04:40:55.0082] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
[04:40:55.0082] WinDFU::ResetDevice: resetting...
[04:40:55.0234] WinDFU::FinalizeDfuUpdate: success
[04:40:55.0237] <DFU Device 05FDA3F0>: DFU succeeded
[04:40:55.0239] Finished DFU Restore Phase: Successful
[04:40:55.0279] DFU mode device disconnected
[04:40:55.0281] Device removed when in state Restoring, moving device to transition state
[04:40:55.0282] Changing state from 'Restoring' to 'Transitioning'
[04:40:55.0283] Creating timer to monitor transition
[04:41:25.0846] DFU mode device connected
[04:41:25.0846] Transitioning device returned, continuing restore.
[04:41:25.0847] Canceling timer
[04:41:25.0848] Changing state from 'Transitioning' to 'Restoring'
[04:41:25.0849] AppleDevice::GetDeviceID: failed for iBoot
[04:41:25.0850] AppleDevice::GetDeviceID: failed for iBoot
[04:41:25.0850] requested restore behavior: Erase
[04:41:25.0851] requested variant: Erase
[04:41:25.0860] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[04:41:26.0594] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
[04:41:26.0595] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
[04:41:26.0597] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
[04:41:26.0598] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
[04:41:26.0600] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
[04:41:26.0601] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
[04:41:26.0602] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBSS"
[04:41:26.0604] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
[04:41:26.0605] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "Diags" not part of manifest, skipping
[04:41:26.0607] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "CFELoader" not part of manifest, skipping
[04:41:26.0608] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RBM" not part of manifest, skipping
[04:41:26.0609] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PHLEET" not part of manifest, skipping
[04:41:26.0610] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PERTOS" not part of manifest, skipping
[04:41:26.0612] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PEHammer" not part of manifest, skipping
[04:41:26.0613] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
[04:41:26.0613] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
[04:41:26.0614] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "LLB"
[04:41:26.0615] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
[04:41:26.0616] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
[04:41:26.0617] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "SEP"
[04:41:26.0618] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
[04:41:26.0619] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreSEP"
[04:41:26.0619] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
[04:41:26.0620] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
[04:41:26.0621] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
[04:41:26.0622] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
[04:41:26.0623] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
[04:41:26.0624] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
[04:41:26.0625] <DFU Device 121B7E30>: production fused device
[04:41:26.0625] requested restore behavior: Erase
[04:41:26.0626] AppleDevice::GetDeviceID: failed for iBoot
[04:41:26.0627] AppleDevice::GetDeviceID: failed for iBoot
[04:41:26.0628] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#ec6fe4df
[04:41:26.0629] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#ec6fe4df
[04:41:26.0630] <DFU Device 121B7E30>: operation 0 progress 0
[04:41:26.0631] <DFU Device 121B7E30>: operation 0 progress 1
[04:41:26.0632] <DFU Device 121B7E30>: operation 0 progress 2
[04:41:26.0633] <DFU Device 121B7E30>: operation 0 progress 3
[04:41:26.0634] <DFU Device 121B7E30>: operation 0 progress 4
[04:41:26.0635] <DFU Device 121B7E30>: operation 0 progress 5
[04:41:26.0639] <DFU Device 121B7E30>: operation 0 progress 6
[04:41:26.0643] <DFU Device 121B7E30>: operation 0 progress 7
[04:41:26.0647] <DFU Device 121B7E30>: operation 0 progress 8
[04:41:26.0653] <DFU Device 121B7E30>: operation 0 progress 9
[04:41:26.0657] <DFU Device 121B7E30>: operation 0 progress 10
[04:41:26.0661] <DFU Device 121B7E30>: operation 0 progress 11
[04:41:26.0665] <DFU Device 121B7E30>: operation 0 progress 12
[04:41:26.0669] <DFU Device 121B7E30>: operation 0 progress 13
[04:41:26.0675] <DFU Device 121B7E30>: operation 0 progress 14
[04:41:26.0679] <DFU Device 121B7E30>: operation 0 progress 15
[04:41:26.0683] <DFU Device 121B7E30>: operation 0 progress 16
[04:41:26.0687] <DFU Device 121B7E30>: operation 0 progress 17
[04:41:26.0694] <DFU Device 121B7E30>: operation 0 progress 18
[04:41:26.0698] <DFU Device 121B7E30>: operation 0 progress 19
[04:41:26.0702] <DFU Device 121B7E30>: operation 0 progress 20
[04:41:26.0706] <DFU Device 121B7E30>: operation 0 progress 21
[04:41:26.0711] <DFU Device 121B7E30>: operation 0 progress 22
[04:41:26.0717] <DFU Device 121B7E30>: operation 0 progress 23
[04:41:26.0721] <DFU Device 121B7E30>: operation 0 progress 24
[04:41:26.0725] <DFU Device 121B7E30>: operation 0 progress 25
[04:41:26.0729] <DFU Device 121B7E30>: operation 0 progress 26
[04:41:26.0735] <DFU Device 121B7E30>: operation 0 progress 27
[04:41:26.0739] <DFU Device 121B7E30>: operation 0 progress 28
[04:41:26.0743] <DFU Device 121B7E30>: operation 0 progress 29
[04:41:26.0747] <DFU Device 121B7E30>: operation 0 progress 30
[04:41:26.0751] <DFU Device 121B7E30>: operation 0 progress 31
[04:41:26.0757] <DFU Device 121B7E30>: operation 0 progress 32
[04:41:26.0761] <DFU Device 121B7E30>: operation 0 progress 33
[04:41:26.0765] <DFU Device 121B7E30>: operation 0 progress 34
[04:41:26.0769] <DFU Device 121B7E30>: operation 0 progress 35
[04:41:26.0775] <DFU Device 121B7E30>: operation 0 progress 36
[04:41:26.0779] <DFU Device 121B7E30>: operation 0 progress 37
[04:41:26.0783] <DFU Device 121B7E30>: operation 0 progress 38
[04:41:26.0787] <DFU Device 121B7E30>: operation 0 progress 39
[04:41:26.0793] <DFU Device 121B7E30>: operation 0 progress 40
[04:41:26.0797] <DFU Device 121B7E30>: operation 0 progress 41
[04:41:26.0801] <DFU Device 121B7E30>: operation 0 progress 42
[04:41:26.0805] <DFU Device 121B7E30>: operation 0 progress 43
[04:41:26.0809] <DFU Device 121B7E30>: operation 0 progress 44
[04:41:26.0815] <DFU Device 121B7E30>: operation 0 progress 45
[04:41:26.0819] <DFU Device 121B7E30>: operation 0 progress 46
[04:41:26.0823] <DFU Device 121B7E30>: operation 0 progress 47
[04:41:26.0827] <DFU Device 121B7E30>: operation 0 progress 48
[04:41:26.0833] <DFU Device 121B7E30>: operation 0 progress 49
[04:41:26.0837] <DFU Device 121B7E30>: operation 0 progress 50
[04:41:26.0841] <DFU Device 121B7E30>: operation 0 progress 51
[04:41:26.0845] <DFU Device 121B7E30>: operation 0 progress 52
[04:41:26.0849] <DFU Device 121B7E30>: operation 0 progress 53
[04:41:26.0855] <DFU Device 121B7E30>: operation 0 progress 54
[04:41:26.0859] <DFU Device 121B7E30>: operation 0 progress 55
[04:41:26.0863] <DFU Device 121B7E30>: operation 0 progress 56
[04:41:26.0867] <DFU Device 121B7E30>: operation 0 progress 57
[04:41:26.0873] <DFU Device 121B7E30>: operation 0 progress 58
[04:41:26.0877] <DFU Device 121B7E30>: operation 0 progress 59
[04:41:26.0881] <DFU Device 121B7E30>: operation 0 progress 60
[04:41:26.0885] <DFU Device 121B7E30>: operation 0 progress 61
[04:41:26.0889] <DFU Device 121B7E30>: operation 0 progress 62
[04:41:26.0895] <DFU Device 121B7E30>: operation 0 progress 63
[04:41:26.0899] <DFU Device 121B7E30>: operation 0 progress 64
[04:41:26.0903] <DFU Device 121B7E30>: operation 0 progress 65
[04:41:26.0907] <DFU Device 121B7E30>: operation 0 progress 66
[04:41:26.0913] <DFU Device 121B7E30>: operation 0 progress 67
[04:41:26.0918] <DFU Device 121B7E30>: operation 0 progress 68
[04:41:26.0922] <DFU Device 121B7E30>: operation 0 progress 69
[04:41:26.0926] <DFU Device 121B7E30>: operation 0 progress 70
[04:41:26.0930] <DFU Device 121B7E30>: operation 0 progress 71
[04:41:26.0936] <DFU Device 121B7E30>: operation 0 progress 72
[04:41:26.0940] <DFU Device 121B7E30>: operation 0 progress 73
[04:41:26.0944] <DFU Device 121B7E30>: operation 0 progress 74
[04:41:26.0948] <DFU Device 121B7E30>: operation 0 progress 75
[04:41:26.0954] <DFU Device 121B7E30>: operation 0 progress 76
[04:41:26.0958] <DFU Device 121B7E30>: operation 0 progress 77
[04:41:26.0962] <DFU Device 121B7E30>: operation 0 progress 78
[04:41:26.0966] <DFU Device 121B7E30>: operation 0 progress 79
[04:41:26.0972] <DFU Device 121B7E30>: operation 0 progress 80
[04:41:26.0976] <DFU Device 121B7E30>: operation 0 progress 81
[04:41:26.0980] <DFU Device 121B7E30>: operation 0 progress 82
[04:41:26.0984] <DFU Device 121B7E30>: operation 0 progress 83
[04:41:26.0988] <DFU Device 121B7E30>: operation 0 progress 84
[04:41:26.0994] <DFU Device 121B7E30>: operation 0 progress 85
[04:41:26.0998] <DFU Device 121B7E30>: operation 0 progress 86
[04:41:27.0002] <DFU Device 121B7E30>: operation 0 progress 87
[04:41:27.0006] <DFU Device 121B7E30>: operation 0 progress 88
[04:41:27.0012] <DFU Device 121B7E30>: operation 0 progress 89
[04:41:27.0016] <DFU Device 121B7E30>: operation 0 progress 90
[04:41:27.0020] <DFU Device 121B7E30>: operation 0 progress 91
[04:41:27.0024] <DFU Device 121B7E30>: operation 0 progress 92
[04:41:27.0028] <DFU Device 121B7E30>: operation 0 progress 93
[04:41:27.0034] <DFU Device 121B7E30>: operation 0 progress 94
[04:41:27.0038] <DFU Device 121B7E30>: operation 0 progress 95
[04:41:27.0042] <DFU Device 121B7E30>: operation 0 progress 96
[04:41:27.0046] <DFU Device 121B7E30>: operation 0 progress 97
[04:41:27.0052] <DFU Device 121B7E30>: operation 0 progress 98
[04:41:27.0057] <DFU Device 121B7E30>: operation 0 progress 99
[04:41:27.0059] WinDFU::UploadData: EOF, cbRead: 1084
[04:41:27.0060] <DFU Device 121B7E30>: operation 0 progress 100
[04:41:27.0061] WinDFU::UploadData: ZLP
[04:41:27.0062] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
[04:41:27.0062] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
[04:41:27.0063] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
[04:41:27.0064] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
[04:41:30.0061] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
[04:41:30.0062] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
[04:41:30.0063] WinDFU::ResetDevice: resetting...
[04:41:30.0127] WinDFU::FinalizeDfuUpdate: success
[04:41:30.0128] <DFU Device 121B7E30>: DFU succeeded
[04:41:30.0130] Finished DFU Restore Phase: Successful
[04:41:30.0174] DFU mode device disconnected
[04:41:30.0175] Device removed when in state Restoring, moving device to transition state
[04:41:30.0176] Changing state from 'Restoring' to 'Transitioning'
[04:41:30.0178] Creating timer to monitor transition
[04:41:41.0291] Recovery mode device connected
[04:41:41.0292] Transitioning device returned, continuing restore.
[04:41:41.0293] Canceling timer
[04:41:41.0293] Changing state from 'Transitioning' to 'Restoring'
[04:41:41.0294] requested restore behavior: Erase
[04:41:41.0295] requested variant: Erase
[04:41:41.0311] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[04:41:41.0927] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
[04:41:41.0929] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
[04:41:41.0930] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
[04:41:41.0932] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
[04:41:41.0933] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
[04:41:41.0934] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
[04:41:41.0936] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBSS"
[04:41:41.0937] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
[04:41:41.0938] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "Diags" not part of manifest, skipping
[04:41:41.0940] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "CFELoader" not part of manifest, skipping
[04:41:41.0941] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RBM" not part of manifest, skipping
[04:41:41.0943] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PHLEET" not part of manifest, skipping
[04:41:41.0944] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PERTOS" not part of manifest, skipping
[04:41:41.0946] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PEHammer" not part of manifest, skipping
[04:41:41.0947] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
[04:41:41.0948] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
[04:41:41.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "LLB"
[04:41:41.0951] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
[04:41:41.0953] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
[04:41:41.0954] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "SEP"
[04:41:41.0955] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
[04:41:41.0957] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreSEP"
[04:41:41.0958] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
[04:41:41.0960] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
[04:41:41.0961] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
[04:41:41.0962] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
[04:41:41.0964] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
[04:41:41.0966] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
[04:41:41.0967] iBoot build-version = iBoot-1940.10.58
[04:41:41.0968] iBoot build-style = RELEASE
[04:41:41.0969] requested restore behavior: Erase
[04:41:41.0971] requested restore behavior: Erase
[04:41:41.0972] unable to open device_map.txt: No such file or directory
[04:41:41.0974] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[04:41:41.0975] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[04:41:41.0976] AMDeviceIoControl: GetOverlappedResult failed
[04:41:41.0979] AMDeviceIoControl: pipe stall
[04:41:41.0980] USBControlTransfer: error 31, usbd status c0000004
[04:41:41.0981] command device request for 'getenv radio-error' failed: 2008
[04:41:41.0983] radio-error not set
[04:41:41.0984] unable to open device_map.txt: No such file or directory
[04:41:41.0985] <Recovery Mode Device 12703958>: production fused device
[04:41:41.0987] requested restore behavior: Erase
[04:41:41.0989] requested restore behavior: Erase
[04:41:41.0990] interface has 1 endpoints, file pipe = 1
[04:41:41.0990]
[04:41:41.0991] <Recovery Mode Device 12703958>: operation 4 progress -1
[04:41:41.0992] unable to open device_map.txt: No such file or directory
[04:41:41.0992] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[04:41:41.0993] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[04:41:41.0994] requested restore behavior: Erase
[04:41:41.0995] requested restore behavior: Erase
[04:41:41.0996] <Recovery Mode Device 12703958>: operation 42 progress -1
[04:41:41.0996] requested restore behavior: Erase
[04:41:43.0024] <Recovery Mode Device 12703958>: operation 5 progress -1
[04:41:43.0367] unable to open device_map.txt: No such file or directory
[04:41:43.0369] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[04:41:43.0370] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[04:41:43.0370] AMDeviceIoControl: GetOverlappedResult failed
[04:41:43.0371] AMDeviceIoControl: pipe stall
[04:41:43.0372] USBControlTransfer: error 31, usbd status c0000004
[04:41:43.0373] command device request for 'getenv ramdisk-delay' failed: 2008
[04:41:44.0483] <Recovery Mode Device 12703958>: operation 6 progress -1
[04:41:45.0512] <Recovery Mode Device 12703958>: operation 7 progress -1
[04:41:45.0832] <Recovery Mode Device 12703958>: operation 8 progress -1
[04:41:45.0833] unable to open device_map.txt: No such file or directory
[04:41:45.0833] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[04:41:45.0834] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[04:41:45.0835] <Recovery Mode Device 12703958>: operation 9 progress -1
[04:41:45.0836] <Recovery Mode Device 12703958>: Recovery mode succeeded
[04:41:45.0836] Finished Recovery Restore Phase: Successful
[04:41:46.0607] Recovery mode device disconnected
[04:41:46.0609] Device removed when in state Restoring, moving device to transition state
[04:41:46.0611] Changing state from 'Restoring' to 'Transitioning'
[04:41:46.0612] Creating timer to monitor transition
[04:41:49.0792] Restore completed, status:4014
[04:41:49.0792] Failure Description:
[04:41:49.0792] Depth:0 Error:Unexpected device state 'DFU' expected 'RestoreOS'[
and After one time give me
2014-04-13 14:22:48.639 [3380:18a4]: restore library built Feb 12 2014 at 16:27:17
2014-04-13 14:22:48.639 [3380:18a4]: iTunes: iTunes 11.1.5.5
2014-04-13 14:22:48.639 [3380:18a4]: iTunes: Software payload version: 11D167 (option key)
2014-04-13 14:22:48.639 [3380:18a4]: iTunes: Using MobileRestore state machine
[12:24:20.0679] Changing state from 'Idle' to 'Restoring'
[12:24:20.0713] AppleDevice::GetDeviceID: failed for iBoot
[12:24:20.0714] AppleDevice::GetDeviceID: failed for iBoot
[12:24:20.0719] requested restore behavior: Erase
[12:24:20.0728] requested variant: Erase
[12:24:20.0803] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[12:24:21.0345] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is True
[12:24:21.0345] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreLogo" Digest = "<CFData 12C393C0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0346] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreDeviceTree" Digest = "<CFData 12C38EB0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0347] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreKernelCache" Digest = "<CFData 12C39408 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0348] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreRamDisk" Digest = "<CFData 12C38E68 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0349] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBEC" Digest = "<CFData 12C388C8 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0350] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 12C38A30 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0351] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "KernelCache" Digest = "<CFData 12C37EA8 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0352] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "Diags" not part of manifest, skipping
[12:24:21.0352] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "CFELoader" not part of manifest, skipping
[12:24:21.0353] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RBM" not part of manifest, skipping
[12:24:21.0354] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PHLEET" not part of manifest, skipping
[12:24:21.0354] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PERTOS" not part of manifest, skipping
[12:24:21.0355] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PEHammer" not part of manifest, skipping
[12:24:21.0356] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow1" Digest = "<CFData 12C38F40 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0357] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow0" Digest = "<CFData 12C394E0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0358] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 12C389A0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0358] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBoot" Digest = "<CFData 12C38AC0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0359] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "DeviceTree" Digest = "<CFData 12C385B0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0360] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "SEP" Digest = "<CFData 12C37D40 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0361] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging1" Digest = "<CFData 12C39768 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0362] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreSEP" Digest = "<CFData 12C38958 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0363] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "AppleLogo" Digest = "<CFData 12C391C8 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0364] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryPlugin" Digest = "<CFData 12C39888 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0365] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryFull" Digest = "<CFData 12C39600 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0366] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging0" Digest = "<CFData 12C39450 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0367] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RecoveryMode" Digest = "<CFData 12C39840 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
[12:24:21.0368] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 12BDD478 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[12:24:21.0369] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
[12:24:21.0369] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/ADMINI~1/AppData/Local/Temp/Per9561.tmp/amai/debug/ts s-request.plist
[12:24:23.0320] amai: tss_submit_job: HttpQueryInfo returned 200
[12:24:23.0326] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.0.0)
[12:24:23.0328] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/ADMINI~1/AppData/Local/Temp/Per9561.tmp/amai/debug/ts s-response.plist
[12:24:23.0408] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
[12:24:23.0410] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "CFELoader"
[12:24:23.0412] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "RBM"
[12:24:23.0414] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PHLEET"
[12:24:23.0415] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PERTOS"
[12:24:23.0417] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PEHammer"
[12:24:23.0443] <DFU Device 07B89C58>: production fused device
[12:24:23.0444] requested restore behavior: Erase
[12:24:23.0446] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[12:24:23.0447] AppleDevice::GetDeviceID: failed for iBoot
[12:24:23.0447] AppleDevice::GetDeviceID: failed for iBoot
[12:24:23.0454] amai: AMAuthInstallPlatformCreateDataFromFileURL: can't resolve file
[12:24:23.0455] failed to read dfu file C:\Users\ADMINI~1\AppData\Local\Temp\Per9561.tmp\Firmware\dfu\iBSS.n51ap.RELEAS E.im4p
[12:24:23.0455] WinDFUUpload: dfuData is NULL!
[12:24:23.0456] AMRAuthInstallDeletePersonalizedBundle
[12:24:23.0765] Restore completed, status:2005
[12:24:23.0765] Failure Description:
[12:24:23.0765] Depth:0 Error:Failed to restore device in DFU mode.
i hope some one help me

Put the iPhone in DFU mode. Connect in iTunes. Hit Restore.
(Don't use Shift or Option)

Restoring complete flash archive

Similar Messages

Maybe you are looking for