- Joined
- Jul 23, 2018
- Messages
- 6,077
- Trophies
- 1
- Age
- 29
- Location
- Lampukistan
- Website
- hmpg.net
- XP
- 6,198
- Country
He didI haven't seen him say that.
He didI haven't seen him say that.
You probably also have dns servers blocked via /atmosphere/hosts/default.txtWhen exactly does the switch crash, I still have prodinfo blanking enabled from exosphere on 17 and havent had a crash yet?
Turn on your wifiWhen exactly does the switch crash, I still have prodinfo blanking enabled from exosphere on 17 and havent had a crash yet?
It seems when the server try to get info, it crashes. So if you block the Nintendo server(s) via DNS or just not going online. You won't get the crash. But if you don't block them, crash.When exactly does the switch crash, I still have prodinfo blanking enabled from exosphere on 17 and havent had a crash yet?
DNS blocking is totally fine. It's just the serial number blanking which causes a fatal screen.It seems when the server try to get info, it crashes. So if you block the Nintendo server(s) via DNS or just not going online. You won't get the crash. But if you don't block them, crash.
This is the case. It initially crashed on me, but after a reboot its now not crashing with prodinfo blankingIt seems when the server try to get info, it crashes. So if you block the Nintendo server(s) via DNS or just not going online. You won't get the crash. But if you don't block them, crash.
are you sure you are using the latest sigpatches?i can boot into 17.0 just fine but i cant run any games, even though 1.6.2 indicates i should be able to? i can use homebrew just fine and even updated sigpatches and i have nothing.
Ironically Tinfoil won't allow you to install bad versions unless you do the konami code.are you sure you are using the latest sigpatches?
and for some games installed from XCI using bad installers (like tinfoil) which messed up with the distributable bit you will have trouble.
If you are sure you have updated Sigpatches to latest then reinstall the games using most recent DBI or TinWoo, you need the most recent versions.
Was the crash from enabling prodinfo blanking looked into/fixed?
noob here - it's been ages since I set up my emunand and I think I blanked my serial. how would I know if I'm using dns-mitm? or does it not matter since my emu-partition is completely offline, and my Switch won't try to connect to Nintendo?The crash does not happen until a connection to nintendo has been established and the switch is actually trying to read your blanked cert, so if you use dns-mitm as you should, it doesn't crash, because it never manages to establish a connection in the first place. The blanking then works as an extra protection layer in case the dns mitm fails for whatever reason. Crashing is much better than sending your cert to nintendo. So I think it's fine the way it is. All the people saying "it works fine for me" are using dns-mitm as well.
https://rentry.org/ExosphereDNSMITMnoob here - it's been ages since I set up my emunand and I think I blanked my serial. how would I know if I'm using dns-mitm? or does it not matter since my emu-partition is completely offline, and my Switch won't try to connect to Nintendo?
aah, I do not have a folder or file like that. thanks. I figured since I never go online that might be redundant
Yes I have both hosts and prod info blanking, I set it up as single player only on the emunand and legit on sysnand so I dont see any issues then and it wont crash since it cant see the nintendo servers... seems like a non issue to me.
How does one undo the blank prod info if we did it with Atmosphere?
I know it's in one of the ini files but can't remember what should be done to undo it.
if yuou only didi with atmosphère, put 0 onHow does one undo the blank prod info if we did it with Atmosphere?
I know it's in one of the ini files but can't remember what should be done to undo it.