yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 11 Lite 5G] Visionu:
Thanks for enlightening me, kindly drop me any links for Nokia forums about rooting and bls. Because am really need that knowledge. I can't forget say am totally fresh...... sorry.

Another thing which is not the same topic: if Nokia and everyone told me that my Nokia x10's bootloader can't be unlocked plus the device can't be rooted. Is it all false because there is some company called "MKOPA" this company provides these kind of phones on loan and Incase you run out of credit/payment expires the phone will automatically be locked by mkopa's app which is preinstalled in the device's software on start. Why am saying all of this is because I believe : If some unofficial company can modify the device's default software builds and rebuild it with their billing and auto lock software it means they are eventually able to unlock the bootloader because am sure there is no way they can install custom files if the device can't be unlocked.

Sorry for my poor English,am not good at it. And kindly help me with that info
[Xiaomi Mi 11 Lite 5G] zgfg:
OMG. What if you google for:

XDA Nokia X10

One of the first hits would be:

https://xdaforums.com/f/nokia-x10-x20.12215/

There, one of the first topics/threads on the list is named:

How do I unlock the bootloader for Nokia X10?

Frankly, I didn't read because I'm not interested about.. But it's about your phone, hence read, learn and post your further questions there
[Xiaomi Mi 11 Lite 5G] Visionu:
Surprisingly it's helpless. It say "the bl can't be unlocked" which returns to my question
[Xiaomi Mi 11 Lite 5G] zgfg:
Please, please, please, stop missusing/spamming our Xiaomi subforum with your out-of-topic Nokia. Someone may thing that BL cannot be unlocked on Xiaomi, what's not thuth

Use the Nokia threads for your Nokia comments, questions, etc

If you are newbie to the XDA forum, read the guides how to behave on the forum
[Xiaomi Mi 11 Lite 5G] TheDaysOfYore:
Ah, that clears it up a bit more for me. So I can still use it, just not install it. Good to know.
[Xiaomi Mi 11 Lite 5G] GPSSlovakia:
MIUI 14: How to root with Magisk ?
[Xiaomi Mi 11 Lite 5G] Aitra:
It still runs fine on the A12, but it takes a lot of work to de-encrypt the memory and turn off the read-only system.
[Xiaomi Mi 11 Lite 5G] Aitra:
I have rooted miui 14- a13 by pat boot.img from magisk app, but it is very difficult to de-encrypt in twrp and also very difficult to disable read-only system.
[Xiaomi Mi 11 Lite 5G] zgfg:
TWRP.me has released 3.7.0, supporting A12 (not yet A13) for some phones, Renoir being one of them

TWRP 3.7.0 Released

TWRP 3.7.0 is out now for most currently supported devices.

twrp.me

Download TWRP for renoir

Download TWRP Open Recovery for renoir

eu.dl.twrp.me
[Xiaomi Mi 11 Lite 5G] zgfg:
SAR (system as root) partitions are read-only on the file-system level, they cannot be made writable by rooting, that's why Magisk provides systemless rooting (it can only mount required changws at the time of booting and initializing Magisk - boot without Magisk and your system partitions will be back intact).

It's not new in A13 - it was already with A11 and A12.

You can have writable System only with some custom ROMs

Google drives the changes with new versions of Android, vendors must support them to be eligible to release the certified phones with the newest Android versions
[Xiaomi Mi 11 Lite 5G] Aitra:
I used to disable system memory read-only lock on a11, a12, miui13 by de-encrypting and resizing system memory with flashing systemrw_1.32.zip. But on miui14, no success yet.
[Xiaomi Mi 11 Lite 5G] tzaneff:
Greetings.

Aitra, Sir, really interesting about your success of resizing system in miui 14..., casue unfortunatelly, a system size is very small, remaining volume is 0, and no matter the system is rooted, nothing can be deleted, or changed in it...​

Best regards.
[Xiaomi Mi 11 Lite 5G] zgfg:
/vendor/etc/fstab.emmc

