Nand dumps are not identical.

[ravihpa]

Hi guys,

My friend who is a professional PS2 modder and Xbox 360 RROD fixer was successful in applying the LPT connections and the JTAG connections.  When starting AutoHacker, I can get to the screen where it shows my mobo as Falcon and my CB being exploitable.

Now, whenever I try to make dumps of my nand, they ALWAYS seem to be different and automatically get deleted   I even tried manually dumping with nandpro by manually putting commands.  The 2 MB ones are perfect matches, but the 16 mb ones don't match.

I also compared them with Total Commander, but it said there were 14 differences.

What would you recommend me to do ?  By the way, here are 2 pictures of my JTAG connections.  We had a little bit of difficulty connecting the J2D2.1 to DB1F1.  Pardon the crap quality of the pics.  It's the best I could take using my phone





He said, and I am quoting, "we almost lost that point - DB1F1".  In the end, he managed to solder a wire to DB1F1 and another wire to J2D2.1 and put the 1N4148 diode in between

The white wire is going from J2D2.2 to RF panel 6 (1N4148 diode).

Since Autohacker was able to get the CB and mobo version, etc., I am quite certain our LPT setup is PERFECT   So, please recommend me as to what should I do now

Desperately waiting for a reply

Edit: By the way, here's how the LPT cable looks like....

[ravendrow]

if i had to guess i'd say try shortening the cables. i try to keep the wires as short as possible when i jtag a 360 also depend on your pc you might not need the resistors we need just a little more info like what was your flash config using nand pro

[miragui]

Use shielded cable you will get better results.

[yoyodunno]

Yeah the cables usually need to be shorter than that. There was a post on some forum where a guy actually tested cable lengths in relation to getting good NAND dumps, and found that the best length is around 1 foot for good dumps. Also, yeah it can depend what cable you're using,  since it's unshielded i have heard of people grounding it for good results too.

[ravihpa]

if i had to guess i'd say try shortening the cables. i try to keep the wires as short as possible when i jtag a 360 also depend on your pc you might not need the resistors we need just a little more info like what was your flash config using nand pro

I am using AutoHacker that was just released by BladBloke.  It detected that I have an exploitable CB.

Use shielded cable you will get better results.

OKay, we'll try to experiment with a shielded CAT5 cable

Yeah the cables usually need to be shorter than that. There was a post on some forum where a guy actually tested cable lengths in relation to getting good NAND dumps, and found that the best length is around 1 foot for good dumps. Also, yeah it can depend what cable you're using,  since it's unshielded i have heard of people grounding it for good results too.

Hmm....I'll ask him to cut this cable short in length, and we'll see how it goes

So all in all, from what I can gather, long cable should be shielded and short cable, even if unshielded, will do, BUT it would be better if the cable is small.

Thank you so much for all the replies guys.  REALLY APPRECIATE IT  I'll tell him to cut short the length and will post here the results.

THANX A LOT

EDIT: Guys, I have a very simple question I would like you to answer.  When actually will the JTAG wiring be coming in use ? AKA, what error should I look forward to if my JTAG wiring is not proper ?

The reason I am asking is coz my JTAG wiring might be in a "critical condition" as we almost lost DB1F1, and my modder friend saved it by connecting that point with a wire at the BOTTOM of the board.  He checked the connections with a multimeter and was sure that it's proper.  Hence, if I encounter that error, then I'll come to know right away that it's coz of the JTAG, and we'll be EXTRA CAUTIOUS in dealing with it.

Thank you so much for all the help. Really appreciate it.

[Arakon]

If your buddy calls that "proffessional soldering", I'd hate to ever give any console to him to work on. That's messy as hell, and considering the lpt dumping is very sensitive to interference, it's no surprise that you get errors/differences.


The jtag wiring is only of concern once xell or XBR are flashed. You'd get E79 with bad jtag wiring.

[jelle2503]

these kind of "problems" are discussed like 10 times on here already

why do you need another topic

[martyboy2011]

hi can any one help I have been tryin to jtag my xbox360 it is a falcon checked it was exploitable and yes it came back ok but the problem was I dumped the nand 4 times got two that matched but it was total comander that said they matched when I use the degraded program it says it isn't but I already had flashed the nand  and it didn't work I have tried repairing the backup nand dump and patched that again and got error e79  then the next time i tried it got the xbox not powerin up have recovered from that and get the xbox powerin up constant green light but no picture as in no video signal plz help on here or email me at martinmcmullan@live.com

[martyboy2011]

sorry forgot to add the cb version is 5770

[peshkohacka]

hi can any one help I have been tryin to jtag my xbox360 it is a falcon checked it was exploitable and yes it came back ok but the problem was I dumped the nand 4 times got two that matched but it was total comander that said they matched when I use the degraded program it says it isn't but I already had flashed the nand  and it didn't work I have tried repairing the backup nand dump and patched that again and got error e79  then the next time i tried it got the xbox not powerin up have recovered from that and get the xbox powerin up constant green light but no picture as in no video signal plz help on here or email me at martinmcmullan@live.com

I just wonder why you ask for help now? You already flashed with a f***ed up cable and judging by the problems you don't have a proper backup. If you don't have a proper backup, put Xell with a better cable (no longer than 30cm, shielded, BAT41, properly soldered), get the CPU key and build an image with a donor nand.

[mat989]

*Sorry, so you did flash your nand!!!*