The magisk apk, when flashed in TWRP flashes as normal but the app does not show up in the ROM, and the phone doesn't get rooted.
I had this problem on both ArrowOS and Syberia OS now, and I clean flashed both times directly from MIUI.
Can anyone help me out with this?
Install the magisk app
Rename magisk.apk to magisk.zip (only change the last 3 letters) and install it from TWRP-recovery.
zhyylz0201 said:
Install the magisk app
Click to expand...
Click to collapse
I already tried, this happened -
Iceman66 said:
Rename magisk.apk to magisk.zip (only change the last 3 letters) and install it from TWRP-recovery.
Click to expand...
Click to collapse
It didn't work either, when I open magisk app it shows this -
Download Canary version of Magisk (23001) from Github: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Rename app-debug.apk to app-debug.zip and flash it with TWRP
Iceman66 said:
Download Canary version of Magisk (23001) from Github: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Rename app-debug.apk to app-debug.zip and flash it with TWRP
Click to expand...
Click to collapse
No change
Other method is patching boot.img with magisk manager. You can find some tutorials with google. Extract the boot.img from ROM.zip, put in on internal memory of your phone and patch it with magisk manager app on your phone.
Than flash the patched boot.img with adb or TWRP. You need an extractor tool to get the boot.img from the rom.zip.
Iceman66 said:
Other method is patching boot.img with magisk manager. You can find some tutorials with google. Extract the boot.img from ROM.zip, put in on internal memory of your phone and patch it with magisk manager app on your phone.
Than flash the patched boot.img with adb or TWRP. You need an extractor tool to get the boot.img from the rom.zip.
Click to expand...
Click to collapse
I am using a custom kernel, will that change the process?
You need to reflash the custom kernel again after flashing the patched boot.img, but first check if your phone is rooted. (check in magisk app or install a root check app.)
The boot backup that I took before I flashed my custom kernel is the one that needs to be patched right?
If this isn't the case, can you guide me on how to get the boot.img? I only see payload.bin in my ROM.zip .
Okay, thank you for your help everyone
I ran into a different problem - when I install the patched boot.img, I get magisk but then I boot into TWRP and flash TWRP and my custom kernel, and I lose my root.
Dhruv.m said:
Okay, thank you for your help everyone
I ran into a different problem - when I install the patched boot.img, I get magisk but then I boot into TWRP and flash TWRP and my custom kernel, and I lose my root.
Click to expand...
Click to collapse
You have to patch the boot IMG with the TWRP already flashed, our phone doesn't have a recovery partition, so it's saved in the boot partition and installing Magisk from TWRP deletes the recovery, here is a good tutorial:
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com
Related
Hi guys
I've just bought a used Pixel 2XL and now figuring out how to root. Just wonder if it's good to use Magisk stable ver 18.0 to root the pixel 2xl on November update?
Thanks
cnkhanh said:
Hi guys
I've just bought a used Pixel 2XL and now figuring out how to root. Just wonder if it's good to use Magisk stable ver 18.0 to root the pixel 2xl on November update?
Thanks
Click to expand...
Click to collapse
Yep, you should be fine :good::good:
How about the December update?
I got lazy...still on October.
TIA!
Badger50 said:
Yep, you should be fine :good::good:
Click to expand...
Click to collapse
docluv01 said:
How about the December update?
I got lazy...still on October.
TIA!
Click to expand...
Click to collapse
No worries there either. Running it myself!
just jumped from november to march update using OTA via adb push and after i flash magisk it causes the phone to bootloop.
looks like there is a problem with patching the boot.img from magisk, reflashing the stock boot file the pixel works but no root obviously....any idea?
beren said:
just jumped from november to march update using OTA via adb push and after i flash magisk it causes the phone to bootloop.
looks like there is a problem with patching the boot.img from magisk, reflashing the stock boot file the pixel works but no root obviously....any idea?
Click to expand...
Click to collapse
There are several scenarios you could try.
1. Fastboot into twrp, flash twrp installer zip, flash magisk and see if it boots.
2. Fastboot into twrp, flash twrp installer zip, flash magisk, flash magisk uninstaller, then flash magisk again and see if it boots.
3. Fastboot into twrp, flash twrp installer zip, flash magisk, reboot to twrp, flash magisk uninstaller zip, then flash magisk again and see if it boots.
4. Fastboot into twrp, flash magisk, then flash magisk uninstaller zip, then flash magisk again and see if it boots. Twrp will be gone as well.
5. Try some of the above, but add a custom kernel into the mix.
Sometimes it can take 4-5 tries before you'll get it to boot up with root. Just be patiently persistent my friend and you'll get it :good:
Badger50 said:
There are several scenarios you could try.
1. Fastboot into twrp, flash twrp installer zip, flash magisk and see if it boots.
2. Fastboot into twrp, flash twrp installer zip, flash magisk, flash magisk uninstaller, then flash magisk again and see if it boots.
3. Fastboot into twrp, flash twrp installer zip, flash magisk, reboot to twrp, flash magisk uninstaller zip, then flash magisk again and see if it boots.
4. Fastboot into twrp, flash magisk, then flash magisk uninstaller zip, then flash magisk again and see if it boots. Twrp will be gone as well.
5. Try some of the above, but add a custom kernel into the mix.
Sometimes it can take 4-5 tries before you'll get it to boot up with root. Just be patiently persistent my friend and you'll get it :good:
Click to expand...
Click to collapse
thank you for spending your time to help me, very appreciated :good:
the trick was to remove magisk flashing the uninstaller, that i didn't before, after this it worked from first time...
HI there, so after patching the Boot.img with Magiskv23, it seems as if flashing it with ABD/Fastboot causes the bootloop. I had to flash to flash the stock boot.img back. Any advices? As I research this seems to be an issue with the fix being "I made some investigation and checked that replacing the file in the Magisk-v21.4.zip/arm/magiskboot with the magiskboot from v21.0 and flashing that one fixes the problem." But I have no idea how it'd work.
My device used to work with Magiskv21 until I updated my device and it has to be rooted again. So I got the stock boot.img file, patched it adb/fastboot flash it into the device (same method as before) and it causes bootloop.
If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default.
HOW do I do this?
In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.
I can't go back to unrooting it, as I still want to keep my data on the device. Is there any way I could attach this without unrooting it?
If you experience issues during installation,
boot.zip
in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.
Will include both stock boot.img, and stable and v23001 patched files.
I'll upload the boot.img file I use and the patched_boot.img file.
I can't upload with github so here https://drive.google.com/drive/folders/1YkekFaXmtOg6d5sMiecf3OnT7oqCEf4S?usp=sharing
Uploading boot.zip…
Device: Xiaomi 10T Pro (apollo) with MIUI Global Stable 12.5.1.0 (RJDMIXM)
Android version: 11 RKQ1.200826.002
Magisk version name: 23001
Magisk v23001 (I chose canary because that's what's needed to submit this report but I tried stable and the issue is the same as well)
Magisk version code: f822ca5(23001)
chinjangs said:
HI there, so after patching the Boot.img with Magiskv23, it seems as if flashing it with ABD/Fastboot causes the bootloop. I had to flash to flash the stock boot.img back. Any advices? As I research this seems to be an issue with the fix being "I made some investigation and checked that replacing the file in the Magisk-v21.4.zip/arm/magiskboot with the magiskboot from v21.0 and flashing that one fixes the problem." But I have no idea how it'd work.
My device used to work with Magiskv21 until I updated my device and it has to be rooted again. So I got the stock boot.img file, patched it adb/fastboot flash it into the device (same method as before) and it causes bootloop.
If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default.
HOW do I do this?
In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.
I can't go back to unrooting it, as I still want to keep my data on the device. Is there any way I could attach this without unrooting it?
If you experience issues during installation,
boot.zip
in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.
Will include both stock boot.img, and stable and v23001 patched files.
I'll upload the boot.img file I use and the patched_boot.img file.
I can't upload with github so here https://drive.google.com/drive/folders/1YkekFaXmtOg6d5sMiecf3OnT7oqCEf4S?usp=sharing
Uploading boot.zip…
Device: Xiaomi 10T Pro (apollo) with MIUI Global Stable 12.5.1.0 (RJDMIXM)
Android version: 11 RKQ1.200826.002
Magisk version name: 23001
Magisk v23001 (I chose canary because that's what's needed to submit this report but I tried stable and the issue is the same as well)
Magisk version code: f822ca5(23001)
Click to expand...
Click to collapse
when you were setting up the patched file you made sure you didnt choose rrecovery method in the magisk app
also rather flash it through twrp there are probably scripts that twrp has to run during the installation
if you dont have twrp you can flash it to recovery if you can access your fastboot/bootloader
reboot to recovery after then flash the patched boot.img to boot in twrp
(i dont know if you should clear cache or data or not just look for the guide )
reboot
flairepathos.info said:
when you were setting up the patched file you made sure you didnt choose rrecovery method in the magisk app
also rather flash it through twrp there are probably scripts that twrp has to run during the installation
if you dont have twrp you can flash it to recovery if you can access your fastboot/bootloader
reboot to recovery after then flash the patched boot.img to boot in twrp
(i dont know if you should clear cache or data or not just look for the guide )
reboot
Click to expand...
Click to collapse
I'm not sure how to use twrp, but I've rooted this device already just have issues with installing magisk patching boot.img after updating from magisk v20=>v23.
After that using boot.img that has been patched by magisk just causes bootloops.
Thanks for you comment though <3
chinjangs said:
I'm not sure how to use twrp, but I've rooted this device already just have issues with installing magisk patching boot.img after updating from magisk v20=>v23.
After that using boot.img that has been patched by magisk just causes bootloops.
Thanks for you comment though <3
Click to expand...
Click to collapse
Yes the stock boot image is locked bootloader so you will boot loop, flash magiskpatched boot image again to stop bootloop , even if its the old patched one
flairepathos.info said:
Yes the stock boot image is locked bootloader so you will boot loop, flash magiskpatched boot image again to stop bootloop , even if its the old patched one
Click to expand...
Click to collapse
Are you suggesting I use the old stock image where it works before I updated the magisk to version 23?
(I did that and it still bootloops)
Thank you for everyone's help. I've solved this by Uninstalling magisk v23001 and reinstalling magisk v23 thru TWRP in this method https://forum.xda-developers.com/t/...tom-rom-working-on-xiaomi-mi-10t-pro.4246339/
So, I accidentally uninstalled Magisk Manager after rooting the phone. I read somewhere on GitHub that Magisk hard-codes something (App ID?) into the boot image which is later installed.
So my question is, can I install Magisk Manager again, then patch the image, flash the image again without corrupting something?
Thanks in advance!
If you patched yout boot.img, you can install Magisk Manager again from github.
RheinPirat said:
If you patched yout boot.img, you can install Magisk Manager again from github.
Click to expand...
Click to collapse
Thanks!
That works without re-flashing the boot.img?
Yes. Because you have already patched and flashed the boot.img. The boot image is patched untill you flash a stock boot.img.
You can factory reset and delete the app as much as you want, it will not be effective at getting rid of root. So nothing to worry about
i dont understand why evertime when i flash the fastboot img of magisk , i lose the kernel and twrp too
.and the opposite way is true either.., maybe related to boot_a and boot_b or something...
im noob please need help
i want Magisk + Kernel Baalam + TWRP en my device
but img Magisk no allowed it
the img contains the ramdisks for recovery and kernel.
flash twrp then from it flash the zips of magisk and the kernel you want,that way they will be patched into the partition instead of replacing the whole thing
metalspider said:
the img contains the ramdisks for recovery and kernel.
flash twrp then from it flash the zips of magisk and the kernel you want,that way they will be patched into the partition instead of relacing the whole thing
Click to expand...
Click to collapse
The only way i know when i install magisk is patch Stock Boot image via Magisk then i flash it via Fastboot
where can i found it zip of magisk ?i didnt do it way before
CRNO said:
The only way i know when i install magisk is patch Stock Boot image via Magisk then i flash it via Fastboot
where can i found it zip of magisk ?i didnt do it way before
Click to expand...
Click to collapse
rename the apk file to zip.
so instead of "magisk.apk" it will be "magisk.zip"
thank you it work with me. all fine now
How can i flash magisk zip without twrp
PromiseKaunda said:
How can i flash magisk zip without twrp
Click to expand...
Click to collapse
Your device is old, it's better to handle with a new recovery like TWRP than another method (if there was)