Reading info...

popovtv · 10.08.2012, 19:15

добрый день,UO5OQ заказал у вас рпл на е52,раньше он мне всегда помогал(всмысле не первый раз делаю),а щас не могу восстановить тело,делаю циклоном фул ераз вот что получил

Reading info...

MCU Version V ICPR82_11w16.3.11
MCU Date 29-03-12
Product RM-469 (Nokia E52)
Manufacturer (c) Nokia
IMEI 12345610654321?
IMEI Spare 1A32541660452301
IMEI SV 1332541660452351F7000000
PSN 0
PSD 0000000000000000
LPSN 0
APE SW 091.003
APE Variant 091.003091.003.05.01091.003.C00.01
APE Test v0.a091
APE HW 256
APE ADSP 256
RETU 40
TAHVO 00
AHNE 11
RFIC |Vapaus_5.1 | Mikki_1.1
DSP 11w52
Failed to read info -> Failed to read SP info
Read info thread finished, continuing...
Post flash tasks finished!
Flashing successfully finished!

анализ секюрити

Security block OK and saved to "RM-469_12345610654321_10.08.2012_200109.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
SIMLOCK SEFLTEST PASSED OK!
Step 2 : Testing SECURITY
SECURITY SEFLTEST PASSED OK!
Step 3 : Analyzing Security Block
"09D0000567D70344D473E345BD0646795015BC77.C0003F42" Exists, That is good...
Checking SUPERDONGLE...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking SIMLOCK...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking MCU&DSP TIMESTAMPS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking CMLA KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking ECC KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking DIV KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Analyze finished!

Step 1 : Testing SIMLOCK
SIMLOCK SEFLTEST PASSED OK!------вот это не могу сделать чтобы было в конце

записываю рпл и сразу анализ секюрити

MCU Version V ICPR82_11w16.3.11
MCU Date 29-03-12
Product RM-469 (Nokia E52)
Manufacturer (c) Nokia
IMEI 357880040507406
Mastercode 1222704463
Reading Security Block...
Security block OK and saved to "RM-469_357880040507406_10.08.2012_200311.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
-- SIMLOCK PROBLEM --

Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED!
To repair simlock area, Select Unlock method : "RPL CALCULATION",
And then click DIRECT UNLOCK. SL Area will be re-formatted.

-- SIMLOCK PROBLEM --
Step 2 : Testing SECURITY
-- SECURITY PROBLEM --

Phone have failed SECURITY Test, that means Superdongle Area is DAMAGED!
To repair it, simply slick "SX4 Authorization / SD Repair" button.
After SX4/SD Repair, don't forget to write PM file with fields 1,309 (if SW don't do this automatically)

Additionaly, Checking HWC/CCC Certs...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000030000022600010007600C192102011104
CMT_EM_ASIC_ID: 00001040
CMT_EM_ASIC_ID: 00001030
CMT_PUBLIC_ID: 09D0000567D70344D473E345BD0646795015BC77
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 25B977A055BE9B5DEC0C38A2A279C695
CMT_BOOT_ROM_CRC: 3E273BF6
CMT_SECURE_ROM_CRC: 37BE26FA
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPUv11_2nd.fg, Type: 2nd Boot Loader, Rev: 768.12.11.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]: 0x0020004000000031, ST, NOR
FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR
FlashChip[0,CMT]: 0x0020004000000031, ST, ONENAND
Requested Algorithm: XSR 1.6 (CMT)
Searching for BootCode: DualLine 32Bit
FlashChip 0x00200040 (ST), Size: 256MBytes, VPP: Not Supported
FlashChip 0x00200040 (ST), Size: 256MBytes, VPP: Not Supported
RAPUv11_XSR17_alg.fg, Type: Algorithm, Rev: 768.12.11.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: 85F252E351E225CAFC4DFBC8041EABD2823E3500
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
HWC Looks OK!
CCC Looks OK!
Restarting MCU...
-- SECURITY PROBLEM --
Step 3 : Analyzing Security Block
"09D0000567D70344D473E345BD0646795015BC77.C0003F42" Exists, That is good...
Checking SUPERDONGLE...
SUPERDONGLE FOUND AND CHECKSUM OK! PASSED!
Checking SIMLOCK...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking MCU&DSP TIMESTAMPS...
MCU&DSP TIMESTAMPS FOUND AND CHECKSUM OK! PASSED!
Checking CMLA KEYS...
CMLA KEYS FOUND AND CHECKSUM OK! PASSED!
Checking ECC KEYS...
ECC KEYS FOUND AND CHECKSUM OK! PASSED!
Checking DIV KEYS...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Analyze finished!

