im trying to set up adb, and it wont recognize my mytouch. ive searched and what i found didnt work for me.
any help would be greatly appreciated.
This helped me.
i dont have windows 7
smjfosho said:
im trying to set up adb, and it wont recognize my mytouch. ive searched and what i found didnt work for me.
any help would be greatly appreciated.
Click to expand...
Click to collapse
First download USBDeview - http://www.nirsoft.net/utils/usbdeview.zip
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
Then, plug your phone in, don't mount it! Pull up a command windows and type:
cd C:\android-sdk-windows\tools (or wherever you have your sdk installed)
adb devices (should see your phones serial number listed if you did it correctly)
adb shell
su (for root access)
sombionix said:
First download USBDeview - http://www.nirsoft.net/utils/usbdeview.zip
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
Then, plug your phone in, don't mount it! Pull up a command windows and type:
cd C:\android-sdk-windows\tools (or wherever you have your sdk installed)
adb devices (should see your phones serial number listed if you did it correctly)
adb shell
su (for root access)
Click to expand...
Click to collapse
i tried this method, did work for me
smjfosho said:
i tried this method, did work for me
Click to expand...
Click to collapse
did work or didn't?
sombionix said:
did work or didn't?
Click to expand...
Click to collapse
sorry, it didnt work for me
Hmmm....worked for me and many others. Strange. You did download SDK with the appropriate drivers, right?
sombionix said:
Hmmm....worked for me and many others. Strange. You did download SDK with the appropriate drivers, right?
Click to expand...
Click to collapse
i downloaded the sdk, what drivers are you talking about?
when i setup the sdk, i downloaded those drivers.
It was a long time ago when I downloaded SDK, however, if I'm not mistaken, I believe when it connects to the server and gives you download options, one of those options is USB drivers.
http://androidcommunity.com/forums/f4/how-to-install-android-sdk-v1-0-step-by-step-5749/index3.html
Yeah, there are definitely USB drivers you need to download.
sombionix said:
http://androidcommunity.com/forums/f4/how-to-install-android-sdk-v1-0-step-by-step-5749/index3.html
Yeah, there are definitely USB drivers you need to download.
Click to expand...
Click to collapse
thats about 64bit windows, im only using a 32bit.
http://developer.android.com/sdk/win-usb.html
Here are the USB drivers for windows. Also, make sure you have 'debugging' checked in your phoned settings. ADB won't work otherwise. After you install the drivers, follow the steps on the first page. Hope that works!
sombionix said:
http://developer.android.com/sdk/win-usb.html
Here are the USB drivers for windows. Also, make sure you have 'debugging' checked in your phoned settings. ADB won't work otherwise. After you install the drivers, follow the steps on the first page. Hope that works!
Click to expand...
Click to collapse
ive tried this as well, that didnt work either,
i think im missing something
Wish I could offer more help, not sure why it won't work. Everything I told you to try is exactly how I set mine up and it works.
sombionix said:
Wish I could offer more help, not sure why it won't work. Everything I told you to try is exactly how I set mine up and it works.
Click to expand...
Click to collapse
when i go into the usbthing i only have one htc and not 3?
smjfosho said:
when i go into the usbthing i only have one htc and not 3?
Click to expand...
Click to collapse
You have to make sure you're running USBdeview as admin on your computer. Also, you won't necessarily have 3. Just select which ever ones you do have, right click and delete those files. Then unplug your phone and plug it back in. You computer should automatically install the appropriate drivers, and you should be able to use adb.
sombionix said:
You have to make sure you're running USBdeview as admin on your computer. Also, you won't necessarily have 3. Just select which ever ones you do have, right click and delete those files. Then unplug your phone and plug it back in. You computer should automatically install the appropriate drivers, and you should be able to use adb.
Click to expand...
Click to collapse
so i did all of that, typed the commands, and it says list of adb devices:
then there is nothing afterward
smjfosho said:
so i did all of that, typed the commands, and it says list of adb devices:
then there is nothing afterward
Click to expand...
Click to collapse
No serial number underneath?
sombionix said:
No serial number underneath?
Click to expand...
Click to collapse
nope, nothing
Okay, I have a permarooted MT4G with S=Off, and I want to use the gfree method to unlock my SIM and get the universal CID while I'm still on the stock kernel. All of the guides I see for that push the gfree files using the ADB.
Problem: I cannot get the Android SDK to recognize my MyTouch 4g. (SEE UPDATE)
I followed this guide http://forum.xda-developers.com/showthread.php?t=834748 to try and set up the ADB to no avail. This is what I did:
-- Downloaded the SDK, booted it up, let it update. Booted it up again, let it update EVERYTHING (took like 30 minutes) again. It has no more updates to install.
-- I tried adding adb as an environmental variable in windows, but the command prompt, no matter where I start it from, does not recognize 'adb' as "an internal or external command, operable program, or batch file." (works now)
-- The HTC Drivers that came with my device have been installed on my computer. So, I uninstalled them, only to have windows reinstall them as soon as I plug the device in (I'm running Windows 7 x64 home edition, Build 7601).
I tried going here http://forums.t-mobile.com/t5/HTC/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017 and using their technique, no dice. My computer has the exact same drivers as when I started, and I have a digital paperweight of a SDK. (see update)
UPDATE: I now have a working ADB (big thanks to TrueBlue_Drew and his guide for us noobs) that recognizes my MT4G, but I have another issue:
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct windows to the usb drivers I downloaded from the both of the guides I've used, but windows wouldn't accept either one. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since adb is working? Any help on that end would VERY MUCH appreciated.
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
neidlinger said:
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
corruptsmurf said:
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
Click to expand...
Click to collapse
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
So close, yet...
TJBunch1228 said:
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Actually no, adb.exe isn't It has a .txt named "Adb has moved," not really sure how to proceed from here; I downloaded the SDK that was in the topic I linked above, and just allowed it to update. More below, and thanks for the response.
jdkoren said:
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
Click to expand...
Click to collapse
Yeah, the problem is that my PC doesn't list any errors when I plug it in. BUT BIG NEWS, I followed the ADB for noobs guide (http://forum.xda-developers.com/showthread.php?t=928370), and I realized, as I said above, that my adb.exe file was nowhere to be found, so I used the one from the noob guide, and it could recognize my device in ADB. BUT it could not recognize my device in fastboot, so after much frustration, I decided to uninstall the drivers and reinstall using pda.net. Whatever it did, it worked, because adb and fastboot both show my serial number under devices. Thanks to the both of you for your help.
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the Misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct it to the usb drivers listed in the both of the guides listed above, but windows wouldn't have it. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since I can use adb anyhow? Any help on that end would VERY MUCH appreciated.
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.. =)