JTAG Jtag written file XBOX 360 Jasper 16mb.

[hawkeye1103]

Hello,

I have tried to RGH 2.0 my xbox 360 Jasper and have hit a speed bumb. I dumped the nand 4 perfect copies, and out of lack of attention I wrote to the console the jasper.bin (which is for JTAG) instead of the ECC.

I am running: 16756
CB: 6754

From what i've noticed the J-runner doesn't have a RGH 2.0 for the firmware my console is on.

and now the problem: I can't seem to flash the original firmware back on... it gives me the following error.
Version: 01
Flash Config: 0x00000000
Can not Continue

What I have tried till now: to remove the coolrunner rev c
- desolder and resolder the connections to the JR Programmer
- clean all the connections of the coolrunner
- test the stb_clk resistor
Nothing has worked... I have no lifted pads, no faulty connections, the console was working on stock dash.
I have run out of ideas and places to look for solutions. Please help.

Thank you in advance.

PS: photos wouldn't help much I believe... but I can provide them... I have removed everything from the console. JR Programmer wires, coolrunner... it's as stock as it gets except for the firmware

 

[john mathews]

Hello,

I have tried to RGH 2.0 my xbox 360 Jasper and have hit a speed bumb. I dumped the nand 4 perfect copies, and out of lack of attention I wrote to the console the jasper.bin (which is for JTAG) instead of the ECC.

I am running: 16756
CB: 6754

From what i've noticed the J-runner doesn't have a RGH 2.0 for the firmware my console is on.

and now the problem: I can't seem to flash the original firmware back on... it gives me the following error.
Version: 01
Flash Config: 0x00000000
Can not Continue

What I have tried till now: to remove the coolrunner rev c
- desolder and resolder the connections to the JR Programmer
- clean all the connections of the coolrunner
- test the stb_clk resistor
Nothing has worked... I have no lifted pads, no faulty connections, the console was working on stock dash.
I have run out of ideas and places to look for solutions. Please help.

Thank you in advance.

PS: photos wouldn't help much I believe... but I can provide them... I have removed everything from the console. JR Programmer wires, coolrunner... it's as stock as it gets except for the firmware

wheres pics of install jr log

- - - Updated - - -

http://team-xecuter.com/forums/showthread.php?t=96474 fill this out

 

[Krafter]

Give this a try. The wrong SMC written to a NAND can cause your problem.

 

[hawkeye1103]

I'm not at home now... to try that .. but will give it a try and get back to you.... that might fix it... sounds promising

 

[hawkeye1103]

TX Product(s) used: J-R Programmer, coolrunnger rev c
Console Type: Jasper
NAND size: 16MB
Dashboard version: e.g 2.0.16756
CB version: 6754
Screenshot of NAND details from J-Runner:
(attach an image to your post)
J-Runner log:

>

J-Runner v0.3 Beta (4) Started






Checking Files
Finished Checking Files
Version: 01
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 6754
Jasper 16MB
Reading Nand to E:\kituri\Xbox 360 RGH\J-Runner v03 (1) Core Pack\J-Runner\output\nanddump1.bin
Reading Nand
Done!
in 3:30 min:sec


Reading Nand to E:\kituri\Xbox 360 RGH\J-Runner v03 (1) Core Pack\J-Runner\output\nanddump2.bin
Initializing nanddump1.bin..
Jasper 16MB
Jtag Selected
Nand Initialization Finished
Reading Nand
Done!
in 3:30 min:sec


Reading Nand to E:\kituri\Xbox 360 RGH\J-Runner v03 (1) Core Pack\J-Runner\output\nanddump3.bin
Comparing...
Nands are the same
Reading Nand
Done!
in 3:30 min:sec


Reading Nand to E:\kituri\Xbox 360 RGH\J-Runner v03 (1) Core Pack\J-Runner\output\nanddump4.bin
Comparing...
Nands are the same
Reading Nand
Done!
in 3:30 min:sec


Comparing...
Nands are the same
XeLL file created Successfully jasper.bin
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 00
Wrong Version.
Version: 01
Flash Config: 0x00023010
Writing Nand
jasper.bin
Done!
in 0:17 min:sec


Retail Selected
Programming Coolrunner
E:\kituri\Xbox 360 RGH\J-Runner v03 (1) Core Pack\J-Runner\common\xsvf\jasper.xsvf
USB XSVF Player Initialized
Xilinx Device ..... [NOT DETECTED]
Programming Coolrunner
E:\kituri\Xbox 360 RGH\J-Runner v03 (1) Core Pack\J-Runner\common\xsvf\jasper.xsvf
USB XSVF Player Initialized
Xilinx Device ..... [NOT DETECTED]
Programming Coolrunner
E:\kituri\Xbox 360 RGH\J-Runner v03 (1) Core Pack\J-Runner\common\xsvf\jasper.xsvf
USB XSVF Player Initialized
Xilinx XC2C64A-VQ44 ......... [DETECTED]
Erase Succeeded
File: E:\kituri\Xbox 360 RGH\J-Runner v03 (1) Core Pack\J-Runner\common\xsvf\jasper.xsvf
Sending Out Packets .........
Success
XeLL file created Successfully jasper.bin
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Device Not Found.
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Device Not Found.
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 00
Wrong Version.
Version: 01
Flash Config: 0x00000000
Can not Continue
Version: 01
Flash Config: 0x00000000
Can not Continue

