Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[urherenow]

You want to test your card first before proceeding though if you got a bootleg card that would explain it, always test your SD card when you get them with H2testw for windows or F3X for mac.

From what I've seen, a fake card doesn't have all of the info a genuine card is supposed to have. Something is always missing. Most often, the serial number is missing. So a faster way to check is to simply look at the SD info in NYX.

 

[zxr750j]

From what I've seen, a fake card doesn't have all of the info a genuine card is supposed to have. Something is always missing. Most often, the serial number is missing. So a faster way to check is to simply look at the SD info in NYX.

I thought a fake card is just missing memory, the metadata stored on the card says it's got like 128GB but it actually only has like 8GB of actual memory chips.

 

[Solo761]

There is not a Black list of SD Cards perse, but in a previous version of Atmosphère was an issue where a model of SD cards generate a error on emuMMC, you should open a Issue on the GitHub for Atomosphère https://github.com/Atmosphere-NX/Atmosphere/issues giving all information about the SD Card and if someone could get the idea why the SD do not work make the correction on the code.

Thanks, I'll make a post there and put card info that I can get out of hekate, maybe it'll help someone.

You want to test your card first before proceeding though if you got a bootleg card that would explain it, always test your SD card when you get them with H2testw for windows or F3X for mac.

This card is two years old, I bought it in legitimate local store. It wasn't from China. And I've been using it with SX OS since without problems, it's not fake. Read is around 85 MB/s, write is around 30 MB/s (though this may just be my card reader, I have a feeling it's faster while in Switch.

Lol no? Every sd card works with the switch.

Welp, the card works with switch, I've been using it for last two years with SX OS without issues. Problem is hidden partition emuNAND and Atmosphere, in every try I ended up with black screen. When I tried emuNAND with files instead of hidden partition it worked. Same procedure on Samsung Evo 128GB and hidden emuNAND partition worked fine. Tried again with this Kingston and again doesn't work.

Card is original, it wasn't bought on aliexpress or ebay, but in legitimate store of legitimate importer. Capacity is also real. I'm currently running SC Card benchmark with Hekate nad I'm getting 92 MB/s read top speed.

From what I've seen, a fake card doesn't have all of the info a genuine card is supposed to have. Something is always missing. Most often, the serial number is missing. So a faster way to check is to simply look at the SD info in NYX.

