Hacking Dios Mios Lite

[ShinyLatios]

just updated, deleting cache data, getting newest version... then going to try playing

 

[JoostinOnline]

I updated boot2 and now it's working!

Did you have bootmii as boot2, and if so have you re-installed it?

 

[IceIceBird]

since my BSOD : I updated my boot2(v2) to V4 with Dop-Mii, reinstalled bootmii with hackmii installer 0.8 >> Super Mario Sunshine (launched with Neogamma) works great
Zelda Wind Waker too (launched with wiiflow) !!
...

Now this is interesting...

Could it be that the whole blackscreen issue is purely with people (like me) who have a boot2 version lower than version 4?


EDIT: sorry...nevermind. Iceicebird already proves this wrong at the top of this page (boot2v4 + blackscreen).

I updated the boot2 to v4 but only tested the game Zelda Four Sword (PAL) with r34 because it worked before with r21 and I thought that this was the perfekt game to test with. AND that gives black screen but I could play retail games trough disc channel.
Now when I tested Luigis Mansion THAT ONE WORKED!

So I'am now also pretty convinst that the boot2 version is the bad guy for the "black screen" issue.
So.. is it just me who can't get Zelda for Sword working with r34?

Edit:
A quick guide to update your boot2 (warning! this "could" brick your wii)
Download boot2v4 from nus (as wad), rename wad file to "boot2v4.wad" and place it in SD/USB root
Use Dop-Mii to update boot2
*You have to reinstall BootMii as boot2 if you had it before.
Done

 

[Taleweaver]

Now this is interesting...

Could it be that the whole blackscreen issue is purely with people (like me) who have a boot2 version lower than version 4?


EDIT: sorry...nevermind. Iceicebird already proves this wrong at the top of this page (boot2v4 + blackscreen).

maybe you can give it a try...it takes a few seconds, and can fix the BSOD

for my part it worked great, and I'm happy with that.

Well...it took more than a few seconds (find out how to install it, get the v4 version from NUS, get past all the "are you really, really, REALLY sure you want to do this"-messages from dop-mii, update, reinstall bootmii), but you were right: it DOES fix things.

...and it recognizes my savegame things.


...and F-Zero is noticeably more smooth.



...and it spit out a disc error just as I was about to start the first race. D:



But still: I'm happy. It beats a black screen any day.

 

[ShinyLatios]

Installing boot2v4 fixed my issues! YAY!

 

[JoostinOnline]

Someone needs to answer my question about bootmii.

 

[Taleweaver]

Hmm...just tested this from neek2o: it gives the same result. (it uses the DML version from the real nand).


Kinda strange...I gotta find that post from this morning again...



EDIT: @Joostinonline: I had bootmii as boot2 installed. Updated from v3 -> v4. Immediately reinstalled bootmii as boot2.

 

[IceIceBird]

Someone needs to answer my question about bootmii.

Yes you have to reinstall bootmii as boot2 after you have updated boot2 to v4 (see my post above for a quick guide)

 

[fldc]

Now when the black screen problem has been identified, let's hope we get a fix for the read errors so we can actually play the games ;-)

 

[JoostinOnline]

Someone needs to answer my question about bootmii.

Yes you have to reinstall bootmii as boot2 after you have updated boot2 to v4 (see my post above for a quick guide)

I know how to install bootmii, I'm not an idiot. I think that bootmii is the culprit, not boot2. Someone with boot2v3 (or below) and an outdated installation of bootmii as boot2 should update bootmii and see if that fixes it.

 

[vpd]

Someone needs to answer my question about bootmii.

Yes you have to reinstall bootmii as boot2 after you have updated boot2 to v4 (see my post above for a quick guide)

I know how to install bootmii, I'm not an idiot. I think that bootmii is the culprit, not boot2. Someone with boot2v3 (or below) and an outdated installation of bootmii as boot2 should update bootmii and see if that fixes it.

I don't think it is that, i get the black screens, and i have boot2 v2 and the latest bootmii installed

 

[IceIceBird]

Someone needs to answer my question about bootmii.

Yes you have to reinstall bootmii as boot2 after you have updated boot2 to v4 (see my post above for a quick guide)

I know how to install bootmii, I'm not an idiot. I think that bootmii is the culprit, not boot2. Someone with boot2v3 (or below) and an outdated installation of bootmii as boot2 should update bootmii and see if that fixes it.

Easy answer to that, it doesn't!
(And just to be really clear, I had boot2v3 with latest bootmii before I updated my boot2 to v4 and reinstalled bootmii, and before that all games gave the "black screen" issue in the most recent revisions)

 

[JoostinOnline]

Someone needs to answer my question about bootmii.

Yes you have to reinstall bootmii as boot2 after you have updated boot2 to v4 (see my post above for a quick guide)

I know how to install bootmii, I'm not an idiot. I think that bootmii is the culprit, not boot2. Someone with boot2v3 (or below) and an outdated installation of bootmii as boot2 should update bootmii and see if that fixes it.

I don't think it is that, i get the black screens, and i have boot2 v2 and the latest bootmii installed

Too bad, it would have been a lot simpler. Bootmii as boot2 affects gamecube from retail discs, so I suspected it might affect DML. Thanks for answering me.

 

[dancemonkey]

So to make sure I get this right

Just click the Pack Wad no need to decrypt in NUS
Dop-Mii v16 (anyone know the difference between normal and Wiibrew Edition?)

Cheers.

 

[dsk]

I'd just like to send my thanks and appreciation to the DML team, since I'm finally able to play the masterpiece that is Wind Waker :3

 

[Bitbyte]

I'd hold off on updating Bootmii, it's pretty unsafe and might brick your Wii. Pretty sure this is gonna be fixed now that the culprit has been found.

*boot2, that is.

 

[IceIceBird]

I'd hold off on updating Bootmii, it's pretty unsafe and might brick your Wii. Pretty sure this is gonna be fixed now that the culprit has been found.

It ain't bootmii that need to be updated it's boot2, two different things. But your right, it could brick your wii if you get a power loss or something while your updating. But the update process take less then a sec. (and you will have to reinstall bootmii AFTER updating boot2 if you want that again)

 

[XFlak]

the only risk when updating boot2 is the risk of power loss. If you have a surge protector with UPS backup power the risk is virtually 0.

 

[themanuel]

So to make sure I get this right

Just click the Pack Wad no need to decrypt in NUS
Dop-Mii v16 (anyone know the difference between normal and Wiibrew Edition?)

Cheers.

Regarding your Dop-Mii question, Wiibrew Edition uses no unofficial IOS's to perform the operation. I would just use the regular version. Better yet, like others have suggested, I would not do anything at all until they figure out exactly what the problem is. There may not be a need to updated boot2 at all.

 

[Taleweaver]

I'd hold off on updating Boot2, it's pretty unsafe and might brick your Wii. Pretty sure this is gonna be fixed now that the culprit has been found.

*boot2, that is.

Pretty unsafe compared to what, exactly? Installing/updating the system menu or priiloader without having bootmii as boot2 is the same risk. The nintendo official updater: exactly the same. And I can list a whole bunch of other activities that people do with their wii on an almost daily basis that's just as risky, or even more so.

Dop-mii may treat it as though your wii might explode if you want it, but that's because 1) it was written when there was zero reasons to update, and 2) because otherwise people might forget to reinstall bootmii after the boot2 update.

I wouldn't mind seeing a fix, but if that is too much effort (or if there isn't enough code space to actually allow for multiple boot2 versions) then it wouldn't bother me if boot2v4 is a prerequisite.