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.

[Q] Want to install recovery image

Hi guys,
I am trying over 4 hours to flash a recovery image on my gt540.
I have installed a fastboot rom via kdz updater.
Then I turn on the device in fastboot mode to install the recovery using command prompt but in this stage my pc does not recognize the phone. It says "waiting for device".
I have tried every driver I found, but I cannot make it work.
I am running windows 7 x64.
Can anybody help me? I am confused, I don't know what to do.

hmm looks like you dont have the drivers installed. im also using windows 7 x64. i got my drivers by plunging in the phone and waiting for the computer to recognize it and install the drivers from windows update. You can try rebooting the PC then change USB ports. Give each port at most 5 mins to try recognize the phone if it fails then change ports sooner or later the computer will get the drivers
the driver for fastboot is called googlee fastboot interface or something liek that, maybe you can try these http://dottech.org/android/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/

Man you are great! I was searching all day for this!
Thank you very very much!! I managed to flash a good rom!
Thanks again!

USB device not recognized

Hello. i noticed that my computer(win 8.1) was giving a usb device not recognized error a few days ago. i didn't fix and eagerly updated to android 4.4.3, but forgot to disable freedom and now can't use google play services. i can fix that but the DAMN PHONE STILL ISN'T RECOGNIZABLE BY THE DAMN COMPUTER. i have tried multiple cables and installed win 8 dual boot but still got the same error. i also tried to reinstall drivers. but i think i didnot do it right.
both adb and fastboot are not working. if u could tell me a method to install a custom recovery without root and adb that would sove half my problems but still need help getting the computer to recognized the phone.

Normally this is a problem with charging block of the phone.
You have to root to flash recovery without a computer, towelroot works on 4.4.3. Once rooted you can use goomanager app to flash twrp recovery.

Does the PC making sound of connected I disconnected continually?

Huge mistake

Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..

Pedrau said:
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Click to expand...
Click to collapse
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?

zaclimon said:
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
Click to expand...
Click to collapse
Yes I can acces to bootloader and TRWP. Tried another USB port, another USB cable, using manual commands it says " <waiting for device>" and nothing happen..

What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.

venu123 said:
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
Click to expand...
Click to collapse
Thanks buddy , but my drivers were fine before all this. And now i can't reinstall it that way since my nexus isn't even showing up on device manager, I used another method from NRT. Gonna test on w7..
EDIT: Problem solved using windows 7. There seems to have problem with drivers on windows 8.1

Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.

venu123 said:
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
Click to expand...
Click to collapse
I didn't have to on Windows 8.1.

[Q] G2 Soft bricked no ROM on Internal Memory

SOLVED!
Hello All.. I have searching for hours not making much progress. Last night my LG G2 ran out of battery and I plugged it into the car charger and it soft bricked. I've been pretty busy lately so I'm on an old ROM Optimus DE 2.2. I don't have the ROM saved and I've been trying to ADB sideload the ROM back onto my phone but in the command prompt it says device not found. I tried installing some generic drivers and that didn't work. I tried the LGUnitedMobileDriver and that isn't working either.
I'm not sure what to do next. I have ADB on my computer and ADB sideload on my TWRP recovery, so I would like to push the ROM on my phone so I can flash it without having to wipe my phone. What drivers do I need; right now my phone shows up under other devices in device manager. Or am I sideloading wrong? Any help please lol..
I was caught off guard because of the random soft brick. If I would have been working on my phone I would have had the proper backups made. Thanks for any help, it is much needed I need my phone back ASAP!! Thanks again.
SOLVED
Finally figured it out. I had to updated my device (LG G2) with the ADB drivers not the LG drivers.
I went into Device Manager, right clicked my phone, clicked update driver software, clicked browse my computer, clicked let me pick from a list of drivers, then selected ADB drivers, then selected HTC Dream Composite ADB Interface. I believe the drivers I last installed were Snoop05's adb-setup-1.4.2.
Then I did a backup in TWRP, then I sideloaded the ROM. Next I had to wipe everything but internal memory and the use Nandroid Manager to restore my data from the backup... Took my whole day but at least I have a phone again.

The car charger soft bricked it ?
So you have TWRP, the drivers you can get from the LG site too. Just search for your model and go to software update section. This is for D802, i dont know if the drivers are the same: http://www.lg.com/uk/support-mobile/lg-D802
Hmm..i dont know how to use the sideload..
Another way can be with USB flash drive and OTG cable, i used my usb flash drive with OTG cable to flash ROMs from TWRP

Last option is lg flash tool and then reroot

Thanks for your help guys.. I appreciate it! Looks like I just needed to update my phone with the ADB drivers in Windows 8 Device Manager. I'm back up and running.
But yea so weird.. I haven't flashed anything on this phone in months so I guess something was corrupted when it died. I think it was trying to boot with too low of a charge and the battery died mid boot which corrupted something.

Although you've solved it let me recommend you another way.
Use : "adb push romname.zip /sdcard/romname.zip"
instead of "adb sideload romname.zip"