Hacking CFW Comparison Chart

Itsuki235

Well-Known Member
OP
Member
Joined
Jun 13, 2019
Messages
228
Trophies
0
XP
338
Country
United States
Let me know if anything is wrong. No promise that I will ever fix/update the chart below, but it will let people know that something has been or should be updated/changed. Last updated 2020May06.

Please see the notes right below the chart for clarifications.

upload_2020-5-6_15-54-4.png


Major Features Notes:
1 SX OS is ~$25-30 or $50 if purchased along with their dongle.
2 NeutOS's boot process is based on SX OS and closed source. NeutOS's boot process is very similar and breaks dual boot compatibility with SX OS. That boot code is also closed source.
4 Atmosphere team does not like SX OS's implementation of emuNAND.
5 Long term support for NeutOS is unclear.
6 Atmosphere/Kosmos/Unicorn Sigpatches must be installed manually, but are ultimately possible. There is no "unicorn distribution" so #6 does not really apply to it.
7 Tinfoil takes issue with Kosmos, Atmosphere requires a lot of patches to everything, and ReiNX s too old.
8 Note that Atmosphere/Kosmos's method of blanking prodinfo is done purely in software and is very new. NeutOS also uses this method by default, but, like Atmosphere, can also support the .nro method instead or in addition to the pure software method.

Minor Features Notes:
9 SX OS has compatibility issues. Atmosphere does not support most useful homebrew w/o flag X or config setting Y.
10 Use "Awoo Installer" for XCI installs. Please show support for important bug fix feature request #15.
11 XCIs can be converted to NSP for other CFWs with 4nxci and Lockpick_RCM.

Other Features Notes:
16 NeutOS bootloader patches take issue with Kosmos Toolbox, use Reboot To payload instead and [this] the button remap template found below.
18 Sysnetcheat or noexes on ReiNX requires a PC or phone (?).
19 Using hid-mitm, may require a PC or phone (?).
20 Nothing can use exFat w/o corruption. SX OS can use NTFS on external HDDs.
21 Trivial to accidentally forget or kids to bypass.

Notes on CFW vs CFW Distributions
- Technically Kosmos, StarDustCFW and Unicorn should all be on a seperate chart because they are not CFW but rather "CFW Distributions" because as-is is an apples/oranges comparison.
- Missing, but should be included: StarDustCFW which is a repackage of Atmosphere and SX OS.
- NeutOS is somewhere in between a CFW and a CFW distribution. NeutOS makes dramatic changes during Atmosphere boot process, but not much else.
- The emphasis for Kosmos is sysmodules and utilizing Atmosphere's existing features.
- StarDustCFW = SXOS + Atmosphere.
- Unicorn is the idea of combining Kosmos + NeutOS. It can also be thought of as applying patches to Kosmos.

On the Unicorn entry:
This is an unholy amalgamation of everything that Tinfoil devs and the Kosmos team and ReSwitched all despise in one way or another.
1. Download Kosmos from https://github.com/AtlasNX/Kosmos/releases
2. Download NeutOS from https://github.com/borntohonk/NEUTOS/releases
3. Download Atmosphere (incl fusee-primary.bin) from: https://github.com/Atmosphere-NX/Atmosphere/releases
4. Use the Kosmos files as a base.
5. Delete the existing atmosphere and sept folders. Copy over Atmosphere's folders.
6. Modify the SD:/bootloader/hekate_ipl.ini file according to this thread to remove the fss0= syntax with payload= syntax.
7..Copy the fs and es patches from NeutOS's Atmosphere directory to the one provided by Kosmos, and also SD:/exosphere.ini to the root.
8..Use these alpha quality loader_patches that were first posted annoymously on 4chan by someone who hacked NeutOS as appropriate. These patches break Kosmos Toolbox btw.
Update: The patches in Raugo's fusee-primary thread by have been updated to include a version of the loader_patches, so they now also work.
9. Next, download updated versions of tinfoil/Awoo/Goldleaf/ChoijdurNX and other homebrew.
10. After that push "hekate_ctr.bin", create a sysnand backup, create emuMMC, boot atmosphere, install incognito, and run tinfoil.

