yashsingh1/xdaforums huggingface dataset:
[Magisk] ipdev:
Momo is very depressed

We have to keep Momo away from Marvin. 👀

“Sorry, did I say something wrong?" said Marvin, dragging himself on regardless. "Pardon me for breathing, which I never do anyway so I don't know why I bother to say it, oh God I'm so depressed. Here's another one of those self-satisfied doors. Life! Don't talk to me about life.”​

​

“Simple. I got very bored and depressed, so I went and plugged myself in to its external computer feed. I talked to the computer at great length and explained my view of the Universe to it," said Marvin.​

"And what happened?" pressed Ford.​

"It committed suicide," said Marvin and stalked off back to the Heart of Gold.”​

- Douglas Adams, The Hitchhiker's Guide to the Galaxy​

:cowboy:
[Magisk] pndwal:
I could keep this up all day, 'n I love the way you mind works although I'm now quite sure it's equally flawed, and I'm concerned for your reputation and repercussions from the mice here who are really... just too sane.

I'll have you know I'm taking my pills prescribed by cybercorp corporation and am no longer depressed at all! Actually looking for more doors to open... Take care, Marvin.
[Magisk] ipdev:
One more before we let the thread get back to normalcy. 😉

“A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.”​

- Douglas Adams, Mostly Harmless​

:cowboy:
[Magisk] HippoMan:
In other words, is the user's mind the real location of the artificial intelligence?
[Magisk] pndwal:
https://github.com/vvb2060/KeyAttestation/ v1.5.0 👍 PW
[Magisk] zgfg:
Or is it Momo developer's mind that decides if your phone is rooted or not😁
[Magisk] zgfg:
Now, with Bootloader Spoofer, Bootloader is no more locked for Key Attestation v1.5
[Magisk] chiteroman:
They patched it, I will try to fix it.
[Magisk] zgfg:
Please update as v1.1 with the same package number and can you please make it that LSPosed offers update (like for the other LSPosed modules)

Thanks
[Magisk] chiteroman:
Updated :) https://github.com/chiteroman/BootloaderSpoofer/releases/latest
[Magisk] zgfg:
Thanks
[Magisk] phuhcue:
I've checked it and rebooted with no success. I thought there were 2 different things selected by default before.
[Magisk] HamsterHam:
I checked the safetynet test app as well.
[Magisk] jsaxon2:
Do you have other modules loaded or just phh? I was having a weird issue with a MOD that would sometimes allow hide to pass safetynet and sometimes not. I've disabled it until I can investigate further. If you have other modules loaded, maybe try and disable all except phh and see what happens.
[Magisk] andrew2432:
I asked in v7 lol
[Magisk] phuhcue:
No change.

Well, if anyone figures out how to pass SN on this device post your method. Thanks.

Tmo Note 5 SM-N920T.

---------- Post added at 02:58 AM ---------- Previous post was at 02:56 AM ----------

Just phh. No xposed either btw.
[Magisk] westeight:
Okay, finally figured how to pass SafetyNet with Xposed activated:

SuperSu v2.78-SR3

SuHide 0.55

Magisk v9

Xposed 86.6 systemless

Root Switch v1.3.3.2
[Magisk] preusstang:
I'm having issues getting checked items to stay checked in the new Magisk Hide section of Magisk Manager 2.5. If I navigate to another section and come back, the checks are gone. If I back out with the soft key and come back, the checks are gone. If I check and pull down to refresh, the check is gone. Is this intended behavior?
[Magisk] mrxtc89117:
I'm also experiencing losing root with the magiskhide switch on when reboot sometimes. This was present in previous magisk versions. The phh-superuser-266-2 will not be shown in the modules. A reboot usually fixes the problem and I have root again.

This is on an LG G3 ls990 Sprint running Team Exodus 6.0.1 MM rom. Magisk v9. No other modules installed.
[Magisk] andrew2432:
Su+Su hide+magisk? This the order you used exactly? Xposed 86.6 for magisk? What do you do in Su hide? What's your root switch settings?
[Magisk] SDMU:
A query regarding the magisk hide option .

