Pair watch Wear OS with another smartphone / Tablet without factory reset - Wear OS Software and Hacking General

Hi, I've been researching how to pair multiple smartphones to my watch with Wear OS for a few days. I have come to the following conclusions and an idea.
If you have ever wanted to pair the watch with a new smartphone or tablet, or you have simply updated your smartphone to a new Custom ROM, you have probably noticed that Google does not make it easy to pair again. The official way of Wear OS requires unpairing the watch from the WearOS App and then it is restored to factory settings (which means deleting all the data and apps installed on the watch), and from there you can see the new device to pair (info on this here ), however there is a simple way to avoid resetting the watch settings to zero. This method does not require root either on the smartphone or on the watch, but it does require executing 3 ADB commands, which at least from the Ticwatch 3 Pro can only be entered via Wi-fi, basically they are the following (link where the method is detailed):
Code:
adb connect IP-of_watch:5555
adb shell "pm clear com.google.android.gms && reboot
adb shell "am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE
In this way, you can pair with a new device without resetting the watch to factory settings, but this method requires a computer and is not a very quick procedure to pair with another device when you need it.
Pairing the watch to just one device is enough for most people, but some have more devices that they would find useful if it could be paired and changed from time to time. For example, in the morning link the watch with your work phone, and in the afternoon with your personal phone; Another case is when it is paired to a small phone for when I go running (that is also my case). Anyway, it seems very useful to me.
The case that I was investigating and it seems that a few years ago (specifically in 2015) a method was published in XDA (here the link) that seems very practical for what I propose, the method is the following:
Note: the first 4 steps are only done the first time, once the phones have been paired to the watch, from there for the quick change only step 5.
Install ADB drivers on your computer and activate USB debugging on your phone, and Debugging via Wi-Fi. This last is because the charging cable of the Ticwatch 3 Pro is only charging, it does not transmit data, as a curiosity the charging cable of the TicWatch Pro 2020 is also data, so it would be enough to activate only ADB debugging and plug the smartwatch to the cable .
Download the Android Wear BeeLink App from this link on the computer, and install the app on the watch through ADB commands from the computer. .
Code:
adb connect IP_of_Watch:5555
adb push beelink.apk /sdcard/
adb -e install beelink.apk
adb disconnect
smartwatch is paired with phone A, so turn off Bluetooth on this device and run the following command from the computer.
Code:
adb shell "pm clear com.google.android.gms && reboot
Turn on Bluetooth on phone B, and pair the watch as normal through the WearOS app on phone B.
Now when you want to switch to phone A, you open Beelink on the watch, and it will search for nearby Android devices that are available to pair. On the app screen you will see the current phone as 'paired' and it also allows you to select any other device if you want to change. Once the watch has connected to a device, it generally remembers it and will automatically connect if no other connections are available.
{
"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"
}
Therefore, BeeLink is ideal for quick exchange of pairings while multiple devices are switched on. And now comes the big problem and in which I claim the help for those who might be interested in this functionality, BeeLink NO LONGER WORKS. The app was discontinued (only an initial version was published) and disappeared from the Play Store in 2015. It can be installed but the app cannot be opened, that is, it is installed but does not appear in the application drawer. I guess it stopped working from some WearOS update.
It would be very interesting if the creator of the app, VizTec (seems gone), or someone with knowledge adapted it to current versions of WearOS. I don't know, if this works, I think it would be very useful, since you don't need a computer to change devices like the method I explained at the beginning of the post. However, does anyone know of an alternative method to do this?
Here is more information about the BeeLink App:
Android Wear BeeLink app - Review - Smart Tech Guide, Consultancy & Magazine by Dr Prem Jagyasi
VizTec has come up with a solution to your Android Wear connectivity problems. It has launched an app called Android Wear BeeLink, which helps you to connect your Android Wear to any other device.
drprem.com
Android Wear BeeLink Finally Lets You Pair Your Watch With A New Device Relatively Painlessly
www.androidpolice.com
BeeLink for Android Wear - Aplikácie pre Android v aplikácii Google Play
web.archive.org

Actually, we can use adb with bluetooth. I have the TicWatch 3 Pro, but did not have a working wifi here at work, so I tried with bluetooth via the phone:
Using the guide from Android Developer to get PC and watch connected via bluetooth. I'm repeating here in case the address changes:
First make sure your watch and phone are paired with bluetooth (in bluetooth settings).
Next make sure your phone is connected to the PC and are ready for adb commands.
Now on the watch
Open the watch's Settings menu.
Scroll to Developer Options.
Confirm that ADB debugging is enabled.
Enable Debug over Bluetooth.
On the Phone:
Open the Wear OS app.
Scroll down to Advanced Settings and tap to view the Advanced Settings options.
Enable Debugging over Bluetooth. A status message appears under the option. It looks like this:
Code:
Host: disconnected
Target: connected
On the PC:
Run these two commands in the debugger (WIN: a cmd window - Linux: a terminal):
Code:
>adb forward tcp:4444 localabstract:/adb-hub
>adb connect 127.0.0.1:4444
After you type the connect command, look at the watch. It will ask you to confirm that you are allowing ADB Debugging.
Go back to the phone and check the status display in the Wear companion app. It should look like this:
Code:
Host: connected
Target: connected
Now we are ready to send commands to the watch.
Check that the phone and watch are connected:
Code:
>adb devicesList of devices attached
K8AIHM######BBY device
127.0.0.1:4444 device
Run the command from previous post (slightly changed to direct the command to the watch):
Code:
>adb -s 127.0.0.1:4444 shell "pm clear com.google.android.gms && reboot"
Watch should reboot and PC answer with:
Code:
Success

It's nice, but it doesn't keep Google Pay cards, every time one switch phones they need to be re-added.

It doesn't work at this time (or for me). After type
Code:
adb shell "pm clear com.google.android.gms && reboot"
cmd answer
Code:
/system/bin/sh: "pm: not found
Success for me typing 2 commands:
1) adb shell
2) pm clear com.google.android.gms && reboot
Spoiler

