Related
i want to modify some properties which actually require deletion of a property...my linux knowledge is far less but i understand things quickly...so tell me how to modify build.prop perfectly
I know however to add lines using sh. But what about deletion
PLEASE READ
This mod ONLY applies to UNLIMITED USERS who DO NOT have tethering on their plan
This mod DOES NOT apply to SHARE EVERYTHING plans
I took a peak over at this thread http://forum.xda-developers.com/verizon-lg-g3/help/g3-hotspot-hack-t2812305 and saw that there were issues with using the G2 apk. I decided to take a looksy at it and see if I can replicate the functionality of the G2 apk with out having to re-apply settings to turn on tethering.
I have always had issues using root explores and database explorers messing up permissions and causing boot loops so until I have a proper recovery I use the android terminal emulator. Many people here have had plenty of success using file explores so give it a shot if you like!
Skip down to the bottom for a video walkthrough created by { owenbeals aka DroidModderX}
First things first you will need root!
0.) Start a root shell
Code:
su
1.) mount the system partition for read and write access
Code:
mount -o remount,rw /system
2.) Rename stock files HotspotProvision.apk and HotspotProvision.odex to something memorable. I use .bak and .bakdex
Code:
cd /system/app
mv HotspotProvision.apk HotspotProvision.bak
mv HotspotProvision.odex HotspotProvision.bakdex
3.) Now copy over the new file, can be the root of the extSD card which is /storage/external_SD/HotspotProvisionVzG3.apk
Code:
cp /storage/external_SD/HotspotProvisionVzG3.apk .
4.) The last thing is to change permissions to 644 (RW- R-- R-- for you file browsy types )
Code:
chmod 644 HotspotProvisionVzG3Mod.apk
5.) Now reboot and enjoy your glitch free hotspot action!
You must reboot! Do not try to "install" it, it does not function like that.
N.B.
Some users have noted that their cpu governors change to Performance while the hotspot is on and change back to On Demand when off instead of normal Interactive. This is the stock behaviour of the kernel, and not a bug introduced by this mod.
Thanks to { owenbeals aka DroidModderX} for this handy video walkthrough.
Thanks { Robshr, JayGoat } for bringing this up
Also thanks to { nrage23 } for answering a ton of questions on here
CREDIT:
Guest who started previous thread
Anonymous original creator
WACOmalt for making the original G2 thread
what was glitchy about the first hotspot app? HotspotProvision_24A_mod.apk
rp201 said:
what was glitchy about the first hotspot app? HotspotProvision_24A_mod.apk
Click to expand...
Click to collapse
You have change something every time you use it.
The modded apk works perfectly. I used root explorer to do it though. I renamed the original files, copied your apk to system/app, renamed it to HotSpotProvision.apk, fixed the permissions and rebooted.
Sent from my VS985 4G using XDA Premium HD app
Pretty cool. I'll have to give this a try when I'm bored later on today at work. Could you explain what you actually did to the hotspot apk though?
One thing though - why not just append ".bak" to the end of the existing filename/extension? That way, you don't lose the original extension so you can't forget what it was. It works fine. That's what I always do. In other words, your files would end in ".apk.bak" and ".odex.bak". The system only sees the extension after the final period.
nrage23 said:
You have change something every time you use it.
The modded apk works perfectly. I used root explorer to do it though. I renamed the original files, copied your apk to system/app, renamed it to HotSpotProvision.apk, fixed the permissions and rebooted.
Sent from my VS985 4G using XDA Premium HD app
Click to expand...
Click to collapse
How do you launch tethering after moving, renaming, and re-permissioning the apk? I've tried to launch from Settings app but nothing happens.
The downloaded apk he modded is named differently from the original one in the system/app folder. After I changed the names for the original files in system/app. I changed the name of the modded apk to match the original apk in system/app. I copied the renamed modded apk to system/app, set the permissions correctly, then rebooted. I went into Settings then More... under wireless networks,Mobile HotSpot and changed the SSID and password. I can turn it on via settings or the quick setting in the notification bar.
sstapley_56 said:
How do you launch tethering after moving, renaming, and re-permissioning the apk? I've tried to launch from Settings app but nothing happens.
Click to expand...
Click to collapse
I'd guess for it to work from stock menus (i.e. without starting the apk directly from a file browser app or terminal emulator) you'd have to rename it the same as the stock apk so that the path is the same for the various apps that would call it.
nrage23 said:
The downloaded apk he modded is named differently from the original one in the system/app folder. After I changed the names for the original files in system/app. I changed the name of the modded apk to match the original apk in system/app. I copied the renamed modded apk to system/app, set the permissions correctly, then rebooted. I went into Settings then More... under wireless networks,Mobile HotSpot and changed the SSID and password. I can turn it on via settings or the quick setting in the notification bar.
Click to expand...
Click to collapse
So I have renamed it exactly as the original apk was and rebooted but still no go. On reboot I get a force close of VZWAWSService. I have some of the system bloat frozen, maybe this has something to do with it.
phobos512 said:
I'd guess for it to work from stock menus (i.e. without starting the apk directly from a file browser app or terminal emulator) you'd have to rename it the same as the stock apk so that the path is the same for the various apps that would call it.
Click to expand...
Click to collapse
---------- Post added at 09:36 AM ---------- Previous post was at 09:33 AM ----------
Sweet it's working now, I had the lgmobilehotspot GUI.apk frozen and that's what was causing the issue. Thanks for the apk and tutorial guys!
sstapley_56 said:
How do you launch tethering after moving, renaming, and re-permissioning the apk? I've tried to launch from Settings app but nothing happens.
Click to expand...
Click to collapse
Did you reboot?
There should be no reason to rename the apk. When android installs applications it goes into the /data... Dir as the package name. All intents are handled via package names therefore the apk name is inconsequential.
To use you should be able to go settings > more and see all the tethering options.
To verify placement and permissions use
Code:
su
ll /system/app/Hotspot*
You should see your two backup files and the new HotspotProvisionVzG3Mod.all
Permissions should be rw-r--r--
Let me know if you still have issues.
I will post a DIY response so that people who want to learn about the modification can play along at home. Think of it as source code for this mod:good:
[email protected] said:
Did you reboot?
There should be no reason to rename the apk. When android installs applications it goes into the /data... Dir as the package name. All intents are handled via package names therefore the apk name is inconsequential.
To use you should be able to go settings > more and see all the tethering options.
To verify placement and permissions use
Code:
su
ll /system/app/Hotspot*
You should see your two backup files and the new HotspotProvisionVzG3Mod.all
Permissions should be rw-r--r--
Let me know if you still have issues.
I will post a DIY response so that people who want to learn about the modification can play along at home. Think of it as source code for this mod:good:
Click to expand...
Click to collapse
Thanks for the detailed response, I got it working now. I had previously frozen some of the bloat on the phone when I got it and one of the apps I froze was the lgemobilehotspotui.apk which is needed to work correctly. Thanks for all the help from the awesome devs here.
Nice work, thanks. I just installed it with Root Explorer, and it worked perfectly. Just have to do it to the wife's phone, now.
Well done. Working great!
Thanks! Works perfect. And now I can use the toggle on the drop down menu to activate the hotspot. Thanks so much.
Worked
Worked perfectly for me. Used ES file explorer to move the files around.
I have downloaded, changed permissions, changed the file names to .bak but when I try to install the nodded split says application not installed. I'm using root explorer. I did have the othe mod installed and deleted it first. Wondering if that is the problem
Edit...Stopped trying to install and just rebooted and it turns on just fine, and my laptop connects...the app shows it connected and listed as an approved device...yet I'm not able to actually get a a connection.
Sent from my VS985 4G using XDA Free mobile app
Thanks! Works like a champ.
works great!
I'm also getting the VZWARSService has stopped message, and when I go into settings and turn on the hotspot, nothing happens. If I go into mobile hotspot and turn it on from there, I get this message: Unfortunately, com.lge.mobilehotspot.ui has stopped. Followed the directions exactly, so I'm not sure what's going on.
Works perfectly. I used Root Explorer to rename and move everything. Thanks!
Worked like a charm the only thing is still changes the cpu governor to performance the g2 one did it to I don't know if someone is able to fix that
It's just when I turn on the hotspot afterwards I use android tuner and change it back to interactive
Does anyone else have this issue
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
deathsquad737 said:
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
Click to expand...
Click to collapse
You know there is already a flash for this and an apk.
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
deathsquad737 said:
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
Click to expand...
Click to collapse
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
tech_head said:
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
Click to expand...
Click to collapse
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
deathsquad737 said:
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
Click to expand...
Click to collapse
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
tech_head said:
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
Click to expand...
Click to collapse
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
deathsquad737 said:
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
Click to expand...
Click to collapse
I can always get you a copy of the file.
tech_head said:
I can always get you a copy of the file.
Click to expand...
Click to collapse
Yes please I pm you
A.L.B/E.B.B
Thank you but...
First of all, thanks for the post. Although I appreciate the helpful post, my phone is now stuck in boot loop . I hate to be the one to open up an old thread but I'm freaking out at the moment due to brick fever :crying: My current setup was a rooted LG G3 VS98512b. My goal was simple, I didn't want to do anything crazy, I just wanted to enable wifi tether now I'm afraid I've lost everything... Is there a way I can get back into the storage of my phone and delete the modified build.prop, remove the ".bak" from the original and be back to the good life? Any assistance is greatly appreciated, this seemed like such a simple modification that led to such a big headache.
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
trent999 said:
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
soundmasterx said:
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
Click to expand...
Click to collapse
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Digital_MD said:
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Click to expand...
Click to collapse
Again, thank you for the response. Do you recommend a specific method or tutorial for trying restore the original build.prop? I did search however, because this scenario is so specific I'm not sure there is an exact solution to my problem.
Again, just in case someone else can chime in, I followed the instructions on the first post of this thread (see first post for detailed info). I copied the original build.prop then changed the name of the original build.prop, edited the copy, moved it to the original directory and restarted the phone. Now my phone doesn't make it to the Verizon screen (I think it is stuck in boot loop), the screen stays black and the small led on the left corner flashes blue and green. If I can just get access to the storage I can replace the modified build.prop with the original that is still in the same directory just renamed. It seems like such an easy task but, I just don't know how to go about it I'm a somewhat of an old school tinker, I'm just now getting back into the swing of Android... Thanks in advance!!
Bump
Bump please
This is crazy... I changed 2 values in build.prop for tethering and my phone wont boot now... I didnt install a ROM, change DPI, or make any major changes WTF???
Do you have a custom recovery (twrp)?
Can you connect to your phone with adb?
If you have twrp, search the board for the startup hardware key sequence to reach twrp, else from adb do a reboot recovery.
In twrp, you can select to mount system, then go to advanced - file manager. You can delete the bad build.prop, rename the good one, then set the permissions on the good one. If your good copy of build.prop is on a PC, put it on a flash drive, and use twrp's file manager to get it into your phone.
If you have a saved copy of build.prop on your PC, you can also use adb's push command. (You may also want to look at the adb shell command. The sequence might be to open a shell, delete the bad build. prop, get the right build.prop into the right directory, then chmod the right build.prop so it has the proper permissions.)
Iam not a good thread maker so i will try to write everything as simple as i can.
Few days ago i bought and switched to A7 2018 from A5 2017, which was/is still an excellent phone to me.
On A5 i was on Oreo and on A7 i am and will be still on Oreo. Not planning to test this on Pie, but be my guest and try it on Pie, some stuff should work. Report if it does.
On A5 i made a similar thread to enable some features, but it was much easier to do because i had a CSC folder instead of ODM folder which has some files encrypted and you need them decrypted to proceed. And there is no flashable zip, you will need to do all on your phone, except decrepitng some files which you will need to do on your pc, and then put back and overwrite the same files on your phone and give necessary permissions.
First of all iam not a developer and i dont know anything about developing.
This is just enabling some features that were allready there in the phone through some lines on some files in ODM/OMC folder and some lines implemented in the stock floating_feature.xml file.
Never delete floating_features.xml file from your phones etc folder and dont touch permissions (0644), or your phone wont boot up. You just need to edit them and save.
Iv tested only on stock A750FNXXU1ASA4 OREO, which was only rooted and nothing else was modified.
The features you should get if everything goes right are:
1. Floating messages (option in Advanced features)
2. Record calls in (phone options)
3. Show network speed (option in status bar)
4. Data Usage Notification (option in data usage)
5. Camera Shutter sound on/of (in camera options)
6. ScreenRecord (options accessible from QPannel and Advanced Features)
7. S Bike Mod
8. Places option on keypad
9. Caller ID spam protection (in phone option)
9. LiveMessages in samsung keyboard
10. S PowerPlanning (Device Maintenance/battery)
11. HomeMode(screensaver option)
12. S Pen features( needed if you ever find working AirCommand).
13. In Samsung video options, but in option that apear when you press play on video,
you should see Video Enhancer option. Download Samsung video from Galaxy apps.
14. Multiuser support
15. Dolby Atmos dual speaker (works with speaker not just with earphones)
Anyway...
I f you dont know anything about floating_features.xml or bulid.prop or ODM/OMC folders and editing them, then dont try this beacuse I won't be held accountable if something happens to your phone if you loose your data or go into bootloop! So Dont Forget to Backup your Phone!
INSTRUCTIONS:
1.You have to be ROOTED offcourse and have a file manager like RootExplorer or simillar.
2. Now you need to copy from root of your phone two files from your contry ODM/OMC folder that your phone/SIMcard uses. It must be from your contrys ODM/OMC folder no other ones. The files are cscfeature.xml and cscfeature_network.xml After you decrypt them put them back in your phone and overwrite the ones inside your contry ODM/OMC folder and give permission 0644.
After that open in text editor with your Root Explorer cscfeature.xml file and on the bottom insert the lines that you can see in the attachment, then save and restart the phone.
To decrypt cscfeature.xml files follow this thread:
https://forum.xda-developers.com/android/software/decode-encode-omc-files-omc-decoder-t3791471
3. Now open your floating_feature.xml which is located in system/etc folder and just edit/enter on the bottom of the file lines that you can see in the attachment, save and restart the phone. Dont do nothing else with this file just insert the lines then save and restart the phone. If you delete it you will go in to bootloop.
4. Now open your build.prop and on the bottom of the file enter lines that you can see in the attachment, save and restart the phone.
5. Now copy all files in system from the attachment and put them in their corresponding places.
Give perrmission for folder 0755 and 0644 for files.
Thats it!
I hope it works for you like it did for me.
Il try to answer any questions, when i have free time.
And if you all have problems doing this i will make a video tutorial when i have free time.
Does this tutorial applies to a7 2018 with android pie? I mean do I have to decrypt those files? I just want to enable call recording.
Adutz1 said:
Does this tutorial applies to a7 2018 with android pie? I mean do I have to decrypt those files? I just want to enable call recording.
Click to expand...
Click to collapse
Yes you have to decrypt and it works on android pie
@kraken77 Can you help me to decrypt those two files if i send them to you? I have problems installing python
I only want to enable call recording
Adutz1 said:
@kraken77 Can you help me to decrypt those two files if i send them to you? I have problems installing python
I only want to enable call recording
Click to expand...
Click to collapse
Okay upload the file. Will decrypt it if i got some time tomorrow. Easiest way is by using firefds xposed module. Youll see call recording setting under phone section.
So can I enable only call recording without decrypting those files? I've did it on my s8, just copied the csc code into build.prop...it will work on this device too?
Some more features if anybody is interested.
Its for Pie
https://forum.xda-developers.com/android/general/samsung-additional-features-t3930900
This works for Galaxy S10e?
Hi There
I have been a long time Hacker of largely MTK devices. So I wanted to ask a question and see if there's anything I am missing here:
I have an Android 8.1 device, I have rooted it using Magisk no problem and I have successfully changed the bootanimation.zip and also the audio files. I have been able to release the rooted OS, get the OS back to a released state with the changes as I have simply kept the removed dm-verity flags that Magisk uses on the OS.
However, I am unable to change the build.prop at all.
If I copy the build.prop file from the device, edit it on the PC, and save it back it bootloops. If I edit it, roll back all the changes and re-copy it back to the device it is fine.
I noticed the original build.prop permissions are RW (Chmod 600). I tested the above chmodding to 600 and 644 and it makes no difference. If it has changes in it, it fails, if not it works!
So something somewhere is maybe checking the build.prop against an original and not liking it.
Is there anyone on here that could help shed some light on this at all?
Bump...Anyone?
So an update to this is that I have now successfully removed DM-Verity from this device. I have also managed this on many other devices. I prove this by installing all kinds of changes on the device.
So I can pretty much do anything with this device, almost like pre-Android 5.1, however whenever I edit the build.prop at all it bootloops.
What I have tried so far:
I have tried all kinds of permissions on the file
I have duplicated the /vendor/build.prop in an attempt to get round possible build.prop variety issue.
I have removed the /vendor/build.prop
I have replaced system/prop with original build.prop but still edited (and changed back) from my PC and the device boots OK.
So it looks like somethiung is looking up the build.prop file and checking something. Almost like a DM-verity for the build.prop.
Really out of ideas now. i can literally unlock/change anything MTK now except for this issue.
Any help is much appreciated.
Oh i forgot to mention, this is a systemless and not TREBLE OS.
I usually change /system/build.prop and have never had an issue up through Android 10. I know this is elementary and no intention to offend anyone - but are you sure the file is being saved with unix-style line endings.
File-permission must be set to 644.