Hi, I'm having k20 pro with miui 12.0.3 android 10. Safetynet fix was success before 13th January 2021. But after that google updated something and safetynet start failing.
Now, I'm dilemma which safetynet fix version should i flash? v1.0.2 or v1.1.1?
JimzFreebies said:
Hi, I'm having k20 pro with miui 12.0.3 android 10. Safetynet fix was success before 13th January 2021. But after that google updated something and safetynet start failing.
Now, I'm dilemma which safetynet fix version should i flash? v1.0.2 or v1.1.1?
Click to expand...
Click to collapse
Try one and then another (uninstall first, install second) - what does it cost (five minures)
zgfg said:
Try one and then another (uninstall first, install second) - what does it cost (five minures)
Click to expand...
Click to collapse
But if my phone goes in bootloop after flashing it, then how to fix it? I don't want to lose my data.
JimzFreebies said:
But if my phone goes in bootloop after flashing it, then how to fix it? I don't want to lose my data.
Click to expand...
Click to collapse
It should not go to bootloop.
Even if it goes, there are couple of ways how to repair bootloop bcs of an errant module, without factory reset - from Magisk go to Github, scroll, open and read Magisk Wiki.
Easist, if you have TWRP, put a "disable" or "remove" (without quotes) empty file to /data/adb/modules/safetynet and reboot - Magisk will disable or uninstall that module.
Or, by booting to Android Safe mode and then rebooting to Android normal mode - all modules will be disabled.
There is also adb command to uninstall all Magisk modules while booting.
All documented in Wiki
It fully applies to the systemless modules (those that use Magisk systemless dynamic mounting instead of hard changing the system partitions) - that modules, when disabled or uninstalled (and rebooted), leave no changes on the system.
SafetyNet-fix is a proper systemless module
Related
Hello,
I'm using magisk 16.0, i get these bugs on Mi A1 stock rom 8.1.0. ROM that i'm using is this https://forum.xda-developers.com/showpost.php?p=76813554&postcount=340
1. Some module not updated on phone reboot. On magisk it still show "module will be updated on nex phone reboot", even i already reboot phone.
2. Phone sometimes won't boot into system, i need to force press & hold power button.
3. Magisk sometimes gone after phone reboot. When i open magisk app, it show me to install magisk even i already install it via twrp
Updated to magisk 16.4 but still not solved
Cc @topjohnwu
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Click to expand...
Click to collapse
I uninstall magisk and reinstal magisk v16. Then updated to v16.4, install all modules and it solved
Attached log for #2 & #3 problem
#2 I can't say much about, don't know what that could be...
#3 Is under some serious investigation at the moment.
Any news?
Title is self explanatory. Running stock pie. I'm tired let me know if additional info is needed. Not much to add.
billard412 said:
Title is self explanatory. Running stock pie. I'm tired let me know if additional info is needed. Not much to add.
Click to expand...
Click to collapse
Magisk 19 should fix Safetynet issues. If not, use Safetynet patch Magisk module
billard412 said:
Title is self explanatory. Running stock pie. I'm tired let me know if additional info is needed. Not much to add.
Click to expand...
Click to collapse
I can confirm that on my Pixel with newest android, and on my wife's moto g6, that magisk is fully working. both have pie now. both pass safetynet just fine.
HueyT said:
Magisk 19 should fix Safetynet issues. If not, use Safetynet patch Magisk module
Click to expand...
Click to collapse
tried everything. Was running magisk 19 when this occurred. Tried multiple versions of magisk and MM. Tried uninstalling and reinstalling. Tried the safetynet fix. Tried reinstalling the OS and other important partitions with fastboot (everything except bootloaders and a data wipe). And not only did I not fix the safetynet issue I'm stuck with no root at all now (magisk is not installed). This is crazy.
billard412 said:
tried everything. Was running magisk 19 when this occurred. Tried multiple versions of magisk and MM. Tried uninstalling and reinstalling. Tried the safetynet fix. Tried reinstalling the OS and other important partitions with fastboot (everything except bootloaders and a data wipe). And not only did I not fix the safetynet issue I'm stuck with no root at all now (magisk is not installed). This is crazy.
Click to expand...
Click to collapse
Have you tried rooting/magisk the old way? By flashing the no verity boot.img? I posted one a page back or so for the newest pie build. Works great from what I can see.
If it were me, and this is assuming you havent already tried this. I would reflash back to stock and make sure to erase userdata in the process. Then flash twrp and the no verity boot.img. Format data and do a factory reset. When that is done go back into twrp and flash magisk. That has worked fine for me on xt1925-6 variant. I actually just the other day followed the old root instructions and they worked fine for pie as well.
I should mention that to flash the image I extract it into the adb/fastboot dir and run the flash_all.bat in elevated CMD window. I do let it do everything including wipe userdata. Not sure if thats important. But it sounded like you were excluding some of the flashing in your process.
i run china k20 pro on indian miui 11.01.0
i installed twrp -21 version
installing magisk 20 provides root access however magisk manager asks to something which results in bootloop to recovery
ignoring that request, the module i wanted to install [energized ] asks for updating to magisk 20.1 which also leads to bootloop to recovery.
is there anything to do ? or just wait for magisk 20.2 to be released and then try it
p.s installing magisk was the only way to prevent redmi recovery from overwriting twrp, i don't know if this has any importance
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
yeah i used magisk uninstaller to make the phone work normally
Glad it worked . Are u able to install magisk again ?
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
Dont install Viper4android via magisk. Just download the package and install in via TWRP. Use this guide
I have this exact problem right now but even with other versions of magisk, I encounter the same issue. Any suggestions?
Same problem here with magisk I guess it is a compatibly issue with MIUI 11
Yep, it's a MIUI11 issue and the reason I haven't shifted over to it. I suspect whatever release of magisk is in the pipeline will fix it provided it's been reported.
In the meanwhile I've read 19.4 works; you could try the canary builds if that seems to old for your liking... just be careful.
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
winesh said:
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
Click to expand...
Click to collapse
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
AvgZing said:
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
Click to expand...
Click to collapse
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
droident said:
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
Click to expand...
Click to collapse
Other than standard app compatibility issues, I haven't heard of any major MIUI11 bugs, which is fantastic to hear.
I have tried all sorts. MI9T MIUI 11.0.1.0 and magisk just causes recovery bootloop . Gonna try magisk 19.4 if thats a thing mentioned in a previous reply
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
I got the same problem on my k20 pro (with MIUI EU).I try driffent ways provided by magisk official but no one works.I have to flash the system. It's not a good idea for intalling V4A on this phone
XedosMD said:
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
Click to expand...
Click to collapse
Does your phone remain encrypted after you do these steps? I doubt...
For some reasons, I wanna keep my phone encrypted.
I am using k20 pro and i got the notification saying 'update available' even though my device is rooted. My actual concern here is will my root privilege and overclocking of cpu be discarded if I install it?
Current MIUI version : 10.3.5.0
Update version : 12.0.6.0
akash2134 said:
I am using k20 pro and i got the notification saying 'update available' even though my device is rooted. My actual concern here is will my root privilege and overclocking of cpu be discarded if I install it?
Current MIUI version : 10.3.5.0
Update version : 12.0.6.0
Click to expand...
Click to collapse
Boot will be overwrited, hence you will loose Magisk and you will have to install again
However, for OTA, you must have stock recovery, not TWRP
Btw, before upgrading, disable all your modules in Magisk - otherwise, when you install Magisk upin the OTA, it will try to initialize all your previous modules (unless you do Factory reset - modules are in /data/adb and they will not be affected by OTA), and your modules for older MIUI/Android (overclicking and so) would likely cause bootloop on the new MIUI/Android
zgfg said:
Boot will be overwrited, hence you will loose Magisk and you will have to install again
However, for OTA, you must have stock recovery, not TWRP
Btw, before upgrading, disable all your modules in Magisk - otherwise, when you install Magisk upin the OTA, it will try to initialize all your previous modules (unless you do Factory reset - modules are in /data/adb and they will not be affected by OTA), and your modules for older MIUI/Android (overclicking and so) would likely cause bootloop on the new MIUI/Android
Click to expand...
Click to collapse
thanks a lot..
Hi, currently my 9t pro has version 12.0.5 (Android 10).
I have root with magisk 25.2 and the twrp version is 3.5.2.9.0 (I point out that, every time I enter recovery, it asks me for the screen unlock pin, without which I cannot access).
I would like to upgrade to version 12.5.2.0 (Android 11).
Do I just boot into twrp, insert the lock screen pin, install the above update, wipe cache and dalvik, install the magisk zip and reboot?
Or am I obliged to update twrp when changing the Android version? The latest version of twrp released for my device seems to me to be 3.6.2.9.0
A thousand thanks
bricca said:
Hi, currently my 9t pro has version 12.0.5 (Android 10).
I have root with magisk 25.2 and the twrp version is 3.5.2.9.0 (I point out that, every time I enter recovery, it asks me for the screen unlock pin, without which I cannot access).
I would like to upgrade to version 12.5.2.0 (Android 11).
Do I just boot into twrp, insert the lock screen pin, install the above update, wipe cache and dalvik, install the magisk zip and reboot?
Or am I obliged to update twrp when changing the Android version? The latest version of twrp released for my device seems to me to be 3.6.2.9.0
A thousand thanks
Click to expand...
Click to collapse
TWRP v3.6.2 should be ok with A10.
On the other side, A11 (AFAIK) will not work with v3.5.2.
Hence better update TWRP
The rest should work the way you descried, just make sure that you upgrade from Global to Global (or EEA to EEA, etc) - ie, not from Global to EEA or so (that would require flashing the Fastboot ROM)
You can also wipe from TWRP:
/data/system/package_cache
PS:
Disable/uninstall Smali Patcher or similar Magisk modules that were specific for the old ROM - to avoid bootloop upon upgrading the ROM and flashing Magisk (if you do not uninstall Magisk, all modules and everything will be back upon your upgrade)
zgfg said:
TWRP v3.6.2 should be ok with A10.
On the other side, A11 (AFAIK) will not work with v3.5.2.
Hence better update TWRP
The rest should work the way you descried, just make sure that you upgrade from Global to Global (or EEA to EEA, etc) - ie, not from Global to EEA or so (that would require flashing the Fastboot ROM)
You can also wipe from TWRP:
/data/system/package_cache
PS:
Disable/uninstall Smali Patcher or similar Magisk modules that were specific for the old ROM - to avoid bootloop upon upgrading the ROM and flashing Magisk (if you do not uninstall Magisk, all modules and everything will be back upon your upgrade)
Click to expand...
Click to collapse
Would you please explain to me how I can upgrade twrp from 3.5.2 to 3.6.2? I also have the official twrp app.
As for the magisk modules these are the ones I currently have installed. Do you think it is better to uninstall magisk directly before entering twrp and flash the new rom and magisk zip?
bricca said:
Would you please explain to me how I can upgrade twrp from 3.5.2 to 3.6.2? I also have the official twrp app.
As for the magisk modules these are the ones I currently have installed. Do you think it is better to uninstall magisk directly before entering twrp and flash the new rom and magisk zip?
Click to expand...
Click to collapse
As usual - TWRP.me, download, find your device, download img and flash to Recovery (you can do from current TWRP or from Fastboot)
Maybe you better disable that liboencrypto module
Or you can try with but study Magisk GitHub Wiki, how to fix the bootloop caused by incompatible modules
zgfg said:
As usual - TWRP.me, download, find your device, download img and flash to Recovery (you can do from current TWRP or from Fastboot)
Maybe you better disable that liboencrypto module
Or you can try with but study Magisk GitHub Wiki, how to fix the bootloop caused by incompatible modules
Click to expand...
Click to collapse
The twrp update flash so I can do it directly from the application?
Instead, to avoid a possible bootloop just uninstall that module? Do all the others give problems?
Thank you.
bricca said:
The twrp update flash so I can do it directly from the application?
Instead, to avoid a possible bootloop just uninstall that module? Do all the others give problems?
Thank you.
Click to expand...
Click to collapse
I never use the TWRP app. Read instructions from TWRP.me
You can uninstall modules. But, plz read and LEARN (it's more useful for the future how to dožisable modules from TWRP - docs I pointed you in the previous post)