Wii U Stuck on Logo

ChefVortivask

Well-Known Member
Member
Joined
Apr 3, 2023
Messages
374
Reaction score
9
Trophies
1
Age
28
XP
826
Country
United States
Hello everyone,

First time poster here. I decided to make this post since I am having issues with my Wii U. Currently, my Wii U will not boot up to the main menu. It stays stuck on the Wii U logo indefinitely.

There are a few things to note about my console. The console is the black 32 gb model. I believe it was bought during the 2012 holiday season (release) as we were expecting to play Pikmin 3 before it got delayed. The system has never been modded in any fashion. It was not the most heavily played console, and I can't even give a good estimate of when it was last used (at least more than 3 years).

I have already tried doing the UDPIH, however it does not seem to be working. When using the second recovery menu, I get a white screen with some blue lines (see attached image). I believe this is similar to what @fadafwet described in his post. I was able to get the logs from the system, which I have attached to this post. Any idea what the issue may be and how to fix it? Any help would be much appreciated.
 

Attachments

  • Garbled Screen.jpg
    Garbled Screen.jpg
    1.5 MB · Views: 278
  • logs.zip
    logs.zip
    63.9 KB · Views: 167
Uh either the delete has a bug or you installed slc titles and it crashed wwhile installing the OSv10

I would suggest you restore your SLC backup and try again
 
It must be the delete then because I only have the mlc titles in the install folder.

I assume that the slc can be restored via minute? If so, where should I put the file?
Post automatically merged:

It’s SLC.RAW, right?
 
Last edited by ChefVortivask,
really strange, I have no clue what's going on.
Maybe check the SD card on the PC using h2wtest (that will destroy the MLC on it). And if the card is fine, discard/trim it again.
Then use this new fw.img: https://github.com/jan-hofmeier/minute_minute/releases to delete the scfm.img (it's in backup & restore).
Then try the setup again (you don't need to run the destroy)
Oh! unbelievable, you really programmed a patch to delete the SCFM.
My previous comments about chaotic scfm is unfair. I found that change mlc capacity can eliminate data errors.
 
Last edited by Ysecond,
Since I'll be restoring my old slc, I assume that I should also go ahead and install the slc titles like I did back at the start so that the mlc and slc are on the same firmware?
 
Now that you mention it, I don't believe I did. It was getting a little late last night, but I think I only tried it right after I restored SLC.RAW (didn't turn the Wii U off). I'll try it again when I get home, but just for future reference, how do I know when the Wii U needs to be reset in order for changes to take effect?
 
I can't think of another case. Here the file system just needs remounting after the restore. I added that to the minute code now, it will be part of my next release
 
So it looks like you were right about the need to reset. I had to try a couple of times to get past the MLC open attempt, and once it did, I started getting that 131090 error again. After that I decided to try the destroy and setup at the same time, but I ended up getting the scfm error again. Just to rule out the sd card being a problem, I decided to try a different card that had worked in the past. I did destroy and setup on that card, but it got stuck in some kind of loop. I then tried doing setup alone, and got a FAT error that I never got before. I tried once more and got that scfm error again, so it looks to me that the card I was using wasn't necessarily a problem. I've attached several logs of note.

Just so that I'm somewhat on the same page, what exactly is the scfm? Is it stored on the slc or mlc (I would assume mlc since it's been said in the past that it gets detected on the card)?
 

Attachments

I just went back and looked at the log with the 131090 error, and it looks like there's an actual mlc error in there. From what I've read, that would normally indicate a bad mlc, which in this case I guess would indicate a bad micro SD card. I don't know if that's the actual issue though because I really feel that the card is still good. I don't have any proof for that (more of a gut feeling), but it is a good quality card.
 
SCFM is a persistent block level write back cache for the mlc, stored on the slc. The persistent file on the slc is the scfm.img in the root. So if you write something to the mlc it gets first written to the scfm.img on the slc. If the scfm.img is full, data get evicted from it and actually written back to the eMMC / nand-aid sd. (Not that we don't know the exact behavior how it decides what and when to evict and if it will also cache often read blocks or just reads).
So if you restore one without the other, data will become inconsitent, as what is in the cache might not fit to the rest that is on the eMMC.

  • 11723_131090 Error.txt: Timeout errors (131090), means the card became unresponsive, either because the comminication failed or it went into a really bad error state.
  • 11723_scfm error.txt: not exactly sure why scfm is failing as the start of the log is missing
  • Basics Card Attempt.txt: also has 131090 but also 131095 errors. Not sure what 131095 is exactly. I don't have the capacity to look that up rn.
  • FAT Error.txt: ISFS corruption, somehow you corrupted the filesystem of the slc.

If you are still getting the FAT error, you need to restore the SLC.
For me it still looks like the communication between the Wii U and the sd card is unstable.
 
I'm going to try my endurance SD card again (after wiping it clean). I have some ideas of things to try.

As for the FAT error, I really don't know how I could have corrupted the file system of the slc. The only thing I can think of is something went wrong when installing the slc titles, but I'll restore it again if I need to.

I don't know how the communication between the Wii U and SD card could be unstable at this point. I tested every connection with the multimeter and everything looked good. My CLK connection is probably better than it ever was before, CMD looks good, and the resistance values for all for DAT connections looks good, both when I test from the resistors and the vias. Don't misconstrue my words though. I'm not saying you're wrong. You definitely have more experience in this area than me. It's just that if there is still a problem with something regarding the NAND-AID, I have no idea what it could be. The only thing that could be possible is that something is in the slot. I'll find some way to clean it better, hopefully without damaging the pins.
 
I can just say what I see in the logs, and that is that the Wii U has trouble talking to the card. Do you have any wires connected to the pads of the NAND-AID? if so remove them, as they could cause signal reflections if they are too long.
And there is also the option that it is a bad connection with the SD slot. Use tweezers or something like that and try to move each leg to the side to see if it is really soldered
 
I just tried setup again and it failed, but I don't think the slc is the problem, which is good. I was a bit freaked out that the delete scfm I did really messed up the Wii U, but I don't think that's the case. I cleaned the micro SD card using diskpart on Windows, restored the slc.raw, restarted the Wii U, and tried installing the mlc and slc titles, and I got error 2228230. I saw that the error means a faulty eMMC, but in the case of the micro SD card, I'm not sure what it indicates. Perhaps a bad connection? I feel very confident that all 4 DAT connections are solid, so my guess is either CLK or CMD. Considering how much I worked on CLK, it's more likely to be CMD.

I'll take a look at the pins of the slot again, although last time I checked, they all appeared connected. Also there are no wires soldered to the pads of the NAND-AID, so that's not an issue.
 

Attachments

You could get the latest minute release from my GitHub and see if you can dump the SD with the format redNAND option.
If you also get errors there I could make a version which only used one dat line and then we can see if that helps to narrow down the problem
 
I just checked the pins for the SD card slot. None of them wiggle and they all seem to be solid. Also checked with the multimeter and again, everything seems to be fine.

For the latest minute release from Github, I assume your Github is jan-hofmeier and I'm looking for fw.img? If that's the case, is there a difference between fw.img and fw_encrypted.img?
 

Site & Scene News

Popular threads in this forum