[Q] Can't Root My Kindle Fire. - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hi Guys
Been trying for what seems an eternity to root my Kindle Fire HD 7inch..I Cant Install ADB drivers,The PC won't find the Kindle.Also when i try to install ADB drivers,it says drivers already installed,when window's searches for it..it says drivers could not be found for your device..When i look in Device Manager i have a kindle in Portable Devices and Kindle in a place of its own in the list..One is listed as a MPT ?..I can't tell you the driver version of the Kindle,because it simply doesn't show one..Any help would be appreciated.
Thanks In Advance
Wizhunter

Wizhunter said:
Hi Guys
Been trying for what seems an eternity to root my Kindle Fire HD 7inch..I Cant Install ADB drivers,The PC won't find the Kindle.Also when i try to install ADB drivers,it says drivers already installed,when window's searches for it..it says drivers could not be found for your device..When i look in Device Manager i have a kindle in Portable Devices and Kindle in a place of its own in the list..One is listed as a MPT ?..I can't tell you the driver version of the Kindle,because it simply doesn't show one..Any help would be appreciated.
Thanks In Advance
Wizhunter
Click to expand...
Click to collapse
If this helps..i ran a program and the No is 11.3.2.5..i personally have no idea,also whats the difference with a factory cable and a fastboot cable ?

MPT is media transfer or something like that. If you have that, drivers should be installed & working. Have you tried transferring files?
Fastboot is a special cable that uses 5v on pin #4 (typically empty) of the usb cable to force Fastboot mode. This is NOT simply a factory charge cable.

Rushead said:
MPT is media transfer or something like that. If you have that, drivers should be installed & working. Have you tried transferring files?
Fastboot is a special cable that uses 5v on pin #4 (typically empty) of the usb cable to force Fastboot mode. This is NOT simply a factory charge cable.
Click to expand...
Click to collapse
Thanks Rushead,i have all the files on my pc but they wouldn't go to my Kindle..I must of been using a standard cable..I have ordered a fastboot cable and it should be here in the next couple of days
Thanks Again
Wiz :good:

Related

USB Mount Issues (CM7)

Hey, everyone, I tried posting about this in the CM7 general discussion thread, but no one seemed apt to respond.
I think this was a problem that popped up in the 60s or 70s in terms of nightlies, but I'm having it again now since around the 155 mark.
I'm on 160 and when I plug my NC into the USB cable, I no longer get any options to connect for file transfers in the notification area. If anyone could help me out with this, I'd really appreciate it. It's just so perplexing and no one seems be having this issue except me. If it's user-side error, that's fine as well, I'd just like to know how to fix it.
1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?
votinh said:
1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?
Click to expand...
Click to collapse
1. No, nothing comes up.
2. The notification area remains blank.
3. I'm running it off eMMC.
Thanks for taking the time, by the way!
If so, unplug the usb cable then replug in a few times and see what happens.
If still nothing, try to use other usb cable.
Oh, btw, have you had Nookcolotweaks app installed?
I do have Nook Tweaks installed, yes. I'm using the cable that came with the Nook, but I'm not sure I have any other cables around.
Do make sure you check OFF the USB Host feature (reboot and reconnect)
I gave that a try, too, but still nothing. So confusing!
Don't be so hard on yourself.
Let try it on different computer if you have.
Also try difference usb cable.
Last, if nothing works, update latest nightly build
When you disconnect and reconnect the nook in testing/trying to get it recognized... unplug usb cable from computer... its made a difference at times.
I know this sounds basic but in applications-settings ensure you have usb debugging checked. Sometimes when flashing different nightlies, settings change.
Sent from my NookColor using Tapatalk
Thanks again for all the help, everyone! I made sure USB debugging was checked and tried unplugging/replugging the cable, but there's still no notification coming up.
A new development:
I tried connecting it to my Windows PC instead of my Linux and it brought up this message that said it didn't recognize the device. I also tried to get ADB to see it and it can't. Does this information help or am I in trouble here?
Next time, do clearly indicate that you are using Linux or Windows. I'm sure many members here are Linux but still far less support than Windows world.
When I provided those suggestions in previous posts, I meant in Windows.
Anyway, back to your issue.
1. "it didn't recognize the device" because of missing adb usb driver. You need to get it installed first in order to use ADB, however it has nothing to do with your usb mass storage function. For now, you don't need to worry about it just yet.
2. Back to my question before, have you seen any "removable" on the PC (Windows)
Along with USB Host uncheck, if still having problem, I would suggest you either downgrade to the earlier versions or wait until tomorrow and update with another nightly build.
Good luck
I have the ADB drivers installed in Windows, as far as I know. I've used it before.
I typed "adb devices" into the prompt and it doesn't see the NC at all. Since one of the nightlies seems to be what prompted this sudden change in connectivity, I guess I'll just hope that one of the new ones can fix it. Thanks again.
Also, Windows doesn't show anything "removable" except for my external HD.
Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.
arda99 said:
Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.
Click to expand...
Click to collapse
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.
junkrobot said:
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.
Click to expand...
Click to collapse
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
If you've installed ADB drivers, you might want to remove it as this might mess up usb storage.
arda99 said:
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
Click to expand...
Click to collapse
Alrighty. I have those two. I've connected my NC to ADB both wirelessly and and with the cable in the past, so this should all be straightforward anyhow. It just plain refuses to cooperate.
Go to the Marketplace and download "Nook Color UMS" app. Follow instructions and it will mount properly. I had the same issue used it and it mounts proper through the app.

