Develop Bugs

Buildprop editor

Hello guys
i konw that it seems that it is a duplicate thread, but im facing a different issue now, i came back to stock (At&t) optimus g pro E980 rom and as i did before i rooted it but to get the network preferred menu in the network settings to change between WCDMA and GSM and LTE i installed the (Buildprop editor) and changed the (ro.build.target_operator) from (ATT) into (OPEN), and i have tried this before and it worked just fine, but now it takes the superuser permission and it reboots but the value (ATT) keeps coming back and the editor doesnt save me new editing, i read many threads and i have installed ES Explorer and change the boot Explorer from the side menu and also gave the (mount R/W) for all the options above, and also it doesnt work and the editor dont save my changes and when i reboots all the old values are coming back,,,,
What can i do?

Setup adb on your pc, then:
- adb root -> give root access to ADB
- adb remount -> remounts system as read-write
- adb pull /system/build.prop -> pulls build.prop from your device to your PC
- find value, change it and save file
- adb push build.prop /system/build.prop -> pushes back file to system
- adb reboot -> reboot to make changes valid
Don't forget to allow both apps and ADB root access in developer options, if you're running something CM based OFC, your phone needs to be rooted for this to work.

Thanks shady but it looks like it is a complicated process specially if i wanna keep switching between the network modes, previously i did it smoothly with the same builtprop editor and i got the preferred network modes menu, but now it is not saving, so there should be a reason for that, i will keep searching and waiting for other members opinion
Thanks again

Well, probably app can't remount filesystem or something goes wrong, take a look at logs. This is the way I prefer to do things - it's easier than typing on the phone and it's error-proof.

Finally i got a logical answer for my issue and it worked just fine
Follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1193245
I simply followed the exact instruction for the ES root explorer
Have a nice day
Sent from my LG-E980 using xda Forums PRO

net.tethering.noprovisioning=true now counts towards tethering? VZW

I've been using this trick added to build.prop for a while now and it seems that with the latest update (oct), that it now is counting towards the tethering limit on my plan. I just received a text stating that I was within 10% of my 15gb limit when it never counted previously.
Is anyone else experiencing this? Are there any alternative solutions out there?

I am still on Grand fathered unlimited and just did the build prop today and it worked for hot spot, I am on the Sept update. Curious to what others say. I am trying to decide to go to the new plan or not, lately I only use about 20 gb and that is a heavy month
Sent from my Pixel XL using Tapatalk

coolhandz said:
I've been using this trick added to build.prop for a while now and it seems that with the latest update (oct), that it now is counting towards the tethering limit on my plan. I just received a text stating that I was within 10% of my 15gb limit when it never counted previously.
Is anyone else experiencing this? Are there any alternative solutions out there?
Click to expand...
Click to collapse
Tethering always counted for data usage. What you're referring to just skipped the check if it was on your cell plan and let you tether without it. It should have only applied to old, grandfathered unlimited lines for Verizon.
Sent from my Pixel XL using Tapatalk

I know it counted against my data, but it didn't previously count towards my tethering data limit. Does that make sense? I have unlimited data, but 15gb high speed tethering limit.

Well I discovered that if I have wifi router as a repeater, repeating the hotspot. Then connect to it via Ethernet with my raspberry pi Kodi box. That the video streamed is not counted towards my tethered data. No clue why.

Brown, are you positive about that? I just noticed that Verizon started seeing tethering on my rooted N6 with build,prop provisioning=true last month. First thread I could find about it was here...
https://forum.xda-developers.com/lg-g2/help/verizon-hotspot-provisioning-t3672546
My wifi router uses the phone as its WAN and prior to last month Verizon couldn't tell my data was being tethered (but they did see the data usage). So now I will hit the tether limit at 15 gig unless someone that understands how it all works can find a way around it.
I was on the old grandfathered unlimited plan and switched to the new unlimited plan. The first month I went way over 15 gig and they didn't see any of it (by checking the verizonwireless website), but now into the second month they are seeing every bit of it.
I don't think this is phone or ROM related as I see the same thing on multiple phone types with different rooted ROMS, it's Verizon that is noticing it somehow.
If anyone can solve this, you will be my hero.

besides editing build.prop did you enter the other command in Terminal?
.
Tethering Hotspot mod:
On phone using Solid Explorer or similar go to /system and open build.prop in text editor.
On the last line enter:
net.tethering.noprovisioning=true
Save
....
Then
Open Terminal Emulator app
type:
su
enter
settings put global tether_dun_required 0
enter
exit
enter
Reboot
Note:
prior to messing with build.prop copy it and rename by adding .bak extension (build.prop.bak).
Save that file somewhere you can get to in case you hose things up.
If ever you need it, remove the .bak and paste file into /system folder to overwrite hosed build.prop file.

