Database Users

Installing TWRP. Stuck at "waiting for device"

I'm getting this issue with Kindle Fire Utility when trying to install TWRP;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have rebooted my kindle fire while waiting for it, but I haven't been able to find other solutions, please help! I'm fairly sure that I have ADB working... I'm really not sure what to do

georgeos said:
I'm getting this issue with Kindle Fire Utility when trying to install TWRP;
I have rebooted my kindle fire while waiting for it, but I haven't been able to find other solutions, please help! I'm fairly sure that I have ADB working... I'm really not sure what to do
Click to expand...
Click to collapse
If you would have followed my tutorial you wouldnt have this problem here is the fix:
• I have noticed that some people have problems getting stuck around 2:32 into the video where twrp is downloading and getting ready to install. If this happens to you and it is constantly “waiting for device” You may need to hit disconnect on your KF and run burrito root on your Kindle again, click “agree”,then click “You Rock”, Then click “root”. Once you do so you must re-open adb shell by opening a command prompt and typing the following:
cd c:\KindleADB this is to get into adb shell
adb devices this is to make sure your kindle is connected properly
adb root this is to get proper permissions
Just to be very clear on what you should type in your cmd prompt:
cd c:\KindleADB
adb devices
adb root
• Once you have done this re-open the run bat in KFU v0.9.1 and select option 5 again and it will install the twrp with proper root permissions.
here is a link to my tutorial for you to check if you have more problems afterwards:
http://forum.xda-developers.com/showthread.php?t=1417234

[-_-] said:
If you would have followed my tutorial you wouldnt have this problem here is the fix:
• I have noticed that some people have problems getting stuck around 2:32 into the video where twrp is downloading and getting ready to install. If this happens to you and it is constantly “waiting for device” You may need to hit disconnect on your KF and run burrito root on your Kindle again, click “agree”,then click “You Rock”, Then click “root”. Once you do so you must re-open adb shell by opening a command prompt and typing the following:
cd c:\KindleADB this is to get into adb shell
adb devices this is to make sure your kindle is connected properly
adb root this is to get proper permissions
Just to be very clear on what you should type in your cmd prompt:
cd c:\KindleADB
adb devices
adb root
• Once you have done this re-open the run bat in KFU v0.9.1 and select option 5 again and it will install the twrp with proper root permissions.
here is a link to my tutorial for you to check if you have more problems afterwards:
http://forum.xda-developers.com/showthread.php?t=1417234
Click to expand...
Click to collapse
I tried what you said, and have made some progress, the Kindle Fire is rebooting when it comes to say "waiting for device" but then gets stuck at boot, so I have to put it back to normal boot rather than fast boot

georgeos said:
I tried what you said, and have made some progress, the Kindle Fire is rebooting when it comes to say "waiting for device" but then gets stuck at boot, so I have to put it back to normal boot rather than fast boot
Click to expand...
Click to collapse
Once again all of the answers to your problems and the questions you have are in this tutorial. From what it looks like to me from your screen shot you do not have "root Permissions" if this is in fact the problem then what you are probably trying to do is to start at step five from the Kindle Fire Utility and download to install twrp2.0 If this is what you are trying to do then you must see on the command prompt of KFU that you are downloading and then waiting on device. If this is still your situation then the fix is what I stated above and in my link. If you have gotten passed that problem and still have issues with you either being stuck at the yellow triangle( firefirefire ) or a Kindle Fire boot screen that will not go away then the fix is also in my link... If you do not wish to follow the link and see the videos or read through the trouble shooting guide then I am afraid I have no way of helping you...
If I helped please do not forget to hit the thanks button and post back in my guide thread that it worked okay for you as well so that new members can see that this is one of the easiest guides to follow here is a link to take you to that guide a little quicker good luck....
http://forum.xda-developers.com/show....php?t=1417234
If you need further help reply in that thread and I will be more than happy to help you there so others can find the fix to the problem that you come across a little easier

