Toggle sidebar

Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,773,572
  • Replies Replies 9,352
  • Likes Likes 93
Hayato213 said:
Reboot_payload.bin doesn't work on mariko, I have two oled and one unpatched it never work for me on the oled, I mean if you really want a reboot method, you can lookup studious pancake. Erista
Click to expand...

Hayato213 said:
Reboot_payload.bin doesn't work on mariko, I have two oled and one unpatched it never work for me on the oled, I mean if you really want a reboot method, you can lookup studious pancake.
Click to expand...
I have Erista and always works to me except last version
Post automatically merged:

josete2k said:
You can manage the reboot to atmosphere in the atmosphere config file too.
Click to expand...
How would you do this?
 
Hayato213 said:
Your answer is all over the place the last post you said you have patched, now you said you have erista v1 unpatched.
Click to expand...
Not sure about which is patched for you. I told that is v1 (first version) and now add that is without chip just software I think is called Erista. I don’t search in google first time. I mean “patched” thinking that is custom firmware opposite to stock firmware
 
alfonsovin said:
Not sure about which is patched for you. I told that is v1 (first version) and now add that is without chip just software I think is called Erista. I don’t search in google first time. I mean “patched” thinking that is custom firmware opposite to stock firmware
Click to expand...

alfonsovin said:
I have a v1 patched without chip
Reboot_payload used to work when I reboot from atmosphere or when there is an error and push volumen button for reboot
Click to expand...

alfonsovin said:
I have Erista and always works to me except last version
Post automatically merged:
Click to expand...

I quoted what you said before that why I said it is all over the place if you have erista unpatched then you should not have reboot payload issue.
 
Hayato213 said:
I quoted what you said before that why I said it is all over the place if you have erista unpatched then you should not have reboot payload issue.
Click to expand...
No matter how or if to was a misunderstanding. I have Erista and I can’t inject last atmosphere payload directly

I will proof 1.11.1 and then again try in fresh atmosphere folder but it’s very strange to me
Post automatically merged:

After several tries I found that there is something wrong in atmosphere folder, I delete and change for a fresh one and fusee works. Now I need to copy one by one till know which is the problem
 
Last edited by alfonsovin,
alfonsovin said:
No matter how or if to was a misunderstanding. I have Erista and I can’t inject last atmosphere payload directly

I will proof 1.11.1 and then again try in fresh atmosphere folder but it’s very strange to me
Post automatically merged:

After several tries I found that there is something wrong in atmosphere folder, I delete and change for a fresh one and fusee works. Now I need to copy one by one till know which is the problem
Click to expand...

Should always replace atmosphere files when updating
 
Hayato213 said:
Should always replace atmosphere files when updating
Click to expand...
Atmosphere files are replaced, in fact I boot CFW through Hekate. There are some rest of files that doesn’t work when boot with new fusee. Previous one works without problem with same atmosphere folder
 
alfonsovin said:
Atmosphere files are replaced, in fact I boot CFW through Hekate. There are some rest of files that doesn’t work when boot with new fusee. Previous one works without problem with same atmosphere folder
Click to expand...
Atmosphere requires fusee.bin paired with your current atmosphere version. As in, you need the same fusee.bin that was compiled when that specific version of atmosphere was compiled.

example if you go use "HATS", or kefirmosphere or whatever they call it, you cannot use the fusee.bin from the official atmosphere release (or "older" fusee.bins anyway) (same with my fork, which is why i put fusee.bin inside the archive)

also whomever distributes some sort of stupid package3 modification would require a fusee.bin linked to that package3, as fusee(secondary) is embedded in it.


hekate breaks open package3 to boot and discards atmosphere's concept of fusee(secondary)
 
mystery resolved, problem was OC Horizon, exosphere.bin concrete.

it needs an update

Now I can reboot via fusee.bin without problem
 
Hi everyone,

I've been away from the Switch scene for quite a while and I'm currently running:

  • Atmosphère 1.10E / AMS 1.10
  • Hekate 6.4.1
  • System firmware 20.1.1
Is there any real reason for me to update Atmosphère right now, or is it better to stay on my current version as long as everything is working?

If I do update Atmosphère, do I also need to update Hekate at the same time, or can I keep using Hekate 6.4.1?

I'm mainly getting back into homebrew, so I'm interested in compatibility and stability rather than updating just for the sake of being on the latest version.

Thanks!
 
gd-zero said:
Hi everyone,

I've been away from the Switch scene for quite a while and I'm currently running:

  • Atmosphère 1.10E / AMS 1.10
  • Hekate 6.4.1
  • System firmware 20.1.1
Is there any real reason for me to update Atmosphère right now, or is it better to stay on my current version as long as everything is working?

If I do update Atmosphère, do I also need to update Hekate at the same time, or can I keep using Hekate 6.4.1?

I'm mainly getting back into homebrew, so I'm interested in compatibility and stability rather than updating just for the sake of being on the latest version.

Thanks!
Click to expand...

General reason to update would be if there is a game that you can't run other wise you can stay at lower firmware if you want. You need to update Hekate and Atmosphere if you update the system firmware.
 
gd-zero said:
Hi everyone,

I've been away from the Switch scene for quite a while and I'm currently running:

  • Atmosphère 1.10E / AMS 1.10
  • Hekate 6.4.1
  • System firmware 20.1.1
Is there any real reason for me to update Atmosphère right now, or is it better to stay on my current version as long as everything is working?

If I do update Atmosphère, do I also need to update Hekate at the same time, or can I keep using Hekate 6.4.1?

I'm mainly getting back into homebrew, so I'm interested in compatibility and stability rather than updating just for the sake of being on the latest version.

Thanks!
Click to expand...
Your firmware is very old. If you are happy with the games you already have on your switch and don't care about getting updates to those game then you can continue until end of life for your hardware. Otherwise you will probably have to update.
 

Site & Scene News

Go to forum More news

Popular threads in this forum

Emulation Gaming Homebrew Others Homebrew app Emulator  [Nintendo Switch] Raika Azahar - The 3DS Emulator aimed at base Nintendo Switch

GTA V port?

nxtube - tizentube (adblock, sponsorblock) for youtube on nintendo switch

Emulation  Vita3K - PlayStation Vita

Homebrew game Project  [Release] The Minish Cap – Alek's Ultimate NX Edition | Dual Screen, FLIP GRIP SUPPORT, Touch, RetroAchievements

Docklight - A port of Lighthouse to the Nintendo Switch

Hello Kitty Island Adventure [010027901C89C000]

Hacking Feedback Tutorial Project  120hz OLED - handled mode.