RGH [Demon] Jasper 512 Xbox Won’t Power On

[ONE 2 NV]

TX Product(s) used: Demon, CoolRunner Rev C
Console Type: Jasper
NAND size: 512
Dashboard version: 2.0.16203
CB version: 6754
Screenshot of NAND details from J-Runner:

J-Runner log:

===================================================
Sunday, June 16, 2013 6:40:58 PM


J-Runner v0.2 Beta (289) Started






Checking Files
Finished Checking Files
Initializing updflash.bin..
CpuKey is Correct
Key already Exists
Nand Initialization Finished
DEMON
Hardware   : Demon Phat
Firmware   : 1.4
Flash ID   : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Invalid Blocks : 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0xA 0xB 0xC 0xD 0xE 0xF 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1A 0x1B 0x1C 0x1D 0x1E 0x1F 0x20 0x21 0x22 0x23 0x24 0x25 0x26 0x27 0x28 0x29 0x2A 0x2B 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 
Writing Nand
Done!
in 0:44 min:sec

Image of Coolrunner/Demon:
http://imgur.com/a/jg8Qq

Images of close-up soldering to motherboard:
http://imgur.com/a/jg8Qq

Description of problem:
First installed CoolRunner, got it to glitch. Then processed to update to 1.4 and test demon, all passed, installed Demon with BB adapter. Erased Demon, wrote 16mb hacked Jasper image. Console will not turn on. Re-seated ribbon cables checked all solder joints. All lights are on.

Was the console working before you started: Y

 

[Martin C]

did you happen to try and write a BB Jasper image to your DemoN the first time?

 

[ONE 2 NV]

did you happen to try and write a BB Jasper image to your DemoN the first time?

Yes I did

 

[Martin C]

When we ask for information, that's what we mean as you didn't mention it until I asked.

Erase the DemoN and re-write the 16MB Jasper image.

 

[ONE 2 NV]

When we ask for information, that's what we mean as you didn't mention it until I asked.

Erase the DemoN and re-write the 16MB Jasper image.

DEMON
Hardware   : Demon Phat
Firmware   : 1.4
Flash ID   : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Erasing Whole Nand
Done!
in 0:00 min:sec


Initializing updflash.bin..
CpuKey is Correct
Key already Exists
Nand Initialization Finished
Load Files Initiliazation Finished
16203
Started Creation of the 16203 xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.07.561
---------------------------------------------------------------
building glitch2 image
---------------------------------------------------------------
C:\Users\ENVY\Desktop\J-Runner v02 Beta (288) Core Pack\170944393305\updflash.bin image built, info:
---------------------------------------------------------------
Console   : Jasper
NAND size : 16MiB
Build     : Glitch (v2)
Xell      : power on console with console eject button
Serial    : 170944393305
ConsoleId : 022278457052
MoboSerial: 705635A208809335
Mfg Date  : 08/13/2009
CPU Key   : 5818A34BFE37418A928FB738B6AEEDB5
1BL Key   : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key   : DDD6B8B8F51C198111397B20F17C7586
CF LDV    : 15
KV type   : type2 (hashed)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\ENVY\Desktop\J-Runner v02 Beta (288) Core Pack\170944393305
Image is Ready
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:43 min:sec

still no power!

 

[Martin C]

Try reading your 360 NAND again.

 

[ONE 2 NV]

Try reading your 360 NAND again.

Reading Nand to C:\Users\ENVY\Desktop\J-Runner v02 Beta (288) Core Pack\output\nanddump1.bin
XBOX360
manufacturer for code FF not found

 

[Martin C]

So there's your problem. You need to fix your soldering.

 

[ONE 2 NV]

So there's your problem. You need to fix your soldering.

any idea what part?

the only part i can think of that mat be causing the problem the D1 Pad and its corresponding point are bridged via the BB upgrade.

 

[skillet34]

My bet would be the stby clk point to the board. (the orange wire B where it connects to the board at r4b24) Lifted or damaged pad/trace.

 

[ONE 2 NV]

My bet would be the stby clk point to the board. (the orange wire B where it connects to the board at r4b24) Lifted or damaged pad/trace.

I completely removed DemoN and everything boots up and glitches, so I don't think the "B" wire is the problem. When i reattach the DemoN and verify that ALL my solder point are good.... no power. I erased the DemoN, flashed a 16mb image, reread the Xbox 66mb Nand. meaning every aspect of what is so posed to happen, is... save for no power!


Also while testing the DemoN with my Multimeter D1, D3, D5 and D7 all register 3.28v-3.3v. While D0, D2, D4 and D6 are nill. Is that right? Should it be like that?

 

[Martin C]

You're checking for continuity between the 360 NAND pins and the DemoN NAND pins. They should all match 1 for 1. You next check for adjacent shorts.

 

[jsinger47]

is it just me, or do you have the 5v wire on the demon going to 3.3v on the console?

EDIT: nevermind, i'm not smart. Please disregard