I have a new DS card 500GB for my hard mod switch.
I have put hekate / atmosphere / fusee sx files on the SD card but get the red boot.dat error on startup.
View attachment 332281
please any advice
i followed that site
-formatted to FAT32
-copy atmosphere-1.4.0-prerelease-e580c3970+hbl-2.4.1+hbmenu-3.5.1 to root of SD
-copy hekate_ctcaer_5.9.0_Nyx_1.4.0 to root os SD
-copy boot.dat and boot.ini from SX gear to root of SD
-copy sigpatches to SD root
-copy fusee.bin in bootloader/payloads
-create hekate_ipl.ini
-create exosphere.ini
-changed hekate.bin to payload.bin (in the hekate zip already was also a payload.bin)
also tried a previous version of hekate etc.
still get boot.dat logo on startup
A few days ago, I wanted to set up a game via awoo and kept getting the message that there was no usb connection.
It was connected to the PC with USB and charging.
Since the SD was almost full so I transferred everything to a bigger one with EaseUS.
Since then, the original SD card has been full of encryptions, strange characters and inaccessible files.
Now I get the BOOT.DAT logo with both SD cards.
Could the card reader be defective?
Getting boot.dat means the SDCard is at least reading. The pic doesn’t show corruption.
Just to be safe, you can test your cards with this to remove doubts:
h2testw — test to determine if your SD Card is good or not.
Is your Switch chipped with SX or HWFLY and which numbered guide did you follow below?
View attachment 332335
You only get boot.dat error if you are sending the SXOS payload. You need to inject fusee.bin payload instead when you enter RCM mode.I have a new DS card 500GB for my hard mod switch.
I have put hekate / atmosphere / fusee sx files on the SD card but get the red boot.dat error on startup.
View attachment 332281
please any advice
I
I am doing the test now but it takes 3 hours.
I don't think the SD card is the problem as it has always worked and the same problem happened with a new SD card.
Without SD card I also get the message BOOT.DAT, so is the card reader OK ??
The switch is chipped with SX and I followed nr 3.
Your card is probably fine. The test is just to remove any concerns you might have.
Since you are using SX chip you will need to follow instructions for nr 5
https://rentry.org/EristaSXCoreEmuNAND
pay close attention to
Step 2.
Rename hekate_ctcaer_x.x.x.bin to payload.bin.
Are you sure you downloaded/unzipped the SX Gear file? It points to the payload.bin file and you shouldn’t see anything about boot.dat after those two steps.get the same boot.dat error
yes, I put the sx gear on it (the 2 boot files).Are you sure you downloaded/unzipped the SX Gear file? It points to the payload.bin file and you shouldn’t see anything about boot.dat after those two steps.
If possible:
-provide an updated screenshot of the files
-open boot.ini and share what's in there.
yes, I put the sx gear on it (the 2 boot files).
I have read on another site that the SD card reader easily breaks down.
Post automatically merged:
Post automatically merged:
the boot.ini shows
[payload]
file=payload.bin
Yeah…I think I’m going to have to concede and agree we need to comfirm/deny the sd reader as the issue. le sighReading through this thread, I am leaning more towards sd card reader damage as well.
Top things that go wrong, The little containing arm that holds it in place and when you push the sd card n and out might be broken.
Also if you took the system apart recently, try reseating the actual sd reader. But when you do, check both the sd card and the port for broken pins. The port on the board seems to fall apart pretty often with removing the sd reader.
It worked but now it is in eFAT, is that a problem because i reed everywhere that FAT32 is better.format your sdcard with "SD Formatter". otherwise switch wont recognize it, thats why you get a boot.dat error
hmmm weird, as far as i know "sdformatter" only format in fat32.
i have sdformatter v4.0. try to find it. it formats to fat32