[Q] Quasi-Pseudo-Semi Bricked? - Motorola Atrix 2

I bought an Atrix 2 a couple of weeks ago. I rooted it and installed cm10, but did not flash any roms (I preferred to have HDMI). Last weekend, my phone ran out of batteries. Plugging it in caused the white LED to flash, but the phone did not wake up after many hours of charging. Since I was away, at a place where I didn't need a phone, I put it aside for a few days.
Upon returning, I plugged my phone into the wall again. A few hours later it woke up, booted, and began to work normally. I charged it fully and used it for a couple of days. A few hours ago it ran out of batteries again, and plugging it in gives the white LED and nothing else. Sometimes when I plug it in the LED will turn off for a moment and the phone will blink, but the screen does not turn on.
Does anyone have any advice? When the phone was on earlier today it worked and charged normally..

Qhastic said:
I bought an Atrix 2 a couple of weeks ago. I rooted it and installed cm10, but did not flash any roms (I preferred to have HDMI). Last weekend, my phone ran out of batteries. Plugging it in caused the white LED to flash, but the phone did not wake up after many hours of charging. Since I was away, at a place where I didn't need a phone, I put it aside for a few days.
Upon returning, I plugged my phone into the wall again. A few hours later it woke up, booted, and began to work normally. I charged it fully and used it for a couple of days. A few hours ago it ran out of batteries again, and plugging it in gives the white LED and nothing else. Sometimes when I plug it in the LED will turn off for a moment and the phone will blink, but the screen does not turn on.
Does anyone have any advice? When the phone was on earlier today it worked and charged normally..
Click to expand...
Click to collapse
First, before you do anything else, research exactly what it is that you are doing. You say you installed cm10 but didn't flash a ROM. It might have been helpful for you to know that cm10 is a ROM. It might have also been helpful to know that HDMI does not work on cm10. As for your battery issue, that has happened to me almost every time my battery has been fully discharged, so I take care to be sure that it doesn't happen. If possible, try charging the battery with an external charger. Then as, I stated in the beginning, research what you are doing BEFORE doing anything else. The best place to start is here:
http://forum.xda-developers.com/announcement.php?a=81
Brought to you by time and relative dimensions in space.

1BadWolf said:
First, before you do anything else, research exactly what it is that you are doing. You say you installed cm10 but didn't flash a ROM. It might have been helpful for you to know that cm10 is a ROM. It might have also been helpful to know that HDMI does not work on cm10. As for your battery issue, that has happened to me almost every time my battery has been fully discharged, so I take care to be sure that it doesn't happen. If possible, try charging the battery with an external charger. Then as, I stated in the beginning, research what you are doing BEFORE doing anything else. The best place to start is here:
http://forum.xda-developers.com/announcement.php?a=81
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
Sorry, meant clockwork mod, not cyanogen. I haven't flashed any ROMs on this phone yet.
Do you think the battery issue arose as a result of rooting/installing clockwork mod?

No no..Many phones these days fail to charge when drained because they use software to detect the charger and then allow current to flow.. This is unlike the older nokia phones or current HTC phones.. what you can do is as suggested above.. use a 9V battery or something that ought to do it.

Related

[Problem] HTC Inspire will not work at all HELP!!

