Hacking TeamXecuter's Official Status Update for 6.2 (12/2/18)

[DaveLister]

My current one is banned , still have 5 more in storage . Just in case. Hurry up kodi ..... laptop fail.

 

[wurstpistole]

I have no idea, I'm playing on dockmode right now with airplane on

Ah, I know why.
If you use the joycons when docked, then airplane mode naturally has to be off for the wireless connection. If you play with a wired controller, then yeah - no connection needed. Airplane mode will stay active, I guess.

 

[thaikhoa]

Ah, I know why.
If you use the joycons when docked, then airplane mode naturally has to be off for the wireless connection. If you play with a wired controller, then yeah - no connection needed. Airplane mode will stay active, I guess.

I turn airplane mode on with bluetooth connectivity on as well (the setting below airplane mode).

 

[JeepX87]

My experience was that airplane mode turned itself off when docking the console and immediately connecting to Wifi. This way I accidentally went online in CFW. And got banned. This was all before SX Stealth mode. Now I don't care anymore, naturally.

That why I don't bother to dock my Switch with CFW, however I deleted the WiFi setting, along with airplane mode.

Sam: I'm running Switch with CFW with airplane mode and it is fuckin awesome.
Sam: I need go to kitchen to cook my dinner so dock Switch in.
Nintendo: Oh wait... I can see that Switch run on CFW.
Nintendo: *evil laughing*
Nintendo: Got Switch's info and knock on BAN button.
Sam: I'm finished with dinner and let go back to OFW.
Sam: Looks like okay and let open eShop.
eShop: Your online is restricted by Nintendo.
Sam: HOLY SHIT!!! I need go to GBAtemp to fill the ban report.
Sam: Fuck to Nintendo.
Nintendo: I won the battle against hackers!!!

 

[SaggyBeans]

Sam: On a plane in 1st class, plugs switch into the dock to play some SSBU.
**Airplane mode turns OFF**
Plane starts going down..
Pilot: mayday!! Mayyyydayy!!
Nintendo: uhhh ohhh!

 

[gnze796]

This is no surprise for anyone who has reversed their boot.dat.
Parts of their security system were based on a custom TSEC payload to hide some keys.
Now with 6.2.0 Nintendo changed how TSEC works and they can no longer use this because it would break compatibility with older firmware.

In other words: it takes so long because they need to make a new obfuscate/security system.
If they would remove it or make it open source, they could release it right now...

This is the best explanation to why it's taking so long for TX to update their CFW. TX will surely release an update "soon" (along with new features probably)

 

[TheZander]

Sam: On a plane in 1st class, plugs switch into the dock to play some SSBU.
**Airplane mode turns OFF**
Plane starts going down..
Pilot: mayday!! Mayyyydayy!!
Nintendo: uhhh ohhh!

what? is this a Simpsons reference?

 

[Dinzy]

I wish they would get their act together. I am bought an SX Pro from my nieces' switch for Xmas and want it to be usable.

 

[g00s3y]

Can't wait for the next banwave when SSBU comes out!

 

[wurstpistole]

I wish they would get their act together. I am bought an SX Pro from my nieces' switch for Xmas and want it to be usable.

It is. Stay on 6.1.
There's no reason at all to go to 6.2 yet

 

[Dinzy]

It is. Stay on 6.1.
There's no reason at all to go to 6.2 yet

It's not my switch and I'm not a time traveler.

 

[wurstpistole]

It's not my switch and I'm not a time traveler.

Welp. Niece's fault to update then I guess

 

[Dinzy]

Welp. Niece's fault to update then I guess

No. It's your fault by turning this into a "do not update preaching session". I just want to have security that they will release the damn update, not hear who's to blame for updating a console. The solution path exists, they will release the thing soon, Xmas is soon. I'd just prefer less uncertainty.

 

[wurstpistole]

No. It's your fault by turning this into a "do not update preaching session". I just want to have security that they will release the damn update, not hear who's to blame for updating a console. The solution path exists, they will release the thing soon, Xmas is soon. I'd just prefer less uncertainty.

Are you reading a different thread or something? At which point did I "turn this into a do not update preaching session"? All I did was say that SX works fine on 6.1

 

[bundat]

I wish they would get their act together. I am bought an SX Pro from my nieces' switch for Xmas and want it to be usable.

Get the SX Gear boot.dat and place it on your SD card.
Then get the latest Atmosphere, and rename the .bin payload to payload.bin, then put it on your SD card.
Then get the sigpatches.

Now you are set up to auto-boot Atmosphere when you stick in the SX Pro dongle, and you should be able to play backup games.

This is one solution you can try to make the dongle "usable".

 

[thaikhoa]

That why I don't bother to dock my Switch with CFW, however I deleted the WiFi setting, along with airplane mode.

Sam: I'm running Switch with CFW with airplane mode and it is fuckin awesome.
Sam: I need go to kitchen to cook my dinner so dock Switch in.
Nintendo: Oh wait... I can see that Switch run on CFW.
Nintendo: *evil laughing*
Nintendo: Got Switch's info and knock on BAN button.
Sam: I'm finished with dinner and let go back to OFW.
Sam: Looks like okay and let open eShop.
eShop: Your online is restricted by Nintendo.
Sam: HOLY SHIT!!! I need go to GBAtemp to fill the ban report.
Sam: Fuck to Nintendo.
Nintendo: I won the battle against hackers!!!

User error could lead to a mess.