yashsingh1/xdaforums huggingface dataset:
[Magisk] IzaacJ:
Currently reflashing the whole thing back to stock. Magisk messes up everything when I try to install it, every partition is a wrecked except preloader, which is why I'm able to unbrick it. Will try to install phhs superuser as soon as everything is back up and running.
[Magisk] gleggie:
Where did you find r266hidesu? I can't find it in the main thread
[Magisk] 73sydney:
I literally just got home and from the strands from others from last night knew to abandon installing TWRP

the adb push and adb shell twrp install are just from my usual clean flashing script (im too lazy to do it manually), i just commented out:

adb push twrp /tmp
adb shell install /tmp/twrp

Having run CAT6 cable all day, crimped it and installed Unifi AP's (so people could have their interwebs for Netflix) i was tired and not looking for too much fun this evening :)
[Magisk] pndwal:
Don't know what to think about the longevity of SN pass though.

Apparently Android 11 was forcing Hardware Backed attestation for most (all?) a day ago, but now SN is passing even w/ Hardware EvalType!

John Wu's thoughts:

https://mobile.twitter.com/topjohnwu/status/1303845469798367233 PW
[Magisk] Rumsfield:
On my second Pixel 3, I did the following:

Remove all modules, uninstall magisk. Dirty flash from A10 to A11, install magisk canary. Flash modified boot .img as normal to regain root, no issues. My other phone boot looped only because I did not remove magisk or at least the stupid edge module that has given me nothing but grief.

Good luck.
[Magisk] pndwal:
Notes:

- Freezes in Android 11:

• A number have experienced freezes / instability with 'systemless hosts' enabled / module present in Magisk Manager:

> https://mobile.twitter.com/dave_alive/status/1303683134484025344

> https://mobile.twitter.com/dave_alive/status/1303797810853294083

• I'm unsure if this is related to SU request issues / fixed in latest release, but guess that's likely as John Wu was aware of it.

- Changes in latest Canary builds:

>> Magisk (20425)

• Upstream libsepol to support latest sepolicy binary format

• Use intent + FIFO for communication between Magisk Manager and magiskd for su request. This should fix all su request dialog not showing up issues.

>> Magisk Manager (299)

• Fix su requests auto response

PW
[Magisk] Alxoom33:
Either learn how to fastboot into TWRP or update Magisk into inactive slot as discussed 2 posts above yours. Or lock your bootloader and stay unrooted.
[Magisk] supachris:
Same here with Pixel 3 blueline. After regular OTA update I installed canary MM 298 / 299 and tried rooting of the boot.img as usual with 20425. But after booting the system is laggy and unresponsible and had to hard rebooted. After flashing stock boot.img system is working properly. Unfortunately so no root for now :/
[Magisk] acidspider:
Was having the same.issue with kernel.panics and having to hard reboot,I figured this was when the screen was off so have switched on ambient display so the screen never completely turns off and it solves the problem
[Magisk] supachris:
This seems to be another issue here. It seems like related to modules. I did the following:

Delete all magisk manager data, uninstall ist.

Re-installed lates canary. Patched boot.img and got a widely different patched image. Compared in hex editor to the one I tried.

Flashed this img, and now it works, have root access and system works normally. But I cannot use the systemless hosts module. If I enable it, and reboot the system again is broken.

Again the whole procedure but withot activating systemless hosts and deleted the modules folder after boot with FX root, I can activate AdAway, but after reboot AdAway is inactive and says, it cannot store hosts as there is no space left. Hmm....strange. maybe the systemless hosts module is not working on A11?

Edit:

I overread Posting 41426, sorry. This seems to be a known issue for now.
[Magisk] spiou:
I Can confirm that even with Magisk 20425.

No problem if I disable the systemless hosts module.

So no ad blocker for the moment...

