Database Info

[Q] Is it possible to flash stock build.prop ??

Sorry for my bad english.
I got a soft brick in my Moto G by changing this line in build.prop
ro.sf.lcd_density=320
for this line
ro.sf.lcd_density=260
My question is if is possible to flash the stock build.prop in /system folder?? Because I didn't make a backup of any picture and I wouldn't like to lose everything.
If it is possible. Would you bring me the .zip file?
By the way, I have this rom in my phone "US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml"

Easy:
1) get stock build.prop
2) adb push c:\build.prop /system
3) Reboot
alternatively to 1) you can
a) adb pull /system/build.prop c:\
b) edit build prop with editor
c) adb push c:\build.prop /system
(had the same problem with density=1320)

MrKra said:
Easy:
1) get stock build.prop
2) adb push c:\build.prop /system
3) Reboot
alternatively to 1) you can
a) adb pull /system/build.prop c:\
b) edit build prop with editor
c) adb push c:\build.prop /system
(had the same problem with density=1320)
Click to expand...
Click to collapse
Where do get the stock build prop from for xt1032 4.4.2?

Hello What if I don't have adb commands to use as i didn't have developer options enabled after factory reset

Unerasable files pushed via ADB

Hi,
I recently pushed a folder (Download) to the sdcard of my OnePlus One via ADB in recovery. Now, I can't delete any of the files inside that folder via any (root) browser.
How can I fix that?
Thanks.

If you are unlocked, install Root Explorer, or the like, and check the directory permissions. Mine is set to 777, and I can delete it if I wish. Or you can change the permission of the files inside, and delete those, as you wish.
There are likely adp commands, as well. Perhaps someone will show with that know-how.

I tried that, though it unfortunately doesn't work via root browser.
I'll try it via adb later today.

adb remount (to gain rw-access to root partition)
adb shell rm -f <path to file> (to delete the apk)

ADB change bluetooth_name not working

Hello,
I am working on a script to provision many android tablets using adb via usb.
The devices all have root access and android 8.1.0.
Some settings I need can be changed using the settings stored in /data/system/users/0/settings_global.xml
i.e.
Code:
adb shell settings put global bluetooth_on 1
However changing the "device name" which is the bluetooth_name stored in /data/system/users/0/settings_secure.xml does not work.
This is the line:
<setting id="218" name="bluetooth_name" value="tablet-99" package="android" defaultValue="tablet-99" defaultSysSet="true" />
Code:
adb shell settings put secure bluetooth_name "tablet-77"
--> this just changes the value and not the defaultValue (how to do this?) ... both settings are reset after reboot
--> changing the file manually via sed/vi is reset after boot
In this thread Cloning Pre-configured Android 8.1 Device / ROM changing settings_secure.xml settings seems to work without problems.
Where else could the setting be stored?
thanks and peace.

[HELP THREAD] blank build.prop file Mi 11T.

Hi,
I was trying to run `adb root` instead of `adb shell su` because when i write something to /system/* dir the files get empty. After that i searched something about it and i see a related topic which contains 'edit build.prop'. Idk maybe i was searching about wrong thing. After that i update build.prop and it just get empty after that i reboot my phone and its staying on MI icon now. What should i do. Is there any way to access shell and replace a default build.prop file.
My Phone: Mi 11T
I tried nothing because after see an empty build.prop file. I just reboot device instead of search something about it.

If file /vendor/build.prop exists, use a copy of it. File default.prop never should get changed / overwritten.
File /system/build.prop should be formatted as UNIX-file, also be RW, hence run the related chmod command.

xXx yYy said:
If file /vendor/build.prop exists, use a copy of it. File default.prop never should get changed / overwritten.
File /system/build.prop should be formatted as UNIX-file, also be RW, hence run the related chmod command.
Click to expand...
Click to collapse
But how can i access shell now. I cant use adb. its not working anymore

Boot phone into Recovery mode: there ADB commands as
Code:
adb pull
adb push
adb shell
are available.

my device shows as unauthorized on adb devices thats why im telling i cant access my device. i removed/replace recent adbkey files but i cant access adb anyway

Then push the RSA-keys what are stored on PC to phone.

Do not mess with system files, Xiaomi doesn't care about props anyway. whatever you want can be probably done systemless.
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
MagiskHide Props Config v6.1.2 Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again. If anyone feels like taking over...
forum.xda-developers.com

SafetyNet on LineageOS 20 microG

Hi guys, I installed LineageOS 20 for MicroG on my Oneplus 6, then I installed Magisk (latest version) through Lineage Recovery and enabled Zygisk and the denylist.
I also installed Universal SafetyNet Fix, but my device doesn't pass SafetyNet attestation test.
What am I missing?
I also found MagiskHidePropsConf module but it was discontinued...
Is there a working method to make banking apps work on LineageOS?
Bye

On my Pocophone F1 at least I don't need magisk at all to pass safetynet. All that is needed is to have USB debugging disabled and to change two lines in build.prop. To do this, you need to pull the file using adb, edit it on your computer, and push the new version. Of course, you have to temporarily enable USB debugging for this to work. On linux, I use the following script:
#!/bin/bash
adb root
adb remount
adb pull /system/build.prop .
sed -i "s/ro.secure=0/ro.secure=1/" build.prop
sed -i "s/ro.debuggable=1/ro.debuggable=0/" build.prop
adb push build.prop /system/build.prop
rm build.prop
the adb commands should work on all systems with adb; the two sed commands just change the lines "ro.secure=0" and "ro.debuggable=1" to "ro.secure=1" and "ro.debuggable=0", and I remove the build.prop file from my pc once it is pushed with the rm command.
Do note that this has to be done after every system update.

nonodie said:
On my Pocophone F1 at least I don't need magisk at all to pass safetynet. All that is needed is to have USB debugging disabled and to change two lines in build.prop. To do this, you need to pull the file using adb, edit it on your computer, and push the new version. Of course, you have to temporarily enable USB debugging for this to work. On linux, I use the following script:
#!/bin/bash
adb root
adb remount
adb pull /system/build.prop .
sed -i "s/ro.secure=0/ro.secure=1/" build.prop
sed -i "s/ro.debuggable=1/ro.debuggable=0/" build.prop
adb push build.prop /system/build.prop
rm build.prop
the adb commands should work on all systems with adb; the two sed commands just change the lines "ro.secure=0" and "ro.debuggable=1" to "ro.secure=1" and "ro.debuggable=0", and I remove the build.prop file from my pc once it is pushed with the rm command.
Do note that this has to be done after every system update.
Click to expand...
Click to collapse
work fine for oneplus 7 pro