yashsingh1/xdaforums huggingface dataset:
[Magisk] droidzer1:
I've searched this thread and not having the ability to read all 42000+ posts I apologize if this has been covered somewhere.

I get 'Installation failed' when Magisk v8.0.2(307) tries to install beta 21.000.

Magisk log file:

- Device platform: arm64-v8a

!Process error

!Installation failed

Developer options are enabled, OEM bootloader unlocked in developer options, USB debuggin On. On Android 10 in MTK device.

Can't seem to find any basic reason for the failure but new to Android 10 version so I'm probably missing something obvious...
[Magisk] pndwal:
Please say what phone model, ROM (custom / stock), ROM device shipped with, and status in Magisk Manager for A/B, Ramdisk, SAR for specific help.

I do know there were recent issues acknowledged by John Wu w/ Magisk and MTK devices in general... PW

Edit: Here it is:

https://github.com/topjohnwu/Magisk/issues/3042

Seems it's still a current known issue...
[Magisk] droidzer1:
Kospet Prime 2, stock ROM, v1.4 Rom (latest)

Ramdisk yes

A/B no

SAR yes

Manager is 8.0.2 (307)

tried latest Beta 21.000 and latest stable 20.4
[Magisk] DiamondJohn:
be sure to distinguish between magisk and magisk manager app.
[Magisk] pndwal:
Ah, Smart watch! I recall some had special difficulties with wearables and MagiskSU root.

Apart from that, it's likely your device is incompatible due to MTK MagiskInit Incompatibility issue I cited above: May need to watch this issue / Magisk changelogs for fix.

Also, it appears this device shipped with Android 10, so I'm assuming TWRP will be incompatible as TWRP was only ever made compatible with devices upgraded to 10, not having newer Logical / Dynamic file structure yours should have.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83725859

This means Patch Image installation method will be necessary, and should be flashed using adb fastboot (which you are most likely doing), and TWRP shouldn't be flashed (stock recovery retained), even if someone has produced an unofficial one for device.

This new file structure is also causing headaches for John's Magisk development, and seems the options available differ between QCom and MTek based devices:

https://mobile.twitter.com/topjohnwu/status/1323014048468754432

Sorry rooting prospects don't look good for you at present. :( PW
[Magisk] EriksR:
Should I update from Magisk Manager 7.5.1 if I have Android 7?
[Magisk] guest4711:
As long as all is well no need to update - never change a running system ;)
[Magisk] EriksR:
Yeah I agree. My suspicion sense is tingling with a big update that's meant for newer devices. But sometimes it's tough to resist updating everything.
[Magisk] cnjax:
You can find help by joining a local flashaholic anonymous group
[Magisk] droidzer1:
Thanks for all the info pndwal! Yeah things are looking sucky for A 10. I also can't get mobile data working on this watch due to being unable to edit APN settings. I know what the APN needs to be for this SIM and area but it defaults to something which does not work so I was hoping to get root in order to be able to edit APN config files directly. Tried some supposedly no root APN editors but no luck.
[Magisk] pndwal:
No worries.

Yes, things are not looking good especially for custom recovery on A10+ architecture.

For MagiskSU though, John has pretty much got it licked for such devices. However, there being differences between Qualcomm and MediaTek implementation, it seems he has given priority to Qualcomm platforms. He is, after all, only a team of one working on SU; the team is two if you include Manager.

For MediaTek platforms, Issues like MagiskInit compatibility (known at least since August) and pre-init access to custom sepolicy rules on MTK are, of course, going to take longer to resolve, if only for lack of personnel and time!

I think these are really your issues too, but I'm sure John will solve these / other issues for MTK socs in reasonably short order just because he's always up for a challenge... but that's only my take. :D

Re APNs, can't you edit / add these in Settings, Sims / Mobile Networks as is usually done? PW
[Magisk] lgs9527:
error when patching img

I have magisk manager 8.0.2 installed. I choose magisk - install - seslect and patch a file, then select my boot.img (Redmi K30 5G MIUI12 android 10), then in the installation, it saids:

copying image to cache

process error

installation failed

no patched img is generated under Download folder.

please help.
[Magisk] pndwal:
Does Magisk Manager show Ramdisk: Yes for you? PW
[Magisk] lgs9527:
A/B No

SAR Yes

Ramdisk Yes

Crypto File
[Magisk] LuminousMazim:
Damnit, sorry for oot but i search "flashaholic anonymous group" on google but found entirely different topic.

Almost wakeup my roommate cause of laughter.
[Magisk] pndwal:
... So this should work on boot image... How did you obtain boot.img? ... Also, please check that Magisk Manager is on 'internal' memory. PW
[Magisk] lgs9527:
thanks. I flash another firmware, the one before latest, and magisk generated the patched img this time.
[Magisk] whitehollow:
After installing the latest magisk canary, xposed doesn't load modules. I'm using edxposed canary. I tried to un install xposed and than all the modules, I tried official xposed but the problem is magisk. Anybody know where I can download the previous magisk Canary version?
[Magisk] zgfg:
From Github, Files, you need to look into History and commits - not easy.

Btw, a good practice would be to use a tag for each release, but not used here. The whole distribution of Magisk over Github is set as utterly complicated as possiible, specially for an ordinary Magisk user who is not a programmer well familiar with Github

To not waste the time for searching (not to mention the case if phone would not boot or so), I never update directly but patch the image and keep my image patched by previous Magisk, and if anything goes wrong simply flash that older patched image
[Magisk] whitehollow:
I'm trying and trying to find it but it's a maze. I hope they will fix it with a newer version
[Magisk] fobtob387:
Any idea how to fix this? Haven't been able to download modules for a few days now, can't expand the notification either so not sure what it says after "error".
[Magisk] Didgeridoohan:
Other users with similar issues have experienced this because their hosts file seemingly has been blocking the CDN the Manager uses for downloads. You could test this by restoring the original hosts file and try again.

But, I would very much appreciate if you could send me your hosts file first (/system/etc/hosts). I would love an opportunity to analyse this...
[Magisk] droidzer1:
Oddly I can add and edit the APN settings with a different SIM but can't do any editing or adding with the SIM I need to use in the Prime 2 watch. To further confuse things that SIM which I can't edit APN's in the Prime 2 watch can be edited in the Kospet Prime 1 watch.

SIM A in Prime 1 = editable

SIM B in Prime 1 = editable

SIM A in Prime 2 = editable

SIM B in Prime 2 = not editable

SIM B is the one I need to use. High Strangeness...
[Magisk] fobtob387:
Disabling Systemless Hosts and excluding Magidk in Adguard did the trick, thanks! Can't provide hosts now that I've disabled Systemless hosts, sorry.
[Magisk] guest4711:
Yes, you can. Simply upload /data/adb/modules/hosts/system/etc/hosts
[Magisk] Lord Sithek:
Hi everybody. I have a strange issue on two out of three my devices (Samsung Galaxy Tab S5e and Xiaomi Redmi Note 4). Right now I'm on latest Canary Magisk Manager and I can't update Magisk itself, because Magisk Manager seems to not having access to the internal storage. And I can't grant it manually, since whenever I try to open MM permissions, the Settings app crashes or take me one step back. I'm attaching screenshots of the toast message and MM log, since I can't even save it in the storage because of this issue ? Hope that somebody can help me figure this out. Cheers
[Magisk] J.Michael:
Can you boot without Magisk? Maybe then you could use Android Settings to inspect and change Magisk Manager permissions.

Maybe uninstall Magisk Manager and reinstall.
[Magisk] Lord Sithek:
Finally I understood your point and yes - it worked. Without Magisk installed I was able to grant permission to MM without a problem and successfully update Magisk on both devices. Thanks for your help.

Just weird why MM didn't ask for storage permission at first... ? Never mind though
[Magisk] Lord Sithek:
Interesting that after the update behavior is similar - Android Settings crashes :confused: Fortunately I have storage access now so I can install modules and flash zips
[Magisk] Spartacus500:
Is it possible in the new version of Magisk to rename or hide magisk files? This would solve this with many new applications that detect magisk files in /data/adb/magisk file, and / sbin/.magisk file ?
[Magisk] zgfg:
v21.1 coming ?
[Magisk] palmbeach05:
Its already out lol
[Magisk] wilsonhlacerda:
And with a new Manager.... And bugs: after update (I was in Beta hidden, everything updated fine) can not select update channel, language.

Probably a new update at least to Manager should be released soon.
[Magisk] zgfg:
I have updated Canary, not hidden, and everything works great.

There were similar issues (prior to this release) reported when updating a hidden Manager.

Suggesting to un-hide and then to update a Manager - or to uninstall and then to install the apk:

https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.3/MagiskManager-v8.0.3.apk

https://github.com/topjohnwu/magisk_files/blob/canary/app-debug.apk

You can also try to delete data and cache for the Manager app - it will not affect Magisk data, you will just probably have to re-enable Magisk hide in Manager's settings
[Magisk] wilsonhlacerda:
I did lots of tests now and there's a bug: as soon as language is switched (from system default to another), all the settings options get broken, can not choose anymore.

Clearing cache, data, reinstall, unhide, hide,....nothing solves it. Seems solved at first sight, but as soon as language is switched the bug shows up.

Running Official LOS16 and Manager 8.0.3(314)(14) here , just to mention.

Try switch your language from system default (mine is not English) to another (I switched to English), hit OK, and then try change other settings.

---------- Post added at 01:20 AM ---------- Previous post was at 01:17 AM ----------

If you have some apps examples I think this does deserve to be opened as an issue (improvement) in Magisk Github. Be sure to mention / give links to download apps.
[Magisk] J.Michael:
Several times I have had to crawl into settings to grant an app some storage privilege. Before that, at most I would get an alert asking if I wanted to grant the permission. I can't swear there was an app that behaved one way, then changed to the other, but I thought the way of the world was that, after installing an app, the first time it needed a permission I would get asked.

It's not like this is a change in Android: I haven't allowed my device to update. I'm running Android 9, whatever was on it in December 2019.
[Magisk] Vs995Child:
Question.....does anyone know if v21.1 is compatible for AO 8? I got update for the 8.0.3 manager, but not the 21.1. Just wondering if i should take the leap or leave well enough alone....
[Magisk] pndwal:
Yes it is...

That's because while Magisk Manager (8.0.3) 314 (14) is Public Stable, Magisk(SU) (21.1) 21100 is still public beta... Latest Public Stable is still (20.4)* 20400.

Latest Debug Canary Manager is 315 (14), Debug Canary Magisk(SU) is 21101.

Simply change Update Channel in Magisk Manager to Beta to get Latest Public Beta.

*Nb While 20400 may be the most stable available as Public release, only 21000+ builds are compatible with Android 11. For some, this will be a major factor in deciding whether to 'take the leap' from 20400... Others will simply jump without a thought, just for the thrill! :D ....Of course, if you are speaking of leaping from Public Beta (21.0) 21000, you have nothing really to lose, and many fixes to gain. PW
[Magisk] zgfg:
No problems with languages for me, but different setup (A10, not LOS; Canary, not Beta or Stable hence Manager 315, not 8.0.3; system language English).

Please check issues on Github and report

Please be more specific, AO what (Alpha Omega ROM for LG - guessing from your profile).

Also, which channel are you on - Stable is still on v20.4
[Magisk] Didgeridoohan:
[MENTION=4668495]wilsonhlacerda[/MENTION] John knows about that bug, I have it too... It only seems to happen if you switch to English though. Other languages doesn't seem to be affected. Clearing data for the Manager will get things back to normal.
[Magisk] pndwal:
Latest ChangeLogs:

Magisk Manager

v8.0.3 (314) (14) Stable (public release)

- Switch to the new Magisk Module Repo setup in preparation to allow 3rd party repos

- Add tapjacking protection on Superuser request dialog

- Stability changes and bug fixes

Magisk (SU)

v21.1 (21100) Beta (public release)

(Maintenance update from v21.0)

- [MagiskBoot] Support boot header v3 (Pixel 5 and 4a 5G)

- [MagiskBoot] Distinguish lz4_lg and lz4_legacy (Pixel 5 and 4a 5G)

- [MagiskBoot] Support vendor boot images (for dev, not relevant for Magisk installation)

- [MagiskInit] Support kernel cmdline androidboot.fstab_suffix

- [MagiskInit] Support kernel initialized dm-verity on legacy SAR

- [General] Significantly broaden sepolicy.rule compatibility

- [General] Add Magisk binaries to PATH when executing boot scripts

- [General] Update --remove-modules command implementation

- [General] Make Magisk properly survive after factory reset on Android 11

- [MagiskSU] Add APEX package com.android.i18n to LD_LIBRARY_PATH when linking libsqlite.so

- [MagiskHide] Support hiding apps installed in secondary users (e.g. work profile)

- [MagiskHide] Make zygote detection more robust

Magisk Manager

(1469b82a) (315) (14) Canary (debug)

- Align with public v8.0.3 release

Magisk (SU)

(1469b82a) (21101) Canary (debug)

- Align with public v21.1 release

Thanks [MENTION=4470081]topjohnwu[/MENTION]! :good: PW
[Magisk] Dixietiger:
Is 21.1 now compatible to mtk devices like xiaomi redmi note 8 pro?
[Magisk] wallace108:
I don't think so. My Oukitel wp5 pro (with A10) still is unaffected by Magisk. :crying:
[Magisk] Didgeridoohan:
Do you mean this?

If so, I doubt it since the issue is still open and there was nothing about it in the changelog.
[Magisk] wilsonhlacerda:
Yeah, I've tried to switch to 3 other languages and all was fine. But if I switch to English the bug shows up.

Clearing data resets to system language and everything works as expected, but as soon as switch to English the bug comes again. And only way to get rid of it is clearing data.

What is funny is that this bug only happens to me on current (updated) Manager. I always switched to English on previous versions without any problems.

Thanks for mentioning that I'm not the only one having this bug.
[Magisk] tramp20:
Hi,

I need help updating Magisk from 20.4 to 21.1.

I could update Magisk Manager to 8.0.3 (of course after unhiding it).

But updating Magisk (within Magisk Manager and direct installation) fails with a bootloop during animated boot screen.

Sony Z1c Lineage ROM 17.1 Android 10

RamDisk No

A/B No

SAR Yes

Crypto N/A

Thank you for detailed instructions to solve this.
[Magisk] Rdier:
I have installed magisk and the yest ctsprofile fails. I have installed props config and a terminal program.

I have run the commands to configure the module but it still doesn't work. I have tried a lot of versions of magisk with the same result. Rom 12.0.6,

magisk 20.4 y manager 8.0.3. If i install the version 21.1, it remains in permanent restart.
[Magisk] Clandaries:
Sorry
[Magisk] pndwal:
You haven't said what you configured in MagiskHide Props Config, but you likely need only option to Force BASIC Key Attestation enabled (configured) to pass ctsProfile... May need more if on custom or uncertified (China etc) ROM. :good:

Not sure why 21.1 bootloops for you... PW
[Magisk] pndwal:
This looks very odd to me.

Is this Legacy 2014 Sony Xperia Z1 Compact?... Not sure why Manager shows RamDisk No. Not sure about SAR on a device launching with Jelly Bean either...

If kernel / boot image are actually as they should be, I'm not sure why direct install update is not working, assuming you originally installed using Patching Image method and recovery.img...

https://topjohnwu.github.io/Magisk/install.html

I think it's more likely boot image has been messed up with custom kernels or other modding (unless Magisk is misreporting your setup).

You may want flash stock ROM, or just boot.img extracted from LOS ROM to fix Ramdisk etc (assuming this boot.img is good / not pre-rooted), then check if Ramdisk Yes is reported in Magisk Manager. If Yes, try again using Patching Image w/ boot.img, or legacy Custom Recovery method. PW
[Magisk] tramp20:
Thank you.

Sorry. RamDisk is Yes ofc.

And it is a legacy 2014 model.

1. In /data I found a lot of magisk_backup_xxxxx files with a boot.img in it.

Were does Magisk store the original ROM?

