Twilightmenu showing up in 3DS without mircosd card inserted and all homebrew apps won't appear

[Yulian_guardsman]

I was having difficulties with twilight menu after its latest update and found there were was a new [twllmenu] version under gbarunner2 in the Universal updater store as updating ndsbootstrap solved issues the first time. I installed it using the universal updater and it immediately gave me a vague short error and crashed my system. Then upon rebooting all the homebrew apps were gone except nitrohax and twilight menu. This persisted even after I removed the microsd card and rebooted.

Inspecting the sdcard on my computer showed that all the twilight menu files were duplicated with "files that were too long" to be deleted in the _gba and _nds folders. Putting it back in my 3ds and examining it in system settings the microsd card will perpetually load and never finish. This leads me to believe there is malware on the universal updater store and I am just wanting to know how the hell do I fix this?

 

[Kwyjor]

This leads me to believe there is malware on the universal updater store

Come on, seriously!? Do you really think you would be the one and only person affected by something like that? Don't you think the entire forum would be brimming with anguish today if that was the case?

By far the most likely explanation is that your SD card is failing, which is something that absolutely happens all too frequently.

Then upon rebooting all the homebrew apps were gone except nitrohax and twilight menu.

By "all the homebrew apps", do you mean anything that was installed to your SD card, or do you still have commercial software you installed to your SD card one way or another that are showing up?

