Hello everyone, my phone (Redmi Note 9 merlin) has started bootlooping. It can boot to fastboot, but is unable to boot to recovery (either through fastboot reboot recovery or Vol + during boot). I have tried using SP Flash Tool using the hard brick tutorial and it still bootloops even though all steps proceed normally. I have tried to flash both old and new versions of MIUI, and all of them stlil do not work.
My bootloader is still locked so I am unable to use fastboot or other tools (like MiFlashBoot) on it.
Trying to unlock it from Mi Unlock gives me an error (1004). It seems to be due to the SIM card not being the same but I have not touched the SIM card since I got the phone.
In the past I have used MiPhoneAssistant to restore it as I could access recovery mode, but now even recovery mode is out of my reach.
What should I do now?
Thanks for your time.
Do you know what could cause the boot looping? The most common one is after installing a new version of MIUI.
I'm not sure how it happened, but if it is caused by a MIUI update, how would I go about fixing it?
If it has a locked bootloader and it's still in a warranty. Visit the store where you bought it from and claim the phone has stopped working and started bootlooping.
Related
Hi guys,
So I had a stock T-Mobile LG G4 H811 that I had unlocked and booted into twrp version 3.1.1-1-g4. I wasn't able to actually flash recovery of this .img becuase of a write failure. So I booted into it instead and then installed it from within twrp into the recovery partition. The actual stock software was the ORIGINAL original, which I think was android 5.1.1
From there, I cleared the cache and delvik cache and installed the G4-H811-10N-xTreme-2.0 Rom. Now, I can't boot into recovery mode anymore, and all I get is the bootloop.. but it's not dead yet because it's a software issue on my part and not a hardware failure.
Any advice on how to get it to recovery mode or at least so I can boot into twrp somehow to try and get this fixed? I tried Power+Volume Down and then let go a sec and Power+Vol Down again and it won't work at all. Just goes straight to bootloop.
Thanks in advance.. I know I screwed up somewhere.. just so many loopholes, it's easy to miss.
Best,
Johnnie
Got somewhere, still broke
Well, somehow I managed to boot into recovery mode only 1 time and installed the stock Tmobile rom. It installed, but now I get a white T-Mobile screen on boot up and it stays there. I tried using the LG Flash Tool 2014 and the stock T-Mobile H811 10N firmware for T-Mobile, but all I get is connection to server errors and the software won't install to the phone over download mode. Anyone else have this problem? I've been trying to figure this stupid thing out for 6 hours. Also, I'm wondering if installing the stock firmware caused the original recovery partition to go back to stock too which is the reason I'm no longer able to boot into recovery mode? It just doesn't recognize it. Power+vol down and then vol down doesn't do anything.
When using the LG Flash Tool 2014, all I get is Connection to Server Failed, Try again. So I do, and nothing. It fails at 9%
Thanks.
jtlefebvre said:
Well, somehow I managed to boot into recovery mode only 1 time and installed the stock Tmobile rom. It installed, but now I get a white T-Mobile screen on boot up and it stays there. I tried using the LG Flash Tool 2014 and the stock T-Mobile H811 10N firmware for T-Mobile, but all I get is connection to server errors and the software won't install to the phone over download mode. Anyone else have this problem? I've been trying to figure this stupid thing out for 6 hours. Also, I'm wondering if installing the stock firmware caused the original recovery partition to go back to stock too which is the reason I'm no longer able to boot into recovery mode? It just doesn't recognize it. Power+vol down and then vol down doesn't do anything.
When using the LG Flash Tool 2014, all I get is Connection to Server Failed, Try again. So I do, and nothing. It fails at 9%
Thanks.
Click to expand...
Click to collapse
try using LGUP
So I successfully rooted my lg k8 2018 (lg aristo 2). I decided to install gravitybox and turned on some things. I rebooted my phone and now it's stuck on the boot logo. I can't boot into recovery because I get the bootloader is unlocked message. (Not possible to re-lock it w/o putting my phone into a boot loop). I can get into fastboot by holding down and plugging in my phone. What should I do?
Update: I need to be able to get into recovery to flash xposed uninstaller. However, because I get the bootloader is unlocked message, I cant. I tried at least a thousand times. I also tried the button combination to disable xposed on startup. That didn't work. It was running android 7.X (I think 7.1 or 7.2)
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.
Hi there guys, yesterday i tried flashing a twrp recovery on this phone via adb fastboot.it was smooth and seuccessfull but everytime i tried going into recovery mode thereafter, it just got stuck on MI logo/blackscreen (but it can properly boot). So i tried reverting to the stock rom and surprise surprise eventhough the whole process wrnt smoothly, it would still loop or blackscreen everytime i boot intl twrp. Interesting thing is, idk if the recovery rom i downloaded was specific to cancro version only or not.at this point, im just floored because i have no working recovey.any help would be abdolutely appreciated guys.sml
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
utundu said:
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
Click to expand...
Click to collapse
Try sideloading an OTA image. You can do that with a locked bootloader.
Thanks Lughnasadh
I've tried multiple times, and the process fails randomly, at different percentages ...
The phone suddenly reboots and the laptop displays " adb: failed to read command: No error"
The weird thing is it doesn't reboot and can stay up for super long while on the bootloader.
With a locked bootloader the rescue OTA (full OTA image flashed via adb) is all you have. I would try a different data cable (A-to-C) first and then move to a different computer. Make sure the new PC is running the latest adb/fastboot binaries. This is why I unlock the bootloader on every Pixel in my family. Even though they will never root the phone, if the fit hits the shan you have many more options. BTW, I just traded in my son's P4XL and got $285 trade-in on a 6a. Net cost was less than $150. The deal just ended but will likely come back again. Same deal was offered earlier but included a pair of first-gen earbuds. Wish you luck on getting your old phone working. The P4XL is still my primary phone and is still working well.