Nintendo Pinky's Wii-U Tutorials

@Joonie ,

w.up("bootDrcTex.tga", "/vol/storage_mlc01/usr/title/00050000/10198900/meta/bootDrcTex.tga") changes the gamepad boot screen. this is using Yoshi's Island title id which is the 101.... portion. change to ur own game's to do this. failure to do so will result in a file can't be found error.

w.up("bootTvTex.tga", "/vol/storage_mlc01/usr/title/00050000/10198900/meta/bootTvTex.tga") changes the tv splash screen.

w.up("iconTex.tga ", "/vol/storage_mlc01/usr/title/00050000/10198900/meta/
iconTex.tga") edits the icon.

and, w.up("bootsound.btsnd", "/vol/storage_mlc01/usr/title/00050000/10198900/meta/bootsound.btsnd") edits the sound byte played when opening the game. change mlc01 to usb01 if the game is on the usb. :)
 
Last edited:
w.dl("/vol/storage_mlc01/usr/title/00050000/10198900/meta/
meta.xml")

downloads the meta file so that u can change the name. reupload it with

w.up("meta.xml ", "/vol/storage_mlc01/usr/title/00050000/10198900/meta/
meta.xml")

this is how I changed all aspects of Yoshi's Island.
 
Last edited:
ygw7o.jpg

I can now boot into the homebrew channel by holding B, boot into cfw by holding Y, and boot into redNAND by default. :-P I didn't create that image. I found it on gbatemp. :)
 
Warning:
Code: 
do not attempt coldboothax.  I'm sure glad I didn't.  every post I've read of people trying it on gbatemp has resulted in a brick.  a brick is almost guaranteed if the game ur using with the exploit is on usb.  I think the usb partition is read near the end of the boot cycle which is y u brick.  opening ur haxchi game only takes about ten more seconds and ur pretty safe with that.  :)
 
pinky said:
u need to use the wupclient.py to make a connection to the system. then, download the sys_prod.xml. modify it. then, reupload it. it's a lot like how u'd download/upload files on the vita before henkaku.
Click to expand...

This method needs caution, my friend just got brick from doing this, He's successfully done his, so he gained the confidence to do his friend's, unfortunately he did not see its completion log, so he just assumed it was done uploading, and turned out, it got bricked..

I don't think he can recover from this unless he's got a NAND dump..
 
Joonie said:
This method needs caution, my friend just got brick from doing this, He's successfully done his, so he gained the confidence to do his friend's, unfortunately he did not see its completion log, so he just assumed it was done uploading, and turned out, it got bricked..

I don't think he can recover from this unless he's got a NAND dump..
Click to expand...

it's the reason I won't try. I have 61 games for the wii-u, so I don't want to risk my system. all of them r digital aside from Nintendo Land since it's not on there (Nintendo's servers). yeah, u need a NAND dump. I'm not sure if u can fix that issue with a redNAND dump or not. I'm still learning. ;) I think the issue is usually associated with using a usb game since it's read later in the boot cycle. that's what I've gathered from temp. :)
 
pinky said:
it's the reason I won't try. I have 61 games for the wii-u, so I don't want to risk my system. all of them r digital aside from Nintendo Land since it's not on there (Nintendo's servers). yeah, u need a NAND dump. I'm not sure if u can fix that issue with a redNAND dump or not. I'm still learning. ;) I think the issue is usually associated with using a usb game since it's read later in the boot cycle. that's what I've gathered from temp. :)
Click to expand...

Good news, he unplugged the wiiu, then let it sit for like an hour, now it boots and was asked to reset.. so after then, it works fine lol
 
Joonie said:
Good news, he unplugged the wiiu, then let it sit for like an hour, now it boots and was asked to reset.. so after then, it works fine lol
Click to expand...

one of the issues is standby with the system. if u turn it (system) off, and leave leave standby on, the power light or the standby light (blue or yellow) will keep flashing. the system won't turn on due to this. maybe that's what happened? u can turn the system on if u power cycle it. this is what can happen with redNAND or cfw, but turning off standby fixes it.
 
this is my home menu to differentiate games. u can't place the disc game (Nintendo Land) in a folder. homebrew houses my redNAND multi elf boot thing as well as system config tool which can install fake tickets:

28savcm.jpg
 
I may write a tutorial on this, but at this time, I'm not interested in that. I could tell u how to get the common key and ancast keys via ur otp. that's what I did, but it's a little larger than the fw.img circling. oh, my....it works though. I'm using my own redNAND and cfw fw.img. the latter is the same size though; the former is a little larger. hehe...
 
I've now got it to where holding A boots up the backup manager where u can injected roms like dq ix on the tv. :-P
 
here r some other important commands for haxchi and wupclient.py:

this command replaces the normal ds rom with a hacked version for haxchi:

Code: 
w.up("rom.zip", "/vol/storage_usb01/usr/title/00050000/YOUR_GAME_TITLE_ID/content/0010/rom.zip")

these two commands inject a configuration file for use with haxchi. the config file will tell the system which homebrew to boot (i.e. default=boot/fw.img)

Code: 
w.up("config.txt", "/vol/storage_mlc01/usr/title/00050000/YOUR_GAME_TITLE_ID/content/config.txt")
w.chmod("/vol/storage_mlc01/usr/title/00050000/YOUR_GAME_TITLE_ID/content/config.txt", 0x644)

this command instructs wupclient to download a particular file (needed for making ur system region free; not this particular command)

Code: 
w.dl("/vol/storage_usb01/usr/title/00050000/YOUR_GAME_TITLE_ID/content/config.txt")

replace usb01 with mlc01 to upload/download to the internal flash.
 
I encountered a weird issue with injecting my red NAND on to a different SD card (the one I use with loadiine). injecting resulted in a completely unallocated card instead of FAT32. I had to recreate the NAND from scratch which takes about two hours. it formats the sd card, so I'm currently replacing the files (148GBs or so).
 
Joonie said:
This method needs caution, my friend just got brick from doing this, He's successfully done his, so he gained the confidence to do his friend's, unfortunately he did not see its completion log, so he just assumed it was done uploading, and turned out, it got bricked..

I don't think he can recover from this unless he's got a NAND dump..
Click to expand...

it's impossible without a NAND dump. since the system contains an otp sector, it contains console-specific keys, so using an others NAND dump won't work. I had a similar error with my config.txt when I added the A button to boot loadiine. I uploaded it, but it didn't replace my original config.txt, so I redownloaded it to see y A wasn't working. that's when I discovered it hadn't replaced the file. if u do choose to do coldboothax, u should probably redownload the system.xml to check if the change is present. though, in ur friend's particular case, it sounds like the entire file didn't get uploaded considering it should've been the original file again otherwise. uploading with wupclient.py is slow as hell too. it took about 20 minutes to upload my 3MB splash screen. a txt file shouldn't take much time though.
 
oh, btw, I don't think u need a complete NAND dump. smea of iosuhax said that u can shift blocks within the NAND and replace the blocks that r corrupted. he was actually responding to the mass of bricks doing coldboothax.
 
Last edited:
I found another "bug:" if u change SD cards, the games won't work, so I'm going to try reinstalling. I'll let u know if that works.
 
it appears that the ticket is applied to the NAND itself in the slc partition. that's y the games wouldn't work after redumping the NAND. though, the games r still present on USB, just the licensing is applied to redNAND/NAND depending on which one ur using. :)
 
You must log in or register to reply here.

Similar threads

Back
Top