Related
Hello guys. Yesterday ( October 30th) I had a notification about upgrading from 10.0.2.0 to 10.0.3.0. I was rooted with Magisk, and after the update the root privileges were gone. I tried to boot to TWRP again, but it stays encrypted without asking for password as usual, so I am unable to flash the zip and root again. Is it ok if I use the boot.img in order to install via patched_boot?As for now there isn't 10.0.3.0 firmware available for download in order to extract it. Thank you for your time.
I am also interested about update with Magisk
GeorgeKatsi said:
Hello guys. Yesterday ( October 30th) I had a notification about upgrading from 10.0.2.0 to 10.0.3.0. I was rooted with Magisk, and after the update the root privileges were gone. I tried to boot to TWRP again, but it stays encrypted without asking for password as usual, so I am unable to flash the zip and root again. Is it ok if I use the boot.img in order to install via patched_boot?As for now there isn't 10.0.3.0 firmware available for download in order to extract it. Thank you for your time.
Click to expand...
Click to collapse
You can flash patched_boot to get the TEMP magisk working before the new twrp available for 10.0.3.0
Code:
fastboot boot patched_boot.img
The boot image can be patched via magisk by yourself or you can use mine from 20181104_mi8_10.0.3.0_patched_boot.img
Remember this TEMP solution fails after rebooting. Or you fastboot boot patched_boot.img every rebooting.
Hello ich have the Same Problem, can U Tell step by step how to do that?
Ich want to flash custom Rom
same issue im on miui.eu 10.0.8.0 with encryption enabled.
Booting into recovery TWRP does not ask for passcode to decrypt data
mikefallen said:
same issue im on miui.eu 10.0.8.0 with encryption enabled.
Booting into recovery TWRP does not ask for passcode to decrypt data
Click to expand...
Click to collapse
I flashed the patched_boot made by magisk, but I am still unable to decrypt twrp. I hope they support 10.0.3.0 soon so I can use twrp again.
Hello guys,
I made an update in TWRP and installed Havoc 2.4 to try it. After 1 hour I restored my backup and changed back to MIUI. I couldn't log in, so I cleaned the keyfiles to set a new pin.
I reflashed new Beta (25.4 MIUI - Xiaomi.eu) ROM and Magisk but root does not apply on my device... What is wrong? Seems that it's not possible to root anymore... Its does not give me any fails when installing the magisk 18.1 zip in TWRP...
thanks in advance
Have you tried a simple reboot? Usually it takes a reboot more to apply.
no it's not that. now its always booting into twrp when I try to flash magisk
makmak001 said:
no it's not that. now its always booting into twrp when I try to flash magisk
Click to expand...
Click to collapse
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.
I fixed it by wiping data... now its working
tsongming said:
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.
Click to expand...
Click to collapse
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Sent from my Xiaomi MI 8 using XDA Labs
slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Here you can see that I have root and latest update
Sent from my Xiaomi MI 8 using XDA Labs
tsongming said:
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Click to expand...
Click to collapse
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?
slave2007 said:
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?
Click to expand...
Click to collapse
I no longer use Viper because my phone has 1 speaker and for me Ainur Sauren works pretty well for all sounds.
For listening to music I have the Pro version of Power amp which has every wanted option such as dynamic compression, dynamic EQ, convolution reverb, limiting , tag editing, visualizations etc, I bought it 5 years ago for $3. Best 3 bucks that I ever spent!
Seriously, I can't recommend Poweramp highly enough, its worth its weight in gold.
Sent from my Xiaomi MI 8 using XDA Labs
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.
Now that we have finally got the update in the EU region I want to know if anyone has successfully flashed TWRP or any other recovery?
In case anyone wondering I have managed to get root with the latest magisk via patched boot image method.
**UPDATE**
I flashed the latest TWRP from this thread and all went smoothly. Also managed to get Viper4android working which was my biggest concern coming from Android 9. Happy days :victory:
_ray_ said:
Now that we have finally got the update in the EU region I want to know if anyone has successfully flashed TWRP or any other recovery?
In case anyone wondering I have managed to get root with the latest magisk via patched boot image method.
Click to expand...
Click to collapse
I'm currently on MIUI 10.3.4.0 Stable with OrangeFox Recovery installed, Going to attempt updating later since, afaik, OrangeFox has Support for OTA Updates.
Fatal_Scythe said:
I'm currently on MIUI 10.3.4.0 Stable with OrangeFox Recovery installed, Going to attempt updating later since, afaik, OrangeFox has Support for OTA Updates.
Click to expand...
Click to collapse
Good luck and please do post back the results :good:
Fatal_Scythe said:
I'm currently on MIUI 10.3.4.0 Stable with OrangeFox Recovery installed, Going to attempt updating later since, afaik, OrangeFox has Support for OTA Updates.
Click to expand...
Click to collapse
Waiting for your feedback, because my orangefox is ready for OTAs but i think because i forgot to check DM VERITY and FORCED ENCRYPTION it asks for password when rebooting for update and ruins it...this is my guess. So please share your feedback and it you checked the 2 options unlike me.
Sent from my Redmi K20 Pro using Tapatalk
I'm also interested in this. I want to keep TWRP and magisk post-upgrade to Android 10
I updated with no issued with the following steps:
1. Installed latest TWRP from here https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
2. Download latest Magsik
3. Download recovery zip for miui 11 rom
4. Reboot to recovery
5. Install rom zip ( do not reboot after install)
6. Install Magsik
7. Install TWRP img via recovery that you downloaded in step 1
8. Reboot into TWRP
9. Reboot to system
_ray_ said:
Good luck and please do post back the results :good:
Click to expand...
Click to collapse
ishaqtkr said:
Waiting for your feedback, because my orangefox is ready for OTAs but i think because i forgot to check DM VERITY and FORCED ENCRYPTION it asks for password when rebooting for update and ruins it...this is my guess. So please share your feedback and it you checked the 2 options unlike me.
Click to expand...
Click to collapse
Okay so, coming from 10.3.4.0 Stable, OFox Recovery and encrypted, the update ran through fine without any problems. Since I'm encrypted I had to enter my password first but after that it started installing the Update. as far as I remember, I've seen that Orangefox's script that prevents Orangefox from being overwritten after every update (it's called OTA.bak I think) already handles both DM-Verity and Force-Encrypt on it's own, at least I didn't had to take any further steps regarding Encryption and such stuff and after updating it booted into MIUI 11 just fine (which ofc since it's an Major Update took a little longer than usual but at least it eventually did)
desiresiscool said:
I updated with no issued with the following steps:
1. Installed latest TWRP from here https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
2. Download latest Magsik
3. Download recovery zip for miui 11 rom
4. Reboot to recovery
5. Install rom zip ( do not reboot after install)
6. Install Magsik
7. Install TWRP img via recovery that you downloaded in step 1
8. Reboot into TWRP
9. Reboot to system
Click to expand...
Click to collapse
So what do you do when you're on 10.3.4 pfkeuxm Rom and running with twrp and magisk installed?
Can't I install the miui 11 rom via twrp and then immediately flash magisk again?
Following the advice here, I've got the update installed with twrp and magisk working fine. The only problem I have is that I can't read/write the system partition so titanium backup isn't working. Any ideas how I could fix it?
Hello everyone, i am new here
I know from the official guides of Magisk that you can NOT flash Magisk from recovery or use a custom recovery if you have no ramdisk(if i understood correctly) and that you must patch your recovery and flash it back to the phone using Odin or other flashing software..
So there are this indian videos showing how they rename Magisk.apk to Magisk.zip and flash it from TWRP and its successful even tho Magisk clearly showes "ramdisk: no"...most of the videos use Magisk V22.0
So my question is it really possible to flash Magisk.zip (obtained by renaming Magisk.apk) from recovery(TWRP) without having ramdisk? Has something changef and the developers forgot to update the official guides??
For reference here is one video in English doing that
Magisk works fine ramdisk=no. However I noticed when you set a pin and reboot the TWRP pin shows preboot and does not work to log in. I'm wondering if magisk patched the TWRP recovery instead of stock recovery would this work? Because of this issue I have had to flash several times. I'm using the Cherish GSI and everything works great except the pin issue.
Oukitel K9 Cherish GSI
nation888888 said:
Magisk works fine ramdisk=no. However I noticed when you set a pin and reboot the TWRP pin shows preboot and does not work to log in. I'm wondering if magisk patched the TWRP recovery instead of stock recovery would this work? Because of this issue I have had to flash several times. I'm using the Cherish GSI and everything works great except the pin issue.
Oukitel K9 Cherish GSI
Click to expand...
Click to collapse
Yes, magisk can patch twrp and it seems to work well for me