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 sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh
   
       # 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
   
   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!

[Ermageeerd]

I just set "adb_wifi_enabled" to 1 at the start of the script!

@Ermageeerd How are you setting that? Can you share the full script?

Its just the same script with

# Enable wireless debugging, because it is needed
    adb shell settings put global adb_wifi_enabled 1

before it creates the script file, likely wont work for you under normal conditioms, and i dunno what condition could allow this, as it still redisables wireless debugging. Maybe my SystemUI Tuner config. It never did anything to help start it manually tho, so I doubt it.

[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)

[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

[Knud3]

It can... But only after manually enabling it in the first place. If you find a way to do it otherwise, please, educate me, and I update the instructions.

[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

[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.

#!/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

    # Start Shizuku
    adb shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh

    # 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

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}"

[onoakino]

Hi Juan! Thanks! I tried your code. I think it works, but it really didn't help me bypass the manual process of starting shizuku. I recorded my termux session while trying to execute shizuku.

Wheb I said the OP scriot worked for me, I meant that after following the OP, i found out that I don't have to manually input the pairing code everytime I try to start Shizuku app. I just press the start button, wait for the process log to exit, and then the service is ready and running. I didn't even have to open Termux and execute the shizuku command from it.

It seems that the script is failing to call shizuku service to start from the command line. IDK, I'm not an expert as scripting. Any ideas?

[juandvasquezp]

Yeah, it isn't working there. My guess is because you don't have localhost in the list of paired devices inside wireless debugging.

Try to repeat step 5 of the main tutorial:

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

At least for me, it was once time only, that I had to pair termux with wireless debugging, and it'll be added to that list so that it'll connect every time.

[onoakino]

Which one to use? The one in the box, or the one in the circle?

[juandvasquezp]

Sure, you use the one from below but not exactly that one.

adb pair localhost:<port> <pairing _code>

Port being what's after the ip and the pairing code is the big one.

So, in that screenshot, the case is:

adb pair localhost:37197 466835