GSM Shop GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > Product Support Sections > No More Supported Solutions (Dead Products) > No More Supported H/W Products > MXKEY (by Alim Hape) > MXKEY Nokia Flasher and Unlocker (by Alim Hape)


Reply
 
LinkBack Thread Tools Display Modes
Old 11-17-2013, 11:07   #1 (permalink)
No Life Poster
 
maxpro12's Avatar
 
Join Date: Aug 2010
Location: SearchinG ...
Age: 39
Posts: 1,633
Member: 1369772
Status: Offline
Thanks Meter: 297
Nokia 2690 RM-635 dead after flash


Nokia 2690 every thing is working, Just i want to upgrade to software version

and flash with latest version now phone is dead.

here is LOG.

MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 3], SN: C0xxxxxx
Using device: HTI, FW ver: 00.50, SN: 000xxxxx
Connection status: UHCI:HUB:USB 2.00 (Full-speed)
Driver: WinUSB, ver: 3.5.1.0
Module ver: 1.0.0.21724(14-05-2013), Library ver: 1.0.0.14397(09-05-2013)
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.0]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 1C500106CDED0256641CB17AF229DF1C9AE86286
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 9.11.1 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
eBB5ProtocolType: OLD
Storage0: 0089 8982 - 0000 8A31 [Intel NU48F512,512 Mbits] type: FLASH,NOR, asic:CMT
Storage content: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 9.50.0 revision: 0.0 size: 0x23010
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
CMT PAPUBKEYS is blank/erased.
TransmissionMode: DDR&TX2
Processing MCU file: rm635__10.65.mcusw
[BB5,BB5 ALGORITHM] size: 17.99 MB
Supported Ids: 010C192101013000, 0103192101003000, 030C192101033000
Storing certificate [NPC, VARIANT, R&D, CCC, HWC] ...OK
Erase size: 21 MB
CMT FLASH,NOR area [00000000-000006BF]
CMT FLASH,NOR area [000006C0-0001FFFF]
CMT FLASH,NOR area [00040000-000BFFFF]
CMT FLASH,NOR area [000C0000-0013FFFF]
CMT FLASH,NOR area [00140000-0137FFFF]
CMT FLASH,NOR area [01380000-0151FFFF]
erased in 0.203 s
Prog.status for Asic CMT ...
NOR: OK
Flash programming ...
Error chk C7012D0103CD
RX2 not responding, please check BSI/cable/pinout !
Error while programming [00] at 0x00000400, Result: 0000
Task failed at (0800001C)!!!
Last RX buffer: C7 01 2D 01 03 CD 00
  Reply With Quote
Old 11-17-2013, 15:27   #2 (permalink)
No Life Poster
 
.::ZUBER::.'s Avatar
 
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.

Clean FBus Cable or change it,

Clean Flashing Terminals & Battery Connector of Phone & try again will solve it.

You can also try USB Flashing.


BR,
ZUBER
  Reply With Quote
Old 11-18-2013, 04:42   #3 (permalink)
No Life Poster
 
maxpro12's Avatar
 
Join Date: Aug 2010
Location: SearchinG ...
Age: 39
Posts: 1,633
Member: 1369772
Status: Offline
Thanks Meter: 297
Quote:
Originally Posted by .::ZUBER::. View Post
Bro.

Clean FBus Cable or change it,

Clean Flashing Terminals & Battery Connector of Phone & try again will solve it.

You can also try USB Flashing.


BR,
ZUBER
Cable 100% ok because i test the cable with other phone.

I clean the Flashing terminal and B/C

Here is USB flashing procedure log

MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 3], SN: Cxxxxx
Using device: USB ROM and HTI, FW ver: 00.50, SN: 00xxxxxxxx
Connection status: UHCI:HUB::USB 2.00 (Full-speed)
Driver: NMWCD, ver: 7.1.32.84
Module ver: 1.0.0.21724(14-05-2013), Library ver: 1.0.0.14397(09-05-2013)
Processing MCU file: rm635__10.65.mcusw
[BB5,BB5 ALGORITHM] size: 17.99 MB
Supported Ids: 010C192101013000, 0103192101003000, 030C192101033000
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: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.0]
CMT EM0 ID: 00000296
CMT EM1 ID: 00000B22
CMT PUBLIC ID: 1C500106CDED0256641CB17AF229DF1C9AE86286
CMT ASIC MODE ID: 00
CMT ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT ROM ID: 273F6D55DFAAF68F
Flashing CMT Update Server Data, ULO: 0x3900 bytes
Update Server code succesfully sent to phone.
Flashing CMT Update Server Data, UPDAPP: 0x49480 bytes
Update Server code succesfully sent to phone.
Flashing CMT Update Server Data, PASUBTOC: 0x57AC0 bytes
Update Server code succesfully sent to phone.
Waiting for USB device removal ...
Device connected: nmwcdnsuc\Nokia USB Flashing Generic, PORT_ID: F0F12C
Verifying communication to device...
ERROR: Could not verify communication !
Failed to set phone to flashmode, possible reason: Update Agent not running or PASUBTOC corrupted !
Please recover phone using FBUS.


Maxpro.
  Reply With Quote
Old 11-18-2013, 04:58   #4 (permalink)
No Life Poster
 
Join Date: Oct 2007
Posts: 1,216
Member: 608516
Status: Offline
Sonork: 100.1607007
Thanks Meter: 123
Quote:
Originally Posted by maxpro12 View Post
Cable 100% ok because i test the cable with other phone.

I clean the Flashing terminal and B/C

Here is USB flashing procedure log

MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 3], SN: Cxxxxx
Using device: USB ROM and HTI, FW ver: 00.50, SN: 00xxxxxxxx
Connection status: UHCI:HUB::USB 2.00 (Full-speed)
Driver: NMWCD, ver: 7.1.32.84
Module ver: 1.0.0.21724(14-05-2013), Library ver: 1.0.0.14397(09-05-2013)
Processing MCU file: rm635__10.65.mcusw
[BB5,BB5 ALGORITHM] size: 17.99 MB
Supported Ids: 010C192101013000, 0103192101003000, 030C192101033000
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: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.0]
CMT EM0 ID: 00000296
CMT EM1 ID: 00000B22
CMT PUBLIC ID: 1C500106CDED0256641CB17AF229DF1C9AE86286
CMT ASIC MODE ID: 00
CMT ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
CMT ROM ID: 273F6D55DFAAF68F
Flashing CMT Update Server Data, ULO: 0x3900 bytes
Update Server code succesfully sent to phone.
Flashing CMT Update Server Data, UPDAPP: 0x49480 bytes
Update Server code succesfully sent to phone.
Flashing CMT Update Server Data, PASUBTOC: 0x57AC0 bytes
Update Server code succesfully sent to phone.
Waiting for USB device removal ...
Device connected: nmwcdnsuc\Nokia USB Flashing Generic, PORT_ID: F0F12C
Verifying communication to device...
ERROR: Could not verify communication !
Failed to set phone to flashmode, possible reason: Update Agent not running or PASUBTOC corrupted !
Please recover phone using FBUS.


Maxpro.
2690 not supported usb flashing use atf or mx key low baud rate with 10.65 version
  Reply With Quote
Old 11-19-2013, 15:53   #5 (permalink)
No Life Poster
 
Fragga's Avatar
 
Join Date: Feb 2011
Location: Android Modding
Posts: 932
Member: 1507693
Status: Offline
Thanks Meter: 131
Quote:
Originally Posted by cheeni View Post
2690 not supported usb flashing use atf or mx key low baud rate with 10.65 version

