ROM Hack RELEASE EmuTool - Move partition Emu on another SD, Switch Emu type on SXOS and more

TheyKilledKenny

Well-Known Member
OP
Member
Joined
Dec 5, 2015
Messages
115
Trophies
0
XP
802
Country
Italy
This might have absolutely nothing to do with Emutool, but I have no clue how to fix my problem..
I used Emutool to go from a file based sxos emunand to a hidden sxos partition on a new SD card.
Before, I was able to run sxos and Atmosphere at the same time, but not anymore.
When I launch Atmosphere through Hekate, the screen stays completely black.
I tried deleting everything except the Emunand folder and the sxos boot.dat and got a new package from sdsetup.
I made my emummc.ini like this, so I could use my old sxos Emuand:
[emummc]
enabled = 1
sector = 0x2
nintendo_path = Emutendo

Still, Atmosphere won't launch anymore, not with Hekate, not with fuse-primary or any other payload.
Am I doing something wrong? Does converting the emunand into another format with Emutool change anything that stops Atmosphere from working now?
What you are describing is the same configuration I am currently using. I moved an sx files emunand to a new sd on hidden partitions and I can start it with both sx and fusee-primary.
My emunand is still on fw 9.20.

If the emunand works with sxos, then the copy is ok and the problem isn't the backup/restore process.

I'm very sorry, but it's really difficult for me to try to guess what's wrong with your installation. A lot of small or big things that can be wrong in loading the emunand.
I can assure you (and everybody) that Emutool does nothing within the emunand, it is a simple binary copy tool (a copy machine)
There are no keys so Emutool is unable to decrypt Emunand (and there is no code inside that attempts to do so), therefore no operations can be performed inside the Emu

Check if you have themes or HBs that are not compatible with Atmosphere, remove any game cards from the cartdrige reader.
Recheck the Atmosphere files, specially sept and atmosphere folders, the sigpatches and try again.

I'm sorry for not giving you a definitive solution.

Ciao!
 

fvig2001

Well-Known Member
Member
Joined
Aug 21, 2006
Messages
928
Trophies
1
XP
2,918
Country
Philippines
Thanks for the tool. I needed this because my NANDs were 256gb and I wanted the SD card to use the 32gb backup. I would like to know, if ever the Dragon MMC comes out, is there a way to get the emunand emmc and convert it to hekate? I would probably send that copy to a new NAND module.
 

TheyKilledKenny

Well-Known Member
OP
Member
Joined
Dec 5, 2015
Messages
115
Trophies
0
XP
802
Country
Italy
Thanks for the tool. I needed this because my NANDs were 256gb and I wanted the SD card to use the 32gb backup. I would like to know, if ever the Dragon MMC comes out, is there a way to get the emunand emmc and convert it to hekate? I would probably send that copy to a new NAND module.
I don't know Dragon MMC in detail, but for what I see it is a switchable Nand able to give you 3 different Nand for your switch.
Emutool can read directly from Switch Nand only if mounted via memloader, but you need to first mount boot0, then boot1 and in the end the rawnand. (Someone know if possible and how to mount all the 3 toghether?).
It's easier if you dump the currently selected Dragon Nand with sxos or hekate (backup or new emunand) and then you can use this tool to make backups and restore in varius format.
I hope I understand your question.

Ciao!
 

fvig2001

Well-Known Member
Member
Joined
Aug 21, 2006
Messages
928
Trophies
1
XP
2,918
Country
Philippines
My question was, will it be possible for emutool to transfer emunand to hekate backup since I cannot do nand to hekate backup. Currently this option is not available. If Dragon MMC ever becomes available, I would like to request that Hekate Backup be available on the right side.
 
Last edited by fvig2001,

TheyKilledKenny

Well-Known Member
OP
Member
Joined
Dec 5, 2015
Messages
115
Trophies
0
XP
802
Country
Italy
My question was, will it be possible for emutool to transfer emunand to hekate backup since I cannot do nand to hekate backup. Currently this option is not available. If Dragon MMC ever becomes available, I would like to request that Hekate Backup be available on the right side.
Ah, ok, the answer is simpler than I thought.
In reality there is no need for this option.
If you saved the emunand as a Hekate file, you can restore this "emunand on file" in a Nand as if it were a normal "Nand Backup".