[Q] 2 KFHD - recognised by ADB the other isn't

Hi
I have 2 Kindle Fire HD 7 inch. The 16GB is rooted and can run ADB commands from the latest FirstAide. The other is a new 32GB (arrived today) and I am trying to root it.
In XPs admin tools/computer management, the Android Composite ADB Interface driver is shown. In Properties/general, the rooted device is shown as working normally, whereas the unrooted device is shown as "Currently, this hardware device is not connected to the computer. (Code 45)"
Obviously, trying to use FirstAide to root the new device won't work if ADB isn't working.
As the PC installation is the same, and even the same USB data is being used, there must be something different with the new device. I can't believe that the storage size plays a part so what should I look at? ADB is turned on in the new device (more/device/ADB).
I do have a factory cable but don't know how that can be used in this instance. The new device seems to work normally, and both device and PC have been rebooted/reset to no avail.
Can anyone help or does it look like the device is faulty?
edit: the new device was v7.2.2 but updated itself soon after to 7.2.3 which is the same as the rooted 16GB device
I just used the factory cable and reset the device which went into fastboot mode but didn't respond to any fastboot commands. Switching off and replacing the factory cable with standard data cable saw it boot normally (I thought the boot mode was persistent until reset?)
Maybe try a factory reset on the new one and then turn off wifi until you root it.
Sent from my KFTT using xda premium
If you connected the 32gb kindle before enabling adb at any point you'll want to UNINSTALL its drivers from device manager on your PC and upon reconnect your PC will install the adb version of these drivers assuming adb is enabled.
Let me know how this works for you.
Sent from my KFTT using xda app-developers app
Thanks for the replies. I'm a little confused.
Eventually, I uninstalled the drivers from the PC. I found I couldn't install the drivers using the new FirstAide, I got an error message, so I used the old FirstAide and the drivers installed no problem. From there I could get to root. :laugh:
However, now I find that the old device isn't seen by ADB whilst the new one is..... it's as if the drivers are device specific.
Can anyone explain this to me? In my mind, the drivers, once installed correctly should work for all devices. At the moment, I'm faced with uninstalling/reinstalling drivers whenever I want to swap devices.
victorlugo do you literally mean that if you charge up the device without enabling ADB then you won't be able to install the drivers? As it is, enabling ADB was one of the first things I did, as it was my intention to root it immediately and transfer data from the 16GB model using Titanium.
well, I now have 5 drivers installed covering the 2 devices:
2 x Android ADB Interface
2 x Android Composite ADB Interface
1 x Tate-PVT-08
anyone have any ideas why this might happen? Each device responds to ADB ok, but they use separate drivers

KFFOWI issue

