Search results
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window.
Edit your SDMC:/exosphere.ini file and add/change the next values to «1» in order to enable Atmosphère incognito on telemetry:
13 paź 2024 · Should I create 2 exosphere.ini, 1 for sysnand, and 1 for emunand and swap them in and out? I'm very new in this ATM scene, has done some research before decided to do the migrate. Reactions: Donnie-Burger
17 paź 2024 · if both are already at 0 in exosphere.ini: try to check if theres another exosphere.ini in root folder and delete it; go to atmosphere > config > system_settings find: enable_dns_mitm = u8!0x1
13 paź 2024 · However, I'm planning to restore it to use Exosphere instead along with DNS MITM. How effective is Exosphere nowadays, and how does it work? Does it actually modify the PRODINFO in NAND, or does it just simulate a blanked PRODINFO without actually altering it?
I am trying to setup ExoSphere and DNS MITM from the rentry.org guide. I am noticing that there are two different exosphere.ini files. One is for EmuNAND and the other for SysNAND.
They recommend to use DNS MITM and exosphere as ban protections but I don't get how they work. So I added to the line of the exosphere.ini file as "blank_prodinfo_sysmmc=1" and created also the "default.txt" in the /hosts folder to test these protections in my legit sysNAND.