Card info has all the data from what I've seen, here's how it looks (I've only blanked last few digits of S/N). Card works fine, barring emuNAND in hidden partition.

I thought a fake card is just missing memory, the metadata stored on the card says it's got like 128GB but it actually only has like 8GB of actual memory chips.

Depends, in most cases yes, capacity is faked, especially with these with bigger capacities. But I guess in some other cases, i.e. 16/32 GB it could be that branding is faked because they get more money for Samsung Evo 32 GB than no name 32 GB .

So far my "best" case was SD card that I got with my 3d printer few years back. It was full size SD card, marked as 8 GB, inside it was microsd with contacts soldered to it's pins (so, not full size adapter with SD slid in it, it was like "normal" full size, fully enclosed, and iniside it was hidden microSD card ) that was marked as 4 GB, and after capacity test it ended up being only 2 GB real capacity. Talk about inception .

 

[urherenow]

Thanks, I'll make a post there and put card info that I can get out of hekate, maybe it'll help someone.

.

I'm not going back through this thread to see if you're the one with issues, but if you are, I'd say your problem is using exFAT. Countless devs say not to use it. The switch itself can potentially corrupt files using it (as in, not necessarily the fault of any homebrew). Do yourself a favor and backup your stuff, and let nyx format your card. But yes, that card looks legit. Doesn't mean that it's not failing though. To test if it's failing, you really do need to use h2testw.

 

[Hayato213]

Thanks, I'll make a post there and put card info that I can get out of hekate, maybe it'll help someone.



This card is two years old, I bought it in legitimate local store. It wasn't from China. And I've been using it with SX OS since without problems, it's not fake. Read is around 85 MB/s, write is around 30 MB/s (though this may just be my card reader, I have a feeling it's faster while in Switch.



Welp, the card works with switch, I've been using it for last two years with SX OS without issues. Problem is hidden partition emuNAND and Atmosphere, in every try I ended up with black screen. When I tried emuNAND with files instead of hidden partition it worked. Same procedure on Samsung Evo 128GB and hidden emuNAND partition worked fine. Tried again with this Kingston and again doesn't work.

Card is original, it wasn't bought on aliexpress or ebay, but in legitimate store of legitimate importer. Capacity is also real. I'm currently running SC Card benchmark with Hekate nad I'm getting 92 MB/s read top speed.



Card info has all the data from what I've seen, here's how it looks (I've only blanked last few digits of S/N). Card works fine, barring emuNAND in hidden partition.

View attachment 261605




Depends, in most cases yes, capacity is faked, especially with these with bigger capacities. But I guess in some other cases, i.e. 16/32 GB it could be that branding is faked because they get more money for Samsung Evo 32 GB than no name 32 GB .

So far my "best" case was SD card that I got with my 3d printer few years back. It was full size SD card, marked as 8 GB, inside it was microsd with contacts soldered to it's pins (so, not full size adapter with SD slid in it, it was like "normal" full size, fully enclosed, and iniside it was hidden microSD card ) that was marked as 4 GB, and after capacity test it ended up being only 2 GB real capacity. Talk about inception .

Shouldn't use exFAT to be honest with you, that most likely the reason it won't boot, also cluster is off, it should be 32kb cluster.

 

[Solo761]

Shouldn't use exFAT to be honest with you, that most likely the reason it won't boot, also cluster is off, it should be 32kb cluster.

I'm not going back through this thread to see if you're the one with issues, but if you are, I'd say your problem is using exFAT. Countless devs say not to use it. The switch itself can potentially corrupt files using it (as in, not necessarily the fault of any homebrew). Do yourself a favor and backup your stuff, and let nyx format your card. But yes, that card looks legit. Doesn't mean that it's not failing though. To test if it's failing, you really do need to use h2testw.

Tried both FAT32 and exFAT, multiple times, no difference. Black screen after Nintendo/Switch logo. Currently it's formatted as exFAT, emuNAND is file based, not partition, and it works fine. I'm still experimenting so there's nothing important on it. I can (and will) reformat it without loss.

It's been used exclusively with this switch, but not that much. I'd guess both the switch and the card don't have more than 100 hours of work time. Last time I used it prior to this week was last year. Basically only played Diablo III, Animal Crossing and Mario Kart 8 on it. It's not had that much read/write cycles.

 

[Hayato213]

Tried both FAT32 and exFAT, multiple times, no difference. Black screen after Nintendo/Switch logo. Currently it's formatted as exFAT, emuNAND is file based, not partition, and it works fine. I'm still experimenting so there's nothing important on it. I can (and will) reformat it without loss.

It's been used exclusively with this switch, but not that much. I'd guess both the switch and the card don't have more than 100 hours of work time. Last time I used it prior to this week was last year. Basically only played Diablo III, Animal Crossing and Mario Kart 8 on it. It's not had that much read/write cycles.

I would recommend going the FAT32 route, I mean everything can be done in FAT32, you have no need of exFAT, exFAT is probably the reason you are getting the black screen, Also you should go with highest available Atmosphere build if you have a sysnand version on 2.0.0 to 4.1.0, as the 0.19.1 build had a problem with it.

 

[urherenow]

@Solo761 we're kind of hijacking the thread here. Please start a new thread to continue, or point me to it, if you already have. Your SD isn't stuck in 1bit either, so it's not a hardware problem (at least not with the sd or sd slot... could be a RAM problem). It's probably either file corruption (switching from fat32 to exfat and back won't do you any favors if you're copying the same corrupted file back and forth), or something silly like a theme, sys module, or game cart slot firmware...

 

[ZachyCatGames]

also cluster is off, it should be 32kb cluster.

Cluster size is fine.
On fat32, you want to use 64KB (highest fat32 allows for).
On exfat, you probably want to use 128KB or 256KB.

 

[Hayato213]

Cluster size is fine.
On fat32, you want to use 64KB (highest fat32 allows for).
On exfat, you probably want to use 128KB or 256KB.

Well it is true that 64kb cluster ain't a bad recommendation for larger card, but do keep in mind higher cluster would cause files to take up more space on the SD card, even though the trade off is worth it as you get faster loading time, reason for the 32kb so you would minimize the amount wasted of space, due to the fact screenshot, homebrew files are really small and game's update and dlc file tends to be small. So it really come down to what people really wants.

 

[CaptainHIT]

I've tried and searched alot to find a solution by myeself but I think I need help:
After I've updated my (RCM-able) Switch to 12.0.1 I've formatted my 400GB Sandisk Ultra microSD and wanted to start a fresh new emuMMC. This card already had emuMMC, but was done by hand (created after the switch hacking guide) prior Hekate's emuMMC creation tools were even built in.
Well, I've cleaned the partitions, formatted it as FAT32 (32k clustersize) and then started everything from scratch again with the switch hacking guide.
Everything went out right of course, I also put in the latest sigpatches, but when I want to install something, doesn't matter if old or new software, doesn't matter if Goldleaf or Awoo-Installer, doesn't matter if trying to install to SD or internal memory, I always get the same error.

It's the latest Atmosphere, Hekate, sigpatches on emuMMC.

 

[petspeed]

I've tried and searched alot to find a solution by myeself but I think I need help:
After I've updated my (RCM-able) Switch to 12.0.1 I've formatted my 400GB Sandisk Ultra microSD and wanted to start a fresh new emuMMC. This card already had emuMMC, but was done by hand (created after the switch hacking guide) prior Hekate's emuMMC creation tools were even built in.
Well, I've cleaned the partitions, formatted it as FAT32 (32k clustersize) and then started everything from scratch again with the switch hacking guide.
Everything went out right of course, I also put in the latest sigpatches, but when I want to install something, doesn't matter if old or new software, doesn't matter if Goldleaf or Awoo-Installer, doesn't matter if trying to install to SD or internal memory, I always get the same error.

It's the latest Atmosphere, Hekate, sigpatches on emuMMC.
View attachment 261798 View attachment 261795 View attachment 261797

Are you sure you have the correct sigpatches on your SD card? You can download them from here: https://github.com/ITotalJustice/patches/releases
How do you boot CFW? If you use the fusee_primary payload directly or boot it though Hekate then you need to download fusee.zip
If you boot FSS0:fusee_secindary with Hekate you need to download hekate.zip
Unzip the downloaded file to the root of your SD card and restart the switch

 

[smf]

Depends, in most cases yes, capacity is faked, especially with these with bigger capacities. But I guess in some other cases, i.e. 16/32 GB it could be that branding is faked because they get more money for Samsung Evo 32 GB than no name 32 GB .

At work we had some sandisk cards that had absolutely terrible performance, which I always figured were fake but they came through the normal distributor and so we could never prove anything. The only visible difference was they had a different country, so it might be that sandisk themselves ended up getting done over when they contracted that factory.

Write speed was incredibly lumpy and we were barely writing anything.

 

[CaptainHIT]

Are you sure you have the correct sigpatches on your SD card? You can download them from here: https://github.com/ITotalJustice/patches/releases
How do you boot CFW? If you use the fusee_primary payload directly or boot it though Hekate then you need to download fusee.zip
If you boot FSS0:fusee_secindary with Hekate you need to download hekate.zip
Unzip the downloaded file to the root of your SD card and restart the switch

I've used the hekate sigpatches because I was booting from hekate. I'm booting Atmosphere FSS0 EmuMMC from the launch menu. Do I never used fusee_secondary up to this date.
I also copied over hekate_ctcaer_(version).bin over to the atmosphere/reboot_payload.bin though this isn't written on the cfw guide. It was before, so I copied over anyways like I always did before. So is this unnecessary?

 

[Hayato213]

I've used the hekate sigpatches because I was booting from hekate. I'm booting Atmosphere FSS0 EmuMMC from the launch menu. Do I never used fusee_secondary up to this date.

You have to make sure that your patches match with the build version of Atmosphere that you are using.

 

[CaptainHIT]

You have to make sure that your patches match with the build version of Atmosphere that you are using.

I did that.

--------------------- MERGED ---------------------------

At work we had some sandisk cards that had absolutely terrible performance, which I always figured were fake but they came through the normal distributor and so we could never prove anything. The only visible difference was they had a different country, so it might be that sandisk themselves ended up getting done over when they contracted that factory.

Write speed was incredibly lumpy and we were barely writing anything.

I bought mine from a nationwide tech-store in germany called Saturn. I didn't notice any big problems until recently. It got slower and slower with time. I've checked it with Crystal Disk Mark and it had poorer results compared to the benchmarks found online. Especially writing to the disk was around 75% slower than promised.

 

[kakaka1]

I'm on 0.19.2 , 12.0.1 OFW using latest sigpatches and fusee, no emunand. Only Xenoblade Chronicles 2 gave "software closed because an error occurred" after latest version update. So far i've changed the nsp files, installed nsp files with goldleaf, tinwoo installer but no luck. Can anyone help me? Much appreciated.

 

[petspeed]

I've used the hekate sigpatches because I was booting from hekate. I'm booting Atmosphere FSS0 EmuMMC from the launch menu. Do I never used fusee_secondary up to this date.
I also copied over hekate_ctcaer_(version).bin over to the atmosphere/reboot_payload.bin though this isn't written on the cfw guide. It was before, so I copied over anyways like I always did before. So is this unnecessary?

If you boot with Hekate and want a reboot to use the Hekate payload then it is necessary to replace the file. However it could be that it has already been done in the downloads from the guide you used.

 

[smf]

I bought mine from a nationwide tech-store in germany called Saturn. I didn't notice any big problems until recently. It got slower and slower with time. I've checked it with Crystal Disk Mark and it had poorer results compared to the benchmarks found online. Especially writing to the disk was around 75% slower than promised.

How old is it?

 

[Hayato213]

I did that.

--------------------- MERGED ---------------------------


I bought mine from a nationwide tech-store in germany called Saturn. I didn't notice any big problems until recently. It got slower and slower with time. I've checked it with Crystal Disk Mark and it had poorer results compared to the benchmarks found online. Especially writing to the disk was around 75% slower than promised.

Should test the card with H2testw for Windows, and F3X for Mac.