Битый Simlock на nokia N96.

[Jackson777]

Принесли из другой мастрерской не смогли прошить UFS пишет ошибки. Прошил Cyclon'ом но написал ошибку при считывании инфы. Подключил к MX-key он выдал вот Phone type: RM-247 (Nokia N96-1)
SW version: V ICPR72_09w13.2 19-05-09 RM-247 (c) Nokia
Imei plain: 35640602743000-7
Product code: 0543701
Battery voltage: 4370 mV, current: 185 mA
Language Pack:
- not available.

SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST failed!
SECURITY_TEST passed


SIMLOCK_DATA corrupted!
SIMLOCK_DATA corrupted!
Телефон SL2 можно восстановить без покупки RPL???

[flashmax]

Можно.
Читайте мануал к MX-key

[Jackson777]

Читал и пробовал делал по видео инструкциям. Но пока что то не получается. 3 дня назад купил его. Пока ещё не совсем разобрался.

[flashmax]

Ваши слова, прикрепите логами.

[GIZO]

поддержу пост номер 4.... дайте нам тоже взглянуть на ваши действия... и поясните как делали

[Jackson777]

Вот лог после Repair SD
MXKEY Serial: [FT SCR2000 0] - ********
Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Connection status: EHCI:HUB:HUB:USB 2.00 (Full-speed)
Driver: UFS2XX, ver: 3.8.14.0 , NTMP ver: 2.8.14.0
Module ver: 1.0.0.18624(06-08-2011), Library ver: 1.0.0.12274(06-08-2011)

Phone type: RM-247 (Nokia N96-1)
SW version: V ICPR72_09w13.2 19-05-09 RM-247 (c) Nokia

Using cached productData.
PUBLIC ID: 06B001054E710052D3DCA29B4ABD98253CE03063
PRIVATE ID: BEA5C0203DC99E6D0635EB4EB02C6584708189FB
Calculating SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host1, agent version 1.1 revision 0.7

Completed in 3.728 s

RPL saved to "C:\Program Files\3.5\data\backup\BB5_RM-247_356406027430007_SD.RPL"
Updating SUPERDONGLE_KEY ...OK
Потом записываю блоки 1 и 309 из того PM что у меня есть и всё равно ничего не изменяется. Может у меня файл PM не тот который нужен?

[flashmax]

Не путайте SLD (Sim Lock Data) c SD (Super Dongle).

[Jackson777]

Я делаю по инструкции как показано. Вот так называется инструкция.7210_SD_Sl_Repair. Это самое подходящее что нашёл.

[GIZO]

Я делаю по инструкции как показано. Вот так называется инструкция.7210_SD_Sl_Repair. Это самое подходящее что нашёл.

вам правильно сказали на посту номер 7, у вас супердонгл целый, вам надо править симлок!

SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST failed!
SECURITY_TEST passed


SIMLOCK_DATA corrupted!
SIMLOCK_DATA corrupted!

http://www.gsmforum.ru/attachment.php?attachmentid=92006&d=1279133388

[Jackson777]

Дайте пожалуйста нормальный файл PM для этого ТА.

[Jackson777]

Ткните пальцем как его восстановить? Я не нашёл этого.

[GIZO]

вот вам РМ : 30712

[GIZO]

как не нашли, на рисунке не видно ? там пошагово всё

[Jackson777]

Ну это та инструкция? я нелаю как там показывают но не так получается как там.

[GIZO]

вы что друг?! первый раз чтоли ТА делаете!

просто цепляйте ТА к боксу, делаете бс чек.. переходите на вкладку сервис-имеи секюрити-симлок-ставите галочку на репаир симлок-нажимаете на репаир сплок.

[Jackson777]

Вот что пишет после попытки залить PM SERVER->Served by MXKEY - BLADE X at host1, agent version 1.1 revision 0.7

