Automatically activate Shizuku in Android 14+ (non-root)

[Knud3]

Just got Android 14 phone and tried to find a possibility to activate Shizuku automatically on the device boot, and every possible solution led to Tasker and MacroDroid. I want to believe that those both projects are legit, but I did not see it an option to install a closed-source app that has rights to "everything". I picked the second-best option and used Termux and shell scripts. Maybe you know better?

After some trial and error, I came to this. I hope I have everything essential here and have not missed any steps.

To activate Shizuku (TL;DR): Press Wireless debugging tile and run shizuku command. Done!

Initialize

All of this needs to be done just once, so do not worry about complexity.

1. Install Shizuku and Termux (eg. with F-Droid or Droid-ify)

2. Initialize Termux with commands:

   pkg up
   pkg install nmap openssl android-tools
   termux-setup-storage

3. Open the Termux and Wireless debugging settings page in the split screen

4. Press Pair device with pairing code in the Wireless debugging settings page

5. Give ADB pairing command in Termux screen: adb pair localhost:Port "WiFI pairing code" (eg. adb pair localhost:37323 908693)

6. Pair and start Shizuku via wireless debugging

7. Use Export files in Use Shizuku in terminal apps from Shizuku app (export files eg. /storage/emulated/0/Shizuku)

8. Create a copy.sh file including the script below to the same directory (use eg. Squircle CE)

   #!/data/data/com.termux/files/usr/bin/bash
   
   BASEDIR=$( dirname "${0}" )
   BIN=/data/data/com.termux/files/usr/bin
   HOME=/data/data/com.termux/files/home
   DEX="${BASEDIR}/rish_shizuku.dex"
   
   # Exit if dex is not in the same directory
   if [ ! -f "${DEX}" ]; then
     echo "Cannot find ${DEX}"
     exit 1
   fi
   
   # Create a Shizuku script file
   tee "${BIN}/shizuku" > /dev/null << EOF
   #!/data/data/com.termux/files/usr/bin/bash
   
   # Make a list of open ports
   ports=\$( nmap -sT -p30000-50000 --open localhost | grep "open" | cut -f1 -d/ )
   
   # Go through the list of ports
   for port in \${ports}; do
   
     # Try to connect to the port, and save the result
     result=\$( adb connect "localhost:\${port}" )
   
     # Check if the connection succeeded
     if [[ "\$result" =~ "connected" || "\$result" =~ "already" ]]; then
   
       # Show a message to a user
       echo "\${result}"
   
       # Start Shizuku
       adb shell "\$( adb shell pm path moe.shizuku.privileged.api | sed 's/^package://;s/base\\.apk/lib\\/arm64\\/libshizuku\\.so/' )"
   
       # Disable wireless debugging, because it is not needed anymore
       adb shell settings put global adb_wifi_enabled 0
   
       exit 0
     fi
   done
   
   # If no working ports are found, give an error message to a user
   echo "ERROR: No port found! Is wireless debugging enabled?"
   
   exit 1
   EOF
   
   # Set the dex location to a variable
   dex="${HOME}/rish_shizuku.dex"
   
   # Create a Rish script file
   tee "${BIN}/rish" > /dev/null << EOF
   #!/data/data/com.termux/files/usr/bin/bash
   
   [ -z "\$RISH_APPLICATION_ID" ] && export RISH_APPLICATION_ID="com.termux"
   
   /system/bin/app_process -Djava.class.path="${dex}" /system/bin --nice-name=rish rikka.shizuku.shell.ShizukuShellLoader "\${@}"
   EOF
   
   # Give execution permission to script files
   chmod +x "${BIN}/shizuku" "${BIN}/rish"
   
   # Copy dex to the home directory
   cp -f "${DEX}" "${dex}"
   
   # Remove dex write permission, because app_process cannot load writable dex
   chmod -w "${dex}"

9. Execute the script in Termux (eg. bash ./storage/shared/Shizuku/copy.sh)

Usage

Commands:

• shizuku - Activate Shizuku
• rish - Open the ADB shell or run the ADB shell command

To activate Shizuku you need to enable wireless debugging. The easiest way to do it is to use a quick setting tile. To add it, you need to enable it in Quick settings developer tiles in Developer options. After that just write shizuku in Termux and press enter. Everything is set and done. Wireless debugging is automatically disabled because it does not need to be running in the background for Shizuku to work. This needs to be done once every reboot.

When you need to open the ADB shell, just use the rish command in Termux. With the rish -c 'command' (eg. rish -c 'whoami') you can run it directly or use it in scripts. More info can be found here.

You can also use Termux:Widget to make shortcut to home screen.

Please, also see the common problems.

[Ermageeerd]

Combined with Termux:Boot, this feels perfect! Thanks!

[Knud3]

If you can run adb commands, then you are already connected. So, you do not need this script at all. There is no need to enable wireless debugging either. If you need Shizuku, just run: adb shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh

Would be interesting to hear how you ended up in that state... Do you have a stock un-rooted ROM on your phone?

[Ermageeerd]

If you can run adb commands, then you are already connected. So, you do not need this script at all. There is no need to enable wireless debugging either. If you need Shizuku, just run: adb shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh

Would be interesting to hear how you ended up in that state... Do you have a stock un-rooted ROM on your phone?

Yes, I have tried to mimic root without doing so for a while, and stay on the OG rom. I'm starting to believe it's SystemUI Tuner as it can edit system settings.

[Dondrejohnson5]

Yes, I have tried to mimic root without doing so for a while, and stay on the OG rom. I'm starting to believe it's SystemUI Tuner as it can edit system settings.

@Ermageeerd I would also very much like to know how you managed to do that locally

[Ermageeerd]

@Ermageeerd I would also very much like to know how you managed to do that locally

Use SystemUI Tuner to set adb_wifi_enabled to 1 on boot, then follow these instructions here, modified for Termux:Boot. That did it for me.
(You can also likely do this normally and just use this guys script with Macrodroid, it should work)

[Coool]

Use SystemUI Tuner to set adb_wifi_enabled to 1 on boot

"Sorry, this feature only works with Android 12 and later" 😂

[mizzunet]

Thanks a lot. I'm using it with Macrodroid
Only if Termux could change settings values(adb_wifi_enabled), I wouldn't need Macrodroid

Shizuku.macro.zip

Edit:

Only if Termux could change settings values(adb_wifi_enabled), I wouldn't need Macrodroid

Oh wait, Shizuku itself could turn on Wireless Debugging, right? Perhaps with WRITE_SECURE_SETTINGS

[mizzunet]

But only after manually enabling it in the first place.

If you are asking about manually enabling Wireless Debugging before running your shizuku. You could turn on that with Macrdroid(setting adb_wifi_enabled 1).

But if Termux could modify settings(perhaps with Termux:API companion), you wouldn't need Macrdroid at all. But Termux can't do that AFIK

Or maybe if Shizuku itself could turn on Wireless Debugging(just by modifying the above adb_wifi_enabled), that'd be way better. Wish Rikka consider this

[Knud3]

Yes, but my main motivation was that I wouldn't be using MacroDroid nor Tasker as told in the first sentences of the instructions.

I'm sure Rikka has considered that, but it's not that straightforward. If you have a solution proposition, please, open PR.

[mizzunet]

If you have a solution proposition, please, open PR.

I don't know Kotlin

[cronyakatsuki]

@mizzunet Hello, I know this is an old thread but just to let you know that you can enable wireless debugging with tasker.

To do it you to use custom setting action.

Create task, go to add action screen, then go to Settings/Custom Setting.

Then set 'Type' to global, name to adb_wifi_enabled and value to 1.

[Knud3]

@mizzunet Hello, I know this is an old thread but just to let you know that you can enable wireless debugging with tasker.

There are numerous discussions about accomplishing this with Tasker or MacroDroid, but this thread specifically highlighted NOT to utilize them.

[J-b432]

. في الخميس، ٨ أغسطس ٢٠٢٤, ١:٢٥ م MSHB ***@***.***> كتب:

…

Thanks a lot. I'm using it with Macrodroid Screenshot_20240808-155421.png (view on web) <https://github.com/user-attachments/assets/4ef8f146-2554-4ce8-82bb-937a2ceaeb32> — Reply to this email directly, view it on GitHub <#462 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJJET6KJPOTSVC5GH2INJRDZQNBTNAVCNFSM6AAAAABFSLMR22VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMRXGQYDGOA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mizzunet]

@Knud3 do you happen to know check if Shizuku service is running already from shell?

[Knud3]

Maybe just capture rish stderr, and if it equals to "Server is not running", then it is not running.

[mizzunet]

Yep, figured this out :)

[e1399579]

so where is "rish_shizuku.dex"?

[Knud3]

You export it in step 7.

[e1399579]

sorry, i don't understand, export form where?
/storage/emulated/0/Shizuku not exists

[Knud3]

It is just for example. Export where ever it is accessible and to your liking. You can create a Shizuku directory if that is your choosing.

[e1399579]

I just see. before i thought step 7 is some explain text, but now i find "Export files" and "Use Shizuku in terminal apps" is Shizuku App's function.
sorry for waste your time and thanks for your help

[Knud3]

No worries! Glad you figured it out. I did add a screenshot to the instructions.

[onoakino]

Thank you for this! It works for my non rooted Poco device Android 14. But it doesn't automatically start Shizuku on my device. After executing the "shizuku" command on Termux, I have to manually press the "Start" button on the Shizuku app for the service to start.

Would you have any idea why this is happening? From the gif you posted, I can see from the terminal that the shizuku command would automatically start the service.

Also, from the Termux terminal, when I issue "shizuku", there's an output that reads:

already connected to localhost:33945 adb: more than one device/emulator adb: more than one device/emulator

I don't know if that output is connected to my issue or not. Any suggestions?

[juandvasquezp]

@onoakino I just happened to have the same problem, I think the problem relies on that we're trying to connect to every open port and as a result when we use adb devices it's possible that we're going to be connected to 2 or more instances.

Well, what I did in order to solve it was to add this line:
adb reconnect offline

It worked for me, you can try and tell me if it works for you as well.

Edit:
I actually found a better solution using directed commands, so it's better to use that instead.

So I added a line that sets target_device="localhost:${port}" and that target device will be used for the next adb commands:
adb -s "$target_device" shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh
adb -s "$target_device" shell settings put global adb_wifi_enabled 0

I also kept adb reconnect offline just in case

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

BASEDIR=$( dirname "${0}" )
BIN=/data/data/com.termux/files/usr/bin
HOME=/data/data/com.termux/files/home
DEX="${BASEDIR}/rish_shizuku.dex"

# Exit if dex is not in the same directory
if [ ! -f "${DEX}" ]; then
  echo "Cannot find ${DEX}"
  exit 1
fi

# Create a Shizuku script file
tee "${BIN}/shizuku" > /dev/null << EOF
#!/data/data/com.termux/files/usr/bin/bash

# Make a list of open ports
ports=\$( nmap -sT -p30000-50000 --open localhost | grep "open" | cut -f1 -d/ )

# Go through the list of ports
for port in \${ports}; do

  # Try to connect to the port, and save the result
  result=\$( adb connect "localhost:\${port}" )

  # Check if the connection succeeded
  if [[ "\$result" =~ "connected" || "\$result" =~ "already" ]]; then

    # Show a message to a user
    echo "\${result}"
    
    # Add this to add recconnect to offline devices. This adds some error correction
    # When there's just one device connected, it will return nothing, so the code will also run regardless
    adb reconnect offline
    
    # Set the target device
    target_device="localhost:\${port}"
    
    # Show a message to a user with the target device
    echo "using device: \${target_device}"

    # Start Shizuku
    adb -s "\$target_device" shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh

    # Disable wireless debugging, because it is not needed anymore
    adb -s "\$target_device" shell settings put global adb_wifi_enabled 0
    
    # Stop the ADB server as it'll no longer be usefull
    adb kill-server

    exit 0
  fi
done

# If no working ports are found, give an error message to a user
echo "ERROR: No port found! Is wireless debugging enabled?"

exit 1
EOF

# Set the dex location to a variable
dex="${HOME}/rish_shizuku.dex"

# Create a Rish script file
tee "${BIN}/rish" > /dev/null << EOF
#!/data/data/com.termux/files/usr/bin/bash

export RISH_APPLICATION_ID="com.termux"

/system/bin/app_process -Djava.class.path="${dex}" /system/bin --nice-name=rish rikka.shizuku.shell.ShizukuShellLoader "\${@}"
EOF

# Give execution permission to script files
chmod +x "${BIN}/shizuku" "${BIN}/rish"

# Copy dex to the home directory
cp -f "${DEX}" "${dex}"

# Remove dex write permission, because app_process cannot load writable dex
chmod -w "${dex}"

[Docga1835]

I have connected my phone to used debugging on my Galaxy watch and this may be why. But I am still unsure what this other port is as even when I have debugging turned on my watch it shows a different port number. Here is my result. I ran adb devices before and after running shizuku to show you what happens. Still no luck. Any other ideas?

[juandvasquezp]

I have connected my phone to used debugging on my Galaxy watch and this may be why. But I am still unsure what this other port is as even when I have debugging turned on my watch it shows a different port number. Here is my result. I ran adb devices before and after running shizuku to show you what happens. Still no luck. Any other ideas?

Honestly, no. It should work as far as I know. If you're using adb -s <device>, there's no reason for it to say "more than one device/emulator" for those adb commands.

Actually, I don't see it trying to reconnect that offline device, and the website says that using -s to specify the device should avoid that error.

[juandvasquezp]

@Docga1835 I just updated my original comment, could you please try it?

Something happened that last reply didn't have the \ symbols so the variables were being referenced while executing the copy.sh script, variables that shouldn't have been read.

Try it and tell me how it goes

[Docga1835]

@juandvasquezp I just tried it. Again, no luck. I can start Shizuku directly by running the command adb -s <device> shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh. But when I run the command shizuku to run the script, my only result is an output that adb is connected to the device, but Shizuku is not running. (I stopped shizuku before trying the script again)

[juandvasquezp]

@Docga1835 Well, I'm out of ideas. I don't know if either is something wrong with your Termux or with your process, but now, nothing makes sense to me.

[droid1413]

Solving the "adb: more than one device/emulator" Error in Shizuku When running the Shizuku command with multiple paired devices, you're encountering a common ADB limitation that prevents it from knowing which device to target. This error occurs because ADB detects all four of your paired devices and cannot automatically select one to work with. Fortunately, there are several effective solutions to resolve this issue without needing to unpair your regularly used devices. Understanding the Problem The error message "adb: more than one device/emulator" is triggered when the ADB system (which Shizuku relies on) detects multiple connected devices but doesn't have instructions on which one to use. This commonly happens when: 1. You have multiple devices paired via wireless debugging 2. You're trying to use Shizuku on the current device but ADB sees all paired connections 3. The standard Shizuku script doesn't specify which device to target by default When you run the "shizuku" command, it attempts to establish a connection with an ADB device, but since you have four paired devices, it cannot determine which one should receive the commands. Solution 1: Modify the Shizuku Command to Specify Device The most direct solution is to modify the "shizuku" command to include the specific device you want to target: Using Device IP and Port 1. Open your Termux app 2. Check your currently connected devices with: text adb devices 3. Identify your current device (usually shown as localhost:port) 4. Modify your shizuku command to target this specific device: text shizuku -s localhost:PORT (Replace PORT with your actual port number) If the -s flag isn't directly supported by the shizuku command, you may need to modify the underlying script. Solution 2: Temporarily Disconnect Other Devices Before running the "shizuku" command, you can disconnect other devices: 1. List all connected devices: text adb devices 2. Disconnect all devices: text adb disconnect 3. Connect only to your current device: text adb connect localhost:PORT (Get the PORT from Wireless debugging settings) 4. Run the "shizuku" command normally Solution 3: Modify the Shizuku Script If you're comfortable with editing scripts, you can modify the Shizuku script itself: 1. Locate the shizuku script file in your Termux environment 2. Edit the script to add the device selector to the underlying ADB commands 3. Add the "-s localhost:PORT" parameter to any ADB command in the script For example, if the script contains lines like: text adb shell command Change them to: text adb -s localhost:PORT shell command Solution 4: Use Shizuku's Built-in Terminal Support Shizuku offers built-in terminal app support that might bypass this issue: 1. Open the Shizuku app 2. Go to "Use Shizuku in terminal apps" 3. Export the required files to a location accessible by Termux (e.g., /storage/emulated/0/Shizuku) 4. Follow the instructions to set up the "rish" command in Termux 5. Use "rish" instead of direct ADB commands to avoid the multiple device issue Identifying the Correct Device To ensure you're targeting the right device: 1. Go to Developer Options > Wireless debugging 2. Note the IP address and port shown under "IP address & port" 3. This is the address you should use with the -s flag (typically in the format localhost:PORT) The port number changes each time wireless debugging is enabled, so you'll need to check it whenever you restart the connection. Conclusion The "adb: more than one device/emulator" error occurs because ADB cannot automatically select which of your four paired devices to use. By explicitly specifying the target device with the -s flag or temporarily disconnecting other devices, you can successfully run the "shizuku" command without needing to permanently unpair your regularly used devices. If you frequently switch between multiple devices, creating a custom script that automatically detects and selects the local device might be the most convenient long-term solution. This would allow you to maintain all your device pairings while still using Shizuku seamlessly on your current device.

