- Feb 3, 2012
- 80
- 0
I just installed a demon and cr rev c to a trinity mobo. I went to power on and I get a beep and that is it. I switched nands and I get the same. I re-seated all 4 ends of the ribbon cables and double checked all my solder joints (not with my multi-meter yet). I am going to post pics for you guys in a min. I was reading the xbox nand through the demon, and got a wrong header message but it finished, then I read the demon nand and it reported a bunch of bad blocks? I am going to erase it and make a new image, then re write it to the demon nand. here is the jr log:
===================================================
Monday, January 07, 2013 4:43:07 PM
J-Runner v0.2 Beta (284) Started
All the best for 2013 - from Team JR!
Checking Files
Finished Checking Files
Current: DemoN
Switching to XBOX
Success
Reading Nand to C:\Users\spikie\Desktop\business\extreme electronics\modding\xbox360\rgh\J-Runner v02 (275) Core Pack\output\nanddump1.bin
XBOX360
Hardware : Demon Slim
Firmware : 1.0
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Reading Nand
Done!
in 0:26 min:sec
Reading Nand to C:\Users\spikie\Desktop\business\extreme electronics\modding\xbox360\rgh\J-Runner v02 (275) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Reading Nand
Header is wrong..
Done!
in 0:25 min:sec
Comparing...
Can't check for bad blocks. No Spare data. Possibly Corona 4GB
Can't check for bad blocks. No Spare data. Possibly Corona 4GB
Nands are the same
Current: XBOX
Switching to DemoN
Success
Reading Nand to C:\Users\spikie\Desktop\business\extreme electronics\modding\xbox360\rgh\J-Runner v02 (275) Core Pack\output\nanddump1.bin
DEMON
Hardware : Demon Slim
Firmware : 1.0
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Invalid Blocks : 0xD6 0xD7 0xD8 0xD9
Reading Nand
Done!
in 0:25 min:sec
Reading Nand to C:\Users\spikie\Desktop\business\extreme electronics\modding\xbox360\rgh\J-Runner v02 (275) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Nand Initialization Finished
Reading Nand
Done!
in 0:24 min:sec
Comparing...
Bad Block ID @ 0x00D6 [Offset: 0x372C00]
Bad Block ID @ 0x00D7 [Offset: 0x376E00]
Bad Block ID @ 0x00D8 [Offset: 0x37B000]
Bad Block ID @ 0x00D9 [Offset: 0x37F200]
Bad Block ID @ 0x00D6 [Offset: 0x372C00]
Bad Block ID @ 0x00D7 [Offset: 0x376E00]
Bad Block ID @ 0x00D8 [Offset: 0x37B000]
Bad Block ID @ 0x00D9 [Offset: 0x37F200]
Nands are the same
------------------------------------------
is this a common problem? I didn't seem to see anything in the first 3 pages of the demon support area...
===================================================
Monday, January 07, 2013 4:43:07 PM
J-Runner v0.2 Beta (284) Started
All the best for 2013 - from Team JR!
Checking Files
Finished Checking Files
Current: DemoN
Switching to XBOX
Success
Reading Nand to C:\Users\spikie\Desktop\business\extreme electronics\modding\xbox360\rgh\J-Runner v02 (275) Core Pack\output\nanddump1.bin
XBOX360
Hardware : Demon Slim
Firmware : 1.0
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Reading Nand
Done!
in 0:26 min:sec
Reading Nand to C:\Users\spikie\Desktop\business\extreme electronics\modding\xbox360\rgh\J-Runner v02 (275) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Reading Nand
Header is wrong..
Done!
in 0:25 min:sec
Comparing...
Can't check for bad blocks. No Spare data. Possibly Corona 4GB
Can't check for bad blocks. No Spare data. Possibly Corona 4GB
Nands are the same
Current: XBOX
Switching to DemoN
Success
Reading Nand to C:\Users\spikie\Desktop\business\extreme electronics\modding\xbox360\rgh\J-Runner v02 (275) Core Pack\output\nanddump1.bin
DEMON
Hardware : Demon Slim
Firmware : 1.0
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Invalid Blocks : 0xD6 0xD7 0xD8 0xD9
Reading Nand
Done!
in 0:25 min:sec
Reading Nand to C:\Users\spikie\Desktop\business\extreme electronics\modding\xbox360\rgh\J-Runner v02 (275) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Nand Initialization Finished
Reading Nand
Done!
in 0:24 min:sec
Comparing...
Bad Block ID @ 0x00D6 [Offset: 0x372C00]
Bad Block ID @ 0x00D7 [Offset: 0x376E00]
Bad Block ID @ 0x00D8 [Offset: 0x37B000]
Bad Block ID @ 0x00D9 [Offset: 0x37F200]
Bad Block ID @ 0x00D6 [Offset: 0x372C00]
Bad Block ID @ 0x00D7 [Offset: 0x376E00]
Bad Block ID @ 0x00D8 [Offset: 0x37B000]
Bad Block ID @ 0x00D9 [Offset: 0x37F200]
Nands are the same
------------------------------------------
is this a common problem? I didn't seem to see anything in the first 3 pages of the demon support area...