Hey all, I just got through with this hurricane sandy business and now I find my phone not working at all. First off I'd like to say that there is no water damage to this phone and it is NOT rooted. The problem is that it just won't turn on at all, and won't charge when I try to charge the device. The day before I charged the phone and it worked fine. I can provide more details if needed but I need to find a solution to this.
Did it run down on battery completely before it did this? You might need to charge it for a bit before it turns on. Also, see if you can get your hands on a spare battery to see if it's the battery's problem. I would also try removing the battery and putting it back just to make sure it wasn't jostled loose.
bananagranola said:
Did it run down on battery completely before it did this? You might need to charge it for a bit before it turns on. Also, see if you can get your hands on a spare battery to see if it's the battery's problem. I would also try removing the battery and putting it back just to make sure it wasn't jostled loose.
Click to expand...
Click to collapse
Two days ago I completely let the battery drain on its own because it was draining faster than usual and I was using it very minimally due to the lack of phone signal during the power outage. And yesterday I charged it until it was 100% in the morning and at night I charged it again until 100%. Before I went to bed, I turned off my phone and it was 90% and when I turned it on in the morning it was at 77% (which I thought was weird since the phone was not even on). Now the phone will not work at all. I took the battery out and everything. I even tried turning the phone on while trying to charge it (but it would not charge). The only feedback I got was that it vibrated when I tried turning it on this afternoon and after that was nothing. (it would either get stuck at the AT&T bootup part or I would get no display at all)
mpvsuperstar said:
Two days ago I completely let the battery drain on its own because it was draining faster than usual and I was using it very minimally due to the lack of phone signal during the power outage. And yesterday I charged it until it was 100% in the morning and at night I charged it again until 100%. Before I went to bed, I turned off my phone and it was 90% and when I turned it on in the morning it was at 77% (which I thought was weird since the phone was not even on). Now the phone will not work at all. I took the battery out and everything. I even tried turning the phone on while trying to charge it (but it would not charge). The only feedback I got was that it vibrated when I tried turning it on this afternoon and after that was nothing. (it would either get stuck at the AT&T bootup part or I would get no display at all)
Click to expand...
Click to collapse
And nothing happened to it in between at all? That's very odd. The only thing I can think of to try is another battery.
Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
bananagranola said:
And nothing happened to it in between at all? That's very odd. The only thing I can think of to try is another battery.
Click to expand...
Click to collapse
Nothing I can think of. It was fully charged by 9PM the other night and shut off before I went to bed. Next morning the batter is nearly halfway drained for no apparent reason. I think I will get another battery to test.
Also I let the battery sit out of the phone for a few days now and the phone still does not work.
Niavaran
mpvsuperstar said:
Nothing I can think of. It was fully charged by 9PM the other night and shut off before I went to bed. Next morning the batter is nearly halfway drained for no apparent reason. I think I will get another battery to test.
Also I let the battery sit out of the phone for a few days now and the phone still does not work.
Click to expand...
Click to collapse
***
Get a hold of a charged battery, then after 1 hour with no battery in the device, replace the battery remove the SD-Card and the SIM-Card, replace all covers. Reboot your PC and go to firewall tab in the control panel and turn of your firewalls, then reboot your PC, then using USB data cable not a charging cable.. with your device being OFF conect to a USB connection in the back of your PC, if it's a laptop use the one next to the intranet connection. Then wait about 1min. If nothing happwned, hold the volume down button then press and release the power button. if nothing happened, hold the volume up then press and release the power button. If nothing happened do the samething this time by holding both up and down volume buttons. If nothing happened with your device connected to the PC go to MY Computer tab right click on C>Properties then go to tools click on check disc tab check mark both options then restart your PC. Before windows tour OS starts, your PC will go through a self check. let it do its thing. it takes a couple of hours. then after its down check to see if it has seen your device. if not then do procedures above once again. GOOD LUCK.
PHP:
Okay so I finally got it to turn on but in order to charge it, the phone must be turned off for some reason. Also, the touch screen is not working, even after I did a hard reset and erased all my data. I'm not sure if it is a hardware issue or a software issue because the display is working fine.
lobig
mpvsuperstar said:
Okay so I finally got it to turn on but in order to charge it, the phone must be turned off for some reason. Also, the touch screen is not working, even after I did a hard reset and erased all my data. I'm not sure if it is a hardware issue or a software issue because the display is working fine.
Click to expand...
Click to collapse
That same thing happened to a friend of mine. She took it to a technician tho and they sorted it out for her.
Hello every one, this just my first post here, but I have been follow the forum very very close since some days ago thanks to Mustaavalkosta and his new CyanogenMod Rom here:http://forum.xda-developers.com/showthread.php?t=2533007&page=283.
I am having a similar problem with my HTC Inspire, here is my story. I bought it like it a year ago, the first thing I do was to rooted with AAHK and install CyanoyenMod cm-7-20130301-NIGHTLY-ace. Everything works just fine till a couple of months ago. One night I just leave my Inspire and go to sleep, the next morning I wasn't able to turn on, not charging, not turn on. Was not the battery because my brother has another Inspire and I check with his battery. I just leave the phone without the battery and Sim and SD for a day and them come back again, but at next day the same occurs. I try all that time, vol down+power. voldown+volup, every convination but nothing works. So I decide to dissensambly my phone... in the process I broke the ribbon flex cable http://www.ebay.com/itm/OEM-HTC-Desire-HD-Inspire-4G-Camera-Socket-Keypad-Membrane-PBC-Ribbon-Flex-Cable-/320925341841?pt=US_Cell_Phone_Replacement_Parts_Tools&hash=item4ab8a41891 The phone was in parts on my table like a month till I was able to buy and recieve the ribbon (I live in Colombia). Finally the ribbon arrives 3 days ago, so I assembled the phone again and...magic! the phone turns on. My next step was install the Mustaavalkosta Rom that I mentioned before.... but, yesterday, my phone was dead again. So a try all steps again, put out the battery, Sim and Sd... and again try all the combinations of buttons, but nothing works... So I do it again: dissensably again my phone: Only disconnecting the display doesn't works... I have to disconect the display and the ribbon cable, assembled again and just turn on again.... Now I am waiting for the next black out...
I know is a weird behavior, but may be some one can point me in some direction to fix it.. I am not a developer or anything like that, but I like to investigate and solve problems... any help will be wonderful.
Cheers!
PD: I dont have any apps installed, just trying the Rom as it is.
PD: The next time it happens I will try the niavaran advises.

