yashsingh1/xdaforums huggingface dataset:
[Magisk] iSyncX:
Any fingerprints for Oneplus 7 GM1900 or GM1901 fingerprints would work? Also does spoofing this and getting the wrong fingerprint messes up the dpi when installing apps from playstore? Thanks
[Magisk] Didgeridoohan:
Copy - paste? :confused:
[Magisk] Didgeridoohan:
Yes. There's none for GM1900 in the included list, but you've got both Android 9 and 10 prints for GM1901.

No. I'm not quite sure why you think it would...
[Magisk] BeeJ1109:
Worked that out, so I transferred to General Magisk Discussion and reposted.
[Magisk] Didgeridoohan:
Fingerprints list updated to v87

It's been a whooping two days since the last update. But still there are a whole bunch of new and updated prints already submitted by several wonderful people! Thank you so much to [MENTION=10762599]s3v3ru5[/MENTION], [MENTION=9699281]pawloland[/MENTION], [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=5293805]GtrCraft[/MENTION] and [MENTION=9098612]Filo1995[/MENTION] for the prints you've posted.

The fingerprints list will update when you run the props command, or by using the -f option or from the "Edit device fingerprint" menu if you've disabled automatic list updates.

New

OnePlus 8 IN2011

OnePlus 8 IN2015

OnePlus 8 IN2017

OnePlus 8 Pro IN2021

Sony Xperia M

Xiaomi Redmi K30 Pro

Updated

OnePlus 5

OnePlus 5T

OnePlus 6

OnePlus 6T

OnePlus 7 Pro NR Spr GM1925

OnePlus 8 IN2013

OnePlus 8 Pro IN2023

OnePlus 8 Pro IN2025

Poco X2

Xiaomi Mi 8
[Magisk] russel5:
[MENTION=4667597]Didgeridoohan[/MENTION]

Sony XZ1 Compact, Android 9

Sony/G8441/G8441:9/47.2.A.11.228/3311891731:user/release-keys__2019-09-01

Update please in your base, works perfect on LineageOS 17.1
[Magisk] Didgeridoohan:
Fingerprints list updated to v88

Forgot about one submitted fingerprint yesterday and another one was submitted, so here's a small update again.

Thank you [MENTION=453495]JEANRIVERA[/MENTION] and [MENTION=4688377]russel5[/MENTION].

The fingerprints list will update when you run the props command, or by using the -f option or from the "Edit device fingerprint" menu if you've disabled automatic list updates.

New

HTC Exodus 1

Updated

Sony Xperia XZ1 Compact
[Magisk] Displax:
Updated prints

Xiaomi Mi A2

Xiaomi Mi A2 (8.1.0 & 9 & 10):Xiaomi:Mi A2=xiaomi/jasmine/jasmine_sprout:8.1.0/OPM1.171019.011/V9.6.17.0.ODIMIFE:user/release-keys__2018-11-05;xiaomi/jasmine/jasmine_sprout:9/PKQ1.180904.001/V10.0.18.0.PDIMIXM:user/release-keys__2019-12-05;xiaomi/jasmine/jasmine_sprout:10/QKQ1.190910.002/V11.0.8.0.QDIMIXM:user/release-keys__2020-04-05

Xiaomi Mi A2 Lite

Xiaomi Mi A2 Lite (8.1.0 & 9 & 10):Xiaomi:Mi A2 Lite=xiaomi/daisy/daisy_sprout:8.1.0/OPM1.171019.019/V9.6.11.0.ODLMIFF:user/release-keys__2018-11-01;xiaomi/daisy/daisy_sprout:9/PKQ1.180917.001/V10.0.20.0.PDLMIXM:user/release-keys__2020-03-01;xiaomi/daisy/daisy_sprout:10/QKQ1.191002.002/V11.0.4.0.QDLMIXM:user/release-keys__2020-03-01

Xiaomi Mi A3

Xiaomi Mi A3 (9 & 10):Xiaomi:Mi A3=Xiaomi/laurel_sprout/laurel_sprout:9/PKQ1.190416.001/V10.3.16.0.PFQMIXM:user/release-keys__2020-03-05;Xiaomi/laurel_sprout/laurel_sprout:10/QKQ1.190910.002/V11.0.14.0.QFQMIXM:user/release-keys__2020-04-05

