yashsingh1/xdaforums huggingface dataset:
[Magisk] jcmm11:
Just tried and it worked for me. 2 possible points of difference

1 - I'm running the latest Canary

2 - in a boot script I'm executing the following command

chmod 440 /proc/net/unix &>/dev/null

This defeats the uds hack method of checking for root.

As far as location goes they claim that Android requires location to use Bluetooth. (See their response to the "most helpful" one star review on the Play Store)
[Magisk] tuvok1981de:
i have open a new Thread with the Information about my Device ..

https://xdaforums.com/galaxy-s4/general/lineageos-magisk-safetynet-t3943750

thanks for help
[Magisk] Hemuli:
Bluetooth... Toothbrush... It all starts making sense. Maybe they are trying to solve some Viking mystery?
[Magisk] martyfender:
I don't see an Oral-B app listed in the Playstore here in the US. However, I do see many toothbrush apps listed. Can someone provide a link?
[Magisk] xunholyx:
I see it in the Play Store in Canada. It should show in the US as well.

https://play.google.com/store/apps/details?id=com.pg.oralb.oralbapp

EDIT: If you still can't get it let me know. I'll upload the apk for you to look at. Not that it matters to me. I already know how to brush my teeth.
[Magisk] martyfender:
Yes, I can open your link in Chrome, which opens in the playstore, but can't download it since it is not compatible with my Nextbook Ares 8A, x86, Android 6.0.1 tablet. My guess would be that the developers never built it for x86, since x86 is now a minority arch.

Why would a toothbrush app need to detect root? This is one of the craziest things I have seen here!
[Magisk] m0han:
maybe to decide which tooth to mark for 'root canal' treatment. :D
[Magisk] martyfender:
Yes, apparently they did not want a 'Magisk' treatment for 'root canals'. since they cost an exorbitant amount and endodontists would loose so much income!

Seriously, we'd better get back on topic before the xda police arrest us!

So back on topic, it will be.
[Magisk] andriy_:
I've tried the same (beta == canary, boot script (via init.d emulation)) but the same ****... Some time ago it worked fine with the hide (until the latest app's update).

p.s. this app allows to change the settings of the toothbrush (like brush color or timeouts notofications) and get stats from the brush. The app uses some sort of vthe augmented reality (vuforia lib) to analyse what part of the mouth you are cleaning + entertains during the cleaning. Absolutely useless, but nice try. Actually, these electronic brushes are pretty effective and nice :)
[Magisk] :
Hello i m shivaji ,i installed magisk 2 months back used it after sometime i got rid of it as i got system update .But again i tried installing magisk and after installing all the modules which i used before got restored without installing.And i tried installing xposed for my android pie but ended up in some bootloop issue so after working alot i got my stock system back.Now i want to install magisk but its causing bootloop as the xposed module getting restored without installing.

I just want a clean install of magisk help me
[Magisk] JudgeDread11:
Use the uninstaller, i believe it will remove everything.

If not then you can delete everything in /data/adb/ (on my device at least everything in the is Magisk related) for version 19+