I got stuck in several places when I did it, the issues I had where an old version of adb, and drivers, had to uninstall and reinstall the drivers
Sent from my Kindle Fire using xda premium

[TOOL] Android Wear APK Tools: Sideload and Uninstall Apps to Android Wear

Android Wear APK Tools:
A GUI application which allows you to install any APK straight to your watch (via adb) or uninstall any non-protected package directly. Much more convenient than doing it through the adb command line.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to use:
Download Link: HERE
Windows:
Unzip Android-Wear-APK-Tools.zip, and run Android-Wear-APK-Tools.exe
Linux:
Run the following command in terminal, and then open AndroidWearAPKTools.py
Code:
sudo apt-get install python-tk
Mac:
Install Python from here, then run AndroidWearAPKTools.py
_________________
Connect your watch to your computer, enable ADB Debugging on your phone and your watch, and make sure ADB and the drivers are set up on your computer.

Doesnt work for me.
I opened it, clicked connect to watch, then it told me that it has connected, i can see the list of all the apps that i have installed on my phone. But android wear doesnt tell me that its connected.
I tried to uninstall an app, then it gave me an error. Then i tried installing an app, and it just stayed on "installing app, please wait" for a very very long time.

So, apparently you must have ADB already on the system path or in the main directory of this application and it must be accessible with the command "adb"

I am experiencing similar errors with the app. It tells me I am connected to my watch. I can't see any apps on the list. When trying to install an app it stops on "Installing app, Please wait..."

root required?
Does this require that the Android Wear device be rooted?

Lord_Cyrix said:
I am experiencing similar errors with the app. It tells me I am connected to my watch. I can't see any apps on the list. When trying to install an app it stops on "Installing app, Please wait..."
Click to expand...
Click to collapse
same here

can we install ota lollipop from this
by regular method my samsung gear live is not responding to sideload method

doesn't seems to work on windows 10
Exception in Tkinter callback
Traceback (most recent call last):
File "Tkinter.pyc", line 1470, in __call__
File "AndroidWearAPKTools.py", line 36, in connectToWatchCallback
IndexError: list index out of range
EDIT:Fixed by allowing adb access through cmd

works for me
In samsung gear neo 2 ported to android wear, works perfect thx...

NightMean said:
doesn't seems to work on windows 10
Exception in Tkinter callback
Traceback (most recent call last):
File "Tkinter.pyc", line 1470, in __call__
File "AndroidWearAPKTools.py", line 36, in connectToWatchCallback
IndexError: list index out of range
EDIT:Fixed by allowing adb access through cmd
Click to expand...
Click to collapse
NightMean, how did you fix it? Could elaborate?
I don't know how to allow ADB access through CMD
Thanks

nagasgura said:
Android Wear APK Tools:
Much more convenient than doing it through the adb command line
Click to expand...
Click to collapse
So writing all that code was easier than "adb install" ?

clevebb said:
So writing all that code was easier than "adb install" ?
Click to expand...
Click to collapse
Not for him (except he installs and deinstalls applications from 9 to 5 )
But for the rest off the world it´s really comfortable

I installed google chrome but i cant see it in the list of apps installed and i cant uninstall it any help? this is the list http://puu.sh/pc5Ka/0e12811101.png

Thanks for creating such a simple but useful tool!

Hy guys , i've used this method to install apps but i have a problem when opening a pdf file , as you can see in the pictures , i can't select a default app for it. can somebody give me a solution ? thx a lot .

kmc99 said:
Hy guys , i've used this method to install apps but i have a problem when opening a pdf file , as you can see in the pictures , i can't select a default app for it. can somebody give me a solution ? thx a lot .
Click to expand...
Click to collapse
Try opening the PDF on your phone instead.

For me, I connect to watch alright, I see the apps list, but uninstalling takes forever.. :/
Much easier to use adb command. meh

My watch is detected by the pc but I see an empty directory ....and if I try to copy a file no way ....

Any idea ?

So the windows 10 users have no chance to enjoy this ???

ADB driver connection

