Yesterday evening I downloaded lineageOS on my device. I did not activate it in any way, the unextracted .zip file stayed untouched in internal memory.
Phone wasn't charging and it died at night. Plugged it in in the morning, unplugged when at 80% battery, and tried to turn it on.
Now when turned on, it immediately turns off after displaying my wallpaper and prompting to unlock SIM card. It switches off immediately, regardless of touch or button input.
When in recovery mode, phone is not recognized or at all seen by Windows and, by extension, Mi PC Suite.
All PC USB ports work fine with other peripherals. Phone was never rooted, the lineageOS .zip file is the only tinkering I've done so far. It worked well, until turned off and on.
[email protected]
Related
Hi there,
i've got a problem with my Mi3. Suddenly, it has "stopped" charging. Actually it charges when it wants to. Sometimes I plug it in and it begins charging, some other times it doesn't. However, it only goes charging for some minutes and then... bluff!! Stops.
I've managed to fully charge it if I turn the device off, then I plug the USB charger and, next, I turn it on again. The only way i've found.
However, I cannot connect it to my computer, it doesn't recognize the device at all. The computer shows "Windows cannot recognize the USB device because bla, bla, bla...", but it does this in a loop. I cannot stop it unless I unplug the device. Moreover, I cannot find the device in the Device Manager. I could flash a fastboot file this morning to check if the problem was in the ROM. No way.
Any idea or Suggestion?
Thanx!
Looks like you're USB has doomed.
My SM910T was working fine, and suddenly the screen froze for a few seconds, then blanked.
From that point on, the phone has done nothing but a brief vibration.
After a battery pull, starting up with 1) normal power switch 2) download startup 3) recovery startup 4) inserting USB cable
all result in the same: A short delay, a brief buzz from the vibration, which may repeat again every few seconds. The screen remains black.
When connected to a Windows computer with USB, the phone is enumerated. It shows up as these devices:
SAMSUNG_Android SAMSUNG Mobile USB Component,
trtlemo
Port #0004 SAMSUNG Android ADB Interface.
ADB does not work. The command "adb devices" returns the null list (List of devices attached)- it does not see any device attached.
Windows sees the phones internal file system as an MTP drive, and shows the file structure, but the files are not accessible.
ODIN sees there is a phone attached (it says <ID:0/004> Added!!)
What mode or state is the phone in, and what should be done to restore normal operation?
You may simply have a bad battery. Have your tried another?
Sent from my SM-N910T using Tapatalk
rcobourn said:
You may simply have a bad battery. Have your tried another?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I don't have another battery, but I can order one. I can't prove that the battery is not bad, but I don't think that is the issue. It runs the phone and is only down to 65 to 75% at the end of a day under normal use. At the time this problem started it was a bit lower, I think about 50%.
Even though the display was black and didn't show the charging logo, I left the phone on the charger with the battery inserted for 8 hours. It still didn't boot normally.
Assuming the phone had a hardware problem, I initiated a warranty replacement process. I wanted to see if any of my existing software tools could wipe the internal data before returning it so I tried a few (as described above). One I hadn't tried was Kies. I connected the phone to USB, and let it settle (USBdeview showed the phone connected and disconnected about 8 times before stabilizing). Then I ran Kies3, and saw the Emergency Recovery on the tools menu. I opened it to see if it would recognize the phone. The phone did not appear in the "list of devices requiring emergency recovery". However, after doing that, the phone booted normally. I don't know what Kies3 does, or if it did anything - maybe it was just a coincidence. But the screen activated, and the phone booted normally. The battery was charged, so it appears that charging does take place even if the system does not boot.
Hello, my phone was fine today, then I put in my bag and went to do stuff, when I came back, I found the phone not working (black screen, no responses).
I thought maybe the battery died, but when I put in the charger, still nothing happens (no charging LED notification, no charging screen). When I plugged it to a computer, it recognized it but still no LED/screen and I cannot access the phone (because of fingerprint security). Recovery and download mode obviously aren't working either.
What could it be? The phone is out of warranty as it's rooted.
Thank you!
So it all started suddenly for no reason at all. It just went off. The same way it had gone off, it came back to life, again, for no obvious reason. I just left it charging overnight. Now it boots up just fine, but my PC won't detect it, regardless of its current state, i.e. Flashmode, fastboot mode or on the OS. I also tried another PC, no clue. FYI, when the phone is on and I connect it to my PC, absolutely nothing happens. No light or anything. And when it is off and I plug it in, the red light turns on and the battery sign shows up, but it's not actually charging.
Oh, and, I do have proper drivers for everything installed, along with Flashtools.
Hi, I have a strange problem with me a2.
The phone after the last update did not want to turn on (the startup screen looped).
The system works thanks to the options of original recovery
Currently everything runs (I think) but has a problem with the cable connection.
After connecting the charger for 5 seconds, it shows charging, after which the phone loses connection, as if I disconnected it from the electricity.
When I want to connect it to my computer, nothing happens.
I suspect that this is still a problem with the system because the phone is charging with the recovery turned on.
I wanted to unlock it and upload the modified recovery to protect myself against miraculous updates in the future.