Hi everyone
I have a Sensation 4g and my system runs Ubuntu 12.04.
I was wondering if there is any way to make Internet Pass Through work with Linux?
In Windows, I install the HTC Sync and it works, but what about Linux?
Thanks
NikosDim said:
Hi everyone
I have a Sensation 4g and my system runs Ubuntu 12.04.
I was wondering if there is any way to make Internet Pass Through work with Linux?
In Windows, I install the HTC Sync and it works, but what about Linux?
Thanks
Click to expand...
Click to collapse
It works by default
In windows it asks for htc sync coz it need drivers to recognize the device
In Linux drivers are not necessarily required
You can just connect the device and use Internet pass through
(if you got adb working on that pc already then you are good to go)
Sent from my pyramid.. Through blazing fast sonic waves
I remember this as well on Ubuntu 11.04 - I only needed to modify some lines for ADB to get it work
well add the attached 51-android.rules file to /etc/udev/rules.d/ ( remove the .txt extension to the file ..i need to add it to attach in xda )
and chmod it to 755
(i.e chmod 755 /etc/udev/rules.d/51-android.rules )
then try the pass through it might work
For me it is not working
Let me explain what I did.
First of all I connected my phone with the laptop. In the beginning the
Code:
adb devices
was giving me ??????????? but I restarted the server as root and then adb was recognizing my device properly.
Then I chose Internet Pass Through in my phone but despite the fact that Ubuntu recognize my phone as a Wired Connection 2 (Wired Network - HTC Android Phone) I don't have internet on my phone. Also when I chose the Internet Pass Through in my phone, the
Code:
adb devices
list is empty (is this normal?).
So, ganeshp I pasted the rules that you gave me in the /etc/udev/rules.d/ and I changed the permisions but no luck. It doesn't work.
Also, after enabling the Internet Pass Through after some minuter I get a failure message on my phone that says
Unable to connect to PC
Either you don't have the latest version of HTC Sync installed on your PC, or another phone is already using Internet pass-through on your PC. Please ensure......etc
Click to expand...
Click to collapse
davebugyi what lines you needed to modify in the adb to get it work?
No one has an answer for this? If you are using Internet pass through without problems in your linux OS share what you did to make it work.
NikosDim said:
No one has an answer for this? If you are using Internet pass through without problems in your linux OS share what you did to make it work.
Click to expand...
Click to collapse
I've got my HIS working in Ubuntu 12.04 (DHD also). No root access or adb needed. Just simple script for Network Manager. I've posted a blog entry about this, it's in Russian, but you can use Google Translate to read it. http_://blog.loquens.org/?p=489
NikosDim said:
For me it is not working
Let me explain what I did.
First of all I connected my phone with the laptop. In the beginning the
Code:
adb devices
was giving me ??????????? but I restarted the server as root and then adb was recognizing my device properly.
Then I chose Internet Pass Through in my phone but despite the fact that Ubuntu recognize my phone as a Wired Connection 2 (Wired Network - HTC Android Phone) I don't have internet on my phone. Also when I chose the Internet Pass Through in my phone, the
Code:
adb devices
list is empty (is this normal?).
So, ganeshp I pasted the rules that you gave me in the /etc/udev/rules.d/ and I changed the permisions but no luck. It doesn't work.
Also, after enabling the Internet Pass Through after some minuter I get a failure message on my phone that says
davebugyi what lines you needed to modify in the adb to get it work?
Click to expand...
Click to collapse
all you have to do is to use sudo
HTML:
sudo adb devices
Do the following:
Press CTRL + ALT + T to open the Terminal.
Inside the terminal type:
Code:
lsusb
Output should look something like this
Code:
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 003: ID 0bb4:0c86 HTC (High Tech Computer Corp.) Sensation
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Take note of these two values 0bb4:0c86 next to the HTC (High Tech Computer Corp.) Sensation.
Then type:
Code:
sudo nano /etc/udev/rules.d/51-android.rules
That will open a file named 51-android.rules then type:
Code:
SUBSYSTEM="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0c86", MODE="0666", OWNER="username"
In the text above change 0bb4 and 0c86 with the numbers you got from the lsusb, and instead of the username type youre user name.
Press CTRL + O and hit enter, then press CTRL + X .
if your adb-server was running up until now you need to kill it and restart it as root so type the following:
Code:
adb kill-server
sudo adb start-server
Then to check if everything worked out type
Code:
sudo adb devices
If all went well there should be an output similar this and you are good to go:
Code:
$ sudo adb devices
List of devices attached
BLABLABLA device
Edit: I assumed by the way that you have turned USB Debugging on :> that covers adb part, for the Internet pass trough you dont need drivers for linux just select the mode when you connect your device and you should be good to go.
Related
This is for if you have flashed a rom and it boot loops and when you try and restore and it stays in a bootloop,
I had this issue during the week and freaked out but thanks to termleech who created this http://forum.xda-developers.com/showthread.php?t=1699535 rom I was able to get my tablet back in working order.
This Tutorial is for Ubuntu/Linux (ill try and get one for windows but I wasnt able to do this through windows) for this im also guessing that you have a custom recovery flashed.
Step one:
go to http://source.android.com/source/initializing.html and go down to the section that says configure usb access the file will be saved in this location in /etc/udev/rules.d/51-android.rules
follow that section for all the lines that say "<username>" replace <username> with the account name that you are using,
in my case each of those it was changed to "aaron".
Step two:
Open terminal and type sudo lsusb this will display everything that is connected through usb. you should get something looking like this
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0c45:641d Microdia 1.3 MPixel Integrated Webcam
Bus 002 Device 003: ID 0b05:4d03 ASUSTek Computer, Inc.
Bus 002 Device 004: ID 0bda:0159 Realtek Semiconductor Corp. Digital Media Card Reader
Bus 002 Device 005: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 002 Device 006: ID 413c:8161 Dell Computer Corp. Integrated Keyboard
Bus 002 Device 007: ID 413c:8162 Dell Computer Corp. Integrated Touchpad [Synaptics]
Bus 002 Device 008: ID 413c:8160 Dell Computer Corp. Wireless 365 Bluetooth
Now in the File you created from step one create a new line and replace the values with the values you just got from lsusb
so the line for me looked like this when I pasted it back into the file.
# usbboot protocol on asus (Asus Transformer TF300T)
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", ATTR{idProduct}=="4d03", MODE="0600", OWNER="Aaron"
Step three:
Setting up the Android SDK
This is where I had the most trouble.
So you need to open the market place on Ubunto and download openJDK7, let that install then go to the android site and download the the android tools
http://dl.google.com/android/android-sdk_r20-linux.tgz
extract that to your desktop.
Then in terminal navigate to the folder called tools in the sdk and open it.
then type sudo ./android
that will install the tools and open android sdk manager.
when that opens all you will need to do is tick the tools box and it will install everything you need.
Once that is installed you will need to navigate to the platform-tools folder in the root of that folder.
What I did was also copy the rom that I wanted to flash into the folder just to make it easier on myself.
On your tablet boot it into the custom recovery but by powering the tablet it on and holding the volume down and power button then pressing the volume up.
YOu can leave you tablet in the home screen for the recovery for the next bit.
Step four:
Copying the rom to the tablet.
On terminal you will need to navigate back to the platform-tools folder.
and copy the rom you want to use into it (for this i will call the rom fix.zip this is just for this tutorial)
make sure your tablet is connected now and in the recovery sceen not{/B] fastboot!!!!!
on terminal type sudo ./adb push fix.zip /sdcard
It will look like its doing nothing that pop up saying that it copied it 33 seconds.
Step five:
factory reset x3
then wipe cache and dalvik
then flash + gapps (if not included with rom)
then wipe cache + davlik again
then reboot, on first boot it can take between 2-5minutes to start.
Now you have a working tablet again
Hope this helps those who are stuck! ill try get a guide together for windows and maybe a video if many people end up using this.
if you need to get in touch fast im always on twitter @d_crossfader
I am not responsible if anything goes wrong
How do you give root to a user in ubuntu? Thanks for the help by the way have ubuntu installed made rule but cant transfer because im not root user?
Sent from my HTCEVOV4G using xda premium
lukethepainter said:
How do you give root to a user in ubuntu? Thanks for the help by the way have ubuntu installed made rule but cant transfer because im not root user?
Sent from my HTCEVOV4G using xda premium
Click to expand...
Click to collapse
Just use sudo. There is no root user in Ubuntu-based distros.
almost got it
i followed all steps and when i go to push the rom i get
[email protected]:/media/sdk/platform-tools$ ls
aapt adb.vol03+04.par2 aidl fix.zip source.properties
adb adb.vol07+08.par2 api lib
adb.par2 adb.vol15+16.par2 dexdump llvm-rs-cc
adb.vol00+01.par2 adb.vol31+32.par2 dx NOTICE.txt
adb.vol01+02.par2 adb.vol63+35.par2 fastboot renderscript
[email protected]:/media/sdk/platform-tools$ sudo ./adb push fix.zip /sdcard
sudo: ./adb: command not found
[email protected]:/media/sdk/platform-tools$
any suggestions?
Hey could you enable root by following these steps https://help.ubuntu.com/community/RootSudo then try again as su
Sent from my Transformer Pad TF300T using XDA Premium HD app
On vacation this week will try it when I get home and thank you for helping me your the best
Sent from my HTCEVOV4G using xda premium
No worries, when it happened to me last week I freaked out
Sent from my Transformer Pad TF300T using XDA Premium HD app
Hi,
In fastboot mode my linux distro (Debian testing) can see and reboot the device:
Output of lsusb:
Bus 003 Device 011: ID 0502:33a5 Acer, Inc.
but with ./adb devices, I cannot see anything:
No trace in lsusb, debug usb is on, udev rules are ok, adb_usb.ini is ok and with ADB_TRACE="all", everything is ok except that there is no device in adb...
Any clue?
Thanks.
Ps: I did google around...
I am using the UBUNTU 12.04 LINUX and I am tring to do some tinkering with USB devices and AT commands .
I have successfully accessed my Huewei E150 USB modem via terminal and also sent a message and called from it.
by using (as a root)
cat /dev/ttyUSB2 (in one terminal)
echo "<AT COMMAND>" > /dev/ttyUSB2 (in another terminal)
now I want to do the same with my samsung C3222 chat .
I have found the device file for it as /dev/ttyACM0
and I am getting the outputs that the system does with it by typing the command
cat /dev/ttyACM0
(which shows that all the drivers are OK and I am able to connect to it)
but the problem is I am not able to communicate with it as I was doing with Huewei modem .
Some of the commands I am trying to do are
"AT"
"ATI"
"ATD<mynumber>"
AT+CMGR"
but none of the above commands get response from the hardware.
I need some help as I don't know how the samsung phones works with USB ? Where am I going wrong?? are there are different AT commands for SAMUNG phones .
This is just with Linux Mint- works in OS X.
adb in Mint works with Nexus 4 and One X every time but the OPO won't show up at all whether stock OS or Mahdi.
Any way to fix?
JAMCx said:
This is just with Linux Mint- works in OS X.
adb in Mint works with Nexus 4 and One X every time but the OPO won't show up at all whether stock OS or Mahdi.
Any way to fix?
Click to expand...
Click to collapse
Did u allow your pc from the phone when connecting it to adb?
JAMCx said:
This is just with Linux Mint- works in OS X.
adb in Mint works with Nexus 4 and One X every time but the OPO won't show up at all whether stock OS or Mahdi.
Any way to fix?
Click to expand...
Click to collapse
Just "sudo adb devices"
Happens to me on my ubuntu build VM too
bud77 said:
Just "sudo adb devices"
Happens to me on my ubuntu build VM too
Click to expand...
Click to collapse
Didn't work. The OTO does not show up in Mint as a connected device for some reason while the Nexus 4 and One X do and they respond to adb devices.
The OTO says connected as media device, android debugging enabled. Again it does connect and respond in OS X.
JAMCx said:
Didn't work. The OTO does not show up in Mint as a connected device for some reason while the Nexus 4 and One X do and they respond to adb devices.
The OTO says connected as media device, android debugging enabled. Again it does connect and respond in OS X.
Click to expand...
Click to collapse
Did yo follow these steps already ?
If you're developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on Ubuntu Linux:
Log in as root and create this file: /etc/udev/rules.d/51-android.rules.
Use this format to add each vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node.
Note: The rule syntax may vary slightly depending on your environment. Consult the udev documentation for your system as needed. For an overview of rule syntax, see this guide to writing udev rules.
Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
(From here)
bud77 said:
Did yo follow these steps already ?
(From here)
Click to expand...
Click to collapse
Above my pay grade ... I'll just plug it in the Mac
Thanks though.
Just plugged it into a W7 Pro machine and it saw it as a portable device and let me browse the folders without any tweaking.
JAMCx said:
Above my pay grade ... I'll just plug it in the Mac
Thanks though.
Just plugged it into a W7 Pro machine and it saw it as a portable device and let me browse the folders without any tweaking.
Click to expand...
Click to collapse
Just had the same problem and solved it by creating the file above.
Create the file
sudo vim /etc/udev/rules.d/51-android.rules
add the line below:
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666", GROUP="plugdev"
and reload the the new rules by using this command (or reboot ):
sudo udevadm control --reload
unplug the device and plug it back in and now "sudo adb devices" should show the correct name and status.
Do sudo bash, then password, the adb and fastboot work fine for me. If using windows cmd, run as admin.
Hi, all.
I went through the forums here and googled, but I can't find one working solution.
I have the tablet in subject (Acer Iconia B1-750).
I'd like to root it using guide I found on this forum and with modification for Ubuntu from here.
I can see my device in adb no problem.
When I run lsusb, I see device
Code:
Bus 003 Device 030: ID 0502:367b Acer, Inc.
So far so good.
When I do
Code:
adb reboot-bootloader
the device restarts to something called DROIDBOOT PROVISION OS.
When I type
Code:
lsusb
I can still see the device as
Code:
Bus 003 Device 031: ID 0502:3680 Acer, Inc.
So far so good.
However, when I do
Code:
sudo fastboot devices
I see no device connected.
I tried the -i 0x0502 switch for fastboot, did not help.
I am working on Ubuntu 15.10, kernel 4.2.0-30-generic x86_64, my android-tools-adb and android-tools-fastboot show version number 4.2.2+git20130218-3ubuntu42.
I tried to modify the ~/.android/adb_usb.ini, no help.
I also ensured I have correct permissions for plugdev on the device using udev rules and I do.
Does anyone have any advice how to force fastboot binary to "see" the device?
@sancho_sk Which Ubuntu version are you using?
Sent From my SM-G928F via Tapa
As I wrote:
I am working on Ubuntu 15.10, kernel 4.2.0-30-generic x86_64, my android-tools-adb and android-tools-fastboot show version number 4.2.2+git20130218-3ubuntu42.
Nobody? Seriously nobody works with Ubuntu?