Hacking Trucha Bug Restorer MOD

[zektor]

Wait, when you do a NAND backup, aren't you backing up boot2 as well? Thus, a restore to a clean 4.1 Wii would be installing a previous version of BootMii, right?

No. Boot2 is not part of the backed up nand portion.

Posts merged

To recap:

Virgin 4.1U system with v0.6 bootmii installed as boot2, updated officially to 4.2U. Bootmii in boot2 NOT deleted.

Virgin 4.1U system with v0.5 bootmii installed as boot2, updated officially to 4.2U. Bootmii in boot2 WAS deleted.

 

[zektor]

For some reason, the Nintendo update on the v0.6 bootmii boot2 did NOT overwrite it. I know TT said nothing had changed, but perhaps they did modify the version number of boot2? If it works the same as IOS installs (version number wise), it would make sense as to why the official updater did not overwrite boot2.

Which brings another idea. Can boot2 version numbers be "maxed out" to avoid future overwrites by Nintendo installers? I guess only TT can answer that one

 

[Dr. Clipper]

Wait, when you do a NAND backup, aren't you backing up boot2 as well? Thus, a restore to a clean 4.1 Wii would be installing a previous version of BootMii, right?

No. Boot2 is not part of the backed up nand portion.

Posts merged

To recap:

Virgin 4.1U system with v0.6 bootmii installed as boot2, updated officially to 4.2U. Bootmii in boot2 NOT deleted.

Virgin 4.1U system with v0.5 bootmii installed as boot2, updated officially to 4.2U. Bootmii in boot2 WAS deleted.

We probably also need to know whether these Wiis had been updated before and then turned back into virgins. BootMii patches itself into whatever boot2 is installed on the Wii, and perhaps the new one IS different to boot2v4 in some way (call it boot2v5). That would explain everything if the first system in your test was a fake virgin and the second system was a real one.

 

[xzxero]

Wait, when you do a NAND backup, aren't you backing up boot2 as well? Thus, a restore to a clean 4.1 Wii would be installing a previous version of BootMii, right?

No. Boot2 is not part of the backed up nand portion.

Posts merged

To recap:

Virgin 4.1U system with v0.6 bootmii installed as boot2, updated officially to 4.2U. Bootmii in boot2 NOT deleted.

Virgin 4.1U system with v0.5 bootmii installed as boot2, updated officially to 4.2U. Bootmii in boot2 WAS deleted.

We probably also need to know whether these Wiis had been updated before and then turned back into virgins. BootMii patches itself into whatever boot2 is installed on the Wii, and perhaps the new one IS different to boot2v4 in some way (call it boot2v5). That would explain everything if the first system in your test was a fake virgin and the second system was a real one.

aahaha!
fake virgin.
caught up!

 

[zektor]

We probably also need to know whether these Wiis had been updated before and then turned back into virgins. BootMii patches itself into whatever boot2 is installed on the Wii, and perhaps the new one IS different to boot2v4 in some way (call it boot2v5). That would explain everything if the first system in your test was a fake virgin and the second system was a real one.

Well, all I do know is that I have nand backups for both systems in which they were officially updated to v4.1U (when that was available), then formatted, then immediately backed up. Both are identical in that fashion. Oh well, it's late. I'll ponder more tomorrow

EDIT: Before I go off to bed, I have to double thank da_letter_a for an incredible job. Alot of great things have surfaced since the v4.2 update (some I have been a part of) and I have to honestly say that this really takes the cake. Trucha bug back in any virgin 4.2....how can you beat that

Thanks once again pal!

 

[Jacobeian]

Strange. I just tested another Wii that had the v0.5 bootmii installed as boot2. I performed the v4.2U official update on this one, and it DID delete bootmii from boot2. I know TT said that nothing changed bootmii wise in the 0.6 update, but what would be the reason for this? I am baffled....

Simple: it depends on the boot2 version which was installed in these Wii before updating, if you already had boot2 v4 when installing bootmii, it won't be updated (the official update only do necessary updates) and remain untouched so any previously installed bootmii will stay...

 

[illinialex24]

Strange. I just tested another Wii that had the v0.5 bootmii installed as boot2. I performed the v4.2U official update on this one, and it DID delete bootmii from boot2. I know TT said that nothing changed bootmii wise in the 0.6 update, but what would be the reason for this? I am baffled....

Simple: it depends on the boot2 version which was installed in these Wii before updating, if you already had boot2 v4 when installing bootmii, it won't be updated (the official update only do necessary updates) and remain untouched so any previously installed bootmii will stay...

I've literally been saying this for two pages lol. I hope they finally listen.

 

[Dr. Clipper]

I've literally been saying this for two pages lol. I hope they finally listen.

If either of them were originally boot2v4, then you wouldn't be able to install BootMii as boot2. This is what was confusing me, but once I was told that boot2 isn't part of the NAND backup, it made sense.

 

[Jacobeian]

lol... btw, there isn't any new boot2 (only v2, v3 & v4) and there isn't any hackmii installer 0.6, only HBC version has changed, so speculation can stop right now

btw, no matter what they could do, any boot2 update WILL delete bootmii, if it's not deleted it means boot2 did not get updated...

If either of them were originally boot2v4, then you wouldn't be able to install BootMii as boot2. This is what was confusing me, but once I was told that boot2 isn't part of the NAND backup, it made sense.

that's not true, you CAN install bootmii in boot2 v4, there is nothing preventing you to do that (otherwise, why would they had released a new installer for those who made the official 4.2 update, which includes the new boot2 ?)

