Bunny5390

Thank you for the help! About $st0, I'm looking through the english chapter text files, and it seems to be used on and off instead of $st1. Here's a chunk of text from the file A001, it uses $st1, then $st0, and then switches back to $st1: I tried changing an $st0 to an $st1 in the text simulator once, and for some reason it made the portrait disapear o_O

Is there a guide/chart anywhere for the text syntax? The FEITS reference guide only has the bare bones basics. I'm especially wondering what $st0, $st1 and $k do.

If I remember correctly, some copies of Smash have the 9.2 update, however as far as I know, cart updates only update the core system files, i.e. not the browser. So he'd have 9.0/9.2 but an 8.x browser. There is a way to update his system to a specific version, but it's currently* rather in-depth unless one of you has either a Gateway card or the game Cubic Ninja. *You can install the 9.2 firmware as a .cia (.cia is a type of 3ds installable), but if you don't have a Gateway or Cubic Ninja, you need to first get a .cia installer onto your 3ds. This is currently rather complicated, but if your interested you can try this. However, the good news is: A much simpler way to do this is currently the top priority of the developers of CakesFW, (one of the CFWs for the 3ds), and they already have a proof of concept working, so I imagine it should be out rather soonish. If you do have a gateway, Cubic Ninja or CakesFW once it's updated, then it should be relatively easy, but I'm not certain on the exact procedure. Gbatemp should have all the info you need though, although it might take some effort to find it -_- Do note though that this carries a small risk, so make sure to back up your sysNAND first. Edit: Also, once CakesFW is updated, you should be able to do the same thing with emuNAND, which carries less risk. The FBI injection method mentioned in my first link should also work for emuNAND if you'd rather not wait.

