Database Develop

[ROOT][64-Bit] Root for Non US HTC Desire 510

I know you guys have waited FOREVER for somebody to pick this project up.... I have, and today I preset to you...ROOT
WARNNG: THIS DOES USE A CUSTOM KERNEL
Steps:
Unlock bootloader using this TUTORIAL:
http://forum.xda-developers.com/desire-510/help/qa-bootloader-unlock-htc-desire-510-t2911491
DO NOT FLASH RECOVERY FROM THAT THREAD
Grab boot.img from here:
http://goo.gl/AlaZpI
Old Versions:
http://goo.gl/dzQ3Wi
Load boot.img into fastboot folder
run this command:
"fastboot flash boot HTC-Desire-510-64bit-Root.img"
Install SuperSU from Play Store. Select cancel everytime it asks to update. It WON'T work​
VigiDroid said:
Okay first things first let's get a couple things straight. SuperSU is the APPLICATION that allows for other applications to gain root access. When you first run SuperSU it will complain that the SU BINARIES are out of date. This is not important. It claims that you need a custom recovery (typically TWRP or CWM) to install the BINARIES, or you can try install it without it. This does not work, but it doesn't matter, since the out dated BINARIES still function correctly.
It is important to identify the difference between those two to avoid confusion though. SuperSU is the APPLICATION that allows root, and SU is the BINARIES which allow SuperSU to have root access.
I had trouble at first, but after a couple of initial reboots, SuperSU functioned correctly and granted root applications access. Once you have rebooted a few times, try download "root access checker" and run it to see if it works.
Click to expand...
Click to collapse

Good job rbheromax

thanks!

Thank you soo much
---------- Post added at 05:59 PM ---------- Previous post was at 05:32 PM ----------
I have started my phone succesfully with this kernel,but no root access (i have installed supersu alredy)
(I dont have recovery on my phone)

Sorry for my english.
I'm not a programmer or expert android but by unpacking the file boot.img, there are necessary files to root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I only checked to make sure that root could be accessed by shell. I'll upload another version with it having universal access
Sent from my XT1028 using XDA Free mobile app

rbheromax said:
I only checked to make sure that root could be accessed by shell. I'll upload another version with it having universal access
Sent from my XT1028 using XDA Free mobile app
Click to expand...
Click to collapse
Alright,thanks.

this will install su to /system as well as remove write protection
http://tempsend.com/33CE45F61D

rbheromax said:
this will install su to /system as well as remove write protection
http://tempsend.com/33CE45F61D
Click to expand...
Click to collapse
You gave me this file in private message,i have tried it and not worked,i had same problem
Edit: Its say there is no SU Binaries installed and SuperSu not installable......(i use SuperSU Free from google play)

Can anyone post a video which shows the process (and success!) of root the HTC Desire 510 64bit (EU)
Thanks

GianniDarkos said:
Can anyone post a video which shows the process (and success!) of root the HTC Desire 510 64bit (EU)
Thanks
Click to expand...
Click to collapse
Fix for root is coming soon,please be patient.

Ops ok, sorry
(I did not understand, I can not read english well)

http://goo.gl/AlaZpI
link updated in OP
it IS rooted, but you cannot update in-app using SuperSU. for some unknown reason, it wont work
use any other root managing app and you should be ok. try using koush's superuser app

Change Screen Size
Guys,
If you wanna be normaly screen size (not original sh.. screen sizes) than download this apk to your phone:
https://play.google.com/store/apps/details?id=com.nomone.resolution_changer&hl=hu
NOMone Resolution Changer (its free)
Open the app and you see
"Width" "Height" "DPI"
Change Width to 720
Change Height to 1280
Change DPI to 312
and click on apply
Or second way:
Open the app
Click on "Select device template"
and choose Motorola Moto X or Htc One X
Click on apply and you done
If you dont like this sizes,dont worry,apk will restore stock sizes after 10 sec and after 1 minutes too.
Good Luck to all.

rbheromax said:
http://goo.gl/AlaZpI
link updated in OP
it IS rooted, but you cannot update in-app using SuperSU. for some unknown reason, it wont work
use any other root managing app and you should be ok. try using koush's superuser app
Click to expand...
Click to collapse
Have you got a link please. I can't seem to find that one in particular

Burtrum57 said:
Have you got a link please. I can't seem to find that one in particular
Click to expand...
Click to collapse
Check the link in the OP? Hit the big blue download button on it and follow the instructions from the OP. In case you missed it, you have to use FASTBOOT to FLASH the KERNEL. So in other words, use this command: fastboot flash boot HTC-Desire-510-64-Bit-Root.img

VigiDroid said:
Check the link in the OP? Hit the big blue download button on it and follow the instructions from the OP. In case you missed it, you have to use FASTBOOT to FLASH the KERNEL. So in other words, use this command: fastboot flash boot HTC-Desire-510-64-Bit-Root.img
Click to expand...
Click to collapse
I've downloaded the kernal, fastboot flashed it and rebooted the phone and all is going well. Your correct supersu won't install without twrp or cwm. I have busybox installed and it is ok but a couple other apps complain that things aren't right.

Burtrum57 said:
I've downloaded the kernal, fastboot flashed it and rebooted the phone and all is going well. Your correct supersu won't install without twrp or cwm. I have busybox installed and it is ok but a couple other apps complain that things aren't right.
Click to expand...
Click to collapse
Okay first things first let's get a couple things straight. SuperSU is the APPLICATION that allows for other applications to gain root access. When you first run SuperSU it will complain that the SU BINARIES are out of date. This is not important. It claims that you need a custom recovery (typically TWRP or CWM) to install the BINARIES, or you can try install it without it. This does not work, but it doesn't matter, since the out dated BINARIES still function correctly.
It is important to identify the difference between those two to avoid confusion though. SuperSU is the APPLICATION that allows root, and SU is the BINARIES which allow SuperSU to have root access.
I had trouble at first, but after a couple of initial reboots, SuperSU functioned correctly and granted root applications access. Once you have rebooted a few times, try download "root access checker" and run it to see if it works.

You are right. All seems to be correct, I have root access, can copy, delete and move files with no problems. A couple apps do complain but if ignore them all still works well. Thank you so much. It may be a small step but it is a huge leap for what can now be done with this phone

/system/build.prop for Europe
Could someone on a European 510 please post their /system/build.prop file?
adb shell
su
cat /system/build.prop
...and since you're at it, could you post a stock (or not) TWRP backup? I know I am asking a lot, but after all I did help (in a very small way) @rbheromax in achieving root for you guys.
Thanks very much!

Installing Magisk on an Emulator?

For the better part of a week I have been trying to install Magisk on an emulator. I have installed Magisk Manager successfully on "Rooted" x86 emulator on a virtual box. The problem comes down to my inability to successfully install TWRP and access the bootloader. The ordinary instructions. I am curious if there is a way or method to install MAGISK directly from ADB shell? Or even better through another method?

magisklover said:
For the better part of a week I have been trying to install Magisk on an emulator. I have installed Magisk Manager successfully on "Rooted" x86 emulator on a virtual box. The problem comes down to my inability to successfully install TWRP and access the bootloader. The ordinary instructions. I am curious if there is a way or method to install MAGISK directly from ADB shell? Or even better through another method?
Click to expand...
Click to collapse
Is this something very difficult/impossible thing to do?

Flashfire the magisk zip?
Load the zip through the magisk manager modules screen?

tymestopm said:
Flashfire the magisk zip?
Load the zip through the magisk manager modules screen?
Click to expand...
Click to collapse
With which emulator? VirtualBox x86 android?

tymestopm said:
Flashfire the magisk zip?
Load the zip through the magisk manager modules screen?
Click to expand...
Click to collapse
Also the Magisk Manager requires to load into recovery/bootloader mode to install it. I was hoping I could install it via adb or similar.

Anyone smarter than me has a solution?

Do you guys think that this is even possible?

I tried so many different things, but still no way.

I was able to install Magisk V12.0 on Android x86 7.1.2 rc2, using this tools to create a "fake" boot.img using kernel and ramdisk.img files:
https://forum.xda-developers.com/showthread.php?t=2319018
But I had to make small modifications in the install scripts and magic_mask.sh to bypass some errors and correctly mount system to the magisk folder. Newer versions don't have magic_mask.sh anymore but a binary, so unless you modify the source and compile it yourself I think it won't work. Probably because v12.0 is somewhat old I can't install modules automatically using Magisk Manager tho...

