Just checking back to report on my "failed to match warmboot" message error. It was indeed fixed by updating my emuMMC FW to 12.0.2 through Daybreak to match my sysMMC which is also on 12.0.2, thank you again @Draxzelex for your kind help. As of writing my Atmosphere is on 0.19.3/Hekate v5.5.6...
In this guide I am reading it says to use TegraExplorer to dump the sysMMC firmware and then use that to update the emuMMC, would that be the best/correct way to go about that to your knowledge? Before when I updated my emuMMC FW to 12.0.1 I had used publicly available FW files so I hadn't gone...
Thank you, I will give that a try. I assume we are not allowed to discuss sources here but I can only see 12.0.1 on the site I use, would TegraExplorer be the best option if I want to make my own backup?
Thank you for your reply. Apologies as I meant I have since upgraded the emuMMC's firmware to 12.0.1 with Daybreak whereas the sysMMC is currently on 12.0.2. I'm still a noob especially with Atmosphere so hope that makes sense. I'm using the latest Atmosphere ver 0.19.3 (when I switched over...
I'm having maybe similar errors as the user above "Failed to match warmboot with fuses, if you continue sleep won't work". If I override the error it boots and runs backups fine, but going into sleep locks the unit until restarted. I recently switched from SXOS to Atmosphere on my Mariko SX Core...
Only thing drive me crazy is all these new horror games nowadays is its so dark, all time. I can't even play them. I understand they trying to create spooky but be creative a little, not just darkness with pop out scare scenes.