yashsingh1/xdaforums huggingface dataset:
[Magisk] evil-google:
Hi,

Yes, it is Redmi Note 7.

I did have it formatted as internal storage but decided to re-install the same LOS 18.1 version I had. Now I cannot format the SD card as internal storage and hence this post. I'd rather not use another app to do this as I can easily move data manually but if would be nice if I can work out why I can no longer format it as internal storage. Thanks.
[Magisk] zgfg:
If you install the root app Fox Magisk Module Manager (FMMM tool was suggested here several times since support for the on-line modules repo was removed by

Magisk v24), you can search for the fbind module (and simply install it directly from FMMM).

Screenshot attached

The module is actually published on the new Alt Repo:

GitHub - Magisk-Modules-Alt-Repo/fbind: A versatile Android mounting utility for folders, EXT4 images, LUKS/LUKS2 encrypted volumes, regular partitions and more.

A versatile Android mounting utility for folders, EXT4 images, LUKS/LUKS2 encrypted volumes, regular partitions and more. - GitHub - Magisk-Modules-Alt-Repo/fbind: A versatile Android mounting uti...

github.com

Disclaimer: I don't use the fbind module
[Magisk] pndwal:
Oh, I see you mean officially adopted...

I never had issues with Adopted Storage on LOS!... Guess you fully formatted card... PW
[Magisk] evil-google:
Thanks. Downloaded and installed fbind. I will first try the LOS forum to see whether anyone can suggest a straight forward solution - if that fails, I will look at using fbind which looks very promising. (y)
[Magisk] samhhmobil:
This is the "thread" for fbind:

https://xdaforums.com/t/fbind.3621814/

The "home" is:

GitHub - VR-25/fbind: A versatile Android mounting utility for folders, EXT4 images, LUKS/LUKS2 encrypted volumes, regular partitions and more.

A versatile Android mounting utility for folders, EXT4 images, LUKS/LUKS2 encrypted volumes, regular partitions and more. - VR-25/fbind

github.com

samhhmobil
[Magisk] Tech = Spy-Biz:
(Excuse, Off-Topic)

Hope you find luck with fbind, also since you asked for the decryption zip i think that is the file that ive attached (you might have to modify the updater-script in google folder to be able to flash it, for that you need to remove the first few lines in the updater-script that mentions which devices this zip is intended to be flashed upon) but please back up your device data first before you flash the modified version of this zip file or even if you flash directly without modifying the file.
[Magisk] evil-google:
Did have a quick look at fbind - haven't got my head around yet on the syntax and usage. Will need to spend a couple of days to work out the details. But it certainly appears to be the way to go.

Not sure whether I want to go down the path of playing around with decryption.zip - just that I do not feel comfortable doing it as my knowledge about Android is file structure is not that great and I might end up creating more work for myself! Thanks for sharing the file anyway. Still waiting to hear from LOS but the only available support is via IRC and given the time difference not had much success in getting someone to have a look at the issue. Looks like fbind is the way forward.

Thanks for all your support.
[Magisk] ipdev:
Quick OT comment.

To touch back on this.

crDroid is based on Lineage.

Think of cr as Lineage with heavy customization. 🙃

If it does not work with Lineage, it will probably not work with cr unless it is fixed in cr.

In turn, I would hope cr submits the fix to Lineage.

Cheers. :cowboy:
[Magisk] evil-google:
I did not know cdDroid background....we live and learn! Thanks for clarifying this.
[Magisk] evil-google:
Finally managed to get hold of devs at LOS and their response was simply not to use adopted storage. That leaves me with the option of looking at fbind or manually move files to sdcard.

Thanks everyone for your comments - greatly appreciated.
[Magisk] jeanxx:
Is there a YouTube video or straight guide on how to get magical installed correctly and working with Android pay?

I installed VenomRom on HTC 10 in systemless mode and flashed magisk v8, installed magisk manager and phh superuser from play store. Removed old superuser app.

Keeps saying su binary out of date and won't update and Android pay not working.

Not sure how this is supposed to be installed.
[Magisk] andrew2432:
Flashed phh superuser 259 zip after flashing magisk?

[MENTION=1341578]churchy[/MENTION]360

There are two parts to magisk and two parts to phhsu. The zip files; to be flashed in custom recovery, and the apk files: GUIs for the zips.

Recovery:

Flash magisk

Flash phhsu259

