Martin C
VIP Member
problems with nand-x
- Thread starter mickeyvilla
- Start date
i took it out it still erors e79 with it in.
so where did i go wrong when i told jtagtool to write xell,reading about thats what i thought was my next step to boot box with xell to get cpu key.
so where did i go wrong when i told jtagtool to write xell,reading about thats what i thought was my next step to boot box with xell to get cpu key.
Martin C
VIP Member
Yes, you'll get E79 if they're not there. You need the cable connected between the two QSBS! Put them back in, set the switch on the J2D2 to 330 and try again.
You should have selected Xenon when flashing Xellous, did you?
You should have selected Xenon when flashing Xellous, did you?
yes i selected my mb type xenon & had the cross over wire connected & i told it to write xell not xellous.
the jtag was in the off position when i told it to write xell,could it because of that ?
the jtag was in the off position when i told it to write xell,could it because of that ?
Martin C
VIP Member
Cool. Now don't mess with ANY of the JTAG QSB wires and settings from this point on, even if you have issues with the freeboot.
how did u know i'd have issues with freeboot
i've created a freeboot nand but when i check it with 360 flashdump tool in key vault its says they are all bad keys.
so should i start from begining now untill i've created a freeboot nand with good keys ?
i've created a freeboot nand but when i check it with 360 flashdump tool in key vault its says they are all bad keys.
so should i start from begining now untill i've created a freeboot nand with good keys ?
Martin C
VIP Member
So you put your CPU key into 360 Flash Dump tool?
I don't reckon you did.
What tool did you use to build the freeboot image?
I don't reckon you did.
What tool did you use to build the freeboot image?
Martin C
VIP Member
cant get nand-x to write freeboot nand
each time try to write i get an error
"looking for usb interface device,can not continue"
i dont understand why i run jtagtool in admin.
why aint my comp finding the nand-x it shows up in device manager as working ok.
each time try to write i get an error
"looking for usb interface device,can not continue"
i dont understand why i run jtagtool in admin.
why aint my comp finding the nand-x it shows up in device manager as working ok.
could my wirering to nand=x be the reason why i cant get cmd to reckonise the device.
because as i've been searching for answers & not wanting to keep asking noobie questions i came across a tut thats shows the plugin to nand-x where as i have mine plugged in different as you'll see by pics.
but i still cant understand how i was able to read nand twice but now i cant.
because as i've been searching for answers & not wanting to keep asking noobie questions i came across a tut thats shows the plugin to nand-x where as i have mine plugged in different as you'll see by pics.
but i still cant understand how i was able to read nand twice but now i cant.
Last edited:
tried that ball00 kept getting loads of errors dont know if it was trying to read usb stick.
if i boot up with jtag swiched off i get hardware error e79
if i boot up with jtag swiched off i get hardware error e79
Martin C
VIP Member
image #2 is for programming the NAND-x with a CK3, nothing to do with connecting it to the console.
Can you still boot to Xellous? Did you flash Xellous or Xell, as it should be Xellous.