yashsingh1/xdaforums huggingface dataset:
[Android General] Techguy777:
No what I meant is that rw folder is already on custom ROMs and it won't allow write access in apps which doesn't make sense because RW stands for read write so I would have thought that the rim should have already been able to write to anyway but it doesn't until you flash your module

---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------

I think your right xda is messing up because the v4.2 won't download either now
[Android General] Ziona:
Yea by default they don't provide the necessary permissions to write to external Sdcard. But i make modifications systemless to the device on startup to allow access
[MENTION=9180355]Techguy777[/MENTION]

Vol test on first page !!
[Android General] Techguy777:
Sorry I've been busy and forgot Ill let you know they did download this time checked the zips contents and everything.

---------- Post added at 10:52 PM ---------- Previous post was at 10:17 PM ----------

Ok I tried both zips in magisk manager on my moto g4 32bit ROM Android 9 and it wouldn't respond to anything had to close it down and I tried twrp recovery it uninstalls. On my S7 edge running Android 10 64 bit with both zip 1 and 2 it doesn't respond to hitting volume up but if you hit back on the navigation bar after trying to hit volume up it then locks in keys programmed so than install module 1 I hit + and nothing but if you hit plus and back on the navigation bar again it installs test 1 2 3 4 5 if you keep doing it. So I don't understand that but it kinda works. After rebooting magisk manager just shows volume key test v1 beta.
[Android General] Ziona:
Its not going to install anything only blank module just for key test. Seems it only works for volume control below Pie.

Ok do this for me please.

type command in both devices: getevent -lp > /data/media/0/key.log

Look for this log file in internal storage an post back here.
[Android General] Techguy777:
https://drive.google.com/file/d/1bu2ETletJ5wLePLX5resXGyDg8m-ER9l/view?usp=sharing

https://drive.google.com/file/d/14aM1MKY31lVKYgVvYASgDBHF-QaaC-P-/view?usp=sharing
[Android General] Ziona:
Thanks get back to you
[Android General] Ziona:
[MENTION=9180355]Techguy777[/MENTION]

Just do quick test on this, hold volume up or down an release once it selects each option.

https://drive.google.com/file/d/1kH0kJaTodYPiST-wsSX5MQMcyK9IjyIe/view?usp=sharing
[Android General] Techguy777:
ok ill let you know
[Android General] Techguy777:
They install if you hold up the volume up I got the keylog

https://drive.google.com/file/d/15dEcsFTHRlbx6hTKQYfdIW-iVmdZkwSF/view?usp=sharing
[Android General] Ziona:
Ok good, but did you try any other yes an no combination. An remember to release the volume key after it has chosen the option like you would normally do when selecting each of the choices.
[Android General] Techguy777:
No I just held it until it installed than released and hit the button again holding it for the next one. Well Ill get back with you on trying different combos. Heres the moto g4 same thing though I held it once it installed I would release and than install the next one with volume up holding it. I didnt see this comment until now so ill try it differently. Would it be better to get keys after a reboot or is it fine just install and get them? Ive been just flashing and getting them?

https://drive.google.com/file/d/1juMmkbQpltz36fbFUIO_EkZWNK-7fkCo/view?usp=sharing
[Android General] Ziona:
Yea that's cool , but you have to also test it how you would normally do a install with options, wont be practical to always select yes to all if theirs options there to choose from. The key.log was only to compare device key event types for the most there kinda the same in nature , to get anything more deeper i would have to show you how to get output log as you test the keys exactly rite then not later. Thx
[Android General] Techguy777:
Sorry its been a couple days I got busy but I didnt forget. So here are different devices different combos logs. 731 Is july 31 on the file.

https://drive.google.com/file/d/1oBgoTDgoCeTvmokqP1R5DZlHEspwta_A/view?usp=sharing

https://drive.google.com/file/d/10Gevc4IvN1kx2EKy4wkQgy-1S8ZzCEkW/view?usp=sharing

https://drive.google.com/file/d/1-7eGhsl9pJDJ8roHyqWumTQOnZQX1_Qq/view?usp=sharing
[Android General] Ziona:
Ok thanks it mostly mattered that they work however you choose the options on your different devices .

Working on a update v4.3
[Android General] pieboots:
Do you have a telegram? Need to ask a few questions.
[Android General] Ziona:
First page rite above the downloads for my telegram !!
[Android General] Ziona:
[MENTION=9180355]Techguy777[/MENTION]

Hit me back when you have time mate
[Android General] Techguy777:
Hello im here
[Android General] Ziona:
I have two things I want you to test I'll upload but meantime also try update v4.3 posted .
[Android General] droidbot1337:
[MENTION=9906981]Ziona[/MENTION]

