Вход

Просмотр полной версии : С7-00 не включается.


chabrus
29.11.2011, 22:30
Предыстория такова: Телефон стал глючить и подтормаживать, почле чего хозяин удалил несколько установленных приложений, и телефон перестал включаться, просто бзикал.
Клиент решил что села АКБ, и подключил ТА к ЗУ, которое в свою очередь он подключил к китайскому преобразователю 12-220в.
Через некоторое время он снял ТА с зарядки, и после попытки включить он просто завис на белом дисплее.
До меня тело прошивали версией 022.003.

Прошил телефон той же версикй Best в реж ме dead usb. Ситуация не изменилась, нет локала и не прошли сбросы.
Затем узнал что это не последняя версия на сегодня, скачал и пролил тем же способом версию 025.007. На дисплее появился локал, и прошли все сбросы. Результат не изменился. ТА все так же висит на белом дисплее.
Заменил Gazoo на 100% рабочую, дальше копать не стал, решив сначала исключить софтовую проблемму на 100%.
Подцепил тело к Cyclone через Fbus и проверка сертификатов показало знакомое Sim Lock damaged:poz:
RPL пока заказывать не решился, поскольку телефон все таки не включается.
Затер тело при помощи Best и прошил последней версией, ничего не изменилось.
К сожалению большинство логов не сохранил, поскольку не думал что придется создавать тему на форуме.
Затер тело через Fbus интерфейс.
Лог cyclone:
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000030000022600010007600C192102031104
CMT_EM_ASIC_ID: 00000C35
CMT_EM_ASIC_ID: 00000C30
CMT_PUBLIC_ID: 27D00005BFA80344F6035905AAA941F74938BCA8
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 916F75217F32081248B15C38DFC8E81B
CMT_BOOT_ROM_CRC: E693EF0D
CMT_SECURE_ROM_CRC: AC22615B
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPUv11_2nd.fg, Type: 2nd Boot Loader, Rev: 768.11.24.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0000000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC006800000131, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0068 (Samsung), Size: 1024MBytes, VPP: Not Supported
RAPUv11_XSR17_alg.fg, Type: Algorithm, Rev: 768.11.24.0, Algo: XSR 1.6
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 95A68E9FA27B2BFA89EA204FC846EB73DEF1D93F
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
Erasing flash chip...
Started group flash erase
EraseArea[0,CMT]: 0x00000000-0x3FFFFFFF, ONENAND
Waiting 640s for erasure finish...
Erase taken 4.157s
Restarting MCU...
BB5 Full Erase Finished!

Лог прошивки тем же продуктом:

