I recently tried to extend my partition using the script on the other thread and everything that could went wrong did went wrong. So I ended up resorting to flashing stock miui via fastboot. During the process, I installed a few things because the adb just decided not to recognize my phone halfway through. So I installed minimal adb, miPhone manager(Chinese version) and android sdk. Now that I have xenonhd installed, my pc doesn't seem to be playing nice with my phone.
Problems:
-adb sideload doesn't want to recognize my phone anymore.
-my USB mass storage device recognizes my phone but the storage media doesn't pops up as blank. Meaning I see the mi3 icon on explorer but it shows up as blank when double-clicked.
-my device manager shows up mi3w as unrecognized device.
My question now is. How do I do a clean wipe of drivers on my PC and could someone provide me with a proper set of drivers that I can install.
Thanks guys.
Sent from my Mi 3W using Tapatalk
You can uninstall the drivers and then connect your phone again and let the drivers auto install
If you had googled then you would have found how to uninstall the drivers, here is the official Microsoft link
https://msdn.microsoft.com/en-us/library/windows/hardware/ff546200(v=vs.85).aspx
Sent from my MI 3W using Tapatalk
Related
Hi
I have 2 Kindle Fire HD 7 inch. The 16GB is rooted and can run ADB commands from the latest FirstAide. The other is a new 32GB (arrived today) and I am trying to root it.
In XPs admin tools/computer management, the Android Composite ADB Interface driver is shown. In Properties/general, the rooted device is shown as working normally, whereas the unrooted device is shown as "Currently, this hardware device is not connected to the computer. (Code 45)"
Obviously, trying to use FirstAide to root the new device won't work if ADB isn't working.
As the PC installation is the same, and even the same USB data is being used, there must be something different with the new device. I can't believe that the storage size plays a part so what should I look at? ADB is turned on in the new device (more/device/ADB).
I do have a factory cable but don't know how that can be used in this instance. The new device seems to work normally, and both device and PC have been rebooted/reset to no avail.
Can anyone help or does it look like the device is faulty?
edit: the new device was v7.2.2 but updated itself soon after to 7.2.3 which is the same as the rooted 16GB device
I just used the factory cable and reset the device which went into fastboot mode but didn't respond to any fastboot commands. Switching off and replacing the factory cable with standard data cable saw it boot normally (I thought the boot mode was persistent until reset?)
Maybe try a factory reset on the new one and then turn off wifi until you root it.
Sent from my KFTT using xda premium
If you connected the 32gb kindle before enabling adb at any point you'll want to UNINSTALL its drivers from device manager on your PC and upon reconnect your PC will install the adb version of these drivers assuming adb is enabled.
Let me know how this works for you.
Sent from my KFTT using xda app-developers app
Thanks for the replies. I'm a little confused.
Eventually, I uninstalled the drivers from the PC. I found I couldn't install the drivers using the new FirstAide, I got an error message, so I used the old FirstAide and the drivers installed no problem. From there I could get to root. :laugh:
However, now I find that the old device isn't seen by ADB whilst the new one is..... it's as if the drivers are device specific.
Can anyone explain this to me? In my mind, the drivers, once installed correctly should work for all devices. At the moment, I'm faced with uninstalling/reinstalling drivers whenever I want to swap devices.
victorlugo do you literally mean that if you charge up the device without enabling ADB then you won't be able to install the drivers? As it is, enabling ADB was one of the first things I did, as it was my intention to root it immediately and transfer data from the 16GB model using Titanium.
well, I now have 5 drivers installed covering the 2 devices:
2 x Android ADB Interface
2 x Android Composite ADB Interface
1 x Tate-PVT-08
anyone have any ideas why this might happen? Each device responds to ADB ok, but they use separate drivers
I'm looking to port app restores - mostly game saves - from my old phone to the Droid Turbo. I've used Helium in the past but I can't get the Turbo to connect to Windows 7 yet. I've been trying to use the drivers linked from the Helium URL and here, but without success.
Anyone have luck tracking down USB drivers?
Any suggestions other than Helium?
Update:
Looks like the Motorola drivers started working as soon as I posted this (of course...).
This one was driving me nuts the last two days. On Win8.1 x64, the driver wouldn't auto-load when the device was plugged in. Until I saw your edit reason, I didn't even think to go through the manual device list and select the driver manually. "ADB Interface/Mot Composite ADB Interface" worked for me, as well.
Also, if you change your USB Storage mode on the phone, it may also change how the ADB Interface is detected. I had to manually add the ADB Interface driver a second time when I turned on MTP mode for the USB Storage connection. I had had it previously disabled while trying to figure out the ADB issues, once I had ADB working, I re-enabled MTP and subsequently Windows "forgot" the ADB device driver again.
For others: I had to go through the device manager, pick the unknown adb device and update drivers, pick drivers, select the clockworkmod section on the left and instead of mot composite I had to use the first option, android composite adb interface. Now my mtp connection works. Haven't tried reconnecting yet so it may well forget the drivers again, but at least I know what to do now!
Need the drivers from google sdk kit. Just google search installing adb drivers. I used helium fine.
I am so frustrated right now I don't even know what to do. Here is where I am and I welcome any ideas. I have read and tried every suggestion I can think of.
I have a Win 8 laptop I want to connect the Nexus to so that I can sideload 5.1. Currently the phone is still factory stock.
With debug turned off, my computer sees the nexus and I can transfer files. It sees it as an MTP device
With USB DEbug checked, my computer no longer sees it at all.
I have the latest android sdk installed.
When I go into platform tools and run adb devices- it is blank, nothing in either state (debug on or off).
Also it is not recognized in "Fastboot devices" when in fastboot mode, so the computer is not seeing it.
I have used USBDEview to delete drivers, then reinstalled using the latest Google USB drivers. no Help.
I have tried using motorola device manager to install proper drivers, no help.
Tried using Koush universal drivers and it did not help.
Thank you for any ideas you may have.
Try using "Nexus Root Toolkit" to set up the drivers for you. It has a driver setup tool.
aawshads said:
I am so frustrated right now I don't even know what to do. Here is where I am and I welcome any ideas. I have read and tried every suggestion I can think of.
I have a Win 8 laptop I want to connect the Nexus to so that I can sideload 5.1. Currently the phone is still factory stock.
With debug turned off, my computer sees the nexus and I can transfer files. It sees it as an MTP device
With USB DEbug checked, my computer no longer sees it at all.
I have the latest android sdk installed.
When I go into platform tools and run adb devices- it is blank, nothing in either state (debug on or off).
Also it is not recognized in "Fastboot devices" when in fastboot mode, so the computer is not seeing it.
I have used USBDEview to delete drivers, then reinstalled using the latest Google USB drivers. no Help.
I have tried using motorola device manager to install proper drivers, no help.
Tried using Koush universal drivers and it did not help.
Thank you for any ideas you may have.
Click to expand...
Click to collapse
I just went through that a couple hours ago. I ended up having to go in the device manager, and manually point it to look for the drivers in the platform-tools folder of windows sdk. Once I did that, the little yellow triangle went away, and all was well, adb and fastboot worked as normal. Hopefully that works for you too.
Hi all,
First a quick info:
The Problem -- Nexus 6 internal storage doesn't show up when connecting to my main desktop computer.
I have had my Nexus 6 for almost a year now and since the beginning I couldn't make my main computer to recognize the phone's internal storage.
Whenever I connected the phone to another computer, the driver installed just fine and I was able to access the internal storage.
I previously had a first gen moto g and I thought the problem was because the moto g drivers were causing some mess with the Nexus so I uninstalled the old drivers and plugged my nexus so windows automatically downloaded what is shown as "Google Nexus ADB Interface" under Android device in Device manager.
I also have installed Android SDK tools in my PC since I had the Moto g and I cant remember how many times I have updated it. The Google driver is shown as installed.
The device is unlocked but not rooted.
Here comes the weird part... If I have USB debugging enabled then I can see the camera files in my PC when I choose PTP in USB configuration. However.. if I disable USB debugging then I can't even see the pictures.
I have tried selecting PTP and changing back to MTP as suggested in some threads with no luck.
I also tried turning the device off and then boot into fastboot, then plug the phone into the computer as this worked in some other computer.
This is driving me crazy, I know this is a computer related problem but I don't know what else to try.
Could you help me please?
Thanks
adrek09 said:
The Problem -- Nexus 6 internal storage doesn't show up when connecting to my main desktop computer.
Whenever I connected the phone to another computer, the driver installed just fine and I was able to access the internal storage.
Click to expand...
Click to collapse
www.wugfresh.com
Install the Nexus Root Toolkit on your PC.
In a sub directory of that kit you will find several usb drivers. Do some trial and error with those drivers.
NLBeev said:
www.wugfresh.com
Install the Nexus Root Toolkit on your PC.
In a sub directory of that kit you will find several usb drivers. Do some trial and error with those drivers.
Click to expand...
Click to collapse
Hi, thanks for the reply,
I forgot to tell that I tried that one too.
I followed the driver installation guide step by step with no luck.
Tried the recommended solution at step 3 of the guide and since it didnt work then I tried the manual installation with a couple "Bluetooth Peripheral Device" devices that are shown under Other Devices in Device manager
adrek09 said:
Hi, thanks for the reply,
I forgot to tell that I tried that one too.
I followed the driver installation guide step by step with no luck.
Click to expand...
Click to collapse
Because it works on a different PC. I assumed a driver issue.
My Suggestion is to install the driver manually.
Open the device manager.
After connecting you must see a change in the device manager. If not change USB-port and/or cable. And change on the Nexus 6 the charging
mode to data mode.
When still no 'internal storage' back to device manager and update the driver by right clicking. Try automatic and search on my computer - navigate to the drivers in NRT.
Hey guys, a fellow flasher here. I've tried everything ( really everyhting i know ) but still i cant get my op3t to get recognized in adb or in fastboot.
It's just shows nothing under the list of adb device. Also in drivers section i cant make that exclamation go which means that drivers arent installed properly, but i've tried every driver and toolkit but none of them are of any help as when i go to update driver and select the option to browse to update the driver i cant find the google one. And when i connect my phone with debugging on it shows( in the right bottom corner ) drivers for adb installing but after about 5 seconds it shows failed-no driver found.
P.S-windows 7 is being used and driver enforcing is off also ive used the same pc to flash and unlock my oneplus one many times.
Help!!!
Try another USB port, another driver source, open console as admin, restart your PC after installing driver etc... there are many options... Did you try the command "fastboot devices"?
redukt said:
Try another USB port, another driver source, open console as admin, restart your PC after installing driver etc... there are many options... Did you try the command "fastboot devices"?
Click to expand...
Click to collapse
Thank you but I've tried all this but no luck.
But I've got it working now.
Things I did-
Download android SDK manager, run it as admin, while connected to internet download the Google drivers under extras section, connected op3t with debugging on, go to drivers section, update that driver manually by selecting the google folder in the android SDK folder under extras and now it's good to go!..
BTW do you suggest that should I unlock bootloader and flash twrp the traditional way or use that unified toolkit?