Edit : problem solved. I just upgraded Adaway to 5.08 and the systemless hosts module can be enabled without freeze.
[Magisk] zgfg:
Instead of "the whole procedure" you can try while booting (but it doesn't work on all devices - probably not for Pixels):

> adb wait-for-device shell magisk --remove-modules

(to remove all Magisk modules)

Since the system is read only, AdAway cannot save edited hosts file and it imprecisely reports that there is not enough space

You could use AdAway 5.0.8, supporting non-root virtual VPN method for resolving and blocking domains (does not block ads in Chrome). Same technique like DNS66 (or Blockada)
[Magisk] supachris:
Thanks, I will test it next time. For now I use Blokada as workaround.
[Magisk] zgfg:
For the matter of fact, why nobody (Pixel users) reported yet to GitHub
[Magisk] supachris:
Now done.
[Magisk] pndwal:
Wouldn't know. Pixel users?

Edit: Thanks [MENTION=1901473]supachris[/MENTION]! PW
[Magisk] :
Anyone have a link to a version of Magisk that works on Samsung Tab S - T700?

Samsung Tab S - T700 (8.4) using Lineage 14.1 rom. I need to get rooted. Have tried flashing a few versions of Magisk, and also installing the version from Aurora Store (Playstore).

Nothing works, it always freezes or shuts down or something after install.

Just looking for a version that works, if anyone can help I would be most appreciative.
[Magisk] pndwal:
Download stable Magisk from GitHub:

https://github.com/topjohnwu/Magisk

For John Wu's installation instructions, click the link on same page.

Don't use use versions from elsewhere!

For other files, see here:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82863085 PW
[Magisk] @kitokit:
I tried using magisk canary but failing to pass safety net, but with magisk stable 20.4 it all ok. What could be the problem?
[Magisk] zgfg:
Did you enable Magisk Hide when you installed Canary?

Then, if SafetyNet still falling, use its own SafetyNet check and describe what it says there (without more info, how could somebody help)
[Magisk] pwkaho:
I have a BV9900Pro. Android10.

Patched with MMcanary for rooting.

However, flashing the patched image causes a boot loop.

Original boot.img file size is 33MB.

Patched image file size is 11MB.

Is there a solution?
[Magisk] zgfg:
Stock images are fixed (partition) size, patched are usually smaller

Did you already have root/Magisk and maybe some modules?

If patching boot image, Recovery option must be turned off - double check (flash stock image and you can patch again)
[Magisk] pwkaho:
I understand the difference in file size. Thank you.

I installed only MM immediately after installed the stock ROM.

The module is not installed.

I couldn't find a Recovery option in MMcanary,

so I reinstalled and repatched the stable version of MM.

Recovery option is unchecked.

I got a boot loop...
[Magisk] Rukbat:
I don't see any posts about the Pixel 2 (walleye) (not the XL, the plain 2), so ...

After about 5 tries of bootlooping, I tried going back to A10 today ... and A10 bootlooped before I even tried flashing anything, with a return to stock recovery. So:

A10->A11 normal fastboot flash (but without the 'wipe')

Boot to TWRP, not flash it, just boot to it

Install Magisk 20425 from TWRP

Reboot

Now it's running A11 with Magisk. (I do a few things daily that require root, so an unrooted phone is almost useless.) Canary manager still doesn't give me access to modules, but I'm not really depending on any. (I was depending on MCS, but I'm running the Battery Charge Limit app now, so I don't need MCS.)

And still no working TWRP for walleye. (That's okay, I can boot to it if and when I need it, but it would be nice to be able to do a full nandroid backup.)

All's good, the phone works and I have root access. Now, when is Google going to come up with a Pixel that has something that makes me want to upgrade? (I'm running the latest Camera app, so there's nothing in the 4 that tempts me.)
[Magisk] 73sydney:
As a fellow Pixel person....

I learned the hard way a few days ago that installing TWRP on Android 11 will bootloop on the 2/2XL, you just have to fastboot it when needed to install zips, like Magisk

Also its not possible on TWRP on the 2/2XL to do a full nandroid anyways. You can only backup /data. For me i think whats the point of that and i just use Migrate - which means i can take my apps/app data and app permissions between ROM's, though be warned, when i tested restoring via Migrate on Android 11, it failed to install split apks (something it doesnt have any issues with on -11, and also failed to install app data for the apps it did restore - in fact hosing many apps ability to run without clearing the garbled data), also something it never had issues with before. I had to roll back to Android 10 for this and other 11 related reasons...same Migrate backup restored perfectly, of course. Ordinarily Migrate can even go between major Android versions , but not 11...

Android 11 has some way to go before i upgrade, as do some apps i rely on
[Magisk] xunholyx:
Because it's user error probably. I've had no issues at all with my P2XL running 11 since DP2
[Magisk] Lughnasadh:
You need to use Canary for R. I believe the recovery option was removed last month on devices with ramdisk because it's not needed.
[Magisk] supachris:
I opened an issue. At my Pixel 3 the system freezes even without any installed AdAway after enabling systemless hosts and reboot.
[Magisk] zgfg:
I see there is not much about your device on XDA but one guy claims that he was able to install Magisk:

https://xdaforums.com/showpost.php?p=83265319&postcount=17

He was not satisfied saying it was "systemless root" but that's not the point, it's not limited by Magisk but by Android 10 itself (and even if he succeeded to root by SuperSU, he would not have full read and write access to the system)

Btw, he says that he also had bootloop first because he forgot to unlock Bootloader.

Please double-check did you unlock Bootloader

Maybe you can ask him/there.

If I understand correctly, there is no TWRP for your device and you cannot collect logs from the bootloop to submit to Magisk GitHub
[Magisk] firewave:
Just to let everyone knows, the last canary version works very well on my Pixel 4XL with Android 11, but not on my wife Pixel 3XL. It leads to black screen after the boot, like the launcher is crashing. Very strange.
[Magisk] Golf c:
Perfectly fine on my 3XL
[Magisk] jesterpaul:
Weird thing is my device is still using basic attestation check (not hardware) but still failing. Galaxy S20 Ultra 5G running the latest canary Magisc manager and app. Hide is on, as is hide Magisc manager (so app is called "manager' only). Reinstalled it twice, but still fails.

I have following modules installed.

Magic hide props config

Air Audio (stream your music)

GPay SQlite fix

Anir Nauril

Systemless hosts

safety patch

Running stock Samsung firmware. Was passing fine before I updated to Aug security patch release.

I'm baffled. I know one it changes to hardware attestation I'll be screwed, but why would it be failing basic???
[Magisk] Ric G:
Any direction on 'process error, installation failed' while trying to patch bootloader on Pixel 2XL?

Using Canary Manager 29.; searched for solutions but came up empty handed.
[Magisk] pndwal:
I guess you have basicIntegrity failing, not just ctsProfile!

This is because you still have SafetyPatch module loaded.

ctsProfile will always fail if no basicIntegrity, and SafetyPatch module has failed basicIntegrity for some time now:

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

You only need one mod to spoof fingerprint anyway, and this function will be disabled in MagiskHide Props if SafetyPatch or other is detected, so remove the latter and configure the former. PW

---------- Post added at 03:51 AM ---------- Previous post was at 03:30 AM ----------

Do you have STOCK Recovery? Also, ensure you try with NO Systemless Hosts module, at least initially. PW

---------- Post added at 04:00 AM ---------- Previous post was at 03:51 AM ----------

Patch bootloader? Canary Manager 29? ... Both sound dangerous! :silly:

If you meant patch boot.img using MM 299, are you doing this from Android 11? You can't use .img made in A10 or earlier environment for A11.

Also, as noted above, you need STOCK Recovery, not TWRP. And ensure you try with NO Systemless Hosts module, at least initially. PW
[Magisk] Rukbat:
Not even, on the 2 - we're still at 3.3.0.0. I've been using Titanium since around February. But it would be nice if Troys Dee, or someone else, rewrote TWRP to run on 11.

Well, as long as I got root on 11, I'm sort of a happy camper for now. And I don't think the 2 will get 12.
[Magisk] pndwal:
Quite. FWIW, I doubt ANY TWRP, official or unofficial, is compatible with A11.

twrp.me site says nothing re A11 compatibility, only ongoing difficulty making it fully A10 compatible, and last build was 3.4.0-0, Released Jun 24, 2020, so their inactivity may even indicate they've given up!

Moreover, TeamWins GitHub shows branches only for Android 4.3 through 10.0. My deduction is that there is slim chance ANY will work with Android 11, and working builds are likely going to take many months, if they surface at all.

This is revealing too:

PW
[Magisk] pndwal:
[MENTION=3236502]jesterpaul[/MENTION] thanks for appreciation. :) Did that fix basicIntegrity and ctsProfile for you? PW
[Magisk] supachris:
Including systemless hosts module activated?
[Magisk] zgfg:
An overlooked and seems never answered question:

Did you mean this stuff - those, lazy to click, please look at the screenshot attached:

https://github.com/topjohnwu/Magisk/commit/a5d7c41d209527fe7b45a2ef7d031add9b6fad24

That changes were commited in May, two months after 20.4 release, hence n/a in Stable (yet) but only in Canary

The "safe mode stuff" is of interest now for Canary A11-ers who forgot to disable modules before update(s) and got the bootloop - with no TWRP for A11 available and with "ADB remove modules stuff" not working on Pixels

Hence, that is the trick (besides Factory resetting or flashing custom made Magisk patched images with overlays forcing to disable/remove modules) to recover from bootloops caused by incompatible module(s) - if you do have Canary:

- Force (re)booting device to Android Safe mode (google to find-out how to for your device).

- Reboot once again to 'normal' (it will boot with Magisk but with all modules disabled).

Install Magisk Manager if lost, re-enable Magisk Hide and go to the Modules tab to decide which modules to keep and re-enable and which to remove

- Reboot once again, with Magisk (Canary) and hopefully without bootloops

Sorry if that was already discussed recently.

Maybe I overlooked since I was not interested (having TWRP - much easier to manipulate with modules if needed, not having A11 and not having bootloops) but I tested yesterday on my Davinci (Xiaomi Mi 9T) with MIUI 12/A10:

- Rebooted to Android Safe mode by pressing and keeping pressed Volume Minus at the moment when mi logo appeared (not earlier).

It states Safe mode at the bottom-left, letting me to know that I was indeed there

- When I rebooted to 'normal' I had to disable Airplane mode (remained after the Safe mode).

I didn't need to reinstall Manager, maybe because mine was repackaged.

I had to re-enable Magisk Hide and to download again SafetyNet check applet but the rest (apps enabled for root or for Magisk Hide) was all preserved

And yes, all modules were there and disabled as expected?

The most daunting part was to organize again my Home screens - on my MIUI, icons for all user apps disappeared upon booting to Safe mode (where user apps were not available) and I had to drag them back from the App drawer?

PS: Troubleshooting and Guide are AFAIK for Stable, but maybe worth to mention under the Module issues
[Magisk] Didgeridoohan:
Once the next stable version is released the Troubleshooting guide will be updated accordingly...
[Magisk] Mother_Teresa:
I Ota flashed 11 over 10 (also wipe) on my pixel 2 xl and managed flashing Magisk by (re)booting the latest twrp.img, after first boot and from there flashing the 20.4 build.

As I did not use the canary (debug) build, it got into a bootloop but the option in twrp to fix a bootloop actually worked :)

Flashed the debug build and canary manager and all works fine it seems.

Using systemless for ad blocking and installed Energized Protection (had to adjust an entry/location).
[Magisk] Ric G:
deleted
[Magisk] bigknowz:
SU Denied

On this point, with the Canary Manager, not seeing an optoin to toggle from Denied to Granted for apps. Guidance on how to Grant after Denying by mistake appreciated, thanks in advance.

Pixel 4XL stock Android 11, Magisk Manager 299, Magisk 20424
[Magisk] zgfg:
Don't understand what are you looking for.

E.g., for SuperSU rights, use floating menu at the bottom, second tab and for each app in the list you have a knob to revoke or grant the root rights.

Or delete from the list to be asked again

Play a little to become familiar
[Magisk] randomaccess0:
no root on KINGKONG MINI (A/B: No, SAR: Yes, Ramdisk: No) running Lineage OS 17.1

Hi,

I am trying to install magisk on a CUBOT KINGKONG MINI. I did install Lineage OS 17.1 following the instructions here:

https://xdaforums.com/general/rooting-roms/installing-custom-rom-cubot-kingkong-t4050815

which is running fine :)

