Adb chromebook
Author: h | 2025-04-24
Install ADB on your Chromebook without Crouton. As we said earlier, your Chromebook must be running on an x86_64 chipset to officially run ADB. To download and run the script for getting ADB Install ADB on your Chromebook without Crouton. As we said earlier, your Chromebook must be running on an x86_64 chipset to officially run ADB. To download and run the script for getting ADB
Enable ADB Debugging On Chromebook
First. Type the following: shell The prompt should change to read “chronos@localhost,” after which ADB and Fastboot should both be available to use like normal. Optional: What if it Doesn’t Work? When I first tested this out, I couldn’t get it to work. ADB could see my Android devices, but it never requested access. Turns out Chrome OS still runs an old version of ABD/Fastboot (because Google, right?) so you’ll need to update it. But that’s where the problem comes into play: you can’t just update ADB and Fastboot like on a normal computer. There is, however, a solution. If you have an Intel-based Chromebook, a script exists that will update ADB and Fastboot to the newest versions , as well as move them to the “correct” location. After that, everything should run fine. The script itself is pretty straightforward, and all the instructions are posted on the GitHub page. We suggest reading through them before you start so you know exactly what’s going on behind the scenes. Everything is also open source, so if you’d like to look through the code, you can do that too. With ADB and Fastboot updated and moved, both commands should work flawlessly. I tested this on a Pixelbook (i5, developer channel) by flashing a stock ROM onto my Nexus 6 and it was perfect. Fastboot ADB And Root Shell On A Chromebook How To Use ADB For Chrome ADB Tutorial: How To Use ADB Learn ADB & Fastboot Commands [ADB & Fastboot] Using Google's New Packages Install Android Debug Bridge (ADB) And Fastboot On Linux (Ubuntu 18.04) How To Enable ADB On Chrome OS How To Turn On Developer Mode On Your Chromebook Samsung Chromebook Fast Boot How To Measure The Performance Of Android Apps On A Chromebook Chrome OS Samsung Intel Fastboot
adb-chromebook/README.md at main homewood-flossmoor-dev/adb
For a long time, Chromebook users who also need access to the Android Debug Utility (ADB) and Fastboot for Android devices were left with one option: Crouton. Now, however, both ADB and Fastboot are included in Chrome OS. Here’s how to access them. First: Your Device Needs to be in Developer Mode First things first: ADB and Fastboot are technically considered “developer” tools, so your Chromebook will need to be in Developer Mode before you’ll be able to access them. Just to make it clear, we’re not talking about the developer channel here—every Chromebook can be put into a sort of “unlocked” mode that allows for deeper system access and tweaks. This is called Developer Mode. RELATED: How to Enable Developer Mode on Your Chromebook Fortunately, enabling Developer Mode is pretty straightforward and simple. There is one caveat, however: it will powerwash your device, so you’ll have to start over. The good news is that it’s a Chromebook, so this really shouldn’t take that long. If you’re cool with that, hit up our guide on enabling Developer Mode . That should get you rolling and ready to go in a matter of a few minutes. Second: Get Your Crosh On In order to use ADB and Fastboot on your Chromebook, you’ll need to use something called Crosh—short for “Chrome Shell.” Think of it as a sort of lightweight terminal just for Chrome OS. There are a couple of ways to access Crosh. To open it in a full browser window, just hit Ctrl+Alt+T on your keyboard. If you find yourself using Crosh fairly often, however, and would like it in a popout window (like a “real” terminal) there are two extensions you’ll need: Secure Shell and Crosh Window . With both installed, you’ll have a Crosh entry in your app drawer that launches Crosh in a nice, tidy little window. Personally, it’s my preferred method of using Crosh. With a Crosh window fired up, you’re ready to rock and roll. You can’t just jump straight into ADB and Fastboot, however—you’ll need to enter one command to get a shell windowHow to Use ADB and Fastboot on a Chromebook
With the power of ADB, you can do more than you think. This command-line tool works like a bridge between a connected computer and an Android device or emulator. Unfortunately, most users are familiar with only a small set of ADB commands. We have compiled a list of ADB commands with detailed explanations. With proper knowledge of the commands and their functions, you can explore the true potential of your Android device and perform basic and advanced tasks.Most users make use of just a small set of commands such as adb devices, fastboot oem unlock, fastboot flash recovery.img, and so on. Check out the following ADB commands list with a simplified explanation for each of them. ADB or Android Debug Bridge consists of 3 components:Client: the computer your Android device or emulator is connected to.Daemon: also known as ‘adbd‘ is the service that runs on your computer and Android device to facilitate command execution and acceptance between the devices.Server: this is the very software that handles the communication between the Client and the Daemon.Don’t Miss: Speed up Android with These ADB Commands List of ADB Commands with ExplanationBelow is a list of useful ADB commands with a brief description of their functions. ADB can help you debug your Android phone, reboot it, sideload APKs and flashable ZIPs, push and pull files, uninstall apps, and perform other tasks. Before you proceed, however, set up the SDK Platform-tools on your computer or install the aShell Terminal app to run ADB commands on your Android device.adbGet the ADB version and all possible commands associated with ADB.adb -sRedirect commands to a specific device when many devices are connected.adb -s adb -dThis command directs the command to a device connected via USB.adb –d adb -eUse this command to direct ADB commands to a connected emulator.adb –e adb devicesThis is one of the most used ADB commands to check the list of Android devices connected to your computer. adb devices -lList connected devices by model or product number.adb devices //show devices attachedThis is similar to the ‘adb devices’ command that shows you the list of Android devices and emulators that are connected to your computer.adb connect ip-address-of-deviceFind out and connect the IP address of your device to your PC. You can use this ADB command to set up ADB over Wi-Fi.adb helpDisplays the help documentation on all ADB commands.adb rootRestarts adbd with root permissions.adb versionFind out the version of the ADB driver installed on your computer.adb rebootReboot your Android phone or tablet into the bootloader, fastboot, or recovery mode.adb reboot bootloaderReboot your Android device in the Fastboot or Bootloader Mode. The command is often used when you want to flash the factory images or a custom recovery.adb reboot downloadBoot Samsung devices into the Download Mode or Odin Mode.adb reboot recoveryReboot your device into Android Recovery mode.adb installUsually, we transfer an APK file to our Android device and install it via File Manager. This command makes it easy to sideload APK files directly from your computer. To. Install ADB on your Chromebook without Crouton. As we said earlier, your Chromebook must be running on an x86_64 chipset to officially run ADB. To download and run the script for getting ADB Install ADB on your Chromebook without Crouton. As we said earlier, your Chromebook must be running on an x86_64 chipset to officially run ADB. To download and run the script for getting ADBChromebook and ADB : r/termux - Reddit
The first version of Chrome OS 75 Canary Channel landed a few days ago and it addresses a key functionality gap for Linux containers: USB device support. We knew this feature was in the works as the Stable Channel of Chrome OS 73 brought a menu option for USB Device management. while Chrome OS 72 added USB storage for Linux apps.Keith Myers noted the addition of USB device support for Linux on a Chromebook and did some testing with his 3D Printer, an Arduino board and a Intel Movidius Compute Stick. This feature is important for those who want to control, pass or read data to some type of external USB device from the Linux container. Keith noted some functions that Chrome OS 75 breaks as well, which is to be expected in the fast-changing Canary channel.Since I dabble with small computing devices myself – my CS group is extending a “pancreas in the cloud” project using a Raspberry Pi, for example – I decided to test some additional features that would be super important for many folks: the Android Debug Bridge (ADB) that lets you modify an Android phone or tablet to install custom software or recovery images.Chrome OS 75 isn’t yet available on the Dev Channel, so I took the plunge of putting a supported Chromebook in Developer Mode and installed Chrome OS 75; you can see if your device has access to this version here.To use the new USB device feature, you also have to enable both chrome://flags/#crostini-usb-allow-unsupported and chrome://flags/#crostini-usb-support, which I did after upgrading to Chrome OS 75.After my browser restarted, I went into my Linux container and I connected my Google Pixel 3XL to the Chromebook. This popup notification to connect appeared and chose to connect the device. Running the lsusb command in Linux shows the new device attached:Now that the Linux container saw the USB device – my Pixel 3XL in this case, I ran a few ADB commands, since I already have them installed as part of Android Studio. Sure enough: Whatever ADB functions I used to do on a PC and Mac can now be done right from my Chromebook!The timing of this new feature coincides nicely with next month’s Google I/O developer event even though I don’t think USB device support in Linux on Chromebooks won’t likely arrive in the Stable channel until after I/O. Last year, Google said that itWhy can't i enable ADB debugging on Chromebook? - Chromebook
Would officially support Android Studio for Android app development on Chromebooks in 2019, which includes ADB support. The company has been working on that since the last I/O event, so I anticipate an on-stage announcement that Android developers will have a fully working environment on Chromebooks within weeks of Google I/O.Remember, if you want to try this by moving to the Canary Channel, you will see bugs. And to access Canary, you first have to put your Chromebook into Developer Mode, which disables some Chrome OS security features and wipes all local data, so attempt this at your own risk. Most people would be better off waiting until USB device support arrives in the Dev Channel, so I’ll be sure to share news of when that happens. After spending 15 years in IT at Fortune 100 companies, Kevin turned a hobby into a career and began covering mobile technology in 2003. He writes daily on the industry and has co-hosted the weekly MobileTechRoundup podcast since 2006. His writing has appeared in print (The New York Times, PC Magazine and PC World) and he has been featured on NBC News in Philadelphia.How to install ADB and Fastboot on an x86_64 Chromebook
How to Use ADB Commands to Bypass FRPDownload the latest ADB Installer setup file from the Internet.Run the adb-setup.exe and type ‘Y’ and follow the onscreen instructions to install the ADB and fastboot driver.Power on your device normally and connect it to your PC using USB cable.Go the folder where the adb drivers are installed. (In most cases they are installed in the C Drive (Windows Drive))Hold down Shift, right-click anywhere blank in the ADB folder, and select "Open command window here".To remove FRP on Samsung devices via ADB commands: Type the following ADB FRP bypass command into the Command Prompt window one by one hitting Enter after each line.adb shell am start -n com.google.android.gsf.login/adb shell am start -n com.google.android.gsf.login.LoginActivityadb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1To remove FRP on Other Brands / MTK /SPD via ADB commands: Type the following ADB FRP bypass command into the Command Prompt window and hit Enter after each line.adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1When the commands are all executed, the FRP lock will be removed from your device. That is how to use ADB FRP bypass to remove the lock from your phone.. Install ADB on your Chromebook without Crouton. As we said earlier, your Chromebook must be running on an x86_64 chipset to officially run ADB. To download and run the script for getting ADB Install ADB on your Chromebook without Crouton. As we said earlier, your Chromebook must be running on an x86_64 chipset to officially run ADB. To download and run the script for getting ADBComments
First. Type the following: shell The prompt should change to read “chronos@localhost,” after which ADB and Fastboot should both be available to use like normal. Optional: What if it Doesn’t Work? When I first tested this out, I couldn’t get it to work. ADB could see my Android devices, but it never requested access. Turns out Chrome OS still runs an old version of ABD/Fastboot (because Google, right?) so you’ll need to update it. But that’s where the problem comes into play: you can’t just update ADB and Fastboot like on a normal computer. There is, however, a solution. If you have an Intel-based Chromebook, a script exists that will update ADB and Fastboot to the newest versions , as well as move them to the “correct” location. After that, everything should run fine. The script itself is pretty straightforward, and all the instructions are posted on the GitHub page. We suggest reading through them before you start so you know exactly what’s going on behind the scenes. Everything is also open source, so if you’d like to look through the code, you can do that too. With ADB and Fastboot updated and moved, both commands should work flawlessly. I tested this on a Pixelbook (i5, developer channel) by flashing a stock ROM onto my Nexus 6 and it was perfect. Fastboot ADB And Root Shell On A Chromebook How To Use ADB For Chrome ADB Tutorial: How To Use ADB Learn ADB & Fastboot Commands [ADB & Fastboot] Using Google's New Packages Install Android Debug Bridge (ADB) And Fastboot On Linux (Ubuntu 18.04) How To Enable ADB On Chrome OS How To Turn On Developer Mode On Your Chromebook Samsung Chromebook Fast Boot How To Measure The Performance Of Android Apps On A Chromebook Chrome OS Samsung Intel Fastboot
2025-04-04For a long time, Chromebook users who also need access to the Android Debug Utility (ADB) and Fastboot for Android devices were left with one option: Crouton. Now, however, both ADB and Fastboot are included in Chrome OS. Here’s how to access them. First: Your Device Needs to be in Developer Mode First things first: ADB and Fastboot are technically considered “developer” tools, so your Chromebook will need to be in Developer Mode before you’ll be able to access them. Just to make it clear, we’re not talking about the developer channel here—every Chromebook can be put into a sort of “unlocked” mode that allows for deeper system access and tweaks. This is called Developer Mode. RELATED: How to Enable Developer Mode on Your Chromebook Fortunately, enabling Developer Mode is pretty straightforward and simple. There is one caveat, however: it will powerwash your device, so you’ll have to start over. The good news is that it’s a Chromebook, so this really shouldn’t take that long. If you’re cool with that, hit up our guide on enabling Developer Mode . That should get you rolling and ready to go in a matter of a few minutes. Second: Get Your Crosh On In order to use ADB and Fastboot on your Chromebook, you’ll need to use something called Crosh—short for “Chrome Shell.” Think of it as a sort of lightweight terminal just for Chrome OS. There are a couple of ways to access Crosh. To open it in a full browser window, just hit Ctrl+Alt+T on your keyboard. If you find yourself using Crosh fairly often, however, and would like it in a popout window (like a “real” terminal) there are two extensions you’ll need: Secure Shell and Crosh Window . With both installed, you’ll have a Crosh entry in your app drawer that launches Crosh in a nice, tidy little window. Personally, it’s my preferred method of using Crosh. With a Crosh window fired up, you’re ready to rock and roll. You can’t just jump straight into ADB and Fastboot, however—you’ll need to enter one command to get a shell window
2025-04-24The first version of Chrome OS 75 Canary Channel landed a few days ago and it addresses a key functionality gap for Linux containers: USB device support. We knew this feature was in the works as the Stable Channel of Chrome OS 73 brought a menu option for USB Device management. while Chrome OS 72 added USB storage for Linux apps.Keith Myers noted the addition of USB device support for Linux on a Chromebook and did some testing with his 3D Printer, an Arduino board and a Intel Movidius Compute Stick. This feature is important for those who want to control, pass or read data to some type of external USB device from the Linux container. Keith noted some functions that Chrome OS 75 breaks as well, which is to be expected in the fast-changing Canary channel.Since I dabble with small computing devices myself – my CS group is extending a “pancreas in the cloud” project using a Raspberry Pi, for example – I decided to test some additional features that would be super important for many folks: the Android Debug Bridge (ADB) that lets you modify an Android phone or tablet to install custom software or recovery images.Chrome OS 75 isn’t yet available on the Dev Channel, so I took the plunge of putting a supported Chromebook in Developer Mode and installed Chrome OS 75; you can see if your device has access to this version here.To use the new USB device feature, you also have to enable both chrome://flags/#crostini-usb-allow-unsupported and chrome://flags/#crostini-usb-support, which I did after upgrading to Chrome OS 75.After my browser restarted, I went into my Linux container and I connected my Google Pixel 3XL to the Chromebook. This popup notification to connect appeared and chose to connect the device. Running the lsusb command in Linux shows the new device attached:Now that the Linux container saw the USB device – my Pixel 3XL in this case, I ran a few ADB commands, since I already have them installed as part of Android Studio. Sure enough: Whatever ADB functions I used to do on a PC and Mac can now be done right from my Chromebook!The timing of this new feature coincides nicely with next month’s Google I/O developer event even though I don’t think USB device support in Linux on Chromebooks won’t likely arrive in the Stable channel until after I/O. Last year, Google said that it
2025-04-06Would officially support Android Studio for Android app development on Chromebooks in 2019, which includes ADB support. The company has been working on that since the last I/O event, so I anticipate an on-stage announcement that Android developers will have a fully working environment on Chromebooks within weeks of Google I/O.Remember, if you want to try this by moving to the Canary Channel, you will see bugs. And to access Canary, you first have to put your Chromebook into Developer Mode, which disables some Chrome OS security features and wipes all local data, so attempt this at your own risk. Most people would be better off waiting until USB device support arrives in the Dev Channel, so I’ll be sure to share news of when that happens. After spending 15 years in IT at Fortune 100 companies, Kevin turned a hobby into a career and began covering mobile technology in 2003. He writes daily on the industry and has co-hosted the weekly MobileTechRoundup podcast since 2006. His writing has appeared in print (The New York Times, PC Magazine and PC World) and he has been featured on NBC News in Philadelphia.
2025-04-02Acquired from and MacFly contain the: GPS Setter, GPS Joystick, and Hide Mock Location. MacFly demonstrated how the tool could be used to spoof the location of a particular modified coordinate, along with a victim’s pre-recorded route, which allows a threat actor to imitate a client in movement (e.g., driving in a taxi). During installation, HUNTER identified the following modules:adb push !workspace.novabackup /storage/emulated/0/ adb push data /storage/emulated/0 adb push 01_Busybox.zip /storage/emulated/0 adb push 02_Propsf.zip /storage/emulated/0/ adb push 03_ACC.zip /storage/emulated/0/ adb push 04_Font_Manager.zip /storage/emulated/0/ adb push 05_hide-usb-debugging.zip /storage/emulated/0/ adb push 06_Riru.zip /storage/emulated/0/ adb push 07_safetynet.zip /storage/emulated/0/ adb push 09_LSPosed.zip /storage/emulated/0/ adb push 10_momohider.zip /storage/emulated/0/ adb push 08_overlayfs.zip /storage/emulated/0/ adb push 11_riru-unshare_a10.zip /storage/emulated/0/ adb push 12_Storage.zip /storage/emulated/0/ adb push 12_sui.zip /storage/emulated/0/ adb push 13_AppDataIsolation.zip /storage/emulated/0/ adb push 14_liboemcrypto_disabler.zip /storage/emulated/0/ adb push 15_fakeencryption.zip /storage/emulated/0/ adb push 16_hidemodified_init.rc.zip /storage/emulated/0/ adb push 17_resetsensitiveprops.zip /storage/emulated/0/ adb push 18_BlockAds.zip /storage/emulated/0/ adb push 19_storage_iso.zip /storage/emulated/0/ adb push app-release.apk /storage/emulated/0/ adb push Hidemyapplist.json /storage/emulated/0/ adb push base.settings /storage/emulated/0/ adb push base_2.12_premium.settings /storage/emulated/0/ adb push LSPosed.lsp.gz /storage/emulated/0/ rem adb shell su -c pm disable com.coloros.phonemanager rem shell su -c pm disable com.oppo.ota rem shell su -c pm disable com.nearme.romupdate rem shell su -c pm disable com.coloros.sau adb shell su -c setenforce 1 adb shell su -c magisk --install-module /storage/emulated/0/01_Busybox.zip adb shell su -c magisk --install-module /storage/emulated/0/02_Propsf.zip adb shell su -c magisk --install-module /storage/emulated/0/03_ACC.zip adb shell su -c magisk --install-module /storage/emulated/0/04_Font_Manager.zip adb shell su -c magisk --install-module /storage/emulated/0/05_hide-usb-debugging.zip adb shell su -c magisk --install-module /storage/emulated/0/06_Riru.zip adb shell su -c magisk --install-module /storage/emulated/0/07_safetynet.zip adb shell su -c magisk --install-module /storage/emulated/0/09_LSPosed.zip adb shell su -c magisk --install-module /storage/emulated/0/10_momohider.zip adb shell su -c magisk --install-module /storage/emulated/0/11_riru-unshare_a10.zip adb shell su -c magisk --install-module /storage/emulated/0/12_Storage.zip adb shell su -c magisk --install-module /storage/emulated/0/08_overlayfs.zip adb shell su -c magisk --install-module /storage/emulated/0/12_sui.zip adb shell su -c magisk --install-module /storage/emulated/0/13_AppDataIsolation.zip adb shell su -c magisk --install-module /storage/emulated/0/14_liboemcrypto_disabler.zip adb shell su -c magisk --install-module /storage/emulated/0/15_fakeencryption.zip adb shell su -c magisk --install-module /storage/emulated/0/16_hidemodified_init.rc.zip adb shell su -c magisk --install-module /storage/emulated/0/17_resetsensitiveprops.zip adb shell su -c magisk --install-module /storage/emulated/0/18_BlockAds.zip adb shell su -c magisk --install-module /storage/emulated/0/19_storage_iso.zip echo press for end install pause adb shell su -c magiskhide add com.google.android.gms adb shell su -c magiskhide add com.google.android.gms.unstable adb shell su -c magiskhide add com.byxiaorun.detector adb shell rm /storage/emulated/0/01_Busybox.zip adb shell rm /storage/emulated/0/02_Propsf.zip adb shell rm /storage/emulated/0/03_ACC.zip adb shell rm /storage/emulated/0/04_Font_Manager.zip adb shell rm /storage/emulated/0/05_hide-usb-debugging.z adb shell rm /storage/emulated/0/06_Riru.zip adb shell rm /storage/emulated/0/07_safetynet.zip adb shell rm /storage/emulated/0/09_LSPosed.zip adb shell rm /storage/emulated/0/10_momohider.zip adb shell rm /storage/emulated/0/11_riru-unshare_a10.zip adb shell rm /storage/emulated/0/12_Storage.zip adb shell rm /storage/emulated/0/05_hide-usb-debugging.zip adb shell rm /storage/emulated/0/!workspace.novabackup adb shell rm /storage/emulated/0/08_overlayfs.zip adb shell rm /storage/emulated/0/12_sui.zip adb shell rm /storage/emulated/0/13_AppDataIsolation.zip adb shell rm /storage/emulated/0/14_liboemcrypto_disabler.zip adb shell rm /storage/emulated/0/15_fakeencryption.zip adb shell rm /storage/emulated/0/16_hidemodified_init.rc.zip adb shell rm /storage/emulated/0/19_storage_iso.zip adb shell rm /storage/emulated/0/18_BlockAds.zip adb shell rm /storage/emulated/0/17_resetsensitiveprops.zipThe actors deploy LSPosed, and HideMyApp (HMA), with configuration settings defined in the "Hidemyapplist.json" file. In addition to that, the package drops "base.settings" and "base_2.12_premium.settings" in encrypted form. Recovered "Hidemyapplist.json" by our reverse engineers contains the following list of supported applications from major online
2025-04-12To upload them onto a device.app: additional softwareArchitecture (previously - Xposed) - unofficial Android framework made for changing codes of system apps ( the author of mobile antidetects uses fork Magisk Delta from HuskyDG - Magisk Delta contains a magiskhide module allowing to hide root from selected apps (which doesn't exist in the official package). The main differences between Magisk Delta from the official version of Magisk are provided below:InstallationTo install the solution on the device, you must first unlock the bootloader and install the driver to connect the device to the PC. Check the connection with the adb devices command.Go to the folder sideload Install MagiskDelta: app-release.apk, to get the root root. Подробнее that Magisk has been successfully installed and has the status Installed:Launch batch script !install.batContent of !install.bat: @echo offadb push !workspace.novabackup /storage/emulated/0/adb push data /storage/emulated/0adb push 01_Busybox.zip /storage/emulated/0 adb push 02_Propsf.zip /storage/emulated/0/adb push 03_ACC.zip /storage/emulated/0/adb push 04_Font_Manager.zip /storage/emulated/0/adb push 05_hide-usb-debugging.zip /storage/emulated/0/adb push 06_Riru.zip /storage/emulated/0/adb push 07_safetynet.zip /storage/emulated/0/adb push 09_LSPosed.zip /storage/emulated/0/adb push 10_momohider.zip /storage/emulated/0/adb push 08_overlayfs.zip /storage/emulated/0/adb push 11_riru-unshare_a10.zip /storage/emulated/0/adb push 12_Storage.zip /storage/emulated/0/adb push 12_sui.zip /storage/emulated/0/adb push 13_AppDataIsolation.zip /storage/emulated/0/adb push 14_liboemcrypto_disabler.zip /storage/emulated/0/adb push 15_fakeencryption.zip /storage/emulated/0/adb push 16_hidemodified_init.rc.zip /storage/emulated/0/adb push 17_resetsensitiveprops.zip /storage/emulated/0/adb push 18_BlockAds.zip /storage/emulated/0/adb push 19_storage_iso.zip /storage/emulated/0/adb push app-release.apk /storage/emulated/0/adb push Hidemyapplist.json /storage/emulated/0/adb push base.settings /storage/emulated/0/adb push base_2.12_premium.settings /storage/emulated/0/adb push LSPosed.lsp.gz /storage/emulated/0/rem adb shell su -c pm disable com.coloros.phonemanagerrem shell su -c pm disable com.oppo.otarem shell su -c pm disable com.nearme.romupdaterem shell su -c pm disable com.coloros.sauadb shell su -c setenforce 1adb shell su -c magisk --install-module /storage/emulated/0/01_Busybox.zip adb shell su -c magisk --install-module /storage/emulated/0/02_Propsf.zipadb shell su -c magisk --install-module /storage/emulated/0/03_ACC.zipadb shell su -c magisk --install-module /storage/emulated/0/04_Font_Manager.zipadb shell su -c magisk --install-module /storage/emulated/0/05_hide-usb-debugging.zipadb shell su -c magisk --install-module /storage/emulated/0/06_Riru.zipadb shell su -c magisk --install-module /storage/emulated/0/07_safetynet.zipadb shell su -c magisk --install-module /storage/emulated/0/09_LSPosed.zipadb shell su -c magisk --install-module /storage/emulated/0/10_momohider.zipadb shell su -c magisk --install-module /storage/emulated/0/11_riru-unshare_a10.zipadb shell su -c magisk --install-module /storage/emulated/0/12_Storage.zipadb shell su -c magisk --install-module /storage/emulated/0/08_overlayfs.zipadb shell su -c magisk --install-module /storage/emulated/0/12_sui.zipadb shell su -c magisk --install-module /storage/emulated/0/13_AppDataIsolation.zipadb shell su -c magisk --install-module /storage/emulated/0/14_liboemcrypto_disabler.zipadb shell su -c magisk --install-module /storage/emulated/0/15_fakeencryption.zipadb shell su -c magisk --install-module /storage/emulated/0/16_hidemodified_init.rc.zipadb shell su -c magisk --install-module /storage/emulated/0/17_resetsensitiveprops.zipadb shell su -c magisk --install-module /storage/emulated/0/18_BlockAds.zipadb shell su -c magisk --install-module /storage/emulated/0/19_storage_iso.zipecho press for end installpause adb shell su -c magiskhide add com.google.android.gms adb shell su -c magiskhide add com.google.android.gms.unstableadb shell su -c magiskhide add com.byxiaorun.detectoradb shell rm /storage/emulated/0/01_Busybox.zip adb shell rm /storage/emulated/0/02_Propsf.zip adb shell rm /storage/emulated/0/03_ACC.zip adb shell rm /storage/emulated/0/04_Font_Manager.zip adb shell rm /storage/emulated/0/05_hide-usb-debugging.zadb shell rm /storage/emulated/0/06_Riru.zip adb shell rm /storage/emulated/0/07_safetynet.zip adb shell rm /storage/emulated/0/09_LSPosed.zip adb shell rm /storage/emulated/0/10_momohider.zip adb shell rm /storage/emulated/0/11_riru-unshare_a10.zipadb shell rm /storage/emulated/0/12_Storage.zip adb shell rm /storage/emulated/0/05_hide-usb-debugging.zip adb shell rm /storage/emulated/0/!workspace.novabackup adb shell rm /storage/emulated/0/08_overlayfs.zipadb shell rm /storage/emulated/0/12_sui.zipadb shell rm /storage/emulated/0/13_AppDataIsolation.zipadb shell rm /storage/emulated/0/14_liboemcrypto_disabler.zipadb shell rm /storage/emulated/0/15_fakeencryption.zipadb shell rm /storage/emulated/0/16_hidemodified_init.rc.zipadb shell rm /storage/emulated/0/19_storage_iso.zipadb shell rm /storage/emulated/0/18_BlockAds.zipadb shell rm /storage/emulated/0/17_resetsensitiveprops.zipThis script will install all the necessary Magisk modules to the device. Note that not all paths used in the script correspond to the data in the sideload directory. Some are missing; others have changed
2025-04-08