…

On Sun, 6 Apr, 2025, 18:48 Docga1835, ***@***.***> wrote: Everytime I run "shizuku", I get "adb: more than one device/emulator" so it fails every single time. I tried adding the prior suggestion from @juandvasquezp <https://github.com/juandvasquezp> "adb reconnect offline", but I am still getting "adb: more than one device/emulator". I do have 4 paired devices that I use on a regular basis. Any ideas to get around this issue? — Reply to this email directly, view it on GitHub <#462 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BQCAKNPOAWYLAIBEGNTOCKT2YFSHBAVCNFSM6AAAAABFSLMR22VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENZUGI2TQNI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Docga1835]

Unfortunately several of these suggestions are unsuitable. If I have to go through the effort of finding my new port number each time I would just open the app and start Shizuku manually.

Additionally, even if I manually disconnect from the other device(s), the code presented here is a loop that finds the available ports and cycles through them. If I disconnect from one it would just pick it back up again. See the attached.

[droid1413]

To resolve the issue of "adb: more than one device/emulator" and disconnect the offline device while keeping the active one, follow these steps: Steps to Disconnect Offline Device List Connected Devices: Run: bash adb devices Identify the offline device (e.g., localhost:XXXXX offline) and the active device (localhost:XXXXX device). Disconnect Offline Device: Use the adb disconnect command with the IP and port of the offline device: bash adb disconnect localhost:XXXXX Replace XXXXX with the port of the offline device. Verify Active Device: Run: bash adb devices Ensure only your active device (localhost:XXXXX device) remains connected. Run Shizuku: Execute the Shizuku command targeting your active device: bash shizuku -s localhost:XXXXX Replace XXXXX with the port of your active device. Additional Tips If the offline device persists after disconnecting, restart the ADB server: bash adb kill-server adb start-server Ensure USB debugging is enabled on your phone and confirm any RSA key prompts

…

On Mon, 7 Apr, 2025, 18:32 Docga1835, ***@***.***> wrote: I have connected my phone to used debugging on my Galaxy watch and this may be why. But I am still unsure what this other port is as even when I have debugging turned on my watch it shows a different port number. Here is my result. I ran adb devices before and after running shizuku to show you what happens. Still no luck. Any other ideas? Screenshot_20250407_132610_Termux.jpg (view on web) <https://github.com/user-attachments/assets/781dd32c-55ad-495d-bd9a-4b57a0625c2a> — Reply to this email directly, view it on GitHub <#462 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BQCAKNO4PMGGYDXS5M3AYSD2YKZBZAVCNFSM6AAAAABFSLMR22VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENZVGQZDOOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Knud3]

Thank you for your efforts to assist, but could you please refrain from sending these non-existent formatted AI-generated comments, or at least keep them within the same thread? Thanks!

[droid1413]

To resolve your issue with Shizuku and multiple connected devices, follow these steps: Steps to Disconnect the Offline Device Identify Devices: Run: bash adb devices Note the ports for both devices: the offline one (localhost:XXXXX offline) and the active one (localhost:XXXXX device). Disconnect Offline Device: Use: bash adb disconnect localhost:XXXXX Replace XXXXX with the port of the offline device. Verify Active Device: Run: bash adb devices Confirm only your phone (localhost:XXXXX device) remains connected. Start Shizuku: Run Shizuku targeting your active device: bash shizuku -s localhost:XXXXX Replace XXXXX with the port of your phone. Additional Debugging Tips If the offline device persists, restart ADB: bash adb kill-server adb start-server Ensure wireless debugging is enabled only on your phone during this process

…

On Mon, 7 Apr, 2025, 18:32 Docga1835, ***@***.***> wrote: I have connected my phone to used debugging on my Galaxy watch and this may be why. But I am still unsure what this other port is as even when I have debugging turned on my watch it shows a different port number. Here is my result. I ran adb devices before and after running shizuku to show you what happens. Still no luck. Any other ideas? Screenshot_20250407_132610_Termux.jpg (view on web) <https://github.com/user-attachments/assets/781dd32c-55ad-495d-bd9a-4b57a0625c2a> — Reply to this email directly, view it on GitHub <#462 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BQCAKNO4PMGGYDXS5M3AYSD2YKZBZAVCNFSM6AAAAABFSLMR22VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENZVGQZDOOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Docga1835]

I'm really having a hard time getting this offline device to go away. I don't even know what it is anymore as it doesn't match my watch. Debugging is only on with my phone. Every time it comes back. Is there a way to parse the results of adb devices and pick the online device?

[droid1413]

