need stock media_profiles.xml for 47a - Verizon LG G3

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

Related

[Q] Fix for invisible sub-menu?

After rooting via Indirect's method, many sub-menus are not readable due to the text being the same color. Has anyone found a standalone fix for this? (I noticed snowball mod addresses it but am already rooted).
there is a partial fix available, but as of now it isn't practical to implement.
btw, there is a discussion about this later down the board. I can't link to it right now. I asked the same question, and I was told to use search instead of the answer and a link to the discussion. I wanted to let you know better than I was told what was going on about this issue.
From what I understand this is a non-trivial problem to solve.
The snowball root method has the fix for this, but its injected while in the root process, but i have read that the framework-res.apk provided in the snowball-mod.zip contains the fix (replaced files) and apparently by just replacing this .apk to your existing system/framework/framework-res.apk it should do the job. However i haven't found someone that has tested this yet and i dont have my nook yet so if you want to give it a try DO IT AT YOUR OWN RISK. Dont worry if it doesn't work you may get bootlops or FC's nothing major and by doing the "magic card" method for go back to stock you be fine again.
I will attach the framework-res.apk if someone wants to give it a try and please report back the results.
*NOTE: You need to uncompress first and inside you will find the .apk
Path: system/framework/
1. Copy the .apk to your sdcard
2. Using a file explorer (eg. root explorer, es file explorer) navigate to your sdcard find the .apk you just copied and copy it
3. Go back and navigate to system/framework/
4. rename the existing framework-res.apk to framework-res.apk.bak
5. immediately hit paste
6. reboot
7. report back
Veronica
lavero.burgos said:
The snowball root method has the fix for this, but its injected while in the root process, but i have read that the framework-res.apk provided in the snowball-mod.zip contains the fix (replaced files) and apparently by just replacing this .apk to your existing system/framework/framework-res.apk it should do the job. However i haven't found someone that has tested this yet and i dont have my nook yet so if you want to give it a try DO IT AT YOUR OWN RISK. Dont worry if it doesn't work you may get bootlops or FC's nothing major and by doing the "magic card" method for go back to stock you be fine again.
I will attach the framework-res.apk if someone wants to give it a try and please report back the results.
*NOTE: You need to uncompress first and inside you will find the .apk
Path: system/framework/
1. Copy the .apk to your sdcard
2. Using a file explorer (eg. root explorer, es file explorer) navigate to your sdcard find the .apk you just copied and copy it
3. Go back and navigate to system/framework/
4. rename the existing framework-res.apk to framework-res.apk.bak
5. immediately hit paste
6. reboot
7. report back
Veronica
Click to expand...
Click to collapse
i can confirm that this works. the only thing you would need to double check before replacing the framework-res.apk is to check the permissions and make sure they are correct because once you replace the apk, the NT auto reboots and if you did the process correctly it will boot up normally, otherwise you will be stuck in an infinite boot loop...
The fix did not work for me I made sure the permissions were the same but my go launcher settings are still white on white
Montisaquadeis said:
The fix did not work for me I made sure the permissions were the same but my go launcher settings are still white on white
Click to expand...
Click to collapse
If you got the snowball bootanimation then the framework-res.apk applied just fine.
However, as I may have mentioned above, but have certainly mentioned elsewhere: the white-on-white fix in snowball-mod is a stop-gap for one specific set of menus (and could even cause black-on-black for those menus!)
We cannot fix all white-on-white, and black-on-black problems without entirely retheming just about everything in the framework-res.apk, which involves the backgrounds and the texts.
As noted above: "this is a non-trivial solution".
Does the snowball animation say hack by Barnes & Noble?
Edit Looks like the modified framework-res.apk file is what is causing the nook not to charge while its on as my nook has stopped charging when its on which sucks as I use the nook constantly through out the day.
Well, if you want to just spill the beans like that... yes.
Just wanted to make sure it had taken as I havent payed any attention the boot animation in the past

[Tutorial] Changing your bootanimation for SGH-I777 dummies