MXKEY Serial: [FT SCR2000 0] - *******
Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Connection status: EHCI:HUB:HUB:USB 2.00 (Full-speed)
Driver: UFS2XX, ver: 3.8.14.0 , NTMP ver: 2.8.14.0
Module ver: 1.0.0.18624(06-08-2011), Library ver: 1.0.0.12274(06-08-2011)

Phone type: RM-247 (Nokia N96-1)
SW version: V ICPR72_09w13.2 19-05-09 RM-247 (c) Nokia

Using cached productData.
PUBLIC ID: 06B001054E710052D3DCA29B4ABD98253CE03063
PRIVATE ID: BEA5C0203DC99E6D0635EB4EB02C6584708189FB
Calculating using security server ...
Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Elapsed: 5.289 s (session timed out after 3 seconds)
Writing PM from Node ...
Section: 1
Warning: failed to write 1 - 0 (114 bytes)
Warning: failed to write 1 - 2 (98 bytes)
Warning: failed to write 1 - 4 (110 bytes)
Warning: failed to write 1 - 6 (98 bytes)
Warning: failed to write 1 - 8 (110 bytes)
Warning: failed to write 1 - 13 (98 bytes)
Warning: failed to write 1 - 16 (98 bytes)
Warning: failed to write 1 - 18 (98 bytes)
Warning: failed to write 1 - 20 (98 bytes)
Warning: failed to write 1 - 22 (16 bytes)
Warning: failed to write 1 - 23 (4 bytes)
Warning: failed to write 1 - 24 (84 bytes)
Warning: failed to write 1 - 25 (4 bytes)
Warning: failed to write 1 - 26 (110 bytes)
Warning: failed to write 1 - 28 (98 bytes)
Warning: failed to write 1 - 29 (10 bytes)
Warning: failed to write 1 - 31 (98 bytes)
Warning: failed to write 1 - 33 (36 bytes)
Warning: failed to write 1 - 34 (80 bytes)
Warning: failed to write 1 - 35 (16 bytes)
Warning: failed to write 1 - 37 (4 bytes)
Warning: failed to write 1 - 39 (36 bytes)
Warning: failed to write 1 - 44 (182 bytes)
Warning: failed to write 1 - 45 (182 bytes)
- 2 skipped
- 4 skipped
- 8 skipped
- 11 skipped
- 12 skipped
- 31 skipped
- 44 skipped
- 50 skipped
- 54 skipped
- 96 skipped
- 107 skipped
- 117 skipped
- 120 skipped
- 193 skipped
- 208 skipped
- 217 skipped
- 239 skipped
- 291 skipped
Section: 309
Warning: failed to write 309 - 0 (4 bytes)
Warning: failed to write 309 - 1 (2 bytes)
Warning: failed to write 309 - 2 (12 bytes)
Warning: failed to write 309 - 4 (12 bytes)
Warning: failed to write 309 - 5 (12 bytes)
Warning: failed to write 309 - 7 (12 bytes)
Warning: failed to write 309 - 8 (12 bytes)
Warning: failed to write 309 - 17 (12 bytes)
Warning: failed to write 309 - 22 (12 bytes)
- 313 skipped
- 322 skipped
- 329 skipped
- 334 skipped
- 341 skipped
- 354 skipped
Completed in 2.480 s
Нет не первый. Но MX-keem пользуюсь 4 дня.
Он спрашивает тогда обновить до SL3.

[GIZO]

зачем заливаете РМ если он вам пишет SECURITY_TEST passed, вы понимаете, что вам не РМ надо заливать, а симлок восстанавливать!

[Jackson777]

Понимаю. Так если нажать на репайр simlock то он обновит телефон до SL и потом если что то только RPL?

[GIZO]

вы что пишите ..я не понял чем вы занимаетесь.. некто нече не обновить ! делайте так как говорять! и закройте тему !

[Jackson777]

Спасибо. Сделал так и всё восстановил. Я просто думал что он обновит тел до SL3 просто там так пишет когда спрашивает да или нет.

[GIZO]

