yashsingh1/xdaforums huggingface dataset:
[Magisk] sujeet_kumar:
No problem in module downloading and installing too. Currently using two module i.e. App Systemizer_14.0.0 and injected YouTube Background playback Vanced_c12.45.56.

You may try Magisk 15.0 (Its also working without any problem) now.
[Magisk] JairPaalman:
I tried doing that, but I can't patch my boot image that way, and it causes a bootloop. Good troll.
[Magisk] mnewiraq:
guys,

the folders appeared in a strangely named manner like " 2h8P9lGY8I1A884LMsBjaA " in twrp and no magisk zip file appears to be flashed. any solution, please?
[Magisk] nirvana97:
A fresh install of magisk v15 causes my s6 edge+ to loop in "SAMSUNG" logo for around 2-3 hours until it drained my battery.
[Magisk] nature boy:
Except v15 put my tablet into an error mode (described on the previous page), so I had to reflash everything and I don't have TWRP for the tablet (otherwise I would just install an old version via TWRP).

I'm completely reliant on magic manager being able to patch the boot.img
[Magisk] Didgeridoohan:
Sorry about that... Didn't read properly (to much going on in the threads the last couple of days).

Great idea and it's been put forward to [MENTION=4470081]topjohnwu[/MENTION] already...
[Magisk] nature boy:
Yes being able to flash a local magisk would overcome some of the issues, especially those (like me) who have a device that doesn't have TWRP but need root

IMO it's a legitimate use case
[Magisk] rom-g:
Hi all,

After installing magisk v15.0.zip + magiskmanagerv5.5.1, i have big big troubles with magiskSU.

My phone : moto g3, android 6.0.1 stock firmware + Squid Kernel r21 (linux 3.10.108) + TWRP 3.2.0-r1

When an app is requests su access, magisksu doesn't answer. If i try to open the MagiskManager, it crashes.

The logcat says :

etc..

FYI :

- i tried all type of installations (update from previous Magisk, update from the manager, update from TWRP, clean install after flashing the boot.img from fastboot...)and encountered the same bug with magiskSU.

- i have the exact same behaviour with magisk 14.6.

- if i go back to magisk 14.5, magiskSU is working again (with just this little annoying bug : su requests doesn't seems to be stored and i have to grant su access for same apps every time).

I hope the logs attached to this post will help the devs to fix bugs and improve this great tool.

Big thank to Topjohnwu and all people contributing to magisk.
[Magisk] fishnchips2:
Still not working for me. A module downloads, installs then just isn't there.
[Magisk] Paenik:
Hello I've tried my luck with my Galaxy S8 + G955F and the Android Oreo 8.0 Beta from Samsung. Root works very well, the phone is running well but both with Magisk Version: v14.0 & v15.0 always no Safetynet pass unfortunately. It always comes only false. Maybe there is still a fix in the future would be happy. Thank you
[Magisk] -Tiz-:
I flashed Magisk 15 and now FlashFire does not work on my phone (Doogee S60) anymore. Moreover, Magisk Manager fails to install modules like Greenify.

What can I do? Thank you.
[Magisk] QkiZMR:
Moto G5S Plus here, Android 7.1.1. I installed 15.0 without any errors, it looks that it works but I saw one error in Magisk logs, it appears right after boot. It says that can't open some sqlite database. No side effects.

Sent from Moto G (5S) Plus via Tapatalk
[Magisk] Didgeridoohan:
That's an issue with the su database, so it's the Manager causing issues.

During your trials, did you ever uninstall the Manager? Do it by pressing Uninstall -> Uninstall App in the Manager and then reinstall v5.5.1.

If that doesn't work, backup your Magisk image (it's in /data or /data/adb), flash the uninstaller followed by the Magisk v15.0 zip and restore the image to /data/adb. Should theoretically work...
[Magisk] Aniruddhlr:
Init.d not installing

I tried to install in new magisk 15v. It says installing failed.

