08-18-2012, 16:42
|
#1 (permalink)
|
| No Life Poster
Join Date: Apr 2003
Posts: 871
Member: 26440
Status: Offline
Thanks: 25
Thanked 3 Times in 3 Posts
| @@@ cannot unlock n95 log inside @@@ [ Solved ] Quote:
establishing connection with box in main mode...
Handling device: [cyclone team], [cyclone box], [platform: Classic]
initializing box...
Box firmware: Cyclone main application v02.04, (jun 10 2012 18:37:23, gcc v4.3.3, rtos v6.0.1), type: Signed production application, (c) karwossoft 2012
hardware platform: Cyclone classic flasher interface (c) 2008,2009 karwoslabs
box serial number:
Hw revision: A, suitable for: Production, case: First plastic case, mcu manufacture time: 2009, wk14
initializing security card...
Card serial number:
Card firmware revision: 0109
card is activated
box is activated
started box selftests procedure
usb voltage 4.98v passed
mcu voltage 3.28v passed
core voltage 1.76v passed
vbat voltage 1.37v passed
vbat voltage 4.90v passed
box vpp disabled
vpp voltage 0.02v passed
internal box vpp enabled
vpp voltage 4.92v passed
box vpp disabled
vpp voltage 0.04v passed
external box vpp enabled
vpp voltage 0.04v failed - ignored - probably power supply is not connected
box vpp disabled
all box selftests passed!
Super dct4 activation: True
xgold/blackberry service running, counter: 88
avaiable physical memory: 119.964mb
avaiable virtual memory: 1.893gb
avaiable pagefile: 1.449gb
initializing fbus...
All initialized - ready to work
bb5 unlock started...
Mcu version v 06wk41v23.4
mcu date 17-04-07
product rm-159 (nokia n95)
manufacturer (c) nokia
imei 3522550189
mastercode 2343633713
simlock server simlock server
simlock key 2343000000000000
simlock profile 0000000000000000
simlock key cnt 0
simlock fbus cnt 0
simlock [1,1] state: Closed type: Mcc-mnc data: 23430f
simlock [2,1] state: Closed type: Mcc-mnc data: 23430f
reading security block...
Security block ok and saved to "rm-159_352255018967***_18082012_161619.securityblock. pm"
warning: "0a400107655b0058e1d32049e40d803dd7a42ed5.c00011cc " not exists, will read it...
Reading cyc file from phone...
Booting cmt...
Ape_system_asic_id: 24200705
ape_asic_mode_id: 00
ape_public_id: 24092a7a0e82aebc21efefc2e3e6003e589ee523
ape_root_key_hash: Ba8710a7e1cd5a2909b9a875db27aa2400000000
cmt_system_asic_id: 000000010000022600010006400c192101011103
cmt_em_asic_id: 00000295
cmt_em_asic_id: 00000b22
cmt_public_id: 0a400107655b0058e1d32049e40d803dd7a42ed5
cmt_asic_mode_id: 00
cmt_root_key_hash: Caeebb65d3c48e6dc73b49dc5063a2ee
cmt_boot_rom_crc: F2c6ebad
cmt_secure_rom_crc: C86e6189
cmt ready!
New_rapidov11_2nd.fg, type: 2nd boot loader, rev: 512.11.16.0, 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
if software stuck here with box tx led lit, that means:
1. You have not attached yellow tx2 adapter (it is required for bb5 phones when using jaf/ufs cables!)
2. Your cable is not tx2 enabled!
3. Transmission error occured, try again
in either cases, you need to reconnect your box from usb.
Cbus request error -> cbus response wrong header
prepare phone failed with message -> failed to get cmt configuration
neither cyc file and exists or failed to read it from phone (failed to boot / prepare phone)
bb5 unlock failed -> failed to obtain phone unique data
|
cable is gpg.
Yellow add on adapter does not work |
|
| |