lfom said:
I was able to install Magisk V12.0 on Android x86 7.1.2 rc2, using this tools to create a "fake" boot.img using kernel and ramdisk.img files:
https://forum.xda-developers.com/showthread.php?t=2319018
But I had to make small modifications in the install scripts and magic_mask.sh to bypass some errors and correctly mount system to the magisk folder. Newer versions don't have magic_mask.sh anymore but a binary, so unless you modify the source and compile it yourself I think it won't work. Probably because v12.0 is somewhat old I can't install modules automatically using Magisk Manager tho...
Click to expand...
Click to collapse
Can you pass safetynet check?
Would you like to get paid 500$ by doing a demo for me via teamviewer?

magisklover said:
Can you pass safetynet check?
Would you like to get paid 500$ by doing a demo for me via teamviewer?
Click to expand...
Click to collapse
No, you cannot pass SafetyNet because it's a debug build (Android x86, probably emulator also don't have proper fingerprint, etc...). You must fake a real device that was certified by Google to pass SafetyNet, and probably you'd also need a newer version of Magisk since Google patched the SafetyNet trick that Magisk used prior to v14.0 by what I've read...

magisklover said:
For the better part of a week I have been trying to install Magisk on an emulator. I have installed Magisk Manager successfully on "Rooted" x86 emulator on a virtual box. The problem comes down to my inability to successfully install TWRP and access the bootloader. The ordinary instructions. I am curious if there is a way or method to install MAGISK directly from ADB shell? Or even better through another method?
Click to expand...
Click to collapse
Its depend of on wich emaulator you want to install Magisk, certains have an debug mode (its give an internal ADB direct access) same as with Andy and other(s).
Now most of android emulator(s) has removed their modded recovery and lets you in place access directly to an adb interface to debug the VM(s) if needed.

lfom said:
No, you cannot pass SafetyNet because it's a debug build (Android x86, probably emulator also don't have proper fingerprint, etc...). You must fake a real device that was certified by Google to pass SafetyNet, and probably you'd also need a newer version of Magisk since Google patched the SafetyNet trick that Magisk used prior to v14.0 by what I've read...
Click to expand...
Click to collapse
Would there be a way to fake this fingerprint and successfully pass it?

My friend is crazy for this to work so he can play Pokemon Go on his computer. I don't understand why it is still being played after all the junk niantic has done.

lfom said:
I was able to install Magisk V12.0 on Android x86 7.1.2 rc2, using this tools to create a "fake" boot.img using kernel and ramdisk.img files:
https://forum.xda-developers.com/showthread.php?t=2319018
But I had to make small modifications in the install scripts and magic_mask.sh to bypass some errors and correctly mount system to the magisk folder. Newer versions don't have magic_mask.sh anymore but a binary, so unless you modify the source and compile it yourself I think it won't work. Probably because v12.0 is somewhat old I can't install modules automatically using Magisk Manager tho...
Click to expand...
Click to collapse
Could you elaborate in more details on how you did it exactly?

Creater0822 said:
Could you elaborate in more details on how you did it exactly?
Click to expand...
Click to collapse
Check this, and if you still need any questions, please ask in that thread, I can try to remember what I did and reply if I remember (I am not using it anymore):
https://forum.xda-developers.com/apps/magisk/mod-magisk-v12-0-android-x86-7-1-rc2-t3699183

Integrate Magisk root into Nox Player and other emulators
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
- Bring Magisk / Zygisk to Nox
- MagiskHide / MagiskDenyList for hiding root
- Magisk / Zygisk modules work properly!
More information click here

huskydg said:
Integrate Magisk root into Nox Player and other emulators
Features
- Bring Magisk / Zygisk to Nox
- MagiskHide / MagiskDenyList for hiding root
- Magisk / Zygisk modules work properly!
More information click here
Click to expand...
Click to collapse
Nice work.

