Hello, I recently rooted my phone as so I can have google wallet on my S3. I used a build prop hack and a modded google wallet apk so I can use it (It works great btw!!! ) but now when I go back to change my build prop back to what its supposed to be and save it. Ill reboot my phone for changes to take effect and itll go into a boot loop. Ill have to go into recovery mode to restore a working nanodroid and im stuck with the same build prop. The build prop has my phone listed as a htc jewel and when i DL certain apps from market its says your device is not comptabile, but i know it should be, come on it's a S3. I tried download brothers in arms and it wouldnt install, i had brothers in arms on my htc sensation no problem.....help....help....help
Sent From The Best Phone Ever Made
Install a different ROM and don't bother with the build.prop change?
Sent from my SGH-T999
Make sure there is a blank line at the end of your build.prop.
I dont know if that'll cause your problem but if there is no blank line it won't be read.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Make sure there is a blank line at the end of your build.prop.
I dont know if that'll cause your problem but if there is no blank line it won't be read.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Check the screen shot below. I edited those lines so I can having working wallet. I know what the default values should be, but are you saying when i edit those back, put a space afterwards? Just wanna make sure i follow what youre saying
Sent From The Best Phone Ever Made
So you used the Jewel code to get Wallet installed? Then signed up and everything, changed the code back to the S3...But it won't stick? Are you using Root Explorer? I think you may have to use that program... I remember reading that if you use ES explorer... It doesn't save the changes or something like that.
So maybe just try using a different explorer to edit and save the file?
No, you shouldn't need a space after the values you entered.
The blank space needs to be at the very end of the build.prop. The very last line should be a line with nothing in it.
Sent from my SGH-T999 using xda app-developers app
Honestly, make sure everything is correct. No typos what so ever. I made a recovery script that was missing a " ; " symbol and it wouldn't work. Typos are very picky when editing build.prop files or any text file in the system.
And what I would do,
Flash the ROM you currently are running
Make a copy of the default build.prop
Make your edits
Reboot
Then restore the backup. Don't edit anything, just restore the backup. If using root explorer, it creates a backup for you. So what I do is rename the build.prop.bak file and get rid of .bak file extension. Then reboot.
Sent from my SGH-T999 using Tapatalk 2
I completely forgot about the automatic backup in root explorer. Good call.
11 Years Ago Today...
WE WILL NEVER FORGET!!!
GOD BLESS AMERICA!!!
DocHoliday77 said:
I completely forgot about the automatic backup in root explorer. Good call.
11 Years Ago Today...
WE WILL NEVER FORGET!!!
GOD BLESS AMERICA!!!
Click to expand...
Click to collapse
Suppose to use root explorer to change out the build prop, after the google prepaid card is up and running, open back up root explorer, delete the build prop and rename the backup build prop to original build.prop and you should be ready to go. I had it happen once where I couldn't download anything on the market til I realize I forgot to change back the build prop
Kid Poker said:
Suppose to use root explorer to change out the build prop, after the google prepaid card is up and running, open back up root explorer, delete the build prop and rename the backup build prop to original build.prop and you should be ready to go. I had it happen once where I couldn't download anything on the market til I realize I forgot to change back the build prop
Click to expand...
Click to collapse
Always make a copy and save it on your computer... use android comander its most simple way to download stuff from android to computer using ADB its just ADB with windows interface... awesome for simple stuff that your to lazy to use ADb for.
Related
so I am not sure where I went wrong and I have been reading some threads and trying what people are saying but I think I am making it worse.
I have
Clean Gb build 16
then I added in Marcusant speed tweaks
the first issue was that instead of showing up as Clean GB in the about phone it shows as Mar... Revival Rom
I was told I could just go in and change the name here so i tried. didnt work out as hoped I think I may have changed the wrong file because it still says the revivial one.
I wanted to update to the newest Clean GB so I said screw it and went to Clock work mod and Wanted to do a full restore.( i backed up just before installing the speed tweaks)
I got an error and it said md5 mismatch
So I figured I would just reinstall Clean Gb as the zip was still on my phone and I had also had done a titanium back up would install clean gb and use that
I tried to install it and got an error and it went to a wierd screen with a lil android guy and an exclamation mark.
Id like to get on Clan Gb latest build and not have to spend 10 hours re -setting up all my contacts and main page and stuff if I can
Any ideas here.
I guess my next step is to do the factory reset from clock work and try to install again??
O I do not have access to odin at this time
Thanks!
First there are 2 entries in build.prop that have Marcusant revival that need to be changed. You would edit the one in the zip and then reflash. You can get the exact lettering from CleanGB's build prop. The other issue sounds like you sd card is going bad or corrupted. You can back it up, reformat it and restore and try again.
Sent from my SPH-D700 using XDA App
so what editor do I use to open the build file. ? thanks I was using astro currently to find it. and it wouldnt open it I was using system/ build
Thanks
svcbadass said:
so what editor do I use to open the build file. ? thanks I was using astro currently to find it. and it wouldnt open it I was using system/ build
Thanks
Click to expand...
Click to collapse
I did it on my PC. It is so much easier to cut and paste across build.prop files.
Sent from my SPH-D700 using XDA App
svcbadass said:
so what editor do I use to open the build file. ? thanks I was using astro currently to find it. and it wouldnt open it I was using system/ build
Thanks
Click to expand...
Click to collapse
Notepad or text editor of choice.
sent from a phone using an app
Djinn23 said:
Notepad or text editor of choice.
sent from a phone using an app
Click to expand...
Click to collapse
Anything should work. I just checked and it defaults to Wordpad on my Windows 7 laptop.
---------- Post added at 07:16 PM ---------- Previous post was at 07:12 PM ----------
These are the lines you need to find and edit:
ro.build.display.id=
ro.rommanager.developerid=
ro.modversion=
The 1st and 3rd are the ROM and the middle one is the email address ROM Manager uses for the developer.
My tweaks wouldn't cause an md5 mismatch of a backup or CWM to not work. Seems as if you need to re Odin Cwm. The only thing my tweak might do is break ROM manager . Just go manual.
Sent from my SPH-D700 using XDA App
this was a good read. i was attempting to add marcusant speedups to cleangb as well. *taking notes*
marcusant said:
My tweaks wouldn't cause an md5 mismatch of a backup or CWM to not work. Seems as if you need to re Odin Cwm. The only thing my tweak might do is break ROM manager . Just go manual.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Sorry If it sounded like I implied that I dont believe your speed tweaks did that. just found that issue when trying to use the back up.
Thanks for the info guys im stuck on this for now until I can buy a pc. I had been doing everything without pc. I have never odin-ed or anything so this will be all new
Just reflash your ROM to remove the fixes.
Sent from my SPH-D700 using XDA App
Hopefully just a quick and dirty question. I used esfile's note editor to edit the wifi scan interval on my build prop and it somehow caused AOKP to fail to boot. I fixed the issue and am running fine now, but can anyone recommend a safe way to edit the build prop while actually on Android?
I've used Rom Toolbox Pro to change my scan frequency without any issue. I have not tried on AOKP though.
Sent on HyDrA using Tapatalk
killaphatboy said:
I've used Rom Toolbox Pro to change my scan frequency without any issue. I have not tried on AOKP though.
Sent on HyDrA using Tapatalk
Click to expand...
Click to collapse
I'm sure that it had something to do with the editor I was using. In the past, I would copy to internal, edit on PC, then push back to system. Esfile probably muffed up the formatting because when I rebooted, I got constant black screen after Samsung logo. A quick Odin of EL29 with cwm and a reflash of AOKP and all is well. But, I'd still like to be able to manually edit build prop on the device.
I was under the belief that ROM toolbox was a no no on the e4gt, especially ICS.
ROM toolbox mostly ok. ROM manager not ok
Sent from my SPH-D710 using xda premium
As stated above it ROM Manager that will not work with this phone on GB or ICS. Using it to load CWM on your phone can brick your phone. Rom Toolbox hasn't bricked a phone to my knowledge. It has caused bootloops when changing boot animation and fonts through it on ICS though. I haven't had any issues with changing build props on ICS though, but again I have not tried it on AOKP/AOSP/CM9 ROMs.
Sent on HyDrA using Tapatalk
ROM toolbox worked well, thank you. Also, I guess the best benefit from this thread is clarification between ROM toolbox and ROM manager. Much appreciated!
Can anyone enlighten me as to why ROM Toolbox is the only thing that seems to work? I to have tried the ES File Explorer method, which worked perfect on my Evo 3D, but on E4GT it sticks at Samsung boot screen. I then booted into recovery, did adb pull, edited file on PC, and adb push back to phone. After rebooting I checked build.prop and it did not reflect the changes, just default settings (and yes I made sure to save the changes before pushing).
I unfortunately have only had the phone a week and it was shipped with FF18, so not sure what behavior was like before update. Pre-ICS, were you able to make manual edits to build.prop without issues?
Did you try wiki rootzbox? But unfortunately it's a paid app. You can ask first about your device compatibility from the dev before you buy it. Afterall it's created by Aokp rom dev.
Sent from my GT-I9100G running on codeworkx's CM10
I went ahead and got ROM Toolbox and it did work, I'm just curious as to why it works but a manual edit does not.
I believe es file inserts hidden stuff.
sent from my BAD A$$ Epic touch
patrao_n said:
I believe es file inserts hidden stuff.
sent from my BAD A$$ Epic touch
Click to expand...
Click to collapse
Perhaps, but like I said it worked on my 3d so why not here? And also curious why the adb push method fails.
reckless_t said:
Perhaps, but like I said it worked on my 3d so why not here? And also curious why the adb push method fails.
Click to expand...
Click to collapse
Are you remounting system as rw first?
Sent from my SAMSUNG-SGH-I717 using xda premium
chris41g said:
Are you remounting system as rw first?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Think i may have forgot it the first time, which may be why I booted back in with default values. But then again it did say adb push was completed. The second time i tried adb and made sure to remount first it resulted in stuck at boot again. Since ROM toolbox worked it's not a big deal anymore, but curiosity is still eating at me...
This is more than likely in the wrong section, but I was wondering if someone would be willing to take the time to guide me on editing the build prop file. I've been reading on it yet only find information for putting into the build.prop. I played around with crossix root method but was not receiving root. I was able to obtain root using the ''easy root'' method. I still don't know how to properly edit the build.prop. I am coming over from rooting and modding my LG-P999 (G2x) so I'm not a complete noob,but have never messed with build.props before.
In the end I would like to do the edit that makes our A100 appear as the A500. I have a huge collection of HD games, mainly gameloft titles. I didn't know that upgrading to stock ICS made so many titles unplayable.
I cannot locate a /rootme folder anywhere in the system partition via ESFile explorer, and the only build.prop file I've located is under /system and I'm fairly certain this is not the correct file to edit.
Any information and links will be greatly appreciated.
Sent from my A100 using xda app-developers app
justjackyl said:
This is more than likely in the wrong section, but I was wondering if someone would be willing to take the time to guide me on editing the build prop file. I've been reading on it yet only find information for putting into the build.prop. I played around with crossix root method but was not receiving root. I was able to obtain root using the ''easy root'' method. I still don't know how to properly edit the build.prop. I am coming over from rooting and modding my LG-P999 (G2x) so I'm not a complete noob,but have never messed with build.props before.
In the end I would like to do the edit that makes our A100 appear as the A500. I have a huge collection of HD games, mainly gameloft titles. I didn't know that upgrading to stock ICS made so many titles unplayable.
I cannot locate a /rootme folder anywhere in the system partition via ESFile explorer, and the only build.prop file I've located is under /system and I'm fairly certain this is not the correct file to edit.
Any information and links will be greatly appreciated.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
I would just grab on of linuxsociety's build props from his tread. The ones ending in A500 will change it. Just grab the one that matches your android version, he has them for ICS 4.0.3 (stock), ICS 4.0.4 (cm9), and 4.1.1 (cm10).
http://forum.xda-developers.com/showthread.php?t=1799148
justjackyl said:
This is more than likely in the wrong section, but I was wondering if someone would be willing to take the time to guide me on editing the build prop file. I've been reading on it yet only find information for putting into the build.prop. I played around with crossix root method but was not receiving root. I was able to obtain root using the ''easy root'' method. I still don't know how to properly edit the build.prop. I am coming over from rooting and modding my LG-P999 (G2x) so I'm not a complete noob,but have never messed with build.props before.
In the end I would like to do the edit that makes our A100 appear as the A500. I have a huge collection of HD games, mainly gameloft titles. I didn't know that upgrading to stock ICS made so many titles unplayable.
I cannot locate a /rootme folder anywhere in the system partition via ESFile explorer, and the only build.prop file I've located is under /system and I'm fairly certain this is not the correct file to edit.
Any information and links will be greatly appreciated.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
Build.prop does sit in /system, that's the correct file you found.
I might suggest using a build.prop from Linux society, there is one for a500 device naming. Its the easy way, not what asked for, but its a start.
Es file manager had an editor that can make changes to build.prop or I would suggest notepad++ it similar for windows. Normal text editors in windows save extra garbage that will break android.
I'm sure others can chime in with additional info.
Tapatalked from my Galaxy S II.
Would I just backup the old one and just copy and paste in the other build file,or is there a special way I need to replace the file? This is starting to take me out of my knowledge zone so this part is new to me.
Thank you both for the information you are providing.
Sent from my A100 using xda app-developers app
justjackyl said:
Would I just backup the old one and just copy and paste in the other build file,or is there a special way I need to replace the file? This is starting to take me out of my knowledge zone so this part is new to me.
Thank you both for the information you are providing.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
Yup, just save the one from the thread. Rename your current build prop from /system, by adding .bak to the name (backup). Then just copy the new one to the directory, making sure it is named 'build.prop'. Then reboot. All this can be done with es file explorer, with root explorer enabled in the options.
Wow. This made it look way harder: http://forum.xda-developers.com/showthread.php?p=22933062
Compatible Games for ICS
Sent from my LG-P999 using xda app-developers app
Now this is really out of my scope. I got all the way through to being ready to flash CWM but I don't have the SDK Tools, and I know nothing about them! Time to study.
justjackyl said:
Now this is really out of my scope. I got all the way through to being ready to flash CWM but I don't have the SDK Tools, and I know nothing about them! Time to study.
Click to expand...
Click to collapse
I would just install twrp recovery. Its very easy to use and install. http://forum.xda-developers.com/showthread.php?t=1799148
All you need is the Acer USB driver working and tee twrp install package. http://support.acer.com/product/default.aspx?modelId=3849
Have you unlocked the bootloader?
Yes. The boot loader is unlocked.
Sent from my A100 using xda app-developers app
Romman0 said:
I would just install twrp recovery. Its very easy to use and install. http://forum.xda-developers.com/showthread.php?t=1799148
All you need is the Acer USB driver working and tee twrp install package. http://support.acer.com/product/default.aspx?modelId=3849
Have you unlocked the bootloader?
Click to expand...
Click to collapse
twrp installed flawlessly. Thank you for the suggestion.
Moved to correct section..
Romman0 said:
Yup, just save the one from the thread. Rename your current build prop from /system, by adding .bak to the name (backup). Then just copy the new one to the directory, making sure it is named 'build.prop'. Then reboot. All this can be done with es file explorer, with root explorer enabled in the options.
Click to expand...
Click to collapse
I haven't had the chance to change build.prob on a100 yet (actually going to now) but everytime I've used a modded build.prop. I had to change the permissions to rw-r-r. Pretty sure you have to with a100 too. Just saying cause that's the only step you didn't mention. And I no how much of as pain it is when you mess up changing the build.prop. not fun at all lol
trevor7428 said:
I haven't had the chance to change build.prob on a100 yet (actually going to now) but everytime I've used a modded build.prop. I had to change the permissions to rw-r-r. Pretty sure you have to with a100 too. Just saying cause that's the only step you didn't mention. And I no how much of as pain it is when you mess up changing the build.prop. not fun at all lol
Click to expand...
Click to collapse
Never had to change permissions on my A100 to mod the /system files. The root process will do it.
I tyred once and umm, to put it shortly, YOU MUST change the permissions or be really familiar with Adb and linux and chmod it that way. I think theres a tool in twrp to do it also but I haven't a clue how it works.
Sent from my A100 using xda premium
I did as instructed. Worked fine.
Sent from G2x running BuROM v0.2 (root; mod stock 2.3.4) w/ faux's GB kernel 014b2-ext4.
When rooting your making /system writable. Zeronulls "easy" script does it automatically, so most if not all users will not have to do anything. I guess in my instructions I should have mentioned you need root, I kinda thought it was implied as the instructions were written for the OP, which stated he had root access.
Hmm....
Sent from my A100 using xda premium
No USER friendly! Sorry I can't create update.zip
Need Safestrap for BackUP and change permissions (chmod -R 755 /system/framework/framework-res.apk).
This mod can open for you full screen display in Razr M without loose toggle bar, just copy framework with style what you want to /system/framework dir, and change permission to file.
Files in zip for 4.1.1 & 4.0.4 Android.
noVbutton - no navibar in Vertical orientation, yes in Horizontal
noV-Hbutton - no navibar in Vertical orientation, no in Horizontal
origin - original file
Of course you can change all manually if decompile framework-res.apk and find file named dimens.xml
<dimen name="navigation_bar_height">18.0dip</dimen>
<dimen name="navigation_bar_height_landscape">18.0dip</dimen>
<dimen name="navigation_bar_width">42.0dip</dimen>
link to framework-res.apk http://forum.xda-developers.com/attachment.php?attachmentid=1763662&d=1361913475
Thank you! I've been trying to figure out if this could be done. Swapped in your file using Root Explorer on the phone, everything crashed (kinda expected). Rebooted, changed permissions, and now she's working great!
jjlangen said:
Thank you! I've been trying to figure out if this could be done. Swapped in your file using Root Explorer on the phone, everything crashed (kinda expected). Rebooted, changed permissions, and now she's working great!
Click to expand...
Click to collapse
Ugh, tried to follow in your footsteps but got totally screwed. Wasnt able to chmod, tried rebooting and stuck in bootloop
Developer only?
Does this work for the developer and regular versions? Anyone tried this with the official JB OTA from Verizon?
I used Root Explorer, not a terminal. Running on stock Verizon Jelly Bean, retail version.
Sent from my XT907
It Works!
Yeah, FINALLY! Get rid of that craptastic waste-of-space navbar.
If anybody want to know, here's how I did it:
Note: I used root explorer
1. I used my windows 7 machine to extract the version of framework-res I wanted.
In my case, i'm on the 4.1.1 JB Verizon OTA, so I chose the 4.1.1 noV-Hbutton.
2.Copy the framework-res of your choice to the root of your internal storage card.
3. Using your file manager (Root explorer in my case) copy the framework file from your internal storage to "\system\" NOT "\system\framework\". Note, if you do this step and it asks you if you want to overwrite "framework-res.apk" STOP!
4. Using your file manager, write down the permissions for your existing "\system\framework\framework-res.apk".
5.Go to the framework-res.apk you just copied "\system\framework-res.apk" and change permissions to match those of your existing framework-res file.
6. AFTER the permissions have been changed and verified (I exited completely out of root explorer, then re-opened it and double checked that the permissions where the same) you can safely move and over-write the file in "\system\framework\".
7. Here's the reason. If you just copy the modified framework file straight from your internal memory to its home in "\system\framework\" the permissions won't be right, and there is a VERY good chance you will end up in an endless bootloop. Copying the file to "\system" first gives you the opportunity to modify its permissions BEFORE overwriting the existing framework file.
Good luck!
Update: Not sure why, and it isn't causing any problems, but every time I reboot the phone, it goes through the "android is upgrading your apps" dialogue".
Guess I got lucky avoiding a bootloop. I just copied the new file, went to /system/framework, renamed the current file, and pasted in the new one. Then all the applications crashed, I rebooted, and changed the permissions. I did have to sign back into all my accounts (Google, Facebook, etc), but zero issues since then.
I'm still loving it! The nav buttons took up so much space. The new version of LMT that you can trigger from the bottom makes it perfect.
http://forum.xda-developers.com/showthread.php?t=1330150
Op you rock man! Thanks ks a ton!
Sent from my SCH-I815 using Tapatalk HD
kensdavid said:
Ugh, tried to follow in your footsteps but got totally screwed. Wasnt able to chmod, tried rebooting and stuck in bootloop
Click to expand...
Click to collapse
same thing happened to me
I got moved the new framework file into the folder except I accidentally deleted it at the same time. Everything started to "stop working" and after I did a hard reset recovery (wipe data/factory reset + wipe cache partition) it stays stuck on the "android" boot loop (past the motorola logo) any help on restoring my phone??
The framework in the OP doesn't work with Eclipse Rom so I recompiled it from the eclipse framework. Same instructions as OP just different file.
So to recover, this is for Eclipse 1.1 no buttons
https://www.dropbox.com/s/5ruaj1rr6klmici/framework-res.apk
If I helped you out toss the OP and I a thanks plz :good:
Stock TB
Clienterror said:
The framework in the OP doesn't work with Eclipse Rom so I recompiled it from the eclipse framework. Same instructions as OP just different file.
So to recover, this is for Eclipse 1.1 no buttons
If I helped you out toss the OP and I a thanks plz :good:
Click to expand...
Click to collapse
I would like to do this for TB. Are you using apktools?
im running cm10 beta on my razr m and i found that simply adding "qemu.hw.mainkeys=1", to the end of your build.prop without the " then reboot. This will make the bottom nav bar disappear.
I found this by accident attempting to make the nav bar translucent so im not sure why it works, but it does for me.
theycallmekenny said:
im running cm10 beta on my razr m and i found that simply adding "qemu.hw.mainkeys=1", to the end of your build.prop without the " then reboot. This will make the bottom nav bar disappear.
I found this by accident attempting to make the nav bar translucent so im not sure why it works, but it does for me.
Click to expand...
Click to collapse
It causes systemui.apk to FC on stock based ROMS. Great for CM10 based ROMs.
From the RAZR M
hillmom said:
I would like to do this for TB. Are you using apktools?
Click to expand...
Click to collapse
Yea just decompile the framework from the rom you want and edit the lines in the op to all zeros. It's located in the "values/dims.xml" (I think). Recompile apk then drop in the meta folder from the original framework inside the new framework (I used 7zip). Just copy to phone, set permissions, and reboot.
Sent from my XT907 using Tapatalk 2
Clienterror said:
Yea just decompile the framework from the rom you want and edit the lines in the op to all zeros. It's located in the "values/dims.xml" (I think). Recompile apk then drop in the meta folder from the original framework inside the new framework (I used 7zip). Just copy to phone, set permissions, and reboot.
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I must be missing something because every time I try to recompile I get the error'
Could not find sources.
Never mind, I made a dumb noob mistake. Got it. Thanks!
hillmom said:
Thanks. I must be missing something because every time I try to recompile I get the error'
Could not find sources.
Never mind, I made a dumb noob mistake. Got it. Thanks!
Click to expand...
Click to collapse
No problem, after you do it once it isn't a big deal
Sent from my XT907 using Tapatalk 2
hillmom said:
Thanks. I must be missing something because every time I try to recompile I get the error'
Could not find sources.
Never mind, I made a dumb noob mistake. Got it. Thanks!
Click to expand...
Click to collapse
So what was the mistake you made when trying to recompile?
Sent from my XT907 using Tapatalk 2
sniperkill said:
So what was the mistake you made when trying to recompile?
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
I'm using APK Multi Tool, and I didn't install the framework-res.apk for 4.1.1 first.
Sent from my XT907 using Tapatalk 2
hillmom said:
I'm using APK Multi Tool, and I didn't install the framework-res.apk for 4.1.1 first.
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Oh, and okay. I know when jelly bean and ICS first came out everyone was having a hard time with recompiling the .apk's from ics and jb. I haven't tried it since. I'm assuming that they must have fixed all that by now?
Sent from my XT907 using Tapatalk 2
sniperkill said:
Oh, and okay. I know when jelly bean and ICS first came out everyone was having a hard time with recompiling the .apk's from ics and jb. I haven't tried it since. I'm assuming that they must have fixed all that by now?
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Yes, they did update them. I tried earlier with an older utility, and was getting really frustrated because I couldn't get the apk to recompile. APK Multi Tool os awesome, I need to play with the themeing tools it has.
Sent from my XT907 using Tapatalk 2
So here is my conundrum. I'm a crack flasher. I use CyanDelta to update CM11 every 3 - 5 days. When it runs I also have it install the EliteLunar kernel flashable zip and the exchangenopin zip. I'd like to create a flashable zip that would edit the build.prop file to change my DPI back to the 420 that I use instead of the mister magoo 480 stock. Is there a way to do this? I don't want to entirely reflash an old copy of the build.prop in case anything gets updated in the nightlies, I just want it to edit the single line with DPI.
Thanks!
PsyberEMT said:
So here is my conundrum. I'm a crack flasher. I use CyanDelta to update CM11 every 3 - 5 days. When it runs I also have it install the EliteLunar kernel flashable zip and the exchangenopin zip. I'd like to create a flashable zip that would edit the build.prop file to change my DPI back to the 420 that I use instead of the mister magoo 480 stock. Is there a way to do this? I don't want to entirely reflash an old copy of the build.prop in case anything gets updated in the nightlies, I just want it to edit the single line with DPI.
Thanks!
Click to expand...
Click to collapse
Use texdroider_dpi to modify DPI on your screen. Free in Google Play.
Use a root file explorer such as es file explorer. Set the system as read/write. Navigate to the build prop, make the change, reboot and bam you have your changed DPI.
Sent from my One using Tapatalk
I'm currently using ES File explorer. My goal was to make a flashable zip that I could include in CyanDelta to automatically change the DPI each time CyanDelta updates the OS.
See the problem you have is that what you want to edit is in a file and I don't think you can edit that file in the way you would like. You could make a flash able build prop but what if you overwrite the build prop cm provided in the update and break something as a result? Your best bet would be to manually edit the build prop or use the suggested app.
Sent from my One using Tapatalk
This is the command to edit the line in build.prop
Code:
sed -i '/ro.sf.lcd_density=480/c ro.sf.lcd_density=420' /system/build.prop
If you need me to i can make the whole flashable zip when i get some time, if you dont know how.
Basicly you just need to mount system and then give the above command.
Any text based files contents can be edited this way.
That's cool I didn't think you could issue a command to edit one line. Learn something new all the time. He should be able to add that to any of the updater scripts after the system partition is mounted and before it is unmounted.
Sent from my One using Tapatalk
Thats a little trick i picked up from tiny over on the droid incredible forums.
If you get the time to make a flashable zip of this that'd be simply amazing! I'm afraid that is a bit over my Android head
Here you go http://vzw1files.dyndns.org/MODs/LCD_Density_420.zip
cmlusco said:
Here you go http://vzw1files.dyndns.org/MODs/LCD_Density_420.zip
Click to expand...
Click to collapse
Many thanks! :highfive: Sent a beer your way...well...not an actual beer...but the paypal equivalent lol.
Thank you.
I happen to be looking for the exact same thing! However the link seems to be down at the moment, could @cmlusco or someone who has downloaded it put it up for download again? Thanks!
It is working now. Mabey it went down for a minute.
@cmlusco, do you mind uploading the zip again, but for a dpi of 400? The old link isn't working. I tried making it for my nexus 5, but it seems as though my binaries are messed. I`ve made other zips that work on android 5.0.2 though....
cmlusco said:
It is working now. Mabey it went down for a minute.
Click to expand...
Click to collapse
Could we get this put back up?
Also, 400 would be great
For those who still want to do this, this awesome zip file by @klenamenis will make any changes to build.prop that you specify. Just edit the tweak.prop file in the zip and flash the zip. I have Cyandelta automatically flash this zip each time I update. This saves me from having to set up all my widgets again after each nightly update because the resolution has changed!
http://forum.xda-developers.com/showthread.php?t=2664332