Bootloop after flashing Magisk on Global ROM - Redmi K20 / Xiaomi Mi 9T Questions & Answers

Hi, I need your help. I got a K20 from China with China official ROM.
I linked my Xiaomi account, then unlocked bootloader (had to wait 7 days).
I downloaded fastboot Global ROM 10.3.6.0 and installed it via Xiaomi Flash Tool (making sure to not relock bootloader)
Phone rebooted ok, now it shows as MI 9T and have Google Services installed, but Google Pay is not working...
So I want to root with Magisk to pass CTS SafetyNet test.
Downloaded Magisk 19.2
I installed TWRP (from the post in here) , rebooted to TWRP, installed Magisk zip file. No errors given. Wiped Dalvik/Cache.
But when rebooting to system I got a bootloop and phone goes back to TWRP.
I had to install Magisk uninstaller to get phone working again.
Any help on how to get Magisk working on Global ROM flashed via Fastboot ?
Thanks

After install Magisk, do a factory reset and reboot.

Schnedi said:
After install Magisk, do a factory reset and reboot.
Click to expand...
Click to collapse
I will try that, thanks for the suggestion.
Is it safe to remove xiaomi account from the phone before doing factory reset ?
I am asking cause last time after I flashed fastboot ROM first thing I had to do was insert xiaomi account pwd, but I would prefer to have a phone with no account linked to it after a factory reset.
Cheers,

seblog said:
I will try that, thanks for the suggestion.
Is it safe to remove xiaomi account from the phone before doing factory reset ?
I am asking cause last time after I flashed fastboot ROM first thing I had to do was insert xiaomi account pwd, but I would prefer to have a phone with no account linked to it after a factory reset.
Cheers,
Click to expand...
Click to collapse
You can remove it, yes.

Schnedi said:
You can remove it, yes.
Click to expand...
Click to collapse
Thanks a lot!
After a factory reset finally I got it working!
I am a bit concerned cause I have then updated via Recovery ROM to 10.3.7 Global (so global to global) but I lost root !
Should I have done it via TRWP ? Cause I did it via the Updater of MIUI.
I reinstalled Magisk via TWRP but got bootloop again, so I had to factory reset once again !
Is that normal ? What will be the best way to update without loosing everything ?
Cheers

are you able to make google pay working?
For me after installing magisk and formating data, when I open magisk it shows additional setup is required. If I say yes, it reboots and again goes back to revocvery bootloop.

seblog said:
Thanks a lot!
After a factory reset finally I got it working!
I am a bit concerned cause I have then updated via Recovery ROM to 10.3.7 Global (so global to global) but I lost root !
Should I have done it via TRWP ? Cause I did it via the Updater of MIUI.
I reinstalled Magisk via TWRP but got bootloop again, so I had to factory reset once again !
Is that normal ? What will be the best way to update without loosing everything ?
Cheers
Click to expand...
Click to collapse
As far as I know you should never do any updates through MIUI when you have custom recovery. I was on EEA 10.3.7 and flashed twrp and magisk. Then updated to EEA 10.3.12 by wiping data, sys, catch and installing 10.3.12 recovery rom through twrp and then magisk and its working fine

Related

Need help quick...

Hello guys.
Today I did it successfully the root of my Oneplus 5 with magisk. But I have a problem. Even with root hide I can't install netflix. Google Play show me not certified. I allready wipeout everthink remove the root install the stock remove, I allways use the stock rom I still no certified in google.
Someone can help me?
pmsfcruz said:
Hello guys.
Today I did it successfully the root of my Oneplus 5 with magisk. But I have a problem. Even with root hide I can't install netflix. Google Play show me not certified. I allready wipeout everthink remove the root install the stock remove, I allways use the stock rom I still no certified in google.
Someone can help me?
Click to expand...
Click to collapse
I think its shows not certified because you unlocked the bootloader.
Thx for aswer. Yes I allready try to lock back but the phone dont boot again.
pmsfcruz said:
Thx for aswer. Yes I allready try to lock back but the phone dont boot again.
Click to expand...
Click to collapse
Do a data factory reset in recovery and then reboot.
gee2012 said:
Do a data factory reset in recovery and then reboot.
Click to expand...
Click to collapse
Well, that's a bit... drastic, isn't it?
I have my op5 rooted with magisk (latest beta version) and i can download netflix and google play doesn't say "uncertified".
If you got magisk hide working (i.e. safety net check inside magisk manager is all green), just go to settings -> apps -> google play and clear its data!
You shouldn't see "uncertified" anymore in google play and you should be able to download netflix (I am).
Ok. I allready do that many times. So I lock first and then do data factory or after reset i lock bootloader? Sorry my question but I allready try everthink.
You don't need to relock the bootloader in order for Magisk hide to work, in fact it's a very bad idea to relock the bootloader with a custom recovery installed. What you need to do first is wipe everything and start from scratch.
Once you have the latest OOS 4.5.5 and everything working properly, download the latest stable twrp from here and download the latest beta of Magisk from here (version c4377ed) and put it in a folder on your phone from where you usually flash files via TWRP.
Boot into bootloader and flash TWRP then boot into TWRP, from there wipe Dalvik and cache, then flash Magisk and wipe Dalvik and cache one more time then reboot into system. Once you booted up, open Magisk manager and hit the safetyNet check, if you get green checkmarks, you're done. If not, go into settings and see if Magisk hide is activated, if it isn't check it and then do the safetyNet check again. If Magisk hide is activated, then deactivate and reactivate it again and then go back and do the safetyNet check again, and it should be good to go.
I did all those things I told you and as you can see from the pictures I have Netflix working no problem.
HueleSnaiL said:
You don't need to relock the bootloader in order for Magisk hide to work, in fact it's a very bad idea to relock the bootloader with a custom recovery installed. What you need to do first is wipe everything and start from scratch.
Once you have the latest OOS 4.5.5 and everything working properly, download the latest stable twrp from here and download the latest beta of Magisk from here (version c4377ed) and put it in a folder on your phone from where you usually flash files via TWRP.
Boot into bootloader and flash TWRP then boot into TWRP, from there wipe Dalvik and cache, then flash Magisk and wipe Dalvik and cache one more time then reboot into system. Once you booted up, open Magisk manager and hit the safetyNet check, if you get green checkmarks, you're done. If not, go into settings and see if Magisk hide is activated, if it isn't check it and then do the safetyNet check again. If Magisk hide is activated, then deactivate and reactivate it again and then go back and do the safetyNet check again, and it should be good to go.
I did all those things I told you and as you can see from the pictures I have Netflix working no problem.
Click to expand...
Click to collapse
Thank you very much for this post, was very helpful throughout the whole process. :good:

Problems updating from 5.1.7 to 9

Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
Hi, I got Pie to install with TWRP_3.2.3-Pie_siankatabg_OP5 on my device.
Go to this link:
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
And follow my post on the part where it says:
" Notes for the Pie update: "
Let us know if those steps work for you. The firmware is linked to on there, pre-modified. Try flashing that pre-modified zip and see if your device boots.
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
strongst said:
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
Click to expand...
Click to collapse
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Maybe try backing your device up, and then locking the bootloader. Try updating with stock recovery on a locked bootloader. If that works, you can then unlock the bootloader and copy your data back
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
strongst said:
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
Click to expand...
Click to collapse
OK, I understand now - if I use an older TWRP, or the siankatabg version, it works fine. I can then flash the Pie ROM, however it still won't boot - I get the oneplus logo, then it just reboots. However having done the Pie flash, I can then flash the more recent TWRPs (codeworx or Bluespark), and can now get into recovery fine. However Pie still won't boot - I've even tried re-flashing the Pie ROM from within the newer TWRPs, but the result is the same - it gets to the oneplus logo, then reboots. At this stage I guess wiping system/vendor/data is the only way forwards?
*Edit* - OK, so wiping everything fixed the issue, I'm now on Pie. Flashing Magisk didn't work when flashing the ROM, but I'll try again once it's finished downloading all my apps etc.

Phone stuck at Decryption unsuccessful :crying:

I am stuck at encryption failed when I flash stock oreo rom. I tried formatting data using twrp and flashed no encryption file as well but nothing works.:crying::crying::crying:
I just want to use the stock oreo rom again with root.
Pls help:crying:
Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.
jl10101 said:
Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.
Click to expand...
Click to collapse
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now
Deadmeat03 said:
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now
Click to expand...
Click to collapse
Odd. If I had to guess anything, it would be that not all the partitions were flashed when going from Nougat to Oreo.
I once flash a Nougat ROM from an Oreo ROM and I had the same encryption issue and lost everything.
That was the last time I would trust myself again and not do a backup.
Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...
Prowler_gr said:
Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...
Click to expand...
Click to collapse
I tried that as well. With stock recovery is says data is corrupted and doesn't do anything. I think it might be a problem with patched lg up because when i use normal lg up to flash oreo it works. But I cant root then.
I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.
In the same boat as OP
scottyrick said:
I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.
Click to expand...
Click to collapse
Hi
Looking for a way to keep TWRP and root ... any help appreciated
I've got a US996 with the same issue as the op. I have the latest TWRP 3.3.1-0. The phone was working fine until I upgraded twrp but I might have done a mistake resetting phone outside of twrp.
I can still get back into twrp but I haven't been able to install zip files without getting that decryption unsuccessful message when booting to system.
When getting back into TWRP using hardware buttons sometimes there is a prompt asking "keep system read only?" which I never chose and swipe to allow modification. I think this happens after
I pull the battery after getting the decryption unsuccessful message. There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
...but if my phone is a us996 and is still
unlocked, would it matter if I did select it? Wouldn't I be able to reinstall twrp using adb again on a computer after Oreo is reinstalled?
To do Prowler_gr's suggestion which guide do I follow (sounds like I should do the second option)
"Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track... "
1-[GUIDE][UNBRICK] Patch LGUP to unlock features & unbrick V20 (Variant mismatch fix) to use lgup
or this guide
2-Ultimate guide to unbrick LG V20(Only Variants with .KDZ)[No OS Firmware Update Loop]
Thank you for any guidance on this...
There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
Click to expand...
Click to collapse
Don't blame me if this goes wrong but I'm pretty much 100% certain that you mush press the rest button. This has happened to me a few times I'm sure. You won't loose twrp. Whatever resetting goes on in the background I don't think it's an actual Factory Reset.
Edit: Just to be clear you taking about a white screen with I think in dark blue or black text ENCRYPTION UNSUCCESSFUL and something like "reset phone" option directly under it, on the upper half of the screen?
Hi ezzony
Yes you are thinking of the right decryption unsuccessful page. I get it when booting to system
after installing Oreo and magisk 19 and having wiped everything (format data too). I will get the exact wording of it tonight
Thanks!
downgrade twrp i has same prob twrp 3.3.1 gives issues
ghet2rockuu said:
downgrade twrp i has same prob twrp 3.3.1 gives issues
Click to expand...
Click to collapse
Hi ghet2rockuu
I downgraded twrp and that got it working Thank You! see also Phoenix591 thread [Recovery][Unofficial for the moment]TWRP 3.3.1-0 : 2019-05-17 #625
Thank You !

After update to V11.0.4.0.QFJEUXM TWRP no longer available

Hi Guys,
yesterday the new update came out, great.
I of course immediately pulled the zip (source) and installed it with TWRP (source).
So far no problems.
After a while I realized that I no longer had root because the apps stopped working.
When I wanted to boot into the TWRP to reinstall Magisk, I unfortunately found that it was no longer available, but only stock recovery.
Well, I thought to myself and tried to reinstall TWRP (method-twrp-3.3.1-2-davinci-fix), which was fatal, because my cell phone only booted into the Fastboot.
Then I got my cell phone, set up again with the Fastboot method.
Now I'm back to 11.0.4.0 but unfortunately without TWRP and root.
Can someone please describe how I can get TWRP and root again on Android 10?
I am thankful for every help !!!
Same thing happening to me, no matter what I do, stock recovery keeps overwriting TWRP
Oh dear, that doesn't sound good.
I hope there will be a solution to the problem soon.
I don't want to do without TWRP and root.
I wanted to try it according to these instructions "https://miui.blog/redmi-k20/twrp-mi-9t-redmi-k20-vbmeta-mauronofrio/". But don't trust me, I'm afraid that it won't work and I can start all over again.
Flash official TWRP this morning with fastboot commands without problem.
1. reboot in fastboot mode
2. Flash recovery with this command "fastboot flash recovery yourrecovery.img"
3. Reboot in recovery with this command "fastboot boot yourrecovery.img"
Any problems here.
The fact that twrp is lost when flashing official rom (even thought twrp itself) is normal. You just have to reboot into bootloader and flash twrp again and it will be back.
Your problem here is that you are using an old and unofficial twrp build, that has problems on newer roms. Flash official twrp and you'll be fine
houbaba said:
Flash official TWRP this morning with fastboot commands without problem.
1. reboot in fastboot mode
2. Flash recovery with this command "fastboot flash recovery yourrecovery.img"
3. Reboot in recovery with this command "fastboot boot yourrecovery.img"
Any problems here.
Click to expand...
Click to collapse
Can u share the twrp file, im unnable to flash the one i have without causing a bootloop
hounter17 said:
Can u share the twrp file, im unnable to flash the one i have without causing a bootloop
Click to expand...
Click to collapse
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Oh sorry it works? I read somewhere that the original causes also bootloops :good:
Found something on a Russian website.
Обновление TWRP Recovery от LR.Team для устройств на Android 10
Does anyone dare to test this?
Here is the link to the TWRP for our Mi9t
> TWRP-3.3.1-1109-DX (полный комплект для установки) <
Check it out...
I finally got it
I did the following.
"V11.0.4.0.QFJEUXM" flashed in the TWRP and booted into the system, TWRP will be overwritten.
Now flashed TWRP "twrp-3.3.1-0-davinci.img" in Fastboot and booted into Recovery (TWRP).
To be on the safe side, I had the cell phone booted again into the TWRP in the TWRP.
Then I flashed Magisk "Magisk-v20.3.zip".
Booted cell phone into the system and everything works.
frank808 said:
I finally got it
I did the following.
"V11.0.4.0.QFJEUXM" flashed in the TWRP and booted into the system, TWRP will be overwritten.
Now flashed TWRP "twrp-3.3.1-0-davinci.img" in Fastboot and booted into Recovery (TWRP).
To be on the safe side, I had the cell phone booted again into the TWRP in the TWRP.
Then I flashed Magisk "Magisk-v20.3.zip".
Booted cell phone into the system and everything works.
Click to expand...
Click to collapse
Where did you get the twrp file from?
You can use OrangeFox Recovery if you want a TWRP that can survive after flashing MIUI ROMs or updates :
https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899
RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Ok, I am on global 11.0.4.0 (QFJMIXM) and I used this latest twrp-3.3.1-0-davinci.img and I can confirm its working without bootloop.
ShiningScias said:
You can use OrangeFox Recovery if you want a TWRP that can survive after flashing MIUI ROMs or updates :
https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899
Click to expand...
Click to collapse
To install TWRP, is it neccesary to wipe Data (or something else)?
And if Data must be wiped, does it mean that Data will no more be encrypted as originally by MIUI?
I have 11.0.4.0, rooted by Magisk (Magisk installed simply by patching and flashing boot.img, did not need TWRP for, did not wipe Data, etc) and I possibly want to have TWRP but don't want to loose encryption of Data, Widewine L1 and so
zgfg said:
To install TWRP, is it neccesary to wipe Data (or something else)?
And if Data must be wiped, does it mean that Data will no more be encrypted as originally by MIUI?
I have 11.0.4.0, rooted by Magisk (Magisk installed simply by patching and flashing boot.img, did not need TWRP for, did not wipe Data, etc) and I possibly want to have TWRP but don't want to loose encryption of Data, Widewine L1 and so
Click to expand...
Click to collapse
You don't need to wipe anything to install a custom Recovery (like TWRP).
TWRP can handle ROM encryption, you just need to install a correct TWRP, and version, for your current MIUI / Android version.
A custom Recovery doesn't change Widevine level.
And TWRP is useful in case of bootloop (because of an installed Magisk module, by example) or if you want to easily reinstall Magisk after ROM update.
RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Micdu70 said:
You don't need to wipe anything to install a custom Recovery (like TWRP).
TWRP can handle ROM encryption, you just need to install a correct TWRP, and version, for your current MIUI / Android version.
Click to expand...
Click to collapse
Ok thanks, so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Maybe I could test first by
fastboot boot twrp-3.3.1-0-davinci.img
zgfg said:
Ok thanks, so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Yes, it should work.
But I prefer OrangeFox Recovery.
zgfg said:
so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Maybe I could test first by
fastboot boot twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Micdu70 said:
Yes, it should work.
But I prefer OrangeFox Recovery.
Click to expand...
Click to collapse
Something is fishy. IMO, if that official TWRP is really ok for 11.0.4.0, then it should correctly boot by:
fastboot boot twrp-3.3.1-0-davinci.img
But phone rebooted into the dark.
TG, I didn't really flash with, so by long pressing Pow it rebooted to system.
Tried again, no avail
Edit:
Tried the same fastboot boot with
twrp-3.3.1-12-davinci-mauronofrio.img and also OrangeFox-R10.1_1-Stable-davinci.img (obtained by unzipping OrangeFox), but it also reboots to dark and I have to long press Pow to reboot to system
frank808 said:
Hi Guys,
yesterday the new update came out, great.
I of course immediately pulled the zip (source) and installed it with TWRP (source).
So far no problems.
After a while I realized that I no longer had root because the apps stopped working.
When I wanted to boot into the TWRP to reinstall Magisk, I unfortunately found that it was no longer available, but only stock recovery.
Well, I thought to myself and tried to reinstall TWRP (method-twrp-3.3.1-2-davinci-fix), which was fatal, because my cell phone only booted into the Fastboot.
Then I got my cell phone, set up again with the Fastboot method.
Now I'm back to 11.0.4.0 but unfortunately without TWRP and root.
Can someone please describe how I can get TWRP and root again on Android 10?
I am thankful for every help !!!
Click to expand...
Click to collapse
You can install twrp by All In One tool
You can find its thread here itself
I took the official TWRP. " Link "
Flashed in fastboat and then booted the phone with a key combination in TWRP.
With the Fastboot command it didn't work for me either, the cell phone remained black ...

OnePlus 6t Wifi Issue on custom roms

Okay so I've tried Pixel experience, lineage os , omni rom treskmod and couple of other custom android 10 roms, all stable and official and also updated ones, the wifi just simply doesn't work, wifi hotspot won't turn on either. I've tried every solution on the internet. I've even factory reset my phone using msm download tool and no luck(did this countless times).
I'm back in OOS 10.3.2 and there's no issue apparently.
At one point , i flashed a custom rom and the wifi didn't work, so I flashed OOS in the two slots and checked , the wifi works in OOS apparently, and never in custom roms.
Has anyone got this issue before and knows a solution?
How is your installation procedure?
onliner said:
How is your installation procedure?
Click to expand...
Click to collapse
I flash OOS and twrp on both slots, reboot recovery,
And then flash the rom and twrp, reboot recovery,then format data and factory reset, reboot recovery, if needed for some gapps, then reboot system
ivanthomas said:
I flash OOS and twrp on both slots, reboot recovery,
And then flash the rom and twrp, reboot recovery,then format data and factory reset, reboot recovery, if needed for some gapps, then reboot system
Click to expand...
Click to collapse
That's a lot of unnecessary steps. OOS on both slots, reboot to bootloader, boot twrp, format data and flash the custom rom, reboot bootloader, boot twrp and flash gapps, don't install twrp permanently if you are not going to install Magisk.
onliner said:
That's a lot of unnecessary steps. OOS on both slots, reboot to bootloader, boot twrp, format data and flash the custom rom, reboot bootloader, boot twrp and flash gapps, don't install twrp permanently if you are not going to install Magisk.
Click to expand...
Click to collapse
I need magisk too, I usually permanently install twrp
Also you think it's the way I'm installing at fault here? Or the rom? Or is it something wrong with my device?
ivanthomas said:
it's the way I'm installing at fault here?
Click to expand...
Click to collapse
This.
I always install roms with the procedure i said above and have never had any problems.
onliner said:
This.
I always install roms with the procedure i said above and have never had any problems.
Click to expand...
Click to collapse
Alright so got one doubt, I used OOS 10.3.2 to flash, should it be oos 10.0 only?
Thought that didn't make a difference.
I am also facing the same issue. Were you able to find any solution ?
So I found out treskmod omni rom and Paranoid android quartz 2 work perfectly , try those out, it still doesn't solve the problem in the other roms though. So not exactly a solution.

Categories

Resources