Phone stuck at Mi logo after flashing TWRP - Xiaomi Redmi Note 4 Questions & Answers

Hi, so I flashed TWRP recovery and booted into it immediately. However, I forgot to flash the lazyflasher zip and rebooted straight away. Now the device is stuck at the logo and I can't seem to get to fastboot or recovery mode using the command line. I read a few other threads similar to my issue but apparently, they could access fastboot mode and I can't. Am I missing something?

ProBlast said:
Hi, so I flashed TWRP recovery and booted into it immediately. However, I forgot to flash the lazyflasher zip and rebooted straight away. Now the device is stuck at the logo and I can't seem to get to fastboot or recovery mode using the command line. I read a few other threads similar to my issue but apparently, they could access fastboot mode and I can't. Am I missing something?
Click to expand...
Click to collapse
Have you tried pressing Volume plus + power button to boot into recovery or Volume minus + power button to boot into fastboot mode?

Solution
It also happened to me but I booted into twrp and flashed an custom rom and also the lazy flasher.zip after couple of minutes it booted up. It may help you

Related

[Q] [Brick] [Lanix Ilium x200] Flashed twrp.img as boot image in Flashify

Hi all!!
I have a Lanix ilium x200, which is a legacy device running 4.4.4. I rooted it with iRoot, and I followed an online tutorial I found to try to get twrp. It told me to download an unofficial flashify by Christian Göllner and flash twrp.img as a boot image. I did that, but halfway, I realized that didn't make a lot of sense, so I stopped it, killed the app, then flashed it as a recovery. Then, I didn't think much about it until my phone ran out of battery.
I tried to boot system, and it flashes white for a second, then nothing. Same thing with recovery (If I press volume up + volume down + power button, it gives me the option to boot system of recovery). I tried executing fastboot commands in the vol up + vol down + pwr mode (I can't tell if it's bootloader or fastboot mode or even either of then), but it isn't listed in fastboot devices, and it quickly (attempts) to boot into system. I tried using SP flash tool to flash stock recovery and boot.img, but it won't detect the device either. The phone just shows the battery charging indicator (even if I try booting it, it just flashes white and goes back to the battery indicator), and SP flash tool doesn't detect a thing (yes, I tried installing the drivers). Does anyone have an idea on how this can be fixed?
Thanks!!
TL;DR rooted and flashed twrp.img as boot image and as recovery in flashify. Cannot boot system or recovery. Not detected by SP Flash tool
Rip.
Sent from my SM-G386T using Tapatalk
Got any advice to say?
[SOLVED]
Nevermind. I fixed it myself. Turns out I didn't install the correct drivers for SP Flash tool. This time, it detected my device and flashed to my phone perfectly. I'm now running stock 4.4.4 without any problems.

OnePlus X soft brick. All I can access is fastboot mode.

Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Sounds very similar to my situation. I did end up following that guide to get mine going again. The link is broken to get the recovery tool, the 2nd one below is the "minimal" version which isn't supposed to wipe data. That is the one that worked for me. I would backup any data if you can first, no guarantee it wont wipe it. Mine wouldn't boot into the stock rom after, but at least it would get to the stock bootloader (VolDOWN + PWR). From there I was able to adb sideload the stock rom (Install from USB). This completely restored it to stock.
23santosh24 said:
Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Click to expand...
Click to collapse
Surely your bootloader is already unlocked isn't it?
You don't actually say what happens when you try to reboot into recovery using fastboot commands. Does that fail too? What happens when you try to flash twrp again? You don't actually say.
That's what I thought too. It would just say 'recovery.img' not found or something like that. But, I followed the Mega unbrick guide and was able to install the stock ROM through the stock recovery. My OPX is alive again!
i'm stuck here. the phone does not go into recovery at all .. stuck on oneplus logo .. I don't know what to do .. any ideas?
---------- Post added at 09:20 AM ---------- Previous post was at 08:24 AM ----------
I managed to get it alive again with this guide

Tried to Unlock Pixel 2 XL Now Stuck in boot mode!