Will selecting an app prevent it from detecting root or will it prevent other apps from detecting that the selected app has root access ?
[Magisk] hokiealumnus:
Is anybody willing to upload a copy somewhere else (with [MENTION=4470081]topjohnwu[/MENTION] 's permission)? I have tried everything I can think of and it just won't flash.

Edit - Got it sorted using magisk manager. Expected, but warning to others: G3 users will get a secure boot error if you don't bump after letting it install!
[Magisk] SDMU:
Did you try installing v9 using the magisk manager ?
[Magisk] mrxtc89117:
You have to repack it. Unzip it and then zip it again. I used WinRAR. I think the twrp version for the LG G3 cannot handle the format for some reason.
[Magisk] westeight:
Yes, in the order listed. Xposed 86.6 for Magisk.

SuHide + Su Hide GUI...
[Magisk] hokiealumnus:
This worked! I assumed it wouldn't and it had to be installed via recovery. Thank you!

Edited my post above. General FYI, G3 users have to bump after installing (which is why it's easier to install via recovery; you're already there to bump).

Very strange! Thank you for the insight. If using the app didn't work, I'd have done this. Great alternative though, and I'll probably repack it to keep the zip handy. Thanks!
[Magisk] andrew2432:
ALL LG will need boot bump I believe...

Install magisk

Cbump

Phhsu

Then more if you're brave!!
[Magisk] hokiealumnus:
Yea, it has always needed bumping. It was just easier to install from recovery - magisk, phh superuser, bump, then boot. Using the app you just have to pull battery and boot into recovery to bump.

Totally not a big deal, just posted that so people didn't freak out when they got the blinking LED. :)
[Magisk] jcrompton:
Running a PN based ROM on Nexus 6

Installed latest Magisk v9

Then rebooted

Then installed the phh root in Magisk, after installing Magisk Manager

Rebooted, then set MagiskHide, rebooted

Passed SN !! Play PoGo

My problem ... I then installed Blackbird kernel and SN no longer passed

Would this be normal behavior with installing a custom kernel?
[Magisk] Didgeridoohan:
It's all explained in the official announcement thread.
[Magisk] SDMU:
Is the Magisk hide option similar to SUhide ?
[Magisk] zgfg:
For tomorrow (ETA?) prepare a little sticker to put over your selfie camera and be ready to pass the brand new 'A'I Momo v5

Or use a sun glasses and keep a calm poker face🥸😻

Edit:

The saga continues and a chapter about Momo and root-hiders is still missing:

https://medium.com/dose/an-epic-history-of-masturbation-around-the-world-366a68618b35
[Magisk] kevinco1:
I'm from the US and haven't seen this till now but always see 'masturbation' made to describe Momo

What does that actually mean? I feel it's worthless to use the app myself and a waste of time even though many do.

Is this how it connects, that using Momo is a waste so sitting around by yourself and....?
[Magisk] zgfg:
Yeah. It's a colloquial term. Been used here on XDA long ago but I don't know who invented originally. I see they use now also on the Alpha TG channel - although today about the KeyAttestation update and the follow-up return from Bootloader Spoofer
[Magisk] pndwal:
.... and if you understand,

👀 PW
[Magisk] pndwal:
Looks like it's going again anyway:

Remove randomness from Magisk

topjohnwu committed 8 hours ago

vv's change temporary only? 🤔 PW
[Magisk] tupu4545:
Hello I'm on android 12 and have Magisk 26.1 enabled. I have SystemUI Bootloop saver installed along with some other modules, recently my system has been crashing/rebooting a lot and upon checking the logs of systemui-bootloop saver in /cache is just "SystemUI is having trouble, so disable all modules and restart"

Is there anyway I can properly diagnose which specific module is causing my system UI to crash?
[Magisk] J.Michael:
I take it that Bootloop Saver is successfully disabling all modules, and you are getting back into your system.

Re-enable some modules and try again. If it works, enable a few more modules. It's up to you to decide whether rebooting is such a burden that you want to keep track of which modules are in which group, or just enable one at a time so when it fails, you know who is responsible.

Be aware you could have more than one problem module. And you really shouldn't have too many modules -- I have no idea how many is too many.
[Magisk] pndwal:
Fresh from Kyiv, update available for @Displax USNF mod fork (MIUI, custom XiaomiEU fixes 👍):

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/

Per:

Nb. Update JSON channel is not pointing to his builds (still aliased to official @kdrag0n builds AFAIK) so need to manually update.

👀 PW
[Magisk] pndwal:
With the recent change,

New magisk tmp dir: /debug_ramdisk, debug_ramdisk replaces /dev/<random_string> as TMP dir in devices where there's no (Magisk accessible) /sbin from Canary, 26102...

I am hoping to learn if PI deviceIntegrity still requires hiding root from com.google.android.gms (GMS Core) in addition to com.google.android.gms.unstable process (attestation / DroidGuardService) where Magisk uses debug_ramdisk as path, or if having root hidden only from the latter will now be enough as it is where /sbin is/was path...

Perhaps a member with XiaomiEU or similar custom ROM with integrated SNF or a like (basic attestation fallback) solution (so don't need/use USNF) who also runs Magisk could check tmpfs mount path = debug_ramdisk by running

su
magisk --path

in a terminal emulator app and let me know if adding the Google Play Services (attestation / DroidGuardService) process com.google.android.gms.unstable to denylist is enough to pass PI deviceIntegrity, or if (GMS Core) process com.google.android.gms is actually still needed also.

Thanks, 👍 PW
[Magisk] Leovre:
Hi, I've got this problem with magisk:

One plus nord asked me to update and I press yess by mistake, luckily it did not bootloop but I lost root, so I started magisk app and it said me: as you do not have root, hidden version of magisk is not needed, would you like to install normal one, and i press yes.

Then I noticed that hidden version was still there and I uninstall it like a normal android app

After that I tryed to root device with patched image metod but magisk app does not find root..

Is it possible that old hidden version of magisk manager is still active?

I do not have uninstall options on magisk app, and I do not have twrp on phone

so is there a way to erase all magisk and start from beginning with a new installation?

Thank you
[Magisk] badabing2003:
If you do adb shell and connect to the phone

Can you do su and see if it works?

Either way it sounds like you have multiple Magisk Managers.

Install TB Checker from Play Store and run it, if you have Magisk installed (hidden or not) it will find it and tell you the package name.

Uninstall and repeat until there are no more Magisk.

Reboot

Install Magisk and then root

By the you uninstall Magisk app just like any other app, from app info.
[Magisk] pndwal:
... further, Magisk full app or renamed stub app sometimes doesn't show in launcher applists... You may need to locate these in device settings, Apps... PW
[Magisk] zgfg:
Follow up on this:

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/post-88658109

In short, I upgraded my daily driver Xiaomi Mi 11 Lite 5G NE (Lisa) to Xiaomi.eu (Stable) MIUI 14.0.8/Android 13 (Sec. update April 1)

Since I Factory reset, I had a 'chance' to clean install everything

This time I chose Magisk Canary, latest v26102 (previously I was on Xiaomi.eu MIUI 13/A12 with Magisk Delta latest v25210)

So far, so good. Eventually I made all important detectors to show green (with Zygisk, DenyList, Shamiko, App Data Isolation for A 11+, LSPosed, HMA, Dev Opts Hide, Bootloader Spoofer) and more important, that all apps I do use privately or for work don't complain about by 'root'

I don't need USNF since it's built-in to the Xiaomi.eu (custom ROMs based on debloated official MIUI, as such they require unlocked BL for installation but then, if you don't install Magisk, you can pass out-of-the-box Play Integrity (Basic and Device integrity) and SafetyNet (Eval type Basic)

Of course, I use other modules like Systemless Debloater, Built-In BusyBox, ToyBox-Ext, YouTube Revanced Ext and YouTube Music Revanced Ext, ViperForAndroid Repackaged, James DSP with AML, Trichrome Library Squash (for deleting deprecated Trichrome libs) and UpdateLocker(for detaching selected apps from Playstore) and Proximity Fix4Xiaomi (Xiaomi release phones with only a virtual Proximity sensor, causing troubles when making calls - screen could suddenly unlock.and your ear can touch buttons like Hold, Bye, Airplane mode, etc, without your without your consent - that module successfully fixes the issue)

And LSPosed modules AOSP Mod and CustoMIUIzer (eg for enabling Smart unlock by WiFi and BL - usually blocked on Xiaomi ROMs)

Last but definitely not the least, have successfully installed Magic OverlayFS, mounting my read-only System partitions as read-write. With Magisk v26102 (not Delta) and with the Xiaomi.eu kernel as-is (no custom KSU)

And root apps like AdAway, MiXPlorer, SMaid, Swift Backup, NH Terminal emulator

(Ie, rooting and flashing is not just an addiction or fashion for me and the phone is not a polygon for me for the useless mas*rba*ion testing)

Everything works fine, smooth and stable. Netflix with L1 Full HD, HDR Dolby Vision...

When time permits, I will install (again) Screen2Auto and Fermata (root versions) for Android Auto
[Magisk] wilsonhlacerda:
Thanks for detailed description of your setup. Does DevOptHide do work for you? It does not for me, neither the similar I Am Not A Developer LSPosed module (I'm in Lineage), Ruru and others detect USB Debug no matter using them or not.

And Bootloader Spoofer is another that has interesting results: some (only some) of my banks crash if it is hooking them, but works fine without spoofing. Clearly those banks are able to detect hooking and/or the module has a bug that cause them to crash.

By the way I use HMA with same banks without problema, so it suggests that is not LSPosed hooking itself that is making them to crash.
[Magisk] zgfg:
Everything that I listed works for me or I needed for something

Fully passing TB Checker, S Check, Ruru, Oprek and Applist detector. Not Momo and Native Test. And BL Spoofer spoofs Key Attestation

All MY banking, e-citizen and loyalty apps work for me - I cannot and wouldn't speculate for others (neither test)for other banks and other countries and so
[Magisk] chiteroman:
Try this: https://github.com/Dr-TSNG/NativeDetector/releases/latest
[Magisk] zgfg:
I wrote in that or the follow up post that Momo and Minotaur do detect root

But I ABSOLUTELY DON'T CARE for them
[Magisk] tim1aust:
2 questions in re. PixelFlasher and P7a.. a) is P7a supported yet? (seems like yes) b) is PixelFlasher from AUR for Manjaro *at the same build level* (it has 5.3.1.2 in lower left)as the one from Github, et.al?

I figured it would be easier to just have a supported AUR package, so I installed that. But when I tried to use it for P7a with latest Full image, it couldn't patch the file (said it couldn't find boot.img). Of course, for P7 & P7a, it should firstly be looking for init_boot.img. Could it be due to the fact that this was a new phone which didn't yet have Magisk installed? (I guess that's 3 questions :) Anyway, I wound up gettng Magisk installed from scratch, so my P7a now has it installed. I'm hoping to use PixelFlasher from AUR next time.