mjrBud said:
Brown, are you positive about that? I just noticed that Verizon started seeing tethering on my rooted N6 with build,prop provisioning=true last month. First thread I could find about it was here...
https://forum.xda-developers.com/lg-g2/help/verizon-hotspot-provisioning-t3672546
My wifi router uses the phone as its WAN and prior to last month Verizon couldn't tell my data was being tethered (but they did see the data usage). So now I will hit the tether limit at 15 gig unless someone that understands how it all works can find a way around it.
I was on the old grandfathered unlimited plan and switched to the new unlimited plan. The first month I went way over 15 gig and they didn't see any of it (by checking the verizonwireless website), but now into the second month they are seeing every bit of it.
I don't think this is phone or ROM related as I see the same thing on multiple phone types with different rooted ROMS, it's Verizon that is noticing it somehow.
If anyone can solve this, you will be my hero.
Click to expand...
Click to collapse
I am experiencing the same thing now. Has a workaround been discovered for this? Exact same scenario as you.

Others have said vpn tether and a vpn connection. It basically routes all hotspot traffic through vpn so they cannot inspect packets. I guess this may not affect TTL tho.

try disable ipv6

You are going to have to change the ttl somehow. I guess they are getting serious and sniffing packets now..

Also might give this a try with Magisk
https://forum.xda-developers.com/showpost.php?p=77371813&postcount=4
Edit: Never mind....does not work with Magisk 17.1

Born<ICs said:
besides editing build.prop did you enter the other command in Terminal?
.
Tethering Hotspot mod:
On phone using Solid Explorer or similar go to /system and open build.prop in text editor.
On the last line enter:
net.tethering.noprovisioning=true
Save
....
Then
Open Terminal Emulator app
type:
su
enter
settings put global tether_dun_required 0
enter
exit
enter
Reboot
Note:
prior to messing with build.prop copy it and rename by adding .bak extension (build.prop.bak).
Save that file somewhere you can get to in case you hose things up.
If ever you need it, remove the .bak and paste file into /system folder to overwrite hosed build.prop file.
Click to expand...
Click to collapse
This made my phone hang at the G logo. Had to do a TWRP restore.
Is there a method that works? I have a Verizon Pixel XL, Oct 2018 Pie, unlocked bootloader with Magisk 17.2 Beta.

jeffshead said:
This made my phone hang at the G logo. Had to do a TWRP restore.
Is there a method that works? I have a Verizon Pixel XL, Oct 2018 Pie, unlocked bootloader with Magisk 17.2 Beta.
Click to expand...
Click to collapse
I made those changes and while I didn't get a bootloop it also didn't remove the 600k tethering cap.
---------- Post added at 10:28 PM ---------- Previous post was at 10:24 PM ----------
firewallgt said:
try disable ipv6
Click to expand...
Click to collapse
How can you do that without the ability to edit or create a custom apn (verizon pixel xl)

After restoring via TWRP, I did not edit 'build.prop' but I did use ADB instead of the emulator app and sent the "settings put global tether_dun_required 0" command. This time it did not hang at the G logo after reboot but Verizon still sees I used tethering so this did not circumvent detection.
I did not edit the 'build.prop' file because I see it exists in two different locations. Last time I edited the one located in '<home>/system_root/system'. There is another one located in '<home>/system'. Which one are you supposed to edit? Unless I'm mistaken, editing the 'build.prop' file is only necessary if you cannot tether. Editing the file is not needed to circumvent detection, is it?

jeffshead said:
After restoring via TWRP, I did not edit 'build.prop' but I did use ADB instead of the emulator app and sent the "settings put global tether_dun_required 0" command. This time it did not hang at the G logo after reboot but Verizon still sees I used tethering so this did not circumvent detection.
I did not edit the 'build.prop' file because I see it exists in two different locations. Last time I edited the one located in '<home>/system_root/system'. There is another one located in '<home>/system'. Which one are you supposed to edit? Unless I'm mistaken, editing the 'build.prop' file is only necessary if you cannot tether. Editing the file is not needed to circumvent detection, is it?
Click to expand...
Click to collapse
Likely just /system/build.prop, I'm on the Pixel 2 XL and I don't have a build.prop in /system_root. It's likely the one in /system_root is symlinked to /system. You can test this with adb shell:
adb shell
su
cd /system_root
ls -al
scroll up and you should see something like this:
lrw------- 1 root root 23 2009-01-01 03:00 build.prop -> /system/build.prop
If it's not a symlink then I would edit the one in /system, save it and check if the one in /system_root updated, if not then I guess add it there as well.

