yashsingh1/xdaforums huggingface dataset:
[Magisk] codblue:
same here on zte blade x9 running android 5.1.1
[Magisk] coldplug:
Thank you for the link! The forked version works flawlessly ?
[Magisk] Augustin79:
How does one download this from github?
[Magisk] coldplug:
https://github.com/pec0ra/AdAway/releases
[Magisk] cypher187:
Hi folks,

since I didn't find anything about my problem I try to find out what I done wrong - with your help :)

Context: Honor 8 (frd-l09-c432) running with ResurrectionRemix 5.8.4 made by OpenKirin-Team. Working perfect with magisk 14 and previous.

But I didn't get Magisk 15 and up to work properly. I tried many times in different way and setup. Every version.

Gatekeeperd is crashing. Fingerprint don't work. Lockscreen don't work. And I bet many more don't work - just didn't notice.

I followed these steps:

Installed Magisk v15.x via recovery (TWRP 3.1.1-1) and via MagiskManager (different versions, but every time with the actual version; now 5.5.4). Both ways - same result. Magisk is working (MagiskSU, MagiskHide, Systemless Hosts and several modules tested) but FPS stops working - as I never had one and it's impossible to change lockscreen settings. "Fingerprint" completely disappears from Settings / Security.

EDIT: If a pattern is set before I install magisk v15.x I cannot unlock my device. SystemUI is crashing every time I enter Pattern/PIN/Password and the FPS has no function.

Only way to get it back is to flash stock-boot. After that it's possible to install Magisk v14 without any problems and everything is working.

I tried nearly everything... Beginning in flashing the uninstaller zip and ending up in a clean install (after I flashed the stock EMUI boot image I was forced to format internal storage). I also removed magisk.zip from ROM-zip, deleted old MagiskManager from /system/ ...

I tried core-only-mode and disabled anything else which can be disabled - without success

I played around with dm-verity and keepforceencryption flags - also with no success.

What else can I try? What did I do wrong?

