Hacking Trucha Bug Restorer MOD

[erikk1]

So, thinking about this, would it not be a good idea to make a custom boot2v4 updater? So people can safely update to boot2v4 without risk of bricking? Then one could install official new firmware without risking a brick. I know there's no reason to update yet, but there might be in the future.

 

[XFlak]

I can't remember the details... but isn't there a reason why we prefer not "upgrading" to boot2v4, doesn't boot2v4 lead to problems downgrading IOSs (if we ever need 2)? Not 100% on this.

 

[erikk1]

I don't know. There's people who have done the official 4.2 update and are still able to do everything they want as far as I know. (with hackmii 0.6 and TBR mod)

Edit: I forgot to thank da_letter_a for this great mod

Well done!

 

[damysteryman]

I've updated the TBR MOD link with the source. First post has been updated with the new link.

 

[User423]

WOW, this works better than the original TBR 1.1 (for 4.2).

The Original gave me every time I tried to load 249 / 36 an Code Dump, this one NOT. Great!

 

[brento]

awesome work!

 

[ChokeD]

This is indeed a step forward. Good job.

 

[nathanderweise]

Do I need to do the following, if so, what for?

Dop-IOS MOD
cIOS installer for USB2
cIOS 222/223 installer v4
(optional) MIOSpatcher
(optional) Preloader or Startpatch

(This is from http://gbatemp.net/index.php?showtopic=171901)

Thanks

You don't need to do any of it. Here's what they are useful for:

Dop-IOS MOD - If you are a filthy pirate
cIOS installer for USB2 - I think this gives media support for MPlayer
cIOS 222/223 v4 - Very useful as an alternative IOS for USB Loaders
MIOSpatcher - If you are a filthy Gamecube pirate?
Preloader/Startpatch - Various tweaks to the system menu and alternative brick protection to BootMii

Dr. Clipper, thanks for your response, can I ask a question of you? I have a Wii LU65xxx v4.2 that I'd like to backup using the USB device but can't get to work for days now.
I've tried all the right steps and loads of web pages but no clear directions except how to install bannerbomb: http://bannerbomb.qoid.us/index.new.php
Everything else has failed me, installing Wad managers, CFG / cIOS / GX variations on USB loaders, etc.
Is there a site where I can get clear concise directions on how to install this?
From your response above it sounds as I'd like to have either cIOS222/223 v4 or cIOS installer for USB2.
Which files go where on my SD chip, what are the steps to install cIOS or GX USBLOADER, do I need WAD manager/files or Trucha?
I'm new to this and nothing has worked, please advise, thanks - N

 

[WiihackingNoobie]

The download link is broken..

 

[PPSainity]

I can't remember the details... but isn't there a reason why we prefer not "upgrading" to boot2v4, doesn't boot2v4 lead to problems downgrading IOSs (if we ever need 2)? Not 100% on this.
A little late, but from reading the HackMii Blog post on Boot2v4, I understood that upgrading to boot2v4 on an older Wii has no benefit nor no negative (aside from risking a brick during the update) as far as incompatible older IOS revisions go. The timing issues in loading older IOS revisions only exists with newer Wii's. Here are the relevant quotes from the blog post:
QUOTELet’s summarize the facts:

* Wiis recently began shipping with a new boot2v4, which is based on the same code present in the set of IOSes released last October
* Reloading IOS is often “broken” on new Wiis — especially when trying to reload to an “older” version of IOS (pre-October, taken from an older Wii)
* Launching PPC titles works just fine on new Wiis, even if that requires reloading to a different version of IOS (as happens when launching the Homebrew Channel
* The same versions of IOS work differently on older Wiis, and have none of the problems noted above. The only difference in the software loaded on these Wiis is in boot1 and boot2.
* The “leaked IOS16? seems to be exempt from these problems
...
A scenario begins to emerge:

1. Nintendo develops a new PCB design to reduce cost by simplifying circuitry in mid-2008; the resulting design has fewer parts but takes a few milliseconds longer for the power supply voltages to stabilize
2. The new hardware requires a more-tolerant IOS kernel, so BroadOn rebuilds boot2 and IOS for Nintendo do use in testing the new PCB design. These IOS versions are still backwards-compatible with C/RVL-CPU-01.
3. Nintendo releases the new IOSes as an update in late 2008, to quash the strncmp() bug (as well as /dev/flash access and ES_Identify()
4. Nintendo starts producing C/RVL-CPU-01 boards with the new IOSes on them. (boot2 is not updated, since there’s no benefit to doing so)
5. Nintendo eventually starts mass-producing C/RVL-CPU-20, which requires an updated boot2(v4) in order to work, along with the new IOS versions which are already well-tested by this point.
6. Consumers receive these new C/RVL-CPU-20 Wiis. Some of them try installing old versions of IOS on them and then running libogc code that uses them
7. libogc doesn’t know that it needs to wait longer for IOS to reload; depending on the timing, this can either cause a hang or it can cause IOS initialization to fail.

-[]D