Related

[APP][ROOT] WearToolbox V1.54 (16-04-2016)

DISCLAIMER:
I'm not responsible for damage to your phone or watch.
You are using this app at your own responsibility
WearToolbox was just an idea to make life easier.
With WearToolbox you can connect from your phone to your watch through adb, with this it's possible to send commands or sideload apps etc. (see features).
For now design doesn't matter for me, functionality does. Design will be better when app is in a further stage.
When enough people have tested it and provided me feedback, it will be released in the Play Store for easier updating.
The app is in DEVELOPMENT and TEST stage and can have BUGS.
Tested on LG Watch R with Android Wear 5.1.1 and LG G2 5.0.2
Have fun with it and let me know if it works or not!
FEATURES
- Automatic installation of necessary binaries (adb -> /system/bin/)
- Automatic connection
- Reboot (system, recovery, bootloader)
- Sideload apps (/sdcard/WearToolbox/sideload/)
- Uninstall apps
- Push files to /sdcard/
- Send adb commands (adb command)
- Send shell commands (adb shell command)
- ADB and shell command history
- Script parser for own created scripts
TODO:
- Make a nicer UI
IDEAS:
- Pull files
- ADB filebrowser
REQUIREMENTS
- Enabled debug and bluetooth debug on android watch, developer options (youtube)
- Enabled debug on phone, developer options
- Enabled debug in Android Wear app, under settings
- Rooted phone
FAQ:
Q: How to use root with shell:
A:
Code:
"su -c '[COMMAND]'"
Snippets:
Code:
"su -c 'echo 85 > /sys/class/timed_output/vibrator/amp'"
Code:
"su -c 'echo 120 > /sys/class/timed_output/vibrator/driving_ms'"
Code:
wm density 200
Q: How to sideload apps:
A: Place apk in the folder /sdcard/WearToolbox/sideload/, restart WearToolbox, choose right apk, click sideload, wait a long time
Q: How to use scripts:
A: Make for example a dummy.txt file in /sdcard/WearToolbox/scripts/ with shell commands in it. Each command on a newline. Save it, restart WearToolbox, test it.
Example (vibrate.txt):
Code:
cat /sys/class/timed_output/vibrator/amp
cat /sys/class/timed_output/vibrator/driving_ms
"su -c 'echo 85 > /sys/class/timed_output/vibrator/amp'"
"su -c 'echo 120 > /sys/class/timed_output/vibrator/driving_ms'"
cat /sys/class/timed_output/vibrator/amp
cat /sys/class/timed_output/vibrator/driving_ms
DOWNLOAD
https://play.google.com/apps/testing/com.diechel.xda.weartoolbox
I might go ahead and try this. Having something like this would be very very useful. (fyi, I believe you initial change log date has the wrong month. Unless it is June 31st already)
Rennat said:
I might go ahead and try this. Having something like this would be very very useful. (fyi, I believe you initial change log date has the wrong month. Unless it is June 31st already)
Click to expand...
Click to collapse
Haha yes youre right about the changelog Will change.
Let me know if it works and what you think about it.
What features would you like etc etc.
stuck on "Checking Connection" for me Sammy 5.1.1 S6 Edge (arm64) and LGWR 5.1.1
EDIT - seems to download binaries every time I open the app, still won't connect - perhaps something to do with arm64 architechture ???
EDIT2 - in Android Wear Manager bluetooth debugging ON, it says HOST disconnected, TARGET connected
kashortiexda said:
stuck on "Checking Connection" for me Sammy 5.1.1 S6 Edge (arm64) and LGWR 5.1.1
EDIT - seems to download binaries every time I open the app, still won't connect - perhaps something to do with arm64 architechture ???
EDIT2 - in Android Wear Manager bluetooth debugging ON, it says HOST disconnected, TARGET connected
Click to expand...
Click to collapse
- Can you check if the files 'adb' and 'fastboot' are present in /system/bin/
- What is there permission? should be 755
- Are the files 'adb' and 'fastboot' on your root of your /sdcard/
- Can you type 'adb' and 'fastboot' in terminal and post output
- Can you type 'mount -o remount, rw /system' in terminal and post output
For me HOST and TARGET are connected in Android Wear App
@Diechel , I have adb but not fastboot in /system/bin
Okay copied adb and fastbook to /system/bin and 755'd them.
{
"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"
}
kashortiexda said:
Okay copied adb and fastbook to /system/bin and 755'd them.View attachment 3343013
Click to expand...
Click to collapse
i see something weird
Code:
localhost:4444:4444
should be
Code:
localhost:4444
Will look if i can find something.
Also wondering why copying didnt work, was searching all over the internet how to correctly remount /system
My output is as follows, see attachment. Of course a newer version but nothing changed to adb init
@Diechel am I supposed to have my watch or phone plugged into my PC by USB when doing all this / running weartoolbox ?
kashortiexda said:
@Diechel am I supposed to have my watch or phone plugged into my PC by USB when doing all this / running weartoolbox ?
Click to expand...
Click to collapse
No just bluetooth connected to each other.
And all the 3 debugging option on as stated in the OP
Edit:
Build 21 online
Yip got all that but no adb devices and the localhost:4444:4444 is clearly wrong
Would a logcat help
kashortiexda said:
Yip got all that but no adb devices and the localhost:4444:4444 is clearly wrong
Would a logcat help
Click to expand...
Click to collapse
I dont know if logcat helps, what you can try is manually connect with terminal on your phone.
Code:
su
adb kill-server
setprop service.adb.tcp.port 5555
stop adbd
start adbd
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444
adb devices
Each line need to be filled in, not all together.
And try build 21
Did the manual Terminal stuff and it FIXED the 4444 problem, installed v21 and.....[emoji1]
kashortiexda said:
Did the manual Terminal stuff and it FIXED the 4444 problem, installed v21 and.....[emoji1]
View attachment 3343080
Click to expand...
Click to collapse
TADAAAAAA
GOOD!
Let me know if you have ideas to implement. First i go for functionality then change the user interface a bit
@Diechel
EDIT: I tried sideloading es file explorer apk ... worked !!! [emoji1]
kashortiexda said:
@Diechel I tried sideloading es file explorer apk ...it says done but nothing on watch.
Have you successfully sideloaded any apks ?
Click to expand...
Click to collapse
Yes i had, will try again.
It takes some time for the watch to install, will try now and report back!
Edit:
From what i see now is that the message done comes too fast.
Bluetooth is slow and is still transferring after the done message, can see that in my top bar.
Seems not working indeed, will check thanks
EDIT:
It got installed after a while
Good that it is working! Will see how i can report in log
I got it installed too, yes the done is misleading .... GREAT app btw, well done [emoji106] [emoji106]
kashortiexda said:
I got it installed too, yes the done is misleading .... GREAT app btw, well done [emoji106] [emoji106]
Click to expand...
Click to collapse
Haha thank you, now there is a message that you need to wait untill it arrives on your watch, bluetooth is slow
@Diechel are you planning on adding the trickier "adb remove sideloaded app" but I think it may not be possible. .
kashortiexda said:
@Diechel are you planning on adding the trickier "adb remove sideloaded app" but I think it may not be possible. .
Click to expand...
Click to collapse
Can try at least, I think it's possible. Maybe a lot of work

