Try them all,one by one and see which file is booting your console into dash.I already got Xell to boot with the dynamic timing file. What timing file do you recommend guys. I have flashed the image and cant get it to boot to dash at all.
Demetris,when you say "keep adding bigger resistor values until you find the sweet spot" is that meaning to solder them,one at a time to the "CPU_RST point from starting with a 1k ohm and going up then in resistor value,one at a time or replacing the 22k ohm resistor on the Ace v3 "PLL" solder pad and starting from 1k ohm upwards. ? thanks for that good bit of info though.I will try this on my next Xenon board victim lolThe ones that don't work is because they have a different pulse timing so you need to use various resistance on the rst line to get them to glitch , sometimes with the use of a longer wire or adding a 1k resistor to cpu_rst and keep adding bigger resistor values until you find the sweet spot.
It's not the image it's just how xenon's are. This tutorial isn't meant for building a reliable xenon rgh. The CPUs on xenon's are trash, often times they'll crash before getting a successful glitch which starts the process all over again, sometimes indefinitely. Even if you get it working it's going to die in a very short time because the CPU won't handle being reset glitched but for so long.Left it overnight with the dynamic timing files for like 10h or more but never booted to dash. I started to believe there is something wrong with the image I wrote.
Just because you have one that works doesn't mean they aren't still ****. The first rgh I built was a xenon and It still works too, still **** though. The CPUs crash under the stress from Reset Glitch Hack, unless you know more than Team Xecuter and 15432. If you've got something to say maybe you should learn some respect or stay in your lane little bruh.@ C CeratedSuperior Stop spreading misinformation please. I have several Xenon boards still working fine here.
So you know i have two placed at a public pool in the summer and they work from 8am to 6pm for several years now and they still perform amazing.
Both have the newer gpu heatsinks and added two fans , one over the gpu ext bracket and one behind the cpu heatsink so they work in parallel [ L shape airflow]
Also i have placed 3mm rubbers in the bottom rams so they stay in place and cutted a 3mm rubber pad to fit under both clamps removing the small plastic Microsoft put there as it melds from heat and destroys and flexes the motherboard.
@ B BluesMan67 CPU_RST point not Ace V3. Looks like some of these cpus switching frequencies and such is slower and glitch effect cant kick in so easily because they never were the target audience of glitch hack and they were left untested and un-finetuned
Edit: The only issue with the xenons is the ones with the nichicon capacitors next to the cpu, those are junk and you need to replace them asap or you will get the RROD and you will think is the gpu or cpu lol.
The ones with the rubicons are good to go but have an eye on those capacitors because before you get them they were getting a lot of stress from heat and they might fail in the future, or maybe not
One of the guides I read on it says "instead of acquiring the CPU key using Xell (which would usually cause a Xenon’s CPU to crash, which is why RGH isn’t really viable on Xenons) it can be acquired using a TTL adapter installed onto the glitch chip", so I was under the impression that it was not using Xell. On the two videos I can find showing it on YouTube the key is sent over the COM port almost instantly after powering on, which only really gives the chip one attempt at glitching, which is much quicker than any Xenon would normally boot Xell. One of the videos clearly shows the timing file used was "rgh12_xettl_02.xsvf" which I cannot find in any package of timing files I have. If you have done this before, do you still have the files for it?
UPDATE - Managed to find the files and was able to recover the CPU key from the console I was working on using a Matrix v3. I can confirm that it is a custom ECC file that needs flashing to the NAND, plus some custom timing files and the CPU key was outputted via COM port without the console having to boot into Xell. Tomorrow I'm going to go back to the other three consoles and see if the process works on them too.
Of course, no problem. I've uploaded them here - [Click here to view this link]would you by any chance share that special set (custom ECC and TTL timing files for Matrix)? All links are to dropbox which already expired