GSM Shop GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > Product Support Sections > Hard/Software Products (official support) > MFC Team Products > iBUS Tools For Apple Watch

Closed Thread
 
LinkBack Thread Tools Display Modes
Old 07-05-2017, 11:13   #1 (permalink)
frx
Junior Member
 
Join Date: Jul 2017
Posts: 30
Member: 2733505
Status: Offline
Thanks Meter: 4
Apple Watch S2 iTunes Restore Error 53 / 54 / 9 / 56


Hello
I'm trying to restore a Demo Apple Watch S2 with iTunes on a Mac. I've tried multiple times with a firmware I obtained from Apple, but when it's near completion, it shows Error 53. Is there a way to solve this problem?
 
Old 07-05-2017, 13:16   #2 (permalink)
Product Manager
 
.::Gsmdenis::.'s Avatar
 
Join Date: Aug 2002
Location: MFC
Posts: 8,297
Member: 79315
Status: Offline
Thanks Meter: 6,024
Check the iTunes operation logs
 
Old 07-05-2017, 13:45   #3 (permalink)
frx
Junior Member
 
Join Date: Jul 2017
Posts: 30
Member: 2733505
Status: Offline
Thanks Meter: 4
Hi

This is the last part of the Log

[23:23:50.1517] yZ/AM7s-[AMSupportURLSession URLSession:didReceiveChallenge:completionHandler:]: Authentication challenge received. Method: NSURLAuthenticationMethodServerTrust
[23:23:50.1517] -[AMSupportURLSession URLSession:didReceiveChallenge:completionHandler:]: Attempting trust evaluate
[23:23:50.1517] AMSupportX509ChainEvaluateTrust: Number of trusted roots: 1
[23:23:50.1517] AMSupportX509ChainEvaluateTrust: Number of server certificates: 1
[23:23:50.1517] AMSupportX509ChainEvaluateTrust: First server cert length 1375
[23:23:50.1517] AMSupportX509ChainEvaluateTrust: Trusted root #0 has length 1462
[23:23:50.1517] AMSupportX509DecodeVerifyCertIssuer: PKI: verify cert was issued and signed by issuer (success)
[23:23:50.1517] AMSupportX509ChainEvaluateTrust: PKI: verify cert was issued by trusted root 0 (success)
[23:23:50.1517] AMSupportX509ChainEvaluateTrust: PKI: Chain validation complete. (success)
[23:23:50.1517] -[AMSupportURLSession URLSession:didReceiveChallenge:completionHandler:]: Trust evaluation succeeded, proceeding..
[23:23:50.1517] _AMFDRHttpMessageSendSync: ^^^^^^^^^^^^^^^^^^^^^^^^^ END httpRequest ^^^^^^^^^^^^^^^^^^^^^^^^^
[23:23:50.1517] _AMFDRHttpMessageSendSync: vvvvvvvvvvvvvvvvvvvvvvvvv BEGIN httpResponse vvvvvvvvvvvvvvvvvvvvvvvvv
[23:23:50.1517] _AMFDRHttpLogResponse: header count=8 status=403
[23:23:50.1517] _AMFDRHttpLogResponse: X-Frame-Options: SAMEORIGIN
[23:23:50.1517] _AMFDRHttpLogResponse: Server: Shield
[23:23:50.1517] _AMFDRHttpLogResponse: Content-Type: application/octet-stream
[23:23:50.1517] _AMFDRHttpLogResponse: Content-Length: 28
[23:23:50.1517] _AMFDRHttpLogResponse: x-fdr-message: Error retrieving device cert
[23:23:50.1517] _AMFDRHttpLogResponse: Connection: keep-alive
[23:23:50.1517] _AMFDRHttpLogResponse: Date: Wed, 21 Jun 2017 21:23:48 GMT
[23:23:50.1517] _AMFDRHttpLogResponse: Strict-Transport-Security: max-age=31536000; includeSubdomains
[23:23:50.1517] _AMFDRHttpLogResponse: Error retrieving device cert
[23:23:50.1517] _AMFDRHttpMessageSendSync: vvvvvvvvvvvvvvvvvvvvvvvvv END httpResponse vvvvvvvvvvvvvvvvvvvvvvvvv
[23:23:50.1517] AMFDRCreateError: _AMFDRHttpHandleHeaderMessage: _AMFDRHttpHandleHeaderMessage returned status 403. x-fdr-message: 'Error retrieving device cert': code=403
[23:23:50.1517] AMFDRCreateError: _AMFDRPermissionsRequestWithString: AMFDRPermissionsRequest failed: code=8
[23:23:50.1517] AMFDRCreateError: _AMFDRPermissionsRequest: _AMFDRPermissionsRequestWithString failed: code=8
[23:23:50.1517] _AMFDRPermissionsRequest: AMFDRPermissionsRequest rescue failed with error Error Domain=AMFDRError Code=8 "_AMFDRPermissionsRequestWithString failed" UserInfo={NSUnderlyingError=0x17536f00 {Error Domain=AMFDRError Code=8 "AMFDRPermissionsRequest failed" UserInfo={NSUnderlyingError=0x1753e000 {Error Domain=AMFDRError Code=403 "_AMFDRHttpHandleHeaderMessage returned status 403. x-fdr-message: 'Error retrieving device cert'" UserInfo={NSDescription=_AMFDRHttpHandleHeaderMess age returned status 403. x-fdr-message: 'Error retrieving device cert'}}, NSDescription=AMFDRPermissionsRequest failed}}, NSDescription=_AMFDRPermissionsRequestWithString failed}
[23:23:50.1517] _AMFDRPermissionsRequest: AMFDRPermissionsRequest failed with error Error Domain=AMFDRError Code=8 "AMFDRPermissionsRequest failed" UserInfo={NSUnderlyingError=0x17618950 {Error Domain=AMFDRError Code=403 "_AMFDRHttpHandleHeaderMessage returned status 403. x-fdr-message: 'Error retrieving device cert'" UserInfo={NSDescription=_AMFDRHttpHandleHeaderMess age returned status 403. x-fdr-message: 'Error retrieving device cert'}}, NSDescription=AMFDRPermissionsRequest failed}
[23:23:50.1517] AMFDRCreateError: AMFDRDataHTTPLoadPersistent: Permissions request failed.: code=12
[23:23:50.1517] AMFDRCreateError: AMFDRDataHTTPCopy: AMFDRDataHTTPLoadPersistent failed: code=8
[23:23:50.1517] AMFDRCreateError: AMFDRDataCopy: sealXXXXXXXXX-<<<<<MEID>>>>>26 get data failed - foundData is NULL: code=10
[23:23:50.1517] AMFDRCreateError: AMFDRSealedDataPopulate: Unexpected error for sealXXXXXXXXX-<<<<<MEID>>>>>26: 12: code=8
[23:23:50.1517] AMFDRCreateError: AMFDRDataErrorIsBenign: AMFDRSealedDataPopulate failed to report what data is missing: code=10
[23:23:50.1517] AMFDRCreateError: AMFDRDataRecover: AMFDRSealedDataPopulate with amfdrRemote failed with a fatal error: code=10
[23:23:50.1517] AMFDRDataRecoverCurrentDevice(sealData=false) failed, errCode=19
[23:23:50.1517] 0: AMFDRError/13
[23:23:50.1517] 1: AMFDRError/a: AMFDRSealedDataPopulate with amfdrRemote failed with a fatal error
[23:23:50.1517] 2: AMFDRError/a: AMFDRSealedDataPopulate failed to report what data is missing
[23:23:50.1517] 3: AMFDRError/8: Unexpected error for sealXXXXXXXXX-<<<<<MEID>>>>>26: 12
[23:23:50.1517] 4: AMFDRError/a: sealXXXXXXXXX-<<<<<MEID>>>>>26 get data failed - foundData is NULL
[23:23:50.1517] 5: AMFDRError/8: AMFDRDataHTTPLoadPersistent failed
[23:23:50.1517] 6: AMFDRError/c: Permissions request failed.
[23:23:50.1517] [00:43:08.0547-GMT]{5>8} CHECKPOINT FAILURE:(FAILURE:53) RESTORED:[0x0634] fdr_recover iled to report what data is missing)[5]D(Unexpected error for sealXXXXXXXXX-<<<<<MEID>>>>>26: 12)[6]D(sealXXXXXXXXX-<<<<<MEID>>>>>26 get data failed - foundData is NULL)[7]D(AMFDRDataHTTPLoadPersistent failed)[8]D(Permissions request failed.)
[23:23:50.1517] restore-step-results = {0x11070634:{0:53}}
[23:23:50.1517] restore-step-codes = {0x11070634:{0:53}}
[23:23:50.1517] restore-step-domains = {0x11070634:{0:"AMRestoreErrorDomain"}}
[23:23:50.1517] restore-step-error = {0x11070634:"iled to report what data is missing)[5]D(Unexpected error for sealXXXXXXXXX-<<<<<MEID>>>>>26: 12)[6]D(sealXXXXXXXXX-<<<<<MEID>>>>>26 get data failed - foundData is NULL)[7]D(AMFDRDataHTTPLoadPersistent failed)[8]D(Permissions request failed.)"}
[23:23:50.1517] restore-step-uptime = 547
[23:23:50.1517] restore-step-user-progress = 75
[23:23:50.1517] [00:43:08.0567-GMT]{5>8} CHECKPOINT NOTICE: (NVRAM set) restore-step-user-progress=75 [sync=true] (first failure)
[23:23:50.1517] [00:43:08.0571-GMT]{5>8} CHECKPOINT BEGIN: RESTORED:[0x0647] cleanup_check_result
[23:23:50.1517] restore-step-ids = {0x11030634:59;0x11030647:60}
[23:23:50.1517] restore-step-names = {0x11030634:fdr_recover;0x11030647:cleanup_check_r esult}
[23:23:50.1517] restore-step-uptime = 547
[23:23:50.1517] restore-step-user-progress = 75
[23:23:50.1517] [00:43:08.0585-GMT]{5>8} CHECKPOINT END: RESTORED:[0x0647] cleanup_check_result
[23:23:50.1517] restore-step-ids = {0x11030634:59}
[23:23:50.1517] restore-step-names = {0x11030634:fdr_recover}
[23:23:50.1517] restore-step-uptime = 547
[23:23:50.1517] restore-step-user-progress = 75
[23:23:50.1517] [00:43:08.0599-GMT]{5>8} CHECKPOINT BEGIN: RESTORED:[0x0648] cleanup_send_final_status
[23:23:50.1517] restore-step-ids = {0x11030634:59;0x11030648:61}
[23:23:50.1517] restore-step-names = {0x11030634:fdr_recover;0x11030648:cleanup_send_fi nal_status}
[23:23:50.1517] restore-step-uptime = 547
[23:23:50.1517] restore-step-user-progress = 75
[23:23:50.1517] ogress = 75
[23:23:50.1517]
[23:23:50.1517] ==== end of device restore output ====
[23:23:50.1543] AMRAuthInstallDeletePersonalizedBundle
[23:23:50.1572] <Restore Device 0x60000034fd00>: Restore failed (result = 53)
[23:23:50.1573] AMRestorePerformRestoreModeRestoreWithError failed with error: 53
[23:23:50.1573] Finished RestoreOS Restore Phase: Failed
[23:23:50.1574] State Machine Dump, status:ERROR - [state:DFU remaining-cycles:1] -> [state:Recovery remaining-cycles:0] -> [state:RestoreOS remaining-cycles:0 (current state)]
[23:23:50.1576] Changing state from 'Restoring' to 'Error'
[23:23:50.1577] State is now set to error
[23:23:50.1579] Restore completed, status:53
[23:23:50.1579] Failure Description:
[23:23:50.1579] Depth:0 Code:-1 Error:AMRestorePerformRestoreModeRestoreWithError failed with error: 53
[23:23:50.1579] Depth:1 Code:53 Error:Failed to handle message type StatusMsg
[23:23:50.1579] Depth:2 Code:53 Error:failed to recover FDR data
[23:23:50.1579] Depth:3 Code:53 Error:Failed to recover FDR data
[23:23:50.1579] Depth:4 Code:19 Error:invalid error description
[23:23:50.1579] Depth:5 Code:10 Error:AMFDRSealedDataPopulate with amfdrRemote failed with a fatal error
[23:23:50.1579] Depth:6 Code:10 Error:AMFDRSealedDataPopulate failed to report what data is missing
[23:23:50.1579] Depth:7 Code:8 Error:Unexpected error for seal:00008002-001D48D024E9A526: 12
[23:23:50.1579] Depth:8 Code:10 Error:seal:00008002-001D48D024E9A526 get data failed - foundData is NULL
[23:23:50.1579] Depth:9 Code:8 Error:AMFDRDataHTTPLoadPersistent failed
[23:23:50.1579] Depth:10 Code:12 Error:Permissions request failed.
 