TIA,

Tim
[Magisk] J.Michael:
Try the PixelFlasher thread where @badabing2003, the author, is more likely to notice.
[Magisk] sawdoctor:
The pixel flasher in the aur is built by a manjaro team member from original source so is the same. The Ubuntu version runs on manjaro as well so you can use that version if you prefer
[Magisk] badabing2003:
Actually, last I checked it is creating a package using the Ubutu build from Github, the one I publish, so it's just packaging so that it is easy install with the system's package manager.
[Magisk] Leovre:
Sorry for delay, First time I could do adb shell and su,

after some magisk install, uninstall, flash patched image, now I do not have permission for su

TB Checher says this for root check, xposed check is all ok but fail Hide mock location (that was a module I activeted in hidden magisk)

I tryed many times to install magisk manager and flash patched boot.img but fresh magisk manager does not see root

Maybe should I just flash unofficial twrp for one plus nord, flash magisk unistaller.zip from twrp, flash stock boot.img and restart all from beginning?
[Magisk] J.Michael:
Did you install Magisk the first time? Or was it part of the ROM you are using?

If the problem is yet another hidden Magisk manager app, flashing the boot image, patched or not, will not help.

I know TBChecker can supposedly detect hidden Magisk apps, but check the system app list yourself anyway. Do you remember the name you gave Magisk when you hid the app?

