Wii U Stuck on Logo

ChefVortivask · Apr 4, 2023

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.

SDIO · May 29, 2023

Code:

def FSA_RemoveQuota(self, handle, path):
  inbuffer = buffer(0x520)
  copy_string(inbuffer, path, 0x04)
  (ret, _) = self.ioctl(handle, 0x72, inbuffer, 0x293)
  return ret

You could try adding this to the wupclient class. For example after the FSA_Remove function.
Make sure the indentation is correct.
But I haven't tested it yet. So try it at your own risk

axmccx · May 29, 2023

Awesome, thanks! I'll give it shot later tonight or tomorrow! So the `handle` is the w.fsa_handle, and a path to try would be `/vol/storage_mlc01/usr/save/00050000/10102000/user/` ?

Post automatically merged: May 29, 2023

I've written this wrapper function for it:

Python:

    def remove_quota(self, path):
        if path[0] != "/":
            path = self.cwd + "/" + path
        ret = self.FSA_RemoveQuota(self.fsa_handle, path)
        if ret == 0x0:
            print("remove_quota error : could not open " + path + " (" + hex(ret) + ")")
        else:
            print("remove_quota : " + hex(ret))

I haven't tried it yet, but will tomorrow morning. Spent the evening playing Nintendo Land. Man, the Wii U is actually so underrated.

V10lator · May 29, 2023

axmccx said:
Awesome, thanks! I'll give it shot later tonight or tomorrow! So the `handle` is the w.fsa_handle, and a path to try would be `/vol/storage_mlc01/usr/save/00050000/10102000/user/` ?

Post automatically merged: May 29, 2023

I've written this wrapper function for it:

Python:

def remove_quota(self, path): if path[0] != "/": path = self.cwd + "/" + path ret = self.FSA_RemoveQuota(self.fsa_handle, path) if ret == 0x0: print("remove_quota error : could not open " + path + " (" + hex(ret) + ")") else: print("remove_quota : " + hex(ret))

I haven't tried it yet, but will tomorrow morning. Spent the evening playing Nintendo Land. Man, the Wii U is actually so underrated.

There's a small mistake inside. Try this one instead (mistake fixed + confirmation added - also strings are a bit differently as I wrote this before seeing your version) :

Code:

    def remove_quota(self, path):
        if path[0] != "/":
            path = self.cwd + "/" + path
        print("WARNING: REMOVING A QUOTA CAN BRICK YOUR CONSOLE, ARE YOU SURE (Y/N)?")
        if self.askyesno() == True:
            ret = self.FSA_RemoveQuota(self.fsa_handle, path)
            if ret == 0x0:
                print("removed quota at " + path)
            else:
                print("removing quota at " + path + " failed : " + hex(ret))
        else:
            print("quota removing aborted")

With this do w.remove_quota("/vol/storage_mlc01/usr/save/00050000/10102000/user/corrupted/common"), w.remove_quota("/vol/storage_mlc01/usr/save/00050000/10102300/user/corrupted/common") and w.remove_quota("/vol/storage_mlc01/usr/save/00050010/1004d100/user/corrupted/80000006"). With a bit of luck this will completely delete these folders, so you should be able to delete the 3 parent folders called "corrupted" afterwards and your issue should be gone.

Note that I say with a bit of luck as I don't have a way to test this on corrupted quota folders, all I tested it on was with the savefile of a game on my USB drive, looked like this:

Code:

w.cd("/vol/storage_usb01/usr/save/00050000/1010ed00")
>>> w.ls()
     meta/
     user/
>>> w.remove_quota("meta")
WARNING: REMOVING A QUOTA CAN BRICK YOUR CONSOLE, ARE YOU SURE (Y/N)?
y
removed quota at /vol/storage_usb01/usr/save/00050000/1010ed00/meta
>>> w.ls()
     user/

//EDIT: My codes are btw written against (with the FSA_RemoveQuota codes from SDIO added).

//EDIT²: In case you can't see the little mistake:

Code:

        if ret == 0x0:
            print("remove_quota error : could not open " + path + " (" + hex(ret) + ")")
        else:
            print("remove_quota : " + hex(ret))

The if/else is wrongly ordered. If ret == 0x0 it worked, else it failed and you should print out the ret code in hex (as we're able to map these codes to error descriptions to see why it failed).

axmccx · May 29, 2023

V10lator said:
The if/else is wrongly ordered

Oh nice catch, thanks for that!

So I updated my wupclient, and tried running:

Code:

w.remove_quota("/vol/storage_mlc01/usr/save/00050000/10102000/user/common")
w.remove_quota("/vol/storage_mlc01/usr/save/00050000/10102000/user/")
w.remove_quota("/vol/storage_mlc01/usr/save/00050000/10102000/")

and they all failed. But then I listed the contents of "/vol/storage_mlc01/usr/save/00050000/10102000/" using my directory traversal class again, and some new files and folders appears, notably the 80000011, and common/save.dat??

Code:

cd /vol/storage_mlc01/usr/save/00050000/10102000
cd /vol/storage_mlc01/usr/save/00050000/10102000/meta
File: /vol/storage_mlc01/usr/save/00050000/10102000/meta/iconTex.tga
File: /vol/storage_mlc01/usr/save/00050000/10102000/meta/meta.xml
File: /vol/storage_mlc01/usr/save/00050000/10102000/meta/saveinfo.xml
cd /vol/storage_mlc01/usr/save/00050000/10102000/user
cd /vol/storage_mlc01/usr/save/00050000/10102000/user/80000011
cd /vol/storage_mlc01/usr/save/00050000/10102000/user/common
File: /vol/storage_mlc01/usr/save/00050000/10102000/user/common/save.dat
cd /vol/storage_mlc01/usr/save/00050000/10102000/user/corrupted
cd /vol/storage_mlc01/usr/save/00050000/10102000/user/corrupted/common
cd error : path does not exist (/vol/storage_mlc01/usr/save/00050000/10102000/user/corrupted/common)

I lost track of what I did after, I may have tried removing some directories, or clearing the quota on `/vol/storage_mlc01/usr/save/00050000/10102000/user/common`, but they're no longer showing now.

It seems to me that something's been unlinked to the `/vol/storage_mlc01/usr/save/00050000/10102000/user/common/`. Like there's a "pointer" from /vol/storage_mlc01/usr/save/00050000/10102000/user/corrupted/ to common, but it's not really there, and still in /vol/storage_mlc01/usr/save/00050000/10102000/user/common.

I tried moving all directories in the `/vol/storage_mlc01/usr/save/00050000/10102000/user/corrupted/common` path to `/vol/storage_mlc01/x_corrupt/` with no success. I also tried moving `/vol/storage_mlc01/usr/save/00050000/10102000/user/corrupted` to any of its parents with no sucess.

I also tried clearing the quota on

Code:

/vol/storage_mlc01/usr/save/00050000/10102300/user/corrupted/common
/vol/storage_mlc01/usr/save/00050010/1004d100/user/corrupted/80000006

but both get the error: 0xfffcffe5. I'll have a look again after work. The console is still booting up fine.

SDIO · May 29, 2023

try creating a folder /vol/storage_mlc01/usr/save/corrupted and then try to move /vol/storage_mlc01/usr/save/00050000/10102000/ there.

V10lator · May 29, 2023

axmccx said:
get the error: 0xfffcffe5

This error means FS_ERROR_DATA_CORRUPTED, so looks like we can't remove corrupted quota folders.

Anyway, try what SDIO suggested, please.

Did you by any chance started Nintendo land so it just created a new save?

Beside that please don't try things blindly, messing with the filesystem does have a brick risk.

axmccx · May 29, 2023

SDIO said:
try creating a folder /vol/storage_mlc01/usr/save/corrupted and then try to move /vol/storage_mlc01/usr/save/00050000/10102000/ there.

Unfortunately, I get:
`moving /vol/storage_mlc01/usr/save/00050000/10102000/ to /vol/storage_mlc01/usr/save/corrupted failed : 0xfffcffea`

V10lator said:
This error means FS_ERROR_DATA_CORRUPTED, so looks like we can't remove corrupted quota folders.

It's unfortunate, but not the worst thing. I installed a few games last night, then I realize that I can't delete title in the UI since I can't open the data manager in settings. I suppose I can use wupclient instead to delete titles from my nand?

V10lator said:
Did you by any chance started Nintendo land so it just created a new save?

Yup, it created a save, everything loads and plays great.

V10lator said:
Beside that please don't try things blindly, messing with the filesystem does have a brick risk.

Understood. Wouldn't it be possible to restore my latest eMMC image if I do manage to brick it? I've been taking the eMMC replacement SD card out, and taking an image with Win32DiskImager.

SDIO · May 29, 2023

axmccx said:
Wouldn't it be possible to restore my latest eMMC image if I do manage to brick it? I've been taking the eMMC replacement SD card out, and taking an image with Win32DiskImager.

No, because that wouldn't match whats in the cache on the SLC. You would either have to restore both the SLC and the MLC or use a MLC backup done with FSA and flash it back through FSA. For the latter you would still need to be able to boot to the recovery and it takes an eternity.

Can you try what happens if you set the permissions of that corrupted folder to 000?

V10lator · May 29, 2023

axmccx said:
`moving /vol/storage_mlc01/usr/save/00050000/10102000/ to /vol/storage_mlc01/usr/save/corrupted failed : 0xfffcffea`

FS_ERROR_ALREADY_EXISTS, so try adding a slash, like this: w.mv("/vol/storage_mlc01/usr/save/00050000/10102000", "/vol/storage_mlc01/usr/save/corrupted/") or maybe w.mv("/vol/storage_mlc01/usr/save/00050000/10102000", "/vol/storage_mlc01/usr/save/corrupted/001")

axmccx said:
I suppose I can use wupclient instead to delete titles from my nand?

It should work but maybe it also tries to delete the corresponding saves.

axmccx said:
Wouldn't it be possible to restore my latest eMMC image if I do manage to brick it?

Not without a matching SLC backup and this you're missing by reading the SD card out.

axmccx · May 29, 2023

Couldn't help to try during my lunch break...

This didn't work:
w.mv("/vol/storage_mlc01/usr/save/00050000/10102000", "/vol/storage_mlc01/usr/save/corrupted/")

But this did!!!

w.mv("/vol/storage_mlc01/usr/save/00050000/10102000", "/vol/storage_mlc01/usr/save/corrupted/001"

I see what happened, and I feel pretty dumb... I think the problem this whole time: I was creating the destination folder before moving. This time I tried moving it without making the "/vol/storage_mlc01/usr/save/corrupted/001" folder.

I was then able to move it to `/vol/storage_mlc01/x_corrupt/001`
and I also successful with the two following moves:

w.mv("/vol/storage_mlc01/usr/save/00050000/10102300", "/vol/storage_mlc01/x_corrupt/002/")
w.mv("/vol/storage_mlc01/usr/save/00050010/1004d100", "/vol/storage_mlc01/x_corrupt/003/")

SDIO · May 29, 2023

does the data management work now?

axmccx · May 29, 2023

SDIO said:
does the data management work now?

Running a mlc_checker now just to be sure. I'll check the data management once it's done. Seems to be taking longer now that I've installed some games.

Post automatically merged: May 29, 2023

Finally finished and looks the corrupted directories are out of the save directory!!

SDIO said:
does the data management work now?

but it's still hanging at the `Preparing...` screen.

Maybe later today I'll try uninstalling those titles using wupclient? or maybe reinstalling them? I see now that `00050000/10102000` was Nintendo Land, my bad, I didn't realize that's why you asked, interesting how the game and saving worked last night. I supposed I lost the save for now, but all good, one night of play lol. The others are Wii Fit U and Notifications.

Post automatically merged: May 29, 2023

SUCCESS!!! I went back in, using wupclient I deleted a bunch of titles and saves that were there from the previous owner. I also reinstalled the Notifications title, 00050010-1004D100, and I can load the Data Management now!!!

Freaking awesome, @SDIO, @V10lator, once again, thank you so much for all your help.

ChefVortivask · Jun 1, 2023

Just wanted to give an update. I successfully soldered the ground connection for the NAND-AID. I didn't need to use hot air. I plan on detailing what I did later or on the NAND-AID thread.

I finished the rest of the connections and tested them with a multimeter. I just wanted to have someone double check my installation (particularly the 3V3 wire) and see if it looks good to go.

Edit: Is it important for the 3V3 wire to not be running over the gold plane next the the ribbon cable connector? If so, I can easily tape it out of the way.

SDIO · Jun 2, 2023

Looks good to me. With the 3V3 you just to have to be careful to not short on any of the VIAs near the the transistor. But from the picture it looks good.

ChefVortivask · Jun 2, 2023

It looks good to me too. I kept the vias in mind and tried keeping the exposed wire as short as possible.

SDIO · Jun 2, 2023

then give it a try

ChefVortivask · Jun 3, 2023

I just tested out the console. When I try to power on, the light turns blue for a second and then blinks red. No picture on the TV. Any idea what might be happening?

Lazr1026 · Jun 3, 2023

disc drive plugged in wrong, you need to flip around the ribbon cable most likely

SDIO · Jun 3, 2023

Thats strage. If it were a mlc problem the LED should just stay blue. Red blinking means something more basic is failing.
Did you unplug any of the wifi or bluetooth adapters?
Can you check if any of the signals for the mlc are shorted toghether or to gnd? Especially the CLK on the SD slot. CLK is the 4th pin from the right.

Post automatically merged: Jun 3, 2023

I wouldn't plug in the Disc Drive at all at this Stage. Only plug it in when we get to the point where the Wii U throws an error and demands it.

ChefVortivask · Jun 3, 2023

It very well could be the disc drive. As for checking for shorts, I was pretty thorough with my multimeter. Let me take a look at the disc drive first before I check for shorts again.

Edit: Should I unplug the ribbon cable from both the disc drive and the board, flip it around, and then plug it back into both. I did unplug it from the drive to check something and lost grip of it, so it very well could be in backwards.

Wii U Stuck on Logo

Well-Known Member

Attachments

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Member

Attachments

Well-Known Member

Attachments

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum