Falcon R-JTAG Install Issue, Please Help! (0x00000000 + 0010)

jsheradin

jsheradin

Full Member
Aug 15, 2013
39
0
United States
www.jsheradin.000a.biz
So I recently acquired an old Falcon Xbox from a friend who is saving for the Xbox One. I had heard about the new R-Jtag mod and thought I might as well give it a try. I have six Xbox's currently (seven including the falcon). I have performed countless mods and repairs on a few dozen Xbox's so I know my way around the console. I have been modding them ever since the original JTAG came out so I know what I am doing (old JTAG and RGH at least), and still have a decked out Xenon that matches my main Jasper BB. Anyways I am looking to liquidate some of my inventory to prepare for the next generation of stuff coming out, so I figured that I will try to sell as many of them as I can. To maximize my profit I was looking to R-JTAG up the falcon and then convert my beloved Jasper into a Demon Dual-Nand R-JTAG beast. I ordered an R-JTAG Ultimate kit, a standard kit, and a Demon w/BB upgrade from CK3.co.uk (even though I live in the US). I was installing the kit in the Falcon and everything went smoothly , I used plenty of flux, kept everything neat and clean, wired it up exactly based on the Xecuter guide, and when I went to read the NAND and write Xell some unfortunate problems occurred. When in J-Runner (build 290) I somehow got a 0x00000000 Flash config error. Naturally I checked all my soldering and did a little Googling and found that some people had similar issues with the J1D2 QSB so I de-soldered it and did a direct wire install. I successfully got two matching NAND dumps and went to write Xell. This is where things get a little frustrating. I once more got the 0x00000000 Flash Config cannot continue error. This time I plugged up the Xbox to see if everything was all good and it presented me with the infamous 3 RROD (0010 secondary error code). Dumbfounded I reflashed the .hex file included with J-Runner to my JRP, double checked all of my soldering and tried again, same error, still RROD'd. Next I re-soldered the glitch chip and quintuple checked all of my soldering points. I even undid the NAND wire install, stripped 'em back and tried again with fresh section of wire. Still no NAND r/w or power on, it instantly goes to RROD and the chip doesn't even get chance to DIP it just sits there with a red light. I unsoldered the glitch chip, and set the AUD_CLAMP QSB to off and still get the same errors. I took lots of pictures in the hopes that I just missed something simple and that one of you can point it out. Please don't hesitate to correct me or recommend something to try. Yes I did read that the 0010 secondary has something to do with the GPU and the south bridge connecting and that it can be remedied by a reflow/re-ball. I do have a AOYUE 968 reflow machine and a modified skillet that I used to use to fix RROD Xbox'x but because I want to get top dollar for this one and have no risk of it breaking I will probably use a reball service online. I found one on eBay that will reball the GPU and CPU for ~$70, is that a good deal? I just want to make sure that that would be absolutely necessary in the hopes that I just screwed up something in the install process or there is some bug with the JR-Programmer. I would use RATER and try to see where the problem lies, but as of now I can't get it to write xell/original nand or even connect to Rater/J-Runner (still gives the 0x00000000 cannot continue error). Once again please let me know anything that may help.

Pictures of install: http://postimg.org/gallery/2ff5vn1k/

Relevant portion of the J-Runner Log: http://pastebin.com/sjeECFWQ

J-Runner info on the NAND's I got: http://postimg.org/gallery/a767kjiu/

Guide I used: http://team-xecuter.com/forums/showt...-26th-2013-***

Pictures of my main box's: http://postimg.org/gallery/7zyhrzwu/
 
Last edited:
G

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
If you have a demon, use that to read and write the nand...... if you want to use it in another console i would suggest using the wire install points which are right behind the quick solder points. this should at least let you flash a nand image..... and i would start with your stock image just to make sure your stock image is ok then go from there......
 
G

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
I would also try testing nand points with a multimeter. Martin has a guide for this somewhere on here, i remember reading it a while ago.
 
jsheradin

jsheradin

