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

I need Help with Rooting OP6 stable not beta 9.0.2, bootloader is unlocked

So, i have used my whole saturday on unlocking the booloader which was the easiest and quickest and then trying to root, but that has failed every time. I first flashed the stock firmware zip 9.0.2 then I go back I dont reboot and flash the twrp and magisk zip and then it wont boot up,
when I try rebooting after flashing the firmware back to the system it sends me to the firmware,
when I try flashing a new firmware and then boot into fastboot then twrp and flash magisk it wont boot up,
and when I do the same only with twrp it wont neither.
I have tried sevel magisk versions, 17.1,17.2,17.3 none of them worked
as for the twrp blu spark or the one from the twrp website, i was always able to boot into twrp but not really to flash it as that would end in a twrp loop
can PLEASE anyone, someone, with a good heart and patience help me ? im really loosing my ****s over this
:fingers-crossed::fingers-crossed:

Try booting into blu_spark twrp
Installing blu_spark twrp
Rebooting to blu_spark twrp
Install magisk 17.3 or 17.1 (I am using 17.3 because it it beta but less stable.)

Faaris Ansari said:
Try booting into blu_spark twrp
Installing blu_spark twrp
Rebooting to blu_spark twrp
Install magisk 17.3 or 17.1 (I am using 17.3 because it it beta but less stable.)
Click to expand...
Click to collapse
can you provide me with the files ? plus
does it make a difference if I take these twrps compared to the one im using from their website ? because I dont see how this can be the fault ?

galaxyss8 said:
can you provide me with the files ? plus
does it make a difference if I take these twrps compared to the one im using from their website ? because I dont see how this can be the fault ?
Click to expand...
Click to collapse
The normal twrp is known to be buggy on the OnePlus 6 since there was encryption and stuff. Here is the blu_spark twrp IMG to boot:
https://forum.xda-developers.com/devdb/project/dl/?id=30485
And here you need to flash the blu_spark twrp: https://forum.xda-developers.com/devdb/project/dl/?id=30484
Flash that then reboot into recovery again
Then flash magisk
If this doesn't work for you I think there is another way.

Faaris Ansari said:
The normal twrp is known to be buggy on the OnePlus 6 since there was encryption and stuff. Here is the blu_spark twrp IMG to boot:
https://forum.xda-developers.com/devdb/project/dl/?id=30485
And here you need to flash the blu_spark twrp: https://forum.xda-developers.com/devdb/project/dl/?id=30484
Flash that then reboot into recovery again
Then flash magisk
If this doesn't work for you I think there is another way.
Click to expand...
Click to collapse
ive done that now and im waiting again in the; the boot loader is unlocked and software integrety.. winodw
im waiting now for some minutes, i flashed the blu spark zip pressed back went to reboot pressed on reboot to recovery and flashed magisk and then reboot to system, thats where i am now

galaxyss8 said:
ive done that now and im waiting again in the; the boot loader is unlocked and software integrety.. winodw
im waiting now for some minutes, i flashed the blu spark zip pressed back went to reboot pressed on reboot to recovery and flashed magisk and then reboot to system, thats where i am now
Click to expand...
Click to collapse
You might be on the wrong slot. DO you even have a system to boot to? Not sure why you even tyred flashing the 9.0.2 ROM. If I was you I would start over. Use the fastboot ROM to get a clean wiped system booting. After that
fastboot boot bluespark twrp v86. Img
Flash bluespark twrp v86. Zip
Reboot revovery
Flash magisk 17.1

yldlj said:
You might be on the wrong slot. DO you even have a system to boot to? Not sure why you even tyred flashing the 9.0.2 ROM. If I was you I would start over. Use the fastboot ROM to get a clean wiped system booting. After that
fastboot boot bluespark twrp v86. Img
Flash bluespark twrp v86. Zip
Reboot revovery
Flash magisk 17.1
Click to expand...
Click to collapse
I flashed the rom because my phone didn't boot up anymore after either flashing TWRP or magisk.
Why should I use the fastboot room, what is the benefit if I use it.
Is the reboot to recovery necessary ? I feel like that part is actually not working properly ?

galaxyss8 said:
I flashed the rom because my phone didn't boot up anymore after either flashing TWRP or magisk.
Why should I use the fastboot room, what is the benefit if I use it.
Is the reboot to recovery necessary ? I feel like that part is actually not working properly ?
Click to expand...
Click to collapse
Yes the reboot to recovery is the most nessesary part of it as it will change slots.
You can try boot to recovery
Flash oos full rom
Flash bluespark twrp. Zip
Reboot recovery
Flash full ROM again
Flash bluespark twrp. Zip again.
Reboot recovery
Flash magisk.

