yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Conversation is all on this page, and I'd quoted member:

I was surprised MagiskDetector caches flags for at least some detection methods, and data needs clearing to reset results just like bank apps.

I thanked member for comment "MagiskDetector use a mechanism to keep the detection in data cache on boot", and commented that I'd confirmed that results for init.rc at least need clearing by clearing apps data.

I don't see how MiXplorer enters into this.

Also, now seems you think I use ES File Explorer. - I haven't for a year or so now, not only because of it's evident security issues, but also due to it's age / trailing compatibility.

Thanks for MiXplorer plug however: I've generally used Total Commander lately, but I'll give that a try. PW
[Magisk] centodue:
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 :D ).

So now no problem for a second "su" but SafetyNet fails and no rom update possible :(

​

​
[Magisk] guhvanoh:
You was replying to the wrong post...
[Magisk] HippoMan:
Yes. Thank you. The typo was in the message I posted, but no typo in the file name I created.

After clearing cache, MagiskDetector shows the same results as before, and the banking app still detects root.

And yes, MagiskDetector is listed in MagiskHide.
[Magisk] HippoMan:
Thank you. I have done all this, including disabling "Riru - Enhanced mode for Magisk Hide" (it was previously enabled). No change in item 2 detection.

Yes, I'll work on that issue separately.

In any case, I'm pretty sure that my banking app is doing more checking than Magisk is able to block. My "run the web-based version of my banking app from within my device" method still seems to be the most fruitful solution for me.
[Magisk] Captain_Throwback:
PoGO still works here, even though SafetyNet is blue.
[Magisk] andrew2432:
V7 is updated. It works on modules like xposed does. You download the bits you need and use them within the app. The old version is strictly root/se Linux mounting toggle. Magisk helps systemless root and supposed to work around safety net. I don't think V6 works on MM
[Magisk] mobileman88:
Safetynet is failing for me, so even if Pogo works, AP will most likely fail. Need a way to easily unroot and root back rather than hiding root as this cat and mouse game is getting a little too tiring
[Magisk] Captain_Throwback:
PoGO uses SafetyNet, just like AP. So if PoGO still works, so should AP.
[Magisk] alanmv567:
delete
[Magisk] ftarules:
Magisk v6 had toggle for the SELinux. Where is that right for Magisk v7? I don't see it. I only see check mark for Superuser.
[Magisk] Captain_Throwback:
Gone.
[Magisk] ataraxist:
see this: http://xdaforums.com/showpost.php?p=69120109&postcount=732
[Magisk] ftarules:
So it is now full time SELINUX permissive?
[Magisk] Didgeridoohan:
Magisk phh's 259. And I do believe that file based encryption isn't gonna be available for us non-Pixel plebs. :)

How about providing a log from the flash (recovery log)?
[Magisk] waylo:
Not the case for everyone. Many of us have fail/error on both safetynet checking apps.

It's quite inconsistent among users reporting in here so there must be some device/ROM dependency which is not easy to sniff out.
[Magisk] Rhoban:
No. You will have to find another way or go back to v6.
[Magisk] _Abel81:
v7 makes my Moto X (XT1095) on Android 6.0 throw error: "Fastboot Reason: Fall-through from normal boot mode".

Boot image (made in TWRP) is in attachment
[Magisk] teddy0209:
No, mine was enforcing by default... You can have another app to toggle that...
[Magisk] RonnYap:
Still work?

have exposed?
[Magisk] negroxxx:
It's 8:30 in Argentina and pogo works perferct.

Superdu2.78

Magisk v7

Suhide

Xposed installer (modulo snorlax)

Without gapps but migrog
[Magisk] alexpower:
[MENTION=7726078]negroxxx[/MENTION]

Stop spamming and cross posting

Gesendet von meinem HTC 10 mit Tapatalk
[Magisk] mobil11030:
I'm not sure r266 is completely blocked. I got blue SafetyNet screen last night, but PoGo still worked. Anyway, I flashed stock NBD90X images, re-rooted r266, no Magisk, no Xposed. As of this morning, I still have green SafetyNet, PoGo works and adding a card to AP works. I'll confirm with a purchase later on...
[Magisk] ghylander:
hi

i have 1 problem and 1 suggestion

the problem is that i can not see the option to unmount the root in the new 2.0 magisk manager app, which makes this root useless to me as i was using the unmount feature

