yashsingh1/xdaforums huggingface dataset:
[Magisk] HM13androfan:
Can anyone help me with this one problem that never resolves for me , when I use the Sony framework module /Sony apps enabler module and install the Sony albums app from Play store it never opens and force closes. Tried almost everything including force stopping /data, cache clearing /reinstalling app and even different firmwares .

Device : Galaxy S6

ROM : Stock (Android 7.0)
[Magisk] UFOZ24:
Does it work with KitKat thanks in advanced
[Magisk] Alxoom33:
Uninstalled SuperSU and fastboot flashed boot image. Installed Magisk v. 15.1 and Magisk Manager 5.5.2 on my Pixel C tablet running stock Andriod 8.1.
[Magisk] sdz2:
I believe this is the F2FS error for Motorola devices referenced in the main post.

Phone: Motorola Droid Turbo

ROM: Computerfreek274_1.0.8 Update Marshmallow 6.0.1 Global,De-bloated,Root,Volte, 5/29/17

I tried from a clean install: Full wipe, install ROM, boot, reboot recovery, flash Magisk 15.2, reboot, install Magisk Manager 5.5.2. I even tried uninstalling Magisk and reinstalling Magisk. I enabled adb debugging and used adb shell to call su.

When calling su, I get the same behavior as in Post #21519. MagiskManager crashes, does not save permissions, and displays the logcat errors from his post: Failed to chmod, disk I/O error (code 1034), etc.

I tried finding a compatible kernel with the F2FS fix. I also tried finding an old Magisk to flash. Then I got the idea to not use F2FS.

Fix (use ext4): Formatting /data as ext4 (rather than the default F2FS) fixed the issue for me. From TWRP, I performed a full wipe, formatted /data as ext4, installed the ROM, and installed Magisk. Since then, Magisk (and everything else on my phone) has worked exactly as expected.
[Magisk] Didgeridoohan:
No.

I believe you are correct. Nice catch! It makes sense, since the su database now has moved with everything else to /data/adb.
[Magisk] JulGer01:
Thanks! 15.1 works like a charm. Reassuring after the shock with v15...[emoji6]

Gesendet von meinem K6000 Pro mit Tapatalk
[Magisk] jasio2k:
Change of subject [emoji3] Happy new year to all and more stable update during this year. Thx to dev and keep doing great work.
[Magisk] Sagittarius199x:
Magisk 15.1 works well on Xperia Z5 android 7.1.1 Kryptonian rom

But it have one problems

E Magisk : mount (null)->/ failed with 16: Device or resource busy

I try reflash rom with all wipe but problem is still not resolved
[Magisk] Sudeep:
But after flashing systemless xposed..my device stuck in boot loop...wht to do??
[Magisk] OreoCupcakes:
I didn't know how to describe the first post, but basically my encrypted phone somehow decrypted after the first time I tried to update to 15.1. How do I know it got decrypted? After the update, when my phone boots up instead of bringing me to a black screen asking me for my password it booted up into the lockscreen. I thought that was strange so I rebooted into TWRP. Instead of the usual screen asking for a password in order to mount my storage to TWRP, it got stuck on the TWRP logo mounting the drive for a while. My security settings said my device was Encrypted but it was acting Decrypted after the initial update of Magisk. The fix to this was resetting the password and clicking the button to require it on boot again.

As for the second post, while I was trying to fix the first issue I was uninstalling and reinstalling Magisk from 14.0 to 15.1. At some point, the installation of Magisks triggered dm-verity. So I used this XDA thread and the provided boot image, to get rid of dm-verity. Once I fixed that issue and before I installed my usual modules, I would grant my usual apps the necessary SU permissions. After that's done, I would install my modules and reboot. Upon reboot all the apps I granted permission, lost that permission. I went back to Magisks and removed their permissions entirely, this would sort of fix it. Some apps, would ask for permissions again while others wouldn't even after clearing their data and cache. The solution I found was to remove permissions from Magisk and uninstall/reinstall the apps. After the reinstall they would ask for permissions and get granted permissions again.

