CBHC opens, but I get error code 160-0101 when trying to open System Menu

Dokkora

New Member
OP
Newbie
Joined
Dec 4, 2021
Messages
1
Trophies
0
Age
26
XP
25
Country
Brazil
Hey people, how are you doing?
By the answers in the forum I'm going to assume the Wii U is totally KO'd, but I'd like to ask anyway:
I just got a Wii U with CBHC that had a vWii bricked. I tried to use vWii Decaffeinator (I know, I should've read the instructions, but now it's too late 🤷‍♂️) and ended up bricking the Wii U system menu as well.
It enters CBHC normally, but turns off when I try to enter vWii and I get an error 160-0101 when I try to enter the Wii U menu.
I also get a -5 error when trying to get into Homebrew Launcher or Mocha CFW, so I'm assuming the previous owner deleted the files from the SD card.
I don't have a NAND backup, so the hardmod restoration won't be possible, but since it turns on CBHC, I was wondering if there's any way to fix those errors.
Maybe putting the right HBL files in the SD and running it through CBHC?
 

Kopimist

Well-Known Member
Member
Joined
Nov 6, 2019
Messages
197
Trophies
0
Age
34
XP
540
Country
United States
-5 means its not finding the homebrew launcher (hbl) or mocha etc. Try redownloading those files to the sd card and see if it launches at least into hbl. If it launches into hbl depending on exactly what was modified at the system level, it might be possible to ftp over whatever corrupt files there are on the WiiU menu side. Lets focus on getting that up amd running If at all possible before trying to tackle the vWii side. Don't want to mess with too many things at once again.
 

AQS

Well-Known Member
Newcomer
Joined
Oct 15, 2021
Messages
47
Trophies
0
Age
39
XP
277
Country
Canada
Hey people, how are you doing?
By the answers in the forum I'm going to assume the Wii U is totally KO'd, but I'd like to ask anyway:
I just got a Wii U with CBHC that had a vWii bricked. I tried to use vWii Decaffeinator (I know, I should've read the instructions, but now it's too late 🤷‍♂️) and ended up bricking the Wii U system menu as well.
It enters CBHC normally, but turns off when I try to enter vWii and I get an error 160-0101 when I try to enter the Wii U menu.
I also get a -5 error when trying to get into Homebrew Launcher or Mocha CFW, so I'm assuming the previous owner deleted the files from the SD card.
I don't have a NAND backup, so the hardmod restoration won't be possible, but since it turns on CBHC, I was wondering if there's any way to fix those errors.
Maybe putting the right HBL files in the SD and running it through CBHC?

Here's what I'd recommend

1. Setup your SD card to have the following files (make sure the SD card is formatted as FAT32). Use a 64GB sd or larger as you'll need it for step 3 below

\wiiu\apps\homebrew_launcher\homebrew_launcher.elf
\wiiu\apps\nanddumper\nanddumper.elf
\wiiu\apps\WiiUFtpServer\WiiUFtpServer.rpx

2. Insert the SD card, boot up the console .. assuming you get the CBHC menu, select Home Brew Launcher.. This should boot "\wiiu\apps\homebrew_launcher\homebrew_launcher.elf"

3. Launch Nanddumper and make sure to select all the options to "YES" including the MLC partition .. This will take about 1.5 hrs.. Doing this will ensure that you get your hands on the unique console key (opt.bin) in case you get into further trouble.

4. Once a full nand backup is complete, power off the console, remove SD card and copy the nand backup files to your PC fore safe keeping ( ensure that you have opt.bin , slc.bin , and a multipart mlc.bin) .

