Dead Asha 302 after log read - GSM-Forum

hoze!!! · 09-23-2013, 08:48

After trying to read SL3 log with logger asha 302 is dead. After trying to flash > Update server code loaded.
ERROR: Loader not responding !

Phone is new!!!

Some help maybe ?

.::ZUBER::. · 09-23-2013, 10:40

Bro.

May be something went wrong while trying to read Logs,

Contact Nokia Service Center if in Warranty.

BR,
ZUBER

hoze!!! · 09-23-2013, 10:58

Hmm..ok, but what can go wrong on reading log from phone ? Is there than maybe some safer reading ???

sahil2000ind · 09-23-2013, 11:27

@zuber

HOW CAN SOME THING CAN GO WRONG IN READING LOGS?
CAN U EXPLAIN MORE

I HAVE SEEN MANY USER HAVING PROBLEM WITH ASHA PHONES EVEN I TOO HAVE FACED PROBLEM IN FLASHING AND UNLOCKING ASHA PHONE
THATS THE BUG IN MX-KEY SOFTWARE.

@hoze!!!

PLS TRY TO FLASH URE PHONE WITH SAME PRODUCT CODE AGAIN WITH MX-KEY OR SOME OTHER NOKIA FLASHER IF U HAVE
ALSO PLS POST RESULTS

I HAVE SEENS SOME MEMBERS THAT FACED PROBLEM WITH ASHA PHONE IN MX-KEY SOLVED THEIR PROBLEM WITH OTHER NOKIA FLASHERS

ALSO PLS MAKE SURE U HAVE FULLY CHARGED BATTERY

WBR
sahil2000ind

.::ZUBER::. · 09-23-2013, 11:28

Quote:

Hmm..ok, but what can go wrong on reading log from phone ? Is there than maybe some safer reading ???

Bro.

There is safer way,

You have to Synchronize File for minor Update,

Bugs fixed for reading Asha Series & some other Phones,

But now don't try to flash it with software & contact Nokia Service or else will not resolve your problem.

BR,
ZUBER

hoze!!! · 09-23-2013, 11:32

no warranty for phone... Can I fix it with rpl ?

.::ZUBER::. · 09-23-2013, 11:42

Quote:

Originally Posted by hoze!!!

no warranty for phone... Can I fix it with rpl ?

If no Warranty,

Then Synchronize File & Buscheck,

If Logs OK, then take Backup of Simlock & Flash it will solve it,

If Logs not OK & Simlock corrupted, then have to Fix it with RPL.

BR,
ZUBER

hoze!!! · 09-23-2013, 12:48

I synchronize File & buscheck and after flash it, but simlock corrupted. SL Logger destroyed simlock zone

sahil2000ind · 09-23-2013, 15:47

SL LOGGER WILL NOT DESTROY SIMLOCK

JUST FLASH IT AGAIN WITH CORRECT RM AND PRODUCT CODE AND URE PHONE WILL BE OK

ALSO PLS POST FULL BUSCHECK AND FLASHING LOGS FOR COMPLETE ASSISTANCE

WBR
sahil2000ind

hoze!!! · 09-23-2013, 18:34

...allready try that. Flash complete, but simlock destroyed and WD timer enabled...

sahil2000ind · 09-24-2013, 08:54

POST LOGS

WBR
sahil2000ind

hoze!!! · 09-24-2013, 16:15

Quote:

Originally Posted by sahil2000ind

POST LOGS

WBR
sahil2000ind

Total time for flashing process(boot+erase+write) was 36.781 s
Waiting for USB device removal ...OK
Waiting for USB device arrival ...OK
Waiting for device boot up ...
Device connected: nmwcdc\Nokia Asha 302 USB Phonet, PORT_ID: 35633505xxxxxx
Verifying communication to device OK.

Phone type: RM-813 (Nokia 302)
SW version: V 14.92 09-11-12 RM-813 (c) Nokia
Imei plain: 35633505xxxxx-x
Battery voltage: 3855 mV, current: 159 mA
Language Pack:
- not available.

SLPA ver[1]: PA_SL (15 digit NCK)
Camera config: 0C219803XXXXXX, ver:

SIMLOCK invalid!
SUPERDONGLE_KEY invalid!
- WD timer enabled, phone will reboot itself after 3 min.
SIMLOCK_TEST failed!
SECURITY_TEST passed

SIMLOCK_DATA corrupted!
SIMLOCK_DATA corrupted!

hoze!!! · 09-24-2013, 16:19

bus check