Took me hours of reading to figure out something extremely simple. But, hopefully this will save some of the smart people here from having to expend energy belittliing retarded noobs like me.
When I flashed to SHOstock's ICS 2.2.6 I missed the droid animation he had with his GB 1.9.4. So I went searching on how to change it back.
It's pretty simple. All you have to do is.....
1. Get a file explorer with root access. I use ES File Explorer
2. Download any of the custom ROMs in GSII Development
3. Unzip the ROM, open System>media folder. Find the bootanimation zip file and copy that to a folder of your choice on your phone.
4. On your phone, open your file explorer and allow it root folder read/write access
5. Navigate to System>media folder and backup the original bootanimation zip, in case you ever want to replace it.
6. Navigate back to where you put the custom bootanimation zip and copy and replace that zip into the media folder on your phone.
You're done.
If there was audio to the bootanimation it's the same copy and paste process. The .wav file should be located in System>etc. It's named "PowerOn". Once you move that over you may have to change the file permissions to RW--R--R.
To change permissions in ES File Explorer you long press the icon. It'll pull up an "Operations" drop down. Scroll to "Properties". Click "Change". Then make sure User: read/write is checked. Group: read. Other: read Then click ok.
If the sound doesn't work you may have to rename the PowerOn.wav to "PowerOn.ogg"
I'll try and answer any questions you may have but keep in mind i've only had this phone for less than two weeks. I've been lurking and studying on XDA for even less. But i'll do my best.
Remember, before asking questions, searching/reading the forums is your best option. I'm still a total novice but because of this wonderful place i've managed to root my phone, installed several different kernels and themes and flashed two different ROMS
You can also put the bootanimation.zip file in data/local. This way you will preserve your stock bootanimation file.
Sent from my SGH-I777
Hey I'm not sure if this is recommended but I didn't see any instructions specifically for disabling the bootsound. I did find the location of it in this post so I just removed it and my phone stopped making noises when it boot up. I'll report back if any weird issues start happening.
JohnnyKushi said:
Hey I'm not sure if this is recommended but I didn't see any instructions specifically for disabling the bootsound. I did find the location of it in this post so I just removed it and my phone stopped making noises when it boot up. I'll report back if any weird issues start happening.
Click to expand...
Click to collapse
Should be ok. Because if the animation didn't have sound to begin with the .wav file wouldn't be there.
Props to chetan_mohanty for the bootanimations.
Most of the links to the ba's are down but the MassEffect one is still active.
MassEffect - http://depositfiles.com/files/f461b8tt3
Video:-
http://www.youtube.com/watch?v=-W2jWIHSODw
You can thank him here or see his other animations.....
http://forum.xda-developers.com/showpost.php?p=20673303&postcount=1

Borrowing bootanimation.zips from the Galaxy Nexus..

