- Jan 6, 2023
so in this step, when you patched the image with 24.3 version, did you rename it to magisk_patched.img? Did you 'copy' or 'cut paste' it to the platform-tools folder?I just received an Ulefone armor 18t and I'm trying to get the phone rooted through a magisk patched boot image. Whenever I attempt to flash the patched image, the phone always ends up bootlooping and gives me the 'android system may be corrupt' message. I've tried flashing an empty vbmeta in order to try to disable secure boot, but it still isn't working.
Does anyone have any other suggestions or have any ideas as to what could be causing my phone to not boot?
Posted this on reddit; just reposting this for more exposure
EDIT: I managed to root my phone by patching my boot.img with an older version of magisk (24.3) and then updating to v25 after.
After this step and updating the magisk to version 25, did you repatch the boot.img and renamed that one to magisk_patched.img and let it sit in the internal memory?
If you 'cut paste' the older version patch to platform-tools folder and let the newer version patch sit in the internal memory, did it create a bootloop issue?
This is where it is confusing.
In my phone the older version patched img file and newer version patched img file were named as magisk_patched_1vukl.img (older version patch) and magisk_patched_2500ihs.img (newer version patch)
What should I do? Should I rename magisk_patched_1vukl to magisk_patched.img and cut paste it in platform-tools folder and then rename the magisk_patched_2500ihs.img to magisk_patched.img and continue with the process ahead? I am apprehensive of the bootloop error due to 2 patched files being from different versions of the magisk.