Windows 8 ADB Fix! - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hello all, you might've seen my thread down below, about having painstaking errors with getting ADB to work with my Windows 8.
PLEASE READ!!!
First and foremost, IF you have plugged in your Fire HD into your Win8 pc already, please go to device management, and see what it recognizes the Kindle as. If it recognizes as "Android ADB", please right click on it, and remove the drivers (With the Kindle unplugged). It MUST be recognized as a "portable media player" or something along those lines. If it's recognized as the "Android ADB", then it will have driver conflicts with my steps below, and nothing will happen. Took me 4 hours to figure out the issue.
IF you haven't plugged in the Kindle before, then PLEASE install the ADB and Android SDK first. Then once you plug the Kindle in, it should be recognized as "Android Composite ADB". IF not, it prolly will set at "Daemon started".
First of all, you gotta do the below method, to remove the darn security, since the ADB is unsigned drivers.
Click on Command Prompt (Admin)
At the blinking cursor type: bcdedit -set TESTSIGNING OFF
Then once done, reboot, you should see "Test Mode" watermark on the lower-left side of the screen. Install Android SDK, all you gotta install is the Google USB Driver, and then install the Amazon ADB drivers NOT Google, or any other drivers. Download those here. Once downloaded, right-click, and "run as admin". They should install without ANY error.
Once done, reboot, and go into your Fire HD, in Settings>Security>Enable ADB, and then root with your program of choice. I used "Root with restore by Bin4ry", it worked PERFECT for my latest version Fire HD 7". Make sure to click "restore" on the Fire HD, when it pops up, then it'll reboot, and be done in approx 2 mins.
Now go back into Command Prompt (Admin), and enter the below data to re-enable the security for unsigned drivers.
Once at CMD, enter bcdedit -set TESTSIGNING ON
Now reboot, and your PC should be back like normal, with the exception of a rooted Kindle. :laugh:
Basically I found out that Windows 8 likes to install it's own version of ADB, which messes things up terribly. Because my ADB drivers from Amazon wouldn't do crap, and once I deleted the drivers that Win8 installed, then it worked PERFECT with the Amazon ADB drivers.
Please "thank me" if I've helped. If you need further help, please ask. Sorry I'm no programmer, only a PC addict.

A few things:
1: Nice guide
2: Forgot something
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
and to disable
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
3: Search the forums for other guides first
http://forum.xda-developers.com/showthread.php?t=2093296

Related

[Q] Stuck in boot loop, have fastboot cable?

I tried installing a second bootloader with Fireflash, and apparently I missed a step. This led to my Kindle being stuck in a bootloop. I bought a fastboot cable from ebay, which arrived today. When I connect with that cable, the logo changes to the fastboot logo, but anything I try with the KFHD System.img Restore Tool doesn't work, neither does Kindle FirstAide.
With KFHD System.img Restore Tool, I always get < waiting for device >.
I'm not sure what to do now, can anyone suggest anything?
You need to install the drivers for the device, open your task manager and hit update driver on the Tate device with a triangle next to it, and download the drivers in my signature, then after extracting them, poi t the update drivers wizard to the place you extracted the drivers to and let them install.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You need to install the drivers for the device, open your task manager and hit update driver on the Tate device with a triangle next to it, and download the drivers in my signature, then after extracting them, poi t the update drivers wizard to the place you extracted the drivers to and let them install.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I just tried that, and the wizard tells me that the hash is not present in the catalog file?
Ah your on windows 8, you need to first disable driver signature enforcement, Google it and then try again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Disable device driver signature enforcement -
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit /set testsigning on
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers next time. Following steps 1,2 and 3 in part B of tutorial, copy these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions
ENABLE_INTEGRITY_CHECKS bcdedit.exe -set TESTSIGNING OFF
Since I don't have Windows 8 to do a personal tutorial, I'll just link to a good tutorial for that.
http://www.fotoclubinc.com/blog/how...on-of-windows-7-printer-drivers-on-windows-8/

Device not detected in adb or fastboot

