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 > GSM & CDMA Phones / Tablets Software & Hardware Area > iPhone ,iPod & iPad (Apple Inc. Products) > iPhone, iPad, iPod Hardware Repair

iPhone, iPad, iPod Hardware Repair Hardware Repair discussions for iPhone, iPod , iPad & Apple Products, help, guides.

Reply
 
LinkBack Thread Tools Display Modes
Old 02-12-2015, 01:07   #91 (permalink)
Junior Member
 
Join Date: Jan 2013
Posts: 11
Member: 1861954
Status: Offline
Thanks Meter: 0

and what is the real solution???because neither the reflow wifi\bb ic or flex change, or battery change, or proxy' sensor replace NOT WORKING!!!!
  Reply With Quote
Old 07-23-2015, 13:02   #92 (permalink)
Junior Member
 
Join Date: Sep 2008
Location: subic, philippines
Posts: 24
Member: 866380
Status: Offline
Thanks Meter: 1
i got same problem with this.. on my iphone 4s.. any solution???
  Reply With Quote
Old 02-22-2016, 23:57   #93 (permalink)
No Life Poster
 
crysst's Avatar
 
Join Date: Jan 2004
Location: romania
Age: 41
Posts: 679
Member: 48215
Status: Offline
Thanks Meter: 17
hello, i have one iPad 4 with 4013 error, i try all the software solution, and many diferent original cabe, and usb ports. here is the log

