FatesHaxx, a WIP research project to get 3 more 1st party games up and running as homebrew entry points.

Hello Temp. As I got stormed in the original post of FatesHaxx, I decided to take it onto a blog to document all of my progress while not being distracted by the storm in the OP.

My progress:

(The no duh part)
Installing Fates
Making a new save
Finishing up chapter 6
Dumping the data
(The end of The no duh part)

At this point, I'm currently analyzing the data with a hex editor. Once I find what I'm looking for, I'll post an update.
Hopefully I'll get something out tomorrow (some info on where I edited and what it exactly does and what it *could* do.
I might be hitting a wall, but if I can get anything out of this issue, it will be documented with the best of my knowledge.

I am currently using:
FE:Fates Special Edition USA + Hand-Made Undub (modified voice acting cannot affect save data nor inventory data)
11.0U A9LH Sysnand with Luma 5.5 Dev Old 3DS XL
Ubuntu MATE 16.10 Early Dev Branch
Bless Hex-Editor (sudo apt-get install bless on Debian based distros)
My young brain.
Hope

I am going to sleep now and I will hopefully get more updates out tomorrow.

Comments

G
(modified voice acting cannot affect save data nor inventory data)
If I'm not mistaken it can change the game's structure which might fuck up ROP related junk
 
  • Like
Reactions: 1 person
If I get it working for the version I use, I'll check to make sure that it works on the official and tweak to fix that, if needed (I can't see some replaced voice files changing the structure. No files deleted, only one female voice set modified, and those are the only modified files). I prefer not waiting 60 hours for 2 GBs to download and wait until it is a good time to download. I also have my people I keep in touch with. They can test.
 
It may be worth using the same hardware/software configuration your friend had when he encountered the crash, in order to more accurately replicate the issue. While undubbing doesn't affect the save file, the altered part of the ROM still runs a risk of unpredictable behaviour/crashes that differ from an unmodified retail ROM. When you get the retail ROM, it shouldn't be too problematic moving your save across from the undubbed version.

There's no guarantee a useable exploit could come from this since not all games are exploitable, but if no-one tried to look then the ones that do contain useful exploits would never have been found, so good on you for at least taking the initiative. Don't get your hopes up too much, but remember that even a negative result is still a contribution nonetheless.
 
  • Like
Reactions: 1 person
using ubuntu doesn't make you smart
it's worse than using windows to me
if you have no ARM knowledge, just stop
this is prohax2 to me
 
  • Like
Reactions: 11 people
Oh wow, you are such an Idiot...
Do research FIRST then talk about it, but not on an open forum!
If the game is exploitable Nintendo has more time to fix it. And if the game isn't exploitable, it makes you looke like an Idiot.
 
@Justinde75 lmao, then i could say Garfield Kart is exploitable (which is really possible, actually), but I never said where it was exploitable or anything, stop being stupid and calling other people idiots
 
  • Like
Reactions: 2 people
@Justinde75 No. He didn't say what kind of vuln it was, what was happening, or anything. He clearly doesn't know what he does.
 
They currently continue developing the game. They can easily patch IF there is a exploitable vuln. .Today every game has "a crazy exploitable vuln"
 
"A WIP research Project to get 3 more games up and running for homebrew" actually they are just two games. The third path is dlc. If you talk about the limited edition, its only one game.
 
Now now children, be nice.

I admire your enthusiasm OP, I hope you'll get something out of it but I doubt it.
 
yeah the thing his
this is his blog
he can write whatever he wants
true or not he can still
 
Remember that one time I shitposted about Garfield Kart?
Crash =/= exploit - crash the game in Citra first, with the debugger running.
Watch the registers (specifically the program counter), and attempt to manipulate the stack by fiddling with the save data area that specifically crashed.
For ROP, you need stack manipulation - achieved by buffer overflows/stack smashing.

In the Garfield Kart case, while the game could be crashed with save manipulation, it did nothing to modify the stack.
 

Blog entry information

Author
seijinshu
Views
131
Comments
34
Last update

More entries in Personal Blogs

More entries from seijinshu

General chit-chat
Help Users
  • No one is chatting at the moment.
    K3N1 @ K3N1: https://i.ibb.co/gTVKLHF/bill-king-of-the-hill.gif