yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
FWIW, seems Tab S4 (Launch version Android 8.1, API 27) was using legacy ramdisk boot method when launched since legacy SAR required API Level 28 (Android 9). This is boot method A, Type 1 device here:

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

Also, updates have converted device to 2SI ramdisk SAR, Method C, Type IV device (Running version 29).

Nb, this boot method is not officially considered SAR by Google, (considers only Initial rootdir; how the kernel boots the device). It is SAR by Magisk’s (John's) definition (considers Final rootdir; what the device ends up using when fully booted)

Correct, as bootloader will accept signing keys for stock ROM. See Android Verified Boot:

https://source.android.com/security/verifiedboot

Looks like bootloader is likely locked. Is there no indication in download / Fastboot mode (padlock symbol, etc?)

Quite possible previous owner tried I guess.

Seems you'll need to sort out driver / Odin issues, try fastboot method(s), check bootloader status etc to get proper unlock and ability to flash Magisk.

Sammy users may be of more help. 😛 PW
[Magisk] xAxB:
In the download mode, it also says that the OEM lock is "Off" leading me to think that it's probably unlocked fine. Wish a Tab S4 user could confirm it but it's kinda quiet over there lol.

(While I am at it though, there is a DID number that I often see people remove from photos - I imagine there must be some important security reason for that, but what is it? Simply Googling "DID Number Android" didn't yield anything that seem to explain it..
[Magisk] dcarvil:
Try googling 'Android "Device ID"' instead. Here is one link - https://www.gtricks.com/android/2-ways-to-find-android-device-id-and-change-it/

It is basically a device identifier, but it is tied to the Android installation, not the device hardware. It will change when you flash a different ROM.
[Magisk] jons99:
27 is out and working well

GitHub - vvb2060/magisk_files

Contribute to vvb2060/magisk_files development by creating an account on GitHub.

github.com
[Magisk] pndwal:
Latest @vvb2060 Magisk Alpha build (July 27, 2021) changelog:​

Chinese Translated:

alpha update log​

Magisk (1eb83ad8-alpha-27)​

Based on 1eb83ad8, please refer to the upstream update log for related modifications

Properly process any data from magiskd

Support SharedUserId

Delete the backup file after restoring the boot image

Built-in current version update log

Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline

Support bootimg v4 format

Support bootconfig

Detect /data/adb/magisk/ not updated and prompt to repair

Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting

Repair can not be brushed in some TWRP

Listen to the PACKAGE_FULLY_REMOVED broadcast to remove completely uninstalled apps from magiskhide

Display the modal waiting pop-up window when hiding/restore the Magisk application

App adapted to Android 12

Android 12+ super user hides the screen overlay when the window pops up

For devices supported by the kernel, MagiskSU uses proprietary devpts to bypass some application detection

Rewrite MagiskSU's logic to open pty and delete extra sepolicy rules

Fix incorrect signal sending in MagiskHide

Add untrusted_app_30

Edit: New changes since last build on GitHub 1eb83ad8-alpha-25

Support oplus.fstab for oppo series devices

Prompt that some devices do not load the module sepolicy problem

Add mount information to the log file

https://github.com/vvb2060/Magisk/b...8916dd34ea8/app/src/main/res/raw/changelog.md

My earlier notes:

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

Current notes:

Check 'earlier notes' for installation method / details.

Alpha build users won't yet see Update button notice in Magisk App for this build as VersionCode has (again) NOT changed from 23001.

I'm not sure if this behaviour will be addressed, but users will observe the 'Latest' and 'Installed' version suffix now differs.

Latest in GitHub magisk_files repo is 1eb83ad8-alpha-27

Latest available from Telegram group is

1eb83ad8-alpha-27

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

Nb. In Magisk Documentation, @vvb2060 has updated "Internal Details" and "Deployment" since John did.

https://github.com/vvb2060/Magisk/tree/alpha/docs

🤠 PW
[Magisk] zgfg:
Updated to 27 - all ok

However, I paid attention and observed (like previously with 20 Jul or 25):

- I download the Alpha 27 apk, install, open, check SN, modules, Magisk hide

- all ok and it does not pop-up, not asking for additional setup and reboot

- I select and patch the img file (actually I patched two img files but it probably doesn't matter)

- few seconds later it pops up and asks for additional setup and reboot (screenshot)

- I accept, it reboots, I reopen Magisk app but it pops up again, asking the same again

This time I ignore and reboot manually to TWRP, flash the patched img and reboot - now it no more asks for any additional setup / reboot

If I chose Direct install, then that pop up asking for reboot would perfectly make sense, but not after just patching the boot.img
[Magisk] jons99:
I think it's because the additional setup was made on the old patched boot img and after the direct install you have a new patched boot img not sure just a theory
[Magisk] rodken:
@73sydney Question: Taking the steps of installing the Alpha apk after unisntalling the Stable version, then patching the boot image and flashing the patched boot image warranted a factory reset. Was wondering when I give it another go - after uninstaling the John Wu's stable Magisk, I suppose that I could I just use TWRP to install the Alpha instead of using a patched boot image?
[Magisk] jons99:
you don't need to factory reset you can flash the alpha patched boot img ontop your existing boot img

or flash in twrp works as well
[Magisk] pndwal:
Interesting...

Just took direct update, all fine, then patched 2 images for kicks to try to replicate you issue, but no such problem / pop-up on RN8T. 🙃

🤔 PW
[Magisk] zgfg:
You were already on 27 after Direct Install.

I did Select and Parch only (like I also did first time with 20, Jul version when I observed and reported about that pop-up the first time)

But I did not do Direct install at all. I only patched the stock boot.img (hence asking for reboot to system makes no sense)
[Magisk] xAxB:
Ahh thanks! Kinda funny I couldn't figure that out when I am 80% of why I am even trying to root in the first place is to change my Device ID Changer :)
[Magisk] 73sydney:
Sorry for late reply, i spent the night trying my best to brick my Pixel 2XL by resizing the partitions and flashing an A12 Beta ...it did not go well :)
[Magisk] rodken:
I guess the key is to ensure that I patch the original boot image and not some generic version that I found laying around in my cloud backup.
[Magisk] jons99:
use the unpatched boot img of your current rom
[Magisk] zgfg:
If you have TWRP, you can patch (without renaming or so) the TWRP backup boot.emmc.win

You can also save your patched img for e.g. Alpha 25 and later repatch by Alpha 27, etc
[Magisk] Didgeridoohan:
@pndwal and @ipdev

I saw you guys did some testing on the mysterious reinstallation of an uninstalled Magisk app on a reboot. I present you with the changelog for Magisk v16.6:

:p
[Magisk] klemi71:
Everything is about Magisk alpha at the moment. Is regular version "dead"?
[Magisk] J.Michael:
And yet, I have Magisk 20.3 and I remember having to install the manager when I booted after installing and wiping data.

Then again, it took me quite a few tries to hit that "almost recovery" boot. And the installation notes specificallly said "the Magisk app might already be installed, it might not; if it's not just install it." [not a real quote]

I suppose now I need to track down the post where I told someone that not finding a Magisk Manager app already installed was not a reason to regard the latest "boot towards recovery" attempt as a failure. (just count the "not"s and reduce mod 2)
[Magisk] zgfg:
It was discussed a lot here about John been hired by Google and the unknown situation with future Magisk releases

Also, do you see any release of Stable or Canary (Canary used to be updated every few weeks) after the v23 cca three months ago
[Magisk] jons99:
afaik it's all v23 alpha is v23 with some bug fixes it's probably more stable then the stable release at least for some devices
[Magisk] zgfg:
Alpha is still marked as 23001 (like the latest Canary) but there were three or four Alpha releases since then
[Magisk] andacro:
Is Magisk compatible with Android 11?
[Magisk] dcarvil:
Yes.
[Magisk] pndwal:
Sure is: even worked with some Android 12 devices out of the box!

Nb. In @vvb2060's Magisk Alpha, App is now adapted to Android 12 (Target SDK (API) was bumped to 31). PW
[Magisk] zgfg:
Please before asking, follow the conversation in the thread and/or search through the thread (XDA rules)

You would find tons of posts here mentioning Android 11 (A11), officially supported since v23 (take a look also to Release Notes from Github)
[Magisk] m0han:
i think it was this post that you meant to quote: https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85391155
[Magisk] zgfg:
Do a Search and you will find MANY posts about A11 - e.g., I'm on A11 and many time mentioned that in the context of using Magisk and posting about

Go back to the times of releasing Magisk v23 and read the posts also there (Release notes, users with Pixel, etc)
[Magisk] pndwal:
Mate, he was trying to help as you did quote the wrong user (ie should be post / poster he linked). PW
[Magisk] zgfg:
Oops, thanks - I 'fixed' my previous answers
[Magisk] b00b:
I seems to be having issues with LSPosed and Magisk:

all of a sudden started having a similar problem as yours -

I am using Redmi Note 10 5G, bootloader unlock and rooted with Magisk v23 and -

- installed (from within Magisk v23) - Riru v25.4.4.r26

- then installed (from within Magisk v23) Riru - LSposed v1.4.7 (5803)

- then installed these apks as normal ie outside Magisk:-

-> eu.faircode.xlua_v131_134273.apk

-> GravityBox_R_11.0.4.apk

and for about a month everything was working find but yesterday the phone started taking a bit longer to startup and after a while investigating why i neticed when i go into the Lsposed Manager (auto-installed when Riru - LSposed v1.4.7 (5803) was install) it was saying in blue background and white text, at the top of screen (see pic below):-

"Not installed

LSPosed is not installed"

and at the bottom of the screen, in black background and white text

"LSPosed is not currently installed or active"

the problem is when i go to Magisk modules, Lsposed is showing as installed and activated

I have tried removing both "Riru v25.4.4.r26" as well as "Riru - LSposed v1.4.7 (5803)" individually and restarting and re-installing them both again and one at a time from within Magisk modules but to no avail, still having the delay re-starting of the phone and sometimes its stays on the MIUI screening flashing slightly until i force restart it.

The interesting thing also is, i have the same setup montioned on another exact same phone and that's working fine with only a slight difference, Magisk v23 on the phone that having the issue is

showing:

Installed: 23.0 (23000) (21)

Package: mz.zr

but on the phone thats everything is fine, Magisk v23 is showing:

Installed: 23.0 (23000) (21)

Package: y.qdyuoa

any help or comment anyone? :unsure:
[Magisk] jons99:
please share magisk log and lsposed log if available

my guess is selinux issue
[Magisk] b00b:
hiya, thanks for responding, log file for magisk is attached but cant get the log file for LSPosed as whenh one get into the LSPosed manage there is no log file as clicking on logs just shows "LSPosed is not currently installed or active" even though its showing installed and activated in Magisk modules.

you say your guess is selinux issue - how do i go about investigating that and or fix it pls? :unsure:
[Magisk] pndwal:
I don't use XPosed in any form, but just installed it without issue on RN8T / Android 10 MIUI. (I've done that much before!)

Looking at GravityBox [R] (from LSposed repo) readme, I think this may be your problem:

Do you have these problems restarting with LSposed module disabled? (Sorry, it's not clear.)

Have you tried LSposed with modules disabled / removed, especially GravityBox?

Nb. I have absolutely no experience with XPosed modules. 😜

Package names are simply randomised ones generated when you hid Magisk App. 😛

Hope it helps. PW
[Magisk] jons99:
open terminal and write su and getenforce to show your selinux situation I was guessing it was the selinux cause new riru won't work if selinux is messed up magisk log seems fine to me try to remember if you installed any module that can change the selinux like some viper and dolby modules do
[Magisk] 73sydney:
Ahem, i though id just mention i posted a enforcing version of Viper (along with the original permsissive one thats been workign well for many on 11 ) here a few weeks back:

https://xdaforums.com/t/app-all-root-solutions-6-0-viper4android-fx-2-7.3774651/post-85262627

The enforcing version sets enforcing after a 90 second delay (you can change this to shorter in the script if wanted) after boot is complete. During this time Magisk Detector WILL detect modifications, but wont after the script is run.
[Magisk] b00b:
thanks for your response,

the response i got from "open terminal and write su and getenforce to show your selinux situation" using Terminal Emulator is "Enforcing" (see attached)

the only modules i had on Magisk were:

- Riru v25.4.4.r426

- Riru - LSPosed v1.4.7 (5803)

- Universal SafetyNet Fix v1.20

and with LSPosed itself, the only modules before it went kaput were:

- Disable-FLaG_SECURE v2.0.0

- SudoHide v1.28.5

-XPrivacyLua v1.31

- GravityBox_R_11.0.4

for apps i do have that cld have messed selinux are-

- Linux deploy

- Termux (with 'nethunter for termux' install within termux)

- Tasker

- Adaway

so if it selinux, how do i go about investigating that further or fix it then :unsure:
[Magisk] b00b:
thanks for your input but i havent install Viper or any variant of it :)
[Magisk] b00b:
but ive been using GravityBox for over a mth now with LSPosed & Magisk, some 'toys / things' in GravityBox worked and other dont but it was okay.

can't got LSPosed to be recognised as installed and active although showing as install & activated within Magisk and so LSPosed Manager reports it as not installed and therefore cant see any xposed modules installed on phone, anyhow i had already uninstalled both 'GravityBox and XPrivacyLua and stll LSPosed not working or recognised as installed within it own Manager.

thanks for this bit, didnt know that, though Magisk had auto-installed some update on itself and that why difference in package names, but now i know.

Yes, every little helps and i'm thankful for your thought :D
[Magisk] zgfg:
Interesting - but I use V4A on A11 (MIUI) successfully without the script enforcing SELinux (I have only SE Policy rules in the sh script and Legacy driver enabled in the V4A Settings)

Does SELinux Enforcing remove the need to use Legacy driver?
[Magisk] 73sydney:
I like how you assume i know these things :)

