** Official JTAG Tool Thread **

Status
Not open for further replies.
X

XmodsUK

Full Member
May 29, 2010
52
0
UK
Got Jasper 256. Dump nand 5 times, all identical (although with some bad blocks). Flash Xell an got my CPU key. When I try and create a Freeboot image I get "Could not find file bin\XB1\jasper 256.bin" This happens after first CMD window closes.

Any help?
 
S

Salvinor

Noob Account
Jun 13, 2004
5
0
possible bug with "Jasper (16 MB), CB 6712"? (after "Write Xell" XBOX is dead)

Hi coolshrimp,
excellent program you wrote.
Makes things very easy for unexperienced people new to the JTAG'ing.

However, could you please look into a possible bug I stumbled upon yesterday?

Here's what happened:
First I modded a Falcon and everything worked fine - just like in the tutorials.

After that I did a Jasper (16 MB) with CB 6712.
My soldered points were correct, reading/writing the NAND was possible.

After I wrote "Xell" and tried to boot with Eject NOTHING happened.
The XBOX just wouldn't boot up, neither with eject button, power button or guide button from controller - it just appeared dead (*which gave me the chills since this was a box of a friend of mine*)

So I triple-checked my JTAG-connections. I guessed that by using the QSB-board included with the NAND-X nothing could go wrong.
Later I even desoldered the QSB and put some own cables on to make sure the QSB board wasn'T defective ot there are any cold solder points. I even tried alternative points - nothing worked.

Reflashing the original NAND brought the box back to life.

So in the end I got the Xell-file for this XBOX version ("Jasper_6712_hack.bin") and did the writing of Xell manually using NANDPro via the command line. (nandpro usb: -w16 Jasper_6712_hack.bin 0)

Guess what - it booted Xell fine *thank goodness*

Afterwards I prepared a freeboot image with "JTAG Tool" and flashed that - also works fine.

So is there maybe a problem with the different CB-Versions (6712 and 6723 for Jasper), that JTAG Tool only is able to correctly write Xell on the latter one?

Question: Isn't there a special Xell version for every CB-Version?
Because in the JTAG Tool program folders I only found one Xell-Version for every XBOX model.
How does JTAG Tool determine what Xell.bin to use? Since there doesn't seem to be a check or query for the specific CB-version of the models.
 
Last edited:
coolshrimp

coolshrimp

1
VIP Member
Nov 25, 2009
596
33
Canada
Salvinor said:
possible bug with "Jasper (16 MB), CB 6712"? (after "Write Xell" XBOX is dead)

Hi coolshrimp,
excellent program you wrote.
Makes things very easy for unexperienced people new to the JTAG'ing.

However, could you please look into a possible bug I stumbled upon yesterday?

Here's what happened:
First I modded a Falcon and everything worked fine - just like in the tutorials.

After that I did a Jasper (16 MB) with CB 6712.
My soldered points were correct, reading/writing the NAND was possible.

After I wrote "Xell" and tried to boot with Eject NOTHING happened.
The XBOX just wouldn't boot up, neither with eject button, power button or guide button from controller - it just appeared dead (*which gave me the chills since this was a box of a friend of mine*)

So I triple-checked my JTAG-connections. I guessed that by using the QSB-board included with the NAND-X nothing could go wrong.
Later I even desoldered the QSB and put some own cables on to make sure the QSB board wasn'T defective ot there are any cold solder points. I even tried alternative points - nothing worked.

Reflashing the original NAND brought the box back to life.

So in the end I got the Xell-file for this XBOX version ("Jasper_6712_hack.bin") and did the writing of Xell manually using NANDPro via the command line. (nandpro usb: -w16 Jasper_6712_hack.bin 0)

Guess what - it booted Xell fine *thank goodness*

Afterwards I prepared a freeboot image with "JTAG Tool" and flashed that - also works fine.

So is there maybe a problem with the different CB-Versions (6712 and 6723 for Jasper), that JTAG Tool only is able to correctly write Xell on the latter one?

Question: Isn't there a special Xell version for every CB-Version?
Because in the JTAG Tool program folders I only found one Xell-Version for every XBOX model.
How does JTAG Tool determine what Xell.bin to use? Since there doesn't seem to be a check or query for the specific CB-version of the models.
Click to expand...

ok i am using the old xell that may be why i will put the new on in next update
 
