Database Develop

Usb Driver Problems

Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying

magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one

I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.

mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up

magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".

nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything

Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.

alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?

http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery

when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right

have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone

tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"

I believe you can also try "./fastboot-mac flash recovery ./recovery.img"

Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!

you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829

fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder

[Q] Can't get out of recovery mode

First I want to apologize for the double post (post in General)
I used odin to get froyo on the Captivate. That worked fine. When I try and root 2.2, the phone froze and now it won't get out of recovery mode. I have tried every combination I can think of to reboot the phone short of throwing it down the street, but I cannot get out of recovery mode. I am also unable to use the power button (ok key?) to select anything. I can use the volume keys fine for up and down.
One of the errors says:
"(Unknown error: 0) ensure_root_path_unmounted++
ensure_root_path_unmounted (/mnt/internal_sd)
ensure_root_path_unmounted ret 0
unmount(/mnt/internal_sd) attempt 1 (unknown error: 0)
Install default apk-files. finished.
Mind you, I have already tried to put the rooted 2.2 files on the sd card, but still to no avail. Any suggestions? I am really hoping this phone isn't rooted.

So you have a european firmware? Which one is it?
Sent from my phone so excuse the spelling errors

I just fixed it. Reinstalled the firmware with Odin and it's working fine now. Thank you.

dude how did you do that.. I have the same friggin issue and I can't fix it. I'm stuck in recovery mode all the time, as soon as I plug the phone in to charge, or plug it in the computer via usb, or push the power button, the damn thing goes into recovery mode and stays there. I can use the volume buttons to navigate up and down through the options and if I hold the power botton down long enough the phone will turn off and back on again. But if I press the power button once (as in select an option) it doesn't do anything. I tried every single option out there to get into download mode with the battery out and usb in and volume buttons then put bat in....etc nothing works. I need to get into download mode
anyone?................

anyone that is messing with flashing firmwares on their phone needs to learn basic ADB skills.
use the following command in adb:
adb reboot
it will get you out of recovery mode

Pirateghost said:
anyone that is messing with flashing firmwares on their phone needs to learn basic ADB skills.
use the following command in adb:
adb reboot
it will get you out of recovery mode
Click to expand...
Click to collapse
What he said. Plus, I have had it happen sometimes that no matter what I always reboot into recovery. At that point I just adb reboot download and re-flash.

ok thanks. I know I said I have tried everything before but I wasn't completely truthful. I did try ADB though, but I don't think I was doing it right. I downloaded the SDK thing and started a command prompt from "start menue, accessories, and command prompt" but when I type the command "adb reboot download" nothing happens and the command prompt disappears. I don't have much experience with ADB, is there anyway you can give step by step instructions on how to do this? I would very much appreciate it.
Thanks

I found this thread on here "http://forum.xda-developers.com/showthread.php?t=517874" but still didn't help me much. Everytime I type cd c:\Android or any other command I get The system cannot find the path specified.

Here's what I do. After you download the sdk. There is a folder called tools. I copy that to c:
Then opencommand prompt and type,
C:
CD tools
adb reboot
Or, adb reboot download
Of course make sure your phone is connected via USB.
Sent from my SAMSUNG-SGH-I897 using XDA App

thanks I'll try that when I get home. I think this might take care of the problem, because I did keep the folder on the desktop and did not move it to C: folder. Although when I plug in the phone via USB, I still can't establish connection between phone and computer, but I will let you know how it goes after I get home tonight. and I did find some stuff about ADB through google so I might be able to do something with it tonight.
Thanks for the help though

Download odin one click, remove the battery, open odin, replace battery, hold down both volume buttons, and plug the usb cable in. That should get you to download mode unless your 3-button doesn't work.

bobbylx said:
Here's what I do. After you download the sdk. There is a folder called tools. I copy that to c:
Then opencommand prompt and type,
C:
CD tools
adb reboot
Or, adb reboot download
Of course make sure your phone is connected via USB.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Hi, so I did all that heres a copy and paste of what I did and results I got
"Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Shahed>cd c:\
c:\>cd c:\android-sdk-windows
c:\android-sdk-windows>tools
'tools' is not recognized as an internal or external command,
operable program or batch file.
c:\android-sdk-windows>cd tools
c:\android-sdk-windows\tools>adb reboot download
error: device not found
c:\android-sdk-windows\tools>"
I guess it can't be done because the device is not initiated to begin with

jatkins09 said:
Download odin one click, remove the battery, open odin, replace battery, hold down both volume buttons, and plug the usb cable in. That should get you to download mode unless your 3-button doesn't work.
Click to expand...
Click to collapse
tried that still nothing.. keeps saying waiting for device