For Unicorn to replicate much of the above functionality of Kosmos Toolbox create "SD:/atmosphere/config/override_config.ini" with the following file with the following contents:
Code:
[hbl_config]
override_key=R
override_any_app=true
override_any_app_key=R

Other Notes:
- What constitutes a major/minor/other feature is subjective.
- The above is not actually step-by-step. Neither, I nor anyone else provide support for unicorn. See #5 above.
- If you do not understand why so and so is this but not that, or how this is related to that, feel free to ask.
- However, this is not a support thread. For help setting up a particular CFW/config/distro on your NX, try asking in: designated support thread.
 
Last edited by Itsuki235, , Reason: updated chart in response to feedback, grammar, formatting

OrGoN3

Well-Known Member
Member
Joined
Apr 23, 2007
Messages
3,116
Trophies
0
XP
2,363
Country
United States
Tinfoil works just fine with vanilla Atmosphere with the correct patches, which are now included in the newer sig patch thread, as long as you're using fusee-primary. It also has regular homebrew support with said patches. As for configuration tools, notepad works just fine.

WTF is Unicorn?

Why no StarDustCFW? @Birbb
 
  • Like
Reactions: KiiWii

Itsuki235

Well-Known Member
OP
Member
Joined
Jun 13, 2019
Messages
228
Trophies
0
XP
338
Country
United States
Tinfoil works just fine with vanilla Atmosphere with the correct patches
[...]
Why no StarDustCFW? @Birbb
The stuff that Tinfoil is used for requires sigpatches which neither Atmosphere's github nor Kosmos's github provide. Even if it will "run" doing so is pointless if it cannot do anything useful.
Read the note at the bottom for Unicorn. It is not an official build/distribution or anything, just a configuration that is possible that merges NeutOS + Kosmos. I could rename it to StarDustCFW in the chart if others request it.

Edit:
Actually I looked up StarDustCFW. I thought you were joking at first. It looks like a spanish focused release group for repackaging stuff. Never heard of them before, but might take a look at their positives/negatives.
 
Last edited by Itsuki235, , Reason: as above

Dust2dust

Well-Known Member
Member
Joined
Jun 17, 2010
Messages
1,638
Trophies
1
XP
2,516
Country
Canada
I would scrap your categories (major, minor, and other). Because, to me, some of your minor features belong in the major features. It looks like you have bias against some CFW. If you want the chart to be as neutral as it should be, get rid of the categories.
 

chocoboss

Well-Known Member
Member
Joined
Jun 25, 2016
Messages
504
Trophies
0
Age
32
Location
FRANCE
XP
1,115
Country
France
Why focuse on "Tinfoil" compatibility ?

Why not talk about the others nsp installer ?

Kosmos is not a cfw but a package ( hekate + atmo )

NTFS ? Lol this is only used by SX for external hard drive
 
Last edited by chocoboss,

OrGoN3

Well-Known Member
Member
Joined
Apr 23, 2007
Messages
3,116
Trophies
0
XP
2,363
Country
United States
The stuff that Tinfoil is used for requires sigpatches which neither Atmosphere's github nor Kosmos's github provide. Even if it will "run" doing so is pointless if it cannot do anything useful.
Read the note at the bottom for Unicorn. It is not an official build/distribution or anything, just a configuration that is possible that merges NeutOS + Kosmos. I could rename it to StarDustCFW in the chart if others request it.

Edit:
Actually I looked up StarDustCFW. I thought you were joking at first. It looks like a spanish focused release group for repackaging stuff. Never heard of them before, but might take a look at their positives/negatives.
Vanilla Atmosphere with the sigpatches REQUIRED to run homebrew for fusee include acid patches, which Tinfoil needed. Tinfoil now works on AMS just fine with patches (just like any homebrew that runs on AMS, it needs patches). It doesn't just "run", it has full functionality. Anything that is locked out due to the lack of an SX OS license is restored if one is found on the SD card. You are clearly not aware of the changes made in Atmosphere 0.12.0.

