Homebrew What am I doing wrong, (patching Neo Y)

[ZedMania]

Hey. I've been having problems with this patching thing for the majority of the day. Heres my 3ds info, if you need it:
Version: 10.1 Old 3ds
Homebrew: Themehax

So here's the steps i took to patch this thing:
1. Dumped the Pokemon Y files using braindump.
2. Received the romfs.bin file and exef.bin file.
3. I put these into a folder and downloaded the Pack Hack thing. I put these into the Pack Hack folder and opened up the RomFS Extractor.
4. Obtained the extracted files from the extractor. I then put the Neo Y file 'a' into the extracted file, replacing the original extracted 'a' file, (if that makes sense :3).
5. I then used the RomFS Builder to put it all back together, and I named the file "00055E00.romfs".
6. Used the Hxd thing to delete the first 1000 uh... code? Idk.
7. I then saved it, and copied it onto the "hans" file on my SD card. (So /SD Root/hans/00055E00.romfs)
8. I put the SD card back into the 3ds, loaded up Hans, clicked Yes on the 'Load romfs from SD Card' and then Yes again to start the game. The game glitched out a little bit and then just showed me some glitchy line on the left corner of the top screen...

I'm sorry in advance if this question has already been answered or something, or if I sound dumb. Im sorta new to this 3ds hacking thing xD

Thanks

EDIT: I can now 'play' Neo Y. Turns out my problem was that the Neo Y 'a' file replaced the entire contents of the 'a' file in my dumped Pokemon romfs. I had to go and manually replace all of the files that needed it.

However, whilst Neo Y does play to an extent now, (It plays through the first cutscene) the game appears to crash after the Fletchling wakes your character up. I don't know why this happens o_o

 

[zeldafan20081]

Hey. I've been having problems with this patching thing for the majority of the day. Heres my 3ds info, if you need it:
Version: 10.1 Old 3ds
Homebrew: Themehax

So here's the steps i took to patch this thing:
1. Dumped the Pokemon Y files using braindump.
2. Received the romfs.bin file and exef.bin file.
3. I put these into a folder and downloaded the Pack Hack thing. I put these into the Pack Hack folder and opened up the RomFS Extractor.
4. Obtained the extracted files from the extractor. I then put the Neo Y file 'a' into the extracted file, replacing the original extracted 'a' file, (if that makes sense :3).
5. I then used the RomFS Builder to put it all back together, and I named the file "00055E00.romfs".
6. Used the Hxd thing to delete the first 1000 uh... code? Idk.
7. I then saved it, and copied it onto the "hans" file on my SD card. (So /SD Root/hans/00055E00.romfs)
8. I put the SD card back into the 3ds, loaded up Hans, clicked Yes on the 'Load code from SD Card' and then Yes again to start the game. The game glitched out a little bit and then just showed me some glitchy line on the left corner of the top screen...

I'm sorry in advance if this question has already been answered or something, or if I sound dumb. Im sorta new to this 3ds hacking thing xD

Thanks

Try loading the romfs->SD, not code->SD.

 

[ZedMania]

Oh xD Sorry I meant to put "load romfs". Thanks for replying though!

 

[suloku]

6. Used the Hxd thing to delete the first 1000 uh... code? Idk.

Did you delete the first 1000 bytes (wrong) or the first 0x1000 bytes (correct)?
0x1000 is base 16, you have to remove the first 4096 bytes.

 

[TamDanny]

Alright, I just got this working for me, so let me tell you how I did it:

1. Dump my X ROM (takes a really long time )
2. Put the dumped romfs.bin and exef.bin (I didn't use this file at all actually) in the computer (keep it there if you want to make your own personal edits )
3. Used either ctrtool or RomFS Extractor to extract the files within the romfs.bin file (I tested both of them, and they both give the same results, though RomFS Extractor is more user-friendly).
4. Replaced the Neo X/Y files with the dumped ROM's files, which is only a folder called "a".
5. Repack the ROM using the RomFS Builder. Name it "00055E00.romfs" here if you want (in my case, it was 00055D00.romfs)
6. Used HxD to delete the first 0x1000 bytes in the repacked file. Only select from the beginning of the binary code til the end of the line FF0, no further.
7. Saved it, then place the 00055E00.romfs file in the directory: sd:/hans (don't put it in sd:/3ds/hans!)
8. Load HANS in Homebrew Launcher, select your game, set your settings, and it should work!

Hope this helps!

 

[suloku]

Again, it's 4096 bytes; neobrain posted the number in hex (0x1000)

 

[ZedMania]

Did you delete the first 1000 bytes (wrong) or the first 0x1000 bytes (correct)?
0x1000 is base 16, you have to remove the first 4096 bytes.

Yeah I deleted the first 0x1000 bytes. Thanks though! (I did it by opening up the .romfs, using ctrl E and putting 1000 in the length or something)

@TamDanny Argh. All of the variables you mentioned that I was thinking of (like using Ctrtool instead of RomFS Extractor) all come to the same outcome. Damn it. Thanks!

 

[TamDanny]

Again, it's 4096 bytes; neobrain posted the number in hex (0x1000)

Oh right, I wanted to say that, but I'm used to saying the decimal number rather than the hex one. Lemme just ninja-edit that.

 

[suloku]

Yeah I deleted the first 0x1000 bytes. Thanks though! (I did it by opening up the .romfs, using ctrl E and putting 1000 in the length or something)

Most hex editors allow to input hex and decimal numbers for that, I know I'm being tyresome with that, but you seem to be doibg everything right

 

[ZedMania]

Most hex editors allow to input hex and decimal numbers for that, I know I'm being tyresome with that, but you seem to be doibg everything right

Oh right. This might be a factor that tells you if im doing something wrong though: My .romfs file at the end of it is 395 Megabytes. I think i've seen others with over a Gigabyte for Neo X and Y...

 

[TamDanny]

Yeah I deleted the first 0x1000 bytes. Thanks though! (I did it by opening up the .romfs, using ctrl E and putting 1000 in the length or something)

@TamDanny Argh. All of the variables you mentioned that I was thinking of (like using Ctrtool instead of RomFS Extractor) all come to the same outcome. Damn it. Thanks!

Okay, from what I can gather with what you said, I only have 2 theories.
Well, first, I'm just wondering if you deleted the whole first 0x1000 bytes. I have this lil' hunch that maybe you actually filled the values with only zeros, which could be the problem. Usually when you get a glitchy line at the corner, the romfs file is invalid; so that's why I ask.
If that's not the problem, then it might be your hax method. The only difference I see between your process and mine is that I used Ironhax, but you used Themehax. I'm pretty sure this isn't the case, but I don't know if people with Themehax might have had problems with that.

--------------------- MERGED ---------------------------

Oh right. This might be a factor that tells you if im doing something wrong though: My .romfs file at the end of it is 395 Megabytes. I think i've seen others with over a Gigabyte for Neo X and Y...

The .romfs file is actually supposed to be like 1.7GB, because it's the entire code of the game. XD
Hmm...when you dumped the ROM, did you later selected a title to choose from? And how long did it took?

 

[ar4757]

Identical problem here, glitchy line on left of screen. I too have 00055E00.romfs
Followed your exact process - think it could be we need to reinstall 2.5 ? Only thing I can think of.

By the way, does your hex show "28" as the first number now? After deleting the 1000 bytes?

 

[Amapola62]

Mine does... is it bad ?

 

[ZedMania]

@TamDanny Umm.... I hope its not the latter case, because thats literally my only way of getting hacks on here. For the former though, I just checked my .romsf file again and it starts at 000000000 28.

@ar4757 Yeah xD

 

[TamDanny]

Identical problem here, glitchy line on left of screen. I too have 00055E00.romfs
Followed your exact process - think it could be we need to reinstall 2.5 ? Only thing I can think of.

By the way, does your hex show "28" as the first number now? After deleting the 1000 bytes?

Mine does... is it bad ?

Don't worry, I have 28 at the beginning, and it's working fine.

@ZedMania I guess you didn't saw the second part of that reply, but I'll just reiterate. The .romfs file is actually supposed to be 1.7GB, because it's literally every bit of code that Pokemon Y is made of. When you dumped the ROM, did you select a title to choose from? And how long did it took?

 

[ar4757]

Mine does... is it bad ?

@TamDanny Umm.... I hope its not the latter case, because thats literally my only way of getting hacks on here. For the former though, I just checked my .romsf file again and it starts at 000000000 28.

@ar4757 Yeah xD

Not sure whose is right, probably none of ours lol

--------------------- MERGED ---------------------------

Don't worry, I have 28 at the beginning, and it's working fine.

@ZedMania I guess you didn't saw the second part of that reply, but I'll just reiterate. The .romfs file is actually supposed to be 1.7GB, because it's literally every bit of code that Pokemon Y is made of. When you dumped the ROM, did you select a title to choose from? And how long did it took?

Really? So my hex must be right then. I don't know what the problem is then. Thanks for confirming that though

 

[ZedMania]

@TamDanny Oh, no I didnt. Sorry Okay so, when first dumped it, it took a really long time, (I ended up leaving to do something else), but as I remember the first romfs.bin file was something like 1.7GB... so I have no clue what happened in the process xD maybe I can salvage the original file somewhere and try it again

 

[TamDanny]

@TamDanny Oh, no I didnt. Sorry Okay so, when first dumped it, it took a really long time, (I ended up leaving to do something else), but as I remember the first romfs.bin file was something like 1.7GB... so I have no clue what happened in the process xD maybe I can salvage the original file somewhere and try it again

Yeah, I think you should try looking for that file. If you can't, I suggest dumping the ROM once more, and retry the whole thing. Hopefully, you should be able to play some Neo Y soon. If anything comes up, don't hesitate to ask.

 

[qtfoo]

Small question, is RomFS Builder supposed to look like it's stuck/frozen on "Prompting to Save..."? I'm wondering if it crashed or its just really taking its time.

 

[Amapola62]

Well...I have it load my X save file so I suppose it works ?

I have level 7 jigglypuff on route 3...I think i have the edits too...