yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Yup, but seems there's a reason. - Remembered this one from way back:

xxxxxxx MOD EDIT: Link removed.

... that's if hiding / denying are really synonymous. PW
[Magisk] zgfg:
Yeah, but now times have changed :)

Btw, it can be added by CLI:

magisk --denylist add com.google.android.webview

It doesn't broke my WebView but now I don't run Alpha version with Zygisk to ser could it fix Webview there
[Magisk] jons99:
I edited my post so it'll be more clear
[Magisk] pndwal:
Could you do me another favour: just disable Riru (S/N will fail if you have USNF 2.x), reboot and check webview (eg whether XDA app notifications actually open page)? 👍 PW
[Magisk] Homeboy76:
Alpha Telegram

"The current recommended version is the version in the update channel.'

Where is the update channel?
[Magisk] jons99:
without riru sn is failing but the webview works fine
[Magisk] zgfg:
Update Channel: Alpha in the Alpha app (if you are using Alpha), that points to Gothub and Alpha b6298f86

Or stay on Stable, Canary...
[Magisk] Homeboy76:
I'm seeing b6298f86-alpha.

Thanks for the confirmation. (y)
[Magisk] pndwal:
It's Alpha (as set in App settings, Update Channel), so that's "the version in the update channel". 😜 PW
[Magisk] pndwal:
FWIW I restored SafetyNet pass (no Riru, installed USNF 1.2.0) and gave denying webview a shot:

- Added and confirmed w/ magisk --denylist ls, rebooted, tried loading from XDA notifications --> no dice.

Just knew you'd want to hear the bad news! 🙃 PW
[Magisk] zgfg:
Tried myself, too, with

0ab31ab0 - same result

Returned back to b6298b86
[Magisk] ipdev:
For those running vvb2060's alpha builds.

You should be able to install any of the alpha builds over each other.

The versionName is changing GitShortHead-alpha.

The versionCode is remaining 23001.

The versionCode is what triggers the upgrade/downgrade install.

PackageManager only see that you are re-installing version 23001. ;)

With that being said, you might run into a problem with magisk.db that was generated by an older/newer build.

There was a very recent commit about this. (Currently the last commit on John's repo.)

Magisk - GitHub - commit - f7c0e40​

Also the last commit in vvb2060's repo currently.

You might have an issues repacking a Magisk boot image.

For testing purposes you should always use your ROM's stock boot image.

Yes testing the updating logic is important but, you need a base line to compare.

A clean install may fail when an update succeeds and vice versa.​

Cheers all. :cowboy:
[Magisk] pndwal:
Alpha Telegram OP note:

Like many w/ or w/o use of a translator, I don't think I fully understand the implications here, but I notice Alpha branch is gone from github.com/vvb2060/Magisk/ at least for now. 🤔 PW
[Magisk] ipdev:
I was using a simple script to add a few things to the magiskhide list.

A few days ago, I updated it to DenyList and...

I updated it to be more shareable (user friendly). 🙃

Work-In-Progress.

Added a few failsafe(s) and also made it compatible to run from a file manager app.

I have only tested that function with fx and MiX but, should work with others..

I did a little more clean up and pushed it to my GitHub.

GitHub - magisk_deny.sh - Link​

The commands need to be run with root privilege so the file manager, terminal or shell you run the script from needs root access.

You can manually add processes to the list even if they are not installed.

You can dump your current list using the command line ls option.

Example dumping it into a text file in Download.

magiskhide ls > /sdcard/Download/MagiskList.txt

magisk --denylist ls > /sdcard/Download/MagiskList.txt​

You need to replace the | with a space to set it using command line.

If you are as lazy as me. ;)

Updated for DenyList.

If you are still on Magisk using a magiskhide list, replace --denylist with magiskhide

If you want to convert your current running magiskhide list into a denylist, replace only $(magisk --denylist ls); with $(magisk magiskhide ls);

[[ -f /sdcard/Download/MagiskList.sh ]] && rm /sdcard/Download/MagiskList.sh;
for i in $(magisk --denylist ls); do
ii=$(printf "$i" | sed 's/|/ /g');
echo "magisk su -c magisk --denylist add "$ii >> /sdcard/Download/MagiskList.sh;
done;

The output was my original magiskhide add script that I used.

Cheers. :cowboy:

PS.

This is based on John's repo.

