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

Status
Not open for further replies.
Search This thread

ace2nutzer

Recognized Developer
Apr 28, 2014
4,311
5,151
36
Cologne
Bootloop with LZ4 RD

Hello !

i'm a Galaxy S8 kernel dev.
Latest stable Magisk works fine with SAMSUNG stock kernel + my custom kernel (lz4 RD comp).
But latest canary (non-debug) causes bootloop, but works fine with stock kernel (gzip RD comp).

Any hints ?

last_kmsg error code
Code:
<6>vdd_ldo6: disabling
<6>vdd_ldo10: disabling
<6>VLDO_20: disabling
<6>VLDO_43: disabling
<6>ALSA device list:
<6>  #0: Exynos8895-Madera
<3>Warning: unable to open an initial console.
<5>RAMDISK: lz4 image found at block 0
<6>max77865 : [0xb1]0x5a, [0xb2]0xdf, [0xb3]0xe0, [0xb4]0x31, [0xb5]0x00, [0xb6]0xff, [0xb7]0x15, [0xb8]0x38, [0xb9]0xc9, [0xba]0x18, [0xbb]0x18, [0xbc]0x1c, [0xbd]0x6c, [0xbe]0x34, [0xbf]0xff, [0xc0]0x14, [0xc1]0x14, [0xc2]0x00, [0xc3]0x73, 
<6>sec-battery battery: sec_bat_temperature: HLT(800) HLR(750) HT(500), HR(450), LT(0), LR(50)
<6>sec_bat_swelling_check: swelling highblock(450), highrecov(400)
<7>max77865_get_float_voltage: battery cv reg : 0x18, float voltage val : 43500
<6>sec_bat_swelling_check: status(1), swell_mode(0:0:0), cv(43500)mV, temp(322)
<6>max77865_get_charger_state : charger status (0x31)
<6>sec-battery battery: sec_bat_fullcharged_check: Charging Mode : Normal
<6>sec_bat_set_current_event: current event before(0x4), after(0x0)
<6>sec_bat_calculate_safety_time : EXPIRED_TIME(0), IP(2500000), CP(0), CURR(0), STANDARD(500)
<6>sec_bat_check_mix_temp: mix_limit(0), temp(322), chg_temp(374), input_current(500)
<6>sec_bat_check_afc_temp: cable_type(4), chg_limit(0) vbus_by_siop(0)
<6>[max77865_set_input_current] REG(0xc0) DATA(0x14), CURRENT(500)
<6>[max77865_set_charge_current] REG(0xb9) DATA(0xca), CURRENT(500)
<6>sec_bat_set_charging_current: power(2500), input(500), charge(500)
<6>max77865_set_topoff_current: reg_data(0x03), topoff(305mA)
<6>sec-battery battery: sec_bat_monitor_work: HLT(800) HLR(750) HT(500), HR(450), LT(0), LR(50), lpcharge(0)
<6>sec-battery battery: sec_bat_monitor_work: Status(Charging), mode(Normal), Health(Good), Cable(USB, USB, 1, 0), level(100%), slate_mode(0), store_mode(0), HV(NONE), sleep_mode(0)
<6>sec-battery battery: sec_bat_set_polling: Status:Charging, Sleep:No, Charging:Yes, Short Poll:Yes
<6>sec_bat_get_property cable type = 4 sleep_mode = 0
<6>sec-battery battery: sec_bat_set_polling: Polling time 10/30 sec.
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x10 Value: 0x16
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x10 Value: 0x16
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x5 Value: 0x0
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x5 Value: 0x0
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x11 Value: 0x20
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x11 Value: 0x20
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x20 Value: 0x0
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x20 Value: 0x0
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x23 Value: 0x0
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x23 Value: 0x0
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x24 Value: 0x44
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x24 Value: 0x44
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x26 Value: 0x0
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x26 Value: 0x0
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x27 Value: 0x44
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x27 Value: 0x44
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x28 Value: 0x2a
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x28 Value: 0x2a
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x29 Value: 0x2a
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x29 Value: 0x2a
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x2a Value: 0x2a
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x2a Value: 0x2a
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x2b Value: 0x26
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x2b Value: 0x26
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x30 Value: 0x9
[B]<3>RAMDISK: EOF while reading compressed data
<3>data corrupted[/B]
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x30 Value: 0x9
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x31 Value: 0x9
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x31 Value: 0x9
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x32 Value: 0x20
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x32 Value: 0x20
<6>
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x33 Value: 0x20
<4>VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
<4>Please append a correct "root=" boot option; here are the available partitions:
<4>0100            8192 ram0  (driver?)
<4>0101            8192 ram1  (driver?)
<4>0102            8192 ram2  (driver?)
<4>0103            8192 ram3  (driver?)
<4>0104            8192 ram4  (driver?)
<6>[SX9320]: sx9320_initialize_register - Read Reg: 0x33 Value: 0x20
<6>
<4>0105            8192 ram5  (driver?)
<4>0106            8192 ram6  (driver?)
<4>0107            8192 ram7  (driver?)
<4>0108            8192 ram8  (driver?)
<4>0109            8192 ram9  (driver?)
<4>010a            8192 ram10  (driver?)
<4>010b            8192 ram11  (driver?)
<4>010c            8192 ram12  (driver?)
<4>010d            8192 ram13  (driver?)
<4>010e            8192 ram14  (driver?)
<4>010f            8192 ram15  (driver?)
<4>0800        62464000 sda  driver: sd
<4>  0801            4096 sda1 52444e41-494f-2044-424f-544130000000
<4>  0802            4096 sda2 52444e41-494f-2044-4e41-000000000000
<4>  0803           20480 sda3 52444e41-494f-2044-4546-530000000000
<4>  0804            8192 sda4 52444e41-494f-2044-5041-52414d000000
<4>  0805            8192 sda5 52444e41-494f-2044-5550-5f504152414d
<4>  0806            8192 sda6 52444e41-494f-2044-424f-544132000000
<4>  0807           40960 sda7 52444e41-494f-2044-424f-4f5400000000
<4>  0808           47104 sda8 52444e41-494f-2044-5245-434f56455259
<4>  0809            8192 sda9 52444e41-494f-2044-424f-544131000000
<4>  080a           43008 sda10 52444e41-494f-2044-5241-44494f000000
<4>  080b            1024 sda11 52444e41-494f-2044-544f-4d4253544f4e
<4>  080c            1024 sda12 52444e41-494f-2044-444e-540000000000
<4>  080d             512 sda13 52444e41-494f-2044-5045-525349535445
<4>  080e            1024 sda14 52444e41-494f-2044-4d49-534300000000
<4>  080f            4096 sda15 52444e41-494f-2044-5354-454144590000
<4>  103:00000      16384 sda16 52444e41-494f-2044-4b45-595245465547
<4>  103:00001    4454400 sda17 52444e41-494f-2044-5359-5354454d0000
<4>  103:00002     512000 sda18 52444e41-494f-2044-4341-434845000000
<4>  103:00003      10240 sda19 52444e41-494f-2044-4849-4444454e0000
<4>  103:00004      51200 sda20 52444e41-494f-2044-4f4d-520000000000
<4>  103:00005       5120 sda21 52444e41-494f-2044-4350-5f4445425547
<4>  103:00006      20480 sda22 52444e41-494f-2044-4e41-445f46570000
<4>  103:00007       1024 sda23 52444e41-494f-2044-4e41-445f52454645
<4>  103:00008   57184256 sda24 52444e41-494f-2044-5553-455244415441
<4>0810            4096 sdb  driver: sd
<4>0820            8192 sdc  driver: sd
<4>0830            8192 sdd  driver: sd
<4>  0831            6144 sdd1 52444e41-494f-2044-4350-454653000000
<6>[SX9320]: sx9320_initialize_register - Write Reg: 0x34 Value: 0xb
<4>
<0>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
<0>Kernel loaded at: 0x80120000, offset from compile-time address a0000
<0>s3c2410_wdt: watchdog reset is started to 30secs
<3>mif: ss310ap_send_panic_noti_ext: Send CMD_KERNEL_PANIC message to CP
<4>CPU: 2 MPIDR: 80000102 PID: 1 Comm: swapper/0 Tainted: G        W       4.4.111-a2n-g50468dc4 #5
<4>Hardware name: Samsung DREAMLTE EUR rev06 board based on EXYNOS8895 (DT)
<4>Call trace:
<4>[<ffffff800812acc4>] dump_backtrace+0x0/0x214
<4>[<ffffff800812aeec>] show_stack+0x14/0x1c
<4>[<ffffff80083f919c>] dump_stack+0xa0/0xc0
<4>[<ffffff80081e0028>] panic+0x154/0x294
<4>[<ffffff80094ee094>] mount_block_root+0x238/0x2d8
<4>[<ffffff80094ee2e0>] mount_root+0x6c/0x78
<4>[<ffffff80094ee444>] prepare_namespace+0x158/0x1a0
<4>[<ffffff80094edca8>] kernel_init_freeable+0x210/0x22c
<4>[<ffffff8008c5af90>] kernel_init+0x10/0x10c
<4>[<ffffff8008125ba0>] ret_from_fork+0x10/0x30

Workaround:
Compress RD with stock method "gzip" instead "lz4".
 
Last edited:
  • Like
Reactions: Nitrogenous

phoberus

Senior Member
  • Oct 21, 2013
    961
    257
    I'm on the latest canary build and my Banking app "UBS Access" detects root after his latest update. I want to flash the canary debug build and help to optimize it, I think it's a new detection method. Do I need to post magisk.log and logcat? Or which information do you need?

    I did all like in the official best practices for magiskhide, safetynet passes und device is certified
     

    martyfender

    Senior Member
    Mar 9, 2017
    3,158
    1,675
    Indianapolis, IN
    I lost hide manager and download section on canary build, anyone has same problem?

    You will get that if Magisk Manager is not connected to the internet.

    ---------- Post added at 09:36 PM ---------- Previous post was at 09:33 PM ----------

    I'm on the latest canary build and my Banking app "UBS Access" detects root after his latest update. I want to flash the canary debug build and help to optimize it, I think it's a new detection method. Do I need to post magisk.log and logcat? Or which information do you need?

    I did all like in the official best practices for magiskhide, safetynet passes und device is certified

    My guess is that this will fall in the category by topjohn of:
    will not fix.

    See here:

    https://github.com/topjohnwu/Magisk/issues/1152
     
    Last edited:

    darenhoff

    Senior Member
    May 28, 2014
    85
    7
    Is magisk working on Q?

    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


    Hello everybody.....belated Happy Christmas and Early new year to all.
    I am searching all, reading all thru magisk developers notes. It looks till now it is still working in twrp/recovery mode on Q.
    Anybody using magisk on Android 10? Need it working on my RN8 AOSIP 10 :eek:
    Thanks
     

    zgfg

    Senior Member
  • Oct 10, 2016
    5,307
    2,606
    Hello everybody.....belated Happy Christmas and Early new year to all.
    I am searching all, reading all thru magisk developers notes. It looks till now it is still working in twrp/recovery mode on Q.
    Anybody using magisk on Android 10? Need it working on my RN8 AOSIP 10 :eek:
    Thanks
    Of course, people use Magisk on Q for quite some time.
    Did you search (upper/right) for 10, Q, Pixel, etc
     
    • Like
    Reactions: RandomPooka

    xunholyx

    Recognized Contributor
    Dec 3, 2012
    7,640
    5,211
    Vancouver
    Google Pixel 2 XL
    Google Pixel 5
    Hello everybody.....belated Happy Christmas and Early new year to all.
    I am searching all, reading all thru magisk developers notes. It looks till now it is still working in twrp/recovery mode on Q.
    Anybody using magisk on Android 10? Need it working on my RN8 AOSIP 10 :eek:
    Thanks

    If Magisk didn't work on Android 10, it would have been all over the Android news sources by now. Yes it works with it, and has since the first beta 10 came out in March.
     
    • Like
    Reactions: yyz71

    rcurious

    Member
    Jul 9, 2011
    21
    10
    Hello. My device is using system-as-root without A/B partitions. I want to install Magisk.
    I found this guide but It's not clear to me if I must do that with both recovery.img and boot.img or just one of them? Thanks

    • Copy the boot/recovery image to your device
    • Download and install the latest Magisk Manager
    • If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
    • Press Install → Install → Select and Patch a File, and select your stock boot/recovery image file
    • Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
    • Copy the patched image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB:
    • adb pull /sdcard/Download/magisk_patched.img
    • Flash the patched boot/recovery image to your device and reboot. For most devices, here is the fastboot command:
    • fastboot flash boot /path/to/magisk_patched.img or
    • fastboot flash recovery /path/to/magisk_patched.img if you are patching a recovery image
     
    Last edited:

    Didgeridoohan

    Senior Moderator / Dev Committee / Dev Relations
    Staff member
    May 31, 2012
    11,648
    12,432
    Gothenburg
    Google Nexus 4
    Nexus 6
    Hello. My device is using system-as-root without A/B partitions. I want to install Magisk.
    I found this guide but It's not clear to me if I must do that with both recovery.img and boot.img or just one of them? Thanks

    You missed this part, in the beginning of the installation instructions:
    If your device is NOT A/B, but IS using system-as-root, then you will have to install Magisk to the recovery partition of your device. Follow the instructions in Boot Image Patching, but instead of using your boot image, use your recovery image. Read through the Magisk in Recovery section!
    I'm other words: use the recovery image.
     
    Last edited:

    edzamber

    Senior Member
    Feb 21, 2012
    3,886
    3,683
    @topjohnwu

    Hi bro

    First Happy New year 2020 [emoji4]

    Seems something goes wrong with last magisk manager : after hide it, it appears out of date... Screenshot_20200102-123021.jpg
     
    • Like
    Reactions: andrey bobylev

    Didgeridoohan

    Senior Moderator / Dev Committee / Dev Relations
    Staff member
    May 31, 2012
    11,648
    12,432
    Gothenburg
    Google Nexus 4
    Nexus 6
    edzamber;81366479 [user=4470081 said:
    @topjohnwu[/user]

    Hi bro

    First Happy New year 2020 [emoji4]

    Seems something goes wrong with last magisk manager : after hide it, it appears out of date...

    It's the stub apk version that's not updating (for whatever reason). It's been brought to @topjohnwu's attention already, so he'll likely have it fixed soon.
     

    RandomPooka

    Senior Member
    Oct 14, 2010
    4,019
    2,488
    Kent, OH
    @topjohnwu

    Hi bro

    First Happy New year 2020 [emoji4]

    Seems something goes wrong with last magisk manager : after hide it, it appears out of date...


    It's the stub apk version that's not updating (for whatever reason). It's been brought to @topjohnwu's attention already, so he'll likely have it fixed soon.

    Fixed by installing the most recent manager app from the download link in the release there's, then uninstalling the old app and rebooting .

    Not elegant, but it will work for now. Sure to be fixed properly in the next release
     

    martyfender

    Senior Member
    Mar 9, 2017
    3,158
    1,675
    Indianapolis, IN
    Fixed by installing the most recent manager app from the download link in the release there's, then uninstalling the old app and rebooting .

    Not elegant, but it will work for now. Sure to be fixed properly in the next release

    Please clarify your instructions here as that didn't work for me unless you mean a manager not hidden?
    I downloaded the latest app-debug.apk, because I am on the debug build, Or do you mean the Stable Magisk Manager or the app-release.apk?

    https://github.com/topjohnwu/magisk_files/tree/canary

    Thanks
     
    Last edited:

    RandomPooka

    Senior Member
    Oct 14, 2010
    4,019
    2,488
    Kent, OH
    Please clarify your instructions here as that didn't work for me unless you mean a manager not hidden?
    I downloaded the latest app-debug.apk.

    https://github.com/topjohnwu/magisk_files/tree/canary

    Thanks

    Steps 1-4 were trying to update from the Magisk Manager app and swearing when it didn't update.

    Went to the release thread and downloaded the 7.5.0 Manager APK.

    With the old Manager hidden, I installed the new one, opened it, and then uninstalled the old one, leaving only unhidden 7.5.0 Manager

    Rebooted to TWRP and flashed the newest Canary build because the new manager didn't see Magisk as installed.

    Everything was peaches and cream when I rebooted to the OS.

    -- OnePlus 7 Pro, 10.3.0 OOS, Canary update channel, no modules installed, only a few apps hidden with Magisk hide --
     

    zgfg

    Senior Member
  • Oct 10, 2016
    5,307
    2,606
    anyone with the same issue with the latest update in canary?
    it has an issue with play Protect...
    Which exact issue with Play Protect?

    Btw, it was recommended earlier (a month or so ago, at the time of Magisk 20.1 and the corresponding Canary builds)), to temporarily disable Play Protect while updating Magisk

    PS: Btw, MM 265 and Magisk 20201 (Canary), everything ok so far (Huawei P9, Oreo, Direct update)
     
    Last edited:

    phelite2015

    Member
    Oct 3, 2019
    49
    14
    Which exact issue with Play protect?

    Btw, it was recommended earlier (a month or so ago, at the time of Magisk 20.1 and corresponding Canary builds)), to temporarily disable Play Protect while updating Magisk
    i cant post picture here..
    but its something just like you say..
    i only experience this today, all other updates is working well with play protect...
    at first the installation doesnt continue then when you try again,
    a pop up saying if i want to install it even it doesnt pass play protect.
    i click install it anyway in order to proceed..

    Sent from my Redmi K20 Pro Premium Edition using Tapatalk

    ---------- Post added at 07:56 AM ---------- Previous post was at 07:47 AM ----------

    UPDATE:
    its weird but i already solved it..
    i just change from wifi to mobile data and now magisk is successfully installed..
    but the magisk manager after updating its still showing the old version and saying update is available..

    Sent from my Redmi K20 Pro Premium Edition using Tapatalk

    ---------- Post added at 08:22 AM ---------- Previous post was at 07:56 AM ----------

    Update:

    Solution: Restore magisk manager, do not hide or rename magisk manager

    Sent from my Redmi K20 Pro Premium Edition using Tapatalk
     
    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.