Weird Intermittent Brick; Completely Dead For Long Periods

Hoping someone can help, haven't found any threads about this particular problem.
I bought a used "One X" that was totally stock and seemed to work OK. I rooted it, unlocked the bootloader, and got S-off. I then installed the newest version of Viper XL. Everything worked fine for a while but after a couple days I went to use it and it was totally dead. Battery was half charged a minute before and now nothing. Plugged it into a wall charger and USB and got nothing, not even an orange light. After trying to reboot and hard reboot it for 20 minutes I quit and just plugged it in and left it.
Checked it a few hours later and it was still the same but just for fun I tried a hard reboot again and it launched right away. It worked with no problems for another day and then same thing. When I got it restarted this time I downloaded and ran the latest RUU exe file to eliminate any problems the Roms might be causing, but no, just happened again today and was hours before I got it restarted, this time just by holding the power button.
Any ideas? All help appreciated.
Its somewhat of a known problem, but unfortunately an unknown cause, and I haven't seen any real solutions. Battery drops suddenly, no LED light, but charging for several hours brings it back. Usually happens at night, for some reason. But yours seems much more frequent than other cases I've heard. I've maybe only had this happen twice in the year+ I've had this phone. If this keeps happening every day, or close to that, its obviously a big problem.
redpoint73 said:
Its somewhat of a known problem, but unfortunately an unknown cause, and I haven't seen any real solutions. Battery drops suddenly, no LED light, but charging for several hours brings it back. Usually happens at night, for some reason. But yours seems much more frequent than other cases I've heard. I've maybe only had this happen twice in the year+ I've had this phone. If this keeps happening every day, or close to that, its obviously a big problem.
Click to expand...
Click to collapse
One extra detail I left out. The phone seems to be truly off, as when I get it restarted it doesn't appear the battery was drained at all. It's basically a brick that randomly decides to come back to life. Even if I only leave it plugged in for 15 minutes and then unplug it and try restarting again, it basically comes to life with a full battery.
Strange. Maybe related to the issue I mentioned, maybe something different.
Since you ran the latest RUU, don't think there is much else that can be done. Might be a hardware issue. I would tell the seller and see how they respond. They will probably swear they didn't have the issue. But it doesn't hurt to bring it up.
My problem is little different but almost same.
BrashL said:
Hoping someone can help, haven't found any threads about this particular problem.
I bought a used "One X" that was totally stock and seemed to work OK. I rooted it, unlocked the bootloader, and got S-off. I then installed the newest version of Viper XL. Everything worked fine for a while but after a couple days I went to use it and it was totally dead. Battery was half charged a minute before and now nothing. Plugged it into a wall charger and USB and got nothing, not even an orange light. After trying to reboot and hard reboot it for 20 minutes I quit and just plugged it in and left it.
Checked it a few hours later and it was still the same but just for fun I tried a hard reboot again and it launched right away. It worked with no problems for another day and then same thing. When I got it restarted this time I downloaded and ran the latest RUU exe file to eliminate any problems the Roms might be causing, but no, just happened again today and was hours before I got it restarted, this time just by holding the power button.
Any ideas? All help appreciated.
Click to expand...
Click to collapse
redpoint73 said:
Its somewhat of a known problem, but unfortunately an unknown cause, and I haven't seen any real solutions. Battery drops suddenly, no LED light, but charging for several hours brings it back. Usually happens at night, for some reason. But yours seems much more frequent than other cases I've heard. I've maybe only had this happen twice in the year+ I've had this phone. If this keeps happening every day, or close to that, its obviously a big problem.
Click to expand...
Click to collapse
My phone was working flawlessly then I connected it to usb, Display turned blank (gray) then It is dead as a brick. No lights no charging signs of life
Avikar said:
My phone was working flawlessly then I connected it to usb, Display turned blank (gray) then It is dead as a brick. No lights no charging signs of life
Click to expand...
Click to collapse
Put the phone on the wall charger (not connected to your computer) for several hours (overnight) and see if there is any change.
Not sure if it's the same problem, but I had something similar happen a couple days ago while on CM 10.2 nightly:
Sudden power drop
I threw a couple logs in there, just in case they were useful.
redpoint73 said:
Put the phone on the wall charger (not connected to your computer) for several hours (overnight) and see if there is any change.
Click to expand...
Click to collapse
Charged it for the whole night still the same dead phone no response... No vibrations, no screen and no LEDS.
Avikar said:
Charged it for the whole night still the same dead phone no response... No vibrations, no screen and no LEDS.
Click to expand...
Click to collapse
Try the bootloader button combination. Then try it while connected to the wall charger. Similarly, just try booting normally while connected to the charger. It makes no sense, but I've seen at least one guy where this worked (bootloader button combo while connected to charger), when nothing else would make the phone boot.
Other than that, its not looking good. No LEDS, and the phone can't be read by the computer, you're pretty done. Odd that just connected to USB did this. Maybe some hardware failure related to the USB port?
redpoint73 said:
Try the bootloader button combination. Then try it while connected to the wall charger. Similarly, just try booting normally while connected to the charger. It makes no sense, but I've seen at least one guy where this worked (bootloader button combo while connected to charger), when nothing else would make the phone boot.
Other than that, its not looking good. No LEDS, and the phone can't be read by the computer, you're pretty done. Odd that just connected to USB did this. Maybe some hardware failure related to the USB port?
Click to expand...
Click to collapse
Yeah even i can't digest the fact that making my phone S-off installing CM 10.2 didnt do any bad but a connection to USB killed my phone