huskydg said:
Integrate Magisk root into Nox Player and other emulators
Features
- Bring Magisk / Zygisk to Nox
- MagiskHide / MagiskDenyList for hiding root
- Magisk / Zygisk modules work properly!
More information click here
Click to expand...
Click to collapse
I tried to install Magisk on Nox Player, everything is working well except Magisk Props Config module. I want to use this module and fake my emulator device fingerprint, but it doesn't work (I means I can change and apply the setting, but after I rebooted my emulator device, everything is same, not change).
Anyone can help to confirm if this module can work well with Magisk on Nox player ? If Nox Player can't work with this module, which emulator tool can I try, ex: MuMu or LDPlayer or Memu? Thank you so much.
Here is my reference link: https://github.com/HuskyDG/MagiskOnEmu

ctsprofile: false and basicIntegrity: false magisk hide error

I am on a honor 8 running Android 7.0 and magisk v16. I Uninstalled xposed through custom recovery, didn't do anything. anyone have any ideas? when I run the SN check both ctsprofile: and basicIntegrity: show as false.

https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417

Didgeridoohan said:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
Click to expand...
Click to collapse
I have read through this, and I'm not sure if I'm missing something but I do not see anything that applies to the problem I am experiencing.

T0blerone said:
I have read through this, and I'm not sure if I'm missing something but I do not see anything that applies to the problem I am experiencing.
Click to expand...
Click to collapse
Really? There's quite a lot of tips on how to get MagiskHide to work and SafetyNet to pass in the wiki linked from that thread. What have you tried so far? And where are your logs?

Didgeridoohan said:
Really? There's quite a lot of tips on how to get MagiskHide to work and SafetyNet to pass in the wiki linked from that thread. What have you tried so far? And where are your logs?
Click to expand...
Click to collapse
I'm brand new to rooting. I rooted my first device yesterday so to be quite honest I'm kind of lost at this point. I haven't tried anything from the forum because I didn't see anything that mentioned how to get the basicIntegrity working. I saw methods that helped the other one if you have basic integrity working but I don't know how to fix that, or anything really.

T0blerone said:
I have read through this, and I'm not sure if I'm missing something but I do not see anything that applies to the problem I am experiencing.
Click to expand...
Click to collapse
Kindly Do The Following
- Install RootBeer Sample From PlayStore --> Send Its Screenshots Before Adding This App To Magisk Hide & After Adding This App To Magisk Hide
- Install SafetyNet Helper Sample Or SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status (Google PlayStore --> Settings --> Device Certification)

Dreamer(3MF) said:
Kindly Do The Following
- Install RootBeer Sample From PlayStore --> Send Its Screenshots Before Adding This App To Magisk Hide & After Adding This App To Magisk Hide
- Install SafetyNet Helper Sample Or SafetyNet Test From PlayStore & Send Its Screenshot
- Send The Screenshot Of PlayStore Device Certification Status (Google PlayStore --> Settings --> Device Certification)
Click to expand...
Click to collapse
I actually can't. as im so new I have less than 10 posts I'm not allowed to upload images. the root beer sample showed checks except four red x's on su binary, su exists, root native, and on root cloaking apps. SafetyNet failed with success on the request but said "fail (response payload validation failed)" and my device Certification is uncertified. hope that helps.

T0blerone said:
I actually can't. as im so new I have less than 10 posts I'm not allowed to upload images. the root beer sample showed checks except four red x's on su binary, su exists, root native, and on root cloaking apps. SafetyNet failed with success on the request but said "fail (response payload validation failed)" and my device Certification is uncertified. hope that helps.
Click to expand...
Click to collapse
For Passing The SafetyNet, Check This Post https://forum.xda-developers.com/ap...playstore-services-data-t3789498/post76682978.
Magisk-v16.4 Is Not Suitable For Most Of Us To Use Due To Many Issues So That Flash Its Replacement Magisk-v16.3.1(ThePatchedBinary) From This Link https://androidfilehost.com/?fid=962339331458996616 Or Magisk-v16.3 (Instead Of Magisk-v16.4).

