yashsingh1/xdaforums huggingface dataset:
[Magisk] curiousrom:
Root Checker Apps & Other Dev's Work

Thanks for the link but it's 404.

A search on https://f-droid.org/ for that app does not return any result: https://search.f-droid.org/?q=Root+Validator

Edit: It's still available in Play Store @ the present: Root Validator

See also https://github.com/d4rken/rootvalidator

***

Could you tell me the exact name of the app you made a screenshot of & where did you get it from please? Edit: found it in Play Store: Check Root Status - with SafetyNet

***

Reposting Other Dev's Work

To post about a solution & to link to the thread is cool but attaching [MENTION=3421557]Geofferey[/MENTION]'s work to your post is not cool IMO unless you have his permission.

He may be looking at the number of downloads & also update it but then the old version will remain attached to your post if it's the case.

Also if people go to his thread to get the zip they may Thanks :good: his post & get more info about it.

***
[Magisk] martyfender:
I can't read that screenshot, as well, as my native language, just like xda is English, only.
[Magisk] Hakkinen3K:
I don't know what the hell happened but, 19.x versions still not working on my xperia g8142 (core mode only) have to use 18.1 the best stable version working. For me magisk is dead after 18.1 for my Xperia.
[Magisk] x_x1_x:
Bank apps still detect root!

Everything seems to be normal and I selected Bank apps from MagiskHide but it still detect that I have root! What's wrong?
[Magisk] martyfender:
I don't think it will help you, but Your Magisk Canary version is not up to date, Magisk Canary version 19301 is available and Magisk Manager 216 is also available. Hiding the Magisk Manager, itself, in MM settings, may help you though. After doing this though, you may need to also clear the offending apps data and cache in Android app settings. In addition, does your device pass Safety Net?

What is your device, and Android version?

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] vMAC:
I'm having issue where I will wake up and it states that there has been an update to Magisk or Magisk Manager. However, when I go to the app OT states I am on latest and no update is necessary. Anyone else experiencing this?
[Magisk] xunholyx:
Yes. It's nothing to worry about, just a glitch that will be fixed in future updates.
[Magisk] :
Why are you still using MM?! It hasn't received a security patch for over a year
[Magisk] DragonFire1024:
We flash files like its going out of style, disabling verified boot, selinux permissive, unlocked kernel...and you are worried about a security patch?
[Magisk] sansnil:
I have a feeling AP is checking for a stock recovery so I'm going to perform some experiments with Recovery Switcher to test out this hypothesis when I have a chance. I hope not stock kernel too.
[Magisk] adrman:
I should have added that I also have stock recovery. I just fastboot TWRP when necessary.
[Magisk] nkk71:
I'll just through some wild and random thoughts your way, but have you considered randomizing the mounts, paths, etc... just a thought,

no clue if it has anything to do with it, as I have no access to AP

Nice work :good::good:, keep it coming
[Magisk] carlosggb:
I through the same dude, changing names at every boot will put Android Engineers crazy lol :D
[Magisk] devsk:
If I flash a custom kernel on top of it, how does Magisk cope with it?
[Magisk] knpk13:
Flash the kernel before magisk, as magisk modifies the kernel(boot.img)

I'm using a custom kernel as well.
[Magisk] nomadism:
Returned to Nexus 6P stock + Magisk + Superus for Magisk + Xposed for Magisk. I've been able to login to snapchat (that usually detects xposed), and also run a few bank apps that have a very strict and sophisticated method (i.e., rootcloack xposed or temp unroot always gets detected) to check whether the phone is rooted. In short, it works! I guess android pay will be the biggest challenge, but AP is not available at my place so we will have to wait.
[Magisk] devilloki:
forgive my poor english.

my devices is : huawei honor7 TL01H

my soft ver is :Emui 4.0.1-6.8.1

my rom is stock boot,stock system.

flash Magisk-v1,cann't boot,display:

boot img load failed.

pls help me

[MENTION=4470081]topjohnwu[/MENTION]

P.S.

supersu 2.76 has same issue.

but supersu 2.60 is ok
[Magisk] FunkeeC:
AP works fine for me unrooted w/ TWRP.
[Magisk] LuckyLukey:
Did you have a systemless or system root previously?

A few pages back I saw someone had been running a systemless and got it working by using the commands in fastboot to remove the .supersu permissions & directory, using the unsu.zip and then flashing to the instructions in the OP. I haven't tried it yet, but this will be the way I go.