[INFO]Software related charging issue on S4

Hi guys,
Had a very weird issue yesterday with my Rogers S4. I have flashed a bunch of ROMS in the past, but wanted to try the new MEA firmware based ROMS..
Well yesterday i tried Mint Jelly v2.1 (flashed via TWRP) and immediately without rebooting flashed 005 FAUX kernal to avoid boot loops. My battery was about 15% at the time. The flash took, and the phone rebooted into the ROM no issues.
Noticed that when i plugged in the charger to my S4 it was NO LONGER charging. I tried multiple 2.1amp chargers, and cables, including OEM, and it no longer charged. However it charged my NOTE2 with no issues.
This is when i was about to FREAK.. but i recall from my HP Touchpad days that sometimes if the battery dies, you need to do something special to get hte phone to charge back up again.
So what i did, was completely shut down the phone, and plug it back in the charger, and it started to charge again. But immediately booting into Android, it would still no longer charge!!.. So i let it charge up for an hour wiht the power off. Once i booted in again, the phone was able to charge again normally with all my chargers while booted in.
I thought my situation was a freak incident until i noticed another XDA member report the same issue. This is NOT a hardware issue, but something related to software.. So give my advice a shot incase you encounter this yourselves!
ED
minirx7 said:
Hi guys,
Had a very weird issue yesterday with my Rogers S4. I have flashed a bunch of ROMS in the past, but wanted to try the new MEA firmware based ROMS..
Well yesterday i tried Mint Jelly v2.1 (flashed via TWRP) and immediately without rebooting flashed 005 FAUX kernal to avoid boot loops. My battery was about 15% at the time. The flash took, and the phone rebooted into the ROM no issues.
Noticed that when i plugged in the charger to my S4 it was NO LONGER charging. I tried multiple 2.1amp chargers, and cables, including OEM, and it no longer charged. However it charged my NOTE2 with no issues.
This is when i was about to FREAK.. but i recall from my HP Touchpad days that sometimes if the battery dies, you need to do something special to get hte phone to charge back up again.
So what i did, was completely shut down the phone, and plug it back in the charger, and it started to charge again. But immediately booting into Android, it would still no longer charge!!.. So i let it charge up for an hour wiht the power off. Once i booted in again, the phone was able to charge again normally with all my chargers while booted in.
I thought my situation was a freak incident until i noticed another XDA member report the same issue. This is NOT a hardware issue, but something related to software.. So give my advice a shot incase you encounter this yourselves!
ED
Click to expand...
Click to collapse
Never flash anything or make major changes to your phone with a low battery (below 70%).
I may be the member he was talking about. I had a thread on this. Only difference was my phone wouldn't charge at all. When I plugged it in when it was off it would boot loop the charge screen. It was rooted and I had some bloat frozen, but the issue started after I installed Sugarsync. I had the same configuration for a few days with no problems, and my battery was about 50 percent when I tried to charge.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Just trying to help. I freaked yesterday because no matter what i did, it wasnt charging. But once i fully powered off, it started chargin!!
scott14719 said:
Never flash anything or make major changes to your phone with a low battery (below 70%).
Click to expand...
Click to collapse
I just flashed a ROM with 56%. I like to live dangerously.
AdePower said:
I just flashed a ROM with 56%. I like to live dangerously.
Click to expand...
Click to collapse
It's definitely possible and usually will work just fine. There are a couple of reasons to flash on a full battery. If something goes wrong and takes a lot longer than originally anticipated, there is less chance of the battery going dead while things are being fixed. Plus, many ROMs (Kernels actually) enact different power profiles for different stages of charge. If this is the case, flashing might not go as anticipated.
scott14719 said:
It's definitely possible and usually will work just fine. There are a couple of reasons to flash on a full battery. If something goes wrong and takes a lot longer than originally anticipated, there is less chance of the battery going dead while things are being fixed. Plus, many ROMs (Kernels actually) enact different power profiles for different stages of charge. If this is the case, flashing might not go as anticipated.
Click to expand...
Click to collapse
I bricked a S2 like that. Flashed a rom adn the battery drained in the process, causing it not flash properly. phone was dead, no download mode or anything.

LG G3 - Fried battery and/or charging port?

Let me lay down the story first:
It all started when I tried out multiROM for the LG G3. I was running cm12 perfectly fine, unlocked and everything. Amazing battery life. But MultiROM barely worked, even though I followed the instructions exactly, I had many errors trying to get anything to boot properly. I got help with it, but ended up getting rid of multirom via internal storage (where it was) and flashing a normal, non modified TWRP 2.8.4.0. This is where stuff starts getting weird.
After getting rid of multiROM and flashing cm12 again from backup, I noticed my phone wouldn't take a charge at all. It was booted up and running at about 30% battery. My PC wouldnt do anything when I plugged it into my computer, too. I thought it was just Cyan being weird, so I rebooted into twrp and tried plugging in. No buzz, still wouldn't take a charge. For some reason, turning the phone off and plugging in the charger while it was off actually turned it on. So the charging port has to be working, the phones just being weird... but then I decided to smell the charging port. Smells like pure burning electronics. I rebooted the phone with the cable plugged in, and it boots up and charges. This is odd, because i can no longer plug the cable in while the phone is on, i have to reboot it with the cable in now in order to get it to charge. I tried flashing back to stock ROM, and same exact issue happens. Not only that, but the battery no longer holds a charge for more than a day on one full charge. It lasts about 3-4 hours now.
Please, xdaers, help a brotha out. I'm really pissed about whatever the hell is happening to my G3. It still works fine, I just have to reboot it with the cable in in order to get it to charge at all and the battery life sucks on top of that.
Note: One time after all this happened, the phone died fully. Plugging the charger in, the battery logo was flashing on and off. I tried multiple cables and chargers with the same problem. I pulled out the battery with the cable still in, and the battery logo actually stayed on the screen and once I put the battery back in, it charged again. THIS IS MAJORLY CONFUSING and hard to explain so I will clarify my issue if you are confused with my post.
Also, the phone likes to get really hot and die fast by itself even without the charger plugged in now.
thanks guys
Hi
Thanks for writing to us at XDA assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
http://forum.xda-developers.com/att-lg-g3
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
http://forum.xda-developers.com/att-lg-g3/help
Good luck!
So you flashtooled back to stock? And still persists? If so you next option is to buy both a battery and a charging port and do some trouble shooting.
2SHAYNEZ
King Ramen said:
Let me lay down the story first:
It all started when I tried out multiROM for the LG G3. I was running cm12 perfectly fine, unlocked and everything. Amazing battery life. But MultiROM barely worked, even though I followed the instructions exactly, I had many errors trying to get anything to boot properly. I got help with it, but ended up getting rid of multirom via internal storage (where it was) and flashing a normal, non modified TWRP 2.8.4.0. This is where stuff starts getting weird.
After getting rid of multiROM and flashing cm12 again from backup, I noticed my phone wouldn't take a charge at all. It was booted up and running at about 30% battery. My PC wouldnt do anything when I plugged it into my computer, too. I thought it was just Cyan being weird, so I rebooted into twrp and tried plugging in. No buzz, still wouldn't take a charge. For some reason, turning the phone off and plugging in the charger while it was off actually turned it on. So the charging port has to be working, the phones just being weird... but then I decided to smell the charging port. Smells like pure burning electronics. I rebooted the phone with the cable plugged in, and it boots up and charges. This is odd, because i can no longer plug the cable in while the phone is on, i have to reboot it with the cable in now in order to get it to charge. I tried flashing back to stock ROM, and same exact issue happens. Not only that, but the battery no longer holds a charge for more than a day on one full charge. It lasts about 3-4 hours now.
Please, xdaers, help a brotha out. I'm really pissed about whatever the hell is happening to my G3. It still works fine, I just have to reboot it with the cable in in order to get it to charge at all and the battery life sucks on top of that.
Note: One time after all this happened, the phone died fully. Plugging the charger in, the battery logo was flashing on and off. I tried multiple cables and chargers with the same problem. I pulled out the battery with the cable still in, and the battery logo actually stayed on the screen and once I put the battery back in, it charged again. THIS IS MAJORLY CONFUSING and hard to explain so I will clarify my issue if you are confused with my post.
Also, the phone likes to get really hot and die fast by itself even without the charger plugged in now.
thanks guys
Click to expand...
Click to collapse
Don't know about the charging port, but as far as battery life I'm getting the same thing, except mine lasts about 2 hours, I've decided I'm selling the phone while its still worth a bit of money, probably getting a Note 2 or Xperia Z2, I've been very unhappy with this phone, also my battery cover is falling apart and cracking,
SmokeyTech1 said:
Don't know about the charging port, but as far as battery life I'm getting the same thing, except mine lasts about 2 hours, I've decided I'm selling the phone while its still worth a bit of money, probably getting a Note 2 or Xperia Z2, I've been very unhappy with this phone, also my battery cover is falling apart and cracking,
Click to expand...
Click to collapse
Well I've had none of your problems. Note 2 or z2 is a downgrade. Have fun with that... Sucks your experience hasn't been a good one. Cheers
2SHAYNEZ
I get 13+ hours with 4 to 5 hours screen on time and 1to 2 hours of talk time. So I don't think your battery issue is normal for this phone. You have either a defective battery or phone or an app that is misbehaving.
I'm having the exact same problem with LG G3.
Can only charge when rebooted. And even then the charge indicator does not show charging.
I have to go into setting->battery where it shows 'charging'
I have tried new battery and cleaning port.
Anyone figure this out...?
My battery drained very fast before too after backed up to stock, but after I upgraded to 5.0, my phone can lives up to next morning!
Sent from my LG-D850 using XDA Free mobile app

HELP!!!! Fixing battery charging problem

Hello,
I went out last Friday and came home late. My phone is out of battery and dead. I plugged it in and woke up the next day with a dead phone. Apparently, there is a bug with the OPO. If the battery is too low, it won't even charge after you plug it in for charging. I have tried all tricks and even contact the OPO Tech Support Team. This thread describes how horrible they are:
http://forum.xda-developers.com/oneplus-one/general/tech-support-onepluse-one-horrible-t3084022
I am at my wit's end. I have tried all the the tricks. This is a thread that I found that seems to have the same problem as I have.
http://forum.xda-developers.com/oneplus-one/help/oneplusone-phone-dead-t3079256
The only choice I have left is to open the phone, disconnect the battery connection and reconnection it again. Hoping it will recharge. However, there is a warranty sticker and I don't want OPO to deny my warranty. I am not new to Android and I have fixed phones before. I also think of buying a new OPO battery and switch it with the factory one. Since the new battery will be charged, I think that will work in fixing it. But, doing that is much more complicate and it requires me to remove more components. If you have a good working solution for my problem, please help.
NOTE: please don't ask me to check my charger or use a different one. I check it 1000 times already. The original charger works, the cable works. I use different chargers and cables. Same result.
Thank you for your help.
Have you rooted and unlocked? I had the same problem when I got mine at first. It would show charging but never fully charge. 73% was all it would do. So after rooting and flashing a custom kernel the problem went away. Now I can go back to stock and the problem has never comeback. Maybe just a small software glitch or something. I'm just happy it's gone!
brandonhatty said:
Have you rooted and unlocked? I had the same problem when I got mine at first. It would show charging but never fully charge. 73% was all it would do. So after rooting and flashing a custom kernel the problem went away. Now I can go back to stock and the problem has never comeback. Maybe just a small software glitch or something. I'm just happy it's gone!
Click to expand...
Click to collapse
The phone is unlocked and rooted. The issue is not fully charged or not. The issue here is the phone does not charge after the battery die. The phone is dead because I let the battery run to 0. When I plug it to recharge, the low battery screen does not even come up. The phone is dead and refuse to recharge. There is no issue with the charger or the charging cable. I have checked it several time already. I am very frustrated with OPO Tech Support right now.
I see. Only other thing I can think of is try holding the power button for 60 seconds while it's plugged in. That does suck man.
I had similar issue, my conclusion is the bootloader charging function is broken.
Basically I would start the charging, it would charge for about 10 seconds or so, and then stop. I thought my battery was dead.
I couldnt boot the os as wasnt enough charge.
So eventually I just kept repeating the process, 10 seconds charge at a time, and eventually had enough juice to boot android and after that point it charged to full ok.
Never had this issue on any of my samsung phones.
Also to point out when it went dead it was plugged into my pc usb at the time with twrp loaded.

Categories

Resources