Or DNSMITM which is a better option.For anyone that wants to use exosphere on firmware 17.0.0, you need to setup 90DNS, as long you block server communication you would be fine, you won't crash even if you have wifi on.
Or DNSMITM which is a better option.For anyone that wants to use exosphere on firmware 17.0.0, you need to setup 90DNS, as long you block server communication you would be fine, you won't crash even if you have wifi on.
Or DNSMITM which is a better option.
Why 90dns though? Just use dns mitm lolFor anyone that wants to use exosphere on firmware 17.0.0, you need to setup 90DNS, as long you block server communication you would be fine, you won't crash even if you have wifi on.
Why 90dns though? Just use dns mitm lol
today there are two options on the beginning was only one, so more people knows or are comfortable with DNS90, both do the same is up to you which one to use.Why 90dns though? Just use dns mitm lol
Nice but... How?Or you can exefs patch throwing error on blanked cert. Works perfectly.
I receive error, I attach screenshotThe emummc should start as it is on 16.1.0
You'll need to update your Hekate (v6.0.7) and Atmosphere (v1.6.2) to their currently latest versions. Since there's no game that requires fw 17.0.0 to run, I'd just update sigpatches after that for your emuMMC firmware (i.e. 16.1.0) and Atmosphere v1.6.2. You can see here how to create your own sigpatches, thanks to @impeeza.Hi, I hope this is the right section to ask, I apologize in advance if I'm wrong.
My son's console was configured with OFW 16.1.0 and emummc 16.1.0.
While playing Minecraft online, the console was inadvertently updated to OFW 17.
Obviously the emummc no longer starts.
Is there a way to update it to FW 17 without having to recreate a new emummc (therefore without losing all installed data and related saves)?
thanks and sorry in advance.
Hi, I hope this is the right section to ask, I apologize in advance if I'm wrong.
My son's console was configured with OFW 16.1.0 and emummc 16.1.0.
While playing Minecraft online, the console was inadvertently updated to OFW 17.
Obviously the emummc no longer starts.
Is there a way to update it to FW 17 without having to recreate a new emummc (therefore without losing all installed data and related saves)?
thanks and sorry in advance.
I receive error, I attach screenshot
I used the latest sthetix hats, I think everything is up to date.Hello at this point you need to follow the steps explained on the thread about Atmosphère crasing Andre update.
In summary, you need to update to latest Atmosphère and hekate, download again the files from GitHub even if you think you have them, you can use Hekate's UMS to connect your SD card to PC, while you are there, backup and delete SD:/atmosphere/contents folder. Then reinstall latest sigpatches.
And before start your console be sure you are using DnsMITM https://rentry.co/ExosphereDNSMITM
It's easy
After all is working. Reinstall all your sysmodules (tesla, emuiibo, etc.) and any theme if you use it.
I receive error, I attach screenshot
Following the guides, the links take you back to tesla menus and related files which have support up to fw 16.Update your tesla and its modules.
Following the guides, the links take you back to tesla menus and related files which have support up to fw 16.
last release date May.
Am I wrong?
https://github.com/WerWolv/nx-ovlloader/releases/tag/v1.0.7
https://github.com/WerWolv/Tesla-Menu/releases/tag/v1.2.3
I still don't understand where the error is.
I had hats based on sthetix 16.1 and everything was ok.
Using the latest sthetix hats, everything appears to be up to date (including darkened DNS).
Despite everything, I get the same error on emumcc.
I don't know what to do, forgive my ignorance.7E51A point to Tesla and its overlay module
I don't know what to do, forgive my ignorance.
I tried looking for the update files, but from github I find versions dating back to May.Update your tesla and its overlay or find out which one is causing the crash.