I've updated my FW to 8.0.1 and downloaded the latest BOOT.DAT 2.7.1 once done, I did the whole power + vol hold with the dongle and it loaded the logo, but it did not load the menu saying "An error has occured"
When I read the thread title of this thread - I half expected the OP to say they'd - 'Sold their soul to Santa'.
If you did not have a custom theme installed and you are having this issue it may be that you are using a exfat sd card but applied the non-exfat update. There will be 209 files/folders in the update firmware .zip if its non-exfat and 213 if exfat.
Verify you have the correct update file with 213 files. If you do, try removing your sd card and booting stock, does it work? If yes, try formatting and using fat32 and see if it boots? If yes, then you did not apply the exfat update.
That's gonna get you banned. You should never go online on a hacked Switch, the only way to safely go online is on a clean stock NAND, for example you can use emuNAND for CFW and keep your sysNAND clean for online.
Only if he installs NSP's etc.
I always go online with my Switch in OFW and havent been banned. Only recently setup emunand because of a couple of NSPs I wanted to use.
There haven't been many reports of bans recently (past few months)
It's likely Nintendo are simply logging everything for when they decide to hand out more bans, so that you haven't been banned yet means nothing.
I've been using online in OFW since before SX OS and when it was released.
I only setup emunand when I decided to do something other than XCI loading, I don't think there is any risk unless the OP does more than XCIs with SXOS in OFW and goes online.
Back on topic though, I also think it could be exfat/corrupt SD card.
People have gotten banned just for running CFW while online and doing nothing else.
Not sure about running CFW offline and booting OFW before going online. That may depend on the CFW, SX OS for example does not have creport and therefore is unsafe. In theory Atmo is safer, but only time will tell.
Last edited by The Real Jdbye,
Always disable custom themes before updating fw. Don't let friends put anything on your Switch that you have no idea of how to handle or what issues it can cause.
You can remove it manually by deleting the folder sxos/titles/01000000001000 on your SD
Then your SX os should boot again
You can remove it manually by deleting the folder sxos/titles/01000000001000 on your SD
Then your SX os should boot again
You are not reading very carefully.
Forget anything and everything theme related. It will only cause you problems. If you've tried installing one, reverse all changes back to default. Only worry about themes after you've fixed everything.
I already gave you advice. Follow it and get back to us. If you cannot, then we cannot help you.
It is a custom theme problem everyone who updates to 8.01 either from choi or through OFW will run into this error with themes installed. He just needs to simply delete the NXTheme folder via sxos/titles from his sd card to get rid of the error. Has nothing to do with exfat
Similar threads
- Locked
-
-
-
@
SylverReZ:
If you want a good system to port it to, at least have a good programmer and knowledge.+1 -
-
-
-
@
Psionic Roshambo:
I didn't know they made an MSU cart for the Genesis.... I knew about the SNES one and the library for that is rather large but the Genesis one has very few games+1
-
-
@
SylverReZ:
An FPGA could probably replicate the chip's functionality without buying donor parts.+1
-
-
-
@
Psionic Roshambo:
Like not emulating the entire SNES but just a loader and the enhancement chips perhaps even slightly overclocked like FX-2
-
-
-
-
-
-
-
@
SylverReZ:
@Psionic Roshambo, The Doom NES cartridges, a few batches were made. One was given to AVGN as seen in his Doom video.+1
-
-
@
Sicklyboy:
I finally modeled and 3d printed the new HDD cages I need in order to build my 2nd NAS. Original ones don't fit the mounting holes on the hdds I'm using. Been sitting on this project for over 2 years smfh -
-
@
Sicklyboy:
I'm finally gonna get this NAS racked and powered on tonight, install truenas core, and burn the disks in with badblocks
-
@
Sicklyboy:
Also another 70TB going in the front mount drive bays of this server. 182tb raw, going to probably use a zfs RAID-Z3 for 3 parity disks, so 140TB usable
-
@
Sicklyboy:
I could claw back 14tb by only doing 2 parity disks but I feel like with 13 disks in the RAID I'd be kind of pushing my luck on rebuild time if I encounter a disk failure
