Related
Hi, I have a Thunderbolt, CM7.1.0 RC0-Thunderbolt-KANG, Kernel 2.6.35.9-cyanogenmod, Android 2.3.4
I've not updated to the one in http://forum.xda-developers.com/showthread.php?t=1049542 because of the Radio problems, and I can't push a Radio because of THIS problem (I've got a few, but a thread for each):
I can't get ADB to detect my device at all. The Android ADB Interface will show up for other rooted devices, just not this one. Laptop, XP SP3, bit old, but works fine. Similarly, I can't get PDANet to detect it, no matter which driver I use. The only device that shows up in Device Manager is "HTC Android Phone USB Device".
Oh, and I've run SDK Manager, making sure everything is up to date. If you want to double check this, just tell me what info to post, I'll gladly do so.
I can't do anything ADB without this. Help?
Bumping this because of how swiftly it got buried. Two hours it's up, and it was four pages down...
triaddraykin said:
Hi, I have a Thunderbolt, CM7.1.0 RC0-Thunderbolt-KANG, Kernel 2.6.35.9-cyanogenmod, Android 2.3.4
I've not updated to the one in http://forum.xda-developers.com/showthread.php?t=1049542 because of the Radio problems, and I can't push a Radio because of THIS problem (I've got a few, but a thread for each):
I can't get ADB to detect my device at all. The Android ADB Interface will show up for other rooted devices, just not this one. Laptop, XP SP3, bit old, but works fine. Similarly, I can't get PDANet to detect it, no matter which driver I use. The only device that shows up in Device Manager is "HTC Android Phone USB Device".
Oh, and I've run SDK Manager, making sure everything is up to date. If you want to double check this, just tell me what info to post, I'll gladly do so.
I can't do anything ADB without this. Help?
Click to expand...
Click to collapse
Quick Question! Are you trying to connect with a MAC or a Windows Computer? Oh... you said Laptop XP SP3... this is not the problem. You know how I made it work on a ViewPad7 connected to a Mac? Activating the USB Tethering...
Can you try if activating the USB Tethering the ADB is able to see your device?
Make sure you have installed the drivers first (adb driver + phone drivers) .... check that in Administrative Tools -> Computer Management (%windir%\system32\compmgmt.msc /s) -> Device Manager -> check if any devices with an ! mark on them, it means the driver for that device is not properly installed.
Right... Well, small new update, and sorry that I haven't responded in a while. Kinda hard to get internet lately.
Anyways, I got a hold of another phone I'd rooted a while back, and decided to test that device. ADB DEVICES worked perfectly for it, but it still can't detect mine. There's no unidentified devices on my laptop's Device Management.
Help?
*sighs* Bump!
http://org.downloadcenter.samsung.c...113815/T-Mobile_T769_Blaze_4G_USB_Drivers.exe
22.8MB file installing slowly?
First off, I apologize for being paranoid. I downloaded this file and started installing it. It's a 22.8 MB .exe file. I started installing, and it *seems* to be working correctly. After clicking install MSS Installation Wizard is installing Samsung USB Driver for Mobile Phones V1.3.2200.0. Slightly after, desktop toolbar icon popped up Installing device driver software, opened it up showing:
USB Composite Device Ready to use
USB Mass Storage Ready to use
CDC Cerial Waiting for user input
Samsung LTE USB Device Ready to use
Samsung LTE Card USB Device Ready to use
It's been like 10-15 minutes and the MSS Installation Wizard is chugging along, at about 50%. Is this file legit? Is it just my slow ass computer that is making this install take forever? Have other successfully installed this for ADB usage?
Looks to just be the link to Samsung, which yes I have installed. It was a bit slow on my netbook.
Sent from my SGH-T769 using Tapatalk 2
Same here. I installed it yesterday while working on my wife's phone (Blaze also). The first time I tried to install it on my desktop it was slow and there was some sort of error. I had to reboot and redo it before I got it properly installed.
I've never needed the drivers, just downloaded kies.
Sent from my SGH-T769 using XDA
Kies I think installs the drivers for you. You can't properly use the device without the drivers and you definitely cannot use some of the tools without them.
No ADB
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Does anyone know how to get this device working with adb on Debian? I can't for the life of me get the device recognized by adb. I have a 51-android.rules set up and all that jazz. udev sees it and rules are applied properly. I just can't get it recognized. It seems references to accessing this device from Linux are very few and far between. What gives?
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
strungoutfan78 said:
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
Click to expand...
Click to collapse
Can you explain this a bit more, like where to input these commands. Im a bit green and having this issue.
---------- Post added at 01:25 AM ---------- Previous post was at 01:04 AM ----------
theshowman said:
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Click to expand...
Click to collapse
I tried the #7284# and #9090# and got "unable to process request"
any other suggestions?
I tried searching everywhere and was not able to find a solution.
When I run it, the following texts appear and then hangs indefinitely.
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
From what I've found after searching, people have solved it by reinstalling driver, but it does not work for me.
I set both the security setting and USB debug setting, and driver is correctly installed.
I also tried following this video tutorial (http://forum.xda-developers.com/showthread.php?t=1798586), but that is pretty much what I did in the first place and that Debugfs hangs at the same spot.
I am new to an Android device. I own an iPhone which I jailbroke, but I am moving away from Apple. All I am trying to do right now is trying to change the dock keyboard layout, which apparently requires rooting.
Any help would be appreciated.
The text is fine, but it should go from there smoothly. Do you have ASUS sync installed and running? If so, kill it and kill it with a heavy stab.
Does your PC recognise the Infinity when you plug in the USB cable?
d14b0ll0s said:
The text is fine, but it should go from there smoothly. Do you have ASUS sync installed and running? If so, kill it and kill it with a heavy stab.
Does your PC recognise the Infinity when you plug in the USB cable?
Click to expand...
Click to collapse
ASUS sync is not installed on my computer and it's disabled on the tablet. My computer recognizes it when it's connected.
Sounds like a classic "it should work" situation.
Try it on a different PC perhaps. You may have some third-party software installed that's interacting with the adb. Hard to tell without looking into it really. When you try to use custom commands in adb, not the .bat file, does anything work? What does waiting for device report?
^^^ this
I know this from experience, that not all Windows PC's are created equal. I had an issue rooting my tablet on 2 Windows XP machines and one Windows 7. The final Windows 7 machine I tried magically worked. All had admin access and no restrictions.
qnfauf said:
I tried searching everywhere and was not able to find a solution.
When I run it, the following texts appear and then hangs indefinitely.
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
From what I've found after searching, people have solved it by reinstalling driver, but it does not work for me.
I set both the security setting and USB debug setting, and driver is correctly installed.
I also tried following this video tutorial (http://forum.xda-developers.com/showthread.php?t=1798586), but that is pretty much what I did in the first place and that Debugfs hangs at the same spot.
I am new to an Android device. I own an iPhone which I jailbroke, but I am moving away from Apple. All I am trying to do right now is trying to change the dock keyboard layout, which apparently requires rooting.
Any help would be appreciated.
Click to expand...
Click to collapse
If you have adb setup properly you should be able to type "adb devices" from a command prompt. If all is well you will see your tablets serial number listed. If adb isn't setup properly, well you won't see anything.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Thanks for all the help. I don't really have another computer I can use right now.
newellj79 said:
If you have adb setup properly you should be able to type "adb devices" from a command prompt. If all is well you will see your tablets serial number listed. If adb isn't setup properly, well you won't see anything.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
When I type "adb devices", it says
"List of devices attached" and two blank lines. I guess adb does not see my device. Am I doing something wrong?
I am having the *exact* same issue. I'm not sure what the deal is - I recently used ADB to root my SGS3 so it definitely boggles my mind as to why it's not working on my tablet.
Just wanted you to know you weren't the only one. I'm going to try reinstalling ADB drivers later tonight to see if maybe something is wrong on that front...
---------- Post added at 09:26 PM ---------- Previous post was at 09:15 PM ----------
Okay, let me explain how I got this to work.
First of all, the xda post you referenced has a link to a bad set of drivers. (Don't worry, it got me too at first, shame on that XDA poster for stealing credit in the first place...)
So, go here (http://forum.xda-developers.com/showthread.php?t=1706588) and download the ASUS Android Drivers USB.zip as well as as the rootdebugfs that is there.
Next, open your device manager - the reason I keyed into this is because there was a driver that said "ASUS Android Composite ADB Interface" that did not install properly. Unzip the ASUS Android Drivers and then right click on "ASUS Android Composite ADB Interface" and update the drivers, manually point to the folder that contains all of the ASUS Android Drivers and click ok, it should update your drivers CORRECTLY (You'll get a successfully updated drivers window). After that try using the rootdebugfs bat again, worked like a charm for me after that!
If you're still having issues, please let me know, and post a screenshot of your device manager if you don't mind, it could be the key to your issues as well.
Sorry for the long post, hope I made sense
Forcepath said:
I am having the *exact* same issue. I'm not sure what the deal is - I recently used ADB to root my SGS3 so it definitely boggles my mind as to why it's not working on my tablet.
Just wanted you to know you weren't the only one. I'm going to try reinstalling ADB drivers later tonight to see if maybe something is wrong on that front...
---------- Post added at 09:26 PM ---------- Previous post was at 09:15 PM ----------
Okay, let me explain how I got this to work.
First of all, the xda post you referenced has a link to a bad set of drivers. (Don't worry, it got me too at first, shame on that XDA poster for stealing credit in the first place...)
So, go here (http://forum.xda-developers.com/showthread.php?t=1706588) and download the ASUS Android Drivers USB.zip as well as as the rootdebugfs that is there.
Next, open your device manager - the reason I keyed into this is because there was a driver that said "ASUS Android Composite ADB Interface" that did not install properly. Unzip the ASUS Android Drivers and then right click on "ASUS Android Composite ADB Interface" and update the drivers, manually point to the folder that contains all of the ASUS Android Drivers and click ok, it should update your drivers CORRECTLY (You'll get a successfully updated drivers window). After that try using the rootdebugfs bat again, worked like a charm for me after that!
If you're still having issues, please let me know, and post a screenshot of your device manager if you don't mind, it could be the key to your issues as well.
Sorry for the long post, hope I made sense
Click to expand...
Click to collapse
Thank you, that worked!
In the process of trying to get it to work, I definitely saw "ASUS Android Composite ADB Interface" a few times in device manager. After reading your post, I could not get it to show. I tried uninstalling the driver, searching for new hardware, etc. to no avail. However, switching the USB connection type from MTP to PTP while the device manager was running (I'm not sure why it had to be running) made it show up. Then I used the correct driver files to install the driver and the root worked. That guy who put up the video tutorial apparently put wrong drivers.
mtp to ptp
qnfauf said:
Thank you, that worked!
In the process of trying to get it to work, I definitely saw "ASUS Android Composite ADB Interface" a few times in device manager. After reading your post, I could not get it to show. I tried uninstalling the driver, searching for new hardware, etc. to no avail. However, switching the USB connection type from MTP to PTP while the device manager was running (I'm not sure why it had to be running) made it show up. Then I used the correct driver files to install the driver and the root worked. That guy who put up the video tutorial apparently put wrong drivers.
Click to expand...
Click to collapse
switching from mtp to ptp fixed it for me. it caused the device manager see an new device, which then had a yellow triangle. i just right clicked on it and hit refresh, and it installed the driver. g2g after that.
I had same problem but its solved now n its just drivers problem
just google "phones_brand_name usb drivers"
download and install them
n you are done
Firstly, thank you for this great forum! I've already found a lot of great info on here, and love my new phone. I was trying to get drivers on my PC to start rooting my phone, but now that I can't even do that, I'm unsure that I should even be trying to root at all. Most, if not all of the driver's links that I've found here are dead so I tried a few other methods: Plugging in the phone after selecting USB debugging. Windows searched for drivers automatically, but found none. Downloaded HTC Sync, but it doesn't recognize my phone. I'm confused because I was already able to transfer my mp3's to the SD card via usb, but otherwise it seems like my phone isn't recognized.
My HBoot is the 1.45.0013, so I take it that it can't easily be turned S-off, but I probably don't need that anyway for what I want. I simply want to be able to remove all of the bloatware, and have access to functions like CPU control. For just that, I think that rooting while S-on will be fine?
I know that this is an old phone, but I bought it because the specs are still quite good, and I was able to get it brand new on Amazon for a song...............I would hope that there are at least drivers still available for it. Thanks for any help in advance!
~E
ericdg said:
Firstly, thank you for this great forum! I've already found a lot of great info on here, and love my new phone. I was trying to get drivers on my PC to start rooting my phone, but now that I can't even do that, I'm unsure that I should even be trying to root at all. Most, if not all of the driver's links that I've found here are dead so I tried a few other methods: Plugging in the phone after selecting USB debugging. Windows searched for drivers automatically, but found none. Downloaded HTC Sync, but it doesn't recognize my phone. I'm confused because I was already able to transfer my mp3's to the SD card via usb, but otherwise it seems like my phone isn't recognized.
My HBoot is the 1.45.0013, so I take it that it can't easily be turned S-off, but I probably don't need that anyway for what I want. I simply want to be able to remove all of the bloatware, and have access to functions like CPU control. For just that, I think that rooting while S-on will be fine?
I know that this is an old phone, but I bought it because the specs are still quite good, and I was able to get it brand new on Amazon for a song...............I would hope that there are at least drivers still available for it. Thanks for any help in advance!
~E
Click to expand...
Click to collapse
ADBSetup will get you the drivers you are looking for:
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Worked for any Android phone I tried.
Thanks, I'll give that a shot and see what happens!
Okay, I installed the driver from ADB, but still can't get HTC Sync to work...........................from reading other threads, it sounds like that's a common issue, though. Is there any way to confirm that I have the drivers installed? Under "devices and printers" on my PC, it will recognize an android phone when the phone is set to disk drive or charge only, but not USB tethering. When I switch the phone to the tethering option, the phone's icon on the PC moves from devices to unspecified. Then when I hover over it, it says there's no drivers. Again, I'm in debugging mode and have already copied MP3's to the SD, but I'd just like to confirm whether or not I have the needed drivers before starting the root process.
Thanks,
~E
ericdg said:
Okay, I installed the driver from ADB, but still can't get HTC Sync to work...........................from reading other threads, it sounds like that's a common issue, though. Is there any way to confirm that I have the drivers installed? Under "devices and printers" on my PC, it will recognize an android phone when the phone is set to disk drive or charge only, but not USB tethering. When I switch the phone to the tethering option, the phone's icon on the PC moves from devices to unspecified. Then when I hover over it, it says there's no drivers. Again, I'm in debugging mode and have already copied MP3's to the SD, but I'd just like to confirm whether or not I have the needed drivers before starting the root process.
Thanks,
~E
Click to expand...
Click to collapse
Easiest way to tell is open up a command prompt in the folder that adbsetup installed to (C:\ADB I think) and type:
Code:
adb devices
If all is well, then the device will be part of the listing.
Thanks Joel.............I think it worked.
The ADB command came back with:
List of devices attached
HT22_______7 device
That's not a number that I've ever seen associated with my phone, but I assume that's it.
Confirmed.................I was able to reboot the phone by ADB!
Excellent! This will also mean the fastboot commands needed to unlock your bootloader will work too.
.........one would think so, Joel, but I can't get fastboot to do anything. ADB recognizes the phone, and will reboot into bootlocker, but once there it'll do nothing. Windows pops up a message shortly after bootlocker opens that says something to the effect of "there was a problem with USB device not recognized". I tried the command "fastboot devices", but got nothing. I know that I'm darned close, and it's probably something simple, but just can't get it to work. Maybe I need additional drivers for fastboot, or need to move it to another directory?
Thanks,
~E
Interesting. Try this:
Go into fastboot mode on the device, with the USB cable plugged in. On the computer, open up device manager. What is read for Android Device? Is there a noted problem with the driver? Open the properties for that device, and select Update Driver. The search process should find something appropriate now (as ADB Setup saves the drivers in the system32 folder - I think).
If not, what kind of user did you run ADBsetup as? If it was one without admin privileges, try installing again as admin (this allows the drivers to be saved where you want them to be).
If there are still problems, unfortunately I cannot think of anything else.
joel.maxuel said:
Interesting. Try this:
Go into fastboot mode on the device, with the USB cable plugged in. On the computer, open up device manager. What is read for Android Device? Is there a noted problem with the driver? Open the properties for that device, and select Update Driver. The search process should find something appropriate now (as ADB Setup saves the drivers in the system32 folder - I think).
If not, what kind of user did you run ADBsetup as? If it was one without admin privileges, try installing again as admin (this allows the drivers to be saved where you want them to be).
If there are still problems, unfortunately I cannot think of anything else.
Click to expand...
Click to collapse
I'm almost sure that the problem lies with the drivers now, but just don't know how to fix it!?! In device manager the phone moves into different categories, depending on the connection type; Charge only, and disk drive both work fine, but the icon for tethering shows no drivers installed. After rebooting into bootlocker the phone automatically switches to tethering, so I assume that's needed for getting root. I can't install drivers when the phone's in tethering from device manager, with either auto or manual. It just won't take! I've tried re-installing HTC sync, removing and re-installing multiple driver files, and the phone's just not being recognized. The sync instructions say that it should be a connection option on the phone also, but I've only ever seen the three: charge, disk, and tether. As for user, I'm pretty sure that I did install ADB as admin...............not sure how to check for that now, but the drivers are not in system32 like you mentioned; they're in program files (x86). Maybe the location of the drivers is the only problem I'm having, but I don't know where I want them to be? I hate quitters, but soon I'll just be enjoying the stock ROM for the best of it, if these problems persist!
Thanks,
~E
ericdg said:
I'm almost sure that the problem lies with the drivers now, but just don't know how to fix it!?! In device manager the phone moves into different categories, depending on the connection type; Charge only, and disk drive both work fine, but the icon for tethering shows no drivers installed. After rebooting into bootlocker the phone automatically switches to tethering, so I assume that's needed for getting root. I can't install drivers when the phone's in tethering from device manager, with either auto or manual. It just won't take! I've tried re-installing HTC sync, removing and re-installing multiple driver files, and the phone's just not being recognized. The sync instructions say that it should be a connection option on the phone also, but I've only ever seen the three: charge, disk, and tether. As for user, I'm pretty sure that I did install ADB as admin...............not sure how to check for that now, but the drivers are not in system32 like you mentioned; they're in program files (x86). Maybe the location of the drivers is the only problem I'm having, but I don't know where I want them to be? I hate quitters, but soon I'll just be enjoying the stock ROM for the best of it, if these problems persist!
Thanks,
~E
Click to expand...
Click to collapse
Dont know where you got your HTC drivers, but you should try the ones in this post (step one - hopefully its still live - if not I can dropbox it for you):
http://forum.xda-developers.com/showthread.php?t=1801106
Sent from my LG-D520 using XDA Free mobile app
You're awesome, Joel!
That is the thread that I've been using predominantly, but I found that link to the drivers dead. I sourced them elsewhere, but couldn't really say where exactly since I've tried so many now. If you could dropbox for me, I'd really appreciate it.
ericdg said:
You're awesome, Joel!
That is the thread that I've been using predominantly, but I found that link to the drivers dead. I sourced them elsewhere, but couldn't really say where exactly since I've tried so many now. If you could dropbox for me, I'd really appreciate it.
Click to expand...
Click to collapse
Uh-oh. Either the link was dead when I went through this process back in April, or I had bad organizing skills at one point and didn't put the file in the Doubleshot folder before completing a purge. Either way, I don;t have the file.
Nor did I really need it. The second Doubleshot I rooted I ended up using it in my native Linux environment (no drivers needed), vs my Windows XP emulated through VirtualBox. That's what you could do. Get a live Debian DVD (Im like the XFCE desktop version), boot in, get fastboot:
Code:
sudo apt-get install fastboot
And then use fastboot:
Code:
sudo fastboot ...
Thanks for the link and instructions; I'll probably not be able to try this for a couple of days now................just super busy, but I'll let you know how it went (or, more likely, have questions)! Any linux stuff is completely foreign to me, but it looks fairly straightforward. One question about the link that you provided, though: It looks like an index of a lot of individual files that I'd need. Under the parent directory, the folder named "iso-hybrid/ " is what I want, correct? I do really appreciate your time and help, Joel.....with as many dead links and outdated drivers that I've found, I don't think I could've got root otherwise!
~E
ericdg said:
Thanks for the link and instructions; I'll probably not be able to try this for a couple of days now................just super busy, but I'll let you know how it went (or, more likely, have questions)! Any linux stuff is completely foreign to me, but it looks fairly straightforward. One question about the link that you provided, though: It looks like an index of a lot of individual files that I'd need. Under the parent directory, the folder named "iso-hybrid/ " is what I want, correct? I do really appreciate your time and help, Joel.....with as many dead links and outdated drivers that I've found, I don't think I could've got root otherwise!
~E
Click to expand...
Click to collapse
Just need the one. My recommended file to download is this:
http://cdimage.debian.org/debian-cd...ybrid/debian-live-7.6.0-i386-xfce-desktop.iso
Burn the image (not the file) onto a DVD (can be a rewritable) and reboot with the disc in the drive. Once it's fully loaded, you can either enter commands by clicking on the "terminal" icon on the bottom of the screen (preferred), or press Ctrl + Alt + F1 to get a prompt (may have to log in as "user", there shouldn't be a password). Hope this helps.
For years, I struggled to get ADB/FASTBOOT installed and working. I've succeeded fairly often but usually have a success/failure ratio of one hundred to one. I'm currently trying it again, so thought I'd make a request for info from someone more experienced than myself.
First of course, is USB Debugging enabled. Done.
Then install OEM USB drivers; in my case Samsung.
Finally install the "short" version of Android SDK Development tools (just adb and fastboot but nothing else).
Am I missing something? I usually have to keep "hacking and whacking" at the damn thing until I finally stumble upon the correct combination of components.
And of course different cables, different computers, different Windows versions, etc, etc, etc ad nauseum.
I even reinstalled Windows 7 for a "fresh" PC and EVEN that did not help.
SO.......... Anyone have any ideas what works "first time, every time". I'm desperate.
Boowho??
boowho said:
For years, I struggled to get ADB/FASTBOOT installed and working. I've succeeded fairly often but usually have a success/failure ratio of one hundred to one. I'm currently trying it again, so thought I'd make a request for info from someone more experienced than myself.
First of course, is USB Debugging enabled. Done.
Then install OEM USB drivers; in my case Samsung.
Finally install the "short" version of Android SDK Development tools (just adb and fastboot but nothing else).
Am I missing something? I usually have to keep "hacking and whacking" at the damn thing until I finally stumble upon the correct combination of components.
And of course different cables, different computers, different Windows versions, etc, etc, etc ad nauseum.
I even reinstalled Windows 7 for a "fresh" PC and EVEN that did not help.
SO.......... Anyone have any ideas what works "first time, every time". I'm desperate.
Boowho??
Click to expand...
Click to collapse
What are you trying to do with ADB
([emoji3590]09-09-18[emoji3590])
boowho said:
For years, I struggled to get ADB/FASTBOOT installed and working. I've succeeded fairly often but usually have a success/failure ratio of one hundred to one. I'm currently trying it again, so thought I'd make a request for info from someone more experienced than myself.
First of course, is USB Debugging enabled. Done.
Then install OEM USB drivers; in my case Samsung.
Finally install the "short" version of Android SDK Development tools (just adb and fastboot but nothing else).
Am I missing something? I usually have to keep "hacking and whacking" at the damn thing until I finally stumble upon the correct combination of components.
And of course different cables, different computers, different Windows versions, etc, etc, etc ad nauseum.
I even reinstalled Windows 7 for a "fresh" PC and EVEN that did not help.
SO.......... Anyone have any ideas what works "first time, every time". I'm desperate.
Boowho??
Click to expand...
Click to collapse
As long as you have the complete USB drivers for your device, USB debugging enabled and the adb 15 second installer installed on PC, it should work. When you connect your device to adb, you "should" get a prompt or notification on your device to allow adb access, if you do, grant it permission.
If you're trying to use fastboot on a Samsung device, you can give up on that notion, Samsung devices can't use fastboot for anything, it isn't compatible at all, you will never get it to work.
But...
ADB works just fine on Samsung.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
As long as you have the complete USB drivers for your device, USB debugging enabled and the adb 15 second installer installed on PC, it should work. When you connect your device to adb, you "should" get a prompt or notification on your device to allow adb access, if you do, grant it permission.
If you're trying to use fastboot on a Samsung device, you can give up on that notion, Samsung devices can't use fastboot for anything, it isn't compatible at all, you will never get it to work.
But...
ADB works just fine on Samsung.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks so much for your thoughts/reply. I found last night that stripping ALL previously installed USB drivers and re-installing the Samsung USB drivers got it working. I plugged the device in BEFORE installing Sammy's drivers and it showed in device manager (without a driver, of course). I then installed the drivers and it connected. At that point ODIN worked just fine. Then I did an "adb devices" and it responded as it should.
For me, all these "packages" (Like 15 second installer or something) with .bat files, etc are not needed at all for ADB and just make things more confusing.
Just the two executables and three .DLL files make ADB and fastboot work in windows; IF you have previously installed Sammy's drivers as mentioned above.
Finally, not to disagree with you (after all it was ME who came here looking for help), but FASTBOOT works just fine on my Samsung device (a Gear Live Watch). I have to use the command "adb reboot bootloader". The watch reboots and from there all fastboot commands seem to work just fine. I flashed several .img files that way.
It's possible (I suppose) that no other Sammy device will accept fastboot, because supposedly Sammy wasn't even involved in creating the firmware for that watch. Google did it ALL.
Oh, and one last thing..... Yes I HAD it all working, but now ADB devices shows the device as "unauthorized". It did not when I first did the ADB devices, but instead put up the popup asking for permission. Now it just says unauthorized and fails to popup the little message
I've gone thru all the "fixes" for this that I can find for this particular problem, but so far no joy.
Maybe it's just me, but setting up ADB/fastoot as ALWAYS been a pain is the ass.
Boowho??
boowho said:
Thanks so much for your thoughts/reply. I found last night that stripping ALL previously installed USB drivers and re-installing the Samsung USB drivers got it working. I plugged the device in BEFORE installing Sammy's drivers and it showed in device manager (without a driver, of course). I then installed the drivers and it connected. At that point ODIN worked just fine. Then I did an "adb devices" and it responded as it should.
For me, all these "packages" (Like 15 second installer or something) with .bat files, etc are not needed at all for ADB and just make things more confusing.
Just the two executables and three .DLL files make ADB and fastboot work in windows; IF you have previously installed Sammy's drivers as mentioned above.
Finally, not to disagree with you (after all it was ME who came here looking for help), but FASTBOOT works just fine on my Samsung device (a Gear Live Watch). I have to use the command "adb reboot bootloader". The watch reboots and from there all fastboot commands seem to work just fine. I flashed several .img files that way.
It's possible (I suppose) that no other Sammy device will accept fastboot, because supposedly Sammy wasn't even involved in creating the firmware for that watch. Google did it ALL.
Oh, and one last thing..... Yes I HAD it all working, but now ADB devices shows the device as "unauthorized". It did not when I first did the ADB devices, but instead put up the popup asking for permission. Now it just says unauthorized and fails to popup the little message
I've gone thru all the "fixes" for this that I can find for this particular problem, but so far no joy.
Maybe it's just me, but setting up ADB/fastoot as ALWAYS been a pain is the ass.
Boowho??
Click to expand...
Click to collapse
Samsung gear doesn't count, as you said, Samsung doesn't have anything to do with creating the firmware. I would think that any android device that Samsung had it's part in making firmware for, doesn't work with fastboot. But, devices that are Samsung "in name" only, may be compatible with fastboot. The question is, is it really a Samsung or is it just wearing the Samsung name?
Sent from my SM-S767VL using Tapatalk