2016-02-22 18:56:48.250 [944:f7c]: restore library built Sep 28 2015 at 12:12:42
2016-02-22 18:56:48.250 [944:f7c]: iTunes: iTunes 12.3.2.35
2016-02-22 18:56:48.250 [944:f7c]: iTunes: Software payload version: 13D15
2016-02-22 18:56:48.250 [944:f7c]: iTunes: Using MobileRestore state machine
[16:58:27.0514] Changing state from '(null)' to 'Restoring'
[16:58:27.0515] device software does not support nonce generation
[16:58:27.0559] requested restore behavior: Erase
[16:58:27.0561] requested restore behavior: Erase
[16:58:27.0561] requested variant: Erase
[16:58:27.0564] requested restore behavior: Erase
[16:58:28.0768] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
[16:58:28.0769] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
[16:58:28.0769] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
[16:58:28.0771] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
[16:58:28.0772] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
[16:58:28.0772] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
[16:58:28.0772] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 0CA94B30 [72A1907C]>{length = 20, capacity = 20, bytes = 0x95ce1e9225adbfcea96b27f921d4a88a9e46c51b}"
[16:58:28.0772] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
[16:58:28.0772] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "ftap" not part of manifest, skipping
[16:58:28.0772] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "rfta" not part of manifest, skipping
[16:58:28.0772] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "ftsp" not part of manifest, skipping
[16:58:28.0772] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "rfts" not part of manifest, skipping
[16:58:28.0772] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
[16:58:28.0772] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
[16:58:28.0772] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 05800CC0 [72A1907C]>{length = 20, capacity = 20, bytes = 0x3f3d637e2856272d0f3a439be735cce2298e9b63}"
[16:58:28.0773] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
[16:58:28.0773] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
[16:58:28.0773] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
[16:58:28.0773] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
[16:58:28.0773] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
[16:58:28.0773] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
[16:58:28.0773] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
[16:58:28.0773] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
[16:58:28.0773] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 0C991318 [72A1907C]>{length = 20, capacity = 20, bytes = 0x853d7a27369f39f47479569a0401d2b93cb6d773}
[16:58:28.0774] amai: AMAuthInstallRequestSendSync: SSO function returned NULL and no SSO token was provided, SSO disabled.
[16:58:28.0779] amai: tss_submit_job_with_retry: TSS Connection attempt 1 of 3. (Will retry if TSS_ERR_SERVER_NOT_REACHABLE.)
[16:58:29.0423] amai: tss_submit_job: HttpQueryInfo returned 200
[16:58:29.0425] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
[16:58:29.0652] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "ftap"
[16:58:29.0653] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "rfta"
[16:58:29.0653] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "ftsp"
[16:58:29.0653] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "rfts"
[16:58:29.0718] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
[16:58:29.0781] <DFU Device 057C7C28>: production fused device
[16:58:29.0781] requested restore behavior: Erase
[16:58:29.0781] device software does not support nonce generation
[16:58:29.0792] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#299af45
[16:58:29.0792] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#299af45
[16:58:29.0802] <DFU Device 057C7C28>: operation 0 progress 2
[16:58:29.0811] <DFU Device 057C7C28>: operation 0 progress 4
[16:58:29.0820] <DFU Device 057C7C28>: operation 0 progress 7
[16:58:29.0829] <DFU Device 057C7C28>: operation 0 progress 9
[16:58:29.0839] <DFU Device 057C7C28>: operation 0 progress 12
[16:58:29.0849] <DFU Device 057C7C28>: operation 0 progress 14
[16:58:29.0858] <DFU Device 057C7C28>: operation 0 progress 16
[16:58:29.0867] <DFU Device 057C7C28>: operation 0 progress 19
[16:58:29.0876] <DFU Device 057C7C28>: operation 0 progress 21
[16:58:29.0885] <DFU Device 057C7C28>: operation 0 progress 24
[16:58:29.0895] <DFU Device 057C7C28>: operation 0 progress 26
[16:58:29.0904] <DFU Device 057C7C28>: operation 0 progress 29
[16:58:29.0914] <DFU Device 057C7C28>: operation 0 progress 31
[16:58:29.0923] <DFU Device 057C7C28>: operation 0 progress 33
[16:58:29.0933] <DFU Device 057C7C28>: operation 0 progress 36
[16:58:29.0942] <DFU Device 057C7C28>: operation 0 progress 38
[16:58:29.0951] <DFU Device 057C7C28>: operation 0 progress 41
[16:58:29.0961] <DFU Device 057C7C28>: operation 0 progress 43
[16:58:29.0971] <DFU Device 057C7C28>: operation 0 progress 46
[16:58:29.0981] <DFU Device 057C7C28>: operation 0 progress 48
[16:58:29.0991] <DFU Device 057C7C28>: operation 0 progress 50
[16:58:30.0000] <DFU Device 057C7C28>: operation 0 progress 53
[16:58:30.0009] <DFU Device 057C7C28>: operation 0 progress 55
[16:58:30.0018] <DFU Device 057C7C28>: operation 0 progress 58
[16:58:30.0028] <DFU Device 057C7C28>: operation 0 progress 60
[16:58:30.0038] <DFU Device 057C7C28>: operation 0 progress 63
[16:58:30.0049] <DFU Device 057C7C28>: operation 0 progress 65
[16:58:30.0059] <DFU Device 057C7C28>: operation 0 progress 67
[16:58:30.0069] <DFU Device 057C7C28>: operation 0 progress 70
[16:58:30.0083] <DFU Device 057C7C28>: operation 0 progress 72
[16:58:30.0087] <DFU Device 057C7C28>: operation 0 progress 75
[16:58:30.0097] <DFU Device 057C7C28>: operation 0 progress 77
[16:58:30.0106] <DFU Device 057C7C28>: operation 0 progress 79
[16:58:30.0116] <DFU Device 057C7C28>: operation 0 progress 82
[16:58:30.0125] <DFU Device 057C7C28>: operation 0 progress 84
[16:58:30.0134] <DFU Device 057C7C28>: operation 0 progress 87
[16:58:30.0143] <DFU Device 057C7C28>: operation 0 progress 89
[16:58:30.0153] <DFU Device 057C7C28>: operation 0 progress 92
[16:58:30.0163] <DFU Device 057C7C28>: operation 0 progress 94
[16:58:30.0172] <DFU Device 057C7C28>: operation 0 progress 96
[16:58:30.0182] <DFU Device 057C7C28>: operation 0 progress 99
[16:58:30.0182] WinDFU::UploadData: EOF, cbRead: 566
[16:58:30.0186] <DFU Device 057C7C28>: operation 0 progress 100
[16:58:30.0186] WinDFU::UploadData: ZLP
[16:58:30.0188] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
[16:58:30.0188] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
[16:58:30.0189] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
[16:58:30.0189] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
[16:58:33.0189] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
[16:58:33.0189] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
[16:58:33.0189] WinDFU::ResetDevice: resetting...
[16:58:33.0255] WinDFU::FinalizeDfuUpdate: success
[16:58:33.0255] <DFU Device 057C7C28>: DFU succeeded
[16:58:33.0255] Finished DFU Restore Phase: Successful
[16:58:33.0312] DFU mode device disconnected
[16:58:33.0312] Device removed when in state Restoring, moving device to transition state
[16:58:33.0312] Changing state from 'Restoring' to 'Transitioning'
[16:58:33.0312] Creating timer to monitor transition
[16:59:07.0230] DFU mode device connected
[16:59:07.0230] Transitioning device returned, continuing restore.
[16:59:07.0230] Canceling timer
[16:59:07.0230] Changing state from 'Transitioning' to 'Restoring'
[16:59:07.0230] AppleDevice::GetDeviceID: failed for iBoot
[16:59:07.0236] requested restore behavior: Erase
[16:59:07.0236] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[16:59:07.0236] requested restore behavior: Erase
[16:59:07.0236] requested variant: Erase
[16:59:07.0236] requested restore behavior: Erase
[16:59:08.0401] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is True
[16:59:08.0401] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreLogo" Digest = "<CFData 0CCE15A0 [72A1907C]>{length = 20, capacity = 20, bytes = 0xd9b24b21275fc8318ce6e1d2c50b4ca8e2da3778}"
[16:59:08.0401] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreDeviceTree" Digest = "<CFData 0CA94B78 [72A1907C]>{length = 20, capacity = 20, bytes = 0xb0a721730368848f2e8ef6d213b6c615e6c008cd}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreKernelCache" Digest = "<CFData 063ECF38 [72A1907C]>{length = 20, capacity = 20, bytes = 0x870e750a3a410bcbd8643c768cf738df981541a8}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreRamDisk" Digest = "<CFData 063ECF80 [72A1907C]>{length = 20, capacity = 20, bytes = 0x0a8192f6a06ee91d743d2ebe680f64564c9dcb7e}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBEC" Digest = "<CFData 063ECEF0 [72A1907C]>{length = 20, capacity = 20, bytes = 0x07519de2c8a29b07325af63a7b2f97cc914913e4}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 063ECEA8 [72A1907C]>{length = 20, capacity = 20, bytes = 0x95ce1e9225adbfcea96b27f921d4a88a9e46c51b}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "KernelCache" Digest = "<CFData 063ECE60 [72A1907C]>{length = 20, capacity = 20, bytes = 0x870e750a3a410bcbd8643c768cf738df981541a8}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "ftap" not part of manifest, skipping
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "rfta" not part of manifest, skipping
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "ftsp" not part of manifest, skipping
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "rfts" not part of manifest, skipping
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow1" Digest = "<CFData 063ECE18 [72A1907C]>{length = 20, capacity = 20, bytes = 0x061d9be3075dbb0fc21f82419904ccad7e6c1c6e}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow0" Digest = "<CFData 063ECDD0 [72A1907C]>{length = 20, capacity = 20, bytes = 0x774717c921846bb3198e513a716be77eb57b84b3}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 063ECD88 [72A1907C]>{length = 20, capacity = 20, bytes = 0x3f3d637e2856272d0f3a439be735cce2298e9b63}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBoot" Digest = "<CFData 063ECD40 [72A1907C]>{length = 20, capacity = 20, bytes = 0x179cdf80039688a683917f1b9d1181098c07a82d}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "DeviceTree" Digest = "<CFData 063ECCF8 [72A1907C]>{length = 20, capacity = 20, bytes = 0xb0a721730368848f2e8ef6d213b6c615e6c008cd}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging1" Digest = "<CFData 063ECCB0 [72A1907C]>{length = 20, capacity = 20, bytes = 0x1bd1428ff52532c3274cbf7dc394b3b7d7185279}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "AppleLogo" Digest = "<CFData 063ECC68 [72A1907C]>{length = 20, capacity = 20, bytes = 0xd9b24b21275fc8318ce6e1d2c50b4ca8e2da3778}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryPlugin" Digest = "<CFData 0CB94A38 [72A1907C]>{length = 20, capacity = 20, bytes = 0x38fcfab835faaf681dc149072e58f067ed66abcc}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryFull" Digest = "<CFData 0CB94A80 [72A1907C]>{length = 20, capacity = 20, bytes = 0x06e84afc38b8655d54fd6efda55cea152792be83}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging0" Digest = "<CFData 0CB94AC8 [72A1907C]>{length = 20, capacity = 20, bytes = 0x464eacba693e8e11624f659422edc3316a25d552}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RecoveryMode" Digest = "<CFData 0CB94B10 [72A1907C]>{length = 20, capacity = 20, bytes = 0x7c86d76d9b35c8ca256cfc103621ba727d85b5d1}"
[16:59:08.0403] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 0C9908A0 [72A1907C]>{length = 20, capacity = 20, bytes = 0x853d7a27369f39f47479569a0401d2b93cb6d773}
[16:59:08.0405] amai: AMAuthInstallRequestSendSync: SSO function returned NULL and no SSO token was provided, SSO disabled.
[16:59:08.0413] amai: tss_submit_job_with_retry: TSS Connection attempt 1 of 3. (Will retry if TSS_ERR_SERVER_NOT_REACHABLE.)
[16:59:09.0892] amai: tss_submit_job: HttpQueryInfo returned 200
[16:59:09.0895] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
[16:59:09.0904] amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "iBSS" has been previously personalized; skipping it
[16:59:09.0906] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "ftap"
[16:59:09.0906] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "rfta"
[16:59:09.0906] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "ftsp"
[16:59:09.0906] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "rfts"
[16:59:09.0908] amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "LLB" has been previously personalized; skipping it
[16:59:09.0914] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
[16:59:09.0978] <DFU Device 1180F548>: production fused device
[16:59:09.0978] requested restore behavior: Erase
[16:59:09.0979] AppleDevice::GetDeviceID: failed for iBoot
[16:59:09.0981] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#71b98727
[16:59:09.0981] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#71b98727
[16:59:09.0983] <DFU Device 1180F548>: operation 0 progress 0
[16:59:09.0984] <DFU Device 1180F548>: operation 0 progress 1
[16:59:09.0986] <DFU Device 1180F548>: operation 0 progress 2
[16:59:09.0988] <DFU Device 1180F548>: operation 0 progress 3
[16:59:09.0990] <DFU Device 1180F548>: operation 0 progress 4
[16:59:09.0992] <DFU Device 1180F548>: operation 0 progress 5
[16:59:09.0993] <DFU Device 1180F548>: operation 0 progress 6
[16:59:09.0996] <DFU Device 1180F548>: operation 0 progress 7
[16:59:09.0998] <DFU Device 1180F548>: operation 0 progress 8
[16:59:10.0000] <DFU Device 1180F548>: operation 0 progress 9
[16:59:10.0003] <DFU Device 1180F548>: operation 0 progress 10
[16:59:10.0004] <DFU Device 1180F548>: operation 0 progress 11
[16:59:10.0007] <DFU Device 1180F548>: operation 0 progress 12
[16:59:10.0009] <DFU Device 1180F548>: operation 0 progress 13
[16:59:10.0012] <DFU Device 1180F548>: operation 0 progress 14
[16:59:10.0014] <DFU Device 1180F548>: operation 0 progress 15
[16:59:10.0016] <DFU Device 1180F548>: operation 0 progress 16
[16:59:10.0019] <DFU Device 1180F548>: operation 0 progress 17
[16:59:10.0021] <DFU Device 1180F548>: operation 0 progress 18
[16:59:10.0024] <DFU Device 1180F548>: operation 0 progress 19
[16:59:10.0026] <DFU Device 1180F548>: operation 0 progress 20
[16:59:10.0029] <DFU Device 1180F548>: operation 0 progress 21
[16:59:10.0030] <DFU Device 1180F548>: operation 0 progress 22
[16:59:10.0033] <DFU Device 1180F548>: operation 0 progress 23
[16:59:10.0035] <DFU Device 1180F548>: operation 0 progress 24
[16:59:10.0037] <DFU Device 1180F548>: operation 0 progress 25
[16:59:10.0041] <DFU Device 1180F548>: operation 0 progress 26
[16:59:10.0043] <DFU Device 1180F548>: operation 0 progress 27
[16:59:10.0046] <DFU Device 1180F548>: operation 0 progress 28
[16:59:10.0047] <DFU Device 1180F548>: operation 0 progress 29
[16:59:10.0050] <DFU Device 1180F548>: operation 0 progress 30
[16:59:10.0052] <DFU Device 1180F548>: operation 0 progress 31
[16:59:10.0054] <DFU Device 1180F548>: operation 0 progress 32
[16:59:10.0057] <DFU Device 1180F548>: operation 0 progress 33
[16:59:10.0059] <DFU Device 1180F548>: operation 0 progress 34
[16:59:10.0062] <DFU Device 1180F548>: operation 0 progress 35
[16:59:10.0064] <DFU Device 1180F548>: operation 0 progress 36
[16:59:10.0067] <DFU Device 1180F548>: operation 0 progress 37
[16:59:10.0069] <DFU Device 1180F548>: operation 0 progress 38
[16:59:10.0071] <DFU Device 1180F548>: operation 0 progress 39
[16:59:10.0074] <DFU Device 1180F548>: operation 0 progress 40
[16:59:10.0075] <DFU Device 1180F548>: operation 0 progress 41
[16:59:10.0078] <DFU Device 1180F548>: operation 0 progress 42
[16:59:10.0080] <DFU Device 1180F548>: operation 0 progress 43
[16:59:10.0083] <DFU Device 1180F548>: operation 0 progress 44
[16:59:10.0085] <DFU Device 1180F548>: operation 0 progress 45
[16:59:10.0088] <DFU Device 1180F548>: operation 0 progress 46
[16:59:10.0089] <DFU Device 1180F548>: operation 0 progress 47
[16:59:10.0091] <DFU Device 1180F548>: operation 0 progress 48
[16:59:10.0094] <DFU Device 1180F548>: operation 0 progress 49
[16:59:10.0096] <DFU Device 1180F548>: operation 0 progress 50
[16:59:10.0098] <DFU Device 1180F548>: operation 0 progress 51
[16:59:10.0100] <DFU Device 1180F548>: operation 0 progress 52
[16:59:10.0103] <DFU Device 1180F548>: operation 0 progress 53
[16:59:10.0104] <DFU Device 1180F548>: operation 0 progress 54
[16:59:10.0105] <DFU Device 1180F548>: operation 0 progress 55
[16:59:10.0108] <DFU Device 1180F548>: operation 0 progress 56
[16:59:10.0110] <DFU Device 1180F548>: operation 0 progress 57
[16:59:10.0113] <DFU Device 1180F548>: operation 0 progress 58
[16:59:10.0115] <DFU Device 1180F548>: operation 0 progress 59
[16:59:10.0118] <DFU Device 1180F548>: operation 0 progress 60
[16:59:10.0120] <DFU Device 1180F548>: operation 0 progress 61
[16:59:10.0122] <DFU Device 1180F548>: operation 0 progress 62
[16:59:10.0125] <DFU Device 1180F548>: operation 0 progress 63
[16:59:10.0126] <DFU Device 1180F548>: operation 0 progress 64
[16:59:10.0129] <DFU Device 1180F548>: operation 0 progress 65
[16:59:10.0131] <DFU Device 1180F548>: operation 0 progress 66
[16:59:10.0134] <DFU Device 1180F548>: operation 0 progress 67
[16:59:10.0136] <DFU Device 1180F548>: operation 0 progress 68
[16:59:10.0139] <DFU Device 1180F548>: operation 0 progress 69
[16:59:10.0141] <DFU Device 1180F548>: operation 0 progress 70
[16:59:10.0143] <DFU Device 1180F548>: operation 0 progress 71
[16:59:10.0146] <DFU Device 1180F548>: operation 0 progress 72
[16:59:10.0148] <DFU Device 1180F548>: operation 0 progress 73
[16:59:10.0152] <DFU Device 1180F548>: operation 0 progress 74
[16:59:10.0154] <DFU Device 1180F548>: operation 0 progress 75
[16:59:10.0157] <DFU Device 1180F548>: operation 0 progress 76
[16:59:10.0158] <DFU Device 1180F548>: operation 0 progress 77
[16:59:10.0159] <DFU Device 1180F548>: operation 0 progress 78
[16:59:10.0165] <DFU Device 1180F548>: operation 0 progress 79
[16:59:10.0167] <DFU Device 1180F548>: operation 0 progress 80
[16:59:10.0170] <DFU Device 1180F548>: operation 0 progress 81
[16:59:10.0172] <DFU Device 1180F548>: operation 0 progress 82
[16:59:10.0175] <DFU Device 1180F548>: operation 0 progress 83
[16:59:10.0176] <DFU Device 1180F548>: operation 0 progress 84
[16:59:10.0179] <DFU Device 1180F548>: operation 0 progress 85
[16:59:10.0180] <DFU Device 1180F548>: operation 0 progress 86
[16:59:10.0181] <DFU Device 1180F548>: operation 0 progress 87
[16:59:10.0184] <DFU Device 1180F548>: operation 0 progress 88
[16:59:10.0185] <DFU Device 1180F548>: operation 0 progress 89
[16:59:10.0188] <DFU Device 1180F548>: operation 0 progress 90
[16:59:10.0190] <DFU Device 1180F548>: operation 0 progress 91
[16:59:10.0193] <DFU Device 1180F548>: operation 0 progress 92
[16:59:10.0195] <DFU Device 1180F548>: operation 0 progress 93
[16:59:10.0197] <DFU Device 1180F548>: operation 0 progress 94
[16:59:10.0200] <DFU Device 1180F548>: operation 0 progress 95
[16:59:10.0202] <DFU Device 1180F548>: operation 0 progress 96
[16:59:10.0205] <DFU Device 1180F548>: operation 0 progress 97
[16:59:10.0207] <DFU Device 1180F548>: operation 0 progress 98
[16:59:10.0210] <DFU Device 1180F548>: operation 0 progress 99
[16:59:10.0210] WinDFU::UploadData: EOF, cbRead: 1116
[16:59:10.0211] <DFU Device 1180F548>: operation 0 progress 100
[16:59:10.0211] WinDFU::UploadData: ZLP
[16:59:10.0212] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
[16:59:10.0212] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
[16:59:10.0212] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
[16:59:10.0212] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
[16:59:13.0213] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
[16:59:13.0213] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
[16:59:13.0213] WinDFU::ResetDevice: resetting...
[16:59:13.0279] WinDFU::FinalizeDfuUpdate: success
[16:59:13.0279] <DFU Device 1180F548>: DFU succeeded
[16:59:13.0279] Finished DFU Restore Phase: Successful
[16:59:13.0346] DFU mode device disconnected
[16:59:13.0346] Device removed when in state Restoring, moving device to transition state
[16:59:13.0346] Changing state from 'Restoring' to 'Transitioning'
[16:59:13.0346] Creating timer to monitor transition
[17:00:05.0176] Recovery mode device connected
[17:00:05.0176] Transitioning device returned, continuing restore.
[17:00:05.0176] Canceling timer
[17:00:05.0176] Changing state from 'Transitioning' to 'Restoring'
[17:00:05.0182] requested restore behavior: Erase
[17:00:05.0186] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[17:00:05.0186] requested restore behavior: Erase
[17:00:05.0186] requested variant: Erase
[17:00:05.0186] requested restore behavior: Erase
[17:00:06.0378] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
[17:00:06.0378] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
[17:00:06.0378] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
[17:00:06.0378] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
[17:00:06.0378] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
[17:00:06.0378] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
[17:00:06.0378] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "iBSS" has been previously personalized; skipping it
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "ftap" not part of manifest, skipping
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "rfta" not part of manifest, skipping
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "ftsp" not part of manifest, skipping
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "rfts" not part of manifest, skipping
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "LLB" has been previously personalized; skipping it
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
[17:00:06.0379] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
[17:00:06.0380] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
[17:00:06.0380] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
[17:00:06.0380] iBoot build-version = iBoot-2817.20.26
[17:00:06.0381] iBoot build-style = RELEASE
[17:00:06.0381] requested restore behavior: Erase
[17:00:06.0382] requested restore behavior: Erase
[17:00:06.0383] unable to open device_map.txt: No such file or directory
[17:00:06.0383] found device map entry for 0x00008955 0x00000004. boardConfig=p103ap platform=s5l8955x
[17:00:06.0383] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[17:00:06.0384] AMDeviceIoControl: GetOverlappedResult failed
[17:00:06.0384] AMDeviceIoControl: pipe stall
[17:00:06.0384] USBControlTransfer: error 31, usbd status c0000004
[17:00:06.0384] command device request for 'getenv radio-error' failed: 2008
[17:00:06.0384] radio-error not set
[17:00:06.0384] unable to open device_map.txt: No such file or directory
[17:00:06.0385] <Recovery Mode Device 0CCF7B60>: production fused device
[17:00:06.0385] requested restore behavior: Erase
[17:00:06.0386] requested restore behavior: Erase
[17:00:06.0387] interface has 1 endpoints, file pipe = 1
[17:00:06.0387]
[17:00:06.0387] <Recovery Mode Device 0CCF7B60>: operation 4 progress -1
[17:00:06.0440] unable to open device_map.txt: No such file or directory
[17:00:06.0440] found device map entry for 0x00008955 0x00000004. boardConfig=p103ap platform=s5l8955x
[17:00:06.0440] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[17:00:06.0441] requested restore behavior: Erase
[17:00:06.0441] requested restore behavior: Erase
[17:00:06.0442] <Recovery Mode Device 0CCF7B60>: operation 42 progress -1
[17:00:06.0442] requested restore behavior: Erase
[17:00:07.0488] <Recovery Mode Device 0CCF7B60>: operation 5 progress -1
[17:00:08.0278] unable to open device_map.txt: No such file or directory
[17:00:08.0279] found device map entry for 0x00008955 0x00000004. boardConfig=p103ap platform=s5l8955x
[17:00:08.0279] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[17:00:08.0279] AMDeviceIoControl: GetOverlappedResult failed
[17:00:08.0279] AMDeviceIoControl: pipe stall
[17:00:08.0279] USBControlTransfer: error 31, usbd status c0000004
[17:00:08.0279] command device request for 'getenv ramdisk-delay' failed: 2008
[17:00:10.0723] <Recovery Mode Device 0CCF7B60>: operation 6 progress -1
[17:00:11.0735] <Recovery Mode Device 0CCF7B60>: operation 7 progress -1
[17:00:12.0151] <Recovery Mode Device 0CCF7B60>: operation 8 progress -1
[17:00:12.0151] unable to open device_map.txt: No such file or directory
[17:00:12.0151] found device map entry for 0x00008955 0x00000004. boardConfig=p103ap platform=s5l8955x
[17:00:12.0151] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[17:00:12.0151] <Recovery Mode Device 0CCF7B60>: operation 9 progress -1
[17:00:12.0151] <Recovery Mode Device 0CCF7B60>: Recovery mode succeeded
[17:00:12.0151] Finished Recovery Restore Phase: Successful
[17:00:13.0691] Recovery mode device disconnected
[17:00:13.0691] Device removed when in state Restoring, moving device to transition state
[17:00:13.0691] Changing state from 'Restoring' to 'Transitioning'
[17:00:13.0691] Creating timer to monitor transition
[17:00:27.0182] Recovery mode device connected
[17:00:27.0182] Transitioning device returned, continuing restore.
[17:00:27.0182] Canceling timer
[17:00:27.0182] Changing state from 'Transitioning' to 'Restoring'
[17:00:27.0182] State Machine Dump, status:ERROR - [stateFU remaining-cycles:0] -> [state:Recovery remaining-cycles:0] -> [state:RestoreOS remaining-cycles:1 (current state)]
[17:00:27.0182] Unexpected device state 'Recovery' expected 'RestoreOS'
[17:00:27.0183] Restore completed, status:4013
[17:00:27.0183] Failure Description:
[17:00:27.0183] Depth:0 Error:Unexpected device state 'Recovery' expected 'RestoreOS'


