ya you get the ds game and make it load a cfwbooter app. which normally would just sig patch you and thats it. but all coldboothax is (from what i see) is editing an xml file that says the wiiu should auto load the wiiu menu title. instead you change that to kirby's title id and the wiiu automatically should play kirby when you boot it I think. But your kirby rom is actually not a rom but a way of booting cfwbooter then you are automatically sig patched at boot I gues.sI never knew it was even possible to do? I checked a thread it seems you need a ds vc game on your wiiu menu, that's all I know at the moment but it also seems like Brain Training DS VC might actually be worth using!. The video looked interesting.
ikr go to system settings>standby options>enable both quick start and standby functions BOOM coldboothax sans a dead sysNANDquick start?
Dude you should be the mascot for the forgotten quick start menu, it actually beats coldboothax in boot time speed and still lets you access sysNAND and is brick free #NEXOCUBE4QUICKSTARTSo, to clarify, I'M SO FUCKING TRIGGERED BECAUSE I BRICKED MY WII U WHILE TRYING TO EDIT THAT SYSTEM.XML (trying to install coldboothax)
So please, don't try installing coldboothax please --> or brick
Thanks that explains it a little more to me. I was googling it but I cant find a method on doing it, it just seems very up in the air from Smea at the moment.ya you get the ds game and make it load a cfwbooter app. which normally would just sig patch you and thats it. but all coldboothax is (from what i see) is editing an xml file that says the wiiu should auto load the wiiu menu title. instead you change that to kirby's title id and the wiiu automatically should play kirby when you boot it I think. But your kirby rom is actually not a rom but a way of booting cfwbooter then you are automatically sig patched at boot I gues.s
WHY YOU BE SILLY Don't do it! There is a reason everyone has removed mentions of it, its a terrible implementation as it locks you of sysNAND never letting you mod it again and quick start is better like I mentioned before so just use thatThanks that explains it a little more to me. I was googling it but I cant find a method on doing it, it just seems very up in the air from Smea at the moment.
ehe, i agreeWHY YOU BE SILLY Don't do it! There is a reason everyone has removed mentions of it, its a terrible implementation as it locks you of sysNAND never letting you mod it again and quick start is better like I mentioned before so just use that
Its ok, thanks for the advice I wasn't going to do it I would not be that silly! I was just talking out loud, I don't suppose I could even do it even if the instructions where black & white in front of me. I shall wait for something a bit more concrete. If @NexoCube says no, as well, up above then I definitely wont be doing it!WHY YOU BE SILLY Don't do it! There is a reason everyone has removed mentions of it, its a terrible implementation as it locks you of sysNAND never letting you mod it again and quick start is better like I mentioned before so just use that
Nope as I explained elsewhere once the fw.img is done patching sysNAND it calls to boot homemenu. homemenu=default title=haxchi yeah you can see where this is going. the only way to reverse it is to call homemenu by title ID instead but none has made a fw.img that those that yetHow does it lock you out of sysnand? I can see it would be tricky if you coldbooted into redNAND but I'm sure there are ways to interact with the sysNAND again. But just a plain modded fw.img for sysNAND booter would still have you in sysNAND and would let you change the xml again at your will.
It sets the haxchi title as the homemenu. That means you can't boot homemenuHow does it lock you out of sysnand? I can see it would be tricky if you coldbooted into redNAND but I'm sure there are ways to interact with the sysNAND again. But just a plain modded fw.img for sysNAND booter would still have you in sysNAND and would let you change the xml again at your will.