The version i use is from Ichigo from ages back in the thread and is based on 2.5.0.4

Not running in compatibility mode

I have got a test version thats simplified and removes some of the script duplication

(namely sepolicy) compared to the original, moved to Zacks extended module format,

with correct service and uninstall scripts, and sepolicy.rule. I also added an easy way to

switch between enforcing and permissive.....by default enforcing, need permissive? just

create a blank file named permissive on /sdcard and reboot

I just havent released that yet due to a really unpleasant experience with another member.

Put me back a ways in testing after that shock, so need to test it a bit further.
[Magisk] jons99:
well I don't know I'm using the same magisk modules as you and lsposed is working fine (pixel 5 with latest a12) the only thing I can think of trying is switch to edxposed and see if it works or at least gives you a log
[Magisk] Tianhe:
Just to randomly butt in - Edxposed causes safety net failure even with universal safety net fix / MHPC enabled. One of the reasons I had to shift from Riru+Edxposed to Riru+Lsposed.
[Magisk] ReservedName:
Having an issue that whenever I reboot or power up there is a single bootloop. It goes all the way to the Google splash with the loading bar then reboots to the warning page about an unlocked bootloader. After that it boots normally. Does this sound like a module issue? I was thinking to disable them one by one to see.

Pixel 4a

Canary channel, build 23001

Busybox, detach, magiskhide props config, systemless hosts, tulsadiver center clock, universal safetynet fix
[Magisk] rodken:
Sometimes, a change to the SystemUI warrants an investigation.

Disable your modules one after another by starting with the one that messes with the status bar clock.
[Magisk] zgfg:
You could try. BusyBox and specially MHCP (unless you made some changes in the props) should not cause the bootloop

Btw, detach module works for you?

I tried to detach three apps, one of them it never found and two other reappeared in Google play after just a few hours
[Magisk] jons99:
can you share a logcat from after you boot?
[Magisk] ReservedName:
That appears to have done it. A shame because I like that center clock. Guess I have to live with the bootloop.

The detach module doesn't seem to really work I still end up with YouTube in my play store. The only thing that gets it is titanium backup but then it doesn't last. At least it doesn't update the YouTube but I still don't enable auto update anyway in case it tries.

I'll re-enable the module and grab a logcat.

Edit: having trouble finding it now. Wonder if @Tulsadiver has a newer version

flashed the latest cc.zip and now i'm stuck in a bootloop for good. this was not worth pursuing I need my phone to work dammit

finally fixed but so not worth it
[Magisk] Lord Sithek:
One of the reason why I use LSPosed is to hide Vanced and Swiftkey from PlayStore with SudoHide module :) Detach script failed for me as well
[Magisk] zgfg:
Rapid fire continues - Alpha 29 is out on Telegram but not yet on Github
[Magisk] pndwal:
Not sure how you fixed, but if you are unaware, simply booting to safe mode, then booting system immediately after is a mechanism to disable all Magisk Modules in case of bootloop. Next, you remove problem / last module, re-enable others and reboot... for next time! 😜 PW
[Magisk] pndwal:
Thanks! I've now updated, all working fine on RN8T.

Latest @vvb2060 Magisk Alpha build (July 29, 2021) changes (since last GitHub release):​

Chinese Translated:

Magisk (1eb83ad8-alpha-29)​

• Fix the default shell path of busybox

Nb. This build is available only on Telegram at present.

https://t.me/magiskalpha/327

I'll post full Changelog here when available on GitHub.

Last GitHub release, notes, links:

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

🤠 PW
[Magisk] DiamondJohn:
You have a Pixel 4a. Do you by any chance have the https://xdaforums.com/t/mod-magisk-...es-for-pixel-devices-pixel-4a-thread.4215069/ by Typhus_ ?

That module has to trigger a "warm reboot" to enable its features.
[Magisk] zgfg:
Seems there is some 'sowing' problem with 29 - anyone could maybe decipher what would that mean in the Magisk concept?

Anyway, be warned

Google Translation from the Alpha Telegram channel:

🎀:

Sudden sowization

bl Bloodfang:

Indeed, the sow turned ()

🎀:

If there is no problem, push to the update channel

Magisk alpha discussion group:

The above is the problem
[Magisk] jons99:
30 is out

Magisk cannot handle oplus.fstab · Issue #3663 · topjohnwu/Magisk

After Installation 21.2. or Canary phone won't boot. There are several fstabs in boot.img. fstab. default, fstab.emmc and oplus.fstab. In cmdline androidboot.fstab_suffix = default. I managed to in...

