Print

[Bukmop]

We all remember the diagram for Jtag Hack very well. I mean there are 2 diodes and 1 wire (as jumper).
    Few days ago I needed to get the CPU key using Xell loader. My MB version is Falcon. At first I've read the original NAND successfully. Then I've prepared falcon_hack.bin for flashing. After successful flashing procedure I've soldered 2 diodes and 1 wire following diagram. When I've powered on my Xbox I saw 3 RRoD. I was confused. Several reflashing procedures didnt solved my problem. Every time when I've powered on my console 3 RRoD appeared.
    In that moment I've recalled about early version of diagram for Jtag Hack. I mean 330 Ohm resistors. And I've decided to use one 330 Ohm resistor instead wire (between J2D2.4 and J2D2.7). Finally it fully solved my problem. And 3 RRoD are no more. With that resistor everytime I've got the successful booting of Xell loader. I think this information will be useful for our forum members.
(IMG:http://img228.imageshack.us/img228/6992/diagram1.jpg)

This post has been edited by Bukmop: Dec 4 2009, 05:24 PM

[Haygar]

GENIUS. Invaluable bit of info. I thought I was losin it!

I was having the same problem, even read back my written XBR from the nand and compared identical but was getting E79. Now with the 330R resistor in place I can boot xell. I only injected my kv to my image but it still wont boot the nxe dash?
Somethings not right with the jtag mod on falcons if this is what some people have to do.
Makes you wonder if 330R is the correct value also.
I might reconnect my lpt wiring and try also injecting my config.bin. I had done that but reversed it coz it didn't help and others were getting theirs going by only putting in kv.bin but now with this new help - crossing fingers.
I'll report back if it works or if I find a solution but I'm running out of ideas.
I had no probs with my old xenon but it keeps crashing due to a pre existing rrod problem.

[Chaosplt]

ohh great. I have a falcon! read the nand fine twice both were the same..  Tried to flash the modified xbr.bin file and it would give me error 79 and sometimes 3 red lights.. I dont' have a resistor in place. I only have a Diode in place in the red wire.   Then i tried flashing the original nand back, but same problem..  Can this solve my problem? Im gonna try it tomorrow.

[Haygar]

Its definitely worth a try if everything else seems ok but it still wont boot.
Seems strange that others haven't had to do the same thing on their falcon.

I found that I could get it to work with anything from 100 - 470 ohm but at the extremes it would intermittently error at start up so 220 - 330R seemed the most stable. Any higher or lower , nothin.

It was the very thing that got my other falcon loading xell, my other problem was actually yet another rrod problem with xbr or orig dash not booting. I can flex the pcb slightly and get red lights, otherwise it would just sit there and flash the centre green led. Since xell doesn't use any gui I guess that spells a gpu problem (surprise surprise) At least that answered why it looked like a problem with the flash.

I've got to find some quality time to do my last and only surviving falcon and do this right, but I've learned a lot and a few tricks along the way thanks to people on here.


Oh. I just realised, you said you just get e79 but didnt say if thats when booting XBR only. If xell IS booting for you then this may not be your answer but its gonna take no effort to try anyway. Good luck

This post has been edited by Haygar: Dec 13 2009, 09:24 PM

[Chaosplt]

Fixed it, now booting xbr...  have the 330 ohm resister in place, soldered the red wire in the pic to the alternate area on the bottom trace of the motherboard after fucking up twice...   Reflashed my nandorig.bin file, Then xxpittbullxx injected the keyvault for me into the XBR for me.  ( for some reason my pc wasn't doing this right)( or it was me who knows..)  Flashed the xbr-kv.bin version to my xbox 360. Booted into xbr. Now have to make sure the stupid little delicate solder point in the bottom doesn't come off. Gonna hot glue gun it.

[arielzadi]

what diodes did you use?
the diode that was used to read nand?
and can someone please post a high reolution pic cuz it isnt that clear where i should make the connection

[beogradski-fantom]

QUOTE(Haygar @ Dec 13 2009, 09:17 PM)

....

I found that I could get it to work with anything from 100 - 470 ohm but at the extremes it would intermittently error at start up so 220 - 330R seemed the most stable. Any higher or lower , nothin.

....

Well as I have no 330 ohm resistors I soldered a 100 ohm resistor to it. To my surprise I now got a RRoD instead of just 1 green light blinking and the e79 error code. Well I'll get 330Rs tomorrow and try that out.

Just one question, did you also get the RRoD while trying it with 100 ohm resistors or something else? And if so do you remember which Error code you got? Me I got the 0022 Error code.

[lovejelly]

The diode going to DB1f1, are you soldering this direct to the board or are you putting the diode in between both points and soldering the wire to the DB1f1 point?

I have my diode directly soldered to the board so I'm wondering if this is where I'm going wrong.

Cheers.

[beogradski-fantom]

looks like I don't need the 330 ohm resistor anymore. I figured out that I have soldered the bridge wire wrong.

[Haygar]

QUOTE(lovejelly @ Dec 15 2009, 08:47 AM)

The diode going to DB1f1, are you soldering this direct to the board or are you putting the diode in between both points and soldering the wire to the DB1f1 point?

I have my diode directly soldered to the board so I'm wondering if this is where I'm going wrong.

Cheers.

Have them soldered at the J2D2 points and kynar wire for the jumpers to the other points. I used 1N4148 diodes, common as mud for me and are normally fine for small signal switching apps like this

[lithium210]

i was also getting random rrod (rarely though) on my falcon xbreboot 3a but i tried your fix of adding a 330ohm resistor on the jtag J2D2.4 and J2D2.7 points and so far i havent seen any rrod. thanks for the tip!

[Snigel]

My 1N4148 diodes seems to be dying could the lack of this resistor be related to that? As it is now, I can use the machine for like ~2 hours, then the diodes goes which results in lots of weird errors, sometimes e79.

If it's related I've written more detailed here:
http://forums.xbox-scene.com/index.php?sho...p;#entry4615512

[fatalert]

I can really use some help right about now trying to get XBR running.
I've read quite a lot around before posting here but right about now I don't know how to

poceed.

I have a falcon box, manufacture date 8/2008, with a 175W PSU ( so no jasper )
I have all wires inplace ( jtag and lpt )

I've used 100ohm resistors and bat41 diodes.

I have successfully dumped my original nand 4 times in a row, verified the files with

nand compare and total commander and all 4 were identical so I feel confident that these

files are correct.
I have extracted rawkv.bin and rawconfig.bin from the original files.
I have no bad blocks in the nand so remapping was not needed

I inserted them into the falcon 8955_3a XBR image and flashed back.
After testing, I sucessfully went to Xell, got my CPU key and tried XBR.
This gave strange issues, I booted to the 360 logo and when I pressed the Xbutton on the

controller it gave me the quick menu but nothing else.
The regular dashboard did not work beyond this.
I suspected a incorrect flash ( since I did not verify it after flash so decided to flash
the same image again).


This is were I got into trouble, the flash started normally but at block 33 it started
to fail, apparantly every block after that gave issues.
I had a hard time detecting the flash controller again after that but after booting the
box up ( with rrod of course ) it finaly came back.

Flashed again and did verify and it seemed that there were differences ( 8 differences
between the flashed nand file and the original)

Eventually broke up the XBR in 16 pieces and flashed them perpiece ( 40 blocks) by following method:
1. erase part ( not needed but can't harm )
2. flash part
3. read flashed part back from nand and compare with original chunk
if match move to next chunk and repeat above steps

this way I got a 100% verified flashed image.

To be absolutely sure I dumped the complete image back and compared to the original xbr.bin ( with kv injected ) and it matched.

However, booting still gave rrod and xell was unavailable.
I doublechecked the jtage wires but they haven't been touched and before the failed flash operation Xell worked perfectly. I have them with two diodes connected

Can it be that the whole box is in a fail state ?
I remember this could happen years ago when the first rrod's started showing that you had to reset the box to get out of rrod state.
The trick was then overheating it on purpose to reset the box.

Could this be what I have now ?
as I said the flash is 100% double verified correct and the wires appear intact ( and have worked )

If reset is the solution, can someone tell me how to do this the easiest way ?
I remember something about a wet towel but that somehow doesn't seem like the proper way to go.

PS in case someone wonders,
when it RROD's , it does not show anything onscreen.
Just rrod very quickly.
It shows three RRods.
I tried getting into xell with eject ( used to work before ), with dvd remote MC button, and with wired controller X button plugged in back usb port - all RROD

Thanks in advance for any feedback on this matter

[Snigel]

If you think it's hardware failure, try reflashing original firmware and see if it still goes RROD. Otherwise apply 330 ohm resistor and see if it makes any difference.

[fatalert]

QUOTE(Snigel @ Jan 17 2010, 12:12 AM)

If you think it's hardware failure, try reflashing original firmware and see if it still goes RROD. Otherwise apply 330 ohm resistor and see if it makes any difference.

I flashed original bac k and verified flash image and it still rrod's like when Xbr is flashed.
Jtag wires are still in place.

I know that original should boot with the wires in place ( lots of conflicting info about that but someone confirmed it from first hand experience ) but could a faulty jtag wiring cause these kind of rrod's when booting original ?