Database Develop

nexus one Driver problem

Hey, i have had this problem for a bit now, but it is really starting to bug me.
I have a dual boot computer, one is fedora, the other windows 7. When i decided to root my nexus one, i did it through windows, so i got the SDK, installed the drivers and rooted the phone.
Some time later (after flashing and restoring from desire rom back to CM 5) my computer can no longer recognise the device properly Windows will say it fails to recognise the device (code 43), and will not let me re-install the drivers. Saying they are up to date even after i uninstall the drivers then re-install them.
I have given up on fedora too, since no command ever seems to work on fedora beyond yum install xxx. Trying to get "fastboot devices" in fedora brings up "command not found" or something to that effect.
I wouldn't be too worried, but not everything comes as an update.zip, and i would like to try out the undervolted kernel some time.
Note: i can still mount the SD card fine.
EDIT: i can Mount the SD on Fedora, but not windows.

Things you can try out:
1. Completely uninstall and remove the driver from the system and connect the phone and install the drive when prompted. (try in safe mode as well)
2. Try other USB ports.
3. Try turning off USB debug, connect the phone and then turn on USB debug.
4. Try on another PC and rule out any problem with ur phone.
5. Reinstall Windows!!!

Thanks for the suggestions, i tried everything there short of re-installing windows.
As soon as i plug in the device windows will bring up the error message, it will not call it a nexus one, an unknown device. Any attempt to install the new drivers and windows will say that better drivers are already installed.
I also figured out that it will not work on fedora because it is not configured, but the only guide to fastboot and linux i have found is for ubuntu, and some of the commands wont work on fedora.
I tried it on another computer, an XP, it would not install on there either, i tried to use my mums N1 afterwards to see if it would install, it didn't but there are a number of reasons why it may not.
Any other suggestions? or could someone point me to a fedora guide for fastboot?

Failed to Connect to Server

Keep getting this message in Command Prompt when trying to install CM9 on my touchpad.
Yes I have cd to the right directory in command prompt
Yes it does show up in Device manager as Palm Novacom (bootie) under the tab Palm Novacom Modules.
Yes drivers are installed
Yes I did re install all drivers after removing them.
Tried different USB cables
Will not show up in Adb either.
My computer does recognize it, in both WebOS Recovery mode, and in Mass storage mode.
What does this message mean? Am I missing something?
Appreciate any help.
Thank you.
Edit: Solved!
Thanks to Scifan on IRC for his help!

I've got the same exact issue... i have a feeling it has something to do with win 7 64bit, im seeing alot of people with the same issue with that setup.

Reinstall novacom using this this installer
http://universal-novacom-installer.googlecode.com/files/UniversalNovacomInstaller.jar
Than in your type this (services.msc) in your windows start bar. Look for Palm Novacom in the services.
If its not there, try installing novacom drivers again while looking at the services menu. It worked for me like that, not sure why. But this was my problem.
I had reinstalled novecom drivers a few times trying to get it to work, and that some how did the trick for me. Was pretty weird.
My net book is running windows 7 32bit. Dont know if 64bit is going to have problems as I cannot test.
Good luck!

[Q] One not detected properly in fastboot mode

Hi there,
I`ve got the following Problem:
My One is not detected properly in fastboot mode, adb works like a charm (all cmds working)
In fastboot mode windows says that the device cannot be started (code 10) and cmd cannot find the device and it`s also not charging in fastboot...
I`m using Windows 8 and I know that there are problems with driver signatures, so I disabled the checks through advanced boot, uninstalled all drivers and reinstalled them (the strange thing is, it worked like a charm with my HOX)
After that still the same issues... Then I uninnstalled the HTC drivers and tried the drivers from Google SDK and after that the drivers from PDAnet but nothing helped...
Then I read that there are Problems with USB3.0 and fastboot but I only got USB3.0. So I tried different USB ports and reconnected many times (about 30 times) and maybe the phone says "fastboot USB" but in cmd it`s still not detected...
As I said before with my HOX it worked like a charm... (also Win8 and USB3.0)
Any ideas?
Thanks for your help!
togx

