I have a Xiaomi Mi 9T (MIUI Global 10.3.9) rooted with Magisk 19.3.
Two days ago, when I woke up and turned on the phone, it no longer had root. I only flashed magisk again.
Yesterday it happened again, but without any reboot, and I found a file in my Downloads folder called "log_antiroot.txt".
Is it possible that something is removing my root?
If so, how can I detect it and remove it?
Magisk 19.3
Related
Hi guys,
so few days ago i tried to root my new honor 9 , i followed this guide https://android.gadgethacks.com/how-to/magisk-101-install-magisk-root-with-twrp-0179668/ , unlocked bootloader, installed twrp and stuff. But It seems like i've missed some part, I don't know where tho because when I try to flash magisk then boot my phone and install the apk i have the Fix SafetyNet 'CTS Profile' & 'Basic Integrity' Errors with Magisk...I then read this https://android.gadgethacks.com/how-to/magisk-101-fix-safetynet-cts-profile-mismatch-errors-0178047/ but none of the solution here worked (most of them are related to supersu which i never installed to my phone so). Also magisk doesnt seem to installed properly, since i always have the "install button". I tried to redo the last step (uninstall magisk then reinstall it) and some factory reset but still the same problem.
What should I do please? I ask here because I don't want to mess up anymore.
Also, I even tried to reinstall the stock rom with this guide https://forum.xda-developers.com/showpost.php?p=73334439&postcount=1 but as soon asI open the bat file, it disapear. So i don't know what to do anymore...
Thank you.
TWRP 3.1.1-1
STF-L09C432B150
Just some quick instructions that helped me with issues with Magisk 19 most recently.
Problem: you updated the ROM, flashed Magisk and now the phone always reboots to recovery within a few seconds of unlocking it.
Solution:
- Flash Magisk 17.3. this should get you back to a stable system with root, but without working modules.
- Install Magisk Manager 6 to use with 17.3
- Use Root Explorer and go to /data/adb
- Delete all files called Magisk and the modules folder
Reboot and reflash Magisk 19
- update Magisk Manager
I almost gave up and would have started from scratch. I don't know why Magisk 19 corrupted after the update but even after deleting only the modules folder it wouldn't work. The phone finally worked normal again after just deleting all things Magisk in the /data/adb folder.
Unfortunately TWRP doesn't mount the encrypted /data partition yet so you can't use Magisk Recovery or Magisk uninstaller from TWRP. I found this workaround finally fixed my issues and I hope it is helpful to someone else on the forum.
Best of luck!
mrchrister said:
Just some quick instructions that helped me with issues with Magisk 19 most recently.
Problem: you updated the ROM, flashed Magisk and now the phone always reboots to recovery within a few seconds of unlocking it.
Solution:
- Flash Magisk 17.3. this should get you back to a stable system with root, but without working modules.
- Install Magisk Manager 6 to use with 17.3
- Use Root Explorer and go to /data/adb
- Delete all files called Magisk and the modules folder
Reboot and reflash Magisk 19
- update Magisk Manager
I almost gave up and would have started from scratch. I don't know why Magisk 19 corrupted after the update but even after deleting only the modules folder it wouldn't work. The phone finally worked normal again after just deleting all things Magisk in the /data/adb folder.
Unfortunately TWRP doesn't mount the encrypted /data partition yet so you can't use Magisk Recovery or Magisk uninstaller from TWRP. I found this workaround finally fixed my issues and I hope it is helpful to someone else on the forum.
Best of luck!
Click to expand...
Click to collapse
Had this issue a while back and ended up starting with a clean install. Nice that you found a fix, should come in handy if I ever face the same problem again...
Hi,
I have similar issue as you but slightly different. Whatever I tried to flash (e.g: twrp (multiple version) or patched magisk boot img). It always reboot to mi official recovery.
Do you face this issue before and how you fixed it?
Info:
Mi 9 EEA rom
cutesniper22 said:
Hi,
I have similar issue as you but slightly different. Whatever I tried to flash (e.g: twrp (multiple version) or patched magisk boot img). It always reboot to mi official recovery.
Do you face this issue before and how you fixed it?
Info:
Mi 9 EEA rom
Click to expand...
Click to collapse
Take a look, if your bootloader is unlock!
Maybe it is relocked.
I had the same issue today, what I did is quickly opened up Magisk manager, and clicked uninstall. It still rebooted in the middle of the process, but after I flashed 19.1, it never rebooted again!
bombername said:
Take a look, if your bootloader is unlock!
Maybe it is relocked.
Click to expand...
Click to collapse
No, I can confirmed it's unlocked because I'm able to flash global rom into mi 9 china phone.
I just updated my Redmi Note 3 (mido) to MIUI 11 (global version).
I unlocked the bootloader officially.
- from the Developer option mentioned "Unlocked"
- during bootup, there's "Unlocked" text.
so, I flash TWRP in with ADB (fastboot flash recovery),
then, I flashed Magisk in recovery, with LazyFlasher (in view of I got stuck in bootloop afterwards).
the issues here is,
no SuperUser access - no permission asked when I open BusyBox/Root Checker app.
there's a Magisk icon on the homescreen, no issues opening it.
passed SafetlyNet.
both Magisk Manager, and Magisk ticked green.
any workaround for this?
got it sorted out.
after reading from "https://forum.xda-developers.com/redmi-note-4/help/how-to-upgrade-miui-10-rooted-to-miui-11-t4006971",
noticed there're issues with Magisk 20.1
I downgraded to MIUI 10 (but using the Xiaomi.EU version), used Magisk 20.1, also no root.
so, I used Magisk 20.0, and it works!
:victory:
11.0.3.0 miui global rom installed 2 different Xiaomi Mi 9 phones (one is M1902F1G, other is M1902F1A)
Following procedures were applied to the phone M1902F1G.
1. TWRP is installed M1902F1G phone. (Worked)
2. Magisk 20.3 was installed via TWRP (Worked)
3. Magisk Manager is properly installed on the phone. Working FINE
Following procedures were applied to the phone M1902F1A.
1. TWRP is installed M1902F1A phone. (Worked)
2. Magisk 20.3 has been installed via TWRP (NOT Worked) BOOTLOOP started and TWRP bootloader opened again.
3. After Phone was flashed Magisk Manager Uninstaller, the phone has been working properly.
I have tried all 20.x, 19.x and 18.x versions of Magisk. There was no improvement is observed.
Is there anyone who has any idea to solve the problem?
nukecore said:
11.0.3.0 miui global rom installed 2 different Xiaomi Mi 9 phones (one is M1902F1G, other is M1902F1A)
Following procedures were applied to the phone M1902F1G.
1. TWRP is installed M1902F1G phone. (Worked)
2. Magisk 20.3 was installed via TWRP (Worked)
3. Magisk Manager is properly installed on the phone. Working FINE
Following procedures were applied to the phone M1902F1A.
1. TWRP is installed M1902F1A phone. (Worked)
2. Magisk 20.3 has been installed via TWRP (NOT Worked) BOOTLOOP started and TWRP bootloader opened again.
3. After Phone was flashed Magisk Manager Uninstaller, the phone has been working properly.
I have tried all 20.x, 19.x and 18.x versions of Magisk. There was no improvement is observed.
Is there anyone who has any idea to solve the problem?
Click to expand...
Click to collapse
You can found the solution by searching google Xiaomi Mi9t Recovery bootloop after magisk install #2492, because XDA does not permit link insertion for new users.
Dear all, I'm using Huawei p20 lite al00C675. I had rooted long back using magisk. And everything was fine. Recently, I tried to unroot for an upgrade, and later rooted back. However after that, my magisk was not giving root prompts. So superuser was getting denied for all, although magisk modules were working.
I had magisk 20.3. In a bid to fix this issue, I tried reinstalling magisk. I uninstalled first and while rebooting, went to twrp, installed magisk 20.4. But that's where the issue happened.
It went into bootloop. So I went to twrp and uninstalled magisk. Now when I booted, it said no boot image. Then I reinstalled magisk 20.3, but now it is stuck at 'This device cannot be trusted' screen. I've tried factory reset via twrp, but no use.
Please help. I don't want to lose this phone. Service centres are closed due to corona lockdown.
Arseon said:
Dear all, I'm using Huawei p20 lite al00C675. I had rooted long back using magisk. And everything was fine. Recently, I tried to unroot for an upgrade, and later rooted back. However after that, my magisk was not giving root prompts. So superuser was getting denied for all, although magisk modules were working.
I had magisk 20.3. In a bid to fix this issue, I tried reinstalling magisk. I uninstalled first and while rebooting, went to twrp, installed magisk 20.4. But that's where the issue happened.
It went into bootloop. So I went to twrp and uninstalled magisk. Now when I booted, it said no boot image. Then I reinstalled magisk 20.3, but now it is stuck at 'This device cannot be trusted' screen. I've tried factory reset via twrp, but no use.
Please help. I don't want to lose this phone. Service centres are closed due to corona lockdown.
Click to expand...
Click to collapse
Hi,
A) try update your phone via eRecovery & Wi-Fi ("download latest ....and recovery") .
B) you can also use Service ROM (dload method & three button combo). This process will erase all your data and will lock your bootloader again!
Service ROM link:
https://androidhost.ru/Ukr
(hope you are running EMUI 9 Follow instructions in file "ReleaseDoc", it can be found after unpacking .zip.
Crossing fingers