NeutOS is NOT basedon SX OS. It's a fork of Atmosphere and the code is open source, just like Atmosphere. Anybody can compile the source. You either just have no knowledge of the subject matter, or are hard trolling.

"16 NeutOS bootloader patches take issue with Kosmos Toolbox, use Reboot To payload instead and [this] button remap template."

That sentence makes 0 sense. NeutoOS bootloader patches are for fusee-primary. Using Kosmos Toolbox, which uses Hekate, would make no sense and have no effect.
 
Last edited by OrGoN3,
  • Like
Reactions: KiiWii

Itsuki235

Well-Known Member
OP
Member
Joined
Jun 13, 2019
Messages
228
Trophies
0
XP
338
Country
United States
Vanilla Atmosphere with the sigpatches REQUIRED to run homebrew for fusee include acid patches, which Tinfoil needed. Tinfoil now works on AMS just fine with patches (just like any homebrew that runs on AMS, it needs patches). It doesn't just "run", it has full functionality.
Patches are not needed for most homebrew. The "reboot to payload.nro" does work normally, with full functionality, without sigpatches for example.

That is sort of the point. You can't really run Tinfoil without sigpatches so it does not get credit for being able to run Tinfoil easily hence the -- on that line. Unicorn should probably be changed to -- for that line to signify parity in this regard, so that should be considered a typo or incorrect until I do so.

NeutOS is a fork of atmosphere that uses a modified boot process based upon SX OS's booting style. If it was 100% based on Atmosphere then the source code for SD:/sept/payload.bin should be accessible courtesy of Atmosphere's GPLv2 license, but it is not.

Instead, it is clear that there is some overlap between SXOS and NeutOS's boot code from the following:
The file referred to as "payload.bin" (also "reboot_payload.bin") is loosely based off of Shofel2. There are no requirements for me to provide the source code for this binary, per Shofel2 licensing. The only requirement per shofel2's license is to include the copyright notice / license and make it clear where it originates from.-NeutOS's github
The above disclaim and the hint in the readme and taking a look at the files shows that their boot code breaks dual-boot compatibility with SX OS due to overlapping file names and directory structure.

If you want, think of it as SX OS and NeutOS sharing the same fork (same parent) in the boot code, as opposed to being one directly copied to another. Even if they share a common fork, there is still a strong association in the boot code there because of that. That is what I was needing to point out in comment #4 because the source code for that bootloader is not available.

If you want I can change the phrasing. What phrasing would you suggest?

NTFS ? Lol this is only used by SX for external hard drive
Yes, as was noted. see the note for # 20:
20 Nothing can use exFat w/o corruption. SX OS can use NTFS on external HDDs.

I would scrap your categories (major, minor, and other). Because, to me, some of your minor features belong in the major features. It looks like you have bias against some CFW. If you want the chart to be as neutral as it should be, get rid of the categories.

What constitutes a major/minor/other feature is subjective.
Even without categories, putting things in a certain order and including/not including certain items would also display a bias. The Kosmos's CFW comparison chart displays a very strong bias to their stuff and deliberately omits very important features of other CFW that those CFW use as their primary bonuses.

The point is not to be 100% unbiased, but rather to try to include as many genuinely unique features of all CFW/repackages available have their entry in the table, with one's bias out in the open and easy for other people to understand, and hence subsequently discard while looking at data in order to understand how that data is useful to them.

BTW, The table itself doesn't even compare like-with-like (which is required for objective comparisons) because only ATM-SXOS and ReiNX are CFW, and, strictly speaking, Kosmos, Unicorn, and StarDustCFW belong on a separate chart called "CFW Distributions" or similar. That said most people think Hekate is a CFW, so...

Edit:

So I will make 2 charts when you convince Team Atlas to remove their repackage of Atmosphere from their own chart Edit3: that is called "Comparing Custom Firmwares".

