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

 

[eskinner3742]

No fuses were burnt since I updated using ChoiDuJour

If you updated to 6.2 using Choidujour then you can simply restore your boot0/1 and NAND and boot normally with no issue. I've taken a 4.1 to 5.1 then back. Then to 6.2 and back. No issues as long as fuse count matches.

 

[starlemming]

I have this files. I am ready to downgrade? Thanks!

 

[Adran_Marit]

6.2 nand and boot 0/1 of the same console or from any 6.2 console?

Same console, if you don't have them you need to do the old downgrade method

it is possible to downgrade from 7.0 if I do not have 6.2 backup? I know, this is desesperate

Wait for 7.0 or see above

I have this files. I am ready to downgrade? Thanks!

you need to join the .bin.00 files using the script

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

@starlemming You should end up with a single 29 gig file called rawnand.bin

 

[starlemming]

Same console, if you don't have them you need to do the old downgrade method



Wait for 7.0 or see above




you need to join the .bin.00 files using the script

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

@starlemming You should end up with a single 29 gig file called rawnand.bin

Thank you for the reply!

Now I have boot0, boot1 and rawnand. I need to put in some specific folder in the root of my SD?

 

[Adran_Marit]

Thank you for the reply!

Now I have boot0, boot1 and rawnand. I need to put in some specific folder in the root of my SD?

yes

From your number and letters folder inside the backup folder on pc, copy the below files to the restore folder on your SD card


- Boot 0
- Boot 1
- rawnand.bin


Example on sd card
inside The folder on SD card Backup>numberletter folder>restore folder <....place files here...

 

[DeJay_Incognito]

yes

From your number and letters folder inside the backup folder on pc, copy the below files to the restore folder on your SD card


- Boot 0
- Boot 1
- rawnand.bin


Example on sd card
inside The folder on SD card Backup>numberletter folder>restore folder <....place files here...

The reason that all the backup files are not already in restore is because the developers are IQ checking users. It also stops any mistakes with resets (which has killed me once).

 

[Adran_Marit]

The reason that all the backup files are not already in restore is because the developers are IQ checking users. It also stops any mistakes with resets (which has killed me once).

meanwhile mine are always there as I test some dangerous stuff and can recover in a heartbeat lol

 

[DeJay_Incognito]

meanwhile mine are always there as I test some dangerous stuff and can recover in a heartbeat lol

Are you on the latest Hekate? Dumb Question: I saw the model number folder thingy, you probably are. I wish I didn't have the restore folder issue.

 

[Adran_Marit]

Are you on the latest Hekate? Dumb Question: I saw the model number folder thingy, you probably are. I wish I didn't have the restore folder issue.

yeah 4.6

As I said I keep a nand backup on the ready on my sd for quick restoring

so SD:\backup\*nandID*\Restore

 

[giger2000]

Same console, if you don't have them you need to do the old downgrade method



Wait for 7.0 or see above




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

@starlemming You should end up with a single 29 gig file called rawnand.bin

I have seen the method that comments but I do not understand if it can be done with a console with 7.0 and that I have never used backup methods.

that is, I have an original with 7.0 that I want to download to 6.2. could you help me?

 

[Adran_Marit]

I have seen the method that comments but I do not understand if it can be done with a console with 7.0 and that I have never used backup methods.

that is, I have an original with 7.0 that I want to download to 6.2. could you help me?

I would just wait, especially if you aren't confident in your modding ability, one wrong click can mess the switch up more, but if you are confident then I linked the other tutorial in the comments somewhere

 

[giger2000]

I would just wait, especially if you aren't confident in your modding ability, one wrong click can mess the switch up more, but if you are confident then I linked the other tutorial in the comments somewhere

I think I'll wait. I have the sx pro and I guess they will do something soon. Thank you

 

[Adran_Marit]

I think I'll wait. I have the sx pro and I guess they will do something soon. Thank you

SX already have support for emunand 6.1 with 7.0, you might be best then enquiring on their latest release post

 

[giger2000]

SX already have support for emunand 6.1 with 7.0, you might be best then enquiring on their latest release post

I have not created any emunand.
Yesterday I wanted to use the SX for the first time but the console was updated.

 

[Jaucent23]

Booted into SX 6.2 emunand and attempted to update Emunand 7.0, now Emunand only boots to black screen, any way to remove the update file from the emunand without having to delete and re setup emunand, or it is just a matter of playing the waiting game for Emunand 7.0 support?

 

[Adran_Marit]

Booted into SX 6.2 emunand and attempted to update Emunand 7.0, now Emunand only boots to black screen, any way to remove the update file from the emunand without having to delete and re setup emunand, or it is just a matter of playing the waiting game for Emunand 7.0 support?

SXOS only support 6.2 emunand for now, so unless you want to wait for that 7.0, it might be re-setup emunand. though you would be better asking in a sxos forum for more info

 

[starlemming]

yes

From your number and letters folder inside the backup folder on pc, copy the below files to the restore folder on your SD card


- Boot 0
- Boot 1
- rawnand.bin


Example on sd card
inside The folder on SD card Backup>numberletter folder>restore folder <....place files here...

Is it necessary for my SD to be in exfat?

 

[Adran_Marit]

Is it necessary for my SD to be in exfat?

Yes for restoring. For normal use though fat32 is recommended

 

[Jaucent23]

SXOS only support 6.2 emunand for now, so unless you want to wait for that 7.0, it might be re-setup emunand. though you would be better asking in a sxos forum for more info

Thank you for the response, I will try to backup emunand, then delete and retore the backup of the emunand, to see if that can be a workaround, (just dont want to reinstall all the games again )

 

[MaverickOne]

sorry but why all this noise if 7.0.0 is open?
PK11: 434FA7D07A8D4FDFD8630AC40FF9BC697E0DE40E0041E225F154BEB9571044E9
Master key: 4EC96B8CB01B8DCE382149443430B2B6EBCB2983348AFA04A25E53609DABEDF6
does anyone confirm?