himom said:
Likely just /system/build.prop, I'm on the Pixel 2 XL and I don't have a build.prop in /system_root. It's likely the one in /system_root is symlinked to /system. You can test this with adb shell:
adb shell
su
cd /system_root
ls -al
scroll up and you should see something like this:
lrw------- 1 root root 23 2009-01-01 03:00 build.prop -> /system/build.prop
If it's not a symlink then I would edit the one in /system, save it and check if the one in /system_root updated, if not then I guess add it there as well.
Click to expand...
Click to collapse
I am on pixel xl and no build.prop in system_root here either. Always modded build.prop in system for like last 6 phones or so, but like i said earlier none of the changes worked for me to hide tether from verizon

himom said:
Likely just /system/build.prop, I'm on the Pixel 2 XL and I don't have a build.prop in /system_root. It's likely the one in /system_root is symlinked to /system. You can test this with adb shell:
adb shell
su
cd /system_root
ls -al
scroll up and you should see something like this:
lrw------- 1 root root 23 2009-01-01 03:00 build.prop -> /system/build.prop
If it's not a symlink then I would edit the one in /system, save it and check if the one in /system_root updated, if not then I guess add it there as well.
Click to expand...
Click to collapse
To clarify, the other 'build.prop' file is not in 'system_root'. It is in '/system_root/system'. I have two 'system' directories. The other 'system' directory is a sub-directory of the 'system_root' directory. Here is a post from another member that has the same 'system_root/system' directory: https://forum.xda-developers.com/showpost.php?p=73968882&postcount=172.
Below is what I get for the 'build.prop' file when I run the "ls -al" command on the '/system_root/system' directory and I get the same exact result when I run the same command on the other 'system' directory:
...
-rw------- 1 root root 1862 2009-01-01 03:00 build.prop
...
I decided to take a chance so I performed the ADB commands that I linked to in this post and the "net.tethering.noprovisioning=true" line was added to both 'build.prop' files. Not sure how the two files are linked???
Still reports usage so these edits do noting. I did notice that there is a system app named "Tethering Entitlement 2.3". I'm guessing that is what keeps track of tethering data usage and reporting.

So no way around the vzw throttling looks like guys? Was y'all using VPN and VPN tether???

what about us Tmo users? I want unlimited tether too ;-]

How to use addon.d or scripts after OTA on LOS without ROOT?

I think I already know the answer but you'll never know.....
I am looking into options to use LOS17 in combination with LOS recovery because then it is possible to have OTA updates even when storage is encrypted.
Though, I would like to have the option to use a script so I can remove some system apps, add some stuff to build.prop and remove some temporary files after every OTA.
As far as I know the only way this is possible is to add an a script to /system/addon.d.
Therefor I have tried using adb to push a file, though when phone is not rooted, it is not possible to use adb root and then adb remount rw and adb push.
So here the questons;
- Is is possible to add a script to /system/addon.d, though without root and without TWRP?
- When not; is there another way to run a script after every OTA without root and without TWRP?
Setup:
LOS 17.1 without root, encrypted and locked bootloader

I will answer myself as it seems OR a stupid question OR something else....
But, as already expected, without root en with a locked bootloader, the recovery is the only place where you can do something root-related when the recovery is giving this option ofcourse. LOS recovery, automatic OTA updates and additional scripts is therefor not possible because you can not place or modify stuff in /system (as it should be out of security concerns on non-rooted devices).
Though, @nvertigo67 posted a nice post about this topic. After reading I realised that, as I want to be in control of my phone AND I want to pay something back to our great dev's, I will definitely stick with TWRP and flashing and running scripts myself.
How to install LOS with TWRP, encrypt en relock bootloader can be found here.
Topic closed for me.

I messed it up myself with my modified build.prop settings:
By design adb root command works in development builds only (i.e. eng and userdebug which have ro.debuggable=1 by default). So to enable the adb root command the ro.debuggable=1 line must be in build.prop, which I have set to 0 for CTS reasons.
Unfortunately it seems my banking app is looking for this parm because when set to 1 the app is giving an error message on startup.
So no adb root for me as long as I want to use the banking app.

How to Modify System files in OOS 10?

Hi,
I want to modify system files in OOS 10 but every method just fails.
Root File manager are shows that they delete the app, but it comes back after reboot.
I can delete app in TWRP but when boot up the OS, the app is back there. If I go in TWRP again to that directory the app doesn't exist but OS has the app there when booted up again. So TWRP is also failing me.
Debloater from magisk seem to work and is able to delete the apps but my main problem is that I want to modify build.prop but I can't as of yet. Nothing is able to save changes and it back to original state after reboot.
Has anyone manage to get proper access to be able to modify to system files via file manager or TWRP?

