Hackmii installer fail

I have been for the past week, trying to help two people recover from a failed soft-mod removal. The details of what they did are unclear, but it defiantly involves the deletion of unknown ios files, likely with any title deleter. I apologize for my limited description, but I am doing my best to avoid breaking any of the forum rules. I have been providing advise on the forum that probably must remain unnamed, but I will mail a like to anyone interested to looking into the matter closer.

The problem is that the hackmii installer fails with

Installing The Homebrew Channel...
.Unable to install ticket (-1040001012).

FAILED (-1040001012).

Have tried many unmentionable fixes, dop ios mod crashes to unreadable stack dump. TBR, fails with error 1012, disk updates fail, person #1 has drivekey- setup fails with unkown error.
Person #2 also has preloader installed, but is unable to boot on ios70. He has limited system menu ability using ios36.
Any ideas as to how to fix this and get the hackmii installer to run would be great. Even an explanation to the cause would be great as well.
Thank you.

Here is the signcheck and hackmii installer log from person #1

"SignCheck 0.3b aka loveSexWii build report"
"Wii region", Usa
"Wii unique device id", 82107603

"IOS number", "Trucha bug", "Flash access", "Boot2 access", "Usb2.0 IOS tree"

"IOS250 (ver 65535)", Disabled, Disabled, Disabled, Enabled
"IOS70 (ver 6687)", Disabled, Disabled, Disabled, Disabled
"IOS61 (ver 5405)", Disabled, Disabled, Disabled, Disabled
"IOS57 (ver 5661)", Disabled, Disabled, Disabled, Disabled
"IOS56 (ver 5405)", Disabled, Disabled, Disabled, Disabled
"IOS55 (ver 5149)", Disabled, Disabled, Disabled, Disabled
"IOS38 (ver 3610)", Disabled, Disabled, Disabled, Disabled
"IOS37 (ver 3869)", Disabled, Disabled, Disabled, Disabled
"IOS36 (ver 3351)", Disabled, Disabled, Disabled, Disabled
"IOS35 (ver 3349)", Disabled, Disabled, Disabled, Disabled
"IOS34 (ver 3348)", Disabled, Disabled, Disabled, Disabled
"IOS33 (ver 3091)", Disabled, Disabled, Disabled, Disabled
"IOS31 (ver 3349)", Disabled, Disabled, Disabled, Disabled
"IOS28 (ver 1550)", Disabled, Disabled, Disabled, Disabled
"IOS22 (ver 1037)", Disabled, Disabled, Disabled, Disabled
"IOS17 (ver 775)", Disabled, Disabled, Disabled, Disabled
"IOS14 (ver 520)", Disabled, Disabled, Disabled, Disabled
"IOS13 (ver 273)", Disabled, Disabled, Disabled, Disabled

HackMii v0.6 installer starting up
PVR = 00087200
running under IOS 36 rev 0xd17
74 titles are installed
Found IOS 223: revision: 0xff00.
Found IOS 222: revision: 0xff00.
Found IOS 250: revision: 0xffff*
Found IOS 61: revision: 0x151d.
Found IOS 60: revision: 0x1900.
Found IOS 57: revision: 0x161d.
Found IOS 56: revision: 0x151d.
Found IOS 16: revision: 0x200.
Found IOS 70: revision: 0x1a1f*
Found IOS 55: revision: 0x141d.
Found IOS 51: revision: 0x1300.
Found IOS 50: revision: 0x1400.
Found IOS 38: revision: 0xe1a.
Found IOS 37: revision: 0xf1d.
Found IOS 35: revision: 0xd15.
Found IOS 34: revision: 0xd14.
Found IOS 33: revision: 0xc13.
Found IOS 31: revision: 0xd15.
Found IOS 30: revision: 0xb00.
Found IOS 28: revision: 0x60e.
Found IOS 22: revision: 0x40d.
Found IOS 21: revision: 0x30e.
Found IOS 20: revision: 0x100.
Found IOS 17: revision: 0x307.
Found IOS 15: revision: 0x20b.
Found IOS 14: revision: 0x208.
Found IOS 13: revision: 0x111.
Found IOS 12: revision: 0x10d.
Found IOS 11: revision: 0x100.
Found IOS 10: revision: 0x300.
Found IOS 9: revision: 0x30a.
Found IOS 36: revision: 0xd17*
Found IOS 3: revision: 0xff00.
Found IOS 2: revision: 0x1e1.
Found IOS 4: revision: 0xff00.
IOS versions: Installer: 34, HBC: 61, DVDX: 35
launching IOS for the installer...starting preparationsCalling boot2_run(1, 34)
Waiting for boot2 to load ...
boot2 loaded, waiting for IOS
IOS loaded: IOS34 v13.20
IPC started (515)
parsing last generation bootmap
found valid boot2 blockmap at block 1 (pos 0x627c0), submap 0, generation 2
found valid boot2 blockmap at block 5 (pos 0xe67c0), submap 0, generation 3
parse_blocks: found 2 valid blockmaps
found 2 valid blockmaps
using generation 3
boot2 blocks: 00 01 02 03 04 05 06
boot2bin @5,0 (blocks=0,1 - bootmii=0)
bootmii@-1,-1
boot2 blocks: 06 05 04 03 02 01 00
boot2bin @5,1 (blocks=6,5 - bootmii=0)
boot2 block layout: 2 2 1 1 1 0 0
Assembling boot2 in RAM
copyright size = 34
copyright text = 'Copyright 2008,2009 Team Twiizers.'
tmd ends at 0x80295dac, data starts at 0x80295de0
bootmii version = '1.1'
prepare_bootmii: bootmii_check_boot1 failed: -2
preparations done!The test results are in:

 Using IOS versions: Installer: 34, HBC: 61, DVDX: 35

The Homebrew Channel: Can be installed
DVDX: Can be installed
BootMii: Can only be installed as an IOS
 The installed boot1 version prevents a boot2 install (-2)
Unable to install ticket (-1040001012).
Unable to install ticket (-1040001012).
A BootMii install requires a SD card.

Runtime files will be written, these are required to
properly boot BootMii.

Here is the hackmii log and signcheck from person #2,

HackMii v0.6 installer starting up
PVR = 00087200
running under IOS 36 rev 0xd17
49 titles are installed
Found IOS 0: revision: 0x0*
Found IOS 202: revision: 0x2*
Found IOS 61: revision: 0x151d.
Found IOS 60: revision: 0x1900.
Found IOS 57: revision: 0x161d.
Found IOS 56: revision: 0x151d.
Found IOS 55: revision: 0x151e*
Found IOS 53: revision: 0x151e*
Found IOS 51: revision: 0x1300.
Found IOS 50: revision: 0x1400.
Found IOS 38: revision: 0xf1b.
Found IOS 16: revision: 0x200.
Found IOS 10: revision: 0x300.
Found IOS 70: revision: 0x1a1f*
Found IOS 37: revision: 0xf1d.
Found IOS 36: revision: 0xd17*
Found IOS 35: revision: 0xd15.
Found IOS 34: revision: 0xd14.
Found IOS 33: revision: 0xc13.
Found IOS 31: revision: 0xd15.
Found IOS 30: revision: 0xb00.
Found IOS 28: revision: 0x60e.
Found IOS 22: revision: 0x40d.
Found IOS 20: revision: 0x100.
Found IOS 17: revision: 0x307.
Found IOS 15: revision: 0x20b.
Found IOS 14: revision: 0x208.
Found IOS 13: revision: 0x111.
Found IOS 12: revision: 0x10d.
Found IOS 11: revision: 0x100.
Found IOS 21: revision: 0x30e.
Found IOS 2: revision: 0x1e2.
Found IOS 9: revision: 0x30a.
Found IOS 4: revision: 0xff00.
IOS versions: Installer: 34, HBC: 61, DVDX: 35
launching IOS for the installer...starting preparationsCalling boot2_run(1, 34)
Waiting for boot2 to load ...
boot2 loaded, waiting for IOS
IOS loaded: IOS34 v13.20
IPC started (510)
parsing last generation bootmap
found valid boot2 blockmap at block 1 (pos 0x627c0), submap 0, generation 4
found valid boot2 blockmap at block 5 (pos 0xe67c0), submap 0, generation 5
parse_blocks: found 2 valid blockmaps
found 2 valid blockmaps
using generation 5
boot2 blocks: 00 01 02 03 04 05 06
boot2bin @5,0 (blocks=0,1 - bootmii=0)
bootmii@-1,-1
boot2 blocks: 06 05 04 03 02 01 00
boot2bin @5,1 (blocks=6,5 - bootmii=0)
boot2 block layout: 2 2 1 1 1 0 0
Assembling boot2 in RAM
copyright size = 34
copyright text = 'Copyright 2008,2009 Team Twiizers.'
tmd ends at 0x80295dac, data starts at 0x80295de0
bootmii version = '1.1'
prepare_bootmii: bootmii_check_boot1 failed: -2
preparations done!The test results are in:

 Using IOS versions: Installer: 34, HBC: 61, DVDX: 35

The Homebrew Channel: Can be installed
DVDX: Can be installed
BootMii: Can only be installed as an IOS
 The installed boot1 version prevents a boot2 install (-2)
Unable to install ticket (-1040001012).
Unable to install ticket (-1040001012).
A BootMii install requires a SD card.

Runtime files will be written, these are required to
properly boot BootMii.

Mounting SD card...
Creating directory '/bootmii'...
Writing '/bootmii/armboot.bin'...
Writing '/bootmii/ppcboot.elf'...
Writing config file...

Done.

Unable to install ticket (-1040001012).

SignCheck 0.3b aka loveSexWii build report
Wii region, Europe
Wii unique device id, 119371059

IOS number, "Trucha bug", "Flash access", "Boot2 access", "Usb2.0 IOS tree"

IOS202 (ver 2), Disabled, Enabled, Disabled, Disabled
IOS70 (ver 6687), Disabled, Disabled, Disabled, Disabled
IOS61 (ver 5405), Disabled, Disabled, Disabled, Disabled
IOS57 (ver 5661), Disabled, Disabled, Disabled, Disabled
IOS56 (ver 5405), Disabled, Disabled, Disabled, Disabled
IOS55 (ver 5406), Disabled, Disabled, Disabled, Disabled
IOS53 (ver 5406), Disabled, Disabled, Disabled, Disabled
IOS38 (ver 3867), Disabled, Disabled, Disabled, Disabled
IOS37 (ver 3869), Disabled, Disabled, Disabled, Disabled
IOS36 (ver 3351), Disabled, Disabled, Disabled, Disabled
IOS35 (ver 3349), Disabled, Disabled, Disabled, Disabled
IOS34 (ver 3348), Disabled, Disabled, Disabled, Disabled
IOS33 (ver 3091), Disabled, Disabled, Disabled, Disabled
IOS31 (ver 3349), Disabled, Disabled, Disabled, Disabled
IOS28 (ver 1550), Disabled, Disabled, Disabled, Disabled
IOS22 (ver 1037), Disabled, Disabled, Disabled, Disabled
IOS17 (ver 775), Disabled, Disabled, Disabled, Disabled
IOS14 (ver 520), Disabled, Disabled, Disabled, Disabled
IOS13 (ver 273), Disabled, Disabled, Disabled, Disabled

Edited 1 time(s). Last edit at 12/18/2009 12:39AM by mauifrog.

Have you tried launching Dop-IOS MOD via LoadMii? Applications that don't work at all with just plain bannerbomb or whatever exploit you are using (if you are in fact using an exploit) tend to work better with LoadMii, some to the point of usability.

EDIT: The problem appears to be that the IOS that the HackMii installer is trying to use is not starting up properly. (possibly a corrupt IOS?) Installing a stock, unmodified IOS36 might help. Installing an unmodified IOS70 might rectify user #2's problem as well.



Edited 2 time(s). Last edit at 12/18/2009 04:15AM by WikiFSX.

Thank you for your reply. I will have them try loadmii, as I believe they bannerbombed dop ios mod.
So for apps that load-
Hackmii installer loads but fails
Signcheck loads
Various versions of WM load
TBR loads, but fails with error
Wads downloaded form NUSD all fail during install, error 1012 and 1024
The godforsaken, unmentionable customized ios38 installer r14 fails with Install ERROR! (ret = -4100), using ios250 I believe.
Have tried HBC loader and Bootmii booter, neither are present.

Both individual uninstalled bootmii, hbc, and possibly dvdx, among a few other things.

Currently trying another attempt of resonating ios16
And will also try dop ios mod via loadmii.

I am of the belief that a trucha bug enabled ios would help fix this trouble, does that sound right? So dop ios mod on ios 36 could be perfect.

Don't patch the IOSes at all. The HackMii Installer doesn't need the Trucha bug, and in fact refuses to use patched IOSes.

Just install an unpatched IOS 30 v1040 with Dop-IOS MOD and Hackmii should work fine.

Have tried to install ios30-v1040 with wadmanager using ios36 and others, receiving error 1012 and 1024 during install. Have tried to install other ios as well, but no luck, same result.

Still trying to get dop ios mod to load.

First, get a WAD (with NUSD) of IOS30 v2816 and uninstall it (if a WAD is present for a given title and version that is on the Wii, WAD Manager considers that WAD installed, in case you didn't know).
Then, install IOS30 v1040.

EDIT: What happens when you try to use Dop-IOS MOD through LoadMii? Same error?
EDIT2: Make sure that the people who are trying to use NUSD have a valid common key.



Edited 2 time(s). Last edit at 12/19/2009 12:59AM by WikiFSX.

OK, so person # has been able to load Dop-Ios-mod, used ios36 I believe.

He attempted to dop ios36, which failed with

Install returned -1
Installation complete!
Error: Something failed. (ret: -1)
Continue?
Are you sure you want to continue?
[A] Yes  NO [Home]/[Y] Exit

Pressed "Yes" and it returned to the previous Dop-IOS MOD v9 menu.

He also tried to uninstall ios30-v2816.wad, decryped with key.bin from NUS download. This failed with: "ERROR! (ret: -1017)"
He also tried to install ios30-v1040.wad decryped with key.bin from NUS, failed with "ERROR! (ret: -1035)"

I have asked person #2 to try to install ios30-v1040 with dop ios mod, waiting for the results.

Waiting for results from person #1 as well.

Thank you to all for the suggestions. They are much appreciated.



Edited 1 time(s). Last edit at 12/19/2009 11:43PM by mauifrog.

If they where to use dop ios mod to install a new ios36, which would be the best ios to run dop ios mod on? Should it be 36 or another?

NSMB offers update, but it fails. System menu offers update, but it also fails.

Run Dop-IOS MOD on any IOS but 36 to install an unpatched 36.

If System Menu updates are failing, there must be some serious problems. Did they do the IOS60 as 70 thing?

Thanks for all the info and ideas, but in the end I had to throw in the towel.

So, since this post I have come across perhaps 6-7 of these wiis. All wii#s have been on 4.2, some have had preloader/priiloader, some have had bootmii ios. All wii have attempted some type of virginization, no HBC etc. Signcheck, syscheck appears to give inaccurate reading on ios known to be patched, nothing but usb and nand permissions show. Nothing installs, HBC bootmii, wads fakesigned or official. I have been able to uninstall ios files using wadmanager and the ios wads. I uninstall all stubs, and ios 33, 34, 61, then attempted to reinstall ios16, 33, 34, 61- all fail to install with ret 1024.

I am convinced the these wii#s are beyond repair, but I am puzzled as to what could have happened to them. Any ideas?

I'm thinking that the IOSes installed onto those Wiis had badly mangled ES modules, so badly mangled that they didn't properly work. You could probably chalk it up to someone's crappy programming. Error -1024 is an out of memory error, so it seems likely.

Whats really odd about this is that, at lease in the first two wiis, most of the IOSes are unmodified. If any of the wiis are old enough to install Bootmii as boot2 and the Hackmii Installer is able to install it, you could try using Comex's NAND formatter. Since it does not rely on IOS, it may work. However, I advise against using the NAND formatter with Bootmii/IOS, as a full brick is not unlikely.

Here is Comex's NAND formatter, and the readme.

Also, are you sure that there is enough available space on the wii's NAND for the things you are trying to install?



Edited 1 time(s). Last edit at 04/13/2010 04:31AM by jbc007.

I had thought the memory might be full, that is why I had them uninstall a substantial number of ios to free up space. As for the mangeled ios, this error happens regardless of what ios is uses. Say ios36 and ios38 fail with ret 1024, same as ios250. Also, this error is given when installing officially signed ios, say ios16, ios33, ios34, etc- all fail regardless of the ios used in wadmanager.

Only one wii had bootmii ios, none boot2 and the hackmii installer will not install anything. With the wii with bootmii ios, I was able to load it using bootmii booter, but when attempting to use a modified boot2, I could not get it to work for them. On my wii I am able to bannerbomb loadmii, then load a usb with bootmii booter, then I swap sd cards with one that has a modified boot2 and load the bootmii booter from usb. This launches the modified boot2 for me, but no luck for the bricked wii user.

Is it possible that these wii's have a common hardware failure?

1) WAD Manager isn't supported around here
2) Have the IOSes you've tried had the Trucha Bug applied?