i gues is a hardware problem , baseband anybody had this problem and solved? The ipad come to me with this problem , i dont know the history on how become in this condition, now the ipad have the itunes cable on screen
  Reply With Quote
Old 05-16-2016, 19:38   #94 (permalink)
Insane Poster
 
Join Date: Nov 2006
Posts: 75
Member: 400972
Status: Offline
Thanks Meter: 24
Quote:
Originally Posted by android unbrik View Post
no need change wifi ic. or basband chip. this problum(4013) i get more than10 pcs. i did sucsessfull. contact me privet

br,
please give me your whatsapp
  Reply With Quote
Old 01-16-2017, 05:49   #95 (permalink)
Junior Member
 
Join Date: May 2014
Posts: 6
Member: 2195858
Status: Offline
Thanks Meter: 0
4014 error

Quote:
Originally Posted by yonasmobile View Post
please give me your whatsapp
I am getting 4014 error on ipad 4 try everything found online. Nothing works
  Reply With Quote
Old 01-25-2017, 18:44   #96 (permalink)
Junior Member
 
Join Date: Aug 2007
Posts: 13
Member: 569081
Status: Offline
Thanks Meter: 0
I'm with several giving this same problem, someone has the solution?
  Reply With Quote
Old 01-26-2017, 16:15   #97 (permalink)
Freak Poster
 
