FIXED Can someone check this NAND for me?

[ndi501]

Hi guys

I had a weird moment with j-runner a few days ago and somehow overwrote both my trinity nand dumps with dumps from a jasper. Probably because I didn't close j-runner before i started messing with the next console.

Anyway, I'm in a bit of a pickle because I don't have the original NAND, and I had only written the ECC to grab the keys. Then when I came to write the original NAND it gave me christmas lights.

But the weird part is I still get the same problem if i re-write the ECC. But, I don't know if that ECC was created from the jasper I glitched afterwards.

I still have all the extracted files (kv, smc, fcrt etc) so I've made a retail nand but i could do with someone checking it out for me if they wouldn't mind.

I placed a clean SMC.bin, the kv.bin, smc_config.bin into the data foler of xebuild and built a clean 14719 nand which was the same dash it came with.

Then I set the LDV to 10 which is from the fuses.txt:

fuseset 00: c0ffffffffffffff
fuseset 01: 0f0f0f0f0f0ff0f0
fuseset 02: f0f0000000000000
fuseset 03: 85fe2442bcb6ed3a
fuseset 04: 85fe2442bcb6ed3a
fuseset 05: 978188d6644fa22c
fuseset 06: 978188d6644fa22c
fuseset 07: ffffffffff000000
fuseset 08: 0000000000000000
fuseset 09: 0000000000000000
fuseset 10: 0000000000000000
fuseset 11: 0000000000000000

I haven't tried to write it yet, but I'd just like someone to check it over and make sure ive done it right.

I've already got the coolrunner installed and I'm sure it works fine because I booted to xell a couple of times (I'll post photos of the install if required but i'm not dealing with that part at the moment).

cheers guys!

https://www.dropbox.com/s/qhp6cs1hx6u4wms/updflash.bin

 

[Martin C]

If Xell gives you the DVD key, then it's from the console in question. If it gives you 00000s instead of the DVD key (and an error), it's from another console.

 

[ndi501]

If Xell gives you the DVD key, then it's from the console in question. If it gives you 00000s instead of the DVD key (and an error), it's from another console.

If I flashed a jasper ecc onto a trinity would it still boot xell?

 

[Martin C]

Nope - different bootloaders.

 

[ndi501]

Nope - different bootloaders.

I didn't think so..

Sorry Martin, your comment confused me a little. I don't need to boot xell as I already have the CPU key and DVD key.

I matched the DVD key to the key I already had pulled from the DVD drive, thats how I know that fuses.txt is correct.

Since I don't have the original nand but i have the files extracted from the nand dump, I've built the retail nand image which I need to flash to the onboard nand.

Hopefully this will boot ok since everything I've tried so far as been from using a jasper nand dump.

 

[Martin C]

I only stated that so you would know if you had the right ECC for the console.

Provided you're sure you have the right KV / SMC / SMC-config for each console, you should be ok. The NAND itself isn't much use without the log which was created from it.

 

[ndi501]

I only stated that so you would know if you had the right ECC for the console.

Provided you're sure you have the right KV / SMC / SMC-config for each console, you should be ok. The NAND itself isn't much use without the log which was created from it.

Ah right fair enough!

This is what's been throwing me:

This is a log from j-runner creating a retail nand which I believe must've been from my jasper:

Load Files Initiliazation Finished
14719
Started Creation of the 14719 xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.04.535
---------------------------------------------------------------
building retail image
---------------------------------------------------------------
Z:\Dropbox\XBOX\RGH\J-Runner\650075592605\updflash.bin image built, info:
---------------------------------------------------------------
Console   : Trinity
NAND size : 16MiB
Build     : Retail
Serial    : 650075592605
ConsoleId : 016896097961
MoboSerial: 7029729100079265
Mfg Date  : 06/23/2009
CPU Key   : 85FE2442BCB6ED3A978188D6644FA22C
1BL Key   : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key   : 2F6EDC763262C10D553D3F460E8870EA
CF LDV    : 10
KV type   : type1 (no hash)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Saved to Z:\Dropbox\XBOX\RGH\J-Runner\650075592605
Image is Ready

Note that the DVD key and CPU key are the same as the below log which is from the retail nand I've created earlier, but the mfg date is june 2009 which is nearly impossible for a slim. I've also checked the mobo serial and that matches.

Load Files Initiliazation Finished
14719
Started Creation of the 14719 xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.04.535
---------------------------------------------------------------
building retail image
---------------------------------------------------------------
Z:\Dropbox\XBOX\RGH\J-Runner\151617703305\updflash.bin image built, info:
---------------------------------------------------------------
Console   : Trinity
NAND size : 16MiB
Build     : Retail
Serial    : 151617703305
ConsoleId : 022470583753
MoboSerial: 7256213208330335
Mfg Date  : 08/08/2010
CPU Key   : 85FE2442BCB6ED3A978188D6644FA22C
1BL Key   : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key   : 2F6EDC763262C10D553D3F460E8870EA
CF LDV    : 10
KV type   : type2 (hashed)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Saved to Z:\Dropbox\XBOX\RGH\J-Runner\151617703305
Image is Ready

