***** How to do the JTAG Hack/Dump NAND/Xell Tutorial *****

I you followed the tutorial correctly then you should have made a folder named nandpro on the root of your harddrive on your PC. That's where your dumps will be.

 

That's not entirely true though.
When I open my Command Prompt, it's automatically working in the c:\Documents and Settings directory.
You have to change to the directory in command prompt. My nand bins were stored in Document and Settings folder, not the NandPro folder, but I realize why it did this and worked through it myself.

There is a lot of room for errors in doing this. My dern LPT port was disabled in BIOS... o completely forgot I disabled it when I built the gaming pc because there was no need for it. I spent the entire day double checking and triple checking wiring that I knew was right but was trying to prove it was the soldering. I've done more PS2 modchip installs than I care to remember..this JTAG install is simple compared to those.

The main thing is, people have to learn to read and follow instructions and use a little common sense BEFORE you go posting and asking questions that have been answered several times over. Rest assured, if I ask a question then the answer is very well hidden or not answered...... I hate asking questions about stuff I should already know.

 

Budreaux you were right they are in docs & settings not in the nandpro folder, i looked every where except there!!

 

Can i use a "USB to PRINTER IEEE 1284 Parallel Port Cable Adapter" to connect the printer cable or I need a PCI card?

 

You're gonna need an onboard LPT port.

 

You mean i need to have it on motherboard already or you mean ill need the pci card?

 

This is a Great Post .

I'm trying to get a DVD key from a 360 I got without a DVD PCB in it.
I have the LPT connector all wired up and using nandpro and I'm dumping the bin but how long does this take to get the info? I'm using an old laptop so I'm not sure if thats why its going so slow.
Ok I think it stopped at like 16.5mb now do i flash hacked bin on it to get cpu key ?
Then I flash my nandbin1 from previous back on to it?

Quick note the dashboard is 7363

 

can i use this item to connect the printer cable to my pc?

 

It should work just make sure you have a free PCI express slot or just get a regular PCI one

 

yeah I have 2 free right now and i only have one regular one and is taken for a sata card . thx a lot for the help

 

Can anyone help possibly ? I was able to get my nand and compared the 2 and they are identical but when trying to write the hacked on to the 360 it says it cant read it.

Is it because I only have the LPT connector wired? I didn't do the JTAG as it stated somewhere you didn't need to do this if just doing the Nand ... Is the LPT just to dump the Nand and JTAG writes it ?

Thanks for any help,

Joe

 

In your cmd prompt, I'll bet it says c:\documents and Settings\
If you are using Nandpro20c, go to your cmd prompt annd type cd\nandpro20c
This will put you in your nandpro20c folder directory,w hich is where I'm sure you placed the hacked nand file.
Once you are there, everything should read and write fine for you.

 

I did that but not sure if I'm trying to write the correct file to the nand to get a reboot. I have 2 identical bin reads also I have a Falcon board -- Do I need the JTAG part wired up or will just the LPT connection work?

 

Type out exactly what you are tying in your cmd prompt please.

 

Joe[/quote]

I did that but not sure if I'm trying to write the correct file to the nand to get a reboot. I have 2 identical bin reads also I have a Falcon board -- Do I need the JTAG part wired up or will just the LPT connection work?[/quote]
You need the the three jumpers installed for it to work once you've completed the writing process. Not having the three jumpers in place is not your current problem, but you will need to do them before oyu go any further after the writing process.
For now we just gotta get you all set for writing the hacked files to the box.

As I asked prior, please post here exactly what you are typing in your cmg prompt box.

 

I made a folder named nandpro20b and then all the files were in that.. so at command prompt i typed Nandpro20b\nandpro.exe lpt: -w16 nameofhackedbin.bin ( I'm trying to use the falcon_opus_hack.rar )

It basically said it couldn't read the bin file I was trying to write to the nand... Do I need to extract that somehow to the folder as a Bin and not .rar ?

 

The easiest way to fix this then would to be just place the falcon_opus_hack.bin file in the same location as the nand1.bin and nand2.bin files.
Make sure you unrared the that file so that you have a .bin file.

Other way is to type cd\Nandpro20b [ENTER]
Then type your nandpro lpt: -w16 nameoffile.bin

Then as long as the bin file you are trying to write is in your Nandpro20b root folder, everything should work fine.
My gut feeling is you are actually working from your Document and Settings folder while in your cmd prompt window.

 

definately working from a command prompt c:\ but I may be wrong.. the other thing is they may be .rar files not bin.
Arent the files you dump created as .bin files ? I must have winrar on the laptop because the files are showing up as little book type icons.

I'll check this and get back to you later tonight I have to run out

 

ok this is what I get --------->
C:\nandpro20b>
C:\nandpro20b>nandpro.exe lpt: -w16 falcon_hack_updxell
NandPro v2.0 by Tiros

Testing LPT device address:0378
Using LPT device at address:0378
FlashConfig:01198010
Starting Block:0x000000
Ending Block:0x0003FF
Press any key to begin writing nand
Couldn't open falcon_hack_updxell for read

I even tried to write my Nand2 & Nand3 but I get the same thing couldn't open for read ! Any Ideas anyone ? Does .bin nead to be on the end ?

 

Ok I added the .bin extension and was able to write the file Duh !!!
I tried rebooting the console and got a E79 error which doesnt make sense as its a hard drive issue ?
I tried hold in the eject but that didnt work either.

Any ideas what I should try next ?

Thanks for the help .
Bedtime soon !