Related
After experimenting for a while, I've managed to successfully use USB 3G dongle, and to connect my Archos 101IT, running uruk-droid 0.4.1, to the Internet over 3G data network. Test was made with two different 3G USB dongles - Huawei E1552 and ZTE MF190.
First of all a big thanks to $aur0n for uruk-droid, because without uruk-droid kernel with adequate configuration, this 3G support would not be possible.
Second, a big thanks to all guys behind usb_modeswitch project (http://www.draisberghof.de/usb_modeswitch/), for providing us with Linux support needed to switch our 3G USB dongles from default cd-rom/mass-storage mode to usb-serial mode needed for 3G operation.
Process of initial setup of 3G USB dongle to a 3G provider under Linux (and Android/Archos) is fairly complex, and requires a little Linux knowledge, but once it is configured right, usage is simple.
Unfortunately I don't see a way to make it simpler, because lot of parameters in various files are greatly dependant on model of 3G USB dongle you are using, and on settings of your 3G data provider.
DISCLAMER:
This is a proof-of-concept modification. Don't expect that everything will work from a first try.
Please note that I don't take responsibility for anything that might happen with your Archos device and/or your data on it.
I didn't had any problems with my A101IT using this mod with Huawei E1552 3G dongle and ZTE MF190 3G dongle, but that doesn't mean that someone else won't have them.
Also, if you make your 3G USB dongle work as modem using steps described here, I don't take any responsibility for possible large bills form you 3G data service provider.
Be sure that you have good and cheap 3G data plan with your 3G data service provider, if you are planning to use 3G data network for Internet connection on a daily basis.
Also, try to avoid using 3G data service while in roaming, because it is very expensive.
Technical explanation:
Basically USB tethering system on Archos is designed to work over PPP connection, provided by /system/bin/pppd via "Serial-over-USB link", provided by cdc-acm.ko kernel module, when supported cdc-acm class device is connected to USB host port of Archos.
Here is a brief description of USB tethering on Archos 101, modified to work with 3G USB dongles, since you probably going to need to edit some of this files in order to adjust them for your 3G USB dongle and your 3G provider:
1. Kernel support for 3G USB dongles.
This is provided by uruk-droid kernel.
One part you'll use from this support is usbserial.ko kernel module that will be loaded by /system/xbin/3Gmodem_init.sh with adequate parameters, when you start tethering.
2. usb_modeswitch program and support files
usb_modeswitch is responsible for switching of 3G USB dongles from default cd-rom/mass-storage mode to usb-serial mode ready for 3G operation.
You'll use it via /system/xbin/3Gmodem_init.sh, when you start tethering.
3. Archos USB tethering support which is partially in Android framework, and partially in Linux scripts called by framework.
This part of tethering support is most complex one, and in order for Android framework to be aware of data connection, we must disguise 3G data connection as a USB tethering:
Android framework calls modified /system/bin/tether_start_usb.sh, which calls /usr/bin/pppd binary, responsible for data connection to your 3G data provider.
Android framework calls modified /system/bin/tether_stop.sh, for stopping data connection to your 3G data provider.
pppd uses couple of configuration files (and additional binary /usr/xbin/chat):
from '/system/etc/ppp/peers' directory, pppd uses configuration file 'tether' (with definition of pppd options for peer it connects to - this may need editing for your 3G provider)
from '/data/' directory, pppd (via /system/xbin/chat) uses 'tether_start' file as definition of <SEND> <EXPECT> pairs of commands sent to configure modem and responses received from modem, when it connects to a peer (this may need editing for your 3G provider).
from '/system/etc/chatscripts/' directory, pppd (via /system/xbin/chat) uses 'tether_stop' file as definition of <SEND> <EXPECT> pairs with commands sent to modem and responses received from modem, when it disconnects from a peer.
This modification relies on modified '/system/bin/tether_start_usb.sh' and '/system/bin/tether_stop.sh', to be able to correctly initialize RNDIS connection or 3G modem, load adequate kernel modules and start connection, while trying to keep compatibility with original "Archos designed" way of USB tethering.
Configured adequatly ('enable' parameter to 'off' in '/etc/uruk.conf/3Gsupport' file), this modified '/system/bin/terher_start_usb.sh' WILL behave as original one. - not needed anymore - scripts auto-detect connection type and behave adequatly.
For a list of changes in recent versions please se post #2 of this thread.
Tutorial how to use RNDIS USB Tethering:
No configuration needed - if your phone is indeed of USB-RNDIS type - everything will be auto-detected.
Just plug your Archos to a RNDIS capable phone in tethering mode via USB cable, wait for at least 5 seconds (or more - depending on phone), and start tethering on Archos.
Expample of RNDIS tethering device is HTC Desire phone with built-in USB Tethering support enabled. Android based phones from "same generation as HTC Desire" are quite probably of same USB-RDNIS type.
NOTE: due to a technical reasons (bad driver), RNDIS tethering support works only if usb host mode driver (musb_hdrc.ko) is loaded in PIO (as opposed to default DMA) mode. When tethering is started, USB host mode driver is reloaded in PIO mode, so this might be indicated on the phone like USB disconnection and re-connection. This is "normal" behaviour, and for now there is nothing I can do about it. When tethering is stopped USB host mode driver is re-loaded again to DMA mode.
Tutorial how to initially configure 3G USB dongle for USB tethering:
NOTE: Everything written here, should be done in Terminal Emulator or ConnectBot (connected as local) under root shell (after 'su' command)!
Install Terminal Emulator, or ConnectBot from Market.
This step is no longer needed if you are running Uruk-Droid 0.7 or later since 3G modem/RNDIS support is integrated in it
Get 3Gsupport-0.4.zip from attachment in this post. Extract 3Gsupport-0.4.tar.gz file from .zip file and copy it to your Archos to /sdcard. Archive contains everything needed (usb_modeswitch binary and support files, replacement tether_start_usb.sh, replacement tether_stop.sh, 3Gmodem_init.sh script, 3Gmodem_detect.sh).
NOTE: Since /system/bin/tether_start_usb.sh and /system/bin/tether_stop.sh from 3Gsupport-0.4.tar.gz will replace original ones, please backup originals.
The 3Gsupport-0.4.tar.gz file contains absolute paths for all files, and should be extracted to a root ('/' path in RootExplorer).
To backup original tether_start_usb.sh and tether_stop.sh:
Code:
# su
# cp /system/bin/tether_start_usb.sh /system/bin/tether_start_usb.sh.ORIGINAL
# cp /system/bin/tether_stop.sh /system/bin/tether_stop.sh.ORIGINAL
Assuming you have 3GSupport-0.4.tar.gz in /sdcard you should do following in Terminal Emulator or ConnectBot to extract 3Gsupport-0.4.tar.gz:
Code:
# su
# cp /sdcard/3Gsupport-0.4.tar.gz /
# cd /
# tar -zvxf 3Gsupport-0.4.tar.gz
Start the Terminal Emulator, or ConnectBot (to localhost).
Issue 'su' command in terminal window to gain root access.
Plug dongle in usb host port (full size USB on A101IT).
NOTE: For A70IT you'll need something called "mini USB Type-A to USB female host cable adapter", and maybe manually loading of host-mode USB driver (musb_hdrc.ko) – I don’t have A70IT so I can’t test.
Wait couple of seconds (at least 5) and then start 3G modem detection script with '/system/xbin/3Gmodem_detect.sh' command.
The output of the detect scripts should be pretty self-explanatory, and if your modem is supported by usb_modeswitch (in both switching and non-switching mode) you should be able to see that usb serial module is loaded and configuration file is written and support for 3G modems is started.
Output should look like this:
Code:
# /system/xbin/3Gmodem_detect.sh
Supported USB device found !!!! VendorID: 12d1 - ProductID: 1446
New VendorID: 12d1
New ProductID not detected in usb-modeswitch config file. Try to detect it later !
Switching device to usbserial mode !
Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
Found devices in default mode, class or configuration (1)
Accessing device 004 on bus 002 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x81 (in)
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
SCSI inquiry data (for identification)
-------------------------
Vendor String: HUAWEI
Model String: Mass Storage
Revision String: 2.31
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI Technology
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Error resetting endpoint: -110
Resetting message endpoint 0x01
Error resetting endpoint: -19
Device is gone, skipping any further commands
Checking for mode switch (max. 20 times, once per second) ...
Searching for target devices ...
Searching for target devices ...
Found target device, now opening
Found correct target device
Mode switch succeeded. Bye.
Detected ProductID of a switched device: 140c
USB device VendorID: 12d1 ProdID: 140c. Probing serial mode
usbserial.ko module registered and /dev/ttyUSB{X} device nodes created sucessfully.
Writing default configuration to '/data/local.prop' file .....Done.
!!! REBOOT your A101IT now in order for your configuration to become active !!!
After reboot:
Disconnect your 3G USB dongle, do not connect anything to USB host port and go to Settings->Wireless & Networks->Cellphone tethering.
If there is tethering profile already defined, delete it - Archos handles only one tethering profile definition at a time.
Create new USB tethering profile.
Your APN, username and password won't be detected automatically, so fill them manually - find adequate info from your 3G service provider (for me on Telekom Srbija: APN is ‘gprsinternet’, username is ‘mts’, and password is ‘064’ (some 3G operators don't need username and password)).
This will create file '/data/tether_start' with adequate commands for ppp daemon to initialize 3G modem and make a connection to your 3G provider.
NOTE for uruk-0.6: It '/data/tether_start' file is not created after wizard finishes try following in terminal emulator:
Code:
su
chown 1000:1000 /data
chmod ug+rwx /data
then delete the tethering profile just created and re-create it again !!! Now everything should be OK.
File should look like this:
Code:
TIMEOUT 5
ECHO ON
ABORT BUSY
ABORT ERROR
ABORT 'NO CARRIER'
ABORT VOICE
ABORT 'NO DIALTONE'
ABORT 'NO DIAL TONE'
ABORT 'NO ANSWER'
ABORT DELAYED
TIMEOUT 12
'' ATZ
OK AT+CGDCONT=1,"IP","[COLOR="DarkRed"]<your APN configured in tethering wizard>[/COLOR]"
OK ATD*99#
TIMEOUT 120
CONNECT ''
If steps 3 and 4 were OK, then you should be able to test pppd connection to the Internet.
NOTE: This test assumes following:
a) that SIM/USIM card in your 3G modem doesn't require PIN code.
b) that your 3G modem automatically register SIM/USIM to a network in Automatic mode (auto-band, 3G preferred mode (EDGE service if no 3G available))
If this is not a case please take a look in section "Modifying tether_start script" later, for reference how to modify '/data/tether_start' script with adequate AT commands that should be sent to modem.
Re-plug your 3G USB dongle.
Wait at least 5 sec.
Start the Terminal Emulator, or ConnectBot (to localhost).
Issue 'su' command in terminal window to gain root access.
Issue '/system/xbin/3Gmodem_init.sh' command
Issue '/system/bin/pppd /dev/ttyUSB0 460800 debug mtu 1280 mru 1280 name <username> password <password> call tether'
If you get CONNECTED message then your dongle and /dev/ttyUSBx port is set right and everything is configured well.
Output should look like this:
Code:
ATZ
OK
AT+CGDCONT=1,"IP","[COLOR="DarkRed"]<your APN configured in tethering wizard>[/COLOR]"
OK
ATD*99#
CONNECT
You can interrupt pppd with Ctrl+C.
If you don't see CONNECT (or any) response from modem try with one of other ttyUSB[0-5] ports first, or refer to following section on modifying /data/tether_start script.
Assuming the step 5 was success, edit '3Gmod.usbPort' option to match the number you have used in test in step 5, in '/data/local.prop' file, and REBOOT your Archos.
From now you can use 3G USB tethering just by plugging 3G USB dongle, and starting 'Setup->Wireless & Network->Cellphone Tethering->Tether'.
Modifying '/data/tether_start' script for your particular 3G modem and 3G operator:
File '/data/tether_start' is standard chatscript for unix chat program ('man chat' on Google for more info and syntax reference) used by pppd when making connection.
In default tether_start file most important line is one for setting APN: ' OK AT+CGDCONT=1,"IP","<your APN configured in tethering wizard>" ' in example above.
Second important line is one that connects your modem to your 3G data provider: 'OK ATDT*99#' - for some providers it needs to be modified to 'OK ATDT*99***1#'.
If your SIM/USIM card needs PIN in order for you to be able to use your 3G USB dongle, try to disable PIN on your card before using it in 3G USB dongle.
If you can't disable PIN for your SIM/USIM card (for example, as far as I know Tele2 cards must have PIN), you'll probably need to modify 'tether_start' script and to add adequate AT commands and expected responses, before setting APN.
A solid reference of 3G modem AT commands and manufacturer/model specific AT commands can be found these pages:
http://3g-modem.wetpaint.com/page/common+AT-commands
http://3g-modem.wetpaint.com/page/Huawei+AT-commands
http://3g-modem.wetpaint.com/page/ZTE+AT-commands and
http://3g-modem.wetpaint.com/page/Sierra+Wireless+AT-commands
Example /data/tether_start script that sends PIN 1234 and sets "auto 3G/GPRS mode" (for Huawei 3G USB dongles only !!!) looks something like this:
Code:
ABORT 'BUSY'
ABORT 'NO CARRIER'
ABORT 'VOICE'
ABORT 'NO DIALTONE'
ABORT 'NO DIAL TONE'
ABORT 'NO ANSWER'
ABORT 'DELAYED'
REPORT CONNECT
TIMEOUT 6
'' ATQ0
OK-AT-OK ATZ
TIMEOUT 3
OK AT+CPIN=1234
OK-AT-OK ATI
OK ATZ
OK ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK AT\^SYSCFG=14,2,3fffffff,0,1
OK-AT-OK AT+CGDCONT=1,"IP","<your APN configured in tethering wizard>"
OK ATDT*99***1#
TIMEOUT 30
CONNECT ''
There is a plenty of information on the Internet on how to configure Linux ppp chatscripts for particular models of 3G USB dongles and 3G operators, so please SEARCH, READ & TRY before asking, since you'll have to try it anyway at the end .
ISSUES:
First start of tethering after plugging, re-plugging 3G USB dongle or stopping tethering can (and probably will) end in "unable to connect by tethering" message.
This happens since dongle needs to be switched to usb-serial mode, kernel modules must be loaded, and most important 3G dongle must register to 3G data network to be able to connect, and Android framework timeout before connection is established.
Solution is to just start tethering again, and since there is no need to do a usb_modeswitch again, and kernel modules are already loaded, and dongle is registered to 3G network provider, it will connect before timeout.
When Archos wakes-up after sleep, some dongles (ZTE-MF190 is one of them), wake-up in default mode (non usb-serial mode), so tethering needs to be stopped and started manually.
One possible workaround is to enable "Prevent device from going to sleep" in 'Setup->Wireless & Network->Cellphone Tethering', but with uruk-droid 0.4.1 based on Archos 2.0.x firmware this option didn't work as expected - device still goes to sleep, even if tethering is connected.
With 2.1.x based uruk-droid (0.6 is first) it seems that this option works.
QUESTIONS & ANSWERS:
Q: Can I use my phone and 3G modem whithout reconfiguring tethering every time I switch them ?
A: Please take a look in this post
FUTURE PLANS:
Integration of real USB-cable tethering with Android based devices that require Archos to tether using usbnet.ko module via "Ethernet-over-USB" type of link. - DONE
Change log:
0.4.1 - Integrated in UrukDroid-0.7 with minor script errors corrected, tutorial updated
0.4 - RNDIS (Ethernet-over-USB) tethering merged with 3G modem, and Archos default USB tethering support this version needs UrukDroid-0.6 at least
changed scripts, in order to acheive auto-detection of tethering type (RNDIS, 3G modem or Archos default Serial-Over-USB)
changed location of saved 3G modem configuration data to /data/local.prop, so the configuration data is avalible upon reboot as Android properties (/data/local.prop file is NOT overwritten by 3Gmodem_detect.sh, so don't worry ;-) )
elimninated need for /etc/uruk.d service, because of previous changes
0.3 - lot of changes in scripts, in order to make 3Gdongle detection and module load configuration simplier.
/system/xbin/3Gmodem_detect.sh introduced for purpose above
tutorial changed to follow 3Gmodem_detect.sh usage
compatible with 3G USB dongles that don't need switching (like Huawei E176)
wokring on uruk-0.6RC2
0.2 - changes to '/system/etc/uruk.d/3Gsupport' script to conform to urukdriod 0.5 standard
'/system/etc/uruk.d/3Gsupport' script now supports (beside start and stop): status, UIstatus and config parameters as well as second parameter force
no other functional changes
working on urukdroid 0.5 and 0.4.1
0.1 - Initial release tested on urukdroid 0.4.1 and 0.5
Here is the list of 3G modems and providers confirmed to work and optional notes if '/data/tether_start' needed to be altered:
1. Huawei E1552 on MTS Serbia (APN: gprsinternet, U: mts, P: 064) and VIP Serbia (APN: vipmobile, U: vipmobile, P: vipmobile)
2. Huawei E1550 on MTS Serbia (APN: gprsinternet, U: mts, P: 064) and VIP Serbia (APN: vipmobile, U: vipmobile, P: vipmobile), and on Starhub (Singapore) (APN as shinternet no U: and no P
3. ZTE MF190 on MTS Serbia (APN: gprsinternet, U: mts, P: 064) and VIP Serbia (APN: vipmobile, U: vipmobile, P: vipmobile)
4. Huawei E173 on MTS Serbia (APN: gprsinternet, U: mts, P: 064) and VIP Serbia (APN: vipmobile, U: vipmobile, P: vipmobile)
5. Huawei E176 on unknown 3G provider/params
6. Huawei E1691 on Wind Mobile in Canada 3G provider and unknown params, but with configuration file change described in this post
7. Huawei E153 on unknow 3G provider/params
Here is the list of phones with RNDIS USB tethering, confirmed to work:
1. HTC Desire (stock 2.29.405.2 with built-in USB Tethering support enabled)
2. US HTC HD2 running a Desire-based NANDroid ROM on T-mobile (APN: epc.tmobile.com, no U: , no P: )
awesome, will have to try this out on my tmobile web and walk III stick later.
Thanks for this very well done explanation ! I'll try on my 70
solune said:
Thanks for this very well done explanation ! I'll try on my 70
Click to expand...
Click to collapse
Note that you'll probably need microUSB-Type A to USB host cable adapter in order to use 3G USB modem dongle.
I really don't know does Archos 70IT automaticaly unload's clinet mode usb driver, and loads host-mode driver when you plug in microUSB host adapter cable (it should do it - that is one of reasons why host cable has one pin more), but if it doesn't you'll have to load musb_hdrc.ko module in manually.
I think that it must be loaded with parameter mode_default set to 1 in order to activate host mode ('insmod /lib/modules/musb_hdrc.ko mode_default=1').
great it is a good news
but no simply
how the merge on UrukDroid
nenadr said:
Note that you'll probably need microUSB-Type A to USB host cable adapter in order to use 3G USB modem dongle.
I really don't know does Archos 70IT automaticaly unload's clinet mode usb driver, and loads host-mode driver when you plug in microUSB host adapter cable (it should do it - that is one of reasons why host cable has one pin more), but if it doesn't you'll have to load musb_hdrc.ko module in manually.
I think that it must be loaded with parameter mode_default set to 1 in order to activate host mode ('insmod /lib/modules/musb_hdrc.ko mode_default=1').
Click to expand...
Click to collapse
Yes I already have microUSB-Type A to USB Host cable adapter, and it works for my USB drive for example. I've already connected my 3G USB modem dongle just for see what's appen, and light blink on it, so I have hope to do something with your very well explained guide
I'll make feed-back here if host-mode driver loads or if I need to mount it manually.
cajl said:
great it is a good news
but no simply
Click to expand...
Click to collapse
I know it is not simple but it is try-error only until your connection is succesfull for a first time (while you fine tune params for your 3G modem, and for your 3G operator). After that is just metter of sticking 3G USB dongle, waiting 5 seconds, and clicking Tethering on Power Widget (twice )
cajl said:
how the merge on UrukDroid
Click to expand...
Click to collapse
I'll hopefully upgrade to uruk 0.5 today, and adapt scripts (mainly uruk-config ones), to 0.5 version of uruk-droid during the weekend, and post those scripts here.
After that my plan is to upgrade to a uruk-0.6RCx and play with USB cable tethering with Android phones that tether via "Ethernet-over-USB" support (usbnet.ko module).
Hopefully, I will know soon enough if that is operational, and after that I'll talk to $aur0n about integration.
solune said:
Yes I already have microUSB-Type A to USB Host cable adapter, and it works for my USB drive for example. ......
Click to expand...
Click to collapse
If it works with USB drive, that should be proof enough that Archos 70IT is switching to USB host mode just by plugging microUSB host adapter. Good news, more devices supported....
solune said:
I'll make feed-back here if host-mode driver loads or if I need to mount it manually.
Click to expand...
Click to collapse
Please do, thank you very much.
i'm up to step 6 . it was pretty clear up to then. a) i dont have a 3Gsupport.conf file in there b) i guess the bit in the [code ] box isnt what you need to do to edit it c) presuming you mean just open the 3Gsupport file and edit that, am i just replacing all instances of vendor and product or also the VendorID /ProductID bits too?
thefunkygibbon said:
i'm up to step 6 . it was pretty clear up to then. a) i dont have a 3Gsupport.conf file in there b) i guess the bit in the [code ] box isnt what you need to do to edit it c) presuming you mean just open the 3Gsupport file and edit that, am i just replacing all instances of vendor and product or also the VendorID /ProductID bits too?
Click to expand...
Click to collapse
Yup I've made a mess in that part of tutorial (wrong path/name of config file, not clear enough explanation):
You have to edit file '/system/etc/uruk.conf/3Gsupport' and it should look something like:
service_enabled=1
enable=on
vendor=12d1
product=1446
port=0
I've corrected that part of initial post. Thanks.
Pictures of this "exploit"
{
"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"
}
I've good news for Huawei E176 user, The modem doesn't require to switch mode.
So we just only need to edit ther_usb start and stop .sh
and here is the code for E176
/system/bin/tether_start_usb.sh
Code:
#!/bin/sh
# $1 is the user (not a mandatory argument)
# $2 is the password (not a mandatory argument)
setprop "3Gmod.enable" "on"
setprop "3Gmod.defVendorID" "12d1"
setprop "3Gmod.defProductID" "1003"
setprop "3Gmod.usbPort" "0"
rmmod usbserial
sleep 1
insmod /lib/modules/usbserial.ko vendor=0x12d1 product=0x1003
sleep 1
SUPPORT3G=`getprop "3Gmod.enable"`
VENDOR3G=`getprop "3Gmod.defVendorID"`
PRODUCT3G=`getprop "3Gmod.defProductID"`
PORT3G=`getprop "3Gmod.usbPort"`
if [ ${SUPPORT3G} != on ]; then
insmod /lib/modules/musb_hdrc.ko mode_default=1
insmod /lib/modules/cdc-acm.ko
if [ $# -eq 0 ]
then
/system/bin/pppd /dev/ttyACM0 460800 call tether
else
/system/bin/pppd /dev/ttyACM0 460800 name $1 password $2 debug call tether
fi
else
if [ $# -eq 0 ]; then
/system/bin/pppd /dev/ttyUSB${PORT3G} 921600 call tether
else
/system/bin/pppd /dev/ttyUSB${PORT3G} 921600 name $1 password $2 call tether
fi
fi
/system/bin/tether_stop.sh
Code:
#!/bin/sh
SUPPORT3G=`getprop "3Gmod.enable"`
if [ $1 = "DUN" ]
then
/system/xbin/dund --killall
elif [ $1 = "PAN" ]
then
/system/bin/pand --killall
else
if [ ${SUPPORT3G} != on ]; then
kill -9 $(pidof pppd)
/system/bin/rmmod cdc_acm
/system/bin/rmmod musb_hdrc
else
killall -15 pppd
fi
fi
Meen said:
I've good news for Huawei E176 user, The modem doesn't require to switch mode.
So we just only need to edit ther_usb start and stop .sh
and here is the code for E176
Click to expand...
Click to collapse
Thanks for the info on Huawei E176. I'll make some chaneges in original scripts, for those users that have modems that don't require switching, to be able to use original scripts. It'll be in 0.3 in next day or so.
cajl said:
Pictures of this "exploit"
Click to expand...
Click to collapse
could you please post some bigger pictures? I'm not sure its big enough for people to see.
ok nenadr, I'll try the rest of the process tonight cant wait to try it. have you managed to get an idea of the sort of battery drain using one of these? ie is it much worse than using wifi?
I'm getting the following on step 7 . I am using uruk 0.5 I it makes any difference
/system/xbin/3Gmodem_init.sh 12d1 1003
No 3G USB dongle support detected. Will try to initialize modem.
Found USB 3Gmodem dongle in default mode connected to device. Starting modeswitch.
ERROR: Module option does not exist in /proc/modules
ERROR: Module usbserial does not exist in /proc/modules
ERROR: Module usb_storage does not exist in /proc/modules
Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
No devices in default mode found. Nothing to do. Bye.
sh: 1003: unknown operand
Found new Product ID: 0002
1003
0001
0a19 for Vendor ID: .
Loading 3G modem kernel driver with adeqate configuration
insmod: error inserting '/lib/modules/usbserial.ko': -1 Invalid parameters
Kernel module load failed. Exiting.
#
thefunkygibbon said:
I'm getting the following on step 7 . I am using uruk 0.5 I it makes any difference
Click to expand...
Click to collapse
Please, take a look couple of posts up, for an alternate solution, because it seems that your vendorID and productID doesn't need mode-switching. I'll fix the scripts, and tutoral for that case tomorrow.
Sent from my A101IT using Tapatalk
lol. oh yeah. sorry. i didnt know mine was a E176 and as such i skimmed over those posts sorry for appearing to be a bit of a idiot. cant wait for the new script.
btw has $auron shown any interest in incorporating this into his rom. would be useful to have all the legwork done automatically and maybe urukconfig could do some of the stuff that isnt able to be done automatically
thefunkygibbon said:
btw has $auron shown any interest in incorporating this into his rom. would be useful to have all the legwork done automatically and maybe urukconfig could do some of the stuff that isnt able to be done automatically
Click to expand...
Click to collapse
yes, his shown interest but this code is stll not mature (and tested on) enough devices to be merged with uruk.... meybe for some later urukdroid, who knows
Sent from my A101IT using Tapatalk
Hi,
I am trying to use a Columbus V800+ usb gps (mtk3329) with my Alwinner A10 tablet. Current rom is Cyanogenmod 10 - 20130327. kernel 3.0.36+. After connecting gps, lsusb show up: Bus 01 Device 008: ID 0e8d:3329. Using USB info apk I got: /dev/bus/usb/001/008 assigned to mtk gps. Seems that device was detected, but I can not use it. I tried to find the CDC-ACM.ko module in lib/modules, but there is no such file.
dmesg after inserting gps:
insmod_host_driver
[sw_hcd0]: sw_usb_host0_enable start
-----------------sw_hcd0_soft_disconnect----------
[sw_hcd0]: open_usb_clock
[sw_hcd0_host0]:set USB power ON
[sw_hcd0]:sw_usb_host0-enable end
-----------------IRQ CONNECT-----------------------
[sw_hcd0]: reset port
[sw_hcd0]:reset port stopped
spurious?
usb 1-1 new full speed USB device number 2 using sw_hcd_host0
[sw_hcd0]: reset port
[sw_hcd0]:reset port stopped
[sw_hcd0]:sw_hcd_h_disable, epnum = 0
[sw_hcd0]:sw_hcd_h_disable, epnum = 0
Does anyone knows how to get the gps working ? I am new to android, but reads a lot.
Thank you in advance.
Heres how to connect to android wear using adb over wifi, theres still some issues, so ill put it here and if someone has some information please share with us:
On wear:
Go to config -> about -> tap the version umber 7 times (it will enable dev options)
Now go back to config menu
Go to developer options
Enable adb (it will also enable the option adb over bluetooth)
On phone:
Open android wear app
Tap the cog icon
Enable Debug over wifi -> Check that the host will be connected (its the android wear)
Now open cmd (you will need to have adb on your path variable):
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444 // if this gives an error try replacing localhost with 127.0.0.1
adb -s localhost:4444 tcpip 5555 // if this gives an error try replacing localhost with 127.0.0.1
On phone:
Disable adb over bluetooth
Disable bluetooth
On wear:
Go to config -> developer options -> disable the option auto change wifi state
Go to wifi, connect to your wifi
still on wifi, theres an advanced options, there you can get your ip address
on cmd:
adb connect 192.168.1.3:5555 // replace 192.168.1.3 with your android wear ip
THE PROBLEM:
Android wear keeps desconnecting the wifi for a lot of reasons, some that i know:
It detect bluetooth connection (its an automatic power save feature)
But even if you disconnect from bluetooth, sometimes it keep disconnecting.
THE SOLUTION:
I have found a feature under developer options named: Enable wifi state change. This is enabled by default, so disabling it should prevent the wear from disconnecting from wifi, and it does. But sometimes android wear auto enable this feature, even if you turn it off manually. If someone know something about it, or another way to prevent wifi disconnection, please share with us.
On phone:
Open android wear app
Tap the cog icon
Enable Debug over wifi -> Check that the host will be connected (its the android wear)
==============================
Unfortunately doesn't work on my phone, cannot find the "Debug over wifi" option, only Debug over bluetooth available.
The same here!! How did you proceed?
Do you know if there is any way to figure out the port being used?
sagits2016 said:
adb connect localhost:4444 // if this gives an error try replacing localhost with 127.0.0.1
Click to expand...
Click to collapse
Thank you SO MUCH!! I have been trying to connect my watch for days!
I use a Galaxy S5 (G900H) with rooted Android 5.0.
I am connecting a serial device to it via USB using cdc-acm driver (compiled in the kernel) and trying to read it from my android application, It works fine on other devices (older and newer).
When connecting the device, the device file /dev/ttyACM0 is created but when trying to read from it I receive an error Permission denied.
When running
Code:
setenforce 0
and setting SELinux to Permissive mode - everything works fine and the app reads the device file successfully.
After connecting the USB in Enforcing mode, the dmesg says:
Code:
cdc_acm 2-1:1.0: usb_probe_interface
cdc_acm 2-1:1.0: usb_probe_interface
cdc_acm 2-1:1.0: This device cannot do calls on its own. It is not a modem.
cdc_acm 2-1:1.0: ttyACM0: USB ACM device
I tried making a new policy using audit2allow but couldn't find any "denied" message to use in order to create an "allow" rule.
Is there any way to use the device file via my app without setting SELinux to permissive? I can edit the kernel and make a new one if needed, but I really prefer not to.
Thanks!
{
"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^