Nand flash errors from xell

[Sovereign.]

I had Xmods install my coolrunner and he did a great job. One day I decided I wanted the 13604 dashboard as I liked the layout better. Made a build with ggbuild using the nand xmods provided me that had 0 bad blocks. Went to flash it using a usb flash drive and everything went well. Turned my console off and unplugged the psu and waited two minutes. When I turned it on it would just be a black screen. So I try to flash the xell build Xmods had made for my console and it went well without any errors using my nand x. When I booted it up it was normal. I put the nandflash.bin and xenon.elf Xmods had used on my console on a fat 32 formatted usb stick and started up my console and when xell went to write the nand I got a ton of errors. About 90% of the blocks did not flash. When I turned off my console and unplugged the psu for two minutes and plugged it back in I got the E 79 error. I flashed xell back on there and tried it again and I got the same thing. So I try to flash xell back to the console not thinking about restarting with the eject button. 90% of the blocks don't flash and when I start it up no xell. I tried again and 100% of the blocks did not flash. So now nothing will boot. This is not a soldering problem in my view as Xmods did the soldering and xell could not flash the nand either from USB. I really hope this can be solved. It has a falcon motherboard if that helps. Also I do not get an E 79 as 10% if that of the xell nand is written but the fan keeps going as normal and the middle light on the rf board keeps flashing.

To long did not read: Nand x and xell both cannot flash the nand. I now do not have access to xell. Xell was using a USB so I think that eliminates soldering.

 

[Martin C]

What console do you have? If it's a BB Jasper, you needed to ensure you were using rawflash v4.

Did you check the LDV on your console before using the dump to build the new dashboard? Did they match?

 

[Sovereign.]

I have a falcon. No I did not check the LDV. I also can't write to the nand at this moment.

 

[itchyf1ngaz]

always make sure ldv matches that is a sure way to have incompatible nand. hence e71. this is very importand that is theefuse that is burned. keep this in mind because when team x comes out with the demon. you will want to use a band kv and make sure that your jtag side and your retail ldv matches or it will be insta band

 

[Sovereign.]

always make sure ldv matches that is a sure way to have incompatible nand. hence e71. this is very importand that is theefuse that is burned. keep this in mind because when team x comes out with the demon. you will want to use a band kv and make sure that your jtag side and your retail ldv matches or it will be insta band

Well now nothing boots up but the green light on the console. How do I fix this?

 

[Martin C]

You now need to write to the NAND using a hardware method.

 

[Sovereign.]

You now need to write to the NAND using a hardware method.

Ok, to be clear can I use the nand x for this? Do I make a new nandflash.bin with ggbuild using the nand that was on my console that booted into the hacked dash? Also last night I could not write with my nand x as well with xell using a USB stick containing the nandflash.bin and xenon.elf when I had xell. About 90% of the blocks would not write. I can try now and post my results using nand x but I would like to get a reply first answering my questions.

 

[Sovereign.]

Xell is now back on my console. Do I flash my nandflash.bin file that contained the hacked dash that was previously on the console or make another build with ggbuild using my original nand?

 

[BL4K3Y]

I would build a new glitch image to be sure it was done correctly, then put xenon.elf (RawFlash v4) and nandflash.bin on the root of a FAT32 USB stick and try the update again.