Wii U Stuck on Logo

ChefVortivask

Well-Known Member
OP
Member
Joined
Apr 3, 2023
Messages
339
Trophies
0
Age
26
XP
540
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: 92
  • logs.zip
    63.9 KB · Views: 84

SDIO

Well-Known Member
Member
Joined
Feb 13, 2023
Messages
2,268
Trophies
0
Age
28
XP
1,386
Country
Germany
It doesn't seem to produce logs anymore. The last one is from 2015 and you were playing Super Smash Bros. for Wii U.
Can you try to dump OTP blindly?

After you have dumped otp put the attached recovery (rename to recovery_menu) on a 64GB sdcard. Start it through UDPIH, the led should be purple, even if the screen doesn't change. Press power and wait a minute, the LED should flicker yellow. When it is done it will go back to purple. You should then find a mlc.log file on the SD please upload that and keep the generated backup somewhere safe, in case you need it.
 

Attachments

  • recovery_menu_dumper.zip
    17.5 KB · Views: 74
  • Like
Reactions: godreborn

marcellomls

Member
Newcomer
Joined
Apr 4, 2023
Messages
10
Trophies
0
Age
41
XP
63
Country
Brazil
First try to get

First try to get otp, then logs and then run my dumper.
My log contains information like this:

00:00:07:259: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050030/10017109/code/app.xml
I have a problem with the nand?
 

osaka35

Instructional Designer
Global Moderator
Joined
Nov 20, 2009
Messages
3,744
Trophies
2
Location
Silent Hill
XP
5,976
Country
United States
Just to add, there is a common problem cropping up that may be related to your issue. For whatever reason, the home menu is getting corrupted on Wii Us. If you can reinstall the home menu, it might fix your issue. not sure what guides are out there, just wanted to raise a potential course of action...if that isn't what y'all have already been talking about. I'm only vaguely aware of the specifics.
 
  • Like
Reactions: Subtle Demise

godreborn

Welcome to the Machine
Member
Joined
Oct 10, 2009
Messages
38,471
Trophies
3
XP
29,138
Country
United States
Just to add, there is a common problem cropping up that may be related to your issue. For whatever reason, the home menu is getting corrupted on Wii Us. If you can reinstall the home menu, it might fix your issue. not sure what guides are out there, just wanted to raise a potential course of action...if that isn't what y'all have already been talking about. I'm only vaguely aware of the specifics.
The home menu will be the first one listed in the mlc, though title id differs based on region.
 
  • Like
Reactions: osaka35

marcellomls

Member
Newcomer
Joined
Apr 4, 2023
Messages
10
Trophies
0
Age
41
XP
63
Country
Brazil
Just to add, there is a common problem cropping up that may be related to your issue. For whatever reason, the home menu is getting corrupted on Wii Us. If you can reinstall the home menu, it might fix your issue. not sure what guides are out there, just wanted to raise a potential course of action...if that isn't what y'all have already been talking about. I'm only vaguely aware of the specifics.
But how do I install the menu if my wiiu (USA Version) is stuck on the home screen?

UDPIH and recovery_menu with raspery pi dont work for me :(
 
  • Like
Reactions: osaka35

SDIO

Well-Known Member
Member
Joined
Feb 13, 2023
Messages
2,268
Trophies
0
Age
28
XP
1,386
Country
Germany
The recovery menu works obviousl, or else you wouldn't have the logs. You just don't see it but we can tell you which buttons to press.
We know this file of the system menu is corrupted but we don't know why. It could be bad eMMC but it doesn't need to be.
Could you check the logs for MEDIA ERROR and mmc messages?
Also I would recommend running the dumper just in case something goes more wrong. It will also give you a picture of the health of the eMMC through the log
 
  • Like
Reactions: osaka35

marcellomls

Member
Newcomer
Joined
Apr 4, 2023
Messages
10
Trophies
0
Age
41
XP
63
Country
Brazil
The recovery menu works obviousl, or else you wouldn't have the logs. You just don't see it but we can tell you which buttons to press.
We know this file of the system menu is corrupted but we don't know why. It could be bad eMMC but it doesn't need to be.
Could you check the logs for MEDIA ERROR and mmc messages?
Also I would recommend running the dumper just in case something goes more wrong. It will also give you a picture of the health of the eMMC through the log

In my log I have 40 .log and .dsc files, have 1 meta.bin file, this is part of the 38.log file content:

Title Id Process Id -> RM Path
00:00:08:928: IFNET_ETH: Link DOWN.
00:00:10:673: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path: null)
00:00:13:486: Acquired IP address via DHCP client for interface: wl0
00:00:13:487: IP address : 192.168.15.10
00:00:13:487: Subnet Mask: 255.255.255.0
00:00:13:487: Gateway : 192.168.15.1
00:00:13:681: MCP: life time number of fatal errors - 37
 
