Hello!
I have a Xiaomi Mi 5 Pro running Global 7.2.8.0.0 Stable. I wanted to unlock my bootloader to install a custom rom.
The sms with unlock permission pin from xiaomi support was already on my device.
My actual rom had no oppurtunity to link the phone with my xiaomi account. So i tried to do a system-update.
That's when i noticed that my phone seems to be on a shop-rom and that i need a deep flash cable to get rid of it.
Because my phone felt a little laggy to me, i decited to do a factory reset. And then the bad supprise happened.
It hangs in a bootloop, showing the recovery image (white phone with cable on black ground).
When i hold volume down, i'm still able to boot into fastboot.
I've ordered a deep flash cable, but it can take 30 days to arrive.
Can somebody help me out? I'm grateful for any hint or help!
best regards
If u are able to boot in to fastboot is it miflash working
Hello,
I have a bootloop on my mi note pro.
I deleted everything, wiped after that i flashed room 6.1.7 china stable and phone dosent start.
I flashed many other rooms and xiaomi still gets into recovery, its going recovery all the time if i turn on.
I can enter into fastboot there is no problem, i was flashing by oem edl, bootloader is unlocked, my pc dosent recognize device as mass storage so i cannot put any rom to it.
Well after new room flashed the xiaomi stays on logo and after 1h there is nothing more, still logo.
In recovery i can move only down by vol- i cannot move up thats normal or i had broken button?
I was trying to dismount buttons and then start my phone and i get same result... recovery.
I was trying to flash 3 other twrp, same thing.
Maybe i doing something wrong, dont know. Please help me.
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and got all the flashing related fastboot commands working i've
Flashed a stock image using the miflash tool, seems to succeed but then on reb but once it's done i'm still in a boot loop!
I've been able to boot into twrp a few times (though most of the time I can't and am still in a bootloop)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Throughout the last few hours i've also managed to hit the os a couple of times but it seems very easy to accidently put it back in a bootloop.
If anyone has advice of something to try, that would be great.
(was trying stock image version 10.0.9.0, going to try and go back to stock Oreo)
Smtih said:
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and flashed a stock image using the miflash tool which all seems to go swimmingly, but once it's done i'm still in a boot loop!
Throughout the last few hours i've managed to get into the os a couple of times.
I've been able to boot into twrp a few times (though most of the time I can't)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Sometimes it goes to a failed to boot screen, while other times it seems to loop endlessly.
If anyone has advice of something to try, that would be great.
(was trying image version 10.0.9.0, going to try and go back to stock Oreo)
Click to expand...
Click to collapse
Try some custom kernel, or patched boot img
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
Yeah, A2 have A/B partition and if update is faulty and the phone ends in bootloop, after a few failed boots, it will boot from other partition.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Smtih said:
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Click to expand...
Click to collapse
Plss post the link of 10.0.10
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!
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