yashsingh1/xdaforums huggingface dataset:
[Magisk] djmcnz:
Good work on the logs, I wish more people would make the effort.

I'm not Magisk dev/guru so hope I'm not stepping out of line here...

It looks like you've got a kernel (or hardware) problem. There's a possibility that cleaning up Magisk as you have may have borked the kernel (not your fault).

The logs reflect a LOT of hardware failures and unless you've dropped/submerged your device they're unlikely to all happen together. The kernel is an interface to your hardware and a problem there could manifest as (apparent) hardware failures. Magisk modifies the kernel so if that's somehow gone wrong, it could explain your bootloop.

You're running LineageOS right? Do you have a stock kernel you can flash? If not, try and find one (Lineage thread) and flash that (if you have no ROM mods, or all your ROM mods are systemless you can flash the whole ROM). Make a backup of your important stuff first, worst case is you wipe your ROM. If you have a (stock) TWRP backup of your /boot partition then you can try restoring that (but I'd prefer a fresh flash).

Once you have the stock (Lineage) ROM booting and working again you can re-approach Magisk.
[Magisk] ecksdeeay:
I can identify your device and OS

https://twrp.me/lenovo/lenovop2a42.html

search through this thread for lineageos

https://xdaforums.com/search/thread/3432382?query=lineageos

Or go to;

https://wiki.lineageos.org/devices/kuntao/install
[Magisk] Daksh Jain:
Hi, I have about 6-7 modules installed and none of them are working. I have tried clean installing the ROM and reinstalling magisk several times using uninstaller but it's not working. Only root access works. My device is Moto G 2015 (osprey) and custom ROM RRv7.0.2
[Magisk] Daksh Jain:
Here's the log: https://hasteb.in/isehayug.yaml

