Страница 1 из 2 1 2 ПоследняяПоследняя
Показано с 1 по 12 из 23

Тема: iphone 6 Error 4005

  1. #1
    Member
    Регистрация
    28.08.2013
    Адрес
    New Jersey
    Сообщений
    120
    Спасибо
    28
    Благодарностей: 4 : 4

    iphone 6 Error 4005

    hello Friends

    I am working on iphone 6 no water damage never been repaired before and its giving error 4005 stuck on apple logo with timer spinning frozen

    Скрытый текст: Показать
    [16:38:29.0998] <Recovery Mode Device <<<<<MEID>>>>>20>: operation 4 progress -1
    [16:38:30.0000] unable to open device_map.txt: No such file or directory
    [16:38:30.0002] found device map entry for 0x00007000 0x00000006. boardConfig=n61ap platform=t7000
    [16:38:30.0003] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [16:38:30.0005] requested restore behavior: Erase
    [16:38:30.0006] requested restore behavior: Erase
    [16:38:30.0008] <Recovery Mode Device <<<<<MEID>>>>>20>: operation 42 progress -1
    [16:38:30.0010] requested restore behavior: Erase
    [16:38:30.0953] <Recovery Mode Device <<<<<MEID>>>>>20>: operation 5 progress -1
    [16:38:31.0495] unable to open device_map.txt: No such file or directory
    [16:38:31.0497] found device map entry for 0x00007000 0x00000006. boardConfig=n61ap platform=t7000
    [16:38:31.0498] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [16:38:31.0500] AMDeviceIoControl: GetOverlappedResult failed
    [16:38:31.0502] AMDeviceIoControl: pipe stall
    [16:38:31.0503] USBControlTransfer: error 31, usbd status c0000004
    [16:38:31.0505] command device request for 'getenv ramdisk-delay' failed: 2008
    [16:38:32.0687] <Recovery Mode Device <<<<<MEID>>>>>20>: operation 6 progress -1
    [16:38:33.0705] <Recovery Mode Device <<<<<MEID>>>>>20>: operation 7 progress -1
    [16:38:33.0995] <Recovery Mode Device <<<<<MEID>>>>>20>: operation 8 progress -1
    [16:38:33.0997] unable to open device_map.txt: No such file or directory
    [16:38:33.0999] found device map entry for 0x00007000 0x00000006. boardConfig=n61ap platform=t7000
    [16:38:34.0000] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [16:38:34.0002] <Recovery Mode Device <<<<<MEID>>>>>20>: operation 9 progress -1
    [16:38:34.0003] <Recovery Mode Device <<<<<MEID>>>>>20>: Recovery mode succeeded
    [16:38:34.0005] Finished Recovery Restore Phase: Successful
    [16:38:34.0823] Recovery mode device disconnected
    [16:38:34.0825] Device removed when in state Restoring, moving device to transition state
    [16:38:34.0826] Changing state from 'Restoring' to 'Transitioning'
    [16:38:34.0828] Creating timer to monitor transition


    any one knows how to solve this issue i checked the voltage going to nand all powers good 1.2, 3v, 1.8 all good

  2. #2
    Member
    Регистрация
    10.07.2006
    Адрес
    Kurgan 45
    Сообщений
    591
    Спасибо
    51
    Благодарностей: 104 : 49
    по питалову смотри.или и2с

  3. #3
    Elite Member
    Регистрация
    16.02.2011
    Адрес
    Махачкала/Избербаш
    Сообщений
    3,743
    Спасибо
    1,149
    Благодарностей: 2,341 : 1,259
    Блог
    30
    4005 - no cpu-nand connection, usually . If all on board okey, try reball it, but you need test points under nand.

  4. 2 участника(ов) поблагодарили cooperlonely за его сообщение:

    BadGoose (19.08.2015), d42k11 (18.08.2015)

  5. #4
    Elite Member Аватар для FARIC
    Регистрация
    13.09.2009
    Адрес
    СПБ.Хаба.Абакан.Тула
    Сообщений
    2,606
    Спасибо
    685
    Благодарностей: 1,564 : 525
    Цитата Сообщение от nuakakisho Посмотреть сообщение
    по питалову смотри.или и2с
    Он наш слэнг прям вот сразу так понял !))

  6. 8 участника(ов) поблагодарили FARIC за его сообщение:

    asaka (18.08.2015), BadGoose (19.08.2015), cooperlonely (18.08.2015), jurik18 (20.08.2015), kir2 (06.03.2021), Polovoi (18.08.2015), verminer (19.08.2015), ремсотник (08.10.2015)

  7. #5
    Senior Member
    Регистрация
    18.09.2014
    Адрес
    Нижний Новгород
    Сообщений
    978
    Спасибо
    295
    Благодарностей: 445 : 215
    try to measure resistance (to gnd) or voltage i2c0 i2c1 line
    probe points PP0301 302 304 305.
    Some bad components can distort i2c signal
    this is first of all

    second, you need to desolder u0604
    And try to test CPU connection
    you can measure solder points resistance to gnd.
    If R= infinity in some data line, you have open circuit and reball CPU is needed

  8. 5 участника(ов) поблагодарили console-maste за его сообщение:

    BadGoose (19.08.2015), cooperlonely (18.08.2015), d42k11 (18.08.2015), kir2 (21.11.2015), verminer (19.08.2015)

  9. #6
    Member
    Регистрация
    28.08.2013
    Адрес
    New Jersey
    Сообщений
    120
    Спасибо
    28
    Благодарностей: 4 : 4
    I tested the resistant on the battery connector the R between gnd copper on the board and + of the battery connector is 0.958m. The R between 2 connector terminal of the battery is 220k and counting means going up i had black probe of the meter on gnd terminal of battery connector and red probe of meter on + terminal of the battery connector and if i interchange the meter prob i get different R readings 13.56k

  10. Спасибо сказали:

    verminer (19.08.2015)

  11. #7
    Member
    Регистрация
    28.08.2013
    Адрес
    New Jersey
    Сообщений
    120
    Спасибо
    28
    Благодарностей: 4 : 4
    will the pp0601,0602,0603 help me any to test the cpu and nand connection ok or not? the pp0601 is on page 8

  12. #8
    Senior Member
    Регистрация
    18.09.2014
    Адрес
    Нижний Новгород
    Сообщений
    978
    Спасибо
    295
    Благодарностей: 445 : 215
    by the way, problem is very hard, if its nand-cpu problem. if you are not hardcore specialist - forget it

    I2c problem -more simple. Try this
    test i2c first. find that pp on the boardview! and measure

    Battery coonector is nothing matter, forget it

    for example, similar problem iph5 4005 error
    In some cases simply solved by desoldering compass chip.
    BUT in some cases this is cpu problem
    And in some cases -nand problem

  13. 4 участника(ов) поблагодарили console-maste за его сообщение:

    BadGoose (19.08.2015), d42k11 (19.08.2015), kir2 (21.11.2015), ремсотник (08.10.2015)

  14. #9
    Member
    Регистрация
    28.08.2013
    Адрес
    New Jersey
    Сообщений
    120
    Спасибо
    28
    Благодарностей: 4 : 4
    Цитата Сообщение от console-maste Посмотреть сообщение
    by the way, problem is very hard, if its nand-cpu problem. if you are not hardcore specialist - forget it

    I2c problem -more simple. Try this
    test i2c first. find that pp on the boardview! and measure

    Battery coonector is nothing matter, forget it

    for example, similar problem iph5 4005 error
    In some cases simply solved by desoldering compass chip.
    BUT in some cases this is cpu problem
    And in some cases -nand problem
    All the PP are I2C point? on the boardview? Also the numbers next to each trace they refer to page number where the trace occurs right>? IF yes they are off by 1 page number like for example if it says 7 it occurs on page 8 am I right about please correct me also much much thanks for help me

  15. #10
    Member
    Регистрация
    30.07.2013
    Адрес
    Казань
    Сообщений
    282
    Спасибо
    224
    Благодарностей: 251 : 124
    Блог
    2
    d42k11
    I2C section located on page 5

  16. 3 участника(ов) поблагодарили BadGoose за его сообщение:

    cooperlonely (19.08.2015), d42k11 (20.08.2015), maxluq (19.08.2015)

  17. #11
    Member
    Регистрация
    28.08.2013
    Адрес
    New Jersey
    Сообщений
    120
    Спасибо
    28
    Благодарностей: 4 : 4
    Thank you for all the help . I dont know what happened but After i removed emi sheild from cpu and tested to make sure phone boots up. and i connected to computer the phone went through restore process and everything went back to normal I dont know what changed thing that made phone work again and restore. any explanation will help me solve this problem faster in future.

    thanks again guys

  18. #12
    Member
    Регистрация
    30.07.2013
    Адрес
    Казань
    Сообщений
    282
    Спасибо
    224
    Благодарностей: 251 : 124
    Блог
    2
    Noone can say exactly about the reasons. Maybe it was poor solder joints under CPU/RAM/NAND/etc due to factory defect or shock. What you did is a kind of so-called "reflowing" but because of the compound under the chips and without following thermal profile is a lottery. So you were lucky this time. You should better test the phone because it can fail again soon.

  19. 3 участника(ов) поблагодарили BadGoose за его сообщение:

    cooperlonely (20.08.2015), maxluq (20.08.2015), mikhail777 (16.05.2018)

Похожие темы

  1. Ответов: 3
    Последний ответ: 11.12.2011, 17:26
  2. Iphone 3g error 1013
    от unders в разделе iPhone
    Ответов: 1
    Последний ответ: 19.10.2011, 22:35
  3. Iphone 4g imei error
    от rk2fxx в разделе iPhone
    Ответов: 22
    Последний ответ: 09.04.2011, 00:02
  4. iphone 3gs error 9
    от unders в разделе iPhone
    Ответов: 3
    Последний ответ: 26.06.2010, 16:12
  5. Iphone Oшибка "firmware error string"
    от SE-2008 в разделе iPhone
    Ответов: 12
    Последний ответ: 24.04.2009, 17:56

Ваши права

  • Вы не можете создавать новые темы
  • Вы не можете отвечать в темах
  • Вы не можете прикреплять вложения
  • Вы не можете редактировать свои сообщения
  •  
  Рейтинг@Mail.ru