Develop Bugs

[Q] no adb after firefirefire - SOLVED

my computer won't recognize the kindle fire in adb. I have the kf rooted. have firefirefire installed. after firefirefire was installed is when I lost adb. I have tried reinstalling the drivers numerous times to no avail. Any suggestions?
I have deleted all previous sdk, usb drivers or anything android related from computer to start from scatch. I did a factory reset on the kf. I currently have KFU v0.9.3 setup from instructions i followed on a youtube video titled (How to Root - Kindle Fire 6.2.2 BurritoRoot3) by Nat3Mil. sorry I would post a link but apparently I can't until I have 8 posts.
kf v6.2.2
win7
thanks

maybe this helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
and check "adb_usb.ini" in the ".android" folder in your personal folder
it should include 0x1949 - i use to add 0x18d1 also in a new line

Sound like your Fire is in Fastboot. This happened to me last week. If you are able to load the drivers in manually, then you should be able to use the following commands:
adb shell su -c "idme bootmode 4000"
adb reboot

b63 said:
maybe this helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
and check "adb_usb.ini" in the ".android" folder in your personal folder
it should include 0x1949 - i use to add 0x18d1 also in a new line
Click to expand...
Click to collapse
I have followed those steps in the link before and did it again but no difference. I don't have the adb_usb.ini file or the .android folder. only "Kindle ADB" and "kfu" folders both on the root of the c drive.
vwpower44 said:
Sound like your Fire is in Fastboot. This happened to me last week. If you are able to load the drivers in manually, then you should be able to use the following commands:
adb shell su -c "idme bootmode 4000"
adb reboot
Click to expand...
Click to collapse
load the drivers manually and it acts like everything is good but adb still won't recognize the kindle under adb devices

zachjen said:
I have followed those steps in the link before and did it again but no difference. I don't have the adb_usb.ini file or the .android folder. only "Kindle ADB" and "kfu" folders both on the root of the c drive.
Click to expand...
Click to collapse
without the .android folder in your personal folder and the correct adb_usb.ini adb will never work !
create the .android folder and copy the file from c:\kfu\drivers\kindle to the .android folder

Thank you a million times! All is well again.
I had that folder and usb file before when it couldn't be recognized and forgot to put them back I guess.

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

b63 said:
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Click to expand...
Click to collapse
I can't get this to work.
I've been trying to root/install jb on my kindle fire hd I bought today. I downlaoded the android sdk, installed the proper pacakges. Ran cmd and did "adb devices" no devices found. Enabled ADB on kindle fire, no devices found still. I've now downloaded the kfu and copied the file over just like you said (as well as installed the driver) and still to no avail.
I'm running Win7 64bit.
Any ideas?!?

