5130 не включается

**pundev1** · 19.05.2012, 12:26

пришло данное тело при включении пишет нокиа,птом чуть выше середины экрана 4ре темные полосы на белом фоне,потом белеет и висит с минуту и тухнет....
прошил-все тоже.
прошил со стиранием-тоже самое.
перекатал без изменений.
пара?

Код:

Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1CA0021288980056E231451828587FC5BF4ADCB2
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
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]: 0x00EC240000008A31, 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 0x00EC2400 (Samsung), Size: 64MBytes, 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: 0C917F11196FDB7378C18EF7260698CA4489DCA0
APE Subsystem Not Found
Flashbus Write baud set to 5.0Mbits
Erasing flash chip...
Started group flash erase
EraseArea[0,CMT]: 0x00000000-0x03FFFFFF, NOR
Waiting 640s for erasure finish...
Erase taken 181.15s
Restarting MCU...
BB5 Full Erase Finished!
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1CA0021288980056E231451828587FC5BF4ADCB2
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, 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 0x00EC2400 (Samsung), Size: 64MBytes, 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
Warning: PAPUBKEYS Hash Missing!
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...
Processing pre flash tasks...
Pre flash tasks finished, continuing...
Processing rm495__07.95.mcusw (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1CA0021288980056E231451828587FC5BF4ADCB2
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm495__07.95.mcusw, Type: Flash Image, Algo: BB5, BB5 ALGORITHM
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]: 0x00EC240000008A31, Samsung, NOR
FlashContent[0,CMT]: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, 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 0x00EC2400 (Samsung), Size: 64MBytes, 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
Warning: PAPUBKEYS Hash Missing!
Flashbus Write baud set to 5.0Mbits
Sending Certificates...
Certificates OK
Started group flash erase
EraseArea[0,CMT]: 0x00000000-0x000006BF, NOR
EraseArea[0,CMT]: 0x000006C0-0x0001FFFF, NOR
EraseArea[0,CMT]: 0x00040000-0x000BFFFF, NOR
EraseArea[0,CMT]: 0x000C0000-0x0013FFFF, NOR
EraseArea[0,CMT]: 0x00140000-0x0137FFFF, NOR
EraseArea[0,CMT]: 0x01380000-0x0151FFFF, NOR
Waiting 320s for erasure finish...
Erase taken 4.875s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Writing CMT NOLO Certificate...
Writing CMT KEYS Certificate...
Writing CMT PRIMAPP Certificate...
Writing CMT PASUBTOC Certificate...
WARNING: CMT PAPUBKEYS Hash is Empty, writing first found PAPUBKEYS
Writing CMT PAPUBKEYS Certificate...
Writing CMT UPDAPP Certificate...
Writing CMT DSP0 Certificate...
Writing CMT MCUSW Certificate...
Programming Status OK!
All blocks written OK! Time taken 66.110s
Flashing Speed: 2308,98 kBit/S
Restarting MCU...
Processing rm495__07.95.mcusw (APE)...
Processing rm495__07.95.ppm_ej (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1CA0021288980056E231451828587FC5BF4ADCB2
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm495__07.95.ppm_ej, Type: Flash Image, Algo: BB5, BB5 ALGORITHM
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]: 0x00EC240000008A31, 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 0x00EC2400 (Samsung), Size: 64MBytes, VPP: 9V
RAP3Gv3_algo.fg, Type: Algorithm, Rev: 0.10.40.0, Algo: BB5 ALGORITHM

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: 0C917F11196FDB7378C18EF7260698CA4489DCA0
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x01520000-0x01DBFFFF, NOR
Waiting 320s for erasure finish...
Erase taken 1.984s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 23.141s
Flashing Speed: 2274,97 kBit/S
Restarting MCU...
Processing rm495__07.95.ppm_ej (APE)...
Processing rm495__07.95.image_ej_uk_red (CMT)...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1CA0021288980056E231451828587FC5BF4ADCB2
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT_BOOT_ROM_CRC: 273F6D55
CMT_SECURE_ROM_CRC: DFAAF68F
CMT Ready!
rm495__07.95.image_ej_uk_red, Type: Flash Image, Algo: BB5, BB5 ALGORITHM
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]: 0x00EC240000008A31, 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 0x00EC2400 (Samsung), Size: 64MBytes, 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: 0C917F11196FDB7378C18EF7260698CA4489DCA0
Flashbus Write baud set to 5.0Mbits
Started group flash erase
EraseArea[0,CMT]: 0x01DC0000-0x0215FFFF, NOR
EraseArea[0,CMT]: 0x02160000-0x03FBFFFF, NOR
Waiting 320s for erasure finish...
Erase taken 7.813s
Writing all blocks...
Initializing TurboCache...
TurboCache Loaded!
Programming Status OK!
All blocks written OK! Time taken 37.750s
Flashing Speed: 2419,43 kBit/S
Restarting MCU...
Processing rm495__07.95.image_ej_uk_red (APE)...
All images processed OK! Processing post flash tasks...
Setting Factory Defaults...
Factory defaults OK
Reading info...
MCU Version V 07.95
MCU Date 03-02-10
Product RM-495 (Nokia 5130 XpressMusic)
Manufacturer (c) Nokia
IMEI 12345610654321?
IMEI Spare 1A32541660452301
IMEI SV 1332541660452341F8000000
PPM V 07.95, 03-02-10, RM-495, (c) Nokia , EJ
CNT Content: ej_uk_red, V 07.95, 03-02-10, RM-495, (c) Nokia ,
PSN 0
PSD 0000000000000000
LPSN 0
RETU 16
TAHVO 22
AHNE 30
RFIC 06540601
DSP ICPR72_10w01
LCD SEIKO
BT 2222-302
Failed to read info -> Failed to read SP info
Read info thread finished, continuing...
Post flash tasks finished!
Flashing successfully finished!
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1CA0021288980056E231451828587FC5BF4ADCB2
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
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]: 0x00EC240000008A31, 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 0x00EC2400 (Samsung), Size: 64MBytes, 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: 0C917F11196FDB7378C18EF7260698CA4489DCA0
APE Boot skipped on user request
Flashbus Write baud set to 5.0Mbits
Restarting MCU...
Skipping RPL decryption...
Parsing decrypted RPL...
Processing FBUS Part...
Writing PSN...
Writing Simlock...
Handling as SL3 Simlock Data
Handling as SIMLOCK1 Format
Reading Security Block...
Security block OK and saved to "RM-495_12345610654321_19.05.2012_101447.SecurityBlock.PM"
15 Digits NCK Found
Simlock ACCEPTED OK !
Writing Superdongle key...
Superdongle Key ACCEPTED OK !
Processing FLASHBUS Part...
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000010000022600010006030C192101033000
CMT_EM_ASIC_ID: 00000296
CMT_EM_ASIC_ID: 00000B22
CMT_PUBLIC_ID: 1CA0021288980056E231451828587FC5BF4ADCB2
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
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]: 0x00EC240000008A31, 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 0x00EC2400 (Samsung), Size: 64MBytes, 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: 0C917F11196FDB7378C18EF7260698CA4489DCA0
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!