Unfortunately there is no built-in root, so I am trying to install magisk. As pointed out in that thread, I installed magisk in recovery-mode but when booting the recovery-magisk-system I do have root but mobile signal is not working. No SIM recognition, no communication, which of course renders the phone useless. :(

I have since then been trying to find a way to install magisk into the boot partition. :eek: The problem is, that the normal boot process does not use a ramdisk, so after patching and flashing the boot.img, there is no magisk installed. :crying:

I then stumbled over some threads and with the help of google translate I was able to understand that, as pointed out by Chela_vek, the problem is, that the magisk install routine can not unpack, patch and repack the kernel to use the installed ramdisk. He even gives a handmade boot.img, which should enable the ramdisk and magisk, but the download link is dead. :( I was trying to follow the instructions to create the boot.img myself, but I am stuck at step 5. I let the latest canary magisk manager modify the stock boot.img, unpacked that, then unpacked the kernel, found and replaced the "skip_initramfs" with "want_initramfs". But I cant repack the kernel and boot.img correctly, as after flashing it always bootloops. :eek:

Could someone please tell me, what software and what command lines are necessary to correctly unpack boot.img and kernel and what software and command lines are needed to repack the modified kernel back into gz and then into a working boot.img? :confused:

Thanks.
[Magisk] Dyrex2004:
Best root tool ever.
[Magisk] KurashikiAzusa:
Does anyone have any idea how to fix this?
[Magisk] Rukbat:
That "be patient" sounds promising. I have no problem waiting 6 months or a year. (Or, if I get bothered enough, to download the source and have a try at it myself [I spent over 40 years developing software for a living, so maybe I'll have to come out of retirement for a short time].)
[Magisk] Didgeridoohan:
Just to clarify: do you have these apps on the MagiskHide list or not?
[Magisk] Svensemann:
I know Android 11 is new. I tried to install canary on my K305G with A11 on the Xiaomi.eu Rom. The problem is, it dont detecting Magisk. I tried it with the Zip from Magisk Canary and i tried to flash the boot.img, but no luck with both. Should i wait or is there workaround for that?
[Magisk] nitramus:
fixed my boot loop.

updated pixel 3xl from 10 to 11 and canary seems to be the only one working for us right now.

Installed Canary but was patching boot.img before setting channel to canary which was causing boot loop

changed channel to canary first, patched boot.img and then flashed magisk_patched.img

Now everything is working fine.
[Magisk] Ch3vr0n:
It's said a few times now before yours, (even by myself) that you need canary for A11 to work on pixel 3 xl and other devices. Magisk 20.4 is NOT compatible with A11
[Magisk] nitramus:
I know for canary bedug apk but I did not see to change the channel to canary within the app.
[Magisk] Ch3vr0n:
Settings - update channel (under the header 'manager', almost at the top of the screen)
[Magisk] jesterpaul:
Yes, thank you. It was that patch you mentioned. Removed it and back in business.
[Magisk] pndwal:
I have briefly read linked info and, while I won't pretend to fully understand why your device loses network function with root, I got the gist.

However, [A Russian Development site that XDA doesn't trust and doesn't want me to mention] link to boot.img (your 2nd link) is not broken. You simply need to login to access hosted files.

I have a login, so have downloaded it and attached it here for you (unzip).

To create login for [same] Russian site, any non Russian speaking person who wants to axcess this resource for many devices should study this: [search for 'login register Russian captcha tutorial] (Hosted files are not available and links appear dead unless logged in) PW
[Magisk] pndwal:
Checklist (not exhaustive!):

- You must use .img made in Android 11 environment, not A10 or earlier.

- You need STOCK Recovery, not incompatible TWRP.

- Ensure you try with NO Systemless Hosts module, at least initially.

Nb. John has been working on 2SI device checking logic problems for those running Android 11 (on affected SAR A-only devices). This is a major reason we didn't get stable MagiskSU v21 in time for Official A11.

Clearly, he has been making progress, but I'm not sure issues with this are yet fully resolved.

If your's is a SAR A-only device, you may still need to wait for resolution.

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

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83433173 PW
[Magisk] KurashikiAzusa:
The list does display all applications but only firefox has magiskhide enabled, as an example.

It is a good thing that magiskhide is disabled by default as after enabling magiskhide and exiting magisk manager I could not open any applications, not even magisk manager itself.
[Magisk] pndwal:
Just a possibility:

Have you loaded Systemless Hosts?

If so, try with NO Systemless Hosts module.

This has been causing app crashes / freezes / instability w/ Canary MagiskSU & Android 11. It may well be a bug w/ earlier Android too.

I'm guessing many previously working features may be comprised in recent Canary, as John Wu is trying to implement a GROUND-UP rebuild of Magisk for upcoming Stable release. PW
[Magisk] KurashikiAzusa:
No modules were installed, not even systemless hosts.

This issue has been here for the last few versions of canary, and I thought about posting it to github issues, but decided against it since magiskhide issues without notable contributions or possible fixes are not welcome there.
[Magisk] xunholyx:
Not true. I've been using TWRP since Android 11 dp 2 with my P2XL. Fastboot booting it instead of installing it is the preferred method now. But TWRP does in fact work with A11