Update: Since Atmosphere has released with 7.0.X support, To downgrade without a backup, just use ChoidujourNX.
For those with backups you can still follow the method below

---

After seeing reports of downgrading back to 6.2 been broken after updating to switch firmware version 7.0, I can confirm these to be false. I successfully downgraded my switch with 9 burnt fuses on 7.0 to 6.2 with 9 burnt fuses

Downgrading to 6.2 is possible and not broken. Both boot0/boot1 must be the same version as nand backup

• Step 1) Place 6.2 nand + boot0/1 backup on sd card
• Step 2) Boot into RCM and launch hekate
• Step 3) Restore boot 0/1
• Step 4) Restore GPP Partitions (or rawnand, I personally used GPP Partitions)
• Step 5) Launch CFW using Hekate 4.6 or ReiNX 2.0 or sxos (haven't tested with fusee-primary)
• Step 6) ????
• Step 7) Profit

EDIT: This is for FG consoles not ipatched
EDIT 2: You will loose any saves you don't have backed up

Will upload proof if people desperately wish

 

[Jellykrop]

Interesting to know that it can be done. Thanks for the info.

 

[Phenj]

Thanks for the debuking

 

[Adran_Marit]

Interesting to know that it can be done. Thanks for the info.

I should note this is for FG consoles not ipatched

 

[Jellykrop]

I should note this is for FG consoles not ipatched

Mine is unpatched and on 6.2, not planning to update anytime soon.

 

[Adran_Marit]

Mine is unpatched and on 6.2, not planning to update anytime soon.

Probably for the best Also if you don't have a backup I suggest doing one

 

[Jellykrop]

Probably for the best Also if you don't have a backup I suggest doing one

I do have a backup that I made when as was on 4.1, but I was wondering, if one day I would like to downgrade back to 4.1, could I use my backup as it was made before autoRCM was enabled? I would assume it would boot straight to OFW and possibly cause problems?

 

[Adran_Marit]

I do have a backup that I made when as was on 4.1, but I was wondering, if one day I would like to downgrade back to 4.1, could I use my backup as it was made before autoRCM was enabled? I would assume it would boot straight to OFW and possibly cause problems?

yeah it won't boot if the fusecount is mismatched, like if the fuses are lower it's fine but if its higher you would need to boot using hekate stock then upgrade officially

 

[Jellykrop]

yeah it won't boot if the fusecount is mismatched, like if the fuses are lower it's fine but if its higher you would need to boot using hekate stock then upgrade officially

No fuses were burnt since I updated using ChoiDuJour

 

[Zumoly]

I'm pretty much sure those who claim they are bricked have not the full NAND backup i.e the Boot0/1 files.

 

[Adran_Marit]

I'm pretty much sure those who claim they are bricked have not the full NAND backup i.e the Boot0/1 files.

yea, They can be repopulated but it's a bit harder to do, I did it when 6.2 dropped

 

[tidusboy21]

i'm trying to restore my backup (FW 6.1.0) from 7.0 by using SX OS and after that i will try to boot into CFW and installing FW 6.1.0 that i downloaded from internet Source. If it work i will let everyone know.

 

[linuxares]

Can people STOP updating to 7.0 and wait for CFW instead?

 

[Cava]

Can people STOP updating to 7.0 and wait for CFW instead?

Why is this such a big problem? Emunand still works right? Ohh sorry... no SXOS users here?

 

[Hayato213]

After seeing reports of downgrading back to 6.2 been broken after updating to switch firmware version 7.0, I can confirm these to be false. I successfully downgraded my switch with 9 burnt fuses on 7.0 to 6.2 with 9 burnt fuses

Downgrading to 6.2 is possible and not broken.

• Step 1) Place 6.2 nand + boot0/1 backup on sd card
• Step 2) Boot into RCM and launch hekate
• Step 3) Restore boot 0/1
• Step 4) Restore GPP Partitions (or rawnand, I personally used GPP Partitions)
• Step 5) Launch CFW using Hekate 4.6 or ReiNX 2.0 (not tested with sxos)
• Step 6) ????
• Step 7) Profit

EDIT: This is for FG consoles not ipatched

Will upload proof if people desperately wish

Well fuse count would be mismatched, he wouldn't be able to boot into OFW, reason it work because he is booting into CFW like Rei NX.

 

[markiemark]

After seeing reports of downgrading back to 6.2 been broken after updating to switch firmware version 7.0, I can confirm these to be false. I successfully downgraded my switch with 9 burnt fuses on 7.0 to 6.2 with 9 burnt fuses

Downgrading to 6.2 is possible and not broken.

• Step 1) Place 6.2 nand + boot0/1 backup on sd card
• Step 2) Boot into RCM and launch hekate
• Step 3) Restore boot 0/1
• Step 4) Restore GPP Partitions (or rawnand, I personally used GPP Partitions)
• Step 5) Launch CFW using Hekate 4.6 or ReiNX 2.0 (not tested with sxos)
• Step 6) ????
• Step 7) Profit

EDIT: This is for FG consoles not ipatched

Will upload proof if people desperately wish

I updated my Switch in error yesterday, it was forced with a Digital game update and I just started with CFW.

Had a full NAND backup with SX OS at 6.2 and restored but unable to boot now, any advice for a newbie on how to resolve please ?

 

[Cardo360]

I have just tried this process and now I cannot boot into RCM, restored both Full NAND and Boot 0/1 6.2. My switch will not turn on to OFW or RCM to launch Hekate 4.6. Any suggestions?

UPDATE: The tablet was actually on and didn't realized it since it now shows a blank screen on OFW, held power button for about 15 seconds and tried RCM again and it worked, all good here!

 

[Adran_Marit]

I updated my Switch in error yesterday, it was forced with a Digital game update and I just started with CFW.

Had a full NAND backup with SX OS at 6.2 and restored but unable to boot now, any advice for a newbie on how to resolve please ?

Try using hekate to chainboot sxos if you can still get into RCM

I have just tried this process and now I cannot boot into RCM, restored both Full NAND and Boot 0/1 6.2. My switch will not turn on to OFW or RCM to launch Hekate 4.6. Any suggestions?

UPDATE: The tablet was actually on and didn't realized it since it now shows a blank screen on OFW, held power button for about 15 seconds and tried RCM again and it worked, all good here!

Glad you got it sorted

--------------------- MERGED ---------------------------

Can people STOP updating to 7.0 and wait for CFW instead?

Yeah it's a rule but newbies to the scene might not know. Don't update until new cfw is out people

I updated for testing purposes of downgrading and other reasons

 

[TheBloodstomper]

Is there a way to download the backup os someone else? A friend of mine updated the swith by mistake...

 

[Adran_Marit]

Is there a way to download the backup os someone else? A friend of mine updated the swith by mistake...

Just commented on the post