• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Status
Not open for further replies.
Search This thread

anthonykb

Senior Member
Apr 23, 2016
95
30
29
New London County, CT USA
How to parse additional kernel arguments to extra_cmdline

Could you add to a tutorial how this could be possible? I think this would help a lot of people maximizing the performance of their devices with all the possible parameters. Imagine if we could change them from the app. Thanks @topjohnwu :):D:):D
 

janedoesmith

Senior Member
Jul 11, 2012
203
184
I have settled on the following workaround. When it fails safetynet, go into the settings and toggle the magisk hide option from on to off then back to on. Then recheck safetynet and it will pass again.
fyi i know that this is not the place to bring up safetynet issues as it was made clear that this is not a priority. but it has been mentioned a few times in here... and the general forum isnt for canary troubleshooting. so apologies in advance but here are some logs that show safetynet not passing. no response necessary, just fyi. note that this is not a consistent issue; rather, comes up sporadically.

https://drive.google.com/file/d/1ZCBZI2ldva36Vha5Hqu5iWL7ec6hnOM_/view?usp=drivesdk

https://drive.google.com/file/d/1P26tO4gQ6FeN1Vgg4uIQJ2lxThJbHnm8/view?usp=drivesdk

https://drive.google.com/file/d/1vQsMeieAQM-KMQuqnVZUWayw-LagxN4K/view?usp=drivesdk
 

candiesdoodle

Senior Member
Jan 24, 2012
843
280
New Delhi
Posted it in the main thread.

Those loosing root/ failing SN intermittently please do a clean install of v18.
It helped me - I had same issue when I upgraded via twrl from 17.3 to 18
Then I rolled back and used the "patch boot image" method.
Then just flashed the patched boot img in twrp. Had to disable and re-enable magiakhide... But it has stuck since then. No issues so far.
 

hshah

Senior Member
Dec 24, 2005
2,122
378
Mine passes initially (always has) and then breaks after a while. I dropped it down to 64kb, rebooted and experienced the same behaviour... it passed initially and then about 45 mins later started failing.

I'll try clearing cache etc and see if that makes a difference :cowboy:

It appeared to last longer but it was failing again this morning.


Posted it in the main thread.

Those loosing root/ failing SN intermittently please do a clean install of v18.
It helped me - I had same issue when I upgraded via twrl from 17.3 to 18
Then I rolled back and used the "patch boot image" method.
Then just flashed the patched boot img in twrp. Had to disable and re-enable magiakhide... But it has stuck since then. No issues so far.

Going to try this now... as they say, what's the worst that could happen :silly:
 

gforceriders

Senior Member
Oct 28, 2010
594
203
Heartland Tx

The_Walking_Playground

Senior Member
Nov 30, 2017
653
346
The latest version of the intelligence Hub? If so maybe it's the ROM I am running.

---------- Post added at 03:36 AM ---------- Previous post was at 03:25 AM ----------




The latest version of the intelligence Hub? If so maybe it's the ROM I am running.
Hi,

Yes, I'm using the latest version of Intelligence Hub. I keep it updated from the Play Store. I'm also running a custom ROM on my device (HTC U11, Slim9 Pie) without an issue.

TWP
 

spambayes

Senior Member
Oct 13, 2009
353
36
After updating to v18 stable, I lost root functions even though Magisk installed without errors. Root apps were not triggering any su requests in Magisk. Rolling back to v17.0 restored root.

Performed a clean uninstall using canary uninstaller in TWRP and flashed Magisk v18 canary build.

Hoping the source of issue could be fixed.

Phone: Samsung Note 3 N9005, stock Lollipop 5.0.1

Magisk.log attached.
 

Attachments

  • magisk.log
    29 KB · Views: 8

martyfender

Senior Member
Mar 9, 2017
3,185
1,704
Indianapolis, IN
After updating to v18 stable, I lost root functions even though Magisk installed without errors. Root apps were not triggering any su requests in Magisk. Rolling back to v17.0 restored root.

Performed a clean uninstall using canary uninstaller in TWRP and flashed Magisk v18 canary build.

Hoping the source of issue could be fixed.

Phone: Samsung Note 3 N9005, stock Lollipop 5.0.1

Magisk.log attached.

In your log I saw that you have xposed installed and just wonder if that could be one of the reasons you are having problems? You made no mention of this in the general thread.

