Hacking Custom SXOS CFW

  • Thread starter Thread starter chronoss
  • Start date Start date
  • Views Views 51,348
  • Replies Replies 120
  • Likes Likes 14

Which licence you use ?

  • Free Licence by Reacher17

  • Original Licence by TX

  • I would prefer Atmophere


Results are only viewable after voting.
Anyways there is no reason to continue use SX OS, only piracy reasons remain (like hdd support and xci mounting).

In all terms atmos its better so far.
 
You don't have anything. Your source's BCPKG2 partition is on FW 11.0.0 and the SYSTEM Partition is supposedly on 11.0.1. The os shows you 11.0.1 but it isn't on 11.0.1. How should that work? SX OS is closed source/proprietary. This spoofing is for the license. Not for higher firmware versions. Why doesn't anyone get that?
Yes

Anyways there is no reason to continue use SX OS, only piracy reasons remain (like hdd support and xci mounting).

In all terms atmos its better so far.
True :)
 
Bonjour , pour lancer le " Original-License-menu_sxos " il faut logiciel python j'arrive pas a patché le fichier ? merci

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

Attachments

  • question.jpg
    question.jpg
    154.9 KB · Views: 230
  • Like
Reactions: chronoss
I renamed the boot to boot.dat.orig and once I run Original-License-menu_sxos with python the name of the file does not change

j'ai renommé le boot en boot.dat.orig et une fois je lance Original-License-menu_sxos avec python le nom du fichier ne change pas
 
Last edited by x65943, , Reason: Added English
  • Like
Reactions: chronoss
j'ai renommé le boot en boot.dat.orig et une fois je lance Original-License-menu_sxos avec python le nom du fichier ne change pas
Il crée un nouveau fichier boot.dat que tu va utilisé sur ta console.

Please, it's a English forum so we need to talk in english :(
 
SX OS boots because the BCPKG2 partition is on FW 11.0.0. Otherwise SX OS would end up in a black screen. SYSTEM partition is on 11.0.1. That's why it shows FW 11.0.1 in the OS. But it doesn't change the fact that it is still on 11.0.0. And furthermore, this spoofing is only for the license. Not for compatibility for 11.0.0+ ;)
So...nice fake.
It’s more of a half upgrade than a spoof, 11.0.1 also updated vi and hid, which are installed in sys.
It’s still stupid though.
 
Please help, tried the tutorial, if i use .py for hacked sxos boot.dat, the result is boot.dat with no license.dat but when i use the .py for original sxos boot.dat, the result is new boot.dat with license.dat (should it be the other way around?) and when I tried to use the new boot.dat on my switch lite, it doesn’t boot, and after a while there is an error warning, no boot.dat, I’ve double checked there was boot.dat and original license.dat on the root of my sd card
 
  • Like
Reactions: chronoss
Please help, tried the tutorial, if i use .py for hacked sxos boot.dat, the result is boot.dat with no license.dat but when i use the .py for original sxos boot.dat, the result is new boot.dat with license.dat (should it be the other way around?) and when I tried to use the new boot.dat on my switch lite, it doesn’t boot, and after a while there is an error warning, no boot.dat, I’ve double checked there was boot.dat and original license.dat on the root of my sd card
It's not compatible with Switch Lite for now
 
If I don't give a shit about XCI and HDD game loading, is there any reason for me to bother with this OS? I heard SXOS had some sort of auto game save cloud storage?
 

Site & Scene News

Popular threads in this forum