I remember that since 20.4 I could never install a canary :(

2. Can I use the oldest one from 05/2020 to patch or do I have to start over and flash a stock ROM with EMMA?

I have an old Z1c with stock ROM 5.1.1 with CWM and TWRP 3.0.2.0. Can I extract a unpatched ROM?

3. I assume Magisk_uninstaller does not help.

Sorry, that is to complicate for me.
[Magisk] pndwal:
Ah, ok then...

So may be no need for stock if Ramdisk is actually Yes.

Yes, may be able to unroot using Uninstall Magisk in Manager, or run uninstaller from TWRP, or flash boot.img extracted from LOS ROM zip (usually in root of zip). - Magisk doesn't store this. Use original zip archive, or download again.

After unrooting, flash Magisk zip from TWRP, or click Install and patch extracted boot.img in latest Magisk Manager before flashing it using ADB Fastboot from PC. PW
[Magisk] tramp20:
Fine, I will try your tips tomorrow.

Thank you
[Magisk] Mrs. Nesbitt:
Hi, I am absolutely new to this thread, also because I always needed only to flash magisk to get root. Today I had the bad idea to update the Xiaomi.eu on my Mi9t, without knowing that i would get Android 11, also withou knowing that i would have problems with magisk.

Of course after flashing 20.4 i get error just right after splash screen, and phone was keeping rebooting. I tried then with 21.1 Magisk and with magisk manager 1469b82a, and if I try booting system i enter fastboot.

As i said it's my first time coming here, so i would like to get a little accurate answers.

Thanks a lot in advance.
[Magisk] dcarvil:
I don't know anything about your phone, but typically you'd flash the stock boot image from your Android 11 update to get the phone to boot. Then patch that image with Magisk 21.1. Flash the patched image, then you should have root.
[Magisk] J.Michael:
What program is displaying that TOC?

Is that a date between "<DIR>" and "21:03"?
[Magisk] Mrs. Nesbitt:
Is there any guide on how to patch my boot image and how to flash it?
[Magisk] FOREST37:
To install on the Xiaomi Mi A2 Lite - first of all I needed to unlock the bootloader - after that I used a program called payload dumper to extract the boot.img from the firmware update which I downloaded to the PC. I then copied this to the phone and used Magisk Manager to patch this boot.img file, which i then copied back to the PC and used ADB & fastboot command to push the patched boot image to the phone to boot with temporary root and then used Magisk Manager to do a permanent direct install

adb reboot bootloader

fastboot boot magisk_patched.img (the patched image that i copied to my PC into my adb folder)

And then open Magisk Manager to make Magisk installation permanent

Last step to stay safe when a new OTA update arrives: go to "Settings" > "System" > "Developer options" > and disable "Automatic system updates".

When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!

Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk.

Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.

When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".

That's how mine works - but I'm on Android 10 so still using 20.4 Magisk - havent yet tried installing the Canary version

Hope the above is helpful
[Magisk] zgfg:
There is a thread for Mi 9T with Xiaomi.eu in the name, you should have studied that first:

https://xdaforums.com/mi-9t/how-to/xiaomi-eu-android-11-weekly-release-t4180491/

In that thread you can find info:

- how to flash Xiaomi.eu (A11)

- how to root

- and that A11 beta is still not good enough to use.

Suggesting you to better ask further questions there (how to unbrick)

From the name of Xiaomi.eu ROM, you can read is it A10 or A11. If it ends with v12-10 it is A10, if it ends with v12-11 it is A11 - you flashed the one pointing to A11

You flashed Xiaomi eu beta - only them are A11.

But Xiaomi.eu Stable are still A10, latest is 12.0.6, you can find it here:

https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv12/

I'm currently on that ROM, I'm very satisfied

Even fron Xiaomi.eu Weekly, few weeks older version 12.9.17 was still A10:

https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/
[Magisk] dcarvil:
The "Install to Inactive Slot" option is not available in Magisk 21. Until [MENTION=4470081]topjohnwu[/MENTION] can get it working again, you have to flash the magisk_patched.img with fastboot. Also, you may have to reboot after the OTA before flashing the patched image.
[Magisk] Mrs. Nesbitt:
Thanks all for the answer.

Unfortunately today I had a lot of time, do I decided to update my ROM (since July), without knowing that the beta weekly just passed to a11. Of course the ROM as a lot of bugs, but I don't think that those would affect magisk. Reading here and there on the internet there are many devices having problems with root on a11.

I will try to read more, but still I didn't find anything about my ROM.
[Magisk] zgfg:
If you download so-called recovery/zip firrmware (talking about Xiaomi phones like you mentioned), just unzip and there you find boot.img file

If you download so called fastboot/tgz firmware, just ungzip and untar, and there you find boot.img and recovery.img files

There are tons of programs (on the PC or Android) to unzip, ungzip, untar - I prefer MiXPlorer since it is mainly an excellent (root) exolorer for Android, but it can do many other things like coming with an integrated text editor, you can change chroot permissions, you can copy, extract or archive (several GB long files) in background, with its additional packages you can e.g. see meta-data for picture files, etc

---------- Post added at 12:10 AM ---------- Previous post was at 12:00 AM ----------

The thread I gave you is all about Xiaomi.eu ROMs for Mi 9T, particularly devoted to A11 beta ROMs - and you still don't see anything there?!
[Magisk] Mrs. Nesbitt:
Of course I went right there after your comment to read the thread.

Thank you.
[Magisk] zgfg:
Ok, but thread was very visible - second in the Guides section when you open XDA Xiaomi Mi 9T subforum:

https://xdaforums.com/mi-9t
[Magisk] xp99:
This worked for me. In the November 2020 android 11 update for pixel 3a, it started enforcing hardware checks for the safety net check. So this bypasses it.
[Magisk] tramp20:
It is a Windows program "TotalCommander", I use LAN Drive as SMB Server to map root and SDcards to a network drive on Windows.

To the date: you should ask Android developers why they use those dates :)