I'm a technician in a console repair shop. In the console modding business since '09.
We have 3 split CB Jaspers. And there's no way we can glitch them at least once with Matrix II neither with Matrix II Rev. C. We've no other chips to try with.
I've tried nearly everything
-CPU_RST cleaner from TX
-Shielded/unshielded/kynar cables (on CPU_RST)
-different cable lengths (20 to 50 cm gradually)
-Xell built with AutoGG and Jrunner
-Switches in recommended RGH2.0 position and in Slim/Trinity =>this "Hangs" the console after a few pulses - the debug led stops blinking, and the fans produce strange sound.
-The quality of solder points is determined by 3 year experience in electronics repairs. (Iíve soldered using flux, of course).
-the three work fine with original FW before and after I try RGH2.0
-No RROD history on the three.
-2 of them have been refurbished by M$ - split CB on pre 14719 FW.
-One was updated to 14719
-Matrix Glithcer II (with switches) and Rev C. (with crystal).
-Updated to the last version with MTX USB programmer.
-Work fine on Slim/RGH1
-Didn't tried doing RGH2.0 on non-jasper boards yet.
-Using Matrix NAND programmer for NAND dump/flash.
I've used Gui tools (AutoGG and Jrunner) to build ECC for 5 other consoles (slim/rgh1), and had no problems. But some people say using GUI tools for ECC may give problems. Could it be for RGH2.0?
If the ECC image isn't ok, can this affect the HW glitch procedure (while LED blinks)?
Thank you in advance for your replies.
I hope to solve it soon, as the clients are nervous...