Database Users

[Q] Help in installing adb drivers

My vibrant is stuck on the vibrant logo after I tried to use the one click unroot program. The only solution I found after two days searching on the net, is to use odin. The first problem is that my phone is locked, so I can't use the vol up+down+power button combo to get into recovery or download mode.
Now comes the issue, I want to use adb to reboot the phone, but adb can't see my device. After installing the samsung USB Drivers, I see that the adb drivers are not installed (The drivers for this device are not installed. (Code 28)), and even when I try to manually install them from the SDK drivers (I checked the "include subfolders) it says that it can't find them.
I have windows 7 x64
Anyone have suggestions to how to install the adb drivers and make the adb see my device?

Can you get into download mode? Have you tried to Odin back to stock? If you want to set up ADB type ADB for dummies in search and you should find everything you need.

Here is the link from the sticky thread for help with drivers:
http://forum.xda-developers.com/showthread.php?t=728929

I just figured out a neat trick to get phone to work even if it's stuck on the vibrant screen.
Just connect it to the usb, wait until the grey battery picture appears.
After 5 seconds, take the battery out and put it right back, (leave usb in) and wait again. Do it once more, until you see that the battery picture turns green. After that take the battery out and unplug the usb, and turn the phone on.
It should work now.
The thing is that, next time you turn the phone off and on, it would be stuck again, so do something to fix it like odin.
That how it worked for me.
And about the adb driver problem, I just pointed manually the driver update to the "USB Drivers" that TGA_Gunnman posted here (I can't post link. just search usb drivers here in the forum) and after that adb worked like a charm, rebooted instantly to download mode - it's crucial for those like me that have hardware locked phones.
The thing is, that all the other posts say to point it to the sdk drivers, but that dosen't work.
Good luck to all others.

installing the samsung drivers and installing adb are two different things. the samsung drivers should install normal by double clicking the driver package (you may have to still tell windows where to look). installing adb is simply downloading the sdk, however, if you want adb to work everywhere (instead of just the sdk/tools folder) you need to put the sdk/tools folder in your path.
then 'adb devices' should show your device in win powershell, but will only work if you are in the sdk/tools folder or have added it to your environment variables.

[Q] Kindle fire bricked, adb : device not found, help me

First, sorry for my english.
I have a Kindle Fire OS 6.2.1. I dont know why my Kindle didn't work with ADB driver.
Only one time it work when I used Kindle Fire Utility 0.9.1, then I run option 2 then 3. After that, my Kindle reboot and stop at logo's screen, and adb didn't recognize my Kindle anymore.
I tried install/uninstall, downloaded new driver, install Android SDK,.... but don't luck.
All method to unbrick need adb work well.
Help me fix this issue, please. I live in Asia and can't return my Kindle for Amazon.

first - have you read and done the tricks from 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
second - don't use the drivers from kfu - do according:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54

This helped me get out of a brick 4 times I hope it helps you-
http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222

Just to be redundant this is not a 'brick'
Confirming the driver issue- gotta use diff drivers I restored my Win8 to the kfu .6 just to get adb working
Sent from my Amazon Kindle Fire

b63 said:
first - have you read and done the tricks from kfu ?
second - don't use the drivers from kfu - do according:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
Click to expand...
Click to collapse
The 2nd option help me out to get my kindle fire recognized.
Thanks.

On mine I booted it up to the firefirefire logo and right before the screen flickered I'm not sure if yours does that) I ran a command on the an adb shell command then re ran Kindle fire utilitity's taro installed and it fixed it!

I spent two weeks with a similar problem, finally have everything working. My biggest problem was a USB to micro USB cable that worked fine for charging, but seldom worked for communication between the Fire and my PC. Try another cable.
If your PC beeps when you insert the USB cable, then the cable is probably OK.
Next likely problem is that you don't have ADB installed properly. You can check this by typing adb help at the CMD prompt. (START, RUN, CMD, adb help) If you get a lengthy response, then ADB is installed OK. If you get an error msg, then you need to fix that. Google "How to Install ADB"
If ADB is OK, and you still can't see your Kindle, you probably haven't updated your PATH Variable properly. "How to Install ADB" should include instruction for doing that, but you need to be sure you enter the actual path that your have to the SDK Platform_Tools folder on your PC, not the one described in the video.
Once I managed to get these three thing all working at the same time, things started to fall into place. To most of the people on this forum, these things are probably obvious, but to an old geezer like me every step is a painful learning process.
Good luck

[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.

[Q] ADB will no longer see Kindle Fire ***NEVERMIND**

I had it working about a hour ago and rooted with burritoroot, but now ADB can no longer see the tablet. Any ideas? So far I factory reset the tablet and I'm stuck. USB drivers installed, win.ini and no connection. Mass storage works but ADB is at a loss...
When I hook my phone up, ADB sees it no problem, when I hook up the Kindle, nothing.....
I'm pulling my hair out here..........
edit...........ok I'm a dumbass I fixed it by mistake.

you should try manually installing the drivers again sometimes it doesnt work all the time but if that doesnt work you should also try installing kindle fire utility and installing drivers from there
lol didnt see you awnser it yourself

[Q] Problem...Recovery with no ROM to flash or USB recognition

Hi XDA. I have a problem and could use your help.
In order to make flashing ROM’s easier for myself I thought it would be a good idea to place them in the first folder listed on the internal sd card. In order to do this I placed a “.” befor the name of the folder. After wiping everything I learned CWM 5.8.1.8 (touch) does not see folders with dots(“.”) at the beginning. So I now am in recovery with no ROM to flash
I then proceeded to dig an even deeper hole for myself. In my attempts to install drivers for my device I have done something; now my computer fails to recognize that the device is plugged into the USB at all. Prior to my messing with it I would hear the USB input chime and Device Manager would show an “unknown device”. Now when I plug in my device nothing happens. I have tried two computers and both Win7 and Ubuntu.
I read that Linux might be able to see my device so I installed Ubuntu then the Android SDK as per this thread. It did not work for me. I still cannot see my tf101 but I can see my Nexus s with the “adb devices” command.
I bought my tf101 refurbished and can’t find the “B” version written on the device. I think I initially rooted with razorclaw...not %100 sure. I am not sure adb debugging was checked when I wiped...not sure it makes a difference at this point.
I am now looking at these NvFlash instructions but I can’t get past the 2nd step (I am a noob...obviously)
- run “./blobunpack recovery-clockwork-5.8.2.1-tf101.img” (Replace “recovery-clockwork-5.8.2.1-tf101.img” with the name of your downloaded file”)
Will this NvFlash tutorial work if the computer can’t see the device?
Any ideas?
Thanks for your time!

Try those steps from this website Reverting to Stock ROM (unroot and remove CWM recovery)
this is easier for you when u try to nvFlash your tf101. remember update driver, run as administrator on program

Thanks for the info!
I am away until tomorrow evening. I will try it then.

Hi,
I am still having problems.
Can I install drivers if the device is not listed in device manager? How?
Thanks again!

it will be reinstall or request when you unplug and plugin back your connect from tablet to PC
if your driver had been load or connected just go to Devices and Printers to check your connection, after that update your driver

Hi. Thanks for trying to help.
My problem is my computer is not seeing the device at all. No USB input chime. Nothing showing up in device manager. No nothing!
Could be the chord I guess but I don't think so. I was getting "unknown device" in device manager initially after I wiped the ROM. After attempts to install drivers I stopped getting any sign of the tf101 in device manager.