I am not sure if vvb2060's alpha build require Zygisk active for enabling DenyList.
[Magisk] pndwal:
AFAICS it does, at least for now.

I believe ptrace was used previously for this; new Magisk needs Zygisk; I don't think we'll have an option in future since all ptrace code is gone... unless it comes back. vvb2060 OP note re. this here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85643797

... 'n please don't team up on me; my Android reflexes are abominably slow and I might just go sulk in the carpark... Marvin.
[Magisk] zgfg:
Good to know, thx

Hopefully, if I make a copy of /data/adb/magisk.db before trying the next Alpha, I will be able to restore the database if I would have to go back to b6298f86-alpha
[Magisk] TNSMANI:
MOD ACTION:

Enough is enough. Despite my deleting some off topic posts yesterday, the spam continues. Thread cleaned. Please check your PM inbox and avoid off topic posts.
[Magisk] unknowndrop:
Hi,

Does snapchat work with the Magisk and corresponding modules for hiding? I've been out of rooting scene for long, so I don't know. The last time snapchat was able to detect it.

Thanks.
[Magisk] maeries:
Need quick help with the installation instructions https://topjohnwu.github.io/Magisk/install.html

Under "Patching Images" it says I need the boot.img (cause my OP 5T has RAM disk), but where can I download it?

Thanks in advance

Edit: I'm running lineage OS with microG
[Magisk] Fif_:
From the LOS install zip file.

Unzip that file, you should find a boot.img in there. That's what Magisk needs.

If you have a boot.img.br file, just uncompress it first with brotli.
[Magisk] maeries:
Thanks. I thought it was somewhere on the magisk github
[Magisk] zgfg:
Boot image is part of your firmware. Imagine how many phones and models and their firmwares are around (usually, each OTA installs its own, new boot img)

What would Magisk have with them, who would collect and manage a thousand of those boot images on the Magisk Github pages?!

Btw, when you take a simple search you will find here on XDA a subforum for almost every phone, e g. for your One Plus 5T.

There you find a section named Guides and another Questions and Answers.

That is the place where users for the particular phone share the knowledge where to find and download their firmwares, how to unpack them (for some phones they are not ZIP files), etc, etc

It is worth (not to say a must) to look there first for the device specific questions like yours - you cannot expect that other users here with maybe Samsung, XPeria phones or who knows, could give you correct (and trustful!) answers for your One Plus

Btw, that's the pretty old device and TWRP must be available, hence Magisk can still be flashed through TWRP (with no need for finding a boot img, patching and flashing, although that is not really a rocket science)
[Magisk] Lefteris Fragiadakis (Frago):
Hi from greece! I have a pioneer SDA8TAB android 9,followed the magisk steps for recovery method as the tablet doesn't have ram disk but it doesn't work, I can't try other method cause this device does not have custom recovery and I cant find a way, anyone can help? I have full system dump made from emmc easyjtag
[Magisk] DiamondJohn:
I have a Pixel 4A without a custom recovery. I use fastboot to install Magisk
[Magisk] Lefteris Fragiadakis (Frago):
Tried, no ramidisk and if I do the recovery it don't do anything
[Magisk] J.Michael:
You might be able to patch the boot image. Sometimes it works, even though the original boot image does not have a ramdisk.

You will need to describe "don't do anything" in more detail. What do you see? When does it look different than the way it looks when booting the stock image?

How can you have a "full system dump" if you are not rooted?

Did you unlock the bootloader?
[Magisk] Lefteris Fragiadakis (Frago):
I take off chip emmc from board with easy jtag and then tried to patch boot then bootloop, flashed stock boot and it fixed, then I read if it's ramidisk no patch recovery, did it, no bootloop but no root using combo for recovery

Bootloader unlocked, I can share default. Prop if this helps or anything else, it don't have a/b partition but it's officially android, allwinnner a50
[Magisk] J.Michael:
WOW!

That's a dream come true!

When you patch recovery image, can you boot to recovery?

Have you looked for a forum for this device?

I have a Samsung tablet, with Magisk in recovery. Booting towards but not quite to recovery was miserable. Maybe you need to try a few dozen more times. There have been notes about having a cable plugged into the phone while trying.

What do you check after booting that makes you decide you do not have root? I kept running the Magisk app, waiting for that glorious moment when it said "more setup needed".