I don't have the logs for issue one as I didn't save the logs when the issue happened and the debugging I did used the full remover so the history is gone. As for issue two, here's Magisk log. I don't have any other logs to provide for that issue.
[Magisk] DodoGTA:
No (But I have an idea of porting it to KK (and below)
[Magisk] Shadear:
Same here now its like super su nothing special about it just syatemless on thing else :o
[Magisk] AndrOmega:
everybody please wait !!

version 15.2 will be released very shortly and all problems will be gone(!)
[Magisk] Didgeridoohan:
Doesn't sound like it decrypted your device, but removed the requirement for a password at boot. Weird. I'm not the guy to comment on that though. Not in my skill set...

That sounds like an issue with the su database. There where some major changes for that between v14.0 and v15.0... If the update didn't work properly, this could happen. Glad you got it sorted.

---------- Post added at 13:19 ---------- Previous post was at 13:12 ----------

This is maybe the 4th time I see you posting this cryptic question in the beta thread... Which is not the place for it and hence those posts get deleted.

But, my curiosity is piqued, so I moved this to the general thread.

What on earth are you talking about? :laugh:
[Magisk] Floydfire:
I also got su issues (I think maybe is related to the db?) I'm on Omni 8.1 op3 if I install directly magisk 15.1 the su page crash as soon as some app request su, if I install 14 then update to 15.1 through app the su permissions doesn't stick and the su page is empty, I think that maybe it can be related to the manager rather than the boot.img? Su is working and the log does shows the history of su not a big deal I can live with that for now... If I can do something to help solve the issue let me know :)
[Magisk] warface9991:
After updating rom magisk is missing??
[Magisk] DodoGTA:
No addon.d support in your ROM = No Magisk after ROM update (without reinstalling it manually after the ROM update)

But, if your ROM has addon.d support and you're getting this problem, then make sure you have Magisk installed before the ROM update, MANUALLY flash the ROM update in TWRP (don't reboot yet), go back to TWRP's main menu > Advanced and tap Copy Log to SD (And now, you can reboot and pull and attach the recovery.log)
[Magisk] teddy0209:
That's supposed to happen, unless magisk is flashed after rom automatically... You just need to reflash magisk...
[Magisk] warface9991:
I flashed magisk for now. If it occurs again I will attach it. Thanks for your support
[Magisk] UFOZ24:
Update me if u do it
[Magisk] u_no_fr:
Hi

I have installed magisk on my xiaomi Redmi note 4X with Epic ROM

And adaway does not work... is there any issue?

If I chech it under hiding with magisk adaway says that my phone shoulb be rooted ...
[Magisk] rom-g:
I suspected that there was a link with the F2FS, but I still don't understand why this is kernel related ... What is strange to me is:

- I'm using a custom kernel which, AFAIK, is not affected by this bad f2fs implementation.

- I have other apps that also use a sqlite database in this f2fs partition and they work with no issues.

- my problem only occurs with magisk 15.x and over (magisk 13.x. and 14.x seems to be able to read/write this F2FS su database with no issues).

Well, I will probably format my data partition to ext4 because I want to benefit from magisk 15.1, but it really bothers me ... :)
[Magisk] Einsteindks:
MM 553 & 15.2 working on a tweaked Cf108 ROM on unlocked XT1254. MM may crash occasionally in the background, but is quite functional, afaik. Gladly, and patiently will wait for other major issues tk be resolved first. FABULOUS development & support!!!!
[Magisk] Truely Simple:
I want to ask that, if it works with Lenovo K3 note K50a40.
[Magisk] Baqir2:
Hello guyz