Has anyone been able to get the Turbo 2 to connect via ADB? I have debugging selected and the drivers says installed correctly for Android ADB interface in the Windows device properties. Yet Helium doesn't connect and adb devices command returns nothing.
Anyone been able to get adb interface running on Turbo 2?

rayjr13 said:
Has anyone been able to get the Turbo 2 to connect via ADB? I have debugging selected and the drivers says installed correctly for Android ADB interface in the Windows device properties. Yet Helium doesn't connect and adb devices command returns nothing.
Anyone been able to get adb interface running on Turbo 2?
Click to expand...
Click to collapse
Yes but I know if you update to Windows 10 it can cause issues you need to reinstall moto drivers
Sent from my XT1585 using XDA Premium 4 mobile app

My Turbo 1 connect just fine not T2 I'll try it again when the wife brings it back

I had a small issue. I think mine cleared up when I installed Vysor, and installed the drivers through that.
http://koush.com/post/universal-adb-driver
Give this a shot and let me know how it goes. btw, Vysor is pretty fun.

Solution update (2017-2018 version) for recent Ubuntu-based Linux and Windows 10
(NOTE: I am unable to post complete URLs due to having an insufficient number of XDA Forum posts at this time. The bulk of this post and the information contained within is available by searching for my GitHub account (maxieds) and selecting the most obvious pinned repo description. My GitHub page is also linked off of my XDA Forum profile just to be clear. )
Preface: I realize that this thread is somewhat dated, but so is this antique 2015-era phone, so I figured it's worth pointing out a recent solution to those patient Google searchers who like me are still using the device. This solution (works for me on a recent 2017 Debian-derivative Linux box, and/or a loaner Windows 10 laptop) is to avoid the proprietary Motorola software and drivers you will stumble onto from the official ADB links from Android Studio. All you need is the standard Google USB drivers and a more recent list of phone USB device ID properties. I haven't tested, and so cannot confirm, but I suspect that this method should get ADB up and functioning on other hard-to-configure deviant phones using the list of Linux udev supported configurations from this recent (and often updated): <GITHUB>/M0Rf30/android-udev-rules. My modification for the DROID TURBO 2 phone is forked <GITHUB>/maxieds/android-udev-rules. If you find this information helpful, I'd appreciate it if you would STAR my repo on GitHub (<GITHUB>/maxieds/android-udev-rules/stargazers). As a variant of the the old Unix joke goes in obscure 20-year-old Slashdot references: How do we fix Windows? ... Well, I propose we port WINE to Windows ... With this in mind and in this spirit, let's port the oh-so-wonderful Linux UDEV config to Windows.
NOTE: the DROID TURBO 2 didn't work out-of-the-box on Ubuntu either however, even after installing other variants of the udev rule sets, so my mod is necessary to fix at least this stubborn class of Motorola devices. One possible explanation for why this device doesn't work like nearly every other Android phone is a USB3 bug where file explorer, etc. works on the same USB port, but ADB fails. The purported non-software work around is to chain the phone's USB connection in serial to a cheap self-powered USB hub that effectively masks this bug, but I had no such luck with this experimental fix and of course your mileage may vary. More likely, the cause is that the phone preempts the typical detection sequence by changing the id of it's ATTR{idProduct}=="2ea4" to ATTR{idProduct}=="2ea5" (or some other related ID) when it is connected through USB debugging for use with ADB. See the following image detailing the respective dmesg and lsusb changes pre/post enabling USB debugging on a device connected via USB in Linux:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
===== Ok, so here, goes with the updated device details: =====
Recent (2017,2018) Solution for Using the DROID TURBO 2 Phone with ADB:
Recently, I finally got into Android development using my Motorola DROID TURBO 2 phone ... only to find that the phone isn't recognized out-of-the-box on either Linux or Windows. After searching around for a while, I finally have found a solution on Linux, which I then "ported" to Windows 10 using the stock Google USB drivers which are easy to find and install with Android studio. The solution is essentially this:
on Linux (after installing Android Studio / ADB / Android Tools in Ubuntu):
Use this updated udev file to get the TURBO 2 recognized: <GITHUB>/maxieds/android-udev-rules. The working forked file basically required setting a few non-standard udev options and inputting the complete device spec found with
Code:
lsusb
LSUSB Outputs: Bus 001 Device 0XX: ID 22b8:2ea5 Motorola PCS, where the XX is a decimal integer local to the running linux box
Click to expand...
Click to collapse
. After following the instructions at the referenced link, running
Code:
adb devices
from your favorite terminal should display the device. Now happy ADB and Android debugging to you and your ancient phone! (AND please be sure to STAR my repos!)​
in Windows 10 (Enterprise): First, install the Google USB Driver using the SDK manager in Android Studio (under Extras). This puts the driver files in (on my local text box) "Program Files (x86)\Android\android-sdk\extras\google\usb_driver\*". I had to right-click, install and enter the administrator password for the local box to install this. At this point, you can open up "Computer Management > Device Manager" (as ROOT) and see if your phone is automatically recognized by the stock Google USB driver. Mine is not, so we have more work to do. From the GitHub repo (<GITHUB>/maxieds/AndroidADBExtraUSBConfig) I have created, copy the two files under android_google_usb_driver_mod into the default folder for the Google USB Driver files (linked on Windows 10 as above). Repeat the process to install the driver.
Hopefully, now you can get the Motorola DROID TURBO 2 device up and developing with ADB and Android Studio! :good:
---------- Post added at 09:40 AM ---------- Previous post was at 09:32 AM ----------
Since I was unable to post the links to the GitHub repos relevant to the recent solution to this problem, maybe this will get past the XDA Forum filters. Here's a QR-Code to the Wiki page on my repo where you can find complete information and files for implementing the custom USB setup needed to get the DROID TURBO 2 phone working out-of-the-box with ADB under Android Studio: <img src='https://chart.googleapis.com/chart?cht=qr&chl=https%3A%2F%2Fgithub.com%2Fmaxieds%2FAndroidADBExtraUSBConfig%2Fwiki%2FFirstBootConfigurations&chs=180x180&choe=UTF-8&chld=L|2' alt=''>. A link to the original image file (which should have been displayed in the above post) using the repo site is also provided as follows: <img src="https://github.com/maxieds/AndroidADBExtraUSBConfig/blob/master/images/idproduct-discrepancy-illustrated.png" alt="" />.