Scanning avaiable products...
Processing C:\Program Files\Nokia\Phoenix\Products\...
Found 17 products, Filtering BB5 Products - wait...
5 Products left after filtering. Ready.
Retrieving Variants for Product RM-675 - wait...
2 Variants Retrieved
Processing pre flash tasks...
Pre flash tasks finished, continuing...
Processing RM-675_025.007_79.92_prd.core.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000030000022600010007600C192102031104
CMT_EM_ASIC_ID: 00000C35
CMT_EM_ASIC_ID: 00000C30
CMT_PUBLIC_ID: 27D00005BFA80344F6035905AAA941F74938BCA8
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 916F75217F32081248B15C38DFC8E81B
CMT_BOOT_ROM_CRC: E693EF0D
CMT_SECURE_ROM_CRC: AC22615B
CMT Ready!
RM-675_025.007_79.92_prd.core.fpsx, Type: Flash Image, Algo: XSR 1.6, BB5
Searching for BootCode: DualLine 32Bit
RAPUv11_2nd.fg, Type: 2nd Boot Loader, Rev: 768.11.24.0, Algo: BB5
Flashbus Write baud set to 650Kbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0xFFFFFFFF00000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC006800000131, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0068 (Samsung), Size: 1024MBytes, VPP: Not Supported
RAPUv11_XSR17_alg.fg, Type: Algorithm, Rev: 768.11.24.0, Algo: XSR 1.6
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
Warning: PAPUBKEYS Hash Missing!
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Partitioning...
Partitioning OK
Started group flash erase
EraseArea[0,CMT]: 0x00040000-0x0007FFFF, ONENAND
EraseArea[0,CMT]: 0x000C0000-0x008BFFFF, ONENAND
EraseArea[0,CMT]: 0x00DC0000-0x0E97FFFF, ONENAND
EraseArea[0,CMT]: 0x2E100000-0x3E5FFFFF, ONENAND
Erase Partition (CMT)
Waiting 320s for erasure finish...
Erase taken 2.94s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT ADA Certificate...
Writing CMT KEYS Certificate...
Writing CMT PRIMAPP Certificate...
Writing CMT RAP3NAND Certificate...
Writing CMT SOS+PMML Certificate...
Writing CMT PASUBTOC Certificate...
WARNING: CMT PAPUBKEYS Hash is Empty, writing first found PAPUBKEYS
Writing CMT PAPUBKEYS Certificate...
Writing CMT GENIO_INIT Certificate...
Writing CMT SOS*UPDAPP Certificate...
Writing CMT SOS*DSP0 Certificate...
Writing CMT LDSP Certificate...
Writing CMT SOS*ISASW Certificate...
Writing CMT SOS+CORE Certificate...
Writing CMT SOS+ROFS1 Certificate...
Programming Status OK!
All blocks written OK! Time taken 139.250s
Flashing Speed: 7413,60 kBit/S
Restarting MCU...
Processing RM-675_025.007_79.92_prd.core.fpsx (APE)...
Processing RM-675_025.007_04.01_Russian_79.92_prd.rofs2.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000030000022600010007600C192102031104
CMT_EM_ASIC_ID: 00000C35
CMT_EM_ASIC_ID: 00000C30
CMT_PUBLIC_ID: 27D00005BFA80344F6035905AAA941F74938BCA8
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 916F75217F32081248B15C38DFC8E81B
CMT_BOOT_ROM_CRC: E693EF0D
CMT_SECURE_ROM_CRC: AC22615B
CMT Ready!
RM-675_025.007_04.01_Russian_79.92_prd.rofs2.fpsx, Type: Flash Image, Algo: XSR 1.6, BB5
Searching for BootCode: DualLine 32Bit
RAPUv11_2nd.fg, Type: 2nd Boot Loader, Rev: 768.11.24.0, Algo: BB5
Flashbus Write baud set to 650Kbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0000000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC006800000131, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0068 (Samsung), Size: 1024MBytes, VPP: Not Supported
RAPUv11_XSR17_alg.fg, Type: Algorithm, Rev: 768.11.24.0, Algo: XSR 1.6
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 95A68E9FA27B2BFA89EA204FC846EB73DEF1D93F
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x09F40000-0x0DA7FFFF, ONENAND
Waiting 320s for erasure finish...
Erase taken 0.266s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT SOS+ROFS2 Certificate...
Programming Status OK!
All blocks written OK! Time taken 52.735s
Flashing Speed: 7593,13 kBit/S
Restarting MCU...
Processing RM-675_025.007_04.01_Russian_79.92_prd.rofs2.fpsx (APE)...
Processing RM-675_025.007_00.01_79.92_prd.rofs3.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000030000022600010007600C192102031104
CMT_EM_ASIC_ID: 00000C35
CMT_EM_ASIC_ID: 00000C30
CMT_PUBLIC_ID: 27D00005BFA80344F6035905AAA941F74938BCA8
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 916F75217F32081248B15C38DFC8E81B
CMT_BOOT_ROM_CRC: E693EF0D
CMT_SECURE_ROM_CRC: AC22615B
CMT Ready!
RM-675_025.007_00.01_79.92_prd.rofs3.fpsx, Type: Flash Image, Algo: XSR 1.6, BB5
Searching for BootCode: DualLine 32Bit
RAPUv11_2nd.fg, Type: 2nd Boot Loader, Rev: 768.11.24.0, Algo: BB5
Flashbus Write baud set to 650Kbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0000000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC006800000131, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0068 (Samsung), Size: 1024MBytes, VPP: Not Supported
RAPUv11_XSR17_alg.fg, Type: Algorithm, Rev: 768.11.24.0, Algo: XSR 1.6
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 95A68E9FA27B2BFA89EA204FC846EB73DEF1D93F
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x0DA80000-0x0E97FFFF, ONENAND
Waiting 320s for erasure finish...
Erase taken 0.94s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT SOS+ROFS3 Certificate...
Programming Status OK!
All blocks written OK! Time taken 0.281s
Flashing Speed: 139,93 kBit/S
Restarting MCU...
Processing RM-675_025.007_00.01_79.92_prd.rofs3.fpsx (APE)...
Processing RM-675_025.007_U01.01_79.92.uda.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000030000022600010007600C192102031104
CMT_EM_ASIC_ID: 00000C35
CMT_EM_ASIC_ID: 00000C30
CMT_PUBLIC_ID: 27D00005BFA80344F6035905AAA941F74938BCA8
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 916F75217F32081248B15C38DFC8E81B
CMT_BOOT_ROM_CRC: E693EF0D
CMT_SECURE_ROM_CRC: AC22615B
CMT Ready!
RM-675_025.007_U01.01_79.92.uda.fpsx, Type: Flash Image, Algo: XSR 1.6, BB5
Searching for BootCode: DualLine 32Bit
RAPUv11_2nd.fg, Type: 2nd Boot Loader, Rev: 768.11.24.0, Algo: BB5
Flashbus Write baud set to 650Kbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0000000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC006800000131, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0068 (Samsung), Size: 1024MBytes, VPP: Not Supported
RAPUv11_XSR17_alg.fg, Type: Algorithm, Rev: 768.11.24.0, Algo: XSR 1.6
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 95A68E9FA27B2BFA89EA204FC846EB73DEF1D93F
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x0E980000-0x2E0FFFFF, ONENAND
Waiting 320s for erasure finish...
Erase taken 2.93s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 172.109s
Flashing Speed: 7258,60 kBit/S
Restarting MCU...
Processing RM-675_025.007_U01.01_79.92.uda.fpsx (APE)...
Processing rm675_ENO_v_0.0491_APEONLY.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000030000022600010007600C192102031104
CMT_EM_ASIC_ID: 00000C35
CMT_EM_ASIC_ID: 00000C30
CMT_PUBLIC_ID: 27D00005BFA80344F6035905AAA941F74938BCA8
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 916F75217F32081248B15C38DFC8E81B
CMT_BOOT_ROM_CRC: E693EF0D
CMT_SECURE_ROM_CRC: AC22615B
CMT Ready!
rm675_ENO_v_0.0491_APEONLY.fpsx, Type: Flash Image, Algo: XSR 1.6, BB5
Searching for BootCode: DualLine 32Bit
RAPUv11_2nd.fg, Type: 2nd Boot Loader, Rev: 768.11.24.0, Algo: BB5
Flashbus Write baud set to 650Kbits
Flashbus Read baud set to 98Kbits
Using NEW BB5 FLASHING PROTOCOL
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,CMT]: 0x0000000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC006800000131, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0068 (Samsung), Size: 1024MBytes, VPP: Not Supported
RAPUv11_XSR17_alg.fg, Type: Algorithm, Rev: 768.11.24.0, Algo: XSR 1.6
Initializing TurboCache...
TurboCache Loaded!
Writing CMT PASUBTOC Certificate...
Writing CMT ALG Certificate...
CMT Algorithm Ready!
Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Adding FUR Client (CMT, State: Ready)...
CMT FUR Ready!
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 95A68E9FA27B2BFA89EA204FC846EB73DEF1D93F
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Started group flash erase
EraseArea[0,CMT]: 0x008C0000-0x00DBFFFF, ONENAND
Waiting 320s for erasure finish...
Erase taken 0.47s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT SOS*ENO Certificate...
Programming Status OK!
All blocks written OK! Time taken 5.125s
Flashing Speed: 7095,77 kBit/S
Restarting MCU...
Processing rm675_ENO_v_0.0491_APEONLY.fpsx (APE)...
All images processed OK! Processing post flash tasks...
Setting Factory Defaults...
Factory defaults OK
Reading info...
MCU Version V 92_11w37
MCU Date 14-09-11
Product RM-675 (Nokia C7-00)
Manufacturer (c) Nokia
IMEI 12345610654321?
IMEI Spare 1A32541660452301
IMEI SV 1332541660452321F1000000
PSN 0
PSD 0000000000000000
LPSN 0
APE SW 025.007
APE Variant 025.007025.007.04.01025.007.00.01
APE Test rm675_ENO_v_0.0491
APE HW 256
APE ADSP 256
APE BT HCI Version 4 (rev. 0). LMP Version 4 (rev. 7455). Manufacturer 13.
RETU 35
TAHVO 00
AHNE 11
PCI o256qHDHCI Version 4 (rev. 0). LMP Version 4 (rev. 7455). Manufacturer 13.n256i025.007j("025.007025.007.04.01025.007.00.01krm675_ENO_v_0.04 91
UEM 256qHDHCI Version 4 (rev. 0). LMP Version 4 (rev. 7455). Manufacturer 13.n256i025.007j("025.007025.007.04.01025.007.00.01krm675_ENO_v_0.04 91
RFIC |Alli_4.3.4
DSP 92_11w36
LCD 256qHDHCI Version 4 (rev. 0). LMP Version 4 (rev. 7455). Manufacturer 13.n256i025.007j("025.007025.007.04.01025.007.00.01krm675_ENO_v_0.04 91Ґ025.007.U01.01
ADSP DevID 256qHDHCI Version 4 (rev. 0). LMP Version 4 (rev. 7455). Manufacturer 13.n256i025.007j("025.007025.007.04.01025.007.00.01krm675_ENO_v_0.04 91
ADSP RevID 256qHDHCI Version 4 (rev. 0). LMP Version 4 (rev. 7455). Manufacturer 13.n256i025.007j("025.007025.007.04.01025.007.00.01krm675_ENO_v_0.04 91
Failed to read info -> Failed to read SP info
Read info thread finished, continuing...
Post flash tasks finished!
Flashing successfully finished!

По идее телефон после этого должен включиться и запуститься, только с дефолтным имей, но он по прежнему висит на белом дисплее и не запускается.
Пролил Бестом сертификаты которые он автоматом сливает перед прошивкой,
Результат:

Checking StartUp data ...
-----------------------
SDD Key status : SDData is Ok

SimLock status : SimLock Damaged!!!!! :(
- > Do REPAIR SL if it SL2/SL phone, if SL3 - Help Only Backup Or RPL

Security status : Security is Ok
-----------------------

PA_SimLock Version :
PA_SL phone detected

Done!


Прошил тело бестом еще раз:

Core version : 1.30 Rev : 1.1

Selected FlashSettings :
Check FlashFiles, Please, wait...

Files Set for Flashing :
MCU : RM-675_025.007_79.92_prd.core.fpsx
PPM : RM-675_025.007_04.01_Russian_79.92_prd.rofs2.fpsx
PPM2 : RM-675_025.007_00.01_79.92_prd.rofs3.fpsx
CNT : RM-675_025.007_U01.01_79.92.uda.fpsx
APE : rm675_ENO_v_0.0491_APEONLY.fpsx
Flashing phone now...
Check files done...
-> SWversion check skipped : Dead mode selected
Dead Mode is Selected
Waiting for USB device...
--- Insert cable and charger or press phone's power button! ---
Connection opened successfully
Waiting for communication response...
[BB5 FLASH]: Bootrom Ok!
ASIC ID: 000000030000022600010007600C192102031104
CPU ID : RAPU v11 , Features : Dead-Test , USBRPL , FullUSB
EM0 ID: 00000C35
EM1 ID: 00000C30
PUBLIC ID: 27D00005BFA80344F6035905AAA941F74938BCA8
ASIC MODE ID: 00
ROOT KEY HASH: 916F75217F32081248B15C38DFC8E81B
ROM ID: E693EF0DAC22615B
Use RAPUv11_2nd.fg , Rev : 3.0 Ver : 11.34.0
Processing RAWLOADER...
FLIC : 006800EC
Req : XSR 1.6
Use RAPUv11_XSR17_alg.fg , Rev : 3.0 Ver : 11.34.0
Processing PASUBTOC ...
Processing ALG ...
Boot Done! :)
TIME : Boot time : 00:00:03
Reopening the connection...
Waiting for response: 30
Waiting for response: 29
ADL: Check mode
Select ASIC [C900]
PAPUBkeys : 95A68E9FA27B2BFA89EA204FC846EB73DEF1D93F
ADL: phone is in flash mode

Backup enabled, will read all certificates...
Reading NPC certificate...
IMEI : 355379043622892
Reading CCC certificate...
Reading HWC certificate...
Reading R&D certificate...
Reading VARIANT certificate...
Reading PARTNERC certificate...
Reading MDM_KEYS certificate...
Cert Read done!

NPC Certificate saved...
CCC Certificate saved...
HWC Certificate saved...

RPL saved : c:\InfinityBox\BEST\Backup\Cert\355379043622892_CR T_2nd.rpl

===Flashing [MCU]===
Erase : Processing RM-675_025.007_79.92_prd.core.fpsx
Partitioning....
Partitioning Ok...
Erasing....
Erasing Ok...
TIME : Erase time : 00:00:02
Write : Processing RM-675_025.007_79.92_prd.core.fpsx
CMT: Writing Hash CERT [ADA]
CMT: Writing Hash CERT [KEYS]
CMT: Writing Hash CERT [PRIMAPP]
CMT: Writing Hash CERT [RAP3NAND]
CMT: Writing Hash CERT [SOS+PMML]
CMT: Writing Hash CERT [PASUBTOC]
CMT: Writing Hash CERT [PAPUBKEYS]
CMT: Writing Hash CERT [GENIO_INIT]
CMT: Writing Hash CERT [SOS*UPDAPP]
CMT: Writing Hash CERT [SOS*DSP0]
CMT: Writing Hash CERT [LDSP]
CMT: Writing Hash CERT [SOS*ISASW]
CMT: Writing Hash CERT [SOS+CORE]
CMT: Writing Hash CERT [SOS+ROFS1]
Total writen 516 blocks
TIME : Write time : 00:00:14
MCU Write done
ADL: Request programm status
NAND status : 00000002 / 00000002 / 00000000

===Flashing [PPM]===
Erase : Processing RM-675_025.007_04.01_Russian_79.92_prd.rofs2.fpsx
Erasing....
Erasing Ok...
TIME : Erase time : 00:00:00
Write : Processing RM-675_025.007_04.01_Russian_79.92_prd.rofs2.fpsx
CMT: Writing Hash CERT [SOS+ROFS2]
Total writen 192 blocks
TIME : Write time : 00:00:05
PPM Write done
ADL: Request programm status
NAND status : 00000002 / 00000002 / 00000000

===Flashing [PPM2]===
Erase : Processing RM-675_025.007_00.01_79.92_prd.rofs3.fpsx
Erasing....
Erasing Ok...
TIME : Erase time : 00:00:00
Write : Processing RM-675_025.007_00.01_79.92_prd.rofs3.fpsx
CMT: Writing Hash CERT [SOS+ROFS3]
Total writen 2 blocks
TIME : Write time : 00:00:00
PPM Write done
ADL: Request programm status
NAND status : 00000002 / 00000002 / 00000000

===Flashing [CNT]===
Erase : Processing RM-675_025.007_U01.01_79.92.uda.fpsx
Erasing....
Erasing Ok...
TIME : Erase time : 00:00:02
Write : Processing RM-675_025.007_U01.01_79.92.uda.fpsx
Total writen 596 blocks
TIME : Write time : 00:00:20
CNT Write done
ADL: Request programm status
NAND status : 00000002 / 00000002 / 00000000

===Flashing [APE]===
Erase : Processing rm675_ENO_v_0.0491_APEONLY.fpsx
Erasing....
Erasing Ok...
TIME : Erase time : 00:00:00
Write : Processing rm675_ENO_v_0.0491_APEONLY.fpsx
CMT: Writing Hash CERT [SOS*ENO]
Total writen 19 blocks
TIME : Write time : 00:00:00
APE Write done
ADL: Request programm status
NAND status : 00000002 / 00000002 / 00000000

ADL: Close_Session
Content: 000300000000020000000200000000
ADL: Reboot

Flashing done!
Total flash time : 00:00:46
Reboot phone now...

Reading Phone Info....
Connected phone - Nokia C7-00
Software Info: V 92_11w37 14-09-11 RM-675 (c) Nokia
IMEI: 355379043622892
Ape Version: 025.007
Product code: 059D9Z9
Checking...
SimLock status : SimLock Damaged!!!!! :(
Security status : Security is Ok
Read Info Done!
Settings After Flash Defaults...
Error When resetting FullFactory :( ...
Error When resetting Product Tune :( ...
Error When resetting SW upgrade Default :( ...
AfterFlash operations done ;D
Done!

Elapsed: 00:01:22
Connect phone on selected interface...


Локал на дисплее появился, но сбросы не прошли. Ситуация с работоспособностью телефона не изменилась.
Если его затереть, то сбросы проходят.


И не понять, то ли тело так софтово убито, то ли из за перепада напряжения в СЗУ его так торкнуло.
Собственно мне непонятно вот что:
Если скажем в 6300 сбит SD то телефон не будет запускаться.
Должен ли запускаться С7-00 без Sim Lock?
Потому что по идее он должен при включении падать в contact servise, а я где то слышал что в этой модели телефона, contact servise не отображаетсяна дисплее.
И должен ли он включаться после стирания и прошивки, без сертификатов, как остальные телефоны?
И исходя из высшеописанного, есть ли смысл заказывать RPL в данный момент.

ЗЫ: прошу ногами сильно не пинать, просто эта модель только недавно вошла широкое распостранение в моем регионе, и потому достаточного опыта по ее ремонту еще не имею.

С уважением: Руслан.

J.M.
29.11.2011, 22:55
chabrus, а self test не делали ?

chabrus
29.11.2011, 23:38
Нет, по запарке не додумался.
Считал что раз проблема софтовая, то и тест не нужен.
Утром выложу.

uo5oq
30.11.2011, 00:08
Почти любой телефон Nokia полностью стёртый и затем полностью прописаный только SW, обязан полностью включаться и полностью работать некоторое время при IMEI 123456...
Эта модель точно должна включаться. Проверено лично.
Так что RPL вам заказывать точно рано.

yuraboss
30.11.2011, 00:28
Руслан проверь разъем Х2400 и его обвязку.
В этой модели, если этот разъем не подключить телефон висит на белом экране и не грузится.
В моем же случае была в обрыве группа контактов разъема Х2400

butum
30.11.2011, 08:04
Должен ли запускаться С7-00 без Sim Lock?
С уважением: Руслан.

Запускаться не будет. БУдет вырубаться при включении.

некоторое время при IMEI 123456...
Эта модель точно должна включаться. Проверено лично.
.
Только с IMEI 123456.... если IMEI родной - будет вырубаться при включении после надписи NOKIA

chabrus
02.12.2011, 12:25
В общем, немного приболел, потому на работу только что пришел.
Вот результат селф теста по Fbus интерфейс при помощи Cyclone.
Прошу обратить внимание на то, что цеплял голую плату, потому на некоторые тест можно не обращать внимания.

Selftests to proceed: 50
Passed ST_SLEEP_X_LOOP_TEST
Passed ST_UEM_CBUS_IF_TEST
Passed ST_EAR_DATA_LOOP_TEST
Passed ST_SIM_CLK_LOOP_TEST
Failed ST_SIM_LOCK_TEST
Passed ST_SECURITY_TEST
Passed ST_PWR_KEY_TEST
Failed ST_CURRENT_CONS_TEST
Failed ST_HOOKINT_TEST
Failed ST_BTEMP_TEST
Passed ST_KELVIN_BATVOLTAGE_TEST
Passed ST_KELVIN_VIBRA_TEST
Passed ST_KELVIN_CAPACITOR_TEST
Passed ST_KELVIN_MISC_TEST
Passed ST_KELVIN_AUDIO_TEST
Passed ST_KELVIN_XEAR_TEST
Failed ST_USB_CHARGING_TEST
Failed ST_DIGIMIC_TEST
Failed ST_LED_CONTROLLER_TEST
Failed ST_AUDIO_PLL_TEST
Failed ST_RAM_IF_TEST
Passed ST_CDSP_SLEEPCLOCK_FREQ_TEST
Passed ST_CDSP_RF_BB_IF_TEST
Passed ST_CDSP_STROBE_TEST
Passed ST_CDSP_DIGI_RXTX_IF_TEST
Passed ST_CDSP_RF_SUPPLY_TEST
Passed ST_CDSP_PA_ID_PIN_TEST
Passed ST_CDSP_WCDMA_TX_POWER_TEST
Passed ST_KEYBOARD_STUCK_TEST
Passed ST_LPRF_IF_TEST
Passed ST_CAMERA_IF_TEST
Failed ST_CAMERA_ACCELERATOR_TEST
Passed ST_SEC_CAMERA_IF_TEST
Failed ST_LED_FLASH_TEST
Failed ST_LPRF_AUDIO_LINES_TEST
Passed ST_MAIN_LCD_IF_TEST
Failed ST_TOUCH_TEST
Failed ST_TOUCH_IF_TEST
Failed ST_BT_WAKEUP_TEST
Passed ST_WLAN_TEST
Passed ST_MASS_MEMORY_IF_TEST
Passed ST_ACCEL_IF_TEST
Passed ST_VIBRA_TEST
Failed ST_USB_LOOP_TEST
Failed ST_MAGNETOMETER_TEST
Failed ST_USB_CHARGER_TEST
Failed ST_LED_FLASH_IF_TEST
Failed ST_NFC_TEST
Passed ST_NFC_ANTENNA_TEST
Passed ST_PROXIMITY_TEST
Selftests done, Tests total: 50, Tests passed: 30, Tests not passed: 20

Стер тем же интерфейсом тело, затем пролил отдельно ENO в режиме dead usb с Best, а затем прошил но уже без ENO. (Где то читал что такой порядок действий часто помогает в подобных случаях)
Телефон включился и запустился. Правда тач был отключен, и потому на выборе региона я отключил телефон.
После того как я его собрал, опять прежняя картина.
Обратил внимание на то, что корпус не родной, и плата немного кривая.
Чуть позже перекатаю весь, и попробую запустить. По результатам отпишусь.

Aristotelos
02.12.2011, 14:15
Руслан проверь разъем Х2400 и его обвязку.
В этой модели, если этот разъем не подключить телефон висит на белом экране и не грузится.
В моем же случае была в обрыве группа контактов разъема Х2400

Обрати внимание, может где-то обрыв, ведь корпус не родной и тел разбирали до тебя!

An144
02.12.2011, 16:46
Так как корпус не родной значить пред история телефона не совсем полна возможно был ударен и т.д. . И еще тел не включится если будет поврежден шлейф да и без него тоже не вкл .
Из этого следует что и self test нужно делать с застегнутым шлейфом .

chabrus
03.12.2011, 17:19
В общем сделал я этот телефон)
Причина оказалась в шлейфе. Прочистил Х2400, и пропаял разьем на шлейфе, телефон включился и работает. Только с дефолтным imei.
Заливать его не стал, все равно придется заказывать RPL.
Спасибо всем кто откликнулся.

Добавлю:

Сегодня прислали RPL. (Сам на серверах не заказываю, потому что имеют место проблемы с вебмани в нашем регионе. Обращаюсь к местнм друзьям, у кого они есть:) )

Will Write RPL keys now...
Check RPL file...
NPC Data found! (CMT)
CCC Data found! (CMT)
HWC Data found! (CMT)
SimLock Data found!
SimLock key found!
SuperDongle Key found!
CMLA key found!
WMDRM key found!
Dead Mode is Selected
Waiting for USB device...
--- Insert cable and charger or press phone's power button! ---
Connection opened successfully
Waiting for communication response...
[BB5 FLASH]: Bootrom Ok!
ASIC ID: 000000030000022600010007600C192102031104
CPU ID : RAPU v11 , Features : Dead-Test , USBRPL , FullUSB
EM0 ID: 00000C35
EM1 ID: 00000C30
PUBLIC ID: 27D00005BFA80344F6035905AAA941F74938BCA8
ASIC MODE ID: 00
ROOT KEY HASH: 916F75217F32081248B15C38DFC8E81B
ROM ID: E693EF0DAC22615B
Use RAPUv11_2nd.fg , Rev : 3.0 Ver : 11.34.0
Processing RAWLOADER...
FLIC : 006800EC
Req : XSR 1.6
Use RAPUv11_XSR17_alg.fg , Rev : 3.0 Ver : 11.34.0
Processing PASUBTOC ...
Processing ALG ...
Boot Done! :)
TIME : Boot time : 00:00:03
Reopening the connection...
Waiting for response: 30
Waiting for response: 29
ADL: Check mode
Select ASIC [C900]
PAPUBkeys : 95A68E9FA27B2BFA89EA204FC846EB73DEF1D93F
ADL: Preparing for write certificates...

Erase NPC... Ok
Writing NPC... Ok
Erase CCC... Ok
Writing CCC... Ok
Erase HWC... Ok
Writing HWC... Ok

ADL: Writing Flash certs done! :)

ADL: Close_Session
Content: 000300000000020000000200000000
ADL: Reboot
Wait, reconneting...

Writing SimLock Key... Ok!
Writing SimLock Data... Ok!
Writing Super Dongle Key... Ok!

SDD Key status : SD Data is Ok
SimLock status : SimLock is Ok
Security status : Security Damaged!!!!! :(

CMLA key sent... Ok
WMDRM_PD key sent... Ok

Done!

После чего пришлось восстанавливать security.

Processing Server SX4 Auth
Checking SDD key...
Check SD : Key is Ok
Operating mode is OK, no need change...
Connecting to server...
Connect to server Ok, checking
SX4 Server : Online, ver:1.04 , Infinity Team (c) 2011
SX4, processing Step #1
SX4, processing Step #2
SX4, processing Step #3
SX4 Result : Ok

Upload PM checked
Uploading RF/Battery tune to phone...
Using : RM-675.pm
Operating mode is OK, no need change...

Field 1
Record 0 write - Ok
Record 1 write - Ok
Record 2 write - Ok
Record 4 write - Ok
Record 6 write - Ok
Record 7 write - Ok
Record 8 write - Ok
Record 13 write - Ok
Record 15 write - Ok
Record 16 write - Ok
Record 17 write - Ok
Record 18 write - Ok
Record 19 write - Ok
Record 22 write - Ok
Record 26 write - Ok
Record 27 write - Ok
Record 28 write - Ok
Record 29 write - Ok
Record 30 write - Ok
Record 31 write - Ok
Record 32 write - Ok
Record 33 write - Ok
Record 35 write - Ok
Record 36 write - Ok
Record 38 write - Ok
Record 39 write - Ok
Record 40 write - Ok
Record 41 write - Ok
Record 43 write - Ok
Record 44 write - Ok
Record 45 write - Ok
Field 2
Record 0 write - Ok
Field 309
Record 0 write - Ok
Record 1 write - Ok
Record 2 write - Ok
Record 3 write - Ok
Record 4 write - Ok
Record 7 write - Ok
Record 17 write - Ok
Field 382
Record 1 write - Ok

Check ST_SECURITY now...
Security status : ST_SECURITY => OK

Done!

Elapsed: 00:00:01

Upload done

Checking StartUp data ...
-----------------------
SDD Key status : SDData is Ok
SimLock status : SimLock is Ok
Security status : Security is Ok
-----------------------

PA_SimLock Version :
PA_SL3 phone detected , SP_CODE_LEN : 15

Done!


Уже прошло около получаса, полет нормальный. Все функции работают кроме передней камеры.
Но это восстанавливать не планируется, учитывая то, сколько платит за работу жмот хозяин.
И еще, тоже вопрос: при восстановлении security используется запись 1 и 309 блоков РМ. А в моем случае сервер прописал еще 2 и 382 поля. Это обязательное действие при лечении подобной неисправности на новых моделях?