Join Date: Sep 2015
Posts: 135
Member: 2453408
Status: Online
Thanks Meter: 42
If you out of ideas try reballing/changing NAND
  Reply With Quote
Old 04-11-2017, 13:12   #98 (permalink)
Insane Poster
 
Join Date: Sep 2008
Location: Poland
Age: 28
Posts: 68
Member: 863309
Status: Offline
Sonork: 4540726
Thanks Meter: 8
Red face

Quote:
Originally Posted by crysst View Post
hello, i have one iPad 4 with 4013 error, i try all the software solution, and many diferent original cabe, and usb ports. here is the log

.....
.....
...
[state:RestoreOS remaining-cycles:1 (current state)]
[17:00:27.0182] Unexpected device state 'Recovery' expected 'RestoreOS'
[17:00:27.0183] Restore completed, status:4013
[17:00:27.0183] Failure Description:
[17:00:27.0183] Depth:0 Error:Unexpected device state 'Recovery' expected 'RestoreOS'


i gues is a hardware problem , baseband anybody had this problem and solved? The ipad come to me with this problem , i dont know the history on how become in this condition, now the ipad have the itunes cable on screen
Reballing baseband or replace.
  Reply With Quote
Old 04-11-2017, 14:14   #99 (permalink)
Freak Poster
 
