[CLOSED][BETA][2018.7.19] Magisk v16.7 (1671)

Status
Not open for further replies.
Search This thread

yochananmarqos

Inactive Recognized Contributor
Feb 15, 2013
3,375
2,520
github.com
Google Pixel 3
Google Pixel 7
Last week I installed Android Pie from Project Treble and also Magisk 16.7 too in my Xiaomi Mi 5s. After some of usage, the device crashed and rebooted to TWRP quite often. Then I came back to LOS 15.1, installed Magisk 16.0 but the problem still persisted. After uninstalled Magisk, device are no longer crashed and reboot. Any idea of what I've done wrong and how to fix it? Tried format data through TWRP but didn't help
No idea without logs. Also they're required per the OP. See here for help: https://www.didgeridoohan.com/magisk/MagiskHelp

Sent from my Pixel using XDA Labs
 
  • Like
Reactions: yyz71 and Pkt_Lnt

Gygun

Senior Member
Mar 13, 2016
59
32
Is there another way to hide root? (like something I could flash to make it work permanently?)
The hide option that comes with the manager doesn't work for me.

If I use another random app to hide it, it works, but it reset after every reboot, and sometimes I lose root and I need to reeboot again to make it work.

Thanks
 

Paschfire

Senior Member
May 16, 2014
932
812
45
Ottawa
Is there another way to hide root? (like something I could flash to make it work permanently?)
The hide option that comes with the manager doesn't work for me.

If I use another random app to hide it, it works, but it reset after every reboot, and sometimes I lose root and I need to reeboot again to make it work.

Thanks

You provide no logs, no information regarding your device or its current setup...

Not sure what you expect anyone to suggest?

Sent from my OnePlus 3T using XDA Labs
 

Gygun

Senior Member
Mar 13, 2016
59
32
You provide no logs, no information regarding your device or its current setup...

Not sure what you expect anyone to suggest?

Sent from my OnePlus 3T using XDA Labs

My bad :( It was a Xiaomi Mi Mix 2, with a custom chiron rom. I have the log now but...
I... just reinstalled the manager and now it works. I don't know what to say.
Sorry to wasting your time. I'm so embarrassed right now... Sorry.
 

Paschfire

Senior Member
May 16, 2014
932
812
45
Ottawa
Not to be impatient, but is there any word on when this might be released? I'm kind of waiting in finishing the majority of my setup until the whole root process is completed in case I need to reflash stock or something.

Thank you!

No ETAs are ever given, its also extremely rude to ask.
So simply learn to be patient and wait for it just like everyone else has too.

Sent from my OnePlus 3T using XDA Labs
 

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,299
1
14,823
Gone
Google Nexus 4
Nexus 6
My last messeges was delete because had a reddit source? OK, i'll post without reddit source to avoid the censorship :confused::
Pokemon GO / PoGO users, after last update, 0.115.3 Niantic can detect MAGISK; we need delete the MAGISK MANAGER FOLDER in STORAGE to hide and be secure (that folder only have the downloaded .zip modules, files not necessary after install it).
So, we can play Pokemon GO without problems after delete it (and need clear Pokemon Go Data if the game detected the folder before we delete it)
Credits: someone in reddit. :highfive:

It was not deleted because of a link to Reddit... It was deleted because it's off topic for the Magisk beta development thread! Simple as that...

Not to be impatient, but is there any word on when this might be released? I'm kind of waiting in finishing the majority of my setup until the whole root process is completed in case I need to reflash stock or something.

Thank you!

You are impatient, and have already been told so by a few people. But, since you are, I suggest you simply install one of the unofficial snapshots that are provided by a few users here in the Magisk forum. That way you'll have the latest code all the time and don't have to wonder when the next official release will be... :good:

I tried moving to Download, it still fails. I don't know why it's in /data. I haven't selected anything there.

I think I remember @topjohnwu adding something to the code that would fix the "Bad system call". You could try an unofficial snapshot if you don't want to wait for an official release.
 

apophis9283

Forum Moderator / Recognized Developer
Staff member
If your post got deleted, its for one of these reasons

off-topic, irrelevant, not the proper thread (see previous reason), did not follow through with the request of logs when reporting an issue , or failing to use the search function.

I remind everyone to please take the time, read the OP and do what is required to post, and to please post in appropriate threads.
 
Last edited:

Wesley_NL

Senior Member
Nov 10, 2010
1,888
255
Rotterdam
ok a logcat from adb logcat

my device , samsung galaxy s9+ sm-g965f G965FXXU2BRG6
stock rom and kernel only root aplied from dr ketan
its just safetynet

hope i done it right
 
Last edited:

Tecalote

Senior Member
Aug 6, 2015
4,116
3,143
61
Leipzig
Huawei Mate 40 Pro
Xiaomi Mi 11 Ultra
New issue on Huawei Phones with OTA Patch: Patch01

@topjohnwu
@Didgeridoohan
New issue on Huawei Phones - Mate 10, Mate 10 Pro, P9 - Huawei roll out a new OTA called: "patch01". In the changelog is some fix mentioned (example: mms...) but the main patch is to disable the possibility of Root.

That means: if someone flash Magisk with TWRP, or flash patched_boot.img to ramdisk and reboot the phone, Phone get stuck on the splash screen: "Your device cannot be trusted..." :)
Only flashing back the original Huawei ramdisk.img helps to boot again to system. But no Root with Magisk is anymore possible.
Downgrade helps (if available, because for some Phones like Mate 10 it is dangerous to downgrade, if the Downgrade Firmware has another Xloader.img... but this is another story)

