Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
retroflashbacks said:
Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
Click to expand...
Click to collapse
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
I'm having the exact same problem here.
RooQemu hangs at *Daemon started successully* and nothing happens
when I try to enter "adb shell" in a cmd i get the error "device not found"
Kindle is shown correct in device manager as "Android Composite ADB Interface" and I can transfer files via explorer without problems.
Windos 7 64 bit and Kindle from amazon Germany Version 7.2.1_user_2040020
Tried on my Laptop and my PC, both with the same result.
At least someone seems to have the same problem as I do. Hope someone comes up with a solution. I tried the steps mentioned above, same result...
spliter200 said:
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
Click to expand...
Click to collapse
Thanks man..
unfortunately, it didn't work for me..
i think it might be something with the drivers since it keeps telling me that the install didn't work correctly..and i need to "manually install it".
Any more ideas?
Thanks everyone! :good:
retroflashbacks said:
Thanks man..
unfortunately, it didn't work for me..
i think it might be something with the drivers since it keeps telling me that the install didn't work correctly..and i need to "manually install it".
Any more ideas?
Thanks everyone! :good:
Click to expand...
Click to collapse
Try this. Install the Android SDK in your computer reboot your kindle and the computer and try again. It worked for me
Darn..still not working...
This problem is due to the drivers!
You need to uninstall the drivers in the device manager, and manually install the drivers from the location you install the ADB drivers.
In my computer, the location is "C:\program files\amazon.com\kindle fire\drivers".
The wrong driver is like this: ”Android ADB Interface“
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And the correct driver is like this:
retroflashbacks said:
Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
Click to expand...
Click to collapse
Thanks everyone for the responses! I really appreciate it!
It's getting really weird..because even though the drivers said it was installed correctly..everything seemed to install fine.
My device manager do say "Android Composite ADB Interface"
can't do a screenshop because i'm not allowed to post links..
retroflashbacks said:
Thanks everyone for the responses! I really appreciate it!
It's getting really weird..because even though the drivers said it was installed correctly..everything seemed to install fine.
My device manager do say "Android Composite ADB Interface"
can't do a screenshop because i'm not allowed to post links..
Click to expand...
Click to collapse
Try to do what PMcHargue explained, it didn't work for me but who knows? Locate the adb_usb.ini file and insert the last line.
PMcHargue said:
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
Click to expand...
Click to collapse
retroflashbacks said:
Thanks everyone for the responses! I really appreciate it!
It's getting really weird..because even though the drivers said it was installed correctly..everything seemed to install fine.
My device manager do say "Android Composite ADB Interface"
can't do a screenshop because i'm not allowed to post links..
Click to expand...
Click to collapse
Hey! I'm the one that had the same problem as you.
I tried everything... Then I installed Android SDK and followed this guide:
groovypost . com / howto / kindle-fire-hd-connect-adb-debug
Then it worked.
Hope that helps!
spliter200 said:
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
Click to expand...
Click to collapse
I had the same problem but I did this bur turned my wifi off before step 2. The device appeared with a caution sign next to it in the device manager (no driver installed) but the adb commands started to work and I could root my kindle. Hope this works for you.
Sent from my KFTT using xda app-developers app
It didn't work for me with the drivers in this post, it worked using the Amazon drivers from Android SDK.
retroflashbacks said:
Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
Click to expand...
Click to collapse
What worked for me was to download the android SDK into the root folder of the PC...OR C: If you like....I still found that after every step I had to unplug the device and re-plug it (Is that a word) to continue as the device wasnt found. Im now told ADB tools works better? Gotta have another go since Super user didnt get root access....Guess were on the same journey!
I have the "Android ADB Interface" and not the Composite one and its worked fine for me
thanks alot mate ...
i have windows 8 and faced same problem ...
i did what u said n the root method worked like charm..
thanks again
spliter200 said:
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
Click to expand...
Click to collapse
x64 problem?
I'm having the exact same issue, 'daemon started successfully' I think it has something to do with my OS being x64. I kpet the Task Manager open, and it seems like it opens up 2 adb.exe *32 at once. I tried closing one, and the program would continue. I'm using an Intel x64, and I noticed that the only drivers in the Amazon.com folder were *386, and AMD64. I'm not sure if AMD64. Not sure if this added info is relevant, since the original driver is prior to these directories. I hope an easier method evolves.
Update ... I tried downloading the android sdk, then copied the adb.exe over to the Root\stuff folder and it worked! once you copy the adb.exe, just follow the original OP's instructions.
Eu quero meu root
Related
So I just installed Windows 7 on my machine and was trying to ADB with my Android since I used it ALL the time on Windows XP.
I put the phone in Debug mode and plugged into my computer and told it the location of the driver. It seems to work well for a second and then it tells me that there was a problem installing the driver. It then says:
HTC ADB Composite Device Driver (not sure exactly of this...)
Access is Denied
Click to expand...
Click to collapse
Anyone else seeing anything similar on Vista or Windows 7? BTW I already tried this in Safe Mode as well.
Stigy said:
So I just installed Windows 7 on my machine and was trying to ADB with my Android since I used it ALL the time on Windows XP.
I put the phone in Debug mode and plugged into my computer and told it the location of the driver. It seems to work well for a second and then it tells me that there was a problem installing the driver. It then says:
Anyone else seeing anything similar on Vista or Windows 7? BTW I already tried this in Safe Mode as well.
Click to expand...
Click to collapse
I have mines working perfectly on Win7. Maybe you don't have admin rights on your computer? Just a guess
xidominicanoix said:
I have mines working perfectly on Win7. Maybe you don't have admin rights on your computer? Just a guess
Click to expand...
Click to collapse
Nope I have administrative rights and even tried it in safe mode.
Would you be able to zip up the drivers you used or link to where you downloaded them from?
So strange.
Even if you have admin rights, UAC can f it up.
Make sure you right click on command prompt and click "Run as Administrator"
Also, do you have x64? That requires a signed drivers. I don't remember if the ADB drivers were signed by microsoft, but if they aren't, it won't work unless you apply the work around
http://forum.xda-developers.com/showthread.php?t=532719
The link in this thread usbdeview seems to fix alot of driver issues
Stigy said:
Nope I have administrative rights and even tried it in safe mode.
Would you be able to zip up the drivers you used or link to where you downloaded them from?
So strange.
Click to expand...
Click to collapse
i got mines from the 1.6 sdk .. x64
Simple Solution
Here is a simple solution without having to read that long thread:
For future reference, here is how to install the drivers or fix the drivers should they not be working.
Everything you need is contained within this:
http://www.divshare.com/download/8845496-f72
This is the howto documentation
This is how to get your android phone to connect to you PC
to use functions like adb and other developer tools.
If you have installed the phone before but adb function dont work
then:
1) Run USBDeview
2) Select the list item(s) that have the word "android" within the description
3) Right Click > Uninstall
If you have done the above, or are plugging your phone in for the first time:
1) Plug in phone
2 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
2 b) If no message appears or you get a message saying drivers failed
to install. Goto device manager
2 b i) start > All Programs > accessories > run
type devmgmt.msc and press ok.
3 b) find the android device in device manager, it will have a warning icon
next to it and be in a section like unknown.
4 b) Right click and install driver
5 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
Click to expand...
Click to collapse
USBDeview is awesome but....
Even after removing all of the drivers associated with my device, as soon as I try to install the fresh new drivers, I still get "Access Denied" at the end of the install.
digimancer said:
Even after removing all of the drivers associated with my device, as soon as I try to install the fresh new drivers, I still get "Access Denied" at the end of the install.
Click to expand...
Click to collapse
I have this same issue on an Ideos U8150 and on XP... At one point in the past it was working (before I flashed Cyanogen 7). Since then I have tried numerous driver packages, both specific to my phone and generic, and have had no luck getting past the access denied error.. I have even gone as far as changing the registry permission as well as checking all of my folder permissions... I am stumped.
Adb root - run that from command prompt.
B-man007 said:
Even if you have admin rights, UAC can f it up.
Make sure you right click on command prompt and click "Run as Administrator"
Also, do you have x64? That requires a signed drivers. I don't remember if the ADB drivers were signed by microsoft, but if they aren't, it won't work unless you apply the work around
Click to expand...
Click to collapse
I know it a while ago since you posted this but still, it helped me fix the "Access denied" thing which i didn't know how to fix. I installed ADB drivers 3 times... anyways, tnx :good:
So If you are like me you had this same issue in 2022. Idk if it will be a fix for you but it was for me.
follow this youtube video for the exact setup so you can get hopfully the same out com to the T.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. make sure you're in administrator mode for command prompt.
2. The file name has changed from what it was so instead of doing
cd adb\platform-tools_r30.0.4-windows\platform-tools
It's now this
cd adb\platform-tools\
This will get you to the correct path if you followed the file placement in the video.
next all you have to do is type
adb devices on the command prompt. to test if it worked
other things that you might have to try is seeing if the driver it self is being blocked. you might also have to turn off and back on developer mode. View other posts in this thread if it's still stuck for you. Hopefully I helped one person at least.
Have the drivers sparkym3 has linked in his post. Have any and all other devices disconnected(made that mistake already) Have ADB access on and have allow installation from unknown sources checked as well. Tried the micro usb cable that came with the kindle a long with the cable that came with my Galaxy S 3. Computer sees the Kindle without issue but ADB can't seem to find it. Where am i going wrong.
Sh!!!!!tttt my bad for posting this here please move or delete.
Did you check to see if the Kindle shows up in your device manager as Composite ADB Interface?
androitri said:
Awesome, want to try it when I receive my HD 7 this week...
Click to expand...
Click to collapse
as such u mean?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
or should it appear differently
was just going to post same thing mines doing same i just fallowed gide
Abiddar said:
was just going to post same thing mines doing same i just fallowed gide
Click to expand...
Click to collapse
care to elaborate?
Aali1011 said:
care to elaborate?
Click to expand...
Click to collapse
Installed all drivers computer recognizes my kindle its in device manager but my adb wont recognize
---------- Post added at 05:17 AM ---------- Previous post was at 05:12 AM ----------
Abiddar said:
Installed all drivers computer recognizes my kindle its in device manager but my adb wont recognize
Click to expand...
Click to collapse
fixed mine
uninstall driver for kindle and reinstall and re connect kindle and u should be good
Abiddar said:
Installed all drivers computer recognizes my kindle its in device manager but my adb wont recognize
---------- Post added at 05:17 AM ---------- Previous post was at 05:12 AM ----------
fixed mine
uninstall driver for kindle and reinstall and re connect kindle and u should be good
Click to expand...
Click to collapse
tried and nothing
Aali1011 said:
Have the drivers sparkym3 has linked in his post. Have any and all other devices disconnected(made that mistake already) Have ADB access on and have allow installation from unknown sources checked as well. Tried the micro usb cable that came with the kindle a long with the cable that came with my Galaxy S 3. Computer sees the Kindle without issue but ADB can't seem to find it. Where am i going wrong.
Click to expand...
Click to collapse
I posted this in the development thread. If you have the SDK installed and you get "error: device not found" or something to that effect when you run Adb Shell, you need to do the following steps.
Navigate to the [your user name]/.android folder under C:\Users
Edit the adb_usb.ini file by adding the following line of code at the end:
0×1949
Close and save the file.
Now find the folder where your SDK is installed, and open the usb_driver folder. In that folder, find the file android_winusb.inf and add the following code to both the [Google.NTx86] and [Google.NTamd64] sections:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Reboot and then run adb shell again. It should recognize your device. This worked for me.
Zagzagel said:
I posted this in the development thread. If you have the SDK installed and you get "error: device not found" or something to that effect when you run Adb Shell, you need to do the following steps.
Navigate to the [your user name]/.android folder under C:\Users
Edit the adb_usb.ini file by adding the following line of code at the end:
0×1949
Close and save the file.
Now find the folder where your SDK is installed, and open the usb_driver folder. In that folder, find the file android_winusb.inf and add the following code to both the [Google.NTx86] and [Google.NTamd64] sections:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Reboot and then run adb shell again. It should recognize your device. This worked for me.
Click to expand...
Click to collapse
what are you using to add the lines of code. It is simply just opening the file up in notepad? I intend to try this when i get home.
Aali1011 said:
what are you using to add the lines of code. It is simply just opening the file up in notepad? I intend to try this when i get home.
Click to expand...
Click to collapse
Attached is the adb_usb.ini, just locate it in c:\%user%\.android directory and remove the ".txt" at the end.
Try rebooting your computer after installing the drivers, then plug in the KF HD.
Zagzagel said:
I posted this in the development thread. If you have the SDK installed and you get "error: device not found" or something to that effect when you run Adb Shell, you need to do the following steps.
Navigate to the [your user name]/.android folder under C:\Users
Edit the adb_usb.ini file by adding the following line of code at the end:
0×1949
Close and save the file.
Now find the folder where your SDK is installed, and open the usb_driver folder. In that folder, find the file android_winusb.inf and add the following code to both the [Google.NTx86] and [Google.NTamd64] sections:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Reboot and then run adb shell again. It should recognize your device. This worked for me.
Click to expand...
Click to collapse
I have tried this and have not had luck. In Device Manager, it shows up as Android ADB Interface (does not have the word Composite like everyone elses'). Is this significant? I also get a pop up on my kindle about USB Compatibility with a link to download a file transfer utility. I have transferred files before, although now I don't appear to be able to.
same here haven't been able to get this to work. Still the same ADB doesn't see the device at all.
Aali1011 said:
same here haven't been able to get this to work. Still the same ADB doesn't see the device at all.
Click to expand...
Click to collapse
Keep trying. Following this guide is what did it for me https://developer.amazon.com/sdk/fire/connect-adb.html . I did this and every other method on my laptop with no luck (USB drivers crapped on me altogether, nothing works now). I finally got it to work on my computer after several attempts. Even once its working, its still fragile and requires you to unplug and reconnect often. And don't forget to turn on ADB on the Kindle (obvious, but sometimes it happens!) Good luck!
Aali1011 said:
same here haven't been able to get this to work. Still the same ADB doesn't see the device at all.
Click to expand...
Click to collapse
Unzip the attached android.zip to C:\users\"your user"(such as administrator)\
Also, the sparkym3's derive is needed to install.
you can see the attached pictures.
jst07 said:
I have tried this and have not had luck. In Device Manager, it shows up as Android ADB Interface (does not have the word Composite like everyone elses'). Is this significant? I also get a pop up on my kindle about USB Compatibility with a link to download a file transfer utility. I have transferred files before, although now I don't appear to be able to.
Click to expand...
Click to collapse
I'm in exactly the same boat.
I was able to transfer files, but after I installed the driver, I wasn't able to do so.
It shows up as "Android ADB Interface".
And of course, I tried doing everything mentioned, and I can't get into it.
dotvezz said:
I'm in exactly the same boat.
I was able to transfer files, but after I installed the driver, I wasn't able to do so.
It shows up as "Android ADB Interface".
And of course, I tried doing everything mentioned, and I can't get into it.
Click to expand...
Click to collapse
That is exactly what I was seeing on my HP laptop, but it has wonky usb drivers (have had issues with other devices). They're total broke now, it wouldn't even recognize my GNex anymore. If you can, I'd recommend trying another computer - friends or other. I don't know if that Device name has any significance, but when I did get it to work on my desktop computer it was listed as "Android Composite ADB Interface"
jst07 said:
That is exactly what I was seeing on my HP laptop, but it has wonky usb drivers (have had issues with other devices). They're total broke now, it wouldn't even recognize my GNex anymore. If you can, I'd recommend trying another computer - friends or other. I don't know if that Device name has any significance, but when I did get it to work on my desktop computer it was listed as "Android Composite ADB Interface"
Click to expand...
Click to collapse
Yeah, I also can't get it to connect to my GNex either. I'm trying on another computer now but still no progress...
For those who are having driver issues; try this program to clean your device drivers in Microsoft Windows.
GhostBuster
Here is my simple instructions, but do advise you to read the actual online documentation.
Under the Status Column RIGHT click on each item, and select "Add Device".
Check "Create System Restore Checkpoint", then Select "Remove Ghosts".
Select DEVICE(s) only in the following Catagories:
Android Phone
Disk drives
Kindle Fire
Other devices
Portable Devices
Storage Volumes
Universal Serial Bus controllers
I hope this is helpful for someone, this worked very well for me.
The exact same thing is happening to me. No matter what I do, I cant' get adb to recognize it. It says "Android ADB Interface" instead of "Android Composite USB Interface" or whatever.
This works for me
TheDoolster said:
The exact same thing is happening to me. No matter what I do, I cant' get adb to recognize it. It says "Android ADB Interface" instead of "Android Composite USB Interface" or whatever.
Click to expand...
Click to collapse
I was having the same issue like you guys. After playing around with it, I got it working.
1. uninstall all Kindle Fire HD drivers in control panel
2. download/install the Kindle Fire HD drivers from Android SDK extra
3. reconnect your Kindle Fire HD. It should say Android Composite USB Interface in Device Manager
* If that doesn't work, try restore your KFHD to factory settings. I actually did that first.
i just got a Kindle 7 HD (7.3.0)...tried installing the ADB drivers several times, seemed to work OK, but i still have an error with the MTP driver....trying to use KFFirstAide64, but every time i try to run an option i get "The System Cannot find the Path Specified" ...the Kindle is also not visible at all using Windows Explorer
i eventually used "Root_with_Restore_by_Bin4ry_v17", and think i have Root (according to SuChecker: "Congratulations!! This Device has Root Access!), but still can't use ADB and KFFirstAide64 to do anything else...keep getting "The System Cannot find the Path Specified"
following the instructions here: http://forum.xda-developers.com/showthread.php?t=2069117
what am i missing?
using Win7 x64
phunzoid said:
i just got a Kindle 7 HD (7.3.0)...tried installing the ADB drivers several times, seemed to work OK, but i still have an error with the MTP driver....trying to use KFFirstAide64, but every time i try to run an option i get "The System Cannot find the Path Specified" ...the Kindle is also not visible at all using Windows Explorer
i eventually used "Root_with_Restore_by_Bin4ry_v17", and think i have Root (according to SuChecker: "Congratulations!! This Device has Root Access!), but still can't use ADB and KFFirstAide64 to do anything else...keep getting "The System Cannot find the Path Specified"
following the instructions here: http://forum.xda-developers.com/showthread.php?t=2069117
what am i missing?
using Win7 x64
Click to expand...
Click to collapse
You should have read more.
Go here and follow the instructions. http://forum.xda-developers.com/showpost.php?p=38409721&postcount=1018
Guardian10 said:
You should have read more.
Go here and follow the instructions. http://forum.xda-developers.com/showpost.php?p=38409721&postcount=1018
Click to expand...
Click to collapse
Took me forever to get the ADB working. Course, I refused to read instructions, and was working under the premise that ADB stood for A Drink Before.
A Drink Before.......
Guardian10 said:
You should have read more.
Go here and follow the instructions. http://forum.xda-developers.com/showpost.php?p=38409721&postcount=1018
Click to expand...
Click to collapse
thanks for pointing that out :silly:...i actually had gone through those steps, BUT, i just realized i had used the wrong folder name...i had "KFFirstAide64" instead of "KFFirstAide" ...KFFirstAide seems to be OK now :good:
anyone know why i have the yellow triangle next to MTP under "Other Devices" in Device Manager, and why the Kindle is not showing up in WIndows Explorer?...anyway to manually get the MTP driver installed properly?...at least the ADP drivers seem to be working
phunzoid said:
thanks for pointing that out :silly:...i actually had gone through those steps, BUT, i just realized i had used the wrong folder name...i had "KFFirstAide64" instead of "KFFirstAide" ...KFFirstAide seems to be OK now :good:
anyone know why i have the yellow triangle next to MTP under "Other Devices" in Device Manager, and why the Kindle is not showing up in WIndows Explorer?...anyway to manually get the MTP driver installed properly?...at least the ADP drivers seem to be working
Click to expand...
Click to collapse
Do you use a Windows 7 N Version? Try this : link
I just got the Kindle fire HD 7 for Christmas but I want to get an app thats only on the Google Play store which the Kindle wont allow us to use.So ive been trying as many tutorials as I can find on how to root the Kindle. The main tutorial ive been trying to follow is this one http://forum.xda-developers.com/showthread.php?t=2351201. But the drivers are not reading the kindle. Yes I have uninstalled the default kindle drivers(which windows keeps installing every time I plug in the usb). The only thing that shows up is a yellow question mark in the devices manager under Other Devices. And yes I also went into the security on my kindle and enabled ADB. Can someone please help out and figure why its not reading my kindle and why there is a yellow question mark on the device manager?
Also I have my Kindle updated to 11.3
heres a picture to help show what im talking about
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
angryhacker said:
I just got the Kindle fire HD 7 for Christmas but I want to get an app thats only on the Google Play store which the Kindle wont allow us to use.So ive been trying as many tutorials as I can find on how to root the Kindle. The main tutorial ive been trying to follow is this one http://forum.xda-developers.com/showthread.php?t=2351201. But the drivers are not reading the kindle. Yes I have uninstalled the default kindle drivers(which windows keeps installing every time I plug in the usb). The only thing that shows up is a yellow question mark in the devices manager under Other Devices. And yes I also went into the security on my kindle and enabled ADB. Can someone please help out and figure why its not reading my kindle and why there is a yellow question mark on the device manager?
Click to expand...
Click to collapse
Windows is not going to let you do this until you disable device driver signature enforcement. Do that and then try the tutorial again. One thing I would do is update manually by searching for the ADB drivers downloaded from that tutorial. Don't do the auto search,
Disable device driver signature enforcement -
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers next time. Following steps 1,2 and 3 in part B of tutorial copy these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
bcdedit /set nointegritychecks ON
bcdedit /set nointegritychecks OFF
Possible Windows 8 cmd
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
Since I don't have Windows 8 to do a personal tutorial, I'll just link to a good tutorial for that.
http://www.fotoclubinc.com/blog/how...on-of-windows-7-printer-drivers-on-windows-8/
I followed your example exactly and got windows into test mode. I forgot to mention I do have windows 7 *64.But the driver is still in other devices and only the default kindle driver seems to be working.Do you know where I can get the latest drivers?I tried searching but i dont know which ones are the latest version.
Try the ones in my signature, they should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Try the ones in my signature, they should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
How do I install it?Theres no exe.
Right click the device in the device manager with the triangle, hit update drivers, then point it to where you extracted my drivers.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Right click the device in the device manager with the triangle, hit update drivers, then point it to where you extracted my drivers.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
It says windows cannot find driver software for your device.
Ok so I installed the updated drivers and got the yellow triangle gone. However the runme bat doesnt work.Its reading my kindle but it keeps saying the specified path does not exist and on a different updated runme bat it says adb not found.The runme bat that I downloaded from the tutorial I posted a link to even reboots my kindle and says its working but at the same time it says no specified path found when going through the prompt steps.And the superuser app doesnt appear on my kindle.
Heres a pic of my changed device manager.Can someone tell me if this is what its supposed to look like?(I tried using both Android composite and the plain ADB but it still didnt work)
angryhacker said:
Ok so I installed the updated drivers and got the yellow triangle gone. However the runme bat doesnt work.Its reading my kindle but it keeps saying the specified path does not exist and on a different updated runme bat it says adb not found.The runme bat that I downloaded from the tutorial I posted a link to even reboots my kindle and says its working but at the same time it says no specified path found when going through the prompt steps.And the superuser app doesnt appear on my kindle.
Heres a pic of my changed device manager.Can someone tell me if this is what its supposed to look like?(I tried using both Android composite and the plain ADB but it still didnt work)
Click to expand...
Click to collapse
that is exactly what it should look like. I just wrote a mini tutorial on the root thread. Someone had a question how to push the files manually. As of now it's the last post on that thread. Try manually pushing them. Also make sure adb is turned on via your tablet.
Im confused what do you mean by manually pushing them?Also ADB is on and it keeps saying cant find C:\windows\system\ric and cant find C:\dloads\GOOGLEKINDLE\RUN ric
C:\dloads\GOOGLEKINDLE\RUN is the folder in which the runme bat and root tool is.
My brother has an android phone so im just going to sideload the app that I wanted onto my kindle when I see him on New Years.Its just too much complicated work dealing with the drivers for a single app.
Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!
Omninano said:
Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
I think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!
Click to expand...
Click to collapse
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish
Datclefxuj said:
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish
Click to expand...
Click to collapse
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!
Omninano said:
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!
Click to expand...
Click to collapse
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:
Datclefxuj said:
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:
Click to expand...
Click to collapse
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!
Omninano said:
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!
Click to expand...
Click to collapse
Great! You're welcome!