Join Date: Jan 2016
Location: Hungary
Posts: 270
Member: 2515187
Status: Offline
Thanks Meter: 71
Donate money to this user
Quote:
Originally Posted by hardboy View Post
Reballing baseband or replace.
Error 4013 not baseband problem. It is NAND or processor.
  Reply With Quote
Old 04-22-2017, 21:36   #100 (permalink)
Junior Member
 
Join Date: Aug 2016
Posts: 6
Member: 2609386
Status: Offline
Thanks Meter: 0
Hi guys, while receiving Error 4013 on Ipad 3 GSM I came across this topic.

I read all your comments, but I am not quiet sure which component has to be replaced/ reballed.
Also my itunes log says "no baseband chip ID reported" i am not sure whether this IC is the problem as I also get this log entry with a fully working Ipad 2 3G (at the end of the log it says "successfully restored").

Already isolated the logicboard, battery, display and dock flex from the rest, but it is still in recovery showing 4013.

While restoring the progress bar on the Ipad display appears for approx. 1 sec. (without any progress at all). The Ipad directly reboots again showing itunes sign and error 4013 (same in recovery and DFU mode).

My suggestion would be that depending on the progress bar status before terminating the restoring process, the error could be linked to a specific component.
In my case, I thought about a NAND error as no progress could be due to an incapability on writing data to the NAND? (just an assumption).

