Hello everyone, i am not an expert, but a not noob either, i recently did a stock firmware flash(FIRST)(just a tag) from odin and after that i am facing this problem
i wanted to change lcd_density and i tried using "build.prop" editor by romtoolbox and it didnt worked, it says that change is successful and when i reboots, its back to stock!
when i check build.prop editor, it dont show changed value, i dont know why! when i manually edit it with root explorer, set correct permissions and then reboots, it says systemui crashed, again and again(softbrick?)
then i reflashed the firmware and tried again, but had the same result. did this 3-4 times and always ended up with same result!
before the FIRST flash, i had no problem changing th build prop, it worked as normal, without any problem, but after this FIRST flash, things messed up
please tell me the reason and(if possible) solution
S,
hi,
install total commander or root browser or use terminal
copy /system/build.prop to /sdcard
cp /system/build.prop /sdcard/build.prop
and edit in text editor
?
mount system read-write
mount -o remount,rw /system
and rename /system/build.prop ----> build.prop_bak
mv /system/build.prop /system/build.prop_bak
copy /sdcard/build.prop ---> /system/build.prop
cp /sdcard/build.prop /system/build.prop
change permissions of new /system/build.prop to 644
chmod 644 /system/build.prop
m
Related
Hello folks,
I have a Wildfire, running CM7 #36, Jacob's 4.1 Kernel flashed.
Now I wanted to edit the /system/build.prop to get access to further apps (rom manager pro, e.g.).
After remounting system via
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
I wanted to copy/remove or whatever the /system/build.prop, but I only get
# rm /system/build.prop
rm: can't remove '/system/build.prop': Directory not empty
What does this mean? /system/build.prop is surely not a directory (ls -al).
Any help would be appreciated - can't post in the development-forums because of unsufficient number of posts - thanks,
Guntram
Don't remove it...
Pull build.prop using adb, edit and push it back to /system
Sent from my HTC Wildfire using XDA App
Hello Kevin1625,
unfortunately, this gives the same message (which I don't understand anyways?):
Code:
$ adb push build.prop /system
failed to copy 'build.prop' to '/system/build.prop': Directory not empty
Any ideas?
Are you doing this via terminal??
Adb is used on your computer.
Sent from my HTC Wildfire using XDA App
Mount system via recovery.
Open a cmd
cd into your tools folder
adb pull /system/build.prop
Edit it.
adb push build.prop /system/build.prop
adb reboot
I think youre trying to adb shell, there is no need.
Sent from my HTC Wildfire using XDA App
Thanks kevin2516 (what are these numbers for?)!
Seems, that build.prop is somehow blocked, when trying to access it on the running phone.
When I adb push on the mounted /system in recovery, everything seems to work fine.
Except, that I don't get the wanted result (Rom Manager Premium in the market) :-(.
Did you got it running, using SympMarket (which only once gave me >4000 video results - but I'm not able to reproduce ;( )?
If so, do you remember how?
Thanks a lot,
Guntram
thank you so much man! saved my phone after i accidently set PPI to 280 :L
and you should also adb shell chmod 644 /system/build.prop
Device says that system directory can not be accessed when pushing the file
I've been trying to edit my build.prop file for the past couple days and anytime I do anything at all to my build.prop file, my phone boots up with a black screen. I have no idea what I'm doing wrong.
1 method I've tried:
Code:
adb reboot recovery
adb shell mount /system or adb shell and then mount /system
adb pull /system/build.prop
I modify the line:
ro.sf.lcd_density=320 to be ro.sf.lcd_density=240
Code:
adb push build.prop /system/
Then I reboot and I get a blank screen after the Google logo.
Makes sure permissions to build.prop are correctly set after you push it to /system/. The permission should be 644. Simply run,
Code:
adb shell
chmod 644 /system/build.prop
after you've pushed the modified file over.
firefox360 said:
Makes sure permissions to build.prop are correctly set after you push it to /system/. The permission should be 644. Simply run,
Code:
adb shell
chmod 644 /system/build.prop
after you've pushed the modified file over.
Click to expand...
Click to collapse
Thank you very much. Seems it was just a permissions issue.
Hi can anyone help me try whether the enable flashlight widget in notification drawer is fixed in this apk? I had tried editing the smalis but need a tester because I am no longer using this ROM. Don't worry, it won't screw up your system. Thanks, and I would be grateful for feedback and comments below.(I know the file size is bigger but it should not affect the installation of the apk. If you could help me reduce the size of the apk. Thanks!)
Download link: https://doc-04-00-docs.googleusercontent.com/docs/securesc/uubj7fqvfjf5ec0jql27eda8tuf8buor/0p3fbcmmlesfvj1h7ji0l8d737crl4c7/1373608800000/04484889645328413275/04484889645328413275/0BxwsPruxmr3vZHlGZHRSYkhrbkE?e=download&h=16653014193614665626&nonce=k5np8umoqtbfq&user=04484889645328413275&hash=sl05t2dh68pd6a3bo75r5ndohmuh8b9h
This is a direct link, just click on it and the download will start.
How to install the apk(for those who don't know)
If you don't know how to install it into /system, here's a guide to how to do it.
If you are using Terminal emulator:
1. Type su, then type this:
Code:
busybox mount -o remount, -rw -t yaffs2 /system
2. Then, type this:
Code:
rm /system/app/Settings.apk
3. Then, type this:
Code:
cp /sdcard/<where is the file>/file.apk /system/app
3. Then, type this(Rename the apk to Settings.apk, then do this step):
Code:
chmod 0644 /system/app/Settings.apk
4. Then, type this:
Code:
reboot
5. Your phone will reboot, and after that test the apk out!
If you're using Root explorer(any kind of root explorer):
1. Copy the file to /system/app
2. Set the permissions to -rw -r -r OR 0644
3. Reboot.
4.Your phone will reboot, and after that test the apk out!
THANK you for trying this out! I appreciate suggestions!
hello everyone
I have a t-mobile note 2 rooted and i was having problems with my play store and deleted my hosts file by mistake i tried making a new one with root explorer but it fails is there anything els that i can do to get it back when i reset my phone the play store is gone and i don't know what to do any help would be great.
Bdvs said:
hello everyone
I have a t-mobile note 2 rooted and i was having problems with my play store and deleted my hosts file by mistake i tried making a new one with root explorer but it fails is there anything els that i can do to get it back when i reset my phone the play store is gone and i don't know what to do any help would be great.
Click to expand...
Click to collapse
Do you have access to a system with adb or heimdall ?
If not
You can create a new file(text) named hosts under /etc/system/ with the following line
127.0.0.0 localhost
You can set the permissions of this file to 0644 via root explorer or using Terminal Emulator:
----
cd /system/etc
chmod 644 hosts
---
Never used root explorer but there has to be a GUI option somewhere in it.
You will have to mount the /system to read-write mode in root explorer in order to make any changes.
Once you have created the file, reboot the phone and see if it works, if not then manually delete all files under /system/data/dalvick-cache.
Be careful before deleting any file, make sure you browse to /system/data/-dalvick-cache directory and select all files and then delete them.
ciphercodes said:
Do you have access to a system with adb or heimdall ?
If not
You can create a new file(text) named hosts under /etc/system/ with the following line
127.0.0.0 localhost
You can set the permissions of this file to 0644 via root explorer or using Terminal Emulator:
----
cd /system/etc
chmod 644 hosts
---
Never used root explorer but there has to be a GUI option somewhere in it.
You will have to mount the /system to read-write mode in root explorer in order to make any changes.
Once you have created the file, reboot the phone and see if it works, if not then manually delete all files under /system/data/dalvick-cache.
Be careful before deleting any file, make sure you browse to /system/data/-dalvick-cache directory and select all files and then delete them.
Click to expand...
Click to collapse
I have adb access how would i do it with adb
root explorer wont let me make a text file
Bdvs said:
I have adb access how would i do it with adb
root explorer wont let me make a text file
Click to expand...
Click to collapse
1) Using text editor create a text file named "hosts" with the following contents:
---
127.0.0.1 localhost
---
If you are on windows make sure you remove the file extension.
2) Connect phone via USB and open command prompt or shell. Make sure USB Debugging is checked under developers options.
3) Check if adb detects your device by typing: adb devices , you should see your device listed, if not please check if your phone has correct USB drivers.
4) Now push the file you created to your phone with this command : adb push /path/to/file/hosts /sdcard/hosts
example: adb push C:\tmp\hosts /sdcard/hosts
5) Now log in to your phone by typing adb shell
6) Switch to super user by typing: su , grant permissions when asked by SuperSU.
7) Mount system in read-write mode by typing: mount -o remount,rw -t yaffsw /dev/block/mtdblk3 /system
8) Move the hosts file to /system/etc by typing: mv /sdcard/hosts /system/etc
9) Browse to /system/etc by typing: cd /system/etc
10) Change file owner and group by typing: chown root:root hosts
11) Change file permissions by typing: chmod 644 hosts
12) Mount system back to read only by typing: mount -o remount,ro -t yaffsw /dev/block/mtdblk3 /system
13) Delete dalvik cache by browsing to cd /data/dalvik-cache and then type rm -f *.dex
14) type exit two times to exit.
15) Reboot phone and it should work.
I believe there might be an easy way or an apk which does this but I haven't tried it.
play store
ciphercodes said:
1) Using text editor create a text file named "hosts" with the following contents:
---
127.0.0.1 localhost
---
If you are on windows make sure you remove the file extension.
2) Connect phone via USB and open command prompt or shell. Make sure USB Debugging is checked under developers options.
3) Check if adb detects your device by typing: adb devices , you should see your device listed, if not please check if your phone has correct USB drivers.
4) Now push the file you created to your phone with this command : adb push /path/to/file/hosts /sdcard/hosts
example: adb push C:\tmp\hosts /sdcard/hosts
5) Now log in to your phone by typing adb shell
6) Switch to super user by typing: su , grant permissions when asked by SuperSU.
7) Mount system in read-write mode by typing: mount -o remount,rw -t yaffsw /dev/block/mtdblk3 /system
8) Move the hosts file to /system/etc by typing: mv /sdcard/hosts /system/etc
9) Browse to /system/etc by typing: cd /system/etc
10) Change file owner and group by typing: chown root:root hosts
11) Change file permissions by typing: chmod 644 hosts
12) Mount system back to read only by typing: mount -o remount,ro -t yaffsw /dev/block/mtdblk3 /system
13) Delete dalvik cache by browsing to cd /data/dalvik-cache and then type rm -f *.dex
14) type exit two times to exit.
15) Reboot phone and it should work.
I believe there might be an easy way or an apk which does this but I haven't tried it.
Click to expand...
Click to collapse
Thanks for all your help i got the hosts file in to system/etc folder but my play store is still not working i get a pop up that play store has stop working so i cleared cache for play store, play services and google framework and its still not working
any ideas thanks again
Did you delete dalvik cache ?
Sent from my SGH-T889 using xda app-developers app
I found no thread about this topic, so here is my guide.
I wanted to disable the navbar in order to use LMT. This is usually pretty simple by modifying build.prop and adding 'qemu.hw.mainkeys=1'.
However, this did not help on my L01 single. I found some hints which i compiled together to this guide:
needed:
a rooted GX8 running Android 5.1 (6.0 is untested, but could also work, please report me) with permissive SELinux (or any other Huawei device)
a working ADB connection
a computer with a text editor of your choice
this is what you do:
Install the TouchPlus app (attached). This apk is taken from a Honor 7, but should be identical on all devices.
Code:
adb install HwTouchplus.apk
grab your build.prop and save a backup copy (on your computer or phone)
Code:
adb pull /system/build.prop
edit the build.prop on your computer adding the following line:
Code:
ro.config.hw_touchplus_enabled=true
write back the build.prop and make sure permissions are 0644
Code:
adb push build.prop /storage/emulated/0/
adb shell
su
mount -o rw,remount /system
mv /storage/emulated/0/build.prop /system/
chmod 0644 /system/build.prop
exit
exit
Code:
reboot the device
Code:
adb reboot
now it's a good idea to enable LMT!
go to settings, there should be a new menu entry called TouchPlus (in the 'intelligent' sector)
activate TouchPlus and the nav buttons. The navbar should be gone.
hit the 'thanks' below this post if it worked.
Thanks to
@IkeaKast for his/her relevant parts of build.prop
@Rashad83 for giving me the idea and his guide
Honor-Info.de for the part about enabling TouchPlus
Unable to chmod /system/build.prop: Read-only file system
why ?
an0s5 said:
Unable to chmod /system/build.prop: Read-only file system
why ?
Click to expand...
Click to collapse
/system is mounted ro by default. If you experience this you have to remount it writeable first.
What did
Code:
mount -o rw,remount /system
return?
did
Code:
su
run successfully?
I just updated these steps, so please try again.