Full Member
Aug 15, 2013
39
0
United States
www.jsheradin.000a.biz
Ok, so all the points checked out (however point 1 and 3 were closer to two volts rather that 1, about 1.85v on both). I managed to locate another JR-Programer (from a friend) and tried to read the NAND, same error. I then tried to write the xell file created with the first successful dumps, and got the same error using both programmers. I then disconnected the JRP and tried to power on the xbox and now it does nothing. I tried a different RF board and the same thing. It just sits there, no fans, led's nada. However the NAND points still have correct power readings (if 1.85v is ok). I have an old school FTDI style JTAG programmer that I used back in the NandPro 2 days, should I try that? Is there any hope left at all? Or should I just cut my losses and see if I can at least save the R-JTAG kit. This is unbelievably frustrating, especially since I followed all the instructions to the T.
 
Last edited:
G

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
it sounds like you corrupted the nand, so you will have to flash back stock nand. if you hook up the demon, you can read/write the stock nand with it, and the points go directly to the nand chip itself...... also when using a SPI flasher i have found that if you try to boot the system right after flashing it will also corrupt the nand, and you will not get any power on. hook up demon, flash stock, and try booting again. just hook up with wires for easy removal, so you can later install it in your jasper. oh and your nand-x qsbs could also be bad...... not likely, but these things do happen from time to time...... just try using the demon for nand read write, once u get it to boot xell, you can use xell to flash freeboot image, dont forget to shut off and unhook power for about 30sec after flash completes, or it is possible that you will have to hook up demon again just to flash the image back to it..... it can also be updated this way.

Also if the stock nand dump is corrupt, the system will not boot, and i think that it will be a task and a half trying to bring it back...... needing donor nands, and everything else...... the biggest problem is rebuilding the keyvault.
 
Last edited:
jsheradin

jsheradin

Full Member
Aug 15, 2013
39
0
United States
www.jsheradin.000a.biz
I had a feeling that could be the case, I will install the Demon tomorrow with some 30AWG kynar wire. Do you recommend using J-Runner or Demon Tool-Box to do the actual NAND dumping/flashing once installed? I assume that I would use Demon toolbox to flash the original back, test it, use J-Runner to make the xell file, flash it using Demon toolbox, and then once the CPU key is obtained flash it via flashdrive through xell (updflash.bin). Am I correct? Also, if the stock NANDs (2 matching reads 0-3FF no errors) that I managed to get earlier were to be corrupt, wouldn't it have shown on the bad blocks tab of J-Runner?
 
Last edited:
scott1503

scott1503

VIP Member
Jul 21, 2012
1,794
88
Harrogate, North Yorkshire , uk
jsheradin

jsheradin

Full Member
Aug 15, 2013
39
0
United States
www.jsheradin.000a.biz
Wow, sorry! I guess I thought the letter corresponded to a different pad! Thanks for pointing that out, just saved me a whole other ordeal. I'll change that ASAP, but I doubt that that could have caused this problem. I can't believe I overlooked that! Thanks again!
 
G

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
jsheradin said:
I had a feeling that could be the case, I will install the Demon tomorrow with some 30AWG kynar wire. Do you recommend using J-Runner or Demon Tool-Box to do the actual NAND dumping/flashing once installed? I assume that I would use Demon toolbox to flash the original back, test it, use J-Runner to make the xell file, flash it using Demon toolbox, and then once the CPU key is obtained flash it via flashdrive through xell (updflash.bin). Am I correct? Also, if the stock NANDs (2 matching reads 0-3FF no errors) that I managed to get earlier were to be corrupt, wouldn't it have shown on the bad blocks tab of J-Runner?
Click to expand...
i would use j-runner for flashing, but demon toolbox has to be installed for the demon driver. and that wire mismatch would not effect nand read/write. and the nand dumps could match, and J-runner could say there were no bad blocks, and the information in those blocks could still be corrupt..... easiest way to test is write back stock nand, and disconnect post out ribbon cable and see if it boots stock, from there if it boots flash ecc, hook post out back up, get cpu key, create new nand, flash new nand, remove demon...... then go through tweeking boot times. Also any time you write a new nand unplug power for 30 seconds before turning on system.
 