System file-system is defined as ro = Read Only

So called resizable partitions

Only OTA when it comes overwrites (and resizes - if needed) the partition

During the usage, nothing writes to the System hence there is no need to be left empty space (except for the remaining unused block space).

That's why it is not writeable - not even with root, because the System itself cannot write to the ro partition
[Xiaomi Mi 11 Lite 5G] tzaneff:
I see... Not good for me as user, who do not completely agreed with some apps, and other, etc. Thank you for the explai. But as notice - system as root, not read only, magisk modules affect it.

Best regards.
[Xiaomi Mi 11 Lite 5G] zgfg:
Magisk modules can make systemless changes

It means that Magisk mounts its changes on boot, when initializing modules

Eg, Magisk built-in Systemless hosts, for eg AdAway

AdAway then writes to:

/data/adb/modules/hosts/system/etc/hosts

and Magisk will mount it to:

/system/etc/hosts

You disable the module or boot without Magisk, and all the mounted changes are gone - safe for OTA and so
[Magisk] robuser007:
Any suggestions on how to get the latest itsme working (identity from gouvernance BE). Magisk was renamed and the app is added on the denylist.

For Keytrade bank I have to freeze magisk to get this app working.
[Magisk] eboelens:
Same problem
[Magisk] Timmmmaaahh!:
Hey all!

This has been brought up before here and I'm in the same boat as you guys: itsme is throwing "Rooted device detected" while KeyTrade, Payconiq etc. is working just fine. Please do provide technical details in order to speed up the process of solving this.

My setup:

Magisk 34b2f525 (24316), Zygisk: Yes, Ramdisk: Yes

Magisk App: 34b2f525 (24316) (31), hidden as 'MagicalUnicorn'

DenyList configured and hiding itsme but also Google Play services & Play Store

LSPosed Zygisk 1.8.3 (6552) - Parasitic manager (app isn't installed)

SudoHide is hiding 'Hide My Applist', 'MagicalUnicorn', 'SudoHide' & 'XPrivacyLua' from 'Android System', itsme, etc.

Hide My Applist V2.3.2 is basically doing more of the same

XPrivacyLua 1.30 enables 'Force stop automatically' on 'Use tracking' for itsme & Keytrade

Yet Applist Detector V1.3.2 still detects the following:

abnormal environment

XPrivacyLua (Suspicious)

libc file detection

org.lsposed.manager (Found)

syscall file detection

org.lsposed.manager (Found)

So I'm guessing itsme is tripping over LSPosed's parasitic manager and haven't found how to circumvent this. Where is it detecting this package name?
[Magisk] Timmmmaaahh!:
Also tried with Shamiko instead of enforcing DenyList but the result is the same. Which did bring me to another check tool: Momo. That's reporting "TEE broken" on my end. This post indicates that it may be resolved with some device spoofing so I should probably do further testing with the MagiskHide Props Config by the amazing @Didgeridoohan.

New Magisk released just today so now on 25001 Canary (now the same as v25.0?), which also didn't change anything.
[Magisk] xenorack:
The latest version of itsme 3.8.1 does not work for me. An older versions like itsme 3.6.4 works. I have downloaded this from https://www.apkmonk.com/app/be.bmid.itsme/#previous. There is a reddit thread where I got this information from but I don't know if sites like apkmonk are trusted, so I only tried if I could open the app. I didn't try to acctualy link any eid.

What I use:

Magisk 24.3 (24300); Zygisk: Yes,

Magisk app is hidden

DenyList: itsme, Google Play Store & Google Play Services

Modules:

Universal SafetyNet Fix v2.2.1 by kdrag0n

MagiskHide Props Config v6.1.2-v137 by Didgeridoohan

Universal SafetyNet Fix & MagiskHide Props Config is used to pass Googles SafetyNet Attestation API.
[Magisk] Timmmmaaahh!:
Right, forgot to mention Universal SafetyNet Fix, also using that. I'm down by one version: v2.2.0.

I would also be very careful with apk's from such websites related to applications like this one. The virustotal scan for itsme 3.6.4 showed up clean though but I wouldn't use it either. APKMirror is overall the most trusted alternative but no itsme there. Same for the Amazon app store. My last Titanium Backup of itsme dates from January (3.5.3) and restoring just the app does make it functional again! It flawlessly let me log into my eBox. If anyone wants it, I've attached the 3.5.3 version, which I've extracted via MiXplorer. The main goal remains tackling the new version's anti-root, of course.
[Magisk] pndwal:
Can't remember where I got this... Think someone asked... Think this passes:

View attachment 5633119

View attachment 5633117

Can't see it on Play Store... May be an old app...

View attachment 5633115

😛 PW
[Magisk] DukeNemesis:
Same here... Hoping somebody finds a way
[Magisk] dvhttn:
Thanks guys. I'll leave it until the weekend until I try in case I have to start from scratch again. I'll try *dirty* first to see what happens ... and let you know.
[Magisk] Eng.Raman:
Itsme detects zygisk ( ONLY ) , follow the few steps below to get it worked properly ( tested on the latest Itsme v3.8.1 ) :

1- Install Magisk alpha. Link

2- Keep Zygisk DISABLED & Enable MagiskHide.

3- Add Itsme to the Configure DenyList and DONE.

Note:

1. Don't use Magisk Canary ( because you can't configure Denylist if you keep Zygisk disabled )

2- No need to add Itsme as effective app in HMA or using ANY additional apps ( sudohide, XPrivacyLua, ...etc ).
[Magisk] Eng.Raman:
Solved in my Post here.
[Magisk] pndwal:
@Timmmmaaahh!

Yup, I see there's now 3.8.1... can someone link APK so I can try in Australia?...

No dice with any TJW Zygisk Magisk however?! ... Guess it would be nice for users to get a proper fix for current ItsMe w/ current official Magisk. 😜 .. PW
[Magisk] Eng.Raman:
Itsme v3.8.1 Link.
[Magisk] Timmmmaaahh!:
Thanks! But ehh..

View attachment 5633699

Debug?
[Magisk] Eng.Raman:
To get Itsme worked and similar apps that detect zygisk with TJW Magisk Canary/Stable or vvb2060 Magisk alpha ( if zygisk enabled ) you need to wait for a new release of shamiko or Denylist Unmount module with another proper/more hide mechanisms for zygisk. ;)
[Magisk] Eng.Raman:
No Magisk Debug.

Use the latest vvb2060 Magisk Alpha ( 25001 ). Link (y)
[Magisk] Timmmmaaahh!:
Oh right, the forked release. I haven't ventured outside official Magisk yet. Is that interchangeable? Say I flash this, can I easily return to official?
[Magisk] Eng.Raman:
Yes, Best to uninstall vvb2060 magisk alpha first then clean install TJW magisk canary/stable.

Don't dirty flashing each other ( Clean install recommended ).

Good Luck.
[Magisk] pndwal:
Many Thanks!
[Magisk] pndwal:
Confirmed I can't bypass detection for ItsMe 3.8.1 w/ current Magisk 25001.

My conclusion is similar...

However my Momo result for 25001 + latest USNF & Shamiko with Magisk App fully uninstalled (RN8T, Android 10 stock MIUI) shows:

View attachment 5633877

Please say how we know itsme is detecting Zygisk rather than something else... 👍 PW
[Magisk] rudi.timmer:
Payconiq give error here and dont start....
[Magisk] dewingerd:
https://xdaforums.com/t/itsme-not-working.4454285/post-88121701
[Magisk] rudi.timmer:
Yes sorry i know i will look for the other app for a solution
[Magisk] Timmmmaaahh!:
Detail your full setup here and perhaps we'll spot the culprit.
[Magisk] virol:
thx for your help,

must the original magisk 25 install first be uninstalled or can we simply "over-installing" the delta version with a direct install from the new installed delta app?
[Magisk] rudi.timmer:
THanks but i think i know what's wrong i have not fully install Magisk 25 first i just removed the app, i have read you need to rename the apk to unstaller.zip and then sideload it with twrp, i think thiw would be the problem that Payconiq still see the old Magisk. I will try that today and see what happens....
[Magisk] kewlsnake:
No problem. I did not remove the original Magisk install, I just did an "over-install" like you said.
[Magisk] virol:
thx kewlsnake,

what do you think: When at a later moment I will come back to the "original" magisk 25.2 can I revert this procure again by "over-installing" the original over the delta version?
[Magisk] i_machine:
Payconiq stopped working here as I fixed the problem for itsme ...

Setup:

Installed Magisk canary over delta 25.2

Enabled MagiskHide and hidden the app itself

Disabled Zygisk, Shamiko and Universal SafetyNet fix

MagiskHide setup:

Android Services Library

Android System Webview

Google Play Services for AR

Google Play Store

Google Play Services

Home

itsme

banking apps

MS Office apps

Payconiq

USB debugging disabled

Above steps fixed the itsme issue and banking apps + MS Office apps are also fine, but Payconiq stopped working (I think by disabling Zygisk, Shamiko and Universal Safetynet fix).

Does anyone have an idea?
[Magisk] Bubble-be:
I had previously detachted itsme from the store with the detach module in Magisk Delta. Even after I updated itsme and verified the version was 3.12, it still kept complaining it needed to be updated. I needed to clear the cache of itsme and even uninstalled the module to get rid of the message.
[Magisk] rudi.timmer:
Same on my frend phone indeed it fixed itsme but for some resion not Payconiq
[Magisk] virol:
like i can follow its either itsme that works with canary and not working anymore payconiq

or

payconiq works with the official magisk 25+ and shamiko with Zigisk but then itsme is not working........

found a new module: a portable magiskhide to use as module on the official magisk 25+ with this you can use magiskhide WITHOUT Zigisk enabled!!!!!!!!!

check it out:

Portable MagiskHide: https://github.com/HuskyDG/magiskhide/tree/v1.6

let us know that both itsme AND Payconic works
[Magisk] PalmerBE:
Hi,

General question.

Does anybody know/have have experience on whether or not Itsme, Payconic and bankapp's (KBC in my case) can work on a full degoogled phone ?

I mean, LineageOs-MicroG, Magisk...... but no Google services or account

Thanks
[Magisk] yoanndp:
Hello everyone,

I'm running Itsme 3.12 and it still detects root.

Here's my setup :

- Magisk Delta Canary (1c6d25f7-delta [25206])

- Zygisk disabled

- Bootloop protection enabled

- MagiskHide enable

- MagiskHide apps :

- Android Services Library

- Android System WebView

- Carrier Services

- Google Services Framework

- Google Play Services for AR

- Google Play Store

- Google Play Protect

- Google Play Services

- Custom apps (Itsme, banking apps, etc.)

- No Shamiko neither Universal Safetynet Fix

- More infos :

- Safetynet status is Failed due to CTS Profile Match

- My device is Google Pixel 7 running latest Android version (13, feb 2023 patch)

Do you guys have ideas of what could I do to fix Itsme ?
[Magisk] dewingerd:
Try Install safetynet fix 2.4.0 and see if you pass CTS Profile Match.

https://github.com/kdrag0n/safetynet-fix/releases/download/v2.4.0/safetynet-fix-v2.4.0.zip

Did you hide the magisk app ?
[Magisk] yoanndp:
Hello, thank you for your answer. I see you mention Safetynet Fix but, afaik, it uses Zygisk, right? I read on some posts that activating Zygisk could trigger root detection.

And yes, the Magisk application is hidden.

Edit : I tried the Riru version of SNF, but it still fails at CTS checks.
[Magisk] dewingerd:
Because you have android 13 I was wondering if with safetynet fix 2.4.0 + zygisk you would pass CTS check.

Also on my phone when I hide the magisk app, afterwards I have to manual uninstall the original magisk app. It doesn't uninstall istself on my phone
[Magisk] yoanndp:
I double-checked, but hiding the Magisk App did uninstall the original app
[Magisk] dewingerd:
You can also try SuList. Works also for me.

Is the opposite of hidelist.

-First unhide magisk app, and besides hidelist also activate enforece SuList.

- reboot

-in settings Configure SuList : only the apps you add to this list can see root !

-hide magisk app again.

-reboot

SuList is more battery friendly.
[Magisk] Timmmmaaahh!:
Just a little heads up in case anyone got their hands on Magisk ff648628-delta, dont use it. You may want to read this.
[Magisk] Pandoriaantje:
.....

Do you have/Did you try payconiq? Unfortunately being on a Samsung device, i run a (ambasadii) custom magisk patched kernel (else i would have to hold a key combination at every bootup, and that is prone to user error). So i'm stuck with original Magisk, unless I build my own Cruel kernel. So magisk delta is no option for me.

I do see some users still reporting other app detecting root, so we're not fully there, I believe. (I tend to be fun at parties, but I'm also a realist :p:LOL:)
[Magisk] Timmmmaaahh!:
Yes but haven't used it for any payments yet. I'm pretty sure the root check is in the startup so I wouldn't be able to see the camera waiting for a QR code if it would be detecting anything. Looking good 👍

That's some good advice you gave there... never get a Samsung! lol
[Magisk] virol:
@Timmmmaaahh! : you say that both itsme 3.12 and payconiq are working.

can you share us your magisk setup?

is it canary and witch version exactly, i supose no Zygist enabled and no modules active, just blacklisting the banking apps?

thx
[Magisk] Bunecarera:
My situation:

9 pro with Android 13 F74

Had magisk delta canary installed with Zygisk enabled, renamed magisk app, HideMyApp for itsme and payconiq, also magicHide. Itsme v 3.9.1

Worked like charm, but gave me a "update before 06.03 or we will kill a puppy" warning.

So.

Deleted cache and data from itsme. Uninstalled itsme. Rebooted

Disabled zygisk. Rebooted

Disabled Magisk delta. Rebooted.

Installed itsme 3.12 apk from apkio.com (had it detached from playstore via temefi so couldn't/didn't want to go Playstore route)

rebooted.

Opened Itsme, confirmed it worked.

Opened magisk delta again, needed to install original app again because renamed it. Rebooted.

Magisk delta was back, renamed and everything. Added itsme to hidelist. Same for Android Services Library, Android System Webview, Google Play Services for AR, Google Play Store, Google Play Services, Home

Rebooted.

Itsme works, Payconiq also works.
[Magisk] Timmmmaaahh!:
See screenshots attached. The amount of hidden apps/services is probably overkill but didn't feel like performing much trial & error. Google Services Framework doesn't appear to be selected but it is, it's just a visual bug. Canary + no Zygisk indeed and just a module for call recording and some for aesthetics. Plain and simple, really.
[Magisk] Pandoriaantje:
Its not just Samsung. A lot of devices are moving away from a boot ramdisk, so magisk has to be installed into the recovery. So one needs to hold whichever button combination that boots the device into recovery (or use magisk to reboot to recovery from within the OS). But this is so prone to user error. Like, when your battery ran out, and you charge it and forget to hold the buttons at boot. And once I had one of the security measures kick in, and reset my data.. so a custom kernel (with built in magisk) is the way to go, to always boot with magisk enabled on such devices, unfortunately.
[Magisk] virol:
thx for this fast reply,

I am on android 12 with the official magisk 25.2

can you explain why you use the non official magisk delta canary, is this version better or what reason to switch over ?

ones on canary , can you come back to official magisk when neccesary?

I suppose to switch over to canary from official, or vice versa its just doing a direct install by use of the magisk manager app starting from the "install" button?
[Magisk] dewingerd:
I use "Enforce SuList" under Magisk Hide settings. After rebooting you can configure SuList and only add those apps to the list that are allowed to see root. You don't have to worry about adding apps and services to the hidelist. With hidelist magisk is mounted for the whole system and you hide it by adding apps and services to the hidelist.

When using SuList magisk is only mounted to apps and modules that need it. So in my opinion it is much more clean and efficient.

You can always revert back to Hidelist by disabeling SuList and reboot.

(Magisk keeps the configurations of both lists)
[Magisk] yoanndp:
Hi everyone, while conducting my research I found that Itsme detects root because of Riru (in my case). I am looking for a way to hide Riru, but I can't find any solution without the help of Zygisk. Is there any way to hide Riru without Zygisk?
[Magisk] Bunecarera:
I'll try to answer:

Topjohnwu, the magisk dev, now works for Google. So, all the stuff he did with magisk (root, hidelist,...) kinda goes against his new employer.

So other people have started to take over with different accents to their vesion. Enter, Magisk Delta.

The Canary version is usually a beta on steroids. Some stuff works, some stuff doesn't. It is updated more frequently then beta or stable.

For the moment, a lot of stuff we want (hidelist for example) works very well on canary.

It all depends on your use case.

Magisk Delta doesn't have a stable at the moment. This would require a lot more testing...

You can always switch between Magisk and MagiskDelta.

To switch from Magisk to Delta, I always install the Delta apk from their github. And then, when rooted in Magisk, patch the boot img in Delta, reboot, boot the patched img, direct install in Delta.

Or, you can use Magisk Delta exactly the same way as Magisk...
[Magisk] virol:
@ Bunecarera,

thx for this explication of the delta magisk:

only one thing is not clear, how to swap from original to canary:

ok you must install ths delta apk from the github, but then i am lost (what then with the original magisk 25.2 apk, must you leave it or delete it from your phone?)

can you write a step by step what exactly to do.

thx
[Magisk] Bunecarera:
I just delete the Magisk app afterwards.

See also the XDA magisk delta forum.
[Magisk] Pandoriaantje:
I guess they tricked us. As of today 28th of february, i'm greeted with a error "Update Needed". Just when I needed Itsme to login to my Electricity provider's website... Great..
[Magisk] conspiracyBE:
Jup. As of monday 27/02 it no longer works.. While the warning told us it would work untill 06/03.
[Magisk] onimorza:
We should all start complaining in the itsme reviews on play store that our phones are not rooted and the app gives false positives and blocks our access for invalid reasons.

They'll never win this cat and mouse game, we'll always find workaround, it just gives us some headaches to do so. It's a waist of their and our time.

Even worse, by looking for workarounds we might open our phones even more making it maybe more vulnerable.

They should make their app foolproof and not try to foolproof the system around it.

They also try to secure an app on an already pretty secure android environment while most of us use it to open websites on our insecure Windows environments.
[Magisk] Pandoriaantje:
I've started going down another path, by looking into patching the app itself. see where the version check is happening (the strings are easily found), maybe even just changing versionCode/versionname in the AndroidManifest.xml. or maybe just patching the root checks... Not sure yet. I did find out APKTool is having a hard time with it though... not sure whats going on there.. 🧐

*edit:

From what i've gathered going through the code, it references com.gemalto.idp.mobile.core.root, which seems to be part of Ezio Mobile SDK So there might be some obfuscation going on also...
[Magisk] Pandoriaantje:
Just a headsup. I've enrolled to their beta programme, and for me the latest 4.0.0 does not show a 'rooted device' message with zygisk. I cant seems to reactivate through my banking app though. I receive an error when trying to sign.

i've attached a backup for the apk.

*edit

The error was caused by hide my app-list (had been experimenting with that). Removed the xposed module and succesfully activated the itsme beta throug my banking app woth official magisk.
[Magisk] omlet:
Same for me ! I was wanting to post here. This beta program is a holy present :D. I'm on latest Magisk Delta.
[Magisk] plekszy:
Let's hope that this will not only be so for the beta version, and that the release version doesn't re-introduce root check...