Wii U 启动直接卡在“Delete All Content and Settings”界面，UDPIH 恢复可用且存储看似正常，有何思路？

• #1

Hi all, first-time poster here. I’ve looked around the forum for a little while and it seemed that this could be a good spot to post some technical details from my digging around on a borked Wii U.

The Problem

My sister gave me her Wii U about two or so years ago along with a variety of games so my son and I can check it out. My memory is a bit hazy on the specifics at this point, but basically I went about clearing some games off of the console to make some room. After poking around, I decided it was best to just wipe it and set it up as a new console. Soon after, it got stuck on the “Deleting All Content and Settings” screen and has been basically that way ever since.

Right after the boot screen the previous screen flashes for about half a second, then the delete screen comes up and plays the usual ambient music. About 10 seconds or so later it freezes, the music stops, and nothing responds. Cold boots and unplugging for a while change nothing.

I considered the whole soldering approach, but I’m definitely not on the level to take that on. A recent experience on fixing a car head unit proved that out and I wasn’t about to do that to an old Nintendo console. Seeing that there was a recovery_menu and UDPIH approach was something I could get around more comfortably.

Console details:

Wii U: USA, WUP-101(02), made around September 2013, retail keyset, Wii U Menu 5.5.3 U.

The console has ever been modded or softmodded from what I could tell.

What I’ve done so far (Nothing written to the console):

• Got into the recovery menu with UDPIH using a Raspberry Pi 4 (recovery_menu v0.6). Took a few tries to get USB connectivity and the timing right.
• Dumped OTP + SEEPROM and backed them up.
• First Dump Syslogs gave me a ~14 KB log from the recovery session. It shows slc01 and mlc01 mounting fine, the master title 0005001010040100 found on mlc01, and no MMC errors. The MLC is a Toshiba 032G4C (29760 MiB).
• I then let the console sit on the hung delete screen for several minutes and dumped logs again. The menu reported success, but the logs folder came out empty.
• Set Coldboot Title to Wii U Menu (USA). No change.
• Connected to wupserver over Wi-Fi and checked things read-only with wupclient. The Wii U Menu title folder (00050010/10040100) has code, content and meta. meta/ has the boot images, boot movie, icon and meta.xml. meta.xml is 9621 bytes, valid XML (checked with xmllint), and ends with </menu>.
• productArea and gameRegion are both USA, so I haven’t touched Debug System Region.

What I’d love help with:

1. Has anyone found more details about a cause? Or perhaps some new ideas where fix could be implemented? I found similar reports on page 31 of the UDPIH thread from 2023 but no resolution.
2. Where does the console store whatever sends it to this screen at boot, and is it something I can look at read-only through wupclient?
3. Why would Dump Syslogs create an empty folder after reporting success?
4. Would Install WUP with the 5.5.6 USA update be safe way to proceed here? What folder layout does it expect, and is going from 5.5.3 up to 5.5.6 okay?

I haven’t changed or deleted anything on the console and I’m happy to run any read-only checks and share more info. I’m leaving out my serial number and OTP/SEEPROM files for obvious reasons.

Thanks for reading, and thanks to everyone who builds and maintains these tools. Getting this far without soldering has been great.

SDIO

Well-Known Member

• #2

The factory reset wipes the logs, so on every boot the previos logs get cleared.
First of all install ISFShax. After that you can run the wafel_setup_mlc plugin with an empty wafel_install folder. That will reset the initial Launch Value to make it boot in the initial setup instead of the factory reset.

From there you will see if you run into 160-0103 errors. If that still works we can run some tests to check the eMMC, which is likely failing.

• #3

The factory reset wipes the logs, so on every boot the previos logs get cleared.
First of all install ISFShax. After that you can run the wafel_setup_mlc plugin with an empty wafel_install folder. That will reset the initial Launch Value to make it boot in the initial setup instead of the factory reset.

From there you will see if you run into 160-0103 errors. If that still works we can run some tests to check the eMMC, which is likely failing.

Thanks SDIO. That explains the empty logs.

Before I start, a few questions so I don’t make things worse:

1. For the empty-wafel_install run, do I skip “Erase MLC” and “Delete scfm.img” in minute, so the MLC isn’t touched?
2. Is it worth backing up the MLC first (64GB card, Format redNAND), or not worth it if the eMMC is probably failing?
3. My plan: enter minute through UDPIH (boot1now.img), dump SLC.RAW plus OTP/SEEPROM, then install ISFShax from there per your guide. Anything specific I should watch for on a console in this state?
4. If it reaches initial setup and then shows 160-0103, is the next step your redNAND-with-ISFShax guide?

SDIO

Well-Known Member

• #4

Skip the erase and delete, we just want to reset the initial launch value.

There is no real value in dumping the MLC. Either it turns out fine or it is bad, in which case you would install a clean one to redNAND anyway.
You can backup the SLC as part of the ISFShax install.

If you run into an issue again, we can then check the log, as it won't be wiped anymore.

Actually: after you installed ISFShax, you can let it boot once to the crash and then dump the sys crash logs in minute. That way you would get the log before it gets wiped again

• #5

Hey SDIO.

Quick sanity check before I install ISFShax.

I dumped SLC.RAW twice via minute (loaded through UDPIH) in two separate sessions with a power cycle between.

OTP was identical and SEEPROM differed by one byte (the RNG seed counter).

SLC.RAW differed in 2,866 of 262,144 pages across 56 blocks (e.g. 1190, 1207, 1218… up to ~4013), mostly whole-page changes, nothing that looks like scattered bit noise.

I assume the partial IOS boot before minute writes to the SLC each time. Is that normal, and is there any reason not to go ahead with the install?

Post automatically merged: Sunday at 8:50 PM

I dumped the SLC.RAW a third time and compared. The pattern from the first two dumps holds, so I'm installing ISFShax now.

Post automatically merged: Monday at 2:02 AM

OK. Things are looking good. Thanks for the guidance SDIO.

So in a "Delete All Content and Settings" scenario, it's good to know there was a work around for it. Since I was wiping out the prior contents, I can't speak to maintaining any of the past data.

Couple of things:

• The empty-wafel_install run worked.
• After ISFShax (4 slots OK) I ran “Dump sys crash logs”, which gave “ERROR opening slc:/sys/logs: 5” (nothing captured).
• wafel_setup_mlc then logged OpenDir/OpenMCP/Flush MLC/Flush SLC: 0, “Region already matches (P:2, G:2, C:2)”, “SetInitialLaunch 0: 1”, and deleted itself.
• The console booted into first-time setup, I finished it and created a user, and it survived a full power cycle. No 160-0103 so far.

Two questions:

• Any eMMC tests anyone would still recommend at this point?
• Is booting without an SD a possibility from here?

Last edited by netbanshee, Monday at 2:02 AM

SDIO

Well-Known Member

• #6

After installing ISFShax, you should have let it boot once more, so it create a log, which you could have then captured with minute, but now it's too late, except if you want to factory reset again.
You can use the NAND Test in the wafel installer to test the eMMC, but it is probably bad.
I mean you can boot without SD at the moment, but in the long run you likely have to use USBMLC or redNAND.