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.
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.
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
Hi S3 fellow users,
Yesterday i wanted to try some new rom so i flashed Darkys rom with siyah kernel, works fine but flashed back to stock because didnt like the rom, now it reboots itself everytime when its on the lock screen and by itself...
I flashed different stock roms and custom roms with odin for 15times, i wiped everything for 100 times.... dont know what to do? any tips?
I try to flash siyah kernel but that also didnt work.... is there something that can wipe everything and is not a odin flash or a wipe factory from recovery. Please help i need my s3:crying:
Try deleting the initd folder.might be conflicting scripts in that folder..
You'll find in system/etc,delete initd and reboot..
I have no other idea without more info.
zodiaxe66 said:
Try deleting the initd folder.might be conflicting scripts in that folder..
You'll find in system/etc,delete initd and reboot..
I have no other idea without more info.
Click to expand...
Click to collapse
Thank you:good:, i am try to do that but cant find initd in that folder also not anywhere else but i find other init files but not the initd. Is there any other way to clean such things up? atm i have stock 4.1.1 and latest siyah kernel, everything rooted su, busybox and root browers with all the tools installed running.
dimi22 said:
Hi S3 fellow users,
Yesterday i wanted to try some new rom so i flashed Darkys rom with siyah kernel, works fine but flashed back to stock because didnt like the rom, now it reboots itself everytime when its on the lock screen and by itself...
I flashed different stock roms and custom roms with odin for 15times, i wiped everything for 100 times.... dont know what to do? any tips?
Click to expand...
Click to collapse
Why not try another rom using stock kernel
ignatios123 said:
Why not try another rom using stock kernel
Click to expand...
Click to collapse
Thanks for your help but i did that, tryd different stock roms and didnt work
Did you do a wipe? Roms don't always transition /data smoothly from one to another.
Sent from my GT-I9300 using Tapatalk 2
xSpeced said:
Did you do a wipe? Roms don't always transition /data smoothly from one to another.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Yes i did 10 times wipe, i tryd different custom roms, and different stock roms, with odin and with cwm..
Now what i found out is that it only reboots when the screen is off so in lockscreen. if i hold the phone awake it wont reboot,
is there an tool to clean the whole system up? like intitd that i cant found in any way..
How could i delete all the mods that came from other roms? i cant find the initd folder...
My phone is on stock 4.1.1 siyah kernel, rooted, busybox, cwm recovery 6.0.1.2, have root explorer working.
I did wipe/factory reset, dalvik, fix permission, wipe batt stats, wipe cach flashing kernel/rom official and non official
and my phone keeps rebooting when the screen go's off auto or if i pres the power button.
Did you changed CPU voltage or clock settings earlier?
BTW you can remove files with ADB.
1) Boot into recovery
2) Connect USB
3) open ADB shell - 'adb shell'
4) navigate to the folder - 'cd /system/etc/'
5) Remove the files - 'rm -r init.d'
6) exit and reboot phone
Yes i did that early i try 1800 max in stweaks on siyahkernel and then the phone rebooted, dont know exactly what happend then but everything was fine after that... i also used other roms and kernels...
But thanks for your advice i will try to do this, i am new to ADB so i am going to figure that out right now.
is it possible to do that with cwm recovery on it?
That's what the problem is. I did it to my phone once. I overcolocked and undervolt.
Everything worked fine for few mins. But when I rebooted my phone, it went to lock screen and hang for few secs and then reboot again.
Never go to 1800 but a max of 1600. mine max is 1500 now.
Let me gather more info for you.
rl421403 said:
That's what the problem is. I did it to my phone once. I overcolocked and undervolt.
Everything worked fine for few mins. But when I rebooted my phone, it went to lock screen and hang for few secs and then reboot again.
Never go to 1800 but a max of 1600. mine max is 1500 now.
Let me gather more info for you.
Click to expand...
Click to collapse
Oke thanks very much for your help i realy appriciate that! but when i look inside the s tweaks my clock speed is just normal was that for you also?
Did you change any other settings in stweaks, voltage settings?
You can try some different kernel if your phone have problem with siyah.
rl421403 said:
Did you change any other settings in stweaks, voltage settings?
You can try some different kernel if your phone have problem with siyah.
Click to expand...
Click to collapse
No i think not, but atm i did a fix permisson and now the phone is not rebooting but it takes about 5 seconds for the screen to turn on when the screen is of in lockscreen. i am very confused
Guys i there any way to clean every bit of **** that could be on the phone like init.d??? please help
Had same thing happen to me, my fix, 1st save everything to pc from sdcard and titanium backup if you can. Flash stock rom and then put (i use omega v34) on external sdcard. Flash touch recovery. Wipe cache and dalvik, fact reset then go to usb mount and format everything (except external card obviously) then flash omega rom.
Sent from my GT-I9300 using xda premium
jj92942000 said:
Had same thing happen to me, my fix, 1st save everything to pc from sdcard and titanium backup if you can. Flash stock rom and then put (i use omega v34) on external sdcard. Flash touch recovery. Wipe cache and dalvik, fact reset then go to usb mount and format everything (except external card obviously) then flash omega rom.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
THank you but i try out this before, nothing works..... :crying:
I didn't read that you formatted your card before, that wipes any conflicting setting, otherwise might be hardware related.
Sent from my GT-I9300 using xda premium
jj92942000 said:
I didn't read that you formatted your card before, that wipes any conflicting setting, otherwise might be hardware related.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I just try the exact method you say just to be sure but the same problem remains, i wiped everything that i could but it remains the phone reboots when the screen is off or it dont reboot but it freezes when the screen is off.
I dont think of hardware related problem because when i keep the screen awake i can do whatever i want without problem....
Hey All-
I cracked my N4 screen for the 3rd time and am using a buddy's Atrix 4g with firmware 4.15(ish) as a loaner... Here's my deal- I used the auto rooter/CWM-installer (I think it installed CWM 4.0.0.2. Everything went fine- it was rooted and fully functional. I should have updated the recovery, but anyway....
I made a backup in CWM recovery and I decided to flash epinter's CM10.1 zip file. I don't know if there is something I missed, but I wiped everything and installed... But it 'installed' wayyyy too fast- it looks like the CWM version I have installed the zip as an update or something, and of course, when I rebooted the phone, nothing happened for about 5 seconds- it just stayed on the unlock/dual core logo screen. But then the screen sort of zoomed in and distorted/it looks like there is a reflection of the dual-core/unlocked logo.. Kind of hard to explain. But it's frozen in place. Nothing happens.
So I reinstalled my backup- it takes a while to install as it should, but when I reboot, the same thing happens- it looks like it's going to boot, and then the screen just distorts and stays that way.... What on earth would make my backup not work??
All that said, I can still access CWM recovery.
Any thoughts on where I should go from here?
Zac
Update your recovery to cwm 5.0.2.x
Sent from my MB860 using xda app-developers app
What would be the best way to do that?
Download img, flash via fastboot. Done.