So I wanted an appropriately shiny boot animation for my newly Fresh-rommed Evo, and I found this page:
http://droidmodderx.com/galaxynexus/how-to-install-100s-of-bootanimations-for-your-galaxy-nexus (Full of previews, will bog your computer down!)
That phone has the same screen resolution, 720 x 1280, so most of these seem to work for me. I didn't bother with flashing them from recovery, as the bootanimation.zip file can be easily extracted and placed in /system/media using Root Explorer. Your mileage may vary. I am using Spyro at the moment, nice ICS-ish colors.
SOME of them did not work, or rather they worked, with intermittent flashes of a white screen..I am not sure but suspect it's something to do with frame rate? Anyone?
Updates.................
Directories: Your individual rom maker may have put the animation package in one of several locations. These include:
/system/media
/system/customize/resource
/data/local
I have seen still other locations used on my old EVO 4G (and new roms are coming out all the time), so if you just cannot find anything, try doing a search for 'animation.zip' from the root level, with your file browser.
Filenames: Your rom maker may have used one of several slightly different name variants for the bootanimation.zip package; it really depends on what they started out with as a base. Sense-based roms, for example, will tend to change things up. You might have an 'HTC_bootup_one.zip' instead of a 'bootanimation.zip'. You can't go wrong by naming your new package the exact same thing, and putting it in the same folder. (BUT you also have the option of deleting all oddly named animation packages you find in odd locations on your phone, and just using the standard 'bootanimation.zip' and putting it in /system/media. This is the Android standard location, and it will almost certainly look there if it can't find it elsewhere. Note that if you do this and fail to find and delete the other package, it will still use the other instead.)
Permissions: You shouldn't need to change permissions on the package file, at least that's never been an issue for me. If you are having problems there, I'd suggest trying the standard 644 setting one usually finds in the system folder, or RW-R--R--. (As long as the file is Readable by the owner, I would think that it would work.)
I can't delete or change these files! You may be using ES File Explorer, which is not the easiest app to drive. It requires root permission being set in its settings, and if you don't do that, hilarity can ensue. (I again recommend Root Explorer by Speed Software, which is not free but gives the most straightforward file browsing experience you can imagine, a big plus if you're new to rummaging around in your phone's innards!)
You absolutely cannot play with this stuff without root, so don't even try, okay? And when you want to change anything in a root-level folder, you will need to remember to set that folder RW (read/write), and then remember to set it back to RO (read only) when you are done, yes? You smart folks already know these things, I just want to make this post as complete as possible.
But I need MORE animations! I found the link above by googling 'bootanimation.zip 720x1280' so have at it!
If you've any more questions, please ask..
Worked great for me, thanks!
-Mike
What about activating sound?
Purest said:
What about activating sound?
Click to expand...
Click to collapse
Well, if you want sound and the animation doesn't include it, it is possible to add any fairly short sound in .ogg format to the same /system/media folder, and call it with an edit to the bootanimation.zip file. (You'll need to call it from the desc.txt file inside the zip.)
Say you have a sound picked out and converted, and it's called evoboot.ogg. Your desc.txt will need to include the line:
s evoboot.ogg
There are some tutorials on building these animations from scratch, if you look around on here, like http://forum.xda-developers.com/showthread.php?t=1420991
Sent from my EVO using xda premium
You can also use this guide
http://forum.xda-developers.com/showthread.php?t=1321360
Sent From My Sweet Ass EVO LTE
I have been wanting to change Boot Animations - and I have done it on other phones and ROMS I have used - but I am a little confused - I went to my system/media folder and there isn't a boot anmiation file in that folder now - The Rom I am using (Charmeleon or something like that) has a boot animation of some kind - but it must be in a different folder - any suggestions?
mocsab said:
I have been wanting to change Boot Animations - and I have done it on other phones and ROMS I have used - but I am a little confused - I went to my system/media folder and there isn't a boot anmiation file in that folder now - The Rom I am using (Charmeleon or something like that) has a boot animation of some kind - but it must be in a different folder - any suggestions?
Click to expand...
Click to collapse
I use the same rom. The file is in system/customize/resource. You have to rename the bootanimation to hTC_bootup_one.zip. Also don't forget to make the permissions match.
I am very much looking forward to trying some of these out tomorrow when I get off of work!! I've read through the two guides on making your own and implementing your own sound files. These sound very exciting as well, but I feel they are over my head still. I am going to pace myself a bit and wait to try them.. but soon I will try.. But for now there are just so many to choose from.
ducky1131 said:
I use the same rom. The file is in system/customize/resource. You have to rename the bootanimation to hTC_bootup_one.zip. Also don't forget to make the permissions match.
Click to expand...
Click to collapse
Could you expand on how to make permissions match. I found two files in that directory that has me confused. One is hTC_bootup.zip and one is SPC_bootanimation.zip. Which do I change? Also it seems that I can't delete the spc one to put the zip I downloaded in its place. Am I making this harder than it really is?
Sent from my htc_jewel using xda premium
MRBULLRED said:
Could you expand on how to make permissions match. I found two files in that directory that has me confused. One is hTC_bootup.zip and one is SPC_bootanimation.zip. Which do I change? Also it seems that I can't delete the spc one to put the zip I downloaded in its place. Am I making this harder than it really is?
Sent from my htc_jewel using xda premium
Click to expand...
Click to collapse
Got it. Thanks.
Sent from my htc_jewel using xda premium
MRBULLRED said:
Got it. Thanks.
Sent from my htc_jewel using xda premium
Click to expand...
Click to collapse
Got what? Can anyone elaborate?
I'm wanting to know this too, because I tried some other boot animations from an HTC ONE series phone, and it didn't work.
These were mentioned here on the boards earlier, and I tried to use a flashable "beats" BA, but it did not work. Also tried the "suckerpunch" BA manually by going into system/customize/resource, and THAT did not work either.
A guide would be greatly appreciated, and a sticky should be made for boot animations, as well as splash screens.
mcwups1 said:
Got what? Can anyone elaborate?
I'm wanting to know this too, because I tried some other boot animations from an HTC ONE series phone, and it didn't work.
These were mentioned here on the boards earlier, and I tried to use a flashable "beats" BA, but it did not work. Also tried the "suckerpunch" BA manually by going into system/customize/resource, and THAT did not work either.
A guide would be greatly appreciated, and a sticky should be made for boot animations, as well as splash screens.
Click to expand...
Click to collapse
Where did those animations come from that you mentioned? Cause i doubt the names are correct for this phone
Sent From My Sweet Ass EVO LTE
Okay. First go download the boot animation that you like from:
http://tinyurl.com/co9ulfv Not sure if you can post the full links here but at least this one is clickable?
(One of the bootanimations I clicked on was bogus so use your brain. The next three brought me right to the file download without visiting a website first.) Then go into ES file explorer and go into settings and make it writable by placing a check next to Root Explorer and Mount File System. Next I found the downloaded file and clicked into it and clicked Data then local and found the actual boot animation zip and copied it to the root of the SD card so it would be easy to find. After that I renamed that file to SPC_bootanimation.zip. Now you go into system/customize/resource and delete the file labeled as SPC_bootanimation.(I saved a copy first and this must be done before you copy the file you're pasting in there. Don't know why but once I copied I couldn't delete the stock _bootanimation.zip file). Then I went back to the sd card and copied the renamed SPC_bootanimation file and pasted it in the resource directory where i deleted the original. Bingo, reboot and you will see your new animation. I did all of these steps in ES File Explorer.
Your folder may be in system/media depending on which rom you're using. I am on stock/ ultra smooth lscape Rosie by flex360.
P.S. the way I was messing up first was I was trying to rename the file I downloaded to spc_bootanimation not the bootanimation.zip file located inside of that original download in the Data/Local directory.
Also, I'm not an English major by any means, so if something is spelled incorrectly or the proper grammar wasn't used, sorry. I'm not looking for a lesson just looking to help out. heck if it's bad enough, just click on the donation tab next to my name and maybe I can afford some classes.
I'm using the bluplazmall boot animation. Looks really good.
http://gunnermike53.com/Themers/jaekar99/Galaxy-Nexus-403/BluPlazmaII-403-Nex.zip
I updated my post, does it answer your questions? If not, or if you would like to correct a point, let me know.
dased14 said:
Where did those animations come from that you mentioned? Cause i doubt the names are correct for this phone
Sent From My Sweet Ass EVO LTE
Click to expand...
Click to collapse
they are correct when your running a one x rom port. thats what hes referring to joelz rom.
thanks, I can't stand the stock animation and haven't found much so far for the EVO LTE. Lots of stuff out there for the G Nex!!
what you looking for?
Ok maybe I'm just retarded, or just a little rusty on my adb. Tried this in RootExplorer, didn't work. Tried it using adb, didn't work either. It's saying /system is mounted as Read-Only. I tried an app called SUFBS and made sure that it was mounted as Read-Write, and it failed. In adb, I'm navigating to the correct folder, "adb devices" to make sure it's showing up, "adb remount" which is succeeding, then "adb push SPC_bootanimation.zip /system/customize/resource/" and it's giving the Read-only error. I'm running ViperRom 1.2.1 and am S-Off. Anybody got any pointers? Oh and btw, I did extract the bootanimation.zip from the .zip file I downloaded from the website in the op.
I am curious what root explorer is saying when in that directory..does the button at the top allow you to set it RW?
It's not showing an icon for rw or anything. May be a different, crappier version? It's the one that came with ViperROM. That SUFBS app is very similar, and I chose rw in it, found the bootanimation.zip file on my sd card, moved it to /system/customize/resource, and it showed it moving the file, but it never showed up.
Edit: It's RootBrowser. Nonetheless, SUFBS is essentially the same thing. I'm curious though why I can mount as read-write in that app, yet adb says its read-only.

How to apply Bootanimations to Rooted Evo LTE

Okay. First thanks to neutopian for the link. First thing you want to do is go and download the boot animation that you prefer from:
http://tinyurl.com/co9ulfv Not sure if you can post the full links here but at least this one is clickable?
(One of the bootanimations I clicked on was bogus so use your brain. The next three brought me right to the file download without visiting a website first.) Then go into ES file explorer On your phone and go into settings and make it writable by placing a check next to Root Explorer and Mount File System. Next I found the downloaded file and clicked into it and clicked Data then Local and found the actual boot animation zip and copied it to the root of the SD card so it would be easy to find. After that I renamed that file to SPC_bootanimation.zip. Now you go into system/customize/resource and delete the file labeled as SPC_bootanimation.(I saved a copy first and this must be done before you copy the file you're pasting in there. Don't know why but once I copied I couldn't delete the stock _bootanimation.zip file). Then I went back to the sd card and copied the renamed SPC_bootanimation file and pasted it in the resource directory where i deleted the original. Bingo, reboot and you will see your new animation. I did all of these steps in ES File Explorer.
Your folder may be in system/media depending on which rom you're using. I am on stock/ ultra smooth lscape Rosie by flex360.
P.S. the way I was messing up first was I was trying to rename the file I downloaded to spc_bootanimation not the bootanimation.zip file located inside of that original download in the Data/Local directory.
Also, I'm not an English major by any means, so if something is spelled incorrectly or the proper grammar wasn't used, sorry. I'm not looking for a lesson just looking to help out. heck if it's bad enough, just click on the donation tab next to my name and maybe I can afford some classes.
I'm using the bluplazmall boot animation. Looks really good.
http://gunnermike53.com/Themers/jaekar99/Galaxy-Nexus-403/BluPlazmaII-403-Nex.zip
Boot animation
MRBULLRED said:
Okay. First thanks to neutopian for the link. First thing you want to do is go and download the boot animation that you prefer from:
"link removed" Not sure if you can post the full links here but at least this one is clickable?
(One of the bootanimations I clicked on was bogus so use your brain. The next three brought me right to the file download without visiting a website first.) Then go into ES file explorer On your phone and go into settings and make it writable by placing a check next to Root Explorer and Mount File System. Next I found the downloaded file and clicked into it and clicked Data then Local and found the actual boot animation zip and copied it to the root of the SD card so it would be easy to find. After that I renamed that file to SPC_bootanimation.zip. Now you go into system/customize/resource and delete the file labeled as SPC_bootanimation.(I saved a copy first and this must be done before you copy the file you're pasting in there. Don't know why but once I copied I couldn't delete the stock _bootanimation.zip file). Then I went back to the sd card and copied the renamed SPC_bootanimation file and pasted it in the resource directory where i deleted the original. Bingo, reboot and you will see your new animation. I did all of these steps in ES File Explorer.
Your folder may be in system/media depending on which rom you're using. I am on stock/ ultra smooth lscape Rosie by flex360.
P.S. the way I was messing up first was I was trying to rename the file I downloaded to spc_bootanimation not the bootanimation.zip file located inside of that original download in the Data/Local directory.
Also, I'm not an English major by any means, so if something is spelled incorrectly or the proper grammar wasn't used, sorry. I'm not looking for a lesson just looking to help out. heck if it's bad enough, just click on the donation tab next to my name and maybe I can afford some classes.
I'm using the bluplazmall boot animation. Looks really good.
"link removed"
Click to expand...
Click to collapse
I done this step by step and when I rebooted, I got a blank screen and other attempts has gotten me the old boot screen back. How can I fix this? Not sure what info you need but I am on HTC Evo 4G lte with all stock software. I am rooted and unlocked bootloader.
Sorry didn't notice this was a guide. I thought he qouted someojes from another thread and posted here. Sorry man.
Sent from my EVO using xda premium
the easiest way to find out where the bootanimation goes is by looking at the default.xml in system/customize/CID
.
some devs not all change the location and names of their bootanimtions(no motter what rom i run i change mine to bootanimation in the defaut xml and name my animations that)
dased14 said:
the easiest way to find out where the bootanimation goes is by looking at the default.xml in system/customize/CID
.
some devs not all change the location and names of their bootanimtions(no motter what rom i run i change mine to bootanimation in the defaut xml and name my animations that)
Click to expand...
Click to collapse
I just took a look at my default.xml (running Sinister V11) and it says SPC_bootanimation.zip should be in /customize/resource. Yet, it's not there.
cabbieBot said:
I just took a look at my default.xml (running Sinister V11) and it says SPC_bootanimation.zip should be in /customize/resource. Yet, it's not there.
Click to expand...
Click to collapse
Try renaming whatever bootani to that anyway and put it there. Might still work.... Can't hurt, right?

Tethering[mod] "build prop edit"vs985

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.)

Categories

Resources