PDA

View Full Version : Nethunter on OnePlus One - several odd things I cannot find answers to on forum or in Google



novicehacker
2019-01-30, 01:52
Hi everyone. I always spend at least 2 days looking for log entries or similar threads or something that can give me a hint on how to get started but I'm completely at a loss currently. Hopefully someone smarter than myself can help me out.

Quick details;
Oneplus One with Lineage 15.1 + addonSU
Latest BusyBox installed from Play Store
Latest nh-term & nethunter APKs from here: https://github.com/offensive-security/kali-nethunter/tree/master/nethunter-installer/update/data/app
Newest kalifs-armhf-full.xz from here: https://build.nethunter.com/kalifs/kalifs-latest/

Once base system was installed I copied kernel-nethunter-oneplus1-orea-20181030_120958.zip over top (thank you to whoever created that).

Now the oddnesses

1 - The first time I ran an HID attack it worked perfectly, three times. I moved on to an nmap scan of the AP and the phone crashed. Now the HID devices do not show up automatically. I have to manually do a setprop sys.usb.config hid from the androidsu (it doesn't work from kali chroot).

1.1 - If I try to enable the HID devices while the USB is plugged in the phone crashes. If I enable them and then plug the USB in the phone crashes.

2 - As previously stated, trying to do an nmap crashes the phone. Everytime. I've tried doing on over SSH so I have some details after it crashes, but even at debug level 9 all I get is that it's resolved the host and is starting the scan.

3- The Nethunter app goes through its startup process, but doesn't seem to be able to actually start any service on-boot.

Since the phone crashes everytime I have no logs to look at. I've tried wiping it clean and doing everything again and have the same issues. If anyone can give me an idea where to start looking it would be most appreciated.

re4son
2019-01-30, 09:00
Hi novicehacker,

You can try the latest test release of the nethunter app:
https://github.com/offensive-security/kali-nethunter/tree/2019.1/nethunter-installer/update/data/app

That's been updated for Oreo and Pie

novicehacker
2019-01-30, 12:40
Thank you re4son. Your advise has helped me out many times, I'm not sure how I missed those updates.

After some more trials I've found the HID issues are basically fixed. A cold boot results in the HIDs missing, while a reboot seems to let them auto detect.

It still can't seem to start services on-boot. I can fix that with a cron job if that starts at boot.

The bigger issues is nmap still crashes the phone entirely. I should be able to do that with the internal wireless correct? Fing works. cSploit core install also crashes the phone.

Any ideas?

re4son
2019-01-31, 09:37
You are probably just missing a couple of recent updates that are important for oreo.
The best thing would be to build a new image. I've asked Phreya (https://forums.kali.org/showthread.php?42494-Kali-NetHunter-for-OnePlus-One&p=84432#post84432)if he could add his kernel to the nethunter-devices repo so you can easily build it yourself. I'm sure it's his kernel that you are using.
Let's wait for his response. I think I've tracked down his github repo and I'll ping him there as well to speed things up. Fingers crossed.

novicehacker
2019-02-02, 02:40
Thanks for the reply Re4son. Not sure why I didn't get the alert that time.

I honestly have no idea how to do that, but I'm sure with some digging I could figure it out.

That makes sense. Since Fing works in Android and I see nothing different between the nethunter nmap and nmap on Kali Pi ;) I'm inclined to think it's a chroot / kernel issue.

0E 800
2019-03-22, 21:01
Thanks for the reply Re4son. Not sure why I didn't get the alert that time.

I honestly have no idea how to do that, but I'm sure with some digging I could figure it out.

That makes sense. Since Fing works in Android and I see nothing different between the nethunter nmap and nmap on Kali Pi ;) I'm inclined to think it's a chroot / kernel issue.

I have the same issue with Nmap causing the device to reboot.
Using Oreo Rom on kernel 3.4.x on Flo (Nexus 7 2013 wifi)


Is there any update on this?

I notice that the command
nmap -sL 192.168.1.1/24 does not reboot the device.
`
nmap -v 192.168.1.1/24` does cause the reboot within 5 seconds.

Possibly related to https://github.com/nmap/nmap/issues/1112

Patched here: https://github.com/nmap/nmap/commit/6889a2f6a5c6ef8f634826d073da839baf4acdfc

novicehacker
2019-03-24, 15:24
Hi 0E 800,

Thank you for replying. No there's no update, I shelved the project for others while waiting for a reply.

I've tried a few nmap commands including the two you suggested and any nmap command reboots the device. I'm more sys admin than developer and never done any Android dev work but do have a Linux background so I could may be compile something to make this work if I had some pointers.