теперь sx4 запись пм

SX4 Authorization / SD Repair Procedure Started....
"09D0000567D70344D473E345BD0646795015BC77.C0003F42" Exists, That is good...
MCU Version V ICPR82_11w16.3.11
MCU Date 29-03-12
Product RM-469 (Nokia E52)
Manufacturer (c) Nokia
IMEI 357880040507406
Mastercode 1222704463
Reading Security Block...
Security block OK and saved to "RM-469_357880040507406_10.08.2012_200410.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
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: 10 bytes, Status: OK
[1,4] Written, Length: 110 bytes, Status: OK
[1,6] Written, Length: 10 bytes, Status: OK
[1,7] Written, Length: 214 bytes, Status: OK
[1,8] Written, Length: 110 bytes, Status: OK
[1,13] Written, Length: 10 bytes, Status: OK
[1,16] Written, Length: 208 bytes, Status: OK
[1,18] Written, Length: 208 bytes, Status: OK
[1,20] Written, Length: 208 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,26] Written, Length: 110 bytes, Status: OK
[1,28] Written, Length: 10 bytes, Status: OK
[1,29] Written, Length: 10 bytes, Status: OK
[1,31] Written, Length: 208 bytes, Status: OK
[1,33] Written, Length: 36 bytes, Status: OK
[1,34] Written, Length: 376 bytes, Status: OK
[1,35] Written, Length: 16 bytes, Status: OK
[1,39] Written, Length: 36 bytes, Status: OK
[1,40] Written, Length: 16 bytes, Status: OK
[1,41] Written, Length: 182 bytes, Status: OK
[1,42] Written, Length: 4 bytes, Status: OK
[1,43] 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: 2080 bytes, Status: OK
[4,1] Written, Length: 1020 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,6] Written, Length: 8 bytes, Status: OK
[4,9] Written, Length: 5 bytes, Status: OK
[4,28] Written, Length: 2 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,8] Written, Length: 8 bytes, Status: OK
[8,9] Written, Length: 8 bytes, Status: OK
[8,10] Written, Length: 32 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: 1058 bytes, Status: OK
[12,0] Written, Length: 102 bytes, Status: OK
[26,0] Written, Length: 16 bytes, Status: OK
[26,1] Written, Length: 68 bytes, Status: OK
[31,4] Written, Length: 18 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: 41 bytes, Status: OK
[107,1] Written, Length: 89 bytes, Status: OK
[107,2] Written, Length: 89 bytes, Status: OK
[107,3] Written, Length: 70 bytes, Status: OK
[107,25] Written, Length: 236 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: 104 bytes, Status: OK
[120,0] Written, Length: 944 bytes, Status: OK
[120,1] Written, Length: 160 bytes, Status: OK
[120,2] Written, Length: 130 bytes, Status: OK
[120,3] Written, Length: 112 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
[217,0] Written, Length: 32 bytes, Status: OK
[239,6] Written, Length: 218 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,3] Written, Length: 36 bytes, Status: OK
[309,4] Written, Length: 12 bytes, Status: OK
[309,7] Written, Length: 12 bytes, Status: OK
[309,17] Written, Length: 12 bytes, Status: OK
[313,0] Written, Length: 173 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: 4512 bytes, Status: OK
[354,0] Written, Length: 28 bytes, Status: OK
[356,0] Written, Length: 2 bytes, Status: OK
[356,1] Written, Length: 8 bytes, Status: OK
[360,0] Written, Length: 1 bytes, Status: OK
[360,1] Written, Length: 2 bytes, Status: OK
[360,2] Written, Length: 3 bytes, Status: OK
[369,0] Written, Length: 40 bytes, Status: OK
Write PM Finished, Record written OK: 105, Record written NOT OK: 0
Started Phone Security Analysis...
MCU Version V ICPR82_11w16.3.11
MCU Date 29-03-12
Product RM-469 (Nokia E52)
Manufacturer (c) Nokia
IMEI 357880040507406
Mastercode 1222704463
Reading Security Block...
Security block OK and saved to "RM-469_357880040507406_10.08.2012_200421.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
-- SIMLOCK PROBLEM --

Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED!
To repair simlock area, Select Unlock method : "RPL CALCULATION",
And then click DIRECT UNLOCK. SL Area will be re-formatted.