Old 07-06-2017, 14:36   #4 (permalink)
Product Manager
 
.::Gsmdenis::.'s Avatar
 
Join Date: Aug 2002
Location: MFC
Posts: 8,297
Member: 79315
Status: Offline
Thanks Meter: 6,024
This error from beginning, try to check with recovery mode
 
Old 07-06-2017, 15:59   #5 (permalink)
frx
Junior Member
 
Join Date: Jul 2017
Posts: 30
Member: 2733505
Status: Offline
Thanks Meter: 4
What do you mean with "recovery mode"?, the watch now seems like is in DFU, screen is black and when connected to iTunes it says it needs to be restored.
 
Old 07-06-2017, 23:36   #6 (permalink)
Insane Poster
 
Join Date: Feb 2017
Posts: 82
Member: 2685790
Status: Offline
Thanks Meter: 21
Quote:
Originally Posted by frx View Post
What do you mean with "recovery mode"?, the watch now seems like is in DFU, screen is black and when connected to iTunes it says it needs to be restored.
Hey. Put Watch in dfu then restore with iTunes. Makes sure the connection is good between ibus and Apple Watch and leave the watch somewhere where it won't be touched or moved by usb cable well you are restoring with iTunes.
 
Old 07-07-2017, 08:08   #7 (permalink)
Product Manager
 
