RGH Coolrunner stopping console from booting?

jayfig

VIP Member
Oct 29, 2010
314
0
North Carolina
Ok so now that the newly decrypted cb's are out now we can create a 14719 dash retail image right? So I created a retail 14719 and even tried bumping up the ldv up 1 and the 360 still doesnt boot just a black screen. Could the coolrunner stop it from booting properly because it needs the new jed file that hasnt been released yet? If so what can I do to disable it on a falcon board?
 
Ok so now that the newly decrypted cb's are out now we can create a 14719 dash retail image right? So I created a retail 14719 and even tried bumping up the ldv up 1 and the 360 still doesnt boot just a black screen. Could the coolrunner stop it from booting properly because it needs the new jed file that hasnt been released yet? If so what can I do to disable it on a falcon board?
This is a new style of RGH hack (hence RGH 2.0) and there will be a new JED file, changes to the CoolRunner design, changes to the QSB's and possibly new install methods (we'll also show you how to change your older version TX CoolRunner to be compatible with the new hack, and initial tests have shown that other cheaper versions of RGH hardware will not work at all).
It looks like we have to wait a little while longer.

From what I've been reading, it looks to be that only the Slim dashes are available.

I believe that the Coolrunner isn't a problem. We're still waiting on the hacked images to be released (along with new PHAT hardware.)
 

jayfig

VIP Member
Oct 29, 2010
314
0
North Carolina
It looks like we have to wait a little while longer.

From what I've been reading, it looks to be that only the Slim dashes are available.

I believe that the Coolrunner isn't a problem. We're still waiting on the hacked images to be released (along with new PHAT hardware.)
Are you sure because I checked the cb and the retail nand 14719 was correct (falcon 5773) after creating it with jrunner
 

ball00

VIP Member
Nov 8, 2011
632
0
France
You sure you're building yuor image with the correct cb for your console? Try building a retail image with multibuilder that may work.
 
  • Like
Reactions: XJonnyGunsX
Are you sure because I checked the cb and the retail nand 14719 was correct (falcon 5773) after creating it with jrunner
I know what you're saying.

The software does say everything looks good, but there's a lot more that Team-X has to do before we can glitch it with our own hardware. This is all based on what I've been reading the last few days.

I've also seen Ubergeek say that it still needs to be released. (The hack in general.)

It's in the front page, on www.team-xecuter.com

Edit: I see what you're saying. I'm too tired. I apologize.

You want to update your dash to 14719 from a lower dash through J-runner. Am I right? One that hasn't been updated straight from Live?
 
Last edited:

jayfig

VIP Member
Oct 29, 2010
314
0
North Carolina
I know what you're saying.

The software does say everything looks good, but there's a lot more that Team-X has to do before we can glitch it with our own hardware. This is all based on what I've been reading the last few days.

I've also seen Ubergeek say that it still needs to be released. (The hack in general.)

It's in the front page, on www.team-xecuter.com

Edit: I see what you're saying. I'm too tired. I apologize.

You want to update your dash to 14719 from a lower dash through J-runner. Am I right? One that hasn't been updated from MS?
Yes but I have updated it through M$ thats why im bumping up the ldv from 17 to 18. And I tried using multibuilder .82 cb is correct 5773. And Im not trying to create a gltich image I know that wont work because the completed glitch nand ends up as dash 14719 with old cb 5771
 
Last edited:
Yes but I have updated it through M$ thats why im bumping up the ldv from 17 to 18. And I tried using multibuilder .82 cb is correct 5773
Ah, ok. Understood.

Unfortunately, we'll have to wait till everything is released for the PHAT console. The split CB hack hasn't been released yet.

So, I'd say your Coolrunner is fine for what it is.

TX is working on new timing files for the PHATS along with changes in the coolrunner and QSB's.

I updated my Jasper RGH so I could turn in the Post-updated NANDS for R&D. It simply won't work until we get the "upgrades" from TX.

This is a new style of RGH hack (hence RGH 2.0) and there will be a new JED file, changes to the CoolRunner design, changes to the QSB's and possibly new install methods (we'll also show you how to change your older version TX CoolRunner to be compatible with the new hack, and initial tests have shown that other cheaper versions of RGH hardware will not work at all.) www.team-xecuter.com
 
Last edited:
Will the current timing now prevent retail 14719 from booting?
If you have your original updated NAND flashed back and your coolrunner switched to PRG (off) it should boot fine.

That's if your stock NAND's LDV wasn't user changed.

I was going to re-post and state that I have had booting issues, with the coolrunner on, when I was booting into a stock retail NAND.
 

jayfig

VIP Member
Oct 29, 2010
314
0
North Carolina
Well that the problem the only original nand I have is 13604 I updated it and erased 14717 by accident. So im stuck with updated cb and old original nands
 
Last edited:

jayfig

VIP Member
Oct 29, 2010
314
0
North Carolina
If you have your original updated NAND flashed back and your coolrunner switched to PRG (off) it should boot fine.

That's if your stock NAND's LDV wasn't user changed.

I was going to re-post and state that I have had booting issues, with the coolrunner on, when I was booting into a stock retail NAND.
I created a retail 14719 nand with multibuilder .82 using a old original 13604 nanddump. And Im booting the newly created retail nand with the coolrunner switch on NOR
 
Well that the problem the only original nand I have is 13604 I updated it and erased 14717 by accident. So im stuck with updated cb and old original nands
Ah! I see.

You can make a retail NAND with Multi-Builder.

Take your older pre-updated NAND and run it through the latest version of Multi-Builder. It'll give you the option to build a retail NAND.

I'm assuming you have your CPU key as well.

I've had to do this with a few consoles, but this was before the split CB had come out.