Boot to system:

Install phhsu application

Install magisk manager

Rooted. The rest is trial and error if you're after xposed and whatnot. Won't work on all devices. System less is the way to go. Cf has system less as well!! It's only a matter of time before other apps start messing with root too.
[Magisk] zapahacks:
Ok man, lets start from the beginig

I know it works because other users reported it working for them. On galaxy s7, I can remember a user with Superman ROM V1.15 and kernel 3.18.43-SuperStock_SM-G930F_V1.4.5 that had it working. Search if this rom works on your edge model, it should, just the kernel might be different (so search for the same kernel but for your edge variant).

You don´t need Xposed. And magisk is not intended to hide Xposed. The procces of hiding Xposed is made by the Root Switch app. And you don´t need suhide or chainfire SuperSu app, so forget about those files for now, that is different method. This method is for magisk v8 + phh's superuser, which I think is the method that works well with Samsung devices like yours and like mine. Don't mix both procedures as you will have problems with safetynet. Just go with the one in this method, if it doesn't work, then try with supersu + suhide (I don´t know if they have updated it to work with samsung)

Safetynet checks for many things, but I don´t think all of them are important to know about, what you need to know (for your S7 Edge) is:

a- It detects Magisk (so that is why Hide Magisk option is available on the app and it is needed to pass safetynet)

b- It detects Xposed Framework (so that is why Root Switch has an option to disable/hide Xposed)

c- It detects root made with SuperSU (so it is very important that you unroot first if you are using a custom rom)

d- It detects some modifications made by custom rom builders, I believe they are related to their custom kernels (so that is why sometimes even if you correctly unroot your custom rom safetynet will be Red). So if this is your roms case, you will need a custom kernel (like Arters kernel in my case, or like 3.18.43-SuperStock_SM-G930F_V1.4.5 for Galaxy S7)

My suggestion is to just forget about Xposed first (this is the tricky part as I said), leave the Xposed steps for later, they are not mandatory to have root working. Just focus on having root working in your device. When you have it working do a backup and ONLY then try the Xposed part.

With respect to the Rom I use, I believe it is the kernel included the one that makes trouble. The other modifications doesn't matter. Just the kernel. So don't worry if you want to modify battery or other stuff. Just first make sure you find a rom+kernel that pass safetynet and then do your modifications. I believe it shouldn't change your safetynet response unless you modify the kernel itself.

Hope it helps. :good:
[Magisk] jeanxx:
I followed a previous guide of fully unrooting through SU app then reboot into recovery, Flash phh su zip, then magisk zip, then reboot. Then installed phh su app and magisk manager. However, now says no root available and phh su binary out of date and not updating.

What did I do wrong?
[Magisk] Captain_Throwback:
Wrong order.

Magisk zip, then phh Superuser Magisk module zip.
[Magisk] andrew2432:
I've always seen magisk first, no idea what happens if you do it the other way around. I think phh plays with a new su folder it creates or magisk creates and I believe it needs magisk in order to install correctly. Not 100 percent on that
[Magisk] jeanxx:
Sorry, I put my message in the wrong order. I uprooted, then flashed magisk, then phh module then installed phh and magical manager but root still not installed
[Magisk] jeanxx:
If I clean install Venomrom, how should I go about it:

I did this order:

Full Wipe clean installed VenomRom in systemless compatibility mode

Booted up

Then unrooted in SU app.

Rebooted in recovery and flashed Magisk then PHH module

Rebooted and installed PHH and Magisk apk

Now root has failed and SU binary out of date and no way to update it.
[Magisk] voltaek:
Has anyone got the Uninstaller ZIP to work properly to uninstall Magisk v8?
[Magisk] yochananmarqos:
Yes. You can check if it uninstalled properly by verifying that /magisk & /data/magisk have been removed.
[Magisk] rgshah3:
If i have a system root (not systemless) how do i install magisk?