Good luck.
[Magisk] danielcr12:
[MENTION=268073]top[/MENTION]jhonwu after installing it my screen battery and all the rest of my devices sensors are for some reason not being read or recognized. Meaning I can use my display and battery shows a unknown icon.
[Magisk] topjohnwu:
If Google is that stupid to detect the path, I would have nothing to say about their engineers lol

Of course if that's the case, I could randomize the path for it. But the real issue is that I cannot test it myself, and that will lower the speed of me trying all kinds of methods :)

Hope the new update will fix issues. Finger crossed
[Magisk] DarkN3ss61:
[MENTION=4470081]topjohnwu[/MENTION] I have added tasker support, check out my fork on GitHub https://github.com/DarkN3ss61/MagiskManager
[Magisk] anantharam:
I think you would already know this, but just to put it out if you can get Green in SafetyNet Playground Test , then it would pass Android Pay.

If google is detecting the path as one of their parameters, since they also get the path of everything in their data collection, then I don't think it is stupid to assume they would add a check for SU in the path, imho.
[Magisk] mobileman88:
It passes Safetynet Playground Test, but have yet to test it with AP since it got broken about 1 week ago.
[Magisk] RandomPooka:
I'm not clear on what this does for/with Tasker. Can you give a bit of detail on how Tasker support is used, or an example of usage?
[Magisk] Jammol:
A good example would be for me. I often go to the gas station while working en route to another hospital. I have an nfc tag mounted on my command center, a simple nfc tap to run a Tasker command to flip the root switch saves a lot of time. Won't even need to take wake the device. The spot on my command center is also a cubby spot to keep my phone.

Tap tag, walk in, get stuff pay, done. A secondary tag can also be used to flip the switch again.
[Magisk] broomer68:
It could be even more automated by location, so when you are there, root will be switched off, and when leaving, switches on again.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[Magisk] topjohnwu:
Thanks, I haven't replied to your Github issue because a new method is coming.

It should be much easier for Tasker support.
[Magisk] Jammol:
I think I just had a phonegasm reading your reply!!! Lol. I totally forgot about that feature!!!
[Magisk] Gian1901:
I uninstall with the zip because I have problems with Snapchat but I still have the crashes.

I think is the phh superuser.
[Magisk] toshi127k:
here you go

magisk-v6k.zip
[Magisk] Artim_96:
There is only one Magisk version for all devices, so best reflash the whole ROM. For XPosed of course the alt version.
[Magisk] Kasimodo:
Thank you Artim.

Can I ask you the link for xposed framework ALT version? :/
[Magisk] ryaniskira:
Magisk Mod not completly installing.

I am trying to adapt TBO's Black Pixel Launcher to work with Magisk, and only the wallpaper picker ever installs, the actual launcher apk itself never installs. Can anyone break this down and see what I am doing wrong?

Here is the zip file.
[Magisk] Artim_96:
everything is linked in the OP
[Magisk] jdcnosse:
How does this work with a custom kernel? I know you flash the custom kernel before Magisk, but does the phone yell at you for using a custom kernel when you disable root?
[Magisk] :
Thanks. Hopefully it will work after this
[Magisk] heslo.rb26:
Custom kernel is fine... running ElementalX on my HTC10 and Magisk works without an issue
[Magisk] EriolAncalagon:
I wanted to voice my "thank you" for this. I was going to post a scathing thing about why doesn't it say to install the android app from the store to make root work... and then re-read it and found out that apparently MY reading skills could be better.

Either way, this works great so far. Glad to have it.
[Magisk] hutigre:
Xperia Z3 can't get back on after flashin magisk v6

Hi i just flashed magisk v6 on my xperia z3 (android 6.0) after unrooting it with super SU, when flashing was done (with TWR) i clicked on reboot but my phone don'tget back on. When i push the power button he just vibrates a bit can someone help me ?
[Magisk] moosc:
So the modify Su root was working fine. Then I started get notifications to up date Su binary but using the superuser app doesn't provide that option.. reading the reviews alot of other users having the same issues. Running stock beta 7.0 Nexus 6
[Magisk] dracinn:
I'm unable to get it working on CM13 Nexus 6P.
[Magisk] JudgeDread11:
You'll have to wait until somebody who knows how to do it will make a magisk module for the new version, or do it yourself if you can.

---------- Post added at 03:33 AM ---------- Previous post was at 03:31 AM ----------

