Toggle sidebar

Homebrew RELEASE NX Nand Manager

impeeza said:
The instructions on the original Eliboa's github repo tell you to use MSYS

I do use for eliboa's:

Bash: 
pacupd git make devkit-env base-devel mingw-w64-x86_64-toolchain mingw64/mingw-w64-x86_64-qt5-static
cd ~
rm -rf ~/NxNandManager
git clone --recursive https://github.com/eliboa/NxNandManager
cd ~/NxNandManager/NxNandManager/gui
/mingw64/qt5-static/bin/qmake.exe NxNandManager.pro 'CONFIG += STATIC ARCH64'

So far you need to edit the NxNandManager.pro file as indicated on the https://github.com/eliboa/NxNandManager/issues/134#issuecomment-2453505924 issue.

Bash: 
make -j$(nproc)
mkdir build
cp release/NxNandManager.exe ./build/
cp ../virtual_fs/dokan/x64/dokan1.dll ./build/



if you note the jorgon's repo have not been able to build since the commits from September 29th which are the ones diverging for the original one. and seems was replaced NxNandManager.pro for a visual studio build process.

stay with the original one, the most recent binaries are on https://gbatemp.net/download/nx-nand-manager.38890/
Click to expand...
Compiling NxNandManager with qt6 is perfectly fine, but with Qt creator it only works in debug, release can't decrypt the nand, which is a magical problem!
 
  • Like
Reactions: impeeza
i'm using the latest build posted here 5.2.1 on a Lite FW19.0.1 but the the program is not able to read the FW version and the Device ID says : keyset needed!, is this correct?

The console is connected to my pc via UMS-Loadere as payload, since it's the only one able to boot on this console at the moment.
 
Greasson said:
i'm using the latest build posted here 5.2.1 on a Lite FW19.0.1 but the the program is not able to read the FW version and the Device ID says : keyset needed!, is this correct?

The console is connected to my pc via UMS-Loadere as payload, since it's the only one able to boot on this console at the moment.
Click to expand...
you need to dump you keys using lockpick first
 
  • Like
Reactions: Greasson and Danook28
Last edited by impeeza,
  • Like
  • Love
Reactions: HS2005, Asia81, Badablek and 1 other person
  • Retrieve and display useful information about NAND file/drive (Firmware version, device ID, exFat driver, S/N, etc.) using BIS keys
can i have step by step how to know the firmware version? i have the nand dump and also the lockpick dump.
- found https://github.com/rajkosto/biskeydump but i dont understand :( any easier way? thank you very much.
...
reason is i found an old nand dump and not sure what version OFW it was.
edit: wait i have done the lockpick dump. that is incl bis, right? then i have it.
after i load the nxnandmanager, what is the next step? (where can i see the OFW version of my dump?)
 
Last edited by chimot,
chimot said:
  • Retrieve and display useful information about NAND file/drive (Firmware version, device ID, exFat driver, S/N, etc.) using BIS keys
can i have step by step how to know the firmware version? i dont have bis key, just the nand dump.
- found https://github.com/rajkosto/biskeydump but i dont understand :( any easier way? thank you very much.
reason is i found an old nand dump and not sure what version OFW it was
Click to expand...
use LockPick_RCM payload.
 
chimot said:
yes i have the prod.keys and dev.keys . where to go from here? thanks
Click to expand...
1747541530096.png


1747541559473.png
 
Hey, I thought I'd leave some info here (in case someone googles this niche scenario i had) if you want to use this but don't have access to a windows system, since there isn't a Linux build you can try: This program works fine on WinPE live boots like HirenBoot (A windows PE live boot utility to do rescue attempts of your system, it's legal.) It's even possible to install the Dokan Driver and keys into this environment.
Managed to backup and recover saves from a busted emunand partition of mine, folder extraction also worked fine except for TOTK which was recognized as japanese version for some reason. The Characters were all rectangles and it didn't want to create the save folder. Saving the files one by one per hand worked nicely though. Also the folder creation with the extraction wasn't reliabe but i could live with that, dunno it was because of the PE boot.

Little request: Multiselect for files in the Save as menu for the savegames?
 
  • Like
Reactions: impeeza
Hi! I used this app to backup and copy the emunand into another SD.
After doing it, I copied all the files from the old SD into the new one, without overwriting any file.

It worked, but with a problem: the apps I had previously installed in my SD aren't recognized by my switch, requiring me to reinstall them.

I'm pretty sure the game data is in the new SD (it's almost full), but somehow it isn't recognized by the system.

What did I do wrong and how do I fix it?
 
Desconocido90 said:
Hi! I used this app to backup and copy the emunand into another SD.
After doing it, I copied all the files from the old SD into the new one, without overwriting any file.

It worked, but with a problem: the apps I had previously installed in my SD aren't recognized by my switch, requiring me to reinstall them.

I'm pretty sure the game data is in the new SD (it's almost full), but somehow it isn't recognized by the system.

What did I do wrong and how do I fix it?
Click to expand...
If you are migrating your setup from a SD card to another you have two ways:

If your EmuNAND is file based, just copy all files from a card to another, remember to initialize the new card using Hekate before.


If your EmuNAND is Raw based, you need:
  • Backup your EmuNAND using Emutool, this tool will save the current Raw partion to a set of files on your local drive, you can use that files to restore the backup to another SD Card or use them as a new EmuNAND file based.
  • Initialize the new card using Hekate, you boot on hekate then instert the new card, and initialize it. if you like to stay with a Raw based EmuNAND you create the partition layout on Hektate, if you like to migrate to File based, do not create any special partition layout.
  • copy all files from the old SD Card to the New one. Put attention on archive bit.
  • Now if you want to stay on Raw Partition EmuNAND, use EmuTool to restore the backup to the new card empty space.
  • if you like to convert your EmuNAND to file based, copy the backup files created to the SDMC:/emuMMC/SD00/eMMC path.
An example of the files you should have is:
Code: 
H:\emuMMC\
|   emummc.ini
|   
\---SD00
    |   file_based
    |   
    +---eMMC
    |       00
    |       01
    |       02
    |       03
    |       04
    |       05
    |       06
    |       07
    |       BOOT0
    |       BOOT1
    |       
    \---Nintendo
        +---Album
        +---Contents
        |   |   private
        |   |   private1
        |   |   
        |   +---placehld
        |   \---registered
        |                   
        \---save
                0000000000000001
                0000000000000002
                8000000000000000
                8000000000000124
  • IMPORTANT: Start Hekate and go to EmuNAND setup, select and activate the new EmuNAND, this way the config files are set for your new card.
Today there is no practical performance difference between File and RAW Partition EmuNANDs once upon a time where a big one, so today is easy to use File Based EmuNAND.
 
Can this program help me resize my SD card, which currently contains my emuMMC on the I: partition ? I wanted to use the 148GB Unallocated space into my H: Partition.
4.png
 

Site & Scene News

Go to forum More news

Popular threads in this forum

Dusk for switch (TLoZ Twilight Princess port)

Homebrew  Full List of N64 Recompilation Switch ports

Homebrew  New Homebrew "Foil Server"?

Homebrew Tutorial Translation Project  CS2SX — Write Nintendo Switch Homebrew in C#

Hacking  WiFi chip failing and can't boot. is it possible to enable Airplane Mode by editing system save files directly?

Homebrew Homebrew game Project  So... Dan didn't want to reveal his Vulkan, so I made mine.

Homebrew  Sonic Unleashed Recompiled (Homebrew Port)

Feedback Homebrew  Essential Homebrew