yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Yeah. I was thinking about to put the parallel with BIOS into my post or not but eventually decided to skip since there are differences between the BIOS on the PC compared to Bootloader/Fastboot/Recovery on the phone

But generally, if BIOS is not locked, you don't need root (Linux) or Admin (Windows) privileges to wipe your PC and to install a new OS

Similarly on the phone. If Bootloader is unlocked, even somebody else (who has not even the user account on the phone) can flash whatever he wants to that phone

However, he may have a problem with the previous Google account (even on the new ROM, Google will ask for the previous user's Pin to unlock the screen if Google account was not signed off before flashing the new ROM - Google's protection from stealing the phones), but if the new ROM is GApps free (or not an Android OS like he dreams off), then no problem

That's what I wanted to emphasize - he doesn't need root (Android superuser privileges) to flash a different ROM. All he needs is to unlock the Bootloader
[Magisk] martyfender:
I tried this ca build:

Fix avd hack #2989​

this build boots as normal on my system. I have only been cherry picking ca or action builds to try, using some of the newer ones signed off by topjohnwu.
[Magisk] manjaroid:
Deletions in /data/adb may not be necessary, it's just a step that ensures a clean start, particularly when downgrading leaves remnant files from the newer build. I've never needed to delete these files but it's still a good tip to know. Restoring the boot image and completely uninstalling 25211 through the app should be enough to start over with 25206 and get systemless hosts working again.
[Magisk] zgfg:
Few comments - properly and successfully uninstalling the Magisk (by flashing the APK renamed to uninstall.zip or by use of the big Uninstall Magisk button in the Magisk app, main screen) will also delete all Magisk stuff from /data/adb

However, just restoring the original boot.img will not delete /data/adb - Android will boot without Magisk, hence Magisk will not read /data/adb (ie, that folder will be ignored for the moment)

But the next time you boot with the patched boot img or you reinstall the Magisk, then Magisk will find all its previous stuff remaining in /data/adb - it will automatically load your old modules and everything

That's why it is recommended to properly uninstall Magisk and/or (if uninstalling for some reason does not work) to manually delete /data/adb (through TWRP if possible)

Of course, Factory reset or wiping or formatting /data will also wipe the /data/adb folder (but dirty flashing a ROM will not wipe /data/adb, hence it will remain as a time bomb for the next time you install Magisk - Magisk will find and load old modules, that may no more be compatible, causing a soft brick)
[Magisk] m0han:
I know. See the part I quoted.

My question was whether this would work as required. @pndwal's answers in this post seem to suggest it would.
[Magisk] zgfg:
Ok but that was also implicitly in my response - I thought that it was understandable...

Actually, when you flash Magisk apk (it does not need to be renamed to zip - depending on the particular TWRP version).

TWRP has to process certain scripts that are packed into the zip (rename magisk.apk to zip, unzip and investigate the content of

META-INF/com/google/android

folder/updater-script, open as text fie)

Hence in that case it is actually TWRP commanded by a script packed into the zip, that can warn or block to flash.

