Question Magisk 26.1 on Mi13 - Xiaomi 13

Anyone tried Magisk 26.1 with stock global rom 14.0.19, is it safe to update and patch the init_boot.img?
Thanks in advance.

I know you asked stock but on .eu it's working fine

Working fine on latest weekly also

Thanks I did it and see no visible problem.

Related

Magisk error 1

Hi guys! I am having some issues when trying to install magisk. I am currently running the latest twrp-3.2.2-0-enchilada. When trying to install magisk I'm currently having a constant error. Attached are the recovery log and a screenshot.
Magisk Error 1 fix
Hi, it looks as though you are trying to install an unsupported version of magisk you need to use the 16.4 installer not the 16.0 installer this will most likely fix your issue, I hope this helped. PS it is a beta version of magisk not the latest stable build.
16 is the stable build and SHOULD work!
Did for me.
It looks like the problem was a bad install of magisk. I went to the forums of magisk and found an uninstaller. I flashes it and then flashes the stable version. It looks like it worked. I have root back.

Which version of Magisk to install?

So, I've been reading posts about the Magisk version that is safer to install with OOS 5.1.8. A lot of them say that Magisk 16.0 stable is safe, some other say that you need the 16.6 version cause it creates less problems. So, my question is: which one do I use?
Also, if for some reason I use a version that creates problems, does using the Magisk uninstaller remove all the problems?
rickyjumb said:
So, I've been reading posts about the Magisk version that is safer to install with OOS 5.1.8. A lot of them say that Magisk 16.0 stable is safe, some other say that you need the 16.6 version cause it creates less problems. So, my question is: which one do I use?
Also, if for some reason I use a version that creates problems, does using the Magisk uninstaller remove all the problems?
Click to expand...
Click to collapse
I used 16.0 on 5.1.8 without any Problems.
I've been using 16.42(1642) beta up until 16.6 was released a week or so ago. It flashed just fine in the Magisk app and have had zero issues. Works well with ex kernel as well.
16.4 until last week, now 16.6 here, no problems at all
(started with OOS 5.1.6 - 5.1.8 now)
rickyjumb said:
So, I've been reading posts about the Magisk version that is safer to install with OOS 5.1.8. A lot of them say that Magisk 16.0 stable is safe, some other say that you need the 16.6 version cause it creates less problems. So, my question is: which one do I use?
Also, if for some reason I use a version that creates problems, does using the Magisk uninstaller remove all the problems?
Click to expand...
Click to collapse
Uninstaller will remove any problems unless you used something to debloat something. Then you would have to reflash system.
Lol
hi all
sorry if this post is off topic
i am having a problem with the latest magisk 17.1 ,where my banking app is not working as it triggered thaf the phone was rooted.
i do not have this problem with 16.1 stable version
my question is how can i install back the old version without twrp?

Is the first Pixel on Android Q rootable?

So I just updated my pixel to Android 10. And besides the issue with getting TWRP to work, I've been trying, and failing, to get Magisk installed.
I havn't tried the newer Magisk beta yet. Does anyone know if this would work instead?
Thanks
it works with me with the latest TWRP and Magisk
henk-jan said:
it works with me with the latest TWRP and Magisk
Click to expand...
Click to collapse
Okay, so with TWRP 3.3.0 with the no-pin workaround, I wasn't able to install magisk 19.3. However, I was able to get the Beta 19.4 to work.

Is V4A working on 10.3.7?

Does anyone know how to get Viper4Android working on 10.3.7?
I updated from 10.3.5 and I remember I had problems installing it on there too and I had to force stop the app before it would work each time. I've updated V4A to the 2.7.2.1 version through magisk and it just says Status: Abnormal, am I supposed to use a different one or?
If anyone knows, thanks
Use magisk for v4A
"I've updated V4A to the 2.7.2.1 version through magisk"
Has anyone managed to make it work? I'm installing it for the first time on 10.3.7 using magisk and I'm also getting the Status: Abnormal message.
Juwapa said:
Does anyone know how to get Viper4Android working on 10.3.7?
I updated from 10.3.5 and I remember I had problems installing it on there too and I had to force stop the app before it would work each time. I've updated V4A to the 2.7.2.1 version through magisk and it just says Status: Abnormal, am I supposed to use a different one or?
If anyone knows, thanks
Click to expand...
Click to collapse
Julortiz said:
Has anyone managed to make it work? I'm installing it for the first time on 10.3.7 using magisk and I'm also getting the Status: Abnormal message.
Click to expand...
Click to collapse
Hello guys,
So what I think that might prevent V4A to be working is having the latest version of Magisk installed. I had the same issue as you guys till I reverted back to Magisk v21.0 from v21.1.
Mr.FREE_Bird said:
Hello guys,
So what I think that might prevent V4A to be working is having the latest version of Magisk installed. I had the same issue as you guys till I reverted back to Magisk v21.0 from v21.1.
Click to expand...
Click to collapse
Thanks for the shout, Mr. Freebird. So yeah I guess it is a problem with new versions of Magisk. I tried on the newest update as well, 21.2, and still couldn't get it to work.
For Julortiz and anyone needing help getting it to work again, the exact steps I did were
- Downgrade Magisk to 21.0
- Download V4A 2.7.2.1 from Magisk and open the app but do not install driver yet
- Go back to Magisk and install Audio Modification Library but do not let Magisk reboot
- Go back to V4A and let it install the driver and reboot
- After reboot, open V4A, go to settings and check Legacy Mode
- Enjoy
Also this is probably really obvious, but make sure you screenshot or take note of all other modules you have installed because downgrading will delete all modules. Again this is probably obvious, just don't be dumb like me and lose all your other modules lol

[OP7][OOS11] root not working with Magisk patched boot.img

Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
matthi383 said:
Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
Click to expand...
Click to collapse
Hello,
Did you see this thread right below yours?
Android 11 OB4
Just installed OB4, anybody got a boot.img file or magisk patched boot image file? Also any news on TWRP for Android 11? Thanks in anticipation OK I was just lazy hoping somebody Elese did the work. Ended up using my OB2 patched boot image file...
forum.xda-developers.com
Magisk canary can also cause a lot of issues. I'm using 22.0.
Hey thank you! I already saw this and tried it out before to get TWRP working as in the Oxygen OS 11 Beta but this TWRP version does not work with the official OOS11 for the Oneplus 7. It's strange that on Open Beta it works and now its not working.
Watching this thread because I'm stuck too. I either need locked bootloader or unlocked with Magisk
Does anyone already has a solution to this one?
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
WareDat said:
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
Click to expand...
Click to collapse
I wish someone would upload the fastboot ROM
Thank you man it worked ! i hope others are seeing also your intructions and files so they can use them and have root back again

Categories

Resources