FIXED Jasper 16MB Wont Boot Xell

[Martin C]

Is it possible you can't get it to boot stock is because it's the wrong NAND?

 

[slighty]

there is no way its the wrong nand i definitly made sure i backed it up straight away
i will try this tonight
http://team-xecuter.com/forums/showthread.php?t=92607

 

[Martin C]

The fact you can't get your stock NAND to boot tells me you probably wrote over the original with one with an ECC written to it.

Load the nanddump1.bin into J-Runner and tell me if it reports 'header is wrong'.

 

[chase]

The fact you can't get your stock NAND to boot tells me you probably wrote over the original with one with an ECC written to it.

Load the nanddump1.bin into J-Runner and tell me if it reports 'header is wrong'.

a nand with ECC written to it should still give him correct cpu key even though it will not boot stock .. right ?

am I correct in saying the cpu key he is getting is correct and the only reason he is getting wrong cpu key is because the nand is not the right one for the console or is modified?

can't he just write jasper_hack_aud_clamp.bin without using any nanddump as source to see if the cpu key is the same (which I think will be) and then he can build an image using donor files and key ?

 

[Martin C]

a nand with ECC written to it should still give him correct cpu key even though it will not boot stock .. right ?

am I correct in saying the cpu key he is getting is correct and the only reason he is getting wrong cpu key is because the nand is not the right one for the console or is modified?

can't he just write jasper_hack_aud_clamp.bin without using any nanddump as source to see if the cpu key is the same (which I think will be) and then he can build an image using donor files and key ?

If he's getting the CPU key from IP then it's 100% correct. J-Runner states 'wrong CPU key' as it tries to decrypt the NAND's keyvault with this. So if you write a vanilla xell to the console without your keyvault, this will happen. It would also explain why nothing happens when you try to boot it (since the console is in a boot loop with xell). Yes, a donor NAND would sort him out of course, but it's better to understand the root cause first.

 

[slighty]

i found out what the issue is guys and i am so sorry my working folder was set to another folder somehow i think its cause i moved jrunner to a folder called xbox but the working folder was still copying to old folder and i have used a different nand from a previous trinity feel like a real douche i am so sorry guys and appreciate all ya help am getting a donor nand and ganna try that. does this mean i cant go retail???

thanks

 

[Martin C]

J-Runner wouldn't overwrite unless you told it to. So unless you kept a copy of your NAND somewhere, then yes - no retail for you.

 

[slighty]

yea well i think i really stuffed it up buy over writing it because the copy i thort i had was not the actual nand so bummed trying to work out how to jtag this console with donor nand now

 

[Martin C]

There's a guide in the JR PDF as well as my sticky to help you on this.

 

[slighty]

i have been trying to do this but not having any luck at all i am real sorry i made such an error i have the cpu key and dvd key. what area is your sticky in so can follow it sorry but cant see it thats all

 

[chase]

you need to know what dash you were on and the LDV b4 you killed it

then you need a donor nand and and cpu key ..

look in the JR pdf on how to use the donor nand and cpu key to build an image .. not that complicated if you follow the guide

 

[Martin C]

You don't need to know dash or LDV. Neither is important since retail can't be used anyway. He'll be building a JTAG image, so all he needs is donor files.

 

[chase]

You don't need to know dash or LDV. Neither is important since retail can't be used anyway. He'll be building a JTAG image, so all he needs is donor files.

my bad ..forgot he couldn't use retail anymore

 

[slighty]

thanks martin i trying this now buy using your sticky i see how i go thanks for putting up with my dumbass move

 

[slighty]

Im a bit lost sorry to sound really stupid but i following this sticky and extract files but there is no kv_dec.bin

 

[chase]

you rename kv_en.bin to kv.bin

 

[slighty]

im really having no joy this is what i am getting in the j runner log

Failed
Wrong CpuKey
Load Files Initiliazation Finished
16537
Started Creation of the 16537 xebuild image
---------------------------------------------------------------
     xeBuild v1.09.639
---------------------------------------------------------------
base path changed to C:\Users\Administrator\Desktop\xbox\J-Runner v02 Beta (288) Core Pack\xeBuild
---- { Image Build Mode } ----
building jtag image


