I installed the kingx bfs kernel #5 and after rebooting my phone, the phone would come on and start loading the widgets and all that good stuff. After about a minute, my phone would reboot and do the same thing. well after about 4 reboots, I pulled the battery and went to bed, thinking I would just download a new kernel in the morning and things would be better. Now when I try and start my phone up into recovery, it vibrates 3 times and nothing happens. The screen doesn't come up; nothing. It will still boot the phone up and load the widgets and then reboot itself again, but I can't get into bootloader or recovery.
I am running the leaked version of froyo that came out a while back.
any ideas?
*EDIT* ok somehow I managed to get into recover... idk how but I did. wish me luck.
You put your phone into some type of Debug mode. I'm assuming you have S-Off enabled? You are fine, you just need to unplug and remove the battery for a while when that happens.
happened to me when i put the CPU clock too high.
If you can get to recovery just flash another kernel or do a nandroid backup. Should be fine.
I've noticed setCPU locks up at higher frequencies w/ KK's #5. Not sure what you are running at, but i don't go much over 1GHz.
knock 3 times....
Speculation, if it makes you feel any better:
I seem to recall in the UnREVOked notes during rooting - that when one pushes the volume button up while pressing the power button, it triggers a harmless diagnostics run on the Qualcomm processor, yielding 3 buzzes - suspect that may have been the 3 buzzes.
Agree w/ other guidance posted to get you up and running again.
FWIW, just because a kernel is capable of going 119 and we can keep it 'to the floor' the whole time by overclocking in SetCPU - it doesn't mean the device will do it, nor that it won't nag you for pushing it so hard.
Some will work reliably/consistently @ that rate.. Some will not.
thanks guys. Setcpu was automatically setting the kernel to 1.13, and I believe that's what was happening as well. I had just enough time to get the setcpu up to see it and then it would restart.
Related
I rooted the phone using odin, then threw lost kernal on the phone. then used odin to flash the stock pulled kernel to eliminate the yellow triangle then used CWM to flash back to lost kernel. then went to zedomax V3. phone has been working very good. did freeze one time when opening a game and then restarted on its own after a few seconds but this is only once so far. I never knew about this problem until last night when i attempted to do a 100% charge with the phone off so I could reset batt stats. well, EVERYTIME I turn the phone off, it stayed off for a few seconds but then it would always turn itself back on... just flashed back to lost kernel (stable version) and it is now sitting powered off charging just like normal. I liked the OC ability but I will sometimes need my phone to stay off, say when I get on a plane...
anyone else have this problem
Same here I am running version V3 of Zedo, stock rooted.....and have the same issue the phone will not stay off. I have tried it both ways with QuickReboot and also manual with the power button and still have the same results. For me it is NBD but I have not been in a situation where I need to have the phone stay off.
I also tried it with quickreboot (not sure if I have the same app, blue circle with a yellow lightning bolt?). also, does your phone do this? when I shut down using the power button long press, choose power off and then hit ok, it shows the sprint logo with the exploding boxes looking screen, capacative buttons stay lit up for a while as its shutting down, quick reboot just SHUTS DOWN! lol, its like the difference of being on a PC and choosing shutdown or just flipping the switch on the back of the PSU. is it better to shut it down the stock method?
(side note- my palm pre power button started acting up so now I do what I can to use the epics power button as little as needed, which is why I have a screen icon to lock my phone and reboot with quick reboot)
yea we have the same quick reboot program....as for shutting it off which way, I think it is better to shut the phone down using the power button and have the phone go thru the shut down process vice just shutting down right there and then like a light switch. I do the same on a pc i try never to just hold the power button to shut down the pc unless it freezes, I just do the regular shut down process.
I flashed zedo v3 too and had problems too. At random moments i couldnt text, browse web,make calls or get calls unless i reboot. I unrooted it and phone went back to normal. Im sure zedomax will put out a better kernal, he knows wats up. Has anyone else had dat problem?
actually the not-staying-off was the only problem I even had on that kernel except the freeze that happened one time. today on lostkernel, right in a row I had 4 texts say they failed to be sent but then when I talked to the people later they all told me that they were actually delivered. I even rebooted the phone after the first 2 and the next 2 still said failed so I highly doubt that it was anything other than a weird problem with the network though... although I dont know exactly how the whole process works. I think I am going to go back to zedomax later though, I dont fly often so if I end up on a plane Ill just flash lostkernel again since I leave both files on the card on a daily basis. and I like the setcpu profiles. could always go with the experimantal build of lost kernel since technically the zedomax is a beta as well...
Hi, I've had my DHD for a fair while now and installed mike1986's ARHD 5.x ROM when I first rooted my device. With the advent of ICS, I have been flashing the betas that have been out for the last few months, eventually got sick of the bugs, and flashed ARHD 7.0.2 earlier today. Ever since doing so my device randomly loses power when I use it - it is hard to pinpoint an exact cause, because the same thing can happen when I boot up a game or when the phone is sitting asleep in my pocket. I am also not sure if it is related to the new ROM or not, but I reflashed an older ICS beta to check, and sure enough the problem also exists on other ROMs now. It is also worth noting that the problem is absent when USB power cable is connected.
I've also tried different kernels and an update.zip that switches the OC daemon in ARHD back to the stock clock speed of 1ghz as it was suggested that perhaps my CPU doesn't like OC/UV. While running older ARHD and ICS ROMs my CPU usually hovered between 1.0 and 1.4ghz. I still get random power loss @ 1ghz.
Can anyone suggest a method/ROM/something to fix?
EDIT: Now, when I boot my DHD, HTC splash comes up, boot animation comes up, handset prompts me to enter PIN, goes to main home screen, and imediately loses power. Help!
Hi, I've got a similar problem. A week ago I installed RD-MIUI-ics 2.3.2_v4 [4.0.3] ROM. Since I use that ROM, my phone occasionally reboots for no reason. For example, when I play music on spotify and remove my headset without pausing the music first, it reboots. I wanted to post this on that thread but I am not allowed to post on the development page.
I did a full wipe before I installed the ROM the first time.
Any ideas?
I underclocked my CPU to 800mhz max and it hasn't crashed again... yet.
First, I'd like to thank the DEV for the Energy ROM. I've run the last two releases and it is truly spectacular. The latest version with Hashcode's Kernel makes it a completely functional daily user (not that the SOD's in the last one made it any less amazing). I understand the battery issues associated with it, and have read through the workarounds in the DEV forum, but this issue seems to be beyond those. On any given day, I leave the house for work with a full charge and, even if I'm not able to use it during the day, I get home and am hovering around the 50% level. Not a big deal, but the last two days I've taken it a step further and did a hard power off before I left (held power for the 20s). When I got back 10 hours later and tried to power it back on, it was completely dead. First day I thought, just a fluke, maybe the power button got bumped accidentally. But two days in a row, while the KF was secured in a hard case, got me concerned. Is anyone else running into this sort of issue? This is by far the best ROM i've run on the KF, and tomorrow I won't bother to shut it down, but I'm curious as to what could be the cause. I'm running at the standard 1200/600 clock speed, but with it shut down, to my understanding I shouldn't see any significant battery loss, right? I'm definitely a noob when it comes to android, so if this is an issue easily remedied, I apologize up front. Thanks in advance for any help offered, and thanks again to all that made this ROM possible!
It's a known issue for older kernels (not sure about the latest one) that if you force the shutdown, it may sometimes turn on at random a while later - this is probably what happened, it turned on a while after you left it off, and then just ate through the battery during the day until you got back home.
If you have flashed the latest kernel, using the "normal" Shutdown option should work (not sure if the ROM would need to be updated or not) fine, so far I've never had it turn back on after using it, but I'm using Hashcode's ROM instead.
Otherwise, just reboot into TWRP and press "Reboot" - "Power Off", which will make it stay off... hopefully.
Thanks, I'll give it a try through TWRP and see what happens. FYI I'm running release #8 of the 3.0 kernel if that sheds any light on the problem
Sent from my Amazon Kindle Fire using XDA
I too had battery issues with EnergyROM... things seem stagnant there so I flashed gedeROM last night and so far so good.
psudeke said:
FYI I'm running release #8 of the 3.0 kernel if that sheds any light on the problem A
Click to expand...
Click to collapse
It'd be for the best if, at the very least, you flash kernel #10, as it allows for "normal" shutdown (ie, no need to go through TWRP or to force the shutdown by holding the power button 10-20s), though I'd recommend switching to Hashcode's ROM (better support, plus a few more ROM only features) instead, at least until everything slows down a bit.
Thanks for the advice. I'll take a look at his ROM as well. I thought about just flashing the #10 kernel, but i understand you lose some of the functionality of the kernel since the ROM isn't designed to take full advantage of it.
Sent from my Amazon Kindle Fire using XDA
Hello, everyone, this is my first post here, and after doing much research on my problem, I haven't had much insight into solving my problem permanently. tl;dr version is at the last paragraph.
First off, I installed AOKP on my phone for the first time a couple months ago and I had no problems for two months for reboots or anything like that, and I believe my phone was overclocked to 1520 mhz on the SmartReflex voltage settings. I did not undervolt whatsoever. In this phase, whenever I would turn it on, I would get to the boot animation, then the animation would hang, and the screen would rise to the highest brightness, flicker, and reboot, or shut down.
Then, in my troubleshooting, being the idiot I was, I accidentally unplugged it while I was flashing back to stock using ODIN. I got the "Android triangle computer" A.K.A. the "Soft Brick" signal. If I booted it normally, into my recovery, ODIN mode, whatever, I would get the same signal.
So, I left my phone alone for a couple weeks, accepting failure. Two weeks ago, I rebooted again into Odin mode, and I saw that Odin on my PC still recognized it, so I connected it and reflashed the stock ICS rom. I re-rooted and installed AOKP, all was fine for two/three days.
After that, the reboots started to happen again, and after a week of constant rebooting, and restoring latest backups,I set the CPU back to normal with no overclocking. I also undervolted but left "Set On Boot" unchecked for everything, This seemed to work fine for normal use, but I still had the phone on "InteractiveX" as the governor. So, when I would go to sleep, I would wake up and the phone would not be on. I would have to battery pull, reboot, etc. I thought this had something to do with one of the cores being turned off when the screen is, so I changed the governor to "Interactive" and the phone would charge now the same.
Now, the problem is, yesterday, I was fiddling with some benchmarks and I OC'd to 1520 for fun, and the phone screen froze, rose to the highest brightness, and shut down. I didn't have it "set to boot" so I thought everything should be fine, so I rebooted and the same thing happened at the boot animation which happened to me when I OC'd. I restored a Nandroid Backup I had before I set it to 1520, and still, no dice.
I reflashed my recovery then, because sometimes it would just freeze at the Google logo and not boot into recovery at all. Then, I restored my Nandroid again, and it booted into Android. After a few minutes, it crashed with the same "High Brightness, Screen Flicker". I restored again, and this time, I rushed into the "Performance Tab" and set my undervolt settings. The phone worked smoothly until I turned the screen off, and then I got the "Screen of Death". Basically, the screen stayed black, but the notification light was still on, and there was no response. So I pulled my battery and tried to reboot, but at the boot animation, the Nexus logo goes into "High Brightness, Screen Flicker". So, I took the battery out, and the phone is just sitting here now for fifteen or so minutes while I typed this out.
My question is, has anyone been having these same issues with their GNex. Because at this moment, I'm thinking I caused a hardware defect for running on 1520 for so long previously and I fried some inner components. Any help?
Edit: I put the battery back in and still the same thing. Going to charge overnight and let it sit, but if anyone has any help, please come forward.
Bump
First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus
Sorry
bk201doesntexist said:
First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus
Click to expand...
Click to collapse
First post here, didn't know much about rules. Thanks for the response. My Nexus did come back, just about 5 minutes ago. I'm going to stay on AOKP for a day and if I don't encounter any problems, I'll stay on it. If I do, I'll revert back to stock.
So yeah, **** this
bk201doesntexist said:
First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus
Click to expand...
Click to collapse
It was working fine until I got 3 or 4 Sleeps of Death a day until today. It just stopped working, and I restored my backup multiple times, but it would just hang at boot or bootloop. So I'm like **** this, so I flashed the stock image for 4.2.2 through Fastboot, and it still didn't boot, even after complete data wipe through the stock recovery. So, I thought it must be 4.2.2 that is doing this, so I installed the 4.1.1 and still the same result.
I'm so done with this thing, it's a hardware issue, total crap of a phone. If it is actually meant to be tinkered with and to be a "developer's phone" this crap wouldn't happen.
This has been happening for about 2 months now and has progressively started happening more frequently.
I've narrowed it down to a set of apps that are running when it happens.
Apps in use:
Screen On ( to keep the screen on while driving)
Waze (If you don't know what this app is stop reading now)
Play Music (Streaming through the Pioneer head unit)
It doesn't happen all the time but when it does the screen freezes for about 5 seconds then goes black and music stops the instant the screen freezes. Once the screen is black I try holding down the power button. Sometimes it'll power back on but most times I have to do a battery pull.
I've tried multiple ROM's and it still does it.
I've formatted my internal and external SD.
The last thing I still need to do is ODIN back to stock and then re-root.
Its taken me two weeks to get a logcat when the phone locks up. I'm not sure how much is needed so I'll attach the 2 hour logcat
Get Logcat here.
If someone can help me out and check out the logcat it would be extremely helpful. I can't ODIN back to stock yet because I'm on call all week and need a semi functioning phone till Friday.
I'm on stock unrooted NF4 and getting this sometimes. It happens when I am charging overnight. The next day, phone is off and I have to do a battery pull to turn it on. Luckily on those days I've gotten up before the alarm time. ?
p_synthesis said:
I'm on stock unrooted NF4 and getting this sometimes. It happens when I am charging overnight. The next day, phone is off and I have to do a battery pull to turn it on. Luckily on those days I've gotten up before the alarm time. ?
Click to expand...
Click to collapse
I had similar experience when using my phone as gps device in a long distance drive. Maybe because it got hotter?
Yesterday I was at the hospital with my son (he just had his tonsils removed). We were watching a movie Netflix and my phone locked up and rebooted 4 times within a 30 minute span. I finally had time afterwards to Odin back to stock and updated to NF4 then CFautoroot, TWRP latest and flashed Hyperdrive. I had hoped all was good but when i was cleaning out my car (streaming to the BT stereo) it locked up 10 minutes into my playlist.
Should I take it back to T-Mobile? Is there something else that I can do to troubleshoot?
Are you guys using any cpu apps?
Not that I'm aware of. I am using the compulsive kernel that is bundled with the latest hyperdrive.
Kernel issues, try other kernels.:good:
If you have a custom kernel, don't use setcpu in addition with the specific cpu governor app for that kernel. Also, don't set you minimum at 300 or lower. It's been documented to cause random reboots.
Not using setcpu. Was using the Hyperdrive tweaks to control frequencies.
I tried the latest compulsion kernel and within an hour it restarted twice. Tried the latest leanKernel and still rebooted. I guess I could go to stock, but I hate that music via bluetooth skips constantly on stock kernel.
The reboots are happening now at complete random, sometimes I'm using the phone other times I have the phone sitting on my desk and I'll look down and its at the Galaxy splash screen with the seandroid is not enforcing at the top.
I'm kinda lost at what it might be...I don't think its the ROM, and I'd really like to stick with hyperdrive just because for what I want in a ROM its all there.
wonderbread24 said:
Not using setcpu. Was using the Hyperdrive tweaks to control frequencies.
I tried the latest compulsion kernel and within an hour it restarted twice. Tried the latest leanKernel and still rebooted. I guess I could go to stock, but I hate that music via bluetooth skips constantly on stock kernel.
The reboots are happening now at complete random, sometimes I'm using the phone other times I have the phone sitting on my desk and I'll look down and its at the Galaxy splash screen with the seandroid is not enforcing at the top.
I'm kinda lost at what it might be...I don't think its the ROM, and I'd really like to stick with hyperdrive just because for what I want in a ROM its all there.
Click to expand...
Click to collapse
if u want to try something, when u ODIN flash the firmware, after it boots up, I ODIN flash TWRP then use my Stock Odex not rooted roms,then if u want root just flash SU from chainfire and install busybox,from the playstore, keep a copy on the sdcard and install.. and LEAVE the STOCK KERNEL, I use stock kernels and have no issues this way,
make a copy of my rom, remove the files u don't want from system/app and system/priv-app then flash that rom and SU right after that install busybox, and test that way. if u want I also have on the 3rd page a tethering rom, I have all the version, http://forum.xda-developers.com/showthread.php?p=51812491#post51812491
try it out, If u have problems, try not restore any data if u use titanium backup..