## From today my device's warranty is finished and i decided to root my samsung j7 prime SM-G610F baseband version G610FDDU1BQJ4 android version 7.0 security patch 1 Aug 2017 Currently i m on stock rom nothing is changed now i want to root this device with magisk apps for this i read the instruction and the method i understand is that TWRP method but i m confused that magisk says that when i root with magisk i can update my device when ever samsung provide the OTA update but when i m going to install TWRP it says that it is custom binary and when ever i install custom binary i cannot install OTA update.

## Plssss explane this to me any one i m confused.

## I also read the instruction to install magisk without custom binary but i cannot find my device's boot image and also didnot understand the instruction properly.

## And plsss provide the TWRP for this device i search for this but cannot find the correct one including the instruction.

## If any other method is available to install magisk and root this device than plssss provide the instruction and file. Thanks in advance.

Sorry for bad english.....
[Magisk] xD2SH:
Magisk v15.2 bootlooped on RROS 5.8.5

device p9lite ( meticulous's last build 12/30 )

anyway to fix this?
[Magisk] DodoGTA:
Same here
[Magisk] fishnchips2:
15.2 finally works with my Huawei Honor 5c. Thank you topjohnwu
[Magisk] Markeee:
What I'm talking about is I have a business where I have paypal payments coming in all the time

I have paypal set for notifications to pop up when a payment comes in but for some reason its not working

I'm thinking maybe some setting I'm missing in Magisk is all ?

I think its a legitimate question again sorry if posted in the wrong thread
[Magisk] skttrbrain:
On Nexus 5X. Had no issues with any previous version but since updating to v15.2 the device has failed to boot (it just stays on the Google logo) unless I reboot it manually, which does get it to boot. Also any module I try to install doesn't actually seem to work but still shows up as installed. I have tried reflashing via recovery and it didn't fix it. Shame I didn't keep the v15.1 zip.
[Magisk] Didgeridoohan:
Doesn't seem like anyone has a definitive answer to that. Install and let us know...

You can use the Magisk Manager to patch a boot image and then use Odin to flash it to your device manually. That way you don't have to have a custom recovery installed. Any questions about installing recoveries or obtaining and flashing boot images to your device is probably best to ask in your device's forum... I'm just trying to point you in the right direction and will not be able to answer any questions about Samsung devices. Wouldn't touch one with a 10-foot pole. :laugh:

Logs (logcat, recovery log, magisk_debug.log, and so forth), boot image, etc... Any details at all would be useful.

That probably has very little to nothing to do with Magisk. I'd make a guess it's got more to do with Doze and Android battery optimisation (as in, remove the app from battery optimisation).

Logs, logs and more logs (logcat, recovery log, magisk_debug.log, and so forth) would be immensely useful.
[Magisk] Setialpha:
I'm also having the issue (on shamu/Nexus 6) that 15.2 does not boot, it produces a linker error, which I've seen in early 13.x beta releases and 14.x beta releases aswell. See attached log. [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] Didgeridoohan:
Is this on a stock factory image? I have no such issues on my Shamu, but I'm using a pretty pure AOSP 7.1.2 ROM...

Edit: Or wait a minute... Saw your message about Validus 8.1. Is it an Oreo issue maybe?
[Magisk] skttrbrain:
Good call. That said I may have been slightly rash - a full power cycle *seems* to have fixed it. I'll definitely post logs if it comes back though.
[Magisk] Setialpha:
On Oreo 8.0 it works and Magisk 15.1 did boot up aswell on a quick test. before updating to 15.2.. Though... you don't happen to still have the 15.1 zip, so I can actually test (I accidently already deleted it)?
[Magisk] habylab:
15.2 boots fine after using the direct update method. This is on the OnePlus 3, 8.0 latest beta.
[Magisk] Setialpha:
Hmm... might really also be a TWRP issue, after updating TWRP to 3.2.1 it suddenly works, maybe it wasn't properly flashed with TWRP 3.2.0 (didn't know this update existed a few minutes ago)?

Though, I have not tried any modules yet.

