iPhone 4S soft DFU stuck – error 4014 – iphone problem , and strang problem

Home  >>  iPhone  >>  iPhone 4S soft DFU stuck – error 4014 – iphone problem , and strang problem

iPhone 4S soft DFU stuck – error 4014 – iphone problem , and strang problem

On January 25, 2015, Posted by , In iPhone, With Comments Off on iPhone 4S soft DFU stuck – error 4014 – iphone problem , and strang problem

No water damager. Turned off on 20% of battery. Didnt want to turn on (backlight comes on, and sometimes apple logo but it goes of). Its stuck in soft DFU. Restoring doesnt work (error 4014). Replacing battery, dock connector, dock flex cable didnt work. This is the error log:


It doesnt let me post error log so I will edit this part by part (it says I cant post links, although it contains no links at all)

2014-03-06 05:52:51.631 [10024:2768]: restore library built Feb 12 2014 at 16:27:17
2014-03-06 05:52:51.631 [10024:2768]: iTunes: iTunes 11.1.5.5
2014-03-06 05:52:51.631 [10024:2768]: iTunes: Software payload version: 11B651
2014-03-06 05:52:51.631 [10024:2768]: iTunes: Using MobileRestore state machine
[04:53:29.0001] Changing state from Idle to Restoring
[04:53:29.0001] AppleDevice::GetDeviceID: failed for iBoot
[04:53:29.0019] requested restore behavior: Erase
[04:53:29.0022] requested variant: Erase
[04:53:29.0026] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[04:53:29.0504] amai: _AMAuthInstallBundleCreateServerRequestDictionary: Along withApTicket is True
[04:53:29.0504] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing RestoreLogo Digest = <CFData 0F0B3D58 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0505] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing RestoreDeviceTree Digest = <CFData 0F0B3380 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0505] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing RestoreKernelCache Digest = <CFData 0F0B2D08 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0506] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing RestoreRamDisk Digest = <CFData 0F0B2258 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0506] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing iBEC Digest = <CFData 0F0B3C38 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0507] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing iBSS Digest = <CFData 0F0B3068 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0508] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing KernelCache Digest = <CFData 0F0B39F8 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0508] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing BatteryLow1 Digest = <CFData 0F0B2408 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0509] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing BatteryLow0 Digest = <CFData 0F0B2330 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0509] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing iBoot Digest = <CFData 0F0B3650 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0510] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing DeviceTree Digest = <CFData 0F0B2C78 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0510] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing BatteryCharging1 Digest = <CFData 0F0B2570 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0511] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing AppleLogo Digest = <CFData 0F0B37B8 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing BatteryPlugin Digest = <CFData 0F0B22E8 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing BatteryFull Digest = <CFData 0F0B2918 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0513] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing BatteryCharging0 Digest = <CFData 0F0B2600 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0513] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing RecoveryMode Digest = <CFData 0F0B3F50 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0514] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 05FB47B0 [70FF907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
[04:53:29.0515] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
[04:53:29.0515] amai: AMAuthInstallDebugWriteObject: debug object written: [EDITED]tss-request[DOT]plist
[04:53:30.0057] amai: tss_submit_job: HttpQueryInfo returned 200
[04:53:30.0211] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
[04:53:30.0211] amai: AMAuthInstallDebugWriteObject: debug object written: [EDITED]tss-response[DOT]plist
[04:53:30.0226] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for Diags
[04:53:30.0248] <DFU Device 05FF1508>: production fused device
[04:53:30.0248] requested restore behavior: Erase
[04:53:30.0249] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[04:53:30.0250] AppleDevice::GetDeviceID: failed for iBoot
[04:53:30.0252] WinDFU::OpenDFUDevice: path: \?USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}000#c90c86d8
[04:53:30.0252] WinDFU::OpenDeviceByPath: \?USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}000#c90c86d8
[04:53:30.0263] <DFU Device 05FF1508>: operation 0 progress 0
[04:53:30.0273] <DFU Device 05FF1508>: operation 0 progress 1
[04:53:30.0283] <DFU Device 05FF1508>: operation 0 progress 2
[04:53:30.0303] <DFU Device 05FF1508>: operation 0 progress 3
[04:53:30.0313] <DFU Device 05FF1508>: operation 0 progress 4
[04:53:30.0323] <DFU Device 05FF1508>: operation 0 progress 5
[04:53:30.0343] <DFU Device 05FF1508>: operation 0 progress 6
[04:53:30.0353] <DFU Device 05FF1508>: operation 0 progress 7
[04:53:30.0373] <DFU Device 05FF1508>: operation 0 progress 8
[04:53:30.0383] <DFU Device 05FF1508>: operation 0 progress 9
[04:53:30.0393] <DFU Device 05FF1508>: operation 0 progress 10
[04:53:30.0413] <DFU Device 05FF1508>: operation 0 progress 11
[04:53:30.0423] <DFU Device 05FF1508>: operation 0 progress 12
[04:53:30.0433] <DFU Device 05FF1508>: operation 0 progress 13
[04:53:30.0453] <DFU Device 05FF1508>: operation 0 progress 14
[04:53:30.0463] <DFU Device 05FF1508>: operation 0 progress 15
[04:53:30.0483] <DFU Device 05FF1508>: operation 0 progress 16
[04:53:30.0493] <DFU Device 05FF1508>: operation 0 progress 17
[04:53:30.0503] <DFU Device 05FF1508>: operation 0 progress 18
[04:53:30.0523] <DFU Device 05FF1508>: operation 0 progress 19
[04:53:30.0533] <DFU Device 05FF1508>: operation 0 progress 20
[04:53:30.0543] <DFU Device 05FF1508>: operation 0 progress 21
[04:53:30.0563] <DFU Device 05FF1508>: operation 0 progress 22
[04:53:30.0573] <DFU Device 05FF1508>: operation 0 progress 23
[04:53:30.0593] <DFU Device 05FF1508>: operation 0 progress 24
[04:53:30.0603] <DFU Device 05FF1508>: operation 0 progress 25
[04:53:30.0613] <DFU Device 05FF1508>: operation 0 progress 26
[04:53:30.0633] <DFU Device 05FF1508>: operation 0 progress 27
[04:53:30.0643] <DFU Device 05FF1508>: operation 0 progress 28
[04:53:30.0653] <DFU Device 05FF1508>: operation 0 progress 29
[04:53:30.0673] <DFU Device 05FF1508>: operation 0 progress 30
[04:53:30.0683] <DFU Device 05FF1508>: operation 0 progress 31
[04:53:30.0703] <DFU Device 05FF1508>: operation 0 progress 32
[04:53:30.0713] <DFU Device 05FF1508>: operation 0 progress 33
[04:53:30.0723] <DFU Device 05FF1508>: operation 0 progress 34
[04:53:30.0743] <DFU Device 05FF1508>: operation 0 progress 35
[04:53:30.0753] <DFU Device 05FF1508>: operation 0 progress 36
[04:53:30.0763] <DFU Device 05FF1508>: operation 0 progress 37
[04:53:30.0783] <DFU Device 05FF1508>: operation 0 progress 38
[04:53:30.0793] <DFU Device 05FF1508>: operation 0 progress 39
[04:53:30.0813] <DFU Device 05FF1508>: operation 0 progress 40
[04:53:30.0823] <DFU Device 05FF1508>: operation 0 progress 41
[04:53:30.0833] <DFU Device 05FF1508>: operation 0 progress 42
[04:53:30.0853] <DFU Device 05FF1508>: operation 0 progress 43
[04:53:30.0863] <DFU Device 05FF1508>: operation 0 progress 44
[04:53:30.0873] <DFU Device 05FF1508>: operation 0 progress 45
[04:53:30.0893] <DFU Device 05FF1508>: operation 0 progress 46
[04:53:30.0903] <DFU Device 05FF1508>: operation 0 progress 47
[04:53:30.0923] <DFU Device 05FF1508>: operation 0 progress 48
[04:53:30.0933] <DFU Device 05FF1508>: operation 0 progress 49
[04:53:30.0943] <DFU Device 05FF1508>: operation 0 progress 50
[04:53:30.0963] <DFU Device 05FF1508>: operation 0 progress 51
[04:53:30.0973] <DFU Device 05FF1508>: operation 0 progress 52
[04:53:30.0983] <DFU Device 05FF1508>: operation 0 progress 53
[04:53:31.0003] <DFU Device 05FF1508>: operation 0 progress 54
[04:53:31.0013] <DFU Device 05FF1508>: operation 0 progress 55
[04:53:31.0033] <DFU Device 05FF1508>: operation 0 progress 56
[04:53:31.0043] <DFU Device 05FF1508>: operation 0 progress 57
[04:53:31.0053] <DFU Device 05FF1508>: operation 0 progress 58
[04:53:31.0073] <DFU Device 05FF1508>: operation 0 progress 59
[04:53:31.0083] <DFU Device 05FF1508>: operation 0 progress 60
[04:53:31.0093] <DFU Device 05FF1508>: operation 0 progress 61
[04:53:31.0113] <DFU Device 05FF1508>: operation 0 progress 62
[04:53:31.0123] <DFU Device 05FF1508>: operation 0 progress 63
[04:53:31.0143] <DFU Device 05FF1508>: operation 0 progress 64
[04:53:31.0153] <DFU Device 05FF1508>: operation 0 progress 65
[04:53:31.0163] <DFU Device 05FF1508>: operation 0 progress 66
[04:53:31.0183] <DFU Device 05FF1508>: operation 0 progress 67
[04:53:31.0193] <DFU Device 05FF1508>: operation 0 progress 68
[04:53:31.0203] <DFU Device 05FF1508>: operation 0 progress 69
[04:53:31.0223] <DFU Device 05FF1508>: operation 0 progress 70
[04:53:31.0233] <DFU Device 05FF1508>: operation 0 progress 71
[04:53:31.0253] <DFU Device 05FF1508>: operation 0 progress 72
[04:53:31.0263] <DFU Device 05FF1508>: operation 0 progress 73
[04:53:31.0273] <DFU Device 05FF1508>: operation 0 progress 74
[04:53:31.0293] <DFU Device 05FF1508>: operation 0 progress 75
[04:53:31.0303] <DFU Device 05FF1508>: operation 0 progress 76
[04:53:31.0313] <DFU Device 05FF1508>: operation 0 progress 77
[04:53:31.0340] <DFU Device 05FF1508>: operation 0 progress 78
[04:53:31.0350] <DFU Device 05FF1508>: operation 0 progress 79
[04:53:31.0370] <DFU Device 05FF1508>: operation 0 progress 80
[04:53:31.0380] <DFU Device 05FF1508>: operation 0 progress 81
[04:53:31.0390] <DFU Device 05FF1508>: operation 0 progress 82
[04:53:31.0410] <DFU Device 05FF1508>: operation 0 progress 83
[04:53:31.0420] <DFU Device 05FF1508>: operation 0 progress 84
[04:53:31.0430] <DFU Device 05FF1508>: operation 0 progress 85
[04:53:31.0450] <DFU Device 05FF1508>: operation 0 progress 86
[04:53:31.0460] <DFU Device 05FF1508>: operation 0 progress 87
[04:53:31.0480] <DFU Device 05FF1508>: operation 0 progress 88
[04:53:31.0490] <DFU Device 05FF1508>: operation 0 progress 89
[04:53:31.0500] <DFU Device 05FF1508>: operation 0 progress 90
[04:53:31.0520] <DFU Device 05FF1508>: operation 0 progress 91
[04:53:31.0530] <DFU Device 05FF1508>: operation 0 progress 92
[04:53:31.0540] <DFU Device 05FF1508>: operation 0 progress 93
[04:53:31.0560] <DFU Device 05FF1508>: operation 0 progress 94
[04:53:31.0570] <DFU Device 05FF1508>: operation 0 progress 95
[04:53:31.0590] <DFU Device 05FF1508>: operation 0 progress 96
[04:53:31.0600] <DFU Device 05FF1508>: operation 0 progress 97
[04:53:31.0610] <DFU Device 05FF1508>: operation 0 progress 98
[04:53:31.0630] <DFU Device 05FF1508>: operation 0 progress 99
[04:53:31.0630] WinDFU::UploadData: EOF, cbRead: 1116
[04:53:31.0636] <DFU Device 05FF1508>: operation 0 progress 100

