[Q] Rooted KF wont show up in "My Computer" as drive. - Kindle Fire General

I rooted my KF on a desktop PC and was always able to plug it in and have it show as a drive, before and after.
Now I'm plugging it into a laptop and the KF wouldn't go into "drive mode". I installed the adb driver and now the KF goes into "drive mode", but doesn't show up in "My Computer". What am I missing?

Maybe is a OS isue, try to install another device
If you culdn`t get working then definetly is a os isue

Right click My Computer, choose Manage and go to the Device Manager screen; locate your KF and see if its icon shows a yellow alert (!) symbol. If it does, try installing the drivers by right clicking the icon, choosing "Update Drivers" and letting Windows download them for you. If you see the icon and tried to have Windows download them but it failed, try downloading KFU and installing the drivers that come with it.
If you still have issues and can't resolve this, however, (and as a quick solution) I recommend you install Airdroid, which is a pretty damn cool app on its own right, and lets you download/upload files to your KF through your local Wi-Fi network, among many other things.
Hope that helps, good luck!

Related

[Q] Managed to screw up my computer's drivers somehow, need help

I was trying to use the Kindle Fire Utility to push the market onto my Fire since I was having issues doing it otherwise. It actually ended up pushing all the gapps onto my phone, an Eris, and at some point I guess messed with the drivers, because after I (understandably freaked out and) unplugged my phone the utility couldn't find any devices at all. It was about then that I noticed that my computer has apparently ceased to recognize my Fire being plugged in or unplugged at all. It doesn't show up on the devices window or the device manager at all. It's like it never existed. I have no idea how to fix this with the drivers being completely missing from device manager and the computer not even giving any hint that it's noticed when the device is plugged in, and I'd really like some advice here.
http://forum.xda-developers.com/showpost.php?p=20729347&postcount=5
http://forum.xda-developers.com/showpost.php?p=20761609&postcount=12
My fire runs perfectly fine, and those posts are about bricked fires. My issue is that my computer isn't detecting my fire at all.
ketchupface said:
My fire runs perfectly fine, and those posts are about bricked fires. My issue is that my computer isn't detecting my fire at all.
Click to expand...
Click to collapse
It's gotta be in there somewhere, but it might not be named Kindle. Look in device manager under every option.
the posts are fine and meant to help you
if your kf is not recognised then you have a bad driver installation
the posts shoud help you to sort it out - follow the second post - it worked x times
if you have done and have any problems ask - i'm willing to help if i can
If the device is missing from device manager, and your computer is refusing to show the installed drivers for it, I would try this:
Open an elevated command prompt and type this:
set devmgr_show_nonpresent_devices=1
Then go to start and into the search bar type in devmgmt.msc
Then when device manager opens, click "view" at the top, and click "Show hidden devices"
Any non-present devices that have had drivers loaded for them in the past should show up here. You should be able to right click on the kindle and click uninstall and with any luck when you plug your kindle back in, it will pick it up again.
Best of luck
judasthehelpful said:
If the device is missing from device manager, and your computer is refusing to show the installed drivers for it, I would try this:
Open an elevated command prompt and type this:
set devmgr_show_nonpresent_devices=1
Then go to start and into the search bar type in devmgmt.msc
Then when device manager opens, click "view" at the top, and click "Show hidden devices"
Any non-present devices that have had drivers loaded for them in the past should show up here. You should be able to right click on the kindle and click uninstall and with any luck when you plug your kindle back in, it will pick it up again.
Best of luck
Click to expand...
Click to collapse
This worked! I deleted every instance of "Android ADB" entry, every "Kindle" entry and the entry with the kindle's name and when I plugged it back in it was detected. Thanks!
I'm glad I could help, you seemed very stressed out in your first post

[Q] I just can seem to unbrick my Fire.

I used kindle fire utility 7 and installed twrp. My kindle is version 6.2.1 and now when i turn it on its just the triangle with fire. I press the power button to go into recovery mode like it says at the bottom but that does nothing. Oh and my computer doesnt recognize the device! I notices somethings plugged it (3 tone sounds) and thats it. In device manager it's just labeled as "USB device". Iv'e tried just about everything i can find online,but the kindle fire utility just says "waiting for device" no matter what. Can someone please help me with this issue? Its a brand new kindle i literally got 2 days ago and would really like it back to normal
Thanks!
Manually re-install the ADB drivers by going into Device Manager, clicking on "Unknown Device" or "kindle" or whatever it's called, and manually selecting the "Android ADB Composite Interface" from the list of drivers rather than having Windows automatically search for it.
Then, go back to the Kindle Fire Utility and re-install TWRP.
If you want to get rid of root and TWRP afterwards, use the KFU to download the stock update.zip, and flash it using TWRP. That'll get rid of everything and restore the Fire to its original state.
It only has "Android phone". When i click it it asks me to browse a folder for the driver. I dont know what folder to pick. I tried then android programs files folder but nothing.
What exactly do you mean by "Android phone"? Is the ADB interface installed, or is it just listed as "Unknown Device?"
It is listed as "USB device" but the ADB is installed.
Try clicking on "Have Disk" in that last screen and specifying "C:\Program Files\Android\android-sdk\extras\google\usb_driver" or something to that effect as the file path.
You need to give it the path where the file "android_winusb.inf" is stored.
It just says that the path specified doesn't contain information about your hardware.

Problem Copying Files to N10

So, I have a Laptop with Win7 Home Premium, and my desktop with W7 Ultimate (also where I installed the Android SDK).
For some reason, when I plug my N10 into the laptop, it pops up right away and I'm able to copy files to it. It shows up just like any other mass storage type device under My Computer, and I can drag and drop as I please.
However, on the desktop, I plug it in, the tablet itself looks the same, recognizes it's connected to the computer, but nothing ever comes up. No drive under My Computer, nothing, and when I go into the Device Manager, it is detected as an "Android Device", and beneath is "Android ADB Interface."
Am I missing something as far as drivers in order to be able to copy files to and from my shiny new tab? Anyone else had anything like this issue? Really frustrating.
Edit: Additionally, I looked in the device manager on the laptop as well, and I forget what the N10 was listed under, but it wasn't listed as an ADB Interface device using a driver from Google from 8/27/12, it was using what looked like a generic MS driver from 2006.
mine appears as a media device on my desktop (W8) but if i click on it i can then access internal storage.
Got worried when i couldn't see an external drive to begin with!
So, fixed it.
Very odd, I had to go into the device manager and uninstall the driver for the ADB device, and check the box to remove it from system. Once that was done, disconnect/reconnect the N10. Windows would try to install the driver, and would fail. Unplug N10, reboot it, plug it back in, and Windows picked it up without a hitch.
I can't figure out why I can't seem to have the ADB and MTP driver at once, but...I guess I'll have to deal with it all over again if I want to relock the bootloader or something.
Any other ideas or suggestions as to a more proper fix or why this may have happened are certainly welcomed.
I had the same issue. Here's what I did to fix it:
Device Manager >> Portable Device/Android >> Right-Click and Uninstall driver >> check the delete software blah blah >> click ok >>
Leave the device connected >> Reboot PC/Computer
If you have Windows 7 it'll automatically re-download the MTP Device Drivers and it should work again. I hope this works! let us know.

Kogan Agora HDMI Smart TV Quad Core - Root Access

Hi,
So I have had a good experience with the Kogan Agora 7" a couple of years ago. I flashed a new ROM and my 6 year old still idolizes it. It's perfect for games and movies while traveling and cost bugger all.
I was considering getting my kids a console unit for games but came across the new Quad core HDMI Dongle. I though to myself there is the ticket, When traveling i could use it as a smart TV (plug and play is King) Or it may be possible to replace or augment my Media-portal HTPC system.
I bought one and on the face of it it appears to do all that I require from an Android device like web surfing, mail checking and video streaming fine, except when it came to installing the Playstation controller.
I needed Root access and it was a bit of a pain to get it done. BUT I found it!
I used RK3188_ROOT for CX-919 FW0715 MOD by Everal. found here.
1. Turn the device on
2. Make sure USB debugging is enabled
3. Connect the device to Win7
4. Start the file "TPSparkyRoot.bat" as admin
Enjoy.
So if anyone decides to purchase one of these to play with, you will be glad to know that it is a Rockchip RK188. Weather you think that hardware is good or not is irrelevant but it is useful to know as I tried many methods to gain root but once I had this bit of info it became easy.
Those infinity Pocket PC's may be the same although I can't be sure.
I managed to pair a sixaxis controller and am working on getting it running in a game. I will post if i have any more issues and or success.
Raskern said:
1. Turn the device on
2. Make sure USB debugging is enabled
3. Connect the device to Win7
4. Start the file "TPSparkyRoot.bat" as admin
Click to expand...
Click to collapse
Thanks for posting this info. However I'm not able to get this to work. My PC doesn't recognise the device when it's in "USB Debugging" mode. In the device manager it just appears in "Other Devices" as "KHSTVQCDONA". I've tried updating the software, selecting the "usb_drivers" folder containing drivers provided in the downloading Zip file, and also tried downloading the "Google USB Drivers" directly from Google, but Windows doesn't find the drivers for this device.
If I disable "USB Debugging" the device does connect successfully under "Portable Devices", but clearly that's not much use.
I can't seem to figure it out.
Below are the steps I took in trying to get it to work. I was going to write it as a guide for dummies, but I never got it working...
Download the software from the link above. On the "Share-Online" page click the small-ish button that says "continue for free", and not the bit "DOWNLOAD FILE (regular download)" button in the banner ad (that I feel very silly for clicking several times).
Once the file "RK3188_ROOT for CX-919 FW0715 MOD by Everal.zip" has finished downloading, extract it to a temp location on your PC.
Make sure the Micro-USB port of the device is connected to a power source (either your PC or the provided AC adapter). The port doesn't seem to transfer data.
On the Agora device, go to "Settings", open the "USB" menu, and enable "Connect to PC". Without this the device wasn't recognised by my PC at all.
In "Settings", click on the "Developer options" menu, and tick "USB debugging".
Connect the provided blue Male-Male USB cable to a full-sized USB port on the device, and to a USB port on your PC. At this stage the device connects but is not recognised.
Open the Windows "Device Manager".
In the "Device Manager", expand "Other Devices", then right-click on "KHSTVQCDONA" and click on "Update Driver Software".
Click "Browse my computer for driver software".
Navigate to the "usb_drivers" folder of the software you extracted earlier, select it, and click "OK".
Click "OK". THIS DIDN'T WORK, stating that "Windows was unable to install your KHSTVQCDONA" and "Windows could not find driver software for your device".
[*] Open "Command Prompt", by right-clicking on it and clicking "Run as Administrator".
[*]C:
[*]cd RK3188_ROOT
[*]TPSparkyRoot.bat
At this point I see the following:
*---* VonDroid.com N101 II Root Tool based on work by sunnydavid *---*
--- Plug in your device, make sure debugging is enabled in Developer Options
--- This script will now copy files over to your N101 II
error: device not found
error: device not found
error: device not found
--- Reboot 1/3 - Press Space Bar once the device has rebooted
Press any key to continue . . .
error: device not found
error: device not found
error: device not found
--- Reboot 2/3 - Press Space Bar once the device has rebooted
Press any key to continue . . .
error: device not found
--- If the ID shows as 0/root then continue, otherwise CTRL+C to cancel and star
t over
Press any key to continue . . .
Click to expand...
Click to collapse
I terminate at this point
I've also done the following
Un-ticked "Verify apps over USB"
In "Security", ticked "Unkown sources", and un-ticked "Verify apps"
At this point I'm totally at a loss.
I had already started using the device initially, so I did a factory reset, but this hasn't helped at all.
Can you see anything I'm missing, or point me in the right direction?
Many thanks in advance! :good:
Ok So I know i messed around with many drivers installing and uninstalling before it worked. I Thought it was the last set that came with the Root method but I may be wrong.
Also I cant remember exactly now but I am pretty sure if you activate the connect to computer you bypass the ROM and connect to the SD card and the U SD. So that would not help when accessing the root files.
Try re-installing the drivers after connecting without the box checked in settings or try the ones from super oneclick 2.3.3 or even the pocket pC ones. you may also need to uninstall the device then reconnect to get a clean run at it. Windows likes hanging onto what it thinks is the best driver even when they don't work or are completely wrong.
Also I ran the batch file form within windows not in console, Just right clock to run as administrator.
I have just used it for a couple of weeks in Japan get let the Kids watch Aview (iView) and it worked a treat. Also the latest sixaxis updates made the controller even better than before. I can probably have a tool around with it later this week but I am busy before then so wont be able to help any. It can be done!
PM me if you cant find the drivers mentioned above I can email them to you.
Thanks for the quick response.
Can you just confirm that you were connecting using the blue Male-Male USB cable, and not a USB-Micro-USB cable?
When I connect to the Micro-USB port it doesn't see a device at all. It just seems to provide power.
When I connect with the blue Male-Male USB cable, unless I have "Connect to PC" ticked, it also doesn't see a device.
I don't have a micro-SD card installed, but that doesn't matter right?
I'll try those drivers you suggest. Thanks.
I am quite keen to figure out what is different but I cant access it for a couple of days sorry.
I definitely used a full sized USB to Connect, I may have used another one, and powered it from the Micro USB direct to power supply. If you are connecting it to the PC for power it may cause problems.
I know that you cannot access the recovery menu unless you are powering through the Micro USB only. Another thing I meant to mention in my original post. I may have posted it elsewhere.
SUCCESS! After I got the SuperOneClick software to forcibly install the drivers the device was then recognised and I could root the device.
Thanks. I'll write up the full instructions.
Excellent!! Thanks for writing up the guide.
OK, here is a full step-by-step guide for getting this to work:
Download "SuperOneClick" from Download.com (CNET). I can't post external links right now because I'm a new user, but it will appear if you do a Google search.
Extract SuperOneClick to a temporary location ("C:\temp" for the purpose of this installation).
Download the software from the link in the first post above. On the "Share-Online" page click the small-ish button that says "continue for free", and not the big "DOWNLOAD FILE (regular download)" button in the banner ad (that I feel very silly for clicking several times).
Once the file "RK3188_ROOT for CX-919 FW0715 MOD by Everal.zip" has finished downloading, extract it to a temp location on your PC (for the purpose of these instructions "C:\temp").
Make sure the Micro-USB port of the device is connected to a power source (ideally the provided AC adapter). The port doesn't seem to transfer data so don't connect it to your PC, unless you are using your PC as the power source. Basically as long as it's turned on, then continue.
On the Agora device, go to "Settings", open the "USB" menu, and enable "Connect to PC". Without this the device wasn't recognised by my PC at all.
In "Settings", click on the "Developer options" menu, and tick "USB debugging".
Connect the provided blue Male-Male USB cable to a full-sized USB port on the device, and to a USB port on your PC. At this stage the device connects but is not recognised.
Open "SuperOneClick"
In SuperOneClick click the "Advanced" tab, then click "Check Drivers".
When prompted to ask if you would like it to forcefully install drivers, click "Yes".
Click the "Install..." option when prompted by "Windows Security".
You should then hear the device connect, and disconnect, and see an message "Driver installed! Please reconnect your device", so click "OK".
Disconnect the blue USB cable from you PC, and then reconnect it. You should hear that the device has connected successfully (and it now appears as "Android Composite ADB Interface" in you "Device Manager" if you care to check.).
Open "Command Prompt", by right-clicking on it and clicking "Run as Administrator". (I found that running the .bat file directly failed because it didn't find the "adb" application)
C:
cd temp\RK3188_ROOT
TPSparkyRoot.bat
Follow the prompts from here. The application should reboot your device several times (if not something is wrong), after which point you press any ket to continue. From here everything was very straight-forward once the .bat file completed the device was then rooted.
Enjoy
I had to do things differently......
Used rocketchip_batch_tool_1.7 for drivers, superoneclick didnt do anything.
I ran the batch from the folder on my desktop.
For EACH device re-boot i had to RE CHECK connect usb on cx919 settings.
I got a few errors about no more storage on my device when it tried to copy some stuff, although i have the super user and i tried sixaxis controller which requires root and it worked. Not sure what the files were.
update:
Hmm and it seems SSL websites dont work now as well as Netflix or the Store.
ill have to try something else!
Update:
did a factory wipe. all seems ok now.
TeqTeq said:
OK, here is a full step-by-step guide for getting this to work:
Download "SuperOneClick" from Download.com (CNET). I can't post external links right now because I'm a new user, but it will appear if you do a Google search.
Extract SuperOneClick to a temporary location ("C:\temp" for the purpose of this installation).
Download the software from the link in the first post above. On the "Share-Online" page click the small-ish button that says "continue for free", and not the big "DOWNLOAD FILE (regular download)" button in the banner ad (that I feel very silly for clicking several times).
Once the file "RK3188_ROOT for CX-919 FW0715 MOD by Everal.zip" has finished downloading, extract it to a temp location on your PC (for the purpose of these instructions "C:\temp").
Make sure the Micro-USB port of the device is connected to a power source (ideally the provided AC adapter). The port doesn't seem to transfer data so don't connect it to your PC, unless you are using your PC as the power source. Basically as long as it's turned on, then continue.
On the Agora device, go to "Settings", open the "USB" menu, and enable "Connect to PC". Without this the device wasn't recognised by my PC at all.
In "Settings", click on the "Developer options" menu, and tick "USB debugging".
Connect the provided blue Male-Male USB cable to a full-sized USB port on the device, and to a USB port on your PC. At this stage the device connects but is not recognised.
Open "SuperOneClick"
In SuperOneClick click the "Advanced" tab, then click "Check Drivers".
When prompted to ask if you would like it to forcefully install drivers, click "Yes".
Click the "Install..." option when prompted by "Windows Security".
You should then hear the device connect, and disconnect, and see an message "Driver installed! Please reconnect your device", so click "OK".
Disconnect the blue USB cable from you PC, and then reconnect it. You should hear that the device has connected successfully (and it now appears as "Android Composite ADB Interface" in you "Device Manager" if you care to check.).
Open "Command Prompt", by right-clicking on it and clicking "Run as Administrator". (I found that running the .bat file directly failed because it didn't find the "adb" application)
C:
cd temp\RK3188_ROOT
TPSparkyRoot.bat
Follow the prompts from here. The application should reboot your device several times (if not something is wrong), after which point you press any ket to continue. From here everything was very straight-forward once the .bat file completed the device was then rooted.
Enjoy
Click to expand...
Click to collapse
Worked fine since then. All a sudden same prob, no Netflix no store. Wtf?
Just wanted to post an updated root method since i got one of these second hand last week
1. get the universal rockchip drivers, or the latest generic google ones. both worked for me on two different PC's. (including windows 8.1 x64)
2. Enable USB Debug mode in developer options. you know the drill.
3. the kogan device has a "USB" menu in settings, that has a 'connect to PC' setting. turn that on or ADB cuts out shortly after the system boots - turn it off after rooting for it to work normally.
4. connect PC to kogan dongle via the USB port next to the power LED. The other one doesnt work.
5. root with whatever method you want - i used kingo root which rooted it flawlessly first time.
6. have fuuuuun!
3 and 4 stumped me for days til i figured out what was going on. not something i'd ever encountered before, and likely unique to this device and why some people cant figure it out.

USB storage not showing up in windows

Anyone else with problems seeing the storage after plugging into PC? adb command works and device drivers installed. Found another forum where turning the usb from MTP to charging and back under developer options does the trick. I have a non stock ROM and seeing if fresh out of the box experiences the same thing.
I have the same issue and can't seem to figure out how to get it to work. My work around has been to use ES File Explorer and open Remote Manager.
Edit: I just plugged it in again to see what I can find. I turned off USB Debugging and Developer Options. Plugged in and pulled the notification bar down, there is an option to change USB Settings to Charging, Power Supply, File Transfers (this works), Photo Transfer and MIDI. Give it a go!
rramey23 said:
I have the same issue and can't seem to figure out how to get it to work. My work around has been to use ES File Explorer and open Remote Manager.
Edit: I just plugged it in again to see what I can find. I turned off USB Debugging and Developer Options. Plugged in and pulled the notification bar down, there is an option to change USB Settings to Charging, Power Supply, File Transfers (this works), Photo Transfer and MIDI. Give it a go!
Click to expand...
Click to collapse
I am running to the exact same problem.
I have tried with USB Debugging off AND on, still no go. I think there's a problem with installing the drivers. Whenever I check the device manager, it still says the drivers weren't installed. I have tried installing the Google drivers. What do we do?!
Kandydish said:
I am running to the exact same problem.
I have tried with USB Debugging off AND on, still no go. I think there's a problem with installing the drivers. Whenever I check the device manager, it still says the drivers weren't installed. I have tried installing the Google drivers. What do we do?!
Click to expand...
Click to collapse
Need to get the drivers to install first and foremost. Even with USB Debugging on, I'm still able to pull down and change from charge only. Those drivers are key. I had to restart my computer before it was able to take the install.
rramey23 said:
Need to get the drivers to install first and foremost. Even with USB Debugging on, I'm still able to pull down and change from charge only. Those drivers are key. I had to restart my computer before it was able to take the install.
Click to expand...
Click to collapse
I'm able to get to the pulldown and change the setting from charging to MTP. Every time I do that, I get a window showing that I'm installing the drivers for Nexus 6P. Then it completes. I can do this over and over again. In the device manager, there's a little exclamation mark by the Nexus 6P and says these drivers weren't installed Code 28. I have exhausted Google to no avail!
Anyone find a solution to this?
Kandydish said:
I'm able to get to the pulldown and change the setting from charging to MTP. Every time I do that, I get a window showing that I'm installing the drivers for Nexus 6P. Then it completes. I can do this over and over again. In the device manager, there's a little exclamation mark by the Nexus 6P and says these drivers weren't installed Code 28. I have exhausted Google to no avail!
Anyone find a solution to this?
Click to expand...
Click to collapse
You chose to install the drivers manually instead of having the system do it for you? Right click the yellow exclamation .. update drivers .. allow me to pick .. choose the download file location see what that gives you.
zosimov21 said:
You chose to install the drivers manually instead of having the system do it for you? Right click the yellow exclamation .. update drivers .. allow me to pick .. choose the download file location see what that gives you.
Click to expand...
Click to collapse
When I choose the location, I see a bunch of options. The most relevant ones are ADB Interface and Android Device. Under Android Device there are several more options such as Android Adapter Interface, Android Bootloader Interface, and the such; no mention of MTP.
Kandydish said:
When I choose the location, I see a bunch of options. The most relevant ones are ADB Interface and Android Device. Under Android Device there are several more options such as Android Adapter Interface, Android Bootloader Interface, and the such; no mention of MTP.
Click to expand...
Click to collapse
Did you already download the google USB drivers?
Should just be able to choose the android_winusb.inf driver. It should allow MTP
zosimov21 said:
Did you already download the google USB drivers?
Should just be able to choose the android_winusb.inf driver. It should allow MTP
Click to expand...
Click to collapse
I have downloaded them. How do I specifically choose just that file? When I go through updating the driver, it asks for a folder location.
Go to dev options, switch the USB from ptp back to mtp and it works for me
xxsashixx said:
Go to dev options, switch the USB from ptp back to mtp and it works for me
Click to expand...
Click to collapse
Tried. Keeps trying to install the MTP drivers and it won't go through.
I was having the same issue with my computer not detecting the my phone storage but then i remove the drivers from my samsung in the device manager and then right away detect my nexus 6p, no only i can see the storage but if i select how i want to connect (MTP, File trinsfer) it will change the connection type and folder
MTP - shows the pics folder
File transfer - it shows the storage
Sweet
bartendersimon said:
I was having the same issue with my computer not detecting the my phone storage but then i remove the drivers from my samsung in the device manager and then right away detect my nexus 6p, no only i can see the storage but if i select how i want to connect (MTP, File trinsfer) it will change the connection type and folder
MTP - shows the pics folder
File transfer - it shows the storage
Sweet
Click to expand...
Click to collapse
I don't have any other drivers from any other devices. This is a clean install of Windows 8.1. I've only tried connecting my 6P, my OG 6, and my 9. All have the exact same problem.
Kandydish said:
I don't have any other drivers from any other devices. This is a clean install of Windows 8.1. I've only tried connecting my 6P, my OG 6, and my 9. All have the exact same problem.
Click to expand...
Click to collapse
You might wanna try installing Huawei Drivers and see if that help
HiSuiteSetup_2.3.55.1.zip
http://download-c.huawei.com/downlo...loadId=16205&version=90864&siteCode=worldwide
bartendersimon said:
You might wanna try installing Huawei Drivers and see if that help
HiSuiteSetup_2.3.55.1.zip
http://download-c.huawei.com/downlo...loadId=16205&version=90864&siteCode=worldwide
Click to expand...
Click to collapse
I installed that application and I was able to see my device, the apps, the contacts, everything. EXCEPT I wasn't able to access the device from Windows Explorer which means I am not able to transfer files.
Kandydish said:
I installed that application and I was able to see my device, the apps, the contacts, everything. EXCEPT I wasn't able to access the device from Windows Explorer which means I am not able to transfer files.
Click to expand...
Click to collapse
So when you change the option in the phone from charging to file transfer, did you check the device manager to see if there any unknown device showing somewhere?
bartendersimon said:
So when you change the option in the phone from charging to file transfer, did you check the device manager to see if there any unknown device showing somewhere?
Click to expand...
Click to collapse
Changing it from charging to MTP shows a MTP device in Manager with a yellow exclamation mark next to it. When looking into the details, it says that no drivers are installed. When I try "Updating Drivers", it says "Windows failed to install drivers. Code 28" or something along those lines. Code 28 MEANS that Windows failed to install drivers.
Thanks for nothing Microsoft.
Nexus 6p Connection to PC Issue - This Helped!
I had similar problems with PC not recognising my Device. I found http://www.technobuzz.net/install-google-nexus-6p-usb-drivers/ which helped me solve my issues.
1. Downloaded and installed the Huawei Nexus 6p drivers. This installed a Huawei Task Manager which connection to pair was still not recognisable.
2. Deleted old drivers (acer, samsung, htc) from' Device Manager'. This actually helped PC recognise my device which showed up in the Device Manager>Other Devices>Nexus 6p, also in PC interface but once moved off charging to MTP, computer didnt recognise device.
3. Downloaded and installed the adb/fastboot installer. Followed instructions till step 10. My screen didn't show anything like Andoid ADB interface, it displayed MTP file install, which I installed. Just remember to refresh in My PC interface when changing over from charging to MTP, sometimes Nexus 6p will be hidden.
4. Uninstalled the Huawie Task Manager.
This has solved my problem with PC and Device connection. The instructions given are from what I can recall of the process I went through.
Credit to Sidharth Rathore from Technobuzz for this solution.
Hope this helps.
Later.
p.s. I have a windows 10 laptop if this helps.
bartendersimon said:
I was having the same issue with my computer not detecting the my phone storage but then i remove the drivers from my samsung in the device manager and then right away detect my nexus 6p, no only i can see the storage but if i select how i want to connect (MTP, File trinsfer) it will change the connection type and folder
MTP - shows the pics folder
File transfer - it shows the storage
Sweet
Click to expand...
Click to collapse
I was having the same issue until I uninstalled some other debugging drivers I had installed. So I would recommend crawling through your installed apps for any other android usb drivers and uninstalling them if you still have this issue.
Working on mine right now. Found that USB 3.0 ports will not recognize device. Once plugged into a 2.0, it is recognized. Might help your issue

Resources