Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[petspeed]

I would buy this.

#MeToo

 

[impeeza]

and ME!

 

[impeeza]

Happy June 15th!

Great Work @SciresM; Keep going!

 

[m3anmug]

Can someone help me with how i need to update my config file to boot the fusee.bin now that the file names have changed?

Do i rename the ones that say fusee-secondary to fusee.bin or what? Sorry i usually don't mess with the config files.

 

[BaamAlex]

Can someone help me with how i need to update my config file to boot the fusee.bin now that the file names have changed?

Do i rename the ones that say fusee-secondary to fusee.bin or what? Sorry i usually don't mess with the config files.

Fusee.bin is the payload. Fusee-Secondary is not longer needed. You don't have to rename any files. Fusee-Secondary is now package3.

 

[m3anmug]

This is what i read on the page.

• Please Note: various components were renamed (fusee-primary.bin -> fusee.bin, fusee-secondary.bin -> package3).
  • If you use another bootloader (like hekate), you may need to update your configuration to use the new layout.

• I guess i said it wrong. It was package3 yeah. So i don't need to rename the fusee-secondary in my hekate.ini file to package3 instead?

• I forgot to mention im using hekate in my first post. Sorry.

 

[Kallrkyle]

Yes, you rename the fusee-secondary.bin in your ini file to package3

 

[m3anmug]

Ok thanks.

 

[impeeza]

Can someone help me with how i need to update my config file to boot the fusee.bin now that the file names have changed?

Please read the release page. On it started: fusee_secondarie.bin is now called package3. You must change that name on your ini files
Remember update injection files on your injection method, now is fusee.bin
Do i rename the ones that say fusee-secondary to fusee.bin or what? Sorry i usually don't mess with the config files.

 

[Jacoghi]

1.0.0 working beautifully, thanks @SciresM so much for all the time and effort you've put into this. Atmosphere is just awesome due to its simplicity / complexity paradox!

 

[BaamAlex]

@SciresM

Is it possible that something was changed in 1.0.0 so that atmosphère no longer starts on firmware 1.0.0? I had just created a file based emuMMC for fun. However, when i boot it, an atmosphère error screen comes up immediately. If you need a picture/log of the error, let me know.

 

[Space_Goddess_Samus_Aran]

is there anything what automatically adds a custom bootscreen in my package3? never used Python.

 

[impeeza]

for now, no, if you use linux or MAC is like you already have python, only need to exec the script iwth parameters:

insert_splash_screen.py image package3

Wher image is the path to a image file and package3 is the full path to atmosphère package3 file.

if you use windows, you can download python on https://www.python.org/downloads/release

is really easy to use.

 

[BaamAlex]

is there anything what automatically adds a custom bootscreen in my package3? never used Python.

Which Bootscreen do you want? I can inject it for you

 

[Space_Goddess_Samus_Aran]

Which Bootscreen do you want? I can inject it for you

this here:

 

[BaamAlex]

this here:

View attachment 275453

Gimme a sec

 

[PHiLiPZ]

Python scripts can be compiled to binary executables as well. Maybe that’d be easier for some than installing the Python interpreter.

 

[BaamAlex]

this here:

View attachment 275453

Try this. Copy this into the /atmosphere folder and send the fusee.bin payload.

 

[Space_Goddess_Samus_Aran]

thx

 

[impeeza]

Look what I just got:

Happy June 15th!