After sending 13 hours working, search and hitting a brick wall, I decide to post. I have full installed all drivers for the my fire (5.1.4) in an attempt to downgrade it. Been to rootjunky and gotten the supertool. Downloaded the full Android Studio. Dow loaded the kindle fire usb driver and the kindle fire HD ADB driver. Downloaded QemuRoot, root_fire. All to no help. Mutilpe computer restarts. Wipe the device and cache. Still nothing. I have used the USB cord it came with and a high quality OEM cord. Still nothing. Been to computer management in an attempt to manually install the driver there. Still nothing. I am at my wits end. As it stands, the kindle when under Amazon system recovery <3e> is not connecting to my computer when I try to apply update from ADB. The message presented by my computer is "KFFOWI-----------------------X no driver found" Any suggestion, ANY WILL BE HELPFUL!
Thank you in advance
edit1: who knew this would be harder to root than the HTC evo 3d paper clip trick
taatoken said:
After sending 13 hours working, search and hitting a brick wall, I decide to post. I have full installed all drivers for the my fire (5.1.4) in an attempt to downgrade it. Been to rootjunky and gotten the supertool. Downloaded the full Android Studio. Dow loaded the kindle fire usb driver and the kindle fire HD ADB driver. Downloaded QemuRoot, root_fire. All to no help. Mutilpe computer restarts. Wipe the device and cache. Still nothing. I have used the USB cord it came with and a high quality OEM cord. Still nothing. Been to computer management in an attempt to manually install the driver there. Still nothing. I am at my wits end. As it stands, the kindle when under Amazon system recovery <3e> is not connecting to my computer when I try to apply update from ADB. The message presented by my computer is "KFFOWI-----------------------X no driver found" Any suggestion, ANY WILL BE HELPFUL!
Thank you in advance
edit1: who knew this would be harder to root than the HTC evo 3d paper clip trick
Click to expand...
Click to collapse
Bump
Solution
Here you have it:
Install manually in the windows drivers list, Fire Device -Android composite ADB interface, over KFFOWI. Then install Stock Rom via ADB. Enjoy!
taatoken said:
After sending 13 hours working, search and hitting a brick wall, I decide to post. I have full installed all drivers for the my fire (5.1.4) in an attempt to downgrade it. Been to rootjunky and gotten the supertool. Downloaded the full Android Studio. Dow loaded the kindle fire usb driver and the kindle fire HD ADB driver. Downloaded QemuRoot, root_fire. All to no help. Mutilpe computer restarts. Wipe the device and cache. Still nothing. I have used the USB cord it came with and a high quality OEM cord. Still nothing. Been to computer management in an attempt to manually install the driver there. Still nothing. I am at my wits end. As it stands, the kindle when under Amazon system recovery <3e> is not connecting to my computer when I try to apply update from ADB. The message presented by my computer is "KFFOWI-----------------------X no driver found" Any suggestion, ANY WILL BE HELPFUL!
Thank you in advance
edit1: who knew this would be harder to root than the HTC evo 3d paper clip trick
Click to expand...
Click to collapse
I have the same problem, how do you install driver manually? On Windows I have only the update driver option and when I give him the location of adb USB driver. Windows tell me that there is no driver available for the device...
Any updates? I hit the exact same problem, tried everything online, still I cannot find a suitable driver for the "Kffowi" (with exclamation mark)..
Driver install
Go to device manager, right click on KFFOWI, click on update driver. Click Browse my computer. On the next screen, click the bottom option, "Let me pick from a list of device drivers on my computer".
Scroll down and click on Fire Devices
Look for "Android Composite ADB Interface" and select it, then hit next.
Driver will install, confirm that you want windows to use the driver, and bam. Done.
Problem solved
Running LineageOS 12.1-20181218-UNOFFICIAL-ford. amonet-ford-v1.4.1 installed on PC and rebooted. There isn't even the sound that a new USB-device is connected nor anything happening in the Windows device manager when pluggin in KFFOWI. Enable Android debugging is grayed out. How should I proceed, if I wan to upgrade to [ford,austin] Lineage-14.1 [17 JAN 2021]?
LineageOS 12.1-20181218-UNOFFICIAL-ford is working fine, but has become very slow.
​​

ADB won't see my BLU R1 HD