Last edited by marcellomls,

ChefVortivask

Well-Known Member
OP
Member
Joined
Apr 3, 2023
Messages
339
Trophies
0
Age
26
XP
540
Country
United States
It doesn't seem to produce logs anymore. The last one is from 2015 and you were playing Super Smash Bros. for Wii U.
Can you try to dump OTP blindly?

After you have dumped otp put the attached recovery (rename to recovery_menu) on a 64GB sdcard. Start it through UDPIH, the led should be purple, even if the screen doesn't change. Press power and wait a minute, the LED should flicker yellow. When it is done it will go back to purple. You should then find a mlc.log file on the SD please upload that and keep the generated backup somewhere safe, in case you need it.
I just ordered a couple of 64 gb micro SD cards. I can try what you suggested tomorrow. Thank you for the guidance!

Edit: By the way, what exactly is OTP and what are we trying to do with the mlc.log file?
 
Last edited by ChefVortivask,

SDIO

Well-Known Member
Member
Joined
Feb 13, 2023
Messages
2,268
Trophies
0
Age
28
XP
1,386
Country
Germany
@marcellomls

Code:
00:02:33:979: UHS0 Trace: DevFsm(EHCI-0/L1/P1): Creating device, speed=HIGH.tered on core 1.
36.log:00:00:05:261: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/00050010/10049100/code/app.xml
36.log:00:00:05:313: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/00050010/1004c100/code/app.xml
36.log:00:00:07:012: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
36.log:00:00:07:105: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
36.log:00:00:07:248: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050030/10017109/code/app.xml
36.log:00:00:10:515: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
37.log:00:00:02:636: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/00050010/10049100/code/app.xml
37.log:00:00:03:326: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/00050010/1004c100/code/app.xml
37.log:00:00:07:127: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
00:00:07:970: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
37.log:00:00:08:117: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050030/10017109/code/app.xml
38.log:00:00:01:414: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/00050010/10049100/code/app.xml
38.log:00:00:01:466: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/00050010/1004c100/code/app.xml
38.log:00:00:08:598: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/0005001b/10065000/code/app.xml
38.log:00:00:08:610: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/0005001b/10042400/content/CafeCn.ttf
38.log:00:00:10:673: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
39.log:00:00:05:210: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050010/10049100/code/app.xml
39.log:00:00:05:239: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050010/1004c100/code/app.xml
39.log:00:00:07:048: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
39.log:00:00:07:133: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
39.log:00:00:07:259: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050030/10017109/code/app.xml
39.log:00:00:10:526: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
40.log:00:00:02:600: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050010/10049100/code/app.xml
40.log:00:00:03:465: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050010/1004c100/code/app.xml
40.log:00:00:03:791: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
40.log:00:00:05:019: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
40.log:00:00:07:166: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
so yeah the data corruption is caused by MEDIA ERRORS, meaning the eMMC is reporting, that it can't read the data anymore -> bad emmc.

Also there are more files damaged (from 40.log):
Code:
00:00:05:019: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
00:00:05:364: mmc_core card err: idx=3, lba=55263232, blks=1024, xfer=0x1, ret=0x00200b40
00:00:05:524: mmc_core card err: idx=3, lba=55263232, blks=1024, xfer=0x1, ret=0x00200b40
00:00:05:524: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:05:781: mmc_core card err: idx=3, lba=55264256, blks=1024, xfer=0x1, ret=0x00200b40
00:00:06:050: mmc_core card err: idx=3, lba=55264256, blks=1024, xfer=0x1, ret=0x00200b40
00:00:06:050: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:06:301: mmc_core card err: idx=3, lba=55265280, blks=1024, xfer=0x1, ret=0x00200b40
00:00:06:559: mmc_core card err: idx=3, lba=55265280, blks=1024, xfer=0x1, ret=0x00200b40
00:00:06:560: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:06:722: mmc_core card err: idx=3, lba=55266304, blks=1024, xfer=0x1, ret=0x00200b40
00:00:06:893: mmc_core card err: idx=3, lba=55266304, blks=1024, xfer=0x1, ret=0x00200b40
00:00:06:893: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:07:022: mmc_core card err: idx=3, lba=55267328, blks=640, xfer=0x1, ret=0x00200b40
00:00:07:165: mmc_core card err: idx=3, lba=55267328, blks=640, xfer=0x1, ret=0x00200b40
00:00:07:165: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:07:166: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
00:00:07:166: failed to read file /vol/storage_mlc01/sys/title/0005001b/10042400/content/CafeStd.ttf, err -196673
00;00;07;046: ***LoadShared - WaitLoadComplete(0,2442464) failed with error -196673 on file "CafeStd.ttf".
The eMMC is also a Hynix, they are known to fail.

