RGH Strange issue never seen before. Please help!

[crazed-cracker]

So this is my 13th RGH console I am doing for a customer (Its a 16mb Jasper). I read the nand 5 times to be very safe. They are ALL matching. I then created the .ecc and wrote it. I programmed the coolrunner and installed it. I boot into xell and get my CPU key (Im 100% sure its correct). I go back to get my kv info and create the GGBuild image but it says error. Its telling me the CPU key doesnt match the nand???? Can someone please help me? I have never seen this before and need to know whats wrong.

 

[klepoh]

get cpukey via xell http
i always do that....

 

[crazed-cracker]

get cpukey via xell http
i always do that....

That is what I did so i know its correct

 

[Mickey3177]

You may have a bad KV, if you want help you need to post everything at this point, clear closeup pictures of all solder points, have you ran your nand with 360 flash dump tool and you are sure that the dump is correct. Have you flashed back the original nand and does it boot....I can go for hours with questions, it's up to you

 

[Martin C]

So this is my 13th RGH console I am doing for a customer (Its a 16mb Jasper). I read the nand 5 times to be very safe. They are ALL matching. I then created the .ecc and wrote it. I programmed the coolrunner and installed it. I boot into xell and get my CPU key (Im 100% sure its correct). I go back to get my kv info and create the GGBuild image but it says error. Its telling me the CPU key doesnt match the nand???? Can someone please help me? I have never seen this before and need to know whats wrong.

Flash back the original NAND. Does it boot?

 

[crazed-cracker]

Yes I have flashed back the original nand and it boots just fine. I ran it in 360 flash tool to see if there were any bad blocks and there are none.

 

[TimboZero]

Best guess (and tbh that is all it is and nothing more) , did your customer try using a donor KV to try and exploit XBLive ? If so and if it wasnt done correctly , this could cause problems for you. I would suggest that you 'demand' the original stock nand backup to use as the source for his new exploit flash.

 

[crazed-cracker]

Okay I will ask him if he has. This is the weirdest thing I have seen

 

[Martin C]

Yes I have flashed back the original nand and it boots just fine. I ran it in 360 flash tool to see if there were any bad blocks and there are none.

So take the original NAND and run it through 360 Flash Dump Tool. Put the CPU key from XeLL into Settings and it will show you the decrypted KV.

 

[crazed-cracker]

I cant open 360 flash tool it keeps crashing. I have tried with jtag tool and it still doesnt work are there any other suggestions?

 

[gerardo15]

I had exactly the same problem!!

Solution:

I figured out that my console was not a 16mb Jasper. it was an 256 mb, i had the cpu key and said error.
So i had to flash the 16 mb that i dumped back. and then re-read the nand but this time as 256mb! this time it would recognize the cpu key perfectly..

It was wierd because if all memory devices were unpluged in the xbox it will not show any memory, but if i had the hdd plugged it will show the 220 internal memory

give it a shot and let me know!

---------- Post added at 14:27 ---------- Previous post was at 14:25 ----------

I cant open 360 flash tool it keeps crashing. I have tried with jtag tool and it still doesnt work are there any other suggestions?

My 360 flash kept crashing too!! thats your solution its not an 16 MB!

 

[crazed-cracker]

I will give it a go but when i put it into 360 flash tool it said 16mb. Maybe that is just because i read it as that

 

[Martin C]

360 Flash Dump Tool will just look at the size, that's all.

What does your flashconfig say?

 

[TilVl]

When I read mine as 16 and it was a 512 flash tool wouldn't open the dump either. Just crashed.

Sent from my SGH-T839 using Tapatalk

 

[shawndezy115]

best way to find out is tell it to try and read a 256 or 512 if it reads a 256 try 512. eventual it will fail out not being able to continue reading if its a 16mb nand. or a 256.

 

[diaboliq20]

or a quicker way is to boot the console with original NAND and look at the memory size - no memory = 16MB NAND - so any memory at all would suggest a larger NAND - just look at the size available

 

[shawndezy115]

diabolq20 - please read previous posts. he said there was no internal memory. others like myself have found a bb jasper sometimes does not display the proper memory size if at all. i have had 2 jasper's not show any mem unless another storage device was connected. we are trying to find out if this is one of those cases.

 

[diaboliq20]

diabolq20 - please read previous posts. he said there was no internal memory. others like myself have found a bb jasper sometimes does not display the proper memory size if at all. i have had 2 jasper's not show any mem unless another storage device was connected. we are trying to find out if this is one of those cases.

I just re-read all the posts - where does it say that? I maybe missed it though lol - could you point it out?

EDIT: nope - tried again, and I still don't see where the OP tells us there is no internal memory.....hmmmmm

 

[Martin C]

best way to find out is tell it to try and read a 256 or 512 if it reads a 256 try 512. eventual it will fail out not being able to continue reading if its a 16mb nand. or a 256.

Not true unfortunately.

You can read with -r256 on a 16MB console and it will happily look to be reading past 03FF.

 

[blastagator]

Diaboliq: "It was wierd because if all memory devices were unpluged in the xbox it will not show any memory, but if i had the hdd plugged it will show the 220 internal memory" - was what he was referring to.

The only sure fire way to know what size a Jasper is is to look at the FlashConfig. So look at FlashConfig!

This sounds like another case of a sneaky BB Jasper to me as well.