Homebrew Should I give up?

[SouthNevadaWX]

I factory reset my Wii U after running out of options. I could no longer access my Internet Browser, nor could I install new mods. After I reset, same thing. I checked a thread on this website and found out I shouldn’t have done that. Should I give up?

 

[EnterpriseFreak]

I factory reset my Wii U after running out of options. I could no longer access my Internet Browser, nor could I install new mods. After I reset, same thing. I checked a thread on this website and found out I shouldn’t have done that. Should I give up?

Just to be clear here, does the console still boot? Does it manage to reach the home menu or does it show an error code before that? What exactly did happen to it? If you can still get to the home menu you could try to use the Bluubomb (https://github.com/GaryOderNichts/bluubomb) together with its install WUP payload to reinstall clean copies of whatever is damaged. Even if the console errors while booting there's still the option of using UDPIH (https://github.com/GaryOderNichts/udpih) to run code before the console shows the error code. You can re-install broken titles and fix some bricks using UDPIH too.

 

[V10lator]

Are you still able to run homebrew? If so grab logs (storage_slc:/sys/logs/), zip and upload them.

 

[SDIO]

in addition to @EnterpriseFreak post, I would recommend to first do a full NAND backup before attempting any repair.

 

[V10lator]

@SDIO I'm suspecting one of two things here:
- Corruption (on the Wii U menu title or some dependency) thanks to a crash or hard (4 button power press) shutdown.
- Hardware defect (dying NAND).

The logs should give at least hints about the issue, so grabbing them would be the first thing I would do.
You're right that taking a NAND backup right after this is a good idea through. Best would ofc. be to have a backup from before the data corrupted.

 

[SDIO]

if he does a full backup he can also extract the logs from the slc backup, which might be even easier if only udpih is working.
Also he can keep an eye on the backup process and look out for retries, which indicate an hardware fault.
Extracting the mlc with wfs-extract would us then give an overview which files are corrupted.
And of course we then also have a backup, in case the mlc degrades further