The issue is that Shizuku is still trying to use ADB in a way that conflicts with the existing connections, even after you've disconnected the offline device. Steps to Correct the Issue Kill ADB Server: Run: bash adb kill-server Start ADB Server: Run: bash adb start-server Verify Devices: Run: bash adb devices Ensure only your phone (localhost:42405 device) is listed. If the offline device reappears, disconnect it again: bash adb disconnect localhost:35131 Repeat the adb devices command to verify. Start Shizuku with Correct Port: Run: bash shizuku -s localhost:42405 If the Issue Persists Ensure Shizuku is Properly Set Up: Double-check that Shizuku is correctly installed and configured in your environment. Check for Conflicting ADB Instances: Ensure no other ADB instances are running on your system that might be interfering with Termux. The "Forget device" function in Wireless Debugging can be used to unpair devices that are causing conflicts, such as the offline device in your case. Here's how to use it: Steps to Forget a Device Access Wireless Debugging Settings: Go to Settings > Developer options > Wireless debugging. View Paired Devices: Tap on Paired devices to see the list of devices paired for wireless debugging. Forget the Offline Device: Locate the offline device (e.g., localhost:35131). Tap on it and select Forget device. Verify Remaining Devices: Ensure only your active device (e.g., localhost:42405) remains paired. Reconnect Shizuku: Run Shizuku again: bash shizuku This should now connect without issues since the conflicting offline device is removed. Notes Forgetting the offline device will unpair it, so you will need to re-pair it later if needed. If the offline device reappears, it might be due to automatic reconnection settings; disable wireless debugging on the other device temporarily. Reinstall Shizuku: As a last resort, try reinstalling Shizuku in Termux to ensure there are no corrupted files or configurations.

…

On Mon, 7 Apr, 2025, 18:50 Docga1835, ***@***.***> wrote: I'm really having a hard time getting this offline device to go away. I don't even know what it is anymore as it doesn't match my watch. Debugging is only on with my phone. Every time it comes back. Is there a way to parse the results of adb devices and pick the online device? Screenshot_20250407_134819_Termux.jpg (view on web) <https://github.com/user-attachments/assets/74cb83b8-1b81-49bf-8d1c-2c3eb25529a3> — Reply to this email directly, view it on GitHub <#462 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BQCAKNNOWHMA5BE3TZ3GRIL2YK3HZAVCNFSM6AAAAABFSLMR22VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENZVGQ2DMMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Docga1835]

I am still new to Termux so I really appreciate all your advice here! I did setup a Linux Ubuntu distro following this article: https://medium.com/@scarletskynned/install-a-cli-linux-distro-in-your-android-phone-with-termux-84841a200f9e

Is this potentially what the other port could be? I am still learning how all this interacts.

[droid1413]

To address the persistent issue of the offline device reappearing and to ensure Shizuku connects only to the active device, you can parse the output of adb devices and dynamically select the online device. Here's how you can do it: Parsing adb devices to Select Online Device You can use a script to automate this process. Below is an example using a shell script in Termux: bash #!/bin/bash # Get the list of devices and filter for "device" (online) status ONLINE_DEVICE=$(adb devices | grep "device$" | awk '{print $1}') # Check if exactly one online device is found if [ $(echo "$ONLINE_DEVICE" | wc -l) -eq 1 ]; then echo "Connecting to device: $ONLINE_DEVICE" shizuku -s $ONLINE_DEVICE else echo "Error: Multiple or no online devices found." echo "Devices:" adb devices fi How It Works: List Devices: The script runs adb devices to get the list of connected devices. Filter Online Devices: It uses grep "device$" to find lines with the status "device" (online). Select the Device: If only one online device is found, it connects to that device using shizuku -s. Handle Errors: If multiple online devices or none are found, it displays an error and lists all devices. Steps to Use: Save the script as connect_shizuku.sh in your Termux environment. Make it executable: bash chmod +x connect_shizuku.sh Run the script: bash ./connect_shizuku.sh Additional Tips: Forget Offline Device: Use the "Forget device" option in Wireless Debugging settings for persistent offline entries. Kill ADB Cache: Restart ADB to clear cached connections: bash adb kill-server adb start-server Debugging Logs: Use adb logcat to check if any specific app or process is causing the offline device to reconnect. This script ensures Shizuku connects only to your phone (the active device), bypassing issues caused by the offline entry.

…

On Mon, 7 Apr, 2025, 18:54 VladiMiBeta, ***@***.***> wrote: The issue is that Shizuku is still trying to use ADB in a way that conflicts with the existing connections, even after you've disconnected the offline device. Steps to Correct the Issue Kill ADB Server: Run: bash adb kill-server Start ADB Server: Run: bash adb start-server Verify Devices: Run: bash adb devices Ensure only your phone (localhost:42405 device) is listed. If the offline device reappears, disconnect it again: bash adb disconnect localhost:35131 Repeat the adb devices command to verify. Start Shizuku with Correct Port: Run: bash shizuku -s localhost:42405 If the Issue Persists Ensure Shizuku is Properly Set Up: Double-check that Shizuku is correctly installed and configured in your environment. Check for Conflicting ADB Instances: Ensure no other ADB instances are running on your system that might be interfering with Termux. The "Forget device" function in Wireless Debugging can be used to unpair devices that are causing conflicts, such as the offline device in your case. Here's how to use it: Steps to Forget a Device Access Wireless Debugging Settings: Go to Settings > Developer options > Wireless debugging. View Paired Devices: Tap on Paired devices to see the list of devices paired for wireless debugging. Forget the Offline Device: Locate the offline device (e.g., localhost:35131). Tap on it and select Forget device. Verify Remaining Devices: Ensure only your active device (e.g., localhost:42405) remains paired. Reconnect Shizuku: Run Shizuku again: bash shizuku This should now connect without issues since the conflicting offline device is removed. Notes Forgetting the offline device will unpair it, so you will need to re-pair it later if needed. If the offline device reappears, it might be due to automatic reconnection settings; disable wireless debugging on the other device temporarily. Reinstall Shizuku: As a last resort, try reinstalling Shizuku in Termux to ensure there are no corrupted files or configurations. On Mon, 7 Apr, 2025, 18:50 Docga1835, ***@***.***> wrote: > I'm really having a hard time getting this offline device to go away. I > don't even know what it is anymore as it doesn't match my watch. Debugging > is only on with my phone. Every time it comes back. Is there a way to parse > the results of adb devices and pick the online device? > Screenshot_20250407_134819_Termux.jpg (view on web) > <https://github.com/user-attachments/assets/74cb83b8-1b81-49bf-8d1c-2c3eb25529a3> > > — > Reply to this email directly, view it on GitHub > <#462 (reply in thread)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BQCAKNNOWHMA5BE3TZ3GRIL2YK3HZAVCNFSM6AAAAABFSLMR22VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENZVGQ2DMMY> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >

[Docga1835]

My goal here his to have the script run at boot either with Termux:Boot, or in my case using MacroDroid. That part is settled but I just have to get the script to work. Originally, when I clicked on wireless debugging, it showed Shizuku, the localhost for Termux, my desktop, and "unknown" which I failed to remove until I removed everything. Now I just have shizuku and Termux paired with my phone. Unfortunately I am still getting the same results. I am really stuck!

[Docga1835]

I have tried running chmod +x connect_shizuku.sh the way you have written and I get No such file or directory. So I used the file path instead. Then when I try to run the script, I get Permission denied. Please help! I really want to find someway to get this to work. I really don't know why I am the only one with this problem. I've tried uninstalling, reinstalling, and repairing Shizuku and I always have this extra port which makes it unusable. Your help is appreciated.

[droid1413]

The script you provided is a great solution to dynamically handle multiple ADB devices and target the correct one for Shizuku. Here's an explanation and refinement of the script to ensure it works seamlessly: Key Features of the Script Dynamic Port Scanning: The script uses nmap to scan for open ports in the range 30000-50000 (commonly used by Wireless Debugging). Target Device Selection: It loops through the detected ports, attempts to connect via ADB, and sets the first successful connection as the target device. Error Handling: If no valid port is found, it notifies the user with an error message. Shizuku Start Command: Once a device is connected, it starts Shizuku using the appropriate ADB commands. Refined Script Here’s an improved version of your script with minor adjustments for clarity and robustness: bash #!/data/data/com.termux/files/usr/bin/bash # Define paths BASEDIR=$(dirname "${0}") BIN=/data/data/com.termux/files/usr/bin HOME=/data/data/com.termux/files/home DEX="${BASEDIR}/rish_shizuku.dex" # Exit if dex file is missing if [ ! -f "${DEX}" ]; then echo "Cannot find ${DEX}" exit 1 fi # Create Shizuku script tee "${BIN}/shizuku" > /dev/null << 'EOF' #!/data/data/com.termux/files/usr/bin/bash # Scan for open ports in the Wireless Debugging range ports=$(nmap -sT -p30000-50000 --open localhost | grep "open" | cut -f1 -d/) # Loop through detected ports to find a valid target device for port in ${ports}; do # Attempt to connect via ADB result=$(adb connect "localhost:${port}") # Check if connection was successful if [[ "$result" =~ "connected" || "$result" =~ "already connected" ]]; then target_device="localhost:${port}" echo "$result" # Reconnect offline devices (error correction) adb reconnect offline # Start Shizuku service on the target device adb -s "$target_device" shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh # Disable Wireless Debugging after starting Shizuku (optional) adb -s "$target_device" shell settings put global adb_wifi_enabled 0 exit 0 fi done # Error message if no valid port is found echo "ERROR: No valid device found! Is wireless debugging enabled?" exit 1 EOF # Create Rish script for Shizuku shell access tee "${BIN}/rish" > /dev/null << EOF #!/data/data/com.termux/files/usr/bin/bash export RISH_APPLICATION_ID="com.termux" /system/bin/app_process -Djava.class.path="${HOME}/rish_shizuku.dex" /system/bin --nice-name=rish rikka.shizuku.shell.ShizukuShellLoader "\${@}" EOF # Set permissions and copy dex file to home directory chmod +x "${BIN}/shizuku" "${BIN}/rish" cp -f "${DEX}" "${HOME}/rish_shizuku.dex" chmod -w "${HOME}/rish_shizuku.dex" How to Use the Script: Save the Script: Save this script as setup_shizuku.sh in Termux. Make It Executable: Run: bash chmod +x setup_shizuku.sh Execute the Setup: Run: bash ./setup_shizuku.sh Run Shizuku: After setup, you can start Shizuku by simply running: bash shizuku Key Adjustments: Error Handling: Added clear error messages when no valid devices are found. Wireless Debugging Disablement: Optionally disables Wireless Debugging after starting Shizuku to avoid conflicts. Improved Port Scanning: Ensures only open ports are considered. Troubleshooting: If you still encounter issues: Ensure nmap is installed in Termux: bash pkg install nmap Restart ADB services before running Shizuku: bash adb kill-server && adb start-server Verify Wireless Debugging is enabled on your phone and no other devices are paired. This script should dynamically handle multiple devices and ensure Shizuku connects only to the correct one!

…

