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/
Related
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.
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Firstly, I'm sorry for your troubles and welcome you to the ROM scene. But I would say posting this (or looking through) the Nebula ROM thread or posting this in the Q&A section would likely end up with better results.
Secondly, I also had experienced issues with Nebula ROM 1.0.7. My recommendation is to Odin all the way back to DK28, then work your way back up to Nebula. Also, try flashing Nebula twice onto the device to try to remedy any problems.
Another tip, it seems that if you are using things like Titanium Backup that there are instances of people running into problems of backed up apps causing problems. Starting new is probably the best bet.
Hope this was of some use!
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
socos25 said:
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
Click to expand...
Click to collapse
Ah, alright. I'm not too certain as I'm unaware of a good deal of the inner workings of Android, but I do hope things get straightened out for you. My phone still has some apps that act up sometimes, mostly JuicePlotter it seems.
Hanging arround... I forgot my last un and passwd(I had an htc tilt a while ago... now I can't post on dev forum...) to use 1.0.7 I think you need ext4 (at least I'm using it) some apps are giving troubles with ext4. So try one by one, and use the cwm3 backup system. At least for me is easier and safer than tit or backup pro.
Sent from my SPH-D700 using Tapatalk
I am so glad I didn't update to 1.0.7!
socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Sorry I missed this yesterday, but I wanted to say that I had the same problem updating to 1.07 and I had already gone back to DK28 stock w/ CWM3 before the upgrade. I also restored some apps and settings selectively using titanium. One thing that we may have in common is that I ran my battery ALL the way down accidentally after this upgrade, tried turning it on a couple times (and it would shut down right away) and when I plugged the phone back in I got the repetitive force closes when I tried to turn it on.
Anyhow, I recharged completely, started from stock DK28 again (and wiped the battery stats) and even with restoring the same settings from Titanium I have been running it for about a week now and it is rock solid. So, give it another shot and see how it goes...
The short version is I got everything working!! And Nebula 1.0.7 is the fastest rom I have used yet... But don't get too excited because this is only the third I've tried, and one of the other two is stock DK28.
What I ended up doing was Odin'ing back to DK28, installing CW3, and then doing the 3x3 clears. Then I also formated everything I could find in CW. Installed the Nebula Rom and still had an issue. Rebooted back into CW3 and then reinstalled the ROM again, and whalla.. It works.
I think for some reason you have to install it twice.. Strange I know..
I had force close issues as well, and all I did to fix it was go into CWM, and format/clear cache partition, and format/clear the dalvik-cache. Did this cache clear and dalvik clear 3 times.
coryshad said:
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I second this as a possible problem. Shut the phone off 100% before removing the battery. On the moment that I also had if you removed the battery or used quick boot with ext2 you faced possible data corruption, but there were kernels that would check and fix data. You'd end up in a boot loop though if it didn't repair.
Sent from my SPH-D700 using XDA App
I've been making sure to shut it off before removing the battery, so far so good. I'm really liking this much better than stock.
Want to try a speedtest with the wifi tethering while going down th road.
I did a speedtest yesterday in my house and got 1.5mb DL, .5mb up. That was on my airrave though.
Sent from my SPH-D700 using XDA App
Hey guys,
So I loaded RubiX a while back and after getting everything all fancied up the way I wanted it my phone decided that it doesn't like when I touch it (touch-screen stopped responding, the hard keys still worked fine, but I have to serious hold screen-keys down to make anything happen).
I thought this problem was just something in the ROM that my phone didn't like, or a bad setting I changed, so I tried out Liberty ROM (which, by the way, is AWESOME). After getting everything completely made for the Liberty ROM, the exact same thing happened.
In a fit of frustration I decided to start from scratch, root and deodex, then load all my fun settings (like the de-throttle and imoseyon's memory changes) and it all started doing it again. Is there something I don't know about the way the screen works?
Another interesting fact: While I was trying to figure this problem out with my phone (stock with root/deodex and imoseyon's changes) I unplugged it from charging on my comp and now it's running pretty smoothly again... I've been having this problem all day, restarting and clearing cache / loading different ROMs and running restores didn't do anything... this is really strange!
Any idea what this is / has anyone experienced it before. I was just about to call Verizon and reset my phone to stock to get an exchange.
Try running a ROM stock and see what happens. Could be an app...
zehk,
I've tried every combination, including running to stock...
What I know now is that it only happens when phone is charging from a computer... The touchscreen goes completely brain-dead...
Any ideas?
I've had a problem when charging my phone from USB before. Someone said it was the drivers on my PC... might try a newer or older version depending on what you have.
That's an odd problem. Seeing how you have tried to troubleshoot your issue, trying the PC Drivers might indeed help as suggested by zehkaiser.
I would recommend downloading Motorola'as MotoConnect. It's the only driver I use for any Motorola device I hookup to my computer. You can download it here. Hope that helps and if not, sounds like you will have to do a .340 SBF with RSD Lite or the maderstcok zip 340 and return your phone for a new one.
nope
It's not the drivers either, I've now realized that it's happening when I plug into the wall too. I thought that might be due to using an old palm charger, since it's slighty higher amperage, but it turns out the standard moto charger still causes this problem...
My DX does exactly the same thing after unplugging. Any ideas?
Hey,
I was hoping to find someone who had similar problems to mine but have had no luck, so I decided to break down and just make a thread.
My Evo (003) has been giving me really scary problems ever since I tried installing CM7 rc3. To preface, I have been installing the nightlies since 15 and could be considered a flashaholic. I run amonra 2.3 and have all of the latest radios and such. To avoid a long paragraph, I'll post them as bullet points. I've tried other ROMs and plenty of kernels and I get similar errors in every attempt. I'm currently running CM7 final and the latest savaged kernel
- Whenever I reboot the phone, it bootloops once, then boots fine
- When I take the phone off the charger in the morning, the phone runs badly and the charging light stays on until I reboot
- I get a lot of "phantom" keypresses every now and then that render my phone useless until it stops in roughly a minute
- The screen off animation no longer works in CM7
- The phone randomly reboots every other day or so
- General slowness
I can't help but be scared that I will restart the phone at one point and it won't boot up, like some other people are experiencing. Can I be saved?
Thanks for any help!
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