Or you need to delete the Magisk.IMG file (can't remember the exact location, but Google can help you out) for older versions.
[Magisk] :
Where can i find that folder data /adb ?
[Magisk] zgfg:
TWRP: Advanced / File Manager, since you can't boot to the System
[Magisk] :
But i m on stock no twrp and no root right now.Just tell me how can i get clean install of magisk i mean without getting back those modules which i used before
[Magisk] zgfg:
How you install Magisk on your device (just by flashing patched Boot/Ramdisk from Fastboot) - can you install TWRP before Magisk

Otherwise, Factory reset should clean Data
[Magisk] :
Yeah firstly i need to install twrp before installing magisk becoz thats the only way to root nokia8

---------- Post added at 08:12 AM ---------- Previous post was at 08:09 AM ----------

If i select those all folders can i del them there itself in twrp
[Magisk] JudgeDread11:
In that case just do a factory reset.

I have told you how to get rid of the leftovers from Magisk. How to use twrp or otherwise modify your data partition is not Magisk related.

There are many good tutorials on how to do this.

Some advice for you and any other beginner, before you start flashing she you know how to undo what you are doing.

Much worse things can happen then having Magisk leftovers on your device, I learned the hard way.
[Magisk] jcmm11:
Beta does not (usually) equal Canary. Current Canary is 19.4-ddbe55ac (19303)

Why are you even bothering with init.d? Just use /data/adb/post-fs-data.d/ (in this case. Usually you're better off using /data/adb/service.d for a number of reasons. post-fs-data.d executes earlier in the boot process, executes it's scripts synchronously, and will time out after 10 seconds since otherwise you can prevent boot from completing. service.d runs asynchronously and boot continues while those scripts are running)

My entire process

Installed Oral-B.

Tried to run, got error about root.

Turned on hide.

Went to Oral-B app info in settings. Force stopped. Deleted data and cache.

Rebooted.

Tried Oral-B again. This time no error, app started.

Note: I do have Manager hidden.

---------- Post added at 09:05 AM ---------- Previous post was at 08:59 AM ----------

You can just boot TWRP without installing. (You have to do this anyway if you want to install it)

Don't delete adb. You should, however, be able to delete everything in adb.
[Magisk] :
U mean all the files and folders in adb but not adb folder

---------- Post added at 09:12 AM ---------- Previous post was at 09:11 AM ----------
[Magisk] zgfg:
Use the bottom-right button to get Delete option for the whole /data/adb folder

See attach
[Magisk] :
Can i delete adb full folder itself but one told me not to delete adb folder
[Magisk] Didgeridoohan:
If you want to keep Magisk after you get the device booting again, the best approach is to just delete the offending module directory under /data/adb/modules.
[Magisk] :
I want magisk but i dnt want all previous modules to be restored i just want it fresh so i can install required modules
[Magisk] Didgeridoohan:
Then just delete the modules directory.
[Magisk] Avalun:
Hi I am using magisk on lineage with android 9 and having the issue that the manager stops finding magisk after about a day. Apps which are already are having root still are working but none can request root anymore until reboot. The device is a one plus 2. How can I dig further to that?

I am not using extra modules, bust basic magisk. I once used the hide option but this one seems not having this anymore.
[Magisk] bigknowz:
Thank you

You just saved me from going completely crazy, found an old version 2.17.0.1169 i had in TiBu and reinstalled, turned off auto update from the play store! [MENTION=4470081]topjohnwu[/MENTION] anything we can provide from BlackBerry Work to help you figure out what they changed in newest version 2.18?
[Magisk] rvenkat:
Bootloops for Pixel 3 / Android 9.0

Hello -- after staring at bootloops all morning and exhausting my google-fu, I hope someone here has some advice for me.

I accepted an OTA for Android 9 (Blueline 190505.002). After that installed, I lost root.

Oh well, gotta re-flash Magisk...

Tried to flash 19.3 via TWRP 3.3.0.0, all seems to have proceeded correctly, but reboots to a loop. every. single. time.

I can reflash the original OTA boot.img to stop the looping, but no root there, obvs. I've also tried the patch-flash-reboot with the same results.

Help!!
[Magisk] duh1:
I posted earlier on how with the June update to Google play services, recent Pixel devices, and others as well, are no longer hiding being bootloader unlocked. I can now confirm that this was the case.

With a bootloader locked device all the banking and payment apps work fine, and all apps appear in the Play Store. Once the device was unlocked, some banking and payment apps no longer worked, and the Play Store showed Netflix, as well as other apps as not compatible with these devices.

Rooting using Magisk, and MagiskHide, no longer did anything to change the situation, as apparently Google play services is still reporting these devices as being unlocked...
[Magisk] Didgeridoohan:
I only really looked at your Magisk logs, and they're interesting because MagiskHide isn't triggering at all. It doesn't react to the apps on your Hide list. What was your device details again?

It's perfectly possible that one of your Magisk modules doesn't work with the updated system. Edge Sense is one known module that causes issues like that.

Here are some tips on how to get out of that kind of predicament:

https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc

Did you still have Magisk installed when you locked the bootloader, or had you gone back to a stock setup?
[Magisk] rvenkat:
Wish that was the issue -- I don't have any modules loaded at all.
[Magisk] duh1:
Stock setup, starting from scratch. Had this confirmed by others as well.

Always knew it was a possibility that one day Google could fall back to an unlocked bootloader trigger to deny secure services. Point is the bootloader knows we are unlocked. We got a preboot screen telling us that the device is insecure. No one has been able to get rid of this. Question is where is this flag being set, how is it being passed to Google play services, and can it be masked?
[Magisk] andriy_:
Thank you :) looks like hiding the Manager has done the trick.
[Magisk] Raygen:
And i thought that i couldn't read the logs well, there's really no trace of MagiskHide actions then! I admit i give up on trying to read the logcats tho

Well it's a start, thanks for now.

