- Joined
- May 10, 2014
- Messages
- 1,178
- Trophies
- 0
- Age
- 34
- Location
- Who wants to know?
- Website
- sites.google.com
- XP
- 2,834
- Country
dumped the title from godmode9 and named it TwlBg.cxi but when i click wide.bat it just blinks and closes
This is what happened to medumped the title from godmode9 and named it TwlBg.cxi but when i click wide.bat it just blinks and closes
seems like there is some inconsistency in the instructionsThis is what happened to me
dumped the title from godmode9 and named it TwlBg.cxi but when i click wide.bat it just blinks and closes
Is "wide.bat" in the same folder as "mkpatch_b.exe"?This is what happened to me
yep same folderIs "wide.bat" in the same folder as "mkpatch_b.exe"?
yep same folder
Hmm, so it's actually expecting "section0.bin", not an actual unpatched TwlBg .cxi file.
This is what I was thinking. However, Sono did say that both would workHmm, so it's actually expecting "section0.bin", not an actual unpatched TwlBg .cxi file.
We might've misunderstood that part.This is what I was thinking. However, Sono did say that both would work
Would changing TwlBg.cxi to section0.bin and then change it back work? I don't know, since I think those files are the sameWe might've misunderstood that part.
I don't think*Would changing TwlBg.cxi to section0.bin and then change it back work? I don't know, since I think those files are the same
I'm having the same problem :/dumped the title from godmode9 and named it TwlBg.cxi but when i click wide.bat it just blinks and closes
I updated the instructions, so that you can get "section0.bin".Would changing TwlBg.cxi to section0.bin and then change it back work? I don't know, since I think those files are the same
--------------------- MERGED ---------------------------
I don't think*
Thank you, man. You're the bestI updated the instructions, so that you can get "section0.bin".
Does it say so?@Robz8 it seems mkpatch_b isn't compatible with my version of Windows... I don't know what to do now.
Yes, it does say soDoes it say so?
If not, put "pause" below the line in "wide.bat", and try running it again.