yashsingh1/xdaforums huggingface dataset:
[Magisk] Hippie459MN:
Yeah, I updaed to this firmware and rom as its the latest build from Sprint and so far its the only rooted/deodexed rom on this build that I know of. Also, there was not a very good list of stuff included in the rom build. But I agree, I am not a fan of when this stuff is pre-installed. As for xposed, I have always used that and it worked for my needs but right now, if I can get this figured out, I will give this go.

I will dig up the uninstaller and make a full backup in TWRP and then uninstall and try to install the latest version. Thank you for the help!
[Magisk] Didgeridoohan:
I just want to point out that Xposed and Magisk are two very different things and you will not be able to do the same stuff with Magisk as you can with Xposed. Just so you don't have any unreasonable expectations... :good:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] martyfender:
If you need to use apps that detect if Safety Net passes, or not, then you will have to remove xposed, otherwise, it should not be a problem. There is a Magisk Module for it, also.

This is just a hunch, but the deodexed rom could potentially be part of the problem.
[Magisk] Ratbug:
No SIM card detected after root

Help! After rooting my SM-J730F with Magisk my SIM card is no longer detected and i get no service. I installed a stock 8.1 android rom and my phone was working fine. I installed twrp and my phone was working fine but after flashing Magisk via twrp my phone no longer detects my SIM card. I've tried the 17.1 and 17.3 version but it's the same result each time. The root is working fine though. What can I do here?
[Magisk] chooks06:
Reboot the phone and see what happens..

If you did a backup with be TWRP, before installing Magisk, you can try restoring it.

Then check through whether you installed Magisk correctly.
[Magisk] guest4711:
Try the canary builds (https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337/post77549897) or the unofficial daily builds (https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901/post70157494). Hopefully your problem is fixed there.
[Magisk] hernan32:
After flashing with patched boot, im getting no signal.

Stock roon

8.1

J7 prime 610m
[Magisk] Hippie459MN:
Well, I checked with a file explorer and found the back up of the original boot image so I went ahead and ran the uninstaller then installed Magisk 17.3 and then rebooted and installed/updated the Manager to he latest version in the first post and everything is working! It passes SafetyNet now and I can see all the modules available in the Downloads and I tested it out and installed one and worked like a champ! I think I am starting to understand better now that I have been had to dig deeper in to this. Thank you everyone that helped or gave me some advise.

Yes, I do use two Xposed Modules and one of them does require to uninstall xposed to log in to the app but thats no problem. Thanks for your help! Certainly a learning curve but now that I got it sorted out im getting a much better understanding of its workings. :)
[Magisk] Ratbug:
Update: I cleared the cache after rooting and it solved my problem!
[Magisk] mordantly:
Deodexing can fail safetynet check?
[Magisk] Hippie459MN:
Im on a deodexed rom and the Magisk Manager says it passes here.
[Magisk] chooks06:
Great!
[Magisk] mikmpaok:
hello

i have xiaomi mi6 with custom rom from xiaomi-miui.gr forum( XTRV8-11-8 aroma) with superSu inside the rom

i've tried to install magisk 1.71 and 1.7.3 from twrp but icant install it because said error in the end

any idea how to install the magisk?
[Magisk] Wolfcity:
You have to get rid of SuperSU before you can flash magisk successfully as they don't work together. Best way would be flashing the unsu.zip: https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post63615067

You can also try to uninstall SuperSU by it's own uninstalling mechanism but as it is baked inside your ROM the unsu.zip may be the safest way. After that flash your stock boot.img (should be found in your custom ROM) and flash latest magisk from TWRP as usual.
[Magisk] braschlosan:
I recently updated magisk and I don't know if this is related but I have a red error log style overlay that I can't seem to get rid of. Can anyone help me? The overlay returns shortly after a reboot and it's very difficult to use the phone
[Magisk] chooks06:
Could it be that the "color inversion" setting was turned on?

It's in device settings - accessibility. Somewhere at the bottom where you can find option for high contrast text (menu setup depend on version of Android). It's generally in there somewhere, else might be found in developers settings.
[Magisk] braschlosan:
Good guess. I found the setting and it made the image even worse haha
[Magisk] chooks06:
Haha! Supposed to turn it off.

There's a warning there about affecting performance.

Good thing no major disaster.

My bad.

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

Try uninstalling Magisk in recovery using Magisk uninstaller zip.

