Redmi S2 stuck on Mi logo - Xiaomi Redmi S2 Questions & Answers

My Redmi S2 somehow got stuck on Mi logo this morning. Everything is still stock and locked. I followed a guide somewhere to unlock bootloader through edl mode, seems like it worked (is says "unlocked" under Mi logo).
With BL unlocked, I tried flashing TWRP using fastboot. But I still can't boot into recovery, only Mi logo. Even stock recovery won't boot.
It seems flashing using Mi Flash Tool doesn't worked anymore , unless with auth. So I found another flash tool. Tried flashing Global/China rom with it(edl mode of course), all is well but "cache","cust","vendor","system","userdata", didn't finished flashing. But the tool says the whole process is completed and proceed to reboot the phone. Which still only showing "Mi Logo".
So I tried using fastboot command to flash those few files. First few time the process completed. But still nothing changes. However, when I try to flash using fastboot now, it just stuck at "erasing". Any file I tried to flash just got stuck here.
"fastboot boot recovery.img" also don't worked. Got the same result using another computer. Now I'm stuck. Would appreciate some advice and guide here.

JEDAlive said:
My Redmi S2 somehow got stuck on Mi logo this morning. Everything is still stock and locked. I followed a guide somewhere to unlock bootloader through edl mode, seems like it worked (is says "unlocked" under Mi logo).
With BL unlocked, I tried flashing TWRP using fastboot. But I still can't boot into recovery, only Mi logo. Even stock recovery won't boot.
It seems flashing using Mi Flash Tool doesn't worked anymore , unless with auth. So I found another flash tool. Tried flashing Global/China rom with it(edl mode of course), all is well but "cache","cust","vendor","system","userdata", didn't finished flashing. But the tool says the whole process is completed and proceed to reboot the phone. Which still only showing "Mi Logo".
So I tried using fastboot command to flash those few files. First few time the process completed. But still nothing changes. However, when I try to flash using fastboot now, it just stuck at "erasing". Any file I tried to flash just got stuck here.
"fastboot boot recovery.img" also don't worked. Got the same result using another computer. Now I'm stuck. Would appreciate some advice and guide here.
Click to expand...
Click to collapse
if your bootloader still unlocked..
try reinstalling twrp via fastboot and use the volume up button and power button to enter recovery

Even in the beginning, before flashing anything, it won't enter stock recovery. I already tried flashing twrp, flash succeed, but it won't enter recovery mode, or twrp. And now, I can't flash anything through fastboot. It just stuck at "erasing..."

Related

Mi Mix 3 stuck in bootloader after twrp update

Hello friends,
i wanted to update my twrp from the very first on to the latest 3.3. I did this in the recovery itself. after i could not boot into twrp anymore. Neither through Updater app, nor through Button Combo.
It all sent me to bootloader. So i tried flashing the twrp img through fastboot.
First: always in cmd fastboot flash recovery twrp.img; but result was that cmd gave no answer at all or failure
Second: i tried fastboot boot twrp.img.; Result was a successful flash, but no boot into recovery afterwards
AND AFTER THAT I cant boot into system anmyore
Edit:
on another pc I got Miflash running and installed latest global rom. Now im stuck till mi recovery. Phone is still unlocked
Edit2:
Got TWRP installed and after newest xiaomi eu rom. Still lost all my data, because everything was still encrypted..

Cannot revive my phone

My note 6 pro suddenly started doing boot loop. I tried to revive it by flashing stock firmware but nothing seems to help. It has unlocked bootloader, with TWRP installed. This is what I tried:
Put phone in fastboot mode, I do see the fastboot image.
Computer recognizes the phone. 'fastboot devices' shows correct device.
Using MI Flash tool to flash 10.3.6 global fastboot image. It takes about 160 seconds to flash all the partitions. The phone will reboot at the the end of the flash. Flash tool doesn't say "successful" though. Its status is still "flashing".
No other errors. When the phone restarts, it is still stuck in the boot loop. Interesting thing is, if I press volume + button and power button, I see TWRP flash for a quick second on the screen then boot again. Looks like the recovery image wasn't flashed properly.
Looked at the logs. Nothing strange. Also tried to run 'flash-all.bat' in a command line (not sure if we are supposed to do that), but all the fastboot flash commands look OK.
Anything else I can do to revive this phone?

Redmi note 7 stuck in a bootloop. Can only access stock recovery, is it fixable?

Good morning!
While attempting to flash a stock MIUI 10 ROM into my Xiaomi Redmi Note 7, to downgrade back to Android 9.0 due to some app compatilibty issue, I messed up big time and my phone is now stuck in a loop where the screen turns on, nothing shows up, then it restarts, going off for a few seconds and turning on again.
Power Button + Volume UP successfully brings me to the stock recovery 3.0 from xiaomi.
Power Button + Volume DOWN fails to bring me to the fastboot mode.
If I select the Connect with MIAssistant in the recovery the phone will show up as "sideloaded" after using the command adb devices, but the MIPCSuite app does not see it and the command adb restart bootloader also fails to bring up the fastboot mode, it just gets stuck in the loop again.
More context on what went wrong and caused this: I followed an online tutorial to flash a rom using the MIFlash app, so I unlocked the bootloader and tried to flash the rom usin xiaomi's tool. I got a failed to check sparse crc error code and it went downhill from there when I tried to fix things reading multiple threads on the issue. I tried deleting some lines from the flash_all.bat file and tried to flash it again but then the flashing process went seemingly forever so I aborted the operation and now this loop happens. I tried a few more times but with no success.
The first time I tried to use the tool I used the clean all and lock option so I'm not certain if the miflash tool locked the bootloader regardless of the outcome of the flashing attempt.
Is there hope? Can I fix this phone if I only have access to stock recovery and nothing else (although it shows up in adb devices but can't get into fastbootmode) ?
Thanks a lot to anyone who took the time to read and possibly help.
Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.
jwoegerbauer said:
Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.
Click to expand...
Click to collapse
I see.
What can I do to try to fix this issue?
I finally managed to fix it through the Emergency Download Mode (EDL). It requires Xiaomi Authentication which I bypassed using this guide: https://www.droidwin.com/fix-mi-account-authorization-unbrick-xiaomi-edl-mode/
With that setup I flashed a stock rom using the MiFlash tool.

Question Stuck in boot loop while trying to root using Magdisk help please?

Hi all,
I was following the steps to root my pixel 6a using Magdisk I had put the patch boot image on my macbook and then went into fastboot, and then used the command "fastboot flash boot [image]"
I got the okays and then I went to reboot and it's stuck in a boot loop.
I've tried to get into recovery but I just keep getting a splash screen about the device bootloader being unlocked.
Any suggestions? I've tried rescue mode too but it also goes to the bootloader unlocked screen.
Hold the power button till it turns off, volume down + power button to get to bootloader. Reflash stock boot.
ALWAYS fastboot boot first before actually flashing in case this happens
Make sure you're using the correct boot image to patch for your build number too
AphoticAffinity said:
Hi all,
I was following the steps to root my pixel 6a using Magdisk I had put the patch boot image on my macbook and then went into fastboot, and then used the command "fastboot flash boot [image]"
I got the okays and then I went to reboot and it's stuck in a boot loop.
I've tried to get into recovery but I just keep getting a splash screen about the device bootloader being unlocked.
Any suggestions? I've tried rescue mode too but it also goes to the bootloader unlocked screen.
Click to expand...
Click to collapse
What version of Magisk did you use? You must use 24.0 or newer.
As @ctfrommn recommended, you can "live boot" the patched image instead of flashing it:
fastboot boot <patched boot image>
If this fails for whatever reason, it'll reboot with the stock boot image.

[HELP] OnePlus Nord booting only to fastboot mode.

I tried installing the pixel experience rom and after I flashed the aex recovery before side loading the ROM, it went into bootloop and ended up with the stock recovery and ROM. I tried to flash TWRP recovery and go a message that the the boot/recovery image is destroyed so I tried to flash the stock boot image back and since then I am not able to get it out of fastboot mode.
I tried everything, flashing the recovery again, both stock and TWRP and also tried using the flash-all to flash the stock ROM back but nothing seems to be working.
When using the flash-all, I get 'partitions not found' and 'flashing is not allowed in critical partitions' error.
I even tried msmtool but I am not able to get my phone into edl mode for the tool to detect it.
Tried holding the vol+/vol- and connecting the usb cable but to no vain, the tool does not seem to detect it.
I even tried using the all-in-one tool but my phone is not getting detected when it is turned off but it gets detected when it's in flashboot mode from where I cannot enter edl.
Let me know if there is anything I can do to fix it? Or if taking the phone to the official service center help?
Can you reboot from fastboot to edl by entering fastboot reboot-edl? Or similar, don't know exactly anymore
Alternatively see if this can help you getting into edl: https://forum.xda-developers.com/t/guide-how-to-reboot-to-edl-from-fastboot.3394292/

Categories

Resources