OK so I tried these instruciton for Lucid on Maverick. I would post the link but I can't cuz I'm a newbie.
Download the latest Android SDK from Google: Android SDK
Extract the TGZ file to your home/user directory
NOTE: User would be your username
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Login as root and create this file: /etc/udev/rules.d/##-android.rules
NOTE: In the above file replace ## with the number 50 if you are running Gusty/Hardy/Dapper (50-android.rules) or with the number 70 if you are running Karmic Koala/Lucid Lynx(70-android.rules)
Or simply type in terminal sudo gedit /etc/udev/rules.d/##-android.rules then enter your password
The file should read:
For Gusty/Hardy: SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
For Dapper: SUBSYSTEM==”usb_device”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
For Karmic Koala: SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
For Lucid: SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
NOTE: In the above lines the code ”0bb4″ refers to a HTC device. If your phone is from a different manufacturer, replace the code with the appropriate from the table below.
Execute: sudo chmod a+rx /etc/udev/rules.d/70-android.rules
Reboot
To run ADB you need to add an environment variable to your bashrc file:
Open a terminal window and type: sudo gedit .bashrc
Add the following line at the end: export PATH=${PATH}:~/home/user/android-sdk-linux_86/tools
Save and close
You should be ready to go, type adb devices in a terminal window with your phone plugged in.
If you see a serial number pop up that means you are done. Should look something like this:
List of devices attached
HT99PHF02521 device
If for some reasons when running adb devices gives you a “no permissions” error, try typing the following in terminal
adb kill-server
adb start-server
USB Vendor IDs
MANUFACTURER USB VENDOR ID
Acer 0502
Dell 413c
Foxconn 0489
Garmin-Asus 091E
HTC 0bb4
Huawei 12d1
Kyocera 0482
LG 1004
Motorola 22b8
Nvidia 0955
Pantech 10A9
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
ZTE 19D2
Common ADB Commands
- Lists which devices are currently attached to your computer
adb devices
- Drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly
adb shell
- Lets you install an Android application on your phone
adb install
- Remounts your system in write mode – this lets you alter system files on your phone using ADB
adb remount
- Rets you upload files to your phones filesystem
adb push
- Lets you download files off your phones filesystem
adb pull
- Starts dumping debugging information from your handset to the console – useful for debugging your apps
adb logcat
Now, as for the credits, I took TheUnlockr “How To” for Windows as a base for this guide.
Click to expand...
Click to collapse
But it doesn't work in maverick. Please help. Because I really want to overlock my phone.
Also keep in mind I'm fairly new to Linux so be easy on the newbie.
Thanks guys.
49 views and no responds? Please help I'm desperate here.
So did post this in the wrong section? This silent treatment is killing me. lol
in terminal type:
$ sudo -i
$ gedit .bashrc
insert the same line at the end: export PATH=${PATH}:~/home/user/android-sdk-linux_86/tools
$ exit
$ sudo -i
$ adb kill-server
$ adb start-server
$ adb devices
benholiio said:
in terminal type:
$ sudo -i
$ gedit .bashrc
insert the same line at the end: export PATH=${PATH}:~/home/user/android-sdk-linux_86/tools
$ exit
$ sudo -i
$ adb kill-server
$ adb start-server
$ adb devices
Click to expand...
Click to collapse
Dude this is for adb, not for recognizing the USB...
My phone is HTC Desire and I am still figuring out why it doesnt work on 10.10 with all the rules...
hungrysquid said:
Dude this is for adb, not for recognizing the USB...
My phone is HTC Desire and I am still figuring out why it doesnt work on 10.10 with all the rules...
Click to expand...
Click to collapse
I'm assuming thisisspeedy got to the same stage i did: USB connects, i can access files through maverick, however adb won't detect the device to allow push/pull/shell.
simply elevating to root & editing the bash script on maverick solves the problem.
I have my Galaxy S connected to Maverick via USB, and i can run all ADB functions.
It should work for HTC using the correct code. If you have a problem with Ubuntu detecting your device on USB when you've set USB to mount on Android, PM me and I'll see if i can help.
Could someone post a link for the Lucid dirs? Thanks.
Sent from my T-Mobile G2 using XDA App
Thanks for everyone responses.
I figured it out thanks to this.
[QUOTEThe Android Debug Bridge (adb) is a tool lets you manage the state of an emulator instance or Android-powered device.
I was trying to run it for the first time on my ubuntu 9.10 box and I kept getting this error:
desktop:~/dev/Android/android-sdk-linux/tools$ adb
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'aub' from package 'aub' (universe)
Command 'dab' from package 'bsdgames' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'arb' from package 'arb' (multiverse)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'jdb' from package 'sun-java6-jdk' (multiverse)
Command 'ab' from package 'apache2-utils' (main)
adb: command not found
What was I doing wrong?
A quick google search shows me the error of my ways.. I haven't added my Android SDK tools directory to my system path!
It should go something like this...
open a terminal window and type:
$ echo $PATH
---(should return the directories associated with $PATH)
$ export PATH=$PATH:/home/YOUR-USERNAME/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)
And now I get:
List of devices attached
emulator-5554 device
Sweet Success!
p.s. Adding to the system path in Windows is along the lines of :
right-click '(My) Computer'
Select 'Properties'
Go to 'Advanced' or whatever tab you find 'Environment Variables'
Select 'Path' then 'Edit' and add your new path in.][/QUOTE]
adb trouble
Hi i am runing on Ubuntu Maverick with device Huawei U8110 on Celestial Teapot 4 ROM
java jdk ver6
installed Android SDK and tools in the home folder
i edit the rules file 99-android.rules to SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
saved and added the file permisions
restart the udev
Connected the Phone put the debug mode on
kill the adb then started
And Then Run The comand
[email protected]:/home/android-sdk-linux_x86/platform-tools# ./adb devices
List of devices attached
There is nothing in the list....?
HELP!? Please......
I use it for Marveric.
vim /etc/udev/rules.d/70-android.rules
# IS01
SUBSYSTEM=="usb",ATTRS{idVendor}=="04dd",ATTRS{idProduct}=="04dd",MODE="0666",OWNER="root"
# GalaxyS
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="681c",MODE="0666",OWNER="root"
# bravo
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
add like a above. then
/etc/init.d/udev restart
Good luck!
thisisspeedy said:
I figured it out thanks to this.
[QUOTEThe Android Debug Bridge (adb) is a tool lets you manage the state of an emulator instance or Android-powered device.
I was trying to run it for the first time on my ubuntu 9.10 box and I kept getting this error:
desktop:~/dev/Android/android-sdk-linux/tools$ adb
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'aub' from package 'aub' (universe)
Command 'dab' from package 'bsdgames' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'arb' from package 'arb' (multiverse)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'jdb' from package 'sun-java6-jdk' (multiverse)
Command 'ab' from package 'apache2-utils' (main)
adb: command not found
What was I doing wrong?
A quick google search shows me the error of my ways.. I haven't added my Android SDK tools directory to my system path!
It should go something like this...
open a terminal window and type:
$ echo $PATH
---(should return the directories associated with $PATH)
$ export PATH=$PATH:/home/YOUR-USERNAME/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)
And now I get:
List of devices attached
emulator-5554 device
Sweet Success!
p.s. Adding to the system path in Windows is along the lines of :
right-click '(My) Computer'
Select 'Properties'
Go to 'Advanced' or whatever tab you find 'Environment Variables'
Select 'Path' then 'Edit' and add your new path in.]
Click to expand...
Click to collapse
============================================================
THANK YOU!! (I did hit 'THANKS' as well)...
You pointed me in the right direction with Ubuntu 10.04.
The only change was with SDK..the 'adb' has moved to $ ~/platform-tools/
By the way folks, when you install SDK, it would be wise to do all the updates, otherwise the platform-tools folder won't be an option....:cyclops:
"The order has been restored.."
whenever i use adb in ubuntu it just says this:
Code:
[email protected]:~# cd /sdk/platform-tools
[email protected]:/sdk/platform-tools# adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
doesnt make sense.. works in windows but im tired of rebooting to use adb
any ideas?
Make sure adb in is your PATH: echo $PATH
If not, add it: export PATH=$PATH:/path/to/sdk/platform-tools
ikon8 said:
Make sure adb in is your PATH: echo $PATH
If not, add it: export PATH=$PATH:/path/to/sdk/platform-tools
Click to expand...
Click to collapse
I think you mean in your bash file. Go into your home folder and hit control-h. It should show hidden files. Open your bash and put the above-mentioned.
If you don't want to go that far you can always navigate to that directory and punch in the commands.
Sent from my ADR6400L using Tapatalk
thanks for the replies guys but ive already done that as well..ugh this is frustrating
You run an executable binary with a ./ before it in linux.
./adb devices
Like that.
But it's really best to add the directory to your path, so you can run adb from any directory easily.
Add this line to your .bashrc file (which is in your home directory) at the end:
export PATH=/sdk/platform-tools:$PATH
Then close and open a new terminal. Then you should be able to run adb without the ./ from any directory.
If that still doesn't work, type "echo $PATH" and make sure it shows the directory there. If not, you did something wrong saving that line in your .bashrc file, or it's not being loaded properly.
Nikolai2.1 said:
whenever i use adb in ubuntu it just says this:
Code:
[email protected]:~# cd /sdk/platform-tools
[email protected]:/sdk/platform-tools# adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'ab' from package 'apache2-utils' (main)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
doesnt make sense.. works in windows but im tired of rebooting to use adb
any ideas?
Click to expand...
Click to collapse
I know exactly what this is. Get out of hard root and stay in your regular home folder. There are two things that will make this simple for you. 1. take the adb executable and place it in your users bin. so that would be something like /usr/bin...once again make sure you are in nautilus as the regular user and not root! 2. Now go back into your terminal and invoke it by typing sudo adb start-server...then sudo adb devices...the key thing here is that ubuntu's permissions are a bit screwy so you have to use adb in this manner. once again sudo everthing ("sudo adb" etc.)...do not become hard root in ubuntu (sudo su)
EDIT: btw if you use this method you will not have to worry about paths as long as it's in your user bin...you dont have to ./adb devices either if you do it this way
Javis
GrdLock said:
You run an executable binary with a ./ before it in linux.
./adb devices
Like that.
But it's really best to add the directory to your path, so you can run adb from any directory easily.
Add this line to your .bashrc file (which is in your home directory) at the end:
export PATH=/sdk/platform-tools:$PATH
Then close and open a new terminal. Then you should be able to run adb without the ./ from any directory.
If that still doesn't work, type "echo $PATH" and make sure it shows the directory there. If not, you did something wrong saving that line in your .bashrc file, or it's not being loaded properly.
Click to expand...
Click to collapse
trendsetter37 said:
I know exactly what this is. Get out of hard root and stay in your regular home folder. There are two things that will make this simple for you. 1. take the adb executable and place it in your users bin. so that would be something like /usr/bin...once again make sure you are in nautilus as the regular user and not root! 2. Now go back into your terminal and invoke it by typing sudo adb start-server...then sudo adb devices...the key thing here is that ubuntu's permissions are a bit screwy so you have to use adb in this manner. once again sudo everthing ("sudo adb" etc.)...do not become hard root in ubuntu (sudo su)
EDIT: btw if you use this method you will not have to worry about paths as long as it's in your user bin...you dont have to ./adb devices either if you do it this way
Javis
Click to expand...
Click to collapse
Thank you both for the advice! Both things worked very well and i appreciate the advise!
sorry for the noob question, but i am new to android and new to rooting. is there a way to do this on a mac that isnt running a windows partition? if so is there an explanation?
jasonr803 said:
sorry for the noob question, but i am new to android and new to rooting. is there a way to do this on a mac that isnt running a windows partition? if so is there an explanation?
Click to expand...
Click to collapse
1. Make sure you have installed ADB and FASTBOOT command line tools first. You can install them from here: http://code.google.com/p/adb-fastboot-install/
2. Download djrbliss's exploit files. You can find it here: http://forum.xda-developers.com/showthread.php?t=1952038
3. Extract the entire zip file.
4. Connect your device via USB, ensure USB debugging mode is enabled.
5. Open Terminal and enter into the folder that you extract that zip file.
6. Just type the following command lines step by step:
1. adb wait-for-device
May be you will see this information in your terminal
=======================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=======================================
2. adb restore backup1.ab
3. adb shell "rm /data/data/com.android.providers.telephony/databases/a/b 2>/dev/null"
4. adb shell "ln -s /dev/diag /data/data/com.android.providers.telephony/databases/a/b 2>/dev/null"
5. adb restore backup2.ab
6. adb push pwn /data/local/tmp
After this you can see some information in your terminal like this:
========================================
1180 KB/s (64526 bytes in 0.053s)
========================================
7. adb shell "chmod 755 /data/local/tmp/pwn"
8. adb shell "/data/local/tmp/pwn"
After this if you see this in your terminal that means you are close to success:
========================================
[+] Set CID!
========================================
9. adb reboot bootloader
In this step, just keep waiting until your phone enter into fastboot mode, then excute step 10.
10. adb kill-server
11. fastboot oem readcid
If you see the cid like this you are success!!!
========================================
...
(bootloader) cid: 11111111
OKAY [ 0.010s]
finished. total time: 0.010s
========================================
12. fastboot oem get_identifier_token
Finally you can get your own identifier token.
For some reason the adb commands dont work for me. Is there something I'm missing?
Edit: Figured it out but now I get a "Failed." error when I type adb shell "/data/local/tmp/pwn"
jasonr803 said:
sorry for the noob question, but i am new to android and new to rooting. is there a way to do this on a mac that isnt running a windows partition? if so is there an explanation?
Click to expand...
Click to collapse
instructions have been updated and there is now a script for mac you can execute in terminal
http://forum.xda-developers.com/showpost.php?p=33178597&postcount=1
h1m said:
For some reason the adb commands dont work for me. Is there something I'm missing?
Edit: Figured it out but now I get a "Failed." error when I type adb shell "/data/local/tmp/pwn"
Click to expand...
Click to collapse
I also encounter this problem. Try to factory reset your phone first. I do this then it works fine.
Hello,
I'm trying to flash a custom a ROM for the first time but I'm facing some issues.
I'm using an Ubuntu 20.04 and my phone is an Asus Max Pro M1.
I can see my device with "adb devices" and I can boot in the bootloader with "adb reboot bootloader".
Then I can see my device with "fastboot devices". But when I'm trying another fastboot command (for example "flash recovery"/"flashing unlock"/"oem unlock") my terminal prompt is just hanging, I don't get any output. And it won't do anything until I restart my phone by pushing the power button, at that time it will just print three lines of logs telling me that the command failed.
Here is an example of what I get :
Bash:
[email protected]:~/Documents/Code/tel$ adb devices
List of devices attached
K3AXB762C86977F device
[email protected]:~/Documents/Code/tel$ adb reboot bootloader
[email protected]:~/Documents/Code/tel$ sudo fastboot oem unlock
...
FAILED (command write failed (Success))
finished. total time: 0.000s
Does anyone have an idea of what is happening ?
IMHO the typical command sequence is
Code:
adb devices
adb reboot fastboot
fastboot devices
fastboot <subcommand>
but I may err, as always ...
This requires an ENG HBOOT, get it here
1. Run the command line and type the command: cd (your platform tools folder) (Press Enter after each command)
2. Enter the command adb devices . It should come back with a list of connected devices and your serial number.
3. Enter the command adb reboot bootloader . (Your device will reboot and boot into a FastBoot USB)
(If your phone will not boot in normal mode. Manually reboot to boot and select fastboot).
4. Enter the command fastboot getvar mid .The window will show your current mid.
5. Enter the command fastboot oem writemid PG58*****
6. Enter the command fastboot reboot-bootloader
7. Enter the command fastboot reboot