Because updating RedNAND would currently brick the system without first updating SysNAND (which makes it kind of pointless)Just to clarify, are we really recommending against a redNAND now? Why has the stance on this suddenly changed?
Because updating RedNAND would currently brick the system without first updating SysNAND (which makes it kind of pointless)Just to clarify, are we really recommending against a redNAND now? Why has the stance on this suddenly changed?
I didn't realise this. I might erase my redNAND later today, then. Anything we should avoid to make syre we don't brick out sysNAND?Because updating RedNAND would currently brick the system without first updating SysNAND (which makes it kind of pointless)
Editing anything that's not in a "content" folder without knowing what you're doingI didn't realise this. I might erase my redNAND later today, then. Anything we should avoid to make syre we don't brick out sysNAND?
yeah, but its kinda useless rn, no reason to use it now.What about sys config tool? Don't you need rednand to install that onto? Since it would brick sysnand?
That means haxchi was already ran.Is the Homebrew Launcher channel supposed to show a black screen when booting from sigpatched sysNAND?
That defeats the purpose of the channel though, right?That means haxchi was already ran.
Open Mii Maker to go back to it.
So I noticed this message:
"BE VERY CAREFUL AND ONLY USE CBHC IF YOU KNOW THE NORMAL HAXCHI VERSION WORKS FINE, AFTER INSTALLATION DONT DO ANYTHING STUPID LIKE MOVING THE DS VC AROUND OR DELETING YOUR DS VC OR UPDATING YOUR SYSTEM OR YOUR WIIU IS DEAD! I AM NOT RESPONSIBLE FOR ANY BRICKS TO YOUR WIIU CONSOLE.
So if my console updates without me realizing it's going to get bricked? Is that what this means?
So i have i BUY a DS game, i cant download one and install it on the NAND, backup way?
Where is the list for the supported DS games?
You hit the home button to cancel it, and then you can get the menu.CBHC is pretty awesome thus far. I found out the following:
Booting using the default fw.img-less patching is around 30 seconds (never timed it). However, this method of patching is limited. WUPserver and FTPiiU Everywhere don't work. WUPclient can't connect and FTPiiU Everywhere can only list the directory contents of the SD card. Also, the sigpatching doesn't get reapllied when exiting System Settings.
Booting regular sysNAND CFW from the CBHC menu works (no infinite loop or double loading). However, the Wii U will freeze to a black screen when exiting the channel version of the Homebrew Launcher. Also, when exiting system settings it will bring you back to the CBHC menu.
Booting coldboothax CFW works as long as you have syshax.xml. It doesn't double load and the Wii U goes from power on to the menu in about 45 seconds. This saves about 20 seconds over the old coldboothax which caused the double load. Everything else works as it did with coldboothax. No freezing when exiting HBL, WUPhax/FTPiiU Everywhere works, and iosuhax reloads when exiting System Settings.
You can select what you want to autoboot (Start Menu with patching, load HBL, or boot fw.img) or you can leave autoboot disabled.
I just can't figure out how to cancel the autoboot.
Thank you @FIX94 !
Edit: You cannot Autobot. Stupid autocorrect.