де нет там нечего такого...если так могли бы сл3 на сл2 переделать ..то тогда кому твой заказ рпл нужен))))

[flashmax]

Спасибо. Сделал так и всё восстановил. Я просто думал что он обновит тел до SL3 просто там так пишет когда спрашивает да или нет.

Телефон N96, SL3 не бывает.

[Jackson777]

Ясно. Всё восстановилось. После этого прошил включаю его но только кнопка навигации белым горит и всё.

[flashmax]

Как на допросе, надо инфу вытягивать!
Логи прошивки, и инфо выложите.

[Jackson777]

Завтра на работе буду выложу утром.

[Jackson777]

Вот лог прошивки Cyclona Handling device: [Cyclone Team], [Cyclone Bootloader]
Handling device: [Cyclone Team], [Cyclone Box]
Initializing box...
Box Firmware: Cyclone Nokia/Blackberry Application v01.66, (Jul 19 2011 16:55:18, gcc v4.3.3, RTOS V6.0.1), Type: Signed Production Application, (C) KarwosSoft 2011
Hardware Platform: Cyclone Classic Flasher Interface (c) 2008,2009 KarwosLabs
Box Serial Number: C0004DA0
HW Revision: B, Suitable for: Production, Case: First Plastic Case, MCU Manufacture Time: 2010, wk35
Initializing security card...
Card Serial Number: ******
Card Firmware Revision: 010A
Card is activated
Box is activated
Started box selftests procedure
USB Voltage 5,04v PASSED
MCU Voltage 3,29v PASSED
Core Voltage 1,80v PASSED
VBAT Voltage 1,12v PASSED
VBAT Voltage 4,91v PASSED
Box VPP disabled
VPP Voltage 0,02v PASSED
Internal Box VPP Enabled
VPP Voltage 4,97v PASSED
Box VPP disabled
VPP Voltage 0,02v PASSED
External Box VPP Enabled
VPP Voltage 0,04v FAILED - IGNORED - Probably power supply is not connected
Box VPP disabled
All box selftests passed!
Super DCT4 Activation: TRUE
Initializing FBUS...
All initialized - Ready to work
Sending User Abort Signal...
Sending User Abort Signal...
Sending User Abort Signal...
Sending User Abort Signal...
Sending User Abort Signal...
CBUS Request Error -> User abort
Failed to read info -> Phone not detected
Processing pre flash tasks...
Pre flash tasks finished, continuing...
Processing RM-247_30.033_prd.core.fpsx (CMT)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 008815D3
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: 6A7D96188A774730C8EEDC8CFA15D78BD9F7BC93
APE_ROOT_KEY_HASH: 0BBC4203E2D3B82504C75CB65E906A35
APE_BOOT_ROM_CRC: 137A9A3B
APE_SECURE_ROM_CRC: 33259D2C
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 06B001054E710052D3DCA29B4ABD98253CE03063
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
RM-247_30.033_prd.core.fpsx, Type: Flash Image, Algo: BB5, XSR 1.5, N8815 ALG STNFMS, BB5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5
Flashbus Write baud set to 51Kbits
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]: 0x00012C7E00006921, AMD, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
Searching for BootCode: DualLine 32Bit
FlashChip 0x00012C7E (AMD), Size: 16MBytes, VPP: 9V
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: AD7799ABC45695918C0B8E955FAD5FF12650E6AE
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Partitioning...
Partitioning OK
Started group flash erase
EraseArea[0,CMT]: 0x00080000-0x007A6EE9, NOR
EraseArea[0,CMT]: 0x00000000-0x0005FFFF, NOR
EraseArea[0,CMT]: 0x00880000-0x00EFFFFF, NOR
Waiting 320s for erasure finish...
Erase taken 36.956s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT NOLO Certificate...
Writing CMT KEYS Certificate...
Writing CMT PRIMAPP Certificate...
Writing CMT PASUBTOC Certificate...
Writing CMT PAPUBKEYS Certificate...
Writing CMT UPDAPP Certificate...
Writing CMT DSP0 Certificate...
Writing CMT MCUSW Certificate...
Programming Status OK!
All blocks written OK! Time taken 28.142s
Flashing Speed: 29012,56 kBit/S
Restarting MCU...
Processing RM-247_30.033_prd.core.fpsx (APE)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 008815D3
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: 6A7D96188A774730C8EEDC8CFA15D78BD9F7BC93
APE_ROOT_KEY_HASH: 0BBC4203E2D3B82504C75CB65E906A35
APE_BOOT_ROM_CRC: 137A9A3B
APE_SECURE_ROM_CRC: 33259D2C
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 06B001054E710052D3DCA29B4ABD98253CE03063
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
RM-247_30.033_prd.core.fpsx, Type: Flash Image, Algo: BB5, XSR 1.5, N8815 ALG STNFMS, BB5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.10.48.1, Algo: BB5
Flashbus Write baud set to 51Kbits
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]: 0x00012C7E00006921, AMD, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
Searching for BootCode: DualLine 32Bit
FlashChip 0x00012C7E (AMD), Size: 16MBytes, VPP: 9V
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: AD7799ABC45695918C0B8E955FAD5FF12650E6AE
Searching for BootCode: DualLine 32Bit
STn8815_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.14.0, Algo: BB5
Adding FUR Client (APE, State: Start)...
APE FUR Ready!
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,APE]: 0x0000000000000000, Unknown, RAM
FlashChip[0,APE]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,APE]: 0x002000B100000000, ST, ONENAND
Searching for BootCode: DualLine 32Bit
FlashChip 0x002000B1 (ST), Size: 8MBytes, VPP: 21V
STn8815_STNFMS_alg.fg, Type: Algorithm, Rev: 512.11.14.0, Algo: N8815 ALG STNFMS
Initializing TurboCache...
TurboCache Loaded!
Writing APE KEYS Certificate...
Writing APE PASUBTOC Certificate...
Writing APE ALG Certificate...
APE Algorithm Ready!
Adding FUR Client (APE, State: Ready)...
APE FUR Ready!
Box VPP disabled
Internal APE Phone VPP Enabled
PAPUBKEYS Hash for APE: AD7799ABC45695918C0B8E955FAD5FF12650E6AE
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Partitioning...
Partitioning OK
Started group flash erase
EraseArea[0,APE]: 0x00000000-0x0007FFFF, NAND
EraseArea[0,APE]: 0x00080000-0x000BFFFF, NAND
EraseArea[0,APE]: 0x000E0000-0x0045FFFF, NAND
EraseArea[0,APE]: 0x00840000-0x0A8FFFFF, NAND
Waiting 320s for erasure finish...
Erase taken 2.574s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing APE X-LOADER Certificate...
Writing APE KEYS Certificate...
Writing APE PRIMAAPP Certificate...
Writing APE SOS*UPDAPP Certificate...
Writing APE SOS+XZIP Certificate...
Writing APE PASUBTOC Certificate...
Writing APE PAPUBKEYS Certificate...
Writing APE SOS+CORE Certificate...
Writing APE SOS+ROFS1 Certificate...
Programming Status OK!
All blocks written OK! Time taken 129.887s
Flashing Speed: 6286,01 kBit/S
Restarting MCU...
Processing RM-247_30.033_005.1_prd.language.fpsx (CMT)...
Processing RM-247_30.033_005.1_prd.language.fpsx (APE)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 008815D3
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: 6A7D96188A774730C8EEDC8CFA15D78BD9F7BC93
APE_ROOT_KEY_HASH: 0BBC4203E2D3B82504C75CB65E906A35
APE_BOOT_ROM_CRC: 137A9A3B
APE_SECURE_ROM_CRC: 33259D2C
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 06B001054E710052D3DCA29B4ABD98253CE03063
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
RM-247_30.033_005.1_prd.language.fpsx, Type: Flash Image, Algo: N8815 ALG STNFMS, BB5, XSR 1.5, BB5
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 100Kbits
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]: 0x00012C7E00006921, AMD, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
Searching for BootCode: DualLine 32Bit
FlashChip 0x00012C7E (AMD), Size: 16MBytes, VPP: 9V
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: AD7799ABC45695918C0B8E955FAD5FF12650E6AE
Searching for BootCode: DualLine 32Bit
STn8815_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.14.0, Algo: BB5
Adding FUR Client (APE, State: Start)...
APE FUR Ready!
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,APE]: 0x0000000000000000, Unknown, RAM
FlashChip[0,APE]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,APE]: 0x002000B100000000, ST, ONENAND
Searching for BootCode: DualLine 32Bit
FlashChip 0x002000B1 (ST), Size: 8MBytes, VPP: 21V
STn8815_STNFMS_alg.fg, Type: Algorithm, Rev: 512.11.14.0, Algo: N8815 ALG STNFMS
Initializing TurboCache...
TurboCache Loaded!
Writing APE KEYS Certificate...
Writing APE PASUBTOC Certificate...
Writing APE ALG Certificate...
APE Algorithm Ready!
Adding FUR Client (APE, State: Ready)...
APE FUR Ready!
Box VPP disabled
Internal APE Phone VPP Enabled
PAPUBKEYS Hash for APE: AD7799ABC45695918C0B8E955FAD5FF12650E6AE
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,APE]: 0x07780000-0x099FFFFF, NAND
Waiting 320s for erasure finish...
Erase taken 0.546s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing APE SOS+ROFS2 Certificate...
Programming Status OK!
All blocks written OK! Time taken 37.441s
Flashing Speed: 5032,61 kBit/S
Restarting MCU...
Processing RM-247_30.033_098.1_prd.customer.fpsx (CMT)...
Processing RM-247_30.033_098.1_prd.customer.fpsx (APE)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 008815D3
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: 6A7D96188A774730C8EEDC8CFA15D78BD9F7BC93
APE_ROOT_KEY_HASH: 0BBC4203E2D3B82504C75CB65E906A35
APE_BOOT_ROM_CRC: 137A9A3B
APE_SECURE_ROM_CRC: 33259D2C
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 06B001054E710052D3DCA29B4ABD98253CE03063
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
RM-247_30.033_098.1_prd.customer.fpsx, Type: Flash Image, Algo: N8815 ALG STNFMS, BB5, XSR 1.5, BB5
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 100Kbits
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]: 0x00012C7E00006921, AMD, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
Searching for BootCode: DualLine 32Bit
FlashChip 0x00012C7E (AMD), Size: 16MBytes, VPP: 9V
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: AD7799ABC45695918C0B8E955FAD5FF12650E6AE
Searching for BootCode: DualLine 32Bit
STn8815_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.14.0, Algo: BB5
Adding FUR Client (APE, State: Start)...
APE FUR Ready!
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,APE]: 0x0000000000000000, Unknown, RAM
FlashChip[0,APE]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,APE]: 0x002000B100000000, ST, ONENAND
Searching for BootCode: DualLine 32Bit
FlashChip 0x002000B1 (ST), Size: 8MBytes, VPP: 21V
STn8815_STNFMS_alg.fg, Type: Algorithm, Rev: 512.11.14.0, Algo: N8815 ALG STNFMS
Initializing TurboCache...
TurboCache Loaded!
Writing APE KEYS Certificate...
Writing APE PASUBTOC Certificate...
Writing APE ALG Certificate...
APE Algorithm Ready!
Adding FUR Client (APE, State: Ready)...
APE FUR Ready!
Box VPP disabled
Internal APE Phone VPP Enabled
PAPUBKEYS Hash for APE: AD7799ABC45695918C0B8E955FAD5FF12650E6AE
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,APE]: 0x09A00000-0x0A8FFFFF, NAND
Waiting 320s for erasure finish...
Erase taken 0.265s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing APE SOS+ROFS3 Certificate...
Programming Status OK!
All blocks written OK! Time taken 0.109s
Flashing Speed: 404,33 kBit/S
Restarting MCU...
Processing RM-247_30.033_100.1_prd.uda.fpsx (CMT)...
Processing RM-247_30.033_100.1_prd.uda.fpsx (APE)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 008815D3
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: 6A7D96188A774730C8EEDC8CFA15D78BD9F7BC93
APE_ROOT_KEY_HASH: 0BBC4203E2D3B82504C75CB65E906A35
APE_BOOT_ROM_CRC: 137A9A3B
APE_SECURE_ROM_CRC: 33259D2C
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 06B001054E710052D3DCA29B4ABD98253CE03063
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
CMT_BOOT_ROM_CRC: 4B9B7510
CMT_SECURE_ROM_CRC: 3E691FF8
CMT Ready!
RM-247_30.033_100.1_prd.uda.fpsx, Type: Flash Image, Algo: N8815 ALG STNFMS, BB5, XSR 1.5, BB5
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 100Kbits
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]: 0x00012C7E00006921, AMD, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
Searching for BootCode: DualLine 32Bit
FlashChip 0x00012C7E (AMD), Size: 16MBytes, VPP: 9V
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: AD7799ABC45695918C0B8E955FAD5FF12650E6AE
Searching for BootCode: DualLine 32Bit
STn8815_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.14.0, Algo: BB5
Adding FUR Client (APE, State: Start)...
APE FUR Ready!
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,APE]: 0x0000000000000000, Unknown, RAM
FlashChip[0,APE]: 0xFFFF000000000000, Unknown, MMC
FlashChip[0,APE]: 0x002000B100000000, ST, ONENAND
Searching for BootCode: DualLine 32Bit
FlashChip 0x002000B1 (ST), Size: 8MBytes, VPP: 21V
STn8815_STNFMS_alg.fg, Type: Algorithm, Rev: 512.11.14.0, Algo: N8815 ALG STNFMS
Initializing TurboCache...
TurboCache Loaded!
Writing APE KEYS Certificate...
Writing APE PASUBTOC Certificate...
Writing APE ALG Certificate...
APE Algorithm Ready!
Adding FUR Client (APE, State: Ready)...
APE FUR Ready!
Box VPP disabled
Internal APE Phone VPP Enabled
PAPUBKEYS Hash for APE: AD7799ABC45695918C0B8E955FAD5FF12650E6AE
Flashbus Write baud set to 5.0Mbits
Started group flash erase
Erase Partition (APE)
Waiting 320s for erasure finish...
Erase taken 1.435s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 18.533s
Flashing Speed: 5816,69 kBit/S
Restarting MCU...
All images processed OK! Processing post flash tasks...
Setting Factory Defaults...
Factory defaults OK
Reading info...
MCU Version V ICPR72_09w13.2
MCU Date 19-05-09
Product RM-247 (Nokia N96)
Manufacturer (c) Nokia
IMEI 356406027430007
Mastercode 3610523010
IMEI Spare 3A65040672340000
IMEI SV 3365040672340000F8000000
PSN CRD980159
Product Code 0543722
Basic Product Code 0542934
PSD 0000000000000000
LPSN 0
WLAN MAC 0022FC98F018
RETU 15
TAHVO 22
AHNE 11
HW 1001
RFIC 17141715
DSP MC_4032_ICPR72_09w13
Simlock Server SIMLOCK SERVER
Simlock Key 2440700000000000
Simlock Profile 0000000000000000
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
Read info thread finished, continuing...
Post flash tasks finished!
Flashing successfully finished!
И он через раз видится и Циклоном и MX-key как только прошил так нормально видится а полежит немного и всё перестаёт видеться. При включении ТА загорается надпись нокиа горит около минуты и потом тёмный экран.

[GIZO]

делайте ерайз сохранив все возможные бэкапы, прошейте последней версией прошивки ,если после этого так будет то тогда капайте железо и не мучайте ТА софтом..