-- SIMLOCK PROBLEM --
Step 2 : Testing SECURITY
SECURITY SEFLTEST PASSED OK!
Step 3 : Analyzing Security Block
"09D0000567D70344D473E345BD0646795015BC77.C0003F42" Exists, That is good...
Checking SUPERDONGLE...
SUPERDONGLE FOUND AND CHECKSUM OK! PASSED!
Checking SIMLOCK...
Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?)
Checking MCU&DSP TIMESTAMPS...
MCU&DSP TIMESTAMPS FOUND AND CHECKSUM OK! PASSED!
Checking CMLA KEYS...
CMLA KEYS FOUND AND CHECKSUM OK! PASSED!
Checking ECC KEYS...
ECC KEYS FOUND AND CHECKSUM OK! PASSED!
Checking DIV KEYS...
DIV KEYS FOUND AND CHECKSUM OK! PASSED!
Analyze finished!

Step 1 : Testing SIMLOCK ---------------вот проблема моя
-- SIMLOCK PROBLEM --

Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED!
To repair simlock area, Select Unlock method : "RPL CALCULATION",
And then click DIRECT UNLOCK. SL Area will be re-formatted.

делаю что говорят и вот что получаю

BB5 Unlock Started...
MCU Version V ICPR82_11w16.3.11
MCU Date 29-03-12
Product RM-469 (Nokia E52)
Manufacturer (c) Nokia
IMEI 357880040507406
Mastercode 1222704463
Warning: Failed to read SP Info, Assuming defaults
Simlock Server SIMLOCK SERVER
Simlock Key 0000000000000000
Simlock Profile
Simlock Key Cnt 0
Simlock FBUS Cnt 0
Reading Security Block...
Security block OK and saved to "RM-469_357880040507406_10.08.2012_200653.SecurityBlock.PM"
"09D0000567D70344D473E345BD0646795015BC77.C0003F42" Exists, That is good...
Checking for Rootkey Hash support with selected Unlock Method...
Selected Unlock Method: RPL Calculation
Asking box to calculate RPL...
Received RPL from Box OK!
Writing Simlock...
BB5 Unlock Failed -> Simlock NOT ACCEPTED ! Maybe is SL3 phone?

все, дальше голова не варит, второй день бьюсь, подскажите пожалуста что я не так делаю?