The phone is a OnePlus One A0001 "bacon" running the latest version of Denser's LineageOS 14.1.

I don't remember to have done system updates or anything major really, from when this issue appeared. Only Magisk updates. Maybe, i could try to install previous versions of Magisk to see if those are the culprit?
[Magisk] BossNexusS:
I got in the canary channel somehow by accident. How did you switch back to the stable channel? Did you have to fully unroot and install the stable? Can you just dirty flash the stable?
[Magisk] kotuamoalt:
The channel settings are in the settings menu.
[Magisk] BossNexusS:
Yeah I know, but is it ok to go from canary to stable without unrooting? Can I just change to stable and flash Magisk 19.3 over 19.4?
[Magisk] kotuamoalt:
Yeah, I wouldn't recommend doing that. If you're going to go backwards, I recommend you do a complete uninstall of magisk, and start over with the version you want.

---------- Post added at 03:32 AM ---------- Previous post was at 03:19 AM ----------

You did create a backup before you did this, yes?
[Magisk] BossNexusS:
When I update my phone/dirty flash rom in twrp can I just flash 19.3 instead of the canary build or is that also not recommended?
[Magisk] kotuamoalt:
Again, I wouldn't recommend it, but you can try. In a worst-case scenario, you can always do a factory reset, and start from scratch. And always make a backup in TWRP, BEFORE you start fiddling around with your phone. It will ultimately save you a lot of time and grief. If it were me, I would use the latest magisk uninstaller, do the OTA update, then install my preferred version of magisk. I am running Lineage OS nightly, and I just dirty flash the newest ROM and I'm good to go. I think OTA works differently, and you have to uninstall magisk before updating. This is my understanding, but I could be wrong.
[Magisk] BossNexusS:
When I update from oneplus official I have to reflash magisk because of the a/b partition stuff. I'll have to use the uninstaller and then flash stable magisk then.
[Magisk] fgozal:
Hello guys .i install magisk .i want to enable volte on samsung galaxy s10+ .i install module.but nothing .i cant find volte obtion in my setting.
[Magisk] kotuamoalt:
That's what I would do. And don't update magisk unless you have to.

---------- Post added at 06:46 AM ---------- Previous post was at 06:36 AM ----------

That is because it is designed for a Pixel phone.

It literally says it in the description.
[Magisk] fgozal:
Please tell me where can i find for galaxy s10+ ?
[Magisk] zgfg:
Post such question in the Galaxy s10+ forum, not here

First, because it's completely off topic here.

Second, for your own good - there must be more users and experts to know how to enable VoLTE on your phone, possible perks about, etc
[Magisk] learnmistakes~#:
I cant find a way to root my vivo y51, i tried to flash even the latest version of magisk zip. But i got error 1 using twrp. I tried previous method but still can't find a way[IMG="Error log"]https://i.imgur.com/B92Eje7.jpg[/IMG]
[Magisk] dd721411:
First of all, 18.1 isn't the latest version of Magisk. Check for the latest one on the Announcement Thread.

Secondly, what TWRP are you using and what version is it?

Lastly, have you searched for any rooting methods on your device's forum? Always go to that forum first because there might be someone who successfully rooted their phones and shared the procedure there.

Good luck! :good:
[Magisk] guest4711:
The recovery log should show whats going one. And did you ask in your devices forum for tips?
[Magisk] learnmistakes~#:
Yes sir i did flash Magisk-v19.3 before, but installation failed. I only used this stock rom version PD1510F_EX_C_2.6.13_vivo_qcom_LA.BR.1.1.3.c14-04700-8x16.0_msm8939, anyway my android version is 5.0.2 and Im using twrp-3.2.1 version.... Is there any possibilities to root my stock rom via magisk? not Supersu because it doesn't work anymore.
[Magisk] The Zwaluw:
With the latest update to root. I lost internet TV capabilities with Canal Digitaal and T-Mobile TV-Anywhere. Looks like there's somekind of check in the player for root violation. Probably Samsung found a way to block the player when rooted.

Samsung S6 (SM-G920F) with Magisk-rooted stock android 7: BTU-G920FXXU6ERF5-20180724103810.

Magisk hide didn't resolve the problem.
[Magisk] Didgeridoohan:
That only really tells us that something is triggering it. If it's Magisk itself, the bootloader or something else is yet to be determined for sure. You're using a Pixel 3a, right? It might very well be that it is the bootloader and that there's something about the 3a that makes it impossible for MagiskHide to properly mask it's state, but so far nothing you've shown makes that a certainty. More investigation needed...

As already stated: a recovery log is needed.

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

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] chris42too:
Pre-rooted ROM possible?

Hi,

is there a way to include Magisk into your ROM build, hence creating a pre-rooted ROM?

Thanks

Chris
[Magisk] dd721411:
Lol! This thread is for Magisk-related issues, not for asking to integrate Magisk into any custom ROMs. This also is against Magisk's developer's wish.

See page #3450. :)
[Magisk] chris42too:
Hilarious comment! :laugh: Integrating into a ROM sounded to me very much like an "General Support / Discussion". (Don't take that laughing serious, but consider reading your answers before posting.)

I am compiling the ROM for myself and this would just have decreased the steps after each build. However I respect topjohnwus view, if he does not want it to be done. Thanks for linking page 3450....
[Magisk] zgfg:
Please, have you rolled back in this thread and read eg what was asked/answered last week.

There was just somebody else who asked the same thing....
[Magisk] duh1:
I think you missed my point -- with an unlocked bootloader only on a stock device, no rooting, no Magisk, the June update to Google play services is notifying the Play store to deem certain apps incompatible, and the same apps when downloaded and installed from an apk mirror, won't run.

Then afterwards when the phone is rooted with Magisk, and MagiskHide is turned on for Play services, nothing changes -- the apps are still incompatible in the Play store and won't run when installed.

I'm not sure what is uncertain, these issues first occur when the bootloader is unlocked without root, and when installed, Magisk is not hiding that unlocked state from Play services. It would seem that Google has added a new detection for the unlocked state. I don't expect this will be immediately remedied, just a heads up that it's out there...
[Magisk] Didgeridoohan:
I'm not missing anything...

An unlocked bootloader has for a very long time triggered SafetyNet and other parts of the Google ecosystem. That's nothing new. Magisk can and has for a long time masked that unlocked state. The only thing you've showed is that there is still something that gets triggered after you've installed Magisk and MagiskHide is active.

An unlocked bootloader is one of the likely culprits, but it's nothing universal or we would have seen many more reports along this line. I have the June Play services with an unlocked bootloader and Magisk on several devices and aren't seeing what your are describing. That doesn't mean there's no issue, but just shows it isn't universal.

If I remember correctly I've only seen these reports from Pixel 3a users which makes it perfectly possible that there's some kind of extra bootloader check on those devices. But this is pure speculation, of course. Until someone can for sure show what's actually going on there's not much to do...
[Magisk] Elder Lyons:
Device:

Oneplus X on Android 7.1.2 (LOS 14.1)

Latest Magisk, hidding and everything.

It passes safety net but I am unable to play Pokemon Go, it loads into the game fine and then tells me the device is not supported. Once I uninstall magisk completely the issue is gone. I only have three modules running, Youtube Vanced, Energized Protection and Systemless Hosts. I tried using MagiskHide Props Config but that didn't work either. Any suggestions?
[Magisk] Dims_Camper:
Help :(

once again grab driver app detects root on latest magisk. Tried hiding everything I could, magisk hide done, hiding magisk manager also done. and i also put .nomedia on every folder that contains root or something. What can i do now?

edit. Tried using magisk canary channel that also didn't help. Tried the basic steps like turning on/off magisk hide didn't work either. Turning off usb debug also didn't work. Using magisk hide props module also didn't help :(

edit 2. Magisk Core Mode also didn't help, fml.
[Magisk] duh1:
I see your point as well. The 3a's came out in mid-May and initially when rooted with Magisk, unlocked bootloader was masked and all apps compatible in the Play store. Then with the June Play services update, that all changed. Still seeing that happening with new or factory reset phones set up offline masking fine until the mandatory updates come through. Is there a straight forward method to isolate what has changed?
[Magisk] KonoeKyon:
I'm on a Pixel 2XL having the same problems with some apps (Netflix being one) not showing up or showing incompatibility. The 2 XL forums have a few posts in some of the kernel threads referencing these issues as well. So I don't think it's only a problem with the 3a users. If you have a suggestion for what to look at to figure out how or what it's detecting to flag incompatibility I'm open to give it a try. I'm passing safety net and it shows certified in the play store.
[Magisk] Luniz2k1:
Hide Pokemon Go in Magisk hide settings. You may have to clear data for Pokemon Go as well afterwards.
[Magisk] typischandy:
Hello, thanks for your help.

I have now used a stock firmware and everything works again. I used "T719XXU2BRF4_T719OXA2BRF1_DBT".

Now I'm unsure. In the instructions for TWRP is that one should format a DATA:

"1. Boot to Twrp

2. Format Data partition using FORMAT DATA button under Wipe options.

(Note: This will wipe the internal storage)

3. Check DATA is mountable.

4. Install SuperSU (if root is required)

5. Install boot image patch below.

6. Reboot "

How should I proceed now? Should I use SuperSU? I've had good experiences with Magisk because it leans well against apps that root does not allow.
[Magisk] zgfg:
I really don't know for your device (?) but you see yourself that it must be an old guide, instructing about SuperSU.

Although, even for SuperSU, I don't get why was necessary to wipe Data...

If you go for Magisk, try installing without wiping Data.

Search here (top-right find the Search box to search in this thread about your device) and on XDA forum for your device about installing Magisk to your device.

Make a backup of your clean Boot image, if anything goes wrong, just flash the backup of your clean Boot image
[Magisk] xunholyx:
Formatting data gets rid of forced encryption. Or at least it used to when I had the HTC 10. Maybe things have changed? I don't know. I just keep my phone encrypted now.
[Magisk] andrew2432:
Did you hide the manager after getting everything installed? I always forget that part and get pissed at incompatible is until I figure it out
[Magisk] :
I have exactly the same problem on my Pixel 2 XL.
[Magisk] typischandy:
Thank you! I'll try it without deleting DATA. But first I do a backup. I forgot to mention my device, I am very sorry. It is a Samsung Galaxy Tab S2 8.0 SM-T719.
[Magisk] Didgeridoohan:
Unfortunately I have absolutely no idea...
[Magisk] Tabs78:
Hi.

Sorry for my english

I installed magisk 19.3.

The problem Is After two days It ask me to update and disable root.

I must reinstall 19.3 each two days
[Magisk] kotuamoalt:
Don't update. Unless you NEED to update, you don't need to update.
[Magisk] Impact7:
As many I cannot play Wizards Unite. It's hidden, manager is hidden and every file with the name of magisk is deleted.

Started the game once 8:57 and getting immediatly kicked.

Didn't start the game 8:59.

07-01 08:57:44.827 3264 3274 I Magisk : proc_monitor: [com.nianticlabs.hpwu.prod] PID=[662] UID=[10201] 07-01 08:57:55.494 3264 3274 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[1091] UID=[10026] 07-01 08:59:08.136 3264 3274 I Magisk : proc_monitor: [com.nianticlabs.hpwu.prod] PID=[1953] UID=[10201]
[Magisk] Tabs78:
If i don't update it says me magisk Is not installed and the apps doesn't see the root
[Magisk] andrew2432:
Wrong thread, post your issue here! This is for general topics, pokemon go is pretty specific!
[Magisk] wilsonhlacerda:
Some problem on your install. Magisk does not work this way.

Maybe you can try to completely remove Magisk, have clean system, reboot at least once this way and run for a few minutes, then install Magisk again.
[Magisk] Dims_Camper:
UPDATE! apparently grab driver app detects magisk manager AFTER being hidden (when it becomes manager). Restoring magisk manager to it's original state didn't trigger any root detection. Maybe [MENTION=4470081]topjohnwu[/MENTION] need to update naming randomisation or something? ?

edit. on the contrary side, banking app detects magisk manager BEFORE being hidden (as expected).
[Magisk] tuvok1981de:
You can see it here

https://xdaforums.com/galaxy-s4/general/lineageos-magisk-safetynet-t3943750
[Magisk] Didgeridoohan:
That sounds very unlikely...

Have you tried the UDS detection workaround (and other applicable tips from that link)?
[Magisk] martyfender:
When I try this in the terminal and test with Rootbeer Fresh it works.

When I download the script from github, I renamed it with the .sh extension and change the permissions to 777 and placed it in /data/adb/service.d then rebooted. It did not work.

Does the downloaded script need to be modified? Since many of us are not proficient with scripting, can anyone provide the necessary modifications?

Thanks
[Magisk] JayanWarden:
Hello everyone,

I installed the update for Magisk (manager 7.3.2 & magisk 19.3) to my Android 8 DOOGEE S60.

Before that I had a working Magisk 17.3 & manager 7.xx on my phone.

However after I patched my boot image and flashed it, Magisk still tells me that it's not installed.

I am 100% certain that I flashed the patched boot image.

Attached is the logfile from Magisk Manager.

Why is it telling me that it's not installed? Everything worked fine with magisk 17.3 before.