Then install again. Latest stable version is 17.3.
[Magisk] Crescendo Xenomorph:
Strange Bootloop...

My phone Mi 5s Plus - MIUI 9.6 Nougat 7.0.0 - TWRP 3.2.3.

No modules installed.

First boot it SOMETIMES bootloop (1st splash - 2nd splash for some seconds - reboot), repeated randomly (90% of the time).

Sometimes 1x, other time till I lost count of it before it successfully boot.

Sometimes it just boot properly without any bootloop (rare).

This also happen everytime after I add/remove/update modules.

Eventually it will boot but before that happens, it bootlooped so many times.

It also left so many orphaned inodes on /data after those bootloop.

I tried to re-flash the whole ROM but the problem remains.

The most puzzling: I have another same phone with same configuration without this problem.

Could you please analyze the log and maybe can tell me what's wrong with it?

Meanwhile back to old trusty SuperSU.

Thank you.
[Magisk] HRider4:
Hey man, could it work as well on Redmi 5?

I thought it should, right? My device is Redmi 5 and i really need to install Magisk. When i tried to flash v17.1 through TWRP 3.2.3, i got this return code error: 1 instead. Oh and yeah, what is it about the uninstall.zip anyway? It took time to surf into this thread pages. So, i jump right into search column and type 'redmi 5' on it and found your post. So i skip it. Anyway, you might have some solution for me man?

Thanks
[Magisk] scorpionvert:
Hello, you have to flash lazyflasher after TWRP, then you flash after magisk zip.

Here is the link for lazyflasher https://mega.nz/#!jV9WgKCL!JBBF2qFviFXMKM4g8CyPLtdzkN3Be5mguMtrVhYPuPE

Tell me if all is OK. Best regards
[Magisk] blake .l:
Trying to install Magisk on my Nexus 6P stock Android 8.1.0. Magisk installs fine but after install the phone becomes unusable, I lose all network functions, no internet, calling nothing. I can turn airplane mode on then off and I get full function fo around a minute or so then its back to nothing. I have to repeat the above to get it to work then its the same thing, works for a minute or two then nothing?? I tried installing 3 times and the same outcome, I can go back to stock and the phone works flawlessly??? Phone is on T-Mobile running 8.1 stock Oreo on the November 2018 security patch...
[Magisk] martyfender:
Have you tried wiping the dalvik cache and cache in TWRP then rebooting?
[Magisk] blake .l:
sure have, several times. I also made sure each time i installed it was a clean install.
[Magisk] demonoidmaster:
got any modules? Are you using 17.1 or 17.3 beta?

Check the magisk logs if there's anything that looks odd or post it here
[Magisk] Grin59:
Is there a app request thread? I don't wanna update to android pie due to there being no xposed. The only app I really want/need is xprivacylua. So since there's no xposed, I wish there was a magisk version.
[Magisk] guest4711:
Forget it, man. XprivacyLua requires xposed to work. Have a look into the xprivacylua thread, it's discussed a lot of times why Magisk can not replace xposed... (see https://xdaforums.com/xposed/modules/xprivacylua6-0-android-privacy-manager-t3730663/post78173533 )
[Magisk] Grin59:
Okay, thanks anyways. Guess I'll be on Oreo for a while then
[Magisk] habylab:
Seems bizarre though, must be a difference in our setup somewhere. I'm using Auto Magisk, and trying the cancel adding card method.
[Magisk] Captain_Throwback:
That folder/file is in the boot.img ramdisk. That's why there's a Magisk-specific version of phh's Superuser to be flashed that installs it as a Magisk module.
[Magisk] HtHNightwolf:
Has nothing to do with disabling the whole framework.

I did the same but AutoMagisk can not help if Magisk is not the problrm but the framework is

Supertoll gesendet mit Tapatalk
[Magisk] ZjemCiKolege:
Any users from lg g3 d855 ? only i have bootloop ?
[Magisk] 4RK4N:
can xposed be unmounted by user action (or shell command) like with root? or wouldnt that help since its the same as lazy unmounting it ?
[Magisk] Captain_Throwback:
I'm pretty sure that's the first thing [MENTION=4470081]topjohnwu[/MENTION] tried, lol. If it was that easy it would've already been done :).
[Magisk] quini2k:
My son's Xperia L (C2105) with unlocked bootloader & unofficial cm13 keeps booting to twrp after flashing v6 + supersu 2.78, and won't try booting to system.