No, if your sysNAND (console's actual firmware)* is Firmware level 9.4 or higher, you don't have much hope outside of selling/trading your console for one with an expolitable (preferably firmware level 9.2 or lower) firmware level. Apparently Smealum (the creator of Ninjhax) is working on a "limited" version of Ninjhax for 9.7, but I haven't been keeping up with it, so I have no idea if RAM dumping could be a possibility with it (unlikely though). *EmuNAND is a special emulated copy of your firmware that's run from the SD card of an already fully exploitable firmware. So it's meaningless if your console's actual firmware is >9.2.

Welp, looks like I've hit the end of the road. Chapter 3 seems to be un-winable due to freezes. It has the worst freezing so far, every character save Avatar and Lissa freeze the game when selected, and the game freezes right after the "enemy phase" banner fades. I had the idea to try using the auto-move thingie to move the unselectable characters, which worked for a few of them (Stahl, chrom, Frederick and Sully), but froze when it got to others (Vaike and/or Virion), and made no difference to the enemy phase freezing. Trading works fine, but interestingly, when I tried to pair up Lissa, the game froze bringing up the pair-up stats bubble when it tried to select Sully. I'm going to try chapter 3 on another difficulty eventually, just in case it makes a difference.

I'm running into some odd glitches on chapter two. After Sully and Virion appear, selecting Chrom, Sully or Virion Freezes the game. Lissa's paired with Chrom, so I can't test if she freezes too. Edit: Lissa does not freeze the game. I have a suspicion that it's related to either character diologue or help topics, because Chrom selected fine before Sully appeared. As a note, the help topics worked fine in Prologue and CH1. Also I'm on Lunatic if it matters. 3rd Edit: [spoiler=more findings] - Sully and Virion's death quotes and battle animations work fine - Emmeryn has dual-coloured hair. She still has that halo-crown thingie, on top of blue marth hair, on top of her regular blonde double braids - Game freezes if I click support from the world map - Vaike looks epic - Stahl best class swap - Freeze free up until the start of chapter 3 - Sadly the good news ends there

How to rebuild Fire Emblem: Awakening We'll basically be following this tutorial, albeit with a few Awakening-specific steps: https://gbatemp.net/threads/tutorial-how-to-decrypt-extract-rebuild-3ds-roms-run-xy-oras-without-update.383055/ [spoiler=Instructions] 1. Download the pack mentioned in the tutorial, and install python (It says 2.7.7, but 2.7.9 worked fine for me and has some security fixes 2. Download RxTools (unless you don't have acess to the 3ds's browser, RxTools is the easier method by far). I think Notepad++ is just for editing, so you won't need it if you're just rebuilding. 3. Download SciresM's modified RomFS Extractor 4. As far as I know, you shouldn't need to fill slot0x25KeyX.bin because Awakening is an SDK <7 game. 5. Do both steps of the "with internet" part of the tutorial. Make sure the rom has a .3ds extention before decrypting it. 6. Put the decrypted rom in the "packhack" folder with all the tools for step two. Note that the file won't look much different after decrypting it. 7. In step two, make sure to type "no" when it asks if you want to decompress the code.bin. (3ds Builder will recompress it if you accidentally miss it, but probably better to leave it compressed in the first place). 8. Now, delete the "romfs" folder and "DecryptedRomFS.bin", as they are broken thanks to CtrTool. 9. Open a command prompt in the "packhack" folder, and run this command (without the quotes): "ctrtool -x --romfs=romfs.bin rom_filename_here.3ds". It will extract a romfs.bin file from your decrypted rom 10. Run "RomFS Extractor" and select the romfs.bin from step 9. Click go, and it will extract a "romfs_" folder 11. Make any edits you want (for example insert the test file from the first post here). You won't need to rebuild the romfs, as 3ds Builder will do it for you. 12. Run 3ds Builder. Click "Open Romfs" and select the "romfs_" folder. 13. Click "Open Exefs" and select the "exe" folder, then click yes when it prompts to rename code.bin. If it prompts you to recompress code.bin, do it. 14. Click "Open Exheader" and select "DecryptedExHeader.bin". It will detect Awakening and prompt to load defaults, click yes. 15. Uncheck "Media Device: Card2" and ignore the warning. I haven't tried Card2, but Awakening is originally a Card1 game, so I imagine Card1 would be the best setting. If someone tests and finds otherwise, tell me and I'll update this. The main difference as far as I know is that Card1 needs a separate save file, and Card2 saves data to the rom file itself. 16. Click "choose save loc.". Choose where you want to save it and what you want to name it, and then hit go. If all goes well, the program will build a fully playable .3ds! If you still have your decrypted rom, just download everything and follow from step 6 and you should be fine. If it doesn't work, try again from the start with a fresh dump.

IT WORKED. I don't have a way to take decent screenshots, but I'll try to post some crappy camera pictures sometime tommorow. I got up to chapter two, but the game hard froze when I selected Sully, so I lost my save (Gateway can only write the save to the SD if the game closes gracefully). Thus, I won't be doing any more playtesting until tommorow. I'm guessing that the freeze had to do with either Sully not having a myrmidon walking animation (is that possible? I'm not sure how map animations work) or because I selected her right after coming out of sleep mode (rarely games will randomly freeze within a few seconds of waking up). [spoiler=Findings so far] - Everything's vanilla in the Validar dream - Chrom the conquerer clanks as he walks during the cutscenes - The DLC skills show up as "Outrealm skill" because I only have the first DLC installed, but seem to work nonetheless (Chrom has resistance boosted by ten, Frederick has everything boosted by two, and Lissa's rally love seems to work properly). Lissa and Fredrick each have three, and Chrom has one. - Chrom and Lissa have a support level of C - Chrom is OP. - Frederick is also OP, but not quite as much as Chrom. - Cool side effect: On the world map, Chrom the Great rides from point to point atop his trusty steed! - Everything worked fine up until selecting Sully on chapter two. I'm making sure to quit regularly now so that Gateway can properly write the save. I didn't try Virion. Everyone else works though. Nothing more for tonight, It's 5 a.m. and I need sleep.

Whew! After ~5 hours from start to finish of decrypting, properly extracting, and running into countless I-didn't-see-that-setting-so-it-didn't-work errors, I have finally succeeded in rebuilding a working unmoddified Awakening rom. It got past the opening music, title screen, starting a new game and loading the prologue-Validar-dream map as well as all the portraits, and I turned it off after that. I'm now going to try rebuilding it with Vincent's test file, and I should be able to report back tonight. I'll try to post a guide on how to properly rebuild the darn thing tommorow.

Looks like we might owe SciresM another big thank you. This was released a few days ago: https://gbatemp.net/threads/release-3ds-builder.388858/

Luckily, xorpads are now obsolete, thanks to rxTools. It let's you decrypt things straight off the 3ds's SD card through the browser exploit, and it works on anything between firmwares 2.0 and 9.2. Also, just to note, I think xorpads are in the same boat as roms copyright- and sharing-wise, at least according to GBAtemp.

There's actually a very easy way to get savedatafiler to work with Card1 on Gateway. You have to rename the Card1 save you want to edit to 000400000FF40A00.sav (which is savedatafiler's titleid) and then mount the rom with Gateway. After you do so CTR card should no longer show up as broken. It worked for me with Smash Bros., but I haven't tried it with my retail save yet. Although, according to this: https://gbatemp.net/threads/tutorial-how-to-export-import-gateway-card1-sav-to-eshop-3ds-3dz-with-savedatafiler.380246/it's use with retail saves is sketchy :(

So in the end, what exactly broke what where with unicode characters in the decrypting/unpacking/repacking/re-encrypting process?

It shouldn't be too far off - Pokémon RAM hacking is now a thing: http://projectpokemon.org/forums/showthread.php?44551-Web-Browser-RAM-based-Pokemon-Injection&p=195497, and you can apparently even do some (pseudo?) save editing: http://projectpokemon.org/forums/showthread.php?44618-RAM2Sav-Save-File-Dumping-Injection-for-X-Y-OR-AS. You can even inject VC roms into RAM to temporarily replace one you're currently playing: https://gbatemp.net/threads/injecting-roms-into-vc-with-only-the-web-browser-sure.379760/

I really have to catch up on how the whole decrypting/extracting/repacking process works, and what breaks where, so I don't know how useful this might be, but this was recently released: http://gbatemp.net/threads/release-romfs-builder.379330/