View Single Post
Old 11-10-2013, 03:06   #11 (permalink)
richiricherd
No Life Poster
 
richiricherd's Avatar
 
Join Date: Sep 2007
Location: Venezuela
Posts: 846
Member: 594580
Status: Offline
Thanks Meter: 157
Quote:
Originally Posted by Octopus box View Post
Hello.
Please post here full software log and describe all of your actions step by step how You connect the device.
Ok Sir, Ive check very well solder points and all are ok but I have same problem, cant conect the phone.. Here is log:

Selected device model: Auto
Connecting. Please wait...
Medusa JTAG Firmware version 1.1.0.
Medusa JTAG Hardware S256 revision C.
Detected TAP ID: 106010E1, IR Length = 4.
JTAG speed : 100 KHz.
VREF level : 1.74 V
CPU : Qualcomm MSM7225A
Core ID : 106010E1
ERROR[004]: Medusa Device Server did not replied to HELLO command.
Selected device model: Auto
Connecting. Please wait...
Medusa JTAG Firmware version 1.1.0.
Medusa JTAG Hardware S256 revision C.
ERROR[045]: Scan chain is too long or damaged. Scanned TAP ID's list:
0x000010E1
0x00000000
0x00000000
0x00000000
0x0000001F
0x00000000
0x0000000F
0x0000000F
MI: Medusa JTAG init failed.

Ive tried HTC Decire C model and Auto model and same result, Ive tried diferent Jtag speed and only with 100 Khz I get this:

Selected device model: Auto
Connecting. Please wait...
Medusa JTAG Firmware version 1.1.0.
Medusa JTAG Hardware S256 revision C.
Detected TAP ID: 106010E1, IR Length = 4.
JTAG speed : 100 KHz.
VREF level : 1.74 V
CPU : Qualcomm MSM7225A
Core ID : 106010E1
ERROR[004]: Medusa Device Server did not replied to HELLO command.

But if I select directly CPU type Qualcom MSM72xx/MSM76xx and 100 Khz speed I get this:

Selected device model: Qualcomm MSM72xx/MSM76xx
Connecting. Please wait...
Medusa JTAG Firmware version 1.1.0.
Medusa JTAG Hardware S256 revision C.
Detected TAP ID: 106010E1, IR Length = 4.
JTAG speed : 100 KHz.
VREF level : 1.74 V
CPU : Qualcomm MSM7225A
Core ID : 106010E1
Storage Device: Hynix eMMC XINYH
Device ID : 00904A01
Block size : 512 bytes
Blocks : 4702208
Storage size : 2296 Mb
Connect successful.

But there are not options for repair IMEI Sir.. What can I do next??
  Reply With Quote
The Following User Says Thank You to richiricherd For This Useful Post:
 
Page generated in 0.09246 seconds with 7 queries