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
yeah your pikmin save took same serious damage, sorry abouzt that. Mine did also take damage, but only two of these genX.sav files in my case
 
Of the two games, I'd prefer the Smash Bros. save to be less corrupted because of the trophy collection. Pikmin 3 is unfortunate, but not the end of the world. I'm curious though as to what makes you say the Pikmin 3 save data is more corrupted as opposed to Smash Bros. since everything returned failed to read.
 
for SSBU there are just texture data in the common save corrupted. I assume they can be regenerated. But now that you speak of your trophys I hope these textures aren't the trophys, that would be really unfurtunate (I am not that familiar with SSBU)
 
Ok so with all that established, I think it's safe to proceed with de_fuse. I was following your guide and the first step of the procedure is to backup what I want to preserve. Since I've already done that (at least as best as I probably can at this point), I think I'm ready to proceed.
 
yes. The first goal is to setup defuse 0.7 and see where that brings us. If that's established, we will see where we go from there.
 

Attachments

  • diagram_final.png
    diagram_final.png
    4.5 MB · Views: 48
  • Like
Reactions: lufeig
(I did post it some time ago)
Sorry but we're also just humans, so we can't remember what you posted some weeks ago. Really, really sorry, don't get me wrong, please.

For the rest: Beside what SDIO told there are corruptions at system titles, too. Now I think I remember your name... Did we try to help you in the past already? Again: Don't get me wrong. We'll try to help you again, just want to make sure where we are at.
 
  • Like
Reactions: RetroGen
I started this thread a couple of months ago so you have been helping me for some time now.
Post automatically merged:

dodnt worry about the downloader for now. Just setup defuse. Defuse isn't explained in the tutorial, it just links you to the nandaid github
Post automatically merged:

Here is how you would need to wire up the pico: https://github.com/shinyquagsire23/wii_u_modchip/tree/main/pico_defuse
I should have asked this yesterday, but since I am deviating from the written procedure a little bit, I just want to make sure I don't miss anything. I'm going to just set up de_fuse now which means wiring up the pico as indicated. Do I or should I flash anything to the pico first before wiring it up, or can this be done after the fact? According to the guide and the link provided, the pico should be flashed with pico_defuse.uf2
 
Last edited by ChefVortivask,
Doesn't matter when you flash it. But flashing first could avoid problems depending on what the old rom is doing. So I would flash it first, but if you have it already soldered you can also flash it after.
 
I finally got around to wiring up the pico. I also flashed the pico with de_fuse before wiring it up. I think I'm going to double check the wiring, but what should my next step be? You said not to worry about the downloader, but do I need boot1.img? If so, it seems I can get away with a 1 gb card.
 

Attachments

  • IMG_9323.jpg
    IMG_9323.jpg
    2.9 MB · Views: 45
I wouldn't wire up the 3V3, as the pico will get it's power from the PC.
Also make sure you put the heatsink back on.
And yes you need to flash the boot1.img to your 1GB sdcard and then format (after removing and reinserting)it and place the minute fw.img on it and the wii u folder with the ios_plugins.
 
The boot1.img is 64KB. The first partition starts after 64MB. Therefore the boot1.img can't contain the filesystem.

EDIT: it even says so in the readme
boot1.img includes an MBR header, so you may have to format the FAT32 partition after flashing in order to continue.
meaning if the partition defined in that header doesn't line up with the partition that was already there, you have to format.
 
It has the partition in the MBR, but not the file system on that partition. It's physically impossible as it would be outside the image.
 
So how was I able to completely null a card, then put the boot1 image on it and use the FAT partition without formatting it? Also why am I able to loop-mount the boot1 image on my Linux system?
Code:
cat boot1.img /dev/zero > foo.img
^C
mounting that foo.img:
Code:
[139560.756472] loop0: detected capacity change from 0 to 2898240
[139560.792738]  loop0: p1
fscking that:
Code:
# fsck.vfat /dev/loop0p1
fsck.fat 4.2 (2021-01-31)
...
 
Maybe your fsck is broken
Code:
$ cat boot1.img /dev/zero > foo.img
^C
$ sudo kpartx -a foo.img
$ sudo kpartx  foo.img 
loop21p1 : 0 1851392 /dev/loop21 131072
$ sudo fsck.vfat /dev/mapper/loop21p1 
fsck.fat 4.2 (2021-01-31)
Logical sector size is zero.
my fsck works and reports as expected that the sector size field is zero (because it was read from /dev/zero)
Or maybe you have a different boot1.img, I used that from the lates de_Fuse_v0.7.1, which is only 64KiB in size.

You can even see that the partition starts outside the 64KiB of the boot1.img

Code:
$ parted foo.img  
foo.img wird verwendet
Willkommen zu GNU Parted! Rufen Sie »help« auf, um eine Liste der verfügbaren Befehle zu erhalten.
(parted) p                                                                
Modell:  (file)
Festplatte  /home/jan/Downloads/de_Fuse_v0.7.1/foo.img:  2317MB
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: msdos
Disk-Flags:  

Nummer  Anfang  Ende    Größe  Typ      Dateisystem  Flags
 1      67,1MB  1015MB  948MB  primary
 
I removed the 3V3 wire, used Win32DiskImager to write boot1.img to the SD card (I didn't realize there was a more recent release of de_Fuse, so I used the one from v0.5.1; not sure if this matters), and then removed the card and reinserted. Upon insertion, I was prompted to format the card, so I did. Formatted to fat32, and then I copied over fw.img and the wiiu folder from de_Fuse v0.7.1. I also copied over the otp.bin file I had from my original nand dump. Not sure if the file is still good.

I just downloaded and installed PuTTY since I intend to use Windows for the time being. I don't believe I've ever used a program like PuTTY, but if I understand correctly, once I plug the pico into my computer, I should try to connect via serial.

What is my next step, specifically what am I aiming to accomplish with de_Fuse? I think we had mentioned trying to find exactly where UDPIH was failing, but I'm not entirely sure the plan.
 

Site & Scene News

Popular threads in this forum