Database Users

[Tool][Windows Only][Root] Android Reverse Tethering 3.19

Android Reverse Tethering for windows users.
Tethering is the ability to surf on your pc using the 3g of your phone
Reverse tethering is the opposite : surf on your phone using the ADSL of your PC. No Wifi or 3G connection required.
==>Troubleshooting (FAQ) <==
Since a lot of users don't read the full article before asking for help, I will start by this section !
Not yet compatible with Android 5. Work on progress. Don't ask me when it will be available
Android 4.3 and upper : You must install the Connectivity hack (see Connectivity hack section) before connect .
Android 4.3 and upper : You must connect your phone/tablet to a working wifi or 3g once after each boot before using reverse tethering !!!
This work only for rooted users and with Windows. Don't ask for linux or for some fruit operating systems !!!
The tool is not compatible with "CrossBreeder" , "adaway" or other tools that change the host file (removing localhost)
Tethering and reverse tethering (this tool) are not compatible at the same time, it's then not possible to turn your android phone as a wifi hotspot.
If your device is not listed in the "select a device" dropdow list:
Ensure Usb debugging is enabled. See "Before starting the tool" section
The ADB subsystem is sometimes not working properly. Click the "Kill ADB" button (on Tools)
Your device is perhaps not installed properly. See your device manufacturer. You can download a generic driver from google here : http://developer.android.com/sdk/win-usb.html.
Windows can detect your device as a "Media Transfer Protocol" (MTP) or "Picture Transfer Protocol" (PTP). When you connect the usb cable, you can receive an "Usb" notification. Click the notification to change this parameter. If one don't work, take the another one...
Click refresh or restart the tool to detect your device.
If the connection shutdown often, try another usb cable
Proxies problems :
Corporte proxy. The windows application is not able to traverse proxies.
The good news is that you can use some applications like FreeCap , sockscap and proxifier.
You must start the androidTool from one of these launchers, giving proxy adress and port.
Thanks "edgd1er" for the information.
Android 3G proxy. Even if 3g is desactivated, your provider (APN) proxy may still be used by applications.
The windows tool is not able to communicate with your provider proxy.
Note that only a few providers include a proxy. You must remove it manually.
The tool will give you informations on how to do it when detected.
Installation :
Unpack the zip file. This zip files contains the windows part, ADB and the android APK.
Before starting the tool :
You must install drivers for your device.
If you don't find drivers for your phone/tablet, check the Universal Naked Driver
Other interesting tool to install Adb and drivers (32/64) : [TOOL] ADB, Fastboot and Drivers - 15 seconds ADB Installer .
Some screenshots are availables in this thread to install the driver.
Ensure you have debugging enabled on your phone :
Settings > Applications > Development > USB Debugging > Turn On
Ensure you have root access AND SuperUser application installed.
Change the superuser settings (Menu -> Preferences -> Notifications part) :
Uncheck "Notifications" label to display "Do not show notification when an app is granted Su Permissions"
{
"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"
}
AndroidTool
The AndroidTool.exe is the windows part
The low level communication tool (ADB) is included in the zip file.
AndroidTool will try to find ADB in c:\android-sdk-windows\platform-tools\adb.exe
If not found he will use the provided one.
The first time you use the program :
If you want to use another version of ADB, clik "config" and in the first tab enter the path to the ADB
Select the DNS server to use in the right list. On complex system, some dns can be detected.
Start reverse tethering
Just click “Connect”.
If it's the first time you use the program, This will install the latest android package and the dependencies (busybox and redsocks).
The SuperUser process may ask you to allow “Usb tunnel”
If the android process crash after receiving superuser rights, close the windows program and start again.
The android interface (first tab) will show connections forwarded to windows.
Others tabs are just for debugging. Send the log on this thread in case of problem.
Start your browser
Google chrome will complain that no connection is available. Don’t care. That work.
Firefox , opera and dolphin don’t have problem with that !!!
The current version of the application can’t forward low level ICMP packet (PING).
From Android Os point of vue, there is no internet connection.
Command line prompt :
The windows tool is a "One click" application. Just click the "Connect" button.
But you can add parameters to directly connect when the program start.
Here are the supported commands : Device:xxxx (where xxxx is the device id), Connect, Disconnect, KillAdb, LogToClipboard, Show, Hide, Quit
Parameter sample : Device:123465789 Connect Hide
Create a second shortcut with Disconnect Quit parameters to stop connection and close the application.
Connectivity hack :
This will install some low level program to install a "fake" Wifi for browsers and google play market.
Don't worry, I didn't brick my phone and tablet during the development.
The Xposed framework author and me are not responsible for anything you do with your phone/tablet/rice cooker.
This work for android 4.X, but an experimental version of the Xposed framework for Gingerbread made by liudongmiao can be found here: http://forum.xda-developers.com/showthread.php?p=44034334#post44034334 (no support from my side)
On the windows program, go to tools tab and click "install hack"
Launch the Xposed Installer (you just installed) on your android and click on "Install/Update"
Go to the module tab and check the HackConnectivityService (see screenshot below)
Reboot the phone
Done!
This work for market but also for some other programs (some games,skype,hangouts...)
For older android 2.x or 3.x version :
The application want to have an active 3G or Wifi network interface.
Some market applications are tagged "Wifi" only.
To get around this problem, you can activate the 3G BEFORE starting reverse tethering,all the data will goes to the usb.
Tips : You can connect to some wifi hotspot not protected by a key.
It's only when you want to surf that the hotspot ask you a user/password.
But, at this point, we have an 'active' connection. Market download should work after starting reverse tethering.
Not fully working application but work if you install the HackConnectivityService on android 4.x:
Market download
Spotify
Skype. (not checked yet)
If someone know another one, post a reply !
History :
Version 3.19
Added some rights for sdcard access.
New windows icons.
Version 3.18
Fixed Xposed HackConnectivityService module. You must click "install hack" to update it
Small bug fix.
Version 3.17
Updated Xposed framework installer 2.4.1
Small bug fix.
For Linux ,Mac OS X , I recommand this guide (from @phamthanhnam ) : http://forum.xda-developers.com/showthread.php?t=2287494 .
This required entering a lot of manual commands on both android and the PC each time you want to connect (reserved to power "geek" users).
This work also for windows, but much more complicated, compared to this "One click" connect tool. I let user chose the solution he want...
I will not respond to email or private message. If you want support, post a reply on this forum.
Do you like this program ? Want to make a donation ? Send any amount to my paypal account (click the donate button on left)
Please read FAQ on top of the page before asking for help.
Older versions were removed (416611 downloads)

