Database Users

Kindle fire - Not even showing in device manager

Hey All,
So my kindle fire was chugging along just fine and it showed up in Windows device manager, mounted as a drive etc. I ran the 'Kindle Fire Utility' v3 and used zergrush - no problem. Then I selected 'Install latest TWRP'. It did something, rebooted, then it all went tits up.
Now when I turn on my kindle fire, I'm stuck on the logo. It doesn't show up in device manager and I've spent about 2 hours trying just about every adb/fastboot command I can find.
Obviously none of them are working because they just say device not found or sit on 'waiting for device' forever.
Anyone got any ideas at all what I could do? I've only had the bloomin' thing for about 2 weeks and I think I've really bodged it up!
I've read through every related post I could find and none of them seemed to match my conditions and none of the commands have done the job.
Fingers crossed! Cheers
UPDATE: I finally managed to fix this by booting from a live Ubuntu disc where the kindle was found over usb and I was able to use fastboot.

philstuffs said:
Hey All,
So my kindle fire was chugging along just fine and it showed up in Windows device manager, mounted as a drive etc. I ran the 'Kindle Fire Utility' v3 and used zergrush - no problem. Then I selected 'Install latest TWRP'. It did something, rebooted, then it all went tits up.
Now when I turn on my kindle fire, I'm stuck on the logo. It doesn't show up in device manager and I've spent about 2 hours trying just about every adb/fastboot command I can find.
Obviously none of them are working because they just say device not found or sit on 'waiting for device' forever.
Anyone got any ideas at all what I could do? I've only had the bloomin' thing for about 2 weeks and I think I've really bodged it up!
I've read through every related post I could find and none of them seemed to match my conditions and none of the commands have done the job.
Fingers crossed! Cheers
Click to expand...
Click to collapse
There is several threads about this use the search
Actually I think the answer to your problem is contained in the thread where you downloaded the tool.

Hiya,
I appreciate the reply but I think you're wrong. There are similar issues but I haven't yet seen any that are exactly the same.
You *think* there's a solution in that thread? or you know? Because I've looked through it and several others over the last couple hours and I'm still not making any progress.
Like any forum you're quick to jump on the bandwagon and scream 'use the search'. I'm active on other forums and I get the reasoning behind it. But I think you've jumped the gun in this case.
Cheers

others have reported the same behavior with version 3 of the tool.
they recovered by downloading version 1 or 2 and use the usb driver
from one of theese versions.
have not tried it, just read it today ...

Thanks for the heads up b63. I saw the same earlier and tried v2 but not yet v1. The reason being that although the drivers are bundled, I can't (that I know of) install them without the device at least showing in the device manager..
Cheers

philstuffs said:
Now when I turn on my kindle fire, I'm stuck on the logo. It doesn't show up in device manager ...
Click to expand...
Click to collapse
From this I read "doesn't make the USB Connected noise when you plug it in". I don't imagine that different drivers will make much difference. Have you seen the post on how to make a factory USB cable?
http://forum.xda-developers.com/showthread.php?t=1392693

philstuffs said:
Thanks for the heads up b63. I saw the same earlier and tried v2 but not yet v1. The reason being that although the drivers are bundled, I can't (that I know of) install them without the device at least showing in the device manager..
Cheers
Click to expand...
Click to collapse
Here's what you need to do to fix that:
Go to device manager
Right click the device. It will be Android USB Composite Device or just kindle
Click uninstall
Disconnect the kindle and reboot the computer
When the computer is back up, turn on the kindle and plug it in
It will fail to install the driver. So, go back to device manager
Right click kindle
Click update driver
Click let me choose...
Click let me pick the driver...
Click have disk
Point the file browser to C:\Program Files (x86)\Android\android-sdk\extras\google\usb-driver\android_winusb.inf and click ok.
Choose Android USB Device when prompted
Click install anyway if prompted
The driver should have installed properly now
open Kindle utility
Choose factory reset
Unplug kindle
Boot kindle
Have fun!!!

daveoggy,
That's right, no ding dong. Although if I turn the kindle fire on and plug the usb cable in immediately (have it sitting ready to push into the fire) then the device manager does refresh after about 5 seconds, as if something was connected. Although no new device is shown.
I'll look into the factory cable, thanks for that.

does the usb connection make a noise - thats the right question !
if jes then ist a driver problem - there is something wrong with the driver from v3
if it makes the typical noise then a factory cable is like shooting with a cannon on flys