All that looks good to me as far as serial numbers are concerned!

 

[Martin C]

The top log shows a type 1 KV. That's definitely not right for a Trinity.

Also, serial number is taken from the KV, as is DVD key. So to have two KVs with the same DVD key but different serial numbers and types of KV is impossible without manual intervention.

There's far more going on here than you've said.

 

[ndi501]

The first log I've pasted in was when I thought i had the right nand.

What I don't understand is why it says its a type1 keyvault. I haven't seen one of those for a long time.

Where is the mobo serial etc stored? I think what I probably did was build the first retail nand with the right keyvault but the wrong SMC, and the wrong nand. That was before I realised that all the files had gotten muddled up.

The second log is from after I'd sorted through every.bin file I had and looked at the creation dates and times and built that retail nand in my first post from those.

 

[Martin C]

So the bottom option looks the more likely. Where did you get the SMC and SMC-config.bin files from?

The only issue here is whether or not your original NAND had an FCRT.BIN file. If it did and you don't have it, the only option is to RGH.

 

[ndi501]

It did have fcrt.bin and I definitely have that (i've included it in the new retail nand - I hadn't before) because when I searched my whole dropbox folder for files created on the 19th of sept that was part of them. I only did two consoles that day, one was a trinity and the other jasper. As far as I'm aware only slims have fcrt.bin, I could be wrong though?

However, the files I found were all written at the same time - presumably when jrunner extracted them.

You can't just generate an fcrt.bin can you? And if that's been lost then it'll never boot retail, correct?

I think that image is good to go. I'll flash it when I get home from work and we'll see how it goes. Switch the CR off since its retail obviously.

If it still doesn't boot I'll post pictures of the wiring.

 

[Martin C]

The only other factor is to ensure you've built a NAND with the same bootloaders you previously had. Obviously they changed between 14699 and 14717/14719.

 

[ndi501]

The dash was 14719 when I dumped it and I haven't run any official updates on it so the LDV should be the same and so should the bootloader.

In theory...

 

[Martin C]

Sounds likely, yes.

Before you built the retail NAND, did you copy over fcrt_enc.bin to the same directory as kv.bin etc and rename to fcrt.bin?

The proper updflash.bin log created with this NAND would be really useful.

 

[ndi501]

Yep, I copied fcrt_enc.bin to the rebuild data directory and renamed it to fcrt.bin.

Here's the log - https://www.dropbox.com/s/o2px8x40u10uyet/updflash(091020121147).bin.log

 

[Martin C]

All looks good - Clean Trinity SMC, no FCRT errors and I assume your serial number matches that in the KV?

If so, you should be ok to go.

 

[ndi501]

Ok, cheers Martin! I'll report back later.

 

[ndi501]

That nand booted up to the dashboard with the CR set to PRG. Although I still got the fan wobble and red light was on constant, I've heard of this happening before though and there's an easy fix.

I've made a glitch image from that band now and written it.

When I boot it, the fan sits there shaking the same way as it did with the retail nand, except constantly. During this time the CR doesn't flash at all. However, if I leave it say 30 seconds the fan will stop shaking, the CR will blink and it'll boot to the hacked dashboard.

So now I'm thinking its a hardware issue. It didn't do this before I fit the cool runner though. I've tested it for shorts and haven't found anything. Here are some closeups of the install:

https://www.dropbox.com/s/95l7x9sr48fd72v/Photo 09-10-2012 21 10 16.jpg
https://www.dropbox.com/s/105wslifcmuzqgx/Photo 09-10-2012 21 10 38.jpg
https://www.dropbox.com/s/4v52tps6a5vrpqh/Photo 09-10-2012 21 19 07.jpg
https://www.dropbox.com/s/bfopqd87c0uiexk/Photo 09-10-2012 21 12 30.jpg
https://www.dropbox.com/s/dtoaow4zev9snny/Photo 09-10-2012 21 14 25.jpg

Edit:
Here's the xebuild log - https://www.dropbox.com/s/qrsjoqeeqi5bqbx/updflash(091020121909).bin.log

 

[Repoman 108]

What do you mean by "Shaking fan"? I've heard of the red dot when booting retail NAND on RGH caused by interference, but never the fan shaking... If the console boots both the retail NAND and the RGH NAND within the normal time frame (which it sounds like it does) then it's not an image issue. Once again, because it boots both images fine I'm guessing it's not a CR install issue, but that install looks very poor... Could be that the weirdness is just being caused by interference with the CR configuration? (I'm not a hardware guy, so I can't give you specifics)

 

[ndi501]

I completely re-did the install, cleaned up the solder joints with braid, new flux and solder and it did exactly the same thing.

Those joints weren't great agreed, probably because I'd re-done them so many times.

I've used some wifi cable from an old laptop and a CR3 and now its perfect. Usually glitches first time but occasionally takes a couple of attempts before it'll glitch.

Thanks for all the help Martin, as usual you've been a great help!