If you have an "su" app, and just don't have permission to use it, then figure out where it came from. You should be able to see what the file is, you might be able to read the file to see if it has a version string buried in it.
[Magisk] amk316:
hi

just bout my s23 yesterday and rooted it with magisk alpha

and i tried to modify "/optics/configs/carriers/single/XGS/conf/system/cscfeature.xml" but its read only

i use to modify it on my s20 with no problem!!!

did i miss something?
[Magisk] zgfg:
Yes. New phones have read-only System hence you cannot modify files by root explorer, Terminal and so

Only modules can do by using systemleess mounting at the time of booting for the particular system files they want to change

Or, if you have KernelSU, then you can use OverlayFS module that will mount System as read-write for you. Again, there are no hard changes but you can then make modifications at any time after boot. And when you disable or uninstall KernelSU, mounted changes will be gone
[Magisk] chiteroman:
Download: https://github.com/Magisk-Modules-Alt-Repo/magisk_overlayfs

Modify mode.sh: export OVERLAY_MODE=2

Install and try again.
[Magisk] chiteroman:
The best option: unpack super.img, unpack system.img, modify it, pack them and flash super.img
[Magisk] pndwal:
Latest Canary + Debug builds:

Magisk (a8c4a33e) (26103)​

Lots of code is migrated over to Rust!

