Well i changed dpi on my primary rom (Stock LPQ, siyah kernel) cause my friend was all like. BRO WUT DAT APP DO. and i changed it to 120, and now it crashes. I can't get to root explorer to access the build.prop cause it wont stay stable for 2 seconds. When i boot into secondary rom, it shows the build.prop for that rom, and not the primary. Is there a zip i can flash to change the prop back to 240 dpi? It's not a major issue, i just need the stock rom for certain things like mms, hence why i'm dual booted. halp pls
Can't you just re-flash the primary ROM ? I have no idea, how to modify your build.prop via phone if it crashes. Maybe somehow via ADB, but I think re-flashing the ROM will be easier.
Can you open some apps ? If yes, you could try some apps like DPI Changer and change it via that app.
extract the original build.prop file from your rom zip and use "adb push" command to manually push the file to system directory.
bala_gamer said:
extract the original build.prop file from your rom zip and use "adb push" command to manually push the file to system directory.
Click to expand...
Click to collapse
That is the ADB way I mentioned, but I think re-flashing the ROM via CWM without wipe would be easier.
Sent from my iPad 2 using Tapatalk HD
Related
I m using OptimusXromv1.1 posted in the forum..However i m not able to install stock apps like Fmradio,Native Android Browser on my P500..tried Every thing COpying files (with root of course) to /system/app and changing permissions to rw,r,r similar to other files however on reboot there is no FMRadio in my app drawer HElp..Tried both Root Explorer and Adb ..Partition was always mounted rw..HElp ?? I dont want to give up on this ROm it Rocks!!
http://forum.xda-developers.com/showpost.php?p=10746505&postcount=31
Try that.
Didn't i just say that i tried all that already..ISnt anybody else having this problem with this rom
Go to recovery, mount system and then push them via adb. They should work.
Sent from my LG-P500 using XDA App
u cud plz post that adb push command with all its parameters(if needed - something) .one more thing i have both the apk and the odex from original STock Firmware do i need to push these both or just apk is fine??
Isn't the ROM deodexed ? You should get the apps deodexed before pushing them.
You could give a try and push them both, but I think you'll be ending with a FC.
When you are in recovery mode:
1. Go to Mounts and then click on mount system.
2. With ADB while in recovery mode type:
adb push file.apk /system/app/file.apk (replace file.apk with your app, ex: browser.apk)
Didnt work! All it does it to copy the file there's a difference in date of creation of file mayb thats the reason
Sent from my LG-P500 using XDA App
I did so with devoid. I took the apps from delta package and I've pushed them through recovery.
I want to edit the build.prop of my phone to add some lines, but i do not want to flash the rom all over again. If i just edit it through a file manager on my phone, will it take effect on the rom? or do i have to edit the build.prop in the .zip fil;e of the rom and flash it all over again?
Edit the Build.prop and then just restart your phone .
Sent from my GT-I9100 using xda app-developers app
okmijnlp said:
Edit the Build.prop and then just restart your phone .
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
same thing with any init scripts right? cuz i want to edit them too
evilcuber said:
same thing with any init scripts right? cuz i want to edit them too
Click to expand...
Click to collapse
Yep.
Sent from my GT-I9100 using xda app-developers app
evilcuber said:
same thing with any init scripts right? cuz i want to edit them too
Click to expand...
Click to collapse
You can edit stuff on the /system partition and they'll survive the device reboot, so go ahead edit /system/build.prop
This does not apply to stuff on the root partition, so you can not edit e.g. /init.rc in the same way and get any lasting change. The root partition is unpacked from flash every boot, restoring any edits you've done. I.e. the running root is only a copy in ram of the root file system from the flash image boot.img containing this plus the kernel. To change files here, you'll have to reflash your device.
It changed after i flashed my ROM
Recently i made a ROM and flashed it , i made many changes to build.prop but when i open it through es file explorer it is not showing those changes ! please help thanks
edit - save - and restart ur phone
Check that you don't have 2 build.prop files after installation
Im trying to install cm 10.1 on galaxy player 5,0 international. But i get error 7 in cwm,so i edited updater-script.i deleted asserts..and now im getting error 6. This can be fixed by installing cm9 or some ics rom before jb? or i need to edit updater-script in notepad++ because unix codes.?? it would be easier for me just to flash cm9 first.
momirsarac said:
Im trying to install cm 10.1 on galaxy player 5,0 international. But i get error 7 in cwm,so i edited updater-script.i deleted asserts..and now im getting error 6. This can be fixed by installing cm9 or some ics rom before jb? or i need to edit updater-script in notepad++ because unix codes.?? it would be easier for me just to flash cm9 first.
Click to expand...
Click to collapse
Just flash this first, without loading the ROM. Enter again on CWM, wipe all but your SD/Internal memory (/cache, dalvik, /data, /datadata or something, /system, /system_app, but not emmc or sd_card) and flash CM10.1. Next flash the INTL kernel if you are not using an US version and flash GAPPS. Reboot and you are done.
A simple personal hint to get a better experience: After you get into CM, set the screen DPI on 160. If you don't like this kind of "tablet mode" set it on 161 or 162
zardak said:
Just flash this first, without loading the ROM. Enter again on CWM, wipe all but your SD/Internal memory (/cache, dalvik, /data, /datadata or something, /system, /system_app, but not emmc or sd_card) and flash CM10.1. Next flash the INTL kernel if you are not using an US version and flash GAPPS. Reboot and you are done.
A simple personal hint to get a better experience: After you get into CM, set the screen DPI on 160. If you don't like this kind of "tablet mode" set it on 161 or 162
Click to expand...
Click to collapse
i already flashed cm9 and then jb.. its working.. but now i tried to change dpi to 160 and it seems like we're talking about different versions or something because now i stuck and boot logo.. not animation. can i somehow change dpi withoud reflashing rom or something so i dont lose all my apps and data installed.
momirsarac said:
i already flashed cm9 and then jb.. its working.. but now i tried to change dpi to 160 and it seems like we're talking about different versions or something because now i stuck and boot logo.. not animation. can i somehow change dpi withoud reflashing rom or something so i dont lose all my apps and data installed.
Click to expand...
Click to collapse
No different version.
You clearly put some garbage on build.prop file OR used a incompatible 3rd party app.
I'd suggest to do it manually even because is not so hard.
Be carefull when trying to modify this file, even a single character (eg. blank space) can mess the device. Just delete the 3 characters ("240") and replace with "160".
The easiest way to get back the device is to reflash the ROM but if your data are too important do the followings:
1) Boot into CWM and connect the device to PC.
2) On "mounts and storage" mount /system.
3) Install ADB drivers on windows if you don't have them.
4) Check if ADB is working by typing "adb devices" without quotes on windows command prompt. You must see something like c501025b1278a9f recovery. If you get an error from that command you don't have adb installed correctly OR you are not in the adb.exe folder OR you didn't set up correctly the environment variable.
5) Get a clean copy of build.prop, you can extract it from the ROM.zip/system
6) Type "adb push PATH_OF_CLEAN_BUILD.PROP_ON_WINDOWS /system" without quotes, this will replace the bad build.prop with the clean one. For example, if you have build.prop on C:\ the command is: adb push C:\build.prop /system
7) Fix Permissions.
8) Done.
momirsarac said:
i already flashed cm9 and then jb.. its working.. but now i tried to change dpi to 160 and it seems like we're talking about different versions or something because now i stuck and boot logo.. not animation. can i somehow change dpi withoud reflashing rom or something so i dont lose all my apps and data installed.
Click to expand...
Click to collapse
alternatively, you could wipe /system and reinstall then wipe cache and dalvik and you should be fine
also, please refrain from creating threads with questions that should be posted in the Q&A
thanks
zardak said:
No different version.
You clearly put some garbage on build.prop file OR used a incompatible 3rd party app.
I'd suggest to do it manually even because is not so hard.
Be carefull when trying to modify this file, even a single character (eg. blank space) can mess the device. Just delete the 3 characters ("240") and replace with "160".
The easiest way to get back the device is to reflash the ROM but if your data are too important do the followings:
1) Boot into CWM and connect the device to PC.
2) On "mounts and storage" mount /system.
3) Install ADB drivers on windows if you don't have them.
4) Check if ADB is working by typing "adb devices" without quotes on windows command prompt. You must see something like c501025b1278a9f recovery. If you get an error from that command you don't have adb installed correctly OR you are not in the adb.exe folder OR you didn't set up correctly the environment variable.
5) Get a clean copy of build.prop, you can extract it from the ROM.zip/system
6) Type "adb push PATH_OF_CLEAN_BUILD.PROP_ON_WINDOWS /system" without quotes, this will replace the bad build.prop with the clean one. For example, if you have build.prop on C:\ the command is: adb push C:\build.prop /system
7) Fix Permissions.
8) Done.
Click to expand...
Click to collapse
Well then its because i used some dpi changing app from play store. Btw i restored everything by formating /system and flashing rom again without wiping cache,dalvik or data. and now its ok. so if set it to 160 i get tablet mode? Real tablet mode or what? Thanks btw for help.really.thanks.
momirsarac said:
Well then its because i used some dpi changing app from play store. Btw i restored everything by formating /system and flashing rom again without wiping cache,dalvik or data. and now its ok. so if set it to 160 i get tablet mode? Real tablet mode or what? Thanks btw for help.really.thanks.
Click to expand...
Click to collapse
I don't know if is the "real tablet mode" you think, but is kinda different than on >160 dpi.
For example, when you install an app, the window is not full screen; the same happens on google play store;
Some in-app buttons like "refresh" or "menu" are labeled (eg. Battery menu).
I use this dpi settting only because everything is smaller and there is more room, i don't care so much about this sort of tablet mode.
As I said is a personal opinion, you can reset at anytime. Just do it manually by opening /system/build.prop with ES File Explorer; scroll untill you find "ro.sf.lcd_density=240", delete 240 and replace with 160; save and reboot.
Another advice: when you aren't 100% sure on what you are doing do always a nandroid backup on CWM, if something goes wrong restoring this backup can save you a LOT of time.
Hello! I'm downloaded an app called LCD Density Modder, and i modified the screen DPI 240 to 210 and i get a bootlop.
I have a .backup file in a stocked recovery, but if i want to recover the backup, i choose recover from sdcard, and i dont see the sdcard, just the in-phone memory.
I have install update.zip via ADB, but gives me just adb sideload file.
Help me how to edit my build.prop via ADB sideload, or how to install backup from sdcard?
Thanks!!!
If you are rooted just use adb push to send the file.
How?
CtrlAltDelIrl said:
If you are rooted just use adb push to send the file.
Click to expand...
Click to collapse
Okay, but how?! My phone gets bootloped, and if i choose the Install update via ADB, it just gives me sideload session
(adb devices, and list me with "sideload" prefix)
Hi, I have a rooted Lenovo B device (Mediatek M6735M) with TWRP recovery. I tried to change some build.prop values using an editor app but the result was I bricked my phone (and had to flash stock firmware again). Now, I wonder if and how I can apply some changes to the system files after flashing the firmware.
I want to ask you: is it possible to modify sys/system files after the firmware has been flashed (even the read-only ones), or is pre-flash manipulation the only solution? For example: is it safe to pull a system file with adb, modify it, then push it to the phone with adb?
Black Heretic said:
Hi, I have a rooted Lenovo B device (Mediatek M6735M) with TWRP recovery. I tried to change some build.prop values using an editor app but the result was I bricked my phone (and had to flash stock firmware again). Now, I wonder if and how I can apply some changes to the system files after flashing the firmware.
I want to ask you: is it possible to modify sys/system files after the firmware has been flashed (even the read-only ones), or is pre-flash manipulation the only solution? For example: is it safe to pull a system file with adb, modify it, then push it to the phone with adb?
Click to expand...
Click to collapse
No. You want to root your android again to do these.
Ashwinrg said:
No. You want to root your android again to do these.
Click to expand...
Click to collapse
I forgot to say that I rooted the phone again. I'd like to know if it is possible to edit system files after flashing a firmware (and rooting the phone) or if I'm forced to apply all system changes before flashing. Also, I'd like to know what kind of changes are allowed and/or forbidden (in order to avoid another brick).
For example, I found a read-only "serialno" file in "sys" folder and this file contains the serial number of the device. Could I pull this file with adb, change the content of this file (with another serial number) then push it into the phone?
Black Heretic said:
I forgot to say that I rooted the phone again. I'd like to know if it is possible to edit system files after flashing a firmware (and rooting the phone) or if I'm forced to apply all system changes before flashing. Also, I'd like to know what kind of changes are allowed and/or forbidden (in order to avoid another brick).
For example, I found a read-only "serialno" file in "sys" folder and this file contains the serial number of the device. Could I pull this file with adb, change this file (with another serial number) then push it into the phone?
Click to expand...
Click to collapse
You can change anything after rooting your phone. Make sure you are doing it correctly. Keep nandroid backup to recover from bad scenarios.
Ashwinrg said:
You can change anything after rooting your phone. Make sure you are doing it correctly. Keep nandroid backup to recover from bad scenarios.
Click to expand...
Click to collapse
Ok, but I'd like to have some general tips or advices before doing that. For example, I read (somewhere, here on xda) that file permissions have to be the same as the original file, so if I edit a read-only file I have to restore its read-only status or I could brick the phone. Is this true?
Black Heretic said:
Ok, but I'd like to have some general tips or advices before doing that. For example, I read (somewhere, here on xda) that file permissions have to be the same as the original file, so if I edit a read-only file I have to restore its read-only status or I could brick the phone. Is this true?
Click to expand...
Click to collapse
Yes. If you change permission to read-write then after modification you want change permission to read-only.
Grab ithat build.prop file and transfer to memory card using TWRP. Edit at PC and restore it