Related
Okay, I have a permarooted MT4G with S=Off, and I want to use the gfree method to unlock my SIM and get the universal CID while I'm still on the stock kernel. All of the guides I see for that push the gfree files using the ADB.
Problem: I cannot get the Android SDK to recognize my MyTouch 4g. (SEE UPDATE)
I followed this guide http://forum.xda-developers.com/showthread.php?t=834748 to try and set up the ADB to no avail. This is what I did:
-- Downloaded the SDK, booted it up, let it update. Booted it up again, let it update EVERYTHING (took like 30 minutes) again. It has no more updates to install.
-- I tried adding adb as an environmental variable in windows, but the command prompt, no matter where I start it from, does not recognize 'adb' as "an internal or external command, operable program, or batch file." (works now)
-- The HTC Drivers that came with my device have been installed on my computer. So, I uninstalled them, only to have windows reinstall them as soon as I plug the device in (I'm running Windows 7 x64 home edition, Build 7601).
I tried going here http://forums.t-mobile.com/t5/HTC/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017 and using their technique, no dice. My computer has the exact same drivers as when I started, and I have a digital paperweight of a SDK. (see update)
UPDATE: I now have a working ADB (big thanks to TrueBlue_Drew and his guide for us noobs) that recognizes my MT4G, but I have another issue:
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct windows to the usb drivers I downloaded from the both of the guides I've used, but windows wouldn't accept either one. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since adb is working? Any help on that end would VERY MUCH appreciated.
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
neidlinger said:
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
corruptsmurf said:
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
Click to expand...
Click to collapse
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
So close, yet...
TJBunch1228 said:
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Actually no, adb.exe isn't It has a .txt named "Adb has moved," not really sure how to proceed from here; I downloaded the SDK that was in the topic I linked above, and just allowed it to update. More below, and thanks for the response.
jdkoren said:
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
Click to expand...
Click to collapse
Yeah, the problem is that my PC doesn't list any errors when I plug it in. BUT BIG NEWS, I followed the ADB for noobs guide (http://forum.xda-developers.com/showthread.php?t=928370), and I realized, as I said above, that my adb.exe file was nowhere to be found, so I used the one from the noob guide, and it could recognize my device in ADB. BUT it could not recognize my device in fastboot, so after much frustration, I decided to uninstall the drivers and reinstall using pda.net. Whatever it did, it worked, because adb and fastboot both show my serial number under devices. Thanks to the both of you for your help.
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the Misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct it to the usb drivers listed in the both of the guides listed above, but windows wouldn't have it. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since I can use adb anyhow? Any help on that end would VERY MUCH appreciated.
I'm Italian, sorry for my English.
A few days ago I unlocked the bootloader via Toolkit, rooted and flashed the TWRP recovery _.
But I had hard difficulty:
After driver installed, I unlocked bootloader, enable debugging and then NOTHING!
In practice, the N7 was recognized by windows 7 64bit only in FastReboot mode ..
I tried in every way possible, deleted and reinstalled the driver 50 times, restored windows to a previous point, installed the drivers manually tried without toolkit, but how ADB just do not want to know.
For hours I was still with the bootloader unlocked but without root, until came to my rescue a friend with another notebook but same windows 7 64. Load the Toolkit, install the drivers and everything goes perfectly, I do everything in 5 minutes.
On my laptop there is always the issue driver ADB, in the future I still need my PC recognized the N7 in ADB, how can I do?
One thing that I think is not well understood is that there is no "Generic Class Driver" for ADB nor for fastboot...
... even though the very driver that works for one mode (or phone/tablet device) may be perfectly fine with a different device. The wire protocol for both fastboot and adb are extremely simplistic.
So, what that means is that if the Hardware ID used by the USB device endpoint registers on the bus with a different VendorID/ProductID, Windows will (correctly) not use a previously-installed ADB driver, or previously installed fastboot driver - even though they would probably work just fine.
Here is an example. The Nexus 7 registers the following Hardware ID when ADB debugging is turned on in the OS:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
On the other hand, if you are using TWRP, it's adbd daemon shows up on the PC as:
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
This means that you might need to install a different driver for using the ADB with the OS, and a different driver for ADB under TWRP - even though it is exactly the same hardware on the other end of the cable! In the absence of a generic class driver for a given USB endpoint, Windows tries to match drivers in it's local (& internet) database based on this VID/PID pair.
If you have a look at the [ADB/FB/APX Driver] Universal Naked Driver 0.72 thread - and download it and have a look at it's included "android_winusb.inf" file - you will see literally hundred of different VID/PID pairs in the driver's android_winusb.inf file in the installer package, corresponding to many hundreds of phones/tablets. Same driver with hundreds of devices listed as compatible.
In the past I recall taking the Google (SDK) USB driver, and manually editing into place matching VID/PID pairs for a HTC phone into the .inf file. It worked perfectly; I probably flashed that phone hundreds if not thousands of times using the Google Driver (My PC is a Windows 7 Pro x64 machine btw).
Anyhow, I have pulled this stunt twice now - once editing the .inf file for the Google Driver, and I did it once with the Universal Naked driver too. You can choose which driver you want to start with.
If you want to give it a roll, you can start with any of those three drivers:
- Google (SDK) USB driver
- XDA "Universal Naked" driver
- Asus Nexus 7 USB Driver (Look under Download)
Note that since you are using W7 x64, make sure that you add each new entries to the .inf file twice - once in the ".NTx86" section, and duplicated again in the ".NTamd64" section. When editing .INF files, make sure to use an editor which preserves simple text file formatting - use "notepad", not "wordpad"
If you want a reference for what values to use, see the bottom end of this post. You should see exactly these same values in your Device Manager, however.
Note that if you see the device show up in the Device Manager as being correctly identified and marked as "working normally" - but it doesn't work - you should probably remove that driver and re-install from a different driver package.
This would certainly be the case for any drivers you saw associating with VID/PID pairs that look like:
VID_18D1&PID_4E40 bootloader/fastboot
VID_18D1&PID_4E41 single adb
VID_18D1&PID_4E42*&MI_01 composite adb
VID_0955&PID_7330 avx mode
VID_18D1&PID_D001 adb in TWRP (maybe CWM too, I didn't check)
That's a lot to throw at you, especially with Italian <=> English in the mix.
Feel free to ask questions.
bftb0
Hello,
I tried to follow your advice but I have not solved.
I'll explain what I did, so you can correct me.
-Uninstalled previous drivers (from device manager, control panel)
-Restart the PC
-Modified the inf file. Package Asus Nexus 7 USB driver (ntx86 and NTamd64 sections) attach screenshots
-Linked N7 (usb debugging actived)
-Found portable device in device manager, update drivers manually from the Nexus 7 Asus USB drivers
I tried to change also too XDA "Universal Naked" driver by following the same procedure.
I tried to create another account on my pc, but no ADB!
View attachment 1734997
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
stonebear said:
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Use "Google USB drivers" you get after you install from here http://developer.android.com/sdk/index.html
Its drivers work with 4.2.2
I got 4.2.2. rooted with ADB working now via only this and no other method
No problem with adb in 4.2.2... I tested yesterday (no need psw too...)
stonebear said:
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Marco16V said:
-Found portable device in device manager, update drivers manually from the Nexus 7 Asus USB drivers
Click to expand...
Click to collapse
Is this the only device which shows up in the device manager? The "Portable Device" is either the MTP or PTP endpoint - not ADB. The latter (adb) should show up elsewhere in the device manager.
You should certainly NOT be trying to install fastboot/adb driver on MTP/PTP endpoints!
I think perhaps I am not understanding because I am guessing at certain details.
Q1) Do the drivers appear to install correctly?
Q2) When you have the N7 in the corresponding mode - whether or not you observe (device manager) "working normally" or "unknown device" - do you see the following Hardware IDs showing up in the device manager?
Bootloader Fastboot Mode:
USB\VID_18D1&PID_4E40&REV_0000
USB\VID_18D1&PID_4E40
OS adb:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
TWRP adb (Possibly also CWM adb, I haven't checked it) :
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
Q3) I presume you went through the same install sequence on your PC that succeeded on the other laptop - in the event the problem is a hardware problem, did you try a different cable or USB port on your PC?
Q4) When you remove drivers, are you requesting that the drivers be removed from the PC?
The 4.2.2 authentication issue might be an issue (although I suspect this is a adb program version issue, not a driver version issue. In any event, it wouldn't effect the behavior of adb in TWRP/CWM.
Sorry for all the questions.
bftb0 said:
Is this the only device which shows up in the device manager? The "Portable Device" is either the MTP or PTP endpoint - not ADB. The latter (adb) should show up elsewhere in the device manager.
You should certainly NOT be trying to install fastboot/adb driver on MTP/PTP endpoints!
I think perhaps I am not understanding because I am guessing at certain details.
Q1) Do the drivers appear to install correctly?
Q2) When you have the N7 in the corresponding mode - whether or not you observe (device manager) "working normally" or "unknown device" - do you see the following Hardware IDs showing up in the device manager?
Bootloader Fastboot Mode:
USB\VID_18D1&PID_4E40&REV_0000
USB\VID_18D1&PID_4E40
OS adb:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
TWRP adb (Possibly also CWM adb, I haven't checked it) :
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
Q3) I presume you went through the same install sequence on your PC that succeeded on the other laptop - in the event the problem is a hardware problem, did you try a different cable or USB port on your PC?
Q4) When you remove drivers, are you requesting that the drivers be removed from the PC?
The 4.2.2 authentication issue might be an issue (although I suspect this is a adb program version issue, not a driver version issue. In any event, it wouldn't effect the behavior of adb in TWRP/CWM.
Sorry for all the questions.
Click to expand...
Click to collapse
When the drivers are not installed and I connect to pc N7, is only recognized as a portable device, then later recognized as Google Nexus 7.
To install the drivers (modified as described) I click reinstall driver, then later recognized (if connected to pc in android mode, with usb debugging actived) as Android Device in another voice, ADB interface. But is not recognized by the toolkit under adb devices, and even when I try using cmd.
1-When I install the drivers. seem to be installed correctly.
2-Sorry, where can I find Hardware IDs in Device Manager? What is the difference between OS adb and TRWP adb?
3 - In other pc (with same N7, same cable, same driver, same toolkit) I had no problems. I tried to change only the USB port.
4-I uninstall the driver from device manager (uninstall voice) and ask to be also uninstalled software from the PC
In some Italian forum, I found people with the same problems.
Solved by formatting PC. I would not do that ...
Thanks for your help, sorry for my English and my limited skills
AW: No ADB mode, driver issue?
Try to download the latest Android SDK and try to connect with that adb version. Adb with version < 1.0.31 will not work correctly with Android 4.2.2.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Try to download the latest Android SDK and try to connect with that adb version. Adb with version < 1.0.31 will not work correctly with Android 4.2.2.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I tried sdk but I have not solved.
I use Android 4.2.1. I'm having problems with the update! I can not update OTA (N7 stuck under the impending reboot). I also tried to download the zip file to upgrade the memory and flash it from recovery but the installation is not completed (error 7 build.prop).
I also tried to flash the factory image 4.2.1 (keeping userdata) and start again. Nothing, same mistakes!
Too many problems!
Marco16V said:
2-Sorry, where can I find Hardware IDs in Device Manager?
Click to expand...
Click to collapse
(Note I attached some pictures below)
From the Device Manager:
- Select the Device in question by right-clicking. Choose "Properties"
- A window with three tabs will appear: General, Driver, and Details. Select Details
- The "Property" combo-box-selector has 20 or 30 items - the 2nd one in the list is Hardware Ids. I attached two pictures from Win7-Pro-x64 (below)
But note as I said before: You should NOT be seeing the ADB endpoint under "Portable Devices" - if ADB Debugging is turned on in the OS, you should see it under "Android Phone" or something similar. In any event, the hardware Ids will identify it exactly
Marco16V said:
What is the difference between OS adb and TRWP adb?
Click to expand...
Click to collapse
Well, as far as the behavior of the USB driver on the PC, almost nothing. Unfortunately - for better or for worse - both TeamWin (TWRP) and CWM authors put their ADB interface on the bus with the VID/PID pair of USB\VID_18D1&PID_D001, whereas the OS puts all its USB interfaces on 18D1/4Exx.
So, even if you get a driver installed for the OS "adb" mode (say by using the Google SDK USB driver or the Asus Nexus 7 driver), it won't work for the custom recovery... unless you fix up the driver installer package to have the matching VID/PID pairs (18D1/D001) in the .INF file for that driver.
I think folks find this confusing - they think, "wait, I have a ADB driver installed" - why does it not work?
OK, there are a couple more things to try (at least before I give up). Roughly they try to answer these questions:
Q1) Is this a toolkit issue, or a driver issue?
Q2) Is it a prior driver you installed that you are not observing that is causing the problem?
The first one (Q1) is easiest to diagnose: when your PC Device Manager indicates that a device is "working normally" - AND THE VID/PID ID MATCHES WHAT YOU SHOULD EXPECT FOR THE MODE THE TABLET IS IN (regular OS, recovery boot, fastboot mode), can you communicate with the device from the Windows command line? e.g.,
Code:
C:\foo> cd C:\blahblah\sdk-platform-tools-directory
C:\blahblah\sdk-platform-tools-directory> fastboot devices
or
C:\blahblah\sdk-platform-tools-directory> adb devices
If you can communicate with the tablet from the command line - your device ID will be printed by the above commands, then you don't have a driver problem at all - there is something screwy about the way your toolkit is installed.
OK, Q2 -
When Windows installs a driver, it caches it into a kind of database. I suppose it is possible that a prior driver installation might be causing trouble. You can observe - from the device manager - all the drivers that are installed - even for devices that are not currently connected to your computer.
This is done by setting the "devmgr_show_nonpresent_devices=1" environment variable. It can be done semi-permanently this way, or for a single invocation of the device manager this way..
See the third image attached (devmgr-all-devices.jpg ) - it is my computer in that "show all devices" mode. See all that rubbish in there? It's from other Android devices (HTC, Samsung, etc).
You can walk through each one of those - even the devices that are not currently attached - and inspect the VID/PID pair to see if they happen to match the values that you are expecting to see for the different operating modes on the Nexus 7. I'll leave it up to you whether you want to do this or not; it is a bit tedious. Just don't start deleting drivers willy-nilly if you don't know what they are associated with.
Marco16V said:
Thanks for your help, sorry for my English and my limited skills
Click to expand...
Click to collapse
I am understanding everything you are saying - and your english is far better than my italian
good luck!
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
Which OS are you using (Windows, Mac, Linux)?
Elrondolio said:
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
Click to expand...
Click to collapse
It's the latest SDK.
bsara said:
Which OS are you using (Windows, Mac, Linux)?
Click to expand...
Click to collapse
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Hope this helps someone. Cheers!
feered said:
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Click to expand...
Click to collapse
I had the same issue on Ubuntu. You need to run ADB with sudo...why? I have no idea...but I found a post suggesting it on StackOverflow and it worked...so I'm not questioning it.
Before doing anything below, have you installed adb via apt-get? If so, remove it and just put a link to your SDK manager adb and fastboot in a folder included in your PATH or add the directory to the path, then start a new shell before proceeding. The adb and fastboot provided by apt-get are old.
Do the following:
Have your device plugged in and fully booted and with USB debugging enabled
run this command: "sudo adb kill-server && adb start-server"
You should be prompted on the device to authorize the access of your computer via adb
run "adb devices" to make sure that it all worked correctly
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.
Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.
Following
I have the same error and like to follow
Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.
No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.
Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.
What fun! Windows 10 and the NST
I find that I cannot negotiate ADB access via USB any longer. I don't know when that started, but it looks like maybe sometime in June. These events are displayed in the Device Manager when accessing "Portable Devices":
Driver Management has concluded the process to add Service WUDFWpdFs for Device Instance ID SWD\WPDBUSENUM\_??_USBSTOR#DISK&VEN_B&N&PROD_NOOK_SIMPLETOUCH&REV_0100#7&22272E47&0&3012440020143004&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B} with the following status: 0.
Device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_B&N&Prod_NOOK_SimpleTouch&Rev_0100#7&22272e47&0&3012440020143004&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} was not migrated due to partial or ambiguous match.
Last Device Instance Id: SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_B&N&Prod_NOOK_SimpleTouch&Rev_0100#3014760074133009&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
Class Guid: {eec5ad98-8080-425f-922a-dabf3de3f69a}
Location Path:
Migration Rank: 0xF000FFFF0000F102
Present: false
Status: 0xC0000719
Device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_B&N&Prod_NOOK_SimpleTouch&Rev_0100#7&22272e47&0&3012440020143004&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} requires further installation.
It's not beyond belief that the spate of major updates to Windows 10 recently trashed my ability to access the device via ADB/USB. The question is: how to fix it?
On the NST I have the following:
service.adb.tcp.port -1
persist.adb.tcp.port 0
All that stuff indicates that the NST is presenting as UMS.
Have you used UsbView.exe to see what interfaces are being presented?
Have you looked at sys.usb.config, sys.usb.config?
That stuff with adb.tcp is only for ADB over TCP (WiFi).
Renate said:
Have you used UsbView.exe to see what interfaces are being presented?
Click to expand...
Click to collapse
Mmm....is that in your signature (NOT)?
Renate said:
Have you looked at sys.usb.config, sys.usb.config?
Click to expand...
Click to collapse
And this is where?
I should have added that none of my three NST/G devices is connecting properly now (other than as USB file transfer devices) whereas all were formerly able to negotiate USB debugging and ADB.
UsbView.exe is the venerable Microsoft utility, to be found here: https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
You can also look in Windows Device Manager (devmgmt.msc), especially in "View > Devices by Connection"
Either OmapLink.exe or ImxLink.exe (in sig) will show you if ADB is showing (err, conditional upon the driver being loaded?)
Renate said:
UsbView.exe is the venerable Microsoft utility, to be found here: https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
You can also look in Windows Device Manager (devmgmt.msc), especially in "View > Devices by Connection"
Either OmapLink.exe or ImxLink.exe (in sig) will show you if ADB is showing (err, conditional upon the driver being loaded?)
Click to expand...
Click to collapse
This is the result from omaplink (green dot for ADB, black for UMS):
Code:
Waiting for bootloader or Fastboot or ADB...
ADB version: 01000000, payload: 4096, type: device
uid=0(root) gid=0(root)
In DeviceManager/Devices by Connection, the Nook shows up as a USB composite device.
And I've attached a screencap from usbview.
Well, OmapLink/ImxLink found your rooted device.
You do have only one Android plugged in?
What part of ADB is not working?
What version adb.exe are you using?
If the version is stone age it goes by VID/PID and it doesn't know about B&N.
Code:
C:\>adb version
Android Debug Bridge version 1.0.41
C:\>adb devices
12345678
Version is not that critical, but should at least be in the high 30's.
(For UsbView you want to click on the device so that you see interesting things in the right panel. But we're past that step.)
Wait, are you talking about UMS not working, not ADB?
Oh, don't tell me that you use UMS?
The NST presents two drives but there may not be anything mounted.
Run Disk Manager (diskmgmt.msc) and see if there are drive letters but nothing inside them.
Renate said:
UsbView.exe is the venerable Microsoft utility, to be found here: https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
You can also look in Windows Device Manager (devmgmt.msc), especially in "View > Devices by Connection"
Either OmapLink.exe or ImxLink.exe (in sig) will show you if ADB is showing (err, conditional upon the driver being loaded?)
Click to expand...
Click to collapse
This is the result from omaplink (green dot for ADB, black for UMS):
Code:
Waiting for bootloader or Fastboot or ADB...
ADB version: 01000000, payload: 4096, type: device
uid=0(root) gid=0(root)
In DeviceManager/Devices by Connection, the Nook shows up as a USB composite device.
And I've attached a screencap from usbview.
Renate said:
Wait, are you talking about UMS not working, not ADB?
Oh, don't tell me that you use UMS?
The NST presents two drives but there may not be anything mounted.
Run Disk Manager (diskmgmt.msc) and see if there are drive letters but nothing inside them.
Click to expand...
Click to collapse
Unless I am transferring a library book with ADE I like to keep UMS turned off since it locks you out of interacting with the screen while debugging...which now isn't happening for some unknown reason.
I try to do most file transfers wirelessly to save wear and tear on the USB jack.
So, yes, I am talking about ADB. "Device not found" is all I get now. I'll check on the version later today but I don't see why a version which was working just fine before should suddenly stop. Unless its Windows' fault.
nmyshkin said:
"Device not found" is all I get now.
Click to expand...
Click to collapse
Ah, ok.
It's definitely a problem with your adb.exe
OmapLink/ImxLink can find your device, connect and even do shell commands (id).
Those programs, unlike AdbSync, do not go through the ADB port 5037 of adb.exe like a normal ADB client does.
If you actually have adb.exe connected OmapLink/ImxLink won't be able to connect to the already connected device.
So this all means tht your WIndows drivers are fine.
You might have had a few copies of adb.exe and one of them got deleted or the PATH changed or a backup restored the wrong one or...
Also, there was that old C:\Users\Person\.android\usb_adb.ini file which was used by old versions of adb.exe
But you don't want/need that anymore, so forget that I mentioned it!
Renate said:
Ah, ok.
It's definitely a problem with your adb.exe
OmapLink/ImxLink can find your device, connect and even do shell commands (id).
Those programs, unlike AdbSync, do not go through the ADB port 5037 of adb.exe like a normal ADB client does.
If you actually have adb.exe connected OmapLink/ImxLink won't be able to connect to the already connected device.
So this all means tht your WIndows drivers are fine.
You might have had a few copies of adb.exe and one of them got deleted or the PATH changed or a backup restored the wrong one or...
Also, there was that old C:\Users\Person\.android\usb_adb.ini file which was used by old versions of adb.exe
But you don't want/need that anymore, so forget that I mentioned it!
Click to expand...
Click to collapse
ADB version is 1.0.31 (Minimal ADB and Fastboot)
Just to see, I connected up my regular non-Nook tablet and ADB saw the device right away. So the issue is definitely with the NST or the interface of the NST with Windows.
I actually do have that usb_adb.ini file, but again, why work with everything else and "suddenly" stop working with the NST?
When UMS is turned off, I do see the two "empty" drives (internal and sdcard) in Windows when I connect via USB.
Marshmallow came out in October 2, 2015.
That had ADB version 1.0.32
That was the first public release that eliminated vendor white-listing that was changed in November 21, 2014.
I could tell you how to fix the adb_usb.ini, but you really should just update a half decade or so.
Renate said:
Marshmallow came out in October 2, 2015.
That had ADB version 1.0.32
That was the first public release that eliminated vendor white-listing that was changed in November 21, 2014.
I could tell you how to fix the adb_usb.ini, but you really should just update a half decade or so.
Click to expand...
Click to collapse
Huh.
So I updated Minimal ADB and Fastboot to v.1.43 which is ADB version 1.0.39. And it worked right away. I still don't see why the previous version just stopped working with the NST. Like so much else in life, it makes no sense.
Anyway now I have another issue, for this version came with a genuine Windows installer and my previous version was a "dump into the folder of your choice and set up the paths". I'm wondering if it's safe to just delete that entire folder now (probably have to clean up the path statement too...). Ugh.
Once upon a time, adb.exe and fastboot.exe were completely standalone.
Now they require AdbWinApi.dll, AdbWinUsbApi.dll
They also require:
Code:
api-ms-win-crt-private-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-environment-l1-1-0.dll
api-ms-win-crt-filesystem-l1-1-0.dll
api-ms-win-crt-time-l1-1-0.dll
api-ms-win-crt-utility-l1-1-0.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
api-ms-win-crt-multibyte-l1-1-0.dll
But these should already be found in the Windows "downlevel" directories.
There's no need to be adding to PATH for every little thing.
If you are invoking adb/fastboot from the command line, you might consider using doskey:
Regedit HKCU\Software\Microsoft\Command Processor AutoRun=\wherever\my-autorun.bat
Code:
doskey /macrofile=\wherever\my-aliases.txt
Code:
adb=C:\some-sort-of-path\adb.exe $*
fastboot=C:\some-sort-of-path\fastboot.exe $*
Edit: I forgot the arguments ($*).
If you are invoking adb/fastboot from a bat or makefile just put the full path in some define.