Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!
asylumxl said:
Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!
Click to expand...
Click to collapse
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?
Gizmoe said:
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?
Click to expand...
Click to collapse
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.
asylumxl said:
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.
Click to expand...
Click to collapse
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.
Gizmoe said:
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.
Click to expand...
Click to collapse
I'll give that a go, that's the only thing I haven't tried so far. It's just bizarre it shows in every other mode. The device is there in the Device Manager under hidden, but doesn't actually show up as connected. Thanks .
Related
It seems like I go through this every damn time I get a new Android device, so you'd think I'd have figured it out by now, but I haven't.
How the heck to I get ADB working for this device? It's not being recognized by the "adb devices" command right now. As far as I know, I've got the drivers installed (at least, I could communicate via fastboot). I don't know what else I need to do, and would appreciate any help.
How did you get install the drivers? If you haven't done so, you can just grab the drivers from here: http://forum.xda-developers.com/showthread.php?t=1992345
Stryder5 said:
How did you get install the drivers? If you haven't done so, you can just grab the drivers from here: http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
Yes, that's where I got the drivers (and that's how I got fastboot working).
I've taken the drastic step now of uninstalling the entire SDK thing and am currently re-installing it. We'll see how that goes.
EDIT: yeah, "adb devices" still gives nothing at all.
You need to turn it on first but Developer Options are hidden in Settings. Go into About phone and tap the build version. After 7 times you will have access and you can turn on USB Debugging
chinly43 said:
It seems like I go through this every damn time I get a new Android device, so you'd think I'd have figured it out by now, but I haven't.
How the heck to I get ADB working for this device? It's not being recognized by the "adb devices" command right now. As far as I know, I've got the drivers installed (at least, I could communicate via fastboot). I don't know what else I need to do, and would appreciate any help.
Click to expand...
Click to collapse
do you have usb debugging on? its under development under settings. to make it appear, you need to press the about phone 7 times or so. http://www.androidcentral.com/how-enable-developer-settings-android-42
^^what the user said above. he beat me to it
0.0 said:
do you have usb debugging on? its under development under settings. to make it appear, you need to press the about phone 7 times or so. http://www.androidcentral.com/how-enable-developer-settings-android-42
^^what the user said above. he beat me to it
Click to expand...
Click to collapse
While this was, admittedly, once my problem back in the early days of android, it's not the problem this time. USB debugging is on.
EDIT: I've also reconfirmed that fastboot is still working after the whole re-installation thing.
Anyone have any other ideas? Is it correct that when I plug the phone in, it's detected add an MTP device?
chinly43 said:
Anyone have any other ideas? Is it correct that when I plug the phone in, it's detected add an MTP device?
Click to expand...
Click to collapse
thats very odd...perhaps run the android sdk and check for any updates for the drivers and whatever else is needed
0.0 said:
thats very odd...perhaps run the android sdk and check for any updates for the drivers and whatever else is needed
Click to expand...
Click to collapse
That's all I can suggest as well, although I can't see what the issue could be
Yer try installing the SDK and downloading the "Google USB Drivers" from there to see if it helps.
Sent from my Nexus 4 using Tapatalk 2
Here try this. It's from the sdk. I just zipped it. https://www.box.com/shared/7sutkummukh4pup0rwoi
Sent from my Nexus 7 using Tapatalk 2
You can just get the windows executable from Google, r21
http://dl.google.com/android/installer_r21-windows.exe
Thanks, everyone who's been reading/trying to help. Unfortunately, it's still not working.
People suggesting the .exe installer - that's how I've installed it each time. Twice now I've uninstalled/reinstalled the SDK. When installing, I choose the SDK tools, SDK platform tools, the 4.2 API (which is probably unnecessary, right?), and the Google USB driver. Each time, ADB has worked *in general*, but will not recognize this device (via the "adb devices" command).
Here's how things are going right now. When I first plug the phone in (with debugging on), if it's not currently installed as a device then it automatically self-installs and shows up as an "mtp" device. I try ADB, doesn't work. I then go in and manually install the drivers found in various places around this board. When I do this, it no longer appears as MTP. This is weird, though, and I didn't notice this last night - when I look at the list of devices in Device Manager in Windows, the category it falls into is "ASUS Android Devices", under which it's listed as "Android Composite ADB Interface", and it still doesn't work.
Something seems wrong about it being listed as ASUS, though. I wonder if all these current difficulties are a result of the problems I had getting my Transformer Prime to work with ADB? If anyone sees anything above that looks like I'm doing something wrong, let me know; I think the next thing I'm going to try is doing this whole process on a fresh computer here at work that's never been exposed to android at all, see how that goes. I'll check back in after I do that.
Have you tried these drivers?...
http://forum.xda-developers.com/showthread.php?t=1992345
EddyOS said:
Have you tried these drivers?...
http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
I have, and it still doesn't work on my laptop. However...
It's working! On a shared computed at work that had never had *anything* android-related installed before. Went through the same procedure I did on my own computer, so the problem is with my laptop, I guess. Which I'm more okay with than it being a problem with the phone. I guess I need to more thoroughly remove everything from the laptop, maybe?
An update:
I DO. NOT. UNDERSTAND. why this worked; I haven't changed the drivers or anything on the laptop itself. On a whim, I changed the device type on the N4 from "media device" to "PTP device" and suddenly ADB is recognizing it on the computer where it's never worked. Should I have expected that?
chinly43 said:
An update:
I DO. NOT. UNDERSTAND. why this worked; I haven't changed the drivers or anything on the laptop itself. On a whim, I changed the device type on the N4 from "media device" to "PTP device" and suddenly ADB is recognizing it on the computer where it's never worked. Should I have expected that?
Click to expand...
Click to collapse
I have to do that to my Nexus 7 before ADB will recognize it, so you're not alone there.
Just curious, what brand phone did you have before? If it was a samsung and you had all the samsung drivers and what not installed still, this could be causing the problem. My cousin couldn't get adb to recognize his device and we finally discovered the samsung software was conflicting in someway. He uninstalled it all and adb worked like a charm.
I had the same problem, here's what you need to do. When you plug it in, change the settings from MTP to Camera for USB settings. I don't know why, but you need to do it.
dcarpenter85 said:
Just curious, what brand phone did you have before? If it was a samsung and you had all the samsung drivers and what not installed still, this could be causing the problem. My cousin couldn't get adb to recognize his device and we finally discovered the samsung software was conflicting in someway. He uninstalled it all and adb worked like a charm.
Click to expand...
Click to collapse
I've got four other android devices that all worked (simultaneously, at that): T-Mobile/HTC G1, Nook Color, T-Mobile/HTC G2, and an Asus Transformer Prime.
Hi folks,
I really hope someone can help me here. My TF300T is currently rooted and unlocked with the lates CM 10 (4.2.2) build. I am having some issues with reboots since upgrading to 4.2.2 and I would like to change the ROM. I am also trying to flash the upgraded TWRP recovery but unfortunately I am unable to do this. When I boot the TF300 into the menu where you have to select the USB icon normally this would load the ADB driver but my PC comes up as 'USB device not recognized'. I've tried this from two different PCs' with the same outcome. I won't be able to flash recovery or ROM unless I get this sorted. I should note that when I connect the TF300 while it is booted the PC recognizes it no problem. It also works in USB debugging mode so I'm very confused as to why it won't work from the boot menu. I've tried manually installing the drivers, installing Asus PC Sync and also re-installing SDK tools; all to no avail. Any ideas on how to fix this would be greatly appreciated. Thank you!
vipergrm said:
Hi folks,
I really hope someone can help me here. My TF300T is currently rooted and unlocked with the lates CM 10 (4.2.2) build. I am having some issues with reboots since upgrading to 4.2.2 and I would like to change the ROM. I am also trying to flash the upgraded TWRP recovery but unfortunately I am unable to do this. When I boot the TF300 into the menu where you have to select the USB icon normally this would load the ADB driver but my PC comes up as 'USB device not recognized'. I've tried this from two different PCs' with the same outcome. I won't be able to flash recovery or ROM unless I get this sorted. I should note that when I connect the TF300 while it is booted the PC recognizes it no problem. It also works in USB debugging mode so I'm very confused as to why it won't work from the boot menu. I've tried manually installing the drivers, installing Asus PC Sync and also re-installing SDK tools; all to no avail. Any ideas on how to fix this would be greatly appreciated. Thank you!
Click to expand...
Click to collapse
When you get the USB device not recognized, go into device manager locate the device on the list right click and then click on update driver. When it asks you selecte that you want to find the driver files on the computer, then select the option to look at the list of drivers. Once in the list there should be a driver for ADB try installing it and see if it works. That's how I got my adb to work while on recovery.
jgaf said:
When you get the USB device not recognized, go into device manager locate the device on the list right click and then click on update driver. When it asks you selecte that you want to find the driver files on the computer, then select the option to look at the list of drivers. Once in the list there should be a driver for ADB try installing it and see if it works. That's how I got my adb to work while on recovery.
Click to expand...
Click to collapse
Thanks but that still didn't work for me. What exact driver did you use? Thanks!
Don't remember the name exactly, but from what I can see right now on device manager these are the details on the driver:
ASUS Android ADB Interface
Driver Provider: ASUSTek Computer INC.
Driver Date: 7/17/2012
Driver Version: 4.0.0.5
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
Also, have you tried removing all previous ASUS drivers and trying to install them again?
jgaf said:
Don't remember the name exactly, but from what I can see right now on device manager these are the details on the driver:
ASUS Android ADB Interface
Driver Provider: ASUSTek Computer INC.
Driver Date: 7/17/2012
Driver Version: 4.0.0.5
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
Also, have you tried removing all previous ASUS drivers and trying to install them again?
Click to expand...
Click to collapse
Thanks again. I will give this another go later and see what happens...
Any luck?
jgaf said:
Any luck?
Click to expand...
Click to collapse
I haven't had the opportunity to try it again just yet. I plan to do this tomorrow night on my nightshift in work. I'll let you know then. Thanks for asking
Tried tonight again and still no luck. I know the driver installed on this machine definitely works because its the same one that worked last week when I tried it. Oddly, the ADB driver picks up ok when I'm in the OS with debugging on but I don't think i would be able to flash whilst logged on to the OS. This is concerning because the CM10 ROM 4.2.2 which I have installed a the moment is firing up random reboots. I know it's still in experimental stage and I'm not complaining but it would be nice to change my ROM when needed. Below is a couple of screenshots of the problem I am having.
I had a similar problem my adb worked flawlessly when the OS was running, but it wouldn't get recognized when in recovery (fastboot worked too). So, what I wrote earlier solve my problem. Sucks it didn't work for you. Anyways do you have a recovery installed? If you do why can't you use that one? Also, I'm pretty sure you can install recovery when the OS is running, even from android terminal emulator in the pad.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Thanks again. I did do a backup thankfully and currently it is restoring. I will try to see after restoring the backup if it works. Another method I have found to repair the bootloader is the NVFLASH method, although this does scare me a little! I would be very interested in trying those drivers you have as mine are older but so far I have been unable to find anything newer, despite extensive searching. :crying:
Thanks for your help thus far! :good:
Looks like I'm finally getting somewhere. I decided that I would try connecting directly to the TF300 instead of through the keyboard dock and oddly this worked. The driver is now loading correctly and I am able to flash again! Now to choose a JB ROM... :good:
I encrypted my phone without realizing that CWM did not support encrypted devices. To fix this I was going to install TWRP since it does support it. My phone is working correctly with adb but I cannot get fastboot to find the device at all. This is making it so I cannot install TWRP on my phone now. Anyone have any ideas or suggestions? Thanks for any help.
You can install the recovery directly through the phone through Goomanager, but the fact that your computer doesn't recognize the device in fastboot is an issue I feel needs to be addressed. Goomanager solves the problem of the recovery, but I'm not sure about the fastboot issue.
Sent from my Nexus 4 using XDA Free mobile app
mikeric said:
I encrypted my phone without realizing that CWM did not support encrypted devices. To fix this I was going to install TWRP since it does support it. My phone is working correctly with adb but I cannot get fastboot to find the device at all. This is making it so I cannot install TWRP on my phone now. Anyone have any ideas or suggestions? Thanks for any help.
Click to expand...
Click to collapse
I had this issue on a different device. To solve it I went into control panel, device manager. Then look for the usb device that had an exclamation mark on it (with your device plugged into the usb port). Right click on it and update driver software. Then go to browse my computer and choose, let me pick from a list...... Pick the android composite adb interface. It'll ask you if your sure, just say yes
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I had this issue on a different device. To solve it I went into control panel, device manager. Then look for the usb device that had an exclamation mark on it (with your device plugged into the usb port). Right click on it and update driver software. Then go to browse my computer and choose, let me pick from a list...... Pick the android composite adb interface. It'll ask you if your sure, just say yes
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you, thank you, thank you. This enabled MTP mode for me in about 3 seconds on my Windows 8 PC. I had tried using Wug's toolkit both automated and manual even disabling enforcement of digital signatures on driver installation and had also installed latest ADK and Google drivers to no avail (all that got me was connection in camera mode and ability to see only DCIM). I don't remember having this kind of trouble last time I decided to play with my Nexus 4. Not sure if I was using my old Windows 7 machine then or if there is a conflict with the other drivers on my machine (I have recently flashed both Motorola and Samsung devices too). I wish you had posted a couple of hours sooner lol.
howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.
Also this is the 2012 N7
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
demkantor said:
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
Click to expand...
Click to collapse
I don't understand how I'm supposed to get fastboot working since I was never able to enable debug mode on the device in the past let alone now that it has nothing installed. And from what I can understand from the instructions I need the drivers to be installed after I plug in while under debug mode for the sdk to work.
I attempted to install the nexus 7 driver from here: http://support.asus.com/download.aspx?SLanguage=en&m=Nexus+7&os=32
However it looks like I already have the files on my computer from a previous attempt with Skipsoft's Android toolkit?
Because of this I'm unsure of how to move forward with this fastboot business.
fastboot doesn't need debugging on or an os installed, just a functional bootloader
You will probably need to manually update the drivers yo the proper ones
I see, how do I go about manually installing this driver then? I'm assuming I need to go through some sort of windows device tree? Or can I just extract a file somewhere?
You can download usbdview (just search Google for a free download) to see what driver is selected when you plug in your tab easily
Or you will need to go into device manager and select to manually update the drivers, don't allow windows to select but manually choose it
There are loads of instructional videos on YouTube for you if needed
I know this is a super late response, but I never managed to get around to trying to find out how to do a manual install. Just tried today using the Nexus Root Toolkit v.1.9.9. I still can't figure out how to manual install the driver because my issue is that windows doesn't recognize anything is plugged in, and all of these guides do state that I should have had usbdebugging checked. I can't seem to find a specific guide that correlates to setting fastboot up exclusively like you mentioned.
Also, using usbdeview like you said I could see that I have installed a google nexus adb interface, a google galaxy nexus adb interface, as well as the mtp usb driver.
Sorry for all the handholding, but this really is an issue that I've never have encountered and I can't seem to manage.
Hey again
There is a fastboot guide in the first post I linked you to
If you can't get fastboot to recognize device in bootloader mode it is possible the USB port is broken, but more likely an issue with drivers, cord or PC
So try a new USB cable, or a different PC
Try try again with drivers, uninstall and reinstall
Unfortunately this type of trouble shooting is hard to do without device in hand
A little history. I have rooted several other brands of tablets, so I am not new at this. Even thogh I am not a programmer by any stretch of the word. My Pixel C drivers work fine in normal mode, I can see the storage as a drive, no problem. I can transfer files back and forth. But, when I boot it into fastboot mode, it will not see it. It is listed as an unknown device in the device manager of Windows 10. I have tried to install the drivers, but they say not found. And this is the driver from the Android website. I'm at my wit's end. I'm not a newbie at windows, either. But, I need suggestions to get this to work. BTW this is the latest version of Windows 10 1903. And I have tried every solution I have found on google and on this website. TIA
Ok, fixed that by selecting a driver from a list of drivers so now I have ADB drivers. I have another issue which I will do some research on if not.....I'LL BE BACK.
What is your goal?
Do you want to use adb or fastboot?
Is the bootloader unlocked, have you enabled usb debugging in the developers menu (hidden) etc
Ok, as I said before, I figured it out. And yes, the bootloader was unlocked and yes USB debugging was enabled. I got everything
working and I am now running Android 9. Thanks for the reply, though.
Toolcrazy said:
Ok, as I said before, I figured it out. And yes, the bootloader was unlocked and yes USB debugging was enabled. I got everything
working and I am now running Android 9. Thanks for the reply, though.
Click to expand...
Click to collapse
Missed that! (you mentioned another issue)
Well done etc