And you have empty files for ALL four options in MomoHider config folder?
Just because development stops on any artifact, does noit mean the thread should be closed. Just think of an app that development may end on, but its use continues.This thread was General, and it included Stable, Beta and Canary versions - all three were maintained by TJW.
Now, when he started to work for Google, it is unclear when and from whom can we expect the new release(s)
If, then maybe from wb2060, and based on his Alpha version (upstream commits to Canary) - in the past he also provided certain important fixes and some of them were also available for pre-testing from his Github (I think, it was also his Alpha), before they would be incorporated to TJW"s Canary
Maybe this thread becomes obsolete in the future, frozen for TJW Magisk up to v23, who knows...
Magisk Detector discussion is about the general issues, certain banking apps that detect the Magisk. Magisk Lite is maybe in that direction (if wb2060 ever decides to release some kind of 'official' release)
Unfortunately, TJW long ago distracted himself from XDA and wb2060 was never a member here
Ok, sorry... so seems mileage varies per device...
It was (and still is), Stable, Beta (not Alpha) and Canary as Magisk versions from TJW as it easily shows in Update Channel (screenshot)Where I was going, is that this new development ios sooooo different to the existing Magisk (inc alpha, canary and stable Magisk), I know I personally find it more time consuming to ignore the posts which have nothing to do with the existing Magisk. I see it kind of like starting a new thread for a different android version (eg A10 to A11) even though its the same dev. I think people who are looking at the exiusting Magisk could come here and those looking for the future (ie beyond the existing canary Magisk) culd be better served on a different thread. It gets condusing for simple folk like me to have to read few paragraphs to ensure there ois nothing pertinent or appli9cable to the existing Magisk.
Glad to see you've sorted it out.And many thanks for suggesting this module!
I think MagiskHide is sorted, at least for my Xiaomi device (Stock RN8T, Alpha Magisk) :
View attachment 5328287
A bit regarding configuration seems to be lost in translation on its GitHub, so did a little googling.
- Install riru_momohider module
- Disable 'Riru - Enhanced mode for Magisk Hide', riru-unhide module (if have it)
- create an empty file named for each option used (I have all enabled), and place these in existing
/data/adb/modules/riru_momohider/config folder (no extension, mine have rw-rw-rw- permission)
[Options: isolated, setns, app_zygote_magic, initrc]
- MagiskDetector in MagiskHide list
- Clear MagiskDetector data
Nb. Only MagiskDetector items 1 & 5 (as per SS above) were being detected before this.
@HippoMan, I'm interested if this solution will solve item 2 detection for you, but guessing you may need to resolve this separately.
Also interested to hear if, with each MagiskDetector item undetected, anyone with Bank App detecting root has success with these... or it there are unlisted methods extant.
Hope it helps! PW
Have to say that even with Alpha builds, not much has really changed.Just because development stops on any artifact, does noit mean the thread should be closed. Just think of an app that development may end on, but its use continues.
Where I was going, is that this new development ios sooooo different to the existing Magisk (inc alpha, canary and stable Magisk), I know I personally find it more time consuming to ignore the posts which have nothing to do with the existing Magisk. I see it kind of like starting a new thread for a different android version (eg A10 to A11) even though its the same dev. I think people who are looking at the exiusting Magisk could come here and those looking for the future (ie beyond the existing canary Magisk) culd be better served on a different thread. It gets condusing for simple folk like me to have to read few paragraphs to ensure there ois nothing pertinent or appli9cable to the existing Magisk. One of the real problems is who will start the threaad considering the actual dev is not present on XDA.
I am confused: Are you trying to accept an Over-The-Air update? Or are you installing a file which is on an SD-card?I Have a original firmware downloaded by a user that created the pached_magisk_boot.zip file too.
This 2 files (original firmware and pached_boot) can be update in automatic way via OTA when USB card is detected.
I tried yesterday to solve using SafetyNet Fix 1.1.0 but head unit remained totally blocked during restart with logo of android.
No OTA update was again possible!
The only solution I find was to insert directly on a microSD slot present on main board disassembling the hardware a microSD with "Android 8.1 Update with Root" in .img format using PhoenixCard tool.
The update was automatic when system was power up, then I removed microSD and Android restarted with Magisk to update.
SafetyNet check fails again but I have not indication of another "su" command present when I open Magisk.
The release uploaded was very old (terrible interface available) So I tried to update via OTA but now I don't know why but it stops with this indication: "no find app file, update falure!" (chinese has good translation ).
So now no problem for a second "su" but SafetyNet fails and no rom update possible
Thank you. I'll try disabling modules to see how that works ... when I have some time.Ok, sorry... so seems mileage varies per device...
I had read it was particularly difficult to hide isolated processes on Xiaomi, so I was chuffed to have all MagiskDetector items undetected...
Just thinking on 'system file(s) are modified by Magisk module', I'm now thinking that means a module may be responsible...
I'm not certain how a module may do this, bit I am aware that if modules are installed via custom recovery (some can work this way) they can / often do actually alter the system partition...
So I'm thinking it may be worth 1) Disabling modules to test, and 2) if you think system mods may have been done, consider how to reverse these (by proper custom recovery uninstall, or by flashing system image?).
Of course, I'm just thinking out loud in case it helps... I may be on the wrong tangent here completely...
Any other ideas on what accounts for 'system file(s) are modified by Magisk module' detected? anyone? PW
Don't forget to wipe Data for Magisk Detector (and your banking app) between testsfwiw really strange things happening here
I flashed a clean ROM, and then flashed and
and set the config options fofo Momo as before
All tests in Magisk Detector came back perfect
then i added my usual modules...fonts, v4a etc
and tested again
suddenly the lower 3 tests in Magisk Detector returned negative results.
whats really weird was that toggling the modules off one by one (until they were all toggled off) did not return the results to their former states.... i saw between 1 and 4 su processes in Magisk Detector...weird
currently removing modules and testing as i go...
all this just to use my own money......whoever is in charge of the root hatred at banks needs to be shot....its my device, i bought it and i have no interest in using your money, just mine, let me use my damn device and money as i see fit...
Last update before i crash for some sleep: i removed all modules back to the Riru and Riru-Momohider, and its still banging on about running su processes and selinux
I had the same result with Lite
I had the same result with Lite
Did you try to install some nodules to Lite?
E.g., can you get MHPC running - it installs for me but terminal complains that props command is unknown.
To the other side, pure REPLACE based module(s) work fine.
Also, does it crash to you when you first time upon the installation of Lite to /data/adb by MiXploree - sounds strange but it happe!ed to me twice
No worries!@zgfg & @pndwal I TOTALLY understand I am only one very small fish in this ocean, and for the most part I swim alone in ever decreasing circles in my little personal puddle. I am not that active in this thread and have an even lower level on contribution. It was simply a suggestion and completely understand that everyone's opinion on any topic of Magisk discussion in this thread, is more pertinent than mine. It was really just a suggestion from someone who's opinion is not very important. Dont fret about it or waste your time explaining/replying too much, I would of accepted a simple"NO", but also understand it might of looked too dismissive.
Wow... 7.30 am! What a night, eh!there is no access via terminal
i installed my fave module, debloat, but of course cant access it...they were serious about the lite part
As for the install of lite...i installed the apk and patched a boot img, had no errors
v4a/vanced youtube doesnt work either, now i really want to die
going to bed finally, in disgust
AFAICS it does, at least for now.
From the LOS install zip file.Need quick help with the installation instructions https://topjohnwu.github.io/Magisk/install.html
Under "Patching Images" it says I need the boot.img (cause my OP 5T has RAM disk), but where can I download it?
Thanks in advance
Edit: I'm running lineage OS with microG
Good to know, thxFor those running vvb2060's alpha builds.
You should be able to install any of the alpha builds over each other.
The versionName is changing GitShortHead-alpha.
The versionCode is remaining 23001.
The versionCode is what triggers the upgrade/downgrade install.
PackageManager only see that you are re-installing version 23001.
With that being said, you might run into a problem with magisk.db that was generated by an older/newer build.
There was a very recent commit about this. (Currently the last commit on John's repo.)Magisk - GitHub - commit - f7c0e40Also the last commit in vvb2060's repo currently.
You might have an issues repacking a Magisk boot image.
For testing purposes you should always use your ROM's stock boot image.
Yes testing the updating logic is important but, you need a base line to compare.A clean install may fail when an update succeeds and vice versa.
Hm, funny things happening. I was thinking this is upgrade of HW attestation, but it is DOWNGRADE actually.
Yep, I have sent a Pull Request with the fix like an hour after v2.1.0 was released.Removed the @Displax safety net mod fix and applied the latest USNF 2.1.0 from @kdrag0n.
Attestation is passed and device is compliant in company portal too with my original device name 1+8 Pro and not Pixel.
This is done over the latest Alpha Magisk.
Update: My In-display fingerprint hardware is not working anymore, I think the fix is already committed. Hopefully it will be resolved in the next version.