switch boot.dat error
- Thread starter MustangBE
- Start date
- Views 23,349
- Replies 47
Smells like you’re booting SXOS instead of Hekate/Atmosphere.
Here’s a guide for converting (and just a good guide in general to check your work.)
https://rentry.co/SwitchHackingIsEasy
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?
-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?
Last edited by MustangBE,
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?
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.
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.
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.
Why is your "payload" file extention .ini?
payload should be a .bin file (payload.bin). Download the correct file and try it again; it should work.
payload should be a .bin file (payload.bin). Download the correct file and try it again; it should work.
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.
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
Attachments
Last edited by MustangBE,
Reading 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.
Yeah…I think I’m going to have to concede and agree we need to comfirm/deny the sd reader as the issue. le sigh
@MustangBE
as long as it‘s not a mobo issue, reader replacements are cheap and easy to test. Youcan get them cheaper from Aliexpress but Amazon is faster and has better return options.
https://www.amazon.com/s?k=nintendo+switch+sd+card+reader
format your sdcard with "SD Formatter". otherwise switch wont recognize it, thats why you get a boot.dat error
Boot Hekate and do an SD card diagnostic check.
If it's showing up that it's in 1-bit mode then your SD card reader/connection is faulty damaged
If it's showing up that it's in 1-bit mode then your SD card reader/connection is faulty damaged
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
i have sdformatter v4.0. try to find it. it formats to fat32
Similar threads
-
-
-
@
Psionic Roshambo:
Broken condoms lead to broken hearts, won't someone think of the children!!! Lol+2 -
-
-
-
-
-
-
-
-
@
Xdqwerty:
@SylverReZ, @Psionic Roshambo something like each group of 3 does the exam (dunno how to explain it)+1 -
-
-
-
@
Xdqwerty:
@Psionic Roshambo, More or less those activities where two or more people do a exam instead of 1 (I still don't know how to explain)
-
-
-
-
-
-
-
@
K3Nv2:
I wish we could comment on Google reviews some of them just sound like they were written by r tards+2 -
-
