N73 темнеет экран и выключается

**Соломон1** · 16.01.2013, 12:23

Изначально телефон пришел с проблемой что периодически выключается,решил прошить с Cyclone,циклон не хотел шить,с Уфсом при чеке и прошивке давал следующую "Product Selection Mismatch: no Response from APE MCU".Визуально заметил полусгнившие шины идущие на микрофон,после чего кинул в УЗВ и после промывки и просушки,подцепил к Уфс и тело прошилось со сбросами без проблем.Работало нормально,но опять при просмотре картинок,или при передаче файлов через блютуз тело зависало и темнел экран,после чего не включалось пока не передернешь АКБ.Решил прогреть ОМАР и Флешку,после прогрева проблема осталась.Подключил к Cyclone и решил прошить заново,вот чек:

Код:

Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1D800015309C0154F23524E0F7E39E707D1935A0
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC22E800006921, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...[/cоde]

При прошивке вышла ошибка вот лог:

[cоde]Processing pre flash tasks...
Pre flash tasks finished, continuing...
Processing N73_4.0839.42.2.1_western_C00_PRD_cc.fpsx (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1D800015309C0154F23524E0F7E39E707D1935A0
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
N73_4.0839.42.2.1_western_C00_PRD_cc.fpsx, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 51Kbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC22E800006921, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud set to 5.0Mbits
Partitioning...
Partitioning OK
Started group flash erase
EraseArea[0,CMT]: 0x00080000-0x00731951, NOR
EraseArea[0,CMT]: 0x00000000-0x0005FFFF, NOR
EraseArea[0,CMT]: 0x001E0000-0x001FFFFF, NOR
EraseArea[0,CMT]: 0x00880000-0x00FEFFFF, NOR
Waiting 320s for erasure finish...
Erase taken 35.734s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT NOLO Certificate...
Writing CMT KEYS Certificate...
Writing CMT PRIMAPP Certificate...
Writing CMT PASUBTOC Certificate...
Writing CMT PAPUBKEYS Certificate...
Writing CMT UPDAPP Certificate...
Writing CMT ADL Certificate...
Writing CMT DSP0 Certificate...
Writing CMT MCUSW Certificate...
Programming Status OK!
All blocks written OK! Time taken 31.469s
Flashing Speed: 13060,31 kBit/S
Restarting MCU...
Processing N73_4.0839.42.2.1_western_C00_PRD_cc.fpsx (APE)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1D800015309C0154F23524E0F7E39E707D1935A0
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
N73_4.0839.42.2.1_western_C00_PRD_cc.fpsx, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 51Kbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC22E800006921, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
APE Subsystem Not Found
Processing Flash Image Failed -> Trying to program APE subsystem, but APE not exists
Failed to Process all Image files -> Failed to process N73_4.0839.42.2.1_western_C00_PRD_cc.fpsx

После чего подцепил к Уфс и он опять дает ошибку"Product Selection Mismatch: no Response from APE MCU".Вероятнее всего проблема в OMAPE,как правильно проверить питание APE и сколько оно должно быть?

**elenlove** · 16.01.2013, 15:30

Все ответы по поводу питания АРЕ, вы найдете в схеме.

Когда делаете чек - выбираете модель телефона в увс ?

**Соломон1** · 17.01.2013, 19:07

Да правильно выставил модель в УФС,после полной разборки платы телефон прошился без проблем вот лог:

Код:

1ST BOOT  : C0,0C [Rm-133] [2.2.0.3]
APE ASICID: 17100708
APE MODE  : 00
APE PUBID : CEF00C555C712F8317294A54441D29AFDA8157A3
APE HASH  : 49A97E826B93BA20B7ED0B082475C005
APE ROMID : 1DFD66132C872FD4
CMT ASICID: 000000010000022600010006010C192101003000
EM 1 ID   : 00000295
EM 2 ID   : 00000B21
CMT PUBID : 1D800015309C0154F23524E0F7E39E707D1935A0
CMT MODE  : 00
CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1
CMT ROMID : 273F6D55DFAAF68F
CMT 1ST Boot OK
CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1
CMT FLID0 : 00EC22E8-00006921, Sam K8S2815ETB
CMT FLCNT : 00000000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO  : RAP3Gv3_algo.fg, Ver: 9.17.0
CMT KSIG0 : 5E8D0D504A0902E261268C14FCD8A2C9093523BC
CMT VPP   : Internal
DUAL LINE : True
CMT ALG Boot OK
IMAGE : N73_4.0839.42.2.1_western_C00_PRD_cc.fpsx
CMT NOR Erase Area: 0x00080000-00731951
CMT NOR Erase Area: 0x00000000-0005FFFF
CMT NOR Erase Area: 0x001E0000-001FFFFF
CMT NOR Erase Area: 0x00880000-00FEFFFF
CMT FLASH ERASE OK, Time: 00:41
Written: 9 Certificate(s)
CMT FLASH WRITE OK, Time: 00:29
1ST BOOT  : C0,0C [Rm-133] [2.2.0.3]
APE ASICID: 17100708
APE MODE  : 00
APE PUBID : CEF00C555C712F8317294A54441D29AFDA8157A3
APE HASH  : 49A97E826B93BA20B7ED0B082475C005
APE ROMID : 1DFD66132C872FD4
CMT ASICID: 000000010000022600010006010C192101003000
EM 1 ID   : 00000295
EM 2 ID   : 00000B21
CMT PUBID : 1D800015309C0154F23524E0F7E39E707D1935A0
CMT MODE  : 00
CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1
CMT ROMID : 273F6D55DFAAF68F
CMT 1ST Boot OK
CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1
CMT FLID0 : 00EC22E8-00006921, Sam K8S2815ETB
CMT FLCNT : 00000000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO  : RAP3Gv3_algo.fg, Ver: 9.17.0
CMT KSIG0 : 5E8D0D504A0902E261268C14FCD8A2C9093523BC
CMT VPP   : Internal
DUAL LINE : True
CMT ALG Boot OK
APE 2ND Bt: helen3_2nd.fg, Ver: 1.35.0
APE FLID0 : 00EC00A1-00800015, Sam KAL00T00EA
APE FLCNT : 010100FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
APE 2ND Boot OK
APE ALG0  : h3_sam_nand_xsr.fg, Ver: 1.49.0
APE VPP   : Internal
APE KSIG1 : 5E8D0D504A0902E261268C14FCD8A2C9093523BC
DUAL LINE : True
APE ALG Boot OK
IMAGE : N73_4.0839.42.2.1_western_C00_PRD_cc.fpsx
APE NAND Erase Area: 0x00000000-0007FFFF
APE NAND Erase Area: 0x00080000-000FFFFF
APE NAND Erase Area: 0x00100000-0025FFFF
APE NAND Erase Area: 0x003C0000-04E1FFFF
APE FLASH ERASE OK, Time: 00:01
Written: 13 Certificate(s)
APE FLASH WRITE OK, Time: 04:08
1ST BOOT  : C0,0C [Rm-133] [2.2.0.3]
APE ASICID: 17100708
APE MODE  : 00
APE PUBID : CEF00C555C712F8317294A54441D29AFDA8157A3
APE HASH  : 49A97E826B93BA20B7ED0B082475C005
APE ROMID : 1DFD66132C872FD4
CMT ASICID: 000000010000022600010006010C192101003000
EM 1 ID   : 00000295
EM 2 ID   : 00000B21
CMT PUBID : 1D800015309C0154F23524E0F7E39E707D1935A0
CMT MODE  : 00
CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1
CMT ROMID : 273F6D55DFAAF68F
CMT 1ST Boot OK
CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1
CMT FLID0 : 00EC22E8-00006921, Sam K8S2815ETB
CMT FLCNT : 00000000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO  : RAP3Gv3_algo.fg, Ver: 9.17.0
CMT KSIG0 : 5E8D0D504A0902E261268C14FCD8A2C9093523BC
CMT VPP   : Internal
DUAL LINE : True
CMT ALG Boot OK
APE 2ND Bt: helen3_2nd.fg, Ver: 1.35.0
APE FLID0 : 00EC00A1-00800015, Sam KAL00T00EA
APE FLCNT : 010100FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
APE 2ND Boot OK
APE ALG0  : h3_sam_nand_xsr.fg, Ver: 1.49.0
APE VPP   : Internal
APE KSIG1 : 5E8D0D504A0902E261268C14FCD8A2C9093523BC
DUAL LINE : True
APE ALG Boot OK
IMAGE : N73_userarea_4.0839.42.2.1.U02
APE NAND Erase Area: 0x04E20000-07C9FFFF
UAR FLASH ERASE OK, Time: 00:00
UAR FLASH WRITE OK, Time: 00:42
1ST BOOT  : C0,0C [Rm-133] [2.2.0.3]
APE ASICID: 17100708
APE MODE  : 00
APE PUBID : CEF00C555C712F8317294A54441D29AFDA8157A3
APE HASH  : 49A97E826B93BA20B7ED0B082475C005
APE ROMID : 1DFD66132C872FD4
CMT ASICID: 000000010000022600010006010C192101003000
EM 1 ID   : 00000295
EM 2 ID   : 00000B21
CMT PUBID : 1D800015309C0154F23524E0F7E39E707D1935A0
CMT MODE  : 00
CMT HASH  : BAF3A9C3DBFA8454937DB77F2B8852B1
CMT ROMID : 273F6D55DFAAF68F
CMT 1ST Boot OK
CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1
CMT FLID0 : 00EC22E8-00006921, Sam K8S2815ETB
CMT FLCNT : 00000000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO  : RAP3Gv3_algo.fg, Ver: 9.17.0
CMT KSIG0 : 5E8D0D504A0902E261268C14FCD8A2C9093523BC
CMT VPP   : Internal
DUAL LINE : True
CMT ALG Boot OK
APE 2ND Bt: helen3_2nd.fg, Ver: 1.35.0
APE FLID0 : 00EC00A1-00800015, Sam KAL00T00EA
APE FLCNT : 010100FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
APE 2ND Boot OK
APE ALG0  : h3_sam_nand_xsr.fg, Ver: 1.49.0
APE VPP   : Internal
APE KSIG1 : 5E8D0D504A0902E261268C14FCD8A2C9093523BC
DUAL LINE : True
APE ALG Boot OK
IMAGE : N73_rofx_4.0839.42.2.1_PRD.V05
APE NAND Erase Area: 0x03920000-04E1FFFF
PPM FLASH ERASE OK, Time: 00:00
Written: 1 Certificate(s)
PPM FLASH WRITE OK, Time: 01:49
Flashing Completed, Rebooting Mobile
UI Defaults Ok, Time: 00:00
Set UI Factory Defaults Ok, Time: 00:00
Set Full Factory Defaults Ok, Time: 00:00
Set Software Upgrade Defaults Ok, Time: 00:00
Set Security Ok, Time: 00:00
All Done, Time: 08:45

Вот инфо:

Код:

MCU SW  : V 05wk47v61.1 09-07-08 RM-133 (c) Nokia. 
APE Core: V 4.0839.42.2.1 27-09-2008 RM-133 
APE Var : V 4.0839.42.2.1-05 27-09-2008 RM-133 
Product : Nokia N73
Prd.Code: 0544984
Bpr.Code: 0527006
Prod.Sn : SBI474356
HW Vers : 6019
APE HW  : 1
APE Adsp: 256
EM VILMA: 15
EM BETTY: 21
RFIC Ver: 17191719
DSP Vers: scarfe_mc.05wk46v50p2
IMEI    : 355506-01-840666-7
SL Serv : SIMLOCK SERVER VERSION 63
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

Вот селфтест

Безымянный.png

Селфтест брался с чистой платы без камеры,без дисплея.С чем связаны эти ошибки селфа?

**Соломон1** · 18.01.2013, 11:34

А циклон не хочет шить его,хоть плата и голая,хотя инфо и бекапы делает вот лог,чек,инфо бекап и прощивка с ошибкой:

Код:

Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: CEF00C555C712F8317294A54441D29AFDA8157A3
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1D800015309C0154F23524E0F7E39E707D1935A0
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC22E800006921, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...
MCU Version V 05wk47v61.1
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 355506018406667
Mastercode 5241733716
IMEI Spare 3A55050681046606
IMEI SV 3355050681046676F8000000
PSN SBI474356
Product Code 0544984
Module Code 0202855
Basic Product Code 0527006
PSD 0000002200000000
RETU 15
TAHVO 21
AHNE 30
HW 6019
RFIC 17191719
DSP scarfe_mc.05wk46v50p2
Simlock Server SIMLOCK SERVER VERSION 63
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
Auto Selecting Flash Files on User Request...
Product Code: 0544984
This is Valid BB5 Product
Retrieving Variants for Product RM-133 - wait...
31 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...
Simlock Store not supported, not a PA_SL2 Phone
WMDRM Store not supported
Reading Security Block...
Security block OK and saved to "RM-133_355506018406667_18.01.2013_112835.SecurityBlock.PM"
"1D800015309C0154F23524E0F7E39E707D1935A0.C00045B2" Exists, That is good...
Storing Additional Data...
Checking Superdongle Key...
Encrypting Superdongle Key...
Storing Superdongle Key...
Checking CMLA Key...
Storing CMLA Key...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: CEF00C555C712F8317294A54441D29AFDA8157A3
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1D800015309C0154F23524E0F7E39E707D1935A0
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 1.0Mbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC22E800006921, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Searching for BootCode: DualLine 32Bit
helen3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.1.35.0, Algo: BB5
If software STUCK HERE with box TX LED lit, that means:
1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!)
2. Your cable is not TX2 Enabled!
3. Transmission error occured, try again
In either cases, you need to reconnect your box from USB.
FlashChip[0,APE]: 0x00EC00A100800015, Samsung, NAND
FlashContent[0,APE]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, NAND
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC00A1 (Samsung), Size: 128MBytes, VPP: 21V
h3_sam_nand_xsr.fg, Type: Algorithm, Rev: 0.1.49.0, Algo: OMAP1710 UNISTORE-II-1.2.1 ALG
Box VPP disabled
Internal APE Phone VPP Enabled
PAPUBKEYS Hash for APE: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud set to 5.0Mbits
Storing NPC...
CMT CCC Not Found
CMT HWC Not Found
Storing VARIANT...
CMT PARTNERC Not Found
Processing APE Part...
Storing Product Code...
Storing PSN...
Storing HWID...
APE NPC Not Found
APE CCC Not Found
APE HWC Not Found
APE VARIANT Not Found
APE PARTNERC Not Found
Restarting MCU...
RPL Saved OK
RPL backup thread finished, continuing...
Backing up simlock...
MCU Version V 05wk47v61.1
MCU Date 09-07-08
Product RM-133 (Nokia N73)
Manufacturer (c) Nokia.
IMEI 355506018406667
Mastercode 5241733716
Simlock backup OK, saved to RM-133_355506018406667_18.01.2013_112850.SLBackup.PM
Backup simlock thread finished, continuing...
Pre flash tasks finished, continuing...
Processing N73_4.0839.42.2.1_western_C00_PRD_cc.fpsx (CMT)...
Booting CMT...
APE_SYSTEM_ASIC_ID: 17100708
APE_ASIC_MODE_ID: 00
APE_PUBLIC_ID: CEF00C555C712F8317294A54441D29AFDA8157A3
APE_ROOT_KEY_HASH: 49A97E826B93BA20B7ED0B082475C00500000000
APE_BOOT_ROM_CRC: 1DFD6613
APE_SECURE_ROM_CRC: 2C872FD4
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1D800015309C0154F23524E0F7E39E707D1935A0
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
N73_4.0839.42.2.1_western_C00_PRD_cc.fpsx, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 51Kbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC22E800006921, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
Flashbus Write baud set to 5.0Mbits
Partitioning...
Partitioning OK
Started group flash erase
EraseArea[0,CMT]: 0x00080000-0x00731951, NOR
EraseArea[0,CMT]: 0x00000000-0x0005FFFF, NOR
EraseArea[0,CMT]: 0x001E0000-0x001FFFFF, NOR
EraseArea[0,CMT]: 0x00880000-0x00FEFFFF, NOR
Waiting 320s for erasure finish...
Erase taken 41.484s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT NOLO Certificate...
Writing CMT KEYS Certificate...
Writing CMT PRIMAPP Certificate...
Writing CMT PASUBTOC Certificate...
Writing CMT PAPUBKEYS Certificate...
Writing CMT UPDAPP Certificate...
Writing CMT ADL Certificate...
Writing CMT DSP0 Certificate...
Writing CMT MCUSW Certificate...
Programming Status OK!
All blocks written OK! Time taken 31.438s
Flashing Speed: 13073,19 kBit/S
Restarting MCU...
Processing N73_4.0839.42.2.1_western_C00_PRD_cc.fpsx (APE)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006010C192101003000
CMT_EM_ASIC_ID: 00000295
CMT_EM_ASIC_ID: 00000B21
CMT_PUBLIC_ID: 1D800015309C0154F23524E0F7E39E707D1935A0
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
N73_4.0839.42.2.1_western_C00_PRD_cc.fpsx, Type: Flash Image, Algo: BB5, BB5 ALGORITHM, BB5, OMAP1710 UNISTORE-II-1.2.1 ALG
Searching for BootCode: DualLine 32Bit
RAP3Gv3_2nd.fg, Type: 2nd Boot Loader, Rev: 0.10.42.0, Algo: BB5
Flashbus Write baud set to 51Kbits
Flashbus Read baud set to 98Kbits
Using OLD BB5 FLASHING PROTOCOL
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]: 0x00EC22E800006921, Samsung, NOR
FlashContent[0,CMT]: 00000000000000000000000000000000, NOR
FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC
Transmission Mode Requested: Single Line, 8 bit, Accepted: Single Line, 8 bit
Searching for BootCode: DualLine 32Bit
FlashChip 0x00EC22E8 (Samsung), Size: 16MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM
Flashbus Write baud set to 2.0Mbits
Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit
Box TX2 Data Pin set to: Service Pin 3
Box VPP disabled
Internal CMT Phone VPP Enabled
PAPUBKEYS Hash for CMT: 5E8D0D504A0902E261268C14FCD8A2C9093523BC
APE Subsystem Not Found
Processing Flash Image Failed -> Trying to program APE subsystem, but APE not exists
Failed to Process all Image files -> Failed to process N73_4.0839.42.2.1_western_C00_PRD_cc.fpsx

