RGH Phat Demon chip installed on Trinity wont boot

Hooli

Noob Account
May 1, 2015
4
0

Symptoms:
Xbox doesn'tboot Demon or Retail nand. When I power on the Xbox the fan/lights don't come on, I only get the start up sound. If I remove WP, WE, ALE CLE, CE & RE I can boot Xbox nand. (Retail or RGH2) The Xbox nand boots whether the Demon tactile button is switched to Demon or Xbox when WP, WE, ALE CLE, CE & RE are removed. I’ve tried two different phat Demon chips on the same Xbox and I get the same results. I’m using a phat Demonchip because I can’t find anyone that is selling the Slim version.

Install: Before I touched the Demon chip, I installed a Coolrunner Rev C and made sure it was glitching without any problems. So far, no problems. I read the nand twice with Nand-X, wrote ecc & got the cpu key. Xell booted within 3 glitches. I flashed Xbox back to the retail nand and installed the Demon chip. Upgraded the Demon chip to the latest firmware then I flashed it with updflash. Flashed the coolrunner with trinity_en.xsvf I also read the Xbox nand with no problems using the Demon chip. I have no problems reading/writing to the Xbox or to the Demon chip but the Xbox will not bootunless I remove WP, WE, ALE CLE, CE & RE.


20150501-IMG_3866.jpg
20150501-IMG_3881.jpg20150501-IMG_3880.jpg20150501-IMG_3873.jpg20150501-IMG_3867.jpg

Hereis the J-Runner Log:
=========================================================

-Runner v0.3 Beta (7) Started

Checking Files
Finished Checking Files
Checking Console..
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 9231
Trinity
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 9231
Trinity
Reading Nand to C:\Users\Michael\Documents\J-Runner v3 (5) CorePack\output\nanddump1.bin
Reading Nand
Done!
in 3:43 min ec

Reading Nand to C:\Users\Michael\Documents\J-Runner v3 (5) CorePack\output\nanddump2.bin
Initializing nanddump1.bin..
Trinity
Glitch2 Selected
Nand Initialization Finished
Reading Nand
Done!
in 3:43 min ec

Comparing...
Nands are the same
ECC created
Version: 10
Flash Config: 0x00023010
Writing Nand
image_00000000.ecc
Done!
in 0:18 min ec

Getting info from ip 192.168.137.136...
LockDownValue is 5
Initializing nanddump1.bin..
CpuKey is Correct
Added Key to Database
Extracting..
Saving SMC_en.bin
Saving SMC_dec.bin
Saving KV_en.bin
Saving KV_dec.bin
Saving smc_config.bin
Working...
Saving fcrt_en.bin
Saving fcrt_dec.bin
Saving C-R.bin
Saving key.bin
Done
Save location C:\Users\Michael\Documents\J-Runner v3 (5) CorePack\output\Extracts-Trinty Amazon demon
Trinity
Nand Initialization Finished
Moving All files from output folder to C:\Users\Michael\Documents\J-Runner v3(5) Core Pack\************
Retail Selected
Version: 10
Flash Config: 0x00023010
Writing Nand
nanddump1.bin
Done!
in 3:37 min ec

***** Firmware Information *****
Manufacturer: Team Xecuter
Device: DemoN Phat
Version: 1.3
Size: 57344 bytes

Entering bootloader mode.
Programming.
Leaving bootloader mode.
Programming completed successfully!


Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Trinity
Glitch2 Selected
Nand Initialization Finished
Comparing...
Nands are the same
Options.ini file was altered successfully
Use Edited Options Selected
Using edited settings
Load Files Initiliazation Finished
17150
Started Creation of the 17150 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.14.693
---------------------------------------------------------------
base path changed to C:\Users\Michael\Documents\J-Runner v3 (5) CorePack\xeBuild
---- { Image Build Mode } ----
building glitch2 image

---------------------------------------------------------------
C:\Users\Michael\Documents\J-Runner v3 (5) Core Pack\************\updflash.binimage built, info:
---------------------------------------------------------------
Kernel : 2.0.17150.0
Console : Trinity
NAND size : 16MiB
Build : Glitch (v2)
Xell : power on console with console eject button
UART : cygnos/demon speed set
Serial : ************
ConsoleId : ************
MoboSerial: ************
Mfg Date : 03/15/2011
CPU Key : ********************************
1BL Key : ********************************
DVD Key : ********************************
CF LDV : 5
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Use Edited Options de-Selected
Saved to C:\Users\Michael\Documents\J-Runner v3 (5) Core Pack\************
Image is Ready
Initializing updflash.bin..
Trinity
Nand Initialization Finished
DEMON
Hardware : Demon Phat
Firmware : 1.4
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Writing Nand
Done!
in 0:32 min ec

Programming Coolrunner
C:\Users\Michael\Documents\J-Runner v3 (5) CorePack\common\xsvf\trinity_en.xsvf
sending xsvf to demon...
Done

Current: DemoN
Switching to XBOX
Reading Nand to C:\Users\Michael\Documents\J-Runner v3 (5) CorePack\output\nanddump1.bin
XBOX360
Hardware : Demon Phat
Firmware : 1.4
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Reading Nand
Done!
in 0:29 min ec

Initializing nanddump1.bin..
Trinity
==========================================================


Troubleshooting: I took out my multimeter to make sure I didn't accidently bridge any of the wires. I didn't have 30g wire so I just used the wires that come with the coolrunners. I used the same wires on my last Corona phat Demon install and it worked fine. Checked D0 - D7 with multimeter to make sure none of the wires were touching. Checked WP, WE, ALE CLE, CE & RE to make sure none of those wires were touching. Next I checked for continuity between Demon chip and Nand pins on the other side of the board. Touched probeto D0 on Demon and other other probe to the corresponding Nand pin. Did thisf or every point on the Demon chip, everything is connected correctly.

Anyone with experience installing Demon chips have any idea what I'm doing wrong? I've already searched the forums and have read through the tutorials butI haven't seen anyone else with the same problem.
 

Hooli

Noob Account
May 1, 2015
4
0
I removed the CR, wrote the original nand to demon and still no boot.

Checked all connections on Demon. I'm not getting any connection between CE pad and CE Pin on Demon. I'm getting a good connection between every other pad and the corresponding pin on the Demon chip. Is this normal?
 
Last edited:

bruno_rv

VIP Member
Jun 8, 2010
181
0
Croatia
Your clk point is soldered on the wrong side of the resistor.
And your soldering is not so good,you need more flux because you are burning your wires
 
Last edited:

Hooli

Noob Account
May 1, 2015
4
0
That's where I usually solder stby_clk and I never have any problems but I moved it to the other side anyway and still no boot.
 

ablegepu

VIP Member
Jan 3, 2014
925
0
Alabama U.S
Picture is blurry but looks like d4 has a strand touching d5 but not sure. You really need smaller wire preferably solid strand around 32-34 gauge if you could find any. But if nothing else check everything with a multimeter twice maybe three times. If that doesn't work remove all wires start over take your time and strive for perfection. With All the wires on the demon being so close together it needs to be damn near perfect