i've looked everywhere inside the app and its menus

my suggestion is to add an option to just download the magisk updates zips, instead of automatically installing them

i have an lg g3 and when i updated magisk from v6 to v7 the phone rebooted itself and i got the boot certification error

i had to go into recovery and flash the bum zip, but i still got very scared

thanks!
[Magisk] Captain_Throwback:
Your problem isn't a problem. Magisk isn't a root app.
[Magisk] pndwal:
Well, my essentials include Busybox for Android NDK, Universal SafetyNet Fix, and, of course, this fix, Riru-MomoHider.

Of course, I'm using Alpha Magisk also, as mentioned.

Add this to MagiskHide list, (MagiskHide toggled on in settings)

Well yes... Mine is... But you can try without! 😛

Well, I haven't yet, an my bank app doesn't detect... But neither does MagiskDetector see this! (An oversight? ... ot perhaps it's just focussed on Isolated process detection).

So I can't say if necessary for your Westpac app... I'd say it may well be though.. all depends on extent to which they've reinvented 'Safetynet'! 😜

Well, with failure and no analysis, you simply don't know how many items are detected; could be one, could be all! If you still have a problem, plug as many root 'leaks' as you can! You can always turn them off again one by one to eliminate....

Why not?... I'll give it a go for kicks and report... PW
[Magisk] zgfg:
Oops, sorry, I was replying about ES FileExplorer/MiXplorer to another post/user (but quoted your post by mistake):
[Magisk] pndwal:
So 'system file modified by Magisk' is now the ONLY item detected for you?

And you're clearing MagiskDetector data between tests? PW
[Magisk] HippoMan:
Oh, init.rc modification is also detected. The others are not detected.

And yes, I keep clearing MagiskDetector data.
[Magisk] pndwal:
Just hid / renamed Alpha Magisk App.

Process works fine! PW
[Magisk] pndwal:
And you have empty files for ALL four options in MomoHider config folder?

PW
[Magisk] HippoMan:
Yes. I stated that above.
[Magisk] DiamondJohn:
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.
[Magisk] pndwal:
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
[Magisk] zgfg:
It was (and still is), Stable, Beta (not Alpha) and Canary as Magisk versions from TJW as it easily shows in Update Channel (screenshot)

And unfortunately, discussion about Magisk Detector and how to pass was started by guys having problems with certain e.g. banking apps that detect Magisk and refuse to use them (although basic checks like SafetyNet pass and MagiskHide is properly enabled), hence it applies to Magisk in the sense: how to use Magisk but also to properly hide it from apps, and what is missing in Magisk in that regard (e.g., su can be found in the path, modifications of init.rc are detectable)

Hence it's IMO disputable if that discussion belongs or not to this thread - if not, then certainly all similar discussions in the past about USNF, MHPC and similar were also not applicable to this thread, and similarly everything about OTA, TWRPs, etc, as well
[Magisk] Stillhard:
Glad to see you've sorted it out.

Recently i was involved with the development (a lot communications with canyie - the developer (reporting issues and send logs privately)). He's a real nice person as a developer.

I hope all his work can help us to overcome the missing pieces in Magisk.
[Magisk] 73sydney:
Its weird, i could get all items setup as you did and report in the Magisk Detector the same as you, but Westpac didnt work.

When i killed that and tried edXposed and XprivacyLUA, Westpac worked, but Samsung pay detected root

note: Its easy to tell when WestPac banking detects root, you lose fingerprint login as an option, AND most importantly the Digital Card option (so you can still use your debit/credit card while waiting for a new card to be sent out, which is kind important right now as of course im waiting on a new card after the last one connected to my account wreaked havoc on my Google Pay account because of Westpacs bugs)

Which circle of hell is this?

2 weeks ago, not a single issue...

Life was good.....

Update: i think i *may* have it fixed with both Samsung Pay and Google Pay/Westpac Bank App working. Ill test it for a few days....because last time i thought i had it with riru-unshared, it lasted 2 days :)

Im going to do a clean flash and recreate it and then leave it for 3 days...tonight i screwed it up trying everything so that its not a reliable test bed right now

It really seems like pot luck these days ...im not sure that execution time in startup isnt half the issue
[Magisk] pndwal:
Have to say that even with Alpha builds, not much has really changed.

