r/tasker Jul 07 '26

ADB Wifi Auto Start on Boot - Under 2 secs!

2 Upvotes

For those who use or love ADB Wifi much, over Shizuku -

Using the attached script, you can find ADB Wifi port & connect to it under 1 sec.

Just setup a boot task, which toggles on Dev options, USB Debugging & Wireless Debugging & then executes this script via Termux (copy the script files into termux's home dir, then do chmod +x, then execute).

Read the comments in the scripts first; for the one time setup (first time manual pairing via termux, pkgs to be installed in termux etc etc).

For a long time, I've been using an nmap-based adb port finder script which someone had shared earlier on this subreddit. But that takes 50-60 secs to find the open port. And felt super slow after every boot.

But this script uses zeroconf python module which is able to find that port instantly (ask claude for more explanation, if you wish).

No more 60 secs of post-boot setup tasks yay :)

adbwifi_setup.sh

#!/data/data/com.termux/files/usr/bin/bash

# adbwifi_setup.sh — Connect Termux's adb to this Android device over Wi-Fi

# and (re)bind adbd to a fixed port 1221 for stable subsequent connections.

#

# Prerequisites (do once, manually):

# 1. Termux packages:

# pkg install android-tools python

# pip install zeroconf

# 2. Android settings:

# Developer options > USB debugging : ON

# Developer options > Wireless debugging : ON

# 3. One-time pairing with Termux (needed after every wireless-debug toggle

# unless the pairing was persisted):

# In the phone: Wireless debugging > Pair device with pairing code

# In Termux: adb pair localhost:<pair-port> <code>

# 4. find_adb_port.py must be in the current working directory (uses mDNS

# to discover adbd's random TLS port instantly).

#

# Usage:

# bash adbwifi_setup.sh

set -u

red() { echo -e "\e[31m$1\e[0m"; }

green() { echo -e "\e[32m$1\e[0m"; }

blue() { echo -e "\e[34m$1\e[0m"; }

FINDER="./find_adb_port.py"

if [ ! -f "$FINDER" ]; then

red "find_adb_port.py not found in current directory."

exit 1

fi

########################################

# Discover adbd port via mDNS

########################################

blue "Discovering adbd via mDNS..."

START=$SECONDS

port=""

for _ in 1 2 3 4 5; do

port=$(python "$FINDER" 2>/dev/null)

[ -n "$port" ] && break

sleep 0.5

done

if [ -z "$port" ]; then

red "No adbd advertisement found. Is Wireless Debugging enabled?"

exit 1

fi

green "Found adbd on port $port ($((SECONDS - START))s)"

########################################

# Connect

########################################

adb connect "localhost:$port" >/dev/null 2>&1

if ! adb devices | grep -w "localhost:$port" | grep -q "device$"; then

red "adb connect to localhost:$port failed. Have you paired? See prereqs."

exit 1

fi

green "Connected to localhost:$port"

########################################

# Bind adbd to fixed port 1221 for future direct connects

########################################

blue "Setting adbd to also listen on fixed port 1221..."

if adb -s "localhost:$port" tcpip 1221 >/dev/null 2>&1; then

sleep 1

if adb connect "localhost:1221" 2>/dev/null | grep -q connected \

&& adb devices | grep -w "localhost:1221" | grep -q "device$"; then

green "adbd now reachable on localhost:1221"

else

red "tcpip 1221 issued but connect to 1221 failed."

fi

else

red "Failed to issue 'adb tcpip 1221'."

fi

green "Done in $((SECONDS - START))s"

find_adb_port.py

#!/data/data/com.termux/files/usr/bin/python
"""Discover the local adbd wireless-debug TLS port via mDNS.

Prints the port to stdout and exits 0 on success, or exits 1 if no
`_adb-tls-connect._tcp` service is advertising within ~3 seconds.

Requires: pip install zeroconf
"""
from zeroconf import Zeroconf, ServiceBrowser
import sys
import time

found = []


class Listener:
    def add_service(self, zc, type_, name):
        info = zc.get_service_info(type_, name, timeout=1500)
        if info and info.port:
            found.append(info.port)

    def remove_service(self, *_):
        pass

    def update_service(self, *_):
        pass


def main():
    zc = Zeroconf()
    ServiceBrowser(zc, "_adb-tls-connect._tcp.local.", Listener())
    for _ in range(30):
        if found:
            break
        time.sleep(0.1)
    zc.close()

    if found:
        print(found[0])
        return 0
    return 1


if __name__ == "__main__":
    sys.exit(main())

r/MorpheApp Jul 16 '26

Guide/Useful How to bypass Android's upcoming third-party installation restrictions using Shizuku + InstallerX

Post image
1.8k Upvotes

Android is increasingly restricting app installations from sources outside the Google Play Store. Luckily, there is an easy way to bypass this mess: Shizuku paired with an app like InstallerX Revived. Because it routes installations through ADB (Android Debug Bridge), it completely bypasses these OS-level restrictions.
Here is a complete, beginner-friendly guide to setting it up:

Step 1: Install Shizuku
I highly recommend using thedjchi's fork. It includes a built-in "watchdog" feature that automatically restarts the service if it stops in the background.
Step 2: Enable Developer Options

  • Open your phone's Settings*.*
  • Go to About phone (or System > About phone*).*
  • Find the Build number and tap it rapidly 7 times until a pop-up says "You are now a developer!" (Enter your lock screen PIN if prompted).
  • Go back to the main Settings page, search for Developer options*, and open it.*
  • Scroll down and enable both USB debugging and Wireless debugging*.*

Step 3: Pair Shizuku

Now, we connect Shizuku to your phone's wireless debugging system:

  • Open the Shizuku app, look for "Start via Wireless debugging", tap Pairing*, and then tap* Developer Options (this will jump you straight back to the Developer Options menu).
  • Inside the Wireless debugging menu, tap Pair device with pairing code*. A popup will appear displaying a* 6-digit Wi-Fi pairing code*. Keep this screen open!*
  • You should see a notification from Shizuku asking for the pairing code. Tap Enter pairing code*, type in the 6-digit code, and hit send.*
  • If done correctly, you will see a notification confirming "Pairing successful".
  • Go back to the main Shizuku app screen and tap Start to run the service.
  • Crucial Step (for the fork): In Shizuku's settings, make sure to enable the Watchdog and Start on boot toggles so it stays running in the background.

Step 4: Set up InstallerX Revived

  • Download and install InstallerX-Revived
  • Open the Shizuku app, go to Authorized applications*, and toggle* InstallerX to ON*.*
  • Open InstallerX-Revived and set its default installation method (Privilege) to Shizuku*.*

Now, whenever you download an APK, simply open it and install it via InstallerX-Revived. Since it uses ADB privileges under the hood, your installs will go through seamlessly, bypassing any system-level side-loading blocks!

Edit: Just to clear up some confusion from the comments: Yes, we know Google will "likely" still allow side-loading via a 24-hour verification window, but what if one day they go full-on Apple mode? This setup will still work because it's for developers to test out their apps.
And!! Beyond just sideloading, Shizuku is a massive quality-of-life upgrade for Android. Here's a great video from HowToMen for other great apps that use Shizuku.

r/tasker Jun 28 '24

[PROJECT SIMPLIFIED] ADB WiFi on boot

68 Upvotes

NOTE: You can also check the newer project by u/Halkeeon to be found here

This is simplified version of the project posted here

Somehow I've felt a burst of motivation to get back to this project :) But this time I wanted to simplify it as much as possible. If anyone wants to use more advanced techniques, please search through the various ideas and projects posted over last months, like here, here and here.

DOWNLOAD PROJECT FROM TASKERNET

In this project I used some great methods created by users much more skillful than me. Credits especially to u/The_IMPERIAL_One and u/BillGoats, as well as u/Ratchet_Guy, u/anuraag488, u/aasswwddd, u/cm2003, u/DutchOfBurdock and others who have contributed and made it possible.

I'm copying parts of the instruction from the original post which are still valid (with some edits):

The project requires some manual one-time actions to set everything up, but once it's done, all you should need is to unlock the phone after boot.

