Database Info

Mi 4C just boots to recovery, no matter what I flash

Hi everyone
I've bought a second hand Mi 4C. The original owner had installed TWRP and LineageOS on the device.
I wanted to go back to MIUI, so I used the existing TWRP to do the usual wipes and then flash:
xiaomi.eu_multi_MI4c_V8.1.3.0.LXKCNDI_v8-5.1.zip
The ROM seems to flash correctly, however after I reboot the device it just boots back into TWRP. Basically, there's no way to boot the device "normally", it always boots to recovery!
Thinking maybe the rom was at fault, I wiped again and flashed the latest LineageOS, since I knew that was working before.
However, I then discovered that even with LineageOS the problem remained: device always starts in recovery mode!!!
How can I solve this? I'm new to Xiaomi devices, so maybe I'm missing something. I've always had Nexus phones and I've never seen a problem like this in years of flashing custom roms.

I would point torwards locked bootloader.

Maybe the volume button is stuck?

Try to go in fastboot mode and execute this:
Code:
fastboot oem device-info
If "device unlocked: False " you have to unlock bootloader or follow this guide http://en.miui.com/thread-335614-1-1.html

Hi? Did you solve this problem? My phone also keeps booting in TWRP. What i did was, get to Fastboot and typed "fastboot continue" .

Got the same. Bootloader unlocked.

i have the same issue.
I had TWRP 3.0.3-0 with the Resurrection Remix ROM. After booting into recovery and make a factory default wipe, started to boot always in recovery (TWRP). Doesn't matter if I force to reboot into system. Tried to flash the latest version of RR and nothing changed. Flashed TWRP v3.0.2 and touch screen didn't work.
Then I decided to start from the beginning, flashing the stock libra_images_6.1.7_20151221.0000.11_5.1_cn, unlock the bootloader ( fastboot oem device-info gaves me "true" unlocked), flashed TWRP 3.0.3-0, and till this point all it worked flawlessly. When I flashed the latest RR, then started the boot loop into recovery.
Any idea? Thank you very much

Latest RR 5.8.2 by AndopaX and LineageOS by HnT build with new Miui N bootloader..
You need to change TWRP base Miui N also Fw Update from Miui N..
You will get bootloop when install that roms into old Miui LP bootloader..

caxwan said:
Latest RR 5.8.2 by AndopaX and LineageOS by HnT build with new Miui N bootloader..
You need to change TWRP base Miui N also Fw Update from Miui N..
You will get bootloop when install that roms into old Miui LP bootloader..
Click to expand...
Click to collapse
Wowww! Thanks for the fast answer!
Could you help me to do that? Where can I find this TWRP base Miui N and Fw Update from MIUI N?
Thanks

korolirio said:
Wowww! Thanks for the fast answer!
Could you help me to do that? Where can I find this TWRP base Miui N and Fw Update from MIUI N?
Thanks
Click to expand...
Click to collapse
AndropaX already prepared all before build rom 5.8.2 with Miui N bootloader.
TWRP Nougat : by AndropaX
FW Update Nougat : by AndropaX
Many ways to update, I have try this one.
* Disable PIN/Pattern Lockscreen (related bug of fw nougat)
1. Boot into your old TWRP LP
2. Wipe System, Data, Dalvik and Cache
3. Install FW Update N via TWRP
4. Install new TWRP N via TWRP too
(choose install image) install to recovery
5. Reboot to new TWRP N
6. Install ROM + GAPPS via TWRP
7. Reboot to System

Yeahhhhh!!! THHHHAAAANNNKKKSSSS!!!! It works like a charm!

Android 10 & Custom ROM & Slot A + B

Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
First Time Install / Clean Flash
- Have OOS 10.3 flashed to both slots!!
- Boot to recovery
- Flash BUILD.zip (TWRP built-in)
- Wipe Cache
- Format data
- Reboot to recovery (optional)
- Flash Magisk.zip (optional)
- Reboot to system & #KeepEvolving
Click to expand...
Click to collapse
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.

roel1976 said:
Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
Click to expand...
Click to collapse
Hi!
I had this exact same problem a couple months ago. Rebooting to recovery used to change slots for me, but then it stopped.
What you can do is change active slot manually on Reboot section. By doing this, you don't even have to reboot to recovery in other to flash the other slot (altough I do it just to be safe).
And remember: the rom is flashed on the inactive slot, so after the final flash you gotta change slots one more time.

When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.

Thanks for the info, it really helps.
One question: in your experience can you wipe your phone and then installl OOS on the wiped phone?

So I just booted into TWRP, did standard wipe action: Data, Cache, and Dalvik. I then try to flash the latest OOS zip and I then get this error:
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
Updater process ended withL ERROR: 1.
Error installing zip file: '/usbstorage/00, INSTALL/OnePlus6Oxygen_22_OTA_044_all_2002220042_a46425f1bfe43d2.zip
FIXED: I was using TWRP 3.3.1.11 and I then found out there was a newer version: 3.3.1.18 which you can get here: https://sourceforge.net/projects/mauronofrio-twrp/files/Enchilada/
I am now able to install OOS from scratch (ie wiped phone).

remewer said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.

harshybar said:
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
Click to expand...
Click to collapse
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.

remewer said:
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
Click to expand...
Click to collapse
When you say local update you mean while I am running the rom, go to settings then do update from local source?

harshybar said:
When you say local update you mean while I am running the rom, go to settings then do update from local source?
Click to expand...
Click to collapse
Exactly

GuestD2559 said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
@Cypher_01, Try this guide. This worked for me. I did not reinstall Nikgapps. Maybe that's where the problem lies? Don't forget to change the update slot at the end before you restart.​

mi mix 3 - stuck on twrp bootloop ?

Ok so fresh out the box, unlocked bootloader etc.
I have twrp running finally, and have gone through following the steps format/wipe etc.
flashed several differant roms to just try and get one to boot. every reboot it will automatically go into twrp..
I have tried Arrow, Lineage, pixel experience and all of them result in the same mi bootloop and automatically booting twrp.
im following the arrow install instructions :
New build required to be on MIUI Q firmware part (Recommended V12.0.1.0).
Use TWRP.
Make FULL WIPE (system/vendor/data/dalvik/cache) and FORMAT DATA - YES.
Flash ROM (link in first post)
Flash gapps, if need for VANILLA buildtype.
Reboot
when i flash the Xiaomi eu 12.0.1.0 as suggested... twrp bootloop.
so i am sitting with a device going between Mi screen and recovery only. I have no system ?
Can someone point me in the right direction.

Hi,
I do a full wipe like the instruction. After that I install the Xiaomi.eu v12 build. When that is installed immediately install Arrow 11 without formatting (and gapps if you choose the VANILLA build). I then don't install magisk or any other root solution and I reboot the device. This worked for me when I installed LineageOS and when I installed Arrow 10 and now 11.
So I first install Xiaomi and than the ROM I want without a format or reboot between them. If you are booted in the rom I then look into a root solution and install that if you want atleast.

Possibly bricked my poco f2 pro, is there a way to fix this?

Hi all.
Today I unlocked my phone to flash the crDroid rom. First I went into fastboot to flash mauro's twrp and that worked fine. Then I flashed the miui 12.0.3 full stock image from twrp, which might have been a mistake since I flashed the full image instead of an extracted vendor / firmware version. Then I wiped system, cache and data and flashed twrp but when I tried to boot the phone it went into an infinite boot screen. Then I wiped and flashed the whole stock miui image again in the hope that I would at least be able to boot miui but that also failed, since the phone kept booting back to recovery and there was no boot screen at all.
I have also tried flashing the stock image (ver 12.0.6) from fastboot but it fails because of the anti rollback check error. The image I tried to flash has an antirollback version of 0 while my phone has a version of 1, so "current device antirollback version is greater than this package" is what I got. Now my options are very limited because for some reason my laptop can't access the file system of the phone so I can't transfer files to the phone anymore and the ADB sideload feature from twrp is not working, so I only have fastboot (adb also won't recognize my device). What can I do to save my phone? Any help is greatly appreciated.

Flash the MIUI with MiFlash.

Had sort of the same issue...
Try using adbfastboot tool ( it's a java programme ) to swap recoveries.
I got the bootloop after installing the LOS recovery , installed twrp from adbfastboot tool and got it working.
Nice to have working recovery but since adb sideload is broken in twrp i needed LOS recovery.
Tried to reflash the LOS recovery from the tool and this time it worked

Flash with Miflash (the latest version https://xiaomiflashtool.com/ option CLEAN ALL) the rom that was on your phone when you bought it.
For the roms It is better to flash firmwares with Miflash because TWRP is not 100% functional.

grt67DFqyu said:
Flash the MIUI with MiFlash.
Click to expand...
Click to collapse
Man I can't believe such a simple suggestion would work but it did thanks! Initially I did not flash with miflash because it prompted me to install drivers and it crashed when I clicked the install button, turns out all I had to do was create a folder named log in the miflash directory lol. So flashing the stock image works. And it definitely boots correctly to miui with the clean all and lock option.
But now when I try to flash crdroid or pixel experience I still end up with an infinite boot screen even when using exactly the specified firmware :/ Like you see crdroid and pixelexp boot animations correctly but it lasts forever. I must be doing something wrong with the firmware still because that's the only reason I can think of why it won't boot. After I flash the firmware in miflash I don't have to boot miui up first right? I'm using the 'save user data' option in miflash if that matters.

In my post, I specified CLEANALL, but anyway, you must format data before flashing.
Which rom do you want to install Cdroid or Pixel?

NOSS8 said:
In my post, I specified CLEANALL, but anyway, you must format data before flashing.
Which rom do you want to install Cdroid or Pixel?
Click to expand...
Click to collapse
I'm now trying to flash crdroid. After flashing V12.0.3.0.QJKMIXM in miflash with flash_all, I formatted data in twrp (the one where you have to type yes) but also with a decrypt & normal factory reset I still get the same result. After the format, I flashed crdroid without magisk and gapps, and it'll just hang on the crdroid boot screen :/. The weird thing is, before I flash the crdroid rom it can boot in MIUI just fine and it'll show that it's indeed the correct 12.0.3.0 in the settings so I have no idea if it's just the crdroid ROM at this point.

Flash with miflash V12.0.3.0.QJKMIXM reboot system and go fasboot when affiche "devices is locked",flash chinesse twrp ,reboot twrp,format data reboot twrp,wipe all ecxept OTG reboot twrp,flash Cdroid format data,reboot twrp flash gapps,reboot system( take time ).

NOSS8 said:
Flash with miflash V12.0.3.0.QJKMIXM reboot system and go fasboot when affiche "devices is locked",flash chinesse twrp ,reboot twrp,format data reboot twrp,wipe all ecxept OTG reboot twrp,flash Cdroid format data,reboot twrp flash gapps,reboot system( take time ).
Click to expand...
Click to collapse
This ended up working perfectly Crdroid is now running like a charm with gapps and magisk. Thank you guys a lot for helping me out with this!

Flashed wrong version , phone keep restarting

Good day ,
kindly I need your Help I have poco x3 nfc Global version with miui 12.08 and After unlocked phone , flashed miui 12.09 Miui india version and now phone show poco logo then keep restarting
I tried All Available soluation flash stock global ron and custom roms and also stock and custom recovery only continue to boot but still keep restarting after show poco logo any soluation please

Have you done FORMAT DATA?

of course tried All thing erase full phone partitions expect encrypted but still keeps restarting

What about original stock ROM with MiFlash? If that doesn't work, only options will be EDL or RMA...

pnin said:
What about original stock ROM with MiFlash? If that doesn't work, only options will be EDL or RMA...
Click to expand...
Click to collapse
Already tried this and flash stock rom from mi box but still anyway i sent to service center , there's no Availabile soulation any more
also I'm sure this rom that flashed it has bug as per the below link , Miui software going worth every day feel sorry
MIUI 12 Update Will Disable These Smartphones, How To Fix?
MIUI 12 update is disabling some of the Xiaomi smartphones including Mi, Redmi and Poco series. Several users have reported unexpected errors installing the latest versions of MIUI 12. Multiple devices have fallen into the endless reboot cycle, witho
trak.in

It happens to me too

First Download the below files
1. TWRP
2. MIUI Firmware( Region wise)
3. Download Recovery Rom.
3. Download Fastboot Rom.
4. Download Mi Global Flash Tool.
5. Boot into Fastboot.
6. Flash TWRP. Install MIUI Firmware( would be around 80MB -100 MB Only) zip file.
7. install the Recovery Rom zip file. Format Data.
8. Reboot in to Bootloader.
9. Now open the Mi global flash tool and select the extracted Fastboot rom and click flash..
Hope this will solve the Problem