capslock66 said:
Unpack the zip file. This zip files contains the windows part, ADB and the android APK.
You MUST uninstall previous version. If you don’t find it, run a dos command prompt on the installation folder and enter this command : Adb uninstall service.tracetool
Ensure you have debugging enabled on your phone :
Settings > Applications > Development > USB Debugging > Turn On
Run the windows program : AndroidTool.exe
The first time you use the program, click on “Show Android interface”. This will install the package and the dependencies (busybox and redsocks).
The SuperUser process may ask you to allow “Usb tunnel”
To start tethering click “Connect”.
Again, The SuperUser process may ask you to allow “Usb tunnel”
If the android process crash after receiving superuser rights, close the windows program and start again. (It’s a beta)
The android interface will show connections forwarded to windows.
Start your browser
Google chrome will complain that no connection is available. Don’t care. That work.
Firefox , opera and dolphin don’t have problem with that !!!
The current version of the application can’t forward low level ICMP packet (PING).
From Android Os point of vue, there is no internet connection.
Market :
The search market work, but due to the same connection problem, it’s not possible to download. I hope Google will fix the market.
Click to expand...
Click to collapse
I was looking to get some internet access on alpha build of ics for galaxy tab... Hope this works..will try and let you know..thanks for the good work...
Sent from my GT-P1000 using XDA App

Great work. Tested this and it works pretty well (on HTC Aria CM7).

do you mean we need to connect the tablet to the PC using the USB cable then we can use reverse thethering thingy ?

Wouldn't the PC app like Connectify Me do this thing without all this?
☞★sent from drajax's Galaxy SL!!! *♂ツ

Wow thanks a million!, i hope we can download apps as well but i'll settle for apks for now, <3
---------- Post added at 08:14 PM ---------- Previous post was at 07:55 PM ----------
drajax said:
Wouldn't the PC app like Connectify Me do this thing without all this?
☞★sent from drajax's Galaxy SL!!! *♂ツ
Click to expand...
Click to collapse
it would, but this program uses a USB cable, connectify uses WiFi, so for us who don't have wifi routers or connectify we can use this

Galaxy S II (GT-I9100) on CyanogenMod 7.1, using SiyahKernel 2.2b6, doesn't work. Using Windows 7 x86, with correct drivers installed. Can't get past the step of clicking 'Show Android Interface'. Clicks, but nothing happens. No devices are listed within the program.

screamworks said:
Galaxy S II (GT-I9100) on CyanogenMod 7.1, using SiyahKernel 2.2b6, doesn't work. Using Windows 7 x86, with correct drivers installed. Can't get past the step of clicking 'Show Android Interface'. Clicks, but nothing happens. No devices are listed within the program.
Click to expand...
Click to collapse
If the device is not listed, it's not a problem related with reverse tethering. It's a driver or installation problem !

ldloh2 said:
do you mean we need to connect the tablet to the PC using the USB cable then we can use reverse thethering thingy ?
Click to expand...
Click to collapse
Yes, you just need to install the windows program then click connect.
It's a beta, market is not able to download.

capslock66 said:
If the device is not listed, it's not a problem related with reverse tethering. It's a driver or installation problem !
Click to expand...
Click to collapse
Elaborate? On your post it says:
Tested under:
Acer Iconia A500 (Taboonay 2.1)
Galaxy S (Cyanogen 7)
Galaxy S II
HTC Aria (CM7)
Click to expand...
Click to collapse
The device is listed. And I've got all appropriate drivers for my device installed?

Inspire 4G CM7, works
As a side note, I had ADB running when I started it & it didnt work. Killed all ADB sessions & relaunched, after that it worked like a charm.

screamworks said:
Elaborate? On your post it says:
The device is listed. And I've got all appropriate drivers for my device installed?
Click to expand...
Click to collapse
Did you enabled USB Debugging ?
Run a dos command prompt then enter this command :
Code:
cd\instfolder
adb devices
instfolder is the folder where you unzipped ReverseTethering.zip
Ensure you have adb.exe in that folder
You should see :
Code:
List of devices attached
xxxxxxxxxxx device
If not, try to re-install driver or test on another PC.