TWiLight Menu is special because it is installed to the NAND. (Not sure about nitrohax; that's kind of odd.)

Regardless, the solution at this point is to copy everything off the SD card to your PC. Use Roadkil's Unstoppable Copier to make sure you get everything you can. Then format the SD card and test it with h2testw. If h2testw says the card is still okay, then you can copy everything back. That's usually enough to fix problems like this.

 

[Yulian_guardsman]

Come on, seriously!? Do you really think you would be the one and only person affected by something like that? Don't you think the entire forum would be brimming with anguish today if that was the case?

By far the most likely explanation is that your SD card is failing, which is something that absolutely happens all too frequently.

By "all the homebrew apps", do you mean anything that was installed to your SD card, or do you still have commercial software you installed to your SD card one way or another that are showing up?

TWiLight Menu is special because it is installed to the NAND. (Not sure about nitrohax; that's kind of odd.)

Regardless, the solution at this point is to copy everything off the SD card to your PC. Use Roadkil's Unstoppable Copier to make sure you get everything you can. Then format the SD card and test it with h2testw. If h2testw says the card is still okay, then you can copy everything back. That's usually enough to fix problems like this.

No I mean everything from the homebrew launcher to luma3DS will not show up at all. Only Twilightmenu++ and nitrohax appear even when the microsd card is not inserted. Everything is still on the card and it worked perfectly until I installed that aforementioned GBARUNNER2 [twllmenu] update today because twilightmenu would not boot gba games anymore after the latest update for me. It would also not work for nds games either until I updated ndsbootstrapper and nothing as catastrophic happened when updating that first.

The 3DS is a fairly old console at this point of time and has ceased production a few years ago. So its not nearly as accessible to most people compared to the switch, where you would see many more people run into issues like this on average as its accessible to a wider audience. Therefore it would not be unheard of for people to run into obscure problems like this.

Thank you for clarifying that twilightmenu++ is written to the nand. It was never persistent like this before the latest update. When removing the microsd it used to disappear normally like every other app on the card.

h2testw says the card is still okay and the problem is persisting. Have never heard of a microsd card failing before in my life and never seen that happen before.

 

[Kwyjor]

Therefore it would not be unheard of for people to run into obscure problems like this.

The deliberate publication of malware on universal-updater would not be an "obscure problem".

h2testw says the card is still okay and the problem is persisting.

Did you copy everything off the card and format it as I suggested? h2testw is only supposed to be used on a completely empty card.

Have never heard of a microsd card failing before in my life and never seen that happen before.

Well, it happens here all too frequently.

When removing the microsd it used to disappear normally like every other app on the card.

That seems surprising.

 

[godreborn]

Check if sd card is being read by loading Luma settings, then use the 3dsx version of fbi, check if your games are listed under titles, any red ones?

 

[Yulian_guardsman]

The deliberate publication of malware on universal-updater would not be an "obscure problem".

Did you copy everything off the card and format it as I suggested? h2testw is only supposed to be used on a completely empty card.

Well, it happens here all too frequently.


That seems surprising.

I do have a backup I am going to try restoring with. h2testw says it is good and not failing at all. Does not look like its failing to me and is a twilightmenu problem. I assume its just copy paste?

Check if sd card is being read by loading Luma settings, then use the 3dsx version of fbi, check if your games are listed under titles, any red ones?

I cannot even access luma. It never loads thanks to the aforementioned universal updater crash that was a precursor to all of the thread above.

 

[Kwyjor]

h2testw says it is good and not failing at all.

You didn't answer the question. h2testw is not useful if the card is not empty. Was the card completely empty when you used h2testw?

I assume its just copy paste?

Did you read my first post? You should use Roadkil's Unstoppable Copier. Doing a copy-paste with Windows Explorer will probably run into problems.

Does not look like its failing to me

I guess if you already know everything then there's no point in posting in this thread anymore.

 

[Yulian_guardsman]

You didn't answer the question. h2testw is not useful if the card is not empty. Was the card completely empty when you used h2testw?

Did you read my first post? You should use Roadkil's Unstoppable Copier. Doing a copy-paste with Windows Explorer will probably run into problems.


I guess if you already know everything then there's no point in posting in this thread anymore.

Yes it was empty. Restoring from a backup solved the issue. Thank you for the assistance. i would not ever recommend the latest twilight menu updates after this bullshit they caused. Older versions of twilight menu work perfectly and don't add excessive folders like _gba and _nds and roms and a few others while duplicating itself and adding files that are "too long" in those folders.

TL;DR if your system is getting screwy then restore from a backup. The default Gbarunner2 takes time to start up just like ndsbootstrap and it takes way longer for some games than others. mgba is better overall so just go with that instead as gbarunner2 is the only gba emulator I've ever seen that his this weird graphics bug at the bottom of the screen. It's a cool menu though and a neat little app.

 

[Kwyjor]

Older versions of twilight menu work perfectly and don't add excessive folders like _gba and _nds and roms and a few others while duplicating itself and adding files that are "too long" in those folders.

Yes, of course, they must have deliberately written the program that way and there are no other possibilities. :-P

The default Gbarunner2 takes time to start up just like ndsbootstrap and it takes way longer for some games than others. mgba is better overall so just go with that instead. It's a cool menu though and a neat little app.

You shouldn't be using mGBA or Gbarunner2. open_agb_firm provides the best performance and compatibility; virtual console injects made with NSUI work mostly the same way.

 

[Yulian_guardsman]

You shouldn't be using mGBA or Gbarunner2. open_agb_firm provides the best performance and compatibility; virtual console injects made with NSUI work mostly the same way.

GBArunner2 comes as the default option for twilightmenu++ for whatever reason. I will try that out.

 

[godreborn]

Gbarunner2 is not technically an emulator iirc. I don't know what could've happened. I updated to the latest with Universal Updater the day it was released, no issues.

 

[AmandaRose]

Gbarunner2 is not technically an emulator iirc. I don't know what could've happened. I updated to the latest with Universal Updater the day it was released, no issues.

Exactly the same for me I updated with zero issues.

 

[Yulian_guardsman]

Gbarunner2 is not technically an emulator iirc. I don't know what could've happened. I updated to the latest with Universal Updater the day it was released, no issues.

open_agb_firm really is the best. They did say they were working on emulation problems with a graphical bug that is acknowledged on their development blog for GBArunner2. It's a graphical bug where the bottom part of the top screen has at least one line of distorted graphics. With the latest update of twilightmenu++ and updating gbarunner2 [twllmenu] and ndsbootstrap it was even worse with 4 lines making the textboxes of leafgreen unreadable. Never had any issues with any other emulators.

 

[godreborn]

open_agb_firm really is the best. They did say they were working on emulation problems with a graphical bug that is acknowledged on their development blog for GBArunner2. It's a graphical bug where the bottom part of the top screen has at least one line of distorted graphics. With the latest update of twilightmenu++ and updating gbarunner2 [twllmenu] and ndsbootstrap it was even worse with 4 lines making the textboxes of leafgreen unreadable. Never had any issues with any other emulators.

you need to use 64KBs allocation size if it's a larger card.

 

[Kwyjor]

GBArunner2 comes as the default option for twilightmenu++ for whatever reason.

It is more useful on the DSi where open_agb_firm and VC injects are not an option.

 

[Yulian_guardsman]

you need to use 64KBs allocation size if it's a larger card.

its an 8gb card. Had been looking into moving to a 256GB card for the lolz while I wait for the switch lite to get hacked but most youtube videos don't just link to a program that can format it to FAT32 like you guys did getting to the point here and one of the fake shills even has a fake guide site : http://3ds.console.guide

 

[AmandaRose]

its an 8gb card. Had been looking into moving to a 256GB card for the lolz while I wait for the switch lite to get hacked but most youtube videos don't just link to a program that can format it to FAT32 like you guys did getting to the point here and one of the fake shills even has a fake guide site : http://3ds.console.guide

1. Put the sd card in the 3ds and start it.

2.Press select and then load godmode9.

3. Press home button then select more

4. Select sd card format

5. Select no emunand

6. Select 64kb cluster.

Job done.

 

[godreborn]

I didn't know about open_agb_firm. I just placed it in a folder inside luma/payloads, so that it doesn't show a list of payloads when booting godmode. I have fastboot installed, so I mapped open_agb_firm to L to avoid confusion. I put the saves in the correct folder. everything is working as I wanted it to.

 

[Eveldee]

Great that the problem is solved, the card seem to be working fine so it should have just been an error in the filesystem that made it unmountable for the 3ds, I wonder if simply running chkdsk would've fixed it