Azottu Head Unit - ADB trouble - Android Head-Units

Hello,
I bought few month ago a Azottu (allwinner T8 core) head unit and I'm trying to link it with my laptop using ADB.
The problem is the HU is USB Host, as well as the Laptop. So using USB for ADB is not possible.
I tried to make the link using Wifi; the HU is connected to the wifi and via the laptop I try to connect (using the ip of HU)
But that's not working.
Does someone manage to connect to a HU using ADB and Wifi ?
Of course the HU is on development mode (7890) and the USB debug is activated ([email protected])
Hope to your light and help. Thank you

install a terminal app on your unit and type in the following line:
setprop persist.adb.tcp.port 5555
Then reboot the device and you should be able to connect via adb over WiFi

realzoulou said:
install a terminal app on your unit and type in the following line:
setprop persist.adb.tcp.port 5555
Then reboot the device and you should be able to connect via adb over WiFi
Click to expand...
Click to collapse
Thank you, works better.
Now with
adb devices -l
List of devices attached
192.168.1.118:5555 unauthorized transport_id:2
But the device is unauthorized
So I tried to remove all the keys generated by adb on my laptop, and revoke the authorization on the HU (with a reboot for both) to resynchronize the pairing without success...
I tried to generate a new key with the adb keygen command, and then copy the public key (.pub) on the HU (adb push or cp from sdcard to /data/misc/adb/adb_keys) without success as well
Do you have any other idea ?
Thank you

To see "unauthorized" when using adb over WiFi with a head unit never happened to me so far. So I have no advice, sorry

Related

adb unable to connect...

