[Update 6]
if you hear ticking more than once every few secs (i.e. 2-3 times a second) then you Pulled the trace off the circuit (to some extent) from the xbox that hooks up ft4r2 to c5r14 (i think?) and it's not a glitching problem, but a physical problem because the circuit is disconnected.
Here's a picture of a slim that f***ed up. I hooked up he c5r14 pad directly to ft4r2 after pulling off the trace in order to fix it.
http://i43.tinypic.com/4v04k2.jpgbtw all ugly/dodgy $#!t on the mobo is just hotglue that i had to melt to get to ft4r2 again. the board is not burnt, just traces pulled off Tongue
on the same note, im using the pad as an alternate soldering point for the cpu_rst cable from the cpld. it's easier to solder to the pad (after f***ing up the trace and probably even before as well)
[Update 5]
Something I forgot to mention, use stranded wire. 2-3 guys tested solid core with no success and stranded with immediate success. all my tests and instant boot slims used stranded wires
[Update 4]
It's likely that different cplds (homemade/branded) will require different cable length. while each different cpld has not been tested for an optimal length, it seems that the optimal length for matrix glitchers lies between 25-32 cms.
For all other cplds, it is recommended to start off with a 50cm cable, testing and cutting intervals of 1.5-2cm at a time until you get a stable/reliable/consistent boot.
[i'll consolidate test results this evening]
[Update 3]
Looks like tx updated their tx coolrunner thread to adopt similar fix for their slims a few hours
"The Wires bundle to the left is for slim. Includes the 50CM extra length for the CPU_RST line."
Tydye81 reckons 50cm fix need for splicing cable. We haven't tested that yet.
[Update 2]
<rf1911> jasper 16mb
<rf1911> 32cm long wire from cpurst
<rf1911> terminal at the end to dip pin
<rf1911> glitch immediate
<rf1911> cmod schema and gligli schema
Looks like this fix potentially works for phats as well! Others please test and report! Thanks!
[Update]
Every slim we have tested so far has glitched under 10 seconds on average after applying this fix. Even the ones that refused to glitch/stopped glitching showed improvement after trying this. Please post your results after trying this, we still don't fully understand why it works and could use your data.
In addition (or not see test results below) to 270pf capacitor, apply Size Matters Fix (SMF):
Simply Extend the wire that connects ft4r2 to Pad A on matrix to make length of wire between ft4r2 and glitch board/cpld a total of 25-32cm wire! At this point it seems like you need spliced wires (i.e. not one single wire of 28-30 cm but 2 wires connected together adding up to 25-32 cm - most likely something to do with resistance)
(There's a good chance this works with other cpld boards/glitchers and phats - see [Update 2] above)
That's all you need to do!! Boots consistently under 10secs!!
A new fix from the RGloader team
[Tests so far]
Ameel 2x slim - consistently successful using 270pf on matrix glitchers
Gadorach 1x slim - consistently successful using standard 220pf on matrix glitcher
dood 1xslim - consistently successful using matrix glitcher
mustache 1xslim - consistently successful using matrix glitcher
cjack 1xslim -successful using matrix glither
rf1911 1xjasper 16mb - consisently successful using cmod schema and gligli schema
iLLNESS 1xslim - boots better but not as good as others, had to use different cable length, using Seeedstudio/Dangerous Coolrunner
ZerOneX 1xjasper - consistently successful with 8sec average boot
Pacote-san 1xjasper CB6751 - fail
edsondario 1xslim - successful
fireworks 1xjasper16mb 6750 -fail
Pacote-san 1xjasper - successful - 6 consecutive boots to xell withing 2 seconds range using 33cm AWG30
galo911 1xslim - successful 3s to 15s
k0mpresd 1x picky slim - successful
watk 1xslim - consistently successful
morenomdz 1xjasper - fail
Neptune 1xslim - fail
bownsir 1x picky slim - consistently successful under 45s
playonlcd - fail on home-made cpld
xandura 1xslim - success?
rikimaer 2xjasper - fail
ptwitb 1xjasper - fail
eddie1990, 2xslim - fail using 30,32,50 cm on matrix 220pf
pacote-san 1xslim - consistently successful under 15s
ZerOneX 1xjasper - successful using 53cm
morenomdz 1xjasper 256 - successful 50% under 3 secs, 50% up to a minute (100% under a minute??)
pacote-san 1xslim - consistently successful (between instant to 30 secs)
lenselijer - successful between 20-30secs
Foccart 2xslim - successful using 50cm (1st 20-30secs, 2nd instant-10secs)
Ameel 2xslim - successful on matrix using single 40ish cm stranded wire + 270pf
Other people can test as follows:
1. Try similar cable length on other glitchers/cplds and see whether that works and report
2. Try similar cable length on non-slim xbox (i.e phat ones) on cpu_rst
Possible Theory/explanation of fix (offered by tydye):
<tydye81> the length of the wire
<tydye81> the signal sent to reset is 20ns
<tydye81> super small
<tydye81> so when the wire hits the solder joint it reflects
<tydye81> because of such a change in resistance
<tydye81> a little energy does get through, but not a lot
<tydye81> so it takes several tries to get it
<tydye81> sometimes several minutes if at all
<tydye81> if you calculate the waveform of a 20ns signal (50mhz) you come up with a harmonic of 35.2cm
<tydye81> change optimal length to 28
<tydye81> cause I think its gonna vary between boxes
<tydye81> and I think that would be a good middle range
[Original Post]
Hardware: Matrix glitcher with 270pf
SO I did my first slim. Glitches between 5-10seconds consistently.
I did my 2nd slim. Glitches beween 2-5 minutes randomly, and sometimes never (or rather cbf waiting more than 10 mins)
So what's the difference? What's the problem? Took me forever to figure it out - resoldered 100x, tested everything over and over: Length of wires!!!
I changed the wire connecing Ft4r2 from the back of console to A from SHORTEST POSSIBLE LENGTH of wire (~10cm) to ~32cm. Result? Slim now glitches consistently within 20 seconds!!!
Can anyone try this out and see if it works for them?
If that is indeed the FIX, then maybe just a resistor could fix it as well? Anyway, TEST AND REPORT!!
edit:
At this point i dont want to rewire anything and would rather just leave everything as is since it's consistently glitching under 10seconds.
So up to you guys to figure out whether length (resistance) or type of cable (resistance) makes a difference or whether it's length (whether signal bounces as tydye81 suggested) could be the issue.
edit 2: i rewired the extension with the better quality cable, and it boots consistently under 10 secs.
edit 3:
http://i44.tinypic.com/atu6v6.jpghttp://i41.tinypic.com/dy90dt.jpgso i added the extension to test.
total length i tested was between 31.5 and 32.5 and it glitches under 10 seconds consistently.
tydye81 speculates 35.2 is the optimal length.
edit 5:
dood just reported extending the same cable on his slim glitched his xbox within 6secs. he's gonna do more test + cold boot
edit 6:
Gadorach's boot time after fix:
<Gadorach> 11
<Gadorach> 4
<Gadorach> 4
<Gadorach> 4
<Gadorach> 6
<Gadorach> 12
<Gadorach> 3
<Gadorach> 6
<Gadorach> 6
<Gadorach> 14
<Gadorach> 10
<Gadorach> 5
<Gadorach> 5
<Gadorach> 7
« Last Edit: November 04, 2011, 03:47:46 AM by ameel »
(programas, como generó el Xell, que nand donada utilizóal igual que restaurar su nand original.
![[360º]](/images/smilies/nuevos/vueltas.gif "como la niña del exorcista")
si te pido mucho pero nesesito que me pases la nand hackeada que utilizaste para instalarle el RGH en tu jasper (yo tengo el mismo modelo que el tuyo cb6751 jasper 512 mb ) por favor , considera mi situacion , estoy en apuros , no tengo xbox desde el 24 /12/2011 , por el problema de que no me lo han podido instalar RGH , y el lector se le perdio la key la unica manera de extraersela es con RGH , por favor ayudame te doy mil gracias si me haces el favor y te cuento como me va ![[buuuaaaa]](/images/smilies/nuevos/triste_ani3.gif "a lágrima viva")
por favor nesesito a alguien que me heche una mano , disculpa los errores ortogrficos 
![[+furioso]](/images/smilies/nuevos/furioso.gif "muy furioso")
