Separate names with a comma.
My friend can boot into sxos even in dock mode:
But, how can this be possible? This console has dualboot (joycon...
Fuses aren't in the nand backup.
That's because you paired your controller on sysnand (or another console)... The Bluetooth key changed between sysnand and emunand.
Use recovery menu (nintendo) and delete all your configs.
Only emunand on files I guess...
So, has the payload.bin changed?
Drain battery is only in sleep mode?
If so... If we power off the console we wouldn't care about it, isn't it?
But... Could the use of D3 in the past the way to do not get the known USB issues?
D3 was used in the first diagrams for the joycon strap isn't it?
I changed it but I remember that it was working as a joycon strap
So now there's a real (little) drain battery with the rcmx86?
Always or only when sleep mode is active?
I didn't have usb issues... Better to...
But you still need the sd files (in all your sd cards) in order to boot hekate cfw.
So, you can place the switchboot.bin in all your sd cards...
Yeah, it launches payload.bin but I like the idea of storing my license.dat in the chip (and I don't use hekate).
A flag to activate the license...
An auto Fusee-UF2 SXOS version would be great.
Launch fusee, check if license.dat is present and create one if doesn't exist...
Use a fat32 sd.
And install the exfat option in choidujournx.
If you're dirty you're dirty...
You can try to initialice the system when installing the fat32 firmware (the one you had when the console was...
If you want a clean sysnand you have to make a nand backup (sxos can make it, hekate is not required) and restore it after the choidujournx...
I had long time for backup too... Until I tested this MicroSD adapter:
I made a backup with DD in 2 hours... Not bad.
Restoring is faster... Around 45 minutes because I use a bigger block size.
But when your sd becomes corrupt your emunand could be too...
I think it's allowed...