RGH Jasper 16mb Issue with creating NAND

[AzarVC]

Hello all,

I follow'd Fib3r's guide (Found here: http://team-xecuter.com/forums/showthread.php?t=76193) and everything was going fine until I needed to create my NAND.

So,

I dumped and read the NAND. There were no bad blocks so I didn't repair anything.
I created a Xell/ECC repair glitch image.
Wrote that glitch image to the NAND.
Programmed the coolrunner.
Installed coolrunner.
Booted the 360 into Xell reloaded, retrieved the fuses, cpu key, etc.

But that's where I get stuck.

Everytime I try to create a NAND to flash in multibuilder, it crashes out with an error in GGBuild.

I thought that maybe my NAND dump was poor, so I checked it in Flash Dump Tool, the results are below...

I've no idea what to do next.


A bit of research showed me that this error has happened to people before when their jasper turns out to be a big block instead of a 16mb. So, I'd like to confirm that this is a 16mb. Is there a way to write back to the nand and make it stock?

Any ideas or questions to get this thing working? Appreciate the assist, fellas.

 

[dj_liss]

are you using 0.4 and re check your cpu key.txt is YOUR cpu key as 1 error in the key wil cause the build program to error no matter which one you use as it can't decrypt your orig nand

 

[riget]

I'm not hot on software, but that dump tool is showing an old dash firmware, did you update it first?
It also shows a 16mb jasper.

 

[Martin C]

OP - first thing to do is to post the output of nandflash.log when it errors.

 

[AzarVC]

are you using 0.4 and re check your cpu key.txt is YOUR cpu key as 1 error in the key wil cause the build program to error no matter which one you use as it can't decrypt your orig nand

I am using 0.4, and I'll double check the CPU key when I get home.

I'm not hot on software, but that dump tool is showing an old dash firmware, did you update it first?
It also shows a 16mb jasper.

I thought I had, but I did only check to make sure this 360 worked. Balls. How do I update now??

OP - first thing to do is to post the output of nandflash.log when it errors.

My apologies, Martin...

It instantly crashes out and does not create a nandflash or nandflash log, and doesn't show an error code.

 

[Martin C]

I'm not hot on software, but that dump tool is showing an old dash firmware, did you update it first?
It also shows a 16mb jasper.

TIP

---

You do NOT need to update your console before the process.

I have done a large number of these installs now and a few on 9199 slims.

---------- Post added at 09:45 ---------- Previous post was at 09:44 ----------

My apologies, Martin...

It instantly crashes out and does not create a nandflash or nandflash log, and doesn't show an error code.

What error do you see on screen?

 

[AzarVC]

TIP

---

You do NOT need to update your console before the process.

I have done a large number of these installs now and a few on 9199 slims.

---------- Post added at 09:45 ---------- Previous post was at 09:44 ----------



What error do you see on screen?

I don't see any error other than multi builder just disappearing. If there's a way I can try to get the error to show, I'm all ears. I feel that would be the most helpful...

Here's a vid of it happening...

[ame="http://www.youtube.com/watch?v=sYWieRi9yoU"]360 Multibuilder Error - YouTube[/ame]

 

[Martin C]

what size is your nanddump.bin which is in my360? ggbuild thinks it's a big block NAND.

 

[AzarVC]

I'm at work, so I can't verify right now...but I'm pretty sure it's 16mb or so. When I get home I'll get the exact size.

 

[Martin C]

s'ok - it's in your video.

How sure are you this is a 16MB Jasper? What does NANDPro detect the FlashConfig as when you dump the NAND?

 

[AzarVC]

Honestly, I'm not that sure anymore. :facepalm: When we started I coulda sworn it was a 16mb.

I didn't save or screenshot the cmd file of the dump, so I'm not sure.

If I go home and dump the nand again (that is injected with the modded ecc file/glitch file) will it pull up the proper flashconfig even though it now has a modded 16mb ecc file?

 

[Martin C]

You can't change the flashconfig of the Southbridge by flashing it, so it'll still be correct.

In your video, you see ggbuild show a screen to state that the NAND has a MU area identified. It must have detected a big block NAND for this to happen.

 

[AzarVC]

Awesome, okay. As soon as I get home I'll check that.

Now, if/when it does show that it's a big block Jasper. How do I go about flashing the NAND back to stock so I can dump 64mb and restart? Or what's the best way??

 

[Martin C]

To get back to stock:

nandpro usb: -w16 nanddump.bin 0 50
(replaces the ecc data)

Read a proper BB Jasper:

nandpro usb: -r64 nand.bin

 

[AzarVC]

Thanks so much, Martin.

I will do this tonight when I get home and post back up.

 

[AzarVC]

Ugh, no such luck.

I used the commands you gave me to re-write the first 50 blocks of the stock NAND back to the system.

Then did 2 full dumps of 64 mb (It did turn out to be a 256mb jasper. :facepalm: )
No bad blocks during the dump, compared the 2 dumps, no differences.

Created a new ECC file, wrote that to NAND with the nandpro usb: +w64 image_00000000.ecc command Made sure that worked by booting into Xell, which it did fine.

Then I created my NAND image with multibuilder v4 using my first 64mb nanddump.bin, it created nandflash.bin and xenon.elf. Copied those to my USB stick.

Plugged that into my 360, turned it on, booted into xell and it tried to write. But it seemed to have some issues...

It looked like this screenshot, but after "attempting to write xxx blocks to flash" it says

bad block sensed 00ex (whatever block it is) error 0x000240 (not exactly sure what error code or what it said as I didn't take a picture because I thought maybe it was normal and I powered down my system at the end)

for a lot of blocks, then it said..

processing 0x0200 of 0x0200

image written, shut down now.

Shut down, disco'd power, video, internet, usb for 30 secs. Reconnected video and power, turned on via power button. Coolrunner flashed green led twice, then didn't do it again. Though it didn't boot to dash...

I can boot to the black Xell screen by using eject.

Did I miss a step?? Why would it say bad block when I dumped my nand and it said no bad blocks?? I'm a bit baffled.

 

[Martin C]

Did your console boot after you wrote the 1st 50 blocks back ?


Sent from my iPad using Tapatalk.

 

[AzarVC]

Didn't try it the first time, I rewrote the first 50 blocks again using my original 16mb dump.

The 360 tries, but the 4 green lights don't flash like they usually do, ya know..in a circle. Just gives the 3 red lights.

Checked the secondary code, it's 0022.

Balls.

It does have the xclamps, should I do an xclamp fix and see if that will work?? Any suggestions?

 

[Martin C]

Didn't try it the first time, I rewrote the first 50 blocks again using my original 16mb dump.

The 360 tries, but the 4 green lights don't flash like they usually do, ya know..in a circle. Just gives the 3 red lights.

Checked the secondary code, it's 0022.

Balls.

It does have the xclamps, should I do an xclamp fix and see if that will work?? Any suggestions?

No, the error has nothing to do with RRoD. It's the console telling you that there's a problem with the startup.

Flash XeLL to it first and get it to boot again. You may need to build a clean NAND.

 

[AzarVC]

Okay, I'll flash Xell to it and get it to boot when I get home tonight.

How do I go about building a new NAND?