Here's the story, a while back, the phone just stopped working, I restarted, and it wouldn't boot, so I went into the recovery console, and tried a clean install, the phone stayed on the second boot screen for like 13 hours, till I quit, this was on a 2.0 ROM, and went back to RC29, I tried 2.0 again, and the same thing happened, finally, I tried the latest Cyan 1.6, and that worked, I've been running that ever since, this happened in April, anyways, I wanna know if this means the phone is dying? I really don't want to drop 500 on a new phone. Also, the phone only stays charged for about 12 hours now, can I fix the issues with the 2.0 ROMS, and get a new battery, or do I cut my losses?
Can no one help me out with this?
How old is your phone. The battery maybe dying and a new one can help you with the battery issue.
As for the ROM, there are much better ROMs our there than April, give another ROM a shot. Don't forget Nandroid and you should be good.
Related
I dont understand i have tried everything! I must be missing something
I have booted before with no problems aside from the robo voice
I come home in hopes to fix it and now no matter what build i use no matter what zimage i use the phone boots like normal in to Android and then just shuts down.... What am i missing here?
Spent all Morning Flashing rom and radio combos and still the same thing, Reformatted my sd card Nothing.
NO HELP?
this happened to me when i started using my extanded battery, no matter what i did it boots vibrates then shuts, im back to my normal battery all the builds work now, i figured out that the extended battery might need a driver or something.
here the same! with original battery is working
With extanded battery is shutting down! in one line by booting with haret
Chragin off (temp overheat)
battery working with
desirebuild_v5
battery dosent work with
mattcfroyorc1.4
mattcfroyorc1.3a
Wow never even thought about changing back to a stock battery. Or even mentioning that i again
This happened to me when I had a multi-boot program installed on the winmo side. Uninstalled it- booted just fine.
there have been a couple of threads with the same issue.. the devs have been asked about it.. nothing heard back as yet.. but it definitely it is an extended battery that is causing it
Yes the extended battery is it. I read it somewhere in the forums that it is not supported yet as there are no drivers and due to which while booting haret reads the battery temp to be 90 while it actually being ~30 and hence cant boot.
Replace it with stock and you are good to go
Mine is still the stock battery and still does the same thing for all versions of ROM and android too..
kingfisher1111 Mine is still the stock battery and still does the same thing for all versions of ROM and android too..
Click to expand...
Click to collapse
Are you using the stock HTC battery cuz im sure if the exteneded one dont work neither will cheap replacment batteries
Works great with my stock battery;
Never thought in a million years to try without extended battery lol
Only thing now i have to do is get over the robo voice.
nardone24 said:
Are you using the stock HTC battery cuz im sure if the exteneded one dont work neither will cheap replacment batteries
Works great with my stock battery;
Never thought in a million years to try without extended battery lol
Only thing now i have to do is get over the robo voice.
Click to expand...
Click to collapse
yes mine is original battery that came out of box with Tmobile..
Any one help me on this issue?
I'm experiencing avery annoying problem with my phone. It's been happening for some time now, and I've tried all sorts of different things to fix it.
The phone completely randomly restarts, or just powers off totally. This happens at least a few times a day on average, and sometimes has a crazy spurt where it restarts itself like, 5 times in an hour. This is very annoying when I get my phone out to check if I have any texts, and it's totally dead or sat on the ChuckyDroid Winmo screen. People text me 3 hours later, asking why I didn't reply to their messages, or they have been trying to ring me!
I have tried everything I can think of. I have tried at least 10 different Android ROMS, and a few different Winmo ROMS. I have tried every radio from 2.08.x to 2.15.x and I have also Task29'd the phone, then started afresh. It still does it.
Any got any ideas what could be causing it? Is it possible it's a faulty battery? I am beginning to think this as it never seems to do it if I have the phone plugged into charge, either from USB or mains. If people think the battery is probably knackered, I'll go onto Fleabay and buy a new one, but I don't want to do this if people don't think that's the issue.
Thanks in advance... I hope people can help, as this issue is totally unworkable for me.
Cheers
That doesn't seem like a battery issue to me, rather SD related.
As you have already tried about everything: full formatting your SD card should fix it. There are some more advanced ways of formatting, in case the Windows (full! not the default quick) format still doesn't do the trick.
Hm.. I'm pretty sure I've run a full format of the SD card before, but I'll certainly do it again when I get in and test out the theory.
Thanks for your reply mate
I also had this problem(s) with Froyo... suddenly my phone rebooted...
However.. since i'm on Gingerbread... the problem didn't occur anymore..
Maybe you can try a Gingerbread build to see if the problems still occur...
I can give that a try too. I know there's a lot still to be worked on the Gingerbread build, but if it's more stable then that's good.
The MDJ Gingerbread build is pretty stable.
Well, thanks for your efforts guys, but no joy. I full formatted the SD, flashed 2.15.50 to my phone, then ran MDJ Gingerbread... I think it lasted about 4-5 hours before it started restarting itself again. So screw this, I'm going back to Winmo until NAND is ready. Winmo might be crap, but at least it's reliable. Totally pissed off now, to be honest.
Updated the wife's phone to CM7 some time ago because stock was getting really sluggish and unreliable for her. Wanted to give it some new life. Been running ok (a bit better than stock) but still not great. Kinda flaky, she says. I haven't had a lot of hands-on with it since setting it up, but she says it has poor battery life, likes to freeze up, etc... But overall, an improvement.
Today, she gets up, and her phone won't power on. I know her charger can be a bit temperamental, so pull and replace the battery, then hook it up to mine to try and get it to boot.
It powers up long enough to show her she has a lost call, then spontaneously reboots again. Now it's stuck in a loop while plugged in. It boots, gets to the lock screen, reboots. I can get into recovery (but it looks like stock recovery, not clockwork, so I can't reflash CM7 to see if that helps).
I wanted to try flashing a stock SBF so I could get it booting again, (or at least take it into Verizon), but it doesn't even power up when plugged into a USB cable hooked up to the computer, only on the charger.
Any thoughts? I'm kinda stumped, and not as familiar w/ the Droid 2 as I am w/ my HTC G2.
*Edit*
Eh, after sitting on the charger for awhile while I typed this, it actually came up and seems to be staying up. I guess the battery was just very VERY low? Nevermind!
Sbf the phone back to stock and use a more stable rom. Custom roms from what i am noticing can have 2 installs of the same rom and give 2 completely different results. I had this problem with my current rom miui 2.2.10. On my first install it was complete garbage, crashing constantly even with system apps. Then i Sbf'd back to GB using the newly released GB sbf file you can find in this forum. Then re-installed miui and it works fine now. So it could just be you got a bad install. Try miui 2.2.10 over at rootzwiki, its a solid rom.
http://rootzwiki.com/topic/17285-ne...tt-charge-while-off-updated-bootmenu-scripts/
A Little History: :silly:
I have been running i9220ZCLP1...known bad kernel since whenever it was first available, April I think. Anyways, acquired that through flashing Rocketrom v5, according to the instructions provided at the time. Everything worked fine, other than contacts crashing and the wlan some times not enabling until reboot...common issues, as far as I've seen on these forums. One thing to note, is that unless the instructions at the time asked for a full wipe after flashing 5 (I'm almost certain they did not), then there has not been a full wipe performed while in this kernel.
The current issue:
The other day my phone froze on me...months after flashing and having used this kernel, waiting for something more solid to come out. After it froze...holding the power button turned it off, but the phone would not boot afterwards...to ics, to recovery, to download mode, nothing.
After some fiddling, I realized that it will charge and once it buzzes and the screen comes on showing a full battery, I can turn the phone on and it will boot...then freeze after getting past unlock screen. Or freeze and go black in download mode...didn't try recovery, wasn't interested in it at the time, but I'd imagine the same.
After removing the battery for a few days, then plugging it in til full charge notification, I was able to get it to boot again, where it froze at the boot screen, but went dark. After one more full charge...oddly, like a minute later, it booted to ICS fine and worked for 24 hours or so.
Now:
With a mind to flashing away from the bad kernel, I restarted the phone tonight from the menu in ics... it booted fine, so I left it plugged in to get a full charge and came back to a phone, screen still on, that shows same battery % as when I left it. And I'm back to where I started with this problem, powered off after holding power button a few seconds and now nothing.
Waiting for a full charge again, to see what happens...I'm guessing/hoping I'll be able to get it to boot again, with some more fiddling...
My question is whether this sounds like it's hardware (battery etc) or software (bad kernel etc) that is causing the problem.
If I can get it into download mode...plugged in, obviously, should I try OdinPC to a safe kernel?
Thoughts would be awesome. :fingers-crossed:
How about flashing stock GB via pc odin first and getting safe?
apurvapatel said:
How about flashing stock GB via pc odin first and getting safe?
Click to expand...
Click to collapse
+1 I've read a few people on ICS having charging/battery related issues over time. Worth seeing if it still happens on a gb kernel.
Sent from my GT-N7000 using xda premium
apurvapatel said:
How about flashing stock GB via pc odin first and getting safe?
Click to expand...
Click to collapse
OK, that's one vote for flash if I can get it running again. Thx, glad you read my post.
SpyderTracks said:
+1 I've read a few people on ICS having charging/battery related issues over time. Worth seeing if it still happens on a gb kernel.
Click to expand...
Click to collapse
Hmm, but how to get there...GB and all.
So now the vote is software. Any idea why this would happen much much later? No battery issues at all, just suddenly.
Maybe I'll buy a battery.
nebreprah said:
Hmm, but how to get there...GB and all.
Click to expand...
Click to collapse
A little searching would show you DrKentan's guide @ http://forum.xda-developers.com/showthread.php?t=1424997
Hey guys,
I have rooted my device over two months ago. The first ROM I had flashed was running nice and smooth except for a few issues like the camera issue.
After a week or so, I've changed the ROM and since then, I've always had problems. The ROM runs nice and smooth at the beginning and later (between ten minutes and three hours) the problems start again.
It never got bricked but it always kept shutting down, freezing (short), lagging, overheating, not reacting untill pulling out the battery or all apps and services crashing and so on.
I then managed it to get working better than ever before running a custom ROM (don't remember which one).
But that didn't last long. After a day or so the phone started lagging again. I've booted into TWRP and wiped cache and dalvik. The next boot ended in a "encryption unsucesfull" and I had to reflash the ROM.
What I've noticed today was that it helped to wait abit before turning the phone on again after pulling the battery out.
Since then I'm trying to figure out how to fix that.
I'm waiting for the Oneplus 4/5 anyway, and I'm not sure anymore if I should root that thing too since I risk to go through the same (or worse) struggle all over again.
If you need any further information to help me, feel free to ask for it.
With my Note 4, I have waited till the warranty time was over.
Thanks in advance
PS: Heat seems to be a huge problem. I don't mean overheating, I mean usual working temperatures. That would explain problems like the massive drop in performance as soon as I got in to my car which was standing in the sun.
PS2: Kind of solved. Downloading the wakelock app and setting it on "partial_wake_lock" helped.