Homebrew Retroarch Bricked (Switch)

[Notshane]

Okay, so I updated Retroarch from the Switch Homebrew Appstore. I have no idea what happened, but after I changed over to Ozone, the software bricked and now I can no longer boot into it at all.

I know there is a way to change the configuration through a text file in the microSD, so I want to know where that file is so that I can unbrick the software. And also where I can find a version of Ozone that loads on the current Retroarch on Switch, because for some reason, the update did not update Ozone, the theory I'm going by. Since it would make sense with the other UI being fine and I know Ozone was already its own problem with how it never stayed open and would infrequently change over to another UI based on the way certain things were loaded.

It has been a year now since the Switch has gotten Retroarch, so I am hoping I can get more help about it now than I did back then.

 

[Notshane]

And yes, I just realized I posted in the wrong category, I am very sorry. I thought I was in Switch - Exploits, Custom Firmwares & Soft Mods.

 

[arianadark]

since you gave out so little info, fat32 or exfat?

 

[Notshane]

since you gave out so little info, fat32 or exfat?

I mean, I figured all I needed to know was where the file was that has the configuration for which GUI loads first. I didn't think I needed to specify more information, but it's exFAT.

 

[arianadark]

retroarch works best with fat32 as exfat can corrupt your sd card, for now reinstall your files for cfw and only run retroarch with full ram access

 

[designgears]

Open up the main config and change it back, also, exfat and retroarch is a corruption bound nightmare. Move to fat32 or don't bother with retroarch.

 

[arianadark]

https://gbatemp.net/threads/retroarch-switch.492920/ always read up to avoid issues

 

[tinkle]

it's exFAT.

Found your problem

 

[crazy_p]

I mean, I figured all I needed to know was where the file was that has the configuration for which GUI loads first. I didn't think I needed to specify more information, but it's exFAT.

Delete your retroarch.cfg File in your Retroarch Folder and try again.
Btw its better to switch to Fat32 like the other People mentioned.

Oh yeah and download Retroarch from here, your Appstore installs Retroarch just partially.

 

[Notshane]

Delete your retroarch.cfg File in your Retroarch Folder and try again.

Thank you! It loaded up Ozone just fine after I removed that CFG and it seems to be working just fine now. In fact, it is running better than it did before. Only issue I have left are some games from one of my setup playlists saying "File could not be loaded from playlist." But, I think I can manage that on my own. I am just glad it works again. Thank you so much.

Oh yeah and download Retroarch from here, your Appstore installs Retroarch just partially.

I did download Retroarch online. I just updated it on the Appstore.

Btw its better to switch to Fat32 like the other People mentioned.

I talked with somebody else on here for quite a while about whether or not exFAT or FAT32 were better and a lot said exFAT was, so I am not going to bother going through all of this again, really. Unless somebody gives me a lot more ground in the argument as to why FAT32 is better, I am sticking with exFAT.

 

[tinkle]

Thank you! It loaded up Ozone just fine after I removed that CFG and it seems to be working just fine now. In fact, it is running better than it did before. Only issue I have left are some games from one of my setup playlists saying "File could not be loaded from playlist." But, I think I can manage that on my own. I am just glad it works again. Thank you so much.



I did download Retroarch online. I just updated it on the Appstore.



I talked with somebody else on here for quite a while about whether or not exFAT or FAT32 were better and a lot said exFAT was, so I am not going to bother going through all of this again, really. Unless somebody gives me a lot more ground in the argument as to why FAT32 is better, I am sticking with exFAT.

The exFAT driver that Nintendo uses is junk. Every time you close a homebrew app, you risk corrupting the whole memory card. I can't imagine why you would think that was the better choice.

 

[Notshane]

The exFAT driver that Nintendo uses is junk. Every time you close a homebrew app, you risk corrupting the whole memory card. I can't imagine why you would think that was the better choice.

It doesn't allow more than 4GB on a single file and I have a lot of resources on here that exceed that limit.

 

[Pipistrele]

Unless somebody gives me a lot more ground in the argument as to why FAT32 is better, I am sticking with exFAT.

So far, FAT32 had no known instances of data being randomly corrupted, while exFAT had a ton of reports on data being randomly corrupted. In fact, the whole "Pokemon Sword & Shield breaks your SD card" debacle a month ago was exactly a result of people using exFAT-formatted SD cards. I hope that's enough of a ground.

 

[Fugelmir]

I had a similar experience. I boot with an exfat card strictly for switch games, and an alternate card for homebrew like retroarch.

 

[shano]

It doesn't allow more than 4GB on a single file and I have a lot of resources on here that exceed that limit.

You can split 4GB files.

 

[Skirlez]

You should switch to FAT32.
exFAT can store files larger than 4gb,
Which is good for pirated stuff, basically the only thing above 4Gb related to switch modding.
However, you can split said files
Or USB Install them via Tinfoil or Goldleaf.

Of course, if you really want exFAT, you can stay on it, but when your SD card eventually corrupts don't say we didn't warn you.

 

[jellybeangreen2]

As others have said. Retroarch = FAT32.
If you just play commercial games only exFAT works great. You can get corruption using retroarch and exFAT combo.

 

[Mchi5]

I had a similar experience. I boot with an exfat card strictly for switch games, and an alternate card for homebrew like retroarch.

Have the same setup as you but took it a step further. My main 400gb card is exfat and sx os (because started on exfat) and only for switch games. and my secondary card is a 200gb fat32, with atmosphere so can run retroarch and emualtors. The perfect setup for me .

 

[Draxzelex]

And yes, I just realized I posted in the wrong category, I am very sorry. I thought I was in Switch - Exploits, Custom Firmwares & Soft Mods.

Personally, the Hardware section is the best for bricks as the term "brick" refers to a type of hardware issue. However the moderators felt that the Homebrew section fit better as your brick was due a homebrew application. The least fitting category is definitely the Exploits/CFW/Soft Mods as nothing about your post deals with exploits, CFW or a soft mod.

 

[Askot]

You must hear to everyone else: use FAT32, if you want to keep exFat and get corrupted again, dont complain if corruption files strikes back, I used Retroarch and magically I started to get data corrupted messages,