I had already reinstalled Msys2 with all requirements, because I didn't know that compiling Atmosphere is currently not possible due to the missing devkitA64 update and I assumed that something was wrong with my Msys2 installation, as it was the case back then. But this time it's not because of...
I would like to compile the latest AMS build. Could you please tell me the exact commands on how to compile libnx?
So far I have used these commands, but you write something about gcc-14. How do I add this?
export DEVKITPRO=/opt/devkitpro
export DEVKITARM=${DEVKITPRO}/devkitARM
export...
That's exactly what I wanted to know (the required commands). Thank you very much for this information! How can I tell that devkitA64 has been updated? Do I have to keep an eye on the libnx code on Github in case something is updated there? Sorry for these questions, but I have no idea about...
Which libnx version must be used for compiling and which branch? I have already tried the original libnx (master branch), as well as the atmosphere fork with the branch "1800_basic", but I always get an error message at the end of the compilation. Apparently this is related to the issue reported...
The binary file cannot be opened. It must be sent or loaded. My latest exploit menu for FW 6.72 is equipped with the GoldHEN v2.4b17. There are two variants, either the DB version or the ESP8266 version with a smaller payload selection. The Exploit menu can be obtained from here...
I have created an ESP8266 firmware for FW 6.72 here, with the current GoldHEN 2.4b16.2
https://psxtools.de/forum/index.php?thread/82529-ps4-exploit-men%C3%BC-muxi672-pro-alpha-lite/&postID=812079#post812079
I have now been able to collect all the PKG1 IDs that have been released so far from various sources and now have everything up to FW 17.0.0 in full. Since I have not received a reply to my last request, does anyone know of any tools that are currently still supported from whose source code I...
It is said that Python 2 is recommended for compiling Atmosphére. I have installed Python 3.12 and have no problems with it. The py script to personalize the package3 with a custom bootscreen also works perfectly.
After I reinstalled everything, the compile went through without a hitch. No idea what caused the original error. If I get problems like this again that are NOT due to an incorrect libnx installation, I will simply reinstall again following the excellent instructions from the title post.
This is actually always the first thing I do when I start Msys2 Ming64.
1698858408
I don't know what else to do. I will now do a complete reinstall of Msys2.
But that's exactly what I did. Still it does not work.....
Here are my steps:
1.
export DEVKITPRO=/opt/devkitpro
export DEVKITARM=${DEVKITPRO}/devkitARM
export DEVKITPPC=${DEVKITPRO}/devkitPPC
export PATH=${DEVKITPRO}/tools/bin:$PATH
2.
cd ~
git clone --recursive...
How is it done with the latest repo and where do I find it? Until now, I always had to install the latest branch. Could you please tell me the corresponding command lines? Thanks in advance for your effort.
Have you been able to find the cause of the problem? Apparently we both have the same problem and I can't figure out what it is.
Edit:
After I compiled Atmosphere again, using only "make", new, previously unknown error messages appear at the end. I do not understand this......
switchbrew/libnx...
Was the code from you for FW 17.0.0? Are the other codes not needed when you are on FW 17.0.0? So it will work from FW 1.0.0 - 11.0.1 and FW 17.0.0. FW 12.0.0 - 16.1.0 is therefore not supported.
I have now added so. Is that right?
static const pkg1_id_t _pkg1_ids[] = {
{ "20161121183008"...
I may try the new ram site, and download more RAM to my Switch. Not sure if ddr3 is the right ram
for it tho. Edit- no it uses floppy Ram, just like @AncientBoi