FIXED Demon Help - Weird things going on!

jia1000

VIP Member
May 20, 2012
210
0
Essex
Hi Guys,

I installed a demon in my trinity about 8 weeks and all has been fine up until yesterday when my son booted the glitch nand.

On the glitch nand i have it boot straight into FSD but yesterday it booted as if i had just bought a brand new console? it came up with a tutorial on how to use the xbox and then proceeded to calibrate the Kinect camera. My son switched the console off and then booted retail nand no problem, then when he tried to boot the glitch nand we got a e79 or e74 error, cant remember which one it was.

So ive just got home from work, plugged my trinity into my laptop via the micro usb cable, started j-runner (admin) and read my stock nand so i could create a new glitch image. 1st read of the nand was fine but 2nd read of the nand it came with an error, i heard "Oh No" and then before i could take note of the error my laptop crashed??? WTF

I then tried to boot my console stock nand and the fans just sped up, no boot!... the same on the glitch nand too. So i connected up the micro usb cable and proceeded to write my original nanddump with jrunner and i got "manufacturer for code AA not found" twice. At this point im thinking some weird fookin shizzle is going on here!! I unplugged the micro usb from the xbox and laptop and re-plugged it back in and wrote my original nand fine.

When i create a glitch image and try and write it to the demon nand i get "manufacturer for code BD not found". Ive tried re-plugging in the micro usb cable but i still get "manufacturer for code BD not found".

Just wondered if anyone had an idea what this could be before i take it apart and take some pics.

Thanks

J-Runner log below


===================================================
24 August 2012 16:26:15

J-Runner v0.2 Beta (279) Started



Checking Files
Finished Checking Files
Initializing Nand..
Nand Initialization Finished
Current: DemoN
Switching to XBOX
Success
XBOX360
manufacturer for code AA not found

XBOX360
manufacturer for code AA not found