"16 NeutOS bootloader patches take issue with Kosmos Toolbox, use Reboot To payload instead and [this] button remap template."

That sentence makes 0 sense. NeutoOS bootloader patches are for fusee-primary. Using Kosmos Toolbox, which uses Hekate, would make no sense and have no effect.
Yes exactly! It indeed makes 0 sense, but try it.

Try using Kosmos Toolbox on NeutOS and see what happens. NeutOS, or even just applying their bootloader patches to vanilla Atmosphere, does actually break Kosmos toolbox. Try it!
 
Last edited by Itsuki235, , Reason: as above

chocoboss

Well-Known Member
Member
Joined
Jun 25, 2016
Messages
504
Trophies
0
Age
32
Location
FRANCE
XP
1,115
Country
France
Itsuki235 said:
So it does not get credit for being able to run Tinfoil easily

Ppl have the habbit to install patches so it's not really a problem.

Btw I do not understand why ppl focus on Tinfoil
"OMG Tinfoil is not working, it su***, going suicide. It su*** atmo do not support Tinfoil"

Come on just go for another installer. Or ask Tinfoil dev to remove the check.
 

linuxares

I'm not a generous god!
Global Moderator
Joined
Aug 5, 2007
Messages
9,124
Trophies
1
XP
10,544
Country
Sweden
Oh I like your chart!
However Kosmos is not a CFW, if I remember correct they don't really like to be called that.

Also "Free" can be turned around to "Cost"
and "Freedom" can just be "Opensource".

Looks a bit cleaner.

EDIT: Prodinfo blanking needs to be researched. Since Atmosphere got their own now. That doesn't destroy your prodinfo.
 
Last edited by linuxares,
  • Like
Reactions: chocoboss

Itsuki235

Well-Known Member
OP
Member
Joined
Jun 13, 2019
Messages
228
Trophies
0
XP
338
Country
United States
Oh I like your chart!
However Kosmos is not a CFW, if I remember correct they don't really like to be called that.

Also "Free" can be turned around to "Cost"
and "Freedom" can just be "Opensource".

Looks a bit cleaner.
First Part) I do understand that, but I cannot compare Kosmos and other repackages/possible configurations without putting them on the same chart or creating a second chart, so they stay as-is for now.
Second) Understood.
 
  • Like
Reactions: linuxares

linuxares

I'm not a generous god!
Global Moderator
Joined
Aug 5, 2007
Messages
9,124
Trophies
1
XP
10,544
Country
Sweden
First Part) I do understand that, but I cannot compare Kosmos and other repackages/possible configurations without putting them on the same chart or creating a second chart, so they stay as-is for now.
Second) Understood.
I get that, no worries :)
 

tom2199

Well-Known Member
Member
Joined
Apr 23, 2015
Messages
255
Trophies
0
XP
470
Country
Germany
NeutOS is NOT basedon SX OS. It's a fork of Atmosphere and the code is open source, just like Atmosphere. Anybody can compile the source. You either just have no knowledge of the subject matter, or are hard trolling.
That is not true, NEUTOS was open source but the source didn't get updated for the 0.12.0 release because the last commit was 8 days ago and the release was 3 days ago. It doesn't seem that borntohonk will release the source code anymore, though I could be wrong.
 

linuxares

I'm not a generous god!
Global Moderator
Joined
Aug 5, 2007
Messages
9,124
Trophies
1
XP
10,544
Country
Sweden
That is not true, NEUTOS was open source but the source didn't get updated for the 0.12.0 release because the last commit was 8 days ago and the release was 3 days ago. It doesn't seem that borntohonk will release the source code anymore, though I could be wrong.
Odd since it's Atmosphere. So he must release it if he publish the bins.
 

Itsuki235

Well-Known Member
OP
Member
Joined
Jun 13, 2019
Messages
228
Trophies
0
XP
338
Country
United States
Odd since it's Atmosphere. So he must release it if he publish the bins.
NeutOS does not really change anything besides some of the boot code. For that, NeutOS uses shofel2's code for which they claim they do not need to publish the source code.

