Database Develop

TWRP 3.1.0 - wipes userdata and more

I install latest TWRP 3.1.0 version today.
All the user data, some apps (Waze, Gmail, Gmaps...), SMS were wiped.
I have RR-N-v5.8.2-20170218-oneplus3t-Official currently installed.
I reinstall some apps back.
After system reboot all seemed fine.... But after boot to recovery (TWRP 3.1) and than boot into system all was gone again.
It looks like every boot to recovery wipes user data and some apps...

Flash 3.0.4-1 again

Same problem here with 3.1.0.0.

I flashed 3.1.0.0 img with 3.0.4-1 and do not have the issues OP is describing.
Edit: stock Open Beta 3 rooted.

sossio18 said:
Flash 3.0.4-1 again
Click to expand...
Click to collapse
I did... and restore system from backup BUT some userdata is gone forever...

Apparently, the official TWRP 3.1.0-0 for OnePlus 3T only works with Oxygen OS. So far, only users using custom ROMs have reported issues with partition wipes after flashing the latest TWRP.

Anova's Origin said:
Apparently, the official TWRP 3.1.0-0 for OnePlus 3T only works with Oxygen OS. So far, only users using custom ROMs have reported issues with partition wipes after flashing the latest TWRP.
Click to expand...
Click to collapse
Happened to me on OOS. Went back to 3.0.4-1
Sent from my OnePlus 3T using XDA Labs

It was updated to 3.1.0-1 try that

I suppose this of because of the official TWRP 3.1.0-0 is not using the backported F2FS driver. I'm using EXT4 filesystem on data partition so therefore I'm not experiencing any data loss.

Was on RR 09.03 with OB3 firmware, it completely destroyed my phone. Bootloops, impossible to go back to recovery, when in recovery, impossible to see files to flash them, even going back to 3.0.4.1 did not solve everything, reinstalled Freedom OS but had screen total freezes.... Had to go through the total disaster recovery utility, and I am still re-installing everything...
TWRP 3.1.0.0 ate 4 hours of my flash-addicted life... FML !!!
**STAY AWAY FOR NOW**

Blu_spark 3.1.0 version is not affected by this, only the official.

Stock OOS 4.0.3 and TWRP 3.1.0-1 = ALL GOOD!

Kjaups said:
Stock OOS 4.0.3 and TWRP 3.1.0-1 = ALL GOOD!
Click to expand...
Click to collapse
Can confirm. TWRP 3.1.0-1 works fine. (rooted OOS 4.0.2)

I had at least two serious issues with official TWRP 3.1.0-1 and LineageOS:
1.) After a first flash attempt via fastboot I was no longer able to unlock my phone with my PIN under LineageOS.
2.) When booting into TWRP I got a black screen - unable to do any useful.
3.) After I could no longer unlock my phone under LineageOS I reinstalled LineageOS from TWRP 3.1.0-1. All looked fine until I rebooted from TWRP into LineageOS: TWRP obviously wiped my device and I was offered
the setup wizzard of LineageOS. All my setting were gone.
I had issue 3.) already with TWRP 3.0.3-1. I immediately reflashed TWRP 3.0.4-1 - the currently only working TWRP version.
I would like to add that I had removed any encryption on the phone before I started at 1.). My device is still unencrypted. I once removed stock encryption because I heard about problems with TWRP and encryption.

[SOLVED!] Can't install Magisk without bootloop

Scroll down over this post to see anwer!
Hey there! I just got my Xiaomi Mi8 from HK Goldway at Aliexpress. It came with its bootloader already unlocked and a Global ROM flashed.
I wanted to install Magisk but failed horribly . I've already done that to several phones (my last one was a Moto X Play, and it worked without major complications). But with this one, it seems I can't get past the bootlogo.
Stock Fastboot image used:
dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global
This is what I've tried so far:
First try
Flashed TWRP for Mi8 version 0711.
Flashed Magisk.
Got a bootloop.
Reflashed stock image via Fastboot.
Second try
Booted (not flashed) TWRP.
Tried to install latest global weekly from this thread.
Also got a bootloop.
Reflashed stock image via Fastboot.
Third try
I thought that those flashable ZIP firmwares were too small for them to be a full-fledged OS. So I went and downloaded this other one. Global version.
I read somewhere that I needed to format data before flashing a new image, so I did.
Booted TWRP.
Formated data (not Wipe)
Installed that ZIP from TWRP and booted correctly.
Booted TWRP again and flashed Magisk.
Got bootloop.
Back to stock image via fastboot.
Last try
Booted TWRP.
Formatted data.
Installed MIUI via TWRP.
Without rebooting, flashed Magisk and no-verity-opt-encrypt-6.0.zip.
This got past bootlogo ("Unlocked" message changed to "powered by Android") but got stuck there. Not booting at all.
Right now I'm back to the last try, booting MIUI successfully but without Magisk nor no-verity-opt-encrypt.
I kinda have no more ideas left. I understand this is a new device but I can't understand why people claim the have been able to install Magisk and I can't! Other thoughts were, maybe they were running MIUI 10 Beta and it only works with that version? I'm unsure about that.
Can someone lend me a hand? What am I missing?
Thank you!!
EDIT: FIX!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7.
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata.
Rebooted.
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Hope this works out for everyone having this problem!

have you tried to use Magisk 16.4,
if not, try to follow this guide:
https://www.theandroidsoul.com/xiaomi-mi-8-root/

gulp79 said:
have you tried to use Magisk 16.4,
if not, try to follow this guide:
https://www.theandroidsoul.com/xiaomi-mi-8-root/
Click to expand...
Click to collapse
Thank you for the fast reply!
I followed that guide and tried these steps:
fastboot boot mi8-twrp-3.2.2.img
Unencrypted via Pattern
Flashed Magisk v16.4 + DM verity disabler file
Reboot
But I'm still stuck at "powered by Android" bootlogo.
Normally it boots within 5 seconds but now it's taking forever. I'll wait a few minutes to see what happens.
I'm attaching some screenshots of the install process.

Padlite said:
Thank you for the fast reply!
I followed that guide and tried these steps:
fastboot boot mi8-twrp-3.2.2.img
Unencrypted via Pattern
Flashed Magisk v16.4 + DM verity disabler file
Reboot
But I'm still stuck at "powered by Android" bootlogo.
Normally it boots within 5 seconds but now it's taking forever. I'll wait a few minutes to see what happens.
I'm attaching some screenshots of the install process.
Click to expand...
Click to collapse
Ok,
but if you install Magisk 16.4, don't install also DM verity disabler.
DM verity disabler is needed if you don't want to root (see poin 14 in the linked guide).
Hope it works...

gulp79 said:
Ok,
but if you install Magisk 16.4, don't install also DM verity disabler.
DM verity disabler is needed if you don't want to root (see poin 14 in the linked guide).
Hope it works...
Click to expand...
Click to collapse
If I only flash Magisk 16.4, then phone shows "Powered by Android" and instantly reboots into stock recovery.
Only way to get it back booting, is performing fastboot flash boot boot.img from stock dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global image
I read somewhere about official and unofficial bootloader unlock. I didn't unlock the bootloader myself. Maybe it has something to do with it?
PS: Anyone had any luck using Magisk with MIUI 9.5.13?

Did you try with a newer magisk version ? ... 16.7 was released 15 day ago
https://github.com/topjohnwu/Magisk/releases
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-v16.7.zip
It´s a good practice to use magisk_uninstaller before flash new one if you had problems.
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-uninstaller-20180719.zip
Please tell us if it´s works

Seems that also others users have this problem
https://forum.xda-developers.com/showpost.php?p=77234924&postcount=6312

punk84z said:
Did you try with a newer magisk version ? ... 16.7 was released 15 day ago
https://github.com/topjohnwu/Magisk/releases
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-v16.7.zip
It´s a good practice to use magisk_uninstaller before flash new one if you had problems.
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-uninstaller-20180719.zip
Please tell us if it´s works
Click to expand...
Click to collapse
I just tried that. Uninstalling and re-installing v16.7. Although it seems now it's doing a few more steps, I'm still getting the recovery bootloop.
Install log screenshot attached.
gulp79 said:
Seems that also others users have this problem
https://forum.xda-developers.com/showpost.php?p=77234924&postcount=6312
Click to expand...
Click to collapse
Exactly that. Maybe we'll need to wait for a supported Magisk version. I'm still wondering what's the difference between our Mi8's that some can get Magisk working and some not. ?

I am running Magisk stable and tmiui 10 from Xiaomi. Eu without any problems.

I have a Mi 8 se and i install the eu rom boot the phone , reboot to twrp wipe and factory reset and installed magisk 16.4 .this is how works for me

i have the same problem too..when using china stable rom 16.7 magisk can be installed successfully tried many times...
flashing global version seems to have this issue...
tried all this steps too but no luck in global rom...

Padlite said:
Hey there! I just got my Xiaomi Mi8 from HK Goldway at Aliexpress. It came with its bootloader already unlocked and a Global ROM flashed.
I wanted to install Magisk but failed horribly . I've already done that to several phones (my last one was a Moto X Play, and it worked without major complications). But with this one, it seems I can't get past the bootlogo.
Stock Fastboot image used:
dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global
This is what I've tried so far:
First try
Flashed TWRP for Mi8 version 0711.
Flashed Magisk.
Got a bootloop.
Reflashed stock image via Fastboot.
Second try
Booted (not flashed) TWRP.
Tried to install latest global weekly from this thread.
Also got a bootloop.
Reflashed stock image via Fastboot.
Third try
I thought that those flashable ZIP firmwares were too small for them to be a full-fledged OS. So I went and downloaded this other one. Global version.
I read somewhere that I needed to format data before flashing a new image, so I did.
Booted TWRP.
Formated data (not Wipe)
Installed that ZIP from TWRP and booted correctly.
Booted TWRP again and flashed Magisk.
Got bootloop.
Back to stock image via fastboot.
Last try
Booted TWRP.
Formatted data.
Installed MIUI via TWRP.
Without rebooting, flashed Magisk and no-verity-opt-encrypt-6.0.zip.
This got past bootlogo ("Unlocked" message changed to "powered by Android") but got stuck there. Not booting at all.
Right now I'm back to the last try, booting MIUI successfully but without Magisk nor no-verity-opt-encrypt.
I kinda have no more ideas left. I understand this is a new device but I can't understand why people claim the have been able to install Magisk and I can't! Other thoughts were, maybe they were running MIUI 10 Beta and it only works with that version? I'm unsure about that.
Can someone lend me a hand? What am I missing?
Thank you!!
Click to expand...
Click to collapse
i allso hade that problem
wen i got my phone it was with global rom
then i flashed twrp
didt like they said
wipe dalvik cache an cache an factory reset
flashed miui eu rom
then flashed twrp again rebooted into recovery
flashed magisk 16.4
ended up in staying on android logo
then i try format data an didt it all again
still android logo an nothing more
well then i didt what i allways didt on my other devices
i wiped dalvik cache
cache
data
system
then i flashed eu rom
an twrp again rebooted into recovery again
then flashed magisk 16.4
rebooted system an now it booted up
REMEMBER to manke a backup before flashing all off thise things otherwice u wont have the option to go back if something goes wrong

-fluffy- said:
i allso hade that problem
wen i got my phone it was with global rom
then i flashed twrp
didt like they said
wipe dalvik cache an cache an factory reset
flashed miui eu rom
then flashed twrp again rebooted into recovery
flashed magisk 16.4
ended up in staying on android logo
then i try format data an didt it all again
still android logo an nothing more
well then i didt what i allways didt on my other devices
i wiped dalvik cache
cache
data
system
then i flashed eu rom
an twrp again rebooted into recovery again
then flashed magisk 16.4
rebooted system an now it booted up
REMEMBER to manke a backup before flashing all off thise things otherwice u wont have the option to go back if something goes wrong
Click to expand...
Click to collapse
Well maybe the critical step is to wipe everything, including System.
Did you Format anything instead of Wipe this last try?
Also, could you please share a link from that working MIUI rom?
Thank you!

Sorry for double-posting, but I wanted to notify you I GOT IT!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata
Rebooted
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Here are some screenshots!

Padlite said:
Sorry for double-posting, but I wanted to notify you I GOT IT!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata
Rebooted
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Here are some screenshots!
Click to expand...
Click to collapse
Is Google Assistant ("OK Google") working for you now as well?

I just flashed magisk v16.0 over the Miui 8.7.26 build and it booted without issues.

japancakes said:
Is Google Assistant ("OK Google") working for you now as well?
Click to expand...
Click to collapse
I just checked and no. If I go to Google Settings -> Voice, Voice Match is disabled because "This feature is currently unavailable for this language". Even though it's set to English UK. Maybe there is some Magisk Module to enable it?

Thanks, followed these steps and it got magisk going on the recent global release. Only difference was i had to use fastboot erase userdata.
Padlite said:
Scroll down over this post to see anwer!
EDIT: FIX!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7.
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata.
Rebooted.
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Hope this works out for everyone having this problem!
Click to expand...
Click to collapse

Hey guys im a toal newbie to this whole flash theme but Ive purchased a mi8 and i would like to use GooglePay and so on, could someone give me a step by step tutorial , how to install all this stuff on my device ?

Padlite said:
Sorry for double-posting, but I wanted to notify you I GOT IT!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata
Rebooted
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Here are some screenshots!
Click to expand...
Click to collapse
well i didt not flash dm-verity an mine pass saftynet

Help getting from LineageOS 14.1 to OxagenOS 5.08 (Something wrong with flash mem?)

Hi,
maybe someone here can help me or point me in the right direction for a guide. That would be much appreciated!
I have a Oneplus 3T (A3003) that I flashed to LineageOS 14.1 with Magisk-Root a while ago.
I have been stuck on 14.1-20171005-NIGHTLY-oneplus3 for a while now, because since then, whenever I tried to do a nandroid backup from within TWRP, the backup failed because of some kind of error on the data partition (I believe). I haven't flashed a new version since then and haven't come around to it until now, because everything ran very smoothly. :silly:
Since I would like to switch to a more modern ROM (I was thinking of going back to Oxygen OS (5.08)) I started playing around with it yesterday and noticed that TWRP (I think 3.2.0) would not start anymore. It will always get stuck on the logo screen.
I then tried to flash a new version (3.2.3.1) through the Official TWRP app. It still got stuck on the logo screen and I tried flashing 3.2.3.0 after reading about problems with 3.2.3.1 but the results were the same.
Can you please tell me how to get TWRP working again and how to flash OxygenOS 5.08 on my 3T or point me to the neccessary guides?
Thank you.
Data about the phone:
ONEPLUS A3003
Android Verson 7.1.2
LineageOS Version 14.1-20171005-NIGHTLY-oneplus3
Security Oct. 5th 2017
Baseband MPSS.TH.2.0.c1.9-00102-M8996FAAANAZM-1.89286.1.99649.1
Kernel 3.18.31-lineageos-g0036392...

As OOS implies enforced encryption of data partition, going to an from it can be a bit tricky. Simplest way is by wiping using Qualcomm factory restore tool and then just OTA upgrade or flash latest OOS zip.
Skickat från min ONEPLUS A3003 via Tapatalk

@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Click to expand...
Click to collapse
That worked, thank you. Yes, my data partition is/was encrypted.

Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?

r_wraith said:
Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?
Click to expand...
Click to collapse
The OOS zip includes the firmware. Custom ROMs don't because they use the OOS firmware. The firmware is stored in separate partitions so it isn't affected by wiping the system and data positions.
Since you're coming from Los 14.1 you'll need to do the following in TWRP:
- take a backup of your current system
- do a factory reset to clear the data partition without losing the files stored on internal storage
- flash the OOS zip file
- flash Magisk 18.0 which will root the phone as well as prevent TWRP from being replaced by the stock OOS recovery
Sent from my OnePlus3T using XDA Labs

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?

Tried root with Magisk and now my phone doesn't start.

Hi all, as the title implies, I'm a newbie to all this. I tried to root my phone using an online guide on how to root xiaomi mi 9 using TWRP and Magisk. I faced some problems but eventually everything was done as the tutorial said.
Here are the exact steps I've done...
- unlocked the phone via Mi unlocking tool
- started fastboot and installed TWRP 3.3.1-0 ( I installed a version first that didn't start when I pressed both power and volume up, then installed the 331-0 version that worked)
- inside TWRP i installed Magisk 20.4
- The phone restarted but never reach the system. It hangs for sometime on android screen then restarts again and then brings me again to TWRP
I spent quiet sometimes reading online solutions but nothing worked for me...
I tried installing Magisk uninstaller.zip nothing changed. tried wiping cache. Tried installing magisk 20 and 20.3
some solutions recommended installing Magisk 19 0r 17 but they both ended up with error for me.
Please help. I'm on Android 10 with MIUI 11

Never had any problems with magisk What TWRP version have you used?
The steps are the same:
-Unlocked phone.
-TWRP.
-Flash magisk zip (you can install magisk manager, then download latest official magisk zip from it and then flash downloaded zip from TWRP).
-reboot.
Anyway you can fix your system by:
-wipe cache/dalvik.
-FORMAT data (with yes).
I don't think you need this 2 first steps for flashing fastboot ROM but it won't hurt.
-Flash official fastboot ROM in fastboot mod, using mi flash tool or included batch/bash scripts (don't lock your device if you don't want to, choose the right option when you flash, with or without "lock").
Mi 9 Fastboot V11.0.5.0.QFAMIXM Global
Mi 9 Fastboot V11.0.8.0.QFAEUXM EEA
You will loose all your data, apps and settings.

Thanks for your help mate...
I'm using this TWRP version..
----//dl.twrp.me/cepheus/
Strangely enough, my phone started after flashing Magisk-uninstaller-20191011.zip I'm sure i tried this before and it doesn't work.
Anyway, all my app and data are gone. I still want to root though, can you help me? what version of TWRP and Magisk i should use?

F.Ashour said:
Thanks for your help mate...
I'm using this TWRP version..
----//dl.twrp.me/cepheus/
Strangely enough, my phone started after flashing Magisk-uninstaller-20191011.zip I'm sure i tried this before and it doesn't work.
Anyway, all my app and data are gone. I still want to root though, can you help me? what version of TWRP and Magisk i should use?
Click to expand...
Click to collapse
Use twrp-3.3.1-62-cepheus-mauronofrio.img.
Magisk-v20.4.zip

antonio52 said:
Use twrp-3.3.1-62-cepheus-mauronofrio.img.
Magisk-v20.4.zip
Click to expand...
Click to collapse
Thanks for your time mate...
I tried this twrp and magisk your mentioned. same issue. boots back to twrp never to system. Any solutions?

F.Ashour said:
Thanks for your time mate...
I tried this twrp and magisk your mentioned. same issue. boots back to twrp never to system. Any solutions?
Click to expand...
Click to collapse
I would try flash latest fastboot ROM as i said before it will reflash almost everything And then flash magisk by installing magisk manager and download latest magisk zip through it and flash it with twrp-3.3.1-62-cepheus-mauronofrio TWRP
Sometimes first flash of TWRP don't work, just flash it ones more by fastboot flash twrp twrp-3.3.1-62-cepheus-mauronofrio.img from your pc.