JTAG Problem

[Infinite4]

Hello. Today I received my nand-x that I ordered a few days ago. It was already installed onto my motherboard from the person I bought the jtag from. All I need to do is put the cables onto the pin headers and etc.
Here's the problem I have no idea what to do after the cable is connected from my motherboard to my nand x and, and my nand x is connected to the USB plugged into my pc.
I think all the wires are connected right, the nand x lights up. I think thats good.

I have the nand x drivers downloaded, in a folder called nandpro_20d_drivers, I downloaded that off this site.
Here's the problem. When I open it up and go to NandPro.exe, cmd opens and closes within a second. There are words in cmd, but it closes to fast to be able to read them. I don't think NandPro recognizes my nand x?

I know that the cables are connected right because when I go to JTAG Tool and click "read nand", the cmd comes up and reads the nand and then I save it to my desktop. So that works.

I am sorry but I don't know a lot about this stuff. But please help me fix my jtag.

 

[BGAMods]

Re: NAND-X Problem

when you plug the nand-x into your usb does it install or ask you to install the drivers?

the command window for nandpro doesnt open by clicking the exe. just use jtag tool as that auto uses nandpro anyway. if jtag tool is dumping your nand then youre good. check the nand dumps in degraded for bad blocks then compare the dumps with nand compare. have a look in the nand-x section at the sticky tutorials.

 

[Infinite4]

Re: NAND-X Problem

Okay. This will probable be by far the dumbest question you ever heard.
How do I unbrick my jtag? Thats what I am doing all this for. It was bricked by flashing wrong nand and now only xell comes up.
How do I fix this? I have a nand x as you know and a jtag.

 

[BGAMods]

Re: NAND-X Problem

do you have your original nand dump? if so then write your original nand back and itll boot as normal.

so you wrote the wrong nand to the console?
if you did that and dont have a backup of your original nand dump from that console then you might be screwed. how have you wrote the wrong nand if youve got xell booting fine?

 

[Infinite4]

Re: NAND-X Problem

Okay xell boots up but gives errors. I have a very close iBuild nand that is basically my original nand, it works perfect.

Please explain how I write my original nand back. Explain in your own words. Like what do I do?

Please help me. Explain in not too advance words lol.

And I think I actually flashed my banned kv to my console, something like that and its now bricked. Useless. This is why I bought nand x.

 

[BGAMods]

Re: NAND-X Problem

as long as the nand dump you have is your original untouched dump then you can write it back easy.

go to jtag tool and click remove xell, itll ask you for your .bin file so just select your original nand dump and itll write it back for you.

ONLY DO THIS IF ITS YOUR ORIGINAL UNTOUCHED NAND.

seems like youve made a mess of this mate, how did you manage to write the wrong nand?

 

[Infinite4]

Re: NAND-X Problem

Thank You.

My friend was trying to help me go from freeboot v.0.032 to 0.03 but I screwed up somewhere and it resulted as my jtag being bricked.

I have nands made in iBuild. So, It's not techically 100% my original nand but It still works perfectly on my jtag. Can i still write it to my jtag?

 

[BGAMods]

Re: NAND-X Problem

id wait for a 2nd opinion on what to do in your situation before you make it worse, ive told you what id do but if you wait then one of the jtag experts will come on and hopefully confirm what ive said or give you some other alternatives.

how do you know the nand dump is good? have you ever wrote it to the 360 to see if it works? i really dont see how you managed to brick it cause jtag is so easy and its just a case of using cmd.

open your ibuild dump in xnand healer or 360 flash tool and see if it loads. do you have your cpu key?

 

[Infinite4]

Re: NAND-X Problem

I had my Falcon jtag for a month or 2 and I was using that freeboot image that was made in iBuild. It has to work! lol. I was just using it 2 weeks ago =]
Your acting like you never heard of jtags being bricked. Its actually easy to do. Flashing bad kv can result in a brick or christmas lights.

And I will wait for an export modder to come here

 

[BGAMods]

Re: NAND-X Problem

im just saying that when i dump consoles to jtag i dump the nand at least 5 times and then create 3 copies of these 5 dumps and rar them up and move to a safe place.

as for bricking, jtag is so easy that i find it hard to believe people can brick doing it. i know it happens but it shouldnt if you follow the guides exactly and ensure all dumps have 0 bad blocks or remap if they do and that all dumps match.

it is easy to do if you dont do it properly, its like saying its easy to brick a 360 when flashing a drive. well yes it is if i liteon erase my liteon without dumping the key.

 

[M AzeeM K]

Re: NAND-X Problem

1. I don't really understand what's wrong here. You have a freeboot image which you say is working fine. So, what's the problem in using it?

2. If you build the freeboot image using iBuild, then I am sure that you would have copied and extracted your Original NAND in the process of building the freeboot image and that the Original NAND will still be present in the freeboot folder. So, you can get it from there, if its still present there, that is.

Alternatively, if you want your Original NAND back, you can reconstruct it. Just get a NAND image with the correct CB, CD, CE, CF and CG as your Original NAND. Extract the Raw KV and RAW Config files out of your working freeboot image and inject it into the NAND image you got before. Now you will have your Original NAND image back.

3. And I must mention this here, for a person who used iBuild to make his freeboot image, you are pretty careless and dumb because of the fact that you lost your Original NAND dump.

 

[BGAMods]

Re: NAND-X Problem

thanks MaK. like i said one of the jtag experts will be along soon. ill leave this in your hands MaK.

 

[M AzeeM K]

Re: NAND-X Problem

thanks MaK. like i said one of the jtag experts will be along soon. ill leave this in your hands MaK.

Seems like quite some work if you just leave it to me . I think it will be better if you stayed around

 

[BGAMods]

Re: NAND-X Problem

lol no probs ill keep my eye on it.

 

[M AzeeM K]

Re: NAND-X Problem

lol no probs ill keep my eye on it.

Great. I feel better already . Plus, looking at the title of this thread is really making me laugh ==> NAND-X Problem <== Can't see any problem mentioned here regarding the Nand-X

 

[BGAMods]

Re: NAND-X Problem

im changing the thread name now.

 

[M AzeeM K]

Re: NAND-X Problem

im changing the thread name now.

This is much better. Thanks

 

[Infinite4]

Re: NAND-X Problem

1. I don't really understand what's wrong here. You have a freeboot image which you say is working fine. So, what's the problem in using it?

2. If you build the freeboot image using iBuild, then I am sure that you would have copied and extracted your Original NAND in the process of building the freeboot image and that the Original NAND will still be present in the freeboot folder. So, you can get it from there, if its still present there, that is.

Alternatively, if you want your Original NAND back, you can reconstruct it. Just get a NAND image with the correct CB, CD, CE, CF and CG as your Original NAND. Extract the Raw KV and RAW Config files out of your working freeboot image and inject it into the NAND image you got before. Now you will have your Original NAND image back.

3. And I must mention this here, for a person who used iBuild to make his freeboot image, you are pretty careless and dumb because of the fact that you lost your Original NAND dump.

Thanks.
I had two main questions. Why isn't my nand x always being recognized in cmd. And how do I write my nand back to my jtag.
And I did not lose my original nand, the guy who sold the jtag to me did.
You guys should have known that I did not jtag it myself from the looks of this noob question I asked.

So Yeah. The seller lost my original nand. And did the next best thing to do with making a new image using iBuild. I have my CPU key and really everything. It works fine. Thanks guys..

 

[M AzeeM K]

Re: NAND-X Problem

Thanks.
I had two main questions. Why isn't my nand x always being recognized in cmd. And how do I write my nand back to my jtag.
And I did not lose my original nand, the guy who sold the jtag to me did.
You guys should have known that I did not jtag it myself from the looks of this noob question I asked.

So Yeah. The seller lost my original nand. And did the next best thing to do with making a new image using iBuild. I have my CPU key and really everything. It works fine. Thanks guys..

Glad to hear everything works fine. Like I mentioned above, you can still get your Original NAND back, but believe me, there isn't really a need for it. Just keep a backup of your working freeboot image at a safe place, so that you can use it in the future because the freeboot image necessarily works as an Original NAND image.

 

[BGAMods]

so youve fixed the problem?

you didnt explain that the guy who sold it to you lost the nand dumps so i apologise for my assumption.

the nand-x will alwys be detected in nandpro. to get to nandpro manually you have to get to nandpro in cmd prompt. once youre there then if you manually try to read itll detect the nand-x.

if you try to load the cmd.exe in the nandpro folder it wont load.

EDIT:

also could you explain what you did to get it working as it may help others in the future.

thanks

flash