I'm trying to sort a bricked phone my ZTE Nubia z5s mini, I've installed linux mint to try and debug the issue but its not detecting my phone where as when in windows it does through adb.
I've installed the ADB & Fastboot packages for linux but it still does not show up on the list of devices, does anyone know how to get linux to detect the phone? am I missing linux drivers for this phone over where windows fills in the gaps because I have no drivers other than the Google USB driver installed for the phone on windows.
try this out, if you can't get that to work let me know.
Audiomad said:
I'm trying to sort a bricked phone my ZTE Nubia z5s mini, I've installed linux mint to try and debug the issue but its not detecting my phone where as when in windows it does through adb.
I've installed the ADB & Fastboot packages for linux but it still does not show up on the list of devices, does anyone know how to get linux to detect the phone? am I missing linux drivers for this phone over where windows fills in the gaps because I have no drivers other than the Google USB driver installed for the phone on windows.
Click to expand...
Click to collapse
ok if you can get to the cd part at all........ open terminal
sudo mkdir /media/<username>/sr1
sudo mount /dev/sr1 / /media/<username>/sr1
Go into the cd drive that was just mounted, copy the USB drivers from the Linux folder. Extract the drivers, now back to terminal and navigate to the folder you unpacked and enter
sudo ./install
command not found
Related
Hi.
I'm trying to make some custom native software for android but I need some help getting started.
What I have done so far is getting a HTC Hero, GSM version.
Flashed a custom rooted ROM. update-hero-generic-2.73.405.38-rooted-signed.zip
Installed the sdk and ndk on Windows.
Downloaded and built the open source android project in a VMWare ubuntu image.
What I'm trying to do now is to get ADB talking to my Hero.
I have USB debugging on in the applications->development menu on in the Hero.
When I attach the phone to my XP PC it detects it and asks for drivers, I point it to drivers in android-sdk-windows\usb_driver, windows won't load them because they do not match the hardware.
I can install the driver manually but eventhough the device manager lists it as working (android phone with android composite ADB interface) adb cant find it.
adb devices just give me an empty list.
I tried this on a Windows 7 box and it seemed to work there, is there something special I need to do to get it working on XP?
Installing HTC Sync (drivers included) should resolve.
Thanks!
I actualy tried that before posting but it did not seem to work.
I now tried it again and this time I manually installed the driver in the HTC directory and now it works.
Hey, I was wondering if anyone had a link to download the HTC Bootloader drivers. It fails when I try and load "something" in Windows.
Thanks.
p.s: This will lead to good things...
The only drivers that I am aware of are the ones that are in the Android SDK Toolbox and in the HTC Sync program. Correct me if I am wrong, but as far as I know, they aren't specific drivers ie "bootloader" drivers. They are just drivers to get your comp to recognize the phone when its attached.
I'm assuming this is something you're expirementing with to get root via the adb in recovery, if so, good luck.
-------------------------------------
Sent via the XDA Tapatalk App
Hi crax0r,
The folks at Android (aka Google) provide these instructions for installing the drivers. It involves installing their SDK first, and installing Java for that, and an IDE called eclipse.... UGH.
The HTC "Sync" Application that hoovnick is referring to can be found here.
It has been so long ago that I installed drivers (on a WinXp x32 laptop) that I can't remember what order I did things in, whether or not the driver used by HTC sync is sufficient for fastboot but not adb (or vice versa), whether I did the SDK install first, etc etc etc. As a matter of fact, it's been so long ago that the computer that I did it on is now dead, and here I am using a Linux machine.
For all I know, the order you do things in affects the outcome - it sure seems like a lot of folks with Windows 7 complained about driver troubles.
One thing is for sure, though - setting up the entire Android SDK (+ Java + Eclipse + ...) in order to install a device driver has to be the worlds most roundabout way of doing a driver install.
If you are considering using the "fastboot" method to install Amon_RA's recovery boot, you might try just installing HTC Sync first, and see if that is sufficient for getting fastboot talking to the phone. That install is way, way easier than setting up the SDK to get a driver installed.
The other thing which is an option, if you are a little bit Linux-savvy, is to boot one of those "Live CDs" (Ubuntu, SuSe, etc) on your PC - there are no drivers to install in the case of Linux, you just need to be running as "root" on the Live (linux) CD to get fastboot to talk to the phone. The downloads (fastboot for Linux and the Amon_RA recovery image) are small, and they will both easily fit in the /tmp folder of the Linux (Live CD) boot on the PC.
Once you have Amon_RA on the phone, you won't need the SDK any longer, unless you want to start doing dev-like things; that's why a one-time boot into Linux would also work.
bftb0
I <3 Ubuntu. It's amazing!
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
crax0r said:
It's OK. I'm running Ubuntu now.
Click to expand...
Click to collapse
Excellent. Just remember to always run fastboot as root, and if using adb, then the first time after you boot (the PC), run adb as root.
The reason is that by default, Ubuntu won't let an unprivileged user access the USB.
Since I have adb and fastboot in my Ubuntu (regular user) PATH, I usually just do a
$ sudo `which adb` blah-blah-blah
or
$ sudo `which fastboot` blah-blah-blah
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
I don't know - I've already forgotten everything I did with the driver install in Windows, and I don't currently have a working Windows machine. Sorry I can't be of more help. As I said, the troubles people have been having seem to depend on which version of Windows (Xp/Vista/7), whether its x32 or x64, phase of the moon, etc. Seems like people run into snags on Win7 or x64 versions of Windows more than Xp-32, but I don't know why that is.
Keep plugging away at it. If you are looking for resources to help resolve the problem, I would go look at docs relating to Windows driver install troubleshooting - the driver install problem seems to be a Windows issue, not really anything to do with the SDK.
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
Sounds like what happened to me. i had to hit the icon at the top of my phone that showed the usb cable.. i had to switch charge only to disk drive "mount as disk drive"... folder popped right up on my windows machine asking how i wanted to open the file
I have the SDK running and my phone being recognized on my computer with Vista but I have another one running XP 32 bit and windows will NOT recognize the .inf? Any ideas? I deleted all previous HTC drivers and tried that approach but nothing seems to be working.
I'm trying to get adb to detect my Electrify on Windows 8, it would seem rooting and/or installing ROMs is impossible without adb, I have my phone plugged in and all the drivers installed except one "Motorola ADB Interface" of course. The manual driver installer errors out on "Cannot detect Operating System" is there anyway around this, either forcing the driver in, or not using ADB to root?
Use a linux live cd and install the android sdk, or use something like vmware, or try to extract the driver and force it to install in device manager, or dual boot an os that isnt in beta...
Sent from my MB855
The linux live cd should actually work I didnt think about that
I found this
http://forum.xda-developers.com/showthread.php?t=741824
It says its for use with HTC phones but could it possibly work with mine?
Its a year and a half old
Will the driver for my phone be installed/available?
I would post this there but its kind of a dead thread
If you have a spare thumb drive of 4gb or larger laying around you can do a persistent install of ubuntu (or just about any other distro) using LinuxLive USB Creator, which can be found here: http://www.linuxliveusb.com/
If you're not very familiar with linux, persistence is like having your linux operating system on a thumb drive with the advantage over a live cd being that any changes you make (such as installations or saved files) are not lost upon shutdown. So you could install the android sdk (which is all you should need) and then whenever you needed it you could just boot from your thumb drive. If you need help setting up (such as installing the sdk and setting the path and what not) let me know.
-devx
Hello,
I'm trying to build my own ROM (CyanogemMod) unfortunately, the command adb devices returns the device name but says its offline.
I don't think it's directly caused by the phone because the same command under Windows is working fine. (see attached pic)
So I tried every USB port (2.0 or 3.0), restarted the VM, the Phone, kill then start the adb server, but the issue remains.
I desperately need your help
Thank you
--
My "building" machine is running under Linux x64 (Ubuntu 12.10) through VMware 9.x
With the new secure adb I had an issue:
(I was transferring data to a new harddrive and in the process
I deleted my /home/me/.android/ (somewhere in \Users\me\AppData\ on windows) folder because I thought I didnt need anything in it.
Then I wanted to pull some files from my CM10.1 nightly device per adb.
It said: "error: device offline" when trying to access it.
Now, the computers adb key was gone with the userdata folder of the sdk (the .android folder) and access was denied. But somehow whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization.
To fix that I did the following:
delete the computers adb key: rm /data/misc/adb/adb_key on device
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
works
In my case it was even nastier because my sdk userdata folder ~/.android (on small ssd) was a symlink to /data/home/me/.android (on a huge drive for the emulators, android-sources and stuff)
and the symlink pointed to a nonexisting path which prevented saving any sdk settings.
On deleting the symlink or recreating the folder it should work.
Thanks. Very useful! :good:
for me and the HTC One X it wont work.....
-Happy Feet- said:
for me and the HTC One X it wont work.....
Click to expand...
Click to collapse
Did work previously?
maybe restart the adbd on the phone.
Can you test in Recovery, Cwm has an extra button for restarting.
Maybe Stock too.
Illidan Pornrage said:
With the new secure adb I had an issue:
(I was transferring data to a new harddrive and in the process
I deleted my /home/me/.android/ (somewhere in \Users\me\AppData\ on windows) folder because I thought I didnt need anything in it.
Then I wanted to pull some files from my CM10.1 nightly device per adb.
It said: "error: device offline" when trying to access it.
Now, the computers adb key was gone with the userdata folder of the sdk (the .android folder) and access was denied. But somehow whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization.
To fix that I did the following:
delete the computers adb key: rm /data/misc/adb/adb_key on device
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
works
In my case it was even nastier because my sdk userdata folder ~/.android (on small ssd) was a symlink to /data/home/me/.android (on a huge drive for the emulators, android-sources and stuff)
and the symlink pointed to a nonexisting path which prevented saving any sdk settings.
On deleting the symlink or recreating the folder it should work.
Click to expand...
Click to collapse
Fraid it didn't work. End up with various errors and randomly appearing devices. Plus, the original error reappears eventually. Please help!
If you give me some Info around the issue, like what you intended to do and if it worked previously, I could help you.
FIX adb offline problem
When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer.
This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog.
This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.
If you haven't this pop-up mesage in your device, there is the solution :
1) Install SDK in your PC
It may asks you to install JAVA, if so, do it.
2) make sure that your adb is 1.0.31 or upper, to know the version, tape : adb version in your commande window
------------------------------------
After that you every thing will be OK
this solved my problem
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
I've ADB problem in bootloader mode: devices not found, list empty. It works fine with phone in normal mode
I've upgraded to adb .31, upgraded drivers but no solution, BTW fastboot devices corectly displays device
Any help ?
Thanks
ciano865 said:
I've ADB problem in bootloader mode: devices not found, list empty. It works fine with phone in normal mode
I've upgraded to adb .31, upgraded drivers but no solution, BTW fastboot devices corectly displays device
Any help ?
Thanks
Click to expand...
Click to collapse
as far as I know adb doesn't work in bootloader mode.
MadMan29729 said:
as far as I know adb doesn't work in bootloader mode.
Click to expand...
Click to collapse
How can I push file to phone it doesn't boot ?
I think thats intentional, bootloader mode is the mode corresponding to fastboot for directly flashing, deleting, formatting, stuff like that in the most basic environment. Try recovery or normal boot for adb, which is for debugging, shell access, backup, filetransfer and so on.
(More info for more specifics)
Thanks, my mistake not using recovery
from Nexus 4 with Tapatalk
took me a bit to get into the thing myself after > 4.2 update
i'm on ubuntu
i had to use the terminal command
Code:
android update sdk --no-ui
a couple of times to get the thing actually updated. using just
Code:
android update sdk
wasn't cutting it for some reason. probably because i'm stupid and didn't fiddle with it enough.
then, realized when i STILL couldn't access the device (even after accepting the computer's RSA key on my n7),
it was because i had previously put a now deteriorated version of adb in /usr/bin. so, i rm'd it (navigate to /usr/bin and
Code:
sudo rm adb
then navigate over the folder whereeveryouputyoursdk/platform-tools/ and
Code:
sudo cp adb /usr/bin
that should be the new version of adb into /usr/bin. remember, do all that after running the
Code:
android update sdk --no-ui
a few times
peace
Long time I play with adb (1.0.31) from Linux without problem.
Today I flash new kernel (GT-I9505_AdamKernel.V1.6 then try Abyss-GT-I9505-1.6.1)
Got abd "device offline"
I come back on KT-SGS4.
adb works.
Can anyboby explian be why adb down't work with some kernels?
MadMan29729 said:
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
Click to expand...
Click to collapse
ah great i thought there was an issue with my adb and you wrote the solution
MadMan29729 said:
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
Click to expand...
Click to collapse
Thanx man you saved me !!!
Sent from my Micromax A57 using xda app-developers app
Thanks
I still had this problem on OSx and Ubuntu in cli.
what i've done on both to address it is, update the SDK to get the newest adb. (i'm suing 1.0.31)
killall adb
then turn off USB debugging on device.
start new adb (doesn't work nothing to connect to)
then turn on USB debugging and suddenly you get the pop up on the android device that says "always allow this computer at xxx"
test adb devices and should show 'device' instead of 'offline'
or try sudo, unplug the device, run adb under sudo on the desktop (sudo adb kill-server; sudo adb start-server), then plug the device back in.
yay!
svs57 said:
Long time I play with adb (1.0.31) from Linux without problem.
Today I flash new kernel (GT-I9505_AdamKernel.V1.6 then try Abyss-GT-I9505-1.6.1)
Got abd "device offline"
I come back on KT-SGS4.
adb works.
Can anyboby explian be why adb down't work with some kernels?
Click to expand...
Click to collapse
When it does that, go to Developer Options and Revoke Permissions and replug it back in. If that isn't it, then make sure you have the newest version of adb. Have had that happen on a couple of times on newer Samsungs.