Sorry, but that specific statement from this specific vendor is false.
Call it a sting or bait, I didn't think it would be so easily accepted, but it was effective in unmasking certain aspects of TX affiliates.
This doesn't mean the TX development team can't/won't come up with a solution for Mariko/Lite units. They've certainly been trying to perfect glitch attacks against all Switch hardware in a way to turn them into viable products to sell (e.g.: modchips).
But this particular rumor was purely fabricated and injected into TX's communication stream at a level further away from the actual development team for reasons that don't need elaboration.
Nonetheless, one of two things will happen now:
1) TX does indeed have a real solution and this whole predicament will force them to show/tease it;
2) TX doesn't have an actual solution, but will still show pictures and even video of a Lite unit running their software.
If number 2 happens, they won't tell you it's running on an HDEV unit. These can't just run unsigned code magically, but using something that wasn't found neither by them nor me you can do... interesting stuff. This is enough to provide plenty of convincing "evidence" of a working hack, but is, of course, not compatible with retail units. This also has nothing to do with transferring and dumping the 8.1.1 firmware, by the way.
Looking at this from a technical standpoint, there are a couple of ways the new hardware could be exploited. In case a second vulnerability in T210's bootrom exists (which I'm not confirming nor denying), exploiting patched units could be achieved rather simply without a need for glitch based attacks. However, there's a huge chance the same vulnerability won't work on T214 due to major differences in the bootrom (specifically at the USB stack level in RCM and/or eMMC handling, which are the only 2 parts of the bootrom that can be interacted with to some degree).
On the other hand, a glitch attack developed to target the T210 hardware won't work out of the box on T214 either, because the boot path has changed significantly (backported X2 fused key system, encrypted bootloader, etc.).
In both cases, at least 2 distinct products would be necessary to cover both patched units and Mariko/Lite ones. The method would also be the same for Mariko and Lite since they share the same SoC, contrary to what the rumor implies (that the Lite version is seemingly a separate beta and Mariko has a very advanced, flawless method).
Also, while successfully glitching the new hardware once is enough to decrypt the new BCT and bootloader (and thus get some data to hash and flaunt), it is obviously not enough to get CFW running. The concept of a glitching setup to consistently break the early boot chain is difficult to achieve, but not impossible so TX can very well have done it, just like anyone else could with enough time and money. However, right now this is nothing but a fabricated rumor and, if TX is smart, they will stand by it regardless of the truth.
EDIT: By the way, you can see where the narrative falls apart once you track DNS records for that particular reseller and realize that said reseller and maxconsole are one and the same. Everything after this point is nonsensical since they would have the product themselves, but spinning this as if it was a "trusted reseller" instead, shelters them from any bad PR damage.
Source: MaxConsole
