- SAMSUNG ADB TOOL HOW TO
- SAMSUNG ADB TOOL APK
- SAMSUNG ADB TOOL INSTALL
- SAMSUNG ADB TOOL PATCH
A quick search online should easily get you this info. Each device model has its own key combo to boot into recovery, as an example for Galaxy S10 it is (Power + Bixby + Volume Up). When Magisk hijacks the recovery, there is a special mechanism to allow you to actually boot into recovery mode. For these devices, you will have to reboot to recovery every time you want Magisk enabled. In the case when your device does not have ramdisk in boot images, Magisk has no choice but to hijack the recovery partition.
If you insist on using custom recoveries, rename the Magisk APK to uninstall.zip and flash it like any other ordinary flashable zip. The easiest way to uninstall Magisk is directly through the Magisk app.
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:įastboot flash vbmeta -disable-verity -disable-verification vbmeta.img. Flash the patched boot/recovery image to your device.įor most devices, reboot into fastboot mode and flash with command:įastboot flash boot /path/to/magisk_patched.img orįastboot flash recovery /path/to/magisk_patched.img. Start the installation, and copy the patched image to your PC using ADB:Īdb pull /sdcard/Download/magisk_patched_.img. Choose “Select and Patch a File” in method, and select the boot/recovery image. If your device does NOT have a separate vbmeta partition, check the “Patch vbmeta in boot image” option. If you are patching a recovery image, check the “Recovery Mode” option. Press the Install button in the Magisk card. 
Copy the boot/recovery image to your device. A boot.img or recovery.img based on (1). Whether your device has a separate vbmeta partition. 
Quick recap, at this point, you should have known and prepared:
Otherwise, your device does not have a separate vbmeta partition. If you find vbmeta, vbmeta_a, or vbmeta_b, then yes, your device has a separate vbmeta partition. You can also check by connecting your device to a PC and run the command:. If your official firmware package contains vbmeta.img, then yes, your device has a separate vbmeta partition. Next, we need to know whether your device has a separate vbmeta partition. You should be able to extract the file you need from official firmware packages or your custom ROM zip. If your device does NOT have boot ramdisk, get a copy of the recovery.img. If your device has boot ramdisk, get a copy of the boot.img. If you are using a Samsung device that is launched with Android 9.0 or higher, you can now jump to its own section. Fortunately, as far as we know, only some Xiaomi devices are known to have this property, so most people can simply ignore this piece of information.) 
There is no way to detect this, so the only way to know for sure is to actually try. In this case, you will have to follow the instructions as if your device’s boot partition does include ramdisk. (Unfortunately, there are exceptions as some devices’ bootloader accepts ramdisk even if it shouldn’t. If your device does not have boot ramdisk, read the Magisk in Recovery section before continuing. The result of Ramdisk determines whether your device has ramdisk in the boot partition.
Your device’s bootloader has to be unlockedĭownload and install the latest Magisk app. If you plan to also install custom kernels, install it after Magisk. This tutorial assumes you understand how to use adb and fastboot. The following tutorial is only for the initial installation. If you already have Magisk installed, it is strongly recommended to upgrade directly via the Magisk app using its “Direct Install” method.
0 kommentar(er)
