Wasabi dx works on almost all backups, but reboots on NSMB
My new wasabi dx was installed and updated to 3.0. It sees and plays all other backups that I created for use with a D2pro (which the wasabi took the place of).
Here's what I've done:
My untouched, uncompressed NSMB image was dragged onto the BCA patcher, and I received a message stating that the patch was successful.
I burned the image using imgburn at 4x on Verbatim DVD-R. The first time I tried, the disk prompted for a system update, and I allowed it to update to 4.1u. Each time thereafter, NSMB would show up in the disk channel, and when the disk channel was selected, would throw up the NSMB splash screen. However, if Start was selected, the screen goes dark, the wii "tv screen" image covers the screen, and the wii boots back to the root menu.
I have read all the Mario Bros threads, and searched (unsuccessfully) to see if anyone else had encountered this problem or uncovered a solution. Lots of black screens and disc errors, but could not find any reports of reboots.
Things I have tried: reflashing the wasabi, reburning the DVD (with two different (NTSC) isos "known" to work), and trying different speeds and media. All resulted in the same outcome -- disk seen in the disk channel, but a wii reboot if started.
I don't think the problem is the BCA, as I can't even play for 5 minutes -- it reboots every time. My understanding is that without the patch, a few minutes of gameplay are possible until the game checks for the BCA data.
Hopefully, I've provided enough background information to allow someone smarter than me to indentify the problem here. Thanks in advance to anyone that has any suggestions or solutions to this problem. The only reason I replaced the D2pro with the wasabi is to gain BCA functionality, and the fact that this seems to be the only problem backup stinks!
Could this be the problem?
I continue to struggle with the issue of the exclusive reboots on NSMB. I don't think it's related to media or image, as I've tried several types/methods, all of which have worked on previous backups.
So, I'm wondering whether the problem has something to do with the system update, which brought my wii from 3.4u to 4.1u. I used the backup disk to perform the update, and maybe the update did not successfully take (even though the system said it did)? I am thinking this way because it is the only disk that causes the reboot, and upon doing more research, I see that this is sometimes a symptom in softmodded systems where certain newer files (cios?) have not been installed.
If I am correct about this, and I somehow borked the system install with the first NSMB, then how do I correct it (preferably without softmodding the system)? Is the only way to update the system online, which would bring me to the dreaded 4.2u?
I don't play any imports, so that really doesn't concern me much, but I'd hate to do that if I didn't have to. Would a system reformat solve the problem?
I hope my questions help others, and lead to a discussion on how to solve this reboot issue, if I'm on the right track. I'm not sure what else could be causing it. Thanks.
Update to 4.2u did nothing
I bit the bullet and updated to 4.2. NSMB bca patched still reboots the wii, but no other disk does. Could this really just be a bad wasabi dx?
Other things to try? Would a system format help? I'm pulling my hair out here trying to make this work.
I really don't want to have to go the softmod route -- I need plug/play for my kids.