Database Info

ADB USB Driver

the USB driver for windows is available at:
http://dl.google.com/android/android_usb_windows.zip
It seems to work... I will update this thread with what I find.

Thanks for posting the driver!
I've tried a few things with adb, and so far I can't get an install to work over usb. I tried the following command.
C:\...\android-sdk-windows-1.0_r1\tools>adb install OperaMini.apk
579 KB/s (0 bytes in 278155.000s)
pkg: /data/local/tmp/OperaMini.apk
Failure [INSTALL_PARSE_FAILED_MANIFEST_MALFORMED]
Click to expand...
Click to collapse
http://www.android-freeware.org/tutorial/how-to-install-apk-files-on-android-device-emulator Had some basic info about the emulator, not sure what would be different for the G1.
The "adb shell" option allows you to access a shell on the phone over USB, which is really great but it appears you don't have root privileges. Any ideas on how to obtain root priveleges? Also, is there a command to install from the android shell? When i cd to /sbin i get access denied. I'm trying to figure out some kind of way to invoke an install either from the device or over USB.

I have the same problem... working on it now...

I don't know about the USB installs, but it seems to be something with the APK as well. I also have the OperaMini.apk and it does nothing. I downloaded the iTunes remote via the G1 and it installed just fine without getting a PC involved.

It looks like you have to put the phone into a "Debug on USB" mode to use ADB. It's working for me now.
http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware

So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on

Thank you dagentooboy!

Can someone explain this for this not so savvy person?

chrimage said:
So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on
Click to expand...
Click to collapse
I think that is caused by an issue with the the AndroidManifest.xml file within the APK having to do with going from "beta" to "live" Android. The same reason most of the apps were pulled from the store. I don't believe it takes a major change to make it compatible, but it's fully compiled so, unless you have a decompiler, I think we may be out of luck on that particular one. I have installed other apk's successfully using the same method.

Mikey1022 said:
Can someone explain this for this not so savvy person?
Click to expand...
Click to collapse
ADB is the Android Debug Bridge that comes as a part of the SKD. I don't think it was really intended as an end user tool. It has to be called from a command line. I know people have built basic UI's for it for file manipulation when the SDK was the only thing out there. If a better solution isn't found shortly I think we'll see one be made, or else I'll make one myself. In the end it seem to make a big difference of what you're trying to install some things work and some don't, there are some differences between the beta SDK and the G1.

For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?

Valicore said:
For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?
Click to expand...
Click to collapse
the su command and sudo su returns "no permission" or "access denied" or something like that. That is also the same message i get when typing arbitrary commands that shouldn't be anything. And like i said earlier, /sbin along with many other directories are inaccessible. Hopefully someone will find a way to access the root account on the G1 pretty soon.

yes... must... have.... root...
Also a normal shell would be helpful esp when looking thru /proc/ for information.

Please help (ahhhhhh)
Okay So I am pulling my hair out here... I just booted android on my Vogue for the first time, everything works great, voice calls and sms.. But I can get a Inet connection but I am using Cricket not sprint so I added the username and password lines in default.txt and can connect, but Cricket uses a proxy for all http connections. So I found this article http://fggarcia.blogspot.com/2007/11/setting-up-proxy-for-android-emulator.html , which basicly says to use the adp app that comes in the sdk to add some lines to make the proxy. NOW, here is my problem... I can not for the life of me get my come (in windows or linux) to see my vogue while its in android..
In windows it does not appear ANYWHERE in the device manager... So I cannot install the driver, and in Linux it doesnt make a blip in dmesg..... USB debugging is marked and so is use adb....
It does charge when plugged in to the comp running linux.....
Can anyone please help me... And thanks to DZO and everyone else for there hard work on this project..

check too make sure your Android isnt listed under usb mass storage devices in device manager.

Ya USB isn't possible on Vogue yet, I just extracted data.img and added the proxy that way, but it still doesn't work. My Problem is I need all connection to use the proxy wap.mycricket.com:8080. I am not trying to be cheap or anything like the tzones thing for tmobile. Its just the only data plan cricket have use this proxy. So any Ideas would be greatly appreciated.

my computer already had a driver installed and when i try to update it with this one it says there is no better match for my hardware
anyone got a solution for this

Im really sorry to bump this old thread up but i need the r3 drivers and i dont know why they are nowhere to be found on the official page... i think its a region lock thing...

[Q] ADB, RSA, Android 4.2.2, Android Commander

