i'm looking for pinout for UFC cable for nokia ASHA 302 RM-813 - GSM-Forum

PSG · 11-19-2012, 11:59

1. i'm looking for pinout for UFC FBUS cable for nokia ASHA 302 RM-813
2. i can;t read SHA file via USB so please advice me: can i read SHA from such Asha 302 via FBUS ?

PSG · 11-19-2012, 12:45

this is log from SHA read via USB with error, i spoke with my friend who has got cyclone and he told he did log from Asha 302 via usb so why mxkey can't do it ?

Code:

MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 0], SN: XXXXXXX
Using device: USB Phonet  and HTI, FW ver: 00.50, SN: 00XXXXX
Connection status: EHCI:HUB:USB 2.00 (High-speed)
Driver: nmwcdc, ver: 7.1.32.75 
Module ver: 1.0.0.21200(18-07-2012), Library ver: 1.0.0.14205(18-07-2012)
 
Phone type: RM-813 (Nokia 302)
SW version: V 14.53 20-03-12 RM-813 (c) Nokia             
 
Waiting for USB device removal ... 
CMT SYSTEM ASIC ID: 000000030000022600010007400C192103032108 [RAPUYAMA ver: 3.x]
CMT EM0 ID: 00001051
CMT EM1 ID: 00001060
CMT PUBLIC ID: E6360000FFFB3C405AEF9DA6C37086BF0FB6A5A6
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: 11.34.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
Interface not supported for current operation or not supported phone !
Nokia USB Phonet detached.
Nokia USB Phonet disconnected.

.::ZUBER::. · 11-19-2012, 15:05

Quote:

Originally Posted by PSG

this is log from SHA read via USB with error, i spoke with my friend who has got cyclone and he told he did log from Asha 302 via usb so why mxkey can't do it ?

Code:

MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 0], SN: XXXXXXX
Using device: USB Phonet  and HTI, FW ver: 00.50, SN: 00XXXXX
Connection status: EHCI:HUB:USB 2.00 (High-speed)
Driver: nmwcdc, ver: 7.1.32.75 
Module ver: 1.0.0.21200(18-07-2012), Library ver: 1.0.0.14205(18-07-2012)
 
Phone type: RM-813 (Nokia 302)
SW version: V 14.53 20-03-12 RM-813 (c) Nokia             
 
Waiting for USB device removal ... 
CMT SYSTEM ASIC ID: 000000030000022600010007400C192103032108 [RAPUYAMA ver: 3.x]
CMT EM0 ID: 00001051
CMT EM1 ID: 00001060
CMT PUBLIC ID: E6360000FFFB3C405AEF9DA6C37086BF0FB6A5A6
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: 11.34.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
Interface not supported for current operation or not supported phone !
Nokia USB Phonet detached.
Nokia USB Phonet disconnected.

Hi,

1st Download & Install Mxkey latest Ver3.5 Rev2.4

Read Hash & post Result,

PS Never ask with Old Software, may not give good Result.

BR,
ZUBER

PSG · 11-19-2012, 15:32

i made update mxkey to rev 2.4
this is log from scan:

Code:

Phone type: RM-813 (Nokia 302)
SW version: V 14.53 20-03-12 RM-813 (c) Nokia             
Imei plain: 35414605XXXXX-4
Product code: 059N121
Battery voltage: 3875 mV, current: 65265 mA
Language Pack:
- not available.

SLPA ver[4]: PA_SL3/PA_SIMLOC30 (15 digit NCK)
warning: avoid SW Downgrade & manual erase to this phone !
Camera config: 01035602004006, ver: 
 
SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed
 
 
Imei net: 3541460XXXXX4
Version: SIMLOCK SERVER
Provider: Idea (Polska Telefonia Komórkowa Centertel Sp. Z.o.o) , Country: Poland
Counter: 0/3, 0/10
 
CONFIG_DATA: 2600300000000000
PROFILE_BITS: 8000000000000000
 
BLOCK1: 1=CLOSED(MCCMNC), DATA=26003F  [Poland-Idea (Polska Telefonia Komórkowa Centertel Sp. Z.o.o) ]

this is SHA read via usb with error:

Code:

MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 0], SN: C08XXX
Using device: USB Phonet  and HTI, FW ver: 00.50, SN: 0XXXXX
Connection status: EHCI:HUB:USB 2.00 (High-speed)
Driver: nmwcdc, ver: 7.1.32.75 
Module ver: 1.0.0.21200(18-07-2012), Library ver: 1.0.0.14214(25-10-2012)
 
Phone type: RM-813 (Nokia 302)
SW version: V 14.53 20-03-12 RM-813 (c) Nokia             
 
Waiting for USB device removal ... 
CMT SYSTEM ASIC ID: 000000030000022600010007400C192103032108 [RAPUYAMA ver: 3.x]
CMT EM0 ID: 00001051
CMT EM1 ID: 00001060
CMT PUBLIC ID: E6360000FFFB3C405AEF9DA6C37086BF0FB6A5A6
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: 11.34.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
ERROR: Secondary boot not responding !
Interface not supported for current operation or not supported phone !

PSG · 11-20-2012, 11:01

will mxkey read SHA via usb for ASHA 302 ?

PSG · 11-21-2012, 10:44

why there is no answer for such simple question about usb SHA read ?

denard · 11-21-2012, 11:53

Very simple to read with usb here is my log file

Quote:

phone type: Rm-813 (nokia 302)
sw version: V 14.23 22-12-11 rm-813 (c) nokia
battery voltage: 3949 mv, current: 0 ma
product code: 059n6s7
imei plain: 35862904024232-7

slpa ver[4]: Pa_sl3/pa_simloc30 (15 digit nck)