yldlj said:
Yes the reboot to recovery is the most nessesary part of it as it will change slots.
You can try boot to recovery
Flash oos full rom
Flash bluespark twrp. Zip
Reboot recovery
Flash full ROM again
Flash bluespark twrp. Zip again.
Reboot recovery
Flash magisk.
Click to expand...
Click to collapse
Can you explain how to properly boot back into recovery?
Previously I either just went on the back button and flashed the other Zip's or I went back to the reboot overview and pressed recovery there but that also did not seem to work properly I think.

galaxyss8 said:
Can you explain how to properly boot back into recovery?
Previously I either just went on the back button and flashed the other Zip's or I went back to the reboot overview and pressed recovery there but that also did not seem to work properly I think.
Click to expand...
Click to collapse
Just press back button in Recovery/ reboot / choose recovery.

unable to boot into any recovery mode after flashing any customs rom

I cant boot into any recovery mode afer installing any the custom roms like pixel experience in redmi note 7 pro violet.
whenever it try to boot into recovery mode , it cannt boot up into any recovery mode. please help me. i am tired of flashing stocked rom again and again for flashing new customs rom. i lost its all recovery mode,neither twrp nor its inbuilt recovery mode. phone only get restarting in normally.

Dhiraj bhattarai said:
I cant boot into any recovery mode afer installing any the custom roms like pixel experience in redmi note 7 pro violet.
whenever it try to boot into recovery mode , it cannt boot up into any recovery mode. please help me. i am tired of flashing stocked rom again and again for flashing new customs rom. i lost its all recovery mode,neither twrp nor its inbuilt recovery mode. phone only get restarting in normally.
Click to expand...
Click to collapse
Reflash twrp using fastboot mode?

Sachin said:
Reflash twrp using fastboot mode?
Click to expand...
Click to collapse
I had tried to reflash twrp in fastboot mode but it also didn't work.. It say "too many link,status red ,failed,error" .....blah blah.. I couldn't do anything rather reflashing stocked ROM. Did I missed anything while flashing new custom ROM so that I had been losing recovery mode??

