yashsingh1/xdaforums huggingface dataset:
[Magisk] tufyuma:
Figured out my problem....sort of...fixed it anyway

So I DON'T think it was a Magisk problem, at all.

I tried to reinstall (dirty flash) Q 2, and It got worse, here is my quote from a different thread:

I screwed up and tried to install the last P build after getting the ota beta Q update….i had issues (possibly of my own making).

Realized that trying to go back wasn’t going to work so I thought I would just reinstall the Q beta version 2, I downloaded it…all seemed well until I wanted to get to “settings”

I can pull the “curtain’ down and see a few quick access icons (wifi, Bluetooth, airplane mode…) but it won’t pull farther down (second swipe) to see other options and the “settings” gear at the top. I also don’t seem to be getting notifications, I hear them but don’t see an icon.

I also can’t get to the setting that allow me to transfer files.

Any ideas?

Edit: also can't get to my app drawer...

Edit 2: home button doesn't work either...

So here is what I did, opted out of the beta program...let it reset and wipe everything...opt back in, while it was resetting...by the time it was done I was able to download and update to Q 2 again.

after it installed I booted to TWRP (new version is out 3.3.0-0) and installed Canary, still gave me the error at the end, but when I rebooted and checked with RootChecker it said rooted and I got prompts to allow Root Access.

I WAS able to install Canary Magisk Manager apk without any issues.

I still have to try to change my build.prop , hopefully that will go smoothly.

Thanks for the suggestions, hope my issue helps someone from having to go through it!

Jim
[Magisk] Tombab:
Seems that installing manager apk manually was needed and it wasn't installed with main ZIP file. But now I have another issue (yes I tried to search). After flashing Magisk new "feature" appeared in both LOS 14.1 and 15.1 that makes screen to suddenly go blank at random times, usually when I'm typing something. After that I press the power button and hear locking sound, with second press screen wakes up to lock-screen normally. In other ppl's messages I found blank screen problems came right after flashing Magisk and during booting Android but my Android boots and works normally otherwise. Phone is Samsung Galaxy S4 GT-I9505 if it matters. No modules installed and I only changed manager packet name and used "hide" for banking app to make it think phone still has stock Android. Does magisk somehow interfere with LOS kernel or why does it make screen to go blank during normal use?
[Magisk] martyfender:
That may be a rom or kernel related issue.

I occasionally have the system ui quit, the screen goes blank until the ui reloads, but not ery frequently. Have you tried the latest beta or Canary build?
[Magisk] martyfender:
Try here:

https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
[Magisk] nicorg3221:
I get this too. Any idea?
[Magisk] hfam:
Wondering if this is related to Magisk:

Google Play Store>Settings>Play Protect Certified>Device is not certified

I never noticed this before. I have a Google Pixel 2 I purchased directly from Google, run stock Google OS, update on time, and of course I'm rooted with Magisk, v18.1.

I don't seem to have any issues from this, but wondering if this is a result of rooting with Magisk or something related, unlocking the bootloader, etc.....maybe a problem in the making?

Is it anything I should be concerned with or try to repair? When I search on this I see people getting notices locking them out of all Google apps, etc. I'm not having that issue but I'd hate to have it start.

Any advice or enlightenment would be greatly appreciated, I can't find anything that seems to point to this specifically, but aside from Magisk, it's all Google hardware and OS.

Thanks all
[Magisk] dandemonic:
Might not be a magisk issue, more likely an issue with playstore data.

You could try wipe data for play store in settings/apps/playstore , force stop playstore, then open playstore again, wait a little bit to give it time to sync and check if certified.

Had the same problem when I first got my oneplus 5t, used the above method to fix it, so am hopeful it may work for you also.
[Magisk] hfam:
1000 thumbs up to you, sir, that worked like a charm!! Thank you so much!!

Best. Forum. Ever. Man I love you folks!

Mods: If my post was too far afield (I thought it was likely Magisk related), my sincere apologies, please go ahead and remove it if you see fit as it indeed was not a Magisk issue.
[Magisk] hshah:
I think the posts are quite helpful for others, and technically it is partially related to Magisk / being rooted etc.

When I'm tinkering with ROMs and Magisk buiids, if Hide is not enabled when I boot up and start the Play Store, it claims the device is uncertified. Even if I turn on Hide, I have to clear Play Store data before it goes back to showing as certified.

