I am trying an experiment with my Atrix in which I need to be able to build the kernel and have a working wifi module. I have successfully built the faux123's kernel-MB860 (thanks very much!).
I then downloaded faux123's atrix-wifi-module in order to get wifi working. I have built the module, and pushed it to /system/lib/modules. However, wifi doesn't work. Under settings, it just displays "error". dmesg doesn't show nearly as much as a kernel packaged by faux123. Here is my output:
Code:
<4>[ 24.504982] sdhci_tegra_wlan_detect Detecting WLAN
<4>[ 24.504998] mot_wifi_set_carddetect: Nobody to notify
<4>[ 24.507937]
<4>[ 24.507940] Dongle Host Driver, version 4.218.248.31
<4>[ 24.507944] Compiled in /home/kenny/android/atrix-wifi-module/open-src/src/dhd/linux/../.. on Apr 17 2012 at 06:54:15
<6>[ 24.724025] request_suspend_state: wakeup (3->0) at 13492036210 (2012-04-21 19:25:46.351491984 UTC)
<6>[ 24.725196] lm3532_brightness_set: lcd-backlight, 0x4c(76), webtop=0
<7>[ 25.088713] mmc1: queuing CIS tuple 0x91 length 3
<6>[ 25.088824] mmc1: new SDIO card at address 0001
<6>[ 25.534772] usb_ether_get_stats
Whereas, dmesg from a kernel/module packaged by faux123 displays:
Code:
[ 49.811365] sdhci_tegra_wlan_detect Detecting WLAN
[ 49.811403] mot_wifi_set_carddetect: Nobody to notify
[ 49.812815]
[ 49.812818] Dongle Host Driver, version 4.218.248.31
[ 49.812822] Compiled in /home/paul/Froyo/system/vendor/bcm/wlan/osrc/open-src/src/dhd/linux/../.. on Dec 17 2011 at 19:58:57
[ 50.108317] mmc1: queuing CIS tuple 0x91 length 3
[ 50.108350] mmc1: new SDIO card at address 0001
[ 50.136595] alloc static buf at e9980000!
[ 50.136975] F1 signature read @0x18000000=0x9934329
[ 50.139716] DHD: dongle ram size is set to 294912(orig 294912)
[ 50.143537] wl_iw_attach thr:6d0 started
[ 50.143598] wl_iw_bt_init thr:6d1 started
[ 50.143655] dhd_attach thr:6d2 started
[ 50.143706] dhd_attach thr:6d3 started
[ 50.143749] dhd_attach thr:6d4 started
[ 50.191722] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
[ 50.273753] wifi_get_mac_addr
[ 50.274700] Firmware version = wl0: May 6 2011 13:09:01 version 4.218.248.31
[ 50.442416] eth0: Broadcom Dongle Host Driver mac=40:fc:89:13:a8:83
If I try to do a insmod, I get an invalid argument message.
Code:
# insmod /system/lib/modules/dhd.ko
insmod: init_module '/system/lib/modules/dhd.ko' failed (Invalid argument)
Can someone suggest what I might be missing or doing wrong?
as far as i've researched this problem, it's hardware related. i get the same error (and an accompanying reboot) every time i try to toggle wifi.
http://forum.xda-developers.com/showthread.php?t=1205775
if you have any more success please let me know.
dLo GSR said:
as far as i've researched this problem, it's hardware related.
Click to expand...
Click to collapse
I'm not convinced it is hardware related (other than maybe having the wrong driver), since wifi works great using a true faux123 kernel/module.
I suspect my problem has something to do with how I compiled module or other files that I need to put on the phone.
How did you build it? A little more background might help
Build process ... it works!?!?
First, the good news...the module now works. But I don't understand what I may have done differently this time other than do the builds consecutively.
I retrieved the source:
Code:
$ cd ~/android/faux123-olympus-cm7-kernel
$ git clone https://github.com/faux123/kernel-MB860.git
$ cd ~/android
$ git clone https://github.com/faux123/atrix-wifi-module.git
Then I built:
Code:
$ cd ~/android/faux123-olympus-cm7-kernel/kernel-MB860
$ make ARCH=arm tegra_olympus_cm7_defconfig
$ make ARCH=arm CROSS_COMPILE=/home/kenny/tools/arm-2011.09/bin/arm-none-eabi- -j1
$ cd ../../atrix-wifi-module/open-src/src/dhd/linux/
$ export LINUXSRCDIR=/home/kenny/android/faux123-olympus-cm7-kernel/kernel-MB860
$ make ARCH=arm CROSS_COMPILE=~/tools/arm-2011.09/bin/arm-none-eabi- -j1
$ adb push /home/kenny/android/faux123-olympus-cm7-kernel/kernel-MB860/vendor/bcm/wlan/osrc/open-src/src/dhd/linux/dhd.ko /system/lib/modules/dhd.ko
I had kernel built a few days before I had found the wifi module source. I then tried building the wifi module and pushing the module as shown above.
Since then (over last week or so), I have tried a number of things, including copying files (/etc/firmware/wifi/*) from another phone which has a faux123 kernel. Are these files required? Are there steps in here that I missed?
Hi all
I know this will sound old school but, does anyone know how to get the startup of the sola to show what is actually loading?
Like when you accidentally hit the esc key on your keyboard and the ubuntu boot screen disappears and shows you what is actually happening.
Like I said STOCK STARTUP!
Now mounting system to /system.........
Mounting data to /data..........
Type of thing, similar to MS Windows 98 SE.
I know there must be a way
DEV Device: MB511 (deodexed)
Current System: MT27i
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
I'm also interesting about it. To disable boot logo (bootanimation.zip) and see what's happening behind
Basically nothing, you just get your manufactures logo and thats it. Nothing more nothing less. We probably have to edit a file somewhere
DEV Device: MB511 (deodexed)
Current System: MT27i
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
Ok....... anyone know how to startup in debbugging mode atleast?
DEV Device: MB511 (deodexed)
Current System: MT27i
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
Possiblilty
finally found something that should work except..... you need UART or JTAG access......
Any how thanks Adam Outler!!!!!!!:highfive:
http://forum.xda-developers.com/showpost.php?p=16466682&postcount=5
Edit:
The settings in SBL prompt are
Code:
setenv SWITCH_SEL 6543
setenv PHONE_DEBUG_ON 1
saveenv
Code: Starting kernel at 0x32000000... Uncompressing Linux................................................................................................................................................................................... [ 0.000000] copy: bad source 0 [ 0.000000] mout_audss: bad source 0 [ 0.090142] KERNEL:kernel_sec_get_debug_level_from_boot=0x574f4c44 [ 0.094877] KERNEL:magic_number=0x0 DEBUG LEVEL low!! [ 0.099895] (kernel_sec_set_upload_cause) : upload_cause set 0 [ 5.833835] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' sh: can't access tty; job control turned off $ [ 11.433364] init: no such service 'bootanim' [ 24.851663] init: sys_prop: permission denied uid:1000 name:wifi.interface [ 35.227503] init: no such service 'bootanim' [ 38.484304] init: sys_prop: permission denied uid:1000 name:dpm.allowcamera su sh: can't access tty; job control turned off # dmesg|tail [ 47.443068] [email protected] [ 51.363390] mook - wm8994 TTY Off [ 51.666438] eth0: SIOCSIWSCAN : ISCAN [ 51.667822] +++: Set Broadcast ISCAN [ 53.013468] [email protected] [ 54.447852] Send Event ISCAN complete [ 54.448053] eth0 wl_iw_iscan_get_scan buflen_from_user 8192: [ 54.448067] eth0: SIOCGIWSCAN GET broadcast results [ 54.448111] wl_iw_iscan_get_scan return to WE 803 bytes APs=3 [ 84.445803] wl_iw_set_ss_cache_timer_flag called #
This app shows you live dmesg at boot [requires root]. Not exactly what you wanted, but close enough on the geek scale.
https://play.google.com/store/apps/details?id=eu.chainfire.livedmesg.lite
will give it a try. i wish there was a guide on the hijack for the motoboot file.
Edit: thank you! It works like a charm, now to strip it and see how it works. When I get cash I will purchase the full version lol! Chainfire kicks ass! :thumbup:
n2droid said:
This app shows you live dmesg at boot [requires root]. Not exactly what you wanted, but close enough on the geek scale.
https://play.google.com/store/apps/details?id=eu.chainfire.livedmesg.lite
Click to expand...
Click to collapse
I found logcat live wallpaper and loving it!
https://play.google.com/store/apps/details?id=org.jraf.android.logcatlivewallpaperlite
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
{
"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"
}
Supports Android 7.0 to 8.1
Recommended for all WiFi tools to work is Android v7.1.2. Installation steps is described further below.
FEATURES:
Features from @flar2 kernel which this is built on.
All credits to him for hosting awesome kernel sources.
* Easy installation and setup with Aroma installer
* Wake Gestures (sweep2wake and doubletap2wake)
* Sweep2sleep
* Overclock or underclock CPU
* Advanced color control (RGB, Saturation, Value, Contrast, Hue)
* Sound control (headphones, speaker and mic)
* Backlight dimmer option
* High Brightness Mode option
* Option to disable touchboost
* NTFS r/w and exFAT support
* Option to disable fsync
* Adjustable vibration
* MultiROM support
* WireGuard support
* Does not force encryption
* Does not modify system partition
* Compatible with systemless root and Android Pay
Added by me on top:
* Big collection of wireless drivers & firmware
* Big collection of ethernet USB, USB hubs and general USB adapters of various kinds.
* rtl8812au drivers from https://github.com/aircrack-ng/rtl8812au
* rtl8188eus drivers from https://github.com/aircrack-ng/rtl8188eus (added but not working yet)
* "linux-firmware" built in
* CD-ROM patch
* USB HID support
* WIFI injection patches for several adapters
* Nexmon support with both monitor mode & frame injection via internal adapter
* SELINUX patched
* USB OTG (w/ACA) is supported
* linux-stable patches merged inside
* wireless-tools (iw, iwconfig, ifconfig etc) is bulilt into Android /system (packing them in a new release in a few days)
[ TODO / W.I.P ]
* Add a bunch of compiled binaries
* Change to anykernel3 installer
* Merge more from linux-stable
* See if we may fix the Android 8.1 issue
[ Images / Media ]
Running wifite2 through SSH with JuiceSSH
Running airodump-ng using the external AWUS036ACH. - Hijacker packs aircrack-ng suite, reaver wps and mdk3 but also has a cracking & scripting option.
A few of my tools, for me WiFi and MITM is important.
[ Installation ]
We recommend you start from scratch and setup the device, full restore to fresh v7.1.2 is recommended,
even though this kernel supports Android 8.1 too, some of the tools can't right now unfortunately.
1. Find the original, stock firmware over here and choose the latest 7.1.2 (N2G48C, Aug 2017)
2. Press & hold VOLUME DOWN [ - ] and POWER to reboot to bootloader
3. Flash the stock firmware with "flash-all.bat" on Windows or "flash-all.sh" for Linux users
4. Boot into stock and ENABLE developer setting (the menu you get after SPAMMING 5-7 times on the "Build Number" in "Settings" and "About Phone"
-- here you may use the phone to download the kernel zip for flashing afterwards. or use "adb sideload" later on.
5. With ADB enabled, reboot to BOOTLOADER
6. Get TWRP recovery from over here and flash it with "fastboot flash recovery twrp-3.3.1-0-angler.img"
7. VOLUME UP or DOWN and choose "Recovery Mode"
8. In recovery mode
9. Either flash the kernel zip (if you downloaded in the phone before reboot), or go to "Advanced" and use "ADB Sideload"
10. If you ended up with "ADB Sideload" open Terminal or "Minimal ADB" prompt (Windows) and flash the kernel with "adb sideload < file.zip >
11. After flashing the kernel, you also would need root. We suggest using Magisk root which you may find over here
And flash the latest stable release. Same method as earlier.
12. Open "Magisk Manager" and search for "busybox" -- Install it and reboot again in order to activate it.
13. Start installing apps, e.g Hijacker official link
--- Nexmon and it's tools ain't a bad choice either, the WiFi SoC is BCM4358 and supported. Grab it over here
14. A Terminal would also be useful here, grap it from NetHunter repo right about here
15. The NetHunter App should also be in place. Direkt link
16. zANTI from Zimperium is loaded with nmap with NSE scripts/plugins and is pretty nifty one. grab it right here!
17. cSploit is available right here (it's getting outdated, but a few things work).
[ Downloads ]
https://github.com/kimocoder/android_static_tools/raw/master/nethunter_angler.zip
[ SOURCE ]
http://github.com/kimocoder/android_kernel_nexus6p
The recommended toolchain for this kernel sources is gcc-linaro-5.4.1-2017.05-x86_64_aarch64-linux-gnu
[ Tools ]
wifite2 - https://www.github.com/kimocoder/wifite2 (newly added to Kali / NetHunter repos)
Hijacker - https://github.com/chrisk44/Hijacker
aircrack-ng - https://aircrack-ng.org
Nexmon - https://github.com/seemoo-lab/nexmon
Magisk - https://github.com/topjohnwu/Magisk
NetHunter - https://gitlab.com/kalilinux/nethunter
zANTI - https://www.zimperium.com/
cSploit - http://wwwcsploit.org
[ Social Media ]
Follow me on Twitter
[ Credits ]
@flar2
@binkybear
@jcadduono
@aircrack-ng
@nathanchance @nexmon
@chrisk44
@NetHunter
@Re4son
kriswebdev at GitHub
kimocoder said:
[...]
Big collection of wireless drivers & firmware
* Big collection of ethernet USB, USB hubs and general USB adapters of various kinds.
* rtl8812au drivers from https://github.com/aircrack-ng/rtl8812au
[...]
Click to expand...
Click to collapse
Hi master!
First of all, thank you very much for this nice work!!
Downloading asap (the href of the URL seems broken. One need to copy paste the url)
Off-topic:
it seems that you have got a lot of knowledge when it comes to android and wifi drivers, maybe you are the one, who could help me:
I would like to add a wifi-driver for "Broadcom BCM94352Z" into "android-x86 9.0-rc1".
On Linux one would update/install "bcmwl-kernel-source" to get the card running.
On Android-x86 I can scan for wifis via terminal.
But I cant neither connect via terminal nor scan via the UI.
Any help would be AMAZING.
please install video, I do not understand English, a video can guide .. ???
@kimocoder
As per instructions, did I completely start from scratch, but wasn't sure where the chroot has to be installed..I copied the latest kalifs over to the SDcard and extracted it from there.. A direct download via the Nethunter.apk wasn't possible.
After I rebooted the Nh terminal is showing the kali chroot, but JuiceSSH via localhost (Snippet 'su -c bootkali_login').
The phone shows the wlan adapter with the according chipset via 'lusb', but cannot be set into Monitor mode with airmon-ng.
Best regards
Could you specify and/or correct the link to the kernel source, please.
As I wrote before, didn't I have much success in getting a external Wlan adapter to work.
After testing the kernel, I am unable to get the phone back to stock.
At startup I got constantly bootloop.Even after flashing the latest 7.12 and 8.1 factory rom and trying various things, like erasing/formatting the various partitions , trying to boot into TWRP..
I flashed the last 8.1 release last(before testing several times the latest 7.1 release and several times the 7.12 version, which is mentioned in OP, tried to boot into Twrp after successful flashing, Bootloader is unlocked and fastboot menu working.
It seems that userdata is creating some issues.
Help would be appreciated.
:>
PS
What for a wlan adapter are you using?
I have followed your instructions to a T but have had a few issues / questions. I've had very little issues getting nethunter (minux nexmon/hijacker) on several other devices.
Nexmon seems to be working but is there a way to keep the firmware and libraries installed permanently? I could not put them into the default /su/xbin and /su/lib, I got error messages so I put them into /system/xbin and /system/lib but it's not persistent.
Using the version of the nethunter app, a chroot can not be downloaded.
I have used the HiJacker that you posted and the latest beta from the Official git project and it keeps freezing the phone. Not sure what settings may need to be changed but no collection with it works.
When I plug an exfat and ntfs drive into the phone it wants to format the drive and if I don't it's can't mount the drive.
Hello download link not working
Hey there,
i ve got a few Questions. I ve spend a lot of time to test the Nexus 6p with different Setups and Android Versions and finally i decided to go with the latest los 14.1.
Your nexmon and Hijacker port are working with the internal wlan Adapter even in 5GHz.
But Default your nexmon installs the Tools and Firmware non persistent, this must done on every reboot. But thats very ok.
But, i am currently on nethunter 2020.1, on the Default kernel my tplink tl-wn822n (rtl8192cu i think) works out of the box.
With your kernel my tplink does not work because perhaps there is no modul Auto loading. I can insmod the rtl8812au for this device i have too, but when i try the 8192 for the tplink this does not work.
And also with your kernel the 8812au Adapter works but when wifite is running an atack the device reboots. Sooo, Long Story short:
Thanks for your hard work and perhaps there will be an update for this kernel.
P.S.: here is the correct link for the Tools
https://github.com/kimocoder/android_static_tools
Nick_Speed said:
But Default your nexmon installs the Tools and Firmware non persistent, this must done on every reboot. But thats very ok
Click to expand...
Click to collapse
Load the Nexmon app from the Nethunter store, because this seems to be a installation path issue.
Even with my antique Samsung Galaxy S2, which hits you with dozens of other problems and even the stupid addonsu has problems with the root recognition within Nexmon.
Hit the button by app start just again and everything, should the install not being screwed up beforehand, are patched firmware, utils etc.. in my experience detected.
But, i am currently on nethunter 2020.1, on the Default kernel my tplink tl-wn822n (rtl8192cu i think) works out of the box.
Click to expand...
Click to collapse
I assume that you meant the "working" setup..
These 2 kernel are for total differrent distributions and shouldn't be used in tandem; mkay..
With your kernel my tplink does not work
Click to expand...
Click to collapse
The adapter resp supported bands and this particular driver is quite old and like I wrote before, not a guarantee that it works in kimocoder's kernel beside; because one in another setup of you did work.That other kernel is LOS based for example, this one stock.
I read a couple months ago, that the RTL8192cu, apart the age, still unstable and buggy is/can be..but the driver is in the kernel..no clue, bud.
because perhaps there is no modul Auto loading. I can insmod the rtl8812au for this device i have too, but when i try the 8192 for the tplink this does not work.
Click to expand...
Click to collapse
Unfortunately did the device age finally caught up shortly after the first installation "try outs", so I didn't have time to try one of my nics with the Realtek RTL8812AU driver.
Your TP-Link should be detected without 'insmod', I am fairly certain.
Did you use iw-tools or airmon-ng for the 8812au?
If you look over kimocoder's repo, you see the regarding driver at 2 or 3 place.
Scroll down and look the commands up, if you have no experience with iw.
I am sure that kimocoder will get back if, he has the time.I am thinking of buying a new one, so let's hope he has time in the foreseeable future to get the kinks out.. ;E
@kimocoder It will spare many user from eventual screwing up their devices in regard to the install from a fairly newer stock release to an older..just look in the Nexus's sub-forum.
Battery issue is not that fantastic whatever, but this is not that safe, man. :/
Would it be possible, as long as the Oreo support is not in dry sheets, to use a stock like custom rom? Pure Nexus comes into my head should be the same, but without the eventuality of messing with the stock files (no idea)..?
thx for your Reply :good:
UsPdSr said:
Load the Nexmon app from the Nethunter store, because this seems to be a installation path issue.
Click to expand...
Click to collapse
Nope, from the store nexmon doesnt start at all, the app forced to close.
UsPdSr said:
These 2 kernel are for total differrent distributions and shouldn't be used in tandem; mkay..
The adapter resp supported bands and this particular driver is quite old and like I wrote before, not a guarantee that it works in kimocoder's kernel beside; because one in another setup of you did work.That other kernel is LOS based for example, this one stock.
I read a couple months ago, that the RTL8192cu, apart the age, still unstable and buggy is/can be..but the driver is in the kernel..no clue, bud.
Click to expand...
Click to collapse
Thats a Point i thougth you got me, of Course i am not on stock like kimocoder wrote in his Installation steps, and so his kernel does not work well with LOS.
So i went to stock and setuped everything and...
the behavior is the same.
Here is some Output from dmesg with his kernel on stock:
For the tplink:
[ 696.723240] hub 2-0:1.0: 1 port detected
[ 697.039016] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 697.056824] usb 1-1: New USB device found, idVendor=0bda, idProduct=8178
[ 697.056884] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 697.056910] usb 1-1: Product: USB WLAN
[ 697.056934] usb 1-1: Manufacturer: Realtek
[ 697.056957] usb 1-1: SerialNumber: 00e04c000001
For the CLS (with 88XX):
[ 833.598100] xHCI xhci_add_endpoint called for root hub
[ 833.598119] xHCI xhci_check_bandwidth called for root hub
[ 833.599024] hub 2-0:1.0: USB hub found
[ 833.599077] hub 2-0:1.0: 1 port detected
[ 833.911239] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 833.926677] usb 1-1: New USB device found, idVendor=0bda, idProduct=8812
[ 833.926737] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 833.926764] usb 1-1: Product: 802.11n NIC
[ 833.926788] usb 1-1: Manufacturer: Realtek
[ 833.926811] usb 1-1: SerialNumber: 123456
And no module is loading.
After insmod 88XX.ko the wlan1 interface appears, i ve read on GitHub About the steps with iw and monitor mode and did this, but...
With wifite the device reboots on this step: PMKID CAPTURE: Waiting for PMKID (29s) (After unplugging the Adapter the devices reboots also...)
So i installed nethunter 2020.1 with the Default kernel on stock and when i Plugin my tplink dmesg says this:
[ 213.223653] xHCI xhci_add_endpoint called for root hub
[ 213.223663] xHCI xhci_check_bandwidth called for root hub
[ 213.224293] hub 1-0:1.0: USB hub found
[ 213.224329] hub 1-0:1.0: 1 port detected
[ 213.224536] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[ 213.224554] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[ 213.224615] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[ 213.224624] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 213.224631] usb usb2: Product: xHCI Host Controller
[ 213.224638] usb usb2: Manufacturer: Linux 3.10.73-nethunter-angler-1.1 xhci-hcd
[ 213.224644] usb usb2: SerialNumber: xhci-hcd.0.auto
[ 213.225498] xHCI xhci_add_endpoint called for root hub
[ 213.225508] xHCI xhci_check_bandwidth called for root hub
[ 213.225990] hub 2-0:1.0: USB hub found
[ 213.226022] hub 2-0:1.0: 1 port detected
[ 213.537162] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 213.551861] usb 1-1: New USB device found, idVendor=0bda, idProduct=8178
[ 213.551890] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 213.551898] usb 1-1: Product: USB WLAN
[ 213.551906] usb 1-1: Manufacturer: Realtek
[ 213.551913] usb 1-1: SerialNumber: 00e04c000001
[ 213.558318] rtl8192cu: Chip version 0x11
[ 213.615218] rtl8192cu: MAC address: c4:6e:1f:25:f5:4a
[ 213.615251] rtl8192cu: Board Type 0
[ 213.615398] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 213.615657] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[ 213.640232] ieee80211 phy1: Selected rate control algorithm 'rtl_rc'
[ 213.643063] rtlwifi: wireless switch is on
[ 213.742373] SELinux: initialized (dev fuse, type fuse), uses mountpoint labeling
without insmod or something else. So...
I will wait what time will bring. I Count on this devices because its performant and the internal Adapter works even in 5Ghz with the Tools.
And sorry for my bad english, its not my native language.
@Nick_Speed
No need to apologise for possible language difficulties, mate.
The dmesg output reminds me of old ones with this device, which showed similar problems.
So it seems that we have to wait for the graciousness that kimocoder or somebody else will look into this.
I thought of building one in the meantime, but I have build only one kernel for android so far, so I consider myself therefore definitely still a beginner.
From what I read is the integration of the capabilities of Nexmon important..I had quite problems to build a kernel for the hammerhead.
Contrary to some opinions is it not that easy to build a kernel with Kali's main functions for Nexus devices.
I will definitely think about it and look over my schedule, but I couldn't accomplish it in the next week(s).Especially with the integration of Nexmon.
Let's hope that the dev comes around, right. :/
I forgot to ask what do you meant with the 2020.1 builds of Nethunter?
How did you install the chroot?
You thought to wipe and format everything, before starting over, right?
UsPdSr said:
I forgot to ask what do you meant with the 2020.1 builds of Nethunter?
How did you install the chroot?
Click to expand...
Click to collapse
I mean the release of kali nethunter 2020.1. It is a flashable zip for twrp. It includes everythink you Need. Nethunter App, Store, chroot, kernel. Ist the official one from the official site.
UsPdSr said:
You thought to wipe and format everything, before starting over, right?
Click to expand...
Click to collapse
Of Course. Always. And for stock i use the factory Image from Google. This means fastboot and flashall with the -w (wipe) Option.[/QUOTE]
Nick_Speed said:
I mean the release of kali nethunter 2020.1. It is a flashable zip for twrp. It includes everythink you Need. Nethunter App, Store, chroot, kernel. Ist the official one from the official site.
Click to expand...
Click to collapse
Yeah, sure.
I was talking about the chroot-installation with this kernel here?
Of Course. Always. And for stock i use the factory Image from Google. This means fastboot and flashall with the -w (wipe) Option.
Click to expand...
Click to collapse
Alright.
For the future: it's always better to wipe the former installation via Twrp and if you flash a stock image, don't use those crappy scripts from Google.
First is it inherently better to use fastboot/adb one command at a time and the '-w' in the flashall-script can by our BLOD-prone devices cause a bootloop, if the restart goes wrong.
Do u have any good links that r working to download the kernel
fowler82 said:
Do u have any good links that r working to download the kernel
Click to expand...
Click to collapse
Yeah, there seems to be some mess with the bbc code.
Here you go
->
https://github.com/kimocoder/android_static_tools/blob/master/nethunter_angler.zip
The rest of the apps and some pics from kimocoder can be found here
->
https://github.com/kimocoder/android_static_tools
Nick_Speed said:
thx for your Reply :good:
Nope, from the store nexmon doesnt start at all, the app forced to close.
Thats a Point i thougth you got me, of Course i am not on stock like kimocoder wrote in his Installation steps, and so his kernel does not work well with LOS.
So i went to stock and setuped everything and...
the behavior is the same.
Here is some Output from dmesg with his kernel on stock:
For the tplink:
[ 696.723240] hub 2-0:1.0: 1 port detected
[ 697.039016] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 697.056824] usb 1-1: New USB device found, idVendor=0bda, idProduct=8178
[ 697.056884] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 697.056910] usb 1-1: Product: USB WLAN
[ 697.056934] usb 1-1: Manufacturer: Realtek
[ 697.056957] usb 1-1: SerialNumber: 00e04c000001
For the CLS (with 88XX):
[ 833.598100] xHCI xhci_add_endpoint called for root hub
[ 833.598119] xHCI xhci_check_bandwidth called for root hub
[ 833.599024] hub 2-0:1.0: USB hub found
[ 833.599077] hub 2-0:1.0: 1 port detected
[ 833.911239] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 833.926677] usb 1-1: New USB device found, idVendor=0bda, idProduct=8812
[ 833.926737] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 833.926764] usb 1-1: Product: 802.11n NIC
[ 833.926788] usb 1-1: Manufacturer: Realtek
[ 833.926811] usb 1-1: SerialNumber: 123456
And no module is loading.
After insmod 88XX.ko the wlan1 interface appears, i ve read on GitHub About the steps with iw and monitor mode and did this, but...
With wifite the device reboots on this step: PMKID CAPTURE: Waiting for PMKID (29s) (After unplugging the Adapter the devices reboots also...)
So i installed nethunter 2020.1 with the Default kernel on stock and when i Plugin my tplink dmesg says this:
[ 213.223653] xHCI xhci_add_endpoint called for root hub
[ 213.223663] xHCI xhci_check_bandwidth called for root hub
[ 213.224293] hub 1-0:1.0: USB hub found
[ 213.224329] hub 1-0:1.0: 1 port detected
[ 213.224536] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[ 213.224554] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[ 213.224615] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[ 213.224624] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 213.224631] usb usb2: Product: xHCI Host Controller
[ 213.224638] usb usb2: Manufacturer: Linux 3.10.73-nethunter-angler-1.1 xhci-hcd
[ 213.224644] usb usb2: SerialNumber: xhci-hcd.0.auto
[ 213.225498] xHCI xhci_add_endpoint called for root hub
[ 213.225508] xHCI xhci_check_bandwidth called for root hub
[ 213.225990] hub 2-0:1.0: USB hub found
[ 213.226022] hub 2-0:1.0: 1 port detected
[ 213.537162] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 213.551861] usb 1-1: New USB device found, idVendor=0bda, idProduct=8178
[ 213.551890] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 213.551898] usb 1-1: Product: USB WLAN
[ 213.551906] usb 1-1: Manufacturer: Realtek
[ 213.551913] usb 1-1: SerialNumber: 00e04c000001
[ 213.558318] rtl8192cu: Chip version 0x11
[ 213.615218] rtl8192cu: MAC address: c4:6e:1f:25:f5:4a
[ 213.615251] rtl8192cu: Board Type 0
[ 213.615398] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
[ 213.615657] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[ 213.640232] ieee80211 phy1: Selected rate control algorithm 'rtl_rc'
[ 213.643063] rtlwifi: wireless switch is on
[ 213.742373] SELinux: initialized (dev fuse, type fuse), uses mountpoint labeling
without insmod or something else. So...
I will wait what time will bring. I Count on this devices because its performant and the internal Adapter works even in 5Ghz with the Tools.
And sorry for my bad english, its not my native language.
Click to expand...
Click to collapse
@Nick_Speed were you able to get around the device reboots on your setup? I have the same issue, and it's driving me mad!
SharkCage said:
@Nick_Speed were you able to get around the device reboots on your setup? I have the same issue, and it's driving me mad!
Click to expand...
Click to collapse
Nope, and unfortunately there arent any updates...
I tried so far an one plus 2 and a nexus 6 because they are supported and recommned but they lack of internal wlan mon support.
So the best devices so far is imo the nexus 6p with Android 7 and the stock nethunter kernel for external non 5Ghz Adapters and internal wlan mon support (with patched firmware).
Nick_Speed said:
Nope, and unfortunately there arent any updates...
I tried so far an one plus 2 and a nexus 6 because they are supported and recommned but they lack of internal wlan mon support.
So the best devices so far is imo the nexus 6p with Android 7 and the stock nethunter kernel for external non 5Ghz Adapters and internal wlan mon support (with patched firmware).
Click to expand...
Click to collapse
Thanks for the quick reply. Hopefully @kimocoder stops in for suggestions.
Nick_Speed said:
Nope, and unfortunately there arent any updates...
I tried so far an one plus 2 and a nexus 6 because they are supported and recommned but they lack of internal wlan mon support.
So the best devices so far is imo the nexus 6p with Android 7 and the stock nethunter kernel for external non 5Ghz Adapters and internal wlan mon support (with patched firmware).
Click to expand...
Click to collapse
You can use the Nougat Nethunter kernel for the N6p with LineageOS(RR, Omnirom, DU etc.) and Stock, or customized Stock images like PureNexus as well.
I haven't give up.Even after 25 kernel sources for Oreo, am I still developing.
Unfortunately did it seem, that the Nethunter team overwhelmed with more "recent" devices are and the Nexus not a OnePlus 7t Pro is. :E
I think it's great, beside the sucky OnePlus fondling have they achieved remarkable innovations, not only the kernel for the 800 Euro Gaming PC aka 7xy.
Like Nick_Speed said, is the internal monitor mode including the screen size, USB-C and foremost the very affordable price (I bought my second one a month ago and paid 90 Euro in great condition.Accu-health is very good and so far no issues.
I recommend commercial reseller.They ensure , at least in my case, three month guarantee and are very selective in their buying.
For now would I choose the stable kernel for 7.1-7.1.2, with with the Ternux setup(not my cup of tea - Termux=bah.Why not Terminus, JuiceSSH or something less trashy? ), or the new Nethunter UI(installer).
The optimal choice is to self build one with the python installer. In addition pick some of the features of the tools from this thread.Nexnon,Hijacker,Zanti, Wiggle and a couple you have to look up for yourself.
It sucks that we can't use devices with AC capabilities,but maybe another dev or myself come around to make this happen.
The problem is that Nexus development really sucks in regard of the modules at least.
I had more success with the Nvidia Shield K1, which was practically claimed as dead.
Many heaps
PS
It's quite difficult to get your hand on a Nano adapter with RTL8811/12/14 chipset.I compiled the current kernel with said driver, but no luck.
I have still the DU repo in my m head.Maybe I get the driver to load.
The patch from a team member didn't work.
Just some nice props^