Difference between revisions of "BC-NAND"
Jump to navigation
Jump to search
Hallowizer (talk | contribs) (Ok, I’m 99% sure it’s the boot program, there’s literally no other explanation for half of these things) |
Hallowizer (talk | contribs) m (Categorized) |
||
| Line 2: | Line 2: | ||
Because the [[Homebrew Channel]] did not have any form of boot program, [[fail0verflow]] never set an entrypoint in the main [[DOL]], since the [[Broadway]] always boots to 0x80003400, and therefore [[IOS]] ignores that field. However, BC-NAND suddenly got inserted on the vWii; because the main DOL was content 1, it was loaded into memory as if it was loaded by the normal boot program, but BC-NAND then jumped to 0, which caused issues. | Because the [[Homebrew Channel]] did not have any form of boot program, [[fail0verflow]] never set an entrypoint in the main [[DOL]], since the [[Broadway]] always boots to 0x80003400, and therefore [[IOS]] ignores that field. However, BC-NAND suddenly got inserted on the vWii; because the main DOL was content 1, it was loaded into memory as if it was loaded by the normal boot program, but BC-NAND then jumped to 0, which caused issues. | ||
| + | |||
| + | [[Category:NAND Boot Program]] | ||
Latest revision as of 22:06, 18 August 2022
BC-NAND is an ancast image for the vWii installed as title 1-512. It replaces the NAND Boot Program when launching any title that includes one, and is responsible for lowering the Espresso clock speed for Wii compatibility.
Because the Homebrew Channel did not have any form of boot program, fail0verflow never set an entrypoint in the main DOL, since the Broadway always boots to 0x80003400, and therefore IOS ignores that field. However, BC-NAND suddenly got inserted on the vWii; because the main DOL was content 1, it was loaded into memory as if it was loaded by the normal boot program, but BC-NAND then jumped to 0, which caused issues.