[Completed] [Q] Nexus 4 won’t boot up/work without charger plugged in after flashing - XDA Assist

I have flashed a CM12 nightly using TWRP recovery. After that, during rebooting, phone switched off automatically after showing “google” logo. I went back to the TWRP and installed the backup which I have kept (stock lollipop 5.0.1). After that when I’m trying to turn on, it’s working with the charger plugged in. If I remove the charger after switching on, if I kept it idle, it will stay on till the battery is empty (I got around 24 hrs). But if I try to take mobile data or camera it will switch off for sure. Sometimes just moving across different home screens also will make it switch off. The battery status show is also not correct when switched on. In recovery mode it works well without battery and battery percentage is also correct.
What will be the reason?? Is it something related to the firmware or a Hardware issue?? Will changing the battery help??

Please Flash Stock Firmware. Once done, you can try another Nightly of CM. If it persists, please post in [Q&A] [Mako][Nexus 4][ROM][CM12][5.0.2] Temasek's UNOFFICIAL Build [v4.2 - 04/01/201
Oh Yes, Don't do any of this until the Battery is Fully Charged.

Related

[Q] Battery Status Bug (Still Charging after disconnected from USB)

Hello.
I got a problem after updating to the latest CyanogenMod 11 from this thread: http://forum.xda-developers.com/showthread.php?t=2528113
I am always updating the latest Nightly Build and since the last update my battery status is showing 3-4%, the charging icon and the orange LED even when im not connected via USB!
Of course my battery is fully charged because it still lasts more then a day.
I read trough the thread and noone reported this bug so i assume that im the only one who got this problem.
My HTC One S:
Hboot: 2.15
Rooted
S-On
Android 4.4.2
CyanogenMod 11-20131216-NIGHTLY-ville
ClockworkMod 6.0.4.5
I tried to wipe Cache, Dalvik Cache and deleted the batterystats.bin but it didnt help.
Can anyone help me?
Thanks
Battery / charge problems
EvilPotato123 said:
Hello.
I got a problem after updating to the latest CyanogenMod 11 from this thread: http://forum.xda-developers.com/showthread.php?t=2528113
I am always updating the latest Nightly Build and since the last update my battery status is showing 3-4%, the charging icon and the orange LED even when im not connected via USB!
Of course my battery is fully charged because it still lasts more then a day.
I read trough the thread and noone reported this bug so i assume that im the only one who got this problem.
My HTC One S:
Hboot: 2.15
Rooted
S-On
Android 4.4.2
CyanogenMod 11-20131216-NIGHTLY-ville
ClockworkMod 6.0.4.5
I tried to wipe Cache, Dalvik Cache and deleted the batterystats.bin but it didnt help.
Can anyone help me?
Thanks
Click to expand...
Click to collapse
I'm having a similar issue except my htc one s is not rooted. But the orange charge indicator light stays on even after unplugged from the charger. I too tried wiping the cache. Battery apps show battery life is healthy.
In order to get the orange charge light indicator off, I have to restart the phone. But strangely enough, after a restart it won't take to a charge unless I restart the phone again.
So, I finally let the phone on all day to kill the battery and charged it for four hours while off. When I turned it back on the battery icon said it was at 96% charged - and I thought I finally fixed it. But when I unplugged the charger, the orange light did not turn off. ugh. So I restarted the phone and once again, the battery now says it's at 33%. WTF?!
Again, I wiped the cache partition; let the battery die, did complete charge while phone off; did a hard reset (held volume rocker and power button for 10 seconds). Other ideas?
Software info:
Android version: 4.1.1
HTC Sense version: 4+
HTC SDK API Level: 4.63

