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!
Related
Well I used a hot reboot app for about the 50th time tonight, and it decided to kill my phone. It gets stuck at the AT&T screen and won't go past it. I've left it there for half an hour (don't wanna go too long because I don't like burn-in) and it just stays there. Tried battery pull, nothing. Running infusion kernel 2.0 core B (or whichever is the 200mhz stepping one) it was overclocked and set to performance mode at the time, which I have a feeling is what broke it. I'd do anything to fix it that doesn't involve completely re-installing the whole ROM and kernel and everything, I had to do that one night and it took about 12 hours. And I just can't be doing that with classes now.
So yes, an app has actually broken a phone for the first time in the history of ever.
If it helps at the very least in the recovery menu I can mount USB storage. I would try deleting the voltage controller boot settings but I don't think you can do that without actually having the phone running.
SNIPPY SNIPPY, WIPE ON (Mod Edit) clockwork MOD FIXED IT, i think.. probably jinxed myself there.
TheNetwork said:
Well I used a hot reboot app for about the 50th time tonight, and it decided to kill my phone. It gets stuck at the AT&T screen and won't go past it. I've left it there for half an hour (don't wanna go too long because I don't like burn-in) and it just stays there. Tried battery pull, nothing. Running infusion kernel 2.0 core B (or whichever is the 200mhz stepping one) it was overclocked and set to performance mode at the time, which I have a feeling is what broke it. I'd do anything to fix it that doesn't involve completely re-installing the whole ROM and kernel and everything, I had to do that one night and it took about 12 hours. And I just can't be doing that with classes now.
So yes, an app has actually broken a phone for the first time in the history of ever.
If it helps at the very least in the recovery menu I can mount USB storage. I would try deleting the voltage controller boot settings but I don't think you can do that without actually having the phone running.
SNIPPY SNIPPY, WIPE ON (Mod Edit) clockwork MOD FIXED IT, i think.. probably jinxed myself there.
Click to expand...
Click to collapse
It is not unheard of for apps that don't shut a device down properly to cause data corruption. Glad you got it fixed.
Thread closed
I've been using my SR for a week now and initially I had QuickWiz ROM installed but after getting some SOD, I switched to TPC ROM which worked great for few days as well but lately I have started getting random reboots that I have not been able to pinpoint the cause for.
I reinstalled TPC rom and then immediately got a reboot. After restarting the phone, it worked for few mins and then rebooted again. At this point, I reinstalled QuickWiz and just within an hour, I have already gotten two reboots.
Any suggestion what might be causing it? Could it be hardware related?
You might try flashing the stock 2.3.5 or 2.3.6 ROM and KERNEL and see if random reboot problem goes away... then you'll know it's not a hardware issue. Check the Development section and read carefully... probably need to clear cache/data multiple times.
DoctorQMM said:
You might try flashing the stock 2.3.5 or 2.3.6 ROM and KERNEL and see if random reboot problem goes away... then you'll know it's not a hardware issue. Check the Development section and read carefully... probably need to clear cache/data multiple times.
Click to expand...
Click to collapse
I ODIN back to stock yesterday and everything worked for until today when I got the reboot when opening email which leads me to believe that there is a hardware problem somewhere. I have already gone through three different ROMS (including stock) and I always get random reboots sooner or later.
So do you now have 3e recovery... or is CWM Recovery still your recovery partition? From what I've read, you need to clear data and clear cache up to 3 times each from 3e recovery.
DoctorQMM said:
So do you now have 3e recovery... or is CWM Recovery still your recovery partition? From what I've read, you need to clear data and clear cache up to 3 times each from 3e recovery.
Click to expand...
Click to collapse
I gave up on this and called Amazon. They are shipping me a new SR overnight
ajamils said:
I've been using my SR for a week now and initially I had QuickWiz ROM installed but after getting some SOD, I switched to TPC ROM which worked great for few days as well but lately I have started getting random reboots that I have not been able to pinpoint the cause for.
I reinstalled TPC rom and then immediately got a reboot. After restarting the phone, it worked for few mins and then rebooted again. At this point, I reinstalled QuickWiz and just within an hour, I have already gotten two reboots.
Any suggestion what might be causing it? Could it be hardware related?
Click to expand...
Click to collapse
I had the same problem and was really confused and then I think I figured the problem out. Do you have one of those thin leather mobile phone cases that attach to your belt? I notice when I put my brand new SR in my case that I purchase that when it moves even just a little bit it will push down on my power button and shut it off and back on. Is there any chance that is happening. I know it sounds stupid but I does happen to me.
reubendevries said:
I had the same problem and was really confused and then I think I figured the problem out. Do you have one of those thin leather mobile phone cases that attach to your belt? I notice when I put my brand new SR in my case that I purchase that when it moves even just a little bit it will push down on my power button and shut it off and back on. Is there any chance that is happening. I know it sounds stupid but I does happen to me.
Click to expand...
Click to collapse
Nope, that was not the case because my phone was rebooting either when I was on call or even when it was just sitting on the table.
I had two reboots last night. Both times, I was On the phone using headphones and phone was plugged into a charger.
It seems to reboot if It's plugged in and am on the phone at the same time. It does get pretty warm.
WTF.
I have been having the same issue with my Skyrocket. I am also using TPC v3 ROM, haven't tried to put the stock rom yet, but one thing for sure that this problem is not persistent.
When this problem start, my phone keep restarting for at least 5-10 times and it doesn't allow you to do anything in between. Once it starts working you won't see the booting issue again.
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.
I've been trying different ROMs (SlimICS, CM9, MIUIv4, Brainmaster's CM9, CyberGR-MOD), kernels (Air, Matrix), other stuff (Fidelity 2.0, changing screen DPI to 182 and 200).
First, after flashing fidelity restore zip I noticed that my phone started to get warmer than usual when I was listening to the music (regardless of player used, deep idle on or off). It was SlimICS which had several more bugs, so I flashed another ROM, and the problem seemed to be gone (but still there was some extra heating during music playback).
After that, my phone started heating when using noinnon's gReader. I thought it was some issue with this app, so I just removed it, and again I thought the problem was solved.
After that, I wasn't using my phone for about 3 weeks (it was fully charged and switched off). When I started using it again, I noticed some heat when using the phone (just screen on, some data usage, regardless of app).
Another day I used Wi-Fi AP for a few hours (while charging) and I was shocked: my phone got so hot I could barely hold it. It wasn't the battery (battery temp was 45 degrees). I thought it was some issue with the radio, so I tried flashing KD1 and even KB3, but doing that didn't make significant difference. I also tried doing full wipe (wiping all partitions I had access to using CWM Recovery, wiping battery stats, Dalvik cache) and flashing stock ICS, CM9, CM7.2, and even unrooting and flashing stock 2.3.6 GB - no difference.
Now it got even worse. Battery life is terrible (barely 8 hours on full battery with about 1 hour of screen on and few hours of music), and my phone heats up even if I just navigate the menu.
Does that mean my hardware is messed up? Is there any way to fix this?
P.S. Though I still have 1 month of warranty, it's not valid in my country (there were no official Nexus S sales), so I can't return my phone.
Did you also format /system and /boot (CWM -> mounts and storage) partitions?
Also, i'd advise flashing the factory images via fastboot. Commands can be found within the archive (flash-all.sh). I would do this:
-backup EVERYTHING on the phone (efs too if you havn't done so already, search for more info)
-download/extract 4.0.4 image for your particular model
-boot to fastboot, plug in usb, type commands in order as shown in the .sh file
-reboot, and hopefully your overheating problems are gone
Have you tried to switch off 3g data traffic? Try to switch to airplane mode and then turn on wifi and look what happens.
Probably the cell radio causes the heat!
Installed ICS OTA update and I think it helped. Didn't get to use my phone as usually, but battery life got better and there's no overheating during music playback. Still not sure if the problem is gone completely.
Thanks everyone for feedback
The original overheating issue beforehand could probably be traced to a rogue app.
I had the same problem and I tryed to wipe everything, but unfornately my battery lifeare lowered compared to some months before..
Now I flashed back via ODIN, the oficial ROM and updated from GB to 4.0.4, to see if that fix the problem....
View attachment 1177499
chronophase1 said:
The original overheating issue beforehand could probably be traced to a rogue app.
Click to expand...
Click to collapse
As I mentioned before, I tried wiping everything and flashing stock ICS, CM9, CM7.2, and even unrooting and flashing stock 2.3.6 GB. The only app common between these ROM's is SuperUser (I didn't install back my usual apps)... but 2.3.6 I flashed didn't have it.
Make sure nothing is overclocked. Try another battery also. Worth a shot
Edit: didn't see you have it sorted. OTA solved it.
Sent from my Nexus S using 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