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
That’s actually very possible. I’ll clear it up and try again.
Post automatically merged:

I tried again with more space and it all seemed to be going good. It looks like it was able to backup both the slc and slccmpt, however towards the end of initializing slccmpt, it all of a sudden just started spitting out "mlc: READ: no card inserted.". The only thing I can recover from that log is that one line. I looked away for a couple of seconds and when I looked up, it was spitting that out.
 
Last edited by ChefVortivask,
where did you get that message? In minute? That does not need to mean anything if you have an older minute. I added sd mlc support to minute in my repo and it is not yet merged back
 
That message was from minute (log in PuTTY). I used the version of minute (fw.img) that was new a week or two ago. I’ll take a look at the new minute.
Post automatically merged:

What do you mean by it’s not yet merged back? I’m assuming the new version of minute? I’m not that familiar with all the details of GitHub.
 
That’s the version of minute I used. If I remember everything correctly, setup was not working so I tried format redNAND like you suggested (I’m not sure if the micro SD was formatted or not since setup failed). I had it back up the slc and slccmpt, which had a couple of errors, and then it started spitting out no card detected. I think I’m going to try again.

Does that make sense?
 
Minute doesn't care for the MLC format, it just copies the raw sectors.
Can you show the output from minute before it shows the menu? You should be able to just scroll up a little bit (there will be lots of blank before the menu)
 
  • Like
Reactions: ChefVortivask
When de_Fuse is starting up? I can do that when I get home. You may be onto something though because the last several times I booted into minute, I thought it looked a bit different, but I wasn’t totally sure and didn’t pay much attention to it. I just assumed that as long as the pico was wired up properly, I would always get into the menu, and if I couldn’t get into the menu, something would be wrong with the pico (assuming the menu file itself was alright).
Post automatically merged:

It definitely looks different than I remember. I noticed an error while mounting mlc.
 

Attachments

Last edited by ChefVortivask,
OK the mlc sd gets initally detected and also responds to everything until the clock gets ramped up to 25Mhz, then the things fall apart.
Can you put another SD in the NAND-AID and see if it behaves differently, just to see if that is not just an incompatibility between minute and the SD?
 
Ok interesting, it failed on the send status again, even on the lower clock.
Could still be the soldering, I don't have a better explaination
 
I’ll go through systematically then and reflow the joints until hopefully the issue is fixed. It’s just odd that the multimeter seems to indicate that all the joints are fine.

I feel confident that the SD slot is fine so I’ll leave that for last in case nothing else works. I also feel that the CLK connection is good, partly because I put so much effort into it, but also because the card does seem to come up consistently. I’m not sure if the CLK signal alone is responsible for that detection though.

I’ll start from CMD and go from there.
 
I can try that if all else fails. I don’t see how it could be though since it should be disabled. Not only was the CLK trace cut, but now that pad on the eMMC side is gone (unfortunately). The CMD resistor as well as the pad on the eMMC side is also gone.

Do you think that the fact that the CLK connection for the eMMC is no longer shorted to GND could be an issue? Also I forgot to ask this earlier, but given the current state of my install, does the DIS jumper have any significance?
 

Site & Scene News

Popular threads in this forum