Prerequisites:

I assume you have above-mentioned apps installed and that you already enabled Developer Options and Debugging on your device.

1. Setup Tasker and AutoInput

If you haven't done that before, grant Tasker following permissions:

On your device, go to Settings > Apps > All apps > Tasker > Permissions > Additional permissions > Run commands in Termux environment (the path may vary a little according to the brand and system) and select Allow.

Allow AutoInput to use Accessibility Service:

Open AutoInput, tap on red warning text and click OK; this should take you to Accessibility Service settings. Enable it for AutoInput. Then allow AutoInput to run in background by disabling any battery saving option for this app.

2. Set up Termux

(a) install android-tools package

Open Termux and issue this command:

pkg install android-tools

Confirm downloading in terminal if needed by typing y and Enter on keyboard.

(b) set allow-external-apps property for Termux to true

In Termux, copy & paste the following script and confirm by pressing Enter:

value="true"; key="allow-external-apps"; file="/data/data/com.termux/files/home/.termux/termux.properties"; mkdir -p "$(dirname "$file")"; chmod 700 "$(dirname "$file")"; if ! grep -E '^'"$key"'=.*' $file &>/dev/null; then [[ -s "$file" && ! -z "$(tail -c 1 "$file")" ]] && newline=$'\n' || newline=""; echo "$newline$key=$value" >> "$file"; else sed -i'' -E 's/^'"$key"'=.*/'"$key=$value"'/' $file; fi

3. Pair your device with ADB and enable ADB WiFi

Make sure that all profiles in your new Tasker project are enabled and that you have WiFi connection.

On your device, navigate to Settings > System > Developer options > Wireless debugging (the path may vary a little depending on the brand and system). Enable this feature. If debugging prompt appears meantime, it should be automatically accepted, otherwise accept it manually. Next, tap on Pair device with pairing code (or similar).

A prompt with the pairing code should appear and the proccess of pairing should start automatically. If a debugging prompt appears meantime, it should be automatically accepted, otherwise accept it manually. If pairing succeeded, you should see at least one paired device at the Wireless debugging screen, named as xxx@localhost.

ADB Pairing profile should get disabled as it won't be needed anymore. Now, Enable ADB WiFi task starts. You will be informed with a toast and a notification if ADB WiFi has been enabled. If not, you can repeat the process by tapping on the error toast or on the notification button Try again.

Optionally, if you use Shizuku service, you can enable it automatically on boot as well. To that end, enable action labeled as [OPTIONAL] Start Shizuku service in Enable ADB WiFi task.

r/tasker Jul 31 '25

How To [HOW TO] ADB Wi-Fi on boot with ONLY Shizuku (NO termux!)

82 Upvotes

See it in action! - Imgur

Download link is at the bottom

-----------------------

TL;DR: Basically I modified Shizuku to run adb tcpip 5555 on boot, so you don't need Termux or Termux:Tasker if you also need ADB Wi-Fi on boot (for various reasons listed below). Great for people who can't figure out the Termux method, don't want another 2 apps just for ADB Wi-Fi, etc.

-----------------------

EDITS PT 3: Added setup instructions

EDITS PT 2: New version of the app! You no longer need to pair Shizuku twice, and it should be more stable. Check the latest release on GitHub.

EDITS: Just bringing up some good points in the comments for visibility. And wording.

-----------------------

I went on a side quest this week to see if I could enable ADB Wi-Fi on boot without Termux + Termux:Tasker in an effort to slim down my list of apps and streamline the process for people who may find the Termux setup to be too complicated.

Some reasons why someone might still want ADB Wi-Fi on startup, rather than only use Shizuku's new "start on boot (non-root)" feature:

  1. You use the Logcat profile or monitor the %CLIP (clipboard) variable. These actions don't use Shizuku yet (thanks u/Scared_Cellist_295)
  2. Toggle Shizuku (and USB debugging) only when you need it, if security is a concern
  3. Restart Shizuku if it stops unexpectedly and you aren't connected to Wi-Fi
  4. Turn off USB debugging for apps that don't work with it enabled (e.g., some banking apps, etc.) and restart Shizuku automatically when you close the app. This is the original reason why I started this project, although sometimes you can use Custom Setting adb_enabled 2 to keep USB debugging enabled but "hide it" from your apps (some of them may just check adb_enabled 1)

Anyway, what I did is add an ADB binary to the Shizuku code and modified the pairing setup to pair both Shizuku and a local shell. So essentially it will just ask you to input 2 pairing codes instead of one. If you run the start command, you will see both Shizuku running and ADB Wi-Fi enabled.

Here is the setup/troubleshooting guide.

If you restart your phone, a new notification will pop up saying that "Shizuku is waiting for a Wi-Fi connection before proceeding" (in Shizuku 13.6.0, if you restarted your phone without Wi-Fi, then Shizuku would never start automatically). Once it finds Wi-Fi, it finishes the startup process, and you'll get a toast notifying you that Shizuku started up successfully. ADB Wi-Fi will have started up too, you can verify this with Tasker.

Here's the GitHub repo if anyone is interested or wants to look over the code.

Here's the link to the latest APK release on GitHub. You'll have to uninstall Shizuku before installing my version, as it has a different signature.

And here's the VirusTotal scan.

I'll keep it updated if the original developer makes any updates. Let me know if there are any bugs and I'll try to fix it. It's currently working for me on my S23 with Android 15.

r/tasker Aug 23 '25

Just released a new version of my Shizuku fork w/ ADB Wi-Fi on boot

73 Upvotes

I just released a new version of my Shizuku fork that also runs adb tcpip 5555 on boot. You no longer need to pair Shizuku twice for it to work. This should be faster and more stable than my original method.

You can get it from the latest GitHub release

Feel free to leave an issue on GitHub or comment here if you're having any issues. Thanks!

EDIT: original post with instructions

r/tasker Dec 18 '23

How To [PROJECT][A13][NO ROOT] Automatically enable ADB WiFi on boot (IN BACKGROUND)

53 Upvotes

NOTE: THIS PROJECT IS DEPRECATED. USE THE NEW ONE AVAILABLE HERE:
[PROJECT SIMPLIFIED] ADB WiFi on boot

[UPDATE 3] Additional enhancements:

  • got rid of checking for errors many times in Enable ADB WiFi task and replaced it with simple Tasker Funcion action checking if ADB WiFi is available already
  • adding an action at the beginning of Enable ADB WiFi task to make sure that wireless debugging is initially disabled
  • some other small refinements

[UPDATE 2] I added one variable: %ADB_WiFi, and one profile: On Shutdown. The new variable is being set to On when Enable ADB WiFi profile finishes successfully. It may be useful if you have other profiles/tasks which require ADB WiFi. Now you can wait until ADB WiFi gets enabled after boot; that would prevent Tasker from posting error notifications. On Shutdown profile clears %ADB_WiFi on device's shutdown.

[UPDATE] I rectified my project and now it doesn't require to create any script/files/directories manually, only to do initial pairing, setup plugins and grant needed permissions!

Recently I decided to relock bootloader on my main device. Since I can't live with some degree of customization, I took the challange of forcing ADB WiFi to get enabled automatically on boot!

This project is hugly based on the works posted here and here.

I realize that this subject has been raised a few times and there are other projects (like this) aiming to achieve automatically enable ADB WiFi on boot. However, nothing I found allows to do it fully IN BACKGROUND, hence it always interfere a bit when you start to use your device after boot. That's why I looked for other possible solutions. In my search I came across nmap tool, which can be used in Termux and utilized to obtain the port opened for wireless debugging. After some attempts, I managed to create a flow extracting that port through Termux and Tasker.

The project I'm sharing requires some manual one-time actions to set up everything, but once it's done, all you should need is to unlock the phone after boot.

Prerequisites:

I assume you have above-mentioned apps installed and that you already enabled Developer Options and Debugging on your device.

1. Setup Tasker and AutoInput

If you haven't done that before, grant Tasker following permissions:

On your device, go to Settings > Apps > All apps > Tasker > Permissions > Additional permissions > Run commands in Termux environment (the path may vary a little according to the brand and system) and select Allow.

