yashsingh1/xdaforums huggingface dataset:
[Magisk] OhioYJ:
You've never changed your device finger print for other reasons? You might not see the need, but others might.
[Magisk] toolhas4degrees:
The only reason for this is to fix fingerprint issues from rooting IMHO. That's why I don't believe you "need" it anymore
[Magisk] J0nhy:
Well people might find it useful still, I'd love to see this project back alive again, it's great for spoofing your phone
[Magisk] fleamour:
& in order to hide “root” you have to root. Some people, shock horror, use Google Pay
[Magisk] immortalwon:
Is there a way to use this module to passs safetynet / cts check on an emulator, specifically LDPlayer 9?
[Magisk] toolhas4degrees:
STRPxSPOOFER

▌Change Ur Current Device To Any Other High End Device Listed In This Module Easly !▌Over 22 High End Devices Added!Powered By Stratosphere!

www.pling.com
[Magisk] J0nhy:
That doesn't have as many devices as hideprops and there's not newer devices
[Magisk] toolhas4degrees:
There are no updated fingerprints for hide props. These are current where is OnePlus 10 pro in hide props. Is this guy requesting new props from every build like the old dev was? Bc I don't see it. And the outdated props under a12 serve no purpose anymore. Don't see anyone running a11 custom roms anymore and if so they would use the original hide props.
[Magisk] OhioYJ:
I have several devices running actively maintained ROMs older than A11 actually. Due to the fact that they are older devices. Instead trying to convince people of your opinion that this is not needed, when many people obviously still use it, perhaps, you could offer suggestions on how to work around these issues:

The original hide props has documentation on how to add custom values (add your own updates) to the list:

Essentially you just add a file called printslist in the root directory of your internal storage, with the fingerprints you want to add:

Here is an example from some that I have (and submitted a long time ago):

Samsung Tab S2 SM-T813 (7.0):samsung:SM-T813=samsung/gts210vewifixx/gts210vewifi:7.0/NRD90M/T813XXS2BSJ3:user/release-keys__2019-08-01
Samsung Tab S5e SM-T720 (9):samsung:SM-T720=samsung/gts4lvwifixx/gts4lvwifi:9/PPR1.180610.011/T720XXS1ASL3:user/release-keys__2020-01-01
[Magisk] toolhas4degrees:
I haven't tried to convince anyone I stated my opinion get over yourself. Also you could use older version if on a11 like I said before.

Also advanced reset props module fixes cts fingerprint issues in OEM rims and you can use hide list to hide gms stable and gms unstable and will pass fully. I'm sorry you don't know what you are doing and rely on old stuff.
[Magisk] fleamour:
.

Could you link a guide for the uninitiated?
[Magisk] toolhas4degrees:
This is not my thread non do I wish to derail people who are here for this. But if you are interested in going about things in other ways. Look to magisk delta and the developer of it for the uses I listed. Also spoofing is just edited the build props that you can do in a magisk module using the reset prop function. All you need is the info of the device you are trying to spoof to. Ex pixel 6 you need fingerprint and build props from a pixel 6 device. You can download firmware for any device then extract their build props to see their values.
[Magisk] soulpower11:
Looks like the link is dead again
[Magisk] ipdev:
@fillwithjoy1

Attached (current) Pixel props.

Hope it helps. 🙃

Cheers. :cowboy:
[Magisk] viperfan7:
Anyone have ae download link, looks like the link is dead
[Magisk] Fellipazo:
Look the discord link, there are 3 versions (stable, nothing inside; Experimental, a lot of things; and beta, 7.01 is the latest 4 months ago)
[Magisk] ibrahm24:
A few days ago I was told to download from telegram because the xda link didn't work, now from discord. what has become of xda, this community is so dead. . .
[Magisk] immortalwon:
It's a reflection of the bigger problem occuring right now with humanity. We are moving toward fascism globally and people are checking out
[Magisk] rodken:
It's not the community.

-- Most folks are not willing to adopt to another medium such as Discord or Telegram for the sake of.
[Magisk] dllud:
Here follow the current links. (@vithuselservices posted them on Discord.)

Download Repository

MHPC Releases & Archive

Source Code

Vithurshan's GitLab
[Magisk] devnoname120:
For future visitors when the links inevitably become dead again, you will find attached a mirror of MHPC-v7.0.1-beta.zip.
[Magisk] fleamour:
How does it run? Daily driver ready?
[Magisk] rodken:
It behaves in the same fashion as its predecessor.

I've been running it for the past two weeks without any issues.
[Magisk] fleamour:
Can I flash atop/upgrade last version?
[Magisk] fleamour:
Working fine here!
[Magisk] fleamour:
Could we borrow code to update from within Magisk Modules interface like Shamiko & Universal Safteynet Fix?
[Magisk] Prattham:
Does this has device list with android 13?
[Magisk] OPO13R:
This may sound rude, but I don't see any advantages over the original repo. The device list ist still outdated (= doesn't support Pixel 7..) and it doesn't offer anything more than the original repo.

I would be pleased to be proven wrong.
[Magisk] neelchauhan:
On LineageOS 20, I don't need this on a Pixel 6 and 7, and OnePlus 11 with an unofficial LineageOS image. LOS has shifted to using the device fingerprint which makes it easy to hide root.

I don't know about other ROMs however.
[Magisk] DuMoGu:
I don't know what the problem is.
[Magisk] rodken:
Are you getting the same results when using MagiskHide Props Config v6.1.2?
[Magisk] DuMoGu:
Actually, I only found 7.0.0 and 7.0.1 on the download page
[Magisk] rodken:
The link to the original thread is located within the OP.
[Magisk] wakkaday:
does this work on pixel 7a

and anyway of confirming the device is changed?
[Magisk] wakkaday:
Do I save this file as it is? Any name changes and save in root folder?
[Magisk] jean019:
I have the same sort of errors with 7.0.1 beta on Derpfest android 13 for Mi 12T pro.

I tried to modify ro.config values (volume steps) but after validation it doesn't change anything.

On the contrary, the old 6.1.2 is working (I have to add "su" before starting "props" under terminal)

edit : but not sure about google play certification now...
[Magisk] psycl9n:
deleted
[Magisk] htc_softbank:
Was this project removed? All of the links in the OP are dead
[Magisk] dcarvil:
I can't answer your question, but the original project is still available at https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf. It has not been updated for some time, but is still useful in some circumstances.
[Magisk] htc_softbank:
Ah, thanks for the link. I already tried this and it doesn't appear to be compatible with lineageos 20 {android 13).

When I tried this module and some of the fingerprints, it was successfully applied, but the Samsung app still detected my modified OS.

I also thought this fork was v7.0, while the original project was the 6.x versions.
[Magisk] kalsta:
Does anyone have a fingerprint for stock Samsung Galaxy Z Fold5 EU/AU variant (SM-F946B) running Android 14?

This is probably the wrong place to ask but I figured I'd give it a shot. Cheers, Kal
[Magisk] 8y73:
All links are dead.
[Redmi Note 10 Pro] mohammedmetto:
my

Fingerprint Security is missing any help​
[Redmi Note 10 Pro] gazza35:
Usually vanishes from settings if theres a hardware issue with sensor, common issue on chinese phones, plagued the Huaweis. Are you running stock Miui or a custom rom on a rooted device?
[OnePlus 9 Pro] sumfahg:
Of the various ROMs available for the OP 9 Pro that are running A13, what's everyone's favorite and why? Currently looking at StagOS, PixelExtender, and Paranoid Android, but not really sure what the respective pros and cons of each are.
[OnePlus 9 Pro] N1ldo:
Oficial Beta 2
[OnePlus 9 Pro] Jonaathaan19:
I havent tried any of the A13 custom roms since im waiting on some features to get added. But i have tried the A12 versions and my favorite so far is the blissRom. Its has the most features that I am looking for and I had the least amount of problems on that rom.
[OnePlus 9 Pro] Psk.It:
I am on Xtended using microG - even if it does not supports sign-spoof

I also tried COS but ... custom is better for me
[OnePlus 9 Pro] davyleggend:
Yes, I really like the A13 Official. Looks like the A12 was a test for this 13. I love it.
[OnePlus 9 Pro] Stogie87:
I would really like to see the official riceDroid rom for our device in the forum.

This is the best rom i ever used and has very supportive developers, but unfortunately we got only some unstable A12 releases for it and no release for A13 so far... :(
[OnePlus 9 Pro] sumfahg:
If you don't mind me asking, what do you prefer about the official OOS13? Is it just more stable than all the custom alternatives?
[OnePlus 9 Pro] Psk.It:
View attachment 5746707

crDroid Android - Browse /lemonadep/9.x at SourceForge.net

Highly customizable Android Platform

sourceforge.net
[OnePlus 9 Pro] Stogie87:
But this is crDroid and not riceDroid!
[OnePlus 9 Pro] Psk.It:
You are right, I misread

sorry
[OnePlus 9 Pro] N1ldo:
Hi, of course, I've been using beta 2 since launch and I come from beta 1, just so far I haven't noticed any problems, zero. I got tired of trying out custom roms, several of them, and I never had a lack of bugs, in addition to problems with excessive battery consumption. Anyway, after trying several different roms, definitely the best and least problematic and the original to use daily. (but attention, I'm just curious and I like to fiddle around on the phone, I'll always try it again, just because I like doing these things, it's like a hobby for me)
[OnePlus 9 Pro] sumfahg:
How does battery life compare?
[OnePlus 9 Pro] N1ldo:
Stock Rom I spend the day listening to music on YouTube or Spotify (always with the screen off) I get home around 5 pm always with more than 50%. Custom Roms always under 30%.
[Google Pixel 7 Pro] thomashacked:
Hello. I have come from the Samsung One UI to the new Pixel 7 Pro, on the Samsung One UI the settings gear used to be one of the first you saw when you drew down the notification bar, is it possible to have the same on the Pixel 7 pro, cause as now I have to pull down twice to see it and that is pretty annoying.
[Google Pixel 7 Pro] joshtb86:
Following
[Google Pixel 7 Pro] simplepinoi177:
not that my suggestion is a solution or anything, as I wish it was easier to get to the Settings as well...

but in case it wasn't known, if you pull the notification down with 2 fingers, it brings it all the way down, so you don't have to pull down twice....

clearly very difficult to do this one-handed, so obviously not really a solution...but more of a workaround until OP or someone finds a satisfactory solution...

just wanted to mention this little bit for general knowledge spreading...
[Google Pixel 7 Pro] roirraW "edor" ehT:
Can't move it, but other than the above mentioned workaround, you can do other things like put a Settings icon on your home screen, or using a custom launcher like Nova, designate a gesture to open Settings such as two finger rotation clockwise.

Matter of fact, I might designate that right now.
[Google Pixel 7 Pro] thomashacked:
YEa I am using nova launcher, so will see, but stupid that they did it that way google.
[Google Pixel 7 Pro] jaseman:
At first I didn't like it either but think of it this way... you have one hand available, you swipe down twice with your thumb, and with one hand you can now reach the settings button. If it was at the top you probably would not be able to reach it with one hand unless you have Pro basketball size hands with llllooooooonnnnnnnggggggggg fingers!
[Google Pixel 7 Pro] Psychlone:
I 'walk" the shade down using my index and middle fingers.

Because I use Nova, the default gesture to open app drawer is two-finger swipe down, and I use that often, so my personal workaround is to 'walk' the shade down with 2 separate fingers in 2 separate swipes, but it's quick. Otherwise, two-finger pull down from the top edge does indeed pull the shade all the way down.

I like Rode Warrior's idea of a two-finger clockwise gesture in Nova though, I'll give that a spin (pun intended?)
[Google Pixel 7 Pro] roirraW "edor" ehT:
It's super quick to get into Settings this way, that's for sure.

😂 I like it!
[Google Pixel 7 Pro] benzwirs:
pull down from the top, right bottom corner is the settings icon.

or put your home screen on 5 rows and put it in there.
[Xiaomi 12 Pro] mazensameh100:
I'm asking about Haptic feedback, It's not supported in pubg

Is there someone playing Asphalt 9 to tell us Haptic feedback supported or not?

Is there any solution for pubg?

Thanks in advance
[Xiaomi 12 Pro] GaM3R_HuB:
I have the similar isuue, if someone finds a way to bypass this,answer this comment
[Samsung Galaxy A02s] Eco24:
Hello recently I tried to root my phone, wanting to fix ghost touch, I did something wrong and the phone stopped working, "Only official binary blah blah blah ..." popped up during startup, I decided to reinstall the official stock, the phone started working normally, even ghost touch repaired, I looked at the Root Checker application if I have root, it turned out not, which is all right, but when I want to add the card to google pay or open McDonald's applications, I get a message that the phone is rooted or was somehow rooted modified, what can I do in such a situation, please help me, I tried to install other stocks from other operators and restore the phone to factory settings: _ (
[Samsung Galaxy A02s] Eco24:
I saw one solution, probably in this forum where someone wrote to enable OEM Unlock and USB Debugging then disable and enable again, something like this, but I don't see OEM Unlock in the developer option, I know that with a failed root attempt, I somehow unlocked this option, but I don't remember how and I prefer someone to help me as best as he can, because I don't want to break anything anymore, I just want Google Pay to start working for me
[Samsung Galaxy A02s] syonox:
OEM is probably hidden cause your device isnt older than 7 days. Connect to wifi and enable automatic time and date, than disable once done set the date atleast 7 day forward and oem should appear but you will have to lock ur bootloader before you disable oem and if you are running a custom firmawre make sure to backup data if you wanna go to normal firmware
[Samsung Galaxy A02s] Eco24:
But I use official firmware from some Samsung firmware site, i think my bootloader is locked, anyway do you have any solves to make work google pay?
[Samsung Galaxy A02s] Eco24:
I tried to unlock OEM but this solution with data & time doesn't work for me.
[Samsung Galaxy A02s] Eco24:
Hey, when I go to Google Play Shop there is an information that my device isn't certified, I tried to register my ID Device and still doesn't work can It be a problem, because of that Google Pay doesn't work?
[Samsung Galaxy A02s] Eco24:
If i wait 7 days OEM option should unlock automatically?
[Samsung Galaxy A02s] Eco24:
Is it good idea to root this device correctly and use magisk to make google pay work good or for example root this device and then unroot to make work google pay?
[Samsung Galaxy A02s] syonox:
before you do this if odin says you are in custom mode backup all your data before doing this. no it wont automatically, first you have to go to odin mode and hold up for a bit until the screen shuts and shows the question (do you wanna lock your bootloader) you select yes once done if you are on custom it will bring up only odin mode before anything thats where u flash firmware, now that should get rid of the root, and then if u wanna disable oem connect to wifi disconnect date and time unselect automatically and go 7 days ahead and the option will appear.
[Samsung Galaxy A02s] Eco24:
How to check if i have custom mode and what i have to hold up?? please explain better because i don't know what i have to do
[Touch Dual, MDA Touch Plus General] loco09:
Hi All!

I update my touch dual with the original rom of htc (wm6.1).

After updating i restore in normal mode the spb-backup file.

after this i see that in my SMS inbox i got a message that named:

"Konto gesperrt. Aufgrund von Firmenrichtlinien..". so it is not possible to receive and send sms/mms/email

hope anybody can help on this issue

B'R'
[OnePlus 10 Pro] shahidmjd:
hi,

i was trying to root a oneplus 10T 5g phone but somehow it got stuck at fastboot mode, device is oem unlocked.

i see following error while manually loading.

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

FAILED (remote: 'Flashing is not allowed for Critical Partitions.

thanks in advance.
[OnePlus 10 Pro] dlads:
Sounds like your bootloader isn't unlocked.
[OnePlus 10 Pro] shahidmjd:
It says boot loader is unlocked.
[OnePlus 10 Pro] dlads:
What model do you have?
[OnePlus 10 Pro] shahidmjd:
It is one plus 10 T 5G 2417 model
[OnePlus 10 Pro] dlads:
I never had to do this but you could try.

fastboot flashing unlock

then

fastboot flashing unlock_critical
[OnePlus 10 Pro] shahidmjd:
I did use unlock critical command but it says device is already unlocked.
[OnePlus 10 Pro] dlads:
Also bare in mind this is the 10 pro forum.. you'd be best making a thread in the 10T section..

They are a little different, I've not witnessed anyone have this issue before.
[OnePlus 10 Pro] dlads:
That's odd.. I've no idea buddy, ask in your actual forum..
[OnePlus 10 Pro] filjusz:
reflash stock
[OnePlus 10 Pro] shahidmjd:
Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot flash abl abl.img

Sending 'abl' (179 KB) OKAY [ 0.006s]

Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.

')
[OnePlus 10 Pro] hosthere247:
Try booting into fastbootd before running those commands, run.. fastboot reboot fastboot

EDIT: Some Oneplus phones do not allow flashing partitions that would be seen as critical within the usual fastboot mode, only fastbootd.. Maybe this is the case for the 10T
[OnePlus 10 Pro] shahidmjd:
platform-tools_r33.0.3-windows\platform-tools>fastboot reboot fastboot

Rebooting into fastboot OKAY [ 0.000s]

< waiting for any device >

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
[OnePlus 10 Pro] hosthere247:
I hate to say this, but I think your phone might be bricked.. I would suggest trying to flash the stock boot.img, and also the none critical files for your device within the bootloader / normal fastboot if it allows you to and then try to rerun - fastboot reboot fastboot, to boot into fastbootd.. My 10T is currently fully bricked.. The Whole EDL nonsense is ridiculous.. The OnePlus Chat Support said remote support could be available for me.. Which is usually unheard of.. Especially seeing as they want to keep their EDL tool and files from prying eyes.. I just want my device back, nothing else.. I would even be willing to leave the room, while they do their work.. They will probably blank my screen until the restore is successful.. They will probably reply to me in a year from now knowing OnePlus.. 😂

Just remember to make sure that you only flash the boot.img and none critical files for your current firmware and region... Otherwise.. It could end badly..

I understand I am encouraging something and engaging in something that is off-topic for this device section.. However I hope what I have said can possibly help you.. Not having a phone really sucks.. And I have gone the entire day without one..
[OnePlus 10 Pro] harty1193:
I know this is too late. but I somehow fixed it when I ran into the same error.

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

It was not booting to UserSpace. So I was in Slot b and changed to Slot a.

>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.047s]
Finished. Total time: 0.050s

Then I could boot into UserSpace.

>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 31.695s

I am able to flash everything now.

>fastboot flash abl abl.img
Sending 'abl_a' (1996 KB) OKAY [ 0.050s]
Writing 'abl_a' OKAY [ 0.020s]
Finished. Total time: 0.086s

Thanks
[Xiaomi Poco F4 (Munch) / Redmi K40S] chihirofujo:
Heya, I wasn't sure whether to put this under Theming, it is half a question and half a list of my discoveries

I'll be putting em here in hopes of better code nerds figuring out the language this thing speaks for custom boot logos

Tl;Dr is I'm trying to get custom boot logos to work on my F4, everything I could gather is below.

Compared to the normal process of there existing a file like splash.img or boot.img as you would find in a F2 Pro or F3, the F4 has neither

To be more specific, there exists a device partition in /dev/block/bootdevice/by-name/splash, which is a few symlinks to the actual device /dev/block/sda20

However, trying to dd sda20 results a 34MB file of naught but zeroes, viewed in a hex editor it is completely empty.

My guess is this stems from the Virtual A/B partitioning and whatever new boot scheme the peeps what enginerded this thing came up with, making /dev/block/ obsolete.

Side note, I did attempt flashing a logo.img made with the K30 Util (download below) with:

fastboot flash splash logo.img

Also tried flashing a splash.img made with a barebones Splash util (again, download below), ran:

fastboot flash splash splash.img

Both cases succeeded in flashing but the logo didn't change, completely ignored it and booted normally. Didn't even brick the device. The nerve.

Half question, half Theme, can anyone help me figure this out?

Links:

K30 Logo Utility (GDrive, 7z, credits to Pzqqt and Gokul NC)

Splash Logo Maker (Generic)
[Xiaomi Poco F4 (Munch) / Redmi K40S] NOSS8:
I also tried on my Xiaomi 12 pro without success while on the F2 pro no problem.

This is probably due to partitions A / b but especially that the partitions at the level of this sector is write protected.

.\fastboot flash logo_ab logo.img not working.
[Xiaomi Poco F4 (Munch) / Redmi K40S] nillkigger:
helo im chiense,

i belicve this is cause by xiaomi protectoing the splash image partitont on a/b phone z

hope this help!! :)
[Xiaomi Poco F4 (Munch) / Redmi K40S] alfZKI:
What about flashing from fastbootD? Will it works?
[Xiaomi Poco F4 (Munch) / Redmi K40S] sachin karinki:
Hello guys, does any of you have a stock boot splash/logo mod without unlocked logo/text, which is working for poco f4 ? (I need this to hide my bootloader unlock status from bootsplash screen, so that in case of device brick, service center guys will not know its unlocked by just looking at it )
[Xiaomi Poco F4 (Munch) / Redmi K40S] NOSS8:
Unlocking the bootloader does not void warranty.
[Android Apps and Games] me7tarfeek:
Does not work on Z Fold 4… Closes before it starts..
[Android Apps and Games] Nx Biotic:
Il definitely investigate the issue
[Android Apps and Games] Badger50:
I get the same issue on my Pixel 6 with the test version. Thank you.
[Android Apps and Games] Nx Biotic:
Update 1.12 published

-Fixed an app breaking bug that tried to find resources that did not exist on some firmware platforms for a material component text style

-Reworked the Firebase authentication login

-Fixes to the avatar view

-Fixes to the popup view and bottomsheet view for Android 13 (Might still be some style issues yet)

-Deeplinks for Terms of Service and Privacy Statement now properly functioning

-Removed License Validator for a homebrew Demo Mode

DEMO MODE

-Demo Mode is active if Carpenter is side loaded as an apk to your device. It simply detects if Carpenter was installed by the user or by Google Play. If by Google Play, All Features are properly unlocked. If sideloaded, "Priority" Features will be locked out but allow the user to tour the application. Major firebase functionality disabled.
[Android Apps and Games] Nx Biotic:
Issues have hopefully been resolved
[Android Apps and Games] Nx Biotic:
Updated OP with DEMO APK Link and some extra deets from the latest update