что то может не от пары зависящее?

**pundev1** · 19.05.2012, 12:26

вот инфа-в то сообщерние не влезла

Код:

MCU Version	V 07.95
MCU Date	03-02-10
Product		RM-495 (Nokia 5130 XpressMusic)
Manufacturer	(c) Nokia            
IMEI		353421047836052
Mastercode	3110127534
IMEI Spare	3A35240174380605
IMEI SV		3335240174380645F8000000
PPM		V 07.95, 03-02-10, RM-495, (c) Nokia            , EJ
CNT		Content: ej_uk_red, V 07.95, 03-02-10, RM-495, (c) Nokia            , 
PSN		0
PSD		0000000000000000
LPSN		0
RETU		16
TAHVO		22
AHNE		30
RFIC		06540601
DSP		ICPR72_10w01
LCD		SEIKO
BT		2222-302
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

**13579** · 19.05.2012, 12:32

n6000 и камеру проверь

**uo5oq** · 19.05.2012, 12:33

Если после полного стирания и записи только SW не работает нормально несколько минут с дефолтным IMEI минут - то точно железо и не обязательно пара.

**pundev1** · 19.05.2012, 12:38

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

n6000 и камеру проверь

блютуз и камера сняты.......
кстати есть один в один 2700 и тоже самое....

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