MXKEY [MxKey Team HTI PLUS Flasher Interface 7], SN: xxxxx
Using device: USB Phonet and HTI, FW ver: 00.50, SN: xxxxx
Connection status: EHCI:HUB::USB 2.00 (High-speed)
Driver: nmwcdnsuc, ver: 7.1.32.115
Module ver: 1.0.0.21724(14-05-2013), Library ver: 1.0.0.14397(09-05-2013)
Make sure USB cable, Battery and charger are removed from device.
Insert USB cable, Battery back to device(make sure to have fully charged battery).
Insert Charger or Press phone's power button(if flashing doesnt start automatically)
Waiting for USB ROM device ...
CMT SYSTEM ASIC ID: 000000030000022600010007400C192103032108 [RAPUYAMA ver: 3.x]
CMT EM0 ID: 00001051
CMT EM1 ID: 00001060
CMT PUBLIC ID: AC5E0000FFFB7C4085CD80AF8A21C8F930B1F232
CMT ASIC MODE ID: 00
CMT ROOT KEY HASH: 3AB5DB70B45D23F1ADEEBB5734160706
CMT ROM ID: 2CAC45E23BC33C8B
Loading CMT secondary boot code
SecondaryBoot: RAPUv21_2nd.fg [BB5] version: 12.14.0 revision: 3.0 size: 0x3B40
Supported Ids: 0003192103002107, 000C192103002107, 0003192103012107, 000C192103012107, 000C192103022107, 0003192103022107, 400C192103022107, 4003192103022107, 000C192103032108, 0003192103032108, 400C192103032108, 4003192103032108, 0003192103042108, 400C192103042108, 0003192103042108, 4003192103042108
eBB5ProtocolType: NEW
Secondary boot loaded.
Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
Storage2: 0020 0040 - 0000 0131 [ST NAND KAT00F00RA] type: FLASH,NOR, asic:CMT
Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT
Storage4: 0020 0040 - 0000 0131 [ST NAND KAT00F00RA] type: FLASH,MuxOneNAND, asic:CMT
Suggested algorithm: XSR 1.6
Loading CMT update server data
Algorithm: RAPUv21_XSR17_alg.fg [XSR 1.6] version: 12.14.0 revision: 3.0 size: 0xD45E0
Supported Ids: 0003192103002107, 000C192103002107, 0003192103012107, 000C192103012107, 000C192103022107, 0003192103022107, 400C192103022107, 4003192103022107, 000C192103032108, 0003192103032108, 400C192103032108, 4003192103032108, 0003192103042108, 400C192103042108, 0003192103042108, 4003192103042108
Update server code loaded.
Waiting for USB device removal ...
Device connected: nmwcdnsuc\Nokia USB Flashing Generic, PORT_ID: 2118965
FUR: Adding Asic CMT as client OK.
CMT PAPUBKEYS HASH: 05BDE0ECC36CDEAA016A0565CB6BAE0B1585232E
Selected firmware certificate matched.
Original Imei: 35633505xxxxxx
Original Product code: 059P462
Bluetooth ID: F4F5A5EF949D
SIMLOCK PA identifier:
[0] PA_SIMLOC30

Reading CMT NPC (0x190 bytes).
Reading CMT VARIANT (0x0 bytes).
Reading CMT CCC (0x1E8 bytes).
Reading CMT HWC (0xD4 bytes).
Reading CMT R&D (0x0 bytes).
Reading CMT MDM_KEYS (0x0 bytes).
Reading CMT PARTNERC (0x0 bytes).

Waiting for USB device removal ...
Waiting for device boot up ...
Device connected: nmwcdc\Nokia Asha 302 USB Phonet, PORT_ID: 356335058xxxxxxx
Verifying communication to device OK.

Phone type: RM-813 (Nokia 302)
SW version: V 14.92 09-11-12 RM-813 (c) Nokia
Imei plain: 35633505xxxxxx-x
Battery voltage: 3853 mV, current: 159 mA
Language Pack:
- not available.

SLPA ver[1]: PA_SL (15 digit NCK)
Camera config: 0C219803XXXXXX, ver:

RPL saved to "D:\mobileEx\3.5\data\backup\BB5_RM-813_35633505xxxxxxx_24_09_13_171743_SIM.RPL"
SIMLOCK invalid!
SUPERDONGLE_KEY invalid!
- WD timer enabled, phone will reboot itself after 3 min.
SIMLOCK_TEST failed!
SECURITY_TEST passed

SIMLOCK_DATA corrupted!
SIMLOCK_DATA corrupted!

.::ZUBER::. · 09-26-2013, 07:56

Quote:

Originally Posted by hoze!!!

no warranty for phone... Can I fix it with rpl ?

Bro.

Only option is Factory RPL to fix it, which you already asked to.

BR,
ZUBER

