yashsingh1/xdaforums huggingface dataset:
[Magisk] Captain_Throwback:
Also, one more reminder that if you're using Magisk v9, you do not need the xSetProp module anymore; as of the v9 release, it's deprecated and the functionality is built into Magisk.

And again, if you're only using Magisk Hide to pass SafetyNet, you don't need to add any apps to the hide list. Adding SafetyNet apps, Android Pay & PoGO is unnecessary because the SafetyNet process is already hidden by default. The list is only for additional apps from which you want to hide root, like Corporate Mail apps (AirWatch), banking apps, etc.
[Magisk] pndwal:
Haha... Are you still using (deprecated) MHPC with Force BASIC key Attestation option active?... 😂

The default setting spoofs Nexus 5 in Model prop(s) on Google devices and it seems it may also use Nexus 5 model prop value for devices unknown to MHPC...

That module sets props globally which may cause all kinds of issues... Probably interfering with targeted USNF/PIF model mismatch method (generally just adds a space chr to real value) too...

Uninstall it!... (Why would you use MHPC with USNF since USNF got Zygisk based solutions?) 😆 PW
[Magisk] Ambivalent_0_o:
I used to have the module installed, but as you said, since the PIF I have uninstalled MHPC and Safetynet. Nevertheless, another device is probably still being fooled.

I think that's why I have UNEVALUATED in the PlayIntegrity test for Play Licensing and my device integrity is now also gone because I played around with the pif.prop in PIF 13.1 and entered the fingerprint of my stock custom rom there...😥

i'm not an android geek either, i think i can manage a lot but i'm missing certain connections. that's probably why i make stupid mistakes in some essential places.... 🤫

Right now I'm a bit at a loss as to where I should continue or what is going wrong at which point...

I also follow this thread because I have the feeling that at least part of my problem lies there: Release v13.1 · chiteroman/PlayIntegrityFix (correct me if wrong 🥴 )

My Setup because it was asked:

I have an S10 with the custom Rom OneUI 5.1 for Exynos Galaxy S10 series with

magisk (hidden), PIFv12, lsposed, shamiko, banking apps, samsung apps - everything worked as in the stock state.

then the update to magisk 26.4 coming from 26.2.

first I updated every module he offered me and from then on nothing worked anymore, since then I only want to go back.

But also a downgrade to 26.3 or 26.2 (Shamiko version taken into account, the latest only works with the latest magisk version) has only made everything worse.

