DGX debug light stop after 5-6 blinks on CORONA v1

tripod731

tripod731

BANNED
Jul 9, 2010
20
0
Bulgaria Black Sea
Hi, guys!
That is not my first DGX-ed xbox360, also i'm not noob in soldering skil...... but:

My last xbox360 goin' me crasy.
Different cable solder points on post_out & cpu_rst and lenghts but with no success.Stop blink after 5-6 blinks. Tried post_out adaptor too- same. I used alt corona 16MB.ecc file. Only NOT tried 70-120cm long post_out wire. HDMI cable hooked . LAN cable too. But reffuse to boot xell.
And finally i'm goin' to think my only sollution is 5kg hammer and 5 gunshots in the air.
 
Last edited:
tripod731

tripod731

BANNED
Jul 9, 2010
20
0
Bulgaria Black Sea
Just to mention after 6 hours fight with non-glitchin' box i leave it and glitched another corona v2, but after 2 cold resets, because my DGX stop blinking again. But finally second box is done.
I'm goin to think that my DGX not function properly.
 
Antalpromille

Antalpromille

VIP Member
Aug 4, 2011
3,146
0
Borås, sweden
tripod731 said:
OK, but how many modified ECCs are out? I used corona 16MB v2.ecc. Is there another modified?
Click to expand...
Sorry, my bad. Same problem with original and alternative ECC? You should still try the comms-cable and post what it posts, so we can see what happens.
 
tripod731

tripod731

BANNED
Jul 9, 2010
20
0
Bulgaria Black Sea
HDMI cable is connected to both sides - xbox360 and TV. Time intervals is not right 5sec, but 3, then 7, then 5...... damn.... even 30sec silence and then blink....

Pos_Out lenght is approx. 1m. I used upper side on mobo alt point under the cooler and now ause the same point.
CPU_RST is 8cm.

No LUCK!!!
 
Last edited:
M

MrOzzySan

Junior Member
Feb 1, 2012
17
0
For me the solution was, using the yellow cable(post out) on the D point (CPU RST) and the blue cable(CPU RST) on the C point(post out), console glitched on the first try.

PS. i had no av / hdmi cable connected, only the comms cable + power supply and i ran the blue cable around the fan. (i also turned off my soldering iron)
 
Last edited:
tripod731

tripod731

BANNED
Jul 9, 2010
20
0
Bulgaria Black Sea
I never used before monitor com usb cable (included in NAND-X package). Just set COM port to 4 regarding from my PC settings. But there is no info shown there.

I'm goin to glitch next corona tomorow,


Forgot to mention:

• Bad Block ID @ 0x5D Found @ 0x3FF[Offset: 0x107BE00]
• Bad Block ID @ 0x17B Found @ 0x3FE[Offset: 0x1077C00]
• Bad Block ID @ 0x221 Found @ 0x3FD[Offset: 0x1073A00]
• Bad Block ID @ 0x256 Found @ 0x3FC[Offset: 0x106F800]
• Bad Block ID @ 0x2A3 Found @ 0x3FB[Offset: 0x106B600]
• Bad Block ID @ 0x2E2 Found @ 0x3FA[Offset: 0x1067400]
• Bad Block ID @ 0x31E Found @ 0x3F9[Offset: 0x1063200]

I doubt that the problem is there.
 
Last edited:
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
tripod731 said:
I never used before monitor com usb cable (included in NAND-X package). Just set COM port to 4 regarding from my PC settings. But there is no info shown there.
Click to expand...
Is COM4 what's been assigned in Device Manager?
 
tripod731

tripod731

BANNED
Jul 9, 2010
20
0
Bulgaria Black Sea
COM4 is. Do I have to change other values on monCOM?

Forgot to mention:

• Bad Block ID @ 0x5D Found @ 0x3FF[Offset: 0x107BE00]
• Bad Block ID @ 0x17B Found @ 0x3FE[Offset: 0x1077C00]
• Bad Block ID @ 0x221 Found @ 0x3FD[Offset: 0x1073A00]
• Bad Block ID @ 0x256 Found @ 0x3FC[Offset: 0x106F800]
• Bad Block ID @ 0x2A3 Found @ 0x3FB[Offset: 0x106B600]
• Bad Block ID @ 0x2E2 Found @ 0x3FA[Offset: 0x1067400]
• Bad Block ID @ 0x31E Found @ 0x3F9[Offset: 0x1063200]

I doubt that the problem is there.


I read that tingedace have same problem and already solved. I'll try the ame trick with kynar wire.
 
Last edited:
You must log in or register to reply here.