combustiblemonkey said:
As a side note, I had ADB running when I started it & it didnt work. Killed all ADB sessions & relaunched, after that it worked like a charm.
Click to expand...
Click to collapse
Better is to configure the application to use the already installed ADB program on your computer :
button config -> ADB sheet -> update path -> button save
Then restart the tool.

Working on Nexus S with MIUI. Opera browser and Market both work.
I was hoping to use it to avoid using my data while playing games or when installing games with huge downloads after installing, but that doesn't seem to be the case yet. I see I can add ports for forwarding, but how can I tell what port a game uses?

This was something i was waiting but i could not use the internet from pc.
I have SGS1, 2.3.6. I dont get any error messages. Clicking connect makes it connect but status column always not connected.
Im on company network. Which IP i will use? Which port i will use?

Kolero said:
I was hoping to use it to avoid using my data while playing games or when installing games with huge downloads after installing, but that doesn't seem to be the case yet. I see I can add ports for forwarding, but how can I tell what port a game uses?
Click to expand...
Click to collapse
Next version will detect automatically ports.
But it's still not possible do download from Market

yken said:
This was something i was waiting but i could not use the internet from pc.
I have SGS1, 2.3.6. I dont get any error messages. Clicking connect makes it connect but status column always not connected.
Im on company network. Which IP i will use? Which port i will use?
Click to expand...
Click to collapse
Beta 2 (+- 15 decembre) will be more stable. With automatic port detection.

serves to moto defy?

Why not just use virtual router on your pc?

Works like a charm on My Ideos X5 U8800.. Thx!

[APP][TOOL] ADB-Over-WiFi-Helper

Free for XDA members and as a thank you for all the information, tools and roms XDA Developers has provided over the years here is something I created that makes it easy to connect adb over tcpip to multiple Android devices. Get rid of the wires!
One click to switch adb on all usb connected devices to tcpip.
One click to switch adb on all tcpip connected device back to usb.
Auto discovery of the devices listening on tcpip.
The application consists of two parts. "Helper.jar" to run on the pc and "Helper.apk" for the device.
View attachment 2455389Helper.jar
- Installs the Helper.apk on the device.
- Attempts to switch adb on the device to use tcpip.
- Sends broadcast messages to look for devices on the network.
- Initiates an adb connection over tcp to any ip that responds to the broadcast.
- Provides a button to switch all usb devices to tcpip.
- Provides a button to switch all tcpip devices to usb which also uninstalls the helper.apk file, leaving no "junk" on the device.
{
"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"
}
On the device, Helper.apk
- Turns on WiFi if not already on.
- Checks and shows if the adb port was indeed opened.
- Listens and responds to udp broadcasts from Helper.jar.
Some android devices will work without root but if you get a red message from the helper on the device, you will need to root it to enable adb in tcpip mode. The rooted method to set adb to use tcpip is used in case the device is rooted.
If you like the tool and want to contribute, please feel free to buy the app on the Play store. The attachment contains exactly the same files for free.
Feedback is welcome and I hope someone finds this useful!
Adrian
UPDATE!!
A new tool I am calling "ADB Master" that includes all functionality of ADB-Over-WiFi-Helper plus a lot more is now also available for free to XDA users.
Get the new ADB Master here: http://forum.xda-developers.com/showthread.php?t=2707556
It is highly recommended to use the new download rather than the file attached to this post!

Thanks for this. Much appreciated. :good:

If you need an icon or Banner created let me know.
Nice work!

so now if i broke my USB port i can lock bootloader with this?Yes?
Nexus 4

ADB over wireless
I think this will be a very useful application for anybody requiring to make changes when on the road, or away from one's main computer.
Running ADB over WiFi should be a great addition to anybody's 'tool kit', I for one, look forward to making use of this application.
Many thanks for bringing this to all of us at XDA.
Thank you!

this apps is awesome make adb over wifi easier

Nice
extremewing said:
Free for XDA members and as a thank you for all the information, tools and roms XDA Developers has provided over the years here is something I created that makes it easy to connect adb over tcpip to multiple Android devices. Get rid of the wires!
One click to switch adb on all usb connected devices to tcpip.
One click to switch adb on all tcpip connected device back to usb.
Auto discovery of the devices listening on tcpip.
The application consists of two parts. "Helper.jar" to run on the pc and "Helper.apk" for the device.
View attachment 2455389Helper.jar
- Installs the Helper.apk on the device.
- Attempts to switch adb on the device to use tcpip.
- Sends broadcast messages to look for devices on the network.
- Initiates an adb connection over tcp to any ip that responds to the broadcast.
- Provides a button to switch all usb devices to tcpip.
- Provides a button to switch all tcpip devices to usb which also uninstalls the helper.apk file, leaving no "junk" on the device.
View attachment 2455388On the device, Helper.apk
- Checks and shows if the adb port was indeed opened
- Listens and responds to udp broadcasts from Helper.jar.
Some android devices will work without root but if you get a red message from the helper on the device, you will need to root it to enable adb in tcpip mode. The rooted method to set adb to use tcpip is used in case the device is rooted.
If you like the tool and want to contribute, please feel free to buy the app on the Play store. The attachment contains exactly the same files for free.
Feedback is welcome and I hope someone finds this useful!
Adrian
Click to expand...
Click to collapse
Nice tool Bro :good:

