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

 

[Adran_Marit]

for a cfw update. i read like 1-2 weeks for 7.0?

for atmosphere it was quoted for a few days to weeks, basically it already has support if you have the 7.0 key, if not he's working on a version that doesn't need it which should be out in that time frame.

Reinx won't be far behind once they keys are know and sxos will follow after that

 

[C0sm1c]

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
EDIT 2: You will loose any saves you don't have backed up

Will upload proof if people desperately wish

I was able to restore firmware from a NAND backup and was able to boot it up to stock firmware. Then i powered if off and tried to instlal custom firmware again and now it wont turn on. just shows black screen. no charging indicator or anything. i did upgrade to 7by accident and had a nand backup of 6.2. did i brick my console?

 

[Adran_Marit]

I was able to restore firmware from a NAND backup and was able to boot it up to stock firmware. Then i powered if off and tried to instlal custom firmware again and now it wont turn on. just shows black screen. no charging indicator or anything. i did upgrade to 7by accident and had a nand backup of 6.2. did i brick my console?

hold power for 15 seconds and try to enter RCM again

also did you restore boot 0/1

 

[C0sm1c]

hold power for 15 seconds and try to enter RCM again

also did you restore boot 0/1

Yes i did restore boot 0/1 and tried the 15 second issue and nothing.

 

[Adran_Marit]

Yes i did restore boot 0/1 and tried the 15 second issue and nothing.

So what is your stock firmware right now? 6.2 or 7.0

 

[C0sm1c]

So what is your stock firmware right now? 6.2 or 7.0

It was 6.2 when i did the full stock nand backup prior to any custom firmware. When i did initally turn off my console to copy the files to install custom firmware. I did copy all the files from the zip file for custom firwmare. Perhaps thats what i did wrong?

 

[Adran_Marit]

It was 6.2 when i did the full stock nand backup prior to any custom firmware. When i did initally turn off my console to copy the files to install custom firmware. I did copy all the files from the zip file for custom firwmare. Perhaps thats what i did wrong?

Can you boot hekate and tell me the burnt fuse count

 

[C0sm1c]

Can you boot hekate and tell me the burnt fuse count

i can't boot anything, not even the pc detects it. kept it on the charger and nada. i think i did brick it

 

[Adran_Marit]

i can't boot anything, not even the pc detects it. kept it on the charger and nada. i think i did brick it

disconnect from power, hold power button for 20 seconds, reboot into RCM and if that doesn't work, leave it on charge for an hour and try again

 

[C0sm1c]

disconnect from power, hold power button for 20 seconds, reboot into RCM and if that doesn't work, leave it on charge for an hour and try again

ok ill check in the morning,

 

[coppertj]

This helped alot, i accidentally updated thinking this update has been out for a while (when in reality it was freshly updated) i literally had complete protection on my switch 90dns etc., and I updated with my friend through the friend share thing. Broke everything and that was like 1 1/2 weeks ago. I thought I was SOL for a while when I noticed I had a nand backup in a random folder on my computer that I must have done a long time ago because the nand backup was 5.1! thank you lol

 

[Adran_Marit]

This helped alot, i accidentally updated thinking this update has been out for a while (when in reality it was freshly updated) i literally had complete protection on my switch 90dns etc., and I updated with my friend through the friend share thing. Broke everything and that was like 1 1/2 weeks ago. I thought I was SOL for a while when I noticed I had a nand backup in a random folder on my computer that I must have done a long time ago because the nand backup was 5.1! thank you lol

Glad to help, if you're unsure make a new backup on 6.2 and don't forget to upload it multiple places

 

[spotanjo3]

I never understand people wanting to upgrade to 7.0 then said uh-oh I better downgrade it. I dont upgrade it until CFW developer said its okay to upgrade. SMH.

 

[coppertj]

Glad to help, if you're unsure make a new backup on 6.2 and don't forget to upload it multiple places

yeah I have it on my dropbox, google drive, emailed to my yahoo, uploaded to my server, this ain't getting lost again (i've bricked my 2ds by not backing up

I never understand people wanting to upgrade to 7.0 then said uh-oh I better downgrade it. I dont upgrade it until CFW developer said its okay to upgrade. SMH.

because i wanted to play smash on lan and was out at the time...?

 

[Adran_Marit]

I never understand people wanting to upgrade to 7.0 then said uh-oh I better downgrade it. I dont upgrade it until CFW developer said its okay to upgrade. SMH.

some people update by accident, or a family member etc etc.

I know I deliberately updated because I knew I could go back :3

 

[C0sm1c]

disconnect from power, hold power button for 20 seconds, reboot into RCM and if that doesn't work, leave it on charge for an hour and try again

Well i dont know what happend but i charged it overnight and still nothing happened. I plugged in my jig and finally i got a computer sound detected and was able to boot into cfw for 6.2. Is there any settings i need to change to make sure i can boot using RCM and the jig next time? or is it just better idea to upgrade to 7.0 so it can boot properly and hopefily CFW comes to 7.0 soon? any suggestions or ideas?

 

[Adran_Marit]

Well i dont know what happend but i charged it overnight and still nothing happened. I plugged in my jig and finally i got a computer sound detected and was able to boot into cfw for 6.2. Is there any settings i need to change to make sure i can boot using RCM and the jig next time? or is it just better idea to upgrade to 7.0 so it can boot properly and hopefily CFW comes to 7.0 soon? any suggestions or ideas?

do not update. Do you have autoRCM? if the console goes flat with autoRcm it can take a bit to get going again

 

[C0sm1c]

do not update. Do you have autoRCM? if the console goes flat with autoRcm it can take a bit to get going again

i believe so how do i check ?

 

[Adran_Marit]

i believe so how do i check ?

boot hekate, click tools, then autorcm and it will say enabled or disabled

 

[C0sm1c]

boot hekate, click tools, then autorcm and it will say enabled or disabled

do i enable or keep it disabled? after that any other suggestions?