Nandflash problem

[sebysin]

Hi
I got the following error when I wanted to build the image with multi builder 7

When I put the original nanndump into the flash tool it freezes and them closes, sometimes it works.
I can only do the image with flashdump.

I put nanddump+cpukey can anybody help me build the image
http://www.4shared.com/rar/89gBgw_q/nandcpukey.html


\\I changed the CF LDV from options; I put 6. But if I don't write anything it says 1. When it boots in Xell, it shows 6xf

 

[JayDee]

When you boot into xell how many f´s are on line 7?

Take a 100% note on this and then open options.ini in the 360_Multi_Builder_v0.7\Data\my360 folder.

Look for the cfldv = line and fill in your number and then try again.

 

[sebysin]

there wasn't anything in cfldv. i put 6.

 

[sebysin]

I write the image and now I can't turn on

 

[WNYConsoles]

Open your NAND in 360 Flash Tool and look for the highest LDV and put that into the options.ini in my360 folder in 360 Multi Builder, then run Multi Builder.

If you want to upload your original nand and post a link to download it I can do this for you.

 

[sebysin]

I put in my first post

 

[tonyjandc]

building image for you

 

[WNYConsoles]

Ill make one too for the hell of it.

OP - Did you just add the DL link for the nand because I did not see that before.....???

 

[tonyjandc]

built you image 14699 with dashlaunch now got to upload it

 

[WNYConsoles]

Your LDV is actually 5. If tonyjandc's image doesn't work, flash the stock nand back and run the official 14699 update. I have experienced problems with Jaspers specifically when building images from older 126xx dashboard NAND dumps.

Additionally, double check your CPU Key as it does not unlock the NAND you provided.

 

[tonyjandc]

sexdrugsoverclocking I am having trouble uploading here can you help ?

 

[WNYConsoles]

sexdrugsoverclocking I am having trouble uploading here can you help ?

Not sure how you created a FB Image correctly with that NAND as the CPU Key is bad.


OP - The CPU Key you provided is incorrect. If you are booting Xell please double-check the CPU key. Once you have the correct key open your NAND in 360 Flash Tool and enter the CPU Key to confirm that the key is correct, then rebuild your image.

360 Multi Builder cannot build a proper image without the correct key.

 

[tonyjandc]

did a double check yes you are right thats what you get for having too manywindows opens . The key doesnt match . Stupid question is that the dvd key it has been done before buddy.

---------- Post added at 09:51 ---------- Previous post was at 09:49 ----------

needs to go back to specsavers me thinks

 

[sebysin]

fuseset 00: c0ffffffffffffff
fuseset 01: 0f0f0f0f0f0f0ff0
fuseset 02: 0000f0f000000000
fuseset 03: 3fbe954aad48307d
fuseset 04: 3fbe954aad48307d
fuseset 05: 5824ee6e84e90e44
fuseset 06: 5824ee6e84e90e44
fuseset 07: ffffff0000000000
fuseset 08: 0000000000000000
fuseset 09: 0000000000000000
fuseset 10: 0000000000000000
fuseset 11: 0000000000000000

My cpukey and CF LDV

 

[WNYConsoles]

I got the correct CPU Key, just wait for me to make you an image before you do anything. There are a few issues with the NAND so I need to use a donor build. This is why I insist updating to 14699, dumping NAND, then building your FB.

Give me a few minutes.


EDIT: Are you sure this is a 16MB Jasper?

 

[sebysin]

yes but I'm not very shure...

 

[WNYConsoles]

Something is wrong with this NAND, there is no file system, I really think you have a 256/512 Jasper. Grab a new dump from Xell and send it to me.

 

[sebysin]

I can't update because I don't have a dvd drive, I have a 256/512 Jasper, dash 2.0.12625.0

 

[JayDee]

1: You can update via usb...
2: READ THIS BEFORE DOING ANYTHING MORE

(Check what flashconfig you get, it tells you if you have a 16,256 or 512 jasper)
You'll get the flashconfig:

01198010 - Xenon, Zephyr, Opus, Falcon
00023010 - Jasper 16mb, Trinity
008A3020 - Jasper 256mb
00AA3020 - Jasper 512mb

Going in to territory where a blind is leading a blind right now as i have not read up on 256/512 nands myself to say for sure, but the nand changes with every boot you might need to build a new retail nand before doing the next step (getting a functioning freebot.bin onto the nand)

So read above link and wait for Martin C or someone that can tell you with 100% certainty.