markgoodboy · 12-04-2013, 16:21

hello sir
.
what if my nokia asha 302 is dead boot but still function of all programs, but i restore all settings then it happen again! do you think i need to flash it ? what box i need ! .
.
.
newbie in this site can you please help me !!
thanks

09-23-2013, 08:48	#1 (permalink)
hoze!!! Freak Poster Join Date: Apr 2004 Posts: 104 Member: 63177 Status: Offline Thanks Meter: 15	Dead Asha 302 after log read After trying to read SL3 log with logger asha 302 is dead. After trying to flash > Update server code loaded. ERROR: Loader not responding ! Phone is new!!! Some help maybe ?

12-04-2013, 16:21	#15 (permalink)
markgoodboy Junior Member Join Date: Dec 2013 Posts: 1 Member: 2077006 Status: Offline Thanks Meter: 0	nokia asha 302 hello sir . what if my nokia asha 302 is dead boot but still function of all programs, but i restore all settings then it happen again! do you think i need to flash it ? what box i need ! . . . newbie in this site can you please help me !! thanks

09-23-2013, 10:40	#2 (permalink)
.::ZUBER::. No Life Poster Join Date: Apr 2006 Location: MXBOX THUNDER Helpdesk Age: 50 Posts: 4,273 Member: 262425 Status: Offline Sonork: 100.1617691 Thanks Meter: 1,264	Bro. May be something went wrong while trying to read Logs, Contact Nokia Service Center if in Warranty. BR, ZUBER

09-23-2013, 10:58	#3 (permalink)
hoze!!! Freak Poster Join Date: Apr 2004 Posts: 104 Member: 63177 Status: Offline Thanks Meter: 15	Hmm..ok, but what can go wrong on reading log from phone ? Is there than maybe some safer reading ???

09-23-2013, 11:27	#4 (permalink)
sahil2000ind No Life Poster Join Date: Apr 2006 Location: INDIA Age: 38 Posts: 5,596 Member: 269044 Status: Offline Sonork: 100.1590584 Thanks Meter: 3,949	@zuber HOW CAN SOME THING CAN GO WRONG IN READING LOGS? CAN U EXPLAIN MORE I HAVE SEEN MANY USER HAVING PROBLEM WITH ASHA PHONES EVEN I TOO HAVE FACED PROBLEM IN FLASHING AND UNLOCKING ASHA PHONE THATS THE BUG IN MX-KEY SOFTWARE. @hoze!!! PLS TRY TO FLASH URE PHONE WITH SAME PRODUCT CODE AGAIN WITH MX-KEY OR SOME OTHER NOKIA FLASHER IF U HAVE ALSO PLS POST RESULTS I HAVE SEENS SOME MEMBERS THAT FACED PROBLEM WITH ASHA PHONE IN MX-KEY SOLVED THEIR PROBLEM WITH OTHER NOKIA FLASHERS ALSO PLS MAKE SURE U HAVE FULLY CHARGED BATTERY WBR sahil2000ind

09-23-2013, 11:32	#6 (permalink)
hoze!!! Freak Poster Join Date: Apr 2004 Posts: 104 Member: 63177 Status: Offline Thanks Meter: 15	no warranty for phone... Can I fix it with rpl ?

09-23-2013, 12:48	#8 (permalink)
hoze!!! Freak Poster Join Date: Apr 2004 Posts: 104 Member: 63177 Status: Offline Thanks Meter: 15	I synchronize File & buscheck and after flash it, but simlock corrupted. SL Logger destroyed simlock zone

09-23-2013, 15:47	#9 (permalink)
sahil2000ind No Life Poster Join Date: Apr 2006 Location: INDIA Age: 38 Posts: 5,596 Member: 269044 Status: Offline Sonork: 100.1590584 Thanks Meter: 3,949	SL LOGGER WILL NOT DESTROY SIMLOCK JUST FLASH IT AGAIN WITH CORRECT RM AND PRODUCT CODE AND URE PHONE WILL BE OK ALSO PLS POST FULL BUSCHECK AND FLASHING LOGS FOR COMPLETE ASSISTANCE WBR sahil2000ind

09-23-2013, 18:34	#10 (permalink)
hoze!!! Freak Poster Join Date: Apr 2004 Posts: 104 Member: 63177 Status: Offline Thanks Meter: 15	...allready try that. Flash complete, but simlock destroyed and WD timer enabled...

09-24-2013, 08:54	#11 (permalink)
sahil2000ind No Life Poster Join Date: Apr 2006 Location: INDIA Age: 38 Posts: 5,596 Member: 269044 Status: Offline Sonork: 100.1590584 Thanks Meter: 3,949	POST LOGS WBR sahil2000ind