Edit: yes, it fails once I install any module
[Magisk] jhill110:
Here ya go....
[Magisk] Shadear:
Now with 15.2 update every thing work great thanks for your hard work ??
[Magisk] Setialpha:
I've found the actual cause: if services.sh tries to execute a script that does not exist for example $MODID/test.sh (which is actually $MODID/notest.sh) it doesn't boot, after fixing up the services.sh of the module in charge it booted normally. My quick test showed that 15.1 and 15.0 behave the same.
[Magisk] m_reyna_16:
Anybody having problems with magisk manager superuser... Everytime I press on the superuser tab it force closes... Problem has been happening since the 15.0 versions and I'm running a oneplus 3 on a 8.1 rom
[Magisk] RandomPooka:
Have you tried clearing data for the Manager app? That's what was fixing that before when people were having this exact issue.
[Magisk] m_reyna_16:
I've tried it with other previous versions... I'll try it again
[Magisk] DankaTanka:
I have problem with Magisk 14.3+ (14.3 is last worked version)

After this commit 4335c588fec05f0abefbd930ae39ea96e3b7e6fe MagiskManager can't access to db any more.

01-02 02:52:55.800 157 4041 E Magisk : sqlite3 open failure: unable to open database file
01-02 02:52:55.803 157 4041 E Magisk : su: cannot find requester
01-02 02:52:55.819 4042 4042 W Magisk : su: request rejected (10152->0)

Magisk mount success without errors.

My device Nexus 5, stock(6.0.1), twrp, cashes and data of MagiskManager are cleared, reinstall/uninstall many times without changes.
[Magisk] Simone98RC:
For OP3/3T users: the dm-verity error can be fixed with the only installation of Magisk v15.2?
[Magisk] illuminator25:
Hi all.

I've been successfully rooting my OnePlus 3 with magisk for a while now. That is, until the Android Oreo update, OxygenOS 5.0, came around. I've tried every beta and stable that I could find since v14.0 with no success (I tried patching the boot image once or twice too). Every time I would flash, reboot, and open the magisk manager to this screen (attached), where it would prompt me to install the latest magisk version again. I've also tried manually editing the boot image and adding a line that sets selinux to permissive.

Any help would be much appreciated.

Thanks in advance.

Edit: I might also add that when I flash a SuperSU zip, I boot into a black screen with a white notification led. That would also happen with every SuperSU zip I tried
[Magisk] hhwong:
Nexus 6p stock rom, elementalX kernel, magisk 15.2.

Adaway no longer works, it was working perfectly fine in 15.1, is anyone else having the same problem?
[Magisk] m_reyna_16:
Did not work, I cleared the data of the app and that didn't work... What works is un installing it and reinstalling it after every update but I update my rom about twice every 3-4 days and for me to be doing that is somewhat annoying lol
[Magisk] xD2SH:
this is magisk logs

also this is my boot img ( twrp back up ) after installing v15.2

https://mega.nz/#!c4pACT4K!5k2es66NB7IyG0dDfhEOh6XAmPXNMnYS2LsHHJF2_lE

and this boot img ( also twrp back up) with v14

https://mega.nz/#!t9oGyaob!UtMJ1ycDP_lzg_QhMmNsQhLuDpkyMjBSl6zr7Mw1VlI
[Magisk] m7md_ramadan:
-After installing magisk v15.2 i can't install any modules anymore

-Magisk V15.1 was working perfectly for me

I have Huawei y6 with Rom Lo 14.1
[Magisk] funm@sterz:
Guys,

I'm using redmi note 3 - 3gb /32gb version.

Right now running magisk 15.0 with magisk manager 5.5.2.

Agni kernel 11.9 miui.

Rom is miui stable.

I'm not able to install any module. Nor am I able to pass safety net. Please help.

Also attaching the screenshot of my magisk logs.
[Magisk] mnewiraq:
Any solution for folders decryption in twrp? My phon is honor 7x
[Magisk] u_no_fr:
Hi all