→ So, for Users of Huawei Phones it is better not to install OTA with Patch01 and disable Systemupdate in /system/app/HwOUC - rename HwOUC.apk to HwOUC.bak

I attach here the patch from Huawei for P9 - may you take a look, thanks :)
 

Attachments

  • PATCH-EVA.zip
    10.8 MB · Views: 148

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,299
1
14,823
Gone
Google Nexus 4
Nexus 6
@topjohnwu
@Didgeridoohan
New issue on Huawei Phones - Mate 10, Mate 10 Pro, P9 - Huawei roll out a new OTA called: "patch01". In the changelog is some fix mentioned (example: mms...) but the main patch is to disable the possibility of Root.

That means: if someone flash Magisk with TWRP, or flash patched_boot.img to ramdisk and reboot the phone, Phone get stuck on the splash screen: "Your device cannot be trusted..." :)
Only flashing back the original Huawei ramdisk.img helps to boot again to system. But no Root with Magisk is anymore possible.
Downgrade helps (if available, because for some Phones like Mate 10 it is dangerous to downgrade, if the Downgrade Firmware has another Xloader.img... but this is another story)

→ So, for Users of Huawei Phones it is better not to install OTA with Patch01 and disable Systemupdate in /system/app/HwOUC - rename HwOUC.apk to HwOUC.bak

I attach here the patch from Huawei for P9 - may you take a look, thanks :)

And this is regardless of dm-verity being disabled?
 

Tecalote

Senior Member
Aug 6, 2015
4,116
3,143
61
Leipzig
Huawei Mate 40 Pro
Xiaomi Mi 11 Ultra
And this is regardless of dm-verity being disabled?

Yes, it is regardless!

@Didgeridoohan
Edit:
I have dm-verity always off (not enabled in Magisk Manager) and I have also avb disabled in /vendor/etc/fstab.ext4.hi.... and fstab.f2fs.hi.... (I have different Huawei devices)

To make the issue clearer here is another summary:
I made a Rebrand Thread for Huawei P9-EVA here: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
The main reason for this is to allow users to unofficially update their device to Android 8 Oreo. Huawei has rolled out the Oreo OTA update in China, but has no plans to release this update outside of China. Although Oreo runs much better on the devices.
To make this possible, root is an important part, otherwise the mobile network will not work on the rebranded devices. Many users were very happy because they can now also use Oreo Treble Roms by the Open Kirin Team.

Okay → Devices rebranded to EVA-AL10 and updated to the official Oreo Firmware b528. With some modification everything is working fine.
→ Yesterday OTA Patch01 was available. I flashed the unmodified original Huawei ramdisk.img, uninstalled Magisk Manager and flashed the original EMUI Recovery. Then I agreed to the OTA update. The update was succesful installed.