09-24-2013, 16:19	#13 (permalink)
hoze!!! Freak Poster Join Date: Apr 2004 Posts: 104 Member: 63177 Status: Offline Thanks Meter: 15	bus check MXKEY [MxKey Team HTI PLUS Flasher Interface 7], SN: xxxxx Using device: USB Phonet and HTI, FW ver: 00.50, SN: xxxxx Connection status: EHCI:HUB::USB 2.00 (High-speed) Driver: nmwcdnsuc, ver: 7.1.32.115 Module ver: 1.0.0.21724(14-05-2013), Library ver: 1.0.0.14397(09-05-2013) Make sure USB cable, Battery and charger are removed from device. Insert USB cable, Battery back to device(make sure to have fully charged battery). Insert Charger or Press phone's power button(if flashing doesnt start automatically) Waiting for USB ROM device ... CMT SYSTEM ASIC ID: 000000030000022600010007400C192103032108 [RAPUYAMA ver: 3.x] CMT EM0 ID: 00001051 CMT EM1 ID: 00001060 CMT PUBLIC ID: AC5E0000FFFB7C4085CD80AF8A21C8F930B1F232 CMT ASIC MODE ID: 00 CMT ROOT KEY HASH: 3AB5DB70B45D23F1ADEEBB5734160706 CMT ROM ID: 2CAC45E23BC33C8B Loading CMT secondary boot code SecondaryBoot: RAPUv21_2nd.fg [BB5] version: 12.14.0 revision: 3.0 size: 0x3B40 Supported Ids: 0003192103002107, 000C192103002107, 0003192103012107, 000C192103012107, 000C192103022107, 0003192103022107, 400C192103022107, 4003192103022107, 000C192103032108, 0003192103032108, 400C192103032108, 4003192103032108, 0003192103042108, 400C192103042108, 0003192103042108, 4003192103042108 eBB5ProtocolType: NEW Secondary boot loaded. Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT Storage2: 0020 0040 - 0000 0131 [ST NAND KAT00F00RA] type: FLASH,NOR, asic:CMT Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage4: 0020 0040 - 0000 0131 [ST NAND KAT00F00RA] type: FLASH,MuxOneNAND, asic:CMT Suggested algorithm: XSR 1.6 Loading CMT update server data Algorithm: RAPUv21_XSR17_alg.fg [XSR 1.6] version: 12.14.0 revision: 3.0 size: 0xD45E0 Supported Ids: 0003192103002107, 000C192103002107, 0003192103012107, 000C192103012107, 000C192103022107, 0003192103022107, 400C192103022107, 4003192103022107, 000C192103032108, 0003192103032108, 400C192103032108, 4003192103032108, 0003192103042108, 400C192103042108, 0003192103042108, 4003192103042108 Update server code loaded. Waiting for USB device removal ... Device connected: nmwcdnsuc\Nokia USB Flashing Generic, PORT_ID: 2118965 FUR: Adding Asic CMT as client OK. CMT PAPUBKEYS HASH: 05BDE0ECC36CDEAA016A0565CB6BAE0B1585232E Selected firmware certificate matched. Original Imei: 35633505xxxxxx Original Product code: 059P462 Bluetooth ID: F4F5A5EF949D SIMLOCK PA identifier: [0] PA_SIMLOC30 Reading CMT NPC (0x190 bytes). Reading CMT VARIANT (0x0 bytes). Reading CMT CCC (0x1E8 bytes). Reading CMT HWC (0xD4 bytes). Reading CMT R&D (0x0 bytes). Reading CMT MDM_KEYS (0x0 bytes). Reading CMT PARTNERC (0x0 bytes). Waiting for USB device removal ... Waiting for device boot up ... Device connected: nmwcdc\Nokia Asha 302 USB Phonet, PORT_ID: 356335058xxxxxxx Verifying communication to device OK. Phone type: RM-813 (Nokia 302) SW version: V 14.92 09-11-12 RM-813 (c) Nokia Imei plain: 35633505xxxxxx-x Battery voltage: 3853 mV, current: 159 mA Language Pack: - not available. SLPA ver[1]: PA_SL (15 digit NCK) Camera config: 0C219803XXXXXX, ver: RPL saved to "D:\mobileEx\3.5\data\backup\BB5_RM-813_35633505xxxxxxx_24_09_13_171743_SIM.RPL" SIMLOCK invalid! SUPERDONGLE_KEY invalid! - WD timer enabled, phone will reboot itself after 3 min. SIMLOCK_TEST failed! SECURITY_TEST passed SIMLOCK_DATA corrupted! SIMLOCK_DATA corrupted!