Trinity Dev rrod. Bad Nand flash?

I think this is the same kit N64 freak was posting about, but I'm going to give it a shot. It seemed like the console failed to boot after a bad nand flash and he was trying to find the nand from another kit to use as a donor. It sits with the rrod after 20ish seconds and there is no video output.

I guess that's where I'm going to start. If anyone could supply a donor nand that would be greatly appreciated! If anyone else has any ideas feel free to share, maybe someone else is stuck with the same thing.

Sorry in advance for the vertical video.

 

And you're absolutely sure it's a corrupt NAND that is causing your particular error?

 

I can't guarante it to 100% but the person i got it from killed it by modifying the Nand and flashing back the modified nand.
The Nand dump has never been checked after initially backing it up and possibly has been damaged since day one (i didn't do that backup).
I personally tried damaging a Nand dump and "killing" a kit that way and resulted in the same 0020 error. After flashing back the good Nand that one worked again.

Problem here is a missing good original Nand dump.

 

From what I've been told it seems like that is what's going on.

This is the story I was told. It seems like someone didn't make a proper backup and flashed a damaged nand.

 

Just for shits and giggles, have you tried running a recovery on this?

 

It does have a disk labeled "Xbox 360 - Rec 20353" in it but I can't see if it's loading or not because there is no video output. I've started the Xbox with it in but it still rrod.

 

if its the clear xbox, it had a bad kv.

 

This isn't N64Freaks is it?

 

It was his, but I recently purchased it off of him. I think this is the same kit deep3r posted in his collection thread also.

 

Ah. Yeah, I wasn't able to help either of them out with this issue. I'd gladly buy it off you though for collectibility. I fixed this one time with a proto slim but I don't recall what I did

 

As of right now, I want to hold on to it until I can get a donor to mess with. Thanks for the offer though! If anything changes I'll PM you!

 

Please keep me in mind. But for now, I will research my notes on how I fixed mine years back.

 

Nice kit.

 

Thanks, if you could find some notes that would be awesome!

Thank you!

 

So after digging through forever in archives of other sites, I found this by me:

Well my Slim XDK had a corrupted nand. It occurred with a failure mid-update. It would not allow any recovery to continue, failing immediately when I would attempt it. Otherwise it would display E79 on the screen and the fan would run full blast. When I connected my Nand-X to the stress test cables from the top of the console and pulled the nand image off I found it was missing the entire Filesystem table. Eventually after trying everything I discovered a way to fix it. I flashed another XDK Slim's nand to the broken one. It turned on but displayed secondary 0022. When I reflashed the correct nand, it then did the E79 again, however the fan wasn't running full blast this time. I then tried the recovery disc again. Recovery rewrote the nand and has been working ever since.

 

Thank you very much for finding those notes! It gives me a idea of where to start. I've never seen what files are in an XDK nand so I don't know if there is any extra files from a retail. What I do have currently is these. The last file is a picture from 360 Flash Dump, I'm just trying to keep everything together.



I'm am still searching for a donor nand to test with!

 

here is the FileSystem Off a Full Dev Kit

Spoiler: PIC

 

.

 

From my understanding after taking to N64 freak some more, it seems the nand is so badly damaged that it can't successfully make it past the bootloader and that's where it just kind of hangs.

I'm hoping that it's not a GPU issue giving me the AV problems, to me that's not as serviceable as a nand haha. I'm willing to play around with it once I get a donor nand in hopes though!

 

Such a shame though.