BortNick
02.07.2011, 12:43
имеется N81-3 RM-223 попытке включения только бзык и около минуты горит подсветка дисплея.
Со слов владельца: телефон шили дома. прошился, но с какой-то ошибкой. некоторое время работал(чему я не верю), потом просто выключился. носили в ремонт "наколенникам". после попал ко мне.
Check
Booting CMT...
Handling device: [Cyclone Team], [Cyclone Bootloader]
Handling device: [Cyclone Team], [Cyclone Box]
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 21B0010F76760058E6D602AF904968B62F799DD5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9A28E119033B91D14D22838C86D0D53C
CMT_BOOT_ROM_CRC: A8C1D671
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, 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]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000022, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5
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: E70C21157D5AB5AF61AAD376910751FB06D6E9FD
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...
Flashing
Handling device: [Cyclone Team], [Cyclone Bootloader]
Handling device: [Cyclone Team], [Cyclone Box]
Processing pre flash tasks...
Pre flash tasks finished, continuing...
Processing RM223_22.0.002_prd.C00 (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 21B0010F76760058E6D602AF904968B62F799DD5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9A28E119033B91D14D22838C86D0D53C
CMT_BOOT_ROM_CRC: A8C1D671
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
RM223_22.0.002_prd.C00, Type: Flash Image, Algo: BB5, XSR 1.5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, 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]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000022, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5
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: E70C21157D5AB5AF61AAD376910751FB06D6E9FD
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Partitioning...
Partitioning OK
Started group flash erase
EraseArea[0,CMT]: 0x00040000-0x00082FFF, ONENAND
EraseArea[0,CMT]: 0x00083400-0x0087FFFF, ONENAND
EraseArea[0,CMT]: 0x00B80000-0x05F7FFFF, ONENAND
Erase Partition (CMT)
Erase Partition (CMT)
Waiting 320s for erasure finish...
Erase taken 1.63s
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 PASUBTOC Certificate...
Writing CMT PAPUBKEYS Certificate...
Writing CMT SOS*UPDAPP Certificate...
Writing CMT SOS*DSP0 Certificate...
Writing CMT SOS*ISASW Certificate...
Writing CMT SOS*CORE Certificate...
Writing CMT SOS+ROFS Certificate...
Programming Status OK!
All blocks written OK! Time taken 69.578s
Flashing Speed: 5654,89 kBit/S
Restarting MCU...
Processing RM223_22.0.002_prd.C00 (APE)...
Processing RM223_22.0.002_prd_0501.V05 (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 21B0010F76760058E6D602AF904968B62F799DD5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9A28E119033B91D14D22838C86D0D53C
CMT_BOOT_ROM_CRC: A8C1D671
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
RM223_22.0.002_prd_0501.V05, Type: Flash Image, Algo: BB5, XSR 1.5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, 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]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000022, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5
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: E70C21157D5AB5AF61AAD376910751FB06D6E9FD
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x03730000-0x05F7FFFF, ONENAND
Waiting 320s for erasure finish...
Erase taken 0.453s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT SOS+ROFX Certificate...
Programming Status OK!
All blocks written OK! Time taken 52.328s
Flashing Speed: 5427,24 kBit/S
Restarting MCU...
Processing RM223_22.0.002_prd_0501.V05 (APE)...
Processing RM223_22.0.002_003_000_U02_uda.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 21B0010F76760058E6D602AF904968B62F799DD5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9A28E119033B91D14D22838C86D0D53C
CMT_BOOT_ROM_CRC: A8C1D671
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
RM223_22.0.002_003_000_U02_uda.fpsx, Type: Flash Image, Algo: BB5, XSR 1.5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, 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]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000022, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5
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: E70C21157D5AB5AF61AAD376910751FB06D6E9FD
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x05F80000-0x079DFFFF, ONENAND
Erase Certificate: SOS-USER (CMT)
Waiting 320s for erasure finish...
Erase taken 0.875s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 0.547s
Flashing Speed: 969,81 kBit/S
Restarting MCU...
Processing RM223_22.0.002_003_000_U02_uda.fpsx (APE)...
All images processed OK! Processing post flash tasks...
Post flash tasks finished!
Flashing successfully finished!
После прошивки Локала нет.
забекапил NPC. затер все циклоном. записал rm223_ENO_x_2007wk24v0.070_001.fpsx
появился Локал. на дисплее надпись rm223_ENO. в логе почему-то RM-179 N81 8Gb...
Восстановил IMEI, циклоном поправил SLD&SDD, SX4+PM.
SelfTests все проходит.
INF
MCU Version Vp 06wk41v34_RD
MCU Date 01-08-07
Product RM-179 (Nokia N81)
Manufacturer (c) Nokia
IMEI 356993013121914
Mastercode 4076604145
IMEI Spare 3A65990331219101
IMEI SV 3365990331219101F4000000
PPM rm223_ENO_x_2007wk24v0.070n256o256
PSN 0
PSD 0000000000000000
LPSN 0
WLAN MAC 001CD4347170
APE Test rm223_ENO_x_2007wk24v0.070
APE HW 256
APE ADSP 256
RETU 15
TAHVO 22
AHNE 11
HW rm223_ENO_x_2007wk24v0.070n256o256
PCI k rm223_ENO_x_2007wk24v0.070n256o256
UEM rm223_ENO_x_2007wk24v0.070n256o256
UPP rm223_ENO_x_2007wk24v0.070n256o256
RFIC 17141715k rm223_ENO_x_2007wk24v0.070n256o256
DSP bruce_06wk41v34k rm223_ENO_x_2007wk24v0.070n256o256
LCD rm223_ENO_x_2007wk24v0.070n256o256
BT rm223_ENO_x_2007wk24v0.070n256o256
ADSP Sw rm223_ENO_x_2007wk24v0.070n256o256
ADSP DevID rm223_ENO_x_2007wk24v0.070n256o256
ADSP RevID rm223_ENO_x_2007wk24v0.070n256o256
AEM rm223_ENO_x_2007wk24v0.070n256o256
Flip MCUSW rm223_ENO_x_2007wk24v0.070n256o256
Simlock Server SIMLOCK SERVER
Simlock Key 2440700000000000
Simlock Profile 8000000000000006
Simlock Key Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [1,2] State: OPENED Type: GID Data: FFFF
Simlock [1,3] State: OPENED Type: GID Data: FFFF
Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [2,2] State: OPENED Type: GID Data: FFFF
Simlock [2,3] State: OPENED Type: GID Data: FFFF
Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [3,2] State: OPENED Type: GID Data: FFFF
Simlock [3,3] State: OPENED Type: GID Data: FFFF
Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [4,2] State: OPENED Type: GID Data: FFFF
Simlock [4,3] State: OPENED Type: GID Data: FFFF
Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [5,2] State: OPENED Type: GID Data: FFFF
Simlock [5,3] State: OPENED Type: GID Data: FFFF
Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [6,2] State: OPENED Type: GID Data: FFFF
Simlock [6,3] State: OPENED Type: GID Data: FFFF
Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [7,2] State: OPENED Type: GID Data: FFFF
Simlock [7,3] State: OPENED Type: GID Data: FFFF
Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
SelfTest
Selftests to proceed: 38
Passed ST_TAHVOINT_TEST
Passed ST_UEM_CBUS_IF_TEST
Passed ST_EAR_DATA_LOOP_TEST
Passed ST_SIM_CLK_LOOP_TEST
Passed ST_SIM_IO_CTRL_LOOP_TEST
Passed ST_SIM_LOCK_TEST
Passed ST_SECURITY_TEST
Passed ST_PWR_KEY_TEST
Passed ST_CURRENT_CONS_TEST
Passed ST_BACKUP_BATT_TEST
Passed ST_SLEEPCLK_FREQ_TEST
Passed ST_VIBRA_TEST
Passed ST_RADIO_TEST
Passed ST_HOOKINT_TEST
Passed ST_BTEMP_TEST
Passed ST_INTERNAL_ANTENNA_TEST
Passed ST_EXT_DEVICE_TEST
Passed ST_CDSP_RF_BB_IF_TEST
Passed ST_CDSP_RF_SUPPLY_TEST
Passed ST_CDSP_TX_IQ_TEST
Passed ST_CDSP_TXC_DATA_TEST
Passed ST_CDSP_PWR_DETECTOR_BIAS_TEST
Passed ST_CDSP_RX_PLL_PHASE_LOCK_TEST
Passed ST_CDSP_TX_PLL_PHASE_LOCK_TEST
Passed ST_CDSP_WCDMA_TX_POWER_TEST
Passed ST_CDSP_RX_IQ_LOOP_BACK_TEST
Passed ST_CDSP_GSM_TX_POWER_TEST
Passed ST_KEYBOARD_STUCK_TEST
Passed ST_LPRF_IF_TEST
Passed ST_CAMERA_IF_TEST
Passed ST_SEC_CAMERA_IF_TEST
Passed ST_LPRF_AUDIO_LINES_TEST
Passed ST_MAIN_LCD_IF_TEST
Passed ST_BT_WAKEUP_TEST
Passed ST_WLAN_TEST
Passed ST_BT_WLAN_COEXISTENCE_TEST
Passed ST_BT_SLEEP_CLK_TEST
Passed ST_NAVISCROLL_TEST
Selftests done, Tests total: 38, Tests passed: 38, Tests not passed: 0
прошиваю SW 22.0.002 - получаю исходное состояние бзык и подсветка дисплея.
Снова стираю, ENO, NPC, SLD&SDD, SX4+PM = Local
Запускаю Феникс пытаюсь шить по USB - получаю ответ
ADL_LDR_DOWNGRADE_NOT_POSSIBLE_ERROR
и теперь становится понятным, почему он умирает после SW_22.0.002.
уважаемые, как быть? что делать?
Со слов владельца: телефон шили дома. прошился, но с какой-то ошибкой. некоторое время работал(чему я не верю), потом просто выключился. носили в ремонт "наколенникам". после попал ко мне.
Check
Booting CMT...
Handling device: [Cyclone Team], [Cyclone Bootloader]
Handling device: [Cyclone Team], [Cyclone Box]
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 21B0010F76760058E6D602AF904968B62F799DD5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9A28E119033B91D14D22838C86D0D53C
CMT_BOOT_ROM_CRC: A8C1D671
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, 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]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000022, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5
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: E70C21157D5AB5AF61AAD376910751FB06D6E9FD
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...
Flashing
Handling device: [Cyclone Team], [Cyclone Bootloader]
Handling device: [Cyclone Team], [Cyclone Box]
Processing pre flash tasks...
Pre flash tasks finished, continuing...
Processing RM223_22.0.002_prd.C00 (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 21B0010F76760058E6D602AF904968B62F799DD5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9A28E119033B91D14D22838C86D0D53C
CMT_BOOT_ROM_CRC: A8C1D671
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
RM223_22.0.002_prd.C00, Type: Flash Image, Algo: BB5, XSR 1.5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, 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]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000022, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5
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: E70C21157D5AB5AF61AAD376910751FB06D6E9FD
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Partitioning...
Partitioning OK
Started group flash erase
EraseArea[0,CMT]: 0x00040000-0x00082FFF, ONENAND
EraseArea[0,CMT]: 0x00083400-0x0087FFFF, ONENAND
EraseArea[0,CMT]: 0x00B80000-0x05F7FFFF, ONENAND
Erase Partition (CMT)
Erase Partition (CMT)
Waiting 320s for erasure finish...
Erase taken 1.63s
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 PASUBTOC Certificate...
Writing CMT PAPUBKEYS Certificate...
Writing CMT SOS*UPDAPP Certificate...
Writing CMT SOS*DSP0 Certificate...
Writing CMT SOS*ISASW Certificate...
Writing CMT SOS*CORE Certificate...
Writing CMT SOS+ROFS Certificate...
Programming Status OK!
All blocks written OK! Time taken 69.578s
Flashing Speed: 5654,89 kBit/S
Restarting MCU...
Processing RM223_22.0.002_prd.C00 (APE)...
Processing RM223_22.0.002_prd_0501.V05 (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 21B0010F76760058E6D602AF904968B62F799DD5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9A28E119033B91D14D22838C86D0D53C
CMT_BOOT_ROM_CRC: A8C1D671
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
RM223_22.0.002_prd_0501.V05, Type: Flash Image, Algo: BB5, XSR 1.5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, 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]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000022, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5
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: E70C21157D5AB5AF61AAD376910751FB06D6E9FD
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x03730000-0x05F7FFFF, ONENAND
Waiting 320s for erasure finish...
Erase taken 0.453s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT SOS+ROFX Certificate...
Programming Status OK!
All blocks written OK! Time taken 52.328s
Flashing Speed: 5427,24 kBit/S
Restarting MCU...
Processing RM223_22.0.002_prd_0501.V05 (APE)...
Processing RM223_22.0.002_003_000_U02_uda.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101021103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 21B0010F76760058E6D602AF904968B62F799DD5
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9A28E119033B91D14D22838C86D0D53C
CMT_BOOT_ROM_CRC: A8C1D671
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
RM223_22.0.002_003_000_U02_uda.fpsx, Type: Flash Image, Algo: BB5, XSR 1.5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, 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]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000022, Samsung, ONENAND
Requested Algorithm: XSR 1.5 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.10.48.1, Algo: XSR 1.5
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: E70C21157D5AB5AF61AAD376910751FB06D6E9FD
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x05F80000-0x079DFFFF, ONENAND
Erase Certificate: SOS-USER (CMT)
Waiting 320s for erasure finish...
Erase taken 0.875s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 0.547s
Flashing Speed: 969,81 kBit/S
Restarting MCU...
Processing RM223_22.0.002_003_000_U02_uda.fpsx (APE)...
All images processed OK! Processing post flash tasks...
Post flash tasks finished!
Flashing successfully finished!
После прошивки Локала нет.
забекапил NPC. затер все циклоном. записал rm223_ENO_x_2007wk24v0.070_001.fpsx
появился Локал. на дисплее надпись rm223_ENO. в логе почему-то RM-179 N81 8Gb...
Восстановил IMEI, циклоном поправил SLD&SDD, SX4+PM.
SelfTests все проходит.
INF
MCU Version Vp 06wk41v34_RD
MCU Date 01-08-07
Product RM-179 (Nokia N81)
Manufacturer (c) Nokia
IMEI 356993013121914
Mastercode 4076604145
IMEI Spare 3A65990331219101
IMEI SV 3365990331219101F4000000
PPM rm223_ENO_x_2007wk24v0.070n256o256
PSN 0
PSD 0000000000000000
LPSN 0
WLAN MAC 001CD4347170
APE Test rm223_ENO_x_2007wk24v0.070
APE HW 256
APE ADSP 256
RETU 15
TAHVO 22
AHNE 11
HW rm223_ENO_x_2007wk24v0.070n256o256
PCI k rm223_ENO_x_2007wk24v0.070n256o256
UEM rm223_ENO_x_2007wk24v0.070n256o256
UPP rm223_ENO_x_2007wk24v0.070n256o256
RFIC 17141715k rm223_ENO_x_2007wk24v0.070n256o256
DSP bruce_06wk41v34k rm223_ENO_x_2007wk24v0.070n256o256
LCD rm223_ENO_x_2007wk24v0.070n256o256
BT rm223_ENO_x_2007wk24v0.070n256o256
ADSP Sw rm223_ENO_x_2007wk24v0.070n256o256
ADSP DevID rm223_ENO_x_2007wk24v0.070n256o256
ADSP RevID rm223_ENO_x_2007wk24v0.070n256o256
AEM rm223_ENO_x_2007wk24v0.070n256o256
Flip MCUSW rm223_ENO_x_2007wk24v0.070n256o256
Simlock Server SIMLOCK SERVER
Simlock Key 2440700000000000
Simlock Profile 8000000000000006
Simlock Key Cnt 0
Simlock FBUS Cnt 0
Simlock [1,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [1,2] State: OPENED Type: GID Data: FFFF
Simlock [1,3] State: OPENED Type: GID Data: FFFF
Simlock [1,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [1,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [2,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [2,2] State: OPENED Type: GID Data: FFFF
Simlock [2,3] State: OPENED Type: GID Data: FFFF
Simlock [2,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [2,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [3,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [3,2] State: OPENED Type: GID Data: FFFF
Simlock [3,3] State: OPENED Type: GID Data: FFFF
Simlock [3,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [3,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [4,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [4,2] State: OPENED Type: GID Data: FFFF
Simlock [4,3] State: OPENED Type: GID Data: FFFF
Simlock [4,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [4,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [5,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [5,2] State: OPENED Type: GID Data: FFFF
Simlock [5,3] State: OPENED Type: GID Data: FFFF
Simlock [5,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [5,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [6,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [6,2] State: OPENED Type: GID Data: FFFF
Simlock [6,3] State: OPENED Type: GID Data: FFFF
Simlock [6,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [6,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [7,1] State: OPENED Type: MCC-MNC Data: FFFFFF
Simlock [7,2] State: OPENED Type: GID Data: FFFF
Simlock [7,3] State: OPENED Type: GID Data: FFFF
Simlock [7,4] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
Simlock [7,5] State: OPENED Type: IMSI Data: FFFFFFFFFFFFFFFF
SelfTest
Selftests to proceed: 38
Passed ST_TAHVOINT_TEST
Passed ST_UEM_CBUS_IF_TEST
Passed ST_EAR_DATA_LOOP_TEST
Passed ST_SIM_CLK_LOOP_TEST
Passed ST_SIM_IO_CTRL_LOOP_TEST
Passed ST_SIM_LOCK_TEST
Passed ST_SECURITY_TEST
Passed ST_PWR_KEY_TEST
Passed ST_CURRENT_CONS_TEST
Passed ST_BACKUP_BATT_TEST
Passed ST_SLEEPCLK_FREQ_TEST
Passed ST_VIBRA_TEST
Passed ST_RADIO_TEST
Passed ST_HOOKINT_TEST
Passed ST_BTEMP_TEST
Passed ST_INTERNAL_ANTENNA_TEST
Passed ST_EXT_DEVICE_TEST
Passed ST_CDSP_RF_BB_IF_TEST
Passed ST_CDSP_RF_SUPPLY_TEST
Passed ST_CDSP_TX_IQ_TEST
Passed ST_CDSP_TXC_DATA_TEST
Passed ST_CDSP_PWR_DETECTOR_BIAS_TEST
Passed ST_CDSP_RX_PLL_PHASE_LOCK_TEST
Passed ST_CDSP_TX_PLL_PHASE_LOCK_TEST
Passed ST_CDSP_WCDMA_TX_POWER_TEST
Passed ST_CDSP_RX_IQ_LOOP_BACK_TEST
Passed ST_CDSP_GSM_TX_POWER_TEST
Passed ST_KEYBOARD_STUCK_TEST
Passed ST_LPRF_IF_TEST
Passed ST_CAMERA_IF_TEST
Passed ST_SEC_CAMERA_IF_TEST
Passed ST_LPRF_AUDIO_LINES_TEST
Passed ST_MAIN_LCD_IF_TEST
Passed ST_BT_WAKEUP_TEST
Passed ST_WLAN_TEST
Passed ST_BT_WLAN_COEXISTENCE_TEST
Passed ST_BT_SLEEP_CLK_TEST
Passed ST_NAVISCROLL_TEST
Selftests done, Tests total: 38, Tests passed: 38, Tests not passed: 0
прошиваю SW 22.0.002 - получаю исходное состояние бзык и подсветка дисплея.
Снова стираю, ENO, NPC, SLD&SDD, SX4+PM = Local
Запускаю Феникс пытаюсь шить по USB - получаю ответ
ADL_LDR_DOWNGRADE_NOT_POSSIBLE_ERROR
и теперь становится понятным, почему он умирает после SW_22.0.002.
уважаемые, как быть? что делать?