I'm sure this is possible, but I would need a more experienced individual to back me up with the newer CB situation.

---------- Post added at 03:54 ---------- Previous post was at 03:49 ----------

I created a retail 14719 nand with multibuilder .82 using a old original 13604 nanddump. And Im booting the newly created retail nand with the coolrunner switch on NOR
Oh? Nice!

So, you're able to get it booted now? Excellent!

I didn't see your last post.

You'll be able to boot with the coolrunner on. You might run into an occasional RRoD because of the coolrunner interfering with the normal boot process.
 

jayfig

VIP Member
Oct 29, 2010
314
0
North Carolina
Yes I do have my cpu key but as for using stock 14719 or 14717 I do not have. Thats why I have to use 13604 because its the only stock nand I have. I took the official update online from M$ from 14699 to 14717 and deleted the stock nand by accident. Im thinking that the jump from 13604 to creating a retail nand with the latest version of multibuilder .82 could be the problem. Multibuilder .82 updates the cb from 5771 to 5773 falcon just fine but my console is still not booting. Its either the coolrunner or the newly updated phat cb's needs to be fully decrypted (a bug or somewhat). They way it looks I might have to wait for another update or the DEMON to be released.

---------- Post added at 06:08 ---------- Previous post was at 06:05 ----------

Ah! I see.

You can make a retail NAND with Multi-Builder.

Take your older pre-updated NAND and run it through the latest version of Multi-Builder. It'll give you the option to build a retail NAND.

I'm assuming you have your CPU key as well.

I've had to do this with a few consoles, but this was before the split CB had come out.

I'm sure this is possible, but I would need a more experienced individual to back me up with the newer CB situation.

---------- Post added at 03:54 ---------- Previous post was at 03:49 ----------



Oh? Nice!

So, you're able to get it booted now? Excellent!

I didn't see your last post.

You'll be able to boot with the coolrunner on. You might run into an occasional RRoD because of the coolrunner interfering with the normal boot process.
LOL no what I meant was trying to boot but no success.
 
Yes I do have my cpu key but as for using stock 14719 or 14717 I do not have. Thats why I have to use 13604 because its the only stock nand I have. I took the official update online from M$ from 14699 to 14717 and deleted the stock nand by accident. Im thinking that the jump from 13604 to creating a retail nand with the latest version of multibuilder .82 could be the problem. Multibuilder .82 updates the cb from 5771 to 5773 falcon just fine but my console is still not booting. Its either the coolrunner or the newly updated phat cb's needs to be fully decrypted (a bug or somewhat). They way it looks I might have to wait for another update or the DEMON to be released.

Ah, ok. Now I'm on the same page.

I was thinking that everything was a-ok, but I got lost out in limbo.

I apologize for shooting all these things at you without really helping.

Do you have pictures of your installment?

Again, didn't mean to ramble on about what you already know.

With the new CB change, I am not that resourceful with answers.

I'm signing off for the night, but I'll see what I can find tomorrow.

The more educated guys will chime in sometime too.
 

ball00

VIP Member
Nov 8, 2011
632
0
France
Yep looks like you'll have to wait until the new tools arrive with the correct cb for your board. Luckily for you the announcement came last night for their release. You wont have to wait long!!
 

jayfig

VIP Member
Oct 29, 2010
314
0
North Carolina
Well im a bit puzzled myself with this new problem I have with the cb change but I know it cant be my wiring because RGH worked on the previous dash.

---------- Post added at 08:40 ---------- Previous post was at 08:35 ----------

Yep looks like you'll have to wait until the new tools arrive with the correct cb for your board. Luckily for you the announcement came last night for their release. You wont have to wait long!!
The new decrypted cb's are already out though. Multibuilder .82 and jrunner automatically downloaded them. I was able to make a 5773 cb nand image. I even bumped up my ldv from 17 to 18 and it still doesnt boot. I really dont feel like opening my box and removing my coolrunner just to see if it will boot with out it.
 

ball00

VIP Member
Nov 8, 2011
632
0
France
Sorry I posted above having read only page 1 of the thread.

I'll get my coat!!

---------- Post added at 14:49 ---------- Previous post was at 14:46 ----------

Might be being stupid here but are you trying to boot retail nand with the coolrunner on. If so it won't boot. Not since 14717. Coolrunner has to be off.
 

jayfig

VIP Member
Oct 29, 2010
314
0
North Carolina
Sorry I posted above having read only page 1 of the thread.

I'll get my coat!!

---------- Post added at 14:49 ---------- Previous post was at 14:46 ----------

Might be being stupid here but are you trying to boot retail nand with the coolrunner on. If so it won't boot. Not since 14717. Coolrunner has to be off.
Thank you so much somebody finally gave me legit answer ill take your advice and see about disabling the coolrunner and see if my console will boot.
 

jayfig

VIP Member
Oct 29, 2010
314
0
North Carolina
Sorry I posted above having read only page 1 of the thread.

I'll get my coat!!

---------- Post added at 14:49 ---------- Previous post was at 14:46 ----------

Might be being stupid here but are you trying to boot retail nand with the coolrunner on. If so it won't boot. Not since 14717. Coolrunner has to be off.
Yup that did it just moved the switch to "Prog" which in case turned it off and it booted right up. Thanks just wanted to make sure that was what I had to do because with my installed blaster its a bitch to open up.
 
Yup that did it just moved the switch to "Prog" which in case turned it off and it booted right up. Thanks just wanted to make sure that was what I had to do because with my installed blaster its a bitch to open up.
Thank you, ball00. :)

I re-read the entire thread and I thought I mentioned turning the coolrunner off. Sorry to keep you hanging on something so simple. :rolleyes2:

That's what I get for being a cabbage head and staying up too late.

Glad it's working now, jayfig.