UDPIH: USB Host Stack exploit + Recovery Menu

It's been a while without any major exploits in the Wii U scene, so I present to you:

USB Descriptor Parsing Is Hard (UDPIH)

An exploit for the Wii U's USB Host Stack. Pronounced like "mud pie" without the M.

The write-up can be found here!

What does this mean?​

Since the USB Stack is running before anything on the PPC side of the Wii U is booted, this allows unbricking things like CBHC bricks without any soldering!


Supported devices:​

  • Raspberry Pi Pico (W) / Pico 2 (W)
  • Raspberry Pi Zero (W) / A / A+ / Zero 2 W / 4 / 5
  • Steam Deck
  • Espressif ESP32 S2 / S3
  • Nintendo Switch capable of running udpih_nxpayload

Instructions​

Device Setup​

Follow the setup guide for the device you want to use below:

Booting the recovery_menu​

warning
Important notes for this to work:
  • Make sure no other USB devices are attached to the console.
  • Only use USB ports on the front of the console, the back ports will not work.
  • If your console has standby mode enabled, pull the power plug and turn it on from a full coldboot state.
  • Copy the latest release of the recovery_menu to the root of your FAT32 formatted SD Card.
  • Insert the SD Card into the console and power it on.
  • As soon as you see the "Wii U" logo on the TV or Gamepad plug in your prepared UDPIH device.
    This timing is important. If you're already in the menu, the exploit won't work.
    Depending on the device, you might have to plug it in sooner or later. This might take several attempts.
    If you get no video output or a distorted screen, your timing was most likely wrong.
  • After a few seconds you should be in the recovery menu.
So what's this recovery menu? The recovery menu allows you to fix several bricks:
screenshot

Wii U Recovery Menu

A simple recovery menu running on the IOSU for unbricking.

Options​

Set Coldboot Title
Allows changing the current title the console boots to.
Useful for unbricking CBHC bricks.
Possible options are:
  • Wii U Menu (JPN) - 00050010-10040000
  • Wii U Menu (USA) - 00050010-10040100
  • Wii U Menu (EUR) - 00050010-10040200
On non-retail systems the following additional options are available:
  • System Config Tool - 00050010-1F700500
  • DEVMENU (pre-2.09) - 00050010-1F7001FF
  • Kiosk Menu - 00050010-1FA81000
Dump Syslogs
Copies all system logs to a logs folder on the root of the SD Card.

Dump OTP + SEEPROM
Dumps the OTP and SEEPROM to otp.bin and seeprom.bin on the root of the SD Card.

Start wupserver
Starts wupserver which allows connecting to the console from a PC using wupclient.

Load Network Configuration
Loads a network configuration from the SD, and temporarily applies it to use wupserver.
The configurations will be loaded from a network.cfg file on the root of your SD.
For using the ethernet adapter, the file should look like this:
Code:
type=eth

For using wifi:
Code:
type=wifi
ssid=ssidhere
key=wifikeyhere
key_type=WPA2_PSK_AES

Pair Gamepad
Displays the Gamepad Pin and allows pairing a Gamepad to the system. Also bypasses any region checks while pairing.
The numeric values represent the following symbols: ♠ = 0, ♥ = 1, ♦ = 2, ♣ = 3.
Note that rebooting the system might be required to use the newly paired gamepad.

Install WUP
Installs a valid signed WUP from the install folder on the root of your SD Card.
Don't place the WUP into any subfolders.

Edit Parental Controls
Displays the current Parental Controls pin configuration.
Allows disabling Parental Controls.

Debug System Region
Fixes bricks caused by setting productArea and/or gameRegion to an invalid value. Symptoms include being unable to launch System Settings or other in-region titles.

System Information
Displays info about several parts of the system.
Including serial number, manufacturing date, console type, regions, memory devices...

Load BOOT1 payload
Loads a payload from the root of the SD Card named boot1.img and executes it from within boot1.
If the file is named boot1now.img it gets loaded automatically when starting the recovery_menu after a 5 second timeout.

Credits​

