Hacking Question Lost with this sxcore mariko switch. dont know where to start

[k28]

i installed the sxcore just 7 month ago. sys and emunand was working properly. the owner decided to update ofw above fw 11.0.1 then brought the console to someone to fix? the mess and now both nands arnt booting. black screen after sx logo. i can still launch sx recovery and hekate. launching emummc via hekate gives the error: emummc is forced but not enabled. trying to launchcfw sysnand gives the error: pkg1 decryption failed is BEK missing?

before i make things more complicated i wanted to ask for your advice. how should i proceed? thx in advance!

 

[raging_chaos]

Whomever tried to fix probably didn't migrate completely. Start over fresh and follow any of the SX to Atmosphere guides for Mariko. They have pretty much lost the ability to ever use SXOS and XCI loading since they are on Mariko and updated sysnand, they will inevitably ask about it.

 

[GothicIII]

This is messed up.
Typically pkg1 decryption failed is pinpointing to a firmware mismachted boot0/1 partition. You'd need to restore those with a backup which is suitable for the firmware installed on the switch. The good news is that boot0/1 can be used from a different switch.
BUT: I don't know if you can do it on a Mariko unit without bricking it for good.

I also don't know how the modchip works but I would say if sysnand is updated then you'll have a bad time running CFW on it again.

 

[k28]

the issue with this switch was that the emunand was updated above 11.0.1. no bootoption would work. that confused me.

after following this tutorial(mariko // Emunand migration methode). stock nand and emunand would boot but with an error message that some file arent warm or so lol. after updating both nand everything is working fine. thx for the help

 

[Draxzelex]

the issue with this switch was that the emunand was updated above 11.0.1. no bootoption would work. that confused me.

after following this tutorial(mariko // Emunand migration methode). stock nand and emunand would boot but with an error message that some file arent warm or so lol. after updating both nand everything is working fine. thx for the help

Its referring to the warmboot. Warmboot refers to bootup while the system is on, or warm. The only bootup relevant is Sleep Mode. The reason its referring to warmboot is because there is also a fuse check at warmboot so if the fuses do not match, the console will not awaken from Sleep Mode. This is a non-issue on Erista units because Dormeux Vu (part of the exploit chain of Deja Vu) bypasses the fuse check. This exploit also allows Erista consoles to reboot to a payload without turning the console off. However this is patched in Mariko units hence why rebooting to a payload doesn't work on those systems. As for making Sleep Mode work, Atmosphere makes a backup of the warmboot.bin and reads that when the console awakens from Sleep Mode.