16203 retail red dot

[ccNick]

I have just updated my retail NAND from 14699 (working perfectly) to 16203 and I'm now getting a red dot a few seconds after power on.

When I flash the 14699 NAND the console starts up fine.

When I flash the 16203 NAND I can hear the coolrunner (rev a/original TX coolrunner) sending the reset signal (fan noise) once the power button is pressed and after a few reset's the red dot appears.

I'm using a trinity that I installed the original TX coolrunner in back in January 2012.

When I boot the 14699 retail NAND I don't hear the coolrunner sending the reset signal and the console boots straight away.

I created the new retail NAND using the latest Jrunner and have flashed with both the toolbox and jrunner but either method yields the same results.

I'm stuck as to what I should try next and why the coolrunner is sending the reset signal when it should be disabled.

 

[15432]

Update it with official update package. New bootloader won't work with old CBLDV

 

[ccNick]

Online or via USB?

 

[15432]

It doesn't matter what way you use

 

[Martin C]

You can't just build a new retail NAND with a higher CB...

 

[ccNick]

Good job I didn't connect to live then.

Any ideas what I need to be looking into? Do you have any links so I can RTFM?

 

[Martin C]

Why are you trying to build a new retail image?

This is probably the best question to ask here.

 

[ccNick]

For Xbox live use.

 

[Martin C]

You have a DemoN, so effectively you treat your 360 NAND exactly the same as any other XBL console: With the DemoN light off (360 NAND selected), connect to XBL and update.

There should be no reason why you would ever need to write to the 360 NAND using the DemoN. J-Runner warns you for this reason.

 

[5kmods]

I'm not sure what official update caused red dot on reital dual boot systems, However the need for coolrunner power off during retail use was implemented at some point - may have been the cause of your issues.

set it to PRG and reboot it?

 

[Martin C]

I'm not sure what official update caused red dot on reital dual boot systems, However the need for coolrunner power off during retail use was implemented at some point - may have been the cause of your issues.

set it to PRG and reboot it?

The issue is he tried to build himself a retail NAND but the CB doesn't match his fuses.txt.

As I said, you shouldn't ever need to build a new retail NAND under normal circumstances (i.e existing NAND dump works).

 

[ccNick]

Cheers Martin.

So take the update from MS and then build a new demon/RGH NAND from that when the next update comes?

I was just being cautious as I've been away for a while and a lot has changed, didn't want to take the update and find I can no longer boot the RGH.

 

[Martin C]

Nothing MS release will stop your console's ability to RGH.

So update the retail, dump the new NAND and use with the CPU key to build a new RGH image.