Beta Issues

[NetviperZ]

1- there is an error when checking Chroot directory (and yes my chroot directory is correct) 2-my external adapter ( TL-WN722N ) external adapter is no longer recognized in nethunter chroot after installing this version 3- device reboot randomly when external adapter is plugged

[chrisk44]

1. When you say error when checking, you mean it fails the test or does the whole app crash?
2. Hijacker does not change anything in nethunter chroot.. It just chroots to kali, sets up the environment variables and runs reaver. If you didn't try reaver with pixie-dust, Hijacker didn't even touch kali. If there is a problem just try a reboot...

[NetviperZ]

yes the test fails, but my nexus5 keeps rebooting everytime I pluggin my adapter and that is just happens with this version

[chrisk44]

wait, you mean that you installed the new version of Hijacker, and now everytime you plug in your adapter, the phone reboots?!

[NetviperZ]

exactly

[chrisk44]

this doesn't make sense... did you even run reaver with pixie-dust?

[NetviperZ]

The test failed, so this option has been disabled

[chrisk44]

Then I don't know what has happened with your adapter, but since the test failed, the app didn't use the chroot installation. Even if it succeded, you'd have to run reaver WITH pixie dust to use the chroot, otherwise it just uses the binary that comes with the app.

[NetviperZ]

In chroot reaver with pixie-dust worked well before with my external adapter, yes its really weird.. i will make a restore and see what's going on

[chrisk44]

That's good... About the test failing: The app checks if /data/local/nhsystem/kali-armhf directory exists, and boot_init in /system/bin. If one of these is missing, then it fails. Please check if these exist, and tell me. The binary might be somewhere else, I'll need to add it.

[NetviperZ]

i cheked before and yes /data/local/nhsystem/kali-armhf exists, however, in the /system/bin directory there is a file named bootkali_init not boot_init

[chrisk44]

Yeah that's what I meant. I don't know why it fails, I will look into it. Does your adapter work?

[NetviperZ]

Of course I just tried it on my computer and it works

[chrisk44]

i mean on the nexus...

[chrisk44]

By the way, what ROM are you running exactly?

[NetviperZ]

Not anymore.. i have to restore my phone first, i will do it tomorrow since I work on it now, i just tried another adapter (AWUS036NH) and it works (inside nethunter chroot), once I pluggin again the first adapter the phone reboots

The ROM is a modified CM 14.1 (nougat) *Linux kali 3.4.0-cyanogenmod-g7ae20b3-dirty

[AutinMitra]

I am running the same ROM as @NetviperZ, and I also have Kali chroot failed on the tools test. My wifi card is the same as netviperz's, tested and working.

[chrisk44]

Yeah it doesn't detect the chroot directory for some reason... Actually, right now i'm wondering why it detects it on mine, rather than why it doesn't on nethunteros... I'll just install it...

[AutinMitra]

Anyways, I found a pixiewps binary for android (found here: https://github.com/aanarchyy/pixiewps-android). I don't know if it will work though.

[chrisk44]

pixiewps is an offline tool, what i need is the reaver 1.5.2 which has pixie-dust integrated.

[AutinMitra]

Can we reopen this issue as chroot detection still doesn't work?

[chrisk44]

do you get directory or bootkali_init not found when you run the test?

[NetviperZ]

Indeed, chroot detection still doesn't work, i get " Chroot directory not found"

[NetviperZ]

@AutinDroid did your external adapter ( TL-WN722N ) works with this rom ?

[chrisk44]

Guys it works on my device with NetHunterOS...

[AutinMitra]

My Adapter works.

[AutinMitra]

I get directory not found. I would also like to report v.18 not responding upon start.

[chrisk44]

The app hangs when denied su permission, you need to go to settings and force close it, and then open the supersu app and remove the stored denial, so it will ask you again. As for the chroot directory, I can't figure out what is the problem, it detects it fine on my device both with NetHunterOS and CM 14.1 caf...

[AutinMitra]

SuperSu was not denied and I have tried multiple times.

[chrisk44]

busybox installed, removed and reinstalled the app?

Is there an ANR? If so, send me the traces.txt from /data/.

[NetviperZ]

@AutinDroid I can't use my tp link because of this kernel panic or issue with the firmware maybe, What version exactly do you use ? @chrisk44 I get also directory not found

[AutinMitra]

Maybe it's a problem with the stock firmware in NethunterOS. I use NethunterOS with the kali rolling full package, which may update the firmware (I'm not sure). I'm positive that it's a problem with the firmware or system, not Hijacker.

