I have problems with safetynet in Magisk manger
Wen I install (Riru core) and EdeXposed to bypass it the Phone keep crashing and restart
Related
I have tried to bypass SafetyNet with my F3113 using the guide to root and the "How to install Magisk" but the creator (rrvuhpg) mentioned something about having the internal memory encrypted and i tried but without luck.
So i decided to open a thread if anyone has a clue to do it or have succeeded bypassing SafetyNet with Magisk´s Root.
I will paste my last experience:
Try to encrypt phone right away (Rooted with Magisk)
It freezes at logo after reboot.
Searched Google and found it hangs at Logo when rooted.
Learned to Hard Shutdown with vol+ & Power.
Unrooted, flashed boot.img, rebooted to system.
Start encryption again, ends successfully.
Rebooted to TWRP and flashed Magisk 12, then rebooted
Opened Magisk manager, Magisk is installed but root permissions not present, still fails at basic integrity &CTS.
Rebooted to TWRP, uninstalled Magisk 12, rebooted and installing Magisk 11.6
Root present, encrypted internal memory, but fails at Basic Integity and CTS.
This is my Newest experience:
Unlocked Bootloader
Flashed with 0.9.23.2 Flashtool 33.2.A.4.70 Stock Firmware
Booting to system, executing SafetyNet test
Test Passes
Flashed boot & recovery from root guide
Booted to system & executing SafetyNet test
Test fails
Installing Magisk in TWRP anyway
Keeps failing SafetyNet
That is how i did but failed any help is apreciated. Thanks.
That's the Google OTA / DM verity reset kicking in when it detects modification.. The next roadblock is Sony RIC
Problems about safetynet checks is related to the way that Google use to check it and the updates of Magisk to bypass it. Generally it works after a new Magisk update until Google update the safetynet test again.
So i know i'm dump , I installed (ABB &Fastboot_For_Android_NDK-1.0.36) Module From Magisk, now it keeps rebooting into TWRP, IS THERE any way to reboot normally without loosing any data.
after updating OS to 10.3.5 i cant boot after installing Magisk 20.4
i hade to uninstall or not installing Magisk to be abele to boot
any help ?
i guess uninstalling should fix
I'm having same problem.
Both magisk 20.3 and 20.4 don't work for me.
The canary build doesn't work either.
I had a somewhat similar issue.
I used Oxygenupdater in 'automatic mode' and it flashed 10.3.5 but lost root.
So I did fastboot with TWRP 3.2 (the same with which I initially rooted) which did not work. I got Qualcomm Crashdump error Ugh.
Then I downloaded TWRP 3.4.0.3 (latest version) and that worked and flashed this TWRP and then Magisk and so I got root back.
So NEVER use Oxygenupdater in Automatic mode, even when you specify you are rooted.
For TO: try latest TWRP and latest Magisk, and more importantly, the latest ADB and Fastboot tools ! And use original USB cables.
I've tried latest TWRP and magisk. Still same problem, I'm stuck at bootloop
Edit :
Turns out one of the magisk module was causing the bootloop. After removing modules folder in /data/adb the bootloop was fixed
WHello colleagues, I have a question how to solve the bootlop problem that I recently caught by installing the module android faker which caused the loops the phone kept turning on and off and on over and over again Factory reset helped but the question is if there is any other option besides the reset I have twrp installed, you can use twrp to remove this module or other module causing the problem so as not to do a reset of the entire phone
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com
it will definitely be useful only in the case of the magisk module But how to remove the module LsPosed ?
After updating magisk and restarting the phone, the phone goes into bootloop. No update method works... inatall .apk, twrp, directly from the app.
Does anyone have a way to update correctly?
Lineage 18.1
Magisk 23.0