After getting the . . .
J-Runner v0.2 Beta (289) Started
Version: 10
Flash Config: 0x00000000
Can not Continue
. . . error all yesterday today I decided to fault find using the guide Martin C wrote. I removed the Nand X QSB and measured the results.
Point (on Martin Cs' guide) - Voltage, Resistance
1 - 1.56v 100k
2 - 2.99v 88k
3 - 0.067v 1.2k
4 - 0v 80k
5 - 3.22v 1.9k
6 - 0.88v 5.4k
R3B14 (equiv) 32 Ohms
R3B15 (equiv) 32 Ohms




Can you confirm that pins 6 and 7 (J2C1) are connected together? Can't seem to find a good enough photo Online to check.
J2C1.3 - is only 0.067v. Is that ok?
The process I followed is the following;
1. Connect JRP to PC (see the logo appear in J-Runner)
2. Connect the JRP to the wiring to QSB's and R-JTAG board plug
3. Plug the console in and leave in standby mode.
4. Try to read the Nand in J-Runner
At the risk of a stupid question . . . . . As a side, could I just plug the JRP into the QSB's with the R-JTAG completely disconnected?
The console powers up to the NXE ok. I believe it is stock not Xell as it does not boot into xell with eject. A very strange thing is that I can not sync my controller anymore. However I do see the opening/closing when I hit the eject button.
Have also tried writing the V2 firmware to the JRP. It does show the logo in J-Runner and reports Version 10.
I have gone round in circles so many times now. I have had the console R-JTAGed 2 twice sucessfully now but Ive not gotten to the point where it is all working 100% buttoned up in the case.
If the readings are within range would the Nand shorting trick be of any use?
Very confused and frustrated. Been at this for 2 weeks!
thank you.
P.S. Don't assume I know anything at all, just incase I have made a glaringly obvious mistake!
EDIT: Just to mention that when I soldered the QSB's (top side) on I could read and write the Nand fine initially.
J-Runner v0.2 Beta (289) Started
Version: 10
Flash Config: 0x00000000
Can not Continue
. . . error all yesterday today I decided to fault find using the guide Martin C wrote. I removed the Nand X QSB and measured the results.
Point (on Martin Cs' guide) - Voltage, Resistance
1 - 1.56v 100k
2 - 2.99v 88k
3 - 0.067v 1.2k
4 - 0v 80k
5 - 3.22v 1.9k
6 - 0.88v 5.4k
R3B14 (equiv) 32 Ohms
R3B15 (equiv) 32 Ohms




Can you confirm that pins 6 and 7 (J2C1) are connected together? Can't seem to find a good enough photo Online to check.
J2C1.3 - is only 0.067v. Is that ok?
The process I followed is the following;
1. Connect JRP to PC (see the logo appear in J-Runner)
2. Connect the JRP to the wiring to QSB's and R-JTAG board plug
3. Plug the console in and leave in standby mode.
4. Try to read the Nand in J-Runner
At the risk of a stupid question . . . . . As a side, could I just plug the JRP into the QSB's with the R-JTAG completely disconnected?
The console powers up to the NXE ok. I believe it is stock not Xell as it does not boot into xell with eject. A very strange thing is that I can not sync my controller anymore. However I do see the opening/closing when I hit the eject button.
Have also tried writing the V2 firmware to the JRP. It does show the logo in J-Runner and reports Version 10.
I have gone round in circles so many times now. I have had the console R-JTAGed 2 twice sucessfully now but Ive not gotten to the point where it is all working 100% buttoned up in the case.
If the readings are within range would the Nand shorting trick be of any use?
Very confused and frustrated. Been at this for 2 weeks!
thank you.
P.S. Don't assume I know anything at all, just incase I have made a glaringly obvious mistake!
EDIT: Just to mention that when I soldered the QSB's (top side) on I could read and write the Nand fine initially.
Last edited:
