I must have screwed something up as my phone is stuck in some sort of power cycle. Everything seemed to be working fine including several restarts after doing configurations and learning how the LCD density works. I do a shutdown of the phone I see the shutdown animation, but the screen still has the backlight on. It never seemed to actually shutdown so I hit the power button and the screen goes out. I go to boot into recovery to create a backup of my settings and like a moron i didn't delete the MR2 upgrade. I answered no to the install up the upgrade and reboot the phone. This is when the power cycles actually started I see no signal, 1x the phone locks up then restarts. I reflashed the radio in case it become corrupted and no change. I cleared the cache and the Dalvik to see if that would work NOPE now it's stuck on the DAS BAMF the baddest! boot screen. I did install the latest dreamkernal for the bluetooth options. Other than starting to install apps I can't think of what I may have done to do this. I don't have a problem reflashing, but I hate to cause this problem again. I did wipe 4x the factory, cache, Dalvik before flashing the rom and verified the md5. I know it's probably not possible without knowing exactly what I did, but any ideas or suggestions?
You've got wiping data/cache/dalvik/bat stats covered. I think 4 times is overkill, but certainly not hurting anything.
When you flash a ROM, are you flashing anything else....other mods, etc., before letting the phone restart?
Do you have a good radio? Try MR2 if you're not already, some have reported bugs or issues with MR2.5.
Check the md5 of both the ROM and Radio.
I would try to shut down the phone then pull the battery then boot bootloader and reinstall radio. If that don't work I would try a full wipe and reinstall
Sent from my BAMFBOLT using XDA Premium App
I flashed the latest dream kernel after flashing bamf and using MR2 verified MD5 before flashing. I did try a battery pull as I had to remove the sd card to delete the radio in order to go in recovery. I did do a reflash since i would have to anyway. I was just trying to figure out what I did wrong in my configuration and I think I did. When I turned the phone off I thought something was wrong since it looked like the backlight was still on. I think I corrupted something during shutdown that caused the problem. I noticed the phone seems to take a little longer to shutdown then with the rooted stock. I'm paying better attention so we will see. Probably all just human error
I also changed my min speed to 368 since i read some phones don't like 245. However I am not sure what the best Governor is to use so I left it with the interactiveX defaults.
Can you restore from a backup?
dms76 said:
I flashed the latest dream kernel after flashing bamf and using MR2 verified MD5 before flashing. I did try a battery pull as I had to remove the sd card to delete the radio in order to go in recovery. I did do a reflash since i would have to anyway. I was just trying to figure out what I did wrong in my configuration and I think I did. When I turned the phone off I thought something was wrong since it looked like the backlight was still on. I think I corrupted something during shutdown that caused the problem. I noticed the phone seems to take a little longer to shutdown then with the rooted stock. I'm paying better attention so we will see. Probably all just human error
I also changed my min speed to 368 since i read some phones don't like 245. However I am not sure what the best Governor is to use so I left it with the interactiveX defaults.
Click to expand...
Click to collapse
AFAIK all phone run fine at 245, its the 184 that doesn't play nice with some phones. Also turn off fast boot in the Settings>Applications menu, some people seem to have random problems when that is turned on.
I was in the process of trying to make a backup when something broke. It was actually easier to start over because then I could go setting by setting to see what I did wrong. I think it was just how I shut it down that fubar the whole darn thing. It seems to be working correctly now and I created a backup as well.
184 not 245 gotcha and thanks! That could save some battery life I would assume. No matter how well built there is still a better idiot!
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
Well, if you were having this issue before the rooting took place, this very well may be hardware related. There are a few things I recommend before the dreaded unroot and send back to manufacturer route (assuming the phone is under warranty still). It's been proven or at least shown that battery calibration (the whole charge to 0Ma and then fully discharge and then recharge) is a pipe dream.
I would first say find out if the CM7 ROM you're using is OCing or UVing, while you may see some people OCing to 1.3 or higher and UVing -75, not all phones are created equal in capabilities and some phones will randomly freeze/turn off if they don't like your OC and UV settings. I would also suggest flashing a different ROM to see if this problem persists. Cleardroid is what I recommend just to get an idea if it is in fact a OC or UV problem as I believe cleardroid is set up to default stock settings.
You can also try a new battery, I have heard/read/seen that bad batteries can cause reboots. Again though if this was an issue you were sometimes experiencing before, you may have hit the tip of the iceberg on a hardware issue and its finally starting to show now. Hope this helps.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
I guess the issue is with the battery itself. Try getting a new battery. I heard some guys experiencing the same and sorting things out replacing the battery....
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Agoattamer said:
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Click to expand...
Click to collapse
That was my thoughts exactly. However, if the ROM or kernel or whatever is set to shut off the phone at a certain reading of discharge from the battery, ie -500mA, this could also be the problem.
I thought it could have been a problem with the phone as well, but before it would shut off on its own MAYBE once a month. 90% of those I attributed to overloading the phone, closing facebook, opening the internet, starting to load a webpage then open a new txt I just recieved while the phone was still vibrating type things.
Now it still feels like it's just quitting on me, it never turns off while the screen is locked or while its charging. So far after the new ROM it has shut off when I place a call, when I receive a call, clicking on a notification, opening the messaging app, clicking download in the market, and my favorite when I unlock it from sleep.
I will download a different rom right now and try it. Just to double check this is what I've been doing to install a new rom... I boot my phone into recovery (vol- and power), go to recovery from the boot screen (opens clockworkmod), scroll down to mounts and storage, have it format /system, /data and /cache, go back to wipe data/factory reset, then install zip from sdcard, select the rom and go... I know some roms require inspiremod, should I still install this if I'm USING an inspire??
Thanks for the input guys, I really appreciate it
If it does turn out to be the battery or you just decide to get a new one to test it out. I recommend these, they are awesome and the only thing anyone should try besides HTC factory replacements. Good luck and I hope this works out for you.
Anker Batteries
i only skimmed this. but cleaning battery contacts can help also check the side door, sometimes that can cause issues as well. air can out everything and clean metal contacts with rubbing (ipa) alcohol.
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
If it doesn't do it when its chargeing then it is the battery. I had bought my inspire from someone and it was having those issues ordered a new HTC stock battery from newegg for like $12 and has been working perfectly since then and honestly if you want the best battery rom absolution is the rom you should check out. It's a non sense rom but again I'd just buy a new battery. I had mine timed it'd reset at 92% 74% and 49% xD
Sent from my Inspire 4G using xda premium
spcclark said:
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
Click to expand...
Click to collapse
hmm, I would say try a new battery before getting a new phone. Worst case scenario is that you spent $15 to learn you need a new phone as opposed to spending $100+ on a new phone...this is of course assuming you want to keep the inspire and not just looking for a reason to get upgrade ahaha
I agree. It still sounds like a battery issue.
I would agree this definitely sounds like an internal short in the battery. Sounds like it's shutting off whenever it gets a significant load on it. Try a new battery first.
I had a similar issue though I was tweaking the CPU. Learned my lesson.
Sent from my Inspire 4G using XDA App
Yeah, Id bet money that its a bad battery. I had this same exact issue with my Inspire. If it shuts off more in low reception areas but it isn't shutting off when plugged in, its definitely the battery. I would try to find someone with an Inspire and try switching them batteries and see if it stops.
If I tried to use the flash with my camera, the phone would shut off. My phone would randomly reboot or turn off. ATT told me they had "some" bad batches of batteries. My phone was still under warranty so ATT sent me a new battery. All the problems went away!
The battery door on the Inspire becomes wonky the more you open it, I was having a problem like yours, new battery and new door has me going good.
Hi everyone, I've got a Nexus S 4g, SPH-D720.
This is the second time this happened to me: my phone's battery reached 0% and turned off, I turned it back on after plugging it in, and it turned off again for some reason. Tried to turn it back on, got stuck in a bootloop.
(I was running Apex 1.1.2 at the time that this happened, but it has happened before when I was on CM 9 v4.0 as well. The first time, I was using a calibrator app that told me I had more battery left than my phoen was displaying, so after it powered off I took the battery out and put it back in multiple times to see if the phone would turn on. It didn't. However, I did not do that this time, but the same thing happened.)
I tried clearing cache and flashing the same rom over the current one, but the loop persisted, and the only way to get my phone back was to do a data wipe/factory restore and reinstall everything from scratch.
The first time this happened, I had last backed my app up via Titanium 2 days prior. After the first time, I set Titanium to make backups every night, so the only thing I lost were a few text messages.
Now, I'm afraid to turn my phone if the battery dies in case this happens again and I have to erase everything. Is there any way I can figure out what the problem is? I suspect it is the ClockworkMod Touch Recovery (v 5.8.0.2), but has anyone else had this issue?
I appreciate you taking your time to read all the way through this.
What setting do you have cpu at? If its set too high your system cant handle the boot process correctly. If theres no power to handle the load itll reset itself. Wait until you get at least a solid bar or completely full and start your phone. Dont trust apps to properly tell you your battery percentage.
sent from nexus s running kangyu 2.2.1 rom/ 3.0.31 CM9 Ink kernel on xda premium
I forgot to add. The recovery is not causing the problem it has to do with battery and/ or rom/ kernel. And its not good for battery to constantly be run to zero. Thats why theres a warning to plug your phone in at a certain percentage.
sent from nexus s running kangyu 2.2.1 rom/ 3.0.31 CM9 Ink kernel on xda premium
Processor is set to 100 min 1200 max. Yeah, I did have the same kernel so that's probably it. I'll try not to turn my phone on until it's charged while off. Thanks!
(btw, the "app" I was using was a battery calibrator script)
Your welcome and i was having issues the same way and turned off set on boot and it didnt happen again. Some of these phones are touchy! im sure you know about scripting if you did it! Lol
sent from nexus s running kangyu 2.2.1 rom/ 3.0.31 CM9 Ink kernel on xda premium
Can I just run this by you to see if there is anything you can add?
My wife’s phone started misbehaving recently it froze up and wouldn’t charge. On inspection I found it had had a little drink of water, only a very small splash but there was definitely some inside when I took the battery out to investigate. It was in her bag where a drink bottle spilled a little.
Anyway did all the usual stuff once I realised: stripped it out and put it in the airing cupboard overnight, still problems. With the remaining battery I managed to reload a clockwork backup I had on it and it seemed to start working, started charging and run for a while. It then froze. It seems the screen stops working but the vol and pwr buttons still function. Booting into recovery ALL functions work perfectly, I can run the tests (the lower screen buttons work) reload roms etc but as soon as I boot into the rom, mostly the screen refuses to work but sometimes it works for a minute or so (enough time to restore the user account after a factory reset). But after a while and always after the screen time out, nothing will work again, not even the power button. Needs a battery pull to allow it to run again.
Any ideas? I assume it is shagged. I was going to try a complete wipe and re install a new different rom. Any suggestions which one to try?
Thanks for any help.
Keith.
you said that you've pulled battery while the phone was running...you could fry the eMMC chip ("E: can't mount /cache/...." error in recovery) does your recovery show that error?
441Excelsior said:
you said that you've pulled battery while the phone was running...you could fry the eMMC chip ("E: can't mount /cache/...." error in recovery) does your recovery show that error?
Click to expand...
Click to collapse
No I am pretty sure it isn't fried. I know it is dodgy to pull the battery but since I recon the thing is buggered any way I have actually now done this dozens of times. The chip seems to be ok. How do I know for sure? I can mount and unmount the cache from within the revolutionary loader screen but it doesnt do anything or give any messages. Where would I see the error message?
I just loaded the new cm10 rom. It seems to work sort of ok running this though it did freeze once and the screen behaves funny. presses take a long time to register - like it is running really slowly and single taps usually respond as long pushed. I am going to try an old rom (3.5) with a full wipe and see if it is any better with this.
Thanks.
Also I had this error and also because of wather and the phone maked like yours. But....I put older recovery non touch clasic version of 4ext and after I recover a older backup and start working normal.... I think this you can do and don't cost nothing.
Sent from my HTC Desire S using Tapatalk 2
Hi. I'm somewhat new to the forum. I've read a lot of info on this website that helped me root my G1 when I had it and my Doubleshot. I was running CM 9.1 I believe and it was working fine. But then my girlfriend wet her phone (Sony Xperia) so I let her use mine while we waited to get her phone a new phone. While she was using my phone she somehow killed it. It won't turn on at all. I can get into bootloader from ADB but when I try to power it on from there, it goes to the splash screen then 1-2 seconds later it shuts off. At first I thought it was a battery issue so I ordered a new battery from ebay, popped it in but was still having the same issue. I had it overclocked to 1.7 Ghz I think and it would run hot sometimes when I would play a game. I'm wondering it got so hot that it actually fried something. Anybody have any idea what could be wrong with it?
chillywilly638 said:
Hi. I'm somewhat new to the forum. I've read a lot of info on this website that helped me root my G1 when I had it and my Doubleshot. I was running CM 9.1 I believe and it was working fine. But then my girlfriend wet her phone (Sony Xperia) so I let her use mine while we waited to get her phone a new phone. While she was using my phone she somehow killed it. It won't turn on at all. I can get into bootloader from ADB but when I try to power it on from there, it goes to the splash screen then 1-2 seconds later it shuts off. At first I thought it was a battery issue so I ordered a new battery from ebay, popped it in but was still having the same issue. I had it overclocked to 1.7 Ghz I think and it would run hot sometimes when I would play a game. I'm wondering it got so hot that it actually fried something. Anybody have any idea what could be wrong with it?
Click to expand...
Click to collapse
It could be that the high-intensity load is causing panic, shutting the device down. It could be that it doesn't like the overclock anymore.
Let's rule out a couple things.
Go into recovery (CWM / TWRP) and wipe data and cache (factory reset). Reflash Gapps while you're at it.
If recovery causes the same problem, reflash recovery in fastboot mode. If recovery still doesn't work right (shutdowns), you can try a different version, but it may really mean something got fried on your MT4GS.
If you were able to get recovery to do your bidding, reboot. Does the system still shut down on boot? If so, this time reflash CM 9.1 and GApps with the data/cache wipe, reboot. If still problems, try a different ROM, like Miktouch. If it fails there, then you may really be having hardware problems.