I........... ****'N.............. LOVE YOU!!!!!!!!!! YOU'RE AMAZING!!!!!!! thanks to you i have made my mi pad 4 into the media tablet that i have been wanting. till today i have been carrying around my tab s5e or tab6 to work and school but i can now leave them and take my smaller 8 inch tablet. vlc failed to view my external drives until this amazing module. thanks for this!
[Android General] Ziona:
Great no prob, when you can please send me the install log. It's in your downloads folder called ExternalSDCard-debug.log .

Am logging device types an methods used that your device supports.

New version drops in days greater support for Android 6 - 10 . New permissions an redone for better compatibility across Android platforms.?
[Android General] veekay:
Is 4.3 the release you mentioned, or will it be another? Still have hope to get this working one of these days.
[Android General] Ziona:
4.4 dropping soon

What do you need working gsi
[Android General] veekay:
You had me try a few things a couple of months back, never could get a success with getting exfat working on Lineage 10 GSI for a Samsung Tab S4.
[Android General] Ziona:
I do have some universal mount.exfat binaries. But if they work it wont add the sm volume , so most apps (unless they can set path manually) will not see the mounted volume but you can use a file manager to add an take things from sdcard like normal.

Seems from Pie up for most devices they removed mount.exfat binaries from bin. So they're using kernel support or no support.

Which is a bummer but some models still support it in factory but hard to find in custom OS.

I have garthered custom binaries for exfat an ntfs from all versions Android 6.0 - 10.0 but exfat support stops at Pie 32bit . Still hoping to get A10 mount.exfat support . If your sdcard is large an you need exfat support, you could always backup it on pc an format an use ntfs.

With custom support binaries it works like normal on Android . Something to think about.
[Android General] veekay:
Didn't think Android could read NTFS. I'm still puzzled by the situation since the base from that phhusson made works perfectly with exfat, but all of the lineage based roms (which use his base) do not. His rom has an issue that might be solved by making a custom overlay, but that is a little outside of what I could probably do.
[Android General] Ziona:
Yes CM, lineage, RR an mokee all have versions with ntfs support. Even some aosp

Wonder do they all use the same type kernel support he does in his OS or not. This would be the main reason other than lacking binaries
[Android General] veekay:
No telling, has something to do with AndyYan not being able to get exfat working on his build, which they then pull from.

Do you know if TWRP can read/write to ntfs? That would be the main thing. TWRP works fine. Funny enough, NTFS only works when using your mod. When I remove it the drive shows as 0B.
[Android General] JidoFisterFilly:
Thanks Ziona it works with Los 17.1 and Magisk 20.2 on Samsung Galaxy s5. :good:

Using XInternalSD to change path to internal sd card.
[Android General] Ziona:
Yeah i use universal type binary support also for ntfs an exfat. When you use an sdcard with exfat file system, do this. Type this in Mixplorer app that has execute support. No quotes " blkid > /sdcard/blkid.log " An post it here. Run that command from root only if any error add busybox before blkid.
[Android General] Ziona:
Great ;)
[Android General] veekay:
/dev/tmp-phh: LABEL="/" UUID="5b97be36-0fac-445c-8f5f-f0e1e352283d" TYPE="ext4"
/dev/block/mmcblk0p1: UUID="D887-2FA0" TYPE="exfat"
/dev/block/vold/public:179,1: UUID="D887-2FA0" TYPE="exfat"
/dev/block/sda27: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/sdd7: LABEL="dsp" UUID="af32c008-2a39-7e5b-a5dc-201456d93103" TYPE="ext4"
/dev/block/sda25: LABEL="omr" UUID="1b861656-3043-5e7c-bda0-83cf6b9ded4c" TYPE="ext4"
/dev/block/sda24: LABEL="hidden" UUID="e59fb056-93af-5f65-8dee-aab2508d9a14" TYPE="ext4"
/dev/block/sda16: UUID="00BC-614E" TYPE="vfat"
/dev/block/sda23: UUID="bb5bb861-b79f-4b9b-afae-c7f4d539094f" TYPE="ext4"
/dev/block/sda15: UUID="00BC-614E" TYPE="vfat"
/dev/block/sda14: UUID="91a42e49-8476-4b1c-be52-6847950ebebc" TYPE="ext4"
/dev/block/sda6: UUID="3e04a822-0bc4-4cef-bc44-0160c3965cca" TYPE="ext4"
/dev/block/sda5: LABEL="persist" UUID="d7a85ad7-dab7-5919-9005-2e498c6b9388" TYPE="ext4"
/dev/block/sda22: LABEL="odm" UUID="611f6132-8328-58af-a0a2-a509323b3f97" TYPE="ext4"
/dev/block/sda21: LABEL="vendor" UUID="1a586026-f608-558c-abfd-72bd8e23948e" TYPE="ext4"
/dev/block/sda20: LABEL="/" UUID="5b97be36-0fac-445c-8f5f-f0e1e352283d" TYPE="ext4"