I haven't installed any custom kernel or mods.
[Magisk] Didgeridoohan:
Disable/uninstall EdXposed and see if that makes a difference.
[Magisk] Daksh Jain:
Yes, it worked. May I know why edXposed was causing problems?
[Magisk] Didgeridoohan:
From what I've seen, from multiple reports, EdXposed has a tendency to mess up Magisk's boot process. No idea why (I don't personally use it and have no interest to do so)...

Take it up with the EdXposed developer.
[Magisk] RMarques:
I don't know how to take the logs but I'd like to report that just like it was happening in 19.1, with 19.2 I just lost root.

OP5

Latest OB

Latest magisk
[Magisk] :
Nobody help so im install SuperSu and now i have root, weak forum any help from people here.
[Magisk] wodgey:
I've an app that doesn't show up in the list for "magisk hide".

What can I do?
[Magisk] samhhmobil:
JFYI,

19.2 does affect bluetooth in some way.

HTC One M7 international (M7_UL),

GPE Firmware,

LineageOS 14.1 unofficial, latest build (2019/05/11),

TWRP 3.2.1,

With Magisk 19.2 no bluetooth connections are possible, solution: downgrade to Magisk 19.1 (and it works again).

I'm sorry, no time found to create log files, and even it may(!) be, that it's not the fault of Magisk, because LineageOS on M7 has other bluetooth issues too... :(

samhhmobil
[Magisk] JudgeDread11:
I read your precious post, but didn't know an answer, like probably many others here did.

To know what is going wrong with your setup, logs are required and you didn't provide any. A Magisk log at least, but likely more. If you read through the last few pages you'll find a link to a help page which explains very clearly how to file bug reports. Follow this guide and surely somebody will try to assist you.

If you're happy with SuperSU, then the problem is solved already

A forum is as strong as it's users. I have always had excellent results finding answers and/or help on this forum, but you need to pay your part. Getting upset is not helping anybody, including yourself.
[Magisk] wilsonhlacerda:
Good luck, Junior. You'll need it.
[Magisk] EvilWormGod:
I have the same setup as you and have the same issue. Does anyone have any ideas? Or is manually applying the OTA update and then re-installing Magisk the only solution?
[Magisk] shaggyskunk:
Well - You just joined XDA one whole day ago & two posts to your name... Search will almost always provide you the answers you need & there's plenty of people here who are more than happy to help - Search & if you still can't find the answers - Ask & patiently wait for help ??

Sent from my SM-G975W ??
[Magisk] Didgeridoohan:
Has anyone tried adding the system updater service to the Hide list? I've tested tricking OOS to download the regular OTA that way (otherwise it would detect root and download the full OTA).
[Magisk] BROKEN1981:
Can't you use FlashFire?

---------- Post added at 07:47 PM ---------- Previous post was at 07:44 PM ----------

I don't have a Pixel, but can't people use FlashFire to take an OTA? I haven't used his app for about a year+ so things maybe changed.
[Magisk] jcmm11:
Flashfire hasn't been updated since Chainfire stopped working on SuperSU.

I forget version numbers but Flashfire hasn't worked with Magisk for quite a while. I think Pie is also a problem. So no, Flashfire isn't an option. You also have the time bomb issue with Flashfire, but there are ways to work around that.
[Magisk] pmj_pedro:
Sorry if this is not the correct place to post this.

But does the lattest version of Magisk works on the Samsung galaxy a40 on android 9.0 and with the cpu exynos 7885?

Thanks
[Magisk] bluenote73:
Unfortunately asderdd is MIA and has been for months (not even logged in since mid Feb), so me and [MENTION=5199968]Dodgexander[/MENTION] can only go by what's been said in the thread for it and relay our observations. I guess I will try again, putting the excerpts from asderdd's summaries and the github into the issue so it's as convenient as possible and hope for the best. Thanks for confirming that this isn't an issue of not providing logs and so on. Do you understand what asderdd meant in the explanation that I excerpted of "The solution is disabling zte's selinux policyproc feature. Lookup the commits at github for details. I don't know what had changed on magisk v17 to cause conflict with our policyproc."? Or hopefully, will topjohnwu understand what that means in a useful way?
[Magisk] wodgey:
Is there any way to add the package name to a text file somewhere, to hide root from the relevant app?

for more info, it's an app called "com.cognitoiq.ciqmobile.byod.hermes"

Do I need to provide logs or anything to aide people in providing assistance?

edit2add

I use magisk Hide for 4 other apps that all work fine (three banking apps and one app for a parcel delivery company). It is just this one new app that I have installed today that doesn;t show up in the list of apps to hide magisk from.
[Magisk] cbk49307:
Hello all,

Need help. I'm using Redmi Note 5 Pro phone, Havoc v2.5 Pie ROM. Installed Magisk 19.2 [19200]. Magisk Hide is not working for below listed applications.

1. YONO SBI: The Mobile Banking and Lifestyle App!

https://play.google.com/store/apps/details?id=com.sbi.lotusintouch&hl=en_IN

Issue facing: App quits immediately after launching it. Works fine with MIUI ROMs [Not Rooted]

2. HDFC Bank MobileBanking

https://play.google.com/store/apps/details?id=com.snapwork.hdfc&hl=en_IN

Issue facing: Throws erro: App does not support rooted phone

These apps have not worked on my phone from Oreo Resurrection Remix also Pie Resurrection Remix ROMs.

Please advise

Thank you!!
[Magisk] wodgey:
For my banking apps, I also had to use an adblock app that adds entries into the "hosts" file, so that the app cannot report back to its' control server.

I don;t know if this is helpful. FYI, my banks are part of the Santander group and I found the info on how to hide root in an xfd thread https://xdaforums.com/apps/magisk/how-to-bypass-lloyds-root-detection-t3837206/page2
[Magisk] guest4711:
Open a terminal on your phone (on some ROMs you need to enable it in developers options, or you can install an app like Terminal Emulator for Android (Access Android's built-in Linux command line shell. Unleash your inner geek!) - https://f-droid.org/app/jackpal.androidterm ) and use the commandline interface of magiskhide.

su
magiskhide --add com.cognitoiq.ciqmobile.byod.hermes

Edit: Syntax corrected (no "PGK" needed after --add

---------- Post added at 09:05 PM ---------- Previous post was at 08:57 PM ----------

Did you hide MagiskManager itself (MagiskManager -- Settings -- Hide Manager by repacking it to random name)?
[Magisk] Didgeridoohan:
I tested both those apps on my OnePlus 3T, ArrowOS (Pie) and had no issues hiding root from them.

Magisk v19.2 and the Manager hidden (repackaged).

That suggests it's not an issue with Magisk and that the apps could be detecting something in the ROM or an app you have installed.
[Magisk] EvilWormGod:
Have not tried that. Will give it a shot and report back.

Just curious then - after choosing Uninstall / Restore Images, Magisk and Magisk Manager are still running? Otherwise hiding the system updater service would have no effect, correct? Or am I missing something? Thanks!
[Magisk] Didgeridoohan:
Well, you would probably have to look for an update first... My suggestion was mainly to see if the update would show up.
[Magisk] DenyDarko:
What a surprise.

Have you considered the possibility of you being rude and offensive to people who aren't exactly your employees?

Just saying.
[Magisk] Schinkentoast:
[solved, problem was on my end]
[Magisk] kotuamoalt:
If memory serves me correctly, flashfire works up to version 18, I believe.
[Magisk] :
Im not insult anyone just say what i see, now everyone respond....
[Magisk] kotuamoalt:
Probably. There's one way you can find out...
[Magisk] :
I'm already have luck so no need your wishes,Junior... Funny.
[Magisk] jcmm11:
Now you made me go look it up ??

Last version of Magisk it worked with was 14.2 (I was pretty sure 18 was too high)
[Magisk] diehard2013:
By any chance do you work for Samsung support?

:):cyclops:

---------- Post added at 02:34 AM ---------- Previous post was at 02:26 AM ----------

Was zackptg5's 'bash for android' removed from the magisk downloads list?
[Magisk] jcmm11:
yes and no

https://xdaforums.com/android/software-hacking/mods-zackptg5-s-misc-projects-t3881164/post79544739

GNU Utils for Android
[Magisk] Woundedangel:
Note 9 exynos

can I root my Note 9 Exynos with Magisk

Model: 960F dual sim 128 GB

Android version : 9

One UI version: 1.0

Security patch: 1 March 2019

Kernal ver: 4.9.59.15135523

#Tue Feb 26 18:14:17 KST 2019
[Magisk] Artim_96:
Processor is irrelevant. You need either a way to flash/boot TWRP or a boot.img you can let the manager modify and flash it through fastboot (or in your case probably Odin). Otherwise there should hardly be any devices impossible to root yet (probably still the Pixel 3's)
[Magisk] wodgey:
Yes. I'll try the terminal route
[Magisk] icanttinkofaname:
I'm hoping someone here might be able to help. I have a HTC 10 on stock Oreo ROM, running latest magisk (19.2).

My problem is my phone keeps encrypting itself. I've done the format data option through twrp (and magisk persists when I do it) but after a little bit of time it becomes encrypted again and requires my password before booting. I want to get rid of this. My phone reboots itself from time to time due to battery issues and having to go through the decryption process every time it does so is super frustrating. Every time I go back into magisk the "preserve force encryption" option is ticked. How do I stop this from happening?!

Thanks for any suggestions.
[Magisk] :
Is this... real...?
[Magisk] avik735:
Where is the magiskhide list of apps in magisk manager 7.2.0?
[Magisk] jcmm11:
There's a table in /data/adb/magisk.db
[Magisk] Bi0haZarD:
The list is under the magisk hide tab.
[Magisk] jcmm11:
See the 2 sections on dm-verity and forced encryption

https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
[Magisk] warrencoakley:
Anyone getting this error when trying to update to the latest Magisk? I can't even unhide manager as it still states error downloading.
[Magisk] jcmm11:
No problem here - but my manager isn't hidden at the moment. Can you download (not install) the zip for the Magisk install? If so you can extract the apk from the common folder in the zip.

Worst case is uninstall the existing Manager then install a new one.

Also, you're on Canary, correct? If so this should probably have been posted there rather than here.
[Magisk] warrencoakley:
Just rebooted my phone and tried again. All good and it's hidden too.
[Magisk] heslo.rb26:
Awesome, thanks mate! I don't need to remove SU or root before I do any of that? Just a simple reflash of everything then I'm good to go?
[Magisk] goodtimes50:
I would imagine flashing the ROM will include whatever root method comes with the rom. I'm guessing you'll need to unroot again and then flash Magisk.
[Magisk] RandomPooka:
Remove root
[Magisk] Hyflex:
I've installed it all but for some reason Magisk manager is acting weird. If I use the "Toggle Root" toggle and try and turn root off it automatically turns back on...

What's going on?

I did the following:

Installed CynanogenMod 13

Installed GApps

Installed Magisk

Installed Phh Superuser

Installed Systemless Xposed

Installed Magisk Manager

I'm ready to install AutoMagisk and Magisk Viper4Android
[Magisk] Beast84:
I don't know exactly what this means? KEEPFORCEENCRYPT=false is default? Which means it won't encrypt my device if I'm currently unencrypted?

And I have no idea what KEEPVERITY does? Any help on that would be awesome
[Magisk] locolyric:
I totally understand xposed should be uninstalled.

Just wondering what steps I did wrong cause the xposed failed to hide from it
[Magisk] JuergenZ66:
You have leftovers from CM root.

from here you can do this:

1. download unSU.zip from here http://xdaforums.com/showpost.php?p=63615067

2. boot into recovery

3. uninstall root with unSU.zip

4. install magisk again

5. install phh 17 again

6. reboot system
[Magisk] Razr1804:
How to install dolby atmos systemless like viper??
[Magisk] jemyzhang:
[MENTION=4470081]topjohnwu[/MENTION] A little bug find in phh's SuperUser 17 (Magisk Version) (2016.8.20)

should be:
[Magisk] Kasimodo:
Hello,

which version of Note 4 have you? I have a N910F. Do you think it will work and which Magisk version do I use?

Regards

EDIT : Oops I found a bit of answer with your previous post

II

V

.

So I have only one question: Which Magisk's Files and xPosed files do you used?

Thank you in advance.
[Magisk] Razr1804:
I get every time I open viper can any one help
[Magisk] 99poison:
Thank you so much brother. Finally, my viper is working with magisk. I copy your audio_effects.conf to /magisk/v4a/system/vendor/etc/. Now driver is install and processing :)
[Magisk] H4X0R46:
Does magisk work the way it should when flashed to a secondary in a multirom environment? Anyone tested this yet?
[Magisk] odurecu:
Hi

I am using a Galaxy S6 with a custom ROM (rooted with SuperSU)

I restored the stock bootloader to unroot.

Then flashed Magisk, phh and systemless xposed

I can't get Android Pay working: even if I turn off the root toggle, SafetyNet helper reports a failure (payload validation failed)

Has someone any clue on what's wrong?

Thks guys for your support
[Magisk] androidmonsta:
Seems like something changed in a Safetynet. It's able to detect xposed now. Uninstalled xposed completely and Magisk works as normal. Installed xposed and Safetynet fails.
[Magisk] ataraxist:
after unSU, you should test it with safetynet app... I think all custom rom will not work with safetynet even full unroot.
[Magisk] JudgeDread11:
Send more and more questions about Android pay, Pokemon, Xposed and v4a popping up here again. Please use the correct threads. [MENTION=4470081]topjohnwu[/MENTION] would it be possible to add these links to the OP somewher?
[Magisk] RandomPooka:
Restoring stock bootloader does NOT equal unrooting. Bootloader itself has nothing to do with root, other than allowing you to boot a custom boot or recovery image. Boot.img is what you need to be restoring. But, restoring the stock boot.img won't unroot you either. It only gives you an untouched selinux policy and stock kernel (or at least the kernel that ships with your custom ROM)

You need to remove all traces of root from the device. The simple way is to do it from within the SuperSU app using the full unroot option, or with the UnSU.zip in recovery.
[Magisk] JudgeDread11:
How to install magisk:

Magisk requires an unlocked boot loader.

If you are on a custom ROM with root baked in you will need to uninstall root first.

To do this several tools come in handy:

Root validator (get it on Google play store) and the unSU script (get it from osm0sis' bits and ends thread: http://xdaforums.com/showthread.php?t=2239421&page=86)

Before you do anything run right validator and write down the locations root and BusyBox are installed in.

If your ROM includes SuperSU use the SuperSU app to fully unroot. You can find this option in the app's settings.

Boot into TWRP

And flash the unSU script

Then in TWRP use the file manager and check the locations you have written down before for left over traces of root. If any, remove them manually. (Some people reported the magisk manager root toddler only worked after BusyBox was removed too)

If you're not on a prerooted ROM you can skip the above steps.

Now you can flash in this order:

Magisk v6

Phh's superuser 17 for magisk (download from the OP)

Xposed 86.5 for magisk (download from the systemless xposed thread: http://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268/page202 )

Restart your device

Install:

Magisk manager (download from the OP)

Phh's superuser app (get from the Google play store)

Material design Xposed installer by DVDAndroid (get from its own thread: http://xdaforums.com/xposed/material-design-xposed-installer-t3137758/page152 )

When you use the root toggle in the magisk manager for the first time it will ask for root permission and switch back. After you have given the permission it will unmount root. (To pass safety net you'll need to disable xposed in the xposed installer app and reboot your device. Then unmount root)

Most problems with magisk that people post on this thread are caused by failing to follow part of these steps.

Then there are some incompatible devices. (See the OP)
[Magisk] grep_i:
Are you sure you mean you restored stock bootloader, because that would mean you have locked your bootloader again.

Probably you mean you restored stock boot.img that way you do disable root but there is a probability that there are remnants of root binaries left on your device.

Search for them and remove them

Hint:

/Su/(x)bin

/System/(x)bin
[Magisk] Witsche:
Hi everyone,

I installed Magisk 19.1 with a temporary TWRP (so on my phone I have the stock recovery), to upgrade to 19.2 I can use Magisk manager or do I have to download the zip, boot with the temporary twrp and flash the zip?

Thanks
[Magisk] EvilWormGod:
Before hiding anything, I always get the System is up to date message when checking for an OTA update.

Not sure which process I should try to hide. On the Magisk Hide screen (showing system apps), the only two items with "update" in their name are "ConfigUpdater" and "Time Zone Updater". Do you think ConfigUpdater the one I should try hiding, or is there another one that I should look for? Thanks!
[Magisk] Didgeridoohan:
I've seen the same thing, but we can't currently figure out what's causing it. Could be an issue with GitHub servers, or something else...

I have honestly no idea what process it could be (doesn't sound like either of those though)... I was just going on a hunch that doing this could solve the whole "System is to to date" even though it isn't.
[Magisk] warrencoakley:
I just rebooted my phone and tried again and it worked.
[Magisk] Pkt_Lnt:
It might be the fact that "codeload.github.com" and "maurerr.github.io" are getting blocked by some blocking list. Phones, routers that use a block list are having this issue with the URL. I've seen this on two other sites I frequent in the last couple weeks. Whitelist "codeload.github.com" and "maurerr.github.io" in whatever blocking app you use fixes it.
[Magisk] Didgeridoohan:
I'm currently not using any blocking apps, so that's likely not it...
[Magisk] jcmm11:
You can use Magisk Manager.
[Magisk] lolpepa:
1) Magisk-v18.1 and less = no problems.

2) Magisk-v19.1 and Magisk-v19.2= problems. accidentally crash, sometimes the phone stays in the black screen and can't wake up. Whether I use a new or old ROM, the new magisk completely destroys a stable phone.

Very much please fix it, I'm absolutely sure there is a bugs in Magisk version 19.1 and 19.2 ...Custom ROM Android Pie (Lineage, AEX), ARM64... :(
[Magisk] Didgeridoohan:
Very much please provide a proper bug report.

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] guest4711:
Did you grant storage permission to Manager?
[Magisk] coolbeans2016:
For quite most of 2019 Google Pay was not working with Magisk.... root was detected.

Latest updates.... 19.2 & MM 7.2 has cleared this on my device:

LG Stylo 3 Plus with Metro PCS (T-Mobile)

Still on Nougat 7.0... where it will stay if a daily driver ROM is never developed.

Thanks so much to the developer John Wu!!!!

Been a couple months behind with monthly donation, getting that caught up

RIGHT NOW... w/Google Pay!!!!

---------- Post added at 03:14 PM ---------- Previous post was at 03:13 PM ----------

For quite most of 2019 Google Pay was not working with Magisk.... root was detected.

Latest updates.... 19.2 & MM 7.2 has cleared this on my device:

LG Stylo 3 Plus with Metro PCS (T-Mobile)

Still on Nougat 7.0... where it will stay if a daily driver ROM is never developed.

Thanks so much to the developer John Wu!!!!

Been a couple months behind with monthly donation, getting that caught up

RIGHT NOW... w/Google Pay!!!!

---------- Post added at 03:14 PM ---------- Previous post was at 03:14 PM ----------

For quite most of 2019 Google Pay was not working with Magisk.... root was detected.

Latest updates.... 19.2 & MM 7.2 has cleared this on my device:

LG Stylo 3 Plus with Metro PCS (T-Mobile)

Still on Nougat 7.0... where it will stay if a daily driver ROM is never developed.

Thanks so much to the developer John Wu!!!!

Been a couple months behind with monthly donation, getting that caught up

RIGHT NOW... w/Google Pay!!!!

:cool:
[Magisk] Baldesarra:
So when I want to hide Magsik. Should there be a "tick" or not? Not sure if this tick means it's hidden or it's un-hidden.
[Magisk] jcmm11:
When hiding apps within Magisk the tick means it's hidden. A horizontal line means some of the services associated with that app are hidden, some aren't. Click the small down Chevron to the left of the line to expand the listing.
[Magisk] kotuamoalt:
I am absolutely positive it worked past version 14.2. I don't think I even had magic installed until version 15 or 16. In fact, I posted inquiring about the fact that it stopped working only a couple of months ago. I'm just too lazy to look it up. ?

---------- Post added at 09:56 PM ---------- Previous post was at 09:52 PM ----------

Wow, it is very rarely that you hear the word 'Chevron' used in that context. ?
[Magisk] strikerz911:
I was just going to report this... Oneplus 5T on stock rom with magisk. Updated to 19.2 today and now my phone gets stuck on black screen with blue notification light after oneplus boot up logo. Not even sure how to proceed.

EDIT: So I flashed the uninstaller through TWRP then installed 19.0 and now all is well. I am able to get back into my phone.
[Magisk] AndrzejDwo:
[MENTION=1870394]strikerz911[/MENTION] didn't you see [MENTION=4667597]Didgeridoohan[/MENTION]'s post right under the one you quoted?
[Magisk] Ps24u:
19.2 on my phone crashes once in a while (as seen in Magisk log), and apps sometimes will just fail to launch, or launch very slowly. This is random.

For that reason I prefer 18.1 which is perfectly stable and working as intended on this phone (xperia with nougat).

My question is, do I need to keep using the Manager bundled with 18.1 (v7.0), or can I actually update and use Manager 7.2 with 18.1?

I'm insure if there are any dependencies..
[Magisk] kotuamoalt:
You can safely update to the new manager.