Hi, i have know idea what's going on, all I know is this settings app added all these icons on my home screen, so i deleted the app. An hr later i'm losing signal, so i went to turn on wifi to use the connection from my router. Soon as I turned on wifi (on the phone) my screen went black, but the bottom buttons (home, search, etc.) are all lit up, but the entire screen is black. I press every button, hold down every button, etc...it wont wake up. I've rebooted several times. It reboots fine, then 10 seconds later it goes black or the phone will reboot.
To make a long story short, i hated that i lost my info. But, I did a hard reset. BTW, my G2X is rooted, I've been running this same MIUI Rom for several months with very few problems.So I wiped data/cache, did the hard reset and my phone worked fine for a day! Sad about losing my data, but happy to have my phone back and not having to spend some money i don't have on a new phone.
Well last night, i fell asleep without putting phone on charger, I woke up and the battery was dead. I plugged in charger and the phone still wouldn't come on. I tried several chargers, so I just left the dead phone in the charger for an hour, still wouldn't boot up, finally after 2 hours it boots! It showed 90% on battery. So I think all is fine! I go to kitchen, come back and the screen is black again. Someone please help, Thanks
Related
My friend recently gave me an HTC Dash for T-Mobile. It's running WM6.1 Kavana's ROM 1.33.424.2. After he gave it to me I unlocked for AT&T completely, 100% legally. I called T-Mobile and they gave me the unlock code.
But since I've been using it it will randomly turn off. It seems to shut off more often using MMS or anything through the Internet, but it will also turn off just sitting in my pocket or while texting. Luckily it hasn't ever crashed during a call.
When I try to turn it back on it will either shut down before fully turning on (it will show the boot screen but turn off), it will turn on but say the battery is dangerously low and it needs to be shut down, or one time it had an error message saying "The device could not be started due to sudden loss of power. Click YES to continue or NO to shut down. Please be sure the device is completely shut down before removing the battery." If you click YES it shuts down. If you click NO the screen turns white then tries to start up a few seconds later and fails.
The way I stop this is plug it in to a charger and turn it on so it can't die. It says the battery is low but since its plugged in it won't turn off. Then once it turns on I turn it off normally by tapping the power button and selecting Power Off. Then I take out the battery, put the battery back in, turn the phone on, and then the battery is back to the power level it was before the crash and the phone works fine again. But any texts or calls I had made in the past few minutes are erased as if they hadn't been made, sent, or received.
I've already tried a few hard resets and it doesn't seem to work. I even downgraded to WM6. I just want to know if this is a software problem, a battery problem, a hardware problem, or something else. Thank you to anyone that can help.
Welcome to the forum
I assume that your battery is working ok right?
Try with a hard reset
Read here:
http://forum.xda-developers.com/showthread.php?t=397583
And:
http://forum.xda-developers.com/showthread.php?t=415225
Good luck,
I've tried the hard reset a few times, I don't know whats wrong.
So I've had my fuze a little over a year now, no major issues. Used mostly energyroms, but about December time I switched back to a simple non-bloated stock rom for the stability.
Anyway today at work I was texting, and I press the power button to put the phone in standby. And the screen remains on and usable. I tried again and it would not go into standby (power button physically feels normal, it does not feel loose or abnormal.) So i let it sit for a few minutes, then i look at it and a message poped up asking if i wanted to turn the phone off (like as if i was holding the power button)so i press no, then it comes up again a few seconds later and aagain and again. So I soft reset the phone.
The phone resets but takes a LOT longer at the att/htc splashscreen, then it hangs at the htc screen and does not make it to the wimo screen, but instead an error screen saying:
"The device is unable to boot because you have either turned off the device incorrectly or tried to install an applicationa from an untrusted source, press SEND to reset your device or press any other button to cancel..."
I think it went through the hard reset this time because when it restarted it asked to calibrate the screen and install stuff. it resets again sometime after that, still takes forever at the splash screen and comes back up to the error, only this time no matter what button i press it wont go away and boot into wimo. It seems like none of my buttons work (they wont light up now) when i slide out the keyboard, it is not lit up like normally.
And heres the kicker, my only way to turn on/off the phone is to take out/put in the battery. As soon as I pop the battery back in the fuze turns on. Is my phone toast? Ive tried to hard reset and the phone does not reach the bootloader, it goes straight to the splash screen. Same with trying to reflash it from my comp, raphealwrapper cannot find my phone.
I've only recently encountered the exact same problem on my Touch Pro, but stock ROM and everything. As far as I can tell, our power buttons are busted and probably need to be serviced. One of the contacts must be stuck in the 'on' position somewhere inside :\ As a temporary fix, I've been using AEButton Plus and remapped double tap end call key to turn the screen off, and removing the stylus to turn it on.
Hi
Strange occurrence today. Turned on phone--nothing. Reset battery and it booted fine, but after awhile (when the screen timed out) it went back to black. When I turn it on it goes to dark blue (BSOD?) but nothing else happens, however as soon as I reset the battery, it will boot successfully and as long as the screen is on, the apps seem to work etc. As soon as I lose the screen, I lose the phone again. Volume down followed by power switch brings up the same BSOD.
The lcd is on and the phone is apparently charging regardless.
Can anyone help get me back in business?
Thanks
So I left work today at 5, paired my phone with the bluetooth in my radio, after I installed Skyfall last night. Pandora was supposedly playing and connected to the radio, but nothing was playing. I toggled the radio a few times and noticed that now only media was playing but no phone. I turned off the bluetooth on the phone thinking that was the problem.
The phone immediately disconnected from my pebble, expected. The bluetooth quick toggle was spinning like it was busy, so I waited. When the light turned green I put the phone in the cupholder. By the time I got to the next light the phone was off, not connected to anything and a bit warm.
The entire 40 minute ride home the phone was hot, and would not turn on or connect to anything. I tried holding the power button down for 10-30 seconds at a time to reset it, but it would not reset. I have tried this multiple times.
I'm home now, connected to the charger but have no charging light, and it still won't turn on. It has cooled off a lot in the past 10-30 minutes
Past couple days I've tried flashing a few things. After the last reset I installed Skyfall, power saver mod, faux kernel, set cpu (and changed some settings) and restored my app backups. Everything was running fine until I tried to connect to the bluetooth on my raido.
I can connect the phone to my computer, and windows recognizes a device connected, but neither ADB or Fastboot see the phone
Am I missing something on the hard power off?
Insertnamehere12 said:
So I left work today at 5, paired my phone with the bluetooth in my radio, after I installed Skyfall last night. Pandora was supposedly playing and connected to the radio, but nothing was playing. I toggled the radio a few times and noticed that now only media was playing but no phone. I turned off the bluetooth on the phone thinking that was the problem.
The phone immediately disconnected from my pebble, expected. The bluetooth quick toggle was spinning like it was busy, so I waited. When the light turned green I put the phone in the cupholder. By the time I got to the next light the phone was off, not connected to anything and a bit warm.
The entire 40 minute ride home the phone was hot, and would not turn on or connect to anything. I tried holding the power button down for 10-30 seconds at a time to reset it, but it would not reset. I have tried this multiple times.
I'm home now, connected to the charger but have no charging light, and it still won't turn on. It has cooled off a lot in the past 10-30 minutes
Past couple days I've tried flashing a few things. After the last reset I installed Skyfall, power saver mod, faux kernel, set cpu (and changed some settings) and restored my app backups. Everything was running fine until I tried to connect to the bluetooth on my raido.
I can connect the phone to my computer, and windows recognizes a device connected, but neither ADB or Fastboot see the phone
Am I missing something on the hard power off?
Click to expand...
Click to collapse
Have you tried holding down power and volume up? When I was using the stock rom rooted with the insecure kernel my phone was running hot and I turned it off and it wouldn't power back on. Nothing worked until I pressed power and volume up - give it a shot.
bloodiedwraith said:
Have you tried holding down power and volume up? When I was using the stock rom rooted with the insecure kernel my phone was running hot and I turned it off and it wouldn't power back on. Nothing worked until I pressed power and volume up - give it a shot.
Click to expand...
Click to collapse
I swear I was trying this in the car... and several attempts after... But that worked! Maybe it was because I had it on the charger when I did it this time?
Why would they ever make you hold two buttons for a hard reset ><
Phone is on now, Thank you for your assistance!
They gave us back our SD Cards... Now give us back our removable batteries!
Insertnamehere12 said:
I swear I was trying this in the car... and several attempts after... But that worked! Maybe it was because I had it on the charger when I did it this time?
Why would they ever make you hold two buttons for a hard reset ><
Phone is on now, Thank you for your assistance!
They gave us back our SD Cards... Now give us back our removable batteries!
Click to expand...
Click to collapse
Awesome, glad it's up and running.
Hey i am new to this forum,so sorry if i am posting this in wrong section or smtn like that .So yesterday i was searcing the web when suddenly my screen turned completely blue!That lasted for about a second ,and then it came back to normal.After a few seconds it happened again but many times in a row.I tryed to power it up ,but on boot,it turned blue again and shut down again.It was off whole night,and at morning,it booted normaly,andbi managed to move all my data to computer.After i finished that,i tryed looking what could be the reason for this to happen.But phone shut down again.Till now i was able to turn it on for about 2-3 seconds and then again shut down.The thing that i noticed is that when phone is booting,it will warm up pritty fast,but not at some high temepratures,but that much that i can fill that it is hotter.I decided to try to put it charging,but the battery icon would appear,and after few seconds screen would be blue again,but it would charge.I also noticed that led indicator was showing charging but with low light.I decided to factory reset,oressed few buttons and screen turned off,but led indicator became much more noticable.Now it wont turn on.I tryed power cycle but it does nothing.Any solutions?My phone is alcatel idol 3 6045k with stock 5.0.2 android.
assuming your phone has a charge.
press and hold the power button till the acatel boot screen shows up.
the phone should reboot this may take 30 seconds to 1 minute to reboot.
you might see if you can get into the boot loader also.
it could be worse issues wich others here might be able to help more with.
Sounds like a hardware failure. I recommend sending it in for repair or replacement.
warranty repair...