I have had three Mytouch 4gs replaced because every one of them I get turns itself off and wont turn back on until the battery is pulled out and put back in. This happens about 6 times a day.
I have tried a new SIM card, new sd card, new battery, factory reset, factory reset with a format of the sd, and they still turned off even without any apps installed and not signed into google.
I am baffled. Does anyone here know what could be wrong here?
i dont know why this has happened to you so many times but it happened to me this morning and immediately after the battery was pulled and reinserted i went to rom manager and fixed permissions. took a while to finish cause i have buku apps but hasnt happened since.
hope it helps ya!
I was running completely stock when this happened, but I've since upgraded to virtuous fusion. Is it better to boot into recovery using CWM to fix permissions or am I fine doing this from the app?
Well I fixed permissions through CWM and it just turned off on me again. Ugh. I'm guessing its not a problem with the rom but with my hardware. Should I try flashing the latest radio?
Does anyone else here have this problem? Wtf is going on?
idk if its the same problem you're having but mine has recently started turning the screen off, the buttons still turn on as well as the led blinking if i have a notification but the screen wont come back on until i do a battery pull
so i'm also wondering what the problem is, fyi i'm using the kernel that came with cm7 and the latest radio
Hmm not sure. When my screen wont turn on I get no lights at all.
One of the causes can be the battery going bad.
I had the same issue until they sent me a new battery.
Sfkn2 said:
One of the causes can be the battery going bad.
I had the same issue until they sent me a new battery.
Click to expand...
Click to collapse
I have tried many different batteries with no effect.
I have noticed however that if it goes unresponsive and I plug it in the charging light comes on and I am able to boot the phone. It will turn off rather quickly though. Like in 20 minutes as opposed to 2 hours. Very weird.
Wow has anyone found a solution for this Problem? I can go into recovery and flash roms with no problem but as soon as it boots to the home screen its just automatically shuts off. Only twice have I gotten it to actually stay on for an hour or so. Also while charging it flashes green then orange, I have two different batteries, any ideas?
Well mine is the same it started after a small six to eight inch drop on the floor and it randomly freezes and when i boot it up just goes into boot loader and after a while of it being off it will go into OS any ideas anybody I am thinking it has something to do with bad chip but what do i know lol tel me know if anybody finds anything out thanks in advance
I've begun encountering the same problem after flashing MIUI 2.3.30 ROM. And I've also noticed that my phone started to get hot. It never did this before. I know my battery is fine, I also re-calibrated my battery and everything. I am even also thinking that for some reason my phone is bricked. It holds charge for about 10 minutes before it dies, even on the new battery, which I have tested on another MT4G and works perfectly. The other phone is my nephews. I wonder if this has to do anything with the bad EMMC chip?
Any input for solving this will greatly help.
Reboots
drunk21 said:
I've begun encountering the same problem after flashing MIUI 2.3.30 ROM. And I've also noticed that my phone to get hot. It never did this before. I know my battery is fine, I also re-calibrated my battery and everything. I am even also thinking that for some reason my phone is bricked. It holds charge for about 10 minutes before it dies, even on the new battery, which I have tested on another MT4G and works perfectly. The other phone is my nephews. I wonder if this has to do anything with the bad EMMC chip?
Any input for solving this will greatly help.
Click to expand...
Click to collapse
You might have already looked at this but have seen in some other roms I have been working with is to make sure to check the md5 sum before flashing just because it flashed doesent
mean it was right it takes is slight hickup in a download and a bit of garbage where it don't belong. Better to check it do the full wipes even a couple times or maybe even mounting and format the boot n system partitions so if on a particular rom ask in its section.
Hope that helps, wish ya well
I would agree with the above post making a clean wipe, and even the format does help. I have been trying out almost all of the newest ICS roms avaliable and I notice it helps when wiping everything/format system and boot. Even the newer ICS rom Awesomev2.1 suggest doing so for the system partition.
As others have stated, you might not have performed a FULL wipe.
Reflash, but do the wipe (I did also wipe battery stats..seemed to help in my case)
Random restarts and won't load
Had the same issue when I switched to Virtuous Unity... battery wouldn't hold a charge and would randomly restart.
After basically nuking my phone (full wipe, cache/battery wipes, etc.), as well as installing Creamed Glacier, the battery life is better but the random restarts are not. Plugging the phone in is the only way to keep it from restarting constantly, where it will load the T-Mobile splash screen but turn off either immediately after or as the home screen loads. But the battery is always at least 50% when I plug it in and it stays on. It also seems to take forever to recharge (plugged into laptop).
I want to think it's a battery issue, but the fact that it's not dead when I plug it in makes me think it's a hardware issue. I can't send it in to T-Mobile (shipping charges and time would be huge, as I'm in a foreign country and I rely on it so much for communication), and I'm loathe to buy a new phone.
Anyone have any ideas?
ivioi3ius said:
Had the same issue when I switched to Virtuous Unity... battery wouldn't hold a charge and would randomly restart.
After basically nuking my phone (full wipe, cache/battery wipes, etc.), as well as installing Creamed Glacier, the battery life is better but the random restarts are not. Plugging the phone in is the only way to keep it from restarting constantly, where it will load the T-Mobile splash screen but turn off either immediately after or as the home screen loads. But the battery is always at least 50% when I plug it in and it stays on. It also seems to take forever to recharge (plugged into laptop).
I want to think it's a battery issue, but the fact that it's not dead when I plug it in makes me think it's a hardware issue. I can't send it in to T-Mobile (shipping charges and time would be huge, as I'm in a foreign country and I rely on it so much for communication), and I'm loathe to buy a new phone.
Anyone have any ideas?
Click to expand...
Click to collapse
I really hate to be redundant, but you formatted /system and data? System gets missed a lot and you didn't specifically mention it.
Sent from my HTC Glacier using XDA
I have had the same problem with ics zips 4.01 all of a sudden the phone stops responding to the power button and have to take out the battery and boot up the phone but as of yesterday with the 4.02 I have had the problem. I don't know if it due to the heat cause where I live it hot and its just the beginning of summer too?
Related
As the title says I have a strange yet very annoying problem. I am running my HD2 with hyperdroid cm7 Nand build (from april 29th). The problem is that when my battery is deleted, as is the case now, and I put my hd2 in the charger it will automatically boot. I think this is due to a setting or something. However since booting drains energy faster than the hd2 charges, the phone will by turned of before it has completely booted. After a while it get's stuck in a pattern of starting to boot and turning of. I don't know why this is the case because I think my phone just used to boot fine before when connected to a charger.
So my questions are:
1. does anyone has a suggestion how to turn on the phone?
2. this automatic booting, can it be turned off?
3. Why is it actually happening?
Maybe it's a very stupid or obvious problem, but I hope someone can help me though.
Do you have installed MGLRD?, it's a Known fact, search in the forum for answer (I'm sorry, I'm with SD Builds and don't use MGLRD, so I can not help you anymore).
I had the same problem with some rom i used earlier. The only way i could solve the issue was to remove the battery and put it back, then I could insert the charger without the phone booting up. Charge it for a while and start it.
Hope this way works for u 2.
Sent from my Desire HD using XDA App
I guess this is what I used to do as well. However now, if I remove the battery and put it back in it keeps automatically booting. Also if I put the charger in the phone and then remove the battery same thing happens. But thanks for the help though.
I am currently using the same ROM via MGLRD. Because of MGLRD, it will always turn on the phone from off when you plug your phone in. This is a known feature of MGLRD to preserve the battery. Checking just now, I turned my phone off, plugged in my charger and the phone automatically booted itself then the lockscreen came on then turned itself off after one minute. This is the cycle I see every time I charge my phone if it is off. I do not see it going into any boot cycle. What I see is after it goes through this, the orange LED light is on letting me know it is charging and will change to green when it is fully charged. Did you make sure before loading the ROM to do a complete wipe before installing? Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.
slbenz said:
I am currently using the same ROM via MGLRD. Because of MGLRD, it will always turn on the phone from off when you plug your phone in. This is a known feature of MGLRD to preserve the battery. Checking just now, I turned my phone off, plugged in my charger and the phone automatically booted itself then the lockscreen came on then turned itself off after one minute. This is the cycle I see every time I charge my phone if it is off. I do not see it going into any boot cycle. What I see is after it goes through this, the orange LED light is on letting me know it is charging and will change to green when it is fully charged. Did you make sure before loading the ROM to do a complete wipe before installing? Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.
Click to expand...
Click to collapse
Well, this cycle I think is caused by the fact that the charger is not strong enough. Normally if plugged in the phone would just boot. The reason that it fails to boot is that is doesn't have enough power to complete the boot cycle even though the phone is plugged in (don't know if booting consumes a lot of power?).
A month ago I bought a new usb cable. Maybe that's where the problem lies? Because I have been using the hyperdroid rom for a while now. Although I don't know if one cable can be stronger than the other.
I have found a solution btw: Though it is a bit hit and miss cause it didn't work a few hours ago. When booting I let it go into mgldr and let it charge there. After a while I'll let it boot when it has enough power to complete the boot.
slbenz said:
Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.
Click to expand...
Click to collapse
Humm, now you making me think lol, the 1st time I installed Android on my HTC HD2 was the NexusHd2 rom one and he had the same problem, no battery but once I plug it to the wall charger it would do the full(normal)boot, I thought was the rom so I changed to Hyperdroid Cm7, but, still does the same..
The wipe you talking is the one, wipe data/cache right?
if it happens to you a lot, I think it's time to invest in a third-party battery charger. you can charge it out of the phone for a bit, and then you're safe to put it back in a continue charging using the phone
Tried some different roms and all them do the same.. so I reckon its normal.. Thank You.
So after a long fiasco of installing an old GB leak before installing the latest version, to running into force close loops and freezing at the M logo. So finally i reflashed everything and rebooted and bam! i finally got 596 to work. But i noticed that my battery logo had a question mark and that it basically wasn't recognizing my battery. I thought maybe a simple reboot will fix it, went in cwm and flashed the 596 deodexer and rebooted. Got into the lock screen when i noticed it immediately said Connect Charger. When i unlocked the screen after about 10 seconds it went black and my phone wouldn't turn on. If i connect it to pc the led flashes blue for a second meaning the battery is dead but with the battery not being recognized it cannot charge. If i connect it to a wall charger it loads up the M logo and goes to the battery charging screen, when you completely drain your phone and need to wait til its 5% to turn on, but again has a question mark in it. I don't have any external chargers either. Whats my best course of action? Do i have to go out and buy a new battery...? All helps appreciated.
im very sorry about bumping my thread.., but my phones just sitting here useless and its very aggravating and extremely inconvenient so once again, any and all help is appreciated please gentlemen(ladies).
If you can boot even for a second, boot into clockwork recovery and find the option to wipe battery stats. I would try that.
Also, even with a charge, booting while plugged into AC causes it to show the charging screen. Unplug it, turn on your phone, and in the middle of booting THEN plug it in.
Sent from my DROIDX using XDA App
djsupersoak said:
If you can boot even for a second, boot into clockwork recovery and find the option to wipe battery stats. I would try that.
Also, even with a charge, booting while plugged into AC causes it to show the charging screen. Unplug it, turn on your phone, and in the middle of booting THEN plug it in.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Thank you for the reply, ill try wiping the batter stats asap might have to end up ghetto rigging a charge into it. Ive heard that car chargers/external chargers will still charge it, is this correct? I would love to try your second idea except for again i don't even have a charge anymore. i tap the lock button and the led flickers blue for half a second, which if im not mistaken means the battery is completely dead. While i guess its always possible, never really expected my phone to just randomly stop realizing there's a motorola batter inside of there.
Edit: also if im not mistaken i believe that i had tried to plug the charger into after/during boot up and it still says its not a certified battery or whatever the message is and refuses to charge.
Not entirely sure about the car charger idea. It might work. Kind of skeptical on that if it won't even charge when connected to a computer. You could always purchase a new battery, maybe the extended. If it doesn't work just return it. If you don't want to purchase one, I possibly could ship you an extra one just to borrow and try to see if it's a battery or phone issue.
If you have a friend with another droid x you could try borrowing his or her battery to see if the actual battery is the issue without buying one...
It sounds to me like the battery stats on your phone got corrupted when flashing the new software and need to be cleared, which as said before can be done in CW recovery. There is also an app called BatteryCalibration which will help the situation also after you actually get booted up.
Hope this helps!
Tone_Capone said:
If you have a friend with another droid x you could try borrowing his or her battery to see if the actual battery is the issue without buying one...
It sounds to me like the battery stats on your phone got corrupted when flashing the new software and need to be cleared, which as said before can be done in CW recovery. There is also an app called BatteryCalibration which will help the situation also after you actually get booted up.
Hope this helps!
Click to expand...
Click to collapse
I have actually seen the app before, at the time didnt really notice what it did but i understand a bit more now. If any of the actual charging methods work ill definitely try that. Might just have to hook it up to a split usb for a while to get a decent charge.
djsupersoak said:
Not entirely sure about the car charger idea. It might work. Kind of skeptical on that if it won't even charge when connected to a computer. You could always purchase a new battery, maybe the extended. If it doesn't work just return it. If you don't want to purchase one, I possibly could ship you an extra one just to borrow and try to see if it's a battery or phone issue.
Click to expand...
Click to collapse
Thanks for all the help man, really appreciate it. Ill try the car charger i suppose, wont hurt. Worst case I do actually have a friend with a DX so i can see whats up with that. Ive been meaning to pick up the extended for a while now just never really got around to it, guess this might give me an excuse. thanks for the offer to send out a battery though
No problem. I've got a bunch of unused stock batteries for various phones from all the extended battery upgrades we've gotten.
In any case, if you can't wipe battery stats, trying a friends battery or something would be the next best thing.
What I would do if you borrow a battery, if it STILL shows the question mark then it is a phone problem. Boot into CWM and wipe battery stats while using your friends battery, then try your own.
Even if your friends battery works without giving the question mark, wipe stats anyways and maybe it will stop doing it for yours.
Best of luck to you with this!
Sent from my DROIDX using XDA App
djsupersoak said:
No problem. I've got a bunch of unused stock batteries for various phones from all the extended battery upgrades we've gotten.
In any case, if you can't wipe battery stats, trying a friends battery or something would be the next best thing.
What I would do if you borrow a battery, if it STILL shows the question mark then it is a phone problem. Boot into CWM and wipe battery stats while using your friends battery, then try your own.
Even if your friends battery works without giving the question mark, wipe stats anyways and maybe it will stop doing it for yours.
Best of luck to you with this!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Great news gentlemen! so after trying the usb split usb method to charge my phone, the first time it didnt work. i just figured i didnt have the wires pushing on the battery poles enough so i retried it. Ended up forgetting it was plugged in and about 30-45 minutes later took it off. plug her in and my phone started up, good signs so far. Finally my os loaded and lo and behold, there's my battery showing green! So i quickly throw it on my wall charger and its charging too. Wiped my battery stats just in case anyways and reflashed everything. Got 596 loaded up and running and deodoxed. After trying to install a battery mod i got a few boot loops but after a wipe didn't work luckily i made a 596 nandroid before trying it. Flashed back to that and everything loaded up fine. Cant thank you guys enough for the help you've been. making a nandroid once my full set up is back to normal haha
I dropped my phone a bit ago and had to replace the screen. I also damaged the battery when I removed it so bought a supposedly genuine one.
The replacement battery doesn't charge right. It will say it's fully charged when the phone is switched off but when I turn the phone on it could be anywhere from 50%-100% charged.
Recently my phone has started turning itself off randomly. It doesn't power down. Just goes from on to off.
And then today it's been constantly asking me to re-enter my sim pin. But the phone isn't resetting before this happens.
I've tried a couple of different ROMS and they both do this.
Strangely if I go into recovery the phone NEVER turns off.
Could a dodgy battery cause these problems? Or is it a hardware problem?
biron_w said:
I dropped my phone a bit ago and had to replace the screen. I also damaged the battery when I removed it so bought a supposedly genuine one.
The replacement battery doesn't charge right. It will say it's fully charged when the phone is switched off but when I turn the phone on it could be anywhere from 50%-100% charged.
Recently my phone has started turning itself off randomly. It doesn't power down. Just goes from on to off.
And then today it's been constantly asking me to re-enter my sim pin. But the phone isn't resetting before this happens.
I've tried a couple of different ROMS and they both do this.
Strangely if I go into recovery the phone NEVER turns off.
Could a dodgy battery cause these problems? Or is it a hardware problem?
Click to expand...
Click to collapse
Try it on stock ROM with a clean flash then report back
TheNerd:] said:
Try it on stock ROM with a clean flash then report back
Click to expand...
Click to collapse
I thought of that. I'll give it a shot.
Tried with stock 4.4.4 and I can't even unlock my sim card now. I put in my pin number and it just goes back to asking for it again. A message flashes for a split second that I can't fully make out but I know it says "failed" at the end. Hmmmm, I'm thinking it's a hardware issue. New battery is coming tomorrow so I'll see if it is that.
Got my new battery today and my phone is now working. Who'd have thought a dodgy battery would cause such weird issues?
Congratulations
Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks
Jz Chong said:
Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks
Click to expand...
Click to collapse
Have you tried making a clean wipe and trying either stock or another ROM, to see if it works then?
Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.
DrFredPhD said:
Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.
Click to expand...
Click to collapse
Hello, much appreciate your reply. I flashed back to stock 5.1.1 now and yet this problem is still persisting. Thus pretty obvious thats an hardware faulty.
In another forum, a guy with Nexus 7 had similar situation as me, and he suggests that its the battery or the circuit board at the charging port went kaput.
Guess nothing else I could do right now, gonna send in the phone for repair and hope the bill wont cost as much as a used nexus 4
The title says it all. For extra information:
So I got the battery full using universal direct battery charger and put it back. Switching it on without the charger plugged in won't work but switching it on with a charger plugged in does. You can even unplugged it after that vibration when turning on. That means, it's not the battery... you can even see the battery's full after booting successfully.
Not only that, with or without the charger, the S4 would heat up so much. No it's not the apps, even in safe mode or just while booting it would start to heat up. It wouldn't stop heating.
At first I thought the problem was the switch cause it won't turn on. Then I figured out it would turn on... but with the charger plugged.
Hmmm, any idea what cause it? It just happen all of a sudden one day. I'm thinking that, even if the switch or the port looks fine they may be the cause. Short-circuit I guess. Or I don't know, just my wild guess. If you experienced this one before, please share you experience and how you fixed it.
I'll add the edit I made on my reply here to make it easier to read.
EDIT: The heat is coming from the upper right area. Very close to where the switch is and sd card slot. Do you think it's the switch? If it's the switch, it's working well. No sudden reboots or shutdown due to the button acting like it's pressed when it's not, etc etc
EDIT: FIXED
Flashed Albe95's LolliRom http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564 and also flashed Imperium Kernel (afterwards... because I thought I already did -_- )
At first I thought I would switch ROM to see if it's really the ROM that caused my problem (Stock with AEL kernel).
I downloaded Albe95's ROM and it took some time before it really boot successfully. On the thread it says that it would after 15mins, but mine after 15mins is still not booting. I flashed many times thinking that I made a mistake, like I forgot to wipe, etc etc.
The overheat problem was still there while it boots. It gets really really hot. I thought it is really a hardware problem now, I flashed a new ROM and therefore the kernel was changed, and if it was changed and it still has that problem my conclusion was right.
BUT...
I put it in the freezer to battle the heat. When I took it from the freezer, the phone's off. I thought the coldness what made it turned off. I took it, charged, and turned it on. And when it turned on after plugging it in... the battery's empty. It was around 50% when I decided to boot again and wait.
While it is still cold, I tried to turn it on again and wait now this time for it to boot.
Albe95 said it would take around 15mins only, but mine did boot past 15 mins. Can't blame me why I thought it's stuck on bootloop for many times. Now I'm thinking if I have only given Imperium ROM a chance... HAHAHAHA too lazy to flash and wait for a long time again.
Please hit thanks if I helped someone in the future with these issues.
what s4 model, rom and kernel do you have ? any mods ?
the battery could still be the problem. can you test it with another one, a friends maybe ?
Maybe a short circuit by sweat water that got into the phone. Open it up, take the board and other other easily removable components out and clean them with Isoprophyl(cleaning alcohol) and a new/clean soft brush, reassemble and see if it helped.
Backe888 said:
Maybe a short circuit by sweat water that got into the phone. Open it up, take the board and other other easily removable components out and clean them with Isoprophyl(cleaning alcohol) and a new/clean soft brush, reassemble and see if it helped.
Click to expand...
Click to collapse
This might do. Did not thought of this.
It's more on hardware I guess... Not kernel or ROM problem. Or, ok fine, just to be sure I'll try to flash Albe95 ROM. I am on Stock before and accidentally wiped the system partition also while trying to factory reset via recovery instead of data, cache, and dalvik only. Even without the ROM, it overheats very much.
EDIT: The heat is coming from the upper right area. Very close to where the switch is and sd card slot. Do you think it's the switch? If it's the switch, it's working well. No sudden reboots or shutdown due to the button acting like it's pressed when it's not, etc etc