imei net: 358629040242327
version: Simlock server
provider: Bouygues telecom , country: France
counter: 0/3, 0/10

config_data: 2082000000000000
profile_bits: 8000000000000000

block1: 1=closed(mccmnc), data=20820f [france-bouygues telecom ]

mxkey [mxkey team hti plus flasher interface 4], sn: C085e944
using device: Usb phonet and hti, fw ver: 00.50, sn: 010030b4
connection status: Ehci:hub:usb 2.00 (high-speed)
driver: Nmwcdc, ver: 7.1.32.75
library ver: 1.0.0.14214(25-10-2012)

phone type: Rm-813
sw version: V 14.23 22-12-11 rm-813 (c) nokia

waiting for usb device removal ...
Cmt system asic id: 000000030000022600010007400c192103032108 [rapuyama ver: 3.x]
cmt em0 id: 00001051
cmt em1 id: 00001060
cmt public id: B2110000fffb3c40bc0471a2484ec79be9fa63ab
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: 11.34.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: 0000 0000 - 0000 0000 [unused/removed] type: Flash,nor, asic:cmt
storage3: 0000 0001 - 0000 0000 [unused/removed] type: Flash,nor, asic:cmt
storage4: 00ec 0040 - 0000 0241 [samsung 2gb ddp onenand,2 gbits] type: Flash,muxonenand, asic:cmt
suggested algorithm: Xsr 1.6
loading cmt update server data
algorithm: Rapuv21_xsr17_alg.fg [xsr 1.6] version: 11.34.0 revision: 3.0 size: 0xd40a0
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 ...ok
waiting for usb device arrival ...
Device connected: Nmwcdnsuc\nokia usb flashing generic, port_id: 31f2311c
fur: Adding asic cmt as client ok.
Public id: B2110000fffb3c40bc0471a2484ec79be9fa63ab
private id: C2d2d432d68c4724b973ddef6f07d48b7d424bbb
e-fuse: 3e3767ca
sec rom crc: 3bc33c8b

waiting for usb device removal ...ok
waiting for usb device arrival ...ok
waiting for device boot up ...
Device connected: Nmwcdc\nokia usb phonet, port_id: 36a1528a
verifying communication to device ok.

Verifying secure data ...ok
hash: 44d446ad178d1e80d2611c780a85cd9332b8617b
verifying rsa signature ...ok, rsa verify passed
hash file saved to "c:\mobileex\3.5\data\sl3\rm-813_358629040242327 "

.::ZUBER::. · 11-21-2012, 12:28

Quote:

Originally Posted by PSG

why there is no answer for such simple question about usb SHA read ?

When you think Question is simple then Answer must also simple,

Check Nokia Settings from Configuration,

Tick same as in Image & try to change Flash Loader.

IGNORE MXKEY VERSION, IT'S ONLY SAMPLE.

BR,
ZUBER

PSG · 11-21-2012, 12:47

user denard some how read Asha 302 using this 11.34.0 version.
i used same loaders (auto setup in mxkey settings) but i've got error :

look he read same asha 302 with same asic as mine:

Code:

Cmt system asic id: 000000030000022600010007400c192103032108 [rapuyama ver: 3.x]

Code:

400c192103032108

Code:

supported ids: 0003192103002107, 400c192103032108, 000c192103002107, 0003192103012107, 000c192103012107, 000c192103022107, 0003192103022107, 400c192103022107, 4003192103022107, 000c192103032108, 0003192103032108, 4003192103032108, 0003192103042108, 400c192103042108, 0003192103042108, 4003192103042108

Code:

loading cmt secondary boot code
secondaryboot: Rapuv21_2nd.fg [bb5] version: 11.34.0 revision: 3.0 size: 0x3b40

loading cmt update server data
algorithm: Rapuv21_xsr17_alg.fg [xsr 1.6] version: 11.34.0 revision: 3.0 size: 0xd40a0

You're suggest to use oldest loaders, i had to give back phone to customer (SHA read via 7evolution) so i can't check it but i think ther is bug in maxkey code.
thanks for help, but i'm quite sure mxkey can't read such asha now.

.::ZUBER::. · 11-21-2012, 16:18

Quote:

mxkey [mxkey team hti plus flasher interface 4], sn: C085e944
using device: Usb phonet and hti, fw ver: 00.50, sn: 010030b4
connection status: Ehci:hub:usb 2.00 (high-speed)
driver: Nmwcdc, ver: 7.1.32.75
library ver: 1.0.0.14214(25-10-2012)

What do you mean by can't read such asha now.

See his Mxkey Version,
It's Latest with same Phone & no such Bugs,
So topic Closed.

BR,
ZUBER

11-19-2012, 11:59	#1 (permalink)
PSG No Life Poster Join Date: May 2003 Location: POLAND Posts: 1,262 Member: 27761 Status: Offline Thanks Meter: 55	i'm looking for pinout for UFC cable for nokia ASHA 302 RM-813 1. i'm looking for pinout for UFC FBUS cable for nokia ASHA 302 RM-813 2. i can;t read SHA file via USB so please advice me: can i read SHA from such Asha 302 via FBUS ?

11-20-2012, 11:01	#5 (permalink)
PSG No Life Poster Join Date: May 2003 Location: POLAND Posts: 1,262 Member: 27761 Status: Offline Thanks Meter: 55	will mxkey read SHA via usb for ASHA 302 ?

11-21-2012, 10:44	#6 (permalink)
PSG No Life Poster Join Date: May 2003 Location: POLAND Posts: 1,262 Member: 27761 Status: Offline Thanks Meter: 55	why there is no answer for such simple question about usb SHA read ?