Если после полного стирания и записи только SW не работает нормально несколько минут с дефолтным IMEI минут - то точно железо и не обязательно пара.

после стирания тоже самое..то что железо понятно,а вот что именно?

**master25** · 19.05.2012, 12:38

А где селфтесты? Вродь не маленький уже.
Проверить все что висит на квадратной шине.

**pundev1** · 19.05.2012, 12:45

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

А где селфтесты? Вродь не маленький уже.
Проверить все что висит на квадратной шине.

Код:

Passed		ST_EAR_DATA_LOOP_TEST
Passed		ST_SIM_CLK_LOOP_TEST
Passed		ST_SIM_IO_CTRL_LOOP_TEST
Passed		ST_SLEEP_X_LOOP_TEST
Passed		ST_UEM_CBUS_IF_TEST
Passed		ST_KEYBOARD_STUCK_TEST
Failed		ST_CAMERA_IF_TEST
Passed		ST_BACKUP_BATT_TEST
Passed		ST_LCD_TEST
Passed		ST_LPRF_IF_TEST
Passed		ST_LPRF_AUDIO_LINES_TEST
Passed		ST_CURRENT_CONS_TEST
Passed		ST_RADIO_TEST
Passed		ST_BACKLIGHT_TEST
Passed		ST_SIM_LOCK_TEST
Passed		ST_SECURITY_TEST
Passed		ST_BT_WAKEUP_TEST
Passed		ST_HOOKINT_TEST
Passed		ST_TAHVOINT_TEST
Passed		ST_BTEMP_TEST
Passed		ST_IIC_TEST
Passed		ST_EXT_DEVICE_TEST
Passed		ST_CDSP_SLEEPCLK_FREQ_TEST
Failed		ST_CDSP_SLEEPCLOCK_FREQ_TEST
Failed		ST_CDSP_RF_BB_IF_TEST
Failed		ST_CDSP_RF_SUPPLY_TEST
Failed		ST_CDSP_TX_PLL_PHASE_LOCK_TEST
Failed		ST_CDSP_RX_IQ_LOOP_BACK_TEST
Failed		ST_CDSP_GSM_TX_POWER_TEST

а толку?на ай2си визуально все ок....

**13579** · 19.05.2012, 12:47

n6000 как раз и висит на I2C, возможно без нее тело не будет запускаться.
Обычно если тело критично относится к ошибкам на I2C, то в локал оно не входит при неисправности на шине.

**pundev1** · 19.05.2012, 12:48

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

n6000 как раз и висит на I2C, возможно без нее тело не будет запускаться.
Обычно если тело критично относится к ошибкам на I2C, то в локал оно не входит при неисправности на шине.

я ж писал что снимал и блютуз и камеру.
локал устойчив.
на обоих телах флешка самсунг......

**tihiy_grom** · 19.05.2012, 12:56

Ну замените FLASH, тем более все что сертификаты есть под этот процессор

**pundev1** · 19.05.2012, 13:35

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

Ну замените FLASH, тем более все что сертификаты есть под этот процессор

мда..никогда б не подумал.
заменил флешь-все гуд,всем спасибо.

Тема: 5130 не включается

Опции темы

Отображение