Hi all,
First of all, many apologies because I imagine that my situation below has been discussed here many times. TL;DR section at the bottom.
I have been trying to use adb to set an option on my Redmi Note 5 phone, to no avail. For the background of why I need that: I have arrived yesterday at my travel destination and I've realized that the app named "Google" has used over 2.24 GB of Wi-Fi data as reported by data usage in the Security app. In less than 24 hours! I've also installed and used the app Network Connections. All of this was in an effort to control the high bandwidth speed I was seeing in the notification bar (over 100 KB/s for minutes, without interruption). I have restricted network usage for all applications on Wi-Fi as well as on mobile data, disabled Sync (all forms of sync, believe me), and done everything I could think of to prevent the huge Wi-Fi usage, including rebooting the phone each time I changed a setting. The "Test Network" tile in Security still shows that about 100% of the bandwidth usage is by "Google" app. 90% of that usage is downloads and I can't figure out what Google is downloading to my device, which I've been using for a year without ever connecting it to a Wi-Fi network, until yesterday. Somehow, on my Redmi Note 5 running MIUI 11, "Wi-Fi" is equated to "unlimited network, with no cap, and no reason to be reasonable".
The root problem is that the Wi-Fi I'm connecting to is metered, and apparently, MIUI has removed the underlying Android option to set a Wi-Fi connection as metered. The solution, as I've discovered online is to issue an adb command (cmd netpolicy set metered-network <name of network> true).
Therefore, I head to using adb. Many pages online deal with enabling Developer Options and US debugging, and I had already done just that in the past.
However, in the instructions on using adb, each such page speaks at a certain point in the list of instructions of a dialog box that is supposed to show up on the phone ("Allow USB debugging?" with something about a computer fingerprint), but it never showed up on my device. The command adb devices does not list anything, not even in a command line opened as an administrator. The adb executable that I'm using is from the Android Platform Tools (platform-tools_r29.0.5-windows.zip).
Many forum pages hint to a missing driver. But I can easily plug the phone via USB and download files and photos from the phone to the computer. If it was a driver issue, shouldn't I have problems doing file transfers?
Moreover, each time I plug the phone via USB, I see a notification from "Android system" stating "USB debugging connected" followed by "Tap to turn off USB debugging", which tells me that USB debugging is working.
TL;DR
adb devices lists nothing when my Redmi Note 5 is connected via USB. I guess it's a driver issue. How can I get the appropriate driver? I would like to avoid downloading sketchy driver packs from random websites such as the ones from xiaomi advices (e.g. the "driver" for Redmi Note 5 was uploaded on October 5, 2014!!!).
Thank you.
do you already set enable usb debugging on developer setting?
You can try to install Xiaomi Mi PC Suite on your PC, after the installation, open the program and connect your phone with the USB cable, that will install the correct drivers, I hope. Then you can close the program and activate USB debugging in Developer Options in your phone, and try again to write the command in the terminal.
EriecTan said:
do you already set enable usb debugging on developer setting?
Click to expand...
Click to collapse
Yes. Both the plain "USB debugging" and the "USB debugging (Security settings)".
openCode168 said:
You can try to install Xiaomi Mi PC Suite on your PC, after the installation, open the program and connect your phone with the USB cable, that will install the correct drivers, I hope. Then you can close the program and activate USB debugging in Developer Options in your phone, and try again to write the command in the terminal.
Click to expand...
Click to collapse
Well, I have installed PC Suite 2.2.0.7032 to no avail: when I connect the phone via USB, a PC suite window shows up and says "Looks like you're missing some drivers... Make sure you're this system's administrator", which I am. I can't believe that in this day and age it is so difficult to find official drivers for a device that's been sold by the thousands.
Thanks for your help.
OMFG, I did it!
Before I say anything more: I have uninstalled Mi PC Suite.
The solution is in the mode that is active in the notification shade once the phone is connected via USB to the computer. In the notification shade, there was a notification from Android system that read "Charging this device via USB, tap for more options". Once I tapped and chose "File transfer", things changed!
At the same time, the Device Manger had been opened on the computer an I was seeing a yellow overlay icon over "SDM636-MTP _SN:xxxxx" in category "Other devices". As soon as I chose "File transfer", the device "SDM636-MTP" disappeared and a new category "Android Phone" showed up, along with a subcategory that read "Android Composite ADB interface". The "ADB" in the title prompted me to try using adb. That's when it all worked! Here is a transcript of the command line session, during which at some point I got (on the phone) a dialog box about authorizing the computer, also showing an RSA fingerprint. I obviously authorized the computer :
Code:
Microsoft Windows [version 6.3.9600]
(c) 2013 Microsoft Corporation. Tous droits réservés.
D:\Programs\adb>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
fce3c2e3 unauthorized
D:\Programs\adb>adb devices
List of devices attached
fce3c2e3 device
D:\Programs\adb>adb shell
whyred:/ $ cmd netpolicy list wifi-networks
waav19781502;none
WI-FI HOME;none
whyred:/ $ cmd netpolicy set metered-network "WI-FI HOME" true
255|whyred:/ $ cmd netpolicy list wifi-networks
waav19781502;none
WI-FI HOME;true
whyred:/ $
So the problem was not about drivers like I thought and complained about, it was about choosing the appropriate mode once the phone is connected to a computer via USB.
I'll see now whether setting the Wi-Fi networks as metered will be enough to stop Google from using up the data allowance.
EDIT: Setting the network as metered did the trick: what was previously hovering well above 100 to 200 KB/s is now around 0.05 - 3.00 KB/s, due this time not to "Google" but to "Google Services Framework" and "Google Play Store"
Related
Currently I'm trying this guide:
Nook Tablet "One Click Root" + gapps ADB script
but I've been trying various guides all day. The drivers are there, debugging enabled, auto mount disabled, robot in the bottom corner but when I run ADB Devices, no dice. Anyone have any clues what the problem could be or atleast anyone else having this problem? At first I thought it might be because I was using a different USB cord but it still doesn't work even with the Nook cord
The problem you describe is almost guaranteed to be a problem on your computer and the driver installation.
For the folks here to help, they will need to know platform (PC or mac) and version of operating system.
If Windows, they will need to know how the device appears to Device manager. If it shows up as a disk drive - you will have to disconnect from the Nook side. ADB Composite should be good.
For either platform, confirm that adb_usb.ini is in the right place and modified correctly.
No, you're wrong dude above me.
OP: Run this in cmd prompt
Code:
echo 0x2080 > %username%\.android\adb_usb.ini
You need to have your nook tablet unplugged when you run that then you would see nook tablet in the device manager when you plug it back in.
Indirect said:
No, you're wrong dude above me.
OP: Run this in cmd prompt
Code:
echo 0x2080 > %username%\.android\adb_usb.ini
Click to expand...
Click to collapse
"Cannot find the path specified." But I can locate the file myself in that directory??
I'm running Windows 7 64-bit, device shows up as android phone>androud ADB interface.
My bad it's
Code:
echo 0x2080 > "%USERPROFILE%\.Android\adb_usb.ini
Check, still nothing in ADB, i did restart the server too. To be clear, the .ini file only has the "0x2080" line in it now, nothing else. I'm assuming that's ok because the other stuff was commented out anyway, am I right?
(thanks for your help! )
1) look in device manager now though, you need to install the drivers.
I still see it listed under android phone > android ADB interface and not mass storage or anything like that, you think that's still the problem though?
*Edit*
SUCCESS!! I uninstalled the "Android ADB Interface" and "Android Composite ADB Interface" appeared in its place!!(??) Whatever happened the device show up now. Thanks for the help and keep up the good work Indirect!
Indirect said:
My bad it's
Code:
echo 0x2080 > "%USERPROFILE%\.Android\adb_usb.ini
Click to expand...
Click to collapse
I was having problems seeing the Nook Tablet in adb devices, but this fixed it for me.
I was having the same issue for a bit, restarted my nook and it worked haha.
Sent from my BNTV250 using xda premium
This worked for me. Hopefully it helps.
While the nook is plugged in (mine showed the 2 "Disk Drives" and 2 Drive Letters under portable devices). Open Device Manager and delete/remove the 2 disk drives called "B&N NOOK Tablet USB Device" (this should also remove the weird drive letters under portable devices). Now go to Control Panel > Advanced System Settings > Hardware Tab > then click "Device Installation Settings". Change this setting to "No, let me choose what to do", and make sure "Never install driver software from Windows Update" is checked below that.
Now unplug and replug your NT, and you should now see an Android Composite device with the "!" next to it. You should now be able to install the custom drivers described in the other posts.
Essentially it seems windows is trying to "help" you by guessing at the drivers you want to use.
If this doesn't work, you can try to remove ALL android devices using the USBDeview Application that you can find http://www.androidsim.net/2009/08/how-to-1-how-to-install-usb-driver-on.html
I used USBDeview for the removal part just because I had a Kindle fire, HTC device, samsung device, all installed and I think they were fighting a little bit. I now have results from adb devices, and dare I say ROOT!?!?!
Hope this helps some of you!
Good post - Windows Vista especially, and Windows 7 somewhat, really think they know better than the user when it comes to drivers. Especially unsigned drivers in preference to signed ones...
I found that the best way to do this for people with this problem (such as me), is to go in Device Manager, expand the USB Mass Storage Device selection, search for the USB Mass Storage device of your Nook Tablet (easiest way would be to unplug any other external hd, sd card, ... so that there is only one USB Mass Storage device). At this point, right click and update driver and select the folder manually.
tsubus said:
I found that the best way to do this for people with this problem (such as me), is to go in Device Manager, expand the USB Mass Storage Device selection, search for the USB Mass Storage device of your Nook Tablet (easiest way would be to unplug any other external hd, sd card, ... so that there is only one USB Mass Storage device). At this point, right click and update driver and select the folder manually.
Click to expand...
Click to collapse
I just joined the forum to thank you! I spent hours looking for a solution and yours worked!
brices21 said:
While the nook is plugged in (mine showed the 2 "Disk Drives" and 2 Drive Letters under portable devices). Open Device Manager and delete/remove the 2 disk drives called "B&N NOOK Tablet USB Device" (this should also remove the weird drive letters under portable devices). Now go to Control Panel > Advanced System Settings > Hardware Tab > then click "Device Installation Settings". Change this setting to "No, let me choose what to do", and make sure "Never install driver software from Windows Update" is checked below that.!
Click to expand...
Click to collapse
Well I am stumped here, seriously. I can't get rid of the above mentioned 2 instances of "B&N NOOK Tablet USB Device" no matter what I do. Auto mount is off on the device and the device installation setting is already set to "No, let me choose what to do." Yet every time I plug the NT in- the computer kindly tells me it's "ready for use" and those two "B&N NOOK Tablet USB Device" listings are back. At this point I'm not sure I'm ever gonna be able to get the device to show up under ADB. The computer just won't seem to let it.
Any advice anyone might on this would be greatly, greatly appreciated.
maybe try what Indirect did here: http://forum.xda-developers.com/showthread.php?t=1363652
The website is below what I did to completely disable Windows from installing the Nook drivers every time it is plugged in. I also had the "Never install driver software from Windows Update" checked from Brices21's post but the drivers would still install everytime it is plugged in.
xxxx = http - still a noob, can't post links
yyy = www
xxxx://yyy.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
I never actually installed the USB drivers that indirect provided, but "adb devices" still detected the NT when plugged in.
This was my whole process to get "adb devices" to detect the NT:
With the NT plugged in and device manager detecting the 2 Nook devices as drives and 2 Nook devices in "other devices" and with automount disabled and USB debugging enabled
I also ran the runmefirst.bat at some point in time previously, so the necessary files were created already
***** Pulled this from the website above******
* Go to Start–>Search type in gpedit.msc
* Click the file to open the Local Group Policy Editor and show Windows who is in control!!
* You want to go here: Computer Configuration->Administrative Templates->System->Device Installation. Click on the subfolder Device Installation on the left and on the right side you will see the possible restrictions.
* Right Click on Prevent Installation of Devices not described by other policy settings and edit this option, set it on ENABLED.
*************************************
From here the website says to reboot and set the option back to default. I did not reboot or set the option back.
* Going back into device manager, I uninstalled the drivers for the 2 Nook drive devices.
* Unplugged the NT
* Plugged the NT back in
Then I got the B&N NOOK Tablet USB Device with the broken symbol under "Other devices" in Device Manager
* Open cmd and run "abd devices" from the ntroot directory
The service should start and list the NT device as a bunch of numbers.
* From here you can run NookandZergy.bat to root the NT.
After rooting you can set the options in the gpedit.msc back to defaults.
I also tried installing the Indirect provided drivers as the USB mass storage device. Windows then detected the device as an Android ADB Composite device but "adb devices" from cmd prompt would not detect the NT. I ended up removing all of the drivers and repeating my steps to get "adb devices" to detect it again.
Hope this helps! It may not be the best solution but it was a workaround for me to get the NT rooted.
****Update*****
Just got home and tried to install the drivers and it worked this time. I was able to see the NT with "adb devices"
With the gpedit.msc edit intact, I plugged in the NT and Windows detected 2 broken Nook devices under "other devices" and a mass storage device under USB controllers.
* I uninstalled the driver for the mass storage device
* set the gpedit.msc back to "not configured"
* unplugged NT
* made sure debug mode was set and automount disabled
* plugged NT back in
Device manager showed a Mass Storage device under "Other devices"
* Update drivers for that device with the Indirect usb driver
* ran "adb devices" in cmd prompt and NT is detected.
So if there's anything to take away from my post...hopefully you can use the gpedit.msc to completely disable the autoloading of drivers.
Drivers Fixed!
Rooted! Got past driver issues (Android Composite ADB Interface appeared in Device Manager, adb still couldn't detect Nook). Thanks to all who have worked so many hours on this.
Here's what worked for me (using Windows XP 32 bit):
1. make sure "adb_ini" file contains "0x2080" and is located at "%USERPROFILE%\.android"
2. I had to manually edit my "path=" environment variable to include the above location - both in Control Panel->System->Advanced->Environment Variables and in cmd window.
3. carefully followed instructions on proper installation of drivers for "Android Composite ADB Interface". At this point, cmd window use of adb was able to detect Nook (as well as runmefirst.bat).
4. Continued with root process (i.e. NookandZergy.bat)
Hope this helps anyone still having driver issues.
Never had this issue using the trick mac method.
I have a brand new windows 7 computer, I have installed the latest android SDK, I want to connect to my Nexus 10 using adb.
(device has windows drivers from SDK; "Android Composite ADB Interface". adb version 1.0.31)
when I do adb devices, it does see my device but it says my device is unauthorised.
It has never displayed the security popup.
I am convinec that the security pop up wouyld make this work, but i cannot get it to show, so that it does whatever magic it does.
I have tried plugging and unplugging the usb cable,
I have tried turning USB debugging on and off.
I have changed the USB connection from Camera, to Media, back to Camera.
I can see the adbkey file under $HOME/.android in windows
The android directory /data/misc/adb/ is empty
I have root.
How can I force the security popup to display?
Or how can I frig this so I can get it working?
What does the secuirty popup do anyway? probably just copy the adbkey file from windows into the android /misc/adb/ directory right? Can I do it by hand?
Slightly unrelated question, is it true that everything works first time, everytime on IOS?
xdaforummartin said:
I have a brand new windows 7 computer, I have installed the latest android SDK, I want to connect to my Nexus 10 using adb.
(device has windows drivers from SDK; "Android Composite ADB Interface". adb version 1.0.31)
when I do adb devices, it does see my device but it says my device is unauthorised.
It has never displayed the security popup.
I am convinec that the security pop up wouyld make this work, but i cannot get it to show, so that it does whatever magic it does.
I have tried plugging and unplugging the usb cable,
I have tried turning USB debugging on and off.
I have changed the USB connection from Camera, to Media, back to Camera.
I can see the adbkey file under $HOME/.android in windows
The android directory /data/misc/adb/ is empty
I have root.
How can I force the security popup to display?
Or how can I frig this so I can get it working?
What does the secuirty popup do anyway? probably just copy the adbkey file from windows into the android /misc/adb/ directory right? Can I do it by hand?
Slightly unrelated question, is it true that everything works first time, everytime on IOS?
Click to expand...
Click to collapse
While it is plugged in, revoke the permissions in Developer Options. Should be right under the USB Debugging option. Then unplug and plug it back in. Should pop up on the phone after that. And for the iPhone question, surely you're joking? Apple's software has bugs in it just like anything else. Check out the massive waves of complaints on any iPhone related forum any time there is a new update as an example.
I did that, but there was no popup. !!??!!
xdaforummartin said:
I did that, but there was no popup. !!??!!
Click to expand...
Click to collapse
does anyone know what chmod (permissions) the adb_keys file on the android is meant to be?
xdaforummartin said:
I did that, but there was no popup. !!??!!
Click to expand...
Click to collapse
Hmm. I've had that happen on quite a few different phones at my shop and that always did the trick. *shrug* There's always the factory reset option.
Hi,
I've been trying to get adb working on a Mac (OS 10.6.8), talking to a Galaxy Note II. The thing is, that USB communication seems all messed up. Between KIES and AFT and the MacOS drivers I keep running into the following:
- connect device via USB
- up pops a disk icon and finder window (showing Verizon's Windows tools); then the WIndow closes, and
- up pops AFT error - can't connect; I close that,
- up pops MacOS's network preferences window asking if I want to configure a USB modem; I close that;
- adb devices list the device properly, lets me do things like start a shell
BUT....
- if I start something long running (like a backup), AFT again tries to pop open a finder followed by an error, network preferences again tries to configure a modem, and in the process, they kill the adb connection
Perhaps somebody can explain a bit about the ins and outs of USB-Android connectivity, on a Mac, specifically with the Samsung strangeness? And maybe suggest a way to suppress all the unwanted behaviors?
Thanks very much,
Miles Fidelman
--Edit--
This is finally solved. There was a problem with my computer's ADB RSA key, so I simply had to delete the key file and rerun ADB and I Received the RSA Key Fingerprint window instantly on my G3.
For the full description of the problem look here:
I'm having issues trying to root my phone. I'm using the ioroot method mentioned here.
I get to "* daemon started successfully *" then nothing. After a lot of troubleshooting I know it's because my phone won't allow access by my computer. I never receive the RSA Fingerprint window allowing my computer access to my phone. Here's what all I've tried:
-Put phone into Internet>Ethernet mode (and I've also tried Internet>Modem, MTP and Camera modes as well just to say I did).
-Enable Developer Options and enable USB Debugging.
-Installed the drivers linked in the ioroot page (I've also downloaded the drivers directly from LG - believe it or not ... it's the same file).
-Installed the Verizon Software Assistant from the phone after connecting to the computer.
-Updated my ADB version with the SDK Manager.
-Used different USB ports on my computer as well as two different USB cables (one of which came with the G3).
-Checked Device Manager, all is as it should be and no unrecognized devices.
When I ran the adb server without the ioroot batch file, typing "adb devices" would return my phone's serial followed by "offline." It did this until I updated ADB; then when typing "adb devices" it would return the serial followed by "unauthorized." I've tried all various methods and combinations of switching adb debugging on and off, switching developer options on and off, installing and uninstalling and reinstalling the LG drivers, unplugging and replugging the USB cable, power-cycling all devices including myself at night, doing these methods with long pauses in between (10 minutes to ensure I wasn't being impatient), scratching my head, drinking more coffee, switching to rum and swearing at all devices but nothing seems to make a difference.
What am I missing?
I've got the Verizon LG G3 in White (LG-VS985W)
Software version VS98510B
Windows laptop running Vista 32 bit (I know I know, "eeew Vista")
I was able to obtain root using a different computer, here's what I tried with my laptop after gaining root to get it and my G3 on speaking terms:
-Deleted the ADB_Keys file on the G3 (/data/misc/adb/adb_key): no change.
-Compared running Windows services between Vista and 8.1 and started services which were running on 8.1 but not vista: no change.
Here was the resolution:
There turned out to be a problem with my laptop's ADB RSA key. I'm assuming my G3 was rejecting a bad key and disallowing my laptop to connect to it via ADB.
ADB saves a key file in one of multiple places on a Windows computer, the first is in the location where adb.exe is (C:\android), the second is in the user's profile (C:\Users\*username*\.android), the third place is in the Windows system files (C:\Windows\System32\config\systemprofile\.android), the file is simply named "adbkey" with no extension. If there is no key file when ADB runs, it will generate one automatically.
Mine was located in my user folder (C:\Users\*username*\.android\). All I had to do was delete the adbkey file (there was also a file named "adbkey.pub" which I deleted as well), restart the adb server in command prompt (adb start-server) and plug my phone in. I instantly received the RSA Fingerprint Key window on my G3 allowing connection between the two devices. Then typing "adb devices" returned my phone's serial number followed by "device" showing it was available. I went back to the C:\Users\*username*\.android\ folder and sure enought there were new "adbkey" and "adbkey.pub" files.
Problem finally fixed!
Here are some VERY useful links which helped me come to this fix:
How ADB enables a secure connection
Reconstructing ADB's RSA key file
Try using this set of Vertizon g3 drivers: https://mega.co.nz/#!58YHAZaQ!yNlgZG1m7toHBZp_0HF1jSQ66gMoZmmiDrNq9W5aJIc
Open the .zip, run the .msi file on Windows.
I do not run the G3's auto-install software when I plug it into the PC.
I do set the G3 to "PTP" USB before initially connecting to the PC.
The adb file in the ioroot "bts" subfolder should be okay to run on Windows.
When the phone is attached to the PC, change its USB connection type to Internet, with submenu type Ethernet. At least on my phone, right when I change the phone connection to Internet/Ethernet is when I get the phone popup to accept the PC's RSA fingerprint.
If I then run "adb devices" on my PC, I'll see the random ID followed by "attached", which means I have a good connection. If this doesn't happen, unplug, then replug, the USB connection at the PC side.
Then I can "cd .." and run ioroot.bat.
Good luck!
markfm said:
Try using this set of Vertizon g3 drivers: https://mega.co.nz/#!58YHAZaQ!yNlgZG1m7toHBZp_0HF1jSQ66gMoZmmiDrNq9W5aJIc
Open the .zip, run the .msi file on Windows.
I do not run the G3's auto-install software when I plug it into the PC.
I do set the G3 to "PTP" USB before initially connecting to the PC.
The adb file in the ioroot "bts" subfolder should be okay to run on Windows.
When the phone is attached to the PC, change its USB connection type to Internet, with submenu type Ethernet. At least on my phone, right when I change the phone connection to Internet/Ethernet is when I get the phone popup to accept the PC's RSA fingerprint.
If I then run "adb devices" on my PC, I'll see the random ID followed by "attached", which means I have a good connection. If this doesn't happen, unplug, then replug, the USB connection at the PC side.
Then I can "cd .." and run ioroot.bat.
Good luck!
Click to expand...
Click to collapse
... no dice.
Ok, I'm switching to my Windows 8.1 machine (my laptop is my server and android-dirty-work machine).
So it worked without hesitation on my 8.1 machine. I used the drivers listed in the ioroot thread (same as the drivers from LG) and the process went off without a hitch. I have no idea why my Vista machine and G3 don't get along but I'll need to figure it out when I do further adb work because I use my laptop for that.
Thank you markfm for the extra drivers.
I'll call this solved for now but if I find out further reasons why it didn't work I'll post it here for others who have similar struggles.
Ok I finally solved this. It turned out there was something wrong with my laptop's ADB RSA key. All I had to do was delete the key file, run the ADB Server and connect the phone. ADB will automatically generate an RSA key if none exists. The RSA key was located in C:\Users\*username*\.android and was simply named "adbkey" with no extension. There was also a file named adbkey.pub (Microsoft Publisher) which I'm assuming is a viewable version of the key. I deleted both of these, re-ran the ADB server and voila I instantly received the RSA Key Fingerprint confirmation window on my G3.
Done and done!
unable to generate RSA key on my MCB
I've read and re-read all the entries addressing this issue. I have a black G3 and am using a 2013 Mac Book Pro. I've followed the instructions to the letter many times but with no success. I'm at a loss. Any ideas would be greatly appreciated.
scooterd said:
I've read and re-read all the entries addressing this issue. I have a black G3 and am using a 2013 Mac Book Pro. I've followed the instructions to the letter many times but with no success. I'm at a loss. Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
You'll have to bear with me because I'm not familiar with Mac file structure.
I would start from scratch. Do all these before trying to run adb again.
On your computer:
-Delete adbkey & adbkey.pub from the .android folder (I'm not sure where that is on a Mac, Home\.android?).
-I'm not sure if Macs have a device manager, but check that your phone is correctly recognized and the drivers are installed properly.
On your phone:
-Ensure you've got developer features unlocked
-Double check that you've got usb debugging enabled.
-Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options.
-When you're plugged in be sure to set your connection to Internet >>Ethernet (you'll see the debugging icon in the notification bar if it's connected right).
I know a lot of that is basic and redundant but if it's all done correctly then it should work. If it doesn't work it gives us a good starting point to troubleshoot.
If you want to test it open terminal, change directory to the bts folder in the ioroot folder and start adb (adb start-server), with everything done right you should get the rsa window on your phone right now. Type "adb devices" and see what comes back.
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
scooterd said:
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
Click to expand...
Click to collapse
Use whatever mode will enable USB Debugging. If Internet>>Ethernet doesn't work then use any other mode that will. It's not necessarily important what mode your phone is in, but what mode will allow USB Debugging. If you have it in MTP, PTP, Camera or any other, and you have the USB Debugging icon in the notification bar, try the "adb devices" command and if it returns "*serial* device" then you should be good to go to root.
Once your phone has enabled USB Debugging and accepted the RSA key from your computer then the connection is made and your phone will accept the ioroot commands.
scooterd said:
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
Click to expand...
Click to collapse
Is your phone a Verizon Model (VS985)? I'm assuming not because I don't have PTP mode on my G3. If it's not Verizon, the ioroot method suggests using PTP mode.
Yes it is a Verizon VS985. I bought it last week. I have four options, charge, MTP, internet and PTP when I connect my phone to the PC. I get usb debugging under either ethernet or modem. Device Manegr sees my phone and I get the RSA key. I never get a terminal which let's me know something isn't right. This is truly weird but I won't give up. I'll start over and see what happens. Again, thanks for your patience.
scooterd said:
Yes it is a Verizon VS985. I bought it last week. I have four options, charge, MTP, internet and PTP when I connect my phone to the PC. I get usb debugging under either ethernet or modem. Device Manegr sees my phone and I get the RSA key. I never get a terminal which let's me know something isn't right. This is truly weird but I won't give up. I'll start over and see what happens. Again, thanks for your patience.
Click to expand...
Click to collapse
No problem at all, happy to help! It sounds like you have everything set up properly, however the terminal doesn't open automatically (you need to do it manually). But you shouldn't need to open the terminal to get ioroot to work, after you've unzipped the ioroot.zip file, simply navigate to the ioroot folder, right-click on ioroot.bat and choose Run as Administrator. That should run through the entire process for you.
If you want to test your adb connection (testing not required for ioroot to work) you'll need to open the command prompt manually. Press Windows Key+R, in the run window, type cmd and press enter, this will open the command prompt. When you're in the command prompt, you'll need to change directory to the location of adb.exe in the bts folder inside the ioroot folder. Mine was in a folder named android on my C drive so the address looked something like this: C:\android\ioroot\bts the command you'll type in command prompt would be: cd C:\android\ioroot\bts then press enter. Then you can type adb devices and see if you're connected properly.
Okay. Here's where we are. I did everything you suggested. I got the RSA key and the G3 went into recovery mode. I toggeld down to the appropriate command and hit the power button. The little green guy fell over with the dreaded red triange and I got the message "This version of ioroot does not support your device/firmware combo. Please downgrade to previously supported software version. My G3 is running VS98510B. I can't post in the devlopment section but wonder if a software update prevents root the the version being used. Just a question but at least I know I'm not going crazy.
---------- Post added at 04:33 PM ---------- Previous post was at 03:46 PM ----------
scooterd said:
Okay. Here's where we are. I did everything you suggested. I got the RSA key and the G3 went into recovery mode. I toggeld down to the appropriate command and hit the power button. The little green guy fell over with the dreaded red triange and I got the message "This version of ioroot does not support your device/firmware combo. Please downgrade to previously supported software version. My G3 is running VS98510B. I can't post in the devlopment section but wonder if a software update prevents root the the version being used. Just a question but at least I know I'm not going crazy.
Click to expand...
Click to collapse
You sir are a genious. After changing my USB cord, I'm rooted and all is well in the world. It's always the little things that matter
My Pleasure! It's the little things that matter and the little things that kill!! I'm glad you're finally victorious!:laugh:
EDIT: Nevermind, I got it to work through Internet>Ethernet.
postal302 said:
Is your phone a Verizon Model (VS985)? I'm assuming not because I don't have PTP mode on my G3. If it's not Verizon, the ioroot method suggests using PTP mode.
Click to expand...
Click to collapse
Hi, hope this thread is somewhat still alive. sorry for the late add on... please help.
Sorry I'm a complete moron when it comes to rooting and ADB / RSA stuff and have no idea what exactly i am doing but for some reason my macbook won't allow me to authorize my oneplus. the authorize computer dialog box never pops up however i get a notification when my phone is plugged in that debugging is active. developer options have been reset, multiple usb cables have been used, and authorization has been revoked multiple times as well.
Im not sure how to access my adb settings on mac and when i attempt to go into terminal and try kill-server / start-server commands i get error messages as commands are not recognized.
Any help is appreciated as i can no longer use stock rom on OPO and i can't go about rooting my device
Wrong forum area -- this is for the Verizon LG G3 smartphone.
Same here! WITH NEXUS 7
Tried all the methods and spent almost 20hrs experimenting to retrieve rsa fingerprint, but in vain
Can you please suggest any remedy?
I cant install any os and unfortunately, my status bar and softkeys disappeared after using softkeyz apk...Dont tell to delete dalvaik data and cache[ it didnt work]
Please...
Jesusmaryqueen said:
Tried all the methods and spent almost 20hrs experimenting to retrieve rsa fingerprint, but in vain
Can you please suggest any remedy?
I cant install any os and unfortunately, my status bar and softkeys disappeared after using softkeyz apk...Dont tell to delete dalvaik data and cache[ it didnt work]
Please...
Click to expand...
Click to collapse
It is also possible to overcome the situation, by installing Mobilego software on your PC and follow the instructions accordingly (connecting your android using usb & debugging etc,.). You will get a RSA fingerprint request.. Easy Once it's done, u can close the mobilego software in the PC and open someother software for example Bacon root toolkit for oneplus one etc etc.. Hope this helps
adbkey doesn't exist
I don't know what i did wrong before, but my computer just DOES NOT have adbkey and adbkey.pub anywhere! First, i thought it was my phone's fault. Then, i tested in a different pc, and it worked. How do i generate those keys? There are no helpful answers in the internet yet...
Hi, I'm new to the N9, have had the tablet about a week. I have tried connecting it to my windows 7 Pc and the N9 isn't recognized. I have tried all the basics, all drivers are current, set tablet to mtp, and not found. I have connected to a friend's Windows 10 PC and the N9 is found immediately. My N9 is a wifi only device, non rooted. I have 2 other Android devices that my W7 PC finds with no issue. Anyone else experience this, and or have any suggestions on how to fix this issue ? Not looking to root at this point. Any help and guidance would be greatly appreciated
I think there are many threads about this problem. Nexus Root Toolkit has a driver installation feature.
If you were starting from scratch I'd delete any unknown "tablet/usb" devices in Device Manager - look for the also delete drivers option.
Google's W7 installation instructions are here http://developer.android.com/tools/extras/oem-usb.html#Win7
On this page http://developer.android.com/sdk/win-usb.html is a link to download a zip file of the drivers (not the full SDK package) Click here to download the latest Google USB Driver ZIP file.
This software http://www.nirsoft.net/utils/usb_devices_view.html is possibly better than device manager in deleting drivers
In some cases, you need to enable ADB on your N9 before plugging it into your PC (Settings -> Developer Options -> Android Debugging).
peterk-1 said:
I think there are many threads about this problem. Nexus Root Toolkit has a driver installation feature.
If you were starting from scratch I'd delete any unknown "tablet/usb" devices in Device Manager - look for the also delete drivers option.
Google's W7 installation instructions are here http://developer.android.com/tools/extras/oem-usb.html#Win7
On this page http://developer.android.com/sdk/win-usb.html is a link to download a zip file of the drivers (not the full SDK package) Click here to download the latest Google USB Driver ZIP file.
This software http://www.nirsoft.net/utils/usb_devices_view.html is possibly better than device manager in deleting drivers
Click to expand...
Click to collapse
Thank you for your help, I had already tried all of this, but tried once more in case a step was missed. Every other Android device I have, or had never gave me an issue like this. The 2 android phones I have connect to pc without a problem, I am at a loss, lol.
When deleting drivers, should I have deleted all drivers for all devices, or just the ones installed from N9 ? Thanks again for your help
eckharttim said:
Thank you for your help, I had already tried all of this, but tried once more in case a step was missed. Every other Android device I have, or had never gave me an issue like this. The 2 android phones I have connect to pc without a problem, I am at a loss, lol.
When deleting drivers, should I have deleted all drivers for all devices, or just the ones installed from N9 ? Thanks again for your help
Click to expand...
Click to collapse
I've not got access to a Windows 7 PC. Does this page help http://www.topnotchtablets.com/FixUSBproblems
A basic one. I don't think it's relevant until you have a connection. Do you know that the N9 USB connection defaults to "charging only" and you need to pull down the notification menu to enable MTP to see the device contents
In USBDeview
Expand the window there are a lot more columns
There is a "connected" y/n column. I'm not certain that this works as expected, I can connect a tablet and despite an F5 refresh or a restart of the program it will stay a "No"
Look at the VendorId column AFAIK everything Google Nexus related has an ID of "18D1"
Have tried to establish what, if anything pops up in Device Manager when you plug in the N9 so you can disable it? Nirsoft have a program http://www.nirsoft.net/utils/device_manager_view.html that gives a table view of all devices - no clicking to expand trees
peterk-1 said:
I've not got access to a Windows 7 PC. Does this page help http://www.topnotchtablets.com/FixUSBproblems
A basic one. I don't think it's relevant until you have a connection. Do you know that the N9 USB connection defaults to "charging only" and you need to pull down the notification menu to enable MTP to see the device contents
In USBDeview
Expand the window there are a lot more columns
There is a "connected" y/n column. I'm not certain that this works as expected, I can connect a tablet and despite an F5 refresh or a restart of the program it will stay a "No"
Look at the VendorId column AFAIK everything Google Nexus related has an ID of "18D1"
Have tried to establish what, if anything pops up in Device Manager when you plug in the N9 so you can disable it? Nirsoft have a program http://www.nirsoft.net/utils/device_manager_view.html that gives a table view of all devices - no clicking to expand trees
Click to expand...
Click to collapse
Thank you for your help I greatly appreciated it. After trying pretty much everything, I decided to see if the ruu's for my two phones would run on W10. They did, so I then proceeded to update my W7 to W10. N9 communicates perfectly now with my PC. Thank you