[BREVENT] A ‘No Root’ alternative to Greenify

First and foremost I am not the developer of this App! I just discovered it and thought those of you missing Greenify might find this useful.
[What's Brevent]
There are a lot of apps which claim to prevent apps from running. However, most of them requires ROOT, or do a system modification via Xposed or patching or unlocked bootloader.
Brevent can app-standby or force-stop apps, prevent apps from running in long time. It doesn't require ROOT, nor modify system. Furthermore, it may doesn't work well on ROOT or modified system. There is an experimental feature to start Brevent Server without adb, please read guide - permissions.
Brevent supports Android 5.0 to Android O DP3, requires "USB debugging" in "developer options". I mainly used it on Google Pixel with Android 7.1.2.
[Simple Guide]
0. (Device) open Brevent, read "Guide"
1. (Device) open Brevent, navigate to "Developer Options", turn on "USB debugging"
2. (PC) Download ADB: https://developer.android.com/studio/releases/platform-tools.html
(If you live in China, you can download it here too: https://developer.android.google.cn/studio/releases/platform-tools.html)
3. (PC) Uncompress, navigate to "platform-tools" directory in Command Line, refer to "Guide - ADB"
4. (PC and Device) connect device and PC with usb cable, type "adb devices" in PC Command Line, and confirm the authorized dialog on Devices if needed
5. (PC) type "adb -d shell sh /data/data/me.piebridge.brevent/brevent.sh" in PC Command Line
[FeedBack]
For any issues, please open an issue at github with logs: https://github.com/brevent/Brevent/issues
1. crash log (in PC's command line): adb -d logcat -d -b crash
2. brevent server log (in PC's command line): adb -d logcat -d -b main -s BreventServer BreventLoader
2.1. enable debug for Brevent Server, type in PC's command line: adb -d shell setprop log.tag.BreventServer DEBUG, then get brevent server log
2.2. disable debug for BreventServer, type in PC's command line: adb -d shell setprop log.tag.BreventServer "" (Note for the back slash)
https://play.google.com/store/apps/details?id=me.piebridge.brevent&hl=en
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Alternative To Greenify, Native Feature
ggrant3876 said:
First and foremost I am not the developer of this App! I just discovered it and thought those of you missing Greenify might find this useful.
[What's Brevent]
There are a lot of apps which claim to prevent apps from running. However, most of them requires ROOT, or do a system modification via Xposed or patching or unlocked bootloader.
Brevent can app-standby or force-stop apps, prevent apps from running in long time. It doesn't require ROOT, nor modify system. Furthermore, it may doesn't work well on ROOT or modified system. There is an experimental feature to start Brevent Server without adb, please read guide - permissions.
Brevent supports Android 5.0 to Android O DP3, requires "USB debugging" in "developer options". I mainly used it on Google Pixel with Android 7.1.2.
[Simple Guide]
0. (Device) open Brevent, read "Guide"
1. (Device) open Brevent, navigate to "Developer Options", turn on "USB debugging"
2. (PC) Download ADB: https://developer.android.com/studio/releases/platform-tools.html
(If you live in China, you can download it here too: https://developer.android.google.cn/studio/releases/platform-tools.html)
3. (PC) Uncompress, navigate to "platform-tools" directory in Command Line, refer to "Guide - ADB"
4. (PC and Device) connect device and PC with usb cable, type "adb devices" in PC Command Line, and confirm the authorized dialog on Devices if needed
5. (PC) type "adb -d shell sh /data/data/me.piebridge.brevent/brevent.sh" in PC Command Line
[FeedBack]
For any issues, please open an issue at github with logs: https://github.com/brevent/Brevent/issues
1. crash log (in PC's command line): adb -d logcat -d -b crash
2. brevent server log (in PC's command line): adb -d logcat -d -b main -s BreventServer BreventLoader
2.1. enable debug for Brevent Server, type in PC's command line: adb -d shell setprop log.tag.BreventServer DEBUG, then get brevent server log
2.2. disable debug for BreventServer, type in PC's command line: adb -d shell setprop log.tag.BreventServer "" (Note for the back slash)
https://play.google.com/store/apps/details?id=me.piebridge.brevent&hl=en
Click to expand...
Click to collapse
One of the reasons I rate this phone so highly is that there are plenty of 'native' features present that make rooting less necessary.
My phone is a UK Sky Mobile Exynos model, and under 'Maintenance', 'Battery' there is an option to put 'non running' apps to sleep, just like 'Greenify'. I don't know if this is true for other regions or carrier's. Maybe other people can check this to see if it's so for their region and carrier.
kxdaorbit said:
One of the reasons I rate this phone so highly is that there are plenty of 'native' features present that make rooting less necessary.
My phone is a UK Sky Mobile Exynos model, and under 'Maintenance', 'Battery' there is an option to put 'non running' apps to sleep, just like 'Greenify'. I don't know if this is true for other regions or carrier's. Maybe other people can check this to see if it's so for their region and carrier.
Click to expand...
Click to collapse
I agree with you on the phone but there are two features that I miss with root.
1. Titanium Backup - they ability to back up your apps and data. I know there is Samsung Cloud but I'm not a big fan of cloud based services.
2. TWRP - the ability to back up your whole phone and restore it if needed.
ggrant3876 said:
I agree with you on the phone but there are two features that I miss with root.
1. Titanium Backup - they ability to back up your apps and data. I know there is Samsung Cloud but I'm not a big fan of cloud based services.
2. TWRP - the ability to back up your whole phone and restore it if needed.
Click to expand...
Click to collapse
I get your apprehension about cloud based services, but this is 2017, you'll have to bite the bullet sooner rather than later.
Also don't forget, if you have really super sensitive or personal data that you can't trust to cloud based services, we have 'Smart Switch'. Enables you to make as close to a 'nandroid' backup as is possible, and to store it locally. You can then restore single elements or the whole phone. Thank you Samsung.
kxdaorbit said:
I get your apprehension about cloud based services, but this is 2017, you'll have to bite the bullet sooner rather than later.
Also don't forget, if you have really super sensitive or personal data that you can't trust to cloud based services, we have 'Smart Switch'. Enables you to make as close to a 'nandroid' backup as is possible, and to store it locally. You can then restore single elements or the whole phone. Thank you Samsung.
Click to expand...
Click to collapse
Yes I read a thread yesterday that said you can use Smart Switch and back it up to your sdcard. It's getting better, I started with the T-Mobile G-1 and the only way to root and even do screenshots was with adb. I learned adb and it has served me well on android, even on the S8+ to get rid of the battery icon I had to run a few commands to get SystenTuner UI to work.
Why don't you just use Samsung built in always sleeping option for apps? Works great
Compusmurf said:
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Click to expand...
Click to collapse
If you have rooted, it's not problem.
And if you don't have rooted, no other alternative third-party apps can app-standby other apps or force-stop apps quickly.
I am rooted, but the app doesnt seem to see that I am rooted.
MrPhilo said:
Why don't you just use Samsung built in always sleeping option for apps? Works great
Click to expand...
Click to collapse
I agree, s8 already have functions to put your apps to sleep immediately without waiting 3 days.
{
"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"
}
Sent from my SM-G955F using Tapatalk
BratPAQ said:
I agree, s8 already have functions to put your apps to sleep immediately without waiting 3 days.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
how do you get here ?
crayonyes said:
how do you get here ?
Click to expand...
Click to collapse
Settings - Device Maintenance - Battery
Then at the very bottom is "always sleeping apps"
Sent from my SM-G955F using Tapatalk
BratPAQ said:
Settings - Device Maintenance - Battery
Then at the very bottom is "always sleeping apps"
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
got it, Thanks
Where is the experimental feature to start server without adb?
mrQQ said:
Where is the experimental feature to start server without adb?
Click to expand...
Click to collapse
suku_patel_22 said:
I am rooted, but the app doesnt seem to see that I am rooted.
Click to expand...
Click to collapse
]
Compusmurf said:
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Click to expand...
Click to collapse
If you have Root
Just press "back" about 6 times
And then a new menu appears
There you press on "ROOT"....

[S905x] Skip's Mi TV Box (USA) Tools v1.00 (Android TV MDZ-16-AB)

Hello My XDA Family!!
Skip's Mi TV Box (USA) Tools v1.00
I take no responsibility for anything you do to your device.
*use at own risk*
~<Before You Start>~
This works best with
MM Build MiBOX3_USA_once_r454
-or-
Noughaut Beta Build 1028
The device has to be in developers mode and you must have a USB to USB cable.
~<What's it Do>~
This tool is a bunch of scripts that uses adb commands.
It will do:
-Teathered Root (USB boot teather required) *use at own risk*
-install BusyBox
-disable/enable OTA updates
-adds SheildTV's keylayouts
-Lite Pack (like AOSP)
-Skip Pack (How I like Mine... MM version adds PurePack from NexusPlayer)
-Kodi Pack (Makes Kodi your Home Button)
-Android Pack (Makes your device look like a tablet)
~<How to>~
Do options 1 - 4, pick Marshmallow or Nougat then pick your pack.
~<Downloads>~
Skip's Mi TV Box (USA) Tools v1.00
~<Thank You>~
krytikul, evilpotatoman, daivietpda, and dhacker29.​
~<Change Log>~
v1.0 release build
Hey @skippyd
First of all thx for this tool and that after half of a year I could change my launcher.
I have little off topic question - do you know what I have to do so other launchers also could put widgets on dekstop?
Launcher3 can do this, bo NovaLauncher and Lawnchair crashes when I try to put widget on desktop.
Does the tethered usb root mean I have to plug it in to a computer at every boot? Is it possible to plugin some kind of device in the USB-port to do this automatically at reboot?
I am right now running 1028, but I am having small issues, like microlag and audio stutters. Is it worth reflashing 1028 to a fresh image?
Heres something else you may like to add, the mibox doesnt come will a full set of keymaps fro other controllers (of particular interest to me was the xbox 360 wireless pads) so after some pokeing about I found keymaps here https://www.s-config.com/ouya-support-xbox-360-controllers/ and pushed these to the box and after a reboot it all worked . I dont see a reason why they would change you may be able to pull newer version from the Shield TV.
The Instuctions below are what worked for me though they are very rough and ready and I only pushed the xbox wireless keymaps
Mount Systems and push new Generic.kl
* ADB connect MIBOX-ip
* ADB root
* ADB connect MIBOX-ip
* ADB remount
* ADB push Vendor_045e_Product_0291.kl /system/usr/keylayout/Vendor_045e_Product_0291.kl
* ADB push Vendor_045e_Product_0719.kl /system/usr/keylayout/Vendor_045e_Product_0719.kl
flipside101 said:
Heres something else you may like to add, the mibox doesnt come will a full set of keymaps fro other controllers (of particular interest to me was the xbox 360 wireless pads) so after some pokeing about I found keymaps here https://www.s-config.com/ouya-support-xbox-360-controllers/ and pushed these to the box and after a reboot it all worked . I dont see a reason why they would change you may be able to pull newer version from the Shield TV.
The Instuctions below are what worked for me though they are very rough and ready and I only pushed the xbox wireless keymaps
Mount Systems and push new Generic.kl
* ADB connect MIBOX-ip
* ADB root
* ADB connect MIBOX-ip
* ADB remount
* ADB push Vendor_045e_Product_0291.kl /system/usr/keylayout/Vendor_045e_Product_0291.kl
* ADB push Vendor_045e_Product_0719.kl /system/usr/keylayout/Vendor_045e_Product_0719.kl
Click to expand...
Click to collapse
+1 for this to be added.
Q1 (sorry): If we have a temporary root could we then zap and remove completely any unwanted apps or should we freeze/remove them like the Kindle Fire 7 using ADB to just hide them?
Q2: This seems to be the only Android box (except Shield) which has a legit working CAST function so I am seriously considering getting some to replace other boxes and Chromecasts... Does that work well with this box?
Thanks for the tool. If I get one I'm sure I will use it!
joq3 said:
Does the tethered usb root mean I have to plug it in to a computer at every boot? Is it possible to plugin some kind of device in the USB-port to do this automatically at reboot?
I am right now running 1028, but I am having small issues, like microlag and audio stutters. Is it worth reflashing 1028 to a fresh image?
Click to expand...
Click to collapse
the "rooted" firmwares are userdebug firmwares.. userdebug comes with adb root shell which is y its a "tethered" root.. all this tool does is compile already available stuff into a sort of gui lol
with that being said, u cannot simply plug in "some kind of device" and have it do anything lol it has to be adb and anything u do is limited to a root shell.. this isnt root like everyone hopes for lol.. im surprised no ones done it tho
flipside101 said:
Heres something else you may like to add, the mibox doesnt come will a full set of keymaps fro other controllers (of particular interest to me was the xbox 360 wireless pads) so after some pokeing about I found keymaps here https://www.s-config.com/ouya-support-xbox-360-controllers/ and pushed these to the box and after a reboot it all worked . I dont see a reason why they would change you may be able to pull newer version from the Shield TV.
The Instuctions below are what worked for me though they are very rough and ready and I only pushed the xbox wireless keymaps
Mount Systems and push new Generic.kl
* ADB connect MIBOX-ip
* ADB root
* ADB connect MIBOX-ip
* ADB remount
* ADB push Vendor_045e_Product_0291.kl /system/usr/keylayout/Vendor_045e_Product_0291.kl
* ADB push Vendor_045e_Product_0719.kl /system/usr/keylayout/Vendor_045e_Product_0719.kl
Click to expand...
Click to collapse
OK so either this was added to start with and i just didnt RTFM and if so im sorry and will do better next time OR its been added in which case THANK YOU. (though looking at the editied date on the post i think the former may be the case )
hello what is Skip Pack PurePack from NexusPlayer
Thanks Skippy , just ordered a male to male usb cable to finish the job (now waiting)
Looking forward to install "pure android" , lets hope your tool/scripts works on the Mi Box 3 , as in the past for my nexus devices (also with your tools)
It's always a bit of risk.
Already downloaded the 'MM Build MiBOX3_USA_once_r454' file for the usb stick.
suggestions or help/tips always welcome ( found also this on reddit https://www.reddit.com/r/AndroidTV/comments/5fd0ry/rooting_the_mi_box_mdz16ab/ just in case)
btw, anyone succeeded with this Skip tool ? its quiet here
It works on Marsh mellow, I have yet to get Nougat to do anything but bootloop when rooting. Also, I had to change the command in the script for the SELinux disable option as it's set to Disable Verity.
I shall go for the MM version.
Btw, is it a 'Pure Android' version?
Sent from my Mi A1 using XDA Premium HD app
@skippyd Hello, does that work with a MDZ-16AB Global?
Mr Skippy Seems to be very quiet ....
Sent from my Mi A1 using XDA Premium HD app
Fooox1 said:
@skippyd Hello, does that work with a MDZ-16AB Global?
Click to expand...
Click to collapse
Do you read the title of the topic?
{
"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"
}

[APP][NO ROOT] ADB on Boot | Run adb commands at boot automatically

How to use?
1. Enable ADB Debugging from Fire TV settings
2. In this app, add the adb commands that you want to execute on every boot
3. Set whether you want to display a Toast message on completion of command execution
4. Test the script if you want by pressing "Test Script" button.
5. Apply the configs by pressing the apply button.
Support the work by purchasing it from here
Note: when you run this app for the first time, you should press the test script button, so that app can acquire adb permission. If you don't do this, then the adb permission prompt would appear when you boot the stick for the first time, after installing and opening this app.
That's all
Also note that, the commands you'll write here should be without "adb shell" prefix.
For example,
you have to write
echo "Hello World"
and not
adb shell echo "Hello World"
{
"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"
}
(or multiple commands separated by semi-colon ' ; ' )
Awesome thanks!
Is it possible to combine commands with ; or add a delay?
Spamm00r said:
Awesome thanks!
Is it possible to combine commands with ; or add a delay?
Click to expand...
Click to collapse
Yes you can add multiple commands with ; and add a delay using sleep command.
Example,
sleep 3; echo "I'm here after 3 seconds";
Shaikh Amaan FM said:
Yes you can add multiple commands with ; and add a delay using sleep command.
Example,
sleep 3; echo "I'm here after 3 seconds";
Click to expand...
Click to collapse
Perfect!
Did you test wether you can use this app to issue "adb tcpip 5555" command at bot so that the adb wifi tasker function can do the rest? Thatway we would have adb shell on a non rooted device all the time.
Spamm00r said:
Perfect!
Click to expand...
Click to collapse
let me know if you are able to get your work done
Spamm00r said:
Perfect!
Did you test wether you can use this app to issue "adb tcpip 5555" command at bot so that the adb wifi tasker function can do the rest? Thatway we would have adb shell on a non rooted device all the time.
Click to expand...
Click to collapse
The issue with Tasker is something else as far as I can see. May be because Tasker have subscription checking thing in it and it needs Google Libraries which are not available in fire os.
So I finally was able to test this. The app does work ok.
I'd like to be able to execute these scripts not only at boot. For example like when you press test script, I'd like to be able to run the app anytime I want the script to execute.
Can you please also add an setting that allows the scripts to be executed by just opening the app, so that you are not limited to run these scripts only at boot or when you manually press " test script". So we could use these scripts anytime we run this app for example via Tasker.
Why does the shell execution work with this app but not with taskers adb shell?
Spamm00r said:
So I finally was able to test this. The app does work ok.
I'd like to be able to execute these scripts not only at boot. For example like when you press test script, I'd like to be able to run the app anytime I want the script to execute.
Can you please also add an setting that allows the scripts to be executed by just opening the app, so that you are not limited to run these scripts only at boot or when you manually press " test script". So we could use these scripts anytime we run this app for example via Tasker.
Why does the shell execution work with this app but not with taskers adb shell?
Click to expand...
Click to collapse
Are you able to use Tasker in the stick?
I tried in my device and it won't even show a simple Toast and possible reason as I said is that Tasker have subscription checking thing in it and that requires Play services which are missing in Fire OS. So unless you have direct purchased version of Tasker or unless you install Play services in it, I don't see any good way of running Tasker in it.
Shaikh Amaan FM said:
Are you able to use Tasker in the stick?
I tried in my device and it won't even show a simple Toast and possible reason as I said is that Tasker have subscription checking thing in it and that requires Play services which are missing in Fire OS. So unless you have direct purchased version of Tasker or unless you install Play services in it, I don't see any good way of running Tasker in it.
Click to expand...
Click to collapse
Yes I have Tasker running on FireTV 4K without play service. You can download an apk with 7 day trial directly from the tasker website and it works without playstore. If it has issues with subscription or trial expired, it will tell so and refuse to execute some advanced features.
I can run intents and stuff with tasker just fine, but as Fire TV has no Accessibility service installed, you can not use most of the nice features and plugins of Tasker. Issuing shell commands for example does not work. so I can not issue any keyinput with tasker. That's why I have to rely on your app.
With your app however I was able to completely avoid tasker for now.
I used Tasker to run an intent that opens a youtube link. Now I run this intent from your app. Also i can now issue keyinput with your app. With Tasker that was not possible due to missing accessibility service, which Tasker relies on.
How is your app able to issue keyinput via shell, while tasker can not due to mssing accessibility services? Maybe you can make your app more advanced and allow it to be used as a proxy for issuing shell keyinput on devices without accessibility service. This is the one single reason why I wish i had root on this device. Just to have accessibility service back, which Amazon removed in the recent firmware versions.
I use input to press home key, which makes Fire TV switch the HDMI input of the TV to itself. Now Whenever I start the tv, Fire TV automatically switches input to itself and starts playing youtube.
What I now also want is to be able to use your app also after boot, as I need to switch input and issue keyinput after boot while running several times. Thats why I asked you to add an option to runn it also after boot.
Because if I press "test script" keyinput also works with your app. But not with Tasker.
Will it work, if I open your app with intent "android.intent.action.MAIN"? Will it execute the shell script like when at boot? if yes, then I will try to run this intent from Tasker.
Also It would be good if it was possible to have multiple scripts that you can execute so that you are not stuck with one single script. For example allow to save script a, b, c etc, and then have an intent to be ebale to run a specific script a, b or c. etc..
Your script is very helpful and solves a big problems that amazon has introduced by cutting accesisbility service. Without your app, fire tv would be so useless for me. Thanks for releasing it.
Spamm00r said:
What I now also want is to be able to use your app also after boot, as I need to switch input and issue keyinput after boot while running several times. Thats why I asked you to add an option to runn it also after boot.
Because if I press "test script" keyinput also works with your app. But not with Tasker.
Click to expand...
Click to collapse
Yes this can be done, but i'm busy in something else, so it might take a while
Spamm00r said:
Also It would be good if it was possible to have multiple scripts that you can execute so that you are not stuck with one single script.
Click to expand...
Click to collapse
For having multiple scripts, currently I think you can do it by creating different bash files containing scripts and store them somewhere in Fire Device's storage and then execute them (but probably you'll face problem in giving execute permission to those bash files), this process can be made easier but as I said would take time.
Shaikh Amaan FM said:
Yes this can be done, but i'm busy in something else, so it might take a while
For having multiple scripts, currently I think you can do it by creating different bash files containing scripts and store them somewhere in Fire Device's storage and then execute them (but probably you'll face problem in giving execute permission to those bash files), this process can be made easier but as I said would take time.
Click to expand...
Click to collapse
OK no problem. Take your time.
I don't think that you can execute scripts without root. How does your app execute these scripts without root permissions?
Also sometimes the script is not executed, not at boot and not when I press "test script". I think maybe adb is being blocked by some other app? I have to look into why this happens.
Spamm00r said:
OK no problem. Take your time.
I don't think that you can execute scripts without root. How does your app execute these scripts without root permissions?
Also sometimes the script is not executed, not at boot and not when I press "test script". I think maybe adb is being blocked by some other app? I have to look into why this happens.
Click to expand...
Click to collapse
Which fire device do you have and what's the Fire OS version in it. App doesn't works in Fire OS 5, in Fire OS 6, you have to make sure that no other device/service is connected to ADB, In Fire OS 7, I didn't saw any issue
Shaikh Amaan FM said:
Which fire device do you have and what's the Fire OS version in it. App doesn't works in Fire OS 5, in Fire OS 6, you have to make sure that no other device/service is connected to ADB, In Fire OS 7, I didn't saw any issue
Click to expand...
Click to collapse
I have Fire TV Stick 4k and OS is 6. I figured out why it sometimes doe snot work. it is because ADB is occupied by another app. If I disable and enable adb debugging and thatway break any exisiting connections, it works fine. I just have to make sure that no other app blocks adb, as apparently only 1 app can be connected to adb at a time.
That might be another point of improvement, to make sure that adb is not left occupied.
Spamm00r said:
I have Fire TV Stick 4k and OS is 6. I figured out why it sometimes doe snot work. it is because ADB is occupied by another app. If I disable and enable adb debugging and thatway break any exisiting connections, it works fine. I just have to make sure that no other app blocks adb, as apparently only 1 app can be connected to adb at a time.
That might be another point of improvement, to make sure that adb is not left occupied.
Click to expand...
Click to collapse
In fire os 7, there's no such issue. But yeah in fire os 6 I have tested, only one service or device can connect to adb at a time, and I don't think there's anything I can do about it
Shaikh Amaan FM said:
In fire os 7, there's no such issue. But yeah in fire os 6 I have tested, only one service or device can connect to adb at a time, and I don't think there's anything I can do about it
Click to expand...
Click to collapse
My exact Fire OS is: Fire OS 6.2.8.1
WHich Fire TV Stick has OS 7?
Being able to connect multiple clients to adb is a big step forward. Right now I have to manually toggle adb access to allow other tools to connect to adb. This is a big problem.
Spamm00r said:
My exact Fire OS is: Fire OS 6.2.8.1
WHich Fire TV Stick has OS 7?
Being able to connect multiple clients to adb is a big step forward. Right now I have to manually toggle adb access to allow other tools to connect to adb. This is a big problem.
Click to expand...
Click to collapse
I have Fire Stick 3rd gen.
New devices including Fire Stick Lite are running Fire OS 7.x and I can connect multiple different devices/services to adb at the same time without any issue.
Curious that the Lite has newer Fire OS Version than man other devices. In this case it would be desirable to update, but until then how can make sure that your app or any other app disconnects form adb and gives it free to use for other applications.
Right now I have to manually go to developer settings and toggle ADB off and on to make it available to other apps. Otherwise, adb will be occupied by the last app that used it.
Is it possible to automate this? Adding "disconnect" to the shell command didn't help.
Spamm00r said:
Curious that the Lite has newer Fire OS Version than man other devices. In this case it would be desirable to update, but until then how can make sure that your app or any other app disconnects form adb and gives it free to use for other applications.
Right now I have to manually go to developer settings and toggle ADB off and on to make it available to other apps. Otherwise, adb will be occupied by the last app that used it.
Is it possible to automate this? Adding "disconnect" to the shell command didn't help.
Click to expand...
Click to collapse
Look for force stopping the application through adb commands.
I have managed to make the app start also after boot via Taskers app action. But the script is only executed after manually pressing the "test Script" button.
What exact intent action is executed by pressing the "Test Script" button? From the xml file I can only see "com.asfmapps.firetv_adbonboot.MainActivity".
I have also tried to send android.intent.action.BOOT_COMPLETED to your app to make it think it just started up but that also does not make your app to execute the script automatically.
What intent is your app listening for to execute the script? And ho do I issue it via shell or tasker?
Hi,
I'm trying to echo to sys/class/display/mode so I can change the resolution on boot.
When I test the script it shows 'permission denied'. It's an android box so it won't work?

Is it possible to connect to scrcpy through ethernet connection only without: rooting the phone, using wifi or having a usb connection to pc

Hello,
I got the following phone:
Moto G Pure | 2021 | 2-Day battery | Unlocked | Made for US by Motorola | 3/32GB | 13MP Camera | Deep Indigo
https://www.amazon.com/gp/product/B09BTB5MKT/
The phone charger port is usb c. It has an Android 11 installed.
Assumptions:
-I got a 2-1 dongle that allows to have an ethernet connection and charger at the same time.
-Phone is not rooted.
-Wifi is disabled (since I'm using ethernet) so assume no adb over wifi setting can be used.
-Phone charger is not connected to the pc usb so assume no adb over usb setting can be used.
How can I enable adb over ethernet so I could launch scrcpy on the same local network to access the phone screen/sending adb commands through command line as needed?
I found a similar post about this from 2018 on xda: https://forum.xda-developers.com/t/scrcpy-connection-help.3791716/
OP ended up ending writing the following update:
EDIT - problem solved: adb over ethernet instead of usb or wifi.
connected my android (galaxy view) to my network (ethernet) using the otg usb port and now, combined with the "adb over ethernet" app from the play store that i just discovered, the adb connection between my android and pc functions just as if they were connected by a usb cable, no more having to first connect the usb to get wifi to kick in, only to have to repeat this process again and again.
But when I tried to download "adb over ethernet" app, I noticed that it says that it requires root so I can't really use it?
A more recent comment on that post from 2022, someone said:
For others who find this in a search, you can get scrcpy to open up (and then kill the console to get it out of the way) on Android up to Android 11 using the "--tcpip=192.168.0.2:5555" option, but there's new capabilities in Android 12 now that eliminate totally the need for the initial USB connection.
In Android 12 you can also use scrcpy completely over Wi-Fi without first establishing the adb connection over USB like you need to do with Android 11.
There are new commands in the Android 12 Developer options to enable everything to be done over Wi-Fi which I've been using since May.
So it seems like the first option here (OP) is to root your phone and the second option (comment) is to upgrade your Android OS to version 12, which eliminates the need for a USB cable to enable adb debugging, but is there a way I could be able to connect to scrcpy on my Android 11 through the ethernet connection only without upgrading the Android version or rooting the phone?
When I currently try to run it this is the error I get (when only ethernet is connected, no wifi or usb connection to pc):
C:\scrcpy>scrcpy.exe
scrcpy 1.25 <https://github.com/Genymobile/scrcpy>
ERROR: Could not find any ADB device
ERROR: Server connection failed
Alternatively, can I enable adb over wifi in Android 11 so I could connect through scrpcy and without worrying that I might need to approve adb debugging in the small popup window that shows on the phone each time (or that shows periodically. In other words can that message be completely eliminated without rooting?). I do see under settings, developer options a setting called "Wireless debugging" (in addition to existing setting "USB debugging" which I had enabled when I used a direct USB connection the pc). So after enabling Wireless debugging, it asked me if I want to allow ADB debugging every time when my phone is connected to my local wifi network, I said yes. Now when I run scrcpy the following way using the local ip of my phone that was received by the wifi, I get the following error (IP was censored - this is only when wifi is connected, no usb connection to pc):
C:\scrcpy>scrcpy.exe --tcpip=192.168.X.X -b 2M -m 1024 --max-fps=15 --legacy-paste
scrcpy 1.25 <https://github.com/Genymobile/scrcpy>
INFO: Connecting to 192.168.X.X:5555...
cannot connect to 192.168.X.X:5555: No connection could be made because the target machine actively refused it. (10061)
ERROR: Could not connect to 192.168.X.X:5555
ERROR: Server connection failed
According to
Wireless debugging in Android 11
Android 11 developer preview has lots of new features to look but one of the coolest is Wireless debugging. It is a new method for…
levelup.gitconnected.com
“Requirements :
Device running with Android 11
SDK platform-tools with version ≥ 30.0.0.
Same Wi-Fi network for Android device and your PC
Wireless debugging
Android 11 supports deploying and debugging your app wirelessly from your workstation via Android Debug Bridge (adb). For example, you can deploy your debuggable app to multiple remote devices without physically connecting your device via USB and contending with common USB connection issues, such as driver installation.”
So this should be supported in Android 11, then why scrcpy fails to connect to my phone ip?
Thank you.
AFAIK the mobile device should be connected to a computer - either via USB or wirelessly in the same LAN.
This computer can be connected from a remote computer (via SSH), and SCRCPY can be used from this remote computer.
Device's Android must not be rooted to run SCRCPY.
jwoegerbauer said:
AFAIK the mobile device should be connected to a computer - either via USB or wirelessly in the same LAN.
This computer can be connected from a remote computer (via SSH), and SCRCPY can be used from this remote computer.
Device's Android must not be rooted to run SCRCPY.
Click to expand...
Click to collapse
SSH is a non graphic user interface, so how exactly can you run scrcpy from a remote computer you connected through SSH in some non gui terminal window?
In Windows 11 you execute SSH commands either via Windows CMD
{
"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"
}
or via Windows PowerShell
jwoegerbauer said:
AFAIK the mobile device should be connected to a computer - either via USB or wirelessly in the same LAN.
This computer can be connected from a remote computer (via SSH), and SCRCPY can be used from this remote computer.
Device's Android must not be rooted to run SCRCPY.
Click to expand...
Click to collapse
au contraire! good sir i checked the website of SCRPY and its supposed to work w/o root, i came across it in this silly phone-spoit nonsense , and i used it with success on my oculus 2 , with all due respect
mrstuffandthings said:
au contraire! good sir i checked the website of SCRPY and its supposed to work w/o root, i came across it in this silly phone-spoit nonsense , and i used it with success on my oculus 2 , with all due respect
Click to expand...
Click to collapse
though i think what your asking has more to do with right port and port forwarding rules aye?
1. obtain permission
2. set the rules on your router
3. "nmap it!" or wireshark (not recommended)
or i think something like twitch would same same
jwoegerbauer said:
In Windows 11 you execute SSH commands either via Windows CMD
View attachment 5920653
or via Windows PowerShell
View attachment 5920655
Click to expand...
Click to collapse
I understand what’s ssh and how to run it from cmd/powershell, what I don’t understand is how it’s related to scrcpy? What’s the context of saying ssh and scrcpy in the same sentence? Assuming you ssh from cmd/powershell into some remote machine, can you run scrcpy in that remote machine? And if so, will the scrcpy/phone color screen will show up in the cmd/powershell black screen? That’s what I don’t understand...
Look inside here - navigate to section
SSH tunnel​
scrcpy/tunnels.md at master · Genymobile/scrcpy
Display and control your Android device. Contribute to Genymobile/scrcpy development by creating an account on GitHub.
github.com
jwoegerbauer said:
Look inside here - navigate to section
SSH tunnel​
scrcpy/tunnels.md at master · Genymobile/scrcpy
Display and control your Android device. Contribute to Genymobile/scrcpy development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
So if I understand correctly, I could ssh from an external network machine into the internal network that has both the phone and ‘pc that I ssh to’, and then I will be able to run scrcpy remotely from my external network machine without the need to actually remote desktop into the machine to launch scrcpy that’s in the same network as the phone as long as I establish an SSH connection with that machine in that local network? Please correct me if I’m wrong, but it sounds very cool, it’s like some sort of VPN that allows you to access the local resources of that network using SSH in this case, thank you for pointing this out to me!
By the way, if I SSH from my iphone to that local machine network, is there an app or a way to launch scrcpy against that local network similar to how you would do it from the remote machine pc but just from my iphone? I have iPhone 12 Pro Max with iOS 14.4.1 jailbroken and got newterm3 terminal that allows me to ssh to remote computers.

Categories

Resources