Hackinformer Your device needs to transform, we are here to inform
Team Xecuter’s SX OS has been the target of a lot of people in the Switch scene recently. Whether you’re wanting it for completely legitimate reasons or if you think it should be stopped, everyone has an opinion and feeling on the matter. It was recently discovered that Team Xecuter’s product to this day contains code that is open source.
After finding out the hard way that the SX OS has brick code in it designed to punish anyone digging around in their product, hexkyz finally got his answers.
Sneak peak of TX's enterprise-ready filesystem layer totally developed from scratch!
But why does it look so familiar?
"embeddedfs:/titles/%016lx/exefs/main.npdm" 🤔 pic.twitter.com/sHMUi7jT0C— Mike Heskin (@hexkyz) June 28, 2018
But that was just the start. He tweeted out a whole thread. He mentioned that he was more than aware that SX OS had brick code in it as that’s the only real thing you could do to stop someone on the Switch. Hexkyz reassured everyone he knew what he was doing and tweeted out the following thread.
After stripping down all the obfuscation we can now say for sure that the SX OS is made of:
– Custom bootloader to display their main menu;
– Set of kernel + INI1/KIP1 patches to disable signature checking;
– Modified KIP1 Loader.— Mike Heskin (@hexkyz) June 28, 2018
Even the code for talking to their license server uses an open-source crypto library so, yes, there are multiple license violations here. However, none of us expected differently, to be honest.
— Mike Heskin (@hexkyz) June 28, 2018
As for the brick code, I was wrong. Not only it is more destructive than I originally thought (it tries to corrupt boot partitions too), but it's also deployed on *multiple* stages across the boot chain. It is also way more likely to be triggered on accident than expected.
— Mike Heskin (@hexkyz) June 28, 2018
I actually bricked my console again (for science!) and was able to unlock the eMMC with the "WANNA PLAY? :)" password, but I don't recommend anyone to try this unless you are really sure on what you're doing.
— Mike Heskin (@hexkyz) June 28, 2018
Once the full write up comes out, we’ll update this article with that as it will divulge more information on the matter. Maybe TX will do something like what Hyperkin did. Recently Hyperkin was under fire for using emulators without permission and proper licensing. Recently, with their Retron 77, they have full licensing for the device. My hope is that TX is just using this code in the meantime until they create their own full-fledged code. Only time will tell. As always, we’ll keep you updated on both sides of the coin.
If you like the author’s work, follow him on Twitter @V1RACY and don’t forget to enter the weekly giveaways!
And as always, stay tuned here on Hackinformer.com for so much more and follow us on Twitter @Hackinformer
