[Q] HTC Sensation Unresponsive - HTC Sensation

Hi guys,
I have had my Sensation rooted with ARHD for about 4-5 weeks and everything has been smooth till now, when yesterday I was just reading an text message and my phone's screen went black but still lit up. I replaced the battery, SIM, SD and tried rebooting but it would still just appear as a black screen with the backlight on, but the keys are not lit up. Occasionally, the HTC splash screen would appear after taking the battery out and restarting, but then would again, go to the black screen. I can't go into Boot Loader either (i think i had my phone set to fast-boot cause I need to frequently switch my phone off).
Anyone have any ideas as to what I should do?
Cheers in advance

Try the taking out the SD card and then booting with the power/vol dn combo to see if you can get to the bootloader. If successful, may have to reload your firmware (P58IMG) and possibly ROM.

Just fyi fastboot has absolutely nothing to do with how fast your phone turns on lol.

Kevc44485 said:
Just fyi fastboot has absolutely nothing to do with how fast your phone turns on lol.
Click to expand...
Click to collapse
Enable fastboot in settings, power off your phone and then power it back up again (without taking out the battery).
Your phone will boot in a jiffy. This more of a Sleep-Wake than a Power Off & power On, but yes, enabling the fastboot option will boot up the phone faster.

nabbyboii said:
Hi guys,
I have had my Sensation rooted with ARHD for about 4-5 weeks and everything has been smooth till now, when yesterday I was just reading an text message and my phone's screen went black but still lit up. I replaced the battery, SIM, SD and tried rebooting but it would still just appear as a black screen with the backlight on, but the keys are not lit up. Occasionally, the HTC splash screen would appear after taking the battery out and restarting, but then would again, go to the black screen. I can't go into Boot Loader either (i think i had my phone set to fast-boot cause I need to frequently switch my phone off).
Anyone have any ideas as to what I should do?
Cheers in advance
Click to expand...
Click to collapse
There were threads a few weeks ago simiar to this with Sensations randomly dying.
What version of ARHD were you running, kernel, and firmware?

gustav30 said:
What version of ARHD were you running, kernel, and firmware?
Click to expand...
Click to collapse
I'm running ARHD 6.5.5 with 3.32.401.5 (can't remember anything after 5) and selected the Sebastian kernel when I installed the ROM ...

Kevc44485 said:
Just fyi fastboot has absolutely nothing to do with how fast your phone turns on lol.
Click to expand...
Click to collapse
He means the feature that just suspends your phone instead of powering off. Ironically, both methods don't fully turn the phone off. Coincidentally, it's also called Fast Boot. You're thinking of that set of bootloader tools.
As per OPs issue, I have no idea. It sounds hardware related, but intermittent. Perhaps crack it open and see if there are any loose ribbon connectors or anything? I'm thinking the ribbon responsible for the screen may be loose. If it's loose but still kind of in place, the pins responsible for power might still be in contact but the ones responsible for sending data to the LCD might not. That could be why it turns on but it's only solid black. Pulling the battery and putting it back in might just coincidentally be "helping" because the angle of the phone is affecting a loose ribbon. Mind you, this is all speculation, and it might not be hardware at all, but that's my best guess.
Also, if you can get it resolved, never use HTC's Fast Boot. It's convenient, but tends to be a major pain when you have legitimate issues.

I have been having similar issues. My phone will be fine and all of a sudden it will turn off. Receiving calls, changing tracks from the lockscreen or playing games. Sometimes just unlocking my phone to use it will cause it to crash. Then getting it to boot again can be a royal pain in the behind. Anywhere from the first bootsplash to first unlock / loading the UI can make it crash and it's usually a pull of the battery SIM and SD to get it to boot.
Age of the ROM is something I have noticed to be a factor, the older the ROM, the more likely it is to do this but wiping cache and Dalvik from 4EXT has no real effect on stopping it from happening for any noticeable length of time.
Also to note, battery life seems to be very jumpy when this happens. I have had 4% battery life for hours, listened to music (at volume) and it's remained at 4%. Hardware LED isn't lit and it's just the OS with it's UI warning me so every so often, with the battery indicator staying at the 4%. It'll change again if the phone crashes again. Either to an accurate reading or to another fixed percentage, but it seems to like the 4%.
Not sure if it's the ROM, or firmware, but my previous ROM's have been using Bricked Kernel. I don't know it that's a deciding factor or not.
Sorry for hijacking the thread, but I too have stability issues and been wanting to say something on here for a while.
I'll post version details later on as I'm just about to get ready for a road trip.
Mark