Last edited:
jsheradin

jsheradin

Full Member
Aug 15, 2013
39
0
United States
www.jsheradin.000a.biz
gavin_darkglide said:
i would use j-runner for flashing, but demon toolbox has to be installed for the demon driver. and that wire mismatch would not effect nand read/write. and the nand dumps could match, and J-runner could say there were no bad blocks, and the information in those blocks could still be corrupt..... easiest way to test is write back stock nand, and disconnect post out ribbon cable and see if it boots stock, from there if it boots flash ecc, hook post out back up, get cpu key, create new nand, flash new nand, remove demon...... then go through tweeking boot times.
Click to expand...
Will do, sounds like a job for tomorrow though. A good night's sleep and a fresh attitude can solve a lot of things!
 
G

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
i should also point out that u should not hook up the demon coolrunner ribbon cable if you are just flashing and testing from stock nand. this will allow the r-jtag to glitch on stock nand.
 
jsheradin

jsheradin

Full Member
Aug 15, 2013
39
0
United States
www.jsheradin.000a.biz
Ok, so I installed the Demon via a freak-ton of wires (yes I set the switch to XB) and it all went well (I thought). I hooked up the box to power and the Demon to the computer after installing ToolBox and drivers; J-Runner found the Demon and the little logo popped up. I was able to create write xell to the NAND on the xbox, I unplugged the Demon from the PC, unplugged the power brick, counted to 30, plugged the PSU back in, and set the Demon to xbox nand, lo and behold.... no power. I repeated the steps to write one of the original dumps to the box, same issue, and then went on to write both to the Demon. You can see everything I did in the log. I managed to get some activity from the box if I tried to boot from xell on the Demon, but that was a freak incident I think. I wrote xell to the Demon and had stock NAND on the xbox, plugged in the PSU the Demon lit up and without even pushing a button or anything it just decided to boot, of course with my luck it was the instant 3RROD I tried to power it off, but the power button was unresponsive as were the sync and eject buttons. So I unplugged the PSU and plugged it back in and it was dead again. I never hooked back up the actual glitch chip throughout this ordeal, should I? I realize xell wont boot, but shouldn't it at least boot/RROD when the stock is flashed? Should I try hooking back up the JRP and see if I can get Rater to work(also, I can't find a dl for the latest version of rater, anybody have one)? Any suggestions? Should I try to power it on with the controls in Demon toolbox? Should I opt for the reball? I already have $100 tied up in this thing (cost of box + R-Jtag) not including the Demon, so I really don't want to spend another $70 on a reball. Is there any hope left? Any at all?

Demon install (with diagram I followed to install it): http://postimg.org/gallery/7k2864ci/

Relevant portion of J-Runner log: http://pastebin.com/UJEZz0S8
 
Last edited:
jsheradin

jsheradin

Full Member
Aug 15, 2013
39
0
United States
www.jsheradin.000a.biz
Another update! So while waiting eagerly for a reply on this thread, I broke out the good ol' multimeter and tested the NAND points again, this time I got some results! Results that actually mean something! All were normal, apart from 1 and 3 on J1D2, they read as 0.05v and 0.08v. According to Martin's guide as stated earlier if they are "less than 1v (i.e 0.05v and a resistance less than 2k)" (which mine are) it can either mean that the SouthBridge needs a reflow/reball or the SMC is corrupt. My money is on the SMC being corrupt given that it was a freak incident that I managed to get the dumps anyways. Is there any way to test this theory/rebuild the SMC (I have plenty of donor NANDs, just a bunch of E79 xenons and a few zephyrs that aren't really worth fixing)? Should I do a reflow of the SB to make sure? I have a rather professional reflow station and have plenty of experience reflowing GPU's and CPU's, anybody know the heat rating on the South Bridge just so I don't end up cooking it?

- - - Updated - - -

I also just realized that the SB having a cold joint would also explain the 0010 error! Any advice before I break out the skillet?
 
You must log in or register to reply here.