Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[alfonsovin]

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

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.

I have Erista and always works to me except last version

Post automatically merged: Yesterday at 1:18 PM

You can manage the reboot to atmosphere in the atmosphere config file too.

How would you do this?

 

[Hayato213]

I have Erista and always works to me except last version

Your answer is all over the place the last post you said you have patched, now you said you have erista v1 unpatched.

 

[Gamehopper]

Folllowing his latest tweet :

https://twitter.com/sciresm/status/874660344408440832

It seems that @SciresM has seriously started working on a CFW implementation.

https://github.com/Atmosphere-NX/Atmosphere

It shouldn’t be long before we get all the elements for hacking our Switches !

Quite impressive Michael !

awesome!

 

[alfonsovin]

Your answer is all over the place the last post you said you have patched, now you said you have erista v1 unpatched.

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

 

[Hayato213]

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

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

I have Erista and always works to me except last version

Post automatically merged: Yesterday at 1:18 PM

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.

 

[alfonsovin]

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.

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: Yesterday at 11:40 PM

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

 

[Hayato213]

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: Yesterday at 11:40 PM

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

Should always replace atmosphere files when updating

 

[alfonsovin]

Should always replace atmosphere files when updating

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

 

[bth]

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

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)

 

[alfonsovin]

mystery resolved, problem was OC Horizon, exosphere.bin concrete.

it needs an update

Now I can reboot via fusee.bin without problem