[AutinMitra]

I also forgot to mention that I had busybox installed (the one that nethunter comes with) and have uninstalled and reinstalled multiple times.

[chrisk44]

I don't know, I installed NetHunterOS, nethunter zip, hijacker, ran nethunter app, run hijacker, it just worked.

[AutinMitra]

Just wondering, how does the app start chroot?

[chrisk44]

bootkali_init to ensure that kali is booted, then open a su shell and run: chroot /data/local/nhsystem/kali-armhf /bin/bash -c ' export USER=root && export SHELL=/bin/bash && export MAIL=/var/mail/root && export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin && export TERM=linux && export HOME=/root && export LOGNAME=root && export SHLVL=1 && export YOU_KNOW_WHAT=THIS_IS_KALI_LINUX_NETHUNER_FROM_JAVA_BINKY && monstart-nh && reaver -i wlan0 -vv -b 18:44:E6:C3:74:48 --channel 3 -d 1 -l 60 -K 1 '

as one command...

[NetviperZ]

Which nethunter zip did you installed? I followed this tuto https://gist.github.com/binkybear/8f0f4eee292d5263372f47c3c3edd08e

[AutinMitra]

I used the 11-26 kalifs full rolling package. I don't know about @chrisk44

[AutinMitra]

Ran the command and got "libsigchain.so from LD_PRELOAD cannot be preloaded (cannot open shared object file)"

[chrisk44]

Yes that's a problem with nethunter chroot and the reaver binary in it.. There's nothing I can do about this. I get that too, but it doesn't stop reaver from running... Obviously it doesn't work because i'm not on nethunteros but it starts and waits for a beacon.

[chrisk44]

About that not responding on start thing, is that still happening?

[AutinMitra]

The responding on start issue happens on v.18, v.19, v.19.2.

[AutinMitra]

I will try to install a different ROM (NethunterOS hammerhead, caf not included) and test the app.

[AutinMitra]

I think I have found the problem why v.19.2 isn't working. Apparently when I grant root access, the Hijacker UID is not granted root, nor is prompt for root. It cannot be found in SuperSu app.

[chrisk44]

The app itself never gets root, it just launches shells with root privileges and does whatever it needs to do using them.

[AutinMitra]

@netviperZ Do you have the app hanging issue?

[NetviperZ]

@AutinDroid no not really, im using now the last CM 14.1 and its works just fine

[AutinMitra]

I've installed the last NethunterOS and the hanging issue has stopped. I still have the chroot problem. @NetviperZ do you have no chroot detection?

[NetviperZ]

@AutinDroid Unfortunately no, there is a new more stable version of nethunteros? because it bugged all the time

[NetviperZ]

After having tested the last version, here are some remarks:

1 Manufacturer name for clients no longer appears as before (It worked well before v.18) 2 You have to enter the path of worldlist everytime time.. and also it will be preferable if the last handshake captured will be selected automatically 3 it will be very practical if we can sort APs by their security 4 adding a filter of WPS only for quick attack via reaver will be cool 5 No handshake recorded from airodump-ng

[chrisk44]

1. When you say it doesn't appear, you mean it says "Unknown manufacturer"? If yes, I changed something, let's see if it works for you.
2. Fixed, done.
3. You can filter them by security.
4. This would require changing a very basic part of the code, but I will do it at some point.
5. There are 2 ways to create .cap files. The first is to enable the option to capture every packet when airodump runs, which will result in cap-01.cap files rarely containing handshakes. The second is to try to crack a network password, in which case a file named handshake-01.cap (or wep_ivs-01.cap for wep) will be created, but there is no guarrantee that it will contain the handshake. Even if there happened to be a handshake while you were watching, it's not certain that you will capture it. Distance and signal strength are at play here, but more importantly, some networks are immune to this. I actually thought that this worked on every WPA/WPA2 network and I was going crazy when I implemented the cracking feature because it would never capture the handshake from my network. I realized that if the network used AES encryption, is would never capture the handshake, even if it was being conducted from my nexus itself, or my laptop right next to me. It worked as soon as I changed it to TKIP. Now, if you are trying to capture a handshake and Hijacker tells you that it got it and stops, but there is no handshake in the file, that's a problem. Keep me updated on this.

I have changed many parts of the code and implemented some more checks. I will upload a new version later today.