It´s "work" (sleep mode doesn´t work on emunand. But the CFW will boot).
Is there a reason the fuse check hasn't been patched out of CFW warm-boot?
Warmboot binary checks your fuses. If they are equal or less than needed, sleep mode works. Otherwise doesn't.
So if you updated to 5 or 6 and burnt fuses, and go back to 4 or 5, it will not work.
Unfortunately this can't be patched, because warmboot is signed with nintendo's private key. So any modification to that binary, also breaks sleep mode.
I suppose that using a warmboot from another version may work. Never tried that though.
With hekate you can do this. Dump a warmboot that matches your fuses and use that on the downgraded one.
warmboot={SD path}
And then create a patch for secmon, so it will use the correct PA segment for warmboot (also checked together with efuses).
Yep, I'm able to boot into my SD emuNAND on 5.x with my clean NAND on 6.2.
To anyone with AUTORCM: Booting into "original firmware" with SX OS results in a black screen though, so AUTORCM isn't very helpful right now with SX OS.
I'm on the exact same boat as you, I've created an emunand already so my sysnand and emunand are 5.1I'm still on 5.1 so I'd like to do this. I'm assuming the process is as simple as: create SD emunand, remove SD card, update console to 6.2?
So just like if you put SysNAND into sleep mode on a firmware lower than the fuse count, EmuNAND will also crash if put into sleep mode when running a firmware lower than the fuse count.
So to be sure, if i update to 6.2 on OFW i can launch EmuNAND with 6.1 but sleep mode wont work, right?
This seems like a fair trade off.yes, im using Original NAND with 6.2 , and SD EmuNAND 6.1 ...
i dont use autorcm, so if i want to boot original, i just switch on. if i want sxos i do the rcm everytime and boot CFW with EmuNAND.