Still hav my pb with adaway... Blank screen and not asking for SU with magisk...

Thanks for your help
[Magisk] Xtriel:
Problems with mounting the system

My Magisk does not mount the system in RW, when the system changes, the smartphone hangs. Smartphone BQ Aquaris X Android 7.1.1 :confused:
[Magisk] ante0:
Trying to install magisk on Mate 9/Mate 10 Pro Oreo.

In installs fine (after decrypting: Format /data) but it seems the phones dont like 'init' getting modified... it ends in a reboot before bootanim.

Loop works fine as I've manually tested it by mounting magisk.img.

recovery.log has no errors in it (except for MtpServer but that's twrp).

Here are ramdisks (ramdisk is a separate partition from kernel):

Prepatched ramdisk: https://mega.nz/#!FSwFiLjJ!0S4KXAKSP76Vg6y4BuiyqJ_oyfkji8KHtRa9LCvCSeM

Stock ramdisk: https://mega.nz/#!FGYS2SpR!GrFiW5OOHL3ElObSFU13faMG8GIqI0Mejo-H8CsesoA

Fstab if needed: https://mega.nz/#!lKBhDYYQ!E8uPJ0_MLG1ViirP1xE1eSJcL-lC30wu4NwgbJtgTtw

Tested on Magisk: v14.3, 15, 15.1, 15.2

Recovery.log and dmesg.log can be uploaded if they are needed. They don't show anything suspected though.

Edit: i stripped the ramdisks of symlinks as they didnt want to zip
[Magisk] Souldrinker:
After upgrading to 15.0 a couple of days ago on my LeEco LeMax2 (AICP 13.1/Oreo 8.1) I experienced some annoying issues. When plugging in the power cable I no longer got the sound and the battery icon didn't change to a flash. Also my Tasker profiles were no longer acting upon power cable being plugged in, thus I didn't get bluetooth/car mode started as usual when plugging in the mobile to the car charger. A couple of days later Magisk 15.1 got released and after upgrading to that my phone got back to normal again. But this morning I got a notification about a new version of magisk manager and magisk 15.2 and installed that and now I'm back to the same issues again, that is Tasker is no longer triggered when plugging in power and the battery icon doesn't change.
[Magisk] nicolap8:
Hi all,

Moto G5 Plus stock (reteu)

with Magisk 14.0 worked well (sometime loses root but not often);

with 15.0 started to show the soft buttons bar even with fingerprint sensor active (so when not needed), this is a problem because hide part of the keyboard;

with 15.2 lost completely the fingerprint sensor!
[Magisk] Truely Simple:
I tried with my fingers crossed, as recently when I tried to install supersu, I was forced to Clear my phone, but Magisk worked and I am so happy. After trying to root my phone(lenovo K3 Note K50a40) with wide variety of ways, I was able to root my phone so easily, by just flashing TWRP and installing the zip.

Thanks a lot, topjohnwu.
[Magisk] czupakabra:
I have p9 lite VNNS-L21. When I used Android 6.0 and Magisk from version 11 safetynet was OK, google store reported that the device is certified and the application of my bank allowed to pay contactless. Now on Android 7.0 and Magisk 15.2, safetynet is OK, but google store claims that the device is not certified, and the bank's application does not allow paying by contactless. What could be wrong?
[Magisk] jkoch3:
It seems the Magsik is changing userdebug to user in ro.build.type though the build.prop file calls for userdebug. I need userdebug to get into QPST and I need root to change sys.usb.config to diag,adb. Is there a way I can change user back to userdebug?
[Magisk] daghaedd:
Magisk does not work with Adaway

I had installed Adaway 3.2 with chainfire under Supersu before Magisk. It worked perfectly.

With Magisk 15.2, Adaway doesn't work anymore. It is not registered with Magisk under Superuser.

What's wrong?

Kind regards

Dag

Adaway 3.2

Magisk 15.2

Magisk Manager 5.5.3
[Magisk] ad33p:
After 15.1 update my Samsung J120W's SafetyNet check and MagiskHide broken. But now with v 15.2 all things working again.

If anyone have problem with SafetyNet problem on Samsung device, update to latest version.

Thanks [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] Didgeridoohan:
Make sure you can pass SafetyNet, clear data for the Play store and then you might have to reboot. That should take care of the Play store certification.

For your bank app you might have to add it to the Hide list (if you haven't already) and also hide the Manager (option in the Manager settings).

Turn off MagiskHide. That's what's changing the prop value.

Or, you could put a script in /sbin/.core/img/.core/service.d with a resetprop command to change it back to userdebug.

resetprop ro.build.type userdebug
[Magisk] RandomPooka:
That is exceedingly weird. You're updating your entire ROM every other day or so? Lineage or one of those ROMs with nightly builds, or you just switching between a couple different ones to see what you like best.
[Magisk] Eng.Raman:
Installing magisk 15.0 / 15.1 / 15.2 gets the magisk manager to stuck at the splash screen, any suggestions ?

Device: Zenfone 2 (ZE551ML) / Stock 6.0.1
[Magisk] jkoch3:
Not sure quite how to do that. Just installed the app, never changed an option to hide anything. Appreciate the quick response!
[Magisk] Didgeridoohan:
MagiskHide is enabled by default. It's what's used to hide Magisk, MagiskSU and most modules. It also changes certain prop values if it finds one with a known troublesome value. Some apps won't work if ro.build.type is set to userdebug, as an example.

If you don't need MagiskHide, you should be able to disable it and reboot to get your userdebug value back.

Otherwise, put a file in /sbin/.core/img/.core/service.d, name it whatever you feel is applicable, give it execution permissions (chmod 755) and put the following line in it:

resetprop ro.build.type userdebug

That will keep MagiskHide running, but changes the prop value back to userdebug when the device finishes booting.
[Magisk] jenslody:
Magiskhide set to on in Magisk's settings is the default.

You can change it in MagiskManagers settings.

If that does not work (or you don't want to switch off magiskhide) try the second solution [MENTION=4667597]Didgeridoohan[/MENTION] mentioned.

Add a file called however you like to "/sbin/.core/img/.core/service.d" (or the symlinked "/magisk/.core/service.d"),

the file should contain the line:

resetprop ro.build.type userdebug

and make sure the file is executable.

That should force the build type to userdebug again.

By the way, you can also change adb settings in a similar script ( I do this on my phone also ).
[Magisk] u_no_fr:
Same for me :(
[Magisk] QkiZMR:
Motorola G5S Plus, Android 7.1.1, Magisk 15.2, Xposed 89, V4A 2.5.0.5. Everything works well for now. No errors in Magisk nor Xposed logs.

Sent from Moto G (5S) Plus via Tapatalk
[Magisk] m_reyna_16:
Yes I'm flashing the entire rom via zip file without wiping system and data every time... It's the same rom and the rom I'm using is nitrogen os.... So, FYI, when I said I would uninstall and install I meant to say that I do it via zip, the entire root, not just the magisk manager app
[Magisk] hasan4791:
Redmi note 3...After updating to latest version, safetynet check isn't working... Having this error
[Magisk] RandomPooka:
Do you only encounter the problem when updating the latest nightly?
[Magisk] Didgeridoohan:
https://xdaforums.com/search?query=safetynet api error
[Magisk] m_reyna_16:
Yes, to my knowledge I correct the problem and it happens again when i update the rom
[Magisk] Didgeridoohan:
Could be an issue with the addon.d feature... Try removing the Magisk addon.d script after flashing the Magisk zip.

Some logs of your issue might be good. I'm guessing you're updating your ROM through TWRP, so a recovery log would be nice. And if it keeps happening, a logcat when the Manager crashes is always a good idea.