http://www.youtube.com/watch?v=JmvCpR45LKA
I have seriously searched EVERY DAMN INCH of the Internet for this. Okay, obviously, I've seen all the posts like this one:
http://forum.xda-developers.com/showthread.php?t=2351390 (I actually wanted to reply there but can't, sad)
And I've done all those steps, I've uninstalled everything, I've reinstalled everything, I've called my mom to tell her she wasn't lying to me about me being special, I've done it all ten times. This is what happens:
System stuff: Windows XP, cyanogenmod 10, ADB and Apps set to root, USB debugging on, Android 4.2.2, latest Android Commander, Galaxy S3 Sprint, Android Debug Bridge version 1.0.31
I open cmd and type adb devices, it shows me a device is available:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
ba0a8be4 device
I open Android Commander, it has a blank line that's highlighted blue, I click "OK", it says:
Connected device has status offline and cannot be used. Please reboot your device.
I reboot my device, same thing happens.
Does anyone have any ideas? I'm seriously about to just flash it to 421 but I hate just giving up. I hate it almost as much as I hate asking for help. I spent 7 hours last night (I was up until 2am!!) and then another 4 or 5 today just trying to figure this out. I'm completely lost here. Oh, another thing, since I'm at it, does anyone know how to delete the saved RSA key from my phone? I looked in that data/adb place that link said and renamed it but it didn't seem to reset the key... maybe I need to restart, I'll try restarting after I rename it. Yep, I bet that'll work. It probably had it in memory. Anyway, pointless rant about RSA done. I hope someone has some ideas before I resort to just sitting in the corner, cuddling up with my phone, and crying until my mommy tells me I'm special.
Another possibly important thing is that Droid Explorer works briefly (I can see phone's files come up) but then crashes when I try opening anything.
It also, as I was just playing with it, seems like Android Commander causes the adb server to become outdated. Does that mean anything? I just ran adb devices, then tried AC, then did adb dev again and it needed to restart the service. I don't know if that means anything. Just something I noticed.
Oops I had to update the link, I just realized I copied the wrong one from the page suggestions it does. This now has the one I meant.

Did you find a solution? I am having the same problem.

I gave up. Flashed stock, then cm 10 with system and cache wipes then cm 10.1 without wiping system. Haven't tried with my computer since I mostly use my phone. I'll check later and update this and let you know. I would have just kept stock but my god that stuff sprint puts on sickens me......

I found a solution and it works.
http://forum.xda-developers.com/showpost.php?p=40276190&postcount=1488

Yeah, I even said in my message that I made sure that was up to date. I was able to connect to adb and see it show up as a device now but Android Commander doesn't work. I did find out that adb push (and I assume pull) works but that probably worked before and I just didn't try. Anyway, I'm not too concerned. Glad you got yours figured out.

Hope this helps!
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!

lukesheardown said:
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!
Click to expand...
Click to collapse
Copying the adb files to the bin directory worked for me, thanks!

[Q] Too dumb to even get drivers!?!

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.

Bootloader unlock and root help?

Hi all, first off im not a complete noob, I've rooted/bootloader unlocked a few phones, jailbroken apple devices etc... but this issue has me pulling my hair out now. Apologies if im in the wrong section of the forum.
So, i'm trying to unlock my bootloader on the OnePlus One using ADB through the Android SDK and i'm having several issues.
1 i cant get my phone to be recognised as an ADB device, have installed every single driver i can find anywhere, and none of it works, my phone has the necessary Developer Options enabled.
2 the Android SDK doesn't actually open for longer than a fraction of a second, i have tried multiple Java SDK's to direct the Android.bat file at, nothings happening for me.
3 i installed Eclipse to open the SDK in, Eclipse doesn't even open, it freezes
Im using Windows 10 on a HP630 laptop. Been trawling through the XDA forums among other forums and websites and im yet to find a solution, im about to try installing JDK 1.7 xxxx to see if i can redirect Android.bat to that version of the Java.exe
I'm aware of the process i have to go through to unlock my bootloader, its just i cant actually get the Android SDK to open, my phone to be picked up as an ADB device, and using Windows button +R to open ADB interface does absolutely nothing either, it flashes on for a fraction of a second and its gone again.
I'd appreciate any help anyone can offer me, im tempted to throw my laptop through the window.

JohnCSElwell said:
Hi all, first off im not a complete noob, I've rooted/bootloader unlocked a few phones, jailbroken apple devices etc... but this issue has me pulling my hair out now. Apologies if im in the wrong section of the forum.
So, i'm trying to unlock my bootloader on the OnePlus One using ADB through the Android SDK and i'm having several issues.
1 i cant get my phone to be recognised as an ADB device, have installed every single driver i can find anywhere, and none of it works, my phone has the necessary Developer Options enabled.
2 the Android SDK doesn't actually open for longer than a fraction of a second, i have tried multiple Java SDK's to direct the Android.bat file at, nothings happening for me.
3 i installed Eclipse to open the SDK in, Eclipse doesn't even open, it freezes
Im using Windows 10 on a HP630 laptop. Been trawling through the XDA forums among other forums and websites and im yet to find a solution, im about to try installing JDK 1.7 xxxx to see if i can redirect Android.bat to that version of the Java.exe
I'm aware of the process i have to go through to unlock my bootloader, its just i cant actually get the Android SDK to open, my phone to be picked up as an ADB device, and using Windows button +R to open ADB interface does absolutely nothing either, it flashes on for a fraction of a second and its gone again.
I'd appreciate any help anyone can offer me, im tempted to throw my laptop through the window.
Click to expand...
Click to collapse
Uninstall all other drivers and android sdk.
https://forum.xda-developers.com/showthread.php?t=2788632
Use this guide and all will be fine.

[Q] setting up adb

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