Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,721,175
  • Replies Replies 9,253
  • Likes Likes 92
Weird, I updated (literally just copied the zip contents and overwrote the SD card existing files) and now none of my installed games work, I've got the patches in the atmosphere folder, but not one game works, they're all working still on sxos, any ideas?

I should have added, this is on FW 6.2
 
Last edited by PC_Arcade,
Weird, I updated (literally just copied the zip contents and overwrote the SD card existing files) and now none of my installed games work, I've got the patches in the atmosphere folder, but not one game works, they're all working still on sxos, any ideas?

I should have added, this is on FW 6.2

Same, I'm on FW 6.2 too
 
Weird, I updated (literally just copied the zip contents and overwrote the SD card existing files) and now none of my installed games work, I've got the patches in the atmosphere folder, but not one game works, they're all working still on sxos, any ideas?

I should have added, this is on FW 6.2
Same, I'm on FW 6.2 too
After i updated to 0.8.6 Kirby star allies is crashing, anyone else?
There seems to be a problem with signature patches on 0.8.6. It affects games from the eShop. XCI to NSP converted games seem unaffected.

Edit: System version seems irrelevant, with the bug affecting at least 6.2.0-7.0.1.
 
Last edited by Lacius,
  • Like
Reactions: mrcroket
Just realized that my System Settings says "AMS 0.8.4" but I just updated to 0.8.6 (and was using 0.8.5 before that). Am I forgetting to copy/delete something?

I'm on OFW 5.1.0 if that makes a difference.
 
Just realized that my System Settings says "AMS 0.8.4" but I just updated to 0.8.6 (and was using 0.8.5 before that). Am I forgetting to copy/delete something?

I'm on OFW 5.1.0 if that makes a difference.

~snip~ I was wrong
'SciresM: I built 0.8.6 with gcc 8.3.0, which produced slightly larger binaries for all the sysmodules.'
 
Last edited by designgears,
I would suggest clearing off all of your CFW files and dropping 0.8.6 in fresh, there are some file changes in the new build that might not work well when you copy it over the previous install.

I would also suggest grabbing the new sigpatches, the 7.0.1 patches were updated at some point after they were initally released.
I just did that, didn't think updating sigpatches was needed since I'm on 5.1 but I did it anyway. However my System settings still show that I'm running AMS 0.8.4. Is it maybe because of the way Hekate is launching Atmosphere?
 
I just did that, didn't think updating sigpatches was needed since I'm on 5.1 but I did it anyway. However my System settings still show that I'm running AMS 0.8.4. Is it maybe because of the way Hekate is launching Atmosphere?
Settings will only display the version of Atmosphere that was launched.
If it says 0.8.4, then you launched Atmosphere 0.8.4 files with Hekate.
 
Last edited by 8BitWonder,
  • Like
Reactions: stick267
Settings will only display the version of Atmosphere that was launched.
If it says 0.8.4, then you launched Atmosphere 0.8.4 files with Hekate.
I just completely deleted my Atmosphere folder and replaced it with the freshly downloaded 0.8.6 one.

Checking my hekate_ipl.ini; it's loading stuff from "sd:/modules/required/" (exosphere.bin and lp0fw.bin). It doesn't look like those are included with Atmosphere or Kosmos anymore so I'm guessing that's what's causing it. I'll try removing those lines from my Hekate config.
 
There's your problem, those are baked in, including them is overriding and including old modules.

@SciresM possible to add some checks on boot to see if outdated modules are being used?
Yep I looked at the template for the hekate_ipl.ini on Github and adapted mine to it. All good now. Thanks for the help gents.

EDIT: Are bootlogos still broken when launching Atmosphere through Hekate? I'm not trying to use a custom one, just the default.
 
Last edited by stick267,
Yep I looked at the template for the hekate_ipl.ini on Github and adapted mine to it. All good now. Thanks for the help gents.

EDIT: Are bootlogos still broken when launching Atmosphere through Hekate? I'm not trying to use a custom one, just the default.

i dont have those lines so... still not working

that's not the cause
 

Site & Scene News

Popular threads in this forum