I see.Well the original reset glitch hack for the xbox 360 required a glitcher chip
this was the case up until very recently when some Russian discovered a way to use the consoles own hardware to glitch the console instead of using TX's RGH chip or a clone glitcher chip
this is a really new concept.
It may also be relevant to the switch because it also uses a glitcher chip from TX( or "HWFLY" TX incognito?)
so this new idea of using a consoles own hardware to perform the glitching instead of a separate chip
might be able to be applied to the switch as well.
but like I said it would only have the benefit of not requiring you to purchase an expensive chip
and possibly make for a simpler hard mod procedure, it would not make any other difference
or lead to new exploits,
Also very likely that has not been looked into yet for the mariko switch models
or it could have been by TX but even if were discovered by TX they would probably have kept it secret to sell their chip
or maybe not since they could probably have come up with a different business model selling NAND reader/flashers or chip clips if such a thing would be required
I did some quick research on glitching and the XB 360 and Tegra CPUs. Glitching seems to involve futzing with the CPU voltage at the right moment to get unintended things to happen. This usually involves an external device that can fiddle with the voltage, check for success, reset if needed, and finally do something after success.
In the case of the XB 360 it was discovered that the CPU did not fully reset if the reset signal was only received momentarily. My guess is that they figured out a way to signal this reset very precisely and allow unsigned code execution reliably and repeatedly.
In the case of the Tegra CPUs, it appears to be using the glitch, test, reset loop until successful and finally executing the unsigned code. I'm also taking a guess that this is what happens repeatedly during the modchip training so that it learns roughly when to glitch for it to be successful. I have no idea what it is testing for though. The unsigned code is obviously hekate and atmosphere. This is why the modchip is needed and I seriously doubt it would be possible to have the console perform the glitch, test, reset loop let alone injecting and executing unsigned code after. Obviously the timing and success condition are the secret sauce of the TX and HWFLY chips. If that gets released then we can indeed create own modchips for a fraction of the current cost.
Last edited by l7777,