iPhone 5s error 4014

[d42k11]

Hello

I am working on this iPhone 5s which is giving error 4014. This phone has no water damage. I know error 4014 is no communication between nand and cpu. I check voltage before band going to capacitor and it is giving 1.8 bolts I did remove nand and check voltage I am getting 1.8volts and 3volts under nand. Can someone shade some light what else could be wrong why I am getting error 4014 ?
Please

Also is their any way I can test nand with multimeter if the band is defective without mounting nand on the board or any tool I can buy to test?

If the nand is defective this phone is garbage?? Because as far as I know band cannot be replaced with new one because it has info on it which has to match to CPU and imei ic please correct me if I am wrong
Thank you for reading my post

[d42k11]

this is the restore log



[16:22:44.0539] WinDFU::UploadData: ZLP
[16:22:44.0549] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
[16:22:44.0549] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
[16:22:44.0549] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
[16:22:44.0549] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
[16:22:47.0549] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
[16:22:47.0549] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
[16:22:47.0549] WinDFU::ResetDevice: resetting...
[16:22:47.0619] WinDFU::FinalizeDfuUpdate: success
[16:22:47.0619] <DFU Device 0000000007D4B7F0>: DFU succeeded
[16:22:47.0619] Finished DFU Restore Phase: Successful
[16:22:47.0649] DFU mode device disconnected
[16:22:47.0649] Device removed when in state Restoring, moving device to transition state
[16:22:47.0649] Changing state from 'Restoring' to 'Transitioning'
[16:22:47.0649] Creating timer to monitor transition
[16:22:49.0510] Recovery mode device connected
[16:22:49.0510] Transitioning device returned, continuing restore.
[16:22:49.0510] Canceling timer
[16:22:49.0510] Changing state from 'Transitioning' to 'Restoring'
[16:22:49.0510] requested restore behavior: Erase
[16:22:49.0520] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
[16:22:49.0520] requested restore behavior: Erase
[16:22:49.0520] requested variant: Erase
[16:22:49.0520] requested restore behavior: Erase
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBSS"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "ftap" not part of manifest, skipping
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "rfta" not part of manifest, skipping
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "ftsp" not part of manifest, skipping
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "rfts" not part of manifest, skipping
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "Diags" not part of manifest, skipping
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "CFELoader" not part of manifest, skipping
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RBM" not part of manifest, skipping
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PHLEET" not part of manifest, skipping
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PERTOS" not part of manifest, skipping
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PEHammer" not part of manifest, skipping
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "LLB"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "SEP"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreSEP"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
[16:22:49.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
[16:22:49.0950] iBoot build-version = iBoot-2817.1.94
[16:22:49.0960] iBoot build-style = RELEASE
[16:22:49.0960] requested restore behavior: Erase
[16:22:49.0960] requested restore behavior: Erase
[16:22:49.0960] unable to open device_map.txt: No such file or directory
[16:22:49.0960] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[16:22:49.0960] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[16:22:49.0960] AMDeviceIoControl: GetOverlappedResult failed
[16:22:49.0960] AMDeviceIoControl: pipe stall
[16:22:49.0960] USBControlTransfer: error 31, usbd status c0000004
[16:22:49.0960] command device request for 'getenv radio-error' failed: 2008
[16:22:49.0960] radio-error not set
[16:22:49.0960] unable to open device_map.txt: No such file or directory
[16:22:49.0960] <Recovery Mode Device 0000000007E2C2B0>: production fused device
[16:22:49.0960] requested restore behavior: Erase
[16:22:49.0960] requested restore behavior: Erase
[16:22:49.0970] interface has 1 endpoints, file pipe = 1
[16:22:49.0970]
[16:22:49.0970] <Recovery Mode Device 0000000007E2C2B0>: operation 4 progress -1
[16:22:49.0970] unable to open device_map.txt: No such file or directory
[16:22:49.0970] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[16:22:49.0970] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[16:22:49.0970] requested restore behavior: Erase
[16:22:49.0970] requested restore behavior: Erase
[16:22:49.0980] <Recovery Mode Device 0000000007E2C2B0>: operation 42 progress -1
[16:22:49.0980] requested restore behavior: Erase
[16:22:50.0990] <Recovery Mode Device 0000000007E2C2B0>: operation 5 progress -1
[16:22:51.0690] unable to open device_map.txt: No such file or directory
[16:22:51.0690] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[16:22:51.0690] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[16:22:51.0690] AMDeviceIoControl: GetOverlappedResult failed
[16:22:51.0690] AMDeviceIoControl: pipe stall
[16:22:51.0690] USBControlTransfer: error 31, usbd status c0000004
[16:22:51.0690] command device request for 'getenv ramdisk-delay' failed: 2008
[16:22:52.0960] <Recovery Mode Device 0000000007E2C2B0>: operation 6 progress -1
[16:22:53.0970] <Recovery Mode Device 0000000007E2C2B0>: operation 7 progress -1
[16:22:54.0300] <Recovery Mode Device 0000000007E2C2B0>: operation 8 progress -1
[16:22:54.0300] unable to open device_map.txt: No such file or directory
[16:22:54.0300] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
[16:22:54.0300] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
[16:22:54.0300] <Recovery Mode Device 0000000007E2C2B0>: operation 9 progress -1
[16:22:54.0300] <Recovery Mode Device 0000000007E2C2B0>: Recovery mode succeeded
[16:22:54.0300] Finished Recovery Restore Phase: Successful
[16:22:55.0250] Recovery mode device disconnected
[16:22:55.0250] Device removed when in state Restoring, moving device to transition state
[16:22:55.0250] Changing state from 'Restoring' to 'Transitioning'
[16:22:55.0250] Creating timer to monitor transition
[16:24:17.0325] DFU mode device connected
[16:24:17.0325] Transitioning device returned, continuing restore.
[16:24:17.0325] Canceling timer
[16:24:17.0325] Changing state from 'Transitioning' to 'Restoring'
[16:24:17.0325] Restore completed, status:4014
[16:24:17.0325] Failure Description:
[16:24:17.0325] Depth:0 Error:Unexpected device state 'DFU' expected 'RestoreOS'

[brukain]

the mistake 4014 can be caused by short circuit of the sensor of approach on a loop of the frontal camera. Also hit of water under a chip of a compass and short circuits of the tire of data of i2c. Nand or the processor failed. Nand changes together with the modem processor and a chip of eeprom (u6_rf) on 5s they aren't attached to the processor.

[d42k11]

the mistake 4014 can be caused by short circuit of the sensor of approach on a loop of the frontal camera. Also hit of water under a chip of a compass and short circuits of the tire of data of i2c. Nand or the processor failed. Nand changes together with the modem processor and a chip of eeprom (u6_rf) on 5s they aren't attached to the processor.


I know the nand and u6_rf as well as modem is paired together

At the moment i dont have modem on the board i want it to confirm thats nand is ok and i want it to give me error -1 that would be because no modem on the board but i keep on getting error 4014 at this moment i have no modem on the board took out U21 , U22, U12 to narrow out the problem but i am still getting error 4014. i get apple logo on screen with wheel spinning and then it it goes away and waits for the phone to reconnect to computer

[brukain]

u16 check if not help, then the problem is in u1 or u4

[cj_miller]

You can individually replace NAND, but it is necessary to correct the serial number. Меняется флешка отдельно, только серийник надо в ней сменить.

[d42k11]

You can individually replace NAND, but it is necessary to correct the serial number. Меняется флешка отдельно, только серийник надо в ней сменить.

how can I do that can you please guide me. thanks in advance

[cj_miller]

look PM

[d42k11]

look pm

[rassoft]

You have said that the dead flush instruction on this matter only one carry in service

[cj_miller]

You have said that the dead flush instruction on this matter only one carry in service

Чаво?

[rassoft]

Sews useless , look at getting water..closure goes on IC2

[Zall]

Do not f@ck head. If you put a work of Nand and get 4014 - a blade DDR.

[d42k11]

Do not f@ck head. If you put a work of Nand and get 4014 - a blade DDR.

blade ddr??

I don't understand what you are trying to say!! Ddr is built in the CPU I think so

[BadGoose]

d24k11
DDR is seating at the top of the CPU so called package-on-package (https://en.wikipedia.org/wiki/Package_on_package). So if you have good skill you can try to reball/replace DDR separately from CPU. Unfortunately, there is often no way to diagnose CPU/DDR/NAND problem with multimeter only. So if you want to check if the problem is in the NAND, you should replace NAND by 100% working NAND or install suspected NAND into 100% working logic board.