jlocohustler said:
Here's what you need to do to fix that:
Go to device manager
Right click the device. It will be Android USB Composite Device or just kindle
Click uninstall
Disconnect the kindle and reboot the computer
When the computer is back up, turn on the kindle and plug it in
It will fail to install the driver. So, go back to device manager
Right click kindle
Click update driver
Click let me choose...
Click let me pick the driver...
Click have disk
Point the file browser to C:\Program Files (x86)\Android\android-sdk\extras\google\usb-driver\android_winusb.inf and click ok.
Choose Android USB Device when prompted
Click install anyway if prompted
The driver should have installed properly now
open Kindle utility
Choose factory reset
Unplug kindle
Boot kindle
Have fun!!!
Click to expand...
Click to collapse
Thanks but remember I said it's not showing up in device manager?

b63 said:
if it makes the typical noise then a factory cable is like shooting with a cannon on flys
Click to expand...
Click to collapse
... is the right metaphor

to uninstall a device you don't see:
http://support.microsoft.com/kb/315539/en-us

b63 said:
to uninstall a device you don't see:
http://support.microsoft.com/kb/315539/en-us
Click to expand...
Click to collapse
Good man. Uninstalled and rebooting now. It's been a long time since I've used Windows.
Will update shortly.
Cheers

Try completely powering the device down. IE holding power for 20+ seconds. Give it a minute, then turn it back on with it plugged in.
DO you hear it dinging over and over for like 10 seconds?

I was able to uninstall the device by following b63's advice on items not listed in device manager.
I then rebooted and connected the kindle. It came up with the new hardware alert in my taskbar but that then disappeared and no new hardware is being shown in the device manager. There was no ding ding at any time.
Vashypooh, I held the power button for 20 seconds, the kindle fire turned off. I then booted it back up about a minute or two later. Still no ding.
*sigh*

You say you are stuck on a logo on the Fire which logo?
Sent from my Kindle Fire using Tapatalk

The logo is static. No animation.

philstuffs said:
The logo is static. No animation.
Click to expand...
Click to collapse
I meant what does it look like
Sent from my Kindle Fire using Tapatalk

which logo ?
"kindle fire" static or yellow triangle ?

It says 'kindle fire' in static text
Kindle in white
Fire in gold
No other icons/logos on the screen.

[Q] How to update drivers to Kindle Fire?????

So I was using the Kindle Fire Utility to root my Kindle, and that went perfectly, then I installed, the gapps, and that worked perfectly. But I planned to install CM7 on it so attempted to use the install recovery image option. (knowing now that it was broken and it was updated as I was performing this). SO it would go into a boot loop, so I was confused and tried to get it to boot in recovery with no progress. So I tried to see if it could even boot into anything besides normal, so I tried to boot it to fastboot, and now it's stuck on the Kindle Fire boot screen with no flashing.
So, I was freaking out, thinking I bricked my Kindle, and I read around, and noticed that the Utility was updated, but when I launched it I realized that it said offline. So I checked the drivers and it said "Code 10 Error" under device manager. So I uninstalled the drivers, and tried to re-install them. The computer see's my Kindle as an Unknown device, and when I plug it in it says that the USB devices attached to this computer has malfunctioned and windows does not recognize it. So, when I try to update the drivers for the unknown device I get "The Folder you specified doesn't contain a compatible software driver for your devices." Even though it does, and if I try to do it another way it says "The Driver is up to date."
I didn't mess with any permissions, or anything like that I just tried to get it to boot in recovery or in fastboot, and it's stuck and now my computer can't recognize it.
Am I SOL? Did I brick it permanently?
Any suggestions would be great. Thank you all for your help.