On Mon, 7 Apr, 2025, 18:10 Juan David, ***@***.***> wrote: Everytime I run "shizuku", I get adb: more than one device/emulator so it fails every single time. I tried adding the prior suggestion from @juandvasquezp <https://github.com/juandvasquezp> adb reconnect offline, but I am still getting adb: more than one device/emulator. I do have 4 paired devices that I use on a regular basis. Any ideas to get around this issue? But this is a local script that you run in your phone, I find curious that you use your phone to connect to adb to other phones. Well, In that case I have a solution, I just came across a way to use an adb parameter to direct commands <https://developer.android.com/tools/adb#directingcommands> to a specific device with their ip and port. The parameter is adb -s <device> So I added a line that sets target_device="localhost:${port}" and that target device will be used for the next adb commands. Try again with this file: #!/data/data/com.termux/files/usr/bin/bash BASEDIR=$( dirname "${0}" ) BIN=/data/data/com.termux/files/usr/bin HOME=/data/data/com.termux/files/home DEX="${BASEDIR}/rish_shizuku.dex" # Exit if dex is not in the same directory if [ ! -f "${DEX}" ]; then echo "Cannot find ${DEX}" exit 1 fi # Create a Shizuku script file tee "${BIN}/shizuku" > /dev/null << 'EOF' #!/data/data/com.termux/files/usr/bin/bash # Make a list of open ports ports=$( nmap -sT -p30000-50000 --open localhost | grep "open" | cut -f1 -d/ ) # Go through the list of ports for port in ${ports}; do # Try to connect to the port, and save the result result=$( adb connect "localhost:${port}" ) # Check if the connection succeeded if [[ "$result" =~ "connected" || "$result" =~ "already" ]]; then # Set the target device target_device="localhost:${port}" # Show a message to a user echo "$result" # Add this to add reconnect to offline devices. Adds some error correction adb reconnect offline # Start Shizuku adb -s "$target_device" shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh # Disable wireless debugging, because it is not needed anymore adb -s "$target_device" shell settings put global adb_wifi_enabled 0 exit 0 fi done # If no working ports are found, give an error message to a user echo "ERROR: No port found! Is wireless debugging enabled?" exit 1 EOF # Set the dex location to a variable dex="${HOME}/rish_shizuku.dex" # Create a Rish script file tee "${BIN}/rish" > /dev/null << EOF #!/data/data/com.termux/files/usr/bin/bash export RISH_APPLICATION_ID="com.termux" /system/bin/app_process -Djava.class.path="${dex}" /system/bin --nice-name=rish rikka.shizuku.shell.ShizukuShellLoader "\${@}" EOF # Give execution permission to script files chmod +x "${BIN}/shizuku" "${BIN}/rish" # Copy dex to the home directory cp -f "${DEX}" "${dex}" # Remove dex write permission, because app_process cannot load writable dex chmod -w "${dex}" — Reply to this email directly, view it on GitHub <#462 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BQCAKNOAY5TGLLVQIBMX2AL2YKWQVAVCNFSM6AAAAABFSLMR22VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENZVGQYDSMA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Docga1835]

Finally got this file to execute, although unsurprisingly it didn't work for me. I found some kind of big with Android where Termux kept returning "Permission Denied" when executing a script file. I fixed it by denying storage permission to Termux and resembling it as outlined here: https://wiki.termux.com/wiki/Termux-setup-storage

When I ran your script, it just freezes midway and does nothing. This is what I got:

[juandvasquezp]

Let's just try deleting or commenting on the line with the reconnection

adb recconnect offline

[Docga1835]

Unfortunately it still freezes at the same point.

[CDM15y]

What about devices that don't have split-screen support

[DanHZY]

I am very confused and require assistance.
When i try to run my copy.sh at this directory
/storage/emulated/0/Shizuku/copy.sh it says permission denied.
I have already gave all file access
Tell me where should i put my file in order to make it work? Also ut is better if it is using termux to move the file as android 14 has a lot of restrictions. Thx

[Knud3]

Path begins with dot (it is relative path). Or type it without slash storage/shared/Shizuku/copy.sh

[juandvasquezp]

@Knud3 did you take a look at the new way to start shizuku starting the new version?

There might be some changes to be made to the script, because shizuku now starts with:

adb shell /data/app/~~gP7XGr9FL0iEWWEOuS80rA==/moe.shizuku.privileged.api-1Byyv3RqK59SAFuJNHK0SA==/lib/arm64/libshizuku.so

And this is just in my case, every case will be different.

[Knud3]

Done

[juandvasquezp]

@Knud3 I made this one, it worked:

It's essentially the same I've been using but changing the previous start command from:

adb -s "\$target_device" shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh

To:

adb -s "\$target_device" shell /data/app/~~gP7XGr9FL0iEWWEOuS80rA==/moe.shizuku.privileged.api-1Byyv3RqK59SAFuJNHK0SA==/lib/arm64/libshizuku.so

And some added modifications to check if we're in Android 14+, verifications that are present in the exported rish file

Here's my code running:

Here's my code:

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

BASEDIR=$( dirname "${0}" )
BIN=/data/data/com.termux/files/usr/bin
HOME=/data/data/com.termux/files/home
DEX="${BASEDIR}/rish_shizuku.dex"

# Exit if dex is not in the same directory
if [ ! -f "${DEX}" ]; then
  echo "Cannot find ${DEX}"
  exit 1
fi

if [ $(getprop ro.build.version.sdk) -lt 34 ]; then
  echo "This script is intended for Android 14+ devices only."
  exit 1
fi


# Create a Shizuku script file
tee "${BIN}/shizuku" > /dev/null << EOF
#!/data/data/com.termux/files/usr/bin/bash

