Help identify what is flashed on my NAND?

Svorax

Junior Member
Mar 8, 2010
23
0
Katy, TX
Hey guys, I bought a slim corona v3 a couple years ago on black friday right after the XBone came out. I got the hardware to RGH it and got a little ways in but had some things in my life come up and I put the project on hiatus. I decided to pull it out of my closet yesterday and found that I truly have no idea what I had done. When I got it out, I found that I had soldered the wires to r/w the NAND and I apparently got it right because I was able to dump the NAND no problem. I also had the postfix adapter v2 installed but that is all. I pieced the system together shoddily (so that I wouldn't have to take the housing apart again) and found that it does not boot. The CPU fan spins but neither drive spins up. The light is green for a bit, but eventually turns red and flashing and the CPU goes full blast for some reason. I thought perhaps that I should remove the postfix adapter in an effort to make it "as stock as possible," but this had no effect. So it seems to me that I had written something to the NAND and I unfortunately have no NAND backup. Any way to tell what is written to the NAND? I never even got my CPU key so I'm not sure where to even start.

EDIT: I actually thought it was a corona v3 by the identification pictures, but now I'm not sure as I've just discovered J-Runner tells me my NAND dump is a Trinity. For reference, my console takes 9.8 amps and was manufactured in April 2013. It also came with a 250GB drive. It definitely does not have the postfix printed on the board next to the CPU, so I was pretty confident it was a corona v3.
 
Last edited:

Alteration

Full Member
Oct 7, 2015
46
0
Raleigh, North Carolina
The Trinity uses 10.83 amps, so I'm fairly sure it's not a Trinity. 9.86 amps is a Corona, but assuming you didn't truncate the hundredths place in the amps to 9.8a, I can't identify this Xbox based off of: http://team-xecuter.com/psu.png

Knowing which motherboard you have will make this process a lot easier in terms of "as stock as possible".
 

Svorax

Junior Member
Mar 8, 2010
23
0
Katy, TX
Err, well not I'm even more confused. I did actually just truncate the .06 because I was stating from memory but now that I'm looking at it, it *actually* says 9.6 amps specifically!

2016-04-10 23.09.46.jpg
 

GeekHeat

VIP Member
Jun 28, 2013
1,805
88
lancashire
U can't go off power supply to tell what mobo u have.
Trinity has a hana chip coronas don't.
Postfix adapters are not needed in trinity's as the post points are there.
Show us pics of the mobo.
If u don't have the original nand dump u can still rgh it.
 

Svorax

Junior Member
Mar 8, 2010
23
0
Katy, TX
@GeekHeat: The PSU and actual housing have the same amperage listed; the PSU was just easier to take a picture of. Regardless, I'm at work so I can't take a picture ATM. I can however guarantee that the mobo does not have a HANA chip. Not only this, the post points are also not there. Let me ask you this: does J Runner pull the board data from the NAND dump? I'm starting to wonder if I maybe flashed a trinity firmware to a corona board. I'll be sure to upload a pic of my mobo this evening.

@Joo C: I never even got the glitch chip installed. I didn't get that far into the process.
 

GeekHeat

VIP Member
Jun 28, 2013
1,805
88
lancashire
Ok so its a corona. Just install a glitch chip and postfix adapter.
Then just write corona ecc to the nand and then try n boot xell to get CPU key.
Once u have the CPU key u can create a xebuild image with a donor nand.
 

Svorax

Junior Member
Mar 8, 2010
23
0
Katy, TX
Odd that J Runner reports it as a Trinity then. So I'm guessing I should override that and force it to install the Corona ECC? Also, I tried doing this previously, but it halted on write after it threw a wrong header error.
 

Svorax

Junior Member
Mar 8, 2010
23
0
Katy, TX
OK sure. I uploaded on imgur to prevent having to compress the image.
http://i.imgur.com/pzuvgRX.jpg
Here's my log:

===================================================
Saturday, April 09, 2016 6:25:19 PM

J-Runner v0.3 Beta (8) Started


Connection Error
Checking Files
Connection Error
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x00043000
00043000
Corona
CB Version: 9188
Trinity
Reading Nand to C:\Users\---\Desktop\J-Runner\output\nanddump1.bin
Reading Nand
Error: 250 reading block C6
Done!
in 3:28 min:sec

Reading Nand to C:\Users\---\Desktop\J-Runner\output\nanddump2.bin
Initializing nanddump1.bin..
Header is wrong..
Trinity
Glitch2 Selected
Nand Initialization Finished
Reading Nand
Error: 250 reading block C6
Done!
in 3:28 min:sec

Comparing...
Bad Block ID 00C6 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 00C6 [Offset: 0x330C00]
Bad Blocks Remapped
Bad Block ID 00C6 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 00C6 [Offset: 0x330C00]
Bad Blocks Remapped
Nands are the same
Creating Directory C:\Users\---\Desktop\J-Runner\xeBuild\16747\bin
Downloaded *xeBuild/16747/bin/addon.idx
Downloaded *xeBuild/16747/bin/nofcrt.bin
...
Downloaded *xeBuild/16747/_jtag.ini
Downloaded *xeBuild/16747/_retail.ini
Creating Directory C:\Users\---\Desktop\J-Runner\xeBuild\common
Downloaded *xeBuild/common/cb_1921.bin
Downloaded *xeBuild/common/cb_1940.bin
...
Downloaded *xeBuild/common/xenonjklatin.xtt
Downloaded *xeBuild/common/ximedic.xex
Finished Checking Files
Checking Console..
Version: 10
Flash Config: 0x00043000
00043000
Corona
CB Version: 9188
Trinity
Header is wrong..
Invalid Image
Failed to create ecc image
Checking Console..
Version: 10
Flash Config: 0x00043000
00043000
Corona
CB Version: 9188
Trinity
Corona Manually Selected
Header is wrong..
Invalid Image
Failed to create ecc image
Checking Console..
Version: 10
Flash Config: 0x00043000
00043000
Corona
CB Version: 9188
Trinity
Header is wrong..
Invalid Image
Failed to create ecc image
 

Svorax

Junior Member
Mar 8, 2010
23
0
Katy, TX
It's a Corona with ecc writen to nand.Install CR4, get cpukey and folow this tutorial: http://team-xecuter.com/forums/threads/92607-How-to-recover-from-losing-NAND-(but-have-ECC-written)
I've gone ahead and bought a CR4, a Corona QSB v3, and a new Postfix adapter v1. My previous postfix adapter was damaged on removal and the v2s are very difficult to find so I simply bought a v1. I read that their basically the same thing so I assume that will be fine. I've run into a new problem now. I got everything soldered and hooked up but I cannot seem to get it to boot. No matter what DIP/jumper settings I try, the debug light just flashes green indefinitely. This system just does not want to glitch. Any advice?
 

john mathews

VIP Member
Jan 3, 2014
2,551
88
peoria illinois
I've gone ahead and bought a CR4, a Corona QSB v3, and a new Postfix adapter v1. My previous postfix adapter was damaged on removal and the v2s are very difficult to find so I simply bought a v1. I read that their basically the same thing so I assume that will be fine. I've run into a new problem now. I got everything soldered and hooked up but I cannot seem to get it to boot. No matter what DIP/jumper settings I try, the debug light just flashes green indefinitely. This system just does not want to glitch. Any advice?
upload pic of soldering and jr log, did u check the cr4 box before u wrote the ecc
 

Svorax

Junior Member
Mar 8, 2010
23
0
Katy, TX
upload pic of soldering and jr log, did u check the cr4 box before u wrote the ecc
Well I'll post a pic of what is and is not done, but I think you answered my question. I wrote this ECC long ago before the CR4 was even announced so it's not an ECC for CR4. I supposed that's why it refused to boot. I had soldered and unsoldered so many times that the CPU_RST pad has lifted. I'm going to use an alternate for this. Regardless, I'm guessing I'll need to use this Slim Proto v2 first to get the key, then build XeBuild for CR4 correct?
 

GeekHeat

VIP Member
Jun 28, 2013
1,805
88
lancashire
Well I'll post a pic of what is and is not done, but I think you answered my question. I wrote this ECC long ago before the CR4 was even announced so it's not an ECC for CR4. I supposed that's why it refused to boot. I had soldered and unsoldered so many times that the CPU_RST pad has lifted. I'm going to use an alternate for this. Regardless, I'm guessing I'll need to use this Slim Proto v2 first to get the key, then build XeBuild for CR4 correct?
U may need to repair the CPU rst point before using an alternative point.

U use the cr4 to do the glitching side of things. Don't know where u got proto v2 from. Just create an ecc with cr4 ticked and write to Xbox nand. Install cr4 chip and set to slim and correct dips and then try to boot xell
 

Svorax

Junior Member
Mar 8, 2010
23
0
Katy, TX
U may need to repair the CPU rst point before using an alternative point.

U use the cr4 to do the glitching side of things. Don't know where u got proto v2 from. Just create an ecc with cr4 ticked and write to Xbox nand. Install cr4 chip and set to slim and correct dips and then try to boot xell
The slim proto is what I was going to use in the first place. It's what I bought 2 years ago when I first started this thing. If I wrote a non CR4 ECC to nand and I don't have the original, how can I write a new ECC? Can I just write over it and it will still work fine? If I can just write over it, that would be much easier.

corona cpu rst under xclamp is dead end , if messed that up , u don't have to repair , u alt point, post pic of install please
As far as repairing the CPU_RST, it looks like there are two pads next to each other for a resistor. Will it be any harm if I bridge the two pads? If I don't have to worry about the two pads getting bridged, then I can really just use the other pad and it will be easier. Here's what I have right now:

http://imgur.com/a/FmBvT

That double shielded cable is not very flexible; Just the force of it pulling up from the board is what lifted that pad. If I can use that regular 30 gauge wire, it'd be much easier.