Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,780,582
  • Replies Replies 9,374
  • Likes Likes 93
Hello, sorry is its a question already done..

I have updated my 3.0.1 switch to 6.0.1 using ChoiDujourNX and I have enabled autorcm using RajNX/ChoiDujourNX and nogc patch enabled.
Till now I am using RajNXv0751a in my Switch.

My questions:
1 - I need to disable autorcm before update to Atmosphere?
2 - I need to format my SD (and games) before move to Atmosphere?
3 - If I download minimal package from https://www.sdsetup.com I am safe with nogc patch (is enabled by default?)?

Thanks!
 
I just updated from Atmosphere 0.8.1 to 0.8.2 (FW 6.2.0) and always when I try to start the album for homebrew I get Error Code: 2347-0005 (0xb5b). Any help? Before the update everything was working fine.
 
Sadly I'm not into coding nor do I know how to code. But on the brighter side I found out that Hekate supports custom boot splashes. :) Now the only thing missing is a touch UI for Hekate.
you can choose to autoboot to a cfw and choose atmosphere, so that when you boot it up the splash screen appears and boots directly to the cfw without you selecting it
 
Has anyone done a cart update with atmosphere 0.8.1 or above, with AutoRCM installed? Having read through the 'AutoRCM protection' patch, I *think* it would protect AutoRCM during game cart updates, because it generally prohibits BCT writes from the NS service, rather than any specific firmware-upgrade function, but I thought I'd ask to be sure.
 
Atmosphere seems to be working pretty well so far. I was wondering if theres a way to replace the Fusee boot sequence with a spalsh screen?

It is possible yes, but the method is missing from documentation.
To use a custom splash screen you must add the following to the BCT.ini file:
Code:
[stage2]
custom_splash = [PATH TO YOUR SPLASH SCREEN FILE]

The splash screen file must be in BMP format just like hekate.
 
Last edited by _hexkyz_,
  • Like
Reactions: GraFfiX420
It is possible yes, but the method is missing from documentation.
To use a custom splash screen you must add the following to the BCT.ini file:
Code:
[stage2]
custom_splash = [PATH TO YOUR SPLASH SCREEN FILE]

The splash screen file must be in BMP format just like hekate.
Does this replace the default atmosphere splash at the same point it displays anyway, or does it actually replace the status text? I think that's what they were asking about.
 
Warmboot coming later this week/early next week

Sources: and https://github.com/Atmosphere-NX/Atmosphere/commits/master

Potentially you won't need the rcm jig once released

@rajkosto any idea how will that work for users who have higher firms with less burned fuses? I suppose warmboot is not for us
 
Warmboot coming later this week/early next week

Sources: https://twitter.com/hexkyz/status/1074712590347993090 and https://github.com/Atmosphere-NX/Atmosphere/commits/master

Potentially you won't need the rcm jig once released

@rajkosto any idea how will that work for users who have higher firms with less burned fuses? I suppose warmboot is not for us
Can't you just downgrade your console? If you haven't burned your fusees there should be no problem

Inviato dal mio Nexus 5X utilizzando Tapatalk
 

Site & Scene News

Popular threads in this forum