Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,763,665
  • Replies Replies 9,326
  • Likes Likes 92
Sorry if this may sound off-topic, but can anyone tell me the difference between FS and ACID patches? Like, what are the functions of the two.
FS patches refer to fs_nosigchk which ignores any .NCA content not signed by Nintendo. These are used for homebrew .NSP files since their .NCA files didn't come from Nintendo so they aren't signed by them and .NSP file converts since converting them invalidates the signature. ACID patches ignore a hash at the end of .XCI files that isn't really useful practically nowadays except for a speed increase when installing .XCI files.
 
FS patches refer to fs_nosigchk which ignores any .NCA content not signed by Nintendo. These are used for homebrew .NSP files since their .NCA files didn't come from Nintendo so they aren't signed by them and .NSP file converts since converting them invalidates the signature. ACID patches ignore a hash at the end of .XCI files that isn't really useful practically nowadays except for a speed increase when installing .XCI files.
Thanks much.
 
  • Like
Reactions: Draxzelex
Anybody else having trouble booting their system after upgrading to Atmosphere 0.13.0?

So, I just recently upgraded to the latest version of Hekate (5.3.0) where it works just fine when the console was still on Atmosphere 0.12.0. But after using the files for Atmosphere 0.13.0, it no longer boots beyond the Hekate part of the chainload booting process.

System firmware: 10.0.2

Having the exact same problem, had to revert to 0.12 as well.

I went as far as starting from scratch with a new SD card and and fresh eMMC. Still same issue.
 
Hi i'm new here but i'm an italian lurker so i've reading this site since mid years 2000.
Anyways i have a little big problem with latest atmosphere.
I'm on firmware 10.0.4, i've installed atmosphere, patches and everything related to the cfw but :
- when i try to boot the cfw - emuMMC from Hekate > launch the cfw works like a charm, games, homebrews and everything works fine.
- when i try to boot the cfw by injecting the latest fusee primary payload i can see the sept logo, the atmosphere logo and then i got an error that looks like an hex editor (see the attachment)

i've tried to delete the switch folder, the config folder and the atmosphere/sept folder and reinstall but this error is still here.
Anyone knows how to fix?
 

Attachments

  • photo_2020-06-15_23-45-14.jpg
    photo_2020-06-15_23-45-14.jpg
    36.8 KB · Views: 179
Last edited by Fireandwater,
Hi i'm new here but i'm an italian lurker so i've reading this site since mid years 2000.
Anyways i have a little big problem with latest atmosphere.
I'm on firmware 10.0.4, i've installed atmosphere, patches and everything related to the cfw but :
- when i try to boot the cfw - emuMMC from Hekate > launch the cfw works like a charm, games, homebrews and everything works fine.
- when i try to boot the cfw by injecting the latest fusee primary payload i can see the sept logo, the atmosphere logo and then i got an error that looks like an hex editor (see the attachment)

i've tried to delete the switch folder, the config folder and the atmosphere/sept folder and reinstall but this error is still here.
Anyone knows how to fix?

Me getting the same error. My config: Sysnand 8.1x, emummc 9.2., atmosphere 10.05

Emummc doesn't boot but sysnand is working fine with below options:
What I've tried so far:
- various AIO packages
- vanilla atmos 12 and 13 including the correct fusee-primary.bin
- vanilla hekate 5.3
- 3 different sdcards with fat32 and exfat
- 2 times new emunand created from sysnand 8.x
- fix archv bit

Nothing helps, it always ends in the "hex screen error" with booting emummc

Any hint or help is much appreciated.
 
Last edited by ,
remove atmosphere/sept/bootloader and reinstall. it should work properly. If you run emunand it s way faster than before
This fixed it for me. Apparently, the files used in 0.12.0 is not completely overwritten by the ones for 0.13.0 and thereby the leftover file(s) is/are in conflict with one another which prevents the system from booting.
 
Last edited by Dothackjhe,
hello i have fixed the game installed nsp with atmo 13 + hekate 5.3 but the retroarch is messed up only the basic of retroarch is fine and the flycast core that has nomai, atmosiwave and dreamcast crash. i noticed that album is automatic into hbl i hold R on game tilte installed to get full ram it doesnt work I need help and some advice please!!
 
Is choidujour working on the latest atmosphere and latest switch fw?
Did you mean for downgrading purposes?

I'm using Armosphere 0.13.0 on a console that runs on firmware 10.0.2, I've had no issues, so far. It's generally stable.
 
Last edited by Dothackjhe,
Did you mean for downgrading purposes?

I'm using Armosphere 0.13.0 on a console that runs on firmware 10.0.2, I've had no issues, so far. It's generally stable.

I mean in general, does choidujour work fine in 10+ fw? My sysnand is still very low but my emunand is 9.2. i am thinking whether i can still update my emunand fw later via choidujour
 
(...) - when i try to boot the cfw by injecting the latest fusee primary payload i can see the sept logo, the atmosphere logo and then i got an error that looks like an hex editor (see the attachment) (...)
Same problem here, i return in 0.12 and work well now.
 
@SciresM How do I make a few Changes on atmo 0.13.0 the jit with emulators seems not work with v0.13.0 what do I need to change also the cart game will not work with this too. Thank you for reading this
 
Having an issue from time to time when exiting a game that atmosphere will crash. It’s reporting that program “010000000000000D” is causing it. Is happening often enough to be annoying, anyway to fix this issue?
 
Having an issue from time to time when exiting a game that atmosphere will crash. It’s reporting that program “010000000000000D” is causing it. Is happening often enough to be annoying, anyway to fix this issue?
I believe that has something to do with a custom theme.

If you're actively using a custom theme, I suggest you disable it.
 

Site & Scene News

Popular threads in this forum