Axon 7 (apperantly) Hard Brick - ZTE Axon 7 Questions & Answers

Hi,
I got my A2017G bricked and I dont really understand how: I had the bootloader unlocked a few hours ago, but i hadnt done anything with it. Than I accidentally long pressed the powerbotton, while turning the phone off. Than the phone turned off and since than im not abled anymore to turn the phone on - the phone does not responds in any way. When pluged into my computer, the phone shows up as: Qualcomm HS-USB QDLoader 9008 (COM3)
The Phone runs ZTE owns Android Oreo and is not rooted.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
I Already tried out the solution above. It didnt worked with the linked MiFlash so I used a slightly newer one which than told me "Error: Timeout while writing" after 15 Seconds.
Do you guys have any Idea what I could try to repair my phone? Otherwise Id just send it in, I still have half a year of warrenty.
sorry for my bad english, im tired.

well i think it was stuck, i left it overnight and late morning it responded first try, buzz and flat battery screen
put in cable and it charged up and seems ok (boots up and stuff)

pingu666 said:
well i think it was stuck, i left it overnight and late morning it responded first try, buzz and flat battery screen
put in cable and it charged up and seems ok (boots up and stuff)
Click to expand...
Click to collapse
got it going again but it crashed installing apps and i cant restart it
guess i have to wait for battery to die, and then try another rom i guess :/

Related

[HELP]Galaxy S4 Hard Bricked ITSELF!!! Everything stock!!

Hey guys,
It's my second S4 as the first one died during the night two months ago (rooted with Google edition rom).
So on my new one I didn't install any custom rom, I didn't root it, everything stock.
But yesterday night I didn't put it to charge during the night so my battery went to 0%, and in the morning it refused to power up. But after many tries it woke up. The problem is that in the evening I rebooted the phone, and it got stock on the blue LED aaaaaaaaand that's it... it gets detected by the computer as QUALCOMM HS-USB QDLOADER so I guess it's hard bricked, how the f***?
Any ideas? I really hate Samsung right now.
nutzy73 said:
Hey guys,
It's my second S4 as the first one died during the night two months ago (rooted with Google edition rom).
So on my new one I didn't install any custom rom, I didn't root it, everything stock.
But yesterday night I didn't put it to charge during the night so my battery went to 0%, and in the morning it refused to power up. But after many tries it woke up. The problem is that in the evening I rebooted the phone, and it got stock on the blue LED aaaaaaaaand that's it... it gets detected by the computer as QUALCOMM HS-USB QDLOADER so I guess it's hard bricked, how the f***?
Any ideas? I really hate Samsung right now.
Click to expand...
Click to collapse
Its not hard bricked if possible try charging the phone to max and then try
u can also try other battery if u have
Already did, went to the store and tried a new battery.. the phone powers up SOMETIMES, like I have to pull out the battery 50 times before it starts up, and if I restart the phone, it dies again.
I went for a refound and I'll get the Xperia Z1, a friend's S4 died the same way as mine....
nutzy73 said:
Already did, went to the store and tried a new battery.. the phone powers up SOMETIMES, like I have to pull out the battery 50 times before it starts up, and if I restart the phone, it dies again.
I went for a refound and I'll get the Xperia Z1, a friend's S4 died the same way as mine....
Click to expand...
Click to collapse
Time to send it to repair center? Why not?
I won't send it to the repair service (takes too long) AND it's my second S4 that dies the same way so I won't give another chance to sammy. I told them that my phone got stolen so I'll get a refound
nutzy73 said:
I won't send it to the repair service (takes too long) AND it's my second S4 that dies the same way so I won't give another chance to sammy. I told them that my phone got stolen so I'll get a refound
Click to expand...
Click to collapse
try this
---Repair dead boot I9505 via usb cable--- Thanks to legija from JTAG team.
QHUSB Qualcomm driver download
or
http://www.riffbox.org/downloads/RiffSetup.exe[/SIZE]
nutzy73 said:
I won't send it to the repair service (takes too long) AND it's my second S4 that dies the same way so I won't give another chance to sammy. I told them that my phone got stolen so I'll get a refound
Click to expand...
Click to collapse
Why would you tell everyone you committed fraud?

[Help] Bricked phone + no battery

I've managed to brick my phone BIG TIME, and i'm posting this thread as a last resort.
Since Saturday my phone is bricked, I've already gone through the process of the HS-USB 9006 and 9008 successfully, the tool on 9008 even tested my phone and all tests went ok.
But, when I reconnect the battery and then to the usb my led is blinking red, that's it.
I heard that the battery is empty and that in order to charge (it doesn't get charged by connecting the a wall charger) I should press volume+ and connect to usb for a few minutes.
Well I've tried that, it didn't helped, I even tried taping a rubber so it will press on the button and kept it over night - didn't helped.
On the plus side in one of my attempts to recover the phone it did went on to download mode for 4-5 seconds, but then the battery died again.
Any recommendation anyone? would really appreciate your help.
BTW d801 here if that matters
Just wondering, maybe the battery is somehow drained/borked and you just have to buy a new one?
Choristav said:
Just wondering, maybe the battery is somehow drained/borked and you just have to buy a new one?
Click to expand...
Click to collapse
Already bought one just in case, it will take time as it from eBay.
Thanks for your suggestion

Powered OFF unlocked nexus 6p with custom rom -> hardbricked?

Hello everybody,
I have a nexus 6p with unlocked bootloader, twrp, rooted and running the latest resurrection remix rom with a few xposed modules on it (amplify, boot manager, greenify donation ).
It was running like a boss, great performance, great battery life and so on.
Yesterday insted of putting it offline for charging overnight I decided to turning it off, and then I plugged the usb cable and I saw that it detected the charging while it was turning off.
This morning when I went to turn it on, nothing, nada, 0, no sign of life at all. Plug-and unplug the charging cable, no luck, change charging cable, plug it to the pc, nothing.
Tried to push the power button for 10, 15, 30 seconds, no luck, tried to boot to recovery with power button plus volume down, no luck again.
Very sad day got any advice for me?
Thank you!
barduro said:
Hello everybody,
I have a nexus 6p with unlocked bootloader, twrp, rooted and running the latest resurrection remix rom with a few xposed modules on it (amplify, boot manager, greenify donation ).
It was running like a boss, great performance, great battery life and so on.
Yesterday insted of putting it offline for charging overnight I decided to turning it off, and then I plugged the usb cable and I saw that it detected the charging while it was turning off.
This morning when I went to turn it on, nothing, nada, 0, no sign of life at all. Plug-and unplug the charging cable, no luck, change charging cable, plug it to the pc, nothing.
Tried to push the power button for 10, 15, 30 seconds, no luck, tried to boot to recovery with power button plus volume down, no luck again.
Very sad day got any advice for me?
Thank you!
Click to expand...
Click to collapse
Sounds hard bricked. Probably an internal malfunction. If you have it plugged in and holding power and volume does nothing, then there is nothing you can do. Very unlucky, sorry. Did you get insurance?
Gizmoe said:
Sounds hard bricked. Probably an internal malfunction. If you have it plugged in and holding power and volume does nothing, then there is nothing you can do. Very unlucky, sorry. Did you get insurance?
Click to expand...
Click to collapse
no, i'm not sure what huawei will have to say about my warranty, given the fact that the phone is modded.
I noticed that if I charge it for a very long period of time the top left portion under the screen gets mildly warm... not too sure why but I think that something hardware was faulty.
barduro said:
no, i'm not sure what huawei will have to say about my warranty, given the fact that the phone is modded.
I noticed that if I charge it for a very long period of time the top left corner gets mildly warm... not too sure why but I think that something hardware was faulty.
Click to expand...
Click to collapse
If you have to deal with Huawei then you are probably SOL. They won't fix anything under warranty. I would just take it to a local repair shop and have them look at it and see if it's something not too spend to fix. You could contact Google though and see if they will help you. Google actually cares about its customers. Huawei does not. If it wont boot they won't notice the mods probably. I got an HTC replaced that I bricked some time ago and they never noticed. If it turns on they might, but that doesn't sound like the case here.
Gizmoe said:
If you have to deal with Huawei then you are probably SOL. They won't fix anything under warranty. I would just take it to a local repair shop and have them look at it and see if it's something not too spend to fix. You could contact Google though and see if they will help you. Google actually cares about its customers. Huawei does not. If it wont boot they won't notice the mods probably. I got an HTC replaced that I bricked some time ago and they never noticed. If it turns on they might, but that doesn't sound like the case here.
Click to expand...
Click to collapse
I think that you can count on google support only if you got it through the play store which is not my case.
I took it to official Huawei repair center here in Milan, in approx 7 to 10 days they'll fix it. But I'm afraid they will eventually turn it on and find out all the naughty things that I did to it and **** my warranty
I'll let you know how it goes, thanks for your support.
the problem was 100% hardware, but now I am happy to report that the italian shop where I bought my phone have it replaced but only after 2 months. They said they fixed it but they lied because it is now graphite instead of silver LOL

Almost completly dead LeEco Le Pro 3 Elite

So I was using my phone (with 1-2%) and someone called me, so I forgot about everything, and I went to talk. I was talking something like 5 mins, and then it stopped. Nothing to worry about, I put it to the charger, but the notification led didn't even started. Tried to boot up, no even a vibration, after 5 min, I tried again, I could heard very small vibration. I got worried, I waited like 20 minutes, still nothing, but the vibrations we're powerfull now.
So my phone is detected by qdloader. I tried with flashone+qfil, succesfull BUT STILL COULDN'T POWER UP. Ok, tried qtps, exactly by tutorial, everything was done, succesfull, BUT STILL ONLY VIBRATES AND NO SIGN OF LIFE, not even notification led when I plug it into the charger. No nothing. So, battery "somehow, I guess" isn't dead. It is soo strange. I contacted @tsongming and we try to fix it later at night, but until then if someone has an ideea or had the same problem, I would be very gratefull, it would be a disaster now to lose this phone
tldr: discharged, put to charge, no led no life, only warming up and 9008 mode works. Qfil doesn't help.
 @F.J.V any ideeas ?
D1stRU3T0R said:
So I was using my phone (with 1-2%) and someone called me, so I forgot about everything, and I went to talk. I was talking something like 5 mins, and then it stopped. Nothing to worry about, I put it to the charger, but the notification led didn't even started. Tried to boot up, no even a vibration, after 5 min, I tried again, I could heard very small vibration. I got worried, I waited like 20 minutes, still nothing, but the vibrations we're powerfull now.
So my phone is detected by qdloader. I tried with flashone+qfil, succesfull BUT STILL COULDN'T POWER UP. Ok, tried qtps, exactly by tutorial, everything was done, succesfull, BUT STILL ONLY VIBRATES AND NO SIGN OF LIFE, not even notification led when I plug it into the charger. No nothing. So, battery "somehow, I guess" isn't dead. It is soo strange. I contacted @tsongming and we try to fix it later at night, but until then if someone has an ideea or had the same problem, I would be very gratefull, it would be a disaster now to lose this phone
tldr: discharged, put to charge, no led no life, only warming up and 9008 mode works. Qfil doesn't help.
@F.J.V any ideeas ?
Click to expand...
Click to collapse
Change the graphics card to see
I do not know what to tell you, maybe so much overclocking ...
I can only tell you that I had a terminal that I left flashing, I forgot and the next day it seemed that everything went well, but the terminal did not do anything.
The terminal was dead, it did not charge, it did not vibrate, the computer did not recognize it, we go as if it had been fried.
After a couple of weeks, the terminal was still the same, it did not matter if I left it charging, it did not react to anything.
At the end I opted to open the terminal to see if I saw something melted, everything was fine, provided with the screen disconnected in case it was the problem and nothing, but ... I disconnected the battery for a few minutes and when reconnecting it the computer recognized 9008 I gave him the qfil and the mobile was as good as new.
The hardware is very damn, sometimes the least unthinkable fails. I have an old notebook, which once stopped working, did not start, but apparently everything was fine. I completely disassembled it and I did not see anything strange, but when I mounted it again it worked perfectly. But every two or three weeks the same thing happened to him. I was trying disconnecting and connecting pieces to see if I found fault, until I discovered that it was the screen.
The fact is that every time it happened to me, I would disconnect the screen, reconnect it and fix it. The funny thing is that there came a time when it did not spoil anymore, now even if I just take it never fails.
I think your failure can be something of that, the bad thing is to open it, but if you can not fix it via software try disconnecting the screen and the battery for a few minutes.
Greetings.
F.J.V said:
Change the graphics card to see
I do not know what to tell you, maybe so much overclocking ...
I can only tell you that I had a terminal that I left flashing, I forgot and the next day it seemed that everything went well, but the terminal did not do anything.
The terminal was dead, it did not charge, it did not vibrate, the computer did not recognize it, we go as if it had been fried.
After a couple of weeks, the terminal was still the same, it did not matter if I left it charging, it did not react to anything.
At the end I opted to open the terminal to see if I saw something melted, everything was fine, provided with the screen disconnected in case it was the problem and nothing, but ... I disconnected the battery for a few minutes and when reconnecting it the computer recognized 9008 I gave him the qfil and the mobile was as good as new.
The hardware is very damn, sometimes the least unthinkable fails. I have an old notebook, which once stopped working, did not start, but apparently everything was fine. I completely disassembled it and I did not see anything strange, but when I mounted it again it worked perfectly. But every two or three weeks the same thing happened to him. I was trying disconnecting and connecting pieces to see if I found fault, until I discovered that it was the screen.
The fact is that every time it happened to me, I would disconnect the screen, reconnect it and fix it. The funny thing is that there came a time when it did not spoil anymore, now even if I just take it never fails.
I think your failure can be something of that, the bad thing is to open it, but if you can not fix it via software try disconnecting the screen and the battery for a few minutes.
Greetings.
Click to expand...
Click to collapse
Now I can't even enter in 9008 mode. What the .... you have telegram or something so we can talk more in depth about this problem ? I really need this phone, and it's a really strange case After some time, the vibration got very low, and 9008 doesn't even get detected anymore.
F.J.V said:
Change the graphics card to see
I do not know what to tell you, maybe so much overclocking ...
I can only tell you that I had a terminal that I left flashing, I forgot and the next day it seemed that everything went well, but the terminal did not do anything.
The terminal was dead, it did not charge, it did not vibrate, the computer did not recognize it, we go as if it had been fried.
After a couple of weeks, the terminal was still the same, it did not matter if I left it charging, it did not react to anything.
At the end I opted to open the terminal to see if I saw something melted, everything was fine, provided with the screen disconnected in case it was the problem and nothing, but ... I disconnected the battery for a few minutes and when reconnecting it the computer recognized 9008 I gave him the qfil and the mobile was as good as new.
The hardware is very damn, sometimes the least unthinkable fails. I have an old notebook, which once stopped working, did not start, but apparently everything was fine. I completely disassembled it and I did not see anything strange, but when I mounted it again it worked perfectly. But every two or three weeks the same thing happened to him. I was trying disconnecting and connecting pieces to see if I found fault, until I discovered that it was the screen.
The fact is that every time it happened to me, I would disconnect the screen, reconnect it and fix it. The funny thing is that there came a time when it did not spoil anymore, now even if I just take it never fails.
I think your failure can be something of that, the bad thing is to open it, but if you can not fix it via software try disconnecting the screen and the battery for a few minutes.
Greetings.
Click to expand...
Click to collapse
We worked on this for a while, I agree this issue is hardware based. Unfortunately it could be anything, in my case disconnecting and reconnecting the battery did not work.
In his case, I am thinking that it may be a shorted usb card, especially because of the port issue.
Symptoms are zero battery, very soft vibrations and after a while at rest vibrates stronger for a moment and stays at zero.
As I mentioned in my case, the USB port did not work at all, neither recognized the computer, nor charged the battery, for some reason there was a blockage that only deactivated when disconnecting the battery for a few minutes.
The USB port is usually burned in the load, but it seems that this is not the case, unless it burned with the battery charged, and when downloading and trying to load appears the problem.
I hope you are lucky.
P.S. I suppose that D1stRU3T0R has tested with another usb cable and another PC
F.J.V said:
Symptoms are zero battery, very soft vibrations and after a while at rest vibrates stronger for a moment and stays at zero.
As I mentioned in my case, the USB port did not work at all, neither recognized the computer, nor charged the battery, for some reason there was a blockage that only deactivated when disconnecting the battery for a few minutes.
The USB port is usually burned in the load, but it seems that this is not the case, unless it burned with the battery charged, and when downloading and trying to load appears the problem.
I hope you are lucky.
P.S. I suppose that D1stRU3T0R has tested with another usb cable and another PC
Click to expand...
Click to collapse
I bought another cable now, and the symptoms are the same. Also tried on another laptop.
So, if I charge it now, it's vibrating every x seconds (something like 10-20 sec), even without touching it. BAttery getting warm when charging. 9008 mode still disappeared for no reason.
So, by judgind this: Battery: Cannot REALLY be, because it's still alive, charging and somehow working. Maybe the voltage dropped and the vibrations are the sign of it?
Port - Don't believe, I can clearly charge it, so what's the problem here?
Motherboard/CPU - hmm, still doing something, something is controlling the vibrations, so not really
Soft - maaaaaaaaaaaaaaaaayyyyyyyyybbbbbbbbbbbbeeeeeeeeeeeee, when I used qpst, I didn't installed qfil with erase option, maybe that would help. When I tried to do that, I got a sahara error(maybe I did something wrong) than I lost 9008 mode.
Today, I got another ideea. Maybe I bricked the UFS memory ? it can't load anything, soooo...... it doesn't start, doesn't know what led color to select? And the vibration is just a sign....
Tried QFIL, 2-3 times, 2 with flashone 1 with qpst.
I went to 3 services, all of them refused me(one only fixing easly fixable phones, another was pretty **** service, and the third .. well I refused it, bcs he said he can try, but he doesn't quarantee that he can open the phone whitout breaking the glass ) But maybe I will try that. I bought another cable to try that EDL force flash, but tsongming is offline, so maybe tomorrow. I'm having some bad times bcs of this loss :crying::crying:
The glass is very hard, I doubt it breaks, but do not pay much attention to the videos that are out there of leeco. If you have never done it better, do not do it (as it happened to me).
I give you some advice in case you try.
Try to use only heat, I do not know if a hair dryer will work, better a heat gun.
Try not to introduce anything to separate the glass, at most a few millimeters, because you can damage the back of the screen and then it looks bad. Above all, do not put anything under and on the left, because you can load the connection strip and goodbye screen. Do not insert any plastic card to separate, because it will fill with glue and will damage the back of the screen.
When you take out the screen it will be full of glue everywhere. In the videos of youtube it says that you scrape it, but it is very easy to scratch the edges or the top part, if the stripes will be transparent and the backlight will be seen.
Do not even think about using a product to eliminate the glue, the screen will be deformed and you will never look good.
Well, you know what you should not do, to see if someone can explain how to do it correctly.
Once you take off the screen remove a small screw and the connector with a slight pressure, then you will have to remove a few more screws to remove a metal plate to access the battery, it may cost a little because it is stuck, but make sure you remove all the screws.
Once you remove the plate you find the battery. If you think it's okay, do not try to remove it, because it's stuck tightly, simply remove the connector for a few minutes and give the power button a moment before reconnecting the battery again
The USB port has not been removed but it seemed easy to remove.
Greetings.
D1stRU3T0R said:
I bought another cable now, and the symptoms are the same. Also tried on another laptop.
So, if I charge it now, it's vibrating every x seconds (something like 10-20 sec), even without touching it. BAttery getting warm when charging. 9008 mode still disappeared for no reason.
So, by judgind this: Battery: Cannot REALLY be, because it's still alive, charging and somehow working. Maybe the voltage dropped and the vibrations are the sign of it?
Port - Don't believe, I can clearly charge it, so what's the problem here?
Motherboard/CPU - hmm, still doing something, something is controlling the vibrations, so not really
Soft - maaaaaaaaaaaaaaaaayyyyyyyyybbbbbbbbbbbbeeeeeeeeeeeee, when I used qpst, I didn't installed qfil with erase option, maybe that would help. When I tried to do that, I got a sahara error(maybe I did something wrong) than I lost 9008 mode.
Today, I got another ideea. Maybe I bricked the UFS memory ? it can't load anything, soooo...... it doesn't start, doesn't know what led color to select? And the vibration is just a sign....
Tried QFIL, 2-3 times, 2 with flashone 1 with qpst.
I went to 3 services, all of them refused me(one only fixing easly fixable phones, another was pretty **** service, and the third .. well I refused it, bcs he said he can try, but he doesn't quarantee that he can open the phone whitout breaking the glass ) But maybe I will try that. I bought another cable to try that EDL force flash, but tsongming is offline, so maybe tomorrow. I'm having some bad times bcs of this loss :crying::crying:
Click to expand...
Click to collapse
Absolutely it sucks that you have these issues, I know how it feels.
But we need to clear a couple of things up, first just because the battery vibrates doesn't mean that it has enough charge to operate the phone. The battery may have enough charge to vibrate but not enough to power up the phone. > The battery would still be shot.
Next, to remove the glass, carefully and briefly use a Heat Gun. The screen can then be removed with a cloth to protect yourself from the heat, no guitar picks needed, no chance of breaking glass. Leeco simply uses A LOT of glue.
QPST use isn't related to the port issue, the port not showing is a driver issue.
The erase function of QPST clears items in the NV memory and then are backed up automatically during the download/restoration process per QPST user guide.
From QPST Technical Journal:​"Nominally, each NAND block will survive 100,000 PROGRAM/ERASE cycles With an HDD, as long as there is no failure of mechanical or circuit parts, data on the platter (disk) can be rewritten for an almost unlimited number of times."
When something goes wrong
It's either drivers, improper QFIl preparation, windows related issues such as antivirus/windows security is not fully disabled, or damaged hardware.
Edit: It seems that @F.J.V already covered it.
@F.J.V new update, so my phone is now opened but the beginner at the service said that the motherboard is dead, didn't specified more. The phone is still open, and after 2 days I'm going home to check what's up. Any ideea what to check ( with voltagemeter, or to try plugging in whitout battery etcetc, checking battery voltage )
D1stRU3T0R said:
@F.J.V new update, so my phone is now opened but the beginner at the service said that the motherboard is dead, didn't specified more. The phone is still open, and after 2 days I'm going home to check what's up. Any ideea what to check ( with voltagemeter, or to try plugging in whitout battery etcetc, checking battery voltage )
Click to expand...
Click to collapse
If the battery has an acceptable voltage, plug it in, do not connect the screen, and test if it recognizes 9008.
If it is totally downloaded, you have to try to load it in some artisan way, and do the same test, without plugging in the terminal screen.
If it is impossible to recognize 9008 almost certainly the motherboard is broken, but as the port of loading, which also manages the data between terminal and pc, is worth little money, you can try a new one. If there is not 9008 something on the motherboard is broken, and I do not think it's viable to find out the problem.
regards
F.J.V said:
If the battery has an acceptable voltage, plug it in, do not connect the screen, and test if it recognizes 9008.
If it is totally downloaded, you have to try to load it in some artisan way, and do the same test, without plugging in the terminal screen.
If it is impossible to recognize 9008 almost certainly the motherboard is broken, but as the port of loading, which also manages the data between terminal and pc, is worth little money, you can try a new one. If there is not 9008 something on the motherboard is broken, and I do not think it's viable to find out the problem.
regards
Click to expand...
Click to collapse
I had 9008 mode, and there are 2 people, tsongming and noel who can backup this theory. Even after I got the brick I had the 9008, but only after somehow it died. Maybe I tried qfil too many times, or I charged too much ?
D1stRU3T0R said:
I had 9008 mode, and there are 2 people, tsongming and noel who can backup this theory. Even after I got the brick I had the 9008, but only after somehow it died. Maybe I tried qfil too many times, or I charged too much ?
Click to expand...
Click to collapse
Hi, I'm not a terminal technician, so all I can say are simple theories, similar situations that I've read or things that have happened to me, so what I say can work or not
I do not think that his problem is present in many flashes, or in many qfil, it would happen to more people.
My intuition tells me that it may be forcing the processor for a long time.
Well, what I can assure you, because it has happened to me with an X722, is that sometimes there is some type of blockage that leaves it totally dead, and the only way to make it work again is to disconnect the battery for a few minutes. In my case, there was no 9008, it was not charged, it did not do anything, but when I removed the battery and plugged it back in after a few minutes, the 9008 returned and I was able to retrieve it with qfil.
Also, and this is just a theory, I think some of the terminals when in edl mode, even if you put the charger and the terminal is hot, in reality the battery does not charge.
In my case, the terminal was connected to the PC one day after making a qfil, when I went to restart it it was already dead, it got stuck for a week in the charger, but when I removed the battery and reconnected it, the battery was for the minimum , but it worked, I passed the qfil and I was able to load it with the new rom.
By this I mean that I think the lock was caused by not restarting after qfil and running out of battery, despite being connected to the PC, which in theory should charge the battery.
So I recommend whenever you can, and more if you have the terminal open, disconnect the battery, but this is not a miracle, is to discard this rare block that sometimes suffers.
It is not the first time I see that a leeco has run out of battery and could not be charged in any way, the only way has been to change the battery and pass the charging port, but I do not know if these people tried to reconnect the battery and make a qfil later, the same would have saved a new battery.
If your problem is the motherboard, I recommend that you look for YouTube to repair the graphics card of a PC. Generally, overclocking damages it, but it does not break, it's because the chip reaches temperatures so high that you can lose a solder, which in some cases can be easily repaired with a heat gun. I know people who have worked for him, it's easy, you just need a heat gun.
I hope you can use some of what I told you, it worked for me to disconnect the battery, but Tsongming did not work.
Greetings.
F.J.V said:
Greetings.
Click to expand...
Click to collapse
hmm, so in 2 days i'll try this. DIsconnect the battery and let it like that. Also can I connect to the PC whitout the battery connected? Also, I can try to see if the battery is warming up, not only the motherboard or whatever, cpu.
This OC what we're using aren't damaging our hardware. Believe me, i'm OC-ed, and I overvolt and overclock for almost 50% stock speed and still didn't broke anything (top 1 hd 7750 on userbenchmark, biggest benchmark site)

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.

Categories

Resources