PDA

Просмотр полной версии : N79 умер после erase

sergiy
17.10.2012, 18:38
Подскажите что делать. Купил телефон с ошибкой при самотестировании решил его стереть Fenix key. Прошил файлом BB5Erase_UNI_rapido и после этого телефон перестал прошиваться.
kiv6666
17.10.2012, 19:11
Подскажите что делать. Купил телефон с ошибкой при самотестировании решил его стереть Fenix key. Прошил файлом BB5Erase_UNI_rapido и после этого телефон перестал прошиваться.
теперь его надо шить по FBUS и логи показать
sergiy
18.10.2012, 10:05
Software version: 1.2.1
Detected card sn: 79BB8E58E52F
Card version: 01.00
Life counter: 100%
Fenix Reader SW version: 0.0.2
Connection interface is set to USB now.
Connecting to UFS3 SarasSoft #1 (SN: 72248)
UFxBoot V2.2 (c) SarasSoft 2003
UFS_USB V2.6 (c) SarasSoft 2005
Connected to UFS interface.
You are using old version of UFS firmware. We recommend you to update your box to the highest version (V 2.8)
Connection interface is set to UFS now.
Job's finished successfully!
Looking for flash files
Flash files found for selected product
Flashing started
Setting flash mode
Reading CMT boot data...

CMT Boot Data
--------------
Asic ID : 000000010000022600010006400C192101031103
Public ID : 1A100109A6BE0158601CCA0BBFFA62964DE174D9
Hash : CAEEBB65D3C48E6DC73B49DC5063A2EE
Hardware ID: 400C192101031103

Booting CMT
Sending 2ND...
Sending Algo...

CMT Flash info:
Vendor : 00EC [SAMSUNG (SEC)]
Product: 0040 [KAT00F00RA]
APE Flash info:
No APE Flash detected

Partitioning file: RM-348_32.001_prd.core.fpsx
Erasing MCUSW Flash area
Erasing CMT area 00040000 - 00082FFF
Erasing CMT area 00083400 - 003FFFFF
Erasing CMT area 00800000 - 00D5FFFF
Erasing CMT area 00D60000 - 0A95FFFF
Erasing CMT partition
Erasing PPM Flash area
Erasing CMT area 08260000 - 09F5FFFF
Erasing CNT Flash area
Erasing CMT area 0A960000 - 0F71FFFF
Erasing CMT area 00400000 - 007FFFFF
Erasing CMT area 09F60000 - 0A95FFFF
Flashing MCUSW
Cannot write data buffer
Job's finished with errors!
kiv6666
18.10.2012, 10:25
попробуй через HWK SUITE без Fenix key
sergiy
18.10.2012, 14:57
не могу установить HWK!
kiv6666
18.10.2012, 19:39
не могу установить HWK!
надо установить HWK Update Client 2.2.0 зарегистрировать BOX и потом уже установить HWK SUITE 2.2.0
sergiy
18.10.2012, 21:27
Authenticating on server...
Authentication stage error: Connection Closed Gracefully.

Интернет мобильный
что делать?
sergiy
19.10.2012, 19:00
попробуй через HWK SUITE без Fenix key

Спасибо большое телефон ожил до прежнего состояния. Теперь пишет Phone start-up failed.Можно его оживить с помощью HWK или Fenix key?
kiv6666
19.10.2012, 19:02
Спасибо большое телефон ожил до прежнего состояния. Теперь пишет Phone start-up failed.Можно его оживить с помощью HWK или Fenix key? Теперь надо посмотреть логи.Желательно логи Fenix key
sergiy
19.10.2012, 19:28
Connection interface is set to UFS now.
Job's finished successfully!
Checking connection...
Powering on the phone
Reading phone info
Product type: RM-348
MCU SW Version:
V ICPR72_09w18.4
14-10-09
RM-348
(c) Nokia
Content Pack Version:
V 53.32.2009.43.xx PRD
Imei: 356387022761473
Product code: 0565708
Simlock status:
Profile bits: 0000000000000000
Config key: 2440700000000000
Fbus codes typed: 0/10
Key codes typed: 0/3
Block 1:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Block 2:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Block 3:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Block 4:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Block 5:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Block 6:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Block 7:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Analyzing profile bits...
This phone can be unlocked via keyboard and fbus
Looking for flash files
Flash files found for selected product
Job's finished successfully!
Setting flash mode
Reading CMT boot data...

