Hacking SX OS contains brick code!

[Cava]

So if you not try to crack the SX OS it won't cause brick at all? If yes i guess it's not a big deal then.

 

[cearp]

So if you not try to crack the SX OS it won't cause brick at all?

exactly! this dude understands

no need to worry.

 

[Localhorst86]

Can you explain how we are "unaware of the extent"? Hexkyz has proven all it takes is a simple RCM payload to unlock and rebuild the eMMC.

"still need a 2.0.0 raw nand dump (I had backups of all the important stuff, the rest is just re-encrypt with BIS key and write back)."

Hexkyz was able to recover because he had a backup of his BIS key (to rebuild his NAND). From what I understand, that's the console unique key. You can't get to that once your eMMC is locked so if you don't already have that backed up, it looks like it might not be recoverable entirely on your own (without help from TX - if that is even possible)

 

[Kioku]

"still need a 2.0.0 raw nand dump (I had backups of all the important stuff, the rest is just re-encrypt with BIS key and write back)."

Hexkyz was able to recover because he had a backup of his BIS key. From what I understand, that's the console unique key. You can't get to that once your eMMC is locked so if you don't already have that backed up, it looks like it might not be recoverable entirely on your own (without help from TX - if that is even possible)

Which is why you back all of that up from the get go. We have the tools to do so.

 

[Deleted User]

"still need a 2.0.0 raw nand dump (I had backups of all the important stuff, the rest is just re-encrypt with BIS key and write back)."

Hexkyz was able to recover because he had a backup of his BIS key. From what I understand, that's the console unique key. You can't get to that once your eMMC is locked so if you don't already have that backed up, it looks like it might not be recoverable entirely on your own (without help from TX - if that is even possible)

The console specific key can be recovered without a working eMMC. You just need to extract the TSEC firmware from any public eMMC dump/software update package, and use that to recover the SBK and others (bis keys).

 

[TheDarkGreninja]

Which is why you back all of that up from the get go. We have the tools to do so.

Does SX OS have backup software?

 

[Deleted User]

~oops~

 

[Metal___]

"still need a 2.0.0 raw nand dump (I had backups of all the important stuff, the rest is just re-encrypt with BIS key and write back)."

Hexkyz was able to recover because he had a backup of his BIS key (to rebuild his NAND). From what I understand, that's the console unique key. You can't get to that once your eMMC is locked so if you don't already have that backed up, it looks like it might not be recoverable entirely on your own (without help from TX - if that is even possible)

Do you have any homebrew that backup? or how can I do it?

 

[Localhorst86]

The console specific key can be recovered without a working eMMC. You just need to extract the TSEC firmware from any public eMMC dump/software update package, and use that to recover the SBK and others (bis keys).

ok, fair enough. If that's the case it should be recoverable even without a backup (which I am sure a lot of people that use SX OS don't have). This does sound very involved, though. Something that a lot of people might not be able to.

 

[jakkal]

How old are you? Resorting to insults (as hilariously bad as yours is) doesn't help anyone.

His avatar is a cuphead. Triggered much?
Maybe you should pay some attention effort getting triggered

 

[Deleted User]

ok, fair enough. If that's the case it should be recoverable even without a backup (which I am sure a lot of people that use SX OS don't have). This does sound very involved, though. Something that a lot of people might not be able to.

While it might sound quite involved, this can be automated pretty easily, to the point where the user only has to copy a few files to their sd card and run a payload. But this all is assuming the "bricking" occurs in the first place, which is quite improbable.

 

[TheDarkGreninja]

you said it was irreversible
and you were wrong you cup head

Yeah I noticed, just seemed a bit odd for you to call him a cuphead for no reason at all.
Guess I just assumed you called him a cuphead out of ill will, my bad.

 

[MrGizMo]

exactly! this dude understands

no need to worry.

And still we have 17 pages of crap

 

[Sp1tFire92]

Im somewhat hesistant to get SX OS License since they do have that brick code. Im an enduser but some people claim that there is a chanche for it to hit normal users under certain circumstances. -.-"

 

[comput3rus3r]

Im somewhat hesistant to get SX OS License since they do have that brick code. Im an enduser but some people claim that there is a chanche for it to hit normal users under certain circumstances. -.-"

yeah don't get it. stay safe.

 

[Sp1tFire92]

By the team:

Hello ,

We are delighted to have now a massive SX OS userbase. We never had a single
report of a 'bricked' or damaged console caused by SX Pro or SX OS.

If people modify, hack and fiddle with their console, regardless of SX OS being
installed, they expose themselves to dangers such as 'bricking' their console.
We can't be held responsible for this.

We are a professional team, with a solid reputation for quality product and
support for many years.
We offer full commercial and technical support, updates for life and warranty on
our product, like we always did.
But obviously this is only valid if you do not use other modifications of hacks
that can damage your console.
Clearly, our customers do not want or need any other software and hardware than
Team Xecuter SX product. Please be careful who you trust when you use other
software or hardware on your valuable Nintendo Switch. Not everyone has a track
record like Team Xecuter, and they can disappear like they appeared.
Please also be careful with copies and clone of our software and hardware,
although as of today, we haven't seen any.

To sum all this up: You can be certain that you are safe when using original
Team Xecuter product such as SX OS. We not only state it, we guarantee it!

Thanks again to all our customers for their trust for the past 15 years already!

--
Best regards,
Team

So i guess i just get it and the other guys in this thread just talked nonsense.

 

[The Real Jdbye]

autorcm = brick code

but yeah, as long as it's safe and won't ever trigger by accident, i'm fine with anti-tamper brick code.

is it recoverable if you have a nand dump?

they could do evil stuff, like burning all your fuses lol

Yes. You need to erase the NAND to get rid of the password, then restore the backup.

 

[pLaYeR^^]

I knew it that there's something fishy. Well, if you don't wanna risk a brick, just buy their product and don't steal it. They have the permission to protect their own product from thieves. But it seems that it's not that hard to recover your NAND, so maybe some people are still waiting for a crack.

 

[Sp1tFire92]

I knew it that there's something fishy. Well, if you don't wanna risk a brick, just buy their product and don't steal it. They have the permission to protect their own product from thieves. But it seems that it's not that hard to recover your NAND, so maybe some people are still waiting for a crack.

I agree, i just hesistated since some people in this thread said that it could hit endusers aswell. Just bought it on axiogame for 24.95 (cheapest i found). Now i just need to wait for the license and my jig

 

[ihaveahax]

http://hexkyz.blogspot.com/2018/06/chill-shills.html hexkyz talks more about SX OS cracking.