10.08.2012, 19:15	#156
popovtv Junior Member Регистрация: 27.07.2011 Сообщений: 7 Вес репутации: 0	Re: Помощь нашим пользователям в восстановлении ПО Nokia BB5 с помощью RPL добрый день,UO5OQ заказал у вас рпл на е52,раньше он мне всегда помогал(всмысле не первый раз делаю),а щас не могу восстановить тело,делаю циклоном фул ераз вот что получил Reading info... MCU Version V ICPR82_11w16.3.11 MCU Date 29-03-12 Product RM-469 (Nokia E52) Manufacturer (c) Nokia IMEI 12345610654321? IMEI Spare 1A32541660452301 IMEI SV 1332541660452351F7000000 PSN 0 PSD 0000000000000000 LPSN 0 APE SW 091.003 APE Variant 091.003091.003.05.01091.003.C00.01 APE Test v0.a091 APE HW 256 APE ADSP 256 RETU 40 TAHVO 00 AHNE 11 RFIC \|Vapaus_5.1 \| Mikki_1.1 DSP 11w52 Failed to read info -> Failed to read SP info Read info thread finished, continuing... Post flash tasks finished! Flashing successfully finished! анализ секюрити Security block OK and saved to "RM-469_12345610654321_10.08.2012_200109.SecurityBlock.PM" Step 1 : Testing SIMLOCK SIMLOCK SEFLTEST PASSED OK! Step 2 : Testing SECURITY SECURITY SEFLTEST PASSED OK! Step 3 : Analyzing Security Block "09D0000567D70344D473E345BD0646795015BC77.C0003F42" Exists, That is good... Checking SUPERDONGLE... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking SIMLOCK... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking MCU&DSP TIMESTAMPS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking CMLA KEYS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking ECC KEYS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking DIV KEYS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Analyze finished! Step 1 : Testing SIMLOCK SIMLOCK SEFLTEST PASSED OK!------вот это не могу сделать чтобы было в конце записываю рпл и сразу анализ секюрити MCU Version V ICPR82_11w16.3.11 MCU Date 29-03-12 Product RM-469 (Nokia E52) Manufacturer (c) Nokia IMEI 357880040507406 Mastercode 1222704463 Reading Security Block... Security block OK and saved to "RM-469_357880040507406_10.08.2012_200311.SecurityBlock.PM" Step 1 : Testing SIMLOCK -- SIMLOCK PROBLEM -- Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED! To repair simlock area, Select Unlock method : "RPL CALCULATION", And then click DIRECT UNLOCK. SL Area will be re-formatted. -- SIMLOCK PROBLEM -- Step 2 : Testing SECURITY -- SECURITY PROBLEM -- Phone have failed SECURITY Test, that means Superdongle Area is DAMAGED! To repair it, simply slick "SX4 Authorization / SD Repair" button. After SX4/SD Repair, don't forget to write PM file with fields 1,309 (if SW don't do this automatically) Additionaly, Checking HWC/CCC Certs... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000030000022600010007600C192102011104 CMT_EM_ASIC_ID: 00001040 CMT_EM_ASIC_ID: 00001030 CMT_PUBLIC_ID: 09D0000567D70344D473E345BD0646795015BC77 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: 25B977A055BE9B5DEC0C38A2A279C695 CMT_BOOT_ROM_CRC: 3E273BF6 CMT_SECURE_ROM_CRC: 37BE26FA CMT Ready! Searching for BootCode: DualLine 32Bit RAPUv11_2nd.fg, Type: 2nd Boot Loader, Rev: 768.12.11.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]: 0x0020004000000031, ST, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x0020004000000031, ST, ONENAND Requested Algorithm: XSR 1.6 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00200040 (ST), Size: 256MBytes, VPP: Not Supported FlashChip 0x00200040 (ST), Size: 256MBytes, VPP: Not Supported RAPUv11_XSR17_alg.fg, Type: Algorithm, Rev: 768.12.11.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: 85F252E351E225CAFC4DFBC8041EABD2823E3500 APE Subsystem Not Found Flashbus Write baud set to 5.0Mbits HWC Looks OK! CCC Looks OK! Restarting MCU... -- SECURITY PROBLEM -- Step 3 : Analyzing Security Block "09D0000567D70344D473E345BD0646795015BC77.C0003F42" Exists, That is good... Checking SUPERDONGLE... SUPERDONGLE FOUND AND CHECKSUM OK! PASSED! Checking SIMLOCK... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking MCU&DSP TIMESTAMPS... MCU&DSP TIMESTAMPS FOUND AND CHECKSUM OK! PASSED! Checking CMLA KEYS... CMLA KEYS FOUND AND CHECKSUM OK! PASSED! Checking ECC KEYS... ECC KEYS FOUND AND CHECKSUM OK! PASSED! Checking DIV KEYS... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Analyze finished! теперь sx4 запись пм SX4 Authorization / SD Repair Procedure Started.... "09D0000567D70344D473E345BD0646795015BC77.C0003F42" Exists, That is good... MCU Version V ICPR82_11w16.3.11 MCU Date 29-03-12 Product RM-469 (Nokia E52) Manufacturer (c) Nokia IMEI 357880040507406 Mastercode 1222704463 Reading Security Block... Security block OK and saved to "RM-469_357880040507406_10.08.2012_200410.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 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: 10 bytes, Status: OK [1,4] Written, Length: 110 bytes, Status: OK [1,6] Written, Length: 10 bytes, Status: OK [1,7] Written, Length: 214 bytes, Status: OK [1,8] Written, Length: 110 bytes, Status: OK [1,13] Written, Length: 10 bytes, Status: OK [1,16] Written, Length: 208 bytes, Status: OK [1,18] Written, Length: 208 bytes, Status: OK [1,20] Written, Length: 208 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,26] Written, Length: 110 bytes, Status: OK [1,28] Written, Length: 10 bytes, Status: OK [1,29] Written, Length: 10 bytes, Status: OK [1,31] Written, Length: 208 bytes, Status: OK [1,33] Written, Length: 36 bytes, Status: OK [1,34] Written, Length: 376 bytes, Status: OK [1,35] Written, Length: 16 bytes, Status: OK [1,39] Written, Length: 36 bytes, Status: OK [1,40] Written, Length: 16 bytes, Status: OK [1,41] Written, Length: 182 bytes, Status: OK [1,42] Written, Length: 4 bytes, Status: OK [1,43] 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: 2080 bytes, Status: OK [4,1] Written, Length: 1020 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,6] Written, Length: 8 bytes, Status: OK [4,9] Written, Length: 5 bytes, Status: OK [4,28] Written, Length: 2 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,8] Written, Length: 8 bytes, Status: OK [8,9] Written, Length: 8 bytes, Status: OK [8,10] Written, Length: 32 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: 1058 bytes, Status: OK [12,0] Written, Length: 102 bytes, Status: OK [26,0] Written, Length: 16 bytes, Status: OK [26,1] Written, Length: 68 bytes, Status: OK [31,4] Written, Length: 18 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: 41 bytes, Status: OK [107,1] Written, Length: 89 bytes, Status: OK [107,2] Written, Length: 89 bytes, Status: OK [107,3] Written, Length: 70 bytes, Status: OK [107,25] Written, Length: 236 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: 104 bytes, Status: OK [120,0] Written, Length: 944 bytes, Status: OK [120,1] Written, Length: 160 bytes, Status: OK [120,2] Written, Length: 130 bytes, Status: OK [120,3] Written, Length: 112 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 [217,0] Written, Length: 32 bytes, Status: OK [239,6] Written, Length: 218 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,3] Written, Length: 36 bytes, Status: OK [309,4] Written, Length: 12 bytes, Status: OK [309,7] Written, Length: 12 bytes, Status: OK [309,17] Written, Length: 12 bytes, Status: OK [313,0] Written, Length: 173 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: 4512 bytes, Status: OK [354,0] Written, Length: 28 bytes, Status: OK [356,0] Written, Length: 2 bytes, Status: OK [356,1] Written, Length: 8 bytes, Status: OK [360,0] Written, Length: 1 bytes, Status: OK [360,1] Written, Length: 2 bytes, Status: OK [360,2] Written, Length: 3 bytes, Status: OK [369,0] Written, Length: 40 bytes, Status: OK Write PM Finished, Record written OK: 105, Record written NOT OK: 0 Started Phone Security Analysis... MCU Version V ICPR82_11w16.3.11 MCU Date 29-03-12 Product RM-469 (Nokia E52) Manufacturer (c) Nokia IMEI 357880040507406 Mastercode 1222704463 Reading Security Block... Security block OK and saved to "RM-469_357880040507406_10.08.2012_200421.SecurityBlock.PM" Step 1 : Testing SIMLOCK -- SIMLOCK PROBLEM -- Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED! To repair simlock area, Select Unlock method : "RPL CALCULATION", And then click DIRECT UNLOCK. SL Area will be re-formatted. -- SIMLOCK PROBLEM -- Step 2 : Testing SECURITY SECURITY SEFLTEST PASSED OK! Step 3 : Analyzing Security Block "09D0000567D70344D473E345BD0646795015BC77.C0003F42" Exists, That is good... Checking SUPERDONGLE... SUPERDONGLE FOUND AND CHECKSUM OK! PASSED! Checking SIMLOCK... Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) Checking MCU&DSP TIMESTAMPS... MCU&DSP TIMESTAMPS FOUND AND CHECKSUM OK! PASSED! Checking CMLA KEYS... CMLA KEYS FOUND AND CHECKSUM OK! PASSED! Checking ECC KEYS... ECC KEYS FOUND AND CHECKSUM OK! PASSED! Checking DIV KEYS... DIV KEYS FOUND AND CHECKSUM OK! PASSED! Analyze finished! Step 1 : Testing SIMLOCK ---------------вот проблема моя -- SIMLOCK PROBLEM -- Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED! To repair simlock area, Select Unlock method : "RPL CALCULATION", And then click DIRECT UNLOCK. SL Area will be re-formatted. делаю что говорят и вот что получаю BB5 Unlock Started... MCU Version V ICPR82_11w16.3.11 MCU Date 29-03-12 Product RM-469 (Nokia E52) Manufacturer (c) Nokia IMEI 357880040507406 Mastercode 1222704463 Warning: Failed to read SP Info, Assuming defaults Simlock Server SIMLOCK SERVER Simlock Key 0000000000000000 Simlock Profile Simlock Key Cnt 0 Simlock FBUS Cnt 0 Reading Security Block... Security block OK and saved to "RM-469_357880040507406_10.08.2012_200653.SecurityBlock.PM" "09D0000567D70344D473E345BD0646795015BC77.C0003F42" Exists, That is good... Checking for Rootkey Hash support with selected Unlock Method... Selected Unlock Method: RPL Calculation Asking box to calculate RPL... Received RPL from Box OK! Writing Simlock... BB5 Unlock Failed -> Simlock NOT ACCEPTED ! Maybe is SL3 phone? все, дальше голова не варит, второй день бьюсь, подскажите пожалуста что я не так делаю?