I was to B&N today, read few books in store (on nook)
Came home, tried to connect:
adb unable to connect...
run dropbear - unable to ssh
rebooted nook via terminal
adb unable to connect...
Scratched head…
rebooted nook again via terminal
adb unable to connect...
Did basic adb troubleshooting:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
adb unable to connect...
stop adbd
adbd &
adb unable to connect...
netstat
showed listening (with adbd running)
127.0.0.1:5037
0.0.0.0:5555
rebooted nook via terminal
rebooted PC…
adb unable to connect...
put noogie SD, reboot, check uRamdisk – same size & timestamp
removed noogie, off/on - connected right away!
I’m puzzled…
I saw few times, after 2-3 days of reading adb is unable to connect, but reboot fixed it always.
What was different this time?
“Cold reboot”?
I spend like 30min and feel like an idiot right now…
I was unable to connect over the usb port as well. Without too long investigation I've used adbwireless app on NT and was able to connect.
You might want to refresh server
adb kill-server
adb start-server
then connect using your NT ip address:5555 and you should be done.
In my case, I think, there are too many conflicting drivers installed and NT is not being recognized when connected.
Good luck
Adapt0r said:
I was unable to connect over the usb port as well. Without too long investigation I've used adbwireless app on NT and was able to connect.
You might want to refresh server
adb kill-server
adb start-server
then connect using your NT ip address:5555 and you should be done.
In my case, I think, there are too many conflicting drivers installed and NT is not being recognized when connected.
Good luck
Click to expand...
Click to collapse
I did it as well before every adb connect, thought it not worth to mention.
Naturally, "rebooting PC" should reboot adb server too, right?
But it didn't help either...
If you see this issue again, just try toggling ADB Wireless On/Off and it should reset anything on the devices side. Also I've noticed that sometimes and completely random from what I can tell "USB Debugging" will get unchecked, which will mess with ADB access via USB.
Disabling/Enabling ADBwireless sometimes may help.
Maybe a stupid question: Do you have a firewall running on your pc?
digiflash said:
Disabling/Enabling ADBwireless sometimes may help.
Click to expand...
Click to collapse
won't it be the same as below or it does more?
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
digiflash said:
Maybe a stupid question: Do you have a firewall running on your pc?
Click to expand...
Click to collapse
Always
I did check it too. It was nothing worth to mention.
abd attempted to connect - got nothing back (timeout)
on NST adbd was listening, I was able to access gmail.
I can ssh neither, and dropbear was listening too.
Looks, in fact, like firewall on NST was blocking all incoming connection.
That's why I wrote "Scratched head…" - which means I checked pretty much everything.
Could somebody explain, what is the major difference for NST between:
reboot (hot reboot) & shutdown/start (cold reboot)
Or more precisely for the latter:
insert noogie SD/reboot/remove noogie SD/turn off/turn on
ApokrifX said:
insert noogie SD/reboot/remove noogie SD/turn off/turn on
Click to expand...
Click to collapse
Cannot connect today at all. Cold reboot doesn’t help anymore...
Did some more tests (including ADBwireless):
I cannot ping [nook IP] from my computer
I can ping [nook IP] from router.
From PC
>telnet [nook IP] 5555
Connecting To [nook IP]...Could not open connection to the host, on port 5555: Connect failed
From router:
telnet [nook IP] 5555
Connection didn’t timeout (i.e. it does connect!)
Again, looks like something on Nook blocking connections from all IP, except from default gateway (i.e. router)
Question: Does rooting process unblock connections from other IPs?
About Disabling/Enabling ADBwireless:
Before running ADBwireless
netstat
127.0.0.1:5037
0.0.0.0:5555
netstat -tapn doesn’t work
stop adbd
both above disappear from netstat
start adbd
both show up
run ADBwireless
get message: ADBwireless is off
pushed button, message changed to: adb connect [nook IP]:5555
(adb connct didn’t work)
Switch to terminal,
netstat
127.0.0.1:5037
I.e. no more: 0.0.0.0:5555
Subsequent "stop adbd"/"start adbd" changes nothing:
netstat
127.0.0.1:5037
I was wondering what ADBwireless supposed to do then?
Could somebody check from his nook what netstat shows, please?
Nook can connect to internet (gmail, market) + netstat shows all outgoing connections…
What else can I try?
I guess, I can switch to adb usb…
It might be helpful if you tell what OS you are running on your PC and what did you do with NT. If we can reproduce your case then we can troubleshoot it otherwise you will hear useless guesses and speculations.
I like NT as a reader and nothing else. Web and games are looking awful on it.
Adapt0r said:
It might be helpful if you tell what OS you are running on your PC and what did you do with NT. If we can reproduce your case then we can troubleshoot it otherwise you will hear useless guesses and speculations.
I like NT as a reader and nothing else. Web and games are looking awful on it.
Click to expand...
Click to collapse
One box is XP with Outpost firewall (abd set to full trust).
Another win7 (FW policy – allow outgoing connections + few exceptions).
I’m Win developer/admin and Linux(CentOs) admin.
I’m complete noob when it comes to Linux non-shell related programming.
Router runs DD-WRT.
As of now I switched to uRamdisk_1_1_rooted_usb.
When I run dropbear, I see it listening on 22, but cannot ssh still.
That’s all I guess…
Could you do one test for me please?
If your NST runs uRamdisk_1_1_rooted_wifi:
Could you ping you NST from you box
If not - could you do same from your router/AP?
1. I don't have uRamdisk_1_1_rooted_wifi on my NT and can't test it.
2. adbWireless works on my Win 7 and Mac the same way. Both comps have firewalls running and both are on the same network. I can connect and ping NT.
Just for clarification I will describe how it works on my setup:
- I start adbWireless on NT,
- it asks for root permission if it for the first time and I grant it
- then shows fat button on the screen and says adbWireless is off
- I push the button
- it says adbWireless is on, from your computer run
adb connect 192.168.15.112:5555
At this point I can ping IP address and run adb shell.
I've rooted NT for purposes of software testing and customization. I did it twice with older and newer Nooter and did not find any noticeable differences.
Let me know if you want some other tests or info.
Adapt0r said:
I can connect and ping NT.
…
At this point I can ping IP address and run adb shell.
Click to expand...
Click to collapse
To clarify (trying to get a setup as simple as possible):
We connected NST to our home wireless network and it gets IP.
We didn’t touch adbWireless yet!
Now do two tests, please:
1. From NST we ping gateway or "another device on same network", (providing it let us).
2. From "another device on same network", ping NST.
What do you get?
I thought, adbWireless just configure adbd for IP connection (as opposite for USB one) and starts it - nothing else.
If #1 works, but not #2,
and #2 starts working after you “hit adbWireless button”, than adbWireless does more then I wrote above…
Sorry, I didn't have time to do your test at home. I'll try today.
I think you are correct, adbWireless does configuration of connection by executing something like this:
Turning On:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Turning Off wifi and start listening on usb
setprop service.adb.tcp.port -1
stop adbd
start adbd
Cheers!
Edit:
Ping NST_ip_address from PC works fine.
Since I don't have terminal installed I could not test reverse pinging.
Ouch…
Just figured out:
1: I press “big red button” in adbWireless.
2: I push back button
And it pushed adbWireless into background.
If it’s the same as turning it (adbWireless) off,
it’s possible, that adbWireless reset adbd service to use USB.
Thus there is nothing listening on 5555 when I run netstat in terminal on NST.
Who’s with me?
Should be east to test:
press “big red button” in adbWireless.
I push back button
try to connect
ApokrifX said:
Ouch…
Click to expand...
Click to collapse
Updated router firmware - I can ping nook and ADB over wireless works too.
Not sure thought, if it was wireless channel problem.
I've read somewhere, some NST firmwares doesn't work on high channels or certain combined modes - like works on A+B, but not A+G
Apparently, NST firmware 1.1.2 was targeted to solve some of these issues.
PROBLEM SOLVED.
I didn't have the proper folder for the adb.exe.
-----
I have a similar problem: I recently rooted my nook simple touch with touchnooter 2.1.31, and all seems well but I can't connect to the adb wireless. IP is 192.168.0.6:5555 according to adb; I can ping from my Win XP computer if I use 192.168.0.6, but not if I add the 5555, but I just can't connect to the ereader. Wireless connections seem fine otherwise. I've tried shutting off and one the wireless adb.
I'm a complete beginner in this. On the reader, the screen has this:
"from your computer run: adb connect 192.168.0.6:5555"
This suggests that I can't simply use a firefox browser to connect? I tried using the windows cmd box, but windows indicates it doesn't know what 'adb' is. Then I found a website about adbwireless: http://theunlockr.com/2011/04/12/how-to-connect-to-your-android-device-through-adb-wirelessly/
and installed Adroid SDK Tools as indicated. When I use the cmd window, go to the proper sdk tools subfolder, and type 'adb connect 192.168.0.6:5555', windows still insists it doesn't recognize 'adb'
Please help!
try adb.exe
Meter 13,
Thanks for the reply. I added a pre-script to my op. I had created a bat file to move to the proper folder but had realized that the adb.exe had been moved to the platform-tools subfolder from its old location in the tools folder. Once I realized this, all worked well - connected to my nook, and used adb to install an apk file.
Bob
Just a note:
Ping isn't the usual TCP/UDP stuff, so there are no (port) numbers on the end.
ping 192.168.1.27
ADB uses TCP and a port number but it usually defaults to 5555
adb connect 192.168.1.27
adb connect 192.168.1.27:5555
You can also telnet to check if you can connect to the nook via TCP and port 5555
telnet 192.168.1.27 5555
(Note: If this works it will tell you that you are connected, but you can't do anything because ADB is a binary protocol.)
I had the same problem, turns out the correct drivers weren't installed. Ive downloaded HTC sync from HTC.com. I installed it and removed HTC sync afterwards. The drivers should stay there. Now reconnect your phone and try "adb devices" Before ADB wouldn't recognize my device but now it does. Tried to "adb backup -all" again, and it worked instantly.
Maybe this solves the problem?
You could try going back to a stock /boot partition.
I run my nstg rooted with the addition of about 8 files (su, xbin, busybox in system, adb wireless in /data plus a launcher) when I first root.
with the nstg, at least, I don't actually need the modified kernels - adb connects from my computers to the nstg, I simply don't have a root shell when I first connect.
This is fixed by doing an
su
once I'm in
Might be worth trying a restore of just partion 1 from your backup?

USB Debugging Xtrons 8.0 BMW E39

Hello guys,
I have a PX5 HeadUnit for my E39, and right now im developing an app for it.
The problem: i can't find a way to connect the HeadUnit with my Notebook to directly debug it.
I have already tried it with an USB to USB-c cable, as i don't have any USB male to male cables here, but it was with no success.
Why not using adb over WiFi?
Actually, I didn't know that was an option...
I'll test it and report later.
Apparently adb over WiFi doesn't work without an USB connection first, so that one was not helpfull at all.
Edit: OK! I found the solution, WiFi over ADB DOES work without an USB connection first.
Simply follow these steps:
install an terminal app on your unit and type in the following lines:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot
(install adb drivers on your pc, kinda obvious)
type in "adb connect [your device ip]:5555
done.
Mumbira said:
Apparently adb over WiFi doesn't work without an USB connection first, so that one was not helpfull at all.
Edit: OK! I found the solution, WiFi over ADB DOES work without an USB connection first.
Simply follow these steps:
install an terminal app on your unit and type in the following lines:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot
(install adb drivers on your pc, kinda obvious)
type in "adb connect [your device ip]:5555
done.
Click to expand...
Click to collapse
How do you connect via adb if you are not rooted?
The same steps should also work without root.
I'm sure that my device wasn't even rooted back then.

Question for Surfer or any other Android guru.

Is adb not able to connect over even see these Joying FYT Airmont units with Oreo on it?
The head unit has a switch to allow debug over usb but when I connect a usb to my laptop I don't get the dialogue screen on the head unit asking if I want to connect to this device and the laptop cannot see the unit at all.
I figured maybe it needed device specific drivers in Windows so figuring Joying hasn't made any I found universal usb drivers for it. Nothing.
I got an app called Naptime or something that's supposed to be able to put the unit in full doze. It's designed to work on rooted devices but also says that can be worked around by using adb to give certain permissions. I can't do that if I can't even connect adb to the damn thing.
Also, is rooting these using that Magisk method result in the same type of full root the normal way on other devices? It isn't limited compared to the normal way is it?
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
rooted = rooted.
It doesn't make a difference in functionality whether the boot.img is rooted (called systemless rooting) or /system.
You always need an apk to "hand out" root rights, be it SuperSU, Superuser, Magisk or another.
In general the current systemless boot.img rooting is preferred. One of the big advantages is that it allows for OTA updates. But... we know that our units do not support that.
If you want to know more, just google for "systemless root" (sometimes "system-less root").
And I don't consider myself a guru. I read a lot and I have a good memory
surfer63 said:
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
rooted = rooted.
It doesn't make a difference in functionality whether the boot.img is rooted (called systemless rooting) or /system.
You always need an apk to "hand out" root rights, be it SuperSU, Superuser, Magisk or another.
In general the current systemless boot.img rooting is preferred. One of the big advantages is that it allows for OTA updates. But... we know that our units do not support that.
If you want to know more, just google for "systemless root" (sometimes "system-less root").
And I don't consider myself a guru. I read a lot and I have a good memory
Click to expand...
Click to collapse
If the USB connection does not work for any reason, you could try the following:
Some units (as mine SC9853i) ADB can be used by WiFi, if you first run some commands on the unit.
You need a shell app and run these commands:
Code:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot
After that you can connect via ADB from your laptop if both are in the same network.
Unfortunately that doesn´t work with all units.
rigattoni said:
If the USB connection does not work for any reason, you could try the following:
Some units (as mine SC9853i) ADB can be used by WiFi, if you first run some commands on the unit.
You need a shell app and run these commands:
Code:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot
After that you can connect via ADB from your laptop if both are in the same network.
Unfortunately that doesn´t work with all units.
Click to expand...
Click to collapse
These commands require root
surfer63 said:
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
Click to expand...
Click to collapse
Maybe I'm doing something wrong then. The developer options are enabled and I have it set for unlocked bootloader but my laptop can't see it whether I'm connected through the OTG usb port or the standard one and the HU doesn't give the popup dialogue asking if I want to allow the connection like my tablet and phone did. Maybe they changed something with these particular units with the new UI?
I did notice on another thread someone that had a FYT Joying Airmont with 8.1 and they said something about the 3 dot menu on the top right for "USB Connection" that brings up two options both in Chinese an his only worked on the lower option. I did try that too but still nothing. IDK. Maybe I had something else set wrong when I tried that lower option that made it not work in all my effort yesterday to get adb to see it and connect.

ADB commands from mobile phone to head unit

If you want to execute ADB commands you can use a USB male to USB male cable but you can also do it wireless:
1. Activate USB debugging on your head unit
2. Install Remote ADB Shell from Google Play Store on your mobile phone: https://play.google.com/store/apps/details?id=com.cgutman.androidremotedebugger
3. Connect your head unit to the wifi hotspot of your mobile phone.
4. Start Remote ADB Shell and connect to the IP of your head unit.
5. Execute ADB shell command.
Here are some samples for the Junsun V1 headunit:
Get su rights:
Code:
su @#zxcvbnmasdfghjklqwertyuiop1234567890,.
Disable duraspeed:
Code:
setprop persist.vendor.duraspeed.app.on 0
Give authorizations to an app:
Code:
pm grant com.llamalab.automate android.permission.WRITE_SECURE_SETTINGS
Would this work on Joying head unit?
CCJ22 said:
Would this work on Joying head unit?
Click to expand...
Click to collapse
Just give it a try. I expect the su command with the "password" will not work but remote adb may be possible.

TS10 ADB offline

Hi all. I´m trying to get ADB to work with my TS10/Topway-style headunit. Since I can´t put the unit in device mode I can´t connect a USB cable to it.
I´ve managed to start ADB listening over WiFi using the internal ADB Shell hidden in the engineering menu. I´ve send adb tcpip (or tcpip 5555), adb stop and adb start over the internal shell. USB debugging is enabled.
I can now connect using my pc and adb connect xyz:5555, and it does connect. But when using adb devices it always reports unit as offline.
I´ve tried changing IP adresses, reboots, kill-server and whatnot. Can´t figure out how to get the unit online.
Any ideas? Could be interesing in terms of rooting these devices.
I'm trying to do the same thing. Wanna get Jõao's Tasker Permissions desktop app to work. You got a bit further than I, but I've had no such luck either.
Anyone else got any ideas?
I wish this thread would've worked. But alas, trying to connect to my TS10 headunit via my phone is showing the same result as trying to connect from my MacBook: CONNECTION REFUSED.
Edit: I have "Enable USB Debugging" turned on in Developer Options. And I've rebooted the headunit a few times now. And I've tried "adb tcpip 5555" and "adb start" via the ADB shell hidden in Engineer Mode. No luck.
~~ Edit ~~
I got it to work! Tasker Permissions is working a treat.
It's amazing what can happen when I try the correct IP address
If this stackoverflow answer is to be believed, apparently ADB over WiFi is only supported in Android 11+ ?
Can anyone confirm this?
Edit: Please disregard. See above post.
Patman27 said:
I wish this thread would've worked. But alas, trying to connect to my TS10 headunit via my phone is showing the same result as trying to connect from my MacBook: CONNECTION REFUSED.
Edit: I have "Enable USB Debugging" turned on in Developer Options. And I've rebooted the headunit a few times now. And I've tried "adb tcpip 5555" and "adb start" via the ADB shell hidden in Engineer Mode. No luck.
~~ Edit ~~
I got it to work! Tasker Permissions is working a treat.
It's amazing what can happen when I try the correct IP address
Click to expand...
Click to collapse
Did you get things working over WiFI or did you need to use the remote ADB app loaded onto your phone + phone hotspot?
I am trying to do similar; i need ADB shell over WiFi... ideally not phone hotspot, regular access point.
Idk what you're trying to do, but why not enter your commands directly to the unit using the terminal emulator app?
watson540 said:
Idk what you're trying to do, but why not enter your commands directly to the unit using the terminal emulator app?
Click to expand...
Click to collapse
I am trying to understand more about how the software works / how key codes are interpreted so I can get my steering wheel controls working as expected and generally learn more about the software so I can tailor it to my needs.
I don't want to do all of this from the seat of my car in the cold using a painful software keyboard on a tiny screen. I'd much rather do this from inside with a real keyboard attached to a monitor that is good for more than running google maps.
This worked on my two joyings and one mtcd unit:
If you can get to the settings > developer options, under where it says "Developer Options" sometimes on the right side is the three dots button. Tap that > Usb Connection > then change to the one not selected (these options might be in chinese)
forgivegod said:
This worked on my two joyings and one mtcd unit:
If you can get to the settings > developer options, under where it says "Developer Options" sometimes on the right side is the three dots button. Tap that > Usb Connection > then change to the one not selected (these options might be in chinese)
Click to expand...
Click to collapse
Can you share a picture of this? I'm not seeing such a menu on my unit.
estoy interesado tengo un problema parecido, lograste la solución?
dro1dy said:
Can you share a picture of this? I'm not seeing such a menu on my unit.
Click to expand...
Click to collapse
I'm interested, I have a similar problem, did you find the solution?

Categories

Resources