Hi, my device (tate) cannot connect to any of my computers in adb or fastboot modes, rendering me unable to transfer any files onto my device. However, I am able to perfectly boot into TWRP recovery. The ROM I previously flashed didn't work, and I had already factory reset the device without making a backup. How can I now transfer a working ROM given my problems in adb?
OS: Windows 8 x64 (failed to install the KFHD adb drivers)
Upon command 'adb devices' or 'adb usb': 'no device found'
Upon command 'fastboot -i 0x1949 getvar product': nothing happens
You need to install the drivers while in twrp/fastboot. I would recommend just using adb to push the ROM onto the sdcard from twrp. You will need to fix your drivers first though, to do that you need to disable windows driver signature enforcement, look it up on Google. Then download the drivers in my signature and update the drivers for the device with a triangle in the device manager and point then to where you extracted the drivers. Then try adb again while in twrp.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Disable device driver signature enforcement.
Both must be done from the administrator profile to work right.
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue.
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit /set testsigning on
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers next time. Following steps 1, 2 and 3 in part B of tutorial enter these commands
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
Since I don't have Windows 8 to do a personal tutorial, I'll just link to a good tutorial for that http://www.fotoclubinc.com/blog/how...on-of-windows-7-printer-drivers-on-windows-8/
---------- Post added at 10:18 PM ---------- Previous post was at 09:55 PM ----------
chemicalrubber said:
Hi, my device (tate) cannot connect to any of my computers in adb or fastboot modes, rendering me unable to transfer any files onto my device. However, I am able to perfectly boot into TWRP recovery. The ROM I previously flashed didn't work, and I had already factory reset the device without making a backup. How can I now transfer a working ROM given my problems in adb?
OS: Windows 8 x64 (failed to install the KFHD adb drivers)
Upon command 'adb devices' or 'adb usb': 'no device found'
Upon command 'fastboot -i 0x1949 getvar product': nothing happens
Click to expand...
Click to collapse
You need to push a ROM onto TWRP using this tutorial http://forum.xda-developers.com/showthread.php?t=2459498 Also disable drivers via my post above this post. Lastly, make sure to use Hashcodes crackflasher mirro as TWRP is still messed up making goo.img zip file downloads a mere shell that fail to flash. Make sure to have the most up to date TWRP as well http://forum.xda-developers.com/showthread.php?t=2128848
Thanks stunts and Linearequation! Disabling driver signature enforcement was the crucial step. Adb now works perfectly in recovery!
chemicalrubber said:
Thanks stunts and Linearequation! Disabling driver signature enforcement was the crucial step. Adb now works perfectly in recovery!
Click to expand...
Click to collapse
You're welcome. To clarify my post, TWRP works fine, goo,.img is causing some corrupted downloads yet.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers

Cant get windows 10 to recognize Fire

Has anyone been able to connect there Fire to windows 10 and get windows 10 to recognize it in order to run ADB commands.
In device manager i have a yellow exclamation showing on the my Fire. Ive tried installing the drivers for it that have been posted by RootJunky and the ones in the zip file from the root zip...they all error out
Don't know which ones those are but maybe the ones here if they are different?
https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Pond-life said:
Don't know which ones those are but maybe the ones here if they are different?
https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Click to expand...
Click to collapse
thanks dude, i think those are the ones that finally worked. funny some of the ones posted here werent working
el7145 said:
thanks dude, i think those are the ones that finally worked. funny some of the ones posted here werent working
Click to expand...
Click to collapse
I'm sure they must have worked for those that mentioned them though, probably depends what other drivers they already have installed. And maybe which windows.
I succeeded with Windows 10 x64 using the drivers in the zip file for installing Google Play found in this thread: http://forum.xda-developers.com/showthread.php?t=3216122
I had to disable driver signature enforcement before it would accept the drivers. Pop an admin command prompt (try the new Windows+X key combo and click admin command prompt there!), then run the following two bcdedit commands:
bcdedit -set loadoptions DISABLE_INTEGRITY _CHECKS
bcdedit -set TESTSIGNING ON
Reboot and proceed to install the drivers. I did it manually from Device Manager, clicking "Let me specify a location" (or whatever that one says) and such. Once I did that, all was well.
Been searching for this! Same problem, the fix worked! Amazon's fix was so useless.

