Database Info

Problems with Thunderbolt and ADB under Ubuntu

I downloaded the uber files tonight to root my HTC Thunderbolt. However, when I moved onto the second step using ADB, I've hit a bit of a snag.
While I am seeing the device listed under devices, it's telling me it's offline. This despite the fact I can copy files to and from the microSD card, as well as internal memory. Below is what I see at my terminal:
[email protected]:~/Desktop/ThunderRoot/downgrade$ adb devices
List of devices attached
HT14DS015334 offline
I am using Ubuntu Lucid Lynx 10.04 32bit version. At this point, I'm guessing it has something to do with the HTC drivers since I didn't install HTC Sync (there is no version in linux, right??)
Anyone on here use linux with their Thundebolt? If so, are you connecting it via ADB??
Thanks,
Robert

I use 10.04 64bit and 11.04 64bit all the time with ADB. You don't need drivers with Ubuntu.

offline means it sees it but it's not connected. try replugging it in and/or kill the adb server and restart it.

as stated above, you do not need drivers for Ubuntu.
try adb kill-server
then adb start-server

you might also need to start the server as root.

UGH!! Turns out the problem was debug mode on the phone. Or rather the fact it WASN'T in debug mode!!!
Enable/Disable USB Debugging Mode - HTC Thunderbolt ADR6400
Once I changed that it showed up as device!!!

Anyone done this in an Ubuntu 11.04 VM in VMware workstation?

[Q]ADB/Fastboot on Ubuntu

My question says it...
I know it is possible on Google devices, but what about our O1? I had my phone to the service just because I couldn't install the drivers on 4 versions of windows...
Is it possible to use them to save our O1 from a permanent brick?

Are you talking about using adb on Linux to connect to your phone? It's quite possible, actually. It's not Ubuntu, but I was using Arch Linux when I rooted my O1. I bricked it once, but was able to revive it using fastboot. Anyway, check out the Ubuntu documentation on installing the Android SDK on Ubuntu. Once you have the SDK, you should have no problems running adb, etc.
---------------
Sent from my LG-P500 via Derpy Mail

onepinksheep said:
Are you talking about using adb on Linux to connect to your phone? It's quite possible, actually. It's not Ubuntu, but I was using Arch Linux when I rooted my O1. I bricked it once, but was able to revive it using fastboot. Anyway, check out the Ubuntu documentation on installing the Android SDK on Ubuntu. Once you have the SDK, you should have no problems running adb, etc.
---------------
Sent from my LG-P500 via Derpy Mail
Click to expand...
Click to collapse
Ok thank you, my problem is that I have no security in case I get my phone with a corrupted recovery and ROM at the same time...
So the phone is detected in fastboot/adb without any additional drivers?(that's what I hate about windows)
Sent from my LG-P500

vlt96 said:
Ok thank you, my problem is that I have no security in case I get my phone with a corrupted recovery and ROM at the same time...
So the phone is detected in fastboot/adb without any additional drivers?(that's what I hate about windows)
Sent from my LG-P500
Click to expand...
Click to collapse
Android and Ubuntu are about the same and may not need drivers. I tried it don't know if it will work for u
Sent from my LG-P500 using xda premium

vlt96 said:
Ok thank you, my problem is that I have no security in case I get my phone with a corrupted recovery and ROM at the same time...
So the phone is detected in fastboot/adb without any additional drivers?(that's what I hate about windows)
Sent from my LG-P500
Click to expand...
Click to collapse
For what it's worth, I didn't have to install any drivers at all, and I was able to adb & fastboot just fine. Just be sure to read the Ubuntu documentation on using Android on Linux, just in case there's any configuring needed.
---------------
Sent from my LG-P500 via Derpy Mail

Easy way to install ADB/Fastboot on ubuntu 11.04 to 12.04
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot

[Q] Rumrunner problem

I'm having a little problem to S-OFF my HTC One S with rumrunner. When my phone reboots the second time into bootloader, it says:
FATAL: Download updated package at rumrunner's website.I read that I had to turn off my firewall and disable the anti virus but even after doing so, the problem is still there. Anybody a suggestion ?

Try rumrunner with Ubuntu. It worked on the first try for me. Live CD or USB drive should work.
Sent from my Nexus 5 using Tapatalk

You mean the ubuntu package or in a ubuntu device? Isn't that like trying to run an ios program on Windows?

Ubuntu is an operating system for PC. If you're familiar with any Linux then you can use it instead of Ubuntu. When you have a working installation of Linux or live CD / USB drive, run rumrunner in it.
Sent from my Nexus 5 using Tapatalk

attelaut said:
Ubuntu is an operating system for PC. If you're familiar with any Linux then you can use it instead of Ubuntu. When you have a working installation of Linux or live CD / USB drive, run rumrunner in it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Not familiar at all.. thanks, but any other way?

Bump?

attelaut said:
Try rumrunner with Ubuntu. It worked on the first try for me. Live CD or USB drive should work.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Will you have to install the linux adb drivers before running rumrunner?

cyberusman said:
Will you have to install the linux adb drivers before running rumrunner?
Click to expand...
Click to collapse
There's no need to install drivers on Ubuntu since the drivers should be integrated to Linux kernel. Just download rumrunner and follow the instructions. Remember to turn on root access for ADB in developer settings and run rumrunner as root user (sudo...).

attelaut said:
There's no need to install drivers on Ubuntu since the drivers should be integrated to Linux kernel. Just download rumrunner and follow the instructions. Remember to turn on root access for ADB in developer settings and run rumrunner as root user (sudo...).
Click to expand...
Click to collapse
I tried it on windows and it worked the first time.

MTP issue after UE40 update

I could not explore the idol3 using MTP after the update.
I keep getting this error:
Unable to access Android "Unable to open MTP device '[usb:003,042]'"
Interestingly, I'm able to work with adb.
ubuntu-linux:/$ adb devices
List of devices attached
XXXXXX device
I'm using ubuntu 14.04, havent tried in windows or Mac.
Any solution?

What app/method are you using to access it as a mtp device?
KashRaman said:
I could not explore the idol3 using MTP after the update.
I keep getting this error:
Unable to access Android "Unable to open MTP device '[usb:003,042]'"
Interestingly, I'm able to work with adb.
ubuntu-linux:/$ adb devices
List of devices attached
XXXXXX device
I'm using ubuntu 14.04, havent tried in windows or Mac.
Any solution?
Click to expand...
Click to collapse

KashRaman said:
I could not explore the idol3 using MTP after the update.
I keep getting this error:
Unable to access Android "Unable to open MTP device '[usb:003,042]'"
Interestingly, I'm able to work with adb.
ubuntu-linux:/$ adb devices
List of devices attached
XXXXXX device
I'm using ubuntu 14.04, havent tried in windows or Mac.
Any solution?
Click to expand...
Click to collapse
Did you try with Windows ? Personnaly, I can't get any android device recognized with Ubuntu (latest version ) and any of its variants (Lubuntu, Kubuntu, Xubuntu) when using MTP mode. I do think there is a missing driver or something like. UMS will work, but not avaible on our idol 3. PTP works also, but so so...
Fortunately adb works like a charm with Ubuntu.

famewolf said:
What app/method are you using to access it as a mtp device?
Click to expand...
Click to collapse
I'm connected to the device thru USB. tried mounting thru Nautilus. It used to work before the update.
frankee207 said:
Did you try with Windows ? Personnaly, I can't get any android device recognized with Ubuntu (latest version ) and any of its variants (Lubuntu, Kubuntu, Xubuntu) when using MTP mode. I do think there is a missing driver or something like. UMS will work, but not avaible on our idol 3. PTP works also, but so so...
Fortunately adb works like a charm with Ubuntu.
Click to expand...
Click to collapse
Same machine is picking up my other devices (S3/ Nexus 4) using MTP. I will try in windows and mac and let know how it goes...

That's kind of weird, I'm using Linux Mint 17.2 and it works with no issues. Though oddly, my SD Card works in Android and mounts via MTP, but TWRP can't see it at all

linux:~$ mtp-detect | grep idVendor
Device 0 (VID=1bbb and PID=af2b) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
libusb_open() failed!: No such device
LIBMTP PANIC: Could not init USB on second attempt
Unable to open raw device 0

USB debugging not working properly (on Ubuntu)

Hello,
I just got a new U11, hoping to use it to test/debug my Android apps. But I cannot get it connect to ADB reliably. I have tried everything I could, including
enabling developer options + USB debugging
adb kill-server, adb start-server and adb devices
revoking USB debugging authorizations
authorizing & remembering my PC
I've tried countless combinations of the above, but adb keeps showing unauthorized or offline. Very very occasionally adb shows "connected", but Android Studio freezes when I run my app. When I unplug, Android Studio immediately unfreezes. But again, when I plug my phone it becomes unauthorized/offline.
My other Android phone works without any issues. Is it a bug with the stock firmware?
The phone is running stock European firmware, with everything stock (including locked bootloader).

Could anyone please test/confirm this on their Linux laptop/desktop? Any fixes? Thanks a lot!

Strangely, it works on Windows. Maybe Ubuntu kernel update yesterday broke adb :crying:

I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Sent from my XT1575 using Tapatalk

drzoo2 said:
I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Click to expand...
Click to collapse
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution

spolarbear said:
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution
Click to expand...
Click to collapse
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.

microcris said:
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.
Click to expand...
Click to collapse
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.

My Xiaomi running LineageOS (basically AOSP) doesn't have any issue. Perhaps HTC Sense heavily modified some USB options?

spolarbear said:
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.
Click to expand...
Click to collapse
I have no problem with my M8 and my computer.
Android "is" Linux. By that, at least, tools like adb and fastboot must be very well tested under Linux :angel:.
Try to open you computer file browser and to browse or copy some files from/to your computer/phone. I'm unable to do that also.
I tried to root my phone in the same day I received it and I was getting really worried because I was unable to use fastboot (I by that I was thinking that my device was defective), even the simple "fastboot getvar all". Then I remembered to switch to another computer and voilà, everything was working perfectly.
Maybe HTC has something broken in the USB3.0 stack.

File transfer and fastboot don't work on my Ubuntu either.

spolarbear said:
File transfer and fastboot don't work on my Ubuntu either.
Click to expand...
Click to collapse
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).

microcris said:
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).
Click to expand...
Click to collapse
I tried 4.10 and 4.4, neither worked

I have same problem with Windows 10 64Bit.

All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?

I have solved my problem. I have install Windows 10 new and now all working.

Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
What Linux distro/version are you running? I've been trying to get this working with Arch and it's driving me nuts!

I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..

Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
Flinny said:
I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..
Click to expand...
Click to collapse
Got it working by downloading adb straight from Google instead of using the Arch package.