Debian Jessie armhf NATIVE boot by multirom Nexus 7 2013

Desktop environment: Mate.
What work?
Wi-Fi - automaticaly connect by using android config
Bluetooth
Xorg server
Audio
What doesn't work:
qemu-i386 + wine
Network Manager applet don't show network connection icon.
Download:
https://drive.google.com/file/d/0B-6iiCUyzZjWZVpKS3EwcjBpZ0k/view?usp=drivesdk
Install:
Install Debian_Jessie_ARMHF.mrom File by twrp multirom.

Working with LTE 2013 ^^

Boots on WiFi only "Flo". Need to figure out WiFi to confirm, but I think gnome will work as a better interface. Much more touch friendly.
Sent from my SM-N910T3 using XDA-Developers mobile app

That is really awesome! Habe been looking for something like this for a long time.
How does one bring up a keyboard?

Failed...
Hi, that was the ROM I was looking for!
I downloaded the ROM from the above link to a USB drive, then I tried to install that ROM on my Nexus 7 2013 device as a secondary ROM besides Cyanogenmod 13 with Multirom TWRP 3.0.0-0, but it failed with following messages:
Code:
Updating partition details...
...done
Full SELinux support is present.
Installing ROM Debian_Jessie_ARMHF...
Free space check: Required: 1500 MB, free: 29118 MB
Creating folders and images for type 9
Disk size: 30703664
Freesize: 29817632
Space Required: 1536000
Creating root.img...
MTP Enabled
Debian Jessie ARMHF by Szybol. GG: 12352244
Extrating tarball rom/root_00.tar.gz...
Failed to extract tarball rom/root_00.tar.gz for folder root!
Failed to extract base root
Erasing incomplete ROM...
Any idea what's been going wrong?
Thanks, Heinz