My recommendation is to run the dumper, then turn the Wii U off and only turn it on again after replacing the eMMC.
Post automatically merged:

I just ordered a couple of 64 gb micro SD cards. I can try what you suggested tomorrow. Thank you for the guidance!

Edit: By the way, what exactly is OTP and what are we trying to do with the mlc.log file?
OTP holds the keys for your console. It allows us to decrypt the dump on the PC. The mlc.log will tell us the state of the eMMC. How many errors the dumper encountered. It also contains the Manufacturer and the Manufacturing date of the eMMC.
 
  • Like
Reactions: Subtle Demise

marcellomls

Member
Newcomer
Joined
Apr 4, 2023
Messages
10
Trophies
0
Age
41
XP
63
Country
Brazil
@marcellomls

Code:
00:02:33:979: UHS0 Trace: DevFsm(EHCI-0/L1/P1): Creating device, speed=HIGH.tered on core 1.
36.log:00:00:05:261: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/00050010/10049100/code/app.xml
36.log:00:00:05:313: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/00050010/1004c100/code/app.xml
36.log:00:00:07:012: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
36.log:00:00:07:105: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
36.log:00:00:07:248: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050030/10017109/code/app.xml
36.log:00:00:10:515: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
37.log:00:00:02:636: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/00050010/10049100/code/app.xml
37.log:00:00:03:326: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/00050010/1004c100/code/app.xml
37.log:00:00:07:127: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
00:00:07:970: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
37.log:00:00:08:117: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050030/10017109/code/app.xml
38.log:00:00:01:414: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/00050010/10049100/code/app.xml
38.log:00:00:01:466: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/00050010/1004c100/code/app.xml
38.log:00:00:08:598: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/0005001b/10065000/code/app.xml
38.log:00:00:08:610: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:25, path:/sys/title/0005001b/10042400/content/CafeCn.ttf
38.log:00:00:10:673: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
39.log:00:00:05:210: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050010/10049100/code/app.xml
39.log:00:00:05:239: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050010/1004c100/code/app.xml
39.log:00:00:07:048: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
39.log:00:00:07:133: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
39.log:00:00:07:259: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050030/10017109/code/app.xml
39.log:00:00:10:526: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
40.log:00:00:02:600: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050010/10049100/code/app.xml
40.log:00:00:03:465: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:25, path:/sys/title/00050010/1004c100/code/app.xml
40.log:00:00:03:791: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
40.log:00:00:05:019: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
40.log:00:00:07:166: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
so yeah the data corruption is caused by MEDIA ERRORS, meaning the eMMC is reporting, that it can't read the data anymore -> bad emmc.

Also there are more files damaged (from 40.log):
Code:
00:00:05:019: FSA: ### DATA CORRUPTION ERROR ###, dev:mlc01, err:-1245211, cmd:11, path:(null)
00:00:05:364: mmc_core card err: idx=3, lba=55263232, blks=1024, xfer=0x1, ret=0x00200b40
00:00:05:524: mmc_core card err: idx=3, lba=55263232, blks=1024, xfer=0x1, ret=0x00200b40
00:00:05:524: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:05:781: mmc_core card err: idx=3, lba=55264256, blks=1024, xfer=0x1, ret=0x00200b40
00:00:06:050: mmc_core card err: idx=3, lba=55264256, blks=1024, xfer=0x1, ret=0x00200b40
00:00:06:050: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:06:301: mmc_core card err: idx=3, lba=55265280, blks=1024, xfer=0x1, ret=0x00200b40
00:00:06:559: mmc_core card err: idx=3, lba=55265280, blks=1024, xfer=0x1, ret=0x00200b40
00:00:06:560: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:06:722: mmc_core card err: idx=3, lba=55266304, blks=1024, xfer=0x1, ret=0x00200b40
00:00:06:893: mmc_core card err: idx=3, lba=55266304, blks=1024, xfer=0x1, ret=0x00200b40
00:00:06:893: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:07:022: mmc_core card err: idx=3, lba=55267328, blks=640, xfer=0x1, ret=0x00200b40
00:00:07:165: mmc_core card err: idx=3, lba=55267328, blks=640, xfer=0x1, ret=0x00200b40
00:00:07:165: mdblk: err=-131099, mid=0x90, prv=0x5c, pnm=[HYNIX ]
00:00:07:166: FSA: ### MEDIA ERROR ###, dev:mlc01, err:-2228230, cmd:11, path:(null)
00:00:07:166: failed to read file /vol/storage_mlc01/sys/title/0005001b/10042400/content/CafeStd.ttf, err -196673
00;00;07;046: ***LoadShared - WaitLoadComplete(0,2442464) failed with error -196673 on file "CafeStd.ttf".
The eMMC is also a Hynix, they are known to fail.

