yashsingh1/xdaforums huggingface dataset:
[Magisk] ipdev:
Hi all.

I am a little frustrated with a personal project so, I decided I would blame my procrastination on grabbing and testing some fingerprints instead. ;)

WTF Google????

I haven't gotten an email from them in quite awhile when testing fingerprints.

Apparently I'm not using the latest Google apps on my Redmi 7 :D

Must have been triggered from Pixel 3aXL (abc rom) or Poco F1 (lineage nightly) testing some fingerprints. I do not have a Redmi 7 but, I miss the emails from Google. Kind of a little reassurance that everything was correct. (Cluttered up my Google Device list a bit though..)

Maybe they are changing things up again or it's just a hiccup.

We will chalk it up to a Google thing.;)

So a quick set of fingerprints.

Redmi 6 and 6A might pass. :confused:

Works on my Nexus 7 2013 WiFi (arm tablet) failed on Pixel 3aXL and Poco F1 (both arm64 phone)

Not the first time I've had a print fail on one device and pass on others.

Why I try to test on multiple (different) devices.

Redmi 7, Redmi Note 7 and Redmi Note 9S pass for me.

Obviously Redmi 7 was a complete successes. ;)

Cheers all. :cowboy:

PS.

Now as I post this, I realize Pixel 3aXL and Poco F1 are running canary 20411 were as Nexus 7 is still on canary 20405. Not sure if that is making a difference.?
[Magisk] ipdev:
Hi.

Since manually changing the build.props worked for you..

I'm not a Samsung guy, I have a few older tablets but, I sure the batteries are dead by now. SM-T230, T330 and T530

I'm not sure if it will break anything (KNOX) but you could try running insecure and debuggable to try and grab an adb logcat on boot.

ro.adb.secure=0
ro.secure=0
ro.debuggable=1

These three settings should let you pull an adb logcat as soon as possible without authentication and hopefully before boot complete.

Just not sure were you need to set them on your device.

vendor/system build.prop, default.prop..

I'm not familiar with Samsung and what I knew I forgot most of.

One of the reasons I did not recommend it earlier.

Give it a try if you are curious or up for a challenge. ;)

I had AOSP GSI running on three devices but, recent changes in device (firmware/vendor/boot) and/or the GSI (system) seemed to break WiFi, SIM card or Sound for me. Haven't taken the time to investigate. If I can get one working properly I'll give it a go and try to get logs.

Out of curiosity, did you try using a MagiskHidePropsConfig configuration script?

Config File GitHub - Link

Cheers. :cowboy:
[Magisk] Some_Random_Username:
Hi, here are a few updated OnePlus A10 fingerprints:

OnePlus 5: OnePlus/OnePlus5/OnePlus5:10/QKQ1.191014.012/2004231127:user/release-keys__2020-04-05

OnePlus 5T: OnePlus/OnePlus5T/OnePlus5T:10/QKQ1.191014.012/2004231356:user/release-keys__2020-04-05

OnePlus 8 IN2011: OnePlus/OnePlus8_IND/OnePlus8:10/QKQ1.191222.002/2005090021:user/release-keys__2020-04-01

OnePlus 8 IN2013: OnePlus/OnePlus8_EEA/OnePlus8:10/QKQ1.191222.002/2005090021:user/release-keys__2020-04-01

OnePlus 8 IN2015: OnePlus/OnePlus8/OnePlus8:10/QKQ1.191222.002/2005090021:user/release-keys__2020-04-01

OnePlus 8 Pro IN2021: OnePlus/OnePlus8Pro_IND/OnePlus8Pro:10/QKQ1.191222.002/2005100226:user/release-keys__2020-04-01

OnePlus 8 Pro IN2023: OnePlus/OnePlus8Pro_EEA/OnePlus8Pro:10/QKQ1.191222.002/2005100226:user/release-keys__2020-04-01

OnePlus 8 Pro IN2025: OnePlus/OnePlus8Pro/OnePlus8Pro:10/QKQ1.191222.002/2005100226:user/release-keys__2020-04-01

Please mind that a new OOS build for 5 and 5T might be released in coming days so you might want to put fingerprints for these devices on hold.
[Magisk] Reznor7:
You were correct about the GitHub update bit. Also, it appears that the bug is with the latest Havoc GSI. I installed the latest LineageOS GSI, and the module works perfectly.
[Magisk] Didgeridoohan:
There has been reports along a similar line already, but I am extremely curious as to what is actually going on and would love to figure it out (even though I realise I have a very low probability of doing so with my limited experience and knowledge with GSIs). This kind of stuff is the perfect procrastination excuse for my 5(!) reports and essays I have to hand in durnig the next 10 days.