Please, verify those prints. All must be correct, but anyway...
[Magisk] sidg2:
Hi. I am using Moto Z Play Oreo 1 August 2018 patch OPNS27.76-12-22-9.

Boot/kernal is patched & dm-verity is disabled.

Latest Magisk v20.4 is installed and systemless root features like systemless Hosts is working fine. Also in Magisk, the CTS profile and basic integrity is showing passed.

Actually, I want to enable the screen Mirroring (Miracast) option and for that I have to edit build.prop and change the value of persist.debug.wfd.enable=0 to 1.

But I want to do it systemless-ly without edit the actual build.prop in system partition.

I have installed the Magisk module "Magiskhide prop config" but I don't know what to do next. I don't know about any latest commands which work with latest magisk version. Actually I don't know about any commands.

So please tell me exactly what I have to do for sustemless-ly edit the build.prop in step by step. [MENTION=4667597]Didgeridoohan[/MENTION]
[Magisk] Didgeridoohan:
To set that prop, and since you have this module, just run the command "props" in a terminal emulator, pick the option to "Add/edit custom props" (currently option 4) and follow the on-screen instructions from there.
[Magisk] Displax:
Updated Essential PH-1

Essential PH-1 (7.1.1 & 8.1.0 & 9 & 10):Essential:PH-1=essential/mata/mata:7.1.1/NMK24B/468:user/release-keys__2018-02-05;essential/mata/mata:8.1.0/OPM1.180104.267/399:user/release-keys__2018-07-05;essential/mata/mata:9/PQ1A.190105.112/550:user/release-keys__2019-08-05;essential/mata/mata:10/QQ1A.200105.032/540:user/release-keys__2020-02-05

---------- Post added at 20:32 ---------- Previous post was at 20:01 ----------

And little rename according to https://developers.google.com/android/images

Google Nexus 7 2012 LTE >>> Google Nexus 7 2012 Mobile

Google Nexus 7 2013 LTE >>> Google Nexus 7 2013 Mobile

Because Google Nexus 7 2012 actually 3G, not LTE.

---------- Post added at 21:19 ---------- Previous post was at 20:32 ----------

Razer Phone

Razer Phone (7.1.1 & 8.1.0 & 9):Razer:Phone=razer/cheryl/cheryl:7.1.1/NMF26X-RZR-180118/3005:user/release-keys__2018-01-05;razer/cheryl/cheryl:8.1.0/OPM1.171019.011-RZR-180803/6033:user/release-keys__2018-07-05;razer/cheryl/cheryl:9/P-MR2-RC001-RZR-N/7083:user/release-keys__2019-11-05

Razer Phone 2

Razer Phone 2 (8.1.0 & 9):Razer:Phone 2=razer/cheryl2/aura:8.1.0/O-MR2-RC009-RZR-181124/2009:user/release-keys__2018-10-05;razer/cheryl2/aura:9/P-SMR3-RC002-RZR-200226/3141:user/release-keys__2020-03-05
[Magisk] MPachulski24:
Ginkgo soon?
[Magisk] Didgeridoohan:
If someone submits a fingerprint for it in the near future, yes.
[Magisk] Conscience04:
Thanks for the tool but it doesnt list device models on me

İt lists all brandmarks but not models.
[Magisk] sidg2:
Thanks [MENTION=4667597]Didgeridoohan[/MENTION] for your reply. If I don't install magiskhide prop config module or any other module in magisk manager, in that case what I have to do to change the build.prop systemless-ly? I don't know how to make and use the bootscripts and all that very technical steps. So, please just tell me simple terminal emulator commands which edit build.prop values systemless-ly by the help of magisk without touching the real system build.prop. And it should be permanent and should not be remove by next reboot.
[Magisk] Didgeridoohan:
And what if you enter the number listed for one of those brands? If things actually aren't working for you I would at least need to see the module logs.
[Magisk] Conscience04:
I tried nearly all of the brands but didnt work i would like to post logs but i cant insert links, how can i directly upload them? Thanks
[Magisk] Didgeridoohan:
Since you don't seem to be too technical I suggest that you simply use this module. It's the easiest solution...