can't install drivers on win7 or win10

i've tried all suggestions to install the drivers and when i connect my fire to my computer, it shows up as portable device > fire. if i try to update drivers, it says that i am already using the best one, the MTP usb device.
i've followed this:
http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
and also tried the drivers from amazon and neither allow me to select the adb driver.
You have turned adb on on the Fire?
Pond-life said:
You have turned adb on on the Fire?
Click to expand...
Click to collapse
thanks for the reply.
yes, i put it in dev mode by tapping the serial numbers and it is adb enabled.
ultraman69 said:
and also tried the drivers from amazon and neither allow me to select the adb driver.
Click to expand...
Click to collapse
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.
i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
thekrakah said:
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.
Click to expand...
Click to collapse
ultraman69 said:
i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
Click to expand...
Click to collapse
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.
i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
thekrakah said:
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.
Click to expand...
Click to collapse
for some reason, on only one out 4 of my win 10 rigs, i had to turn off driver signature enforcement. to do this go to settings, update and security, recovery, advanced startup, restart now. then in the restart menu push, troubleshoot, advanced options, startup settings, then restart. when booted choose "Disable driver signature enforcement" (which is option 7 on current build). now try to install the drivers. after successful just do a normal restart to enable the signature enforcement again
ultraman69 said:
i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
Click to expand...
Click to collapse
Can you verify that, "android debug" mode is turned on in the Fire devices developer settings? At least that was the only way I could reproduce the same message output from "adb devices".
I faut with my win 7 laptop for about an hour with one of my fires. Has the yellow icon on unknown device. Ended up "update driver" "browse for file" "let me choose from a list" picked Android/adb composite device. Adb and fast boot now work. I originally had to install Android studio and some extras to get my first fire to link up. Pm if you need help.
Sent from my Nexus 6P using Tapatalk
I recommend RootJunky tool, does everything and gives you instructions what to dohttp://www.rootjunky.com/amazon-fire-5th-gen-supertool/ Also recommend watching all his videos https://www.youtube.com/watch?v=sVv1D_LNLTg&feature=youtu.be

Honor 3C Vibrate only when connected to pc for flash

Hello, I've searched everywhere but can't find a solution to my problem. every bricked honor 3c that I read can be flashed, but when I connect mine to the pc to flash it sp fails and the computer makes a disconnected device sound.
does anyone have any idea how to flash the stock ROM on this phone in this state? I'd really hate to throw it away because of a software problem.
thanks and have a great day!
with windows 10 or 7?
if you use win 8 or 10 :
1- Open a Command Prompt with admin privileges. In Windows 10 or 8, just press the Windows key + X and then select “Command Prompt (Admin)”.
2- Type in the following command and press Enter.
bcdedit /set testsigning on
You should receive “The operation completed successfully” message. If you see a message saying the value is protected by Secure Boot policy, then you have to turn off Secure Boot in the UEFI/BIOS, before disabling Driver Signature Enforcement.
3- Close the Command Prompt and restart your computer. From now on, you will be able to install or run any unsigned driver without problems.
If you need to enable the Driver Signature Enforcement again, run this command instead:
bcdedit /set testsigning off
source
for win 7 reinstall Handset WinDriver.
mt_nik said:
with windows 10 or 7?
if you use win 8 or 10 :
1- Open a Command Prompt with admin privileges. In Windows 10 or 8, just press the Windows key + X and then select “Command Prompt (Admin)”.
2- Type in the following command and press Enter.
bcdedit /set testsigning on
You should receive “The operation completed successfully” message. If you see a message saying the value is protected by Secure Boot policy, then you have to turn off Secure Boot in the UEFI/BIOS, before disabling Driver Signature Enforcement.
3- Close the Command Prompt and restart your computer. From now on, you will be able to install or run any unsigned driver without problems.
If you need to enable the Driver Signature Enforcement again, run this command instead:
bcdedit /set testsigning off
source
for win 7 reinstall Handset WinDriver.
Click to expand...
Click to collapse
I don't know how you got faulty drivers from my problem. my problem isn't drivers, they're installed correctly, my problem is the phone not staying on enough for the software to flash before it reboots.

Categories

Resources