Database Users

Magisk (Manager) Update

Hi there,
A quick question - has someone here recently updated to Magisk 13.3 / Magisk Manager 5?
I am currently on Magisk 12.0 / Manager 4.3.3 (Resurrection Remix) and would like to update as Safety Check is failing after the Playstore update.
However according to this thread
https://forum.xda-developers.com/showpost.php?p=73142437&postcount=17290
there is a problem with the Axon 7 and the latest Magisk...
So which version is everyone one using and how did you get there (update Magisk first/Manager first...)?
(Magisk Manager is prompting me to update to 13.1 at the moment - not sure that's wise then?)

I updated to magisk 13.3 using magisk manager. Everything went smoothly and safety net passes even with a few modules installed. I was using A2017G on stock B05

Grogros4 said:
I updated to magisk 13.3 using magisk manager. Everything went smoothly and safety net passes even with a few modules installed. I was using A2017G on stock B05
Click to expand...
Click to collapse
Hi there,
Thanks a lot for your reply - when you updated to Magisk 13, did you already use Manager version 5 or are/were you still on version 4 and updated afterwards?

I am not sure.... I think I was running magisk 13 beta so I guess I was using magisk manager 5

I'm using magisk 13.3 with manager 5.1.1 on a stock chinese rom. I already fixed my issues regarding our unit which crashes the manager after giving su permissions.
After installing magisk in twrp and booting into system, open terminal manager and type these codes.
Code:
su
cd /data/data/com.topjohnwu.magisk/
mkdir /sdcard/Android/data/com.topjohnwu.magisk
cp -R ./databases /sdcard/Android/data/com.topjohnwu.magisk/
mv databases .databases_old
ln -s /sdcard/Android/data/com.topjohnwu.magisk/databases databases
chcon -h "u:object_r:app_data_file:s0:c512,c768" "/data/data/com.topjohnwu.magisk/databases"
Credits to @zorgzd for his fix.

Thanks a lot both of you -
I'll try the fix once I updated, that's really helpful. (Still wondering if I should try to update to Magisk 13 from Manager 4 and then install the Manager 5 apk after reboot...).

Whoooo? said:
Thanks a lot both of you -
I'll try the fix once I updated, that's really helpful. (Still wondering if I should try to update to Magisk 13 from Manager 4 and then install the Manager 5 apk after reboot...).
Click to expand...
Click to collapse
I would suggest to remove your old magisk using the latest uninstaller flashed in twrp. That will also install manager v4.
Then restore your boot.img backup if you have any.
And lastly, flash the latest version, 13.3 as of writing. It contains the latest manager also included in the zip.

Magisk on Mate 9 Pro

Is someone had more luck with Magisk than me ?? I have a rooted LON-L29C432B225. Was trying Magisk 13.3 but without luck. Phone restarts automatically during magisk installation through twrp.

I have finaly made it Magisk is working without problems on Mate 9 Pro (LON-L29C432B225).
1. Install latest twrp recovery - https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
2. Unroot rom, easy way i to download boot.img and flash by fastboot flash boot boot.img (https://www.dropbox.com/s/sj5su702r8omp2u/BOOT.img?dl=0)
3. Thanks to @ante0 (https://forum.xda-developers.com/member.php?u=2247733), he made a modified magisk package - https://mega.nz/#!QhMmRDgC!c3UqYIoaGtsekmJbWoP5x90spHbXVhircmmA_68s3pY
4. Flash magisk in twrp
5. After reboot you receive info about magisk update to 13.3. Mark in magisk manager settings "keep force encryption" and allow to update.
6. After next reboot you shuld have working magisk and SafetyNet status green
I hope it will help someone

On AL00 mate 9, followed the same procedure except downloading the boot.img as restored by huawei eRecovery, only unlocked the bootloader and didn't do anything else. Can install 13.2 modified version but safetynet fail, update to 13.3 with keep force encryption then bootloop. Checked the magisk log nothing seems wrong when can boot. Root works fine. Any help? Thanks

Guys any updates on Magisk v14 with xposed on our phone? fw B225

Magisk v15 doesn't work on miui

I tried flashing magisk v15 on miui global beta mm, but when I boot to system I couldn't find magisk installed . I also tried installing apk but it said magisk not installed. Magisk v14 works on this ROM( Magisk v15 works on my nos 8.1)

tom jp said:
I tried flashing magisk v15 on miui global beta mm, but when I boot to system I couldn't find magisk installed . I also tried installing apk but it said magisk not installed. Magisk v14 works on this ROM( Magisk v15 works on my nos 8.1)
Click to expand...
Click to collapse
Mine is working fine, magisk 15. Miui 9 latest dev beta.

rajbain said:
Mine is working fine, magisk 15. Miui 9 latest dev beta.
Click to expand...
Click to collapse
Which build, I tried it on 8th Dec build

I've also tried magisk v15 on my miui8 kenjo. its showing that magisk not installed. but v14 is working.

I have the same. Redmi 4A and Redmi 4Pro. Rom Xiaomi.eu 7.12.28. Magisk 14.0 works correctly. However, 15.0 and 15.1 can not be installed. Installation via twrp also does not change anything.

Same problem with redmi 4 pro miui 9.2 stable (xiaomi.eu)
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
Caused by: java.lang.OutOfMemoryError: Failed to allocate a 134209548 byte allocation with 16777216 free bytes and 113MB until OOM
at java.io.ByteArrayOutputStream.expand(ByteArrayOutputStream.java:91)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:201)
at com.topjohnwu.crypto.ByteArrayStream.readFrom(Unknown Source)
at com.topjohnwu.crypto.ByteArrayStream.readFrom(Unknown Source)
at com.topjohnwu.crypto.SignBoot.verifySignature(Unknown Source)
at com.topjohnwu.magisk.asyncs.InstallMagisk.doInBackground(Unknown Source)
at com.topjohnwu.magisk.asyncs.InstallMagisk.doInBackground(Unknown Source)
at android.os.AsyncTask$2.call(AsyncTask.java)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
... 3 more

i'm also facing the same problem. in my case even v14 isn't working.
send me your zip link

ktanay said:
i'm also facing the same problem. in my case even v14 isn't working.
send me your zip link
Click to expand...
Click to collapse
Hi, I used the official version, you can download it from the official XDA thread

I also have it up and running... I updated from v14 to v15, then v15.1 and i reboot to flash v15.2 now.
Rom: Official Global Developer
Version: 7.12.28 (latest when i write this post)

GreatApo said:
I also have it up and running... I updated from v14 to v15, then v15.1 and i reboot to flash v15.2 now.
Rom: Official Global Developer
Version: 7.12.28 (latest when i write this post)
View attachment 4377599 View attachment 4377600
Click to expand...
Click to collapse
What version of TWRP are you running?, did you update from 14, 15, and 15.1 at once or reboot after each update, I also noticed you have force preserve force encryption checked,

otyg said:
What version of TWRP are you running?, did you update from 14, 15, and 15.1 at once or reboot after each update, I also noticed you have force preserve force encryption checked,
Click to expand...
Click to collapse
I am running the ZCX TWRP (i think it's v3.0.2, available here in xda). I had installed v14.x and I was constantly updating when the new versions became available. I am now on 15.2 (so not all at once). I don't remember pressing the force encryption button, maybe it was checked for me...

GreatApo said:
I am running the ZCX TWRP (i think it's v3.0.2, available here in xda). I had installed v14.x and I was constantly updating when the new versions became available. I am now on 15.2 (so not all at once). I don't remember pressing the force encryption button, maybe it was checked for me...
Click to expand...
Click to collapse
Strange since I could not update to 15.2 no matter what I tried (only 14.0 would work), I was also using ZCX TWRP, I recently updated to redwolf twrp and now Magisk 15.2 went in fine, but I think it does have something to do with "force encryption" since RedWolf TWRP has a option "disable force encryption" and "disable dm-verity" , I don't think the first option was in ZCX twrp, so maybe when that got checked in your magisk manager it fixed it the same way the newer twrp does.
for people having issues here are the steps that worked for me
https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-install-magisk-15-2-kenzo-t3729329

otyg said:
Strange since I could not update to 15.2 no matter what I tried (only 14.0 would work), I was also using ZCX TWRP, I recently updated to redwolf twrp and now Magisk 15.2 went in fine, but I think it does have something to do with "force encryption" since RedWolf TWRP has a option "disable force encryption" and "disable dm-verity" , I don't think the first option was in ZCX twrp, so maybe when that got checked in your magisk manager it fixed it the same way the newer twrp does.
for people having issues here are the steps that worked for me
https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-install-magisk-15-2-kenzo-t3729329
Click to expand...
Click to collapse
Awesome! Here is your "thanks" for helping others

otyg said:
for people having issues here are the steps that worked for me
https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-install-magisk-15-2-kenzo-t3729329
Click to expand...
Click to collapse
I'm having trouble with the part about flashing the Magisk Uninstaller file, since my device (Redmi Note 2) is encrypted, I can't seem to make it work from the TWRP, in the same way wiping the Dalvik/Cache doesn't work.
So I'm stuck on Magisk 14 and even the direct update from the Magisk app puts my device in a bootloop (resolved only by installing the latest rom from the TWRP), maybe because I can't uninstall Magisk properly.
Should I try to flash the uninstall package from the adb?
EDIT: I finally managed to solve it by
1: Uninstalling Magisk from the Magisk manager app itself rather than flashing the uninstaller zip
2: Rebooted into the TWRP recovery where I first followed the instructions here under "Keeping dm-verity and forced encryption
": https://forum.xda-developers.com/showpost.php?p=73145975&postcount=2
3: and I then installed the latest Magisk 15.3
booted into system and no bootloop this time, successfully switched from Magisk 14 to 15

Updating Magisk & Magisk Manager

Hello everybody ! Today, Magisk Manager asked to update to MM v5.9.0 (I had 5.8.3). After updating, it first said Magisk was not installed, but found magisk 16.0 after refreshing . The problem is, I don't have access to SuperUser anymore, nor MagiskHide nor modules.
At the same time, a new version of magisk is available , v17.0. If I choose "Install", I have 2 choices : Download zip only, or patch img boot file. I don't want to make more mistakes than I've already done, so I ask you :
What do I have to do to get my Magisk working again ? Uninstall MM 5.9.0 and install 5.8.3 with it's apk ? Go ahead and let MM patch boot img file (sounds risky ) ?
My phone is a VNS-L31 C432B414, with OldDroid's TWRP.
EDIT : Uninstalling MM 5.9.0 app and installing 5.8.3 didn't helped : Magisk is detected, but still no access to SuperUser,hide,etc...

Root and Magisk

History:
After I change the kernel I lost the root! Then I tried to update the Magisk to version 18 and the Magisk Manager to a most recent version that I don't remember its version.... But my phone continued without root.
Trying to solve this again I install Magisk 16.3 and Magisk Manager 5.6.4 downloading and installing the files available in this link: https://www.stechguide.com/download-magisk-v16-3/
Without success too!
-
So, darlings.
I'm asking for a tutorial to uninstall all the Magisk things of my phone (if you experts think it is necessary) and I'm asking for a tutorial to root again my phone with Magisk.
And I'm also asking to know the latest STABLE version of Magisk and of Magisk Manager COMPATIBLE with my phone and that will work well!
I have a Galaxy Note 3 (SM-N9005) with [ROM][C9 Pro Port][N900X] AspireTeam C9 Pro v5.0 [18.5.18][Aroma/Smooth/Modded] installed.
Thank you so much!!!

LeandritoG said:
History:
After I change the kernel I lost the root! Then I tried to update the Magisk to version 18 and the Magisk Manager to a most recent version that I don't remember its version.... But my phone continued without root.
Trying to solve this again I install Magisk 16.3 and Magisk Manager 5.6.4 downloading and installing the files available in this link: https://www.stechguide.com/download-magisk-v16-3/
Without success too!
So, darlings.
I'm asking for a tutorial to uninstall all the Magisk things of my phone (if you experts think it is necessary) and I'm asking for a tutorial to root again my phone with Magisk.
And I'm also asking to know the latest STABLE version of Magisk and of Magisk Manager COMPATIBLE with my phone and that will work well!
I have a Galaxy Note 3 (SM-N9005) with [ROM][C9 Pro Port][N900X] AspireTeam C9 Pro v5.0 [18.5.18][Aroma/Smooth/Modded] installed.
Thank you so much!!!
Click to expand...
Click to collapse
First, Magisk is one of the most documented tools on xda, has its own official forum and especialy its official releases on GitHub (where all versions are available). It's useless to get it elsewhere.
Second, Magisk will only do his magic on an already flashed kernel. If you flash kernel after Magisk, you won't get root.
Third, Magisk flashable zip contains the corresponding Manager and will inject it systematically.
Finaly, you need TWRP for a successful flash of Magisk. With other custom recoveries, errors like "can't find the boot image" can happens.
Now, for a complete removal of Magisk from the system, you only have to flash the latest official uninstaller.
After reboot, go to recovery, flash your prefered kernel then flash Magisk. The latest stable version is v18 and will work well on your rom.

...