Completion Status Sent Two Times

I am having a problem with my completion status being sent
twice to an LMS. I have 5 questions that are multiple choice (I
give users two attempts at answering each question). Prior to the
Results page, the results are sent to the LMS and the record is
sent twice, not once, like I would like it to be. I have turned off
"reporting interactions", I've turned off the message when an
answer is "correct"...I am not sure what I am doing wrong. Is there
some way to control the submit button or control how the data is
sent to the LMS? Please help...thanks!

chuckguytoronto,
This message seems quite similiar to someone else posting
with the same
issue. Is this AICC or SCORM? What problem is occuring with
the status
being sent more than once?
Regards,
Andrew

Similar Messages

  • ALE VA01 IDOCs are sent two times ?

    My ALE is working well, but for eacher sales order created, Two Idocs are send (Two different idoc number but the same sales order)!
    I use message controle and a partner profile Ku ans LS.
    So where can I check where is this double ?
    Transaction ? Tables ? Spro?
    Best regards
    Henri

    Hi Henri,
    Why do you need to have two partner profile KU and LS?
    Unless you want to send to different target systems. For example, KU is for customer 'ABC' and LS for CRM system.
    If you need only to send one target system then use only partner profile and delete the other one.
    Please ensure the two IDoc generated are having two different recipient (KU and LS) in IDoc control.
    If both IDocs have same recipient then you may need to check the ALE and IDoc configuration again.
    Please check NAST table for initial investigation.
    Hope this will help.
    and don't forget to reward points if helpful as a way to say thanks.
    Regards,
    Ferry Lianto

  • I have had a new hard drive installed. On start up I transferred all my settings and documents from my time capsule. Once complete I have two user accounts. Mine and guest. I cannot access either. Mine says password incorrect even though its not.

    I have had a new hard drive installed. On start up I transferred all my settings and documents from my time capsule. Once complete I have two user accounts. Mine and guest. I cannot access either. Mine says password incorrect even though its not. Any idea what is wrong here and how I can reset my password. I don't have a start up disc. Thanks very much

    From System Preferences/Help:
    Reset your login password using your Apple ID
    Before you can use your Apple ID to reset your login password, make sure that FileVault isn’t enabled on your computer.
    Also make sure that an Apple ID is associated with your user account, and that an administrator has given you permission to reset your own password using an Apple ID. For more information, see this help topic:
    Associate Apple IDs with your user account
    Make sure your computer is connected to the Internet.
    In the login window, click the question mark in the password field, and then click the arrow in the dialog that appears.
    Enter an Apple ID and password, and then click Reset Password.
    I don't know if it works.

  • How system will capture the course completion status

    Hi Gurus,
    Module: OLM/iLearning
    Question: Users have to manadatorily click on "Home" button to get the completion status captured on OLMS? Is it standard functionality? I couldn't find the details in the user manual. Please suggest. Thanks.
    Regards,
    Grandhi.

    Couple points of clarification (at least in Oracle iLearning)
    Completion/learner status is recorded when one of the four things below occur:
    1. The learner navigates to another learning object within the course outline (if there is more than one object)
    2. The learner clicks the home icon (or close, depending on player preference settings)
    3. The content calls ExitAU (for AICC content), or LMSFinish (for SCORM 1.2/2004 content).. This is typically called when the learner moves away from the content by items 1 or 2 above but can also occur for example on the last page of the course, depending on when the content decides to finish communication with the LMS.
    4. The learner closes the browser window. At this stage, assuming pop-up blockers are disabled, the LMS will open a small window for a couple seconds that will finish off the communication with the LMS before fully shutting down. This typically gives the content enough time to call the appropriate finish command listed in #3 above.
    In Oracle iLearning, there are two main options for opening content in a new window, the first separates the main player window from the content and the second includes the content and player in a separate window.
    1. On the content object properties page, the Open in New Window checkbox can be checked. This opens the player in the main browser window and pops up the content in a separate window.
    2. On the offering properties page (select content object -> Offerings link, edit offering), the Open in New Window checkbox can be checked. This will open the player in a new browser window and the content within the player frameset in that new window. If the admin has also clicked the Open in New Window checkbox on the content object properties, a 2nd window will open (total of 3) with the content.
    Scott
    http://www.seertechsolutions.com

  • Complete Status of Purchase Order

    HI SRM Gurus,
       For SRM 7.0  system, for purchase Order  what is the signifance of "Transaction Completed"  status ?
    I have completed one purchase Order which has open item.
    At header level it sets "Transaction Completed" status in SRM PO. but neither it set delete indicator nor delivery complete indicator of open PO items . Hence i wonder what is the signifiance of complete functionality of PO in SRM.
    Can you please through light on this topic ?
    Regards,
    Kalandi

    Checks (SRM-SUS)
    Before SAP SRM SUS documents are archived, they are processed by a check program to determine if they qualify for archiving. This validation procedure prevents documents that still require processing, erroneous documents, and current documents from being archived and subsequently deleted from the database.
    The residence time is a general criterion used to determine when SUS documents are archived. Each document must remain in the system for a certain period of time (the retention period) after it was last changed before it can be archived.
    For more information about setting retention periods, see the Supplier Relationship Management Implementation Guide (IMG):  Supplier Relationship Management  Supplier Self-Services  Cross-Application Basic Settings  Archiving of Documents  Define Residence Times for Documents .
    Note
    Only SUS documents from completed business processes are considered for archiving. Before you can archive documents, you need to complete the business process to which they belong.
    End of the note.
    During the check process, the system also checks the relevant follow-on documents. If these documents have been created and completed, the relevant business transactions are assumed to have been completed. In particular, if a SUS purchase order can be archived, then so can the relevant follow-on documents.
    *The status Transaction Completed is only applicable to SUS purchase orders and indicates that the document flow has been completed.* This means that all necessary documents in the document flow have been created and that, in the SUS EBP scenario, the confirmations and invoices pertaining to the purchase order have also been approved.
    As well as the follow-on documents, the ordered quantity (or the quantity confirmed by the supplier if a purchase order response was requested) and the quantity specified in the follow-on documents must be considered. A purchase order can have one or more follow-on documents for each document type. If the total amount of item values of the follow-on documents does not match the total order value, the process step is not complete. In this case the system does not apply the status Transaction Completed to the original SUS purchase order.
    An exception to this process is when a final delivery indicator has been set for an advanced shipping notification or for the invoice. Only the purchaser can set this indicator, which is used to show that no further delivery or invoice is expected and that this particular process step is completed. This information is only available on the purchaser's side in the purchasing system.
    Example
    A SUS purchase order has one or more advanced shipping notifications (ASN). If the total quantity specified in the ASNs does not match the quantity specified in the purchase order, it implies that some of the goods ordered have not yet been delivered. The delivery process step is therefore not yet completed even though invoices have been created for the existing ASNs.
    http://help.sap.com/saphelp_srm70/helpdata/EN/d8/757af9204942aa86735dfefc62e9cd/frameset.htm

  • Deletion of Leave which is in Status 'SENT' by employee in SAP HR

    Hi All,
    We are using BADI  (BAdI Definition PT_ABS_REQ) for leave validation. In this validation we are checking Current Leaves with the Leaves already applied (Approved / Non-approved).
    In this process, We are trying to DELETE a leave which is in status 'SENT'.
    Issue:
    When we CREATE a new leave, importing parameter of BADI is IM_ATTABS_TAB (type PTARQ_ATTABSDATA_TAB) -Operation = INS.
    And when we DELETE the leave with 'SENT' status, It is also coming IM_ATTABS_TAB - operation = INS.
    Due to above issue, my validation is getting triggered even in DELETE scenario which is not required.
    Please help on this.
    Thanks in advance.
    Hemendra Singh

    to change the status by user, he can modify the hours in the application and resubmit
    For administrator purposes, you should cats_appr_lite, you can reject the all time and do it,
    Do not make any changes directly to CATSDB< it might cause inconsistency
    So better use standard transaction like cats_appr_lite or cats_da

  • I just purchased two Macbook Air along with two Time Capsule (2TB) for my kids. Meanwhile I use a sagemcom ADLS modem/router for home use. Can I connect both Time Capsule and laptop which will allow both laptop to have their own backup system?

    I want both of the computers to have their own independent time capsule.

    want both of the computers to have their own independent time capsule.
    I assume that you are asking about using the Time Capsules for Time Machine backups here, correct?
    If yes, both MBAs will be able to select the specific Time Capsule that they will use for backups, so "point" MBA1 to Time Capsule 1 and MBA2 to Time Capsule 2.
    Since you will have plenty of available backup space if you use two Time Capsules, you might want to consider having each MBA back up to both Time Capsule 1 and Time Capsule 2.
    This way, if one Time Capsule fails, you will still have a complete set of backups for both MBAs.

  • Error submitting tasks: Operation could not be completed within the specified time

    I've created a Batch Application and I'm having an issue running a job.  Its suppose to synchronize 2 azure blob containers.
    In my JobSplitter, I compare 2 azure blob containers and find the files in the first container that need to be copied over to the second one.  Just figuring out which files to copy over can take about 5 to 6 minutes the first time this is run depending
    on the number of files that need to get copied over.
    Once we have the files that need to be copied, we group them into sets and create a task for each set.
    The exe that the TaskProcessor runs doesn't do anything just yet. All it does is write the arguments sent to it into a file. Nothing major.
    On the last run, about 900 tasks were created. Four of the tasks completed successfully. I can download the output files for them just fine. The next 4 tasks failed with an error.
    Looking in the JobLogs, I see this:
    The job orchestrator finished
    Failed to process job ac8dd4a3-d882-4ec1-847d-48844fa3e1f4: Error submitting tasks: Operation could not be completed
    within the specified time. RequestId:27eab612-c8ce-4e4b-8dfb-00e7024c71ec Time:2015-01-29T00:37:03.5943898Z
    Has anyone seen this before?
    Thanks,
    matt

    This error is usually a transient error, typically related to an internal storage timeout.  We're working on a fix for it.
    In the meantime, if you go into the Batch Apps portal, select the failed job and click Reprocess in the command bar, Batch Apps should re-run the failed tasks and the not-run tasks.  (Note that the tasks that already succeeded will not be re-run, and
    we will not re-run the job splitter to create new tasks.)
    Please let us know if you continue to see this problem or if reprocessing the job doesn't work for you.

  • TS4268 Hello, it's been 5 days now since my imessage has not working..and i have chatted to the costumer for two times. I took thier advice and instructions just to enable to send and receive on it but unfortunately until now its still NOT working. Pls.he

    Hello, it's been 5 days now since my imessage has not working..and i have chatted to the costumer for two times. I took thier advice and instructions just to enable to send and receive on it but unfortunately until now its still NOT working. Is there anybody who could help me please?

    Try this even if you have already.  Just make sure to follow the steps specifically.
    Go to settings > Facetime > send and recieve > tap on your apple id and sign out.  If your not signed in then that will work as well.
    Go to settings > Messages > sent and recieve > tap on your apple id and sign out.
    Restart the iPad by doing the slide to power off setup.  Just hold the power button on the top right till it turns off.
    After the iPad has been restarted:
    Go to settings > Facetime > and sign in
    Go to settings > Messages > and sign in
    Wait about 3 min then restart the iPad again.  Same instructions as above.
    When you restart you should be able to use messages again.  If not then call support again and talk to someone higher than the first level support they have.

  • Process does not follow the routing ends up in complete status

    Installed Adobe LiveCycle server ES 2.5 with SQL Server 2008 as database
    And followed the tutorial ‘Create Your First LiveCycle Application’
    Deployed it on the server when I test the same
    i.e. when the workspace user fills in form details and hits complete button it ends up as status complete
    And not assigned to next user in the route
    The process does not follow the routing it ends up in complete status
    And nothing shows up when trying to record and play back the process
    Tried invoking Via workbench too
    no errors in the server log
    Could this be an installation issue any pointers appreciated
    Please advise

    Issue with Jboss as it was taking longtime time to start due to low CPU ideally it should not take more than 3 to 5 minutes
    Process works now

  • The same email sent multiple times

    I have seen this topic a few times but as yet have not read an answer to the issue. It appears that occassionally an email will be sent multiple times to the same recipient. This is very annoying for the recipient, but more importantly can become very expensive if this is happening whilst roaming. Does this only happen if the signal is poor at the point of sending? Replies welcomed.

    that is your problem.
    You are saying: run this workflow whenever the incident is updated with the sole criteria that the incident has the status resolved.
    What is happening is then that the workflow runs the first time and applies the template. This updates the incident which then triggers the workflow. This goes on until one of the runbooks has updated the incident to status closed. Then the criteria is no
    longer true.
    change the changed from to include the criteria
    status NOT EQUAL resolved.
    http://codebeaver.blogspot.dk/

  • Whats the status of Two Step Verification in Canada?

    Has anyone heard what the status of Two Step Verification is in Canada. I have not been able to set it up since it was (supposedly) set up a few months ago. Thanks for your time.

    I have read a dozen news articles regarding two step verification in Canada. They are all a few months old and clearly state that it is ready to go here in Canada. However I have tried the steps to set it up and nothing! It seems to be a dead issue as I can not find any recent info about two step verification in Canada. I was really hoping that with iOS 7 it would have appeared in my account settings but no.

  • To Reopen the Completed Status Global outline agreements

    Hi,
    We have got some Global Outline Agreemtns with 'completed' status by the user. We want to reopen it for additional processing,but the change icon in the global outline agreement is greyed out. Could anybody tell me how to reopen the 'completed' status global outline agreement again?
    Regards,
    Manojkumar.

    Hi
    i believe system behaves correctly.
    to prove you..
    note 712367- Deleted and completed contracts can be changed
    Symptom
    You delete or complete a contract. If you are on the items list of the contract at this time, the change button is still active so that you can change the contract items.
    regards
    muthu

  • SAP 4.6 work processes too often goes to completed status

    Hello,
    SAP 4.6 C  (Oracle 9i / windows NT) system, always work process goes to completed status. This a quality system.
    As of now we are only restaring the work processes (SM50->process->restart after error-> yes) manually as a temporary fix.
    Could you please suggest any solution to this issue ?
    Here is more information about the system :
    SAP R/3 Kernel              46D_EXT
    Support package number      2283
    Thanks,
    Prabhakar Reddy.

    Thank you for your quick reply. Below is the log
    B
    B Wed Sep 29 06:15:32 2010
    B  create_con (con_name=R/3)
    B  Loading DB library 'E:\usr\sap\ING\SYS\exe\run\dboraslib.dll' ...
    B  Library 'E:\usr\sap\ING\SYS\exe\run\dboraslib.dll' loaded
    B  Version of library 'E:\usr\sap\ING\SYS\exe\run\dboraslib.dll' is "46D.00", patchlevel (0.2238)
    B  New connection 0 created
    M  relno      4640
    M  patchlevel 0
    M  patchno    2283
    M  intno      0
    M  pid        8144
    M
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 9 8144) [dpxxdisp.c   976]
    I  MtxInit: -2 0 0
    X  EmInit: MmSetImplementation( 2 ).
    X  <ES> client 9 initializing ....
    X  Using implementation std
    M  <ES> Memory Reset enabled
    X  ES initialized.
    M  ThSysUsrCheck: clear T9
    M  calling db_connect ...
    C  Got NLS_LANG=AMERICAN_AMERICA.US7ASCII from environment
    C  Logon as OPS$-user to get SAPR3's password
    C  Connecting as /@ING on connection 0 ...
    C  *** ERROR => OCI-call 'olog' failed: rc = 12547
    [dboci.c      2460]
    C  *** ERROR => CONNECT failed with sql error '12547'
    [dboci.c      7025]
    C  Try to connect with default password
    C  Connecting as SAPR3/<pwd>@ING on connection 0 ...
    C  *** ERROR => OCI-call 'olog' failed: rc = 12547
    [dboci.c      2460]
    C  *** ERROR => CONNECT failed with sql error '12547'
    [dboci.c      7025]
    C  Got NLS_LANG=AMERICAN_AMERICA.US7ASCII from environment
    C  Logon as OPS$-user to get SAPR3's password
    C  Connecting as /@ING on connection 0 ...
    C  *** ERROR => OCI-call 'olog' failed: rc = 12547
    [dboci.c      2460]
    C  *** ERROR => CONNECT failed with sql error '12547'
    [dboci.c      7025]
    C  Try to connect with default password
    C  Connecting as SAPR3/<pwd>@ING on connection 0 ...
    C
    C Wed Sep 29 06:15:33 2010
    C  Now I'm connected to ORACLE using OCI_7 API
    C
    C Wed Sep 29 06:15:36 2010
    C  Database instance ing is running on TIRUINT04 with ORACLE version 9.2.0.4.0 since 20100929
    B  Connection 0 opened
    B  Wp  Hdl ConName              ConCnt ConState     TX  PRM RCT Date     Time
    B  000 000 R/3                  000000 ACTIVE       NO  YES NO  20100929 061532
    B  ***LOG BY2=> sql error 0      performing CON [dbsh    0707 ]
    B  ***LOG BY0=> ORA-00000: normal, successful completion
    [dbsh    0707 ]
    B  ***LOG BY2=> sql error 0      performing CON [dblink  0627 ]
    B  ***LOG BY0=> ORA-00000: normal, successful completion
    [dblink  0627 ]
    M  ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c   1188]
    M  in_ThErrHandle: 1
    M  *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3) [thxxhead.c   8468]
    Edited by: prabhakaryc on Sep 29, 2010 2:03 PM

  • 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)

Maybe you are looking for

  • Server Side activties have been updated. You need to restart SharePoint Designer to use the updated version of activities.

    Hello, I have the following scenario for the installation of EPM 2013 environment: 1 Server running Windows 2008 R2 SQL Server 2008 R2 Service Pack 2 1 Windows Server 2008 R2 Standard SP1, running Sharepoint 2013 Enterprise (Standard Initially instal

  • Accounting Key & Accruals Key in Calculation Schema (Pricing Procedure)

    Hi Freinds,                I have a query regarding use of Accounting Key & accruals key in the Calculation Schema (Pricing Procedure). What is the significance of Accounting key & accruals key in the calcuation schema?  Which Accounting  & Accruals

  • Email notifications stuck in Mail status

    Hi, The notification mailer is up and running and we receive emails when we run the test. However, when a user goes through the application, lets say the Purchase requisition process, the process completes successfully, we see the notification in his

  • Exit name of  line item in migo

    Hello Gurus. I am doing a Badi in Migo. i want  Exit name  in migo. i am  entering excise line item value in BED ECS HSCess AED NCCD SED . so what is exit name  during this Activity. i am waiting Your Reply. Regard, Riten Patel

  • Easy Question -String conversion to type int

    Greetings Java Gurus, What is the best way to convert a String to type int? I have looked through the JAVA API documentation and have found the following possibilites but I cannot get the JAVA syntax right :( Java.lang.decode public static Integer de