https://xdaforums.com/apps/magisk/module-magisk-init-d-universal-init-d-t3579305

Form here.
[Magisk] rom-g:
I can't uninstall the app from the manager itself because i just can't open it. It crashes as soon as i try to launch it.

I can uninstall>reinstall it from the android settings (applications list) but the bug is still here after reinstallation.

As suggested, I'll try to manually restore the magisk image and come back later with the result.
[Magisk] tomiga:
Same issue here. Installed Magisk 15, and my S6 Edge (T-Mobile variant) is stuck on the boot animation.

EDIT: Fixed with 15.1.
[Magisk] Timberlake.C:
fixed already thanks ya..but now I'm trying to install systemless Xposed.
[Magisk] RichmondoUK:
Unfortunately this messes up samsung. 14.0 is best and sorry to see this going downhill :(
[Magisk] drich66:
Hopefully you have a recent back up you can restore and dont update magisk.
[Magisk] SeishiNui18:
Not updating

Hi,

I'm on 14.5 and since 15 is stable I decided to update. I installed Magisk via patched boot.img technique simple because I want to preserve the stock recovery.

I can use TWRP but I don't want to wipe data due to encryption and TWRP version on my phone can't decrypt it.

So updated Magisk Manager to 5.5.1 and update to 15 through it, it went fine until reboot and still shows 14.5 so I was wondering if it's not possible to update because of the patched boot way?

I have the log but can't seem to attach.
[Magisk] AtomicStryker:
Moto X Play on 6.0.1 here

unwisely upgraded when Magisk prompted me to - Manager 5.5.1 keeps crashing and not reacting to requests such as Module updates

v15 refused to play ball with Module updates too, after downloading it keeps complaining about app overlays (what do they have to do with anything?!)

Tried flashing uninstaller and clean re-install but the issue is clearly in the manager, github commitlog even has a "sudb init fix" recently. Someone doesn't do regression testing.

After wasting several hours i've reverted to Magisk v14 and Manager 5.3.0, both of which actually work. Also had to re-install my custom kernel because the Magisk uninstaller somehow reapplied the stock kernel and broke the phone's WLAN ... joy.
[Magisk] Sir Backe:
I have 2 problems which I wonder if you have the same ones:

1. Safety net test is successful with versions 15.0 / 5.5.1. However, as soon as I activate Xposed framework SDK25/89 it says: Safetynet test successful, but CTSprofile and basicintegrity false. Is there a problem with xposed and how could I solve this?

2. It concerns the e-banking app 'UBS access'. This app does not allow me to start itself, even with working Safetynet and activated in Magisk hide. It says that it has found a security relevant issue (probably root). Does anyone has an idea how to fix this?

tks a lot!
[Magisk] tdhite:
Samsung Devices appear OK

For those having troubles on Samsung devices, v15.0 works fine, but that assumes a well formed kernel and ROM (Stock should work as well).

I attached a couple pics of my S6 on which v15 was installed over a modified boot image (custom kernel I maintain) and after Magisk install, a debloating module. All works fine.

All that suggests is v15 does work, but may need coercing (e.g., completely remove Magisk before installing it, and restore stock (or custom) kernel prior to install). Not sure that helps anyone, but at least you know Samsung devices do actually work ok with v15.0
[Magisk] SeishiNui18:
Pretty much anywhere tells that xposed wouldn't pass safety net in whatsoever, so it's not a problem with Magisk.

Without xposed, I'm passing safety net, so you might want to try your banking app without xposed and see.
[Magisk] ColeTrain!:
I appreciate your post. I havnt been able to fool with the phone these days. Happy to install any modules needed.

Just let me know where to get them, and specifically which ones.
[Magisk] mtbsoft.:
So my Huawei Mate 8 (7.0, latest stock) running Magisk 14 and Manager 14.1 announced a new Manager this morning which, in turn offered me Magisk 15 which I installed (no errors).

Unfortunately I now cannot boot the phone. It comes up with the unlocked warning screen and, if I leave it, simply restarts again - rinse and repeat. I can get to the TWRP screen but am unsure what to try to install - should I try to go back to 14 (it's on the SD) or reinstall 15 but via the SD.

Suggestions please. Gonna trawl the site for alternatives but if anyone can shortcut the process with some pointers I'd really appreciate it.
[Magisk] Sir Backe:
Banking app doesn't work even with deactivated xposed or start with core functions only. Do you think that uninstalling xposed might help?

I actually wouldn't like to do that because I need exposed for many modules.
[Magisk] raosahab:
No support is provided here i told my problem 2 days ago i am waiting for my solution that any Dev will help us but no one replied for our problem for safety net. Devs please give any suggestion or solution.
[Magisk] /root:
Same problem here.

I updated to magisk v 15.0 and also updated the Magisk Manager v 5.5.1 and I get 'SafetyNetApi Error' when I try 'SafetyNet Check'.
[Magisk] SeishiNui18:
Usually, uninstall xposed, check safetynet and it should show green. That will allow you to use the banking app. If not then you need to add the app to MagiskHide list.

---------- Post added at 06:08 AM ---------- Previous post was at 06:07 AM ----------

Not a pro, but it looks like encrypted data.
[Magisk] Zottex:
hello,

i am a new user of magisk, i have always used SU until now.

on my xiaomi note 3 all works flawlessly but i have a problem wit ROOT EXPLORER , it not recognize that i have root and so i cannot use it.

if i cannot resolve this problem its possible to suggest another similar app?
[Magisk] tag68:
Seems root explorer relies on some path of su binary, which should not be treated as fixed. This is not the thread for this discussion. It is no problem of Magisk. Otherwise please give logs.

Hint for searching for alternatives: I remember several threads for choosing a file explorer. Some came from the time when it was found out that ES Explorer is bad implemented and sends data to unknown destination. They should exist in the general part of xda. My personal choices are Total Commander, MiXplorer and X-Plore.
[Magisk] jacklul:
Magisk 15.0 doesn't patch boot image here, did clean install (remove and restore twrp boot backup), magisk still not recognized by manager and install script says boot image is stock each time. Redmi 3S, xiaomi.eu stockish rom.

Edit: Wifi is not working now on my device, thanks... [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] Clark789:
Hi,

only to let you know, that in some cases it works flawlessly: i'm on a OP3T and so far i used Magisk Manager 5.5.0 and Magisk 14.0 on Android 7.1.1 (OOS 4.5.0) and everything worked.

Now i updated to the Magisk Manager 5.5.1 and it shows me the update for Magisk 15.0 and i updated without any issues. After this i moved to Android 8.0 (OOS 5.0) and again (this time nearly) without issues. Some installed modules won't work proper under Android 8.0 (Call recording, Viper4Android 2.5.0.5 and two others). I uninstalled all modules and so far everything works pretty good, even my banking app won't moan...

So, for the moment i'm quite satisfied!! :)

Regards

Clark
[Magisk] mnewiraq:
Please

Can you solve this problem

Twrp will not show the files correctly
[Magisk] QkiZMR:
What call recording module you use?

Sent from Moto G (5S) Plus via Tapatalk
[Magisk] redking974:
Got the same issue with this phone. I go back to v14
[Magisk] der_Kief:
just FYI ....

updated to Magisk v15 (1500) on my BQ Aquaris X5 Plus with Stock Nougat ROM v2.3.0

no problems so far .....
[Magisk] Clark789:
I used this: OOS Call Recording Enabler (with Android 7.1.1). Not just tested it yet with Oreo...

Regards

Clark
[Magisk] MushroomStealer:
My S7 Edge is stuck on Boot logo

Soo, later this morning i updated my magisk on v15.0 from v14.0 over recommended magisk installation, and when my phone rebooted, it was stuck on a boot logo img "Samsung galaxy s7 Edge, powered by android" and its not moving from there, and its not even looping, it is just solid img? I also tried the beta v15.0 and downgrading to v14.0, when i downgrade to v14.0 then it started to bootloop the same img from solid? Is there anyone here that is having the same problem with this and if so, is there any fix to this rather than installing new fresh firmware :rolleyes:
[Magisk] pierrep56:
No issues on Magisk v.15 with Nexus 6P angler and unofficial Liineage 15 (Oreo)
[Magisk] Pi.mp3:
After updating my phone got stuck on the same respective screen for my LeEco Le Pro 3 and what I did was boot into my recovery and since I haven't downloaded the Magisk uninstaller yet I wiped everything including data and flashed an outdated version of my ROM that I for some reason haven't deleted after flashing.

After that I managed to boot up again and found out that, my device wouldn't pass SafetyNet even after flashing the uninstaller. Now I'm on the latest version of Resurrection Remix again and even though I have wiped everything including data I'm still not passing and I'm still not able to boot after installing Magisk 15.0. I have no idea what to do about this since I want to pass SafetyNet and root my device, but am unable to do any of this. Keep in mind Magisk 14.0 worked perfectly fine with the latest Resurrection Remix.
[Magisk] der_Kief:
Problems with updating to Magisk v15 on Huawei P9 Lite with Stock Nougat ROM EMUI 5.0.1

It updates without any problems but boot process takes much longer and boot logo/animation is not original Huawei anymore ... seems to be Stock AOSP boot animation.

Also modelnumber in device information is set to generic device instead of VNS-L31. So it seems that that Magisk v15 is not 100% compatible with EMUI 5.0.1

So i reverted back to v14 for now....
[Magisk] Floodland:
That happen because magisk forced encryption (even when you specified not to). You could format /data from twrp to recover access to it, but as long as Magisk v15 is installed, it will re-encrypt the partition, without warning or notification. V14 does not mess with /data.

Beware of re-formatting /data though, you will loss information stored in internal storage and any info stored there,I learned the hard way. Magisk v15 presented many issues for some people, where v14 does not
[Magisk] Didgeridoohan:
PSA - Magisk v15.0 issues

Gonna recap possible solutions for some issues that have arisen from Magisk v15.0.

Samsung devices that experience bootloops, try flashing a dm-verity zip together with the Magisk zip. See here for more details (thank you [MENTION=5566313]Aria.A97[/MENTION]):

https://xdaforums.com/apps/magisk/fix-bootloop-issue-magisk-14-6-15-0-t3725962

Huawei devices that experience bootloops or weird issues like changed model number etc, before installing v15.0 make sure to enable "Preserve AVB 2.0/dm-verity". This has been known to work for some. Might possibly also work for other devices experiencing similar issues...

Users experiencing su issues and/or the Manager crashing, if you can open the Manager, uninstall it by pressing Uninstall -> Uninstall App and then reinstalling the Manager (download from the release thread).

If you can't open the Manager or if the above doesn't work, flash the latest uninstaller zip (download from the release thread) in recovery and reinstall Magisk.

If you can't open the Manager and don't have access to a custom recovery, I'm currently at a loss as to how you should continue... Open to suggestions.

Users experiencing SafetyNet issues, read through the troubleshooting guide. It's not yet updated for v15.0, but the SafetyNet tips should still apply. If you can't get it working, make sure to post logs (take a look at the "Asking for help" section).
[Magisk] kantjer:
What worked for me and a few other user when experiencing similar issues with the unofficial build was

Uninstall MagiskManager

Reboot

Flash zip

The reboot in-between was essential to fix the MM issue

Hope this will work for others
[Magisk] der_Kief:
thanks for the hint ... the "Preserve AVB 2.0/dm-verity" thing was the solution for me :good:
[Magisk] V4LKyR:
I get no root after installing Magisk v15. However, everything works fine, the modules and integrity tests. Just no root.

Why?
[Magisk] nickrs:
Same here. I have tried everything, uninstall magisk, reinstall, install previous version, flash no-verity zip, nothing works, the boot loop remains. Unfortunately I think I have to format the system.

[UPDATE]

I was able to save my phone. Here are the exact steps i did (S7 edge):

1. Download Latest Magisk Uninstaller (20171226) and flash it.

2. Flash no-verity-opt-encrypt-5.2.zip (I know it's not the latest, but I already had it on the phone and it worked for me).

3. Flash Magisk 14.0.

4. Reboot to system, give some time and finally worked.

In other attempts I did not flash the no-verity zip and the system continued in bootloop. It was essential, at least for me, to flash it before flash back Magisk 14 (even though I already had flashed no-verity in the past).

PS: I tried to add the links to the zips, but for some reason XDA is not letting me add links. I apologize for this.
[Magisk] Damonzer:
hi,

i use a Samsung Galaxy S5 (G900F)

i was previously on 14.0 with manager 5.5.0 and everywithing was fine

since updating to manager 5.5.1 then 15.0 with the manager i dont pass safetynet (both cts and basic integrity) anymore

in my attempts i tried to go back to 14.0 (with twrp) and 5.5.0 (first attempt to install 14.0 put me in a bootloop so i reflashed my original boot.ini with twrp then installed 14.0 with twrp) but without passing safetynet

since then i am back on 5.5.1 and 15.0, still without passing safetynet

but i noticed a lot of error in magisk log who seem to happen during the booting

here is the log:

what can i do to fix it?

thank you A LOT in advance for your help!
[Magisk] Pi.mp3:
Nah it doesn't.
[Magisk] SnoopKilla:
magisk cant update from 14 to 15 via manager. have bootloop if flash via recovery. tried ununstal via ununstaller.zip and flash again and gave bootloop too.

solved problem(for me): install via manager(strange but this time magisk install go on), reboot and have bootloop, disable verify in recovery(miui have this stuff), boot normaly(manager say magisk not installed), reboot in recovery and flash magisk 15. this works for me

redmi 4x miui 8 android 6
[Magisk] nature boy:
Give magisk one last try before waiting for a new version and....

Wow, my issue was also fixed with the preserve AVB 2.0/dm-verity option selected and the preserve force encryption unselected. With v15 mind you.

For those with the encrypted error message asking for the password, just like me, this worked for me.

My tablet has root again! Tablet has a Mediatek SoC and no TWRP, FYI
[Magisk] Einsteindks:
Installed the update to 15 with Manager 5.4.2. no problem, everything worked. Updated to Manager 5.5.1., and Manager crashes, but I still have root. Tried a clean install of the Manager, no luck. Running a slightly personaly tweaked ComputerFreak 1.0.8 on Droid Turbo 64gb.
[Magisk] Yooshaw:
I've got the same issue on two S5s (G900T), my logs look almost identical to yours. No modules work at all. Help!
[Magisk] jenslody:
Can you try to install stock boot.img in TWRP, reboot, go back to TWRP and flash magisk again ?
[Magisk] klausstoertebeker:
Hi jenslody,

before I do as you suggested maybe there is a hint in the installation I added in my post...

Regards

"Klaus"
[Magisk] linuxdep:
Hi, i don't know that is ab bug of magisk or HTC?

other HTC thread
[Magisk] connde:
MagiskHide stopped working

Hello, I'm having issues with MagiskHide after upgrading to v15.

All apps that were hidden are now saying that my phone is rooted, what can I do to fix the problem?

How can I go back to v14 easily?

Just tried and my phone is not passing SafetyNet anymore.

I have a Samsung J5.

Thanks.
[Magisk] thomasswan5547:
Safety net doesn't pass magisk v15, pa Android 7.30
[Magisk] y2klol:
Does anyone know if v15 is safe to install on Samsung (SM-A520F)?
[Magisk] jamy015:
I upgraded from v14 to v15 on my Nexus 5X and it started freezing and locking up like crazy.

I flashed the uninstall zip and re-flashed v14 and everything seems to be fine again...
[Magisk] PowerOfTwo:
I'm here because Magisk Manager wanted to update Magisk to v15 but didn't download the file. I tried several times but nothing happened.

Now I've read last ten pages. It's still an error I don't know how to handle but happy me. :)
[Magisk] mctiew:
Due to this, I downloaded the zip file instead. When I try to install it using TWRP, it failed with error boot image not found. I already previously installed with 14.0 using the same TWRP.

Btw, this is a TV box, not a phone. Possibly it can detect the device file for boot image ?
[Magisk] Sir Backe:
I already get a green Safetynet test when I deactivate Xposed. I also have added the banking app to the Magisk hide list. But this app still recognizes some changes on my phone. I assume it recognizes root, because I have no other changes.

If you have a similar phone like me with Magisk, would you do me a favor please? Install the 'ubs access' app from playstore, give it internet access if you have a firewall, and then just start the app and see if you come to a page where you should enter a code. I do not get this page because the app says before that it has found a safety issue. I would be very happy if you could do that. Tks a lot!

PS: The magisk log says following after starting the banking app:

]

12-28 08:33:38.910 456 783 I Magisk : proc_monitor: com.ubs.swidK2Y.android (PID=5770 ns=mnt:[4026534250])
[Magisk] Didgeridoohan:
If by code you mean "Contract number", I can get to it just fine.

Magisk v15.0, Manager v5.5.1, the app added to the Hide list and the Manager hidden (there's an option for that in the Manager settings).
[Magisk] -Tiz-:
I have a question: People say that Magisk Manager can root an unrooted phone without further help. On my phone (Doogee S60) this does not work. Magisk Manager merely offers to download a magisk.zip file that can subsequently be flashed via a custom recovery. Alternatively, Magisk Manager offers to patch a dump of a boot.img. I guess you can then subsequently flash the patched boot.img via fastboot. Is my understanding correct or is Magisk Manager indeed capable of independently rooting a phone or at least certain exploitable phones? Thank you.
[Magisk] Didgeridoohan:
Your understanding is correct. The Manager can only install Magisk if already rooted (preferably with MagiskSU), or patch a boot image for manual flashing if not rooted. Other than that you need the zip for installation through recovery.
[Magisk] mnewiraq:
That's right for me also. I have Huawei honor7x. It is non rootable with magisk and for all magisk versions.
[Magisk] shemgp:
Hello, could anyone help fix this segmentation fault? Thank you.
[Magisk] tomaasz:
[MENTION=4470081]topjohnwu[/MENTION] thank you for great solution!

do you see opportunity to resolve data mounting issue on S8 with Oreo ? Is it known for you or do you need any logs from us?
[Magisk] SeishiNui18:
I don't pass safetynet, sorry, can't try it for you. I have a custom rom, even with magisk it doesn't pass. Just using this for compatibility and ease of use.
[Magisk] SeishiNui18:
[MENTION=4667597]Didgeridoohan[/MENTION],

Can you check, I've tried doing the patched_boot.img to get v14 installed. I updated to Magisk Manager 5.5.1 to update to v15. It shows successful but after restarting it stays with v14.

Log from manager attached. Thanks.
[Magisk] mctiew:
Okay the problem is with the magisk 15.0.

Because I could install magisk 14.0 and it is working but cannot install magisk 15.0 via TWRP.
[Magisk] songokujames:
I downgraded magisk from version 15 to v14 directly via TWRP, now stuck at bootloop, how can I get accesss into my phone again? I have try flash the uninstaller but I still not able to enter my system. Please help as I don't want to factory reset my phone as it will cause all my data and app loss.
[Magisk] theandroidguy:
Flash the stock boot img again
[Magisk] songokujames:
Will it cause my data loss? And how do I flash back the boot image?
[Magisk] theandroidguy:
are you using a custom rom? if yes then open the rom.zip there you will find the boot.img, extract it and flash it via fastboot or using TWRP