Related
Hi,
Last night my nexus died, i have no idea why. it was working fine until the battery drained and when i tried to charge the phone the LED charged to RED and nothing happen.
I have tried every thing that i can think of to reboot the phone but with no success.
(charging it all night, pressing any button combination.. etc.)
the only thing i can do with the phone is when i press the power + volume up for 30-60 sec the red led turn off.
I have taken apart the phone and disconnected the battery for few hours and tried again, but noting helps.
I believe that the problem is that the battery is fully drained and i need to charge it without using the phone.
how can i do it ?
do you have any other recommendations ?
Thanks
http://forum.xda-developers.com/search.php?searchid=158131778
Hi,
Try this:
Faux123 said:
I got into many red LED situations, I was able to come out of it everytime by using the procedure I posted above (that post was from pure experience I had).
red led bootloop unbrick procedure
1. plug phone into USB cable connected to computer
2. wait for it to go into charge animation
3. unplug, then press power button to boot, immediately press vol up + vol down.
4. hopefully you booted into bootloader mode (rinse and repeat steps 1~4 if you can't get to this point)
5. chose recovery (if your recovery is corrupted, repeat steps 1~4 and do fastboot flash recovery cwmxxx.img)
6. from recovery choose restart system
if you can't get to step 2, because N4 has a bug with battery capacity, plug your phone into AC charge and let it charge for a few mins. then restart from step 1...
Click to expand...
Click to collapse
But even if disconnected / reconnected the battery still nothing... (howewer it's a good solution for the red light of death)
Try the thing above or let your phone in charge for some hours and don't use it...
If nothing works -> warranty
and if you get into download mode instead of red led use power and hold it for 10 secs till the screen goes off then quickly press and hold power up and down at the same time to boot into bootloader
Sent from my Nexus 4 using Tapatalk 2
12 hours in the charger and nothing.
disconnect the battery (wait 10 minutes) reconnect and try to charge/power button/button combination .. nothing!!!!
i will try contact Google and check how can i replace the phone.
did any one manage to replace a phone ? Google is blocking my IP (i'm not from the US) so i can't read the FAQ .
fakeer said:
12 hours in the charger and nothing.
disconnect the battery (wait 10 minutes) reconnect and try to charge/power button/button combination .. nothing!!!!
i will try contact Google and check how can i replace the phone.
did any one manage to replace a phone ? Google is blocking my IP (i'm not from the US) so i can't read the FAQ .
Click to expand...
Click to collapse
I read somewhere that disconnecting the battery and reconnecting it will clear this issue, of course it means that you have to open the phone which is not hard
DynamicRam said:
I read somewhere that disconnecting the battery and reconnecting it will clear this issue, of course it means that you have to open the phone which is not hard
Click to expand...
Click to collapse
it didn't work
Hi,
@ fakeer, when you said you have disconnect the battery, you mean you have open the phone? Or it's just plug / unplug from the charger? This is what I understood...
Like DynamicRam said you can open the phone and disconnect / reconnect the battery...
EDIT: ok...
fakeer said:
it didn't work
Click to expand...
Click to collapse
open the phone
It looks like your battery(battery sensor) is damaged
http://www.ebay.com/sch/i.html?_trk...timus+E960+Google+Nexus+4+&_sacat=0&_from=R40
Trying to fix a family members xt907 so here's the situation which has been nothing but headaches for me:
1. The Phone is only 7 months old and the bootloader is unlocked so warranty exchange is out of the question. She let the battery run down until the phone died. Then without charging the phone she turned it back on and it died again. From that point she couldn't get it to charge or turn back on while plugged in. At this point she brought it to me.
2. I got the phone and did a soft reset which finally got the charging screen to come up (showed the actual charging icon and the fill meter would flash up and then back down periodically). Problem is it never went past 0% after charging all night. I went ahead and tried to power it up thinking maybe it was just a glitch with the charging screen. Phone wouldnt boot. Just stuck at the Motorola logo. Another soft reset and the phone finally boots but now the battery icon showed a '?' and status showed '5% - Unknown'.
3. Performed a factory reset. No change. So I used RSD to flash the stock 4.1.2 firmware/kernel/modem, etc... What I found strange here is that despite the low battery Fastboot AP showed battery as OK, not low and let me flash (bootloader is unlocked, not sure if that affects low battery flashing or if that safeguard just wasnt built into the M).
4. So phone boots back up and shows 7% battery. Plugging in the charger at first notice has no affect. Battery stats shows '7% - Not Charging'. So I unplug the charger and the low battery warning pops up. Plug it back in and phone still doesnt register as charging, but says 'Not Charging'. Then I notice that the lockscreen shows '7% Charging'. Weird. Regardless of all that, the battery was not charging. The percentage never goes up and after reboots the percentage will remain the same. The battery does slowly discharge on the charger if I have it powered on.
5. I tried flashing a couple different roms before flashing back to stock and all had the same problem. I've formated /system hoping it was a problem with the OS but it didnt help. All of these charging tests were performed with the stock Motorola usb cable plugged into the wall charger. I tested the Motorola charger against my S4 to verify it works and also tried my Samsung charger on the Razr and it made no difference. However, booting the Razr M up with the Samsung charger resulted in the '?' in the battery icon and a notification in the status bar saying something about a CommServer starting. This notification was persistant and could not be dismissed. If I reboot the phone with the Motorola charger or no charger then that notification and the '?' dont appear.
6. I should also point out that I opened the phone up and disconnected the battery from the board and discharged the board. As a last resort I completely removed the battery and peeled back the tape on the bottom of the battery to expose the + and - terminals on the battery and wired it up to a stripped down charger and left it for a bit. Upon putting the battery back in the phone it showed a charge of 30% but still had all the same problems otherwise. So the battery is capable of taking a charge, it just wont take it through the phone, whether powered on or off. Thats what leads me to believe the battery itself is not bad. Its not practical for her to pull the battery to charge it, obviously. The phone detects the cable being plugged in and I can transfer files via usb cable to/from the computer no problem, so I'm fairly sure the Micro usb port is ok. Just refuses to charge.
A little lengthy but I'm at my wits end on this and really dont want to have her buy a $50 battery and then its a problem with the phone. I dont usually get stumped when it comes to fixing something but this one really has me. So if anybody can shed some light on this situation it would be greatly appreciated.
CallMeAria said:
Trying to fix a family members xt907 so here's the situation which has been nothing but headaches for me:
1. The Phone is only 7 months old and the bootloader is unlocked so warranty exchange is out of the question. She let the battery run down until the phone died. Then without charging the phone she turned it back on and it died again. From that point she couldn't get it to charge or turn back on while plugged in. At this point she brought it to me.
2. I got the phone and did a soft reset which finally got the charging screen to come up (showed the actual charging icon and the fill meter would flash up and then back down periodically). Problem is it never went past 0% after charging all night. I went ahead and tried to power it up thinking maybe it was just a glitch with the charging screen. Phone wouldnt boot. Just stuck at the Motorola logo. Another soft reset and the phone finally boots but now the battery icon showed a '?' and status showed '5% - Unknown'.
3. Performed a factory reset. No change. So I used RSD to flash the stock 4.1.2 firmware/kernel/modem, etc... What I found strange here is that despite the low battery Fastboot AP showed battery as OK, not low and let me flash (bootloader is unlocked, not sure if that affects low battery flashing or if that safeguard just wasnt built into the M).
4. So phone boots back up and shows 7% battery. Plugging in the charger at first notice has no affect. Battery stats shows '7% - Not Charging'. So I unplug the charger and the low battery warning pops up. Plug it back in and phone still doesnt register as charging, but says 'Not Charging'. Then I notice that the lockscreen shows '7% Charging'. Weird. Regardless of all that, the battery was not charging. The percentage never goes up and after reboots the percentage will remain the same. The battery does slowly discharge on the charger if I have it powered on.
5. I tried flashing a couple different roms before flashing back to stock and all had the same problem. I've formated /system hoping it was a problem with the OS but it didnt help. All of these charging tests were performed with the stock Motorola usb cable plugged into the wall charger. I tested the Motorola charger against my S4 to verify it works and also tried my Samsung charger on the Razr and it made no difference. However, booting the Razr M up with the Samsung charger resulted in the '?' in the battery icon and a notification in the status bar saying something about a CommServer starting. This notification was persistant and could not be dismissed. If I reboot the phone with the Motorola charger or no charger then that notification and the '?' dont appear.
6. I should also point out that I opened the phone up and disconnected the battery from the board and discharged the board. As a last resort I completely removed the battery and peeled back the tape on the bottom of the battery to expose the + and - terminals on the battery and wired it up to a stripped down charger and left it for a bit. Upon putting the battery back in the phone it showed a charge of 30% but still had all the same problems otherwise. So the battery is capable of taking a charge, it just wont take it through the phone, whether powered on or off. Thats what leads me to believe the battery itself is not bad. Its not practical for her to pull the battery to charge it, obviously. The phone detects the cable being plugged in and I can transfer files via usb cable to/from the computer no problem, so I'm fairly sure the Micro usb port is ok. Just refuses to charge.
A little lengthy but I'm at my wits end on this and really dont want to have her buy a $50 battery and then its a problem with the phone. I dont usually get stumped when it comes to fixing something but this one really has me. So if anybody can shed some light on this situation it would be greatly appreciated.
Click to expand...
Click to collapse
I presumed you tried to wipe the battery stats via the battery calibration app? not that I think it would make a difference. another option is enable/disable USB debugging. you could also try charging into a PC or a different outlet (perhaps that outlet does not provide a good current)?
not really sure, just tossing out some ideas...
jco23 said:
I presumed you tried to wipe the battery stats via the battery calibration app? not that I think it would make a difference. another option is enable/disable USB debugging. you could also try charging into a PC or a different outlet (perhaps that outlet does not provide a good current)?
not really sure, just tossing out some ideas...
Click to expand...
Click to collapse
I actually installed cwm recovery just to wipe battery stats. Im assuming it works the same way but I'll give the app a try. I'll try anything at this point. Tried your other ideas already though and didnt make any difference.
I appreciate the input. I'll give that app a try and see if it does something different from wiping battery stats in recovery.
CallMeAria said:
I actually installed cwm recovery just to wipe battery stats. Im assuming it works the same way but I'll give the app a try. I'll try anything at this point. Tried your other ideas already though and didnt make any difference.
I appreciate the input. I'll give that app a try and see if it does something different from wiping battery stats in recovery.
Click to expand...
Click to collapse
Doubt it. However, the issue seems to be with the hardware, and since it is not a software issue, Motorola could honor the warranty. Last resort would be to unroot and see if you can get an exchange.
Sent from my XT907 using xda app-developers app
have you tried a non moto cable? the one that came with my fone was total crap, would continuously connect and disconnect when i hooked it up to my comp or try to charge it, so i tried my old samsung cable and i didnt have any disconnect problems at all. just a suggestion
CallMeAria said:
I actually installed cwm recovery just to wipe battery stats. Im assuming it works the same way but I'll give the app a try. I'll try anything at this point. Tried your other ideas already though and didnt make any difference.
I appreciate the input. I'll give that app a try and see if it does something different from wiping battery stats in recovery.
Click to expand...
Click to collapse
Did you ever find a solution? I am having the same issues with my xt907.
What did you have it plugged in to? The fact that it said it was not charging indicates maybe you didn't have enough power coming through the charging port...
Sent from my XT907 using Tapatalk 4 Beta
uthkuknwme said:
have you tried a non moto cable? the one that came with my fone was total crap, would continuously connect and disconnect when i hooked it up to my comp or try to charge it, so i tried my old samsung cable and i didnt have any disconnect problems at all. just a suggestion
Click to expand...
Click to collapse
yeah I tried my Samsung cable as well.
jgramkow said:
Did you ever find a solution? I am having the same issues with my xt907.
Click to expand...
Click to collapse
No. Verizon finally sent her a refurb replacement. I got the battery to charge up by taking it out and rigging a charger to it. But the phone still wouldnt accept a charge with the battery back in and it lost the charge it did have 2-3 times faster than normal. Battery Stats also showed the battery was showing a pretty decent voltage so unless the battery itself has a low charge circuit that gets tripped I'd be hesitant to point to the battery itself. And the charger port transfered files just fine and the phone recognized when the charger was plugged in (would go from 'discharging' to 'not charging'. So yeah, I was left stumped. Hopefully somebody else can get this solved for you.
CallMeAria said:
yeah I tried my Samsung cable as well.
No. Verizon finally sent her a refurb replacement. I got the battery to charge up by taking it out and rigging a charger to it. But the phone still wouldnt accept a charge with the battery back in and it lost the charge it did have 2-3 times faster than normal. Battery Stats also showed the battery was showing a pretty decent voltage so unless the battery itself has a low charge circuit that gets tripped I'd be hesitant to point to the battery itself. And the charger port transfered files just fine and the phone recognized when the charger was plugged in (would go from 'discharging' to 'not charging'. So yeah, I was left stumped. Hopefully somebody else can get this solved for you.
Click to expand...
Click to collapse
Just an update: I ended up buying a replacement battery and it fixed the charging issue. I rsd back to stock. Then, playing around with it, I booted to bootloader and selected "Factory" and it immediately booted back to stock, but, the battery had a "?" again. Ready to throw the damn phone against the wall, I rebooted it. The "?" is mysteriously gone. What is the "Factory" setting? I think I tried it before, but had CM10.1 installed. My theory is that this "factory" boot from bootloader actually soft bricked the phone. Either that or the issue was truly the battery and simply replacing it fixed things. I am up and running now, cm10.1 is flawless, imho. Thanks for the quick reply and I hope this helps anyone with similar issues.
Beware of the "Factory" bootloader option...........
Here we go again. Upon a reboot into recovery. Recovery is twrp 2.5. What I notice is the motorola boot img takes an extremely long time (2 minutes) to turn off and cyanogenmod to begin. Could there be something corrupt in the bootloader? Is there any way to reload the bootloader on this device? Anyone have any ideas? Could it be Recovery?
Symptoms:
Phone wont charge (nor will it show charging - no lightning bolt)
Phone wont connect to computer USB.
If I connect the USB (to either a computer or a charger) the phone just pulses the vibration every 2 sec or so... and does not show the battery progress... just black screen.
As long as the phone has a fresh battery, it functions normally otherwise.
What its NOT:
The cable - tried many cables.
The charger - tried different samsung chargers...
The comptuer - tried more than one
The usb connector in the phone - nope.. not that either. When in ODIN mode, the phone stays on when I remove the battery... thus.. the USB connector is passing power.
The power button - The phone starts normally via the power button. It shuts down properly with the power button. The power button performs wakeup, etc all normally.
The battery - I have two Note 4's. I swap the battery, and the problem remains on the one phone.
Steps I have done:
I wiped the cache partition first... no change.
I did a full factory reset... no change.
I need some answers. I have run out of ideas. I'm not taking this to sprint. It will take an hour to explain to them what I've already done, and they will want to do expensive things that I bet will not fix it.
Rod
martinav said:
Symptoms:
Phone wont charge (nor will it show charging - no lightning bolt)
Phone wont connect to computer USB.
If I connect the USB (to either a computer or a charger) the phone just pulses the vibration every 2 sec or so... and does not show the battery progress... just black screen.
As long as the phone has a fresh battery, it functions normally otherwise.
What its NOT:
The cable - tried many cables.
The charger - tried different samsung chargers...
The comptuer - tried more than one
The usb connector in the phone - nope.. not that either. When in ODIN mode, the phone stays on when I remove the battery... thus.. the USB connector is passing power.
The power button - The phone starts normally via the power button. It shuts down properly with the power button. The power button performs wakeup, etc all normally.
The battery - I have two Note 4's. I swap the battery, and the problem remains on the one phone.
Steps I have done:
I wiped the cache partition first... no change.
I did a full factory reset... no change.
I need some answers. I have run out of ideas. I'm not taking this to sprint. It will take an hour to explain to them what I've already done, and they will want to do expensive things that I bet will not fix it.
Rod
Click to expand...
Click to collapse
It seems that the micro USB connector on the phone is broken.
Note 4 is using 11 pin microUSB not the ordinary 5 pin.
You can still have power but very minimum wattage if 1 or several pins are broken, that's why in ODIN mode it still ON without battery as ODIN mode requires minimum power.
Try changing the micro USB connector on the phone (not the cable)
Hello guys. I have problem with fast charging. My brother used my "head" of my P10+ supercharger with his lighting usb to charge his iPhone, after that supercharger stopped to work with my phone. It charge it like normal slow charger, and dont have a clue what to do to restore it. Theres no fastcharge option in settings or anything to disable supercharging on phone. What i can do? Anyone have solution?
Sent from my VKY-L29 using Tapatalk
Anyone?
Sent from my VKY-L29 using Tapatalk
Buy a new charger? They are cheap on eBay.
need wipe cache partition will be work super charging
Thank you so much Gamkutopolowk. it does work for me.
I encounter same issue, I used different charger, when i used the huawei p10 supercharger, it doesnt work anymore. it took several hours to be fully charged.
here's what i did.
I just wipe cache partition, and voila good as new, back to supercharger.
how to wipe cache partition huawei p10? turned off the phone, hold up volume and power for around 10 secs. huawei logo will appear, continue pressing until emui appear. then, browse to wipe cache partition using volume down, then select using power button.
Hope this help. Thank you guys. :good::angel:
Good to know your problem it's solved.
Super charging issue
Its not the charger or cable just clean out your usb C port and cable ports and also the charger port once and voila its resolved. Ive had the same issue the reason was the dirt in the connectors
I have an ASUS ZenFone Max Pro (X00T/X00TD)
It is/was discharged and powered off. When i plug it in for charging, it is cycling in start of chaging:
1. vibration
2. the icon of empty battery
3. The bootloader is unlocked... text
4. the icon of empty battery
5. empty screen
1. and then starts again from vibration
I tried to clean the phone's connector, even wiped and stracthed the connector a littlebit, and changed cable, charging source. (One cable is in the 1A charger, another cable is connected to PC.) It doesn't get better.
I tried to leave it in the cycling, i hoped it gets some power.
Does the phone charge always when connected to power, or it just start the charging process after it shows the charging animation (which i don't reach)?
I tried to step in Fastboot mode. It stays in this mode, no cycling.
Does the phone charge in fastboot mode?
I tried to step in Recovery mode.
1. vibration
2. powered by android
3. The bootloader is unlocked... text
4. powered by android
5. empty screen and turns off
In fastboot mode i tried to flash stock recovery, and also TWRP recovery. The flashing process works, but i still cannot get in recovery mode, to see something more, maybe about battery or i dont know.
Of course the phone does not turn on. The same as when i try to get in recovery mode.
1. vibration
2. powered by android
3. The bootloader is unlocked... text
4. powered by android
5. empty screen and turns off
I did not do anything special nowadays with the phone. Bootloader unlock and rooting was years ago, nor i did upgrade, so nothing special. I just used the phone, it discharged, and i'm in this state.
What can i do? Is it something with charging, or it has enough power after connected in fastboot mode, but the problem is something with the software?
Please help.
Was it discharged until it turned off or left more then a few weeks in a very low charge state?
Auto shutoff is about 5-6% of battery capacity.
If allowed to sit until it self discharges below 1% the battery's microprocessor will permanently disable the output to prevent a possible runaway thermal event from charging a depolarized LI cell(s).
blackhawk said:
Was it discharged until it turned off or left more then a few weeks in a very low charge state?
Click to expand...
Click to collapse
It discharged today morning, turned off (or maybe i turned it off, i don't remember), and about one hour later i tried to charge.
blackhawk said:
If allowed to sit until it self discharges below 1% the battery's microprocessor will permanently disable the output to prevent a possible runaway thermal event from charging a depolarized LI cell(s).
Click to expand...
Click to collapse
Does it mean really permanently, without any possibility of get it back?
One more thing: maybe i "pressed" the buttons randomly in my pocket. Is it possible that in an unlucky situation i got into the recovery mode and pressed something away in recovery menu?
Even if discharge to the 6% cutoff you have at least a few weeks in cool temps until permanent auto shutdown.
It is permanent. If disassembled you could bypass the controller and attempt to charge.
Once the cell voltage reaches the controller threshold (if it takes a charge) it would function as before. Generally this is impractical to do.
If the cell has completely dipolarize it may not charge and will simply overheat with a potential thermal runaway if not manually disconnected.
Inspect port for debris, clean if needed.
Try a -known- good charger/wall socket and cable.
Normally phones will take a charge regardless of their power on/off state.
Otherwise the port, battery or the internal phone power control circuit may have failed.
A cable, charger, port failure are the most common causes though.
Best to use a 3 foot long cable; longer ones can cause charging issues.
blackhawk said:
Even if discharge to the 6% cutoff you have at least a few weeks in cool temps until permanent auto shutdown.
It is permanent.
Click to expand...
Click to collapse
It was definitely not a few weeks.
blackhawk said:
Inspect port for debris, clean if needed.
Click to expand...
Click to collapse
Sure, this was the first thing i checked. I also tried to carefully scratch off the possible oxid/dirt layer with a paper clip's end.
blackhawk said:
Normally phones will take a charge regardless of their power on/off state.
Otherwise the port, battery or the internal phone power control circuit may have failed.
A cable, charger, port failure are the most common causes though.
Best to use a 3 foot long cable; longer ones can cause charging issues.
Click to expand...
Click to collapse
So should i try to leave it in the cycle? Or better leave it in the fastboot state?
Hm. But i tried to charge in fastboot state for a few hours.
I don't understand.
blackhawk said:
Otherwise the port, battery or the internal phone power control circuit may have failed.
Click to expand...
Click to collapse
Yesterday with a third charger everything was fine. And this charger was fine, last time i used it two weeks ago. I tried to charge in my car now - the same cycling of starting to charge.
Okay, so i keep trying to charge, if you don't have better ideas.
But why does not it go into recovery mode? Maybe i could inspect the things more in recovery mode.
Thank you very much for your detailed answers.
If the battery is nearly fully discharged ie >5-6% and not recieving enough current or voltage from the cable, it will not power up even to its boot menu.
blackhawk said:
If the battery is nearly fully discharged ie >5-6% and not recieving enough current or voltage from the cable, it will not power up even to its boot menu.
Click to expand...
Click to collapse
But it should start to charge without cycling, and show the charging animation, right?
Edit #1: Ah, you mean, IF enough current. And if three different charger and cable was not enough for it, then probably the connector damaged. But i don't know how and why.
Edit #2: No, you mean this for booting up. But charging should start normally without the cycling.
trob83 said:
But it should start to charge without cycling, and show the charging animation, right?
Edit #1: Ah, you mean, IF enough current. And if three different charger and cable was not enough for it, then probably the connector damaged. But i don't know how and why.
Edit #2: No, you mean this for booting up. But charging should start normally without the cycling.
Click to expand...
Click to collapse
Your first concern is getting the battery to at least 60%
That's why you use a known good wall socket, cable and charger; a process of elimination.
I've had 2 bad power cables in a row before; more bad cables, etc. doesn't help.
For the boot issues someone here will hopefully recognize your problem if it persists.
blackhawk said:
I've had 2 bad power cables in a row before; more bad cables, etc. doesn't help.
Click to expand...
Click to collapse
Yes, i threw out a bad cable last week. But these 3 cables were good, there is not a big chance that all of them get wrong suddenly and at the same time, i think. I would be happy, because this would be the most easy solution for my problem.
In fastboot the red/green LED is dark, even if the cable is plugged in. Is this LED controlled directly also by the charging controller? Or does not the dark LED show anything, because it controlled by software, what does not run now, while the charging still work?
Or maybe both of charging start cycling and fastboot are use power of battery, while they don't charging it, so power is only getting lower? (Although you said the opposite, as phone is charging, not matter of the power state.)
Could be a bad batch if all are the same brand.
That's why you use a >known< good cable etc.
Don't have that phone so can't say how it behaves.
If it's below 5% power it won't do anything except maybe try to boot maybe not even that. Plus each attempt drains the battery more towards that critical 1% auto disable in the Li pack.
Killing the battery won't help your cause...
blackhawk said:
That's why you use a >known< good cable etc.
Click to expand...
Click to collapse
Okay, i try.
Thank you very much for your help.
Is it possible to turn off the charging screen, charging vibration, screen turning on from fastboot mode? Maybe flash something on or similar?
Because then it won't use the slowly chagring power.
So the screen is active abnormally when it's charging?
Is it stuck in a boot loop?
I know zero about rooting and firmware flashing.
Eventually someone here with that knowledge will step up... be patient.
blackhawk said:
So the screen is active abnormally when it's charging?
Is it stuck in a boot loop?
Click to expand...
Click to collapse
1. I plug the cable in.
2. It recognize there is power, so vibrates a littlebit, then starts to charge OR starts to start to charge - it would be in important thing to know which.
3. It shows the big battery icon at the center of the screen.
4. It notices its boot loader is unlocked, so it warns me - i can pause the phone for one minute in this step.
5. It shows the big battery icon at the center of the screen for a second.
6. But i think it feels its battery is too low, so it turns itself off, even from the charging process.
2. Then it feels the power again, so the cycle starts again and again...
In step 2., if i would know it is already charging itself, then i played with it, i pause every time for a minute, and everytime the battery gets a little more power. Because every vibrate and starting charging take a littlebit power from the battery i think.
So, for example, in every unpaused charge cycle (about 10 seconds) it gets 5 mAh, but uses 7mAh from the battery, then it get worse and worse. But if i pause it for a minute, it gets 30mAh, uses 7mAh, then every minute it gets 23mAh more, so this game eventually worths.
But, if in step 2. it does not start to charge itself, just later, after the "unlocked" text, then playing with this does not help, worse, take the battery lower and lower.
But: if i could disable the charging screen and the vibration, then it won't use the power just for showing to me it charges. And maybe the screen is the one who use the power and makes the controller feel low power from battery/cable.
Or, maybe, charging is already disabled, so no matter what i do, it does not help, and the only solution is to take apart and charge the battery directly.
I just put
blackhawk said:
Eventually someone here with that knowledge will step up... be patient.
Click to expand...
Click to collapse
Okay i try to be patient.
Good news!
This gets the voltage of the battery:
Code:
fastboot getvar battery-voltage
It says it's 4,32 V. If i remember right, this is around a fully charged battery. So probably it charged up when i left in Fastboot state for some hours. And the cycle/loop meant not that it cannot charge, but rather it does not need to charge.
Bad news!
Then what the heck is with my phone?
Summary:
1. My phone is fully charged.
2. It does not boot into normal.
3. It does not boot into recovery, nor by hardware keys, nor by command from fastboot. I tried to flash TWRP, RedWolf and the original recovery too.
4. Fastboot mode works normally.
Believe it or not...
The solution was very stupid.
I cleaned the phone inside, especially the bottom part. Around the connectors, lot of dirt and drying moisture got in. Just enough for - probably - some short circuit.
I don't know why was it okay for fastboot mode, and not okay for recovery and normal boot.
Blackhawk, Thank you soooooo much for your help and your time. I learned a lot from you now.
Excellent.
Guess it was getting mixed signals...