Initializing Nand..
Nand Initialization Finished
XBOX360
Hardware : Demon Slim
Firmware : 1.0
Flash ID : 0x7320 ST Micro (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Writing Nand
Done!
in 0:33 min:sec

Load Files Initiliazation Finished
15574
Started Creation of the 15574 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.04.515
---------------------------------------------------------------
building glitch2 image
---------------------------------------------------------------
C:\Users\Spunky\Desktop\RGH Tools\J-Runner v02 (275) Core Pack\150160113009\updflash.bin image built, info:
---------------------------------------------------------------
Console : Trinity
NAND size : 16MiB
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 150160113009
ConsoleId : 320573430063
MoboSerial: 9948652201011309
Mfg Date : 07/22/2011
CPU Key : BCABCDF42C03FCA2D9587901CCED901B
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 7A91EB08FA56C9A90FCA812836C0B566
CF LDV : 4
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Saved to C:\Users\Spunky\Desktop\RGH Tools\J-Runner v02 (275) Core Pack\150160113009
Image is Ready
Current: XBOX
Switching to DemoN
Success
DEMON
manufacturer for code BD not found

Load Files Initiliazation Finished
15574
Started Creation of the 15574 xebuild image
KV Info saved to file
Load Files Initiliazation Finished
The Creation of the xebuild image has already started, Don't rush me!
---------------------------------------------------------------
xeBuild v1.04.515
---------------------------------------------------------------
building glitch2 image
---------------------------------------------------------------
C:\Users\Spunky\Desktop\RGH Tools\J-Runner v02 (275) Core Pack\150160113009\updflash.bin image built, info:
---------------------------------------------------------------
Console : Trinity
NAND size : 16MiB
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 150160113009
ConsoleId : 320573430063
MoboSerial: 9948652201011309
Mfg Date : 07/22/2011
CPU Key : BCABCDF42C03FCA2D9587901CCED901B
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 7A91EB08FA56C9A90FCA812836C0B566
CF LDV : 4
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Saved to C:\Users\Spunky\Desktop\RGH Tools\J-Runner v02 (275) Core Pack\150160113009
Image is Ready
DEMON
manufacturer for code BD not found

Initializing Nand..
CpuKey is Correct
Key already Exists
Nand Initialization Finished
Load Files Initiliazation Finished
15574
Started Creation of the 15574 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.04.515
---------------------------------------------------------------
building glitch2 image
---------------------------------------------------------------
C:\Users\Spunky\Desktop\RGH Tools\J-Runner v02 (275) Core Pack\150160113009\updflash.bin image built, info:
---------------------------------------------------------------
Console : Trinity
NAND size : 16MiB
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 150160113009
ConsoleId : 320573430063
MoboSerial: 9948652201011309
Mfg Date : 07/22/2011
CPU Key : BCABCDF42C03FCA2D9587901CCED901B
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 7A91EB08FA56C9A90FCA812836C0B566
CF LDV : 4
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Saved to C:\Users\Spunky\Desktop\RGH Tools\J-Runner v02 (275) Core Pack\150160113009
Image is Ready
DEMON
manufacturer for code BD not found

DEMON
manufacturer for code BD not found

Initializing Nand..
Nand Initialization Finished
Load Files Initiliazation Finished
15574
Started Creation of the 15574 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.04.515
---------------------------------------------------------------
building glitch image
---------------------------------------------------------------
C:\Users\Spunky\Desktop\RGH Tools\J-Runner v02 (275) Core Pack\150160113009\updflash.bin image built, info:
---------------------------------------------------------------
Console : Trinity
NAND size : 16MiB
Build : Glitch
Xell : power on console with console eject button
Serial : 150160113009
ConsoleId : 320573430063
MoboSerial: 9948652201011309
Mfg Date : 07/22/2011
CPU Key : BCABCDF42C03FCA2D9587901CCED901B
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 7A91EB08FA56C9A90FCA812836C0B566
CF LDV : 4
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Saved to C:\Users\Spunky\Desktop\RGH Tools\J-Runner v02 (275) Core Pack\150160113009
Image is Ready
DEMON
manufacturer for code BD not found

DEMON
manufacturer for code BD not found

DEMON
manufacturer for code BD not found

DEMON
manufacturer for code BD not found

DEMON
manufacturer for code BD not found

Load Files Initiliazation Finished
15574
Started Creation of the 15574 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.04.515
---------------------------------------------------------------
building glitch2 image
---------------------------------------------------------------
C:\Users\Spunky\Desktop\RGH Tools\J-Runner v02 (275) Core Pack\150160113009\updflash.bin image built, info:
---------------------------------------------------------------
Console : Trinity
NAND size : 16MiB
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 150160113009
ConsoleId : 320573430063
MoboSerial: 9948652201011309
Mfg Date : 07/22/2011
CPU Key : BCABCDF42C03FCA2D9587901CCED901B
1BL Key : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key : 7A91EB08FA56C9A90FCA812836C0B566
CF LDV : 4
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Saved to C:\Users\Spunky\Desktop\RGH Tools\J-Runner v02 (275) Core Pack\150160113009
Image is Ready
DEMON
manufacturer for code BD not found
 

jia1000

VIP Member
May 20, 2012
210
0
Essex
I'm assuming you tried re-installing the DemoN drivers?

Ensure the ribbon cable is correctly and firmly connected.
Yes ive checked the ribbon seating but havent re-installed the drivers as demon toolbox wont start on my laptop, some dll error. Ill try re-installing the drivers my neighbours pc. Thanks for your help BL4K3Y
 

jia1000

VIP Member
May 20, 2012
210
0
Essex
Tick the box at the end of the installer.
Installed drivers and demon toolbox, then went to flash updflash.bin with demon toolbox but got this error:

ERROR: Unknown NAND-flash device id 0xBD73 reported.
Please verify correct installation!


So time to take her apart dont you think?
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
It's going to be a solder issue. Error BD etc is the DemoN not able to get the ID from the chip.

Pics will probably show some 'interesting' soldering.
 
  • Like
Reactions: jia1000

jia1000

VIP Member
May 20, 2012
210
0
Essex
It's going to be a solder issue. Error BD etc is the DemoN not able to get the ID from the chip.

Pics will probably show some 'interesting' soldering.
Ok so i took the console apart and found the light blue wire (No1 Wire on the TX Diagram) from the demon had come away from the mobo. So i applied some flux and re-soldered it but i still have the same problem "Error BD etc"

Anyway i made the mistake of putting the whole xbox back together before trying it as i was convinced the the light blue wire was my problem. So im gonna re-do all my soldering tommorow after work as i have a early start in the morning but would that wire cause such a error?
 

jia1000

VIP Member
May 20, 2012
210
0
Essex
Finally managed to to take my xbox apart and look at the demon qsb points. Couldnt see anything wrong after using a magnifying lens but re-soldered the qsb points for a peace of mind and..... Woohoooo i can now right to the demon!!!

Cheers for your help guys, thanked for the support.

Can some one sign this off as "Fixed"
 

BL4K3Y

VIP Member
Jul 7, 2010
13,721
118
Colne, Lancashire (UK)
Finally managed to to take my xbox apart and look at the demon qsb points. Couldnt see anything wrong after using a magnifying lens but re-soldered the qsb points for a peace of mind and..... Woohoooo i can now right to the demon!!!

Cheers for your help guys, thanked for the support.

Can some one sign this off as "Fixed"
Done.

I'm glad you got if fixed, but for future reference, a visual inspection isn't always enough - having a multimeter to hand is essential when working with electronics.