Hi all,
I'm sorry, I tried to provide direct links/images but unfortunately only after 10 posts I'm allowed to post URLs
The most recent, much welcomed, update to ChromeOS has introduced ADB over USB for a select few models ( find the chromium org url "chrome-os-systems-supporting-adb-debugging-over-usb" ).
However, I have yet failed to get this to work by connecting my brand new Pixelbook (as of yesterday) to a Windows 10 machine, and using the guide provided on developer (dot) android topic/arc/#adb-usb
Did anyone get this work successfully?
If so, can anyone point me in the right direction?
Using hardware:
- Pixelbook with Stable Build 67, and also attempted Dev Channel with build 69.
- Connected USB0 (left side) to my Windows 10 laptop USB-A port, but also attempted connecting it to my laptop's USB-C port (so a USB-C to USB-C cable).
My steps:
- Powerwashed the Pixelbook
- Set Pixelbook to 'Developer Mode', see image:
h ttps://ibb.co/cRmiEo
- Enable Android Developer Options by going to Settings in ChromeOS, Manage Android --> 7 taps on Build Number and then opening the 'Android Developer Options' and enable ADB Debugging:
h tt ps://ibb.co/mLikS8
- Run the setup commands in crosh/shell as described in the guide (link above), such as dev_enable_udc , and dr_swap commands. As stated by the guide on developer.android: "Use this command each time you disconnect and reconnect a USB cable. To ensure your Chromebook is in UFP mode, you can run ectool usbpd <port number>" . See attached:
h tt ps://ibb.co/j8m5S8
- Attached the USB-C cable to the W10 laptop and run ADB devices.
- No devices show up in cmd (adb devices)
- Android Studio also does not list any devices to run on
- This is what I'm seeing in Device Manager, a 'malfunctioning adb device'
h tt ps://ibb.co/cpXen8
Any help would be greatly appreciated if anyone has already managed to the ADB USB to work!
No solution (yet)
Let me know whenever someone has given this a shot with their Chromebook.
I still haven't managed to solve it, also posted it to the Google Product forums now
Quick search of this forum shows this.
https://forum.xda-developers.com/ha...oks/guide-setting-adb-fastboot-x8664-t3806428
Brounzer said:
Hi all,
I'm sorry, I tried to provide direct links/images but unfortunately only after 10 posts I'm allowed to post URLs
The most recent, much welcomed, update to ChromeOS has introduced ADB over USB for a select few models ( find the chromium org url "chrome-os-systems-supporting-adb-debugging-over-usb" ).
However, I have yet failed to get this to work by connecting my brand new Pixelbook (as of yesterday) to a Windows 10 machine, and using the guide provided on developer (dot) android topic/arc/#adb-usb
Did anyone get this work successfully?
If so, can anyone point me in the right direction?
Using hardware:
- Pixelbook with Stable Build 67, and also attempted Dev Channel with build 69.
- Connected USB0 (left side) to my Windows 10 laptop USB-A port, but also attempted connecting it to my laptop's USB-C port (so a USB-C to USB-C cable).
My steps:
- Powerwashed the Pixelbook
- Set Pixelbook to 'Developer Mode', see image:
h ttps://ibb.co/cRmiEo
- Enable Android Developer Options by going to Settings in ChromeOS, Manage Android --> 7 taps on Build Number and then opening the 'Android Developer Options' and enable ADB Debugging:
h tt ps://ibb.co/mLikS8
- Run the setup commands in crosh/shell as described in the guide (link above), such as dev_enable_udc , and dr_swap commands. As stated by the guide on developer.android: "Use this command each time you disconnect and reconnect a USB cable. To ensure your Chromebook is in UFP mode, you can run ectool usbpd <port number>" . See attached:
h tt ps://ibb.co/j8m5S8
- Attached the USB-C cable to the W10 laptop and run ADB devices.
- No devices show up in cmd (adb devices)
- Android Studio also does not list any devices to run on
- This is what I'm seeing in Device Manager, a 'malfunctioning adb device'
h tt ps://ibb.co/cpXen8
Any help would be greatly appreciated if anyone has already managed to the ADB USB to work!
Click to expand...
Click to collapse
I have suceeded in doing this in my Samsung Chromebook Pro. There are a few problems off the bat.
1) Chrome OS ships with a very outdated version of ADB
2) There is no rule by default for accepting usb connections from vendors. You have to add it to your rules.d folder.
If you know what you're doing you can install the dependencies directly to your system and update the shipped adb using debian resources. You could also use crouton. I made a tutorial a while back. Things have changed a tab, but not much. tutorial link
Also I will attatch the script I made to automate the process on my CBP. With a little tweaking you could make it work for yourself. I know this probably isn't what you are looking for. But installing the debian resources will almost certainly get it running in the native crosh shell.
Related
ViewSonic viewpad VB71 Android 4 tablet
i try to use SuperOneClick but with not luck
any one know how to root it thx
Have a look at the roll-up sticky in the dev section: http://forum.xda-developers.com/showthread.php?t=1236990
Success on rooting the Viewsonic VB71
rust2014 said:
ViewSonic viewpad VB71 Android 4 tablet
i try to use SuperOneClick but with not luck
any one know how to root it thx
Click to expand...
Click to collapse
Here is my personal experience.
I found that Windows not able to load the USB device driver for the VB71 tablet.
Since Viewsonic does not provide the driver in their support web site, you can download the SuperOneClick software (in fact any software come with the Android USB driver) from cnet.com
Then, plung the tablet to your PC (do not Enable the USB Connection) when prompt by your tablet - Windows XP will prompt that new hardware detected and prompt to install new driver for the “VSM752HC” device (the tablet USB device name). I direct the prompt to use the folder of the SuperOneClick software driver folder - example
“C:\Android software\SuperOneClick\SuperOneClickv2.3.3-ShortFuse\Drivers”
to look for driver installation by windows and windows able to install the driver from there.
Note: Only use the driver of SuperOneClick – this software can only root old versions of Android … not Android 4.x
And you can see that the device now become “Android Phone” in the windows “Device Manager”.
After you have windows installed the USB driver for your Android device. Go and download “Android_Root_1.0” (which support Android 4.x) from sourceforge.net. Unzip it to a folder.
Connect your tablet to the PC with Android USB Debugging enabled and run the downloaded script “ICS_Root_Unlocker.bat” under the “Android_Root_1.0” folder.
It will stop and then start "ADB server" (Android Debugging server) and then prompt you to “hit ENTER key to continue” – wait for the reboot complete and "USB Debugging connection is back ON" before you hit the ENTER key !! This applies to first two reboots.
On the third time, you will not see the machine come back on (seems dead) but wait for a few minutes and just “hit ENTER key to continue” which will complete the final change and perform last reboot.
Just “hit ENTER key to continue” to quit the script.
Note: In the first few trials without success – I was not sure anything is going on and assumes the script is dead. I did a Factory reset on the VB71 tablet to put the Factory setting back before I perform the root script again.
Key points:
- You NEED to install make sure the Android drivers for your phone are installed
- You NEED to put your phone on USB Debugging mode (and connected) for the script to work
- Make sure you DO NOT mount your SD card
- If you still can't get something to run, try doing it in recovery mode (or set it back to Factory settings).
All the best with your rooting !
So I ran into some issues with my HTC Evo 4G LTE when attempting to use it on my Windows 8 laptop that I wanted to post about in case others have the same issue. I did a number of Google searches and while I ran across a number of others who had this same issue, no one seemed to have the fix all in one place, so here's what I experienced and what I did.
First step in CM10.1 is to enable Developer Options. Go to System>About Phone and tap on the build number 6-7 times. I know this is well documented but like I said, I'm putting this all in one place for reference.
Initially when connecting my phone via USB to my Windows 8 machine it would immediately detect it as an external storage device (even when ADB root and Android debugging were enabled in the Developer Options)
The specific driver it kept loading was called Linux File-CD Gadget USB Device under Disk Drives
It would also load as an external drive letter under Portable Devices (in my case F:\)
Finally, under Universal Serial Bus Controllers it would load a USB Mass Storage driver and a USB Composite Device Driver
First, you'll need the Android SDK. This is important for two reasons: 1: The most up to date ADB as it is required in CM10.1 / Android 4.2.x because of the device fingerprinting that Android now does with ADB. Get rid of older versions or you'll end up with the device detected but offline. 2: You need the USB driver installed from the Android SDK.
I tried a number of suggested things to attempt to update the driver for my device with the Android USB driver, some people had suggested installing it over the USB driver, some over the Portable Device driver and some over the Linux File-CD Gadget driver. None of these worked, windows kept returning the following error:
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
What I eventually found is this: After enabling Android Debugging and connecting your phone via USB, you need to go to the View menu in the Device Manager and select 'Show hidden devices'. At that time I was presented with a new section called Android USB Devices. I specifically recall in Windows 7 this was not a hidden area, however it is in Windows 8. Under this heading was a device labeled My HTC. I'm quite sure I never installed the HTC drivers for my phone in Windows 8 so this may be something that is shipped with the OS at this point... or if I did install them I dont recall doing it.
Either way, this is the driver you need to update. Simply right-click, update driver, and replace it with the driver stored in the Android SDK folder (AndroidSDK folder root\sdk\extras\google\usb_driver\). This will load as a Samsung Android driver. Dont worry about it, it works fine.
Finally, as I mentioned before, if you run adb devices and all you see is your phone but it says "offline" and you're sure you have the newest ADB, check your phone screen, it will be asking you to confirm the fingerprint of your machine before it comes online and lets you issue commands.
I hope this helps other people, it was quite a hassle figuring this out, mostly because I didnt expect the driver to be hidden since it wasnt in Windows 7.
Greetings....
(This post is regarding my Nook Touch, however; as I believe the development setup is the same as a Nook Tablet, I am posting here also)
I am hoping to get my Asix Usb to Ethernet adapter working with my nook STG. I believe the only remaining requirement is to compile the drivers for it (which are android 2.x compatible according to the driver manufacturer website).
I am rooted and have 'usb host mode' successfully working.
When my adapter is plugged in, it displays as a 'connected device' in my Usb Host information app and shows the details; make/model etc - so its connected successfully.
It works plugnplay with my other droid devices, however in these devices there is an Asix driver folder in /sys/bus/usb/drivers and there is not in my Nook, thus I believe i simply need to compile the drivers which will create the Asix driver folder.
There are no errors displayed in Terminal Emulator after a typing "dmesg" once connected.
If you have the correct setup and can compile the drivers for me (and potentially other Nook users), i will exchange them for => 10GPB or 10 of your currency, via your desired means.
I was trying myself on an ubuntu vm in windows but have had to stop due to eye troubles; hence trying to use a Nook eink as my sole computer.
INFO:
Device: Nook STG firmware 1.21 - kernel source file link = images.barnesandnoble.com/PResources/download/Nook/source-code/nook2_1-2.tgz
Adapter Driver: Asix AX88772 - driver source file link = www.asix.com.tw/FrootAttach/driver/AX88772C_772B_772A_760_772_178_LINUX_Driver_v4.11.0_Source.tar.bz2
Adapter Info: BobjGear Adapter made for Android Tablets = www.amazon.co.uk/BobjGear-Ethernet-Exceptions-Description-Ultrabooks/dp/B007RTACDM
Other info: An XDA thread compiling the same drivers - http://forum.xda-developers.com/showthread.php?p=37548841
I don't know how to apply the drivers so I need to learn how to do so, I have ADB set up and have Noogie, CWM and NookManager .img also.
My Nook Touch thread - ]http://forum.xda-developers.com/showthread.php?t=2570149
Any other info needed i will provide
Sam
Hi guys, I've been tearing my hair out for the past 24hrs trying to get ADB to communicate with my devices (Amazon Fire tablet + Nexus 5x).
I've installed ADB and drivers for my devices. They currently show up as Android Device > Google Nexus ADB Interface (ClockworkMod driver installed) and Android Device > Android Composite ADB Interface (Amazon.com driver installed).
I have enabled ADB on my Amazon Fire tablet (5th Gen - 5.1.3) and USB debugging on my Nexus 5x.
When I run ADB, all it sees is my Fire tablet but says "unauthorized" next to it.
On both devices, when plugged into the computer via USB, I get no message about enabling the computer to access the device etc. They just sit there, charging with "USB Debugging Connected" on both devices.
Could someone point me in the right direction to get ADB communicating properly with both devices? I originally wanted to use it to root my Fire Tablet to load a different OS on to it, so I used my Nexus 5x to see if that could communicate with ADB but it appears that neither do.... properly anyway.
Another flag that I'm wondering is that in Device Manager, I do have an exclamation mark next to a USB controller - I've found drivers for it (Renesas USB 3.0 Host Controller) - but it came up with an error saying the device cannot start (code 10) - I don't think this is anything to do with my issue as the drivers are installed correctly it appears for the Android devices.
Thanks a lot in advance.
I've done it! I had to delete adbkey from .android folder on my PC - god knows why! all fixed though. yay.
Hello,
This is my first time posting here, I did read the rules and looked for the info before posting but had no luck.
I recently installed two ShenZhen Coresmore Technology Co.LTD Coresmore Car Entertainment tablets (website: h t t p : / / w w w . coresmore . c o m /?page_id=838. I would like to root them so I can use the airdroid/airmirror app to control them from my phone, however all my rooting efforts have been unsuccessful.
I tried kingoroot app (and PC version), and framaroot but neither worked.
I also tried connecting directly to my PC, but the device is not detected. I contacted the manufacture and they told me that the usb port is host only. ( I could not find an device drivers on the manufactures website either).
There is an all in one connector coming out of the back of the tablet, but I could not find any adapters for it that would allow me to connect it to my computer.
The tablet also has a TF card slot, but I do not know if there is a root option that can take advantage of that.
Here is some more info about the tablet
android version 6.0
CPU: Quad-CoreCortex-A53 1.6Ghz
Ram: 2.0 GB
Flash Memory
8.00 GB
Kernel version
3.10.86
Thu May 10 11:43:46 CST2018
Build number: NJ1017-180510-S3383
Any help would be greatly appreciated
Coresmore Rear Entertainment Monitors
psychogator said:
Hello,
This is my first time posting here, I did read the rules and looked for the info before posting but had no luck.
I recently installed two ShenZhen Coresmore Technology Co.LTD Coresmore Car Entertainment tablets (website: h t t p : / / w w w . coresmore . c o m /?page_id=838. I would like to root them so I can use the airdroid/airmirror app to control them from my phone, however all my rooting efforts have been unsuccessful.
I tried kingoroot app (and PC version), and framaroot but neither worked.
I also tried connecting directly to my PC, but the device is not detected. I contacted the manufacture and they told me that the usb port is host only. ( I could not find an device drivers on the manufactures website either).
There is an all in one connector coming out of the back of the tablet, but I could not find any adapters for it that would allow me to connect it to my computer.
The tablet also has a TF card slot, but I do not know if there is a root option that can take advantage of that.
Here is some more info about the tablet
android version 6.0
CPU: Quad-CoreCortex-A53 1.6Ghz
Ram: 2.0 GB
Flash Memory
8.00 GB
Kernel version
3.10.86
Thu May 10 11:43:46 CST2018
Build number: NJ1017-180510-S3383
Any help would be greatly appreciated
Click to expand...
Click to collapse
Hi,
first of all excuse me for my english. Learn english in school is centuries gone. I have the same problem with monitors and Android 8.1. I try to describe my way till yet:
1. Start monitor and do a factory reset in android settings
2. Connect to your wifi-network. Must be in the same network as your computer.
3. Open Google Play Store on the monitor and look for a app called "ssh helper" from Paul Lutus
4. Install and start the app. Notice ip-adress and port.
5. Install "Putty" on your computer
6. Open an SSH-session and connect to the monitor. In my case the credentials "admin/admin" or "root/admin" worked.
7. Connect an USB-Keyboard to the monitor.
8. In the "Putty"-shell type reboot bootmanager and press enter. The monitor should reboot and showing the bootmanager menu
9. Look for an option "show recovery logs" ore something similar
10. In the log you should find a line with content "adb connect" and a port
11. Download Android debug bridge on your computer and unzip in a folder. Use Google search to find it.
12. In the directory type "adb connect [ip-adress of monitor]:[port shown in log above]
13. Now you can use all Android ADB commands. If you use "adb shell" you will get a session via wifi. If you type "su" without any other letters, the commandline will switch from "$" to "#".
14. When you try "whoami" in the commandline, the session should answer with root.
15. Now you can remount folders or root folder with read/write permissions, change Ownership of files or folders, download, edit and upload files, e.g. init.rc. Try a Google search for all ADB-commands.
But be carefully...operations at a opened heart are dangerous.