It might still be saveable if they have an OTP backup (SEEPROM is not for this needed I believe)
Also, if your guide indeed doesn't mention not to delete the profile the DS game was purchased on you should probably add that.
its a matter of conveniance, i got cbhc installed every since day one
and im never going back to regular haxchi, people only brick their consoles when they do stupid stuff like deleting nnid that purchased the actual game, or formating the wiiu, this are the only 2 ways to brick your wiiu after you get cbhc running.I've never personally seen a brick via CBHC and I've modded a s**t ton of consoles. If it errors, it's always PEBKAC.its a matter of conveniance, i got cbhc installed every since day one
Yeah I just haven't had time. Also I didn't want to have a huge list of ways you can brick. If you understand the logic of how CBHC works you should be able to tell if you're about to do something that will brick your console. Just my thoughts
I've been rocking CBHC since it's release and although a lot of users are scared about this sort of thing, I can honestly say I've never had a single issue and love it loading from boot. But the instructions on what to do and how to do it, come with clear warnings about what not to do and so long as you follow these, I can't see you'd have a problem. - All of this aside however, when you have multiple accounts on a console, I don't think it's a good idea. I'd stick with the manual loading of HaxChi in that scenario. Also, as others have pointed out USB is always the best to install to or at the very least to test an install on before putting it on internal memory. I did that with BOTW before I transferred it to internal.
To be fair it would still be a pretty short list. There aren't a whole lot of ways you can brick a Wii U.
with cbhc installed there is only two lol well 3 if your nand actualy corrupts but that is an hardware fault and would have bricked anyway with or without cbhc
Oh, there are more ways, but they all boil down to "don't mess with system files", which should be common sense really.with cbhc installed there is only two lol well 3 if your nand actualy corrupts but that is an hardware fault and would have bricked anyway with or without cbhc
well but like i said those arent cbhc bricks without cbhc you would brick just as well doing that xD.
Do we even have a valid way of restoring a NAND backup? I haven't been paying attention to the scene much lately, so not sure if a good method is available. I have CBHC installed and a backup of the NAND and otp.
Yes. Check my signature. There's a guide for using a teensy++ to restore your nand or just fix your CBHC brick
This is not stupidity, it's ignoranceits a matter of conveniance, i got cbhc installed every since day one
CBHC is a dirty hack, not a proper solution. It's unfortunate that the guides don't give enough warnings about the risks.
Last edited by piratesephiroth,
I would like to insist that deleting the NNID when having CBHC installed does not brick the console; it is perfectly fine. It is visiting the Nintendo shop that bricks the Wii U, with the buyer NNID missing. Almost all guides formerly ask to not touch the VC game only, this is the shame.
Last edited by nailug,
Okay, tons of bullshit in here.
CBHC won't increase you bricking more than you writing anything else to the system. The Wii U is just crap in regards to NAND read/write, and generally the 160-1603 pops as much on a stock console as a hacked one. It's a poor exploit, yeah, but it's not really an unsafe one either.
CBHC won't increase you bricking more than you writing anything else to the system. The Wii U is just crap in regards to NAND read/write, and generally the 160-1603 pops as much on a stock console as a hacked one. It's a poor exploit, yeah, but it's not really an unsafe one either.
Last edited by lisreal2401,
Similar threads
