Hacking USB Loader GX

[themanuel]

Sincerely, this community is lucky to have people like Cyan.

 

[OriginalHamster]

Cyan is nice guy, he always have enough patient to resolve users questions, he and the ULGX team are very solid with upates too =)

 

[d.d.d.]

Hey y'all~
Something I've tried and failed at many times but I want to really get it working now. I want to use Priiloader to auto-boot USBLGX.
I've tried to "install" that to Priiloader but I've been unsuccessful. Any tips to do that? Where to put the stuff on the SD card etc... Thanks!

 

[Cyan]

You need to install the forwarder dol, not the main program's dol.

in the all-in-one package, there's a wad/ folder, and inside there are the dols of the channel and the forwarder.

But I heard that it doesn't work correctly (it works, but not very good).
A user told that he used the Wiiflow forwarder instead (I don't know if he changed the code, or just put gx in the target path)


Do you have Bootmii launched from Boot2?
There's a program to replace Bootmii by a forwarder, Boot2 will launch the USBLoaderGX directly.

 

[d.d.d.]

No my boot2 was over-written by a game update long before I hacked my Wii unfortunately.
I'll try the forwarder for GX and see how it goes. Thanks~

Yeah I guess I was installing the wrong thing (instead of the forwarder). It works great now! Thanks again

 

[themanuel]

No my boot2 was over-written by a game update long before I hacked my Wii unfortunately.

Shouldn't you be able to still install bootmii as long as you have the vulnerable boot1, even if you did those updates?

 

[Etheboss]

From the wiibrew website:

The new boot1

Consoles made after some point in 2008 (no concrete date is known) have a new version of boot1 that patches the vulnerability which allows the console to boot a modified boot2. The Hackmii Installer will detect this situation and refuse to modify boot2(see more at Hackmii). Since boot1 cannot be updated, all consoles already manufactured before this update are safe. About 10% of the consoles that ran the BootMii Checker tool have the new boot1
Along with the System Menu 4.2 update, Nintendo released a new version of boot2 (boot2v4); there is nothing in boot2v4 that prevents BootMii from working, but it will overwrite an existing BootMii installation when it is installed.

The way i read this is that it should be possible to reinstall bootmii from the hackmii installer as long as you have a Wii with a vulnerable boot1.

 

[d.d.d.]

(Forgot which Wii I was running when I typed that.)
My launch J-Wii did let me install the modified boot2 but it kinda 1/2 way died from the GPU pixelation (I wonder if I send it in for repairs if it will still have the vulnerability or not).
My 2009 US-Wii (to replace the f'd up GPU J-Wii and what I currently use) would only let me install boot2 as IOS. So no matter what, I only get it as the IOS option because of the updated boot1 in manufacturing. No biggie~

 

[doveman]

I'm not sure to understand correctly.
I'll tell you what I think should be done.

First, you can keep the full channel installed, it will not conflict with other boot method. But if you don't want it anymore because of the outdated state, you can remove it.

Removing the UNLR Full channel:
1. use a WAD manager to install again the channel (as you said you have left data of the channel, it's best to install it fully again so the channel is correctly installed)
2. use a WAD manager again, but this time when you select the .wad file select "uninstall" instead of "install". it will delete the data on your NAND corresponding to that .wad file

installing the Forwarder Channel:
1. use a WAD manager to install the UNEO forwarder v5.1

both channels (full and forwarder) are available on the googlecode download page (as stand alone, or in the full all-in-one package). They can be installed together without problem (but you will have difficulty to know which channel is the full or the forwarder, unless you launch them, and remember the position on the system menu)

The Forwarder channel will launch the boot.dol located on SD or USB.
To exit games to the loader instead of the system menu, you can set this:
In USBLoaderGX settings > Loader settings > Return to > USBLoaderGX (UNEO)

Thanks Cyan. I thought I'd uninstalled the Full Channel which is why I was confused why it still seemed to be loading the old version rather than the one on the HDD/SD but I'll go through those steps again and hopefully clear it up.

I've got the Wii booting directly into USB Loader GX so I'm not sure where it looks for the files if the Full Channel is uninstalled. I'll change it to boot into the normal Wii menu and try launching the Forwarder from there though. It's been a while since I looked at the boot settings (whatever comes up when I hold reset whilst booting, it's been so long I can't even remember what that's called!) so it might become obvious once I have a look at them.

 

[doveman]

OK, I've managed to uninstall the Full Channel and install the Forwarder which is great.

The Boot settings I was talking about let me set it to boot to the System Menu or Installed File and I previously had it set to Installed File and that was USB Loader GX. I've changed it now to boot to the System Menu and load USB Loader GX from there via the Forwarder Channel. However, I also tried updating the Installed File and that gave me a list of what appeared to be the apps that were on my SD card, so I selected USB Loader GX from there to install the new version but now if I try to boot the Installed File it just gives me a white screen.

A separate issue, if I upgrade from d2x-v8 to v9 or v10-beta53-alt, USB Loader GX 1207mod1 (or the previous version I had installed) can't access my USB HDD. The HDD spins up and down repeatedly until the countdown times out and then USB Loader GX loads and says it can't find the HDD. Switching back to d2x-v8 and it works fine again.

 

[Cyan]

Do not install the USBLoaderGX's boot.dol into priiloader, instead you need to install the USBLoaderGX Forwarder's boot.dol (that file is located in the "all-in-one package" on the download page of the loader, inside the wad folder)

For the cIOS d2x, you can use v10, but just do not use the "alt" version if your drive don't like the alternative one.

 

[doveman]

Ah,

Do not install the USBLoaderGX's boot.dol into priiloader, instead you need to install the USBLoaderGX Forwarder's boot.dol (that file is located in the "all-in-one package" on the download page of the loader, inside the wad folder)

For the cIOS d2x, you can use v10, but just do not use the "alt" version if your drive don't like the alternative one.

Ah, that's where I was going wrong then, installing the wrong USBLoaderGX dol in priiloader

I'll try the non alt d2xv10, although I'm not sure it will work as v9 doesn't either. I only wanted to upgrade to the alt-v10 so that I could use both USB ports in WiiXplorer so if I can't use that there's probably not any reason to change from v8 for now.

 

[Cyan]

Hermes cIOS v4+ allows you to use both ports too. if Wiixplorer let you select the IOS, use one of hermes IOS.

else, you can always install both d2x v8 and v10 alt in different slots.

 

[doveman]

Hermes cIOS v4+ allows you to use both ports too. if Wiixplorer let you select the IOS, use one of hermes IOS.

else, you can always install both d2x v8 and v10 alt in different slots.

Ah cool, I'll give that a go.

I installed following this guide http://www.wiihacks.com/recommended-faqs-guides-tutorials-only/96886-guide-softmod-any-wii.html so it looks like Hermes v4 should be IOS223 or should I use IOS224?

IOS222 (rev 65535): Trucha Bug, ES Identify, NAND Access, USB 2.0 -hermes v4 base-38
IOS223 (rev 65535): Trucha Bug, ES Identify, NAND Access, USB 2.0 -hermes v4 base -37/38
IOS224 (rev 65535): Trucha Bug, NAND Access, USB 2.0 -hermes v5.1r base-57

So if I wanted to install v10-alt in a different slot, leaving v8 in 249/250 how would I do that? I presume the Wii would still boot using 249/250 so USB Loader GX would still find the HDD OK?

 

[crisash]

i have problems with this loader, everything loads fine, games, banners, options, but at time to play, the games never loads.
I think i have the correct configuration of ios (hermes, d2x, etc), because with a older version of cfg loader (and older gx version) I load every existing game.
with the new version of wiiflow and cfg loader its the same problem. all load, but at time to play, black screen.
just work the oldest version of each loader.
can anyone to know what happen?
thanks.

 

[Cyan]

So if I wanted to install v10-alt in a different slot, leaving v8 in 249/250 how would I do that? I presume the Wii would still boot using 249/250 so USB Loader GX would still find the HDD OK?

The Wii is booting with IOS80 (if you are on system menu 4.3)
USBLoaders are booting with the IOS slot you decide.

By using the cIOS d2x installer, you can select any slot from 200 to 255 (254=bootmii, 220-229 usually where Hermes cIOS are installed, other are free)

@crisash:
which version of the "old" loader is working, and which version of the new loader is not working?

 

[Shiranui-san]

Following with force video mode tests, I found something weird:

Rune Factory Frontier PAL:

Force Video Mode:

Disc Default --> 480i
System --> 480i (My Wii is configured as HDTV 480p)
PAL50 --> 480i (Should be 576i)
PAL60 --> 480i
NTSC --> 480p (Should be 480i)
PAL480p --> 480i (Should be 480p)
NTSC480p --> 480p

Then I tried forcing Mario Party 8, DBZ Tenkaichi 3 and Shinchan (which I had previously tested forcing them to PAL480p and were displayed in 480i) to NTSC480p but I got black screen.

 

[d.d.d.]

What version are you using?

 

[Shiranui-san]

Both r1207 mod1 and the .dol included in "USBLoader GX V3.0 AllinOnePackage IOS249".

 

[Cyan]

My games are correctly displayed in 480p when I select Disc default (and Wii set to 480p).
Maybe the game doesn't support some video mode, so it's using default mode for incompatible mode. (games like No More Heroes USA, and One Piece unlimited Adventure don't have PAL mode at all, I don't know how these games react when forcing to an unavailable mode (I matched my boot.dol to add them))

Could you test with v2.3 too?
I changed the video mode past 3.0, so I thought maybe I broke it, but if even 3.0 is not working then there's something wrong from an old revision.