ANSWERED R-JTAG Chip smoking. Can't find correct DIP settings

Status
Not open for further replies.

Precarious

Junior Member
Jan 23, 2014
15
0
Console Type: (Zephyr/Falcon/Opus/Jasper)
NAND size: 16/256/512
Dashboard version: 2.0.16537
CB version: 5774
J-Runner log:
PHP:
Monday, March 10, 2014 10:29:42 PM

J-Runner v0.3 Beta (4) Started




Version: 01
Flash Config: 0x00000000
Can not Continue


Checking Files
Finished Checking Files
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 00
Wrong Version.
Falcon Manually Selected


===================================================
Monday, March 10, 2014 10:35:03 PM


J-Runner v0.3 Beta (4) Started




It's advised to run in administrator mode on Windows 8


Checking Files
Finished Checking Files


===================================================
Monday, March 10, 2014 10:35:13 PM


J-Runner v0.3 Beta (4) Started






Checking Files
Finished Checking Files
Version: 00
Wrong Version.
Falcon Manually Selected
Version: 00
Wrong Version.
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue


===================================================
Monday, March 10, 2014 10:37:34 PM


J-Runner v0.3 Beta (4) Started






Checking Files
Version: 01
Finished Checking Files
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Power Up
Version: 01
Flash Config: 0x00000000
Can not Continue
Update


Bootloader Attached
Bootloader Version: 1.0.4
Bootloader Removed.


Bootloader Attached
Bootloader Version: 1.0.4
Bootloader Removed.
Version: 01
Flash Config: 0x00000000
Can not Continue


===================================================
Monday, March 10, 2014 11:14:28 PM


J-Runner v0.3 Beta (4) Started




Version: 01


Checking Files
Flash Config: 0x00000000
Can not Continue
Finished Checking Files


Bootloader Attached
Bootloader Version: 1.0.4
Bootloader Removed.


Bootloader Attached
Bootloader Version: 1.0.4
Bootloader Removed.
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x01198010
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 5774
Falcon/Opus
Reading Nand to C:\Users\Quneibi\Downloads\output\nanddump1.bin
Reading Nand
Done!
in 3:21 min:sec


Reading Nand to C:\Users\Quneibi\Downloads\output\nanddump2.bin
Initializing nanddump1.bin..
Falcon/Opus
Jtag Selected
Nand Initialization Finished
Reading Nand
Done!
in 3:21 min:sec


Reading Nand to C:\Users\Quneibi\Downloads\output\nanddump3.bin
Comparing...
Nands are the same
Reading Nand
Done!
in 3:21 min:sec


Comparing...
Nands are the same
XeLL file created Successfully falcon.bin
Version: 01
Flash Config: 0x01198010
Writing Nand
falcon.bin
Done!
in 0:18 min:sec




===================================================
Tuesday, March 11, 2014 8:42:35 PM


J-Runner v0.3 Beta (4) Started




WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button




Checking Files
Finished Checking Files
Jtag Selected
R-Jtag Selected
Falcon Manually Selected


===================================================
Tuesday, March 11, 2014 8:43:38 PM


J-Runner v0.3 Beta (4) Started




WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button




Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Falcon/Opus
Jtag Selected
Nand Initialization Finished
Comparing...
Nands are the same
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 00
Wrong Version.


===================================================
Tuesday, March 11, 2014 9:02:55 PM


J-Runner v0.3 Beta (4) Started




WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button




Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Falcon/Opus
Jtag Selected
Nand Initialization Finished
Version: 00
Wrong Version.
R-Jtag Selected
Version: 00
Wrong Version.
Version: 00
Wrong Version.
Power Up
Version: 00
Wrong Version.


Bootloader Attached
Bootloader Version: 1.0.4
Bootloader Removed.


Bootloader Attached
Bootloader Version: 1.0.4
Bootloader Removed.


Bootloader Attached
Bootloader Version: 1.0.4
Bootloader Removed.


Bootloader Attached
Bootloader Version: 1.0.4
Bootloader Removed.


===================================================
Tuesday, March 11, 2014 9:10:54 PM


J-Runner v0.3 Beta (4) Started




WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button




Checking Files
Finished Checking Files


Bootloader Attached
Bootloader Version: 1.0.4
Bootloader Removed.


Bootloader Attached
Bootloader Version: 1.0.4


Erasing Flash ...
Writing Flash: ....................................................................................................
Done!
Verifying Flash: ....................................................................................................
 Write Verified!
Restarting Device ...
Finished!


Bootloader Removed.
Version: 01
Flash Config: 0x01198010
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 5770
Falcon/Opus
Reading Nand to C:\Users\Quneibi\Downloads\output\nanddump1.bin
Cancelled
Initializing nanddump1.bin..
Falcon/Opus
Jtag Selected
Nand Initialization Finished
Version: 01
Flash Config: 0x01198010
Writing Nand
nanddump1.bin
Done!
in 3:41 min:sec


Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x01198010
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 5774
Falcon/Opus
Reading Nand to C:\Users\Quneibi\Downloads\output\nanddump1.bin
Reading Nand
Done!
in 3:21 min:sec


Reading Nand to C:\Users\Quneibi\Downloads\output\nanddump2.bin
Initializing nanddump1.bin..
Falcon/Opus
Nand Initialization Finished
Cancelled
Comparing...
0x0068
0x0069
0x03DE
Version: 01
Flash Config: 0x01198010
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 5774
Falcon/Opus
Reading Nand to C:\Users\Quneibi\Downloads\output\nanddump1.bin
Cancelled
Version: 01
Flash Config: 0x01198010
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 5774
Falcon/Opus
Reading Nand to C:\Users\Quneibi\Downloads\output\nanddump1.bin
Reading Nand
Done!
in 3:21 min:sec


