[japsander]

ok, so i finally got hold of a trinity slim and have ordered the matrix II glitch chip as it is very hard in UK to find a coolrunner supplier that accepts paypal.

sooo....
anyone here used this chip and had any issues?
its been a while since i did my jtag and the RGH seems to be more complicated to me.

im also going to be dumping/flashing over LPT >.<

i am interested more in knowing whether the capacitor that needed replacing for better timings on the previous model still applies to the matrix II and tips on the wire length.

i have no problems in waiting a while for the timings. i hear different tales of between 5 sec and a minute. if it takes a minute or 2 each time i turn it on i can live with that but obviously would like to do it the best way first time so as not to require taking it apart in order to re-program the chip to fine tune the timings

any and all tips appreciated

[CrystalWolf]

This may not be a tip but ask our resident 360 guys over here @pbanj and @BobbyBlunt .

[japsander]

Originally Posted by CrystalWolf This may not be a tip but ask our resident 360 guys over here @pbanj and @BobbyBlunt .

lol, i thought i just had

[Mistawes]

I use xeBuild-GUI-v1.0 which has plenty of options and worked 100% for me. I originally used Bestpig's tool on a couple RGH's and they gave me 0022 errors (using my own SMC.bin with MB 0.6 fixed them). I tried Multibuilder 0.6 for some and then moved onto xeBuild-GUI-v1.0 which I use every time, both worked flawless.

For the majority of the tools available: No CPU key = ecc image, with CPU key = Freeboot (RGH) image.. JTAG images are completely seperate.

I use TX CR's so amn't too familiar with Matrix unfortunately, but since the v2 have a switch, you should be fine, except I think for BB jaspers which need a capacitor.

Once its glitching, you can play around with wire length depending on boot times, each one I've done is different but you don't have to re-flash the glitcher, once it's flashed for your Trinity mobo. CPU_RST (FT4R2) on the back of the mobo is mainly the one you'd need to adjust, anywhere from 35-50cm seems best.

The soldering for LPT is the exact same layout as on phats, so if you've a DIY flasher like I do, it's handy to know it works the same.. The points for the glitcher are "interesting" when trying to avoid shorts, so I don't expose too much wire before tinning/connecting. Clear off any glazing on the points and flux + tin the points before making a connection, definitely helps.

Good luck & have fun!

[pbanj]

coolshrimps jtag tool is really good for doing the rgh, some people have reported better timing from having the cpu_rst wire resting on top of the mobo(less interference)

rogeros multibuilder also works well http://www.ps3hax.net/showthread.php?t=29868
coolshrimps tool has not been updated for the newest dash but it is real noob friendly http://www.jtagtool.co.cc/

[steveo1978]

Originally Posted by pbanj some people have reported better timing from having the cpu_rst wire resting on top of the mobo(less interference)

Yeah thats the only way I do mine. The one time I have ran the wire under the motherboard the 360 would not glitch at all then I moved the wire to the top and it glitched.

Originally Posted by pbanj rogeros multibuilder also works well

Thats the only one I use. Rogero has been busy so he has not updated it to include the newest dashlaunch but that easy to install once the 360 is up and running. I am not sure about coolshrimp but you can have multi-builder install the launch.ini for FreeStyle Dash in the nand so its a little easier to get the 360 up and running once the RGH is done.

[jhax78]

bit off topic but

just a theory
if interference affects glitch times wouldn't a wire that's shielded and grounded provide much better timings?

[japsander]

I have just seen an interesting bit of info about only dumping the first 1mb a few times instead of the whole 16mb in order to cut times and then dump the rest from within xell.

Has anyone tried this as over LPT there are many errors and 1mb can be dumped many times to get a batch that pass compare.

Has anyone done this? I haven't found reports as I guess most have a USB nand Dumper

[Mistawes]

Yeah, that new AutoGG has it built in, but there was always a way to do it:

You dump a load of times using "nandpro lpt: -r2 part_nand.bin" and then when you have a definite match, flash ecc/Xell to dump rest of NAND via http, followed by "nandpro full_nand.bin: -w16 part_nand.bin 0" to join the 2 parts back together. Then use Xell + Rawflash to write the Freeboot image from onboard.

It definitely helps reduce waiting times and errors, well worth it if you're still using LPT (which I am).

[japsander]

Well I give up with LPT.
3 cable rebuilds, short as possible, with/without resistors still takes over 2hrs to dump.
Every dump has thousands of mismatches but no errors in nandpro itself
Even just dumping the first 1mb has thousands lol. I don't know if something is different with slims or my pc has turned psycho.

Either way I've splashed out on nandx. I hate waiting for **** to get delivered