Exfat drive shows in Mix, but when you click it there is nothing there (Says Not Exists!). NTFS is working fine though, so it seems that would be a good enough solution.
[Android General] Ziona:
Yeah with ntfs size is no limit, the sdcard your using does it have both exfat an vfat on different partitions ?
[Android General] veekay:
Only exfat partition, freshly formatted a card just for testing.
[Android General] Ziona:
What about any usbotg connection , am asking cause i see vfat in one of the 8 digits serial numbers that sdcard an usbotg uses. It could be internal storage also but that mostly emulated an doesn't show there normally.

mkdir /external
/system/xbin/mount.exfat /dev/block/mmcblk0p1 /external
[Android General] veekay:
Nothing outside of the device itself and the sdcard.
[Android General] Ziona:
Run the code given see what happens, check external folder in root afterwards
[Android General] veekay:
Ah, missed the code section. So that works and gives me read/write access, but only when using that folder from root. The actual external sdcard shortcut in mix still doesn't work correctly.
[Android General] Ziona:
Its not auto mounted by vold an sm.volume so any apps relaying on direct path of sdcard serial number in /storage or /mnt/media_rw wont see it there. But you could point apps to that path if they have that built-in feature. You could add that code to one of these files -

/system/bin/early.sh or /system/bin/sdcard.sh thats from my module an every startup it will execute it .

Its a good start for you can see the possibility of maybe full exfat support
[Android General] Ziona:
[MENTION=9180355]Techguy777[/MENTION] ready to test v4.4
[Android General] Techguy777:
Ready
[Android General] Ziona:
Download section v4.4 is posted
[Android General] Techguy777:
yes it works great on android 10. Im going to download an android 11 rom for my phone is it setup to work on android 11? Also the buttons volume up and down work perfectly to select options in magisk manager.
[Android General] Ziona:
Ok great, yea it's tailored to support Android 11 an am using my own custom volume addon to go with my modified magisk module. Does your devices have ntfs support ?
[Android General] Techguy777:
Well I dont think android 11 is going to work. The rom doesnt even read my sdcard at all. So its still pretty early. Ill have to check on ntfs support not sure.
[Android General] Ziona:
Ok yeah you can possibly get ntfs support for USB an sdcard with this module. As for A11 if you're still interested in it execute this command if you have BusyBox an let me know the output with a sdcard in the device