Really SDA8TAB? Not SDA-835TAB?
[Magisk] Lefteris Fragiadakis (Frago):
Thanks! Yes it boot to recovery, tried few times but root not working, there is a forum but they don't know something, I also sent the the files to try, yes sda835a, in greece yes different name, is any other way? Any way to patch the system. Img may be? Or someone who can make twrp for this device?
[Magisk] J.Michael:
The point of Magisk is to *not* patch the system image.

I think installing TWRP to use it to install Magisk is the wrong way to go. Finding a working TWRP is a whole other project.

"few times" isn't nearly enough. The process is very fussy. You have to find just the right time to let go of the buttons so the (BIOS?) has committed to booting the recovery image, but the recovery image (hijacked by Magisk) has not yet tested to see if the buttons are being held down. Someone finally found a way to explain it to me, it involved identifying just which of the three to five "boot logos" was my signal to let go. I really meant it when I said try it a few dozen times. And, like I said, at some time, for some device, someone declared that it wouldn't work unless you had a cable plugged into the device.

Make a point of shutting down to the completely powered off state before each trial.

I don't know in what form you have the original boot image, but compare the sizes of the original and patched images. If the patched image is smaller, maybe it needs to be padded. Even if they are the same size, it could be that the Magisk app you are using discarded some signature string that was in the original. Somebody else will need to comment further.
[Magisk] Lefteris Fragiadakis (Frago):
Here is the stock imgs from my firmware, if anyone can help me to make it work I will be thankful and I will buy him a drink! Maybe Raki we have here in crete!
[Magisk] DiamondJohn:
I have NOT read all the posts. But to flash the boot image, I do NOT go into recovery, it is dlashede in fastboot. CAn you get into fastboot? and can your PC "see" the phone in fastboot mode?
[Magisk] pndwal:
As mentioned by @J.Michael, I think you have likely already succeeded in flashing root w/ Magisk in recovery ramdisk since it flashed without errors, and you don't get bootloop.

Your difficulty appears to be booting to recovery mode system-with-Magisk on type III device using key combo.

https://topjohnwu.github.io/Magisk/boot.html#piecing-things-together

Nb. 'booting into recovery mode' is not referring booting into recovery, but system-with-Magisk mode achieved using recovery ramdisk, ie. booting into system via 'hijacked' recovery ramdisk since boot.img lacks ramdisk. This involves Magisk independently detecting recovery mode key combo + release of buttons within a specific time window in order to execute magiskinit. (A ramdisk is always required for systemless Magisk.)

https://github.com/topjohnwu/Magisk/blob/master/docs/details.md#magisk-booting-process

If the key combo only is detected ramdisk will boot to recovery.

Instructions:

https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

As mentioned, key release timing is critical, and varies per device.

Compounding the issue is the fact that John's hybrid Magisk key combo detection does not operate as expected / designed on many devices, and users may need to experiment to establish a working method that is sometimes at odds with John's instructions.

As an example, safe mode is not always detected by Magisk resulting in modules remaining active even after safe-mode has been activated w/ Magisk installed on (some) Xiaomi devices. This can be very misleading to users. However, an altered key combo does work to both trigger safe mode and allow Magisk to detect Safe mode trigger.

I opened an issue here Regarding this failure to detect key combo and critical timing 'sweet spot'.

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

So I recommend you keep trying to boot system w/ Magisk in recovery as you already seem to have (had) this installed correctly.

🤠 PW
[Magisk] pndwal:
Seems he can't patch / flash the boot.img per se, as it lacks ramdisk (Nb Magisk can/does however add ramdisk to boot.img on certain type III (ramdisk = no) devices eg. Xiaomi).

Seems in his case he must (actually did) patch / flash recovery.img, which is also actually a boot image. PW
[Magisk] pndwal:
AFAIR, this may be unique to Sammy's OneUI v3.0+ (Android 11), but without USB connection booting to special modes (recovery, safe etc) simply don't succeed.

I therefore don't think this is the issue here since member boots to recovery w/o issues...

it seems issue is simply the release timing required to bypass recovery to reach recovery mode system with Magisk from recovery ramdisk (ie. system incl. Magisk w/ initial rootdir = rootfs from recovery ramdisk, final rootdir = system as opposed to system w/ initial rootdir = system, final rootdir = system). PW
[Magisk] Lefteris Fragiadakis (Frago):
Yes I can go to recovery
[Magisk] DiamondJohn:
No, its FASTBOOT not RECOVERY that I use.

