yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Are you now trying to remove Magisk root? (MagiskHide is just a cloaking feature).

Or do you mean trying to UnHide (restore) Magisk Manager / App to remove conflicts? (This is different from MagiskHide also.)

I'm guessing you mean the latter, but I'm confused by 3) '... flashed new boot.img'. Did you mean Magisk-patched boot image?

Still, sounds like this is your problem:

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

Nb. If by icon that has 'disappeared from screen' you mean hidden / renamed Magisk Manager and you can't locate it, go to Settings, Manage apps, and go through whole list till you remember assigned name / find it / delete it.

If this is not the problem, please describe it properly, and give Model / OS details, and Ramdisk / SAR / A/B status. PW
[Magisk] Danny94:
Thanks, yeah the problem is i need to go physically to my bank each time i wipe data and restoring data from titanium does not work.

I aswell tried to clone the app with island, did not work.

I gona change my bank anyway now, no sense messing around with those. Other people in comment section have reported they got problems aswell and werent rooted and my dad had to buy a new phone because the old one didnt worked. Im sure they lost already a lot customers because they lock people to this app which doesnt work properly.
[Magisk] pndwal:
Sure, but caching flags for detected 'root' (really means any 'modified environment') seems to be standard fare for bank apps even when no methods other than checking SafetyNet result (ie. Play Protect certification status - check PlayStore, Settings, About, Play Protect certification says 'Device is certified') are employed.

This means that when ANYTHING goes wrong, and a future bank app detects root, you will still need to be prepared to clear it's data to reset flags before any solution will work, and unless you do, you can't be sure if a fix works or not!

For those having root however, i's all part of the thrill of the chase using MagiskHide with security centric apps ... You will not always win!

John's been playing the game of Cat and Mouse for some time now. The mouse is still alive, but tiring fast... And we're mere fleas in the equation. 😁 PW
[Magisk] dlewando:
yea, 3) is confusing :) i tried both. removing modified magisk .img by installing stock boot.img, which removes root. and also flashing modified magisk boot.img which gives me root back for both apps. also magiskhide is working for two apps (security token generating apps). these were only ideas to get back to a running magisk app.

after installing magisk app, the flashed magisk .img is not recordnized in magisk app (n/a). also i can not find any magiskhide app in settings/manage_apps (i'm also not remembering the hidden name, but scrolling slowly through all apps, there's no app with random characters). my goal is to get magisk app running that i'm able to use root for more apps.

thx fo your fast help btw!

device: google pixel 4a 5g
[Magisk] pndwal:
Ah, that's exactly as expected, not confusing. But you had only said you flashed new boot.img and still had root!

