GENERAL Couple of bad blocks in this Jasper nand 512 meg ?

[mowax]

Hi guys,

This is my 1st post so i hope that you can bare with me.

I have a 512 meg jasper that i have attached a couple of QSB too for reading the nand and i've also installed a cool runner as well.

Bought my self a nand-x and have read the nand a few times and i keep getting the same bad blocks all the time.

How ever this is what i've found out so far.

32768 block(s) in nand image
2 non-matching block(s) found
44
34EB

So when i run them through the "jtag" tool then i get the following:

So i've been reading and it looks like the 2 bad blocks might be in the nand since it was created in the beginning.

I then have done some more reading.

It is not possible to remove bad blocks. They are physically bad parts of the nand chip.

The image has to be modified so that it avoids the bad areas. Have a look at Coolshrimp's tutorial on remapping.

So i followed the guide on you tube "cool shrimps" and it shows him patching the two bad blocks and then clicking on "un-map" which i can do no problem, but then when i go to create "freeboot" then i get an error.

There saying that the xell is in the 1st 50 blocks and of course that's where i'm getting the nand bad blocks.

I was then going to follow the "degraded" post but that's also throwing the toys out the pram.

I get the following error when i try and open the 1st nand that i read. (Having a ball at this i am!)

But then found out the following :

Just tried it, edited the hex file to 2005 and then saved it but then read the following...

NAND wont open in Degraded? Here is how to fix that.
1) Make a copy of your NAND backup
2) Open that copy in a hex editor
3) At offset 0x0012 you will see 2004 - 2007 Microsoft Corporation
4) Change that to 2004 - 2005 Microsoft Corporation
5) Now you image will open in Degraded.

For Big Block consoles. Degraded will not open your image.

So i'm wondering if I can go back to jtag tool and fix the nand?

I tried downlaoding the nand (the good nand that comes with jtag tool) and then fixing it but the nand that it created still showed as having the same bad blocks.

I've tried nand healer as well...

 

[hodgie]

Well first thing first. You have non-matching blocks, not necc bad blocks. No go. You need to have matching dumps. I've recently learned the convience of using cmd prompt in nandpro. Instead of jtag tool, and only dumping 64mb. Look up fibers guide. It's great!
That's where I would start.
http://www.team-xecuter.com/forums/showthread.php?t=76193&highlight=tutorial+rgh

 

[mowax]

Thanks for your post, appreciated.

It's the same 2 bad blocks in both the nands that got me asking about it and then people were saying that if it's the same two all the time in both nands then there probably bad blocks within the nand at the time of writing.

So I'm very interested in when you say the 1st 64 meg as this has been discussed but no ones ever mentioned where to look or what to do to get it to read this and not the whole nand.

As you know the big jasper takes about 45 minutes per read and that's a head ache watching it crawl along.

I did try the nand-x attached direct to the board and this is the 2nd set of QSB's added to this machine.

Checked them all with a multi meeter and installed cool runner with out any problems/shorts etc. wires all in the right place.

Thanks for the heads up, i'm going to go and have a read of what you have suggested.

This jaspers got my head in bits.!

Thanks again.

 

[hodgie]

I certainly understand. I used jtag almost exclusively, I used cmd prompt a bit until I got a bb jasper. And Martin advised learning cmd instead. It does take a bit, but not bad at all. Now, I will use CNET prompt all the time. Fiber's guide is really good, especially for a noob to cmd prompt.

As far as the non-matching, that's odd. I would have to ask someone more knowledgeable about that. But everything I have read, says to have matching dumps.
As a side note, I use multi builder v.07 for image building

 

[mowax]

Yip thanks for that.

Grabbing all the files now and going to have a read and a cup of coffee and look through that guide, That's what I've been told about the nands, but hey I know nothing, the thing that was frustrating is that I was going to sell an old xenon that was already jtagged and had FSD 1.1 i think it was on it, then I decided that I'd update the dashboard to the latest dash, which all went flawlessly with the tools that are out there for that. (that's all sitting in the lounge with a couple of terrabytes of HDD's attached all working as well so then that's when i decided that "well it can't be that hard" )

