(Power up normally) → (System with NO Magisk).If you decide to boot into the actual recovery mode, long press volume up until you see the recovery screen.Īs a summary, after installing Magisk in recovery (starting from power off): As soon as you press the key combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. 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. Reboot and launch Magisk app (you will see a stub Magisk app if you have wiped your data use it to bootstrap to a complete Magisk app), and you will see a prompt asking for environment fix click and wait for the reboot.(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 (note that it may wipe your data).Where should be _a or _b or empty depending on your device Flash the patched boot/init_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 init_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/init_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/init_boot/recovery image to your device.A boot.img, init_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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |