yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Using either uninstall zip, or Uninstall Magisk from app won't remove (old) hidden Manager as mentioned, and I'm unsure if it will remove new (compatible) app when hidden either.

It will restore unpatched image as you say, and should remove Magisk data from /data/adb, although in practice, this sometimes needs cleaning manually. PW
[Magisk] pndwal:
Interesting... Just checked with speaker / NewPipe music, and steps doubled, volume changes uniformly! For me, seems to work as advertised! 😬 PW
[Magisk] mamba76:
Great, just me then..( I wonder if theres another build prop or config file elsewhere like /Vendor or Hardware Abstraction Layer. There must be another config setting of ro.config.media_vol_step=30 somewhere If anyone has any ideas/suggetsions I can try would be very greatful.

My device:

What device did you test volSteps on?

*Bump - where is audioservice.java ?
[Magisk] shengruoyu:
I have installed Magisk v22 correctly on my Mi 6 with AOSP Android 11. It worked fine for days. But suddenly all the modules didn't work, even though app showed that modules were installed. Root works fine now.
[Magisk] J.Michael:
There is some module with a name like Props. Do you have that installed?

[CC: @pndwal]
[Magisk] mamba76:
Na just magiskHide. I think I read somewhere that Lenovo or Mediatek devices in general can be more problematic than samsungs. So I believe this not to be anything with Magisk. I got a feeling its more complicated as havn't found anyone with this issue on this device yet. Its a clean install. I will be looking into the differences between a samsung and mediatek, specifically the software / HAL config files. (the deep end😨) Please tell me what device do you have this module working on? At least I can use that to compare. Thanks
[Magisk] J.Michael:
I don't use the module. I remember references to it, and thought it was needed to spoof readonly properties.
[Magisk] ipdev:
A little more than spoofing. ;)

[MODULE] MagiskHide Props Config - SafetyNet, prop edits, and more - v5.4.0

MHPC xda thread - Link

Cheers. :cowboy:
[Magisk] pndwal:
Xiaomi Redmi Note 8T

Not sure I have this on my device.

Like you, not sure what it is exactly either! 😐

https://xdaforums.com/t/what-exactly-is-audioservice-java.4253381/ PW
[Magisk] pndwal:
If you are meaning MHPC, I had it on Xiaomi MI Pad 4 because it's especially useful to spoof fingerprint of a certified device / model (stock) ROM on Chinese uncertified and many custom ROMs that don't integrate certified fingerprint (eg all official LOS, due to strict anti-spoofing etc policies) to pass ctsProfile; MI Pad 4 is a China (uncertified) stock ROM only device.

@Didgeridoohan (and helpers) are meticulous in keeping passing fingerprint list current, so it has become a very elegant solution for this, not to mention other prop customisation. 👍 PW
[Magisk] J.Michael:
My thought was that @mamba76 should install this MHPC module, maybe the reason he is not enjoying the same success you have had is that he is not able to change a readonly property associated with volume control without that module.
[Magisk] knipp21:
Best to flash unsu.zip

And please don't forget the echo commands.
[Magisk] Guitos30:
Ok. I'm gonna try it.

Unroot, systemless SuperSU and than suhide right?

---------- Post added at 09:02 PM ---------- Previous post was at 08:55 PM ----------

Where do I find the unsu zip?
[Magisk] Captain_Throwback:
For the record, that was here.
[Magisk] tabp0le:
Thanks. I did go back through and found that. Again, sorry about that.
[Magisk] knipp21:
The search feature in this thread. Sep27th or so...Someone dropped a link
[Magisk] Guitos30:
Thanks
[Magisk] Hyflex:
Issues:

Magisk manager 2.0 on my Nexus 10 crashes on loading the app plus I am also unable to get magisk working, there is no errors when flashing the zips (Magisk, phh, Xposed, viper4android but I am unable to get root even after installing you superuser app. It's a fresh 5.1.1 stock ROM from Google.

Any one know what's up and how do I fix it?
[Magisk] knipp21:
Someone smarter than me can chime in.. But I think the OP stated you needed android 6+

Edit.. That's for Suhide...

What's the error you're getting?
[Magisk] teddy0209:
What version of phh superuser did you flash?

Edit: try flashing just magisk then phh magisk 259, just install the other mods inside the manager
[Magisk] gudenau:
When you download a file you can activate the notification to open the file. There is no need to use a file manager. I tried ADB after the phone didn't like it.

Worked this time...
[Magisk] soder:
If nothing in /system is changed, and you are back to stock recovery, you should.

/Söder
[Magisk] KaMonsieur:
Tried. But it failed. Everything is stock. :confused:
[Magisk] soder:
Then someone else in here can help you with what might cause a problem.

I've never tried an OTA with Magisk myself since I use TWRP, and if I still need to change recovery with fastboot, I might as well flash the whole updated ROM when it becomes available.

/Söder
[Magisk] ashyx:
Surely one of the basic requirements of ANY gui driven OS is to have basic access to files? Personal or otherwise. For that a file manager is certainly required unless you like doing things the hard way?
[Magisk] soder:
I just wonder if someone that knows how it all works, can confirm if what is shown in the screenshot is correct? I pass SafetyNet and all that, but I still got problem with some apps that refuse to show protected vidoes, and I suspect they still can see I got a rooted phone.

I use SuperSU, suhide, Magisk and Xposed (SuperSU 2.78-SR1-systemless, suhide 0.54, Magisk v7, Xposed (systemless) 86.6.

What I think of is the two paths for Superuser binary, if that's correct for example?

Edit: And yes, SuperSU is installed systemless (in the SuperSU app the option about systemless is greyed out).

/Söder
[Magisk] grep_i:
This problem I did not encounter yet but I do not use many videos apps.

I seldom use YouTube and VEVO don't know if these qualifies.

Can you give an example of an app so I can test if your problem also exist in an non Magisk setup ?

This can also be kernel related but in this phase I'm not quite sure yet.

Please don't say latest versions just give version numbers to support your claim.

Supersu v2.78-SR1 (systemless [MENTION=631273]Chainfire[/MENTION] & CCMT)

Suhide v0.55 [MENTION=631273]Chainfire[/MENTION])

Elementalx-n5-6.23 (kernel [MENTION=4684315]flar2[/MENTION])

Xposed v86.1 (systemless [MENTION=2476451]romracer[/MENTION])
[Magisk] soder:
Yeah, you're right, I even missed there was a 0.55 of Suhide.

I use SuperSU, suhide, Magisk and Xposed (SuperSU 2.78-SR1-systemless, suhide 0.54, Magisk v7, Xposed (systemless) 86.6.

The apps I got problem with are two swedish apps, TV4 Play https://play.google.com/store/apps/details?id=se.tv4.tv4playtab and C More https://play.google.com/store/apps/details?id=se.cmore.bonnier.

They are owned by the same company and people with root got problem with them. Was talk about RootCloak back in the days but I never got it to work. Not even now with my setup.

Of course I reset data of the apps. Both apps need logins I think... At least C More need a subscription.

/Söder
[Magisk] KaMonsieur:
Thanks anyway!:)
[Magisk] foongwk:
Im using Note 3 with ported Aryamod full edge 7 features and did pass safety net fully now after i use Super SU to fully unroot. Please assist me step by step to install and run full Magisk on my set.

Previously did tried as per mentioned steps to install but fail either safety net not pass or having boot loops.
[Magisk] soder:
Said before, but can do it again.

Clean rom.

Flash SuperSU 2.78-SR1-systemless with TWRP 3.0.2.0

Boot up, and then back to recovery.

Flash Magisk v7 and Xposed (systemless) 86.6 (or install Xposed from Magisk Manager when booted up next time I guess)

Boot up. Then back again to recovery.

Flash suhide 0.55

I think this is the correct way. Someone else please correct me if it's not.

After this I've flashed newer suhide right on top over this setup (0.53, then 0.54, then 0.55).

/Söder
[Magisk] mamba76:
MagiskHide Props Config was the first and only module I installed on this freshly rooted device as I wanted to pass safetyNet checks. After this I applied the ro.config.media_vol_steps=30 mod manually to the /system/build.prop this is where I got the the wierd 30 steps issue (2 lots 0-15). So I removed the manual mod, rebooted back to normal. I then installed VolumeStepsExtender module via Magisk and it installed fine this time. Rebooted. Test the volume, the same issue has returned (0-15 steps x2). strangely this module achieved the same weird issue without adding anything to the build.prop that I initially changed.

My conclusion - Theres more than one way to produce the wierd volume symptoms - edit build.prop adding the ro.config.... line OR install VolumeStepsExtender (via Magisk) - result wierd volume!

So Im not convinced that changing anything on the Masgisk Reset Prop config will solve this.

I have however discovered, using android studio device explorer, a lot of interesting audio related config files in the /Vender folder including script files but I think the problem lies in one of the shared library files, .so files. To open these they need to be de-compiled thats as far as I got ATM. Will let you know if I find anything that fixes my problem.
[Magisk] pndwal:
But I don't run MHPC on my RN8T, the device on which I had success w/ that vol. steps module. And being a systemless mod, my understanding is that it should work regardless of read only system; I'm on stock MIUI, A10, and I understand that most stock ROMs are locked to read only due to new Shared Blocks (incl. Super partition devices) implementation.

---------------------------

ANNOUNCEMENT (Only for the Adventurous!):

It may be of interest to many 'Power Users' here that a mod has been developed that can 'Universally Mount System read write for Android 10+ ROM w/ SUPER or NO_SUPER'!

It does this by dumping existing super OR system / product / vendor partitions, extracting embedded read-only partitions, then flashing images back to device as read-write partition(s).

Description:

A script for all Android power users that wish to make their read-only Android 10+ system read-write-able again to remove bloatware and make more thorough customizations to their device.

https://xdaforums.com/t/script-android-10-universal-mount-system-read-write-super-no_super.4247311/

John Wu's initial comments on EXT4_FEATURE_RO_COMPAT_SHARED_BLOCKS, ext4 dedup filesystems:

https://twitter.com/i/web/status/1170404631865778177

---------------------------

Back to the subject: The problem re. MHPC is that simply installing does NOTHING without configuring prop changes (hence the name MHPC) thru terminal interface.

Some changes incl. preconfigured ones are quite safe (changing device fingerprint etc) but other 'manual' changes etc can have unexpected results / consequences, and be quite dangerous.

Also there are so many props affecting audio, even in build.prop alone (not only in Audio section (I have 10 there), but also in Bluetooth, HW, Media and Persistent (many here) sections, as well as a number of 'unknown' categories) that it takes much time and effort just to determine which does what... Good thought though. PW
[Magisk] pndwal:
I remember playing with build.prop settings etc (fluencetype, audio.fluence settings etc) to fix in-call and other audio issues on Huawei Y550. In the end it was a combination of modifying these settings and the rom Dev adding missing support in kernel that fixed audio issues, but I recall we also encountered strange problems like only 2/3 of volume slider affecting audio although working visually, etc.

All the best with the fraught science of Android audio engineering! 😃 💪 PW
[Magisk] loshabih:
My EmiratesNBD banking app detects root, attached logcat can anybody find how it detect it, only this app detects root

URL

http://m.uploadedit.com/busd/1617019179247.txt
[Magisk] ineedroot69:
just add Emirates NBD to MagiskHide
[Magisk] loshabih:
this one?

Emirates NBD - Apps on Google Play

Emirates NBD’s mobile banking application, convenient & useful banking services.

play.google.com
[Magisk] ineedroot69:
there are 9 emirates nbd version i only tested it on UAE and the root warning is gone
[Magisk] pndwal:
If above advice isn't enough, may need to clear apps data after hiding root.

Much more here also:

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot 🤠 PW
[Magisk] loshabih:
I've removed the app installed it , cleared data, but still same error
[Magisk] GilX:
-deleted-
[Magisk] ineedroot69:
it is detecting something not Magisk
[Magisk] Drake008:
I'am a bit overwheled with this program.

I installed it and started my banking app but still I get the "YOur device is rooted" message.

I have a lineage v 16 rom on my Galaxy Tab 4 (matisselte). Is it because the rom is unfortuanly prerooted or do I something wrong?
[Magisk] J.Michael:
Is this video showing that the banking app does not detect root after it has been added to Magisk's "Hide from" list?
[Magisk] J.Michael:
What is "this program"?

How "prerooted"?

Have you asked @matteo0026 ?
[Magisk] matteo0026:
Thanks for reporting me @J.Michael .

First of all, I really don't advice to install a banking app in Galaxy Tab 4, since it's an old device with an old kernel and without all security components that a modern device has. But, if it's the only choice, do these checks:

- Enable Magisk Hide and check the banking app in the list of Magisk Hide

- Check if device passes Safetynet and if device is certified (check it in settings of Play Store).

To precise your doubt, ROM isn't prerooted. Since some Android versions, by default, all custom ROMs don't provide su binaries.
[Magisk] ineedroot69:
yes i guess?? or did i accidentally upload a video of me singing "Rap God by Eminem" since i'm actually planning to join America's Got Talent ..
[Magisk] cris royal (Elec):
at least your sense of humor is intact! 😁 btw, this season?!...
[Magisk] pndwal:
Not sure you rebooted. Also, ensure you have full SafetyNet pass, and 'Device is certified' in Google PlayStore settings first.

In Magisk app Settings, toggle MagiskHide off, then on again, then make sure app is also toggled on in MagiskHide hide list after above steps, then reboot before clearing apps data.

Of course, this will only ensure MagiskHide is working properly with your app. As many bank apps also use other custom methods to detect insecure/modified environment (unlocked bootloader etc), it may not hide 'root' fully for your app, but other users seem to indicate that it does for them. (And it does for my bank app).

If your app is in fact using these additional detection methods, the wiki link I gave you covered many of these as well as additional steps you can take. PW
[Magisk] pndwal:
Perhaps this is by we are still waiting for new Canary despite a number of recent changes already committed:

PW
[Magisk] Drake008:
@

J.Michael​

I dont have these buttons like in the video. I mean the Hide button and the other ones in the video. I can install an image and thats it. But I tried the Lineage16 image and it gives me an error. Seems that this image is not meant there.

It is the S-ID BAnking App from Sparkasse. It s the program for Creditcards.

I do not know how it is prerooted
[Magisk] Didgeridoohan:
I can't say for sure, but it sounds like the apk installation when you flashed through recovery didn't work propely. That can happen for a number of reasons... Generally pretty easy to fix by uninstalling the app and installing it again manually.
[Magisk] Drake008:
Iam not sure if I installed MAgisk correct. I have a Galaxy S4 LTE

I opened the App and after that I patched the apropiate boot.img file from the lineage 16 zip I got. After that I booted into TWRP and switched to Imagemode. I selected the boot.img and let twrp cioy it to the boot partition. But there is still nothing working.
[Magisk] ineedroot69:
download root checker from play store
[Magisk] theintel:
My device running android 8.1 has a stock boot image size of 7.7MB. After patching it with Magisk, it becomes 8.1MB of size. But the boot partition only allows up to 8MB. So when I flash the patched boot image, the device fails to boot.

It worked previously when older Magisk patched the image within 8MB. But the boot image patched by the new version of Magisk always exceeds the 8MB limit.

How do I get around this issue? Thanks in advance for suggesting a solution.
[Magisk] Ota2501:
Anyone with galaxy a8 on mewest magisk got trough csc for safety net? Tried a lot of diferent fingerprints none worked
[Magisk] ineedroot69:
you need to install safetynet fix by kdragon prop config certify basicattestation while safetynet fix certify ctsprofile
[Magisk] Didgeridoohan:
That is not correct. Changing the fingerprint prop has nothing to do with basic integrity, but is necessary to pass CTS on custom ROMs (that doesn't already use a certified fingerprint) or other devices that haven't been Google certified.

The SafetyNet fix is necessary on devices that use hardware attestation, possibly in combination with changing the fingerprint prop (depending on your general setup, of course).

Be careful with posting statements about things you don't quite know how they work... That's how misconceptions are created (and there are many of those available around root and it's hiding, no need to add more).
[Magisk] ineedroot69:
sorry about that a correct device finger print and safetynet fix by kdragon is required to pass ctsprofile
[Magisk] Drake008:
Downloaded and tested. It says Root is not properly installed on this device. GT-I9505 Android version 9
[Magisk] Ota2501:
Thanks you guys, sucess on passing trough safety net.
[Magisk] pndwal:
If you are using Universal SafetyNet Fix and have issues on Samsung with biometrics etc, latest test version fixes many issues on SOME Sammy devices:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84693353

No guarantees for your older device, and don't bother unless encountering problems. PW
[Magisk] jasonmerc:
Is there a way to force Magisk to patch a boot image with the 32 bit su binary?

I'm trying to patch the boot image of the ZTE Blade A3 Prime, which is a bit of an oddball phone. Runs Android 10, with A/B partition layout, but 32 bit Android. I am so close to patching this thing's boot image up and getting it to work, the last thing standing in our way is that when we tried to run Magisk on our patched boot image it said not executable: 64 bit ELF for the su binary.

If there was a way to force it to use the 32 bit binary when patching that would be all I'd need to solve my issue
[Magisk] J.Michael:
Are you saying the Magisk app reports that Magisk is installed?
[Magisk] jasonmerc:
So according to my buddy (I don't have a Blade A3 Prime myself, I'm helping him root HIS remotely) it seems Magisk is "mostly" installed (I think?) but when he tries to open an adb shell and run "su" it gives the following error:

user@asus-ubuntu--lts:~$ adb shell

Z5157:/ $ su

/system/bin/sh: /sbin/su: not executable: 64-bit ELF file

He also said in a previous post about this when he checked Magisk if it was installed:

MTK Easy Su says "Super user permission granted, use the magisk manager to manage". So I go to Magisk and it shows:

Magisk -> [Folder with down arrow] Install

installed N/A -> A/B Yes

Ramdisk Yes -> SAR Yes

I'm assuming the error here is simply because it can't run a 64 bit binary, but if you have another solution feel free to let me know and I'll forward it to him to try
[Magisk] pndwal:
Saw that thread ( https://xdaforums.com/t/blade-a3-prime-visible.4128481/ ); not sure of answer to your question, but from scanning the info, seems users have no problem unlocking bootloader.

The 'mtk-su' tool your friends 'mtk-easy-su' is based on seems to be aimed at using an exploit to root without unlocking bootloader. Interestingly, original OP says:

Thread 'Amazing Temp Root for MediaTek ARMv8 [2020-08-24]' https://xdaforums.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ OP

His tutorial for "bootless root for Magisk 20+!" Is here:

https://xdaforums.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/post-82081703

A clue for you here:

Further:

The more recent Mtk-Easy-Su module repos / notes / links are here:

GitHub - JunioJsv/mtk-easy-su: Get bootless root access with few clicks.

Get bootless root access with few clicks. Contribute to JunioJsv/mtk-easy-su development by creating an account on GitHub.

github.com

I didn't read all the progress with this device, and I hope some of the above may be helpful / new information.

However, since bootloader is unlocked on this device and you seem to have boot image(s) (original ROM, or extracted emmc images?), I'm not sure using this security exploit for temporary / 'bootless' root is the best approach / needed.

Recent Magisk (21.3+) has a number of fixes for MTK SOC, and Canary builds have extra fixes that may help too.

I may have missed reasons for your unique approach, but please tell me what occurs if you simply unlock bootloader, Install Magisk app (Latest v22), patch boot.img and flash using PC / Fastboot? And can you try with latest Canary? PW
[Magisk] ineedroot69:
that's really small stock boot.img i'm android 8.1 too but my boot.img is 32mb
[Magisk] ineedroot69:
does the superuser request from magisk shows up if not then your provably don't have magisk properly installed
[Magisk] Tickle.:
Hello,

User for a long time of Magisk, I had the issue once from my bank app which told me that my (rooted of course) phone was no longer supported and that i was ask either to unroot it or reset it.. bla..bla... bla.

I fixed it using magisk hide in one click.

It's doing it again today. I've updated magisk (v22), busybox, rebooted my phone but it still doesn't succeed to hide the root properly.

Does anyone have an idea please ?

Sincerely
[Magisk] booneb50:
The Manager was not hidden when trying to update Magisk within the App, it failed. I uninstalled the Manager using the system uninstall. I verified all installed apps for any app that appeared to be a hidden Manager app, none found.

When I rebooted my tablet, I see a green Android app with the Magisk name, it asks if I want to connect to the internet to download and install the complete app. This comes back each time I uninstall and reboot.

I tried patching boot.img, it fails, I have tried a complete uninstall from within the App, it fails, I have tried to flash the uninstall.zip file with TWRP, it fails.

Just for grins, I reinstalled the Manager and hid it and named it. The only thing that I tried that worked was to patch the boot.img file. I didn't try to flash that file yet, I don't want to brick my tablet incase.
[Magisk] robbayani:
yess.. on every reboot sometimes magisk hide not working..

i dont know im installing magisk properly or not.. because i'm just rename to magisk.zip then flash via twrp(OrangeFox Recovery)..

not using patching boot.img or recovery.img..

but safetynet always working (im using Riru + EdXposed)..

usually using EdXposed high risk get safetynet failed..
[Magisk] Tickle.:
Yes indeed, after a few tries, it works fine again.

I had to reset ma bank app, just as if i just downloaded it and installed it. kinda weird...

I hope it will work until i buy my new phone, some weeks maybe a few months. this one is done.

RIP my old friend Xperia you'll be my last Sony phone ^^.
[Magisk] J.Michael:
Did you check to see if "Hide" is ON? Then turn it off, turn it back on, reboot, clear the cache of the bank app, run bank app?
[Magisk] J.Michael:
fumbled post