My guess is it stands for MicroController Unit.What does mcu stand for/What is the mcu
You might want to check your sd card for errors with h2testw, as it could be dying. Backup your somewhere safe beforehand, empty the sd card completely, then run h2testw with the "read and verify" setting. It should tell you if it's faulty. Also check the lock slider on the sd card adapter if you have an old 3ds system, or change it completely.I tried to add agp_gba_firm to my SD card via ftp - the 3DS folder got affected in the process (I renamed it then named it back before ending ftp session) - since I did this Universal Updater and Twilight Menu have completely stopped working for me.
Twilight Menu will flash white and then boot back to menu
Universal Updater will tell me the Unistore is wrong and even if I delete store data in /3ds/ it will do the same thing (and maybe crash the system)
It's odd because PKSM and checkpoint both seem ok despite having files in the same location (and Twilight Menu doesn't have anything in /3DS/ anyway)
I can't even uninstall the applications or reinstall them - FBI tells me there was an issue attempting to uninstall and reinstalling also doesn't work.
EDIT: it seems the other apps will load but not run properly hshop gets an error when I try to download anything from it. But Luma Menu seems fine and games still boot.
Check this...i got the backup and now I've recovered everything, from old data, to the sd card encrypted game save data (using movable.sed and other tools).
Now, next, I'm looking to recover my Mii Maker and Mii Plaza save files. Using ninfs, I decrypted my nand.bin,
You already started a separate thread about this at https://gbatemp.net/threads/how-can-i-decrypt-nand-sysdata-saves-mii-maker-mii-plaza-etc.631010/ . Posting your problem in two different places just makes things confusing.Any help would be appreciated
I want to know if its safe to update my console firmware or if I should do something first (like update luma first or something).
Ok you're on boot9strap, good, what you want to do now is update b9s (optional but recommended) and Luma3DS, before updating the firmware on the 3ds. After doing that then update the firmware from the system settings as normal.My current firmware: 11.2.0-35U
Luma: v7.1-cf0b05e2
Definitely not Luma3DS.Anyway, I don't know if this problem is related to the console or luma not being updated
Maybe. But it's awfully specific it happening in specific games (like you described), i'd try reinstalling those games (not the Download Play tho) do this after you update Luma3DS/b9s/3ds etc. as for the DP app it might fjx itself after updating fw (if there's something wrong with it.or if is a console error (like a faulty wi-fi card)
Thank you.Ok you're on boot9strap, good, what you want to do now is update b9s (optional but recommended) and Luma3DS, before updating the firmware on the 3ds. After doing that then update the firmware from the system settings as normal.
Definitely not Luma3DS.
Maybe. But it's awfully specific it happening in specific games (like you described), i'd try reinstalling those games (not the Download Play tho) do this after you update Luma3DS/b9s/3ds etc. as for the DP app it might fjx itself after updating fw (if there's something wrong with it.
Not sure but could be hardware related (wifi board like you said).But now I have another problem, a message saying that "An exception ocurred" appears randomly, for example a little after turning on the console (in the 3ds menu, not when I turn the console on) or sometimes after opening a game or closing it.
This is when I have wireless connection on, if it's off then the console works fine.
No.I don't know if it's because of the console not on the current firmware,
Yea.. One more thing to try, is to open the 3ds and re-seat the wifi board then test again. It might not do anything if the wifi board is damaged somehow, but sometimes the board could get loose if the system fell accidentally etc. and it's worth a try imo.but i'm afraid that if I update the console then at the middle of the update the error occurs.
It's not necessary. But it's recommended to keep regular backups of your game saves (with Checkpoint), or even the Nintendo 3ds folder (if you want).Also I backed up the sd before updating luma just in case.
The key thing of interest here is the "boss" process. This comes up occasionally but no one really knows what causes this error. It can be a problem with the wifi board, but in many cases the wifi board is completely fine and you should probably avoid tinkering with the interior of your unit unless it's absolutely necessary.But now I have another problem, a message saying that "An exception ocurred" appears randomly, for example a little after turning on the console (in the 3ds menu, not when I turn the console on) or sometimes after opening a game or closing it.
Not sure but could be hardware related (wifi board like you said).
No.
Yea.. One more thing to try, is to open the 3ds and re-seat the wifi board then test again. It might not do anything if the wifi board is damaged somehow, but sometimes the board could get loose if the system fell accidentally etc. and it's worth a try imo.
It's not necessary. But it's recommended to keep regular backups of your game saves (with Checkpoint), or even the Nintendo 3ds folder (if you want).
Well I removed the sd card and the console worked without this error showing up or any crash.The key thing of interest here is the "boss" process. This comes up occasionally but no one really knows what causes this error. It can be a problem with the wifi board, but in many cases the wifi board is completely fine and you should probably avoid tinkering with the interior of your unit unless it's absolutely necessary.
The first thing to do is to see if the error goes away if you remove your SD card. If so, standard procedure is to copy everything off the SD card (Roadkil's Unstoppable Copier is recommended), format the card, test the empty card with h2testw, and then copy everything back if the test is okay. Sometimes this is sufficient to make the error go away.
The other thing that sometimes helps is to update the system in Safe Mode.
You can read about different light colors at https://github.com/SciresM/boot9strap/releases . "Pink" in this case corresponds to "magenta".By some days my new 3ds xl modded with luma 11 and b9s doesnt turn on, infact when I try to do so a red light on top and a blue light below appears and it shuts down. I tried to update boot.firm and boot.3ds copying the new luma files but nothing, tried to turn on the nintendo pressing select but only 2 times it worked and applied the option to load the new version. I also reformatted and verified the micro sd that i user with Minitool partitioning wizard and H2testw but no error appeared, and also tried to turn the 3ds on without the micro sd and by doing so the red light is pink.
Did you follow https://3ds.guide? Are you running FBI through Homebrew Launcher, or from the Home menu?So after installing FBI and using it to install checkpoint and the rest of the main apps the very first time
yes. i have tried both. but i am running it from the home screen usually. it doesnt matter which one i use.Did you follow https://3ds.guide? Are you running FBI through Homebrew Launcher, or from the Home menu?