Related
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.
Hi people
I've been trying to unlock the bootloader to root my nexus s 2.3.3 for 2 days now and have tried everything i can find in all the related threads but my computer wont see the phone when in fastboot mode.
Im getting really fed up as i do not know what to try next.
Anyone had this problem before?
Any help would be much appreciated.
Jon
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Andrew421 said:
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Click to expand...
Click to collapse
Yeah I've tried that too but computer does'nt see the phone in fastboot mode so i cannot update the drivers at all.
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
kenvan19 said:
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
Click to expand...
Click to collapse
Hi, when i put the phone in fastboot mode the computer doesnt see the phone in device manager but it does see it when not in fastboot mode. Im running windows 7 64.
Hey man, I had the same issues. It took me a total of 12 hours to root my phone and I tried everything . I was stuck trying to unlock the bootloader for hours. The problem for me was that the driver couldnt be found. I tried the pda net and it kept saying that the drivers were installed. Assuming your using windows, go to devices with the phone plugged in and you should see the device named something different with a yellow exclamation mark..... right click and hit update driver software. Then find the file pdanet and point it to update with that file. If this doesnt work, theres a file in there I believe its called android_usb or android_winusb and you push "have disk" and force install from that file . then it should see your phone. this was the only way i could get it to work was by pushing have disk and pointing it at the actual android 1.0 driver becuase the google usb package didnt have it (at least at the time). Im new to the forum, so bare with me if my directions aren't too great, just thought I'de try to help you out bc it was so frustrating!. Also, here is a good link in the xda forums for you to check out http://forum.xda-developers.com/showthread.php?t=875580
also,,,are you getting the "waiting for device" message when you type fastboot oem unlock? these instructions are for if you are experiencing that... Its basically not found becuase there is an android 1.0 driver that you have to force to update. good luck!
Thanks for the replies am now downloading the sdk onto the wifes laptop as hers is win 7 32 so hope there is less issues. fingers crossed.
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
mattdub1 said:
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
Click to expand...
Click to collapse
Have the same drivers installed but computer still doesn't see the phone when in fastboot mode. It worked perfectly on win7 32 on other laptop and I managed to root. still trying to get it to work on win7 64 as this is my main OS.
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
also, you did make sure to dowload the google usb package and get the right sdk version correct? I cant see any other reason that the phone wouldn't be recognized. I also believe you need usb debugging on
http://forum.xda-developers.com/showthread.php?t=878786 check out this post... VERY good guide and this is what helped me on the 64 bit 7. it sounds like your missing the fastboot driver which allows the computer to see the device in fastboot mode
mattdub1 said:
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
Click to expand...
Click to collapse
On win7 32 it was really easy once all the necessary programs and files were downloaded I first connected the phone switched on in normal mode with USB debug on and installed the drivers. Once in fastboot mode the path for the drivers was already there from the previous driver install I just selected the bootloader driver and the rest is history
Sent from my Nexus S using XDA Premium App
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
mattdub1 said:
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
Click to expand...
Click to collapse
it was the google usb drivers when i went update drivers on my system the path is
C:\android\android-sdk\extras\google\usb_driver.
Then go to option 'let me pick from a list of drivers on my computer' Which brings up three options:
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
Choose the Android Bootloader Interface hit next and yes to install.
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
noj78 said:
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
Click to expand...
Click to collapse
If you can see the phone in fastboot what else do you need?
deleted!!!!!!!!!!
I can see it in fastboot mode but not in device manager where it should be.
I can only see it in devices and printers where there are no driver options.
Okay, so put it in fastboot mode and try to run a fastboot devices real quick.
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.
Ok so I think I've searched well enough to conclude no one has my particular problem. When I plug in my A500 into my computer that has windows 7 windows recognizes that something was plugged in but not what it is. It says USB device not recognized, unknown device, and so on. I've tried installing the drivers from the acer website, I've tried installing the drivers from the link in the ics rooting thread, I've tried using the google android drivers and none have worked. I've even tried reinstalling windows but that had nothing to do with this it was a different thing that made me do it. Nothing has worked and I've become a bit frustrated with the tablet. Any suggestions on what to do?
Thanks
SolomonAiel said:
Ok so I think I've searched well enough to conclude no one has my particular problem. When I plug in my A500 into my computer that has windows 7 windows recognizes that something was plugged in but not what it is. It says USB device not recognized, unknown device, and so on. I've tried installing the drivers from the acer website, I've tried installing the drivers from the link in the ics rooting thread, I've tried using the google android drivers and none have worked. I've even tried reinstalling windows but that had nothing to do with this it was a different thing that made me do it. Nothing has worked and I've become a bit frustrated with the tablet. Any suggestions on what to do?
Thanks
Click to expand...
Click to collapse
What state are you connecting it in (recovery, fastboot, normal boot)?
Moborobo test program
Sorry forgot to say, it's stock rom not rooted and is being connected in normal boot.
SolomonAiel said:
Sorry forgot to say, it's stock rom not rooted and is being connected in normal boot.
Click to expand...
Click to collapse
tick the usb debugging
and that is on. Forgot to mention that as well. I forget about details quite often when i'm explaining something.
SolomonAiel said:
and that is on. Forgot to mention that as well. I forget about details quite often when i'm explaining something.
Click to expand...
Click to collapse
Moborobo, download the program and try it. Ami has worked with me many android devices
---------- Post added at 06:30 PM ---------- Previous post was at 06:26 PM ----------
Moborobo, download the program and try it. to me has run many android devices. sorry for my English
Your computer isn't detecting it at all, or is there an error while trying to identify it? Make sure you have the proper drivers for your device on your computer.
It's an error identifying it. I do have the correct drivers the a500 drivers from either the rooting guide or the Acer website neither has worked.
Moborobo does not work with the a500. I tried it and it still says to connect my device. which it is but it's just unrecognized.
If you have installed the driver correctly, AND you had administrator rights when you installed, should be no reason why you can't get the PC to recognize the device.
First, I would advise using a good USB cable. It's been known in the past, that some folks try to use a printer cable, and sometimes it doesn't work. If changing cables doesn't work, then do the following
1. In Device Manager, try loading the drivers manually. You should be able to have it search the windows system for the drivers. If it doesn't find it, then windows is being stupid. Try installing it manually (ignore the warning it may not be compatible,.....)
2. If that doesn't work, then you can use the Google USB drivers
http://www.redmondpie.com/android-u...r-samsung-htc-asus-sony-lg-and-other-devices/
Generally, we install the Android SDK first;
http://developer.android.com/sdk/index.html
And again, have Device manager look to that directory and manually select.
Either way, this should get you up and running.
And one more thing, turn on USB Debugging in your tablet's system properties.
MD
I've tried that. Didn't seem to work as windows would still not recognize the a500. And the usb debugging has been on since the beginning.
Okay i've gotten windows to the point of being able to install the drivers from the device manager but there is no clear option to choose. Here are the choices:
acer android communications port
acer android modem
acer hs-usb android diag
acer hs-usb diagnostics
acer composite adb interface
acer fastboot interface
acer picasso usb boot-recovery driver (google driver)
android bootloader interface (google driver)
So any suggestions cause I've tried installing the adb interface, fastboot interface and the android bootloader interface and haven't gotten any good results.
Thanks
Did you try a second PC? Sometimes a machine can get wonky if you've been using for years. Using a second machine or reinstalling Windows freshly would greatly increase the chances of detection.
Yep tried about 3 machines.
SolomonAiel said:
Yep tried about 3 machines.
Click to expand...
Click to collapse
I'm having the same issue with a bricked A500 I bought on ebay
Windows just recognizes it as an MTP USB device and fails to install the drivers
I have another A500 that comes up fine as an A500 on the same PC.
Try disabling the USB debugging in developer options I have the same issue with my Win 7 x64 system
I had a rooted 4.3 stock image on my N10. Got the notification about the downloaded update for 4.4
It did the update through TWRP (which was weird to me) and finished, restarts and gets stuck on the boot loading screen.
So I went into recovery, and cleared cache, no luck, then complete factory reset, no luck, then I added "System" to that wipe, not knowing what it was an now there is no OS installed.
I installed the Nexus 10 Toolkit (Unified Toolkit) and install the USB drivers, but my computer is not seeing my device..
Help?
As long as you can get to the bootloader, you can reflash a stock image. Easiest way is with wugfresh nexus root toolkit. It will walk you through the driver installation and the various image downloads.
That did not work.
The computer is not seeing my device. Drivers are installed, not seeing it, it's in the proper Boot mode.
I followed the mode that said I didn't need debugging enabled, still nothing.
bmancell said:
I followed the mode that said I didn't need debugging enabled, still nothing.
Click to expand...
Click to collapse
I would recommend uninstalling the USB drivers you installed with the toolkit and manually installing the Google USB drivers attached to this post. After you have installed the USB drivers I would recommend manually booting into your devices bootloader by simultaneously holding down the power button + volume up button + volume down button. Once you are in bootloader mode I would recommend download this Android 4.4 KitKat Factory Image and flashing it to your device in order to restore things to a working order. Let me know if you still have questions I'll be happy to help you out.
And want explain to me how I copy that file to my device when the computer can't see it?
bmancell said:
And want explain to me how I copy that file to my device when the computer can't see it?
Click to expand...
Click to collapse
Check out my previous post and see if those steps will allow your computer to see your device, and let me know how that goes for you.
Ok, I unziped the folder, got the tablet in bootloader mode, which I already said I tried, nothing.
Weird thing, I plugged the tablet into my other computer, it makes the noise for Windows 8.1 that you hear when you plug a USB device in, but there is no notifcation, nothing in device manager, nothing. Just the sound .
bmancell said:
Weird thing, I plugged the tablet into my other computer, it makes the noise for Windows 8.1 that you hear when you plug a USB device in, but there is no notification, nothing in device manager, nothing. Just the sound .
Click to expand...
Click to collapse
I just want to re-state everything to make sure anyone can understand.
This was a Nexus 10 rooted 4.3 Stock. I got the 4.4 update, it finished without issues, but got the boot loop issue.
I cleared cache, factory reset and eventually the system without luck, which left the tablet without an OS (bootloader or recovery only options).
My systems can not detect the tablet, I have installed, re-installed, tried two different toolkits and no luck.
I can't believe it's an actual brick that can't be fixed? Anyone?
Its definitely NOT your tablet. I had similar issues when rooting a Kindle and it was an issue with the PC's USB drivers. If you search the forums for USB / ADB drivers you will find a detailed discussion on how to delete existing drivers (its a process) and update new drivers.
sojthumper said:
Its definitely NOT your tablet. I had similar issues when rooting a Kindle and it was an issue with the PC's USB drivers. If you search the forums for USB / ADB drivers you will find a detailed discussion on how to delete existing drivers (its a process) and update new drivers.
Click to expand...
Click to collapse
Did you read? I have installed/reinstalled the drivers 3 times.
bmancell said:
Did you read? I have installed/reinstalled the drivers 3 times.
Click to expand...
Click to collapse
I also tried a third computer, and another cable. It will charge from a computer, nothing else.
I went through the same experience; it *was* the drivers. If you're using the wugfresh toolkit, it gives at least three options for driver installation. In my case only the drivers from pdanet worked. I've had similar issues in the past with my N7; in that case only the pdanet drivers worked on one computer, and only the Koush drivers worked on a different computer -- both Win 7 by the way; I have no idea why.
I did have to go through the whole procedure described in the toolkit to manually unistall old drivers and manually remove references to the device before reinstalling the driver.
You can get into TWRP, correct? Do you have a USB-OTG cable? You could download a ROM, put it on a flash drive then install it directly from the USB drive. There should be some flashable stock roms, or if you have an old Nandroid backup on your computer (always a good idea to have) you could restore it.
Sent from my Nexus 7 using xda app-developers app
gc84245 said:
You can get into TWRP, correct? Do you have a USB-OTG cable? You could download a ROM, put it on a flash drive then install it directly from the USB drive. There should be some flashable stock roms, or if you have an old Nandroid backup on your computer (always a good idea to have) you could restore it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Don't know what a USB-OTG cable is, and not sure how you'd connect a flash drive, but...
I tried one more computer, this time it was a computer with Windows 7 one it. Detected the tablet right away.
So, why the heck does Windows 8 (8.1 to be exact) not allow my tablet to be seen (im sure with the OS on, and booted in, it will)./
tjupille said:
I went through the same experience; it *was* the drivers. If you're using the wugfresh toolkit, it gives at least three options for driver installation. In my case only the drivers from pdanet worked. I've had similar issues in the past with my N7; in that case only the pdanet drivers worked on one computer, and only the Koush drivers worked on a different computer -- both Win 7 by the way; I have no idea why.
I did have to go through the whole procedure described in the toolkit to manually unistall old drivers and manually remove references to the device before reinstalling the driver.
Click to expand...
Click to collapse
This must be why my Windows 8 machines don't work, but I dont remember seeing other driver options, only the one, will keep in mind in the future.
Sounds like the problem is solved, but I highly recommend getting a USB-OTG cable anyways. Go to Amazon and search for "USB-OTG". You can connect flash drives and external hard drives to your tablet. I got mine for $2.
Sent from my Nexus 7 using xda app-developers app