the only thing that can prevent bootmii installation in boot2 is the version of boot1

 

[illinialex24]

I've literally been saying this for two pages lol. I hope they finally listen.

If either of them were originally boot2v4, then you wouldn't be able to install BootMii as boot2. This is what was confusing me, but once I was told that boot2 isn't part of the NAND backup, it made sense.

No, you have to have a bug in boot1 to install bootmii. Having boot2v4 is unrelated to having a bootmii as boot2able Wii.

 

[Dr. Clipper]

that's not true, you CAN install bootmii in boot2 v4, there is nothing preventing to do that (otheerwise, why would they had released a new installer for those who made the official 4.2 update, which includes the new boot2 ?)

the only thingthat can prevent bootmii installation in boot2 is boot1

Yes, but the Wiis that shipped with the new boot1 are the first Wiis where boot2v4 was seen in the wild. So if NAND backups were possible at 4.1, it means both of zektor's Wiis had boot2v3 or less and thus both should have updated by the 4.2 update (except if they had been updated then NAND restored to 4.1, which I thought replaced boot2 as well before).

Anyway, this is too much derailment. There does still seem to be something weird with zektor's Wiis still going on given it appears both went through revirgining, but we should take it to its own thread later once zektor has had enough sleep to do further testing.

On topic:

TBR on 4.2, WOO!

 

[piratesmack]

I've literally been saying this for two pages lol. I hope they finally listen.

If either of them were originally boot2v4, then you wouldn't be able to install BootMii as boot2. This is what was confusing me, but once I was told that boot2 isn't part of the NAND backup, it made sense.

No, you have to have a bug in boot1 to install bootmii. Having boot2v4 is unrelated to having a bootmii as boot2able Wii.

I think what he means is if your Wii came with boot2v4, then your boot1 wouldn't have the sign bug.

 

[illinialex24]

Right but with the 4.2 update, its too easy to get a 4.1U Wii with boot2v4.

 

[kyliecoast]

Newb here ...

I tried running your new TBR MOD on my virgin 4.2e (boot2v4). I downgraded IOS15 (it said it was successful) but when I ran the
IOS36 to IOS236 it failed with the following error:

ES_AddTicket returned -2011
You need IOS with trucha bug, thats what IOS 15 downgrade is good for.


Then I restored IOS15 and it said it IOS15 restored successfully. What could be the problem?

(I left the setting as default, patch hatch check YES, patch ES_Identify YES and patch NAND permissions NO, and tried again with 3 'YES').

I'm guessing that the IOS15 downgrade has been unsuccessful but the program output says it was successful - what can I do to re-introduce the trucha bug into my virgin 4.2e (boot2v4)
Thanks

 

[Dr. Clipper]

Newb here ...

I tried running your new TBR MOD on my virgin 4.2e (boot2v4). I downgraded IOS15 (it said it was successful) but when I ran the
IOS36 to IOS236 it failed with the following error:

ES_AddTicket returned -2011
You need IOS with trucha bug, thats what IOS 15 downgrade is good for.


Then I restored IOS15 and it said it IOS15 restored successfully. What could be the problem?

(I left the setting as default, patch hatch check YES, patch ES_Identify YES and patch NAND permissions NO, and tried again with 3 'YES').

I'm guessing that the IOS15 downgrade has been unsuccessful but the program output says it was successful - what can I do to re-introduce the trucha bug into my virgin 4.2e (boot2v4)
Thanks

For the second step (installing IOS236), did you make sure to choose IOS15 at the first IOS selection screen? Was it saying IOS15 at the top right f the screen during the install?

Check my guide for step-by-step instructions. If those fail, then there seems to be a problem.

 

[kyliecoast]

Thankyou Dr Clipper. I was choosing IOS36. It works now that I used it on IOS15! yay! thankyou!

I then used AnyTitle Deleter to delete the stub IOSes and then ran cIOS38 rev14 installer. WAD manager is working on my virgin 4.2e! I can't believe it.
Thanks for everybody!

 

[kyliecoast]

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

 

[Dr. Clipper]

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

 

[kyliecoast]

Thanks again Dr Clipper

 

[zektor]

Strange. I just tested another Wii that had the v0.5 bootmii installed as boot2. I performed the v4.2U official update on this one, and it DID delete bootmii from boot2. I know TT said that nothing changed bootmii wise in the 0.6 update, but what would be the reason for this? I am baffled....

Simple: it depends on the boot2 version which was installed in these Wii before updating, if you already had boot2 v4 when installing bootmii, it won't be updated (the official update only do necessary updates) and remain untouched so any previously installed bootmii will stay...

EDIT: Nevermind. I know what happened.

The first Wii (the one that did not erase bootmii on official update) is different in one way...and it completely slipped my mind.

I updated this console to v4.2 officially a few days ago in testing. IIRC, it *did* erase my boot2 bootmii then. I bannerbombed (actually, I used the Indy hack then..bannerbomb was not available at that time) and installed bootmii afterward. Now, when I restored my v4.1U nand and performed another official update, the Nintendo updater must have seen that the boot2 was current and it skipped it on updating.....hence why bootmii was still in boot2 after the upgrade.

The other Wii has been sitting in the closet and that was the FIRST time it saw the official v4.2 update. Even tho I installed the latest bootmii before updating, the Nintendo update saw that my boot2 was a lesser version as a whole, so it updated (and wiped) boot2.

Mystery solved. Not a big mystery really, but it was last night since I was half asleep