ANSWERED Jasper 512 bad blocks

[steven007]

Hi again

doing a jasper 512mb today with jtagtool 1.74 but getting lots of bad blocks, 8 in a row at 960-967

then again around 7aaa looks like every block after that is showing "error 0 reading block 7aaa" same error for every block after that right up till end 7fff.have read the nand twice and errors are same locations both times.
not sure if i need to reading the full nand or not

any advice

thanks

 

[manwithoutname]

Check your soldering I'd say. A picture of your handy work would help tell us too ..

 

[steven007]

Ok since i got my Zephyr all sorted here with the help of other...i thought i would get back to looking at this one

I have redone all my solder work even though i tested it previously..i am 100% confident my soldering skills are up to the job so am sure i can eliminate soldering issues.

I formatted the internal MU and made sure the console is on 7371 then i used jtag tool 1.74 to read the full 512mb 3 times and get the same bad block locations each time 960 to 967, 2960,3fe0 to 3fe7, 4300 to 4307 and 5fe0

I have used jtag tool 1.74 to install Xell and retreived my CPU key

What i want to know is the easiest method to create the freeboot

i have read somewere(cant find the link now)that you only need to dump the first 66mb from the 512 nand or should i continue with the full nand dump i have taken from the nand

i am comfortable with the comand line nandpro but i just wanna be sure i am going about it the best way in order to limit any problems

thanks again guys

steven

 

[marshamods]

well if you got 3 dumps and had a bad block at the same spot on all of them your going to have to remap that bad block before going on flashing a rebooter.

 

[M AzeeM K]

Ok since i got my Zephyr all sorted here with the help of other...i thought i would get back to looking at this one

I have redone all my solder work even though i tested it previously..i am 100% confident my soldering skills are up to the job so am sure i can eliminate soldering issues.

I formatted the internal MU and made sure the console is on 7371 then i used jtag tool 1.74 to read the full 512mb 3 times and get the same bad block locations each time 960 to 967, 2960,3fe0 to 3fe7, 4300 to 4307 and 5fe0

I have used jtag tool 1.74 to install Xell and retreived my CPU key

What i want to know is the easiest method to create the freeboot

i have read somewere(cant find the link now)that you only need to dump the first 66mb from the 512 nand or should i continue with the full nand dump i have taken from the nand

i am comfortable with the comand line nandpro but i just wanna be sure i am going about it the best way in order to limit any problems

thanks again guys

steven

The first 66MB should be enough, even only the first 16MB will work fine.

You don't need to touch the rest of the NAND which is used as an MU i.e. after the first 66MB of the NAND.

You can create a freeboot with only the first 16MB of data from the NAND. Just read out the first 16MB of the NAND, then use it to create a JasperBB freeboot image manually using the freeboot 0.032 and 9199 file through CMD. You will have yourself a 16MB freeboot image. Just write this 16MB freeboot image to your NAND and your Xbox360 will be good to go.

 

[steven007]

OK so i got it going with freeboot but it wasn't straight forward

here is my method incase it helps anyone

i tried nandpro cmd,jtag tool and the iHc jtag package all failed as did the 16mb dump of my nand.

So i used freeboot toolbox along with the original 512mb nand dump and it created a 66mb bin file so i wrote this to nand and it works

so thanks again for all advice

 

[M AzeeM K]

OK so i got it going with freeboot but it wasn't straight forward

here is my method incase it helps anyone

i tried nandpro cmd,jtag tool and the iHc jtag package all failed as did the 16mb dump of my nand.

So i used freeboot toolbox along with the original 512mb nand dump and it created a 66mb bin file so i wrote this to nand and it works

so thanks again for all advice

Glad you got it working. The funny thing is, Freeboot Toolbox has never worked for me, but seems like it actually does work, atleast it did in your case

 

[steven007]

Just one more question... do ineed to worry about the MU memory corruption,ir is this taken care of in the freeboot .32 install i did.