T0blerone said:
I actually can't. as im so new I have less than 10 posts I'm not allowed to upload images. the root beer sample showed checks except four red x's on su binary, su exists, root native, and on root cloaking apps. SafetyNet failed with success on the request but said "fail (response payload validation failed)" and my device Certification is uncertified. hope that helps.
Click to expand...
Click to collapse
If you add the Rootbeer app to the MagiskHide list in the Manager and check again, we'll know of MagiskHide works on your device or not. With the app on the Hide list, all checkmarks should be green.
If it doesn't seem to work, the first thing to try is to toggle MagiskHide off and on in the Manager settings.

Didgeridoohan said:
If you add the Rootbeer app to the MagiskHide list in the Manager and check again, we'll know of MagiskHide works on your device or not. With the app on the Hide list, all checkmarks should be green.
If it doesn't seem to work, the first thing to try is to toggle MagiskHide off and on in the Manager settings.
Click to expand...
Click to collapse
I added it and nothing changed. I then toggled it off and on and ran the test a third time and got the same results.

T0blerone said:
I added it and nothing changed. I then toggled it off and on and ran the test a third time and got the same results.
Click to expand...
Click to collapse
Which means MagiskHide isn't working properly on your device. Or you have remnants of previous root stuff (if you were playing around with something else before flashing Magisk), or possibly stuff left over from Xposed. Have you uninstalled the Xposed Installer app?
If you can save the Magisk log to Pastebin and then post the id for that paste, we can at least take a look at that. If you then can install the beta release of Magisk (or an unofficial snapshot, since they're more up-to-date) and provide the magisk_debug.log, that would be even better.

Didgeridoohan said:
Which means MagiskHide isn't working properly on your device. Or you have remnants of previous root stuff (if you were playing around with something else before flashing Magisk), or possibly stuff left over from Xposed. Have you uninstalled the Xposed Installer app?
If you can save the Magisk log to Pastebin and then post the id for that paste, we can at least take a look at that. If you then can install the beta release of Magisk (or an unofficial snapshot, since they're more up-to-date) and provide the magisk_debug.log, that would be even better.
Click to expand...
Click to collapse
I removed the xposed installer app and the root cloaking checkmark went green.

Didgeridoohan said:
Which means MagiskHide isn't working properly on your device. Or you have remnants of previous root stuff (if you were playing around with something else before flashing Magisk), or possibly stuff left over from Xposed. Have you uninstalled the Xposed Installer app?
If you can save the Magisk log to Pastebin and then post the id for that paste, we can at least take a look at that. If you then can install the beta release of Magisk (or an unofficial snapshot, since they're more up-to-date) and provide the magisk_debug.log, that would be even better.
Click to expand...
Click to collapse
although that's green safetynet is still failed both in the magisk app and the separate safetynet test

T0blerone said:
although that's green safetynet is still failed both in the magisk app and the separate safetynet test
Click to expand...
Click to collapse
same as mine,but i use custom rom. device redmi note 2
RR, Viper, couldnt work to pass basic integrity and cts, i have tried flash safetynet fix but stillnothing

I have the same issue. But sometimes the checks fail and sometimes they dont

Same issue here
I am having the same problem. I tried everything, every possible option on the internet I could find. Managed to get "basicIntegraty: true" probably from uninstalling Xposed but I still am unable to fix "ctsProfile: false". Here are the screens from RootBeer Sample and SafetyNet:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Click to expand...
Click to collapse

zbysogi said:
I am having the same problem. I tried everything, every possible option on the internet I could find. Managed to get "basicIntegraty: true" probably from uninstalling Xposed but I still am unable to fix "ctsProfile: false". Here are the screens from RootBeer Sample and SafetyNet:
Click to expand...
Click to collapse
Busybox shouldn't have an impact on SafetyNet, but if you want to make sure that other apps don't defect it, uninstall the currently installed Busybox and install from the Magisk Manager instead.
For passing the CTS profile check you can use my MagiskHide Props Config module. Details here:
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228

Didgeridoohan said:
Busybox shouldn't have an impact on SafetyNet, but if you want to make sure that other apps don't defect it, uninstall the currently installed Busybox and install from the Magisk Manager instead.
For passing the CTS profile check you can use my MagiskHide Props Config module. Details here:
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Click to expand...
Click to collapse
Yeah. Im in the middle of sorting out the problem with modules not working. They show up in the modules tab in Magisk but dont work :/ Thus Magisk is not working properly. I can not even change the fingerprint using the Terminal Emulator :/ cause it doesnt even recognise Magisk being installed :/
EDIT:
half a day but its sorted. Thx

T0blerone said:
I am on a honor 8 running Android 7.0 and magisk v16. I Uninstalled xposed through custom recovery, didn't do anything. anyone have any ideas? when I run the SN check both ctsprofile: and basicIntegrity: show as false.
Click to expand...
Click to collapse
You can get both to pass. Here are the steps...
1. From your magisk, install these 2 modules: Riru - Core, and Riru - EdXposed (Sandbox or Yahfa is okay]
2. Reboot your device to activate both modules.
3. Install Xposed Installer APK by DVDandroid. You can get it here: https://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v33_36570c.apk
4. Reboot to activate the Xposed Installer app
5. Inside Xposed Installer app, go to downloads and install the HiddenCore Module.
6. Reboot and go back to Magisk and test the SafetyNet.
7. Boom! Everything passes now.

Magisk HIDE defeated by NemID code app

Magisk v16.4 (also tried v16.0)
I've hidden the app in the HIDE list, I repackaged Magisk, force stopped NemID, cleared cache and data, and the app still spots root. I've successfully hidden apps from root before using this method, so it's just this app here that somehow goes beyond the usual. Are there any further steps I can take to hide root from the app more thoroughly?
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Launchy21 said:
Magisk v16.4 (also tried v16.0)
I've hidden the app in the HIDE list, I repackaged Magisk, force stopped NemID, cleared cache and data, and the app still spots root. I've successfully hidden apps from root before using this method, so it's just this app here that somehow goes beyond the usual. Are there any further steps I can take to hide root from the app more thoroughly?
Thanks
Click to expand...
Click to collapse
I believe that the app detects root by any of the following things :-
1. Bootloader unlocked detection
2. Custom ROM detection
3. Presence of apps that require root
4. Reading log of root being used (which is very rare, but possible)
5. Some very private code that renders Magisk useless

Tested it, and the app looks for both Magisk and the Manager. With the app on the Hide list and the Manager repackaged I can open the app without issue. It doesn't seem to "remember" root. This is on stock OxygenOS and also NitrogenOS (both on Oreo).
The app might be detecting other properties of the ROM your using (if not stock) or other known root apps on your device. Try running a logcat when the app detects "root" to maybe see what it's detecting, or simply uninstall some root apps and try again.

It works for me aswell, im using custom rom 8.1, hide the app, repackage, reboot, open app
So if that doesnt work, you might wanna try another rom as mentioned above me

It seems the app changed its way of detecting root after their upgrade on 25/6. It also worked for me before by using Magisk Hide and repack Magisk manager, but not anymore.
It is a losing battle anyway, just a matter of time. So I do not expect this method will work for good.

yeah my nemid app also stopped working a few days ago. This is not good if its not possible to hide root from an app anymore

Since there are users reporting that they can open up the app with MagiskHide active for NemID and the Manager repackaged, it's very likely that the app is detecting some other thing on your device. It could be a property of a custom ROM you're using, it could be a root app, etc... Possible solutions: try a different ROM (as stock as possible), uninstall root apps, etc.
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Ok I'm running Samsung s7 stock oreo w. Root. Knox is tripped
Removed all apps needing root, installed magiskhide props config module, disabled systemless hosts.
Still no go. It worked until before latest update

mbeltoft said:
Ok I'm running Samsung s7 stock oreo w. Root. Knox is tripped
Removed all apps needing root, installed magiskhide props config module, disabled systemless hosts.
Still no go. It worked until before latest update
Click to expand...
Click to collapse
What Magisk version do you have? If not on beta v16.4, the issue might be that the app has a sub-process that previous Magisk versions can't hide automatically. Scratch that... Just went back and saw that the OP has tested it on v16.4.
Or, if you're unlucky it's checking Knox...
Does it only check for root at the start, or is it other points as well? As stated before, I can open the app just fine on both my Oneplus 3T and Nexus 6.

AFAIK it's only checking at start-up. It shows it's load screen for a few seconds ( but longer than before when it was working) and then give the error screen OP posted.
If you leave the app and reenter it it will show the main screen but jump back to the error screen whenever a button is pressed

I tested this on a pixel 2 with stock rom in this order :
All root apps installed, no magisk or root : working fine
All root apps installed, no magisk or root, custom kernel: working fine
All root apps installed, root and magisk, magisk hidden+magisk hide: not working
No root apps installed, root and magisk, magisk hidden+magisk hide: not working
No root apps installed, root and magisk, magisk manager not installed+magisk hide: working
I then tried cloning the apk without changing the name: not working
I tried cloning the app but changing the name of Magisk Manager from "Magisk Manager" to just "Manager" and then Nemid worked again.
Could it be the Nemid app is just looking to see if there's an app called Magisk Manager installed and if there is, the app failes
Unfortunately the cloned app doesn't work. Maybe we could have the "Hide magisk" function rename the app name too?
//Peter

Just tried cloning an entirely different app and renaming it "Magisk Manager" - after this the nemid app failed, so I guess that confirms that nemid just checks the name.
//Peter

Nice detective work.
By uninstall the app (not unroot) NemID works. If you use magisk 16.6 you can just reboot phone to get the manager again or just install the apk.
But if being able to change magisk managers name to something generic (like manager) or a custom name could be a great solution (I would change name to NemID). Because if nemid can defeat magiskhide, others will follow

I posted the findings in the beta thread but I think it got removed during thread cleanup. Any other way to let the developers know?

peter_dk01 said:
I posted the findings in the beta thread but I think it got removed during thread cleanup. Any other way to let the developers know?
Click to expand...
Click to collapse
It's already on the to-do list.

Didgeridoohan said:
It's already on the to-do list.
Click to expand...
Click to collapse
Perfect! Thank you ?

Didgeridoohan said:
It's already on the to-do list.
Click to expand...
Click to collapse
Unfortunately, the change is not included in the latest 5.8.1 release.

kqueenc said:
Unfortunately, the change is not included in the latest 5.8.1 release.
Click to expand...
Click to collapse
Manager v5.8.1 was simply a bug fix. Stability is prioritised over new features. You'll have to wait, and that feature will be available when it's available. Not before that...

Didgeridoohan said:
Manager v5.8.1 was simply a bug fix. Stability is prioritised over new features. You'll have to wait, and that feature will be available when it's available. Not before that...
Click to expand...
Click to collapse
Is there any other workaround to change the name of Magisk Manager App in order to bypass the check? And will there be any other consequence (like root cannot be detected by other app)?

kqueenc said:
Is there any other workaround to change the name of Magisk Manager App in order to bypass the check? And will there be any other consequence (like root cannot be detected by other app)?
Click to expand...
Click to collapse
Until there is a feature like that, you can uninstall or freeze the Manager whenever you need to use whatever app detects it.

Magisk Manager: Manager was denied Superuser rights (and buttons missing)

Please see the posted screenshot image for the problem. I just got a brand new OnePlus 8 Pro today, updated the firmware (it's current and running Android 11), unlocked the bootloader, installed my data, and rooted it. Since there is no TWRP for Android 11 for this device, I had to manually extract the current boot.img and patch it myself with Magisk Manager to root this device.
On the first boot after root, I launched Magisk Manager. The countdown timer was so fast, I did not have a chance to grant Magisk Manager root permissions. Now Magisk Manager is being denied Superuser permissions, and there are no buttons at the bottom of Magisk Manager to set Magisk Hide settings or set what apps are allowed Superuser/root.
I have googled as well as searched this forum for relevant help, and have found nothing helpful (really, I may have missed something, but I did try). How can I reset the apps allowed root permissions so that I can grant Magisk Manager the Superuser permissions it needs to function?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help is greatly appreciated!
I already tried force stopping Magisk Manager and clearing the storage for Magisk Manager (which did nothing to solve the problem).

https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access

Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access
Click to expand...
Click to collapse
Thank you for the reply. I found this article earlier (or a variant of it), and it does not appear to solve the issue. I don't have two different Magisk Managers installed. I just accidently denied the one Superuser access by not granting it Superuser access quickly enough.

The Magisk app does not need to ask for superuser access. It is the one that grants it... In other words, one way or the other Magisk is looking for a hidden Magisk app with a package name that doesn't match the one you're using.
Try deleting /data/adb/magisk.db. It'll reset everything (including granted superuser requests, etc) and you can reinstall the app and start over.

Didgeridoohan said:
The Magisk app does not need to ask for superuser access. It is the one that grants it... In other words, one way or the other Magisk is looking for a hidden Magisk app with a package name that doesn't match the one you're using.
Try deleting /data/adb/magisk.db. It'll reset everything (including granted superuser requests, etc) and you can reinstall the app and start over.
Click to expand...
Click to collapse
Thank you. This is no longer an issue (I have a new issue that is unrelated to this thread, so I'll search for the solution to it).

chriv said:
Thank you. This is no longer an issue (I have a new issue that is unrelated to this thread, so I'll search for the solution to it).
Click to expand...
Click to collapse
Just out of curiosity, did you solve it be deleting the database file?

Didgeridoohan said:
Just out of curiosity, did you solve it be deleting the database file?
Click to expand...
Click to collapse
I wish I could say, yes, but no. Long story short, I started over from a clean phone install. Unfortunately, (this part is off topic), I accidently upgraded to 11.0.4.4.IN11AA with an OTA after starting over (the version almost nobody has yet), didn't realize it, and patched a stock 11.0.2.2.IN11AA boot.img and flashed it to the boot partition. Magisk and root worked great, but WiFi and phone calls were broken. Now I'm stuck waiting to get the 11.0.4.4.IN11AA full package (Global/NA/US version of 11.0.4.4) to fix everything (by extracting the boot.img from a payload dumper).

So you mean that deleting the database file didn't work, or that you never tried it?

Sorry if I was unclear. I didn't try it. My phone was already in a state where I could not try it (and this no longer applied) before I saw this message. I am very grateful for the assistance/information.

I have the same problem. can you help me?

kas001 said:
I have the same problem. can you help me?
Click to expand...
Click to collapse
Have you already checked to see if this is the cause? https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access. It's definitely the best starting point.

Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.

SparJar said:
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
Click to expand...
Click to collapse
Yeah, I did forgot that I have changed magisk name to "settings" and magisk is working fine right now.

aleep123 said:
Yeah, I did forgot that I have changed magisk name to "settings" and magisk is working fine right now.
Click to expand...
Click to collapse
Can you please explain?

ivanov_16 said:
Can you please explain?
Click to expand...
Click to collapse
There's a setting in the Magisk app where you can rename it with a random package name, to hide it and make the app harder to detect. This will give it a generic Android icon and give it the same "Settings" (previously it would name the repackaged app "Manager").

OK I missed the prompt to grant access to the ADB shell. Where's the settings for all the applications permission grants? So that I can untick the "deny" for ADB shell. I've changed the setting from prompt to grant, and tried again. But the toast just says Shell denied superuser access.
Thanks.
--Chris
EDIT:
OK I just installed a terminal app and nuked
/data/adb/magisk/magisk.db
which allowed me to start the permission process over.
This sure seems like a brutal approach to grant/permission management. It also requires starting the whole process from scratch.

SparJar said:
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
Click to expand...
Click to collapse
You are a superstar!! I have been tearing my hair out for acouple of days now trying to work out why i could not reinstall magisk, this was exactly the solution to the problem i was facing, therefore i give you my gratitude.

I have the same issues after updating to v24.1 how can I Access to delete the duplicate apps of Magisk. It was naming to Settings.

After the 25206
Didgeridoohan said:
So you mean that deleting the database file didn't work, or that you never tried it?
Click to expand...
Click to collapse
I on the other hand tried it. Not sure if it works or not. After the 25206 to 25207 disaster, 25208 is finally normal except it can't hide itself anymore. Any solutions there? Many thanks. F Droid file explorer/Network Signal Guru also lost super user rights. Rootchecker now says it's not properly rooted

I tried deleting /data/adb/magisk/magisk.db with Termux but can't even access it as I get "permission denied" and am still seeing SuperUser and Modules greyed out. Tried sudo, was prompted to install 'tsu' package and it failed as it appears the host no longer exists