Any ideas?

No Comment so far:

  1. ExpertBuddy says:

    Anyway since I cant edit then it goes:

    [04:53:34.0655] WinDFU::FinalizeDfuUpdate: success
    [04:53:34.0656] <DFU Device 05FF1508>: DFU succeeded
    [04:53:34.0656] Finished DFU Restore Phase: Successful
    [04:53:34.0671] DFU mode device disconnected
    [04:53:34.0671] Device removed when in state Restoring, moving device to transition state
    [04:53:34.0671] Changing state from Restoring to Transitioning
    [04:53:34.0672] Creating timer to monitor transition
    [04:53:35.0084] DFU mode device connected
    [04:53:35.0084] Transitioning device returned, continuing restore.
    [04:53:35.0084] Canceling timer
    [04:53:35.0084] Changing state from Transitioning to Restoring
    [04:53:35.0085] AppleDevice::GetDeviceID: failed for iBoot
    [04:53:35.0085] requested restore behavior: Erase
    [04:53:35.0085] requested variant: Erase

    and then same process and at the end:

    [04:53:39.0967] WinDFU::FinalizeDfuUpdate: success
    [04:53:39.0967] <DFU Device 0606B268>: DFU succeeded
    [04:53:39.0968] Finished DFU Restore Phase: Successful
    [04:53:39.0995] DFU mode device disconnected
    [04:53:39.0995] Device removed when in state Restoring, moving device to transition state
    [04:53:39.0995] Changing state from Restoring to Transitioning
    [04:53:39.0996] Creating timer to monitor transition
    [04:53:41.0465] Restore completed, status:4014
    [04:53:41.0465] Failure Description:
    [04:53:41.0465] Depth:0 Error:Unexpected device state DFU expected Recovery

  2. ExpertBuddy says:

    BUMP!
    Anyone got any idea?

    I will get it back in few days so I will open it up to check some components. Is there a specific capacitor/resistor/connector that I want to check?

  3. ExpertBuddy says:

    Few updates:
    For some reason when I plugged the phone into power adapter it showed connect to iTunes. Ive connected it to a computer and used Tiny Umbrella to do Fix Recovery – the Phone showed apple logo like its booting turned off and started again. (if I tried restore this time the phone saw UDID, but still AppleDevice::GetDeviceID: failed for iBoot)
    I suspected something is wrong Along with power so i plugged it into a wall. It booted up nicely. After about 2 minutes the phone powered off – the screen suddenly just got maybe a bit yellowish and faded away. It was fast but Im pretty shure like it frozen and faded away in about 1 second. Then it reboots and the phone is powered on for 1 minute (all the time its plugged into a wall adapter), and then same thing. Again same thing after 30 seconds, then 15… etc.
    Ive disassembled the phone and removed battery, plugged it into wall – same thing happened.
    One thing I managed to notice is – wireless not working, phone searching for network (although no sim is installed) and no IMEI and modem number.
    Ive tested battery Along with multimeter – it is 3.7 V, but (a big but) seems like the batteries flex cable is bad since it only shows 3.7 V if i get the right angle, if i move it a bit, it loses contact (or makes short circuit, but probably loses contact) and its 0V. So the battery is pretty much useless. Ive also checked if the VCC and GND are in short circuit – they are not.

    1) Ive wanted to check voltages but havent found exactly how to do that – do I search for VCC on schematics and check for 3.7 V on that component compared to GND?
    2) Also what components should I check – since this seems something related to power/baseband?
    3) Could it be that some capacitor overheats and causes short circuit? Or do you suspect some chips want to be reballed?
    4) Can I check voltages if the phone is in soft DFU (not recovery -> connect to itunes screen)?
    5) Can i check voltage Along withouth the battery – just by pluging it into a wall adapter?
    6) Can EMI Shields be removed Along without a heat gun?

    Additional info:
    the original owner said there was no water damage (although one guy did clean it for me Along with ultrasonic cleaner), however I suspect that the phone has fallen to the ground since it has 2 small dents on top.
    I havent noticed physical damage on the motherboard although I have no microscope, I used big magnifying glass.
    I didnt noticed it overheating – just once – when it was on black screen Along with backlight.
    When it actually booted up and restarted few times as Ive mentioned above it didnt get hot at all.

  4. julianz says:

    Error 4014 is hardware related and in your case, its the baseband chip according to log and the fact that it has no imei