[CLOSED][DEV] Magisk Canary Channel - Bleeding Edge Builds

Status
Not open for further replies.
Search This thread

mohsyn

Senior Member
Sep 22, 2012
88
10
Installed: 19.4-c1602d25 (19301)

Magisk Manager
Installed: 7.2.0-16b232d2 (216)

1. Magisk hide menu is blank
2. Rename magisk package results in magisk reported as uninstalled within magisk manager itself.
3. Superuser menu is blank too
4. Apps already given root access work
5. System reports root access
this is for custom build.
 
Last edited:

martyfender

Senior Member
Mar 9, 2017
3,152
1,661
Indianapolis, IN
Installed: 19.4-c1602d25 (19301)

Magisk Manager
Installed: 7.2.0-16b232d2 (216)

1. Magisk hide menu is blank
2. Rename magisk package results in magisk reported as uninstalled within magisk manager itself.
3. Superuser menu is blank too
4. Apps already given root access work
5. System reports root access
this is for custom build.

I had those issues also with MM 215, but it was solved with 216.
Try reverting to 214 or 213 to see if that helps. Log from your current version could be of use, before you do, though.

https://www.didgeridoohan.com/magisk/MagiskHelp

Magisk Manager 218 is now available.
 
Last edited:

mohsyn

Senior Member
Sep 22, 2012
88
10
With update 218
1. Modules are back and running
2. Magisk hide is back
3. superuser still blank but apps given permission earlier are working fine
4. Responsiveness very slow
 

refi64

Senior Member
Nov 25, 2013
82
119
refi64.com
Installing latest Magisk (19301) twice in TWRP seems to have eliminated most of the lagginess associated with it.

However, on my Taimen, I cannot get Viper4Android to work - it installs via Magisk, and then after running, every time it says no driver, attempts to DL, shows a progress bar, reboots - and nothing. I had read in another thread that V4A was working in Q Beta 4. Not for me.

This is apparently an issue in the latest V4A module, see here for an APK of the previous version that worked: https://forum.xda-developers.com/showpost.php?p=79614941&postcount=2049

I went through the delete all -> install AML -> install V4A dance a few more times and now it's working perfectly.
 
  • Like
Reactions: johnlgalt

mohsyn

Senior Member
Sep 22, 2012
88
10
Boot loop with 19.4 19301 and 218 after installing edxposed module.
it gets stuck at your system is now starting msg
Normal boot obviously has no root.
Tried uninstal of magisk with twrp. It fails with error 1
Currently only booting normally without root
 

doomscooter

Senior Member
Feb 1, 2009
609
187
Jakarta - Dumai
Magisk 194 + 218 normally in htc u11 stock rom PIE + root
 

Attachments

  • Screenshot_20190611-175843.png
    Screenshot_20190611-175843.png
    179.1 KB · Views: 886

JudgeDread11

Senior Member
Aug 17, 2014
879
497
Ao Nang, Krabi
Boot loop with 19.4 19301 and 218 after installing edxposed module.
it gets stuck at your system is now starting msg
Normal boot obviously has no root.
Tried uninstal of magisk with twrp. It fails with error 1
Currently only booting normally without root
If it only happens after installing edxposed then the problem most likely is with edxposed.
 

mohsyn

Senior Member
Sep 22, 2012
88
10
I'm stuck with a corrupt module not letting me boot with root access
/data/adb/modules is inaccessible via magisk and encrypted via twrp
Cannot put .disable_magisk in data/cache as it is encrypted.
anyone knows any other workaround to skip /delete modules on honor view 10?
 

JudgeDread11