kgs1992 said:
Enable fastboot in settings, power off your phone and then power it back up again (without taking out the battery).
Your phone will boot in a jiffy. This more of a Sleep-Wake than a Power Off & power On, but yes, enabling the fastboot option will boot up the phone faster.
Click to expand...
Click to collapse
fastboot has nothing to do with how fast your phone boots up. take your battery out and put it back in then start it and see if it starts up fast. you're thinking of quick start from basically hibernate
http://android-dls.com/wiki/index.php?title=Fastboot

Related

[Q] Atrix 2 wont boot up, battery issues?

Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
fire_fist_ace said:
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
Click to expand...
Click to collapse
First off mate, all questions go in our Q&A Section, so just keep that in mind going forward.
Now, your 1st question regarding the touch screen's responsiveness while trying to unlock with password, I've experienced this myself, and while charging. Though I'm not really sure what causes this, to be truthful. I've found though, that sometimes locking and unlocking will get things to cooperate. I doubt it there's anything to cause concern with any hardware (digitizer) since you don't mention this as being an issue outside the unlocking of the device while charging. Mine was sporadic, and I eventually grew tiresome of the pattern unlock, and did away with it altogether. Perhaps someone else could chime in here with a better explanation as to why this happens. (?)
Now, to your more 'serious' issue. Seeing as how you have Clockworkmod Recovery (CWM) installed, you never want to allow your device to power down at the low battery state. You're lucky that you can at least -or at least have- been able to boot after a low power shut down. You may need to FXZ back to stock, if the phone will not boot at all. Can you get into AP Fastboot by pressing and holding AT THE SAME TIME the volume up +volume down + power buttons? If so, you can restore to stock and get yourself out of the soft brick. Here is a great thread with discussions by Fall of Enosis and jimbridgman, I suggest you read through this:
http://forum.xda-developers.com/showthread.php?t=1756048
[Q] Unable to charge while off?
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
fire_fist_ace said:
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
Click to expand...
Click to collapse
I've experienced the screen lag as well.. I think it only comes out when u are charging...usually i just d/c the carger then unlock the device and then plug it again..Something is still lagged...I relly don't know why this happens, but one friend has a Vibrant..and have this problem as well..So we aren't the only one whit this problem.
---------- Post added at 11:47 PM ---------- Previous post was at 11:38 PM ----------
Chichoman said:
I've experienced the screen lag as well.. I think it only comes out when u are charging...usually i just d/c the carger then unlock the device and then plug it again..Something is still lagged...I relly don't know why this happens, but one friend has a Vibrant..and have this problem as well..So we aren't the only one whit this problem.
Click to expand...
Click to collapse
Edit: Also i'm on SCV7 so it's nothing to do with the rom.
For your second Q...Try to clear battery stats on CWM?? Sometimes when u flash a new rom u need to clear those stats...So give it a shot and let us know what happened.
Chichoman said:
<snip>
Edit: Also i'm on SCV7 so it's nothing to do with the rom.
For your second Q...Try to clear battery stats on CWM?? Sometimes when u flash a new rom u need to clear those stats...So give it a shot and let us know what happened.
Click to expand...
Click to collapse
This won't do anything for the OP's inability to boot. That's why I said that likely his best bet is to see if he can boot into AP Fastboot, so that he may be able to FXZ back to stock...
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
Apex_Strider said:
First off mate, all questions go in our Q&A Section, so just keep that in mind going forward.
Now, your 1st question regarding the touch screen's responsiveness while trying to unlock with password, I've experienced this myself, and while charging. Though I'm not really sure what causes this, to be truthful. I've found though, that sometimes locking and unlocking will get things to cooperate. I doubt it there's anything to cause concern with any hardware (digitizer) since you don't mention this as being an issue outside the unlocking of the device while charging. Mine was sporadic, and I eventually grew tiresome of the pattern unlock, and did away with it altogether. Perhaps someone else could chime in here with a better explanation as to why this happens. (?)
Now, to your more 'serious' issue. Seeing as how you have Clockworkmod Recovery (CWM) installed, you never want to allow your device to power down at the low battery state. You're lucky that you can at least -or at least have- been able to boot after a low power shut down. You may need to FXZ back to stock, if the phone will not boot at all. Can you get into AP Fastboot by pressing and holding AT THE SAME TIME the volume up +volume down + power buttons? If so, you can restore to stock and get yourself out of the soft brick. Here is a great thread with discussions by Fall of Enosis and jimbridgman, I suggest you read through this:
http://forum.xda-developers.com/showthread.php?t=1756048
[Q] Unable to charge while off?
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Cheers for the heads up, its not exactly a question, but I've seen questions on this board before so i thought that was ok.
Thing is, its not that it wont boot, it boots after i charge it for a while, but it states that the charger is not connected each time it boots, then shuts down.
Why should we not allow it to go into a low battery state when on CWM? I also set CWM recovery to start at each boot, and i have backups of just before and after i flashed the phone. Cant i just restore a previous backup rather than flash to stock?
And with the battery reset, doesnt clear any user data yeah? I have alot of stuff i would hate to lose
fire_fist_ace said:
Cheers for the heads up, its not exactly a question, but I've seen questions on this board before so i thought that was ok.
Thing is, its not that it wont boot, it boots after i charge it for a while, but it states that the charger is not connected each time it boots, then shuts down.
Why should we not allow it to go into a low battery state when on CWM? I also set CWM recovery to start at each boot, and i have backups of just before and after i flashed the phone. Cant i just restore a previous backup rather than flash to stock?
And with the battery reset, doesnt clear any user data yeah? I have alot of stuff i would hate to lose
Click to expand...
Click to collapse
Okay, I thought from the thread title that at some point, the phone wouldn't boot after a low power shut down. If the phone is saying that it isn't recognizing the battery while charging, you might have some luck trying the methods I overview in THIS POST. The battery will NOT charge while in CWM Recovery, nor will it charge while in AP Fastboot. This is why it is imperative that you not allow the phone to get to such a low power stage, especially when attempting a flash. You can certainly restore via CWM either of the backups that you have, and see if the problem clears up. And with a battery stats reset, nothing is wiped except the battery statistics. All of your user data, applications, settings, etc. will remain in tact. Hope this helps...
Apex_Strider said:
Okay, I thought from the thread title that at some point, the phone wouldn't boot after a low power shut down. If the phone is saying that it isn't recognizing the battery while charging, you might have some luck trying the methods I overview in THIS POST. The battery will NOT charge while in CWM Recovery, nor will it charge while in AP Fastboot. This is why it is imperative that you not allow the phone to get to such a low power stage, especially when attempting a flash. You can certainly restore via CWM either of the backups that you have, and see if the problem clears up. And with a battery stats reset, nothing is wiped except the battery statistics. All of your user data, applications, settings, etc. will remain in tact. Hope this helps...
Click to expand...
Click to collapse
The battery reset actually worked! I had to charge it for quite a while on the usb charger since it wouldnt charge on the mains charger. Once it was on i made a backup then cleared the battery stats, and now it detects the mains charger.
Cheers for your help guys i still dont get why it wouldnt charge on the mains charger when the battery was low, even though before it would charge before when the battery wasnt...

