Related
I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?
LOL, I just switched back from Ubuntu to Windows 7 just to see how things have progressed. There are so many little Windows 7 quirks that drive me crazy that drove me back to Ubuntu almost instantly. Give Linux a try. A good starting Linux OS would be Linux Mint:
http://www.linuxmint.com/index.php
I had a similar issue when I tried it. Despite the fact that there are 64-bit drivers for Vista/7 available, I don't believe they actually work for ADB currently. I'm pretty sure everyone who has ADB working is using Windows XP 32-bit.
I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.
I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.
ch4dr0x said:
I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?
Click to expand...
Click to collapse
I faced the same problem a few days ago. I have Windows 7 Ultimate x64 and in a first installations the drivers work fine and the device has been displayed, but BAM when I try to use ADB no way.
After many tries I resolved the issue running the Command Prompt as "Run as administrator" and VOILA worked fine.
I hope this can help you.
ch4dr0x said:
I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.
Click to expand...
Click to collapse
Try Mint instead of Ubuntu. Mint is Ubuntu based. The big difference with Mint is that it already has all of your codecs installed - great for beginners.
If you installed first the htc sync, you have to remove the current drivers..
and had the drivers from the androidsdk pack! There's is a a lot of program who delete usb installed hardware/drivers.. delete all from htc on this programs!
Hope this solves ur issue!
I use Win7 64bit(rc1) .. i have the amd64 driver installed..
I see the phone from adb (not fastboot) when it's normally connected with USB debugging turned on.
I see the phone from fastboot (not adb) when it's in fastboot mode.
I have no choice but to laugh at myself, just realized I was IN FASTBOOT on my phone and not recovery. Fail me.
Now if I could just edit this apps2hd code /sigh.
ricardomega said:
If you installed first the htc sync, you have to remove the current drivers..
Click to expand...
Click to collapse
and remove htc sync, there are a process than cause problem with adb (i don't remember the name)
I kill this process and adb 100% work fine, or unistall HTC Sync..
GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=
ricardomega said:
GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=
Click to expand...
Click to collapse
Except that... that wasn't my issue Its ok thanks for the input.
"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.
parrot5 said:
I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.
Click to expand...
Click to collapse
The same confi, the same result
Everything works fine here with Win 7 Ultimate x64, you just install the driver in the Android SDK.
make sure u have usb debugging checked... cause i have windows 7 rtm ultimate and my adb works fine... i just loaded the needed file into windows/system32 and also put my fastboot.exe in there and added the tools folder to the environment variables and have no problems
What do I load to the system32 folder? I can't install the drivers from the SDK package. Is there a way to overwrite the ones Windows automatically installs and thinks is more up to date?
detonate said:
"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.
Click to expand...
Click to collapse
Make sure your phone is in recovery mode and NOT fastboot mode.
Finally, I experienced that error you people had been reporting. It MAY have to do with the HTC Sync driver, as suggested, but it really had worked fine with other roms before, so I am not sure. I tried uninstalling and reinstalling the driver, tried to push the ADB driver manually, but that didn't work. And, before I try to uninstall the HTC Sync driver as suggested (I don't even know if I have that installed), I got it working by just plugging in another USB flash drive. Go figure.
So for anyone still having the issue after trying all other solutions, try this bizarre one:
1. Go to device manager and uninstall the HTC disk drive device. (This alone won't work, I tried)
2. With phone still plugged in, plug in a USB disk drive (or maybe just any USB device?) into another USB port.
3. Suddenly Windows 7 detect that unknown ADB driver, as it should. Now you can go ahead to install the correct ADB driver.
As a side note, this computer running Windows 7 Beta/RC have had a lot of problems with USB disk drives in general. The problems disappear after Windows 7 RTM (final).
Heimdall frontend does not work on mac.
I installed the packages qt 4.7 and Heimdall but this I do not see the galaxy's when I connect to the USB port (under the download) why?
mathun said:
Heimdall frontend does not work on mac.
I installed the packages qt 4.7 and Heimdall but this I do not see the galaxy's when I connect to the USB port (under the download) why?
Click to expand...
Click to collapse
Please refer to this thread for information and a possible fix.
!A. DOWNLOAD HEIMDALL SUITE For Your OS---LINK
SETUP OF HEIMDALL WINDOWS
MAKE SURE THAT YOU HAVE THE MICROSOFT C++ 2010 REDISTRIBUTIBLES INSTALLED INSTALLED; DOWNLOAD HERE ----LINK
UNZIP HEIMDALL
GO TO DOWNLOAD MODE ON PHONE
Windows
Read the Readme
OPEN THE HEIMDALL FOLDER AND NAVIGATE TO DRIVERS
OPEN zadig.exe
GO TO THE OPTIONS MENU AT THE TOP
SELECT LIST ALL DEVICES
INSTALL THE SAMSUNG COMPOSITE DEVICE DRIVERS
INSTALLATION MAY TAKE A LOT OF TIME
REBOOT PHONE NORMALLY
OPEN HEIMDALL FRONTEND
REBOOT TO DOWNLOAD MODE (VOLUME DOWN + POWER ON GB ROM)
SELECT FILES FROM THE ORIGINAL TAR (EXTRACT THROUGH 7ZIP OR SOMETHING LIKE THAT AFTER REMOVING THE .MD5 FROM THE END IF THERE IS ONE)
LOAD THE FILES THAT YOU WANT
Mac
Read the read me
Install the mpkg
Reboot
Open Heimdall-Frontent(Applications folder)
Load what you want to flash
or load heimdall archice(most have firmware.xml in it)
Put phone into Download Mode.
Flash(no need of installing any drivers)
airfluip1 said:
SETUP OF HEIMDALL WINDOWS
MAKE SURE THAT YOU HAVE THE MICROSOFT C++ 2010 REDISTRIBUTIBLES INSTALLED INSTALLED; DOWNLOAD HERE ----LINK
DOWNLOAD HEIMDALL SUITE 1.1.1---LINK
UNZIP HEIMDALL
GO TO DOWNLOAD MODE ON PHONE
OPEN THE HEIMDALL FOLDER AND NAVIGATE TO DRIVERS
OPEN zadig.exe
GO TO THE OPTIONS MENU AT THE TOP
SELECT LIST ALL DEVICES
INSTALL THE SAMSUNG COMPOSITE DEVICE DRIVERS
INSTALLATION MAY TAKE A LOT OF TIME
REBOOT PHONE NORMALLY
OPEN HEIMDALL FRONTEND
REBOOT TO DOWNLOAD MODE (VOLUME DOWN + POWER ON GB ROM)
SELECT FILES FROM THE ORIGINAL TAR (EXTRACT THROUGH 7ZIP OR SOMETHING LIKE THAT AFTER REMOVING THE .MD5 FROM THE END IF THERE IS ONE)
LOAD THE FILES THAT YOU WANT
FLASH!
Click to expand...
Click to collapse
thank you for posting this flip
people definitely need it
Lol
Sent from my SGH-T959V using XDA Premium App
Heimdall for linux install
go here and download i386 and or amd 64 based if u are running 64 bit nix or not
http://www.glassechidna.com.au/products/heimdall/
download the heimdall and then also the front end especally easy for ubuntu users
click the heimdall command line installer install though software center then install the front end
make sure you have usblib 1.0 installed most current distbutions installl this default for usb
open terminal and run the program heimdall-frontend or commandline which ever u want u can also make a laucher and lauch it as a shortcut
Sick post brah.. for Mac???
Sent from my SGH-T959V using XDA App
On, mac, we have an issue. I am a Mac and Windows user. I can't use my mac for flashing. I need windows. Why, because Heimdall is "compatible with mac". Unfortunately, everyone has had issues with Mac Heimdall above 10.6 Snow Leopard. this means that Leopard and under, work just fine.(I believe) I have Lion (10.7) which also is incompatible with Heimdall.
Dual boot with Leopard or Linux or Windows for it to work.
This guide is for windows
Thanks for all your help
Sent from my SGH-T959V using XDA App
This guide is outdated now and probably a good example of why you shouldn't hard link to a particular version. The latest version (1.3.0) works fine on all Snow Leopard and Lion versions. The READMEs includes detailed instructions for each platform.
istalled drivers ...is it normal that i dont see my device in odin nomore?
wizardslovak said:
istalled drivers ...is it normal that i dont see my device in odin nomore?
Click to expand...
Click to collapse
Yes, it's normal.
finish flashing phone in rainbow screen for long time
you need the correct bootloaders. Use the heimdall 1 click collection and find the beta 2d kernel with bootloaders. Flash it through the first page of heimdall. You will be good to go.
Ok, I have scoured google, xda, galaxytabhacks... you name it. I have pretty much tried it all. Yes I have tried heimdall, odin in virtualbox, updated ia32-libs, tried adb, tried fastboot... You name it.
I have a Galaxy Tab 2 10.1 (Wifi) and I thought it would be a fairly simple thing to root it and put a cyanogenmod Rom on it using a ubuntu 12.04 based OS PC I have. I guess I am wrong. I have figured out the Power On/Down Vol button puts the device in some recovery mode and the Power On/Up Vol puts it in the Download mode, but pretty much once I do either the usb connection to the device appears to be a brick - no matter what method I use.
When I do power up the device normally I do mtp-tools to try to recognize the device but they do fail to connect to it. So it is not a problem with USB at a low level - and honestly this PC has been used for a lot of technical things and it has worked flawlessly in the past. I have found several posts about linux/ubuntu and doing a root, but they seem to not have full answers.
Any help?
Tek Tengu said:
Ok, I have scoured google, xda, galaxytabhacks... you name it. I have pretty much tried it all. Yes I have tried heimdall, odin in virtualbox, updated ia32-libs, tried adb, tried fastboot... You name it.
I have a Galaxy Tab 2 10.1 (Wifi) and I thought it would be a fairly simple thing to root it and put a cyanogenmod Rom on it using a ubuntu 12.04 based OS PC I have. I guess I am wrong. I have figured out the Power On/Down Vol button puts the device in some recovery mode and the Power On/Up Vol puts it in the Download mode, but pretty much once I do either the usb connection to the device appears to be a brick - no matter what method I use.
When I do power up the device normally I do mtp-tools to try to recognize the device but they do fail to connect to it. So it is not a problem with USB at a low level - and honestly this PC has been used for a lot of technical things and it has worked flawlessly in the past. I have found several posts about linux/ubuntu and doing a root, but they seem to not have full answers.
Any help?
Click to expand...
Click to collapse
Is the cable disconnected when you try it? Also I assume you have a 10.1. You have to be clear on that.
Sent from my GT-P3113 using Tapatalk HD
Luigi2012SM64DS said:
Is the cable disconnected when you try it? Also I assume you have a 10.1. You have to be clear on that.
Sent from my GT-P3113 using Tapatalk HD
Click to expand...
Click to collapse
I have tried it cable disconnected, cable connected, cable complete off both pc and device, cable across the room, cable in a coil, cable in a straight line, cable in the left usb port, cable in the right usb port... You name it. So yes I have tried all of the variations. Trust me I have worked on this for 4 nights solid and have read every variations of tab 10.1 and tab 2 10.1 rooting guide and tried it (which many of them lie).
I think my original post said the device is a Samsung Galaxy Tab 2 10.1, but if it didn't that is the type. Again, I am trying to do this with/on a 64 bit Ubuntu 12.04 laptop. Its actually a Samsung Chronos 7 15.6". I has 3 USB ports and I have tried two of them (my wireless mouse is on one).
1. Put your Tab in download mode, conect it to your PC, run heimdall as root:
Code:
$ sudo heimdall detect
If your device not detected, downgrade heimdall to 1.3.1 .
2. Extract cf-auto-root for your device, flash it:
Code:
$ sudo heimdall flash --recovery recovery.img --cache cache.img
ketut.kumajaya said:
1. Put your Tab in download mode, conect it to your PC, run heimdall as root:
Code:
$ sudo heimdall detect
If your device not detected, downgrade heimdall to 1.3.1 .
2. Extract cf-auto-root for your device, flash it:
Code:
$ sudo heimdall flash --recovery recovery.img --cache cache.img
Click to expand...
Click to collapse
Normaly should
Code:
sudo heimdall flash --recovery recovery.img
be the thing, flash the supersu.zip in Recovery and you have been root.
Have you all udev rules? Fastboot and ADB is installed?
---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------
Oh and use only heimdall 1.3.1 all higher versions will brick your tab!
ketut.kumajaya said:
1. Put your Tab in download mode, conect it to your PC, run heimdall as root:
Code:
$ sudo heimdall detect
If your device not detected, downgrade heimdall to 1.3.1 .
2. Extract cf-auto-root for your device, flash it:
Code:
$ sudo heimdall flash --recovery recovery.img --cache cache.img
Click to expand...
Click to collapse
heimdall does not detect any device and it was already downgraded to 1.3.1. I have tried to build the 1.4 RC1 but I can't get beyond the lsub1.0.0 32 lib issues. I have also read all the tips on that and none of them seem to work either.
So I assume if I can't detect I can't do (2).
Any??
Any further ideas or help?
Dexxmor said:
Normaly should
Code:
sudo heimdall flash --recovery recovery.img
be the thing, flash the supersu.zip in Recovery and you have been root.
Have you all udev rules? Fastboot and ADB is installed?
---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------
Oh and use only heimdall 1.3.1 all higher versions will brick your tab!
Click to expand...
Click to collapse
I am only using Heimdall 1.3.1
I develop mobile apps and have adb installed and fastboot is installed. I played around with both of them trying to connect and neither would. Did not try as su.
What did you mean by udev rules?
The device is detectable but not connectable when it is operating normally by this laptop using mtp-tools. So I know the USB ports are working. It seems like once I put the device in either recovery or download modes the ports act "dead" like there is nothing on the other end. Do I need to manually mount something?
Tek Tengu said:
What did you mean by udev rules?
Click to expand...
Click to collapse
You need the 51-android rules to connect successfully a android device
Dexxmor said:
You need the 51-android rules to connect successfully a android device
Click to expand...
Click to collapse
Never heard of these in all the googling... Where can I find them?
http://developer.android.com/tools/device.html
https://code.google.com/p/51-android/
https://help.ubuntu.com/community/AndroidSDK
Put the attached file (the file in the zip) to /etc/udev/rules.d
Dexxmor said:
http://developer.android.com/tools/device.html
https://code.google.com/p/51-android/
https://help.ubuntu.com/community/AndroidSDK
Put the attached file (the file in the zip) to /etc/udev/rules.d
Click to expand...
Click to collapse
So does Heimdall use adb to accomplish its tasks under the hood? Is that the rub?
Sure, and fastboot this both are very important. But without the udev rules they are usseles.
Dexxmor said:
http://developer.android.com/tools/device.html
https://code.google.com/p/51-android/
https://help.ubuntu.com/community/AndroidSDK
Put the attached file (the file in the zip) to /etc/udev/rules.d
Click to expand...
Click to collapse
Still not connecting. Here are screenshots. I have the udev rules set up, and have rebooted adb does not detect any devices when I have the device in Download mode, nor does Heimdall.
Any more ideas??
Tek Tengu said:
Still not connecting. Here are screenshots. I have the udev rules set up, and have rebooted adb does not detect any devices when I have the device in Download mode, nor does Heimdall.
Click to expand...
Click to collapse
Any other ideas?? I am running out of options and I need to root/mod this tablet.
Resolved - but not with Ubuntu
Tek Tengu said:
Any other ideas?? I am running out of options and I need to root/mod this tablet.
Click to expand...
Click to collapse
I think there must just be some issue with Samsung/Ubuntu 12.04 with the USB devices with this Samsung device. I have done a lot of mobile development on this box, and have not run into issues before, but this one I poked and poked, and never made any traction any way.
Finally I brought up a Windows 8 machine (actually a slightly newer version of the same Samsung model, but a 17" laptop vs 15") and ran Odin and accomplished this rooting/ROM'ing with no issues whatsoever. Amazing. I am a big linux fan, have run into fringe issues like this before, normally after some poking resolved them - this one blows me away.
Thanks for the help!
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.