Emunand, emuMMC and Nand Backup are all the same binary dump (copy) of a Switch Nand and can be (quite) freely interchangeable.
they change the file names and the way they're splitted in different number of files and sizes for various reason.
Hekate already support restore from differently splitted backups.

I'm not good in English, I try to explain with an example:
If you create an Hekate Backup and immediately after (without turning on your sysnand) an sxos Emunand on file, then you join all the XX files together of hekate backup and all the full.xx.bin files of sxos emunand, you will get 2 exact same file.

I hope I was able to explain myself

Ciao!
 
Last edited by TheyKilledKenny,

chuliu

New Member
Newbie
Joined
Sep 16, 2017
Messages
3
Trophies
0
Age
53
XP
67
Country
Hong Kong
Thanks for your work.
I was able to upgrade to a 512gb sd card from a 256gb one.
I did this by using emutool to create backup of my hidden partition on the same sd card as files.
Then I copied boot.dat and license.dat to my new sd card and booted into sx os.
Then I clicked on options, emunand, create emunand to create the hidden partiton. I stopped at seeing boot1 and boot2.
Then I restore from the old sd card the backup of the hidden partition as files to my new sd card as a partition.
After that, I copied all the contents on my old sd card except sxos/emunand/ to my new sd card.
Then it works.

I also noticed I couldn't do the copy of the old contents on the old card to new one in mac os.
If I do that, it boot to switch os but says that it cannot access sd card with error 2016-0247.

I re-formatted the new sd card in windows and copied again all the files except the sxos/emunand and it works.
 

TheyKilledKenny

Well-Known Member
OP
Member
Joined
Dec 5, 2015
Messages
115
Trophies
0
XP
802
Country
Italy
Thanks for your work.
I was able to upgrade to a 512gb sd card from a 256gb one.
I did this by using emutool to create backup of my hidden partition on the same sd card as files.
Then I copied boot.dat and license.dat to my new sd card and booted into sx os.
Then I clicked on options, emunand, create emunand to create the hidden partiton. I stopped at seeing boot1 and boot2.
Then I restore from the old sd card the backup of the hidden partition as files to my new sd card as a partition.
After that, I copied all the contents on my old sd card except sxos/emunand/ to my new sd card.
Then it works.

I also noticed I couldn't do the copy of the old contents on the old card to new one in mac os.
If I do that, it boot to switch os but says that it cannot access sd card with error 2016-0247.

I re-formatted the new sd card in windows and copied again all the files except the sxos/emunand and it works.
Thank you for your feedback.
Yes, Macos add some hidden file and other stuff to the SD Card and sometimes it is not compatible with switch.

Ciao!
 

chuliu

New Member
Newbie
Joined
Sep 16, 2017
Messages
3
Trophies
0
Age
53
XP
67
Country
Hong Kong
hi, can someone please help me?
I tried to load atmosphere with tegrarcmgui and play around with it on my switch that I jailbroke with sx pro before.
I used a new sd card thinking it won't affect my old sd card with sx os on it.
Then this morning I booted sx os with the old sd card with my switch.
The emunand option is disabled, even if the sxos/emunand files were there.
I tried to convert the files to a hidden partition with emutool but to no avail.
What should I do to get my emunand back?

Thanks.
 

TheyKilledKenny

Well-Known Member
OP
Member
Joined
Dec 5, 2015
Messages
115
Trophies
0
XP
802
Country
Italy
hi, can someone please help me?
I tried to load atmosphere with tegrarcmgui and play around with it on my switch that I jailbroke with sx pro before.
I used a new sd card thinking it won't affect my old sd card with sx os on it.
Then this morning I booted sx os with the old sd card with my switch.
The emunand option is disabled, even if the sxos/emunand files were there.
I tried to convert the files to a hidden partition with emutool but to no avail.
What should I do to get my emunand back?

Thanks.
I understand that you started with and SX OS emunand on file and then you copied the content, using windows, to a new SD and booted the Emunand using Atmosphere.
If you did a normal copy and paste then this operation should not touch your old SD card and If all the Emunand file are in the folder sxos/Emunand then SXOS should be able to recognize an emunand.

It's difficult for me try to guess what can be wrong, because there are a lot of reason like sd card corruption (if not removed correctly), viruses, wrong operations (cut instead of copy), etc.
If you want to try with hidden partition (I read you already copied in hidden partition) insert the sd card in the PC (not a MacOs), open Emutool and set SXOS hidden partition as source then check that the "Enable Partition Emu" button is selected (pressed)
If Enable Partition Emu is selected then SXOS should recognize a Hidden Partition Emunand even if the Emunand does not exist (in which case the switch does not start, obviously).
If even in this case SXOS is not able to recognize the Emunand, I'm sorry but I really don't know what can be wrong.