Dhiraj bhattarai said:
I had tried to reflash twrp in fastboot mode but it also didn't work.. It say "too many link,status red ,failed,error" .....blah blah.. I couldn't do anything rather reflashing stocked ROM. Did I missed anything while flashing new custom ROM so that I had been losing recovery mode??
Click to expand...
Click to collapse
Looks like it. So, next time you flash a ROM just keep these things in yo mind -
Boot to Peter's twrp
Wipe
Flash latest firmware.zip
Flash Rom
Flash Gapps
Flash fcrypt zip
Flash magisk
Format data (if you're installing custom Rom for the first time)
Then reboot.
^^

Sachin said:
Looks like it. So, next time you flash a ROM just keep these things in yo mind -
Boot to Peter's twrp
Wipe
Flash latest firmware.zip
Flash Rom
Flash Gapps
Flash fcrypt zip
Flash magisk
Format data (if you're installing custom Rom for the first time)
Then reboot.
^^
Click to expand...
Click to collapse
Thanks ,?

Sachin said:
Looks like it. So, next time you flash a ROM just keep these things in yo mind -
Boot to Peter's twrp
Wipe
Flash latest firmware.zip
Flash Rom
Flash Gapps
Flash fcrypt zip
Flash magisk
Format data (if you're installing custom Rom for the first time)
Then reboot.
^^
Click to expand...
Click to collapse
fcrypt is optional right

Rooting MIUI 12 on Mi Mix 2s?

Folks,
I wish to update to MIUI 12 but I also want to have ROOT and Magisk functionality.
Is it the same process as before where we:
1) fastboot boot recovery.img (this is twrp)
2) then flash Magisk?
has anyone achieved Root and Magisk functionality on MIUI 12 on Mi Mix 2S ?

I flashed MIUI 12 using fastboot then Magisk using Orange Fox and everything was fine. So the process is the same. I used Magisk v21.

dawidcx3 said:
I flashed MIUI 12 using fastboot then Magisk using Orange Fox and everything was fine. So the process is the same. I used Magisk v21.
Click to expand...
Click to collapse
Thanks bro,
Yea I flashed it the old TWRP/Magisk method and it works.
Placing my personal step by step instructions here in case anyone needs it. You can use Orange Fox in place of TWRP. Your choice.
Get latest Magisk Zip (Magisk-v21.0+) https://github.com/topjohnwu/Magisk/releases/
Copy Magisk-v21.0.zip to Phone Storage
Get latest TWRP (twrp-3.4.0-0-polaris+) https://dl.twrp.me/polaris/
Copy twrp-3.4.0-0-polaris.img to Phone Storage
Rename twrp-3.4.0-0-polaris.img to recovery.img (on local PC)
Go to bootloader mode (Power & Vol - )
CMD the following command: fastboot boot recovery.img
after starting TWRP on the phone flash twrp-3.4.0-0-polaris.img file again in TWRP by clicking Install then Select Image then Recovery Partition.
and after this, do not restart
flash Magisk-v21.0.zip
restart
and TWRP remains and you have root.
Regards..

Hi, I don't know if i have to start a new post but i have a inherent problem. I'm trying to install recovery, I've tried twrp and orange via fastboot. I successfully install both, but if i leave them and i reboot to system, next boot make my recovery disappear.... What i'm wrong?
Both at start aks me if i want to keep read only, but i swipe for allow modifications, i can do backups, install zip, Anything (i think, I've not tried this, but it seems fully working), no errors during flash and in recovery LOG also.... Dunno what to do

25agosto said:
Hi, I don't know if i have to start a new post but i have a inherent problem. I'm trying to install recovery, I've tried twrp and orange via fastboot. I successfully install both, but if i leave them and i reboot to system, next boot make my recovery disappear.... What i'm wrong?
Both at start aks me if i want to keep read only, but i swipe for allow modifications, i can do backups, install zip, Anything (i think, I've not tried this, but it seems fully working), no errors during flash and in recovery LOG also.... Dunno what to do
Click to expand...
Click to collapse
Stock rom has software that checks recovery and replaces it with stock if it detects changes. After you flash recovery in fastboot make sure you power off. Then boot to recovery with button combo and flash the recovery zip (orange fox). After flash it should reboot and automatically edit files to stop stock recovery install.

Is Google Pay working with rooted mi mix 2s?

howpathetic said:
Is Google Pay working with rooted mi mix 2s?
Click to expand...
Click to collapse
Yes it does. You have to use "hide magisk" option.

Question Flash TWRP and custom rom

today the 168 waiting time has expired and I was finally able to unlock the bootloader. Now I'm trying to install TWRP to be able to install ArrowOS, I do everything I have to do via fastboot, I put "fastboot flash....." etc and all good, when booting, it boots in TWRP, but when I reboot to the system and enter the recovery again I get back the MIUI recovery, something I'm doing wrong? I have tried installing the .img directly from the twrp recovery in the first boot using "fastboot reboot" after flashing and nothing. Should I install the custom rom on the first boot from recovery?

I had the same behavior on reboot into stock firmware when I installed Lineage Recovery. My guess would be that the stock firmware is actually rewriting recovery if it detects that it's not original but I haven't really investigated it.
MIUI recovery didn't come back after I flashed the system image of a custom rom.

T.Anri said:
I had the same behavior on reboot into stock firmware when I installed Lineage Recovery. My guess would be that the stock firmware is actually rewriting recovery if it detects that it's not original but I haven't really investigated it.
MIUI recovery didn't come back after I flashed the system image of a custom rom.
Click to expand...
Click to collapse
Do you install the rom directly after flash the lineage recovery and booting on it? without rebooting or something

chavaa said:
Do you install the rom directly after flash the lineage recovery and booting on it? without rebooting or something
Click to expand...
Click to collapse
Read here if you have issues with flashing custom ROMs.
https://forum.xda-developers.com/t/4288121/post-85137963
If your OS is Official MIUI, the recovery will always be replaced with MIUI recovery on every boot.

Try Orange Fox as recovery, it has an option to prevent recovery from being overwritten by stock recovery, but i dont know wether orange fox works with lineage os. I run it with AICP and it runs like a charm..

I haved the same problem when I haved a whyred (redmi note 5 pro), the solution is very easy, when you have the blue screen of the CMD (now powershell), you need to put "fastboot devices", then put "fastboot boot <twrpfilename>.img, this action will do the device restart in TWRP, then you need to copy and paste the twrp.img in a folder of the device, any folder, it doesn't matter. Then go to install, choose the option "Install image", and go to the folder where you copy the file twrp.img, pick it and choose the option "recovery", then install.
That should be works.
Sorry for my english, I'm trying to learn.