| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 673
» Latest member: Epirei
» Forum threads: 1,867
» Forum posts: 15,668
Full Statistics
|
| Online Users |
There are currently 180 online users.
» 0 Member(s) | 177 Guest(s)
Bing, Google, Yandex
|
| Latest Threads |
Make it to 10,000
Forum: General Discussion
Last Post: Fzerowii
2 hours ago
» Replies: 8,781
» Views: 6,497,406
|
INCOMPLETE: How to create...
Forum: Other
Last Post: Epirei
Yesterday, 03:18 PM
» Replies: 4
» Views: 1,170
|
Looking for the Movement ...
Forum: Code Support / Help / Requests
Last Post: _Ro
05-12-2025, 09:42 PM
» Replies: 4
» Views: 102
|
Instant Respawn [davidevg...
Forum: Offline Non-Item
Last Post: Vega
05-12-2025, 03:05 PM
» Replies: 2
» Views: 5,980
|
Customize Unlock Screen [...
Forum: Incomplete & Outdated Codes
Last Post: B_squo
05-11-2025, 11:43 PM
» Replies: 1
» Views: 68
|
Bring up specific unlock ...
Forum: Offline Non-Item
Last Post: B_squo
05-11-2025, 11:39 PM
» Replies: 0
» Views: 45
|
Blue Shell Explosion Visu...
Forum: Offline; Item
Last Post: SonGotanTheSaiyan
05-10-2025, 01:16 AM
» Replies: 5
» Views: 15,645
|
How to Make your own Chea...
Forum: PowerPC Assembly
Last Post: Vega
05-09-2025, 07:20 PM
» Replies: 73
» Views: 150,813
|
Ghost Always Saves (Compe...
Forum: Misc/Other
Last Post: B_squo
05-08-2025, 11:08 PM
» Replies: 0
» Views: 89
|
No Record Uploading on Co...
Forum: Misc/Other
Last Post: B_squo
05-08-2025, 10:52 PM
» Replies: 0
» Views: 72
|
|
|
| Beginner's Guide to add ISO/WBFS to USB Drive |
|
Posted by: Vega - 03-04-2018, 02:12 AM - Forum: HBC & General Wii Softmodding
- No Replies
|
 |
Beginner's Guide to add ISO/WBFS to USB Drive
This guide is meant for the absolute beginner who has just softmodded their Wii and wants to add a ISO/WBFS file to their USB stick so they can play their games via a USB Loader app. The most common setup to play your Wii games via ISO/WBFS, is to have your all your HBC apps on your SD card while having your ISO/WBFS files on your USB stick.
Requirements:
- SD card that you already use that works for HBC
- USB Stick at least 4GB in size
- Softmodded Wii (Guide - https://mkwii.com/showthread.php?tid=1614)
- WBFS or ISO file of game that you are wanting to add to the USB
Visit this page - https://sourceforge.net/projects/usbloadergx/
Click on the large green Download button. You will be navigated to a new web page (still on sourceforge.net). After a brief moment, the download will begin..
Extract the download. You will see a folder called 'apps'. Move the apps folder to the root of your SD card. The SD card must be in FAT32 format. Place SD into Wii.
1. Insert your USB stick into your Computer.
2. Format the USB stick to FAT32 (Quick format will work)
NOTE if you use Linux and need to format a USB to FAT32: There is a program called 'gparted'. Simply google gparted FAT32, and you will find plenty of guides to format the USB.
3. Make a folder on the USB called "wbfs" (without the quotations)
4. Now we will make a folder within the wbfs folder. The name of this folder varies depending on the title and game ID of your game. For demo purposes we will use the American MKW game (game ID of RMCE01)
5. Within the wbfs folder, make the folder called - "MarioKartWii [RMCE01]" (without quotations)
6. The title of the game (no spaces) goes first, then the game ID within the brackets.
7. If your game is already in .wbfs format. We can simple drag and drop our American MKW game into the "MarioKartWii [RMCE01]" folder. If your game is in .iso format, please see further below for solution.
8. Once the .wbfs file has been added to the USB we need to rename it to match its game ID, so for this guide we rename the wbfs file to RMCE01.wbfs
9. Eject your USB. Now you must plug in your USB stick into the correct port. If your Wii is laying flat, this would be the BOTTOM port.
10. Launch HBC, launch USB Loader GX. You will see your game listed on the main menu. Select and launch it. Congratz.
If your game is in .iso format read this:
You will need WIT Tools to change the iso to a wbfs file. Download WIT Tools https://wit.wiimm.de/download.html
For help installing WIT Tools, view this thread HERE
If you are on Windows:
1. Once the tools are installed, there is a new Wiimm folder within your Program Files (x86) folder of your C Drive. Within that Wiimm folder, is a folder called WIT. Drag your ISO file into that WIT folder.
2. Open up cmd/command prompt
3. Type this: cd C:\Program Files (x86)\wiimm\wit
4. Now type this: wit copy nameofyourISO.iso newnameofyourISO.wbfs
5. And that's it you have made a copy of your game in the better wbfs format. Now you can complete the rest of the guide.
If you are on Linux:
1. Once the tools are installed. Open a terminal in the directory where your iso file is located.
2. wit copy nameofyourISO.iso newnameofyourISO.wbfs
3. And that's it you have made a copy of your game in the better wbfs format. Now you can complete the rest of the guide.
Troubleshooting:
If you get a black screen when attempting to boot your WBFS via USB Loader, there's a few reasons why this could happen:
1. Your USB stick is corrupted or near the end of its life. Reformat it to FAT32 (Do a FULL format, will take awhile)
2. Your WBFS file is corrupted, this could be because you possess a corrupt file of your game, or you simply pulled your USB stick out of your computer without properly right clicking on it and selecting Eject.
3. Your SD card containing your USB loader app is bad, reformat it.
|
|
|
| Controller Input Limitations |
|
Posted by: Vega - 03-01-2018, 09:32 PM - Forum: Non-Hacking MKW Threads
- Replies (1)
|
|
Not all controllers are created equally. Here are the values of each controller when holding the analog stick in the right+up position.
GCN: (Right 7, Up 1)
Classic: (Right 7, Up 1)
Wii Chuck: (Right 7, Up 4)
Wii Wheel: (Right 7, Up 7)
The Wii Wheel by far has the best diagonal inputs. This allows for a much higher advantage for taking SC's, charging MT's, etc. However, due to the fact of the difficulty to master the Wheel, Chuck is the best option. It is easy enough to learn and be consistent with while having the 2nd best diagonal inputs.
NOTE: Values for the Wii U (Wii compatible) Fight Pad controller are unknown.
|
|
|
|
| Country Codes |
|
Posted by: Vega - 02-28-2018, 11:49 PM - Forum: Resources and References
- No Replies
|
|
Here's a list of country codes (in decimal value) for use with something like the Any Region Changer HBC application. If you are using these for the Any Region Changer ocarina code, remember to convert these to Hex.
0: Error
1: Japan
2: Error
3: Error
4: Error
5: Error
6: Error
7: Error
8: Anguilla
9: Antigua and Barbuda
10: Argentina
11: Aruba
12: Bahamas
13: Barbados
14: Belize
15: Bolivia
16: Brazil
17: British Virgin Islands
18: Canada
19: Cayman Islands
20: Chile
21: Colombia
22: Costa Rica
23: Dominica
24: Dominican Republic
25: Ecuador
26: El Salvador
27: French Guiana
28: Grenada
29: Guadeloupe
30: Guatemala
31: Guyana
32: Haiti
33: Honduras
34: Jamaica
35: Martinique
36: Mexico
37: Montserrat
38: Netherlands Antilles
39: Nicaragua
40: Panama
41: Paraguay
42: Peru
43: St. Kitts and Nevis
44: St. Lucia
45: St. Vincent and the Grenadines
46: Suriname
47: Trinidad and Tobago
48: Turks and Caicos Islands
49: United States
50: Uruguay
51: US Virgin Islands
52: Venezuela
53: Error
54: Error
55: Error
56: Error
57: Error
58: Error
59: Error
60: Error
61: Error
62: Error
63: Error
64: Albania
65: Australia
66: Austria
67: Belgium
68: Bosnia and Herzegovina
69: Botswana
70: Bulgaria
71: Croatia
72: Cyprus
73: Czech Republic
74: Denmark
75: Estonia
76: Finland
77: France
78: Germany
79: Greece
80: Hungary
81: Iceland
82: Ireland
83: Italy
84: Latvia
85: Lesotho
86: Liechtenstein
87: Lithuania
88: Luxembourg
89: F.Y.R. of Macedonia
90: Malta
91: Montenegro
92: Mozambique
93: Namibia
94: Netherlands
95: New Zealand
96: Norway
97: Poland
98: Portugal
99: Romania
100: Russia
101: Serbia
102: Slovakia
103: Slovenia
104: South Africa
105: Spain
106: Swaziland
107: Sweden
108: Switzerland
109: Turkey
110: United Kingdom
111: Zambia
112: Zimbabwe
113: Azerbaijan
114: Mauritania
115: Mali
116: Niger
117: Chad
118: Sudan
119: Eritrea
120: Djibouti
121: Somalia
122: Error
123: Error
124: Error
125: Error
126: Error
127: Error
128: Taiwan
129: Error
130: Error
131: Error
132: Error
133: Error
134: Error
135: Error
136: South Korea
137: Error
138: Error
139: Error
140: Error
141: Error
142: Error
143: Error
144: Hong Kong
145: Macao
146: Error
147: Error
148: Error
149: Error
150: Error
151: Error
152: Indonesia
153: Singapore
154: Thailand
155: Philippines
156: Malaysia
157: Error
158: Error
159: Error
160: China
161: Error
162: Error
163: Error
164: Error
165: Error
166: Error
167: Error
168: U.A.E.
169: India
170: Egypt
171: Oman
172: Qatar
173: Kuwait
174: Saudi Arabia
175: Syria
176: Bahrain
177: Jordan
178: Error
179: Error
180: Error
181: Error
182: Error
183: Error
184: Error
185: Error
186: Error
187: Error
188: Error
189: Error
190: Error
191: Error
192: Error
193: Error
194: Error
195: Error
196: Error
197: Error
198: Error
199: Error
200: Error
201: Error
202: Error
203: Error
204: Error
205: Error
206: Error
207: Error
208: Error
209: Error
210: Error
211: Error
212: Error
213: Error
214: Error
215: Error
216: Error
217: Error
218: Error
219: Error
220: Error
221: Error
222: Error
223: Error
224: Error
225: Error
226: Error
227: Error
228: Error
229: Error
230: Error
231: Error
232: Error
233: Error
234: Error
235: Error
236: Error
237: Error
238: Error
239: Error
240: Error
241: Error
242: Error
243: Error
244: Error
245: Error
246: Error
247: Error
248: Error
249: Error
250: Error
251: Error
252: Error
253: Error
254: Error
255: Error
|
|
|
|
| Hack VR [XeR] |
|
Posted by: Vega - 02-26-2018, 08:03 PM - Forum: Online Non-Item
- Replies (2)
|
|
Hack VR [XeR]
Simple standard VR Hack. Works on all Licenses. You must do one online race for the VR to be updated on your profile.
NTSC-U
C2619048 00000002
3800XXXX B0039018
A0039018 00000000
PAL
C264C35C 00000002
3800XXXX B0039018
A0039018 00000000
NTSC-J
C264B9C8 00000002
3800XXXX B0039018
A0039018 00000000
NTSC-K
C263A674 00000002
3800XXXX B0039018
A0039018 00000000
XXXX = VR in Hex
270F = 9999VR
Code creator: XeR
|
|
|
|
| About Purgatory |
|
Posted by: Vega - 02-25-2018, 02:43 AM - Forum: Purgatory
- No Replies
|
|
About Purgatory
Any thread that is locked and we (the staff and I) are not sure whether or not to keep it archived in it's original sub-forum, will be placed in here.
If thread(s) have had many posts, they will never be deleted (to keep users' post counts from being drained down). If that's not the case, then the thread(s) could be deleted after residing in here for some time.
|
|
|
|
| About Wiimm's Tools |
|
Posted by: Vega - 02-24-2018, 12:06 AM - Forum: Wiimm's Tools
- Replies (3)
|
|
Wiimm's Tools
Wiimm's Tools is a program for manipulating Wii games and contents/parts within Wii games. It is split up into two major categories. WIT Tools and SZS Tools.
WIT Tools is the utility for manipulating whole ISO's/WBFS's/etc. You can extract, build, patch, edit ISOs/WBFSs. You can also use WIT Tools to format USB sticks in WBFS format and add ISOs/WBFSs to USB sticks. WIT Tools is meant to replace WBFS Manager, Wii Scrubber, & Wii Backup Manager.
SZS Tools is the utility for manipulating extracted contents/parts of ISO's/WBFS's. It is a popular tool for editing MKW's main.dol and StaticR.rel files. SZS Tools can also manipulate other file types such as .szs, .brres, .img, etc. Basically, you use WIT to extract and ISO, then use SZS to edit the parts, and use WIT again to rebuild the ISO.
The tools are purely command-based. There is no fancy, noob-friendly GUI. Windows uses the Tools via cmd/command prompt. With Linux, you just use your standard terminal screen.
Both major toolsets come with a set of command interfaces. WIT Tools comes with WIT command and WWT command. WIT is for any manipulation for ISOs/WBFSs while WWT is the command interface for WBFS USB drives, and adding ISOs/WBFSs to USB's.
There are many command interfaces that come with SZS Tools. The most popular one is WSTRT (used for main.dol and StaticR.rel manipulation). Theres other command interfaces such as WSZST, WBMGT, etc etc.
In this forum, I have provided download links, installation help, and command cheat sheets. It is expected you have some sort of intuition to figure out how to get started using the Tools. It is too difficult to post full fledge tutorials that include every itty bitty detail. Most users would be on Windows and I don't use Windows, so me writing Windows tutorials probably wouldn't be the most sufficient. I figured the cheat sheets would be perfect once you know how to utilize the basics of the tools.
If you still have some questions/concerns, post them here or go to WIT/SZS Tools Homepages (links provided below)
WIT Home Page - https://wit.wiimm.de
SZS Home Page - https://szs.wiimm.de
Some users will still not want to adapt away from archaic programs (WBFS manager, Wii Scrubber, SZS Modifier, etc). Those old programs are glitchy, out-of-date, can corrupt ISOs, etc etc. For example here are a list of reasons why you shouldn't be using WiiScrubber over Wiimm's Tools
- WiiScrubber hasn't been updated since 2010, it only works for Windows (unless you're running Wine emulation) while WIT/SZS (still being updated in 2020) has versions for both Linux & Windows
- WiiScrubber can corrupt ISOs
- WiiScrubber only allows ISO edits within its GUI program. WIT allows you make edits using your OS's own desktop/window manager/etc.
- Can't open WBFS files with WiiScrubber, must convert to ISO no matter what
- Can't replace/edit most parts to an already wiimmfi-patched ISO
- There's no options in WiiScrubber to check if main.dol/StaticR.rel are clean/original
- In some cases replacing too much items will cause WiiScrubber to not allow you to save changes because the ISO file size was altered too much.
|
|
|
|
| MKWii RAM Code Address Ranges for Hex Editing ISO's |
|
Posted by: Vega - 02-23-2018, 06:48 PM - Forum: Resources and References
- No Replies
|
|
Usable addresses for codes when hex editing an MKWii ISO
Main.dol
Start: 0x00003f00 End: 0x00384dbf NTSC-U (USA)
Start: 0x00003f00 End: 0x0038913f PAL (EUR)
Start: 0x00003f00 End: 0x00388abf NTSC-J (JAP)
Start: 0x00003f00 End: 0x0037715f NTSC-K (KOR)
StaticR.rel
Start: 0x0050bf60 End: 0x009b8ef3 NTSC-U (USA)
Start: 0x005102e0 End: 0x009bd6a3 PAL (EUR)
Start: 0x0050fc60 End: 0x009bc71b NTSC-J (JAP)
Start: 0x004fe300 End: 0x009abcfb NTSC-K (KOR)
If a code address falls into the main.dol range, then it can be edited in the main.dol.
If it falls in the staticr.rel range, then it can be edited in the staticr.rel
All other code addresses cannot be hex edited into an ISO.
Example of address offset to code address conversion:
004fe300 = 044FE300 XXXXXXXX
Credits to: Luis
|
|
|
|
| How to Port Codes to other Regions |
|
Posted by: Vega - 02-23-2018, 06:31 PM - Forum: Coding (Non-ASM) and Dolphin
- Replies (4)
|
|
How to Port Codes to other Regions
This guide will teach you how to manually port codes to other regions. There are programs out there (such as Bean's auto porter) that can port codes for you. But at some point, those programs will not work on a particular code, and you will need to manually port.
Requirements:
- Hex Editor**
- RAM Dumps*** (you will need at least the RAM Dump of the region you are porting from and the region you are porting to)
**I recommend HxD. HxD is used in this guide. You can find it very easily on a google search for free download. If you are a Linux User, you will need Wine emulation to run HxD.
***Regarding RAM Dumps: If you have Dolphin Emulator, look at this thread HERE. If not, run this code HERE on your Wii.
Chapter 1: Introduction
We will start off with the NTSC-U Show Item Early Code. We want to port the code to PAL.
I have chosen the Show Item Early Code for this guide since ASM (C2 type) codes are not as simple as 32-bit (04 type) codes, but are still easy enough for any beginner to quickly grasp. Basically in 95% of all C2 and 04 codes, the very first line (the C2XXXXXX/04XXXXXX value) is what needs to be ported. All other lines within the code will remain the same. Of course, there are some codes where this isn't the case, but this guide is meant for beginners.
Chapter 2: Finding Location of Code's Address in RAM
Open HxD and press CLTR+O on your keyboard to open up the menu to search your computer for your NTSC-U RAM Dump. We always start off with the RAM Dump version that matches the region of code we are porting from.
So our NTSC-U Show Item Early code is...
Code: C27AB9D4 00000002
807F0020 907F001C
60000000 00000000
What we want to do is find the Code's RAM Address (offset & column location) within the RAM Dump. To figure this out, simply remove the first 2 digits off the first line (the C2 line) of the code. Don't worry about any other lines in the code. If you did the conversion correctly, you should come up with a value of...
7AB9D4
On you hex editor, press CTRL+G. a 'Goto' prompt will appear to enter in an offset to search for.
![[Image: goto.png]](https://mariokartwii.com/pics/tut/goto.png)
Paste in that 7AB9D4 number and be sure number/data type is in Hexadecimal (Hex).
![[Image: gotofilled.png]](https://mariokartwii.com/pics/tut/gotofilled.png)
Click OK and HXD will navigate you to row 007AB9D0 under column 4. The last digit of a code's RAM address is the column number value on the hex editor. The following picture contains a red arrow pointing to where your mouse cursor will now be at, the green arrow points to the spot in HxD where you can always see your Offset location for the current file you are in.
![[Image: atoffset.png]](https://mariokartwii.com/pics/tut/atoffset.png)
Chapter 3: String Searching
What you need to do is highlight the first 4 bytes (8 digits) of code beginning where your cursor was navigated to. If done correctly, you should have highlighted the following hex string...
90 7F 00 1C
![[Image: firststringfilled.png]](https://mariokartwii.com/pics/tut/firststringfilled.png)
Once you have that higlighted, press CTRL+C on your keyboard to copy the hex string.
Now open up your PAL RAM dump file, HxD will add it as a new tab. You should automatically be in the PAL Ram dump now, if not click on the tab to view it.
![[Image: palopened.png]](https://mariokartwii.com/pics/tut/palopened.png)
Now press CTRL+F and a 'Fine' prompt will appear.
![[Image: findwindow.png]](https://mariokartwii.com/pics/tut/findwindow.png)
For the "Search for" field, paste in what you have just copied. Change Datatype from Text-String to Hex.
![[Image: findwindow1ststring.png]](https://mariokartwii.com/pics/tut/findwindow1ststring.png)
Click OK.
If done correctly, you will be brought to offset 000F441C indicated by the green arrow.
![[Image: 1ststringfound.png]](https://mariokartwii.com/pics/tut/1ststringfound.png)
Right off the bat, I will you that this is the wrong address. When comparing the address of one region to another, if the margin of difference is huge, then it's a high chance that you ported to the wrong address. If we were to use the offset value of F441C and convert that, the PAL code's C2 line would be C20F441C, which is a Huge difference compared to the NTSC-U Code's Address, which means it's obviously wrong.
There are many instances where a 4 byte string of hex is repeated in MKWii RAM. Sometimes, you only need to use a 4 byte string to find your address, other times you may need to copy something as long as 32 bytes. It all depends on the code.
Lets go back to our NTSC-U RAM Dump file. This time highlight the first 12 bytes (24 digits of code). You should have a hex string of...
90 7F 00 1C 88 1F 00 2D 2C 00 00 00
![[Image: highlight2ndstring.png]](https://mariokartwii.com/pics/tut/highlight2ndstring.png)
Copy that string using CTRL+C. Go back to PAL RAM Dump file. Hit CTRL+F to bring up the 'Find' window. Paste in the new 12 byte string. However, we want to change search direction from "Forward" to "All".
![[Image: 2ndstringfind.png]](https://mariokartwii.com/pics/tut/2ndstringfind.png)
Since we searched in PAL RAM earlier, we are no longer at the very beginning of the PAL RAM Dump file. So we need the "All" search direction to tell HxD to search both ways from out current spot in PAL RAM. Click OK.
You will be navigated to the offset value of 7BA434 indicated by the green arrow of the above picture.
![[Image: 2ndstringfound.png]](https://mariokartwii.com/pics/tut/2ndstringfound.png)
If we convert the offset value to a usable C2 line, we get C27BA434. As you can see, this is slightly different than the NTSC-U address. Chances are, this address is the correct one. What you want to also do is compare the surrounding random numbers of both RAM Dumps, they should be very identical (doesn't have to be exactly the same). If it is, there's a very good chance the address is correct. So now you have the C2 line for PAL, complete the rest of the code....
PAL Show Item Early~
Code: C27BA434 00000002
807F0020 907F001C
60000000 00000000
Chapter 4: Testing; Conclusion
After porting any code, always be sure to test it. If your tests fail, go back to the hex editor and try to re-port the code.
|
|
|
|
| Force Battle Bug/Glitch [XeR] |
|
Posted by: Vega - 02-23-2018, 04:52 PM - Forum: Online Non-Item
- Replies (2)
|
|
Force Battle Bug/Glitch [XeR]
Battle Bug/Glitch is on automatically all the time, no need to do a quick battle.
NTSC-U
048CEEAC 47927C00
PAL
048D3E14 47927C00
NTSC-J
048D2F64 47927C00
NTSC-K
048C22AC 47927C00
Code created by: XeR
|
|
|
|
|
![[Image: cn.png]](http://mkwii.com/pics/flags/cn.png)
Big