Corona v4 - infinite Glitch, No Xell,...

[valentin]

Hello, guys. I have a problem with a Corona V4 its a new Xbox 360 Slim E.

The problem is that the Xbox Glitches but its not stoping to glitch. I have resoldered every wire and i have checked all the Cables with a Multimeter. I have tryied 2 alternative CPU_RST points but nothing. I have tryied to take longer wires like 60cm but nothing. The Xbox is glitching but its not booting to Xell. DIP 8 is on.

I have make some Photos but i have a bad Camera. Sorry.



Any ideas what it could be ?

 

[john mathews]

try 3 8 2 8 etc wheres your jr log/ what chip is that

 

[BrockThunderjam]

Your pictures need to be in focus or nobody can help you.


Sent from my iPhone using Tapatalk

 

[valentin]

Thats a DGX v 1.1

Checking Files
Finished Checking Files
Corona 4GB Manually Selected
F:\
Reading from F:\ to C:\Users\PC\Desktop\J-Runner\output\nanddump1.bin
Done!
in 0:04 min:sec
F:\
Initializing nanddump1.bin..
Reading from F:\ to C:\Users\PC\Desktop\J-Runner\output\nanddump2.bin
Corona 4GB
Glitch2 Selected
Nand Initialization Finished
Done!
in 0:04 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
Corona 4GB Manually Selected
Writing to F:\ from C:\Users\PC\Desktop\CORONA_4GB_DGXv2.ecc
Done!
in 0:00:639 min:sec:ms
Corona 4GB Manually Selected
Writing to F:\ from C:\Users\PC\Desktop\J-Runner\common\ECC\CORONA_4GB.ecc
Done!
in 0:00:785 min:sec:ms
Writing to F:\ from C:\Users\PC\Desktop\J-Runner\common\ECC\CORONA_4GB.ecc
Done!
in 0:00:605 min:sec:ms
Tip: Load the nand on source to have quicker results.
Too Many Bad Blocks
Scanning.....
No Xbox Detected
Finished
Connection TimeOut

I have tryied everything.

 

[john mathews]

try the cpu rst under the xclamp/ we need clearer pic take a look at this http://team-xecuter.com/forums/showthread.php?97032-Xecuter-DGX-v1-0S-v1-1s-Install-Guide

 

[valentin]

i have tryied it two times. But nothing. Now i have bridged R2C4 as i have found that it should be vridged but nothing. Just infinite loop of glitches. Sometimes its like its glitching with the sound and a pause between the glitches but sometimes come a glitch and a other immediately after.

 

[john mathews]

look at this

 

[valentin]

I know that i have it bridged. But i found that i shell bridge the R2C4 pad too. So i have bridged it. Now i am on DIP 5 - 8 but without success.

 

[john mathews]

its all about cpu rst length read guide keep trying u will get it just follow guide

 

[valentin]

should it be smaller ?

 

[john mathews]

if I remember when I did it I hat it short as possible cpu rst wire

 

[BrockThunderjam]

You really need to post better pics. That said, measure resistance between point c and ground. If it's not between 60-70k your postfix isn't fitted correctly or is busted.

Cpu_rst length would not prevent it from booting like you've described.

Sent from my iPhone using Tapatalk

 

[valentin]

i have measured it and its about 14 when set to 200K. Is that wrong ?

 

[BrockThunderjam]

Doesn't sound right. Do you have a spare to try?

Set the meter to auto.

Sent from my iPhone using Tapatalk

 

[valentin]

I have a spar part i will try. And i dont have auto on my Multimeter only 2000k, 200k, 20k, 2000, 200.

 

[valentin]

The spare part shows 15 on 200k

 

[BrockThunderjam]

Take clear focused pics of the postfix and where you're soldering to and where you're measuring between. Still doesn't sound right

Try to measure on 20k and see what you get.

Sent from my iPhone using Tapatalk

 

[valentin]

I am measuring on the C pad and Ground on the DGX.

 

[BrockThunderjam]

So now you're going to take clear pictures of each point you've soldered to, yes?


Sent from my iPhone using Tapatalk

 

[chase]

15 KOhms on postout is ok