.::Gsmdenis::.'s Avatar
 
Join Date: Aug 2002
Location: MFC
Posts: 8,297
Member: 79315
Status: Offline
Thanks Meter: 6,024
Here is some useful info:

How to enter DFU mode on Apple Watch
 
Old 07-07-2017, 20:22   #8 (permalink)
frx
Junior Member
 
Join Date: Jul 2017
Posts: 30
Member: 2733505
Status: Offline
Thanks Meter: 4
Thanks

I tried putting it in DFU mode but sadly it still shows error 35.

I monitored the log, and it's a little different

[21:17:43.1067] <Restore Device 0x6000001526f0>: operation 14 progress 78
[21:17:44.6140] <Restore Device 0x6000001526f0>: operation 14 progress 80
[21:17:46.0413] <Restore Device 0x6000001526f0>: operation 14 progress 82
[21:17:47.3782] <Restore Device 0x6000001526f0>: operation 14 progress 84
[21:17:48.8803] <Restore Device 0x6000001526f0>: operation 14 progress 86
[21:17:50.2096] <Restore Device 0x6000001526f0>: operation 14 progress 88
[21:17:51.6460] <Restore Device 0x6000001526f0>: operation 14 progress 90
[21:17:52.9804] <Restore Device 0x6000001526f0>: operation 14 progress 92
[21:17:54.4798] <Restore Device 0x6000001526f0>: operation 14 progress 94
[21:17:55.8138] <Restore Device 0x6000001526f0>: operation 14 progress 96
[21:17:57.3211] <Restore Device 0x6000001526f0>: operation 14 progress 98
[21:17:58.5821] <Restore Device 0x6000001526f0>: operation 14 progress 100
[21:18:42.5095] Completed checkpoint id: 0xC05
[21:18:42.5242] Completed checkpoint id: 0x64F
[21:18:42.5429] <Restore Device 0x6000001526f0>: operation 15 progress -1
[21:19:18.7689] <Restore Device 0x6000001526f0>: operation 15 progress -1
[21:19:19.1991] <Restore Device 0x6000001526f0>: operation 16 progress -1
[21:19:19.3909] <Restore Device 0x6000001526f0>: operation 16 progress -1
[21:19:19.6192] Completed checkpoint id: 0x626
[21:19:19.6504] Completed checkpoint id: 0x627
[21:19:19.6842] requested restore behavior: Erase
[21:19:19.6867] <Restore Device 0x6000001526f0>: operation 27 progress -1
[21:19:22.1266] <Restore Device 0x6000001526f0>: operation 27 progress -1
[21:19:22.3114] Completed checkpoint id: 0xE00
[21:19:22.3694] Completed checkpoint id: 0xE01
[21:19:22.4042] Completed checkpoint id: 0xE02
[21:19:22.4186] Completed checkpoint id: 0x628
[21:19:22.4457] Completed checkpoint id: 0x652
[21:19:25.4207] Completed checkpoint id: 0x634
[21:19:25.4208] Checkpoint 0x634 failed with result: 53
[21:19:25.4485] Completed checkpoint id: 0x647
[21:19:25.5442] device returned CFError with code 53
[21:19:25.5442] dumping CFError returned by restored:
[21:19:25.5443] CFError domain:AMRestoreErrorDomain code:53 description:failed to recover FDR data
[21:19:25.5443] CFError domain:AMRestoreErrorDomain code:53 description:Failed to recover FDR data
[21:19:25.5444] CFError domain:AMFDRError code:19 description:(null)
[21:19:25.5444] CFError domain:AMFDRError code:10 description:AMFDRSealedDataPopulate with amfdrRemote failed with a fatal error
[21:19:25.5444] CFError domain:AMFDRError code:10 description:AMFDRSealedDataPopulate failed to report what data is missing
[21:19:25.5445] CFError domain:AMFDRError code:8 description:Unexpected error for seal:00008002-0000F81024E9A526: 12
[21:19:25.5445] CFError domain:AMFDRError code:10 description:seal:00008002-0000F81024E9A526 get data failed - foundData is NULL
[21:19:25.5446] CFError domain:AMFDRError code:8 description:AMFDRDataHTTPLoadPersistent failed
[21:19:25.5446] CFError domain:AMFDRError code:12 description:Permissions request failed.
[21:19:25.5447] Sending acknowledgement that final status was received
[21:19:25.6171] regex matching failed for '[0-9a-fA-F]{40}': 0
[21:19:25.6171]
[21:19:25.7954] regex matching failed for '[0-9]{15}': 0
[21:19:25.7954]
[21:19:25.7956] regex matching failed for '[0-9]{15}': 0
 