My recommendation is to run the dumper, then turn the Wii U off and only turn it on again after replacing the eMMC.
Post automatically merged:


OTP holds the keys for your console. It allows us to decrypt the dump on the PC. The mlc.log will tell us the state of the eMMC. How many errors the dumper encountered. It also contains the Manufacturer and the Manufacturing date of the eMMC.

don't have a backup of the nand, with this dump will it be possible to recover the system by changing the nand?
 

SDIO

Well-Known Member
Member
Joined
Feb 13, 2023
Messages
2,268
Trophies
0
Age
28
XP
1,386
Country
Germany
The backup isn't strictly necessary as you could just read out the eMMC and clone it to the new media, and that would also be the recommended way. But the backup gives us a chance in case thing deteriorate further. Also we could analyze it on the PC to see which other files are broken.

Here you can find more info about that problem: https://gbatemp.net/threads/how-i-fixed-160-0103-system-memory-error.626448/

@Voultar is working on a board, which makes the replacement much easier: https://gbatemp.net/threads/how-i-fixed-160-0103-system-memory-error.626448/post-10115383 you might want to wait for this.
 

ChefVortivask

Well-Known Member
OP
Member
Joined
Apr 3, 2023
Messages
339
Trophies
0
Age
26
XP
540
Country
United States
It doesn't seem to produce logs anymore. The last one is from 2015 and you were playing Super Smash Bros. for Wii U.
Can you try to dump OTP blindly?

After you have dumped otp put the attached recovery (rename to recovery_menu) on a 64GB sdcard. Start it through UDPIH, the led should be purple, even if the screen doesn't change. Press power and wait a minute, the LED should flicker yellow. When it is done it will go back to purple. You should then find a mlc.log file on the SD please upload that and keep the generated backup somewhere safe, in case you need it.
I did as you instructed. I turned off my Wii U when the light was going back and forth between blue and yellow. I have mlc.log, but it looks like there is nothing there.
 

ChefVortivask

Well-Known Member
OP
Member
Joined
Apr 3, 2023
Messages
339
Trophies
0
Age
26
XP
540
Country
United States
My mistake. It had gone on for so long that I assumed that the light switching back and forth meant it was done. I have it going right now and it has been dumping for more than an hour. On average, how long does this usually take?
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
  • Mondooooo @ Mondooooo:
    wth is that?
  • bernard_kekette @ bernard_kekette:
    A version of ModMii
  • Mondooooo @ Mondooooo:
    and what is ModMii
  • bernard_kekette @ bernard_kekette:
    a tool to install WADs on the Wii
  • Mondooooo @ Mondooooo:
    nice
  • BakerMan @ BakerMan:
    WELCOME TO WARIO WORLD THE UNDERGROUND GBATEMP
    +2
  • Mondooooo @ Mondooooo:
    LMAO
  • Mondooooo @ Mondooooo:
    Wario world underground
  • K3Nv2 @ K3Nv2:
    Don't know why yellow potatoes come out so creamy when you roast them
  • AncientBoi @ AncientBoi:
    Did you soak them B4 hand?
  • AncientBoi @ AncientBoi:
    Cool. Though I'm Not the effeminate type. You know, the limp wrist, Sascha walking type of gay. :)
  • AncientBoi @ AncientBoi:
    Though I Do Cross-Dress Once in awhile :D
  • K3Nv2 @ K3Nv2:
    The home just confuses your wardrobe
  • AncientBoi @ AncientBoi:
    How are you doing today K3Nv2?
  • AncientBoi @ AncientBoi:
    You did? By whom?
  • AncientBoi @ AncientBoi:
    Ohh, Don't tell me lEOTck did it to you? :O:sad:
  • BakerMan @ BakerMan:
    nah we all know luke is who leo's smashing
    +1
  • AncientBoi @ AncientBoi:
    Oh :shit:! And I didn't get to 📽️ it! :angry::sad::cry: :hateit:
  • BakerMan @ BakerMan:
    GUYS I JUST FOUND OUT THAT ULTERIOR MOTIVES WAS FOUND YESTERDAY, AND IT WAS FROM P O R N 💀😭
    +1
  • AncientBoi @ AncientBoi:
    😱 .............................. :evil::tpi::evil:
    AncientBoi @ AncientBoi: 😱 .............................. :evil::tpi::evil: