FenrirWolf said:Is this confirmed? I've dumped my NAND 3 times now.tenpmetabg said:I have read that writing-erasing NAND too much can be damageable... mind it !
FenrirWolf said:Is this confirmed? I've dumped my NAND 3 times now.tenpmetabg said:I have read that writing-erasing NAND too much can be damageable... mind it !
knowthing said:FenrirWolf said:Is this confirmed? I've dumped my NAND 3 times now.tenpmetabg said:I have read that writing-erasing NAND too much can be damageable... mind it !
pro2oman said:just out of curiosity is it possible to uninstall bootmii?
Wouldn't we be able to uninstall it by installing a boot2 wad from a Wii disc, overwriting BootMii?kedest said:pro2oman said:just out of curiosity is it possible to uninstall bootmii?
there is no uninstaller yet, that will be released later
FenrirWolf said:Is this confirmed? I've dumped my NAND 3 times now.tenpmetabg said:I have read that writing-erasing NAND too much can be damageable... mind it !
bdr9 said:Wouldn't we be able to uninstall it by installing a boot2 wad from a Wii disc, overwriting BootMii?kedest said:pro2oman said:just out of curiosity is it possible to uninstall bootmii?
there is no uninstaller yet, that will be released later
Helsionium said:To all who have problems with bootmii.ini, the configuration file for BootMii, I have found something (a bug?) that might be interesting.
First, a little explanation on ASCII control characters for the noobs:
ASCII control characters are special, unprintable characters, like for example "TAB" or "NEW LINE". There are 32 of them in total, but only two of them are of interest when dealing with the "bug" in BootMii: "CARRIAGE RETURN" (short: CR, in hex: 0x0D) and "LINE FEED" (short: LF, in hex: 0x0A)
In Unix-type environments, lines of text files usually end with LF (0x0A) only, while in Windows environments, lines are usually ended with CRLF (0x0D0A). This often causes texts from other environments to be incorrectly rendered or interpreted.
The BootMii problem might be a variant on that problem, as the presence of CRLF caused the file to be ignored. Also, the last character of the file must apparently be LF, because otherwise, the file was still ignored.
So if you have a problem with the bootmii.ini file, open it in a hex editor, remove all 0x0D characters, and ensure that the file is ended with a single 0x0A character. That fixed it for me, and I played around with it a little, my findings are consistent with the type of possible "bug" I explained.
Stroganoff said:FGOD said:anybody has any idea on how to get the sd card be read on pc after the format/backup with the bootmii nand dumper? i cannot back it up to pc as the sd card cannot be read on pc :s
That's odd. Does the SD partition appear in Disk Management? (start -> run -> compmgmt.msc -> disk management)
Also try to access it with a Linux LiveCD (e.g. Knoppix).
Or you can use a text editor with Windows/linux conversion support. (the open source Notepad++ for example, or any other supporting linux text format)mydarxide said:has anyone confirmed that HBC 1.0.2 can load files from USB HDD FAT Partition?Not yet, as stated on bugs.hackmii.com, openned by Bushing and marked as low priority.
To all who have problems with bootmii.ini, the configuration file for BootMii, I have found something (a bug?) that might be interesting.jhoff80 said:Bushing asked, here, for someone else NAND dump provided with his keys. Maybe the keys are for decrypting only, and he didn't attempt to install it on his Wii, or maybe he knows a way but I don't think it might be public for piracy reason.pacman366 said:so would it be possible to dump the nand from one wii and flash it to another w/ bootmii?Hmm I don't know the answer to that but that's an interesting thought. Theoretically, you could buy two Wiis and copy legally purchased DLC/ WW/ VC stuff to the second Wii that way (though the legality of that is iffy.)
QUOTE(Helsionium @ May 14 2009, 08:53 PM)
[...CR LF explanation...], open it in a hex editor, remove all 0x0D characters, and ensure that the file is ended with a single 0x0A character. That fixed it for me, and I played around with it a little, my findings are consistent with the type of possible "bug" I explained.