Hi guys,
I think I made a huge mistake Any help appreciated...
I was following the Magisk and TWRP guides to try and root my phone. I thought it was all going well, but then when trying to flash TWRP, it didn't let me flash it to recovery, it said 'no partisan'. I found on a forum post to try the command 'fastboot getvar current-slot' (this returned a) then 'fastpool flash_a twrp.img'.
I tried this but then TWRP got stuck on the loading screen. I then realised that I couldn't boot into my Android version anymore as I'd flashed TWRP directly onto the boot partition! So I went about trying to flash my stock Android version back onto the phone... I then did this:
'fastboot boot_a boot.img' I stupidly then rebooted. I now am stuck with a perpetually spinning Google loading boot image. I can't launch into recovery mode as I have none, and when holding the power button and volume up it shows an info screen saying "PRESS POWER BUTTON TO PAUSE" and then it goes to the perpetual loading screen again.
I also can't do any more fast booting because adb cannot connect anymore...
Am I completely doomed?
silkt said:
Hi guys,
I think I made a huge mistake Any help appreciated...
I was following the Magisk and TWRP guides to try and root my phone. I thought it was all going well, but then when trying to flash TWRP, it didn't let me flash it to recovery, it said 'no partisan'. I found on a forum post to try the command 'fastboot getvar current-slot' (this returned a) then 'fastpool flash_a twrp.img'.
I tried this but then TWRP got stuck on the loading screen. I then realised that I couldn't boot into my Android version anymore as I'd flashed TWRP directly onto the boot partition! So I went about trying to flash my stock Android version back onto the phone... I then did this:
'fastboot boot_a boot.img' I stupidly then rebooted. I now am stuck with a perpetually spinning Google loading boot image. I can't launch into recovery mode as I have none, and when holding the power button and volume up it shows an info screen saying "PRESS POWER BUTTON TO PAUSE" and then it goes to the perpetual loading screen again.
I also can't do any more fast booting because adb cannot connect anymore...
Am I completely doomed?
Click to expand...
Click to collapse
I ended up eventually un-bricking my phone by booting into safe mode and re-connecting the ADB. I then successfully ran 'flash-all.'

I accidentally deleted recovery using "fastboot erase recovery"

I accidentally deleted recovery using fastboot command "fastboot erase recovery". What should I do? My phone is totally dead now :crying:
SP Flash Tool is not working.
p.s:sorry for my grammar:silly:
not sure but you can still boot to fastboot, as recovery is like when you want to install twrp. so try to boot to fastboot. and flash back twrp
Sent from my vivo 1723 using Tapatalk
ahhl said:
not sure but you can still boot to fastboot, as recovery is like when you want to install twrp. so try to boot to fastboot. and flash back twrp
Sent from my vivo 1723 using Tapatalk
Click to expand...
Click to collapse
The above should work, but if all else fails then following this guide should get you back to stock. http://en.miui.com/a-234.html
My phone can't boot to fastboot, EDL, recovery, etc. It's just vibrating every 5 and 2 seconds until battery drain.
It's connected to PC, but shortly it's vibrating again and disconnected from PC.
RayhanR4chman said:
My phone can't boot to fastboot, EDL, recovery, etc. It's just vibrating every 5 and 2 seconds until battery drain.
It's connected to PC, but shortly it's vibrating again and disconnected from PC.
Click to expand...
Click to collapse
manage to solve?
if you press volume-up + power button until it shows mui logo. then release all button . you will go into recovery again. the phone will vibrate few times before mui logo appear

twrp issue

Installed successful on fastboot command but twrp won't boot up I am on redmi note 5 Amy ideas
I have the same issue and it's with any custom recovery, when I try to flash it it works but when I try to boot into one of these things happen:
1. I get the stock recovery
2. Fastboot shows up (what?)
3. It just does not boot and shows the xiaomi logo
I have literally tried everything but I cannot get this fixed.
Phone is unlocked everything is ok but it does just not work and it is very annoying.
Please if you have any ideas share them
IteXD said:
I have the same issue and it's with any custom recovery, when I try to flash it it works but when I try to boot into one of these things happen:
1. I get the stock recovery
2. Fastboot shows up (what?)
3. It just does not boot and shows the xiaomi logo
I have literally tried everything but I cannot get this fixed.
Phone is unlocked everything is ok but it does just not work and it is very annoying.
Please if you have any ideas share them
Click to expand...
Click to collapse
I had the same issue, and I did the following: enter fastboot, flash the recovery using fastboot flash recovery twrp.img, disconnect the USB cable, and try entering recovery directly from fastboot mode (Volume Up + Power).

Categories

Resources