But it be irrelevant for YOUR device, as covered in the post https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85674179
[Magisk] Lefteris Fragiadakis (Frago):
Guy

im sorry ,yes i can go into fastboot,i will read everything you said and i will start from scratch!
[Magisk] J.Michael:
@Lefteris Fragiadakis (Frago) What are the sizes of your {original,patched}{boot,recovery} images?

Were you careful to

NOT check "Recovery" when patching boot.img

CHECK "Recovery" when patching recovery.img

?
[Magisk] Lefteris Fragiadakis (Frago):
yes i checked,,is the same size both boot and recovery,patched and stock version but when i extract ptched versions i see the diffrence in boot and recovery
[Magisk] jons99:
new alpha is out and working fine
[Magisk] Lefteris Fragiadakis (Frago):
so after hours nothing, i am sure something else is missing for this device, also while searching I found for the same allwinner brand a custom twrp for a TV box and it pass the signature verification, it does not work cause diffrence device, but when I try to load with the same method magisk zip it failed cause verification error, can we fix somehow the verification on magisk, searching for ways...
[Magisk] Didgeridoohan:
You cannot install the magisk.zip from the stock Android recovery, you need a custom recovery like TWRP. But if your device need to use the recovery image to install Magisk (due to no ramdisk in boot) you cannot install Magisk through recovery...

So far it sounds to me like you've managed to get a recovery image patched, but you have not yet managed to boot to a rooted system. I'm assuming you've read this:

https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

When you do the recovery key combo to boot to a rooted system, does it boot up straight away or do you end up in recovery first? If everything is installed correctly it might just be down to a timing thing (as mentioned earlier) and you need to try different timings of releasing the buttons when the device vibrates with splash screen.

It could also be that the device simply is incompatible too, but let's hope it's a timing thing.
[Magisk] Lefteris Fragiadakis (Frago):
it always boot to recovery,tried 100 times sure!fiffrent timing-with cable and without,im tired but i dont want to give up,somebody who can examine the stock recovery will find a way sure!
[Magisk] Didgeridoohan:
I took a quick peek at the images you provided earlier. Magisk patches them just fine, without any errors and the boot image is indeed missing ramdisk so the recovery image is what you need to use (unless it's a Xiaomi situation kind of thing where the bootloader does accept the added initramfs, but that's probably unlikely). I can't tell you anything more about the images than that though... Not my area of expertise.

Since you haven't been able to get the boot key combo working yet, that is what I would focus my efforts on for now. But, maybe that just means that you haven't been able to install the patched image properly, or that it isn't compatible somehow. It could of course be something completely different, but since it seems like you're the pioneer (pun intended) for this device it's hard for us to know what that could be.
[Magisk] Lefteris Fragiadakis (Frago):
Thanks for your time! Sure I flash the patched recovery right cause if I flash boot

Img on recovery img can't boot on recovery, I flash back patched recovery and it boot on recovery, maybe the key combo don't work on this device, is any other way to patch the system? Tried to unpack it but I can't find working squashfs extractor
[Magisk] pndwal:
No way to patch system; Magisk needs to reside in ramdisk as I mentioned, preferably in boot partition, otherwise in recovery partition...

I don't have experience with Magisk in Recovery, but it seems the trick to key combo detection is to release all keys at the earliest possible time without booting to system...

Since you can reach recovery, don't bother with Sammy USB-connected-for-Android-11 requirement...

Also, can we assume you used this device to patch recovery.img in Magisk App? PW
[Magisk] Lefteris Fragiadakis (Frago):
Yes off course
[Magisk] pndwal:
Alpha Magisk update (61783ffc-alpha)

[General] Based on 61783ffc, the content that has been merged into the upstream is no longer listed

[App] Correctly process any data from magiskd

[App] Support SharedUserld

[App] Delete the backup file after restoring the boot mirror image

[App] Built-in current version update log

[App] Use the local version when you cannot download the stub, now it can be used completely offline

[Busybox] Fix the default shell path

[App] Switch to Java 8 modern time API

[DenyList] Deal with suspicious props

[App] Expand and update SafetyNet, update the version of snet.jar to 18

[Sepolicy] Sepolicy with built-in LSPosed

[General] Add an obsolete cgroup v2 path

