For whatever reason, my GT 7+ is showing: ????????? offline/device when I run adb devices. I've tried running adb kill/start as root, still nothing. I've cycled "USB debugging". I'm running ubuntu 10.10. Every thing but adb is working but adb
Any insight or help would be helpful.
udev.
See: http://wiki.cyanogenmod.com/wiki/Udev
Answered
Here's the rule I put up in /etc/udev/rules/98-android.rules:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666" #all samsung devices
Then restart udev and then restart adb and it's up!
This method is hard to remember. You can also start adb as root with:
adb start-server
and it should work that way, at least until adb is closed. You do not have to do all the adb commands as root, only the start.
Jason_25 said:
This method is hard to remember. You can also start adb as root with:
adb start-server
and it should work that way, at least until adb is closed. You do not have to do all the adb commands as root, only the start.
Click to expand...
Click to collapse
Why do you need to remember it? Create a udev rule once and you never have to deal with it again.
Running things as root should be avoided if possible.
I have found that there may be an issue with ubuntu 10.10 and this tablet. For me, it seems that the MTP crud is interfering with adb. If I freeze the MTP application on the tablet, I have no problem.
...and now it gets even stranger: If I boot ubuntu 10.10 in a virtual machine (vmware 8.x), its fine even with mtp enabled.
I haven't had any issue at all with my gentoo boot. (However, I've been trying to do the android development with ubuntu as it appears to be directly supported by google.)
(This really isn't an issue for me, as I actually prefer to keep MTP disabled so I don't get popups.)
Entropy512 said:
Why do you need to remember it? Create a udev rule once and you never have to deal with it again.
Running things as root should be avoided if possible.
Click to expand...
Click to collapse
Because I work on computers other than my own?
Because I have more than one computer?
Because I sometime reinstall the OS?
Because I don't have magical fail-proof hardware?
Because udev gets messed up and apt-get replaces the rules file?
This method is simpler for new users. The adb tools are straight from google so can be trusted and the udev approach just adds a lot of complexity.
edit:
garyd9 said:
I have found that there may be an issue with ubuntu 10.10 and this tablet. For me, it seems that the MTP crud is interfering with adb. If I freeze the MTP application on the tablet, I have no problem.
Click to expand...
Click to collapse
I do not seem to have any problem using 64-bit debian, which you probably know Ubuntu is based on. I have even built the AOSP with it without much trouble. Though, deploying it to a device is a different matter for me.
Related
Ok I think im going crazy, I cant find anything about this.
Im trying to access my tab via ADB in OSX. My Evo works just fine, but I just cant find the gtablet. I see in Windows driver's ini has to be modded to include tegra device ID and vendor ID, but I dont see anything for osx and my device is not getting recognized!
Thanks for your help!
Click to expand...
Click to collapse
Ok so after some time, I just found the solution, I dont know why I need it, and some people didnt but anyway, for whoever is having the same problem as I did, this is the solution!
This steps are assuming you have ADB ready and installed!
First, open terminal (/Applications/Utilities/Terminal.app)
Run the command:
Code:
android update adb
Then you will get a adb_usb.ini file in your $HOME/.android directory. Open that file and you will have the following..
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
Add in the 4rth line the following (Device vendor code, this case NVIDIA 0x0955):
Code:
0x0955
Save the file and exit.
On terminal window type
Code:
adb kill-server
and then
Code:
adb start-server
Adb devices should now show up your device!, if by any reason you get "device offline" a re-plug fixed it!
thanks!
damn! bumping this thread, really nothing? I just want to know if anyone can ADB with osx??? Its just me? or what?! thanks
Works fine for me.
OSX is the only OS I've used (so far) to connect to my G-Tablet via ADB.
Make sure USB Debugging is on on the 'pad, and it's Plug and Play. No udev stuff like on Linux, no USB driver issues like on Winhose.
I have had troubles in the past connecting through USB hubs. I'm currently using the front connectors on a Mac Pro.
Just another trivia note on the subject:
adb remount
Works for me on ZPad, it does not on TnT Lite.
I have a hackintosh netbook, but I don't really use it in this space. Nor Windows. Sorry about that.
Linuxslate said:
Works fine for me.
OSX is the only OS I've used (so far) to connect to my G-Tablet via ADB.
Make sure USB Debugging is on on the 'pad, and it's Plug and Play. No udev stuff like on Linux, no USB driver issues like on Winhose.
I have had troubles in the past connecting through USB hubs. I'm currently using the front connectors on a Mac Pro.
Just another trivia note on the subject:
adb remount
Works for me on ZPad, it does not on TnT Lite.
Click to expand...
Click to collapse
Thanks for your reply, so...TnT Lite doesnt work for you?..mh that may be. I have not tried Zpad!
Will keep trying!
roebeet said:
I have a hackintosh netbook, but I don't really use it in this space. Nor Windows. Sorry about that.
Click to expand...
Click to collapse
no worries! Thanks for the reply man!
Fix posted on OP!
Hey guys, I am a pretty new to ADB, I spent all day yesterday trying to figure it out and I think I have a fairly loose understanding of how it works. But, my question is what are the differences in the rooting guide if I'm trying to root on a Mac?
yea unfortunately for us mac users trying to root any device is very scarce, most if not all rooting methods require windows, even if they say works for mac, it usually doesn't for some reason.
I use VM ware, just torrent it for free, and torrent a windows 7 as well, if ussed this to root my older Droid model.
Rooting a phone using ADB on a Mac is no different than on Windows. IMO it's easier on osx/linux, as you don't have to worry about USB drivers.
Assuming you don't have a PATH variable setup for the platform-tools directory, just type "./adb whatever" instead of "adb whatever". That's about the only difference.
GrdLock said:
Rooting a phone using ADB on a Mac is no different than on Windows. IMO it's easier on osx/linux, as you don't have to worry about USB drivers.
Assuming you don't have a PATH variable setup for the platform-tools directory, just type "./adb whatever" instead of "adb whatever". That's about the only difference.
Click to expand...
Click to collapse
+1. It's SOOO much easier on a Mac, no driver issues, same basic command lines.
The only time it's easier on Windows is if there's some one-click method that requires a windows executable...but you still have to worry about getting Win to recognize the phone.
Edit: to answer the original post, there's no difference. Just put ALL the files into the same folder on your computer. Open the terminal app, type in cd then drag and drop the folder onto the terminal and hit enter. Type in ls and enter to make sure the files are actually there. After that, just follow the guide step by step. You can even drag and drop or copy/paste the commands. That's what I did (to make sure I made no typos).
Come to think of it, if OSX has curl installed on it (which I have no clue if it does or not), the linux easyroot script in the development forum should work just fine.
If not you could probably just change curl to wget and it would work fine. I'm assuming OSX comes with wget.
GrdLock said:
Come to think of it, if OSX has curl installed on it (which I have no clue if it does or not), the linux easyroot script in the development forum should work just fine.
If not you could probably just change curl to wget and it would work fine. I'm assuming OSX comes with wget.
Click to expand...
Click to collapse
OS X comes with curl.
Hi guys, I have been having major reboots problem with my Sensation after upgrading to the new ICS firmware. I have described my problem in this thread. The last attempt to fix my problem was flashing the firmware from this thread. I'm trying to flash other firmwares from the development section, but i keep getting the wrong model ID error. After some research, I believe I need to change my phone's CID to superCID using ADB.
And I have followed the instructions from this thread to do the superCID on my phone. Unfortunately, ADB is not detecting my phone. I installed ADB on two other Windows machines with the same result. Any help is greatly appreciated.
If you're running ADB from Linux (Ubuntu or something like it) by chance, you can run the commands as root. Put 'sudo' in front of the commands. That might fix it.
Also, try killing the server and restarting it. I don't know if this works in Windows.
Linux commands....
sudo ./adb kill-server
sudo ./adb start-server
./adb devices
Windows commands....if this even works in Windows (I've never tried using ADB in Windows so I have no idea)
Same, just take out sudo and "./"
Not sure if needed, but do you need to have HTC sync for adb to work properly?
Skipjacks said:
If you're running ADB from Linux (Ubuntu or something like it) by chance, you can run the commands as root. Put 'sudo' in front of the commands. That might fix it.
Also, try killing the server and restarting it. I don't know if this works in Windows.
Linux commands....
sudo ./adb kill-server
sudo ./adb start-server
./adb devices
Windows commands....if this even works in Windows (I've never tried using ADB in Windows so I have no idea)
Same, just take out sudo and "./"
Click to expand...
Click to collapse
Thanks for the reply buddy. I don't have any machine running Linux at the moment, but I will try killing the server in Windows.
In the mean time, can anyone help me find an older/stable firmware please? My phone have been rebooting every 2 minutes. Opens camera, reboots. Opens youtube app, reboots. Makes a call, reboots. It's driving me crazy!!
i had the same problem when i tried to flash the radio for my new ics...
so what i did was to to untick and retick the usb debugging mode and suddenly my windows 7 can automatically install some drivers in my computer... i also install htc sync too... then only my phone can be detected by my computer and i was able to flash the radio...
Thank you for the help guys. It turns out i didn't install HTC Sync. I just flashed a new firmware from the dev forum. Hopefully it will solve my nightmare.
I have come to the conclusion that the latest firmware broke all the gingerbread based rom , and so far only the 4.0.3 Sense ROM works, and not even the asop based 4.0.3 rom.
Sent from my HTC Sensation using Tapatalk
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.
I'm really having a hard time getting ADB drivers to work on Windows 7 so that I can connect my Android phone to my computer to run some ADB commands. I've tried three different packages; I guess the latest ADB MSI installer and another couple various packages. And I can't get any devices to show up when I type ADB devices. I need something simple if somebody can help treat me like a newbie although I have some experience with Linux and the command prompt but I really need something dead simple that will just install ADB on my computer so I can run a command on my phone. Any help would be greatly appreciated.
Wjbell said:
I'm really having a hard time getting ADB drivers to work on Windows 7 so that I can connect my Android phone to my computer to run some ADB commands. I've tried three different packages; I guess the latest ADB MSI installer and another couple various packages. And I can't get any devices to show up when I type ADB devices. I need something simple if somebody can help treat me like a newbie although I have some experience with Linux and the command prompt but I really need something dead simple that will just install ADB on my computer so I can run a command on my phone. Any help would be greatly appreciated.
Click to expand...
Click to collapse
While plenty of people know adb better than I do, I can try to help you where we need to start at the beginning I think, which is to state that there is nothing to "install" on either Android or Windows, other than the one adb.exe executable on Windows.
However, you do need to enable a few options in Android settings.
With that, you can get Windows to talk to Android over adb as shown in my screenshots below, whether over USB or completely over Wi-Fi.
My first question to you to help you is to ask a basic question.
Q: Did you turn on USB debugging in Developer options?
A: ?
Yes I have us debugging on on my Android phone. I've installed USB drivers before on an older phone to allow me to use my Android phone for an internet connection on my PC and it was pretty simple and word flawlessly.