Used to get it a lot last year when we had that ongoing issue with the hide function and randomly losing root... all good now though :svetius:
[Magisk] Didgeridoohan:
[MENTION=2843606]hfam[/MENTION] [MENTION=4980778]dandemonic[/MENTION] [MENTION=271749]hshah[/MENTION]

Play Store device certification is based on the same check as the CTS profile of SafetyNet. If CTS fails on your device the Play store will eventually report uncertified (it seems to do checks intermittingly). Solution (as has already been given) is to make sure you pass CTS and then clear Play store data.
[Magisk] DinIslamJoy:
I got a problem about rooting my device,

In aosp ex and pixel experience rom, whenever

I flash magisk my wifi mac address goes unavailable and wifi doesn't work.

I have tried many versions of magisk but the problem remains:(

I also tried two different versions of pixel experience rom but i can't fix the problem.

I tried to restore modem firmware it restored sucessfully but still not working.
[Magisk] hfam:
[MENTION=4667597]Didgeridoohan[/MENTION], thanks for the clarity. That makes perfect sense, and I'd bet it went wonky for me around the 18.0 stable. I seem to remember safety net issues on that release (maybe 17.x even?), probably failed and PS marked it as invalid them and it's been like that since. So as [MENTION=271749]hshah[/MENTION] said, I guess it is indeed a Magisk related issue in that way.

I learn a LOT from you all, know that I appreciate every bit, absorb it like a sponge. As always, thanks for the selfless help, all!! Have a great weekend!
[Magisk] timg11:
Titanium Backup cannot acquire root right, after Magisk grants it?

I've tried the process of uninstalling TiBk, removing the data folders, rebooting, and re-installing several times.

The first time I run TiBk, I get the Magisk prompt to grant superuser. The notification that TiBk was granted superuser permissions appears at the bottom. TiBk then asks for the Android app permissions. Then it restarts and immediately displays the "unable to acquire root" error.

Typically, TiBk tries for quite a while before giving up - maybe a minute. The error now occurs immediately when opening TiBk.

Subsequent runs of TiBk immediately display the "unable to acquire root" error, but the Magisk notification "granted superuser rights" is not displayed again. TiBk is shown in the list of SU rights. Other apps are able to gain SU normally.

TiBk was working a few days ago - I haven't done anything but uninstall and reinstall the app from the store. (V8.3.3)

Edit - I think I found a solution.

Instead of deleting the data folders with Solid Explorer, I used adb shell:

>adb shell
blueline:/ $ su
blueline:/ # rm -rf /data/data/com.keramidas.TitaniumBackup
blueline:/ # rm -rf /data/user/0/com.keramidas.TitaniumBackup
blueline:/ # exit
blueline:/ $
>

So the process:

Uninstall TiBk Pro and the Pro Key apps

adb shell as above to clear

Reboot phone

re-install TiBk Pro Key, and TiBk Pro app

Run TiBk. See normal delay while TiBk displays line about checking su and busybox. Grant permission when requested.
[Magisk] dex2grigg:
Starling banking app detecting root, any ideas? :(
[Magisk] Wolfcity:
The obvious? Hide the banking app and hide magisk manager.

Maybe some additional information could be helpful like

- magisk version

- device

- OS

and always seen with pleasure: Logs.
[Magisk] martyfender:
Also, clear the banking apps data.
[Magisk] hshah:
Depending on your app settings, there may be similar Titanium folders under the following, so if you are clearing it out then make sure you include them:

/sdcard/Android/data

/sdcard/data

I've generally not had issues with Titanium, and my "pro key" is actually a text file on the SD card (from back in the day before it was sold on the Play Store, lol) but I've just started copying the APK to /system/priv-app as that tends to result in less issues for me.
[Magisk] Ph0z3:
Thought I'd give this a go on my Pixel 2 XL...

Set everything up, updated, deleted the remnants & blocked PoGo.

It got about 5 minutes of game play before it locked up. :(

Bummer. Looked & searched every thread I could for a working solution, found nothing.

O well... Guess I'll stay stock?
[Magisk] Strephon Alkhalikoi:
If you want to play Pokémon Go, yes. Though I'm sure someone will chime in saying they got it to work.
[Magisk] Ph0z3:
I figured as much. O well .. sucks to suck I guess?

I've been stock since they first banned root when I had my Nexus 6... Thought maybe I'd give it another shot with my "new to me" phone & honestly, with what little I do on my phone, I'm not losing much being stock.
[Magisk] RandomPooka:
Chiming in here. 19.0 Magisk beta, not canary build.

PoGo working fine.

Have you gone into the Magisk manager app settings and repackaged the manager up under a random name? That, in addition to hiding the PoGo app, worked for me.
[Magisk] Ph0z3:
I don't know how to repackage the name.
[Magisk] martyfender:
Open Magisk Manager and go to settings. Choose: Hide Magisk Manager. Confirm that it was successful. It's that simple, unless for some reason, it fails to hide. Since the app detected root, you may have to also delete the apps data, also. Finally, there is a dedicated thread to Pokemon Go, somewhere here on xda. I don't play the game, myself.
[Magisk] Ph0z3:
Did... Tried everything... Nothing works :eek:

O well. Yeah, controlling a few CPU modules would be cool, but I'm fine being stock for real.

UPDATE: Tried the beta channel... Borked my boot block, tried to restore a backup... It broke that too. Tried to flash a fresh image... Didn't work.

Had to "flash-all" & fresh install.

LOST EVERYTHING. :crying:

Just spent the last 90+ minutes setting up my "new device"
[Magisk] Xilous:
S5 G900W8 Magisk Manager Error

Here's what I've done so far:

I've rooted my Samsung S5 G900W8 using something called CFAutoRoot through a software called Odin on my PC.

I then installed the latest TWRP, made sure it was the correct image/tar for my model.

I then tried installing Magisk, through TWRP recovery, by flashing? It returned an error saying "system patched by unsupported programs, please boot stock image"

I carefully grabbed the correct stock image for my phone, country and provider. (I didn't backup anything before starting)

I flashed the boot image through the TWRP recovery, and then flashed the latest Magisk which is v18.1 straight from the github source. This time it worked meaning the boot image fix worked.

I then grabbed the Magisk Manager apk straight from the github as well and installed it.

This is where I currently am stuck at. After opening the Magisk Manager app, initially it says Magisk isn't installed

pic:

But if I swipe up to refresh the page, it'll say that latest Magisk is installed. However, a popup will appear right after, saying "additional setup required".

pic:

If I click on yes, after a couple seconds it'll say "setup failed" and then just leave me from there. It says Latest Magisk is "installed" yes I dont have any option to do anything. No option to install Modules, or Hide Magisk.

pics showing no options:

I do the safetynet check however and it apparently says I pass

pic:

However, I downloaded a root checker app. When I didnt have Magisk installed, I passed the safetynet test. After I installed Magisk, even though the Magisk Manager app says I pass, this root checker app disagrees

pic:

I've tried installing 1 previous version behind the latest stable Magisk and same for Magisk Manager apk, all from the source github. Same results. I've come through a lot of obstacles to get to this point, but I'm at a complete dead end. Any help is heavily appreciated at this point. Please save me, I've spent hours upon hours to get this far!

Other info:

Model Number: SM-G900W8

ANDROID VERSION: 6.0.1

ANDROID SECURITY PATCH LEVEL: FEB 1 2017

BASEBAND VERSION: G900W8VLU1DQB2

KERNEL VERSION: 3.4.0-10710752 DPI@SWDD5514 # 1

BUILD NUMBER: MMB29M.G900W8VLU1DQB2
[Magisk] martyfender:
I believe cf auto root is essentially SuperSu, so flashing UnSu.zip would remove it before flashing Magisk?

I believe cf essentially flashed SuperSu to supported devices.

https://www.didgeridoohan.com/magisk/HomePage

You might want to start with a factory fresh flash of your rom and try again. I would suggest trying either the v19 beta, or the latest Canary build, as many fixes have been made in them since v18.1 was released.

I you don't want to try these then flash the latest Magisk uninstaller in TWRP, confirming that it restored the stock boot.img, followed by flashing the Magisk v18.1..zip, before rebooting to Android.
[Magisk] Strephon Alkhalikoi:
Galaxy S4 owner here. As others have noted, start fresh and install a stock ROM via Odin. Then...

Flash TWRP using Odin.

Reboot into recovery using the Samsung 3-button salute (Volume +, Home, Power).

Flash Magisk in TWRP.

Boot into Android.

CFAutoroot temporarily installs a recovery and flashes SuperSU. The presence of SuperSU is why Magisk fails.
[Magisk] Tombab:
I have installed only the latest stable 18.1. I guess I'll wait for next stable version as this screen blanking issue doesn't seem to be that frequent for me either (maybe once a day).
[Magisk] brown1178:
Hello, I just updated my Oneplus6 to OOS 9.0.5 with all substratum themes deaktivated. With installed Magisk to other slot, the phone boots, but on the loginscreen it imedetly shuts down. At this point the OTA was still present in folder .OTA so I booted to twrp, flashed 9.0.5 again and was able to boot like expected - without root. Flashing Magisk 18.1 and again the device shuts down. Trying to flash the previous OS 9.0.4 now just brings me back to recovery. I used msm download tool to go back to 9.0.4 for now, but I would like to know if the reboot issue with 9.0.5 and Magisk 18.1 is already known or if I did something wrong. Thanks guys and happy easter
[Magisk] thirtythr33:
I have a op6T, and running stock oxygenos (9.0.13), and after updating a few hours ago from .12, I no longer can authenticate via fingerprint for root requests. additionally, my security setting is only reflecting pattern, not pattern + fingerprint, although my fingerprint is working fine for the device/apps

I have searched through the wiki, along with this thread and another one, but have not found an answer

any suggestions are appreciated!

EDIT: I recently suffered a fatal 1D10T error which blue screened by brain housing group, and realized I needed to go to fingerprint settting first (not pattern/swipe/pin) and all is good now. I HAVE ROBOT LEGS!
[Magisk] Manuela.k:
Hello, Does Magisk already support Emui 9.1? I would like to root my P30 Pro.

Thank you, Georg
[Magisk] bohemist:
Latest beta Magisk 19 works with OP6 9.0.5 update.

Initially, I had issues with SafetyNet not passing but a quick Disable/Enable of Magisk Hide solved it.

I simply follow the instructions provided at OP, except that I flashed Beta instead of Stable. Why? The stable version did not work but beta version 19 works.

In the past, I used to used VPN and install OTA's via System but I find it more convenient downloading the full rom and flash it via TWRP. I am using blu_spark TWRP always.
[Magisk] brown1178:
Tried again with beta 19.0 and the recomended instructions. I never restored the image in Magisk before updating. Only had issues with substratum overlays activated. But to play safe, from now I will add restoring the image to my steps.
[Magisk] Wolfie0827:
Magisk Manager error app has stopped.

Phone: ZTE Zmax Pro (Z981)

Android: 6.1

Magisk: 16

Magisk Manager: 5.8.2

Magisk manager stops working during start screen. I have cleaned cache, Storage, tried uninstalling magisk and re-installing magisk (When I do this I can not boot into anything but TWRP, no system), Updating Magisk to 17 -18 (Again won't boot into anything but TWRP when I try that). Some times root seems to work for apps, other times any app attempting root access will get the "Magisk Manager has stopped working" message and then close.

Not sure what else to try any help would be greatly appreciated.
[Magisk] Debizzle:
So is there a fix for magisk hide for certain apps yet? Specifically Directv Now app and most banking apps. All these apps were working fine i think back with version 17.5 I believe.

Currently:

Magisk 18.1

Manager: 7.1.1

Device :

Pixel 3
[Magisk] fightinfilipino:
try switching to Magisk Canary
[Magisk] Debizzle:
THanks for responding, I have tried the canary and its closing the apps as soon as they open. Any other ideas?
[Magisk] lazye53:
I have a strange problem. If I root my device, I connect to the wifi network at my university, but my speed is very low.

If I remove root from my device, the speed in the wifi network is quite normal.

How can I overcome this?

The wifi network system at my university is eduroam.

Information about eduroam; https://en.wikipedia.org/wiki/Eduroam

---------- Post added at 10:29 AM ---------- Previous post was at 10:29 AM ----------

I have a strange problem. If I root my device, I connect to the wifi network at my university, but my speed is very low.

If I remove root from my device, the speed in the wifi network is quite normal.

How can I overcome this?

The wifi network system at my university is eduroam.

Information about eduroam; https://en.wikipedia.org/wiki/Eduroam
[Magisk] mrjoy:
I'm on galaxy s8+ pie & otg is not working for me. Please help me is this root issue?
[Magisk] fndpena:
Hey guys, I just can't get latest beta (19) installed on my marlin running Android Q.

I boot into twrp (tested on both latest and previous release), I install the zip and it goes just fine, no errors. But when I boot back to the system and check Magisk Manager, it tells me magisk is not installed. I've done this so many times before on previous android/magisk versions. I don't know why it's not working this time.
[Magisk] martyfender:
I think you need the latest Canary build for Q.
[Magisk] TacoLoco:
Hi there,

just flashed magisk and my WIFI also stopped working (cannot even turn it on)..

A few infos:

Leagoo M9 Pro with Android 8.1 (Stock)

- boot.img patched with Magisk Manager 7.1.1

- flashed boot.img with newest SP Flash Tool

- did factory reset but problem persists

Bluetooth seems also affected..

Please help, this is my second try, already bricked an identical device while reflashing original firmware.. :rolleyes:

Update:

Nevermind, I flashed Stock ROM again (without preloader, cause I think this way I bricked previous device) -> WiFi and BT working -> Flash patched boot.img again -> WiFi and BT still working.. If someone can unbrick my second Leagoo M9 Pro (I think preloader is f***** up), write me a pm..
[Magisk] fndpena:
I didn't know there was canary builds, thanks for the heads up!

EDIT: Nevermind, latest canary worked like a champ.
[Magisk] M1chiel:
I'm sorry, but I never noticed this on Eduroam. Maybe you have to hide your byod client?
[Magisk] TemperateRoot:
Hi.

I have a OnePlus6 and I just flashed the new update ZIP. Logically I lost root after the update, so I booted into blu_spark recovery, installed the recovery onto the ramdisk, then flashed the Magisk beta zip. This caused me to immediately be kicked back to the recovery once I booted into system. It'll shut down at the PIN input screen and then boot into recovery.

If I flash the latest stable Magisk, it'll just say I'm not rooted and doesn't detect Magisk.

I just want to get my root back so I can run AdAway, Substratum, etc. What can I do to fix this?
[Magisk] paulo boë:
My uncle told me that Google is tired of people rooting there device. And that they are going to edit almost every apk to not work on rooted devices. And Pokemon Go was the first app to do so. And because Android is Google's property they can do whatever they want.

I'm sorry if somethings are wrong. He didn't told me where he got it from so I don't know for sure. If you want to see for yourself, just search Google (lol) for it.
[Magisk] ilfat12:
FlashFire and DriveDroid does not work with Magisk :(

I have to use SuperSU-2.78-SR1 with Xposed-86.2-topjohnwu.
[Magisk] Pival81:
That's entirely not true, if PokemonGo doesn't work with root, it is because Niantic Labs doesn't want it to, Google is not involved. And yes, Google develops Android, but it doesn't mean that it can control it. Being an opensource project, Android is not the property of anyone.

Also Snapchat is the first i remember not working with root, but I may be wrong on this.

And of course not even Google can edit every apk, either because it is physically impossible and it would also be illegal (think for example of Google editing the bank app).

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Magisk] paulo boë:
Okay than I was wrong. I already thought that when he said it it sounded wired. Thank you for your explanation. :good::good:

(Snapchat works fine with my rooted Galaxy J5 though.)
[Magisk] thag1979:
Installing Magisk on Resurrection Remix ROM breaks network service

Has anyone have the same problem???

I have network service and wifi before installing Magisk, afterwards i see "no service" message and can't enable my wifi.

How can I fix this?

Update: I've tried Dirty Unicorns ROM, same problem, then I tried Nameless ROM, then it worked !!!! wohooo... there's seems to be a problem with these ROMS.
[Magisk] JudgeDread11:
If Google would want to battle root they would do it on a system level not an apk level. They have developed safety net so that app producers can opt in on extra security, without having to lock down the whole system. This shows they actually support root. And why wouldn't they. Being an open source project with many development options has great benefits for Google. Many of the Android improvements over the years has started as community driven mods.
[Magisk] Krunk_Kracker:
I have a Nexus 6p, running Pure Nexus rom. I was originally system rooted and xposed.

I ran both the xposed uninstaller, and the unsu.zip. I then flashed phh's supersu zip, installed the apk, I also installed Magisk V6, and the magisk manager as well.

IT appears to be intalled correctly, but the toggles will not toggle. When I switch one, it changed for about a second, and then goes back.
[Magisk] joeyddr:
android pay just updated for me to 1.6.133355066, all i have is magisk and no exposed, I am passing safety net and was able to add a card after disabling root. I have not tried in store yet.
[Magisk] got2best:
Haven't received this update yet. Still on the August release 1.5.130002920.. curious on any changes? Anyone able to test yet?
[Magisk] joeyddr:
Just says you can change default card. And bug fixes
[Magisk] got2best:
You can now pay with card other then default? Mine shows the same thing in "what's changed" but last updated is aug 10 .. what is the update date if you don't mind me asking?
[Magisk] joeyddr:
Sept 20