CMT Boot Data
--------------
Asic ID : 000000010000022600010006400C192101031103
Public ID : 1A100109A6BE0158601CCA0BBFFA62964DE174D9
Hash : CAEEBB65D3C48E6DC73B49DC5063A2EE
Hardware ID: 400C192101031103

Booting CMT
Sending 2ND...
Sending Algo...

CMT Flash info:
Vendor : 00EC [SAMSUNG (SEC)]
Product: 0040 [KAT00F00RA]
APE Flash info:
No APE Flash detected

Job's finished successfully!
Security analysis procedure started
Setting flash mode
Reading CMT boot data...

CMT Boot Data
--------------
Asic ID : 000000010000022600010006400C192101031103
Public ID : 1A100109A6BE0158601CCA0BBFFA62964DE174D9
Hash : CAEEBB65D3C48E6DC73B49DC5063A2EE
Hardware ID: 400C192101031103

Sending 2ND...
Initializing...
Booting loader...
Reading secure data...
Powering the phone
Reading phone data
Analyzing block: SUPERDONGLE
SUPERDONGLE: Checksum is INVALID.
Analyzing block: SIMLOCK
SIMLOCK: Checksum is INVALID.
Analyzing block: TIMESTAMPS
TIMESTAMPS: Checksum is INVALID.
Analyzing block: CMLA
CMLA does not exist!
Analyzing block: ECC
ECC does not exist!
Analyzing block: DIV
DIV does not exist!
Executing security self tests...
ST_SIM_LOCK_TEST: PASSED!
ST_SECURITY_TEST: FAILED!
Job's finished successfully!
kiv6666
19.10.2012, 19:30
ST_SECURITY_TEST: FAILED! вот это твоя проблема.Надо записать PM 1-309 поле с SX4 авторизацией
sergiy
19.10.2012, 19:34
Checking connection...
Powering the phone
SX4 Auth procedure started
Authenticating client...
An error occurred: Cannot perform SX4 auth. Possible reason: SD keys has been repaired in this phone.
Job's finished with errors!
kiv6666
19.10.2012, 19:36
сделай Repair SD
sergiy
19.10.2012, 19:39
Это оно?
Repairing SD keys started
Setting flash mode
Reading CMT boot data...

CMT Boot Data
--------------
Asic ID : 000000010000022600010006400C192101031103
Public ID : 1A100109A6BE0158601CCA0BBFFA62964DE174D9
Hash : CAEEBB65D3C48E6DC73B49DC5063A2EE
Hardware ID: 400C192101031103

Sending 2ND...
Initializing...
Booting loader...
Reading secure data...
Powering the phone
Writing SD keys...
Job's finished successfully!
kiv6666
19.10.2012, 19:41
Советую найти BEST или ATF и все легко получится
sergiy
19.10.2012, 19:45
А HWK ничем не поможет?
kiv6666
19.10.2012, 19:47
А HWK ничем не поможет? UFS не востанавливает секьюрити и SD
UO5OQ
19.10.2012, 19:47
Это оно?
Repairing SD keys started
Setting flash mode
Reading CMT boot data...

CMT Boot Data
--------------
Asic ID : 000000010000022600010006400C192101031103
Public ID : 1A100109A6BE0158601CCA0BBFFA62964DE174D9
Hash : CAEEBB65D3C48E6DC73B49DC5063A2EE
Hardware ID: 400C192101031103

Sending 2ND...
Initializing...
Booting loader...
Reading secure data...
Powering the phone
Writing SD keys...
Job's finished successfully!
Оно.
А теперь сделайте Locаl SX4 и запишите PM 1 и 309 поля.
HWK тут не поможет ничем, но у Fenix-KEY должна быть такая функция.
sergiy
19.10.2012, 19:57
Сделал

Initialize authentication
Authenticating [STEP1]
Authenticating [STEP2]
Finalizing
Job's finished successfully!
Checking connection...
Writing field 1
Writing field 309
Job's finished successfully!