M

M AzeeM K

VIP Member
Nov 20, 2009
2,096
0
Madinah-al-Munawwara, Saudi Arabia / Karachi & Isl
Hey everyone, just wanted to inform about a bug in JTAG Tool 1.74. I don't know why nobody mentioned it before. But still, here is the original quote from another user posted in another thread:
Hackerjac said:
Problem solved now

i was stuck and coulden find a reason why it shoulden work, so i just tried making a nand.bin with jtagtool 1.74 again but this time i made it as mem editing, and now xb1 games are working, so guess coolshrimp made a little error when making this great little appz
Click to expand...
Which means that if you select option XB1 compatibility, the program will make a freeboot image with Memory editing option, while if you select Memory Editing option, the program will make an image with XB1 compatibility option.

In short, XB1 compatibility=Memory editing option and Memory editing=XB1 compatibility option. Remember, this bug is confirmed to be present in JTAG Tool version 1.74 only. So, probably it will be fixed the next version. But until then, keep this in mind so you don't run into any problems with your Xbox360 and freeboot image.
 
Last edited:
N

neural

Full Member
Oct 29, 2009
52
0
leigh
hi im having a problem using this jtag tool when i go to create.bin i get an unhandled exception error

could not find file "C:\program files\tech-modz\jtag tool\temp\crl.bin

could you enlighten me to whats wrong

im using windows 7 ultimate 32bit
nand x
board is xenon
and program is running in admin mode
 
I

id241

Noob Account
Jun 11, 2010
4
0
having an issue with my Jasper 512Mb

using jtag tool

have read nand off compares ok.

flashed xell

switch on 360, nothing, light flashes in centre (NO DRIVE ATTACHED)

if i connect via hdmi i get 3 green lights (bottom 2 top left)

when i go back into jtag tool to try to remove xell i get

arm controller not supported in this version of nandpro ? (or words to that effect)

any idea?
 
M

M AzeeM K

VIP Member
Nov 20, 2009
2,096
0
Madinah-al-Munawwara, Saudi Arabia / Karachi & Isl
id241 said:
having an issue with my Jasper 512Mb

using jtag tool

have read nand off compares ok.

flashed xell

switch on 360, nothing, light flashes in centre (NO DRIVE ATTACHED)

if i connect via hdmi i get 3 green lights (bottom 2 top left)

when i go back into jtag tool to try to remove xell i get

arm controller not supported in this version of nandpro ? (or words to that effect)

any idea?
Click to expand...
Xell does not support HDMI. You should use a composite video cable. It should work.
 
M

M AzeeM K

VIP Member
Nov 20, 2009
2,096
0
Madinah-al-Munawwara, Saudi Arabia / Karachi & Isl
id241 said:
sorry i should have mentioned when connected via component, no video no lights
Click to expand...
Hey, you installed the JTAG part of the Nand-X, right? Because it's necessary to run Xell or freeboot...
 
K

korn_16_f_t_l

VIP Member
Dec 30, 2005
686
0
Muir, Michigan
www.ps2hd.com
modmonster said:
Run your NAND dump through degraded or 360 flash dump tool. That will show you your CB then you can check it.
Click to expand...
kool thanx i knew i read of a diffrent tool for it just couldnt remember for the life of me where or anything ill have to book mark this so that dont happen again once again thanx

thought i read about some program that said it will just tell you automaticly if its JTAG-able or not but either way as long as its listed in plain bold like CB XXXX im good ill ask here and in the is my console JTAGable what CB im looking for for a zeper model mobo any how :p for dash 7371 :p

i was reading in another thread for this tool that was linked from the NAND-X install and it said that this tool hasn't got anything implimented for bad blocks or something to that effect what other methods are there to dump the 360 NAND that could possibly be more efficient than this tool?
 
Last edited:
K

Kyleking

Full Member
Dec 14, 2009
42
0
BC
I'm getting an error when I try and run JTag Tool.
I am running Windows XP Pro SP 3.5
I just installed on a macbook using bootcamp. As I had MANY troubles with my 64bit Win 7 Drivers
My Nand-X Drivers work fine on my new install...
Could someone help me?

Here is the error
Jtag Tool.exe - Application Error
The Application failed to initialize properly. (0xc0000135). Click ok to terminate the application.

Thanks

-Kyle
 
Status
Not open for further replies.