Old 07-08-2017, 18:19   #9 (permalink)
Product Manager
 
.::Gsmdenis::.'s Avatar
 
Join Date: Aug 2002
Location: MFC
Posts: 8,297
Member: 79315
Status: Offline
Thanks Meter: 6,024
Do full recharge and try again , must be sure using the last iTunes version
 
Old 07-09-2017, 15:40   #10 (permalink)
frx
Junior Member
 
Join Date: Jul 2017
Posts: 30
Member: 2733505
Status: Offline
Thanks Meter: 4
I left the watch charging for several hours and also tried restoring with the magnetic charger connected. I used both the latest version of iTunes under macOS Sierra and an older (but still supported) version on El Capitan.

Also, I had a closer look at the logs, looks like they are actually identical. What I posted last time was just another part of it (where it would show the error)
 
Old 07-09-2017, 16:56   #11 (permalink)
Product Manager
 
.::Gsmdenis::.'s Avatar
 
Join Date: Aug 2002
Location: MFC
Posts: 8,297
Member: 79315
Status: Offline
Thanks Meter: 6,024
If as u said the procedure near completion, then your watch must displays a red exclamation point now (Or called recovery mode)

Anyway, Delete all old logs, and do one more time ! i need to saw full logs.
 
Old 07-09-2017, 17:06   #12 (permalink)
frx
Junior Member
 
Join Date: Jul 2017
Posts: 30
Member: 2733505
Status: Offline
Thanks Meter: 4
After the error the display stays stuck on the progress ring, if I reset it, it goes back to a black screen. no red exclamation point.

Here are the logs of the two attempts I've done today
www(DOT)mediafire(DOT)com/folder/77h3cuu631op4/LOG_Watch_S2
 
Old 07-09-2017, 17:21   #13 (permalink)
frx
Junior Member
 
Join Date: Jul 2017
Posts: 30
Member: 2733505
Status: Offline
Thanks Meter: 4
I've also uploaded another log, after deleting all the old ones.

Is it possible to have a MD5 checksum of your firmware?
Mine (that I got from Apple directly) is efdddcb4fd5bfb7da1f6e45be71bf54a
 
Old 07-10-2017, 03:39   #14 (permalink)
Product Manager
 
.::Gsmdenis::.'s Avatar
 
Join Date: Aug 2002
Location: MFC
Posts: 8,297
Member: 79315
Status: Offline
Thanks Meter: 6,024
If iBUS S2 Customer, we will send file download link directly

And this s2 firmware (iBUS + MFC (Windows System)- Apple Watch Flash / Restore / Update IPSW (S0 S1 S2) - GSM-Forum) required MFC Dongle :-)
 
Old 07-10-2017, 09:11   #15 (permalink)
frx
Junior Member
 
Join Date: Jul 2017
Posts: 30
Member: 2733505
Status: Offline
Thanks Meter: 4
Currently I'm using the official Apple adapter (the one given to retail stores and service providers). I got it before the iBUS S2 became available.

Since I already have the adapter, can you sell me just the firmware?
 
The Following User Says Thank You to frx For This Useful Post:
Closed Thread

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 



All times are GMT +1. The time now is 17:58.



Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.21997 seconds with 8 queries

SEO by vBSEO