E52 RM-469 "умер" на руках.
#1
Доброго времени суток Всем.
Пришел E52 моргалик. Похоже на прошивку.
Phoenix прошил полностью, сделал post-flash, все ок, только ругнулся что-то типа "не смог сохранить некоторые бэкапы..."(логов к сожалению не сохранил)
После этого аппарат включился, но показывал "Contact Retailer".
Для достоверности подключил по F-bus к Cyclon`у :
Info
Развернуть для просмотра
Код:
Initializing FBUS...
All initialized - Ready to work
MCU Version V ICPR82_10w22.10
MCU Date 03-01-11
Product RM-469 (Nokia E52)
Manufacturer (c) Nokia
IMEI 355216034017403
Mastercode 3457741221
IMEI Spare 3A55120643104700
IMEI SV 3355120643104750F1000000
PSN SEL643956
Product Code 0592471
Basic Product Code 0590828
PSD 0000000000000000
LPSN 0
WLAN MAC 1886AC77C258
RETU 40
TAHVO 00
AHNE 11
HW 6000
RFIC |Vapaus_5.1 | Aura_?.?
DSP ICPR82_10w22.7
Failed to read info -> Failed to read SP info
[свернуть]
Security Analysis
Развернуть для просмотра
Код:
Started Phone Security Analysis...
MCU Version V ICPR82_10w22.10
MCU Date 03-01-11
Product RM-469 (Nokia E52)
Manufacturer (c) Nokia
IMEI 355216034017403
Mastercode 3457741221
Reading Security Block...
"RM-469_355216034017403_06.04.2011_135449.SecurityBlock.PM"
Step 1 : Testing SIMLOCK
-- SIMLOCK PROBLEM --
-- SIMLOCK PROBLEM --
Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED!
To repair simlock area, Select Unlock method : "RPL CALCULATION",
And then click DIRECT UNLOCK. SL Area will be re-formatted.
-- SIMLOCK PROBLEM --
Step 2 : Testing SECURITY
SECURITY SEFLTEST PASSED OK!
Step 3 : Analyzing Security Block
"0F40010937640344876D31D262A2A358DB47CE31.C0002F96" 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!
[свернуть]
PM read
Развернуть для просмотра
Код:
Starting PM read in range 0-512...
[1] Reading 27 records
[1,0] Reading 114 bytes
[1,2] Reading 10 bytes
[1,4] Reading 110 bytes
[1,6] Reading 10 bytes
[1,7] Reading 214 bytes
[1,8] Reading 110 bytes
[1,13] Reading 10 bytes
[1,16] Reading 208 bytes
[1,18] Reading 208 bytes
[1,20] Reading 208 bytes
[1,22] Reading 16 bytes
[1,23] Reading 4 bytes
[1,24] Reading 84 bytes
[1,26] Reading 110 bytes
[1,28] Reading 10 bytes
[1,29] Reading 10 bytes
[1,31] Reading 208 bytes
[1,33] Reading 36 bytes
[1,34] Reading 376 bytes
[1,35] Reading 16 bytes
[1,39] Reading 36 bytes
[1,40] Reading 16 bytes
[1,41] Reading 182 bytes
[1,42] Reading 4 bytes
[1,43] Reading 36 bytes
[1,44] Reading 182 bytes
[1,45] Reading 182 bytes
[2] Reading 1 records
[2,0] Reading 2080 bytes
[4] Reading 6 records
[4,1] Reading 1020 bytes
[4,3] Reading 10 bytes
[4,4] Reading 8 bytes
[4,5] Reading 8 bytes
[4,9] Reading 5 bytes
[4,28] Reading 2 bytes
[8] Reading 8 records
[8,0] Reading 2 bytes
[8,1] Reading 16 bytes
[8,2] Reading 16 bytes
[8,3] Reading 128 bytes
[8,4] Reading 128 bytes
[8,8] Reading 8 bytes
[8,9] Reading 8 bytes
[8,10] Reading 32 bytes
[11] Reading 5 records
[11,0] Reading 4 bytes
[11,1] Reading 4 bytes
[11,2] Reading 4 bytes
[11,3] Reading 4 bytes
[11,4] Reading 1058 bytes
[12] Reading 1 records
[12,0] Reading 102 bytes
[26] Reading 2 records
[26,0] Reading 16 bytes
[26,1] Reading 68 bytes
[31] Reading 1 records
[31,4] Reading 16 bytes
[44] Reading 1 records
[44,0] Reading 1 bytes
[50] Reading 1 records
[50,0] Reading 2 bytes
[54] Reading 1 records
[54,0] Reading 2 bytes
[88] Reading 1 records
[88,0] Reading 36 bytes
[96] Reading 2 records
[96,0] Reading 2 bytes
[96,1] Reading 20 bytes
[107] Reading 6 records
[107,0] Reading 41 bytes
[107,1] Reading 89 bytes
[107,2] Reading 89 bytes
[107,3] Reading 70 bytes
[107,25] Reading 236 bytes
[107,26] Reading 12 bytes
[117] Reading 11 records
[117,0] Reading 4 bytes
[117,1] Reading 3 bytes
[117,2] Reading 6 bytes
[117,3] Reading 1 bytes
[117,4] Reading 9 bytes
[117,5] Reading 10 bytes
[117,6] Reading 8 bytes
[117,8] Reading 104 bytes
[117,13] Reading 3 bytes
[117,14] Reading 3 bytes
[117,16] Reading 40 bytes
[120] Reading 4 records
[120,0] Reading 944 bytes
[120,1] Reading 160 bytes
[120,2] Reading 130 bytes
[120,3] Reading 112 bytes
[153] Reading 7 records
[153,0] Reading 68 bytes
[153,1] Reading 68 bytes
[153,2] Reading 68 bytes
[153,3] Reading 68 bytes
[153,4] Reading 68 bytes
[153,5] Reading 68 bytes
[153,6] Reading 68 bytes
[193] Reading 4 records
[193,2] Reading 8 bytes
[193,3] Reading 32 bytes
[193,4] Reading 32 bytes
[193,9] Reading 64 bytes
[217] Reading 1 records
[217,0] Reading 32 bytes
[239] Reading 7 records
[239,0] Reading 2 bytes
[239,1] Reading 3284 bytes
[239,2] Reading 3284 bytes
[239,3] Reading 3284 bytes
[239,4] Reading 3284 bytes
[239,5] Reading 3284 bytes
[239,6] Reading 218 bytes
Failed to read PM -> Failed to read PM Record 239,6
[свернуть]
Эти строки:
=========================
Failed to read info -> Failed to read SP info
Phone have failed SIMLOCK Test, that means Simlock Area is DAMAGED!
=========================
ясно указывают что повреждена сим-лок зона и выход - заказ РПЛ....
НО вот эта строка:
=========================
Failed to read PM -> Failed to read PM Record 239,6
=========================
навела на мысль, что возможны механические повреждения бутерброда....
А следовательно возможны проблемы при записи RPL, SX4 и записи PM`а.
Было принято решение прогреть бутер и gazoo...
При съеме экрана треснула внутрення батарейка.
Аппарат был аккуратно прогрет.
После этого - не включается (только вибро, ток до 100 мА, затем падает до 30, через 10 сек падает в 0).
На любые манипуляции по F-bus cyclone реагирует одинаково :
Развернуть для просмотра
Код:
Initializing FBUS...
All initialized - Ready to work
Booting CMT...
CMT_SYSTEM_ASIC_ID: 000000030000022600010007600C192102011104
CMT_EM_ASIC_ID: 00001040
CMT_EM_ASIC_ID: 00001030
CMT_PUBLIC_ID: 0F40010937640344876D31D262A2A358DB47CE31
CMT_ASIC_MODE_ID: 00
CMT_ROOT_KEY_HASH: 25B977A055BE9B5DEC0C38A2A279C695
CMT_SECURE_ROM_CRC: 37BE26FA
CMT Ready!
Searching for BootCode: DualLine 32Bit
RAPUv11_2nd.fg, Type: 2nd Boot Loader, Rev: 768.10.48.1, 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
CBUS Request Error -> CBUS Response wrong header
Prepare phone failed with message -> Failed to get CMT Configuration
[свернуть]
Полный ребол проц-флэшь, gazoo, N3301, замена gazoo, замена N3301, замена кварца (возле газоо), ребол RF-проца результата не дали. Вторичные напряжения в норме.
При всем этом аппарат прошивается фениксом по usb в dead-mode, ругаясь на :
================================================== ========
WARNING: Asic CMT: NAND status reported bad blocks
================================================== ========
и не делая пост-флэшь. Естственно аппарат не входит ни в тест, ни в локал и не включается (вибро и всё...)
Клиент уже задрал.. Требует вернуть хотяб в том состоянии, в котором здавал... (включающийся аппарат с "контакт ретайлером" он видел).
Прочитав кучу тем на разных форумах узнал что часто "умирают" некоторые сектора флэшки. Из доноров - только 6700.
Собственно вопросы:
1. Может ли из-за хреновой флэши шиться по usb, НО не видиться по F-bus???
2. Подойдет ли флэшька с 6700 , если они разного типа? (фотки приатачены)
3. Может я что-то пропустил или незаметил??
4. посоветуйте чё нибудь - у меня мысли просто закончились....
E52-flash
6700-flash
Последние файлы