There is no such script in the raw IMG file, raw IMG is just a binary blob that TWRP or Fastboot dump to the selected partition, hence flashing the patched boot.img should work as usual
[Magisk] m0han:
When I ask questions and/or seek help on something, I wish for answers/solutions that would be beneficial - while being easy to comprehend - to a wider audience; not just me. @pndwal and you seem to have answers to all the questions thrown here. In this case, his answer was more to the point, IMHO. Thanks for your help.
[Magisk] Spartacus500:
Please help, i won a new custom Rom 9.0 Pie has system 8.0 In twrp, tries to root magisk 20.1 , 22.3, 25.2, and every time magisk root not installed :(
[Magisk] zgfg:
What does it particularly mean "magisk root not installed"

Did you try su or magisk -c in Terminal emulator?

If Magisk app just shows Magisk N/A - make sure that you didn't leave your old magisk app renamed/repackaged by Hide Magisk app
[Magisk] Spartacus500:
Reinstalled 9.0 Pie NFE 2.2 on S7 Edge, trying for 5 hours to root this Rom but every time In magisk manager 25.2 or lower it says root is not installed :( I flashed root on this 9.0 Pie from 3 years ago and without I managed to root the problem and now it doesn't work, please help :(
[Magisk] Lughnasadh:
Looks like Beta 26.0 has been released.

Release Magisk v26.0 · topjohnwu/Magisk@7cb0909

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Magisk] napster113:
Works fine on my s6 edge plus with stock rom.
[Magisk] andrew2432:
It has issues. Samsung needs wanam xposed.

Search for wanams build for exposed, or try a cache wipe in twrp

Which android os are you on? MM? Have you gone system less 2.78 or s till with magisk? Which xposed version did you use, newest systemless, is that 86.6?? Carrier?
[Magisk] napster113:
MM + 2.78r1 systemless + magisk + exposed 86.6
[Magisk] andrew2432:
Tjw Magisk + cf 2.78??? Blasphemy!! Are you able to pass sn???
[Magisk] napster113:
No but that doesn't bother me.
[Magisk] andrew2432:
But snapchat...pocket monsters...the ever useful android pay...

I'm jealous haha. Why did you go with this method then if you don't mind me asking??

I'm tryin to more effectively cheat at pgo mostly...lol
[Magisk] napster113:
Originally I wanted to go systemless for pogo and ota's but I don't play pogo no more so I've left it as is.
[Magisk] AntholifeV2:
Hello ; I use audax rom on samsung galaxy s6 edge +; after magisk flash my phone bootloop... it comes from the boot.. HELP please. :)

Envoyé de mon SM-G928F en utilisant Tapatalk
[Magisk] Nomelas:
hey guys, so I want to encrypt my phone but I want to stay rooted with magisk and xposed. (Using SuperSU 2.78 SR3)

Are there any special steps I need to take before I start the encryption proccess? do I need to completely unroot and remove all traces of all these before going back or will it just work?

Thanks for any advice!
[Magisk] jadajada:
Is there any way to hide root with Magisk V8? I used V6 earlier and I could toggle root on/off. I don't see how I can do the same with V8. There is a Magisk Hide option, but that does not work. The app I am trying (Vipps = a Norwegian payment app) says that rooted devices are not supported. It used to work with the V6 on/off toggle. What now?
[Magisk] andrew2432:
Gone are the days of the v6 toggle switch. Unmagisk to pass. Safety net is the issue, To pass safety net while rooted is a chore. You need to systemless root and a program called root switch and/or root hide. Smoe devices do it no problem, others soft brick
[Magisk] Alxoom33:
You will also need xsetprop to hide your unlocked bootloader.
[Magisk] andrew2432:
Any idea what the difference between root and unlocking the bootloader is? I've seen that it's different things. If you have system less su is xsetprop still necessary??
[Magisk] Alxoom33:
Typically you need to unlock the bootloader in order to root your device. There are a few exceptions which you can look up with regard to the old locked S4's and Droid Bionic devices. Xsetprop is still necessary for systemless su, as far as I know.
[Magisk] Didgeridoohan:
Have you added the app to the blacklist (as explained in the official Magisk announcement thread)?
[Magisk] Alxoom33:
Don't know about Norway. But in the US SafetyNet detects Magisk and any device using Magisk to hide root or an unlocked bootloader will not pass SN.
[Magisk] Didgeridoohan:
We don't know if that app uses SN... A lot off apps use their own detection methods.
[Magisk] andrew2432:
Necessary for what? I've seen 1.3.3.2 rootswitch mentioned to hide both root and system installed xposed
[Magisk] Alxoom33:
To change the flag for unlocked bootloader state.
[Magisk] andrew2432:
Interesting, that will probably need to be my next read
[Magisk] martyfender:
Also, new canary builds.
[Magisk] immortalwon:
Should we upgrade, is the question? Is it stable and will it result in broken modules?
[Magisk] Nergal di Cuthah:
Works for me (mods systemless hosts and usnf2.4 mod 1.2 pixel 6pro march 2023 update)
[Magisk] majorfigjam:
And works for me, direct installed upgrade from 25206.
[Magisk] pndwal:
26.0 Changes:

😋 PW
[Magisk] pndwal:
Latest Canary (+Debug) Magisk:

Magisk (e2545e57) (26001)​

Sync with public v26.0 release

Diffs to v26.0​

None

https://github.com/topjohnwu/magisk-files/blob/76a6e7a53b6509dc6c2ae2974a2ea2a8b07d3a12/notes.md

👍 PW
[Magisk] Spartacus500:
26.0 work :) I only get this information every time 🤔
[Magisk] Nergal di Cuthah:
Some how you have the 2.6 boot but the 2.52 app. Check your downloads folder for the right version and make sure you don't have a hidden magisk and unhidden one
[Magisk] zgfg:
For the app your screenshot says v25.2 latest but v26 as installed - what is your Update Channel (Magisk app, Settings), is it Stable, Beta, Canary or some Custom?

Also, go to Magisk Install (top, right) and choose Direct install - it will hopefully help you to get rid of that Additional set-up required
[Magisk] pndwal:
Both 26000 patched image and App installed!... All is fine... 🙂 PW
[Magisk] ipilcher:
Magisk installation not working on latest LineageOS 19.1

I just installed the latest OTA update for my OnePlus Nord N200 (dre). After previous OTA updates, I've always been able to re-install Magisk with no trouble.

After installing the 20230405 update, however, the installation process (patch boot.img, adb pull patched image, reboot to fastboot mode, flash patched image to boot partition, reboot) all appears to complete successfully, but the Magisk app still reports that Magisk is not installed. I have tried both version 25.2 and version 26.0 of the app (flashing the corresponding patched boot image in each case).

Anyone else seeing this?
[Magisk] pndwal:
All good since you took reflash... Magisk now needs this when installing via zip installer package from custome recovery to set up selinux / module rules properly. 🙂 PW
[Magisk] Nergal di Cuthah:
Lol not you @pndwal i meant @Spartacus500
[Magisk] Nergal di Cuthah:
Do you have a hidden magisk and non hidden one that 99 percent of the time is why
[Magisk] pndwal:
Yes... @osm0sis already opened an issue... 26.0 / 26001 broke addon.d survival script. 🙁 PW

Edit: Actually, your issue is likely failure of to uninstall hidden App as mentioned above... Hidden (stub) + full apps causes conflict...
[Magisk] pndwal:
I meant this member too! 🙂 PLS check screenshots again... 🙃 PW
[Magisk] zgfg:
But for the latest available App it says 25.2 although 26 (newer) is installed, that's strange?!
[Magisk] pndwal:
Yes... Just checked Stable channel and JSON isn't properly set yet... Still sees 25.2 as latest... Canary properly shows 26001 however...

Edit: Ah, of course... We don't have stable yet!... It's Beta... 🤦 (Set channel to Beta to see all public updates!)...

Maybe they only want informed stable users to update ATM? 😝 PW
[Magisk] Nergal di Cuthah:
Oh snap, yes only "latest" lists 2.5.2. wonder why. thanks for pointing out
[Magisk] ipilcher:
I installed the APK, so I don't have an addon.d script (so I've always had to re-install after an OTA update).

With the latest OTA update, though, the re-install isn't working.
[Magisk] pndwal:
Yeah, I saw LOS and assumed!... Edited my post already... Do you have previously hidden app still? PW
[Magisk] Lughnasadh:
Stable 26.0 hasn't been released yet, only Beta and Canary have been updated. Stable usually gets released a day or two or so after the Beta has been tested by the masses.
[Magisk] ipilcher:
You are correct. I had uninstalled the hidden app, but I missed the fact that it also needed to be uninstalled from within my work profile.

Thanks!
[Magisk] pndwal:
Ah, of course... It's that cursed Alzheimer's again... Another post to edit above... Now, which one was it... Dear me... 🙃 PW

Edited post (will edit Release notes posts too...):
[Magisk] osm0sis:
Just Direct Install again after it shows this and it should work.
[Magisk] pndwal:
I think member means that's been done and all is good... Seems screenshots are in reverse order!... 😉 PW
[Magisk] pndwal:
@osm0sis

@dr.ketan noted:

Unable to mount system rw

@Displax says this:

Make module mirror read only

prevents mounting system rw... Could this be issue with addon.d?... 🤔 PW

Edit: Haha... Bit late... Looks like you've found issue is removing stub.apk embedding in magiskinit... Will follow new issue with interest when you make it... 👍

I'd still like to know the implications of Unable to mount system rw, especially for custom ROMs... It's just been closed with no further comment... 😶
[Magisk] osm0sis:
Alrighty, bombs away!

Fix scripts by osm0sis · Pull Request #6833 · topjohnwu/Magisk

manager.sh + boot_patch.sh: all listed files from boot_patch.sh header are required for boot patching, but stub.apk was being removed so install_magisk via addon.d.sh would fail without it; leave ...

github.com

Not sure about that rw commit... Will have to look into it on my devices. 🤔
[Magisk] dr.ketan:
Yes, really helpful to make system changes. Please have a look if can be bring back.
[Magisk] osm0sis:
Looks like I can still make changes on my Lineage 20 devices, to both the / (system) and /dev/*/.magisk/mirror trees. 🤯
[Magisk] dr.ketan:
Root explorer can also able to mount as rw (direct system not with magiskpath/.magisk/system)

Can this be done with script?

Thank you

Edit : issue is only with system, I can mount MagiskPath/. magisk/mirror/system_ext
[Magisk] osm0sis:
I don't see why not.
[Magisk] dr.ketan:
Can you please elaborate how to?

I am trying with

mount -o remount,rw %MagiskPath/.magisk/mirror/system but fails

Though

mount -o remount,rw %MagiskPath/.magisk/mirror/system_ext works
[Magisk] osm0sis:
It's because /system isn't a partition on your device, / is (system-as-root).

So you would need to remount the mirror itself since that's the actual mountpoint for the system partition: `mount -o rw,remount -t auto $(magisk --path)/.magisk/mirror`
[Magisk] ipdev:
Just do not tell that you can use AdAway in root mode without using the Systemless Hosts module. 😏

Most custom roms (even official Lineage) there is extra room left in system for addons like gApps.

If you are not a gapps glutton, you have room to directly write a hosts file to system.

/etc/hosts will be truncated as soon as you run out of room in system.​

Cheers. :cowboy:
[Magisk] dr.ketan:
Thank you! Worked like a charm.

Actually I have tried that y'day with messed little in hurry so didn't worked. I tried

mount -o remount,rw %MagiskPath/.magisk/mirror/

:ROFLMAO:
[Magisk] dr.ketan:
You are always helpful

Kindly accept token of appreciation and oblige 🙏

PayPal Transaction ID: 0380042829198345N

Regards
[Magisk] pndwal:
XiaomiEU custom ROM users:

Just a heads-up if facing issues passing PI deviceIntegrity w/ @Displax forked/modded USNF builds:

... May be useful, 👍

👀 PW
[Magisk] m0han:
I think @zgfg is one. He hasn't reported any related issues yet. Or, has he?
[Magisk] pndwal:
AFAIK he doesn't have issues...

I'm not at all sure if all or only some XiaomiEU builds are overwriting USNF props, but I have seen some reports of issues from XEU users. PW
[Magisk] zgfg:
I don't have issues , but I don't have MIUI 14 (only Xiaomi.eu 12.5 and 13)
[Magisk] Spartacus500:
The reverse of the photos, after uploading Magisk 26.0 via TWRP recovery, there was this information every time after opening Magisk manager, although root worked correctly 😊

I have installed Magisk 26.0 Beta 🤗
[Magisk] Spartacus500:
I did direct install and now this information is not there 🤗
[Magisk] Spartacus500:
Unfortunately, yesterday I was uploading a clean Rom 9.0 Pie NFE 2.2 and the same thing, after opening tb checker crash open, so the ideas are over, luckily it's only a root testing application, so there is no loss 😑
[Magisk] martyfender:
The new TB Checker crashes for me also on both of my devices.
[Magisk] immortalwon:
Something does not seem right with the new 2.6 beta magisk. Device seems slower and choppier. A lot of modules also not working. Hopefully people can port them and also find out why may seem slower? is it just me? Also Momo is detecting Zygisk trace files when before on 25.2 was fine.
[Magisk] zgfg:
For me, Momo was detecting Zygisk already with Canary versions v252xx (I don't use Beta and don't recall how it was on the corresponding Canary v25201)

But now I have something new in Momo: Permission system is abnormal, while the previous Found Magisk is gone

All other checkers, incl. TB Checker are still fully ok (except that Memory Detector, as usual, finds ReVanced YT and Music)

Modules work fine for me
[Magisk] immortalwon:
Thanks for your input. I went back to v 25.2 because its more stable and smooth.
[Magisk] zgfg:
Ok, I simply installed again ViPER4Android_FX_repackaged.zip (without uninstalling) and now Viper4Android works fine again under the new Magisk v26 (Canary v26001)
[Magisk] osm0sis:
Well it is the latest stable still! 🙂
[Magisk] zgfg:
MRepo update, in-app notification for v1.2.3

It downloaded the apk but I had to install it manually (although I gave it Install from unknown sources permission)
[Magisk] g000n:
Updated Magisk app to 26, waiting for modules to catch up before fully installing Magisk 26
[Magisk] Life_goes_on:
Magisk 26, Lineage Android 13- Modules do not install from local storage. Copying Zip to temp directory > Unzip Error

Same happened with Magisk 25

The kicker Fox's Magisk Module Manager install from storage no problem and the going to Magisk> Modules. The modules show up as install.

???
[Magisk] makaveliddon:
Great project
[Magisk] ctcx:
Finally tried checking the source code:

PixelFlasher/modules.py at main · badabing2005/PixelFlasher

Pixel™ phone flashing GUI utility with features. Contribute to badabing2005/PixelFlasher development by creating an account on GitHub.

github.com

If you could help with these doubts just once:

Why is "magiskboot cleanup" command needed?

If dealing with 64-bit devices anyway, why is it necessary to also copy -and rename- libmagisk32?

Is all the stuff inside lib/ strictly needed? I only copied/used libmagisk{32/64,boot,init}.so...

Is all the stuff inside assets/ strictly needed as well, or just boot_patch, util_functions, stub.apk?

Out of all flags KEEPVERITY, KEEPFORCEENCRYPT, PATCHVBMETAFLAG, RECOVERYMODE, SYSTEM_ROOT, how could I tell which ones I need exactly for the particular device I have?

Thanks again.
[Magisk] Kastilo:
Hello! It seems that I am missing a stock backup on the Pixel 7 Pro when trying to do OTA and I can't seem to find a fix at all? I flashed via patching boot and then using

fastboot flash init_boot <filename>
[Magisk] jons99:
latest shamiko messed up my lockscreen real good anything I can do about it other than flash the previous build which works fine as far as I can tell
[Magisk] pndwal:
Strange... v0.6-141 flash just fails for me w/o an Alpha Magisk build... Are you using Alpha?... Did it flash with official Magisk?... Why do you suspect Shamiko caused the lockscreen issue?... You don't mean fingerprint scanner do you?... PW
[Magisk] jons99:
never mind it wasn't shamiko causing it it was something else
[Magisk] CrimsonHeretic:
Does anyone have the custom rom of nokia c21 I've searched all over google ive only found for c21 plus. Or perharps its boot.img
[Magisk] kevinco1:
You need to post in the proper thread for this issue not Magisk support
[Magisk] CrimsonHeretic:
Okay pardon just didn't find the thread containing nokia c21 just thought I'd find it here
[Magisk] pndwal:
Latest Shamiko

Shamiko v0.7; Pre-release 0.7-161

Requires Magisk 26000+

Support Magisk 26.0

Fix font loading

Hide more traces of Magisk

Support zygisk loaded by native bridge

👍 PW
[Magisk] pndwal:
New Shamiko is hiding 26000+ Zygisk again! 👍:

Previously:

... Getting better... 🙂 PW
[Magisk] immortalwon:
Excellent, will wait for a more stable release though
[Magisk] pndwal:
Sure... But there may be another 26.x Beta and/or more Canaries before we get a Stable build... 🙃🤷 PW
[Magisk] Spartacus500:
Memory detector 2.0 still found zygisk 😏
[Magisk] pndwal:
Confirmed.

😶 PW
[Magisk] immortalwon:
where is the github page of this app?
[Magisk] pndwal:
Seems original links are removed/broken...

I can longer find MemoryDetector in @huskydg's GitHub or public Delta TG channel... (Seems the March 28 file posts have been removed)... The apk can still be found in @huskydg's TG chats for registered members however...

@huskydg or @zgfg may have further information... PW
[Magisk] zgfg:
Seems it's gone on GitHub, and cannot find on TG channel anymore
[Magisk] m0han:
If it's the .apk that is needed (and you don't have it), I can share here, if that is allowed.
[Magisk] immortalwon:
Would appreciate that, would like to test how it works, etc. But the real question: Why remove it in the first place? Probably no longer maintained
[Magisk] m0han:
Grab it before somebody deletes the post/file :D
[Magisk] immortalwon:
Pretty cool app, it seems good at detecting magisk zygisk and other module traces Someone needs to send this to shamiko developer and others who can fix this.
[Magisk] pndwal:
Please add it to denylist and post results again... 🙃 PW
[Magisk] immortalwon:
Good point, oof.Magisk v25.2
[Magisk] SwifterGrip:
After installing the Magisk module "terminal-systemizer-70.zip" from the Magisk application I had a Bootloop

After I understood that I immediately went to twrp and deleted the folder with the module in /data/adb/modules

This did not help.

After that I tried:

- Installing and uninstalling this module again with Magisk Manager 2019.4.4

- Enable and disable "Core only mode" with Magisk Manager

- Uninstall magisk with Magisk-uninstaller-20181022.zip, and install again

- Flash boot partition to boot.img image that I pulled from the original .zip firmware

- Uninstall magisk and flash the original boot again to erase all traces of magisk from the system

The folders "modules, modules_update, post-fs-data.d, service.d" are empty

No matter what i do i still have a Bootloop

In more details, phone doesn't boot beyond "Brand, powered by android" and after a while it restarts in FastBoot Mode

SOLVED!!!

It turned out I just needed to flash the same firmware over with TWRP, without any formatting

Just like during the update
[Magisk] pndwal:
Already discussed this with her on TG...

She said:

... I said:

She said:

I said:

Someone said;

😋 🤪 PW
[Magisk] immortalwon:
Thanks man, you are a very helpful individual. Always contributing and bringing knowledge.
[Magisk] Spartacus500:
For me, on the new version of Magisk 26.0 :), the information about detecting 'fingerprint has been tampered' is only on a clean loaded 9.0 Pie NFE 2.2 without root 🙄. If I knew what exactly this file detects...🙄
[Magisk] shoey63:
No problem here

Or with Momo

However Google remains a problem due to being blacklisted

ROG phone 3 Android 12

- Magisk Alpha 25211

- Zygisk enabled

- Zygisk Lsposed 1.8.6

- Shamiko 0.6 (141)

- HMA 3.1.1

- USNF 2.2.1 (Yes you read correctly, I don't want to be called a Pixel XL)

- MHPC spoofing Rog3 Android 10 to force basic attestation due to fingerprint mismatch.
[Magisk] immortalwon:
Magisk Alpha might be the reason you are passing the memory detector test. Interesting and thanks for the share.
[Magisk] pndwal:
FWIW, Dirty memories in libandroid_runtime.so/libart.so detection was resolved at least by 25209. 🙂 PW
[Magisk] m0han:
Delta too. Riru; not Zygisk.
[Magisk] rodken:
Enlighten me on the 'waiting for modules to catch up'.