Hi,
I have been trying to flash few roms. I constantly do though. Last rom I was on, I found that the battery drained very quickly and it keeps changing its stats in a random way.
I decided to flash new roms, and since, I flash the rom, and then the phone turns off by itself. I tried few different kernels "of course the right ones", and some seem to help for few more minutes, but that is not the case.
I tried to flash the latest version of "FOXHOUND ROM' for the i9505, and it would show the boot animation and then turns off instead of starting the phone. Tried to wipe cache and all the stuff, and still the problem persisted. Could it be a bad battery all of the sudden?
matteosaeed said:
Hi,
I have been trying to flash few roms. I constantly do though. Last rom I was on, I found that the battery drained very quickly and it keeps changing its stats in a random way.
I decided to flash new roms, and since, I flash the rom, and then the phone turns off by itself. I tried few different kernels "of course the right ones", and some seem to help for few more minutes, but that is not the case.
I tried to flash the latest version of "FOXHOUND ROM' for the i9505, and it would show the boot animation and then turns off instead of starting the phone. Tried to wipe cache and all the stuff, and still the problem persisted. Could it be a bad battery all of the sudden?
Click to expand...
Click to collapse
Go back to stock first, and check if that has the same problems...
matteosaeed said:
Hi,
I have been trying to flash few roms. I constantly do though. Last rom I was on, I found that the battery drained very quickly and it keeps changing its stats in a random way.
I decided to flash new roms, and since, I flash the rom, and then the phone turns off by itself. I tried few different kernels "of course the right ones", and some seem to help for few more minutes, but that is not the case.
I tried to flash the latest version of "FOXHOUND ROM' for the i9505, and it would show the boot animation and then turns off instead of starting the phone. Tried to wipe cache and all the stuff, and still the problem persisted. Could it be a bad battery all of the sudden?
Click to expand...
Click to collapse
For some reason I have tried this a lot on my old phone... Some kernels worked for mine and others not... While it should..
Flash stock and see... Keep stock kernel and flash rom, if no problems then try new kernel... If problem returns then flash stock kernel again
Sent from my GT-I9505 using xda app-developers app
DenmarkRootN00b said:
For some reason I have tried this a lot on my old phone... Some kernels worked for mine and others not... While it should..
Flash stock and see... Keep stock kernel and flash rom, if no problems then try new kernel... If problem returns then flash stock kernel again
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the tip. I tried that as well, but Unfortunately, the same problem. I don't have a problem what so ever when I am using the phone while it is charging or plugged in, but as soon as I take it out, and even if it is full, it shuts off, tries to turn back on and it wouldn't, it keeps rebooting, once i plug the charger in it, it would stay on.
That tells me either:
The Battery is bad!
Or
There might be a circuit problem with the phone sucking power out of the battery!
Related
Hey all, I've been running Ic3ROM 2.6 or 2.7 (can't remember now) for a while. Upgraded to that from the two previous versions of Ic3ROM.
Right now I cannot flash ANY ROM. I always end up having to restore my nand backup.
I've tried flashing DarchDroid 2.5, 2.6, 2.6.something, and 2.7. I've tried flashing Ic3ROM 2.9. Every time I do it flashes fine but when I boot I get stuck on the black HTC loading screen for 30+ minutes. Sometimes I'll hear the phone vibrate and see it start that loading screen over, too.
This is very frustrating as I'm such a fan of trying out different ROMs and the latest darchdroid looks fantastic (love AOSP).
Any ideas? I've tried wiping, wiping battery stats, rotate settings, dalvik, even my SD card.
remove your SD card from your phone after you flash, see if it boots then.
Thanks, will try that tonight. Hadn't even thought of it.
(Waiting on a call back about a major job interview so won't do it today at work, heh.)
No luck. I got impatient and tried your suggestion, Kcarpenter, and had no luck.
Thinking I'll just have to struggle with the RUU tonight. The only reason I'm so adamant about flashing a new ROM is that my phone reboots randomly when I hang up or when I try to answer a call. Occasionally just for fun it reboots when I look at it.
Is_907 said:
The only reason I'm so adamant about flashing a new ROM is that my phone reboots randomly when I hang up or when I try to answer a call
Click to expand...
Click to collapse
Here, try the OC kernel fix for those issues......http://forum.xda-developers.com/showthread.php?t=705074
Is_907 said:
I've tried flashing DarchDroid 2.5, 2.6, 2.6.something, and 2.7. I've tried flashing Ic3ROM 2.9. Every time I do it flashes fine but when I boot I get stuck on the black HTC loading screen for 30+ minutes. Sometimes I'll hear the phone vibrate and see it start that loading screen over, too.
Click to expand...
Click to collapse
Does your dalvik debug monitor (ddms.bat) output anything when this keeps happening? If so could you post that for us?
smolck said:
Here, try the OC kernel fix for those issues......http://forum.xda-developers.com/showthread.php?t=705074
Click to expand...
Click to collapse
That's not exactly the problem I'm having... no FC, just reboots.
But I'll try this anyway when I get home. Can't hurt, right?
Can you run adb logcat when it's booting? If you can post it on pastebin, we can probably help you out a bit more.
Now, This may have been answered or tied into the post by neidlinger, however I've found my problem to have some strange symptoms and was wondering if anyone could help me out.
I had my Glacier working just fine using the ice Glacier ROM, decided to try out some new ROMS including a couple Gingerbread roms. I updated Clockwork Recovery to 3.0.2.4 and flashed the roms, they seemed fine, but they weren't my cup-o'-tea. So I flashed back to IceGlacier 1.1.6. Ever since then My phone has had a boot loop issue that seems to be effected or triggered by power management. Not always, but sometimes If I plug my phone into the stock charger or otherwise, it'll reboot and sit there looping at the MyTouch splash screen until I pull the battery. Same happens on occasion when unplugging the phone. I can get it to boot into Android by letting it sit off for a while then come back to it a couple minutes later and power it on. Is there anything totally wrong with my device outside of what neidlinger posted?
Any help or advice will be greatly appreciated, Thanks!
Update!
Update: I found some time finally to look through some roms and flashed "Royal Panache" using CWM recovery 3.0.2.4. I still get the boot loops described above, still related to power, seemingly. If I plug the phone in while it's off, often it will start up on its own. Any help is still greatly appreciated . Please tell me if I'm just being stupid and/or blind.
try changing charger, or use pc charge and see if that happens
Thanks! I'll give it a whirl. Though I will say, it happens when using my car charger which is just a usb port.
Sent from my HTC Glacier using XDA App
You keep mentioning the cwr version as part of the flash process. Have you been reflashing recoveries each time you flash a new rom or something?
eqjunkie829 said:
You keep mentioning the cwr version as part of the flash process. Have you been reflashing recoveries each time you flash a new rom or something?
Click to expand...
Click to collapse
I have not, it's just added information. From what I've heard some recoveries only support froyo or only gingerbread.
atifsh said:
try changing charger, or use pc charge and see if that happens
Click to expand...
Click to collapse
It still happens when plugging into my pc.
Try restoring your phone to stock using PD15IMG, and see if it takes care of the problem.
If you have engineering bootloader - remember to reflash it after PD15IMG (it'll restore 0.86 stock bootloader when flashed).
If the problem won't be cured - it means that somewhere in your flashes you've probably damaged/overheated something in the phone, and now it needs replacement.
Jack_R1 said:
Try restoring your phone to stock using PD15IMG, and see if it takes care of the problem.
If you have engineering bootloader - remember to reflash it after PD15IMG (it'll restore 0.86 stock bootloader when flashed).
If the problem won't be cured - it means that somewhere in your flashes you've probably damaged/overheated something in the phone, and now it needs replacement.
Click to expand...
Click to collapse
Thank you very much for that bit of info. As soon as I get some time, I'll try that out.
Ok I'm on tasks aokp Rom and it works great. I have tried a couple of times to flash a new rom. I make sure that the battery is charged to 100% and flash the rom (tried with several different roms). It will work for a while, then it will crash to 0% and will boot loop because the battery reports 0%. I plug it in and it will boot up and start charging. At some point it will jump right back up to 100%.
I've tried battery calibration and no dice. The only thing that works is restoring my nandroid of tasks Rom.
My next step is doing a full wipe or going back to stock. I would like to avoid this if possible
Any help would be appreciated.
Sent from my Nexus 10 using Tapatalk 2
That is a very weird problem to have. Supposedly Android generates new battery stats at each boot, so not sure what is going wrong with your device.
Which ROMs have you tried flashing? If you are just trying to flash between different builds of AOKP then perhaps you should try a CM based ROM. Or if you are flashing from AOKP to a CM ROM, then try other AOKP based things only and see if the problem is still there or not.
EniGmA1987 said:
That is a very weird problem to have. Supposedly Android generates new battery stats at each boot, so not sure what is going wrong with your device.
Which ROMs have you tried flashing? If you are just trying to flash between different builds of AOKP then perhaps you should try a CM based ROM. Or if you are flashing from AOKP to a CM ROM, then try other AOKP based things only and see if the problem is still there or not.
Click to expand...
Click to collapse
It's happened with Mr Robinsons and rasbean and rassabre.
I always do a full wipe (dalvik, cache, factory reset)
Sent from my SGH-I747 using Tapatalk 2
There is something called battery calibration, try that. PM me for more info
shaker2k said:
Ok I'm on tasks aokp Rom and it works great. I have tried a couple of times to flash a new rom. I make sure that the battery is charged to 100% and flash the rom (tried with several different roms). It will work for a while, then it will crash to 0% and will boot loop because the battery reports 0%. I plug it in and it will boot up and start charging. At some point it will jump right back up to 100%.
I've tried battery calibration and no dice. The only thing that works is restoring my nandroid of tasks Rom.
My next step is doing a full wipe or going back to stock. I would like to avoid this if possible
Any help would be appreciated.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
what about the kernel did you try resetting or uninstalling the kernel tweaker apps before you installed a new ROM.
I wiped everything and flashed back to stock using the nexus toolkit.
Everything is working great now.
Sent from my SGH-I747 using Tapatalk 2
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Battery
Williamharv said:
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
I also think there's a problem with your battery, it might need to be replaced.
ebahena said:
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
Click to expand...
Click to collapse
Thanks for the quick reply! Would the battery explain why my ROMS wouldn't start though? Such as how Omega got stuck at the logo. I will try using my friend's battery, or just keeping the phone on charge whilst doing it and see how that works.
Im sending them through Usb currently, is there any other way to get it on my phone as I can't turn it on to send it over wifi :/
Sent from my GT-N5110 using Tapatalk
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
norml said:
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
Click to expand...
Click to collapse
Thank you for the reply i just got home so I'll try this soon, would it be risky though since my battery and/or cable may be damaged, meaning if it turns off during flashing stock, I'll get a hard brick?
Update: just reflashed Omega whilst it was on a charger and it actually worked.
Does this suggest that the battery is damaged?
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Obagleyfreer said:
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
I just checked my battery, it does start with BD, and it does appear to be somewhat swollen.. I haven't noticed it before :l Could I just return it to Samsung for a replacement, without going back to stock ROM? I'm currently in Australia, haven't really seen a Samsung support center anywhere nearby.
Update: got my hands on a new battery, everything seems to be working great now. Flashed paranoid android, no reboots or any other problems.
Thank you so much to everyone who helped
So I flashed mako-jb-kernel-028u-JWR on my nexus 4 and when I rebooted the notification light was flashing red. I booted back into TWRP and flashed mako-jb-kernel-027m-JWR to try and fix it. After I rebooted it was stuck on the boot animation with the flashing light. Whenever I started up TWRP the light would start flashing and the phone would turn off before I could reflash carbon rom. The light wouldn't flash when I was in fastboot . Now it won't even turn on, even if I plug it into power. I looked around and couldn't find anyone else with this problem. I'm assuming the battery ran out of power and I need to let it charge before I can do anything. Though last time I booted into TWRP the battery was above 90%. If someone could suggest something to do it would be great.
if nothing else works http://forum.xda-developers.com/showthread.php?t=2250454
simms22 said:
if nothing else works http://forum.xda-developers.com/showthread.php?t=2250454
Click to expand...
Click to collapse
I'm hoping I won't need to do that since I don't have a T5 screwdriver and I don't trust myself with manually charging a battery with a power supply.
I should also mention that I used this https://play.google.com/store/apps/details?id=com.nema.batterycalibration&hl=en about an hour before flashing the new kernel.
Try first to flash stock kernel.
If this doesn't work then reflash whole factory image.
Sent from my NookColor using Tapatalk 4
RASTAVIPER said:
Try first to flash stock kernel.
If this doesn't work then reflash whole factory image.
Sent from my NookColor using Tapatalk 4
Click to expand...
Click to collapse
The problem is that it won't even turn on. I think it ran out of battery and its refusing to charge.
Alright so I did some searching and found this post http://forum.xda-developers.com/showpost.php?p=43291951&postcount=27 I did that and my phone can actually boot up now. Also I should mention that you need to hold the buttons for EXACTLY 60 seconds or it won't work. I'll let it charge and attempt to reflash Carbon Rom after.
TWRP kept closing on me before I could reflash Carbon, so I restored to the stock rom and kernel using WugFresh's toolkit. I couldn't boot into the rom until I went into fastboot, went into stock recovery, and restarted my phone. Now I can boot up perfectly fine! Also I flashed the latest faux kernel again just to make sure it was the problem, and after flashing mako-jb-kernel-028u-JWR I got the red led again, So I'm advising everyone to stay away from that build.