drhusamali said:
tried that still nothing.. keeps saying waiting for device
Click to expand...
Click to collapse
Find the tools folder in the SDK you dowloaded and extracted, I found a shortcut to it scroll over the tools folder, hold the shift key and right click on the tools folder then choose open command window here.
When the command window opens type the command ADB shell then hit enter, then type adb reboot download then hit enter with your phone plugged into pc. This always works for me. You can always change the path by moving the folder directly to your c drive but this will work for you for now.

Pirateghost said:
anyone that is messing with flashing firmwares on their phone needs to learn basic ADB skills.
use the following command in adb:
adb reboot
it will get you out of recovery mode
Click to expand...
Click to collapse
This has saved my azz a few times.....Learn to use adb mode from PC inDEEED!!!!
Adb recovery adb download ....on and on.....

[Q] Nexus one bricked :( and lost recovery mode

can you help me fix this problem
after wipe all data, cache and anotherthing wipe (it's name very hard to remember ).
I cant use recovery mode, my phone can open fastboot and bootloader, but can't open recovery mode (it's only show a android logo when i press "recovery")
please help me (

I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.

justflikwalk said:
I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.
Click to expand...
Click to collapse
can you show me more, i dont know adb commands, and push new recovery is "recovery clockwork" and "recovery RA". I tried apply them, but it's not work,may be i wrong in some thing, it's the first time i use android phone . throught usb, i have "fastboot usb"
please help me

http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide

but my phone cant connect with PC, atlthough i installed google usb driver.

i might be wrong but cant you just flash a original ruu, than root and reinstall recovery

#1)Go and download yourself a recovery.img file that is compatible with your device and put the image on the root of your SD card (that means on the main directory and not in a folder)
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
#3)Open up your terminal and type in
Code:
su
to gain root access. If you are root the next line should show the
Code:
# symbol
#4)At the next line type in
Code:
flash_image recovery /sdcard/name-of-recovery.img
you will need to replace the code that says name-of-recovery.img with the exact name of the file on your SD card.
#5)Hit enter, wait a few seconds and viola ! you have a recovery again.
Good luck man.

hxq88 said:
but my phone cant connect with PC, atlthough i installed google usb driver.
Click to expand...
Click to collapse
Try the driver from this thread.
It helped me set up my ADB for the N1
http://forum.xda-developers.com/showthread.php?t=613217

#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone

hxq88 said:
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone
Click to expand...
Click to collapse
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?

baseballfanz said:
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?
Click to expand...
Click to collapse
i typed ADB devices on command prompt, it'show
View attachment 763802
and it's my driver after update from your link
View attachment 763803
what is passimg method, is the way rename room.zip => PASSIMG.zip

You did have debugging turn on correct?
Not sure what else to suggest except the passimg method, worth a shot.
Sent from my Transformer TF101 using Tapatalk

And... if you try to install a stock rom? When starts the HBOOT automatically detect the rom and ask to install. One time you've installed the rom, root & install recovery
I think that work because, It happens to me 1 week ago.

[Q] ADB command help

I am trying to get my bros captivate into download mode and his power button is broken. I tried doing this command:
Method 1: ADB - from recovery or normally booted with usb debugging on)
1.Open a cmd prompt/console/shell
2.adb shell
3.adb reboot download
but after i typed "prompt/console/shell" adb shell would not work?? It said it wasnt excutable batch...anyone here can help me figure out what Im doing wrong?Edit:FYI the phone was on debugging at at the home screen while trying this. The phone doesnt turn off and there is not app in the market that can turn off the phone without root. And since his power button is broken I cant ODIN root access( to use quick boot)
This is whats is happening:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>prompt/console/shell
/console/shell adb shell
'adb' is not recognized as an internal or external command,
operable program or batch file.
/console/shell adb reboot download
'adb' is not recognized as an internal or external command,
operable program or batch file.
/console/shell

You have to change directories to where adb is installed
Type cd c: (where you put have adb)
Then your adb commands
And console/shell/adb shell
Shouldn't be needed, once in the proper folder simply "adb reboot download" should do it.

adb doesn't have the ability to put the Captivate into DL mode. So even if you added ADB to your enviornmental variable, you won't be able to get it into DL mode..

b-eock said:
adb doesn't have the ability to put the Captivate into DL mode. So even if you added ADB to your enviornmental variable, you won't be able to get it into DL mode..
Click to expand...
Click to collapse
anyway i can get the phone into download mode, that you know of?

DL mode has nothing to do with the power button. DL is vol + and - and insert USB cable after ODIN is open and waiting.

b-eock said:
DL mode has nothing to do with the power button. DL is vol + and - and insert USB cable after ODIN is open and waiting.
Click to expand...
Click to collapse
I've tried that but it gets me into Recovery with the ! in the triangle..i look at ODIN and it doesnt reconize it. I have the samsung mobile drivers installed. Im using ODIN 1.82 should i use a diff version? The deivce cant be probely powered off either. Once i remover battery and place back in it turn straight on. That could be why its not going in download cuase it cant be powered off??

It looks like
Phone---/!\---PC
That is DL mode read these
-Flashing Guide
-New User Guide
-Captivate connection issues

b-eock said:
It looks like
Phone---/!\---PC
That is DL mode read these
-Flashing Guide
-New User Guide
-Captivate connection issues
Click to expand...
Click to collapse
No it says recovery and gives me the option of wipe data/factory reset, wipe cache, apply update. And in odin I dont have the yellow bar that says a device is connected.

well then you have a stuck power button, not broken. look for the Captivate tear down guide and do that then get compressed air and blow around the button... and try that

b-eock said:
well then you have a stuck power button, not broken. look for the Captivate tear down guide and do that then get compressed air and blow around the button... and try that
Click to expand...
Click to collapse
OH LORD !!!

b-eock said:
adb doesn't have the ability to put the Captivate into DL mode. So even if you added ADB to your enviornmental variable, you won't be able to get it into DL mode..
Click to expand...
Click to collapse
That is only true on aosp builds bro
On tw roms/kernels it works just as you would expect. Perfectly.

Then I learned something new, thanks never knew that. Maybe because I never stayed on stock for more than 10 mins.
And yes it works, thanks for catching me studacris

Reinstalling stock firmware?!?!

Ok I've been at this for hours trying to get adb to recognize the tablet in recovery mode and to no avail. I've tried every trick and random driver i can find on here and still am unable to get adb to recognize the tablet while waiting for a sideload .bin file. While in normal mode while up and running adb devices command find sit np but once it goes into recovery it's gone.
I type adb devices and it comes back null. I've tried killing and restarting the daemon server and that isn't it. I've tried uninstalling and reinstalling the drivers. There is even an ADB composite driver listed in the device manager and yet once the tablet is in recovery mode it seems to disappear.
I tried doing a factory reset and wiping the cache. i'm drawing a blank on this. I've also tried changing usb ports and cables on the computer. It's just not working.
Any ideas?

You may need to disable driver signature enforcement
then install drivers.
After that you may still need to follow this guide
http://forum.xda-developers.com/showpost.php?p=62561874&postcount=2
This was written for a different FIRE so yours will be KFFOWI instead of KFARWI in the guide.
I did this and in worked for me..

There are two options to restore stock at the bottom of this link, it all depends what version you have. See if it helps...
http://forum.xda-developers.com/showpost.php?p=62986666&postcount=4
or you could also try this to get into Amazon Custom recovery:
adb reboot recovery

Yeah, most likely a driver issue. Try different drivers until you find one that actually works!

Well I just thought of this when I woke up, could it be that I'm using minimal ADB and fastboot or should that not make a difference?

As long as your device is listed when doing a "adb devices" or "fastboot devices" should make no difference. But yes, minimal should be fine.
But it is usually a good idea to have the latest version.
I think your issue is with getting to Amazon recovery. If in recovery, there should be a menu. See that menu here in post #3:
http://forum.xda-developers.com/amazon-fire/general/amazon-fire-2015-tips-tricks-t3214544

Tuvan03 said:
Ok I've been at this for hours trying to get adb to recognize the tablet in recovery mode and to no avail. I've tried every trick and random driver i can find on here and still am unable to get adb to recognize the tablet while waiting for a sideload .bin file. While in normal mode while up and running adb devices command find sit np but once it goes into recovery it's gone.
Click to expand...
Click to collapse
You're talking 2 different modes here: (1) Recovery mode: You see menu options on tablet. Windows can't ever recognize device while in recovery mode; no driver appears in Win Device Manager. (2) Sideload mode: After you select "apply update from ADB" and press power button and you see yellow text on tablet saying to sideload the file. Fire appears in Device Manager. If no driver installed (or messed up), it's under "Other" with the name KFFOWI as @gray-beard said. That's what you need to install drivers for in order for sideload to work. I doubt Minimal adb is the problem. You're probably just not all the way into sideload mode. If problems persist, open the console window from the folder containing adb.exe.

gray-beard said:
You may need to disable driver signature enforcement
then install drivers.
After that you may still need to follow this guide
http://forum.xda-developers.com/showpost.php?p=62561874&postcount=2
This was written for a different FIRE so yours will be KFFOWI instead of KFARWI in the guide.
I did this and in worked for me..
Click to expand...
Click to collapse
Many Thanks Gray Beard, it's reloading the stock firmware now. I was just trying to go through the pick your device drivers thing too quickly and needed to do the see all devices to be able to see the adb drivers to get them loaded.
A pint of the finest dwarven ale to you (with a name like gray beard i couldn't resist)
EDIT: I did all this just to try to restore OTA updates, yet i hit the update button now that it's restored with the factory firmware and it's saying no updates found. hmm