Fastboot Brick - Unkown device in Windows Device Manager - Kindle Fire General

Problem was solved by changing the xml file to the language code.
Original Problem:
Hi everyone, just got the kindle today and finished root, then I used the Kindle Utility tool to change to fastboot.
As I finished the fastboot, it ended up stuck on the boot screen. Try serverl methods, but did not work.
According to:
http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
"Once rebooted, connect your Kindle again via USB. You'll probably hear 3 tones (which means it recognized a device, but didn't load any drivers). In device manager, you'll see a device just called "kindle" or "unknown" with an exclamation point by it. At this point, you'll need to install drivers for it again. Pick "Browse my computer for driver software" BUT don't browse, just click on "Let me pick from a list...", and select "Android Phone" and then pick the newest "Android Composite ADB Interface" from the list. I think you may have 4.0.0.0 or something similar (you may have only a 2.x version possibly depending on which drivers you loaded to root your phone)."
But the problem here is that it the Windows Manager recgnized the kindle as an "Unkown Device" , and also I did not find "Android Phone" from the list, and cannot install driver manually as well. Does anyone have any suggestions?

just right click the unknown device and update the drivers
about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

Excellent method! Thanks

Related

[Q] I just can seem to unbrick my Fire.

I used kindle fire utility 7 and installed twrp. My kindle is version 6.2.1 and now when i turn it on its just the triangle with fire. I press the power button to go into recovery mode like it says at the bottom but that does nothing. Oh and my computer doesnt recognize the device! I notices somethings plugged it (3 tone sounds) and thats it. In device manager it's just labeled as "USB device". Iv'e tried just about everything i can find online,but the kindle fire utility just says "waiting for device" no matter what. Can someone please help me with this issue? Its a brand new kindle i literally got 2 days ago and would really like it back to normal
Thanks!
Manually re-install the ADB drivers by going into Device Manager, clicking on "Unknown Device" or "kindle" or whatever it's called, and manually selecting the "Android ADB Composite Interface" from the list of drivers rather than having Windows automatically search for it.
Then, go back to the Kindle Fire Utility and re-install TWRP.
If you want to get rid of root and TWRP afterwards, use the KFU to download the stock update.zip, and flash it using TWRP. That'll get rid of everything and restore the Fire to its original state.
It only has "Android phone". When i click it it asks me to browse a folder for the driver. I dont know what folder to pick. I tried then android programs files folder but nothing.
What exactly do you mean by "Android phone"? Is the ADB interface installed, or is it just listed as "Unknown Device?"
It is listed as "USB device" but the ADB is installed.
Try clicking on "Have Disk" in that last screen and specifying "C:\Program Files\Android\android-sdk\extras\google\usb_driver" or something to that effect as the file path.
You need to give it the path where the file "android_winusb.inf" is stored.
It just says that the path specified doesn't contain information about your hardware.

no longer rooted?

