|
SE K310i странно не подключается к Cruiser. Почему?
Есть телефон SE K310i.
Аккумулятор полностью заряжен. Пдоключаю его к программатору, стартовая диагностик идет и в самом конце сбрасывает подключение. Первый раз такое вижу. И скорость менял и галочки микшировал - не помогает. Подсобите. С чем связано сие действие? System diagnostics passed. Version 12.02 ready! [ --- Attach to Phone --- ] Connecting via Fighter USB Cable... Powering on the phone... Baseband chip ID: 0x8040 Protocol version: 3.1 Baudrate = 460800Bd Booting via ROM... Sony Ericsson phone detected. Phone CID: 49 Phone color: Red Flash certificate: A1_DB2010_49_RED Trying Red CID49 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 1s Initializing phone hardware... Applet ID: 060206 1814 NPACXC125872_COMPACTPRO... Flash manufacturer: Intel Flash ID: 0x897E OTP Security Level: 1 (Retail) OTP CID: 49 Phone type (from GDFS): K310i CXC article: R4DA044 prgCXC1250466_GENERIC_DO CXC version: R4DA044 Language package: RUSSIA Operator: Sony Ericsson CDA article: CDA102576/8 CDA version: R5A Default article: cxc1250474 Default version: R4DA044 Phonecode: 0000 Terminating threads... All threads terminated. |
А телефон как себя ведёт ? Моргает ?
|
а если в normal boot попробывать
|
Нет телефон не моргает.
Но сразу при подключении издает какой-то глухой щелчок. В normal boot и пробую. Через recovery boot, CID 49 подключается. Но доступна только команда "replace certificate", а кнопка "repair certificate" не активна. |
не надо рековер труп получиш,по логу дело в железе, потребление тока смотри,воду смотри все смотри но не рековер. если щелчок то оконечник звук или стабилизатор .Выключается по перегрузке.
|
Так уже рековери сделал :) И почему труп? SE по софту надо еще постараться сделать трупом. Сколько их мутузил по софту всегда выводил на рабочее состояние. Мне главное, чтобы он загружался в normal boot.
А что такого в логе, что говорит о железе? Разбирал - телефон чистый, воды нет. Сделал так еще: подключил телефон к Блоку питанию, делаю включение, телефон у меня показывает потребление 80мА, но ничего на экране не зажигает, а продолжает висеть на потреблении в 80мА. Так и не пойму почему он так себя ведет. Продолжаем разговор. Кто еще что думает по этому поводу? |
полный лог прошивки кинь если не трудно, по первому логу ПО в норме, по этому и железо ,самое много это моргалик со снесеной FS
|
Цитата:
|
cruiser нормально отключает режим identify потому как нет error. можно для проверки на другом компе или шнур 4в1 подкинуть
|
Цитата:
На другом компе попробую. А вот шнур 4в1 - это который? |
Цитата:
|
Цитата:
|
Цитата:
|
Цитата:
|
При подключении через DCU-60 кабель по методике из help-а
How to repair phones killed by deadly software combination Description: This procedure repairs majority of CID49/51 DB2020 phones killed by deadly combination - unsuccesful unlock by other tool (SETool, etc.) followed by unlocking by codes in Cruiser. Prerequisities: · Ensure the phone battery is fully charged. · Ensure you have at least one server credit available. Repair procedure: · Attach the phone via DCU-60 or DCU-65 cable. Instead of holding the C key hold keys 2 & 5. Cruiser has to show "Booting via ROM..." Alternatively you may use a UC-10/Cruiser/Fighter cable. · Reflash phone by any main firmware flash file of suitable CID and color. · Reflash phone by any raw FS flash file of suitable CID and color. · Customize the FS. One server credit will be deducted. · Go to the Locks tab, press the Save security button and save the file to a folder of your choice. · Press the Unterminate button and wait until the operation finishes. · Now turn the phone off and disconect it from the cable. Подключаю телефон, после запроса Cruisera, удерживая клавиши 2 и 5. Но каждый раз как только компьютер находит новое устройство Generic Flash Device(драйвера для него брал тут: c:\Program Files\Cruiser\USB Flash Device Drivers\v1.1.0.12\), он тут же сбрасывает это устройство. После несколько таких попыток, один раз удалось сделать так, что Generic Flash Device не сбрасывается, но телефон все равно не подключается. Получаю такой лог. В котором один раз мелькнула строчка Unsupported flash certificate. Это значит, что у телефона испорчен сертификат, а соответственно - труп? System diagnostics passed. Version 12.10 ready! Do NOT connect the phone at this time! [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Time spent entering bootstrap: 10s Unsupported flash certificate Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! USB connection established. Baseband chip ID: 0x8040 Protocol version: 3.1 Booting via EROM... Trying Red CID52 flash applet... Sending applet prologue... Sending applet body... Time spent entering bootstrap: 0s Initializing phone hardware... Terminating threads... All threads terminated. [ --- Attach to Phone --- ] Connecting via SEMC DCU-60... Connect the phone while holding its C button! [ --- Detach Phone --- ] Terminating threads... Terminating threads... All threads terminated. All threads terminated. |
Похоже железо у него убитое, других причин не вижу.
|
| Текущее время: 09:02. Часовой пояс GMT +3. |
Powered by vBulletin®
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd. Перевод: zCarot