-
Notifications
You must be signed in to change notification settings - Fork 338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[*] Configuring NetHunter for Termux ... ./install-nethunter-termux: line 361: chroot/kali-arm64/etc/resolv.conf: No such file or directory ~ $ #436
Comments
I deleted and downloaded Kali more than once and it did not solve it despite the availability of all files. I do not know what the problem is. |
Do you have root? |
No |
I encountered the same problem; my phone is running Xiaomi HyperOS 2. |
!!! I USED THE OFFICIAL INSTALLER SCRIPT (https://www.kali.org/docs/nethunter/nethunter-rootless/) !!! Okay, this is indeed an error from their script (Kali Nethunter Official). If it's not, then what else? So they changed the directory of the Nethunter into the "chroot" folder (because previously the directory was in HOME) and at first it was safe, but I don't know why now it's like that (I don't know what they changed). So the solution (for now) is to "slightly" edit the installer script (install-nethunter-termux):
Hope this helps :) |
!!! I USED THE OFFICIAL INSTALLER SCRIPT (https://www.kali.org/docs/nethunter/nethunter-rootless/) !!! Okay, this is indeed an error from their script (Kali Nethunter Official). If it's not, then what else? So they changed the directory of the Nethunter into the "chroot" folder (because previously the directory was in HOME) and at first it was safe, but I don't know why now it's like that (I don't know what they changed). So the solution (for now) is to "slightly" edit the installer script (install-nethunter-termux):
Hope this helps :) |
[*] Configuring NetHunter for Termux ...
./install-nethunter-termux: line 361: chroot/kali-arm64/etc/resolv.conf: No such file or directory
~ $
The text was updated successfully, but these errors were encountered: