Tutorial  Updated

Switch 7.0 Downgrade to 6.2 tutorial

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
 
Last edited by Adran_Marit,
Noob quesion here: Can i updato to 7.0.1 from 6.2 or do i have to go first 7.0.0?

Are these stepss ok to follow if want to update ofline no burning fuses?

1.png
 
Last edited by jorgesd,
Noob quesion here: Can i updato to 7.0.1 from 6.2 or do i have to go first 7.0.0?

Are these stepss ok to follow if want to update ofline no burning fuses?

1.png

You can just go straight to the new firmware version. Atmosphere supports 7.0.X so yee and yeah, just don't disable autorcm
 
  • Like
Reactions: jorgesd
You can just go straight to the new firmware version. Atmosphere supports 7.0.X so yee and yeah, just don't disable autorcm
last question: will i have sleep mode problemss because i'll have 8 fuses burned but 7.0 required 9 fuses or not because booting with autorcm prevent fuse checks?
 
last question: will i have sleep mode problemss because i'll have 8 fuses burned but 7.0 required 9 fuses or not because booting with autorcm prevent fuse checks?

if you're booting with hekate + chainloading sleep mode should be fine, you won't be able to boot ofw though, only cfw
 
Hello Guys,

I am not a total noob, but still want to be safe, so not to brick my sons Switch.

I have successfully installed atmosphere on my Switch (it was on 7.0 when I bought it (used)). But since atmosphere is not well working with goldleaf or other installers and i can not install any nsp, i want to downgrade from 7.0.1 to 6.0, so I can update to 6.2 with ReiNX.

Am I right to just download Firmware 6.0 and then install it with ChoidujourNX?
 
Hello Guys,

I am not a total noob, but still want to be safe, so not to brick my sons Switch.

I have successfully installed atmosphere on my Switch (it was on 7.0 when I bought it (used)). But since atmosphere is not well working with goldleaf or other installers and i can not install any nsp, i want to downgrade from 7.0.1 to 6.0, so I can update to 6.2 with ReiNX.

Am I right to just download Firmware 6.0 and then install it with ChoidujourNX?

1) MAKE A NAND AND Boot0/1 Backup

2) Use Checkpoint to backup saves

3) Use ChoidujourNX to install 6.2, make sure you choose system initialisation

4) Use the latest files from the reinx guide

5) Restore saves in with checkpoint

Message me or here in the reinx discord if you need help
 
  • Like
Reactions: TunisDream
Like I told you, I am new on Switch, but not a total newbie. Made a full backup yesterday, took about 2 hours..... And saved it into my cloud :)
 
I backed up these two:

eMMC BOOT0/1
eMMC RAW GPP

How do you guys get your MicroSD Card from the switch and do not have to push a Payload via PC?

Everytime I pull the MicroSD Card out from the switch, i get the info that it will shut down (it goes to rcm) and i have to push a payload to boot it again.

is there a workaround?
 
I backed up these two:

eMMC BOOT0/1
eMMC RAW GPP


How do you guys get your MicroSD Card from the switch and do not have to push a Payload via PC?

Everytime I pull the MicroSD Card out from the switch, i get the info that it will shut down (it goes to rcm) and i have to push a payload to boot it again.

is there a workaround?

FTP or power off the switch. You can take the sd card in and out in RCM
 
Questions man.. To the ones ive downgraded.. If i want to revert it back to ofw 7.0..can i just conect it to wifi then update or will i need to restore the nand backup? Tia
 
Hi,
Successfully restored by 6.1 nand backup and was able to boot in cfw and then used choiNX to install 6.2 which was the firmware I was on before my son updated the switch to 7.0.
Problem I have no is that I cannot boot in SXOS. I can boot into Hekate but I don't know how to boot into SXSO from there.
If I try to boot into the usual way, using the dongle and jig, I just get black screen.
The boot.dat file is on the SD card and the dongle is fully charged.
Any ideas what I am doing wrong?
Thanks.
 
Hi,
Successfully restored by 6.1 nand backup and was able to boot in cfw and then used choiNX to install 6.2 which was the firmware I was on before my son updated the switch to 7.0.
Problem I have no is that I cannot boot in SXOS. I can boot into Hekate but I don't know how to boot into SXSO from there.
If I try to boot into the usual way, using the dongle and jig, I just get black screen.
The boot.dat file is on the SD card and the dongle is fully charged.
Any ideas what I am doing wrong?
Thanks.

sysnand has been updated, downgrade again to 6.1/6.2 using the backup and setup emunand which can be updated using the latest sxos
 
sysnand has been updated, downgrade again to 6.1/6.2 using the backup and setup emunand which can be updated using the latest sxos

I never used emunand. My switch was running 6.2 before the accidentally update to 7.0. No emunand.
The only backup I had was a 6.1 version I took just before I added to 6.2 using Choi.
The steps I took were:
Booted in Hekate 4.2 (which was the version I was running when I took the backup)
Restored boot
Restored rawnand
Enabled autocrm in hekate
Launched CFW in hekate, which booted in atmosphere from the looks of it. I must have had atmosphere files on my SD card.
From there I installed 6.2 exfat (which is how I originally updated from 6.1) via choi then rebooted
I can get in hekate but can't boot in SXOS and CFW isn't working either.
Tried with Hekate 4.2, 4.6 & 4.8

UPDATE - I got it working by downloading SXOS Loader 1.0 and putting the payload.bin into the payload folder of the Hekate bootloader folder on my SD card. Then booted in Hekate, launch, payload and selected the payload.bin file I copied. Tested a copy of XCI and NSP games and they worked fine. Phew.
 
Last edited by morpheus9394,
  • Like
Reactions: Adran_Marit
I never used emunand. My switch was running 6.2 before the accidentally update to 7.0. No emunand.
The only backup I had was a 6.1 version I took just before I added to 6.2 using Choi.
The steps I took were:
Booted in Hekate 4.2 (which was the version I was running when I took the backup)
Restored boot
Restored rawnand
Enabled autocrm in hekate
Launched CFW in hekate, which booted in atmosphere from the looks of it. I must have had atmosphere files on my SD card.
From there I installed 6.2 exfat (which is how I originally updated from 6.1) via choi then rebooted
I can get in hekate but can't boot in SXOS and CFW isn't working either.
Tried with Hekate 4.2, 4.6 & 4.8

UPDATE - I got it working by downloading SXOS Loader 1.0 and putting the payload.bin into the payload folder of the Hekate bootloader folder on my SD card. Then booted in Hekate, launch, payload and selected the payload.bin file I copied. Tested a copy of XCI and NSP games and they worked fine. Phew.

glad ya got it working
 
Hello...

I got a used stock switch this week in version 7.0.... I used a tutorial, backup the nand and downgrade to 6.2 atmosfere.... everything is ok...
My question is: After that can i install SX OS? Its possible to back my switch to original 7.0?

thx!
 

Site & Scene News

Popular threads in this forum