Hi. I've been trying for hours to get Helium backup to work with my R1 and it won't work. My G4 works fine with the same USB port and cable. When my G4 is plugged in, if I type adb devices, it shows up. The BLU phone does not show up. I've tried uninstalling and installing Helium in my computer and in the phone. I did a hard reset on the phone. I downloaded and installed the drivers Helium recommends and nothing. I simply can't make the R1 work. I've noticed a few people having the same problem in other forums but I haven't found a fix for it.
Anyone can give me some ideas? Thanks.
Did you enable usb debugging. Not calling you an android dummy but we have all forgot to enable usb debugging one time or uhnutha.
Yeah, I enabled it.
Another day trying to get adb to see my phone and nothing. I installed mtk drivers, etc and I'm still getting a blank when typing "adb devices"...
Are you using the cable from Blu? I noticed that my other devices work fine with any cable, but the R1 only seems to respond with the Blu provided USB cable.
Yeah, I started using the BLU cable just in case and it didn't make a difference.
Sent from my VS986 using Tapatalk
My phone recognizes ADB perfectly in TWRP but I cannot get adb to work with the system up.
Not a cable or adb drivers.
king200 said:
My phone recognizes ADB perfectly in TWRP but I cannot get adb to work with the system up.
Not a cable or adb drivers.
Click to expand...
Click to collapse
Don't be so sure it's not driver, because while in recovery and while in system the phone reports different mode to PC, so could be using different driver
Try going into device manager in Windows and updating the driver. Select choose from available drivers, and if there's one that's different than what is currently loaded, try that one.
Sent from my BLU R1 HD using Tapatalk
Vendor ID issue, you need to update the adb_usb.ini to include it.
I got adb to see my R1 under Windows. When you plug it in, change from MTP mode to PTP mode and unplug it, then plug back in. It works in PTP mode but not MTP mode for some odd reason.
Synir said:
Vendor ID issue, you need to update the adb_usb.ini to include it.
Click to expand...
Click to collapse
What is the proper vendor entry. What is your entries. Currently I have:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
0x12D1
king200 said:
What is the proper vendor entry. What is your entries. Currently I have:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
0x12D1
Click to expand...
Click to collapse
did it work?
Has anyone solved this issue yet?
i cant seem to figure out how to get adb to work with this phone. need help im on 6.6 and no step by step instructions on how to either roll back or just install a new rom.
pookeye said:
i cant seem to figure out how to get adb to work with this phone. need help im on 6.6 and no step by step instructions on how to either roll back or just install a new rom.
Click to expand...
Click to collapse
ADB just "works" for so many users, It leaves the dumb question . Did you enable developer options and turn adb debugging?
Also what abd are you using?
Easiest thing to do would be reinstall adb + fastboot with 15 second install.
link to that is in the unlock tool thread. Which will also answer your question what is needed to install new / other rom.
(tool unlocks bootloader, flash twrp, can install superSU,)

No OS installed, boots to TWRP but PC does not recognise device

So I've got a 3T which currently has no OS installed, just the TWRP3.2.3-0. The problem is that every time I connect the phone to the PC, the PC will only recognise the phone as Unknown USB device (Device Descriptor Request Failed). Due to this I cannot use adb to transfer files to the phone or transfer files directly to the internal storage.
I have tried using Minimal adb but device isn't found, tried different USB ports and cables too. For some reason the recovery does not read devices attached to OTG as I have also tried to transfer files using this method.
Any suggestions as to what I can do to make my PC recognise this device? Thanks
first of all check your usb cable then use this op3/t tool
it will install all drivers, unlock, decrypt, install twrp and dm-verity issue solution
https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/toolkit-root-recovery-drivers-t3651138
Hayatzada said:
first of all check your usb cable then use this op3/t tool
Click to expand...
Click to collapse
device isn't found, tried different USB ports and cables too
Click to expand...
Click to collapse
So yeah.
 @op USB port in the phone is damaged
