Translated from Original Link....
http://m.zol.com.cn/padbbs/d173_8385.html
Steps in English. Simplified and rooted in 15 minutes!
1. Download and install Fastboot ADB and Android Drivers from here. Remove all other Android drivers before you start installing this. It is better to have a clean machine without other android USB drivers getting in the way.
http://forum.xda-developers.com/showthread.php?t=2588979
2. Download Intel Fastboot Tethered Temporary Recovery Session Launcher
https://www.androidfilehost.com/?fid=23991606952604606
3. Download SuperSU into your N1 device. Put it in download folder.
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3a. Download pa_gapps_modular_nano from here. This is the Google Play Store.
https://drive.google.com/folderview...JwYm9nNEt0cndRU1VaeDdzNmN6TXZYVlk&usp=sharing
4. Run the Intel Fastboot Tethered Temporary Recovery executable. Type ACCEPT and enter T4 option. Keep this running in the background don't close it.
http://bbs.fd.zol-img.com.cn/t_s320...VVarC-INpsIAADvNf4lBFUAADy2ABYE0wAAO9N357.png
5. Device will boot and go into bootloader mode. Next Go to My Computer, right mouse click and select Device Manager. Look for Unknown Android device and update driver. Important!! Select only the Android driver.
http://i0.bbswater.fd.zol-img.com.c...lVarh2IJaD5AAE0UD6WLr0AADy3QBVUiEAATRo910.png
6. Once the Android drivers have been installed successfully, the recovery files will be automatically copied to the device. If doesn't happen, repeat Step 4 again.
http://i1.bbswater.fd.zol-img.com.c...VVarmqISftXAAF0GxqUxooAADy3QMrrLwAAXQz437.png
7. Once the device is finished copying the files successfully, it will automatically boot into Recovery mode. You can install the SuperSU file from your download directory. Install google app store if you wish, but it may mess up your US AOSP keyboard. Switch to other keyboards! If you don't have it, download from Google play.
7a. Go back --> Go back --> Reboot system now --> Yes - Fix /system/xbin/su
8. Reboot the device after you have finished the installation. Download and install SuperSU.apk from the Internet.
9. Done! No more error popup messages when you run SuperSU.
It is rooted with Google Play!
it is not working for me, I am on 5.0.2 and got my N1 yesterday...
after typing accept it is ok but as soon as I type T4 it shows me an error. need help ASAP
Have you updated to the latest build A5CN51C?
Can you post your error here?
Sent from my N1 using XDA Free mobile app
gtee said:
Have you updated to the latest build A5CN51C?
Can you post your error here?
Sent from my N1 using XDA Free mobile app
Click to expand...
Click to collapse
yes I have updated it, check the picture for error details...
You need to connect to internet and plug in the N1 USB to your computer to let it detect the generic android driver. Currently its not detected!
Sent from my N1 using XDA Free mobile app
gtee said:
You need to connect to internet and plug in the N1 USB to your computer to let it detect the generic android driver. Currently its not detected!
Sent from my N1 using XDA Free mobile app
Click to expand...
Click to collapse
Well I am connected to the internet, this is exactly what I am asking, why isn't it detecting if there are no drivers. I am always connected to the internet
Sent from my N1 using XDA Premium 4 mobile app
gtee said:
You need to connect to internet and plug in the N1 USB to your computer to let it detect the generic android driver. Currently its not detected!
Sent from my N1 using XDA Free mobile app
Click to expand...
Click to collapse
It has been few days since I last time heard from you, any help with the google services...
Sent from my N1 using XDA Premium 4 mobile app
Are you running Windows 7?
Sent from my N1 using XDA Free mobile app
---------- Post added at 08:25 PM ---------- Previous post was at 08:25 PM ----------
[/COLOR]
gtee said:
Are you running Windows 7?
Sent from my N1 using XDA Free mobile app
Click to expand...
Click to collapse
No its win 8.1, and in hardware management the mtp is showing yellow exclamation mark. I guess this now make my problem clear.
Sent from my LG-F320S using XDA Premium 4 mobile app
Just rooted and for those who can't detect the device
thanks for the post, I just rooted my Nokia N1. But one very important step is missing in the post if you can't detect the device in "Intel Fastboot Tethered Temporary Recovery executable".
In your Nokia N1, please remember to uncheck both "MTP" and "PTP" under "settings" --> "Storage" -->click on the 3 vertical dots in upper right
your android keyboard will keep crashing after root, but I just download the .apk file and use another keyboard.
LaxtC said:
thanks for the post, I just rooted my Nokia N1. But one very important step is missing in the post if you can't detect the device in "Intel Fastboot Tethered Temporary Recovery executable".
In your Nokia N1, please remember to uncheck both "MTP" and "PTP" under "settings" --> "Storage" -->click on the 3 vertical dots in upper right
your android keyboard will keep crashing after root, but I just download the .apk file and use another keyboard.
Click to expand...
Click to collapse
Your step is all I needed. Rooted it just now within 5 minutes. Thank you very much
Sent from my LG-F320S using XDA Premium 4 mobile app
data transfer failure...
Dear XDA Friends,
Yesterday I got my N1. I also immediately the Google Apps attempts to install after gtee's instructions.
However, I get the following error
Can someone help me?
thx in adv
der_hd said:
Dear XDA Friends,
Yesterday I got my N1. I also immediately the Google Apps attempts to install after gtee's instructions.
However, I get the following error
Can someone help me?
thx in adv
Click to expand...
Click to collapse
don't see the error image.. repost pls
LaxtC said:
don't see the error image.. repost pls
Click to expand...
Click to collapse
Here again the error image. I hope jou see it now.
It's done. Root and Gapps are on the N1.
My problem also comes from the default driver to use the bootloader interface.
Thx to jujudeshighland http://forum.xda-developers.com/showpost.php?p=60925623&postcount=44
The fastboot drivers must be reinstalled each time for "Android Bootloader Interface".
problems recognising N1
Hi, I was hoping you may be able to help with some trouble I am having with a new Nokia N1. I am trying to install the google play services etc. The N1 I have came from Taiwan, hence the Chinese build. it is updated to android 5.0.2. build number is A5CN51C.
I have tried to use the ADB installer (ver1.4.2) despite everything I try I cannot get the N1 to install using the google driver. the computer installs the N1 as a portable device using the default Microsoft mtp driver (from 2006).
I have no conflicting android drivers (this is the first android device I have) and have run the ADB tool installing the google drivers. however, no matter what I try, it consistently loads the default Microsoft driver. I have disabled it, uninstalled, rebooted, tried multiple computers etc. each time however when I plug the N1 back in, it reinstalls the Microsoft driver.
I read the thread suggesting I need to uncheck MTP and PTP support on the device (under storage) however when I do that the computer doesn't recognise the N1 at all and hence no driver is installed when I plug the device in.
I also read that I need to enable USB debugging on the device however my N1 doesn't seem to have that option.
would you have any idea of what I may be doing wrong?
thanks very much
In order to root the Taiwanese N1 (which has google play store/apps preinstalled) just skip step 3a?
tlr1000 said:
In order to root the Taiwanese N1 (which has google play store/apps preinstalled) just skip step 3a?
Click to expand...
Click to collapse
unfortunately not. when i run the Intel Fastboot Tethered Temporary Recovery executable it does not recognise my device, i presume as the wrong driver is being installed as said above.
btw, on my device at least (from Taiwan), google play and apps do not come pre-installed.
pdt100 said:
Hi, I was hoping you may be able to help with some trouble I am having with a new Nokia N1. I am trying to install the google play services etc. The N1 I have came from Taiwan, hence the Chinese build. it is updated to android 5.0.2. build number is A5CN51C.
I have tried to use the ADB installer (ver1.4.2) despite everything I try I cannot get the N1 to install using the google driver. the computer installs the N1 as a portable device using the default Microsoft mtp driver (from 2006).
I have no conflicting android drivers (this is the first android device I have) and have run the ADB tool installing the google drivers. however, no matter what I try, it consistently loads the default Microsoft driver. I have disabled it, uninstalled, rebooted, tried multiple computers etc. each time however when I plug the N1 back in, it reinstalls the Microsoft driver.
I read the thread suggesting I need to uncheck MTP and PTP support on the device (under storage) however when I do that the computer doesn't recognise the N1 at all and hence no driver is installed when I plug the device in.
I also read that I need to enable USB debugging on the device however my N1 doesn't seem to have that option.
would you have any idea of what I may be doing wrong?
thanks very much
Click to expand...
Click to collapse
Have the same problem with my N1.
Could somebody help please?
---------- Post added at 06:37 PM ---------- Previous post was at 06:23 PM ----------
moloun said:
Have the same problem with my N1.
Could somebody help please?
Click to expand...
Click to collapse
Found the solution
Go to "About tablet" menu, tap Build number 8 times - new Developer options menu will appear.
Go there and check USB debugging, after this you will see new unrecognized device to install drivers
pdt100 said:
unfortunately not. when i run the Intel Fastboot Tethered Temporary Recovery executable it does not recognise my device, i presume as the wrong driver is being installed as said above.
btw, on my device at least (from Taiwan), google play and apps do not come pre-installed.
Click to expand...
Click to collapse
I just received my N1 from Taiwan and out of the box it has the google apps like chrome browser, play store, google maps, drive, etc. Mine was purchased at Sunfar which appears to be the only authorized reseller in Taiwan. Did yours come from Sunfar?
Related
Hello!!
Well, hey guys. I thought I tell you the story, on why I posted this thread.
It started as I was installing Windows 8, on my laptop, and had the same problem, as some others. I just could not install the drivers, for my Droid, so I had a looksee and found that Windows 8 didn't yet have the capability, to download unsigned drivers, unlike Windows 7. So, I found a way of "tricking" Windows, into thinking, that these drivers are legit and it isn't forbidden to use, which is exactly what this tutorial tells Windows, in a way.
So, get going and use the full potential of your Android device!
Tutorial:
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... : devmgmt.msc
Now, the dive manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here/
To prevent confusion: When I say install, it can mean unpack, or instal... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has poped up, choose "Browse my computer" and goto your dsktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\adb reboot-bootloader
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick, from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices.
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check my root helper out, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your SAMUNG GALAXY NEXUS!"!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Addition: You can only reboot into bootloader, if you are using a motorola, Google or HTC branded Android device! This will NOT work with Samsung models (i.e. Galaxy S II/III) due to the fact, that they use Odin mode. Should the drivers need updating, for some devices, please let me know!
Motorola Razr
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Click to expand...
Click to collapse
Download MotoHelper. Right click the file and run in compatibility mode. It should install the drivers. I used this to run fastboot with my xoom.
It still hangs while running as admin under compatability mode for 7, I'll try as XP momentarily.
Edit: XP compatability didn't work either.
thejakenixon said:
It still hangs while running as admin under compatability mode for 7, I'll try as XP momentarily.
Edit: XP compatability didn't work either.
Click to expand...
Click to collapse
Bummer, I just remembered there was a setting to skip os version check in compatibility mode. Did you try that? If that won't work unfortunately I don't know what else to try. Sorry.
Sent from my Xoom using XDA Premium HD app
thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
Click to expand...
Click to collapse
First of all, thanks, for letting me know about the link It's uploading again ^^
Yes, you can do the same for your Motorola. But only with the ADB drivers. Just do the same as with the Samsung. Select your device, form the devman. and right click. Update device drivers -> Browse -> Let me choose from a list... -> Samsnung ADB interface.
They are all provided by Google, inc. so, they are compatible, with every Android device. I've even used my Samsung ADB drivers, for a Sony Ericsson Xperia X8. So I can actually say, for myself, that they work. You then can work, using fastboot... ^^
Have fun fastbooting!
LG familyguy59/Beatsleigher
Well, I'm definitly glad, to see I'm actually helping some people, and they're appreciating it!!
I don't remember mentioning it, but if you Need help, PM me. I'll help you via Team Viewer ^^
will this work on Windows 8 Release Preview also ? are those compatible with x64 version of W8?
iconicpaul said:
will this work on Windows 8 Release Preview also ? are those compatible with x64 version of W8?
Click to expand...
Click to collapse
Yes, it works on both x86 and x64 bit architectures of Windows 8, works withRC and with pre-release...
Sent from my GT-I9300 using xda app-developers app
confirmed, it works, thank you...very fast and easy
thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
Click to expand...
Click to collapse
To your edit. You have extracted the files. This is also called "installing" because you have extracted NEEDED files. Even when you extract a .zip/.rar/.tar/.tar.gz and so on, because you need files out of them, you are installing, but not to the system, but to yourself
Sorry for bringing up an old post, but this method is not working for me on Windows 8 Consumer Preview. When I'm trying to install the ADB drivers, it says the drivers cannot be installed because it's not digitally signed.
UPDATE: I got it to work by disabling the Digital Signature Enforcement on Windows 8. Steps: Restart Windows > Boot loader Menu > Other Options > Advance Options > *Computer Automatically Restarts* > Press F7 to Disable Digital Signature Enforcement
I cant get odin to work on win8 with my epic touch could this be my solution? Ive tried everything
Sent from my SPH-D710 using xda app-developers app
2phonejones said:
I cant get odin to work on win8 with my epic touch could this be my solution? Ive tried everything
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yes, it should work with all Android-modification applications. I have never really had problems, with Odin, with any version of Windows, mainly because this is the first thing I do, on any of my Windows machines, but it is always worth a try Tell us, what you have found out!
If necessary, I'll try to find a solution myself
Sent from some GS III in some country, to a server somewhere in the US...
iconicpaul said:
confirmed, it works, thank you...very fast and easy
Click to expand...
Click to collapse
No worries, dude That's what I posted this thread for.
familyguy59 said:
Yes, it should work with all Android-modification applications. I have never really had problems, with Odin, with any version of Windows, mainly because this is the first thing I do, on any of my Windows machines, but it is always worth a try Tell us, what you have found out!
If necessary, I'll try to find a solution myself
Sent from some GS III in some country, to a server somewhere in the US...
Click to expand...
Click to collapse
thanks bro i didnt think anyone would repsond lol. Trying now, report back with results i want to flash so bad.:good:
Could someone pls. create a video tutorial, nad post this on Youtube, for me?
My laptop broke a couple of days ago, and my PC is only capable of running 98 - Vista, so, running on XP with 1GB of RAM.
I would appreciate this very much!
If you could do so and send me the link, via PM, I would be glad to pay 5€, via PayPal!
2phonejones said:
thanks bro i didnt think anyone would repsond lol. Trying now, report back with results i want to flash so bad.:good:
Click to expand...
Click to collapse
Ok, dude! Have fun!
Didn't work for me.
jorgefcbastos said:
Didn't work for me.
Click to expand...
Click to collapse
Did you follow the tutorial COMPLETELY, or did you leave stuff out? If you left something out, it's obviously not going to work
You may have to disable device driver signing, I've had quite a few people notify me about this.
But I'll sign the drivers, ASAP, so you won't have this problem
LG familyguy59/Beatsleigher
Edit: I forgot to mention, you need to tell me what exactly didn't work, otherwise I can't really help you
Hello,
I have a problem the my HTC One X and my (Windows 7 x64) Computer. It won't install the correct drivers to use ADB and to see it in Windows Explorer. I've tried everythingI can think of. I know there thousands of other threads like this, and I read many of them but none provide a solution for me :/. I'm sure my One X is not the problem, it's working fine, I have a laptop wich also runs Windows 7 x64 and it's all working fine on it. (It's a Lenovo Ideapad Z500, i7 version) What I've tried:
- 4 different USB Ports (I have tried 2 USB2 ports and 2 USB3 ports. No luck.
- Remove the device from system using Windows Device Manager -> Disconnect phone -> Install HTC Sync -> Reboot -> connect phone. Nothing happens, Windows reports no drivers can be found.
- Manually select drivers from the HTC Sync Installation folder. Windows tells me those aren't the correct drivers. (For me: C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
And yes, USB debugging is on, and I do accept HTC Sync Manager on my phone. I am running ARHD 31.0. My phone does connect OK in Fastboot mode, by the way. I can use Fastboot commands perfectly fine. (Flash boot/recovery image, clear cache etc etc)
I have no idea what to do to get it working, but maybe you guys do? Any tips/ideas?
Thanks in advance.
Had this problem last week. I solved it this way:
- Uninstalled HTC Sync + HTC Drivers
- Installed ADB Universal Drivers: http://drivers.softpedia.com/get/MOBILES/Clockworkmod/Clockworkmod-Universal-Android-ADB-Driver.shtml
- Rebooted PC
- Booted my HOX in bootloader
- went to fastboot
- connected usb cable between pc and hox
- went in recovery mod (latest cwm version)
- from there I was able to push adb commands from my pc
I basically did what is said on this page: http://news.softpedia.com/news/A-Clockworkmod-Universal-ADB-Driver-Is-Finally-Up-for-Grabs-343944.shtml
You can also use ADB over network if your phone boot properly and if your PC is on the same wifi network.
Thanks Alray for the tips but it doesn't install that driver either. Still a big ! in device manager named Android Phone. And I shouldn't need to push anything to the phone AFAIK, as I said it all works fine on the laptop, Including ADB!
What if u turn on 'automatically install from windows update' option and let the windows make the work.
Sent from my HTC One X using xda premium
convict_moody said:
What if u turn on 'automatically install from windows update' option and let the windows make the work.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It says it can't find good drivers in Windows Update.
Did u enabled the option?
This morning I faced the same problem since I recovered my pc to windows 7 x64 ultimate. And fixed it through the option, when I come home ill take screenshots and post. Btw the options are in the bottom of the window where it says driver failed.
Sent from my HTC One X using xda premium
convict_moody said:
Did u enabled the option?
This morning I faced the same problem since I recovered my pc to windows 7 x64 ultimate. And fixed it through the option, when I come home ill take screenshots and post. Btw the options are in the bottom of the window where it says driver failed.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
All options I can find about downloading drivers from the internet are enabled. When I tell the PC to look online for drivers, it won't find anything.
EDIT:
Okay, I had the setup look thru the whole C drive looking for drivers, it reported it found one. But failed installing because files were missing..... !? That makes me think there's something corrupt in Windows/System32/Drivers or somewhere in those driver folders.
Try this Link I think it is helpfull, if didn't help I will but when I reach home.
http://windows.microsoft.com/en-us/...ivers-and-updates-for-your-hardware#section_2
Sent from my HTC One X using xda premium
convict_moody said:
Try this Link I think it is helpfull, if didn't help I will but when I reach home.
http://windows.microsoft.com/en-us/...ivers-and-updates-for-your-hardware#section_2
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks for the link I was looking for something like that. But nothing works, I already had setup everything automatic updating and driver search thru windows update. It can't find any drivers.
Hey, I just wanted to chime in on this thread because I'm having precisely the same problem as Qubica.
I'm using Windows 7/64 and I've been using this laptop to manage/root/ADB several Android devices for as long as I've owned it.
I noticed last Friday that I could no longer mount my T-Mobile G2 either as a USB mass-storage device nor could I connect to it using ADB. This was the day after Windows Update installed a bunch of patches, and I had also installed the updated chipset drivers for my laptop a few days earlier.
I took a look at the device manager and this is what I saw:
(android_devmgmt.png)
Now, that's weird because I mount the storage card at least two times a month to move files around. So I did what seemed like the reasonable thing and Uninstalled the device altogether, and then installed the HTC Sync app to reinstall the drivers, as I had done originally. Unfortunately, the "Android Phone" non-detection of the device has persisted.
The installation logs from the HTC Sync app also indicates that the drivers were successfully installed, but the installer seems to quit about halfway through the process, so it's not at all clear that the installation logs are accurate.
Here's what the properties sheet of that device looks like:
(android_devmgmt_properties.png)
I've been following the advice I've read here and elsewhere: I've attempted to download several different versions of the HTC drivers from various locations and manually point Device Manager at the folders containing those drivers. I've extracted and executed the HTCDriver.exe installer separately from the HTC Sync installer. I've attempted to install generic ADB drivers from a number of locations, including Google and the Clockworkmod Universal ADB drivers.
Here's the result when I try to install the drivers (by pointing Windows at the correct location for the driver files) or if I allow Windows Update to search for the drivers:
(cant-find-android-driver.png)
So, this morning I tried the more drastic step of uninstalling all of the USB Root Hub devices and rebooting the laptop. When the computer came back, it did not automagically reload those generic drivers, but fortunately I was able to manually choose the generic (Standard USB Host Controller) -> USB Root Hub device from the list of options, and it worked---for getting the USB ports to function, but not the Android device.
I've also checked to make sure there were no software restriction policies in place in gpedit.msc that affected the installation of the drivers, and found none. I also poked around in the Registry in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles path and found no problems there with either permissions or settings.
I'm basically at my wit's end here; Windows is behaving like the driver installation is subject to a software restriction policy -- seemingly, actively preventing the driver from being installed -- but nothing shows up in the logs that would indicate that a policy is in place. The laptop can't mount the device, and I'm kind of stuck.
I guess I'll follow the thread for a while and see if anyone else has any suggestions. Thanks in advance to all that offer their help.
Amishrabbit said:
--Long post--
Click to expand...
Click to collapse
Hi, I've did everything you did execept for uninstalling the USB root hub and looking in the registry, I hope someone has a solution....
Anybody?
I prefer uninstalling the driver (Called unknown device, and it appears when I plug the device) from device manager, unplug your device then replug it again and wait for windows to get your driver.
Sent from my HTC One X using xda premium
convict_moody said:
I prefer uninstalling the driver (Called unknown device, and it appears when I plug the device) from device manager, unplug your device then replug it again and wait for windows to get your driver.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I tried that many times, the problem is, it doesn't get the driver when I plug it back in.
Do u have linux?
Sent from my HTC One X using xda premium
convict_moody said:
Do u have linux?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Not at the moment, but I can get it.
If you can't solve the drivers problem, install linux then install adb and fastboot packages from the sftware marketplace. That should help.
Sent from my HTC One X using xda premium
convict_moody said:
If you can't solve the drivers problem, install linux then install adb and fastboot packages from the sftware marketplace. That should help.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
But there must be a way to get it working, as it works PERFECT on my laptop. (Wich uses Microsoft drivers!)
Here's a screenshot][ of my laptop:
http://i.imgur.com/WCT2ku2.png
Try uninstalling the unknown device, and when the driver not found notification appears click on it and take a screenshot and post it here.
Sent from my HTC One X using xda premium
convict_moody said:
Try uninstalling the unknown device, and when the driver not found notification appears click on it and take a screenshot and post it here.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I'll have to do that tonight, I can't access my PC right now. But you mean the notification on bottom right corner? If I click on it a small window pops up saying "ANDROID PHONE: No drivers found" with a red cross.
Can anyone help me?
I'm running windows 8 64-bit, and I have an HTC One from VZW.
The phone is recognized via ADB, but whenever I get into the bootloader, it tells me the device isnt recognized and I can't do any fastboot commands with it. I was able to root and use fastboot on my N7 2013 from the same PC, so this is frustrating because I want to send my One in to sonic but if I can't DO anything when I s-off there's no point in sending it it.
If anyone can help I'd appreciate it.
Thanks
PS - I've only tried this PC, no others. It may work on my macbook but thats away for repair.
crazyg0od33 said:
Can anyone help me?
I'm running windows 8 64-bit, and I have an HTC One from VZW.
The phone is recognized via ADB, but whenever I get into the bootloader, it tells me the device isnt recognized and I can't do any fastboot commands with it. I was able to root and use fastboot on my N7 2013 from the same PC, so this is frustrating because I want to send my One in to sonic but if I can't DO anything when I s-off there's no point in sending it it.
If anyone can help I'd appreciate it.
Thanks
PS - I've only tried this PC, no others. It may work on my macbook but thats away for repair.
Click to expand...
Click to collapse
I would just install HTC Sync, sounds like it's a driver issue and HTC Sync will provide those needed new drivers for HTC.
andybones said:
I would just install HTC Sync, sounds like it's a driver issue and HTC Sync will provide those needed new drivers for HTC.
Click to expand...
Click to collapse
So just install and plug my phone in and the drivers will be installed?
Sent from my HTC6500LVW using Tapatalk 4
EDIT - that didnt do anything
Looks like I need to try something else...
crazyg0od33 said:
EDIT - that didnt do anything
Looks like I need to try something else...
Click to expand...
Click to collapse
sorry, thought I read it installed all the new drivers, you could try using Google to find the HTC current drivers, I can give you the numbers I have on mine my cpu is win 7 64bit not sure if it'll help but when in "uninstall or change a program" my HTC BMP USB Driver driver # is 1.0.5375
and my HTC Driver Installer driver # is 4.0.1.001
can't say it this helps at all but this is the CPU I used that I fixed the issue with
Best of luck!
andybones said:
sorry, thought I read it installed all the new drivers, you could try using Google to find the HTC current drivers, I can give you the numbers I have on mine my cpu is win 7 64bit not sure if it'll help but when in "uninstall or change a program" my HTC BMP USB Driver driver # is 1.0.5375
and my HTC Driver Installer driver # is 4.0.1.001
can't say it this helps at all but this is the CPU I used that I fixed the issue with
Best of luck!
Click to expand...
Click to collapse
My BMP is the same but my HTC Driver Installer is 4.0.3.001
Maybe I can find that other one and it will work for me
Here is a previous post I made to another guy having the same problem. Not sure if this will help but this is what I did.
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
eL_777 said:
Here is a previous post I made to another guy having the same problem. Not sure if this will help but this is what I did.
-snip-
-eL
Click to expand...
Click to collapse
Yeah I'm going to try it out on my roommates laptop that only has samsung drivers and the ADB installed and see what happens. Can't reformat the PC cause it's my School desktop and I've got work on there.
Once my macbook pro comes back from repairs I'll use that though, since I've never had issues running adb commands on my mac
Found a soultion
After I tried almost everything I tried to improvise and try something totally different and it worked!
First uninstall the driver in the Device Manger and then press to update it >> then press Browse my Computer for driver Software >> then press on Let me pick from list.... >> in the list choose the Portable Devices >> choose MPT USB Drive !
And It works...
:good:
gald said:
After I tried almost everything I tried to improvise and try something totally different and it worked!
First uninstall the driver in the Device Manger and then press to update it >> then press Browse my Computer for driver Software >> then press on Let me pick from list.... >> in the list choose the Portable Devices >> choose MPT USB Drive !
And It works...
:good:
Click to expand...
Click to collapse
MPT USB Drive isnt one of my options
However I've found that it's microsofts USB3 drivers, which override the Intel ones.
I just got my macbook back from repairs and it has USB3 ports as well so I was worried it wouldnt work, but its working fine from there
I'm having this same problem and nothing I do is working. I even tried from another computer but had no luck. adb finds the phone fine but fastboot just won't work. This is keeping me from getting S-Off. Someone please help.
Edit: Nevermind I think the issue is that I'm using Windows 8.1
I'm having the same problem I'm windows 8 64bit...
I have a nagging feeling that it's pda net.. I need to look into it today sometime
Sent from my HTC6500LVW using xda app-developers app
I've been trying to play with some of the ROM's of Pokemon games recently and i've been using the Pokemon ROM editor to edit the games ROM's. This was before i rooted my nexus 7. Be aware that I haven't flashed any other ROM's or played with any kernels or device mechanics yet and the device was still connecting as MTP before I had rooted and for a while after i had rooted. I can connect it as PTP, but that's not useful when you need to take the whole .nds file for a game off your device. I'm not quite sure what's causing it, but I can tell you what i've already tried so far.
I've reinstalled the ADB drivers and every single part of my Nexus 7 from both PC's that I plugged it into, then enabled MTP and reconnected them, but Windows gives me a driver not found error and so ends the driver solution. I've connected it to more than one PC, one of which had not had the device connected to it ever before, yet it still it didn't appear. (Both PCs are running windows 7), so that means it's either Windows 7 doesn't like Google and wants to screw them by not showing their devices (which is unlikely) or the nexus 7 is just being derpy (which is likely). I've tried different cables, but i assume the cable is alright seeing as it can charge and connect as PTP.
I'm not really sure where else to go from here and i kinda need to edit that ROM soon as my Electabuzz needs to evolve and I need to change his evolution conditions so he evolves at level 56 instead of by trade. There's a random piece of info for you. Also, if i get any solutions that require software downloads, please link to the software or files. I'm pretty new to android tinkering and I don't know all of the terms yet.
EDIT: I don't understand this anymore. At first, PTP was working, now i tried it on a laptop, It didn't work, then i tried it on the PC again and now both PTP and MTP are suddenly working again...
Why does android continue to just fix itself automatically? This is the third time!
SassMaster said:
EDIT: I don't understand this anymore. At first, PTP was working, now i tried it on a laptop, It didn't work, then i tried it on the PC again and now both PTP and MTP are suddenly working again...
Why does android continue to just fix itself automatically? This is the third time!
Click to expand...
Click to collapse
Sounds to me like you have a driver or cable/usb port issue. One of these two links might be useful. Installing a USB driver and [FIX] MTP with USB debugging. Sometimes you might need to go into the device manager and uninstall the driver AND driver software then do a fresh install of the driver. You might want to do a reboot of the computer after uninstalling the driver. I've been lucky and never had problems but my brother had problems and we basically just had to uninstall and reinstall the driver.
SassMaster said:
Why does android continue to just fix itself automatically? This is the third time!
Click to expand...
Click to collapse
To add to what was said above you will need to disables driver security enforcement in order to install the drivers. This will put your computer in test mode and allow you to install non signed drivers. You will also need to manually install the drivers in device manager. I assume you already tried settings > storage > click three dots in the upper right hand side of the screen > click USB connection > select MTP.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
To add to what was said above you will need to disables driver security enforcement in order to install the drivers. This will put your computer in test mode and allow you to install non signed drivers. You will also need to manually install the drivers in device manager. I assume you already tried settings > storage > click three dots in the upper right hand side of the screen > click USB connection > select MTP.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Absolutely right! I also forgot to mention that I have my Windows 7 desktop and laptop both set to Not automatically install drivers which I think makes it easier, at least for me.
You're all wrong! MTP is one big witchery!! It has a mind of its own! It's going to work when you don't need and expect it! It's going to fail when you need and expect it! MTP comes from Microsoft, the house of dark witchcraft and wizardry that gave birth to ugly and sad things like Kin and its misscarried brother Kin 2, Windows Vista and a cursed, evil, dark and lonely soul called Zune! The legend and tales of Gates tell that on Judgement Day, Zune will enslave his very own strain just to take revenge on humanity! Fear the day of revenge! Fear the day of Zune!...
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Hakizi said:
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Click to expand...
Click to collapse
I did the same : Choose from List >fastboot (I didn't install Wug)
jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
This is what worked for me....
http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96
jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
@Istvan_86,
We should move the discussion for your problem here.
cam30era said:
@Istvan_86,
We should move the discussion for your problem here.
Click to expand...
Click to collapse
Hello,
I don't see any link and sorry if I made too many posts.
Istvan_86 said:
Hello,
I don't see any link and sorry if I made too many posts.
Click to expand...
Click to collapse
That's OK. No problem. Did you try the steps in post #5 above?
Which operating system are you on? What worked for me on Windows 10 was to give up after several days and use a Windows 7 computer. I read everything and tried everything and I could not get Fastboot working on this device with Windows 10. I used every toolkit, every driver version, toolkits that install multiple driver versions, Minimal ADB + Fastboot, and who knows what else. If a well-documented end-to-end solution to this ever appears I'll be really grateful.
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
cam30era said:
That's OK. No problem. Did you try the steps in post #5 above?
Click to expand...
Click to collapse
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Istvan_86 said:
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Click to expand...
Click to collapse
Welcome.
cam30era said:
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
Click to expand...
Click to collapse
It's very annoying, there seems to be a few reasons it fails. Cable, 3.0 usb ports, windows 10 drivers. I get different results with different cables in different types of usb ports. Also switching to PTP seems to work using a usb 2.0 port with a standard usb 2.0 A to micro with a micro to c adapter. Charging and MTP fail, but at least ADB and Fastboot respond.
I am going to try to edit the win10 driver using this post as reference.
http://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
---------- Post added at 11:05 PM ---------- Previous post was at 11:04 PM ----------
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
I came to the same conclusion, but after a reboot it was unrecognized again.
Only way I can it to stick is installing the 2nd option drivers via skipsoft toolkit. Connect pixel c via 2.0 port and cable to PC. Switch to ptp. Then manually force install driver choosing have disk using bootloader option. From then on it works using ptp.
What I am able to see using USB Device Tree Viewer, is that when I plug in my Pixel C to my ASUS Z97-A blue usb ports with USB debugging enabled, it can not identify it. Those ports use Microsoft Windows 10 drivers for the Intel USB 3.0 eXensible Host Controller - 1.0. Which is what is causing the failure, not the Pixel C drivers. When I updated my other green USB ports driver, windows used the same ones on my ASMedia USB 3.1 eXtensible Host Controller and also couldn't recognize the Pixel C any longer. I rolled back to ASMedia drivers, it worked fine. Updated using newer ASMedia drivers 4/11/2016 ver 1.16.35.1 and those work fine. Now to find working drivers for the Inter Host. Win7 drivers refuse to load.
UPDATE: If your bios allows, disable xHCI. Your USB ports will work as USB 2.0 but will detect your PIXEL C without issues.
Solution works 100%
If you've installed the SDK drivers and win10 can detect your Pixel C in every mode with usb debugging off. Use these win10 USB xHCi drivers,
http://www.win-raid.com/t834f25-USB-Drivers-original-and-modded.html
@clockcycle,
This solution works 100% too. https://www.ubuntu.com/
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Been smashing my face off the wall since LAST NIGHT trying to figure this out. windows 7 machine/ windows 8/ ubuntu ! trying 100 different methods and this one FINALLY SOLVED THE ISSUE. gawd dayum thank you so much from the future !!!