**Соломон1** · 18.01.2013, 12:03

И теперь и УФС снова не хочет шить вот скриншот:

Безымянный.png

**asg-gealt** · 18.01.2013, 12:21

Trying to program APE subsystem, but APE not exists

Нет смысла его пытаться шить. Замерить vcorea, проверить N6515. Думаю APE-флэшка труп.

**Соломон1** · 19.01.2013, 10:21

Vcorea 1.39V на L6505,C7565 есть.

---------- Сообщение добавлено в 08:21 ---------- Предыдущее было в 08:06 ----------

Вообщем не совсем есть то появляется 1,38V то исчезает,после того как подержал во вкл.состоянии плату около минуты,стабильно появился 1,39V Vcorea,и после этого подключил к УФС чек проходит нормально.Значит проблема в N6515,откуда его можно снять?

**Daemon pisec** · 19.01.2013, 10:29

Сообщение от Соломон1

Vcorea 1.39V на L6505,C7565 есть.

---------- Сообщение добавлено в 08:21 ---------- Предыдущее было в 08:06 ----------

Вообщем не совсем есть то появляется 1,38V то исчезает,после того как поддержал во вкл.состоянии плату около минуты,стабильно появился 1,39V Vcorea,и после этого подключил к УФС чек проходит нормально.Значит проблема в N6515,откуда его можно снять?

N73-N6515=E61-N4200,E65-N4200,E60-N4200, E70-N4200,N71-N4200,N72-N4200,N77-N4200,N80-N4200,N91-N4200,N92-N4200

Сообщение от Соломон1

А может это быть из-за ОМАПА?

Легко. Только лучше микру замените сначала, а то омапы нежинки...

**Соломон1** · 19.01.2013, 10:43

А может это быть из-за ОМАПА?

**asg-gealt** · 19.01.2013, 11:20

Сообщение от Соломон1

А может это быть из-за ОМАПА?

Так можно долго гадать. Пока не поменяешь - не узнаешь.

**Соломон1** · 19.01.2013, 11:46

Омап и его Флэш с каких тел. подходит по взаимозаменяемости на N73?

**wasbar** · 19.01.2013, 16:27

Так было запитал от бп поиграл напругой и пршивка пошла.

Тема: N73 темнеет экран и выключается

Опции темы

Отображение

N73 темнеет экран и выключается

Спасибо сказали:

2 участника(ов) поблагодарили Daemon pisec за его сообщение:

Похожие темы

ke970 темнеет экран

6085 темнеет экран

B2050 в темнеет экран

C35 темнеет экран

Ваши права