Не восстанавливается Nokia 5230 после заливки RPL

dfyz · 15.08.2012, 18:13

Здраствуйте не получается восстановить 5230-RM588 .Стирал полностью флешь заливал последнюю версию прошивки, потом заливал заказанный RPL, потом пройдя SX-4 авторизацию заливал PM без 120 и 308 поля .Телефон включается до заствки Nokia и перезагружается прошу помочь с восстановлением данного ТА.

**kiv6666** · 15.08.2012, 18:40

А логи INF есть ?

dfyz · 15.08.2012, 18:51

Да извините вот прилогаю лог Ciclone Box при считывании инфы

Код HTML:

MCU Version	V ICPR72_11w16.1
MCU Date	28-07-11
Product		RM-588 (Nokia 5230)
Manufacturer	(c) Nokia
IMEI		35xxxxxxxxxxx
Mastercode	2024375122
IMEI Spare	3A35240414983400
IMEI SV		3335240414983420F5000000
PSN		MIK461812
Product Code	0585940
Basic Product Code	0582715
PSD		0000000000000000
LPSN		0
APE SW		V 51.6.002
APE Variant	V 51.6.002V 51.6.002 V 51.6.002 
APE Test		eno_version
APE HW		256
APE ADSP	256
RETU		16
TAHVO		22
AHNE		11
HW		0501
RFIC		17141716
DSP		ICPR72_11WK13
Failed to read info -> Failed to read SP info

Прошу помочь так как я новичек в этом деле.
Скажите какие логи надо выкласть и я выкладу из оборудования есть UFS-HWK , Ciclone Box , MX-KEY Dongle.

Dili · 15.08.2012, 22:37

Цитата:

Сообщение от dfyz

Здраствуйте не получается восстановить 5230-RM588 .Стирал полностью флешь заливал последнюю версию прошивки,

как ввел себя телефон, после это (до того как залили RPL) ?

Сохраните все бекапы
1.) Полное стирание телефона.
2.) Запись только SW = прошивка (очень желательно из полного Nokia SW Installer по INI)
телефон должен полностью включиться и работать несколько минут с IMEI 123456...
если этого не происходит, то: a.) телефон не полностью стёрся. b.) неисправно железо телефона

После это отпишитесь.

dfyz · 15.08.2012, 23:16

После полного стирания и заливки самой прошивки тел включается с IMEI-1234565... и работает но после проливки в него RPL он не хочет включатся только до заставки Nokia прошивки пробывал разные и из ЕХЕ инсталлера и с NaviFirm результат одинаковый.

Kostil · 16.08.2012, 11:37

Выложите какой нибудь более информативный лог от другого бокса. У вас после стирания, прошивки, записи RPL, до SX4 авторизации simlock нормально показывает. пройдите sx4 авторизацию с файлом который выложил. Вы на сервере Uo5oq покупали RPL?

dfyz · 16.08.2012, 15:26

Да покупал на сервере .
Вот лог UFS

Цитата:

APE Core: V 51.0.002
APE Var : V 51.0.002V 51.0.002 V 51.0.002
APE ENO : eno_version
Product : Nokia 5230
Prd.Code: 0585940
Bpr.Code: 0582715
Mod.Code:
Prod.Sn : MIK461812
HW Vers : 0501
APE HW : 256
APE Adsp: 256
EM VILMA: 16
EM BETTY: 22
RFIC Ver: 7141716
DSP Ver : ICPR72_11WK13
BT Id : 80 50 1B D6 86 2A
IMEI : 35ХХХХ-ХХ-ХХХХХХ-Х
SL Conf : 000-00-00000000000
SL Prof : 0000000000000000
SL Count: 00 00
Bad SL Structure BC: 00
Provider: Not Found

Вот еще лог от UFS

Цитата:

Insert USB Cable to Switched OFF Phone and Power ON
USB BOOT : 60,07 [Rm-588] [2.2.0.3]
CMT ASICID: 000000010000022600010006400C192101051103
EM 1 ID : 00000296
EM 2 ID : 00000B22
CMT PUBID : 1740001356950052D46B53C59EA161353A3E64F6
CMT MODE : 00
CMT HASH : 479C6DDE3942E12C429C1D6ADED80371
CMT ROMID : 4B9B75103E691FF8
CMT 2ND Bt: RAPIDOv11_2nd.fg, Ver: 11.34.0
CMT 2ND Bt: SILO OK
CMT RMID0 : 00000000-00000000
CMT MCID0 : FFFF0000-00000000
CMT FLID0 : 00EC0040-00000231, Sam OneNAND-2G
CMT RQALG : XSR 1.6
CMT 2ND Boot OK
CMT ALGO : RAPIDOv11_XSR17_alg.fg, Ver: 11.34.0
CMT KSIG0 : 7DC72D3FDC552426A4479BC820097D304CFB6C15
CMT ALG Boot OK
PASUBTOC : PA_SIMLOC30
Rebooting Mobile

**kiv6666** · 16.08.2012, 15:46

по логу юпса нечего не поймешь. Нужен лог МХ или циклона. Одно видно что сим лок не прописан

dfyz · 16.08.2012, 16:32

Вот полный лог от Ciclone Box
От прошивки до заливки PM через SX-4 авторизацию

Код HTML:

Initializing FBUS...
All initialized - Ready to work
Booting CMT...
CMT_SYSTEM_ASIC_ID:	000000010000022600010006400C192101051103
CMT_EM_ASIC_ID:		00000296
CMT_EM_ASIC_ID:		00000B22
CMT_PUBLIC_ID:		1740001356950052D46B53C59EA161353A3E64F6
CMT_ASIC_MODE_ID:	00
CMT_ROOT_KEY_HASH:	479C6DDE3942E12C429C1D6ADED80371
CMT_BOOT_ROM_CRC:	4B9B7510
CMT_SECURE_ROM_CRC:	3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.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]: 0xFFFFFFFF00000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000231, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, 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
Warning: PAPUBKEYS Hash Missing!
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...
Processing pre flash tasks...
Backing up RPL...
RPL Creation started...
Processing CMT Part...
Proceeding with Recovery Mode...
Booting CMT...
CMT_SYSTEM_ASIC_ID:	000000010000022600010006400C192101051103
CMT_EM_ASIC_ID:		00000296
CMT_EM_ASIC_ID:		00000B22
CMT_PUBLIC_ID:		1740001356950052D46B53C59EA161353A3E64F6
CMT_ASIC_MODE_ID:	00
CMT_ROOT_KEY_HASH:	479C6DDE3942E12C429C1D6ADED80371
CMT_BOOT_ROM_CRC:	4B9B7510
CMT_SECURE_ROM_CRC:	3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.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]: 0xFFFFFFFF00000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000231, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, 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
Warning: PAPUBKEYS Hash Missing!
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
NPC Backup stored in "1740001356950052D46B53C59EA161353A3E64F6_16.08.2012_161953.NPC.CMT.crt"
Recovery Mode Failed, storing Certificates Only
Booting CMT...
CMT_SYSTEM_ASIC_ID:	000000010000022600010006400C192101051103
CMT_EM_ASIC_ID:		00000296
CMT_EM_ASIC_ID:		00000B22
CMT_PUBLIC_ID:		1740001356950052D46B53C59EA161353A3E64F6
CMT_ASIC_MODE_ID:	00
CMT_ROOT_KEY_HASH:	479C6DDE3942E12C429C1D6ADED80371
CMT_BOOT_ROM_CRC:	4B9B7510
CMT_SECURE_ROM_CRC:	3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.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]: 0xFFFFFFFF00000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000231, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, 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
Warning: PAPUBKEYS Hash Missing!
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
CMT NPC Not Found
CMT CCC Not Found
CMT HWC Not Found
CMT VARIANT Not Found
CMT PARTNERC Not Found
Restoring from Recovery Mode...
WARNING: Certificate not accepted, Probably TX2 Problem (check Adapter/Cable!)
FAILED to Restore from Recovery Mode. Possible reasons:
1. Not attached yellow TX2 Adapter
2. Using 5-pin Cable (not TX2 Enabled)
In either cases, check cable/adapter, and write NPC Certificate Manually using "Write Cert" and writing NPC Backup from "StoredFiles".
Restarting MCU...
RPL Saved OK
RPL backup thread finished, continuing...
Pre flash tasks finished, continuing...
Processing RM-588_51.0.002_prd.core.C00 (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID:	000000010000022600010006400C192101051103
CMT_EM_ASIC_ID:		00000296
CMT_EM_ASIC_ID:		00000B22
CMT_PUBLIC_ID:		1740001356950052D46B53C59EA161353A3E64F6
CMT_ASIC_MODE_ID:	00
CMT_ROOT_KEY_HASH:	479C6DDE3942E12C429C1D6ADED80371
CMT_BOOT_ROM_CRC:	4B9B7510
CMT_SECURE_ROM_CRC:	3E691FF8
CMT Ready!
RM-588_51.0.002_prd.core.C00, Type: Flash Image, Algo: XSR 1.6, BB5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.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]: 0x00EC004000000231, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR17_alg.fg, Type: Algorithm, Rev: 512.12.8.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-0x00082FFF, ONENAND
EraseArea[0,CMT]: 0x00083400-0x003FFFFF, ONENAND
EraseArea[0,CMT]: 0x00400000-0x007FFFFF, ONENAND
EraseArea[0,CMT]: 0x00800000-0x00D5FFFF, ONENAND
EraseArea[0,CMT]: 0x00D60000-0x09E5FFFF, ONENAND
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...
WARNING: CMT PAPUBKEYS Hash is Empty, writing first found PAPUBKEYS
Writing CMT PAPUBKEYS Certificate...
Writing CMT SOS*UPDAPP Certificate...
Writing CMT SOS*ENO Certificate...
Writing CMT SOS*DSP0 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 169.219s
Flashing Speed: 5287,45 kBit/S
Restarting MCU...
Processing RM-588_51.0.002_prd.core.C00 (APE)...
Processing RM-588_51.0.002_prd.rofs2.V05 (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID:	000000010000022600010006400C192101051103
CMT_EM_ASIC_ID:		00000296
CMT_EM_ASIC_ID:		00000B22
CMT_PUBLIC_ID:		1740001356950052D46B53C59EA161353A3E64F6
CMT_ASIC_MODE_ID:	00
CMT_ROOT_KEY_HASH:	479C6DDE3942E12C429C1D6ADED80371
CMT_BOOT_ROM_CRC:	4B9B7510
CMT_SECURE_ROM_CRC:	3E691FF8
CMT Ready!
RM-588_51.0.002_prd.rofs2.V05, Type: Flash Image, Algo: XSR 1.6, BB5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.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]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000231, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR17_alg.fg, Type: Algorithm, Rev: 512.12.8.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: 7DC72D3FDC552426A4479BC820097D304CFB6C15
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x06FE0000-0x0915FFFF, ONENAND
Waiting 320s for erasure finish...
Erase taken 0.250s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT SOS+ROFS2 Certificate...
Programming Status OK!
All blocks written OK! Time taken 43.312s
Flashing Speed: 5191,48 kBit/S
Restarting MCU...
Processing RM-588_51.0.002_prd.rofs2.V05 (APE)...
Processing RM-588_51.0.002_C01_prd.rofs3.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID:	000000010000022600010006400C192101051103
CMT_EM_ASIC_ID:		00000296
CMT_EM_ASIC_ID:		00000B22
CMT_PUBLIC_ID:		1740001356950052D46B53C59EA161353A3E64F6
CMT_ASIC_MODE_ID:	00
CMT_ROOT_KEY_HASH:	479C6DDE3942E12C429C1D6ADED80371
CMT_BOOT_ROM_CRC:	4B9B7510
CMT_SECURE_ROM_CRC:	3E691FF8
CMT Ready!
RM-588_51.0.002_C01_prd.rofs3.fpsx, Type: Flash Image, Algo: XSR 1.6, BB5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.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]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000231, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR17_alg.fg, Type: Algorithm, Rev: 512.12.8.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: 7DC72D3FDC552426A4479BC820097D304CFB6C15
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x09160000-0x09E5FFFF, ONENAND
Waiting 320s for erasure finish...
Erase taken 0.156s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT SOS+ROFS3 Certificate...
Programming Status OK!
All blocks written OK! Time taken 10.47s
Flashing Speed: 5142,00 kBit/S
Restarting MCU...
Processing RM-588_51.0.002_C01_prd.rofs3.fpsx (APE)...
Processing RM-588_51.0.002_000_001_U001.uda.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID:	000000010000022600010006400C192101051103
CMT_EM_ASIC_ID:		00000296
CMT_EM_ASIC_ID:		00000B22
CMT_PUBLIC_ID:		1740001356950052D46B53C59EA161353A3E64F6
CMT_ASIC_MODE_ID:	00
CMT_ROOT_KEY_HASH:	479C6DDE3942E12C429C1D6ADED80371
CMT_BOOT_ROM_CRC:	4B9B7510
CMT_SECURE_ROM_CRC:	3E691FF8
CMT Ready!
RM-588_51.0.002_000_001_U001.uda.fpsx, Type: Flash Image, Algo: XSR 1.6, BB5
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.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]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000231, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR17_alg.fg, Type: Algorithm, Rev: 512.12.8.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: 7DC72D3FDC552426A4479BC820097D304CFB6C15
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x09E60000-0x0F47FFFF, ONENAND
Waiting 320s for erasure finish...
Erase taken 0.547s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 31.328s
Flashing Speed: 4970,86 kBit/S
Restarting MCU...
Processing RM-588_51.0.002_000_001_U001.uda.fpsx (APE)...
All images processed OK! Processing post flash tasks...
Setting Factory Defaults...
Factory defaults OK
Reading info...
MCU Version	V ICPR72_11w16.1
MCU Date	28-07-11
Product		RM-588 (Nokia 5230)
Manufacturer	(c) Nokia
IMEI		12345610654321?
IMEI Spare	1A32541660452301
IMEI SV		1332541660452321F5000000
PSN		0
PSD		0000000000000000
LPSN		0
APE SW		V 51.0.002
APE Variant	V 51.0.002V 51.0.002 V 51.0.002 
APE Test		eno_version
APE HW		256
APE ADSP	256
RETU		16
TAHVO		22
AHNE		11
RFIC		17141716
DSP		ICPR72_11WK13
Failed to read info -> Failed to read SP info
Read info thread finished, continuing...
Post flash tasks finished!
Flashing successfully finished!
Skipping RPL decryption...
Parsing decrypted RPL...
Processing FBUS Part...
Writing Simlock...
Handling as SL3 Simlock Data
Handling as SIMLOCK2 Format
Reading Security Block...
Security block OK and saved to "RM-588_12345610654321_16.08.2012_162750.SecurityBlock.PM"
15 Digits NCK Found
Simlock ACCEPTED OK !
Writing Superdongle key...
Superdongle Key ACCEPTED OK !
Writing CMLA key...
CMLA Key NOT ACCEPTED !
Writing WMDRM PD Data...
WMDRM PD Data NOT ACCEPTED !
Processing FLASHBUS Part...
Booting CMT...
CMT_SYSTEM_ASIC_ID:	000000010000022600010006400C192101051103
CMT_EM_ASIC_ID:		00000296
CMT_EM_ASIC_ID:		00000B22
CMT_PUBLIC_ID:		1740001356950052D46B53C59EA161353A3E64F6
CMT_ASIC_MODE_ID:	00
CMT_ROOT_KEY_HASH:	479C6DDE3942E12C429C1D6ADED80371
CMT_BOOT_ROM_CRC:	4B9B7510
CMT_SECURE_ROM_CRC:	3E691FF8
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.12.8.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]: 0x0400000000000000, Unknown, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x00EC004000000231, Samsung, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported
RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.12.8.0, 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: 7DC72D3FDC552426A4479BC820097D304CFB6C15
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
CMT NPC Erased
CMT NPC Written
CMT HWC Erased
CMT HWC Written
CMT CCC Erased
CMT CCC Written
Restarting MCU...
Write RPL Finished!
SX4 Authorization / SD Repair Procedure Started....
"1740001356950052D46B53C59EA161353A3E64F6.C00084A8" Exists, That is good...
MCU Version	V ICPR72_11w16.1
MCU Date	28-07-11
Product		RM-588 (Nokia 5230)
Manufacturer	(c) Nokia
IMEI		353424041894309
Mastercode	2024375122
Reading Security Block...
Security block OK and saved to "RM-588_353424041894309_16.08.2012_162806.SecurityBlock.PM"
SX4 Status: Not authorized (74)
Started mutual authenthication with card...
Receiving Phone Seed 1...
Phone Seed 1 Received
Sending calculated Data 1, and expecting Seed 2...
Calculated Data 1 accepted, Phone Seed 2 Received
Superdongle Key is probably CORRUPTED, Writing custom keys...
Received SD Keys from box, writing to phone...
Superdongle Key ACCEPTED OK !
SX4 Status: Not authorized (74)
Started mutual authenthication with card...
Receiving Phone Seed 1...
Phone Seed 1 Received
Sending calculated Data 1, and expecting Seed 2...
Calculated Data 1 accepted, Phone Seed 2 Received
Sending calculated Data 2
Calculated Data 2 sent, Checking Authorization Status again
Authorization successfully finished!
Looking for Virgin PM In Database...
Found, writing...
[1,0] Written, Length: 114 bytes, Status: OK
[1,2] Written, Length: 98 bytes, Status: OK
[1,4] Written, Length: 110 bytes, Status: OK
[1,6] Written, Length: 98 bytes, Status: OK
[1,8] Written, Length: 110 bytes, Status: OK
[1,13] Written, Length: 98 bytes, Status: OK
[1,16] Written, Length: 98 bytes, Status: OK
[1,18] Written, Length: 98 bytes, Status: OK
[1,20] Written, Length: 98 bytes, Status: OK
[1,22] Written, Length: 16 bytes, Status: OK
[1,23] Written, Length: 4 bytes, Status: OK
[1,24] Written, Length: 84 bytes, Status: OK
[1,25] Written, Length: 4 bytes, Status: OK
[1,26] Written, Length: 110 bytes, Status: OK
[1,28] Written, Length: 98 bytes, Status: OK
[1,29] Written, Length: 10 bytes, Status: OK
[1,31] Written, Length: 98 bytes, Status: OK
[1,33] Written, Length: 36 bytes, Status: OK
[1,34] Written, Length: 80 bytes, Status: OK
[1,35] Written, Length: 16 bytes, Status: OK
[1,37] Written, Length: 4 bytes, Status: OK
[1,39] Written, Length: 36 bytes, Status: OK
[1,44] Written, Length: 182 bytes, Status: OK
[1,45] Written, Length: 182 bytes, Status: OK
[2,0] Written, Length: 448 bytes, Status: OK
[309,0] Written, Length: 4 bytes, Status: OK
[309,1] Written, Length: 2 bytes, Status: OK
[309,2] Written, Length: 12 bytes, Status: OK
[309,4] Written, Length: 12 bytes, Status: OK
[309,5] Written, Length: 12 bytes, Status: OK
[309,7] Written, Length: 12 bytes, Status: OK
[309,8] Written, Length: 12 bytes, Status: OK
[309,17] Written, Length: 12 bytes, Status: OK
Write PM Finished, Record written OK: 33, Record written NOT OK: 0