Thank you for the Christmas gift. I'm on HTC DNA and I am rooted but I get the red port closed message about root required.
No request for root occurs in supersu from this app.

rayjr13 said:
Thank you for the Christmas gift. I'm on HTC DNA and I am rooted but I get the red port closed message about root required.
No request for root occurs in supersu from this app.
Click to expand...
Click to collapse
Same issue here, on my rooted Xperia J. No entry regarding this apk's request for root is found in Super-SU's logs, whatsoever.

Wow, thanks for all the comments!
The helper on the device does not use or need su and ONLY does the following:
1) Checks if the adb tcp port was indeed opened on the device (by creating a tcp connection attempt to it)
2) Listens and then responds to a udp broadcast from the java app.
In future, it could do more.
All the work is done over the USB cable (or WiFi to switch back) using adb from the java app.
In essence, the java app executes the following abd commands to each device (both the "rooted" and non rooted methods are attempted each time):
To turn ON tcpip mode:
adb -s <devicename> tcpip 5555
adb -s <devicename> shell su -c 'setprop service.adb.tcp.port 5555'
To turn OFF tcpip mode:
adb -s <devicename> usb
adb -s <devicename> shell su -c 'setprop service.adb.tcp.port -1'
Please explain a bit more what is happening when the red message appears?
Is the device connected over USB and appearing in the left hand list on the java app?
Perhaps post the output from the java app when you press Switch to WiFi.

darkmatthew said:
so now if i broke my USB port i can lock bootloader with this?Yes?
Nexus 4
Click to expand...
Click to collapse
This app needs you to be able to first connect the USB and is intended to make it easier to work with lots of devices at the same time. For a rooted device without USB / damaged USB, any ADB to WiFi switching app on the play store should work to get adb onto WiFi and then, yes, you should be able to execute your required adb commands.

Thank you in advance for this very important tool!
extremewing said:
This app needs you to be able to first connect the USB and is intended to make it easier to work with lots of devices at the same time. For a rooted device without USB / damaged USB, any ADB to WiFi switching app on the play store should work to get adb onto WiFi and then, yes, you should be able to execute your required adb commands.
Click to expand...
Click to collapse
I have a HTC One, 4.3 Sense 5.5, ( 3.62.771.3 ), and need to reset it back to stock. My USB port doesn't function when the phone is on.
(Works OK in fastboot mode) - and I need to be S-off, then S-on again (locked, remove tampared via revone, moonshine,
or rumrunner) but all those require USB adb. and I can't do that.
So I'll try this and let you know how it goes.

spereree said:
I have a HTC One, 4.3 Sense 5.5, ( 3.62.771.3 ), and need to reset it back to stock. My USB port doesn't function when the phone is on.
(Works OK in fastboot mode) - and I need to be S-off, then S-on again (locked, remove tampared via revone, moonshine,
or rumrunner) but all those require USB adb. and I can't do that.
So I'll try this and let you know how it goes.
Click to expand...
Click to collapse
Please note, this app also requires USB ADB to start off.

Tried it...
extremewing said:
Please note, this app also requires USB ADB to start off.
Click to expand...
Click to collapse
OK, so I've tried it, and it seems like it can only pick up an ongoing ADB WiFi connection but I'm sure I'm doing something wrong.
Remember; I can't use USB debugging coz my usb doesn't work when the phone is on. so USB debugging is off, and there is no point using it. I'm using this as an alternative to restore back 100%.
(1) I pushed the apk file to the phone, using "WiFi File explorer pro"
(2) I installed it using "APK installer"
(3) Ran Helper.jar
(4) Opened an already installed WiFi ADB app on my phone, and established a connection (granted SU first)
(5) ran your app, "ADB over wifi helper" - it picked up the connection (showed green, " ... listening on port 5555 ... ", etc)
Back to the Helper.jar, all it does is saying "Searching - Hello to 255.255.255.255" "Timeout"
I was assuming it would have automatically connected it for me (say running a command like "adb connect ip.address:5555" )
or am I getting this wrong?
I kept the path to my android sdk
****Also, I used the mini sdk (It's quite popular, so I'm assuming most users will have this) and I'm missing the "platform-tools" folder. I just have fastboot and adb,exe and some dll files. So, can you provide a link we could get the required "platform-tools" folder alone? (zipped) ****
However, when I connect manually via command prompt, "adb connect ip.address:5555" the Helper.jar automatically detects it, and the option to Switch devices to USB appears (which I will not use, personally)
But the "Searching" cycle still continues.
Also, what is the use of the large text entry form below the "Searching" indication?
Again, thanks for this tool!!!
P.S. imagine a user trying to do what is said in this thread, but doesn't have a functioning USB port to use adb with, and has to result with your app (alongside another WiFi adb app) - This will fill the gap! as in ANYONE can recover / flash roms, etc, even if you have a broken USB port!!!

spereree said:
Back to the Helper.jar, all it does is saying "Searching - Hello to 255.255.255.255" "Timeout"
I was assuming it would have automatically connected it for me (say running a command like "adb connect ip.address:5555" )
or am I getting this wrong?
Click to expand...
Click to collapse
This is not wrong. After the helper.apk was running on the device, and showing you the port was open, the jar app should be able to discover it. Are both the pc and device connected to the same wifi access point, and that access point allows the two to talk? I assume so based on your later comments. What OS version?
spereree said:
I kept the path to my android sdk
****Also, I used the mini sdk (It's quite popular, so I'm assuming most users will have this) and I'm missing the "platform-tools" folder. I just have fastboot and adb,exe and some dll files. So, can you provide a link we could get the required "platform-tools" folder alone? (zipped) ****
Click to expand...
Click to collapse
Just point the app to the folder containing the adb executable.
spereree said:
However, when I connect manually via command prompt, "adb connect ip.address:5555" the Helper.jar automatically detects it, and the option to Switch devices to USB appears (which I will not use, personally)
But the "Searching" cycle still continues.
Click to expand...
Click to collapse
Searching will always continue. Something is either blocking the udp broadcast or the device is not allowing helper.apk to get them.
spereree said:
Also, what is the use of the large text entry form below the "Searching" indication?
Click to expand...
Click to collapse
That is a log of what the app is doing

extremewing said:
Are both the pc and device connected to the same wifi access point, and that access point allows the two to talk? I assume so based on your later comments. What OS version?
Click to expand...
Click to collapse
I'm on Windows 8.1 x64
and both devices are on the same network (I'm using my PC as the hotspot via a program called connectify. I'm using a USB 3G dongle for internet.
Just point the app to the folder containing the adb executable.
Click to expand...
Click to collapse
So that means I've done that OK...
Searching will always continue. Something is either blocking the udp broadcast or the device is not allowing helper.apk to get them.
Click to expand...
Click to collapse
I believe that might be the problem, but I don't see where that issue comes from...
Also as an addition, When I connect adb over WiFi on my phone, and I list all devices, I see my phone (as an IP address) but with "unauthorized" next to it (please search on the this issue for more info)... This was a brick wall I hit, when I was trying to get my phone 100% to stock, to send it to repairs for my USB issue... MEaning I can't run any shell commands, etc... via ADB... I was hopping this app could find a way around that?

spereree said:
I'm on Windows 8.1 x64
and both devices are on the same network (I'm using my PC as the hotspot via a program called connectify. I'm using a USB 3G dongle for internet.
So that means I've done that OK...
I believe that might be the problem, but I don't see where that issue comes from...
Also as an addition, When I connect adb over WiFi on my phone, and I list all devices, I see my phone (as an IP address) but with "unauthorized" next to it (please search on the this issue for more info)... This was a brick wall I hit, when I was trying to get my phone 100% to stock, to send it to repairs for my USB issue... MEaning I can't run any shell commands, etc... via ADB... I was hopping this app could find a way around that?
Click to expand...
Click to collapse
You have more than one thing going on here.
1) The program you mentioned "connectify" *may* be blocking the broadcast for discovery to work.
2) The "unauthorized" message is due to an out of date adb on the pc. You should upgrade to the latest version in order to connect to newer android devices. Note that you would also need to accept a permission prompt on the android screen.
3) I am also thinking you need to enable USB debugging for anything to work properly when executing adb commands (even over wifi with a faulty usb port).
4) If you get it back to stock, you may want to see if the USB issue you have is fixed.
5) You may also actually use fastboot to flash it back to stock?

Hi, Thanks for the reply.
I'll try all the options and get back to you.
extremewing said:
4) If you get it back to stock, you may want to see if the USB issue you have is fixed.
5) You may also actually use fastboot to flash it back to stock?
Click to expand...
Click to collapse
As for getting back to stock, I would also love to remove the tampered and "unlocked"
warnings from the top, so that I can take it back to repairs under warranty.
So actually ADB over WiFi need to work flawlessly as if I connected the USB cable,
This is so that when rumrunner is run on the device, no problems should be encountered.
Even after multiple reboots (hence, this application should load ASAP when Android booted.)

This tool is so awsome.
Saved alot of time here.
Tyvm

New version out soon
Since there are nearly 1000 downloads, I was going to bring out a new version I've been working on and I wanted some feedback or thoughts about what you would like to see.
The new version at the moment will give you these new features in the JAR app:
- Improved: device lists that will allow you to multi-select devices to perform actions on
- New: list of all apps on all devices (replaces the "console" at the bottom)
- New: Install an APK from your PC onto all selected devices
- New: One click uninstall of multiple apps on all selected devices
- New: One click enable / disable of multiple apps on all selected devices
Is there anything else one would want to do on all devices?

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?

ADB : Missing popup debugging authorization permission