Logs are here (tell me if anything's missing): https://drive.google.com/folderview?id=1nTIPHsn7QazdVCVYmX_zxwrSLrz8Z4IV

EDIT2: I also uploaded bootimage to the same place - just in case

EDIT3: In case it's important: after successful installation of v15.x, reboot, device behaves like selinux=enforcing. In last_kmesg is shown that the kernel is started with parameter setenforce=1. Usually no problem except for this device. Behavior when switching to enforcing after reboot is exactly the same. I know, if it is like I think, it is primarily a ROM problem but has anyone got an idea to workaround? Since development for Kirin seems to be very hard...

Regards
[Magisk] One-ti-teuf:
[emoji41][emoji41]

Thanks for the links..

It work nice

Envoyé de mon HTC One M9 en utilisant Tapatalk
[Magisk] lp2yisdfu:
Latest update through Magisk Manager fails. 15.3.

Hangs on "flashing new boot image".

Trying to open other apps causes the phone to lockup and become unresponsive until reboot.
[Magisk] kalawy:
Didn't work

On magisk 15.3 now

Edit : it worked after deleting the app then installing .. The first time i updated it
[Magisk] spambayes:
I'm getting the same thing on Note 3 with Android 5.0. After the latest update to 5.5.4, Magisk Manager crashes when I go into settings.
[Magisk] AndrOmega:
no crash here.

5.5.4, Magisk Manager

14.0 Magisk
[Magisk] lalitjoshi06:
Magisk root works in f2fs data and f2fs chach. But module not loding. Is it works or not with f2fs data and cache?
[Magisk] Artim_96:
Let me guess, you have a Motorola device? Then there is a bug in their f2fs implementation. There is a module said to fix this but I haven't heard of any success yet. If that won't work you'll need to install a custom kernel that has the fixes
[Magisk] lalitjoshi06:
I have infinix zero 5. Mt6757 with 4.4.15 kernel. That module works only if chche in ext4 but mine is f2fs . if i format it to ext4 then stuck on splash then need again to flash it to f2fs to boot again. Thats why i ask?
[Magisk] Artim_96:
The bug might be the same, custom kernel should solve that. It's already proven by working when formatted to ext4
[Magisk] jasio2k:
Oneplus 3T

RR-5.8.5 (custom build)

Magisk 15.3

All good, but problem with f2fs data still exist, if I use f2fs for /data getting random system hangs and need force reboot, for ext4 all work fine.
[Magisk] lalitjoshi06:
No custom kernel available. Cant format ext4.

1. Format data to ext 4 loop to recovery not booting system. need to change data to f2fs .

2. Format cache to ext 4 stuck on splash screen. Need aging to change it to f2fs to boot.

No option till now. Any suggestion.
[Magisk] Artim_96:
Well then your quite screwed. You can try that module, I think it's called f2fs fix or something like that. But if data and cache are formatted you don't have much of a choice left and ext4 bootlooping means your kernel doesn't support it (for that partition). You should go to your device forum and find a solution there. In theory there are versions/modifications that let you install Magisk to a different directory. You you would need to find a partition that's not f2fs and that you can use for Magisk
[Magisk] Triviox:
Are some way to automate unroot /root if we open or clouse some apk? I hide root but wanna unroot when open some apk.

Thanks
[Magisk] Artim_96:
If you set an app to the blacklist, for all I know part of hiding Magisk is to simply unmount the magisk.img. so if the app is detected, you are basically unrooted. That's the most you can get without completely installing Magisk which would require a restart. Of course there are apps that still will be able to detect Magisk, but you don't be able to do anything about them unless there is a method found
[Magisk] Ex_FallenSkyTear:
i have installed 15.3, but he ask to me if i want install same version.

what?
[Magisk] Fredheg:
Me too !

I have Android 8.0 on primary rom ( with multirom) ans Android 7.1.2 on secondary rom.

The bug IS on secondary with flashs magisk15.3.zip fromage multirom TWRP. MAGISK APK 5.5.2 or 5.5.3 or 5.5.4

If i go go SuperSU Windows thé Windows IS empty. After eachvreboot i must re-autoris aller alication they bref Root

Box Can i résolve it ?

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[Magisk] Badger50:
Probably got that since you just updated the app to 5.5.5. Just let it install again, reboot, and you should be fine. Worked for me :good:
[Magisk] bigb159:
Any Magisk upgrade 15+ give my Xperia XZ Premium camera issues. Tap to focus does not work, and it will not take photos using hardware button or on-screen button.

Downgrade to 14.5 solves the issue.
[Magisk] Null.Dot:
Lenovo A5000 Build A5000_S125_170112_8G_ROW

Im using Lenovo A5000 Build A5000_S125_170112_8G_ROW and Magisk zip doesnt work on it saying "Unable to unpack boot image"

So i used "Path Boot Image" installation method, then it worked but it fails SafetyNet both basicIntegrity and ctsProfile after installing Magisk.

Already tried the following :

Core Only Mode

Universal SafetyNet Fix

Sensitive Props

Thank you for Making Magisk!
[Magisk] teddy0209:
Try to remove and reinstall magisk... Then check if magiskhide is working by using root checker app (like rootbeer)... If magiskhide is working, then you just need the right props to pass cts...
[Magisk] lalitjoshi06:
Thanx for suggestion.

I have only system partation in ext4 and modifications in system not gud idea i think.

So I have sd card currently in vfat. Should i format it to ext4 than could i able to use this to mount or use for modules.

Any help appreciated.

Thanks
[Magisk] gothicVI:
Same here.

Will try. Thanks for the hint.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] Null.Dot:
Thanks for the support, just tried it a moment ago, still no luck. I used magisk uninstall zip.
[Magisk] @raul:
If i go go SuperSU Windows thé Windows IS empty. After eachvreboot i must re-autoris aller alication they bref Root

Yeah.. and i was thinking it is only me..

I'm using xperia z1 (c6902) LP .236 rooted-Magisk 5.5.5 and V15.3 and having same issue(?):confused:

While granting permission it is FOREVER and next time may be after reboot it'll ask again.. So Please either correct me:p or help us:good:

It's my first post so pls help me if i'm doin somethin wrong.. Thnx in advance..

And Thanks to dev for this great app..
[Magisk] teddy0209:
Have you tried clearing Magisk Manger's data?... Try that, if it didn't work, might as well wait for a fix...
[Magisk] Didgeridoohan:
It's a small hotfix.

Have you made sure that MagiskHide works at all on your device? Can you hide root from a root checker (like the previously mentioned root beer) or an app that needs root access?
[Magisk] Null.Dot:
When i enable an app in Magisk Hide using Manager, then go back to home screen, then open the magisk manager then go to magisk hide, magisk manager i stuck on mask face and if i swipe it and open it again, the magisk hide list is not saved.

My kernel version is 3.10.54 and it is the stock image
[Magisk] Didgeridoohan:
So, in other words, things aren't working as they should. You need to provide logs.

