[Discussion] Magisk Alpha (Public Released) fork - @vvb2060

Search This thread
By:
Advanced…
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,729
Google Pixel 8 Pro
huskydg said:
Magisk Alpha has implemented appcenter tracker, include commits that are not merged into official Magisk and more unstable than Magisk Canary/Debug.
If you want MagiskHide, you can use my build instead: http://github.com/huskydg/magisk-files
Click to expand...
Click to collapse
Suggestion
Create a Discussion Magisk Custom HuskyDG Fork thread , or Magisk Custom HuskyDG Fork / Discussion Thread. There are a lot of XDA Members that liked using MagiskHide and some of them have Android 9/10 devices. The XDA members with Android 9 / 10 devices would appreciate having a Magisk Custom HuskyDG Fork discussion thread.
 
Last edited:
  • Like
Reactions: zgfg
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,729
Google Pixel 8 Pro
shoey63 said:
Why not make this the discussion thread for ALL Magisk forks?
At any rate there is always ┤Mod Edit├┤Telegram link removed as it does not meet posting requirements├ for Husky DG Magisk Delta
Click to expand...
Click to collapse
Nope! @huskydg's App makes MagiskHide available for most devices. It is perfect for older devices that are still using Android 9 and 10. AFAIK, the alpha fork does does not support Android 9 and 10. Additionally, there are several XDA Member that do not use Telegram. They rely on XDA for help with their devices. Further, huskydg not only post his information on XDA but also responds to questions on XDA. Finally, a Magisk Delta huskydg Fork thread would provide a place where XDA Members that do not use Telegram can ask specific questions pertaining to his fork rather than posting them on the Magisk General Support / Discussion thread, [Discussion] Magisk - The Age of Zygisk thread, etc., that were not created for huskydg Magisk Delta fork.
 
Last edited by a moderator:
  • Like
Reactions: rodken
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,729
Google Pixel 8 Pro
"...Magic alpha
Telemetry data public
https://openapi.appcenter.ms
owner_name vvb2060
app_name Magisk X-API-Token
34e45ff8c41acb07f58cdb271454e85c80622f11

A question was asked about GDPR compliance for telemetry, since no personal information that could identify a user is collected or correlated, GDPR Articles 15 to 20 do not apply. This can be confirmed via the source code tarball or the public query API.


This information is issued in fulfillment of a notification obligation.

Art. 11 GDPR – Processing which does not require identification - General Data Protection Regulation (GDPR)

If the purposes for which a controller processes personal data do not or do no longer require the identification of a data subject by the controller, the controller shall not be obliged to maintain, acquire or process additional information in order to identify the data subject for the sole...
gdpr-info.eu gdpr-info.eu
General Data Protection Regulation (GDPR)
Art. 11 GDPR – Processing which does not require identification - General Data Protection Regulation (GDPR)

If the purposes for which a controller processes personal data do not or do no longer require the identification of a data subject by the controller, the controller shall not be obliged to maintain, acquire or process additional information in order to identify…"
 
Last edited:
  • Like
Reactions: rodken and Eng.Raman
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,729
Google Pixel 8 Pro
alpha changelog
Magisk (4eb71830-alpha)
- [App] Delete backup file after restoring boot image
- [App] Built-in current version update log
- [General] no longer automatically unlock device blocks
- [App] Add telemetry ┤Mod Edit├┤Telegram link removed as it does not meet posting requirements├
- [App] Allow loading zygisk modules
- [MagiskInit] Fix stub cpio's missing folder caused the failure to boot
- [App] Reduce file size

How to install? Magisk is installed and uninstalled through the Magisk application. Generally, it should be done directly in the application. In special cases such as the first installation, the image should be patched and then flashed using the fastboot/odin tool. By customizing Recovery is not a supported way.

Upstream changelog
v25.1
- [MagiskBoot] Fix ramdisk backup being incorrectly skipped
- [MagiskBoot] Add new feature to detect unsupported dtb and abort during installation
- [Zygisk] Change binary hijack paths
- [App] Fix incorrect recovery mode detection and installation
- [MagiskInit] Fix config not properly exported in legacy SAR devices
- [General] Enforce the Magisk app to always match or be newer than `magiskd`
 
Last edited by a moderator:
  • Like
Reactions: rodken and dr4go
P

pndwal

Senior Member
Jun 23, 2016
7,795
9,617
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
Latest Unofficial vvb2060 Alpha Magisk build (Chinese translated):

# alpha changelog

## Magisk (0b26882f-alpha)
- [App] Delete backup file after restoring boot image
- [App] Built-in current version update log
- [General] no longer automatically unlock device blocks
- [App] Add telemetry... (Replaced this line excluding link after mod edit; please see following posts...)
- [App] Allow loading zygisk modules
- [MagiskInit] Fix stub cpio's missing folder caused the failure to boot
- [App] Reduce file size
- [App]Fixed that the app cannot be updated when Magisk is not installed
- [General] Fix devices that do not support encryption cannot load modules
- [MagiskInit] Fixed Android 13 GKI not rebooting into recovery mode

# Upstream changelog

##v25.1

- [MagiskBoot] Fix ramdisk backup being incorrectly skipped
- [MagiskBoot] Add new feature to detect unsupported dtb and abort during installation
- [Zygisk] Change binary hijack paths
- [App] Fix incorrect recovery mode detection and installation
- [MagiskInit] Fix config not properly exported in legacy SAR devices
- [General] Enforce the Magisk app to always match or be newer than `magiskd`

👀 PW
 
Last edited:
  • Like
Reactions: rodken, Homeboy76, dr4go and 1 other person
P

pndwal

Senior Member
Jun 23, 2016
7,795
9,617
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
To mod / mods concerned (+ Stephen)
Re this:
IMG_20220702_155955.jpg


This particular link complies with the posting requirements given (as well at recent clarifications I read), namely:
We will allow links to messages on Telegram and/or other platforms anywhere, as long as they provide content for a discussion, question, or is pertinent news. This is exactly like the guidelines for YouTube links.
Click to expand...
Click to collapse
https://xdaforums.com/t/device-forum-rules-please-read-before-posting.3333345/post-79278325

It simply provides context and pertinent details re. Alpha telemetry data collection and MS Appcenter usage for those interested in / concerned about the [App] Add telemetry change. (Nb. There is much distrust of telemetry / Appcerter, and disallowing proper details is only perpetuating the myths surrounding such data collection and nefarious intent of Devs, etc... vvb2060 no doubt links such information to head off such misinformation currently circulating even in GitHub PRs...)

Nb. This contains NO download links and doesn't require registration to access linked information. Moreover this XDA thread is not a Development thread, and other caveats listed do not apply either...

Clearly, other messages in that TG thread contain download links and would be an issue for XDA, but this one complies fully... As such, it appears again in the Alpha changelog given above...

Respectfully, PW
 
Last edited:
  • Like
Reactions: dr4go and 73sydney
P

pndwal

Senior Member
Jun 23, 2016
7,795
9,617
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
Last edited:
  • Like
Reactions: 73sydney
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,729
Google Pixel 8 Pro
# alpha changelog

## Magisk (c97d1044-alpha)
- [App] Delete backup file after restoring boot image
- [App] Built-in current version update log
- [General] no longer automatically unlock device blocks
- [App] Add telemetry - Telegram link removed as it does not meet posting requirements
- [App] Allow loading zygisk modules
- [General] Update to official NDK 25, remove rust # Upstream changelog

## Magisk (f42c089b) (25102)
- [MagiskInit] Fix a potential issue when stub cpio is used
- [MagiskInit] Fix reboot to recovery when stub cpio is used
- [General] Better data encryption detection
- [General] Move the whole logging infrastructure into Rust

## Diffs to v25.1
- [MagiskInit] Fix a potential issue when stub cpio is used
- [MagiskInit] Fix reboot to recovery when stub cpio is used
- [General] Better data encryption detection
- [General] Move the whole logging infrastructure into Rust
 
  • Like
Reactions: dr4go and rodken
huskydg

huskydg

Senior Member
Feb 17, 2021
430
553
Magisk alpha said:
The new version of Magisk Lite has been developed, based on v25.2.
Relying on logcat, installation of devices with abnormal log systems is prohibited.
Removed Zygisk functionality. Module functionality is not supported and most modules are expected to break the system.
Remove the function of hiding apps, there is no need to hide apps, just uninstall them directly.
Internal testing, not public release.
Click to expand...
Click to collapse
 
  • Like
Reactions: dr4go and Homeboy76
P

pndwal

Senior Member
Jun 23, 2016
7,795
9,617
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
rodken said:
@huskydg Theoretically, does this replace Alpha in its entirety?
Click to expand...
Click to collapse
No!...

Lite is a completely different animal, and only for mavericks/ those testing/ desperate to hide difficult root traces (especially isolated process leaks etc) from bank apps and willing to sacrifice many (most?) modules (although some will work) for Lites whitelist-mode hiding... PW
 
  • Like
Reactions: 73sydney, Homeboy76 and rodken
huskydg

huskydg

Senior Member
Feb 17, 2021
430
553
magisk alpha and lite is now closed source and you can only download it from Telegram channel
 
Last edited:
  • Like
Reactions: Homeboy76
You must log in or register to reply here.

Similar threads

T
  • Sticky
Magisk General Support / Discussion
Replies
58K
Views
6M
P
pndwal
T
  • Locked
  • Sticky
Magisk - The Magic Mask for Android
Replies
56
Views
6M
T
topjohnwu
T
  • Locked
[CLOSED][BETA][2018.7.19] Magisk v16.7 (1671)
Replies
7K
Views
3M
T
topjohnwu
yochananmarqos
Collection of Magisk Modules v2
Replies
1K
Views
1M
あなたの
あなたの
Heisenberg
[Discussion] PokeMon Go Magisk Discussion Thread
Replies
5K
Views
649K
beneditodragon
beneditodragon

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 4
    rodken
    rodken
    Verbatim from the developer(s) of Magisk Alpha:

    magisk may lead to leakage of device unique identifiers

    Affected versions: All versions before 27.0, and under special circumstances all versions after 27003 Affected devices: Android11 and higher devices

    Details

    Starting from Android 11, the system restricts user applications from using netlink's RTM_GETLINK to read the network card mac address. This is achieved by customizing SELinux to add flag bits. This modification is rejected by Linux upstream and is an Android-specific modification.
    Prior to 27.0, magisk used the upstream libselinux library, so this Android-specific flag was lost when patching sepolicy, resulting in the restriction not being enabled properly and any application being able to read the mac address.
    After 27.0, magisk enables restrictions unconditionally for all devices. However, some devices that have been upgraded to new kernels support processing this flag, but the sepolicy in the user space is not ready, causing all processes to be restricted. The intuitive manifestation is that they cannot connect to WiFi.
    Starting from 27003, magisk parses the flag of the old sepolicy and copies it to the new sepolicy, and the original problem is solved.

    Magisk's sepolicy real-time patching function reads the current sepolicy from the kernel and reloads the sepolicy after patching the rules. Due to bugs in the kernel, Android-specific flags will not be reported to user space, and the current sepolicy read by magisk will never have this specific flag. So after sepolicy was patched in real time, the restriction was disabled and all applications could read the mac address.
    This kernel bug can be fixed using https://android-review.googlesource.com/c/kernel/common/+/3009995 , but for unknown reasons Google requested that the patch be submitted to Linux upstream, and then it was said that this Android-specific bug should be deleted. Function. In short, the patch is currently refused to be merged by Google, and there is nothing we can do about it. Compared with being unable to connect to WiFi, it is acceptable to leak the mac address after patching the sepolicy in real time.

    Utilization

    We observed that popular apps are using RTM_GETLINK to obtain the device mac address. At least one app detects magisk by determining that Android 11+ devices can still read mac addresses.

    suggestion

    Devices prior to Android 11 are not affected. Other devices should be upgraded to magisk 27.0. If WiFi is not available, upgrade to 27003. When using 27003+, do not use sepolicy live patching, check all modules and root applications and ask their developers to switch to sepolicy.rule.

    Related Links

    magisk causes mac address to leak https://github.com/topjohnwu/Magisk/issues/7636
    magisk breaks WiFi https://github.com/topjohnwu/Magisk/issues/7764
    magisk copies Android specific flags to new sepolicy https://github.com/topjohnwu/selinux/commit/48fcf8bba0635dc597bef75994294fd055d9f0ba
    Implementation of Android-specific flags in the kernel (only the policydb_read() function is processed, and the policydb_write() function is forgotten)https://android.googlesource.com/ke...dacce6fbc6fchttps://android.googlesource.com/ kernel/common/+/bdf56fbea560eea1e9c2793d69ba13cca2596d7d
    Kernel repair patch, processing policydb_write() function https://android-review.googlesource.com/c/kernel/common/+/3009995

    Acknowledgments

    aviraxp     https://t.me/qianqianzhuang/33
    View
    1
    rodken
    rodken
    HippoMan said:
    I don't know anything about "sepolicy live patching", and I therefore don't know whether or not it's in use on my device. Can someone point me to some docs about how I can check that?
    Click to expand...
    Click to collapse
    The last time that I checked, SEPolicy live patching is not a widely advertised feature and might not be explicitly mentioned in device settings or documentation due to the fact that it's integrated within one's kernel, which isn't typically user-accessible.

    You can try:
    Code: 
    adb shell logcat -b kernel -b security
    Look for keywords or phrases that might indicate live patching activity.
    sepolicy
    livepatch
    security patch - (could be a generic term)
    View
    1
    HippoMan
    HippoMan
    rodken said:
    The last time that I checked, SEPolicy live patching is not a widely advertised feature and might not be explicitly mentioned in device settings or documentation due to the fact that it's integrated within one's kernel, which isn't typically user-accessible.

    You can try:
    Code: 
    adb shell logcat -b kernel -b security
    Look for keywords or phrases that might indicate live patching activity.
    sepolicy
    livepatch
    security patch - (could be a generic term)
    Click to expand...
    Click to collapse

    Thank you!

    I ran the following:

    adb shell logcat -b kernel -b security | egrep -i '(sepolicy|livepatch|security\s*patch)'

    ... and I then ran a number of apps on my phone. Nothing at all has been printed from the egrep-filtered logcat output, even though I've been running for around 5 monutes. I therefore assume that it would indeed be safe for me to upgrade to Alpha 27003 (at least w/r/t SEpolicy) ... correct?

    PS: 27003 is not yet being offered as an update from within the Alpha manager, so I would just wait until it shows up.
    View
    1
    HippoMan
    HippoMan
    rodken said:
    The lack of output from your egrep-filtered logcat doesn't necessarily guarantee a safe upgrade to Alpha 27003 regarding SEPolicy even though it's still under development as of this writing. Bear in mind, SEPolicy violations or live patching events might not always generate messages containing those exact keywords.

    On the other hand, it's possible that the apps that you ran might not have triggered any SEPolicy checks or live patching activities because it's possible that they don't interact with system components in a way that would require such mechanisms.
    Click to expand...
    Click to collapse

    OK. Thank you!

    I'll hold off on 27003 until I find out more about the SEPolicy conventions on my device.
    View
  • 22
    H
    Homeboy76

    This is the spot for the General Support Discussion of Magisk Alpha "Public Released" fork created by @vvb2060.

    Disclaimer    : This Magisk Alpha fork is not supported by @topjohnwu and is not an official channel for him. Use at your own risk.

    Important : This Magisk Alpha thread was created to share information about Magisk Alpha Public Releases with XDA members that do not use telegram.

    If Magisk Alpha doesn't work for you try one of the other versions of Magisk (See Useful links below).

    How to install Magisk Alpha?
    Magisk Alpha is installed and uninstalled through the Magisk application (App). Generally, it should be done directly in the application. In special cases such as the first installation, the image should be patched and then flashed using the fastboot/odin tool. By customizing Recovery is not a supported way.

    Detailed Instructions for the first installation of Magisk Alpha on Google™ Pixel™ phones.

    Note: These Instructions may not apply to all Google™ Pixel™ Phones.
    1. If you have another version of Magisk (Beta/Stable [Forks - Cygisk/Delta] Stable) installed:
      • Open the Magisk Manager app and disable/remove all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
        If you gave it a different name and you've forgotten the name. Use TB checker to find the name of the hidden Magisk Manager. You can also use TB Checker to check if you have more than one Magisk Manager app installed.
      • Uninstall Magisk
    2. Extract boot/init_boot.img from Factory Image
      • Download the latest Factory image to your phone.
      • Extract the Factory Image file (aaaaaaa-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
      • Open the folder you extracted the Factory image to and, extract the Image file (image-aaaaaaa-aa9a.999999.999.zip) into the folder. The, stock, boot/init_boot.img file will be in this folder.
    3. Patch the boot/init_boot.img.
      • Download the latest version of Magisk Alpha
      • Install the Magisk Alpha App
      • Open Magisk Alpha App
      • Tap Install (next to Magisk)
      • Tap, Select and Patch a File
      • Navigate to the folder that you extracted the Stock boot/init_boot.img to and select it.
      • Tap the ✓ (Check Mark)
      • Tap Let's Go
      • When you see done, the boot/init_boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
      • Reboot
      • Move the patched boot/init_boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
        1. Copy it to a USB drive and transfer it to your computer.
        2. Move it to your computer using adb push
      • Boot fastboot mode
      • Connect the phone to the Computer with USB cord.
      • Open a Command Prompt in the folder you copied the patched boot.img to.
      • Type fastboot flash boot --slot all "name of patched boot".img or fastboot flash init_boot --slot all "name of patched boot".img without the quotation marks at the Prompt and press enter.
      • When it finishes installing the patched boot.img or init_boot.img, type fastboot reboot at the Prompt and press enter.
      • Important Notes:If your phone boot loops try one of the following options:
        1. Flash the 'stock' boot/init_boot.img to both slots: fastboot flash boot/init_boot --slot all boot/init_boot.img. Then reboot , that will remove root.
        2. Boot Safe Mode[/URL] - While booting, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode. Then reboot and magisk modules should be disabled. (Thanks Lughnasadh)

    Changing/Downgrading Magisk?

    Useful Links
    1. Androidacy - Module Manager
    2. Androidacy - Module Manager - Releases
    3. Androidacy - Download Center
    4. Magisk alpha
    5. Magisk Beta - 26.4 - 5 Nov
    6. Magisk Canary - Latest release
    7. Magisk Cygisk - Click Page 5 for installation Instructions.
    8. Kitsune Mask Another unofficial mask of Magisk (previously referred to as Magisk Delta)
    9. Magisk Stable - 26.4 - 5 Nov
    10. Magisk - Documentation
    11. LSPosed - Framework
    12. LSPosed - Releases
    13. LSPosed - Shamiko Releases
    14. SafetyNet - osm0sis Play Integrity Fork - Latest version installation

      Install osm0sis PlayIntegrityFork module
      • Open Magisk
      • Tap Modules icon
      • Tap Install from storage
      • Navigate to the osm0sis PlayIntegrityFork file you downloaded.
      • Tap the osm0sis PlayIntegrityFork file.
      • When you see the confirmation screen, tap Ok.
      • After it installs tap the Disc icon to save the log
      • Tap Reboot
      Settings for Magisk
      • Open Magisk App
      • Tap the Setup icon.
      • Scroll down to App and set the Update Channel to Alpha.
      • Scroll down to Check Updates and enable it.
      • Scroll down to Magisk and enable Zygisk.
      • Enable Denylist
      • Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
      • (Optional) Scroll down to Superuser and enable Enable Biometric Authentication.
      Get Device Certified
      • Flash the osm0sis PlayIntegrityFork module in Magisk
      • Turn Airplane mode on
      • Open Settings
      • Tap Apps & notifications
      • Tap see all...
      • Tap three dot menu
      • Tap Show system
      • Scroll to Google Wallet/Play Store/Play Services/Netflix/etc.
      • Clear Google Wallet cache (if you have it)
      • Clear Google Play Store cache and data
      • Clear Google Play Services (com.google.android.gms) cache and data (Optionally skip clearing data and wait some time, ~24h, for it to resolve on its own)
      • Clear Netflix cache and data
      • Clear ect. items cache and data
      • Turn Airplane mode Off
      • Reboot
      Check Device Certification
      • Note: If after completeting Get Device Certified your device is not certifed or your device is certified but certain apps (Google Pay, NetFliks, etc.) are not working. Do this to verify you are passing Play Integrity.
        1. Open Google Play Store app
        2. Tap your profile icon (top right corner)
        3. Tap Settings.
        4. Open the About menu
        5. Tap the row labeled Play Store version seven times to unlock developer mode.
        6. Tap the back arrow (upper left corner)
        7. Tap your profile icon (top right corner)
        8. Tap Settings.
        9. Open the General menu
        10. Tap Developer options
        11. Tap Check integrity
        12. If you see Basic Integrity and Device Integrity, you're passing Play integrity.
    View
    8
    P
    pndwal
    malcolmy said:
    The Alpha dev archived the Github repo, thus breaking another very needed repo we use to build our kernels for out devices:

    https://github.com/CruelKernel/samsung-exynos9820

    Anyone know the guy or how to contact him?
    Click to expand...
    Click to collapse
    Not a guy... It was private test fork of vvb2060 (Xue ShanNangong, or Nangong Xueshan), one of the five current main official Magisk Devs... (Only John Wu is Male. 😜)

    I think the mentality has changed somewhat from days when she was happy for it to be an alternative daily use Magisk build and scrupulously made source available either on GitHub or later as associated source code .zip, although it was always meant to be a test-bed for innovations in official Magisk*, and has delivered ground breaking commits... It used to be her personal fork, but seems recent Alpha builds are build from https://github.com/LSPosed/Magisk/commits/ , not public, rather than from her GitHub... You can see the LSP / @yujincheng08 (LoveSy, lovesykun, shanasaimoe, Shana Saimoe) Metagisk test branches where many commits currently originate however and of course if you don't trust Alpha you could fork a Metagisk test branch and build from source yourself... Eg for current WIP native bridge loaded Zygisk (with PR in official Magisk also from this Metagisk branch), see:
    https://github.com/LSPosed/Metagisk/commits/zygisk

    * Nb. vv's prolific contributions to Magisk over the last 3 years or so probably make up a good half of the current Magisk code and include so many early tests and first available builds adding compatibility for countless devices Incl. most MTK based devices & fixes... She has developed some initial fixes and enhancements in other test branches like Lite (for enhanced root detection bypasses) and MTK (for MediaTek compatibility fixes), but most have been tested in Alpha experimental branch. Just to mention a sampling I posted a couple of years ago: MTK compatibility, single package delivery, support for 64bit, sepolicy fixes, several isolated process fixes, fixes for UID, MicroG, process names, file based encryption, mount rules for Samsung, auto-close issues bot, reboot menu, multi-user and shared user id compatibility fixes, hidden apps, Chinese doc translations, offline restore app, unsupported environment checking, fix for apex path (a big one), permission fixes, module Installation fixes, Kotlin code cleanup, MagiskHide stopping fix, renameable App / single package Magisk archive (developed in cooperation with John).... And countless more recent commits for various devices/compatibility, new functionality and major refactoring of magiskinit injection, sepolicy rules and so on.

    The mentality now seems to be to use a smaller test group (of course Alpha now uses MS App Centre both for telemetry to facilitate debugging and testing in a test pool mainly aimed at Devs and testers in the Chinese TG Alpha discussion group, many of whom contribute to LSPosed and associated projects, and for distribution/updates; App Centre allows mainland China users to get the automated updates since GitHub repos are apparently blocked for them) who are OK with telemetry (Devs received very negative responses about that from outsiders) and who simply trust the LSP associated Devs rather than to continue to supply source and accommodate the wants of 'needy' users any longer...

    Notably, the Alpha builds are often available privately for days or weeks in the private discussion group (some 940 members) before they are forwarded to the public Alpha TG release channel (circa 33000 subscribers) which just seems to exist now to allow others to access it also if they wish... Of course if Canary is "cutting edge" Magisk, Alpha is "bleeding edge", and Devs are simply not going to accommodate users with issues who don't know how to rescue devices from bad builds, revert changes, downgrade etc even within the discussion group... It's for testers and mavericks after all, not a substitute Magisk fork for general users' daily use, and was never meant to be...

    malcolmy said:
    I can't build a kernel now with the latest Magisk Alpha.
    Click to expand...
    Click to collapse
    Do you mean a pre-rooted kernel / ROM?... Not sure why you want to do that... In my experience these often cause more issues/headaches for users than clean ROMs...

    🤠 PW
    View
    7
    WhoIsJohnGalt1979
    WhoIsJohnGalt1979
    This is my dumbed down version of this post https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/post-88851739 two pages back, which allowed me to transition from Stable Magisk to Alpha without having to reflash any modules etc.
    1. Put the phone in airplane mode.
    2. If you have hidden current magisk, unhide it.
    3. Rename alpha.apk to alpha.zip
    4. Flash alpha.zip with current magisk. Don't reboot.
    5. Delete the magisk folder from data-adb. Also remove magisk.db file from the same location.
    6. Uninstall the current magisk application which you had unhidden in step 2.
    7. Reboot
    8. Remove airplane mode to complete magisk installation
    9. You would be prompted to reboot when you enter the new magisk alpha app. Do that. Once rebooted, open Magisk and do a direct installation to be doubly sure that magisk is properly installed with root.
    10. Make sure that in all this process do no open play store or any of the applications that you had in Deny list.
    11. You will find that all the apps in deny list would be unchecked. Re-check the same applications once again
    12 Reboot
    13 Profit
    View
    7
    huskydg
    huskydg
    Reversed
    View
    6
    mlgmxyysd
    mlgmxyysd
    The author of Magisk Alpha is extremely untrustworthy. It is highly recommended to use the official version.
    View

New posts