I erased my boot.dat file from team executer :-( help please

[MarieParis]

Hello everyone
I erased my Team Executer boot.dat file from my switch card (error on my side), and i can't find any on the web. Could someone send me the file please ?
Thank you so much
Marie

 

[Hayato213]

Don't think if we can share boot.dat and sxos.bin here since it has copyright stuffs on them.

 

[MarieParis]

Don't think if we can share boot.dat and sxos.bin here since it has copyright stuffs on them.

got it thanks. But is there a way to find it please :-)

 

[Reploid]

got it thanks. But is there a way to find it please :-)

I'm sure it's not that rare if you'll google hard enough.

 

[Hayato213]

got it thanks. But is there a way to find it please :-)

Google would be your friend

 

[The Catboy]

An easier solution would be upgrading to Atmosphere
https://nh-server.github.io/switch-guide/

 

[SylverReZ]

SX OS has never been updated for years. The team has also been disbanded following the arrests of one of their members, so I doubt that we'll see an update any time soon. Atmosphere is nowadays a modern solution as previously mentioned.

 

[mrdude]

Internet Archive - (google it). In the search box type SXOS, and see what turns up.

 

[SylverReZ]

Internet Archive - (google it). In the search box type SXOS, and see what turns up.

To my knowledge, v3.1.0 BETA is the latest.

 

[mrdude]

To my knowledge, v3.1.0 BETA is the latest.

SX_OS_v3.1.0 - yes that's correct, there's no more public versions after that version.

 

[Hayato213]

An easier solution would be upgrading to Atmosphere
https://nh-server.github.io/switch-guide/

Have a switch sitting at 11.0.0 SX OS emunand lol

 

[SylverReZ]

One risk when using SX OS is that you can brick your console. The developers, one of whom supposedly worked for Gateway (not very surprised at all), implemented bricking code into their SX OS firmware to prevent pirates from modifiying it for their fake SX OS clones, which will wipe the entire NAND, turning your Switch into an expensive paperweight; this can also happen if, for example, the firmware files weren't copied over to the SD card properly.

 

[Hayato213]

One risk when using SX OS is that you can brick your console. The developers, one of whom supposedly worked for Gateway (not very surprised at all), implemented bricking code into their SX OS firmware to prevent pirates from modifiying it for their fake SX OS clones, which will wipe the entire NAND, turning your Switch into an expensive paperweight; this can also happen if, for example, the firmware files weren't copied over to the SD card properly.

I remember this

 

[Hayato213]

Found this leaked image on Reddit showing the developers discussing in the SX OS Discord about implementing bricking code into their firmware.

*modsnip*

Thread 'SX OS contains brick code!' https://gbatemp.net/threads/sx-os-contains-brick-code.508800/

 

[SylverReZ]

Thread 'SX OS contains brick code!' https://gbatemp.net/threads/sx-os-contains-brick-code.508800/

Did they by any chance remove it in the later firmwares, or were they so dickish infact that they kept it in?

 

[Hayato213]

Did they by any chance remove it in the later firmwares, or were they so dickish infact that they kept it in?

I assume it is still in the version 3.1.0.

 

[SylverReZ]

I assume it is still in the version 3.1.0.

Okay, thanks.

 

[Hayato213]

Okay, thanks.

As long you have a legit license you should be fine. The license is tied to motherboard.

 

[raging_chaos]

It's still there but the only risk was to other hackers that might want to sell their own clones. They themselves even admitted that anyone knowledgeable enough to dig in that deep into the binary would also know how to retrieve the password and remove the brick, it was just meant to be a speed bump. It's not something a regular user would ever encounter on their own, so no need to devolve this thread into fearmongering like every other SXOS thread that pops up. The horse is dead and turned to dust already so no need to keep trying to beat it.

“We can detect malicious tampering with 100 percent accuracy and have a harmless cat-and-mouse game between aspiring hackers and competing teams that (amongst other things) simply puts a reversible [password] on the system. Someone would have to purposefully bypass lots of layers of integrity checking put in place to trigger this condition. This is not something that can happen in regular usage, ever.”

“We do not ‘brick’ any consoles, ever. We do implement inconveniences to safeguard anti-tampering of our SX OS boot file to remain at a competitive advantage. It would simply be bad business to intentionally harm a user’s console"

 

[SylverReZ]

"We do not 'brick' any consoles, ever. It would simply be bad business to intentionally harm a user’s console."

Yeah right, as if they're trying to backpedal those statements away from the whole Gateway scandal.