I need to completely unroot my phone and flash magisk? (Native system less supersu doesn't install on the moto x play)
[Magisk] DodoGTA:
[MENTION=4470081]topjohnwu[/MENTION], can you make Magisk Manager APK compatible with KitKat (API 19) because I've booted CM 11 successfully with Magisk installed?
[Magisk] teddy0209:
Unroot and try magisk, then report...????
[Magisk] makinista69:
Hi, i have CM12.1 with Magisk v8 (updated from Magisk 6) and when I reboot, I get root and everything looks fine.

But after a couple of hours, Magisk says "no root access" and no apps can access root.

I have Magisk Hide activated, and phh's superuser (everytime I reboot it says "The su binary is outdated")

What can I do?

PS: I had Magisk v6 and everything worked fine. Then I updated to Magisk v8 and this happens.

(Device: bq Aquaris e5, a spanish brand that uses stock android roms)
[Magisk] mobileman88:
Anyone tried installing the "Google Assistant" module in Magisk Manager 2.1? I tried installing it in 7.1.1 for my 6p. After reboot it's not activated and does not allow me to remove/delete it. It keeps having the following status. "Please reboot to update changes" even after rebooting 5 times.
[Magisk] Captain_Throwback:
This isn't possible. The app requires at least Lollipop to function.
[Magisk] cridtohs:
Im not passing checkpoint 1 with just magisk and phh magisk root . Tried Hydra Rom, Superman, Decent Rom, King Rom, tekrom, stock rom. Also magisk Hide sometimes blocks root or sometimes not, but is still detected by most apps looking for modified android. With no root installed I get green safteycheck passed. Also there is no value in getprop for bootverify on these phones so xsetprop is not a problem. If theres anyone with an s7edge who got this working or is able to hide root from applications using THIS method (magisk) please let me know. I AM able to hide root using supersu and suhide method, but NO method allows safteycheck bypass.

[MENTION=4577747]zapahacks[/MENTION] , the problem is xposed 86.2 will NOT install WITHOUT supersu, thats why I think there is something fishy in the way you have it working. Try to reformat and follow your steps I almost 100% guarentee they are not reproducible.
[Magisk] Biz92k:
Got the same issue with my moto g on idcrisis... When I reboot everything is fine, after a while the root is not recognized by any app, even if all the xposed modules keeps on working.

I'm on lagest SuperSU, with phh su it happened but less frequently... What could be that causes the problem?
[Magisk] Little Nugget:
Thank you so much! I followed this guide VERY VERY carefully and I finally have safety net passing green with both apps (sample/helper) and it stays green with my phone rooted, magisk installed, and xposed as well! Nothing else helped me to get it working after days of endless searching and reading but this helped me!

T-Mobile Samsung Galaxy S6 Edge+ (SM-G928T)

Magisk v8 mod2

phh's superuser r259

Magisk Manager 2.1

Xposed 86.2

RootSwitch 1.3.3.2
[Magisk] xander33:
the cause is magiskhide when it's enable you loose the root after a while and you need to reboot your phone

actually no solution yet.... but if you don't need to hide your root simply uncheck magiskhide and your root became stable
[Magisk] 73sydney:
Custom ROM's generally have just 2 sources, AOSP (Google open source) which is usually close to Pixel appearance or LineageOS.

Just to make things murkier for you there may be 3 or 4 custom ROMs using LineageOS as a base, but often devs will "cherrypick" commits etc from other repos (other than LineageOS) to fix issues, so issues may exist on one ROM, but not another. Usually (though not always) once a dev finds fix for an issue they will share which commits theyve used to benefit the other ROM's.

I dont miss the days, while on my s20+, of testing 3/4 ROMs a week like i used to on previous devices....

<insert Murtaugh quote>

p.s. If you dont get the Murtaugh quote then youre probably too young, and youre part of what daddy calls "The Problem" :)
[Magisk] 73sydney:
Thats not entirely surprising given the downsides of adoptable storage, namely corruption (any issue on the memory can cause the entire ROM to have a spazz), disappearing shortcuts to apps, and that other great one, running out of space (because what do you think happens when you run out of space with adoptable storage? - nothing good is the simple answer)...though thats not as big of a deal as it once was...some of us remember it though....
[Magisk] rodken:
Off-Topic: I always thought that 'The Problem' colloquially known as Zoomers were the 'ones' that prefer to use abbreviations and/or acronyms for every other word typed or spoken.
[Magisk] 73sydney:
like i totes dont like even get you right now....Bruh
[Magisk] Makishima:
Anyone knows if Magisk works on A13? My Pixel 4a seems to have got it this month. Tried to do a search in this thread, but the search function seems completely broken (unless I'm doing something wrong...)
[Magisk] m0han:
https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87293477
[Magisk] Lughnasadh:
Yes it does.
[Magisk] exist2resist:
I have been running lineage OS on my Pixel 3 XL (crosshatch) for about 3 years now side by side with Magisk.

I recently upgraded to Lineage OS 19.1 and some issues started popping up in the OS.

Primarily when I boot, I see a toast message about network not being available.

Also my Amazon app stopped working, it keeps complaining about not being able to find a network.

So I decided to remove magisk/root, as soon as I did that the toast message stopped popping up on boot and the Amazon app started working.

I'd like to keep using magisk so I can backup my apps and run adblocker, anyone seen this before or know a fix for this?
[Magisk] J.Michael:
How did you upgrade Lineage?

Did you re-install Magisk after upgrading Lineage? How?

How did you remove Magisk?

If you flashed a Magisk-patched boot image after upgrading the LineageOS, did you extract the boot image from the new Lineage and re-patch?
[Magisk] pndwal:
... Further to the above did you remove root by manual boot.img flash, or Unstall Magisk from App?... PW
[Magisk] evil-google:
I read the instructions but got swayed by another post elsewhere where it was stated that instaling the apk first and renaming it as zip and then sideloading has worked for someone quite well. So out of laziness I did the same process and found that it all installed without any errors.

Could this be the contributing factor with my adopted storage issues which I did not experience earlier? Also, I am experiencing some wierd problems with bluetooth where I can connect using bluetooth to most devices but if I try to connect to another android device it attempts to pair and then fails without any errors. Fortunately, haven't experienced any other major issues.

What is the correct un-installation procedure for Magisk? I would like to uninstall and re-install as per the official method to see whether my issues will go away.
[Magisk] pndwal:
Bit vague on your setup now...

Guess RN7 with ramdisk=no (since launched w/ A9... unless has A/B(?))

So default instructions are install magisk in recovery ramdisk (recovery mode selected)... Zip install can't do this... Did you ever do that (patch recovery.img)?... But being Xiaomi you won't actually need this... Best to patch boot.img (recovery mode un-selected) using M. App and flash...

And I wouldn't use .zip install for your device... It's legacy SAR... May be fine, but zip install is fraught since legacy ramdisk booting devices (any device w/ Launch Version A8 or less, but not updated to A10+)... Whether this could impact on SD card, BT issues etc, I'm not sure, but I'd start again w/ proper patch / flash for SAR / 2SI devices...

You can use Uninstall Magisk from App; Nb. Restore Images leaves android configuration in /data/adb, so you'll want to take Complete Uninstall... (Or, if you first want to test if issue is that magisk.db or other config files are corrupted / causing issues, with root explorer or twrp simply delete everything in /data/adb and reboot and magisk daemon will rebuild config files... You'll have cleanly installed root and modules, superuser, deny lists etc will be gone too...)