To edit build prop in oos 10 install magisk hide props config and busy box. Then open terminal and type props and choose options to add remove or change lines. Will keep researching and add a working way to change any system file but if it's anything getting put into the system twrp and magisk modules work but removing files and editing by removing bits doesn't seem to work through twrp.
---------- Post added at 02:20 PM ---------- Previous post was at 02:00 PM ----------
Appears you can mount in ADB to edit files and replace bits etc. Using the command " mount -o rw,remount / " without brackets and spaces beginning and end. Not to strong of a user with ADB but if I use the command to move an app to system combined with the mentioned command it lets me make a folder on system and puts the app into system.
So surely you can extract any file from system with ADB and then re insert it while mounted. It's long winded compared to root explorers but with Android 10 system being read only we may have to wait for a new method through root to do this again if ever possible at all.
This doesn't effect the ability to edit any part of the system for the purposes of custom ROMs but makes it near impossible to edit a running/installed ROM in Android 10 (atleast in stock os)

1. adb definitely works for uninstalling system apps. All you need to do is open an adb shell and run the following command,
Code:
pm list packages
pm uninstall --user 0 <package_name>
The list packages command will give you the appropriate package name
I use this myself and can confirm it works. I am running OOS 10 Open Beta 2.
2. I think you should be able to edit build.prop through adb shell. In case you run into /system mounting issues, reboot into recovery, manually mount system and run adb in recovery itself.
I haven't done this myself, so please tell me if it works!

Can't Remove System Apps (even with root priviledges)

I recently rooted my moto G fast (boost) but I'm unable to debloat. Even with root I still can't seem to figure out how to successfully remove system apps from the following folders: /product/app, /product/priv-app, /system_root/system/app, or /system_root/system/priv-app. I've tried running chmod 755 to no avail. The ability to debloat is the main reason I always root so if I can't do that then I don't really see any point in having root at all. I like to be able to freely add or remove apps from the priviledged apps folder. This is far from my first rodeo but I'm not a professional by any means; I still have quite a bit to learn, so correct me if I'm wrong but I'm assuming its because selinux is set to enforcing so I've been scouring the internet looking for a way to set it to permissive and so far nothing has worked. I tried running "su setenforce 0" in both termux and the twrp terminal but neither were successful. I'm also assuming this is the reason I've been unable to install busybox to xbin. I got it to install fine in sbin but I have a couple apps which require it to be in xbin in order to function properly. Any and all advice would be greatly appreciated

Use a third party app in play store to remove system apps.
I recommend this: https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_US&gl=US

mrsiri said:
Use a third party app in play store to remove system apps.
I recommend this: https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_US&gl=US
Click to expand...
Click to collapse
I have been using third party apps. I have SD Maid pro and even that can't remove anything that's in system apps or priv system apps.

What about deleting the files with Root explorer (file manager with root access) ? you can find it on the play store
Otherwise try using adb commands:
adb shell
pm uninstall --user 0 com.useless.piece.of.trash

mrsiri said:
What about deleting the files with Root explorer (file manager with root access) ? you can find it on the play store
Otherwise try using adb commands:
adb shell
pm uninstall --user 0 com.useless.piece.of.trash
Click to expand...
Click to collapse
Did it work?

mrsiri said:
Did it work?
Click to expand...
Click to collapse
Haven't gotten a chance to try ADB just yet. Ive tried using a couple different root file explorers with no luck (I assume due to either selinux or not having BusyBox in xbin) but last night I was somehow able to drunkenly set selinux to permissive and fix the busybox issue (unfortunately I can't recall how lol) so I'm gonna try again with a root uninstaller after work. I realize my efforts are largely pointless since this phone performs perfectly even with the bloat. I pretty much just do this on principal cuz I like knowing I have total control of my device.

AMShiech said:
Haven't gotten a chance to try ADB just yet. Ive tried using a couple different root file explorers with no luck (I assume due to either selinux or not having BusyBox in xbin) but last night I was somehow able to drunkenly set selinux to permissive and fix the busybox issue (unfortunately I can't recall how lol) so I'm gonna try again with a root uninstaller after work. I realize my efforts are largely pointless since this phone performs perfectly even with the bloat. I pretty much just do this on principal cuz I like knowing I have total control of my device.
Click to expand...
Click to collapse
Try the ADB method, I used it once and successfully deleted phone app for trying the pixel 2 method of clearing verizon gray OEM unlock toggle on my G6 Plus, although it didn't help in the end...