Try disabling Fastboot in the Power Settings.

I tried it again with fastboot disabled but it still doesn`t work... :/

same problem here....

envoy_467 said:
same problem here....
Click to expand...
Click to collapse
hey envoy_467,
I found a solution for this issue:
It seems that microsoft´s own driver for the Intel USB3.0-Host breaks the support for several devices. You can install the Intel drivers for Win7 on Win8 (search google: Windows 8 and Intel USB3.0 host controller there should be a link to plugable. I´m not able to post links cause I don´t have enough posts...) but it only works with the Intel host.
Hope it will help you too!
greetz,
togx

usb device not recognized
I'm having a similar problem using windows 8, but I tried both my usb 2.0 and 3.0 ports but results in same problem. I have a t-mobile HTC One S (JB 4.1.1). Everytime I try to do the fastboot to get my token id my pc tells me my usb device is not recognized. Does anyone have any suggestions? Thanks in advance!

Try THIS

Sorry to bump this thread, but it's better than creating a new one.
Anyway, I have the same issue as the others here: fastboot won't work at all.
Btw, I've tried all possible solutions but installing the intel driver isn't possible due to a limitation on Windows + Intel 8 Series.
Windows 8, Intel 4th generation processor (8 Series/220) on a Gigabyte GA-Z87N-WIFI.
USB eXtensible Host Controller driver by Microsoft can't be modified to work with the Intel 8 Series driver. When trying to install it it says that my PC doesn't have the requirements to install the program (driver can be found here -- 8 Series ONLY!!) probably because I'm on Windows 8 (no, setting the app to run with Win7 compatibility mode doesn't work either).
Using Naked Driver 0.72..
Has anyone tried with a virtual machine? Maybe I could install Ubuntu on a VM to test it when I get the time.
Any other ideas?

VM doesn't work.. Since Windows won't recognize the phone while on fastboot that means that the VM Linux won't find the devide either.
LiveUSB won't install the android SDK either.. I'm stuck..

FIXED, kinda.. Workaround on Linux.
More info:
Just did it..
But not on Windows..
I've created a LiveUSB from Ubuntu 12.04 using the "Universal USB Installer" from: http://www.pendrivelinux.com/downloads/
When creating the LiveUSB I've created with 4gb (4096mb) of free space on a 16gb flash drive just in case, but you can make it work with a 4gb flash drive.
Then I installed the Android SDK.
Then I was able to use fastboot to change the CID to 11111111.. Working great.. Now let's download the developer ruu..
Tutorial used to install the SDK: http://askubuntu.com/questions/318246/complete-installation-guide-for-android-sdk-on-ubuntu
To run all commands faster, just type "sudo su" before starting. After that type "apt-get -f install" to clean everything.
Remember: To install anything the tutorial asks you have to use the command "apt-get install name-of-package", where the name is the item the tutorial says.
Go up to Step 4.
Download and Unzip/extract the AndroidSDK to the desktop (just the SDK, you don't need the full bundle).
Go to the unzipped folder, go to the Tools folder, double click "android", run in terminal, install the SDK and the TOOLS.
When finished, open a terminal window, navigate to your unzipped folder, than navigate to platform-tools and use the command "./adb" and "./fastboot" to work your magic..
Edit: Still not able to install the RUU..
At least now I have the phone ready.. Just have to find a new PC to install the RUU..

No OS on phone! OTG USB / conncetion to PC not recgonized! Seeking Help

In the past 3 months or so I noticed that my Mi5 3GB 32GB is not recognized by my PC anymore. I didn't care too much because I hardly connect my phone to PC.
I was running the lastest xiaomi.eu Rom unrooted.
So on Thursday, I deleted my OS by mistake, therefore I do not get past the Mi Logo.
I can boot into TWRP Recovery & Fastboot however, there is not code when using CMD adb/fastboot devices such as 1cwe3f23.
Also, I read about the EOL method aka test point method, to force a connection as Qualcomm driver with no success. Different PCS dont recognize any drivers.
The battery is not an issue because I can easily charge my phone to 100% and it can hold its charge, therefore I do not think it is a battery related issue.
What i did so far :
- used 3 differenct USB C cables and PC -> phone still not recognized
- Installed all lastest driver on Drivers -> phone still not recognized
- tried to use the test points method -> phone still not recognized
- tried Miflash tool -> phone is still not recognized
- tried Mi PC Guide -> didn't work either
Then I read somewhere that I can use a OTG cable with a pen drive
- OTG storage is not recognized in TWRP recovery and cannot be selected. [OTG STORAGE 0MB even if different pen drives are connected]
SO my Main problem is not the phone itself, it is that I cannot get any data onto the internal memory because I can't get past TWRP.
Please help me out since I really struggling with this problem for the past 7 days and I'm desperate now for any kind of help.
Greetings and thanks in advance.

amando1991 said:
SO my Main problem is not the phone itself, it is that I cannot get any data onto the internal memory because I can't get past TWRP.
Click to expand...
Click to collapse
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.

Hi bro
same as me, 4 days ago...
system, vendor error
flashing stock rom miui9 via twrp
although the error twrap will only provoke usb computer,
if it works usb computer, try flashing by using miflash...
goodluck
Sory bad englis

moo113 said:
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Click to expand...
Click to collapse
I did as you recommended and used Ubuntu. However also there the system didn't recognize the phone when plugged. It may because I am not fully familiar with Ubuntu. I would appreciate if you could point me in the direction of a tutorial.
same as me, 4 days ago...
system, vendor error
flashing stock rom miui9 via twrp
although the error twrap will only provoke usb computer,
if it works usb computer, try flashing by using miflash...
Click to expand...
Click to collapse
could you be more precise please? How did you overcome not having a PC conncetion?
Currently, I am not able to transfer any kind of data to the phone either by PC or OTG. Furthermore, the internal storage is completely empty after wiping everything by mistake.
I have twrp working fine, but without any data on the device, I cannot use it. Also, the device only stays in fastboot for roughly 20 secs before it turns off.
any help is welcomed. Thank you
EDIT : I got Ubuntu to work but its the same process. My phone is not recognized and running the command adb devices gives me
"list of devices" .... thats not! Nothing ! usally there is the code Phones ID but nothing there

amando1991 said:
EDIT : I got Ubuntu to work but its the same process. My phone is not recognized and running the command adb devices gives me
"list of devices" .... thats not! Nothing ! usally there is the code Phones ID but nothing there
Click to expand...
Click to collapse
A number of different issues could be here.
#1 Firstly, ensure you've installed openvm tools and reboot. This should enable things like hardware pass through.
$ apt-get install open-vm-tools open-vm-tools-desktop
$ sudo init 6
Then, follow these instructions for the pass through (may be slightly different, but very similar) https://forum.xda-developers.com/showthread.php?t=570452
#2 Type "adb" and see what version is in use in the first line of output. If it's 1.0.0.32 or older, it might be an issue. Try installing the following packages:
$ sudo apt-get install android-tools-fastboot android-tools-adb
You might need to find a newer version elsewhere, Ubuntu repos are often old. Google around for 1.0.36 or newer. This could solve your issue.
#3 Ensure you have the necessary rules for the Mi 5. There's a few different hardware models. The Arch Wiki can walk you through it better than I can: https://wiki.archlinux.org/index.php/android#Connect_device (ignore the package hyperlinks, they're arch-specific). Only do this if you've properly configured the pass through from #1. Do F"igure out device IDs" and then "Adding udev Rules". Instead of the "udevadm" command run
$ sudo service udev restart
If you're still not detected, no idea.

moo113 said:
A number of different issues could be here.
#1 Firstly, ensure you've installed openvm tools and reboot. This should enable things like hardware pass through.
$ apt-get install open-vm-tools open-vm-tools-desktop
$ sudo init 6
Then, follow these instructions for the pass through (may be slightly different, but very similar) https://forum.xda-developers.com/showthread.php?t=570452
#2 Type "adb" and see what version is in use in the first line of output. If it's 1.0.0.32 or older, it might be an issue. Try installing the following packages:
$ sudo apt-get install android-tools-fastboot android-tools-adb
You might need to find a newer version elsewhere, Ubuntu repos are often old. Google around for 1.0.36 or newer. This could solve your issue.
#3 Ensure you have the necessary rules for the Mi 5. There's a few different hardware models. The Arch Wiki can walk you through it better than I can: https://wiki.archlinux.org/index.php/android#Connect_device (ignore the package hyperlinks, they're arch-specific). Only do this if you've properly configured the pass through from #1. Do F"igure out device IDs" and then "Adding udev Rules". Instead of the "udevadm" command run
$ sudo service udev restart
If you're still not detected, no idea.
Click to expand...
Click to collapse
Thank you again for the help!
Unfortunately, it appears that my device is still not recognized by either Ubuntu or Win10.
I Have taken the necessary steps to install Ubuntu and update the adb drivers (1.0.39) but still no luck so far.
It really pisses me off since I was stupid enough to wipe the internal storage ☹ and not I am not able to transfer any data to the devices again.
Any other out of the box ideas?

amando1991 said:
Thank you again for the help!
Unfortunately, it appears that my device is still not recognized by either Ubuntu or Win10.
I Have taken the necessary steps to install Ubuntu and update the adb drivers (1.0.39) but still no luck so far.
It really pisses me off since I was stupid enough to wipe the internal storage ☹ and not I am not able to transfer any data to the devices again.
Any other out of the box ideas?
Click to expand...
Click to collapse
You configured the USB pass through to your Ubuntu host? Double check you followed #3, and then run sudo fastboot devices. That step is tricky for some.
Reconnect your phone to your Ubuntu host (in fastboot) and run "dmesg -T", see what errors are present. If you have no errors, I would image it's a configuration issue. Other than that I'm out of ideas.

moo113 said:
You configured the USB pass through to your Ubuntu host? Double check you followed #3, and then run sudo fastboot devices. That step is tricky for some.
Reconnect your phone to your Ubuntu host (in fastboot) and run "dmesg -T", see what errors are present. If you have no errors, I would image it's a configuration issue. Other than that I'm out of ideas.
Click to expand...
Click to collapse
OMFG!!! First of all, thank you for support and your patience. I really appreciate it.
HOWEVER, all it was is that the USB PORT was full of dust( literally tons!) which appears to have allowed to charge the phone but seemed to have cloaked up some part of the responsibile for a usb connection to a computer.
Stupid me should have known this because the usb port was kinda wobbly which I had mistaken for degradation using the phone for almost 2 years
MANY THANKS!

moo113 said:
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Click to expand...
Click to collapse
Hey , I was researching about my issue and came up to this. I'd be really glad if you can sort me out with this. I have the same mobile , by mistakenly wiped out the phone including the internal storage , my pc does not detect the device , and whenever i go to fastboot mode to try something like miflash , it goes back to twrp after 15 seconds. Also , i tried several OTG's but none of them get detected on TWRP , and I am stuck on this thing for almost a week now . Please guide me on how to sort this out . i basically just downloaded adb files , miflash , etc from the internet and never reinstalled them. also i used several usb c cables to connect to pc and even then device manager does not detect it . thank you . i would really appreciate your reply.

Can't use fastboot

To clarify, my problem is that on my windows 11 laptop my phone is not recognized in fastboot. When I try to run any commands i get "<waiting for device>" and in device manager it is listed as "Android" with a yellow triangle near it because windows says it is an unknown device. I even installed all the drivers i could but still no luck. It works on my ubuntu laptop so I don't know why it wouldn't work on my windows laptop.

Ah yes, welcome to Windows Driver Hell. You see, while you think your drivers are installed, Windows has a different opinion
Try finding the directory of the driver and install it manually in device manager. If this works there is a chance you'll even have to do it every goddamn time. Has happended before.
If you're using a device specific driver you can try Universal Drivers instead. And vice versa if you're on universal drivers now.
Sometimes I have luck with a Nexus driver.

Thanks for your help, it finally worked with the qualcomm driver I found in the msm tool post