Operating System: Windows 7 Ultimate 64 Bit
Kindle 7" HD Fire
7.2.3
I've looked everywhere for a fix to this but can't find anything which helps me. I apologise that my first post is asking for help but I'm really struggling with this at the moment, any assistance would be greatly appreciated.
Basically, I got my Kindle HD Fire 7" on 7.2.3 firmware and the first thing I wanted to do was root it. I followed different methods which just led to weird system path errors. I was eventually directed to a post on this site which was really well written: http://forum.xda-developers.com/showthread.php?t=2069117
I followed this guide to get rid of all the current drivers: http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361 after I had re-installed the drivers, the first time I plugged the kindle into my laptop.
The driver installation came up with this:
{
"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"
}
The guide said "Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface".
However when I look at my device manager is just shows this when the kindle is plugged in:
I believe this is where the problem is, although I can transfer files. I don't think the ADB is recognising my Kindle.
I thought, "I may aswell continue with the rest of the guide" however when I ran "KF First Aide" these are the errors I got
Option 15:
Option 16:
When I run the ADB kill/start server device commands:
If anyone could come forward with a solution for this I'd be very thankful.
The kindle will be shown as kindle.... under nothing. Not under portable devices. My guess would be that the driver is installed incorrectly or it's the wrong driver. Have you tried rolling the driver back?
Did you enable ADB under security??
Sent from my KFTT using Tapatalk 2
Krsmqn said:
The kindle will be shown as kindle.... under nothing. Not under portable devices. My guess would be that the driver is installed incorrectly or it's the wrong driver. Have you tried rolling the driver back?
Click to expand...
Click to collapse
I installed the drivers as instructed by the guide. What does rolling the driver back mean?
jailuis said:
Did you enable ADB under security??
Sent from my KFTT using Tapatalk 2
Click to expand...
Click to collapse
Yes
xl2onald- said:
Click to expand...
Click to collapse
This says your adb is connected.
This means adb.exe and fastboot.exe are not in the same directory that the script was run from.
Does that help?
Sent from my KFHD 8.9 using Tapatalk 2
I had more luck rooting my kindle using the alternative step instead of using the first aide software.
It is under the heading:
C-2) The next steps are used to Root the Kindle - Alternative Method (Manual Version): in the first post of their thread. Extract the win32 or win64 folder onto your desktop and run the RunMe.bat as admin.
Though soupmagnet's diagnostic is correct so have a look at that first.
Related
For some reason I cannot get ADB to work with my NC. I cleaned out ADB and reinstalled with all updates except for the Galaxy Tab add ons. I used the driver that is available all over the forum and got the proper device id in device manager. When I try to check devices I just get nothing connected. Does anyone have any ideas? Any help is appreciated. Device manager also still has the USB as mass storage also.
*Running Win 7 x64
{
"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"
}
Uninstall the Android Composite ADB Interface driver
Download the updated adb drivers from here
http://forum.xda-developers.com/showthread.php?t=882751
and reinstall them. A reboot of your pc should show your device.
So nooks good just no adb via PC? Win7 64bit puts it c:/program files (x84)/android/android-sdk-windows/platform-tools
If not just type adb.exe in the search box above winows start
sent from a Nook Color using xda-app
thanks for the responses.
camwinnn said:
So nooks good just no adb via PC? Win7 64bit puts it c:/program files (x84)/android/android-sdk-windows/platform-tools
If not just type adb.exe in the search box above winows start
Click to expand...
Click to collapse
ADB is not the issue, it must be some kind of driver problem. the SDK is in my path, it will run no matter what directory im in. It works fine on the vibrant.
ewong90 said:
Uninstall the Android Composite ADB Interface driver
Download the updated adb drivers from here
http://forum.xda-developers.com/showthread.php?t=882751
and reinstall them. A reboot of your pc should show your device.
Click to expand...
Click to collapse
thats what I used orginally to get to this point. plus the 1.01 image. I tried it again just to be sure. The composite device shows when plugged in but so does the mass storage, does that matter? should the storage still mount?
Here is what I have for drivers.
uninstall all the nook mass storage device drivers
ewong90 said:
uninstall all the nook mass storage device drivers
Click to expand...
Click to collapse
Here is what I did, (just to be clear)
Plugged in Rooted Nook.
Uninstalled USB Mass storage
right clicked "nook" and hit update driver
selected driver from downloaded Win7 post
clicked install unsigned driver
adb composite device showed up
reboot
plugged nook back in, now both USB storage and Adb composite device show up
Be lazy, get adb wireless from the market. I didn't even bother setting up my PC
sent from a Nook Color using xda-app
There's a thread somewhere around here with a solution that worked for me, it involved adding 0x2080 to the adb_USB.initial file in /user/yourname/.android.
Edit: Oh yeah, adbwireless is awesome so give that a try if you can't get USB to work.
+1 for AdbWireless!!!
Its free and you can get it from the market.
(I finally gave up after days of trying to get the usb drivers figured out on my computer.)
camwinnn said:
Be lazy, get adb wireless from the market. I didn't even bother setting up my PC
sent from a Nook Color using xda-app
Click to expand...
Click to collapse
Didnt even think of that. I use it for my Vibrant and love it. thanks.
My wireless works great...but I still need the usb connection to modify wireless settings to allow connection to adhoc network (mywi on iPhone 4).
I've tried everything and am still having a problem.
I am running a Windows Vista machine. When I attempt to install the USB drivers, it runs through the steps, but at the end, it says:
"Windows found driver software for your device but encountered an error while attempting to install it.
Android Composite ADB Interface
The data is invalid.
If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
I've cleared it all and still have the same problem.
I ran it on an XP machine, and was able to install the drivers, however, the nook still does not show up in the list of devices.
Any ideas?
Noob question for sure, sorry. I'm studying up and getting ready to root my Droid Bonic. I have installed the Motorola Device Manger for drivers. I checked the device manager per the instructions and yes with debugging on and the Media device (MTP) on the ADB Interface, "Mot Composite ADB Interface" does show in my device manager but I see there's an issue of some sort with "Portable Devices/ MTP !" Should I be concerned with this?
{
"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"
}
Thanks,
Marty
Sys Version 6.7.246
Android Version 4.0.4
Build 6.7.2.223
Windows xp SP3
martyslc said:
Noob question for sure, sorry. I'm studying up and getting ready to root my Droid Bonic. I have installed the Motorola Device Manger for drivers. I checked the device manager per the instructions and yes with debugging on and the Media device (MTP) on the ADB Interface, "Mot Composite ADB Interface" does show in my device manager but I see there's an issue of some sort with "Portable Devices/ MTP !" Should I be concerned with this?
Thanks,
Marty
Sys Version 6.7.246
Android Version 4.0.4
Build 6.7.2.223
Windows xp SP3
Click to expand...
Click to collapse
I'm thinking it should say "Droid Bionic" but not sure how to get it to show?? Maybe it wont in xp?
Any idea's??
-Marty
XP has a really hard time enumerating and loading the drivers for the MTP device. You can basically ignore it for the purposes of manipulating the phone as all the other interfaces for fast boot and diagnostic mode etc. load properly and function under XP.
cellzealot said:
XP has a really hard time enumerating and loading the drivers for the MTP device. You can basically ignore it for the purposes of manipulating the phone as all the other interfaces for fast boot and diagnostic mode etc. load properly and function under XP.
Click to expand...
Click to collapse
Thank You !
cellzealot said:
XP has a really hard time enumerating and loading the drivers for the MTP device. You can basically ignore it for the purposes of manipulating the phone as all the other interfaces for fast boot and diagnostic mode etc. load properly and function under XP.
Click to expand...
Click to collapse
Thank You !
I'm sure there have been some other topics about this, but I haven't found a post that fixes my issue, or applies to my situation. I will gladly read though any linked posts to try to fix the problem.
All ADB commands that KFFirstAide does are successful, but when I try using ADB on my own (trying to install the bootloader) it can't find the device. What am I doing wrong?
I would use KFFirstAide to install the bootloader, but I'm running 7.3.0, and so I have to do it manually
I have been running it from the platform-tools directory. I thought that maybe because on windows 7 files in the C:\Program Files (x86)\ directory are somewhat protected, that I should copy the folder to the desktop. I did so, and it still cannot find the device when running "adb devices" command. I then tried using the admin command prompt, and it couldn't find the device either.
There are no yellow triangles in the device manager, and commands issued by KF First Aide work fine, so I'm not sure why it's not working manually...
Thanks in advance for any help!
I followed the tutorial rev Kyle have on getting adb working and have never had a problem... google rev Kyle kindle fire hd forum
Sent from my GT-P3110 using xda app-developers app
After watching this video, Rev Kyle suggested that the Android SDK might not be properly installed. I currently do not have good internet, so is there any way I can check to see if the SDK is properly installed without re-installing it?
Here is a pic of what is going on
{
"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"
}
kthedude said:
All ADB commands that KFFirstAide does are successful, but when I try using ADB on my own (trying to install the bootloader) it can't find the device. What am I doing wrong?
Click to expand...
Click to collapse
ADB works fine with my Kindle Fire HD 7". I'm using Windows 7. Try to kill ADB server from the Windows task manager, and run "adb devices" again. Also, try to connect/reconnect your device from USB a few times.
I've done all of this. The thing that puzzles me is that kindle fire first aide uses adb of its own, right? As you can see in my picture, KFFA finds the device using its adb, but when I run adb through the command prompt it cannot find the device. In the picture above, I used both programs within the same minute. How can it work one way but not the other?
Would wiping the kindle help in any way?
Sent from my KFTT using xda app-developers app
kthedude said:
I've done all of this. The thing that puzzles me is that kindle fire first aide uses adb of its own, right? As you can see in my picture, KFFA finds the device using its adb, but when I run adb through the command prompt it cannot find the device. In the picture above, I used both programs within the same minute. How can it work one way but not the other?
Would wiping the kindle help in any way?
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Copy the adb.exe from the KFFA directory to the SDK platform-tools directory.
soupmagnet said:
Copy the adb.exe from the KFFA directory to the SDK platform-tools directory.
Click to expand...
Click to collapse
Thank you so much! Worked just fine!
Also, moving to C:\KFFirstAide and running adb from there works as well.
Hi,
I am attempting to root my Kindle Fire HD 7.4.6 but no luck so far. I am using Windows Vista. Below is a list of what I have done so far.
1. Downloaded the Root_with_Restore_by_Bin4ry_v33 and unzipped. Stored files in a new folder on desktop.
2. Deleted all old Kindle drivers beforehand in Device Manager
3. Downloaded the Kindle Fire ADB Drivers, installed them and made sure they were up-to-date. Files stored in same folder as above.
4. Enabled ADB on Kindle
5. I connect my Kindle to PC and allow the drivers to install automatically.
6. In Task Manager I end the adb.exe process.
7. I run the RunMe.bat file as Administrator (Also ran everything else as Administrator where possible)
8. I press 1 then hit Enter. Hopefully below is a screen shot of what occurs in the window.
{
"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"
}
Nothing comes up on my Kindle screen asking me to back-up my data or restore my data but I pressed the keys just to go down the menu.
Hopefully I have given enough information for someone to help.
Regards, GCUK
GCUK said:
Hi,
I am attempting to root my Kindle Fire HD 7.4.6 but no luck so far. I am using Windows Vista. Below is a list of what I have done so far.
1. Downloaded the Root_with_Restore_by_Bin4ry_v33 and unzipped. Stored files in a new folder on desktop.
2. Deleted all old Kindle drivers beforehand in Device Manager
3. Downloaded the Kindle Fire ADB Drivers, installed them and made sure they were up-to-date. Files stored in same folder as above.
4. Enabled ADB on Kindle
5. I connect my Kindle to PC and allow the drivers to install automatically.
6. In Task Manager I end the adb.exe process.
7. I run the RunMe.bat file as Administrator (Also ran everything else as Administrator where possible)
8. I press 1 then hit Enter. Hopefully below is a screen shot of what occurs in the window.
View attachment 2483376
Nothing comes up on my Kindle screen asking me to back-up my data or restore my data but I pressed the keys just to go down the menu.
Hopefully I have given enough information for someone to help.
Regards, GCUK
Click to expand...
Click to collapse
Use KFFA (Kindle Fire First Aide) that's what I used on my Kindle Fire HD
GCUK said:
Hi,
I am attempting to root my Kindle Fire HD 7.4.6 but no luck so far. I am using Windows Vista. Below is a list of what I have done so far.
1. Downloaded the Root_with_Restore_by_Bin4ry_v33 and unzipped. Stored files in a new folder on desktop.
2. Deleted all old Kindle drivers beforehand in Device Manager
3. Downloaded the Kindle Fire ADB Drivers, installed them and made sure they were up-to-date. Files stored in same folder as above.
4. Enabled ADB on Kindle
5. I connect my Kindle to PC and allow the drivers to install automatically.
6. In Task Manager I end the adb.exe process.
7. I run the RunMe.bat file as Administrator (Also ran everything else as Administrator where possible)
8. I press 1 then hit Enter. Hopefully below is a screen shot of what occurs in the window.
View attachment 2483376
Nothing comes up on my Kindle screen asking me to back-up my data or restore my data but I pressed the keys just to go down the menu.
Hopefully I have given enough information for someone to help.
Regards, GCUK
Click to expand...
Click to collapse
You can try KFFA as suggested or try v31 root Many Android.
Hi there,
I have a E6335, isn't there released adb drivers for windows 10 pro x64?
I've used the "Minimal ADB and Fastboot" pack from here, and i can get it to reboot through ADB, but after that it isn't recognized, so i have to perform a hard reboot throug the button beside the sim.
Im not that familiar with adb and fastboot, so if anyone could guide me, i'll be very thankful.
Kind regards.
driver signed in Windows 10
Try this:
http://forum.xda-developers.com/crossdevice-dev/sony/minitut-installing-adb-drivers-sony-t3185585
... and tell us if it works (should with the proper drivers from SONY's developer site).
Hi there,
It dosn't work.
Genuine drivers was installed, but i did a reinstall, same problem, the S1 Fastboot driver is not installed.
Drivers works fine, until i perform the "adb reboot bootloader" command in adb, after that, the fastboot driver is unknown in device manager.
I've tried to perform the unlock command afterwards, but it keeps hanging on the "waiting for device".
Performing the "fastboot devices" dosn't work.
{
"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 guess i have to go on a win7 machine then?
Thanks.
I guess i have to go on a win7 machine then?
Click to expand...
Click to collapse
I recommend Debian Jessie
Read Androplus's advice. http://forum.xda-developers.com/showpost.php?p=62577784&postcount=2
I see the wrong command in your screenshot.
You know how to get into fastboot mode?
Power off the device. Hold "Volume up" (until the LED turns blue) and plug in USB cable.
I do not know, what you are up to with unlocking the bootloader but if these first steps go so badly you better stop here before attempting to root the device or doing something else. You could end up with a brick.
reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.
I'm not a newb in droid phones, just the adb. And i've just used the commands from this thread: http://forum.xda-developers.com/xperia-z4/general/bootloader-unlock-tip-t3165018
And if thats wrong, i think that it should be corrected.
And same issue as the before mentioned, when i use the vol up option.
@monx
I'll try that right away. I've just updated all 6 machines to win10 from 7, so im not that familiar with it yet
reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.
Click to expand...
Click to collapse
That did the trick, thank you buddy