- Thread starter Goldenman66
- Start date
- Views 18,969
- Replies 113
You mean you tried using hekate/nyx to create + enable emummc and it didn't work, so you tried doing the DD method as an alternative?
Hekate/nyx emummc creation should work unless what you are doing is wrong or the sd card is bad.
Last edited by tabzer,
Using an emuNAND decreases the lifespan of an SD card, and if/when the SD card dies, your primary NAND (the emuNAND) is gone, in addition to the contents of the SD card itself. In other words, recovering your emuNAND requires restoring your NAND the same way you would do it with your sysNAND, and the SD card is more likely to die. This is all in addition to the cumbersome process of setting up the emUNAND in the first place, and the sacrifice of a significant amount of storage space on your SD card.
If you have a good backup of your sysNAND stored somewhere safe, a Switch's sysNAND will almost always be able to be repaired. It's equally safe for the sysNAND to use your sysNAND with a NAND backup on file as it is to use an emuNAND instead, and it's less safe for the SD card.
While it's a matter of personal preference, using an emuNAND merely as brick-protection is not recommended, and it's largely pointless.
Last edited by Lacius,
These are the steps:
[First step is important]
1. TURN ON AIRPLANE MODE, or DELETE NETWORK CONFIGURATION. (This prevents us from accidentally going online with emummc, which would cause a ban when you go online again with sysnand due to nintendo log mismatch).
[EmuMMC Prep + Setup]
2. Format your SD card with 2 partitions. Both partitions are FAT32 Primary (no extended). The second partition needs to be 31307 MegaBytes ("MB" not mb or Mb; megabits) or 29856 MiB.
3. Put Atmosphere 0.9.3 on the SD card. Put Hekate+Nyx on SD card. Extract the hekate_ipl.zip so that hekate_ipl.ini goes into /bootloader/ on the sd card, overwriting the one that's there. All of this is on the first partition.
4. Boot with Hekate payload.
5. Tap "emuMMC" icon on the switch.
6. Tap "Create emuMMC"
7. Tap "SD Partition"
8. (should say found applicable partition: [Part 1]) Tap "Continue"
9. Wait until it finishes. Tap "X Close" at the top right.
10. Tap "Change emuMMC"
11. Tap "SD RAW 1" followed by "OK"
12. Tap "X Close"
13. Tap "Launch". Tap "Emummc"
14. Atmosphere should launch. You can confirm that you are using emummc if you go to System Settings -> System, and under System Update it should say "Current version: X.X.X|AMS 0.9.3|E" where E stands for emuMMC.
That's it. There's a lot more I would recommend, like updating emuMMC to 8.1 using ChoiDujourNX (intermediate -- just remember to choose exfat and not fat32 when given the option). You can turn on autorcm (easy). You can use incognito from blawar (complicated/reccomended) or 90DNS (easier/acceptable) to block your emuMMC from talking to Nintendo while you are online with it. You can also customize your boot list via the hekate_ipl.ini. (easy <-> difficult: https://github.com/CTCaer/hekate/blob/master/res/hekate_ipl_template.ini)
@Lacius + @xabier:
I personally think using sysNAND for going online and emuMMC for cfw is the safest route. If you mess up a NAND that you use to go online, and then restore it from a backup, the logs will mismatched when paired against nintendo's data and will likely result in a ban. emunand or emuMMC has a greater chance of corruption, likely leading to the inevitable outcome of a ban if it is what you use to play "legitimately".
[First step is important]
1. TURN ON AIRPLANE MODE, or DELETE NETWORK CONFIGURATION. (This prevents us from accidentally going online with emummc, which would cause a ban when you go online again with sysnand due to nintendo log mismatch).
[EmuMMC Prep + Setup]
2. Format your SD card with 2 partitions. Both partitions are FAT32 Primary (no extended). The second partition needs to be 31307 MegaBytes ("MB" not mb or Mb; megabits) or 29856 MiB.
3. Put Atmosphere 0.9.3 on the SD card. Put Hekate+Nyx on SD card. Extract the hekate_ipl.zip so that hekate_ipl.ini goes into /bootloader/ on the sd card, overwriting the one that's there. All of this is on the first partition.
4. Boot with Hekate payload.
5. Tap "emuMMC" icon on the switch.
6. Tap "Create emuMMC"
7. Tap "SD Partition"
8. (should say found applicable partition: [Part 1]) Tap "Continue"
9. Wait until it finishes. Tap "X Close" at the top right.
10. Tap "Change emuMMC"
11. Tap "SD RAW 1" followed by "OK"
12. Tap "X Close"
13. Tap "Launch". Tap "Emummc"
14. Atmosphere should launch. You can confirm that you are using emummc if you go to System Settings -> System, and under System Update it should say "Current version: X.X.X|AMS 0.9.3|E" where E stands for emuMMC.
That's it. There's a lot more I would recommend, like updating emuMMC to 8.1 using ChoiDujourNX (intermediate -- just remember to choose exfat and not fat32 when given the option). You can turn on autorcm (easy). You can use incognito from blawar (complicated/reccomended) or 90DNS (easier/acceptable) to block your emuMMC from talking to Nintendo while you are online with it. You can also customize your boot list via the hekate_ipl.ini. (easy <-> difficult: https://github.com/CTCaer/hekate/blob/master/res/hekate_ipl_template.ini)
@Lacius + @xabier:
I personally think using sysNAND for going online and emuMMC for cfw is the safest route. If you mess up a NAND that you use to go online, and then restore it from a backup, the logs will mismatched when paired against nintendo's data and will likely result in a ban. emunand or emuMMC has a greater chance of corruption, likely leading to the inevitable outcome of a ban if it is what you use to play "legitimately".
Last edited by tabzer,
Exactly, and I tried different SD cards also
--------------------- MERGED ---------------------------
Will try again and send you, thanks a lot for your support
Hello @tabzer , here is the steps i did:
1- switch never connected to the internet but i put it to airplane mode.
2- delete sd card partitions and recreated with the values at your post.
3- download latest atmosphere 0.9.3 without fusee-primary (https://github.com/Atmosphere-NX/Atmosphere/releases) and extract it to sd card.
4- download hekate & Nyx (https://github.com/CTCaer/hekate/releases) and extracted to sd card "i didn't found hekate_ipl.ini on sd card to replace it so i paste it to bootloader folder extracted from hekate.
5- boot to Hekate using RCMLoader and Jig.
6- Tap "emuMMC" icon on the switch.
7- Tap "Create emuMMC".
8- Tap "SD Partition" and it found applicable partition: "Part 1".
9- it takes 25m 14s to finish then i taped "X Close" at the top right.
10- Tap "Change emuMMC"
11- Tap "SD RAW 1" followed by "OK"
12- Tap "X Close"
13- Tap "Launch". Tap "Emummc"
all steps done successfully but it reboots again to hekate
Alright, I double-checked and you are right, there is no hekate_ipl.ini from the start (4). Based on what you are experiencing, I am inclined to think there is something wrong with the SD card. It will take time, and it will delete what's on your SD card, but it will tell you if it is good or not:
https://www.heise.de/download/product/h2testw-50539
If you want to try this changed hekate_ipl one time before you do that, it's better, but I am doubting that the ipl is the problem. I'm leaning toward sd card issues.
**If you download this ipl, you will need to also download fusee-primary via Atmosphere and put it in the directory indicated.
https://www.heise.de/download/product/h2testw-50539
If you want to try this changed hekate_ipl one time before you do that, it's better, but I am doubting that the ipl is the problem. I'm leaning toward sd card issues.
**If you download this ipl, you will need to also download fusee-primary via Atmosphere and put it in the directory indicated.
Last edited by tabzer,
, Reason: missing fusee-primary
i tried to replace hekate_ipl.ini file and this time there is a behavior change switch reboots showing hekate logo then logo disappeared and show again (like logo flash twice), then i opened the ini files and compare them the difference is 1st one use fusee-secondary.bin and 2nd use fusee-primary.bin so i downloaded fusee-primary.bin and put it under Atmosphere folder this time switch goes to black screen?
yeah, sorry, forgot to include that. i use hekate to boot fusee-primary because when i boot fusee-secondary it prevents me from installing and running certain ncas/nsps. It was good that you caught on that it was missing, and put the file there. But unfortunately it looks like it didn't help.
I really am thinking it is your sd card.
I really am thinking it is your sd card.
Ok i’ll use the software you share to check the sd card then will try again
Verification process will take long time and i’ll share with you the results, here is a link for my sd card
https://www.amazon.com/Samsung-mc128d-128gb-Uhs-i-Adapter/dp/B0118LR9Z8
Yes I think sd is good but will check also to be sure, I think it may be firmware version
@tabzer it seems SD card is the problem after testing it's defective here under the result of testing
Warning: Only 127866 of 127936 MByte tested.
The media is likely to be defective.
14.8 GByte OK (31138359 sectors)
110.0 GByte DATA LOST (230731209 sectors)
Details:0 KByte overwritten (0 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
110.0 GByte corrupted (230731209 sectors)
0 KByte aliased memory (0 sectors)
First error at offset: 0x00000003b6446e00
Expected: 0x00000003b6446e00
Found: 0x76f978a86be5e318
H2testw version 1.3
Writing speed: 18.1 MByte/s
Reading speed: 3.59 MByte/s
H2testw v1.4
Warning: Only 127866 of 127936 MByte tested.
The media is likely to be defective.
14.8 GByte OK (31138359 sectors)
110.0 GByte DATA LOST (230731209 sectors)
Details:0 KByte overwritten (0 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
110.0 GByte corrupted (230731209 sectors)
0 KByte aliased memory (0 sectors)
First error at offset: 0x00000003b6446e00
Expected: 0x00000003b6446e00
Found: 0x76f978a86be5e318
H2testw version 1.3
Writing speed: 18.1 MByte/s
Reading speed: 3.59 MByte/s
H2testw v1.4
Totally a fake sd card. Glad that clears things up. Many scam providers take smaller sd cards, and label them as bigger, and then hack them to look like that they accept more data than they actually do.
You want at least a U1 sd card. If you plan on using it for Android or L4T - Ubuntu, you will want a U3 card. Get them from a legit retailers like Sandisk or Samsung, directly, if you can. In the states, and in Japan, both of those companies will sell through Amazon.
You want at least a U1 sd card. If you plan on using it for Android or L4T - Ubuntu, you will want a U3 card. Get them from a legit retailers like Sandisk or Samsung, directly, if you can. In the states, and in Japan, both of those companies will sell through Amazon.
Last edited by tabzer,
make a nand backup, install it as emuMMC, and then fully update the real NAND. Keep emuMMC offline forever for CFW, homebrew and piracy. Keep NAND clean of any homebrew or piracy or CFW.
How many times did I ask him to check his sd card and make sure he uses a genuine high quality make!
I quote from one of my first comments to him "Make sure you use a high quality genuine micro sd card don’t go cheap you will only have issues in the long term."
https://gbatemp.net/threads/what-is...itch-with-firmware-4-1-0.545406/#post-8747807
I quote from one of my first comments to him "Make sure you use a high quality genuine micro sd card don’t go cheap you will only have issues in the long term."
https://gbatemp.net/threads/what-is...itch-with-firmware-4-1-0.545406/#post-8747807
Last edited by Reecey,
How many times did I ask him to check his sd card and make sure he uses a genuine high quality make!
I quote from one of my first comments to him "Make sure you use a high quality genuine micro sd card don’t go cheap you will only have issues in the long term."
https://gbatemp.net/threads/what-is...itch-with-firmware-4-1-0.545406/#post-8747807
sorry dear i have a two similar cards Samsung 128GB and i don't know there is a fake cards in the market also they are expensive not cheap. i'll buy another card and try again. thanks a lot
Similar threads
