Related
ok so i have done lots and lots of research on this because as it turns out you need the android sdk for just about everything.. i dont know if it is just me or im not reading sumthin correctly or i jus dont understand but i read the instructions over and over agen on how to install this dam thing and it never works.. can somebody please help me intall this?
Lot of people install it so it does work. The trick is uninstalling the windows driver and replacing it with the adb driver. I assume that's what you want to use. "Install" I think is the wrong word to use, because you don't install anything in the sdk except the driver.
cd to the path of adb.exe in the command prompt. The inital command is 'adb devices' it will show the serial number so you know the phone is detected.
i type that in the cmd and it just says list of devices attached then theres nuthin attached to it.. i read through the instructions on the android website several times and all it really tells me about getting the sdk is adding the full path to the tools\ directory path.. i did this and then what do i do after?
Did you activated "debugging" in USB-Options?
on the phone or on the pc? i have it turned on on my phone but if that is even possible to do on a pc then no i dont...
I have my 2.1 DamageControl ROM running fine (thx damage!). I'm just trying to connect to adb. I'm on win7, 64bit.
I used to connect fine when I was on fresh 1.1.
I thought it was b/c I had an outdated sdk, which I did. I upgraded from v3 to v5, and made sure I downloaded all the latest, including the latest usb driver.
I also checked to make sure I have HTC sync 2.08.
but I just keep getting this.
C:\android-sdk-windows\tools>adb remount
error: device not found
Click to expand...
Click to collapse
anyone else getting this issue, or know the solution?
Try this. It worked for me with Windows 7.
http://theunlockr.com/2009/10/06/how...droid-devices/
I started at Step II. Reinstall Drivers since I already had the SDK.
crunchybutternut said:
Try this. It worked for me with Windows 7.
http://theunlockr.com/2009/10/06/how...droid-devices/
I started at Step II. Reinstall Drivers since I already had the SDK.
Click to expand...
Click to collapse
Link no worky.
I had this same problem. Go into your device manager and reinstall your ADB driver. If you're in the same situation I was in, it'll have a "!" on the ADB item in your list. Right click ADB, update driver, pick from a list of available drivers... or something like that. In the list it gives you, you should see something along the lines of "Android ADB Interface." Pick that... it may give you some kind of warning but install it anyway and you're done.
Try this,
adb kill-server
abd start-server
illogic6 said:
Link no worky.
I had this same problem. Go into your device manager and reinstall your ADB driver. If you're in the same situation I was in, it'll have a "!" on the ADB item in your list. Right click ADB, update driver, pick from a list of available drivers... or something like that. In the list it gives you, you should see something along the lines of "Android ADB Interface." Pick that... it may give you some kind of warning but install it anyway and you're done.
Click to expand...
Click to collapse
Ah hah.. thanks for the heads up. Here's the correct link. I also fixed my original post.
thanks for all the advice! I'll give them all a try.
This is what makes this website awesome. I'm glad everyone has come back together after all of that madness.
Tipharet said:
Try this,
adb kill-server
abd start-server
Click to expand...
Click to collapse
FYI, this one didn't work.
@crunchy - hm, I don't see any adb driver reference
I also went to device mgr in win7, and yeah, it has the !, but when I tried to update, it still failed. I even tried pointing to the usb driver folder in my android sdk, but it didn't like it. maybe something specific to win7 64bit?
Maybe I need to install the drivers manually? But what driver should I look for, for this Damagecontrol 2.1 ROM Sprint Hero now?
Did you make sure to enable debugging?
I don't have a link handy, but just go to the HTC support site for the Eris and download the latest HTC sync. It will fix your drivers, no fuss and straight forward.
smw6180 said:
Did you make sure to enable debugging?
Click to expand...
Click to collapse
Yes, tried with it off, and on. I also tried reinstalling HTC sync 2.08.
I didn't tell you to reinstall sync 2.0.8
Go here http://member.america.htc.com/download/Driver/DROID_ERIS_Verizon/HTCSync2.0.25.zip
And install THAT version of sync it has the proper drivers.
Think I told you to go to the Eris page by accident? Think again. Do it, fix your problem and let's all move on.
Sorry for being so blunt, just frustrated you that you wrote off my original suggestion, responding that you already tried reinstalling the same version of sync that wasn't working in the first place. If you paid attention to my first tip this would have already been solved.
obelisk79 said:
I didn't tell you to reinstall sync 2.0.8
Go here http://member.america.htc.com/download/Driver/DROID_ERIS_Verizon/HTCSync2.0.25.zip
And install THAT version of sync it has the proper drivers.
Think I told you to go to the Eris page by accident? Think again. Do it, fix your problem and let's all move on.
Sorry for being so blunt, just frustrated you that you wrote off my original suggestion, responding that you already tried reinstalling the same version of sync that wasn't working in the first place. If you paid attention to my first tip this would have already been solved.
Click to expand...
Click to collapse
actually, I didn't read your post yet when I posted my statement that I installed 2.08. I was responding to someone else. I'll try out your tip. thx.
obelisk79 said:
I didn't tell you to reinstall sync 2.0.8
Go here http://member.america.htc.com/download/Driver/DROID_ERIS_Verizon/HTCSync2.0.25.zip
And install THAT version of sync it has the proper drivers.
Think I told you to go to the Eris page by accident? Think again. Do it, fix your problem and let's all move on.
Sorry for being so blunt, just frustrated you that you wrote off my original suggestion, responding that you already tried reinstalling the same version of sync that wasn't working in the first place. If you paid attention to my first tip this would have already been solved.
Click to expand...
Click to collapse
Try your own link. It doesn't have a link to the Eris page.
EDIT: the joys of technology. When I used google chrome, the download link didn't work - when I used firefox, it did.
FYI, HTC sync 2.0.25 for the Eris didn't work.
ro_bro said:
Try your own link. It doesn't have a link to the Eris page.
googled and found it myself:
http://www.htc.com/us/support/droid-eris-verizon/downloads/
edit: ugh, the download link leads to a general support page again.
Click to expand...
Click to collapse
Must be a problem with the htc site, the link I provided was a direct link. I'll see if I can find another
Edit: now you do have some kind of weirdness going on. If that didn't work.
First make sure you have done the following... reboot pc and phone. Usb debugging enabled. Then connect phone attempt and shell and copy error here.
Also a question, did you install sync 2.0.8 prior to installing the 2.0.25version ?
A few other possible steps you could try.
Go to your start menu and type cmd one you see the cmd icon pop up in the menu rightclick and run as administrator. Then,
adb kill-server
adb start-server
adb shell
If you still get device not found try: adb devices and paste the output here.
obelisk79 said:
Must be a problem with the htc site, the link I provided was a direct link. I'll see if I can find another
Edit: now you do have some kind of weirdness going on. If that didn't work.
First make sure you have done the following... reboot pc and phone. Usb debugging enabled. Then connect phone attempt and shell and copy error here.
Also a question, did you install sync 2.0.8 prior to installing the 2.0.25version ?
A few other possible steps you could try.
Go to your start menu and type cmd one you see the cmd icon pop up in the menu rightclick and run as administrator. Then,
adb kill-server
adb start-server
adb shell
If you still get device not found try: adb devices and paste the output here.
Click to expand...
Click to collapse
Yes, I had 2.0.8 installed, but i uninstalled first before installing the 2.0.25. but I haven't tried the pc reboot, nor the kill server yet, I'll give those a try. thx!
obelisk79 said:
Must be a problem with the htc site, the link I provided was a direct link. I'll see if I can find another
Edit: now you do have some kind of weirdness going on. If that didn't work.
First make sure you have done the following... reboot pc and phone. Usb debugging enabled. Then connect phone attempt and shell and copy error here.
Also a question, did you install sync 2.0.8 prior to installing the 2.0.25version ?
A few other possible steps you could try.
Go to your start menu and type cmd one you see the cmd icon pop up in the menu rightclick and run as administrator. Then,
adb kill-server
adb start-server
adb shell
If you still get device not found try: adb devices and paste the output here.
Click to expand...
Click to collapse
This advice got me further... but here's what I get:
C:\>cd android-sdk-windows
C:\android-sdk-windows>cd tools
C:\android-sdk-windows\tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\android-sdk-windows\tools>adb kill-server
C:\android-sdk-windows\tools>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
C:\android-sdk-windows\tools>adb shell
error: device not found
C:\android-sdk-windows\tools>adb devices
List of devices attached
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
FYI, I still see a '!' beside my 'Android Phone' icon in my device manager.
Try to download and Install
HTC Sync Version 2.0.18 from HTC Support and it must work for you
Thanks
okay, I devoutly hope someone can help me here, because I'm at my wit's end with this. I'm using windows 7x64. I followed the instructions in THIS thread first(after installing the android sdk directly from the main website ), and got through everything okay, but when I try to do anything with adb(adb devices, for example) I get
"
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
"
Here's what I've tried so far:
1. Killing and restarting the adb.exe process, both with task manager and with adb kill-server(which is the only adb command I've found that does anything other than return an error message)
2. reinstalling both the drivers posted in this thread and those at nookdevs
3. rebooting both the computer and the nook color multiple times.
4. deleting all SDK files and both re-downloading and re-installing.
5. deleting every file I could find and the drivers and following the Nookdevs instructions. same problem
6. using the adb_wireless app, where it tells me to use adb connect <iP address> after running the app. same error message appears. Because of this step I'm less inclined to believe that it's a driver error, since the wifi app bypasses the USB driver, at least as far as I understand. I do, however, believe my drivers are installed correctly, I have ADB Composite android device in the device manager
The only google results I got with this error(for different devices) referred to the port adb needs being locked in to something else, but that doesn't appear to be the case here, I see nothing running on port 5037 in netstat
Thank you for taking the time to read my short novel, and I appreciate the help.
*shameless bump*
seriously though, 65 views and not a single person with even a suggestion? would this be better off in a different portion of the forums? Any advice at all?
dumb question, but with out the NC plugged in, when you type in "adb devices", what get's returned?
if you get that error message, than that's a config symptom.
Hey i'm no pro and got adb to work on accident...What i found is that the android sdk folder needs to be in your user folder. So when i go to start and click my user name my android sdk folder is in there with my downloads folder, desktop folder, and music folder. Makes sense? ALso any thing i push to my device i put into that folder in the tools directory. I found that that fixed most of my problems as i had the folder in the root of my c drive. Let me know if that helps.
No luck there, but thanks for the reply anyway. gives me the same error. I suspect in your case that you were not getting into the c:\android-sdk-windows folder and moving it to your username folder fixed that problem because that's the default path when you open a cmd prompt. Thanks for trying, though
Last thing i can think of is maybe your firewall? Kill it for a few mins and see what happens.
Still happens when the device isn't connected. I agree that its a config error rather than a driver issue. Also, disabling my firewall has no effect. Thanks for the suggestions though
Sent from my NookColor using XDA App
I have the same
nicbennett said:
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
Click to expand...
Click to collapse
W7/64.
ADB worked for me for months. I used it regularly. The last thing I did was *trying* to use Wireless ADB Widget and issueing ADB TCPIP command. I have made no changes to the system.
The error occurs when no device device connected. Same error when device IS connected.
-Downloaded ADB/SDK again to a different directory, same error
-Updated USB driver and SDK components, same error
-Disabled all firewall/anti-malware/anti-virus, same error
-Rebooted multiple times, same error off boot
-Port 5037 is not bound by any app or process
-ADB, upon failed load, is not listed in Taskmgr, nothing to kill
-Deleted temp files
-Issued at prompt: ADB Disconnect, ADB USB, ADB devices: All return same error as above
-Issued at prompt: ADB kill-server, only prompt returns
Read lots of posts on the web, nothing helps.
I am really interested in a solution and would like to understand what is causing the problem. If in fact it is a configuration issue, where is the ADB config file?
Thanks.
Edit: I am running the command prompt as an administrator.
not sure what was causing the issue, I ended up reformatting my HD and re-installing, it worked fine after. Sorry I couldn't be of more help, I looked everywhere for about 2 weeks and didn't find a thing that worked
nicbennett said:
not sure what was causing the issue, I ended up reformatting my HD and re-installing, it worked fine after. Sorry I couldn't be of more help, I looked everywhere for about 2 weeks and didn't find a thing that worked
Click to expand...
Click to collapse
Wow... I would hate to have to rebuild my computer just to get ADB back. I will post this in the Evo forum and see if there is some help.
Edit: Started a new thread in Evo forum:
http://forum.xda-developers.com/showthread.php?p=10730809#post10730809
Hello everyone! I'm writing because I need help rooting my KFHD 7".
I've read a lot of stuff and I'm kind of familiar with the topic now. This is my first android device though, so I'm still a noob with all of this.
I read a tutorial that said I needed some programs (QemuRoot, Root with restore by Bin4ry, Kindle Fire ADB Drivers).
The first step normally is to install the ADB drivers. Every time I try to install them a window opens and it starts the process, the bar loads completely and gives me an option to "Finish". Now, every time I click "Finish", another window opens and says "The drivers were not properly installed. Please install the drivers manually." I believe this is my main issue. Another thing is, I have no idea when to plug in/out my device... I don't know if I have to try to install the ADB thing when the Kindle's connected, etc. I tried to delete all the Kindle drivers on my pc to reinstall the ADB drivers, but I still get the same error...
Now, when I try to use the other programs, they say that my Kindle should open a dialog window asking if I want to restore my device, and that it will reboot in 10 secs. None of this happens. I just want to root my Kindle so I can use GooglePlay and download some good stuff. Also, I don't live in the US so I pretty much can't use my Kindle for anything. I even paid for Amazon Prime and I can't enjoy Amazon Instant Video (streaming series, etc) because of some geographical restrictions... IF any of you would know a workaround... Thanks
Kindle Fire 7" HD ADB Driver
Krawdd said:
Hello everyone! I'm writing because I need help rooting my KFHD 7".
I've read a lot of stuff and I'm kind of familiar with the topic now. This is my first android device though, so I'm still a noob with all of this.
I read a tutorial that said I needed some programs (QemuRoot, Root with restore by Bin4ry, Kindle Fire ADB Drivers).
The first step normally is to install the ADB drivers. Every time I try to install them a window opens and it starts the process, the bar loads completely and gives me an option to "Finish". Now, every time I click "Finish", another window opens and says "The drivers were not properly installed. Please install the drivers manually." I believe this is my main issue. Another thing is, I have no idea when to plug in/out my device... I don't know if I have to try to install the ADB thing when the Kindle's connected, etc. I tried to delete all the Kindle drivers on my pc to reinstall the ADB drivers, but I still get the same error...
Now, when I try to use the other programs, they say that my Kindle should open a dialog window asking if I want to restore my device, and that it will reboot in 10 secs. None of this happens. I just want to root my Kindle so I can use GooglePlay and download some good stuff. Also, I don't live in the US so I pretty much can't use my Kindle for anything. I even paid for Amazon Prime and I can't enjoy Amazon Instant Video (streaming series, etc) because of some geographical restrictions... IF any of you would know a workaround... Thanks
Click to expand...
Click to collapse
The first step is to get the ADB Driver installed.
The following ADB Driver was provided by Amazon and should install: Kindle Fire ADB drivers
If not, I have an alternative driver here: https://dl.dropbox.com/u/54456659/usb_driver.zip
The alternative driver originates from the Android SDK and is universal for just about any Android device.
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response.
The instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer to see if it initializes properly.
Reply once you have done this step OR respond with the error OR where you are stuck. We will get you on Google Play!
Amazon Notes regarding this ADB Driver can be found here: https://developer.amazon.com/sdk/fire/connect-adb.html
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Hardware Update Wizard.
2. Select Install from a list or specific location and click Next.
3. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
4. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
5. Click Next to install the driver.
Or, to upgrade an existing Android USB driver on Windows XP with the new driver:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Android Phone in the right pane.
5. Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7.Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9.Click Next to upgrade the driver.
prokennexusa said:
The first step is to get the ADB Driver installed.
The following ADB Driver was provided by Amazon and should install: link that you provided
If not, I have an alternative driver here: link that you provided
The alternative driver originates from the Android SDK and is universal for just about any Android device.
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response.
The instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer to see if it initializes properly.
Reply once you have done this step OR respond with the error OR where you are stuck. We will get you on Google Play!
Amazon Notes regarding this ADB Driver can be found here: link that you provided
Click to expand...
Click to collapse
Thanks for replying! The first ADB Driver (provided by Amazon) is the one that has given me the same error every time... something about an error and me installing the drivers manually (I have no idea how to do). The second link (dropbox) is broken... So right off the bat I'm stuck. The thing is, when I go to device manager, my Kindle Fire says "Android Composite ADB Interface"... I thought I already had ADB, but it appears that no matter what I do I can't get it to work... I don't have SDK or anything like that, though I'm downloading it to see if anything works...
Android Composite ADB Interface
Krawdd said:
Thanks for replying! The first ADB Driver (provided by Amazon) is the one that has given me the same error every time... something about an error and me installing the drivers manually (I have no idea how to do). The second link (dropbox) is broken... So right off the bat I'm stuck. The thing is, when I go to device manager, my Kindle Fire says "Android Composite ADB Interface"... I thought I already had ADB, but it appears that no matter what I do I can't get it to work... I don't have SDK or anything like that, though I'm downloading it to see if anything works...
Click to expand...
Click to collapse
OK, stop there. Even though it gave you an install error, it looks like the driver is installed. So let's move forward assuming they are functioning enough to get the job done.
Leave the Kindle plugged into USB and move on to my step-by-step which can be found 3/4 the way down on this Thread: http://forum.xda-developers.com/showthread.php?t=2064633
Note: The Kindle is left plugged in to USB through the entire tutorial.
prokennexusa said:
OK, stop there. Even though it gave you an install error, it looks like the driver is installed. So let's move forward assuming they are functioning enough to get the job done.
Leave the Kindle plugged into USB and move on to my step-by-step which can be found 3/4 the way down on this Thread: http://forum.xda-developers.com/showthread.php?t=2064633
Note: The Kindle is left plugged in to USB through the entire tutorial.
Click to expand...
Click to collapse
Thanks again. So I have the tool run with restore by bin4ry v18. When I open the folder, there is a RunMe.bat. I right click on it and click on run as administrator. It starts up and I write 1 to use normal mode. When it says that my Kindle should ask me for "restore", my Kindle is sitting there, doing nothing. It doesn't ask me for a restore. Then it says that my device will reboot in 10 seconds... My Kindle, again, does nothing. So that doesn't work... Now, I did another thing. I shift-right-clicked on the inside of the folder and clicked open command window here, then on the cmd that opened up I wrote "runme.bat" So it started the thing again, asked me for the number, etc. I write 1, and then this comes up (and it's stuck there): "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" ON on my Kindle... Any suggestions?
Krawdd said:
Thanks again. So I have the tool run with restore by bin4ry v18. When I open the folder, there is a RunMe.bat. I right click on it and click on run as administrator. It starts up and I write 1 to use normal mode. When it says that my Kindle should ask me for "restore", my Kindle is sitting there, doing nothing. It doesn't ask me for a restore. Then it says that my device will reboot in 10 seconds... My Kindle, again, does nothing. So that doesn't work... Now, I did another thing. I shift-right-clicked on the inside of the folder and clicked open command window here, then on the cmd that opened up I wrote "runme.bat" So it started the thing again, asked me for the number, etc. I write 1, and then this comes up (and it's stuck there): "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" ON on my Kindle... Any suggestions?
Click to expand...
Click to collapse
I see the problem. The way you are executing the batch files will cause the utilities to fail. You can not run the batch files (RunMe.bat and RootQemu.bat) through the mouse, you must execute them through a CMD Prompt.
OK, let's start from the top.
Let's make sure all the utilities are on your desktop.
Next Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v17 folder.
Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v17 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v17 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v17 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RunMe.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633), when you are ready to run Qemu
Next Double Mouse Click and Open the Qemu folder.
Single Left Mouse Click on the Qemu folder toolbar.
This highlights the Qemu folder.
Note: Make sure none of the files within the Qemu are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RootQemu.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633).
prokennexusa said:
I see the problem. The way you are executing the batch files will cause the utilities to fail. You can not run the batch files (RunMe.bat and RootQemu.bat) through the mouse, you must execute them through a CMD Prompt.
OK, let's start from the top.
Let's make sure all the utilities are on your desktop.
Next Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v17 folder.
Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v17 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v17 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v17 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RunMe.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633), when you are ready to run Qemu
Next Double Mouse Click and Open the Qemu folder.
Single Left Mouse Click on the Qemu folder toolbar.
This highlights the Qemu folder.
Note: Make sure none of the files within the Qemu are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RootQemu.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633).
Click to expand...
Click to collapse
Thanks for the reply. As I said in the previous post, I had already done the "shift right click and open windows command here" thing. It doesn't work. This is where it gets to and stays there forever "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" So I'm stuck right at the first step... Doesn't matter what way I run the batch files I can't get them to work.
ADB Communication Issues
Krawdd said:
Thanks for the reply. As I said in the previous post, I had already done the "shift right click and open windows command here" thing. It doesn't work. This is where it gets to and stays there forever "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" So I'm stuck right at the first step... Doesn't matter what way I run the batch files I can't get them to work.
Click to expand...
Click to collapse
Let's check the ADB communication path on your workstation.
Open a command prompt at the root of the Qemu folder, type:
Code:
adb kill-server
adb start-server
adb devices
The next command will probably fail, but let's try it:
Code:
android update adb
Finally, try:
Code:
adb shell
Reply back with the results.
prokennexusa said:
Let's check the ADB communication path on your workstation.
Open a command prompt at the root of the Qemu folder, type:
Code:
adb kill-server
adb start-server
adb devices
The next command will probably fail, but let's try it:
Code:
android update adb
Finally, try:
Code:
adb shell
Reply back with the results.
Click to expand...
Click to collapse
Thanks a lot! Well this are the results:
I did adb kill-server and nothing happened.
I did adb start-server and it said "daemon not running. starting it now on port 5037. daemon started succesfully"
I did adb devices and it said "list of devices attached" and then a blank space after that..
I did android update adb and it said "android is not a recognized internal or external command"
I did adb shell and it said "device not found"
I did all of that in the QemuRoot folder.. Am I doing it right? I double click on the folder to open it and then I click on the white space below all the files (while holding shift) and open the command window.
ADB Server Out of Date
Krawdd said:
Thanks a lot! Well this are the results:
I did adb kill-server and nothing happened.
I did adb start-server and it said "daemon not running. starting it now on port 5037. daemon started succesfully"
I did adb devices and it said "list of devices attached" and then a blank space after that..
I did android update adb and it said "android is not a recognized internal or external command"
I did adb shell and it said "device not found"
I did all of that in the QemuRoot folder.. Am I doing it right? I double click on the folder to open it and then I click on the white space below all the files (while holding shift) and open the command window.
Click to expand...
Click to collapse
Yes, you did this perfectly.
Hmmmm, looks like the ADB Driver is NOT working, bummer.
We need to focus on getting the driver functional.
Step 1) Go into Windows Add/Remove Software, find the Android ADB Driver, Uninstall the driver. If you can not find the driver in Add/Remove, then use the Uninstall Utility found in the Qemu folder "Drivers".
Step 2) Remove the Kindle from USB. Reboot the PC.
Step 3) Plug the Kindle back into USB after startup.
Step 4) When the PC has completed the reboot cycle, let's try to install the driver manually using the driver inside the usb_driver folder. Follow my instructions performing a manual driver install.
prokennexusa said:
Yes, you did this perfectly.
Hmmmm, looks like the ADB Driver is NOT working, bummer.
We need to focus on getting the driver functional.
Step 1) Go into Windows Add/Remove Software, find the Android ADB Driver, Uninstall the driver. If you can not find the driver in Add/Remove, then use the Uninstall Utility found in the Qemu folder "Drivers".
Step 2) Remove the Kindle from USB. Reboot the PC.
Step 3) Plug the Kindle back into USB after startup.
Step 4) When the PC has completed the reboot cycle, let's try to install the driver manually using the driver inside the usb_driver folder. Follow my instructions performing a manual driver install.
Click to expand...
Click to collapse
I deleted everything, I rebooted my PC, plugged in my Kindle and it started to install the Kindle drivers... (the normal ones)... It got an error and the driver didn't install... I got to manage under "computer" and i see "other devices" and under that it says "kindle" with a yelow exclamation mark... I go to its properties and drivers, I click update driver and use the folder that you gave me (usb_driver) and it gives me an error, saying that it could not find drivers... now do I set it to install the driver in C:\Users\Name\Desktop\usb_driver? or after usb_driver should I add \amd65 or \i386?
Thanks for your help... I don't know why nothing is working out!!
By the way, i just tried to install the adb drivers again and I got the same error... saying I have to install them manually. I ran both the bin4ry v18 and the qemuroot and both got stuck at "*daemon started successfully*" and they just sit there doing nothing...
ADB Driver Install
Krawdd said:
I deleted everything, I rebooted my PC, plugged in my Kindle and it started to install the Kindle drivers... (the normal ones)... It got an error and the driver didn't install... I got to manage under "computer" and i see "other devices" and under that it says "kindle" with a yelow exclamation mark... I go to its properties and drivers, I click update driver and use the folder that you gave me (usb_driver) and it gives me an error, saying that it could not find drivers... now do I set it to install the driver in C:\Users\Name\Desktop\usb_driver? or after usb_driver should I add \amd65 or \i386?
Thanks for your help... I don't know why nothing is working out!!
Click to expand...
Click to collapse
Yes, you are correct on the path: C:\Users\Name\Desktop\usb_driver
Let's try to install the Kindle Fire ADB Driver provided by Amazon. This time Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
If that fails, try to Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose Properties.
Then select the "Compatibility" tab
Check "Run this program in compatibility mode for"
Choose Windows XP Service Pack 2
Finally Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
prokennexusa said:
Yes, you are correct on the path: C:\Users\Name\Desktop\usb_driver
Let's try to install the Kindle Fire ADB Driver provided by Amazon. This time Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
If that fails, try to Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose Properties.
Then select the "Compatibility" tab
Check "Run this program in compatibility mode for"
Choose Windows XP Service Pack 2
Finally Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
Click to expand...
Click to collapse
Didn't work... I'm using windows 7 though... When I plugged in my Kindle it said something like Android ADB Composite installed succesfully... It did it by its own... When I try to install the Amazon ADB I get the same error, that i have to install it manually... I tried running the bin4ry root again and it doesn't work...
ADB Communication Issues
Krawdd said:
Didn't work... I'm using windows 7 though... When I plugged in my Kindle it said something like Android ADB Composite installed succesfully... It did it by its own... When I try to install the Amazon ADB I get the same error, that i have to install it manually... I tried running the bin4ry root again and it doesn't work...
Click to expand...
Click to collapse
We are missing something, usually simple.
What is the date and time stamp on the adb.exe daemons in the Root_with_Restore_by_Bin4ry_v17 "Stuff" folder?
---------- Post added at 05:09 PM ---------- Previous post was at 04:20 PM ----------
For everyone having trouble with ADB, here is a video that you may find helpful:
ADB Driver Install Video
prokennexusa said:
we are missing something, usually simple.
What is the date and time stamp on the adb.exe daemons in the root_with_restore_by_bin4ry_v17 "stuff" folder?
---------- post added at 05:09 pm ---------- previous post was at 04:20 pm ----------
for everyone having trouble with adb, here is a video that you may find helpful:
adb driver install video
Click to expand...
Click to collapse
1/13/2012 4:20 pm
ADB Server Out of Date
Krawdd said:
1/13/2012 4:20 pm
Click to expand...
Click to collapse
I thought I was going crazy. I knew it had to be something simple. You must have downloaded these utilities (Qemu and Root_with_Restore_by_Bin4ry_v17) from the developers site and not our site. Our utilities include the latest ADB daemons
which are dated 11/05/2012 11:06AM.
This is your problem.
Please use our utilities:
Kindle_Fire_HD_ADB_Drivers
Root_with_Restore_by_Bin4ry_v17
Qemu
Then go back to our step-by-step instructions. The ADB driver is probably fine, so you can probably bypass that step.
prokennexusa said:
I thought I was going crazy. I knew it had to be something simple. You must have downloaded these utilities (Qemu and Root_with_Restore_by_Bin4ry_v17) from the developers site and not our site. Our utilities include the latest ADB daemons
which are dated 11/05/2012 11:06AM.
This is your problem.
Please use our utilities:
Kindle_Fire_HD_ADB_Drivers
Root_with_Restore_by_Bin4ry_v17
Qemu
Then go back to our step-by-step instructions. The ADB driver is probably fine, so you can probably bypass that step.
Click to expand...
Click to collapse
Genius!!! It went smoothly, I did all the steps on the bin4ry and then qemu, and it said you now have root! How do I now if I actually have root? I don't see any different app in my kindle, I think I should have something like superuser?
Initialize Superuser.apk
Krawdd said:
Genius!!! It went smoothly, I did all the steps on the bin4ry and then qemu, and it said you now have root! How do I now if I actually have root? I don't see any different app in my kindle, I think I should have something like superuser?
Click to expand...
Click to collapse
Yes, you should see Superuser.apk in the APPS Folder. Go ahead and launch Superuser.apk to initialize it.
prokennexusa said:
Yes, you should see Superuser.apk in the APPS Folder. Go ahead and launch Superuser.apk to initialize it.
Click to expand...
Click to collapse
I guess it was too good to be true... there's no superuser.apk in the apps folder.. what to do? I already tried rooting it again and it said that i was rooted again
EDIT: I just woke up and tried again. Instead of usin first the root with restore and second the qemu, I used root with restore twice. Now I have a different app called SuperSU... It isn't Superuser though... It has a picture of the android robot wiith a cape flying... I opened but I have no idea what to do with it!
It worked for the error that you are having.
Hello i just read your post.. before continue sorry about my English is not perfect but i will try to to explain hot to explain the "solution"..
ok the first thing you need to do,is uninstall all the ADB drivers from the device manager.
after that you have to restart your PC..
when your pc is already started install de ADB drivers and then connect your kindle..! and let windows install the drivers again.
It worked for my so i hope it work for you.. =)
When I try to flash something via ADB on my computer it doesn't work because I get an error message that multiple terminals are open. I'm not good with command line stuff on the computer and usually figure out a way around it so I can flash what I need to, but the next time I need to flash something I'm in the same boat again with the same error message. Is there a way to close everything that is supposedly running so I don't get that error?
jhs39 said:
When I try to flash something via ADB on my computer it doesn't work because I get an error message that multiple terminals are open. I'm not good with command line stuff on the computer and usually figure out a way around it so I can flash what I need to, but the next time I need to flash something I'm in the same boat again with the same error message. Is there a way to close everything that is supposedly running so I don't get that error?
Click to expand...
Click to collapse
Hello,
What's the output of:
adb devices
Also, can you paste the exact error displayed on the command prompt?
You could try:
adb kill-server
Which kill the adb.exe process
Then:
adb start-server
Cheers...
Updated Android platform tools and when I flashed the latest bootloader didn't get that error again. The update must have cleared up the problem. Hopefully it won't happen again. Is there something you are supposed to do after flashing to ensure that the terminal doesn't rename open in the background in windows?
jhs39 said:
Updated Android platform tools and when I flashed the latest bootloader didn't get that error again. The update must have cleared up the problem. Hopefully it won't happen again. Is there something you are supposed to do after flashing to ensure that the terminal doesn't rename open in the background in windows?
Click to expand...
Click to collapse
Hello,
By "rename" you meant "remain" ?
I don't think so... But you can right click on your windows taskbar and open task manager.
Look at processes and see if ADB.exe is still running. You can also tic:
"Show processes for all users" and see here...
Cheers...