Lately, more development has been done by others rather than John (which is why he commented on how open source is great, allowing him to be lazy). And @vvb2060 has been at top of list for a long time... So many commits authored by him, many tested first in his Alpha, but many (most?) being merged into John's builds.

Of the current 5 pull requests for example, 2 are his.

So his changes have been at the forefront; So many major innovations in John's builds have been his babies. Here is a sampling, just from this year:

MTK compatibility, single package delivery, 64bit support, sepolicy fixes, several isolated process fixes, fixes for UID, MicroG, process names, file based encryption, mount rules for Sammy, auto-close issues bot, reboot menu, multi-user and shared user id compatibility fixes, hidden apps, Chinese translation, offline restore app, unsupported environment checking, fix for apex path (a big one), permission fixes, module Installation fixes, Kotlin code cleanup, MagiskHide stopping fix, Rename App include uninstaller..........

Really, users here have been testing / discussing @vvb2060's innovations for a good while.

Existing Magisk is already very much @vvb2060's... And, of course, @diareuse's... And @osm0sis', ... And @topjohnwu's, and that of some 208 more contributors.

I'm sorry, but I hope from this you might agree that this isn't really 'new development', and is NOT 'sooooo different to the existing Magisk'... It's actually continuation of the same without a break!

Some of the same Devs already help @vvb2060. I hope the others (I'm sure they will) will continue to colaborate with him as they already were with John signing off commits.

But we've certainly lost a great team leader, and original innovator and visionary... for now. PW
[Magisk] J.Michael:
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?

Are you now running a newer version of the patched operating system that you originally described?

Is your original problem resolved? *Was* your original problem "Magisk complains that it detects another copy of 'su'"?
[Magisk] HippoMan:
Thank you. I'll try disabling modules to see how that works ... when I have some time.

For the moment, I'm kind of busy with two jobs and some issues with my cat needing surgery, so I probably won't get to that for a while. In the mean time, my web-based Android access to my banking app is serving me just fine.
[Magisk] 73sydney:
fwiw really strange things happening here

I flashed a clean ROM, and then flashed and

setup:

Magisk (alpha)

Riru

Riru-MomoHider

and set the config options of 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
[Magisk] zgfg:
Don't forget to wipe Data for Magisk Detector (and your banking app) between tests
[Magisk] 73sydney:
I did wipe data for Magisk Detector before every one of the what seemed like 50 reboots :)

I did not test any further than Magisk Detector at this point to see if anything weird was going on...and it was, variable numbers of su processes reported..often jumping between 1 and 4, when closing and reopening it between reboots..

fwiw: magisk lite tests ok, except for init.rc modified message
[Magisk] zgfg:
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
[Magisk] 73sydney:
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
[Magisk] DiamondJohn:
@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.(y)
[Magisk] pndwal:
No worries!

Just hope some info on recent Magisk development, and behind scenes gratuitous efforts of unseen developers aids ALL in understanding this group/community effort...

Of course it's only my opinion (but I think fairly evident) that Magisk has become more than just John's baby.

You may well be right that it merrits a new thread too... But, as you note, Dev with current builds available is without citizenship here...

John's an OP AWOL anyway, but hasn't formally put the baby up for adoption either!

Magisk, it does appear, is in a state of flux... But without @vvb2060, it might have been a state of limbo.

I see @vvb2060 as now in a caretaker role. He didn't ask for it either... We just found him holding the baby... And nurturing it.

So what to do?... It's perplexing, but very early days yet... And anything could happen!

I think time will tell, but unless the baby gets a new home, I'm happy to watch it grow here.

John will always be the father of Magisk... Hope he hasn't abandoned him... and that he can at least get visitation rights / contribute in future. 😐

You are very modest, but I know you've made countless valuable contributions / comments here. There's more than one Diamond John!

Please don't feel your opinions are less valuable / pertinent here either - you raised valid points, and in a forum expressly designated for such general discussion / bouncing ideas by John himself. I certainly didn't intend to dismiss them... You've swum in these waters much longer than me, after all!

Please remember this: If enough fish swim in circles, you get a whirlpool... Difficulty when you've swum to the middle is swimming out again....

The effort is the price you pay, but IMHO, it beats swimming alone. 😜 PW
[Magisk] pndwal:
Wow... 7.30 am! What a night, eh!

