Related
I work with Cisco devices on a regular basis. To connect to them, I need to use a DB9 serial.
I have tried the usb to serial Prolific 2303 chipset but it isn't supported in the OS (I'm not sure why this was removed from the Android Linux kernel because it is standard in Linux kernel 2.4.31 and later but anyway...)
Anyone know of a way to get serial connectivity so I can use this tablet as a true laptop replacement? Maybe a serial to bluetooth would work? Samsung says the bluetooth supports SPP but I don't want to dish out $70+ to find out it doesn't work.
Maybe someone familiar with compiling kernel modules for Android could assist? I have the pl2303.c source code but I'm not familiar enough with compiling kernels or kernel modules to attempt this.
I've been looking into this myself the past couple of days. The kernel is not compiled with support for USB-Serial converters, but all of the code is there. It looks like the kernel would have to be recompiled along with the required modules. Here is the source I'm using: https://github.com/pershoot/galaxy-2636
So far I've just looked at config and it is easy to enable the required modules, but I haven't managed to get the kernel compilation and ARM toolchain to work just yet.
samsung source
I noticed the pl2303.c and pl2303.h are in the Samsung source I downloaded.
I'm going to try to compile a kernel module in the next week.
I'm fairly shocked this hasn't been a bigger issue. We can't be the only ones wanting this functionality - especially since Samsung support basically told me to pound sand.
I've managed to compile an ICS kernel with the required configuration and modules, once I figure out how to get it on the device I'll test it. If it works I'll build a honeycomb kernel as well and post both in the dev section.
That is fantastic! I'm having issues getting my cross compile to work properly.
Well, I managed to build the kernel & modules properly but the adapter still isn't recognized even with the modules loaded. I think there might be more to the problem than missing modules
I read today that the main linux kernel and the android fork are going to be merging. Maybe that will lead to better device support.
Hello. I have decided to finally register on this forum as I am in process of creating my own kernel which will be aimed towards penetration testing. So far I have come close to releasing the alpha build however I found a problem. I compiled it using ralink usb drivers so i can get my usb wifi adapter working for aircrack. I have succeeded at doing that however when I flash this kernel the internal wifi isnt working. It will not let me turn it on which basically means the device isnt recognized(right?) I do not have much experience in kernel development but I would appreciate help :angel: If required I could upload the kernel as it is now. logcat attached as i cant post links pre 10 posts -_-
Archlinux Phone for Sony Xperia S
Part of GNU/Linux for Android devices project
First of all, this project is not ready for end users but everything is provided to build an archlinux system for the Sony Xperia S. So you will be able to have a complete system with GPU hardware acceleration, support of vibrator, sensors, GPS, wifi etc (everything is not yet tested like bluetooth, nfc...). Graphical applications are already able to display (Qt/Kwin tested but GTK3/kwin should be ok too).
This project is not just for this device and is really open to support multiple devices and GNU/Linux distributions. So you can share this project everywhere (xda, distributions forum...) ! Contribution are welcome and can be discussed directly on this thread to share efforts.
Introduction
This is a project to create a convergence between the desktop and the mobile/phablet/TV... so to build new mobile OS based on existing GNU/Linux distributions with the most common parts possible. We share some common base between mer-hybris (SailfishOS) and Ubuntu Touch but the architecture and integration are different (refer to Architecture).
Cell phone are powerful and expensive for flag ship so why just use it as a phone ?
Imagine that your cell phone can become your core device ! Plug it to a big screen and this is your workstation ! Plug it to an 'empty' laptop (no CPU, no RAM needed ...) and this is your laptop ! Move everywhere and this is just your mobile phone !
This is what motivate this project.
Applications
Applications are critical on a mobile platform and we hope to support Android application as soon as possible (need further studies to complete the architecture).
GNU/Linux applications are already compatible but not always adapted for a mobile phone for now but... We hope a lot of plasma mobile and KDE convergence guideline for Application developers
Source code
There is few projects and some fork available under my github but if you want to start to port a new distribution or a new device, everything is documented in the gnulinux_support project.
Android needs to be modified but we deliver a solution that permit to be integrated upstream and so to compile Android or Android for GNU/Linux with the same code.
For now we have only Android 5.1.1 patches available but 6.0 will come soon. CyanogenMod 12.1 and 13.0 can be a good target to support a lot of devices in the future (or at least to simplify the portage process per device).
manifest for Sony Xperia S
manifest for Pure AOSP 5.1.1 (can be used for Nexus devices)
Documentations
Architecture schema
Main documentation
Archlinux installation
Videos
https://vimeo.com/177893595
Distributions supported
archlinux (archlinuxarm)
Project status
This project is in an early stage and for developers but we created solid base of works and the portage of plasma mobile, ofono, ... and amazing features will start over those solid base to provide an end user product
Todo :
pulseaudio support for GNU/Linux - Android Hw (and maybe for Android to support sound from Android application)
fix libinput/kwin environment
ofono (or maybe an alternative/hybrid solution that can use the Android Telephony Framework ? no study yet on this point)
flashing after boot.img package update + generation of a custom initramfs
security with crypto, firewall and SELinux (SELinux or equivalent integration will mainly depend of the distribution support but for now this is disabled)
plasma mobile or other ?
localisation framework (see freedesktop project)
OMX
merge everything possible to every upstream projects used to create GNU/Linux for Android devices
overlayfs into kernel ? (not mandatory but can be a great solution for the Android rootfs and schroot)
... (a lot that I forget)
BUT despite this long list of todo... We already did :
New architecture (GNU/Linux and Android integration, systemd, libhybris, chroot, wayland ...)
SurfaceFlinger Composer supported by Qt and Kwin
schroot for Android (Android can run into a chroot and we can interact easily with it)
systemd integration (with reboot to bootloader and recovery, Android /init support, etc)
libhybris_ext (compatibility version with support of Android 5+)
Android integration with GNULINUX_SUPPORT (rc, init, busybox, ramdisk, OTA ... adaptation)
clean rootfs with only 2 symlinks that permit to see that we are on an Android device (nothing more)
OpenGL support (with backend hwcomposer or SurfaceFlinger)
Archlinux support (OTA and packaging)
Design a possible solution for a lot of other GNU/Linux distributions (share architecture and Android adaptation)
Documentation
Download
Binaries will be available when really usable for end user. For now everything can be compiled from source code
Devices supported
Sony Xperia S (nozomi): work in progress (this is our reference device)
RESERVED
I will provide OTA file, binaries (archlinux packages), images and video to show what is working and how really soon
Very interested in this,is HDMI out working?
Στάλθηκε από το 6045Y μου χρησιμοποιώντας Tapatalk
Demetris said:
Very interested in this,is HDMI out working?
Στάλθηκε από το 6045Y μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
Multi screen is not yet supported on kwin_wayland so for now I have just focused to render on the main screen (0) but it will be possible to do it for hdmi (1). But for sure I hope to support hdmi output.
For now I will focus to port plasma-mobile/ofono/pulseaudio.
Impatient to try another gift from genius mickybart.
Waiting............
wow something new
waiting eagerly...
lovely, cannot wait to try it
finally there is hope to ditch android, ios and windows
I have not a lot of time to work on this project with the release of nAOSP b11 but once done I will rework on it and provides binaries for Devs.
But, I think that this "new OS" powered with plasma is a good choice and I'm happy to see that plasma 5.7 integrate such kind of features :
https://www.kde.org/announcements/plasma-5.7.0.php
https://blog.martin-graesslin.com/blog/2016/05/virtual-keyboard-support-in-kwinwayland-5-7/
Great improvement have been done on Wayland support too.
If some of you are interesting to do some packaging with Archlinux, I'm really interested to get some help to provide a usable system for end user. The work for now is more too package/install user tools (so integration of components). I miss pulseaudio and ofono patching but I'm optimist to solve every issues.
finally nAOSP 6.0 b11 and b12 took me more time than expected but I'm back on this project.
For information, I updated everything to Qt 5.7.x support.
Some pull request have been done and are in discussion for at least qt5-qpa-hwcomposer-plugin (mer-hybris).
I decided to don't provide binaries for now as there is not a lot of sense to do it except if you are interesting to help the project (mainly to package some stuffs, integrate tools for GPS, ofono, pulseaudio etc).
I just finalized to record a small video. I will cut it and upload it to prove that archlinux arm phone can be a reality with the proposed new architecture (and on our Xperia S).
I will work again on the kwin/libinput issue. Maybe just a logind/dbus/kwin discussion issue. Once fixed that should permit to have a graphical keyboard by default (I know that for iOS or Android this is normal... but not really on a GNU/Linux desktop) !
I continue to look for help on this project and if you can create some packages like the one for plasma-mobile and derived repo let me know in PM or in the thread.
small video of the project
https://vimeo.com/177893595
Great achievement today
libinput is working and so I'm now able to move windows, plug a keyboard to write a text file, plug the mouse (pointer is not visible) ...
Menus are well displayed now with the good size.
Next steps : pulseaudio, wifi, plasma-mobile... (and bug fix on the kwin backend).
wow mickybart !. u just struck my interest in coming back to this phone! amazing work. my phone was unusable and parts needed replacement. looking at the activity of yours in this section made me repair the device and try out your work.. cheers mate! keep going with ur awesome work!
OnePlus X (onyx) port
I'd like to port this to OnePlus X (onyx). What's a preferable Android OS that I should use? The device comes with manufacturer's OxygenOS, which was made open source. OxygenOS was based on Android 5.1.1. I've also used Cyanogenmod 13 on this device. Out of these 3 options, I prefer CM. Any considerations I should keep in mind making this choice?
latgarf1 said:
I'd like to port this to OnePlus X (onyx). What's a preferable Android OS that I should use? The device comes with manufacturer's OxygenOS, which was made open source. OxygenOS was based on Android 5.1.1. I've also used Cyanogenmod 13 on this device. Out of these 3 options, I prefer CM. Any considerations I should keep in mind making this choice?
Click to expand...
Click to collapse
I have a Sony Xperia S and a OnePlus One and I'd like this port!
On my OnePlus One I'm using Ubuntu Touch that is very cool but apt-get doesn't work so I can't install other apps.
I really like this on my "old" Xperia S !
latgarf1 said:
I'd like to port this to OnePlus X (onyx). What's a preferable Android OS that I should use? The device comes with manufacturer's OxygenOS, which was made open source. OxygenOS was based on Android 5.1.1. I've also used Cyanogenmod 13 on this device. Out of these 3 options, I prefer CM. Any considerations I should keep in mind making this choice?
Click to expand...
Click to collapse
Hi @latgarf1,
Sorry for my late answer. I'm busy with Android 7.
That would be nice to have another device on this project to have a better view and maybe have a real alternative in the future .
I will ask a moderator if we can move this thread to a general one.
Advantage to use Android 5.1.1, is that every patches are available and tested to run Archlinux with android Hw support.
But as OxygenOS is not pure AOSP you will maybe need to cherry-pick those patches.
So it is preferable to maybe try to use CM-13 but everything need to be done on that side. I have now a device (Samsung S3) that is able to run CM-13.0 so I will be able to help in case of an issue to port the code to CM-13.0.
The big advantage to try to do it on CM-13.0 is that we can touch a lot of device in the future ! If CM is open, we will be able to push the patches upstream because those patches will not interfere with Android build as this is the case for Ubuntu Touch and mer-hybris patches.
I have not take a lot of time to continue this project since a while but I'm able to run desktop applications with windows management + opengl acceleration etc... I need to work on audio part (in progress), modules to integrates sensors (but sensors are already working). The last video posted do not show those progress.
Let me know your advice and if you thing to base your work on CM 13.0, I will probably switch the development to the Samsung S3 instead of Xperia S (but I will try to keep Xperia S in sync ).
I'm really interested to have some help to speed up this project and to have more motivation for it
You can take a look on the documentation and let me know if you need some help (that will permit me to improve the documentation too).
nik012003 said:
I have a Sony Xperia S and a OnePlus One and I'd like this port!
On my OnePlus One I'm using Ubuntu Touch that is very cool but apt-get doesn't work so I can't install other apps.
I really like this on my "old" Xperia S !
Click to expand...
Click to collapse
Here I really want to don't do any difference between a PC and a smartphone. So every tools used on a PC should work on the smartphone (update the kernel and manage initrd should be, at the end, possible to do in the same way than on the desktop ).
Do you know if you are using pulseaudio on Ubuntu Touch ? And do you know in which way it is done ?
For now I'm following mer-hybris and Sailfish to implement it by creating a droid module for pulseaudio.
mickybart said:
...
Advantage to use Android 5.1.1, is that every patches are available and tested to run Archlinux with android Hw support.
But as OxygenOS is not pure AOSP you will maybe need to cherry-pick those patches.
So it is preferable to maybe try to use CM-13 but everything need to be done on that side. I have now a device (Samsung S3) that is able to run CM-13.0 so I will be able to help in case of an issue to port the code to CM-13.0.
The big advantage to try to do it on CM-13.0 is that we can touch a lot of device in the future !
Let me know your advice and if you thing to base your work on CM 13.0...
I'm really interested to have some help to speed up this project and to have more motivation for it
You can take a look on the documentation and let me know if you need some help (that will permit me to improve the documentation too).
Click to expand...
Click to collapse
I've not tried arch but have attempted similar to this project with Debian (raspbian) on ancient hardware with partial success.
As free time rears its rare head I'll be trying to adapt your project for my newer HTC based on cm13.
By the way, your work on N ril from github is great, allows my cm14 to get/make calls without rebooting. Now if I can just figure out why rild takes forever to stop dying and respawing and start actually running...
mickybart said:
Hi @latgarf1,
Sorry for my late answer. I'm busy with Android 7.
That would be nice to have another device on this project to have a better view and maybe have a real alternative in the future .
I will ask a moderator if we can move this thread to a general one.
Advantage to use Android 5.1.1, is that every patches are available and tested to run Archlinux with android Hw support.
But as OxygenOS is not pure AOSP you will maybe need to cherry-pick those patches.
So it is preferable to maybe try to use CM-13 but everything need to be done on that side. I have now a device (Samsung S3) that is able to run CM-13.0 so I will be able to help in case of an issue to port the code to CM-13.0.
The big advantage to try to do it on CM-13.0 is that we can touch a lot of device in the future ! If CM is open, we will be able to push the patches upstream because those patches will not interfere with Android build as this is the case for Ubuntu Touch and mer-hybris patches.
I have not take a lot of time to continue this project since a while but I'm able to run desktop applications with windows management + opengl acceleration etc... I need to work on audio part (in progress), modules to integrates sensors (but sensors are already working). The last video posted do not show those progress.
Let me know your advice and if you thing to base your work on CM 13.0, I will probably switch the development to the Samsung S3 instead of Xperia S (but I will try to keep Xperia S in sync ).
I'm really interested to have some help to speed up this project and to have more motivation for it
You can take a look on the documentation and let me know if you need some help (that will permit me to improve the documentation too).
Here I really want to don't do any difference between a PC and a smartphone. So every tools used on a PC should work on the smartphone (update the kernel and manage initrd should be, at the end, possible to do in the same way than on the desktop ).
Do you know if you are using pulseaudio on Ubuntu Touch ? And do you know in which way it is done ?
For now I'm following mer-hybris and Sailfish to implement it by creating a droid module for pulseaudio.
Click to expand...
Click to collapse
I don't know how the audio works but I know that it works.
This is the ubports repo https://github.com/ubports?tab=repositories
If you want me to type some commands on the ubuntu touch terminal let me know.
EDIT : I searched and I think that the Oneplus port is using pulseaudio but I don't know how does it work.
https://wiki.ubuntu.com/Touch/Core/PulseaudioProfiles
nik012003 said:
I don't know how the audio works but I know that it works.
This is the ubports repo https://github.com/ubports?tab=repositories
If you want me to type some commands on the ubuntu touch terminal let me know.
EDIT : I searched and I think that the Oneplus port is using pulseaudio but I don't know how does it work.
https://wiki.ubuntu.com/Touch/Core/PulseaudioProfiles
Click to expand...
Click to collapse
Thanks. I will give it a try but to have a more automatic process I will maybe follow what is done in mer-hybris :
https://github.com/mer-hybris/pulseaudio-modules-droid
Hi guys.
I have been working on a project to port NetHunter to Jiayu S3 (advanced for me , MT6752 platform) , working okay so far.
Tho I was still unable to start a new thread in DEVELOPMENT area . This is my first post in XDA. XDA helped me for many informations tho mostly all I care is the dev area so unable to say even a thank-you.
Any way I am here preparing to make a contribution for XDA. More talk with me so I can post the project earlier.
Kernel is modified and patched based on LoliTeam's project on Github.
mac80211 patched with script provided by Offensive-Security , HID manually patched regarding "Kernel-3.10-Nexus9.patch". Not exactly the same yet similar.
Additional Package of NetHunter is built under construction of [email protected]
Tested on AICP 6.0 UNOFFICIAL for JIAYU S3a MT6752 ( Should work on JIAYU S3 normal too I guess. never tried )
Progress:
OTG: Fix the 5V Power Supply for OTG so we can mount more than a USBdisk , like Mouse/Keyboard/JoyStick/WirelessAdapter , all avaliable now.
DuckHunter HID attack: working. Tho simple HID attack item didnt work , no idea why.
BadUSB MITM: RNDIS enabled. Capable to redirect the traffic of the computer you connected through your phone. (DHCPD on phone required, do it manually)
WiFi MITM: built-in wireless adapter does not support Monitor Mode so built-in Nethunter WiFi MITM does not work either. But we can do it manually , with a external USB via an OTG cable
Kali Chroot: Working
USBkeyboard(as HID device): Working
cSploit: Working
Shodan: Working
OpenVPN for Android: Working
VNC: Working
MSF: Working
Not working:
aircrack-ng toolkit: seldom working. But can be replaced by manually command.
War Driving: not working normally , because aircrack-ng. Not planning a fix.
Router Keygen: Only support built-in adapter. Giving it up.
Not tested:
RF Analyzer: No equipment. No plan on it.
Unsolved:
$ifconfig wlan1 mode monitor Wrong command but cause phone stuck (may be kernel panic)
Mana-Toolkit with wlan1 same , phone no responding. SO DO MITM MANUALLY , dont use mana.
Problems:
Battery Power is consumed faster.
Easier to heat up.
I think they are bearable
It has many drawbacks but still working great considering its condition.
Keep project on track:
@ https://github.com/offensive-security/kali-nethunter
@ https://github.com/DKingCN/nethunter-devices
@ https://github.com/DKingCN/android_kernel_jiayu_s3_h560
@ https://github.com/DKingCN/android-keyboard-gadget
Now you are able to build it on your own.
I will release it later when I got enough posts.
Thread closed by OP request.
OKAY SO
I present to you: Kali NetHunter 3.15.4 for the OnePlus 3 and OnePlus 3T
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-security/kali-nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
Most ROMs should be supported, as our installer uses a dynamic patching method on your current boot image!
The NetHunter installer zip will add a few files to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local/nhsystem, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
NetHunter also includes its own Busybox that gives you full large file support and some extra applets.
It will not overwrite your current one, and will happily install alongside it as busybox_nh.
DOWNLOAD
Current version: 3.15.4 (stable, 2017-02-02)
Please be careful to download the right version based on this table:
OnePlus 3: kernel-nethunter-oneplus3-nougat
OnePlus 3T: kernel-nethunter-oneplus3-nougat
All others be sad.
For the apps, chroot, and everything other than just the kernel, you will also need to download:
nethunter-generic-arm64-*
See installation instructions before proceeding!
Downloads are available at the official NetHunter build server: http://build.nethunter.com/nightly/
BEFORE INSTALLING
IMPORTANT: The Kali NetHunter installer requires write access to your data partition!
You should back everything up first before installing Kali NetHunter.
The Kali chroot and apps are installed on your data partition (in /data/local/nhsystem for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The generic NetHunter installer will automatically install SuperSU. We try to keep it up to date, but it isn't always.
If you already have SuperSU or another root method installed, please simply delete the supersu.zip from the root of the zip file before installing it.
** If modifying the installer zip, you will have to disable ZIP signature verification as modifications will break it.
It's recommended that you restore or flash your ROM's original kernel before installing NetHunter.
FULL INSTALLATION STEPS
Install Team Win Recovery Project to your recovery partition.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Recommended: If you have a custom kernel or SuperSU installed, restore your stock kernel. (called Boot in TWRP)
This isn't entirely necessary, but you may need to flash the NetHunter kernel again if SuperSU replaces it.
For new installations: Download the nethunter-generic-arm64-kalifs zip.
For upgrades: Download the update-nethunter-generic-arm64 zip.
Without exiting TWRP, transfer the NetHunter generic arm64 installer zip to your device over MTP* and flash it using [Install] in TWRP.
Download the kernel-nethunter zip specific to your device.
Without exiting TWRP, transfer the NetHunter kernel installer zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
Open the NetHunter app to initialize the environment
You're done!
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TO A NEWER BUILD OR UPDATING YOUR ROM
Follow the installation steps above. NetHunter can be installed over itself as many times as you'd like.
If you don't want to lose your chroot, flash the smaller update-nethunter-generic-arm64 zip instead.
DEVICE RECOMMENDATIONS
The OnePlus 3/3T internal wireless does not support monitor mode. This means you'll need to use an OTG adapter and a wireless card that does.
I highly recommend these two items:
Alfa Networks AWUS036NEH: https://smile.amazon.com/802-11g-Wireless-Long-Rang-Network-Adapter/dp/B0035GWTKK/
iXCC USB Type-C to Type-A OTG adapter: https://smile.amazon.com/iXCC-Adapter-Charge-Supported-Devices/dp/B017TJN22C/
* I am not affiliated with these sellers
The AWUS036NEH is the most tested and stable adapter available, and also comes in a very convenient portable form factor allowing antenna swaps for greater scanning ranges.
The iXCC USB adapter is compliant with USB Type-C specifications and provides up to USB 3.1 Gen 2 compatibility. It's also well built.
I don't recommend using smaller OTG adapters - they can break your ports if you accidentally put too much pressure on them or your phone falls with them plugged in.
THE KERNEL
The NetHunter kernel for the OnePlus 3 & 3T is based on OnePlus's OxygenOS 4.0.2 GitHub kernel sources.
It has the following changes:
Rebased on top of CodeAurora msm-3.18 for msm8996 7.0 tag: LA.UM.5.5.r1-02500-8x96.0 (2017-01-22)
Updated to the latest Linux mainline stable - 3.18.47
SELinux Permissive (required for DriveDroid until I fix policy injection rules, it will pretend to be Enforcing)
Tuxera exFAT drivers replaced with Samsung's latest open-source exFAT drivers
Enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
FIOPS IO scheduler as default IO scheduler, SIO available
DriveDroid compatibility
USB HID Gadget keyboard & mouse support
mac80211 packet injection support
savoca's KCAL color calibration driver built in
Additional drivers built in for the full Kali NetHunter experience
Data partition encryption optional
Kernel module support, insert your own modules! (modprobe available in Kali chroot)
CIFS, NFS, USB serial available through included kernel modules
VerifiedBoot=green status hack to pass SafetyNet (may not work with SuperSU, remove SuperSU from the installer if this is important!)
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
If your issue is with a specific app, it might be better to contact the developer of that app.
For Kali NetHunter bugs/issues, you can open a ticket at: https://github.com/offensive-security/kali-nethunter/issues
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
KNOWN ISSUES
USB Keyboard - The keyboard is unusable when using Google Keyboard as your input method. Switch to Hacker's Keyboard.
DEVELOPMENT & CONTRIBUTIONS
You can see the main branch of NetHunter's development on the Offensive Security GitHub: https://github.com/offensive-security/kali-nethunter
Kali NetHunter Official device updates: https://github.com/offensive-security/nethunter-devices/commits
OnePlus 3T NetHunter kernel source: https://github.com/jcadduono/android_kernel_oneplus_msm8996/commits/nethunter-7.0
If you wish to donate to the NetHunter project, you can donate directly to me through the Donate button under my name.
This will generally go towards supporting my next flagship device purchase, which will receive NetHunter and TWRP support from myself.
You can also use "Basenji Rescue and Transport" as your Amazon Smile charity and that will make me really happy!
(in my avatar, if you see a dog, that's a Basenji!)
SCREENSHOTS
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
XDA:DevDB Information
Kali NetHunter for the OnePlus 3 & 3T, Kernel for the OnePlus 3T
Contributors
jcadduono, The Kali NetHunter team
Source Code: https://github.com/offensive-security/kali-nethunter
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.15.4
Stable Release Date: 2017-02-02
Created 2016-11-27
Last Updated 2017-02-03
That's pretty cool, but I guess for me if I need it, I usually grab a laptop for it. IMO, this is not for most people. Seriously, if you have more tools to do a bunch of pen-test stuff on your phone, the very same phone that you use for other daily routine stuff, it also means those daily routine daily apps could have access to your pen-test tools also. It's like having a bunch of lock picking tools available in your garage when a thief trying break in to your house.
someone0 said:
That's pretty cool, but I guess for me if I need it, I usually grab a laptop for it. IMO, this is not for most people. Seriously, if you have more tools to do a bunch of pen-test stuff on your phone, the very same phone that you use for other daily routine stuff, it also means those daily routine daily apps could have access to your pen-test tools also. It's like having a bunch of lock picking tools available in your garage when a thief trying break in to your house.
Click to expand...
Click to collapse
On the plus side, the lock picking tools in the garage are locked in a safe (SuperSU permission requests), so those thieves can't access them unless they hold a gun to you and say "open the damn safe! ... in 3...2...1...accept supersu request!"
Anyway this could be ported over to oneplus 3??
aadityarulez said:
Anyway this could be ported over to oneplus 3??
Click to expand...
Click to collapse
Umm.. what are you talking about? The OP3 already has Kali nethunter. The kernel download is in the OP's link.
@jcadduono wanted to confirm whether this was the right zip to download. Used nethunter on OP2 before and it didn't have a separate generic zip and a kernel zip.
https://build.nethunter.com/nightly...-kalifs-full-rolling-3.15.3-20161126-1805.zip
knpk13 said:
Umm.. what are you talking about? The OP3 already has Kali nethunter. The kernel download is in the OP's link.
@jcadduono wanted to confirm whether this was the right zip to download. Used nethunter on OP2 before and it didn't have a separate generic zip and a kernel zip.
https://build.nethunter.com/nightly...-kalifs-full-rolling-3.15.3-20161126-1805.zip
Click to expand...
Click to collapse
Yes and we don't have the storage to make 800 MB files for every device every day.
knpk13 said:
Umm.. what are you talking about? The OP3 already has Kali nethunter. The kernel download is in the OP's link.
@jcadduono wanted to confirm whether this was the right zip to download. Used nethunter on OP2 before and it didn't have a separate generic zip and a kernel zip.
https://build.nethunter.com/nightly...-kalifs-full-rolling-3.15.3-20161126-1805.zip
Click to expand...
Click to collapse
really? i couldn't find the links to it.
aadityarulez said:
really? i couldn't find the links to it.
Click to expand...
Click to collapse
https://build.nethunter.com/nightly...oneplus3-marshmallow-3.15.3-20161126-1805.zip
Here.
I'd suggest you continue this in the Kali nethunter thread for OP3.
Thanks @jcadduono!! Looking forward to this ****!
So I'm trying to understand this. Many Qualcomm SoC do not support Monitor mode. Now I know Qualcomm used to use the name Qualcomm Atheros (which had open sourced drivers), so are SoCs not under the same umbrella? If that's true then are the sources for the Qualcomm SoC wifi driver not available? If they are then why can't we take and add monitor mode to the source and build it (like you used to have to do for many drivers to do aircrack)?
This might be a stupid question but am I able to get OTAs when I have NetHunter installed? And if yes do I have to reinstall it every time I get an OTA?
I am just curious because I never ever flashed a custom kernel till now. And thats what I am basically doing here right? Flashing a custom kernel + the NetHunter packge.
Regards
Boind
boind said:
This might be a stupid question but am I able to get OTAs when I have NetHunter installed? And if yes do I have to reinstall it every time I get an OTA?
I am just curious because I never ever flashed a custom kernel till now. And thats what I am basically doing here right? Flashing a custom kernel + the NetHunter packge.
Regards
Boind
Click to expand...
Click to collapse
Most devices you probably can't take OTA's. But I'm pretty sure for this device, that if it's detected that you're rooted or system modified or stuff, it downloads the entire ROM zip instead of just the OTA so you can upgrade manually. Kali is not just a custom kernel , you'll probably have to reinstall it when you update, AFAIK.
knpk13 said:
Most devices you probably can't take OTA's. But I'm pretty sure for this device, that if it's detected that you're rooted or system modified or stuff, it downloads the entire ROM zip instead of just the OTA so you can upgrade manually. Kali is not just a custom kernel , you'll probably have to reinstall it when you update, AFAIK.
Click to expand...
Click to collapse
So I am probally good to go, as far as reflash NetHunter every time I get an OTA?
BTW will NetHunter still work when Nougat gets rolled out in december?
knpk13 said:
Most devices you probably can't take OTA's. But I'm pretty sure for this device, that if it's detected that you're rooted or system modified or stuff, it downloads the entire ROM zip instead of just the OTA so you can upgrade manually. Kali is not just a custom kernel , you'll probably have to reinstall it when you update, AFAIK.
Click to expand...
Click to collapse
You are correct about the OTA'S. It will try the patch first but if it fails it will download the full ROM OTA.
Sent from my OnePlus3T using XDA Labs
How can i go back to the stock kernel? Nethunter kernel is killing my battery .
Hello there. It is possible to change the battery capacity read from the hardware?
I'm sorry if that sounds vague. OP3 owner here. From this video
you can see that one plus 3 batteries are sorta interchangeable. However the capacity is not read correctly. I presume that the OP3T has the correct code for it. I don't want to mess up your thread but if you can contribute it would help existing OP3 owners. (please look up Battery Mod /lens mod thread on One plus 3 forums and reply there.)
thanks
boind said:
So I am probally good to go, as far as reflash NetHunter every time I get an OTA?
BTW will NetHunter still work when Nougat gets rolled out in december?
Click to expand...
Click to collapse
yeah you'll get the full OTAs instead of update OTAs tho like above people said. you already have the rootfs on data partition, so you only need to flash kernel-nethunter-oneplus3t and update-nethunter zips. you might also need to flash supersu again, or you can use another root like phh superuser.
when oneplus releases nougat kernel sources i will support nougat. it will not work with the marshmallow kernel.
update: 3.5.3 sources are out! updating!
https://build.nethunter.com/nightly/3.15.3-20161201-1343/
this kernel is updated for 3.5.3 touchscreen changes (a lot of changes) and also updated to CAF tag LA.HB.1.3.2-33100-8x96.0 (more touchscreen and wifi fixes)
Hello, I installed the latest zips as of 12/01/2016
You mentioned in the OP;
"I highly recommend these two items:
Alfa Networks AWUS036NEH: https://smile.amazon.com/802-11g-Wir...dp/B0035GWTKK/
iXCC USB Type-C to Type-A OTG adapter: https://smile.amazon.com/iXCC-Adapte...dp/B017TJN22C/
* I am not affiliated with these sellers"
I already had the iXCC USB-OTG cable but I have the TL-WN722N wifi card. Do I need a different USB-OTG cable (the Y version)?? The TL-WN722N wifi card will not power on so I wasn't sure if it is a power issue or if I need to configure this somehow?
Any help is appreciated! Thanks!!
MrGimpGrumble said:
Hello, I installed the latest zips as of 12/01/2016
You mentioned in the OP;
"I highly recommend these two items:
Alfa Networks AWUS036NEH: https://smile.amazon.com/802-11g-Wir...dp/B0035GWTKK/
iXCC USB Type-C to Type-A OTG adapter: https://smile.amazon.com/iXCC-Adapte...dp/B017TJN22C/
* I am not affiliated with these sellers"
I already had the iXCC USB-OTG cable but I have the TL-WN722N wifi card. Do I need a different USB-OTG cable (the Y version)?? The TL-WN722N wifi card will not power on so I wasn't sure if it is a power issue or if I need to configure this somehow?
Any help is appreciated! Thanks!!
Click to expand...
Click to collapse
cards don't turn on until you turn them on
ip link set wlan1 up
will turn it on (in whatever mode its currently in)
but most people want monitor mode, theres a monitor mode power on command in the nethunter app
jcadduono said:
cards don't turn on until you turn them on
ip link set wlan1 up
will turn it on (in whatever mode its currently in)
but most people want monitor mode, theres a monitor mode power on command in the nethunter app
Click to expand...
Click to collapse
Thanks! Although the wifi adapter doesn't light up to show its on... Will this happen after I use that command?