every now and then, my phone will completely shutdown by itself. the only way to get it back on is to do a battery pull. it doesn't matter what kernal/radio/rom variation I use either. oddly, I find it seems to do it when I set my phone down for awhile. I haven't experienced it while I'm actively using the phone.
is this a common issue? fix?
Power Off
I have had the same issue. I thought it was something I did wrong. Beware, the problem suddenly got much worse for me today. My phone will only stay on about 90 seconds before powering off. It powers off even while in RECOVERY! It powers off unplugged, plugged into ac, and plugged into usb. The only time it does not power off is while in HBOOT. Does anyone have a fix to this problem or am I stuck going to Verizon and telling them I dropped my phone in the toilet?
Did you recently overclock because i was messing with mines today and it wojld also do that but now i got mines at 1.9ghz and has stopped doing that i guess mine is stable
Mine shuts off if i under clock it to low. 368 is my stable underclock. Anything lower and I risk being late for work LOL.
If I helped you in any way please use the thank you button
I have been using Imoseyen's (please forgive any spelling errors as I am doing this from memory) lean kernal 3.8.0 with the 184 MHz option left locked with bamf forever 1.0.7 for a few weeks now. My phone would freeze and reboot if I even tried to run at the 184 MHz setting, but I never had an issue with it at the 245760 Hz setting but I would up the power to 875 for that speed up from the 850 value used in extreme option. After I fixed power and speed values in init.d, I had an incredibly fast and smooth system (2500+) quadrant with a sense rom 245Mhz-1.6 GHz overclocked and undervolted at my custom power values.
Yesterday I decided to try an A05P rom to see if they were faster than the sense counterparts. I tried ShiftA05PHacked V2.7 again with Imoseyen's lean kernal for A05P 3.9.2. I did a nandroid of my stable and wonderful sense rom then did a complete wipe (dalvik cache, battery stats, system, and factory reset). So I get this puppy running and do all the same tweaks and things I did to my sense rom and I end up with an amazingly fast rom! I got a quadrant score of 3000+ when clocked from 245Mhz to 1.59 GHz. Again it was very stable but I missed my sense stuff so I thought I would just nandroid and wipe again to try a few more roms.
The next time I wiped and loaded Liquid Smooth v 1.6, I never got it booted before the random power off thing started happening. So I reboot into HBOOT by holding down volume after it powers down and go into recovery. I immediately attempt to format /system to no avail. I have wiped everything multiple times and cannot get my phone to stay on in recovery. Any ideas???
Problem Solved
Hey all, I have a solution to the problem I had and would like to share it. It isnt pretty or fun but it WORKED!
I tried to flash a rooted/deodexed stock rom as HBOOT was the only thing working for me...didnt work. My last step before dunking the phone in the sink with the screen on was to put a truely stock ruu (unrooted and all) on it. For whatever reason this cured the problem! I have since then re-rooted my t-bolt and have been able to get back to testing roms and tweaking to my flash-addicted heart's content!
BTW I have seen a lot of confusion about the flashing AMBER led light. It was due to the battery being dangerously low. Thank you to everyone here and the people at AndIRC #thunderbolt. You were great helps!
Related
So first a little background. I woke up in the middle of the night with an EXTREMELY hot phone. Somehow it had gotten under my pillow while it was charging (I have no idea how this happened but it did). The phone had a battery symbol with a temp sign, obviously way overheated. Well I quickly pulled the phone from the charger and the battery out of the phone to cool it down. After a few minutes when it had cooled down, I tried to boot it back up. At first everything looked good, TW bootscreen came up, but then nothing else happened. The phone would act like it had fully booted (captive buttons would light up then screen would time out and go black) but the boot screen animation would still be going if I pressed the power button to light the screen back up.
At that point I thought it was all over. I put in my spare battery and got the same results. So I went into recovery and wiped to see if the phone could read from the memory. I didnt have any problems with the wipe or reflashing (running next-gen TW). The phone booted up just fine. I haven't seemed to have any problems since.
So I guess my question is do you think I am in the clear? I ran quadrant to stress the phone to see if anything happened and I am still seeing the same scores. I thought I might have problems with data but it seems to be running ok now.
Is there more stress tests I should run to make sure everything is ok? I have always been cautious with my electronics so I havent run into overheating them before so I am not sure what to look for in this area.
Thanks guys/gals you all are awesome, love the community Usually I don't post/create new threads because search is my friend and I dont like to crowd threads with my stupid answers lol. Thanks again all!
PSS sorry for the long post and confusing explination let me know if I need to re-explain anything. and sorry if this is the wrong section just let me know and/or move to correct location.
My phone got stuck in the boot animation with Trigger v3.2 once. It had nothing to do with overheating.
I remember just doing a reboot and it got stuck in the animation. The screen timed out as if it had booted normally. I rebooted again and it was fine, never had that problem since. It has only happened to me with Trigger v3.2, which is based on KB5 (I think Bionix NextGen is also based on KB5).
So it's probably a software related bug and not related to heat damage or anything.
That's what I am hoping, guess the only way to really know is see if I start having problems over the next few weeks. Thanks for the replay
Hi all,
I have never had this problem before, and it's making me kind of nervous.
My battery was low today(~47%), I had it plugged into my computer. It showed that it was charging, but I was using the phone at the time(and the battery was slowly going down, which was weird to me). I went to plug it into the wall, but before that, I turned it off.
I noticed that there was a hibernate option in the menu which I tapped by accident. I woke the phone back up, turned it off, and charged it. I went to turn it on, and it got through both "HTC" screens, and did the "Bamf thunderbolt screen", but it stayed stuck there for like 5 minutes.
I pulled the battery, waited a few seconds, turned the phone back on. Still stuck.
If it helps, SetCPU was updated today, and I hadn't rebooted the phone in a few days.
UPDATE: I restored an old backup, and the phone booted. Could it be a Problem with SetCPU? Anyone else having an issue with the new update?
Thanks for the help!
Could have been a bad flash of the ROM or something? Did you do anything new to it recently?
The only thing that I did was update SetCPU...I haven't flashed anything since I flashed the ROM.
I put the phone in Hibernate by accident, woke it up, and shut it immediately off afterwords. I turned "Stay Awake" off in the development menu to charge it (phone was a little hot; I had been using it). I charged it, turned it back on, and was stuck at the boot screen...don't know why.
I restored, removed SetCPU, and rebooted it twice yesterday (once to flash a battery framework mod, and another just to test it), and it booted right up.
I don't think it was a setcpu problem more than a conflict frequency problem. The bamf toolkit, if you've used it, will clock a certain frequency, and the setcpu will also clock a certain frequency. I think the two apps might have some conflict if you enable them both.
Did ever mess with the voltage settings on setcpu.
Sent from my ADR6400L using XDA App
Wipe wipe wipe and flash again
Sent from my bamf Thunderbolt using XDA App
tryceo said:
I don't think it was a setcpu problem more than a conflict frequency problem. The bamf toolkit, if you've used it, will clock a certain frequency, and the setcpu will also clock a certain frequency. I think the two apps might have some conflict if you enable them both.
Did ever mess with the voltage settings on setcpu.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Don't even know how to mess with the voltage...I've never really messed with setCPU beyond setting battery/charging/screen off profiles.
I uninstalled it and frankly am getting better battery life without it.
I have been running Das Bamf 1.7 Stripped no for quite some time without any problem, but recently I have been having quite a few random reboots. This morning I try to turn my phone on and It will not respond. This has happened before and all I had to do was plug it into the charger for a few minutes and then do a battery pull and it would start up. I tried that and all that it will do is give a small vibration and then do nothing.
Any help is appreciated.
I would try leaving it plugged in for like an hour and then give it a shot to see if it'll start up. The problem is every reboot eats a good percentage of battery so if you have enough of them you'll pretty much drain it down to where it will not power on.
I had this issue a long time ago but after leaving it plugged in for about an hour I was able to bring it back up easily.
Its kernal related
trentreed said:
Its kernal related
Click to expand...
Click to collapse
please enlighten us oh great one...
Hey, i am using thory GB rom lastest release 3.5.1 and it works perfectly but when i did the speedtweak.sh and set it to extreme my phone will not boot now it stays stuck at HTC and reboots itself but never goes past it how could i fix this please.
Was there a resolution?
No. I finally was able to boot into recovery and i deleted the kernel and re installed it and it finally booted back up idk why that did that if the speedtweak.sh preset settings should be safe.
I have been tinkering around with Checkrom all day after moving away from LightningRom (haven't even updated my sig yet ). I came up with a really stupid idea of trying to flash a battery mod made for CrickeloRom so I could get a better looking icon than the ones already available in the kitchen app.
After recovery mode flashing, and then gave me an error message on the home screen view before continuing endless reboots. Managed to wipe and format everything (sdcard, system, data, cache, emmc) I could through recovery mode and reflashed Checkrom to get it to boot properly.
Only problem now is when the phone is hooked up to the charger, it displays 96% and then quickly goes 97, 98, 99, 100....96 and repeats. The number changing only happens when the battery icon flashes it little charging animation. I have tried to reflash the stock battery mod hoping whatever got screwed up would fix itself but it didn't work. Any suggestions?
Is there any place I can find a stock nandroid backup that will replace all system files, not just the ROM-related files, so it gets back to true factory state?
I am hoping that you mean that even if the battery dips below 96% it still shows what you are saying.
If not i am fairly sure that it is part of checkrom revo 2.0 as mine does the same thing while it charges so mine at this pont in time will sit at 56% the count up to 100% stop for a little wile and repeat.
kenshinzer0 said:
I am hoping that you mean that even if the battery dips below 96% it still shows what you are saying.
If not i am fairly sure that it is part of checkrom revo 2.0 as mine does the same thing while it charges so mine at this pont in time will sit at 56% the count up to 100% stop for a little wile and repeat.
Click to expand...
Click to collapse
The problem you have is exactly what I am experiencing. I was using the blue circle bat mod from the kitchen app and it was not doing this before I messed up, so something definitely seems to be wrong software wise. I'm just hoping someone knows a way to restore deeper problems like this one, because a factory wipe and reinstall rom through recovery mode wasn't enough to fix it. I've even tried switching back to lightningrom and different kernels to make sure it wasn't a bug.
Last resort for is to restore stock rom+kernel and play dumb with samsung tech support, and get it serviced. Hope it doesn't come to that.
hey everyone,
I installed Liquidsmooth v2.5 on my dorid razr a few days ago.
All in all it works good and could be used as a daily driver but nonetheless there are a few bugs.
I installed in on System1 with BMM. and i always need a cuple of tries to startup my pohne.
The other times, BMM loads the files, starts kexex to boot and i keep stuck with a black screen and the green LED alight.
I gotta restart the phone up to 5 or 6 times if i finally see the boot animation and the phone starts normally.
And I'm not sure but I gotta feeling this rom drains the battery.
The process 'Android OS' used 46% and display did only 19%. This seems kind of weird because with the ICS stock Rom I always had display as the number 1 in consuming battery.
Does anyone has got the same problems, or even better knows to fix the boot issue?
greetings
I have a LiquidSmooth ROM out there, I know for a fact it works amazing. As for your recovery problems, I would advise using safe strap instead. Liquid smooth ROMs are reserved for slot 3 in safe strap.
i run Liquid smooth on BMM and never had any problems dude.....and about startup's yes it does take some tries if you had hard reset the phone...if u have done normal reboot then u wouldn't encounter this problem....so the fix as of i know is to not hard reset the phone....
and about battery drain i have great battery life i recommend u to use hotplug+noop as governor....and use setCPU and there is option to turn down CPU speed to 300 min and max being 800 under profiles...add a profile when screen off and set the given CPU freq..