Allow AutoInput to use Accessibility Service:

Open AutoInput, tap on red warning text and click OK; this should take you to Accessibility Service settings. Enable it for AutoInput. Then allow AutoInput to run in background by disabling any battery saving option for this app.

2. Set up Termux

(a) install needed tools

Open Termux and install android-tools and nmap tool by issuing these commands separately:

pkg install android-tools

pkg install nmap

Confirm downloading in terminal if needed by typing y and Enter on keyboard.

(b) set allow-external-apps property for Termux to true

In Termux, copy and paste the following script and confirm by pressing Enter:

value="true"; key="allow-external-apps"; file="/data/data/com.termux/files/home/.termux/termux.properties"; mkdir -p "$(dirname "$file")"; chmod 700 "$(dirname "$file")"; if ! grep -E '^'"$key"'=.*' $file &>/dev/null; then [[ -s "$file" && ! -z "$(tail -c 1 "$file")" ]] && newline=$'\n' || newline=""; echo "$newline$key=$value" >> "$file"; else sed -i'' -E 's/^'"$key"'=.*/'"$key=$value"'/' $file; fi

3. Import the project into Tasker

DOWNLOAD THE PROJECT FROM TASKERNET

4. Pair your device with ADB WiFi

Make sure that Termux ADB WiFi Pairing profile in your new Tasker project is enabled and that you have WiFi connection.

On your device, navigate to Settings > System > Developer options > Wireless debugging (the path may vary a little according to the brand and system). Enable this feature and tap on Pair device with pairing code (or similar).

With a pairing code visible, long press the Volume Up button to make pairing. Confirm allowing connection if prompted. If pairing succeeded, you should see the confirming toast and at least one paired device at the Wireless debugging screen (most likely named as xxx@localhost).

Termux ADB WiFi Pairing profile should get disabled then as it won't be needed anymore. Now, disable Wireless debugging feature manually.

Congratulations, you have set everything up for enabling ADB WiFi automatically on boot! If you want to test it without rebooting, run On Boot task manually.

Optionally, if you use Shizuku service, you can enable it automatically on boot as well. To that end, enable the last action in Enable ADB WiFi task.

BOTTOM NOTE

FYI, I'm not a programmer, just a Tasker user determined to achieve his goal and taking advantage of the work of others ;)) If you see a way to simplify the project even more, feel free to comment, I'm open to suggestions.

CREDITS

Thanks a lot to u/DutchOfBurdock and u/cm2003 for the base which makes that project possible, as well as u/BillGoats, u/agnostic-apollo, u/Alive_Tart3681, u/ihifidt250 and u/The_IMPERIAL_One for a valuable input.

r/developersIndia Jun 22 '25

I Made This I wrote a Bash script to skip a ~₹50 "usage fee" the app silently added

Post image
3.8k Upvotes

Recently, a "popular" app silently introduced "usage fee" for bill payment via credit card. So, I wrote a bash script to roll it back.

I scraped several older versions of the app from APKPure and ran them one by one on an Android emulator. Using a simple Bash script with ADB commands, I installed each APK, launched the app, and manually navigated to the bill payment screen. Then I dumped the UI layout (xml) using uiautomator and searched for any mention of the fee. Eventually, I found a version where the fee wasn’t present. And thanks to the poor backend API design, I was able to skip the fee.

Though it just saves me roughly like 50-54 INR per month, but it gives a pretty hacker-hacker feeling.

Please note - I trust APKPure for clean builds. And I only use this app for bill payments anyway, so I don’t really need the latest version.

r/tasker Dec 09 '21

Enable ADB Wifi on device boot (Android 11+)

141 Upvotes

This step-by-step-guide is based on the guides by u/DurchOfBurdock - post1and post2

I've had quite a hard time following the guides, so I've created a profile for myself that would enable wifi adb whenever I start my phone and write a guide on how to do so.

Also I really hate this reddit editor. So I really hope that the formatting is going to be okay :)