I bought the other machine like that you see, it's a really old faithful xenon with a few wires attached, the really old type with a few resistors man handled into place, so yeah that one was bought with the jtag already installed and glitched which is why i then decided to have a go my self!

...and here we are......lol!

Thanks for your input, appreciated. and have a Good Christmas won't ya' I'll have a read now and report back if that be cool.

Thanks again.

 

[mafia 5k]

bad blocks especially in the first 50 are always a pain, i found nandflasher for windows 1.02 works like a charm auto remaps for you.

 

[Martin C]

Read my sticky on remapping bad blocks in the ecc area. you may find your console won't glitch without it.

 

[mowax]

Thanks Martin, I'll have a read of it, much appreciated the tip for not having to read the full whole nand, phew that's cut the time down a little.

I've just started following the link to the 1st tut and as you can see this is what I've been greeted with all the time re the bad blocks.

Thanks again.

I'm just taking my time with this so thanks for being patient.

 

[Martin C]

so open it in 360 flash dump tool. See where 40 and 44 are being remapped to and follow my guide

 

[mowax]

Yeah thanks,

I've been having a read over where your thread is and i guess that's what cuts the mustard as to speak.

I've failed at the 1st hurdle...and that's

Write the ecc file to your NAND as per normal. You'll get an error writing to one of the blocks. Don't worry about it for now.

But please don't "tut" in a bad way, It's all been a learning curve for me! and a massive one at that, I'm willing to learn by reading, and reading some more. after all I've come this far!

I did manage to remap them the other day (or what i thought I'd done but that's why I'm here i guess.....I wasn't using your guide though.

Your instructions are clear, just need to get my head around it, a little out of my league for now.....

The guide that I was following was the Jtag Tool Tutorial (Remap Bad Blocks) - Coolshrimp youtube video and all seemed to go well.

But I agree, nothing worse when a n00b comes along (like me!) and starts posting! (but then again i guess that's why you have the forum!)

Thanks I'l do some more reading on writing the ecc file to my NAND as per normal. (as for now I'm totally lost) is this actually writing to the nand of the 360? I know it says don't worry about it, but hey you can't help your self when you've come this far, just don't want to screw it up.

Thanks again for your time.

Mo

I can see that i'll have to map 171=1FE and 008=1FF i guess to fix the bad blocks...

 

[Martin C]

Take the values there and follow my guide.

The file that you create for XeLL has no ECC so it has to be rebuilt. Easiest way is to write it to a VNAND first, hence my tutorial.

EDIT: leave 171 - you only have to manually remap 8 using my guide.

 

[mowax]

Hi Martin,

Thanks for all your input so far.

OK I tried to get my head around the nand repair to be honest so I'll hold my hands up in the air.

So a friend said he'd have a go at repairing it which he did and sent me it back.

(I have a feeling this jasper may be knackered, after all it did get heat gunned to death so thinking that might be the cause of the bad blocks on the nand? all though it did boot originally.)

Used the following command to write the nand.

nandpro usb: -w64 orig.bin

And I get 2 bad blocks when it's writing.

I know that i have a bad block in the 1st 50 which is block 0008 x 1FF and I can see that you can ignore blocks above this size so just work on that bad block.

I have tried remapping them in "jtag" tool where you add the nand (the broken one with bad blocks) and then go to "un-map" but then the tut goes on to say insert your CPU key which of course I don't have.

Tried writing the Original nand back to the box but it just has the same two bad blocks. and console won't boot etc..

Thanks

 

[Martin C]

(I have a feeling this jasper may be knackered, after all it did get heat gunned to death so thinking that might be the cause of the bad blocks on the nand? all though it did boot originally.)

Reason enough for me to close this thread to prevent anyone else here wasting time on it.

Don't start any other threads on this.