Hacking CONFIRMED: No roadblocks for 7.0.1 Support on SXOS

[stephrk398]

They need to consider doing updates like this before an uproar occurs.

 

[Essasetic]

Reinx got nightly builds that support 7.0! Guess what? They used Sept! Come on TX just use it. Stop trying to bypass it.

--------------------- MERGED ---------------------------

hey man i am waiting for your os and it needs to be 7.0.1 compatible eh.. as its so easy to make that there should not be roadblocks... if any other dev of any other os tells you something then you will not think they are credible ? -.-

TX is a business.

--------------------- MERGED ---------------------------

That's already a red flag that they're not a credible source. But I can keep going.

 

[ombus]

the funny thing is that there always people who say sxos steal code and what not... now that ( i think ) they try to make it themself then its actually bad ?

 

[Essasetic]

the funny thing is that there always people who say sxos steal code and what not... now that ( i think ) they try to make it themself then its actually bad ?

They're not making it themselves though. They're trying their best to bypass Sept. It's obvious at this point.

 

[tinkle]

It's obvious at this point

List your credible sources and facts (not speculation, not guessing, not assuming,) that this is 'obvious' please.

 

[Lacius]

the funny thing is that there always people who say sxos steal code and what not... now that ( i think ) they try to make it themself then its actually bad ?

A reason why SX OS hasn't updated to support 7.0.x might be because they weren't able to use public exploits like the one for 6.2.0, since the 7.0.x exploit is still private.

 

[ombus]

They're not making it themselves though. They're trying their best to bypass Sept. It's obvious at this point.

yeah ? source or proof plz, thanks

A reason why SX OS hasn't updated to support 7.0.x might be because they weren't able to use public exploits like the one for 6.2.0, since the 7.0.x exploit is still private.

isnt reinx using sept ? why would sxos not be able to do the same ?

 

[Lacius]

List your credible sources and facts (not speculation, not guessing, not assuming,) that this is 'obvious' please.

yeah ? source or proof plz, thanks

I think he means it would be the obvious thing to do, assuming they're trying to find the path of least resistance to 7.0.x support.

 

[Essasetic]

yeah ? source or proof plz, thanks

Alright. Before Sept dropped SX OS got it's firmware updates usually 1-2 weeks after Atmosphere. This has stopped since Sept has dropped.

--------------------- MERGED ---------------------------

List your credible sources and facts (not speculation, not guessing, not assuming,) that this is 'obvious' please.

 

[smf]

They're not making it themselves though. They're trying their best to bypass Sept. It's obvious at this point.

You don't make sense, if they bypass sept then they have to make it themselves.

Alright. Before Sept dropped SX OS got it's firmware updates usually 1-2 weeks after Atmosphere. This has stopped since Sept has dropped.

That doesn't prove anything yet.

 

[Essasetic]

That's literally all the proof I need to know something is up.

 

[ombus]

Alright. Before Sept dropped SX OS got it's firmware updates usually 1-2 weeks after Atmosphere. This has stopped since Sept has dropped.

--------------------- MERGED ---------------------------

again.. they could be trying to break tsec and not sept.. you didint provide any proof of this.

 

[Essasetic]

You don't make sense, if they bypass sept then they have to make it themselves.

Exactly. There is no point of trying to bypass it. They just haven't realised yet

--------------------- MERGED ---------------------------

again.. they could be trying to break tsec and not sept.. you didint provide any proof of this.

Have you literally ever seen them trying to break TSEC? They haven't mentioned it even once on their changelogs or their site.

 

[smf]

Exactly. There is no point of trying to bypass it. They just haven't realised yet

What do you mean there is no point in bypassing it?

You appear to be extrapolating a lot of things from pretty much nothing.

Have you literally ever seen them trying to break TSEC? They haven't mentioned it even once on their changelogs or their site.

They haven't mentioned eating, taking a shit, sleep etc either. What is your point?

 

[Lacius]

Alright. Before Sept dropped SX OS got it's firmware updates usually 1-2 weeks after Atmosphere. This has stopped since Sept has dropped.

The main reason for the delay is that TX would have to break TSEC to get 7.0.x support. Now that sept is out, I would think it would be the path of least resistance, but it's odd they haven't used it. It leads me to believe that either:

1. They don't plan on updating SX OS to support 7.0.x.
2. The Atmosphere logo would be too damaging to their business model that necessitates ignorance of free custom firmwares.

 

[Essasetic]

What do you mean there is no point in bypassing it?

You appear to be extrapolating a lot of things from pretty much nothing.

There's no point in bypassing it because it's impossible. It's locked behind keys and the method to generate said keys is private.

 

[ombus]

The main reason for the delay is that TX would have to break TSEC to get 7.0.x support. Now that sept is out, I would think it would be the path of least resistance, but it's odd they haven't used it. It leads me to believe that either:

1. They don't plan on updating SX OS to support 7.0.x.
2. The Atmosphere logo would be too damaging to their business model that necessitates ignorance of free custom firmwares.

literally the thing one do is search cfw nintendo switch.. its not hard to see free cfw ...

 

[Essasetic]

The main reason for the delay is that TX would have to break TSEC to get 7.0.x support. Now that sept is out, I would think it would be the path of least resistance, but it's odd they haven't used it. It leads me to believe that either:

1. They don't plan on updating SX OS to support 7.0.x.
2. The Atmosphere logo would be too damaging to their business model that necessitates ignorance of free custom firmwares.

Let's also mention that none of the members of their team can even come close to breaking TSEC. So that's out of the question.

 

[smf]

There's no point in bypassing it because it's impossible. It's locked behind keys and the method to do so is private.

Sounds like circular reasoning to me. You're assuming TX can't do it because you think TX can't do it.

Maybe you're right, maybe you're wrong. It just makes you sound arrogant.

Let's also mention that none of the members of their team can even come close to breaking TSEC. So that's out of the question.

You know them personally?

 

[Essasetic]

Sounds like circular reasoning to me. You're assuming TX can't do it because you think TX can't do it.

Maybe you're right, maybe you're wrong. It just makes you sound arrogant.

The fuck you on about? Nobody can do it because the method to bypass it is closed source. End of story.

 

[ombus]

Let's also mention that none of the members of their team can even come close to breaking TSEC. So that's out of the question.

lets also mention that none of the members of atmosphere comes close to make xci loading, hdd or emunand... see this is just fanboy.. people use the cfw they like for the features it has .. stop this.

The fuck you on about? Nobody can do it because the method to bypass it is closed source. End of story.

by that logic nobody should have hacked the switch as is closed source. -.-