[HELP] Phone fell down the road, now stuck in bootloop - Xiaomi Mi 5 Questions & Answers

Okay here it goes, I held my phone while riding my motorcycle and suddenly it fell down. Back panel shattered but fortunately it's just minor damage on the screen.
Now, it stucks in bootloop. I can still access recovery(TWRP, made a backup) and fastboot. I tried to wipe cache/dalvik and wipe data but still no avail. Any other options??

Related

[Q] Bootloop and Volume down not working

Hi folks. I think I may have kill by beloved m7.
The volume button was a bit sticky for a few weeks after I accidentally dropped it in a tiny puddle. The volume down only would stick about 80% of the time. I controlled volume down by using the volume up and then using the slider on screen.
Today I was loading a ROM, and when it booted it gave a few forced closures. Odd, as I always delete cache and dalvik cache prior to rebooting. Anyway, I turned off the device, rebooted, and to my horror it is now looping.
As the volume down is obviously sticking, I cannot get back into recovery through bootloader.
Is there anything I can do other than reboot it a million times and hope that the volume engages at some stage?
Just an update on this in case anyone else has the same issue - or if you have issues with your volume rocker.
Be very careful as it appears there is no way round it, and in effect the phone is permanently softbricked, Luckily I have insurance but it is going to take three to four weeks to sort out.

[Q] Unresponsive screen fixed by tapping ME572C

Couldn't unlock the screen of the ME572C, screen unresponsive, booted to recovery, wiped cache, still unresponsive. Tapped the back of the tablet and it started working. I assume something is loose inside, any one know how to fix this so it won't happen again?

Major problem. Phone Stuck at start up logo

This morning during a call my phone shuts off for no reason. It is not rooted no physical or water damage. I tried to power it on it will vibrate than attempt to start get stuck at boot screen than eventually turn black. I tried booting into recovery to hard reset I will get to the menu do all the prompts and get the lg logo and back to black screen. I don't know what is going on. Is this a common issue? Admins if this is in the wrong section feel free to move it.
Kingaries79 said:
This morning during a call my phone shuts off for no reason. It is not rooted no physical or water damage. I tried to power it on it will vibrate than attempt to start get stuck at boot screen than eventually turn black. I tried booting into recovery to hard reset I will get to the menu do all the prompts and get the lg logo and back to black screen. I don't know what is going on. Is this a common issue? Admins if this is in the wrong section feel free to move it.
Click to expand...
Click to collapse
Not sure what caused the issue but if wiping from recovery doesn't work I would look into restoring phone with kdz file. Sucks to do that seeing as all data will be gone but hopefully you have a backup. If restore doesn't work you need to call T-Mobile for replacement
Sent from my Porn Infested G4
The replacement has been processed. Unfortunately trying to factory ? reset doesn't work because the phone ? wouldn't stay on long enough for that to happen. Love to know what actually caused this issue. Kinda kicking myself for not doing a weekly backup.
I actually got the same problem on mine but mine is rooted and was working fine but then randomly my phone is doing bootloop. I don't have terp installed and I'm I only able to boot up to software upgrade mode. Ive tried the step for format everything with holding the volume up n on button but after I did the reset stuff still does boot loops. Also another problem is that whenever I plug in phone to computer it doesn't show up, so I have no option to add roms or anything like tht to internal or sd card. Is there anyways too flash anything of the software mode, if so can you plz let me know thank you.

Sudden death... repaired... then dead again (after failed nandroid restore) :'(

This looks like yet another sudden death post... or is it?
Some days ago I had my beloved Z3C repaired from a sudden death.
Motherboard replaced, as expected.
Back home, I flashed KitKat, gained root access, installed recovery, then proceeded with the TWRP restore of a backup from last December.
The restore went smoothly until 99%, when suddenly I got the infamous "extractTarFork() process ended with ERROR=255"
Now bear with me.
I only remember a "reboot system" button available on the screen.
I don't recall a "back" button to stay in the recovery, or at least I didn't see it.
So I went on and pressed "reboot"... and my phone never rebooted.
Dead again.
Now my question is *not* "what can I do to wake it up", because I am 99% sure it is really dead again.
Power + Vol UP won't do a thing, no 3 vibrations, nothing; Vol DOWN then plugging usb to trigger flashmode with flashtool does not work, either; besides, the led is faintly blinking red when plugged in for recharge, which to me is a sign of hardware failure.
So I guess my question is rather "did *I* do it?"
I know a recovery sits in a dedicated partition and uses its own kernel, so why in the world if a restore goes wrong shouldn't I be able to reboot and go into recovery again?
I feel pretty stupid now.
I am afraid I will have to pay this second repair.
any news i have same probleme
This does sound very werid, It almost sounds like trying to flash a custom rom on locked bootloader, although usually you can come back from that.
Now there is a reboot button under the sim flap, from memory it is a little yellow square, you could try and press that (Using a pin or something) and it *may* boot your phone back up.
Through all my failed rom flashes and etc, i have never had this happen to me, could be faulty hardware...
WHY should you pay for it if it is under warranty?
Murphy laws exist for reason.
If the motherboard is dead, there is no way for most of the technicians to know what the hell happened.
that's why i never use nandroid restore.

Device is not recognised on PC - Driver issues or phone died?

Hello there! During my holidays I accidentally slipped into a swimming pool while holding my Mi 9 Lite on my hand :crying: . The device was merged into the water for no more than 2-3 secs but seemed enough to do some damage (apparently). At first the device was in a loop booting again and again in the mi recovery mode, i gave some time to dry it and suck the water off the phone. At the end of that day i tried to turn it on but after the mi logo and the vibration the mi logo seemed to fade out and the screen turned off. I got into the mi recovery mode, did wipe all data, but still the logo died after a few seconds i tried to turn the phone off... I am trying to use fastboot and miflash in order to flash again the stock rom, but no mater what i did, the device is not recognised by the pc. I did manual install the drivers, used adb, set the device as portable device, but still im not able to connect the phone in order to proceed with the flash... Is there a way to fix it because the device seems to work and respond properly (buttons on the recovery menu, the image of the fastboot looks perfect etc..), or it is permanently damaged ?
Vassilis_ said:
Hello there! During my holidays I accidentally slipped into a swimming pool while holding my Mi 9 Lite on my hand :crying: . The device was merged into the water for no more than 2-3 secs but seemed enough to do some damage (apparently). At first the device was in a loop booting again and again in the mi recovery mode, i gave some time to dry it and suck the water off the phone. At the end of that day i tried to turn it on but after the mi logo and the vibration the mi logo seemed to fade out and the screen turned off. I got into the mi recovery mode, did wipe all data, but still the logo died after a few seconds i tried to turn the phone off... I am trying to use fastboot and miflash in order to flash again the stock rom, but no mater what i did, the device is not recognised by the pc. I did manual install the drivers, used adb, set the device as portable device, but still im not able to connect the phone in order to proceed with the flash... Is there a way to fix it because the device seems to work and respond properly (buttons on the recovery menu, the image of the fastboot looks perfect etc..), or it is permanently damaged ?
Click to expand...
Click to collapse
I don't think water damage is covered under the warranty. You could try to point a torch down the USB-C port and see if you see any obvious corrosion blocking the port. If you see some then you could use a toothbrush and some isopropyl alcohol to carefully clean out the port. If that doesn't resolve it then it is likely that the water has gone through your phone and has caused damage to components.

Categories

Resources