Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[jinzo]

I just updated to the latest version of Athmosphere, injected latest hekate and when I launch the cfw the Athmosphere logo pops up and then black screen, everytime I try. But I'm still in RCM. Any ideas?

Maybe you forget to update the fusee-primary.bin?

Make sure you overwrite the "switch" "sept" and "atmosphere" folders.

Hekate doesn't work with the latest Atmosphere I believe.
Try using fusee instead of Hekate for booting up.

It does. Im using Hekate v4.10.1 on my switch fw v8.1.0 with atmosphere v0.9.1 and the new "sweet patches" and everything worked at the first try updating all xD

 

[qris1]

Maybe you forget to update the fusee-primary.bin?

To my knowledge fusee-primary.bin is of no use when injecting hekate and if so, why and how would it need updating?

 

[Chocola]

To my knowledge fusee-primary.bin is of no use when injecting hekate and if so, why and how would it need updating?

I always chainload the fusee-primary.bin with hekate and all work as expected.

 

[lemonadess]

I always chainload the fusee-primary.bin with hekate and all work as expected.

I ran into the same black screen although I updated the fusee-primary.bin. Overwriting old atmosphere files caused this problem.
Guess I'll have to stay at Atmosphere 0.8.10 for a while until the developers figure this out.

Edit: After a few times of getting black screen, while it was still in RCM, I turned my switch off by pressing the Power button. Then I powered it on and injected Hekate payload. And voila! My switch booted in to Atmosphere 0.9.1 (during the process I did not unplug the switch from my computer). Hope this method helps anyone who has the same problem as me.

 

[Deleted User]

There was a small mix up with some code for the original v 0.9.1 release, it was corrected so you might have to download the entire thing. I was going nuts trying to figure it out until I stumbled on the note on discord. The corrected version when used with the new fusee-primary.bin boots fine chainloaded.

 

[josebalu]

como llego en emmunand

 

[CaptainHIT]

AMS 0.8.10 worked fine. Updating to 0.9.0 made my Switch always reboot to RCM. Updating to 0.9.1 gives me this "Failed to run sept" error. I've did a fresh install also aswell as copying over to old installation. Nothing changed. Always got the same errors. So I'm stayin on 0.8.10.
My Switch fw is 7.0.1, I'm using RCMloader (as seen on the last photo) and I also tried it with TegraRCMGUI, resulting with the same errors. My card is a 128GB Sandisk Ultra microSD card.

 

[OperationNT]

"sept" infrastructure has changed in order to support FW 8.1.0. I think it makes current Hekate version confused. You should probably wait for an Hekate update or use "fusee-primary.bin" payload instead: you can put different payloads in "bootloader\payloads" in order to access them through Hekate (second option in your first screenshot).

 

[SkullHex2]

Does every system module need to be updated in order to work on 8.1.0?

 

[vanir29]

Hi, I am currently running AMS 0.8.10 w/ FW 8.0.1, I would like to try the emummc of AMS 0.9.1 but I dont excatly know how to do it, I have a NAND backup btw but it is FW 8.0.1, so I think what I need to do is;

1. Restore NAND Backup (8.0.1)
2. Create emummc (I don't exactly know how to do this but I read somewhere here that SXOS create emunand can be used)
3. Place AMS 0.9.1 on SD card with emummc config
4. Boot emummc???

Another question is, should I disable autoRCM? If not, how can I access the ofw?

I hope someone can help enlighten me on this, thanks in advance.

 

[SciresM]

Happy June 15th!

 

[zomborg]

Woo-hoo!
That was fast

 

[Philliyxx]

Awesome. I would love to get atmosphere working for me, but it hangs right after the new logo. sept> blue atmosphere logo> new logo>black screen.
SD: CARD: fat32 only files are from github FW7.0.1

 

[alba93]

happy June 15th

# Changelog 0.9.2

+ A number of emummc bugfixes were added (all thanks to @m4xw's hard work). The following is a summary of emummc changes:
+ Support for file-based emummc instances was fixed.
+ Please note: file-based emummc is still unoptimized, and so may be much slower than partition-based.
+ This speed differential should hopefully be made better in a future emummc update.
+ The way emummc handles power management was completely overhauled.
+ Emummc now properly handles init/de-init, and now supports low voltage mode.
+ Much better support for shutdown was added, which should assuage corruption/synchronization problems.
+ This should also improve support for more types of SD cards.
+ A bug was fixed that caused emummc to not work on lower system versions due to missing SVC access.
+ **Please note**: The configuration entries used for emummc have been changed.
+ `emummc_` prefixes have been removed, since they are superfluous given the `emummc` category they are under.
+ As an example, `emummc!emummc_enabled` is now `emummc!enabled`.
+ INI configurations made by @CTCaer's [tool](https://github.com/ctcaer/hekate/releases/latest) (which is the recommended way to manage emummc) should automatically work as expected/be corrected.
+ **If you do not wish to use the above, you will need to manually correct your configuration file**.
+ General system stability improvements to enhance the user's experience.
+ Stratosphere is currently in the process of being re-written/refactored.
+ Stratosphere was my (SciresM's) first C++ project, ever -- the code written for it a year ago when I was learning C++ is/was of much lower quality than code written more recently.
+ Code is thus being re-rwitten for clarity/stlye/to de-duplicate functionality, with much being moved into libstratosphere.
+ Stratosphere will, after the rewrite, globally use the `sts::` namespace -- this should greatly enhancing libstratosphere's ability to provide functionality for system modules.
+ The rewritten modules consistently have lower memory footprints, and should be easier to maintain going forwards.
+ The `sm`, `boot`, `spl`, `ro`, and `loader` modules have been tackled so far.
+ General system stability improvements to enhance the user's experience.

 

[aarstar]

Cheats seem to be broken atm.

 

[dc9884]

Is it possible to create an emuMMC from a backup of another console? (i.e., a hektate backup of my clean switch that I use for eShop purchases)

Or does the backup have to be from the same console?

 

[OperationNT]

It has to be from the same console (due to the fact that it's crypted with console specific BIS keys).

 

[dc9884]

It has to be from the same console (due to the fact that it's crypted with console specific BIS keys).

I see, thanks. I guess I’ll still have to use SD Dumper to get those eShop NSPs onto my CFW switch.

 

[phillyrider807]

For someone who is already banned is there any need for emunand?

 

[Hayato213]

For someone who is already banned is there any need for emunand?

Not really.