the issues with the guides is that it's evolving quickly every day. you have to follow the progress daily to not be lost, until it's becoming more stable and "unique". currently, there are a lot of things which can do the same thing, and it tends to merge together little by little, so at the end there will probably be a single solution.
If you already have HaxChi installed, you did the first step for a permanent persistent hack. (it's not permanent, you can revert and uninstall it)
You can now launch HBL quickly.
I don't know which version of haxchi you installed, but if it's the last one (CBHC+Haxchi) it already comes with a signature patched mode, so you don't really need to add anything else.
did you install CBHC too ? do you want or need CBHC?
CBHC is "Cold Boot HaxChi", it's a way to auto-boot haxchi channel at console boot, entering in a signature patched console right away without the need to "click" on haxchi icon yourself. It's REALLY just a step for lazy people, and it's safer to not install coldboot if you don't need it. I would recommend waiting again until all is becoming easier/safer. But if you want a coldboot option, use CBHC instead of the previous method of colboot (coldboothax, Phoenix's installer, etc. they work but could be misused and brick your console, while CBHC is designed with additional patches to speed coldbooting time).
the fourth different methods:
Boot -> system menu -> manual launch of haxchi => homebrew or cfw, or anything setup using config.txt
boot -> quick boot menu -> haxchi => same as above, loads way faster but "standby mode" is usually not recommended to prevent auto-update from nintendo.
boot -> system.xml (coldboothax) -> haxchi => same as above, but dangerous (you could end in infinite reboot loop and/or brick your console)
boot -> CBHC (replaces haxchi) => CFW patched sysNAND, or homebrew launcher (press A), or fw.img on SD, or Mocha on SD ! (you have a menu at install to choose what to boot, CBHC doesn't use config.txt)
if you don't use CBHC, you can launch a CFW loader (loading a fw.img file from SD) from the homebrew launcher or from Haxchi channel, which can be a simple signature patched firmware (but you already have that with haxchi+CBHC), or redNAND (if you compiled a redNAND fw.img), or Dimok sysNAND cfw (if you compiled it).
if you use CBHC, you need to install it AFTER you installed haxchi and made sure it works fine. (reboot, test, etc. !)
CBHC will replace haxchi with a special haxchi version which does not use config.txt, instead it has hardcoded boot options : auto-re-patched sysNAND (repatch when exiting settings), homebrew launcher, fw.img or mocha.
fw.img is not needed anymore since yesterday (dec 12th 2016).
Dimok released Mocha CFW, which applies all the different and existing patches on the fly in RAM, instead of patching and generating different fw.img files that you have to keep on your SD card without remembering which does what... (confusing!)
from Mocha (launched from HBL or from CBHC, or standalone haxchi) you select if you want to redirect NAND to SD.
RedNAND is not something you "install", it's a feature of the custom firmware. it's bad to make a different between "cfw and rednand", both are the same CFW, just with different features.
you choose whether you want NAND access to be redirected or not when you launch Mocha.
Mocha will always patch signature check, add IOSUhax nod to allow ftpiiu everywhere, wup server, etc. whether you choose to redirect NAND or not.
On first use of redNAND option, your SD card will be formated to add a copy of your NAND before the FAT32 partition. backup all your files first!
But again, do you really need or want a NAND redirection? you need to know what it does, and why you will need it.
if all you want is play games, you don't need NAND redirection. install your games on sysNAND or USB.
if, on the contrary, you want to develop a homebrew or a hack, or mod your console (edit the menu themes, edit xml files to see what happens, etc.), then you WANT to use NAND+SEEPROM+OTP redirection option, or you'll brick your console. You'd better brick your NAND copy on SD (redNAND) than your real one (sysNAND).
Now, to answer your question "what to install after haxchi":
1) best choice is CBHC if you want autoboot.
- it has the fastest booting time into patched sysNAND.
- it can auto-boot mocha (for users who want to auto-boot redNAND), but don't autoboot mocha if all you want is a patched sysNAND ! it will take a long time to boot while CBHC can do it faster without mocha.
- just install the Homebrew launcher channel version and launch homebrew from here instead of using haxchi with config.txt to boot different homebrew at boot.
2) nothing else if you don't want autoboot.
- launch haxchi channel manually to boot whatever you like (homebrew launcher, a fw.img, mocha, redNAND, etc.)
- your console will be "clean" and non sigpatched at boot. you can enable signpatch and hacks manually by launching haxchi channel yourself, when you need it.
- you don't need to install the homebrew launcher channel as you can boot it with haxchi channel (set a button to load HBL from SD card). You can install the homebrew launcher channel if you want but you will have to PATCH sysNAND first before launching it by loading haxchi (set a button to load simple signature patcher from SD).
)