You want install debian on usb stick, simple set root's image size to 4000MB.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
New distro comming.
Ubuntu Xenial
View attachment 3726433

Oh no, I wanted to install Debian on the Nexus 7, not on the USB stick. How do I do that? Must be quite simple, but I have no idea...
Heinz

Do you have Access to folder: /data/media/0/multirom/roms ? On this location can you find folder internal or cyanogenmod?
Your device is flo "wifi" or deb "LTE"?
If you have this path and folders you can install Debian manualy.
You must have busybox installed!
I wait for reply, then i post next steps to extract Debian archive

Szybol said:
Do you have Access to folder: /data/media/0/multirom/roms ? On this location can you find folder internal or cyanogenmod?
Click to expand...
Click to collapse
Yes, I have access to this folder. My device is rooted. And there is a folder "Internal".
Your device is flo "wifi" or deb "LTE"?
Click to expand...
Click to collapse
It is the "deb" version with LTE.
If you have this path and folders you can install Debian manualy.
You must have busybox installed!
Click to expand...
Click to collapse
Busybox is installed, it's version 1.24-meefik.
Thank you for supporting me! My English is not the best, I live in Germany.
Heinz

Copy file to /sdcard and run in terminal or adb commands
[email protected]:/# adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
[email protected]:/ # cd sdcard
[email protected]:/sdcard # unzip /sdcard/Debian_Jessie_ARMHF.mrom
[email protected]:/sdcard # mkdir /data/media/0/multirom/roms/Debian
[email protected]:/sdcard # mkdir /data/media/0/multirom/roms/Debian/root
[email protected]:/sdcard # cp /sdcard/root_dir/rom_info.txt /data/media/0/multirom/roms/Debian
[email protected]:/sdcard # tar -C /data/media/0/multirom/roms/Debian/root -xpzvf /sdcard/rom/root_00.tar.gz
[email protected]:/sdcard # tar -C /data/media/0/multirom/roms/Debian/root -xpzvf /sdcard/rom/root_01.tar.gz
[email protected]o:/sdcard # tar -C /data/media/0/multirom/roms/Debian/root -xpzvf /sdcard/rom/root_02.tar.gz
Click to expand...
Click to collapse

