Database Users

Evo refuses to turn on AT ALL

This has happened once before, but just for a small amount of time to to the heat (I believe). The phone has been off for over and hour and refuses to turn on whether I hold down the volume button, don't hold down the volume button, or push the battery in at the exact time as I'm doing the other one or two. The splash screen flashed for half a second and immediately went back off when I plugged my evo charger, the usb part, into my portable ipod charger, so I believe this means there is still help available! Last time this happened, which was months ago, it seemed as if it just needed to cool down a bit, and my reading on the internet confirmed that the phones shut off when their batteries reach too high of temperatures. So what I did was wrap the phone and the battery, separately, in a large wash cloth and let them sit it the fridge for a little while. No luck, I'm running out of ideas (and I realize a ziplock bag may have been better but who cares). A few days ago I installed cm7gginggerbread7 (wimax) over cm7gingerbread2, but have not had any issues up until now and everything has run perfectly as well as smoothly. Is there any way I can turn my brick into a phone? Perhaps there's a way to adb something even though the phone wont boot (im a noob). I'm just pissed cuz I finally got every little thing exactly the way I wanted it, and now I'm stuck with a paperweight :/ I thank you for all your help, brave knights

It just suddenly shut off and won't turn back on?
And you weren't messing with anything?
If so, sounds like it's a hardware or battery issue.
Can you try a different battery?

Does the charging light come on when you plug it in? It could be a dead battery, and if the charging port is broke, it wont charge.
Otherwise, it seems like a hardware issue. I would take it to sprint, and they should be able to replace it for you.

sitlet said:
Does the charging light come on when you plug it in? It could be a dead battery, and if the charging port is broke, it wont charge.
Otherwise, it seems like a hardware issue. I would take it to sprint, and they should be able to replace it for you.
Click to expand...
Click to collapse
But it has teh rootz!!!!!!!!!
Smash that mofo with a hammer and call Asurion!!!!!!
jk

matt2053 said:
But it has teh rootz!!!!!!!!!
Smash that mofo with a hammer and call Asurion!!!!!!
jk
Click to expand...
Click to collapse
If they can't get it to power on then it really doesn't matter if it's rooted or not because they won't be able to find out.

Well I was messin with it a couple days ago, flashed gginggerbread6 w/ wimax over gginggerbread2 after wiping cache and dalvik and of course making a nandroid. I was thinking of smashing it but I've gotten everything they way I want it for the thousandth time. I'm also reluctant to do it because this issue has resolved itself in the past, albeit a tad quicker. For christ's sake, it even fixed itself for half a second this time, just enough to show me the splash screen lol. I'm very gentle with my evo and have never had any problems that weren't easily resolved with a little bit of work. I guess I could smash it until it works, and then if it ends up breaking then I win either way, but I'd really like to get my darling fixed. I know it's nothing compared to the cyanogenmod team, but I've flashed and flashed (almost always to cyanogenmod, what can I say it's perfect) and I have FINALLY got everything set up the way I wanted it, which includes manually going through and changing all the icons to custom pngs lol.
I guess I just don't understand why this would happen all of a sudden like this, I've onlu had it for three or four months, htc can't make that shotty of work can they? The other thing is I have a battery widget so as to make sure my battery does not get to hot, as well as having a setting in setcpu which stops overheating if it should ever occur. I really have a feeling it's something which can be fixed just because it has been magically fixed in the past and it was "fixed" for half a second today. Is there any way to adb into recovery even though the screen is black? Any suggestions help, I have important calls coming in as well as rather important calls to (hopefully) future employers. Of course I also don't want people to think that I am ignoring them, which isn't quite as bad but I still try to be as rude as possible :/
So...any ideas guys Don't wanna sound like I'm fishing for compliments, but you all are by far the best in the field. Keep up the good work (on my phone haha) Thanks so much for the advice you're going to give me on how to fix this up so I don't miss all my friends calls and texts until I get pissed off at. Later trooper
EDIT: Sry got block of text. tl/dr fix my evo that wont turn on asap thx

Raillery said:
Well I was messin with it a couple days ago, flashed gginggerbread6 w/ wimax over gginggerbread2 after wiping cache and dalvik and of course making a nandroid. I was thinking of smashing it but I've gotten everything they way I want it for the thousandth time. I'm also reluctant to do it because this issue has resolved itself in the past, albeit a tad quicker. For christ's sake, it even fixed itself for half a second this time, just enough to show me the splash screen lol. I'm very gentle with my evo and have never had any problems that weren't easily resolved with a little bit of work. I guess I could smash it until it works, and then if it ends up breaking then I win either way, but I'd really like to get my darling fixed. I know it's nothing compared to the cyanogenmod team, but I've flashed and flashed (almost always to cyanogenmod, what can I say it's perfect) and I have FINALLY got everything set up the way I wanted it, which includes manually going through and changing all the icons to custom pngs lol.
I guess I just don't understand why this would happen all of a sudden like this, I've onlu had it for three or four months, htc can't make that shotty of work can they? The other thing is I have a battery widget so as to make sure my battery does not get to hot, as well as having a setting in setcpu which stops overheating if it should ever occur. I really have a feeling it's something which can be fixed just because it has been magically fixed in the past and it was "fixed" for half a second today. Is there any way to adb into recovery even though the screen is black? Any suggestions help, I have important calls coming in as well as rather important calls to (hopefully) future employers. Of course I also don't want people to think that I am ignoring them, which isn't quite as bad but I still try to be as rude as possible :/
So...any ideas guys Don't wanna sound like I'm fishing for compliments, but you all are by far the best in the field. Keep up the good work (on my phone haha) Thanks so much for the advice you're going to give me on how to fix this up so I don't miss all my friends calls and texts until I get pissed off at. Later trooper
EDIT: Sry got block of text. tl/dr fix my evo that wont turn on asap thx
Click to expand...
Click to collapse
If this occurred while you were NOT changing anything with the radio partition or recovery partition then it's not a brick issue.
Sounds like you have a hardware issue.
Take it to the store.
If you smash it you will be paying $100 to asurion for a replacement as Sprint changed the TEP again.

Just wondering was your battery completely dead before this happened. I have read some people here and other places have said that if the battery completely dies that it won't charge unless you put it on a actual battery charger made for it. Does the charge light come on when you plug it in? Also, like my friend before me said, take it to Sprint. Ask them if they have a battery you could try. If it doesn't work it will eliminate the battery being the issue. If it won't boot they will replace it. They won't be able to tell if it is rooted because it won't boot. If you were flashing a radio and didn't let it finish or the battery died during the process, you are bricked.

Does the charge light flash when plugged in?
Sent from my PC36100 using Tapatalk

The light doesnt change

clean off the battery contacts

the same exact thing happened to me. i read in another post that the TP2 battery was a suitable replacement, so i checked the VDC and mA and they were exact and also the contacts were in the right place. (looks exactly like the evo batt just black instead of red in retrospect). It was a good call on the TP2 battery. My evos batt died on me tonight while it was charging. no light while plugged into OEM wall charger, no blinking, nothin, I wasnt even using it, never had a problem before. luckly i was just chargin up my old TP2 to give to my girlfriend. popped in that battery and the evo came right up. popped the evo battery in my TP2 and it appears to be charging. curiously the evo appears to be charging the tp2 batt now aswell. so i dont know what happened... one positive thing is that i know i have 2 batteries now. a negative is that my gf cant have my TP2 untill i get this sorted.
anyone have any insight as to what is goin on? or why this happened? if my charging port has gone bad why is the tp2 batt charging in the evo? and if the evo battery went bad why is it charging in the TP2?
i am using the stock sprint evo rom. not scared to root, just havent yet.

vespix said:
the same exact thing happened to me. i read in another post that the TP2 battery was a suitable replacement, so i checked the VDC and mA and they were exact and also the contacts were in the right place. (looks exactly like the evo batt just black instead of red in retrospect). It was a good call on the TP2 battery. My evos batt died on me tonight while it was charging. no light while plugged into OEM wall charger, no blinking, nothin, I wasnt even using it, never had a problem before. luckly i was just chargin up my old TP2 to give to my girlfriend. popped in that battery and the evo came right up. popped the evo battery in my TP2 and it appears to be charging. curiously the evo appears to be charging the tp2 batt now aswell. so i dont know what happened... one positive thing is that i know i have 2 batteries now. a negative is that my gf cant have my TP2 untill i get this sorted.
anyone have any insight as to what is goin on? or why this happened? if my charging port has gone bad why is the tp2 batt charging in the evo? and if the evo battery went bad why is it charging in the TP2?
i am using the stock sprint evo rom. not scared to root, just havent yet.
Click to expand...
Click to collapse
Take the original battery to sprint. Tell them the story and get a replacement, ask for some free accessory since you've helped them isolate a reliability issue.
LOL

There are two known issues with the Evo to be aware of. The first is the charging bug. If the Evo shuts off due to low battery level there is the possibility that the charging circuit fails to recognize the dead battery as even being there and will not charge. The workaround is to charge the dead battery in another compatible phone or use an external battery charger. This is supposed to be fixed in the next update but we'll see.
The second is the thermal sensor bug. The thermal cut off starts to trigger at lower and lower temps til even freezing the phone won't work. I thought the local service center was joking til I actually saw it reproduced. This is a hardware issue and the only fix is a replacement phone.
The first issue is intermittent but knowledgeable service centers are aware of this and will either charge the dead battery or swap out with a charged one.
The second issue is reproducible but can take some time to do so depending on how far off the sensor is. Again, knowledgeable service centers are aware of this and will want to reproduce it before ordering a replacement.

Not sure what technical thong is happening, but I do know I panicked when it happened to me, bit it turns out if you try to charge EVO from a USB port while its in the recovery mode it will eventually drain and **** off. I forgot I was on recovery mode and came back to what you described. After doing the swap with my GF's EVO and realizing my battery was fine, I remembered how I had left the phone in the first place and Googled it to confirm that will cause the dead EVO scare.
Sent from a corrective lens wearing eskimo translating Turkish smoke signals viewed over a streaming webcam at 640x480 resolution via a U.S. Robotics 14.4 Hayes compatible modem.

This has happened to me twice, but since I was on the extended battery from sprint, I would just pop my stock battery in and it powered up fine. Each time I just brought my battery in to sprint and they replaced it. Also, when it happened to me the charging light wasn't turning on or anything.
Sent from my PC36100 using XDA Premium App

OK friends, same thing happening here to me today.
Here's my story: Last night, working fine, running stock turbo rom and netarchy cfs-havs-sbc-4.3.4 kernel for about a month, working great.
Used Kernel manager and flashed to cfs-suv-nohavs-nosbc and it was working great. Figured I didnt need the extra batter life/damage risk anymore. Went to sleep, phone on my bed.
Wake up today, phone is fully unresponsive. Take the battery out, put it back in, unresponsive. nothing whatsoever when holding down power, volume, etc.
When I plug it in, the orange battery led comes on and off.
:[

cjh6386 said:
OK friends, same thing happening here to me today.
Here's my story: Last night, working fine, running stock turbo rom and netarchy cfs-havs-sbc-4.3.4 kernel for about a month, working great.
Used Kernel manager and flashed to cfs-suv-nohavs-nosbc and it was working great. Figured I didnt need the extra batter life/damage risk anymore. Went to sleep, phone on my bed.
Wake up today, phone is fully unresponsive. Take the battery out, put it back in, unresponsive. nothing whatsoever when holding down power, volume, etc.
When I plug it in, the orange battery led comes on and off.
:[
Click to expand...
Click to collapse
Blinking charge light means that the battery v has dropped below the required v to turn on the phone. I see 4-5 Evo's a day like this as well as the charge bug.

I actually got it booting again somehow. Now, it consistently turns on, will boot to the bootloader, but recovery doesnt work and it wont boot into the phone. It does search for pc36 image though... i might try that.

I just sit here and shake my head on a daily basis when I see people talk about problems and inevitably, and I'm not saying this is applicable in this case, but they say in their post they were using ROM or Kernel Manager.....

[Q] Red Light of Death - RMA or Repairable?

I very recently had my Nexus give me the blinking red light of death. It started when I couldn't flash the latest Franco Kernel due to an "Unmatching MD5" error. So, I thought why not update Cyanogenmod 10 to the latest nightly? Lo and behold, it skips the prompt asking if I want to install it and the phone shuts off. The furthest I've gotten right now is getting it to the standard recovery, and that was only for a minute (this was after I hooked the phone up and used the Nexus toolkit to reflash the stock recovory). Now, when I try to flash the stock ROM, I either get "device not found" or that some random error has happened. I'm stuck between either using software methods to fix this, or sending it in for an RMA sooner than I thought I would (it has tons of scratches and dents).
Just as a note, I know about the battery trick, and I'm not up for doing that. I'd sooner RMA it, as I believe after relocking the bootloader it would still be under warranty since it seems to technically have no ROM installed right now.

Will it boot into fastboot?

It will. It won't go beyond that though. I did, at one point, get the default recovery screen where the dead android with a red triangle in it's chest popped up, but I haven't been able to get past that. I have a replacement coming in, but it'd be great to know how to fix this in case the replacement faces the same issue.
Sorry for the late reply, didn't have it set to email me or even had it subscribed.

CodemasterRob said:
It will. It won't go beyond that though. I did, at one point, get the default recovery screen where the dead android with a red triangle in it's chest popped up, but I haven't been able to get past that. I have a replacement coming in, but it'd be great to know how to fix this in case the replacement faces the same issue.
Sorry for the late reply, didn't have it set to email me or even had it subscribed.
Click to expand...
Click to collapse
If you can get into Fastboot mode, have you tried flashing the stock images from Google?

Yes. I've, as far as fastboot has told me, successfully flashed the stock kernel, ROM, and recovery, and the bootloader is still in tact so I can lock and unlock that at will. The phone is completely dead now though. Must have been a battery problem, because it won't even show the light now.

CodemasterRob said:
Yes. I've, as far as fastboot has told me, successfully flashed the stock kernel, ROM, and recovery, and the bootloader is still in tact so I can lock and unlock that at will. The phone is completely dead now though. Must have been a battery problem, because it won't even show the light now.
Click to expand...
Click to collapse
You need to take it apart and pull the battery connection off. Its the same thing as a battery pull. I had to do it this morning cause I had the red light of death. Booted back up no problem. There's a video on YouTube red light of death fix.
Just saw you know about it. Mine was bought used so I couldn't RMA. But it works easy enough. And I'm a amateur who isn't good at working on small tech stuff and it was easy enough for me.
Sent from my Nexus 4 using xda app-developers app

Mephisto Zap said:
You need to take it apart and pull the battery connection off. Its the same thing as a battery pull. I had to do it this morning cause I had the red light of death. Booted back up no problem. There's a video on YouTube red light of death fix.
Just saw you know about it. Mine was bought used so I couldn't RMA. But it works easy enough. And I'm a amateur who isn't good at working on small tech stuff and it was easy enough for me.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Heh, I was about to direct you to the OP
That *might* fix it, but I believe a full battery replacement is in order. The phone was reaching an excess of 150 degrees before it shut down, it literally burnt my leg and gave me a red spot. All is well though; I managed to pry the SIM card out, wipe all of the partitions, and get it back to factory state before it completely turned over in it's grave. Learned my lesson the first time around; got myself a case to prevent all of those nasty scratches and I'll be ordering XO skins soon.

touch screen problems?

I have a small line on my screen that is unresponsive. It goes straight across the top of the screen exactly where the install button is in the play store (about 1" from top of screen at roughly 1/4" thick). Its in a pretty awkward spot and causes a lot of problems. For some reason it has also disabled the tap to wake feature of my phone.
I installed the "Touch Test" app which shows that my entire touch screen is working. However it shows the phone recognizing 2 pointers (touches) being active whenever I touch that area of my screen. I've been having this problem for 2 or 3 months now and all of a sudden today on my lunch break it went away. I was able to tap to wake the screen (worked perfectly the 20 or so times I attempted it), I was also able to hit the install button in the play store and life was great... Or so I thought. A few hours later on my next break my phone went back to annoying piece of junk that I completely dislike using.
Now I dont know exactly when this started happening. I did notice it sometime soon after the 4.4 update, and flashing a custom rom/kernel has made no improvement. Anyone got any ideas? I loved this phone before this started, and my phone is so frustrating now that I completely disrespect the thing and have scratched the crap out of the screen. I'm really hoping this can be fixed so I can go on with enjoying whatever life I have left with the g2, if not I'll probably just abuse it until it breaks then switch over to a water proof z2 or something along those lines... Phone was very well taken care of before the problem started, wasnt dropped or exposed to water (other then using outside in the rain for a few min at a time)

mikeinaus said:
I have a small line on my screen that is unresponsive. It goes straight across the top of the screen exactly where the install button is in the play store (about 1" from top of screen at roughly 1/4" thick). Its in a pretty awkward spot and causes a lot of problems. For some reason it has also disabled the tap to wake feature of my phone.
I installed the "Touch Test" app which shows that my entire touch screen is working. However it shows the phone recognizing 2 pointers (touches) being active whenever I touch that area of my screen. I've been having this problem for 2 or 3 months now and all of a sudden today on my lunch break it went away. I was able to tap to wake the screen (worked perfectly the 20 or so times I attempted it), I was also able to hit the install button in the play store and life was great... Or so I thought. A few hours later on my next break my phone went back to annoying piece of junk that I completely dislike using.
Now I dont know exactly when this started happening. I did notice it sometime soon after the 4.4 update, and flashing a custom rom/kernel has made no improvement. Anyone got any ideas? I loved this phone before this started, and my phone is so frustrating now that I completely disrespect the thing and have scratched the crap out of the screen. I'm really hoping this can be fixed so I can go on with enjoying whatever life I have left with the g2, if not I'll probably just abuse it until it breaks then switch over to a water proof z2 or something along those lines... Phone was very well taken care of before the problem started, wasnt dropped or exposed to water (other then using outside in the rain for a few min at a time)
Click to expand...
Click to collapse
I have this problem too, any fixes?

Well I am in shock as to how we all have the same exact problem.
I first thought it was hardware failure on the screen itself and was pretty bummed. But now I see people have the exact same unresponsive touch screen in the exact same spot as mine? What ROM/Kernel are are you guys running? I am running what is in my sig and had not noticed it before until a couple of days ago. Coupled with the unresponsiveness, my Knock on does not work and the phone becomes mildly warm faster than usual. I think it might be a kernel software issue.

Ugh... I was hoping this wouldn't turn in to this big of a problem. I've got the same thing here, VS980 after flashing a Cloudy ROM.
I took over a thread here recently http://forum.xda-developers.com/showthread.php?p=52858791 , but I'll post here again anyways. I wonder if it's the same spot with you guys too. It's right where the install button is on the Play Store, right? For a few hours after it started it went back to normal, then messed up again permanently.
TOT'ing back to 12B didn't help, so I got a replacement device from Verizon. I've yet to send back my old one because I'm worried about the unrooted flag in the bootloader and settings.
I don't have enough posts yet to be able to do this, but can someone alert a dev about this? Particularly in the thread of whatever ROM it was that you last used? A lot of people in the last thread said it came from Cloudy, and I figured it might make sense as Knock Code was supposed to be a feature on there even though the VS980 source wasn't out. Then again I probably have no idea what I'm talking about, but I'd love to hear from someone who does.

I dont think my blacked out area is quite as thick as yours but yes its in the exact same place. To confuse things even more my phone just started working properly again (for how long is another story). Its very odd that It hasnt worked once in 2 months or so and now twice in 2 days its started working.
As a side note I'm pretty sure I started having this problem immediately or very shortly after the OTA kitkat update. I'm now running cloudypro II 2.0 with 3.4.0 kernel, which as i said before didnt fix the problem in the 1 month ive been using this rom.
I originally thought it may have been a software issue, but for it to randomly start/stop working all of a sudden after so long of no function (with no software being added or changed) I'm thinking its more likely a hardware problem? When I fly home on Monday I'm going to try opening up the phone and cleaning the contacts to the from the touchscreen to the mainboard.
If it is software related it may have something to do with air plane mode. I get almost no signal where I'm working at the moment and the constant searching for signal kills my battery pretty fast so I've started using air plane mode the past few days. Thats the only thing out of the ordinary that i've done software wise.

Having the same issue!!
Has anyone found a solution ?
Please reply.

hashir1296 said:
Has anyone found a solution ?
Please reply.
Click to expand...
Click to collapse
Yes, we've sent it to LG for repairs and they were able to fix it easily.

Sfkn, was your phone rooted when you sent it to them? I'm having the same issue, and it either started happening today, or I just noticed it today, but it's bugging the crap out of me. I'm running stock kk, rooted with twrp and on the cloudyfa kernel.
Sent from my LG-D801 using XDA Free mobile app

Had the same today but at the middle of the screen, I pressed on the corners and around the screen pretty hard and it is back to normal(for now).
Hope it wont come back.
You can unroot the device by flashing original rom with LG flash tool.

THISISINSANE said:
Sfkn, was your phone rooted when you sent it to them? I'm having the same issue, and it either started happening today, or I just noticed it today, but it's bugging the crap out of me. I'm running stock kk, rooted with twrp and on the cloudyfa kernel.
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
No, I am completely stock.

Yeah I used the LG mobile support tool and that unrooted it. Now I'm just waiting for my replacement phone to arrive.
Sent from my LG-D801 using XDA Free mobile app

THISISINSANE said:
Yeah I used the LG mobile support tool and that unrooted it. Now I'm just waiting for my replacement phone to arrive.
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
You claimed insurance rather than with LG repair?

Sfkn2 said:
You claimed insurance rather than with LG repair?
Click to expand...
Click to collapse
I went with T-Mobile's warranty replacement. I already sold my backup phone so I couldn't send the phone to LG for repairs and still have a phone
Sent from my LG-D801 using XDA Free mobile app

[HELP] Battery problem

Recently I've rooted my phone, one week later I was experiencing battery problems, drop 30% to 3%, unexpected shutdowns, camera and flash almost not working.
The flash doesn't work, only turns on one led and the. Shuts down, sometimes both but then shutdown instantly, he camera (when bat is lower than 30%) looks like a CRT TV
I've flashed the stock rom xt1644, and still having the same problems.
Any suggestion?
Edit* it wasn't hardware problems, battery was uncalibrated, I followed these steps
https://www.androidpit.com/how-to-calibrate-the-battery-on-your-android-device
Edit* wasn't battery uncalibrated, was battery pin problem (contact problem maybe), I've removed the back housing, and disconnected the battery, now everything is working fine

panchoarcia said:
Recently I've rooted my phone, one week later I was experiencing battery problems, drop 30% to 3%, unexpected shutdowns, camera and flash almost not working.
The flash doesn't work, only turns on one led and the. Shuts down, sometimes both but then shutdown instantly, he camera (when bat is lower than 30%) looks like a CRT TV
I've flashed the stock rom xt1644, and still having the same problems.
Any suggestion?
Click to expand...
Click to collapse
Sounds like a problem with the board. Any moisture?

strongst said:
Sounds like a problem with the board. Any moisture?
Click to expand...
Click to collapse
Currently I have a cover and a tempered glass, there's no moisture even on the backside

panchoarcia said:
Currently I have a cover and a tempered glass, there's no moisture even on the backside
Click to expand...
Click to collapse
Ok, but only rooting the phone won't cause such behavior. I know iPhones, Nokia, Blackberry etc. with similar problems and after opening that, the moisture indicators were red or metal/parts was corroded,that's why I'm asking. Even dropping a phone can bring problems weeks later (iPhone 4 sound chip, wasn't soldered good). And as it seems you're the only one around here with this problem, I guess it's a hardware failure. (sorry for the story )
For understanding: you only root the phone to, nothing else(flashing something)

strongst said:
Sounds like a problem with the board. Any moisture?
Click to expand...
Click to collapse
strongst said:
Ok, but only rooting the phone won't cause such behavior. I know iPhones, Nokia, Blackberry etc. with similar problems and after opening that, the moisture indicators were red or metal/parts was corroded,that's why I'm asking. Even dropping a phone can bring problems weeks later (iPhone 4 sound chip, wasn't soldered good). And as it seems you're the only one around here with this problem, I guess it's a hardware failure. (sorry for the story )
For understanding: you only root the phone to, nothing else(flashing something)
Click to expand...
Click to collapse
I haven't dropped my phone, I'm very careful, I know root can't damage hardware but, it's funny cause since I've rooted, problems came

panchoarcia said:
I haven't dropped my phone, I'm very careful, I know root can't damage hardware but, it's funny cause since I've rooted, problems came
Click to expand...
Click to collapse
Was your phone new and the package sealed?

Is it only when the battery runs low? Mine did the thing with dropping from like %80 down to 30 then shut down and would turn back on at be like 44. If I used camera it shut the off off and sometimes calls too. I was told to try calibrations and resets and didn't help. Turns out I had to get the battery replaced by moto.

I experienced the exact same issue
panchoarcia said:
Recently I've rooted my phone, one week later I was experiencing battery problems, drop 30% to 3%, unexpected shutdowns, camera and flash almost not working.
The flash doesn't work, only turns on one led and the. Shuts down, sometimes both but then shutdown instantly, he camera (when bat is lower than 30%) looks like a CRT TV
I've flashed the stock rom xt1644, and still having the same problems.
Any suggestion?
Click to expand...
Click to collapse
Had this same exact problem with this same exact model of the G4 plus on the stock rom (unrooted). I sent it in for a warranty repair and it came back to me with the same issue. I ended up doing a warranty exchange where you put down a deposit and they send you a new phone and release the deposit back to you when they receive the defective device back. I don't think you would be able to swap the device if you unlocked the bootloader and rooted the device since that voids the warranty but I can confirm that this is most definitely a defective hardware issue you are experiencing.

strongst said:
Was your phone new and the package sealed?
Click to expand...
Click to collapse
I bough it used from ebay, came flawless with no problems.
Everything happened after rooting my phone, plus I'm not from NA, I live in central America, Nicaragua.

panchoarcia said:
I bough it used from ebay, came flawless with no problems.
Everything happened after rooting my phone, plus I'm not from NA, I live in central America, Nicaragua.
Click to expand...
Click to collapse
Ok... So this problem can also be present before you do flashing. Imagine the guy did what I think(dropped it, moisture, bad hardware cause lenovo manufacture it on a Monday), he recognized it, then sell it maybe with bootloader locking and you're happy who bought it now. That's possible!

Keasbeychay said:
Had this same exact problem with this same exact model of the G4 plus on the stock rom (unrooted). I sent it in for a warranty repair and it came back to me with the same issue. I ended up doing a warranty exchange where you put down a deposit and they send you a new phone and release the deposit back to you when they receive the defective device back. I don't think you would be able to swap the device if you unlocked the bootloader and rooted the device since that voids the warranty but I can confirm that this is most definitely a defective hardware issue you are experiencing.
Click to expand...
Click to collapse
Hopefully (Maybe) next Android update fixes the problem, if not, this is the last moto g fam I will own

panchoarcia said:
Recently I've rooted my phone, one week later I was experiencing battery problems, drop 30% to 3%, unexpected shutdowns, camera and flash almost not working.
The flash doesn't work, only turns on one led and the. Shuts down, sometimes both but then shutdown instantly, he camera (when bat is lower than 30%) looks like a CRT TV
I've flashed the stock rom xt1644, and still having the same problems.
Any suggestion?
Click to expand...
Click to collapse
I'm just curious, did you root using SuperSU? If so, which version did you use? I ask you this because you keep saying that all these issues propped up AFTER you rooted your device.
Battery charge jumps can be caused because of battery calibration issues, which you can recalibrate using a plethora of apps available (by using root access), or the old fashioned way.
I didn't respond till now because of your camera issues — CRT stumped me.

panchoarcia said:
Hopefully (Maybe) next Android update fixes the problem, if not, this is the last moto g fam I will own
Click to expand...
Click to collapse
Look at iPhone 6 or Note 7 complex hardware, short research and development cycles, cheap parts, human fail. It can happen everywhere today.

zeomal said:
I'm just curious, did you root using SuperSU? If so, which version did you use? I ask you this because you keep saying that all these issues propped up AFTER you rooted your device.
Battery charge jumps can be caused because of battery calibration issues, which you can recalibrate using a plethora of apps available (by using root access), or the old fashioned way.
I didn't respond till now because of your camera issues — CRT stumped me.
Click to expand...
Click to collapse
I've used this tutorial
http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772

Which phone you guys recommend? Have about 230$

panchoarcia said:
Which phone you guys recommend? Have about 230$
Click to expand...
Click to collapse
Search or ask here please: http://forum.xda-developers.com/showthread.php?t=1620179
Or here:
http://forum.xda-developers.com/showthread.php?t=1846277
Otherwise btt please.

Edit* battery was uncalibrated, wasn't hardware problems

Edit* battery was uncalibrated, wasn't hardware problems.
Followed these steps (no root)
https://www.androidpit.com/how-to-calibrate-the-battery-on-your-android-device

Weird screen flickering

Hello,
This is my first post in this part of XDA.
My wife has an s7 Edge and the screen started flickering. I got out of this state messing with the power buttons etc. Mainly getting the touch screen to unlock the phone and it somehow cleared right up.
Is this a software issue? The screen when it came back is working as usual when I restarted the phone it became crap again.
Im think it maybe the lock screen causing this, I never heard of parts being corrupted.
I've attached a little clip of the screen.
Thoughts?
Thanks in advance!
https://youtu.be/gFSTlcDWGQY

I have never seen this happen before. If I were you I'd flash a new ROM on it in Odin and if it still happens take it to the Verizon store.

k1ska said:
I have never seen this happen before. If I were you I'd flash a new ROM on it in Odin and if it still happens take it to the Verizon store.
Click to expand...
Click to collapse
Forgot to mention, it's not rooted completely stock.
So screen is messed up?

I had this issue. My phone fell from less than a foot off the ground and landed on the corner. Barely any force, but after that the screen would flicker intermittently. For a day or two it would come and go, and then it became permanent. It looked exactly like yours. If your bootloader/recovery/download mode flickers then it is a hardware problem, since the ROM isn't even loaded yet. With Verizon, your phone is fully covered from manufacturing defects for one year, so you should be able to get it replaced. Sorry bro. Wish I had better news.

v1ral said:
Forgot to mention, it's not rooted completely stock.
So screen is messed up?
Click to expand...
Click to collapse
Honestly with a screen issue like that, I really recommend taking it to the Verizon store and asking them about it. It seems like a hardware issue to me but that's just my opinion.

My screen has done some weird things as well fresh out of the box. I would have random areas of the screen pixelize until I smack the back of the phone. Even after root It will randomly do it every other month. My father in law had the same exact issue you're having. He brought it into T-mobile where the screen literally failed and went black in the employees hand. Neither his or my phone has ever been dropped. This is definitely a hardware issue. It's almost like a bad connection between the LCD and main board. Make verizon get you a new one before the screen goes black!

Okay...
Is it okay to say I can get a new screen and do that repair myself?
I wanna make sure that the issue I am having is just "buy a new screen and be good to go".
Thanks for your time!