If you say so....You have the same risks with an emuNAND, and using an emuNAND increases the risk of an SD card going bad.
Broken SD card means no problem for the console, bad backup+restore is troublesome
If you say so....You have the same risks with an emuNAND, and using an emuNAND increases the risk of an SD card going bad.
I tried to use hekate/nyx to create+enable emummc earlier before using dd method with same results
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.Broken SD card means no problem for the console, bad backup+restore is troublesome
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.
Will try again and send you, thanks a lot for your supportThese 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".
If something goes wrong, let us know what step didn't work, and we'll be able to trace it.
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.
Ok i’ll use the software you share to check the sd card then will try againyeah, 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.
Verification process will take long time and i’ll share with you the results, here is a link for my sd cardlet us know if the sd is good. also could you tell me the brand size and class? if you have a link to an actual product page, it would probably be easiest.
Yes I think sd is good but will check also to be sure, I think it may be firmware versionI honestly think that should work. I don't see how it could have gone wrong.
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