Hello.
When I try to turn on my N4, I hold power button, and after about 10 seconds Red light blinks (just once, if it's connected to USB that 1 blink last for 3 seconds, if connected to wall, it's just quick 1 blink. If it not connected anywhere there is no action at all, it just stays dead, no blinks, nothing). Same if I try to go in bootloader by holding volume down+power.
This happened after I successfully installed CM12, with no errors. Then I rebooted my phone, and it just stayed black as it is now. Battery was around 25~30% that time, and phone was connected to USB.
Did I bricked my phone totally? I am now trying to charge it up already for 1 hour... but it nothing changes.
I have searched here for similar problems, but couldn't find solution...
Edit: Charging already for 10h+ , still same..
Edit2: I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Edit3: I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".
easy fix
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:
zelexon said:
Hold down the power button and the volume down button at the same time until phone reboots. If you see the little android no need to worry just let go and wait for your device to reboot on its own. This is not a factory reset it's just like restarting your device. :good:
Click to expand...
Click to collapse
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.
I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Cracken6 said:
I removed battery, reconnected after a while, still same problem.
So I tested it with multimeter, it says 2.6V, but fully charged must be 3.8V. Could this be a problem? I was charging it for whole night.
Click to expand...
Click to collapse
I had the same problem a year ago, I tried to remove the battery, charging all night, and other solutions that I found online and no one worked.
Finally I found here in XDA a user with the same problem and his solution was charger the phone with a wireless charger, a friend of mine has one and I put the phone to charge and after a few minutes the screen goes on and the phone was charged, then I press power button and the nexus run again.
Hope this works.
Sorry for my bad English, I'm from Spain.
Good luck.
(I bought a wireless charger in case it happen again)
I don't know anyone with wireless charger. I already ordered a new battery, and then I probably will get wireless charger also. Ty.
But this problem is very weird if you think so.. I think it happened because of many aspects together:
1) Battery was already below 30%
2) I pretty regularly charge phone with USB (won't do it again)
3) It was connected to PC USB in same time.
4) I installed CM12 ROM in same time
So main reason I think is USB, that I restarted phone while it was on pretty low battery and with USB connected.. phone restarted and got invalid voltages and couldn't even boot up or charge phone. I also found an article which says, minimum voltage, when phone battery has 0%, it's 3.0V, so I was below that.. it just screwed everything and battery died. Well, I am not sure for 100% that it's battery fault, but I hope so, I really love my N4 and still wanna use it for long time, I hope it's not dead phone, just a dead battery. Lets see! I will update this thread , when I get my new battery (less than month probably).
Sorry, my english is also not perfect. I am from Latvia.
I was playing when it happened to me. The phone was very very hot and the battery was around 70%. When I put in the wireless charged and I can reboot the phone the battery was at 65%, so it had charge but the phone won't boot.
I charge my phone almost every day, sometimes with AC, others with USB (plugging to PC) or wireless that depends of my needs
I hope you can fix it. Good luck.
Btw. Do you know if battery charges with wireless charger, if it's removed from the phone?
Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.
Flipz77 said:
Don't think it does, since the receiving coils for wireless charging are located just behind the glass back.
Click to expand...
Click to collapse
The battery will charge with a NCF Charger
Major Issue Google
This "Nexus SOD" issue is showing up on many sites across the Internet. I have multiple "Nexus" devices including 2 Nexus 4, 1 Nexus 5, 2 "Nexus 7 2013". It suddenly started out of the blue with one of my Nexus 4 phones. Symptoms included rapid battery discharge. I am using Lollipop 5.1 on all devices. There are many claims as to the cause, Hardware Motherboard, Power Button etc. Others claim it is "Software Related" or App Related. The problem effects Nexus 4 and Nexus 5 phones. I have ordered a new motherboard for my nexus 4 device and see if that makes a difference.
This problem should warrant a "Major Android Lollipop Crisis Team" by Google to investigate the cause and let us know what it is and what Google is doing to solve the problem before moving to announce "Android M". This issue needs to brought up and actively pursued at the upcoming "Google I/O Conference" by the strong Android Developers Groups to press for "Formal Action"
charging method
Cracken6 said:
I have tried that many times. Nothing. It's bootloader screen, but I can't get there. Nothing happens. If I keep holding volume down+power it just keep blinking once every ~10 seconds, same if I hold just power button. If phone is not connected to charger, there are no blinks at all.
Click to expand...
Click to collapse
I had this problem a long time ago and my fix worked for me after doing a little research it seems like this is a case called battery total discharge. The fix was simply to charge your phone using the wall adapter that came with your phone (I still use my old apple cube wall thing) and to wait for the red light to appear then wait about ten minutes before trying to reboot.
I just got new battery . But it looks the same.. phone doesn't boot up.. same red light blinks once.. so.. its my phone is dead? I can't believe that...
When I connect to PC usb, there are unrecognized deviced called "QHSUSB_DLOAD".
Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help
AndRe5575 said:
Maybe this video will help you: Oh I´m not allowed to post links until now.
Just search for: - Nexus 4 "red light of death" fix - at youtube.
Hope it will help
Click to expand...
Click to collapse
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...
Cracken6 said:
I have checked all kind of videos there. Also that one. Most of these cases are related to battery, but it seems in my case it isn't. I just searched for QHSUSB_DLOAD unrecognized device, all posts says it means phone is bricked... But cmon, how? I installed CM12, successfully, without any errors, then just restarted phone, and its dead...
Click to expand...
Click to collapse
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved
as9333 said:
Did u try booting the phone without battery by connecting to wall charger and what about flashing stock ROM via PC
Also check that the power button works
This case should be solved
Click to expand...
Click to collapse
Just tried booting without battery, and connecting to wall. Same - red light blinks once, after I hold Power button or Power+Volume down for about 15 seconds. If I keep buttons pressed, it just repeats every ~15 seconds.
Power buttons works fine.
After I checked that Device manager thing in google.. it looks very bad.. phone is dead.. probably need to change motherboard. I am just shocked, how this could happen... I didn't receive any errors during CM12 installation. Phone just instantly died after restart.
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)
My phone doesn't turn on nor can it turn on in recovery mode neither and seems to be dead... The only signal of life is the blinking white led next to the fingerprint scanner.
Here's how this happened: The phone was charging very slowly, I thought this was a problem with the cable so I tried other ones without success, I continued using the original, days later it stopped charging so I opened the phone very carefully and saw the battery conector raised ever so slightly, I pushed it back in place and noticed that the flash flex cable had some kind of bump that was caused by some kind of chip under it, maybe I sat on my phone some day and caused this but I don't really know. So I reassembled the phone and now it won't turn on.
I've tried to "unbrick" the phone since apparently that's what causes the blinking white led and not being able to turn on the phone, but unfortunately, the phone won't get recognized when connected to a computer, this means I can't do the unbricking.
I want to know what else could this mean? Is the motherboard dead? Would the led blink even when the motherboard is dead? What can I do?
I've tried(in order to get my phone to show up on the computer):
*Using different kind of usb cables(including the original).
*Connecting to other computers.
*Installing Qualcomm and Motorola drivers.
*Running PC on test mode and disabling signature checks.
Please tell me your opinions, do I buy a new phone or is this fixable?
Originally, I would have thought your issue might have been to do with the charging port (possibly explaining that your device can't be identified).
Just to confirm, all the connectors that you saw, including those attached to the motherboard, are all connected and it's a good connection?
It's entirely possible the motherboard/flash memory is dead - so not being to load the bootloader, though I would have thought you'd be able to see Qualcomm HS-USB 9008 in Windows if your device can't boot to the bootloader (it'll drop to the Emergency Download Mode).
I honestly do not know what the issue/issues might be, though you could take it to a service centre/repair shop and see what they say (get them to inspect the device). Given what you've described, it's possible you may be better served by a new device rather than spending money fixing up this one.
echo92 said:
Originally, I would have thought your issue might have been to do with the charging port (possibly explaining that your device can't be identified).
Just to confirm, all the connectors that you saw, including those attached to the motherboard, are all connected and it's a good connection?
It's entirely possible the motherboard/flash memory is dead - so not being to load the bootloader, though I would have thought you'd be able to see Qualcomm HS-USB 9008 in Windows if your device can't boot to the bootloader (it'll drop to the Emergency Download Mode).
I honestly do not know what the issue/issues might be, though you could take it to a service centre/repair shop and see what they say (get them to inspect the device). Given what you've described, it's possible you may be better served by a new device rather than spending money fixing up this one.
Click to expand...
Click to collapse
Thanks for the reply, I checked all connectors and none seem to have problems so I'm going to take it to a repair shop as you say, depending on what their diagnose is, I'll consider buying a new phone. Once again, thank you.
wasteoflife said:
My phone doesn't turn on nor can it turn on in recovery mode neither and seems to be dead... The only signal of life is the blinking white led next to the fingerprint scanner.
Here's how this happened: The phone was charging very slowly, I thought this was a problem with the cable so I tried other ones without success, I continued using the original, days later it stopped charging so I opened the phone very carefully and saw the battery conector raised ever so slightly, I pushed it back in place and noticed that the flash flex cable had some kind of bump that was caused by some kind of chip under it, maybe I sat on my phone some day and caused this but I don't really know. So I reassembled the phone and now it won't turn on.
I've tried to "unbrick" the phone since apparently that's what causes the blinking white led and not being able to turn on the phone, but unfortunately, the phone won't get recognized when connected to a computer, this means I can't do the unbricking.
I want to know what else could this mean? Is the motherboard dead? Would the led blink even when the motherboard is dead? What can I do?
I've tried(in order to get my phone to show up on the computer):
*Using different kind of usb cables(including the original).
*Connecting to other computers.
*Installing Qualcomm and Motorola drivers.
*Running PC on test mode and disabling signature checks.
Please tell me your opinions, do I buy a new phone or is this fixable?
Click to expand...
Click to collapse
Try to hold the power button and the volume down buttons together for more than 2 minutes. My moto g4 goes dead sometimes and nothing I do will turn it on except holding those buttons for like 2 to 3 minutes then it reboots to fastboot and turns on. It might not work but it works for mine and its worth a shot. It takes a few minutes and I dont know why but it does no more 3. Let me know if it worked.
Last night I've put my Mi 9t to charge and went to sleep. When I woke up, the phone was turned off.
I've tried to restart it and also pressed the volume + power button combinations to force the recovery mode - unsuccessfully.
No blinking lights, no MIUI entry, no vibration, zero response from the phone. (Is it bricked?)
I've started to research and since my computer can't find the Mi 9t (running Windows 10) the only solution seems that to disassemble it and do the EDL Mode Test Point, to acess the recovery mode and try to flash the phone.
Do you have other sugestions to try?
Martholas said:
Last night I've put my Mi 9t to charge and went to sleep. When I woke up, the phone was turned off.
I've tried to restart it and also pressed the volume + power button combinations to force the recovery mode - unsuccessfully.
No blinking lights, no MIUI entry, no vibration, zero response from the phone. (Is it bricked?)
I've started to research and since my computer can't find the Mi 9t (running Windows 10) the only solution seems that to disassemble it and do the EDL Mode Test Point, to acess the recovery mode and try to flash the phone.
Do you have other sugestions to try?
Click to expand...
Click to collapse
This is weird. Maybe it's not charged? Did you try another charger and/or cable? How can the phone get bricked overnight by doing nothing? Never heard of it.
edittt
attitude12 said:
This is weird. Maybe it's not charged? Did you try another charger and/or cable? How can the phone get bricked overnight by doing nothing? Never heard of it.
Click to expand...
Click to collapse
I've tried today during all day with a different charger, no response.
It's the first time a thing like this happened to me as well. I've never flashed it before or did any major modifications. I was running MIUI 11 still.
If the battery runned out how can I revive it?
On another forum a user told me it could be the integrated circuit broken or a battery problem.
Martholas said:
I've tried today during all day with a different charger, no response.
It's the first time a thing like this happened to me as well. I've never flashed it before or did any major modifications. I was running MIUI 11 still.
If the battery runned out how can I revive it?
On another forum a user told me it could be the integrated circuit broken or a battery problem.
Click to expand...
Click to collapse
Then I really don't know. Like I've said, never encountered this before. You could try going to a repair service.
you could open backcover and charge battery directly to see if thats usb problem
You can make an EDL cable. is very easy to do and you have a lot of videos and pictures about it.
Dont worry if you have to open the phone is really really easy. With a hot air gun or a hair dryer you can do it in 2 minutes. You are going to need also a piece of radiography to separate the cover
Then the test point is really easy to do it, check some pictures in google, also you can check the usb port if it is damaged or not once the phone is opened, but of course if the phone stoped working from day to night is weird a usb faulty port
Pls don't open anything or try an trick. Just take it to a repair service so u don't make things worse
I've tried the test point and didn't work, as well
So I took it to a repair shop that accepts xiaomi. They are going to order a new battery and a battery connector (2-3 Weeks).
I'll post when I'll get more updates.
I had a lg g3 that did the same thing. Charged it over night and it didn't work the next morning, could be power surge. Ever since then I never charge my phone over night
So, I've picked it from the repair shop and they couldn't fix it. They changed the battery, the battery connector and the display. They said they don't have a solution for the phone.
My next step is to contact gearbest to see if they have a solution for me.
Martholas said:
So, I've picked it from the repair shop and they couldn't fix it. They changed the battery, the battery connector and the display. They said they don't have a solution for the phone.
My next step is to contact gearbest to see if they have a solution for me.
Click to expand...
Click to collapse
It must be the mother board then, Same with my old lg g3.