If you really want to use something else you'd have to use a boot script or perhaps an app like Tasker to execute a command with the resetprop tool at each boot (that's the only way to make it "permanent").

You'll find the details on how to use Magisk's boot scripts here:

https://topjohnwu.github.io/Magisk/guides.html#boot-scripts

And the syntax and detail for resetprop here:

https://topjohnwu.github.io/Magisk/tools.html#resetprop

But basically you just enter:

resetprop <prop name> <prop value>

either in the boot script or whatever app you're using to run the command.
[Magisk] Conscience04:
I hope i wont be blocked:confused:

https://imgur .com/a/RAPdEjU

Logs:https://gofile .io/?c=xDKv1X
[Magisk] Didgeridoohan:
What do you mean by "didn't work"? What happens? You'd have to upload the logs somewhere (Google Drive, etc) and post the link to me. Maybe also include a screenshot of what you mean.
[Magisk] Conscience04:
I cant insert links to other sites because i havent reach to 10 posts and İnserted them with spaces couple minutes ago
[Magisk] Didgeridoohan:
Yeah, I saw. We both posted at the same time...

Looks like your fingerprints files have gotten messed up. You could try running the props script again, since I've just updated the fingerprints list again (v89). That should generate new files.
[Magisk] Conscience04:
Thanks could you give ETA for list update or are there other solutions like reinstalling module from magisk works?

---------- Post added at 10:33 PM ---------- Previous post was at 10:28 PM ----------

Wow now i removed the edxposed rebooted then device models listed thanks for your help
[Magisk] Didgeridoohan:
Fingerprints list updated to v89

Well... [MENTION=6345368]Displax[/MENTION] decided to throw about a metric tonne of prints on my head. So naturally I had to spend some time digging out of the wreckage caused by the crash. I do test every single print I add to the module, and this time is no different. If I calculated correctly (and I might not have since I've gone slightly cross-eyed) I have just spent some time testing 66 new (mainly old) fingerprints (good thing I've got the process mostly automated). In truth most of them aren't actually needed since they're just completing the list with missing Android versions for a bunch of devices (with a couple of the newest available prints thrown in there as well). This update can officially be labelled: "just because we can".

Wow...

The fingerprints list will update when you run the props command, or by using the -f option or from the "Edit device fingerprint" menu if you've disabled automatic list updates.

Anyway, here's the list of devices. None of them are new to the list, but they should now be complete when it comes to the available Android versions for those devices (which means that there are now some devices with fingerprints from 8 Android versions in the list).

Updated

Essential PH-1

Google Pixel

Google Pixel XL

Google Pixel 2

Google Pixel 2 XL

Google Pixel C

Google Nexus 5X

Google Nexus 6

Google Nexus 6P

Google Nexus 9 LTE

Google Nexus 9 WiFi

Google Nexus Player

Razer Phone

Razer Phone 2

Xiaomi Mi A2

Xiaomi Mi A2 Lite

Xiaomi Mi A3
[Magisk] Didgeridoohan:
See the post above. Reinstalling the module should also work...

That's weird... I've seen issues caused by EdXposed, but never that. You sure though? Since I had just updated the list, as soon as you ran the props command the fingerprint files would have been recreated. I don't think it had anything to do with EdXposed.
[Magisk] Conscience04:
Yes i'm sure, i have tried to just reboot before that but didnt work, after removing edxposed it worked
[Magisk] sidg2:
[MENTION=4667597]Didgeridoohan[/MENTION] Please detailed reply to my both questions.

Q1. So this one line command

"resetprop persist.debug.wfd.enable 1"

in terminal emulator is a bootscript ???

I was thinking that I have to write hundreds of words and create a file of bootscript than flash it, something like that.

If this is not a bootscript than how to create it and use it? Also tell how to delete it?

I can do technical stuff if I get detailed guidence.

Q2. I see your this few days old reply to [MENTION=5925610]chuppito[/MENTION] who also had same question like me and you have replied this to him.

I have already delete all installed magisk module like Magiskhide prop config and then I reboot. After that I run this same command in terminal emulator.

" su

resetprop persist.debug.wfd.enable 1 "

And it works. It enables the top three dots option for Cast in my Moto Z Play.

But you said that it is a temporary command and it will only survive until a reboot but in my case it works permanently because I have reboot my phone several times and I also wiped delvik cache & cache in twrp. But Cast option is still there. Why is this happened, I am curious to know ?
[Magisk] Didgeridoohan:
That is not a boot script, no. A boot script is a file with commands that run at boot (as detailed in the link I posted).

But yes, you're right that this particular prop doesn't need a boot script... What I forgot is that persist props are just that: persistent. You only need to run the command once and the prop will stay with that value until a new value is set, even across reboots. Thank you for reminding me about that.

So, you're done. You've achieved your mission. :good:
[Magisk] chuppito:
[MENTION=8251837]sidg2[/MENTION] Hi, I confirm that for my part, it's permanent (unless there is a new value as stated [MENTION=4667597]Didgeridoohan[/MENTION])
[Magisk] Maron Prime:
Aermoo M1 (Android 7.0) (Should work with Doogee S60 too but I can't confirm that)

alps/full_s21v57c2k_dg/s21v57c2k_dg:7.0/NRD90M/1515719372:user/release-keys

Link to screenshot:

https://ibb.co/PxWbKDP
[Magisk] Didgeridoohan:
Thank you, but that fingerprint does not pass the CTS profile check.
[Magisk] ipdev:
May Pixel prints.

List is slightly different.

I started adding the build date to the description below the printslist.

Yep, Google appears to build in the first half of the month so the April 1st builds are actually May (security) releases...

Cheers all. :cowboy:
[Magisk] Didgeridoohan:
Fingerprints list updated to v90

As usual at the start of the month, [MENTION=7280276]ipdev[/MENTION] has supplied this months updates for the Pixel devices. Thank you very much.

The fingerprints list will update when you run the props command, or by using the -f option or from the "Edit device fingerprint" menu if you've disabled automatic list updates.

Updated

Google Pixel 2

Google Pixel 2 XL

Google Pixel 3

Google Pixel 3 XL

Google Pixel 3a

Google Pixel 3a XL

Google Pixel 4

Google Pixel 4 XL
[Magisk] phil454:
Need some help

I keep getting no command prop found when typing prop in termux. I have no idea why it wont work. I have a Pixel 4 XL with the latest update. :(
[Magisk] ipdev:
Using Termux you need to switch to root first.

The command is props not prop.

Typos are one of my worst enemies in the shell/script world. ;)

su
props

Cheers. :cowboy:
[Magisk] phil454:
Thanks for your help. That solved the problem. The website i was following instruction on said it was prop. so that was what I was typing. The only reason im editing the props is to add net.tethering.noprovisioning.

I did that with my old pixel 3 xl and I think that was the only line I added but this tutorial im reading says to add settings put global tether_dun_required 0 as well. Any idea if that is required? Thanks.
[Magisk] ipdev:
Not sure off hand since I do not use/set that prop.

Will look into it a bit and see what I can find. ;)

Cheers. :cowboy:
[Magisk] Didgeridoohan:
That's one of the classic build.prop edits... I've never had to use it myself, fortunately, but if things are working without the tether_dun_required command there shouldn't be anything to worry about. If it doesn't work you'll likely need it. But, it doesn't hurt to add it either way...

Just curious: what tutorial were you following?
[Magisk] phil454:
I was following this tutorial.

https://piunikaweb.com/2019/11/07/h...tive-tethering-on-a-rooted-google-pixel-4-xl/
[Magisk] Didgeridoohan:
Thank you. I contemplated leaving a comment saying their guide is a bit off, but a Facebook login is needed for that... No thanks.
[Magisk] pndwal:
FWIW, he does cite 'source' XDA thread which correctly specifies 'props' in OP:

https://xdaforums.com/pixel-4-xl/how-to/how-to-native-tethering-rooted-pixel-4-t3993405 PW
[Magisk] TheUndertaker21:
getting bootllop on latest havoc 3.5 GSI

only changing fingerprint

weird :(
[Magisk] Didgeridoohan:
Weird indeed... Logs?
[Magisk] TheUndertaker21:
Sure

View attachment 5014311

Thanks for the quick reply
[Magisk] Didgeridoohan:
That file unfortunately seems to be broken.
[Magisk] TheUndertaker21:
https://drive.google.com/file/d/1CjdrCRQTAu9LrAP3mcd34B4CMvJyI8LH/view?usp=drivesdk
[Magisk] Didgeridoohan:
Sorry, but that's a zero byte file that just errors out when trying to download.
[Magisk] TheUndertaker21:
Yeha I noticed.

Still showing zero. Idk lol
[Magisk] mik84:
I, too, on havoc 3.5 GSI do not boot the OS after installing fingerprint.

I tried post-fs-data, it doesn’t load, with late_start the phone loads, but the device is “uncertified”.

Logs: drive.google.com/open?id=191cmny0zZ39iJxwmfi8jsSJqMoFueanZ
[Magisk] Evengard:
For some reason I'm getting the error

"The service.sh module script does not

appear to have run during boot."

I've tried to fully reinstall the script, disable EdXposed, reflashing Magisk with the stock boot image, changing the boot process via props -s - nothing helped.

What is wrong?

PS: also the log file was 0 bytes for me too, so I pulled it directly from /data/adb/mhpc - seems to be related to some weird selinux problem.
[Magisk] Didgeridoohan:
Seeing logs from when the module settings are standard and the device doesn't boot would be ideal.

And besides module and Magisk logs, a boot log would also likely be necessary to try to figure things out.

I didn't ask before, but does your issue arise with a certain release of the ROM, or a specific Magisk version, etc? If there's something I can help with I need details. I suspect there's not much I can do though...
[Magisk] Didgeridoohan:
That's because there's a bug in Magisk Canary release 20409. It's been fixed already (but no new release yet).
[Magisk] TheUndertaker21:
I used safetynet v3 and deleted line 11 in post data something in data/adb/module /safetynet v3 or whatever.

I wanted to use this it's better but whatever.

I'd move to another gsi once the other rom gets updated
[Magisk] Evengard:
Thank you for your answer! I'll wait for the new canary release then.

And separate thanks for that quick answer!
[Magisk] Didgeridoohan:
If using Safetypatcher worked I would very much appreciate if you could provide logs that show the issue you're having, because that would suggest that there is an issue with this module.

Did you try using the regular method of picking a fingerprint from the list, or only the "Treble GSI ROM" option?
[Magisk] TheUndertaker21:
I picked first, finger print then it bootloop then I used the treble setting. Same thing.

I can provide logs I'm not sure how to be honest.

If I can provide a log while it's bootlooping then I'd do it.

Let me. Know. I'm here to help. It's midnight here. If I don't reply. I will tomorrow morning
[Magisk] Didgeridoohan:
I linked instructions on how to get a boot log in my previous post:

https://didgeridoohan.com/magisk/MagiskHelp
[Magisk] lilo_ind:
Please add for Zte Nubia Red Magic 3, thanks
[Magisk] zfk110:
could you please look into it to see why its failing?
[Magisk] TheUndertaker21:
Back

Here's the boot script.

https://drive.google.com/file/d/1EijfdH4pJTd6BWjwSxZTFy5l096lGP-D/view?usp=drivesdk

Xda kept giving me error when tried to post it.

Thanks.
[Magisk] Incrovantilist:
[MENTION=4667597]Didgeridoohan[/MENTION] Any chance of updating fingerprints of Sony phones to latest available android version? (I use XZP and latest is pie)
[Magisk] Didgeridoohan:
That particular subject (updating fingerprints) is actually covered in the docs:

https://github.com/Magisk-Modules-R.../master/README.md#please-update-fingerprint-x
[Magisk] Didgeridoohan:
Unfortunately there's nothing about the information you have provided that would help in answering that... Best I can give you is:

Have you tried toggling MagiskHide off and on again?

Have you made sure that MagiskHide is actually working at all (for example by adding one of those terminals app you have to the Hide list and then running the su command)?

For more, check here and if you still can't get thing working I suggest you post in the General support thread, to keep posts in this thread about the module.
[Magisk] Didgeridoohan:
Question: Is this from an instance when the device refuses to boot?

If so, this issue is not specific to this module but rather changing the device fingerprint since in that log you aren't actually using MagiskHide Props Config, but SafetyPatcher. If this is the case, I suggest you bring this up in the ROM thread instead and with the help of the users and developers there try to figure out why changing the device fingerprint causes the device to not boot.

If that log is from when the device boots, it can't actually tell me anything... Unless I can compare it to one where the device doesn't boot.
[Magisk] TheUndertaker21:
Wait?

It overrides it lol.

Let me know try again. I'd get the log again.
[Magisk] TheUndertaker21:
https://drive.google.com/file/d/1FB4kgA_r4aizy90P_rCKS3uun2O0wEmf/view?usp=drivesdk

Last one.

Idk at this point.

Don't think the havoc team cares

Also same issue on other gsi roms.

I'm on evolution now.

It got bootloop when changed fingerprint
[Magisk] Didgeridoohan:
It's getting pretty hard to follow what's going on... I've asked several questions that still go unanswered.

I need to know (to start with, at least):

Does any of the logs you've sent me come from when the device actually boots?

In the last log, it looks like you did a fresh install of MagiskHide Props Config. Did you set it up with a fingerprint through a configuration file at install, or is it a completely fresh install?

Does the device bootloop when you install SafetyPatcher?

Have you tried without other modules installed, to make sure there isn't some kind of conflict going on?
[Magisk] Displax:
Updated Xiaomi Mi A3

Xiaomi/laurel_sprout/laurel_sprout:10/QKQ1.190910.002/V11.0.15.0.QFQMIXM:user/release-keys__2020-05-05
[Magisk] LONE_GUY:
can you add lenovo k6 power.

thanks in advance
[Magisk] pndwal:
Often repeated advice:

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228/post82527741

And please have a look at OP. :good: PW
[Magisk] TheUndertaker21:
1. The device doesn't provide any logs while in bootloop and while fingerprint is set.

I had to uninstall props in other to boot

And safety patcher doesn't bootloop

Also props also bootloop if flashed in twrp

It doesn't if flashed in magisk.

There's no other modules.

It did the same thing with fresh gsi installed.

I'm going to try Phh's base and see.

I have been trying to see what could cause it.

I think it's either module or Phh side.
[Magisk] Didgeridoohan:
Are you absolutely sure about that? After the device bootloops, boot directly to TWRP and grab the boot log and all files described here: https://github.com/Magisk-Modules-R...lob/master/README.md#collecting-logs-manually

The TWRP install log of the module would also be interesting (if you're saying that a fresh install of the module through TWRP is causing a bootloop).

Since I don't have any devices that can run GSIs there's absolutely nothing I can do without proper information, and logs that don't show the issue are of no use whatsoever...

I might add that in regards to GSIs and Magisk, there's also this: https://github.com/topjohnwu/Magisk/issues/844
[Magisk] TheUndertaker21:
View attachment 5016431

ok provided you with recovery log and magisk log as well

it worked before, so i'm sure it's not magisk related
[Magisk] Didgeridoohan:
You said it stopped working with a recent ROM update, so it might be related to that (possibly in combination with Magisk). Just guessing though...

But we are so, so close now. The module log clearly shows that something happens after the post-fs-data stage, but I need that all-important boot log to see what...
[Magisk] TheUndertaker21:
View attachment 5016503

still unable to get the script to work while in bootloop but i tried phh base and i was able to use props fine after changing fingerprint. i'm guessing the issue is on havoc and evolution build.

here's one last log. don't think i can do much at this point.

this is havoc 3.5

the whole magisk logs with modules and eevrything

for the script i gave it 0755

do i need to give it a different permission ?

thanks

edit: on phh build props works but it's not passing anything even after i run the core
[Magisk] Kennytriplex:
Anyone been able to solve this issue? I’m having the exact same problem. And the log has nothing written in it

---------- Post added at 12:20 AM ---------- Previous post was at 12:17 AM ----------

Anyone been able to solve this issue? I’m having the exact same problem. And the log has nothing written in it