dfyz · 16.08.2012, 17:02

Вот еще позже после проливки PM через SX-4 ауторизацию

Код HTML:

SX4 Status: Authorized
[1,0] Written, Length: 114 bytes, Status: OK
[1,2] Written, Length: 98 bytes, Status: OK
[1,4] Written, Length: 110 bytes, Status: OK
[1,6] Written, Length: 98 bytes, Status: OK
[1,8] Written, Length: 110 bytes, Status: OK
[1,13] Written, Length: 98 bytes, Status: OK
[1,16] Written, Length: 98 bytes, Status: OK
[1,18] Written, Length: 98 bytes, Status: OK
[1,20] Written, Length: 98 bytes, Status: OK
[1,22] Written, Length: 16 bytes, Status: OK
[1,23] Written, Length: 4 bytes, Status: OK
[1,24] Written, Length: 84 bytes, Status: OK
[1,25] Written, Length: 4 bytes, Status: OK
[1,26] Written, Length: 110 bytes, Status: OK
[1,28] Written, Length: 98 bytes, Status: OK
[1,29] Written, Length: 10 bytes, Status: OK
[1,31] Written, Length: 98 bytes, Status: OK
[1,33] Written, Length: 36 bytes, Status: OK
[1,34] Written, Length: 80 bytes, Status: OK
[1,35] Written, Length: 16 bytes, Status: OK
[1,37] Written, Length: 4 bytes, Status: OK
[1,39] Written, Length: 36 bytes, Status: OK
[1,44] Written, Length: 182 bytes, Status: OK
[1,45] Written, Length: 182 bytes, Status: OK
[2,0] Written, Length: 448 bytes, Status: OK
[4,3] Written, Length: 10 bytes, Status: OK
[4,4] Written, Length: 8 bytes, Status: OK
[4,5] Written, Length: 8 bytes, Status: OK
[4,9] Written, Length: 5 bytes, Status: OK
[8,0] Written, Length: 2 bytes, Status: OK
[8,1] Written, Length: 16 bytes, Status: OK
[8,2] Written, Length: 16 bytes, Status: OK
[8,3] Written, Length: 128 bytes, Status: OK
[8,4] Written, Length: 128 bytes, Status: OK
[8,7] Written, Length: 4 bytes, Status: OK
[8,8] Written, Length: 8 bytes, Status: OK
[8,9] Written, Length: 8 bytes, Status: OK
[8,10] Written, Length: 24 bytes, Status: OK
[11,0] Written, Length: 4 bytes, Status: OK
[11,1] Written, Length: 4 bytes, Status: OK
[11,2] Written, Length: 4 bytes, Status: OK
[11,3] Written, Length: 4 bytes, Status: OK
[11,4] Written, Length: 1062 bytes, Status: OK
[12,0] Written, Length: 102 bytes, Status: OK
[31,4] Written, Length: 20 bytes, Status: OK
[44,0] Written, Length: 1 bytes, Status: OK
[50,0] Written, Length: 2 bytes, Status: OK
[54,0] Written, Length: 2 bytes, Status: OK
[96,0] Written, Length: 2 bytes, Status: OK
[96,1] Written, Length: 20 bytes, Status: OK
[107,0] Written, Length: 21 bytes, Status: OK
[107,1] Written, Length: 79 bytes, Status: OK
[107,2] Written, Length: 79 bytes, Status: OK
[107,3] Written, Length: 70 bytes, Status: OK
[107,25] Written, Length: 132 bytes, Status: OK
[107,26] Written, Length: 12 bytes, Status: OK
[117,5] Written, Length: 10 bytes, Status: OK
[117,6] Written, Length: 8 bytes, Status: OK
[117,8] Written, Length: 42 bytes, Status: OK
[153,0] Written, Length: 68 bytes, Status: OK
[153,1] Written, Length: 68 bytes, Status: OK
[153,2] Written, Length: 68 bytes, Status: OK
[153,3] Written, Length: 68 bytes, Status: OK
[153,4] Written, Length: 68 bytes, Status: OK
[153,5] Written, Length: 68 bytes, Status: OK
[153,6] Written, Length: 68 bytes, Status: OK
[193,2] Written, Length: 8 bytes, Status: OK
[193,3] Written, Length: 32 bytes, Status: OK
[193,4] Written, Length: 32 bytes, Status: OK
[193,9] Written, Length: 64 bytes, Status: OK
[208,1] Written, Length: 4 bytes, Status: OK
[217,0] Written, Length: 32 bytes, Status: OK
[291,0] Written, Length: 92 bytes, Status: OK
[309,0] Written, Length: 4 bytes, Status: OK
[309,1] Written, Length: 2 bytes, Status: OK
[309,2] Written, Length: 12 bytes, Status: OK
[309,4] Written, Length: 12 bytes, Status: OK
[309,5] Written, Length: 12 bytes, Status: OK
[309,7] Written, Length: 12 bytes, Status: OK
[309,8] Written, Length: 12 bytes, Status: OK
[309,17] Written, Length: 12 bytes, Status: OK
[322,0] Written, Length: 1 bytes, Status: OK
[329,0] Written, Length: 8392 bytes, Status: OK
[334,0] Written, Length: 1 bytes, Status: OK
[341,0] Written, Length: 1 bytes, Status: OK
[341,3] Written, Length: 4 bytes, Status: OK
[341,4] Written, Length: 4516 bytes, Status: OK
[354,0] Written, Length: 13 bytes, Status: OK
[356,0] Written, Length: 2 bytes, Status: OK
Write PM Finished, Record written OK: 89, Record written NOT OK: 0
MCU Version	V ICPR72_11w16.1
MCU Date	28-07-11
Product		RM-588 (Nokia 5230)
Manufacturer	(c) Nokia
IMEI		35ХХХХХХХХХХХХХ
Mastercode	2024375122
IMEI Spare	3A35240414983400
IMEI SV		3335240414983420F5000000
PSN		MIK461812
Product Code	0585940
Basic Product Code	0582715
PSD		0000000000000000
LPSN		0
APE SW		V 51.0.002
APE Variant	V 51.0.002V 51.0.002 V 51.0.002 
APE Test		eno_version
APE HW		256
APE ADSP	256
RETU		16
TAHVO		22
AHNE		11
HW		0501
RFIC		17141716
DSP		ICPR72_11WK13
Failed to read info -> Failed to read SP info