Special thanks to Maschell, rw-r-r-0644, QuarkTheAwesome, vgmoose, exjam, dimok789, and everyone else who contributed to the Wii U scene!
 
Last edited by GaryOderNichts,
How did the font corrupt? Is the eMMC failing? Did you replace it?

Also you didn't do a flush before you resetted it hard
 
Any way to grab the controller pairing Pin without being able to see the screen? Ideally through the dumps? I can blind dump, but can't find any way to get the Pin to pair a new controller. Dead HDMI.
 
I think the recovery writes it to the SD when you go to the pair gamepad option
That would be perfect, I'll take a look tonight when I try again.
Post automatically merged:

I think the recovery writes it to the SD when you go to the pair gamepad option
I was able to test on a console that does have a working output, and it doesn't dump the pin to the SD. Looks like brute forcing might be the only way
 
Last edited by sirjman,
Hi, I have a hackable Switch laying around, but it's vanilla. Do I have to fully mod it (emuMMC...etc) or can I just boot UDPIH payload from TegraRcmGUI when on RCM mode?

Thanks in advance.
Yep. You can run the udpih payload via rcm for example. There is no need to setup an emummc for this.
 
Just have to say thanks so much for this, I've rescued so many WiiUs with this tool, great work and thank you for sharing 😊
 
I was able to test on a console that does have a working output, and it doesn't dump the pin to the SD. Looks like brute forcing might be the only way
You are right, it isn't in the main branch.

I compiled it here, so it dumps the pin directly on loading the recovery, so you don't have to press any buttons
 

Attachments

You are right, it isn't in the main branch.

I compiled it here, so it dumps the pin directly on loading the recovery, so you don't have to press any buttons
Awesome, I'll try that one when I go home next week. Thanks!
 
I just came to say thank you, for real. I'm so grateful for this tool. You saved my Wii U which had been in its box for 2 years, since it gave 160-0103 error for no apparent reason . I even bought a second Wii U.

Thank you so much man, thank you.
 
It would require a lot of adjustments to work on old firmware versions. Only 5.5.X is supported for now.
Can you please provide an update on if support for old FW may be a possibility in the future? The quoted post is from July 2022 and looking through the entire thread your last mention of old/outdated/incompatible firmware was in January 2023 (#518).

In addition to the other people in this thread with known or suspected old FW on their consoles I personally have a couple labeled as having "2.x" and "3.x" firmware. I'm at least hoping to get OTP dumps in order to decrypt MLC dumps from NAND-AID. de_Fuse is apparently an alternative, but that looks like a last resort.

Thanks!
 
I have a friend that bricked his Wii u on the first ever launch day update. Think there's going to be a way to unbrick it?
 
Last edited by Evamdro,
Hi.

What do I install to get Wii menu (not really urgent since it's on Warawara plaza) and Load disc menu back? This was a result of rednand + minute + region change.
 
Hello i have this error code 160-1710 and i can boot with UDPIH and set cold boot title but after reboot same error code anyone know how to fix? My console is MLC
 

Attachments

  • 20231109_181841.jpg
    20231109_181841.jpg
    3 MB · Views: 95
  • 20231109_182405.jpg
    20231109_182405.jpg
    3.1 MB · Views: 97
  • 20231109_182434.jpg
    20231109_182434.jpg
    3.7 MB · Views: 89
Hi there, would anyone be able to provide links to the raspberry pi pico or zero for purchase? also, is there a preference between the two for wii u purposes?
 
Hi there, would anyone be able to provide links to the raspberry pi pico or zero for purchase? also, is there a preference between the two for wii u purposes?
If it's Raspberry Pi Pico you're looking for, I've personally purchased one linked here (one from AliExpress, in fact) for setting up my GameCube's Picoboot. It's one of the ways to support the Picoboot developer and it's pretty cheap as well (provided shipping costs aren't ridiculously high for you for one reason or another).
 
That's neither the error code for eMMC corruption, nor is it the CBHC error code (so changing the CB title won't help)
Maybe it is SLC corruption, I don't know the error code for that from the top of my head. Please dump and upload the logs.
From the logs we can probably see what's wrong.
 

Site & Scene News

Popular threads in this forum