Im running the latest software for the KF, I guess I got the update. I seem to be unrooted now. I can still access the android market and things like that. I didnt even know that I was unrooted until I went to change something and tried to change r/o to r/w or vice versa. I checked with root checker and it does confirm that I am not rooted. How do I reroot? Do I need to take certain files off the KF first, or can I just go over whatever is there?
Thanks
what firmware does it say your on
It says 6.2.2
I'm trying to re root but I'm not sure if I have to unroot first.
I just want to start from scratch, root, install aneroid market, install calendar, get it to.sync.......that's it. Lol.
Sent from my Kindle Fire using Tapatalk
you don't have to unroot first - just redo it
I cant install the drivers. They were on there at one point because I.was rooted. Now my kf says I'm not. So I am trying to reroot. No matter what I try....I cannot get the drivers to install. Ive tried uninstalling and reinstalling, rebooting kindle, rebooting computer. Running out of options.
please help
Thanks in advance
Sent from my Kindle Fire using Tapatalk
the drivers on the computer have nothing to do with the root status of the kf
would suggest to use newest kfu and extract it to c:\ and rename to "kfu"
now you have the drivers in c:\kfu\drivers\kindle
you can try to use install_drivers.bat if you'r on an english os
if not you can change the country value in the file c:\kfu\drivers\dpinst.xml from 0x0409 to your country value (eg 0x0407 for gemany)
if you get "install failed (unsigned)":
Follow these steps to set driver verification levels:
1.Press [Windows]Break to display the System Properties dialog box.
2.Select the Hardware tab and click the Driver Signing button in the Drivers panel.
3.Select the Block-Never Install Unsigned Driver Software button. (Verify that the Make This Action The System Default check box is selected.)
4.Click OK twice.
if you are not able to get the drivers running with the installer (install_drivers.bat) you can do it manually:
that's only a loose description that you see how it is done
if you' asked for a driver:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
if you'r not asked and want to update the driver:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
if you have the code 10 problem:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
now you should be able to install the drivers ...
right driver for the actual bootmode:
normal & recovery mode -> android composite adb interface
fastboot mode -> android adb interface
test the drivers:
open a (elevated) command prompt and cd to c:\kfu\tools
if kf is in normal or recovery mode (twrp) issue "adb devices" - it should return ser.nr. and mode
if kf is in fastboot mode (yellow triangle or "kindle fire" static") issue "fastboot -i 0x1949 getvar product" - it should return "kindle"

ADB, Samsung_Android and Win x64 - Solved

After many hours googling and searching here, I have finally successfully rooted my new Verizon Galaxy S4 (SGH-i545), and it had nothing to do with the root process itself, but it was the basic setup that was giving me fits.
Googling and searching has shown that this is actually a common enough problem with some Samsung devices, and there is a fix for it. Since I had to combine several different processes, I thought I would add a note here on how to get the device connected. I will leave the rooting and other discussions to the others. I am also going to give credit to arpruss, most of the steps here come from his work on the Epic. I have trimmed down to only what is necessary to get ADB working properly.
This assumes that you have already tried the various processes to install or update drivers, and that has not worked. Also assumes mid- to advanced user skills:
1. Install KIES. (Downloading the separate driver package didn't work--the driver package refused to install.)
2. Set device in USB Debug mode (Settings | Applications | Development | USB debugging(x)).
3. Plug device into computer.
4. Run Device Manager
5. Look for SAMSUNG_Android. You shoud see it in the Other devices section.
6. Right-click on "SAMSUNG_Android".
7. Choose "Update driver software" | "Browse my computer for driver software" | "Let me pick from a list".
8. Make sure "Show All Devices" is selected and click on "Next".
9. Click on "Have Disk" and type in "C:\Program Files (x86)\Samsung\USB Drivers\25_escape" (auto complete made it easier to type; if you have 32-bit windows, the " (x86)" should be omitted).
10. You will get a two-pane selection of the drivers. Selecting one of the two "SAMSUNG Electronics Co., Ltd." listings (you may need to look through both) in the left pane gives an option list on the right that includes two "SAMSUNG Android ADB Interface".
11. Choose the first "SAMSUNG Android ADB Interface" and click on "Next". You will get a warning that Windows cannot verify compatibility. Accept this. Windows will install the driver and once it's done you'll click on "Close".
12. Windows installed the driver and ADB started working. (If it didn't start working, I would now have gone back to the Device Manager, right clicked on "SAMSUNG Android ADB Interface", and then redid steps 7-11, but this time with the other "SAMSUNG Android ADB Interface" driver.)
This is enough to get adb working. But it's still probably worth fixing the CDC Serial device.
13. Repeat steps 7-11 in the Device Manager with the "CDC Serial" device now, except that instead of the ADB driver you will look for and install "Samsung Mobile USB CDC Composite Device" in the right pane in steps 10-11.
If all goes well, you will get more spinning stuff in the task bar, and eventually Device Manager doesn't show any devices in "Other devices" with yellow triangles. But if things go for you like they did for me, you'll have "CDC Abstract Control Model (ACM) in "Other devices".
14. Repeat steps 7-9 in the Device Manager with the "CDC Abstract Control Model (ACM)" device now. (You may have some USB Modem options showing up in some places, but I ignored those, and did the same "Have Disk" move as before.)
15. I got a single-pane display showing only "SAMSUNG Mobile USB Modem". (Maybe you'll have two-pane display and you'll have to find it as in steps 10-11.) Select it and click "Next". I didn't get any warnings. Windows will install the driver and once it's done you'll click on "Close".
At this point, Device Manager showed all devices correctly functioning. And "adb shell" worked fine.
16. If you don't want KIES, just uninstall it, but make sure not to uninstall the drivers (the KIES uninstaller will ask).

[Q] Help with USB Drivers for Nook Simple Touch

The current project I am trying to work on is trying to get USB mode to work on a rooted NST with NookManager. I have found a guide somewhere else, but it requries pushing boot and uimage files from ADB. I have tried everything I could, even using Ubuntu in Vbox but I haven't been successsful yet. For whatever reason, the USB isn't being read in Vbox-Ubuntu correctly and can't be mounted.
I have done everything I could to install the USB drivers on Windows properly, but I haven't had any luck. I have scoured the forums, but I couldn't find anything. What I need help is how to uninstall what I have reinstall correctly. I have tried the uninstall fuction in device manager but if there is a better way of doing this I haven't found anything. Can anyone help? Point me in the right direction at least? I hope if i can at least get the drivers installed correctly and adb devices to read it properly, I can figure out how to do everything else. It's just that one hurdler I'm having issues with.
I am running win 8.1 pro but willing to use ubuntu if necessary.
I should also mention what I have done. I Have altered the android_winusb.inf and the adb_usb.ini files, which sort of worked, but I still have yellow exclamations ove the device names.
Well, what do the Yellow Warnings say?
The first step is to get the category in Device Manage "Android Devices" (or "Android Phones") with a device listed under it.
If you have yellow, what driver does it say it has loaded?
It should be using WinUSB.sys
What does it say when you try to reload drivers?
If it suggest "Composite USB Device" accept that.
If you are using the latest version of adb.exe (819,200 bytes) it will already have the vendor ID in it for Nook.
You will not have to modify adb_usb.ini (not that it will hurt anything).
The first step is to get the driver installed (obviously).
abd.exe should be able to connect.
If you have a problem you could try omaplink.exe as an independent check of ADB.
Renate NST said:
Well, what do the Yellow Warnings say?
The first step is to get the category in Device Manage...
Click to expand...
Click to collapse
Well to say the least, it's mess
Anyhow, the category is "Other Devices - Nook SimpleTouch"
Driver Provider: Unkown
When I try reinstalling it says:
Windows found driver software for you device but encounterd an error while attempting to install it.
Android Composite ADB Interface​The system cannot find the file specified​I have done the Advance Restart for Win 8 that disables the driver signatures and I still get this message.
The modified .inf file has to be where it was originally.
That is, in the same directory as:
Code:
android_winusb.inf
i386\WdfCoInstaller01009.dll
i386\winusbcoinstaller2.dll
i386\WUDFUpdate_01009.dll
Renate NST said:
The modified .inf file has to be where it was originally.
That is, in the same directory as:
Code:
android_winusb.inf
i386\WdfCoInstaller01009.dll
i386\winusbcoinstaller2.dll
i386\WUDFUpdate_01009.dll
Click to expand...
Click to collapse
It's in the adt-bundle folder under ~sdk/extras/google/usb_driver. Should it be in the i386 folder?
I just meant that you can't take android_winusb.inf from where it was, edit it, plunk it down somewhere else and try to run it from there.
I don't know about "adt-bundle".
Do those 4 files listed above appear together in the same relative positions?
When you try to update the driver keep saying NO until you get to the "Have disk" button.
Renate, your questions helped me figure it out.
Yes all the files are where they are suppose to be in the same relative position that you outlined.
So i did this to get the "Have Disk Button"
I first did a right click "Update Driver software
1. Browse for driver on computer.
2. Clicked "let me pick from a list of device drivers"
3. A windows that says "Select your device type from the list below:"
4. List gives options includes Show all devices, ADB Interface, Android Device
5. I chose Android Device: It gave me a selection of devices and Nook Android Interface was there. I selected that and installed.
6. I then went to the command tutorial and typed in adb devices and I got the serial numbers.
I wrote this out for future refence for myself, and in the hopes it will help someone else.
thank you so much Renate! You were a huge help! I can't wait to start using your USB Host!
Renate NST said:
I just meant that you can't take android_winusb.inf from where it was, edit it, plunk it down somewhere else and try to run it from there.
I don't know about "adt-bundle".
Do those 4 files listed above appear together in the same relative positions?
When you try to update the driver keep saying NO until you get to the "Have disk" button.
Click to expand...
Click to collapse
I'm glad that worked.
I actually meant saying even more Nos until an actual "Have Disk" button appears.
Window caches the driver inf files and you could have had a bad one.

Diagnosing USB Driver and ADB issues in Windows

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

Categories

Resources