In TWRP I was not able to see System and Vendor Partitions in Wipe Section so like a fool
I flashed twrp image in Super, this put me in bootloop
After this I flashed some files from the fastboot version of Stock ROM in the following manner
https://www.droidwin.com/unbrick-poco-x2-fastboot-commands/
But even after this I am was in Bootloop so to see if it is a TWRP problem due to which I was not able to see System and Vendor Partitions, I installed Orange Fox Recovery.
After installing Orange Fox Recovery R11
I wiped Dalvik / ART Cache
Data
Cache
And flashed the Custom ROM(Evolution X 5.8) but then this happens :
assert failed: update_dynamic_partitions (package_extract_file("dynamic_partitions_op_list"))
Updater Process ended with EROOR :1
Error installing ZIP file "path of the file"
Please help !!!
I heard that orangefox has issues with custom rom. Use Original twrp for custom roms. Hot boot twrp and flash . No need to wipe cache or data before flahsing. But after flash format data.
notathinker said:
In TWRP I was not able to see System and Vendor Partitions in Wipe Section so like a fool
I flashed twrp image in Super, this put me in bootloop
After this I flashed some files from the fastboot version of Stock ROM in the following manner
https://www.droidwin.com/unbrick-poco-x2-fastboot-commands/
But even after this I am was in Bootloop so to see if it is a TWRP problem due to which I was not able to see System and Vendor Partitions, I installed Orange Fox Recovery.
After installing Orange Fox Recovery R11
I wiped Dalvik / ART Cache
Data
Cache
And flashed the Custom ROM(Evolution X 5.8) but then this happens :
assert failed: update_dynamic_partitions (package_extract_file("dynamic_partitions_op_list"))
Updater Process ended with EROOR :1
Error installing ZIP file "path of the file"
Please help !!!
Click to expand...
Click to collapse
I found a copy of OrangeFox that worked for me available here.
OrangeFox-R11.1-Stable-Unofficial-lime.zip
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
The key was to first flash xiaomi.eu_multi_HMNote94G_HM9T_V12.5.6.0.RJQCNXM_v12-11.zip
reboot the phone and let it fully start (I think this updated the partition tables or something)
Then go back into OrangeFox and flash crDroidAndroid-11.0-20220121-juice-v7.14.zip
By doing this I was able to get the phone to boot into crDroid whilst using OrangeFox without any bootloops or partition size errors like the one I was initially getting "assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))"
I think the important step is to let it fully boot after putting on the xiaomi.eu ROM as it must resize partitions or something...
I am having the same problem. I tried to restore an orangefox backup and i ticked the "super" box. After that when i try to flash a rom proccess fails with the exact same message (assert failed: update_dynamic_partitions (package_extract_file("dynamic_partitions_op_list"))). I have flashed three different recoveries (pitchblack, orangefox, lineageos) and tried from every each of them flashing a rom both from the recovery and sideloading. The roms i have tried are: crdroid A12, arrowos A11 & A12, lineageos microg and at last the stock miui for my device. Nothing worked so far. Please if someone has any knowledge or ideas help because i am starting to believe it is irreversible...
Device: Redmi note 9s (curtana)
I finally figured it out. Since I was not able to flash any ROM (including stock miui) from the recovery, neither with sideloading, I had to download Mi Flash tool on my PC and a miui ROM .tgz file, used especially for flashing through Fastboot/Mi Flash. Then I booted my phone on fastboot mode and connected it to PC, opened the MiFlash tool on PC, chose the miui Rom file (you have to extract twice from the original .tgz file to reach to the selectable one, and I also had to put it on Desktop otherwise it could not be reached) and finally flash it.
HomoImpudens said:
I finally figured it out. Since I was not able to flash any ROM (including stock miui) from the recovery, neither with sideloading, I had to download Mi Flash tool on my PC and a miui ROM .tgz file, used especially for flashing through Fastboot/Mi Flash. Then I booted my phone on fastboot mode and connected it to PC, opened the MiFlash tool on PC, chose the miui Rom file (you have to extract twice from the original .tgz file to reach to the selectable one, and I also had to put it on Desktop otherwise it could not be reached) and finally flash it.
Click to expand...
Click to collapse
Yeah, after flashing it with miflash tool your phone runs fine with miui. Were you able to install a custom rom after this? If yes, could you tell what steps did you follow.
If I remember correctly, after that I followed the standard procedure first to flash a custom recovery and then through that a custom rom. Downloaded SDK tools (if I remember the name correctly), opened smartphone on fastboot mode, opened terminal window fom inside SDK tools folder, downloaded a custom recovery, placed it inside SDK folder, rename it "recovery", typed on terminal window: "fastboot flash recovery recovery.img" (again if I remember correctly) and then reboot to recovery. From there install any custom Rom you want.
Orangefox recovery have tick of unmount system and vendor, dont forget to tick them and it will solve your problem
GiGilGilang said:
Orangefox recovery have tick of unmount system and vendor, dont forget to tick them and it will solve your problem
Click to expand...
Click to collapse
Thank you so much. I'm so lucky that I stumbled into your comment, you saved my device!!
Related
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
Hi
I have problems to install LineageOS on my new OnePlus6. I tried to install LineageOS with the guide on https://wiki.lineageos.org/devices/enchilada/install. If I follow the guide exactly step by step no OS is starting and I can't boot into recovery because (I think) twrp isn't installed (just black screen with blue led). But also if I first boot twrp with fastboot boot 'twrp.img' and after install the twrp.zip, no OS is starting after sideload or flash the 'lineageos.zip'. I think, the install doesn't finish correct. In the terminal on my debian I can see, that the installprocess ends at 47%. But I'm not really shure if this is the problem and if it is, how I can solve it. Probably in this thread the same problem is described: https://forum.xda-developers.com/oneplus-6/help/lineage-doesnt-boot-black-screen-light-t3958351 Unfortunately no solution is available in the thread.
Now I flashed the stockrom (https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665) and have done all updates but don't know how I can install twrp and after LineageOS. I hope somebody can help me. Thanks
Do you have the latest ADB version? Instead of sideloading you can try just transferring the zip files (with e.g. "adb push lineageos.zip /sdcard/") and then installing directly from TWRP.
Make sure you do all the wipes / formats mentioned in the guide. Transfer and flash the lineageos.zip. Then directly after you should flash the twrp.zip Then reboot back into recovery and flash Magisk / Gapps etc if needed. Then finally reboot to system.
Also read this guide if you haven't already as it explains a lot about how flashing ROMs on OnePlus 6 is different to many other older phones.
Hi and thank you makeyourself
I tried the following steps:
1. starting fastboot
2. fastboot boot twrp-3.3.1-2-enchilada.img -> twrp starting up
3. adb push twrp-installer-3.3.1-2-enchilada.zip /sdcard/ -> transfer ok
4. adb push lineage-16.0-20190922-nightly-enchilada-signed.zip /sdcard/ -> transfer ok
5. in twrp Wipe -> Format Data
6. in twrp Advanced Wipe -> System
7. in twrp install lineage-16.0-20190922-nightly-enchilada-signed.zip
8. in twrp install twrp-installer-3.3.1-2-enchilada.zip
9. reboot to recovery
After this steps I got the same problem as before. Before the reboot to recovery, twrp showed the message "no OS installed". So I think, the zip weren't installed correctly. Now, I have the black screen with the blue led. Can you find out what I did wrong?
Edit: Now, I can't also boot twrp. Also if I do a fastboot boot twrp-3.3.1-2-enchilada.img nothing happens.
Fastboot to twrp (newest blu spark should be fine, or black twrp)
Flash twrp zip
Reboot to twrp
Wipe data, cache.
Flash recommended oos
Flash twrp
Reboot to twrp
Flash recommended twrp (yes...... Again)
Flash twrp (yes... Again, recovery is lost after rom Flash ALWAYS)
Reboot to twrp
Flash LOS or any other custom rom
Flash twrp (rom Flash, so twrp is lost like I said)
Reboot to twrp
Flash magisk (IF ypu want magisk)
Flash gapps (IF ypu want gapps)
Flash kernel (IF I like to run another custom kernel)
Boot
Enjoy
Thank you whizeguy, I'll try this. But just one question about "Flash recommended oos". Which OxygenOS can I flash (this full OTA? https://www.xda-developers.com/oneplus-6-oneplus-6t-oxygenos-9014-906/) and why I have to do this? Sorry if it is a bad question.
You Flash The oxygen OS version that is recommended in Los thread, simple as that.
You have an a/b device, vendor partition (could be other files needed aswell, not 100 % sure) is needed to Flash custom, IF you did Amy research you'd finns some good info. Also for faster answers in The future: post your issue in the thread for LOS, that way you would get help from People Who uses it, knows The exact version you should use and what not
Hey whizeguy, thank you very much. Everything works perfect now. But why for heaven's sake do I have to flash oos and why the guide on the LineageOS site don't tell me this way?
Wow idk what happened here. Mistakenly replied to this thread. Apologies.
I've tried installing PixelExperience 10 on my phone (which is unlocked and with a custom recovery) and first it throw me Error 7, but that was because I hadn't flash the firmware and vendor .zips before PixelExperience, but even flashing that, the device bootloops until a certain point and then it boot back to recovery.
I've tried with dotOS, LineageOS, even MIUI, multiple versions of it, and non of it are working. The device just bootloops with everything.
Fastboot is accesible, recovery is accesible. I'm using OrangeFox Version R10.0_2, but I originally installed TWRP and I had the same problem.
Have you tried flashing TWRP, then using TWRP recovery environment to wipe EVERTHING, then use adb to push lineageOS (since you will have wiped internal data and lost your rom file)
RunNgun42 said:
Have you tried flashing TWRP, then using TWRP recovery environment to wipe EVERTHING, then use adb to push lineageOS (since you will have wiped internal data and lost your rom file)
Click to expand...
Click to collapse
OrangeFox lets me wipe the same partitions (even Vendor, which TWRP doesn't let me).
I'm not sure if I can install Lineage OS thru adb because it asks for MIUI firmware to be installed. If I wipe everything, I loose the firmware.
Althought, I haven't wiped the internal storage in I while, since I have all the roms and zips, there. I'll try with that.
Make "Format Data" - Yes after that wipe data, system, cache and vendor. Copy zips to storage and dont sideload.
Flash fw 9.6.27, los17 and opengapps. Must work.
The way these roms work you basically have to have previously installed a corresponding version of MIUI first. For instance, if you want to install los16 then you must have previously been running MIUI 10. If you want to install los17 then you need to install MIUI 11 first. I guess Xiaomi does some weird stuff to the internal storage between flashes. If you're stuck in a bootloop the easiest thing to do is use the official MiFlash tool to flash the ROM version of your choice. MiFlash uses fastboot rom files. This site has the best catalog of roms
https://xiaomifirmwareupdater.com/miui/
MAKE SURE YOU UNTICK "Clean and lock" at the bottom or else you will relock your bootloader!
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!
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.