Install Magisk beta to get the magisk_debug.log in /data/adb (post it after you've done all the things you mention and a SafetyNet test). A logcat from when the Manager gets stuck could also be useful.
[Magisk] Artim_96:
Reformatting is unnecessary since it's not f2fs. However it's probably still impossible since SD cards are mounted way too late
[Magisk] lalitjoshi06:
So no way for now to use module in this case.?
[Magisk] Artim_96:
Probably not, I don't know. That's way too device specific, you should ask in your devices forum
[Magisk] Didgeridoohan:
Probably means your TWRP isn't quite up to the task...

You should be able to direct install the beta by just changing the update channel in the Manager settings to Beta and then press install. Or do the same, but just patch the boot image.
[Magisk] @raul:
Have you tried clearing Magisk Manger's data?... Try that, if it didn't work, might as well wait for a fix...

Tried..

Settings-->apps-->magisk manger-->clear cache+data--> reboot

also wiped Dalvik & Cache from recovery. Reboot. Still no luck..

After clearing the root authorized app from memory or reebot and relaunch, asking for permission..

Any other suggestions or should wait for fix??:confused:
[Magisk] Null.Dot:
Does it mean that the TWRP installed in my device is not functioning as it should be? i tried the lower version of TWRP provided by different dev in my device from 4pda, it still says error.

Thank you for the support! Ill try to post magisk beta logs here after installing
[Magisk] derAndroidler:
Is this normal?
[Magisk] Didgeridoohan:
"com.google.android.gms.unstable" is perfectly normal. That's just Magisk hiding itself from SafetyNet.

The sqlite3 failure isn't normal though and might mean root won't work properly for you.
[Magisk] martyfender:
On an older version of the same tablet in my signature, with Magisk 15.3, Magisk Manager, 5.5.5, in settings, the Magisk Hide slider keeps getting disabled. I have tried deleting data and cache in settings, apps, magisk Manager. Does anybody have any suggestions? I could try the beta to get debug logs, if that would help.

THANKS

My bad, the recovery log is actually my backup rom restore with userdata deleted to start fresh, since Nextbook never releases ROMs.

at /data/data/co.topjohnwu.magisk/shared_prefs/com.topjohnwu.magisk_preferences.xml, magiskhide value shows as false.
[Magisk] Didgeridoohan:
Yes. Yes it would.
[Magisk] derAndroidler:
But what does unstable mean here?

And why I get this sqlite error?

I have lineage os from sultanxda on one plus 3t
[Magisk] saspo59:
Don't know how but i updated to 15.2 magisk and to 15.3 with no problem but the magik manager is stuck on 4.4.3 how to update magik manager please?

I am on Nos 8.1 3t fhone.
[Magisk] Wolfcity:
Extract it from the common folder inside the magisk.zip and install it as usual.
[Magisk] saspo59:
Thanks for replay i traying to install mgick manager 5.5.5 .apk and it saying not install
[Magisk] Didgeridoohan:
That's just the name of the package. Don't worry about it...

Don't know. Closest I've come to it during my tests to reproduce what seems like a possible issue on Android 8.1 ROMs is that I sometimes see that on the first boot, but then it's not there on subsequent boots.

Do you happen to have an unofficialy built Manager installed? Uninstall your current Manager, download the latest version from the release thread and install manually.
[Magisk] Duden17:
Hi guys, I always fail pass safetynet after flash magisk.15 above. In my case magisk 15.3 success installed but my safetynet always break. Any one can help me. my device Redmi note 3 Mtk or hennessy. I am using Rom xiaomi.eu stable lollipop 5.0.1. Please help thanks.
[Magisk] saspo59:
Ok i uninstall old 4.4.3 and reinstall ver 5.5.5 all ok but the apps thst need su permision keep asking for permission and the tap of su remain empty ,what i have to enable for that
[Magisk] Didgeridoohan:
Superuser database issue... You'll likely see some sqlite3 errors in the Magisk log.

Do you happen to be running an Android 8.1 ROM? Seems to be a prevalent issue on 8.1 ROMs...

You can try reinstalling Magisk. Use the uninstall option in the Manager and do a complete uninstall, or use the uninstall zip (from the release thread) in recovery, before installing v15.3 again.
[Magisk] hemantv:
Hi! I'm trying to create a Magisk module for enabling navigation bar on my device. I added the necessary property with its value in system.prop, set the PROPFILE to true to load the file. Except that it doesn't seem to be working.

qemu.hw.mainkeys=0
ro.product.model=Nexus

getprop qemu.hw.mainkeys is still returning 1. The product model seems to have set properly though. Please help.

One thing I tried was to create a file under /magisk/.core/service.d/ directory and set the command using resetprop.

resetprop qemu.hw.mainkeys 0

This seemed to have work properly and navigation bar was present after reboot. My device is Mi A1 running stock 8.0 build.
[Magisk] Sony92:
[MENTION=4470081]topjohnwu[/MENTION]

can you please fix in the next version that twrp in android oreo no longer loses the internal memory access?
[Magisk] PokemonTotalWar:
Does anyboxy else seem to have a problem booting any time they enable a module that adds to /system/xbin? I'm not sure how to get a log without being able to boot, but that seems to be the problem with the busybox module, as well as one I've built myself. A user came to me for help and I wasn't sure what was wrong, but I just updated to a 8.1 ROM and I'm now having the issue as well. Changing the mount point to /system/bin/ fixes the bootloop. Thank you!
[Magisk] Eversmile23:
module not working.

I had flashed 'magisk init.d enabler by android_expert', found the name of the module with tick marked on right side inside magisk manager. Then I tried to implement a MOD by manually copying and pasting some files in '/system'partition. It worked. But after making a reboot, I found the init.d folder that existed(after flashing the mentioned module had vanished, but the name of module with tick mark still existed in magic manager(version 15.3). Why does this happen?
[Magisk] n.p.:
After an aborted (very brief) attempt to use Magisk several months ago (I had to return to the previous ROM, and never got around to re-installing it), I made another effort last week.

It has really been a tale of two devices. On the first (Samsung Galaxy Tab 2 - p5110), everything has been completely flawless. No problems installing or updating, SafetyNet check passed, everything working exactly as it is supposed to (so far - I haven't tried installing any modules yet :) ).

The second device (Bluboo Maya Max - pri6750_66t_m) has been an absolute nightmare. Although these devices are quite different, they are actually almost identical in terms of software (both running LinageOS 13.0). It required several attempts to install - and I am always getting "Invalid Upgrade Channel" messages (even though I have stable selected), which (let me know if there is a workaround) requires me to go through the painful process again. It crashes all the time ("Unfortunately, Magisk has stopped"), have never been able to pass the ctsProfile portion of SafetyNet (still attempting to troubleshoot that), and the manager will no upgrade Magisk. It appears to succeed (as far as I can tell), but when I reboot the phone, it still has the old version. Ended up uninstalling everything (again), and booting into recovery several times to flash the new version, and finally update Magisk Manager.

I am going to attach the log of the attempted upgrade from 15.2 to 15.3 (which appeared to work but didn't) in case someone has any thoughts, or it might be helpful in tracking down the problem and/or fixing a bug.
[Magisk] martyfender:
I may have solved the issue, I am keeping my fingers crossed. First, I deleted the app data and cache, uninstalle Magisk Manager 5.5.5, rebooted to twrp and deleted cache, dalvik cache, then restarted. I then rebooted, reinstalled v5.5.5 and magisk hide slider was still disabled after re-enabling it. I then checked app permissions. The app permissions for storage were turned off. Most apps that need storage permissions ask for it when launched, Magisk Manager, does not.

I turned on storage permissions and initially that didn't fix the problem,but later, I tried and it appears the setting eventually stuck. I unplugged the charger, let the device doze for a while, woke it up and, so far, so good.

Why doesn't Magisk Manager ask for storage permissions? Is it a bug, or a bug in my device and ROM?

Thanks

I am waiting to install the beta, debug build, until I see if the settings stick, long term.

I would rather stay on the stable, as the beta appears to have no new fixes over the current, stable, version. They appear to be the same build, the difference being debugging code?

The settings seem to have stuck through a reboot and a short period of time, so, far, with the granted storage permissions
[Magisk] Powita:
Hey bro is possible to add "network speed indicator" module to magisk repo?

Thanks in advance!
[Magisk] Didgeridoohan:
Are you sure there aren't any typos in the system.prop file?

To troubleshoot, you can install the beta build of Magisk v15.3 (only difference is verbose logging) and take a look in /data/adb/magisk_debug.log. There you can see if the prop gets set or not.

There is so extremely little information to go on in this post that it's impossible to know what kind of issue you have. All my devices are on Oreo and I have no issue accessing any part of my device in TWRP...

Does your device have TWRP baked into the boot image? Do you have any logs? More details? You're going to have to give some kind of info showing that it's Magisk causing an issue before there's even a possibility of a fix from topjohnwu's side.

Longshot, but does your device have a /system/xbin folder by default? It should, but if it doesn't, letting Magisk mounting files or folders (that doesn't already exist there) directly to the root of /system can cause bootloops.

That's a very outdated module by a user that hasn't been a member of xda for a long time. I don't think there are any current init.d modules available...

Unless you specifically need init.d (because some app looks for it), you can use Magisk's boot scripts instead.

Place your scripts in /sbin/.core/img/.core/post-fs-data.d or service.d (depending on when you want the script to run, see the docs for info), give them proper permissions and you should be good to go.

I'm not sure if you're saying that you have things working or not. I get that the update attempts failed, but does it work after uninstalling and reinstalling?

The log you posted doesn't show much, unfortunately.

The Manager does ask for storage permissions when it needs it. That shouldn't have an impact on the MagiskHide setting though...

It would be interesting to hear if you keep seeing any difference now and if you can try to reproduce the issue by toggling storage permissions again. With logs, of course.

Hey "bro". Nope.
[Magisk] skymera:
Seeing Magisk errors with su.db and no app are being remembered under Superuser.

Using F2FS.

Seems as though some recent F2FS commits breaks Magisk. Can anyone else confirm ?
[Magisk] hemantv:
I'm pretty sure it was not an issue of typo as I tried it several times. The method which finally worked for me was to add the command to service.sh .

resetprop qemu.hw.mainkeys 0

The property qemu.hw.mainkeys isn't actually present in /system/build.prop. Is that the reason why it makes no effect via system.prop?
[Magisk] Didgeridoohan:
Actually, the system.prop feature just runs the resetprop tool, just like you did with your service.sh script. So there shouldn't be any difference. Only thing I can think of is timing, because they run at slightly different times.

It would be very interesting to see that magisk_debug.log with the prop in system.prop...
[Magisk] saspo59:
Me too,i am on ext4, no aplication is remembered in su tab,try all what i know unistall from app and from twrp no lack when ever i uninstal with zip file in twrp i cant even instal magic at all help please
[Magisk] hemantv:
I'd like to help debug this further. How can I flash the beta Magisk zip? I don't have TWRP installed.
[Magisk] Crapping_Bricks:
Hi everyone,

I recently noticed that magisk has a forced encryption prevention setting. After noticing this it was also discovered that my Google Pixel 2 is also encrypted by default. None of my previous phones have had encryption. I was wondering, does encrypted storage cause any issues with magisk, its modules, xposed and its modules, or any TWRP backup and restores and finally any root apps/functions. If it does then should i bother resetting my device to prevent encryption with magisk?

Any help is appreciated
[Magisk] Didgeridoohan:
Change update channel in the Manager settings to Beta and then do a direct install or patch the boot image for manual flashing.

Standard Android encryption shouldn't cause any issues with Magisk. Sometimes there are TWRP issues, or similar, but mainly when devices are new or there's been major OS updates. But, best place to find info on that is in your device's forums.
[Magisk] Andulea:
Hi, I have installed Magisk on my Samsung Galaxy S6.

In the previous versions, I was losing root after 15 minutes that I enabled Magisk Hide. With the recent versions, instead, when I enable Magisk Hide and I close and reopen Magisk Manager, Magisk Hide is disabled, but it works. The problem is that after about 1 day the root goes away. I already tried to uninstall and reinstall it, but it didn't worked. (Some time ago, I accidentally uninstalled the Manager and, after reinstalling it, when I opened it, it was continuously crashing. A complete uninstall and reinstall fixed it).
[Magisk] hemantv:
Thank you. Installed the beta version by following the above steps and pulled the magisk_debug.log after enabling module. It seems to be identifying it as new prop and calling setprop after it. Please take a look at it.

EDIT: log file size is slightly larger than max allowed. Pastebin - https://pastebin.com/ZTU47b9Y
[Magisk] Didgeridoohan:
You sure that's the right file? I see nothing about Magisk in that log...
[Magisk] hemantv:
Sorry, the file was truncated. I've filtered the Magisk only logs and attached the same over here.
[Magisk] rebeldu34:
Hi,

I did not find information on this thread, also I ask the question : Does it work on Huawei Mate 10 Pro?

:confused:

Thank's.
[Magisk] 4ndr0x:
When checking for Magisk updates with the 5.5.5 Manager, I'm getting "Invalid Update Channel" instead of a download prompt. Anyone else having this issue?
[Magisk] Clint Ryan:
hi, any possible solution how do i pass pass safety net on the latest magisk v15.3?
[Magisk] Didgeridoohan:
Log looks fine. It's running resetprop like it should...

I'm curious though. Initially you said that getprop qemu.hw.mainkeys returned 1. But, according to your log (and what you said about it not being in build.prop) it's a prop that's not available by default on your device. How can it then be set to 1?
[Magisk] walid77dz:
Hi,

not working on lenovo vibe c2