Hi, I downloaded and install optimize from new provision optimize tool (automatically adding tweeks ) but it screwed my 2g and 3g connection so here's the question. I want to delete modified build.prop and restore the backedup one (the apply did it before optimization). I'm noob in this, so can I just delete the modified one and rename the original back up? Is it OK? Thanks
Swyped from my ZTE Blade
Yes u can. Just delete build.prop and rename ur backup which is usually build.prop.bak to build.prop.
Sent from my Blade using xda premium
OK I tried to delete it but it said It can't be deleted. Tried renaming but action cannot be done ... I'm using es file explorer.
Oh and permissions for it are rw-r-r
Swyped from my ZTE Blade
Use root explorer. Mount R/W.
Sent from my ZTE Blade using XDA app
if u r using es go to setting and allow root access and superuser access or its something like that delete the modified build.prop first and then remove the .bak from the backuped one and reboot.
or simply use root explorer as kartik said
Ok ive done it in different way. I reinstalled the tool that screwed it and remove the JiT compiler option from it and installed the optimization again and reboot. Working ok now. Thnx for help guys
Hey peeps!
I just flashed to the latest CM9 nightly from RC2 and wiped cache and dalvik. I tried to change the DPI back to 213 as I did before: reading this guide and using Total Commander and editing the build.prop in the /system dirr which worked without any problems in RC2 but now TC or any other file manager cant save the file. I thought first that I didnt have root possibilites but all other apps that require root works and get roots. Whats your idea of this? I tried using ROM Toolbox but I couldnt figure out where to change the DPI there
EDIT: Uhm rather delete this one, Ill post it in the correct thread instead
Same experience with total commander. That's why I copied the build.prop in another folder, edited it and pasted it back into /system. Check the permissions.
ROM toolbox has two options, one with a slider (build prop tweaks) and the other is the editor. Look for ro.sf.lcd_density= 320 and change it there.
AAh thanx! finally away from the horror DPI 320, all mothers nightmare! =)
I bid you thank you kind sir!
AA1973 said:
Same experience with total commander. That's why I copied the build.prop in another folder, edited it and pasted it back into /system. Check the permissions.
ROM toolbox has two options, one with a slider (build prop tweaks) and the other is the editor. Look for ro.sf.lcd_density= 320 and change it there.
Click to expand...
Click to collapse
You can manualy change it with Root Explorer too. This is the only safe file explorer which doesn't kill you ROM if you change lcddestiny setting with it.
Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
synesthesiac said:
Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
Click to expand...
Click to collapse
Hello,
I was trying to edit the build prop file using the ES Explorer, but the same happened to me, I could edit the file by downloading the "build prop editor" from play store.
Edit the file by pressing the button in shape of a pencil and later press the save button. If you only search for the line you want to edit in the main screen of the app you will be able to modify the line but the changes are not saved.
Thanks/rate
synesthesiac said:
Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
Click to expand...
Click to collapse
Never mind.
ES File doesn't always save, you'll just have to try a different app. Root explorer should work or fx file manager.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hello, I have just wasted about a day of my time on this issue.
Problem:
When I root my S4, running Kitkat, or load custom Kitkat ROM - wanamlite in my case, then the auto rotate screen feature stops working.
The problem is not in the HW - the camera app, which rotates labels on the screen based on orientation - kept working through all the trouble.
Details:
- I decided to root my S4, mainly to be able to install xposed/xprivacy and Titanium Backup
- first, I rooted the stock ROM, using the chainfire method. Worked fine
- I did not install custom recovery at this point
- removed few modules in TB
- noticed that the screen auto rotate stopped working
- restored the removed modules in TB, auto rotate still not working
- installed TWRP and Wanamlite. Screen rotation first worked, but after some time ( and my guess is after few reboots ), screen auto rotate failed again.
I was unable to fix this, so I had to go back to stock ROM ( Swiss FNB9 ), to get the phone working again.
Searching on Google, it seems that few of the Samsung devices have this problem of screen auto-rotation not working after rooting....
Before I try rooting again, is this a known problem ? Any fix with a high degree of reliability ?
Thanks for any info, Paul.
paulcc said:
Hello, I have just wasted about a day of my time on this issue.
Problem:
When I root my S4, running Kitkat, or load custom Kitkat ROM - wanamlite in my case, then the auto rotate screen feature stops working.
The problem is not in the HW - the camera app, which rotates labels on the screen based on orientation - kept working through all the trouble.
Details:
- I decided to root my S4, mainly to be able to install xposed/xprivacy and Titanium Backup
- first, I rooted the stock ROM, using the chainfire method. Worked fine
- I did not install custom recovery at this point
- removed few modules in TB
- noticed that the screen auto rotate stopped working
- restored the removed modules in TB, auto rotate still not working
- installed TWRP and Wanamlite. Screen rotation first worked, but after some time ( and my guess is after few reboots ), screen auto rotate failed again.
I was unable to fix this, so I had to go back to stock ROM ( Swiss FNB9 ), to get the phone working again.
Searching on Google, it seems that few of the Samsung devices have this problem of screen auto-rotation not working after rooting....
Before I try rooting again, is this a known problem ? Any fix with a high degree of reliability ?
Thanks for any info, Paul.
Click to expand...
Click to collapse
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
Wow, very much appreciated! This worked perfectly for my S4 with KitKat.
Today I noticed my auto screen rotation stopped. I googled around, tried many work-arounds, but none of them helped. A hard reset didn't work, a soft reset didn't work, Bluetooth/GPS/WiFi off didn't help, calibration using an app didn't work, etc.
I rooted my phone (as I had before, but because of the hard reset I had to root it again), installed Root Explorer, and put the libgnustl_shared.so file in the System/lib folder (while mounted R/W). I rebooted and BAM! Auto screen rotation was back again!
jupkeyope said:
Wow, very much appreciated! This worked perfectly for my S4 with KitKat.
Today I noticed my auto screen rotation stopped. I googled around, tried many work-arounds, but none of them helped. A hard reset didn't work, a soft reset didn't work, Bluetooth/GPS/WiFi off didn't help, calibration using an app didn't work, etc.
I rooted my phone (as I had before, but because of the hard reset I had to root it again), installed Root Explorer, and put the libgnustl_shared.so file in the System/lib folder (while mounted R/W). I rebooted and BAM! Auto screen rotation was back again!
Click to expand...
Click to collapse
Glad that fixed your issue mate Have a nice day.
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
That fixed it indeed !! Thanks man ! I had problems pasting the file into that directory but the "root browser" app from the play store could paste it. Then changed permissions, rebooted and ... back is screen rotation !!! Thanks !! :good:
---------- Post added at 04:09 AM ---------- Previous post was at 03:58 AM ----------
BTW, so it seems the problem is that when you uninstall samsung HUB (which I indeed did), it removes that particular file. See: http://forum.xda-developers.com/showpost.php?p=49604191
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
this solves the problem of the motion sensor? My s4 stopped working screen rotation and motion sensor ... stopped after uninstalled some apps by TB
sensor motion
its solve
Hi, Besides hitting the THANKS button, I would like to give following information for other users:
I have PhilzTouch installed and tried to flash the zip file severel times, But everytime after wiping cache part. and dalvik I noticed that nothing changed.
So I did the copy/paste action as described and after rebooting it worked.
Hi All,
I had the same issue when i rooted my device, and lost the rotation and use the method described here to fix the issue.
But after reboot the phone it will keep popping the message " Unfortunately, Samsung Hub has stopped" and it won't go away or let me do anything on the phone, as soon as i hit the OK button it will popup again.
Any possible fix for that, Please !!!
Thank you all.
In English, please...
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
Can someone help me with this, please... I have no idea what this means.
1) I downloaded the file
2) The instructions say to move the libgnustl_shared.so file into System>>Lib. When I download the file, libgnustl_shared.so is already in a folder called System>Lib...
3) Someone else said to FLASH via recover or something?? What does that mean? Can someone explain this in straightfoward terms? Thank you.
In that case, you should try to replace the existing file with the new one.
You just need to set up the parameters of the file (permissions into rw r r) as explained before. You can do it with ES Explorer for instance.
No need to do something else, just reboot.
Sent from my GT-I9505 using XDA Free mobile app
HEEELP !!!!!!!!!!!!!!!!!!!!
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
Please help if done every thing you said ive flashed it using touched based cwm ive flash my stock files before to unbrick pls help
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
That really works on my S4. But my hand motion sensor(air gesture) still does not work. How 2 fix it?
I followed the instructions to the T and still no luck. What else could it be?
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
dude you're my friggin hero...no joke...
Galaxy S4 Screen Rotation
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
Hello,
Still trying to fix my screen rotation. I reinstalled samsung hub but it dod not fix anything.I have gotten the above file into my system here, device storage-download-system-lib-libgnustl_shared.so
It does not open with any apps and under the menu button I show
hidden files
file extension
catagories
or Select directories
I cant find the right place to change permission to rw-r--r--
thanks for your help.
dave
davekane said:
Hello,
Still trying to fix my screen rotation. I reinstalled samsung hub but it dod not fix anything.I have gotten the above file into my system here, device storage-download-system-lib-libgnustl_shared.so
It does not open with any apps and under the menu button I show
hidden files
file extension
catagories
or Select directories
I cant find the right place to change permission to rw-r--r--
thanks for your help.
dave
Click to expand...
Click to collapse
Use a rootexplorer mate. And try again
Sent from my SM-G900F using Tapatalk
changin permission parameters for getting screen rotation
OK, easy, my first question was and has been "how to change the permissions".
And alone, not being an Android Geek, I succeeded !!!
First use Root Explorer, with it copy and paste (or move) the " libgnustl_shared.so" file in the "\system\lib" directory.
Once it's done (always with Root Explorer) apply a finger on this new file, a menu appears and choose "Permissions". Then there, keep only Read on the three lines, and only Write on the first line. Then click on OK.
And reboot your system.
Amazing, it's working, like the first day and before you rooted it...
Thanks again for your solution.
thanks
works great on i9505 kitkat. don't forget to reboot
no permission
im getting this when i try to do it,
"changing permissions was not successful. please note that some file systems do not allow permission changes"
anyone know how to get around this??
cheers
Using MagMa 6.0.1, with RR DPI Changer system app.
I changed the dpi, and the phone immediately said System UI has stopped. Now I can't get use it. The last backup was a while ago.
Any way to use TWRP to remove the effects of the RR DPI Changer app?
I tried deleting the app, but I'm not sure a) if I'm deleting the right files, b) if I'm deleting all the files, and c) if just deleting the app is all I need to fix it anyway, since this obviously affects System UI.
Tried dirty-flashing. No help.
Other posts in similar scenarios suggest reflashing only System, but that doesn't seem to help here since I changed dpi through an app, not just through build.prop.
Is there any way to revert the dpi without just doing a clean flash?
O's said:
Using MagMa 6.0.1, with RR DPI Changer system app.
I changed the dpi, and the phone immediately said System UI has stopped. Now I can't get use it. The last backup was a while ago.
Any way to use TWRP to remove the effects of the RR DPI Changer app?
I tried deleting the app, but I'm not sure a) if I'm deleting the right files, b) if I'm deleting all the files, and c) if just deleting the app is all I need to fix it anyway, since this obviously affects System UI.
Tried dirty-flashing. No help.
Other posts in similar scenarios suggest reflashing only System, but that doesn't seem to help here since I changed dpi through an app, not just through build.prop.
Is there any way to revert the dpi without just doing a clean flash?
Click to expand...
Click to collapse
You could copy and edit the build prop file to your desired dpi. The default is 560, I think.
QuoPrimum said:
You could copy and edit the build prop file to your desired dpi. The default is 560, I think.
Click to expand...
Click to collapse
I wasn't sure if a dpi-changer app would override manual build.prop edits, but, worth a try. Thank you! Will report back.
QuoPrimum said:
You could copy and edit the build prop file to your desired dpi. The default is 560, I think.
Click to expand...
Click to collapse
ETA: Negative. Changed build.prop dpi to ro.sf.lcd_density=560 — no help. Used TWRP File Manager to delete as many dpi changer files I could find from system/app-priv and data/data, and wiped cache/dalvik — all no help. I have no idea why it wouldn't have reverted the dpi by now. There must be something else.
O's said:
ETA: Negative. Changed build.prop dpi to ro.sf.lcd_density=560 — no help. Used TWRP File Manager to delete as many dpi changer files I could find from system/app-priv and data/data, and wiped cache/dalvik — all no help. I have no idea why it wouldn't have reverted the dpi by now. There must be something else.
Click to expand...
Click to collapse
Sorry about that. Perhaps you could replace systemui itself?
QuoPrimum said:
Sorry about that. Perhaps you could replace systemui itself?
Click to expand...
Click to collapse
Not your fault, of course. Any thoughts welcome. I've tried to replace System UI with other UI mods, to no avail. I'm trying different combinations of wiping and restoring between this backup and past one from before the dpi debacle. Nothing so far, but it's a mission now. If it's fixable, I'm gonna do it.
you could do a dirty flash of same rom. After backup of course.
There is a guide on XDA to change dpi using adb, assuming your phone still boots.
I had the same issue in the past, cannot remember if I fixed it or just reflashed from zero : now I don't modify (whole system) dpi's anymore.
Any chance you can grab the RR DPI changer apk, and share it, to know the method used to change the dpi ?
Do you get bootloop ?
Or since SystemUI is "broken" it does finish boot, but ROM is unusable (notification bar appears, then disappear in loop ? Or lockscreen keep restarting ?)
Or is it the persistent "SystemUI has stopped working" that is preventing you to do any actions ?
May be flashing a dpi changer from TWRP could work... I know most of them just re-update the build.prop, but may be try the stock 480dpi from here :
https://forums.oneplus.com/threads/flashable-zips-to-change-your-dpi-on-android-6-0.401639/
Hope you'll solve this issue !