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.
Related
Flyaudio in Russia sells head units for a variety of cars that are also based on the Intel Airmont CPU, similar, but not equal to Joying latest Intel Airmont head units (see https://forum.xda-developers.com/an...ying-android-8-1-intel-airmont-eight-t3897206 and https://forum.xda-developers.com/an...ing-finally-head-unit-digital-output-t3891087 )
I purchased a G4909R unit, a 10 inch (=no knobs) unit for Volkswagen Passat B7 (https://flyaudio-shop.ru/products/g4909r-magnitola-android-volkswagen-passat-b7-2010-2015)
Youtube video https://www.youtube.com/watch?v=HZhE30W5ej8
Similarities to Joying’s units:
- Android 8.1.0 “user” build with its limitations for rooting, adb, debugging, etc.
- DSP with quite a lot of equalizer settings, but it seems to be a slightly different DSP
- FYT/SYU system apps (oh dear…)
Differences to Joying:
- No SPDIF audio output
- No 3G/4G modem
- Different BT chip
- Completely different form-factor (see video linked above at timestamp 6:06 https://youtu.be/HZhE30W5ej8?t=366 )
Passwords
Factory Settings: 3368
Developer Settings: 3368
Backlight current adjustment: 5768
Door lock interference: 0000
I was able to root it with the same approach (but not using the ready-made files!) as documented for the Joying units https://forum.xda-developers.com/an.../howto-root-joying-sc9853i-head-unit-t3915530
I noticed that some apps that I used on Intel Sofia and Rockchip PX5 units without problems now run into crashes on this unit, actually ANRs (Application Not Responding).
Actually, the Android 8.1 version on this unit is quite different compared to a “stock” Android 8.1, both from its UI and also “internally”.
SYU has created a monster of a Settings app. Car related settings and standard Android settings are all mixed without any structure. Not very clever at all!
Another Android modification: The steering wheel controls for PREV and NEXT only work when used in the SYU system apps (e.g. FM radio and Music player). No other standard app works, also not my DAB-Z app. Reason is that the FYT middleware is circumventing the Android framework MediaSession handling completely and thus the MediaControl interfaces in apps don’t work.
The SYU Bluetooth app still kills Google contacts, a bug that existed already 3 years ago in the Intel Sofia units with Android 6.01. They have not done anything about it!
My conclusion after some days with the unit on my desk, and now in the car for about a week:
Nice hardware, but the software is crippled more than ever…
realzoulou said:
Similarities to Joying’s units:
- Android 8.1.0 “user” build with its limitations for rooting, adb, debugging, etc.
I was able to root it with the same approach (but not using the ready-made files!) as documented for the Joying units https://forum.xda-developers.com/an.../howto-root-joying-sc9853i-head-unit-t3915530
Click to expand...
Click to collapse
Now that you have it rooted, you can make the /system read-writable from a rooted terminal.
Code:
su
mount -o remount,rw /system
Can you change the build.prop?
Code:
ro.build.type=user
to
Code:
ro.build.type=userdebug
and add:
Code:
persist.adb.tcp.port=5555
ro.debuggable=1
ro.adb.debuggable=1
And reboot?
Maybe you can then adb over tcpip?
I'm not sure whether this will work, but you can try.
On a normal user build adbd is not enabled/started. So it also might require the addition of "start adbd" in the "/system/bin/install-recovery.sh".
(But maybe when you set the debuggable properties, it is started automatically. I should take a look at the rc files in the boot image)
I enabled adb over WiFi persistently. However, it was a bit tricky.
1. Enable USB device mode in Developer Menu (very well hidden: First click on "..." on uper right corner, then the second option in the Chinese dialog)
2. Connect head unit to PC via USB (not all USB ports of the device allow adb, so try out all of them)
3. Use "adb shell" to execute
Code:
su
setprop persist.adb.tcp.port 5555
After a reboot you can connect via adb over WiFi.
The property ro.build.type is set usually by the kernel. You cannot set it via build.prop.
realzoulou said:
I enabled adb over WiFi persistently. However, it was a bit tricky.
1. Enable USB device mode in Developer Menu (very well hidden: First click on "..." on uper right corner, then the second option in the Chinese dialog)
2. Connect head unit to PC via USB (not all USB ports of the device allow adb, so try out all of them)
3. Use "adb shell" to execute
Code:
su
setprop persist.adb.tcp.port 5555
After a reboot you can connect via adb over WiFi.
The property ro.build.type is set usually by the kernel. You cannot set it via build.prop.
Click to expand...
Click to collapse
i know this is old, but...
I have adb over wifi enabled... when i connect to ADB i get device unauthorized. I shouldn't need usb drivers since its wifi, right? I am 99% sure its device related and not my laptop or software, because I have an 8227 headunit that connects fine. Is there anyway to authorize my TS9 Topway unit through terminal without root?
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.
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
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.
Hi I have an xtrons PSF70vxl
Firmware: android 10:
OneDrive
onedrive.live.com
I can gain root shell access via:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
that works fine, however i cant "root" the device as there is no ADB via USB only via WIFI.
I've emailed their support and got back:
"Sorry,there is no pre rooted version of the software we offer and there is no way to ADB via usb."
how can I root it?
anyone got any ideas?
I want to use a kernal with Swap support.
waz000000 said:
Hi I have an xtrons PSF70vxl
Firmware: android 10:
OneDrive
onedrive.live.com
I can gain root shell access via:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
that works fine, however i cant "root" the device as there is no ADB via USB only via WIFI.
I've emailed their support and got back:
"Sorry,there is no pre rooted version of the software we offer and there is no way to ADB via usb."
how can I root it?
anyone got any ideas?
I want to use a kernal with Swap support.
Click to expand...
Click to collapse
Please share your System Info screen