Develop Bugs

Magisk problems in Moto Z2 Play

I can not install magisk modules and my device constantly loses its root without a reason.

I have the same problem. Magisk seems to be still buggy. But at least I haven't seen the "losing root" issue after disabling "Magisk Hide" in the settings.

Thanks
romhippo.com said:
I have the same problem. Magisk seems to be still buggy. But at least I haven't seen the "losing root" issue after disabling "Magisk Hide" in the settings.
Click to expand...
Click to collapse
Thanks Romhippo.com for responding!
If anyone knows more about it, I'd be happy to know.

Had that issue on a One Plus 3T. Finally updated Magisk in the app and it fixed itself. Was really flakey on root.

larsdennert said:
Had that issue on a One Plus 3T. Finally updated Magisk in the app and it fixed itself. Was really flakey on root.
Click to expand...
Click to collapse
Cool! I hope they also correct here.

Loosing root + possible fix
I was getting the same problem, magisk loosing root and phone getting encryptation problems... making me to format my phone twice.
After i noticed the problem was with magisk 13.3, so i tried to install 13.6 beta but no success, it give me error "Unable to detect boot image" during instalation.
Then i decided to mod magisk zip file (updater_script) , installed then and jrummy busybox (I think oldversions are conflicting with magiskSu)... and now i got 2 days without problem.
Magisk 13.6 beta modded
https://drive.google.com/open?id=0B1UKyTc_LCSOc09UMFhHNVFTd1U

raphamfc said:
I was getting the same problem, magisk loosing root and phone getting encryptation problems... making me to format my phone twice.
After i noticed the problem was with magisk 13.3, so i tried to install 13.6 beta but no success, it give me error "Unable to detect boot image" during instalation.
Then i decided to mod magisk zip file (updater_script) , installed then and jrummy busybox (I think oldversions are conflicting with magiskSu)... and now i got 2 days without problem.
Magisk 13.6 beta modded
https://drive.google.com/open?id=0B1UKyTc_LCSOc09UMFhHNVFTd1U
Click to expand...
Click to collapse
LoL Many thanks for your help. It's all normal here.

I'm going to agree on conflict issues being the likely cause. Between custom roms having su built in like Resurrection remix, SuperSU and standalone magisk, there are plenty of possibilities for messed up boot images.

In fact, 2 things bother me the most.
1. I can not install magisk modules
2. The magisk does not pass SafetyNet.
I do not know if that happens to you.

My Z2 is a verizon one so this is where my advice stops on that phone. I've Magisk on the 3T and pixel only

anyone have a guide to install Magisk?

Refer the following threads completely. Junior answered all my querries. His Moto Brazil blog has systematic and structured guides as well. Very well done.
https://forum.xda-developers.com/z2-play/help/indian-stock-firmware-xt1710-10-t3711423
http://motozbrasil.blogspot.in/search/label/TutorialZ2Play

DP4 with Magisk = System UI strange beheavior

** Resolved: Please see post #9 below by @henderjr for a solution and don't forget to thank @henderjr!
--------------------------
Just downloaded DP4 and dirty flashed from DP3 (remove -w), everything looks normal....
Then I install Magisk 16.4 with TWRP (boot only), when I go back to system, System UI just crash continuously...
Also, even with 89% battery, the system still complain "battery low" (with message say the battery will last until tomorrow morning 7 o'clock, which is 19 hrs later! ha ha !)
When swipe down the notification area, the upper part of screen become dark... looks like UI glitch..
Anyone have same issue like this?
(Maybe I should factory reset, but I see somewhere that contact will not sync... So now stuck in the middle...)

Same issues here. And with random reboots also.

That's weird.
I clean flashed from Android 8 and haven't had any SystemUI issues.
I also use Substratum and haven't had any issues.
I've only been running it for a couple of hours, I'll report back if anything changes.
Edit: I'd suggest a clean flash, though. Stuff seems REALLY bugged lol.

For me started failing after a reboot. The first moment I got into the system, UI was broken
Tried factory reset also. Same problem after reboot

Same here (((

It seems we really need update of Magisk. @topjohnwu while your country need you, we also need you!

Even before flashing magsik CTS profile is false.
Sent from my Pixel 2 XL using XDA Labs

Has anyone confirmed this happens only after flashing Magisk? I'm currently trying to reproduce all the other steps (restore apps, config, etc) just to be sure who is guilty
Edit: well, I can't reproduce it. So everything seems to be pointing Magisk as the guilty

lssong99 said:
Just downloaded DP4 and dirty flashed from DP3 (remove -w), everything looks normal....
Then I install Magisk 16.4 with TWRP (boot only), when I go back to system, System UI just crash continuously...
Also, even with 89% battery, the system still complain "battery low" (with message say the battery will last until tomorrow morning 7 o'clock, which is 19 hrs later! ha ha !)
When swipe down the notification area, the upper part of screen become dark... looks like UI glitch..
Anyone have same issue like this?
(Maybe I should factory reset, but I see somewhere that contact will not sync... So now stuck in the middle...)
Click to expand...
Click to collapse
I had the same exact behavior yesterday. If you're still running the magisk module "[APP] 18. Feb ◦ Edge Sense Plus 1.22.0 ◦ Customize Active Edge on your Pixel 2 XL" it will cause SystemUI to behave strange and show the battery saver icon. Disable the module until it gets updated.

Mine was working normally on DP4, Substratum, Magisk...only had the ctsProfile false problems others are having.
Often upon flashing, especially dirty flashing any Rom, when opening Magisk it would force close. Found by just reinstalling the Magisk.apk it would work again.
But, since Google Pay is failing with the ctsprofile false problem, I've rolled back to DP3 for now and all is good.

No issues for me either. I dirty flashed and installed Magisk 16.4 and no issues at all besides the SafetyNet issue.

henderjr said:
I had the same exact behavior yesterday. If you're still running the magisk module "[APP] 18. Feb ◦ Edge Sense Plus 1.22.0 ◦ Customize Active Edge on your Pixel 2 XL" it will cause SystemUI to behave strange and show the battery saver icon. Disable the module until it gets updated.
Click to expand...
Click to collapse
It WORKS! It just WORKS! Thank you SOOOO Much!

It works for me too. Thanks!

...............

Insinuendi said:
So I booted into TWRP 3.2.2-0-taimen on DP4, still can't decrypt,. Tried using ADB sideload with Magisk 16.4 zip anyway, looks like it works. Then I try rebooting and it never starts.
Click to expand...
Click to collapse
Turn off your screen lock and you won't have to worry about TWRP not decrypting (settings > security & location > screen lock > none). Turn your screen lock back on after you've completed the flash.

xunholyx said:
Turn off your screen lock and you won't have to worry about TWRP not decrypting (settings > security & location > screen lock > none). Turn your screen lock back on after you've completed the flash.
Click to expand...
Click to collapse
I've tried both ways, same issue. Twice now I've had to flash DP4 again (without -w) because it gets stuck in a bootloop. Is there something I might be missing?
Sent from my Pixel 2 XL using Tapatalk

Insinuendi said:
I've tried both ways, same issue. Twice now I've had to flash DP4 again (without -w) because it gets stuck in a bootloop. Is there something I might be missing?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Since you flashed Magisk without decrypt data, it's highly likely that the data partition maybe damaged. Just flash-all with -w (don't remove -w) and your phone should boot... Anyway I think your data is already gone the moment you flashed Magisk without decryption...

magisk + xposed problem

Hi all,
I have installed Magisk 16.0 based on Maik93's post, and Xposed Framework SDK27 90.2-beta3 (Systemless), through Magisk modules.
When I enable the Xposed module, the phone first shows endless boot animation, and when restarting it again, it boots, but the Xposed app seems not installed (not listed in Settings->Apps and its icon is not present in chooser), although, in Magisk, it is visible in the Modules and it's checkbox is checked.
Did anybody successfully installed Xposed with A2 Lite? What can be the problem?
Thanks a lot,
Circum

Did you install the apk of xposed?
---------- Post added at 11:51 PM ---------- Previous post was at 11:46 PM ----------
https://forum.xda-developers.com/attachment.php?attachmentid=4393082&d=1516301692
Here is the link from xda

No, sorry, I was not aware that it is a separate thing.
Now I have installed, but it says that no Xposed Framework is installed. If I try to install a framework from inside the installer (90-beta3), it -- obviously -- reports an error that /system/framework/XposedBridge.jar already exist...
Because of this, I cannot enable any module from Xposed Installer.
Any tips what do I do wrong?

I want to use Xposed too but we will have to wait for TWRP I guess.

Not sure what happened to you, did you tried ti reboot your phone? Mine is working just fine

mik.y said:
I want to use Xposed too but we will have to wait for TWRP I guess.
Click to expand...
Click to collapse
You can install now through Magisk if you want, if yiu get bootloopbfor any xposed module, just flash thr original boot.img

HoangP05 said:
You can install now through Magisk if you want, if yiu get bootloopbfor any xposed module, just flash thr original boot.img
Click to expand...
Click to collapse
I was able to install it somehow,but stuck after each reboot in process. Now some apps are diying like call enhancement and some test app. So its quite dirty. I have Magist 16.0 installed.
Lol,I cant connect to internet with xposed to download any module. Useless

mik.y said:
I was able to install it somehow,but stuck after each reboot in process. Now some apps are diying like call enhancement and some test app. So its quite dirty. I have Magist 16.0 installed.
Lol,I cant connect to internet with xposed to download any module. Useless
Click to expand...
Click to collapse
Not all are working apparently, but if it is bootloop, you so try to let it boot again, press power and volume down as the same time while it bootloop, the second boot always work for me

There is TWRP for Mi A2 Lite.
Search on google.
NOTICE: For now there isn't official TWRP. There'w unofficiak fork which can you install using fastboot. :good:

Not sure what happened, AFAIK I have rebooted the phone at least once, but after rebooting again, it said that the framework is installed, but has some problem with it and not functioning (yellow background, sorry, I forgot to take a screenshot), and rebooting once again solved the problem, I can confirm that Xposed works.
But as others mentioned, installing Magisk itself makes problems with the boot. Booting always stucks, I always needed (even before installing Xposed) to long-press power after several minutes and the second try usually boots up.
Now having Magisk and Xposed (and GravityBox) installed usally need to restart booting twice (i.e., the 3rd boot works).
Any suggestions how to debug / get logs about this problem?
HoangP05 said:
Not sure what happened to you, did you tried ti reboot your phone? Mine is working just fine
Click to expand...
Click to collapse

Xposed's Gravity box module works on Mi A2 lite?

Yes, GravityBox is working, although as I mentioned, there are issues with boot - I have to reboot several times until it succeeds...

performace drops significantly when i install the xposed module for magisk. i hope they fix it.

So far everything works fine on my end, I'm not noticing any performance drops in my day to day use. Then again I haven't used it much without Magisk + exposed but from what i'm seeing it's working well, no noticeable lag or stuttering.
I have gravity box, Amplify and Greenify modules running.

circum said:
Not sure what happened, AFAIK I have rebooted the phone at least once, but after rebooting again, it said that the framework is installed, but has some problem with it and not functioning (yellow background, sorry, I forgot to take a screenshot), and rebooting once again solved the problem, I can confirm that Xposed works.
But as others mentioned, installing Magisk itself makes problems with the boot. Booting always stucks, I always needed (even before installing Xposed) to long-press power after several minutes and the second try usually boots up.
Now having Magisk and Xposed (and GravityBox) installed usally need to restart booting twice (i.e., the 3rd boot works).
Any suggestions how to debug / get logs about this problem?
Click to expand...
Click to collapse
Magisk alone didnt give me boot problems. What rooting guide did you follow?

fake__knv said:
Magisk alone didnt give me boot problems. What rooting guide did you follow?
Click to expand...
Click to collapse
I used this one: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
But before the update. Since that I have removed Magisk to enable the OTA update, and did not put it back yet -- although, there are many small areas I feel the lack of root...

circum said:
I used this one: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
But before the update. Since that I have removed Magisk to enable the OTA update, and did not put it back yet -- although, there are many small areas I feel the lack of root...
Click to expand...
Click to collapse
I can assure you @BubuXP's guide is good. Used his rooting guide, followed the steps for updates and its good to go. I rooted my phone when Im on August update. Now Im in September update

Android 12 Developer Preview

Developer Preview is up if anybody wants to try it
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com

Holy Moly.

Side loaded OTA via ADB all works fine no issues so far no FC can't say much difference

DoobyDroid said:
Side loaded OTA via ADB all works fine no issues so far no FC can't say much difference
Click to expand...
Click to collapse
Seems like for now, most UI and user facing changes in general are hidden behind flags, this one is meant for the devs, so it's to be expected. The beta, on the other end, will be aimed at users, and then we will see what changes

I upgraded last night. Had to reboot twice after restart. Then everything was stable. First time it rebooted after install, nothing seemed to want to work and kept FCing. Second reboot, everything is fine now. Sometimes, Nova needs to be indicated when I press the home button that it's default, otherwise, everything is working fine.
Is it me or does the Android version still say 11 but the build is "S"?

I downloaded the 12 DP1... and it just isn't ready yet (understandably so) for the daily driver use I need.f
Rooting it requires disable verity and verification. You'll need magisk 23 or canary to patch boot.img as well. Not disabling verity/verification, it will only boot back into fastboot and list the reason as something like, "unable to load boot image".
Once rooted, I moved on to installing edxposed --- using riru, riru edxposed, and edxposed manager. Everything installs without problems. Final reboot, and reboots as normal. But then about 90 seconds later, you'll start getting FC after FC after FC. All apps too, and background apps, and systemui, etc.
Removing the riru components and edxposed manager, doesn't correct this problem.
Did fresh format and reinstall of the DP1... rooted again... and then tried Viper4Android. I use a very simple version. You just flash it, and its done (no manual driver install either). Rather than the 3 reboot, AML, driver install, etc.
V4A installs with good logs. Reboots without a hitch. But I noticed the v4a icon in the status bar is missing. I open it up manually, and start getting freezes and fc's. Within 5 minutes, I get kernel panic reboots -- and non-bootloop freezes on the working G screen.
Reboot manually with long press power, get it loaded back up and immediately remove V4A. Reboot and now I'm back to stock.
Get FC's every hour or two. Random reboots too. Battery life is struggling.
I decided to wait until a better version drops, perhaps the beta or at least a DP2.5 or 3.0. As of right now, having Android S is mostly just a status thing -- to show people how cool we are to have access to it as such an early stage. But unless you are dedicated to helping improve the ROM through daily use and reporting... I highly recommend that you stick with Android R.

Just flashed the 1st public android 12 beta bramble-ota-spb1.210331.013-3c294b13.zip with adb sideload. Listed as android S atm, surprised 5G was enabled as this wasn`t the case with android 11 in the Netherlands. All apps working fine so far and still finding out the new stuff.

Has anyone been able to root the Pixel 4a 5G with Android 12 Beta 1?.
Kindly share the steps.

ekowwillis said:
Has anyone been able to root the Pixel 4a 5G with Android 12 Beta 1?.
Kindly share the steps.
Click to expand...
Click to collapse
yep i also like to know..tried twice but ended up in fastboot mode and cant get it to boot.i used the old magisk patched method but i probebly missing something

galza said:
yep i also like to know..tried twice but ended up in fastboot mode and cant get it to boot.i used the old magisk patched method but i probebly missing something
Click to expand...
Click to collapse
Clean wipe and follow the OP instructions in this Pixel 5 thread. Make sure you use the images for 4a5g where needed
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com

Random freezes using magisk with latest stock (no modules)

I was getting random freezes (at least once daily) that I had to force reboot (sometimes twice at a time) using magisk.
It appears to have started on January patch (or android 11). I decided to remove magisk and unroot completely and the freezes were gone.
Then I decided to try magisk (stable channel) with this April security patch and less than 12 hours later I got the first freeze. Just to make sure I did not install any module.
Note: the kind of freeze I'm experiencing makes the phone extremely slow, almost no app start and the app drawers renders with some icons missing. I cannot even power off normally so I need to force reboot.

quera said:
I was getting random freezes (at least once daily) that I had to force reboot (sometimes twice at a time) using magisk.
It appears to have started on January patch (or android 11). I decided to remove magisk and unroot completely and the freezes were gone.
Then I decided to try magisk (stable channel) with this April security patch and less than 12 hours later I got the first freeze. Just to make sure I did not install any module.
Note: the kind of freeze I'm experiencing makes the phone extremely slow, almost no app start and the app drawers renders with some icons missing. I cannot even power off normally so I need to force reboot.
Click to expand...
Click to collapse
I had similar, random freezes starting in January too. I'd try Magisk Canary and either EX or Kirisakura kernel. I'm on April running Magisk Canary, EX kernel with Active Edge, Systemless Hosts, Universal SafetyNet Fix modules and have no freezes.

newkydawg said:
I had similar, random freezes starting in January too. I'd try Magisk Canary and either EX or Kirisakura kernel. I'm on April running Magisk Canary, EX kernel with Active Edge, Systemless Hosts, Universal SafetyNet Fix modules and have no freezes.
Click to expand...
Click to collapse
Which features of Ex kernel are you using?

quera said:
Which features of Ex kernel are you using?
Click to expand...
Click to collapse
DoubleTap2Wake - Enabled
Sweep2Wake - Enabled
Sweep2Sleep - Enabled
Vibrate on wake - Disabled
Memory>ZRAM>Swappiness 100 (can't remember is that's a stock value or not)