github.com
[Magisk] pndwal:
Latest @vvb2060 Magisk Alpha build (July 29, 2021) changelog:​

Chinese Translated:

alpha update log​

Magisk (1eb83ad8-alpha-30)​

Based on 1eb83ad8, please refer to the upstream update log for related modifications

Properly process any data from magiskd

Support SharedUserId

Delete the backup file after restoring the boot image

Built-in current version update log

Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline

Support bootimg v4 format

Support bootconfig

Detect /data/adb/magisk/ not updated and prompt to repair

Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting

Fix that it cannot be flashed in some TWRP

Listen to the PACKAGE_FULLY_REMOVED broadcast to remove completely uninstalled apps from magiskhide

Show modal waiting pop-up window when hiding/restore Magisk application

App adapted to Android 12

Android 12+ super user hides the screen overlay when the window pops up

For devices supported by the kernel, MagiskSU uses proprietary devpts to bypass some application detection

Rewrite MagiskSU's logic to open pty and delete extra sepolicy rules

Fix incorrect signal sending in MagiskHide

Add untrusted_app_30

Prompt that some devices do not load the module sepolicy problem

Add mount information to the log file

Fix the default shell path of busybox *

Support oplus.fstab for oppo series devices

https://github.com/vvb2060/Magisk/b...0d886c64224/app/src/main/res/raw/changelog.md

*Nb. Change since last build on GitHub 1eb83ad8-alpha-27

My earlier notes:

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

Current notes:

Check 'earlier notes' for installation method / details.

Alpha build users won't yet see Update button notice in Magisk App for this build as VersionCode has (again) NOT changed from 23001.

I'm not sure if this behaviour will be addressed, but users will observe the 'Latest' and 'Installed' version suffix now differs.

Latest in GitHub magisk_files repo is 1eb83ad8-alpha-30

Latest available from Telegram group is

1eb83ad8-alpha-30

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

Nb. In Magisk Documentation, @vvb2060 has updated "Internal Details" and "Deployment" since John did.

https://github.com/vvb2060/Magisk/tree/alpha/docs

🤠 PW
[Magisk] pndwal:
I think it's just a follow-on comment on "Recently high production 👍" and your comment, which may not have been properly understood.

Still seems to be struggling with this Magisk issue:

https://github.com/topjohnwu/Magisk/issues/3663#issuecomment-888875725

Re '• Support oplus.fstab for oppo series devices' as we speak however...

Said "I tried my best, MTK asked for more blessings" (translated) on Telegram. PW
[Magisk] m0han:
would be nice to check it out. waiting for it to be ready.
[Magisk] pndwal:
& @73sydney

Also, could someone please explain to me what is the advantage of changing sepolicy for viper? It's still not clear to me.

Also, is Legacy mode still needed with this fix? And can someone say if Legacy mode has any disadvantage?

FWIW, I'm running Viper4Android FX 2.7.2.1 from Magisk repo w/ 2.5.0.4 driver on stock MIUI Android 10.

After installing and setting Legacy mode (Compatibility mode does nothing for me), Driver Status is Abnormal, but driver is always reset properly / working (for Legacy mode) simply by disabling module and rebooting, then enabling and rebooting again (2 reboots).

Hope someone knows! 👍 PW
[Magisk] m0han:
Just sharing my setup: ViPER4Android FX 2.7.1.6 (2716) w/ 2.5.0.4 driver on custom rom AICP 16.1 of 7-july (Android 11).

I don't see the setting for Legacy mode. Driver Status is Normal. Compatibility mode does nothing for me as well. My rom has selinux permissive atm.