Looking after that I just get photo editors.
You can find the link further above - it was erroneously marked as spam before, but has been restored now.
1 Like
@mrspeccy I have been using that tool and it is not helping me, but after some differents try
I have been able to use the tool properly now.
After I have sideload the new.zip in the phone, I install aurora, I install mitid and the phone is still founded like rooted phone.
I have just change the build.prop in system. Is that enough , or is something else that has to be changed?
Then you will probably need to install Magisk on top of it to hide the unlocked bootloader.
And for that I have to install the app and then the module hide?
Can confirm that MitID will run on Lineage 18.1 after the following:
Install Magisk (I got the 24.3 version) plus the following Magisk modules: MagiskHide Props Config, Universal Safetynet Fix (reboot every time asked to - which is a lot of times)
In Magisk settings enable Zygisk and Enforce DenyList
In Configure DenyList select all Google play related services .
Install MitID app from Play store (don’t open it yet - if you do you must clear the apps cache and storage - under settings and apps)
Add MitId to Magisk DenyList
Edit the file build.prop (I use the app BuildPropEditor from google play)
change the following strings "dev-keys"or “test-keys” to “release-keys”, “userdebug” to “user” and “lineage” to something else fx linage
save and reboot and open the MitId app.
Oddly enough it appears the developers specifically chose to target lineage. First time I missed one instance of lineage in build.props and it still would not run. Seems they are more comfortable with your phone being controlled by some chinese or US company than from the user himself. MitId even will not run after the phone passes safety net tests and google pay works if it finds just one string that says lineage. Really odd priorities if you ask me, and rather amateurish in implementation.
Wish I could just continue with NemID, I am not exactly impressed with MitId or the competence of the developers.
Anyway here you go. Maybe not all these steps are needed, (hopefully someone will test and we can reduce to minimum) but if done it does run.
1 Like
I will try later with magisk. In my case I have dev-keys changed to release-keys. Should I write then user? And for example where in the build is write dev- , should I change it also for stable or release?
thanks for your info.
No you are correct dev-keys to release-keys was what it should have said. It was me who messed up my own notes. I have corrected it now.
So much for writing guides whille being in a meeting at work 
And I forgot to give great thanks to mrspeccy for finding all these things
1 Like
I have got these lines
ro.build.user=root
ro.modversion=0.22-r-20220224165877-dev-cheeseburger
do they need to be change root for something else, and dev-cheeseburger for another thing?
Firts, thanks for your time.
I might say that it has not work for me yet.
I am gonna write here my build.prop:
begin common build properties
autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Thu Feb 24 21:31:37 UTC 2022
ro.system.build.date.utc=1645738297
ro.system.build.fingerprint=OnePlus/OnePlus5/OnePlus5:10/QKQ1.191014.012/2010292059:user/release-keys
ro.system.build.id=RQ3A.211001.001
ro.system.build.tags=release-keys
ro.system.build.type=user
ro.system.build.version.incremental=eng.root.20220224.213248
ro.system.build.version.release=11
ro.system.build.version.release_or_codename=11
ro.system.build.version.sdk=30
ro.product.system.brand=OnePlus
ro.product.system.device=OnePlus5
ro.product.system.manufacturer=OnePlus
ro.product.system.model=ONEPLUS A5000
ro.product.system.name=OnePlus5end common build properties
begin build properties
autogenerated by buildinfo.sh
ro.build.id=RQ3A.211001.001
ro.build.display.id=lineige_cheeseburger-user 11 RQ3A.211001.001 eng.root.20220224.213248 release-keys
ro.build.version.incremental=eng.root.20220224.213248
ro.build.version.sdk=30
ro.build.version.preview_sdk=0
ro.build.version.preview_sdk_fingerprint=REL
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=11
ro.build.version.release_or_codename=11
ro.build.version.security_patch=2022-01-05
ro.eos.version.security_patch=
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=Thu Feb 24 21:31:37 UTC 2022
ro.build.date.utc=1645738297
ro.build.type=user
ro.build.user=root
ro.build.host=runner-j3uhvwmz-project-53-concurrent-0
ro.build.tags=release-keys
ro.build.flavor=lineige_cheeseburger-userro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.locale=en-US
ro.wifi.channels=ro.build.product is obsolete; use ro.product.device
ro.build.product=cheeseburger
Do not try to parse description or thumbprint
ro.build.description=OnePlus5-user 10 QKQ1.191014.012 2010292059 release-keys
ro.lineige.device=cheeseburgerend build properties
from device/oneplus/msm8998-common/system.prop
Audio
af.fast_track_multiplier=1
audio.deep_buffer.media=true
audio.offload.min.duration.secs=30
audio.offload.video=true
ro.af.client_heap_size_kbyte=7168
ro.config.media_vol_steps=25
ro.config.vc_call_vol_steps=6Camera
camera.disable_zsl_mode=1
Charger
ro.charger.disable_init_blank=true
ro.charger.enable_suspend=trueDRM
drm.service.enabled=true
FRP
ro.frp.pst=/dev/block/bootdevice/by-name/config
Graphics
debug.gralloc.enable_fb_ubwc=1
debug.sf.disable_backpressure=1
debug.sf.enable_hwc_vds=1
debug.sf.hw=1
debug.sf.latch_unsignaled=1
dev.pm.dyn_samplingrate=1
persist.demo.hdmirotationlock=false
persist.hwc.enable_vds=1
persist.sys.wfd.virtual=0
ro.opengles.version=196610Media
media.stagefright.thumbnail.prefer_hw_codecs=true
vidc.enc.dcvs.extra-buff-count=2OEM Unlock
ro.oem_unlock_supported=1
RIL
keyguard.no_require_sim=true
persist.radio.multisim.config=dsds
ril.subscription.types=NV,RUIM
ro.com.android.dataroaming=true
ro.telephony.call_ring.multiple=false
ro.telephony.default_network=22,20
ro.telephony.iwlan_operation_mode=legacy
telephony.lteOnCdmaDevice=1SurfaceFlinger
ro.surface_flinger.force_hwc_copy_for_virtual_displays=true
ro.surface_flinger.max_frame_buffer_acquired_buffers=3
ro.surface_flinger.max_virtual_display_dimension=4096
ro.surface_flinger.protected_contents=trueTimeService
persist.timed.enable=true
VoLTE
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1Wi-Fi
wifi.interface=wlan0
end of device/oneplus/msm8998-common/system.prop
ADDITIONAL_BUILD_PROPERTIES
ro.treble.enabled=true
persist.debug.dalvik.vm.core_platform_api_policy=just-warn
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
ro.build.fingerprint=OnePlus/OnePlus5/OnePlus5:10/QKQ1.191014.012/2010292059:user/release-keys
ro.lineige.version=0.22-r-20220224165877-release-cheeseburger
ro.lineige.releasetype=dev
ro.lineige.build.version=0.22
ro.modversion=0.22-r-20220224165877-dev-cheeseburger
ro.lineigelegal.url=https://lineigeos.org/legal
ro.elegal.url=https://e.foundation/legal
ro.cm.build.pipeline.id=165877
ro.cm.build.pipeline.iid=7199
ro.lineige.display.version=0.22-20220224165877
ro.lineige.build.version.plat.sdk=9
All this I have been changing it in my computer so I get the new build, which I sideload it to my device.
Then I have install magisk, do all what you have write, but I am not sure what to put in deny list. I have put there mitID and Aurora Store and microG. Mitid has been installed from Aurora Store.
And still the phone is recognize like rooted
The items I have added to denylist are MitID + Google play services see screenshot
The others I think are not needed
I use aurora store and microG, nothing to do with google play. That why all this. Otherwise if I need to use google play, I will use the stock rom , but because I wanna be out of google as much as I can , this problem with mitID has pop up.
And how can I give root acces to buildpropeditor?
Sorry I don’t have experience with that. I myself use lineage to get newer android versions for my device and get rid of the vendor modifications. Have a minimal version of Gapps.
Can your device pass safety net test. (Can be checked with an app such as SafetyNet test?
I dont think so, if it is check like rooted
cts fail
Magisk is supposed to hide that you are root from the libraries usually used to check for root access and should be able to do so. The apps added to the DenyList should not experience to have “extra rights” and be running “non root”.
MitId then has added some extra checks on top of that - that are not standard “root checks” like the check for the lineage string in build.prop. This is really not usual practice but rather some developer on MitId trying to be clever and do some additional checks of their own.
I have been changing all the lines with what you suggest . I have installed that 2 modules. And still is not passing the safetynet. Øv
maybe this is useful: https://www.reddit.com/r/MicroG/comments/izvqnt/how_can_i_pass_safetynet_in_lineageosmicrog/
there is this at the bottom of the thread:
I got SafetyNet on Lineage+MicroG and the latest Magisk version. Select
microG service coreanddroid helperin the zygisk denylist, then use the Magisk Prop Config module and select the correct fingerprint for your device (XDA thread). Reboot and remember to activate the SafetyNet option in MicroG settings. Done
Seems if yoiu are using microg there are some other modules and items in denylist needed
2 Likes
I cant find that android helper ?