Related
Hey guys im pretty good with adb, not many problems at all but ive recently ditched windows for a real os Ubuntu but im not super familiar with the commands and how to do this and that. Can someone hep me with setting up adb in Linux the guide posted is really rough for noobs to linux.
well if you using linux then you will be using terminal to type out the adb commands. once you installed adb into linux you can type adb /? and it will give you the list of commands. In most cases you have to use sudo when running adb commands, at least using sudo when starting the adb server.
no i have no problem using adb at all, i was asking how to install it i cant get it to run in the first place ?
you have to follow the steps for linux, they are mostly meant for ubuntu afaik. Download the special linux SDK, Eclipse etc. One thing you should do to make adb work is add your sdk/tools directory to linux's $PATH.
It should go something like this...
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
$ adb devices (now adb should do something, if nothing else at least error, no devices)
Is this what you were looking for? or some other issue..
sonikamd said:
you have to follow the steps for linux, they are mostly meant for ubuntu afaik. Download the special linux SDK, Eclipse etc. One thing you should do to make adb work is add your sdk/tools directory to linux's $PATH.
It should go something like this...
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
$ adb devices (now adb should do something, if nothing else at least error, no devices)
Is this what you were looking for? or some other issue..
Click to expand...
Click to collapse
thank you you are officially great
jamizzal said:
thank you you are officially great
Click to expand...
Click to collapse
Just to expand on that a little, when you adb start-server you will need to sudo, IIRC on ubuntu root is only enable to connect to USB.
Eg
Code:
sudo adb start-server
adb devices
adb logcat
NPerry said:
Just to expand on that a little, when you adb start-server you will need to sudo, IIRC on ubuntu root is only enable to connect to USB.
Eg
Code:
sudo adb start-server
adb devices
adb logcat
Click to expand...
Click to collapse
thank you i was wondering why i could not find my device
sonikamd said:
you have to follow the steps for linux, they are mostly meant for ubuntu afaik. Download the special linux SDK, Eclipse etc. One thing you should do to make adb work is add your sdk/tools directory to linux's $PATH.
It should go something like this...
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
$ adb devices (now adb should do something, if nothing else at least error, no devices)
Is this what you were looking for? or some other issue..
Click to expand...
Click to collapse
Thank youu a lot! It's working with this but everytime I am rebooting Ubunutu 9.04 I have to type in these commands again to get adb...
what can I do?
you have to put this command in your .bashrc file
$ sudo gedit ~/.bashrc
then you need to enter your password
in the file you just need to add that command at the end :
PATH=$PATH:/SDK_PATH/tools/
export PATH
SDK_PATH.. you need to put your path .. something like ~/android-sdk-linux/
then you need to reboot to see if it works ;-)
enjoy !
how do you
install apps on the virtual device?????????
This is how I did it on my machine:
1. Download this zip file
2. Extract the file and copy both files to /usr/bin/
3. In the terminal type lsusb and copy first 4 ID symbols for High Tech Computer Corp
4. In the terminal type sudo gedit /etc/udev/rules.d/51-android.rules and paste the following SUBSYSTEM=="usb",ATTRS(idVendor)=="0bb4",SYMLINK+="android_adb",MODE="0666" where the bold symbols are taken from step #3.
5. Save and close everything. Unplug your device and plug it back again. ADB should now work as supposed.
Thanks for this easy instruction and for the files Karolis. Everything works fine on Ubuntu 10.10 x64
Karolis said:
4. In the terminal type sudo gedit /etc/udev/rules.d/51-android.rules and paste the following SUBSYSTEM=="usb",ATTRS(idVendor)=="0bb4",SYMLINK+="android_adb",MODE="0666" where the bold symbols are taken from step #3.
Click to expand...
Click to collapse
Just in case anyone else runs across this, in Suse 11.3 I needed to replace the brackets around idVendor with curly braces.
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",SYMLINK+="android_adb",MODE="0666"
Even after that, I don't seem to get any devices in adb
Code:
# adb devices
List of devices attached
Here is /var/log/messages when plugging the device in
Code:
Apr 8 16:40:38 vaio kernel: [362518.911578] usb 2-1.1: new high speed USB device using ehci_hcd and address 9
Apr 8 16:40:38 vaio kernel: [362518.997898] usb 2-1.1: New USB device found, idVendor=04e8, idProduct=681c
Apr 8 16:40:38 vaio kernel: [362518.997905] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 8 16:40:38 vaio kernel: [362518.997910] usb 2-1.1: Product: SAMSUNG_Android
Apr 8 16:40:38 vaio kernel: [362518.997914] usb 2-1.1: Manufacturer: SAMSUNG
Apr 8 16:40:38 vaio kernel: [362518.997918] usb 2-1.1: SerialNumber: 3030610AA1A700EC
Apr 8 16:40:38 vaio kernel: [362519.007324] cdc_acm 2-1.1:1.0: This device cannot do calls on its own. It is not a modem.
Apr 8 16:40:38 vaio kernel: [362519.007426] cdc_acm 2-1.1:1.0: ttyACM0: USB ACM device
Apr 8 16:40:38 vaio kernel: [362519.016244] scsi11 : usb-storage 2-1.1:1.2
Apr 8 16:40:38 vaio modem-manager: (ttyACM0) opening serial device...
Apr 8 16:40:38 vaio modem-manager: (ttyACM0): probe requested by plugin 'Generic'
Apr 8 16:40:39 vaio kernel: [362520.016848] scsi 11:0:0:0: Direct-Access Android UMS Composite 0001 PQ: 0 ANSI: 2
Apr 8 16:40:39 vaio kernel: [362520.017149] sd 11:0:0:0: Attached scsi generic sg2 type 0
Apr 8 16:40:39 vaio kernel: [362520.021880] scsi 11:0:0:1: Direct-Access Android UMS Composite 0001 PQ: 0 ANSI: 2
Apr 8 16:40:39 vaio kernel: [362520.022034] sd 11:0:0:1: Attached scsi generic sg3 type 0
Apr 8 16:40:39 vaio kernel: [362520.026214] sd 11:0:0:0: [sdc] Attached SCSI removable disk
Apr 8 16:40:39 vaio kernel: [362520.027091] sd 11:0:0:1: [sdd] Attached SCSI removable disk
Apr 8 16:40:42 vaio modem-manager: (ttyACM0) closing serial device...
Apr 8 16:40:42 vaio modem-manager: (Generic): GSM modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1 claimed port ttyACM0
Apr 8 16:40:42 vaio modem-manager: Added modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1
Apr 8 16:40:42 vaio modem-manager: Exported modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1 as /org/freedesktop/ModemManager/Modems/5
ls -al /dev/android_adb before plugging phone in
Code:
# ls -al /dev/android_adb
ls: cannot access /dev/android_adb: No such file or directory
and after
Code:
ls -al /dev/android_adb
lrwxrwxrwx 1 root root 15 2011-04-08 16:35 /dev/android_adb -> bus/usb/002/008
Am I doing something wrong?
i did all thing but it stiil dont show this first in terminal
Code:
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
thanks.
koala996 said:
you have to put this command in your .bashrc file
$ sudo gedit ~/.bashrc
then you need to enter your password
in the file you just need to add that command at the end :
PATH=$PATH:/SDK_PATH/tools/
export PATH
SDK_PATH.. you need to put your path .. something like ~/android-sdk-linux/
then you need to reboot to see if it works ;-)
enjoy !
Click to expand...
Click to collapse
Thanks bud, this helped me out.. Recently installed Ubuntu back on my machine and could not remember for the life of me how to do this lol. So, thanks again.
Hi My name is abbas, I followed the procedure to set the path in ubuntu for adb, however after setting the path: when I typed
$adb
the response was:
$ error while loading shared libraries: libncurses.so.5: wrong ELF class: CLASS64
Can someone help me, i'm using both Windows and Linux Ubuntu 11.10 OS, and i did manage to get adb to work on Windows, but now i prefer Linux and i can't manage adb to work. Downloaded sdk, proprietary platform etc. . . Exported path, installed lsusb-1.0.8, edited rules and inserted rules for Sony Ericsson etc. But when i type $ sudo adb start-server (then i type my password) it says that command is unknown. " sudo: adb: command not found " so my question is what the f**k i'm doing wrong?
EDIT: Changed location of sdk folder, eclipse. . . And it worked, tnx anyway. . .
sonikamd said:
you have to follow the steps for linux, they are mostly meant for ubuntu afaik. Download the special linux SDK, Eclipse etc. One thing you should do to make adb work is add your sdk/tools directory to linux's $PATH.
It should go something like this...
$ echo $PATH (should return the directories associated with $PATH)
$ export PATH=$PATH:/home/user/sdk/tools (replace with path to your tools directory, you may need to add 'sudo' to the beginning of this cmd)
$ echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
$ adb devices (now adb should do something, if nothing else at least error, no devices)
Is this what you were looking for? or some other issue..
Click to expand...
Click to collapse
Thanks alot!
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
ketchupotamus said:
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
Click to expand...
Click to collapse
Yup. I have similar experiences on my linux box.
Try adb shell and see if you get a shell into the device.
ketchupotamus said:
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
Click to expand...
Click to collapse
the one time I had that problem, killing and starting adb fixed it, but it looks like you're already doing that.
Try launching Eclipse?
When I had the same setup as you (ubuntu 9.10 + Eclipse + all relevant parts), adb "just worked".
Running under Vista32bit though, adb only works when I have Eclipse running. Don't know why. Don't care why. Felt like banging my head into a wall when I realized that. (More specifically: under Vista32bit, my Vogue shows up with only one question mark, not a whole slew like you have.)
Anyway, try making sure Eclipse is running when you try to connect via adb. Who knows. Maybe it's a cross-platform issue.
Thanks for the reply. Everything works fine in Windows Vista 32bit, although the device serial number shows up as a question mark. I read somewhere that adb is broken for the 2.6.27+ kernels. There is a proposed fix:
review.source.android.com/#patch,sidebyside,10633,1,adb/usb_linux.c
I've compiled the source, tried the new adb and still not working... maybe the next official release will be better.
I shell access and can browse filesystem with adb shell, but ddms in Eclipse doesn't show much useful information.
Excellent work by the way! And thank you.
Found a compiled version of adb with the fix highlighted on code.google.com:
h t t p ://floe.butterbrot.org/external/adb.gz
Don't forget to make it executable.
That worked for me
This was hard to find. Thanks.
I just installed Android on my Sprint touch vogue. No luck using adb to get a shell on my phone.
My environments are Debian sid 2.6.32 and/or OS X Snow Leopard. I installed the r06 SDK and adb doesn't work under either OS. ./adb devices shows nothing, ./adb shell shows device not found. Under debian, I downloaded the recompiled version of adb linked above, no change
dmesg shows:
Code:
usb 1-3.2: USB disconnect, address 28
usb 1-3.2: new full speed USB device using ehci_hcd and address 31
usb 1-3.2: New USB device found, idVendor=0bb4, idProduct=0c02
usb 1-3.2: New USB device strings: Mfr=3, Product=2, SerialNumber=0
usb 1-3.2: Product: Android Phone
usb 1-3.2: Manufacturer: HTC
usb 1-3.2: configuration #1 chosen from 1 choice
scsi9 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 31
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 9:0:0:0: Direct-Access HTC Android Phone 0100 PQ: 0 ANSI: 2
sd 9:0:0:0: Attached scsi generic sg2 type 0
sd 9:0:0:0: [sdb] Attached SCSI removable disk
Thanks for any help.
Might have figured something out that can help. uninstall the mass storage driver. I just did this and it connected right up.
I put the P880 in software mode. I hope this is correct.
I am using Xubuntu 12.04 and I execute the commands as user root in a shell
Code:
adb reboot oem-unlock
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Code:
adb devices
List of devices attached
[nothing]
Code:
lsusb | grep LG
Bus 003 Device 003: ID 1004:61f1 LG Electronics, Inc.
Code:
grep -i 1004 /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", ATTR{idProduct}=="61c5", MODE="0600", OWNER="<~/>
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", ATTR{idProduct}=="61f1", MODE="0600", OWNER="<~/>
Adb does not work in software update mode. You have to boot to your normal android system. Make sure usb debugging is enabled.
Thanks, I cannot activate usb-debugging, it is grey. Is it ok to use battery-loading with usb?
You can't activate usb-debugging while your phone is plugged in. Just plug out the usb-cable then it should work.
Dexxon said:
You can't activate usb-debugging while your phone is plugged in. Just plug out the usb-cable then it should work.
Click to expand...
Click to collapse
Thanks, now I get a response.
When i execute "adb reboot oem-unlock" with my Xubuntu 12.04 the phone reboots and I see a very very small red text for a short time and then this disappears and I see the phone is loading the battery.
Whats the version of your ROM?
Device: LGE LG-P880
Android Version: 4.1.2
Build: JZO54K
lg-optimus said:
Device: LGE LG-P880
Android Version: 4.1.2
Build: JZO54K
Click to expand...
Click to collapse
Your SW version is 262-000, afaik to unlock bootloader you gotta write directly to fuse, the official way won't work. There is a topic on general subforum on how to do this. Good luck
for other devices follow this
****i am not responsible for your phone or anything you do with aircrack-ng
this guide will help you, do what a $1,295.00 PWN PHONE can!!
{
"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"
}
------------------------------------------------------------------------------------------------
Things You Need
------------------------------------------------------------------------------------------------
1) Nexus 5 (rooted)
2) OTG Cable
3) list of USB supported
.TP-LINK TL-WN722N(confirmed by me & DragonHunt3r)
.Linksys WUSB600N V2 (confirmed by DragonHunt3r)
.TP-LINK TL-WN725N V1 & V2
.ALFA Network AWUS036H
(if you have other wifi usb then just ask ill try to add it into the guide)
4) Ubuntu (to compile kernel)
------------------------------------------------------------------------------------------------
PART A
(Compiling Kernel)
------------------------------------------------------------------------------------------------
Setting up your ubuntu machine
Code:
$ sudo apt-get update
Code:
$ sudo apt-get install oracle-java6-installer
Code:
$ sudo apt-get install git gnupg ccache lzop flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32bz2-1.0 lib32ncurses5-dev x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z1-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc libreadline6-dev lib32readline-gplv2-dev libncurses5-dev bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev squashfs-tools pngcrush schedtool dpkg-dev
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Code:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/
create a file /etc/udev/rules.d/51-android.rules (as the root user)
copy paste the below code and save
Code:
# adb protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="<username>"
# fastboot protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="<username>"
# adb protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="<username>"
# fastboot protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="<username>"
# adb protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="<username>"
# fastboot protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="<username>"
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="<username>"
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="<username>"
# adb protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="<username>"
# adb protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d002", MODE="0600", OWNER="<username>"
# fastboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="<username>"
# usbboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d00f", MODE="0600", OWNER="<username>"
# usbboot protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d010", MODE="0600", OWNER="<username>"
# adb protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="<username>"
# fastboot protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="<username>"
# adb protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0600", OWNER="<username>"
# fastboot protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0600", OWNER="<username>"
<username> must be replaced by the actual username of the user who is authorized to access the phones over USB.
Setting correct paths
Code:
gedit android-path.sh
cope paste the code and save it
Code:
export CC=$(pwd)/arm-eabi-4.6/bin/arm-eabi-
export CROSS_COMPILE=$(pwd)/arm-eabi-4.6/bin/arm-eabi-
export ARCH=arm
export SUBARCH=arm
export PATH=$PATH:$(pwd)/andorid_boot_tools_bin
Make it executable and source to current terminal window.
(you need to source it to your current terminal window before you compile)
Code:
$ chmod +x android-path.sh
$ source android-path.sh
Download Source (any kernel source can be used)
ElementalX Kernel Source
Franco.kernel Source
Android Kernel Source
using andoid kernel source
Code:
$ git clone https://android.googlesource.com/kernel/msm.git
Code:
$ cd msm/
$ git branch -a
$ git checkout origin/android-msm-hammerhead-3.4-kitkat-mr2
Code:
$ make hammerhead_defconfig
$ make menuconfig
Adding required drivers
For TP-LINK_TL-WN722N
Code:
quick look in [URL="https://wikidevi.com/wiki/TP-LINK_TL-WN722N"]wikidev[/URL] will tell you that TP-LINK TL-WN722N uses [URL="http://wireless.kernel.org/en/users/Drivers/ath9k_htc"]ath9k_htc[/URL] drivers
Enabling [URL="http://wireless.kernel.org/en/users/Drivers/ath9k"]ath9k[/URL] drivers in kernel
To enable ath9k, you must first enable mac80211 through make menuconfig when compiling your kernel. If you do not know what this means then please learn to compile kernels or rely on your Linux distribution's kernel. Below are the options you need to enable ath9k through make menuconfig.
[CODE]Networking support --->
Wireless --->
< * > cfg80211 - wireless configuration API
< * > Generic IEEE 802.11 Networking Stack (mac80211)
You can then enable ath9k in the kernel configuration under
Code:
Device Drivers --->
[*] Network device support --->
Wireless LAN --->
Atheros Wireless Cards ---->
< * > Atheros 802.11n wireless cards support
< * > Atheros HTC based wireless card support
save and exit menuconfig
check in your .config file if you have them enable(its a hidden file)
Code:
CONFIG_ATH_COMMON=y
CONFIG_ATH9K_HW=y
CONFIG_ATH9K_COMMON=y
CONFIG_ATH9K_HTC=y
[/CODE]
For TP-LINK TL-WN725N V1 & V2
Code:
quick look in [URL="https://wikidevi.com/wiki/TP-LINK_TL-WN725N_v1"]V1[/URL] & [URL="https://wikidevi.com/wiki/TP-LINK_TL-WN725N_v2"]V2[/URL] wikidev will tell you that TP-LINK_TL-WN725N uses [URL="http://wireless.kernel.org/en/users/Drivers/rtl819x"]rtl8192cu[/URL] & [URL="https://github.com/lwfinger/rtl8188eu"]8188eu[/URL] drivers
To enable rtl8192cu & 8188eu, you must first enable rtl8192cu & 8188eu through make menuconfig when compiling your kernel. If you do not know what this means then please learn to compile kernels or rely on your Linux distribution's kernel. Below are the options you need to enable rtl8192cu & 8188eu through make menuconfig.
[CODE]Device Drivers --->
[*] Network device support --->
Wireless LAN --->
[*] Realtek RTL8192CU/RTL8188CU USB Wireless Network Adapter
For Linksys WUSB600N V2
Code:
quick look in [URL="https://wikidevi.com/wiki/Linksys_WUSB600N_v2"]wikidev[/URL] will tell you that WUSB600N V2 uses [URL="http://wireless.kernel.org/en/users/Drivers/rt2800usb"]rt2800usb[/URL] drivers
To enable rt2800usb, you must first enable rt2800usb through make menuconfig when compiling your kernel. If you do not know what this means then please learn to compile kernels or rely on your Linux distribution's kernel. Below are the options you need to enable rt2800usb through make menuconfig.
[CODE]Device Drivers --->
[*] Network device support --->
Wireless LAN --->
Ralink driver support ---->
< * > Ralink rt27xx/rt28xx/rt30xx (USB) support -->
< * > rt2800usb - Include support for rt35xx devices (EXPERIMENTAL) (NEW)
< * > rt2800usb - Include support for unknown (USB) devices
For ALFA Network AWUS036H
Code:
quick look in [URL="https://wikidevi.com/wiki/ALFA_Network_AWUS036H"]wikidev[/URL] will tell you that AWUS036H uses [URL="http://wireless.kernel.org/en/users/Drivers/rtl8187"]rtl8187[/URL] drivers
Enabling [URL="http://wireless.kernel.org/en/users/Drivers/ath9k"]rtl8187[/URL] drivers in kernel
To enable rtl8187, you must first enable rtl8187 through make menuconfig when compiling your kernel. If you do not know what this means then please learn to compile kernels or rely on your Linux distribution's kernel. Below are the options you need to enable rtl8187 through make menuconfig.
[CODE]Networking support --->
Wireless --->
< * > Common routines for IEEE802.11 drivers
< * > Generic IEEE 802.11 Networking Stack (mac80211)
You can then enable rtl8187 in the kernel configuration under
Code:
[CODE]
Device Drivers --->
[*] Network device support --->
Wireless LAN --->
[*] Realtek 8187 and 8187B USB support
save and exit menuconfig[/CODE]
save and exit menuconfig if you dint do it
now your ready to compile
Code:
make -j4
this will take some time to compile
you should get something like this in the end
Code:
Kernel: arch/arm/boot/zImage-dtb is ready
now you need to get a boot.img from any nexus 5 rom and place it in boot_img (create this folder where you earlier downloaded the toolchain and the kernel)
Code:
$ cd .. # if you was in msm directory
$ git clone https://github.com/pbatard/bootimg-tools.git
$ cd bootimg-tools/
$ make
$ cd cpio/
$ gcc mkbootfs.c -o mkbootfs -I../include
$ cd ../..
$ mkdir andorid_boot_tools_bin
$ cd andorid_boot_tools_bin/
$ cp ../bootimg-tools/mkbootimg/mkbootimg .
$ cp ../bootimg-tools/mkbootimg/unmkbootimg .
$ cp ../bootimg-tools/cpio/mkbootfs .
$ cd ..
time to create your own boot
Code:
$ unmkbootimg -i boot_img/boot.img
$ cp msm/arch/arm/boot/zImage-dtb kernel
$ mkbootimg --base 0 --pagesize 2048 --kernel_offset 0x00008000 --ramdisk_offset 0x02900000 --second_offset 0x00f00000 --tags_offset 0x02700000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1' --kernel kernel --ramdisk ramdisk.cpio.gz -o boot.img
install the boot.img to your phone (this wont flash the kernel, it will temporarily boot with this kernel, after you restart you will go back to what ever kernel you had before
Code:
$ adb reboot bootloader
$ sudo fastboot boot boot.img
------------------------------------------------------------------------------------------------
PART B
(setting up your phone)
------------------------------------------------------------------------------------------------
For TP-LINK_TL-WN722N
Code:
download the firmware files [URL="http://wireless.kernel.org/download/htc_fw/1.3/"]here[/URL]
1. htc_7010.fw
2. htc_9271.fw
For TP-LINK TL-WN725N V1 & V2
Code:
Download the firmware files [URL="https://drive.google.com/folderview?id=0Bxm4XqSOJU3YWlVaZ1NFRDF4RTA&usp=sharing"]here[/URL]
For Linksys WUSB600N V2
Code:
Download the firmware files [URL="https://drive.google.com/folderview?id=0Bxm4XqSOJU3YMGZTcjJ2ei10V1k&usp=sharing"]here[/URL]
1. rt2870.bin
For ALFA Network AWUS036H
Code:
hopefully nothing to do here,... if it doesnt work let me know
copy them to your phone
use a file manager with root to copy firmware files to /system/etc/firmware/
install Linux deploy on your phone
fire up linux deploy and go to properties-->Distribution and select kali linux
installation path set to /sdcard/linux.img
hit the install button
after installation click start button
start your favorite ssh program and happy aircrack-ng
(SH credentials are “android” for the username (configured via Linux Deploy) and “changeme” as the password.)
hello ... how did you get those two lines of commands on the keyboard ?!
which command are you talking about?
you should use the commands one by one
chiragkrishna said:
which command are you talking about?
you should use the commands one by one
Click to expand...
Click to collapse
If I'm not mistaken, I believe he means your screen shot. In terminal with Ctrl, alt, etc above the keyboard.
you need to install aircrack-ng in kali
i am not going to guide you on how to use kali!! you have to figure it on your own!!
code used in that screenshot,
Code:
$ sudo airmon-ng
$ sudo airmon-ng start wlan1
chiragkrishna said:
you need to install aircrack-ng in kali
i am not going to guide you on how to use kali!! you have to figure it on your own!!
code used in that screenshot,
Code:
$ sudo airmon-ng
$ sudo airmon-ng start wlan1
Click to expand...
Click to collapse
Love this reply.Honestly if u don't know how then you should not be trying it
Sent from my Nexus 5 using Tapatalk
What does this do, get you better WiFi connection in terms of speed/stability?
Search aircrack-ng on Google, you're very far !
Sent from my Nexus 5 using XDA Free mobile app
GT-af said:
Search aircrack-ng on Google, you're very far !
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well..... It could, just not the way he was probably expecting
Pretty cool tut I must say, I'm wondering, could you make it support aswell the Wusb600n v2 ? that's what I'm currently having as usb wifi
added support for WUSB600N V2
this guide will help you, do what a $1,295.00 PWN PHONE can!!
chiragkrishna said:
added support for WUSB600N V2
this guide will help you, do what a $1,295.00 PWN PHONE can!!
Click to expand...
Click to collapse
Oh woow cool, will test this out when I'm home
Hopefully packet injections etc will work ^.^
parker09 said:
What does this do, get you better WiFi connection in terms of speed/stability?
Click to expand...
Click to collapse
Yes, it turns your Wi-Fi into a 1Gb/s power house regardless of the connection you're on.
To test do this:
1 - hook up your dial-up cable and modem/router/whatever
2 - connect your N5 to that network and try to open www.nike.com
3 - if it takes 10m to load, then you're on the correct network, 56k yay!
4 - flash this
5 - connect to your 56k network
6 - ???
7 - www.nike.com loads in 2s
8 - profit
-----
Nice guide OP
Testing it out right now but there seems togo something weird ?
SIOCSIFFLAGS: No such file or directory
I gave the .bin file privs 644 and when trying airodump it says
Gave wlan1 and mon0 for fun a try... but not working
Kill the processes
867
1263
867
These are the problems..
@chiragkrishna
You know man if it works with tp-link tl wn723n ou wn725n?
...
chiragkrishna said:
Kill the processes
867
1263
867
These are the problems..
Click to expand...
Click to collapse
Killed em and the message dissapeared but it's still not working ?
http://puu.sh/b0BBg/18d9bc170b.png <- click the image
Could the alfa awus036h be compatible in the future?
Orderd now the same as OP (TP-LINK TL-WN722N) and we'll see how it goes
I got my OP3 today and my laptop, running ElementaryOS (ubuntu based) didn't recognize the OP3 as MTP,
Here is a guide how to fix this, I based this guide on this guide for the OP2.
steps:
Do NOT connect your OP3 to your pc
run the command "lsusb" from your terminal
Connect your OP3 to your pc with original cable
run the command "lsusb" again
You will see a new device, my OP3 is called " Bus 001 Device 012: ID 05c6:900e Qualcomm, Inc. "
You see that it has an ID, in my case "05c6:900e".
the first value is the vendor-id, the second the product-id, you need those so write them down!
so in my case it's :
vendor id: 05c6
product id: 900e
Install the MTP drivers: "sudo apt-get install libmtp-dev mtpfs"
edit the following file with the command: "sudo gedit /lib/udev/rules.d/69-libmtp.rules"
if you don't have gedit installed use the command: "sudo nano /lib/udev/rules.d/69-libmtp.rules"
Add the following line to the file:
Code:
ATTR{idVendor}=="[COLOR="Blue"]vendor-id[/COLOR]", ATTR{idProduct}=="[COLOR="blue"]product-id[/COLOR]", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1", TAG+="uaccess"
make sure you change the blue values to your own values found in the step above.
safe the file
restart the service: "sudo service udev restart"
If you did it correct you will see a popup on your OP3, select "File Transfers (MTP)", select that and now you can transfer files between your OP3 and linux
I don't know if the vendor-id and/or product-id are always the same, if some people can confirm that then I will edit the post.
Hey, I got the same vendor id and product id as you did.
However, even after following the procedure step-by-step, I am unable to transfer files between my OP3 and my laptop running Ubuntu 12.04 LTS.
The OnePlus drivers folder gets loaded as a CD(though I'm connecting the phone using USB) when I change the "Use USB for" setting to "File Transfer(MTP)," and the file named "adb_config_Linux_OSX.sh" doesn't do anything when run in terminal either.
Could you help me out with this?
I run Ubuntu 16.04 and needed to install any drivers. simply connect op and I was able to access it.
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
krankyvampire25 said:
Hey, I got the same vendor id and product id as you did.
However, even after following the procedure step-by-step, I am unable to transfer files between my OP3 and my laptop running Ubuntu 12.04 LTS.
The OnePlus drivers folder gets loaded as a CD(though I'm connecting the phone using USB) when I change the "Use USB for" setting to "File Transfer(MTP)," and the file named "adb_config_Linux_OSX.sh" doesn't do anything when run in terminal either.
Could you help me out with this?
Click to expand...
Click to collapse
update: In "设置" -"其他设置" - "内部设备和USB" - "USB计算机连接", select -- "File Transfers (MTP)", everything is ok.
14.04 can't transfer file. a folder cant write anything(not cd image folder).
hi....... i have a other problem with the same OS (Ubuntu 16.04)
MTP works
fastboot works
ADB DON'T !!!
do you know why ?????
ADB and fastboot are working at the same device with Win 10
OK, thanks, forget it, i found a file named "adb_config_Linux_OSX.sh" on the phone and run it...... now it works
ty, it worked after two reboots and a system update. btw, i have the OP3 soft gold with ID 2a70:f003
cheers!
washichi said:
I got my OP3 today and my laptop, running ElementaryOS (ubuntu based) didn't recognize the OP3 as MTP,
Here is a guide how to fix this, I based this guide on this guide for the OP2.
steps:
Do NOT connect your OP3 to your pc
run the command "lsusb" from your terminal
Connect your OP3 to your pc with original cable
run the command "lsusb" again
You will see a new device, my OP3 is called " Bus 001 Device 012: ID 05c6:900e Qualcomm, Inc. "
You see that it has an ID, in my case "05c6:900e".
the first value is the vendor-id, the second the product-id, you need those so write them down!
so in my case it's :
vendor id: 05c6
product id: 900e
Install the MTP drivers: "sudo apt-get install libmtp-dev mtpfs"
edit the following file with the command: "sudo gedit /lib/udev/rules.d/69-libmtp.rules"
if you don't have gedit installed use the command: "sudo nano /lib/udev/rules.d/69-libmtp.rules"
Add the following line to the file:
Code:
ATTR{idVendor}=="[COLOR="Blue"]vendor-id[/COLOR]", ATTR{idProduct}=="[COLOR="blue"]product-id[/COLOR]", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1", TAG+="uaccess"
make sure you change the blue values to your own values found in the step above.
safe the file
restart the service: "sudo service udev restart"
If you did it correct you will see a popup on your OP3, select "File Transfers (MTP)", select that and now you can transfer files between your OP3 and linux
I don't know if the vendor-id and/or product-id are always the same, if some people can confirm that then I will edit the post.
Click to expand...
Click to collapse
I just now happened upon this forum because my OP3 wasn't connecting for file transfers over USB. This worked like a charm for me; the vendor and product IDs were different (as I'm sure others have commented already), thank you for putting this out there, I definitely hit that 'thanks' button!!!!!!!
It's also possible to use this script (Vendor & Product id can differ).
Code:
#!/bin/sh
# adb configuration script
PATH=$PATH:/bin:/sbin:/usr/sbin
ANDROID_HOME=~/.android
ANDROID_CONFIG=~/.android/adb_usb.ini
CUST_VID="0x2a70"
if [ -e $ANDROID_HOME ] ; then
echo "android home is exist!"
else
echo "creat android home!"
mkdir $ANDROID_HOME
fi
grep $CUST_VID $ANDROID_CONFIG 2>/dev/null
if [ $? -eq 0 ] ; then
echo VID $CUST_VID is already configured..
echo "adb should be OK!"
exit 0
else
echo config adb ...
echo $CUST_VID >> $ANDROID_CONFIG
fi
adb kill-server
if [ $? -eq 0 ] ; then
echo "OK! You can use adb now!"
exit 0
else
echo "try sudo exec adb.."
sudo adb kill-server
if [ $? -eq 0 ] ; then
echo "OK! You can use adb now!"
exit 0
else
echo "Please do command \"adb kill-server\""
fi
fi
exit 0
Useful link: https://wiki.archlinux.org/index.php/android#Android_Debug_Bridge_.28ADB.29
Thanks a lot washichi It worked liked a charm on my OnePlus3T. Thanks a ton