I did.
Edit: The result file I renamed to hs.app was originally called "inject.app" instead of " FBI_inject_with_banner.app," did I possibly mess something up there?
Last edited by UnassumingVenusaur,
Edit: The result file I renamed to hs.app was originally called "inject.app" instead of " FBI_inject_with_banner.app," did I possibly mess something up there?
Well, that's the one I *was* trying to inject. I don't know why the name of the file turned out different from the instructions because I followed the steps. Bu I *was* supposed to change the name to hs.app, after I go.bat was done, right?
Okay. (First off, I have an O3DSXL if that's relevant.)
- I booted Decrypt9WIP from the homebrew launcher, went to EmuNAND options, selected Health & Safety dump, and told it to save the file as "hs.app"
- I copied this hs.app file into "input" folder of Universal Inject Generator, and then copied FBI.cia into it as well.
- I ran go.bat
- This, I believe, generated a folder called "work." Inside that folder was a folder called "dummy_romfs" with a file called dummy.bin in it, a file called hs.app (which I believe is identical to the starting one), and a file called "inject.app". Note that this file name is different from what the tutorial says it should be (FBI_inject_with_banner.app) so I suspect something might be going wrong here.
- I copied inject.app to the root of my SD card and renamed it hs.app
- I booted Decrypt9WIP again from the homebrew launcher, selected EmuNAND options, and then Health & Safety Inject.
- I inputted the button sequence to allow the injection, and got the aforementioned "Inject failed" result.
I am not at home to be sure but i dont remember getting my file in a work folder. I remember the program creating a file called FBI_inject_with_banner.app or something similar. Look in other folders. If not, run go.bat again. You are using the wrong file to inject.
Last edited by uribemaster,
Ok, I ran it 3 different times with the same result, I think something in go.bat itself is not working right for me. Could I possibly just send my dumped hs.app to someone and have them run it in go.bat and see if it works any differently?
Once i get home from work, ill see what i can do. Sorry im not much help while at work haha. For now though, you could just use fbi in the homebrew browser to install fbi.cia. itll be the same. Only problem is that it may be hard to differentiate emunand and sysnand
Last edited by uribemaster,
Haha don't worry, it's no problem. I have someone else I can message about it who has gone through this process before, I'll try them first.
So I'm an idiot and used Tiny Format while in EmuNAND. Is there anything I can do? Would using Tiny format on my SysNAND fix everything? Or do I have to go through the whole emuNAND process again? The emuNAND still had FBI and would install cia's so I'd assume not.
You can use tinyformat on any NAND, using it on emuNAND means all of you sysNAND content will stay in sysNAND and your emuNAND is a fresh empty NAND, it is simply suggested to use it in sysNAND because you're not supposed to touch sysNAND ever and using tinyformat on it moves everything into emuNAND.
You can create a fresh new emuNAND if you want, but if you didn't really have anything in sysNAND worth transferring over to emuNAND then it's fine.
Well, the problem is in emuNAND now I can't access all of my digital games and downloads. I'm also not sure if I could re-link my old NNID to it? I want to be able to access the internet and download DLC and the like.
In that case, you'd need to make a new emuNAND, and use tinyformat on sysNAND after you make your new emuNAND.
Copy everything from your SD into your PC and copy everything, run Emunand9 again to make a fresh emuNAND, copy everything back into your SD and run tinyformat on sysNAND, this will format your sysNAND, transfer all of it's contents into emuNAND while also unlinking them.
Okay, awesome, thanks to help from @Sgt. Lulz I got my emuNAND restored. However, I'm still having trouble getting the homebrew launcher cia working correctly. When I open it it boots into the CtrBootManager, and when I use that to try to select the homebrew launcher it freezes. This is puzzling as it did the same thing the very first time i tried it (I tried to boot it through HBL8.3dsx that time), but the seconf time I tried it on the old emuNAND i used boot_hb.3dsx and it worked. This time I tried to use that same file again and it froze. Any advice or help?
This is because it downloaded a new payload for you emuNAND, what FW is your emuNAND?
You'll need to locate the payload for your current emuNAND FW in your SD, run it through HxD, find the string "boot.3dsx" and replace boot with HBL8 so it reads "HBL8.3dsx"
Yeah, the "hold Y to download payload to SD card" advice is outdated as of 1.1.
hblauncher_loader is booting to CTRBootManager because of the unedited payload, so what you have to do is edit the payload to make it boot HBL8.3dsx instead, as stated above.
Okay, where is this payload I'm supposed to edit on my SD? What is it called? Or does that vary?
Similar threads
