I don't like to create threads for asking anything, specially when I feel it's a dumb question. But this is driving me mad. Please, read it all if you have some spare time.
It all started when I read the braindump prerelease thread from the great temper @neobrain. I was delighted at such nice development for the ROM hacking community. I immediately got my 3DS outside of my backpack, where I usually keep it, and using the nifty app, I put my Fire Emblem: Awakening digital copy in a long but straightful dumping process. I went to read more from the marvelous GBATemp community meanwhile.
Three or four hours of reading so many good lines from the great VinsCool later, I went to check my 3DS. It had already finished the dumping task, from which I got a 1 GB romfs.bin file. Using SciresM's excellent ROMFS extracting tool, I managed to get so many media, data and whatnot directories. I started to happy editing several LZ11 compressed files! Oh, the joys of life!
Anyway. After messing up with around four or five files, I decided to check the subtle changes I had done. Using the builder tool from SciresM, I reunited all of the directories into one big file, from which I erased the first 0x1000 bytes as everyone in several threads says it has to be. My excitement was in the clouds when the builder ended its task! Being fairly new to the ROM hacking stuff, I was joyful and already looking forward to everything I could just by changing some scripts and images.
I renamed my rebuilt file as the HANS app stated. It was 000A0500.romfs, I remember, and I put it in the hans folder, which I created in the root directory of the SD card. I know I did it right since HANS didn't print the "INVALID" message it prints when it doesn't find the ROMFS file as specified, or when it's been wrongly edited. Everything went down once I pressed A with the "OK" option selected. My screen got filled by so many weird pixels, just like when opening any homebrew app, but it froze there.
I retried the process so many times, some of which I used the romfs file as I got it, without editing anything, and only removing the 0x1000 first bytes. The same result every time. I even tried using my other 3DS, an old one. The result was the same. Both screens filled by strange lines and patterns of white, pink and green pixels. All of the screen, not only a part, nor only the far left side. I tried to pick a shot using the HOME menu button, but it didn't work. The L + R + down + B combo for getting back to the Homebrew Launcher worked, though.
Thinking that maybe braindump or the extractor app could be doing something bad, I went to filthy places of the www. I had to get a CIA file! What a shame... I thought it could work better than my own dump. I even used the ctrtool.exe file to extract the its contents as described by Asia81 in another thread. I had false hopes...
Nothing. That's what I got. The exact same result, which I won't describe again since I already repeated it several times. I gave up on this. I just couldn't stand up...
I went happy editing Pokémon then, trying to forget all of this for my own good. It worked great. No strange pixels. Only the ocassional yellow screen freezing when booting it up. The romfs loaded flawlessly nearly always. But today, I just thought "Hey, maybe I get some luck with Awakening today". Oh, the suffering...
I don't need to say the exact same thing happened.
I simply can't load my American Fire Emblem: Awakening digital copy with a ROMFS through HANS, even if the ROMFS isn't edited (the 0x1000 bytes removed always, of course).
Could someone help me, please? Is it HANS' fault? Is Awakening the culprit? I have both a N3DS 10.2, and a O3DS 9.9, both with an American copy of the game, both digital. I've gotten the same results with both consoles, in the same way, and with the same evil pixels...
It all started when I read the braindump prerelease thread from the great temper @neobrain. I was delighted at such nice development for the ROM hacking community. I immediately got my 3DS outside of my backpack, where I usually keep it, and using the nifty app, I put my Fire Emblem: Awakening digital copy in a long but straightful dumping process. I went to read more from the marvelous GBATemp community meanwhile.
Three or four hours of reading so many good lines from the great VinsCool later, I went to check my 3DS. It had already finished the dumping task, from which I got a 1 GB romfs.bin file. Using SciresM's excellent ROMFS extracting tool, I managed to get so many media, data and whatnot directories. I started to happy editing several LZ11 compressed files! Oh, the joys of life!
Anyway. After messing up with around four or five files, I decided to check the subtle changes I had done. Using the builder tool from SciresM, I reunited all of the directories into one big file, from which I erased the first 0x1000 bytes as everyone in several threads says it has to be. My excitement was in the clouds when the builder ended its task! Being fairly new to the ROM hacking stuff, I was joyful and already looking forward to everything I could just by changing some scripts and images.
I renamed my rebuilt file as the HANS app stated. It was 000A0500.romfs, I remember, and I put it in the hans folder, which I created in the root directory of the SD card. I know I did it right since HANS didn't print the "INVALID" message it prints when it doesn't find the ROMFS file as specified, or when it's been wrongly edited. Everything went down once I pressed A with the "OK" option selected. My screen got filled by so many weird pixels, just like when opening any homebrew app, but it froze there.
I retried the process so many times, some of which I used the romfs file as I got it, without editing anything, and only removing the 0x1000 first bytes. The same result every time. I even tried using my other 3DS, an old one. The result was the same. Both screens filled by strange lines and patterns of white, pink and green pixels. All of the screen, not only a part, nor only the far left side. I tried to pick a shot using the HOME menu button, but it didn't work. The L + R + down + B combo for getting back to the Homebrew Launcher worked, though.
Thinking that maybe braindump or the extractor app could be doing something bad, I went to filthy places of the www. I had to get a CIA file! What a shame... I thought it could work better than my own dump. I even used the ctrtool.exe file to extract the its contents as described by Asia81 in another thread. I had false hopes...
Nothing. That's what I got. The exact same result, which I won't describe again since I already repeated it several times. I gave up on this. I just couldn't stand up...
I went happy editing Pokémon then, trying to forget all of this for my own good. It worked great. No strange pixels. Only the ocassional yellow screen freezing when booting it up. The romfs loaded flawlessly nearly always. But today, I just thought "Hey, maybe I get some luck with Awakening today". Oh, the suffering...
I don't need to say the exact same thing happened.
I simply can't load my American Fire Emblem: Awakening digital copy with a ROMFS through HANS, even if the ROMFS isn't edited (the 0x1000 bytes removed always, of course).
Could someone help me, please? Is it HANS' fault? Is Awakening the culprit? I have both a N3DS 10.2, and a O3DS 9.9, both with an American copy of the game, both digital. I've gotten the same results with both consoles, in the same way, and with the same evil pixels...
