Hi,
I have the following problem.
I was able to install the custom ROM properly on my Mi9t pro. Unfortunately my Orangefox Recovery was deleted After the installation.
If I want to install Magisk now, I have to reflash the recovery first.
Do you have any idea why the recovery is deleted? Is there a way to prevent that?
Thanks in advance.
der_andi01 said:
Hi,
I have the following problem.
I was able to install the custom ROM properly on my Mi9t pro. Unfortunately my Orangefox Recovery was deleted After the installation.
If I want to install Magisk now, I have to reflash the recovery first.
Do you have any idea why the recovery is deleted? Is there a way to prevent that?
Thanks in advance.
Click to expand...
Click to collapse
Your (custom) Recovery was really deleted?
Or replaced by stock Recovery
Who says that installation of Magisk requires custom Recovery?
Magisk documentation (Installation Instructions) - please find it on Magisk Github - certainly not.
Patch the boot.img and flash (it can be flashed by Fastboot, hence custom Recovery is not a must to have)
Hi,
it really gets deleted. My cell phone is then only in fastboot mode.
I am not interested in flashing Magisk either, but rather that recovery after an installation is no longer available. This makes installing updates more cumbersome.
I only have the problem when I flash a custom ROM. when I flash a MIUI ROM from xiaomi.eu Beta, the recovery is retained.
Related
Hello guys.
I've just tried to update to MIUI 9.0.1.0 NDDMIEI from MIUI 8.5.9.0 NDDMIED on device Xiaomi Mi Max 2 but it failed.
I have an unlocked bootloader and SuperSu installed, but the recovery is Mi Stock Recovery. :cyclops:
I had directly booted TWRP Recovery without flashing using
Code:
fastboot boot twrp.img
to flash SuperSu on device. :good:
Need support with this issue. I don't want to flash whole ROM every time I recieve an update.
steve.24 said:
Hello guys.
I've just tried to update to MIUI 9.0.1.0 NDDMIEI from MIUI 8.5.9.0 NDDMIED on device Xiaomi Mi Max 2 but it failed.
I have an unlocked bootloader and SuperSu installed, but the recovery is Mi Stock Recovery. :cyclops:
I had directly booted TWRP Recovery without flashing using
Code:
fastboot boot twrp.img
to flash SuperSu on device. :good:
Need support with this issue. I don't want to flash whole ROM every time I recieve an update.
Click to expand...
Click to collapse
i successfully flashed to miui v9(V9.0.1.0.NDDMIEI) over miui v8(V8.5.8.0.NDDMIED) without data wipe. all my data were intact
Keep a backup just in case
make sure you downloaded recovery flashable full rom package ~1.38GB (not the 500mb OTA update )
donot wipe data/cache/dalvik
flash via TWRP recovery
just flashing rom wont boot due to dm-verity. (result will be bootloop)
u need to flash super user or magisk (or lazy flasher "ive not tried though" ) which patches boot.img which makes rom bootable
reversegear said:
i successfully flashed to miui v9(V9.0.1.0.NDDMIEI) over miui v8(V8.5.8.0.NDDMIED) without data wipe. all my data were intact
Keep a backup just in case
make sure you downloaded recovery flashable full rom package ~1.38GB (not the 500mb OTA update )
donot wipe data/cache/dalvik
flash via TWRP recovery
just flashing rom wont boot due to dm-verity. (result will be bootloop)
u need to flash super user or magisk (or lazy flasher "ive not tried though" ) which patches boot.img which makes rom bootable
Click to expand...
Click to collapse
I'll give it a try. Currently I have data wiped and installed full ROM through fastboot method. So next time, for sure I'll give it a shot.
But I have a doubt, where TWRP be able to flash an MIUI ROM. I mean the bootloader unlocked, encrypted system partition and all.
Since you have your device rooted, first install flashify, and backup your stock recovery. Then you can flash twrp recovery and install Miui 9, and root the device again. Last, install flashify again and restore your stock recovery.
scholastova said:
Since you have your device rooted, first install flashify, and backup your stock recovery. Then you can flash twrp recovery and install Miui 9, and root the device again. Last, install flashify again and restore your stock recovery.
Click to expand...
Click to collapse
Can you give stock recovery from mi max 2? I forgot to back up his original recovery stock and was hit with twrp.
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Akash731 said:
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Click to expand...
Click to collapse
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Akash731 said:
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Click to expand...
Click to collapse
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
pradeeppk said:
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
Click to expand...
Click to collapse
I don't want to try custom rom's as this is my main device guess I'm stuck with the encryption then thanks for your help. :good:
Edit:-
Tried TWRP r20 it decrypts fine thanks
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
gewe said:
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
Click to expand...
Click to collapse
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
I am using stock ROM, and yes, also Magisk (installed later). IIRC Magisk is not needed for TWRP to work. When I receive the next OTA notification, I will test this.
The thread you are referring to is for a OnePlus 3T. For our device this is the thread: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910.
Since there is no official TWRP for the Moto G5S Plus, I took the following text from the TWRP page for the Moto G5S.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Instead of that you can also use fastboot reboot-bootloader, and then from the bootloader start recovery.
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
gewe said:
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
Click to expand...
Click to collapse
As like you said this is the first time in my life i need to flash magisk to stick twrp.
I usualy doesn't use root or custom roms, install twrp, remove unnecessary apps from stock system, replace host files with adaway hosts, replace or edit gps config files. and continue using stock.
This is the main routine from Android 1.5
(Samsung spica (i think it was the first Android phone from Samsung)).
It may be due to security reason stock kernel or system delete twrp.
When installing magisk it patch stock boot image, that may be the reason of twrp remains after flashing magisk.
Hello, I have a Mi 9T Pro with 10.3.3, TWRP and Magisk. I received the update to 10.4.0. As stated in the title, how could I update the system without losing the TWRP and root through Magisk? Thank you in advance
MagikGab said:
Hello, I have a Mi 9T Pro with 10.3.3, TWRP and Magisk. I received the update to 10.4.0. As stated in the title, how could I update the system without losing the TWRP and root through Magisk? Thank you in advance
Click to expand...
Click to collapse
You can't. The best way to update is to download the 10.4.0 recovery ROM, then flash that in TWRP. This will still overwrite Magisk, so you will need to install that again straight after installing the update. If you don't install Magisk immediately, then booting into system would also restore stock recovery, so it needs to be done before you reboot to system.
Robbo.5000 said:
You can't. The best way to update is to download the 10.4.0 recovery ROM, then flash that in TWRP. This will still overwrite Magisk, so you will need to install that again straight after installing the update. If you don't install Magisk immediately, then booting into system would also restore stock recovery, so it needs to be done before you reboot to system.
Click to expand...
Click to collapse
Many thanks! In this way I could at least save the TWRP! Should I have to take some other precautions? Like deactivate all Magisk modules, perform a backup of apps ecc?
i have the same question too..
MagikGab said:
Many thanks! In this way I could at least save the TWRP! Should I have to take some other precautions? Like deactivate all Magisk modules, perform a backup of apps ecc?
Click to expand...
Click to collapse
No, you can simply flash the ROM and right after that, flash Magisk. This way you won't loose twrp or Magisk.
MagikGab said:
Many thanks! In this way I could at least save the TWRP! Should I have to take some other precautions? Like deactivate all Magisk modules, perform a backup of apps ecc?
Click to expand...
Click to collapse
P12AV33N said:
No, you can simply flash the ROM and right after that, flash Magisk. This way you won't loose twrp or Magisk.
Click to expand...
Click to collapse
I would just add to this that, although this is all that is required, I would still backup things, just in case.
It's always good practice when flashing things to backup what you can, even when it's not needed should things go smoothly. It only takes an absent minded moment of stupidity in TWRP to do some serious damage. As many people, myself included, can vouch for.
Thank you everyone!
I've read a lot about this, some say it's better with fastboot rom and Miflash, but twrp method with recovery seems to be easier method.
Can anybody confirm is it necessary to remove compatibility.zip file from flashable zip file before flashing?
Clean flash or dirty should work for 10.3.4.0 update?
I'm using 9T Pro (EU), rooted, stock 10.3.3.0, TWRP 3.3.1-15
macanovic88 said:
I've read a lot about this, some say it's better with fastboot rom and Miflash, but twrp method with recovery seems to be easier method.
Can anybody confirm is it necessary to remove compatibility.zip file from flashable zip file before flashing?
Clean flash or dirty should work for 10.3.4.0 update?
I'm using 9T Pro (EU), rooted, stock 10.3.3.0, TWRP 3.3.1-15
Click to expand...
Click to collapse
Flashing a minor update is fine to do as a dirty flash in TWRP.
Doing a major update is 50/50 (going from 10.3.x to 10.4.x as it's s change from Android 9 to 10, or going from 10.x.x to 11.x.x). You may be fine, you may have issues. It might be a better option to try using the 'save data' option in the Mi Flash Tool, which is the same as a dirty flash, but will still update vendor and firmware files, should they have changed between the versions.
You might be guided by what the OTA would do. Occasionally when an OTA provides a major version change, it will perform a clean flash and give you big warnings that this will happen first. If an OTA tells you this will happen, then I would definitely use the Mi Flash Tool and use the 'clean all' option.
As for the compatibility zip, it depends on the TWRP you are using. Just try as is first and if your get an error about the wrong device, then remove it and try again.
Thanks a lot, your answers are very helpful in this thread! ?
I got the OTA update to 10.3.4.0 on my Mi 9T Pro, too, but it wouldn't install via TWRP (mauronofrios version 3.3.1-15). I also tried to flash the full 10.3.4.0 ROM (https://bigota.d.miui.com/V10.3.4.0...EAGlobal_V10.3.4.0.PFKEUXM_964826982c_9.0.zip) with TWRP, but that didn't work either, not even after removing compatibility.zip.
I then changed my TWRP to OrangeFox Recovery 10.0_7 stable (via fastboot) and dirty flashed the full ROM via OrangeFox. That worked flawlessly, it even seems that it will be able to install future OTA updates, but that remains to be seen when the next OTA update arrives.
cgdams said:
I got the OTA update to 10.3.4.0 on my Mi 9T Pro, too, but it wouldn't install via TWRP (mauronofrios version 3.3.1-15). I also tried to flash the full 10.3.4.0 ROM (https://bigota.d.miui.com/V10.3.4.0...EAGlobal_V10.3.4.0.PFKEUXM_964826982c_9.0.zip) with TWRP, but that didn't work either, not even after removing compatibility.zip.
I then changed my TWRP to OrangeFox Recovery 10.0_7 stable (via fastboot) and dirty flashed the full ROM via OrangeFox. That worked flawlessly, it even seems that it will be able to install future OTA updates, but that remains to be seen when the next OTA update arrives.
Click to expand...
Click to collapse
You need to confirm if orangefox is actually ready for OTA by checking in its settings.
Sent from my Redmi K20 Pro using Tapatalk
I cannot root my phone through TWRP for some reason and I would really like to use my phone with Google Pay.
K20 pro, MIUI Global 11.0.1 unlocked bootloader.
Install Magisk yourself. It will work.
Which zip did you flash? The right version of maiden
Magisk will work.
@XblackdemonX I can't install Magisk since it's giving me an error message. Tried every possible way with no luck
@Turbine1991 I have tried install "twrp-3.3.1-15-raphael-mauronofrio"
After installing it the phone is always going back to Stock rom recovery.
@XblackdemonX I can't install Magisk since it's giving me an error message. Tried every possible way with no luck
@Turbine1991 I have tried install "twrp-3.3.1-15-raphael-mauronofrio"
After installing it the phone is always going back to Stock rom recovery.
cohenelad said:
I cannot root my phone through TWRP for some reason and I would really like to use my phone with Google Pay.
K20 pro, MIUI Global 11.0.1 unlocked bootloader.
Click to expand...
Click to collapse
install magisk 19.3
Video install
https://drive.google.com/file/d/16vDfZDWBgtY8_ECB8aRWNed_6mqctY5T/view
@redmiK20ProIndonesia
Are you rebooting the device after installing TWRP? If you installed TWRP then rebooted without first trying to install Magisk it'll probably just stick the stock recovery back in place and overwrite TWRP if nothing is done to circumvent stock recovery overwrite. If this doesn't apply then no worries but thought I'd mention it.
That's also an old version of TWRP; have you tried a newer version? I'd say try fastboot boot recovery.img then immediately attempt to install Magisk. You're on MIUI11 so you'll want to go with Magisk 19.3.
cohenelad said:
After installing it the phone is always going back to Stock rom recovery.
Click to expand...
Click to collapse
You have to install Magisk to prevent the recovery from changing back to stock.
Received an update today , if i use standart ota updater via settings, does it overwrite the twrp and root stuff i have or it wont? Coz i never done this before, always using custom roms and now latest stock miui 11 with root.
You could flash the zip rom through the recovery, but keep in mind this. Let the phone boot with the new update, then go back to recovery (if you get the stock recovery, reflash it with fastboot), then flash magisk
So it is overwriting twrp and magisk even if i install it directly from twrp?
meezy5 said:
Received an update today , if i use standart ota updater via settings, does it overwrite the twrp and root stuff i have or it wont? Coz i never done this before, always using custom roms and now latest stock miui 11 with root.
Click to expand...
Click to collapse
You will loose Magisk/root but not Magisk Manager app and all Magisk data like modules, apps granted root, etc - once you re-root, everything will be there again.
I only suggest that you first un-hide Magisk Manager (if hidden for you), at the end you can hide it again
If you update via OTA, you will loose TWRP. If you don't want to flash TWRP again, then download the same full MIUI 12 zip package you got OTA notification for, and flash it from TWRP (without wiping, formatting or so), and immediately thereafter reboot first back to TWRP, and only then to MIUI 12
If you would like to update truly by OTA, you would have to flash the stock recovery back before starting the OTA.
Hence the way as described above, you save first on flashing stock recovery, and later on flashing TWRP back
Ok thanks so after twrp flash i have to reboot back to twrp , do i have to install force encrypt then to prevent overwriting twrp by miui or not?
meezy5 said:
Ok thanks so after twrp flash i have to reboot back to twrp , do i have to install force encrypt then to prevent overwriting twrp by miui or not?
Click to expand...
Click to collapse
See posts #933, #935-#937 in the TWRP thread:
https://forum.xda-developers.com/showpost.php?p=82945031&postcount=936