My hunch is that you still have hidden Manager (I'm assuming issue started w/ move up from pre 22 series Magisk?) as all symptoms indicate this. Manager app will be what you named it, not random characters.

If not, aside from the known issue mentioned in my linked post, you could have this:

https://github.com/topjohnwu/Magisk/issues/4319

But you seem to have working SU... Have a look and compare symptoms anyway. Also possible you have a new edge case. PW
[Magisk] martyfender:
On both my Andrioid 6 and 9 devices, the hidden Magisk Manager is named Settings, with the generic Android icon, as I don't change its name when hiding it. In older versions of Magisk it was named Manager when hidden, I believe.
[Magisk] dlewando:
thx 4 the hint. there's a "settings" with generic android-icon. i disabled it, but still root is hidden. maybe on android 11 it's renamed different? i'm thinking about installing lineage over my pixel stock. this should remove all system modifications.
[Magisk] HippoMan:
I am having a similar problem with the Chase banking app. I tried running it in Shelter, but the app still manages to detect root. Even when running inside of Shelter, the app says the following when I try to access a number of features:

Magisk is not running in the shelter. And outside of the shelter, the Chase app is hidden in Magisk 23.0

Chase and some other banks are going beyond SafetyNet and other tests. Luckily, the Chase IT people are not very smart, and all of the features that I cannot access via the Chase Android app are available when I access my account via the Chase web site from my Android device. This renders all of their so-called "security" useless.

The following is what I did, and it might work for some other banks, as well:

* Install a browser besides the standard Android browser (I chose Dolphin)

* Configure it so that its user agent string is the same one as the one that is used by your desktop browser (not all Android browsers allow this)

* Also configure it so that the start page for that browser is that bank's normal web site

This allows me to log into my bank's web site without all the Android-root-related restrictions.

PS: I used my "Home app" (Nova, in my case) to set the icon of this browser app to be the Chase app's icon, and I changed the title of that app on the screen to "Chase Alternate".
[Magisk] J.Michael:
If you "disabled" it, then it wasn't Magisk: system apps have a "Disable" option, non-system apps have an "Uninstall" option. (I assume you went to "App info" from the app icon in the Apps drawer. Is there an entry in App info for "details"?)
[Magisk] ipdev:
Just checked on my Pixel 3aXL (Android 11)

Default name to Hide the Magisk app is Settings

Take a look at the app info. (package name)

com.android.settings is the device settings app.

In my case, ziqfexf.wfukfetecw is the hidden Magisk app.

Cheers. :cowboy:
[Magisk] pndwal:
Ah yes; nice way to make distinction!

App names are not random; they're what user sees generally.

APK names are generally logical names too; android, com.android.xxx, com.miui.xxx, vendor.qti.xxx

Magisk hidden app APK name IS random however; oor.xuuzw.xfa.j PW
[Magisk] olexiiy:
Hello.

The situation happened with my mi 9t.

Steps :

Updated crDroid official from 21.4.12 to 21.5.10.

Updated the firmware to 21.5.12

Magisk 22005 to 23001

Nikgapps to 21.5.14

Cleared the cache

Turned on the system, everything is ok.

I made an android patches, I don't use magisk modules.

Everything works well.

After a few hours, without reboots, without other manipulations, gpay broken.

I thought that I do mistake.

Installed clean via miui from fastboot. The result is the same.

I set up everything, it works. After a couple of hours, gpay brokes again, there is no certification, ctsProfile does not work.

There is another phone with crDroid 6.17

(Not k20 / mi9t), the software is the same. Magisk is the same. All OK.

Which way to fix?

Or are there any tips?
[Magisk] pndwal:
I'm assuming you have full SafetyNet pass and Device is Certified PlayProtect result (check PlayStore, Settings, About) once again, and have cleared data in GPay to wipe cached flags before setting up cards etc again, especially if you had MagiskHide off at all, Uncertified device PlayProtect result, or root / insecure environment was detected by GPay.

Also, have you "Set up a screen lock to use the Google Pay app" since updating OS? It's required by Google.

Data / card info is also cleared by Google when screenlock is removed, even without opening Google Pay!

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-84758885

Hope it helps. PW
[Magisk] olexiiy:
Now I have clean instaled rom.

Step:

Install Rom

Install Magisk 23001

Install Gapps

Turn on rom

First setup and Set up a screen lock with pin

Reboot phone

Open magisk and hide

Clean data for Google service and Play Market.

Reboot phone.

Everything worked, Gpay worked, SafetyNet passed.

After a few hours SafetyNet and Gpay failed.

With Gpay fails cetrification.

There are screenshots with actual status.

Also I can grab the log with adb.

Spoiler content hidden.
[Magisk] pndwal:
OK... Not sure why you hide root from PlayStore... Who does that? (Google Play Services only is default for GApps) Likely this is causing your issues.

www.twitter.com/topjohnwu/status/1039528958289760256 PW
[Magisk] olexiiy:
I changed MagiskHide.

Clean PlayMarket data.

Reboot phone....

and nothing changes.

Trying to fix this last 3 day.

Tricks and modules only repairs part of the functions.

There is no complex solution to the problem. Everything used to work out of the box.

And now dancing with a tambourine. No information on which side is causing the issues.

In other forums people write about the same problem.

Spoiler content hidden.
[Magisk] Didgeridoohan:
What about the unlocked bootloader? That'll likely need to be taken care of as well... Details:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Unlocked_bootloader_3
[Magisk] olexiiy:
Bootloader is unlocked.

I tried to certificate (data cleared). The id is registered, at play market is not certified.
[Magisk] Didgeridoohan:
And are you using Universal SafetyNet Fix to help hide the unlocked bootloader (see link in my previous post)?
[Magisk] olexiiy:
Yesterday, I tried MagiskHideProps , SafetyNetFix1.1.1, MagiskHideProps + SafetyNetFix1.1.1.

ctsProfile failed.
[Magisk] HippoMan:
I don't know if this is the same situation as your problem, but I also ran into GPay problems that were a bit similar. It would work for a while, but then, without doing anything on my device (i.e., just leaving it sitting in an idle state), GPay would stop working after some amount of time.

One thing which I know that happens is that Google periodically checks the state of devices to see if they are "secure", by Google's standards. If not, the device is flagged on Google's web site as being insecure.

As soon as my device showed up on Google's web site as being insecure, then GPay stopped working properly.

In my case, Google decided to deem my device as insecure because after setting a PIN lock and setting up GPay, I went back to a Swipe lock. My idea was to switch back to a PIN lock whenever I decide to use GPay, and then go back to Swipe when I am done with GPay. However, after a while, Google detected that I no longer had a PIN lock, even though the device was just sitting idle in Swipe mode, and at that point, my device showed up as being insecure on Google's web site, and GPay stopped working, even when I reinstated the PIN lock before restarting GPay.

There might be other things that Google checks for which would trigger their deeming the device as insecure with regard to GPay, in addition to simply having set Swipe lock. If so, perhaps this could be the cause of your GPay problem.
[Magisk] Didgeridoohan:
Before anyone freaks out, Google has given John the ok to keep working on Magisk.

Edit: hmm... John has deleted the tweet stating that he's got the green light from Google in regards to Magisk. Maybe bad news, maybe no news. We'll just have to wait and see...

Ref:

https://www.xda-developers.com/magisk-developer-topjohnwu-leaves-apple-joins-google/

https://twitter.com/i/web/status/1394307859815407619
[Magisk] Lord Sithek:
Hope they won't tighten the noose around his neck in time...
[Magisk] pndwal:
Cat wrests mouse from dog. Mouse excited to collaborate with cat... and nothing changes?

Interesting turn of events, but I'm sure there'll be implications (especially for MagiskHide)...

It's not as though the Cat hasn't missed it's opportunity before however. 😉

... But this:

PW
[Magisk] HippoMan:
Given Google's recent actions against a few employees whose actions outside of Google were not considered to be Google-positive, I'm a bit concerned about John ... and as a consequence, about Magisk, as well.

Let's hope and pray for the best for him.
[Magisk] XenonF-Dev:
Sorry for the late response, I finally got some time to tinker with the phone again, and this time everything went smoothly, luckily for me I guess :p (All detailed on an edit from my original post in the S60's Root guide thread).

Well, I did the 22.1 uninstall process by renaming Magisk22.1.apk to uninstall.zip and flashing it, first time it detected Magisk 22.1 installed and removed it (or at least the log said that). I also flashed it a second time and this time the log said that no version was installed, so I though it did successfully unroot it, although I can't completly confirm that.

I think I had, yeah, since I had some folders inside the modules folder when I was researching how to fix the bootloop, I renamed them if I remember correctly and still got the bootloop.

Indeed, since the Cat S60 for some odd reason doesn't support a Safe Mode key combination, I did what is described on Whan Hun Lo's blog entry about a Cat S60's bootloop and created the needed file using TWRP root terminal (exactly echo "1" > /data/property/persist.sys.safemode), but the bootloop was still there so not sure if it did work, also I never tried to do that again after executing Magisk 22.1 uninstall script.

As I commented on my edited post, all this was caused by installing M22.1 over M20.3 using Mapp22.1, since Mapp22.1 didn't support M20.3 (It had a popup warning I ignored when opening the app, about <20.4 versions beign unsupported by the app).

I downloaded Magisk20.4.zip, flashed it with TWRP, updated MM7.5.1 to Mapp22.1 and it detected M20.4. Next I updated M20.4 to M22.1 through the Mapp and worked flawlessly this time.

I hope this helps to clarify what happened, and also could let Github Issue #4219 be properly answered. So far I got Mapp to v23 and installed the SystemBrowser module without problems.

Sorry again for the late answer, and thanks again for all the support I got here :giggle:.
[Magisk] pndwal:
As you're using CRdroid custom ROM, you may need MagiskHide Props Config to spoof certified fingerprint if ROM doesn't already do this. You need to configure using a terminal emulator, or it does nothing!

You should ONLY use fingerprint function.

With MHPC using a terminal interface you can see what fingerprint ROM already applied. Try changing it any other, but best to use Xiaomi.

You'll need Universal SafetyNet Fix also, regardless of MHPC setting. PW
[Magisk] XenonF-Dev:
Edit: This was a double-post since somehow the post was still on the post menu and I wasn't able to see the post already posted (Maybe a forum's bug?).

Feel free to remove it (since I can't find the option myself, I'm afraid).

In case this can't be removed, I would comment about the news from the Magisk Dev on Joining the Android Security Team, as google could say he is using it's priviledged position and internal knowledge to overcome SafetyNet, which could end in MagiskHide demise, although I hope I'm wrong. Google already did nasty stuff, like what they did with the Stadia team.
[Magisk] pndwal:
His seems different... He's losing ctsProfile pass and device certification, not just card registration etc. 😛 PW
[Magisk] Didgeridoohan:
Since you do make an interesting comment regarding John's new job I won't remove the post... Instead I'll reply.

Since Google decided to activate hardware backed key attestation there's no longer anything Magisk can do to circumvent SafetyNet (on modern devices). John has even stated that he's not interested in that (and now that he's part of Android Security he definitely won't work on anything along those lines, even if he could). It is going to be interesting to see how things develop though...
[Magisk] pndwal:
I doubt there'll be anything further from colaborators on issue as it's now considered closed. 😬 PW
[Magisk] HippoMan:
I know that his is different, and I mentioned that. I also said that perhaps Google's ongoing checks for devices being "insecure" might also trigger other issues. The fact that the problem occurred after a period of time when nothing was being done on the device makes me wonder about whether this is another instance of Google periodically checking devices and sometimes changing their security profiles.
[Magisk] J.Michael:
Renaming a folder in /data/adb/modules is just changing the name of the corresponding module.

Renaming /data/adb/modules itself would eliminate all modules.

Putting a file named "disable" *in* a module folder disables that module.

Removing (or moving) all of the folders in /data/adb/modules would eliminate all modules.

In the most general case, the "installation" of a module could have made other changes to the system. "Removing" the module might run some "uninstall" script associated with the module.

@Didgeridoohan's treatise on Magisk modules recommends giving the module a chance to uninstall itself gracefully.
[Magisk] WillyRy:
Congrats, Bro!

Or should I say Broogle!
[Magisk] altwu:
does direct install work with magisk v23? i have a oneplus 7 pro and encountered a bootloop after direct installing v22 or v22.1. since then, i've been installing magisk by patching the boot image and flashing the patched boot image.
[Magisk] pndwal:
Depends... Stock? Custom ROM?

A few issues reported incl. OnePlus. Here's one seems to affect LOS 18.1:

https://github.com/topjohnwu/Magisk/issues/4213 PW
[Magisk] tesiz22:
In this message in 2018 it's been noted that Magisk is incompatible with Alcatel Onetouch Pixi 3 10" 8079 because of its boot.img. Why is this? Is there anything I can do or has there been anyhing done on the development side to make it compatible?

It has an MTK8127 SoC.

This has been mentioned in this Github issue, is it resolved now?
[Magisk] pndwal:
Not sure / don't know.

Likely. There have been a number of fixes for MTK, especially more recently, and I understand the basic issues are fixed, but MTK has been difficult and I believe there are still issues.

Why not try again? You can always create a new issue with proper logs and contribute to fix if still not working! 😋 PW
[Magisk] tesiz22:
On that note, say I flashed the boot.img patched by Magisk but it didn't work, would I be able to flash my stock boot.img over it or would I be forced to do a full system wipe except the bootloader and re-flash an entlre stock ROM?
[Magisk] pndwal:
Yes / no.

Reflash unpatched image is easiest / best way to recover from boot loop.

Nb. Do it the recommended way via PC / fastboot. No guarantees with TWRP, unless you are confident your TWRP is 100% compatible.

Nb. Magisk (mask) Installation does nothing other than flash a patched boot image (whether in boot or in recovery), so recovering / removing root is simple. And any Magisk App root settings, although not removed, are likewise disabled without root. PW
[Magisk] aleMarvel:
is the end... sigh...
[Magisk] HippoMan:
I share your concern and your hope. I think that now is a good time to fork the github Magisk repo, just in case.
[Magisk] 73sydney:
Congrats to John, some people just stand out from the crowd by their demonstration of knowledge, and he richly deserves the recognition

Im not going to make any comment about Magisk itself. We will just have to wait to see how things pan out.

Regardless, thanks John

p.s. At least he ain't working for Big Skivvy anymore :)
[Magisk] olexiiy:
Yes, I use crDroid 7.6

Yesterday, I found out

Spoiler content hidden.

This patch brokes ctsProfile and certificate (the last six months everything worked with the patch)

Now without patch works. I can't try previous version of rom.

crDroid's maintainer and LuckyPatcher ignore this issue.

I don't know, what is the reason(LP, ROM, Magisk, Google)
[Magisk] pndwal:
My 2 cents:

John's celebrating!

New job with the one phone OS builder that has always allowed modders to customise / root / contribute because of Android Open Source Project, Apache licencing, etc!

The shock and horror was palpable when John landed internship, then permanent position with this OS's main contender. Personally, I wondered 'Why didn't Google snap him up?' Now that it's happened, why be surprised? Or shocked? Or horrified?

As has already been mentioned, SafetyNet pass & continued use of proprietary apps from corporate players & devs who don't want these to run in a custom modded environment (usually, not always, for pretty obvious reasons), is really out of John's hands in any case.

I'm very surprised G has turned a blind eye for so long, and I've commented here on the damage done / effect on market share, of allowing major a competitor to prove to have, or even to be perceived as having a more secure, even impenetrable, platform. Clearly, that's why Samsung came up with Knox, and others have tried to implement similar security measures to align themselves with corporate players and their needs, cognisant of the tide of customers turning to A to fill this need.

In any case, it seems a switch will be flipped at some point when bad vendor Keystore implementations (OnePlus etc) etc are resolved, and Hardware Keystore Attestation rollout finalised. And G will do it, simply because they have a vested interest in stemming the tide.

John said right at the outset of HKA testing (March 2020) not only that it would be impossible (practically) to circumvent, but that he too had been surprised that G had taken so long to implement it.

www.twitter.com/topjohnwu/status/1237656703929180160

Well, they still haven't, but it's not anything John can control in any case... He already said "Let's face it. Fun is over guys"... 14 months later we're still having fun! ... But when the lights do go out, it won't be John flipping the switch.

... or maybe now they'll let him! 😁

Interestingly, John's now on Shawn Willden's team.

www.twitter.com/shawnwillden/status/1394457196021252098

I said previously that I believe Shawn when he says "The Android security team doesn't want to prevent the use of custom ROMs; we're actually quite supportive of that, and do a lot of work to ensure that remains possible".

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

I can't see G implementing any root prevention either, even if that were possible with AOSP. After all, custom development has been good for Google, root users included.

However, when considering the bottom line, their loyalties are necessarily torn, and they clearly need to strike a balance. Seems to me we've been spared till now while Google has postponed the inevitable HKA, but don't think we're going to be able to continue to have our cake and eat it too, John G, John A, or John Wu!

Anyway, WELL DONE JOHN! A well deserved break! 🎉 🎉 PW
[Magisk] romilspm:
I had the latest magisk. I tried to hide the app (renamed it to something else) and when I tried to restore the app, it can't. And the root is gone-- Said that "Magisk is installed to the external storage. Please move the app to the internal storage. I tried to flash magisk again and there is no change. My root is gone and I can't bring it back. I'd appreciate it if anyone can help me. Thank you.
[Magisk] J.Michael:
You have not said what your phone is, what versions of Magisk you have used, or how you installed Magisk.

The message about external storage sounds like Android talking about the Magisk Manager app. At that point I would have suggested uninstalling every copy of the Manager app you can find in your app drawer. Look closely, probably no more than one is called Magisk, but you must find and remove all of them.

What, exactly, did you do when you "tried to flash magisk again"?

What makes you say your root is gone? (Where do you look? What do you try to do? How does it fail?)
[Magisk] Stillhard:
S.A.D

- Image removed -
[Magisk] Didgeridoohan:
Just want to point out that sharing screenshots of a private conversation isn't cool. The damage is already done and it's out there, but let John himself be the one to break the news.
[Magisk] pndwal:
Still, sad to see the retraction.

Watching this space.

This from his new team leader;

www.twitter.com/shawnwillden/status/1394457196021252098

So, root, but no security circumvention I'm guessing... Mask (overlay), but no masking (spoofing)... (or no mask at all?)

Serious implications for MagiskHide.

Have cake, but can't eat it too... at least no cherry on top... 🙁 PW