yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
If it wasn't exactly the same Xiaomi.eu version (ie, if you downgraded by mistake), you had to Format Data

Or maybe you somehow, while flashing, affected partitions that do not flash through Xiaomi.eu zip

In those cases you would now need to flash the stock through Mi Flash (but that would erase your Data).

If doing so, make sure you disable (by default it is enabled) the option in Mi Flash to relock your Bootloader

The good think with your old device (that was originally released with MIUI 11/A10) was that you could have:

- Magisk (patched to boot)

and

- fully working TWRP (flashed to Recovery, actually Xiaomi.eu requires TWRP for their installation and updates)

Hence you could had Nandroid backup through TWRP that would now help you to easily restore the previously working stage.

But unfortunately too late now☹️
[Magisk] Hallohannes123:
I didn't downgrade, my data is there...

I really don't understand at all why it isn't booting.

I have reinstalled my os and restored my boot image to the original what could possibly still be causing my device to bootloop?? I am so lost right now
[Magisk] zentis:
In case this helps anyone. I'm on a Samsung S20 ultra with android 12 and had an issue with HSBC Singapore detecting that the phone was rooted. I tried both using the magisk deny list and using shamiko. In both cases, hsbc singapore detected that my phone was rooted.

I then created a new user (I enabled multi user accounts by following this guide https://www.xda-developers.com/add-multi-user-support-android/)

With the new user, I could then use hsbc singapore with no issue.

One thing to note, magisk is setup with "Only owner has root access".

Having a separate user for banking apps is not super convenient but better than nothing :) Next I'll try to install island manually and see if that works.
[Magisk] Hallohannes123:
I have sort of given up now:

I gotta work early tomorrow (it's 0:16 here), I need my phone.

If you have any idea what I could try please tell me otherwise tell me if you don't and I will clean install my phones ROM.

Thank you for your help
[Magisk] dohanin:
Some users also reported that disabling (freezing) the magisk app prior to starting the hsbc app solved the problem. You may like to try this as well.
[Magisk] pndwal:
Lacking any complete rom (fastboot type) from EU mob, I'd be flashing firmware only (not ROM, stock firmware partitions only)... You don't need to check these match; assuming you flashed recovery ROM, just flash latest firmware and see if fixes issues (if with other partitions)...

Xiaomi Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com

Far too many adds now (annoying), but an otherwise excellent resource...

Read FAQs here:

XM Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com

Go to main page, scroll down, select your model, select Firmware (not ROM), select latest, download and flash...

XM Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com

If this doesn't fix boot, I'd reflash EU ROM (dirty) again after firmware. If still a problem, I understand flashing Vendor (xiaomifirmwareupdater.com links these from 3rd party) partitions (again seperated from ROM partitions) can work, but this is more fraught... Please research yourself... Again, may need ROM dirty flash afterwards...

Hope this helps keep data! 🙃 PW
[Magisk] pndwal:
My guess is that this has happened, but likely w/ Magisk flashing if it alters partitions other than boot.img, recovery.img on his device...

This should not be necessary with extracted Firmware or Vendor (includes Firmware) partition images available. Please see my post above.

👀 PW
[Magisk] pndwal:
Actually, by "Fastboot flashing images should do it" I meant his attempts to restore boot and recovery... Ordinarily this should work... Then, in event "Perhaps you used / enabled a special setting available for your device in Magisk (disable Verity, other)? ... Could be that other partitions were actually modified in this case, or if installed mods apart from Magisk" I suggested flashing "full ROM package"... Sorry if wasn't clear...

Thanks, so other (stock) partitions should be flashed seperately as per my last posts to keep data in this case. PW
[Magisk] pndwal:
... Just realised you said tried to flash "old patched boot/recovery.img files"...

Did you ever/later flash both unpatched boot.img and recovery.img from current EU ROM?... Cos that should/would most likely have sorted boot! ... Probably can still try. 🙃 PW

Edit: 🤦‍♂️ Oh, of course you would have done this now as long as you flashed all partitions available in current ROM... 😝
[Magisk] Prof_Shekhar:
No. All but one banking and financial apps are needed to be put on denylist but no enforce denylist option needed to be turned on for Shamiko to work.

Only the rogue banking app continues to keep crashing complaining the device not meeting minimum safety requirements to run this banking app.

As pointed out by @zgfg and others here, I am getting more than ever convinced that the Shamiko is working perfectly all right in hiding the root but it is somehow this rogue banking app is detecting Lineage OS as unsafe and refusing to work. Also, I don't think that this rogue app is detecting open BL as when I was running Canary Magisk root with open BL on stock firmware, this same app was running without any fuss.

And as far as I know, there isn't a workaround yet to spoof the OS for banking apps except using Magiskhide config module to pass the safety net, which I have already done and device has no issues with the Google.
[Magisk] ithehappy:
The iMobile app (by ICICI bank) is detecting root since their last update (13th March one) on Play. I have obviously put the app under Deny list but to no avail. Latest stable Magisk 24300 with Zygisk enabled, and kdragon's 2.2.1 USNF and no other modules installed. Device is a taimen and running on LOS 18.1.
[Magisk] pndwal:
Yup... Shamiko just won't work with it on!...

Yup, yup... But this?:

👍 PW
[Magisk] Prof_Shekhar:
Enforce denylist option was not required to be enabled before installing Shamiko. Only apps for which root needed to be hidden were required to be put on denylist. Once installed, Shamiko correctly detected the denylist status.
[Magisk] Prof_Shekhar:
@pndwal @zgfg

I have received an update for my Lineage OS 19.1. But before I go for its installation, needed to check with you if there are in special steps to be taken before going for this upgrade to ensure that my recovery (TWRP) and Magisk root remains intact.

I ask question as I had read an advisory from topjohnwu describing the procedure to install OS upgrade. But that was for the samsung stock firmware.

Do I have to follow the same steps with the Lineage OS upgrade or it has to be usual upgrade.
[Magisk] HippoMan:
I'm looking for suggestions. If this question is deemed to be OT, I'm glad to discuss this in private messages.

I'm thinking of buying a new Android device, and I'd like to purchase one for which it will be easiest and most straightforward to get rooted and to get working with Zygisk and related utilities, and with the fewest apps being blocked.

What's particulary important to me, besides simply root and and the hiding of modding and of root are the following ...

* I want to be able to run Gravity Box, which means LSPosed, TaiChi, or something similar.

* I want the rooting/modding/hiding-of-root-and-modding procedures to have as few complications as possible, and a high probability of being reliable as long as instructions are carefully followed.

* (Optional) a good chance of being able to run the Chase banking app. I can live without this, and I just consider it to be a "nice to have".

* (Optional) if these things can be accomplished more easily with a custom ROM, then I'm glad to use one, on whatever device(s) would be suitable.

I know that different people have had different levels of success on various devices. I'm just looking to at least get a sense of which device(s) might have a better likelihood of being usable with Zygisk and other related utilities for rooting, modding, and the hiding of root and modding, with the least likelihood of my being kicked down into a crazy rabbit hole.

Thank you in advance for any suggestions/recommendations.

PS: I'm not optimistic about this, but hope springs eternal!
[Magisk] pndwal:
This is confusing... Before I said:

You said:

and:

and screenshots showed Shamiko not working stating erroneously it is "since enforce denylist is enabled".

I'm just trying to ascertain what, or how you resolved this, which is why, when you finally reported Shamiko working, I asked:

You said:

🤔

Ok, so if it wasn't this, please say how you got it fixed!...

As I mentioned, I've already spoken with an LSPosed dev (re. Shamiko's erroneous message stating "denylist is enforced" when it wasn't) who is willing to diagnose this ... I just want to report accurately the solution!!... Or did you muddle screenshots and have denylist enforced all along??? ... I'm just guessing now. 😟 ... But you could clear this up... For the sake of posterity! 😐 PW
[Magisk] Prof_Shekhar:
I am sorry if my reples have caused any confusion.

As you can see, I had not only disabled the deny list but also disabled the HideMyAppList after installing the Shamiko module. Which caused all the banking modules to crash. Panicked, I re-enabled the enforce denylist and sent you the screenshot, which shows the denylist enabled status.

However later on I learnt that the Shamiko works in tandem with HideMyAppList to prevent the banking and financial apps from crashing. Only installing Shamiko module alone is not going to get any banking and financial apps working except Google pay.

In a nutshell, my final conclusion is that either I use enforce denylist in conjunction with HideMyAppList or Shamiko in conjunction with the HideMyAppList to successfully prevent majority of the banking and financial apps from crashing.

Ofcourse, none of the above combinations worked with SBI Card app.

Currently, I am running my device with Shamiko and HideMyAppList. Enforce denylist is off.

Coming back to the sequence in which I got the Shamiko installed running, I first disabled the enforce denylist, let the HideMyAppList configured as it was, rebooted the device, flashed the Shamiko, rebooted the device once again.

Let me know if you need any further clarification.
[Magisk] zgfg:
I told you to try but you didn't notice or neglected or what?

- Install TWRP and reinstall Xiaomi eu (it distributes only as zip for TWRP).

And DELETE through TWRP (google how to do if you don't know) only /data/adb folder.

That does not delete your files, apps, whatever.

It only deleted Magisk database, Magisk modules - this is in case some modules or so causing you the bootloop

But if that does not help, and since you didn't maintain Nandroid backups through TWRP, to restore now, then you can only:

- Format Data in TWRP (you will loose all your apps, files, settings, etc)

And if that does not help, you will need to use Mi Flash tool to reinstall the full stock firmware - in the prev answer I instructed you to pay attention that you don't relock Bootloader.

Then you can install Xiaomi.eu again

---

I have Mi 9T and I use Xiaomi.eu since Nov 2020. I went through 30 or more weekly and later stable updates.

Over the 2bd part of 2021 I played extensively with pre-v24 Magisk switching between Alpha, Custom, later Canary, back and forth (for sure went over 20 times through updating or switching Magisk).

And I never, ever bricked the phone

Hence you must have done something terribly wrong (as you said you don't know exactly what you did)

I absolutely cannot give you better advice than above

Btw, this is general Magisk audience here. Users with LG, Samsung, who knows.90+ % have never heard of Xiaomi.eu.

I think, it was not the best place to ask, since the problem how to unbrick your case is not generic to Magisk but about your model and Xiaomi.eu ROM
[Magisk] mrspeccy:
There is more you can do. Using MagiskHidePropsConf, you can change individual keys (variables) appearing in the output of the "prop" command. For example, there may be properties such as

ro.lineage.version=0.22-r-20220224165877-release-cheeseburger

ro.lineage.releasetype=dev

etc. (https://community.e.foundation/t/app-called-mitid-keeps-saying-my-device-is-rooted/38271/64)

There are examples of apps (see the linked thread above) that say "device rooted" if they encounter system properties including the string "lineage".

Concretely, if you have the key "ro.lineage.version" in your properties, try renaming it.
[Magisk] J.Michael:
"remains intact" is asking a bit much. If this "update" is OTA, it might be incremental. You cannot expect it to work unless you restore the device to the state the update provider is expecting. I am not saying "uninstall Magisk", I am saying you should completely reinstall the previous version of the system.

Even if the update is delivered as a complete, flashable, ROM, you should install it and confirm that it works before repeating the process of installing Magisk.

If TWRP is not part of the system ROM, you should confirm that the new system works before installing TWRP. Unless TWRP is a necessary part of the installation process for LOS, in which case you should not be worrying about the update interfering with TWRP.
[Magisk] Prof_Shekhar:
T

@J.Michael

Thanks mate for taking out your time to reply to my question. Appreciate it.

As the Lineage OS update received is an OTA update, I guess I ll have to be prepared for complete loss of Magisk root alongwith possibly lose TWRP recovery.

I have currently only downloaded the update but not going for its installation until the day when I have entire day to myself to reinstall the TWRP recovery and Magisk Root and be ready to fix all apps which may go rogue.
[Magisk] zentis:
I've spent a bit more time playing around this and got it to work without using the multi-user fix.

Your suggestion of freezing the magisk app set me on the right track, I installed HideMyAppList on LSPosed created a black list that hides Magisk, Titanium and HideMyAppList and set Enable All Hide Methods.

I then applied that blacklist to the HSBC Apps and restarted my phone (before that it said "Module Activated System service not running"

After this, HSBC no longer detected my phone as rooted.

Tip to test this, install AppList detector and make sure that everything passes. This will allow you to verify that hidemyapplist is working well.

HideMyAppList is a super useful module, unfortunately it seems that development has stopped. Luckily it's open source...
[Magisk] Prof_Shekhar:
Very interesting. Will try soon. Hope it works 👍🏻
[Magisk] zgfg:
Actually, if it is only about 'hiding' Magisk app, you can UNINSTALL Magisk APP (not the Magisk)

That is, from Settings, Apps, find Magisk app and uninstall

It WILL NOT affect your modules, root grants, DenyList, you name it - because uninstalling Magisk app (year ago it had more suitable name Magisk Manager) does not affect root, Magisk database (with all info about DenyList, root grants), modules, etc

Later, you just install again the Magisk app, it shows you DenyList, modules, everything - just as it had been 'hyberneted', ie, you did not loose anything

Btw, all that has been commented many times - nothing revolutionary new here

---

The strongest way to 'hide' Magisk APP is to uninstall it as above (I'm not talking about hiding Magisk/root), and that is also the easiest way (properly configuring HMA is almost a rocket science for some users)

HideMyAppList, freezing Magisk app or using 'Hide Magisk apps' from inside the Magisk app are weaker methods

Some banking apps still detect Magisk app even when you do Hide Magisk app.

Besides so many users have troubles when updating Magisk because they did Hide Magisk app and they don't do Restore Magisk app before upgrading

You can practically keep uninstalled Magisk app all the time, and you will temporarily Install only when:

- when you want to install/update/disable a module (you can even do all that from Fox Mmm, hence you don't need Magisk app for)

- when you want to grant root to some new app, change DenyList (although, even that can be done manually by editing magisk.db)

- when you see on the Forum that new Magisk version is deployed and you want to install (Direct update or patching)
[Magisk] J.Michael:
I'm confused: I thought OTA was "Over The Air", and indicated that the update was "streamed" and applied during transfer, and that there was no option to download first and apply at a later time. If you have downloaded a file that can be used to install LOS19 on a device that does not already have a version of LOS, I don't think that's an OTA update.
[Magisk] Prof_Shekhar:
I already have LOS 19.1 installed with Magisk.

I got a notification this morning to download an update for LOS 700 mb+. I have downloaded it but didn't install it because I wanted to make sure that I only install it after l know the correct steps to do so without losing my TWRP and Magisk Root.

Today, I read on Lineage OS forum on telegram that the latest version of LOS auto install can use TWRP to update itself without losing either TWRP or Magisk root .

I am still to find out how far it is true.
[Magisk] vandyman:
After reading the last few pages of this thread to get caught up.

I swear that I was reading a soap opera.

😋
[Magisk] zentis:
Yes, I did read about uninstalling the Magisk app but I just received my new phone, I know I'm going to regularly use the magisk app to change things, add zygisk modules (granted I have Fox Mmm for that), grant root or change the DenyList and so it would be a lot of hassle.

Since, I found a solution that worked for me using HideMyAppList, I figured writing about it would be helpful because I know I'm not the only one whose first reflex is to search HSBC magisk and see if someone had a solution.
[Magisk] zgfg:
Good that it works for you but if you read back in this thread you will find really a lot of posts, the guides, discussions, success stories about using HMA

It has been mentioned many times when talking about banking apps, Oprek detector, etc, etc
[Magisk] zentis:
You're right you did discuss it extensively on this thread. I originally read the first page on this thread, did a search for hsbc and magisk and saw people asking how to get it working and didn't see all your posts on HMA.
[Magisk] Shazilsonu:
Yeah. I have Done everything.

now I am Using Old version of Magisk. :(
[Magisk] g000n:
When I try to run safetynet attestation on the latest version of YASNAC

it says

" Requires Googe Play Services v13.0 or above"

even though my Google Play services is v22.09.20

Any help?

Lineageos 18.1

mindthegapps
[Magisk] dohanin:
Hi, just curious. Is disabling the magisk app doesn't work for your or you just want to save the trouble of disabling/enabling it? For me, I use Airfrozen to automate this process. I avoid using LSPosed and HMA as far as possible, otherwise I would need to hide one more thing from all the apps which might detect LSPosed/HMA.
[Magisk] m0han:
is this what you're referring to? https://github.com/hyongbai/AirFrozen/releases/tag/v1.2.8
[Magisk] dohanin:
i am using this version

AirFrozen~Disabler(ROOT) for Android - APK Download

Download AirFrozen~Disabler(ROOT) apk 1.6.2 for Android. App disabler

m.apkpure.com
[Magisk] m0han:
fyi: Fox's MMM is up to v0.4.1
[Magisk] asripath:
Is it similar to the freeze functionality available in sdmaid & 3C toolbox ?
[Magisk] m0han:
All on a sudden, Oprek Detector is flagging 'Custom Recovery Files', although there is no TWRP folder on my device (renamed to NandBaks, as earlier - all was good then). Cleared cache and data of Oprek Detector and rebooted. No go!
[Magisk] m0han:
package name looks the same. wonder why the app is not updated on github.
[Magisk] zgfg:
I actually use HMA for two other purposes, for detaching (hiding) YouTube and Android Auto from Playstore

Both for YT and AA I have to use their old versions and I must assure that Playstore never updates them (I need YT v16.29.39 bcs of Vanced root and AA v7.0.16 bcs of Screen2Auto that allows me to project all apps to the car infotainment)
[Magisk] zgfg:
Also using AirFrozen v1.6.2 but only for freezing apps that I rarely use (like Momo, Applist Detector, Oprek, YASNAC, etc)

Not for hiding something - because package names for frozen apps can be easily detected, hence freezing is not very effective method for hiding

Just run from Terminal

or via ADB:

and you will see package names for all the frozen apps - see screenshots
[Magisk] dohanin:
Understand your point. But freezing magisk app works for some banking apps like HSBC. Of course, the magisk app itself need to be repackaged to a random name first. So "pm list packages -d" shouldn't reveal the magisk app, although I have no idea how those apps able to detect the magisk app with random package name when not frozen.
[Magisk] zgfg:
I have TWRP.bak and Fox folders (I sometimes switch between TWRP, SHRP and OrangeFox) with the recent backups inside, and no problem with Oprek
[Magisk] zgfg:
Probably they check for totally garbage (random) package name (human could easily distinguish hidden/repackaged Magisk app package name from the other, "regular' package names, maybe they use some AI to scan for 'strange' package names)

Then, having a candidate or two they double-check the candidate(s) to find the repackaged Magisk app

And they (still) miss some step if you both repackage first and then freeze

Btw, there is a notorious warez app whose name (L...r)i s forbidden on XDA, I wonder if you repackage Magisk app by that app (it doesn't randomize but append a letter to the package name), would it similarly help for some banking apps for whom hiding/repackaging the Magisk app helps
[Magisk] m0han:
started happening only this morning, without me having done anything to trigger 'something', which is why i'm perturbed. things seem fine otherwise - safetynet passes, gpay works...
[Magisk] zgfg:
SafetyNet and GPay don't bother about TWRP folder, but what is your folder name (try to rename - for me, TWRP and SHRP happily use the folder named TWRP.bak and that also hides the folder from Oprek)
[Magisk] pndwal:
I think John's OTA guide is what he read...

Magisk (not TWRP) can be preserved following that, but only on A/B devices... His is not IIRC.

https://topjohnwu.github.io/Magisk/ota.html#devices-with-ab-partitions

Nb. As this was recently fixed, bold note at top of page no longer applies.

An older option exists (addon.d survival script) to preserve Magisk w/ compatible custom ROMs, but only if Magisk was initially installed from custom recovery.

https://github.com/topjohnwu/Magisk/issues/3820#issuecomment-779243423

TWRP is also preserved; I'm not sure if LOS Recovery is preserved, but it's likely as it was originally an LOS initiative.

I wrote some details recently here:

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

and @osm0sis responded to confirm that this may, unfortunately, be broken in recent builds:

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

@osm0sis, info in this Feb 7 bot-closed issue may be helpful; the user didn't persue it further...

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

Streamed is only for A/B OTAs...

OTAs can be "Full OTA Images" like these for nexus and pixel:

https://developers.google.com/android/ota

and can be downloaded and installed from stock recovery using

adb sideload ota_file.zip

LOS OTAs are "Full OTA Images" (always?), and and can come 'Over The Air'.

User can either Initiate the OTA download and install process from built-in updater tool; it will download the OTA update and boot into TWRP to automatically install. Or user can manually download, boot into recovery and flash the OTA .ZIP.

W/o working addon.d, full OTA LOS images (non delta) can be flashed without restoring original images, but mods including Magisk and TWRP will need to be reinstalled.

🤠 PW
[Magisk] m0han:
...renamed to NandBaks, as earlier - all was good then...