Incognito

incognito
Wipes personal information from your Nintendo Switch by removing it from prodinfo.

purpose
a) So your switch can go online without worrying about a ban or using random dogdy DNS servers that are also likely to get you banned.

b) so malicious homebrew applications cannot steal your personal certificate.

disclaimer
Always have a nand backup. I am not responsible for any bricks or bans. Use at your own risk, experimental.

This application backs up your prodinfo to the SD root, you should keep this backup in a more secure location, and not leave it on the SD card where malicious applications can read it.

https://github.com/blawar/incognito

edit: atmosphere blocks writes to CAL0, so you must use ReiNX or SX OS to install this. Once installed, you can switch back to atmosphere.

Cogn_mode-225x225.png
 
I restored a prodinfo file from a unbanned switch, and I can confirm it doesn't work
Did it boot? Or just blackscreen?

I'm pretty sure it just says "Online services have been restricted from this console"

this is huge because now we know Nintendo bans more than just the CERT from a console... probably the MAC and the Friend Code?

This also confirms that:

This software is useless if you are avoiding ban. Nintendo bans more that just prodinfo.
 
Last edited by huma_dawii,
I'm pretty sure it just says "Online services have been restricted from this console"

this is huge because now we know Nintendo bans more than just the CERT from a console... probably the MAC and the Friend Code?

This also confirms that:

This software is useless if you are avoiding ban. Nintendo bans more that just prodinfo.
So just to be sure, the prodinfo contains the cert and they are not two separate things?
 
Last edited by JJTapia19,
Instead of replacing it with junk data, you should make an algorithm to replace the PRODINFO with a heavily modified version of the user's actual PRODINFO. This way, if the user looses his backup, they can just use the fake PRODINFO they have and reverse the algorithm to retrieve the original.
 
Instead of replacing it with junk data, you should make an algorithm to replace the PRODINFO with a heavily modified version of the user's actual PRODINFO. This way, if the user looses his backup, they can just use the fake PRODINFO they have and reverse the algorithm to retrieve the original.

Dont want to do that, because its open source, and I do not want malicious applications reading the prodinfo. If I did that, malicious apps could reverse it unless the user was prompted for a password to encrypt it with... better to just zero it out and give them a backup.
 
  • Like
Reactions: Lacius
Instead of replacing it with junk data, you should make an algorithm to replace the PRODINFO with a heavily modified version of the user's actual PRODINFO. This way, if the user looses his backup, they can just use the fake PRODINFO they have and reverse the algorithm to retrieve the original.

yes if anyone has the same edits its also shit becauce of bans.
 
._. what's the point then?

The main reason for emunand is so you can run the latest fw while keeping your systems nand on old fw for best chance at cold boot cfw in future

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

anyway what are people experience with this app and testing if they can play and retain online?
 
Related to CAL0 and Atmosphere:
Atmosphere 0.8.0 changelog said:
Functionality was added implementing basic protections for NAND from userland homebrew:
  • BOOT0 now has write protection for the BCT public key and keyblob regions.
    • The ns sysmodule is no longer allowed to write the BCT public keys; all other processes can.
      • This should prevent system updates from removing AutoRCM.
    • No processes should be allowed to write to the keyblob region.
  • By default, BIS partitions other than BOOT0 are now read-only, and CAL0 is neither readable nor writable.
    • Adding a bis_write flag for a title will allow it to write to BIS.
    • Adding a cal_read flag for a title will allow it to read CAL0.
  • An automatic backup is now made of CAL0 on boot.
    • fs.mitm maintains a file handle to this backup, so userland software cannot read it.
  • To facilitate this, fs.mitm now mitms all sessions for non-system modules; content overriding has been made separate from service interception.
So both cal_read and bis_write might be needed to get it to work. I'm not sure what id I needed for the folder to put the files in, otherwise I would of tried.
 
Related to CAL0 and Atmosphere:

So both cal_read and bis_write might be needed to get it to work. I'm not sure what id I needed for the folder to put the files in, otherwise I would of tried.
I couldn’t get it to work even with the flags set.

Also you can read the flags.md if you want to learn more about them. It’s found on the atmosphere github in the docs folder.
 
Last edited by Deleted member 413168,

Site & Scene News

Popular threads in this forum