Meaning that I can login on google.com using the flawed device, but not into chrome app (which at first seems very similar to me, because both are basically Google, hence the comparison. but I know that from a technical point of view it's a completely different matter)
[Magisk] pndwal:
Oh... Sorry then... Your sure MHPC is uninstalled?...

Guess you mean USNF...

?

Is that Play Store Developer options check?

So custom ROM... Looks like it was spoofing Nexus 6P in September:

And now I'm more confused... Latest ROM seems to be March 17, or is yours later/different?... Or did you really mean Nexus 6P, not Nexus 5?...

Anyway, you may simply have registered Google account before changing to custom OneUI 5.1 ROM that spoofs one Nexus or another I guess... 😬 PW
[Magisk] Ambivalent_0_o:
That was actually my assumption. I did nothing more than remove the module in Magisk. This brings me back to the point where I thought MHPC had not undone the spoof of the device

(Nexus 5, I'm sure about the "5"). And yeah, March 17 is right.

When I just fiddled around with the PIFv13.1 in the pif.prop, the Nexus 5 was also there. I don't know where this comes from in the end, but I tried to enter my S10 there again (without really knowing why, but Nexus 5 seemed strange to me). I downloaded the mentioned custom ROM again and copied the fingerprint from the build.prob into the pif.prob. Since then the device integrity is also gone.

That's right

"spoofed" was the right word - blame deepl ^^ - meaning the remnants of Nexus 5.

No, I have apps: Integrity Checker, TB Checker and YASNAC

So any suggestions on what I should do now? 😬
[Magisk] pndwal:
I've just updated and looked at pif.prop, and see now fingerprint, product and device are set as bullhead which = Nexus 5x, so PIF seems to spoof Nexus by default...

Maybe you see hammerhead which = Nexus 5, or you really meant 5x?... If really Nexus 5, various devices may be used for default spoofing settings now...

Anyway, Mystery seems to be solved...

Try authentication with PIF disabled? PW
[Magisk] Ambivalent_0_o:
My fault again - it was "bullhead" before my first edit - so u r right with Nexus 5x

Deactivated PIF and the result is the same.

BASIC INTEGRITY ✅

DEVICE INTEGRITY ❌

Play Licensing: UNEVALUATED

Play Recognition: PLAY_RECOGNIZED
[Magisk] J.Michael:
What browser do you use when you are able to log in on google.com?

What is the "Chrome app" if it is not the Chrome browser?

Do you have an app (in your app drawer) that you recognize as the Chrome browser, and another app that you call the Chrome app but that is clearly not the same as the Chrome browser?

Look at the app info for both apps. Maybe click on "app details in store", and try very hard to identify these two apps in a way that makes it clear what they are.
[Magisk] Ambivalent_0_o:
Ok, that leads to more and more misunderstandings. There are not 2 apps. 🙈

I simply meant that I can use the Chrome browser, as you call it, to sign in to the google.com website.

However, it is not possible to log into that very browser (app) to enable the syncing passwords ect. stuff.

You know, the "login to sync your data across all your devices" type of thing - that's the thing not working.

In the end, it just shows that the problem is with my device and not with my google account. Nothing more. so sry for confusing you. ✌️
[Magisk] J.Michael:
You keep saying things like "log into browser". You don't log into a browser. You use a browser to talk to a web site. You might log into the web site.

As for "sync across devices", I think that gets to what I might have mentioned (I can't keep these subthreads straight) about the Google Account associated with the device: When you were setting up the device you were "invited" to Add an Account. I don't think a browser was involved, I think some Google app prompted you for your Google Account username and password. Now this Account is associated with the device. Even after doing that, when you opened a browser and went to google.com, you were not "logged in" as far as the web site was concerned -- you had to log in again, this time talking to the browser, before the Google website considered you to be logged in.

There was some problem that could occur if you flashed a ROM without first removing the Google account from the device. I didn't understand what could go wrong, I just followed the advice to delete the account from the tablet before running Odin.

Go to Android Settings -> Accounts and see if you have a Google account associated with the device. Maybe you have more than one Google account (I think that every Google account *is* a GMail address, and vice versa), and you associated a different account with the device than the account you keep logging into in the browser.
[Magisk] HippoMan:
Actually, you can indeed log into the Chrome browser. It offers a login option, and when logged in via a Google ID, you have access to additional Google services.

And using that browser (or any browser), you can, of course, log in to web sites that require their own login.

Those are two separate logins.

If I'm not mistaken, the problem being discussed is that for a given Google ID, login to the Chrome browser itself succeeds, but that same Google ID is not being allowed to log in (via Chrome) to a Google web site that allows syncing of passwords, etc.
[Magisk] Ambivalent_0_o:
Thank you sir, that's exactly what I am talking about :)

Except for this part

corret would be: "but that same Google ID is not being allowed to even open and login to play store on the phone. On my desktop I can access play store without a hustle. I can't get any google apps and services to start on my phone because it wants me to login - and that fails as said.

All web based logins via browser are working (even the ones where google sends me a sms code after entering my password, which in this case works). For example I was working with Google Sheets on my macbook all day long.

However, if I want to open play store or other g-apps, it also sends me this sms code when trying to login (or if you want some other verification method like backup codes), but then aborts with an error when given. I've posted that a few pages eralier with screenshots fyi.

Spoiler content hidden.
[Magisk] J.Michael:
Did you go to Android Settings, Accounts, and check that the account associated with the device is the same as the one you have been using to log into google.com in a browser?
[Magisk] J.Michael:
Can you describe what it looks like when you open a browser, do not go to a web page, and get a chance to "log into the browser"?

Do you get this offer when you open a browser on a desktop PC?

Does this happen with any browser other than Chrome?
[Magisk] Ambivalent_0_o:
Login to Chrome

Login to Google.com

Hope that helps, but it's the wrong direction anyways.

Sorry but that's way off the road and I think you're still misunderstanding my situation. 😓

Main problem is: Settings > Google > Login = not working

same with all google apps wich use this method

So no backup, no restore, no sync, no play store, no wallet - you name it...
[Magisk] Nergal di Cuthah:
Ok out of the box thoughts: any firewall, ipblock? Adblock? Lsposed? Do you pass PI? Other magisk modules not mentioned? Deny list? Sandbox?
[Magisk] Ambivalent_0_o:
cleaned everything up so now I only run Magisk 26.2 wich was the last one everything worked on + PIFv13.1, nothing else.

gained Basic + Device integrity back, but stil not able to login....

no firewall, no ip block, no adblock, only Play Services on Denylist, what u mean by sandbox?
[Magisk] Maka218:
Hello,

How do I find modules for my samsung? And how do I install them?

Im very noob at this, would appreciate a lot if someone can teach me.

Thank you
[Magisk] lorenzin:
The beginning of this article: https://www.makeuseof.com/tag/best-magisk-modules/ has links to the main Magisk repo and a quick overview of how to install them - hopefully this will get you started!
[Magisk] kind of android newbie:
Noticed a problem installing Magisk 26.4 on lineage-20.0-20231118-nightly running on River / Moto G7. Patching the boot.img from the Magisk app goes without a hitch, but when flashing the boot partition via fastboot, I get the following error / output:

:~$ fastboot flash boot magisk_patched-26400_cXLoE.img

(bootloader) is-logical:boot_b: not found

Sending 'boot_b' (26144 KB) OKAY [ 0.828s]

Writing 'boot_b' FAILED (Status read failed (No such device))

fastboot: error: Command failed

:~$

With the same cable / Linux Host system, using fastboot to flash the unmodified boot.img works fine as does flashing a boot.img patched with Magisk 26.3. Not sure what the underlying issue is, accordingly. Doing a direct install from Magisk 26.3 to Magisk 26.4 results in an unbootable phone, though again, I can recover by getting the phone into the bootloader and using fastboot to flash either the unmodified boot.img or a boot.img patched with Magisk 26.3.

Staying on Magisk 26.3 works fine of course, as a temporary work around. Any one have something similar happen?
[Magisk] molitar:
Unable to hide the app Malwarebytes it detects Root! How can I hide Magisk from Malwarebytes?
[Magisk] Nergal di Cuthah:
Research shamiko, deny list and "hide my apps" (hma). One or all of those should fix detection.
[Magisk] TraderJack:
@Eng.Raman I've been redirected to this post in many of my searches. I have this SDK error in Momo, yet I am using stock Pixel 3xl A11 ROM.

After I reflashed clean a week ago the warning went away and stayed gone throughout install of apps, Magisk, LSposed,etc. Earlier today it was gone, but it just reappeared and AFAIK I haven't changed anything.

What could be causing this? Can't be my ROM and I don't believe I've done anything (especially since last momo check) that would have deodexed anything.

Thanks

UPDATE: I believe I found the answer for my device. I've posted the answer here.
[Magisk] spicediablo:
I can't seem to find /data/adb/Magisk and /data/adb/magisk.db and i'm using magisk delta. Anybody knows where i can find the folders?

Update: Found them in /data/unencrypted
[Magisk] zgfg:
But don't you have links in /data/adb, so that you can execute also from the 'regular' path, like

/data/adb/magisk/busybox

From PC, prepend

adb shell
[Magisk] spicediablo:
I checked and there is magisk and magisk.db in /data/adb. I also found magiskbin folder in data/adb/unencrypted. All these has to be deleted when i need to clean install magisk?
[Magisk] zgfg:
If you have Magisk Delta then it installs binaries to /data/unencrypted/MAGISKBIN

and makes a link from /data/adb/magisk

So it appears to you that you do have/data/adb/magisk stuff but they are just linked to the other folder

But if you previously had Delta, did not uninstall it and just flashed regular Magisk, then you have now regular Magisk in /data/adb/magisk and you can delete the old Delta stuff from

/data/unencrypted/MAGISKBIN

You should know what is your current Magisk installation

Anyway, you can check do you really have Magisk binaries in /data/adb/magisk or only a link

Or you can execute

/data/unencrypted/MAGISKBIN/magisk -c

and

/data/adb/magisk/magisk -c

to see if they both declare Delta version, or first does regular Magisk and the second Delta
[Magisk] Mitezuss:
Hi, anyone can confirme me:

Can delete:

.backup\ (folder and all files inside)

overlay.d\sbin\magisk32.xz (just this file)

From a boot.img of arm64 ?

And magisk64 need .backup\.magisk ? to read value of "KEEPFORCEENCRYPT" or "KEEPVERITY" ? (if not, so can be deleted ?)

thanks
[Magisk] spicediablo:
Thanks for your detailed info. I am currently still on delta 26401 as attached. When I upgraded from delta 26301 to 26401,i did not managed to find those magisk file/folder and therefore, I skipped the step and proceeded to flash 26401 through magisk (same as installing magisk modules). Since I am still on delta, I assume it's safe to leave the magisk files/folders as it is.

By the way, can I please clarify what you mean by execute

/data/unencrypted/MAGISKBIN/magisk -c

and

/data/adb/magisk/magisk -c?

Are these adb commands? Much appreciated.

Update: I tried to execute as attached. Not sure if I did this correctly?
[Magisk] Mitezuss:
Maybe these files remain at the root of boot.img to restore stock / uninstall magisk ? So, can it be deleted if that does not matter?

Anyone can confirm ? thk
[Magisk] J.Michael:
Your screen grab cuts off the left margin, so I have no clue where you were when you typed the commands.

I think @zgfg meant to run them from the command line in a terminal window opened on the device.

I thought "adb shell" also opened a window that was running on the device, so that should have been good enough.

Try using the "ls" command to see the filenames, instead of guessing what's where:

ls -l
ls -l /data/unencrypted
ls -l /data/adb/magisk
[Magisk] spicediablo:
Sorry, I recapture as attached.
[Magisk] zgfg:
Sorry, executables are magisk32 and magisk64

So you did correctly from ADB (I meant Terminal Emulator hence I am omitting adb shelll) but it must be:

/data/adb/magisk/magisk32 -c

etc

It will give you the version of Magisk

See also my screenshot from TE

Try also with:

su -c ls -l /data/adb/magisk

It will show how the folder is linked in Magisk Delta

Also, check to where and which executable the magisk is linked to:

su -c which magisk
[Magisk] spicediablo:
I have the same output as yours. It means only unencrypted folder is being used and I can delete /data/adb/magisk?
[Magisk] zgfg:
No, don't delete, it is just linked to unencrypted

Some modules may call directly like/data/adb/magisk/busybox, if you delete the folder that would fail
[Magisk] spicediablo:
Thanks! So, my understanding is that, I need to delete /data/adb/magisk ,/data/adb/magisk.db and /data/unencrypted/MAGISKBIN for me to have clean uninstall?
[Magisk] zgfg:
You have a big, red, Uninstall Magisk button down in the Magisk app. Then accept full uninstall or so
[Magisk] spicediablo:
Sorry, i'm refering to this post. There is delete instruction after turning on aeroplane mode.
[Magisk] zgfg:
You can always put to Airplane but I don't think you would need
[Magisk] J.Michael:
I think between the time you click "uninstall Magisk" and the time you reboot, you still have root.

Click the "Uninstall" button, then look at /data/adb and /data/unencrypted: Is anything there?
[Magisk] Nekromantik:
if I am on magisk delta do I need to remove delta and then install official or can i just direct install official over delta?
[Magisk] nylium:
Magisk Manager crashes whenever I launch it after it ran an update.

How do I re-install magisk?

I can't open Magisk Manager to patch a rom.

Poco X4 Pro 5G, A13
[Magisk] J.Michael:
Do you think you have Magisk installed?

What ran an update, Magis, or Magisk manager?

If it was Magisk manager that updated, and that's where your trouble began, you should be able to uninstall the current Magisk manager app without opening it -- just use app info (long press the manager icon) and uninstall -- then re-install the manager you had before the update.
[Magisk] J.Michael:
I think the safer approach is to uninstall whatever you have before installing the different branch.

I think @pndwal recommended using the current manager app to install the new Magisk branch by renaming the magisk.apk to magisk.zip then using manager app as if installing a module.
[Magisk] klemi71:
Description on Page 2745
[Magisk] HippoMan:
Given that we're on page 2883 now and that the page selector shows "1 ... 2883", is there any way to get to page 2745 without having to click on the back arrow of the page selector 138 times?
[Magisk] badabing2003:
You can click on the 3 dots and type the page number or change it in the browser address bar
[Magisk] HippoMan:
Oh, I never realized that the three dots are clickable. Also, my handheld device is narrower than the space needed to show the full address-bar URL, and the right-hand side of it is truncated, so I didn't see the page number.

Thank you!
[Magisk] HippoMan:
When doing this, should the Magisk Manager first be un-hidden?
[Magisk] zgfg:
Click as on the screenshot
[Magisk] pndwal:
Maybe this (p2879)?:

For any wanting to downgrade, or change between Magisk forks from different Devs, or to CI builds from Magisk Actions etc:

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

Nb. @Nekromantik, the salient point begins with "To avoid unexpected issues..."

👀 PW
[Magisk] HippoMan:
Thank you.

Given that there are 20 messages to read on each page, IMO it's usually more helpful to paste the URL of the exact message being referenced than simply to post a page number.
[Magisk] rodken:
I think that the general consensus is that you should always un-hide before upgrading/updating.
[Magisk] rodken:
Even a clickable link of the page number when referencing a particular post.
[Magisk] J.Michael:
Is this "3-dots" only in the app?

I only use a browser. I do not see 3 dots to the right of the search icon (or anywhere else).
[Magisk] badabing2003:
This is from a browser
[Magisk] J.Michael:
Yes, thank you, I finally noticed that the ellipsis was clickable.
[Magisk] badabing2003:
Yep, definitely not an obvious one.
[Magisk] Giorgi-geo:
I unlocked the bootlaoder on LG V40 following this guide, then I flashed the magisk 26.4 patched boot_b.img and got root. It worked well, except battery was draining, but I don't know if it started immediately, or I installed something. So I tried to fix it, installed battery guru, gave it all the persmissions, tried to uninstall included 3 facebook apps, unsuccessfully, and rebooted the phone. It bootlooped, I tried factory reset, but after saying "erasing", it went into bootloop again. I restored original boot_b.img with qfil, and android, that was factory reset booted up.

So I tried to root it again, with the same .img I originally used - bootloop. Patched original boot image again and flashed that - bootloop, Took boot image off the phone and patched that - bootloop. Phone only boots with original boot_b.img. Does anyone have any clue why? It was working for a few days during which I restarted phone dozens of times.

TL;DR Root worked for a few days until I installed/uninstalled/disabled/enabled some system apps and rebooted. after reboot phone went into bootloop and now only boots with original unpatched boot image.
[Magisk] zgfg:
The real problem is that Neo has now completely broke the Search this thread:

https://xdaforums.com/t/all-xda-members-feedback-recommendations-for-xda.1987254/post-89185625
[Magisk] J.Michael:
What is "qfil"?

Try wiping and starting over, this time with older Magisk. And don't fiddle with system apps, or install any modules, or install any apps that need root privilege.
[Magisk] BillGoss:
I've found that it's sometimes best to boot the patched boot image fastboot boot <IMG file> instead of flashing it. Then, when the phone boots up on the patched image do a Direct Install in Magisk and reboot.
[Magisk] HippoMan:
Other people have also recommended this, and after trying it, I've found that it's worked well for me, and so it's my preferred method now, also.
[Magisk] badabing2003:
@BillGoss

I believe the live boot approach only works for devices that patch boot.img not init_boot.img

At least it used to be that way, I'm not sure if it is still the case.
[Magisk] BillGoss:
Ah, that's something I've read about but not had to deal with - my phone uses boot.img.
[Magisk] Giorgi-geo:
qfil is "Qualcomm Flash Image Loader" it's used to flash engineering bootloader to v40 abl partitions, then by deleting laf_a and laf_b partitions I can get into fastboot, do unlock and restore the original abl_a and abl_b.

What do you mean by wiping all? I did factory reset, and restored original partitions and tried countless times but no success.

Yeah I'll just stick to disabling what can't be normally uninstalled.

If I don't install any modules or apps that need root, than what's the point of rooting? I'm rooting because I need root access. Could any app or module cause such damage that would break rooting the phone again?

I tried this, but since loading fastboot on v40 requires flashing engineering bootloader that won't allow android to actually boot, it didn't work, I tried restoring bootloader from fastboot, and then trying to boot the boot.img but it resulted in error.
[Magisk] Paulkw:
Can anybody help. I installed official Magisk and a couple of modules (Shamiko, SafetyNetFix) to try and fix a banking app.

Now decided to remove Magisk and I uninstalled it through the app (complete uninstall).

During the process there was a message saying something like "can't find image backup" and "using internal image". Then the phone rebooted to recovery and is only booting to recovery.

How can I restore the system? Can I just flash original boot.img? My device is Xperia XA2, and LineageOS 20.

Thanks!
[Magisk] J.Michael:
When I said don't do any of the things you want to do (install modules, disable system apps), I meant until you are sure you got back to the working Magisk you said you had for a few days.

I know nothing about this dance you have to do with "engineering bootloader" that won't boot Android.

When you are able to boot Android, can you use "qfil" to flash partitions? Why bother with "fastboot"? Especially if it's so much work to make it available, and you can't boot Android while fastboot is available.

What is it to delete a partition?

Have you flashed a complete ROM, just to make sure you have restored all of the partitions you had to modify in earlier attempts?
[Magisk] J.Michael:
Flashing the original boot image is always a good thing to try. It's just very important to really be flashing the right boot image.

Failing that, try flashing a full ROM.