Let me know.

Ciao!
 
Last edited by TheyKilledKenny,

CrimShadow

New Member
Newbie
Joined
Jun 30, 2019
Messages
1
Trophies
0
Age
31
XP
50
Country
Brazil
Well, something feels wrong. Already spent three whole days without success. Here's the thing, i use a sxos partition emunand in a 256 card. Just got a 512 one. I can transfer the hidden partition to files on my pc alright. But, when i try to move the sxos files to my 512 card as a partition, the program works fine, but it does not boot. I have a non allocated 31gb partition on it. When i boot hekate, it cant recognize the existance of the foreign emunand, but on my 256 it works just fine. I did some small modifications such as emummc.ini and renaming nintendo path to "emutendo, so i can boot atmosphere on my old-ass sxos emunand. I copypasted everything from the 256 into the 512 several times, including emummc and Emutendo, but it never boots. I'm really new to this and totally lost...
 
Last edited by CrimShadow,

TheyKilledKenny

Well-Known Member
OP
Member
Joined
Dec 5, 2015
Messages
115
Trophies
0
XP
802
Country
Italy
Well, something feels wrong. Already spent three whole days without success. Here's the thing, i use a sxos partition emunand in a 256 card. Just got a 512 one. I can transfer the hidden partition to files on my pc alright. But, when i try to move the sxos files to my 512 card as a partition, the program works fine, but it does not boot. I have a non allocated 31gb partition on it. When i boot hekate, it cant recognize the existance of the foreign emunand, but on my 256 it works just fine. I did some small modifications such as emummc.ini and renaming nintendo path to "emutendo, so i can boot atmosphere on my old-ass sxos emunand. I copypasted everything from the 256 into the 512 several times, including emummc and Emutendo, but it never boots. I'm really new to this and totally lost...
Ok, sorry for the problem.
Let's check what is wrong, please follow all these steps from the beginning:
- since you have backed up the sxos hidden partition to file, copy the files to sxos\Emunand on the new SD card
- Now open Emutool and select sxos partition as SOURCE and disable partition using the button "Disable Partition Emu" that appears
- try to boot the new sd card with sxos
- if it not boot correctly, then try to backup your partition again from the old sd card.
- if it boots correctly then put the sd card in the console and start a hidden partition Emunand creation with sxos option menu
- no need to wait all the process, stop it when you see boot0 or boot1 creation done.
- using Emutool try to restore the sx emu files (the same files you copied and tested on step 1) sxos File as source and sxos partition as target.
- at the end continue with Emutool and set sxos Hidden partiton as SOURCE and check if it is enabled using the button "Enable Partition Emu"
- Delete Emunand files in the new SD card from the folder sxos\Emunand and remove Emunand folder too.
- try to see if now sxos is able to boot from hidden partition.

Let me know.

Ciao!
 
Last edited by TheyKilledKenny,

TheyKilledKenny

Well-Known Member
OP
Member
Joined
Dec 5, 2015
Messages
115
Trophies
0
XP
802
Country
Italy
This tool saved me time from setting up an Ubuntu live CD for DD. Works perfectly when combined with switch.homebrew.guide for Windows.

As others have said, make sure to run repair emunand in Hekate after restoring the nand.

Thanks OP!
Thank you very much for yuor feedback, It helps me to improve.
I need to check why someone need to do the repair emunand because in all the tests I did with my 2 switch I never had to do it.

If you need DD you can find on google various versions compiled for Windows.
This is only an example http://www.chrysocome.net/dd The project is old, but it does it's job.

Ciao!
 
  • Like
Reactions: r5xscn

r5xscn

Well-Known Member
Member
Joined
Apr 8, 2014
Messages
317
Trophies
1
Location
On earth, somewhere
XP
2,273
Country
Antarctica
Thank you very much for yuor feedback, It helps me to improve.
I need to check why someone need to do the repair emunand because in all the tests I did with my 2 switch I never had to do it.

If you need DD you can find on google various versions compiled for Windows.
This is only an example http://www.chrysocome.net/dd The project is old, but it does it's job.

