I was playing with DPI and after reboot it just get stuck in black screen.
I have tried to adb push a stock build.prop I found in the forum, but it doesn't help.
I would not really like to have to reflash the phone.
I believe the only file changed with the DPI programs is build.prop. Should I look somewhere else? Can somebody upload me an stock build.prop file?
thanks
EDV11 said:
I was playing with DPI and after reboot it just get stuck in black screen.
I have tried to adb push a stock build.prop I found in the forum, but it doesn't help.
I would not really like to have to reflash the phone.
I believe the only file changed with the DPI programs is build.prop. Should I look somewhere else? Can somebody upload me an stock build.prop file?
thanks
Click to expand...
Click to collapse
You might look here to fix it with adb http://forum.xda-developers.com/showthread.php?t=1927198 or here http://forum.xda-developers.com/showthread.php?t=1797864 , haven`t used it myself. Good luck.
Thanks, you were right, it was a permission problem
Sent from my iPad using Tapatalk
Related
Posted this earlier in themes.
Can we adb push to /system/fonts ?
I think we have to be booted in recovery for this to work ?
Correct me if I am wrong.
Thank you.
pman219 said:
Posted this earlier in themes.
Can we adb push to /system/fonts ?
I think we have to be booted in recovery for this to work ?
Correct me if I am wrong.
Thank you.
Click to expand...
Click to collapse
I've done this using the app Typefresh. It has a thread in the Android software forum here at xda somewhere.
With root, you can replace the fonts, yes.. backup your old ones just in case!
.mak said:
With root, you can replace the fonts, yes.. backup your old ones just in case!
Click to expand...
Click to collapse
I attempted this yesterday.
Mind giving a quick walkthrough ?
I basically did:
su
adb push "c:\fonts" /system/fonts
No joy- Got back adb can not be found ??
TYIA
The way I got this done is with Typefresh. There is a thread about this in here: Android Development and Hacking>Android Apps and Games>[APP]Type Fresh - change your fonts!
(Sorry, I can't post links yet. If someone else wants to repost it as a link, help yourselves.)
What I did was download a font (a Harry Potter font is not installed from the factory--heehee) and adb push it to /sdcard/Fonts. Then I opened Typefresh and click the font you want changed, in my case it was DroidSans.ttf, and it allows you to choose the font you want to change it to. I will note here that apparently some fonts do not work well and may result in a brick. DO NOT DO THIS IF YOU ARE NOT COMFORTABLE DOING IT, YOU MAY BRICK YOUR DEVICE. Luckily, there is a fix for that now.
Anyway, thanks to openback for the app.
I forgot to mention that you also need to dl andexplorer to use this app. I personally did not have a root explorer hitherto so that was fine for me.
Now my question is, how can i change the font for the homescreen, or launcher pro in my case, but leave the browser's font stock?
Hey Guys, I updated and rooted my phone to 2.3.4 HK...
Anyways, I remember seeing a post about an app that lets you enable the whole screen.
It appears that I have some dead space on the main home screen and I can not place any widgets in it (Its in the bottom)...
Any way I can fix that ? I cant remember the app name for the life of me.
thank you,
Alex
Hey, just use root explorer or shell in order to edit the build.prop in your system folder (or just use CWM and mount your /system folder to your computer). in the build.prop, there is a section that describes the ppi and for some reason, it's set as default to 240. Change it to 275 and it should fix all screen issues.
thanks for your response!! I checked thru Root Explorer, and only found
dpi... not PPI.. is that what you meant? Cause I see that listed as 240.
Also, do I need to reset after the edit?
Thanks a lot!!
The stock launcher seems to be messed up, get a different launcher.
Sent from my MB860 using XDA App
Some people have complained about the resulting effects of changing the build.prop file with this fix. Better to just use a different launcher than stock as was said.
LCD density for root I believe it is the 270 setting you need to select.
Sent from my MB860 using XDA App
So guys...after surfing many websites..restoring my nandroid backup for almost 10 times i finally found a safe way to edit the build.prop file.. I don't exactly know if this happens on other android smartphones but whenever you try to edit the build.prop file via any editor on your phone or in my case even via adb i get bootloops...
So i tried remounting system and then unmounting it...i tried many file editors file explorers but every time what i got was a god damn phone stuck at the galaxy s2 logo
And also i would mention that I SEARCHED OVER XDA TOO!!.....the guys had great tools developed but they did not work in my case either.
So no more talkingss.....just how to do it...its rather very simple...you just need an app called Rom Toolbox...its free as well as paid too...download as per your requirement.. AND obviously YOU NEED ROOT.
Well open it(duh) and go into the performance tab and select the build.prop editor...well i will explain you what these values stand for...i am not going to explain each and every value but the ones you would require...leave the unlisted in the comments...
ro.build.date - Change your roms build date
ro.build.description - Your phone's description
ro.build.display.id - Change the build no.(dont use it on custom roms....respect the devs)
ro.build.product - Change your model number....
ro.build.version.release - change the android version(not really actually )
ro.product.brand - Phone's company (Samsung in my case)
ro.product.device - Change the device name
ro.product.model - change the model number
ro.sf.lcd_density - Change the lcd density(dont ask me what it is...google it)\
So guys dont change the values out of range like setting lcd density to 5000...or anything else...and also if anything happens to your phone I AM NOT RESPONSIBLE....
also this is my first thread so guys bear with me....i am a new semi pro java developer i would really like to contribute....
build.prop editing = Root Explorer, long press, open in text editor...
karendar said:
build.prop editing = Root Explorer, long press, open in text editor...
Click to expand...
Click to collapse
+1
Sent from my GT-I9100 using XDA
Or build.prop editor from the market.
Never had any trouble editing the LCD Density with root explorer :/
B3311 said:
Or build.prop editor from the market.
Click to expand...
Click to collapse
I second this.
I had bootloops....
I had bootloops dont you guys read.......!! I used root explorer...and text editor too
May be its the rom thats causing problems......
rohan999 said:
I had bootloops dont you guys read.......!! I used root explorer...and text editor too
May be its the rom thats causing problems......
Click to expand...
Click to collapse
Check for ownership and permissions before restarting. They are probably messed up and are causing bootloops. Or you made a typo somewhere and cause bootloops that way. Root Explorer always works fine for me.
No bootloops here either using root explorer or rom toolbox
Sent from my GT-I9100 using Tapatalk
rohan999 said:
I had bootloops dont you guys read.......!! I used root explorer...and text editor too
May be its the rom thats causing problems......
Click to expand...
Click to collapse
Maybe it's you bro
Sent from my GT-I9100 using xda premium
Please be dont be too hard on him. And i heard someone said it needs to be edited at two places sometimes, but i didnt read the threaded comments till the end. Its lost now. I guess thats that the thread starter means. On some roms, it caused bootloops. Is there any special thing to be taken care of cuz bootloop does happen on certain roms when u edit the build.prop on certain custom roms? On stock deodexed roms, no issues for me
Sent from my GT-I9100 using xda premium
The OP is definitely onto something, because it happened to me.
Specifically, I was trying to edit the DPI setting. Out of the stock ROM, the lcd_density setting was present twice in the file (kind of strange, but oh well - normally it shouldn't cause problems). Edited from 240 to 200 without typos, I'm not allowed to do that due to my line of work , reboot, bam! boot loop.
Replaced the build.prop from backup, edited with "build.prop Editor" from Market - no problems. Really don't see what was the difference, except the duplicated key which was gone after editing with build.prop Editor (probably it does some sort of unique key checking). Oh well, not serious enough to investigate further.
VAXXi said:
The OP is definitely onto something, because it happened to me.
Specifically, I was trying to edit the DPI setting. Out of the stock ROM, the lcd_density setting was present twice in the file (kind of strange, but oh well - normally it shouldn't cause problems). Edited from 240 to 200 without typos, I'm not allowed to do that due to my line of work , reboot, bam! boot loop.
Replaced the build.prop from backup, edited with "build.prop Editor" from Market - no problems. Really don't see what was the difference, except the duplicated key which was gone after editing with build.prop Editor (probably it does some sort of unique key checking). Oh well, not serious enough to investigate further.
Click to expand...
Click to collapse
How did u replace it with ur backup? I normally restore back my nandroid. Is there a much simpler way such as putting it in an update zip or something? Mind to share?
Sent from my GT-I9100 using xda premium
kyleforge said:
Maybe it's you bro
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
bpivk said:
Check for ownership and permissions before restarting. They are probably messed up and are causing bootloops. Or you made a typo somewhere and cause bootloops that way. Root Explorer always works fine for me.
Click to expand...
Click to collapse
override182 said:
Please be dont be too hard on him. And i heard someone said it needs to be edited at two places sometimes, but i didnt read the threaded comments till the end. Its lost now. I guess thats that the thread starter means. On some roms, it caused bootloops. Is there any special thing to be taken care of cuz bootloop does happen on certain roms when u edit the build.prop on certain custom roms? On stock deodexed roms, no issues for me
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
thank you really mate....you are not like the others who just need a reason to insult.....well this is my first thread...so its noobish....but i am a programmer (java) so i will be bringing some good roms later..
override182 said:
How did u replace it with ur backup?
Click to expand...
Click to collapse
I made a copy of /system/build.prop before editing it, of course. After rebooting and getting the bootloop, it's just replacing this file from the backup copy.
I've been using build.prop editor from Nathan Campos, 0 issues so far.
VAXXi said:
I made a copy of /system/build.prop before editing it, of course. After rebooting and getting the bootloop, it's just replacing this file from the backup copy.
Click to expand...
Click to collapse
Im still not clear on this. How did u managed to replace when u cant boot the device and edit it back again to the working build.prop. Did u push back via adb or some update.zip?
Sent from my GT-I9100 using xda premium
The device boots just fine, it just doesn't complete the booting process and remains at the spinning S with blue particles. You can use ADB during that time.
VAXXi said:
The device boots just fine, it just doesn't complete the booting process and remains at the spinning S with blue particles. You can use ADB during that time.
Click to expand...
Click to collapse
Noted. Thx
Sent from my GT-I9100 using xda premium
rohan999 said:
thank you really mate....you are not like the others who just need a reason to insult.....well this is my first thread...so its noobish....but i am a programmer (java) so i will be bringing some good roms later..
Click to expand...
Click to collapse
Most of us didn't insult. Don't jump the gun. Just giving the other side of the coin. Root explorer editing works fine, as others have stated it's possibly a messed up rom giving weird permissions to build.prop. chmod 644 build.prop usually solves the issue though.
I can't speak for everyone, but I wasn't hard on you... Noobs are noobs and I'm fine with that. Most info is readily available on the forums though... Just not necessarily on this forum. XDA is bigger than the sgs2 forums and other communities have very interesting ideas and threads!
***edit*** yeah, after re-reading, noone was harsh in any way. So... yeah!
Sent from my GT-I9100
can someone take the time to school a noob on DPI? I change the dpi n my ro.build and I see no difference... pretty sure I am misunderstanding some part of it.
From my understanding you change the build.prop... save and exit the text editor (must be rooted) and restart the device... I've been using that method on my galaxy nexus and now nexus 7 and it works perfect... think of lowing the dpi as in tricking the OS into thinking you have a bigger screen than you actually have... thus making everything smaller and also triggering tablet mode
No I've been there and done this too. If you open and save the file... then open it back up, the changes are reverted. Yea I was rooted and was using root explorer. Once I flashed a custom rom, I could change it no problem. Maybe something with stock rom or something else not allowing the file to change, even though the folder is R/W and all that.
The file keeps reverting back after you save it.
Sent from my Nexus 7 using xda premium
player911 said:
No I've been there and done this too. If you open and save the file... then open it back up, the changes are reverted. Yea I was rooted and was using root explorer. Once I flashed a custom rom, I could change it no problem. Maybe something with stock rom or something else not allowing the file to change, even though the folder is R/W and all that.
The file keeps reverting back after you save it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
It should work if the folder is R/W and you save and exit. Maybe you should try es Flie Explorer?
I was rushed while posting that and I believe I was completely unclear. I did edit the you Build.prop, I am on a custom rom sgt7 and the dpi and build.prop and DPI was 213 I think maybe 216, I changed it to 180 and I saw no difference at all. this is possibly because there are other modifications to the Rom that aren't dpi dependent or something.
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 !