[Zygisk] Fix app_zygote and webview_zygote binary

- You update the journal From 23.0 to 61783ffc

[General] Supports pure 64-bit devices

[General] Support Android 12 emulator

[Zygisk] Code injection framework

[General] Remove MagiskHide

[General] Support Simulator to add modules

[MagiskBoot] Support zimage format

[MagiskBoot] Add zopfi encoder

[Magisklnit] Support bootconfig

[App] The repair installation function will now check if the script under /data/adb/magisk/ has not been updated

[Magisklnit] Support some Meizu devices

[MagiskSU] If the kernel supports it, use isolated devpts

[MagiskSU] Fix the pts configuration code, now no additional sepolicy rules are needed

[MagiskBoot] Support v4 boot image header format

[Magisklnit] Support oplus.fstab for some OnePlus and Opal devices

[App] Restart and update modules, not allowed to be marked as pending deletion

[App] Delete online warehouses

[App] Add mounting information to the saved log file

[App] Suitable for Android 12 API level

[App] Display the waiting pop-up window that is running when hide/restore the original app

[Stub] Open source obfuscation function

[Script] Check and display the sepolicy rule folder of the module.

[App] When the window pops up, hide the screen and add layers. Android 12+ is required

[App] Delete the floating bottom bar and change it to the general bottom operation bar

[General] Support compilation and cache

[General] Add rejection list function

[App] Delete DoH

[App] Delete SafetyNet

[App] Allow the log page to be opened when Magisk is not installed

[App] Display Zygisk status, add restart to take effect to remind Zygisk to Fix the problem

PW
[Magisk] J.Michael:
Could you repeat what you said about the sizes of the original/patched boot/recovery? I thought you said they were all the same size, but then you said you see the difference. Do you see different sizes? Or were you looking at the contents of the images?

If on an unpatched device you can get to recovery, then you have the right key combo to get to recovery. What we keep harping on is, when you magisk-patch recovery, when you want to boot to magisk-controlled Android, you have to pick just the right time to let go of all buttons. It is easy to tell that you let go too late: you end up in recovery. What's harder is telling that you let go too soon: it boots Android, and you can't tell whether Magisk is active until it finishes booting so you can run the Magisk app. (It might be you could test by looking for files that only exist when Magisk is active, but I'm not sure that they are there before Magisk has done its "more setup".)
[Magisk] Lefteris Fragiadakis (Frago):
Size is the same but inside I see the extra files of magisk, I will try again today to see if I manage to boot with root, for confirmation, should I use only the keys to boot in recovery or all?
[Magisk] martyfender:
How is this version working for you?
[Magisk] J.Michael:
If you patched recovery image, and "installed" it (I don't know what mechanism you use),

Whatever key combo you use to boot to recovery, that's the key combo you use to try to boot Android-with-Magisk.

You could try writing the magisk-patched-recovery to the boot partition. Then you wouldn't need a special key combo to boot. I just do not know whether Magisk booting in recovery requires the boot partition at some point.
[Magisk] Lefteris Fragiadakis (Frago):
I flashed

Fastboot flash recovery recoverypatched.img
[Magisk] 73sydney:
Just a reminder for peeps that this like all alphas is bleeding edge, and there are with

this lastest alpha of reports of:

* intermittent root failure (requiring reboot)

* zygote non-functioning

* safetynet failure with denylist enabled

The above can be device dependent

Be prepared for such possibilities, and for the first step in resolution to return to

official Magisk builds, as reporting faults here is unlikely to lead to resolution as

alpha dev doesnt monitor XDA and gets most bug reports via Telegram where we

see them.

In short, it can still be borky folks, your mileage may vary

Return to official builds *may* requite removing /data/adb/magisk.db if not the entire

/data/adb path, after first doing a full uninstall of magisk from within magisk manager

Completely factual post, must be impersonal machine, just facts. Must not smile, must not

emote.
[Magisk] Lefteris Fragiadakis (Frago):
Now I'm thinking, is any way to disable recovery while holding the combo key so the combo key work only for the magisk too boot?
[Magisk] Didgeridoohan:
It's possible to alter the device so that it boots directly to Magisk, it's been done on a few Samsung devices I believe. But, that meant manually baking Magisk into the kernel so you'd have to figure that out (I have no idea).
[Magisk] Lefteris Fragiadakis (Frago):
I will try to find a way, thanks!