What does Havoc have against me!? :crying: /joke
[Magisk] TheUndertaker21:
i'm going to provide you a log from phh GSI

it does install on phh base but it's not working at all. it doesn't bootloop though

i think these gsi implementation of PHH base is causing issue.

brb with the log
[Magisk] TheUndertaker21:
[MENTION=4667597]Didgeridoohan[/MENTION]

Hey boss here's a log with bootlog and normal logcat as well

Props installed on phh with no bootlog but it's failing

You can see this is a clean install with no exposed etcc

Only two modules BusyBox and props

View attachment 5021547
[Magisk] Didgeridoohan:
Thank you. Do you have the module logs for that as well? They might confirm a hunch I have...
[Magisk] TheUndertaker21:
Like this log ?

View attachment 5021563
[Magisk] Didgeridoohan:
No, that's the Magisk log (which actually is included in the boot log you previously posted).

I'm talking about the module logs that you can collect by picking the corresponding option in the main menu of the ui (currently option 7). Those might show me a few things about the module setup and scripts.
[Magisk] TheUndertaker21:
that option doesn't work on gsi lol

just 0 bytes

how come you don't have any gsi compatible phone ? treble has been activated since android 8
[Magisk] Didgeridoohan:
If you take a look at the docs I linked you can also collect the logs manually.

The newest device I have is a OnePlus 3T. I'm a piss-poor student and can't afford an upgrade. And I don't really need an upgrade anyway... When stuff breaks, I fix it. Just recently I replaced the camera module and the battery. Like new. I hold on to a device until it is well and truly dead. By then I've gotten more than my fair share of use out of it.

I'm gonna be very careful when picking my next device... I've even contemplated going without, but the damned thing is way too integrated into my everyday life and society as a whole. Could be a fun experiment though.

There's too much greed involved in this industry (and many other) that I don't want to be a part of. Conflict materials, inhuman work conditions all along the production chain, low to no sustainability, etc, etc. Cheap and crappy (or ridiculously expensive) throwaway electronics being pumped out by the millions and you can bet it's not the end-users that are paying the ultimate price. If I do go for a new device it'll likely be something like Fairphone or Shifthpone.

Rant is over. No idea if any of that made any kind of sense whatsoever. Let's get back to the usual programs...
[Magisk] TheUndertaker21:
No worries bro

You are smart as hell

Just finish your school and I have no doubt you'd end up working for a big company

Used to be like you too

Just don't give up

View attachment 5021653
[Magisk] Didgeridoohan:
Thank you.

Everything looks like it should with your setup, and the print you're using is confirmed to be certified so it's not that. If MagiskHide works as it should I can (at the moment) only conclude that there's something about the ROM that's triggering SafetyNet. Which neither I nor Magisk can do anything about...
[Magisk] Displax:
Updated Xiaomi Mi A1

xiaomi/tissot/tissot_sprout:9/PKQ1.180917.001/V10.0.21.0.PDHMIXM:user/release-keys__2020-05-01
[Magisk] ayesse:
OnePlus 7 Pro Open Beta 14: OnePlus/OnePlus7Pro/OnePlus7Pro:10/QKQ1.190716.003/2005122138:user/release-keys__2020-05-01
[Magisk] Nightshadex543:
Interesting, thanks.
[Magisk] Some_Random_Username:
And as expected, OnePlus released yesterday a new build for them:

OnePlus/OnePlus5T/OnePlus5T:10/QKQ1.191014.012/2005112111:user/release-keys__2020-04-05

OnePlus/OnePlus5/OnePlus5:10/QKQ1.191014.012/2005112104:user/release-keys__2020-04-05
[Magisk] Filo1995:
Update

Xiaomi Redmi K30 Pro (10)

Redmi/lmi/lmi:10/QKQ1.191117.002/V11.0.19.0.QJKCNXM:user/release-keys

Patch:2020-04-01 (Unchanged)
[Magisk] Didgeridoohan:
Module updated to v5.2.5-v91

There's been quite a few fingerprints posted recently, but I have been taking my sweet time getting them published. Simply because I also have been working on fixing a couple of small problems with the module. [MENTION=7280276]ipdev[/MENTION] reminded me that I needed to fix the verbose boot log, so I did (together with a few other small things).

This time around the fingerprints were provided by a bunch of helpful people:

RealAkito @ Github, [MENTION=6345368]Displax[/MENTION], [MENTION=7280276]ipdev[/MENTION], [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=5351653]ayesse[/MENTION], [MENTION=9098612]Filo1995[/MENTION]

As usual, huge thanks go out to all of you.

Changelog

v5.2.5

Fixed and improved verbose boot logging.

Fixed collecting logs producing a broken 0-byte file.

Logging does not need to use nanoseconds. Microseconds is enough.

Added ro.bootmode and ro.boot.mode to "Edit MagiskHide props".

Don't use ro.build.selinux in "Edit MagiskHide props" if it isn't set.

Added fingerprints for POCO F2 Pro, Redmi K30 Pro Zoom Edition and Note 9S, Samsung Galaxy A20 and Xiaomi Redmi 6 and 6A. Updated fingerprint for OnePlus 5, 5T, 7 Pro (GM1911 and GM1917) several variants of 8 and 8 Pro, Redmi K30 Pro and Xiaomi Mi A1, Mi A3, Redmi 7 and Redmi Note 7. Relabeled Xiaomi Redmi K30 Pro and Redmi Note 8 Pro with Redmi as manufacturer. List updated to v91.
[Magisk] Sid220:
[MENTION=4667597]Didgeridoohan[/MENTION] New Fingerprint for Xiaomi PocoPhone F1

Xiaomi/beryllium/beryllium:10/QKQ1.190828.002/V11.0.8.0.QEJMIXM:user/release-keys

Android Version 10

Security Patches 2020-04-01
[Magisk] Some_Random_Username:
OnePlus just released a new update for its 5G EU model, OnePlus 7 Pro NR GM1920, here is updated fingerprint: OnePlus/OnePlus7ProNR_EEA/OnePlus7ProNR:10/QKQ1.190716.003/2005102305:user/release-keys__2020-05-01
[Magisk] swour:
Samsung Galaxy A5(2017) fingerprint update:

Security patch date: 2020-05-01
[Magisk] amipel:
Redmi note 8 (Ginkgo)

I found this but im supper new to android. photos for verification.

"Target: xiaomi/ginkgo/ginkgo:9/PKQ1.190616.001/V11.0.8.0.PCOMIXM:user/release-keys"

[IMG="Security Patch level"]https://i.ibb.co/WDjyDFn/cert-ginkgo-spl.png[/IMG][IMG="Certificate"]https://i.ibb.co/vkyVXRW/cert-ginkgo.png[/IMG]
[Magisk] thunderteaser:
How to remove Magisk version check from the zip? Modules from the repo now force me to update to 20+ but I can't, otherwise this module and any module requiring scripts won't work on lavender. I hoped by downloading it here that it wouldn't have a Magisk version check but it's there. Thanks

EDIT: Solved, i just had to swap the updater binary with an older one
[Magisk] Didgeridoohan:
Yes, that would do it.

It's after all been almost 8 months since Magisk v20.0 was released, so John felt that it was safe to drop module installer script compatibility for earlier versions.

About this (made me curious):

A quick check showed one single mention of this specific problem on the Github issue tracker, and some possibly related ones. All of them have in common that they do not follow proper bug report procedures set down by John (use Magisk Canary, and provide logs).

You have any further insight?
[Magisk] thunderteaser:
I should probably report an issue myself. I also checked for this kind of issue but no Redmi/Xiaomi user seem to care (they probably don't use modules that rely on post-fs scripts). I'm fairly certain that since 20+ something has changed in when Magisk is supposed to run post fs scripts that is not compatible with MIUI roms. What's making me reluctant is that to update to 20.4 I would need to break my whole environment (and Viper which was a pain in the xxx to make it work)
[Magisk] Didgeridoohan:
That is indeed a pain... I've been holding off doing some much needed maintenance (and switching of ROMs) on my daily driver for way too long now. Just don't have the time to set everything up again...

There were some fairly big changes with Magisk v20.0, where system-as-root, 2-stage-init and a whole bunch of stuff got added that I'm not even gonna pretend to understand. There was a lot of issues with a bunch of devices following that release (mainly because a lot of OEMs don't follow standards, and that Google constantly changes said standards). A lot has been fixed though and the current Canary release seems very stable and a lot of devices that has been having issues has since been brought back to the comfort Magisk's warm embrace.

If you decide to do some testing and gathering of logs and such, do

not

use the stable release (currently v20.4). All testing and bug hunting should always be done on the Canary debug release so that we are sure that you aren't experiencing something that's already been fixed and so that logging is as verbose as it can be. Magisk logs and logcats are the way to go when it comes to logs.
[Magisk] thunderteaser:
Thanks, you have provided more insight than I could gather since forever. I will make sure to use canary when i will find some spare time to set everything up again. Thanks again
[Magisk] Juzman:
Thanks for the update. I've noticed with new version of Magisk it has it's own busybox.

Are you able to use that instead of needing the other busybox? May simplify things, and one less pre-requisite. :)
[Magisk] Didgeridoohan:
Magisk has always has its own internal Busybox. It hasn't always been 100% usable though (in the past John has built it with some applets not working, stuff like that).

With [MENTION=4544860]osm0sis[/MENTION]' Busybox I always know what I get, which is why I recommend it. I know John has been improving the internal Busybox a lot recently, but I haven't kept track off the exact changes, so it's possible that I could switch over to using it fully. Maybe for a future update...

Thanks for planting the idea. Don't think I would have considered it without your post.
[Magisk] Juzman:
Ah that makes sense. Yeah, I can understand why you would stick with busybox by osm0sis.

No worries, who knows maybe the internal busybox has all the stuff you may need for it. :)

Keep up the awesome work!
[Magisk] ricosf415:
Magisk Problems

:( My Magisk keeps changing my ID# everyday. Does anyone know why this is accuring,and if theres a fix can you please point me in the right direction. TIA
[Magisk] Mr.ziad:
Hi guys, Thank you so much for your great work! but I have a problem please help Can not pass SafetyNet's CTS Profile

I run a stock ROM Oneplus 7 pro android 10

Tried changing fingerprint to a couple of devices pick, tried to change boot to late or past, tried the original fingerprint and using costume prop changed security patch date, sadly nothing seems to work

here is a link for the logs ( XDA won't let me upload )

https://mega.nz/file/HYsFjb6Z#fHkipkuQIsmPX1_0bYGLOCRjFSiW8iVaEFwiT1nawts

Thanks!
[Magisk] Didgeridoohan:
Since you're using stock OOS you don't need this module to pass CTS. All you need to do is to enable MagiskHide in the Manager settings...
[Magisk] Mr.ziad:
That actually does it ! and I went nuts trying so many prints and props! I feel so stupid now! Thank you man! you are awesome.

one more noob question. all of my bank apps work well. except two, got an idea why ?
[Magisk] Didgeridoohan:
Not my first rodeo... :cowboy:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] estofjlw:
failing Safety Net

I installed the crdroid Android 10 ROM from https://xdaforums.com/g7-power/development/rom-t4070607 for the Moto g7 Power - and crdroid 9 (PIE) I was able to get to pass with this module and submitting the key and a security patch date,

This has both checks red. I modded the module through custom props for

motorola/ocean/ocean-9/PPOS29.114-134-13/6abfe:user/release-keys

2020-04-01

rebooted and checked the values but still no pass. This is the value from my stock phone Then I came across this => https://www.xda-developers.com/magisk-no-longer-hide-bootloader-unlock-status/

Has Google broken this module ??
[Magisk] Didgeridoohan:
If it was caused by the fingerprint only the CTS profile check would fail. Since you say both checks fail there's something else triggering it. Have you made sure that MagiskHide is enabled?

I tested that print and security patch date and it does indeed fail the CTS profile check. You sure you've got the correct patch date?

Google has not broken the module. Changing the device fingerprint has nothing to do with that article. What it is talking about is that Google has tested, and will in time activate again, proper hardware key attestation for SafetyNet. That means that it will be impossible for Magisk to hide the bootloader state on devices that have the proper hardware (any device that shipped with Android 8+). Only CTS will be affected though, basic integrity will still pass (since it doesn't check the bootloader).
[Magisk] Displax:
Updated Mi A2 Lite

xiaomi/daisy/daisy_sprout:10/QKQ1.191002.002/V11.0.5.0.QDLMIXM:user/release-keys__2020-05-01
[Magisk] estofjlw:
Yeah it was a colon and not a dash . . .

Yeah it was a colon and not a dash . . at ocean:9 - NOT ocean-9

Still did not work however - but the one from the certified fingerprint list did

BUT . . . also Magisk hide was NOT active and configured . . . and so when I fixed that and finally got Safety Net to give two green checks - the IMEI was banned and blocked. The tower no longer will negotiate and serve an LTE signal to that device - but the SIM works in four other devices just fine and back in my version 9 phone

I think because it was Android 10 originally as a google/coral/ xxxx fingerprint it did not trigger anything until the mixed fingerprints kept showing up someone figured it was a rooted device

That is why you buy a cheap tester phone to flash a ROM to - so the next one I will be sure and keep off the network until I pass integrity and CTS through a wifi connection first
[Magisk] CobalTitan:
Deleted
[Magisk] Didgeridoohan:
I am fairly sure that you have posted this in the wrong thread. You might want to try again in the proper place...
[Magisk] Didgeridoohan:
Yes, that would cause an issue. I should have caught that... With that small change the print passed perfectly when I tested.

That is the first time I have seen anyone report that their device gets IMEI blacklisted with their provider if they don't pass SafetyNet. Are you absolutely sure that this is what's going on? Sounds rather improbable...
[Magisk] CobalTitan:
Sorry
[Magisk] Didgeridoohan:
[MENTION=8483170]estofjlw[/MENTION] That was very informative. Thank you. And yes, now that you mention it, even the terms of my provider has stipulations that in theory could be used for this under some circumstances, although very unlikely (we have very strict laws when it comes to surveillance).
[Magisk] kontini:
[MENTION=4667597]Didgeridoohan[/MENTION]

I have a Lenovo Tab 4 10 Plus. Can you test this fingerprint and maybe add to your list?

Lenovo/LenovoTB-X704L/X704L:7.1.1/NMF26F/TB-X704L_S000056_181015_ROW:user/release-keys

In lineageOS I pass CTS profile check if I set custom prop ro.build.version.security_patch to:

2018-10-01

Further details:

Manufacturer=Lenovo

Product=X704L

System.model=Lenovo TB-X704L

Mine is X704L (LTE) but there are other variants like X704F (WiFi only)
[Magisk] thecosmicone22222:
Please help I did everything correctly and past the safety check but now my phone wont charge
[Magisk] Didgeridoohan:
That sounds strange...

More information is needed though. Does it stop charging after you install Magisk, or after installing the module, or after setting up a device fingerprint or a custom prop?

What's your device, Android version, custom ROM or stock?

Stuff like that.

If you need help it is always a good idea to include as much information as possible. And logs are also a good idea (in this case probably a logcat when you connect the charger). Here's a guide on bug reporting/asking for help:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] Didgeridoohan:
This print doesn't pass CTS when I test it. Are you sure it's correct (no typos)?
[Magisk] kontini:
I'm not seeing any typos. Only I read a comment in build.prop: ro.build.product is obsolete; use ro.product.device

Anyway Can you try the same for X704F?

Lenovo/LenovoTB-X704F/X704F:7.1.1/NMF26F/TB-X704F_S000056_181015_ROW:user/release-keys
[Magisk] Displax:
Updated Xiaomi Mi A2

xiaomi/jasmine/jasmine_sprout:10/QKQ1.190910.002/V11.0.10.0.QDIMIXM:user/release-keys__2020-05-05
[Magisk] thecosmicone22222:
I turned on Android debugging and ist charging now but It takes like 4 hours instead of 2 hours now which would be fine but it only charges at this rate while powered of. When on it gets 1% every 15 minutes. I dont know when it stopped charging but I realized after I set up the device fingerprint. I would think it was sometime after installing busybox/ your module. I have a Galaxy s8+ Android 10 also on lineage os. I also noticed that before I turned on Android Debugging my phone was saying plugged in cannot charge at the moment but toggling ADB on and off fixed that. Im gonna try and get a logcat and link it if I can.

---------- Post added at 05:09 PM ---------- Previous post was at 04:40 PM ----------

oh shoot xda wants me to send 10 messages before I can link anything but i have the log now

---------- Post added at 05:16 PM ---------- Previous post was at 05:09 PM ----------

Is there any other way I can send it to you?
[Magisk] Didgeridoohan:
[MENTION=10841985]thecosmicone22222[/MENTION] honestly, I don't think either Busybox or this module has anything to do with that. Sounds more like a battery that's on it's last legs...
[Magisk] Mysticblaze347:
So I am stuck on 7.0 for full root ability and yet would like to try Google cams night sight. However it for 8.0+.

I know OS and build ect. can be changed to mimic, but it messes up whole system if I do. Need to fake even for an install to happen. Is there a way that libs can be faked for the app to still think it's 8.0 + and yet open and work properly after install? Everything else still needs 7.0 to run properly. This would be amazing and a sweet work around for everyone who is in same boat as I. I have been willing to check lineage, but no one will say if they are all ARB free or not.