Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[mariogamer]

im a bit confused...

is there any way to get the full ram for hbl without installing the nsp? the new hbloader says it can, but its limited by the album still. do i have to change the app that boots it?

Just change the title id to an app. The changelog says that it's still compatible with applet, not that it can't use the ram from an app.

You'll need to change something in the npdm if not using atmosphere for now.

 

[kje123]

Just change the title id to an app. The changelog says that it's still compatible with applet, not that it can't.
You'll need to change something in the npdm if not using atmosphere for now.

ohhh okay, i couldnt for the life of me find exactly what i had to change when searching. thank you!

 

[andijames]

exactly

Well is not difficult to check, NX_Sysmodules https://github.com/Reisyukaku/NX_Sysmodules/ is the part of reinx forked from Atmosphere, It is approximately 40% of all the reinx code

He won't reply as it's readable proof. Doesn't seem to like that quite funny really. Happy days .

 

[Reisyukaku]

Well is not difficult to check, NX_Sysmodules https://github.com/Reisyukaku/NX_Sysmodules/ is the part of reinx forked from Atmosphere, It is approximately 40% of all the reinx code

I only maintain loader and lfs shit and those are all optional even.. nice try goy.
The toolkit is moreso "the cfw" than these modules.

 

[Ryab]

im a bit confused...

is there any way to get the full ram for hbl without installing the nsp? the new hbloader says it can, but its limited by the album still. do i have to change the app that boots it?

you need to install the nspfor full ram usage

 

[kje123]

you need to install the nspfor full ram usage

i dont believe you can install nsp with atmosphere, plus thats an easy ban lol

i just did what mariogamer said and changed the titleid in the preferences to KAMIKO. works great

 

[mariogamer]

you need to install the nspfor full ram usage

No. You can look at the 2.0 release of hbl:

• Now supports running as an application with access to the full ~3.2GB of RAM reserved for applications, while being backwards compatible with older NRO homebrew. Running as a library applet is still supported, although it only has access to 442MB of RAM.
• ...
• Custom NPDM built from source.
  • Default kernel caps application type set to applet (2). Atmosphère users aren't affected by this change, since its native support for nx-hbloader automatically sets the appropriate application type.

It does support the full ram. However, you need to change the kernel caps to application (1) if not using atmosphere.

 

[hippy dave]

Yes, I maked one for 5.1 and now all works well. I uploaded it in case someone wants it.

https://www.mediafire.com/file/dk41...6b0604dca341f4c00e8c4699ea03ddddf018.ips/file

This allows homebrew nsps, like homebrew laucher or retroarch, to run? Thanks.

 

[BryanNigson]

So wtf do we use this for? Like, really, what does the average user do with this?

 

[Raugo]

I only maintain loader and lfs shit and those are all optional even.. nice try goy.
The toolkit is moreso "the cfw" than these modules.

It's optional but useful, and all of this "discussion" start when someone said that atmosphere has nothing useful, At least on my part it was not an attack to Reinx.

This allows homebrew nsps, like homebrew laucher or retroarch, to run? Thanks.

Yes.

 

[kje123]

So wtf do we use this for? Like, really, what does the average user do with this?

right now, the best thing is probably emulators.

 

[hippy dave]

Yes.

I just booted up atmosphere with that patch in place (I think), and got "the software was closed because an error occurred" when I tried to run homebrew menu installed as nsp.

e: same for devmenu, another custom-built nsp.

 

[Raugo]

I just booted up atmosphere with that patch in place (I think), and got "the software was closed because an error occurred" when I tried to run homebrew menu installed as nsp.

e: same for devmenu, another custom-built nsp.

The ips need to be in /atmosphere/kip_patches/<user-defined patch name>/ and this ips only works in firmware 5.1 with exfat.

 

[hippy dave]

The ips need to be in /atmosphere/kip_patches/<user-defined patch name>/ and this ips only works in firmware 5.1 with exfat.

Oh thanks, had the kip_patches bit wrong, will try again. Cheers.

 

[Billy Acuña]

The ips need to be in /atmosphere/kip_patches/<user-defined patch name>/ and this ips only works in firmware 5.1 with exfat.

exFAT only? That sucks, guess I need to build the patch myself, I will never go back to exFAT anymore.

 

[Raugo]

exFAT only? That suck, guess I need to build the patch myself, I will never go back to exFat anymore.

To use the ips you don't need to have the SD in exfat but the switch need to have the exfat compatibility.

 

[Billy Acuña]

To use the ips you don't need to have the SD in exfat but the switch need to have the exfat compatibility.

Ohh, does it? Because I cannot get to run hbmenu.nsp, I'm on 5.1.0 btw

 

[Ryab]

So wtf do we use this for? Like, really, what does the average user do with this?

this will allow homebrew apps to take advantage

 

[hippy dave]

The ips need to be in /atmosphere/kip_patches/<user-defined patch name>/ and this ips only works in firmware 5.1 with exfat.

Still not working for me, same error message. I'm definitely on 5.1.0 with exfat support. Can you tell me what directory name you're using for the patch name, just so I can rule out an issue with that? Thanks.

 

[Raugo]

@Billy Acuña @hippy dave Sorry, I upload it with a wrong name (I changed it in the SD and forgot to change the name of the copy in the HDD)

I reupload it with the folders too https://www.mediafire.com/file/ccdn6j8pgg14j6r/kip_patches.rar/file