Now I am confused...... I remodded using mod me on the 4.2.... got dk on and working... but now I can't get online and get the cover art....I keep getting several different errors when I try to test my connection
maybe I should edit this part of the guide so that this includes stack dumps and dsi errors, those can occur randomly for no reason and thats normal, if it is very frequently, like urs it could be something more though, how is your usb hard drive formatted, and where do u have you covers folder being saved? Its possible the location doesn't exist, or ur trying to save to the sd card without one in there, or u are having troubles using ntfs or something like thatMarioBrotha said:I just realized my problem might be more ModMii related, so copy/pasting from noob paradise thread
I recently upgraded all of my softmodding stuff using ModMii. I have come into some problems.
First, I can't get priiloader installed. I had installed priiloader before, but now bootMii loads instead of it everytime I boot. I tried to install it using the app from the homebrew launcher, but it just restarts my wii, it doesn't open. I should mention that I have bootmii installed as boot2.
Also, on some odd times, my Wii crashes and I get a screen full of dump codes and errors (something a DSI exception). This happens everytime that I try to fetch the covers for my wii games from the USB Loader. It also happens when I try to open the Netflix app (which I installed using YAWMM). I can upload these codes if necessary.
help plz?
*If your Wii ever freezes, hold the power button on the Wii for 5 seconds to power it off then try again.ModMii Guide said:Note: if Bootmii was installed as boot2, then it will show up as soon as the Wii is turned on AS LONG AS it finds the bootmii folder (mentioned above) on the root of the SD card.
so u should rename the bootmii folder on your sd card something else, and if u ever need bootmii, just rename it back, there are a bunch of apps that will rename the folder for u, but thats for lazy ppl anyways, one is called bootmii switch and can be found in my Top Channels thread. Oh yea, its also possible u have ur priiloader autoboot settings set to load bootmii @ startup instead of priiloader. Also, if u need to access priiloader, after launching the system menu from bootmii @ boot2, hold reset
ModMii Guide
I am using the Wii Backup Manager that was downloaded from the ModMii guide, and it doesn't seem to copy the covers over the the hard drive. Where should I copy them? My hard is NTFS formatted, and I do have a SD card in my wii, but there is no covers folder or anything like that.XFlak said:maybe I should edit this part of the guide so that this includes stack dumps and dsi errors, those can occur randomly for no reason and thats normal, if it is very frequently, like urs it could be something more though, how is your usb hard drive formatted, and where do u have you covers folder being saved? Its possible the location doesn't exist, or ur trying to save to the sd card without one in there, or u are having troubles using ntfs or something like thatModMii Guide said:Note: if Bootmii was installed as boot2, then it will show up as soon as the Wii is turned on AS LONG AS it finds the bootmii folder (mentioned above) on the root of the SD card.
so u should rename the bootmii folder on your sd card something else, and if u ever need bootmii, just rename it back, there are a bunch of apps that will rename the folder for u, but thats for lazy ppl anyways, one is called bootmii switch and can be found in my Top Channels thread. Oh yea, its also possible u have ur priiloader autoboot settings set to load bootmii @ startup instead of priiloader. Also, if u need to access priiloader, after launching the system menu from bootmii @ boot2, hold reset
ModMii Guide*If your Wii ever freezes, hold the power button on the Wii for 5 seconds to power it off then try again.
and I don't support netflix so I don't have any advice regarding netflix, but I will say that if u want netflix, i think its even free from the shopping channel, at least the first couple months or something, some1 correct me if I am wrong
chop said:When I open the folder on my computer where Modmii is stored the computer freeze's for about 30 seconds. the mouse pointer still moves but I can't click on anything.
r u saying u r getting an error when trying to reinstall .NET Framework? Disregarding ModMii entirely, u should be able to uninstall/reinstall .NET Framework 3.5... so the fact that u cannot to me is an indication that your windows is screwy.iancer said:i know i have 3.5 installed from when i 1st used modmii, but i get an error when trying to reinstall...
hmmm, alll i want is 250dx56. damn.
there's nothing wrong with the newer priiloader ONCE IT IS INSTALLED. But installing it can lead to bricks as the new installer uses ahbprot and direct hard ware access via the HBC... but the problem is the HBC's network init bug can cause random crashes if a network connection isn't set up, and if this occurs in the middle of a priiloader installation, it can result in brick. This problem will not fully go away until a new HBC is released.hazzarduk1 said:Thanks for this great tool XFlak. Just a quick question really. I notice modmii seems to use a priiloader 0.4 version which is unable to update, is there a reason for this or am i safe to upgrade to 0.6? it seems 0.4 is unable to boot the wii with the black ops headset plugged in.
Well , i really like to see priiloader 0.6 anyway, but with a warning.XFlak said:ahbprot and direct hard ware access via the HBC... but the problem is the HBC's network init bug can cause random crashes if a network connection isn't set up, and if this occurs in the middle of a priiloader installation, it can result in brick. This problem will not fully go away until a new HBC is released.
So if u decide to install priiloader v0.6, make sure u have proper brick protection in place (ie. nand dump and bootmii @ boot2 if possible), also be sure to set up an internet connection before trying to install it, otherwise u run the risk of experiencing the HBC network init bug and bricking