Ok, do I am changing all of my work over to Ubuntu and have the 1.5 SDK installed and working now. What I don't have is a device connection when I type "ADB Devices" in my terminal window, or when I bring up DDMS. IS there a trick to getting Ubuntu to recognize the G1 as an ADB device? Help is appreciated.
chicojd said:
Ok, do I am changing all of my work over to Ubuntu and have the 1.5 SDK installed and working now. What I don't have is a device connection when I type "ADB Devices" in my terminal window, or when I bring up DDMS. IS there a trick to getting Ubuntu to recognize the G1 as an ADB device? Help is appreciated.
Click to expand...
Click to collapse
Do a search for an Ubuntu SDK guide, there's a really good one floating around. You need to create a couple of text files to get it to register the USB device, the guide tells you how to do that.
Search for ubuntu udev android. You should be able to find it that way...
Hi,
I am having problems rooting my Transformer that I just purchased this morning.
My windows XP instance is running in VMWare as I have OSX.
I have the USB drivers installed and the APX driver. If I ADB the device in normal mode I can see the device ID, but when I connect in APX mode VMWare gives a warning about not being to connected to it's ideal controller. I am guessing this is because it's not installed to a USB 2.0 port.
When I run root.bat, my usb host controller interface blue screens and windows restarts.
Has anyone else had this problem? I not a noob as I have managed to root my desire and s-off it. I wondering if it's related to the VMWare USB message.
Thanks,
Jon
You can root the transformer in OSX, I rooted mine through terminal.
Sent from my Transformer TF101 using XDA Premium App
What method did you use? Did you try the nvflash method or using BLOB?
Jon
I've rooted and flashed Prime now but i'd be interested to hear how you did it on OSX. I created a linux VM in the end and used the method in this thread http://forum.xda-developers.com/showthread.php?t=1123429
Jon
They did it the old way in terminal.
Sent from my Transformer TF101 using XDA Premium App
Just use this guide
Didn't need to install any extra drivers like Windows users do get adb from the link provided at the beginning of the guide and the followed each of the steps including downloading the rooting tools. The commands are the same but are entered slightly differently in OSX.
Example
In OSX
Code:
./adb devices
instead of Windows
Code:
adb devices
If you've used OSX terminal before you should be fine.
Back when I did it it was primordial 3.1 but this guide has been updated for Prime v1.4 and the overclocking kernal and sloarnz customized CWM, the latter two i don't use myself.
Edit - I see I'm a bit too late replying, but yes just used terminal adb etc. Was very easy to do and satisfying.
Thanks for the replies, I'll have a read through, if anything just to improve my knowledge.
Thanks again.
Sent from my HTC Desire using XDA Premium App
Hi guys,
I'm currently experiencing a probem with my Nexus 4. No matter what OS I use (Linux or Windows) or what driver I use adb keep saying that my device is offline. As I saw elsewhere I tried an other usb cable or port but nothing seemed to work. Does anyone got an idea for this ? This thing is gonna drive me crazy !
Thanks
Task Manager, then kill the ADB one. Then open ADB, adb devices again.
Otherwise, did you check the debugging =.= Or reinstall the driver manually (not by WIndows).
I have had a problem with this and it has been unsolved as of yet, but I may be able to help you. In the SDK Manager, there is an extras area, if you don't have the drivers from there I have found you may have trouble. It could be something else, but this should be a sufficient launchpad.
Sent from my ADR6425LVW on GrayTheWolf's CM10 build.
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
saintjimmy said:
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
Click to expand...
Click to collapse
Are you on 4.2.2 they changed somethings with the update. Have you updated your SDK?
Try installing PDAnet drivers. They will make it work.
xdaOSdev.team said:
Try installing PDAnet drivers. They will make it work.
Click to expand...
Click to collapse
I can verify this, it solved the problem I have been having for a few months in Linux OSes.
Sent from my ADR6425LVW on GrayTheWolf's CM10 build.
saintjimmy said:
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
Click to expand...
Click to collapse
Guys, he said he's using ubuntu lol there are no usb drivers to install
try this...it sounds like your adb may be out of date. This will also reinstall fastboot, unless you leave 'android-tools-fastboot' off the last command
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
btw, if you haven't already done so, you should get the full sdk installed. It's better to have it and not need it than to not have it and realize after three hours of pulling your hair out you should have had it all along lol (I've done it, so I speak from experience)
Thanks @hp420 but sadly the device is still offline. I'm just realizing it now but I didn't have the warning message about the association with the computer that I usually have when activating USB debugging with 4.2.2
Load latest SDK version. Load driver inf fix. Search forum. Known problem. Easy fix.
sent from my nexus 4; cat on lap, beer in hand
This is due to the new whitelist for adb in 4.2.2.
Some of these steps may be unnecessary, but I know this works (I've had to do it a few times to all my devices that have been upgraded to 4.2.2).
You need the adb from the latest SDK.
Untick USB Debugging.
Reboot the phone.
Tick USB Debugging.
Reboot the phone.
On your PC, make sure you add the new SDK/tools to the PATH then do adb kill-server; adb start-server
Unlock your phone.
Plug it in to your PC.
A message on your phone will appear asking to add the PC to the whitelist.
Accept this and your phone should appear when you do an adb devices
No need for driver i'm running linux...
Sent from my Nexus 4 using xda app-developers app
Nark.GA60 said:
This is due to the new whitelist for adb in 4.2.2.
Some of these steps may be unnecessary, but I know this works (I've had to do it a few times to all my devices that have been upgraded to 4.2.2).
You need the adb from the latest SDK.
Untick USB Debugging.
Reboot the phone.
Tick USB Debugging.
Reboot the phone.
On your PC, make sure you add the new SDK/tools to the PATH then do adb kill-server; adb start-server
Unlock your phone.
Plug it in to your PC.
A message on your phone will appear asking to add the PC to the whitelist.
Accept this and your phone should appear when you do an adb devices
Click to expand...
Click to collapse
Tanks fort that answer I'll try it as soon as possible !
Sent from my Nexus 4 using xda app-developers app
Try typing
adb kill server
adb start-server
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Try typing
adb kill server
adb start-server
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
saintjimmy said:
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
try a live cd of ubuntu and see what happens. that will at least narrow it down to whether it's your ubuntu installation or your phone. if it still won't mount in the live cd we can assume it's an issue with your phone. from there you can run a nandroid backup and reflash the factory images to see if that fixes the issue. if it does, you can try a fresh install of the rom you're using. if it still works, then restore all your apps/app data
if it's your ubuntu installation there are other avenues you can try.
saintjimmy said:
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You can try uninstalling SDK and perform a fresh install. Move your platform tools to a more convenient locations and change the path under windows properties.
I don't know if you tried this already but..
Have you tried uninstalling and reinstalling the drivers for phone?
switch to another USB port? A different usb cable?
scream4cheese said:
You can try uninstalling SDK and perform a fresh install. Move your platform tools to a more convenient locations and change the path under windows properties.
I don't know if you tried this already but..
Have you tried uninstalling and reinstalling the drivers for phone?
switch to another USB port? A different usb cable?
Click to expand...
Click to collapse
UBUNTU!!!!!
lol
hp420 said:
UBUNTU!!!!!
lol
Click to expand...
Click to collapse
Or try using Ubuntu. LOL.
But dual-booting to another OS is a hassle.(?) If ubuntu is not your daily driver, you're gonna have to keep rebooting in between OSs.
scream4cheese said:
Or try using Ubuntu. LOL.
But dual-booting to another OS is a hassle.(?) If ubuntu is not your daily driver, you're gonna have to keep rebooting in between OSs.
Click to expand...
Click to collapse
Thann you all for your answers! I use linux mint which is my main OS. I manage to resolve my problem in a weird way: first I push a CWM recovery with fastboot and then I flash the ZIP from SuperSu ! From now USB debugging is working properly and I get the usual warning !
What I would like to know now is why ? Does the SuperSU ZIP reset something ?
Sent from my Nexus 4 using xda app-developers app
Hi guys I followed the instructions to root the Verizon G2 on my Mac. I installed adb and have an android folder but when I access terminal and type ./adb devices it detects the phone but says device offline. I'm wondering how to fix this? I feel like I've done every step right up to this point if I can get it to recognize adb commands I'm just stuck. Thanks for the help.
Sent from my VS980 4G using XDA Premium 4 mobile app
So running into a problem. I have downloaded and installed ADB but the version installed is 1.0.32. And my computer doesn't find any devices when I type adb devices.
Is this because I need a later version of ADB and if so any clue how to install it on Ubuntu? I have searched the WEB and can't find it.
Cheers!
swehes said:
So running into a problem. I have downloaded and installed ADB but the version installed is 1.0.32. And my computer doesn't find any devices when I type adb devices.
Is this because I need a later version of ADB and if so any clue how to install it on Ubuntu? I have searched the WEB and can't find it.
Cheers!
Click to expand...
Click to collapse
i am not a Ubuntu user (using Win10 for now), but i found this
https://www.howtoinstall.co/en/ubuntu/xenial/adb
hope that helps
DrakenFX said:
i am not a Ubuntu user (using Win10 for now), but i found this
https://www.howtoinstall.co/en/ubuntu/xenial/adb
hope that helps
Click to expand...
Click to collapse
Thanks DrakenFX for trying. I had already looked at that one. I looked some more and I guess Ubuntu has been having some problems with MTP. The answer for the problem is found at HERE if anyone is running into the same issue.
I use linux as well, but instead of installing the whole Android development kit, I went for the leaner, no-install-required platform-tools, which is the linux equivalent of "Minimal ADB and Fastboot". You can download it directly from Google here: https://dl-ssl.google.com/android/repository/platform-tools_r23.0.1-linux.zip
Unzip it, open up a terminal in the folder, and type " ./adb devices "
swehes said:
Thanks DrakenFX for trying. I had already looked at that one. I looked some more and I guess Ubuntu has been having some problems with MTP. The answer for the problem is found at HERE if anyone is running into the same issue.
Click to expand...
Click to collapse
man this was driving me nuts , LoL :silly::silly:
just did Step 1 and 2 and my issue got fix ,
just got back with dual boot Ubuntu 16.04.1 + Windows 10 and even installing the drivers couldn't get adb to detect my axon 7...till came across your thread and post reply to the other thread....thanks man
DrakenFX said:
man this was driving me nuts , LoL :silly::silly:
just did Step 1 and 2 and my issue got fix ,
just got back with dual boot Ubuntu 16.04.1 + Windows 10 and even installing the drivers couldn't get adb to detect my axon 7...till came across your thread and post reply to the other thread....thanks man
Click to expand...
Click to collapse
Glad I could help.
adb devices on ubuntu 16.04
swehes said:
Glad I could help.
Click to expand...
Click to collapse
Just to document this in case it would benefit someone else: I have been trying everything I could find on the net to get my A7 recognized by adb devices. The list always came up empty. Yet, on my windows 10, adb devices for my A7 worked. And my htc m7 on ubuntu was also recognized. Finally, I removed the famous 51-android.rules (which had a line for my A7 but not for my m7; on /etc/udev/rules.d) and then adb devices showed the A7.
EDIT:
The day after having written this, I lost the device again: adb devices no longer showed the A7. Again tried everything with no success. Then I downloaded the Android SDK, which comes with version 1.0.39 of adb. Ran that and it worked. Go figure. So I still cannot really put my finger on what made the difference.