Related
Connect my G1 with my laptop(Ubuntu 8.10 x64)
When I run the adb devices, it only said: List of devices attached
No devices line; It lists one line when I start the emulator program.
And not like the SDK for windows, there is not some folder related to drivers.
Does it support for linux x64? plz help.~
have you activated the debugger in your g1 ?
oh I remember when I was in ubuntu now
you gotta launch adb daemon as root
try this :
adb kill-server && sudo adb devices
and let me know if it worked
dixxa said:
have you activated the debugger in your g1 ?
Click to expand...
Click to collapse
Absolutely, it works fine in Vista x64 with SDK 1.1 r1
I had to do two things to get this to work (although this was on x86) -
1) Build the kernel with the Android drivers enabled. This might not be necessary; I have no idea if they are turned on in the kernels you get from the Ubuntu repository as mine has been custom built for a while, but I'm guessing that they aren't enabled by default because they are in the "staging" area as of 2.6.29.1. So these were in Device Drivers/Staging Drivers/Android.
2) Add a "50-android.rules" file to /etc/udev/rules.d that has this line:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",SYMLINK+="android_adb",MODE="0666"
The idVendor is different if you have an ADP phone, I believe; this was the value worked for mine (non-dev). You can do an 'lsusb' after it's been plugged in and see what shows up. Also, try grepping /var/log/messages for "udev" after you plug it into a USB port and see if there are meaningful messages.
- Chris
Hi all,
I got similar issue here, the main difference is that i got ubuntu 9.04.
running adb daemons as root permit to see devices when it's started normally, but not when in fastboot mode.
I tried all suggestions above (and others!) without success :/
Thanks for any help
noz.geek said:
Hi all,
I got similar issue here, the main difference is that i got ubuntu 9.04.
running adb daemons as root permit to see devices when it's started normally, but not when in fastboot mode.
I tried all suggestions above (and others!) without success :/
Thanks for any help
Click to expand...
Click to collapse
copy the 50-android.rules file you created into a file called 51-android.rules. The problem is related to the order in which things are launched and copying this file to the new name will solve your problem.
I should also note that you will have to restart udev Or reboot or logout/in
to restart udev, In terminal type:
Code:
sudo /etc/init.d/udev restart
sudo is necessary~ thx
Hi all,
After creating 50-android.rules file in /etc/udev/rules.d, I can mount my sdcard on my gPhone to Ubuntu8.04 but I still see no thing when i type command : adb devices. I also did some commands which you gave here. Can anybody help me?
Thanks so much,
NPAK
npak243 said:
Hi all,
After creating 50-android.rules file in /etc/udev/rules.d, I can mount my sdcard on my gPhone to Ubuntu8.04 but I still see no thing when i type command : adb devices. I also did some commands which you gave here. Can anybody help me?
Thanks so much,
NPAK
Click to expand...
Click to collapse
Code:
$ sudo mv /etc/udev/rules.d/50-android.rules /etc/udev/rules.d/51-android.rules/code]
that should fix it ;)
Thanks,
It can work now!
I have the same problem here. adb used to be able to see my phone when I was using Ubuntu 8.10. After I upgraded to 9.04, it never worked. I tried change the udev rule file from 50-** to 51-** or as haykuro suggested to 51-**/code. I also changed the permission to 777. And I did kill and restart adb-server several times under root, but I still get nothing~~~
Can anyone help?
Ok, I have fedora 11 installed on most of my computers, since i love this distro to death. My big thing was trying to get adb to work. This is my guide to get it to work, for now.
First things first. Navigate to /etc/udev/rules.d as root. Create a rules file called 50-android.rules (touch 50-android.rules). NOTE: You are better off looking at the contents and picking a rules number set other than what is listed. Sometimes udev is picky. For the newbies, so if any rules start with '50', then change the number by one or two, like 51 or 52. Paste this into the file:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="0bb4",SYMLINK+="android_adb",MODE="0666"
Make sure you use ATTRS, not ATTR or SYSFS, since this is a newer updated udev system.
After that, run udevadm control --reload-rules to reload your rules files. Now just run ./adb devices as root to make sure it recognized your HTC dream. I am working on this fix right now so you don't need to be root, keep patient. Now you can adb shell into your device either as root OR normal user, just as long as you start the server as root. This is a permissions problem, and hopefully I can fix this and/or find a fix soon.
I wrote this because i searched high and low through google, and only found a few good parts as far as a fix. Hopefully this helps a few people out there.
Just wondering if this has helped anyone. If not, delete this thread or do whatever with it....
I have adb on my eeepc 900 with f11 I believe this method works too as well. although it says it has been tested with ubuntu, it works pretty well with f11.
http://www.talkandroid.com/android-sdk-install-guide/
Installing The Android SDK
First you will need to download the Android SDK pack .zip archive, once downloaded find a suitable installation location on your machine and extract the zipped files.
Please note: This installation location will be referred to as $SDK_ROOT from now on through this tutorial
Alternatively you can add /tools to your root path which will prevent the need to specify the full path to the tools directory along with enabling you to run Android Debug Bridge (adb) along with other command line tools.
To add /tools:
Linux
1. Edit the ~/.bash_profile or ~/.bashrc files looking for a line that sets the PATH variable.
2. Add the full path location to your $SDK_ROOT/tools location for the PATH variable.
3. If no PATH line exists you can add the line by typing the following:
4. export PATH=${PATH}:<path to your $SDK_ROOT/tools>
Click to expand...
Click to collapse
It helped me, since the creation of the file my OpenSuSE 11.0 recognizes the phone perfectly
Thanks a lot for your hint.
thanks it helped me. ill be looking forward to getting it to work without root
just use sudo instead
Just a heads up for user's using Ubuntu 9.10, this isn't needed. I connected my G1 to it and ran ADB with no adjustments to udev or anything else.
Pretty much it works out of the box.
Here is my version
download the .tgz file from googlecode
http://developer.android.com/sdk/index.html
sudo tar -xzvf android-sdk_r3-linux.tgz
Click to expand...
Click to collapse
Code:
sudo gedit ~/.bash_profile
heres my bash_profile
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH=$PATH:/android-sdk-linux/tools
Click to expand...
Click to collapse
logout
login
connect android g1 device via usb to pc
open a terminal
Code:
adb devices
if you cant get a device try it with superuser.
Don't you think that this is all just a little bit excessive?
To make it work in F11, just do this;
Download SDK, extract.
To use, type:
/path/to/sdk/tools/adb
Another option is to edit the /etc/profile and add
PATH=$PATH:/<Path to android-sdk>/tools
This option will allow any user to use the adb tools when logged in or if you
su -
into another user
I wrote a short guide as well for Windows and Ubuntu. Might help others.
Unfortunately, as anyone with a passing acquaintence with ADB knows, the scrolling issue can be a killer. I swear the other day I pressed "up" twice and it composed "rm /sdcard/rootfs.img /sdcard/system.ext2" and executed it. We run Android on our SD's btw.. Was not cool. Instead, I use ADB via telnet and it works beautifully. Here's how:
Code:
adb shell telnetd &
adb forward tcp:9999 tcp:23
Now type this: "telnet localhost 9999"
Enter "root" and hit enter
Finally update PATH: "export PATH=/usr/bin:/usr/sbin:/bin:/sbin:/system/sbin:/system/bin:/system/xbin:/system/xbin/bb:/data/local/bin"
Okay, so 4 lines to enter and you have a "regular, sane" shell connection to the phone and you can actually scroll through history and text without it jumbling the text and executing random code. Enjoy.
lbcoder said:
Don't you think that this is all just a little bit excessive?
To make it work in F11, just do this;
Download SDK, extract.
To use, type:
/path/to/sdk/tools/adb
Click to expand...
Click to collapse
that works too as well but i would rather open up a terminal and type
sudo adb devices
sensimila said:
that works too as well but i would rather open up a terminal and type
sudo adb devices
Click to expand...
Click to collapse
WHY would you want to make it *MORE COMPLICATED*??
There is NO NEED for root.
/path/to/adb ...
THATS ALL.
This is kind of funny... i wrote this because i had trouble with it, so i am just sharing my fix...
In case this is interesting to someone:
The fix mentioned in the first post has to be applied to open SuSE x86 and x64 edition to make the G1 work. The external device works without it, but not the adb device.
Thanks again!
Just wanted to come and post that this does work with OpenSUSE 11.2 x86. Did this hoping to get adb to work with my LG Ally and it does. Thanks!
(Still) works for me on 64bit SUSE 11.4.
Before adding this file, I could not access my device with adb, received permissions errors.
Added this file, and I can shell into my device.
Permissions on adb itself was not the problem, it was access to the device when udev found it.
[edit]Actually used the lines from http://developer.android.com/guide/developing/device.html[/edit]
This is for CyanogenMod and its derivates. Stock ROMs should be fine.
If you are inrested in editing your MAC address, there's a guide linked below. I don't know if stock ROMs will automcatically correct the MAC. In this case I think you have to edit /efs/imei/.nvmac.info (read more something about /efs before playing with it!)
Click to expand...
Click to collapse
The easiest way to do the calibration is:
Turn wifi ON and run
Code:
tiwlan_plts -n
This is the script called from a oneshot init service in my init.latona.rc if someone is interested. It will calibrate and correct the MAC automatically, even after a data wipe:
Code:
#!/system/bin/sh
if [ ! -f /data/misc/wifi/nvs_map.bin ]; then
insmod /system/lib/modules/tiwlan_drv.ko
/system/bin/tiwlan_loader -i /system/etc/wifi/tiwlan.ini -f /system/etc/wifi/firmware.bin
/system/bin/tiwlan_plts -n
rmmod tiwlan_drv
fi
____________________________________
Older method
Click to expand...
Click to collapse
UPDATE: I found an easy way to get the real MAC.
Download the apk attached or run the following commands:
Code:
su
mount -o remount,rw /system
ln -s /system/lib/modules/tiwlan_drv.ko /system/etc/wifi/tiwlan_drv.ko
#Make sure wifi is off
./mfgloader -l #Take the binary from a stock ROM
./mfgloader -u
rm /system/etc/wifi/tiwlan_drv.ko
mount -o remount,ro /system
After that your MAC address shoud begin with D0:C1:B1 and not 08:00:28.
To see your current MAC: System Settings > About phone > Status (turn wifi on)
Click to expand...
Click to collapse
____________________________________
This is the first post with some more informations about the calibration
Click to expand...
Click to collapse
While I was reading some logs, I noticed these lines
Code:
TIWLAN: 1089.979242: Starting to process NVS...
TIWLAN: 1089.983698: No Nvs, Setting default MAC address
TIWLAN: 1089.989007: pHwInit->uEEPROMCurLen: 1c
TIWLAN: 1089.993462: ERROR: If you are not calibating the device, you will soon get errors !!!
...
TIWLAN: 1094.726827: Station ID : 08-00-28-12-03-58
...
You can see that the device is not calibrated and that the default MAC address is assigned.
Each device should have a unique MAC address, two devices with the same MAC address in the same network will give problems.
________
UPDATE
I made two flashable files:
wlan_calibration.zip will only do the calibration
wlan_calibration_rand.zip will do the calibration and will randomize the last three octets of the address
Click to expand...
Click to collapse
If you still want to do it on your own, here the guide:
_______________
WLAN Calibration
Here the steps you need to follow (taken from: WLAN Calibration):
1) Turn wifi off
2) From ADB/terminal emulator run the following commands [1]:
Code:
$ su
# cd /data/misc/wifi
# insmod /system/lib/modules/tiwlan_drv.ko
# start wlan_loader
# ifconfig tiwlan0 up
# tiwlan_cu -b
/ w p 1 l 2 f 2
/ t b v 21
/ t b t 1 0 0 0 0 0 0 0
/ q
# rmmod tiwlan_drv
This will create this file: /data/misc/wifi/nvs_map.bin. If it's not there, you did something wrong.
After that you should not get the error while turning wifi ON.
________
MAC address fix
Even after the calibration, you'll still have the default MAC address (Station ID : 08-00-28-12-03-58). But no problem, you can 'easly' change it: Editing the MAC Address.
You need to get the newly created /data/misc/wifi/nvs_map.bin and edit it with an hex editor as described in the guide linked above.
I still don't know if the calibration will improve anything, but it surely won't hurt:
For optimal Wi-Fi performance it is mandatory to calibrate the Wi-Fi hardware
Click to expand...
Click to collapse
NOTE: nvs_map.bin is in /data, so if you do a factory reset you have to do this again.
___
[1]
ADB: System settings > Developers options (ON) > Root access > Apps and ADB
Wow...good solution buddy. I think u shouldpost this in development thread. People dont look much in general thread.
this should be added to the cm9/10 instalation .zip file
I did flash the zip file, ran the other commands thru terminal and see the file /data/misc/wifi/nvs_map.bin.
I don't understand the next step to be done.
I cannot open the bin file using hexeditor, I gave it root access.
And, in case i open it what mac address should i use? Is some address hard coded to each phone?
Hetalk said:
I did flash the zip file, ran the other commands thru terminal and see the file /data/misc/wifi/nvs_map.bin.
I don't understand the next step to be done.
I cannot open the bin file using hexeditor, I gave it root access.
And, in case i open it what mac address should i use? Is some address hard coded to each phone?
Click to expand...
Click to collapse
I don't know how MAC are assigned, I simply randomized the last part of the address (I kept the first part: 80:00:28).
Anyway I just uploaded a new zip file to make things even simpler. It will automatically randomize the last four three groups. If you want to use it, you need to delete /data/misc/wifi/nvs_map.bin first. EDIT: I changed the script, now you can do the calibration without removing the file.
Anyway I don't know what's wrong with your editor, I did it from my computer.
I tried using hex editor from play store.
I'll try the new zip tomorrow..
As I wrote in the OP, today I found the way to get the original MAC.
I don't know what is needed to make the commands work while in recovery (services needed etc...), so I made a dummy app (I simply adapted the code of an app I made few days ago to do a similar thing).
No fancy icon (it's the default one), no checks, ugly etc... It simply does the job (my Java knowledge is almost zero)
EDIT:
I almost forgot to say that the real MAC is in /efs/imei/.nvmac.info. It was the first place where I looked, but it's an hidden file an I didn't see at first.
bam....
Dear @loSconosciuto
I following this guide to solve the problem that actually I have in my phone with CM 11. In the Status menu, "non available" appears in my device WIFI mac. I following the guide step by step and I couldn't change it.
Could you help me?
carniman78 said:
Dear @loSconosciuto
I following this guide to solve the problem that actually I have in my phone with CM 11. In the Status menu, "non available" appears in my device WIFI mac. I following the guide step by step and I couldn't change it.
Could you help me?
Click to expand...
Click to collapse
This guide is for the kernel 2.6.35 which uses a completely different driver, it's quite an old thread. The calibration is done in a different way and I don't think that's the problem.
I'm not using CM11, so it's quite hard for me to know exactly what's wrong.
loSconosciuto said:
This guide is for the kernel 2.6.35 which uses a completely different driver, it's quite an old thread. The calibration is done in a different way and I don't think that's the problem.
I'm not using CM11, so it's quite hard for me to know exactly what's wrong.
Click to expand...
Click to collapse
Ok, sir. Thank you for your help.
Hi there
trying to fix Samsung s4 active i9295 wifi problem. at least got the MAC address showing (was 02:lots of zeroes) still unable to start wifi. is there anything else I should search for? tiwlan_drv.ko was not there so I downloaded it sepparately. do I need some more modules to be added? using stock 4 file engineering FW Android 5.0.1
Hi xda-mates. In this post I'm gonna show you, How to get wifi monitor mode on your device without external wifi adapter. If you don't know what is "wifi mode" goto wikipedia. The package consist from drivers, some wifi tools and aircrack.
Monitor Mode getting steps:
1. You have to root your device.
2. Flash CM 9.1.0.
3. Check out, your using originally cwm kernel included in the firmware you flashed.
4. Download my package(the password is my nickname).
5. Extract it to your sd.
6. Open up the terminal.
7. Type
Code:
su
cd pathToYourSd
sh install.sh
it will simply install all stuff to your system.
8. Type 'wmon on' in the terminal to activate monitor mode (type 'wmon off' to activate managed mode).
That's all. You have installed all that you needed, activated monitor mode and now you can use aircrack.
Troubleshooting:
Problem:
Code:
cannot find wireless tools, exiting!
Solution:
a) You must execute wifi tools (aircrack also) from root directory!
Code:
cd /
b) Check out of iwconfig, iwmulticall, iwpriv existance in /data/local/bin/.
Problem:
Code:
insmod: can't insert 'dhd.ko': invalid module format
error: SIOCGIFFLAGS (No such device)
Solution:
a) Make sure you are in supported rom and kernel.
b) Check out the file existance in /data/wmon/ (3 file).
Credits:
Aspartame21
Omri Ildis
Ruby Feinstein
Yuval Ofir
MemoryController
Could this possibly work on the Sprint Galaxy S2?
Sent from my SPH-D710 using xda premium
Mattix724 said:
Could this possibly work on the Sprint Galaxy S2?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
May be but I don't know exactly. Try to istall it. I'll help you.
GREAT!
Thanks man! i was waiting for someone to go into this much detail, but does the wmon siyah mean that i can dualboot CM 9 and w/e rom ( in my case alliance) and get this to work? my problem with this before is that nothing would happen after my wifi is disabled and module is "loaded", also what do you mean run aircrack from the root dir? like root of the sd?
P.S. Testing now on the Galaxy S2 LTE version ( Rogers)
tutchthesky7 said:
Thanks man! i was waiting for someone to go into this much detail, but does the wmon siyah mean that i can dualboot CM 9 and w/e rom ( in my case alliance) and get this to work? my problem with this before is that nothing would happen after my wifi is disabled and module is "loaded", also what do you mean run aircrack from the root dir? like root of the sd?
P.S. Testing now on the Galaxy S2 LTE version ( Rogers)
Click to expand...
Click to collapse
I get suck after airmon-ng wlan0
says cannot find wireless tools, exiting!
Some help please and thanks?
tutchthesky7 said:
I get suck after airmon-ng wlan0
says cannot find wireless tools, exiting!
Some help please and thanks?
Click to expand...
Click to collapse
Use iwconfig wlan0 instead of airmon-ng wlan0. And make sure that you are in the root directory.
Code:
su
cd /
wmon on
iwconfig wlan0
iwconfig wlan0
aspartame21 said:
Use iwconfig wlan0 instead of airmon-ng wlan0. And make sure that you are in the root directory.
Code:
su
cd /
wmon on
iwconfig wlan0
Click to expand...
Click to collapse
OK thank you!, i'll give that a shot and post back!
Nada
aspartame21 said:
Use iwconfig wlan0 instead of airmon-ng wlan0. And make sure that you are in the root directory.
Code:
su
cd /
wmon on
iwconfig wlan0
Click to expand...
Click to collapse
# wmon on
Original module loaded. disabling wifi
LOADING MODULE
insmod: cant insrt dhd.ko : file exists error : SI0CIFFLAGS (no such device)
then i tried iwconfig wlan0
wlan0 No such device
so i checked iwconfig to see whats up
and my Wlan0 isn't there.. hmmm
Edit: I typed in wmon on and it responded with LOADING MODULE, then i did iwconfig wlan0 and it showed it in manage mode, what next?
tutchthesky7 said:
# wmon on
Original module loaded. disabling wifi
LOADING MODULE
insmod: cant insrt dhd.ko : file exists error : SI0CIFFLAGS (no such device)
then i tried iwconfig wlan0
wlan0 No such device
so i checked iwconfig to see whats up
and my Wlan0 isn't there.. hmmm
Edit: I typed in wmon on and it responded with LOADING MODULE, then i did iwconfig wlan0 and it showed it in manage mode, what next?
Click to expand...
Click to collapse
Don't pay attention to "managed mode" lettering, you are in monitor mode. To test monitor mode working type 'airodump-ng wlan0' and you will see that everything works perfect.
errrm.. not QUIIITEE, it says cannot find wireless tools, exiting. then it deletes all the files i extracted
IT IS WORK! one little question
THIS WORK, first, and ofc, THX man
I had a sgs2(official), rooted in gingerbread, and then i flashed ICS with CM 9.1, then i folllow yours steps, y putted my sgs2 in mode monitor and i checked.
Just one question, i searched in google, and ask in IRC, but i don't find the answer:
¿Do can i use the same steps to get WPA as Ubuntu or Backtrack? else... ¿do you know some link where a tutorial get wpa via sgs2?
I want complete the last step, thx for your time, and sry for my english
Clitoris Errante said:
THIS WORK, first, and ofc, THX man
I had a sgs2(official), rooted in gingerbread, and then i flashed ICS with CM 9.1, then i folllow yours steps, y putted my sgs2 in mode monitor and i checked.
Just one question, i searched in google, and ask in IRC, but i don't find the answer:
¿Do can i use the same steps to get WPA as Ubuntu or Backtrack? else... ¿do you know some link where a tutorial get wpa via sgs2?
I want complete the last step, thx for your time, and sry for my english
Click to expand...
Click to collapse
You can use all stuff like in ubuntu/bt.
Mode inyecction?
Thx for answer me, i did decide install another time backtrack in my sgs2(i removed ), but i want crack wpa without brute force or diccionaries, because it is imposible.
¿Is there some way to crack a wpa without brute force or diccionaries? ¿Do i could implement rainbow tables in sgs2, or is there some way to hashing with aircrack?
Thx for your time,
Clitoris Errante said:
Thx for answer me, i did decide install another time backtrack in my sgs2(i removed ), but i want crack wpa without brute force or diccionaries, because it is imposible.
¿Is there some way to crack a wpa without brute force or diccionaries? ¿Do i could implement rainbow tables in sgs2, or is there some way to hashing with aircrack?
Thx for your time,
Click to expand...
Click to collapse
Aircrack-ng is included to the package you installed. Just type aircrack-ng after switching wifi monitor mode
from a day to other, i can't use this
i didn't use somedays, and now i can't use, it is appears as delete, or simplely, not work. I did install applications in my sgs2.
But now i can't run it. I tried reinstall, but always put in the output:
"wmon on" not found
"wmod on" not found
"wmod monitor" not found
i did that in /, and i executed the install.sh in sdcard as you said in your post.
In internet i not found nothing, and i know programming bash a little, i tried solved gave wmon bit executable but is useless, i follow all steps rights as you said. The only one thing interesant when i execute install that is the output:
Installing Driver...
OK
Installing Utils...
OK
Creating Symlink...
link failed FIle exists
link failed File exists
//I think here is the fail of my steps, i think that make reference to /data/wmon, but i am not sure, i checked that files, but i can't solved
OK
Fixing Permissions...
OK
Temporary FIles Cleaning...
OK
Installation COmpleted! To start WiFi monitor mode just type : "wmod monitor"
I am sry if i am heavy, thx for your time.
This is pretty cool, I managed to make some progress, however got error at authorization stage at line:
aireplay-ng -1 0 -a MAC wlan0
Waiting for beacon frame (BSSID: .......) on channel -1
Couldn't determine current channel for wlan0, you should either force the operation with --ignore-negative-one or apply kernel patch
same error with injection
I'm pretty new to linux stuff, is there any way to bypass this?
Another thing is that I can't use wi-fi after using monitor mode, even if i shut it down (wmon off) until phone restart, is that alright?
Thanks in advance, and keep doing the great job!
Clitoris Errante said:
i didn't use somedays, and now i can't use, it is appears as delete, or simplely, not work. I did install applications in my sgs2.
But now i can't run it. I tried reinstall, but always put in the output:
"wmon on" not found
"wmod on" not found
"wmod monitor" not found
i did that in /, and i executed the install.sh in sdcard as you said in your post.
In internet i not found nothing, and i know programming bash a little, i tried solved gave wmon bit executable but is useless, i follow all steps rights as you said. The only one thing interesant when i execute install that is the output:
Installing Driver...
OK
Installing Utils...
OK
Creating Symlink...
link failed FIle exists
link failed File exists
//I think here is the fail of my steps, i think that make reference to /data/wmon, but i am not sure, i checked that files, but i can't solved
OK
Fixing Permissions...
OK
Temporary FIles Cleaning...
OK
Installation COmpleted! To start WiFi monitor mode just type : "wmod monitor"
I am sry if i am heavy, thx for your time.
Click to expand...
Click to collapse
I've to correct my scripts, but don't wait for it. Just type "export PATH=/data/local/bin:$PATH". You can also add this to your terminal emulator as launch commands or create a script in autostart folder:
Code:
su
cd /system/etc/init.d/
touch 17env
echo "#!/system/bin/sh\nexport PATH=/data/local/bin:$PATH\nexit 0" > 21env
makslll said:
This is pretty cool, I managed to make some progress, however got error at authorization stage at line:
aireplay-ng -1 0 -a MAC wlan0
Waiting for beacon frame (BSSID: .......) on channel -1
Couldn't determine current channel for wlan0, you should either force the operation with --ignore-negative-one or apply kernel patch
same error with injection
I'm pretty new to linux stuff, is there any way to bypass this?
Another thing is that I can't use wi-fi after using monitor mode, even if i shut it down (wmon off) until phone restart, is that alright?
Thanks in advance, and keep doing the great job!
Click to expand...
Click to collapse
I use "aireplay-ng -2 -b VICTIM -h FAKEDMAC wlan0"
aspartame21 said:
I've to correct my scripts, but don't wait for it. Just type "export PATH=/data/local/bin:$PATH". You can also add this to your terminal emulator as launch commands or create a script in autostart folder:
Code:
su
cd /system/etc/init.d/
touch 17env
echo "#!/system/bin/sh\nexport PATH=/data/local/bin:$PATH\nexit 0" > 21env
Click to expand...
Click to collapse
Where is this Terminal autostart folder? Also, I tried executing the first command and it gave me nothing but a "> " line. What should I do?
Hi guy,
first of all, thanks for your great job.
I've seen as you have uploaded a wmon_siyah4.5.1 version... does it work with that siyah version?
I have that kernel (and that version), and I get the error:
Code:
insmod: can't insert 'dhd.ko': invalid module format
error: SIOCGIFFLAGS (No such device)
just after run 'wmon on'.
Can you help me, please?
thanks
This post is adapted from a post in the android hacking general thread by user jackattack79.
I just changed the udev rules to work with our tf700's. Perhaps it can be helpful here. Thanks again to jackattack79 for the original post.
Anyone wanting to use adb with your ASUS Infinity through Ubuntu/Linux... follow these steps (these steps will make accessing adb much easier and allow abd to recognize your phone)[Please note - modifying the .bashrc in step 1 is not required; it will just make using Android SDK much easier for beginners]:
1. Modifying the PATH Environment Variable will help out immensely when it comes down to making use of SDK tools like ADB. Doing this will also allow you to execute certain protocols like ADB from ANY location. So if you're operating from the Desktop, you don't have to redirect to the SDK's platform-tools folder to make use of ADB if you need to make use of it.
To modify the PATH variable of your system, you need to edit your .bashrc file. To do so, in a terminal, execute the following command:
$ nano ~/.bashrc
You will now have the Nano text editor enabled on the terminal. Now, at the very top of the file(yes, that means go to the top and hit enter to create some space at the top. Then just copy and paste - a caveman really could do it!), enter the following:
#AndroidDev PATH
export PATH=${PATH}:~/android-sdk-linux/tools
export PATH=${PATH}:~/android-sdk-linux/platform-tools
Once you're finished, press CTRL + X, Y, and then hit Enter to save your changes and exit the Nano text editor.
2. Now that we have our PATH variable set up, we need to make sure our hardware will be detected once we initialize ADB. However, Ubuntu won't allow ADB access to the Android phone via USB unless the appropriate udev rule is set. This is Bug #316215. In order to get around this rule, you need to create a rule file as root.
In a terminal, execute the following command that will create the rule file. This will utilize the graphical sudo command, so that we can still have control over the file if we're not a root user.
Now, you create a file:
sudo nano /etc/udev/rules.d/51-android.rules
Copy and paste the following udev rule in the text editor that opened up which contains the new rule file we created:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c91", MODE="0666" #Normal tf700
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4daf", MODE="0666" #Fastboot tf700
Once you've copied and pasted the udev rule in the text editor which contains your newly created rule file, save your changes and quit (Control+X, Y, Enter). Now that you've set your udev rule you have to reboot (shut down terminal and reopen; I also recommend unplugging your phone from usb and plugging it back in) so that ADB will be in your path.
To test your changes, open up a terminal and execute the following:
$ adb devices
You should now see:
List of devices attached
C61DAXXXXXXX device
If you see:
List of devices attached
???????????? no permissions
Reread this post and try again.
more helpful udev info here http://wiki.cyanogenmod.com/wiki/Udev
Can't get this to work.
I'm on Ubuntu 12.10 64 bit version.
I have installed Android SDK, i have put in the paths in bashrc, i have created the file in /etc/udev/rules.d/51-android.rules
When i iisue the command abd devices:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
My tab don't show up...
I have tried lsusb and there it lists it as vendor 0b05 and product 4c90
I have tried with putting that in to 51-android.rules but to no avail.
Any hint on how i can get this to work?
I have even rebooted the laptop and tried restarting the adb deamon with: adb kill-server
Best regards Mackis
Mackis said:
Can't get this to work.
I'm on Ubuntu 12.10 64 bit version.
I have installed Android SDK, i have put in the paths in bashrc, i have created the file in /etc/udev/rules.d/51-android.rules
When i iisue the command abd devices:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
My tab don't show up...
I have tried lsusb and there it lists it as vendor 0b05 and product 4c90
I have tried with putting that in to 51-android.rules but to no avail.
Any hint on how i can get this to work?
I have even rebooted the laptop and tried restarting the adb deamon with: adb kill-server
Best regards Mackis
Click to expand...
Click to collapse
Yes, use the values you got with lsusb.
Did you set the permissions on the rules file to 0644 so all can read?
Yepp
ls -al /etc/udev/rules.d/51-android.rules
-rw-r--r-- 1 root root 194 okt 22 14:34 /etc/udev/rules.d/51-android.rules
And i even reloaded the udev rules by:
udevadm control --reload-rules
That way i don't have to reboot. But i tried rebooting to.....
Hmmmm in some mysteroius way USB debugging was disabled, i'm 100% confident i enabled it.......
Now i find my device puhhhhhhhhhh Was so near of reinstalling linux and going back to ubuntu 12.04 as a last resort.
Thanks for the help!!
Best regards Mackis
Mackis said:
Can't get this to work.
I'm on Ubuntu 12.10 64 bit version.
I have installed Android SDK, i have put in the paths in bashrc, i have created the file in /etc/udev/rules.d/51-android.rules
When i iisue the command abd devices:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
My tab don't show up...
I have tried lsusb and there it lists it as vendor 0b05 and product 4c90
I have tried with putting that in to 51-android.rules but to no avail.
Any hint on how i can get this to work?
I have even rebooted the laptop and tried restarting the adb deamon with: adb kill-server
Best regards Mackis
Click to expand...
Click to collapse
Are you using a US tf700 ASUS Infinity?
Just wondering why the product code was different for you.
Thanks
lowreeds said:
Are you using a US tf700 ASUS Infinity?
Just wondering why the product code was different for you.
Click to expand...
Click to collapse
lsusb with USB debugging disabled:
Bus 002 Device 070: ID 0b05:4c90 ASUSTek Computer, Inc.
lsusb with USB debugging enabled:
Bus 002 Device 071: ID 0b05:4c91 ASUSTek Computer, Inc.
64 bit used to require certain 32 bit libs to be installed once upon a time. Not sure if it's still the case, but you could try:
sudo apt-get install ia32-libs
_that said:
lsusb with USB debugging disabled:
Bus 002 Device 070: ID 0b05:4c90 ASUSTek Computer, Inc.
lsusb with USB debugging enabled:
Bus 002 Device 071: ID 0b05:4c91 ASUSTek Computer, Inc.[/QUOTE
Ahhh.
i see.
Click to expand...
Click to collapse
Yeah you are right, for some reason debugging was unchecked and im 100%sure i checked it. I have it up and running now. Thanks!!
//Mackis
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
lowreeds said:
List of devices attached
C70KASXXXXXX device
Click to expand...
Click to collapse
Just a heads up. I'm not sure it's such a good idea to out your serial number like that (I censored it in my quote for you)...