[Q] Xperia E single is dead, please help :(

so i changed my galaxy tab to cyanogenmod, and it was love at first sight. jks but i really wanted to put my xperia E (single) onto cyanogen in the hopes that it wouldnt lag all the time.
i unlocked the bootloader, and then installed i think TWRP. i used my tab to install CM 10 nanhu.zip to my sd card, and then moved that to my phone, before loading it from there.
this worked, and i was setting up my new phone, but i turned it off to install gapps.zip from recovery. i turned it off, and it never turned back on. i then reflashed a recovery image, and from there, i could adb , and fastboot, and when i plugged it in the led glowed green. i left it to charge for 15 minutes, and then i realised the glowing charge light had gone out. then i tried putting it to fastboot, but the fastboot light never activated. is there a booting limit as to how much battery i need.i need heelllpppp
Try charging your batery in a battery charger not in the phone.When you do something with ROM and things like that be sure the battery is at 100%.

[Completed] I think I have bricked my SM-T320, help

model: sm-t320 wifi only, just flashed cm13 nightly, i believe it was the one released on the first of February 2016, the tablet was working okay sometimes a bit laggy but that is expected with the nightly not fully developed or whatever. i installed and am still using cm13 on my tablet but i installed it on my friends tablet which is the exact same tablet, color and all, and this happened: it shut of by itself and when i tried to turn it back on it wouldnt. i plugged it in and the battery charging icon turned on but it was only the icon with the loading circle image in the middle. so i let it charge for a good six hours and during that the screen stayed on with the same image. when i unplugged it, after about two seconds the screen dimmed and started flashing on and of as if there was a loose connection. then it just shuts off. when it is unplugged i cant do anything, (turn on, download mode, recovery) the screen just stays blank. when i have it plugged in i can access the first boot screen displaying "samsung galaxy tab pro" and it will not go any further. i can also access download mode perfectly. i cannot access recovery mode, it just goes straight to the first boot screen. i tried flashing the stock rom and was unsuccessful. either because the computer was not supplying enough voltage/amps to keep the tablet running or it just simply would not boot. the flash was successful each time i tried on odin but the same issues happened on the tablet each time. i did not install Gapps because he just wanted to try it out quickly and maybe keep it or go back to stock if (that helps). i believe that is all i know. please help me!
XDA Visitor said:
model: sm-t320 wifi only, just flashed cm13 nightly, i believe it was the one released on the first of February 2016, the tablet was working okay sometimes a bit laggy but that is expected with the nightly not fully developed or whatever. i installed and am still using cm13 on my tablet but i installed it on my friends tablet which is the exact same tablet, color and all, and this happened: it shut of by itself and when i tried to turn it back on it wouldnt. i plugged it in and the battery charging icon turned on but it was only the icon with the loading circle image in the middle. so i let it charge for a good six hours and during that the screen stayed on with the same image. when i unplugged it, after about two seconds the screen dimmed and started flashing on and of as if there was a loose connection. then it just shuts off. when it is unplugged i cant do anything, (turn on, download mode, recovery) the screen just stays blank. when i have it plugged in i can access the first boot screen displaying "samsung galaxy tab pro" and it will not go any further. i can also access download mode perfectly. i cannot access recovery mode, it just goes straight to the first boot screen. i tried flashing the stock rom and was unsuccessful. either because the computer was not supplying enough voltage/amps to keep the tablet running or it just simply would not boot. the flash was successful each time i tried on odin but the same issues happened on the tablet each time. i did not install Gapps because he just wanted to try it out quickly and maybe keep it or go back to stock if (that helps). i believe that is all i know. please help me!
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
Based on the model number you've provided, this is the homepage for your device:
Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Guides and other helpful information can be found in the General Section.
If you create an XDA account, you can ask your questions in the Q&A Section.
Good luck and welcome to XDA!

LG G3 stuck in bootloop, even after flashing stock ROM

Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
ccraw said:
Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
Click to expand...
Click to collapse
Sadly that is because of a hardware issue. Been happening. A lot lately.
hyelton said:
Sadly that is because of a hardware issue. Been happening. A lot lately.
Click to expand...
Click to collapse
Alright, that's what I had read. Just seemed like a software issue so I was hoping for the best. I went ahead and ordered a new device. Im guessing a full motherboard replacement would be required to fix the device?
Recurring Issue
Hello,
The same problem happened to me a few days ago so this is trully a recurring issue.
I also tried to fix my rom by reinstalling it, then tried to install multiple new rom, and finally flashed the original stock rom. I also am stuck on the bootloop issue.
I'm going to contact LG to see if they can do anything to repaire it but my hope are very low.
I'll try to update this message if I find a solution.
Mine just started bootlooping and no wifi and today it just died. Battery pulls didnt work either no power at all. Probably going to switch to the V30 when its released.
Sent from my One using Tapatalk
ccraw said:
Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
Click to expand...
Click to collapse
It's probably to late but theres another method returning to stock KitKat dont know the link off hand in development forums. Sucks you couldnt try no adb methods. Still have the Phone want to sell it i need a cheap screen ?

Samsung Tab 2 [GT-P3100] Won't work

Summary: I was installing a Slim7 custom rom on my tablet when before it finishes off the power went off and my device turned off completely, when I was trying to boot back on Recovery [TWRP] it won't work so thus Download mode it is completely dead. Thinking this was a battery problem (drained, I guess) I tried to charge my tablet but it doesn't charge properly, stucked in "cycle" logo inside a battery (but won't animate as usual) and doesn't proceed to actual charging animation.
"I am sure this was due to battery problem, I tried to install it with 5% battery (but charging on a pc). I think it didn't charge correctly until it ran out."
I tried everything that might help myself
- holding power button for few minute and plugging the charger after a couple of seconds..
- Using Samsung Kies
- Odin
So how do I fix this problem??
please help me.
none works. hopefully someone here is willing to help me out, thanks in advance
You should never use KIES if you installed a custom ROM or a custom recovery - it's likely to fail and giving "black screen of death"

Categories

Resources