As a practical mater, if you want to know what the source code for NeutOS, just look at Atmosphere's source tree.

Mirroring the changes identically into their fork is little more than a formality. I am sure lawyers care a lot about these formalities and technicalities, but it is not a big deal to normal people or the community.
 

linuxares

I'm not a generous god!
Global Moderator
Joined
Aug 5, 2007
Messages
9,124
Trophies
1
XP
10,544
Country
Sweden
NeutOS does not really change anything besides some of the boot code. For that, NeutOS uses shofel2's code for which they claim they do not need to publish the source code.

As a practical mater, if you want to know what the source code for NeutOS, just look at Atmosphere's source tree.

Mirroring the changes identically into their fork is little more than a formality. I am sure lawyers care a lot about these formalities and technicalities, but it is not a big deal to normal people or the community.
Yeah I know.
A bit silly just not to update it.
But lets not turn this thread in to those "THEY MUST UPDATE BECAUSE GPL! AGUUUUH"
 

OrGoN3

Well-Known Member
Member
Joined
Apr 23, 2007
Messages
3,116
Trophies
0
XP
2,363
Country
United States
Patches are not needed for most homebrew. The "reboot to payload.nro" does work normally, with full functionality, without sigpatches for example.

That is sort of the point. You can't really run Tinfoil without sigpatches so it does not get credit for being able to run Tinfoil easily hence the -- on that line. Unicorn should probably be changed to -- for that line to signify parity in this regard, so that should be considered a typo or incorrect until I do so.

NeutOS is a fork of atmosphere that uses a modified boot process based upon SX OS's booting style. If it was 100% based on Atmosphere then the source code for SD:/sept/payload.bin should be accessible courtesy of Atmosphere's GPLv2 license, but it is not.

Instead, it is clear that there is some overlap between SXOS and NeutOS's boot code from the following:
The file referred to as "payload.bin" (also "reboot_payload.bin") is loosely based off of Shofel2. There are no requirements for me to provide the source code for this binary, per Shofel2 licensing. The only requirement per shofel2's license is to include the copyright notice / license and make it clear where it originates from.-NeutOS's github
The above disclaim and the hint in the readme and taking a look at the files shows that their boot code breaks dual-boot compatibility with SX OS due to overlapping file names and directory structure.

If you want, think of it as SX OS and NeutOS sharing the same fork (same parent) in the boot code, as opposed to being one directly copied to another. Even if they share a common fork, there is still a strong association in the boot code there because of that. That is what I was needing to point out in comment #4 because the source code for that bootloader is not available.

If you want I can change the phrasing. What phrasing would you suggest?


Yes, as was noted. see the note for # 20:





Even without categories, putting things in a certain order and including/not including certain items would also display a bias. The Kosmos's CFW comparison chart displays a very strong bias to their stuff and deliberately omits very important features of other CFW that those CFW use as their primary bonuses.

The point is not to be 100% unbiased, but rather to try to include as many genuinely unique features of all CFW/repackages available have their entry in the table, with one's bias out in the open and easy for other people to understand, and hence subsequently discard while looking at data in order to understand how that data is useful to them.

BTW, The table itself doesn't even compare like-with-like (which is required for objective comparisons) because only ATM-SXOS and ReiNX are CFW, and, strictly speaking, Kosmos, Unicorn, and StarDustCFW belong on a separate chart called "CFW Distributions" or similar. That said most people think Hekate is a CFW, so...

Edit:

So I will make 2 charts when you convince Team Atlas to remove their repackage of Atmosphere from their own chart.


Yes exactly! It indeed makes 0 sense, but try it.

Try using Kosmos Toolbox on NeutOS and see what happens. NeutOS, or even just applying their bootloader patches to vanilla Atmosphere, does actually break Kosmos toolbox. Try it!
Again, why would I use a toolbox designed for hekate when using fusee? That is what makes no sense. You're not supposed to be able to use it.