Hello !
I bought this radio head unit on AliExpress (it's the D version) : https://fr.aliexpress.com/item/1005002212221194.html?spm=a2g0o.productlist.0.0.f7057521b4ZITh&algo_pvid=d9ce368e-ff00-495f-a529-2a731b4c08e1&algo_exp_id=d9ce368e-ff00-495f-a529-2a731b4c08e1-3&pdp_ext_f=%7B%22sku_id%22%3A%2212000019285936076%22%7D&pdp_npi=2%40dis%21XPF%2122714.0%219313.0%21%21%215390.0%21%21%402103250d16614764984578815e1966%2112000019285936076%21sea&curPageLogUid=tE6VyZxSAnJY
Device Name : ums512_1h10_Natv
Build Number : QP1A.190711.020 release-keys
I developed an app for it and I need to debug this app with ADB.
How do I proceed ?
For now, I activated the developper mode and the FileTransfer mode in default USB settings then I connected a male-to-male cable to the 2 USB ports but the device does not pop up the debugging authorization permission.
Thanks for your help !

Kapoe said:
Hello !
I bought this radio head unit on AliExpress (it's the D version) : https://fr.aliexpress.com/item/1005002212221194.html?spm=a2g0o.productlist.0.0.f7057521b4ZITh&algo_pvid=d9ce368e-ff00-495f-a529-2a731b4c08e1&algo_exp_id=d9ce368e-ff00-495f-a529-2a731b4c08e1-3&pdp_ext_f=%7B%22sku_id%22%3A%2212000019285936076%22%7D&pdp_npi=2%40dis%21XPF%2122714.0%219313.0%21%21%215390.0%21%21%402103250d16614764984578815e1966%2112000019285936076%21sea&curPageLogUid=tE6VyZxSAnJY
Device Name : ums512_1h10_Natv
Build Number : QP1A.190711.020 release-keys
I developed an app for it and I need to debug this app with ADB.
How do I proceed ?
For now, I activated the developper mode and the FileTransfer mode in default USB settings then I connected a male-to-male cable to the 2 USB ports but the device does not pop up the debugging authorization permission.
Thanks for your help !
Click to expand...
Click to collapse
I think you are using your unit at a power supply on bench?
May be a solution to use ADB with WiFi to connect to the unit. This is what I use... and on top I use SCRCPY to see the screen on my laptop.
Just give it a try and connect to the unit with the IP of the unit, instead trying to use the USB cable which is mostly not registered.

Hi,
thank you for your reply !
I'm not using the unit on bench but directly in the car, but I can connect it to home wifi
The device address on wifi is 192.168.88.105.
So, I used this command :
$ adb connect 192.168.88.105:5555
cannot connect to 192.168.88.105:5555: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée. (10061)
The result is "connection refused" with error code 10061.
Any idea to fix this ?

Kapoe said:
Hi,
thank you for your reply !
I'm not using the unit on bench but directly in the car, but I can connect it to home wifi
The device address on wifi is 192.168.88.105.
So, I used this command :
$ adb connect 192.168.88.105:5555
cannot connect to 192.168.88.105:5555: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée. (10061)
The result is "connection refused" with error code 10061.
Any idea to fix this ?
Click to expand...
Click to collapse
Did you activate "Open Net ADB" in the developer settings?
On the other side... May be you first need to activate ADB in your device. See this posting: https://forum.xda-developers.com/t/how-to-adb-when-head-unit-has-usb-a-sockets.3879769/post-83181523
You really need to use Terminal Emulator on your head unit. Other emus may not work.
What app are you developing?
Edit: If you are connected to the home WiFi and you have a good battery charger added to the car battery, then you can use SCRCPY sitting on your sofa... I don´t want to miss this tool...

rigattoni said:
Did you activate "Open Net ADB" in the developer settings?
On the other side... May be you first need to activate ADB in your device. See this posting: https://forum.xda-developers.com/t/how-to-adb-when-head-unit-has-usb-a-sockets.3879769/post-83181523
You really need to use Terminal Emulator on your head unit. Other emus may not work.
What app are you developing?
Edit: If you are connected to the home WiFi and you have a good battery charger added to the car battery, then you can use SCRCPY sitting on your sofa... I don´t want to miss this tool...
Click to expand...
Click to collapse
I didn't found "Open Net ADB" in the developer settings...
But I activated ADB as you indicates, and it's better :
$ adb connect 192.168.88.105:5555
failed to authenticate to 192.168.88.105:5555
I tried to copy my adb.pub in /data/misc/adb/adb_keys but I need root access...
I installed apk like OneClickRoot, KingRoot, Kingo Root with no success in rooting

Kapoe said:
I didn't found "Open Net ADB" in the developer settings...
But I activated ADB as you indicates, and it's better :
$ adb connect 192.168.88.105:5555
failed to authenticate to 192.168.88.105:5555
I tried to copy my adb.pub in /data/misc/adb/adb_keys but I need root access...
I installed apk like OneClickRoot, KingRoot, Kingo Root with no success in rooting
Click to expand...
Click to collapse
Did you use ADB on a Windows-PC?
$ adb looks like a terminal thing....
Code:
C:\ADB\scrcpy-win64-v1.19>adb connect 192.168.178.41
* daemon not running; starting now at tcp:5037
* daemon started successfully
connected to 192.168.178.41:5555
BTW... for getting root, you may give a screenshot from "About tablet" or similar, which shows the MCU and firmware you are using,

Kapoe said:
I didn't found "Open Net ADB" in the developer settings...
But I activated ADB as you indicates, and it's better :
$ adb connect 192.168.88.105:5555
failed to authenticate to 192.168.88.105:5555
I tried to copy my adb.pub in /data/misc/adb/adb_keys but I need root access...
I installed apk like OneClickRoot, KingRoot, Kingo Root with no success in rooting
Click to expand...
Click to collapse
From Android 4.2, every ADB device needs to be authorized for a computer to connect. This is done for security. So when a USB is connected a prompt comes asking to authorize the device when USB debugging is set. But does not happen for WIFI ADB.
So the workaround is to connect the device by USB, accepting the machine always. Then when the Wireless ADB is tried, it should work.

rigattoni said:
Did you use ADB on a Windows-PC?
Click to expand...
Click to collapse
Yes, and the "failed to authenticate" message is because, as TorstenH said, my ADB device is not authorized for my computer.
TorstenH said:
From Android 4.2, every ADB device needs to be authorized for a computer to connect. This is done for security. So when a USB is connected a prompt comes asking to authorize the device when USB debugging is set. But does not happen for WIFI ADB.
So the workaround is to connect the device by USB, accepting the machine always. Then when the Wireless ADB is tried, it should work.
Click to expand...
Click to collapse
That's the problem...
In my first message I explained I activated the developper mode and the FileTransfer mode in default USB settings then I connected a male-to-male "data cable" to each 2 USB ports but the device does not pop up the debugging authorization permission.
That's why I tried to copy the adb.pub file from my computer to my device but unsuccessfully due to root rights needed.
I search how to root my device but I found nothing...
{
"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"
}

Kapoe said:
Yes, and the "failed to authenticate" message is because, as TorstenH said, my ADB device is not authorized for my computer.
That's the problem...
In my first message I explained I activated the developper mode and the FileTransfer mode in default USB settings then I connected a male-to-male "data cable" to each 2 USB ports but the device does not pop up the debugging authorization permission.
That's why I tried to copy the adb.pub file from my computer to my device but unsuccessfully due to root rights needed.
I search how to root my device but I found nothing...
Click to expand...
Click to collapse
You could try to enable USB debugging after! you connected your PC. That helped on some smartphone FWs.
And here are some more approaches you could try:
Can't authorise android device in USB debugging mode
I am trying to use a Samsung Galaxy S6 Edge for debugging an android app. I've downloaded and installed the Samsung USB driver but when the device appears in android studio it says the device is
android.stackexchange.com

There is already another thread regarding ADB with these TS10 units.
Seems that they did not find a reliable solution.
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...
forum.xda-developers.com
Even rooting the device is nearly impossible. Search for TS10 root and you find a lot of threads for that.
Not the best unit to work on.

I finally solved my problem by rooting my device and setting manually /data/misc/adb/adb_keys
Thank you for your support !

Kapoe said:
I finally solved my problem by rooting my device and setting manually /data/misc/adb/adb_keys
Thank you for your support !
Click to expand...
Click to collapse
Maybe you can describe how you did this to help other users.

BE CAREFUL ! USE AT OWN RISK !
Firmware update used to root my device :
https://disk.yandex.ru/d/rIBtRseJuNvbTg --> TS10 / TS10.1.2_20220507.095321_THEME1-Rooted.zip

Junsun V1 (pro) 8667 - system modifications

Many system modification (e.g. Status Bar visibility and quick boot) require a modification of files on /vendor partition. There is a lot of information available for Mtk8257 devices - but​not for 8667​devices.​
Because I only own a Mtk8257 device I can only develop and test my apps...
JunsunSleepConfigurator
JunsunSleepConfigurator On Junsun V1 (pro) devices apps get killed before head unit enters sleep mode. So you have to restart the apps every time you continue your ride. The file /vendor/etc/qb_list.xml defines which apps should be just...
forum.xda-developers.com
AppSwitcher - smart SWC launcher (for Junsun, Xtrons and similar devices) incl. autostart
AppSwitcher SWC (Steering Wheel Control) app launcher Stay focused on the street and don't touch the head units display to switch between apps. Support the development of this free app via ko-fi.com/appswitcher Please note: This app is...
forum.xda-developers.com
...on this device.
Hereby I ask the owners of a Junsun 8667 head unit for their support.​Please get in touch if you are ready to run some tests on your head unit and are not afraid of shell commands.​

I tried to get root for model 8667, Magisk method. I found the commands, but there is a problem, it's hard to get detailed information on how to make Windows 11 detect the android radio. I wanted to perform ADB wirelessly, also the radio is not detectable. I heard that first you need to connect the radio with a cable, enter the command in ADB, only then you can work wirelessly in ADB

wybitny2 said:
I tried to get root for model 8667, Magisk method. I found the commands, but there is a problem, it's hard to get detailed information on how to make Windows 11 detect the android radio. I wanted to perform ADB wirelessly, also the radio is not detectable. I heard that first you need to connect the radio with a cable, enter the command in ADB, only then you can work wirelessly in ADB
Click to expand...
Click to collapse
Have you tied this method?
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.
Get su rights:
Code:
su @#zxcvbnmasdfghjklqwertyuiop1234567890,.

I'm sorry

TorstenH said:
Have you tied this method?
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.
Get su rights:
Code:
su @#zxcvbnmasdfghjklqwertyuiop1234567890,.
Click to expand...
Click to collapse
I know a little, I don't have much experience. The strange thing is that even when I connect the radio with a cable, unlike the phone, the android radio is not detectable in Windows 11. Phone connecting to usb, it is detectable and works, android radio no longer. It worked once, but I did something wrong that it was detected without turning on the usb ignition, then I failed to do it a second time.

wybitny2 said:
I know a little, I don't have much experience. The strange thing is that even when I connect the radio with a cable, unlike the phone, the android radio is not detectable in Windows 11
Click to expand...
Click to collapse
Never tried it on my MTK8257 with a cable. Remote adb shell worked without further preparation.
If not it may help to enable USB debugging and try again with Remote adb shell.
If not it may be sufficient to install Termux on the head unit and execute the commands directly on the device.
If not it may work with a cable after changing USB mode (from host to device).
...

TorstenH said:
Never tried it on my MTK8257 with a cable. Remote adb shell worked without further preparation.
If not it may help to enable USB debugging and try again with Remote adb shell.
If not it may be sufficient to install Termux on the head unit and execute the commands directly on the device.
If not it may work with a cable after changing USB mode (from host to device).
...
Click to expand...
Click to collapse
I see you have knowledge, thank you for sharing it. Do you know how to change the host mode on the device, I tried to search, there is no such option in the developer options. Someone wrote that the code 8877 but this code does not work for me, also someone wrote that there are three dots in the developer menu and you can change it there, it also does not work

wybitny2 said:
I see you have knowledge, thank you for sharing it. Do you know how to change the host mode on the device, I tried to search, there is no such option in the developer options.
Click to expand...
Click to collapse
I think there is a three dot menu on the top right in developer options.
Labels may be Chinese so remember the current setting and use a phone with Google Lens to translate it.

TorstenH said:
I think there is a three dot menu on the top right in developer options.
Labels may be Chinese so remember the current setting and use a phone with Google Lens to translate it.
Click to expand...
Click to collapse
The problem is that I don't see the three dots in the developer options, I know there are no options without it

wybitny2 said:
The problem is that I don't see the three dots in the developer options, I know there are no options without it
Click to expand...
Click to collapse
Maybe it can be changed via factory menu 8877.

TorstenH said:
Maybe it can be changed via factory menu 8877.
Click to expand...
Click to collapse
Thanks for such information, you could read about every radio but not 8667. I will check it even more carefully and write what I checked. Thanks again for letting me know your knowledge here. If I manage to do root, I will also write here, it's good to have all the information in one place

wybitny2 said:
Thanks for such information, you could read about every radio but not 8667. I will check it even more carefully and write what I checked. Thanks again for letting me know your knowledge here. If I manage to do root, I will also write here, it's good to have all the information in one place
Click to expand...
Click to collapse
To be honest I try to find somebody who tries (together with me) to modify a system file on a non-rooted device.
That was the intention of this thread.

TorstenH said:
To be honest I try to find somebody who tries (together with me) to modify a system file on a non-rooted device.
That was the intention of this thread.
Click to expand...
Click to collapse
I do not have such knowledge, sorry, my knowledge is limited. All I know is that when it comes to rooting, Magisk Manager is the best, maybe not so much the best but it will do the best.

Created a small app which allows to execute root commands directly on the head unit - without adb.
{
"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"
}
This may simplify the tests on 8667 unit.
Still searching for 8667 users willing to support me...

TorstenH said:
've created a small app that allows you to execute root commands directly on the head unit - without adb.
View attachment 5835641
This can simplify testing on the 8667.
Still looking for 8667 users willing to support me...
Click to expand...
Click to collapse
You have created the application, and how to get it, you can ask for a link. this app works or needs improvement

wybitny2 said:
You have created the application, and how to get it, you can ask for a link. this app works or needs improvement
Click to expand...
Click to collapse
Yes, I created the app. It works on MTK8257 and should do its job on 8667, too. But in a first step I will share it only with a person who will use it to support me: figure out how /vendor partition can be made writeable on 8667 device.

TorstenH said:
Да, я создал приложение. Он работает на MTK8257 и должен работать и на 8667. Но на первом этапе я поделюсь им только с человеком, который будет использовать его для моей поддержки: выясните, как сделать раздел /vendor доступным для записи на устройстве 8667.
Click to expand...
Click to collapse
Головные магнитолы на Android состоят из двух половинок, одна из которых — MCU, вторая — среда APK. Root можно спрятать в MCU, который, кстати, прошивается отдельно от APK. Загрузочные файлы поставщика системы, насколько я понимаю, отключают загрузку системы MCU, которая затем запускает APK из системы и поставщика. Как получить обновленную систему MCU 8767? Заебал этот сай с двойным переводом.Head radios on Android consist of two halves, one of which is the MCU, the second is the APK environment. Root can be hidden in the MCU, which, by the way, is flashed separately from the APK. The system vendor's boot files, as far as I understand, are responsible for loading the MCU system, which then runs the APK from the system and the vendor. How do I get a copy of the MCU 8776 system?

Vendor mounts:
Mtk8257:
8667:

First outcome is new version of JunsunSleepConfigurator which can be used on 8667 devices, now:
JunsunSleepConfigurator
JunsunSleepConfigurator On Junsun V1 (pro) devices apps get killed before head unit enters sleep mode. So you have to restart the apps every time you continue your ride. The file /vendor/etc/qb_list.xml defines which apps should be just...
forum.xda-developers.com
Please note, it's still an alpha version - even if it will not harm your device.

I have V1 on 8667. i can help