FIXED My 2nd Demon Trinity Install and another red dot on stock nand!!

[stj2112]

Have just completed my second Demon install and found that I had a red dot again booting stock nand (15774) but working fine but with no controller leds.


I had to switch the CR Rev B that I used to the Phat position to clear the red dot but boot times realy suffered. Was glitching in around 1.5 mins to 2 mins.

I tried to tune up by useing all the QSB points and bridging Cap & shielded cable to no use.

Then I lengthened the blue wire CPU_RST to approx 20cm soldered it on point 41 on the QSB and bang boot times of betweeen 5 secs and 30 secs but mostly 20 secs and now well chuffed !!

Pics attached before I lengthened CPU_RST

Just thouight I would share this

I've never realy got on with shielded cable from CR Rev. C's all sorts of probs.

Don't know what this red dot is all about hope the CR III fixes in the future as have another Trinity to sort out at a later date

 

[Themonk]

Thanks for sharing mate. Ur install looks nice and clean. Good job!!

 

[stj2112]

Thanks for sharing mate. Ur install looks nice and clean. Good job!!

Yea thanks m8 - just wondering if it's to do with Demon firmware and perhaps a firmware update would poss fix??

 

[sick360mods]

Don't believe so. It might just slims being a pain in the ass. Mine works fine without a red dot

Sent from my PC36100 using Tapatalk 2

 

[BL4K3Y]

I got a red dot with the stock NAND on a DemoN install.

OggyUK advised me to set the CR to PHAT and it worked !