Well I have tried everything, but I the moment I am at installing official ios files- so no trucha bug required. Ios36 and ios38 among other should be able to install these, but they fail. I am not looking for support for wadmanager or any app, take your pick on the method of wad install, assume the result is the same. I want to know, what would cause such a corruption of the wii?


Also speaking of wadmanager. That is a strange position. You'll support dop-mii, but not wadmangager. Well the point is mute I am sure, but wadmanager does not do anything, it is the ios that it uses that does the dirty work, like that produced by dop-mii.... off topic, I know. Sorry.

Quote
mauifrog
Also speaking of wadmanager. That is a strange position. You'll support dop-mii, but not wadmangager. Well the point is mute I am sure, but wadmanager does not do anything, it is the ios that it uses that does the dirty work, like that produced by dop-mii.... off topic, I know. Sorry.

Wrong, Wad Manager (and the user, I guess), do the dirty work. IOS is just what the software runs on. The Trucha Bug enables it to do the dirty work. As far as DOP-Mii goes, you can't do anything illegal with it. So I don't see your point of us being in a strange position.

@Cactusjack901: The errors Mauifrog is experiencing are not related to not having the trucha bug.

WAD Manager is often used to install illegal WADs, which is why it is unsupported here. DOP-Mii can't install anything illegal (at least not in any normal situation) so it is supported.

IOSes are small, so you may need to delete something else, such as channels or WW/VC games, if present. Deleting IOSes is usually a bad idea, anyway. If I remember correctly, wiis can't perform system updates without a certain amount of free space to store temporary files. When deleting things, try running AnyTitle Deleter Mod or WAD Manager on any available cIOS, at least if the unmodified IOSes don't work.

Also, how much free space does does it say there is in data management? Deleting things through data management is probably the best idea, if possible.