5. Boot up the console , launch Home Brew Launcher again, and this time open WiiUFtpServer ( The console will need to be connected to your network .. either via a previously set up wifi , or if that is not set up you'll need to get a USB LAN Adapter dongle )

6. Fix XYZ using FTP

... All of this carries a high risk of bricking your system further , but this is what I'd do if it were my system (only if I had a working backup of course ) .. good luck!
Perhaps wait to get a few more responses from other folks as well .. like @godreborn
 
Last edited by AQS,

Milonjorge

Member
Newcomer
Joined
Feb 8, 2022
Messages
6
Trophies
0
Age
21
Location
Spain
XP
97
Country
Spain
Here's what I'd recommend

1. Setup your SD card to have the following files (make sure the SD card is formatted as FAT32). Use a 64GB sd or larger as you'll need it for step 3 below

\wiiu\apps\homebrew_launcher\homebrew_launcher.elf
\wiiu\apps\nanddumper\nanddumper.elf
\wiiu\apps\WiiUFtpServer\WiiUFtpServer.rpx

2. Insert the SD card, boot up the console .. assuming you get the CBHC menu, select Home Brew Launcher.. This should boot "\wiiu\apps\homebrew_launcher\homebrew_launcher.elf"

3. Launch Nanddumper and make sure to select all the options to "YES" including the MLC partition .. This will take about 1.5 hrs.. Doing this will ensure that you get your hands on the unique console key (opt.bin) in case you get into further trouble.

4. Una vez que se completa una copia de seguridad nand completa, apague la consola, retire la tarjeta SD y copie los archivos de copia de seguridad nand en su PC para mantenerlos seguros (asegĂşrese de tener opt.bin, slc.bin y un mlc.bin de varias partes) .

5. Inicie la consola, inicie Home Brew Launcher nuevamente y esta vez abra WiiUFtpServer (la consola deberá estar conectada a su red... ya sea a través de un wifi previamente configurado, o si no está configurado, necesitará para obtener un dongle USB LAN Adapter)

6. Desde su PC, envĂ­e FTP a su consola a la siguiente ruta \slc\sys\config\

Edite el archivo "system.xml"

Dentro de las primeras líneas, verá una etiqueta similar a esta... Esto representa el ID de título de su título DS (CBHC)
<default_title_id tipo="hexBinario" longitud="8"> 0005000010179b00 </default_title_id>

Para restaurarlo de nuevo al menĂş del sistema, puede cambiarlo a lo siguiente

<default_title_id tipo="hexBinario" longitud="8"> 0005001010040100 </default_title_id>



... Todo esto conlleva un alto riesgo de bloquear aún más su sistema, pero esto es lo que haría si fuera mi sistema... ¡buena suerte!
Tal vez esperar a recibir algunas respuestas más de otras personas también... como [USUARIO=221542]@godreborn[/USUA
If he change the boot title id the cbhc will be desactivate and the wii u will brick totally because the menu is bricked
 
  • Like
Reactions: Kopimist

Kopimist

Well-Known Member
Member
Joined
Nov 6, 2019
Messages
197
Trophies
0
Age
34
XP
540
Country
United States
If he change the boot title id the cbhc will be desactivate and the wii u will brick totally because the menu is bricked
This actually makes a lot of sense. It will forces the console to boot into a bricked system menu, instead of CBHC and create a full brick
 

AQS

Well-Known Member
Newcomer
Joined
Oct 15, 2021
Messages
47
Trophies
0
Age
39
XP
277
Country
Canada
If he change the boot title id the cbhc will be desactivate and the wii u will brick totally because the menu is bricked

Error 160-0101 normally occurs when the system is trying to boot into a title that does not exist.
His System menu is probably not bricked, otherwise he'd be getting error 160-0103 ... but who know you guys may be right , maybe something's up with the system title id : 0005001010040100 .. something he could examine by extracting mlc.bin after doing a nand backup.

In either case, he should definitely try and get a nand backup ( even in a semi-bricked state) to get the opt.bin before trying anything else

 
Last edited by AQS,
  • Like
Reactions: Kopimist

Lazr1026

Member
Newcomer
Joined
Oct 30, 2020
Messages
9
Trophies
0
Age
15
XP
109
Country
United States
Error 160-0101 normally occurs when the system is trying to boot into a title that does not exist.
His System menu is probably not bricked, otherwise he'd be getting error 160-0103 ... but who know you guys may be right , maybe something's up with the system title id : 0005001010040100 .. something he could examine by extracting mlc.bin after doing a nand backup.

In either case, he should definitely try and get a nand backup ( even in a semi-bricked state) to get the opt.bin before trying anything else

someone once told me something..

1644739297680.png


edit: not me realizing you were replying to someone else after i sent that.
 
Last edited by Lazr1026,

Milonjorge

Member
Newcomer
Joined
Feb 8, 2022
Messages
6
Trophies
0
Age
21
Location
Spain
XP
97
Country
Spain
Error 160-0101 normally occurs when the system is trying to boot into a title that does not exist.
His System menu is probably not bricked, otherwise he'd be getting error 160-0103 ... but who know you guys may be right , maybe something's up with the system title id : 0005001010040100 .. something he could examine by extracting mlc.bin after doing a nand backup.

In either case, he should definitely try and get a nand backup ( even in a semi-bricked state) to get the opt.bin before trying anything else

Is better what he try to download the system menu in nusspli and if work, change the title id
 
  • Like
Reactions: AQS

godreborn

Well-Known Member
Member
Joined
Oct 10, 2009
Messages
28,332
Trophies
2
XP
18,289
Country
United States
You can download the system menu with jnus tool. It will decrypt it automatically. Then, I guess you could compare byte size with what's on your system.
 
  • Like
Reactions: AQS
General chit-chat
Help Users
  • No one is chatting at the moment.
    KenniesNewName @ KenniesNewName: https://youtube.com/shorts/mSSVwQ9i-UU?feature=share