[Q] Bricked phone (in a weird way)

So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.
stealth.kid said:
So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.
Click to expand...
Click to collapse
It reminds me Desire S problem - fried emmc chip... If your phone has no valid warranty, I'm suggesting to see phone's internals and inspect emmc chip.
The phone still has warranty, I will try to have it repaired/replaced. The only thing I'm concerned about is the fact that it was S-OFF and running a custom ROM... And I don't have the knowledge or equipment to try to take it apart and fix it myself
If you have warranty just use it they won't be able to ckeck if phone was unlocked or not since it can't boot up.

[Q] sensation vibrates and black screen bootloop

Hey I have a sensation 4g. All has been well until today. I was at work and got an email. Went to check it but the screen wouldnt turn on. This has happend several times since using Viper rom, which is why I switched to energy. I pulled the battery and went to turn it back on.
Since than all I get out of it is a brief lighting of the screen followed by a boot vibration. After that the screen stays off and it "boot vibrates" at regular intervals never displaying anything. Attempts to get into the boot loader for recovery are met with the same.
If I plug a charger into it the charge indicater lights for about 15 seconds than turns off. Occasionally I can see a red light in the upper left hand corner.
I have used a htc g2 battery held against the pins as a known good battery so I have eliminated my battery as bad.
It is rooted, was running ICS Energy rom.
adb does not detect the device nor does linux or windows, but thats not too unusual since it technically doesnt turn on.
I am assuming that the thing is totally dead for whatever reason, but on the off chance someone has any ideas Im all ears, I love this phone.
azethoth said:
Hey I have a sensation 4g. All has been well until today. I was at work and got an email. Went to check it but the screen wouldnt turn on. This has happend several times since using Viper rom, which is why I switched to energy. I pulled the battery and went to turn it back on.
Since than all I get out of it is a brief lighting of the screen followed by a boot vibration. After that the screen stays off and it "boot vibrates" at regular intervals never displaying anything. Attempts to get into the boot loader for recovery are met with the same.
If I plug a charger into it the charge indicater lights for about 15 seconds than turns off. Occasionally I can see a red light in the upper left hand corner.
I have used a htc g2 battery held against the pins as a known good battery so I have eliminated my battery as bad.
It is rooted, was running ICS Energy rom.
adb does not detect the device nor does linux or windows, but thats not too unusual since it technically doesnt turn on.
I am assuming that the thing is totally dead for whatever reason, but on the off chance someone has any ideas Im all ears, I love this phone.
Click to expand...
Click to collapse
Maybe it was a hardware failure. how many times does it vibrate? there is something called qualcomm diagnostic mode that htc phones sometimes get happens when the hboot gets corrputed/damaged. depending how many vibrations you get some people have had luck attempting to blind boot a pc58img.zip to the bootloader to flash a ruu. but since your phone isnt being recognised by the pc as anything i wouldnt hold out to much hope how many vibes do you get?
You might be in diag mode, as heavy_metal_man said.
Does QHSUSB_DLOAD come up in Device Manager?
neither windows nor linux recognize the device at all.
as far as the vibration. I call it a boot vibration, as it is the same intensity and duration of the normal boot vibrate you get on power up.
Its a single vibration of about one second. After that every about 30 seconds it vibrates again.
I did try to shove a P58IMG.zip onto the sd card but I figured that was a long shot anyway and of course nothing happened.
Just out of curiosity have you tired another battery? I know you did check it but one time I was charging my device with a perfectly good battery, it wasn't low, and my device made a weird noise like a high pitch noise then went black. I had no charging light, no life what so ever. I thought I was completely screwed thinking something fried my device. Out of desperation I put another fully charged battery in. Then my device sprang back to life and I haven't had any trouble since. I never figured out what happened. But I was so Glad it worked. So just for curiosity do try another battery. It can't hurt to try it. In my weird case it worked. Like I said earlier the weird part was my battery was good! Not dead! So it won't hurt to just try. You have nothing to lose. I do hope it helps. Good luck and best wishes!
Sent from my HTC Sensation using xda premium
sadly I have no other battery, I have a g2 battery that I can hold in as a substitute but still the same result. I will try to throw that img back on the sd card and see if I can blind install it.
Appreciate the help guys.

Help - One X will not stay on

Right guys,
I was just updating some apps on my One X, left it to its business and came back and it had turned off, so turned it on and it seems to load to the lock screen and then the screen goes blank and the phone turns off.
I have had it on charge (mains), tried the recovery, that doesn't help and I have tried a factory reset (when you hold the power and volume button) that doesn't work either.
Every time, just about gets to the lock screen freezes, goes blank and turns off.
It is totally stock software and hardware.
Locked to EE (Orange) network in the UK
Any help please?
Mike
More information please. Is the phone stock or modified?
Sent from my Evita.
timmaaa said:
More information please. Is the phone stock or modified?
Sent from my Evita.
Click to expand...
Click to collapse
Sorry, it is totally stock, not rooted or anything like that.
Just edited my first post too, sorry I was in a rush when I wrote it.
More info:
I have noticed that sometimes the little LED flashes red then green then pauses and repeats. I have seen this is an overheating problem?! The phone feels cool/warm to the touch, I know when playing the odd game the back of the phone gets really warm and it's no where near as warm as it can get.
More info:
Had it on charge overnight from the mains and it doesn't appear to have taken any charge, when it loads the lock screen it will show the battery level and when I press the power & volume buttons it tell me the battery level is too low.
Thanks again!
Mike
I've been having the same kinds of problems for months now.
I only use my OneXL for app testing fortunately, if I needed it as a normal phone I'd have given up and bought something new.
It often reboots after an hour or 2, even if it's doing "nothing", not even running any app after a restart.
Maybe it's overheating or something, but it seems more random to me. I was going to say that smacking it a bit doesn't cause any problem, but I just tried it now and it died. So maybe a PCB is cracked or there's some cold solder joints.
And yeah, the phone acts like the battery is dead. Again tonight I tried to boot it several times before it started up OK. It can end up dead but "powered" so I have to remove USB plug and hold power down 10-20 seconds to boot again.
I dunno, to me the phone is just broken, in effect.
I have had this same problem in the past with mine. Try disassembling it and pulling the battery.. then reassemble and see if that works, or could be a faulty power button
Sent from my HTC One X using xda app-developers app
Hmm.
I just updated with the latest RUU for the HBoot or whatever, and it looks like the reboots may have stopped !
Crosses fingers for luck...

Moto G 4G freezing randomly, requires reset to power on (long/detailed post inside)

so yeah, my phone just freezes randomly at different time.
I believe it's freezing and then it just drains the power.
When I turn it back on, there's a gap in the battery life. Unfortunately, this time it must have happened really early and the battery drained to 0 and now it doesn't even power on.
This includes power + vol down with and without charger on for at least 1 or 2 mins, nothing happens. The notification light turns on when you plug it in.
I believe I do need to open it and unplug the battery then plug in the power, but I can't test it out because I don't have T5 torx around so it may take a while.
Anyways, I am not definitive on the freezing, it's just most likely scenario since phone becomes unresponsive randomly.
When it happens, plugging in power, power button, plug to usb/data does nothing. Phoning the cellphone gets user not in service. And powering back on I see the battery is drained.
This started happening like around a month and a half ago, I was using SaberRom. The rom was very stable until it this started happening.
I thought there was a bug in the Rom or something, so I made the jump to CM12. However it still continues to happen.
My only guess why this may be happening, software wise now, through the process of elimination is maybe Xposed might be doing something.
If it's not, then it could be a hardware problem, which doesnt make much sense to me since the phone is stable when I actually use it.
The freezing problem never happens while I use it, it usually happens over night or not in use in my pocket.
I started using logcat to try to keep a record, but I only have 1 record, plus 1 the most current one which I dont know if it even recorded properly since I can't turn phone on.
I personally would do a full wipe and flash stock ROM and kernel without Xposed. Until you do that you really are just shooting blind. Find out if the problem goes away and go from there.
n0ts0smart said:
I personally would do a full wipe and flash stock ROM and kernel without Xposed. Until you do that you really are just shooting blind. Find out if the problem goes away and go from there.
Click to expand...
Click to collapse
+100000²
outlook not so good
so i tried doing this
where you plug in the phone directly to power without the battery
for me, only the notification light turns on, the screen doesnt turn on

Categories

Resources