epichasem.blogg.se

1. #Savegame manager gx wii u exception dsi occurred install
2. #Savegame manager gx wii u exception dsi occurred Patch
3. #Savegame manager gx wii u exception dsi occurred full

But I also have a wii with a non-working disk drive and have been using uloader 3.5 with the usb hard drive for a while with no problems.

#Savegame manager gx wii u exception dsi occurred full

I have a full working we and the new uloader loaded and works fine. I was also reading on here about Uloader saves game files in your SD but lets say my SD is only a GB and is full could this also affect adding new games, not sure what to do, didnt have any problems before uploading loader GX. Going to try and extract ISO’s and put them on my computer and wipe the drive and is formatting through Uloader better than formatting it through WBFS Manager 3.0. So I uninstalled the WAD channel but not my SD card wonder if I should delete it there also but now Uloader is having the same trouble, could of adding loader GX somehow mess up my HDD, and wonder if anyone has a problem with DDR3, it installs but says it cant view partition or access partition but my other games work fine, I even installed it twice. So I installed that and used it for a couple days but had many problems and errors and just didnt load a lot of the games right. I softmodded my 4.2u menu wii and when I first got Uloader up and running, didnt run into any issues until a friend showed me his USB loader GX and it looked really nice so I read you can have both on here. The problem is (well not really a problem, good for me) is that my Wii is old enough to support boot2 changes so I’ve never had to mess about too much with preloader. I’ll be updating my Bootmii/preloader guides once I’ve done a bit more research and testing myself. You may want to start making some NAND backups to save yourself from such messes in the future. Although it will warn you it is not safe to do so if bootmii is not at boot2, but a few people are reporting success with it, see these threads: and although bit more conflicthing info on that one till I posted the video!! To restore it you need a gamecube controller as well so that you are able to hit A+B+X+Y at the same time in order to restore the NAND. In Homebrew Channel press the home button to access Bootmii (Once you’ve installed it to IOS via the hackmii installer) and backup the nand.

#Savegame manager gx wii u exception dsi occurred Patch

Just for my own reference if anyone else has the same issue, when you reinstalled preloader did you also patch IOS60 again or is it still the original IOS60?Īlso I learnt yesterday whilst trying to troubleshoot your issues that it is possible to recover your NAND with Bootmii as IOS as long as you have preloader also installed. As well as any other detail on exactly what you’ve done in order if you can remember.Ĭongrats. Įxactly what guide did you follow? If I can get an idea of what you’ve been doing it might be helpful.

In which case you can run Trucha Bug restorer hopefully to add it again.

#Savegame manager gx wii u exception dsi occurred install

Otherwise you can use savemii in conjuction with a modchip to create a custom boot disk to install sys menu 4.1 (the only way to fix in recovery mode is to upgrade the sys menu rather than reinstall it, i think!!!) Have you attempted to downgrade any IOS’ other than 15 which you should have restored before reboot if you was using trucha bug restorer to install as your an LU65? Also you haven’t removed 249 have you? As wadmanager needs that to run, which could be the problem. I assume you’ve used Any Title Deleter DB (If you need it let me know and I’ll whack it up on my mediafire) to remove IOS 222 and 223 as well? If none of that works I think your going to have to call in your warranty or try using savemii although I don’t know of any games that contain sys menu 4.1 on the disc yet. Although you said this happened after you installed cios 222/223 which confuses me even more, I have never heard of anyone bricking their wii through installing the cios 222. If it still doesn’t boot after removing all wads, try installing sys menu 4 again and original IOS60. Except Cioscorp wad if you ever installed that as that will remove every IOS. Starting with the most recent one you installed to the first one you installed.

I would imagine either your SD card is screwed (thou probably unlikely) or at some point somewhere you have installed a bad wad, possibly one that’s not meant for your region wii? The only thing I can recommend now is that you put all of the wads you have installed back onto your SD and uninstall them with Wad Manager 1 by 1. That error normally relates to a bad wad, but if they are all getting it, i doubt it is.