Image of Coolrunner:
Images of close-up soldering to motherboard:
(attach images to your post)

Description of problem:cannot write nand

Was the console working before you started: Y

Do you get a green debug light appear on the RGH chip every 4-5 seconds: N

as you requested ...

PS: it didn't work with the short of the pins... i am still giving it a try .... i've seen that some got it working after an hour

 

[N.E.Modz]

Your soldering looks ok so dont think thats the problem, you have got power to the board but not switched on ? Is JRProgrammer recognised in Jrunner ? Load your original nand dump into source and click write nand and tell me what happens

 

[hawkeye1103]

I have power.... i will check also the voltages on all the pins of the jr programmer with the power source pluged and the jr programmer also plugged. The jr programmer is recognized, i do not have any driver errors in device manager. Tried writing the original nand... what i got was the error i described in the original post.

Voltages:
Orange = 0
Red = 3.5
Yellow = 0
Blue = 3.5
Green = 3.5
Brown = 3.5
Black = 0.03

 

[N.E.Modz]

I have power.... i will check also the voltages on all the pins of the jr programmer with the power source pluged and the jr programmer also plugged. The jr programmer is recognized, i do not have any driver errors in device manager. Tried writing the original nand... what i got was the error i described in the original post.

Voltages:
Orange = 0
Red = 3.5
Yellow = 0
Blue = 3.5
Green = 3.5
Brown = 3.5
Black = 0.03

99% of the time is a poor connection on nand wires (happened to me loads of times) I would reinstall the nand wires just to elimate that

P.S was also gonna say shorting the pins sometimes works, but youve already tried that

 

[hawkeye1103]

I've connected the nand wires 2 dozen times it's not the connection. If it is the connection i'm gonna throw the board out the window))

 

[nofeloniesyet]

if you go to custom nand options,tick erase and whichever size nand u got,right as u plug power in hit erase,if it erases ur set to write orig back and start over.has to be timed juuuuust right,this works for me when shorting the pins dont.

 

[BrockThunderjam]

Have you checked for continuity from the trace leading to the STDBY_CLK point and the right side of the resistor? (I saw you said you checked the resistor but make sure there is continuity as wlel in case the resistor lifted) If it was damaged you wont be able to communciate with your JRP until it's repaired.

 

[hawkeye1103]

just checked it... works like a charm.

 

[BrockThunderjam]

just checked it... works like a charm.

That was the problem? Or you checked it and it's fine?

 

[hawkeye1103]

That was the problem? Or you checked it and it's fine?

I checked it and it's fine... i also checked the continuity of the jrp wires... starting from the connector on the device all the way to the back of the board (the traces) all good.

 

[Krafter]

I've connected the nand wires 2 dozen times it's not the connection. If it is the connection i'm gonna throw the board out the window))

If all else fails you could get someone to pull the NAND, flash your backup and refit the NAND. I can handle such a task if need be and your in the U.S..

 

[hawkeye1103]

If all else fails you could get someone to pull the NAND, flash your backup and refit the NAND. I can handle such a task if need be and your in the U.S..

I'm a bit far my friend Europe, Romania... I can pull the nand no worries... just tell me if you know how to flash it....does the corona method with the card reader work?

 

[Krafter]

I'm a bit far my friend Europe, Romania... I can pull the nand no worries... just tell me if you know how to flash it....does the corona method with the card reader work?

No. You'll have to get an Infectus or a Pgogskeet. You can use either of those in combo with a clip so you wouldn't have to pull the NAND if you wanted to.

 

[CHUCKEMZ]

you could try reflashing your jr programmer see if that fixes the problem. Just a thought

 

[hawkeye1103]

you could try reflashing your jr programmer see if that fixes the problem. Just a thought

Tried it didn't help... I tried a random card reader with an xd slot ... didn't manage to read or write. An olympus MAUSB-10 might work tho

Would you guys suggest a reflow of any part .... I was thinking maybe the hanna chip? Would it help with anything? or is it just the fault of the nand? Note that it didn't work with the bridging of the pins on the nand

 

[hawkeye1103]

Got myself a progskeet 1.21 ) hope it works wish me luck guys, it's coming in tomorrow