Any suggestions?
  Reply With Quote
Old 05-06-2017, 17:48   #101 (permalink)
Junior Member
 
Join Date: Apr 2017
Posts: 2
Member: 2711169
Status: Offline
Thanks Meter: 0
Hello , I wrote you a private message.. thanks
  Reply With Quote
Old 05-13-2017, 22:39   #102 (permalink)
Junior Member
 
Join Date: Aug 2016
Posts: 6
Member: 2609386
Status: Offline
Thanks Meter: 0
To me? Havn't gotten any...
  Reply With Quote
Old 05-14-2017, 02:38   #103 (permalink)
Junior Member
 
Join Date: Mar 2017
Posts: 32
Member: 2697189
Status: Offline
Thanks Meter: 10
error 4013/4014 appear to be generic, expected device recovery mode but appeared again in hdfu. Typically I have seen this with oem parts/ battery failure or low power / incorrectly programmed nand as temp ramdisk o/s cant talk to it / nand bridging when fitted / shorted cap... so there is a lot to look at, even a failed nand can cause it!

first thing i do after battery is remove nand and boot in 3utools make sure it switches from hdfu to recovery mode, if its a phone unplug as many ancilliary devices as you can.
  Reply With Quote
Old 05-19-2017, 18:12   #104 (permalink)
Junior Member
 
Join Date: Aug 2016
Posts: 6
Member: 2609386
Status: Offline
Thanks Meter: 0
Quote:
Originally Posted by TBC01 View Post
error 4013/4014 appear to be generic, expected device recovery mode but appeared again in hdfu. Typically I have seen this with oem parts/ battery failure or low power / incorrectly programmed nand as temp ramdisk o/s cant talk to it / nand bridging when fitted / shorted cap... so there is a lot to look at, even a failed nand can cause it!

first thing i do after battery is remove nand and boot in 3utools make sure it switches from hdfu to recovery mode, if its a phone unplug as many ancilliary devices as you can.
Thanks for your reply. I already changed the battery and disconnected all th unnecessary auxiliaries. nothing changed. My guess would be the NAND too, but at what temp. do you remove it? (another suggestion of one member was the processor?!)

So if I got you right, you are pulling off the NAND and after that you use 3u-tools? Does it work with the free version of 3u too? What exactly are you trying to achieve by rebooting after you removed the NAND? What is supposed to happen?

Thx in advance
  Reply With Quote
Old Yesterday, 16:17   #105 (permalink)
Junior Member
 
Join Date: Mar 2017
Posts: 32
Member: 2697189
Status: Offline
Thanks Meter: 10
3utools displays the actual mode the target device reconnects in i.e dfu / recovery / normal .... itunes doesnt show this except when reading the logs afterwards.
  Reply With Quote
Reply

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 13:36.



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

SEO by vBSEO