Related
The main reasons to root the kindle is to gain access to the Google Android Market and or flash a Rom. The the act of rooting the stock software is very near obsolete in most cases. For one reason or another this appears to be an arduous task for the kindle, the computer, the utility and for the inexperienced user. There`s a better way, not a new way but far less talked about. My hope is to create a better safety net for the average user. A few simple steps and you`re well on the way. The process involves getting drivers installed correctly, putting a custom recovery in place as well as a bootloader, managing your first backup and installing a modified stock Rom with root. It`s a good idea to first understand some basic things about what your device will need to make all this possible. I do not believe it could be anymore clearly laid out for you than FSM Kinfauns wrote here [GUIDE] Kindle Fire For Beginners. If you`re new to rooting or just to the Kindle Fire this is a must see.
Drivers
Well I`m sorry the first part is difficult at least for some users it requires getting drivers in order. I`m not going to go into great detail on this it`s very well highlighted in the second post of the above thread. Some things that may help installation.
Avoid using 3.0 USB ports users have had trouble with them not reacting well to fastboot causing serious problems.
Make sure your using the proper cable.
Run the Install_driver bat file first. Any errors during this may indicate the need for a manual installation. Windows XP requires manual installation.
Plug in the Kindle. Watch to see if windows shows installation of drivers and which one. Windows 7 usually shows a popup balloon of the driver it`s installing, click on it to view progress and type.
Open device manager. In device manager you should see "Android phone" click to view driver it should read "Android Composite ADB Interface".
If it reads "Android ADB Interface" more work is needed.
Right click then select update driver.
Click "browse my computer for driver software", and point it to the kindle drivers. On my Windows 7 machine, for instance, it's C:\Documents and Settings\HP_Administrator\Desktop\Kindle_Fire_Util ity_v0.9.6\Kindle Fire Utility\drivers\kindle.
Include subfolders and click next. Disregard any warnings update driver software anyway, preferably it will then read "Android Composite ADB Interface".
For manual installation here`s a very good tutorial. How to install Kindle Fire adb USB driver?
Driver flex testThere`s a way to test the driver before ever attempting to send anything to your device. The Kindle Fire driver is in and of itself multifaceted and Windows has only met with the first half of it. A mild introduction to the second half could very well prevent Windows from being confused when you need it function correctly for the technical part of this process. I would consider this "the lesser of two evils" with the only risk being stuck in fastboot. This far less under weighs actually physically breaking something if it were to fail.
Plug your kindle in.
Unlock the screen.
Tap disconnect at the bottom of the screen to stop the USB file transfer application if it auto launches.
Open device manager.
Launch Kindle Fire Utility.
Confirm driver indicates "Android Composite ADB Interface" in device manager and Kindle Fire Utility indicates ADB Status: Online / Boot Status: 4000.
In KFU select # 1 Bootmode Menu then select # 2 Fastboot <4002> the Kindle will be told to reboot in fastboot mode. Setting bootmodes with KFU takes a bit be patient.
Check device manager see that the driver reads "Android ADB Interface" without errors such as an exclamation point or a question mark.
Powering the device off and back on again while attached can prompt new hardware found for updating driver on XP and proper installation of the driver in Windows 7.
If it does have an error or Windows does not recognize the device you must once again right click then select update driver to make it read "Android ADB Interface".
Press any key to continue
If it says ADB status offline Boot Status: Unknown disregard and select # 1 Normal <4000> this will tell the Kindle to reboot in Normal mode.
After booted press any key to continue.
Press 0 to recheck device status.
Confirm driver indicates "Android Composite ADB Interface" in device manager and Kindle Fire Utility indicates ADB Status: Online / Boot Status: 4000. This completes the driver flex test. If you get stuck in fastboot don`t panic there`s no damage, just an altered bootmode. Keep working with your drivers, powering the device off and back on again while attached seems to work pretty well.
Device preparation
Start with a fully charged battery.
This step is very important under settings/device turn on allow installation of applications from unknown sources.
Plug your kindle in.
Unlock the screen.
Tap disconnect at the bottom of the screen to stop the USB file transfer application if it auto launches.
Status verification
Open device manager.
Launch Kindle Fire Utility.
Confirm driver indicates "Android Composite ADB Interface" in device manager and Kindle Fire Utility indicates ADB Status: Online / Boot Status: 4000.
TWRP installation
Select # 3 Install Latest TWRP Recovery. The Kindle will be told to reboot in fastboot mode. If all goes smooth it will reboot, in the terminal it will download the recovery, send it, write it. Then return your kindle to normal bootmode.
If nothing happens after 3 or 4 minutes and it just sits there <waiting for device> simply hold down the power button while connected till it turns off then turn it back on again. This could even take a few times always wait the 3 or 4 minutes in between.
Bootloader installation
Hopefully now the risky part is over and you`re booted back to the stock OS of the kindle.
Swipe to unlock the screen.
Do not disconnect the USB file transfer application. If it fails to auto launch touch upper left of screen, tap USB is connected select to copy files to/from your computer. This will show the contents of your sdcard on your computer.
Download bootloader only from here [bootloader][05-26] FFF 1.4A bugfixes + new look + recovery boot [.zip file size]. All files to be flashed in recovery must be in zip form. DO NOT EXTRACT. Do not use the bin file from KFU it`s not intended for flashing in recovery and will break the bootloader.
Drag and drop fff-u-boot_ v1.4a.zip on to your sdcard but do not place it inside of a folder.
Then disconnect the file transfer application when finished transferring.
In KFU select # 1 Bootmode Menu then select # 3 recovery <5001> this will tell your kindle to enter recovery.
In TWRP select install then locate fff-u-boot_ v1.4a.zip tap on it and flash it, leave the boxes unchecked.
When finished hit the home button upper right to return to TWRP home screen.
Select reboot.
Select system if prompted.
First backup and flashing rooted stock
After reboot Swipe to unlock screen.
Do not disconnect the file transfer application.If it fails to auto launch touch upper left of screen, tap USB is connected select to copy files to/from your computer.
Drag and drop this Rom zip onto your sdcard [ROM] 14 Jun Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire. Use the standard version not the altrom but do not put it inside of any folder. I`m not trying to highlight just one developers work but this is needed for this method.
Disconnect the file transfer application after the transfer has finished.
Unplug kindle from pc.
Power the kindle off , then back on again. When you see the white Kindle blue Fire logo quickly depress the power button a few times till you get a boot menu select --Recovery--.
In recovery select backup the default selections are fine, swipe to backup. This backup you will later rename noroot631 without spaces. Adding spaces will cause it to fail if you need to restore it.
When finished hit the home button upper right.
Select install.
Tap on GR9 Modaco zip and flash it. Do not enable force MD5 check or zip file verification or it will fail.
When done select reboot.
Select system if prompted.
Final result
When the Kindle reboots it will have root and have the Google Android Market in your applications.Take note that this is the only Rom that you flash without doing the proper wipes. To increase your safety net it is recommended to perform an MD5 check on fff-u-boot_ v1.4a.zip and Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire using this application WinMD5Free. You may ask" Why so many steps?" or "Why not flash everything at once?" This is to insure everything works throughout the process and prevent mishaps. The entire point of this thread to avoid having to use a factory cable or firekit to rescue your device because something went wrong. I hope that some of my tips and tricks will make your rooting experience safer and easier. Good luck and have fun.
How to flash another Rom
1. Transfer Rom zip and matching gapps zip to sdcard.
2. Enter recovery.
3. Create a backup.
4. Wipe factory reset.
5. Wipe cache.
6. Wipe dalvik.
7. Wipe system.( unless same Rom, same system, same developer)
8. Flash Rom zip.
9. Flash gapps zip.
10. Select reboot, then system if prompted.
11. Enjoy!
A very special thanks for all they continue to teach me and coaxing me to strive for more.
Kinfauns for Kindle Fire For Beginners
Soupmagnet for All the fun
Thanks to Vashypooh for Kindle Fire Utility
Thanks to Paulobrien for Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire
reserved
Your welcome.
Got up to the "Open adb_usb.ini with notepad.", but the file was not there. Did I forget something?
---------- Post added 12th October 2012 at 12:09 AM ---------- Previous post was 11th October 2012 at 11:53 PM ----------
Got up to the "Open adb_usb.ini with notepad.", but the file was not there. Did I forget something?
adb_usb.ini needs to be located in your .android folder if its not copy paste it from Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers\kindle to .android and plug your device in. Make sure that 0x1949 is written in if its written in twice or not written in the device will appear offline.
Thepooch said:
adb_usb.ini needs to be located in your .android folder if its not copy paste it from Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers\kindle to .android and plug your device in. Make sure that 0x1949 is written in if its written in twice or not written in the device will appear offline.
Click to expand...
Click to collapse
Did the trick. Ty sir
No problem.
abd Server offline and offline and offline......
Hello
I have a very neus Kindle Fire. Unfortunately I can not make it to rooten it.
For two days I build drivers back and forth. Always unsuccessful. The adb server is offline. Can it be that the device is too new? The device connects normal with win7. All attempts failed to use the modified drivers. It was only when I entered in my driver hardware ID from the Kindle (USB \ VID_1949 & PID_000A & REV_0216
USB \ VID_1949 & PID_000A) I was able to install the driver. Then stood in Device Manager under Android Phone ADB interface. Unfortunately the Kindle but then disappears completely from the workplace. But brings no good, the adb server is offline. Weis someone whether to run the adb server must also, not even when the kindle is connected? In Task Manager starts at least the adb exe.. Comes in the shell, but the message is written if I have adb properly etc.
I hope anyone have any advice.
Greetings and thanks
kindle-user said:
Hello
I have a very neus Kindle Fire. Unfortunately I can not make it to rooten it.
For two days I build drivers back and forth. Always unsuccessful. The adb server is offline. Can it be that the device is too new? The device connects normal with win7. All attempts failed to use the modified drivers. It was only when I entered in my driver hardware ID from the Kindle (USB \ VID_1949 & PID_000A & REV_0216
USB \ VID_1949 & PID_000A) I was able to install the driver. Then stood in Device Manager under Android Phone ADB interface. Unfortunately the Kindle but then disappears completely from the workplace. But brings no good, the adb server is offline. Weis someone whether to run the adb server must also, not even when the kindle is connected? In Task Manager starts at least the adb exe.. Comes in the shell, but the message is written if I have adb properly etc.
I hope anyone have any advice.
Greetings and thanks
Click to expand...
Click to collapse
Very important...what software version is your KF running?
soupmagnet said:
Very important...what software version is your KF running?
Click to expand...
Click to collapse
Hallo
My systemversion is 10.2.1_user_2030020
Don't do anything to your device until you read this:
http://forum.xda-developers.com/showthread.php?t=1928866
Hallo
Thank you for your Info. I will send it back to amazon. With original software do not like it.
best regards
soupmagnet said:
Don't do anything to your device until you read this:
http://forum.xda-developers.com/showthread.php?t=1928866
Click to expand...
Click to collapse
Bump
KFU ERRO
Well, I did exactly as in the procedure, but when I install TWRP, the KFU informed the log below:
***********************************************
* Recovery Installer *
***********************************************
***********************************************
* WARNING *
***********************************************
Make sure to read each screen carefully!
Make sure to follow instructions given to you!
twrp.img has been found.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
3440 KB/s (510876 bytes in 0.145s)
The kindle has been told to reboot in Fastboot Mode.
Cannot open input file recovery\twrp.img
error: cannot load 'recovery\twrp.img'
***********************************************
* READ ME *
***********************************************
If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Normal Bootmode.
Please wait...
< waiting for device >
... OKAY [ 0.198s]
finished. total time: 0.198s
rebooting...
finished. total time: 0.002s
***********************************************
* All Done! *
***********************************************
That's all folks. TWRP has been installed.
Please tap reboot on the kindle.
Press any key to continue . . .
_______________________________________________________________________
OBS:
In KFU shows the device status ONLINE.
I'm using Windows 7 Enterprise 64bit.
I figured it was giving error downloading the file, so I consulted the log and I downloaded manually, I created a folder "twrp.img" inside the folder "recovery" and threw the file "openrecovery-2.2.2.1-twrp-blaze" inside, but kept giving the same error.
The KF just restarts and nothing happens and does not install TWRP.
The version of my KF is 6.3.1.
Does anyone have a solution? Thankful!
PS: Sorry for the English, I'm using Google Translator!
Up!
Thank you your the best Thepooch
svartes said:
Well, I did exactly as in the procedure, but when I install TWRP, the KFU informed the log below:
***********************************************
* Recovery Installer *
***********************************************
***********************************************
* WARNING *
***********************************************
Make sure to read each screen carefully!
Make sure to follow instructions given to you!
twrp.img has been found.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
3440 KB/s (510876 bytes in 0.145s)
The kindle has been told to reboot in Fastboot Mode.
Cannot open input file recovery\twrp.img
error: cannot load 'recovery\twrp.img'
***********************************************
* READ ME *
***********************************************
If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Normal Bootmode.
Please wait...
< waiting for device >
... OKAY [ 0.198s]
finished. total time: 0.198s
rebooting...
finished. total time: 0.002s
***********************************************
* All Done! *
***********************************************
That's all folks. TWRP has been installed.
Please tap reboot on the kindle.
Press any key to continue . . .
_______________________________________________________________________
OBS:
In KFU shows the device status ONLINE.
I'm using Windows 7 Enterprise 64bit.
I figured it was giving error downloading the file, so I consulted the log and I downloaded manually, I created a folder "twrp.img" inside the folder "recovery" and threw the file "openrecovery-2.2.2.1-twrp-blaze" inside, but kept giving the same error.
The KF just restarts and nothing happens and does not install TWRP.
The version of my KF is 6.3.1.
Does anyone have a solution? Thankful!
PS: Sorry for the English, I'm using Google Translator!
Click to expand...
Click to collapse
I had the same issue, I had to rename the recovery file name to twrp.img then it worked perfectly. Also delete the file you created for twrp in the recovery directory in the kfu package and just replace the copy of twrp (if the is one there) in the recovery folder with the one you downloaded and renamed.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
everything is set but when i open the KFU 0.9.9 it look like this.
failed to copy 'files\fbmode' to '/data/local/fbmode': Permission denied
This is a great guide that goes into more detail than most of them which helps a lot for troubleshooting.
Unfortunately, the /data file system on my fire is read only, so copying the files to root it is not possible. I'm using KFU 0.9.9 and the kindle is running 6.3.2. Compter is windows 7 64-bit. What do I need to do to get permission to write to the kindle's filesystem? See the screenshots below.
Thanks for the guide
Sent from my Amazon Kindle Fire using xda app-developers app
Hello everyone! I'm writing because I need help rooting my KFHD 7".
I've read a lot of stuff and I'm kind of familiar with the topic now. This is my first android device though, so I'm still a noob with all of this.
I read a tutorial that said I needed some programs (QemuRoot, Root with restore by Bin4ry, Kindle Fire ADB Drivers).
The first step normally is to install the ADB drivers. Every time I try to install them a window opens and it starts the process, the bar loads completely and gives me an option to "Finish". Now, every time I click "Finish", another window opens and says "The drivers were not properly installed. Please install the drivers manually." I believe this is my main issue. Another thing is, I have no idea when to plug in/out my device... I don't know if I have to try to install the ADB thing when the Kindle's connected, etc. I tried to delete all the Kindle drivers on my pc to reinstall the ADB drivers, but I still get the same error...
Now, when I try to use the other programs, they say that my Kindle should open a dialog window asking if I want to restore my device, and that it will reboot in 10 secs. None of this happens. I just want to root my Kindle so I can use GooglePlay and download some good stuff. Also, I don't live in the US so I pretty much can't use my Kindle for anything. I even paid for Amazon Prime and I can't enjoy Amazon Instant Video (streaming series, etc) because of some geographical restrictions... IF any of you would know a workaround... Thanks
Kindle Fire 7" HD ADB Driver
Krawdd said:
Hello everyone! I'm writing because I need help rooting my KFHD 7".
I've read a lot of stuff and I'm kind of familiar with the topic now. This is my first android device though, so I'm still a noob with all of this.
I read a tutorial that said I needed some programs (QemuRoot, Root with restore by Bin4ry, Kindle Fire ADB Drivers).
The first step normally is to install the ADB drivers. Every time I try to install them a window opens and it starts the process, the bar loads completely and gives me an option to "Finish". Now, every time I click "Finish", another window opens and says "The drivers were not properly installed. Please install the drivers manually." I believe this is my main issue. Another thing is, I have no idea when to plug in/out my device... I don't know if I have to try to install the ADB thing when the Kindle's connected, etc. I tried to delete all the Kindle drivers on my pc to reinstall the ADB drivers, but I still get the same error...
Now, when I try to use the other programs, they say that my Kindle should open a dialog window asking if I want to restore my device, and that it will reboot in 10 secs. None of this happens. I just want to root my Kindle so I can use GooglePlay and download some good stuff. Also, I don't live in the US so I pretty much can't use my Kindle for anything. I even paid for Amazon Prime and I can't enjoy Amazon Instant Video (streaming series, etc) because of some geographical restrictions... IF any of you would know a workaround... Thanks
Click to expand...
Click to collapse
The first step is to get the ADB Driver installed.
The following ADB Driver was provided by Amazon and should install: Kindle Fire ADB drivers
If not, I have an alternative driver here: https://dl.dropbox.com/u/54456659/usb_driver.zip
The alternative driver originates from the Android SDK and is universal for just about any Android device.
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response.
The instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer to see if it initializes properly.
Reply once you have done this step OR respond with the error OR where you are stuck. We will get you on Google Play!
Amazon Notes regarding this ADB Driver can be found here: https://developer.amazon.com/sdk/fire/connect-adb.html
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Hardware Update Wizard.
2. Select Install from a list or specific location and click Next.
3. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
4. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
5. Click Next to install the driver.
Or, to upgrade an existing Android USB driver on Windows XP with the new driver:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Android Phone in the right pane.
5. Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7.Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9.Click Next to upgrade the driver.
prokennexusa said:
The first step is to get the ADB Driver installed.
The following ADB Driver was provided by Amazon and should install: link that you provided
If not, I have an alternative driver here: link that you provided
The alternative driver originates from the Android SDK and is universal for just about any Android device.
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response.
The instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer to see if it initializes properly.
Reply once you have done this step OR respond with the error OR where you are stuck. We will get you on Google Play!
Amazon Notes regarding this ADB Driver can be found here: link that you provided
Click to expand...
Click to collapse
Thanks for replying! The first ADB Driver (provided by Amazon) is the one that has given me the same error every time... something about an error and me installing the drivers manually (I have no idea how to do). The second link (dropbox) is broken... So right off the bat I'm stuck. The thing is, when I go to device manager, my Kindle Fire says "Android Composite ADB Interface"... I thought I already had ADB, but it appears that no matter what I do I can't get it to work... I don't have SDK or anything like that, though I'm downloading it to see if anything works...
Android Composite ADB Interface
Krawdd said:
Thanks for replying! The first ADB Driver (provided by Amazon) is the one that has given me the same error every time... something about an error and me installing the drivers manually (I have no idea how to do). The second link (dropbox) is broken... So right off the bat I'm stuck. The thing is, when I go to device manager, my Kindle Fire says "Android Composite ADB Interface"... I thought I already had ADB, but it appears that no matter what I do I can't get it to work... I don't have SDK or anything like that, though I'm downloading it to see if anything works...
Click to expand...
Click to collapse
OK, stop there. Even though it gave you an install error, it looks like the driver is installed. So let's move forward assuming they are functioning enough to get the job done.
Leave the Kindle plugged into USB and move on to my step-by-step which can be found 3/4 the way down on this Thread: http://forum.xda-developers.com/showthread.php?t=2064633
Note: The Kindle is left plugged in to USB through the entire tutorial.
prokennexusa said:
OK, stop there. Even though it gave you an install error, it looks like the driver is installed. So let's move forward assuming they are functioning enough to get the job done.
Leave the Kindle plugged into USB and move on to my step-by-step which can be found 3/4 the way down on this Thread: http://forum.xda-developers.com/showthread.php?t=2064633
Note: The Kindle is left plugged in to USB through the entire tutorial.
Click to expand...
Click to collapse
Thanks again. So I have the tool run with restore by bin4ry v18. When I open the folder, there is a RunMe.bat. I right click on it and click on run as administrator. It starts up and I write 1 to use normal mode. When it says that my Kindle should ask me for "restore", my Kindle is sitting there, doing nothing. It doesn't ask me for a restore. Then it says that my device will reboot in 10 seconds... My Kindle, again, does nothing. So that doesn't work... Now, I did another thing. I shift-right-clicked on the inside of the folder and clicked open command window here, then on the cmd that opened up I wrote "runme.bat" So it started the thing again, asked me for the number, etc. I write 1, and then this comes up (and it's stuck there): "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" ON on my Kindle... Any suggestions?
Krawdd said:
Thanks again. So I have the tool run with restore by bin4ry v18. When I open the folder, there is a RunMe.bat. I right click on it and click on run as administrator. It starts up and I write 1 to use normal mode. When it says that my Kindle should ask me for "restore", my Kindle is sitting there, doing nothing. It doesn't ask me for a restore. Then it says that my device will reboot in 10 seconds... My Kindle, again, does nothing. So that doesn't work... Now, I did another thing. I shift-right-clicked on the inside of the folder and clicked open command window here, then on the cmd that opened up I wrote "runme.bat" So it started the thing again, asked me for the number, etc. I write 1, and then this comes up (and it's stuck there): "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" ON on my Kindle... Any suggestions?
Click to expand...
Click to collapse
I see the problem. The way you are executing the batch files will cause the utilities to fail. You can not run the batch files (RunMe.bat and RootQemu.bat) through the mouse, you must execute them through a CMD Prompt.
OK, let's start from the top.
Let's make sure all the utilities are on your desktop.
Next Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v17 folder.
Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v17 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v17 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v17 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RunMe.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633), when you are ready to run Qemu
Next Double Mouse Click and Open the Qemu folder.
Single Left Mouse Click on the Qemu folder toolbar.
This highlights the Qemu folder.
Note: Make sure none of the files within the Qemu are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RootQemu.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633).
prokennexusa said:
I see the problem. The way you are executing the batch files will cause the utilities to fail. You can not run the batch files (RunMe.bat and RootQemu.bat) through the mouse, you must execute them through a CMD Prompt.
OK, let's start from the top.
Let's make sure all the utilities are on your desktop.
Next Double Mouse Click and Open the Root_with_Restore_by_Bin4ry_v17 folder.
Single Left Mouse Click on the Root_with_Restore_by_Bin4ry_v17 folder toolbar.
This highlights the Root_with_Restore_by_Bin4ry_v17 folder.
Note: Make sure none of the files within the Root_with_Restore_by_Bin4ry_v17 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RunMe.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633), when you are ready to run Qemu
Next Double Mouse Click and Open the Qemu folder.
Single Left Mouse Click on the Qemu folder toolbar.
This highlights the Qemu folder.
Note: Make sure none of the files within the Qemu are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, type:
Code:
RootQemu.bat
Go back to my tutorial and follow the steps (http://forum.xda-developers.com/showthread.php?t=2064633).
Click to expand...
Click to collapse
Thanks for the reply. As I said in the previous post, I had already done the "shift right click and open windows command here" thing. It doesn't work. This is where it gets to and stays there forever "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" So I'm stuck right at the first step... Doesn't matter what way I run the batch files I can't get them to work.
ADB Communication Issues
Krawdd said:
Thanks for the reply. As I said in the previous post, I had already done the "shift right click and open windows command here" thing. It doesn't work. This is where it gets to and stays there forever "Cheking if i should run in Normal Mode or special Sony Mode Please connect your device with USB-Debugging enabled now Waiting for device to shop up, if nothing happens please check if Windoes ADB-drivers are installed correctly!" Now, I have ADB turned ON on my Kindle. I also have the "Install apps" So I'm stuck right at the first step... Doesn't matter what way I run the batch files I can't get them to work.
Click to expand...
Click to collapse
Let's check the ADB communication path on your workstation.
Open a command prompt at the root of the Qemu folder, type:
Code:
adb kill-server
adb start-server
adb devices
The next command will probably fail, but let's try it:
Code:
android update adb
Finally, try:
Code:
adb shell
Reply back with the results.
prokennexusa said:
Let's check the ADB communication path on your workstation.
Open a command prompt at the root of the Qemu folder, type:
Code:
adb kill-server
adb start-server
adb devices
The next command will probably fail, but let's try it:
Code:
android update adb
Finally, try:
Code:
adb shell
Reply back with the results.
Click to expand...
Click to collapse
Thanks a lot! Well this are the results:
I did adb kill-server and nothing happened.
I did adb start-server and it said "daemon not running. starting it now on port 5037. daemon started succesfully"
I did adb devices and it said "list of devices attached" and then a blank space after that..
I did android update adb and it said "android is not a recognized internal or external command"
I did adb shell and it said "device not found"
I did all of that in the QemuRoot folder.. Am I doing it right? I double click on the folder to open it and then I click on the white space below all the files (while holding shift) and open the command window.
ADB Server Out of Date
Krawdd said:
Thanks a lot! Well this are the results:
I did adb kill-server and nothing happened.
I did adb start-server and it said "daemon not running. starting it now on port 5037. daemon started succesfully"
I did adb devices and it said "list of devices attached" and then a blank space after that..
I did android update adb and it said "android is not a recognized internal or external command"
I did adb shell and it said "device not found"
I did all of that in the QemuRoot folder.. Am I doing it right? I double click on the folder to open it and then I click on the white space below all the files (while holding shift) and open the command window.
Click to expand...
Click to collapse
Yes, you did this perfectly.
Hmmmm, looks like the ADB Driver is NOT working, bummer.
We need to focus on getting the driver functional.
Step 1) Go into Windows Add/Remove Software, find the Android ADB Driver, Uninstall the driver. If you can not find the driver in Add/Remove, then use the Uninstall Utility found in the Qemu folder "Drivers".
Step 2) Remove the Kindle from USB. Reboot the PC.
Step 3) Plug the Kindle back into USB after startup.
Step 4) When the PC has completed the reboot cycle, let's try to install the driver manually using the driver inside the usb_driver folder. Follow my instructions performing a manual driver install.
prokennexusa said:
Yes, you did this perfectly.
Hmmmm, looks like the ADB Driver is NOT working, bummer.
We need to focus on getting the driver functional.
Step 1) Go into Windows Add/Remove Software, find the Android ADB Driver, Uninstall the driver. If you can not find the driver in Add/Remove, then use the Uninstall Utility found in the Qemu folder "Drivers".
Step 2) Remove the Kindle from USB. Reboot the PC.
Step 3) Plug the Kindle back into USB after startup.
Step 4) When the PC has completed the reboot cycle, let's try to install the driver manually using the driver inside the usb_driver folder. Follow my instructions performing a manual driver install.
Click to expand...
Click to collapse
I deleted everything, I rebooted my PC, plugged in my Kindle and it started to install the Kindle drivers... (the normal ones)... It got an error and the driver didn't install... I got to manage under "computer" and i see "other devices" and under that it says "kindle" with a yelow exclamation mark... I go to its properties and drivers, I click update driver and use the folder that you gave me (usb_driver) and it gives me an error, saying that it could not find drivers... now do I set it to install the driver in C:\Users\Name\Desktop\usb_driver? or after usb_driver should I add \amd65 or \i386?
Thanks for your help... I don't know why nothing is working out!!
By the way, i just tried to install the adb drivers again and I got the same error... saying I have to install them manually. I ran both the bin4ry v18 and the qemuroot and both got stuck at "*daemon started successfully*" and they just sit there doing nothing...
ADB Driver Install
Krawdd said:
I deleted everything, I rebooted my PC, plugged in my Kindle and it started to install the Kindle drivers... (the normal ones)... It got an error and the driver didn't install... I got to manage under "computer" and i see "other devices" and under that it says "kindle" with a yelow exclamation mark... I go to its properties and drivers, I click update driver and use the folder that you gave me (usb_driver) and it gives me an error, saying that it could not find drivers... now do I set it to install the driver in C:\Users\Name\Desktop\usb_driver? or after usb_driver should I add \amd65 or \i386?
Thanks for your help... I don't know why nothing is working out!!
Click to expand...
Click to collapse
Yes, you are correct on the path: C:\Users\Name\Desktop\usb_driver
Let's try to install the Kindle Fire ADB Driver provided by Amazon. This time Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
If that fails, try to Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose Properties.
Then select the "Compatibility" tab
Check "Run this program in compatibility mode for"
Choose Windows XP Service Pack 2
Finally Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
prokennexusa said:
Yes, you are correct on the path: C:\Users\Name\Desktop\usb_driver
Let's try to install the Kindle Fire ADB Driver provided by Amazon. This time Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
If that fails, try to Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose Properties.
Then select the "Compatibility" tab
Check "Run this program in compatibility mode for"
Choose Windows XP Service Pack 2
Finally Right Hand Mouse Click over the Kindle Fire ADB drivers.exe driver choose "Run as Administrator".
Click to expand...
Click to collapse
Didn't work... I'm using windows 7 though... When I plugged in my Kindle it said something like Android ADB Composite installed succesfully... It did it by its own... When I try to install the Amazon ADB I get the same error, that i have to install it manually... I tried running the bin4ry root again and it doesn't work...
ADB Communication Issues
Krawdd said:
Didn't work... I'm using windows 7 though... When I plugged in my Kindle it said something like Android ADB Composite installed succesfully... It did it by its own... When I try to install the Amazon ADB I get the same error, that i have to install it manually... I tried running the bin4ry root again and it doesn't work...
Click to expand...
Click to collapse
We are missing something, usually simple.
What is the date and time stamp on the adb.exe daemons in the Root_with_Restore_by_Bin4ry_v17 "Stuff" folder?
---------- Post added at 05:09 PM ---------- Previous post was at 04:20 PM ----------
For everyone having trouble with ADB, here is a video that you may find helpful:
ADB Driver Install Video
prokennexusa said:
we are missing something, usually simple.
What is the date and time stamp on the adb.exe daemons in the root_with_restore_by_bin4ry_v17 "stuff" folder?
---------- post added at 05:09 pm ---------- previous post was at 04:20 pm ----------
for everyone having trouble with adb, here is a video that you may find helpful:
adb driver install video
Click to expand...
Click to collapse
1/13/2012 4:20 pm
ADB Server Out of Date
Krawdd said:
1/13/2012 4:20 pm
Click to expand...
Click to collapse
I thought I was going crazy. I knew it had to be something simple. You must have downloaded these utilities (Qemu and Root_with_Restore_by_Bin4ry_v17) from the developers site and not our site. Our utilities include the latest ADB daemons
which are dated 11/05/2012 11:06AM.
This is your problem.
Please use our utilities:
Kindle_Fire_HD_ADB_Drivers
Root_with_Restore_by_Bin4ry_v17
Qemu
Then go back to our step-by-step instructions. The ADB driver is probably fine, so you can probably bypass that step.
prokennexusa said:
I thought I was going crazy. I knew it had to be something simple. You must have downloaded these utilities (Qemu and Root_with_Restore_by_Bin4ry_v17) from the developers site and not our site. Our utilities include the latest ADB daemons
which are dated 11/05/2012 11:06AM.
This is your problem.
Please use our utilities:
Kindle_Fire_HD_ADB_Drivers
Root_with_Restore_by_Bin4ry_v17
Qemu
Then go back to our step-by-step instructions. The ADB driver is probably fine, so you can probably bypass that step.
Click to expand...
Click to collapse
Genius!!! It went smoothly, I did all the steps on the bin4ry and then qemu, and it said you now have root! How do I now if I actually have root? I don't see any different app in my kindle, I think I should have something like superuser?
Initialize Superuser.apk
Krawdd said:
Genius!!! It went smoothly, I did all the steps on the bin4ry and then qemu, and it said you now have root! How do I now if I actually have root? I don't see any different app in my kindle, I think I should have something like superuser?
Click to expand...
Click to collapse
Yes, you should see Superuser.apk in the APPS Folder. Go ahead and launch Superuser.apk to initialize it.
prokennexusa said:
Yes, you should see Superuser.apk in the APPS Folder. Go ahead and launch Superuser.apk to initialize it.
Click to expand...
Click to collapse
I guess it was too good to be true... there's no superuser.apk in the apps folder.. what to do? I already tried rooting it again and it said that i was rooted again
EDIT: I just woke up and tried again. Instead of usin first the root with restore and second the qemu, I used root with restore twice. Now I have a different app called SuperSU... It isn't Superuser though... It has a picture of the android robot wiith a cape flying... I opened but I have no idea what to do with it!
It worked for the error that you are having.
Hello i just read your post.. before continue sorry about my English is not perfect but i will try to to explain hot to explain the "solution"..
ok the first thing you need to do,is uninstall all the ADB drivers from the device manager.
after that you have to restart your PC..
when your pc is already started install de ADB drivers and then connect your kindle..! and let windows install the drivers again.
It worked for my so i hope it work for you.. =)
Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!
Thanks to:MaxRabbit
Other solutions
Windows 8 Diagnosis
Originally Posted by Yorus
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse
➜ No big ol’ SDK ➜ Latest Google drivers ➜ No messing with inf files ➜ ADB from any location ➜ Drag and drop files
Figured XDA needed a couple more ADB driver guides, so I'm bringing these down from Google drive where they've been getting a lot of use--with no complaints so far. :fingers-crossed:
Follow the steps below to install the Google ADB driver for "normal" (OS) mode.
Follow post #2 to install the driver for sideload mode. You must do this to sideload OS .bin files via stock recovery.
See post #3 for basic info/tips for using the command window and entering adb commands.
[EDIT September 21, 2015] If you're running Windows 10, read this:
At step 3 you install 15 Second ADB Installer. Some Win 10 users are reporting a problem. Please do this to help track it down:
- Be sure to run as Administrator.
- If you get an error, post the exact error and when it happens. Do not rerun Installer until someone replies to post.
- If you do not get an error, please post and say so and tell what type of Win 10 you have (home, pro, enterprise, etc.)
Thanks!
Install ADB Driver for "Normal" (OS) Mode
This uses @Snoop05's 15-Seconds ADB Installer. It provides the driver and software you need and puts the path to adb.exe into your PATH variable so you can run ADB commands from any folder.
Before you begin:
(1) Turn off anti-virus software
(2) Disconnect other physical devices that use adb and shut down any virtual ones. This can go very smoothly if you're not running anything that uses adb, including emulators, some photo-sync software, Gatesjr debloater, etc.
1. Make sure adb debugging is enabled on the the device. (Settings->My Device->Developer Options: Debugging)
To open Developer Options: In Settings -> My Device, tap on the serial number until Developer Options appears at bottom of screen.
2. If you've never connected Fire HD to computer, connect now and read this:
a. You may see a USB debugging message on tablet, tap "Always" and "Allow."
Even if you don't see message, Windows should try to install generic MTP drivers (not ADB!). Wait until you see success or failed message.
b. Unplug/replug and wait for Windows Explorer OR for message that prompts what to do when device is connected and choose Open window to Display Files, check Always do this and then OK.
c. Disconnect..
3. If you KNOW there’s no adb driver installed for the device, go to next step.
. . . If driver might already be installed, do hidden steps.
Connect to computer, open Device Manager (instructions below) and see if a driver is listed under Android Device.
- If a driver is NOT listed, go to next step.
- If a driver IS listed, open CMD window in folder containing adb.exe and run adb devices command (step 12).
* If adb devices DOES return an ID, this driver is working and you don’t need to install a different one.
* If adb devices does NOT return an ID:
a. In Device Manager, right-click the driver and choose Uninstall.
b. Unplug the device and restart Windows.
4. Download the latest version, currently v. 1.4.3, of 15 seconds ADB Installer and run it as Administrator.
If you are not Administrator, right-click the file and choose “Run as Administrator“
Read all about 15-seconds Installer at the link.
Press Y to install ADB and Fastboot
Press Y to install ADB system-wide or N for current user onlyYou should see:
Installing ADB and Fastboot . . .
4 files(s) copied
If you see 0 files copied, post the error with your Windows version and the drive it's installed on.
Press Y to install drivers
View attachment 3455788
5. An Install Wizard will run. Look for it and install device software!
6. Connect the Fire to the computer and wait until you see it in Windows Explorer.
7. 6/3/2016 Update for Win 10: Your drivers might already be installed. Check for Allow USB Debugging on tablet. Go to step 12 and run the adb devices command.
. . . If it shows serial number and unauthorized, you need to enable USB debugging and run command again. It should then show serial number and "device." You're done!
. . .If it doesn't show serial number, continue the steps.
Win 7 and 8.1: Open Device Manager:
Win10: ? Win8: Right-click Start Button and choose Device Manager. Win7: Click Start button and type Device Man [enter]
8. Find Fire under Other Devices, right-click it, and choose Update Driver Software.
If you don't see Fire under Other Devices, disconnect/reconnect or try a different USB port, or try toggling Enable ADB in Developer Options. If nothing works, disconnect and reboot both Fire and computer and try again.
{
"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"
}
9. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
10. Find Android Device, click it and press Next.
. . . If Android Device is not listed, look here.
If you DID NOT run 15 Seconds ADB Installer, STOP, disconnect from PC and run it now.
If you DID run 15 Seconds ADB Installer:
a. Double-click Show All Devices.
b. Under Manufacturer, scroll to Google, Inc, click it and continue.
↠ If Google, Inc is not listed, the ADB drivers are not installed, they installed incorrectly or were corrupted. STOP now and follow all the steps again.
11. Select Google, Inc in left pane and then Android Composite ADB interface in right, and press Next.
If the screen you see only has the Model pane (on the right above), scroll down to Android Composite ADB.
↠ If the driver is not listed, drivers have not been installed, they installed incorrectly or were corrupted. STOP now and follow all the steps again. 12. At the warning screen, press Yes.
Driver is updated!
13. Run the adb devices command and confirm it returns a device id:
a. Open CMD window: Hold down the Shift key, right-click the desktop (or an empty space in a folder) and choose Open command window here.
b. Type: adb devices [enter]
View attachment 3467199
If you see an ID followed by “device,” the driver is installed correctly. DONE!
If you see an ID followed by “unauthorized,” look at the tablet for “Allow USB Debugging?” message and tap OK.
If debugging message disappears before you say “OK,” unplug/replug tablet to see it again.
Repeat the adb devices command and confirm it now looks like above. DONE!
If you do not see an ID, the driver may not be correctly installed or USB debugging might still be disabled on your tablet. Verify all connections and reboot tablet and PC and repeat this step. If adb devices still doesn’t return an ID, follow this guide from the beginning again.
Install ADB Driver for Sideload Mode
Windows can’t recognize the Fire in sideload mode until you install the driver for it.
Note: These steps are pretty much identical to Post #1. Refer there for illustrations.
1. Connect the tablet to the computer and put it into sideload mode, like this: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
To reboot to recovery:
- From CMD window, run: adb reboot recovery
or
- Manual: (a) Power off the Fire. (b) Hold the power and volume-up buttons until Amazon logo appears, then let go.
2. Open Device Manager, find KFARWI under Other Devices, right-click it and select Update Driver Software.
If you don't see KFARWI under "Other Devices," see hidden text.
When KFARWI isn't under Other Devices, first be sure you "clicked" Apply Update from ADB on tablet to get into sideload mode.
If you did, see if "Android Device" is listed at top of Device Manager with a driver under it.
If Android Device is not listed, unplug/replug the tablet and see if KFARWI shows up under Other Devices. If it does, go to step 3. If it doesn't, post the problem.
If Android Device is listed, open CMD window in folder containing adb.exe and run adb devices command
- If adb devices returns an ID, this driver is working and you don’t need to install a different one.
- If adb devices does not return an ID, in Device Manager, right-click the driver, select Update Driver Software and go to Step 4.
3. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
[See “Select your device’s type”]
4. Click Android Device.
[See "Select the device driver you want . . .”]
5. Select the same driver you use for “normal” OS mode (post #1, step 10) and press Next.
6. Click Yes at warning screen.
Driver is updated!
7. In CMD window, run adb devices command and confirm you see your device ID and "sideload," like this:
8. DONE! Issue the sideload command or reboot to exit sideload mode.
Note (shouldn't happen, but . . . ) If you don't get a device ID and you had a driver installed at step 2 and updated it, you'll have to uninstall the driver.
In Device Manager, right-click and uninstall the driver under Android Device.
Restart computer and reboot tablet (to get out of sideload).
Go into sideload mode, right-click KFARWI under Other Devices and see if it has Update Software option.
- If YES, update the driver.
- If NO, reboot once more and go into sideload and you'll have Update option. Update the driver.
Info and Tips for Using the Command (CMD) Window - for "Newbies"
Here's some basic info for using the CMD window and entering commands found in the guides.
Open CMD window
Hold down the shift key, right-click an empty space in an open folder (including desktop), and choose "open command window here"
Give commands on-the-fly
If you used 15-Second Installer (post #1) you can open the CMD window from any convenient location, so you can easily give adb commands "on the fly."
Example: Open CMD from desktop and run adb devices to confirm adb recognizes your Fire.
Install an app (or sideload a bin file)
Open CMD window in the folder containing the file and enter the command: adb install filename.apk
If you open CMD from a different folder, include the full path: adb install "full_path_to\filename.apk"
Format: If there are spaces in the path or filename, put quote marks ( " ) around "full_path_to\filename.apk"
Drag & drop files and copy/paste commands
To enter a long or complicated command or file name into the CMD window, use drag & drop or copy/paste.
Drag and Drop
Type: adb install <--type a space after "install"
. . . then drag and drop your file into the window. The "full_path_to\filename.apk” will be inserted at cursor.
Copy and Paste
Select the command or long file name and use CTRL-C to copy it. In CMD window, type adb install(space) as above, right-click the top bar of the window and choose Edit then Paste.
Installing drivers for sideload
Is there a discussion or a fix for installing the ADB drivers for sideload using windows 10? I'm not sure if Windows 10 is the issue, but instead of getting KFARWI in device manager, I get MT65xx android device. I've followed the instructions after step 9 several times with no luck. I've tried updated the drivers with the ones mentioned in step 3 but ADB device doesn't list a device. Any suggestions?
rking38 said:
Is there a discussion or a fix for installing the ADB drivers for sideload using windows 10? I'm not sure if Windows 10 is the issue, but instead of getting KFARWI in device manager, I get MT65xx android device. I've followed the instructions after step 9 several times with no luck. I've tried updated the drivers with the ones mentioned in step 3 but ADB device doesn't list a device. Any suggestions?
Click to expand...
Click to collapse
Sounds like you're opening Device Manager while in recovery, not sideload mode. Look at step 1 again: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
Once in sideload mode, you should see KFARWI.
(I edited OP to make step for getting into sideload more obvious)
DoLooper said:
Sounds like you're opening Device Manager while in recovery, not sideload mode. Look at step 1 again: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
Once in sideload mode, you should see KFARWI.
(I edited OP to make step for getting into sideload more obvious)
Click to expand...
Click to collapse
Wow...follow the instructions from step one! thanks for your patience
15 Second ADB problem
DoLooper said:
Installing Google ADB drivers for your Fire HD:
Click to expand...
Click to collapse
MRDirtyPixels said:
I followed a guide to install Lolipop on my device, I managed to get the 15 Second ADB Installer but could only get the 1.3 version to work.
When I try to do it now it states on the device that I need 1.3.2 or higher. The 1.4 download gives me an Access Denied message and installed 0 drivers.
Click to expand...
Click to collapse
Someone else encountered this with 15 Second installer. Are you running Win10? What flavor (pro, home, etc)? At what point exactly is "Access Denied" displayed with version 1.4.2?
Also, do you have folder, C:\adb or C:\users\username\adb? If yes, what files are in it?
Please let me know these things so I can try to find a fix. EDIT: @MRDirtyPixels I'll post how to update the driver when you reply. Thanks!
Fire HD 6 on 4.5.3
Win7 Ultimate x64
I'm having an issue at "Apply update from ADB". I do not have this option in recovery - only "Reboot your Fire", and "Reset to Factory Defaults".
I've had ADB drivers installed from past projects. Tried it, got this issue. Went back and installed the ADB drivers from the 15 second installer to see if that helped, still have this issue.
Also, at no point is my Fire listed under "Other Devices" - I don't even have that listed as a category. The Fire is always listed under "Android Device" > "Android Composite ADB Interface", so I figured my drivers were all set.
Any ideas would be greatly appreciated.
**EDIT: Should I somehow remove/uninstall all ADB related drivers and software and try again?
You use sideload mode to downgrade to 4.5.3 from OS 5. (It's only an OS 5 recovery option.) Since you're on 4.5.3, presumably with OTA blocked, you don't need sideload. Sounds like your drivers set up right for OS mode. Go root!
EDIT: @jiznon Be sure OTA is blocked. Else you'll OTA update as soon as you turn on wifi to root!
DoLooper said:
You use sideload mode to downgrade to 4.5.3 from OS 5. (It's only an OS 5 recovery option.) Since you're on 4.5.3, presumably with OTA blocked, you don't need sideload. Sounds like your drivers set up right for OS mode. Go root!
EDIT: @jiznon Be sure OTA is blocked. Else you'll OTA update as soon as you turn on wifi to root!
Click to expand...
Click to collapse
Oh, great! I may have overlapped a guide or two. Thanks so much!
I managed to turn airplane mode earlier as the OTA began to download. Should be good, ya?
jiznon said:
I managed to turn airplane mode earlier as the OTA began to download. Should be good, ya?
Click to expand...
Click to collapse
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
DoLooper said:
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Click to expand...
Click to collapse
I see. That step isn't for sometime in the guide I'm following (it also states to install sideload drivers). Maybe it should be edited.
http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/
jiznon said:
I see. That step isn't for sometime in the guide I'm following (it also states to install sideload drivers). Maybe it should be edited.
http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/
Click to expand...
Click to collapse
Well, it's the step you do before turning on wifi to root. Notice that first step says that if you're on 4.5.3, get kingroot and go to step 6. So you're right there, at step 6.
jiznon said:
. . . (it also states to install sideload drivers). Maybe it should be edited. http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/
Click to expand...
Click to collapse
Yes, I see I introduced some confusing info about drivers/versions in last update. I'll fix. thanks.
DoLooper said:
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Click to expand...
Click to collapse
DoLooper said:
Well, it's the step you do before turning on wifi to root. Notice that first step says that if you're on 4.5.3, get kingroot and go to step 6. So you're right there, at step 6.
Click to expand...
Click to collapse
Right. I'm still at "Before You Begin:
Install adb device drivers if you don't have them.
Here's an illustrated guide for Windows drivers. Install driver for both OS mode and sideload mode."
Wanted to make sure I don't miss anything. Looks like I'm on the right track. Thanks!
**EDIT: Everything went smooth. Thanks everyone!
Hi DoLooper, I'm currently following your [Root] OS 4, 5.0.n and Install Lollipop & Gapps ("Newbie Friendly") guide to root and update a Fire HD 7 and that's how I got here. I have successfully completed this guide, but only after I solved a problem that I ran into along the way. I solved it myself, so I want to share how I did it.
I had a Samsung phone before, had Samsung Kies (bringing along drivers) and "Minimal ADB and Fastboot" installed. I had removed all of these and all traces of them I could find. But when I got to step 4 of your first post in this guide, it always asked whether I wanted to install a driver with the name "Google, Inc. SAMSUNG Android Phone". I was worried the driver might be set wrongly in some way and I would brick my Fire tablet during the rooting process because of that (possible?). I continued anyway and after the driver installation finished, it didn't refer to the Fire as a Samsung device in the device manager anymore and the other steps in this guide were successful as well. So I guess I'm safe now.
However, I do have to add that when the Samsung drivers from Kies were still installed (I forgot about them at first), the device manager did refer to the Fire as a Samsung even after step 4. So I guess the moral is that you have to clean your system of other Android drivers/software thoroughly and restart first - and only then begin the procedure described in this guide.
Last but not least, thank you very much for spelling everything out step by step, it all seems like a doable task now.
podikan said:
. . .
I had a Samsung phone before, had Samsung Kies (bringing along drivers) and "Minimal ADB and Fastboot" installed. I had removed all of these and all traces of them I could find. But when I got to step 4 of your first post in this guide, it always asked whether I wanted to install a driver with the name "Google, Inc. SAMSUNG Android Phone". I was worried the driver might be set wrongly in some way and I would brick my Fire tablet during the rooting process because of that (possible?). I continued anyway and after the driver installation finished, it didn't refer to the Fire as a Samsung device in the device manager anymore and the other steps in this guide were successful as well. So I guess I'm safe now.
However, I do have to add that when the Samsung drivers from Kies were still installed (I forgot about them at first), the device manager did refer to the Fire as a Samsung even after step 4. So I guess the moral is that you have to clean your system of other Android drivers/software thoroughly and restart first - and only then begin the procedure described in this guide.
Click to expand...
Click to collapse
This is helpful and I'd like to add it, but I'm a little confused. Step 4 is just installing the 15-second Installer software. I don't think it asks anything. Could you please clarify the step where you got that prompt? Also, when it was listed under Samsung, you were able to right-clicking and choose Update and install the google drivers, right? Thanks.
Well, at the end of step 3 the program 15 Second ADB asks "Do you want to install device drivers?" and then a windows prompt appears. This is when I got the following prompt on top of that (only have it in German, sry): imageshack.com/a/img911/8983/bBg2q0.jpg I assume it's some kind of driver, as 15 Second ADB calls it. Is it really specific to a device?
As for your second question, if I remember correctly I was able to do that (I had to dig for it like you explain in step 9 after ". . . If Android Device is not listed, look here."). But afterwards it was still displayed as a (fully installed) Samsung portable device in my device manager. No chance I would go ahead and root from there. That's when I found and removed the Samsung drivers which came with Kies, rebooted, and started the procedure from the beginning.
ADB not cooperating
Ok. I am on a Fire HD 7 Gen 4 at OS 5.1.1, and attempting to downgrade to 4.5.3 for rooting purposes. (My eventual goal is to get CyanogenMod or another 'pure android' ROM on it, if you can help with that, great) When in sideload mode, Windows doesn't detect my device at all (no KFARWI or any other 6-letter combo) but ADB can detect it in both sideload and OS mode. My problem is this: Whenever I attempt to flash a .bin stock recovery, adb stalls for about a second, while on my Fire I only see:
Now send the package you want to apply to the device with "adb sideload <filename>"
Finding update package...
Opening update package...
Verifying update package...
before the device reboots. On adb I then see: "failed to read command: connection reset by peer" Any subsequent attempts without a manual reboot into sideload mode just instantly time out. I have a feeling this has something to do with the weird reboot, but how do I prevent it?
DoLooper said:
Install ADB Driver for Sideload Mode
Windows can’t recognize the Fire in sideload mode until you install the driver for it.
Note: These steps are pretty much identical to Post #1. Refer there for illustrations.
1. Connect the tablet to the computer and put it into sideload mode, like this: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
To reboot to recovery:
- From CMD window, run: adb reboot recovery
or
- Manual: (a) Power off the Fire. (b) Hold the power and volume-up buttons until Amazon logo appears, then let go.
2. Open Device Manager, find KFARWI under Other Devices, right-click it and select Update Driver Software.
If you don't see KFARWI under "Other Devices," see hidden text.
When KFARWI isn't under Other Devices, first be sure you "clicked" Apply Update from ADB on tablet to get into sideload mode.
If you did, see if "Android Device" is listed at top of Device Manager with a driver under it.
If Android Device is not listed, unplug/replug the tablet and see if KFARWI shows up under Other Devices. If it does, go to step 3. If it doesn't, post the problem.
If Android Device is listed, open CMD window in folder containing adb.exe and run adb devices command
- If adb devices returns an ID, this driver is working and you don’t need to install a different one.
- If adb devices does not return an ID, in Device Manager, right-click the driver, select Update Driver Software and go to Step 4.
3. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
[See “Select your device’s type”]
4. Click Android Device.
[See "Select the device driver you want . . .”]
5. Select the same driver you use for “normal” OS mode (post #1, step 10) and press Next.
6. Click Yes at warning screen.
Driver is updated!
7. In CMD window, run adb devices command and confirm you see your device ID and "sideload," like this:
8. DONE! Issue the sideload command or reboot to exit sideload mode.
Note (shouldn't happen, but . . . ) If you don't get a device ID and you had a driver installed at step 2 and updated it, you'll have to uninstall the driver.
In Device Manager, right-click and uninstall the driver under Android Device.
Restart computer and reboot tablet (to get out of sideload).
Go into sideload mode, right-click KFARWI under Other Devices and see if it has Update Software option.
- If YES, update the driver.
- If NO, reboot once more and go into sideload and you'll have Update option. Update the driver.
Click to expand...
Click to collapse
thank you
I have done this on Windows 10/11 with the 8 Pro, 8T, and 9 Pro personally.Other members have had success with the OP5T, OP6T, OP7P, OP7T, OP8 and even a OP1 for @mawil1013 and somehow a Xiaomi Mi 9T lol
Spoiler: Backstory
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
To fix the issue, we are going to disable driver signing enforcement in Windows and then install the Unsigned OnePlus drivers.
Install the OnePlus drivers that are included with your phone.
They should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer.
I'm sure you can find the installation package somewhere online, but I don't have a good download source so I am not going to give out random links.
This will create a directory containing the USB driver. This will most likely be
C:\Program Files (x86)\OnePlus USB Drivers
In that folder there is a driver, but both when installed using the installer incuded with my phone, and a downloaded version, I ran into...
The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.
To get around this we are going to disabled signed drivers on windows.
Select the “Start” button.
Type “startup”.
Select “Change advanced startup settings“.
Select “Restart now” under the “Advanced startup” area.
Once presented with the Advanced options select...
“Troubleshoot“ --> “Advanced Options“ --> “Startup Options“ --> “Restart“
After that, a menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver until you reboot, meaning we can install our unsigned OnePlus driver.
Pop open Device Manager
You can press windows + x to bring up a menu, then you can press m or select device manager for quick access
Boot your device into fastboot mode.
This should cause it to show up in device manager as "Andriod", with a yellow triangle
In device manager right click the "android" device
Then press the following options
Update driver --> Browse my computer --> Let me pick --> Have Disk
Navigate to the folder from earlier: C:\Program Files (x86)\OnePlus USB Drivers
Select OnePlus_android_winusb.inf and click okay
After that, OnePlus Android Bootloader interface should be selected. Go ahead and install it.
Congrats! Your device should start showing up in fast boot mode.
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
Make sure when you allow adb debugging in developer mode that you authorize the phone when using adb devices, otherwise you will not see fastboot when you try to use.
Thank you, that would have driven me crazy. It is crazy that it is 2020 and driver manufactures still don't sign their drivers some times.
There is no CD Drive show up....
find on internet a oneplus usb driver and installed....
then got this message trying to get the [oem get_unlock_code]
Code:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Thanks OP.
finally works...
Okay, I just figured out my mistake, but I'll leave it in case someone else stumbles across the same thing. The fix: choose your language, then choose "reboot to fastboot" and confirm that you're sure. You'll get to a screen with "Fastboot mode" in red near the top. Once there, run the get code command.
Click to expand...
Click to collapse
REFERENCE: reference link
Thanks a lot @Mbektic. This seems so much harder than it needs to be and I wouldn't have been able to unlock my bootloader without your guide. Thanks again!
Wow I didn't even realize that I had helped people until now! I am so glad I could help you guys @bigd4ve @jefffeely and @Pain-N-Panic
Mbektic said:
Hey Guys,
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
So for me, the issue was resolved by doing the following below.
1) install the OnePlus drivers that are included with your phone.
--- they should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer
2) This will create a directory like this... C:\Program Files (x86)\OnePlus USB Drivers, containing the USB driver
3) In that folder there is a driver "" but both when installed from my phone, and a downloaded version, i ran into The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.. So next we are going to disabled signed drivers on windows.
-----Select the “Start” button.
-----Type “startup”.
-----Select “Change advanced startup settings“.
-----Select “Restart now” under the “Advanced startup” area.
-----Select “Troubleshoot“.
-----Select “Advanced Options“.
-----Select “Startup Options“.
-----Select “Restart“.
-----A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver you like in Windows 10 until you reboot.
4) Boot your device into fastboot mode. This should cause it to show up in device manager as Andriod, with a yellow triangle
5) In device manager(press windows + x to bring up a menu, then you can press m or select device manager for quick access) right click the android device
-----Update driver
-----Browse my computer
-----Let me pick
-----Have Disk
-----Navigate to C:\Program Files (x86)\OnePlus USB Drivers
-----Select OnePlus_android_winusb.inf and click okay
-----OnePlus Android Bootloader interface should be selected, and go ahead and install it.
After that your device should start showing up in fast boot mode.
I'm not sure if for some reason my driver version just was lacking a hash, or if it is a common issue, but hopefully i'll save someone a couple of minutes.
Click to expand...
Click to collapse
Yes, I also had to disable device driver signing, then the phone showed up in the bootloader.. You can just open an admin command prompt, type "bcdedit /set testsigning on", REBOOT, then install the proper driver. This seems to be a problem with OOS11.
The easiest method for any newbie is to install , iobit driver booster , free.
Driver Booster 10 Free: Official Free Driver Updater Tool for Windows 2023
The best free driver updater for Windows 11/10. Fully detect and update all your old drivers for graphics, USB, audio, display, network, printer, mouse, keyboard and scanner. Free check driver updates now.
www.iobit.com
Then update the android driver. The fastboot would be working fine after that.
dogmatism said:
The easiest method for any newbie is to install , iobit driver booster , free.
Driver Booster 10 Free: Official Free Driver Updater Tool for Windows 2023
The best free driver updater for Windows 11/10. Fully detect and update all your old drivers for graphics, USB, audio, display, network, printer, mouse, keyboard and scanner. Free check driver updates now.
www.iobit.com
Then update the android driver. The fastboot would be working fine after that.
Click to expand...
Click to collapse
I just cant thank as much as I have to! I couldnt find solution for months, I was using magisk module on old phone to use fastboot and it sucked. Now updated driver and works like charm. Thank you so much!
Thanks for making this thread. I couldn't believe I were having so many issues on my desktop, when I had managed to get everything right when I first got the phone(8PRO) on my laptop. I had adb & fastboot installed, then plugging in Kona w/ usb debug off allowed me to install the adb driver and then for fastboot(while in fastboot, using window's "device manager" I selected the Google usb driver I had downloaded, and finally for edl mode driver just in case (msm), I installed the qualcomm driver while in edl mode( whew). Anyway thanks,
I cannot believe I did not see this thread earlier...
Just finished solving the same problem after going nuts for a couple of hours.
It is most definitely just getting the PC to install the OnePlus drivers AND disabling the driver signing.
What a pain.
Mbektic said:
Hey Guys,
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
So for me, the issue was resolved by doing the following below.
1) install the OnePlus drivers that are included with your phone.
--- they should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer
2) This will create a directory like this... C:\Program Files (x86)\OnePlus USB Drivers, containing the USB driver
3) In that folder there is a driver "" but both when installed from my phone, and a downloaded version, i ran into The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.. So next we are going to disabled signed drivers on windows.
-----Select the “Start” button.
-----Type “startup”.
-----Select “Change advanced startup settings“.
-----Select “Restart now” under the “Advanced startup” area.
-----Select “Troubleshoot“.
-----Select “Advanced Options“.
-----Select “Startup Options“.
-----Select “Restart“.
-----A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver you like in Windows 10 until you reboot.
4) Boot your device into fastboot mode. This should cause it to show up in device manager as Andriod, with a yellow triangle
5) In device manager(press windows + x to bring up a menu, then you can press m or select device manager for quick access) right click the android device
-----Update driver
-----Browse my computer
-----Let me pick
-----Have Disk
-----Navigate to C:\Program Files (x86)\OnePlus USB Drivers
-----Select OnePlus_android_winusb.inf and click okay
-----OnePlus Android Bootloader interface should be selected, and go ahead and install it.
After that your device should start showing up in fast boot mode.
I'm not sure if for some reason my driver version just was lacking a hash, or if it is a common issue, but hopefully i'll save someone a couple of minutes.
Click to expand...
Click to collapse
you've saved my sanity on oneplus5T after upgrading to Android Q 10. Thank you
I also struggled with this issue but found another solution. Once my phone was plugged in (can't remember if it was system or fastboot) I went to Windows Update and browsed the optional updates. One of the optional updates was a driver for android recovery. Installed it and it worked.
bynarie said:
Yes, I also had to disable device driver signing, then the phone showed up in the bootloader.. You can just open an admin command prompt, type "bcdedit /set testsigning on", REBOOT, then install the proper driver. This seems to be a problem with OOS11.
Click to expand...
Click to collapse
Between the OP and this post, I was finally able to get the drivers to work on my 8T (Sim Free- Carrier Unlocked) new phone from Oneplus. I spent several hours trying to determine what the issues were and then found this thread. I am successfully unlocked from the bootloader. Thank you both.
behel1t said:
I also struggled with this issue but found another solution. Once my phone was plugged in (can't remember if it was system or fastboot) I went to Windows Update and browsed the optional updates. One of the optional updates was a driver for android recovery. Installed it and it worked.
Click to expand...
Click to collapse
THANK YOU! This worked 100% for me, super easy too. Went to Windows Update, View Optional Updates, saw the Android External Device update, device showed in fastboot after installing.
THANK YOU SO MUCH!!!!! You're a legend, it works on my OnePlus 5T as well.
Mbektic said:
Hey Guys,
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
So for me, the issue was resolved by doing the following below.
1) install the OnePlus drivers that are included with your phone.
--- they should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer
2) This will create a directory like this... C:\Program Files (x86)\OnePlus USB Drivers, containing the USB driver
3) In that folder there is a driver "" but both when installed from my phone, and a downloaded version, i ran into The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.. So next we are going to disabled signed drivers on windows.
-----Select the “Start” button.
-----Type “startup”.
-----Select “Change advanced startup settings“.
-----Select “Restart now” under the “Advanced startup” area.
-----Select “Troubleshoot“.
-----Select “Advanced Options“.
-----Select “Startup Options“.
-----Select “Restart“.
-----A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver you like in Windows 10 until you reboot.
4) Boot your device into fastboot mode. This should cause it to show up in device manager as Andriod, with a yellow triangle
5) In device manager(press windows + x to bring up a menu, then you can press m or select device manager for quick access) right click the android device
-----Update driver
-----Browse my computer
-----Let me pick
-----Have Disk
-----Navigate to C:\Program Files (x86)\OnePlus USB Drivers
-----Select OnePlus_android_winusb.inf and click okay
-----OnePlus Android Bootloader interface should be selected, and go ahead and install it.
After that your device should start showing up in fast boot mode.
I'm not sure if for some reason my driver version just was lacking a hash, or if it is a common issue, but hopefully i'll save someone a couple of minutes.
Click to expand...
Click to collapse
ohhh my man, you really saved my time. thanks a lot. appreciates ur help.
I recovered my account just so I could post a reply on this thread. THANK YOU MBEKTIC, you saved my skin!
I was puzzled for 3/4 hours wondering what to do. Thank you
Mbektic said:
Hey Guys,
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
So for me, the issue was resolved by doing the following below.
1) install the OnePlus drivers that are included with your phone.
--- they should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer
2) This will create a directory like this... C:\Program Files (x86)\OnePlus USB Drivers, containing the USB driver
3) In that folder there is a driver "" but both when installed from my phone, and a downloaded version, i ran into The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.. So next we are going to disabled signed drivers on windows.
-----Select the “Start” button.
-----Type “startup”.
-----Select “Change advanced startup settings“.
-----Select “Restart now” under the “Advanced startup” area.
-----Select “Troubleshoot“.
-----Select “Advanced Options“.
-----Select “Startup Options“.
-----Select “Restart“.
-----A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver you like in Windows 10 until you reboot.
4) Boot your device into fastboot mode. This should cause it to show up in device manager as Andriod, with a yellow triangle
5) In device manager(press windows + x to bring up a menu, then you can press m or select device manager for quick access) right click the android device
-----Update driver
-----Browse my computer
-----Let me pick
-----Have Disk
-----Navigate to C:\Program Files (x86)\OnePlus USB Drivers
-----Select OnePlus_android_winusb.inf and click okay
-----OnePlus Android Bootloader interface should be selected, and go ahead and install it.
After that your device should start showing up in fast boot mode.
I'm not sure if for some reason my driver version just was lacking a hash, or if it is a common issue, but hopefully i'll save someone a couple of minutes.
Click to expand...
Click to collapse
Thanks for this - I know its a little after the fact but 6+ months later this post has gotten me out of a fastboot hole with a oneplus 9. Now fully rooted only for this. Thanks again.