Reading Nand to C:\Users\Quneibi\Downloads\output\nanddump2.bin
Initializing nanddump1.bin..
Falcon/Opus
Nand Initialization Finished
Reading Nand
Done!
in 3:21 min:sec


Comparing...
Nands are the same
Comparing...
0x0068
0x0069
0x03DE
Initializing nanddump1.bin..
Falcon/Opus
Nand Initialization Finished
Comparing...
0x0068
0x0069
0x03DE
Initializing nanddump1.bin..
Falcon/Opus
Nand Initialization Finished
Comparing...
Nands are the same
R-Jtag Selected
Patching Jasper version 2.3 SMC at offset 0x12BA
XeLL file created Successfully falcon.bin
Initializing falcon.bin..
Header is wrong..
Falcon/Opus
Nand Initialization Finished
Patching Jasper version 2.3 SMC at offset 0x12BA
XeLL file created Successfully falcon.bin
Version: 01
Flash Config: 0x01198010
Writing Nand
falcon.bin
Done!
in 0:18 min:sec

Image of R-JTAG board: Added
20140311_223354.jpg

Images of close-up soldering to motherboard: Added
(attach images to your post)
20140311_223422.jpg
20140311_223536.jpg
20140311_223723.jpg
20140311_223635.jpg

Description of problem: The R-JTAG board smokes every time I plug in the power for the 360 but the green LED (on R-JTAG) glows when I power on the console. Yet I get random error codes on every DIP I try like 0022, 0132 and 1022.
I solved 0022 by writing original NAND back then writing Xell again once I did the R-JTAG started smoking, I tried bridging the 1.2v points on the R-Jtag Chip but the green LED doesn't light up at all. Console works when returned to stock NAND. I also noticed that the part circled in the picture heats up and is the source of smoke.
20140311_223354(2).jpg

Was the console working before you started: Y/N

View from Top:
IMAG0802.jpg
 
Last edited:

Precarious

Junior Member
Jan 23, 2014
15
0
Have updated post with pictures. Hersheys247 thanks for the quick reply. Hopefully you recognize something wrong.
 

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
Maybe you got a defective chip. it doesnt happen often, but isnt unheard of either. it could also have something to do with how much wire is exposed, as it could have shorted out somewhere. My advice, replace the chip, and cut down the wires.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
It's probably defective now, yes.



It would help if you soldered CPU_RST (Blue) to the correct point.

I won't even mention how bad the other soldering is.
 

Precarious

Junior Member
Jan 23, 2014
15
0
It's called Macro mode.

OP: Does the stock NAND boot?
Will get a picture right now. It does boot in stock NAND.

It's probably defective now, yes.



It would help if you soldered CPU_RST (Blue) to the correct point.

I won't even mention how bad the other soldering is.
It is in the right point but I had to scrape the pad to get to the track and solder the wire there. Also what do you mean defective now? Did I solder something to the wrong place? I used so much flux and didnt clean up the residue with some alcohol but is there anything else noticeable about soldering? I only wish to improve.
 
Last edited:

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Soldering is the most important thing and you're dismissing it right away. If you couldn't solder beforehand, you weren't really wise in starting with something like this. Learning by mistake is a very harsh road. I suggest removing everything, writing the original NAND back and making sure the console still boots.
 

Precarious

Junior Member
Jan 23, 2014
15
0
Soldering is the most important thing and you're dismissing it right away. If you couldn't solder beforehand, you weren't really wise in starting with something like this. Learning by mistake is a very harsh road. I suggest removing everything, writing the original NAND back and making sure the console still boots.
I have already done that as stated in the description. I solder before on over 35+ controllers doing rapid fire mods. Nothing in the console is damaged from soldering. I checked before and once again just for you ;). Oh I added a new picture in the OP.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Then you've obviously damaged the R-JTAG chip. Looking at your chip install, it's a mess - you could have a shorted/bridged anything in the process. Lifting pads on the chip is an indication of needing to gain more experience first.
 

Precarious

Junior Member
Jan 23, 2014
15
0
Then you've obviously damaged the R-JTAG chip. Looking at your chip install, it's a mess - you could have a shorted/bridged anything in the process. Lifting pads on the chip is an indication of needing to gain more experience first.
The pad was lifted because I forgot to lower the temperature. Trial and Error is the best way to learn. “It is common sense to take a method and try it. If it fails, admit it frankly and try another. But above all, try something.”
 

Precarious

Junior Member
Jan 23, 2014
15
0
Yes - you damaged it. The smoking indicates this.
If I damaged it I just fixed it no thanks to you. this is why I prefer to learn from trial and error. I just added flux and soldered a point that didn't seem right on the R-JTAG board and it works perfectly. I did the Aud_Clamp method and it boots almost instantly. The point is the one circled in the picture below.
IMAG0802.jpg
For others reading this thread DIPS 4 and 7 were on.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
If I damaged it I just fixed it no thanks to you. this is why I prefer to learn from trial and error. I just added flux and soldered a point that didn't seem right on the R-JTAG board and it works perfectly. I did the Aud_Clamp method and it boots almost instantly. The point is the one circled in the picture below.
View attachment 25471
For others reading this thread DIPS 4 and 7 were on.
No thanks to me? With the information given, my best 'guess' was the board was damaged as components shouldn't smoke. We ask for full images in the template. Did you supply a top-down view of the chip before? nope.

I had already stated the soldering was horrible. That capacitor wasn't shipped like that - you did it.

You're welcome.
 
  • Like
Reactions: Precarious
Status
Not open for further replies.