|
Nokia 5228 phone start-up failed. contact the retailer
Вложений: 1
Здравствуйте, принесли нокию 5228 RM-625 с проблемой: phone start-up failed. contact the retailer., я его прошивал, рм заливал с сх4 авторизацией, но это не помогло, как я понял надо рпл
вот логи чек циклона:Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C 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.11.48.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.11.48.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 Boot skipped on user request Flashbus Write baud set to 5.0Mbits Restarting MCU... инфо: MCU Version V ICPR72_11w16.1 MCU Date 28-07-11 Product RM-625 (Nokia 5233/5232/5228) Manufacturer (c) Nokia IMEI 357896042084145 Mastercode 1130365177 IMEI Spare 3A75980624801404 IMEI SV 3375980624801414F6000000 PSN 158314BAA Product Code 059B961 Module Code 0204695 Basic Product Code 0587948 PSD 0000000000000000 LPSN 0 APE SW V 51.1.002 APE Variant V 51.1.002V 51.1.002 V 51.1.002 APE Test eno_version APE HW 256 APE ADSP 256 RETU 16 TAHVO 22 AHNE 11 HW 0201 RFIC 17141716 DSP ICPR72_11WK13 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 с телефона слил всё, что нужно было и что нет) можно его как то привести в чувство с тем, что есть не заказывая рпл? |
Re: Nokia 5228 phone start-up failed. contact the retailer
Форматируйте зону пользователя !
|
Re: Nokia 5228 phone start-up failed. contact the retailer
и бэкап NPC неплохо бы сделать.Извиняюсь он есть незаметил
|
Вложений: 1
почему не удаётся рпл та сохранить не пойму?, лога нет, есть процедуры на сегодняшний день..., там все логи в кучи
вот вроде отдельно лог сохранения рпл:Processing pre flash tasks...
Backing up RPL... RPL Creation started... Processing CMT Part... Storing Product Code... Storing PSN... Storing HWID... Trying to store Simlock... Reading Configuration Key... Hashing... Reading SHA1-RSA Signature... Reading SHA1-HMAC Signature... Storing Simlock... Trying to store WMDRM RPL... Reading Keys... Storing WMDRM PD... Reading Security Block... "RM-625_357896042084145_13.06.2012_145104.SecurityBlock.PM" "22E0000DE5B4005230EC6A82375E605FCF5DF57B.C0004D44" Exists, That is good... Storing Additional Data... Checking Superdongle Key... Encrypting Superdongle Key... Storing Superdongle Key... Checking CMLA Key... Storing CMLA Key... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.48.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: 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.11.48.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 Storing NPC... Storing CCC... Storing HWC... CMT VARIANT Not Found CMT PARTNERC Not Found Restarting MCU... RPL Saved OK RPL backup thread finished, continuing... Pre flash tasks finished, continuing... Processing RM-625_51.1.002_prd.core.C00 (CMT)... 'Cyclone.exe'. Read of address 00000000 Failed to Process all Image files -> Failed to process RM-625_51.1.002_prd.core.C00 с сохранённым рпл как то спокойней будет..., по логам по моему он некорректно сохранился(( Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
ТС Глянь хорошо цепь BSI!Если программно всё сделано и не чего не помогает то остаётся только глянуть эту цепь!Не раз было такое что все программные действия были проделаны(Ну кроме заказа RPL)А результата не было а виной была цепь BSI!
P/S При таком ходе событий я склоняюсь к ней!:yes: |
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
Ну а с другой стороны,дело ваше я вам дал совет а воспользоваться им или нет решать вам! |
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
посмотри BESTом или МХ какое состояние SDD Key и Security status
|
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
вот анализ секъюрити:
Started Phone Security Analysis... MCU Version V ICPR72_11w16.1 MCU Date 28-07-11 Product RM-625 (Nokia 5233/5232/5228) Manufacturer (c) Nokia IMEI 357896042084145 Mastercode 1130365177 Reading Security Block... Security block OK and saved to "RM-625_357896042084145_14.06.2012_101631.SecurityBloc k.PM" Step 1 : Testing SIMLOCK SIMLOCK SEFLTEST PASSED OK! Step 2 : Testing SECURITY SECURITY SEFLTEST PASSED OK! Step 3 : Analyzing Security Block "22E0000DE5B4005230EC6A82375E605FCF5DF57B.C0004D44 " 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! вроде всё в поряде... только одна строчка не понравилась Failed to decode Security Section, Box Reported: Security Section Not Found (SL3 phone?) что она обозначает? |
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
возможен вариант что он был прошит 51.9 и потом понижен.Поэтому есть смысл прошить его последней прошивкой
|
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
1ST BOOT : C0,07 [Rm-625] [2.2.0.1] CMT ASICID: 000000010000022600010006400C192101051105 EM 1 ID : 00000296 EM 2 ID : 00000B22 CMT PUBID : 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT MODE : 00 CMT HASH : B8C3ADECFC997FCD8081D3DEAF870B8C CMT ROMID : 4B9B75103E691FF8 CMT 1ST Boot OK Cannot Find KEYS CERT BAD BOOT ERR: CMT 2ND Boot File not Found Rebooting Mobile а инфо читается нормально: MCU SW : V ICPR72_11w16.1 28-07-11 RM-625 (c) Nokia APE Core: V 51.1.002 APE Var : V 51.1.002V 51.1.002 V 51.1.002 Product : Nokia 5228 Prd.Code: 059B961 Bpr.Code: 0587948 Prod.Sn : 158314BAA HW Vers : 0201 APE HW : 256 APE Adsp: 256 EM VILMA: 16 EM BETTY: 22 RFIC Ver: 17141716 DSP Vers: ICPR72_11WK13 IMEI : 357896-04-208414-5 SL Serv : SIMLOCK SERVER SL Conf : 244-07-00000000000 SL Prof : 0000000000000000 SL Count: 00 00 BLK1= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN BLK2= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN BLK3= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN BLK4= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN BLK5= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN BLK6= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN BLK7= L1: OPEN L2: OPEN L3: OPEN L4: OPEN L5: OPEN Provider: Nokia Test;Finland |
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
UFS его по FBUS непотдерживает.Прошивки в навифирм
|
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
Воспользуйтесь программой NaviFirmEx |
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
прошил циклоном в последнюю версию и ТА погиб, теперь только вибро и всё, вот лог прошивки с автоматическим сохранением рпл:
Скрытый текстAuto Selecting Flash Files on User Request...
Product Code: 059B961 This is Valid BB5 Product Retrieving Variants for Product RM-625 - wait... 1 Variants Retrieved No variant found with given Product Code, selecting first one Processing pre flash tasks... Backing up RPL... RPL Creation started... Processing CMT Part... Storing Product Code... Storing PSN... Storing HWID... Trying to store Simlock... Reading Configuration Key... Hashing... Reading SHA1-RSA Signature... Reading SHA1-HMAC Signature... Storing Simlock... Trying to store WMDRM RPL... Reading Keys... Storing WMDRM PD... Reading Security Block... Security block OK and saved to "RM-625_357896042084145_14.06.2012_105709.SecurityBlock.PM" "22E0000DE5B4005230EC6A82375E605FCF5DF57B.C0004D44" Exists, That is good... Storing Additional Data... Checking Superdongle Key... Encrypting Superdongle Key... Storing Superdongle Key... Checking CMLA Key... Storing CMLA Key... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C 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.11.48.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.11.48.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 Storing NPC... Storing CCC... Storing HWC... CMT VARIANT Not Found CMT PARTNERC Not Found Restarting MCU... RPL Saved OK RPL backup thread finished, continuing... Pre flash tasks finished, continuing... Processing RM-625_51.9.002_prd.core.C00 (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-625_51.9.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.11.48.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.11.48.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 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.250s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT ADA Certificate... Writing CMT KEYS Certificate... Writing CMT PRIMAPP Certificate... Writing CMT RAP3NAND Certificate... Writing CMT PASUBTOC Certificate... Writing CMT PAPUBKEYS Certificate... Writing CMT SOS*UPDAPP Certificate... Writing CMT SOS*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 112.438s Flashing Speed: 7089,36 kBit/S Restarting MCU... Processing RM-625_51.9.002_prd.core.C00 (APE)... Processing RM-625_51.9.002_prd.rofs2.V25 (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-625_51.9.002_prd.rofs2.V25, Type: Flash Image, Algo: XSR 1.6, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.48.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.11.48.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]: 0x06DE0000-0x0915FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.281s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS2 Certificate... Programming Status OK! All blocks written OK! Time taken 31.859s Flashing Speed: 6976,36 kBit/S Restarting MCU... Processing RM-625_51.9.002_prd.rofs2.V25 (APE)... Processing RM-625_51.9.002.549.04.rofs3.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-625_51.9.002.549.04.rofs3.fpsx, Type: Flash Image, Algo: XSR 1.6, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.48.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.11.48.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.140s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS3 Certificate... Programming Status OK! All blocks written OK! Time taken 7.531s Flashing Speed: 6863,64 kBit/S Restarting MCU... Processing RM-625_51.9.002.549.04.rofs3.fpsx (APE)... Processing RM625_51.9.002_002_U549.uda.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM625_51.9.002_002_U549.uda.fpsx, Type: Flash Image, Algo: XSR 1.6, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.48.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.11.48.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.578s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Programming Status OK! All blocks written OK! Time taken 29.16s Flashing Speed: 6695,08 kBit/S Restarting MCU... Processing RM625_51.9.002_002_U549.uda.fpsx (APE)... All images processed OK! Processing post flash tasks... Setting Factory Defaults... Factory defaults OK Reading info... Sending User Abort Signal... CBUS Request Error -> User abort Failed to disable VBAT -> No answer from CBUS Failed to read info -> Phone not detected Read info thread finished, continuing... Post flash tasks finished! Flashing successfully finished! локал пропал.. |
Re: Nokia 5228 phone start-up failed. contact the retailer
попробовал опять прошить, но всё так же вибро и ТА невкл, может обратно прошить той версией которая была? т.е. понизить версию.
|
Re: Nokia 5228 phone start-up failed. contact the retailer
RPL не пробывал залить?
|
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
http://www.uo5oq.com/forum/showthread.php?t=376 почитайте там |
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
беда в том что приборов у него мало,UFS тут вообще не помошник а циклон под вопросом
|
Re: Nokia 5228 phone start-up failed. contact the retailer
рпл не записывается, не видит ТА по ф бас((, но чек норм проходит и шиться шьётся, лог попытки записи рпл:
Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Failed to Write RPL File -> Phone not detected |
Re: Nokia 5228 phone start-up failed. contact the retailer
Вложений: 2
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
интересно всё таки почему предыдущую версию прошивки прошивал и ТА включался, а с этой версией не хочет включаться? может "Variant" не тот скачал?
скачивал я "5236 RM-625 PRC Country Variant CN Black Metal v4 (059F6X6) а есть ещё варианты такие: 5236 RM-625 PRC Country Variant CN White_Chrome v4_COLOR (059F6X5) и RM-625 NDT 5236 PRC BLACK_METAL PROTO (059L8D0) может надо было 3-й вариант? |
Re: Nokia 5228 phone start-up failed. contact the retailer
нужно его стереть,прошить файлом ENO и востанавливать
|
Re: Nokia 5228 phone start-up failed. contact the retailer
А вы Seregaddt, еще не стирали телефон, ведь в инструкции написано:
Порядок полного стирания телефона с последующей полной перезаписью: 1.) Полностью стереть телефон по адрессам автоматически выствляемым используемой программой (кнопка ERASE) или записать соответствующий модели ремонтируемого телефона, файлик Erase_xxxx). 2.) Записать самую новую версию SW соответствующую модели (RM-xxx) ремонтируемого телефона. Если после этого телефон включится нормально, значит идем дальше 3.) Записать рассчитанный на сервере www.UO5OQ.com RPL файл.( у вас свои бекапы пока есть) 4.) Записать 1 и 309 блоки PM (или полный PM без 120 и 308 полей) от данной модели, предварительно пройдя SX4 Autorisation. Если и это не помогло, то ремонтируем аппаратную часть телефона. |
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
Скрытый текстProcessing rm625_ENO_x_09wk43v0.050.fpsx (CMT)...
Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! rm625_ENO_x_09wk43v0.050.fpsx, Type: Flash Image, Algo: XSR 1.6, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.48.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.11.48.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 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.218s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT ADA Certificate... Writing CMT KEYS Certificate... Writing CMT PRIMAPP Certificate... Writing CMT RAP3NAND Certificate... Writing CMT PASUBTOC Certificate... Writing CMT PAPUBKEYS Certificate... Writing CMT SOS*ENO Certificate... Writing CMT SOS*DSP0 Certificate... Writing CMT SOS*ISASW Certificate... Programming Status OK! All blocks written OK! Time taken 7.500s Flashing Speed: 6100,19 kBit/S Restarting MCU... Processing rm625_ENO_x_09wk43v0.050.fpsx (APE)... All images processed OK! Processing post flash tasks... рпл так и не хочет записываться, сейчас пробовать шить его? |
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
сделал FULL ERASE, прошил последней версией прошивки, ТА начал включаться, но после надписи NOKIA перезагружался, дальше записал рпл, полный РМ без 120 и 308 блоков с предварительной SX4 авторизацией, но ТА так же перезагружается, вот логи:
Скрытый текстBooting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C 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.11.48.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.11.48.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 Erasing flash chip... Started group flash erase EraseArea[0,CMT]: 0x00000000-0x0FFFFFFF, ONENAND Waiting 640s for erasure finish... Erase taken 1.485s Restarting MCU... BB5 Full Erase Finished! Failed to Extract BB5 Variant -> VPL File not found at all! Unexpected error. Retrieving Variants for Product RM-200 - wait... 20 Variants Retrieved Retrieving Variants for Product RM-625 - wait... 16 Variants Retrieved Processing pre flash tasks... Pre flash tasks finished, continuing... Processing RM-625_51.1.002_prd.core.C00 (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-625_51.1.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.11.48.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.11.48.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.266s 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 113.579s Flashing Speed: 7088,11 kBit/S Restarting MCU... Processing RM-625_51.1.002_prd.core.C00 (APE)... Processing RM-625_51.1.002_prd.rofs2.V05 (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-625_51.1.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.11.48.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.11.48.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]: 0x06CE0000-0x0915FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.313s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS2 Certificate... Programming Status OK! All blocks written OK! Time taken 31.250s Flashing Speed: 6981,37 kBit/S Restarting MCU... Processing RM-625_51.1.002_prd.rofs2.V05 (APE)... Processing RM-625_51.1.002_C01_prd.rofs3.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-625_51.1.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.11.48.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.11.48.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.172s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS3 Certificate... Programming Status OK! All blocks written OK! Time taken 7.500s Flashing Speed: 6888,18 kBit/S Restarting MCU... Processing RM-625_51.1.002_C01_prd.rofs3.fpsx (APE)... Processing RM625_51.1.002_000_001_U001.uda.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM625_51.1.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.11.48.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.11.48.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.578s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Programming Status OK! All blocks written OK! Time taken 21.438s Flashing Speed: 6678,59 kBit/S Restarting MCU... Processing RM625_51.1.002_000_001_U001.uda.fpsx (APE)... All images processed OK! Processing post flash tasks... Post flash tasks finished! Flashing successfully finished! Skipping RPL decryption... Parsing decrypted RPL... Processing FBUS Part... Writing Product Code... Writing PSN... Writing HWID... Writing Simlock... Handling as SL3 Simlock Data Handling as SIMLOCK1 Format Reading Security Block... Security block OK and saved to "RM-625_12345610654321_14.06.2012_140440.SecurityBlock.PM" 15 Digits NCK Found Simlock ACCEPTED OK ! Writing Superdongle key... Superdongle Key ACCEPTED OK ! Writing CMLA key... CMLA Key ACCEPTED OK ! Writing WMDRM PD Data... WMDRM PD Data ACCEPTED OK ! Processing FLASHBUS Part... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C 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.11.48.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.11.48.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! [1,0] Protecting [1,2] Protecting [1,4] Protecting [1,6] Protecting [1,8] Protecting [1,13] Protecting [1,16] Protecting [1,18] Protecting [1,20] Protecting [1,24] Protecting [1,25] Protecting [1,26] Protecting [1,28] Protecting [1,29] Protecting [1,31] Protecting [1,34] Protecting [2,0] Written, Length: 440 bytes, Status: OK [4,1] Written, Length: 80 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,7] Written, Length: 4 bytes, Status: OK [8,8] Written, Length: 8 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: 1054 bytes, Status: OK [12,0] Written, Length: 102 bytes, Status: OK [31,4] Written, Length: 14 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 [54,2] Written, Length: 24 bytes, Status: OK [88,0] Written, Length: 36 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,0] Written, Length: 4 bytes, Status: OK [117,1] Written, Length: 3 bytes, Status: OK [117,2] Written, Length: 6 bytes, Status: OK [117,3] Written, Length: 1 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 [117,13] Written, Length: 3 bytes, Status: OK [117,14] Written, Length: 3 bytes, Status: OK [117,16] Written, Length: 40 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 [309,0] Protecting [309,1] Protecting [309,2] Protecting [309,4] Protecting [309,5] Protecting [309,7] Protecting [309,8] Protecting [309,17] Protecting [322,0] Written, Length: 1 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 [372,0] Written, Length: 48 bytes, Status: OK Write PM Finished, Record written OK: 83, Record written NOT OK: 0 |
Re: Nokia 5228 phone start-up failed. contact the retailer
после этих процедур, анализ секъюрити:
Скрытый текстStarted Phone Security Analysis...
MCU Version V ICPR72_11w16.1 MCU Date 28-07-11 Product RM-625 (Nokia 5233/5232/5228) Manufacturer (c) Nokia IMEI 357896042084145 Mastercode 1130365177 Reading Security Block... Security block OK and saved to "RM-625_357896042084145_14.06.2012_144627.SecurityBlock.PM" Step 1 : Testing SIMLOCK SIMLOCK SEFLTEST PASSED OK! 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: 000000010000022600010006400C192101051105 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 22E0000DE5B4005230EC6A82375E605FCF5DF57B CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: B8C3ADECFC997FCD8081D3DEAF870B8C 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.11.48.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.11.48.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 HWC Looks OK! CCC Looks OK! Restarting MCU... -- SECURITY PROBLEM -- Step 3 : Analyzing Security Block "22E0000DE5B4005230EC6A82375E605FCF5DF57B.C0004D44" 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... 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! что то может нужно записать кроме прошивки, рпл и рм? |
Re: Nokia 5228 phone start-up failed. contact the retailer
Ты должен стереть полностью телефон и потом прошить только SW без никаких рпл ов, после этого он должен включится нормально с имеем 12345..., если не включится значит дефект по железу
|
Re: Nokia 5228 phone start-up failed. contact the retailer
Цитата:
|
Re: Nokia 5228 phone start-up failed. contact the retailer
Вы откуда прошивки качаете?
|
| Текущее время: 02:01. Часовой пояс GMT +3. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd. Перевод: zCarot
© 2007—2022 www.UO5OQ.com