In the past, on an older Android 5 device, it caused all kinds of problems for me.
what xposed addons and Magisk modules do you use?

I really think you need a clean install of your rom, without xposed installed. Was xposed installed systemless as a Magisk module or did you use the standard xposed install method, which modifies the system?

Or you could stay on the older version of Magisk as it appears to be working for you.
 
Last edited:

kaibird

Senior Member
Jan 25, 2011
165
61
Burnaby
I have settled on the following workaround. When it fails safetynet, go into the settings and toggle the magisk hide option from on to off then back to on. Then recheck safetynet and it will pass again.
This didnt work for me as I lost MagiskHide and Safetynet(ctsProfile and basicintegrity) both failed simultaneously
 

kaibird

Senior Member
Jan 25, 2011
165
61
Burnaby
Try flashing the magisk uninstaller and then dirty flashing ROM, magisk, kernel, etc.

Cheers!

Thx for ur reply
I installed an OTA update on my phone, Safetynet was working on previous Canary v18.1-a54eaf5 but failed on the latest v18.1-b245031c.
MagiskHide Props Config module could not load the late_start service boot script during boot
I have to reboot 3 to 5 times by chance to get safetynet working and I try not to reboot my phone for as long as I could
now??
 

Attachments

  • magisk_log_20181216_070202.log
    50.3 KB · Views: 10

yannik~

Senior Member
Oct 17, 2013
78
19
Flashing magisk (latest debug build) stops 'adb root' from working:
$ adb root
adbd cannot run as root in production builds

This is my magisk log:
Code:
03-04 07:25:26.850   624   624 D Magisk  : resetprop: getprop [ro.crypto.state]: [encrypted]
03-04 07:25:26.850   624   624 D Magisk  : resetprop: getprop [init.svc.vold]: [running]
03-04 07:25:26.853   624   624 I Magisk  : * Creating /sbin overlay
03-04 07:25:26.867   626   626 I Magisk  : Magisk v18.1-b245931c(18002) daemon started
03-04 07:25:26.867   626   627 I Magisk  : ** post-fs-data mode running
03-04 07:25:26.867   626   627 I Magisk  : * Initializing Magisk environment
03-04 07:25:26.869   626   627 D Magisk  : resetprop: getprop [ro.build.version.sdk]: [28]
03-04 07:25:26.869   626   627 I Magisk  : * Mounting mirrors
03-04 07:25:26.869   626   627 I Magisk  : bind_mount: /sbin/.magisk/mirror/system <- /system_root/system
03-04 07:25:26.869   626   627 I Magisk  : mount: /sbin/.magisk/mirror/vendor <- /dev/block/platform/soc/1d84000.ufshc/by-name/vendor_b
03-04 07:25:26.869   626   627 I Magisk  : bind_mount: /sbin/.magisk/mirror/bin <- /data/adb/magisk
03-04 07:25:26.870   626   627 I Magisk  : * Setting up internal busybox
03-04 07:25:26.887   632   632 I Magisk  : Magisk v18.1-b245931c(18002) logger started
03-04 07:25:26.907   626   627 I Magisk  : Create /data/adb/magisk.img with size 64M
03-04 07:25:26.979   626   627 I Magisk  : * Mounting /data/adb/magisk.img
03-04 07:25:27.032   626   627 I Magisk  : * Running post-fs-data.d scripts
03-04 07:25:27.032   626   627 I Magisk  : * Running module post-fs-data scripts
03-04 07:25:27.032   626   627 I Magisk  : * Loading modules
03-04 07:25:27.059   626   650 I Magisk  : * Starting MagiskHide
03-04 07:25:27.059   626   650 I Magisk  : hide_utils: Hiding sensitive props
03-04 07:25:27.059   626   650 D Magisk  : resetprop: prop [ro.boot.vbmeta.device_state] does not exist
03-04 07:25:27.059   626   650 D Magisk  : resetprop: prop [ro.boot.verifiedbootstate] does not exist
03-04 07:25:27.059   626   650 D Magisk  : resetprop: prop [ro.boot.flash.locked] does not exist
03-04 07:25:27.059   626   650 D Magisk  : resetprop: prop [ro.boot.veritymode] does not exist
03-04 07:25:27.059   626   650 D Magisk  : resetprop: prop [ro.boot.warranty_bit] does not exist
03-04 07:25:27.059   626   650 D Magisk  : resetprop: prop [ro.warranty_bit] does not exist
03-04 07:25:27.059   626   650 D Magisk  : resetprop: getprop [ro.debuggable]: [1]
03-04 07:25:27.059   626   650 D Magisk  : resetprop: setprop [ro.debuggable]: [0] by modifing prop data structure
03-04 07:25:27.059   626   650 D Magisk  : resetprop: getprop [ro.secure]: [1]
03-04 07:25:27.059   626   650 D Magisk  : resetprop: getprop [ro.build.type]: [userdebug]
03-04 07:25:27.059   626   650 D Magisk  : resetprop: setprop [ro.build.type]: [user] by modifing prop data structure
03-04 07:25:27.059   626   650 D Magisk  : resetprop: getprop [ro.build.tags]: [test-keys]
03-04 07:25:27.059   626   650 D Magisk  : resetprop: setprop [ro.build.tags]: [release-keys] by modifing prop data structure
03-04 07:25:27.059   626   650 D Magisk  : resetprop: getprop [ro.build.selinux]: [1]
03-04 07:25:27.059   626   650 D Magisk  : resetprop: setprop [ro.build.selinux]: [0] by modifing prop data structure
03-04 07:25:27.059   626   650 D Magisk  : hide_list: initialize
03-04 07:25:27.060   626   650 I Magisk  : hide_list add: [com.google.android.gms/.droidguard.DroidGuardService]
12-16 16:17:44.873   626  1069 I Magisk  : ** late_start service mode running
12-16 16:17:44.873   626  1069 D Magisk  : magiskdb: query magiskhide=[1]
12-16 16:17:44.873   626  1069 I Magisk  : * Running service.d scripts
12-16 16:17:44.873   626  1069 I Magisk  : * Running module service scripts
12-16 16:17:49.874   626  1069 D Magisk  : apk_install: attempting to install APK
12-16 16:17:57.668   626  1069 D Magisk  : apk_install: Success
12-16 16:18:10.388  2771  2868 F Adjust  : PRODUCTION: Adjust is running in Production mode. Use this setting only for the build that you want to publish. Set the environment to `sandbox` if you want to test your app!

I suspect that this is caused by magisk changing my ro.build.type from userdebug to user. How this be prevented?

Edit: I managed to fix it by disabling MagiskHide. However, I would prefer to keep both MagiskHide and adb root functional. Is this possible?
 
Last edited:

martyfender

Senior Member
Mar 9, 2017
3,185
1,704
Indianapolis, IN
Totally, but really OT here: @topjohnwu Congratulations! I just saw you completed your finals, on Twitter. That is quite an accomplishment! That brings back memories for me from way back in 1980-82, when I completed my BA degree. Back then I had no interest in computers, as the classes were using punch cards with Cobal and Fortran. I was a graduate of the school of journalism and I saw the first primative gui, when they replaced all of the school's news room typewriters with computers with monitors with the green, primative terminals. Maybe they were Wang, I'm not sure. All I know is that I worked for years for a firm that had Wangs that looked alot like the first that I saw at Indiana University. We have come along way since then.

By any means, I am looking forward to your future developments with Magisk.
 
Last edited:

peterlee928

Senior Member
Oct 16, 2014
950
405
fyi i know that this is not the place to bring up safetynet issues as it was made clear that this is not a priority. but it has been mentioned a few times in here... and the general forum isnt for canary troubleshooting. so apologies in advance but here are some logs that show safetynet not passing. no response necessary, just fyi. note that this is not a consistent issue; rather, comes up sporadically.

https://drive.google.com/file/d/1ZCBZI2ldva36Vha5Hqu5iWL7ec6hnOM_/view?usp=drivesdk

https://drive.google.com/file/d/1P26tO4gQ6FeN1Vgg4uIQJ2lxThJbHnm8/view?usp=drivesdk

https://drive.google.com/file/d/1vQsMeieAQM-KMQuqnVZUWayw-LagxN4K/view?usp=drivesdk
update:

after some testing, i believe that my issue was caused by a rogue app. after deleting this app, i have not had safetynet issues. something to consider for those who are also having issues.
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 294
    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.