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.)
Related
laymil has posted a much better script for this. As such I will be discontinuing my work on this for now. Not for any hard feelings, but because it is now beyond me to help any further.
As always I am glad to have helped the community in some small way. Thank you all
CHEERS
Geniusdog254 Posted the exact lines in the build prop that needed to be changed. This is a pretty common fix for problems like this between versions of Android. There was some concern however that you may miss some of the newer apps released only for Froyo. I wrote some simple scripts that will fix this for us.
Simply: One puts the Froyo build.prop on your phone. The other puts the modded build.prop on your phone.
Prerequisites
YOU MUST HAVE GSCRIPT INSTALLED
YOU MUST HAVE BUSYBOX INSTALLED
(IF YOU ARE USING PAULS FROYO ROM FROM HERE
http://forum.xda-developers.com/showthread.php?t=686631
IT DOES NOT HAVE BUSYBOX INSTALLED
Also--
There are now 2 downloads.
One will reboot your phone automatically
One will not!
(I recommend this one for anyone that has problems, or doesn't know ADB well.)
Installation
Code:
Download the attached .zip file
Place the "buildprop" folder in the root of your sdcard
Place both "Normal_Froyo.sh" and "Modded_Froyo" files in the gscript folder on your sdcard
Code:
Open Gscript
Press menu and select Add Script
Press Load File button
Select Normal_Froyo file
Press Save button at bottom
Repeat for Modded_Froyo file
After that all you have to do is open gscript and select which one to run.
Normal_Froyo will give you stock froyo build.prop and let you see froyo only apps
Modded_Froyo will give you the market fix build.prop
You can also create shortcuts directly on your homescreen for each script if you wish
-----------------------------------------------
I've decided to skip the update.zip, I've found no way to copy the scripts to the gscript folder on the sdcard this way.
I'm going for an app instead.
P.S. I've never written an app before, java looks like russian to me lol. So if anyone has any tips, or knows any good tut's let PM me and let me know.
------------------------------------------------
fixed no buildprop folder
added NON-autoreboot download.
buildprop switcher v0.3.zip ORIGINAL
buildprop_switcher_no_rebootv0.3.zip NO REBOOT
buildprop swticher v0.3.1.zip DOWNLOAD THIS ONE
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Dayzee said:
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Click to expand...
Click to collapse
So sorry lol Didn't notice until I was making the update.zip that I didn't put the other files in a folder IN the zip. Just make a folder on your sdcard called buildprop. and put them in there.
BTW testing the flashable update.zip method right now
thx, seems to work
so no more *#*#etc.. afterwards?
watercool said:
thx, seems to work
so no more *#*#etc.. afterwards?
Click to expand...
Click to collapse
Right.. the checkin service runs on each reboot. So it is not needed.
Worked just fine, but I did have to do the checkin thing. Possibly had poor signal but checkin hadn't done on reboot. Worked fine after that...
Dayz xx
followinginsanity said:
Right.. the checkin service runs on each reboot. So it is not needed.
Click to expand...
Click to collapse
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Namuna said:
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Click to expand...
Click to collapse
The reboot is built into the script. On my phone, if I checkin, the apps still don't show till I reboot. But show if I only reboot. If checkin alone works for you though, you can remove the reboot command from the script.
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
This worked great for me I also solved my (unrelated) prob with SlideIt by forcing the dictionary to save in the settings, so I'm no longer bothered about losing shortcuts stuff on a reboot.
Dandy!!
tested again with a second n1. works perfect! automated checkin works perfect.
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
Mine did this as well, though I am unsure why just yet. Been busy all day.
Mikey1022 said:
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
Click to expand...
Click to collapse
The only thing I changed from the stock to the "modded" build.prop were these 2 lines
from this
ro.build.description=passion-user 2.2 FRF50 38042 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF50/38042:user/release-keys
to this
ro.build.description=passion-user 2.1-update1 ERE27 24178 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys
I didn't add anything else to these. If you would like other things added to the build.prop files. You are welcome to edit them yourselves, or let me know what things you want changed, and I can include them.
I can make it user friendly. With descriptions for each modded line, then you can simply un-comment the options that you want.
PS: I thought I had the flashable update ready, but the update-script is giving me problems. ANYONE that wants to help please let me know. I'd really like to get this out to everyone.
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
same thing here....ANY IDEAS????????????
This is a great find, inductions were perfect and easy to follow. Not one issue getting all my paid apps back! Thank again!
JDMSirEK4 said:
same thing here....ANY IDEAS????????????
Click to expand...
Click to collapse
To anyone that can't get thier phone to boot all the way after doing this
Its not a big deal. Your phone booted. But the build.prop didn't get copied before the reboot.
If you did a nandroid before you tried it. Restore that!
If you didn't, OR you know how to use adb. Do this
Code:
adb remount
adb push [COLOR="red"]/path/to/build.2.1(or)build.2.2[/COLOR] /system/build.prop
adb reboot
I hope to have this fixed quickly.
ANYONE WHO'S PHONE WILL NOT BOOT AFTERWARDS!
Check and make sure you put the files in the right place.
build.2.2
&
build.2.1
go in
build.prop FOLDER ON YOUR SDCARD
that was the only reason I got the error, i deleted the files off my card when i was testing the flashable update.
If you still get an error. open both files in the gscript folder, and remove or comment out the reboot line. Then tell me what error you get in gscript.
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
r0adki111 said:
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
Click to expand...
Click to collapse
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
dictionary said:
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
Click to expand...
Click to collapse
Nope they're not on SD. I'll try the fc of launcher.
Ok it worked thank you! but my xiia widget still is not back and I'm assuming others. Anything I can do for the widgets?
Ok installed and reinstated the app. Works great thx again.
Update:
Ok after another reboot, apps don't show again. FC the launcher they come back but not the widgets.. Grrrrrr...
Here is the correct way to use root explorer for manually replacing system files:
1. Mount the system as r/w (read/write) per the top right corner. Navigate to the file that you plan to replace (e.g., system/framework/framework.jar).
2. Copy (not move) the file and paste it somewhere on your SD card (internal or external, doesn't matter - as long as you can locate it in case you need to put it back). Rename the file you just pasted, but very subtly. For example, when renaming framework.jar, I would only throw something in front of the file name, such as "Backup - framework.jar", so I can easily distinguish it from the new file if I put them in the same spot.
3. NANDROID BACKUP!
4. Download/put on your sd card (whatever you do) the new file that you want to replace the old one with.
5. Move the new file to /system (not in a subfolder yet). Here you will change the permissions, which is crucial to avoid FCs and problems. In root explorer, you would long press the file, press permissions, and set them to whatever the old file's permissions are. This may require going to verify what they are before starting this step. For example, in a lot of cases, the permissions will be RW-R-R. In Root Explorer, this would mean checking the first two boxes on the first line and only the first box on the next two lines. In any situation, confirm that the permissions you see after you've changed them (right below the file name) match exactly what you're replacing.
6. Ensure that your new file is correctly named to exactly what it is replacing (case actually matters) and double check the permissions.
7. Move your new file to the folder, root explorer will ask if you want to replace the file. Confirm.
8. Back out of root explorer and immediately reboot.
No force closes, no problems .
It may seem like a lot to someone who doesn't do it often but for me, I actually do this method faster than any other and fly through it every time. I got tired of seeing people explain ways to use Root Explorer which result in bootloops, FCs, etc. without fail. So, I decided to put an end to it.
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Audiochild said:
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Toggle "Mount R/W" button at the top.
Audiochild said:
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Sounds like you need to mount \system as read-write. There is a button in the upper right corner of root explorer to mount
Sent from my SGH-I777 using XDA App
Thanks wonner and kbilly70! That was the issue
Awsome. Bookmarked!
thanks for the awesome guide. worked great for me!
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
kZard said:
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
Click to expand...
Click to collapse
Those are only for flashing purposes. Not needed if you're not flashing it. You only need to pull everything besides that folder and place them appropriately.
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Edgarhighman said:
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Click to expand...
Click to collapse
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Simba501 said:
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Click to expand...
Click to collapse
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Edgarhighman said:
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Click to expand...
Click to collapse
If the apk is compatible, it will work. At no point should you get an "application not installed" prompt, unless you attempted to manually install it at some point. If it wouldn't work, it just wouldn't appear in the app drawer: no prompt.
I guess this should be mentioned in the OP, but some times, clearing data of the application may be necessary after finishing. Usually a force stop at the most will allow you to see changes (which is why the steps include a reboot). You've piqued my interest. Post the files of question and I'll see if they work on my device. There was a similar issue someone else was having; I told him to redownload the apk and that was the problem. Some kind of botched file/download.
Sent from my Galaxy S II (i777)
can you edit or create new folders in the /sys directory?
mikoal said:
can you edit or create new folders in the /sys directory?
Click to expand...
Click to collapse
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Simba501 said:
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
dsmboost said:
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
Click to expand...
Click to collapse
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Simba501 said:
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
Ah okay, I was referring to ES file explorer, which can modify other files in that directory.
thanks to you both!
Guys,
I can't post in the official thread here:
http://forum.xda-developers.com/lg-g3/development/guide-headphone-speaker-volume-booster-t2819821
But I just wanted to confirm that if you root your device and follow the directions here, I've got confirmed working on the Sprint LS990 variant of this phone. The thread mentions nothing of this on Sprint or the LS990 but I can confirm that it is indeed working.
You'll need to:
1. Have root with SuperSU installed
2. Install Root Browser and 920 Text Editor (Available in market for free)
3. Navigate to system/etc and then mixer_paths.xml
4. Change file permissions to rw-r-r
5. Save to your downloads folder just in case you trash your phone or something
6. Navigate to markers mentioned in thread link above. The LS990 variant will have aforementioned markers listed approximately 15 lines later in the code. Edit them to your liking.
7. Save, reboot, pray not to get caught in limbo.
8. Enjoy having better sound than everyone else with a phone.
Just an FYI anyone attempting this: If you do not edit the permissions correctly when overwriting the file the phone will not boot. It will get stuck at the yellow sprint screen and you will have to preform a reset.
Root browser did not allow me to change permissions correctly and when going quickly I did not notice it when overwriting.
However, second attempt after recovery it worked great.
Thanks for the info TROPhouse
So i havnt edited yet but permissions look right here. Will they change after I edit and save. And then change them back right. I don't wanna get stuck since we have no custom recovery yet.
Did it. It was way worth sweatin through the reboot process. Haha.
Has anyone thats using Viper used this mod?
Sent from my LGLS990 using Tapatalk
sinisin said:
Has anyone thats using Viper used this mod?
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
I'm using viper. Works perfect. After installing I moved the app from data/app to system/app. Heard people were having it being stopped after using it for awhile and this was there fix for that.
Kept having permission issue and was kind of nerve wrecking with no recovery.... However, phone sounds awesome now!
stagejuan said:
Kept having permission issue and was kind of nerve wrecking with no recovery.... However, phone sounds awesome now!
Click to expand...
Click to collapse
What settings did you end up with. I used 68 or 69 on all mine and it's pretty good. Not sure if I want it louder or quieter but it's definitely way better than stock was.
delete
Mahapederdon said:
What settings did you end up with. I used 68 or 69 on all mine and it's pretty good. Not sure if I want it louder or quieter but it's definitely way better than stock was.
Click to expand...
Click to collapse
I did 69 which seems perfect to be honest... I mainly hear music at the gym and usually use soundcloud... at 69, I don't even get close to full volume on the phone now. Its perfect
it seems like there are another few steps in this process that aren't being mentioned, like how to save the mixer_paths file because following the instructions and updating the lines I want to update then trying to save with 920 text editor ends with the message that it's a read only system file.
Anyone care to fill in the blanks as to how you get the update to stick?
thanks!
Super loud
Thanks! Great volume!:victory:
dk2463 said:
it seems like there are another few steps in this process that aren't being mentioned, like how to save the mixer_paths file because following the instructions and updating the lines I want to update then trying to save with 920 text editor ends with the message that it's a read only system file.
Anyone care to fill in the blanks as to how you get the update to stick?
thanks!
Click to expand...
Click to collapse
Don't know if this is too late to help, but...
I don't use 920, but my guess is there's an option somewhere (probably in settings for the app) to switch the file system to read - write mode, instead of read-only. I use the FX app, and that's what I had to do with it. Be sure to set it back to read-only when you're done.
dk2463 said:
it seems like there are another few steps in this process that aren't being mentioned, like how to save the mixer_paths file because following the instructions and updating the lines I want to update then trying to save with 920 text editor ends with the message that it's a read only system file.
Anyone care to fill in the blanks as to how you get the update to stick?
thanks!
Click to expand...
Click to collapse
SUCCESS!
So you need to download an app that will mount your system, I used an app called mount/system. You launch it then select Mount r/w. Once you do that you have the needed access to edit the files as listed. I used this guide as well and had success....hope this helps others!
copy the original mixer_paths to your memory by ES file
edit it by notepad++ on windows and put it again in your memory
copy it from internal to your /system
highlight it and set permissions rw r r
move it from /system to /system/etc/
reboot and enjoy
Has anyone tryied playing with bluetooth volume i cant find where to change it any sugestions?
Nice, I haven't had any issues with my phone being too quiet, but I also came from a Verizon G2. Those were noticeably horrible for volume levels, so the G3 is a welcome change.
In regards to all the questions about which app to use for which function:
You could use Root Explorer, or any other file explorer that has root capabilities (ES File Explorer, Total Commander). You do NOT need to use a specific app set and if your file explorer can't mount/unmount the system partition with root permissions, try a new one because that one sucks.
You also should not be downloading three separate apps to accomplish this. It's kind of overkill to have a file explorer, a text editor, and a system partition mounter when any decent file explorer has all three of those built in. I think ROM Toolbox even has all those capabilities in the free version.
RandomPooka said:
Nice, I haven't had any issues with my phone being too quiet, but I also came from a Verizon G2. Those were noticeably horrible for volume levels, so the G3 is a welcome change.
In regards to all the questions about which app to use for which function:
You could use Root Explorer, or any other file explorer that has root capabilities (ES File Explorer, Total Commander). You do NOT need to use a specific app set and if your file explorer can't mount/unmount the system partition with root permissions, try a new one because that one sucks.
You also should not be downloading three separate apps to accomplish this. It's kind of overkill to have a file explorer, a text editor, and a system partition mounter when any decent file explorer has all three of those built in. I think ROM Toolbox even has all those capabilities in the free version.
Click to expand...
Click to collapse
Agreed but I downloaded ES File Explorer and several others and I was unable to find the ability to mount as r/w. If the option is in those apps, it's very much hidden so an app to mount your file system then an editor was what I needed and it worked.
dk2463 said:
Agreed but I downloaded ES File Explorer and several others and I was unable to find the ability to mount as r/w. If the option is in those apps, it's very much hidden so an app to mount your file system then an editor was what I needed and it worked.
Click to expand...
Click to collapse
ES's current interface does hide a lot, and is in almost every way inferior to the original interface. But the option is there. It's also in FX (File Explorer) which is my root editor of choice.
the pursuit of sound quality! bullet for my valentine cant be heard on stock!!!!!!!
tried this. guess i messed up. stuck on spark screen. sat and read through the pages here. gotta fix my phone when i get home tonight.
what did you change you volume levels to?
So can those who have successfully made the edits share what volume levels you changed and what are the new numbers? I've made the change to mine and even with my $100 earphones there's distortion at what I feel is a low level. I'm thinking maybe there's a balance among these that I need to achieve?
thanks!
dk2463
I found the thread to edit the. Xml and when I view the file in ES Explorer, I can see the entire file but when I click on edit it's like half of the file disappears. I can't edit the last part of the file because it's not there. Anyone have any suggestions?
I know lots of people like ES, but I found it pretty flakey. I really like FX:
https://play.google.com/store/apps/details?id=nextapp.fx
and the root add-on:
https://play.google.com/store/apps/details?id=nextapp.fx.rr
Hasn't failed me yet, and it's the only file manager I've used that keeps the permissions correct when you edit and save a file.
I have a sprint g3 that is rooted. I tried to do the volume mod but ran into some problems. I did exactly what it said. I edited it with es file explorer. In your last section labeled speaker and headphone, there is no section on my g3. I went through the whole text file 3 times and there is no such section. I did find and change the other changes exactly as you specified. After I was done, I rebooted and it got stuck on the sprint boot screen. I took the battery out and tried starting back up but each time it gets stuck on the sprint boot screen. I did a battery pull 4 times and each time the same thing happens. Now when I do a battery pull and hold the power button, nothing happens, it doesn't even turn on. Please help.
Anyone have any suggestions on this??
I had to try to do a full wipe by reinstaling the OP through the LG website because I didn't have a custom recovery installed to back up. Somehow that didnt work and ended up bricking my device. I was within the warranty period so I just exchanged the phone. I would like to try the vol mod again (this time with twrp installed) but don't want to run into the same issues. Is there anyone that can help me with this? Thank you
I have flashable vol mods already. In the stock ZV4,ZV6 and all the Barrin Roms. They're in the op of each.
You can just pull them from the zip, place it, and make sure to FIX PERMISSIONS. That's why the bootloop. If you want to do it manually.
The first thing is to not save and reboot with an incomplete file. If you can't edit it fully, don't save it. I made the edits with FX, Linked above, and it didn't truncate the file. Finally, after editing and saving, double check that the permissions are 0644 / rw-r--r-- before rebooting.
Oh, and make a nandroid backup of your rom first, including the East partition, so if something goes wrong you can recover and make a copy of the original file, too.
Edit: Corrected the permission, in red, above.
This is a update. Just to refresh, I am on a sprint phone rooted with custom recovery, model # LGLS990, first off these are the only two files thats similar in system-etc mixer_paths_auxpcm.xml and mixer_paths.xml. Which mixer file do I use? I used the mixer_paths.xml. I found a file that someone had saved in another thread with the modified changes so I downloaded that file, moved it to my phone, copy and pasted it, overwrite the orignal file, then changed permissions and when it rebooted, I had no sound at all. PLEASE HELP
engine95 said:
I have flashable vol mods already. In the stock ZV4,ZV6 and all the Barrin Roms. They're in the op of each.
You can just pull them from the zip, place it, and make sure to FIX PERMISSIONS. That's why the bootloop. If you want to do it manually.
Click to expand...
Click to collapse
Thanks for the response. Could you link to the volume mods? I would really appreciate it. I just don't want to grab a wrong file thats not for my model device.
meyerweb said:
The first thing is to not save and reboot with an incomplete file. If you can't edit it fully, don't save it. I made the edits with FX, Linked above, and it didn't truncate the file. Finally, after editing and saving, double check that the permissions are 0644 / rw-rw-r-- before rebooting.
Oh, and make a nandroid backup of your rom first, including the East partition, so if something goes wrong you can recover and make a copy of the original file, too.
Click to expand...
Click to collapse
I noticed you said on the permissions rw-rw-r but in the Op of the vol mod (different thread), it said to use rw-r-r-
I am a little confused as to which permission to use??
jreink01 said:
Thanks for the response. Could you link to the volume mods? I would really appreciate it. I just don't want to grab a wrong file thats not for my model device.
Click to expand...
Click to collapse
If your on ZV6, then flash this. http://forum.xda-developers.com/showthread.php?p=56990565
If on ZV4, then look in those threads. I'm on my phone so I can't multi-link.
Edit. Here for ZV4. http://forum.xda-developers.com/showthread.php?p=54322264
And here. http://forum.xda-developers.com/showthread.php?p=56234124 you'll need to pull the extras out that you don't want/need, from these though.
engine95 said:
If your on ZV6, then flash this. http://forum.xda-developers.com/showthread.php?p=56990565
If on ZV4, then look in those threads. I'm on my phone so I can't multi-link.
Edit. Here for ZV4. http://forum.xda-developers.com/showthread.php?p=54322264
And here. http://forum.xda-developers.com/showthread.php?p=56234124 you'll need to pull the extras out that you don't want/need, from these though.
Click to expand...
Click to collapse
I'm on zv 4. I'm not sure what to do. Do I just pull the build prop out of the zip and use it like it is? Iclicked on your 2nd link and just downloaded the zip. I'm not sure what the first link is for. Sorry, but I just want to make sure I absolutely know what Im doing so I dont brick another g3. Thanks again for the help.
jreink01 said:
I'm on zv 4. I'm not sure what to do. Do I just pull the build prop out of the zip and use it like it is? Iclicked on your 2nd link and just downloaded the zip. I'm not sure what the first link is for. Sorry, but I just want to make sure I absolutely know what Im doing so I dont brick another g3. Thanks again for the help.
Click to expand...
Click to collapse
First off, be careful you do not take the ota. You will lose root and have to Flashtool back to zv4. There's threads on that.
I don't remember what's in the zips, but you can flash it all and it'll probably run better. If you just want the mixer_path.xml, delete the build prop, and any other file. Leave Meta and system/etc/mixer path.xml
jreink01 said:
I noticed you said on the permissions rw-rw-r but in the Op of the vol mod (different thread), it said to use rw-r-r-
I am a little confused as to which permission to use??
Click to expand...
Click to collapse
Sorry, my typo. the OP is correct.
engine95 said:
First off, be careful you do not take the ota. You will lose root and have to Flashtool back to zv4. There's threads on that.
I don't remember what's in the zips, but you can flash it all and it'll probably run better. If you just want the mixer_path.xml, delete the build prop, and any other file. Leave Meta and system/etc/mixer path.xml
Click to expand...
Click to collapse
Ok, thanks. So, I can just flash the entire zip then? Flashing the entire zip will probably make it run better then? Or do I need to pull apart the zip and just use the mixer file. The entire zip is for the stock rom then? Thanks for your help, havent done this in a few years so I'm a bit rusty. By the way, you said to leave meta, what is that file? If I'm just flashing the zip, I can do through recovery then?
Yes. Leave meta. Its part of what directs the file in the zip file where to go and gives permissions to replace existing files Etc.
---------- Post added at 09:20 AM ---------- Previous post was at 09:15 AM ----------
OK. So I'm a bit confused too about what engine95 linked to. There are zips for final mixer path, and for extreme volume. Which one does the stereo effect? Having trouble reading some of the strings in the first post against the black background of Xda app
I flashed the mixer xml file. It worked but the speaker volume is still a little too low. How can I change the speaker volume to a little bit louder? Thanks
jreink01 said:
I flashed the mixer xml file. It worked but the speaker volume is still a little too low. How can I change the speaker volume to a little bit louder? Thanks
Click to expand...
Click to collapse
Which part do I need to edit to change just the speaker volume? Thanks in advance.
jreink01 said:
Which part do I need to edit to change just the speaker volume? Thanks in advance.
Click to expand...
Click to collapse
About mid file. It'll say "speaker". 70 is the Extreme version setting.
engine95 said:
About mid file. It'll say "speaker". 70 is the Extreme version setting.
Click to expand...
Click to collapse
I went into path - speaker and to digital volume and changed the rx values (3 and 4) to 70 and rebooted and now I'm in a bootloop. It stays on the sprint logo screen. Please help.
jreink01 said:
I went into path - speaker and to digital volume and changed the rx values (3 and 4) to 70 and rebooted and now I'm in a bootloop. It stays on the sprint logo screen. Please help.
Click to expand...
Click to collapse
Not 3 and 4. 1 and 2. I think I have them at 65. And your bootloop is because you didn't set permissions properly. You'll need to restore in TWRP if you made a backup. If you didn't, then it's Flashtool.
If you're still on zv4 why didn't/don't you just flash the extreme one I linked you to before?
OK thanks but the permissions were set correctly. rw-r-r
There is no 1 and 2 that I see. I have attached a screenshot.
Hello,
I flashed a different media_profiles.xml (found in the latest camera thread in the developer section) to try out open camera and see what it could do to see if i wanted to venture from stock based roms (with all the LG camera features) to an AOSP based rom but i forgot to back up the stock media_profiles.xml file first.
does anyone have copy of this file from 47A that they could share? I dont think i lost any functionality with xcamlg as 60fps 1080p video still looks correct but id rather have the file in case i do run into any issues.
i tried to browse system.img from the 47A rom on my PC with 7zip and extract media_profiles.xml and copy to my G3 and reset the permissions and reboot but there is something about the file that solid explorer isnt happy with and im guessing its the program i extracted it with or windows or something that isnt linux/android friendly.
anyone know the proper way to do this in addition to posting the file?
thanks
brian
Here's the one from my running ROM, which is stock 47A so it shouldn't be different than what's in the system.img. If you have trouble with this one, I'd guess there's some other problem going on and maybe try a different root file manager. Or maybe you just can't replace that file while the ROM is running.
You could take zip you had flashed which had the one your current running, delete the .xml file out of it, place this .xml (or the one you extracted from the system.img) in the zip in the same place as the other was, then flash this new zip file.
For what it's worth, I've never had any problem using any file I extracted from the system.img with 7-Zip - but since I've never fooled with that one...
thank you.
ill try it in a few min.
yeah i remembered someone saying use 7-zip rather than other utilities (cant remember if it was you or stang5litre or muniz_ri over in the vzw galaxy s4 forum) to edit/extract android images.
great idea on swapping files in the zip. if i cant copy this one in ill try the zip swap method.
Brian
problem solved.
turns out it was my fault. i was able to copy the file that i extracted into system/etc/ no problem but was not able to change permissions so i figured that it was something wrong with the file.
nope...
when i copied in your file, i couldnt change permissions..... it gave me the same error.
i was using solid explorer and i had the phone sideways so i could have two directories selected for super easy copying.
downloads on the left, system/etc/ on the right.
once the file copied into the right window, i tried to scroll down to the bottom of the list where it now was placed and edit the permissions in the right window and it gave me the error.
i rotated the phone vertical so there was only one window and selected system/etc/ and the file and was able to change the permissions no problem. then rebooted the phone and everything was back to normal.
oops....
Brian
reliant_turbo said:
problem solved.
turns out it was my fault. i was able to copy the file that i extracted into system/etc/ no problem but was not able to change permissions so i figured that it was something wrong with the file.
i rotated the phone vertical so there was only one window and selected system/etc/ and the file and was able to change the permissions no problem. then rebooted the phone and everything was back to normal.
oops....
Click to expand...
Click to collapse
Ha! What an interesting bug! Wonder if the dev of Solid Explorer knows? Glad you solved it. Thanks for sharing the solution.
roirraW "edor" ehT said:
Ha! What an interesting bug! Wonder if the dev of Solid Explorer knows? Glad you solved it. Thanks for sharing the solution.
Click to expand...
Click to collapse
Yeah it's weird. I guess you have to "refresh" the window before you can edit permissions of the file. I just tried to set permissions in both the left and right window when in landscape rotation just to check and you can.
Its just that you can't immediately after pasting a file. You seem to have to select that directory again.
I'll try to contact them.
Brian