Can you change the lcd density on stock rom? On my droid 2 I could only do it on custom roms. Whenever I tried on stock i would end up on a black screen and have to sbf.
Sent from my ADR6400L using XDA App
It worked when I did it by editing the build.prop using Root Explorer. You should probably do a backup just to be safe though.
I made a back up and changed build prob. Changed it to 220, reboot and got stuck in a boot loop.
Hmm... it works on 224 and 192 for me, but I haven't tried 220.
Maybe clearing the cache/dalvik-cache would help? I'm not sure. Weird.
Related
Hey guys. I changed my lcd dendity from 240 to 200 in the build.prop file in root explorer, restarted and now I just get a blank screen that vibrates. Any way to fix this without re flashing? I have a vibrant running the new froyo update.
Sent from my GT-P1000 using XDA App
can anyone help?
I think you have same situatuion that i got...
now I cannot turn on my cell phone and I cannot fix it....
I tried a lot of ways to solve that but I wannot able to... it's horrible...
Ended up just reflashing. Grab the stock 2.2 tar here http://forum.xda-developers.com/showthread.php?t=919687, put your phone into download mode and use odin to flash. Booted up as good as new.
Hi, my phone locks when I set the CPU over 652800, it freeze continuosly, often he can't manage to pass the LG logo and if I let it go, after a while it reset and it keep freezing and restarting over and over again.
The only way I can go on is to keep it cold with ice, and as soon as it start I jump into cpuclock, if it doesn't lock again, and then I change the settings and restart.
From this point on the phone works correctly. The problem is that almost all the ROMs set the clock above 652800, so everytime I change the ROM I have to spend much time to make the phone work again.
I suppose that some of the people complaining for phone stuck on LG logo may have my same problem.
Is there a way to set the cpu clock at 652800, some sort of zip file to apply after the ROM in recovery, or some commands to launch thru ADB before restarting?
Thank you very much
which rom you are using
samrox144 said:
which rom you are using
Click to expand...
Click to collapse
I've tried IRIDIUM, GINGERFORN, AGAROM, GINGERCRIME, GINGERLOL, OPENOPTIMUS, etc..
Right now I'm using IRIDIUM with new baseband.
Change the kernel and try i am using iridium no problems
Or set cpu to 600 and mark set on boot.try ...
Sent from my LG-P500 using XDA App
samrox144 said:
Change the kernel and try i am using iridium no problems
Or set cpu to 600 and mark set on boot.try ...
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
The problem is that I can't manage to reach cpuclock when I install a ROM. By default the roms are above 700000 and this make my phone freeze, maybe it's more delicate than yours.
Resolved, FYI
Resolved!
matteof93, from IRIDIUM ROM tell me the solution.
In the zip file i edited system -> etc -> init.d -> 05cpu and wrote 600000 in the maximum value.
Saved it back and installed. All it's ok now!
I am using Wanam 9.0 but I have seen other similar posts from other custom roms from people saying that editing build.prop results in bootloop.
I tried removing the second line that had the lcd density, keeping only one with my new lcd.density settings, but it resulted in bootloop.
I tried cache, dalvik, fix permissions... nothing helps.
Any ideas?
I suggest to flash your rom again or make nandroid, flash rom again and restore data
Sent from my sgs2 running cm9 using xda app
It could depend on ur density-level. Some roms have problems with less than 183dpi.
Sent from my GT-I9100 using xda premium
Siemser said:
It could depend on ur density-level. Some roms have problems with less than 183dpi.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I only tried some values above 200
Having the same problem, restored backup.
You can also push the backed up original build.prop to it's original directory via adb shell.
Look here http://forum.xda-developers.com/showpost.php?p=23438841&postcount=11877
Well.. that thing won't work.
The problem is that some changes are being made to build.prop and then it goes into bootloop.
The SUPER EASY way to change DPI, is to have a copy of the build.prop from your custom rom. Extract it from zip, change value, paste it in /system/ --->>> SUCCESS
blue265 said:
Ok I've confirmed it by installing LPQ, rooting and changing LCD density. As mentioned, there are two 'ro.sf.lcd_density=240 locations in build prop. Change both of them to desired density level. I changed both of mine to 210 and after a reboot, the LCD changed without issue and a lot smaller.
Click to expand...
Click to collapse
Apparantly, this ^
Havent tried it though
blue265 said:
I know on LPH and a few other ICS roms that the build prop has two locations you need to set the LCD Density. If you changed one already, look for the other one as there should be two locations within build prop.
Click to expand...
Click to collapse
dyallo said:
Apparantly, this ^
Havent tried it though
Click to expand...
Click to collapse
Well... no. That might be one cause of the problem but in a couple of roms I tried, there was only one line. And still it got a bootloop.
I am telling you.... THIS--->
jastonas said:
The SUPER EASY way to change DPI, is to have a copy of the build.prop from your custom rom. Extract it from zip, change value, paste it in /system/ --->>> SUCCESS
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=23438841
The instructions there nailed it for me. I used to use dpi changer from the market but it doesn't work with the official ics.
I had to reflash the official ics to fix it.
Sent from my GT-I9100 using XDA
LG optimus 2x p990 stuck in bootloop
Deal All,
i am new to XDA and having issue with my LG O2x.
I had manged to upgrade LG O2x on ICS and it was running fine, but last Saturday i tried to check update via LG update tool, it says update available, when respective file download completed, O2x started in boot-loop.
I am not able to figure out what went wrong and how to solve it ?
As i was not prepared all so no backup of ROM, no developer mode ON and top of that i am not able to get into recovery mode by precessing volume down + Power button.
i can only enter in software upgrade mode, can anyone help me out ?
Thanks in advance !
Rajesh
Hey Guys,
I am using system tuner to OC/UV my Note, but once I turn off my phone it doesn't seem to stick. I have checked off all the boot settings to reapply on boot completed, but when I restart the phone it goes to the default settings. Am I the only one with this problem or is this something common with system tuner... or am I just an idiot and doing something wrong?
Thanks
PS- I am running Saurom VI
I had issues with it on and off...seems to be working now
Sent from my SAMSUNG-SGH-I717 using XDA
Im experiencing the same thing. Stock Telus with Oc Kernel and CWM
Would be nice if its settings actually saved lol...
VinceG said:
Hey Guys,
I am using system tuner to OC/UV my Note, but once I turn off my phone it doesn't seem to stick. I have checked off all the boot settings to reapply on boot completed, but when I restart the phone it goes to the default settings. Am I the only one with this problem or is this something common with system tuner... or am I just an idiot and doing something wrong?
Thanks
PS- I am running Saurom VI
Click to expand...
Click to collapse
Soooo... what was the answer for this?
I got an i9100m here which I attempting to change the dpi using LCD modder. I changed it to 160, but it would not reboot successfully.
The phone is on stock 4.0.3 and is rooted, is there a way I can alter the build.prop from my computer and get it to boot again?
Also, whats a better way to change the dpi into something smaller?
edit: I booted into CWM and wiped cache/dalvik, its still hanging on the boot screen though.. hmm.
If you can get to download mode re-flash your stock ROM or via CWM restore a back up. I've used Density Modder a lot and never had a problem. I think 160 is too small, the I9100 has a minimum dpi of around 182. Make sure the ROM you choose is the right one for your I9100 variant.
Sent from my GT-I9100 using xda app-developers app
Yes I can do that but I do not want to lose data so I am going to adb pull the build prop, change it back, then push it.
edit: and, it adb wont recognize it in recovery for some reason.
whatever, fixed it. just reflashed stock firmware on odin,