Being a Sony I was just trying, as you've written that some Sony devices won't work.

I don't know if it's useful, but it seems that Sony devices doesn't have a recovery partition, and twrp has to be flashed to boot instead (fastboot flash boot twrp.img).

Thanks for your work! :)
[Magisk] mrvearn:
Bootloader unlocked?
[Magisk] shawkes:
Did you bump your boot image after installing?
[Magisk] Deep Diver:
:confused:

Any help plz
[Magisk] SidneyD:
Yes Phh's SuperUser app was installed from Google Play Store. I'm probably using the wrong terminology, but when I said Magisk didn't prompt for root, I mean that no root manager application appeared to give me the option to allow root.

I've detailed my steps in my original post, and I don't understand why it doesn't work for me the same as it does for others.

---------- Post added at 11:34 AM ---------- Previous post was at 11:30 AM ----------

Yes, as I detailed in my original post, in my first attempt I tried using just phh-superuser-17-magisk.zip but either no root binaries were installed, they weren't properly mounted, or Magisk was unable to see/mount/unmount them.
[Magisk] ZZZZXCC:
will 0.7 compatible with other devices? :crying:
[Magisk] azsde:
Xposed is now detected :(
[Magisk] Gungrave223:
I've been getting the same since yesterday

**Edit**

Looks like SafetyNet was update to check for Systemless xposed...smh
[Magisk] Opticuhl:
I've switched to using Suhide since then, works well for bypassing Safety Net.
[Magisk] juangcardoso:
Man, can u please share the link to download the uninstaller of root?
[Magisk] teddy19.teddy:
I think so too, did the whole process yesterday evening. Everything worked fine until lunch. SafetyNet Helper now just gives back "Response payload validation failed".

I'm using the latest CyanogenOS with Magisk v6, phh's root and systemless XPosed.
[Magisk] Triviox:
And, with suhide, can use xposed without Safety Net fail?
[Magisk] Opticuhl:
[MENTION=4635364]Triviox[/MENTION] Not sure if you can as of today, but it was working yesterday. I'll give it a try and let you know.

(Reply function isn't working for me right now :/)
[Magisk] BadWithPhones:
Is this thread for module writing support too? If no, sorry and I will keep looking for a thread for it.

If yes, I am having issues with Magisk not replacing/overwriting an apk that I modified that I want in /data/app/my.app.here

The base.apk does show up in the magisk.img (under modID/data/app/my.app.here) but not on my phone under /data/app/my.app.here (only the original one shows up here). Automount is set to true. The only other module that I use is busybox (which appears to be working fine).

(the my.app.here example is more like /my.app.here-B96mB_g9a==/ on my phone)
[Magisk] Didgeridoohan:
Magisk modules do not mount files to /data, only /system.
[Magisk] BadWithPhones:
There goes that idea.

Thanks for letting me know now I just need to find a solution that is easier than backup apk+data -> uninstall -> install moded apk -> restore data only
[Magisk] mikmpaok:
thank you . i did it
[Magisk] moloko01:
Got problem with LOS 14.1 and magisk on my Galaxy Tab Pro (SM-T320). Some games (the room, etc.) crashing by startup. Any solutions?
[Magisk] guest4711:
Add these apps to Magiskhide, clean the cache for these apps and retry. If this does not help, clear the data of the games, too (after backing it up).

If this does not solve your problems post logs.
[Magisk] moloko01:
Sorry, this don't helps.
[Magisk] guest4711:
Check [MENTION=4667597]Didgeridoohan[/MENTION]'s fine troublechecking guide: https://www.didgeridoohan.com/magisk/HomePage

If this does not solve your problems post logs. Nobody can check what happens on your phone without proper logs ...
[Magisk] vMAC:
Is there anyway to tell what module or when something has changed system? Every month I try to do the easy update but the system doesn't find an update available. I'm need to find out what is editing my /system. Is there a module for that? Could Magisk Manager potentially report when something edits /system?
[Magisk] raptorddd:
having problems with magisk 17.1 and 17.3 beta

my phone hangs at times for like more then 30 seconds. redmi note5 miui10 .

does magisk have confict if i disable logd.? whenever i disable logd it hangs.. but phone works ok if i use version 16.7 with logd disabled ???

wish to use latest.
[Magisk] bunklung:
Has anyone got the Dec Pixel 3 OTA notification or manually checked and found an update with the check button?

I have not been able to get OTA notifications for months on my Pixel 2 and now Pixel 3. Maybe I am just jumping the gun on the Pixel 3.

Is OTA broken with Magisk? It was working fine at one point for me.
[Magisk] martyfender:
You need to have logd enabled. Disabling it is known to cause high cpu usage, which would cause a hang. I really don't understand why anyone would disable it, I don't believe there is much overhead with it enabled.
[Magisk] jcmm11:
TWRP. Move original apk to sdcard to back it up. Replace with new apk. Done.

You might be able to just do it with a root explorer and skip TWRP. You'd still, obviously, have to reboot afterwards.
[Magisk] raptorddd:
been a user of superSU when i first tried magisk i remeber the high frequencie.

logd gives meore SOT and performance. thays why.

but like i said 16.7 ot works strange.
[Magisk] xunholyx:
Did you reboot after clearing data for it/them?
[Magisk] Deepso7:
Setting has stopped :confused:

How to fix on miui 10 RN4
[Magisk] martyfender:
What? That is about a vague as you can get! How about doing a good English translation!
[Magisk] firozpatel:
Hi guys, I was wondering if you can resize magisk, I have adaway installed and a message keeps saying not enough space, so I did some research and some people are saying magisk size is to small, any ideas?
[Magisk] HRider4:
Okay, i'll try and thanks for the link. i'll keep you updated man

So there's no need to wipe anything right?. Cause i read this crazy idea that i need to go back to miui ROM first. Haha.

Update:

So i already flash the lazyflasher and again, try to install magisk v17.1 but it didn't do any. It always returns the same error code. Error code = 1. You might have another solution man?
[Magisk] moloko01:
Okay, here is my magisk log. Please have a look.
[Magisk] jcmm11:
https://topjohnwu.github.io/Magisk/tools.html

See imgtool entry
[Magisk] Ev0luti0n_:
Hey guys. Having a strange issue with my magisk install. Everything works as it should, but everytime I reset the app gets some issue and it YouTube disappears, xposed gives me a yellow status bar, and Greenify stops working too. Restarting again the phone, makes everything work back to normal. Any idea what's going on here? Feels very odd.
[Magisk] Hippie459MN:
I was doing some reading and I seen where I can possibly downgrade to 16.0 without having to uninstall Magisk first. I have a module I would like to install that works perfect in 17.3 but wont install and need 16.0 as the install package hasnt been updated. So I guess what im asking is, can I just flash 16.0 over 17.3 then boot to phone and install the module, then reboot into recovery and flash 17.3 over 16 or do I need to uninstall for each version? Just want to triple check before I go ahead.

Also, is there a way to back up the root app setting so I dont have to reconfirm root in all my apps again?
[Magisk] jcmm11:
Why don't you just update the install package? It's usually not very difficult to do, although the exact details depend on the package. It may be as simple as updating module.prop and replacing update-binary.
[Magisk] Hippie459MN:
I will check that out. But being VERY green to this Magisk stuff, I honestly have zero clue how it all works when it comes to the way the modules install or how the installer is written to install properly. I will start there though. Thank you.
[Magisk] jcmm11:
What's the module? Attach a copy and I'll take a look.
[Magisk] Hippie459MN:
There is a newer version that will install but it doesnt play nice with Samsung so this version is needed but the installer doesnt install on anything over v16.0

Thank you!

Some reason it keeps timing out when I try to upload it here so here is a link from my server - http://www.hippie459mn.com/fileuploads/xposed-v87.3-sdk23-topjohnwu.zip
[Magisk] cmch:
Suggest me some awesome modules for pie custom rom :angel:
[Magisk] yochananmarqos:
I suggest you look through the Downloads section of Magisk Manager and my Collection of Magisk Modules v2 thread pinned to the top of this subforum.

This is a Magisk support thread, not Reddit. Let's not clutter it with off topic discussion.
[Magisk] firozpatel:
I found a much easier way to do it, download Magisk manager for recovery module

Thanks for your help, much appreciated
[Magisk] Ingan121:
Security engine v5.0.1 detects Magisk

[IMG="Screenshot"]https://xn--s39ap43c.kr/img/Screenshot_bithumb.jpg[/IMG]

SafetyNet is passing (both ctsProfile and basicIntegrity) and MagiskManager is hidden, but it detects 'Magisk' (Not for other reason such as SELinux). MagiskHide doesn't work, and my device is not vulnerable to ProcGate, too.

I could easily bypass security engine v5.0.0 with Magisk 17.2+, SafetyNet pass, MagiskManager hide, and MagiskHide, but this one is hard to bypass even with 17.3.

Link of an app that uses security engine v5.0.1 / v5.0.0
[Magisk] smtaba61:
Hi guys

sorry for my dummy question! I studied and searched a lot but couldn't find the answer so I was wondering if someone could help me here

I am having LegacyXperia which is based on cm13 on my wt19i. The latest stock rom is ISC so basically there is not the stock boot. Also there is not TWRP for this rom just CM recovery. however I tried to delete the internal root by unSU.zip and flash the Magisk.zip but it gives the status1 failure.

Is there any hope and chance of having Magisk on my device?!

I am looking forward to any help I may get
[Magisk] Didgeridoohan:
If you can test it on the latest Canary build with the Manager hidden and it still detects root, check here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Please note that the error status 1 you mention means nothing without the corresponding log... But, I'm going to take a wild stab in the dark and guess that this link will be applicable to your case:

https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
[Magisk] alecthenice:
unable to install modules

I have patched my boot.img with magisk manager and did a direct install while respecting DM-verity. Now I can't install any modules "install not allowed" do I have to change something in the ramdisk file in the boot.img to enable install? I really just want to enable gapps on an uncertified device by some means. Thank you!
[Magisk] Didgeridoohan:
Logs are usually a good way to provide information that would be useful for those that might be able to help...

Take a look here:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] blake .l:
Tried again from a new install of stock 8.10 except this time I went with 17.3 beta and all seems to be working fine so far. I am having one small problem though, everytime I restart the phone I have to reinstall busybox cause for some reason it's like it uninstalls when you restart. Any ideas???
[Magisk] jcmm11:
Give me a day or 2 and I'll see what I can come up with.
[Magisk] Hippie459MN:
That would be great! Thank you!
[Magisk] martyfender:
Is ISC actually ICS or Ice Cream Sandwich? If so, Magisk will not work on it. The minimum Android version is 5+.
[Magisk] shamsul007:
Hi, I'm having an issue regarding magisk manager. In an attempt to play Pokémon go, I followed some directions that told me hide magisk manager and clear repo. I know have two magisk manager apps (one of which opens and functions perfectly,) the other stays stuck on the splash screen. Every time I attempt to restore magisk manager with original package, it begins a download which stops a quarter of the way through. I've also downloaded the latest manager online and installed and this hasn't solved the issue.

It's not affecting any of my hidden apps. Banking apps work perfectly. I'm just worried down the road it might cause some issues. Some help would be appreciated.

Thank you.
[Magisk] kindrich:
Does the latest December 2018 update break Magisk for anybody else besides me?

Pixel 2 XL, stock everything. My normal routine to update the phone every month: flash full the full firmware, boot to TWRP, flash Magisk. Everything works great as far as November 2018.

However after updating to December 2018 update, flashing Magisk puts my phone in a boot loop, i.e. stuck at the G logo for a long time then reboot. Uninstall Magisk and the phone boots up normally.

I've also tried 17.3 and same issue applies.
[Magisk] Pkt_Lnt:
Here are two things that *might* help, since you did not detail your install procedure and if you have any modules. Some are known problems if not updated.

https://twitter.com/topjohnwu/status/1070029212428439553

https://twitter.com/j_to_the_4n/status/1069900562601254912
[Magisk] Hippie459MN:
Nevermind...
[Magisk] smtaba61:
my mistake! it's ICS. But Legacyxperia is a ported rom that is based on CM13 that means android 6.1
[Magisk] Satzz:
New version of Playstore possibly doesn't work with Magisk anymore and still shows device is uncertified even though the Magisk CTS is passing the Safety net.

Tried with the beta version as well, for time being back to stable.
[Magisk] loadie:
Have you tried clearing cache and storage?
[Magisk] jcmm11:
Mine is working fine. 2 things

1 - I'm running the canary build (which may or may not matter, see 2)

2 - try stopping Play Store, clear it's data/cache, reboot. May take a little while to show any certified/uncertified status
[Magisk] LeMoise:
I usually Magisk Hide root from the Play Store and Play Services, then clear the Play Stores cache and storage. Upon opening the Play Store again and waiting a minute it says it is certified again.