Incognito_RCM

since Incognito by blawar doesn't work on vanilla atmosphere, I made a payload to use with hekate (or any other payload injector) with the same functionality.
Incognito_RCM wipes personal information from your Nintendo Switch by removing it from prodinfo.

Functionality:​

• wipe personal information on sysnand/emunand
• backup prodinfo from sysnand/emunand
• restore prodinfo to sysnand/emunand

Since NAND memory is encrypted, this is based on shchmue's Lockpick_RCM to first get the neccessary encryption keys.
You can apply Incognito_RCM directly after installing atmosphere or any time after and it has the advantage that you don't need to set 90DNS after an internet connection and possibly communication with nintendo servers is already established. (You can apply 90DNS anyway)

This has only been tested by me on firmware 8.1.0, so please test it and report back.
Since it has only been tested by me, keep a hekate nand backup ready to be safe.

source: https://github.com/jimzrt/Incognito_RCM
releases: https://github.com/jimzrt/Incognito_RCM/releases

Disclaimer:
This is early stage and there is no guarantee that everything works as expected! Please have a hekate NAND backup ready!​

Screenshots:

Spoiler

Changelog:

Spoiler

v0.6.1

• bugfix: write to emummc instead of sdmmc

v0.6.0

• incorporate hekate & lockpick_rcm changes
• reboot to payload

v0.5.1

• firmware 9.1.0 support

v0.4.0

• adopt lockpick_rcm and hekate changes (includes fixing of possible bugs and better resource management)
• reduced payload size
• use tui progressbar

v0.3.0

• more error handling
• backup validation when reading and writing
• retry up to 5 times when reading and writing before aborting

v0.2.0

• more validation
• code cleanup and refactoring

v0.1.0

• much faster read and write speed (not sector by sector anymore)
• much more validation and verification (still not perfect)
• more error handling (still not perfect)
• backups aren't overwritten, old backups are renamed
• check for backup before applying incognito
• auto-restore backup if something goes wrong

v0.0.2

• Removed external libraries and better handling of reading big chunks of memory.

as always, have a NAND backup ready!

 

[OldGnashburg]

How can you tell if it's working? My serial is still visible in settings.

 

[Localhorst86]

How can you tell if it's working? My serial is still visible in settings.

Then it's not set up correctly. Serial Number should show up as XAW00000000000

 

[OldGnashburg]

How do I set it up correctly? I thought stock Atmosphere would do it automatically?

 

[Localhorst86]

How do I set it up correctly? I thought stock Atmosphere would do it automatically?

No, they put the feature in because people wanted it, but they don't encourage this feature. Therefore it's not enabled by default.

Grab this file
https://github.com/Atmosphere-NX/Atmosphere/blob/master/config_templates/exosphere.ini

And put it on the root of your SD and enable prodinfo blanking on your mmc(s) of choice by setting either or both of these lined to 1

blank_prodinfo_sysmmc=1
blank_prodinfo_emummc=1

 

[OldGnashburg]

Still not working. Serial is still there.

 

[tom2199]

Still not working. Serial is still there.

If you're booting via hekate it does not work yet, only via fusee-primary (directly or chainloading through hekate)

 

[OldGnashburg]

How do I chainload through hekate, and how do I get it to boot EmuNAND by default? Or will the Incognito_RCM fork that works with 10.0.0 work with 10.0.1

 

[tom2199]

How do I chainload through hekate, and how do I get it to boot EmuNAND by default? Or will the Incognito_RCM fork that works with 10.0.0 work with 10.0.1

The fork does work on 10.0.1, if you want to chainload fusee-primary through hekate you need the following entry in hekate_ipl.ini:
[fusee-primary]
payload=bootloader/payloads/fusee-primary.bin
(if your fusee-primary is located there, else you have to change the path). fusee-primary boots emunand by default if there is one, so you don't need to change anything for that to work.

 

[Nicola]

The author, jimzrt, states that this application wipes "personal information" from the switch nand, but what is this personal information? Does it have any effect on games/OS? Does it need to be restored? It is randomised/re-filled by the OS after being wiped?

 

