I've been trying to root my kindle fire for the last 6 hours now. I keep getting hung up with ADB not finding it. Everyone seems to magically fix it and then disappear without saying how they got it to work, hahaha.
I have tried everything I can find. Set the .inf file, set drivers, anything. I get the feeling that I'm missing something really obvious, but I can't figure it out. Any help would be very greatly appreciated, thanks!
Win 32/64 (tried on both)
Kindle Fire 6.2.2
No roots, no nothing
KFU says:
ADB Status: Offline
ADB Rooted: No
Boot Status: Unknown
Right now I need sleep, but please please let me know if you have any suggestions!
I am in the same boat..any luck?
KFU Problem
Does your device manager say "Android Phone" followed by " Android Composite ADB device " below it? Your device manager has to say this ( exactly, not just Android adb device or Android Composite Device) before you can access your KF correctly.
If you don't see the correct Android device showing up then Google this "how-to-install-kindle-fire-adb-usb-driver"
and there should be a good walkthrough as the first search result.
If you do see the correct entry then I'm sorry, I don't have enough experience with that specific problem to help you.
I'm in the same boat, and my kindle is definitely seen as the composite device.
Related
Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.
Update driver
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.
ShreddinPB said:
Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.
Click to expand...
Click to collapse
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.
Emul8or said:
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.
Click to expand...
Click to collapse
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
it2steve said:
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.
Click to expand...
Click to collapse
There is a fix posted for the slowdown issue after resume from sleep, and you ADB to fix it
ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Here's what dev mgr looks like on XP...
Jim
ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.
davinci07 said:
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.
Click to expand...
Click to collapse
Found it.. it was under "Universal Serial Bus Controllers" and called "USB storage device" i believe.
I tried updating the driver with the andoid one, but it errored out and wouldnt load it. After that however, 2 new devices popped up.. both the Nvidia harmony drive, and another nvidia tegra one. The harmony drivers failed to load.. so I pointed at the directory in the SDK and bam it works!!
Thanks guys!
But also btw.. before I got this working, I did use ADBWireless to run the adb shell and run that camand mentioned in the main thread that is supposed to stop the slow downs.. and I think its working.
enjoy, can you point me to the post that you needed this for? Also, now that ADB works you can start making your own apps. With either Eclipse and Android SDK (more advance route, but there is alot of good books that could help you alot) or with app invnetor that just got released to the public.
Can anyone please help me...?
I'm running Windows XP, using the Kindle Fire Utility, and have installed Android SDK Tools. I'm attempting to root a Kindle Fire running 6.3.1.
I have followed instructions (from here and elsewhere), and while the KFU driver installer would not install the proper drivers, I WAS able to direct Windows to the driver folder and have it install them directly. Afterward, Windows had no problem seeing (in Device Manager) the KF as 'Android Composite ADB Interface', indicating the drivers are correct.
Now the problem. No matter what I do, I can't get ANY of the root systems (KFU or SDK Tools) to see the device when it is connected. Tried to use Fastboot command to change the boot loader to 4002 fastboot mode, but it also hangs on '< waiting for device >'...
I can see the device as a mass storage device in 'My Computer' and can add or delete files from it without issue, but I just can't make any progress rooting this thing without the appropriate programs being able to see it!
I HATE feeling stupid, and this thing is REALLY making me feel like I'M the idiot that can't see what's right in front of his face! Can someone PLEASE light the neon sign that will finally illuminate what my obviously lacking vision refuses to see?? (T_T)
Thank you for taking the time to read all this, and thank you to ANYONE who answers with ANY useful information! I'll be watching, and waiting with baited breath for SOME sort of assistance...
-Asuka Jr.
<update> 120 views now, and not even a scathing remark about how much of a moronic noob I am... While waiting, I went to PCWorld, and tried to follow their step-by-step, downloading Firefirefire, fbmode, TWRP, AOKP, and Google Aps for AOKP release 38. Once again, attempted to follow directions, and once again, get one of the dreaded variants 'device not found' when trying to use adb to push the fbmode file to the KF... (T_T)
SOLVED!!
It WAS a driver issue! I would like to say:
Thank you, thank you, THANK YOU!!! To josepho1997!
He posted a link to a set of drivers that was EXACTLY what I needed to get the Kindle to be recognized by root software!
KF is now fully rooted and flashed, and running IceCream Sandwich!!
Sorry I posted this whole thing here, instead of in the Q&A for the Kindle Fire... for some reason, I thought that was where I was, but later noticed otherwise...
To admin: please feel free to delete this whole topic, as it wasn't in the right place to begin with...
Once again, thank you to josepho1997 for his post to themagicm containing the link to the FAR better driver set!!!
-Asuka Jr.
I tried searching everywhere and was not able to find a solution.
When I run it, the following texts appear and then hangs indefinitely.
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
From what I've found after searching, people have solved it by reinstalling driver, but it does not work for me.
I set both the security setting and USB debug setting, and driver is correctly installed.
I also tried following this video tutorial (http://forum.xda-developers.com/showthread.php?t=1798586), but that is pretty much what I did in the first place and that Debugfs hangs at the same spot.
I am new to an Android device. I own an iPhone which I jailbroke, but I am moving away from Apple. All I am trying to do right now is trying to change the dock keyboard layout, which apparently requires rooting.
Any help would be appreciated.
The text is fine, but it should go from there smoothly. Do you have ASUS sync installed and running? If so, kill it and kill it with a heavy stab.
Does your PC recognise the Infinity when you plug in the USB cable?
d14b0ll0s said:
The text is fine, but it should go from there smoothly. Do you have ASUS sync installed and running? If so, kill it and kill it with a heavy stab.
Does your PC recognise the Infinity when you plug in the USB cable?
Click to expand...
Click to collapse
ASUS sync is not installed on my computer and it's disabled on the tablet. My computer recognizes it when it's connected.
Sounds like a classic "it should work" situation.
Try it on a different PC perhaps. You may have some third-party software installed that's interacting with the adb. Hard to tell without looking into it really. When you try to use custom commands in adb, not the .bat file, does anything work? What does waiting for device report?
^^^ this
I know this from experience, that not all Windows PC's are created equal. I had an issue rooting my tablet on 2 Windows XP machines and one Windows 7. The final Windows 7 machine I tried magically worked. All had admin access and no restrictions.
qnfauf said:
I tried searching everywhere and was not able to find a solution.
When I run it, the following texts appear and then hangs indefinitely.
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
From what I've found after searching, people have solved it by reinstalling driver, but it does not work for me.
I set both the security setting and USB debug setting, and driver is correctly installed.
I also tried following this video tutorial (http://forum.xda-developers.com/showthread.php?t=1798586), but that is pretty much what I did in the first place and that Debugfs hangs at the same spot.
I am new to an Android device. I own an iPhone which I jailbroke, but I am moving away from Apple. All I am trying to do right now is trying to change the dock keyboard layout, which apparently requires rooting.
Any help would be appreciated.
Click to expand...
Click to collapse
If you have adb setup properly you should be able to type "adb devices" from a command prompt. If all is well you will see your tablets serial number listed. If adb isn't setup properly, well you won't see anything.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Thanks for all the help. I don't really have another computer I can use right now.
newellj79 said:
If you have adb setup properly you should be able to type "adb devices" from a command prompt. If all is well you will see your tablets serial number listed. If adb isn't setup properly, well you won't see anything.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
When I type "adb devices", it says
"List of devices attached" and two blank lines. I guess adb does not see my device. Am I doing something wrong?
I am having the *exact* same issue. I'm not sure what the deal is - I recently used ADB to root my SGS3 so it definitely boggles my mind as to why it's not working on my tablet.
Just wanted you to know you weren't the only one. I'm going to try reinstalling ADB drivers later tonight to see if maybe something is wrong on that front...
---------- Post added at 09:26 PM ---------- Previous post was at 09:15 PM ----------
Okay, let me explain how I got this to work.
First of all, the xda post you referenced has a link to a bad set of drivers. (Don't worry, it got me too at first, shame on that XDA poster for stealing credit in the first place...)
So, go here (http://forum.xda-developers.com/showthread.php?t=1706588) and download the ASUS Android Drivers USB.zip as well as as the rootdebugfs that is there.
Next, open your device manager - the reason I keyed into this is because there was a driver that said "ASUS Android Composite ADB Interface" that did not install properly. Unzip the ASUS Android Drivers and then right click on "ASUS Android Composite ADB Interface" and update the drivers, manually point to the folder that contains all of the ASUS Android Drivers and click ok, it should update your drivers CORRECTLY (You'll get a successfully updated drivers window). After that try using the rootdebugfs bat again, worked like a charm for me after that!
If you're still having issues, please let me know, and post a screenshot of your device manager if you don't mind, it could be the key to your issues as well.
Sorry for the long post, hope I made sense
Forcepath said:
I am having the *exact* same issue. I'm not sure what the deal is - I recently used ADB to root my SGS3 so it definitely boggles my mind as to why it's not working on my tablet.
Just wanted you to know you weren't the only one. I'm going to try reinstalling ADB drivers later tonight to see if maybe something is wrong on that front...
---------- Post added at 09:26 PM ---------- Previous post was at 09:15 PM ----------
Okay, let me explain how I got this to work.
First of all, the xda post you referenced has a link to a bad set of drivers. (Don't worry, it got me too at first, shame on that XDA poster for stealing credit in the first place...)
So, go here (http://forum.xda-developers.com/showthread.php?t=1706588) and download the ASUS Android Drivers USB.zip as well as as the rootdebugfs that is there.
Next, open your device manager - the reason I keyed into this is because there was a driver that said "ASUS Android Composite ADB Interface" that did not install properly. Unzip the ASUS Android Drivers and then right click on "ASUS Android Composite ADB Interface" and update the drivers, manually point to the folder that contains all of the ASUS Android Drivers and click ok, it should update your drivers CORRECTLY (You'll get a successfully updated drivers window). After that try using the rootdebugfs bat again, worked like a charm for me after that!
If you're still having issues, please let me know, and post a screenshot of your device manager if you don't mind, it could be the key to your issues as well.
Sorry for the long post, hope I made sense
Click to expand...
Click to collapse
Thank you, that worked!
In the process of trying to get it to work, I definitely saw "ASUS Android Composite ADB Interface" a few times in device manager. After reading your post, I could not get it to show. I tried uninstalling the driver, searching for new hardware, etc. to no avail. However, switching the USB connection type from MTP to PTP while the device manager was running (I'm not sure why it had to be running) made it show up. Then I used the correct driver files to install the driver and the root worked. That guy who put up the video tutorial apparently put wrong drivers.
mtp to ptp
qnfauf said:
Thank you, that worked!
In the process of trying to get it to work, I definitely saw "ASUS Android Composite ADB Interface" a few times in device manager. After reading your post, I could not get it to show. I tried uninstalling the driver, searching for new hardware, etc. to no avail. However, switching the USB connection type from MTP to PTP while the device manager was running (I'm not sure why it had to be running) made it show up. Then I used the correct driver files to install the driver and the root worked. That guy who put up the video tutorial apparently put wrong drivers.
Click to expand...
Click to collapse
switching from mtp to ptp fixed it for me. it caused the device manager see an new device, which then had a yellow triangle. i just right clicked on it and hit refresh, and it installed the driver. g2g after that.
I had same problem but its solved now n its just drivers problem
just google "phones_brand_name usb drivers"
download and install them
n you are done
Hello,
My Kindle Fire HD 7" (model # P48WVB4) got stuck in a bootloop. The kindle is used to play games and I am not aware of anything special that was being done at the time this happened. I can get into the kindle menu after typing the kindle password for just a few seconds and it looks normal, and then reboots. We got a fastboot cable which seems to work fine, and displays "Fastboot kindle fire". I can attach it to my desktop computer running Windows XP and updated the drivers such that it properly shows up under devices as "Kindle Fire" -> "Android ADB Interface".
I have installed the ADK onto the desktop and tried running the "adb devices" and "fastboot devices" commands. These say "List of devices attached" but the list is blank; it does not show my device.
Any help would be appreciated.
I would very much like to preserve the game data on this unrooted device. There are a couple games I have been able to back up by finding directories where they live, or saving them to facebook, but there are others which I could not figure out how to back up (perhaps I could if I had rooted the device when I got it).
Thanks
ratkins said:
Hello,
My Kindle Fire HD 7" (model # P48WVB4) got stuck in a bootloop. The kindle is used to play games and I am not aware of anything special that was being done at the time this happened. I can get into the kindle menu after typing the kindle password for just a few seconds and it looks normal, and then reboots. We got a fastboot cable which seems to work fine, and displays "Fastboot kindle fire". I can attach it to my desktop computer running Windows XP and updated the drivers such that it properly shows up under devices as "Kindle Fire" -> "Android ADB Interface".
I have installed the ADK onto the desktop and tried running the "adb devices" and "fastboot devices" commands. These say "List of devices attached" but the list is blank; it does not show my device.
Any help would be appreciated.
I would very much like to preserve the game data on this unrooted device. There are a couple games I have been able to back up by finding directories where they live, or saving them to facebook, but there are others which I could not figure out how to back up (perhaps I could if I had rooted the device when I got it).
Thanks
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
Please direct your question here:
http://forum.xda-developers.com/kindle-fire-hd/7-inch-help
That's the help forum specifically for your device. You'll get the expert advice you need there.
Good luck!
Thread closed.
Total noob. Have had this old thing sitting around for a while after a failed root attempt. Kingroot, I think? Been trolling through past threads to try to find a solution so I can use it for whatever but I'm a little stupid.
PC is Windows 10 64x. The Kindle persistently displays the fire logo, with a swiping flash from left to right.
Android SDK is installed, as well as the Google Driver. I have modified both android_winusb and the inf file to have proper values, but the device is not being detected by the adb command or in device manager at all. Couldn't find an answer in terms i could understand to this. I understand that the first step is to have the device detected, but I am unsure how to do that.
nebulanebula said:
Total noob. Have had this old thing sitting around for a while after a failed root attempt. Kingroot, I think? Been trolling through past threads to try to find a solution so I can use it for whatever but I'm a little stupid.
PC is Windows 10 64x. The Kindle persistently displays the fire logo, with a swiping flash from left to right.
Android SDK is installed, as well as the Google Driver. I have modified both android_winusb and the inf file to have proper values, but the device is not being detected by the adb command or in device manager at all. Couldn't find an answer in terms i could understand to this. I understand that the first step is to have the device detected, but I am unsure how to do that.
Click to expand...
Click to collapse
Last I saw Fire OS 5.3.1.0 was the last version rootable with Kingroot.
Try looking here for help
Amazon Fire
The Amazon Fire is a budget tablet released in September 2015. It runs on Amazon's Android Lollipop based Fire OS 5, which provides easy access to Amazon's online features. The Amazon Fire has a 7" 1024 x 600 display, 1.3GHz quad-core processor, 1GB of RAM, 8GB internal storage, microSD...
forum.xda-developers.com
nebulanebula said:
Android SDK is installed, as well as the Google Driver. I have modified both android_winusb and the inf file to have proper values, but the device is not being detected by the adb command or in device manager at all. Couldn't find an answer in terms i could understand to this. I understand that the first step is to have the device detected, but I am unsure how to do that.
Click to expand...
Click to collapse
The mentioned Google Driver - as it name implies - is for Google devices only: You have to install the Kindle Fire USB driver instead to get things working as expected.