It stays stuck at Google Logo(after I've chosen Debian in Multirom) for me. I waited about 30 Minutes.

I Now I have a working GUI with root privileges, thank you Szybol! Even a wireless keyboard and mouse works, with the USB plug on the other end of an OTG cable. The next is to get the wifi and mobile network working...

The point all this is to have dock station with some usb's.
Wireless keyboard, mouse.
And hdmi to monitor, tv.
Of course OS must support second screen.

bluetooth devices
Has anyone test bluetooth keyboard and mouse yet ?
Considering before install

Does it have the same bugs, that the native Arch port had, like issues with rotating the screen or breaking the whole system while updating it? Does the framebuffer output work?

Tried pairing my bluetooth keyboard, sadly it fails everytime for me
Is there anyway to set screen rotation to horizontal? Tried that, but it made Debian crash

witti96 said:
Does it have the same bugs, that the native Arch port had, like issues with rotating the screen or breaking the whole system while updating it? Does the framebuffer output work?
Click to expand...
Click to collapse
RodrigoDavy said:
Tried pairing my bluetooth keyboard, sadly it fails everytime for me
Is there anyway to set screen rotation to horizontal? Tried that, but it made Debian crash
Click to expand...
Click to collapse
The driver that is being used for hardware acceleration (freedreno) does not support rotation on our GPU (Adreno 3xx). Unfortunately, when tried, the driver crashes and takes the entire X-Server with it. If you look in the arch thread, you can find that I had even attempted building freedreno from source with the hope that upstream has this issue fixed, but sadly they do not. That said, the framebuffer works, it's just that the refresher built into the MSM driver is broken. So a separate software refresher needs to be used in order to see anything via the FB. If you don't care much about hardware acceleration, you can easily install an alternative framebuffer driver such as fbturbo or the like, however you'll need to do some hacky work to get X to initialize properly with them. In my custom arch image, I had to make a systemd unit that first started X using a freedreno configuration file, then killed X and started it properly using fbturbo in order to get it to work properly.

How to connect to a WiFi network
Thank you for your work, it is awesome. But i don't understand how to connect to a WiFi network... Can you please explaine me this? Many thanks

jiocol said:
Thank you for your work, it is awesome. But i don't understand how to connect to a WiFi network... Can you please explaine me this? Many thanks
Click to expand...
Click to collapse
It uses the wifi configurations of your android tablet. So if you have your wifi configured on the android it should connect automatically on Debian. (even if it doesn't indicate so)

[=RodrigoDavy;66834836]It uses the wifi configurations of your android tablet. So if you have your wifi configured on the android it should connect automatically on Debian. (even if it doesn't indicate so)[/QUOTE]
Ok, great, many thanks

How to ADB when head unit has USB A sockets?

I am trying to get the ADB working so I can root my device, it has USB A sockets on....so I bought a USB A Male to Male cable but when I plug in the computer doesn't even recognise anything is plugged in.
I presume this is because the USB A socket on the head unit is in host mode.....is there a way to change it?

I have the same problem with Allwinner quad-core t3 k2001 based unit. Can't find solution either.

I would not hold my breath waiting for a reply. Not had any luck here myself getting information but I did see something about using adb over wifi. Not tried it yet myself but I understand that is the way round it. Not got a link but if you google it there are some answers. Of course, that's only going to be of any use if the unit has wifi.

You probably need to enter developer mode and change the USB port from host to device. That usually involves tapping the build number 7 times in the About menu and entering a password. You will have to search for the specifics to your unit.

I'm going to test in a few days. It's necessary to activate developer mode and install in your computer the driver that matches with the concrete Android chipset. Links to download sites for several manufacturers are in https://www.google.com/url?sa=t&sou...FjAGegQIBRAC&usg=AOvVaw3bRtfdRuhK13_oV6PN8EhO
After that it's necessary to use ADB or Android Studio, that includes it. I have tested with a tablet and I'm waiting now for a male to male type A-A cable.

Excuse me. When a real Intel architecture, the driver is here: https://software.intel.com/content/...les/intel-usb-driver-for-android-devices.html
All links are in Android Developer. Search "Install OEM USB drivers". Some links are direct but another ones go to a more generic Web and require to search in.

Pacovich said:
Excuse me. When a real Intel architecture, the driver is here: https://software.intel.com/content/...les/intel-usb-driver-for-android-devices.html
All links are in Android Developer. Search "Install OEM USB drivers". Some links are direct but another ones go to a more generic Web and require to search in.
Click to expand...
Click to collapse
Why don´t you use ADB via WiFi?

rigattoni said:
Why don´t you use ADB via WiFi?
Click to expand...
Click to collapse
As far as I know, if you want to connect from ADB through WIFI it is neccesary a first time through a USB cable in order to execute a command "adb tcpip 5555". Since then you will can execute a command "adb connect 192.168.x.x:<port>" and continuing through WIFI. I know you can activate ADB on device launching commands on an Android terminal emulator. But, as far as I know, you will need root and you can damage the unit.

Pacovich said:
As far as I know, if you want to connect from ADB through WIFI it is neccesary a first time through a USB cable in order to execute a command "adb tcpip 5555". Since then you will can execute a command "adb connect 192.168.x.x:<port>" and continuing through WIFI. I know you can activate ADB on device launching commands on an Android terminal emulator. But, as far as I know, you will need root and you can damage the unit.
Click to expand...
Click to collapse
Sorry this is not true.
You don´t need root to get ADB working and I never heard from someone who just used these both commands and bricked his device....
Code:
setprop persist.adb.tcp.port 5555
setprop sys rkadb.root 1
...and then reboot.

rigattoni said:
Sorry this is not true.
You don´t need root to get ADB working and I never heard from someone who just used these both commands and bricked his device....
Code:
setprop persist.adb.tcp.port 5555
setprop sys rkadb.root 1
...and then reboot.
Click to expand...
Click to collapse
I have test the first command you propose in a tablet and I receive the response
setprop: failed to set property 'persist.adb.tcp.port' to '5555'
I suppose it is necessary a "su" prefix.
See that: https://www.it-swarm.dev/es/android/como-puedo-conectarme-android-con-adb-sobre-tcp/969881143/

Pacovich said:
I have test the first command you propose in a tablet and I receive the response
setprop: failed to set property 'persist.adb.tcp.port' to '5555'
I suppose it is necessary a "su" prefix.
See that: https://www.it-swarm.dev/es/android/como-puedo-conectarme-android-con-adb-sobre-tcp/969881143/
Click to expand...
Click to collapse
I have a Tasker task for that. It´s just one click solution after updating on my units, so I don´t use a command prompt to put it in every time...

Pacovich said:
I have test the first command you propose in a tablet and I receive the response
setprop: failed to set property 'persist.adb.tcp.port' to '5555'
I suppose it is necessary a "su" prefix.
See that: https://www.it-swarm.dev/es/android/como-puedo-conectarme-android-con-adb-sobre-tcp/969881143/
Click to expand...
Click to collapse
You tested this in a Android tablet? However, I believe the head units we have are different to Android tablets (using different firmware and setprop includes the property for persist.adb.tcp.port option), and will accept the command.. even without root / su permission. I have been able to run this abd commands on a few android head units (px3 / px6) and had no issue, without root..
There is no risk involved trying to use the listed commands on a head unit, if the command isnt possible it will just tell you as mentioned it will fail to set the property.. you will never be at risk of bricking your head unit by trying to set adb tcp port for WIFI adb access... the risk would be after you have obtained ADB access over WIFI, what commands you run with ADB to the unit would be where you could go wrong.

In all case, the most direct and secure solution is to use a USB type A-A male to male cable. This way changes in the head unit and risks will be minimal. I have tried in my head unit long time ago and I think it's not easy to get root access. Adding potential risks after get it and the required time to make manipulations I have decided to use a cable. Nevertheless, it's possible I will find issues with cable method. But it's the simplest way to intervene. Best regards.

If you are able to get USB working, it´s fine.
...but most of the units don´t have OTG ports available. The only possibility with these devices is to work with WiFi.... and on top: My units are in my office in another room, so I am able to do it with WiFi from the sofa if I want....
SCRCPY is a nice tool to get the screen on my laptop, instead sitting in front of the unit.

I was able to modify the build.prob file to allow adb over wifi and i an able to issue adb commands and reboot into fastboot but with no wifi capabilities in fastboot and not being able to usb a usb to connect... Has anyone figured out a way to issue fastboot commands or get the usb A to A working at least in fastboot?

rigattoni said:
Code:
setprop persist.adb.tcp.port 5555
setprop sys rkadb.root 1
...and then reboot.
Click to expand...
Click to collapse
Sorry, I didn't get where to run these commands.

Sedhadi said:
Sorry, I didn't get where to run these commands.
Click to expand...
Click to collapse
Android Terminal Emulator as example... on the head unit for sure.

rigattoni said:
Android Terminal Emulator as example... on the head unit for sure.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It didn't work

Sedhadi said:
View attachment 5459703
It didn't work
Click to expand...
Click to collapse
old thread, so for posterity sake; Termux won't do. look for terminal emulator on Fdroid.

Very late to this party but what worked for me was the three dots in the top right corner of the developer options. Tap those and it should say USB Computer Connection. Once selected I had two options in Chinese. I selected the option that wasn't already selected and now my PC is being recognised and my unit is visible within ADB.
Hope it helps someone