I'm sorry, but I don't really get what you mean by clean install.Fudge said:Very odd. I would try doing a clean install of 4.2E or 4.3E to see if you can fix the problem.
I'm sorry, but I don't really get what you mean by clean install.Fudge said:Very odd. I would try doing a clean install of 4.2E or 4.3E to see if you can fix the problem.
When we say a clean install we mean a fresh download from nus unpatched by any wii tool. You can download them via NUSD and install them via any wad manager or use a tool like Wii Mod to install them right after downloading it.JoostinOnline said:I'm sorry, but I don't really get what you mean by clean install.jskyboo said:You could try downloading Wii Mod, go to the IOSs menu and check if 60 is clean. If it isn't install a fresh copy. If it is clean, try checking IOSs and posting the resulting csv. Does the Wii hang when you start it with the sd card ejected as well?
You really should bother to read previous posts.
I did, Syscheck checks permissions. So the output told us the version was untouched and it didn't have permissions patched. Wii Mod checks the hash against the hashes of clean installs from nus, so if the IOS is not clean it may be messed up but it also does not have permissions patched. Also the output from check IOS in Wii Mod tells more info.
Very odd. I would try doing a clean install of 4.2E or 4.3E to see if you can fix the problem.awful_name said:QUOTE(Fudge @ Jul 3 2011, 12:37 AM)
When I installed 4.1E I downloaded it with ModMii (the download page 1) and then installed it with Multi-Mod Manager. But okay, I'll try with 4.2E.jskyboo said:When we say a clean install we mean a fresh download from nus unpatched by any wii tool. You can download them via NUSD and install them via any wad manager or use a tool like Wii Mod to install them right after downloading it.JoostinOnline said:I'm sorry, but I don't really get what you mean by clean install.jskyboo said:You could try downloading Wii Mod, go to the IOSs menu and check if 60 is clean. If it isn't install a fresh copy. If it is clean, try checking IOSs and posting the resulting csv. Does the Wii hang when you start it with the sd card ejected as well?
You really should bother to read previous posts.
I did, Syscheck checks permissions. So the output told us the version was untouched and it didn't have permissions patched. Wii Mod checks the hash against the hashes of clean installs from nus, so if the IOS is not clean it may be messed up but it also does not have permissions patched. Also the output from check IOS in Wii Mod tells more info.
Tried it now, but it just says "Press any button to continue" and then goes back to the menu without saving anything.
Very odd. I would try doing a clean install of 4.2E or 4.3E to see if you can fix the problem.jskyboo said:QUOTE(awful_name @ Jul 2 2011, 05:38 PM) QUOTE(Fudge @ Jul 3 2011, 12:37 AM)
When you tried going to which menu IOS menu or checking your IOSs? What IOS was loaded(up in the top right on main menu)? You should probably try the IOS if you already tried reinstalling the system menu. One of them is likely messed up the question is which....or maybe its something completely different, be on the look out for the Spanish Inquisition.awful_name said:Tried it now, but it just says "Press any button to continue" and then goes back to the menu without saving anything.
When I installed 4.1E I downloaded it with ModMii (the download page 1) and then installed it with Multi-Mod Manager. But okay, I'll try with 4.2E.
And a fair amount of that info is wrong. It often detects patches that aren't applied, or misses ones that are. That's why I don't suggest it. It's still a new app though, so I imagine with time a lot of the bugs will be fixed.awful_name said:Also the output from check IOS in Wii Mod tells more info.JoostinOnline said:So when did this start?
As I stated in the OP, when I tried restoring from the BootMii backup.
I just wanted to make sure. There have been a lot of cases lately where people fail to mention things they did right before the problem occured, usually because they don't think it's significant. I didn't want for this thread to drag on for days before you mentioned you did [insert failure] after the restore.
QUOTE(jskyboo @ Jul 2 2011, 05:48 PM)
If you are having problems with Wii Mod please post on the Wii Mod thread and I'll help resolve the issues you are having. And as for how new Wii Mod is follow the link at the bottom of the change log to find out about the history of Wii Mod and MMM.JoostinOnline said:And a fair amount of that info is wrong. It often detects patches that aren't applied, or misses ones that are. That's why I don't suggest it. It's still a new app though, so I imagine with time a lot of the bugs will be fixed.
Joostin slaps himself.jskyboo said:If you are having problems with Wii Mod please post on the Wii Mod thread and I'll help resolve the issues you are having. And as for how new Wii Mod is follow the link at the bottom of the change log to find out about the history of Wii Mod and MMM.JoostinOnline said:And a fair amount of that info is wrong. It often detects patches that aren't applied, or misses ones that are. That's why I don't suggest it. It's still a new app though, so I imagine with time a lot of the bugs will be fixed.
Well we were unable to get it to work, we needed to use comex' NAND formatter to fix it. If really nothing works now it could be such a NAND problem.awful_name said:Essentially, I'm trying to downgrade a Wii to system menu 4.1E from system menu 4.2E after it was accidentally upgraded.
I had a BootMii backup from before, but it was complaining over being from another Wii, so I overrode the check.
Hi, it sounds like a NAND problem, I remember a guy with a very strange one:
QUOTEactaully, the usb channel loads fine and works but when the wii is turned off, it won't turn back on and i ahve to restore the nand
I've seen this 5 times in the past. Reinstalling all IOS's fixed the problem for those who were able to run homebrew. Most couldn't get the HBC or Priiloader to run without freezing, and games wouldn't work. Only one person had 4.3, and since BB2 wasn't an option, he had to get a new Wii.FIX94 said:Well we were unable to get it to work, we needed to use comex' NAND formatter to fix it. If really nothing works now it could be such a NAND problem.awful_name said:Essentially, I'm trying to downgrade a Wii to system menu 4.1E from system menu 4.2E after it was accidentally upgraded.
I had a BootMii backup from before, but it was complaining over being from another Wii, so I overrode the check.
Hi, it sounds like a NAND problem, I remember a guy with a very strange one:
QUOTEactaully, the usb channel loads fine and works but when the wii is turned off, it won't turn back on and i ahve to restore the nand