Manually install the drivers by selecting them from the list (don't tell Windows to automatically search for them).

TheDoctor1177 said:
So I was using the Kindle Fire Utility to root my Kindle, and that went perfectly, then I installed, the gapps, and that worked perfectly. But I planned to install CM7 on it so attempted to use the install recovery image option. (knowing now that it was broken and it was updated as I was performing this). SO it would go into a boot loop, so I was confused and tried to get it to boot in recovery with no progress. So I tried to see if it could even boot into anything besides normal, so I tried to boot it to fastboot, and now it's stuck on the Kindle Fire boot screen with no flashing.
So, I was freaking out, thinking I bricked my Kindle, and I read around, and noticed that the Utility was updated, but when I launched it I realized that it said offline. So I checked the drivers and it said "Code 10 Error" under device manager. So I uninstalled the drivers, and tried to re-install them. The computer see's my Kindle as an Unknown device, and when I plug it in it says that the USB devices attached to this computer has malfunctioned and windows does not recognize it. So, when I try to update the drivers for the unknown device I get "The Folder you specified doesn't contain a compatible software driver for your devices." Even though it does, and if I try to do it another way it says "The Driver is up to date."
I didn't mess with any permissions, or anything like that I just tried to get it to boot in recovery or in fastboot, and it's stuck and now my computer can't recognize it.
Am I SOL? Did I brick it permanently?
Any suggestions would be great. Thank you all for your help.
Click to expand...
Click to collapse
Here is the exact way to re-install the drivers again if you did not do so already...
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
You should be good now!!
Click that thanks if I helped ya
Big thanks to Jcase for Burrito Root

[Q] Stuck on FireFireFire logo slightly diffrent problem

So after reading and trying how others on here fixed that very same problem I deiced its time to make a post and ask for help because those other methods did not work.
Ok I did something stupid and I went ahead and did a factory reset to my kindle. Yes I know it was a complete noob thing to do and I should have known better seeing that I have rooted and flashed ROMs on all my other android devices and never once did something that dumb but I did it this time. Now I do have a back up made and had it safely stored on my PC.
Problem is that I can't get into recovery it stuck on the FFF logo and holding down the button only brings it back up. When the device restarts windows recognizes it as an unknown usb device and won't connect and Adb also wont recognize the device or show that it is connected. So now I need to ask someone who is more knowledgeable then me on what to do next. Any help will be appreciated
Ok update: Was able to solve my own problem using the Kindle fire utility and by uninstalling the drive for the kindle through the device manager, then using the drive install_drivers.bat in the KFU folder to reinstall the drivers. I next unplugged my kindle from the pc, turned it off by holding the button on the kindle in and then restarted it with the usb plugged into the pc. My Pc recognized my kindle and I was then able to use KFUs Bootmode menu and once in there used option 1. to boot it in normal mode. Hope this helps anyone who was stuck like I was. My memory of which adb commands to use was a bit rusty but using the KFU helped with that part.

[help] kindle fire stuck at yellow triangle/reboot loop

Hi, I've recently rooted my Kindle Fire device using KFU v9.3. After this, I noticed that FFF and TWRP weren't installed. So I used KFU to install FFF and it worked perfectly. I tried to install TWRP and it failed saying
"Oops… something went wrong with the download.
The recovery downloaded is not correct.
Please try the download again."
However, on the second try it worked up until a point where KFU said "Setting Normal bootmode" followed by "waiting for device...". This was when my kindle got stuck on the yellow triangle screen and my computer has not been able to recognize it since.
I have tried to install drivers via the install_drivers.bat file in KFU, however i get the error "install failed (Unsigned)" I tried to use Zombiepirates' Kindle Fire Unbrick Utility and selected "Stuck at logo" but it can't find the device.
Now when I plug my kindle into the computer it just keeps turning on and off and my computer doesn't recognize it.
I'm using a WIndows XP pc and I have access to a windows 7 one if needed.

Try this..
http://forum.xda-developers.com/showthread.php?t=1422832

Have you tried using KFU to change the bootmode back to normal despite your kindle not being detected? After you attempt to change the bootmode to normal perform a hard reset (hold the power button for 30 seconds) and your kindle should be detected. Hope this helps, worked for me for the same issue

I can't, whenever I use "install_drivers.bat" I get an error that says "Install failed (Unsigned)"
Do you know how I should go about fixing this?

BluesHawk said:
Have you tried using KFU to change the bootmode back to normal despite your kindle not being detected? After you attempt to change the bootmode to normal perform a hard reset (hold the power button for 30 seconds) and your kindle should be detected. Hope this helps, worked for me for the same issue
Click to expand...
Click to collapse
Yes I have. It says "waiting for device" and I did a hard reset to my Kindle but still it's "waiting for device" now my Kindle is just shutting on and off rapidly whenever it's plugged into the computer

Is windows blocking the driver? You're on XP right? Try this, then try installing the driver.
Right click on My Computer then select Properties to open System Properties.
In “System Properties” dialog box, select the Hardware tab.
Click on Driver Signing button.
Make sure "block" option isnt checked. That wouldn't let you install any uncertified drivers.

BllgpapaG said:
Yes I have. It says "waiting for device" and I did a hard reset to my Kindle but still it's "waiting for device" now my Kindle is just shutting on and off rapidly whenever it's plugged into the computer
Click to expand...
Click to collapse
The same thing is happening to me. My kindle is rebooting when plugged into the computer, KFU or KUU aren't able to do anything. I'm using Windows 7 but I can't bring up the drivers because the device isn't recognized by windows
any ideas on how to stop this rapid rebooting is much appreciated
Edit
a link to my post on a similar issue can be found here

MasterJoefus said:
The same thing is happening to me. My kindle is rebooting when plugged into the computer, KFU or KUU aren't able to do anything. I'm using Windows 7 but I can't bring up the drivers because the device isn't recognized by windows
any ideas on how to stop this rapid rebooting is much appreciated
Click to expand...
Click to collapse
Update your kindle fire driver with the file in the KFU directory.
Go into Device Manager, find the Kindle fire, update the driver and point it to the driver in the KFU directory. (KFU>drivers>kindle)

_Justin said:
Update your kindle fire driver with the file in the KFU directory.
Go into Device Manager, find the Kindle fire, update the driver and point it to the driver in the KFU directory. (KFU>drivers>kindle)
Click to expand...
Click to collapse
The kindle is not listed in the device manager because after the kindle reboots a few times while connected to the pc, windows stops adding it to the device manager. Is there any way to manually add it and add the drivers?

MasterJoefus said:
The kindle is not listed in the device manager because after the kindle reboots a few times while connected to the pc, windows stops adding it to the device manager. Is there any way to manually add it and add the drivers?
Click to expand...
Click to collapse
I don't know why it's doing that. Is it constantly rebooting? Try another USB port or PC.

from the op of kfu:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and from vashypooh - dev of kfu:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
hope this helps ...

@b63
THANK YOU! Your post about drivers is the most direct and effective way to install drivers. I wish I could thank you a million times.

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

Kindle Fire in FFF Loop
I am also having the same issue as well. Tried running the KFU for unbricking and still nothing as my PC nor my laptop is able to recognize my KF. Not sure what to do. It is constantly just looping while connected via USB and if I disconnect it, it powers off.
Any help would be great.

sounds like empty battery
would try to charge it with the wall charger for some hours
if it turns on if you plug it to the wall charger try to power it off by holding the pwr button ~20sec till it turns off to allow charging

noob needs help with ice cream sandwitch gone wrong!!
Hey ya'll,
So I'm sure you're tired of noobs posting but I just need a little help. I rooted my kindle last night and then tried giving it ics 4. So, I wiped everything (as instructed) and before hand I added the cm09 file along with the gapps. Yet, when I downloaded and extracted these two files they came out as multiple files so I first extracted the files to my desktop. I then transferred the individual files to the root of my kindle. When trying to "install" them , the individual files(which cm09 and gapps had been comprised of ) popped up but I couldn't do anything with them (flash ,etc). So, then I tried condensing all the gapps files into one "gapps" folder and all the cmo9 files into one "cm09" folder and transfer it to the root. Same thing happened. What I think I should haev done is not extracted either and just have sent the unzipped files to the root of my kindle...woops...I am a dumb noob after all! So, now I'm stuck with my kindle and when I turn it on to "normal mode" (not the TWRP) the "kindlefire" insignia pops up at start up like normal but it just sits there like that. Any idea of what I should do and where I can get the files to do it so that I too can have the LIMITLESS POWER OF ICE CREAM!!?? MWAHAHAHAHA...really though..any help ?

would try to boot to twrp - tap mount and mount sdcard - copy the cm9 file to the root of sdcard as instructed - install it with twrp - that should do it
you can install the necessary gapps afterwards - if i remember right it is also described how to do in the op of cm9

i just wanted some help. I rooted my kindle fire and flashed everything had cm7 on it one point and wanted to try miui's rom. I did as instructed but its stuck on the fff screen. Ive also tried as b63 instructed. But every time i connect my kindle it shows up for a brief second and disappears. What do i do? Please help! thank you!

You are 100% correct.
b63 said:
sounds like empty battery
would try to charge it with the wall charger for some hours
if it turns on if you plug it to the wall charger try to power it off by holding the pwr button ~20sec till it turns off to allow charging
Click to expand...
Click to collapse
If the yellow triangle is flashing and the tablet turns of when you unplug it from your computer then the battery is totally dead. I figured that out after 7 hours of frustration!

Yea I had that same issue with mine. I connected it to its factory shipped charger and about an hour later it was turning on and staying on.
Sent from my Kindle Fire using Tapatalk

A load of problems...

So recently flashed CM 10.1 FUSION. Nexus battery drains, I end up turning it back on while on the charger. Then, it shuts down on me.. so I let it charge overnight. Turned it back, and I get stuck at a boot screen (FUSION). I attempt to turn my device off, and it just restarts. I have to turn it off from the bootloader (P+Up+Down).. I tried using the toolkit, but I freeze in the bootloader when I plug my device in.
Help.
Running 4.2.1
Yes I'm aware of the common problems, none of the solutions seem to be working.

Rovon said:
Yes I'm aware of the common problems, none of the solutions seem to be working.
Click to expand...
Click to collapse
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers

bftb0 said:
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers
Click to expand...
Click to collapse
I tried watching a majority of the "unbrick nexus 7" vids on youtube. They didn't get me too far
Holding power for a long time
Restarting bootloader
Root toolkit
If I don't connect it to a device, I can move through the bootloader but can't access recovery

Rovon said:
If I don't connect it to a device, I can move through the bootloader but can't access recovery
Click to expand...
Click to collapse
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?

bftb0 said:
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?
Click to expand...
Click to collapse
Sorry, I meant its frozen on the fastboot screen...
I can scroll through the fastboot, but that's it. None of the commands work, unless I hit power off. The toolkit tells me "fastboot device not found", when I try the Flash Stock + Unroot button. There is no device ID I can see on the toolkit. Also, drivers fail to install when I plug it in to my computer.

Rovon said:
None of the commands work, unless I hit power off.
Click to expand...
Click to collapse
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?

bftb0 said:
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?
Click to expand...
Click to collapse
I should've been more specific. When I say none of the commands work, I mean they don't do what they're supposed to. So if I hit "recovery mode" it will not go into recovery mode, it just stays stuck at the Google logo when it restarts.
As for device manager, when plugged in to the computer with Fastboot, I do get "android" under other devices. However, when I'm booting the device up regularly, the computer attempts to install drivers and fails. I do get "MTP USB Device" under portable devices. I have an unknown device under portable as well.
All 3 seem to have error symbols next to them.

Rovon said:
All 3 seem to have error symbols next to them.
Click to expand...
Click to collapse
Well, if you can't communicate with the device successfully, there's no hope of doing something correctly from the PC. So, try a few simple things on that angle of the problem first. The problem you are seeing could come from any number of places:
- damaged USB (or other) hardware on tablet
- bad / cheap USB cable
- damaged USB port on PC
- driver install issues
The symptoms you describe for fastboot sound a bit like the custom recovery got damaged or erased, although more severe (and not fixable) problems are also a possibility.
Since you previously installed a ROM, I would take it to mean that at one time you had at least one driver working (fastboot at a minimum), and possibly also ADB mode (in the OS and/or in the recovery). That's why I put "driver install issues" last in the short list above. If you never touched any of the drivers after you did your initial ROM installs, I would not expect driver issues ... but I don't know what you might have tried subsequently with the toolkit (which does fool around with drivers).
Are you using the OEM cable? Some aftermarket/charger cables have a short mini-USB connector, and one dollar cables off of eBay can be poorly constructed (bad shielding or impedance control, so they cause data errors at high speeds).
If you have an 2nd cable, I would try to see if you experience a different set of symptoms with that; same goes for trying a different USB port on your PC.
If you see errors in the Device Manager associated with fastboot I certainly would not be attempting any operation from the PC until you get that resolved. Note there is a huge difference between "unknown device" and a device showing errors - the latter suggests that the OS is aware of a driver which is supposed to be loaded when the tablet shows up on the USB bus, but then some malfunction occurs. That malfunction could either be hardware or an inappropriate driver.
Drivers
http://www.asus.com/Tablet_Mobile/Nexus_7#support_Download
http://forum.xda-developers.com/showthread.php?t=1426502
Note that you should be able to use the Asus driver for every mode of your Nexus 7 (except MTP and PTP, which are handled by Windows generic class drivers), including your custom recovery by doing the following:
A) Download the Asus Driver and unzip it someplace.
B) make a backup copy of the "android_winusb.inf" file (for instance "android_winusb.inf.backup")
C) Open up the "android_winusb.inf" file with the Notepad program (Note: not Wordpad!)
D) Find the ";Google Nexus 7" stanza in the [Google.NTx86] section and add this line:
%CustRecoveryADBAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_9999
E) Add the same line (step D above) in the [Google.NTamd64] section
F) At the very bottom of the file in the [Strings] section, add the line
CustRecoveryADBAdbInterface = "Nexus 7 Custom Recovery ADB Interface"
G) Save the file and then proceed to do a manual de-installation of the drivers for fastboot and ADB.
H) Disconnect from the internet and then re-install the Asus driver for fastboot and ADB using the "Choose Location" method.
Don't know if that will work, but it's something to try; the problem you are having might lie outside the scope of what all of the above deals with
good luck

Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!

Rovon said:
Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!
Click to expand...
Click to collapse
Please describe what you found out and what DID work for you. Even if it was just a simple mis-understanding. It might help others in the future.
Probably you should also alter the title of your thread to be something much more descriptive - and add the keyword "[SOLVED]" to the title as well.