WiiMart/WiiMart-Patcher
1
0
Fork 0
mirror of https://wiilab.wiimart.org/wiimart/WiiMart-Patcher synced 2025-09-05 21:11:13 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix markdown woes

Browse Source
This commit is contained in:
Spotlight 2021-12-30 16:38:03 -06:00
parent bd625c0779
commit 88142b2269
No known key found for this signature in database
GPG Key ID: 874AA355B3209BDC
2 changed files with 32 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/README.md
View File

@ -2,6 +2,6 @@
This directory contains documentation about given patches applied. This directory contains documentation about given patches applied.
Contents: Contents:
- [[`opcacrt6.yml`]]: A [Kaitai](https://kaitai.io) structure describing a very basic `opcacrt6.dat`. - [`opcacrt6.yml`](opcacrt6.yml): A [Kaitai](https://kaitai.io) structure describing a very basic `opcacrt6.dat`.
It does not attempt to handle things such as client certificates or user passwords. It does not attempt to handle things such as client certificates or user passwords.
- [[`patch_overwrite_ec.md`]]: An explanation as to why IOS needs to be patched for our operations. - [`patch_overwrite_ios.md`](patch_overwrite_ios.md): An explanation over why and how IOS is patched for operation of the Wii Shop Channel.

51
docs/patch_overwrite_ios.md
View File

@ -67,12 +67,14 @@ However, space constraints for our patch made this difficult. We chose to hardco
By default, the PowerPC core (Broadway) has memory protections enabled, preventing from us editing IOS's memory in MEM2. By default, the PowerPC core (Broadway) has memory protections enabled, preventing from us editing IOS's memory in MEM2.
We need to apply several patches to achieve our goal. We need to apply several patches to achieve our goal.
1. e need to obtain access to overwriting IOS memory. ---
First, we need to obtain access to overwriting IOS memory.
We set the Access Rights field in the WAD's Title Metadata (or `.tmd`) to 0x00000003, permitting memory access. We will use this with `MEM2_PROT` later. We set the Access Rights field in the WAD's Title Metadata (or `.tmd`) to 0x00000003, permitting memory access. We will use this with `MEM2_PROT` later.
This is thankfully a very quick fix. This is thankfully a very quick fix.
2. We need to find space to put our own custom function within the binary. ---
Second, we need to find space to put our own custom function within the binary.
Via symbols within the main ARC, we find a C++ class named `textinput::EventObserver` with 4 functions in a row that Via symbols within the main ARC, we find a C++ class named `textinput::EventObserver` with 4 functions in a row that
immediately `blr` - returning with no other logic: immediately `blr` - returning with no other logic:
@ -88,7 +90,8 @@ We must additionally update references to this single at two separate virtual ta
- `textinput::EventObserver` at `0x802f7a9` - `textinput::EventObserver` at `0x802f7a9`
- `ipl::keyboard::EventObserver` at `0x802f8418` - `ipl::keyboard::EventObserver` at `0x802f8418`
3. We need to devise a way to have the channel overwrite IOS memory. ---
Next, we need to devise a way to have the channel overwrite IOS memory.
We have carved out our own space at `0x80014428` to put a function. We have carved out our own space at `0x80014428` to put a function.
Thankfully, the operation is fairly simple: Thankfully, the operation is fairly simple:
@ -104,33 +107,33 @@ Thankfully, the operation is fairly simple:
We write and apply the following PowerPC assembly to achieve this task: We write and apply the following PowerPC assembly to achieve this task:
```asm ```asm
overwriteIOSPatch: overwriteIOSPatch:
; Load 0x0d8b420a, location of MEM_PROT, to r9. ; Load 0x0d8b420a, location of MEM_PROT, to r9.
lis r9, 0xcd8b lis r9, 0xcd8b
ori r9, r9, 0x420a ori r9, r9, 0x420a
; We wish to write 0x2 in order to disable. ; We wish to write 0x2 in order to disable.
li r10, 0x2 li r10, 0x2
; And... write! ; And... write!
sth r10, 0x0(r9) sth r10, 0x0(r9)
eieio eieio
; Load 0xd3a73ad4, location of of IOSC_VerifyPublicKeySig, to r9. ; Load 0xd3a73ad4, location of of IOSC_VerifyPublicKeySig, to r9.
lis r9, 0xd3a7 lis r9, 0xd3a7
ori r9, r9, 0x73ad4 ori r9, r9, 0x73ad4
; 0x20004770 represents our actual patch. ; 0x20004770 represents our actual patch.
lis r10, 0x2000 lis r10, 0x2000
ori r10, r10, 0x4770 ori r10, r10, 0x4770
; And... write. ; And... write.
stw r10, 0x0(r9) stw r10, 0x0(r9)
; Clear cache ; Clear cache
dcbi 0, r10 dcbi 0, r10
blr blr
``` ```
---
4. We need to determine the best way to call our custom patching function. Finally, we need to determine the best way to call our custom patching function.
Using the aforementioned symbols we find `ES_InitLib`, called once during initialization to open a handle with `/dev/es`. Using the aforementioned symbols we find `ES_InitLib`, called once during initialization to open a handle with `/dev/es`.
We insert a call to our function in its epilog, immediately before loading the previous LR from stack and branching back. We insert a call to our function in its epilog, immediately before loading the previous LR from stack and branching back.