I wonder how they could not test their usb support properly before releasing... even if it’s an BETA.
I’ll stay on my 6.2. Emunand with 2.5.3. stable and 7.0.1. sysnand
My right joycon has some issues when I play solo with it. Every now and then the buttons don't accept any input for a few seconds. When I play with it in handheld or plugged to the joycon grip there are no problems. Any idea what might solve this issue?
I did the downgrade from 7.0.0. to 6.2.0. without factory reset and everything worked perfectly. Why is it strongly advised?
I still did not power off the switch since I downgraded and now I'm planning to create EmuNAND 6.2.0. and then restore my NAND backup from before the downgrade to avoid...
Okay, so as far as I understand:
currently 9 fuses are burnt because switch was on 7.0.0.
Creating an EmuNAND of my current 6.2. version and then updating sysNAND to 7.0.1. should not cause any problems for EmuNAND usage and with disabling AutoRCM.
After I downgraded I only booted once to CFW with RCM mode.
So if I get that right I just should leave AutoRCM enabled even if I use Emunand and update sysnand back to 7.0 ?
Sorry this eFuse thing is conFUSEing af to me lol...
Hi @All
Can someone explain in what situation my switch is:
- I had a hackable Switch on 7.0.0.
- Loaded AMS with fuse primary on a SX dongle
- Downgraded to 6.2.0. through ChoidujourNX with AutoRCM option and without system initialize option
- Now using SX OS on 6.2.0. - everything is working...
if they get permission from 4j (the studio who helped put minecraft on consoles), they could put the console edition tutorial worlds in the game, as seeds
and i mean all of them (if not, maybe a few highlights, like TU1, TU31, and TU69)