Getting my facts straight about installing Nethunter

[bpartin2009]

So at https://github.com/offensive-security/kali-nethunter/wiki it says "about downloading Nethunter" that you will need nethunter-generic-[arch]-kalifs-.zip as well as a kernel-nethunter-[device]-[os]-.zip. which can both be found in https://build.nethunter.com/nightly/2017.11-18-1618/ but at https://github.com/offensive-security/nethunter-LRT the instructions say to "Put the NetHunter zip image you downloaded or built in the /kaliNethunter folder.". I am assuming the full kalifs generic zip or if a built scipt is used the "--rootfs full" option must be used. So using nethunter-LRT do you put the genric (or built full option) in the kali folder, then later go in with TWRP and flash the kernal for the device secondly? Even so, in a tweet with binkybear he mentioned the when you build... "you add the full fs option but you actually have to include the file. https://build.nethunter.com/kalifs/kalifs-latest/ ". Does that mean the put the latest kalifs in the LRT kali folder then later flash the full option built zip file? My issue is that the LRT steps refer to one zip file, but other people and the nethunter wiki refer to two zip files. The wiki says to flash the full generic rolling zip first and then the kernal zip last but there is no mention about selecting both files in TWRP at the same time or letting TWRP flash the full zip first, then after full reboot go back into recovery reboot with TWRP and flash kernal zip.

In offensive-security/kali-nethunter#836 simonpunk said that the build.py --rootfs full option can only build the flashable zip but not the kernel itself. Does this mean you still must download a correct kernal from the https://build.nethunter.com/nightly/2017.11-18-1618/ area and flash that even after your full fs option build.py zip file? If so, binkybear is saying a built zip with --rootfs full needs to be accompanied by the https://build.nethunter.com/kalifs/kalifs-latest/ kalifs.... then simonpunk is saying you need the kernal from https://build.nethunter.com/nightly/2017.11-18-1618/ as well? Maybe I'm just really confused but some clarification would be nice.

Also, I and a Nexus 9 (flounder) Nougat 7.1.1, kernal 3.10.103-gcbed67d00ed-dirty, build # N9F27M and a Nexus 6 (shamu) Nougat 7.0m kernal 3.10.40-g9f039ba, build # NBD91P.
With the Nexus 9, the nethunter-LRT would stick in fastboot commands (adb would work, but fastboot oem unlock would be waiting on device and device would stay at the white recovery reboot screen with the LOCKED indicated at the top and never go to the black screen comfirming unlock). I had to use wugfresh's Windows Nexus Tool to get me to the point where SuperSU and TWRP were installed and then I flashed a 9.6 MB kernel-nethunter-flounder-nougat-2017.11-18-1618.zip first by mistake and later flashed a "build.py -d founder --nougat --rootfs full" zip file. I sort of seems to work, I have nh-terminal, and nh-app. Has issues where I can't get metapackages, monstart-nh (no bash script found), and I have to run custom commands 4 or 5 times to work (most of the time nh-term just comes up and nothin happens). The Nexus 6, I haven't done anything with yet.

Is there a way to 100% start over with the Nexus 9 if I messed up (apparently I did) with my above process?