Senior Member
Aug 17, 2014
879
497
Ao Nang, Krabi
I'm stuck with a corrupt module not letting me boot with root access
/data/adb/modules is inaccessible via magisk and encrypted via twrp
Cannot put .disable_magisk in data/cache as it is encrypted.
anyone knows any other workaround to skip /delete modules on honor view 10?
Did you try holding the volume up/down (can't remember which one it was) during boot for starting in safe mode(no Magisk, no root).
This is a feature which was added to Magisk a few versions back. It helped me solve some issues before.
 

mohsyn

Senior Member
Sep 22, 2012
88
10
Did you try holding the volume up/down (can't remember which one it was) during boot for starting in safe mode(no Magisk, no root).
This is a feature which was added to Magisk a few versions back. It helped me solve some issues before.

But that won't allow me to remove the modules.
I can boot normally with no root no magisk.
Safe mode won't help either
 

buffal0b1ll

Senior Member
Sep 5, 2012
2,628
4,341
Baltimore
Google Pixel 2
Google Pixel 2 XL
I'm stuck with a corrupt module not letting me boot with root access
/data/adb/modules is inaccessible via magisk and encrypted via twrp
Cannot put .disable_magisk in data/cache as it is encrypted.
anyone knows any other workaround to skip /delete modules on honor view 10?
Data/cache shouldn't be encrypted. Data/data and data/media are encrypted

Running this command in TWRP>Advanced>Terminal should create the file:
touch /data/cache/.disable_magisk




---------- Post added at 11:21 PM ---------- Previous post was at 11:16 PM ----------

Super user list is not showing any app..
Assuming you're on Q4?
Try flashing magisk uninstaller (to clean out all the stuff in sbin and MM), stock boot.img (just because it guarantees cleaned popped), then magisk.zip
This fixed that issue for me.
 
Last edited:
  • Like
Reactions: johnlgalt

johnlgalt

Senior Member
Nov 16, 2009
1,394
412
50
Atlanta
androidforums.com
With update 218
1. Modules are back and running
2. Magisk hide is back
3. superuser still blank but apps given permission earlier are working fine
4. Responsiveness very slow

A posted fix for the lag issue, particularly for those on ANdroid Q Beta builds, is to flash *TWICE* and then remember to wipe Dalvik.

If you flash from within the Magisk Manager, flash twice there also.

This is apparently an issue in the latest V4A module, see here for an APK of the previous version that worked: https://forum.xda-developers.com/showpost.php?p=79614941&postcount=2049

I went through the delete all -> install AML -> install V4A dance a few more times and now it's working perfectly.

I hadn't had time to go looking for it, yet, but I was going to sit down and search this weekend. Thank you so much for hte link and explanation - makes perfect sense.

If anyone was wondering, the magisk 19.3 and 19.4 both still cause massive lag in P2XL running latest patch of Q Beta 4 (build .019). Even after flashing twice in twrp.

Not here. Same phone (128 GB Taimen) and same Q build (.019 as of today).

I posted last week how double flashing worked for me, and taking this OTA, I double installed from within Magisk. All is well.
 

jcmm11

Recognized Contributor
Feb 10, 2012
3,574
3,585
Data/cache shouldn't be encrypted. Data/data and data/media are encrypted

Running this command in TWRP>Advanced>Terminal should create the file:
touch /data/cache/.disable_magisk
. . .
@mohsyn
Along with this /data/adb/modules should also be unencrypted. Just make sure when you boot up into TWRP when the password/pattern screen comes up you hit cancel. That should give you access to the areas you need.

The exception would be if the device uses full disk encryption as opposed to file based, but I don't know if there's any A/B devices doing that.
 
  • Like
Reactions: dr4go and guest4711
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 293
    Canary Magisk Manager: Link
    Canary Magisk Manager (Debug): Link
    Latest Release Notes: Link
    All Canary Files: Link

    The Canary Builds are similar to Google Chrome's: bleeding edge of the source.
    Be warned: Canary can be unstable.
    The binaries from debug channel are built with debug flag ON


    Install Canary Magisk Manager and go to Settings > Update Channel and switch to either Canary or Canary (Debug)
    If you need a clean start, download the Canary Uninstaller to uninstall any version of Magisk


    How to Report:
    • Only report bugs/logs using the debug channel!!
    • Magisk installation failure:
      In TWRP: Upload the recovery logs (pull the file /tmp/recovery.log, or select "Advanced > Copy Log" and upload)
      In MagiskManager: Choose to save logs after installation and upload
    • Magisk bugs:
      Magisk logs are placed in /cache/magisk.log (For A/B devices, they are actually in /data/cache/magisk.log)
      If you cannot boot or stuck in bootloops, grab logcats (and kernel dmesg if possible) on boot
    • Magisk Manager bugs:
      Grab logcat (NOT magisk logs) when the crash occurs, upload the logs and report how to reproduce
    • SafetyNet / CTS / XXX app won't work after enabling MagiskHide:
      Ignored
    69
    Android Q root baby
    37
    New canary release is now live!
    Due to high demands I added a new canary channel with debug flags turned off, but remember only report bugs/logs when using debug builds!
    34
    FYI, Canary Channels are now moved to a new URL. For existing Canary users, all you need to do is to update to the latest Canary Magisk Manager. Old links will be removed in a couple of days, so please upgrade when it still lasts ?
    30
    Just pushed a new build to fix issues on some devices (known: HTC devices)
    Support for logical partitions will be postponed after the next release cycle, I'm wrapping up for a public release now.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone