Database Info

Cannot start ROM / permanent reboot into recovery

Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy

jjeans said:
Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy
Click to expand...
Click to collapse
Download fastboot rom and flash it

thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS

jjeans said:
thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS
Click to expand...
Click to collapse
How do you flash recovery tell me the procedure?

Talha7866 said:
How do you flash recovery tell me the procedure?
Click to expand...
Click to collapse
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy

jjeans said:
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy
Click to expand...
Click to collapse
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.

zhart said:
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.
Click to expand...
Click to collapse
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.

jjeans said:
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.
Click to expand...
Click to collapse
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.

Sorry, what exaclty is a fastboot rom and where do i get it?

zhart said:
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.
Click to expand...
Click to collapse
I don't know what happens all the time.
Currently I used MiFlash to make a clean fastboot install. I choosed in MiFlash "flash_all.bat" to do it. (flash_all.bat means everything was reinstalled, also recovery.img). Afterwards everything was normal, MiRecovery 2.x and Mi4C MiUI 7 chinese version was installed without error. But after manual flashing TWRP with "fastboot flash recovery xxx", the recovery loop was again! :/
So AGAIN I made a clean fastboot install again with MiFlash application, but this time I REPLACED the recovery.img with the newest TWRP (renamed to recovery.img) within the fastboot rom installation folder "images". I could see that MiFlash flashed THIS! recovery.img, but after that again the old Mi Recovery was on the device and no TWRP. But why? I replaced the original recovery.img file! How can that happen?
The flash_all.bat included flashing recovery and I could confirm it during the fastboot flash. Strange.
I used fastboot rom libra_images_V7.0.16.0.LXKCNCI_20151104.0000.4_5.1_cn
MiFlash newest version and I tried with 2 TWRP versions (one from decuro and one from sMiUI)

Maybe my phone has a problem with flahing recoverys in general I don't know.

jjeans said:
Maybe my phone has a problem with flahing recoverys in general I don't know.
Click to expand...
Click to collapse
it sound very strange i did all these steps and my phone was all good after it. is it the newest recovery? the one with material theme and touch fix you are using? if not, then thats the only difference between your procedure and mine :/
i hope you can fix it
Edit: I can see that i have the following fastboot roms downloaded, so i used one of these:
libra_images_V7.0.6.0.LXKCNCI_20150917.0000.1_5.1_cn_4dd76a55cb.tgz
or libra_images_V7.0.15.0.LXKCNCI_20151104.0000.4_5.1_cn_f6e955ee14.tgz

What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...

Hello, don't know if applicable. I've read on mi forums that dev Roms need dev recovery, that's different from twrp for stock rom.....

guegangster said:
What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...
Click to expand...
Click to collapse
Hallo,
thank you, that worked for me finally
I have now used another TWRP 2.8.7.1 with touch-issue, but that is now no problem.
I flashed also xiaomi.eu rom, for now seems to be stable and cleaned.
strange everything, but now it is fixed.
BR,
Jimmy

Can't install Custom Roms.

Alright, so its without wasting time of people here, I'd just state the summary in points.
I flashed stock rom a.17 - I had custom roms before, I got fed up with them changing every 2 months.
Then everything worked fine until I flashed the boot.img from vishal_android_freak to get recovery.
I got the twrp recovery 2.7.0.0.
I flashed AOSP 6.0.1 through it, it was done very well but the rom stuck on boot animation for more then 30 mins.
I pulled the battery out - now I had TWRP 2.8.4.0
I tried flashing the rom again, it gave /data error.
I flashed stock rom, rooted then tried other methods of getting recovery, I failed everytime (Tried from TWRP app, su dd command, Recovery installer app )
Then I found a CWM boot.img to flash through fastboot.
I did and got CWM.
I flashed AOSP again from it, it stuck on boot animation again.
Then again I flashed stock rom and repeated the process.
This time with CWM, I flashed Stryflex LP Ultimate
It also stuck on boot animations.
Any idea why this happens? How to fix this ****?
Summary: Only stock rom works, not any other rom.

Observer000 said:
Alright, so its without wasting time of people here, I'd just state the summary in points.
I flashed stock rom a.17 - I had custom roms before, I got fed up with them changing every 2 months.
Then everything worked fine until I flashed the boot.img from vishal_android_freak to get recovery.
I got the twrp recovery 2.7.0.0.
I flashed AOSP 6.0.1 through it, it was done very well but the rom stuck on boot animation for more then 30 mins.
I pulled the battery out - now I had TWRP 2.8.4.0
I tried flashing the rom again, it gave /data error.
I flashed stock rom, rooted then tried other methods of getting recovery, I failed everytime (Tried from TWRP app, su dd command, Recovery installer app )
Then I found a CWM boot.img to flash through fastboot.
I did and got CWM.
I flashed AOSP again from it, it stuck on boot animation again.
Then again I flashed stock rom and repeated the process.
This time with CWM, I flashed Stryflex LP Ultimate
It also stuck on boot animations.
Any idea why this happens? How to fix this ****?
Summary: Only stock rom works, not any other rom.
Click to expand...
Click to collapse
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM

Kungfu73 said:
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Click to expand...
Click to collapse
Alright, I check bootloader state, it says bootloader unlock done means it's unlocked.
I am going to flash twrp 3.0.2 and will update you soon!

Kungfu73 said:
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Click to expand...
Click to collapse
Oh Man, you saved my day! nothing worked but the damnit twrp 3.0.2
For anyone else referring here:
I get hell lot of graphical glitches when I flashed twrp 3.0.2, I just made it to factory reset and click install button although my screen was glitched and I cant even look at it.
JUST IGNORE THE GLITCHES! I wiped dalvik cache after flashing AOSP-RRO, now I'm flashing Lineage OS, thanks a lot! Button pressed.

Observer000 said:
Oh Man, you saved my day! nothing worked but the damnit twrp 3.0.2
For anyone else referring here:
I get hell lot of graphical glitches when I flashed twrp 3.0.2, I just made it to factory reset and click install button although my screen was glitched and I cant even look at it.
JUST IGNORE THE GLITCHES! I wiped dalvik cache after flashing AOSP-RRO, now I'm flashing Lineage OS, thanks a lot! Button pressed.
Click to expand...
Click to collapse
Did TWRP 3.0.2 ultimately work with this?
If worked, I am also curious to know how much space is left there for apps in device memory, since the ROM seems to be Marshmallow based.

Twrp opening screen shown then device goes into bootloop.

I had pixel experience rom installed and tried to flash the new update when it showed error 7. Anyways, trying to fix it, i decided to wipe and install fresh rom. But when i try to boot to recovery now, the twrp opening screen comes up and instead of going into recovery menu, goes into boot loop. Tried flashing dummy img and flashing new twrp img too but same result. Tried booting to recovery using fastboot boot twrp.img too still same result.
btw device is redmi note 5 pro

[email protected] said:
I had pixel experience rom installed and tried to flash the new update when it showed error 7. Anyways, trying to fix it, i decided to wipe and install fresh rom. But when i try to boot to recovery now, the twrp opening screen comes up and instead of going into recovery menu, goes into boot loop. Tried flashing dummy img and flashing new twrp img too but same result. Tried booting to recovery using fastboot boot twrp.img too still same result.
btw device is redmi note 5 pro
Click to expand...
Click to collapse
Try reinstalling the stock ROM, it'll delete any modification brought to the device...

Bricked device?

I unlocked the bootloader through mi unlock tool. I flashed official twrp from their site, 3.3.1-0-violet.img but when I tried booting it into recovery, it got stuck at twrp logo. Then I learnt that it's necessary to wipe userdata using fastboot first so I did that. Then, when twrp started, it was unable to install/wipe/mount any partition. Tried installing magisk using sideload, did work but then device stopped booting.
Figured out a way on how to fix the mount issue, twrp working fine, but then I accidentally wiped /system. Now my device only opens in fastboot, even though I've tried installing, erasing and reinstalling that twrp recovery as well as a couple of others I found in pixel experience forums for my device.
I've got all the stuff needed to install pixel experience, fcrypto disabler, xiaomi latest firmware and the rom itself. Can anyone guide me on how to install it using fastboot?
Also whenever I try booting the recovery image straight from fastboot, it says that command failed, too many links.
I can't boot into recovery via vol up + power button, fastboot doesn't recognize command fastboot reboot recovery.

you need to install stock rom ,then flash twrp but newer unofficial twrp and orangefox twrp boots into recovery even if system partition is empty.
try installing unofficial twrp or orangefox.
orangefox is recommended .

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!