yashsingh1/xdaforums huggingface dataset:
[Magisk] HippoMan:
What version of Android are you using on your OnePlus 7Pro? If it's Android 10 or earlier (or *maybe* also Android 11), there is a version of TWRP that runs on that device, with which you can do full nandroid backups and restores of /system, /boot, etc.

If you're running a later Android version, I think you're out of luck with nandroid backup/restore, and so I don't know if you have any meaningful backup options.
[Magisk] kiwigi:
I often, if not always, get the same result. This on FF mobile
[Magisk] J.Michael:
Update what after OTA?

Isn't OTA an update? What are you updating after OTA?
[Magisk] wallace108:
Hi everybody. I just bought a Motorola LEX C10 which - odd enough - comes with a pre-installed version of magisk (v 1.0) which is installed in the system partition and is hidden. I discovered it because when I tried to install Magisk Manager, the system replied it was already installed. However since it's hidden and cannot be un-hidden I really don't know how to go about it. This version of magisk is installed in the system partition and is listed as "test". If I run an adb shell, the adb command whoami replies with root. It is also listed in the pm list packages as com.topjohnwu.magisk. I tried to remove it with "pm uninstall -k --user 0 com.topjohnwu.magisk" which returned "success", but after that, I was still unable to install Magisk Manager, as the system kept saying Magisk was installed. I also tried to simply delete the file and folder, but was prevented because it's a read-only system partition.

What else can I do? I do want Magisk to work in the phone but I'm stuck because I got no root access and can't install the Manager.

Thank you

Mike
[Magisk] J.Michael:
What do you mean "listed as test"?

If you have a copy of the ROM, you could try making a new copy in which you have removed this "magisk manager app" from the system partition.

When you use adb, do you seem to have root access? Take a look at "/data/adb". Is there a "modules" subdirectory? What modules do you have?

Your phone is billed as "for Safety Critical use". Maybe they deliberately installed a dummy system app specifically to prevent you installing Magisk. If you don't want to get up to your elbows in reorganizing the ROM, you might have to buy another phone.
[Magisk] zgfg:
Stock ROM coming with Magisk preinstalled - or you bought a second-hand rooted device?

Or maybe you arerunning a custom ROM
[Magisk] wallace108:
Ok, thanks J.Michael and zgfg for your prompt reply. The device is brand new and I bought it off ebay at this link: https://www.ebay.it/itm/155697454777 and when I got it, clearly it was new: so no second hand and the ROM is an official rom, no customizations. Unfortunately I don't have a copy of the fimware in order to remove the magisk directory. The magisk app appears only in the listing of the system apps as "test" (see pic). I also took a look at "/data/adb and found: magisk, magisk.db, modules, post-fs-data.d and service.d

This is the very first time I run into such a problem. Never heard of preinstalled and hidden Magist in an official ROM. If there were a way to properly remove it, I would than proceed and install the latest version with the Manager.

Thank you

Mike
[Magisk] zgfg:
Scroll down and play with Style Chooser and then try to Search Thread upon you reset the style

See the screenshots
[Magisk] zgfg:
It really looks as that somebody installed Magisk

All that does not come with the official, cerified stock ROM

Btw, download Play Integrity Checker from Playstore and test do you pass Play Integrity

One more thing, did you unlock Bootloader (or it was also unlocked when you bought)

Btw, try to open that test app, to see would it update the Magisk app (from your v1 stub)

Test also from Terminal emulator

magisk -c

or

su -c magisk -c

or via ADB

adb shell su -c magisk -c
[Magisk] Nergal di Cuthah:
I personally would not trust a phone that came with an inaccessible magisk (or any magisk), it sounds like the seller altered it and it's not as new as you believe.

Especially if (as in your case) the seller doesn't disclose it has root.

For english speakers. note originally German on an italian ebay (again a little suspect)

I definitly would not trust this phone for security and police as it's marketed. Security services wouldn't want a rooted devices imho.
[Magisk] wallace108:
zgfg, the Play Integrity Checker red flags the phone, btw the bootloader was already unlocked. I tried to open the test app but got nothing. Also the command you asked to execute returned this:

z2_row:/ # su -c magisk -c

WARNING: linker: /sbin/magisk64: unsupported flags DT_FLAGS_1=0x8000001

WARNING: linker: /sbin/magisk64: unsupported flags DT_FLAGS_1=0x8000001

24.2:MAGISK (24200)

z2_row:/ #

How on hell am I going to remove this junk? I usually like Magisk, but only when I am in command.

Anyway I agree Nergal di Cuthah, this device cannot be trusted.

PS

A number of people I know have also bought this phone. Useless to say they also have this issue.

Mike
[Magisk] Nergal di Cuthah:
I found this thread maybe it has the default rom for the lex c10

[Index] Motorola Stock Firmware

Motorola Firmware [INDEX] Helpful Information Welcome, this thread has been created to encompass everything you may need to find Motorola Firmware. Please only post in this thread with feedback on how to improve this document. Do not post "Thank...

xdaforums.com
[Magisk] zgfg:
So you have Magisk v24.2

Maybe, you have also TWRP or a custom Recovery installed, or you can find one and flash

Then, rename Magisk app to uninstall.zip and flash it from TWRP to (try to) uninstall the Magisk
[Magisk] Nergal di Cuthah:
Just a test does

pm list users

Work for you and list any unknown user.
[Magisk] J.Michael:
If you really have "root", you are in a position to read and save all partitions.

If Android 7 corresponds to unsophisticated, you might be able to modify the system partition. This might be as easy as remounting it. It might require producing and flashing a new image.

If you plan to put the effort into salvaging this phone, you should start by backing up all partitions, then finding how you can flash a partition without counting on a bootable Android -- if you hose the system, you can't count on using the system to fix the system.

I think you and everyone you know should try to return these as "not what was advertised."

Failing that, maybe you can find the real stock ROM and flash that.
[Magisk] SerjP:
And to finalize this discussion, I found the reason for 'screen_auto_brightness_adj' value to get reset on every reboot.

It is because in the LineageOS source code this value is overwritten when

So that this system settings value is not supposed to be manipulated manually, because it may be overwritten when auto-brightness controller decides so. And of course Magisk won't help here.

It is for anyone who found this discussion with search (even me in future :) ) and want to know.
[Magisk] J.Michael:
Can you disable "autobrightness controller"?
[Magisk] ZG_DEV:
Well, any help ??
[Magisk] J.Michael:
You could try installing 27 by copying the 27.apk to 27.zip and installing it from the Magisk manager 26 app as if it were a module.

Your screenshot showing a single panel referring to a Magisk version confuses me. The Magisk front page is two panels, the upper referring to what's installed in the boot image, the lower referring to the manager app itself. I've never experienced the "further updating required", so I don't know whether the message obstructs the view of the lower panel. If it does, I've got nothing more on that.

When you try to install 27.apk, have you uninstalled the 26 app? Is it hidden?

When you install the 27.apk, just before patching a new boot image, does the manager app say Magisk 26 and manager 27?

Are you absolutely certain that you are using the right boot image when you patch a boot image with the 27.apk?
[Magisk] pndwal:
Aside from unresolved upgrade and Zygisk issues affecting some devices with 27+, here are some other things worth noting from LSP/Magisk Devs:

Public LSPosed TG channel

Public Magisk alpha TG channel

👀 PW
[Magisk] SerjP:
I don't think so. It is part of the OS. Of course I can turn the adaptive brightness off in the settings so that controller will be deactivated. But thats the whole point to stay with auto-brightness enabled but make it a little bit dim.

No worries, I have a plan B of how to reach it. System resource file 'framework-res__auto_generated_rro_vendor.apk" modification can help. That file contains the auto-brightness related settings and in particular the actual backlight values for given light sensor readings. I've already tried to rebuild that file and replaced the one in the OS. It is more complicated way, but possible.
[Magisk] ZG_DEV:
Did that, didn't work (update was not applied, but strangely Magisk 26.1 asked me to reboot for an additional installation, installed 27.0 as normal APK, magisk 27.0 showed me the next error :

The screenshot I provided has solved the mystery

Hope you find an answer, the message that was shown was hiding the manager app version behind it lmao 😂
[Magisk] wallace108:
This morning the seller accepted my request of reimbursement, and so I shipped the device back. I also informed the many people I know about this issue (and yes they all have this issue) so that they will take an informed decision on what to do.

Thank you guys for your support

Mike
[Magisk] zgfg:
One question

You mentioned that it was the walkie talkie - maybe it needed Magisk for that, or it should work with the stock ROM?
[Magisk] wallace108:
No the walkie-talkie had nothing to do with Magisk. There definitely was a malicious intent in installing AND HIDING Magisk.
[Magisk] pndwal:
A Clarification re. note on access to root shell above:

Public 5ec1cff TG channel.

👀 PW
[Magisk] Santoshji:
HI everyone,

new here,

I am currently playing around with developing my own zygisk mod, is there a way for my zygisk process to get a info on a lib.so file such as magic number, the lib.so is loaded by another process? I am planning to use companion process capability of the zygisk mod to do this :)
[Magisk] ZG_DEV:
Update, got the patched boot.img by 26.1 myself, patched it using 27.0, tried to replace "mmcblk0p29" with the boot.img i had patched (and renamed the boot.img again into mmcblk0p29), my phone went on bootloop. Didn't get it fixed until I replace the boot image patched by 27.0 with that boot image that has been patched by 26.1 .

Looks like I am not lucky in updating magisk :/
[Magisk] J.Michael:
What do you mean "got the patched boot.img by 26.1 myself"? Who has been getting it up to now?

Is "mmcblk0p29" the boot partition?

If you are using "fastboot flash", the name of the image file doesn't matter, you tell the "flash" command what partition to flash, and what file to flash to it.

You keep saying that you take the image patched by Magisk 26.1 and re-patch it with Magisk 27. Don't you have access to the original, unpatched, boot image?
[Magisk] pndwal:
As I said to you above, there are peculiar issues with 2700x ATM where Magisk mount points are broken for some users, Magisk can't see SU, now seems much more work is needed for new 'Atomic' mount, two way binding in rust, Magisk mount refactoring (removal of mirror, issues with tmpfs mount), Zygisk issues etc...

Personally, I'd be sticking with last 26.x/2600x build that worked for you, at least until the increasingly apparent refactoring and regressions in 2700x are sorted out. 🙃 PW
[Magisk] pndwal:
ZG089

Further to @J.Michael's comments above, you should at least try installing 27.0 (etc) Magisk clean... Dirty flash current ROM to ensure everything is back to stock, consider deleting /data/adb contents completely in case some Magisk configuration is corrupted or incompatible, patch and flash stock un-patched boot image... If that doesn't work, regressions I mentioned may be affecting your device... 🤠 PW
[Magisk] alphace:
Hello, I'd like to write a module for magisk to transfer in userspace actions like this:

"echo "16 2048" > /sys/class/leds/aw210xx_led/single_led_br" to allow led control on Nothing Phone 1 to any app, would you suggest me an example module I can take inspiration from?
[Magisk] J.Michael:
You want to write a "service" that can be called from an unprivileged app to write to the LED "file"?

Maybe you could write a program or script that writes its argument to the magic LED file. A Magisk "module" could cause that program file to appear in /system/bin with owner root, and the set-UID permission bit.

How many apps do you expect to call this new service? Instead of using a Magisk module, you could just put the program somewhere. I think /data/local is visible to everyone, just put the script there, or invent a subdirectory.
[Magisk] alphace:
Thanks for your answer, next step would be to inject a new widget in the installed "nothing lockscreen app", a widget created to use that new service/script, so I think I need magisk for that
[Magisk] zgfg:
Write your service.sh script with whatever commands you need

Then use any module you already have installed that does not have its service.sh script and add your scriot to that module, eg in case of Systemless Hosts itbwill be:

/data/adb/modules/hosts/service.sh

Or use some other module that does have its own service sh script and extend its script with your commands

You may need to wait booting to finish (you have to debug how yout modifications works if executed earlier or later), in that case script will look like:

#!/system/bin/sh

until [ "$(getprop sys.boot_completed)" == "1" ]; do

sleep 1

done

echo "16 2048" > /sys/class/leds/aw210xx_led/single_led_br

You can add additional sleep if you need to further postpone upon the System finish booting, eg couple of seconds to establish WiFi connection or something

Or if that is too late (some modifications must be done much earlier, while the System boots), you will have to use post-fs-data.sh script instead of service.sh script but then you must not wait for booting to finish and you must not use sleep

Read on Magisk GitHub Developer info avout differences in service sh and post-fs-data.sh usage

Read there generally about the structure of the module scriot, etc

At the end reboot and test does it work

Once you make sure that your script does the job properly, it will be an easy step to pack it into your own module

Similar questions have been asked couple of times (and I responded with instructions and minumalistic sceleton to pack final scripts into the zip installation for a new module)
[Magisk] Tirofog:
Or maybe put it in data/adb/service.d?
[Magisk] zgfg:
Yes, you can

Or if it needs to execute earlier, add your sxript to the folder:

/data/adb/post-fs-data.d

If putting scripts into those common folders, use any name (some descriptive name)

Brw, for real modules it is better to use their own folders - then disabling or uninstalling the module will disable/uninstall the script.

Although, external mess can be force-cleaned by uninstall.sh script (but cannot be disabled) that automatically executes on uninstallation of the module
[Magisk] ZG_DEV:
Sorry, got the patched the boot image by magisk 26.1, patched it by using magisk 27.0, then replaced it with the installed boot.img (using recovery mode, no flashing)

Yes

Ik, but I don't use fastboot as it is not available in my device (Oppo A5s). Fastboot binaries are removed by Oppo itself.

I have the access to the original, unpatched boot image, patched it using magisk 27.0, flashed it using sp flash tool (my device has mtk chipset and the only way to flash anything is using spft), and after flashing, device went on bootloop. Checked the logs, and as I expected, magisk modules aren't the reason for the bootloop.
[Magisk] Pixi7:
Hello! Is there any module that blocks automatic application updates in the Play Store?
[Magisk] J.Michael:
I don't think this is a job for a Magisk module.

Read back through @zgfg's posts. I think he described locking an app to a desired version.

I am pretty sure the Play Store still has a setting "Do Not Update Automatically".

I set my connections "metered". Mostly it's respected, I'm still fending off "important updates" from five years ago.

(I'm not sure what happens when I connect to a foreign network. I don't do it often.)

Understand, an app may refuse to run until it has been updated. For your own good, of course. Even Magisk manager app has been known to refuse to let you do what you did last week because there is an update available.
[Magisk] Pixi7:
I wanted to block Android System WebView. Unfortunately, there is no option to turn off automatic updates in GP. Unfortunately, updating it every time causes problems with other applications. This is a system application, that's why I'm wondering if it's possible to block the update, e.g. via the Magisk module.
[Magisk] sawdoctor:
Zygisk detach
[Magisk] J.Michael:
My Android System Webview is disabled. I don't remember doing it. I don't know what's being used instead. I would have guessed it was critical. Apparently, not so much.
[Magisk] Schmye Bubbula:
This says that in order to downgrade to an earlier version by renaming the magisk.apk as .zip & then install as a module, "to avoid unexpected issues, delete /data/adb/magisk.db file and /data/adb/magisk directory contents and reboot..."

But I don't seem to have a magisk directory. (I'm on R65C33E4F-kitsune 27001)
[Magisk] J.Michael:
What version of Magisk are you on?

I would guess that you should delete everything in /data/adb.
[Magisk] Nergal di Cuthah:
If you're using kitsune why are you asking in the magisk thread, ask in the kitsune thread and get correct guidance.

Kitsune is not magisk it's a fork with its own directory structure (probably)
[Magisk] zgfg:
Answered in the Kutsune thread
[Magisk] HippoMan:
I know about the SuList (whitelist) capabilities of Kitsune. I'm wondering if in the TJW and Alpha Magisk versions there is a way to force an app to always run as root, even if that app doesn't specifically request root.

I'm looking for an Android-app-equivalent to the following way to force an originally non root-enabled linux executable to always run as root in linux ...

chmod ug+s /path/to/executable
chown root:root /path/to/executable

Note that these commands set up the linux executable to both *request* root and then be *granted* root capabilities.

Is some sort of parallel capability even possible for apps in Magisk-enabled Android?

Thank you in advance.

UPDATE: A related question: I also wonder whether putting an app in Kitsune's SuList would force the app to run as root even if the app doesn't specifically *request* root.
[Magisk] Boom_Hacker:
Magisk broke the auto rotation funcution on my samsung s5e lte( gts4lv)
[Magisk] Lord Sithek:
I remember this issue occures on this tab since Magisk 26. Perhaps consider KSU if you use a custom ROM, Pixel, Voltage and crDroid has it integrated
[Magisk] Boom_Hacker:
but the issus appear in magisk 24.but i am trying to build a kernel for stock oneui
[Magisk] Dakeddy88:
Hello am David from uganda 🇺🇬
[Magisk] Dakeddy88:
My lg thin q v50 does not work why
[Magisk] Slim2none4u:
📚 XDA Developers Forum Rules 📚

XDA-Developers FORUM RULES List of Forum Moderators, click HERE Delete Your XDA Account HERE 1. Search before posting. Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new...

xdaforums.com
[Magisk] pndwal:
Looks like issues opened weren't persued/closed for lack of logs... Please consider running Debug build, supplying logs/logcat and opening an issue on GitHub. 👍 PW
[Magisk] Boom_Hacker:
Thanks,but i am giving up.KernelSU runs well.
[Magisk] ZG_DEV:
** Update : flashed magisk using twrp and the phone took a little time to boot, now the update is installed successfully, the phone is a bit laggy, but good that I have updated magisk 😁
[Magisk] woozie.2007:
Hi, is there someone who installed magisk 27.0 on a mi 9t? For me, from the magisk 26.3 when i updated it to 26.4 and nothing worked, i had to uninstall magisk completely. Now i wish to find out if magisk 27 is working well on my phone. Thank you
[Magisk] GreenDotBlue:
Magisk (latest stable) isn't patching these images what to do? Not extracted non non-extracted. But then how to get patched boot.img rooted rom?

Andy Yan's personal builds // GSI - Browse /lineage-18.x at SourceForge.net

sourceforge.net
[Magisk] mathysp:
I'm using a Samsung A127F/DSN (A12s...)

FRP Unlocked and OEM OFF (U) Fully unlocked

Can anyone help me with Magisk, I've done the rooting part so flashing the custom AP file and it luckly didn't bootloop. But when I do the normal Samsung setup and then reinstall the Magisk app it says installed N/A and I can't use root.

Someone helped me with the bootloop part, would it be possible if someone could help me it is done in the thread linked below.

Thanks in advance!

thread: https://xdaforums.com/t/bootloop-after-flashing-magisk.4660510/
[Magisk] mrgbuzz:
I am trying to install Magisk and I have it a stumbling block. Copied to the boot.img to my device, done the pull request. But when I try to flash fastboot, I get the "waiting for any device" message. Its weird as fastboot/adb is working. All drivers are fine. Any suggestions please?

Poco X5 Pro, Bootloader unlocked, custom rom. Device showing in ADB Devices.
[Magisk] badabing2003:
It's your device in bootloader mode?

It would like is waiting for that.
[Magisk] mrgbuzz:
I got it sorted eventually. Between my fat fingers and bootloader mode. Thanks
[Magisk] Gemini3B9TL:
I can't access superuser and modules they are both locked
[Magisk] BillGoss:
Your phone isn't rooted! The top section of your screenshot shows Magisk "Installed N/A".

Installing the Magisk app isn't enough to root your phone.
[Magisk] J.Michael:
If you had Magisk working just before you tried updating by installing the v27 app, maybe you had the manager app hidden. Check your app drawer for the name you gave the manager app when you renamed it. If you don't remember what you named it, look at every app in the drawer.

Or search this thread for something named "TBChecker" (or something like that). It has the interesting side-effect of locating the renamed manager app.
[Magisk] Schmye Bubbula:
Where, exactly? I ran every check in my TB Checker v2.7.4.r344.d28eb46, and the Xposed Check found my hidden app's Magisk Random Package Name, but I don't see the app name I gave it anywhere. (Maybe Kitsune hides it better.)
[Magisk] J.Michael:
Cross reference with "pm".

Help is "pm help" or "pm -h" -- why would it be "pm --help" like so many other programs?

I don't see how to get the name in the app drawer, but it looks like you can use pm to uninstall the package by package name, so if you were really trying to recover from having lost track of a hidden manager, that might be good enough.

Other than that, all I can think of is to search this thread to see if anyone covered that.
[Magisk] bombadier:
Latest canary Update 27002 will not let me hide the Magisk app, get a failed toast, tried opening an issue but need to use the debug version,

Installed the debug version and it works and hides the magisk app?
[Magisk] badhabit_wb:
Same here. P8p. Haven't installed the debug version Edit. can hide magisk with debug version
[Magisk] pndwal:
Latest Canary/Debug Magisk:

Magisk (81658d45) (27002)​

[General] Use a minimal libc to build static executables (magiskinit and magiskboot) for smaller sizes

[MagiskInit] Rewrite 2SI logic for injecting magiskinit as init

[MagiskBoot] Support spliting kernel images without decompression

[App] Support patching Samsung firmware with images larger than 8GiB

[App] Use user-initiated job instead of foreground services on Android 14

Diffs to v27.0​

https://github.com/topjohnwu/magisk-files/blob/3180e66585494131b76b498531c2d3a56e56e69b/notes.md

👍 PW
[Magisk] sawdoctor:
How the heck are you supposed to file a bug report? You use the broken version and your post gets automatically closed by the bot. You use the debug version as required but that doesn't have the bug.

I get it i really do they must get 100s of useless bug reports but this one is daft. Maybe only option is to open a bug report with the debug version but explain the issue is only there on none debug