bro you are 1000% WRONG, usb flashing for 2690 rm-635 is very well supported by MXBOX, MXKEY, but if flashing failed first time with usb or rj-45 cable, then you cannot continue flashing with usb, you recover using rj-45 cable.this is RAP3Gv3_algo!!! USB FLASHING SUPPORTED. but if flashing failed before finishing PROGRAMING CMT you have to use RJ-45 cable to recover it, check where his software stopped


(
CMT PAPUBKEYS is blank/erased.
TransmissionMode: DDR&TX2
Processing MCU file: rm635__10.65.mcusw
[BB5,BB5 ALGORITHM] size: 17.99 MB
Supported Ids: 010C192101013000, 0103192101003000, 030C192101033000
Storing certificate [NPC, VARIANT, R&D, CCC, HWC] ...OK
Erase size: 21 MB
CMT FLASH,NOR area [00000000-000006BF]
CMT FLASH,NOR area [000006C0-0001FFFF]
CMT FLASH,NOR area [00040000-000BFFFF]
CMT FLASH,NOR area [000C0000-0013FFFF]
CMT FLASH,NOR area [00140000-0137FFFF]
CMT FLASH,NOR area [01380000-0151FFFF]
erased in 0.203 s
Prog.status for Asic CMT ...
NOR: OK
Flash programming ...
Error chk C7012D0103CD
RX2 not responding, please check BSI/cable/pinout !
Error while programming [00] at 0x00000400, Result: 0000
Task failed at (0800001C)!!!
Last RX buffer: C7 01 2D 01 03 CD 00


AND THAT ERROR IN RED SHOWS RJ-45 CABLE IS NOT WELL CONNECTED TO PHONE, OR CABLE NOT GOOD
  Reply With Quote
The Following User Says Thank You to Fragga For This Useful Post:
Old 11-20-2013, 10:36   #6 (permalink)
No Life Poster
 
maxpro12's Avatar
 
Join Date: Aug 2010
Location: SearchinG ...
Age: 39
Posts: 1,633
Member: 1369772
Status: Offline
Thanks Meter: 297
Quote:
Originally Posted by Fragga View Post
bro you are 1000% WRONG, usb flashing for 2690 rm-635 is very well supported by MXBOX, MXKEY, but if flashing failed first time with usb or rj-45 cable, then you cannot continue flashing with usb, you recover using rj-45 cable.this is RAP3Gv3_algo!!! USB FLASHING SUPPORTED. but if flashing failed before finishing PROGRAMING CMT you have to use RJ-45 cable to recover it, check where his software stopped


(
CMT PAPUBKEYS is blank/erased.
TransmissionMode: DDR&TX2
Processing MCU file: rm635__10.65.mcusw
[BB5,BB5 ALGORITHM] size: 17.99 MB
Supported Ids: 010C192101013000, 0103192101003000, 030C192101033000
Storing certificate [NPC, VARIANT, R&D, CCC, HWC] ...OK
Erase size: 21 MB
CMT FLASH,NOR area [00000000-000006BF]
CMT FLASH,NOR area [000006C0-0001FFFF]
CMT FLASH,NOR area [00040000-000BFFFF]
CMT FLASH,NOR area [000C0000-0013FFFF]
CMT FLASH,NOR area [00140000-0137FFFF]
CMT FLASH,NOR area [01380000-0151FFFF]
erased in 0.203 s
Prog.status for Asic CMT ...
NOR: OK
Flash programming ...
Error chk C7012D0103CD
RX2 not responding, please check BSI/cable/pinout !
Error while programming [00] at 0x00000400, Result: 0000
Task failed at (0800001C)!!!
Last RX buffer: C7 01 2D 01 03 CD 00


AND THAT ERROR IN RED SHOWS RJ-45 CABLE IS NOT WELL CONNECTED TO PHONE, OR CABLE NOT GOOD
Yes, You are right. I solved my problem
  Reply With Quote
Reply

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 



All times are GMT +1. The time now is 05:39.



Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.21073 seconds with 9 queries

SEO by vBSEO