The skinny:
So I dropped my phone and shattered the glass, rendering the touchscreen useless. After replacing the screen/digitizer, the phone will no longer boot. I made the mistake of not keeping the phone completely charged prior to the screen replacement, and now I fear the battery has reached a point where it will not take a charge (question following...)
The details:
Prior to the fall, I was running CM13.
Because the battery was not charged, it will only power on while plugged in.
While plugged in, the white LED will continue to blink - and nothing else, (dark, empty, black screen of nothing.) I left it sit here over night, thinking (hoping?) the battery would charge and would be able to boot or at least get into recovery.
I can get into the bootloader by holding Vol-Down before inserting the cable.
While in the bootloader, I get the message (in red) Battery low (Charging) when plugged into the wall, or (in green) Battery OK (Charging) when plugged into the computer (using moto factory USB cable...)
I am able to fastboot flash. I successfully flashed CLARK_RETUS_MPH24.49-18_18, hoping a factory image would trigger -- something.
From the bootloader, if I select anything (except for Bar Codes, which actually shows the correct bar codes,) the screen freezes and the white LED will start blinking in the same manner as it does powering on, outside of the bootloader - No recovery, no boot to system.
I've tried first erasing recovery and then reinstalling (both TWRP and factory,) but this did not result in any change in behavior.
After re-flashing all of the stock 24.49-18_18 image, it did restore the white 'Unlocked bootloader!!!' warning screen (when selecting Factory Mode from the bootloader,) so I'm confident the fastboot flashes were successful.
So, everything should be fine, but it's not, leading me to believe the battery is hosed. My question(s) for anyone who is able and willing to possibly help, am I wrong in thinking the battery is shot? While in the bootloader and it says Battery OK (Charging) is it really charging? Is there another way to test/verify the status of the battery outside of bootloader? Is there another way of getting a charge to the battery?
Or am I completely off track and it's something else entirely?
I appreciate any and all help! Thank you!
Oh, Bootloader info (whether it's useful or not...):
Code:
AP Fastboot Flash Mode (Secure)
Baseband: M8992_1255331.29.01.88.02R SUPER_NA
Product/Variant: clark XT1575 16GB P3C
Serial Number: [...]
CPU: MSM8992
eMMC: 16GB Samsung RV=07 PV=01 TV=57 PN=AGND3R
DRAM: 3072MB SK Hynix S8 SDRAM DIE=6G M5=x6 M6=x3 M7=x0 M8=x3B
Console [NULL]: null
Battery OK (Charging)
Device is UNLOCKED. Status Code: 3
Software status: Modified
Transfer Mode: USB Connected
Good Afternoon,
Did you ever find a solution to your problem? I am experiencing the same issue, although I can't even get the phone to power to the boot loader. The LED flashes once when plugged into the wall and doesn't flash at all when plugged into the laptop.
Thank You,
Justin
Related
Hi, i have i tilapia 32 gb with latest bootloader and i used it during the last 2 year with a slimkat rom.
Now almost everytime it won't turn on normally. The screen is black ,i can't get into recovery or bootloader and charging the battery does nothing.
If i connect it to a pc ,first it shows apx mode on device manager, then if keep pushing the power button many times sometimes it starts and i can access to bootloader and recovery.
I wiped everything,flashed twrp again,tried other roms but almost everytime it won't turn on normally even if the battery is fully charged.
Do you think it is 100% a motherboard problem?
Is there some chance that replacing the old battery(i never changed the original one) will solve this problem? thanks
Most likely storage finaly died so you are out of luck
after battery empty, phone boot only in "fastmode" even no in "recovery"
Hello all,
I gave my son my "old oneplus2".
The device was root with last OS with twrp.
Here the situation, my 10 old son don't learn , i'm always tell him to charge any devices when close to 10%.
Well, few day ago, the phone power off itself (0% battery) then nothing.
no charging light, boot only in fastboot, no recovery mode either, i precise that the fastboot (logo) mode appear even when press only power button.
i got the original partitions, i don't know if it can help.
i can't do anything, i tried lot of tutos without success.
The phone rebooted by it self, no firmwareupdate going on, just random reboot.
Got stuck on redmi logo.
Could reboot and get fastboot, but could not flash original fastboot rom, got errors. a normal reboot gave only redmi logo.
Now the phone is out of power, not taking charge, not powering on.
Anyone have any solution for this problem? Or any tips? The phone is stone dead
Not sure if this will help...
here's my random reboot thread and fix
Well, i have no simcards or sd-cards inserted.
And its not charging or turning on. volume up and down + power is not making any results.
The weird thing is that it said "redmi" on the display for about 24 hours draining the power, and after it died out of power i'm unable to do anything with it. its basically a brick.
This happened totally random. just a spontaneous reboot into a never ending redmilogo.
During redmilogo i had the posibility to get it into fastboot by rebooting it, but mi flash would not accept the phone. so another reboot into regular boot ended in infinite redmilogo again :|
Your phone's bootloader unlocked?
Nope
Did you try keeping it charged for a while? Device might not show any sign (charging indication) but the battery will get charged eventually (I guess).
Charge it well and try to SIDELOAD that FASTBOOT IMAGE via PC..
It loooks like its bricked all by itself. i left it in charger for days.
I got contact with the phone with mi flash, but it has gone into some authentication mode with the flashing, so i'm not possible to reflash rom without authorization.
Read about this on reddit, and it seems like a dealer has to look at it.
Hello friends, I have a pretty specific issue with my Mi A1. My phone suddenly stopped booting and doesn't launch. No matter which buttons I press. When I connect the charger, the blue LED starts blinking and it keeps blinking as long as the charging cable is connected.
I looked at previous forum posts and tried all the solutions but none of them worked for me. However, when I connect the phone to a computer, I get the Qualcomm 9008 mode and when I try to flash a fastboot ROM using MiFlash it actually flashes normally and shows "Success".
Since the phone is able to flash a ROM normally, could this be a faulty LCD screen? Or is this an issue with a faulty motherboard or something else?
if it shows 9008 then its in edl mode when u flash the rom press power on button for 10 to 15 seconds for booting it. and if it won't boot then i think its some kind of hardware issue
I have an S5 with stock Samsung ROM which I rooted some years ago with Magisk and TWRP recovery. For the last few years it has only been used as an alarm clock and I have forgotten how I set it all up in the first place, in fact I had forgotten that I ever rooted it. Up until now it has been working fine but I wanted to give it to my 9 year old daughter to use, so I did a factory reset on it through the normal Android menu. After that the phone works but will only charge in Recovery, not when its off or when its booted normally. Same cable and charger that I have been using up until now and I also tried others but didn't make any difference.
When the phone is off and I plug in the charger,it vibrates, the battery symbol comes up for a second and it displays the message "set warranty bit: kernel" then the screen goes off. The charging LED does not come on. Then after about 10 sec it does the same thing again: vibrate, battery symbol, message, screen off and just keeps going round that loop but never charges. When the phone is booted in normal mode it doesn't seem to detect the charger at all, nothing happens. In Recovery it charges perfectly but its a bit inconvenient!
I tried restoring the last TWRP backup that I had which seemed to contain all the partitions but it hasn't made any difference to the charging problem. It seems the phone has power and CAN charge but is deciding not to. Any ideas please how I can get it back into operation?
Model: SM-G901F
Android 6.0.1
Kernel 3.10.40-9709634
Build MMB29M.G901FXXU1CRH1
Magisk 19.3
Magisk Manager 7.3.4
Magisk version is old but I have not attempted to update it yet in case that makes the situation worse.
spencetj said:
I have an S5 with stock Samsung ROM which I rooted some years ago with Magisk and TWRP recovery. For the last few years it has only been used as an alarm clock and I have forgotten how I set it all up in the first place, in fact I had forgotten that I ever rooted it. Up until now it has been working fine but I wanted to give it to my 9 year old daughter to use, so I did a factory reset on it through the normal Android menu. After that the phone works but will only charge in Recovery, not when its off or when its booted normally. Same cable and charger that I have been using up until now and I also tried others but didn't make any difference.
When the phone is off and I plug in the charger,it vibrates, the battery symbol comes up for a second and it displays the message "set warranty bit: kernel" then the screen goes off. The charging LED does not come on. Then after about 10 sec it does the same thing again: vibrate, battery symbol, message, screen off and just keeps going round that loop but never charges. When the phone is booted in normal mode it doesn't seem to detect the charger at all, nothing happens. In Recovery it charges perfectly but its a bit inconvenient!
I tried restoring the last TWRP backup that I had which seemed to contain all the partitions but it hasn't made any difference to the charging problem. It seems the phone has power and CAN charge but is deciding not to. Any ideas please how I can get it back into operation?
Model: SM-G901F
Android 6.0.1
Kernel 3.10.40-9709634
Build MMB29M.G901FXXU1CRH1
Magisk 19.3
Magisk Manager 7.3.4
Magisk version is old but I have not attempted to update it yet in case that makes the situation worse.
Click to expand...
Click to collapse
Never mind, I got it working with a different charger. Very strange. The first charger works fine with my Huawei P20, maybe too high power for the S5? Although I thought the device only draws the power it needs even if the charger is capable of more.