Increase your knowledge on the subject please.

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

Yeah I know.
A bit silly just not to update it.
But lets not turn this thread in to those "THEY MUST UPDATE BECAUSE GPL! AGUUUUH"
Aside from the bootloader there may not be any changes. Vanilla atmosphere with patches fully supports tinfoil, so no need for changes anymore. The primary changes were removing the write lock on cal0. No need for that anymore, and if you want to, use the exosphere settings.

Patches are available in a thread here and on discords.
 

Itsuki235

Well-Known Member
OP
Member
Joined
Jun 13, 2019
Messages
228
Trophies
0
XP
338
Country
United States
Again, why would I use a toolbox designed for hekate when using fusee? That is what makes no sense. You're not supposed to be able to use it.

Increase your knowledge on the subject please.
Because it is useful and has other functionality besides just interfacing with Hekate and works 100% works 100% when just using fusee.

W/O the NeutOS bootloader patches and having a loader.kip instead, KosmosToolbox works do things like change boot profiles. What is odd is that those NeutOS patches break Kosmos Toolbox. There is no fundamental reason for them to do so when all Kosmos Toolbox does amounts to editing text files or rebooting the console.

That is what is odd and deserves to be pointed out because it is an important incompatibility that helps one understand how these different CFW relate/do not relate to one another.

Edit:
Vanilla atmosphere with patches fully supports tinfoil, so no need for changes anymore. The primary changes were removing the write lock on cal0. No need for that anymore, and if you want to, use the exosphere settings.

Patches are available in a thread here and on discords.
One minor thing work mentioning is that the Vanilla atmosphere with normal patches cannot run Tinfoil on OFW 10+. It only runs on vanilla atmosphere because of a hack.

Those alpha-quality patches that were extracted from NeutOS that can be used to patch vanilla Atmosphere are required for OFW 10+. There is 100% no technical need for Tinfoil to require these patches in that configuration because it has/could have the related functionality available from the SD:/atmosphere/kips/loader.kip available.

The reason why Tinfoil disallows use of SD:/atmosphere/kips/loader.kip is to deliberately break compatibility with Kosmos and vanilla Atmosphere with that loader.kip. Literally everything works with that loader.kip and other patches *except* for Tinfoil.

So it is misleading to say that it works, when this configuration was clearly not intended, and is 100% a Tinfoil side issue. It is also a very fragile configuration and likely to break on the next update cycle.
 
Last edited by Itsuki235, , Reason: as above

OrGoN3

Well-Known Member
Member
Joined
Apr 23, 2007
Messages
3,116
Trophies
0
XP
2,363
Country
United States
That is not true, NEUTOS was open source but the source didn't get updated for the 0.12.0 release because the last commit was 8 days ago and the release was 3 days ago. It doesn't seem that borntohonk will release the source code anymore, though I could be wrong.
Look at the source code itself. Changes have been made as recently as an hour ago. The source code is there and you can view it.

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

Because it is useful and has other functionality besides just interfacing with Hekate and works 100% works 100% when just using fusee.

W/O the NeutOS bootloader patches and having a loader.kip instead, KosmosToolbox works do things like change boot profiles. What is odd is that those NeutOS patches break Kosmos Toolbox. There is no fundamental reason for them to do so when all Kosmos Toolbox does amounts to editing text files or rebooting the console.

That is what is odd and deserves to be pointed out because it is an important incompatibility that helps one understand how these different CFW relate/do not relate to one another.
Neutos may be nuking your hekate patches because they do not include acid patches for tinfoil, and the point of neutos is to support tinfoil. Who knows. I don't because I didn't read the source code. But again, using kosmos app, I mean, let's not even go there.

I stand by my recommendation for you to gain more knowledge and heavily editing the OP so that it reflects the truth.
 
General chit-chat
Help Users
  • No one is chatting at the moment.
    KennieDaMeanie @ KennieDaMeanie: https://youtube.com/shorts/52YAkk71E90?feature=share