1st jtag want to make sure everything is good

[sick360mods]

i got my first jtaggable console to without even trying to get one was just ordering more 360 with dvd drive issues to fix and when i got this i powered it up and i was like what would happen if this was the old dash and bam it was. so i had a few problems in the beginning first no device was found it ddnt download the drives and i had to manually put the drivers on my going to devices and hitting update drive , click to manually so which folder to look in and that fixxed it then i got cant see flast controller which was poor solder connections so i took the motherboard out of the case and tested each point from the top and bottom of the hole had about 3-4 that werent getting connection. then it worked woooh and i got 3 read with 2 blocks one at 44 and the other at 136. used jtag tool and nand compare to compare them and they were good. now i just want to make sure that the blocks are fine and that im good to write xell. oo and do i have to put the jtag part then xell or xell then jtag part.

 

[marshamods]

well if your using jtag tool you put on the xell version for the whatever board you have. boot up get cpu key. then make freeboot image with cpu key and flash freeboot to the console.

 

[sick360mods]

i wrote xell but my 360 wouldnt power so wrote my nand back and tried again but the same thing happened i think it because of the block in 44. how do i fix that.

 

[PureVVater]

First you need to solder the Tms and Tdi points, then write xell. Also, it was probably that block because it is in the first 50 blocks. So remap that block, then continue.

 

[jhgerm7300]

also bro make sure ur using jtag tools 1.74 because for whichever reason alot of people have been having problems with version 2.01 so yea.. and i hope everything goes alright with ur jtagging process...

 

[manwithoutname]

Your console should boot as normal when you flash the original NAND back to it, if this hasn't happened then there is something wrong beyond what you can see. You don't mention what board it is, however I have noticed that HDMI consoles tends to give RROD after flashing the original NAND unless you disconnect them from the mains for few seconds and then they will boot up as normal after. On the other hands xenon's will work straight away after being flashed with the original NAND.

You say it's the old dash, but you might want to share the inside info with us such as kernel, CB & CD versions!!!

 

[sick360mods]

its a xenon and yes it boots up fine when i write the nand back. CB is 1903. when i try to use nand healer it gives my an error saying " Could not find program C:/Nandpro/Nandpro.exe please configure setting ". how do i fix this to remapp these blocks. CD is 1888. was able to get nand healer to work but it still has the blcoks. is there a way to manually do it.

 

[sick360mods]

how do u do it manually.

 

[manwithoutname]

Before you move onto the remapping, have you flashed xell and did that work for you or not?

If you want to remap xell image this what to do:

>nandpro xenon.bin: -r16 44.bin 1

This will creat a 16k 44.bin image file which contains the specific block

Then you need to write the block back at the location it meant to be which you should see next to the bad block in either degrader or 360 flash tools. I wouldn't
be surprised if this was 3FF!!!!

So next to do is write the block back

>nandpro xenon.bin: -w16 44.bin 1 3FF (this based on the assumption that the
block is @ 3FF location).

Let us know first if you have flashed xell and what did you get?

 

[sick360mods]

wrote xell but the 360 wouldnt power at all so i wrote the nand back and worked but xell wont and yess its 03ff

 

[sick360mods]

and when i do what u said it comes up not recongnized as an internal or external command

 

[sick360mods]

got it work but now im getting " could not open virtual nand device file: xenon.bin

 

[sick360mods]

C:\Users\kyle>nandpro xenon.bin: -r16 44.bin 1
NandPro v2.0b by Tiros
Using Virtual Nand Device File: xenon.bin
Starting Block:0x000001
Ending Block:0x0003FF
Reading
03FF
C:\Users\kyle>nandpro xenon.bin: -w16 44.bin 1 3FF
NandPro v2.0b by Tiros
Using Virtual Nand Device File: xenon.bin
Starting Block:0x000001
Ending Block:0x0003FF
Writing
File: 44.bin FileLen:107be00 Blocks:3ff
03FF
C:\Users\kyle>

 

[sick360mods]

now what do i do. i think i did it right

 

[manwithoutname]

Now flash the remapped xell image to your console. Either replace the file back into Jtag tool xbin's folder and then use 'write xell' or use nandpro:

>nandpro usb: -w16 xenon.bin 0 50

 

[jhgerm7300]

make sure you extracted the nandpro drivers and software to My computer and the hard drive mine is C:

 

[sick360mods]

i did with my regular nand being an idiot where can i get the xenon.bin

 

[manwithoutname]

It's in here 'C:\Program Files\Jtag Tool\Xell Bins'

 

[sick360mods]

not mine i have the xell , smc , and bin theonly one that has the xenon is the smc. do i use that one.

 

[manwithoutname]

You must have version 2.00 of Jtag tool, uninstall it and then install version 1.74. Make sure you delete the whole Jtag tool folder after the uninstall and before installing the other version.