**kiv6666** · 16.08.2012, 17:24

у тебя сим лок с RPL не востанавливается. Надо МХом стереть РМ

dfyz · 16.08.2012, 19:11

После полной процедуры с MX-KEY телефон включился все ОК спасибо всем за помощь.

15.08.2012, 18:13	#1
dfyz Junior Member Регистрация: 29.07.2012 Сообщений: 7 Вес репутации: 0	Не восстанавливается Nokia 5230 после заливки RPL Здраствуйте не получается восстановить 5230-RM588 .Стирал полностью флешь заливал последнюю версию прошивки, потом заливал заказанный RPL, потом пройдя SX-4 авторизацию заливал PM без 120 и 308 поля .Телефон включается до заствки Nokia и перезагружается прошу помочь с восстановлением данного ТА.

15.08.2012, 18:40	#2
kiv6666 Moderator Регистрация: 15.11.2011 Адрес: Haifa IL Сообщений: 1,369 Вес репутации: 695	Re: Не восстанавливается Nokia 5230 после заливки RPL А логи INF есть ?

15.08.2012, 18:51	#3
dfyz Junior Member Регистрация: 29.07.2012 Сообщений: 7 Вес репутации: 0	Re: Не восстанавливается Nokia 5230 после заливки RPL Да извините вот прилогаю лог Ciclone Box при считывании инфы Код HTML: MCU Version V ICPR72_11w16.1 MCU Date 28-07-11 Product RM-588 (Nokia 5230) Manufacturer (c) Nokia IMEI 35xxxxxxxxxxx Mastercode 2024375122 IMEI Spare 3A35240414983400 IMEI SV 3335240414983420F5000000 PSN MIK461812 Product Code 0585940 Basic Product Code 0582715 PSD 0000000000000000 LPSN 0 APE SW V 51.6.002 APE Variant V 51.6.002V 51.6.002 V 51.6.002 APE Test eno_version APE HW 256 APE ADSP 256 RETU 16 TAHVO 22 AHNE 11 HW 0501 RFIC 17141716 DSP ICPR72_11WK13 Failed to read info -> Failed to read SP info Прошу помочь так как я новичек в этом деле. Скажите какие логи надо выкласть и я выкладу из оборудования есть UFS-HWK , Ciclone Box , MX-KEY Dongle. Последний раз редактировалось dfyz; 15.08.2012 в 19:45.