The Trinity I have here is a repair I have done for somebody - the 50CM CPU_RST wire (I left it at it's standard size) is wrapped around the X-Clamp and I get < 30 second boot times.

 

[sick360mods]

I'd rather have the red dot. Looks cool to me and a easy way to if your on demon or stock nand. Maybe that should be added to demon

Sent from my PC36100 using Tapatalk 2

 

[Martin C]

I don't see any images of your CPU_RST soldering, which is what normally causes this.


Sent from my iPad using Tapatalk HD

 

[stj2112]

I don't see any images of your CPU_RST soldering, which is what normally causes this.

Here are the pics of the Post QSB I ommited
These were taken before I cleaned up the exess flux
Thanks Martin

 

[Martin C]

Well that eliminates that!

I really would solder all the QSB points on there though, as it helps keep the board steady.


Sent from my iPad using Tapatalk HD

 

[stj2112]

Well that eliminates that!

I really would solder all the QSB points on there though, as it helps keep the board steady.


I did put some hot glue on to steady but advise taken and
will solder all points in future.
Thanks again Martin

 

[socalbill]

great examples of clear, concise pics...wish everyone took pics like this

 

[Mack702]

great examples of clear, concise pics...wish everyone took pics like this

What he said , beautiful pics. Well done.

 

[gamehawk55]

I figured out what causes the red dot when booting the stock nand. It is interference within the CPU_RST line causing the xbox to "rapid reset". Listen to the fan when you are booting the demon NAND. If you hear the fan stuttering rapidly a few times before the debug light comes on on the coolrunner, then you need to find a better placement for your CPU_RST line to eliminate the stutter. With proper placement and minimal interference you should only here the fan chirp once per reset on the coolrunner.

I have noticed that with the coolrunner in place, even though it is techically disabled when booting stock, it's still sending a reset pulse once as if it were enabled while booting to the stock nand. But if you have too much interference that could be 2 or more pulses.

I figured this out with my second demon install. At first I was using the POST QSB and I was getting too much interference (fan would stutter 2-3 times before debug) but I was still getting decent boot times so I was going to leave it. But when trying to boot the stock nand that triple reset would still happen before booting which the xbox detects as a fault and throws the error light on but the dash still boots up fine for some reason. So I switched from the POST QSB points (left the QSB board in place) and used the 50cm wire coiled under the board in the usual place and soldered the wire to the quick-solder point on the QSB. That got rid of the rapid reset issue (the wire probably acting as shielding on itself from being coiled). So now when I boot the stock nand I get no reset stutter and the error light never comes on. Had to do a bit of trial and error after with wire length to get good boot times, but now the demon boots in 5-15 seconds and the stock side boots without error 100% of the time.

The reason switching the CR to PHAT mode works to get rid of the red dot on boot is because for some reason with the CR switched to PHAT it never rapid resets (gets rid of the interference somehow), but then most of the time your demon boots suffer, unless you have a slim that boots better in PHAT mode

Hope this helps someone with this problem cuz I know optimizing boot times in PHAT mode can be a pain sometimes

 

[stj2112]

great examples of clear, concise pics...wish everyone took pics like this

&

What he said , beautiful pics. Well done.

Thanks for your comments

Used my new Ixus 240 HS Digital Camera which I got in June this year.

A fantastic compact low light camera.

Can take pics in low light without a flash and retain all the colours (not washed out with flash) and good macro shots 16 mega pixel.

I've had many many digital camera's of all makes & can highly recommend !!

 

[stj2112]

I figured out what causes the red dot when booting the stock nand. It is interference within the CPU_RST line causing the xbox to "rapid reset". Listen to the fan when you are booting the demon NAND. If you hear the fan stuttering rapidly a few times before the debug light comes on on the coolrunner, then you need to find a better placement for your CPU_RST line to eliminate the stutter. With proper placement and minimal interference you should only here the fan chirp once per reset on the coolrunner.

I have noticed that with the coolrunner in place, even though it is techically disabled when booting stock, it's still sending a reset pulse once as if it were enabled while booting to the stock nand. But if you have too much interference that could be 2 or more pulses.

I figured this out with my second demon install. At first I was using the POST QSB and I was getting too much interference (fan would stutter 2-3 times before debug) but I was still getting decent boot times so I was going to leave it. But when trying to boot the stock nand that triple reset would still happen before booting which the xbox detects as a fault and throws the error light on but the dash still boots up fine for some reason. So I switched from the POST QSB points (left the QSB board in place) and used the 50cm wire coiled under the board in the usual place and soldered the wire to the quick-solder point on the QSB. That got rid of the rapid reset issue (the wire probably acting as shielding on itself from being coiled). So now when I boot the stock nand I get no reset stutter and the error light never comes on. Had to do a bit of trial and error after with wire length to get good boot times, but now the demon boots in 5-15 seconds and the stock side boots without error 100% of the time.

The reason switching the CR to PHAT mode works to get rid of the red dot on boot is because for some reason with the CR switched to PHAT it never rapid resets (gets rid of the interference somehow), but then most of the time your demon boots suffer, unless you have a slim that boots better in PHAT mode

Hope this helps someone with this problem cuz I know optimizing boot times in PHAT mode can be a pain sometimes

Yea you have got this spot on. That's exactly what's been happening to both of my Demon Trinity installs.

The fan judders for a while 15secs to 35 secs without the debug green light comming on at all. Then it starts glitching with a green light and boots fairly quickly with CR in Slim mode. Normally within 3 green pulses.

I thought realy weird behaviour

Does non of this with CR in Phat mode just pulses green straight away. Although as I said before, a lot of experimenting needed to get good boot times.

Now it reminds me I thought it strange that when I first RGH'd the box I switched CR to prog mode to use with stock nand for live for a while before the Demon install and it showed a red dot then 98% of the time.

So it makes sense to me now that you have explained it's not the Demon at fault at all.

So thanks, great explanation

Will try to re-route the CPU_RST cable next time like you said

 

[Oggy]

Could someone try and disable C15 or remove it as opposed to switching to phat?

That should work, if my memory serves me correctly.

 

[sick360mods]

Ill try it on a slim on putting in a demon now if it happens

Sent from my PC36100 using Tapatalk 2

 

[Oggy]

Any luck?

 

[ndi501]

Sorry for bringing up an old-ish thread but I'm having the exact same issue.

Oggy I'll try removing c15 on mine tomorrow and report back.

With mine it resets 3-5 times on stock and does the same for about 30 seconds with a glitch NAND. Although Im not using a demon at the moment I will be. I AM using the CPU-rst qsb though. Might try removing it and using 50cm wrapped round the xclamp.

 

[ndi501]

Removing c15 made no difference at all, trying it with a cr3 now.

Doesnt do the constant reset when switched to phat, and takes forever to boot to a glitched dash.

So strange!