Yeah. So I was thinking on some good Android wear apps to maximize my experience with my Huawei Watch (WHYYY) and just remembered that sideloading was a thing. But, I dont know how to do it and if it's compatible and possible on Wear 2.0
I'm on a Mac, but it has full ADB and Fastboot access.
This in the Huawei watch forums. I've had no luck with sideloads, a mass of changes in 2.0.
https://forum.xda-developers.com/huawei-watch/general/android-wear-2-0-apk-installer-t3472766
Related
hello,
I wonder if one day it will be possible to proceed to the root of the machine without going through the adb android SDK?
Thank you
Anything is possible I suppose but being able to use ADB is something everyone who wishes to tweak needs to at least have a passing knowledge of. Even "one-step roots" sometimes go awry. Being able to use ADB could well be the only (if not best) way to un-brick!
Ok, just because SDK + Eclipse for mac, update and more is too big just for a root.
But I understand your reply.
Does anyone use the micro usb port? I have yet to find a use for it. I can't transfer files with it, charge with it nor are there any peripherals (that I know of) that can use it. I searched around but couldn't find much useful stuff on the port. All I found was this useless video:
**Ok I can't post the video because of more stupid forum rules but just go to youtube.com and append this after the url: /watch?v=1xBVu-IatDQ **
Anyway, if someone has ideas on how this port can be used I'm all ears... Thanks.
dq
It is a file transfer port. you plug a cable into it and into your PCs usb port. works like the ones on your phone.
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
What OS are you using on your computer, and have you installed the drivers for it?
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
Computer OS? i just plugged it into my Win7 system and it was there instantly. 3.0 shows up as a media device, which allows both the tablet and the computer to talk to the sdcard at the same time. So you won't see a mount prompt on the tablet. BTW my Incredible2 is running 2.3 and also lets me access the SD card on it and the computer at the same time.
I'm still using an old tiny xp and it worked fine for me just plugged it in and there it was
I tried Gentoo Linux and XP and neither worked. What drivers do I need to install?
I also have access to a Win7 system so I'll try that.
dq
Drivers from acer website.
I have adb installed should this not be enough?
You need none installed. ADB if its running in some form might be interfering. its just a basic driver in windows it uses.
I only run adb-server when I need it and not all the time. I thought that any needed drivers would have been installed when I installed adb.
For my Gentoo machine what should I do? It's not detected at all if I plug it in. My x10 mini and Nexus One are detected no problem and I can mount them and everything so what's up? Is there a kernel module that I need to build?
Thanks.
dq
I had to download these drivers for my xp netbook ,,
http://global-download.acer.com/GDF...A Tab&Step3=A500&OS=a05&LC=en&BC=Acer&SC=PA_6
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Yes, well I only really use adb in the same capacity as what you describe-- to root a device. After that busybox can be installed and I can either ssh into the device (which I prefer) or use the terminal on the device itself.
But my problem is the detection of the device once it is plugged into my Linux box. I'm not sure if I need a special driver for that and I'd rather not aimlessly search through the kernel config in order to build one (I've done that before and it's painful!). It's good to know that one can mount it on an external device and still use it simultaneously though. That will save me time in trying to fiddle around with settings in the tablet itself...
dq
don quixada said:
I have adb installed should this not be enough?
Click to expand...
Click to collapse
If you are not able to transfer files Try enabling usb debugging before connecting to pc.
If the tab is not in the usb devices list and it doesn't show up as an unknown device, you might want to try another usb cable. Or another port if you have the Windows and Linux on the same machine and you are trying to connect on the same port.
Sent from my A500 using XDA Premium App
gradyzero said:
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not nearly what I was saying. Not even close enough that a bomb would touch it.
Simple answer is my vista and win7 systems accessed the iconia as a media player device requiring no drivers as they are a common system driver. My only comment about ADB was that it might be interfering if it somehow was left running in the background.
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
sandiegoan said:
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
Click to expand...
Click to collapse
Sometimes mine gets a bit wonky as well. Every now and then, I'll plug it in, get the windows dialogue box asking me what I want to do. I open it up and the box is blank, no drives, nothing. Unplug it, wait a few seconds, pop it back in, and everything is OK. No rhyme or reason, and it doesn't happen all the time.
Quick trick for win7 .
Plug in the device.go into device manager delete its entry and the USB controller it resides on.unplug device.install driver from acer web site.then try the device again.
This works on several USB type issues
Good luck if you don't understand don't try
I just got my Moto X Play and wanted to root it and flash CM13. I installed the Google USB Drivers to get Windows to recognize the ADB interface, and getting into fastboot mode with ADB works just fine. But once there, "fastboot devices" fails to recognize the device. The device manager shows an unrecognized device "Fastboot lux S" for which the google USB drivers don't work. I've read that this should be fixed by installing the official Motorola drivers, but I would like to avoid that if possible - I'm doing this to get rid of the Motorola crap, installing more of it on my PC to do so would be disappointing.
So, I've got a heap of questions:
- Can I use fastboot on Win7 without installing Motorola-specific drivers? It seems that there should be a generic driver for the fastboot interface as it's a feature on all modern android devices AFAIK.
- Is it possible to use Linux to connect to the device via fastboot? I doubt there's a Linux driver from Motorola... but if it's possible to get fastboot access, I'd just boot a live CD and do the unlock from there.
- Does my objection to the Motorola Drivers make sense? Are there any benefits to having the drivers installed if I flash CM on the device?
The drivers are irrelevant to the OS you want. You need the drivers, install the drivers. Your computer is trying to talk to the phone, and right now they are speaking different languages, the driver is an instruction on how to talk to the phone. It has very little to do with Motorola, google didn't build your phone, they supplied the OS. Fastboot is effectively the BIOS of your phone, imagine what would happen if you flashed the wrong BIOS on your computer., would you call Microsoft and say fix it? no.
Install the damn drivers and get over it.
ImWarped said:
It has very little to do with Motorola ...
Click to expand...
Click to collapse
That's exactly why I asked, I thought this was a standartized part of Android for which there might be a generic Windows driver - I guess that's not the case, thanks for the clarification. But I googled around and unlocking under Linux seems to work (and without requiring a driver), so I'll try that first.
fckmoto said:
- Is it possible to use Linux to connect to the device via fastboot? I doubt there's a Linux driver from Motorola... but if it's possible to get fastboot access, I'd just boot a live CD and do the unlock from there.
Click to expand...
Click to collapse
fckmoto said:
I googled around and unlocking under Linux seems to work (and without requiring a driver), so I'll try that first.
Click to expand...
Click to collapse
Since my wife moved to an Android phone, our house is Microsoft free. Being a fairly novice user who likes to tinker, this always introduces extra layers of doubt and uncertainty ...even fear, at times. I am forced to wonder, in the presence of all the Windows software and Windows-based procedures and advice, does it work on Linux?
My answer, so far, over three phones, is that if it is adb or fastboot stuff, then, yes it does. Or, at least, so far, everything I've tried works.
Depending on your linux distro, you might have to install some extra package containing those commands. You might want to install the whole Google android package. 99.999% developer stuff, but includes the two commands that you want. It's probably more up-to-date than the Linux-distro versions.
You might have to insert a line with some manufacturer ID (I didn't for the X Play) in some configuration file.
Look... my anti-MS biases show even through a thick overcoat. But do the linux thing only if you want to do linux. By the time you've read this post, you could probably have installed those drivers .
Does my objection to the Motorola Drivers make sense?
Click to expand...
Click to collapse
No.
Thad E Ginathom said:
No.
Click to expand...
Click to collapse
Heh, I guess it's somewhat thick-headed to look for alternatives instead of just installing the drivers. My main problem with that is that Motorola doesn't offer a direct download of the driver but wants me to install a driver manager tool instead... I've kept my pc crapware-free thus far and intend to keep it that way If it's as simple as installing a few Android dev packages under Linux, I'll definitely take that route.
But with bash and the full Canonical repositories coming to Win10, maybe one could use the Linux adb and fastboot binaries under Windows in the not-so-far future... I wonder if those would then work without a device driver
Install 15 seconds adb 1.4.3 and run it in your fastboot folder you create in C of Windows7, no Motorola drivers.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
I dont have a laptop to move near my Shield Tv to use adb. Could all the same be done on my Android phone using Terminal Emulator, or does that over-complicate rooting the Shield Tv?
No help yet....?
Well first you'd have to have adb/fastboot and you'd have to have driver's to connect to device.
I fly racing drones and have seen a clean flight app for configuring flight controller changes. That involves connecting your quad flight controller to your Android device with a USB cable. Typically you would use a PC with drivers very similar an operation to running fastboot to root your phone. I think it comes down to which device is running command prompt can connect with its drivers to the Target device
You should post in other forums like in adb development forum or Nexus up forum.
I suppose I could try it for the yucks... But, since your the One asking? Why don't you just download a Terminal Editor (From the PlayStore), which should allow you to use (e.g. emulate), ADB at the least of it. Not sure if it'll be of much help to you at the Fastboot Level though.
TBQH: I'm not sure this is the best plan of attack. As you would almost have to be very meticulous here, as to not accidentally flash your Phablet with the Shield TV Firmware, or vise-versa.
*EDIT*
Just outta ****s, and giggles I decided to just try it out to see how far One could get with it. As it turns out, you can at least get into the Fastboot System like this. However since I don't have anything like Fastboot, or ADB as a callable executable (From Emulated Android Terminal), I can't issue any Fastboot commands durr.
It could be interesting to look Into if there isn't an Android OS version of Fastboot that could be ran from the Terminal. But, my guess is there wouldn't be. As 99.9% of Devices out there don't require you to be patched into a USB Host just to get into Fastboot / Update / Recovery Mode. And for the times when you do need a PC there is bespoke Software like Kies, or Odin out there to make that task simpler.
*EDIT II*
A quick shufti on ATE, and Fastboot brought up this Gem.
http://www.nairaland.com/2351005/how-set-up-run-fastboot
Of course the usual caveats about being Rooted, (The Device from which you plan to root from. e.g. your Phablet), apply.
I've tried this with my Nexus 6p. 7.1.1 Pure Nexus ROM. ElementalX Kernel. Rooted. I used the included USB C to USB A cable and was never able to get the Shield to show up under adb devices.
I ended up just splicing two broken micro USB cables. You just cut and match the colors. I didn't even seal the wires. No solder, no electrical tape. No heat shrink. Just made sure none of the splices were touching and it worked just fine on my laptop connected to the shield TV 2017. These were USB 2.0 cables. But make sure they're data cables and you shouldn't have any issues.
I personally tried many versions of adb for Android and could never get the Shield to show up. So I just gave up and make the USB A male to male cable and did it the right way.
Sent from my Pixel+XL using Tapatalk
I have developed apps for Android and Wear OS watches – mainly for personal use. It's no problem for me to use ADB to Install to a watch.
But, I would like to install the APK on a friend's watch, who is not a developer or very technical. It Would be nice to be able to do this without a lot of rigmarole. I can enable Developers Options on his watch, but installing ADB to his PC is asking a lot. It would be nice to have a PC app, hopefully that is portable and can reside on a flash drive, that will simply interface with the install protocol to install an APK on the watch.
Does something like this exist?
Barry.
A little more searching and I found this, Flakie's ADB GUI:
Direct download:
https://flakie.co.uk/downloads/FlakieADBGUI.zip
There is a GUI for the common ADB commands and an integration with scrcpy (as in version 1)
It now has an experimental option to use ADB and ADB Shell commands by typing/pasting them in.
I have not actually tested it, but it seems to be exactly what I was looking for.
I downloaded ADB and put the "platform tools" folder on my Flash drive. I also put Flakie's on the flash drive along with the APK I intend to eventually install.
Theoretically this should give me a portable install for the APK (fingers crossed). I am hoping to connect to my friends watch via Wi-Fi and use Flakie's to install the APK.
As an alternative, there is also ADB AppControl. It is well known, and the developer has it quite improved.
ADB AppControl
Official website of the ADB AppControl application. Free Download. Latest release. The ultimate applications manager and debloat tool for Android devices.
adbappcontrol.com