Separate names with a comma.
Discussion in 'Wii - Hacking' started by Vishnoo, Jul 2, 2016.
If i install bootmii as boot2 .Can i recover a full brick.Can it prevent me from any type of bricks.
If you install bootmii as boot2, you can recover from just about any kind of brick, as long as you didn't mess with boot2 afterwards to cause the brick in the first place. You should also have a NAND backup on hand to more easily recover from a brick.
Installing bootmii as IOS offers almost no brick protection.
What is boot 1 and boot 2.
boot0 is the first-stage bootloader. It loads boot1.
boot1 is the second-stage bootloader. It loads boot2.
boot2 is the third-stage bootloader. It loads the system menu and other things.
If i install bootmii as boot2,Then bootmii boots system menu.Am i right?
Then why are you recommended to install as iOS in some guides?
Because you can still use some of bootmii's features with it, such as creating and restoring NAND backups. If you're bricked, however, bootmii as IOS will likely not be able to help you.
Yes, basically. The modified boot2 boots it.
no boot2 cannot fix low level brick and error 002 brick
With bootmii installed as boot2, you can recover from most bricks. Even if one's Wii is so screwed up that it won't boot, one can restore a NAND backup using bootmii installed as boot2.
no i tested with a wii that was screwed low level brick = cant boot anything
It sounds like you didn't have bootmii installed as boot2. Perhaps you had it installed as IOS instead because your Wii didn't support it being installed as boot2.
no it had boot2 maybe low level brick screwed all boot funcions (boot0 boot1 and boot2)
Bootmii as Boot2 can recover almost 99.9 of the brick, error 002 its from a game needing an update to play. so its not a full brick.
Boot 2 its loaded from 1, which is loaded from boot0.
Boot0 "cant be damaged" due to its Read Only Function, therefore, the first access its boot2 which is loaded by boot2, since it use a write once function.
Having Bootmii or priiloader on boot2, plus a FULL BACK UP of the nand, its pretty much a safe bet among almost any brick.
Without being rude, please stop misleading user, the same thing happened on the last thread you were posting, saying that USBloaderGX was shit, and that WBFS partition was the best partition to have, since fat32 did not allow 4gb games...
Not trying to be rude, but please, first inform yourself. C:
Priiloader installs to the system menu, not boot2, which is why it's the second-best option compared to bootmii installed to boot2.
As far as i know you cant have priiloader and Bootmii on the same system, since its true, priiloader installs as let says, an IOS, however, if you install Priiloader when having Bootmii, holding the reset button will load priiloader instead of Bootmii. trough from there you can go to mostly anywhere, however, i still recommend Botmii as boot2 is possible. if no, then as an IOS, and priiloder.
the new boot1 protects boot2 from overwriting so i recommend then priiloader it has much more features then bootmii
Yes, one can have Priiloader and bootmii on the same system. Priiloader installs to the system menu, and bootmii installs to boot2 and/or an IOS. I have bootmii installed as boot2 for brick-protection, bootmii installed as an IOS because there's no reason not to, and Priiloader installed to the system menu for various system menu hacks.
Priiloader is the best one can do without bootmii as boot2, but it can't help in a lot of cases. One should also install bootmii as an IOS, because Priiloader might be able to get you to it in order to restore a NAND backup.
I, normally install bootmii as boot2, then priiloader, however, hitting resset launch priiloader, im asumming that having prilloader plus bootmii as boot2, will trigger priiloader instead of bootmii, but since priiloader can launch HBC, and HBC can launch Botmii, he/she should be fine.
However priiloader itself doe snot offer a nand restore function. however it does have a launch.dol you can pretty much boot MMM and install the system menu again, hopefully the nand its not corrupted.
What if i install Botmii as Boot2, and have prilloader, but priiloader cant get to HBC since the nand its lets say corrupted, and hitting reset trigger priiloader and not botmii. wouldnt it be better to have bootmii without priiloader, long time i dont mess with a wii, and cant quite remember if bootmii loads without pressing the reset button and just having the bootmi files on the SD card.
actully theres a way to stop boot1 from protecting boot2
why do you need to have a nand backup on priiloader? lol
Depending on how you mess with the system menu, Priiloader can become unusable since it installs to the system menu. If, for example, you install a system menu in conjunction with an IOS stub for that system menu, Priiloader gets erased because you've overwritten the system menu, the system menu can't boot, and you can't save your Wii without bootmii as boot2.
By default, bootmii as boot2 is set to launch automatically at boot with the proper easy-to-obtain files on your SD card. The reset button is irrelevant.