For downgrading, you don't need any 6.2-specific keys but if you haven't dumped your biskeys yet you will need to use the latest biskeydump to extract them.Thank you very much. I will follow the guides to a T and will report back if everything went OK or not.
Edit: Sorry to bother you again @Draxzelex, but the guide says I need to prepare the keys.txt. I read that 6.2. has changed some keys. (elmirorac tweet).
Do I need the new keys from 6.2 in my keys.txt or are tweeted ones not necessary for the downgrade and I can use the old ones I found (starting with master_key_00 = C2CAAFF0... )?
There are no games with that firmware. You can use xbins to get the firmware files instead.Can anyone point me in the direction of where I can get the exfat driver for 6.0.0 or, for any version above 6.0.0 but below 6.2.0 please? I can't find any games which need 6.0.0 to get the driver from, and the switch I got today has 6.0.0 on it, I'm hoping to get exfat so I don't need to mess about with splitting files.
If you don't want to factory reset the console and go online, you put yourself in a Catch 22 situation since those are the primary ways of removing the User. You can try DevMenu but I'm not sure if that will work.Hi,
I've already unlinked my primary console from my hacked switch, and I'd like to remove my linked Nintendo Account from my User on my switch. Am I too late for this now that I've disabled any internet access. Am I safe enough from any Nintendo repercussions if they ban the console. Currently, my switch has my user, then my linked nintendo account. Although I removed this console from the linked account after i hacked it. But i've never been online since, so it still thinks i'm linked to my nintendo account.
Is there a manual way to delete this user? Are there any suggestions? I just want my hacked switch to not have any record of my nintendo account. But I've started some games on a separate account on the console, so a factory reset wouldn't be ideal.
Whoever told you that is not aware that RCM is triggered before the NAND so theoretically there should be no traces on the console. However if we're being 100% unbiased, there is always a chance that something gets logged in the system even when using Hekate. And if that's the case, its impossible to remove these traces.Hi again,
This is just a question to sate my own curiosity. Earlier in the thread I asked about restoring a NAND using hekate with no trace of CFW on it to go back online. I was told that this wasn't safe to do and that it is still a ban risk. If this is the case, where else are these traces of CFW / logs stored if not on the NAND?
Atmosphere's EmuNAND will be different as it will be a 1:1 copy of the entire NAND on the SD card as opposed to SX OS that only duplicates the USER partition.Are there any concerns about sx os' sd card emuNAND? i know that there were worries about it when it was on the partition of the sysNAND. and I remember long ago people worrying about sx os because it's not open source so people can't see exactly how their things work. Will the upcoming atmopshere emuNAND be fundamentally any different than sx os' current emuNAND?