What do you expect to get out of this post. If you want help you need to provide more information.
[Magisk] dracinn:
I had install stock CM and and Magisk v6 along with the Magisk-SuperSu zip, says root is mounted but can't toggle it.
[Magisk] churchey360:
So can we just flash magisk on CyanogenMod and use the root that comes with CyanogenMod ROM?
[Magisk] RonnYap:
After flashing , when reboot system in TWRP

will ask to install su because no root

Did you install it or jus ignore?
[Magisk] abuddlah:
Hi,

Im getting some errors on my Oneplus3. I ran all the install and also phh superuser zip and app. When I reboot, i got a notification of "Install Superuser. The su binary is out of date"

What can I do? please help :(
[Magisk] hotaru2k3:
i just reflashed my nexus 6p today and magisk doesn't seem to be working. here's what I did:

flashed Magisk-uninstaller.zip in recovery

flashed stock boot.img in bootloader

flashed Magisk-v6.zip and phh-superuser-17-magisk.zip in recovery

after rebooting my phone, root isn't working. /data/magisk.img does get mounted to /magisk/, and I can run su, but it doesn't give me root. the superuser app is showing a notification saying the su binary needs to be updated. i've tried installing some other magisk modules since then, and while the files for the modules are present in /magisk, they don't show up under /system, so it looks like something is going wrong with magisk itself, rather than just being a problem with su.

any ideas how to fix this?
[Magisk] tb79:
Safetynet Test in magiskmanager failed,

In checkrootstatus App all fine.

OnePlusOne [MENTION=3352421]bootlegger[/MENTION]s 4.1 Pie
[Magisk] :
1) First of all you don't need to leave your bootloader unlocked. It's just as easy to relock it as unlocking it. Nobody seems to understand this.

2) my selinux is set to enforcing. No issues here.

3) Android monthly security patches fix critical system security holes, including firmware ones. You're telling me you're ok running the old wpa2 krack-vulnerable algorithm? Just going to a public setting and ticking your WiFi on would render everything you do on your phone unsafe. Not to mention physical vulnerabilities... What if someone stole your device? Since it seems you're ok with an unlocked bootloader, all they'd have to do is flash a rogue kernel on your device and brute Force your encryption password, which probably isn't longer than 20 characters since you'd have to know how to change it manually in terminal emulator or using the deprecated cryptfs app.

Do your research. This stuff is important in 2019.
[Magisk] DragonFire1024:
You cannot relock a bootloader on every device. All of what you mention requires they have physical access to the device and can get into it. If one is to become paranoid over these things, one should not partake. Security patches don't fix everything.
[Magisk] :
You ignored half of my reply. You're wrong, anyone can get access through the WiFi network, Bluetooth, the INTERNET through JavaScript or a cookie. An MMS message. The list goes on. Please don't waste my time.
[Magisk] DragonFire1024:
Those are your concerns. There's no reason to fear monger. Have a good day
[Magisk] hildeb:
I have a general question regarding updates: I upgraded from Magisk 19.2 -> 19.3 in-app.

(I'm not using any special modules, all I do is root hiding, since Pokemon Go and Banking Apps/G Pay won't work on the Pixel Experience Rom otherwise, as well as the systemless hosts file for AdAway)

I then rebooted the phone and (waited quite a while) it wouldn't boot (stuck in the boot screen). I then restarted the phone and it would boot.

Magisk Manager wouldn't start, some apps wouldn't start either.

I then rebooted to recovery and ran the 19.3 uninstaller. The device would boot again. Apps were running ok.

I then installed the previous 19.2, and the device would boot again, apps were running ok. But Magisk Manager said Magisk is not installed.

I then removed the Magisk Manager and reinstalled the same version -> Suddenly Magisk was installed ok.

Are updates somehow broken when not using the original Magisk Manager package? Meaning do I have to unhide the Magisk Manager prior to updates?
[Magisk] Didgeridoohan:
Both those apps show the same thing (SafetyNet failed).

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

No. But if you had the Manager hidden, the uninstaller can't uninstall it (since it doesn't know the package name). If you then installed Magisk and kept the old (repackaged) Manager it can't be recognised by the new Magisk installation (since the random name isn't on the database).

Your booting issue and apps not working I can't say much about. Only way to know what that was about is to reproduce and save logs.

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] :
I'm not fear mongering, lol. I'm informing you to update your phone to a rom with the latest security patches, preferably a pie rom, so you'll be protected from these vulnerabilities. Once you find a rom like lineageos and keep up with the monthly update cycle your phone will be patched as the vulnerabilities come along. It's common sense, would you run windows XP on your desktop computer?
[Magisk] guest4711:
No, as long as OS/2 is running fine ;)
[Magisk] JudgeDread11:
Google Android versions in use and you'll see you are asking very few who think this way.

