Hacking Problems with softmodded wii and Zelda SS

[FDoodleDoo]

I'll give a quick overview of my situation:

1) I have a retail copy of LoZ:SS

2) Problem: blackscreen when I leave the first building (the double doors to go outside once you get out of Link's bedroom)

3) Restored the wii to its former state (first backup you do when you softmod)

4) Upgraded to 4.3 via Nintendo. Still doesn't work. same blackscreen.

5) Softmodded again via Softmod ANY wii guide. Installed cios 249[56]d2x v6 and 250[57]d2x v6. Still same blackscreen.
6) Formatted my HD to Fat32 and created a wbfs image from my Collector's Edition retail disc using USBLoaderGX

7) Loaded the game with USBLoaderGX with ios 248, with ios 249, with ios 250, and with ios 222 blocking ios reload. It all failed at the same spot : the moment I leave the first building to get outside.

8) I tried loading with Wiiflow. Failed too.

9) Converted my retail version to an iso and then to wbfs using Wii Backup Manager Build 76. Transfered on my Fat32 USB Drive and loaded with Cfg Usb Loader. Tried with ios 248 and ios 249.
My disc is working. I went to my friend's house tonight and I saw for the first time what was beyond those damn double doors....

Can someone help me? Is the only solution left to virginize my wii?
I think the problem comes from the first time I softmodded, since I had bugs sometimes in other games too. Those were randoms though. Like Donkey Kong, it was suddenly freezing with a buzz sound.
But this is the first time with Zelda where it always freezes at the same spot.

Here is my syscheck report:

Spoiler

sysCheck v2.1.0b14 by Double_A and R2-D2199
...runs on IOS58 (rev 6176).


Region: NTSC-U
System Menu 4.0/4.1U (v54449)
Priilaoder installed
The drive supports DVDs
Homebrew Channel 1.0.8 running on IOS58
Hollywood v0x11
Console ID: xxxxxxxx
Boot2 v4
Found 85 titles.
Found 51 IOS on this console. 5 of them are stub.


IOS4 (rev 65280): Stub
IOS9 (rev 54321): Trucha Bug
IOS10 (rev 768): Stub
IOS11 (rev 54321): Trucha Bug
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 54321): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS17 (rev 1032): No Patches
IOS20 (rev 54321): Trucha Bug
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 54321): Trucha Bug
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 54321): Trucha Bug, ES Identify, NAND Access
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 54321): Trucha Bug
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 54321): Trucha Bug
IOS61 (rev 5662): No Patches
IOS70 (rev 54321): Trucha Bug
IOS80 (rev 54321): Trucha Bug
IOS90 (rev 54321): Trucha Bug
IOS202[60] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS222[38] (rev 65535, Info: hermes-v4.0): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223[38] (rev 65535, Info: hermes-v4.0): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS224[57] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS236 (rev 54321): Trucha Bug, ES Identify, NAND Access
IOS247[37] (rev 21006, Info: d2x-v6): Trucha Bug, NAND Access, USB 2.0
IOS248[56] (rev 21006, Info: d2x-v6): Trucha Bug, NAND Access, USB 2.0
IOS249[56] (rev 21, Info: d2x-v6): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 21, Info: d2x-v6): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v6
MIOS v65535


Report generated on 2011/11/22.

Thank you in advance!!

 

[Lucif3r]

Hm, while I cant see anything wrong with the syscheck, you could try letting ModMii scan it for you and see if it wants you to install any new ios.

However, d2x base 56 is really all thats needed to play. So your issue seems quite weird. Im afraid I cant think of any solution for your issue.

 

[FDoodleDoo]

Thank you for the quick reply Lucif3r!

I got told that there is a dupe in my cios 248 and 249. Think it might change something to solve this?

Or, if really no solutions are found... should I virginize? Or does even virginizing a wii leave a trace? (I'm quite surprised it didn't work the first time when I upgraded officially to 4.3.....)

 

[The_Dragons_Mast]

They way I see it your wii laser might be dieing so can't read some part of the disc & that lead to the backup you made using usbloader having the same problem . Try going to your friend house & dumping your disc using his wii & see if it works .

As for virganizing doing that official system update is the closest thing to virganizing your wii can get & if that didn't work then its useless .

EDIT: You can't dump a wii disc using the pc unless you have one of very old few lg drives so its normal that the iso you made didn't work .

 

[FDoodleDoo]

Actually, I thought of that also, and the wii of my friend is factory, so what I did is I downloaded an iso version to check if my image was the problem. That is my step 9) actually. I modified the version because on one website they got really annoyed about the fact that I downloaded the iso, (even though I bought the retail...)

Same blackscreen with this iso version... -_-'

 

[bjorno]

Bad rips/bad laser? Also, don't just update and downgrade and mess with virginizing, you might end up with a brick. Be careful!
Updating does not help at all since it doesn't add anything new, only new checks to prevent homebrews.
You can play any game on any firmware as long as you update your IOS.

 

[Lucif3r]

Or, if really no solutions are found... should I virginize? Or does even virginizing a wii leave a trace? (I'm quite surprised it didn't work the first time when I upgraded officially to 4.3.....)

Virginizing a Wii isnt quite that simple, and theres also a big chance of bricking it if you do something wrong. So I'd avoid doing that if I were you.

 

[The_Dragons_Mast]

Well in that case either you where unlucky & downloaded a bad rip or something wrong with your ios . Try using modmii to download the recommended cios & reinstalling them .

 

[FDoodleDoo]

ok, I'll try that tonight (modmii). I'll keep you up to date with that as soon as I can.

two more things:
1) the iso I got, the comments were all saying thank you it's working!
2) when you say "dump", is it actually a synonym to burn or create an image? I'm newb + french, soo... lol! my situation doesn't help at all! ;-)
While searching for the definition of dump, I found the "dump BCA" thing, which I remember I encountered while trying to create an image using usbloader. And when I clicked on the option dumpBCA, I think, from what I remember, the BCA code it read was something like 000000.
Is it normal only zeros?

Thank you all guys for your help, it's so appreciated!

 

[The_Dragons_Mast]

Dumping is creating the image & if they say it works then I guess its not the iso .

 

[FDoodleDoo]

Just tried again after updating with ModMii. Asked ModMii to update my wii from 4.1 to 4.1. Reinstalled 45 files, including an usb loader.

Still same problem....

Any ideas?

 

[FDoodleDoo]

OK, I really feel I am in this zone where there's just something weird and no one can understand why this is happening because it is completely irrational.....

After hours wasted trying to fix my problem, I really think my only solution left is to send it for repair.....

If I follow this guide to virginize my wii http://www.wiihacks.com/tutorial-archives/48787-completely-virginize-any-4-2-softmodded-wii.html

1st: I would update my wii from 4.1 to 4.2 using modmii, it's that simple?

2nd: Would I be in shit sending it to Nintendo after, or no one will be able to tell I softmodded it? Is it safe to send it to Nintendo once virginized or there are still some traces left of softmodding?