i have did try with fat and fat32 with partition defaultSoooooooooooo. This might seem rude, but do you have a FAT/FAT32/exFAT in your switch?
i have did try with fat and fat32 with partition defaultSoooooooooooo. This might seem rude, but do you have a FAT/FAT32/exFAT in your switch?
OK. I'll tell you what I did with my SD card to see if that works. While your switch is turned on (not in CFW) insert your micro sd. It should tell you to reboot. once it reboots, shut it off and try going into cfw again.i have did try with fat and fat32 with partition default
I tryied like this now, didnt work... :/OK. I'll tell you what I did with my SD card to see if that works. While your switch is turned on (not in CFW) insert your micro sd. It should tell you to reboot. once it reboots, shut it off and try going into cfw again.
If this doesn't work then the only thing I can think of is the size of it being too small.
Then try looking up the sd card file sizes that are compatible with the switch. If a 2gb card is acceptable, the it's probably a bad sd.I
I tryied like this now, didnt work... :/
As discussed a failed init is card based and before the filesystem. Changing filesystem does not help.I keep getting failed to init sd card. tried exfat 200gb card and also 128gb fat32 card and same result. help!
--------------------- MERGED ---------------------------
I already tried setting the cluster from 32 to 16 but same thing happening.
--------------------- MERGED ---------------------------
does this only work on 5.1? i'm on 4.1.0 help please
2GB, aka SDSC, are not supported.i need help! the switch doesnt want to boot on CFW! (error: No FAT/FAT32/exFAT filesystem
i have a 2GB sd card (i have lost my 16gb sd card )
I'll check this. Thanks for reporting it.@CTCaer I've compiled a new .bin from the most recent master branch to test the archive bit. It doesn't seem to be working when I use the 'switch folder only' option. From what I can understand of your code, I think it might be opening the /switch folder and unsetting the archive bit for files inside it but not actually unsetting the bit for the switch folder itself. I was able to verify loading up a windows computer and unsetting the archive bit on only that folder fixed the issue for me. Homebrew works and all switch games work!
I know you're a busy man and everything but someone is claiming that your mod broke his license file for SX OS. Now I know you may not care much for SX OS, but if he did something like that, that might explain what happened. Anyways, here's the thread if you ever have the time and want to take a look/help out the user: https://gbatemp.net/threads/how-to-fix-sx-os-boot-dat-error.510109/Additionally, don't use the current fix attributes implementation, because it may (some had a problem, other didn't) render files in atmosphere and nintendo folders unusable.
I know you're a busy man and everything but someone is claiming that your mod broke his license file for SX OS. Now I know you may not care much for SX OS, but if he did something like that, that might explain what happened. Anyways, here's the thread if you ever have the time and want to take a look/help out the user: https://gbatemp.net/threads/how-to-fix-sx-os-boot-dat-error.510109/
I don't know actually. I don't use any backup loaders.@CTCaer which romfs do I use on 5.1 I loaded the standard one and my Skyrim cart gave me an instant error I might have to go back to my old hekate ini instead of the 3.0 one
That thread does not talk about fix sd card files attributes. With init not done, you can't do any changes on files.I know you're a busy man and everything but someone is claiming that your mod broke his license file for SX OS. Now I know you may not care much for SX OS, but if he did something like that, that might explain what happened. Anyways, here's the thread if you ever have the time and want to take a look/help out the user: https://gbatemp.net/threads/how-to-fix-sx-os-boot-dat-error.510109/
So have you thought that the switch you had, may had a sdmmc controller incompatible with the driver hekate (or SX os) uses?didn't break my license file. I feel like it did something to the way the switch reads my memory card. OFW reads the card perfectly ie. installs demos,save games, screenshots. all working fine but when I try to boot into sx-os using the boot.dat file it's like it's not reading it or doesn't see it. I had to go buy a new switch to get my sx-os to work. I used the same memory card and booted up first try. So I don't know what's going on. just seems odd.
I do t use backup loaders I never said I did, I use my cart only, also what breath of the wild mods are out for switch?I don't know actually. I don't use any backup loaders.
My mods for BotW and Odyssey still work though.
You can try on other threads.
(The only sure thing, is that in v3.0 the fusee patches are broken for switch 4.X)
That thread does not talk about fix sd card files attributes. With init not done, you can't do any changes on files.
Also he states that he just got sx os. He does not say that it worked before. I hate when assumptions and claims like that are made.
So, false information spreading. Hekate can't break a card. And if it has problem with hekate, he's bound to have problems with sx os payload that loads boot.dat.
(sx os payload uses a similar driver as hekate. It does not uses the switch's driver like the boot.dat code)
He also asked help through PM and I told him I had testing payloads for his case, so we can track down the incompatibility (because these sd work in Horizon and PC, so it must be a case we don't support), but I don't know if I'm willing to help now...
EDIT:
So have you thought that the switch you had, may had a sdmmc controller incompatible with the driver hekate (or SX os) uses?
No..
you're right I didn't try sx-os before I tried to dump nand. Like I stated I found it very odd that i had "fail to init sd" errors on a switch that's 3 months old and literally not being used just waiting for sx-pro to arrive. then I gave up on the nand dump and it won't read the boot.dat file.. then I get a new switch and just boots sx-os boot.dat file perfectly with same sd card.I don't know actually. I don't use any backup loaders.
My mods for BotW and Odyssey still work though.
You can try on other threads.
(The only sure thing, is that in v3.0 the fusee patches are broken for switch 4.X)
That thread does not talk about fix sd card files attributes. With init not done, you can't do any changes on files.
Also he states that he just got sx os. He does not say that it worked before. I hate when assumptions and claims like that are made.
So, false information spreading. Hekate can't break a card. And if it has problem with hekate, he's bound to have problems with sx os payload that loads boot.dat.
(sx os payload uses a similar driver as hekate. It does not uses the switch's driver like the boot.dat code)
He also asked help through PM and I told him I had testing payloads for his case, so we can track down the incompatibility (because these sd work in Horizon and PC, so it must be a case we don't support), but I don't know if I'm willing to help now...
would that controller change depending on the firmware version? cuz i started out on 4.1 and after 1 hour all i could think of was maybe i need to be on 5.1 and it didnt' work either.I don't know actually. I don't use any backup loaders.
My mods for BotW and Odyssey still work though.
You can try on other threads.
(The only sure thing, is that in v3.0 the fusee patches are broken for switch 4.X)
That thread does not talk about fix sd card files attributes. With init not done, you can't do any changes on files.
Also he states that he just got sx os. He does not say that it worked before. I hate when assumptions and claims like that are made.
So, false information spreading. Hekate can't break a card. And if it has problem with hekate, he's bound to have problems with sx os payload that loads boot.dat.
(sx os payload uses a similar driver as hekate. It does not uses the switch's driver like the boot.dat code)
He also asked help through PM and I told him I had testing payloads for his case, so we can track down the incompatibility (because these sd work in Horizon and PC, so it must be a case we don't support), but I don't know if I'm willing to help now...
EDIT:
So have you thought that the switch you had, may had a sdmmc controller incompatible with the driver hekate (or SX os) uses?
No..
Then what romFS?I do t use backup loaders I never said I did, I use my cart only, also what breath of the wild mods are out for switch?
you're right I didn't try sx-os before I tried to dump nand. Like I stated I found it very odd that i had "fail to init sd" errors on a switch that's 3 months old and literally not being used just waiting for sx-pro to arrive. then I gave up on the nand dump and it won't read the boot.dat file.. then I get a new switch and just boots sx-os boot.dat file perfectly with same sd card.
Not firmware version. But based on manufacturer's demands (volume produced) and supplier not able to meat these demands.would that controller change depending on the firmware version? cuz i started out on 4.1 and after 1 hour all i could think of was maybe i need to be on 5.1 and it didnt' work either.
If you use your switch completely offline, none.So what exactly are the risks of restoring a full unmodified NAND backup? I'm interested in using this to avoid bans before emunand is available.