Related
I thought I'd clean up the OP for folks who got here with similar issues as me since it seems more common than we'd like.
Scenario:
Phone does not turn on without the charger or USB plugged in.
When plugged in, it boot loops at the Google logo (i.e. turns off at the logo, and reboots) and gives what is beginning to be referred to as the the 'red LED of death'--where the LED just blinks read.
The bootloader is accessible when plugged in. But trying to boot into recovery causes a loop. If you try to enter recovery, the phone has to turn off then boot back into recovery. But turning off means that when it turns on it will loop at the Google logo. So, booting into recovery is NOT an option.
Download mode is also accessible when plugged in.
Since the bootloader is accessible, it is possible to flash the factory image to the phone, however, doing so does not resolve the boot loop, nor does it allow the phone to turn on without being plugged in.
Fixes which have worked for some people
Instructions in this post worked for a couple people. NOTE: you have to be able to get into the bootloader for this to work.
One person who left it in download mode plugged into the PC (which was off) overnight, and somehow the problem was resolved. Thread here.
Here's a post in this thread from a user who was able to get it booting up again by leaving it on the charger for a bit.
You fool.
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: http://forum.xda-developers.com/showthread.php?t=2010312
overhauling said:
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: [/QUOTE]
Yeah, it would be nice if...en if I get into the bootloader for a second.
Click to expand...
Click to collapse
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
ntt1409 said:
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
Click to expand...
Click to collapse
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Ulver said:
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, but it's already full charged. Even if I leave it on the charger for a while, it still doesn't start up
KonstantinKeller said:
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would say try this to drain the battery. Then charge it and see what happens.
So how exactly did the phone brick? Just so everyone here knows what not to do. Is it the kernel that caused it since its still in experimental stages?
Sent from my Nexus 4 using xda premium
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Have you tried reflashibg or using your nan droid back up from the recovery console?
Just because our won't not does not mean it is bricked.
It is really ticking me of that many people do not even have our phones and you are exchanging because of ignorance. Surely all these exchanges must impact stock. I know they keep extras but how many?
Stop messing with things you know nothing about until you at least learn..
sent via xda premium with nexus 7
abnormalreply said:
Yeah, it would be nice if I could get into the bootloader :/
But as I mentioned, it 'thinks' the battery is dead so it just keeps turning on and off even if I get into the bootloader for a second.
Click to expand...
Click to collapse
That's the point. It'll turn on and off until the battery is ACTUALLY dead. Then, charge it fully, and try to start it.
Dude this happened to me last night! Same ROM kernel combo! And fired up an tutu after ocing point is this should not be happening just made a thread and seen this here! Freaky! I'm telling u people beware something is up for sure been doing this a long time never seen this before
First if you have an unlocked bootloader, your replacement won't be free. As soon as Google gets it and realizes it's unlocked they will charge you full price for your replacement.
Second, Nexus devices are next to impossible to brick. There is probably a way to reset the device. I would try first unplug the device from your computer or charger and try holding the power button for a full 15-20 seconds. Then try booting into bootloader or recovery. If that doesn't work, try holding volume up and power for 15-20 seconds. If that doesn't work, try volume down and power for 15-20 seconds. And if that one doesn't work try holding all 3 down for 15-20 seconds. This sounds like a problem that would more than likely be fixed by removing the battery and rebooting. Since this doesn't have a removable battery there has to be a built in 'hard reset' that will power cycle the phone.
I am willing to bet there is a way to get this working. I guarantee if I had it here in front of me I could.
Also, like someone else has said before, if you are a not good at diagnosing problems, troubleshooting problems, fixing this kind of stuff on your own and adb/fastboot, it makes no sense to be using experimental software on your device. Especially if you plan on pushing its boundaries by overclocking and running benchmark software. If I were you, after you get this straightened out, wait a while until stuff is more ppolished and tested better.
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Yo hold power down then plug USB in then right after hold all three button .like after u plus in USB while holding power button then at same time hold volume buttons also this is how I got into download mode.....but.....phone was not detected and comp SD there was a driver failure. But yes dude phone was charged. And I had same exact combo as u I mean same exact. This is why it is freaky. Aokp was fine all day then when I flashed faux test kernel and fired up antutu I just had a flash then nothing. Not blaming anyone of course it was me who chose to flash after all this is custom software and I love these guys work just wish I knew what did it ....like what actually did it
Richieboy67 said:
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Click to expand...
Click to collapse
Seriously... thousands of people waiting for the phone to become available, and people who deserve to have their phone bricked are getting 2nds for free.
abnormalreply said:
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Click to expand...
Click to collapse
I was able to do the same thing but it would vibrate then see Google for a sec then nothing and back to a blinking red light....dude this is crazy I can't. Believe this happened to another person the same exact way
dammit. And I was just going to try this combo. Guess that's gonna be a no go.
Last ditch effort is to unscrew the two t5 screws at the bottom and do a real battery pull. Probably wont work, but what do you have to lose?
Ok so I was running paranoid android 3.99 and I've been getting the OTA notices that I need to update. I did that just today, and it downloaded the update and apparently installed it. Then I was stuck in recovery (reboot just kept sending it back to recovery). So I did some googling, decided I should not have tried to OTA and decided I should try to go back to stock and properly flash the rom.
This was my first attempt going back to stock. I downloaded what I thought was the correct nakasi file for my 2012 Nexus 7 (Wifi only, grouper I believe). I got adb and fastboot installed and started sending the prompts. It appears 'fastboot flash bootloader bootloader-grouper-4.23.img" worked properly, but when I tried "fastboot -w update image-nakasi-jwr66v.zip" I got an error and the tablet just kept rebooting into recovery; it would not load past the "Google" screen.
So I put the tablet down (with 98% charge), took my kid to baseball practice and came back an hour later to work on it. The tablet had turned off. Now it appears dead. It does not show a charge symbol when plugged in, and will not power on with "power" or "power and down button." As a result, adb/fastboot does not recognize it.
I thought I had soft bricked it, but now I'm scared I might have hard bricked it. It looks like maybe I installed the wrong nakasi file (the one I installed ended in "v," but the one I just saw from Google ends in "y").
I will try letting it charge overnight and seeing if it will boot in the morning. In the meantime, any ideas, or should I just consider this brick a sign that I should upgrade to the new Nexus (and be more careful)?
Where did you get the stock image? All the official one can be downloaded from here: https://developers.google.com/android/nexus/images#nakasi
If you can boot into bootloader, you can flash the proper image with fastboot, of not, then your device is hardbricked.
If you are worried about a flat battery then you can check it with a voltmeter the voltage should be between 3.6 and 3.7 if the tablet won't charge the battery you could manually charge it THIS IS DANGEROUS the n7 regulates the voltage and current to the battery but if you uses 500mA charger and tape the wires onto the battery and only give it about 30 mins you should be ok . Check the temp of the battery as you do this if it starts to get hot unplug wait for it to cool and go again.
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Thanks for responding. I charged it overnight, to no avail. I don't think it was hard-bricked, but probably is now that it shutdown and won't recharge or boot.
I unfortunately did not get the file from this site or google, as I should have. I got it from another site I have used before, which was linked to a youtube video on how to return to stock. I thought I followed it exactly, but maybe not.
there is one final thing I'm thinking. when I plug it in to my computer, I am getting the "ding-dong" sound like it's connected. Still, adb/fastboot don't appear to be picking it up. Anything i can do to get it recognized?
It doesn't sound good try plugging it in and holding in the power button for one minute use your watch it can take anything over 30 second's that works on a fully functioning n7 with a completely flat battery to get it to charge not sure if it will work on yours. A bricked device should have the same characteristics as a brick if your computer detects something well a brick can't do that otherwise back to my suggestion of manual charging
Sent from my C5303 using xda app-developers app
You may be in what is called APX mode. Sounds like you might have overwritten the bootloader with the wrong image, which usually means bad news, especially if you can't get into fast-boot mode to write over the image.
Unless it's still under warranty, you can't do much. I had this same problem when I attempted to upgrade to Kit Kat. Not sure what happened, but my tablet was hosed and it only shows up as an APX device. Luckily, it was still under warranty and I was able to RMA it with Asus and they replaced the motherboard free of charge. My purchase date happened to be 11 months prior, so I had about a month left on my warranty. Got lucky.
Try what is suggested in this post: http://forum.xda-developers.com/showpost.php?p=30002160&postcount=10
It might help, it might not. Some have reported trying for a few hours eventually helped get it out of APX mode, but I tried it with mine for days, and nothing helped.
Hi there,
My Note 4 started playing up 3 weeks ago, it started to lag, freeze and reboot. I managed to bring it back to function as my daily driver (handy as I didn't have another phone!) with the Wake Lock app. Sometimes when I'd try to boot it up, it would be glitchy and it would take a while to fire up again, most often I'd have to boot into TWRP and wipe the cache, but then it would be fine. The wake lock app was set to auto run and all was good, apart from a major hit in battery life.
Today I started to set up my replacement N910F (bought used). It too was running stock MM, I'd rooted this one too and installed xposed. All was going well until I went to remove the sd card from the first phone. When I went to reboot.....nothing.
I tried to remove the battery and hold down the power button and then try again. Nothing. Tried holding down the power button for a few minutes with the battery removed and then trying again. Nothing. I even tried holding it down for a couple of minutes, putting the battery in for 10 mins and then trying to power it up. Nothing.
It doesn't show up on my PC or with Odin. Nothing happens when I plug it into the charger. I've tried 3 different batteries. All with the same end result. Nothing. :crying:
Is there ANYTHING I can do?
woldranger said:
Hi there,
My Note 4 started playing up 3 weeks ago, it started to lag, freeze and reboot. I managed to bring it back to function as my daily driver (handy as I didn't have another phone!) with the Wake Lock app. Sometimes when I'd try to boot it up, it would be glitchy and it would take a while to fire up again, most often I'd have to boot into TWRP and wipe the cache, but then it would be fine. The wake lock app was set to auto run and all was good, apart from a major hit in battery life.
Today I started to set up my replacement N910F (bought used). It too was running stock MM, I'd rooted this one too and installed xposed. All was going well until I went to remove the sd card from the first phone. When I went to reboot.....nothing.
I tried to remove the battery and hold down the power button and then try again. Nothing. Tried holding down the power button for a few minutes with the battery removed and then trying again. Nothing. I even tried holding it down for a couple of minutes, putting the battery in for 10 mins and then trying to power it up. Nothing.
It doesn't show up on my PC or with Odin. Nothing happens when I plug it into the charger. I've tried 3 different batteries. All with the same end result. Nothing. :crying:
Is there ANYTHING I can do?
Click to expand...
Click to collapse
Could be battery is dead or your device is hard bricked.
You might wanna see link below to unbrick method
http://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
Trex888 said:
Could be battery is dead or your device is hard bricked.
You might wanna see link below to unbrick method
http://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
Click to expand...
Click to collapse
It's not the battery as I've tried the 3 that were working with the phone originally, and I've just tried the one form the "new" phone.
After looking through the link, that doesn't look like an option - the phone needs to be detected by the pc. Mine was connecting fine earlier, so I know it's not a lack of drivers. I makes a noise when plugged in, but then isn't shown.
woldranger said:
It's not the battery as I've tried the 3 that were working with the phone originally, and I've just tried the one form the "new" phone.
After looking through the link, that doesn't look like an option - the phone needs to be detected by the pc. Mine was connecting fine earlier, so I know it's not a lack of drivers. I makes a noise when plugged in, but then isn't shown.
Click to expand...
Click to collapse
It should be detected in device manager under ports section.
If the pc makes a sound when the device is connected, that means the device is fine. You can try the debrick method given on my thread.
Try it and report.
Reporting Via N910G
Don't ask me how but.....it suddenly came to life this morning! I put a battery in it and tried to go into recovery, and voila! No rhymne nor reason to it but she's up and running for the mo!
Thanks for the suggestion yashthemw but thankfully I've not had to try it!
Hei
I have problem with my moto g 4 plus mobile.As yesterday night i was working fine when i awake up the mobile was off.
I try to reset but nothing happened then i recharge it again with orignal charger nothing happened.
Then i remove the battery and plus it again but the same problem came white light start to blink again near to touch button.
White light only blink while charging.
Kindly any solution.
Sent from my iPhone using Tapatalk
What did you do to 'reset'?
When I've had similar issues, I've held the power and volume up buttons for over a minute and eventually it turned on. If not, then volume down and power for over a minute. If you haven't, try that with and without the charger plugged in.
samipaswaal said:
Hei
I have problem with my moto g 4 plus mobile.As yesterday night i was working fine when i awake up the mobile was off.
I try to reset but nothing happened then i recharge it again with orignal charger nothing happened.
Then i remove the battery and plus it again but the same problem came white light start to blink again near to touch button.
White light only blink while charging.
Kindly any solution.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
samipaswaal said:
Hei
I have problem with my moto g 4 plus mobile.As yesterday night i was working fine when i awake up the mobile was off.
I try to reset but nothing happened then i recharge it again with orignal charger nothing happened.
Then i remove the battery and plus it again but the same problem came white light start to blink again near to touch button.
White light only blink while charging.
Kindly any solution.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Have you try volume up+down+power button at the same time your device is booted into fastboot mode the control to switch off your phone done..... Ok??
7418988214 said:
Have you try volume up+down+power button at the same time your device is booted into fastboot mode the control to switch off your phone done..... Ok[emoji2][emoji39]
Click to expand...
Click to collapse
Yes i also tried this but this method also did not work.
Sent from my iPhone using Tapatalk
eekreek said:
What did you do to 'reset'?
When I've had similar issues, I've held the power and volume up buttons for over a minute and eventually it turned on. If not, then volume down and power for over a minute. If you haven't, try that with and without the charger plugged in.
Click to expand...
Click to collapse
I did both method with charger and without charger but nothing is happening any other solution.
Sent from my iPhone using Tapatalk
Mine does this all the time if I let it die you gotta have the oem charger if I recall correctly wish I could find the post about it I wanna say with oem charger you hold vol up or down try either while you plug it in and if you get the charging graphic you wanna then leave it charging for a while then retry the power button it's stuck in some sort of Sahara type mode from what I could see when that happens...let us have a bit more detail when it's plugged in do you see the charging graphics at all? If not and only seeing the LED light I'd bet it's in the mode others have mentioned here if you do then I am not certain but other times I had same prob just left it on charge for couple hours then it finally booted.
Sent from my Moto G4 using Tapatalk
I think your phone is bricked
siddhesh9146 said:
I think your phone is bricked
Click to expand...
Click to collapse
Please read the linked thread .
KinslayerDeth said:
Please read the linked thread .
Click to expand...
Click to collapse
What linked thread are you referring to?
samipaswaal said:
Hei
I have problem with my moto g 4 plus mobile.As yesterday night i was working fine when i awake up the mobile was off.
I try to reset but nothing happened then i recharge it again with orignal charger nothing happened.
Then i remove the battery and plus it again but the same problem came white light start to blink again near to touch button.
White light only blink while charging.
Kindly any solution.
Click to expand...
Click to collapse
You must have hard Bricked your device happened to me once . See this video on YouTube -
Or refer to the ultimate hard bricking guide - https://forum.xda-developers.com/mo...4-plus-hardbrick-solved-guide-t3657761/page29
Hope this helps you
I am facing similar problem with my G4 Plus. The difference is that my phone kept on hanging while doing normal tasks and then it used to restart. The weird thing was that while the phone booted up, there this boot animation where a person is doing flips there my phone used to hang and then it restarts. Only after that it used to completely boot up. But after 10-15 mins of usage it used to hang and restart.
One more weird thing that used to happen is that with every restart the battery used to drain drastically.
Then finally the phone died. And while charging the white led kept on blinking.
I took my phone for repair and even they were not able to figure out the problem. They replaced the battery but still the same issue. At the end they said that the problem is with motherboard and needed to be replaced.
Now I'm using Honor 7X but I still have my G4 Plus with me.
If anyone was able to boot up his device then please do reply on this thread.
RishabhZR said:
I am facing similar problem with my G4 Plus. The difference is that my phone kept on hanging while doing normal tasks and then it used to restart. The weird thing was that while the phone booted up, there this boot animation where a person is doing flips there my phone used to hang and then it restarts. Only after that it used to completely boot up. But after 10-15 mins of usage it used to hang and restart.
One more weird thing that used to happen is that with every restart the battery used to drain drastically.
Then finally the phone died. And while charging the white led kept on blinking.
I took my phone for repair and even they were not able to figure out the problem. They replaced the battery but still the same issue. At the end they said that the problem is with motherboard and needed to be replaced.
Now I'm using Honor 7X but I still have my G4 Plus with me.
If anyone was able to boot up his device then please do reply on this thread.
Click to expand...
Click to collapse
Hmm, have you tried a firmware re-flash? Here's a stock firmware that should work on XT1643 devices - https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock the bootloader if you do not wish to (skip the OEM lock begin and OEM lock commands). I would recommend a full device wipe though (using the 'fastboot erase userdata' command) unless there's crucial data you still want to try to save on your G4 Plus. A full wipe however with the full flash should help us troubleshoot.
However, if a firmware flash doesn't work, then it does start to suggest there is a hardware issue. Do you experience reboots if booted to the bootloader or the recovery?
Also, do you recall if the hangs were random or were in a particular app or with a particular task?
echo92 said:
Hmm, have you tried a firmware re-flash? Here's a stock firmware that should work on XT1643 devices - https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock the bootloader if you do not wish to (skip the OEM lock begin and OEM lock commands). I would recommend a full device wipe though (using the 'fastboot erase userdata' command) unless there's crucial data you still want to try to save on your G4 Plus. A full wipe however with the full flash should help us troubleshoot.
However, if a firmware flash doesn't work, then it does start to suggest there is a hardware issue. Do you experience reboots if booted to the bootloader or the recovery?
Also, do you recall if the hangs were random or were in a particular app or with a particular task?
Click to expand...
Click to collapse
I tried to boot my device to fastboot after one and half month, as I was busy with my exams, and fortunately today it booted (Earlier it was not at all booting). But the hang and reboot problem still persists. So, now I'll try to re-flash the firmware and then I'll update about the status.
Currently my device is running on December Patch Firmware.
No, till now no reboots in bootloader and recovery. And yes, I forgot to mention, my recovery is stock. In December I went back to stock from rooted. But the bootloader was not locking. It still has that warning at the starting of boot process.
The reboots were random, it still are. The device is rebooting within 5 minutes of reboot.
RishabhZR said:
I tried to boot my device to fastboot after one and half month, as I was busy with my exams, and fortunately today it booted (Earlier it was not at all booting). But the hang and reboot problem still persists. So, now I'll try to re-flash the firmware and then I'll update about the status.
Currently my device is running on December Patch Firmware.
No, till now no reboots in bootloader and recovery. And yes, I forgot to mention, my recovery is stock. In December I went back to stock from rooted. But the bootloader was not locking. It still has that warning at the starting of boot process.
The reboots were random, it still are. The device is rebooting within 5 minutes of reboot.
Click to expand...
Click to collapse
Update on situation:
Even before I could try anything the phone battery died due to hanging and restarting and again the same thing, the phone is not at all booting up. I've tried the key combinations still it's not working.
Just you need to take and reinsert the battery strip to the board cause its non removable battery ..this worked for many ...may be will help you too
@ sanjay sahu said:
Just you need to take and reinsert the battery strip to the board cause its non removable battery ..this worked for many ...may be will help you too
Click to expand...
Click to collapse
Sorry for late reply, I did tried it and also tried to replace the battery but it didn't boot up. So I took my phone to Service Centre where they kept the phone for 2 days and returned the phone saying that the problem is with the motherboard and it has to be replaced.
Hi,
I have a problem with my G4+.
The screen looks black even when turned on however when I shine a torch on the screen I can vaguely see the graphics but not enough to do anything with the phone.
My son suggests a problem with the back light. Is this a known fault and can it be fixed or is it a case of a new phone.
Thanks for any suggestions,
Martin
i got solution
the problem is a flex, it is the one that contains the camera's flash, that flex has a small resistance, when it dies the phone stops charging, your phone is not briqueado just does not charge. replace that flex and the phone charging again
7418988214 said:
Have you try volume up+down+power button at the same time your device is booted into fastboot mode the control to switch off your phone done..... Ok
Click to expand...
Click to collapse
I am facing similar issue with G4 plus. phone's battery was low to about 13%, and was heating up in charging, so i thought to switch it off for faster charging. but its not booting up back after that. white led near fingerprint sensor keeps blinking when i put it to charge. i read this thread and tried the methods of holding power button, or power+volume up, or power+volume down, or power+volume up+volume down. but nothing works. i did all with and without charging. tried all these last night and this morning as well. meanwhile i left the phone in charge over night, for approx 8 hours. no charging screen, not booting up. now what ??
It's the battery.
Go to your nearby Motorola service center and either get your battery replaced, or ask them to boost your battery (if it works you'll save money.)
I discontinued using my X Compact in mid-2020 when I got a new Pixel 4a. It's been sitting in a drawer since. It was rooted but working fine.
Recently I pulled it out to try charging it up to use as a spare. What I found was, upon plugging it in to charge, I'd get the "Your devices has been unlocked and can't be trusted" splash screen, then after the 5 seconds it would vibrate and bootloop back into the same screen, etc. I tried booting into recovery with power button / volume down and got only a blank screen. I booted it into fastboot with power button / volume up and left it to charge in that state.
Today I got all the drivers set up on my laptop and was able to access fastboot. I tried installing two different versions of TWRP for kugo (twrp-3.3.1-0-kugo and twrp-3.6.2_9-0-kugo). In both cases, subsequently attempting to boot into recovery, I got the SONY screen followed by the TWRP splash screen and then... hang.
Certainly seems like something got corrupted in there. Should I just call it a brick and leave it alone, or are there any further bright ideas on what to try?
Is the battery good? It may not be able to sink enough current otherwise.
blackhawk said:
Is the battery good? It may not be able to sink enough current otherwise.
Click to expand...
Click to collapse
Hard to judge in this state, but if I immediately plug it into charge after launching recovery mode, it still hangs.