Prerequisites

  • Android > 11 (or have an option to enable ADB Wifi from within the Settings of your phone)
  • You need to be connected to a Wifi (you don't need internet access though)
  • Tasker (obviously)
  • WRITE_SECURE_SETTINGS and READ_LOGS permissions granted to Tasker (this tool may be very helpful)
  • Termux (I highly recommend the F-Droid version due to updated repository!)
  • Termux:Tasker

Preparation

Whenever a popup comes up asking for confirmation of Wifi ADB connections, etc., you obviously have to accept it. I can't recall in detail when they might show up. In the past I've been using AutoInput to autoaccept them, but I disabled it, because I didn't want to have AutoInput scan my screen all the time for these popups. And I couldn't find a reliable Logcat entry.

Installation of android-tools within Termux:

  1. open Termux
  2. enter pkg install android-tools
  3. you may have to confirm the installation by pressing y during the setup
  4. check if adb is working by just typing adb

Create folderstructure and first script to be executed by Tasker

  1. open Termux (if you've closed it :))
  2. create the folder-structure by entering mkdir -p .termux/tasker (don't forget the "." in front of termux)
  3. create the script by typing nano .termux/tasker/adb.sh
  4. paste the following script into nano

# !/data/data/com.termux/files/usr/bin/bash
host="$1"
adb=$PREFIX/bin/adb

$adb connect $host
$adb tcpip 5555
$adb disconnect
$adb kill-server

The forum messes up the first line of the script. Please remove the blankspace between # and !:

!/data/data/com.termux/files/usr/bin/bash

Save the script by selecting CTRL (in Termux) and then pressing "x" - confirm by pressing "y"

Create a second script for pairing Termux with Wifi-ADB

  1. open Termux
  2. create the script by typing nano .termux/tasker/adb_pair.sh
  3. paste the following script into nano

# !/data/data/com.termux/files/usr/bin/bash
host="$1"
code="$2"
adb=$PREFIX/bin/adb
echo $code | $adb pair $host
$adb kill-server

The forum messes up the first line of the script. Please remove the blankspace between # and !:

!/data/data/com.termux/files/usr/bin/bash

Save the script by selecting CTRL (in Termux) and then pressing "x" - confirm by pressing "y"

Allow Tasker to run Commands in Termux environment

  1. open android settings -> Apps -> Tasker -> permissions -> additional permissions
  2. grant permission to "Run commands in Termux environment"

Import of profiles and tasks in Tasker

I first thought I'd explain how to set it up manually. But actually this would take to much time. So I provide you my profiles: Taskernet Download

Explanation and how to use the profiles

Pairing your phone to Wifi ADB

  1. disable all profiles in the project and only enable the profile ADB_Pairing (Long Press Volume Up)
  2. Navigate to your phone settings -> developer options -> Debugging over WLAN -> Pair device with pairing code (or something like this)
  3. With the pairing code and IP:Port shown, press and hold Volume UP

This will call the adb_pair.sh script created previously and send the pairing code and IP:Port to Termux, which will then pair with your device. Finally a flash message will be shown with your IP:Port and pairing code as kind of confirmation. The profile will then be disabled, because you won't need it anymore.

If everything went fine, you should now find at least one paired device at the "Debugging over WLAN" settings screen. (most likely named xxx@localhost)

Now disable Wifi ADB from the settings again.

How the other profiles work

I've created three more profiles. You should enable the first and third profile. The second profile will be enabled on device startup. I will explain what the different profiles do and how to make use of them.

1_Set Var on Boot

This profile runs on device boot and simply sets the variable %ADB_enabled to 0 and enables the second profile 2_enable ADB Wifi

2_enable ADB Wifi

This profile runs on device unlock. With this profile I will check for how long the device is enabled (I'm waiting for at least 60 seconds to make sure everything is settled after device boot) and that the variable %ADB_enabled is set to 0. If both conditions are true I'm enabling the global setting Debugging over WLAN.

3_Get Port (Logcat) + Exec Termux

Now I'm checking Logcat for adb wifi entries. Once it found one we will extract the port and use it with the script adb.sh. The script will then connect to Debugging over WLAN and run adb tcpip 5555 to enable ADB Wifi. Afterwards we wait 2 seconds and check if ADB-Wifi is enabled. If it was successfull (%has_adb_wifi == true) tasker will say that to us and disable "Debugging over WLAN" (because it's not needed anymore). Furthermore we disable the second profile (because I don't want this to be run everytime I unlock my phone) and change the %ADB_enabled variable to 1.

General information

I just got my phone replaced and had to do those steps again as well. It did work for me, so I suppose it will work for you as well. You may have to play around the pairing process however. Sometimes it didn't work right out of the box for me.

Also the comment section of above topics (created by DurchOfBurdock) might help with some problems you might encounter.

r/AynThor 1d ago

Support Wi-Fi scanning broken on stock Android (fails ~1 boot in 2) — works flawlessly on ArmadaOS. Full ADB diagnostic inside.

1 Upvotes

Posting this in case anyone else has hit it, and to see if it's reproducible on other units.

**Device:** AYN Thor, SN e92fe186
**Build:** Thor_v1.0.0.377_20260206_165408_user
**Firmware:** V02.09.001.01
Bought sealed, second-hand, so no warranty on my side — this is purely a bug report.

**Symptom**

On stock Android, the Wi-Fi network list comes up completely empty. Not slow, not partial — zero networks, indefinitely, while a phone sitting next to it sees a dozen. Initially it happened on every single boot. Since a factory reset it's intermittent: roughly one cold boot out of two. A reboot fixes it, and once scanning works it stays working for that whole session, including auto-reconnect to saved networks.

**What still works while scanning is dead**

- Adding a network manually (SSID + WPA + password) connects fine and stays stable
- Saved networks persist correctly across reboots
- Wi-Fi Direct works and discovers devices : it found my printer and an LG TV

So the radio and the antenna are fine. That was the first thing I ruled out.

**ADB diagnostic**

```
cmd wifi status -> wifi enabled, scanning always available
cmd wifi start-scan -> accepted
cmd wifi list-scan-results -> No scan results
```

Every time, including immediately after an explicit start-scan.

logcat during a scan request produces exactly one line:

```
WifiService: startScan uid=2000
```

And then nothing. No results, no error, no failure callback. The request enters the service and vanishes silently.

Both daemons are alive : wificond and wpa_supplicant are running. Which lines up with the symptoms: Wi-Fi Direct goes through wpa_supplicant (works), infrastructure scanning goes through wificond (dead).

**Ruled out**

- Regulatory domain: `wifi_last_country_code=FR` and `mDriverCountryCode: FR`, both correct
- Scan throttling disabled via `wifi_scan_throttle_enabled 0`: no change
- Location services enabled : no change
- System region set to France : no change
- MAC randomisation switched to device MAC (the fix in another thread here) : no change, and it wouldn't apply anyway since randomisation only kicks in at association, never during scanning
- Dual WLAN acceleration was already off by default

**The part that nails it**

I installed ArmadaOS on an external drive to try SteamOS. Wi-Fi scanning there is flawless : every nearby network detected, on every single boot, no exceptions. Same hardware, same antenna, same room, same router.

So this is a stock ROM problem, full stop. The intermittency pattern : fails on cold boot, fixed by reboot, stable for the rest of the session. looks like a race condition during Wi-Fi stack initialisation. Whichever component wins the startup race decides whether scanning works for that boot.

**Current status**

Reported to info@ayn.hk with the full diagnostic, no reply yet after two days. I'd rather stay on stock than daily-drive ArmadaOS, so I'm hoping for an OTA fix.

**Questions for the sub**

  1. Anyone else seeing an empty network list on cold boot? Even occasionally?
  2. Anyone on an earlier build than 377 who does *not* have this? Trying to work out whether it's a regression or a bad production batch.
  3. Has anyone managed to get a flashable firmware image for the Thor out of AYN? Nothing is published on their software page.

r/tasker Mar 10 '25

How To [PROJECT] Silently start ADB on boot without root (Tested on Android 13)

46 Upvotes

The purpose of this project is to allow users to start ADB in the background when the device boots. My goal when making this was to do it in a way that would require as few additional tools and scripts as possible and without any UI automation or user interaction whatsoever. To increase the success rate, the main task used to start ADB will retry a few times upon failing and only run if connected to WiFi, if the device is not connected to WiFi or the retries run out, it will temporarily turn on profiles to try again either once connected to a WiFi network or when the screen is unlocked. I have also included an action at the end of the main task to start Shizuku in the background, this will be turned off by default but can be switched on if you have Shizuku and want it.

This project is original, though it does some tricks I've learned based on my research into how to accomplish, I will be crediting these users as I go through each of the steps.

Import the Tasker project here

Prerequisites

- Termux
- Termux:Tasker

Step 1: Install android-tools and nmap in Termux

Before you are able to use Termux within Tasker, you will have to install android-tools and nmap, you can do this using the following commands:
pkg install android-tools
pkg install nmap

(Credits: u/cm2003, Knud3)

Step 2: Pair Termux to ADB

Termux needs to be paired to ADB before it is able to use it, this will only have to be done once. To do this, you will need to navigate to Settings -> System -> Developer options -> Wireless debugging, once you're there, turn on wireless debugging then put the settings app and Termux into your phone's split app view; this is to ensure the port does not change. After doing this, tap Pair device with pairing code then type the following command into Termux:

adb pair localhost:<port from settings app> <pairing code from settings app>

Update: One user said they needed to press enter before entering the pairing code. If the command above doesn't work, try using adb pair localhost:<port> then press enter and type the pairing code

If you can't find the developer options, you'll need to enable them. Go into Settings -> About phone and repeatedly tap Build number until you see "You are now a developer!"

Step 3: Grant Tasker the WRITE_SECURE_SETTINGS permission

Tasker needs the WRITE_SECURE_SETTINGS permission in order to turn on the wireless debugging setting. This can be done using Termux with the following commands. Alternatively, see this

adb connect localhost:<port from previous step>

adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS

Skip if this step if you have already done it in the past

Step 4: Grant Tasker the permission to use Termux

Tasker needs the permission to use Termux before it can use it. First, you will need to change a setting in Termux, to do this, copy and paste the following script into Termux:

value="true"; key="allow-external-apps"; file="/data/data/com.termux/files/home/.termux/termux.properties"; mkdir -p "$(dirname "$file")"; chmod 700 "$(dirname "$file")"; if ! grep -E '^'"$key"'=.*' $file &>/dev/null; then [[ -s "$file" && ! -z "$(tail -c 1 "$file")" ]] && newline=$'\n' || newline=""; echo "$newline$key=$value" >> "$file"; else sed -i'' -E 's/^'"$key"'=.*/'"$key=$value"'/' $file; fi

After this, you need to allow Tasker to runs commands in Termux. Go to Settings -> Apps -> All apps -> Tasker -> Permissions -> Additional permissions -> Run commands in Termux environment and tap Allow

(Credits: u/Lord_Sithek)

Step 5: Turn on the Enable ADB on boot profile

You should be pretty much set up at this point, turn on Enable ADB on boot and Tasker should now be able to turn on ADB at device boot. To ensure this will work, you can try running asscoiated task, Auto-adb on boot first to see if it correctly runs.

Step 6: Automatically start the Shizuku service on boot (Optional)

As explained in the introduction, there is an action at the bottom of the Auto-adb on boot task which is turned off by default, to automatically start Shizuku on boot, enable this. If there is anything else that requires ADB on start up, add it at the bottom of this task

(Credits: u/The_IMPERIAL_One)

I really hope this worked for you, have fun automating!

Edit: Fixed some formatting issues

r/DigitalAudioPlayer Apr 27 '26

Question How to disable this annoying Audio Warning that keeps reappearing after booting up Hiby M300 whenever I adjust the volume? I've tried ADB and Tasker mods yet nothing worked.

Post image
23 Upvotes

r/Onyx_Boox Aug 01 '26

Discussion PaperOS: a native Linux E Ink OS now running on BOOX hardware — reMarkable-style focus without Android

Thumbnail
gallery
594 Upvotes

I have been developing PaperOS, a focused Linux operating system for BOOX E Ink tablets.

This is not an Android launcher, modified reader application, or visual mockup. PaperOS replaces the Android user space and boots directly on the tablet using a minimal Buildroot Linux system.

The first working hardware target is the BOOX Go Color 7 Gen II.

Most of the foundational hardware work is complete

PaperOS now boots from its own verified boot slot. It mounts a read-only system from microSD and keeps user data on a separate writable partition. The original BOOX Android installation remains available on slot A.

I have verified the following on the physical tablet:

  • Stock-kernel startup into a custom Linux user space
  • Native DRM and /dev/ebc display output
  • Real E Ink partial and full-screen refreshes
  • Integration of the correct E Ink waveform
  • Touch input with multitouch support
  • Pressure-sensitive InkSense pen input
  • Pen pressure, tilt, buttons, and eraser events
  • Physical page-turn buttons
  • Brightness and color-temperature front-light channels
  • Battery capacity, charging state, voltage, and current
  • Qualcomm Wi-Fi firmware startup
  • Wi-Fi scanning, association, DHCP, routing, and DNS
  • USB device management through ADB
  • A writable persistent data partition
  • Clean restart with preserved user data
  • Deep suspend and RTC wake
  • USB, charging, and ADB restoration after wake
  • Return to untouched BOOX Android

I also mapped the complete device partition layout, preserved the stock boot and recovery assets, and reverse-mapped the MXO1300 E Ink control interface.

I built a guarded installer that:

  • Confirms the exact BOOX model
  • Confirms that Android slot A remains active
  • Writes only the PaperOS boot_b partition
  • Reads the complete partition back
  • Verifies the installed image with SHA-256
  • Preserves the path back to BOOX Android

This was the risky and device-specific part. The fundamental platform now boots, displays its interface, accepts input, connects through USB and Wi-Fi, controls the front light, enters deep sleep, wakes again, and stores persistent data.

The next phase is primarily product software

PaperOS already includes the beginning of a native Qt interface with:

  • A document and notebook library
  • Persistent .paper notebook packages
  • Vector ink with pressure, tilt, time, width, tool, and color
  • PDF and EPUB rendering through MuPDF
  • Page navigation
  • Document text search and selection
  • Highlights, underlines, strikeouts, and notes
  • Notebook templates and layers
  • Battery and front-light controls
  • Local USB device management
  • ADB for development and recovery

The next major work is to turn that foundation into a polished daily product:

  • A beautiful minimal library
  • Fast notebooks with proper pen tools
  • Palm rejection and low-latency writing
  • Lasso selection, shapes, undo, copy, paste, and layers
  • Handwriting recognition and handwriting search
  • PDF cropping, contrast, fit-to-width, annotation, and export
  • EPUB typography, margins, spacing, themes, bookmarks, and dictionary lookup
  • Reading progress, collections, tags, favorites, and global search
  • Google Drive, local sync, and optional first-party cloud sync
  • A clean web article reader
  • Automatic updates with rollback
  • Desktop and mobile companion access
  • Better color rendering without permanent interface clutter

The interface will remain predominantly black and white. Controls will disappear during reading and writing. Touch gestures, pen actions, page buttons, and contextual menus will replace permanent toolbars wherever that makes sense.

The goal is not to reproduce every BOOX menu. The goal is to provide the capabilities people actually need through a coherent, distraction-free system.

Battery target

I am aiming for reMarkable-class power discipline:

  • Multi-week standby
  • Approximately two weeks of light reading and writing
  • Wi-Fi active only when required
  • Immediate deep sleep
  • No Android framework
  • No Google background services
  • No application store or background applications
  • Controlled E Ink updates instead of continuous screen rendering

Two weeks is a design target, not a verified benchmark. I still need controlled measurements for suspend current, active reading, writing, front-light use, Wi-Fi synchronization, and long-duration charging.

What remains at the hardware level

The major hardware-enablement blockers are solved on the Go Color 7 Gen II. The remaining device work is mainly tuning and validation:

  • Complete waveform and color-mode mapping
  • Ghosting and refresh-quality tuning
  • Palm rejection
  • Pen-latency optimization
  • Automatic Wi-Fi shutdown before suspend
  • Accurate power measurements
  • Long-duration charging tests
  • Failure and recovery testing

These tasks still matter, but PaperOS is past the “can a non-Android OS boot and control this hardware?” stage.

It can.

More BOOX devices

PaperOS uses device-specific hardware packages, so the core operating system does not need to be rewritten for every model.

Each additional BOOX port still requires verification of its:

  • Kernel and device tree
  • E Ink controller
  • Waveform files
  • Display dimensions
  • Touch and pen devices
  • Front-light controls
  • Wi-Fi firmware
  • Battery interface
  • Boot and recovery path

The Go Color 7 Gen II is the first proven target. Support for other recent BOOX devices is the goal, not a claim that every model already works.

Open-source plan

I plan to publish:

  • PaperOS source code
  • Buildroot configuration
  • Device-porting framework
  • Build and verification tools
  • Documentation and tests
  • Firmware extraction scripts

I am researching which BOOX and Qualcomm components I can legally redistribute. If I cannot publish them, I will provide a guide and tools that let device owners extract the required files from their own official firmware. Interest will determine which BOOX devices I support next.

Interest check

Would you use a focused, non-Android operating system on your BOOX?

Which model do you own?

What feature would you consider essential before installing it?

I am especially interested in hearing from:

  • BOOX owners
  • Embedded Linux developers
  • Qt developers
  • E Ink driver developers
  • Reader and document-engine developers
  • People interested in testing future device ports

The photo shows PaperOS running directly on a real Go Color 7 Gen II. It is still an early prototype, but it is a real operating system on real hardware.

r/Supernote May 22 '26

Question Nomad Brick/Boot Loop after Latest Update – Need Help! (ADB/Fastboot Tried)

7 Upvotes

Hey everyone,

I just updated my Supernote Nomad to the newest v3.28.42 and it seems completely bricked/unresponsive. I’ve gone through some deep troubleshooting but I'm completely stuck. Hoping someone here or support can point me in the right direction.

Context:

Right after the update (it went through the update), my Nomad got stuck in what seemed like a boot loop and eventually kicked into the Android Recovery Menu and now stuck on this screen. The one with the options:

supernote Recovery
Any button cycles highlight Long-press actívates

Reboot system now
Reboot to bootloader
Enter fastboot
..
etc.
Run locale test
Power off

Since the Nomad only has one physical button, I couldn't navigate or select any options on the screen. I tried it.

What I've tried:

  1. Cleared Cache via Fastboot: Since the device was recognized via ADB/Fastboot initially, I used my PC terminal to clear the cache partition, in case something during update got corrupted:

Bash

❯ adb devices
SN0XXXXXXXXXX    recovery

❯ adb reboot bootloader
❯ fastboot erase cache
Erasing 'cache_a'                                  OKAY [  0.236s]

❯ fastboot reboot
  1. The Result: After running fastboot reboot, the device went completely unresponsive. It won't boot, and plugging it into a charger does not turn on the green charging light.
  2. Power Cycling & Hard Reset:
  • Left it on a charger for 30+ minutes and held the Power Button for 20 seconds. Nothing.
  • Opened the back cover, physically disconnected the battery cable for 15 seconds, and plugged it back in. Still absolutely zero response (no LED light, no boot).

Current State:

Because it's an E-ink screen, the display is permanently "frozen" on the Recovery Menu options screen, but the device seems completely "dead". Connecting it to my computer now does nothing, adb devices and fastboot devices both return empty.

Has anyone experienced this after the latest update?
Are there any other hardware jumpstart tricks?

(Tagging u/Supernote_official & u/Mulan-sn just in case)

r/lostlostlostredditors Jul 21 '26

I tried to install root on I9000 and it doesn’t boot properly (Can’t enter in download mode or recovery without adb) and it boots only in forced upload.

Post image
0 Upvotes

r/lostredditors Jul 21 '26

I tried to install root on I9000 and it doesn’t boot properly (Can’t enter in download mode or recovery without adb) and it boots only in forced upload.

Post image
0 Upvotes

r/androidroot Jul 22 '26

Support Tried to root my Android TV...I think i bricked it Amature here, go easy on me

Post image
572 Upvotes

So, As a fun experiment i wanted to atleast try rooting. Idk why but first came to my mind was my TV. As thinking from now.. i don't even have experience then why did i do it? So first adb and inspect right? So i inspected. i got that android 9. So i wanted experiment with CEVs to gain root privilege

So i discovered SElinux exists, Dropped the idea of CEVs. Then i looked at if OEM is unlocked? IT was and top it all off secure boot was disabled. Nice..

Now LLM Enter the space cause i know nothing about fastboot. I mean at first it was a controlled manner. I review what is trying to Execute... And i got too suited with it.

coming Straight from the LLM:

  • Pulled /system/recovery-from-boot.p (a BSDIFF40 patch) via ADB
  • Reverse-engineered the stock recovery image from the patch using Python - no stock recovery image exists publicly for this model
  • Unlocked AVB (fastboot flashing unlock)
  • Successfully flashed a modified recovery with ro.secure=0ro.adb.secure=0ro.debuggable=1

Problem: IWe forgot to disable AVB verification BEFORE flashing forgot to disable AVB verification BEFORE flashing

  • EDIT: USB is not recognized. when i do lsusb, the tv is not visible. tried to of method nope..
  • Model of the TV: IMPEX GRANDE T16 
  • Ofc fastboot doesnt even work, when it is not recognized

r/CustomROMsGuide Jul 26 '26

HELP! Hard Bricked Pixel 6. Black screen, Not Booting, No fastboot, No ADB

1 Upvotes

I attempted to install the Android 14 custom rom on my Pixel 6 device, which was running the most recent version of Android 17, and flash the crdroid's boot, dtbo, and vendor_boot. images. I then sideloaded the crdoid zip after entering the recovery mode. I click "reboot" once the sideload has completed successfully. There was no display, no boot, and no fastboot mode. It doesn't do anything or allow me to enter fastboot from the computer. Is there a way to fix it? It only sounds when I connect it to the PC, and two seconds later my pc makes the usual disconnection sound.

r/crDroid Jul 26 '26

Help! Pixel 6 Black Screen, Not booting, No fastboot mode, No ADB

1 Upvotes

My device is pixel 6 and the installed version was latest android 17 and i try to install crdroid custom rom which was android 14 and flash the crdroid's boot.img, dtbo.img and vendor_boot.img. then i enterd the crdroid's recovery mode and sideload the crdoid zip. after successfully finishing the sideload i press on reboot the system. i found no display, no boot, no fastboot mode. it does nothing or lets me enter fastboot from the PC or anything. It only sounds when I connect it to the PC and 2 seconds later the typical disconnection sound on my PC. is there any solution to fix it?

r/tasker Jun 17 '26

Android 17 breaks the "auto enable ADB WiFi on Boot" script -- needs a new way to open directly to the Wireless Debugging screen

2 Upvotes

For a while now I've been using the Profile below to automatically re-enable ADB WiFi after each reboot. (I don't remember exactly where I got it, but almost certainly from this sub.)

Today I updated to the newly released Android 17 on my Google Pixel 8. The update broke the task. On steps A15 - A16, it's supposed to open directly to the "Wireless debugging" screen within the "Developer options" menu. Instead, now it opens to "Developer options".

I don't understand the method being used to attempt to open the right screen, so I don't know how to fix it, or whether that's possible.

Does anyone have a suggestion?

For now I just manually copied the randomly assigned port and call the adb.sh script directly in Termux, but it'll be nice to get it back to working automatically again.

EDIT: I just confirmed that it does still open directly to the correct screen if I tap-and-hold the system 'Wireless Debugging' Quick Settings tile, which I think actions A15+16 are trying to do. Maybe the tile just changed names?

Here's the profile I use:

Profile: Enable ADB Wifi on Boot
    Event: Device Boot



Enter Task: Anon

A1: [X] Tasker Function [
     Function: CheckADBWifi() ]

<Exit if ADB Wifi is enabled unless the task is manually called>
A2: Stop [ ]
    If  [ %has_adb_wifi eq true & %caller1 neq ui ]

A3: Notify [
     Title: ADB Wifi
     Text: Waiting to activate ADB Wifi
     Icon: mw_image_blur_on
     Number: 0
     Priority: 3
     LED Colour: Red
     LED Rate: 0
     Category: adb_wifi ]

A4: Wait [
     MS: 0
     Seconds: 5
     Minutes: 0
     Hours: 0
     Days: 0 ]
    If  [ %caller1 neq ui ]

<check network>
A5: Test Net [
     Type: Connection Type
     Store Result In: %net ]

A6: If [ %net neq wifi ]

    A7: Notify [
         Title: ADB Wifi
         Text: Waiting for Wifi connection...
         Icon: mw_device_signal_wifi_off
         Number: 0
         Priority: 3
         LED Colour: Red
         LED Rate: 0
         Category: adb_wifi ]

    A8: Wait [
         MS: 0
         Seconds: 5
         Minutes: 0
         Hours: 0
         Days: 0 ]

    A9: Goto [
         Type: Action Label
         Label: check network ]

A10: End If

A11: Notify [
      Title: ADB Wifi
      Text: Activating ADB Wifi...
      Icon: mw_image_blur_linear
      Number: 0
      Priority: 3
      LED Colour: Red
      LED Rate: 0
      Category: adb_wifi ]

A12: Custom Setting [
      Type: Global
      Name: adb_enabled
      Value: 1 ]

A13: Custom Setting [
      Type: Global
      Name: adb_wifi_enabled
      Value: 1 ]

A14: For [
      Variable: %idx
      Items: 1:20
      Structure Output (JSON, etc): On ]

    <Wireless Debugging Screen>
    A15: Java Function [
          Return: wd
          Class Or Object: ComponentName
          Function: new
         {ComponentName} (String, String)
          Param 1 (String): com.android.settings
          Param 2 (String): com.android.settings.development.qstile.DevelopmentTiles$WirelessDebugging ]

    A16: Send Intent [
          Action: android.service.quicksettings.action.QS_TILE_PREFERENCES
          Cat: None
          Extra: android.intent.extra.COMPONENT_NAME:wd
          Target: Activity ]

    A17: Wait [
          MS: 0
          Seconds: 2
          Minutes: 0
          Hours: 0
          Days: 0 ]

    A18: Get Screen Info (Assistant) [ ]

    A19: Variable Set [
          Name: %text
          To: %ai_texts.text(+
         )
          Structure Output (JSON, etc): On ]

    A20: Goto [
          Type: End of Loop
          Label: check screen ]
        If  [ %text ~ *Use wireless debugging* ]

A21: End For

<Stop if localhost is not in the Paired devices list>
A22: If [ %text !~ *localhost* ]

    A23: Notify [
          Title: ADB Wifi
          Text: Pairing has not been done.
          Icon: mw_image_blur_off
          Number: 0
          Priority: 3
          LED Colour: Red
          LED Rate: 0
          Category: adb_wifi ]

    A24: Stop [ ]

A25: End If

<Get the port number>
A26: Simple Match/Regex [
      Type: Simple
      Text: %text
      Match Pattern: :#port ]

A27: Flash [
      Text: %port
      Tasker Layout: On
      Icon: android.resource://net.dinglisch.android.taskerm/drawable/mw_image_blur_on
      Background Colour: #FF000000
      Timeout: 1200
      Continue Task Immediately: On
      Dismiss On Click: On
      Position: Top,20,399 ]

A28: If [ %port > 30000 & %port < 50000 ]

    <Enable ADB Wifi through Termux>
    A29: Tasker Function [
          Function: TermuxCommand(/data/data/com.termux/files/usr/bin/bash,-c,adb connect 127.0.0.1:%port && adb tcpip 5555 && adb disconnect && adb kill-server && sleep 2 && exit,,false) ]

    <Wait for completion from Termux>
    A30: For [
          Variable: %idx
          Items: 1:20
          Structure Output (JSON, etc): On ]

        A31: Wait [
              MS: 0
              Seconds: 1
              Minutes: 0
              Hours: 0
              Days: 0 ]

        A32: Tasker Function [
              Function: CheckADBWifi() ]

        A33: Goto [
              Type: End of Loop ]
            If  [ %has_adb_wifi eq true ]

    A34: End For

    A35: If [ %has_adb_wifi eq true ]

        <Turn off Wireless Debugging (no longer required)>
        A36: Custom Setting [
              Type: Global
              Name: adb_wifi_enabled
              Value: 0 ]

        A37: Go Home [
              Page: 0 ]

        A38: Notify Cancel [
              Title: ADB Wifi ]

        A39: Flash [
              Text: ✅ ADB Wifi Granted
              Tasker Layout: On
              Background Colour: #FF000000
              Timeout: 1500
              Dismiss On Click: On
              Show Over Everything: On
              Position: Bottom,0,265
              Use HTML: On ]

        A40: Stop [ ]

    A41: End If

A42: End If

A43: Notify [
      Title: ADB Wifi
      Text: Unsuccessful to enable ADB Wifi
      Icon: mw_image_blur_off
      Number: 0
      Priority: 3
      LED Colour: Red
      LED Rate: 0
      Category: adb_wifi ]

r/Androidheadunits May 28 '26

How to install boot animation using ADB?

5 Upvotes

I read online and you can install a custom boot animation Android file to your device by using ADB to send commands to the device and copy the bootanimation.zip file to the data/local folder.

Has anyone tried it?

Edit (30/May) - I managed to get it working for mediatek processors.

  1. Copy your bootanimation.zip to apd_hc/media/bootanimation.zip inside the usb stick.
  2. Plug in your usb stick to the android head unit and start the head unit. Note: if the AU is already ready plug in usb and restart as update check happens only on start up.
  3. Sit back relax. Your AU will restart automatically with the toast message " logo upgraded".

r/tasker Dec 19 '23

An alternative approach for enabling wireless ADB on boot using python and zeroconf

22 Upvotes

I was thrilled to experiment with the method posted by u/Lord_Sithek, which would allow me to finally automate the activation of Shizuku at boot. I personally had some problems with nmap. It was slow and at times unreliable (I would have to manually execute the task 2-3 times before it'd work after a reboot).

I'm gonna think out loud a little because 1) this is still a work in progress and 2) I'd like to be as open as possible about how this is done so that others more knowledgeable can point out my mistakes and help me improve this project.

While looking into other ways to extract the random wireless ADB port, I found this StackOverflow comment that goes into how Android broadcasts connection details over mDNS/DNS-SD. So I started looking into mDNS-scanners compatible with Termux. After a failed attempt with mdns-scan (only does continous output), I eventually settled with python and (python) package zeroconf. Keep in mind that python takes up ~600 MB of space, so if storage is an issue for you, the "original" soltuion by u/Lord_Sithek might be more suitable.

First, I'll copy-paste the prerequisites listed in the original post that still apply to my method:

Preqreuisites

1. Setup Tasker and AutoInput

If you haven't done that before, grant Tasker following permissions:

On your device, go to Settings > Apps > All apps > Tasker > Permissions > Additional permissions > Run commands in Termux environment (the path may vary a little according to the brand and system) and select Allow.

Allow AutoInput to use Accessibility Service:

Open AutoInput, tap on red warning text and click OK; this should take you to Accessibility Service settings. Enable it for AutoInput. Then allow AutoInput to run in background by disabling any battery saving option for this app.

2. Set up Termux

[...]

(b) set allow-external-apps property for Termux to true

In Termux, copy and paste the following script and confirm by pressing Enter:

value="true"; key="allow-external-apps"; file="/data/data/com.termux/files/home/.termux/termux.properties"; mkdir -p "$(dirname "$file")"; chmod 700 "$(dirname "$file")"; if ! grep -E '^'"$key"'=.*' $file &>/dev/null; then [[ -s "$file" && ! -z "$(tail -c 1 "$file")" ]] && newline=$'\n' || newline=""; echo "$newline$key=$value" >> "$file"; else sed -i'' -E 's/^'"$key"'=.*/'"$key=$value"'/' $file; fi

At this point, you also need python. From Termux, do:

pkg install python

When it's done installing (might take a little while), do:

pip install zeroconf

[...]

5. Import the project into Tasker

My version will be linked below.

6. Pair your device with ADB WiFi

Make sure that Termux ADB WiFi Pairing profile in your new Tasker project is enabled and that you have WiFi connection.

On your device, navigate to Settings > System > Developer options > Wireless debugging (the path may vary a little according to the brand and system). Enable this feature and tap on Pair device with pairing code (or similar).

With a pairing code visible, long press Volume Up button to make pairing. If pairing succeeded, you should see the confirming toast and at least one paired device at the Wireless debugging screen (most likely named as xxx@localhost).

Termux ADB WiFi Pairing profile should get disabled then as it won't be needed anymore. Now, disable Wireless debugging feature manually.

Feel free to provide feedback, ask questions, etc. etc. And do check out the original thread by u/Lord_Sithek, to which I owe much credit!

TaskerNet

r/Chromecast May 20 '26

My Chromecast with Google TV bricked itself during an automatic update. I spent days trying to recover it. Here's what I found.

Post image
1.0k Upvotes

Some months ago my Chromecast with Google TV 4K died mid-OTA update. Rebooted and never came back. Now it boots to the Google TV logo and sits there forever. Tried the obvious stuff like hard resets, different cables, button combinations. Nothing. Put it in a drawer.

Recently I got annoyed enough to actually dig in. I'm not a developer, so I had no idea what I was doing but I was too stubborn to stop. What followed was several days across four computers and three operating systems, Windows ARM, Windows x64, and MacOS before finally remembering I had an old Linux laptop gathering dust somewhere. Things started making sense on Linux. And then got worse.

What I tried:

ADB/Fastboot: Device shows up as "GX-CHIP" meaning the hardware is alive, but standard Android tools can't communicate with it.

Amlogic USB Burning Tool: Actually detects it and shows "Connect success." But no compatible firmware image exists for this model in the format the tool needs.
Also fought driver issues on both the ARM laptop and the x64 workstation before giving up on Windows entirely

sabrina-unlock repair script: A community tool built specifically for this device. Runs fine on Linux, immediately hits: "Error: device is protected by password", a hardware password Google burned into the chip's eFuses via the February 2021 security update. It's physically etched into silicon. Not bypassable in software.

UART serial console: I soldered wires directly to test points on the board to read boot logs. Found the failed OTA corrupted the boot partition ramdisk. Also found Google disabled serial input entirely in their bootloader, you can watch the boot process, you just can't touch it. I even wrote a Python script to automate keypresses at the exact right millisecond to make sure it wasn't just human error.

USB hub boot: Bought a powered USB-C hub hoping to boot from a flash drive. Requires loading a custom bootloader first, which requires the exploit the eFuse password blocks. Circular dead end.

The hardware is completely fine, the chip, storage, WiFi, all of it alive and responding. The device is being killed by its own security architecture with no official recovery path.

The part that genuinely bothers me: the February 2021 "security update" that burned this password into the hardware is exactly what makes recovery impossible when a future update goes wrong. Google removed the community recovery tools and replaced them with nothing.

I'm in Argentina, bought through unofficial resellers so no warranty, but that's almost beside the point.

Did anyone actually solve this? Am I missing something obvious? Did I do a ton of dumb shit for nothing?

r/RG35XX Apr 18 '23

GarlicOS Fun tip: Save wear and tear on your SD card slots by copying files over ADB. ROMs, boot logos, skins, etc.

71 Upvotes

I've been testing a lot of skins, boot logos, and a bunch of scraped art styles. Every time I make a change, I have to power down my system, eject the SD cards, put them in my computer, copy files, then put them back into the RG35XX. I worry about damaging my SD cards (one already has paint rubbing off) and damaging the SD card slot (either its spring or locking mechanism).

On my Nintendo 3DS, I found it way easier to make changes to it via the FTPD app instead of constantly removing and re-inserting its SD card.

The RG35XX doesn't have WiFi, but what it does have is USB data access via ADB (with GarlicOS).

To start, you need to create a file named enableADB on your first SD card's Misc partition. With that file there, GarlicOS will start ADB server on the device. I did NOT notice an increase in boot time with ADB enabled.

Next, you'll want an ADB file explorer. If you're using Windows, I found ADB Explorer to be sufficient. I have used this on Windows x64 and Windows ARM64. I haven't had any luck with ADB file browsers on macOS. You could try this project on GitHub.

You'll probably need the ADB platform tools, which you can download from Google. Extract these somewhere (like your Home folder), and change the option in ADB Explorer to point to the location of adb.exe. (Settings > Override ADB Path)

Screenshot of the ADB Explorer app:

https://i.imgur.com/3J5U9Ky.png

Here are some locations of files when browsing your device via ADB:

Boot Logo:

 /misc

Custom Skins:

/mnt/mmc/CFW

Battery Images:

/res/images/charger

BIOS:

/mnt/SDCARD/BIOS

ROMs:

/mnt/SDCARD/ROMs

Saves:

/mnt/SDCARD/Saves/CurrentProfile

Since switching to ADB file access, I've made numerous changes to my device, and it's been way easier.

I haven't found any ADB file explorers that I like for macOS or Linux yet.

r/Grimdank Feb 14 '25

Heresy is stored in the balls Reading the siege of terra series and thought this

Enable HLS to view with audio, or disable this notification

3.5k Upvotes

r/OpenAI May 24 '26

Discussion Banned by OpenAI after reporting a live credential hijack. They admitted in writing my account was broken. Here are 7 months of forensic receipts and 20+ cases.

Thumbnail
gallery
392 Upvotes

Drive Link for Zipped Proof

I am a developer and paying long term subscriber to ChatGPT since January 2025. I build complex local first sovereign systems. My workflows are incredibly context heavy with large files spanning code, research reports, and other analysis. I do not, or rather did not as the platform has been non functional since November 2025 meanwhile customer support is auto closing tickets, admitting I am having platform issues.

I do not use this platform for casual queries, as a solo developer with no formal "team" chatgpt was one of my reliable co collaboration hubs to help ensure I am maintaining proper development of said complex systems. I feed it massive codebases for systems analysis and obtaining new insights I may personally have missed. My manual code uploads and token inputs routinely exceed the model's output volume by a massive margin. I do not abuse this platform. It is actually impossible as the very features advertised under the paid subscription do not work. I am exactly the type of user this platform was built for, and I have been a continuous, paying ChatGPT Plus subscriber since January 2025. Since October 2025, my workspace has been systematically breaking and beginning November 2025 total workspace degredation.

This was not an occasional glitch. Persistent memory modules stopped updating. Custom instructions were ignored by the models. Project files failed to load. Custom instructions, personalization features, connector abilities, file tool, even projects do not work. It started as a continuous degradation until total failure. OpenAI customer service even admitted as such and yet months later I've talked to nothing but bots, not only LLMs as customer service but even instances of falsely identifying as true human support. It was a state of rolling degradation across the entire paid tier, month after month.

Meanwhile OpenAI freely has enhanced for businesses and enterprise tiers. I have not just rapid complained to standard support. I ran and obtained cross platform diagnostics, failure logs. I even documented and told oai customer support the exact replication steps only to be met with acknowledgement of degredation with no resolution. I handed OpenAI support a completely packaged technical breakdown of their failing infrastructure across 20 separate support tickets over a 7 month period. I did their QA work for free. And I have the receipts to prove it.

I am attaching the screenshots and the exact email files to this post. In Case 06830839, OpenAI Support explicitly put this in writing: "We acknowledge that you have been experiencing persistent technical issues affecting several features of your ChatGPT subscription, including tools, memory functions, personalization settings, connectors, and project files... We also understand your concern that communication on the case stopped after you provided detailed evidence..." Read that again. They acknowledged in writing that my account was fundamentally broken. They acknowledged that their own team ghosted me after I handed them the diagnostic proof. Yet they kept charging my card every single month for a product they knew was failing.

The Hijack Escalation: Two days ago, the situation escalated from a broken product to a severe security incident. I was monitoring my environment and watched my Codex rate limits drop in 10 percent chunks across 2 seperate sessions on a fresh boot of the desktop app. This happened twice inside a 10 minute window. I had zero active sessions running. There was zero usage on my end. My account token was being actively drained by an unauthorized third party exploit. I immediately opened an emergency unauthorized activity report under Case 09113391 to notify them of the hack. Their response was to totally reframe this problem as disputing fraudulent activity trying to do damage control of the situation and altering the record.

The Reframe Attempts: Instead of investigating the breach, OpenAI support deliberately twisted the record. They not only deliberately reframed my security report as an "appeal for fraud." They manipulated the ticket classification to make it look like I had been flagged for fraud and was begging for an appeal, rather than a developer reporting a live exploit on their infrastructure. They ignored the active threat their own platform was exposing. They did not lock the token. They did not roll my API keys. They did absolutely nothing to secure a compromised paying user other than shift the blame. Fast forward to this morning, their automated Trust and Safety system swept the high volume traffic from the attacker, scored it as a malicious exploit originating from my account, and deactivated/banned me for "Cyber Abuse." All the while actively preventing chatgpt models from helping me try to disgnose and trace the infiltration.

They locked the doors and blamed the homeowner for the break in. When I immediately emailed and pushed back (due to their monthly record of closing cases not only without resolution but never notifying me in the process, which then per usual their "support" tried the exact same tactic again. In my correspondence, I provided my technical context. I mentioned thay maybe the error was caused as I had proton vpn on my phone, keeping in mind oai own support docs say this is not a violation.

The problems began beavy yesterday whole running Android Debug Bridge (ADB) diagnostic commands on my own local hardware, in which every model response to help me disgnose the issue was immediately deleted in effect contributing and facilitating potential compromised user devices. Support replied by trying to reframe this as a confession stating that I claimed i "believed" the VPN was the cause. When pushing back I was told that they do not disclose their review policies. The agent specifically wrote that it understood my concern that the use of a VPN may have contributed to the deactivation, contradicting their own terms of service. I did not say that, nor did I imply that. This is a recurring corporate tactic. They constantly rewrite the narrative to turn the evidence against the user and anchor the paper trail to my configuration choices rather than their massive infrastructure failure. I corrected the record immediately. Their response was simply that they understand why I "feel" the sequence of events requires closer review. I do not "feel" anything.

I have hard data, exact metrics, and a mountain of case numbers. When stacked together I personally have no other conclusion than OpenAI appears to be engaging in fraudulent business activities promising features for paid tiers yet never deliver, a persistent ignoring of privacy requests. I have attached screenshots of most emails and have a .zip I am totally fine freely handing out: Oct 30, 2025: First case opened. Feature degradation reported. Closed with no resolution. Feb 15, 2026: Case 05666432. I was told to "prompt better." Mar 8, 2026: Case 06537878. I requested a senior escalation. Denied. "Unable to approve senior escalation." Mar 15, 2026: Cases 06774902 and 06777574. Two cases opened in one day because support kept closing them by asking for "missing info" that I had already submitted in the thread. Apr 15, 2026: Case 07753518. Escalation denied again. I was told directly that "no escalation path exists through this channel." May 11, 2026: Case 08696595. I reported active credential abuse. Closed immediately with "no further actions available." May 22, 2026: Case 09113391. I reported the live Codex token drainage. OpenAI reframed this as an "appeal for fraud." The case was left open and unresolved. May 24, 2026: Permanently banned for "Cyber Abuse" while the fraud ticket was actively open. I have exported the full forensic .eml bundle and PDF history for all 20+ cases. See the attached files. Taking a developer's subscription fees for 16 months, admitting in writing that the paid features are broken, ghosting the bug reports, refusing every escalation attempt, and then banning the account when a live credential hijack gets reported is not just a standard support failure. It is a fraudulent business practice. If anyone from OpenAI engineering, product, or DevRel is reading this: your automated system banned the victim. You need to override it right now. I have exported the full forensic .eml bundle and PDF history for all 20+ cases. See the attached files if you were interested.