15.08.2012, 23:16	#5
dfyz Junior Member Регистрация: 29.07.2012 Сообщений: 7 Вес репутации: 0	Re: Не восстанавливается Nokia 5230 после заливки RPL После полного стирания и заливки самой прошивки тел включается с IMEI-1234565... и работает но после проливки в него RPL он не хочет включатся только до заставки Nokia прошивки пробывал разные и из ЕХЕ инсталлера и с NaviFirm результат одинаковый.

16.08.2012, 15:46	#8
kiv6666 Moderator Регистрация: 15.11.2011 Адрес: Haifa IL Сообщений: 1,369 Вес репутации: 695	Re: Не восстанавливается Nokia 5230 после заливки RPL по логу юпса нечего не поймешь. Нужен лог МХ или циклона. Одно видно что сим лок не прописан

16.08.2012, 17:24	#11
kiv6666 Moderator Регистрация: 15.11.2011 Адрес: Haifa IL Сообщений: 1,369 Вес репутации: 695	Re: Не восстанавливается Nokia 5230 после заливки RPL у тебя сим лок с RPL не востанавливается. Надо МХом стереть РМ

16.08.2012, 19:11	#12
dfyz Junior Member Регистрация: 29.07.2012 Сообщений: 7 Вес репутации: 0	Re: Не восстанавливается Nokia 5230 после заливки RPL После полной процедуры с MX-KEY телефон включился все ОК спасибо всем за помощь.