***** WARNING: nanddump.bin has a mixed controller LBA at block 0x2 (raw offset 0x8400), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x3 (raw offset 0xc600), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x4 (raw offset 0x10800), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x5 (raw offset 0x14a00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x6 (raw offset 0x18c00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x7 (raw offset 0x1ce00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x8 (raw offset 0x21000), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x9 (raw offset 0x25200), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0xa (raw offset 0x29400), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0xb (raw offset 0x2d600), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!s likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0xf (raw offset 0x3de00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x10 (raw offset 0x42000), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x11 (raw offset 0x46200), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x12 (raw offset 0x4a400), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x13 (raw offset 0x4e600), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x14 (raw offset 0x52800), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x15 (raw offset 0x56a00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x16 (raw offset 0x5ac00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x17 (raw offset 0x5ee00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x18 (raw offset 0x63000), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x19 (raw offset 0x67200), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x1a (raw offset 0x6b400), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x1b (raw offset 0x6f600), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x1c (raw offset 0x73800), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x1d (raw offset 0x77a00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x1e (raw offset 0x7bc00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x1f (raw offset 0x7fe00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x20 (raw offset 0x84000), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x21 (raw offset 0x88200), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x22 (raw offset 0x8c400), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x23 (raw offset 0x90600), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x24 (raw offset 0x94800), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x25 (raw offset 0x98a00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x26 (raw offset 0x9cc00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x27 (raw offset 0xa0e00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x28 (raw offset 0xa5000), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x29 (raw offset 0xa9200), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x2a (raw offset 0xad400), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x2b (raw offset 0xb1600), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x2c (raw offset 0xb5800), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x2d (raw offset 0xb9a00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x2e (raw offset 0xbdc00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x2f (raw offset 0xc1e00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x30 (raw offset 0xc6000), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x31 (raw offset 0xca200), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x32 (raw offset 0xce400), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x33 (raw offset 0xd2600), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x34 (raw offset 0xd6800), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x35 (raw offset 0xdaa00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x36 (raw offset 0xdec00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x37 (raw offset 0xe2e00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x38 (raw offset 0xe7000), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x39 (raw offset 0xeb200), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x3a (raw offset 0xef400), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x3b (raw offset 0xf3600), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x3c (raw offset 0xf7800), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x3d (raw offset 0xfba00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x3e (raw offset 0xffc00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x3f (raw offset 0x103e00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x40 (raw offset 0x108000), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x41 (raw offset 0x10c200), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x42 (raw offset 0x110400), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x43 (raw offset 0x114600), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x44 (raw offset 0x118800), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x45 (raw offset 0x11ca00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x46 (raw offset 0x120c00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x47 (raw offset 0x124e00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x48 (raw offset 0x129000), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x49 (raw offset 0x12d200), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x4a (raw offset 0x131400), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x4b (raw offset 0x135600), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x4c (raw offset 0x139800), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x4d (raw offset 0x13da00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x4e (raw offset 0x141c00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: nanddump.bin has a mixed controller LBA at block 0x4f (raw offset 0x145e00), block ignored
               this is likely caused by previously using jaspersb on a jasper type console!
***** WARNING: could not find a non-zero CF LDV to use, setting it to 1 but that may be incorrect!


******* WARNING: could not patch SMC reset limit!




******* ERROR: could not decrypt keyvault, please be sure your provided a valid kv.bin!




***** ERROR: -2 writing to file C:\Users\Administrator\Desktop\J-Runner v02 Beta (288) Core Pack\ \updflash.bin

 

[Martin C]

you rename kv_en.bin to kv.bin

No you don't.

Please stop replying.

OP - you need DECRYPTED files from another NAND for which you have the CPU key for.

 

[chase]

sorry again got mixed up between donor nand and nand with ECC written to it

 

[slighty]

i think i am on to something i have now a console that will glitch with the rater monitor but when i power up the console im getting no video out put.
i managed to download some donor nands and used bincrypt 2 to get jtag image but not getting anything on my tv.