Ciao!
I need to fix the emunand because the offset is changed. My sd card was a 64 GB, thus the offset is at around 32 GB memory address (cant remember the exact offset). The new sd card is 128 GB, thus the offset must be changed to 96 GB or something because hidden emunand partition is the last 32 GB of the SD card.

I can manually change the offset in the emummc.ini or something. But "repair emunand" is easier and only takes a short amount of time.

I know the dd project, but was afraid that Windows environment might have some difference with Linux, so I opted to use your tool. Thanks!
 
  • Like
Reactions: TheyKilledKenny

mattyxarope

Well-Known Member
Member
Joined
Jan 15, 2019
Messages
544
Trophies
0
XP
1,995
Country
United States
I'm trying to take the emunand (hidden SXOS) from my old 512 gb card and transfer it to a smaller 128gb card.

What would be the best way to do that?

Should I:
  1. make a backup of my emunand from the 512 card (as an SX file using this tool)
  2. restore it to the 128 card (as a hidden SX emunand partition)
  3. copy over my files from the 512gb sd card to the 128gb card? (I know I'd have to pair down the total size to be under 128gb?

Would it be that easy?
 
Last edited by mattyxarope,

Bala666

Member
Newcomer
Joined
Jul 5, 2020
Messages
21
Trophies
0
Age
28
XP
88
Country
Brazil
Sorry, my English is kind of bad and I couldn't quite understand it.

My question is: I currently have a 256GB MicroSD, with SXOS Emunand Hidden, if I buy a 512GB card, what is the procedure for copying my emunand in exactly the same way for this 512GB card? That is, without losing the hidden partition of sxos.
I don't know if that matters, but I have the SX core.


Thanks in advance!
 

TheyKilledKenny

Well-Known Member
OP
Member
Joined
Dec 5, 2015
Messages
115
Trophies
0
XP
802
Country
Italy
I'm trying to take the emunand (hidden SXOS) from my old 512 gb card and transfer it to a smaller 128gb card.

What would be the best way to do that?

Should I:
  1. make a backup of my emunand from the 512 card (as an SX file using this tool)
  2. restore it to the 128 card (as a hidden SX emunand partition)
  3. copy over my files from the 512gb sd card to the 128gb card? (I know I'd have to pair down the total size to be under 128gb?

Would it be that easy?
Yes, but remember to recreate the hidden partition on the new sd card, the easyest way is to let SXOS create a new emunand on hidden partition, stop it when you see boot0 or boot1 and then restore with Emutool your previously backupped emunand.
Remeber that you need to copy Emutendo folder to have all the installed games or you need to renistal them (saves are stored in emunand)
Don't erase you actual sd card until you're sure the new sd card works as expected.

Sorry, my English is kind of bad and I couldn't quite understand it.

My question is: I currently have a 256GB MicroSD, with SXOS Emunand Hidden, if I buy a 512GB card, what is the procedure for copying my emunand in exactly the same way for this 512GB card? That is, without losing the hidden partition of sxos.
I don't know if that matters, but I have the SX core.

Thanks in advance!
Read the answer I just gave above, the procedure is what @mattyxarope wrote. as said, remember to recreate the hidden partition, so start with the new sd as if it were the first time you create an emunand and stop it when you see boot0 or boot1 (enough for the partition to be created).

All of my games show up on my home menu, but I need to reinstall them? Is this normal or what do I do.
You need to copy on the new sd also the Emutendo folder (if sxos) or the Nintendo folder you can find under emuMMC\RAWxx (if atmosphere). the installed game are stored inside that Nintendo folders.

I need to fix the emunand because the offset is changed. My sd card was a 64 GB, thus the offset is at around 32 GB memory address (cant remember the exact offset). The new sd card is 128 GB, thus the offset must be changed to 96 GB or something because hidden emunand partition is the last 32 GB of the SD card.

I can manually change the offset in the emummc.ini or something. But "repair emunand" is easier and only takes a short amount of time.

I know the dd project, but was afraid that Windows environment might have some difference with Linux, so I opted to use your tool. Thanks!
Thanks for your report, I have to investigate because Emutool should already create the correct emummc.ini file with the correct offset, but if you need to repair it, it means that it is not doing it correctly.
Did you overwrite the emuMMC folder or the emummc.ini file after restoring with Emutool?

Ciao!
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: https://youtu.be/2UeWMgjwogU?si=PfULn0Jf4XpnU6M_ Now I know how to install m.2