Hayatzada said:
first of all check your usb cable then use this op3/t tool
it will install all drivers, unlock, decrypt, install twrp and dm-verity issue solution
https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/toolkit-root-recovery-drivers-t3651138
Click to expand...
Click to collapse
But I cannot enable USB debugging since there is no OS installed, however I have not yet tested this program.
The USB port was working normally before the OS was removed. This problem started once there was no OS and just recovery. Is there truly no other way I can transfer the ROM to the phone? Thanks for your help
J-_-M-_-C said:
But I cannot enable USB debugging since there is no OS installed, however I have not yet tested this program.
The USB port was working normally before the OS was removed. This problem started once there was no OS and just recovery. Is there truly no other way I can transfer the ROM to the phone? Thanks for your help
Click to expand...
Click to collapse
while having TWRP installed pc should recognize your phone, if encrypted phone shows Oneplus 3 in my computer Location without showing internal storage,
Check your USB cable, then boot into fastboot(Boot loader By pressing Power & volume up button together while phone is in off state) connect your cable to pc and phone and run the tool, to install op3 driver select number from your pc
install driver (1)
unlock bootloader (3)
decrypt(10)
install twrp (5)
boot into TWRP from fastboot screen select recovery and reboot
Push superSU (7) (it'll copy superSU into internal memory) install supersu otherwise phone lose root and go back to encrypted state and you cant see internal storage in pc
reboot into recovery and copy your rom, gapps and Magisk 17.1, install them
You are done now
Hayatzada said:
while having TWRP installed pc should recognize your phone, if encrypted phone shows Oneplus 3 in my computer Location without showing internal storage,
Check your USB cable, then boot into fastboot(Boot loader By pressing Power & volume up button together while phone is in off state) connect your cable to pc and phone and run the tool, to install op3 driver select number from your pc
install driver (1)
unlock bootloader (3)
decrypt(10)
install twrp (5)
boot into TWRP from fastboot screen select recovery and reboot
Push superSU (7) (it'll copy superSU into internal memory) install supersu otherwise phone lose root and go back to encrypted state and you cant see internal storage in pc
reboot into recovery and copy your rom, gapps and Magisk 17.1, install them
You are done now
Click to expand...
Click to collapse
Thank you for this information, however I get as far as installing the drivers but the PC still shows phone as Unknown USB Device (Device Descriptor Request Failed) and therefore the program does not find the phone. Tried this on two different PC's.
Go to advance in TWRP then click on sideload and flash the os using sideload command i. e. adb sideload filename. zip
J-_-M-_-C said:
Thank you for this information, however I get as far as installing the drivers but the PC still shows phone as Unknown USB Device (Device Descriptor Request Failed) and therefore the program does not find the phone. Tried this on two different PC's.
Click to expand...
Click to collapse
please please please check your cable
johnybravo.1981 said:
Go to advance in TWRP then click on sideload and flash the os using sideload command i. e. adb sideload filename. zip
Click to expand...
Click to collapse
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
J-_-M-_-C said:
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
Click to expand...
Click to collapse
i have the exact same problem as u my friend i had that problem so i just sideloaded my stock rom and searching for a method to fix this if u find a way to make the device recognised in twrp pls let me know
J-_-M-_-C said:
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
Click to expand...
Click to collapse
Just sideload dude. I came across the same issue 2 days ago.
Or flash using usb otg.
johnybravo.1981 said:
Just sideload dude. I came across the same issue 2 days ago.
Or flash using usb otg.
Click to expand...
Click to collapse
I have tried using USB OTG but the recovery does not detect my connected usb drive. Regarding sideload, when I boot to recovery and select adb sideload, and connect the phone to my PC I get a USB device not recognised message. The commands adb devices and fastboot devices do not list my phone.
J-_-M-_-C said:
I have tried using USB OTG but the recovery does not detect my connected usb drive. Regarding sideload, when I boot to recovery and select adb sideload, and connect the phone to my PC I get a USB device not recognised message. The commands adb devices and fastboot devices do not list my phone.
Click to expand...
Click to collapse
Try this guide if your phone detects as Qualcomm in device manager then proceed otherwise check your charging port (type c port) as you mention usb otg didn't detected and usb cable worked with other phones.
don't forget to clean your type c port if dirty or rusted. :good:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Hayatzada said:
Try this guide if your phone detects as Qualcomm in device manager then proceed otherwise check your charging port (type c port) as you mention usb otg didn't detected and usb cable worked with other phones.
don't forget to clean your type c port if dirty or rusted. :good:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
I have tried to install the qualcomm driver but when I go to Device Manager -> Update Driver -> Have Disk and select the qcser.inf file I get the following message: "The folder you have specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems." I have disabled driver signature verification. No idea why nothing seems to be working.
J-_-M-_-C said:
I have tried to install the qualcomm driver but when I go to Device Manager -> Update Driver -> Have Disk and select the qcser.inf file I get the following message: "The folder you have specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems." I have disabled driver signature verification. No idea why nothing seems to be working.
Click to expand...
Click to collapse
which method do you try? i suggest full method, first one didn't worked for me .
Hayatzada said:
which method do you try? i suggest full method, first one didn't worked for me .
Click to expand...
Click to collapse
I have tried Method 1 and arrived till step 6. Then when I try to select the file I get the error I mentioned in my previous post.
J-_-M-_-C said:
I have tried Method 1 and arrived till step 6. Then when I try to select the file I get the error I mentioned in my previous post.
Click to expand...
Click to collapse
try to connect otg keyboard and type in TWRP advance section selecting terminal
if keyboard works, your type c port is ok otherwise change or repair the port
Hayatzada said:
try to connect otg keyboard and type in TWRP advance section selecting terminal
if keyboard works, your type c port is ok otherwise change or repair the port
Click to expand...
Click to collapse
Tried to connect a keyboard with otg and it did not work with this phone. It worked fine using the same otg cable on another phone.
J-_-M-_-C said:
Tried to connect a keyboard with otg and it did not work with this phone. It worked fine using the same otg cable on another phone.
Click to expand...
Click to collapse
now you should go for a hardware repair of Type C port
Hayatzada said:
now you should go for a hardware repair of Type C port
Click to expand...
Click to collapse
I already said that at the beginning.

Categories

Resources