Systemless Root change Build.Prop Possible ? - Samsung Galaxy S7 Edge Questions and Answers

Hey guys
Is it possible to change the Build.Prop with Systemless Root somehow because I want to Screen Mirror with my Samsung Smart TV and there is every time this error that leads to no connection and therefore I need to write this line (wlan.wfd.hdcp = disable) in the Buil.prop file that works.

I used BuildProp editor and it shows as having been applied, but I still get the error trying to use Smart View.
Is a systemless root the same as using cf-autoroot?
Update: I made 2 changes to build.prop and at least one of them fixed it.
1. I removed the extra line at the end of the file
2. I changed the last line from wlan.wfd.hdcp=disable to wlan.wfd.hdcp = disable (added space before and after = )

Related

Access all apps from market

I'm not responsible if your phone crashes, bricks, vanishes or display Apple logos, or if you buy apps you can't use because "wrong version".
Also, experimental tweak, don't expect miracles - It is useful for developpers and curious guys ^^
Okay guys, here is a very easy tweak to allow you to display/install (NOT use, most won't work) all apps from Market (your version and all upper), just add the stuff I give below and you're ready to go
What you need : rooted phone, Android (1.6, 2.x.y, 3.x... Stock or not)
File to edit : /system/build.prop
How to edit : Root explorer
How long : 5 minutes (edit, reboot, try)
** Make a backup of your build.prop !!!!!! (Root Explorer will do it automatically) **
1. Root Explorer > Go to /System/ > Long press build.prop and click Open in Text Editor
2. Find the line :
Code:
ro.build.version.sdk=7
Simply edit the value (API Level) according to what you want to display.
Code:
API Level = 7 >> Android 2.1 (Default)
API Level = 8 >> Android 2.2
API Level = 9 >> Android 2.3
API Level = 10 >> Android 2.3.3
API Level = 11 >> Android 3.0
Save and check backup is created, then reboot and try searching apps you usually can't access (ie. for Android 2.1 : Flash Player)
What it will do :
* Display & install apps for your current Android version AND upper versions (ie. if you set API Level to 9, you will see apps for Android 2.1 + 2.2 + 2.3). Dunno if you can display previous versions, but you can try levels 3,4...
* Allow you to get .apk directly from Market (install, then copy apk with Root Explorer)
What it will not do :
* Make the downloaded/installed apps of other versions to work. The apk will come with no icon, service name and will probably crash when you'll try to run it - You can try to patch it with APK Manager. So do not buy apps, you will probably won't be able to use them ! (Check also the version, Market will NOT warn you about the app's API Level)
Hope this will help people to port .apk files from other versions to our old 2.1...
what about device fingerprint?
DooMLoRD said:
what about device fingerprint?
Click to expand...
Click to collapse
I haven't tried, but there are also several strings you can edit in the build.prop... Those *should* allow to change fingerprint.

HOw to disable latest 2.3.6 OTA (root required)

Make a backup of /system/build.prop file
Open /system/build.prop in text editor (one way to do this is via Root Explorer) and locate line that starts from "ro.build.fingerprint"
Edit this line to read:
ro.build.fingerprint=google/passion/passion:2.3.6/GRK39F/189904:user/release-key
Save the file. Reboot. You may be asked one more time to install update but after that you will no longer be asked.
Thanks to user efrant for providing me with this value.
This change makes OTA think you already have this update installed. "Settings/About phone" will still show correct information about OS version that you now have on your phone.
Note that if newer OTA updates are released you will need to edit this line again.
Easier to just "Freeze" DMClient.
If I remember correctly with this update is lost and the super-user recovery.

MIUI 11 Update Notification

OP status for the first time
I just found out you can snooze it just before typing this sentence lol. But is there a way to disable the notification permanently without root?
I don't expect it to survive a reboot but if there is a way I would imagine it being achieved via ADB?
Not a big deal anymore since I just found out you can snooze it for 2 hours but hey might as well finish what I started. If you were wondering my concern is burn in but I think the icons on the status bar move? I would rest better knowing it's not there anyway.
Thanks, I appreciate it.
EDIT: Nevermind I think I did it.
System/System app settings
Then disable "Show update notifications"
EDIT 2: It did not work:laugh:
- With root I used this solution:
Edit the file: system/build.prop
copy / paste the line that contains the version number.
Example: ro.build.version.incremental=V14.3.11.0.PFJMIXM
I have put a "#" for memo and changed v10 to v14 :
Code:
# ro.build.version.incremental=V10.3.11.0.PFJMIXM
ro.build.version.incremental=V14.3.11.0.PFJMIXM
- Without root It may also be possible (to check) to modify this file with XiaomiADBFastbootTools (with the small embedded file manager).
Do I need an unlocked bootloader or root access to use XiaomiADBFastbootTools?
The Flasher, Wiper and Camera2 modules require an unlocked bootloader but everything else works without rooting or unlocking.
Click to expand...
Click to collapse

I cannot edit Build.Prop even with root!!!!

Hello all ,
I've been trying to edit some BuildProp tweaks but I cant edit it also my build.prop goes empty and when I restart the device BAM!!!!! Bootloop I have installed the latest magisk manager I have proper root then why cant I set /system to r/w mode I dont know??!!

Buildprop cannot write changes

Lineage 17 and last version Magisk installed.
Buildprop last version installed.
Buildprop shows SuperUser rights
I want the entry then
ro.product.system.brand
change from samsung to htc
Why? To get the Samsung Wear app working for Watch 3 ...
But I got an error.
Report from BuildProp:
Please ensure the app has root ...
But they are there and are displayed under properties ...
What am I doing wrong?
Problem solved with a workaround.
Finding: You don't need a BuildProp ...
After installing MagisK you have root rights.
As a file manager you take the TotalCommander and give it root rights.
You can then access the build.prop file in the system directory and change it with the integrated text editor.
Just stupid:
My SamsungWear app still does not start.
But this is another story...

Categories

Resources