Hacking How to downgrade Nintendo Switch firmware 6.2.0?

[sj33]

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.

 

[Thetoto]

Wait, do you mean it's possible to downgrade by restoring nand backup ?

It's not a downgrade, it's a brick. You'll have to boot with RCM mode.

 

[Hellboybeats]

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

*6.1.0/6.2.0

 

[Perfect One]

Wait, do you mean it's possible to downgrade by restoring nand backup ?

Not in 6.2.0 yet.

 

[alkar]

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)

 

[Draxzelex]

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)

It was literally the first response...

 

[alkar]

indeed but yet people flamed him and this was lost among the flaming posts "omg you didn't do a nand backup".

And this is a link to a tutorial so..even better!

Enjoy your NSW back to 6.1.0 and screw flamers

 

[FortalezaG]

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.

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 it
on sleep mode.

 

[larrypretty]

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.

Thanks, I hope so, no matter the TX or SciresM, I wish they can release an update soon.

 

[mdmachine]

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...

 

[larrypretty]

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...

"the new key encryption being offloaded to the chip, it may NEVER get reversed", how do you know it?

 

[ZachyCatGames]

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

*6.1.0/6.2.0

The edit message feature exists for a reason

 

[EmulateLife]

"the new key encryption being offloaded to the chip, it may NEVER get reversed", how do you know it?

Because the one trying to hack it says it's difficult and gave Nintendo credit for how they updated the keys. If a hacker is giving the console maker credit, you can probably bet we're in for a long wait.

PS3 needed 3.55 firmware for years, you never know.

 

[ccfman2004]

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.

 

[mdmachine]

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.

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.

 

[ccfman2004]

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. I 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.

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.

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)

 

[Asia81]

I 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?

karma

 

[k7ra]

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.

Wait, there no other way to add it? exFAT update
I still not update console and not hack it

 

[ccfman2004]

Wait, there no other way to add it? exFAT update
I still not update console and not hack it

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.

 

[dotdissent]

I have a similar question, if it's okay I hijack for a moment;

I have a backup from pre-6.0 before I hacked it to mess around with homebrew briefly. Let's Go updated me to 6.2 today, I didn't realize it was not just a title update. So here's my question;

Am I currently locked of RCM booting to something like Hekate and NAND dumping my current 6.2, downgrading to that pre-6.0 backup, then when I'm done messing around with homebrew restoring that 6.2 NAND?