i9082 alwayes error - GSM-Forum

IBRAHIM6X · 09-12-2013, 18:30

log:
Using EasyRepair Mode...
Checking repair data...
EasyJtag Suite ver.: 1.0.64.0 started.
Operating system ver.: Windows 7 (build 7601, Service Pack 1).
For support and updates visit EasyJtag , just better ? - New powerful JTAG unbrick device.
Initialising: SAMSUNG GT-I9082 Config ver.:1.00
I/O Level set to : 2200 mV
Box S/N: 1313010F1161FBAB ,FW Ver.: 01.47
Connecting to Target...
JTAG device: BCM28155
CPU IDCODE : 0x4BA00477 Mfg.: 0x23b, Part: 0xba00, Ver.: 0x4
CPU Manufacturer: QUALCOMM , CPU Name: CORTEX A9
Halting CPU...
Target Not Examined

**blang** · 09-13-2013, 19:35

99% you have erased rom2. Only one way for repair this problem, rewrite rom2 via Emmc direct connection. I9082 Emmc direct pinout and rom2 uploaded to support.

Only after rewriting rom2 you can connect phone via JTAG connection and repair boot via rcp file.

lunno · 12-18-2013, 13:33

I got the same problem.
But I don't know if the problem is rom2

**blang** · 12-19-2013, 16:59

Quote:

Originally Posted by lunno

I got the same problem.
But I don't know if the problem is rom2

write ROM2 and you will know

NoName® · 12-19-2013, 23:02

Thats possible CPU are in undef state. Try to recover ROM2 in eMMC tool.

sultan_ · 11-30-2014, 11:40

can i erase emmc then write rom1 and rom2?

09-12-2013, 18:30	#1 (permalink)
IBRAHIM6X Major Poster Join Date: Feb 2005 Age: 44 Posts: 40 Member: 113453 Status: Offline Thanks Meter: 12	i9082 alwayes error log: Using EasyRepair Mode... Checking repair data... EasyJtag Suite ver.: 1.0.64.0 started. Operating system ver.: Windows 7 (build 7601, Service Pack 1). For support and updates visit EasyJtag , just better ? - New powerful JTAG unbrick device. Initialising: SAMSUNG GT-I9082 Config ver.:1.00 I/O Level set to : 2200 mV Box S/N: 1313010F1161FBAB ,FW Ver.: 01.47 Connecting to Target... JTAG device: BCM28155 CPU IDCODE : 0x4BA00477 Mfg.: 0x23b, Part: 0xba00, Ver.: 0x4 CPU Manufacturer: QUALCOMM , CPU Name: CORTEX A9 Halting CPU... Target Not Examined

09-13-2013, 19:35	#2 (permalink)
blang Product Manager Join Date: Oct 2000 Location: future Posts: 22,431 Member: 2368 Status: Offline Sonork: 100.111111 Thanks Meter: 186,557	99% you have erased rom2. Only one way for repair this problem, rewrite rom2 via Emmc direct connection. I9082 Emmc direct pinout and rom2 uploaded to support. Only after rewriting rom2 you can connect phone via JTAG connection and repair boot via rcp file.

12-18-2013, 13:33	#3 (permalink)
lunno Freak Poster Join Date: Dec 2012 Location: Brazil Posts: 216 Member: 1859706 Status: Offline Sonork: 100.1648492 Thanks Meter: 28	I got the same problem. But I don't know if the problem is rom2

12-19-2013, 23:02	#5 (permalink)
NoName® Product Supporter Join Date: Mar 2005 Location: China Posts: 3,338 Member: 129885 Status: Offline Sonork: 100:1603514 Thanks Meter: 6,202	Thats possible CPU are in undef state. Try to recover ROM2 in eMMC tool.

11-30-2014, 11:40	#6 (permalink)
sultan_ No Life Poster Join Date: May 2008 Posts: 2,434 Member: 770299 Status: Offline Sonork: 100.1603105 Thanks Meter: 1,029	can i erase emmc then write rom1 and rom2?