busybox blkid
[Android General] kubalav:
It's work for me too on LOS 17.1.
[Android General] droidbot1337:
i had this installed on my mi pad 4 while on Q. i recently updated to android R and cant get this to work. i mainly use my pad 4 as a media tablet because its compact but after upgrading i cant get vlc to load anything from my storage devices. any help is appreciated. btw @Ziona, thanks for the mod!
[Android General] Ziona:
You can try this an see if media is located. Let me know if a new ExternalSD1 folder (your actual sdcard) is found in your internal storage area where your music and download etc folders are located
[Android General] hltdev:
So if I am reading correctly, the directories created by this module would permit exec permissions? (I think that's what "full permissive mode (optional)" means... )

For instance I am on a pixel 4a. Would this module allow me to run scripts from the directories/lns this module creates? (I know that the pixel 4a has no sdcard, but I believe that the internal storage is mounted as an emulated sd anyways (/storage/emulated/0))

Hope I got all my knowledge straight in this post... lol 😂 My basic question is just simple:

does this module provide full exec permissions to the sdcard?

Thanks for this module regardless!

Ill probably just try it and see what happens anyways heh...
[Android General] Ziona:
It should but some devices may vary so you would have to install an test. Theirs a 5.0 version last page to try as well
[Android General] Weedy0104:
Hey,

Version 5.0 and i think all before that too arent working with newest magisk version. The installer Script i guess searches for magisk Manager App, but in New magisk Versions apk is renamed to magisk. So the Script cancels install with am error. If I am Installing old magisk Manager then it is working. Can you edit the Script for supporting newest magisk Versions? Thanks
[Android General] Ziona:
Which version of magisk.
[Android General] Weedy0104:
Look at Screenshots i guess it is since all Versions above last stable.
[Android General] briank6932:
@Ziona Hey, so I know I'm an idiot and didn't backup my device beforehand, but I attempted to install 5.0, and once I rebooted I was hit with, "Cannot load Android System. Your data may be corrupt.", and no matter how many boot cycles I attempt, I can't boot. I tried to re-flash some imgs, reinstall the OTA, etc, but I can't figure out how to fix it. I really don't wanna reset to factory, so any help would be appreciated.

Just as a reference point, I did attempt to install 4.4, and it didn't work successfully, the best success I had was with your fs-binaries-updated.zip weirdly enough. It would give me exFAT support in the files app only, but wouldn't work with solid explorer for whatever reason, and I could only access the storage devices on the notification prompt, I couldn't re-acceAttach filesss them afterwards.

Phone: Essential PH-1

Bootloader: Unlocked

ROM Version (Stock ROM): QQ1A.200105.032 (February 2020)

Kernel: ElementalX 4.12

Root: Magisk 22.0

Recovery: Stock (TWRP doesn't really install well on this ROM version)
[Android General] JidoFisterFilly:
I get it to work with v5.0 on Android 11 (LineageOs 18.1) with Magisk 22.1 on my Samsung Galaxy S5.

@Ziona thank you for your awesome work!!
[Android General] Ziona:
Sorry was very busy, did you get this sorted out?

What options did you choose when you installed v5.0?

Normally if any problems come from a magisk module on boot you need twrp install to disable it.

What android version are you on?
[Android General] bl4ckOut93:
Works flawlessly for my use case:

Full NAND Backup via OrangeFox Recovery over USB OTG on a WD 1TB Slim external drive with NTFS.

My device:

Xiaomi Redmi Note 5 Pro (whyred) with Android 11 Havoc OS v.4.5 CFW.

Thanks for creating this module.
[Android General] briank6932:
@Ziona Yea I would use TWRP if I could, the patch I'm on doesn't really have very good support, I'm on android 10(Q). I think I'm going to try to modify a magisk boot.img to core-only mode, it's possible, but seems really annoying
[Android General] briank6932:
Ok, I managed to get TWRP working (required flashing an older abl.img), however, I still can't figure out how to circumvent the bootloop and get to my ROM, @Ziona are there any residual files left over that could trip a bootloop or something? I have magisk running core-only, and can't boot on stock boot.img either.
[Android General] Ziona:
Del.
[Android General] Heavy-MatIll:
Hi there,

Love the idea of using this to read exfat SD cards from via USB-c card reader.

However Installation fails.

Device: Redmi Note 7

Rom: MIUI 12.0.1

Android: 10 QKQ1

Tried it with 4.6 and 5.0, see attached logs. Any idea why it fails?
[Android General] Heavy-MatIll:
Double post
[Android General] Ziona:
Is your magisk up-to-date have you tried using an older version of magisk manager to check if it installs.
[Android General] Ziona:
Try not choosing ((boot.img patch)) & ((custom vold)) during install it's not necessary to pick yes to all options at once.
[Android General] Heavy-MatIll:
Tried it with an old version (think 20.? Where Manager was still called manager.apk) first, later updated to 23. No difference in the result.

However disabling (boot.img patch) option did the trick with installing ( Log).

After reboot I noticed /mnt/sdcard1 now being accessible (which it was not, before this patch).

However it points to my extsd path which was always available at /mnt/media_rw/xxxx-xxxx and storage/xxxx-xxxx.

After plugging in exfat usb drive, it is automatically mounted by android system, tried it with 2 thumb drives and a card reader.

It did not work with ntfs usb drive. Android system recognizes, that usb has been attached but says there was an error with the storage and it needs formatting. It does work with Microsoft Paragon app and Total commander usb-plug in. However those tools do not give a regular link in mnt/media_rw or /storage/ (which is what i am looking for).

Anything i can do to fix that?
[Android General] briank6932:
@Ziona

It's been a while since I installed, so I don't fully remember, but I believe it was custom vold, is there an installation log file? I tried to flash the ROM imgs via TWRP and through fastboot, even OTAs under stock recovery don't work, I still ended up with the same problem, "Cannot load Android System. Your data may be corrupt." I also tried to mount system via TWRP, and that wasn't working for whatever reason, is it possible that is related?
[Android General] Ziona:
Have you tried using version 5.0 I uploaded for testing pages back?
[Android General] Ziona:
Magisk module Install log should been saved in internal storage (root) or in download folder depending upon version. If data is corrupted somehow an you cant mount it or system partition with twrp. You may need to format an then clean install the rom again. Hopefully you backup before modifying anything
[Android General] Heavy-MatIll:
5.0 is the one that I am using. I was able to make it work with exfat by formatting sdcard on windows pc. previously I let the camera do the job. This way exfat works flawlessly with both USB drive and sdcard in otg reader.

Ntfs is not such a big deal, I figured out a way to set all my systems to exfat.

Thanks for your help!
[Android General] Heavy-MatIll:
I only noticed now that calls do not work anymore.

I get an error about no accounts for calls being available. Calling was possible again after disabling the module. I tried with both 5.0 and 4.4, same results. The symptoms are similar to a problem acc magisk module had: Acc github issue

Does this have anything to do with the install options? I attached the install log when I tried it with 4.4
[Android General] Ziona:
First ive heard of this issue will have to maybe looking into it. Install log seems basically fine , could you try installing it using just one option.

first option :

SD-Link

If issues then try just option :

ntfs & exfat binaries

fully uninstall module before each check.
[Android General] Heavy-MatIll:
I tried a few combinations, some may be irellevant, but i was not sure about the sd module interaction with my other magisk modules (Riru, edxposed, magisk hide, systemless hosts).

In conclusion sd module did never allow me to make or receive calls, no matter which version and which options I selected.

There were two cases where uninstalling sd module did not directly resolve the problem. Both (marked in red) where connected to uninstalling or installing another module in the same run. Not sure if this is possible or a reboot after each uninstall is recommended. After reinstalling e.g. Magisk hide it did work again.

Is this a problem with my magisk? Which version is recommended? I am using newest: Magisk 23.0 and App 23.0.

Action	Module and option	Calling account working
install	4.4 SD-Link only	no
uninstall	4.4	yes
install	4.4 ntfs & exfat binaries	no
uninstall	4.4	yes
install	4.4 no options	no
uninstall	4.4	yes
install	5.0 no options	no
uninstall	5.0	yes
uninstall	Riru and other modules (magisk hide, edxposed)	yes
install	5.0 no options	no
uninstall	5.0	yes
update	Magisk Hide	yes
install	5.0 ntfs & exfat binaries	no
uninstall	Magisk Hide	no
install	Magisk Hide	no
uninstall	systemless hosts	no
uninstall	5.0 ntfs & exfat binaries	no
uninstall	Magisk Hide	yes
install	4.4 ntfs & exfat binaries	no
uninstall	4.4 and install Magisk Hide in one go	no
uninstall	Magisk Hide	yes
install	Magisk Hide	yes
[Android General] Ziona:
Yes you have to reboot then test again after each module install/uninstall.

You can try an older magisk version, It may also be a module you use thats not compatible with my module.

If you can uninstall or disable all modules then test only mines to check.
[Android General] droidbot1337:
do you mind sharing your install process? i have tried to get this to work with LOS 18.1 on my pixel 3 and have had no luck. i might just disable all my other modules and give it one more try before i just give up.
[Android General] JidoFisterFilly:
i choose no ( Vol -) for every installation option.
[Android General] TaffestTaffer:
Hello, I have an issue with this module on my Xiaomi Redmi Note 8 Pro. Installation through Magisk appears to work but every time I reboot after installation the phone just shuts down after about a minute or enters bootloop. It doesn't seem to matter what installation options I use, even when I choose no to everything the problem continues. My phone has Android 10 (MIUI V12.0.5.0). Magisk version is 23.0 and there are no other modules installed. I have tried both v4.4 and v5.0. I would appreciate any help with this.
[Android General] Ziona:
When you install via magisk manager, upload the <modules name> magisk debug log - located within your internal storage root or download folder, depending on installer. Something non compatible with your device is happening on install.
[Android General] Taverius:
Just tried v5 and every volume press selects 2 options on the install script, as if it was getting 2 button presses.

Le ninja edit: 4.4 install script works fine.
[Android General] droidbot1337:
im having trouble getting this to work on my galaxy tab s5e running crdroid 7.11 (R). i have tried both 4.4 and 5.0 but i cant get VLC to load the files from my external thumb drives. any help?
[Android General] Abnova:
Hey, just writing to say that I used this on my old Infinix HOT 4. For some reason they did not bother to allow exFAT support even though it was running android 7. This module worked and created a new directory, "external_sd". Everything works fine although the only gripe I have with this is that it doesn't come up as an external sd card in the default android file explorer.
[Android General] Stijl:
You might need to enable Global Namespace for Root Processes in Magisk options and/or force switch SELinux to Permissive using this module. The built-in script for enabling Permissive doesn't work with every ROM out there, I had to do the two above steps to get V5.0 working on two phones running A9 and A10, respectively.