Database Develop

MI 8 SE Pie Update

Hello everyone, after xiaomi.eu update to Android Pie, I'm not able to flash or boot TWRP, so I can't restore my apps and, of course, I can't get root. So, there's a way to boot TWRP or, at least, to obtain root access? Thanks in advance

I updated to xiaomi.eu_multi_MI8SE_8.11.1_v10-9. The stock recovery doesn't work anymore, so we need an updated version for Android Pie.

Sebbo06 said:
I updated to xiaomi.eu_multi_MI8SE_8.11.1_v10-9. The stock recovery doesn't work anymore, so we need an updated version for Android Pie.
Click to expand...
Click to collapse
Try new twrp, in xiaomi eu forum someone give link for download new twrp
After flash pie update are you get option for hide notch
Sorry my bad english

Here is new TWRP img working with Pie -
https://forum.xda-developers.com/showpost.php?p=78047648&postcount=14
Flash from your existing TWRP, or from fastboot if you've lost recovery
Can verify its working with MIUI PIe release 8.11.1, and with Magisk 16.6 for root

same thing happened to me, did anyone figure it out?
danielwright said:
Here is new TWRP img working with Pie -
https://forum.xda-developers.com/showpost.php?p=78047648&postcount=14
Flash from your existing TWRP, or from fastboot if you've lost recovery
Can verify its working with MIUI PIe release 8.11.1, and with Magisk 16.6 for root
Click to expand...
Click to collapse
this worked for me, thank you

Oneplus 6 Bootloop after flashing Magisk over Oxygen OS Beta 11

Here is what I have done:
1. Boot into TWRP recovery
2. Flash OOS 9.0.3 Beta 11 followed by TWRP and Wipe Dalvik Cache
3. Reboot Successfully to android
4. Boot back into TWRP and flash Magisk 18.0 (I also tried 18.1, same result)
5. Bootloop
I've done this multiple times, each time I was able to get back into android before flashing Magisk.
Thank You for your help, much appreciated.

This might go without saying but after flashing Magisk are you also wiping Dalvik?

Nuzzlet said:
Here is what I have done:
1. Boot into TWRP recovery
2. Flash OOS 9.0.3 Beta 11 followed by TWRP and Wipe Dalvik Cache
3. Reboot Successfully to android
4. Boot back into TWRP and flash Magisk 18.0 (I also tried 18.1, same result)
5. Bootloop
I've done this multiple times, each time I was able to get back into android before flashing Magisk.
Thank You for your help, much appreciated.
Click to expand...
Click to collapse
I could be wrong but I do it slightly differently.
1. Boot into TWRP.
2. Flash rom, flash TWRP
3. Reboot TWRP, flash magisk.
4. Reboot system
Works for me.

TLX317 said:
This might go without saying but after flashing Magisk are you also wiping Dalvik?
Click to expand...
Click to collapse
Yes I am
mixlex said:
I could be wrong but I do it slightly differently.
1. Boot into TWRP.
2. Flash rom, flash TWRP
3. Reboot TWRP, flash magisk.
4. Reboot system
Works for me.
Click to expand...
Click to collapse
So I finally made it work by flashing with "Blue" TWRP. I still don't really understand the difference between the official TWRP. Whiel in loop looping after installing magisk, I went back to TWRP, flashed Blue TWRP and it booted. Wen't back intro Blue TWRP and flashed Magisk 18 (Not 18.1, thought that might have been why) and it worked. It confused me because I have successfully flashed magisk with the other TWRP before so I really don't know what fixed this.
Thank you for your help. I think I flashed me rom over 30 times yesterday getting this to work.

Nuzzlet said:
Yes I am
So I finally made it work by flashing with "Blue" TWRP. I still don't really understand the difference between the official TWRP. Whiel in loop looping after installing magisk, I went back to TWRP, flashed Blue TWRP and it booted. Wen't back intro Blue TWRP and flashed Magisk 18 (Not 18.1, thought that might have been why) and it worked. It confused me because I have successfully flashed magisk with the other TWRP before so I really don't know what fixed this.
Thank you for your help. I think I flashed me rom over 30 times yesterday getting this to work.
Click to expand...
Click to collapse
Hi could you please provide me the link to the blue TWRP you have used? I'm stuck in the same situation as you. Pls help

a4abbas said:
Hi could you please provide me the link to the blue TWRP you have used? I'm stuck in the same situation as you. Pls help
Click to expand...
Click to collapse
At the moment I'm just using regular TWRP actually. Havnt used blue since I switched the beta builds. I actually remember having trouble finding a download for Blu spark. What are your issues?

TWRP gets replaced by stock recovery

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.

Lineage OS 17 unable to root with Magisk

Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks

vehz said:
Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks
Click to expand...
Click to collapse
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP

ISoreo said:
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP
Click to expand...
Click to collapse
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time

vehz said:
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time
Click to expand...
Click to collapse
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot

ISoreo said:
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot
Click to expand...
Click to collapse
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root

vehz said:
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root
Click to expand...
Click to collapse
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!

jonapiron said:
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!
Click to expand...
Click to collapse
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
https://drive.google.com/drive/folders/1UdPbIbM3luYIiOdXMXb7raAnWLERjssh
beyond0lte folder is for S10E.

vehz said:
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
beyond0lte folder is for S10E.
Click to expand...
Click to collapse
Oh I'm so stupid, I had seen the Magisk boot img in the files but ended up using another one... It seems to work now, thank you sooo much!!
It still cannot pass SafetyNet check (ctsProfile), I'll investigate that...

I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).

I am trying root Lineage 18.1 on my s10. I have tried differtent magisk-files from TWRP, but still no root access.
What are the required files for 18.1 for Galaxy s10 and steps to get root-access?

Hafizp5100 said:
I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).
Click to expand...
Click to collapse
Dude, thanks so much. I faced the exact same problem with my Z2, now it's running magisk just fine. You saved me a bunch of headaches.

Flashed Lineage os 17.1 with twrp and accidently missed checking the boot box ...

when i flashed the rom and now i no longer have access to root, twrp and on top of that.... gapps failed so i lost my google account on my phone. can anyone help me recover twrp, root, and successfully flash gapps. i have a great working os 17.1. no complaints there.

badwax said:
when i flashed the rom and now i no longer have access to root, twrp and on top of that.... gapps failed so i lost my google account on my phone. can anyone help me recover twrp, root, and successfully flash gapps. i have a great working os 17.1. no complaints there.
Click to expand...
Click to collapse
LineageOS 17.1 comes with a own recovery. Use the installer.zip provided on twrp.me to install TWRP. After that start TWRP and format /data. That's necessary to install the GApps. Otherwise you end in a bootloop.
Now flash GApps and Magisk and boot into system.

You can also temporarily boot into TWRP with "fastboot boot twrp.img" in fastboot. Then do backups etc. and reinstall the system.