For full uninstall you can also delete everything in /data/adb and flash unpatched boot image (recovery.img or boot.img or both these boot images)... If deleting data with root, don't reboot before flashing original boot image...

Issue does sound VERY like a mismatched kernel to me... Often this gives associated hardware issues...

Kernel is in boot image, so this is a common issue where users restore images to take an OTA update (even a minor one), then flash back previous boot image instead of sourcing the ROM corresponding with the OTA to obtain boot.img (or recovery.img) to patch and flash... or simply mix up boot images on the PC... Failing to restore unpatched images before an OTA can cause issues too...

Did you ever use App to patch images? (... Old .zip installation doesn't allow such a mismatch/ user error).

... Remember to treat your Xiaomi SAR A only device as

ramdisk=yes

for your clean setup, and patch / flash boot.img exactly matching or extracted from current ROM...

🤠 PW
[Magisk] exist2resist:
I upgraded Lineage using the Lineage Recovery, as per Lineage instructions, then I flashed the Magisk.zip as my phone supports boot ramdisk.

I removed Magisk using the APP inside the OS.

No, I did not extract it from the lineage zip.

I am unable to mount the payload.bin in windows, and it errors out on me when I try and use 7zip to open it up.
[Magisk] zgfg:
To extract img files from payload.bin you have to use Payload Dumper. There are several threads (under different devices) with download links on XDA (you should search for) - for Windows, Linux, even for Android (not working great with bin files of several GBs), and with instructions

Link to my copy (for Windows) I downloaded months ago from XDA and happily used couple of times:

6.44 MB file on MEGA

mega.nz
[Magisk] J.Michael:
From what @pndwal just said to someone else, if Lineage recovery can flash a zip like TWRP can flash a zip, then there is no danger that you are using the wrong boot image (which includes using the wrong kernel). That was the point of my questions about extracting the boot image. They just don't apply for the procedure you used.

If you want to try a different way of installing Magisk, you will have to solve your problem of how to handle payload.bin. You can probably get guidance in a Lineage thread. Or search the forum for words like "payload dumper". I know I've seen a set of files / scripts. I do not remember if ZIP is any part of the process.
[Magisk] exist2resist:
That seems to have done the trick. Thanks
[Magisk] exist2resist:
Thanks for that worked really well, and solved my issue.
[Magisk] J.Michael:
WHAT seems to have done the trick?
[Magisk] exist2resist:
Using the payload.bin extractor that zgfg recommended, patching the boot.img, and flashing it via recovery. Didn't know the lineageos had an extractor for this.
[Magisk] pndwal:
Android OTA payload dumper by LOS? Really? PW
[Magisk] evil-google:
Hope you will have patience with my ignorance on this matter :oops:...so, will the following help?

1. open Magisk app and select recovery mode and do a direct install

2. then again using Magisk app uncheck the recovery mode and do a direct install

Or will it be just better to uninstall magisk completely, re-install the apk and use boot image patching method? Again, when creating the boot image patch file do I need to select the recovery mode option?

Once again, thanks for your patience. As you can see, I am clueless on how Magisk does its tricks!

EDIT : You are correct, in my case ramdisk=no.
[Magisk] pndwal:
First, I asked : Did you ever use App to patch images? (Answer will eliminate some possible issue causes...)

No... Treat you device as ramdisk = yes...

- Magisk manually added a basic ramdisk to boot partition (it always does when missing, yous in case it can be used for Magisk init... Still says no to indicate no

OEM

ramdisk as most A-only legacy SAR booting type devices won't be able to use the ramdisk due to incompatible bootloader... Xiaomi inexplicably has boot-ramdisk compatible bootloader despite OEM not utilising it...

So,

don't

use recovery mode (for patching recovery image)...

Well you can, but won't be clean... Thought you wanted to eliminate any issues with configuration which is in /data/adb...

Uninstall Magisk, so do as you said (select Complete Uninstall) or simply patch correct image, delete /data/adb but leave app if correct version and flash newly patched image before any reboot... (Am I repeating all this?)

No! ... Only if you want to use the troublesome Magisk in Recovery ramdisk option, but why do this when bootloader allows Magisk in boot??

No worries, but do take time to read official Installation instruction(s) 3 or 4 times till you get your head around pertinent instructions... Many clues I've given are just from these...

👍

PS Google is your friend! (Not Evil)... And FWIW, Android is their (adopted) baby, their mobile OS!... What's not to like?! 😛 PW
[Magisk] J.Michael:
@evil-google If you use the Magisk manager app to patch an image, and there is a checkbox for "Recovery mode", it is your responsibility to use that checkbox to tell Magisk what kind of file it is patching. Only check that box if you are giving Magisk a recovery image to patch. And make sure that you flash a recovery image to the recovery partition.
[Magisk] evil-google:
No, I did not. As I mentioned, I took the quick and dirty option since someone posted that it worked of them without any issues and now I know that it was the wrong choice!

Thanks again for going through the responses in detail and it makes a lot more sense to me. I will uninstall it and then patch the LOS boot.img file and flash it as you have mentioned rather than trying to fix what may be broken.

Appreciate your help.(y)
[Magisk] evil-google:
Is there any advantage of patching the recovery image over patching the boot image?
[Magisk] pndwal:
To be clear, issues may not stem from .zip installer recovery installation, but it is not recommended even by John for post ramdisk boot type devices... Modern installation can patch other partitions where needed also (zip installer doesn't), and also eliminates issues stemming from 3rd party Recoveries of which there are many that magisk cannot control (flashing, mounting, etc etc).

👍 PW
[Magisk] J.Michael:
I think not.

If anything, patching the recovery image is a last resort, used only when patching the boot image cannot work.

(All right, if Magisk is installed in recovery, it might be possible to boot in a way that leaves Magisk inactive. It is possible that some "tamper detection" processes will be satisfied if Magisk is not active. So, you could make the case that there is some advantage to installing Magisk to recovery.)