[MagiskBoot] Support cpio files containing character files

[MagiskBoot] Support listing cpio content

[App] Support patching boot image from ROM zips

Diffs to v26.1​

[MagiskBoot] Support extracting boot image from payload.bin

[MagiskBoot] Support cpio files containing character files

[MagiskBoot] Support listing cpio content

[Daemon] Make daemon socket a fixed path in MAGISKTMP

[resetprop] Support printing property context

[resetprop] Support only printing persistent properties from storage

[resetprop] Properly support setting persistent properties bypassing property_service

[MagiskSU] Support -g and -G options

[MagiskSU] Support switching mount namespace to PID with -t

[App] Support patching boot image from ROM zips

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

👍 PW
[Magisk] traversone:
1st feedback: impossible to upgrade in LOS 18.1 on Samsung S5--> it does not recognize the boot image format (both from within the Manager and in TWRP)
[Magisk] pndwal:
Interesting... Can you screenshot errors?

Is it boot.img?... Does Select and Patch a File work with unpatched .img? PW
[Magisk] traversone:
good question and quick feedback: patching of stock image is successfull !

edit: Android Box with Amlogic 32bit architecture: stock boot (regularly patched by 26.102 manager) fails as per 3rd snapshot
[Magisk] zgfg:
On my Xiaomi, I patched the boot.img that was previously patched by 26102 and 26103 works so far all ok
[Magisk] pndwal:
... So a fix was needed for "Direct Install" fails on arm (v7a) devices #7114 opened 11 hours ago by ipdev99 (Thanks doc!)... Fix:

Fix mmap block device #7115 (@yujincheng08)

😋 PW
[Magisk] pndwal:
... Also coming, @osm0sis' fix for new payload.bin boot patching; broken from hidden/stub App:

Ensure magiskboot is executable for payload.bin processing #7108

And @yujincheng08's fix for late Android GKIs, eg beta A14 for Pixel 6 Pro:

Fix backup fails when ramdisk does not exist #7111

among others... 👍 PW
[Magisk] DaOldMan:
For some weird reason even on the latest canary 26103 every app in the denylist crashes when zygote and denylist are enabled. When not in the list they work fine. And it's ANY app, so it doesn't matter what I put there. I tried my medical app, crashed on the spot :-( . No problems on older 25 version ....

It's on my ViperOS rom which is Nougat 7.1.1 on Note 3. No idea what's wrong. Had to patch the kernel manualy though - unsupported format error.
[Magisk] J.Michael:
What unsupported format error?

What did you do to the kernel?
[Magisk] pndwal:
Mmm...

I have seen that reported before... Not sure if it was properly addressed in GitHub issues or if confined to custom ROMs...

This current issue looks similar however:

Opening apps causes the system to crash and reboot sometimes, if Zygisk is used. #6569 opened on Jan 27 by MarisaDAZA

Looks like custom ROM implementation may be an issue in your case and devs may not be interested therefore, but I'd probably post a report in that thread if I were you... Best to move to Magisk Debug and Include logs if possible... See what they say...

🤠 PW
[Magisk] pndwal:
Think he meant boot.img by 'kernel'(?)... Not strictly correct, but think he means Magisk-patching failed (direct install?) but patching (unpatched) image worked... This is most likely due to arm v7a issue however... See:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88681203 🙃 PW
[Magisk] zgfg:
I have kind of opposite issue but on arm64-v8a - my old Xiaomi Mi 9T with Xiaomi.eu 12.5 / Android 11 (case known as "Ramdisk No" as always reported by Magisk but also always successfully patching the boot.img)

Patching stock boot failed, re-patching the previously patched boot.img (as well as direct install) worked

But a much worse issue:

After installing 26103, my TWRP 3.7.0 does no more ask for pin and thus became useless

It's TWRP from TWRP.me and I happily used it for almost two years, until this Magisk Canary 26103

Last time I successfully used TWRP just few days before Canary 26103 (still working with Canary 26102) and it worked as usual - asking for unlock pin at start

Now it does not ask and shows only scrambled files names on Storage).

Since its old (and my second) phone, I use it only for Magisk, browsing, playing music). Last ROM was upgraded two years ago. Hence, now this problem with TWRP must have been caused by Canary 26103.

And reinstalling TWRP did not help