You might be able to root the hd but the 1st gen. methods will not work and you will not be installing jelly bean at this point it`s not even possible. The hd forum can be found here http://forum.xda-developers.com/forumdisplay.php?f=1782

KF Failed Root

Hi guys! I'm new to the forum but not new to the IT world and not new to Linux or Android devices.
I'm stuck at the Kindle Fire screen after a failed attempt to root the device. Here's what I did. I'm hoping somebody can please help me. I did lots of Google searches to try to solve my issue and I can't seem to find the right solution.
So here's the background. I tried to root my KF by using this process http://www.pcworld.com/article/244303/how_to_root_your_kindle_fire.html on an Windows 7 VM. Then I found that SuperOneClick didn't work for KF6.3. So then I tried to KF Utility v.0.9.5 http://forum.xda-developers.com/showthread.php?t=1399889
I selected the option to root the KF. After it went through the process and I got the Kindle Fire screen (which is sounds like the KF is in the fastboot process) I couldn't get anything to work at that point. I couldn't get the VM to even see the KF nor Ubuntu (which is the main OS of that laptop). So then I figured I bricked the device. So I followed these instructions http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/ but that won't work ecause the KF isn't being recognized by the OS. SO at that point, I couldn't get anything to work. So I rebooted the laptop (which is running Ubuntu 12) and the KF booted back up and it fired back up.
If I power off the KF and turn it back on, it gets stuck at the KF bootup screen.
So at that point I decided to throw Windows 7 on a different laptop that I have and see if I can get it to work. So I installed java & Android ADK for my OS (Windows 7). I installed the USB driver and updated the packages. So I go through these instructions first http://forum.xda-developers.com/showthread.php?t=1568340 and I can't get the KF to be recognized as a device through adb. So I go back to the PC World instructions (linked above) and I follow steps through step 8. And I still can't get the KF to be displayed through adb. When I try to kill the adb server and then enter adb devices, I still can't get the KF to be recognized.
Oh and btw, Windows 7 does recognize the device as a "Kindle".
Any help would be greatly appreciated.
Sparty On!

Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works:
Sent from my Amazon Kindle Fire using Tapatalk 2

Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.

I'm having the same problem I think since windows doesn't recognize my kindle I can't install the drivers.

AndroidSparty said:
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
Click to expand...
Click to collapse
Us the same commands without -i 0x1949
fastboot oem idme bootmode 4000
fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk 2

ammubarak said:
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works
Click to expand...
Click to collapse
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567

From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA

I received mine with 6.3 and KFU wouldn't recognize it even after using the driver installation. BUT I found way around it. You need to install the drivers manually, and then KFU will work. Download the drivers, then extract the .android folder (create it if you don't have one) to
C:\Documents and Settings\YOURUSERNAME\.android open up your device manager, click on the Kindle and follow the UI to select the .android folder. Restart and use KFU. Enjoy!

soupmagnet said:
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
Click to expand...
Click to collapse
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
backspacepc said:
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!

AndroidSparty said:
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
Click to expand...
Click to collapse
Actually it will, status will still be off line, just select the boot mode option, and then on the next screen select normal bootmode
Sent from my MB860 using XDA

For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.

soupmagnet said:
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
Click to expand...
Click to collapse
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA

backspacepc said:
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Actually...I'm a she.
Since I have both available to me...it sounds like I should scrap the Windows (which is an understatement anyway) and use Linux/Ubuntu. That I can do!

I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.

AndroidSparty said:
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA

backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
You may also want to try to rerun your root script, oddly enough I've had that work before too.
Sent from my MB860 using XDA

AndroidSparty said:
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Did you notice the second post in the Linux tutorial?
kinfauns said:
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse

backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I just ran kfu and I I was able to get it to do a normal boot. YAY!
Then I ran the .bat file in the KFU and I selected the permanent root. During the activating fastboot, it said that "Oops something went wrong...." it couldn't find the kindle. Then it installed twrp.img is missing and it downloaded successfully. So then I got the Notice, and it's installing TWRP and it's waiting for the device. I turned the Kindle off & on a few times to get the KFU to recognize the Kindle, and no luck. At least I was able to boot into the KF while it's still still waiting for the device. BUT....at this point during the TWRP install process, it's waiting for the device and not recognizing it.

soupmagnet said:
Did you notice the second post in the Linux tutorial?
Click to expand...
Click to collapse
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.

AndroidSparty said:
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
Click to expand...
Click to collapse
I can't imagine why using vi would make any difference but you could try gedit to see if it works.
As for TWRP, you could install it manually (Windows). Make sure you have a connection with adb/fastboot and use KFU to set your device to fastboot mode. Keep in mind when you do this that you may have to go through the whole process of fixing your drivers again (blame Windows/KFU).
When you're in fastboot mode, hold the power button until the device shuts down.
Shift + right click the KFU folder that contains fastboot (tools) and open as a command
In the prompt that comes up, enter:
Code:
fastboot -i 0x1949 flash recovery /path/to/twrp2.1.img
When your prompt says "waiting for device", turn the device back on.
Make sure it's twrp 2.1 Version 2.0 is installed in a different manner and will most likely cause problems if installed with the "flash recovery" command.

Kindle bricked - Can't find the solution anywhere

Hey guys,
so I'm pretty new to the whole android scene and thought it would be a good idea to root my kindle fire. So, i went and downloaded the kindle fire utility and hit install permanent root with superuser.... but didnt put on twrp. oops. I was one of the few unfortunate ones whos rooting didnt work so smoothly. Now i have a kindle that is stuck on the stock start up screen indefinitely. When i plug it in it says windows does not recognize the device - just install the drivers, no big deal right? wrong. i installed the android sdk and all that jazz, and i installed the drivers packed with the kindle fire utility, and still my computer recognizes it as a universal serial bus controller.
every guide for unbricking either assumes you have twrp, or that the re installation of drivers will fix it. im at a complete and utter loss

Josepho1997 said:
Then, in cd to fastboot in cmd and type:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
So, i installed the drivers, and opened up the cmd window, but i have no idea how to navigate to the correct directory through cmd now. sorry about my ignorance, really, but could you break t down a tad more?

cellophanemask said:
So, i installed the drivers, and opened up the cmd window, but i have no idea how to navigate to the correct directory through cmd now. sorry about my ignorance, really, but could you break t down a tad more?
Click to expand...
Click to collapse
Navigating to a directory is very easy.
Type cd and then put the file path after it.
Example:
cd c:\Program Files\ Adobe

Shift+ right click on the tools folder in kindle fire utility select open command window here.

[Q] Code?

My KF is bricked. It has TWRP on it but it has been wiped clean and my pc will not recognize it. It does in ADB, I keep seeing write the CODE: then stuff. I was told I could to where I needed to write this code by right clicking on the KFU Tools folder. I then get C:\android\Kindle Fire Utility>
Now that being said.. where do I begin to type the fastboot -i Ox1949 and so on. Sure do need some much appreciated help assistance.

Boot into TWRP and then do what Josepho1997 said. Then you can just flash the rom.
The "Rom.zip" would be the file path to wherever the rom is saved on your computer.

Where can I write the tag
Josepho1997 said:
So you just have no OS?
Boot into TWRP. Then Download and transfer the ROM via adb
Code:
adb push Rom.zip /sdcard
Then flash the ROM.
Sent from my Kindle Fire
Click to expand...
Click to collapse
But where do I code?

adb in cmd not recognized as a command
Josepho1997 said:
In cmd. Open up cmd, run adb, and then type that code. And remember what veeman said. When I say Rom.zip, you must put both the correct name and directory applicable to you. (Ex. C:\AlienDroid.zip)
Sent from my Kindle Fire
Click to expand...
Click to collapse
in cmd, adb is not recognized as a internal or external command, operable program or batch file.
Know how long it's been since I used cmd. Help me out please.

You need to open the cmd window when you are in the directory that contains the adb.exe file. Usually this is in C:/kfu/tools directory. The easiest way to do that is to use windows explorer and navigate to that directory then press shift and right click your mouse then select the option "open command window here". You should now be able to issue adb commands.
Sent from my Amazon Kindle Fire using Tapatalk 2

nacraracer said:
in cmd, adb is not recognized as a internal or external command, operable program or batch file.
Know how long it's been since I used cmd. Help me out please.
Click to expand...
Click to collapse
Easiest way is to download the Kindle Fire Utility and then navigate to the tools directory in the command line. Then you can run adb and fastboot commands.

Still won't communicate
veeman said:
Easiest way is to download the Kindle Fire Utility and then navigate to the tools directory in the command line. Then you can run adb and fastboot commands.
Click to expand...
Click to collapse
I have tried everything to get the computer to see the kindle. adb commands are not working. Just says waiting on device, tried to adb push a rom and it just said device not found.
I was able to bring up a fastboot menu one time but once there it wouldn't respond.
Any ideas please.
I am looking at the TWRP v2.2.0 screen. It will not mount either

nacraracer said:
I have tried everything to get the computer to see the kindle. adb commands are not working. Just says waiting on device, tried to adb push a rom and it just said device not found.
I was able to bring up a fastboot menu one time but once there it wouldn't respond.
Any ideas please.
I am looking at the TWRP v2.2.0 screen. It will not mount either
Click to expand...
Click to collapse
Have you installed the drivers?

veeman said:
Have you installed the drivers?
Click to expand...
Click to collapse
I did install the google drivers at the fire tool kit

[Q] how to restore back to stock after invalid CM10.1 instal.

hallo
1)i have a kindle2-root this-install cm10.1-but the mistake was "wipe internal storage".after install.
now it starts but no menue etc.
now i have to restore back to stock and flash again.
2)i have a fastboot-cabel
how can i flash the stock software/OS ????????
thx for help
reinhardrudi

Use this:
http://forum.xda-developers.com/showthread.php?t=2096888
If you have issues i can tell you the steps to restore manually, but it should work for you.
Edit: if that doesn't work you can also try this instead:
http://forum.xda-developers.com/showthread.php?t=2035047
--
Sent from my mind to your screen.

mindmajick said:
Use this:
http://forum.xda-developers.com/showthread.php?t=2096888
If you have issues i can tell you the steps to restore manually, but it should work for you..
Click to expand...
Click to collapse
hello
i have issues-is it possible you can tell me the steps ??
my bigest problem is,that i cant really install ADB driver-i test a lot of tutorials, also in german forums,but nothing helps.perhaps the kindle cant aktivate the adb at himself ??? because of the broken CM10.1 installation (wipe internal storage)
mfg
reinhardrudi

Windows or Linux? What version?
Sent from my SGH-I727 using Tapatalk 2

Enhaphym she
mindmajick said:
Windows or Linux? What version?
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
servus
win7x64
THX

@reinhardrudi,
when you say "i cant really install ADB driver", do you mean you have installed the drivers, but Windows fails to detect your Kindle when plugged into your PC's USB port?
On your PC, please check if file "adb_usb.ini" is present in folder "C:\Users\<your username>\.android\" (please note the leading dot in ".android").
I should contain the line "0x1949".
If you don't have this file (or it does not contain above-mentioned line), just create it with a normal text editor, e.g. Notepad.
Again, it only needs to contain one single line:
0x1949
and must be located in folder
C:\Users\<your username>\.android\ (assuming you have not changed the location of the user profiles on your PC).
Hope this helps

E_Zatopek said:
@reinhardrudi,
when you say "i cant really install ADB driver", do you mean you have installed the drivers, but Windows fails to detect your Kindle when plugged into your PC's USB port?
On your PC, please check if file "adb_usb.ini" is present in folder "C:\Users\<your username>\.android\" (please note the leading dot in ".android").
I should contain the line "0x1949".
Hope this helps
Click to expand...
Click to collapse
hello and THX
i have access to kindle to put files on it.but all the ADB/fastboot access test are failed. the kindle does not respond.i have no separately entry in the device manager.only under "mobile devices (in german "tragbare geräte")
Amazon Kindle Fire2 and the driver is a microsoft driver!
yes-i have this ini with "0x1949".
thx
reinhardrudi

@reinhardrudi
OK, let's try it this way:
In your very first post of this thread you mentioned you had a "fastboot-cabel".
When you connect the Kindle to your PC via this cable, does it come up in fastboot mode? If it it does, it will clearly display "fastboot" on the Kindle's screen - so there's no mistaking any other condition with the fastboot mode.
With the Kindle in fastboot mode, please open a command prompt (aka DOS box) and enter "fastboot -i 0x1949 getvar product" (without the quotation marks) and hit the [Enter/Return] key (assuming the directory where you have fastboot.exe and adb.exe residing is your current directory - if not cd into this directory first). Please post the result.
If your cable does not trigger the device to boot into fastboot, then it's most probably NOT a factory cable. Please note that the USB cable that comes with the Kindle by default is NOT a factory cable. A factory cable is specially wired to force the Kindle to fastboot mode.
Please run the test described above and come back here with the results. We'll then take it from there.

E_Zatopek said:
@reinhardrudi
In your very first post of this thread you mentioned you had a "fastboot-cabel".
When you connect the Kindle to your PC via this cable, does it come up in fastboot mode? If it it does, it will clearly display "fastboot" on the Kindle's screen - so there's no mistaking any other condition with the fastboot mode.
With the Kindle in fastboot mode, please open a command prompt (aka DOS box) and enter "fastboot -i 0x1949 getvar product" (without the quotation marks) and hit the [Enter/Return] key (assuming the directory where you have fastboot.exe and adb.exe residing is your current directory - if not cd into this directory first). Please post the result.
Please run the test described above and come back here with the results. We'll then take it from there.
Click to expand...
Click to collapse
hallo and THX for help
look at this picture-link:desktop-screenshot.
http://imageshack.us/photo/my-images/96/fastboot2.png/
and look her,my device manager after install all kindle drivers and boot kindle in fastboot-mode.
http://img18.imageshack.us/img18/5925/otter2.png
1)i get fastboot on my kindle-
2)but with your command i get a message: "waiting for device" .
mfg
reinhardrudi

reinhardrudi said:
hallo and THX for help
look at this picture-link:desktop-screenshot.
http://imageshack.us/photo/my-images/96/fastboot2.png/
and look her,my device manager after install all kindle drivers and boot kindle in fastboot-mode.
http://img18.imageshack.us/img18/5925/otter2.png
1)i get fastboot on my kindle-
2)but with your command i get a message: "waiting for device" .
mfg
reinhardrudi
Click to expand...
Click to collapse
The picture quality is awful.. But- it looks like there is an exclamation point next to your otter2 device.
Is that correct?
If so, the drivers are not installed
Sent from my SGH-I727 using Tapatalk 2

mindmajick said:
The picture quality is awful.. But- it looks like there is an exclamation point next to your otter2 device.
Is that correct?
If so, the drivers are not installed
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
yes i know-i test every driver here and in german forums-but no driver works for me.
did you know the name of the driver in the windows driverstore??????perhaps i can install the driver manually.
i never had so mutch trouble with any device what i get/buy,and i buy a lot of devices for PC etc.
THX

I used the drivers from here:
http://forum.xda-developers.com/showthread.php?t=1893838
I also installed manually. Please let me know if this helps
--
Sent from my mind to your screen.

hello again
after 2 hard weeks,and a lot of reading in this and other forums,many questions etc. i found a solution to install the driver correkly for my kindle
:laugh:
what did i have done??
after i had tested every cm 10.1 nigthly and the original 4.2.2 rom,every kindle USB- driver in this world--nothing,--no chance to install the kindle on 3 div. PC (win8+ win7) and 1virtual. Win7 Prof. x86
than i delete my cm10.1 inkl. gapps installation complete,and test the UNOFFICIAL TeamBAKED Black Bean 9 inkl. team baked's inverted gapps
http://forum.xda-developers.com/showthread.php?t=2237167
and -its magic-after the first boot and plug-in in my PC, the driver install is correkt in the device manager. i see kindel-ADB device and the driver comes from amazon - :good: Yeeaah.
now i test the kindle first aid again, to go back to stock.rom with the "Option1" when im at home (after work)
i hope everything goes well!!!!!
thx at all people who helps
EDIT: everything OK.first stock rom. Than cm10.1
reinhardrudi