Hi everybody!
I recently purchased mi 11, after owning mi 10.
Since recently, a strange thing happens after some time. After using phone for a while, the sound does not work. After restart, the phone goes through boot proces, miui logo shows up, and after that only the black screen appears.
I then would go to the recovery mode, select safe mode or repair mode, and after couple of tries the phone boots normally. Everything else works, it is on global miui, bootloader is not unlocked.
Anybody has any idea why is this happening and is there a solution?
Thanks!
Related
hello, i was using normally my phone. then it suddenly restarted itself. it just do that.. finish booting up i get into the home screen, i have time to unlock it, then it freeze up.. and 2 sec laters auto reboot...........
i tried enter in safe mode.. nothing happens
and well. im still waiting to get into recovery mode, it got 6 mins in the teamwin screen
what i can i do help
Sounds like a broken recovery. Reflash in odin
I got the same problem, flashed team w recovery, tried another kernel and still got this issue, it freeze, the screen turns a little white then reboot, WHAT CAUSE THIS? HELP!!
TLDR: Dropped phone. Broke screen. Battery ran out (while waiting for replacement screen). Replaced screen. Phone bootloops at Mi logo. Able to boot to fastboot. Able to unlock bootloader and flash stock rom, but bootloops continue.
...
I recently dropped and shattered the screen of my Mi 8 Global (128Gb, purchased from GearBest), and was not able to see anything at all.
While waiting for a replacement screen I ordered online, I tried to turn off the phone, but it didn't seem very successful - sometimes, when handing the phone, I could feel it vibrate a little when I touched the fingerprint sensor with another finger. After some time, I guess the battery ran out.
New screen arrived, and I was able to replace it - however, while testing the screen (motherboard, battery, new screen only), the phone would bootloop at the mi logo. Not much else I could do, except reassemble it with the new screen and try figure out what's wrong.
Plugging in a charger, the same thing happens: mi logo bootloop; charging led does not light (I seem to recall that it did not light too when I plugged in a charger with the broken screen, before I disassembled the phone)
Holding down up+power button; or up+down+power has no effect, and same thing happens: mi logo bootloop
Holding down+power button brings me to fastboot mode.
In fastboot, I am able to unlock the bootloader with miflash-unlock; I had requested for permission and linked my phone with my account when I first got it. Mi logo bootloops continue (With 'unlocked' displayed)
In fastboot, I am able to flash dipper_global_images_V10.1.2.0.PEAMIFI_20181211.00 00.00_9.0_global_0099f5af5f.tgz with xiaomiflash successfully. With 'clean all' Mi logo bootloops continue; even after flashing twice. Same with 'clean all and lock'. Mi logo bootloop (but 'unlocked' is no longer displayed). I am able to unlock the phone again with miflash-unlock.
Any suggestions on what I can try to do from here? Pretty much at a loss now.
Bump for help.
Any suggestions on what I can try to do to recover the phone?
If anyone is wondering, my phone booted correctly after flashing with the current ROM (dipper_global_images_V10.2.1.0.PEAMIXM_20190110.0000.00_9.0_global_4d02fd6c97.tgz), downloaded from here, via fastboot. Earlier version would result in a bootloop.
Just a quick update.
The latest Miui Global Rom (V10.3.3.0.PEAMIXM) can't boot on my phone, and I have to stick with the previous (V10.3.2.0 PEAMIXM) for now. It doesn't loop, just gets stuck at the initial Mi screen; this also happens if the bootloader is locked and updated via OTA.
Official TWRP versions also can't boot, but TWRP by LR Team (from here) works.
Lineage OS 16 bootloops.
I'm not exactly sure why replacing the broken display causes this, or what I can do to try figure out what the problem is; but I thought someone else might find this information useful.
Hey guys!
So my girlfriend's Xiaomi Mi 9 (Global Version) suddenly entered a black screen and became unresponsive. No LED when charging, no connected sound when plugged into the pc. She managed to turn it on through fastboot mode twice, but it eventually entered the black screen again and now not even fastboot will work. She has never flashed any custom ROMs or rooted her phone and afaik she's on the latest version of MIUI. Any tips on how to get it working again?
hey friend.. i have the same problem...and i have sent the phone to the service..do y know what hapenned?
I wanted to copy all my titanium saved apps to my new phone and before that i put the mix for charging.
I noticed that the screen went on and off many times , it showed the reboot/turn off buttons appearing and dissapering and then it went off and shows the mi logo going off and again, since an hour.
i tried to access the custom recovery but after a few seconds it goes back to the mi logo
same happens when entering fastboot
i think i had the same thing a few weeks back but there i could enter recovery and wipe cache and then it went back on again but this time i can not access anything
any ideas what i could do?
Hello there, I`ve got a problem with my Xiaomi Redmi Note 10 5G.
After I`ve flashed TWRP, when I turn on my Phone, it doesn`t boot.
The first time it did llike this the accu was next to empty.
So thought, when I would buy a new accu, I would be able to flash it again, but now I've put a new accu in but It's also not possible to flash it again.
I've got a broken Display on this phone, too.
Yesterday I've ordered a new Display.
Today I've tried to boot into Fastboot Mode, so I would have known that it's booted into Fastboot Mode, if there is shown a device in the CMD.
Before I get the new Display, please help me to "Unbrick", I think it's bricked, this phone.
I don't know what I can do.
Bootloader is opened and I think I bricked it by flashing TWRP. And the accu could has been a problem, because it was next to empty.
JonnyBoy84
i dont understand if your phone can enter into fastboot. your message is not clear