Database Users

N1 Windows Drivers problems

Hello,
After few months with my n1, finally I decide to root and put some roms.
Even when I already have done with my magic, tatoo, and hero, I can´t handle the driver problems in my nexus one.
I could unlock the bootloader. My problems came after this step.
Ive tested few things, but I will put my last experience.
In a just-formatted windows XP sp3, I downloaded the last android SDK and Ive downloaded the usb driver (R3).
After this, I connect my nexus one phone and it asked me for the drivers, I gave the path and it was successfully installed.
I unplugged the USB cable, turn the phone off and restart in debug mode, bootlader. Plug the cable, my PC reconigzed "something", and install some driver. "Unknowledge device". So, I tried to update the driver, giving the path to the USB-driver folder (inside of android-sdk-windows folder). And nothing. It tells me that there is not a better driver for my device. And I can´t connect to my phone. Of course Ive tried uninstalling the driver and nothing. (always from control panel).
I dont know what to do. Please, give me some suggestion because im totally frustrated.
Thank you

http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/Posted Yesterday, 10:17 PM
ATT N1's can run CyanogenMod without any real trouble. The commands and guides remain the same as the Tmo N1
THE ONLY CAVEAT IS: YOU CANNOT USE CM 5.0.5.1 or 5.0.5.2 as your initial install base, as these releases were bugged. Use 5.0.5 here
For Nexus' you DO NOT NEED SUPERBOOT and steps are super easy.
Setup ADB/FASTBOOT
Fastboot oem unlock
fastboot flash recovery recovery-ra-blah-blah.img
Reboot into recovery
NANDROID
WIPE!!!! (if you dont wipe you get boot loops)
Flash CM
Flash Google (optional)
Reboot
Fastboot flash radio radio.img (unnecessary on ATT n1's)

cheloman said:
Hello,
After few months with my n1, finally I decide to root and put some roms.
Even when I already have done with my magic, tatoo, and hero, I can´t handle the driver problems in my nexus one.
I could unlock the bootloader. My problems came after this step.
Ive tested few things, but I will put my last experience.
In a just-formatted windows XP sp3, I downloaded the last android SDK and Ive downloaded the usb driver (R3).
After this, I connect my nexus one phone and it asked me for the drivers, I gave the path and it was successfully installed.
I unplugged the USB cable, turn the phone off and restart in debug mode, bootlader. Plug the cable, my PC reconigzed "something", and install some driver. "Unknowledge device". So, I tried to update the driver, giving the path to the USB-driver folder (inside of android-sdk-windows folder). And nothing. It tells me that there is not a better driver for my device. And I can´t connect to my phone. Of course Ive tried uninstalling the driver and nothing. (always from control panel).
I dont know what to do. Please, give me some suggestion because im totally frustrated.
Thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=613217
Try those drivers.

jerrycycle said:
...For Nexus' you DO NOT NEED SUPERBOOT and steps are super easy.
Click to expand...
Click to collapse
jerrycycle said:
fastboot flash recovery recovery-ra-blah-blah.img
Click to expand...
Click to collapse
Thank you by your post, it was very usefull and I could change my drivers, so I have access in debug mode to my n1. Even with this, Ive tried to apply the root with modaco´s files, using the original ERE27 pack, but, it just stucks in "copying...".
Maybe the problem is that I was instructed about I should execute the .bat, in bootloader moder (no in fastboot). I have the adb commands with fastboot mode, but, when I do: fastboot devices in bootloader mode, I dont have any device. Maybe the tutorial that I followed its wrong and should I execute directly in fastboot not in bootloader.
Anyway, Ive quoted your post, because when you say that isnt necessary, the instructions of recovery installation, says about its a "pre-requirement"
You can check it in /showthread.php?t=611829 As new user, i cant put the link to the thread of RA recovery, sorry
I dont want to mess with this, because the consequence of bad procedure.
Thank you by your help and patience.

you might want to make sure you're using the main USB ports, not those extension ones or those that are built into PC cases. I used to have the problem with "unrecognised device" because of that.

windows driver in recovery mode

possibly silly question, seeing everyone is saying the rooting problem is something different(drivers(htc/pdanet/android sdk), sdcard, computer(OS)). you guys that have gotten ADB to successfully get the phone recognized in recovery mode:
Did the phone show up in the device manager for windows?
i feel like windows has to register the phone under a certain driver in order for ADB to pick it up(otherwise the OS doesn't recognize it like any other piece of hardware). maybe part of the problem is some people don't have a recovery driver?
just throwing it out there since I have tried every method on the forum except using the original sdcard that came with the phone(it's my my gf's phone at the moment and i haven't been able to get it from her)
also, does anyone know what eugene's setup is? OS, drivers, sdk version? or eugene if you see this, it would be wonderful if you could chime in.

Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...

chrisinaz said:
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
Click to expand...
Click to collapse
What OS are you using? 32 or 64 bit? Do you have HTC Sync installed?

i've used winxp pro 32bit, win7 pro 64bit, win7 ultimate 64bit. i tried the htc drivers, the pdanet drivers and the sdk drivers. i just made a ubuntu boot drive, i think im going to try that later tonight.
and i think chrisinaz is trying to root his friends phone on the same computer he did his on if i'm not mistaken.

Using xp 32 bit and fedora 13. Neither work for his, both work for mine.
-------------------------------------
Sent via the XDA Tapatalk App

chrisinaz said:
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
Click to expand...
Click to collapse
Where it says android 1.0 this is the driver that you need to update. I used the PDANet driver to update it.

[Q] Device doesn't show up in adb

Ok, I'm having a problem here. I'm buzy on a ROM, and I have made something that I want to test. But when I try to access my phone via adb, it doesn't show up in adb devices. Just nothing. I reïnstalled adb, the drivers, rebooted the phone and computer, put on debugging mode, everything. The phone is showing in (windows) devices, but adb just don't recognize him. I'm on Windows 7 Home Premium. And on my phone Swiftdroid M5 (with ClockworkMod Recovery 3.2.0.1, which is working properly). Anyone knows what to do?

Anyone?
Sent from my GT540 using Tapatalk

Heres my solution ^^ adb worked for me some weeks ago but now i had your problem too lol:
first uninstall all the adb drivers from:
Start>devicemanager
then get this :
http://www.junefabrics.com/bin2/LGDriver.exe
original LG drivers
and install
then plug your phone(debugging on of course)
then it will show 7 (i think) installations
5 of them will be done fast but 2 won't finish installation
so just go to devices and printer
rightclick on android sooner single adb interface and select troubleshooting( marked with a yellow triangle)
then just let is solve the error
the last of the 7 drivers wont install but thats not a problem
EDIT: make sure u know on which port u were doing this

Oh of course you should reinstall the adb drivers. Btw i'm in linux you can use linux for building rom. What are you using?

Sadronis said:
Oh of course you should reinstall the adb drivers. Btw i'm in linux you can use linux for building rom. What are you using?
Click to expand...
Click to collapse
Windows 7 + Ubuntu 11.10
Sent from my GT540 using Tapatalk

is fastboot working now ?. and installed properly in device manager.

regisol said:
is fastboot working now ?. and installed properly in device manager.
Click to expand...
Click to collapse
Wrong topic
Sent from my GT540 using Tapatalk

Hello, I tried all of the above but my device still doesn't get recognized. Is there any other way to fix this? Thanks.

I've been in the same situation like this before. My phone wasn't recognized by adb. I though it was a driver problem so I reinstall the driver million times but it doesn't help. I tried on many other computer with various OS as well but adb still can't recoginized it. At last I flash another ROM and adb can recognized my phone again. so the problem is the SDSL ROM

I see. Thanks for the info ^_^

[Q] Device Manager Error 43 + No ROM installed

I'm having one heck of a problem here. So I've got my Nexus 7, on stock Android, but rooted and unlocked.
I wanted to try Paranoid Android, so I installed the TeamWin Recovery using the Nexus Root Toolkit, then flashed the ROM and wiped cache/dalvik. I tried to boot into the new ROM, but it just stayed on the boot animation. So I looked up the issue, and the solution seemed to be return to stock Android, then flash Paranoid Android again.
So I tried to use the 'Flash Stock and unroot functionality' of the Nexus Root Toolkit, which proceeded fine until the copying of 'system' onto the device... This lasted for about an hour without progress, so I decided to try again with a different version of stock Android. This too didn't work.
So then I (foolishly) rebooted the tablet. But when I got back to fast boot, it didn't show up in Windows (on either of the two machines I have here, and with two cables that have both worked previously, in multiple USB ports). The specific error is that it shows up as an unknown device (which is fine) but also in the device manager there is error 43, which states that the USB has malfunctioned so it has stopped.
For that reason, it's impossible for me to connect it to a computer or even re(install) the proper drivers for it. And as it doesn't have a working OS, i can't get to ADB either. So right now I can't think of anything that will work - no fast boot, no recovery, no connection to a PC.
Any ideas?

Really, no ideas? Come on XDA Developers, you're my only hope <3

Hi there!
ive got the same issue and i can tell what is NOT working to fix this problem:
deleting ALL usb drivers from pc and installing adb drivers, windows troubleshoot and nrt
i'm just like confused but i think it's all windows fault, if i could i would trie on linux or any other pc os

Fastboot trouble windows 8 x64

Hi guys,
I want to go back to stock since 4.4 is coming. However, when I try to flash the stock rom+ with Nexus Root Toolkit 1.7.3, I get stuck at the whole fastboot part. Fastboot IS working on my Nexus, but the drivers cause a lot of trouble. Installing the drivers when my device is running normally ( so no fastboot mode or whatsoever) works fine.
I have followed the Full driver installation guide where I tried options 1 till 4 but they all get stuck at the point where my device reboots into fastboot mode. At this point, my computer doesn't recognize my device and gives me an error. My nexus is shown in the device manager as unknown device and updating the drivers manually by redirecting my computer to the NRT drivers does not work. It says it cannot find drivers for the device. Does anyone know what I might have done wrong?
Or is it possible to flash a stock rom through twrp? like this one? http://forum.xda-developers.com/showthread.php?t=2376881

TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.

issak42 said:
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
Click to expand...
Click to collapse
Yeah, I tried the same things you did, including disabling driver signature verification but it won't work. I'll try a windows 7 machine.
Thanks for your answer!