can you create build.prop of other devices

[Emieanderson]

can you create build.prop OR Spoofind module for magisk and KernelSu of other devices like Oppo Vivo Xiaomi Poco Redmi Samsung Motorola Meizu Asus Infinix Realme Nubia TECNO HUAWEI HONOR Lenovo Lava Nokia OnePlus Itel IQOO also spoofing features like - fake location, random android device id change , IMEI , Mac Address , Fake Sim Card info (like country iso, operator mcc+mnc, operator name. sim sub id, sim serial) , framework id (GSF ID) , Baseband Version.

so we could bypass Device Ban from some apps.

[0x11DFE]

The project aims at building Pixel props, You can always fork it!

[0x11DFE]

Actually nevermind since we now can dump the images with literally no issue, I could focus on doing so?

[Emieanderson]

thanks so when we get update or new project

[skupjoe]

Is it correct to say that for non-Pixel devices we should use sensitive-props-v6.5.0-60507-release.zip?

How about Pixel devices using LOS/crDroid roms? Use the Pixel-based build.props module for the respective device, or use sensitive props module? Or both?

[skupjoe]

Oh, I re-read the readme, I think this module covers both then?

---

Integrated Sensitive Props Mod Features:

• Incorporates all Sensitive Props Mod features and disables them if the standalone module is also present, avoiding conflicts.

---

[0x11DFE]

Oh, I re-read the readme, I think this module covers both then?

---

Integrated Sensitive Props Mod Features:

• Incorporates all Sensitive Props Mod features and disables them if the standalone module is also present, avoiding conflicts.

---

The initial issue was about having such a project for non-Pixel devices, e.g Samsung, Huawei etc..

In theory it is possible to achieve but without much benefits as in doing so, and i myself didn't have enough time to polish this current project so that i could try to find a way of automating the download and dumping of other phone brands.

Then as i could guess not all phone images are built/made the same way and it could be a fairly long route until i figure a proper automated way of handling build.prop for all phone brand OTA images.

Talking about sensitive props, it was made because some custom ROM's don't really care about hiding the fact that they are custom Androids and so they might be flagged by Google or some third party root detecting apps running on your system.