[OldGnashburg]

The author, jimzrt, states that this application wipes "personal information" from the switch nand, but what is this personal information? Does it have any effect on games/OS? Does it need to be restored? It is randomised/re-filled by the OS after being wiped?

It wipes the serial from the NAND, meaning Nintendo shouldn't be able to identify your Switch and therefore shouldn't be able to ban you via telemetry. Also means you won't be able to use Nintendo services, but that's what SysNAND is for. Pairs well with 90DNS

 

[Nicola]

I wipes the serial from the NAND, meaning Nintendo shouldn't be able to identify your Switch and therefore shouldn't be able to ban you via telemetry. Also means you won't be able to use Nintendo services, but that's what SysNAND is for. Pairs well with 90DNS

Thanks. That should be in the description. Devs always seem to forget about newcomers.

 

[sj33]

I thought the whole point of this was to not need 90DNS?

 

[driverdis]

It would be interesting to see if Nintendo will be able to eventually identify and ban users who use this alongside any form of Nintendo account.

My reasoning behind this is that Nintendo can still log data from Incognito users and can potentially make a connection between Nintendo accounts on the system and what their real system serial is by checking login and telemetry info for that account.

If it has only logged in on one system ever then it can be guaranteed 100% that is the system serial to ban since linking a Nintendo account requires doing so online and having no other systems logged in or ever accessed means that the system they linked the account to has to be the one modified now.

I will continue using 90DNS (for the reason above) alongside incognito_rcm (guarantees patches or other mods can’t accidentally stop the new Atmosphere feature from working and show my serial anyway)

in case the above is a problem in the future I would recommend people only use local accounts on an incognito system if they are not using 90DNS.

 

[BladeRunner64]

The fork does work on 10.0.1, if you want to chainload fusee-primary through hekate you need the following entry in hekate_ipl.ini:
[fusee-primary]
payload=bootloader/payloads/fusee-primary.bin
(if your fusee-primary is located there, else you have to change the path). fusee-primary boots emunand by default if there is one, so you don't need to change anything for that to work.

Does it matter where we put those two lines? I have them under my emuMMC before the brackets like this:


{------ Atmosphere ------}
[Atmosphere FSS0 EmuMMC]
fss0=atmosphere/fusee-secondary.bin
kip1=atmosphere/kips/*
icon=bootloader/res/emu_boot.bmp
[fusee-primary]
payload=bootloader/payloads/fusee-primary.bin
{}

Edit: Nevermind. Tried that and it worked.

 

[Slim45]

How can you tell if it's working? My serial is still visible in settings.

btw where are you placing the .ini file? should be in root i thyink

 

[OldGnashburg]

btw where are you placing the .ini file? should be in root i thyink

It was root, I figured out the issue. I wasn't booting from fusee primary. I was booting from Hekate, however latest Incognito RCM fork works so I just used that.

 

[Slim45]

It was root, I figured out the issue. I wasn't booting from fusee primary. I was booting from Hekate, however latest Incognito RCM fork works so I just used that.

can you link plz

 

[Nemix77]

Needs to be updated, not working with fresh install of Atmosphere 0.12.0 and firmware 10.0.2.

Edit:

Getting bis_keys...
Unknown pkg1 version.

 

[masagrator]

Needs to be updated, not working with fresh install of Atmosphere 0.12.0 and firmware 10.0.2.

Edit:

Getting bis_keys...
Unknown pkg1 version.

You don't need Incognito with 0.12.0
It has blank prodinfo in exosphere.ini and it's better, because it doesn't wipe your prodinfo from nand, but gives HOS fake one to use.
https://github.com/Atmosphere-NX/Atmosphere/blob/master/config_templates/exosphere.ini

 

[Muxi]

Needs to be updated

Here is a version of Incognito RCM that works under FW 10.x.x. If you run AMS and SX OS via the same emuMMC, you will still need Incognito_RCM, since only AMS currently offers this native Incognito feature.