Chin up! When you wake up for lunch, things will be brighter. 😛 ... And make coffee... for two! 🙂 🐻 PW
[Magisk] dd805bb:
From what John has said on Reddit and behind the scenes, recanting on some made statements, he can not touch magisk at all not speak on it anymore. Since he does own the repositories for magisk so we could see them just disappear. He can't push an update which only he can do, so it's either fork it and go that route, which he knows all the ins and outs of magisk and now works for Google(2+2 says he will spilling the beans on the background to block it), I believe they have him on a gag because conflict of interest with magisk sidestepping their security system. You can't work for somewhere and have an ap they completely bypasses their OS without a amjor conflict of interest. Magisk, from John's standpoint and having to delete his tweet about keeping magisk going, I don't think an answer will ever be given from John unless he leaves Google. They did the smartest move I have ever seen them do.
[Magisk] centodue:
In the start I had original firmware updated with OTA (it is necessary just to insert the zip file in root of SD card and automatically is opened the window to update system) and I flashed the zip file with boot pached for Magisk (see picture attached) to have root.

In this condition I had :

1- the notification of another su present

2- safetynet check failed

3- Playstore --> Settings --> Device is not certified

So I tried to use Safety Fix 1.1.0 module in Magisk, but when the system restarted it remained blocked in startup with android logo.

So the only solution that I yesterday found was to flash the unit using .img rom on a microSD inserteing it on a microSD slot present directly on the main board.

But this ROM (already rooted) was older than my starting firmware.

This ROM with Magisk has not another copy of 'su' but safetynet check fails again and under Playstore 'device is not certified'.

So the problem is that Magisk Hide does not work for me.

So now the OTA update are not working (every times the updated stops to 62/66 % with an error message that for me is not clear).
[Magisk] pndwal:
mmm... But if John said anything on Reddit, it's news to me.

I am aware a private message was re-posted there, and John has since appealed to any concerned for privacy.

Fair to say there have been no updates since... And his pinned 'Latest Magisk' announcement is gone from top of his Twitter also. PW
[Magisk] dd805bb:
Here is what he said.
[Magisk] rodken:
@Didgeridoohan Is it preferable to fastboot flash the original boot file versus restoring the boot image via Magisk. Can't seem to wrap my head around as to why I keep receiving 'Error 402' each and every time a OTA comes through the pipes.

​
[Magisk] rodken:
I wish that it would be that easy to just grab a factory image for the OnePlus 8 5G UW and flash away.
[Magisk] rodken:
If all else fails, maybe we revert back to a forked repo of topjohnwu's Magisk similar to what ianmacd was doing a couple of years ago.
[Magisk] rodken:
This whole scenario makes this project seem bleak.
[Magisk] HippoMan:
Sadly, this doesn't surprise me about Google. Anyway, many of us have already forked the repo.
[Magisk] 73sydney:
Things already reverted to sh1te when i woke up today, my card was no longer working in Westpacs app...i should point out that at this point as my last one got so screwed up (and screwed up my google pay account), they cancelled it and are sending me a new one. Until then i only have access to my money via tap and pay when i can add it to Google Pay or Samsung Pay from their app (appears as a virtual card with its numbers, expiry and CVC. If it detects root it disabled this. Today i woke up to find that at least on the ROM i flashed, it had entered a new phase, where the virtual card was not showing numbers and that it couldnt, and i would need to call them....

Im hoping a flash to another ROM may improve things, because currently i have no way to access my money for day to day things :)

Cheers i may look into this once i have my banking sorted. I think ill move to a new bank...i only just swapped to this one (after my last ones ATM ate my card and they had closed branches during covid leaving me stranded with no money, and only able to get money by going into their city office at the height of covid), but their app is an a$$h0l3

Ive had nothing but trouble with my account since i opened it, had to reset my PIN 4 times, and it still doesnt work for withdrawing cash, and made more calls and visit to the bank than in my entire life in the last few months. Then the app starting being a pain in the bum...time to move on...
[Magisk] Didgeridoohan:
That's a partial screenshot of a much longer private conversation (a conversation the person sharing the screenshot no longer is a part of), not any kind of official information from John. You can't say anything definitive from that alone...

Whenever John has anything to share with the world on what the future of Magisk will be like (and he's thinking hard on that, I'm sure) he'll most likely do so on his Twitter.