velvet_nitemare
Member
Muchas Gracias.
-
Hey Guest. Check out your NeoGAF Wrapped 2025 results here!
GAF Wii Homebrew thread: Homebrew, emulators, USB disc installs! Easy tutorial!
- Thread starter radioheadrule83
- Start date
I am trying to get USB Loader to work but I am having a problem with rev13b.
My Wii is on 4.0, but when I follow the instructions from the GAF tutorial this seems to be the problem
" * If your Wii is 3.4 or less, use the default IOS chosen by the app
o If you tried this and the installer failed with a returned -2011 error, do the steps of the appropriate "I am on version 4.0 or greater" section above then retry this step.
* If your Wii is 4.0 or more and serial number is less than LU64, use IOS35, or IOS249 if you have it available and IOS35 didn't work."
I get a -2011 error. The tutorial states that I should only try to install the Hermes ones after I have installed IOS249, so can anybody help me with this?
Thanks!
EDIT: So, I tried the entire procedure from the start, downloading everything again from scratch, and it seems to have worked!!!!!! No idea what I did wrong.
I have to go out now (already late but had to get this working!) but later tonight I will try to get HOTD: Overkill loaded so I can play it without the stuttering. Hopefully my next post will be one of joy and triumph.
SECOND EDIT: Yeeeeees! It works flawlessly. So gooood! Totally worth the hassle.
My Wii is on 4.0, but when I follow the instructions from the GAF tutorial this seems to be the problem
" * If your Wii is 3.4 or less, use the default IOS chosen by the app
o If you tried this and the installer failed with a returned -2011 error, do the steps of the appropriate "I am on version 4.0 or greater" section above then retry this step.
* If your Wii is 4.0 or more and serial number is less than LU64, use IOS35, or IOS249 if you have it available and IOS35 didn't work."
I get a -2011 error. The tutorial states that I should only try to install the Hermes ones after I have installed IOS249, so can anybody help me with this?
Thanks!
EDIT: So, I tried the entire procedure from the start, downloading everything again from scratch, and it seems to have worked!!!!!! No idea what I did wrong.
I have to go out now (already late but had to get this working!) but later tonight I will try to get HOTD: Overkill loaded so I can play it without the stuttering. Hopefully my next post will be one of joy and triumph.
SECOND EDIT: Yeeeeees! It works flawlessly. So gooood! Totally worth the hassle.
Alright, I think I'm finally slamming my head against the wall here.
I guess it's my turn to ask for help.
I've been spending the past few nights figuring out how to totally hack my sister's new LU64 3.4U Wii. Sorry, I didn't use your tutorial Clipper, since I found so much conflicting info on Google, and your LU64 Fix 4.rar link is broken.
Either way, I managed to crack it and upgrade to 4.0U without running those steps; and instead used a combination of Bannerbomb, DOP-IOS v5, and Trucha Bug Restorer 1.0 to crack her Wii, install HBC, DVDX, Bootmii v2 (as IOS only, sadly), and Waninkoko's CIOS38 rev13a.
I also duplicated my own CFG USB Loader (v35 final) setup and tested things with my HDD and everything seems to be working almost perfectly. I'm stumbling over Hermes CIOSes, which I personally prefer over CIOS38 rev13. Unfortunately, on my sister's Wii, I can ONLY get rev13 working. Hermes' CIOSes seem to install just fine. On my Wii I use 36 as 202, 36 merged with 38 as 222, and 36 merged with 37 as 223, and have CFG USB Loader set up to run with IOS 223-mload by default.
On my sister's Wii, the exact same set up fails. CFG USB Loader hangs at bootup with a pure black screen. I don't even see CFGUSBL load up. If I switch the config.txt to IOS 249, it works great. If I run a game, it launches. If I try to get the same game running on 222 or 223 via the in-loader options, it hangs when trying to load the new CIOS.
Hermes' own ULoader (2.5b) also hangs at bootup if his CIOSes are installed on my sister's Wii. If I only have 249 installed, it at least gets to the main screen before it reports that it fails to find a USB device (probably because 222 and 223 aren't installed.) ULoader and CFG USB Loader (running off 223-mload) both work fine on my Wii, with the exact same setup.
Clearly something's borked on my sister's Wii, and it has something to do with IOS222 and IOS223. I've narrowed things down that much. I've tried uninstalling them and reinstalling them in different configurations again and again, but every time I try to use 222 or 223 (natively or from within CFG USB Loader) the Wii hangs.
Any ideas?
Edit - For what it's worth, everything else works. Yes, it's a LU64 Wii updated to 4.0, but WAD Manager, IOS Installers, DOP-IOS, TBR, HBB, various emulators, Any Title Deleter, BootMii as IOS, and every other bit of homebrew I throw at it all work fine. But not a loader trying to run as IOS222 or IOS223.
I guess it's my turn to ask for help.
I've been spending the past few nights figuring out how to totally hack my sister's new LU64 3.4U Wii. Sorry, I didn't use your tutorial Clipper, since I found so much conflicting info on Google, and your LU64 Fix 4.rar link is broken.
Either way, I managed to crack it and upgrade to 4.0U without running those steps; and instead used a combination of Bannerbomb, DOP-IOS v5, and Trucha Bug Restorer 1.0 to crack her Wii, install HBC, DVDX, Bootmii v2 (as IOS only, sadly), and Waninkoko's CIOS38 rev13a.
I also duplicated my own CFG USB Loader (v35 final) setup and tested things with my HDD and everything seems to be working almost perfectly. I'm stumbling over Hermes CIOSes, which I personally prefer over CIOS38 rev13. Unfortunately, on my sister's Wii, I can ONLY get rev13 working. Hermes' CIOSes seem to install just fine. On my Wii I use 36 as 202, 36 merged with 38 as 222, and 36 merged with 37 as 223, and have CFG USB Loader set up to run with IOS 223-mload by default.
On my sister's Wii, the exact same set up fails. CFG USB Loader hangs at bootup with a pure black screen. I don't even see CFGUSBL load up. If I switch the config.txt to IOS 249, it works great. If I run a game, it launches. If I try to get the same game running on 222 or 223 via the in-loader options, it hangs when trying to load the new CIOS.
Hermes' own ULoader (2.5b) also hangs at bootup if his CIOSes are installed on my sister's Wii. If I only have 249 installed, it at least gets to the main screen before it reports that it fails to find a USB device (probably because 222 and 223 aren't installed.) ULoader and CFG USB Loader (running off 223-mload) both work fine on my Wii, with the exact same setup.
Clearly something's borked on my sister's Wii, and it has something to do with IOS222 and IOS223. I've narrowed things down that much. I've tried uninstalling them and reinstalling them in different configurations again and again, but every time I try to use 222 or 223 (natively or from within CFG USB Loader) the Wii hangs.
Any ideas?
Edit - For what it's worth, everything else works. Yes, it's a LU64 Wii updated to 4.0, but WAD Manager, IOS Installers, DOP-IOS, TBR, HBB, various emulators, Any Title Deleter, BootMii as IOS, and every other bit of homebrew I throw at it all work fine. But not a loader trying to run as IOS222 or IOS223.
Mejilan said:
You could try installing the ehcmodule.elf file with Configurable. This apparently helps stability of the Hermes' IOSes. Get it from the uLoader package and then install it as sd:/usb-loader/ehcmodule.elf. Configurable will find it and do the rest.
As for the LU64 fix, yeah, it seems to have disappeared sometime over the last few days. I'll look for another source of the file. Somebody must have mirrored it somewhere. Alternatively, do you have a nice set of instructions for the method you used that you could add or show me to fix up that section?
Edit: Oh, now I know what you mean by TBR. That makes things a lot easier. I think I'll use it to replace both 4.0 methods.
I don't really have a nice set of instructions, since I've kind of been cobbling together applications and procedures on my own, mostly via various readmes. I'm sure some of what I did was redundant (DOP-IOS v5 and Trucha Bug Restorer v1.0 both seem to do more or less the same thing, with DOP-IOS perhaps allowing for more). Additionally, I'm not exactly sure which of these did the trick from a LU64 standpoint.
First time working on a LU64 Wii, and all that.
Thanks for the suggestion. I'll see if that does the trick. I'm don't think it will, since I can't even get Hermes' uloader working, which tells me that there's got to be something wrong with CIOS222/223, despite the installer insisting that it all went well.
First time working on a LU64 Wii, and all that.
Thanks for the suggestion. I'll see if that does the trick. I'm don't think it will, since I can't even get Hermes' uloader working, which tells me that there's got to be something wrong with CIOS222/223, despite the installer insisting that it all went well.
OK, GWHT has been updated to a new, simpler install method for all 4.0 Wiis. If anybody tries it out, please let me know of any problems. Thanks.
That's strange. You did use the new 222/223 installer that installs via IOS249, right? Wait, have you tried running Configurable off the SD card and not using the forwarder? Then again, I guess that's the only way to get uLoader going, so it's probably useless.Mejilan said:
Ok, after NAL admitted they were not going to release ExciteBots in Australia, I've finally decided to install the HBC and start playing imports.
This will be the first time I've ever done this to any console so I'm a bit nervous. I've got the GAF Homebrew Wiki and I'll follow that, but first, can anyone answer these questions:
1. My Wii is 4.0E. All I want to do is install Gecko OS to run US imports on my machine. This should be no problem, following the tutorial, right?
2. The Wii doesn't have any problems reading Micro SD Cards, right? (in an adapter, obviously)
3. If I'm just installing Gecko OS and the HBC, is there a threat, no matter how small, of my Wii bricking?
This will be the first time I've ever done this to any console so I'm a bit nervous. I've got the GAF Homebrew Wiki and I'll follow that, but first, can anyone answer these questions:
1. My Wii is 4.0E. All I want to do is install Gecko OS to run US imports on my machine. This should be no problem, following the tutorial, right?
2. The Wii doesn't have any problems reading Micro SD Cards, right? (in an adapter, obviously)
3. If I'm just installing Gecko OS and the HBC, is there a threat, no matter how small, of my Wii bricking?
Nemesis_
Member
I can only answer these.
2.) But yeah, I use a 2GB microSD in an SD adapter. Works perfectly!
3.) There's always going to be a threat. You can install BootMii or something and that "saves" the "unbricked" Wii "OS" or something. I didn't use it and I got by fine, but suppose that's what you'll need. (Wait, I just realised, you'd have to install HBC to install it anyway >_>). But to answer your question, there is always going to be a threat but these days I am fairly certain it's minimal.
legend166 said:
1. You'll need to do the Bannerbomb method, HBC should install GeckoOS all by itself (at least mine did)
2. It's fine
3. Yes there is a threat, but if it happens there is multiple ways of recovery now. It's probably won't happen though, I've installed the HBC on at least 5 Wii's flawlessly using the other TP Hack and Bannerbomb methods.
Yeah, the only thing you are actually installing is the HBC and that has extremely small chance of bricking, less chance than installing BootMii even. Gecko OS will remain on your SD card and is never actually installed, so don't worry.
Welcome to the club, legend166. All of us Aussies will be importing soon enough
Welcome to the club, legend166. All of us Aussies will be importing soon enough
Just noticed that part, which is wrong. An old version of Gecko OS used to be included on the installation page for HBC as a resource, but it is now very out of date and no longer included. GWHT gives all the instructions to get the latest version (both via Homebrew Browser or directly copying to the SD card).VOOK said:
It was an option as part of the install procedure listed there (they had a package of several apps). Since BootMii, they no longer provide the apps and instead link to WiiBrew.VOOK said:
And yes, I'm a true blue Aussie, born and bred. From the land that lacks an R classification, wants to block foreign games sites that sell said games, and where format shifting of anything except music is in violation of copyright law... oh crap.
Ok, so I installed the HBC and Gecko OS. It's all fine, my Wii is working.
Since I don't have an NTSC Wii game with me, I decided to test out my NTSC copy of Ikaruga. It loads, gets me into the game. I go to start, and it says "An error has occured, please restart the GameCube" D:
Since I don't have an NTSC Wii game with me, I decided to test out my NTSC copy of Ikaruga. It loads, gets me into the game. I go to start, and it says "An error has occured, please restart the GameCube" D:
Clipper, I just wanted to thank you for the tutorial - I used it as a lurker and couldn't say thanks then! :lol
I do have a question, though: how "safe" is it to use a USB Loader? For example, if I play Mario Kart Wii online, and Nintendo knows when I did that, can they check my play logs and see "Homebrew Channel" listed instead of Mario Kart Wii? Doesn't some data get sent to Nintendo when using the Wii Shop Channel and the Nintendo Channel?
Is that something they could ban me from online for?
Edit: I know updating right away is generally not recommended, but I just got a notification that 4.1 (the Wii Sports Resort fix) is now available. Since 4.1 is already out in Japan, does anyone know if updating breaks HBC?
I do have a question, though: how "safe" is it to use a USB Loader? For example, if I play Mario Kart Wii online, and Nintendo knows when I did that, can they check my play logs and see "Homebrew Channel" listed instead of Mario Kart Wii? Doesn't some data get sent to Nintendo when using the Wii Shop Channel and the Nintendo Channel?
Is that something they could ban me from online for?
Edit: I know updating right away is generally not recommended, but I just got a notification that 4.1 (the Wii Sports Resort fix) is now available. Since 4.1 is already out in Japan, does anyone know if updating breaks HBC?
I just saw my blinking Wii notifying me of a new firmware update. 4.1 is just the patch for Wii Sports Resort, right? it doesn't do anything else to the console? (I don't have HBC but I'm still wary of firmware updates... in other news, Vista Service Pack 2 is still sitting in my update queue.)
So that's why my Wii was blinking this morning...
For now: don't update. People have been playing Japanese Wii Sports just fine without updating, so it should be safe to play without updating now. Just play it once with Gecko OS and then use Gecko OS or USB Loader to play your game from then on.
If you have updated to 4.1, do not despair just yet. The new USB Loader method I have on the site is confirmed working with Japanese 4.1 already.
Edit: OK, it seems the only thing that might be broken is Preloader. If Preloader is important to you, maybe wait ( I think you can reinstall later, not 100% sure yet). For the rest of us, I'd say that if you're on 4.0, update. Otherwise stay where you are, unless you want the 4.0 stuff.
For now: don't update. People have been playing Japanese Wii Sports just fine without updating, so it should be safe to play without updating now. Just play it once with Gecko OS and then use Gecko OS or USB Loader to play your game from then on.
If you have updated to 4.1, do not despair just yet. The new USB Loader method I have on the site is confirmed working with Japanese 4.1 already.
Edit: OK, it seems the only thing that might be broken is Preloader. If Preloader is important to you, maybe wait ( I think you can reinstall later, not 100% sure yet). For the rest of us, I'd say that if you're on 4.0, update. Otherwise stay where you are, unless you want the 4.0 stuff.
You're welcome. On the MK Wii online thing, I have no clue. Nobody seems to have been banned for playing online with USB Loader so far, but people have been banned for cheating online. USB Loader might be detectable on Nintendo's servers due to differences in load times, so I don't risk it, personally. MK Wii's the only thing I play online, so I just leave the disc in the system and play it normally, while playing the rest of my games off USB.lutherjw said:
Try fiddling with the force video settings. Also, if you have cables that support 480p for your Wii, try holding B as the game starts and tell it to use progressive scan.legend166 said:
Clipper said:
The thing is, it loads up the intro videos and the menu just fine. I even got into a practice mode quickly, but then it gave me an error. I imagine if it was a video setting issue it wouldn't load up properly at all, but rather give me flickering, bad colour or what have you.
It's possible the menu can handle running at 50Hz just fine, but the actual gameplay screen requires a fixed refresh rate of 60Hz. Shmups are usually very highly tied to framerate to work properly.legend166 said:
Oh, I also meant to add earlier that you should also try setting your Wii to 480i instead of 576i if you can't handle 480p.
wackojackosnose
Member
legend166 said:
What region system do you have? I'm on a PAL Wii and have the same problem. I've tried both Ikaruga and Naruto 4 (both JAP NTSC) and they run until the intro or so and then I get what I presume is an error message. It's quite annoying because playing my import Gamecube games is the main reason why I modded my Wii.
Howdy Clipper,
Great work on keeping the guide updated
I just installed HBC on a 3.1J Wii and then ran anyregion changer and turned his Jap Wii into a USA Wii with no problems.
Then I downloaded the latest update (4.1) from online.
After that I tried your updated guide for installing a USB loader and used the Trucha Bug Restorer and then installed CIOS 13 as described in the guide. Everything worked without a hitch.
Thanks from a fellow Aussie
Great work on keeping the guide updated
I just installed HBC on a 3.1J Wii and then ran anyregion changer and turned his Jap Wii into a USA Wii with no problems.
Then I downloaded the latest update (4.1) from online.
After that I tried your updated guide for installing a USB loader and used the Trucha Bug Restorer and then installed CIOS 13 as described in the guide. Everything worked without a hitch.
Thanks from a fellow Aussie
criesofthepast
Member
Thank you Clipper for the awesome guide and to everyone else in this thread providing great info. Have had a Wii since november and barely use it and finally decided to install the homebrew channel. Such a simple process and really enjoying what the homebrew channel/browser has to offer so far.
MrPing1000
Member
So I am wanting to import Tiger Woods 2010 from the USA because quite frankly EA can go to hell for making the PAL version 50hz only.
Has anyone successfully got it running on a PAL system. I've heard that people are having difficulty. Hmm.
Has anyone successfully got it running on a PAL system. I've heard that people are having difficulty. Hmm.
Dash Kappei
Not actually that important
Is there any chance to do "snapshot" saves for Wii games, maybe through the USBLoader+Ocarina or something like that?
I'll explain myself better:
I'm playing (and loving so far) De Blob, but the fuckers ruined the game with hours long chapters where you can't save nor have auto'saving checkpoints in the levels, so you either finish your level tasks in one sitting or you're screwed.
I barely game 4 hours or so throughout the week, so I can't spend 1hour+ every goddamn time I want to play De Blob, so basically I'm stuck with a game that I can't play.
Any ideas/fixes, guys?
I'll explain myself better:
I'm playing (and loving so far) De Blob, but the fuckers ruined the game with hours long chapters where you can't save nor have auto'saving checkpoints in the levels, so you either finish your level tasks in one sitting or you're screwed.
I barely game 4 hours or so throughout the week, so I can't spend 1hour+ every goddamn time I want to play De Blob, so basically I'm stuck with a game that I can't play.
Any ideas/fixes, guys?
Nothing homebrew-wise is going to provide state saves until we are a generation or two in the future (besides playing the games on that PC Wii emulator).Dash Kappei said:
There is one somewhat drastic solution: Pause the game and leave the Wii on until the next time you play... It means you can't play any other games on the Wii, but it does allow you to split up the action a bit.
Dash Kappei
Not actually that important
Firestorm said:
YES! Ok, fantastic, how do I do that?
Clipper said:
Oh snap
Wow, that's genius!
...:lol
Just kiddin' Clip, thanks anyway for the reply
MidnightScott
Banned
Help me GAF
I just got a copy of Another Code R PAL. I tried to play it on my NTSC Wii using Gecko OS in Homebrew Channel. Well the game refuses to play. I have a feeling this is because I updated my Wii to 4.1 because I heard nothing was really affected by it.
Once I load the game, I get a blue screen saying "An error has occured. Please eject the game disk, and read the Wii Operation Manual"
EDIT: Okay, it seems the issue is only with Another Code R. I just tried my PAL copy of Disaster: Day of Crisis and it works fine...I have an older version of Gecko OS, would that be the reason?
EDIT 2: Nevermind. I got the latest version of Gecko OS. However, I kept selecting Force NTSC like I did with Disaster: Day of Crisis...and the game was slow and the colors were horrid. Then I chose PAL60 and it was the same way. I chose PAL50 and voila, the game works perfectly now =D
I just got a copy of Another Code R PAL. I tried to play it on my NTSC Wii using Gecko OS in Homebrew Channel. Well the game refuses to play. I have a feeling this is because I updated my Wii to 4.1 because I heard nothing was really affected by it.
Once I load the game, I get a blue screen saying "An error has occured. Please eject the game disk, and read the Wii Operation Manual"
EDIT: Okay, it seems the issue is only with Another Code R. I just tried my PAL copy of Disaster: Day of Crisis and it works fine...I have an older version of Gecko OS, would that be the reason?
EDIT 2: Nevermind. I got the latest version of Gecko OS. However, I kept selecting Force NTSC like I did with Disaster: Day of Crisis...and the game was slow and the colors were horrid. Then I chose PAL60 and it was the same way. I chose PAL50 and voila, the game works perfectly now =D
If I have the Backup Launcher Channel on my Wii and I'd like to get rid of it, how can I go about doing that when I no longer have the WAD of it? The WAD Manager needs it right?
I've tried to find the version (0.3) but all I see is 1.1 on websites.
Is there a way to uninstall the channels (tickets) without the WADs?
**additionally, is there a simple way to completely overwrite all the work done to install HBC and channels and bring the wii back to factory settings as if the user never even installed anything? For example, some flash that'll reset everything back? Just curious.
I've tried to find the version (0.3) but all I see is 1.1 on websites.
Is there a way to uninstall the channels (tickets) without the WADs?
**additionally, is there a simple way to completely overwrite all the work done to install HBC and channels and bring the wii back to factory settings as if the user never even installed anything? For example, some flash that'll reset everything back? Just curious.
AnyTitleDeleter should get rid of that nasty, (and hopefully) accidentally-installed piracy tool from your Wii quite nicely. I wouldn't use it if you have an LU64 Wii, but given you probably had BUL installed by the Yafaze tutorial, you probably don't have one. In any case, be very careful with the tool and only delete stuff you know is safe to delete.danootz said:
As for reverting the Wii, a system format will undo a lot of the stuff. There'll still be some traces lying around, though. The only real way to remove everything is to have installed BootMii first and made a backup before installing anything else. Then you only have to restore and use the delete option in its installer (which may or may not totally remove it, we don't really know). It's obviously too late for that in your case, though.
Thanks to all the info here, i've miraculously :lol put hb on my system as well as getting coverfloader and usbloader to work...i'm really not sure how it started working as i was running into a few errors that had me stumped
at any rate, problem. i can't seem to play another game after i exit to the menu. it just crashes. from what im reading,it's a bug in cIOS13b which is the version i guess i have since i have the same problem.
Which version do you guys recommend? and can anyone describe the install process of the new file? again, miraculous in describing how i got it to work in the first place is a huge understatement.
Thanks again all, especially you Clipper; saw you on some other boards with just fantastic advice.
at any rate, problem. i can't seem to play another game after i exit to the menu. it just crashes. from what im reading,it's a bug in cIOS13b which is the version i guess i have since i have the same problem.
Which version do you guys recommend? and can anyone describe the install process of the new file? again, miraculous in describing how i got it to work in the first place is a huge understatement.
Thanks again all, especially you Clipper; saw you on some other boards with just fantastic advice.
14 will apparently be out sometime before the end of July, might be best waiting for that. My current preference goes with 13 (not b). It has the best compatibility and the only problem is the reset bug, but it is easy to work around it by choosing Reset instead of Wii Menu on the home screen. And for installing it, the GWHT tells you how.moowear said:
Dash Kappei
Not actually that important
Mejilan said:The only thing 4.1 broke for me is Preloader.
Technically, you CAN reinstall it, and it'll work again.
But since there are now 4.1 hacks yet, it's kind of gimped.
I have Preloader installed but no 4.1 yet, what will happen when I updated?
It gets unistalled by the update or something else?
I'd hate to have a non-working app installed in my system, so I'd prefer to get rid of it... but I've never tried to uninstall Preloader.
Apparently, Preloader installs itself over IOS60, and 4.1 overwrites IOS60, so the update essentially uninstalls Preloader for you.Dash Kappei said:
Edit: actually, scratch that. It patches IOS60 so that it can do stuff, but I don't think it can patch the new one properly until people make some new hacks or something. It's probably best to wait for Mejilan or somebody else who actually uses Preloader for further info
.Upgrading or downgrading your System Menu will always wipe Preloader. This has been true for quite some time, and is basically the only way to fully get rid of it.
Upgrading from 4.0 to 4.1, expectedly, will wipe Preloader 0.29.
SysMenu 4.1, like SysMenu 4.0 before it, uses IOS60, so the current Preloader 0.29 installer can install to SysMenu 4.1 exactly the same way it installed to SysMenu 4.0.
That'll restore normal functionality. But arguably the biggest benefit to using Preloader was to implement hacks, which are and have always been SysMenu (not IOS)-dependent. As of 2 days ago, when I upgraded to 4.1 and reinstalled Preloader 0.29, no 4.1-specific hacks had yet been developed. I played around with the 4.0 hacks and eventually got them to show up for 4.1, but the memory addresses changed, so the hacks don't actually work. Or, at worst, break things. I have them all disabled for the moment.
Long story short: Preloader 0.29 works on 4.1, but must be reinstalled. Installation works exactly like before, and no new installer is required. New 4.1 hacks need to be developed before the best of Preloader's functionality will be restored on 4.1.
Upgrading from 4.0 to 4.1, expectedly, will wipe Preloader 0.29.
SysMenu 4.1, like SysMenu 4.0 before it, uses IOS60, so the current Preloader 0.29 installer can install to SysMenu 4.1 exactly the same way it installed to SysMenu 4.0.
That'll restore normal functionality. But arguably the biggest benefit to using Preloader was to implement hacks, which are and have always been SysMenu (not IOS)-dependent. As of 2 days ago, when I upgraded to 4.1 and reinstalled Preloader 0.29, no 4.1-specific hacks had yet been developed. I played around with the 4.0 hacks and eventually got them to show up for 4.1, but the memory addresses changed, so the hacks don't actually work. Or, at worst, break things. I have them all disabled for the moment.
Long story short: Preloader 0.29 works on 4.1, but must be reinstalled. Installation works exactly like before, and no new installer is required. New 4.1 hacks need to be developed before the best of Preloader's functionality will be restored on 4.1.