Yes, sort of. You can downgrade but if you've already blown efuses then you will have to load through CFW. OFW will detect the incorrect fuse count, CFW ignores them.
It's not a downgrade, it's a brick. You'll have to boot with RCM mode.Wait, do you mean it's possible to downgrade by restoring nand backup ?
Wait, do you mean it's possible to downgrade by restoring nand backup ?
It was literally the first response...https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/
funny 2 pages of flaming and nobody gave him the solution (or use the search function for that matter)
But in that case the sleep mode will work? I update my switch to 6.2.0 and keep my emunand on 6.1.0. My sysnand works fine. But my emunand crash when a put itYes, sort of. You can downgrade but if you've already blown efuses then you will have to load through CFW. OFW will detect the incorrect fuse count, CFW ignores them.
Thanks, I hope so, no matter the TX or SciresM, I wish they can release an update soon.Don't worry about it too much. The new encryption keys will get released, SciresM is already working on it. There's just no time frame and it might not be soon.
"the new key encryption being offloaded to the chip, it may NEVER get reversed", how do you know it?It's hard to remain calm when the entire boards fill up with the same ish. After the recent pokimon brick fiasco, anyone who uses cfw, and never made a backup & uses these boards, is an idiot. I mean this is a basic rule of thumb since long before the switch existed.
Sucks for the few who really are new and didn't know any better. Also from what I understand, the new key encryption being offloaded to the chip, it may NEVER get reversed, or could take a VERY LONG TIME.
Hopefully not...
So if I back up 6.0.2 ofw and have a 6.0.1 ofw back up and restore to the back up and use rcm to boot cfw until a 6.0.2 fix and then restore the 6.0.2 back up , all should be good right ? Anyone tested thanks a lot
The edit message feature exists for a reason*6.1.0/6.2.0
"the new key encryption being offloaded to the chip, it may NEVER get reversed", how do you know it?
For me I didn't even know that 6.2.0 came out. If something popped up saying update to 6.2.0 I would have canceled. I needed the exFAT update and was already on 6.1.0. It was only after I updated that I saw it was 6.2.0 and not 6.1.0. I'm guessing there is no "Payload" that will let me downgrade yet, huh.
I still have a 6.1.0 Switch that I accidentally busted the screed so I'll just wait for either the new screen to arrive or a new CFW.
Swapping screens is how I busted the screen in the first place. I borked the ribbon cable somehow and all I get is the backlight. I can use it in the Dock at least but the payloads don't work in Dock Mode (unless I'm doing something wrong)Thats a bummer. Instances like that is why with any device, I always look for a way to update firmwares manually whenever possible.
Why dont you swap the screens? Then live in airplane mode.
karmaI never intendo to do this, the system udpate pop out when I'm playing a game, then I just click on it, and regret for my whole life...
--------------------- MERGED ---------------------------
Yes, I don't, so that means I have no way to downgrade, yes?
Wait, there no other way to add it? exFAT updateFor me I didn't even know that 6.2.0 came out. If something popped up saying update to 6.2.0 I would have canceled. I needed the exFAT update and was already on 6.1.0. It was only after I updated that I saw it was 6.2.0 and not 6.1.0. I'm guessing there is no "Payload" that will let me downgrade yet, huh.
I still have a 6.1.0 Switch that I accidentally busted the screed so I'll just wait for either the new screen to arrive or a new CFW.
There is a way to do it but you have the modify some stuff manually. I would have gladly done that if I had known they just pushed a new update. At least with the PS4 you know what the new version is but not Nintendo.Wait, there no other way to add it? exFAT update
I still not update console and not hack it