After that I flashed the Magisk patched_ramdisk.img again, but the phone did not boot → it booted only with original b528 ramdisk.img
We were three people who tested it. Me and @dkionline and @zgfg We tried everything that came to our mind. → flashing first original ramdisk and kernel.img and booted to system. Then flashing patched ramdisk.img b528 with Magisk 16, Magisk 16.7 with flag "force encryption" and without "force encryption" (related to - if device is with data encrypted or data decrypted)

Flashing TWRP was not a problem, and together with the original Huawei ramdisk.img phone was able to start to system. To get Root again, we must downgraded to b528 without this Patch.
→ The Patch includes a Fix for mms and Fix for gaming (changes a Line in a local.prop) and it includes also a Kernel patch.
Looking back, we should have tested a little more. What we did not test → making dd with TWRP from ramdisk.img after the OTA Patch and then patch the "dump" ramdisk.img with Magisk. → Maybe that would have worked - we do not know it now and I do not feel like reproducing it again. But perhaps @zgfg can try this in a view days (he did not downgrade yet, because he is outside).
With this last test we could say it for sure, if the Kernel patch includes something to make Huawei Phones unbootable together with Magisk.
https://forum.xda-developers.com/showpost.php?p=77424635&postcount=462
And coincidentally I read then in the Mate 10 forum that there also a user (with ALP-L29c636) got an OTA with a Patch01 and similar problem " I got a patch notification so I download it, rebooted and the patch installed (phone booted and I checked version and it was patch1). Cool. So then I rooted using magisk and phone was soft bricked..." : https://forum.xda-developers.com/showpost.php?p=77405758&postcount=256

My first thought was simple, Huawei is now trying to prevent root with this patch01 and much confirms this theory....
→ Bootloader Unlock Site closed
→ TrustSpace is a new App in system which definitely check and disable Root (we had this app disabled and two of us has it deleted in system)
→ Downgrade with unofficial methods become danger for hardbrick, because of two different Xloader.img in the Firmware (Mate 10)
 
Last edited:

georgekav33

Senior Member
Mar 4, 2017
97
31
Xiaomi Mi 5
Magisk on the NXP MX8 AOSP Platform

Hello I am trying to install the Magisk using the patched img approach (no twrp recovery available) on a AOSP Android 8.1 on a development device of NXP MX8M, soon to be the main certified device by Google for Android Things 1.0. This is A/B and treble scheme arm64 device. SELinux was enforcing, and dm-verity enabled.

Concerning Magisk, the stock boot.img is patched successfully (see log attached) but after installing in with fastboot in boot partition, the Magisk is not actually there: files of Magisk in /sbin/ are missing and of course Magisk manager reported it as uninstalled. Tried both with keepverity true and false.
Could it be that the patcher got the wrong partitions as in this device we have much less that the locked down mobiles phones?
Can we enable a more verbose log?


Here is the list of partitions:
Code:
lrwxrwxrwx 1 root root  20 2000-01-01 00:00 boot_a -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root  20 2000-01-01 00:00 boot_b -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root  47 2000-01-01 00:00 bootloader -> /dev/block/platform/30b40000.usdhc/mmcblk0boot0
lrwxrwxrwx 1 root root  21 2000-01-01 00:00 fbmisc -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root  20 2000-01-01 00:00 metadata -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root  20 2000-01-01 00:00 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root  20 2000-01-01 00:00 presistdata -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root  20 2000-01-01 00:00 system_a -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root  20 2000-01-01 00:00 system_b -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root  21 2000-01-01 00:00 userdata -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root  21 2000-01-01 00:00 vbmeta_a -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root  21 2000-01-01 00:00 vbmeta_b -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root  20 2000-01-01 00:00 vendor_a -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root  20 2000-01-01 00:00 vendor_b -> /dev/block/mmcblk0p9

Finally, since we are building the AOSP from sources, is there any guide for modifying directly the ramdisk/boot sources?
 

Attachments

  • install_log_20180823_173415.log
    2.2 KB · Views: 23

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,299
1
14,823
Gone
Google Nexus 4
Nexus 6
Hello I am trying to install the Magisk using the patched img approach (no twrp recovery available) on a AOSP Android 8.1 on a development device of NXP MX8M, soon to be the main certified device by Google for Android Things 1.0. This is A/B and treble scheme arm64 device. SELinux was enforcing, and dm-verity enabled.

Concerning Magisk, the stock boot.img is patched successfully (see log attached) but after installing in with fastboot in boot partition, the Magisk is not actually there: files of Magisk in /sbin/ are missing and of course Magisk manager reported it as uninstalled. Tried both with keepverity true and false.
Could it be that the patcher got the wrong partitions as in this device we have much less that the locked down mobiles phones?
Can we enable a more verbose log?


Here is the list of partitions:
*snip*

Finally, since we are building the AOSP from sources, is there any guide for modifying directly the ramdisk/boot sources?

Is there any kind of information in the Magisk log?
 

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,299
1
14,823
Gone
Google Nexus 4
Nexus 6
The /cache is unfortunately empty, it is like the Magisk daemon is never run.
I am attaching also the logcat of the patching procedure using the app.

I also tried to patch the boot.img with a different device, and the results are the same.

The boot image seems to be patched correctly, but like you say, it doesn't seem like Magisk runs at all. Are you sure you're flashing the patched image to the correct slot?
 
  • Like
Reactions: georgekav33

georgekav33

Senior Member
Mar 4, 2017
97
31
Xiaomi Mi 5
The boot image seems to be patched correctly, but like you say, it doesn't seem like Magisk runs at all. Are you sure you're flashing the patched image to the correct slot?

Indeed that was the first I though.
However looking at the kernel (I have full console log)
Code:
Kernel command line: console=ttymxc0,115200 earlycon=imxuart,0x30860000,115200 init=/init androidboot.console=ttymxc0 consoleblank=0 androidboot.hardware=freescale cma=1536M firmware_class.path=/vendor/firmware  androidboot.soc_type=imx8mq androidboot.storage_type=emmc androidboot.boottime=1BLL:0,1BLE:3898,KL:0,KD:0,AVB:2022,ODT:0,SW:0 androidboot.verifiedbootstate=orange androidboot.slot_suffix=_a dm="1 vroot none ro 1,0 3095928 verity 1 PARTUUID=66b27d57-a91a-4aec-a051-6ad4c0faea45 PARTUUID=66b27d57-a91a-4aec-a051-6ad4c0faea45 4096 4096 386991 386991 sha1 f7c35576e076f77d1224fd20d99e900954645fa8 0ce0b4ede22e3f24178f835743ba80875d089208 10 restart_on_corruption ignore_zero_blocks use_fec_from_device PARTUUID=66b27d57-a91a-4aec-a051-6ad4c0faea45 fec_roots 2 fec_blocks 390040 fec_start 390040" root=/dev/dm-0 androidboot.vbmeta.device=PARTUUID=b43e0c02-3ac4-4814-ba40-822e5e61e2e0 androidboot.vbmeta.avb_version=1.0 androidboot.vbmeta.device_state=unlocked androidboot.vbmeta.hash_alg=sha256 androidboot.vbmeta.size=3008 androidboot.vbmeta.digest=39b9ac7f694e5e548a534e59ebf0309a2994500b07f403fd9cf6b8d9d9d04c10 androidboot.vbmeta.invalidate_on_error=yes androidboot.veritymode=enforcing skip_initramfs
kernel   @ 80080000 (25747968)
ramdisk  @ 84000000 ([B]7083766[/B])
fdt      @ 83000000 (44729)

it nearly agrees with the output size of magisk (the stock is 6838730)
Code:
KERNEL [25747968]
RAMDISK [[B]7083760[/B]]
SECOND [44729]
EXTRA [0]
PAGESIZE [2048]
NAME []

Can it be that the init rc scripts are not configured the same way as expected by Magisk and thus its init method is never run? Is there a guide for porting Magisk? Maybe I can try manually.
 

Wesley_NL

Senior Member
Nov 10, 2010
1,888
255
Rotterdam
Do this log helps to find out safetynet ?

Root sofar works fine but hide pokemon go wont work
 

Attachments

  • magisk_log_20180824_140535.log
    26.6 KB · Views: 29

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,299
1
14,823
Gone
Google Nexus 4
Nexus 6
Indeed that was the first I though.
However looking at the kernel (I have full console log)
Code:
Kernel command line: console=ttymxc0,115200 earlycon=imxuart,0x30860000,115200 init=/init androidboot.console=ttymxc0 consoleblank=0 androidboot.hardware=freescale cma=1536M firmware_class.path=/vendor/firmware  androidboot.soc_type=imx8mq androidboot.storage_type=emmc androidboot.boottime=1BLL:0,1BLE:3898,KL:0,KD:0,AVB:2022,ODT:0,SW:0 androidboot.verifiedbootstate=orange androidboot.slot_suffix=_a dm="1 vroot none ro 1,0 3095928 verity 1 PARTUUID=66b27d57-a91a-4aec-a051-6ad4c0faea45 PARTUUID=66b27d57-a91a-4aec-a051-6ad4c0faea45 4096 4096 386991 386991 sha1 f7c35576e076f77d1224fd20d99e900954645fa8 0ce0b4ede22e3f24178f835743ba80875d089208 10 restart_on_corruption ignore_zero_blocks use_fec_from_device PARTUUID=66b27d57-a91a-4aec-a051-6ad4c0faea45 fec_roots 2 fec_blocks 390040 fec_start 390040" root=/dev/dm-0 androidboot.vbmeta.device=PARTUUID=b43e0c02-3ac4-4814-ba40-822e5e61e2e0 androidboot.vbmeta.avb_version=1.0 androidboot.vbmeta.device_state=unlocked androidboot.vbmeta.hash_alg=sha256 androidboot.vbmeta.size=3008 androidboot.vbmeta.digest=39b9ac7f694e5e548a534e59ebf0309a2994500b07f403fd9cf6b8d9d9d04c10 androidboot.vbmeta.invalidate_on_error=yes androidboot.veritymode=enforcing skip_initramfs
kernel   @ 80080000 (25747968)
ramdisk  @ 84000000 ([B]7083766[/B])
fdt      @ 83000000 (44729)

it nearly agrees with the output size of magisk (the stock is 6838730)
Code:
KERNEL [25747968]
RAMDISK [[B]7083760[/B]]
SECOND [44729]
EXTRA [0]
PAGESIZE [2048]
NAME []

Can it be that the init rc scripts are not configured the same way as expected by Magisk and thus its init method is never run? Is there a guide for porting Magisk? Maybe I can try manually.

I have absolutely no clue... :D I'm gonna link this to some people that actually know what they're talking about. Let's hope they have some idea...

Do this log helps to find out safetynet ?

Root sofar works fine but hide pokemon go wont work

That has absolutely nothing to do with Magisk beta discussion... Please keep Pokemon queries in the dedicated Pokemon Go thread: https://forum.xda-developers.com/apps/magisk/discussion-pokemon-magisk-discussion-t3465722
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 1775
    Hello, welcome to the beta Magisk thread! First check the main thread before starting.
    I expect users reporting to at least have basic debug skills, this thread is heavily moderated so refrain from spamming with "useless" reports!


    Latest Magisk Beta: v16.7 (code: 1671)
    Bundled Magisk Manager: v5.8.3

    Release Note | Changelogs | Download

    If you need a clean start, use the uninstaller in the main thread to uninstall any verison of Magisk installation

    Symptoms and Diagnose Procedure:
    • Installing Magisk fails:
      If you're flashing in TWRP: Upload the recovery logs (pull the file /tmp/recovery.log, or select "Advanced > Copy Log" and upload)
      If you're installing in MagiskManager: Choose to save logs after installation and upload
    • I want to report a Magisk bug:
      Magisk logs are placed in /cache/magisk.log
      If you face any issue, please upload /cache/magisk.log
      Starting from v16.6, /data/adb/magisk_debug.log is NOT USED anymore!
    • Magisk Manager is crashing:
      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:
      If it worked in previous versions, please at least upload /cache/magisk.log
      Please do NOT SPAM the forum with these kind of issues! It is NOT a priority to fix
    Donation
    I spent endless hours to create Magisk. If you like my work, feel free to donate.
    https://www.paypal.me/topjohnwu
    428
    New Stable Release Coming In a Few Hours!
    Thanks for everyone involved in testing the brand new Magisk and provide useful information for me to fix the bugs :)

    And here I give the moderators a sincere respect, please accept my highest appreciation!
    Everyone on the Internet has a real life, not only me but also the moderators. It's very heartwarming to see them willing to sacrifice their time just to give me a better time on the forums.
    I cannot be more grateful, so thanks to all of you again :good:

    Thread will be temporarily closed until a next beta is available, all future releases (except quick hotfixes) should go through a beta stage before directly going to the masses.
    229
    2017.8.13 Magisk v13.5 (1350)(beta)
    Here comes another public beta!
    As most of you should know, Magisk is a fairly young project, and only recently does it undergo a complete rewrite on v13, so I place stability and compatibility first before I kept adding more features into it. This release comes with several major under-the-hood changes, both in native Magisk and Magisk Manager sides.

    Busybox Fights Back Strong
    Previously I had completely removed busybox from Magisk for causing too many troubles, and also the difficulty to build it myself. But after dealing with so many compatibility issues, and the need of reliable and feature packed command-line tools pushed me to add this gem back. I spent quite a lot of time integrating busybox sources into Magisk's building system, and believe me this isn't an easy task: busybox's config is based on Linux kernel, which itself is a complex topic. I created a tool (ndk-busybox-kitchen) to automatically handle the generation of config-based headers, and parse those files into Android.mk to support building with ndk-build command. To be honest this is super dope IMO, and I'm really proud of it lol.

    The next effort is to maximize compatibility for the Magisk installation process. I decided instead of adding busybox directly into the flashable zip, I would directly embed busybox into update-binary, which is now a specially crafted shell script to dump the correct binary for the CPU architecture, and then execute the installation process completely on the busybox's shell and command-line tools. The extracted busybox will also be utilized in many other places such as boot scripts (yes, the boot scripts will now run in a complete busybox environment) and Magisk Manager. The busybox binary will be installed only for internal use, if you want to install busybox to your device, @osm0sis already uploaded a Magisk Module on the repo, please install that instead.

    Finalizing Magisk Procedures
    Magisk hijacks specific points in the boot process, and will go through its own procedures to fulfill all the features. The order of these procedures are now be finalized, which means it is very less likely to change in the future. For post-fs-data mode, general scripts (scripts under post-fs-data.d) and modules scripts (post-fs-data.sh in each module) are executed before magic mount happens. This means experienced developers can now customize magic mount's behavior to a certain degree. However, I still suggest that most scripts should be run in service mode unless necessary such as time critical commands. Service mode will guarantee SELinux patches are finished, and setting props with proper init triggers will not block the device's boot or lead to a crash.

    Samsung Stock Kernel Workarounds
    Well, apparently Samsung is always here to break everything. On stock kernels, it places a restriction on how binaries can behave if they are executed from /data. An additional magisk binary mirror is created to overcome this issue, and will be used extensively in Magisk Manager (it will not effect recovery). Unfortunately, even though I had offloaded most of the functionality into a shell script function collection that can be upgraded through Magisk updates, the template itself still has to be slightly updated to reflect the changes. Magisk Module Template v5 is already live on another branch. However, before you go and upgrade all your modules to v5, please think twice and consider it as a Developer Preview. It depends on the updated util_functions.sh in this beta, so if you upgrade them into the Online Repo, your module won't install on users running the latest stable Magisk version (v13.3). It will be the default template version once the next stable release is live.

    A Small Mistake
    There was a small mistake in v13.3, which the SHA1 of the stock image cannot be acquired, and also the SHA1 backed up within ramdisk is also not extracted. This leads to stock boot image restoration (happens when uninstalling) fails, and will only revert your device by ramdisk backups. This mean you will be able remove Magisk, but the boot image will not be 100% reverted. If you are concern about the backups, restore your boot image back to stock, and reflash this current build to re-create the Magisk's stock boot image backup.
    227
    Beta releases are no longer "development oriented", this thread will be closed and replaced with a more "experimental channel" thread.
    Thank you to all reported useful logs and info, and I highly appreciate all moderators involved in moderating this thread extensively.