Many people use or versions for many different reasons (there are plenty of people still using Windows XP as well)

A common rain is older phones don't receive update anymore and cheaper phones don't even come with the newest version.

Most people using root are opening several security holes and few ever have problems.

IMHO if the date you Carrie on your phone is so sensitive then it's not advisable to root your phone or have it on your phone at all. There are better more secure place for sensitive data.

Anybody trying to get in to my phone will be very disappointed.

And noon of all this is Magisk related and therefore shouldn't be on this thread.
[Magisk] :
The appreciation for good security advice is lacking, and it's sad. Not only do ridiculous replies get favored, I get replies trying to defend why people use outdated insecure malware ridden software? What has this world come to. It's full of idiots.
[Magisk] twist3d0n3:
:crying:
[Magisk] StanLeY Sd:
[Help] Disable dm-verity and force encryption

Hy...

I own a Xiaomi device.(redmi 6 pro)

I wanna disable dm-verity and force encryption using magisk.

echo KEEPVERITY=false>>/data/.magisk

echo KEEPFORCEENCRYPT=false>>/data/.magisk

I read somewhere that they can be disabled by running above commands. My doubt is, can i run them on twrp terminal before flashing magisk or i should flash magisk first then running those commands.??

Second doubt is, after successful installation of magisk, how to remove root keepin dm-verity & Force encryption disabled.

Thank you!
[Magisk] DinoDisaster:
I have just updated to magisk 19.3, and now my Google Photos app crashes after a few seconds.
[Magisk] Didgeridoohan:
Those commands tell the installer to patch the boot image, so they need to run before installation.

But if your only reason to flash Magisk is to disable those, there are more specific tools available.

Example: https://xdaforums.com/android/software/universal-dm-verity-forceencrypt-t3817389

Logs or it didn't happen...
[Magisk] xunholyx:
Not everyone can afford a new phone. And many people can only afford phones that don't get custom ROM support. Marshmallow was probably the last update for his.
[Magisk] trojanz:
Updated to magisk 19.3 and magisk hide isn't working on an app that needs hide to work. Do i have to downgrade to 19.2? Is this a known issue or isolated. Using OPO.
[Magisk] Ballroomblitz:
Is the systemiser module actually called systemiser? I can't find it.
[Magisk] Lothaen:
HTC Desire 626 help

hey,

My kids want to play Pokemon Go and I have an old HTC Desire 626 - only catch is it doesn't run Pokemon Go saying its unsupported - I think its because the bootloader is unlocked, I tried to root it and install Magisk but I have no clue what this boot.img patching thing is all about... I thought it'd be easy but it errors when trying to flash from TWRP

anyone have a proper newbie guide I can follow?

thanks
[Magisk] sdz2:
I'm still rocking the original Droid Turbo (had it 4+ years) on its third battery. The devs never got Verizon VoLTE working on AOSP, and the latest stock ROM is MM.

I run Magisk, Xposed, XPrivacyLua, AFWall+, AdAway, and Debloater. I use websites over bloated apps where possible (YouTube, Facebook, etc). It's surprisingly still bearable for me.

I've searched specs for over a year now. Every bootloader unlockable, Verizon compatible phone was missing something for me. For one, I hate notches. I'll buy the OnePlus 7 Pro soon, now that the initial issues are supposedly patched.
[Magisk] martyfender:
App Systemizer (Terminal Emulator)

https://xdaforums.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851

You also need a terminal emulator program installed to run it from. I recommend Terminal Emulator for Android by Jack Palevich.

According to a recent post in the above thread, you my also need the Magisk module: Busybox for Android NDK installed, also. I'm not sure, as I have always had it installed, or another version of Busybox, in the past.
[Magisk] RMarques:
It has stopped dropping root so far. Thanks again man!
[Magisk] Ramme:
its worked, thank you
[Magisk] guest4711:
Its called App Systemizer. If you don't find it, clear the repo cache (MM -- Settings -- Clear Repo Cache), then go to Download and refresh the list.
[Magisk] kotuamoalt:
:svetius:
[Magisk] BeeJ1109:
patch file option for output in latest version of manager missing

How do Samsung users create patched_boot.img.tar file, now this option is now removed from latest version of magisk manager. Why was it removed. Now only .img format is available, which will not work in ODIN to flash the patched file via a PC connected to Samsung device.

I have a previous saved patched_boot.img.tar created from same boot.img original, but patched with version 7.1. Is there any changes when magisk in updated from magisk versions 17.1 to 17.3 in regards to using a previously patched file compared to updating to the latest magisk manager 7.1 to 7.2. files.
[Magisk] kotuamoalt:
Try adding the ".tar" extention to the file. If memory serves me correctly, I have done that in the past and it worked.
[Magisk] warrencoakley:
I've been getting the same over the last week or 2. Stating there is an update but when I press on it Magisk is up to date already and nothing needs to be done. I wonder if this is a bug or something.
[Magisk] ayesse:
I can't fetch downloadable modules, i have to refresh multiple times

Xiaomi Mi A2 Lite, Stock Android 9
[Magisk] Ch3vr0n:
Play store suddenly reports Netflix is no longer compatible with my Pixel 3 XL rooted with magisk. Passing magisk safetynet. Currently running netflix 7.13.0 build 15 34276 and latest STABLE Magisk manager and magisk. Play store still reports "certified", yet netflix app can no longer be found in play store app and PC browser (firefox) reports "incompatible" with my pixel 3 XL.

** edit ** could manually install latest version, kept crashing, restored TiBu backup, now that one crashes too as well as build 13 and i'm without netflix entirely
[Magisk] Chillipaste:
So I flashed v19.3 via twrp but I am unable to install modules. An error says I need to install the latest version of Magisk.

I am on Xiaomi Mi9se on global miui rom.

See attached screenshots.

Magisk manager detects I have the latest version, but when I try to install a module, it says I don't have the latest version

I also noticed a popup saying "Requires additional Setup. Your device needs additional setup for Magisk to work properly. It will download the Magisk setup zip, do you want to proceed now?". See screenshot.

If I let it perform the additional setup, my phone bootloops to twrp.

Any ideas?
[Magisk] decayed.cell:
Got the same issue on MIUI Global 10.2.2.0 PFBMIXM, Mi 9 SE
[Magisk] zzz2002:
Maybe I missing something, but I get a notification every time anything I have installed under Magisk changes.

Using the latest versions of Ivan'shero2lte, opengspps & Magisk.
[Magisk] dbolivar:
Core Only mode without TWRP access to /data

TL;DR: Is there any way to enable core-only mode, or disable a specific module, when we are facing bootloop issues

and

TWRP is unable to access /data, because it's unable to decrypt the partition?

I've faced this situation recently, due to a bad-behaving module, and I had to reflash my firmware, losing all my data. All the suggested workarounds, like creating /data/cache/.disable_magisk or erasing /data/adb/modules/<module>, couldn't be used, since TWRP didn't have access to my /data partition, due to lack of support of the encryption scheme used in my phone (not uncommon, by the way, as it seems there's no standard among vendors).

The only partitions that could be accessed were /vendor and /system (but RW access to the latter would probably make the firmware unbootable). I've even tried to modify the init.rc from the kernel's RAMdisk, to erase the bad module after /data was mounted, but it didn't work. I could, of course, boot the system with the original kernel (without root), but it was useless, as I couldn't access /data without root.

I'm wondering if there's any alternative, like creating .disable_magisk in another partition, or a patching tool for the Magisk RAMdisk.
[Magisk] Logix:
Please keep the OT out of here I just had to delete like 20 posts of back and forth nonsense. I have had 10+ reports in this thread.

Keep Off Topic to the off topic forum.

It is part of the rules consider this your warning. I will monitor this thread going forward and will be issuing instant infractions or bans for people who dont want to follow the rules.
[Magisk] martyfender:
I believe it is a bug in the current Magisk Manager, I see it even in today's latest Canary release, 218.

Go to settings and clear the repo cache, then go back to the main page and swipe down to refresh.
[Magisk] nanquan:
I only get notifications for when there are updates to Magisk itself. I have to manually go to Magisk -> Downloads to find out about updates to any modules I have installed.
[Magisk] guest4711:
Afaik the core-only flag is /cache/.disable_magisk

On my device(s) /cache is an own partition...
[Magisk] dbolivar:
My device has A/B partitions, cache is inside /data... It would be ideal if /cache was separate and not encrypted, but that's not the case. :(

There used to be a safemode-key, if I'm not mistaken, like boot with VolumeUp pressed or something, but I tried and didn't work. That would be nice as a last resort...
[Magisk] RMarques:
Just as a follow up...just lost root today, even after using the workaround.

I'll update OOS today so, fingers crossed!