π» => the device running adb
(usually a PC)
π± => the device where Magisk is going to be installed (usually a Phone or Tablet)
- π± Install Magisk App
- π» Download Magisk
- π» Rename .apk to .zip
- π» Reboot device in Sideload mode
- π» Sideload Magisk
- π± Complete the Magisk installation (if needed)
The app can be found on F-Droid:
- π± if an older version is installed, update it directly from the Magisk app
Download the latest Magisk .apk
from the official GitHub repo:
mv Magisk.VERSION-NR.apk Magisk.VERSION-NR.apk.zip
sudo adb reboot sideload
- π± USB debugging mode must be active (under Settings > Developer Options)
- π± the device running
adb
(π») must be approved on the receiving device (π±), else no actions will be taken - π» in case something goes wrong, kill the running server and start over
sudo adb kill-server
sudo adb sideload /path/to/Magisk.VERSION-NR.apk.zip
- π± signature verification might fail, I bypass it to install Magisk anyway
- π»
adb
might show something likeTotal xfer: 0.90x
, this is fine - π± reboot to system once done
Magisk might need to be re-installed "internally".
This can be done directly from the app.
- π± a popup will appear
- π± re-install Magisk using the recommended option
- π± once done a reboot option will be shown, reboot
Thank you very much! This saved me after installing (not yet rebooting!) an OTA-update of /e/OS custom ROM killed the running system. So I could not patch the inactive slot with the Magisk App. Your description worked perfect. β€οΈ
The phone was still reachable via adb. (At the second time I used this procedure I had to lock and unlock the phone to have it reachable with adb.) I first rebooted to sideload mode and installed Magisk as described and afterwards rebooted to the new system.