XeBuild Dash - No Video [TRINITY RGH2 CR4 XL]

barr123

Noob Account
Nov 23, 2014
8
0
Hey Guys,

I managed to fix my blown caps by soldering new ones (and I got retail dashboard working). I got Xell Booting up and got the CPU KEY!

I flashed a 16767 Dashboard to it. Here is J-runner output:

Code:
---------------------------------------------------------------     xeBuild v1.14.693
---------------------------------------------------------------
base path changed to C:\Users\XXXXXXXXXXXXXXX\Downloads\J-Runner v3 (5) Core Pack\J-Runner v3 (5) Core Pack\xeBuild
---- { Image Build Mode } ----
building glitch2 image


---------------------------------------------------------------
C:\Users\XXXXXXXXXXXXXXXX\Downloads\J-Runner v3 (5) Core Pack\J-Runner v3 (5) Core Pack\XXXXXXXXXXXXXXXXXX\updflash.bin image built, info:
---------------------------------------------------------------
Kernel    : 2.0.16767.0
Console   : Trinity
NAND size : 16MiB
Build     : Glitch (v2)
Xell      : power on console with console eject button
Serial    : 21XXXXXXXXX9
ConsoleId : 14XXXXXXX1
MoboSerial: 99XXXXXXXX19
Mfg Date  : 07/30/2011
CPU Key   : EEXXXXXXXXXXXXXXXXXXXXXXB27001
1BL Key   : DDXXXXXXXXXXXXXXXXXXXXXXX63EFA
DVD Key   : DXXXXXXXXXXXXXXXXXXXXXXXXB84D
CF LDV    : 4
KV type   : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\XXXXXXXXXXXXXXXXX\Downloads\J-Runner v3 (5) Core Pack\J-Runner v3 (5) Core Pack\2XXXXXXXXXXXXX9
Image is Ready
Initializing updflash.bin..
Trinity
Nand Initialization Finished
The console boots into Xell perfectly but just shows a black screen when booting to dash. The controller connects to the xbox and shows the first quadrant lit up. The CR4 XL stops glitching the console (No Green debug).

Any Idea what the cause may be?
 

barr123

Noob Account
Nov 23, 2014
8
0
Yes, CR4 option was ticked.

It can boot sometimes, but the logo is covered in artifacts, and games will usually crash as soon as you get into the actual game
 

barr123

Noob Account
Nov 23, 2014
8
0
I ran stock before with no problems. I can boot up to freeboot sometimes, and running dash has no problems from what i've seen so far. Only games and booting is a problem.Xell is fine though.
 

barr123

Noob Account
Nov 23, 2014
8
0
I loaded up 756, flashed it from Xell, first time round, nothing. Flashed again from Xell, console booted twice in a row, started a game and went into the game, game worked fine.

Boot time slow as hell. I'm gonna try booting after 10 minutes.

Whats so special about 756?

No artifacts on startup either, good sign.
 
Last edited:

Krafter

VIP Member
Apr 17, 2011
3,737
118
Indiana
Nothing special. I just wanted to see if it would boot when 16767 wouldn't (at least without problems). It sounds like you gave some tuning to do at this point.
 

Krafter

VIP Member
Apr 17, 2011
3,737
118
Indiana
To be honest, I'm not sure if it supports CR4. I know that there has been an unofficial release of XeBuild with 17*** support but I don't know if JR included that on the last update. Have paid that much attention. Try it and see.
 

barr123

Noob Account
Nov 23, 2014
8
0
Ok, thanks for your help, the console actually boots now every time. Even though boot times aren't instant, i can sort that out at a later date
 

barr123

Noob Account
Nov 23, 2014
8
0
So, i got the latest JRunner, and went to update to 17150, no luck. Getting the same error as first post.

So, decided to go back to 756, but getting the same error as first post again. Xell still boots, but thats about it.