Database Users

[Q] Phone will not charge, can't get past boot screen

I'm using donut with NAND. This morning my phone seemed to have drained the battery overnight, and was completely off. When I plug it in it in the charge light will not come on. The battery has enough juice to almost complete the boot, but always dies just as the lock screen comes up.
I've been trying to search for possible solutions. Some posts seem to say that it is normal for the phone not to charge while off or booting (thought I thought mine did), but I definitely have this now. One suggested going to the coke bootloader screen to charge. this does not work for me. I tied flashing back to WinMo, but my PC can't see the phone through usb. I also tried a hard reset. One suggestion said to have a Verizon store charge the battery. So I guess I'll try that next and report back.
Any help or confirmation that my phone is bricked and I should just give up, is appreciated!

try going into boot loader, you know power+camera+rest button, and let it charge in that for 5 min, then try and boot

Thanks for the suggestion. I did try that and it didn't seem to be working (I didn't see a charge indication led come on). Maybe it is charging and it just does not indicate it? I'll give it a try again. I'm just worried that if I completely drain the battery then I'll have no chance to start it up and charge at all.

nope that killed it alright. guess it wasn't charging after all. Guess my only hope now if Verizon, or finding another working vogue to charge it.
And it still makes me wonder if the not charging problem will remain. If I could only flash back to Winmo. Is there a way to do that without a usb link to the PC?

Flash back windows via sd
copy the nbh file of windows rom to the /sdcard
rename it to VOGUEIMG.nbh
press camera button
connect usb
4 color screen appears
release camera button
press power
restart
connect the phone to power source all the night
flash back android.

The charge light will not come on when in bootloader mode, but I assure you the phone will charge. I plugged it in and put it in bootloader mode for about 20 minutes, then was able to continue.
I had the EXACT same problem a few months ago.
NuAngel

In boot loader mode it doesn't charge, you need to flash windows and then reflash android.

l1q1d said:
In boot loader mode it doesn't charge, you need to flash windows and then reflash android.
Click to expand...
Click to collapse
Again, I've been through this myself. The light may not come on, but the battery DOES charge when in bootloader mode. Please do not misinform. The OP does not have to re-flash - and, in fact, it may be impossible to re-flash without a healthier charge to the battery.
NuAngel

Sure? I test it in polaris and in kaiser and it doesn't charge.
Probably vogue has a different power connection inside.
Good to know

l1q1d said:
Sure? I test it in polaris and in kaiser and it doesn't charge.
Probably vogue has a different power connection inside.
Good to know
Click to expand...
Click to collapse
i have done it too

In my case the phone was not charging in boot loader mode. I let it sit plugged in like that and it completely killed the factory battery as well as my extended one.
I went to Verizon but they said they didn't have a vogue phone anymore and so couldn't charge my battery.
I ordered one of these, but had to wait awhile to get it from Hong Kong. I just got it today and was able to charge my battery, but even after booting into android my phone will not charge the battery its self. I've tried with the AC cord, and usb which I know is a good cord. Maybe something in my phone got fried? I'll try going back to windows next.

My solution (which is using the same phone NuAngel more then likely had an issue with, since he gave it to me) was to go out and get a new battery charger. The chargers connector itself had become worn out. I was able to pickup a fantastic generic Touch/Touch Pro/Touch Pro2 charger at Walmart for $15 or so, Now the phone chargers fine (although it still touchy when flashing via USB).
In short, the USB port is really getting worn out on this thing, but I can still do data at times, even though its not getting a charge (via USB).. its odd at times.

So maybe that's my problem, the usb port has worn out. I can't seem to get a charge or data.
So now I'm having trouble flashing windows from the sd card. I tried to follow the above post:
l1q1d said:
Flash back windows via sd
copy the nbh file of windows rom to the /sdcard
rename it to VOGUEIMG.nbh
press camera button
connect usb
4 color screen appears
release camera button
press power
restart
connect the phone to power source all the night
flash back android.
Click to expand...
Click to collapse
and I found this in another post:
WnG88 said:
If you want to re-flash your nand back to wm, here is the instruction:
1. find your wm rom, it will be the RUU_Singed.nbh
2. copy the RUU_Signed.nbh to SD card as VOGUIMG.nbh, pull the battery, replace, press power and hold camera button and reset hole, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not be finding the VOGUIMG.nbh.
Even simpler:
- put the phone into boot loader mode (power + camera + reset pinhole, you should see the tricolor screen)
- plug into USB of computer
- Flash the windows mobile rom right from windows using whichever rom install file you want.
Click to expand...
Click to collapse
I downloaded NFSFAN's 6.5 in a rar file from here, opened it with 7zip, copied RUU_signed.nbh to the root of the sd card (FAT32), changed the name to VOGUEIMG.nbh .
I assume I can't use any of the instructions that involve the usb port, and I can't figure out if I am supposed to be doing something different with the button holds. I'm just holding power, reset, and camera at boot up to get to the boot loader screen right? After that screen pops up I get a quick flash to a white screen that says something like "Loading... File not found!" then back to the 4 color screen that says Serial.
Can anybody tell me what I'm doing wrong?
Thanks.

The nbh should be renamed to "VOGUIMG.nbh" not "VOGUEIMG.nbh"
However, I am not sure if it will actually help fix your problem.

Thanks for that correction. I was using VOGUEIMG.nbh, but sadly changing it to VOGUIMG.nbh did not seem to fix anything.
Now I found this thread which says to flash from sdcard
egzthunder1 said:
Your SD card has to be:
*Formatted for FAT32
*Be 2GB or less
*Not be SDHC
Simply do what you are doing (rename file and drop in the root of the SD card, put the device in bootloader, and the device takes care of the rest.... it should work.
Good luck!
Click to expand...
Click to collapse
My card is 2 GB so I assume it is not SDHC. The HC stands for High Capacity right? (not Host Controller which shows up in the properties for the card in windows)

I would plug the phone into a wall charger if you are going to use the SD card method. I haven't tired this method, but I would assume it would work best when not plugged in at all, and the battery is +50% charged.
If the phone doesn't have a valid image installed, you should automatically get the three screen on first startup, so there shouldn't be a need to use the key combo. You should only have to pull the battery if you plan on leaving the phone off.

Just to clarify, using the wall charger does not charge my phone, but I did buy an external battery charger, so I can make sure it is above 50%. Also I do have android installed as NAND so the bootloader is not automatically loaded on start up. I have to use the key combo. I'm just trying to flash back to Windows to see if it fixes the usb/charging problem. I've tried a couple of nhb files now in case one was corrupted, but the bootloader still does not see the files as valid. I'm using CoKe 2.31. I'm not sure what else to try.

bricked?

i have unlocked my atrix fine, then failed to flash gingerbread, and so tried to flash back to the original tmobile 2.2.2, but during the sbf flash through terminal, it just stopped dead, then after a while rebooted the phone, and now it does nothing. except the green charge light comes on when plugged in via usb. the power button appears to do nothing, so i cant boot back into fastboot or RSD. help pleeease XD
*EDIT* i have just rebooted with fastboot after many tries to boot failed 4, which is ok i can deal with that, but also "battery to low to flash"
is the phone charging when the green light is on, even when it cant boot? if so thats fine and i'll delete the thread. many thanks

ishamm said:
i have unlocked my atrix fine, then failed to flash gingerbread, and so tried to flash back to the original tmobile 2.2.2, but during the sbf flash through terminal, it just stopped dead, then after a while rebooted the phone, and now it does nothing. except the green charge light comes on when plugged in via usb. the power button appears to do nothing, so i cant boot back into fastboot or RSD. help pleeease XD
*EDIT* i have just rebooted with fastboot after many tries to boot failed 4, which is ok i can deal with that, but also "battery to low to flash"
is the phone charging when the green light is on, even when it cant boot? if so thats fine and i'll delete the thread. many thanks
Click to expand...
Click to collapse
First Rule, always charge your battery to the full before flashing.
Second Rule, always read the instructions carefully beforehand. Most importantly the warnings.
Third Rule, always follow the steps exactly as described.
Fourth Rule, if u face any hiccups or problems please describe in detail. Which version of Atrix, which country, how were u flashing, how did u unlock, what steps did u follow.

tbh i didnt realise that the phone couldnt charge while in fast boot, never even crossed my mind to check. im ok getting the phone out of RSD etc, and am aware of all the warnings, i suppose the real issue here is that when i plug the phone in, it boots up to the fail to boot/RSD screen, and wont charge. is there any way i can force it not to try to boot? thanks

Unfortunately, this sounds like the classic bricking situation. However, more details are required to be sure. To start:
What GB file did you use to upgrade from froyo?
What exactly is your error message?
Sent from my MB860 using XDA App

Buy an external battery charger so you can charge your battery. You can still flash ROMs when you have a fully charge battery using RSD Lite.

i tried to upgrade to GB with an orange sbf, since it seems from other forums tmobile people had had success with it. for whatever reason mine failed at the end, leaving me with RSD mode, then when i tried to flash back to the tmobile sbf from the Original sbf thread, the process just stopped part way through (it had worked fine before, with the same method) and again left me with RSD, but with low charge this time. is there no way around this without buying a charging station? i'd like to save money if possible, and with shipping the phone would be out of action for days, not ideal, though of course if its between that and an argument with tmobile about unlocking/waranty, i'll spend the £20 XD thanks

ishamm said:
i tried to upgrade to GB with an orange sbf, since it seems from other forums tmobile people had had success with it. for whatever reason mine failed at the end, leaving me with RSD mode, then when i tried to flash back to the tmobile sbf from the Original sbf thread, the process just stopped part way through (it had worked fine before, with the same method) and again left me with RSD, but with low charge this time. is there no way around this without buying a charging station? i'd like to save money if possible, and with shipping the phone would be out of action for days, not ideal, though of course if its between that and an argument with tmobile about unlocking/waranty, i'll spend the £20 XD thanks
Click to expand...
Click to collapse
If you have a spare USB cable you can use it to charge the battery. Search on YouTube for how to charge any phone without a charger
Sent from my MB860 using xda premium

do you mean charging with a stripped down usb cable? would that not cause the phone to still boot up? the videos i have seen before clamp the wires between the battery and phone terminals, i would of thought this would make the phone boot as it is, without charging since i only have RSD mode? if im wrong, thatd be great, but if not ive found a battery only charger for £0.99 XD

ishamm said:
do you mean charging with a stripped down usb cable? would that not cause the phone to still boot up? the videos i have seen before clamp the wires between the battery and phone terminals, i would of thought this would make the phone boot as it is, without charging since i only have RSD mode? if im wrong, thatd be great, but if not ive found a battery only charger for £0.99 XD
Click to expand...
Click to collapse
from what i remember someone posting who was in your situation, they did this and it gave their battery a charge. it's worth a try right?

[Q] softbricked with no info

Ok my buddy has an atrix 4g for ATT. he 'said' he was in cwm and loading a rom and now its softbricked. though i am familiar with droid, after reading recovery threads and everything, im still unsure of my resolution. most threads tell me i need an unlocked bootloader, others say not to flash if you were on this version. Honestly i have no idea if the BL is locked, what version or update he was on. at the moment it says failed to boot, starting RSD mode, battery is too low to flash.
A. will it charge while it says that or how should i charge it in this state?
B. after it does charge, what should i flash to it?
I apologize that i dont have much information. you have no idea how long it took me to find the power button lol. I appreciate any and all suggestions. Thanks

You definitely need to get more information from him before you can do anything. If his bootloader wasn't unlocked, then he was likely trying to flash one of the P-Roms like Greyblur or Gingerblur, in which case your solution will be a lot messier since the only way I remember accessing recovery back then was by using Tenfar's CWM app that reset it to recovery w/ a wall charger.
As for charging the phone, I don't recommend keeping it on and plugged in, in the chance that it doesn't charge and you are left with a dead battery. When the phone is completely off and you plug the charger in, do you see the charging battery?

When the phone is plugged into the wall charger it boots up automatically and says failed to boot 1, starting rsd, battery too low to flash. If I plug it into my pc the green power light turns on but nothing else happens. I never get any pictures on screen. No battery and no motorola logo. He was on 2.3.4 but he took his sd so I couldn't see what he was trying to flash. I will try to get more info
Sent from my DROID3 using XDA App

Same thing happened to me, and I can assure you it doesn't charge in that state. I have to find a way to charge the battery now... It is 0% dead. I hope I can use RSD Lite to fix it when it is charged.

alright, what happened was his battery was too low to finish the flash. it died halfway through, and now the phone is in some sort of limbo state that is just completely unusable.
but, if you have a spare USB cable you can fix this.
http://www.youtube.com/watch?v=EQ6JNCvIe8k
just watch that video, and let your phone charge for about half an hour to 45 minutes. after that, reflash the pudding .sbf with rsdlite (unless you can boot into recovery, then you can just reflash any ROM)

If you can boot the phone into recovery by holding the volume down key when powering on, then simply find the alien rom, save onto your SD card from the PC, then install in recovery...then you should be able to reboot into a working phone and charge. If you can't boot into recovery, and the phone is stuck on the "starting rsd protocol" screen, than...I think its a paper weight, but I could be wrong.

Although this problem could probably be fixed by an earlier post, I'm curious....
what would happen if you plugged it into the wall charger, let it boot up into the boot loop, then pulled the battery, left it out for 30 seconds, then put it back in. (this is without unplugging it from the wall charger). Does it allow the phone to stay off and charge, or does it still automatically boot up? Just curious.

im gonna look at the youtube video. ive got a D3 and i saw where a kid had cut a usb cable and made something work for 30 minutes and was able to flash again, but i was def trying to avoid that lol. also, there is no loop really. it doesnt restart, it just sits there. when the battery is pulled, it still stays on the same screen and never powers off until the charger is removed. i may see if i can get a new battery. i really apprecaite the feedback

Phalanx7621 said:
Although this problem could probably be fixed by an earlier post, I'm curious....
what would happen if you plugged it into the wall charger, let it boot up into the boot loop, then pulled the battery, left it out for 30 seconds, then put it back in. (this is without unplugging it from the wall charger). Does it allow the phone to stay off and charge, or does it still automatically boot up? Just curious.
Click to expand...
Click to collapse
It will not charge in this state

well my only option at this moment is to try the usb trick. im trying to strip the wire and hook it to the connector on the phone and then just smash teh battery on top of it, but i have no idicator light, so i dont know if its charging. would it charge if i tape/rig/solder it to the battery itself and not have it in the phone? i really dont wanna try a wall outlet charger

I am going to splice a cable and report back with results. My only other option is to charge the battery in my friend's Droid X
If that fails, to AT&T I go.

i havent been able to get it to charge through the usb using the red and black wires. i was very careful and have a decent set of tools to work with. he can buy the external battery charger for $30 if he'd like. im not really sure what else to do at this point.

I think I'm bricked?

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?

Moto G5 Plus Dead (only white light blinking)

This is my first time posting here so hi everyone.
I have a problem with my moto g5+.
I purcased my moto g5+ around a year a go completely new and ended up not using it.
Now my primary device broke down and i thought its time to switch only one problem.
It won't turn on.
When I connect charger white led will consistantly blink but nothing else happens no battery charging screen , nothing.
It wasn't compleatly discharged since I charged it up till 100% and turned it off when I puted it away , i still did charge it a couple times during the year of not using it and last time was a month ago and it charged just fine.
No water or Physical Damage has been done to the phone no rooting also , it just wont turn on.
I tried hard reseting it , tried to hold power button for 5 min tried to enter boot loader to access recovery mode with no luck.
I used original charger and cable that came with phone to charge it.
Since warranty is out of the way by this point because i bought it in july im seeking a fix or recommendation here.
All help will be appreciated

ridestos said:
This is my first time posting here so hi everyone.
I have a problem with my moto g5+.
I purcased my moto g5+ around a year a go completely new and ended up not using it.
Now my primary device broke down and i thought its time to switch only one problem.
It won't turn on.
When I connect charger white led will consistantly blink but nothing else happens no battery charging screen , nothing.
It wasn't compleatly discharged since I charged it up till 100% and turned it off when I puted it away , i still did charge it a couple times during the year of not using it and last time was a month ago and it charged just fine.
No water or Physical Damage has been done to the phone no rooting also , it just wont turn on.
I tried hard reseting it , tried to hold power button for 5 min tried to enter boot loader to access recovery mode with no luck.
I used original charger and cable that came with phone to charge it.
Since warranty is out of the way by this point because i bought it in july im seeking a fix or recommendation here.
All help will be appreciated
Click to expand...
Click to collapse
It seems your device had hard bricked, you can recover it by using the blank flash file.
Here is the procedure:-
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
But, I don't understand how you are device got hard bricked as you need to downgrade or root it to get your device bricked. But you can recover it by above link.

riyan65 said:
It seems your device had hard bricked, you can recover it by using the blank flash file.
Here is the procedure:-
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
But, I don't understand how you are device got hard bricked as you need to downgrade or root it to get your device bricked. But you can recover it by above link.
Click to expand...
Click to collapse
thanks for the reply gonna try it today, I don't really understand my self how did i hard brick it but gonna try you're solution.

riyan65 said:
It seems your device had hard bricked, you can recover it by using the blank flash file.
Here is the procedure:-
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
But, I don't understand how you are device got hard bricked as you need to downgrade or root it to get your device bricked. But you can recover it by above link.
Click to expand...
Click to collapse
Tried doing this methode but my pc wont reconize the device as connected , when i connected it to the pc it showed lightning symbol like charging , i left it to charge for 2h but still nothing.

In order to use blankflash successfully your PC needs to be in test mode. To do this
Code:
Click Start, and then type cmd in the Search box.
Under Programs, right-click cmd.exe, and then click Run as administrator.
At the command prompt, type the following text, and then press Enter: bcdedit /set TESTSIGNING OFF.
Close the Command Prompt window, and then restart your computer
When you plug in phone, look at device manager, ports, and see that it is connected. It should say something like "Qualcomm HS- USB Diagnostics " with a port "Comm 7" or whatever #.
1.Be sure Qualcomm drivers are installed.
2.Make sure your Hard Bricked Moto is connected in device manager under ports .
3.Hold volume down and power until you see it connect under ports. It should say "qhsusb-bulk" You should hear a slight sound from PC when it connects. This can be very tricky as another member [ Rakesh1b] explained his method.
trick is to press and hold the power button then it disconnects and connects to pc u could hear sound from pc then press voldown and power and launch blankflash.bat at the same time i mean same time then it detects and leave the buttons once you see the script running if not it will reboot the device and after running the script it will be booted to fastboot mode . if u failed 1st time repeat same power off then remaing things same as mentioned.
Click to expand...
Click to collapse

[email protected] said:
In order to use blankflash successfully your PC needs to be in test mode. To do this
Code:
Click Start, and then type cmd in the Search box.
Under Programs, right-click cmd.exe, and then click Run as administrator.
At the command prompt, type the following text, and then press Enter: bcdedit /set TESTSIGNING OFF.
Close the Command Prompt window, and then restart your computer
When you plug in phone, look at device manager, ports, and see that it is connected. It should say something like "Qualcomm HS- USB Diagnostics " with a port "Comm 7" or whatever #.
1.Be sure Qualcomm drivers are installed.
2.Make sure your Hard Bricked Moto is connected in device manager under ports .
3.Hold volume down and power until you see it connect under ports. It should say "qhsusb-bulk" You should hear a slight sound from PC when it connects. This can be very tricky as another member [ Rakesh1b] explained his method.
Click to expand...
Click to collapse
Thanks for heads up gonna try to do it again tomorrow I hope this will work and I will be able to get my new phone runing tomorrow since I really need that phone .

ridestos said:
Thanks for heads up gonna try to do it again tomorrow I hope this will work and I will be able to get my new phone runing tomorrow since I really need that phone .
Click to expand...
Click to collapse
Good luck, as it is not an easy process. One time it took me nearly half an hour to time it right, to get blankflash to run successfully. Also I played with a phone that would never flash Vaches blankflash for the G5 + but had to use the one for addison, Moto Z play. When that happens you have to do the extra step of flashing the addison to potter files. Hopefully you won't have to do all that, but just warning that sometimes it is necessary. Like I posted before, in device manager on PC, make sure under ports it shows as qhsusb-bulk under the port it lists as. Also be sure you have adb/fastboot and all its drivers correctly installed. I am really curious as to how it got hard bricked, because even doing my test phone, it is difficult to hard brick it. I have this "test phone" that has a bad microphone, so I have run it through all kinds of crap, rather than jeopardise my every day phone.

ridestos said:
This is my first time posting here so hi everyone.
I have a problem with my moto g5+.
I purcased my moto g5+ around a year a go completely new and ended up not using it.
Now my primary device broke down and i thought its time to switch only one problem.
It won't turn on.
When I connect charger white led will consistantly blink but nothing else happens no battery charging screen , nothing.
It wasn't compleatly discharged since I charged it up till 100% and turned it off when I puted it away , i still did charge it a couple times during the year of not using it and last time was a month ago and it charged just fine.
No water or Physical Damage has been done to the phone no rooting also , it just wont turn on.
I tried hard reseting it , tried to hold power button for 5 min tried to enter boot loader to access recovery mode with no luck.
I used original charger and cable that came with phone to charge it.
Since warranty is out of the way by this point because i bought it in july im seeking a fix or recommendation here.
All help will be appreciated
Click to expand...
Click to collapse
If your phone was in oreo, you maybe want to try the addison (moto z play) blankflash, i once bricked mine and the potter blankflash always failed.
Also try the USB 2.0 ports, as the 3.0 ones doesn't recognizes it.

Put it on the charger and let it charge. IT could just be deader than disco.
Also check your cable make sure it's a data cable buddy.

pwag said:
Put it on the charger and let it charge. IT could just be deader than disco.
Also check your cable make sure it's a data cable buddy.
Click to expand...
Click to collapse
Already tried that didn't work. And I'm using included cable that came with g5+

red002 said:
If your phone was in oreo, you maybe want to try the addison (moto z play) blankflash, i once bricked mine and the potter blankflash always failed.
Also try the USB 2.0 ports, as the 3.0 ones doesn't recognizes it.
Click to expand...
Click to collapse
Well good news is , that i manged to get it to show up as the device with which i should be able to do blank flash.
The problem now is it won't stay in bootloader to be recognized as that device longer than 30 sec.
It just turns off after some time and pc automaticly wont recognize it anymore.

[email protected] said:
Good luck, as it is not an easy process. One time it took me nearly half an hour to time it right, to get blankflash to run successfully. Also I played with a phone that would never flash Vaches blankflash for the G5 + but had to use the one for addison, Moto Z play. When that happens you have to do the extra step of flashing the addison to potter files. Hopefully you won't have to do all that, but just warning that sometimes it is necessary. Like I posted before, in device manager on PC, make sure under ports it shows as qhsusb-bulk under the port it lists as. Also be sure you have adb/fastboot and all its drivers correctly installed. I am really curious as to how it got hard bricked, because even doing my test phone, it is difficult to hard brick it. I have this "test phone" that has a bad microphone, so I have run it through all kinds of crap, rather than jeopardise my every day phone.
Click to expand...
Click to collapse
Well managed to get it to point where my pc recognized phone as device buuut another thing came up. It only is recognized for max 30sec after witch phone gets disconected from pc. Any way to fix that? Or mby im doing something wrong here? I'm starting to consider battery replacment which i dont want to do because it awful to replace battery on this thing.

What is it recognised as? Battery replacement may save you from having to go through the blankflash process if the device will not stay on while plugged in. Only use blankflash if it shows as qhsusb-bulk.

[email protected] said:
What is it recognised as? Battery replacement may save you from having to go through the blankflash process if the device will not stay on while plugged in. Only use blankflash if it shows as qhsusb-bulk.
Click to expand...
Click to collapse
yes it showed up like that but like I said it wont stay on. I remembered one time when I got it to work this month. I was able to boot in to android , factory reset it but the problem was as soon i pluged in the charger phone went from 44% up to 89% in 2 sec then droped to 14% and then to 0 and turned off. I was able to turn it on again after that , it showed 44% like before the charger was connected then I tried to charge it while it was off and since then I haven't been able to go past booting screen since it just turns off after like 30sec on boot screen.
Mby i should just buy a new battery and see if that will fix it.

ridestos said:
yes it showed up like that but like I said it wont stay on. I remembered one time when I got it to work this month. I was able to boot in to android , factory reset it but the problem was as soon i pluged in the charger phone went from 44% up to 89% in 2 sec then droped to 14% and then to 0 and turned off. I was able to turn it on again after that , it showed 44% like before the charger was connected then I tried to charge it while it was off and since then I haven't been able to go past booting screen since it just turns off after like 30sec on boot screen.
Mby i should just buy a new battery and see if that will fix it.
Click to expand...
Click to collapse
I would recommend that or to take it to a service center. Using the blankflash method could brick the device forever (if it's just a battery/display problem), also you will have to live with another devices bootloader and resulting problems from that.

Wolfcity said:
I would recommend that or to take it to a service center. Using the blankflash method could brick the device forever (if it's just a battery/display problem), also you will have to live with another devices bootloader and resulting problems from that.
Click to expand...
Click to collapse
Well service center is out of the way since closest one to me is like 200km away . I should be able to replace it my self so no problems there. I just hope that maybe replacing the battery will fix everything since the phone is practicly brand new and it would be painful and expensive if it's not a battery problem but like motherboards or smth like that.

ridestos said:
Well good news is , that i manged to get it to show up as the device with which i should be able to do blank flash.
The problem now is it won't stay in bootloader to be recognized as that device longer than 30 sec.
It just turns off after some time and pc automaticly wont recognize it anymore.
Click to expand...
Click to collapse
Reboot your pc, and connect the phone to the wall charger for about 10 minutes, then try again the blankflash, and when it's done just play around with the volume up/down buttons just to keep the bootloader on, and use the g5+ toolkit to flash the oreo stock firmware
in any case, this is the blankflash i used it
https://www.mediafire.com/file/hw7hs4vve51c1qh/blankflash.zip/file

Led Light Blinking
ridestos said:
Well good news is , that i manged to get it to show up as the device with which i should be able to do blank flash.
The problem now is it won't stay in bootloader to be recognized as that device longer than 30 sec.
It just turns off after some time and pc automaticly wont recognize it anymore.
Click to expand...
Click to collapse
How did you managed to show it up as a device , i couldn't. I tried everything that i understood from written on these forums, installed qualcomm drivers , moto g5 plus drivers. The device doesn't show up in device manager, its just blinking and doesn't show anything else , i tried charging it overnight. The Led light does go away after a while when i put it o charging, but when i hold down the power button and volume down key it starts blinking again and nothing beyond that

Rather Suhail said:
How did you managed to show it up as a device , i couldn't. I tried everything that i understood from written on these forums, installed qualcomm drivers , moto g5 plus drivers. The device doesn't show up in device manager, its just blinking and doesn't show anything else , i tried charging it overnight. The Led light does go away after a while when i put it o charging, but when i hold down the power button and volume down key it starts blinking again and nothing beyond that
Click to expand...
Click to collapse
Well for me it works like this , i leave it for about 12h (over night) untouched , then after that I can put it on charger and get in bootloader with holding down power button and vol down button at the same time. I have seen some other people that have revived their phones like this usualy they say to just leave it for 24h but for me it works after 12h. if u can get in to the bootloader
after those hours and the phone doesn't turn off (like mine) I would suggest that u leave it for charging in bootloader for atleast 2h and then try to power it on in factory mode thats how I got it to work one time. I hope this will help you.

ridestos said:
Well for me it works like this , i leave it for about 12h (over night) untouched , then after that I can put it on charger and get in bootloader with holding down power button and vol down button at the same time. I have seen some other people that have revived their phones like this usualy they say to just leave it for 24h but for me it works after 12h. if u can get in to the bootloader
after those hours and the phone doesn't turn off (like mine) I would suggest that u leave it for charging in bootloader for atleast 2h and then try to power it on in factory mode thats how I got it to work one time. I hope this will help you.
Click to expand...
Click to collapse
Thanks for replying.
A few points to clear with 12 hours untouched ,do you mean i have to left phone as it is without even charging and if so after 12 hours for how much time do you charge it before getting it to bootloader and did you charge it with the moto turbo charge or just a regular charger or with computer.