Related
Hey! I'm not completely new at this, I have a little knowledge as regards to rooting and and tweaking different things. But I'm having an issue that I just don't understand how to fix, and I can't find any help on google. So I came here.
BTW, I have Windows XP 32bit.
I'm trying to install the ADB files so the computer can recognize the phone. Before Ive done anything(nothing installed or changed), I can plug my phone into the computer and the phone gives me the option to charge, sync, use as disc drive, or internet sharing. So, I don't know if maybe thats all I need.
I downloaded the adb files for windows from here http:/ /htcevohacks . com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/. I hope its not a vista/win 7 file...
I installed the correct "SDK platform Android 2.1 AP17" and "usb driver revision 3" as the instructions read. I shut the phone off and boot into recovery mode, and then plug the USB in. Nothing happens. Nothing on the computer or the phone change. I don't find any "ADB" in the device manager, and no window pops up asking about updating drivers. I do exactly as the instructions on that site say, but nothing happens.
If the phone is on normally and in "Debugging Mode", I can plug the phone in and the Device Manager shows the "ADB". Also, the window pops up to ask about updating drivers. So I've tried going through both; I specify a location, which for me is c:\android-sdk-windows\usb_driver. It searches for a few seconds, and then says it cant find the right driver for my device.
I really want to start doing some things with this phone, but im stuck! Any help would be greatly appreciated.
read this whole thread
that should help. hopefully
and I think I've just recently read that its not really necessary to install the adb files?
timothydonohue said:
read this whole thread
that should help. hopefully
Click to expand...
Click to collapse
thanks, I'll take a look at it now!
I don't want to bother you with stupid threads and things like that, but I've used the search function on XDA and I'm still lost on this really small problem - my Kindle Fire is not being recognized anymore in ADB.
See, a long time ago (few weeks) I rooted my KF and installed Android Market, whatever. Never installed a recovery or custom ROM. Everything was ok until I tried to install TWRP using Kindle Fire Utility.
While trying to install, I got the famous "adbd cannot run as root in production builds". So I thought it was something with my drivers. Ok, then I installed the drivers that come with KFU - just to screw with everything. My Kindle Fire stopped being recognized by ADB.
I tried: (1) uninstall the drivers and install from KFU again. (2) uninstall the drivers and install the drivers I got from the video-tutorial (the famous one). (3) factory reset the kindle fire and do all the drivers install again. (4) hold the power button 900 seconds to reset the kindle fire and install the drivers again. (5) finally install the drivers on ANOTHER computer (running WinXP instead of Win7) and plug my factory reseted KF.
I gave up.
I don't know why my Kindle Fire isn't recognized by ADB on any computer at all. I thought it was my laptop, but then I tried the same steps I did at the first time using a Windows XP and no good. I don't know.
Can someone help me? Thanks a lot.
i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-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
or you can try this solution:
http://forum.xda-developers.com/showthread.php?t=1430038
b63 said:
i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-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
Click to expand...
Click to collapse
Tried that and didn't work.
I'm going to wait a little more before using Linux, I really wanted to do this using Windows only.
in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu
b63 said:
in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu
Click to expand...
Click to collapse
Right now my KF is normally booting into stock ROM and stock everything.
I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Thanks for your support.
I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
Click to expand...
Click to collapse
xp will be the better choice cause you don't have to hassle with 32/64 bit drivers and the uac (user access control)
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Click to expand...
Click to collapse
add it in another line
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Click to expand...
Click to collapse
seems that the patched version (the whole thread) is deleted - you will have to do it by yourself - take the original from the dev section and:
http://forum.xda-developers.com/showthread.php?t=1454913
The issue persists. I've seen that other people are having the same issue. The device got "unrooted" by unknown reasons and then it's invisible to any adb. As I'm writing to you right now, I'm trying the adb on my brother's Ubuntu. I've tried other solutions using linux but without success.
I'm running out of options here.
I'll admit that I haven't tested the last link you sent, but I can't see how that can change the way adb works on my device. Anyway I'll try that tomorrow.
in the meantime br3 is out - if you use kfu you will have to use an updated run.bat: http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
but you'r right - that will not change the communication
firekit http://forum.xda-developers.com/showthread.php?t=1430038
is worth a try cause linux don't use drivers to communicate
only needs some entries which are included in firekit
maybe try an other cable ?
really running out of ideas at this point ...
I got the same problem.
If you can fix it, please show me how, thank you.
c:\KindleADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
c:\KindleADB>
Just a quick idea. Have you tried the attach the kindle to a different USB port? I had the same issue until I used a different port. The front ports on my desktop are totally fubar, but the port where my mouse was worked when 4 out of 6 ports did not. This for me is probably a hardware problem, but it may help someone.
Sent from my Kindle Fire using Tapatalk
I am having the same exact problem as the OP and I truer everyway to root it and install the drivers but its still not recognized by adb
Its seems i should give up
Similar problem with cm9, and fixed
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.
Push push push it
tried all the steps. and still nothing. dont know what im doing wrong. starting to get pissed. any help would be great, thanks
Save my KF
sudogeek said:
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.
Click to expand...
Click to collapse
Could you help me to fix same problem with window. My PC alway, automatic recognize my KF as normal disk driver. I try to make a factory cab but not success .
Thanks.
Edit android-path.sh
1. On my Mac I opened System Profiler, then checked Hardware > USB > and 'MyDeviceName' (for me its: LePan Tablet PC)
2. Opened this file with a text editor: /Users/MyName/.android/android-path.sh
3. Added a new line in this file with the tablet Vendor Id, for example:
0x22a4
4. Executed: adb kill-server
5. Executed: adb start-server
6. Finally adb devices is showing:
List of devices attached
0163AE9D0801F02C0C280002 device
Bricked?
I think I'm having the same problem, or at least a very similar one.
Using windows XP. I got the drivers working, plugged my kindle into the Kindle Fire Utility, and ran option 2, which seemed like it was the option to create a backup in case you bricked your kindle. It ran, showed up on the Kindle screen, and did it's thing without a problem.
Then, when the kindle rebooted, I got the yellow-triangle-fire symbol. It says 'press power button for recovery', but pressing the power button does nothing. Holding it down for a long time shuts the kindle down, but pressing it again brings it right back to the yellow-triangle-fire symbol.
So I uninstalled the drivers from Windows XP (as another thread mentioned). I now have two ways that I can think of to install the drivers. Using the KFU, I get the "unsigned drivers" shutdown even after I went into the Driver Signing menu and chose "ignore and install regardless".
The other option I have is to install the drivers that I downloaded manually -- the same ones that worked in the first place. Problem with that is that I go through the entire process, selecting the directory the drivers are in and whatnot, and the only thing that happens is I get an error that says "These drivers aren't the drivers for your hardware" or something similar to that.
So neither of my options allow me to actually install drivers for my Kindle Fire, and my Fire itself is in a recovery loop. All of the tools that are supposed to address the recovery loop require drivers, so I seem to be up a creek without a Fire.
Any ideas?
Okay, to enter recovery...When you see the yellow triangle, hold the power button until it turns orange then release. It shouldn't take more than 10-15 seconds. If you still can't get into recovery, reinstall it.
For your drivers...uninstall completely and delete them if you're using Win7. Then reinstall using one of the previous methods.
The power button doesn't do anything when I push it. It stays bright green until the kindle fire shuts down. I'm not sure what "reinstall it" means, sorry, n00biness.
The drivers (winXP as mentioned) I've uninstalled, but I can't reinstall. One option says "unsigned drivers" and the other doesn't recognize the device as a Kindle and thus quits the install with a "this is not an appropriate driver for your device" message.
Thanks for trying, though! I appreciate your time and effort.
I need help! FKU 0.9.5. Drivers set. Kindle is seen by the system (Windows) as Android Phone\Android Composite ADB Interface . When you run status of the ADB is offline, the status of unknown boot. FKU ustonovlena in C / FKU. What is the problem?
Thanks in advance for your help.
sergei pan said:
I need help! FKU 0.9.5. Drivers set. Kindle is seen by the system (Windows) as Android Phone\Android Composite ADB Interface . When you run status of the ADB is offline, the status of unknown boot. FKU ustonovlena in C / FKU. What is the problem?
Thanks in advance for your help.
Click to expand...
Click to collapse
Ustonovlena? What is that? Serbian? Nevertheless. Even when Windows says the drivers are installed, if adb doesn't connect, it's a driver issue. Uninstall and delete your current drivers then reinstall with the device turned off. When you turn the device back on, KFU should recognize it.
If not, try to issue the command you need anyway. Sometimes it will work anyway. Either way, it is a driver issue. Keep working at it. You may have to reboot your computer to get it to work but as long as you understand that it's the drivers causing problems, you should be able to get it working.
try to change to another user,or worst still use another pc.
Not sure if this can work,but its worth a try since mine work this way.
Sorry. I am writing through Google. Russian. Already endured, and once again put the driver. It did not help.
What rom are you using?
Rom?
If I understand you correctly, a native Amazon 6.3.
The reason I ask is that some custom roms have USB debugging turned off by default and others have trouble with adb to begin with.
But, considering that is not the case, it is a driver issue, plain and simple.Just keep trying. Uninstall/delete/reinstall your drivers. It may help to get the Android SDK and configure them yourself.
It has been repeatedly reinstalled the driver. It does not help. Tried on two computers (XP and Vista). The result is the same. The question-whether the Kindle can be seen in My Computer? I have Windows does not see it.
Programmes at the request of the developer to KFU (Vashypooh) to help. Write in the subject can not have enough rights-http://forum.xda-developers.com/showthread.php?t=1399889.
I beg to inform him of my request for help.
Im having the same issue
I cant tell you how many times i have re installed the drivers. Reboots in between.. u name it
One time i did get adb to see my device. But it still wouldn't fast boot
Im on 2.2.. its a brand new refurb..got it today
Sent from my DROID RAZR using XDA
So, I tried searching for days on how to fix my problem.
A little while ago I rooted my Kindle Fire, and it was great. Then I did something. Not sure exactly what. But It ended up just doing nothing. When I boot up the Kindle it shows the blue and white Kindle Fire logo. Nothing else past that (unless I go to recovery.) Now, my computer doesnt recognize it anymore, even after doing most of the driver updates that people on here have said to do.
I need help, basically, getting it back to normal, so I can give rooting a try again. Now that I know what exactly I am dealing with, I can do this and not screw everything up.
First, the computer says the driver is installed, yet it doesnt recognize it.
Second, (before the driver mishap) KFU said it was connected but the adb was unknown.
Third, I have CWM and I tried to flash the normal Amazon update to bring it back, and it says"it cant open it (bad)".
Now, I would really like some help with this. I'm just at a complete lost.
Now should I put that into command prompt in the adb part? because it just says fastboot is not recognized.
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Now its just not connecting to the computer. I installed Android sdk and everything and its just not working. It says the driver is installed but there was an error because a problem had occurred. Any help? :crying:
As soon as you get tired messing with drivers you can move on to something that works http://forum.xda-developers.com/showthread.php?t=1850038
ManofFishFry said:
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Click to expand...
Click to collapse
I hope u r on windows PC..
first after u set up adb, make sure u install adb drivers that came with kindle fire utility with ur kindle fire unplugged..if u had plugged in kindle fire while doing that, go to device manager and uninstall that device and its driver software and start up from beginning..
keep kf unplugged and install driver..u dont get usb debugging option in stock kf rom..its enabled if u have installed the drivers properly..ur kindle fire appears as android phone in device manager if everything u hav done is correct..
then boot up ur kf..that blue and white kf logo is of firefirefire bootloader..i hope its v1.4a and u see it on right top of the screen..if its stuck there then open command prompt as administrator on ur pc..connect ur kf to pc..type in to cmd
Code:
fastboot devices
if u see something under list of devices attached that will be ur kindle fire(unless some other android device is connected in fastboot mode lol)
Because kindle fire, as far as i know, can only boot into 3 bootmodes(normal, recovery, fastboot) unless u have altered the partition table to install different roms and multiboot ur kindle fire..
if fastboot command is not recognized, try setting the path to where fastboot.exe is present in KFU folder
alternatively u can go to folder where fastboot.exe is located and right click while holding shift and selecting 'open command window here' and fastboot needs to firefirefire bootloader to be installed on ur kindle fire..
also u can try this..
JUST GO TO RECOVERY..twrp has always been a better recovery software than cwm based thing available for kindle fire at least for me..if u go to recovery, ur kf will definitely show up as an adb device..u can change the bootmode using this..just type in:
Code:
adb devices
if ur kf is seen as in recovery then type this in cmd
Code:
idme bootmode 4000
reboot
just report if this worked..
okay well, I deleted all the drivers and started from the beginning. Yet, after running the install_driver.bat I plugged my Kindle in and it still says device not recognized. Now, you how can get adb working? It is coming up as unknown device. Its just seeming like theres something wrong on the kindle part. But hey, what do I know. haha
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
But doesn't that require linux? I have windows 7. Is there something like that for windows?
Thepooch said:
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
This is what I get when I try to install the driver....
To run soupkit all you need is at least a 2 gig usb flash drive ubuntu 12.04 32 bit and universal usb creator. By the way your problem with the driver is you (or how you`re going about it), You would trip if I got on your computer and got it to work or could at least tell you why its not working. that`s why I suggested soupkit if you would of actually read the information I gave you, I wouldn`t have had to tell you twice and you would know that to use it it`s not required to be installed on your computer. But hey catch me online I can either help you fight through windows crappy drivers or help you set up soupkit I`m always game for a challenge When updating the driver you need to point it to the 32 bit version of the driver for instance on my computer it`s located here C:\Documents and Settings\HP_Administrator\Desktop\Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers. After it`s ran unplug and replug device if that doesn`t work power off and power on while connected this generally does the trick when windows finally catches on it will install android adb interface, this is the fastboot driver (if you`re stuck in fastboot). Then select option 1 in KFU for changing bootmodes, then option 1 for normal if it does nothing power off and power on while connected it should then detect the kindle and reset the bootmode to normal. Pm me later I will be online all evening and most every evening I will help you sort it out.
Josepho1997 said:
Whoops! Somehow my post was posted twice. I didn't even get to see your reply. Sorry!
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
this is what I get when I try this... (btw im working with firefirefire. its got the blue and white kindle fire.)
Why don't you let me take a look?
Dark__king said:
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
Click to expand...
Click to collapse
Yes soupkit can fix mounting problems.
This is a very interesting issue with this Kindle windows detects it as unknown usb device, drivers are installed properly from what I can see. Ubuntu with soupkit ran on it fails to detect it in recovery or fastboot. multiple cables tried, lsusb doesn`t show the device connected. I really think this one the computer is the problem, because it`s the only unchanged variable.
Firekit may be the only option if Linux won't detect the device. Before doing that, make sure a USB 3.0 port isn't being used and try a fresh install of Linux to be safe. Otherwise, it seems putting it in USBboot is the only option for getting Linux to detect.
I'm not exactly sure what causes the unknown device error, but it almost always means there is something wrong with the bootloader, and it seems as though Windows might be the main culprit. Not sure why exactly, but it may be similar to the problem soulweeper51 had. Possibly a hardware issue involving the computer's USB port or the motherboard itself.
@ManoFishFry has doomlords cwm recovery and he flashed JB at first I thought it was an issue with cwm not being detected but the fact that it`s not detected in fastboot raised my eyebrows. The bootloader appears to be functional but I cannot rule out any minor state of being broken in another fashion when lsusb returns null. The computer doing the work had never been used prior to the incident so driver install didn`t take place till after the fact. The usb ports are all either 1.0 or 2.0 no 3.0 ports are being used. An alternate computer would be nice to rule out the computer itself @ManoFishFry only has a dinosour of an xp machine as alternate use of is not possible yet, not that it would even be possible to install drivers because of the typical unsigned driver failure of xp and booting ubuntu isn`t happening at the moment on this machine.
I'm willing to bet it is the bootloader.
Just USBboot and get it over with.
We did try usb boot once but it didn`t work will keep trying.
Hello,
I successfully rooted my Kindle Fire last year and a few months ago I decided to flash ICS on it. It worked perfectly and I've had no issues so far on it except for one thing that is driving me nuts.
I had downloaded a couple albums and a few magazines on my Kindle and I wanted to get them on my PC. So I proceeded to plug my Kindle as usual and I heard the USB sound on the PC. I checked My PC and my device did not appear there. I checked Device Manager and the ADB Composite thing did not appear either, it now says Amazon Kindle Fire with the yellow exclammation mark.
I suppose somehow the drivers got uninstalled or something, so I tried installing the drivers again... Which is another nightmare because first of all, I'm on Win XP and my computer is in Spanish. So when I double click on the drivers thing it doesn't work. And now when I try to manually install the drivers it won't let me.
I have no idea what to do now, maybe someone can help me with this. I'll be so grateful for any help you guys can give me! :crying::crying:
KindleTrish said:
Hello,
I successfully rooted my Kindle Fire last year and a few months ago I decided to flash ICS on it. It worked perfectly and I've had no issues so far on it except for one thing that is driving me nuts.
I had downloaded a couple albums and a few magazines on my Kindle and I wanted to get them on my PC. So I proceeded to plug my Kindle as usual and I heard the USB sound on the PC. I checked My PC and my device did not appear there. I checked Device Manager and the ADB Composite thing did not appear either, it now says Amazon Kindle Fire with the yellow exclammation mark.
I suppose somehow the drivers got uninstalled or something, so I tried installing the drivers again... Which is another nightmare because first of all, I'm on Win XP and my computer is in Spanish. So when I double click on the drivers thing it doesn't work. And now when I try to manually install the drivers it won't let me.
I have no idea what to do now, maybe someone can help me with this. I'll be so grateful for any help you guys can give me! :crying::crying:
Click to expand...
Click to collapse
When I flashed CM10.1 I needed to download "google android usb drivers" or something...
sghsmorgan said:
When I flashed CM10.1 I needed to download "google android usb drivers" or something...
Click to expand...
Click to collapse
Yup, I've tried every possible solution out there and nothing has helped.
kindle fire not found after cm10
KindleTrish said:
Yup, I've tried every possible solution out there and nothing has helped.
Click to expand...
Click to collapse
Trish: First, I am presuming you are working with a first gen Kindle fire?
I am pretty sure the problem is that the cm10 build is not using the 0x1949 kindle vendor ID and your drivers do not know what to do.
I am not entirely sure how to modify your USB driver ini files but, if you were to install something like USBDview, which lists usb attachments to your PC or, if you were in LINUX for certain and listed the syslog (which prints out all activity on ports basically), you would see a USB connection each time the tablet is connected but, the VID is no 0x1949 but, 18D1. 1949 is the VID for Kindle and I was told that 18D1 is the VID for google devices.
If your PC was set up and configured to work with google devices, I think you would be OK.
I had one person indicate their machine was configured to recognize either Kindle on Google Vendor IDs.
C:\Users\"your user name"\.android\adb_usb.ini
The file normally has 0x1949 listed in it which is the VID for Kindle.
Once cm10 is loaded the VID may no longer 0x1949.
I once tried to add 0x18D1 to the .android/ adb_usb.ini file located in the users base folder but, I did not have any better luck.
This issue happens quite a bit and there are lots of posts indicating that the PC will not recognize the tablet after loading one rom or another or just getting the tablet into one boot mode or another.
galearned said:
Trish: First, I am presuming you are working with a first gen Kindle fire?
I am pretty sure the problem is that the cm10 build is not using the 0x1949 kindle vendor ID and your drivers do not know what to do.
I am not entirely sure how to modify your USB driver ini files but, if you were to install something like USBDview, which lists usb attachments to your PC or, if you were in LINUX for certain and listed the syslog (which prints out all activity on ports basically), you would see a USB connection each time the tablet is connected but, the VID is no 0x1949 but, 18D1. 1949 is the VID for Kindle and I was told that 18D1 is the VID for google devices.
If your PC was set up and configured to work with google devices, I think you would be OK.
I had one person indicate their machine was configured to recognize either Kindle on Google Vendor IDs.
C:\Users\"your user name"\.android\adb_usb.ini
The file normally has 0x1949 listed in it which is the VID for Kindle.
Once cm10 is loaded the VID may no longer 0x1949.
I once tried to add 0x18D1 to the .android/ adb_usb.ini file located in the users base folder but, I did not have any better luck.
This issue happens quite a bit and there are lots of posts indicating that the PC will not recognize the tablet after loading one rom or another or just getting the tablet into one boot mode or another.
Click to expand...
Click to collapse
Thank for your response. I wasn't running CM10 on my KF 1st gen when I had this USB problem. To be honest, I don't even remember what's the name of the ROM I was running. All I have to say is that it was a very poor ROM, very unstable and it was missing a lot of features. For instance, when I went to Settings > Storage I would have no option to turn on the Mass Storage option.
I was so frustrated with this USB issue since I couldn't find a solution or help anywhere, so I decided to flash CM10.1 on my KF and now I have a very stable tablet. When I first tried to connect it to the pc after flashing, the PC didn't recognize it either. But at least I have the mass storage option in Settings > Storage.
Either way, the PC still doesn't recognize my tablet as an Android Phone. But I can get files from my KF to PC and vice versa.
KindleTrish said:
Hello,
I successfully rooted my Kindle Fire last year and a few months ago I decided to flash ICS on it. It worked perfectly and I've had no issues so far on it except for one thing that is driving me nuts.
I had downloaded a couple albums and a few magazines on my Kindle and I wanted to get them on my PC. So I proceeded to plug my Kindle as usual and I heard the USB sound on the PC. I checked My PC and my device did not appear there. I checked Device Manager and the ADB Composite thing did not appear either, it now says Amazon Kindle Fire with the yellow exclammation mark.
I suppose somehow the drivers got uninstalled or something, so I tried installing the drivers again... Which is another nightmare because first of all, I'm on Win XP and my computer is in Spanish. So when I double click on the drivers thing it doesn't work. And now when I try to manually install the drivers it won't let me.
I have no idea what to do now, maybe someone can help me with this. I'll be so grateful for any help you guys can give me! :crying::crying:
Click to expand...
Click to collapse
Some ROMs just don't seem to work with Windows PCs. The latest CM/SG7 one works fine (early versions did not, the ones from around May going forward do). If all else fails, I've never had an issue getting USB to connect when using TWRP's option. A minor inconvenience, but there it is.
KindleTrish said:
Thank for your response. I wasn't running CM10 on my KF 1st gen when I had this USB problem. To be honest, I don't even remember what's the name of the ROM I was running. All I have to say is that it was a very poor ROM, very unstable and it was missing a lot of features. For instance, when I went to Settings > Storage I would have no option to turn on the Mass Storage option.
I was so frustrated with this USB issue since I couldn't find a solution or help anywhere, so I decided to flash CM10.1 on my KF and now I have a very stable tablet. When I first tried to connect it to the pc after flashing, the PC didn't recognize it either. But at least I have the mass storage option in Settings > Storage.
Either way, the PC still doesn't recognize my tablet as an Android Phone. But I can get files from my KF to PC and vice versa.
Click to expand...
Click to collapse
zerbey said:
Some ROMs just don't seem to work with Windows PCs. The latest CM/SG7 one works fine (early versions did not, the ones from around May going forward do). If all else fails, I've never had an issue getting USB to connect when using TWRP's option. A minor inconvenience, but there it is.
Click to expand...
Click to collapse
This has been talked about several times, but for some reason no one ever seems to catch on.
You have to check the hardware IDs reported by your device in the Device Manager for every ROM you install, and make sure the information matches whatever is listed in your 'adb_usb.inf'.