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!
Related
hi,
I installed a new Rom (hyperdroid 5.2.1) after installing many Roms before.
always doing the same procedure.
but this time when i try to restore my User apps it keep doing reboot every once in a while. (it happen more then once or twice).
has any one encounter this behavior?
and yes i checked "unknown sources", and it's after a full WIPE.
Thanks.
Have you tried toggling Settings > applications > Development > USB debugging on/off?
i made sure it's on (if not titanium yell at you)
Barakfel said:
i made sure it's on (if not titanium yell at you)
Click to expand...
Click to collapse
Well yes, but sometimes titanium doesn't want to play ball until you toggle it, at least for me.
I'll try, but i really don't think this is the problem since it does succeed in restoring until it reboots.
any other suggestion?
Barakfel said:
I'll try, but i really don't think this is the problem since it does succeed in restoring until it reboots.
any other suggestion?
Click to expand...
Click to collapse
What kind of reboot, does it reboot to boot animation or boot logo?
It reboot back to boot animation. (feel like a quick boot)
Sent from my GT-I9100 using XDA App
Barakfel said:
It reboot back to boot animation. (feel like a quick boot)
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Thats a rom crash, what rom are you on? Also your best bet is to hook your phone upto your computer and use adb to get logs upto the crash otherwise goodness knows whats happening.
OK that's a start .
I'm using hyperdroid 5.2.21 or trying to use.
Do you have a guide on how to pull the log?
Sent from my GT-I9100 using XDA App
Barakfel said:
OK that's a start .
I'm using hyperdroid 5.2.21 or trying to use.
Do you have a guide on how to pull the log?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
This should cover it: http://forums.miui.us/showthread.php?113-How-To-Install-ADB-and-Logcat
You want to pull the logcat to file.
Start it up, then do what you do to make it crash, then post a pug report in the hyperdroid thread with that logcat attached.
Good bug report:
Rom version
Kernel version
What happens: (eg I start restoring backed up apps, after X time it crashes the phone to the boot logo)
Any mods installed: (eg surgeons)
Any other info:
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?
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....
Hello,
I have flashed a few custom ROMs onto my x10i and each time it reaches the lock screen when it starts up it just seems to go into a reboot loop from kernel splash screen to lock screen again. Is there any fix for this ? I have tried using SEUS and restarting the whole process of flashing a kernel, rooting etc but it doesn't seem to work. it literately only happens when it reaches the lock screen. sometimes it lasts longer than that. Whenever I wipe the system it seems to work fine but as soon as a few things are running it starts to reboot again. The current ROM I'm running is PAC-man, with the kernel supplied along with it.
Could anyone help me ?
Thanks,
mmy4life
I have the same problem
use the phone until the battery become empty charge it in off mode up to 100 enter in xrecovery advanced options wipe battery stats and reboot
maybe you did an error when flashing or it runs wrong kernel. my suggestion : just use another ROM there are many nice ROM you can choose, and dont forget to follow step by step installation guide provide by developers.
Is the rom overclocked as this can can happen on some devices try and set the CPU to 998
Sent from my Google Nexus S
mmy4life said:
Hello,
I have flashed a few custom ROMs onto my x10i and each time it reaches the lock screen when it starts up it just seems to go into a reboot loop from kernel splash screen to lock screen again. Is there any fix for this ? I have tried using SEUS and restarting the whole process of flashing a kernel, rooting etc but it doesn't seem to work. it literately only happens when it reaches the lock screen. sometimes it lasts longer than that. Whenever I wipe the system it seems to work fine but as soon as a few things are running it starts to reboot again. The current ROM I'm running is PAC-man, with the kernel supplied along with it.
Could anyone help me ?
Thanks,
mmy4life
Click to expand...
Click to collapse
That usually happens when the ROM is using overclocked CPU settings or an unstable CPU governor as default but it can also be defaulted inside the kernel. You simply flash another kernel and appropriate ROM.
CCVader13 said:
That usually happens when the ROM is using overclocked CPU settings or an unstable CPU governor as default but it can also be defaulted inside the kernel. You simply flash another kernel and appropriate ROM.
Click to expand...
Click to collapse
I've tried this multiple times, it happens on the stock ROM and kernel.
mmy4life said:
I've tried this multiple times, it happens on the stock ROM and kernel.
Click to expand...
Click to collapse
Install xrecovery and wipe the dalvik cache.
Sent from my Xperia X10 using xda app-developers app
CCVader13 said:
Install xrecovery and wipe the dalvik cache.
Sent from my Xperia X10 using xda app-developers app
Click to expand...
Click to collapse
I've also tried that. I went through all the proper procedures when installing a new rom.
mmy4life said:
I've also tried that. I went through all the proper procedures when installing a new rom.
Click to expand...
Click to collapse
Then it has to be a hardware problem. Try removing your SD card before booting it up.
Sent from my Xperia X10 using xda app-developers app
I've had the same problem
1eyedmonster said:
Is the rom overclocked as this can can happen on some devices try and set the CPU to 998
Sent from my Google Nexus S
Click to expand...
Click to collapse
I flashed 2.3 and it kept rebooting after a while, so i re flashed 2.1 and it is more stable but reboots if i open a app or anything that uses ram.
btw 1eyedmonster how do you set the CPU to 998?
I am also having ths reboot and crash issue... is there no fix for it? I have read about this reboot error at numerous sites. Must be a bug or summin man... or we dn summin wrong... and if it were hardwars related then to what hardware wd you be referring to? Is it a replaceable part? How easy wd such a task honestly be... i have 2.3.3 with 3.0.0.75 and no matter what it just wont stop dropping itself while i just start to appreciate it all over again... so im sure there have bn plenty issues regards this... so is there an answer?
Sent from S3Terry, Galaxy SIII GTI9300, using 8ta/Telkom Mobile.
reboot issue
mmy4life said:
I've also tried that. I went through all the proper procedures when installing a new rom.
Click to expand...
Click to collapse
hi,
i have the issue, did you fixe your phone ?
thank