- Jun 17, 2005
- 5
- 0
Probably a bit of a long read... I am quite new to this aspect of 360 moding... Attached 2 pictures hastily taken to show soldering job. Not my soldering btw (I can't do that worth anything) as that seems to be a common request from people offering help.
Already read the thread: http://www.team-xecuter.com/forums/showthread.php?t=54748
so have been assuming something wrong with soldering (and something was) but tests seem to indicate that it's ok now (at least from a continuity perspective).
Solder is 60/40 rosin core (not sure the thickness). Iron is AUYOE Int 2900, thin tip (350c IIRC). Flux was used (not sure what type but I believe it doesn't require cleanup).
Had a bit of a problem with the normal jtag path (got the wire in place fine once but then bumped later and it came loose, couldn't get anything to stick since so went another route, see below).
QSBs used (as seen in pictures).
Continuity from bottom of board to top of solder points (ohms tester) for all points (related to nand read/write) is good. Specifically tested j1d2 and j2b1. No cross talk (continuity between 2 different points) except where expected (on the j2b1 - compared with an un-moded board).
Drivers installed, tried both the drivers that come with nandpro 20d (that included signed drivers for nand-x) and nandpro 20e generic memory device.
Tried longer USB cable (easier to work with) and shorter cable that came with nand-x.
Something I picked up from the 'net - tried powering on the 360 and then issuing a request to read the nand (nandpro usb: -r16 orig.bin) causes the console to shut off... powered on or off (in the off case, power supply light is amber) still get the error message. Not only is power supply plugged in durring attempts but drive is also plugged in (data and power) just in case.
As for the small yellow wire on j1d2, original attempt on that path was bad (I don't know the details exactly) and while repairing, damaged the trace on the QSB. Continuity on that wire is good though from back of the board to through the to the pin on the QSB... (person doing the soldering has done repairs like this previously when traces got damaged).
As for the jtag - it's the aud clamp + DVD tray (might have that wrong but from what I understand the jtag aspect isn't in use yet since I can't even read the nand).
I don't know for sure what the board is but I know it's non-xenon. (mfg 2008, HDMI, elite).
Oh, I have 2 nand-x and tried them both, also tried different computers just to see if that might have anything to do with... anything...
winxp btw (32 bit).
The only thing (I can think of) I haven't tried is having it plugged into video while trying to read the nand.
Would love some tips on where to go next (preferably without having to remove the QSBs, am worried that tape could pull some traces from the board). Pin headers are an option (have wick) but direct wires not so much. Also would love to know if the jtag aspect has any role to play trying to read the nand for the first time.
Already read the thread: http://www.team-xecuter.com/forums/showthread.php?t=54748
so have been assuming something wrong with soldering (and something was) but tests seem to indicate that it's ok now (at least from a continuity perspective).
Solder is 60/40 rosin core (not sure the thickness). Iron is AUYOE Int 2900, thin tip (350c IIRC). Flux was used (not sure what type but I believe it doesn't require cleanup).
Had a bit of a problem with the normal jtag path (got the wire in place fine once but then bumped later and it came loose, couldn't get anything to stick since so went another route, see below).
QSBs used (as seen in pictures).
Continuity from bottom of board to top of solder points (ohms tester) for all points (related to nand read/write) is good. Specifically tested j1d2 and j2b1. No cross talk (continuity between 2 different points) except where expected (on the j2b1 - compared with an un-moded board).
Drivers installed, tried both the drivers that come with nandpro 20d (that included signed drivers for nand-x) and nandpro 20e generic memory device.
Tried longer USB cable (easier to work with) and shorter cable that came with nand-x.
Something I picked up from the 'net - tried powering on the 360 and then issuing a request to read the nand (nandpro usb: -r16 orig.bin) causes the console to shut off... powered on or off (in the off case, power supply light is amber) still get the error message. Not only is power supply plugged in durring attempts but drive is also plugged in (data and power) just in case.
As for the small yellow wire on j1d2, original attempt on that path was bad (I don't know the details exactly) and while repairing, damaged the trace on the QSB. Continuity on that wire is good though from back of the board to through the to the pin on the QSB... (person doing the soldering has done repairs like this previously when traces got damaged).
As for the jtag - it's the aud clamp + DVD tray (might have that wrong but from what I understand the jtag aspect isn't in use yet since I can't even read the nand).
I don't know for sure what the board is but I know it's non-xenon. (mfg 2008, HDMI, elite).
Oh, I have 2 nand-x and tried them both, also tried different computers just to see if that might have anything to do with... anything...
winxp btw (32 bit).
The only thing (I can think of) I haven't tried is having it plugged into video while trying to read the nand.
Would love some tips on where to go next (preferably without having to remove the QSBs, am worried that tape could pull some traces from the board). Pin headers are an option (have wick) but direct wires not so much. Also would love to know if the jtag aspect has any role to play trying to read the nand for the first time.