I'm running the dual boot with phiremod 6.2 on SD. I tried to update the kernel to the 04242011 version and after setting OC to 1200 or 1300, it immediately freezes. I did the update from recovery and wiped cache and dalvik. Am I sol with a bum CPU?
Sent from my ADR6400L using XDA Premium App
after it froze up, did you try to just power down by holding the button, then just try to boot back up normally?
i've set my OC too high a few times back when i was first testing it out on my device and the same happened.
My NC can only handle up to 1100
But everytime i reflash a new kernel or build, i still try my luck with 1200 and it'll freeze up randomly then i just power down and reboot
djlim4 said:
after it froze up, did you try to just power down by holding the button, then just try to boot back up normally?
i've set my OC too high a few times back when i was first testing it out on my device and the same happened.
My NC can only handle up to 1100
But everytime i reflash a new kernel or build, i still try my luck with 1200 and it'll freeze up randomly then i just power down and reboot
Click to expand...
Click to collapse
Yup. So this is weird,i actually updated to phieremod test build then upgraded the kernel to 0618 and1200 works great.
Sent from my ADR6400L using XDA Premium App
My nook was freezing constantly at 1100, but never does as 1200. Might be a stepping issue.
Related
Im having an unusual problem when i flash any of the Stupidfast kernels, right now I am on the test version of v1.0.36, i tried to flash the stable version as well as the UV kernel and the v1.1.4. When i tried to flash the stable version i was able to boot up fine but i have an issue where it freezes when my media scanner runs and the only remedy is to do a battery pull. the same thing happened when I tried the UV kernel, I think my phone doesnt like UV kernels anyways so im not too concerned with that one, I am running setcpu with min at 100 and max 1000 on conservative. Im just curious if any one else had has this issue with the freezing. Any help would be appreciated!
civicr6 said:
Im having an unusual problem when i flash any of the Stupidfast kernels, right now I am on the test version of v1.0.36, i tried to flash the stable version as well as the UV kernel and the v1.1.4. When i tried to flash the stable version i was able to boot up fine but i have an issue where it freezes when my media scanner runs and the only remedy is to do a battery pull. the same thing happened when I tried the UV kernel, I think my phone doesnt like UV kernels anyways so im not too concerned with that one, I am running setcpu with min at 100 and max 1000 on conservative. Im just curious if any one else had has this issue with the freezing. Any help would be appreciated!
Click to expand...
Click to collapse
I'm having the same problem. But only when I plug in USB while media scanner is running. I'm using the most recent stupidfast kernel 1.2.3. I have to wait until the media scanner is done then plug in the USB, but have to be patient. If I try to do too much too fast..... freeze.
I wish thats all i had to deal with, i dont even touch my phone and it freezes all on its won, and for some reason my media scanner runs twice, and its always on the 2nd time when it freezes.
My phone always ran media scanner twice, before root and now, have u tried wiping ur phone reinstalling kernel and rom and then use titanium to restore apps?
Sent from my SCH-I500 using Tapatalk
I have done a full wipe on my phone and it is still doing it, maybe my phone doesnt like being played with ha ha. im not running any rom, just root and a kernel
I've been using Mikfroyo 4.5 for a few weeks now and finally decided to flash a kernel. I chose this one here
http://forum.xda-developers.com/showthread.php?t=719763&highlight=rebooting
I think I am using clockworkmod recovery and I've been using rom manager to flash my roms and Mikfroyo had a built in reboot to recovery feature that I used to reboot my phone into recovery to flash the new kernel. I did not delete dalvik cache or anything I think. I'm not entirely sure. So when i tried to set the cpu to the max that it would allow it froze twice. and i rebooted each time and chose a different setting. I also saw a setting that said "set at boot" and i chose yes for that option. After a random reboot it seems to freeze just after the lockscreen shows up and it starts setting up the sd card. I have held down the power and raise volume button and nothing happens. And I have also tried the hold down power and lower volume button and nothing happens. Am I supposed to do both volume buttons at the same time? How can I fix my phone? It is completely unusable right now. Please help!!
sent17inel said:
I've been using Mikfroyo 4.5 for a few weeks now and finally decided to flash a kernel. I chose this one here
http://forum.xda-developers.com/showthread.php?t=719763&highlight=rebooting
I think I am using clockworkmod recovery and I've been using rom manager to flash my roms and Mikfroyo had a built in reboot to recovery feature that I used to reboot my phone into recovery to flash the new kernel. I did not delete dalvik cache or anything I think. I'm not entirely sure. So when i tried to set the cpu to the max that it would allow it froze twice. and i rebooted each time and chose a different setting. I also saw a setting that said "set at boot" and i chose yes for that option. After a random reboot it seems to freeze just after the lockscreen shows up and it starts setting up the sd card. I have held down the power and raise volume button and nothing happens. And I have also tried the hold down power and lower volume button and nothing happens. Am I supposed to do both volume buttons at the same time? How can I fix my phone? It is completely unusable right now. Please help!!
Click to expand...
Click to collapse
You can try reflashing Mikfroyo 4.5 without wiping and see if you can recover, or just flash another kernel over what is currently installed to reset setcpu. It's not wise to enable "set at boot" until you are sure that your settings are stable.
How can I flash a new rom or kernel if I can't get it to fully boot? It gets to the lock screen and then reboots. I have tried the holding down power button and volume and nothing happens. It still continues to boot up.
nandroid backup or full data wipe. Other than that fast fingers and you gotta hurry to the app and turn of start at boot before it starts loopin
chandlerw88 said:
nandroid backup or full data wipe. Other than that fast fingers and you gotta hurry to the app and turn of start at boot before it starts loopin
Click to expand...
Click to collapse
No way it would let me get that far. I've tried.
Soo nandroid backup or full data wipe. Either sound fine with me. How do I do that though?
Pull out battery, wait a couple seconds to put it back in, and press power and volume down until white screen shows up. You should know the rest.
It sounds like your messing around with a lot of things you don't know about. Before you do anything like majorly over clocking CPU Research it first
Sent from my Superphone. (Evo)
chandlerw88 said:
nandroid backup or full data wipe. Other than that fast fingers and you gotta hurry to the app and turn of start at boot before it starts loopin
Click to expand...
Click to collapse
Ha, had to do that a few times myself. Gotta be very quick lol.
Sounds like you aren't holding down the volume button if its starting up normally. Set CPU wouldn't have messed up your recovery. Hold down the volume button before pressing the power button and don't let go untilled the white screen pops up. Then you can reflash mikfroyo.
That was all I needed. I looked up a couple ways on how to get into recovery and they were all very vague. I didn't know that you needed to initially hold down power button and volume. I was initially tapping the power button and then holding power and volume. But I should be able to take it from here. Thank you everyone for you speedy responses!!!
When you flash a kernel you are supposed to clear cache and dalvik or else you will get the issues you described.also running set cpu at max can cause instability and random reboots.
Most 1gHz devices will only support overclocking around 1.9 before coming unstable. do as the thread says FULL WIPE, reflash rom, flash kernel, boot, then when adjusting set cpu dont "set on boot" until you have tried it out first.
pureEVO91 said:
Most 1gHz devices will only support overclocking around 1.9 before coming unstable. do as the thread says FULL WIPE, reflash rom, flash kernel, boot, then when adjusting set cpu dont "set on boot" until you have tried it out first.
Click to expand...
Click to collapse
A 1Ghz device at nearly 2Ghz! That's an awesome overclock!!! How stable?
Its completle stable in a powered off state!!!
Sent from my PC36100 using XDA App
^^^ yeah... lol
1.19 is best I can do on my evo.. before lockup/reboot.
i wish we can do 1.9
OP.. sounds like you got it handled...
and was able to get into recovery. I hate ROM manager... because of this kind of issues.. you did not really know how to do it manually.
to a nandroid restore or flash the ROM again (only wipe cache and dalvik) should fix it.
I did the same thing when i first tryed to overclock my last phone and checked "set on bootup". Learned.. never do that till I am 100% sure it is stable.
I was a noob back then.. and what I did was put my phone in the freezer.. then raced the clock before the cpu overheated and locked up. LOL silly.. but it worked.
hah. Our evos don't have enough of a heat sink to reach 1.9ghz
Wow. Sry guys didn't mean to miss post. 1.19gHz
Oh ok 1.19 sounds alot better. I was lookin like 1.9 WOOOOOOOOW!!!! I wish mine would go that fast.
I had the same problem as you b4. Netarchy's kernel doesnt like overclocking. Looks like your good tho....
I have installed http://forum.xda-developers.com/showthread.php?t=1382999 kernel and now when I turned off my Kindle it won't turn back on when I press the power button it goes green for a second and then go clear. Can someone people help. Thanks.
Edit: I figured out the problem... After shutting down i have to hold the power button for 20 seconds and then turn it on... Anyone know why this is happening?
sleep of death
This is called sleep of death. Unfortunately, it happens a lot. I had the exact same problem. To fix it. Just reflash your Rom from twrp, wipe cache and dalvik cache. Do not wipe data. Reboot and that should take you back to the original kernel that came with your rom. What rom are you on?
I am using stock 6.2.2 rom.
I flashed his latest on cm7 and it feels great. Which version are u using?
Sent from my kindle fire using xda premium
I am also using his latest flashed on stock.. It is probably a known issue I won't worry about it though. If the boot problem really causes any trouble I will reflash.
It is, in fact, a known issue.
Just set your minimum speed to 600mhz and the SOD will stop
Thanks for everyones help. I will just revert kernels until the problem is fixed.
Sent from my Kindle Fire using Tapatalk
Hi,
I just got my nexus 7 3 days ago.
I flashed TWRP and CM10.1.2, then the franco.kernel
Everything was going fine, until today it started to freeze when I select power off/reboot, while yesterday, everything was fine.
Any help?? (I can go into bootloader/recovery, by doing the combination)
I've tried re-flashing the franco kernel, and CM10.1.2.
Edit: I Fixed by under-clocking my GPU to stock settings (416 MHz), Before I Over-clocked it to 750 MHz
You can leave now
drew1ind said:
Hi,
I just got my nexus 7 3 days ago.
I flashed TWRP and CM10.1.2, then the franco.kernel
Everything was going fine, until today it started to freeze when I select power off/reboot, while yesterday, everything was fine.
Any help?? (I can go into bootloader/recovery, by doing the combination)
I've tried re-flashing the franco kernel, and CM10.1.2.
Click to expand...
Click to collapse
What exactly do you want help with? You can still transfer files onto your device and boot into recovery. Try a different ROM and/or kernel.
Username invalid said:
What exactly do you want help with? You can still transfer files onto your device and boot into recovery. Try a different ROM and/or kernel.
Click to expand...
Click to collapse
No thanks.
It turns out, it's because I've overclocked my GPU from 416 MHz to 750 MHz. It's fine now
Ive recently flashed the latest 4.3 ROM from Quarx. (previously I was using an old version of the 4.1 ROM from Quarx too).
First it was _really_ slow, after a while I figured out, that the CPU was reporting 0MHz maximum and 300 MHz minimum. The problem was, that the CPU speeds were in the bootmenu 300,600,1000,1000. To fix it, ive changed it to 300, 600, 800, 1000.
Now the phone is super fast, but I think there is some problem with the CPU speeds. If the screen is off, it runs at 300, but if I turn the screen on it will always run at 1000 - even if the CPU load is like 10%. Ive tried boosted and smartass governors, stock and lower Vsel values, no help.
Is this normal? If not how can I fix it?
thanks
Strange. It shouldn't be stuck to 1000 when screen is on, in fact it should increase to 1000 when there is some interaction. Try starting fresh.
Sent from my MB526 using xda app-developers app
syddd said:
Ive recently flashed the latest 4.3 ROM from Quarx. (previously I was using an old version of the 4.1 ROM from Quarx too).
First it was _really_ slow, after a while I figured out, that the CPU was reporting 0MHz maximum and 300 MHz minimum. The problem was, that the CPU speeds were in the bootmenu 300,600,1000,1000. To fix it, ive changed it to 300, 600, 800, 1000.
Now the phone is super fast, but I think there is some problem with the CPU speeds. If the screen is off, it runs at 300, but if I turn the screen on it will always run at 1000 - even if the CPU load is like 10%. Ive tried boosted and smartass governors, stock and lower Vsel values, no help.
Is this normal? If not how can I fix it?
thanks
Click to expand...
Click to collapse
Did you flash with 08.01 or with 09.17 rom?
I tried both and only 08.01 is working fine for me, I had problems with the 09.17 ( My hardware buttons didn't work right....)
andy-q said:
Did you flash with 08.01 or with 09.17 rom?
I tried both and only 08.01 is working fine for me, I had problems with the 09.17 ( My hardware buttons didn't work right....)
Click to expand...
Click to collapse
If hardware buttons didn't work, it is usually indicative of a full system partition/wrong gapps/too big zip.
hotdog125 said:
Strange. It shouldn't be stuck to 1000 when screen is on, in fact it should increase to 1000 when there is some interaction. Try starting fresh.
Click to expand...
Click to collapse
Will these steps result in a complete reinstallation? Ive backed up all data from the phone, so I can wipe everything.
Copy the zip file to your SD card.
Reboot and enter recovery.
Wipe cache + wipe data + wipe dalvik cache.
Install the zip file from the SD card.
Wipe cache + dalvik cache again
Or do I need to do something else for Quarx's latest ROM? like install a different SBF or kernel? Ive rooted (and flashed an .sbf) this phone like 2 years ago.. Before 4.3 I was using a 4.1 build for a long time.
You need to flash a new 4.1 build which has TWRP and then flash 4.3, because the old CWM binary does not support 4.3. I suggest you do a full wipe with defy full wiper or AROMA wiper.
Sent from my MB526 using xda app-developers app