Что должно получиться?
kiv6666
19.10.2012, 19:58
Лог INF покажи
sergiy
19.10.2012, 20:04
Checking connection...
Powering on the phone
Reading phone info
Product type: RM-348
MCU SW Version:
V ICPR72_09w18.4
14-10-09
RM-348
(c) Nokia
Content Pack Version:
V 53.32.2009.43.xx PRD
Imei: 356387022761473
Product code: 0565708
Simlock status:
Profile bits: 0000000000000000
Config key: 2440700000000000
Fbus codes typed: 0/10
Key codes typed: 0/3
Block 1:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Block 2:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Block 3:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Block 4:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Block 5:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Block 6:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Block 7:
Lock 1: OPEN(IMSI); TYPE: 5; DATA: FF FF FF
Lock 2: OPEN(GID1); TYPE: 1; DATA: FF FF
Lock 3: OPEN(GID2); TYPE: 1; DATA: FF FF
Lock 4: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF
Lock 5: OPEN(IMSI); TYPE: 5; DATA: FF FF FF FF FF FF FF FF

Analyzing profile bits...
This phone can be unlocked via keyboard and fbus
Looking for flash files
Flash files found for selected product
Job's finished successfully!
kiv6666
19.10.2012, 20:08
покажи лог
CMT Boot Data
--------------
Asic ID : 000000010000022600010006400C192101031103
Public ID : 1A100109A6BE0158601CCA0BBFFA62964DE174D9
Hash : CAEEBB65D3C48E6DC73B49DC5063A2EE
Hardware ID: 400C192101031103

Sending 2ND...
Initializing...
Booting loader...
Reading secure data...
Powering the phone
Reading phone data
Analyzing block: SUPERDONGLE
SUPERDONGLE: Checksum is INVALID.
Analyzing block: SIMLOCK
SIMLOCK: Checksum is INVALID.
Analyzing block: TIMESTAMPS
TIMESTAMPS: Checksum is INVALID.
Analyzing block: CMLA
CMLA does not exist!
Analyzing block: ECC
ECC does not exist!
Analyzing block: DIV
DIV does not exist!
Executing security self tests...
ST_SIM_LOCK_TEST: PASSED!
ST_SECURITY_TEST: FAILED!
Job's finished successfully!
sergiy
19.10.2012, 20:15
CMT Boot Data
--------------
Asic ID : 000000010000022600010006400C192101031103
Public ID : 1A100109A6BE0158601CCA0BBFFA62964DE174D9
Hash : CAEEBB65D3C48E6DC73B49DC5063A2EE
Hardware ID: 400C192101031103

Sending 2ND...
Initializing...
Booting loader...
Reading secure data...
Powering the phone
Reading phone data
Analyzing block: SUPERDONGLE
SUPERDONGLE: Checksum is INVALID.
Analyzing block: SIMLOCK
SIMLOCK: Checksum is INVALID.
Analyzing block: TIMESTAMPS
TIMESTAMPS: Checksum is INVALID.
Analyzing block: CMLA
CMLA: Checksum is INVALID.
Analyzing block: ECC
ECC does not exist!
Analyzing block: DIV
DIV does not exist!
Executing security self tests...
ST_SIM_LOCK_TEST: PASSED!
ST_SECURITY_TEST: FAILED!
Job's finished successfully!
kiv6666
19.10.2012, 20:17
SUPERDONGLE: Checksum is INVALID.
ST_SECURITY_TEST: FAILED! не востановил
sergiy
19.10.2012, 20:21
Может MX key поможет?
se13
19.10.2012, 20:22
Ищите ATF и сделайте нормально Repair SD потом запись PM с SX4 авторизации и все станет на место
UO5OQ
19.10.2012, 20:26
Может MX key поможет?
Странно, что Fenix-KEY не восстановил STF
MX-KEY HTI тоже имеет эту ф-цию, кнопка Recover CERT

http://www.uo5oq.com/forum/attachment.php?attachmentid=1486&stc=1&d=1350667577
sergiy
19.10.2012, 20:29
Спасибо всем большое! На сегодня заканчиваю свое торможение!!!
kiv6666
19.10.2012, 20:33
Павел в MX ему нужно вкладка service - PM Super SD Auth или Repair SD. Но простым MXKEY без HTI этого не сделать
UO5OQ
19.10.2012, 20:38
Павел в MX ему нужно вкладка service - PM Super SD Auth или Repair SD. Но простым MXKEY без HTI этого не сделать
Ну я и написал, что в MX-KEY HTI есть эта ф-ция.
И для исправления STF у него ещё есть кнопка Recover CERT