Hacking Sysnand updated to 8.0.1 - Switch not starting anymore

[hhrocha]

hmm ok, so if i understand in my case (i never have my switch hacked before), im in 8.0.0 and i wanna hack it now, i will need to downgrade it first to 7.0.0/1 do a emunand with the license of SXOS and update the Sysnand to 8.0.0 again to preserve the online? Am i right? (Sry im new in this)

 

[Draxzelex]

hmm ok, so if i understand in my case (i never have my switch hacked before), im in 8.0.0 and i wanna hack it now, i will need to downgrade it first to 7.0.0/1 do a emunand with the license of SXOS and update the Sysnand to 8.0.0 again to preserve the online? Am i right? (Sry im new in this)

If you want to setup EmuNAND now and don't have any patience, then yes. Otherwise you can wait until TX releases a version of SX OS that supports 8.X which will be who knows how long now considering both Atmosphere and ReiNX both support 8.X

 

[hhrocha]

If you want to setup EmuNAND now and don't have any patience, then yes. Otherwise you can wait until TX releases a version of SX OS that supports 8.X which will be who knows how long now considering both Atmosphere and ReiNX both support 8.X

Thanks Will do that when i get home, Any advice to the process?

 

[Draxzelex]

Thanks Will do that when i get home, Any advice to the process?

Well you have 2 routes for downgrading:

1. The first one is a bit lengthy and only supports downgrading to a firmware of 6.1 or lower. This involves ChoiDujour, a PC program that turns firmware files into parts of the NAND you flash via another tool known as hacdiskmount. The tutorial of which can be located here. The only reason I bring this one up is because it doesn't involve running any CFW or homebrew which keeps your SysNAND clean. If you are to follow this tutorial, I recommend dumping the keys in Step 6 using Lockpick_RCM
2. The second method is faster but risks tainting your SysNAND. It involves using the homebrew application with a similar name, ChoiDujourNX. Since you're already on 8.0, you will need a CFW to launch ChoiDujourNX. Your choices are Atmosphere or ReiNX as both support 8.X but since you will only temporarily be using these, the choice of CFW does not really matter. As mentioned, using ChoiDujourNX involves running CFW and homebrew which can taint your SysNAND. If you still want to use this method to downgrade instead of the first one but don't want to dirty SysNAND, make a complete NAND backup with Hekate before doing anything else (meaning boot0/boot1 as well as eMMC raw GPP). Once SX OS releases support for 8.X, you can restore your full NAND backup which will not only bring you back to firmware 8.0 but keep your SysNAND untouched

 

[hhrocha]

Thanks man, will give feedback in a couple hours.

 

[josete2k]

If you want a clean sysnand you have to make a nand backup (sxos can make it, hekate is not required) and restore it after the choidujournx downgrade and emunand creation.

 

[naddel81]

If you want a clean sysnand you have to make a nand backup (sxos can make it, hekate is not required) and restore it after the choidujournx downgrade and emunand creation.

what if your NAND is already "dirty"? how to start fresh without having to delete everything?

 

[josete2k]

If you're dirty you're dirty...

You can try to initialice the system when installing the fat32 firmware (the one you had when the console was officially connected to the Internet).

And pray... Nintendo could be more friendly with regretful users...

 

[hhrocha]

Im getting error 2137-0040 after trying to downgrade from 8.0.0 to 7.0.1 any idea why?

 

[Draxzelex]

Im getting error 2137-0040 after trying to downgrade from 8.0.0 to 7.0.1 any idea why?

Unfortunately I forgot to mention that since you'll be downgrading from 8.0, you'll be downgrading across major firmware versions which requires you to initialize the system which I'm guessing you didn't do. In case you haven't, you will have to manually perform a system initialize which you can do via maintenance mode. To enter maintenance mode, simply hold volume + and - when turning the console on. If you have AutoRCM enabled (which you should since both ChoiDujour and ChoiDujourNX apply AutoRCM automatically), simply hold both volume + and - when using a payload that boots CFW/OFW.

 

[CarefulCrysis]

I saw one person claiming AutoRCM to be the culprit here which is beyond insane so just to make sure everyone is on the same page, this is due to SX OS not supporting launching "OFW" on firmware 8.X. Their "OFW" option is not really true OFW which would just be turning the console on normally without AutoRCM. For one, their OFW option bypasses the fuse check meaning it lets you launch an OFW with any fuse count. This means its just a very watered down version of CFW mode further indicating they must patch parts of the firmware in order to launch "OFW". Now if their CFW doesn't support that firmware, obviously "OFW" won't even work. Note the fault is not on AutoRCM before anyone gets any ideas as Hekate can launch its "Stock" profile on 8.X just fine, after version 4.10 was released.

tl;dr SX OS currently does not support launching CFW or "OFW" on 8.X

lol you could have just said SX OS isn't supported like I speculated a few posts back

 

[hhrocha]

Unfortunately I forgot to mention that since you'll be downgrading from 8.0, you'll be downgrading across major firmware versions which requires you to initialize the system which I'm guessing you didn't do. In case you haven't, you will have to manually perform a system initialize which you can do via maintenance mode. To enter maintenance mode, simply hold volume + and - when turning the console on. If you have AutoRCM enabled (which you should since both ChoiDujour and ChoiDujourNX apply AutoRCM automatically), simply hold both volume + and - when using a payload that boots CFW/OFW.

Didn't work, im restoring my nand. i will forget the online and stay with the atmospher OS in offline mode
thanks

 

[Draxzelex]

lol you could have just said SX OS isn't supported like I speculated a few posts back

I know but I have seen others quick to pin the blame on anything towards AutoRCM whether its SysNAND not launching on 8.0 pre-v2.7.1 or draining battery in sleep mode. AutoRCM is not the devil that people make it out to be.