# Make a list of open ports
ports=\$( nmap -sT -p30000-50000 --open localhost | grep "open" | cut -f1 -d/ )

# Go through the list of ports
for port in \${ports}; do

  # Try to connect to the port, and save the result
  result=\$( adb connect "localhost:\${port}" )

  # Check if the connection succeeded
  if [[ "\$result" =~ "connected" || "\$result" =~ "already" ]]; then

    # Show a message to a user
    echo "\${result}"
    
    # Add this to add recconnect to offline devices. This adds some error correction
    # When there's just one device connected, it will return nothing, so the code will also run regardless
    adb reconnect offline
    
    # Set the target device
    target_device="localhost:\${port}"
    
    # Show a message to a user with the target device
    echo "using device: \${target_device}"

    # Start Shizuku
    adb -s "\$target_device" shell /data/app/~~gP7XGr9FL0iEWWEOuS80rA==/moe.shizuku.privileged.api-1Byyv3RqK59SAFuJNHK0SA==/lib/arm64/libshizuku.so

    # Disable wireless debugging, because it is not needed anymore
    adb -s "\$target_device" shell settings put global adb_wifi_enabled 0
    
    # Stop the ADB server as it'll no longer be usefull
    adb kill-server

    exit 0
  fi
done

# If no working ports are found, give an error message to a user
echo "ERROR: No port found! Is wireless debugging enabled?"

exit 1
EOF

# Set the dex location to a variable
dex="${HOME}/.rish/rish_shizuku.dex"

# Create a Rish script file
tee "${BIN}/rish" > /dev/null << EOF
#!/system/bin/sh

export RISH_APPLICATION_ID="com.termux"

/system/bin/app_process -Djava.class.path="${dex}" /system/bin --nice-name=rish rikka.shizuku.shell.ShizukuShellLoader "\${@}"
EOF

# Give execution permission to script files
chmod +x "${BIN}/shizuku" "${BIN}/rish"

# Create the directory if it doesn't exist
mkdir -p "$(dirname "${dex}")"

# Copy dex to the home directory
cp -f "${DEX}" "${dex}"

# Remove dex write permission, because app_process cannot load writable dex
chmod 400 "${dex}"

# Check made in the original exported rish script
if [ -w "${dex}" ]; then
    echo "Cannot remove the write permission of "${dex}"."
    echo "You can copy to file to terminal app's private directory (/data/data/<package>, so that remove write permission is possible"
    exit 1
fi

[Blazko381]

@RikkaW pls add option to disable and enable start adb, because in 13.6.0 this always start wireless adb when WRITE_SECURE_SETTINGS is granted and wifi is on. Make this like on fork from @pixincreate

[juandvasquezp]

Interesting, I didn't know that. I just checked the Shizuku repo and I found this commit:

a9ee6ce

Which indicates that that feature is already on the original Shizuku app. And well, I just tested it and it worked. Shizuku started wireless debugging by itself, quite cool.

[guniens]

Interesting, I didn't know that. I just checked the Shizuku repo and I found this commit:

a9ee6ce

Which indicates that that feature is already on the original Shizuku app. And well, I just tested it and it worked. Shizuku started wireless debugging by itself, quite cool.

Hi
Can you tell me how do I get it to work?
I've done the manual setup using adb wireless, enabled the setting to start on boot but after a reboot shizuku is stopped and adb wireless turned off.
Do I need to allow WRITE_SECURE_SETTINGS to shizuku app via PC?
Thanks

[fakerat]

@RikkaW pls add option to disable and enable start adb, because in 13.6.0 this always start wireless adb when WRITE_SECURE_SETTINGS is granted and wifi is on. Make this like on fork from @pixincreate

Very intuitive! I'd love to see that implemented too.

[xpirad]

Interesting, I didn't know that. I just checked the Shizuku repo and I found this commit:
a9ee6ce
Which indicates that that feature is already on the original Shizuku app. And well, I just tested it and it worked. Shizuku started wireless debugging by itself, quite cool.

Hi Can you tell me how do I get it to work? I've done the manual setup using adb wireless, enabled the setting to start on boot but after a reboot shizuku is stopped and adb wireless turned off. Do I need to allow WRITE_SECURE_SETTINGS to shizuku app via PC? Thanks

Yes, you need to run

adb shell pm grant moe.shizuku.privileged.api android.permission.WRITE_SECURE_SETTINGS

And then when you are connected to a wifi, you can press start and shizuku will start directly.

Although, i hope that this can be done automatically on boot and without wifi.

[gaberilde]

Interesting, I didn't know that. I just checked the Shizuku repo and I found this commit:
a9ee6ce
Which indicates that that feature is already on the original Shizuku app. And well, I just tested it and it worked. Shizuku started wireless debugging by itself, quite cool.

Hi Can you tell me how do I get it to work? I've done the manual setup using adb wireless, enabled the setting to start on boot but after a reboot shizuku is stopped and adb wireless turned off. Do I need to allow WRITE_SECURE_SETTINGS to shizuku app via PC? Thanks

Yes, you need to run

adb shell pm grant moe.shizuku.privileged.api android.permission.WRITE_SECURE_SETTINGS

And then when you are connected to a wifi, you can press start and shizuku will start directly.

Although, i hope that this can be done automatically on boot and without wifi.

The "without WiFi" part will likely be impossible, it is a android restriction not a shizuku one but should be possible to auto start it on boot if connected to WiFi?

[alexytomi]

Suggestion: Use adb mds services to find device and connect instead of bruteforcing all the ports. This is also what Android Studio uses to my knowledge.

Downside here is that the adb termux ships doesn't have mdns :/